| Internet-Draft | BGP SPF for NRP | March 2022 |
| Dong, et al. | Expires 5 September 2022 | [Page] |
A VTN is a virtual underlay network which has customized network topology and a set of dedicated or shared network resources. Network Resource Partition (NRP) refers to a set of network resources that are available to carry traffic and meet the SLOs and SLEs. Multiple NRPs can be created in a network to provide different Virtual Transport Networks (VTN) to meet the requirements of different services or different service groups.¶
As the number of NRP increases, there can be scalability concerns about using Interial Gateway Protocols (IGP) to distribute the NRP information in the network. In networks where BGP Shortest Path First (SPF) can used as the underlay routing mechanism to distribute the link-state information among network nodes, the information of NRPs needs to be distributed along with the basic network information. This document specifies the BGP SPF mechanisms with necessary extensions to distribute the NRP information and perform NRP-specific path computation.¶
This Internet-Draft is submitted in full conformance with the provisions of BCP 78 and BCP 79.¶
Internet-Drafts are working documents of the Internet Engineering Task Force (IETF). Note that other groups may also distribute working documents as Internet-Drafts. The list of current Internet-Drafts is at https://datatracker.ietf.org/drafts/current/.¶
Internet-Drafts are draft documents valid for a maximum of six months and may be updated, replaced, or obsoleted by other documents at any time. It is inappropriate to use Internet-Drafts as reference material or to cite them other than as "work in progress."¶
This Internet-Draft will expire on 5 September 2022.¶
Copyright (c) 2022 IETF Trust and the persons identified as the document authors. All rights reserved.¶
This document is subject to BCP 78 and the IETF Trust's Legal Provisions Relating to IETF Documents (https://trustee.ietf.org/license-info) in effect on the date of publication of this document. Please review these documents carefully, as they describe your rights and restrictions with respect to this document. Code Components extracted from this document must include Revised BSD License text as described in Section 4.e of the Trust Legal Provisions and are provided without warranty as described in the Revised BSD License.¶
The concept of Virtual Transport Network (VTN) is introduced in [I-D.ietf-teas-enhanced-vpn]. A VTN is a virtual underlay network which has customized network topology and a set of dedicated or shared network resources. In a network, different VTNs may be created to meet different service requirements, and services can be mapped to the same or different VTNs.¶
[I-D.ietf-teas-ietf-network-slices] introduces the concept Network Resource Partition (NRP) as a set of network resources that are available to carry traffic and meet the SLOs and SLEs. In the context of network slicing, an NRP can be used to instantiate a VTN for one or a group of IETF network slice services.¶
[I-D.ietf-spring-sr-for-enhanced-vpn] describes the use of resource-aware segments [I-D.ietf-spring-resource-aware-segments] to build SR based NRPs. The SIDs of each NRP and the associated topology and resource attributes need to be distributed using the control plane. [I-D.dong-lsr-sr-enhanced-vpn] specifies the IGP mechanism and extensions to build a relatively large number of SR based NRPs. [I-D.dong-idr-bgpls-sr-enhanced-vpn] further specifies the BGP-LS mechanisms and extensions to advertise the NRP information within each domain and the NRP information on the inter-domain links to the network controller, so that the controller could use the collected information to obtain the view of the inter-domain SR NRPs .¶
As the number of NRP increases, there can be scalability concerns about using IGP to distribute the NRP information in the network. In networks where BGP SPF is used to distribute the link-state information among network nodes, the NRP information needs to be distributed along with the basic network link state and TE information. Comparing with the Internal Gateway Protocols (IGPs), BGP SPF may have some advantage in supporting a relatively large number of NRPs. This document specifies the BGP SPF mechanisms with necessary extensions to advertise the information of NRPs. The proposed mechanism is applicable to segment routing with MPLS data plane (SR-MPLS), segment routing with IPv6 data plane (SRv6), and native IPv6 data plane.¶
The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", "SHOULD", "SHOULD NOT", "RECOMMENDED", "NOT RECOMMENDED", "MAY", and "OPTIONAL" in this document are to be interpreted as described in BCP14 RFC 2119 [RFC2119] RFC 8174 [RFC8174] when, and only when, they appear in all capitals, as shown here.¶
As described in [I-D.ietf-lsvr-bgp-spf], the NLRI and TLVs of BGP-LS can be reused by BGP SPF, this section describes the TLVs which are defined in BGP-LS and can be reused in BGP SPF for the distribution of NRP related information.¶
According to [I-D.ietf-teas-enhanced-vpn], a virtual transport network (VTN) has a customized network topology and a set of dedicated or shared network resources. Thus a VTN can be defined as the combination of a set of network attributes, including the topology attribute and the network resource attribute. As the instantiation of VTN, an NRP is associated with a Multi-Topology ID (MT-ID) and/or an Algorithm ID which are used to define the NRP topology and path computation constraints. In some cases, each NRP can be associated with a separate MT-ID or a Flex-Algo ID. When the amount of NRPs in a network is large, as described in [I-D.dong-teas-nrp-scalability], multiple NRPs may be associated with the same topology and/or algorithm, so that the amount of topology-specific path computation can be shared by a group of NRPs, this could help to reduce the computation overhead in the control plane.¶
[I-D.ietf-lsvr-bgp-spf] does not cover the usage of Multi-Topology or Flex-Algo with BGP SPF. This document proposes to use Multi-Topology [RFC4915][RFC5120] or Flex-Algo [I-D.ietf-lsr-flex-algo] with BGP SPF for topology and/or algorithm -specific link-state information distribution and path computation. For this purpose, the Multi-topology TLV as defined in [I-D.ietf-idr-rfc7752bis], the SR Algorithm TLV as defined [RFC9085], and the Flex-Algo Definition TLV as defined in [I-D.ietf-idr-bgp-ls-flex-algo] are reused for BGP SPF.¶
[I-D.ietf-lsvr-bgp-spf] does not explicitly describe the usage with Segment Routing data plane. To build SR based NRPs, the SR-MPLS and SRv6 TLVs as defined in [RFC9085] and [I-D.ietf-idr-bgpls-srv6-ext] are reused for BGP SPF.¶
The NRP extensions to BGP-LS as defined in [I-D.dong-idr-bgpls-sr-enhanced-vpn] applies to BGP SPF as well. This section lists the TLVs which are reused by BGP SPF, the detailed format of the TLVs are described in [I-D.dong-idr-bgpls-sr-enhanced-vpn].¶
The BGP-LS Attribute TLVs which are defined in [I-D.dong-idr-bgpls-sr-enhanced-vpn] and reused with BGP-LS-SPF SAFI are listed as below:¶
Further BGP-LS TLVs may be defined in [I-D.dong-idr-bgpls-sr-enhanced-vpn], their usage with BGP SPF will be specified in a future version of this document.¶
In network scenarios where each NRP is associated with a unique MT-ID, The BGP-LS mechanisms used to distribute the NRP topology and resource information to the network controller are described in [I-D.ietf-idr-bgpls-sr-vtn-mt]. Such mechanism can be reused for the distribution of NRP information with BGP SPF.¶
In network scenarios where each NRP is associated with a unique Flex-Algo ID, The BGP-LS mechanisms used to distribute the NRP topology and resource information to the network controller are described in [I-D.zhu-idr-bgpls-sr-vtn-flexalgo]. Such mechanism can be reused for the distribution of NRP information with BGP SPF.¶
In network scenarios where multiple NRPs are associated with the same <topology, algorithm> tuple, while each NRP has different resource attributes, the BGP-LS mechanisms which can be used to distribute the NRP topology and resource information to the network controller are described in [I-D.dong-idr-bgpls-sr-enhanced-vpn]. Such mechanism can be reused for the distribution of NRP information with BGP SPF.¶
The Sequence Number TLV as defined in [I-D.ietf-lsvr-bgp-spf] MUST be carried in the BGP-LS attribute associated with the BGP-LS-SPF NLRI. If the Sequence-Number TLV is not received then the corresponding Link NLRI is considered as malformed and MUST be handled as 'Treat-as- withdraw'. An implementation MAY log an error for further analysis.¶
[I-D.ietf-lsvr-bgp-spf] describes the mechanisms of using the BGP-LS-SPF Node, Link, and Prefix NLRIs for shortest path computation. With the introduction of NRP, the same mechanism is used for the shortest path computation of each NRP. The path computation for a NRP is based on the topology attributes and the constraints specified with the MT-ID and/or Algorithm ID associated with the NRP. When multiple NRPs are associated with the same <topology, algorithm> tuple, the result of the shortest path computation based on that <topology, algorithm> could be shared by these NRPs.¶
This document introduces no additional security vulnerabilities to BGP SPF.¶
The mechanism proposed in this document is subject to the same vulnerabilities as any other protocol that relies on BGP SPF.¶
This document request no IANA actions.¶
TBD¶