< draft-chen-idr-bgp-srv6-sid-allocation-00.txt   draft-chen-idr-bgp-srv6-sid-allocation-01.txt >
IDR Working Group H. Chen IDR Working Group H. Chen
Internet-Draft Z. Li Internet-Draft Futurewei
Intended status: Standards Track S. Zhuang Intended status: Standards Track Z. Li
Expires: September 9, 2019 Huawei Expires: January 8, 2020 S. Zhuang
March 8, 2019 Huawei
July 7, 2019
BGP Extensions for SRv6 SIDs Allocation BGP Extensions for SRv6 SIDs Allocation
draft-chen-idr-bgp-srv6-sid-allocation-00 draft-chen-idr-bgp-srv6-sid-allocation-01
Abstract Abstract
This document describes extensions to the BGP-LS for IDs allocation. This document describes extensions to the BGP for IDs allocation.
The IDs are SIDs for segment routing for IPv6 (SRv6). They are The IDs are SIDs for segment routing (SR), including SR for IPv6
distributed to their domains if needed. (SRv6). They are distributed to their domains if needed.
Requirements Language Requirements Language
The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
"SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this
document are to be interpreted as described in RFC 2119 [RFC2119]. document are to be interpreted as described in RFC 2119 [RFC2119].
Status of This Memo Status of This Memo
This Internet-Draft is submitted in full conformance with the This Internet-Draft is submitted in full conformance with the
skipping to change at page 1, line 39 skipping to change at page 1, line 40
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 September 9, 2019. This Internet-Draft will expire on January 8, 2020.
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
carefully, as they describe your rights and restrictions with respect carefully, as they describe your rights and restrictions with respect
to this document. Code Components extracted from this document must to this document. Code Components extracted from this document must
include Simplified BSD License text as described in Section 4.e of include Simplified BSD License text as described in Section 4.e of
the Trust Legal Provisions and are provided without warranty as the Trust Legal Provisions and are provided without warranty as
described in the Simplified BSD License. described in the Simplified BSD License.
Table of Contents Table of Contents
1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 2 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 2
2. Terminology . . . . . . . . . . . . . . . . . . . . . . . . . 2 2. Terminology . . . . . . . . . . . . . . . . . . . . . . . . . 3
3. Protocol Extensions . . . . . . . . . . . . . . . . . . . . . 3 3. Protocol Extensions . . . . . . . . . . . . . . . . . . . . . 3
3.1. Node NLRI for IDs Allocation . . . . . . . . . . . . . . 3 3.1. Node SID NLRI TLV . . . . . . . . . . . . . . . . . . . . 4
3.2. Link NLRI for IDs Allocation . . . . . . . . . . . . . . 6 3.2. Link SID NLRI TLV . . . . . . . . . . . . . . . . . . . . 6
4. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 9 3.3. Prefix SID NLRI TLV . . . . . . . . . . . . . . . . . . . 10
5. Security Considerations . . . . . . . . . . . . . . . . . . . 9 4. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 11
6. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . 9 5. Security Considerations . . . . . . . . . . . . . . . . . . . 11
7. References . . . . . . . . . . . . . . . . . . . . . . . . . 9 6. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . 12
7.1. Normative References . . . . . . . . . . . . . . . . . . 9 7. References . . . . . . . . . . . . . . . . . . . . . . . . . 12
7.2. Informative References . . . . . . . . . . . . . . . . . 11 7.1. Normative References . . . . . . . . . . . . . . . . . . 12
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 11 7.2. Informative References . . . . . . . . . . . . . . . . . 13
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 14
1. Introduction 1. Introduction
In a network with a central controller, the controller has the link In a network with a central controller, the controller has the link
state information of the network, including traffic engineering state information of the network, including traffic engineering
information. In addition, the controller allocates and manages the information. In addition, the controller allocates and manages the
resources of the network in general. It is natural and beneficial resources of the network in general. It is natural and beneficial
for the controller to allocate and manage IDs as a kind of network for the controller to allocate and manage IDs as a kind of network
resources. resources.
This document proposes extensions to the BGP-LS as a controller for When BGP as a controller allocates an ID, it is natural and
allocating Segment Identifiers (SIDs) for segment routing for IPv6 beneficial to extend BGP to send it to its corresponding network
(SRv6). If needed, some SIDs will be distributed into their network elements.
PCE may be extended to send IDs to their corresponding network
elements after the IDs are allocated by a controller. However, when
BGP is already deployed in a network, using PCE for IDs will need to
deploy an extra protocol PCE in the network. This will increase the
CapEx and OpEx.
Yang may be extended to send IDs to their corresponding network
elements after the IDs are allocated by a controller. However, Yang
progress may be slow. Some people may not like this.
There may not be these issues when BGP is used to send IDs. In
addition, BGP may be used to distribute IDs into their domains easily
when needed. It is also fit for the dynamic and static allocation of
IDs.
This document proposes extensions to the BGP for sending Segment
Identifiers (SIDs) for segment routing (SR) including SRv6 to their
corresponding network elements after SIDs are allocated by the
controller. If needed, they will be distributed into their network
domains. domains.
2. Terminology 2. Terminology
The following terminology is used in this document. The following terminology is used in this document.
SR: Segment Routing. SR: Segment Routing.
SRv6: SR for IPv6 SRv6: SR for IPv6
skipping to change at page 3, line 13 skipping to change at page 3, line 35
SR-Path: Segment Routing Path. SR-Path: Segment Routing Path.
SR-Tunnel: Segment Routing Tunnel. SR-Tunnel: Segment Routing Tunnel.
RR: Route Reflector. RR: Route Reflector.
MPP: MPLS Path Programming. MPP: MPLS Path Programming.
NAI: Node or Adjacency Identifier. NAI: Node or Adjacency Identifier.
GTID: Global Tunnel Identifier. It is used to identify a tunnel in
a network.
TED: Traffic Engineering Database. TED: Traffic Engineering Database.
3. Protocol Extensions 3. Protocol Extensions
This section defines a new Protocol-ID, called IDs-Allocation (IDA), A new SAFI is defined: the SID SAFI whose codepoint TBD is to be
in the Protocol-ID field of Link State NLRI. The use of the new assigned by IANA. A few new NLRI TLVs are defined for the new SAFI,
Protocol-ID allows separation and differentiation between the NLRIs which are Node, Link and Prefix SID NLRI TLV. When a SID for a node,
carrying IDs Allocation information from the NLRIs carrying IGP link- link or prefix is allocated by the controller, it may be sent to a
state information defined in [RFC7752]. network element in a UPDATE message containing a MP_REACH NLRI with
the new SAFI and the SID NLRI TLV. When the SID is withdrawn by the
controller, a UPDATE message containing a MP_UNREACH NLRI with the
new SAFI and the SID NLRI TLV may be sent to the network element.
3.1. Node NLRI for IDs Allocation 3.1. Node SID NLRI TLV
The Node NLRI with the new Protocol-ID is used for allocating the IDs The Node SID NLRI TLV is used for allocating the IDs such as SID
associated with a node. It has the same format (refer to the associated with a node. Its format is illustrated in the
Figure below) as that defined in [RFC7752] and may contain the Figure below, which is similar to the corresponding one defined in
descriptor and attributes defined in [RFC7752]. [RFC7752].
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
+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
|IDs-Allocation | Protocol-ID | Type (TBDa for Node SID) | Length |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Protocol ID |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Identifier | | Identifier |
| (64 bits) | | (8 octets) |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
~ Local Node Descriptor ~ | Peer IP (4/16 bytes for IPv4/IPv6 Address) ~
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
~ Node IDs Allocation ~ ~ Local Node Descriptors TLV ~
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
~ Sub-TLVs ~
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
Where: Where:
Protocol-ID: set to IDs-Allocation, a new Protocol-ID. Type (TBDa): It is to be assigned by IANA.
Local Node Descriptor: defined in [RFC7752], can be reused. Length: It is the length of the value field in bytes.
Node IDs Allocation: TLVs or sub-TLVs for IDs associated with the Peer IP: 4/16 octet value indicates an IPv4/IPv6 peer. When
node given by the Local Node Descriptor. receiving a UPDATE message, a BGP speaker processes it only if the
peer IP is the IP address of the BGP speaker or 0.
Node IDs Allocation field may contain some of the followings: Protocol-ID, Identifier, and Local Node Descriptor: defined in
[RFC7752], can be reused.
Sub-TLVs may be some of the followings:
SR-Capabilities TLV (1034): It contains the Segment Routing Global SR-Capabilities TLV (1034): It contains the Segment Routing Global
Base (SRGB) range(s) allocated for the node. Base (SRGB) range(s) allocated for the node.
SR Local Block TLV (1036): The SR Local Block (SRLB) TLV contains SR Local Block TLV (1036): The SR Local Block (SRLB) TLV contains
the range(s) of SIDs/labels allocated to the node for local SIDs. the range(s) of SIDs/labels allocated to the node for local SIDs.
SRv6 SID Node TLV (TBD1): A new TLV, called SRv6 Node SID TLV, SRv6 SID Node TLV (TBD1): A new TLV, called SRv6 Node SID TLV,
contains an SRv6 SID and related information. contains an SRv6 SID and related information.
skipping to change at page 6, line 5 skipping to change at page 6, line 44
Metric: 4 octets. As described in [RFC5305]. Metric: 4 octets. As described in [RFC5305].
Locator-Size: 1 octet. Number of bits in the Locator field (1 to Locator-Size: 1 octet. Number of bits in the Locator field (1 to
128). 128).
Locator: 1 to 16 octets. SRv6 Locator encoded in the minimum number Locator: 1 to 16 octets. SRv6 Locator encoded in the minimum number
of octets for the given Locator-Size. of octets for the given Locator-Size.
Reserved: MUST be set to 0 while sending and ignored on receipt. Reserved: MUST be set to 0 while sending and ignored on receipt.
3.2. Link NLRI for IDs Allocation 3.2. Link SID NLRI TLV
The Link NLRI with the new Protocol-ID is used for allocating the IDs The Link SID NLRI TLV is used for allocating the IDs such as SID
associated with a link. It has the same format (refer to the associated with a link. Its format is illustrated in the
Figure below) as that defined in in [RFC7752] and may contain the Figure below, which is similar to the corresponding one defined in
descriptors and attributes defined in [RFC7752]. [RFC7752].
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
+-+-+-+-+-+-+-+-+
|IDs-Allocation | Protocol-ID
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Identifier | | Type (TBDb for Link SID) | Length |
| (64 bits) |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
~ Local Node Descriptor ~ | Protocol ID |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
~ Remote Node Descriptor ~ ~ Identifier (8 octets) ~
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
~ Link Descriptor ~ | Peer IP (4/16 bytes for IPv4/IPv6 Address) ~
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
~ Link IDs Allocation ~ ~ Local Node Descriptors TLV ~
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
~ Remote Node Descriptors TLV ~
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
~ Link Descriptors TLV ~
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
~ Sub-TLVs ~
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
Where: Where:
Protocol-ID: set to IDs-Allocation, a new Protocol-ID. Type (TBDa): It is to be assigned by IANA.
Node Descriptors: defined in [RFC7752], can be reused. Length: It is the length of the value field in bytes.
Link Descriptor: defined in [RFC7752], can be reused. Peer IP: 4/16 octet value indicates an IPv4/IPv6 peer.
Link IDs Allocation: TLVs or sub-TLVs for IDs associated with the Protocol-ID, Identifier, Local Node Descriptors, Remote Node
link given by the Link Descriptor. Descriptors and Link Descriptors:
defined in [RFC7752], can be reused.
Link IDs Allocation field may contain some of the followings: The Sub-TLVs may be some of the followings:
Adj-SID TLV (1099): It contains the Segment Identifier (SID) Adj-SID TLV (1099): It contains the Segment Identifier (SID)
allocated for the link/adjacency. allocated for the link/adjacency.
LAN Adj-SID TLV (1100): It contains the Segment Identifier (SID) LAN Adj-SID TLV (1100): It contains the Segment Identifier (SID)
allocated for the adjacency/link to a non-DR router on a allocated for the adjacency/link to a non-DR router on a
broadcast, NBMA, or hybrid link. broadcast, NBMA, or hybrid link.
SRv6 Adj-SID TLV (TBD2): A new TLV, called SRv6 Adj-SID TLV, SRv6 Adj-SID TLV (TBD3): A new TLV, called SRv6 Adj-SID TLV,
contains an SRv6 Adj-SID and related information. contains an SRv6 Adj-SID and related information.
SRv6 LAN Adj-SID TLV (TBD3): A new TLV, called SRv6 LAN Adj-SID SRv6 LAN Adj-SID TLV (TBD4): A new TLV, called SRv6 LAN Adj-SID
TLV, contains an SRv6 LAN Adj-SID and related information. TLV, contains an SRv6 LAN Adj-SID and related information.
The format of an SRv6 Adj-SID TLV is illustrated below. The format of an SRv6 Adj-SID TLV is illustrated 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 (TBD3) | Length | | Type (TBD3) | Length |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Weight | Algorithm |B|S|P| Flags | | Weight | Algorithm |B|S|P| Flags |
skipping to change at page 9, line 5 skipping to change at page 10, line 5
OSPF neighbor Router ID of 4 octets, set to 0 indicating IS-IS OSPF neighbor Router ID of 4 octets, set to 0 indicating IS-IS
neighbor System ID of 6 octets. neighbor System ID of 6 octets.
SRv6 Endpoint Function: 2 octets. The function associated with SRv6 SRv6 Endpoint Function: 2 octets. The function associated with SRv6
SID. SID.
SRv6 Identifier: 16 octets. IPv6 address representing SRv6 SID. SRv6 Identifier: 16 octets. IPv6 address representing SRv6 SID.
Reserved: MUST be set to 0 while sending and ignored on receipt. Reserved: MUST be set to 0 while sending and ignored on receipt.
3.3. Prefix SID NLRI TLV
The Prefix SID NLRI TLV is used for allocating the IDs such as SID
associated with a prefix. Its format is illustrated in the
Figure below, which is similar to the corresponding one defined in
[RFC7752].
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
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Type (TBDc for Prefix SID) | Length |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Protocol ID |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
~ Identifier (8 octets) ~
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Peer IP (4/16 bytes for IPv4/IPv6 Address) ~
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
~ Local Node Descriptors TLV ~
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
~ Prefix Descriptors TLV ~
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
~ Sub-TLVs ~
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
Where:
Type (TBDc): It is to be assigned by IANA.
Length: It is the length of the value field in bytes.
Peer IP: 4/16 octet value indicates an IPv4/IPv6 peer.
Protocol-ID, Identifier, Local Node Descriptors and Prefix
Descriptors:
defined in [RFC7752], can be reused.
Prefix IDs Allocation field may contain some of the followings:
Prefix-SID TLV (1158): It contains the Segment Identifier (SID)
allocated for the prefix.
Prefix Range TLV (1159): It contains a range of prefixes and the
Segment Identifier (SID)s allocated for the prefixes.
4. IANA Considerations 4. IANA Considerations
This document requests assigning a code-point from the registry "BGP- This document requests assigning a new SAFI in the registry
LS Protocol-IDs" as follows: "Subsequent Address Family Identifiers (SAFI) Parameters" as follows:
+-------------+-----------------------------------+-------------+ +-------------+-----------------------------------+-------------+
| Protocol-ID | Description | Reference | | Code Point | Description | Reference |
+-------------+-----------------------------------+-------------+ +-------------+-----------------------------------+-------------+
| TBD | IDs Allocation | Section 3 | | TBD | SID SAFI |This document|
+-------------+-----------------------------------+-------------+
This document defines a new registry called "SID NLRI TLVs". The
allocation policy of this registry is "First Come First Served
(FCFS)" according to [RFC8126].
Following TLV code points are defined:
+-------------+-----------------------------------+-------------+
| Code Point | Description | Reference |
+-------------+-----------------------------------+-------------+
| 1 (TBDa) | Node SID NLRI |This document|
+-------------+-----------------------------------+-------------+
| 2 (TBDb) | Link SID NLRI |This document|
+-------------+-----------------------------------+-------------+
| 3 (TBDc) | Prefix SID NLRI |This document|
+-------------+-----------------------------------+-------------+ +-------------+-----------------------------------+-------------+
This document requests assigning a code-point from the registry "BGP- This document requests assigning a code-point from the registry "BGP-
LS Node Descriptor, Link Descriptor, Prefix Descriptor, and Attribute LS Node Descriptor, Link Descriptor, Prefix Descriptor, and Attribute
TLVs" as follows: TLVs" as follows:
+----------------+-----------------------------------+-------------+ +----------------+-----------------------------------+-------------+
| TLV Code Point | Description | Reference | | TLV Code Point | Description | Reference |
+----------------+-----------------------------------+-------------+ +----------------+-----------------------------------+-------------+
| TBD1 | SRv6 Node SID | Section 3 | | TBD1 | SRv6 Node SID |This document|
+----------------+-----------------------------------+-------------+ +----------------+-----------------------------------+-------------+
| TBD2 | SRv6 Adj-SID | Section 3 | | TBD2 | SRv6 Allocator |This document|
+----------------+-----------------------------------+-------------+ +----------------+-----------------------------------+-------------+
| TBD3 | SRv6 LAN Adj-SID | Section 3 | | TBD3 | SRv6 Adj-SID |This document|
+----------------+-----------------------------------+-------------+
| TBD4 | SRv6 LAN Adj-SID |This document|
+----------------+-----------------------------------+-------------+ +----------------+-----------------------------------+-------------+
5. Security Considerations 5. Security Considerations
Protocol extensions defined in this document do not affect the BGP Protocol extensions defined in this document do not affect the BGP
security other than those as discussed in the Security Considerations security other than those as discussed in the Security Considerations
section of [RFC7752]. section of [RFC7752].
6. Acknowledgements 6. Acknowledgements
The authors would like to thank Nan Wu, and others for their valuable The authors would like to thank Eric Wu, Robert Razuk, Zhengquiang
suggestions and comments on this draft. Li, and Ketan Talaulikar for their valuable suggestions and comments
on this draft.
7. References 7. References
7.1. Normative References 7.1. Normative References
[I-D.bashandy-isis-srv6-extensions] [I-D.bashandy-isis-srv6-extensions]
Psenak, P., Filsfils, C., Bashandy, A., Decraene, B., and Psenak, P., Filsfils, C., Bashandy, A., Decraene, B., and
Z. Hu, "IS-IS Extensions to Support Routing over IPv6 Z. Hu, "IS-IS Extensions to Support Routing over IPv6
Dataplane", draft-bashandy-isis-srv6-extensions-05 (work Dataplane", draft-bashandy-isis-srv6-extensions-05 (work
in progress), March 2019. in progress), March 2019.
[I-D.ietf-idr-flowspec-path-redirect] [I-D.ietf-idr-flowspec-path-redirect]
Velde, G., Patel, K., and Z. Li, "Flowspec Indirection-id Velde, G., Patel, K., and Z. Li, "Flowspec Indirection-id
Redirect", draft-ietf-idr-flowspec-path-redirect-07 (work Redirect", draft-ietf-idr-flowspec-path-redirect-08 (work
in progress), December 2018. in progress), June 2019.
[I-D.ietf-isis-segment-routing-extensions] [I-D.ietf-isis-segment-routing-extensions]
Previdi, S., Ginsberg, L., Filsfils, C., Bashandy, A., Previdi, S., Ginsberg, L., Filsfils, C., Bashandy, A.,
Gredler, H., and B. Decraene, "IS-IS Extensions for Gredler, H., and B. Decraene, "IS-IS Extensions for
Segment Routing", draft-ietf-isis-segment-routing- Segment Routing", draft-ietf-isis-segment-routing-
extensions-22 (work in progress), December 2018. extensions-25 (work in progress), May 2019.
[I-D.ietf-rtgwg-bgp-routing-large-dc] [I-D.ietf-rtgwg-bgp-routing-large-dc]
Lapukhov, P., Premji, A., and J. Mitchell, "Use of BGP for Lapukhov, P., Premji, A., and J. Mitchell, "Use of BGP for
routing in large-scale data centers", draft-ietf-rtgwg- routing in large-scale data centers", draft-ietf-rtgwg-
bgp-routing-large-dc-11 (work in progress), June 2016. bgp-routing-large-dc-11 (work in progress), June 2016.
[I-D.ietf-spring-segment-routing] [I-D.ietf-spring-segment-routing]
Filsfils, C., Previdi, S., Ginsberg, L., Decraene, B., Filsfils, C., Previdi, S., Ginsberg, L., Decraene, B.,
Litkowski, S., and R. Shakir, "Segment Routing Litkowski, S., and R. Shakir, "Segment Routing
Architecture", draft-ietf-spring-segment-routing-15 (work Architecture", draft-ietf-spring-segment-routing-15 (work
skipping to change at page 11, line 16 skipping to change at page 13, line 31
and D. McPherson, "Dissemination of Flow Specification and D. McPherson, "Dissemination of Flow Specification
Rules", RFC 5575, DOI 10.17487/RFC5575, August 2009, Rules", RFC 5575, DOI 10.17487/RFC5575, August 2009,
<https://www.rfc-editor.org/info/rfc5575>. <https://www.rfc-editor.org/info/rfc5575>.
[RFC7752] Gredler, H., Ed., Medved, J., Previdi, S., Farrel, A., and [RFC7752] Gredler, H., Ed., Medved, J., Previdi, S., Farrel, A., and
S. Ray, "North-Bound Distribution of Link-State and S. Ray, "North-Bound Distribution of Link-State and
Traffic Engineering (TE) Information Using BGP", RFC 7752, Traffic Engineering (TE) Information Using BGP", RFC 7752,
DOI 10.17487/RFC7752, March 2016, DOI 10.17487/RFC7752, March 2016,
<https://www.rfc-editor.org/info/rfc7752>. <https://www.rfc-editor.org/info/rfc7752>.
[RFC8126] Cotton, M., Leiba, B., and T. Narten, "Guidelines for
Writing an IANA Considerations Section in RFCs", BCP 26,
RFC 8126, DOI 10.17487/RFC8126, June 2017,
<https://www.rfc-editor.org/info/rfc8126>.
7.2. Informative References 7.2. Informative References
[I-D.gredler-idr-bgp-ls-segment-routing-extension] [I-D.gredler-idr-bgp-ls-segment-routing-extension]
Gredler, H., Ray, S., Previdi, S., Filsfils, C., Chen, M., Gredler, H., Ray, S., Previdi, S., Filsfils, C., Chen, M.,
and J. Tantsura, "BGP Link-State extensions for Segment and J. Tantsura, "BGP Link-State extensions for Segment
Routing", draft-gredler-idr-bgp-ls-segment-routing- Routing", draft-gredler-idr-bgp-ls-segment-routing-
extension-02 (work in progress), October 2014. extension-02 (work in progress), October 2014.
[I-D.ietf-idr-bgpls-segment-routing-epe] [I-D.ietf-idr-bgpls-segment-routing-epe]
Previdi, S., Talaulikar, K., Filsfils, C., Patel, K., Ray, Previdi, S., Talaulikar, K., Filsfils, C., Patel, K., Ray,
S., and J. Dong, "BGP-LS extensions for Segment Routing S., and J. Dong, "BGP-LS extensions for Segment Routing
BGP Egress Peer Engineering", draft-ietf-idr-bgpls- BGP Egress Peer Engineering", draft-ietf-idr-bgpls-
segment-routing-epe-17 (work in progress), October 2018. segment-routing-epe-19 (work in progress), May 2019.
Authors' Addresses Authors' Addresses
Huaimo Chen Huaimo Chen
Huawei Futurewei
Boston, MA Boston, MA
USA USA
Email: Huaimo.chen@huawei.com Email: Huaimo.chen@futurewei.com
Zhenbin Li Zhenbin Li
Huawei Huawei
Huawei Bld., No.156 Beiqing Rd. Huawei Bld., No.156 Beiqing Rd.
Beijing 100095 Beijing 100095
China China
Email: lizhenbin@huawei.com Email: lizhenbin@huawei.com
Shunwan Zhuang Shunwan Zhuang
Huawei Huawei
Huawei Bld., No.156 Beiqing Rd. Huawei Bld., No.156 Beiqing Rd.
Beijing 100095 Beijing 100095
China China
Email: zhuangshunwan@huawei.com Email: zhuangshunwan@huawei.com
 End of changes. 49 change blocks. 
81 lines changed or deleted 185 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/