Requirements for Operations, Administration, and Maintenance (OAM) in MPLS Transport Networks
RFC 5860
Yes
No Objection
Note: This ballot was opened for revision 06 and is now closed.
Lars Eggert (was Discuss) No Objection
Section 2.2.12., paragraph 1: > The MPLS-TP OAM toolset MUST provide a function to enable the > quantification of the one-way, and if appropriate, the two-way, delay > of a PW, LSP or Section. Both the IETF and the ITU-T have detailed delay metrics, and they are even aligned between the two bodies [RFC2679][RFC2681]. Should we refer to these here? Section 3., paragraph 1: > A mechanism (e.g., rate limiting) MUST be provided to prevent OAM > packets from causing congestion in the Packet Switched Network. Rate limiting only works in conjunciton with reserved PSN capacity for OAM (limit the rate to at most the reserved capacity.) Section 2.1.1., paragraph 1: > point associated bidirectional LSPs, point-to-point undirectional Nit: s/undirectional/unidirectional/
(Adrian Farrel; former steering group member) Yes
(Dan Romascanu; former steering group member) (was Discuss) Yes
(Jari Arkko; former steering group member) No Objection
(Lisa Dusseault; former steering group member) No Objection
(Ralph Droms; former steering group member) No Objection
(Robert Sparks; former steering group member) No Objection
(Ron Bonica; former steering group member) (was Discuss) No Objection
(Ross Callon; former steering group member) No Objection
(Russ Housley; former steering group member) No Objection
(Tim Polk; former steering group member) (was No Record, Discuss) No Objection