<html xmlns:o="urn:schemas-microsoft-com:office:office" xmlns:w="urn:schemas-microsoft-com:office:word" xmlns:m="http://schemas.microsoft.com/office/2004/12/omml" xmlns="http://www.w3.org/TR/REC-html40">
<head>
<meta http-equiv="Content-Type" content="text/html; charset=Windows-1252">
<meta name="Generator" content="Microsoft Word 15 (filtered medium)">
<style><!--
/* Font Definitions */
@font-face
{font-family:"Cambria Math";
panose-1:2 4 5 3 5 4 6 3 2 4;}
@font-face
{font-family:Calibri;
panose-1:2 15 5 2 2 2 4 3 2 4;}
@font-face
{font-family:"Times New Roman \(Body CS\)";
panose-1:2 11 6 4 2 2 2 2 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0in;
font-size:10.0pt;
font-family:"Calibri",sans-serif;}
a:link, span.MsoHyperlink
{mso-style-priority:99;
color:blue;
text-decoration:underline;}
samp
{mso-style-priority:99;
font-family:"Courier New";}
span.apple-converted-space
{mso-style-name:apple-converted-space;}
span.EmailStyle20
{mso-style-type:personal-reply;
font-family:"Arial",sans-serif;
color:windowtext;}
.MsoChpDefault
{mso-style-type:export-only;
font-size:10.0pt;}
@page WordSection1
{size:8.5in 11.0in;
margin:1.0in 1.0in 1.0in 1.0in;}
div.WordSection1
{page:WordSection1;}
--></style>
</head>
<body lang="EN-US" link="blue" vlink="purple" style="word-wrap:break-word;-webkit-nbsp-mode: space;line-break:after-white-space">
<div class="WordSection1">
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Arial",sans-serif">Thanks Phil! We will discuss on the next WG call.<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Arial",sans-serif"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Arial",sans-serif">tim<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Arial",sans-serif"><o:p> </o:p></span></p>
<div style="border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0in 0in 0in">
<p class="MsoNormal" style="margin-bottom:12.0pt"><b><span style="font-size:12.0pt;color:black">From:
</span></b><span style="font-size:12.0pt;color:black">Phillip Hunt <phil.hunt@independentid.com><br>
<b>Date: </b>Thursday, August 18, 2022 at 19:06<br>
<b>To: </b>Tim Cappalli <Tim.Cappalli@microsoft.com><br>
<b>Cc: </b>OpenID RISC List <openid-specs-risc@lists.openid.net><br>
<b>Subject: </b>Re: [Openid-specs-risc] Question on delivery methods<o:p></o:p></span></p>
</div>
<p class="MsoNormal"><span style="font-size:11.0pt">Tim,<o:p></o:p></span></p>
<div>
<p class="MsoNormal"><span style="font-size:11.0pt"><o:p> </o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-size:11.0pt">I’m not sure what you mean by “I don't believe the secevent RFCs say how they should be referenced”. They would never do that.<o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-size:11.0pt"><o:p> </o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-size:11.0pt">Inside the stream configuration which is entirely within the SSEF, I think you can reference any way you want. <o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-size:11.0pt"><o:p> </o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-size:11.0pt">The confusion I had was that <a href="https://nam06.safelinks.protection.outlook.com/?url=https%3A%2F%2Fschemas.openid.net%2Fsecevent%2Frisc%2Fdelivery-method%2Fpush&data=05%7C01%7CTim.Cappalli%40microsoft.com%7C25b171c7399b4f048d4508da816e49c8%7C72f988bf86f141af91ab2d7cd011db47%7C1%7C0%7C637964607945199780%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=eiNcQw3t3n%2BzIBD%2F3Nl5Tg2AME4KA3UAdXxrZ9XPWIU%3D&reserved=0"><span style="font-size:10.0pt;font-family:"Courier New";color:#2020FF">https://schemas.openid.net/secevent/risc/delivery-method/push</span></a> suggested
an entirely different method than RFC8935. If that’s not the intention, then just use RFC8935 or "<a href="https://nam06.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.rfc-editor.org%2Frfc%2Frfc8935.txt&data=05%7C01%7CTim.Cappalli%40microsoft.com%7C25b171c7399b4f048d4508da816e49c8%7C72f988bf86f141af91ab2d7cd011db47%7C1%7C0%7C637964607945199780%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=dSPIJ6xNXM1zdb6C4UEQ92qDoqNDLm50GM1RhqxAPAo%3D&reserved=0">https://www.rfc-editor.org/rfc/rfc8935.txt</a>”.
The rfc-editor link would be considered the authoritative link for an RFC.<o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-size:11.0pt"><o:p> </o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-size:11.0pt">The openid specific URI had given me the impression openid was doing yet another delivery method than the IETF specs (which of course I could not find).<o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-size:11.0pt"><o:p> </o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-size:11.0pt;color:black">Phillip Hunt</span><span style="font-size:11.0pt"><o:p></o:p></span></p>
</div>
<div>
<div>
<div>
<div>
<p class="MsoNormal"><span style="font-size:11.0pt;color:black">@independentid<o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-size:11.0pt;color:black"><a href="mailto:phil.hunt@independentid.com">phil.hunt@independentid.com</a><o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-size:11.0pt;color:black"><o:p> </o:p></span></p>
</div>
</div>
<p class="MsoNormal" style="margin-bottom:12.0pt"><span style="font-size:11.0pt"><o:p> </o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-size:11.0pt"><br>
<br>
<o:p></o:p></span></p>
<blockquote style="margin-top:5.0pt;margin-bottom:5.0pt">
<div>
<p class="MsoNormal"><span style="font-size:11.0pt">On Aug 18, 2022, at 11:56 AM, Tim Cappalli <<a href="mailto:Tim.Cappalli@microsoft.com">Tim.Cappalli@microsoft.com</a>> wrote:<o:p></o:p></span></p>
</div>
<p class="MsoNormal"><span style="font-size:11.0pt"><o:p> </o:p></span></p>
<div>
<div>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Arial",sans-serif">Hey Phil – thanks for bringing this up. I don't believe the secevent RFCs say how they should be referenced.</span><o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Arial",sans-serif"> </span><o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Arial",sans-serif">Are you suggesting we should reference the RFC numbers instead of URIs?</span><o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Arial",sans-serif"> </span><o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Arial",sans-serif">Tim</span><o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Arial",sans-serif"> </span><o:p></o:p></p>
</div>
<div style="border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0in 0in 0in">
<p class="MsoNormal" style="margin-bottom:12.0pt"><b><span style="font-size:12.0pt">From:<span class="apple-converted-space"> </span></span></b><span style="font-size:12.0pt">Openid-specs-risc <<a href="mailto:openid-specs-risc-bounces@lists.openid.net">openid-specs-risc-bounces@lists.openid.net</a>>
on behalf of Phillip Hunt via Openid-specs-risc <<a href="mailto:openid-specs-risc@lists.openid.net">openid-specs-risc@lists.openid.net</a>><br>
<b>Date:<span class="apple-converted-space"> </span></b>Thursday, August 18, 2022 at 14:28<br>
<b>To:<span class="apple-converted-space"> </span></b>OpenID RISC List <<a href="mailto:openid-specs-risc@lists.openid.net">openid-specs-risc@lists.openid.net</a>><br>
<b>Subject:<span class="apple-converted-space"> </span></b>[Openid-specs-risc] Question on delivery methods</span><o:p></o:p></p>
</div>
<div>
<div>
<p class="MsoNormal"><span style="font-size:11.0pt">Looking at the shared signals framework spec (<a href="https://nam06.safelinks.protection.outlook.com/?url=https%3A%2F%2Fopenid.net%2Fspecs%2Fopenid-sse-framework-1_0-ID1.html&data=05%7C01%7CTim.Cappalli%40microsoft.com%7C25b171c7399b4f048d4508da816e49c8%7C72f988bf86f141af91ab2d7cd011db47%7C1%7C0%7C637964607945199780%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=1%2BJnCoOS%2FxJTgs9IyQtMozyRntJDX4h%2B806M7rx80tY%3D&reserved=0">https://openid.net/specs/openid-sse-framework-1_0-ID1.html</a>), </span><o:p></o:p></p>
</div>
</div>
<div>
<div>
<p class="MsoNormal"><span style="font-size:11.0pt"> </span><o:p></o:p></p>
</div>
</div>
<div>
<div>
<p class="MsoNormal"><span style="font-size:11.0pt">I noticed the delivery methods are not RFC8935/8936 (as per the SECEVENTS specs) but instead are: </span><o:p></o:p></p>
</div>
</div>
<div>
<div style="margin-left:.5in;margin-right:24.0pt">
<p class="MsoNormal"><samp><a href="https://nam06.safelinks.protection.outlook.com/?url=https%3A%2F%2Fschemas.openid.net%2Fsecevent%2Frisc%2Fdelivery-method%2Fpush&data=05%7C01%7CTim.Cappalli%40microsoft.com%7C25b171c7399b4f048d4508da816e49c8%7C72f988bf86f141af91ab2d7cd011db47%7C1%7C0%7C637964607945199780%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=eiNcQw3t3n%2BzIBD%2F3Nl5Tg2AME4KA3UAdXxrZ9XPWIU%3D&reserved=0">https://schemas.openid.net/secevent/risc/delivery-method/push</a></samp><o:p></o:p></p>
</div>
<div>
<div style="margin-left:.5in;margin-right:24.0pt">
<p class="MsoNormal"><samp><a href="https://nam06.safelinks.protection.outlook.com/?url=https%3A%2F%2Fschemas.openid.net%2Fsecevent%2Frisc%2Fdelivery-method%2Fpoll&data=05%7C01%7CTim.Cappalli%40microsoft.com%7C25b171c7399b4f048d4508da816e49c8%7C72f988bf86f141af91ab2d7cd011db47%7C1%7C0%7C637964607945199780%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=eidwdfl4jblZpf0piywCTJOQFYU3xoKi9l2yS4B%2BuB8%3D&reserved=0">https://schemas.openid.net/secevent/risc/delivery-method/poll</a></samp><o:p></o:p></p>
</div>
</div>
<div>
<div>
<p class="MsoNormal"><span style="font-size:11.0pt">Is there a difference between these methods and RFC8935, RFC8936? If they are different, is there a specification for these methods? Near as I can tell, the CISCO shared signals implementation is the same.</span><o:p></o:p></p>
</div>
</div>
</div>
<div>
<div>
<p class="MsoNormal"><span style="font-size:11.0pt"> </span><o:p></o:p></p>
</div>
</div>
<div>
<div>
<p class="MsoNormal"><span style="font-size:11.0pt">Thanks,</span><o:p></o:p></p>
</div>
</div>
<div>
<div>
<p class="MsoNormal"><span style="font-size:11.0pt"> </span><o:p></o:p></p>
</div>
</div>
<div>
<div>
<div>
<div>
<div>
<p class="MsoNormal"><span style="font-size:11.0pt">Phillip Hunt</span><o:p></o:p></p>
</div>
</div>
<div>
<div>
<p class="MsoNormal"><span style="font-size:11.0pt">@independentid</span><o:p></o:p></p>
</div>
</div>
<div>
<div>
<p class="MsoNormal"><span style="font-size:11.0pt"><a href="mailto:phil.hunt@independentid.com">phil.hunt@independentid.com</a></span><o:p></o:p></p>
</div>
</div>
</div>
</div>
</div>
</div>
</blockquote>
</div>
<p class="MsoNormal"><span style="font-size:11.0pt"><o:p> </o:p></span></p>
</div>
</div>
</body>
</html>