Multiprotocol Label Switching (MPLS) Label Stack Entry: "EXP" Field Renamed to "Traffic Class" Field
draft-ietf-mpls-cosfield-def-08
Yes
No Objection
Note: This ballot was opened for revision 08 and is now closed.
Lars Eggert No Objection
Section 1.2, paragraph 7: > The EXP field has been renamed to the TC field, and thus all > references in RFC 3270 to EXP field SHOULD be taken to refer > to the TC field. I think the "SHOULD" here needs to be a "MUST" - otherwise it leaves the option of not using the new name. (And I don't believe an RFC2119 term is appropriate here, so it should be a lowercase "must".) Similar phrasings occur in Sections 2.3 and 2.4, and they should be changed accordingly.
(Dan Romascanu; former steering group member) Yes
(David Ward; former steering group member) Yes
(Mark Townsley; former steering group member) Yes
(Ron Bonica; former steering group member) Yes
(Ross Callon; former steering group member) Yes
(Chris Newman; former steering group member) No Objection
(Cullen Jennings; former steering group member) No Objection
(Lisa Dusseault; former steering group member) No Objection
(Magnus Westerlund; former steering group member) No Objection
(Pasi Eronen; former steering group member) No Objection
(Russ Housley; former steering group member) No Objection
(Tim Polk; former steering group member) No Objection
Abstract s/current use of the EXP this field/current use of this field/ Section 1. Introduction s/after the work on the document were started/after the work on the document was started/ Section 3. Use of the TC field s/have different TF fields from the rest/have different TC fields from the rest/