[mpls] [Errata Rejected] RFC8287 (5290)

RFC Errata System <rfc-editor@rfc-editor.org> Fri, 29 June 2018 14:21 UTC

To: alexander.vainshtein@ecitele.com, naikumar@cisco.com, cpignata@cisco.com, swallow.ietf@gmail.com, nobo.akiya.dev@gmail.com, sriganeshkini@gmail.com, mach.chen@huawei.com
From: RFC Errata System <rfc-editor@rfc-editor.org>
Cc: db3546@att.com, iesg@ietf.org, mpls@ietf.org, rfc-editor@rfc-editor.org
Content-Type: text/plain; charset="UTF-8"
Message-Id: <20180629142146.0AAE8B8116C@rfc-editor.org>
Date: Fri, 29 Jun 2018 07:21:46 -0700
Archived-At: <https://mailarchive.ietf.org/arch/msg/mpls/Luw9wOTecUxdj6P1R_urmLOUAwY>
Subject: [mpls] [Errata Rejected] RFC8287 (5290)
Precedence: list

The following errata report has been rejected for RFC8287,
"Label Switched Path (LSP) Ping/Traceroute for Segment Routing (SR) IGP-Prefix and IGP-Adjacency Segment Identifiers (SIDs) with MPLS Data Planes".

--------------------------------------
You may review the report below and at:
http://www.rfc-editor.org/errata/eid5290

--------------------------------------
Status: Rejected
Type: Technical

Reported by: Alexander ("Sasha") Vainshtein <alexander.vainshtein@ecitele.com>
Date Reported: 2018-03-20
Rejected by: Deborah Brungard (IESG)

Section: 5.1

Original Text
-------------
   The IPv4 IGP-Prefix Segment ID is defined in [SR].  The format is as
   specified below:

      0                   1                   2                   3
      0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
     +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
     |                         IPv4 Prefix                           |
     +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
     |Prefix Length  |    Protocol   |         Reserved              |
     +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+

   IPv4 Prefix

      This field carries the IPv4 Prefix to which the Segment ID is
      assigned.  In case of an Anycast Segment ID, this field will carry
      the IPv4 Anycast address.  If the prefix is shorter than 32 bits,
      trailing bits SHOULD be set to zero.

   Prefix Length

      The Prefix Length field is one octet.  It gives the length of the
      prefix in bits (values can be 1-32).

Corrected Text
--------------
   The IPv4 IGP-Prefix Segment ID is defined in [SR]. 
   The sub-TLV length MUST be set to 8, and its format is 
   as specified below:

      0                   1                   2                   3
      0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
     +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
     |                         IPv4 Prefix                           |
     +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
     |Prefix Length  |    Protocol   |         Reserved              |
     +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+

   IPv4 Prefix

      This field carries the IPv4 Prefix to which the Segment ID is
      assigned.  In case of an Anycast Segment ID, this field will carry
      the IPv4 Anycast address.  If the prefix is shorter than 32 bits,
      trailing bits SHOULD be set to zero.

   Prefix Length

      The Prefix Length field is one octet.  
      It gives the length of the
      prefix in bits (values can be 1-32).

Notes
-----
The RFC in its current form does not explicitly specify the length of the sub-TLV for the IPv4 IGP-Prefix Segment ID, while the format includes a reserved (MBZ) field at the end. 
the implementers therefore must guess whether the reserved bits are or are not included in the sub-TLV guess. Such guesses have already caused interoperabilty issues with some implementations including these bits and some not including them.

For comparison, RFC 8029 explicitly specifies length of every sub-TLV it defines. It also never includes MBZ fields at the end of sub-TLVs in the sub-TLV length.

The proposed text is aligned with majority of implementations known to me.

Note also that sub-TLV length is also omitted in section 6.1. However, I am not aware of any actual interoperability issues with this sub-TLV.
 --VERIFIER NOTES-- 
   This change requires an update to the RFC, requires consensus.

--------------------------------------
RFC8287 (draft-ietf-mpls-spring-lsp-ping-13)
--------------------------------------
Title               : Label Switched Path (LSP) Ping/Traceroute for Segment Routing (SR) IGP-Prefix and IGP-Adjacency Segment Identifiers (SIDs) with MPLS Data Planes
Publication Date    : December 2017
Author(s)           : N. Kumar, Ed., C. Pignataro, Ed., G. Swallow, N. Akiya, S. Kini, M. Chen
Category            : PROPOSED STANDARD
Source              : Multiprotocol Label Switching
Area                : Routing
Stream              : IETF
Verifying Party     : IESG

[mpls] [Errata Rejected] RFC8287 (5290) RFC Errata System