RFC 8690

Clarification of Segment ID Sub-TLV Length for RFC 8287, December 2019

File formats:

icon for HTML icon for text file icon for v3pdf icon for XML
Also available: XML file for editing
 
Status:
PROPOSED STANDARD
Updates:
RFC 8287
Authors:
N. Nainar
C. Pignataro
F. Iqbal
A. Vainshtein
Stream:
IETF
Source:
mpls (rtg)

Cite this RFC: TXT  |  XML  |   BibTeX

DOI:  https://doi.org/10.17487/RFC8690

Discuss this RFC: Send questions or comments to the mailing list mpls@ietf.org

Other actions: Submit Errata  |  Find IPR Disclosures from the IETF  |  View History of RFC 8690


Abstract

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.


For the definition of Status, see RFC 2026.

For the definition of Stream, see RFC 8729.




Advanced Search