RFC8287 Sub-TLV Length Clarification
draft-nainar-mpls-rfc8287-len-clarification-00
| Document | Type | Replaced Internet-Draft (mpls WG) | |
|---|---|---|---|
| Last updated | 2019-03-10 (latest revision 2019-01-17) | ||
| Replaces | draft-nainar-mpls-rfc8287-errata | ||
| Replaced by | draft-ietf-mpls-rfc8287-len-clarification | ||
| Stream | IETF | ||
| Intended RFC status | (None) | ||
| Formats |
Expired & archived
pdf
htmlized
bibtex
|
||
| Stream | WG state | Adopted by a WG | |
| Document shepherd | Loa Andersson | ||
| IESG | IESG state | Replaced by draft-ietf-mpls-rfc8287-len-clarification | |
| Consensus Boilerplate | Unknown | ||
| Telechat date | |||
| Responsible AD | (None) | ||
| Send notices to | zali@cisco.com, Loa Andersson <loa@pi.nu> | ||
https://www.ietf.org/archive/id/draft-nainar-mpls-rfc8287-len-clarification-00.txt
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.
Authors
Nagendra Kumar
(naikumar@cisco.com)
Carlos Pignataro
(cpignata@cisco.com)
Faisal Iqbal
(faisal.iqbal@msn.com)
Sasha Vainshtein
(vainshtein.alex@gmail.com)
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)