<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=utf-8"><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;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0in;
margin-bottom:.0001pt;
font-size:11.0pt;
font-family:"Calibri",sans-serif;}
a:link, span.MsoHyperlink
{mso-style-priority:99;
color:blue;
text-decoration:underline;}
span.EmailStyle18
{mso-style-type:personal-reply;
font-family:"Calibri",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;}
/* List Definitions */
@list l0
{mso-list-id:204605453;
mso-list-template-ids:-64559564;}
ol
{margin-bottom:0in;}
ul
{margin-bottom:0in;}
--></style></head><body lang=EN-US link=blue vlink=purple><div class=WordSection1><p class=MsoNormal>Hi Atul,<o:p></o:p></p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>Thank you for your contribution!<o:p></o:p></p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>You are introducing 3-4 new concepts into this draft (including the notion of “conformance” which you have not listed below). I think it would be more appropriate to start an email thread on this list on each one, in order to gauge the working group’s interest. In general the IETF reserves the PR process for smaller, editorial changes, or else for changes that had already been discussed by the mailing list.<o:p></o:p></p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>Thanks,<o:p></o:p></p><p class=MsoNormal> Yaron<o:p></o:p></p><p class=MsoNormal><o:p> </o:p></p><div style='border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0in 0in 0in'><p class=MsoNormal><b><span style='font-size:12.0pt;color:black'>From: </span></b><span style='font-size:12.0pt;color:black'>Id-event <id-event-bounces@ietf.org> on behalf of Atul Tulshibagwale <atultulshi=40google.com@dmarc.ietf.org><br><b>Date: </b>Monday, July 13, 2020 at 05:38<br><b>To: </b><id-event@ietf.org>, Openid-specs-risc <openid-specs-risc@lists.openid.net><br><b>Cc: </b>Annabelle Richard <richanna@amazon.com>, Marius Scurtescu <marius.scurtescu@coinbase.com>, michaeljones_fwd <Michael.Jones@microsoft.com><br><b>Subject: </b>[Id-event] SSE changes to the Subject Identifiers Spec<o:p></o:p></span></p></div><div><p class=MsoNormal><o:p> </o:p></p></div><div><p class=MsoNormal>Hi all,<o:p></o:p></p><div><p class=MsoNormal>We've made a number of changes to the subject-identifiers spec in the OpenID "Shared Signals and Events" working group. I have incorporated these changes in a pull request to the present draft in the repository <a href="https://github.com/richanna/secevent">https://github.com/richanna/secevent</a>.<o:p></o:p></p></div><div><p class=MsoNormal><o:p> </o:p></p></div><div><p class=MsoNormal>Please review the changes here:<o:p></o:p></p></div><div><p class=MsoNormal><a href="https://github.com/richanna/secevent/pull/1">https://github.com/richanna/secevent/pull/1</a><o:p></o:p></p></div><div><p class=MsoNormal><o:p> </o:p></p></div><div><p class=MsoNormal>Summary of the changes:<o:p></o:p></p></div><div><ol start=1 type=1><li class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;mso-list:l0 level1 lfo1'>Defined "Subject Principals" as management entities that are represented by the subject identifiers<o:p></o:p></li><li class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;mso-list:l0 level1 lfo1'>Defined "Subject Principal Administrative Groupings" or SPAGs that may be used for certain events that pertain to the entire grouping. IRL Spags may be tenants in a multi-tenanted host or may be OUs or groups within a tenant.<o:p></o:p></li><li class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;mso-list:l0 level1 lfo1'>Defined the following Common Claims that may be applied to any subject identifier:<o:p></o:p></li></ol><ol start=3 type=1><ol start=1 type=1><li class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;mso-list:l0 level2 lfo1'>spag_id: An optional claim that can be used to ensure uniqueness of the subject identifier within the SPAG.<o:p></o:p></li><li class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;mso-list:l0 level2 lfo1'>category: An optional claim that can be used to define the scope of the subject identifier. E.g., Does a phone number represent the user or the device the user is using. The category can disambiguate this.<o:p></o:p></li></ol></ol><ol start=4 type=1><li class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;mso-list:l0 level1 lfo1'>Added a SAML subject identifier type as was needed by some use cases in SSE.<o:p></o:p></li><li class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;mso-list:l0 level1 lfo1'>Added myself as a co-author, given the scope of these changes.<o:p></o:p></li></ol><div><p class=MsoNormal>Thanks,<o:p></o:p></p></div></div><div><p class=MsoNormal>Atul<o:p></o:p></p></div><div><p class=MsoNormal><o:p> </o:p></p></div></div><p class=MsoNormal>_______________________________________________ Id-event mailing list Id-event@ietf.org https://www.ietf.org/mailman/listinfo/id-event <o:p></o:p></p></div></body></html>