Last Call Review of draft-atarius-dispatch-meid-urn-as-instanceid-05
review-atarius-dispatch-meid-urn-as-instanceid-05-opsdir-lc-brownlee-2017-12-19-00

Request Review of draft-atarius-dispatch-meid-urn-as-instanceid
Requested rev. no specific revision (document currently at 08)
Type Last Call Review
Team Ops Directorate (opsdir)
Deadline 2017-12-08
Requested 2017-11-02
Other Reviews Genart Last Call review of -05 by Francis Dupont (diff)
Secdir Last Call review of -05 by Daniel Migault (diff)
Genart Telechat review of -05 by Francis Dupont (diff)
Review State Completed
Reviewer Nevil Brownlee
Review review-atarius-dispatch-meid-urn-as-instanceid-05-opsdir-lc-brownlee-2017-12-19
Posted at https://www.ietf.org/mail-archive/web/ops-dir/current/msg02965.html
Reviewed rev. 05 (document currently at 08)
Review result Has Nits
Draft last updated 2017-12-19
Review completed: 2017-12-19

Review
review-atarius-dispatch-meid-urn-as-instanceid-05-opsdir-lc-brownlee-2017-12-19

Hi all:

Last-Call review for draft-atarius-dispatch-meid-urn-as-instanceid-05

I have reviewed this document as part of the Operational directorate's
ongoing effort to review all IETF documents being processed by the IESG.
These comments were written with the intent of improving the operational
aspects of the IETF drafts. Comments that are not addressed in last call
may be included in AD reviews  during the IESG review.  Document editors
and WG chairs should treat these comments just like any other last call
comments.

Overall this draft is very tightly focused on 3gpp2 URNs, it will
therefore be important to Mobile Operators.

The draft is clearly written, spelling out exactly what's required for
this kind of URN, and exactly how such URNs will be used.  Its Security
Considerations section is particularly well done.
Overall, Mobile Operators will need to understand how these URNs will
be used in their networks - but this drafts explains that well.

Some tiny typos:
Section 3: s/The Mobile Communication/Mobile Communication/
and
Section 5: starts with "A single mode 3GPP2 UAC which ...", but
that's the first place where UAC appears. I had great difficulty finding that TLA with my browser, until I guessed it was User Agent
Client.  Saying "UAC (User Agent Client)" would help here!

Cheers, Nevil

--
---------------------------------------------------------------------
 Nevil Brownlee                          Computer Science Department
 Phone: +64 9 373 7599 x88941             The University of Auckland
 FAX: +64 9 373 7453   Private Bag 92019, Auckland 1142, New Zealand