Update to IANA Registration Procedures for Pool 3 Values in the Differentiated Services Field Codepoints (DSCP) Registry
RFC 8436

Note: This ballot was opened for revision 06 and is now closed.

Alvaro Retana No Objection

Benjamin Kaduk No Objection

Comment (2018-06-06 for -06)
No email
send info
Is there a good reference already for the security considerations of
bleaching the TOS field?  That's not really the main point of this
document, so I don't want to make you write something from scratch,
but since we mention the issue in passing it might be nice to have
a reference if one exists.

Section 3

   The new registry contents are shown in Figure 2.

nit: Figure 2 does not show the registry *contents*, but rather the
assignment policies.

Section 5

   The Registration Procedure for use of Pool 3 is "Standards Action"
   [RFC8126].  IANA is expected to normally make assignments from Pool
   1, until this Pool is exhausted, but MAY make assignments from Pool 3
   where the format of the codepoint has properties that are needed for
   a specific PHB. The required characteristics for choosing the DSCP
   value MUST be explained in the IANA considerations of the document
   that requests any assignment from Pool 3

Does/should this requirement go away when Pool 1 is completely
allocated?

Martin Vigoureux No Objection

Comment (2018-06-06 for -06)
No email
send info
Hello,

Alissa's question also came to my mind, so I support her COMMENT.

Twice in the document you give a definition to "Standards Action", but it is not strictly identical to the one of 8126. 
Citing RFC 8126 should be sufficient.

Warren Kumari No Objection

(Mirja K├╝hlewind; former steering group member) Yes

Yes ( for -06)
No email
send info

(Spencer Dawkins; former steering group member) Yes

Yes ( for -06)
No email
send info

(Adam Roach; former steering group member) No Objection

No Objection ( for -06)
No email
send info

(Alexey Melnikov; former steering group member) No Objection

No Objection (2018-06-04 for -06)
No email
send info
I am supporting Alissa's question.

(Alissa Cooper; former steering group member) No Objection

No Objection (2018-06-01 for -06)
No email
send info
The only question this raises for me is whether there are widespread experimental uses of Pool 3 codepoints. If so, will the people using those will be aware of this change, or is the likely impact of collisions not viewed as terribly problematic, or both?

(Ben Campbell; former steering group member) No Objection

No Objection (2018-06-06 for -06)
No email
send info
- The use of 2119/8174 keywords seem unneeded for this document. As far as I can tell, there's just a MAY that talks about IANA behavior.

- Please define "bleaching".

(Deborah Brungard; former steering group member) No Objection

No Objection ( for -06)
No email
send info

(Eric Rescorla; former steering group member) No Objection

No Objection ( for -06)
No email
send info

(Ignas Bagdonas; former steering group member) No Objection

No Objection ( for -06)
No email
send info

(Suresh Krishnan; former steering group member) No Objection

No Objection ( for -06)
No email
send info

(Terry Manderson; former steering group member) No Objection

No Objection ( for -06)
No email
send info