A URN Namespace for Device Identity and Mobile Equipment Identity (MEID)
draft-atarius-dispatch-meid-urn-18

[Ballot comment]
I am letting Ben hold this document until comments from urn@ietf.org mailing list are received.

    and  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?

[Ballot comment]
  HEX              = DIGIT / "A" / "B" / "C" / "D" / "E" / "F"

Just do double check: do you always intent to use uppercase letters or are lowercase also allowed? If the former, than your ABNF is not correct (values in "" are always case-insensitive in ABNF).

    and  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?

(Via drafts-lastcall@iana.org): IESG/Authors/WG Chairs:

The IANA Services Operator has completed its review of draft-atarius-dispatch-meid-urn-13. If any part of this review is inaccurate, please let us know.

The IANA Services Operator understands that, upon approval of this document, there is a single action which we must complete.

In the Formal URN Namespaces registry on the Uniform Resource Names (URN) Namespaces registry page located at:

https://www.iana.org/assignments/urn-namespaces/

a single new namespace will be registerd as follows:

URN Namespace: 3gpp2
Template:
Reference: [ RFC-to-be ]

Because this registry requires Expert Review [RFC 8126] for registration, the IESG-designated experts for Formal URN Namespaces have asked that you send a review request to the mailing list urn@ietf.org. Expert review should be completed before your document can be approved for publication as an RFC.

The IANA Services Operator understands that this is the only action required to be completed upon approval of this document.

Note:  The actions requested in this document will not be completed until the document has been approved for publication as an RFC. This message is only to confirm what actions will be performed.


Thank you,

Sabrina Tanamal
IANA Services Specialist

The following Last Call announcement was sent out (ends 2017-12-08):

From: The IESG
To: IETF-Announce
CC: ben@nostrum.com, aallen@blackberry.com, draft-atarius-dispatch-meid-urn@ietf.org
Reply-To: ietf@ietf.org
Sender:
Subject: Last Call:  (A Uniform Resource Name Namespace for the Device Identity and the Mobile Equipment Identity (MEID)) to Informational RFC


The IESG has received a request from an individual submitter to consider the
following document: - 'A Uniform Resource Name Namespace for the Device
Identity and the
  Mobile Equipment Identity (MEID)'
  as Informational RFC

The IESG plans to make a decision in the next few weeks, and solicits final
comments on this action. Please send substantive comments to the
ietf@ietf.org mailing lists by 2017-12-08. Exceptionally, comments may be
sent to iesg@ietf.org instead. In either case, please retain the beginning of
the Subject line to allow automated sorting.

Abstract


  This document defines a Uniform Resource Name (URN) namespace for the
  Third Generation Partnership Project (3GPP2) and a Namespace Specific
  String (NSS) for the Mobile Equipment Identity (MEID).  The structure
  of an MEID is 15 hexadecimal encoded digits long and is defined in
  the Third Generation Partnership Project 2 (3GPP2) (see [S.R0048-A])
  to uniquely identify each individual mobile equipment (e.g., a
  handset or mobile phone).  The 3GPP2 has a requirement to be able to
  use an MEID as a URN.  This document fulfills that requirement.




The file can be obtained via
https://datatracker.ietf.org/doc/draft-atarius-dispatch-meid-urn/

IESG discussion can be tracked via
https://datatracker.ietf.org/doc/draft-atarius-dispatch-meid-urn/ballot/


No IPR declarations have been submitted directly on this I-D.