[prev in list] [next in list] [prev in thread] [next in thread]
List: ietf-saag
Subject: [saag] Fwd: Two topics of discussion for the Sec Dispatch session
From: Atul Tulshibagwale <atul () sgnl ! ai>
Date: 2024-03-15 8:15:15
Message-ID: CANtBS9fEsNOTU4x5TqQ62ZB5NvkyCF2o_UR3c1empue+3mmAAQ () mail ! gmail ! com
[Download RAW message or body]
[Attachment #2 (multipart/alternative)]
FYI, not sure if this belongs here, or in the secdispatch mailing list (to
which I've sent this email earlier)
There are a couple of topics for which I have been seeking answers. I don't
know if these are appropriate topics for the saag session next week. I will
be attending remotely, and can prepare a presentation for the second point
below if required.
1. *Errata to RFC 9493* There is an errata required for RFC9493
<https://datatracker.ietf.org/doc/rfc9493/> (Subject Identifiers for
Security Event Tokens). The errata request is here
<https://www.rfc-editor.org/errata/eid7727>. The errata requests a
change to the registry created by this RFC, and there was consensus on
the mailing list
<https://mailarchive.ietf.org/arch/msg/id-event/-S-MsO2W6PeFF_O5kjP8om-7QNM/>
that the errata should be accepted and the appropriate change reflected in
the IANA registry. However, since the WG is completed, there was no clear
identification of how to go about making these changes. If there is
discussion required on this topic, we should have it in the meeting in
Brisbane.
2. *New PushPull Delivery Proposal* While we currently have specified
Push delivery (RFC 8935 <https://datatracker.ietf.org/doc/html/rfc8935>)
and Poll delivery (RFC 8936
<https://datatracker.ietf.org/doc/html/rfc8936>), we are seeing a clear
requirement in the OpenID Shared Signals Working Group (SSWG) where a
Transmitter is also a Receiver, and we would like to have a way of
symmetric asynchronous event delivery. I would like to propose a new spec
for this, but since the WG is closed, I wanted to know how to go about
doing this. I realize the date for proposing new ideas for IETF 119 is
past, but I can propose it after IETF 119 and discuss it in Vancouver. The
topic I would like to discuss in IETF 119 is: What is the venue to propose
this new idea for a combined "push and pull" delivery mechanism?
Thanks,
Atul
--
<https://sgnl.ai>
Atul Tulshibagwale
CTO
<https://linkedin.com/in/tulshi> <https://twitter.com/zirotrust>
<atul@sgnl.ai>
[Attachment #5 (text/html)]
<div dir="ltr"><div>FYI, not sure if this belongs here, or in the secdispatch mailing \
list (to which I've sent this email earlier)<br><div class="gmail_quote"><div \
dir="ltr"><div><br></div><div>There are a couple of topics for which I have been \
seeking answers. I don't know if these are appropriate topics for the saag \
session next week. I will be attending remotely, and can prepare a presentation for \
the second point below if required.</div><div><ol><li><b>Errata to RFC 9493</b> There \
is an errata required for <a href="https://datatracker.ietf.org/doc/rfc9493/" \
target="_blank">RFC9493</a> (Subject Identifiers for Security Event Tokens). The \
errata request is <a href="https://www.rfc-editor.org/errata/eid7727" \
target="_blank">here</a>. The errata requests a change to the registry created by \
this RFC, and there was <a \
href="https://mailarchive.ietf.org/arch/msg/id-event/-S-MsO2W6PeFF_O5kjP8om-7QNM/" \
target="_blank">consensus on the mailing list</a> that the errata should be accepted \
and the appropriate change reflected in the IANA registry. However, since the WG is \
completed, there was no clear identification of how to go about making these changes. \
If there is discussion required on this topic, we should have it in the meeting in \
Brisbane.</li><li><b>New PushPull Delivery Proposal</b> While we currently have \
specified Push delivery (<a href="https://datatracker.ietf.org/doc/html/rfc8935" \
target="_blank">RFC 8935</a>) and Poll delivery (<a \
href="https://datatracker.ietf.org/doc/html/rfc8936" target="_blank">RFC 8936</a>), \
we are seeing a clear requirement in the OpenID Shared Signals Working Group (SSWG) \
where a Transmitter is also a Receiver, and we would like to have a way of symmetric \
asynchronous event delivery. I would like to propose a new spec for this, but since \
the WG is closed, I wanted to know how to go about doing this. I realize the date for \
proposing new ideas for IETF 119 is past, but I can propose it after IETF 119 and \
discuss it in Vancouver. The topic I would like to discuss in IETF 119 is: What is \
the venue to propose this new idea for a combined "push and pull" delivery \
mechanism?</li></ol><div>Thanks,</div></div><div>Atul</div><div><br></div><span \
class="gmail_signature_prefix">-- </span><br><div dir="ltr" class="gmail_signature" \
data-smartmail="gmail_signature"><div dir="ltr"><span><div dir="ltr" \
style="margin-left:0pt" align="left"><table \
style="border:none;border-collapse:collapse"><colgroup><col width="142"><col \
width="482"></colgroup><tbody><tr style="height:0pt"><td \
style="vertical-align:middle;padding:-9.432pt -9.432pt -9.432pt \
-9.432pt;overflow:hidden"><p dir="ltr" \
style="line-height:1.2;margin-top:0pt;margin-bottom:0pt"><a href="https://sgnl.ai" \
target="_blank"><span style="font-size:11pt;font-family:"Work \
Sans",sans-serif;color:rgb(17,85,204);background-color:transparent;vertical-align:baseline;white-space:pre-wrap"><span \
style="border:none;display:inline-block;overflow:hidden;width:137px;height:68px"><img \
src="https://lh3.googleusercontent.com/aO7jB_JqOxA0tVDXsAotNQnsfEkxEORgtkVnVFrmkR7O8j3 \
B4lbbRsGFuprzQhfDmri2YH8_dnjPiZnGMZxIcT9xRcdY6rYm-xGophLkgvl_v8istAefyh4qkSVINQtPfcmq5BZiKbfFHmursSUHyll1jEWBTd--nw26MIMKd86Br32rGZkvJwnEED_nzQ" \
width="137" height="68" \
style="margin-left:0px;margin-top:0px"></span></span></a></p></td><td \
style="vertical-align:top;padding:5pt 5pt 5pt 5pt;overflow:hidden"><p dir="ltr" \
style="line-height:1.44;margin-top:0pt;margin-bottom:0pt"><span \
style="font-size:11pt;font-family:"Work \
Sans",sans-serif;color:rgb(0,0,0);background-color:transparent;vertical-align:baseline;white-space:pre-wrap">Atul \
Tulshibagwale</span></p><p dir="ltr" \
style="line-height:1.44;margin-top:0pt;margin-bottom:0pt"><span \
style="font-size:11pt;font-family:"Work \
Sans",sans-serif;color:rgb(102,102,102);background-color:transparent;vertical-align:baseline;white-space:pre-wrap">CTO \
</span></p><p dir="ltr" \
style="line-height:1.2;margin-top:0pt;margin-bottom:0pt"><font size="1"><span \
style="font-family:"Work \
Sans",sans-serif;color:rgb(17,85,204);background-color:transparent;vertical-align:baseline;white-space:pre-wrap"><span \
style="border:none;display:inline-block;overflow:hidden;width:20px;height:27px"><a \
href="https://linkedin.com/in/tulshi" target="_blank"><img \
src="https://lh6.googleusercontent.com/ezm4lDcLtajK4RMqqHALoRgXyaC4HRlw0wWsR2Jvms0V9Wr \
xr3x5G66zsUrYpRXyeJ3RwLS3GdKUwO0Ui5mXPodSkUx8Xsarf_vj6WlJ05Y1qJoMFTlCZnEgtHvlJ7_7Dr7zWNjkvf3nMW9u1P5ye76SeHgz2QqGQ_rm-sjqYOS-vH1UZL7Yiewi4UO3Qw" \
width="20" height="27" style="margin-left:0px;margin-top:0px"></a> \
</span></span><span style="font-family:"Work \
Sans",sans-serif;color:rgb(0,0,0);background-color:transparent;vertical-align:baseline;white-space:pre-wrap"><span \
style="border:none;display:inline-block;overflow:hidden;width:20px;height:27px"><a \
href="https://twitter.com/zirotrust" target="_blank"><img \
src="https://lh6.googleusercontent.com/HAnAvykj318aQf5zTUZkjIJDtwelDecFi5d-idBrpUDBj7a \
KTdup5Mfia6UIbXTAP46zg7gigNnroQ9he3j81Sf9qCRRSS-w_nZ3oSXJnYLbPlCXgt6IqoifgHXETuJSRvFIZRIdn_aAbtp8ilKFyIVuTXjVe6cNAfXc5KZNwJeYinwfZZxVvHHaR5uIdQ" \
width="20" height="27" style="margin-left:0px;margin-top:0px"></a> </span></span><a \
href="mailto:atul@sgnl.ai" target="_blank"><img \
src="https://lh3.googleusercontent.com/63PpVJLMybZyfD61JVu0TVH_KkP_IhneeBpDNvbd1KeSFJn \
6KZzWCgp4hFbrTrIxfksYyM-_wOjNKbjEhSQ2khRXVI3XKcwABLNLI_bFjkN0_NgVoijs_nIRcVJKeQm0s0MRdtkUkCOp5Omyv1faqcNiQxGEUyAvmE9HkeeQCeHa-LxleK0oHSAyQrDY6g" \
width="21" height="21" \
style="background-color:transparent;color:rgb(0,0,0);font-family:Arial;white-space:pre \
-wrap;margin-left:0px;margin-top:0px"></a></font></p></td></tr></tbody></table></div></span></div></div></div>
</div></div></div>
_______________________________________________
saag mailing list
saag@ietf.org
https://www.ietf.org/mailman/listinfo/saag
[prev in list] [next in list] [prev in thread] [next in thread]
Configure |
About |
News |
Add a list |
Sponsored by KoreLogic