Diffserv-Aware Class-Type Object for the Path Computation Element Communication Protocol
RFC 5455
Yes
No Objection
Note: This ballot was opened for revision 02 and is now closed.
Lars Eggert No Objection
(David Ward; 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
(Dan Romascanu; former steering group member) No Objection
(Jari Arkko; former steering group member) No Objection
Title and abstract spell diff-serv differently: Diff-Serv Diff-Serve which is right?
(Jon Peterson; former steering group member) No Objection
(Magnus Westerlund; former steering group member) No Objection
(Mark Townsley; former steering group member) No Objection
(Pasi Eronen; former steering group member) No Objection
(Ron Bonica; former steering group member) No Objection
(Russ Housley; former steering group member) No Objection
(Tim Polk; former steering group member) No Objection
Section 3.3, paragraph 6 suggest the following rewording: OLD A PCE that recognizes the CLASSTYPE object finds that P flag is not set in the CLASSTYPE object, it MUST send PCE error message towards the sender with the with the error type and error value specified in [PCEP-ID]. NEW A PCE that recognizes the CLASSTYPE object, but finds that the P flag is not set in the CLASSTYPE object, MUST send a PCE error message towards the sender with the error type and error value specified in [PCEP-ID].