Subject: [mpls] FW: New Version Notification for draft-nainar-mpls-rfc8287-errata-01.txt

From: "Nagendra Kumar Nainar (naikumar)" <[email-masked]>
Date: Wed, 19 Dec 2018 01:03:10 +0000

Hi,

This is a simple draft that clarifies the Length fields in new Target FEC Stack Sub-TLVs proposed as part of RFC8287. We, the authors would like to request the chair to consider for WG adoption.

Thanks,
Nagendra

On 12/18/18, 8:00 PM, "[email-masked]" <[email-masked]> wrote:

    A new version of I-D, draft-nainar-mpls-rfc8287-errata-01.txt
    has been successfully submitted by Nagendra Kumar Nainar and posted to the
    IETF repository.
    
    Name:		draft-nainar-mpls-rfc8287-errata
    Revision:	01
    Title:		RFC8287 Sub-TLV Length Clarification
    Document date:	2018-12-18
    Group:		Individual Submission
    Pages:		6
    URL:            https://www.ietf.org/internet-drafts/draft-nainar-mpls-rfc8287-errata-01.txt
    Status:         https://datatracker.ietf.org/doc/draft-nainar-mpls-rfc8287-errata/
    Htmlized:       https://tools.ietf.org/html/draft-nainar-mpls-rfc8287-errata-01
    Htmlized:       https://datatracker.ietf.org/doc/html/draft-nainar-mpls-rfc8287-errata
    Diff:           https://www.ietf.org/rfcdiff?url2=draft-nainar-mpls-rfc8287-errata-01
    
    Abstract:
       RFC8287 defines the extensions to MPLS LSP Ping and Traceroute for
       Segment Routing IGP-Prefix and IGP-Adjacency Segment Identifier
       (SIDs) with an MPLS data plane.  RFC8287 proposes 3 Target FEC Stack
       Sub-TLVs.  While the standard defines the format and procedure to
       handle those Sub-TLVs, it does not sufficiently clarify how the
       length of the Segment ID Sub-TLVs should be computed to include in
       the Length field of the Sub-TLVs which may result in interoperability
       issues.
    
       This document updates RFC8287 by clarifying the length of each
       Segment ID Sub-TLVs defined in RFC8287.

    
    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.
    
    The IETF Secretariat