draft-ietf-mpls-rfc8287-len-clarification-01.txt | draft-ietf-mpls-rfc8287-len-clarification-02.txt | |||
---|---|---|---|---|
Network Work group N. Nainar | Network Work group N. Nainar | |||
Internet-Draft C. Pignataro | Internet-Draft C. Pignataro | |||
Updates: 8287 (if approved) Cisco Systems, Inc. | Updates: 8287 (if approved) Cisco Systems, Inc. | |||
Intended status: Standards Track F. Iqbal | Intended status: Standards Track F. Iqbal | |||
Expires: November 26, 2019 Individual | Expires: December 2, 2019 Individual | |||
A. Vainshtein | A. Vainshtein | |||
ECI Telecom | ECI Telecom | |||
May 25, 2019 | May 31, 2019 | |||
RFC8287 Sub-TLV Length Clarification | RFC8287 Sub-TLV Length Clarification | |||
draft-ietf-mpls-rfc8287-len-clarification-01 | draft-ietf-mpls-rfc8287-len-clarification-02 | |||
Abstract | Abstract | |||
RFC8287 defines the extensions to MPLS LSP Ping and Traceroute for | RFC8287 defines the extensions to MPLS LSP Ping and Traceroute for | |||
Segment Routing IGP-Prefix and IGP-Adjacency Segment Identifier | Segment Routing IGP-Prefix and IGP-Adjacency Segment Identifier | |||
(SIDs) with an MPLS data plane. RFC8287 proposes 3 Target FEC Stack | (SIDs) with an MPLS data plane. RFC8287 proposes 3 Target FEC Stack | |||
Sub-TLVs. While the standard defines the format and procedure to | Sub-TLVs. While the standard defines the format and procedure to | |||
handle those Sub-TLVs, it does not sufficiently clarify how the | handle those Sub-TLVs, it does not sufficiently clarify how the | |||
length of the Segment ID Sub-TLVs should be computed to include in | 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 | the Length field of the Sub-TLVs which may result in interoperability | |||
skipping to change at page 1, line 44 ¶ | skipping to change at page 1, line 44 ¶ | |||
Internet-Drafts are working documents of the Internet Engineering | Internet-Drafts are working documents of the Internet Engineering | |||
Task Force (IETF). Note that other groups may also distribute | Task Force (IETF). Note that other groups may also distribute | |||
working documents as Internet-Drafts. The list of current Internet- | working documents as Internet-Drafts. The list of current Internet- | |||
Drafts is at https://datatracker.ietf.org/drafts/current/. | Drafts is at https://datatracker.ietf.org/drafts/current/. | |||
Internet-Drafts are draft documents valid for a maximum of six months | Internet-Drafts are draft documents valid for a maximum of six months | |||
and may be updated, replaced, or obsoleted by other documents at any | and may be updated, replaced, or obsoleted by other documents at any | |||
time. It is inappropriate to use Internet-Drafts as reference | time. It is inappropriate to use Internet-Drafts as reference | |||
material or to cite them other than as "work in progress." | material or to cite them other than as "work in progress." | |||
This Internet-Draft will expire on November 26, 2019. | This Internet-Draft will expire on December 2, 2019. | |||
Copyright Notice | Copyright Notice | |||
Copyright (c) 2019 IETF Trust and the persons identified as the | Copyright (c) 2019 IETF Trust and the persons identified as the | |||
document authors. All rights reserved. | document authors. All rights reserved. | |||
This document is subject to BCP 78 and the IETF Trust's Legal | This document is subject to BCP 78 and the IETF Trust's Legal | |||
Provisions Relating to IETF Documents | Provisions Relating to IETF Documents | |||
(https://trustee.ietf.org/license-info) in effect on the date of | (https://trustee.ietf.org/license-info) in effect on the date of | |||
publication of this document. Please review these documents | publication of this document. Please review these documents | |||
skipping to change at page 4, line 26 ¶ | skipping to change at page 4, line 26 ¶ | |||
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | |||
4.3. IGP-Adjacency Segment ID Sub-TLV | 4.3. IGP-Adjacency Segment ID Sub-TLV | |||
The Sub-TLV length for IGP-Adjacency Segment ID varies depending on | The Sub-TLV length for IGP-Adjacency Segment ID varies depending on | |||
the Adjacency Type and Protocol. In any of the allowed combination | the Adjacency Type and Protocol. In any of the allowed combination | |||
of Adjacency Type and Protocol, the sub-TLV length MUST be calculated | of Adjacency Type and Protocol, the sub-TLV length MUST be calculated | |||
by including 2 octets of Reserved field. Below is a table that list | by including 2 octets of Reserved field. Below is a table that list | |||
the length for different combinations. | the length for different combinations. | |||
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | |||
| Protocol | Length for Adj.Type | | | Protocol | Length for Adj.Type | | |||
+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | + +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | |||
| | Parallel | IPv4 | IPv6 | | | | Parallel | IPv4 | IPv6 | | |||
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | |||
| OSPF | 20 | 20 | 44 | | | OSPF | 20 | 20 | 44 | | |||
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | |||
| ISIS | 24 | 24 | 48 | | | ISIS | 24 | 24 | 48 | | |||
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | |||
| Any | 20 | 20 | 44 | | | Any | 20 | 20 | 44 | | |||
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | |||
For example, when the Adj. Type is set to Parallel Adjacency and the | For example, when the Adj. Type is set to Parallel Adjacency and the | |||
Protocol is set to 0, the Sub-TLV will be as below: | Protocol is set to 0, the Sub-TLV will be as below: | |||
0 1 2 3 | 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 | 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 | |||
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | |||
|Type = 36 (IGP-Adjacency SID) | Length = 20 | | |Type = 36 (IGP-Adjacency SID) | Length = 20 | | |||
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | |||
| Adj. Type = 1 | Protocol =0 | Reserved | | | Adj. Type = 1 | Protocol =0 | Reserved | | |||
End of changes. 5 change blocks. | ||||
15 lines changed or deleted | 15 lines changed or added | |||
This html diff was produced by rfcdiff 1.47. The latest version is available from http://tools.ietf.org/tools/rfcdiff/ |