Skip to main content

Last Call Review of draft-ietf-tsvwg-iana-dscp-registry-05
review-ietf-tsvwg-iana-dscp-registry-05-genart-lc-holmberg-2018-05-23-00

Request Review of draft-ietf-tsvwg-iana-dscp-registry
Requested revision No specific revision (document currently at 08)
Type Last Call Review
Team General Area Review Team (Gen-ART) (genart)
Deadline 2018-05-25
Requested 2018-05-11
Authors Gorry Fairhurst
I-D last updated 2018-05-23
Completed reviews Secdir Last Call review of -05 by Robert Sparks (diff)
Genart Last Call review of -05 by Christer Holmberg (diff)
Genart Telechat review of -06 by Christer Holmberg (diff)
Assignment Reviewer Christer Holmberg
State Completed
Request Last Call review on draft-ietf-tsvwg-iana-dscp-registry by General Area Review Team (Gen-ART) Assigned
Reviewed revision 05 (document currently at 08)
Result Almost ready
Completed 2018-05-23
review-ietf-tsvwg-iana-dscp-registry-05-genart-lc-holmberg-2018-05-23-00
I am the assigned Gen-ART reviewer for this draft. The General Area
Review Team (Gen-ART) reviews all IETF documents being processed
by the IESG for the IETF Chair.  Please treat these comments just
like any other last call comments.

For more information, please see the FAQ at

<https://trac.ietf.org/trac/gen/wiki/GenArtfaq>.

Document: draft-ietf-tsvwg-iana-dscp-registry-05
Reviewer: Christer Holmberg
Review Date: 2018-05-23
IETF LC End Date: 2018-05-25
IESG Telechat date: Not scheduled for a telechat

Summary: The document is well written, and almost ready for publication. I have
one minor editorial comment that I'd like the authors to address.

Major issues: None

Minor issues: None

Nits/editorial comments:

The Abstract says:

"This update to RFC2474 changes the IANA assignment method..."

...and the Introduction says:

 "To allow the IETF to utilise Pool 3 codepoints, this document
   requests IANA to to manage Pool 3 assignments for DSCP values in Pool
   3 via the Standards Action policy [RFC8126].  This assignment method
   requires publication of a Standards Track or Best Current Practice
   RFC."

I suggest to replace "method" with "policy".