| Internet-Draft | OSPFv3 Extensions for SRV6 | June 2023 |
| Li, et al. | Expires 23 December 2023 | [Page] |
The Segment Routing (SR) architecture allows a flexible definition of the end-to-end path by encoding it as a sequence of topological elements called segments. It can be implemented over an MPLS or IPv6 data plane. This document describes the OSPFv3 extensions required to support Segment Routing over the IPv6 data plane (SRv6).¶
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 23 December 2023.¶
Copyright (c) 2023 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 Segment Routing (SR) architecture [RFC8402] specifies how a node can steer a packet using an ordered list of instructions, called segments. These segments are identified using Segment Identifiers (SIDs).¶
Segment Routing can be instantiated on the IPv6 data plane through the use of the Segment Routing Header (SRH) defined in [RFC8754]. Segment Routing instantiation on the IPv6 dataplane is referred to as SRv6.¶
The network programming paradigm for SRv6 is specified in [RFC8986]. It describes how any behavior can be bound to a SID and how any network program can be expressed as a combination of SIDs. It also describes several well-known behaviors that can be bound to SRv6 SIDs.¶
This document specifies OSPFv3 extensions to support SRv6 capabilities as defined in [RFC8986], [RFC8754], and [RFC9259]. The extensions include advertisement of an OSPFv3 router's SRv6 capabilities, SRv6 Locators, and required SRv6 SIDs along with their supported endpoint behaviors. Familiarity with [RFC8986] is necessary to understand the extensions specified in this document.¶
At a high level, the extensions to OSPFv3 are comprised of the following:¶
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 BCP 14 [RFC2119] [RFC8174] when, and only when, they appear in all capitals, as shown here.¶
The SRv6 Capabilities TLV is used by an OSPFv3 router to advertise its support for the SR Segment Endpoint Node [RFC8754] functionality along with its SRv6-related capabilities. This is an optional top level TLV of the OSPFv3 Router Information LSA [RFC7770] which MUST be advertised by an SRv6-enabled router.¶
This TLV MUST be advertised only once in the OSPFv3 Router Information LSA. When multiple SRv6 Capabilities TLVs are received from a given router, the receiver MUST use the first occurrence of the TLV in the OSPFv3 Router Information LSA. If the SRv6 Capabilities TLV appears in multiple OSPFv3 Router Information LSAs that have different flooding scopes, the TLV in the OSPFv3 Router Information LSA with the area-scoped flooding scope MUST be used. If the SRv6 Capabilities TLV appears in multiple OSPFv3 Router Information LSAs that have the same flooding scope, the TLV in the OSPFv3 Router Information LSA with the numerically smallest Link State ID MUST be used and subsequent instances of the TLV MUST be ignored.¶
The OSPFv3 Router Information LSA can be advertised at any of the defined flooding scopes (link, area, or Autonomous System (AS)). For the purpose of SRv6 Capabilities TLV advertisement, area-scoped flooding is REQUIRED. Link and AS-scoped flooding is OPTIONAL.¶
The format of OSPFv3 SRv6 Capabilities TLV is shown below:¶
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 | Length | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | Flags | Reserved | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | Sub-TLVs... +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
Where:¶
Flags: 2-octet field. The flags are defined as follows:¶
0 1
0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| |O| |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+¶
where:¶
The SRv6 Capabilities TLV may contain optional Sub-TLVs. No Sub-TLVs are defined in this specification.¶
An SRv6-enabled OSPFv3 router advertises its algorithm support using the SR-Algorithm TLV defined in [RFC8665] as described in [RFC8666].¶
An SRv6-enabled router may have different capabilities and limits related to SRH processing and these need to be advertised to other OSPFv3 routers in the SRv6 domain.¶
[RFC8476] defines the means to advertise node and link specific values for Maximum SID Depth (MSD) types. Node MSDs are advertised using the Node MSD TLV in the OSPFv3 Router Information LSA [RFC7770] while Link MSDs are advertised using the Link MSD Sub-TLV of the Router-Link TLV [RFC8362]. The format of the MSD types for OSPFv3 is defined in [RFC8476].¶
The MSD types for SRv6 that are defined in section 4 of [RFC9352] for IS-IS are also used by OSPFv3. These MSD Types are allocated under the IGP MSD Types registry maintained by IANA that are shared by IS-IS and OSPF. They are described below:¶
The Maximum Segments Left MSD Type signals the maximum value of the "Segments Left" field of the SRH of a received packet before applying the Endpoint behavior associated with a SID. If no value is advertised, the supported value is assumed to be 0.¶
The Maximum End Pop MSD Type signals the maximum number of SIDs in the SRH to which the router can apply "Penultimate Segment Pop (PSP) of the SRH" or "Ultimate Segment Pop (USP) of the SRH", as defined in [RFC8986] flavors. If the advertised value is zero or no value is advertised, then the router cannot apply PSP or USP flavors.¶
The Maximum H.Encaps MSD Type signals the maximum number of SIDs that can be added as part of the "H.Encaps" behavior as defined in [RFC8986]. If the advertised value is zero or no value is advertised then the headend can apply an SR Policy that only contains one segment, without inserting any SRH. A non-zero SRH Max H.encaps MSD indicates that the headend can insert an SRH with SIDs up to the advertised value.¶
The Maximum End D MSD Type specifies the maximum number of SIDs present in an SRH when performing decapsulation. These include, but are not limited to, End.DX6, End.DT4, End.DT46, End with USD, and End.X with USD as defined in [RFC8986]. If the advertised value is zero or no value is advertised, then the router cannot apply any behavior that results in decapsulation and forwarding of the inner packet when the outer IPv6 header contains an SRH.¶
An SRv6 Segment Identifier (SID) is 128 bits and consists of Locator, Function, and Argument parts as described in [RFC8986].¶
An OSPFv3 router is provisioned with algorithm-specific locators for each algorithm supported by that router. Each locator is a covering prefix for all SIDs provisioned on that router that have the matching algorithm.¶
Locators MUST be advertised within an SRv6 Locator TLV (see Section 7.1) using an SRv6 Locator LSA (see Section 7). The SRv6 Locator LSA is introduced instead of reusing the respective Extended Prefix LSAs [RFC8362] for a clear distinction between the two different types of reachability advertisements (viz., the base OSPFv3 prefix reachability advertisements and the SRv6 Locator reachability advertisements).¶
Forwarding entries for the locators advertised in the SRv6 Locator TLV MUST be installed in the forwarding plane of receiving SRv6-capable routers when the associated algorithm is supported by the receiving OSPFv3 router. Locators can be of different route types that map to existing OSPFv3 LSA types - Intra-Area, Inter-Area, External, and NSSA. The advertisement and propagation of the SRv6 Locator LSAs also follow the OSPFv3 [RFC5340] specifications for the respective LSA types. The processing of the prefix advertised in the SRv6 Locator TLV, the calculation of its reachability, and the installation in the forwarding plane follows the OSPFv3 [RFC5340] specifications for the respective LSA types.¶
Locators associated with algorithms 0 and 1 (refer section 3.1.1 of [RFC8402]) SHOULD also be advertised using OSPFv3 Extended LSA types with extended TLVs [RFC8362] so that routers that do not support SRv6 will install a forwarding entry for SRv6 traffic matching those locators. When operating in Extended LSA sparse-mode [RFC8362], these locators SHOULD be also advertised using legacy OSPFv3 LSAs [RFC5340].¶
When SRv6 Locators are also advertised as Intra-Area-Prefix-LSAs and/or E-Intra-Area-Prefix-LSAs, the SRv6 Locator MUST be considered as a prefix associated with the router and the referenced LSA type MUST point to the Router LSA of the advertising router as specified in Section 4.4.3.9 of [RFC5340].¶
In cases where a locator advertisement is received both in a prefix reachability advertisement (i.e., via legacy OSPFv3 LSAs and/or Extended Prefix TLVs using OSPFv3 Extended LSAs) and an SRv6 Locator TLV, the prefix reachability advertisement in the OSPFv3 legacy LSA or Extended LSA MUST be preferred over the advertisement in the SRv6 Locator TLV when installing entries in the forwarding plane. This is to prevent inconsistent forwarding entries between SRv6 capable and SRv6 incapable OSPFv3 routers. Such preference for prefix reachability advertisement does not have any impact on the rest of the data advertised in the SRv6 Locator TLV.¶
SRv6 SIDs are advertised as Sub-TLVs in the SRv6 Locator TLV except for SRv6 End.X SIDs/LAN End.X SIDs which are associated with a specific Neighbor/Link and are therefore advertised as Sub-TLVs of the E-Router-Link TLV.¶
SRv6 SIDs received from other OSFPv3 routers are not directly routable and MUST NOT be installed in the forwarding plane. Reachability to SRv6 SIDs depends upon the existence of a covering locator.¶
Adherence to the rules defined in this section will ensure that SRv6 SIDs associated with a supported algorithm will be forwarded correctly, while SRv6 SIDs associated with an unsupported algorithm will be dropped. NOTE: The drop behavior depends on the absence of a default/summary route matching the locator prefix.¶
If the locator associated with SRv6 SID advertisements is the longest prefix match installed in the forwarding plane for those SIDs, this will ensure correct forwarding. Network operators should take steps to make sure that this requirement is not compromised. For example, the following situations should be avoided:¶
[RFC9350] specifies IGP Flexible Algorithm mechanisms for OSPFv3. Section 14.2 of [RFC9350] explains SRv6 forwarding for Flexible Algorithm and analogous procedures apply for supporting SRv6 Flexible Algorithm using OSPFv3. When the algorithm value that is advertised in the SRv6 Locator TLV (refer to Section 7.1) represents a Flexible Algorithm, the procedures described in section 14.2 of [RFC9350] are followed for the programming of those specific SRv6 Locators.¶
Locators associated with Flexible Algorithms SHOULD NOT be advertised in the base OSPFv3 prefix reachability advertisements. Advertising the Flexible Algorithm locator in a regular prefix reachability advertisement would make it available for non-Flexible Algorithm forwarding (i.e., algorithm 0).¶
The procedures for OSPFv3 Flexible Algorithm for SR-MPLS, as specified in [RFC9350], like ASBR reachability, inter-area, external, and NSSA prefix advertisements and their use in Flexible Algorithm route computation also apply for SRv6.¶
Both prefixes and SRv6 Locators may be configured as anycast and as such the same value can be advertised by multiple routers. It is useful for other routers to know that the advertisement is for an anycast identifier.¶
A new bit in OSPFv3 PrefixOptions [RFC5340] is defined to advertise the anycast property:¶
0 1 2 3 4 5 6 7
+--+--+--+--+--+--+--+--+
|AC|EL| N|DN| P| x|LA|NU|
+--+--+--+--+--+--+--+--+
Value: 0x80¶
Description: Anycast (AC-bit)¶
When the prefix/SRv6 Locator is configured as anycast, the AC-bit MUST be set. Otherwise, this flag MUST be clear.¶
The AC-bit MUST be preserved when re-advertising the prefix/SRv6 Locator across areas.¶
The AC-bit and the N-bit MUST NOT both be set. If both N-bit and AC-bit are set in the prefix/SRv6 Locator advertisement, the receiving routers MUST ignore the N-bit.¶
The same prefix/SRv6 Locator can be advertised by multiple routers. If at least one of them sets the AC-bit in its advertisement, the prefix/SRv6 Locator is considered as anycast.¶
A prefix/SRv6 Locator that is advertised by a single node and without an AC-bit is considered node-specific.¶
All the nodes advertising the same anycast SRv6 Locator MUST instantiate the exact same set of SIDs under that anycast SRv6 Locator. Failure to do so may result in traffic being dropped or misrouted.¶
The PrefixOptions field is common to the prefix reachability advertisements (i.e., the base OSPFv3 prefix LSA types defined in [RFC5340] and the OSPFv3 Extended Prefix TLV types defined in [RFC8362]) and the SRv6 Locator TLV advertisements specified in Section 7.1 of this document. When a router originates both the prefix reachability advertisement and the SRv6 Locator advertisement for a given prefix, the router SHOULD advertise the same PrefixOptions bits in both advertisements. In the case of any inconsistency between the PrefixOptions advertised in the SRv6 Locator and in the prefix reachability advertisements, the ones advertised in prefix reachability advertisement MUST be preferred.¶
The SRv6 Locator LSA has a function code of 42. The S1/S2 bits are dependent on the desired flooding scope for the LSA. The flooding scope of the SRv6 Locator LSA depends on the scope of the advertised SRv6 Locator and is under the control of the advertising router. The U-bit will be set indicating that the LSA should be flooded even if it is not understood.¶
Multiple SRv6 Locator LSAs can be advertised by an OSPFv3 router and they are distinguished by their Link State IDs (which are chosen arbitrarily by the originating router).¶
The format of SRv6 Locator LSA is shown below:¶
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 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | LS age |U|S12| Function Code | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | Link State ID | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | Advertising Router | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | LS sequence number | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | LS checksum | Length | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | | +- TLVs -+ | ... |
The format of the TLVs within the body of the SRv6 Locator LSA is the same as the format used by [RFC3630]. The variable TLV section consists of one or more nested TLV tuples. Nested TLVs are also referred to as Sub-TLVs. The format of each TLV is:¶
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 | Length | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | Value... | . . . . . . +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
The Length field defines the length of the value portion in octets (thus, a TLV with no value portion would have a length of 0). The TLV is padded to 4-octet alignment; padding is not included in the Length field (so a 3-octet value would have a length of 3, but the total size of the TLV would be 8 octets). Nested TLVs are also 32-bit aligned. For example, a 1-byte value would have the Length field set to 1 and 3 octets of padding would be added to the end of the value portion of the TLV. The padding is composed of zeros.¶
The SRv6 Locator TLV is a top-level TLV of the SRv6 Locator LSA that is used to advertise an SRv6 Locator, its attributes, and SIDs associated with it. Multiple SRv6 Locator TLVs MAY be advertised in each SRv6 Locator LSA. However, since the S12 bits define the flooding scope, the LSA flooding scope has to satisfy the application-specific requirements for all the locators included in a single SRv6 Locator LSA.¶
When multiple SRv6 Locator TLVs are received from a given router in an SRv6 Locator LSA for the same Locator, the receiver MUST use the first occurrence of the TLV in the LSA. If the SRv6 Locator TLV for the same Locator appears in multiple SRv6 Locator LSAs that have different flooding scopes, the TLV in the SRv6 Locator LSA with the area-scoped flooding scope MUST be used. If the SRv6 Locator TLV for the same Locator appears in multiple SRv6 Locator LSAs that have the same flooding scope, the TLV in the SRv6 Locator LSA with the numerically smallest Link-State ID MUST be used and subsequent instances of the TLV MUST be ignored.¶
The format of SRv6 Locator TLV is shown below:¶
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 | Length | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | Route Type | Algorithm | Locator Length| PrefixOptions | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | Metric | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | Locator (up to 16 octets) ... | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | ... Locator continued ... | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | ... Locator continued ... | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | ... Locator concluded | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | Sub-TLVs (variable) | +- -+ | ... |
Where:¶
Route Type: 1-octet field. The type of the locator route. The only supported types are the ones listed below and the SRv6 Locator TLV MUST be ignored on receipt of any other type.¶
1 - Intra-Area
2 - Inter-Area
3 - AS External Type 1
4 - AS External Type 2
5 - NSSA External Type 1
6 - NSSA External Type 2
¶
The following OSPFv3 Extended-LSA sub-TLVs corresponding to the Extended Prefix LSAs are also applicable for use as sub-TLVs of the SRv6 Locator TLV using code points as specified in Section 13.9:¶
The SRv6 End SID Sub-TLV is a Sub-TLV of the SRv6 Locator TLV in the SRv6 Locator LSA (defined in Section 7). It is used to advertise the SRv6 SIDs belonging to the router along with their associated endpoint behaviors. SIDs associated with adjacencies are advertised as described in Section 9. Every SRv6-enabled OSPFv3 router SHOULD advertise at least one SRv6 SID associated with an END behavior for itself as specified in [RFC8986], although it MAY omit doing so if that node is not going to be used as a Segment Endpoint (e.g., for TE or TI-LFA) by any SR Source Node.¶
SRv6 End SIDs inherit the algorithm from the parent locator. The SRv6 End SID MUST be allocated from its associated locator. SRv6 End SIDs that are NOT allocated from the associated locator MUST be ignored.¶
The router MAY advertise multiple instances of the SRv6 End SID Sub-TLV within the SRv6 Locator TLV - one for each of the SRv6 SIDs to be advertised. When multiple SRv6 End SID Sub-TLVs are received in the SRv6 Locator TLV from a given router for the same SRv6 SID value, the receiver MUST use the first occurrence of the Sub-TLV in the SRv6 Locator TLV.¶
The format of SRv6 End SID Sub-TLV is shown below¶
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 | Length | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | Flags | Reserved | Endpoint Behavior | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | SID (128 bits) ... | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | ... SID continued ... | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | ... SID continued ... | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | ... SID concluded | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | Sub-TLVs (variable) . . . +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
Where:¶
The SRv6 endpoint behaviors defined in [RFC8986] include certain behaviors that are specific to links or adjacencies. The most basic of these, which is critical for link-state routing protocols like OSPFv3, is the End.X behavior that is an instruction to forward to a specific neighbor on a specific link. These SRv6 SIDs and others that are defined in [RFC8986] which are specific to links or adjacencies need to be advertised to OSPFv3 routers within an area to steer SRv6 traffic over a specific link or adjacency.¶
Therefore, SRv6 SIDs that are specific to a particular neighbor, such as End.X, are not advertised as a sub-TLVs of the SRv6 Locator TLV but via two different optional Sub-TLVs of the E-Router-Link TLV defined in [RFC8362]:¶
Every SRv6 enabled OSPFv3 router SHOULD instantiate at least one unique SRv6 End.X SID corresponding to each of its neighbors, although it MAY omit doing so if features like traffic engineering or Topology-Independent Loop Free Alternate (TI-LFA) that require End.X SID are not in use. A router MAY instantiate more than one SRv6 End.X SID for a single neighbor. The same SRv6 End.X SID MAY be advertised for more than one neighbor. Thus multiple instances of the SRv6 End.X SID and SRv6 LAN End.X SID Sub-TLVs MAY be advertised within the E-Router-Link TLV for a single link.¶
All End.X and LAN End.X SIDs MUST be subsumed by the subnet of a Locator with the matching algorithm which is advertised by the same OSPFv3 router in an SRv6 Locator TLV. End.X SIDs which do not meet this requirement MUST be ignored. This ensures that the OSPFv3 router advertising the End.X or LAN End.X SID is also advertising its corresponding Locator with the algorithm that will be used for computing paths destined to the SID.¶
The format of the SRv6 End.X SID Sub-TLV is shown below¶
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 | Length | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | Endpoint Behavior | Flags | Reserved1 | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | Algorithm | Weight | Reserved2 | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | SID (128 bits) ... | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | ... SID continued ... | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | ... SID continued ... | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | ... SID concluded | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | Sub-TLVs (variable) . . . +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
Where:¶
Flags: 1-octet field. The flags are defined as follows:¶
0 1 2 3 4 5 6 7
+-+-+-+-+-+-+-+-+
|B|S|P| Reserved|
+-+-+-+-+-+-+-+-+
¶
The format of the SRv6 LAN End.X SID Sub-TLV is as shown below:¶
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 | Length | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | Endpoint Behavior | Flags | Reserved1 | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | Algorithm | Weight | Reserved2 | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | Neighbor Router-ID | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | SID (128 bits) ... | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | ... SID continued ... | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | ... SID continued ... | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | ... SID concluded | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | Sub-TLVs (variable) . . . +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
Where:¶
Flags: 1-octet field. The flags are defined as follows:¶
0 1 2 3 4 5 6 7
+-+-+-+-+-+-+-+-+
|B|S|P| Reserved|
+-+-+-+-+-+-+-+-+
¶
SRv6 SID Structure Sub-TLV is used to advertise the structure of the SRv6 SID as defined in [RFC8986]. It is used as an optional Sub-TLV of the following:¶
The Sub-TLV has the following format:¶
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 | Length | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | LB Length | LN Length | Fun. Length | Arg. Length | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
Where:¶
The SRv6 SID Structure Sub-TLV MUST NOT appear more than once in its parent Sub-TLV. If it appears more than once in its parent Sub-TLV, the parent Sub-TLV MUST be ignored by the receiver.¶
The sum of all four sizes advertised in SRv6 SID Structure Sub-TLV MUST be less than or equal to 128 bits. If the sum of all four sizes advertised in the SRv6 SID Structure Sub-TLV is larger than 128 bits, the parent TLV/Sub-TLV MUST be ignored by the receiver.¶
The SRv6 SID Structure Sub-TLV is intended for informational use by the control and management planes. It MUST NOT be used at a transit node (as defined in [RFC8754]) for forwarding packets. As an example, this information could be used for:¶
The details of these potential applications are outside the scope of this document.¶
Endpoint behaviors are defined in [RFC8986]. The codepoints for the Endpoint behaviors are defined in the "SRv6 Endpoint Behaviors" registry of [RFC8986]. This section lists the Endpoint behaviors and their codepoints, which MAY be advertised by OSPFv3 and the Sub-TLVs in which each type MAY appear.¶
|-----------------------|--------------------|-----|-------|-----------| | Endpoint | Endpoint | End | End.X | LAN End.X | | Behavior | Behavior Codepoint | SID | SID | SID | |-----------------------|--------------------|-----|-------|-----------| | End (PSP, USP, USD) | 1-4, 28-31 | Y | N | N | |-----------------------|--------------------|-----|-------|-----------| | End.X (PSP, USP, USD) | 5-8, 32-35 | N | Y | Y | |-----------------------|--------------------|-----|-------|-----------| | End.DX6 | 16 | N | Y | Y | |-----------------------|--------------------|-----|-------|-----------| | End.DX4 | 17 | N | Y | Y | |-----------------------|--------------------|-----|-------|-----------| | End.DT6 | 18 | Y | N | N | |-----------------------|--------------------|-----|-------|-----------| | End.DT4 | 19 | Y | N | N | |-----------------------|--------------------|-----|-------|-----------| | End.DT64 | 20 | Y | N | N | |-----------------------|--------------------|-----|-------|-----------|
This document introduces extensions to the OSPFv3 protocol and as such does not affect existing security considerations for OSPFv3 as documented in [RFC5340]. [RFC7166] describes an alternative and improved authentication mechanism to IPsec for OSPFv3. The use of authentication is RECOMMENDED for OSPFv3 deployment.¶
Reception of malformed TLV or Sub-TLV SHOULD be counted and/or logged in a rate-limited manner for further analysis.¶
This document describes the OSPFv3 extensions required to support Segment Routing over an IPv6 data plane. The security considerations for Segment Routing are discussed in [RFC8402]. [RFC8986] defines the SRv6 Network Programming concept and specifies the main Segment Routing behaviors to enable the creation of interoperable overlays; the security considerations from that document apply too.¶
The advertisement of an incorrect MSD value may have negative consequences, see [RFC8476] for additional considerations.¶
Security concerns associated with the setting of the O-flag are described in [RFC9259].¶
Security concerns associated with the usage of Flexible Algorithms are described in [RFC9350].¶
This document requests IANA to perform allocations from OSPF and OSPFv3 related registries as well as creating of new registries as follows.¶
IANA has allocated a code point via the early allocation process in the "OSPF Router Information (RI) TLVs" registry under the "OSPF Parameters" registry group for the new TLV below that needs to be made permanent:¶
IANA has allocated a code point via the early allocation process in the "OSPFv3 LSA Function Codes" registry under the "OSPFv3 Parameters" registry group for the new LSA below that needs to be made permanent:¶
IANA has allocated a code point via the early allocation process in the "OSPFv3 Prefix Options" registry under the "OSPFv3 Parameters" registry group as below that needs to be made permanent:¶
This document requests a new IANA sub-registry name "OSPFv3 SRv6 Capabilities TLV Flags" be created under the "OSPFv3 Parameters" registry group to control the assignment of bits 0 to 15 in the Flags field of the OSPFv3 SRv6 Capabilities TLV specified in this document. The registration procedure is "Standards Action" as defined in [RFC8126].¶
The following assignments are made by this document:¶
This document requests a new IANA sub-registry name "OSPFv3 SRv6 End SID Sub-TLV Flags" be created under the "OSPFv3 Parameters" registry group to control the assignment of bits 0 to 7 in the Flags field of the OSPFv3 SRv6 End SID Sub-TLV specified in this document. The registration procedure is "Standards Action" as defined in [RFC8126].¶
No assignments are made by this document.¶
This document requests a new IANA sub-registry name "OSPFv3 SRv6 Adjacency SID Sub-TLV Flags" be created under the "OSPFv3 Parameters" registry group to control the assignment of bits 0 to 7 in the Flags field of the OSPFv3 SRv6 End.X SID and OSPFv3 SRv6 LAN End.X SID Sub-TLVs specified in this document. The registration procedure is "Standards Action" as defined in [RFC8126].¶
The following assignments are made by this document:¶
IANA has allocated the following code points via the early allocation process in the "OSPFv3 Extended-LSA Sub-TLVs" registry under the "OSPFv3 Parameters" registry group for the new Sub-TLVs below that need to be made permanent:¶
For all 3 of these sub-TLVs the column L2BM in the registry is set to "Y".¶
This document requests the creation of an "OSPFv3 SRv6 Locator LSA TLVs" registry, that defines top-level TLVs for the OSPFv3 SRv6 Locator LSA, under the "OSPFv3 Parameters" registry group. The initial code-points assignment is as below:¶
Types in the range 2-32767 are allocated via IETF Review or IESG Approval [RFC8126].¶
Types in the range 32768-33023 are Reserved for Experimental Use; these will not be registered with IANA and MUST NOT be mentioned by RFCs.¶
Types in the range 33024-45055 are to be assigned on a First Come First Served (FCFS) basis.¶
Types in the range 45056-65535 are not to be assigned at this time. Before any assignments can be made in the 45056-65535 range, there MUST be an IETF specification that specifies IANA Considerations that cover the range being assigned.¶
This document requests the creation of an "OSPFv3 SRv6 Locator LSA Sub-TLVs" registry, that defines Sub-TLVs at any level of nesting for the SRv6 Locator LSA, to be added under the "OSPFv3 Parameters" registry group. The initial code-points assignment is as below:¶
Types in the range 6-9 and 11-32767 are allocated via IETF Review or IESG Approval [RFC8126].¶
Types in the range 32768-33023 are Reserved for Experimental Use; these will not be registered with IANA and MUST NOT be mentioned by RFCs.¶
Types in the range 33024-45055 are to be assigned on a First Come First Served (FCFS) basis.¶
Types in the range 45056-65535 are not to be assigned at this time. Before any assignments can be made in the 45056-65535 range, there MUST be an IETF specification that specifies IANA Considerations that cover the range being assigned.¶
The note indicated below needs to be added under this registry to ensure that any document requesting allocations under this registry for sub-TLVs of any of the OSPFv3 SRv6 Locator TLVs checks if allocations are also applicable for the "OSPFv3 Extended-LSA Sub-TLVs" registry.¶
Note: Allocations made under this registry for any sub-TLVs that are associated with OSPFv3 SRv6 Locator TLVs MUST be also evaluated for their applicability as OSPFv3 Extended-LSA Sub-TLVs and, therefore, also requiring allocation under the "OSPFv3 Extended-LSA Sub-TLVs" registry.¶
This document requests IANA to add the note indicated below under the "OSPFv3 Extended-LSA Sub-TLVs" registry under the "OSPFv3 Parameters" registry group. The purpose of this note is to ensure that any document requesting allocations under this registry for sub-TLVs of any of the OSPFv3 Extended Prefix TLVs checks if allocations are also applicable for the "OSPFv3 SRv6 Locator LSA Sub-TLVs" registry that is created by this document.¶
Note: Allocations made under this registry for any sub-TLVs that are associated with OSPFv3 Extended TLVs related to prefix advertisements MUST be also evaluated for their applicability as OSPFv3 SRv6 Locator Sub-TLVs and, therefore, also requiring allocation under the "OSPFv3 SRv6 Locator LSA Sub-TLVs" registry.¶
The authors would like to acknowledge the contributions of Dean Cheng in the early versions of this document. The authors would like to thank Ran Chen and Detao Zhao for their suggestions related to the extension of PrefixOptions for the signaling of the anycast property.¶
The authors would like to thank Chenzichao, Dirk Goethals, Baalajee S, Yingzhen Qu, Shraddha Hegde, Dhruv Dhody, Martin Vigoureux, and Reese Enghardt for their review and comments on this document. The authors would like to thank Acee Lindem for his detailed shepherd review and feedback for improvement of this document. The authors would like to thank John Scudder for his AD review and suggestions to improve this document.¶