Re: [mpls] MPLS-RT review of draft-mirsky-mpls-p2mp-bfd-04

[Greg Mirsky <[e-mail]>]

Dear Andy,
thank you for your thorough review and the most helpful comments. I'll work
on the update to address them.

Regards,
Greg

On Wed, Oct 24, 2018 at 9:17 AM Andrew G. Malis <[e-mail]> wrote:

> I’ve been selected as an MPLS-RT reviewer for
> draft-mirsky-mpls-p2mp-bfd-04, which is currently a candidate for MPLS WG
> adoption. This draft documents procedures for using BFD for multipoint
> networks to detect data plane failures in MPLS p2mp LSPs.
>
> The BFD WG has been working on draft-ietf-bfd-multipoint, which describes
> BFD procedures for multipoint and multicast networks.
> draft-mirsky-mpls-p2mp-bfd uses that draft as a basis to detect MPLS data
> plane failures for p2mp LSPs. This is a straightforward and useful
> application of the BFD draft for MPLS data plane failure detection.
>
> However, I would have expected to see at least a reference to RFC 4687,
> "Operations and Management (OAM) Requirements for Point-to-Multipoint MPLS
> Networks", and some text on how this draft addresses the requirements in
> that draft.
>
> I also expected more text on the relationship between this draft and RFC
> 6425, "Detecting Data-Plane Failures in Point-to-Multipoint MPLS -
> Extensions to LSP Ping"', and more of an explanation of why the keyword MAY
> is used in sections 4.1 and 4.2 - what are the implications of following or
> not following the MAY in each case?
>
> The draft also needs an editing pass, for example "MaultipointHead" for "MultipointHead"
> and some incorrect English grammar in several places.
>
> Once these items have been addressed, I think that the draft should be
> ready for an adoption call.
>
> Cheers,
> Andy
>
>
>