A URN Namespace for Device Identity and Mobile Equipment Identity (MEID)
draft-atarius-dispatch-meid-urn-18
Yes
(Ben Campbell)
No Objection
Warren Kumari
(Adam Roach)
(Alia Atlas)
(Alissa Cooper)
(Alvaro Retana)
(Benoît Claise)
(Deborah Brungard)
(Kathleen Moriarty)
(Mirja Kühlewind)
(Spencer Dawkins)
(Suresh Krishnan)
Note: This ballot was opened for revision 13 and is now closed.
Warren Kumari
No Objection
Ben Campbell Former IESG member
Yes
Yes
(for -13)
Unknown
Adam Roach Former IESG member
No Objection
No Objection
(for -14)
Unknown
Alexey Melnikov Former IESG member
(was Discuss)
No Objection
No Objection
(2018-01-11 for -14)
Unknown
I am letting Ben hold this document until comments from urn@ietf.org mailing list are received. <future-pp2-specifier> and <pp2-defined-nonempty> can comprise any ASCII characters compliant with URN syntax in [RFC5234]. This reads to be as if RFC 5234 is the URN syntax reference, but it is not. Identifiers in the '3gpp2' NID are defined and assigned by the 3GPP2 or an agency appointed by 3GPP2 after ensuring that the URNs to be assigned are unique. Uniqueness is achieved by checking against the IANA registry of previously assigned names. This seems to suggest that IANA is tracking assignments within the 3gpp2 URN Namespace, but this is not true. Maybe just delete the last sentence above?
Alia Atlas Former IESG member
No Objection
No Objection
(for -14)
Unknown
Alissa Cooper Former IESG member
No Objection
No Objection
(for -14)
Unknown
Alvaro Retana Former IESG member
No Objection
No Objection
(for -14)
Unknown
Benoît Claise Former IESG member
No Objection
No Objection
(for -14)
Unknown
Deborah Brungard Former IESG member
No Objection
No Objection
(for -14)
Unknown
Kathleen Moriarty Former IESG member
No Objection
No Objection
(for -14)
Unknown
Mirja Kühlewind Former IESG member
No Objection
No Objection
(for -14)
Unknown
Spencer Dawkins Former IESG member
No Objection
No Objection
(for -13)
Unknown
Suresh Krishnan Former IESG member
No Objection
No Objection
(for -14)
Unknown