CurrentPROPOSED STANDARDIETF stream

RFC 8690: Clarification of Segment ID Sub-TLV Length for RFC 8287

In plain English — editorial summary, not part of the RFC

RFC 8287 defines the extensions to perform LSP Ping and Traceroute for Segment Routing IGP-Prefix and IGP-Adjacency Segment Identifiers (SIDs) with the MPLS data plane. RFC 8287 proposes three Target Forwarding Equivalence Class (FEC) Stack sub-TLVs. While RFC 8287 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 be included in the Length field of the sub-TLVs. This ambiguity has resulted in interoperability issues. This document updates RFC 8287 by clarifying the length of each of the Segment ID sub-TLVs defined in RFC 8287.

Document record

Document ID
RFC8690
Published
December 2019
Authors
N. Nainar; C. Pignataro; F. Iqbal; A. Vainshtein
Status
PROPOSED STANDARD
Stream
IETF
Area
rtg
Pages
7
Also known as
Updates:
RFC 8287

Topics

Related documents

Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.

Also filed under

About this page

The document record above — title, authors, date, status, stream, area, relationships, DOI and errata — is imported verbatim from the public RFC Editor index. The “in plain English” section is editorial: written by The metasystema editorial team, not part of the RFC. Where the two differ, the RFC text governs.

Last checked against the RFC Editor index on . RFCs are never revised after publication; changes are issued as new documents.

Data sources · Editorial policy · Report a correction · What is an RFC?

canonical URL: /rfc/8690-clarification-of-segment-id-sub-tlv-length-for-rfc-8287