Last Call Review of draft-ietf-mpls-oam-ipv6-rao-02

Request Review of draft-ietf-mpls-oam-ipv6-rao
Requested rev. no specific revision (document currently at 03)
Type Last Call Review
Team Ops Directorate (opsdir)
Deadline 2015-02-17
Requested 2015-01-31
Authors Kamran Raza, Nobo Akiya, Carlos Pignataro
Draft last updated 2015-03-01
Completed reviews Genart Last Call review of -02 by Brian Carpenter (diff)
Genart Telechat review of -03 by Brian Carpenter
Secdir Last Call review of -02 by Vincent Roca (diff)
Opsdir Last Call review of -02 by Tina Tsou (diff)
Assignment Reviewer Tina Tsou
State Completed
Review review-ietf-mpls-oam-ipv6-rao-02-opsdir-lc-tsou-2015-03-01
Reviewed rev. 02 (document currently at 03)
Review result Has Nits
Review completed: 2015-03-01


Dear all,

I have reviewed this document as part of the Operational directorate's ongoing effort to review all IETF documents being processed by the IESG. These comments were written with the intent of improving
 the operational aspects of the IETF drafts. Comments that are not addressed in last call may be included in AD reviews during the IESG review. Document editors and WG chairs should treat these comments just like any other last call comments. 

Meta: You may want to elaborate a bit on what you say about IPv6 "not

having a generic RAO" -- FWIW, I understood what you meant only after

checking RFC5350 and realizing that for the IPv6 case RAOs have so far

been specified for specific use cases (e.g. MLD).

* Section 1, page 2:

Similarly, the section 4.5 states that IP Router

  Alert Option MUST be set in the IP header of an MPLS Echo Reply

  message if the Reply Mode in the echo request is set to "Reply via an

  IPv4/IPv6 UDP packet with Router Alert".

s/the section 4.5 states that IP Router/Section 4.5 states that the IP


Other than that, the document is ready for publication.

Thank you,