Last Call Review of draft-kyzivat-case-sensitive-abnf-01
review-kyzivat-case-sensitive-abnf-01-opsdir-lc-shore-2014-09-19-00
| Request | Review of | draft-kyzivat-case-sensitive-abnf |
|---|---|---|
| Requested rev. | no specific revision (document currently at 02) | |
| Type | Last Call Review | |
| Team | Ops Directorate (opsdir) | |
| Deadline | 2014-09-30 | |
| Requested | 2014-09-05 | |
| Authors | Paul Kyzivat | |
| Draft last updated | 2014-09-19 | |
| Completed reviews |
Genart Last Call review of -01 by Brian Carpenter
(diff)
Genart Last Call review of -02 by Brian Carpenter Secdir Last Call review of -01 by Chris Lonvick (diff) Opsdir Last Call review of -01 by Melinda Shore (diff) |
|
| Assignment | Reviewer | Melinda Shore |
| State | Completed | |
| Review | review-kyzivat-case-sensitive-abnf-01-opsdir-lc-shore-2014-09-19 | |
| Reviewed rev. | 01 (document currently at 02) | |
| Review result | Ready | |
| Review completed: | 2014-09-19 |
Review
review-kyzivat-case-sensitive-abnf-01-opsdir-lc-shore-2014-09-19
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. Summary: Ready This document describes a modification to the base ABNF definition to allow the specification of case-sensitive string literals. This may impact those developing protocol specifications and those implementing IETF protocol specifications but is not likely to have an operational impact. It is possible (but not likely) that there may be future impacts on existing OAM protocols in -bis specifications. Any nits we noticed were picked up in the sec-dir review ( https://www.ietf.org/mail-archive/web/secdir/current/msg05000.html ). Melinda