Last Call Review of draft-ietf-oauth-amr-values-04
review-ietf-oauth-amr-values-04-opsdir-lc-dunbar-2017-01-17-00
Request | Review of | draft-ietf-oauth-amr-values |
---|---|---|
Requested revision | No specific revision (document currently at 08) | |
Type | IETF Last Call Review | |
Team | Ops Directorate (opsdir) | |
Deadline | 2016-12-13 | |
Requested | 2016-11-29 | |
Authors | Michael B. Jones , Phil Hunt , Anthony Nadalin | |
I-D last updated | 2017-06-16 (Latest revision 2017-03-13) | |
Completed reviews |
Secdir IETF Last Call review of -04
by Catherine Meadows
(diff)
Genart IETF Last Call review of -04 by Paul Kyzivat (diff) Opsdir IETF Last Call review of -04 by Linda Dunbar (diff) Genart Telechat review of -05 by Paul Kyzivat (diff) |
|
Assignment | Reviewer | Linda Dunbar |
State | Completed | |
Request | IETF Last Call review on draft-ietf-oauth-amr-values by Ops Directorate Assigned | |
Reviewed revision | 04 (document currently at 08) | |
Result | Ready | |
Completed | 2017-01-17 |
review-ietf-oauth-amr-values-04-opsdir-lc-dunbar-2017-01-17-00
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 primarily for the benefit of the operational area directors. Document editors and WG chairs should treat these comments just like any other last call comments. I think the document is written very clear, it doesn’t create any operational issues to network. However, I am a bit surprised that the draft is “standard track”. The draft describes the procedure to register to IANA, acronyms, and template. I am not sure if you need an RFC for this, let alone “Standard Track”. At most, the draft should be “informational”. Linda Dunbar Huawei USA IP Technology Lab 5340 Legacy Drive, Plano, TX 75024 Tel: +1 469-277 - 5840 Fax: +1 469 -277 - 5900