Re: [Id-event] [UNVERIFIED SENDER] Re: I-D Action: draft-ietf-secevent-subject-identifiers-05.txt

[Mike Jones <[e-mail]>]

The registered OpenID Connect claim name is phone_number.  I’d use underscores so the names match.

                                                                -- Mike

From: Id-event <[e-mail]> On Behalf Of Richard Backman, Annabelle
Sent: Friday, August 2, 2019 3:18 PM
To: Dick Hardt <[e-mail]>
Cc: [e-mail]; [e-mail]
Subject: Re: [Id-event] [UNVERIFIED SENDER] Re: I-D Action: draft-ietf-secevent-subject-identifiers-05.txt

I believe the “-“ delimiter in subject identifier types is a carryover from RISC, where it matches the delimiters used in event types (“-“ since those appear as part of full event type URIs). Since we’re standardizing subject identifiers outside of RISC’s profile of SET, I’d be fine with switching “iss-sub” and “phone-number” to “iss_sub” and “phone_number”, respectively.

--
Annabelle Richard Backman
AWS Identity


From: Dick Hardt <[e-mail]<mailto:[e-mail]>>
Date: Wednesday, July 24, 2019 at 3:06 PM
To: "Richard Backman, Annabelle" <[e-mail]<mailto:[e-mail]>>
Cc: "[e-mail]<mailto:[e-mail]>" <[e-mail]<mailto:[e-mail]>>, "[e-mail]<mailto:[e-mail]>" <[e-mail]<mailto:[e-mail]>>
Subject: [UNVERIFIED SENDER] Re: [Id-event] I-D Action: draft-ietf-secevent-subject-identifiers-05.txt

What was the reason to have a dash in the type “phone-number” rather than an underscore “phone_number”?

On Wed, Jul 24, 2019 at 4:54 PM Richard Backman, Annabelle <richanna=[e-mail]<mailto:[e-mail]>> wrote:
This update to the Subject Identifiers for Security Event Tokens draft addresses comments raised at the secevents working group session this week. Specifically:

* Renamed the "phone" type to "phone-number" and its "phone" claim

to "phone_number".

—
Annabelle Backman
AWS Identity

On Jul 24, 2019, at 5:46 PM, "[e-mail]<mailto:[e-mail]>" <[e-mail]<mailto:[e-mail]>> wrote:

A New Internet-Draft is available from the on-line Internet-Drafts directories.
This draft is a work item of the Security Events WG of the IETF.

       Title           : Subject Identifiers for Security Event Tokens
       Authors         : Annabelle Backman
                         Marius Scurtescu
   Filename        : draft-ietf-secevent-subject-identifiers-05.txt
   Pages           : 15
   Date            : 2019-07-24

Abstract:
  Security events communicated within Security Event Tokens may support
  a variety of identifiers to identify the subject and/or other
  principals related to the event.  This specification formalizes the
  notion of subject identifiers as named sets of well-defined claims
  describing the subject, a mechanism for representing subject
  identifiers within a [JSON] object such as a JSON Web Token [JWT] or
  Security Event Token [SET], and a registry for defining and
  allocating names for these claim sets.


The IETF datatracker status page for this draft is:
https://datatracker.ietf.org/doc/draft-ietf-secevent-subject-identifiers/<https://nam06.safelinks.protection.outlook.com/?url=https%3A%2F%2Fdatatracker.ietf.org%2Fdoc%2Fdraft-ietf-secevent-subject-identifiers%2F&data=02%7C01%7CMichael.Jones%40microsoft.com%7Caba6951b02954371797708d7179741d7%7C72f988bf86f141af91ab2d7cd011db47%7C1%7C0%7C637003810743497680&sdata=oWTA1nb9ERYx568GdSZQIwfpkduPS4S2KScql7IqSDM%3D&reserved=0>

There are also htmlized versions available at:
https://tools.ietf.org/html/draft-ietf-secevent-subject-identifiers-05<https://nam06.safelinks.protection.outlook.com/?url=https%3A%2F%2Ftools.ietf.org%2Fhtml%2Fdraft-ietf-secevent-subject-identifiers-05&data=02%7C01%7CMichael.Jones%40microsoft.com%7Caba6951b02954371797708d7179741d7%7C72f988bf86f141af91ab2d7cd011db47%7C1%7C0%7C637003810743507672&sdata=dDdIX1beEaUgQoJES4Cg0C5IXzBZsa1ZXfpfvUNAhCg%3D&reserved=0>
https://datatracker.ietf.org/doc/html/draft-ietf-secevent-subject-identifiers-05<https://nam06.safelinks.protection.outlook.com/?url=https%3A%2F%2Fdatatracker.ietf.org%2Fdoc%2Fhtml%2Fdraft-ietf-secevent-subject-identifiers-05&data=02%7C01%7CMichael.Jones%40microsoft.com%7Caba6951b02954371797708d7179741d7%7C72f988bf86f141af91ab2d7cd011db47%7C1%7C0%7C637003810743507672&sdata=NgsPxBYezXy92OYZgWgLQ6HPtq4Eamy%2Fo1nbu%2FD%2BPgY%3D&reserved=0>

A diff from the previous version is available at:
https://www.ietf.org/rfcdiff?url2=draft-ietf-secevent-subject-identifiers-05<https://nam06.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.ietf.org%2Frfcdiff%3Furl2%3Ddraft-ietf-secevent-subject-identifiers-05&data=02%7C01%7CMichael.Jones%40microsoft.com%7Caba6951b02954371797708d7179741d7%7C72f988bf86f141af91ab2d7cd011db47%7C1%7C0%7C637003810743517669&sdata=BdYDGuypPEmgY7ctUO3tfwi2puwM7rIBbClyqK8cTIY%3D&reserved=0>


Please note that it may take a couple of minutes from the time of submission
until the htmlized version and diff are available at tools.ietf.org<https://nam06.safelinks.protection.outlook.com/?url=http%3A%2F%2Ftools.ietf.org&data=02%7C01%7CMichael.Jones%40microsoft.com%7Caba6951b02954371797708d7179741d7%7C72f988bf86f141af91ab2d7cd011db47%7C1%7C0%7C637003810743527665&sdata=uWqmGEKnY%2BD8Y6%2BC568NSs7BwtwJv%2BFcvoDbjEB9Vl4%3D&reserved=0>.

Internet-Drafts are also available by anonymous FTP at:
ftp://ftp.ietf.org/internet-drafts/

_______________________________________________
Id-event mailing list
[e-mail]<mailto:[e-mail]>
https://www.ietf.org/mailman/listinfo/id-event<https://nam06.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.ietf.org%2Fmailman%2Flistinfo%2Fid-event&data=02%7C01%7CMichael.Jones%40microsoft.com%7Caba6951b02954371797708d7179741d7%7C72f988bf86f141af91ab2d7cd011db47%7C1%7C0%7C637003810743527665&sdata=FPDo8uBEspfIqb9SU06VzKPFQqMnuMt0yvdrvZYeCNw%3D&reserved=0>
_______________________________________________
Id-event mailing list
[e-mail]<mailto:[e-mail]>
https://www.ietf.org/mailman/listinfo/id-event<https://nam06.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.ietf.org%2Fmailman%2Flistinfo%2Fid-event&data=02%7C01%7CMichael.Jones%40microsoft.com%7Caba6951b02954371797708d7179741d7%7C72f988bf86f141af91ab2d7cd011db47%7C1%7C0%7C637003810743537659&sdata=kLDzInm04yegWEjNttjFV%2BowU7anUKdKv9jPq1W0ivc%3D&reserved=0>