Last Call Review of draft-atarius-dispatch-meid-urn-as-instanceid-05

Request Review of draft-atarius-dispatch-meid-urn-as-instanceid
Requested rev. no specific revision (document currently at 08)
Type Last Call Review
Team Security Area Directorate (secdir)
Deadline 2017-12-08
Requested 2017-11-02
Other Reviews Genart Last Call review of -05 by Francis Dupont (diff)
Opsdir Last Call review of -05 by Nevil Brownlee (diff)
Genart Telechat review of -05 by Francis Dupont (diff)
Review State Completed
Reviewer Daniel Migault
Review review-atarius-dispatch-meid-urn-as-instanceid-05-secdir-lc-migault-2017-12-07
Posted at
Reviewed rev. 05 (document currently at 08)
Review result Ready
Draft last updated 2017-12-07
Review completed: 2017-12-07



I have reviewed this document as part of the security directorate's 
ongoing effort to review all IETF documents being processed by the 
IESG.  These comments were written primarily for the benefit of the 
security area directors.  Document editors and WG chairs should treat 
these comments just like any other last call comments.

The summary of the review is Ready

Some comments / questions:

1.  Introduction

   This specification specifies how the URN namespace reserved for 3GPP2
   identities and its NSS for the MEID as specified in draft-atarius-
   dispatch-meid-urn [8] can be used as an instance-id as specified in
   RFC 5626 [2] and also as used by RFC 5627 [3].

<mglt> I think it would be good to have the acronyms (URN, 3GPP2, NSS,
MEID) expanded in the introduction section as it is being done in the

   3GPP2 defines High Rate Packet Data (HRPD) with high data rates and
   it dispenses with the 1x Circuit Switched (1xCS) infrastructure.
   This means that with HRPD networks, voice calls will need to be
   conducted using IP and IMS.  However, the transition to all IP, SIP
   based IMS networks worldwide will take a great many years from the
   time of this writing and mobile devices will need to operate in both
   IP/SIP/IMS mode and circuit switched mode.  This means that calls and
   sessions will need to be handed over between IP/SIP/IMS mode and
   circuit switched mode mid-call or mid-session.  To achieve this the
   mobile device needs to be simultaneously attached via both the
   IP/SIP/IMS domain and the circuit switched domain.

<mglt> I am questioning whether "registered" would not be better
appropriated than "attached". My reading of attached is a dual 
radio case while "register" seems to include the single radio. 
I might be wrong as well.</mglt>