Last Call: <draft-atarius-dispatch-meid-urn-as-instanceid-05.txt> (Using the Mobile Equipment Identity (MEID) Uniform Resource Name (URN) as an Instance ID) to Informational RFC

The IESG <iesg-secretary@ietf.org> Thu, 02 November 2017 22:43 UTC

MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: The IESG <iesg-secretary@ietf.org>
To: IETF-Announce <ietf-announce@ietf.org>
Subject: Last Call: <draft-atarius-dispatch-meid-urn-as-instanceid-05.txt> (Using the Mobile Equipment Identity (MEID) Uniform Resource Name (URN) as an Instance ID) to Informational RFC
Auto-Submitted: auto-generated
Precedence: bulk
CC: ben@nostrum.com, aallen@blackberry.com, draft-atarius-dispatch-meid-urn-as-instanceid@ietf.org
Reply-To: ietf@ietf.org
Sender: iesg-secretary@ietf.org
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
Message-ID: <150966262028.32040.15224707222922251846.idtracker@ietfa.amsl.com>
Date: Thu, 02 Nov 2017 15:43:40 -0700
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf-announce/WVarsffu9fmVOFzDGUABk4XTuJA>

The IESG has received a request from an individual submitter to consider the
following document: - 'Using the Mobile Equipment Identity (MEID) Uniform
Resource Name (URN)
   as an Instance ID'
  <draft-atarius-dispatch-meid-urn-as-instanceid-05.txt> 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 specification specifies how the Uniform Resource Name (URN)
   namespace reserved for the Third Generation Partnership Project 2
   (3GPP2) identities and its Namespace Specific String (NSS) for the
   Mobile Equipment Identity (MEID) can be used as an instance-id.  Its
   purpose is to fulfill the requirements for defining how a specific
   URN needs to be constructed and used in the "+sip.instance" Contact
   header field parameter for outbound behavior.




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

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


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

Last Call: <draft-atarius-dispatch-meid-urn-as-in… The IESG