RFC8287 Sub-TLV Length Clarification
draft-nainar-mpls-rfc8287-errata-01
Document | Type |
Replaced Internet-Draft
(individual)
Expired & archived
|
|
---|---|---|---|
Authors | Nagendra Kumar Nainar , Carlos Pignataro , faiqbal@cisco.com , Sasha Vainshtein | ||
Last updated | 2018-12-18 | ||
Replaced by | draft-nainar-mpls-rfc8287-len-clarification | ||
RFC stream | (None) | ||
Intended RFC status | (None) | ||
Formats | |||
Stream | Stream state | (No stream defined) | |
Consensus boilerplate | Unknown | ||
RFC Editor Note | (None) | ||
IESG | IESG state | Replaced by draft-nainar-mpls-rfc8287-len-clarification | |
Telechat date | (None) | ||
Responsible AD | (None) | ||
Send notices to | (None) |
This Internet-Draft is no longer active. A copy of the expired Internet-Draft is available in these formats:
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 Nainar
Carlos Pignataro
faiqbal@cisco.com
Sasha Vainshtein
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)