Re: [mpls] Fw: I-D Action: draft-smack-mpls-rfc4379bis-02.txt

[Loa Andersson <[e-mail]>]

Sasha,

The directives (or maybe ideas to work with) that the authors have is
basically to "do it all". I will let the authors answer to the
specifics, but one of the things I asked for is to get a first version
(we are now on the third) out to start up the discussion. That one
RFC or another is missing, is not necessarily a plan, but we know
that this has to be a wg wide effort to get it right.

I've already told the authors that we expect a f2f discussion in
Yokohama.

/Loa

On 2015-09-27 14:12, Alexander Vainshtein wrote:
> Hi all,
> I have a comment regarding draft-smack-mpls-rfc4379bis-02.
>
> According to the draft, its purpose is "take LSP Ping to an Internet  Standard". As part of this work the authors address all the outstanding Errata to the original RFC 4379, and update the references.
>
> I fully agree with the goal that the authors have set to themselves.
>
> However, I have noticed that there is quite a long list of RFCs  that update RFC 4379, and it would be nice to understand whether these updates have been incorporated or not.
>
> Specifically:
> 1.  RFC 6424 states that it "deprecates the Downstream Mapping TLV in favor of a new TLV".
> 2. RFC 6426 extends applicability of LSP Ping to MPLS-TP thus introducing new  address types and new TLVs
> 3. RFC 6289  extends LSP Ping to PWs signaled with LDP sessions running on top of IPv6 and introduces new sub-TLVs
> 4. RFC  7506 clarifies the use of IPv6 Router Alert option for LSP Ping.
> 5. RFC  7537 has introduced new IANA  registries for various aspects of LSP Ping.
>
> Neither of these RFCs is mentioned anywhere in draft-smack-mpls-rfc4379bis-02.
>
> Does this mean that if/when the draft is published as an RFC, all the  documents  updating RFC 4379 would equally update a new RFC?
>
> And what would happen to all the TLVs, sub-TLVs and procedures that are defined in these documents?
>
> I honestly do not know what is the right way to proceed here, but I think that silence is definitely not the best way to address the problem.
>
> My 2c,
> Sasha
> ________________________________________
> From: I-D-Announce <[e-mail]> on behalf of [e-mail] <[e-mail]>
> Sent: Saturday, September 26, 2015 11:52 PM
> To: [e-mail]
> Subject: I-D Action: draft-smack-mpls-rfc4379bis-02.txt
>
> A New Internet-Draft is available from the on-line Internet-Drafts directories.
>
>
>          Title           : Detecting Multi-Protocol Label Switched (MPLS) Data Plane Failures
>          Authors         : Carlos Pignataro
>                            Nagendra Kumar
>                            Sam Aldrin
>                            Mach(Guoyi) Chen
>          Filename        : draft-smack-mpls-rfc4379bis-02.txt
>          Pages           : 49
>          Date            : 2015-09-26
>
> Abstract:
>     This document describes a simple and efficient mechanism that can be
>     used to detect data plane failures in Multi-Protocol Label Switching
>     (MPLS) Label Switched Paths (LSPs).  There are two parts to this
>     document: information carried in an MPLS "echo request" and "echo
>     reply" for the purposes of fault detection and isolation, and
>     mechanisms for reliably sending the echo reply.
>
>     This document obsoletes RFC 4379.
>
>
> The IETF datatracker status page for this draft is:
> https://datatracker.ietf.org/doc/draft-smack-mpls-rfc4379bis/
>
> There's also a htmlized version available at:
> https://tools.ietf.org/html/draft-smack-mpls-rfc4379bis-02
>
> A diff from the previous version is available at:
> https://www.ietf.org/rfcdiff?url2=draft-smack-mpls-rfc4379bis-02
>
>
> Please note that it may take a couple of minutes from the time of submission
> until the htmlized version and diff are available at tools.ietf.org.
>
> Internet-Drafts are also available by anonymous FTP at:
> ftp://ftp.ietf.org/internet-drafts/
>
> _______________________________________________
> I-D-Announce mailing list
> [e-mail]
> https://www.ietf.org/mailman/listinfo/i-d-announce
> Internet-Draft directories: http://www.ietf.org/shadow.html
> or ftp://ftp.ietf.org/ietf/1shadow-sites.txt
>
> _______________________________________________
> mpls mailing list
> [e-mail]
> https://www.ietf.org/mailman/listinfo/mpls
>