]> Compressed SRv6 Segment List Encoding China Mobile
China chengweiqiang@chinamobile.com
Cisco Systems, Inc.
Belgium cf@cisco.com
Huawei Technologies
China lizhenbin@huawei.com
Orange
France bruno.decraene@orange.com
Cisco Systems, Inc.
France fclad.ietf@gmail.com
General SPRING Internet-Draft Segment Routing over IPv6 (SRv6) is the instantiation of Segment Routing (SR) on the IPv6 dataplane. This document specifies new flavors for the SRv6 endpoint behaviors defined in RFC 8986, which enable the compression of an SRv6 SID list. Such compression significantly reduces the size of the SRv6 encapsulation needed to steer packets over long segment lists.
Introduction The Segment Routing (SR) architecture describes two data plane instantiations of SR: SR over MPLS (SR-MPLS) and SR over IPv6 (SRv6). SRv6 Network Programming builds upon the IPv6 Segment Routing Header (SRH) to define a framework for constructing a network program with topological and service segments. Some SRv6 applications such as strict path traffic engineering may require long segment lists. Compressing the encoding of these long segment lists in the packet header can significantly reduce the header size. This document specifies new flavors to the SRv6 endpoint behaviors defined in that enable a compressed encoding of the SRv6 segment list. This document also specifies new SRv6 endpoint behaviors to preserve the efficiency of CSID compression in multi-domain environments. The SRv6 endpoint behaviors defined in this document leverage the SRv6 data plane defined in and , and are compatible with the SRv6 control plane extensions for IS-IS , OSPF , and BGP .
Terminology This document leverages the terms defined in , , and , in particular segment, segment list, SID, SID list, SR policy, prefix segment, adjacency segment, SRH, SR domain, SR source node, SR segment endpoint node, transit node, SRv6 endpoint behavior, flavor, SID block, locator, function, and argument. The reader is assumed to be familiar with this terminology. This document introduces the following new terms: Locator-Block: The most significant bits of a SID locator that represent the SRv6 SID block. The Locator-Block is referred to as "B" in Section 3.1 of . Locator-Node: The least significant bits of a SID locator that identify the SR segment endpoint node instantiating the SID. The Locator-Node is referred to as "N" in Section 3.1 of . Compressed-SID (CSID): A compressed encoding of a SID. The CSID includes the Locator-Node and Function bits of the SID being compressed. If the Locator-Node length of a SID is zero, then the Locator-Node length of its CSID encoding is also zero. Similarly, if the Function length of a SID is zero, then the Function length of its CSID encoding is zero. CSID container: A 128-bit IPv6 address that functions as a container holding a list of one or more CSIDs, and the Argument (if any) of the last CSID. CSID sequence: A group of one or more consecutive SID list entries encoding the common Locator-Block and at least one CSID container. Compressed SID list: A segment list encoding that reduces the packet header length thanks to one or more CSID sequences. A compressed SID list also contains zero, one, or more uncompressed SIDs. Global Identifiers Block (GIB): The pool of CSID values available for global allocation. Local Identifiers Block (LIB): The pool of CSID values available for local allocation. In this document, the length of each constituent part of a SID is referred to as follows. LBL is the Locator-Block length of the SID. LNL is the Locator-Node length of the SID. FL is the Function length of the SID. AL is the Argument length of the SID. In addition, LNFL is the sum of the Locator-Node length and the Function length of the SID. It is also referred to as the CSID length.
Requirements Language 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 when, and only when, they appear in all capitals, as shown here.
Basic Concepts In an SR domain, all SRv6 SIDs instantiated from the same Locator-Block share the same most significant bits. In addition, when the combined length of the SRv6 SID Locator, Function, and Argument is smaller than 128 bits, the least significant bits of the SID are padded with zeros. The compressed segment list encoding seeks to decrease the packet header length by avoiding the repetition of the same Locator-Block and reducing the use of padding bits. Building upon and fully compatible with the mechanisms specified in and , the compressed segment list encoding leverages a SID list compression logic at the SR source node (see ) in combination with new flavors of the SRv6 endpoint behaviors that process the compressed SID list (see ). An SR source node constructs and compresses the SID list depending on the SIDs instantiated on each SR segment endpoint node that the packet is intended to traverse, as well as its own compression capabilities. The resulting compressed SID list is a combination of CSID sequences, for the SIDs that the SR source node was able to compress, and uncompressed SIDs, which could not be compressed. In case the SR source node is able to compress all the SIDs in the SID list, the compressed SID list comprises only CSID sequences (one or more), and no uncompressed SIDs. Conversely, the compressed SID list comprises only uncompressed SIDs when the SR source is unable to compress any of the constituent SIDs.
SR Segment Endpoint Flavors This section defines two SR segment endpoint flavors, NEXT-CSID and REPLACE-CSID, for the End, End.X, End.T, End.B6.Encaps, End.B6.Encaps.Red, and End.BM behaviors of . This section also defines a REPLACE-CSID flavor for the End.DX6, End.DX4, End.DT6, End.DT4, End.DT46, End.DX2, End.DX2V, End.DT2U, and End.DT2M behaviors of . A counterpart NEXT-CSID flavor is not defined for these behaviors: since any SID can be the last element of a CSID sequence compressed using the NEXT-CSID flavor (see ) and the aforementioned SRv6 endpoint behaviors are always in the last position in a SID list, there is no need for any modification of the behaviors defined in . Future documents may extend the applicability of the NEXT-CSID and REPLACE-CSID flavors to other SRv6 endpoint behaviors (see ). The use of these flavors, either individually or in combination, enables the compressed segment list encoding. The NEXT-CSID flavor and the REPLACE-CSID flavor both leverage the SID Argument to determine the next SID to be processed, but employ different SID list compression schemes. With the NEXT-CSID flavor, each CSID container is a fully formed SRv6 SID with the common Locator-Block for all the CSIDs in the CSID container, a Locator-Node and Function that are those of the first CSID, and an Argument carrying the subsequent CSIDs. With the REPLACE-CSID flavor, only the first element in a CSID sequence is a fully formed SRv6 SID. It has the common Locator-Block for all the CSIDs in the CSID sequence, and a Locator-Node and Function that are those of the first CSID. The remaining elements in the CSID sequence are CSID containers carrying the subsequent CSIDs without the Locator-Block. In the remainder of this document, the term "a SID of this document" refers to any End, End.X, End.T, End.B6.Encaps, End.B6.Encaps.Red, or End.BM SID with the NEXT-CSID or the REPLACE-CSID flavor, and with any combination of Penultimate Segment Pop (PSP), Ultimate Segment Pop (USP), and Ultimate Segment Decapsulation (USD) flavor, or any End.DX6, End.DX4, End.DT6, End.DT4, End.DT46, End.DX2, End.DX2V, End.DT2U, or End.DT2M with the REPLACE-CSID flavor. All the SRv6 endpoint behaviors introduced in this document are listed in at the end of the document. In the remainder of this document, the terms "NEXT-CSID flavor SID" and "REPLACE-CSID flavor SID" refer to any SID of this document with the NEXT-CSID flavor and with the REPLACE-CSID flavor, respectively.
NEXT-CSID Flavor A CSID sequence compressed using the mechanism of the NEXT-CSID flavor comprises one or more CSID containers. Each CSID container is a fully formed 128-bit SID structured as shown in . It carries a Locator-Block followed by a series of CSIDs. The Locator-Node and Function of the CSID container are those of the first CSID, and its Argument is the contiguous series of subsequent CSIDs. The second CSID is encoded in the most significant bits of the CSID container Argument, the third CSID is encoded in the bits of the Argument that immediately follow the second CSID, and so on. When all CSIDs have the same length, a CSID container can carry up to K CSIDs, where K is computed as floor((128-LBL)/LNFL) (floor(x) is the greatest integer less than or equal to x ). Each CSID container for NEXT-CSID is independent, such that contiguous CSID containers in a CSID sequence can be considered as separate CSID sequences. When a CSID sequence compressed using the NEXT-CSID flavor comprises at least two CSIDs, the last CSID in the sequence is not required to have the NEXT-CSID flavor. It can be bound to any SRv6 endpoint behavior, including behaviors and REPLACE-CSID flavor, as long as the updated destination address resulting from the processing of the previous CSID in the sequence is a valid form for that last SID. Line S12 of the first pseudocode in provides sufficient conditions to ensure this property.
Locator-Block Loc-Node Argument Function LBL LNFL AL <------> <------------------------------> LBL LNFL AL ]]>
illustrates a compressed SID list as could be produced by an SR source node steering a packet into an SR policy with a SID list of eight NEXT-CSID flavor SIDs. All SIDs in this example have a 48-bit Locator-Block, 16-bit combined Locator-Node and Function, and 64-bit Argument. The SR source node compresses the SR policy SID list as a compressed SID list of two CSID containers. The first CSID container carries a Locator-Block and the first five CSIDs. The second CSID container carries a Locator-Block and the sixth, seventh, and eighth CSIDs. Since the SR source node does not use the second CSID container at full capacity, it sets the 32 least significant bits to zero. The SR source node sets the IPv6 Destination Address (DA) with the value of the first CSID container and the first element of the SRH Segment List with the value of the second CSID container. Without reduced SRH, the SR source node also writes the first CSID container as the second element of the SRH Segment List (the elements in the SRH Segment List appear in reversed order of their processing, as specified in Section 4.1 of ).
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 Locator-Block 1st CSID 2nd CSID 3rd CSID 4th CSID 5th CSID First CSID container 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 Locator-Block 6th CSID 7th CSID 8th CSID 0 Second CSID container
An implementation MUST support a 32-bit Locator-Block length (LBL) and a 16-bit CSID length (LNFL) for NEXT-CSID flavor SIDs, and may support any other Locator-Block and CSID length. The Argument length (AL) for NEXT-CSID flavor SIDs is equal to 128-LBL-LNFL. When processing an IPv6 packet that matches a FIB entry locally instantiated as a SID with the NEXT-CSID flavor, the SR segment endpoint node applies the procedure specified in the following subsection that corresponds to the SID behavior. If the SID also has the PSP, USP, or USD flavor, the procedure is modified as described in . An SR segment endpoint node instantiating a SID of this document with the NEXT-CSID flavor MUST accept any Argument value for that SID. At high level, for any SID with the NEXT-CSID flavor, the SR segment endpoint node determines the next SID of the SID list as follows. If the Argument value of the active SID is non-zero, the SR segment endpoint node constructs the next SID from the active SID by copying the entire SID Argument value to the bits that immediately follow the Locator-Block, thus overwriting the active SID Locator-Node and Function with those of the next CSID, and filling the least significant LNFL bits of the Argument with zeros. Otherwise (if the Argument value is 0), the SR segment endpoint node copies the next 128-bit Segment List entry from the SRH to the Destination Address field of the IPv6 header.
End with NEXT-CSID When processing an IPv6 packet that matches a FIB entry locally instantiated as an End SID with the NEXT-CSID flavor, the procedure described in Section 4.1 of is executed with the following modifications. The below pseudocode is inserted between lines S01 and S02 of the SRH processing in Section 4.1 of . In addition, this pseudocode is executed before processing any extension header that is not an SRH, a Hop-by-Hop header or a Destination Option header, or before processing the upper-layer header, whichever comes first.
A rendering of the complete pseudocode is provided in .
End.X with NEXT-CSID When processing an IPv6 packet that matches a FIB entry locally instantiated as an End.X SID with the NEXT-CSID flavor, the procedure described in Section 4.2 of is executed with the following modifications. The pseudocode in of this document is modified by replacing line N08 as shown below.
The resulting pseudocode is inserted between lines S01 and S02 of the SRH processing in Section 4.1 of after applying the modification described in Section 4.2 of . In addition, this pseudocode is executed before processing any extension header that is not an SRH, a Hop-by-Hop header or a Destination Option header, or before processing the upper-layer header, whichever comes first. A rendering of the complete pseudocode is provided in .
End.T with NEXT-CSID When processing an IPv6 packet that matches a FIB entry locally instantiated as an End.T SID with the NEXT-CSID flavor, the procedure described in Section 4.3 of is executed with the following modifications. The pseudocode in of this document is modified by replacing line N08 as shown below.
The resulting pseudocode is inserted between lines S01 and S02 of the SRH processing in Section 4.1 of after applying the modification described in Section 4.3 of . In addition, this pseudocode is executed before processing any extension header that is not an SRH, a Hop-by-Hop header or a Destination Option header, or before processing the upper-layer header, whichever comes first. A rendering of the complete pseudocode is provided in .
End.B6.Encaps with NEXT-CSID When processing an IPv6 packet that matches a FIB entry locally instantiated as an End.B6.Encaps SID with the NEXT-CSID flavor, the procedure described in Section 4.13 of is executed with the following modifications. The pseudocode in of this document is modified by replacing line N08 as shown below.
The resulting pseudocode is inserted between lines S01 and S02 of the SRH processing in Section 4.13 of . In addition, this pseudocode is executed before processing any extension header that is not an SRH, a Hop-by-Hop header or a Destination Option header, or before processing the upper-layer header, whichever comes first. A rendering of the complete pseudocode is provided in . Similar to the base End.B6.Encaps SID defined in Section 4.13 of , the NEXT-CSID flavor variant updates the Destination Address field of the inner IPv6 header to the next SID in the original segment list before encapsulating the packet with the segment list of SR Policy B. At the endpoint of SR Policy B, the encapsulation is removed and the inner packet is forwarded towards the exposed destination address, which already contains the next SID in the original segment list.
End.B6.Encaps.Red with NEXT-CSID This is an optimization of the End.B6.Encaps with NEXT-CSID behavior. When processing an IPv6 packet that matches a FIB entry locally instantiated as an End.B6.Encaps.Red SID with the NEXT-CSID flavor, the procedure described in of this document is executed with the modifications in Section 4.14 of .
End.BM with NEXT-CSID When processing an IPv6 packet that matches a FIB entry locally instantiated as an End.BM SID with the NEXT-CSID flavor, the procedure described in Section 4.15 of is executed with the following modifications. The pseudocode in of this document is modified by replacing line N08 as shown below.
The resulting pseudocode is inserted between lines S01 and S02 of the SRH processing in Section 4.15 of . In addition, this pseudocode is executed before processing any extension header that is not an SRH, a Hop-by-Hop header or a Destination Option header, or before processing the upper-layer header, whichever comes first. A rendering of the complete pseudocode is provided in .
Combination with PSP, USP and USD flavors PSP: The PSP flavor defined in Section 4.16.1 of is unchanged when combined with the NEXT-CSID flavor. USP: The USP flavor defined in Section 4.16.2 of is unchanged when combined with the NEXT-CSID flavor. USD: The USP flavor defined in Section 4.16.3 of is unchanged when combined with the NEXT-CSID flavor.
REPLACE-CSID Flavor A CSID sequence compressed using the mechanism of the REPLACE-CSID flavor starts with a CSID container in fully formed 128-bit SID format. The Locator-Block of this SID is the common Locator-Block for all the CSIDs in the CSID sequence, its Locator-Node and Function are those of the first CSID, and its Argument carries the index of the current CSID in the current CSID container. The Argument value is initially 0. When more segments are present in the segment list, the CSID sequence continues with one or more CSID containers in packed format carrying the series of subsequent CSIDs. Each container in packed format is a 128-bit Segment List entry split into K "positions" of LNFL bits, where K is computed as floor(128/LNFL). If LNFL does not divide into 128 perfectly, a zero pad is added in the least significant bits of the CSID container to fill the bits left over. The second CSID in the CSID sequence is encoded in the least significant bit position of the first CSID container in packed format (position K-1), the third CSID is encoded in position K-2, and so on. The last CSID in the CSID sequence is not required to have the REPLACE-CSID flavor. It can be bound to any SRv6 endpoint behavior, including behaviors and NEXT-CSID flavor, as long as it meets the conditions defined in . The structure of a SID with the REPLACE-CSID flavor is shown in . The same structure is also that of the CSID container for REPLACE-CSID in fully formed 128-bit SID format.
Locator-Block Locator-Node Argument + Function LBL LNFL AL <--------------> <-----------------------> LBL LNFL AL ]]>
The structure of a CSID container for REPLACE-CSID in packed format is shown in .
Fourth CSID Third CSID Second CSID First CSID (position 0) (position 1) (position 2) (position 3) LNFL LNFL LNFL LNFL <--------------> <--------------> <--------------> LNFL LNFL LNFL LNFL ]]>
illustrates a compressed SID list as could be produced by an SR source node steering a packet into an SR policy SID list of seven REPLACE-CSID flavor SIDs. All SIDs in this example have a 48-bit Locator-Block, 32-bit combined Locator-Node and Function, and 48-bit Argument. The SR source node compresses the SR policy SID list as a compressed SID list of three CSID containers. The first CSID container is in fully formed 128-bit SID format. It carries a Locator-Block, the first CSID, and the argument value zero. The second and third CSID containers are in packed format. The second CSID container carries the second, third, fourth, and fifth CSIDs. The third CSID container carries the sixth and seventh CSIDs. Since the SR source node does not use the third CSID container at full capacity, it sets the 64 least significant bits to zero. The SR source node sets the IPv6 DA with the value of the first CSID container, sets the first element in the SRH Segment List with the value of the third CSID container, and sets the second element of the SRH Segment List with the value of the second CSID container (the elements in the SRH Segment List appear in reversed order of their processing, as specified in Section 4.1 of ). Without reduced SRH, the SR source node also writes the first CSID container as the third element of the SRH Segment List.
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 Locator-Block 1st CSID 1st CSID continued 0 First CSID container 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 5th CSID 4th CSID 3rd CSID 2nd CSID Second CSID container 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 7th CSID 6th CSID Third CSID container
The REPLACE-CSID flavor SIDs support any Locator-Block length (LBL), depending on the needs of the operator, as long as it does not exceed 128-LNFL-ceiling(log_2(128/LNFL)) (ceiling(x) is the least integer greater than or equal to x ), so that enough bits remain available for the CSID and Argument. A Locator-Block length of 48, 56, 64, 72, or 80 bits is recommended for easier reading in operation. This document defines the REPLACE-CSID flavor for 16-bit and 32-bit CSID lengths (LNFL). An implementation MUST support a 32-bit CSID length for REPLACE-CSID flavor SIDs. The Argument length (AL) for REPLACE-CSID flavor SIDs is equal to 128-LBL-LNFL. The index value is encoded in the least significant X bits of the Argument, where X is computed as ceiling(log_2(128/LNFL)). When processing an IPv6 packet that matches a FIB entry locally instantiated as a SID with the REPLACE-CSID flavor, the SR segment endpoint node applies the procedure specified in the following subsection that corresponds to the SID behavior. If the SID also has the PSP, USP, or USD flavor, the procedure is modified as described in . At high level, at the start of a CSID sequence using the REPLACE-CSID flavor, the first CSID container in fully formed 128-bit SID format is copied to the Destination Address of the IPv6 header. Then, for any SID with the REPLACE-CSID flavor, the SR segment endpoint node determines the next SID of the SID list as follows. When an SRH is present, the SR segment endpoint node decrements the index value in the Argument of the active SID if the index value is not 0 or, if it is 0, decrements the Segments Left value in the SRH and sets the index value in the Argument of the active SID to K-1. The updated index value indicates the position of the next CSID within the CSID container in packed format at the "Segment List" index "Segments Left" in the SRH. The SR segment endpoint node then constructs the next SID by copying this next CSID to the bits that immediately follow the Locator-Block in the Destination Address field of the IPv6 header, thus overwriting the active SID Locator-Node and Function with those of the next CSID. If no SRH is present, the SR segment endpoint node ignores the index value in the SID Argument (except End.DT2M, see ) and processes the upper-layer header as per . The CSID sequence ends with a last CSID in the last CSID container that does not have the REPLACE-CSID flavor, or with the special CSID value 0, or when reaching the end of the segment list, whichever comes first.
End with REPLACE-CSID When processing an IPv6 packet that matches a FIB entry locally instantiated as an End SID with the REPLACE-CSID flavor, the SRH processing described in Section 4.1 of is executed with the following modifications. Line S02 of SRH processing in Section 4.1 of is replaced as follows.
Lines S09 to S15 are replaced by the following pseudo code.
max_LE) or (Segments Left > Last Entry)) { R03. Send an ICMP Parameter Problem to the Source Address, Code 0 (Erroneous header field encountered), Pointer set to the Segments Left field, interrupt packet processing and discard the packet. R04. } R05. Decrement DA.Arg.Index by 1. R06. If (Segment List[Segments Left][DA.Arg.Index] == 0) { R07. Decrement Segments Left by 1. R08. Decrement IPv6 Hop Limit by 1. R09. Update IPv6 DA with Segment List[Segments Left] R10. Submit the packet to the egress IPv6 FIB lookup for transmission to the new destination. R11. } R12. } Else { R13. If((Last Entry > max_LE) or (Segments Left > Last Entry+1)){ R14. Send an ICMP Parameter Problem to the Source Address, Code 0 (Erroneous header field encountered), Pointer set to the Segments Left field, interrupt packet processing and discard the packet. R15. } R16. Decrement Segments Left by 1. R17. Set DA.Arg.Index to (floor(128/LNFL) - 1). R18. } R19. Decrement IPv6 Hop Limit by 1. R20. Write Segment List[Segments Left][DA.Arg.Index] into the bits [LBL..LBL+LNFL-1] of the Destination Address of the IPv6 header. R21. Submit the packet to the egress IPv6 FIB lookup for transmission to the new destination. ]]>
The upper-layer header processing described in Section 4.1.1 of is unchanged. A rendering of the complete pseudocode is provided in .
End.X with REPLACE-CSID When processing an IPv6 packet that matches a FIB entry locally instantiated as an End.X SID with the REPLACE-CSID flavor, the procedure described in Section 4.2 of is executed with the following modifications. The pseudocode in of this document is modified by replacing lines R10 and R21 as shown below.
The SRH processing in Section 4.2 of is replaced with the resulting pseudocode. The upper-layer header processing is unchanged. A rendering of the complete pseudocode is provided in .
End.T with REPLACE-CSID When processing an IPv6 packet that matches a FIB entry locally instantiated as an End.T SID with the REPLACE-CSID flavor, the procedure described in Section 4.3 of is executed with the following modifications. The pseudocode in of this document is modified by replacing lines R10 and R21 as shown below.
The SRH processing in Section 4.3 of is replaced with the resulting pseudocode. The upper-layer header processing is unchanged. A rendering of the complete pseudocode is provided in .
End.B6.Encaps with REPLACE-CSID When processing an IPv6 packet that matches a FIB entry locally instantiated as an End.B6.Encaps SID with the REPLACE-CSID flavor, the procedure described in Section 4.13 of is executed with the following modifications. The pseudocode in of this document is modified by replacing lines R10 and R21 as shown below.
The SRH processing in Section 4.13 of is replaced with the resulting pseudocode. The upper-layer header processing is unchanged. A rendering of the complete pseudocode is provided in .
End.B6.Encaps.Red with REPLACE-CSID This is an optimization of the End.B6.Encaps with REPLACE-CSID behavior. When processing an IPv6 packet that matches a FIB entry locally instantiated as an End.B6.Encaps.Red SID with the REPLACE-CSID flavor, the procedure described in of this document is executed with the modifications in Section 4.14 of .
End.BM with REPLACE-CSID When processing an IPv6 packet that matches a FIB entry locally instantiated as an End.BM SID with the REPLACE-CSID flavor, the procedure described in Section 4.15 of is executed with the following modifications. The pseudocode in of this document is modified by replacing lines R10 and R21 as shown below.
The SRH processing in Section 4.15 of is replaced with the resulting pseudocode. The upper-layer header processing is unchanged. A rendering of the complete pseudocode is provided in .
End.DX and End.DT with REPLACE-CSID When processing an IPv6 packet that matches a FIB entry locally instantiated as an End.DX6, End.DX4, End.DT6, End.DT4, End.DT46, End.DX2, End.DX2V, or End.DT2U SID with the REPLACE-CSID flavor, the corresponding procedure described in Sections 4.4 through 4.11 of is executed. These SIDs differ from those defined in by the presence of an Argument as part of the SID structure. The Argument value is ignored by the SR segment endpoint node. When processing an IPv6 packet that matches a FIB entry locally instantiated as an End.DT2M SID with the REPLACE-CSID flavor, the procedure described in Section 4.12 of is executed with the following modification. For any End.DT2M SID with the REPLACE-CSID flavor, the value of Arg.FE2 is 16-bit long. The SR segment endpoint node obtains the value Arg.FE2 from the 16 most significant bits of DA.Argument if DA.Arg.Index is zero, or from the 16 least significant bits of the next position in the current CSID container (Segment List[Segments Left][DA.Arg.Index-1]) otherwise (DA.Arg.Index is non-zero).
Combination with PSP, USP, and USD flavors PSP: When combined with the REPLACE-CSID flavor, the additional PSP flavor instructions defined in Section 4.16.1.2 of are inserted after lines R09 and R20 of the pseudocode in , and the first line of the inserted instructions after R20 is modified as follows.
USP: When combined with the REPLACE-CSID flavor, the line S03 of the pseudocode in are substituted by the USP flavor instructions S03.1 to S03.4 defined in Section 4.16.2 of . Note that S03 is shown in the complete pseudocode in . USD: The USD flavor defined in Section 4.16.3 of is unchanged when combined with the REPLACE-CSID flavor.
CSID Allocation The CSID value of 0 is reserved. It is used to indicate the end of a CSID container. In order to efficiently manage the CSID numbering space, a deployment may divide it into two non-overlapping sub-spaces: a Global Identifiers Block (GIB) and a Local Identifiers Block (LIB). The CSID values that are allocated from the GIB have a global semantic within the Locator-Block, while those that are allocated from the LIB have a local semantic on an SR segment endpoint node and within the scope of the Locator-Block. The concept of LIB is applicable to SRv6 and specifically to its NEXT-CSID and REPLACE-CSID flavors. The shorter the CSID, the more benefit the LIB brings. The opportunity to use these sub-spaces, their size, and their CSID allocation policy depends on the CSID length relative to the size of the network (e.g., number of nodes, links, service routes). Some guidelines for a typical deployment scenario are provided in the below subsections.
Global CSID A global CSID is a CSID allocated from the GIB. A global CSID identifies a segment defined at the Locator-Block level. The tuple (Locator-Block, CSID) identifies the same segment across all nodes of the SR domain. A typical example is a prefix segment bound to the End behavior. A node can have multiple global CSIDs under the same Locator-Block (e.g., one per IGP flexible algorithm ()). Multiple nodes may share the same global CSID (e.g., anycast).
Local CSID A local CSID is a CSID allocated from the LIB. A local CSID identifies a segment defined at the node level and within the scope of a particular Locator-Block. The tuple (Locator-Block, CSID) identifies a different segment on each node of the SR domain. A typical example is a non-routed Adjacency segment bound to the End.X behavior. Let N1 and N2 be two different physical nodes of the SR domain and I a local CSID value, N1 may allocate value I to SID S1 and N2 may allocate the same value I to SID S2.
Recommended Installation of CSIDs in FIB Section 4.3 of defines how an SR segment endpoint node identifies a locally instantiated SRv6 SID. To ensure that any valid argument value is accepted, an SR segment endpoint node instantiating a NEXT-CSID or REPLACE-CSID flavor SID should install a corresponding FIB entry that matches only the Locator and Function parts of the SID (i.e., with a prefix length of LBL + LNL + FL). In addition, an SR segment endpoint node instantiating NEXT-CSID flavor SIDs from both GIB and LIB may install combined "Global + Local" FIB entries to match a sequence of global and local CSIDs in a single longest prefix match (LPM) lookup. For example, let us consider an SR segment endpoint node 10 instantiating the following two NEXT-CSID flavor SIDs according to the CSID length, Locator-Block length, and GIB/LIB recommendations in this section. 2001:db8:b1:10:: bound to the End behavior with the NEXT-CSID flavor is instantiated from GIB with Locator-Block length (LBL) = 48 (Locator-Block value 0x20010db800b1), Locator-Node length (LNL) = 16 (Locator-Node value 0x0010), Function length (FL) = 0, and Argument length (AL) = 64. 2001:db8:b1:f123:: bound to the End.X behavior for its local IGP adjacency 123 with the NEXT-CSID flavor is instantiated from LIB with Locator-Block length (LBL) = 48 (Locator-Block value 0x20010db800b1), Locator-Node length (LNL) = 0, Function length (FL) = 16 (Function value 0xf123), and Argument length (AL) = 64. For SID 2001:db8:b1:10::, Node 10 would install the FIB entry 2001:db8:b1:10::/64 bound the End SID with the NEXT-CSID flavor. For SID 2001:db8:b1:f123::, Node 10 would install the FIB entry 2001:db8:b1:f123::/64 bound the End.X SID for adjacency 123 with the NEXT-CSID flavor. In addition, Node 10 may also install the combined FIB entry 2001:db8:b1:10:f123::/80 bound the End.X SID for adjacency 123 with the NEXT-CSID flavor. As another example, let us consider an SR segment endpoint node 20 instantiating the following two REPLACE-CSID flavor SIDs according to the CSID length, Locator-Block length, and GIB/LIB recommendations in this section. 2001:db8:b2:20:1:: from GIB with Locator-Block length (LBL) = 48, Locator-Node length (LNL) = 16, Function length (FL) = 16, Argument length (AL) = 48, and bound to the End behavior with the REPLACE-CSID flavor. 2001:db8:b2:20:123:: from GIB with Locator-Block length (LBL) = 48, Locator-Node length (LNL) = 16, Function length (FL) = 16, Argument length (AL) = 48, and bound to the End.X behavior for its local IGP adjacency 123 with the REPLACE-CSID flavor. For SID 2001:db8:b2:20:1::, Node 20 would install the FIB entry 2001:db8:b2:20:1::/80 bound the End SID with the REPLACE-CSID flavor. For SID 2001:db8:b2:20:123::, Node 20 would install the FIB entry 2001:db8:b2:20:123::/80 bound the End.X SID for adjacency 123 with the REPLACE-CSID flavor.
SR Source Node An SR source node may learn from a control plane protocol (see ) or local configuration the SIDs that it can use in a segment list, along with their respective SRv6 endpoint behavior, structure, and any other relevant attribute (e.g., the set of L3 adjacencies associated with an End.X SID).
SID Validation for Compression As part of the compression process or as a preliminary step, the SR source node MUST validate the SID structure of each SID of this document in the segment list. The SR source node does so regardless of whether the segment list is explicitly configured, locally computed, or advertised by a controller (e.g., via BGP or PCEP ). A SID structure is valid for compression if it meets all the following conditions. The Locator-Block length is not 0. The sum of the Locator-Node length and Function length is not 0. The Argument length is equal to 128-LBL-LNL-FL. When compressing a SID list, the SR source node MUST treat an invalid SID structure as unknown. A SID with an unknown SID structure is incompressible. discusses how the SIDs of this document and their structure can be advertised to the SR source node through various control plane protocols. The SID structure may also be learned through configuration or other management protocols. The details of such mechanisms are outside the scope of this document.
Segment List Compression An SR source node MAY compress a SID list when it includes NEXT-CSID and/or REPLACE-CSID flavor SIDs to reduce the packet header length. It is out of the scope of this document to describe the mechanism through which an uncompressed SID list is derived. As a general guidance for implementation or future specification, such a mechanism should aim to select the combination of SIDs that would result in the shortest compressed SID list. For example, by selecting a CSID flavor SID over an equivalent non-CSID flavor SID or by consistently selecting SIDs of the same CSID flavor within each routing domain. The SID list that the SR source node pushes onto the packet MUST comply with the rules in and and express the same list of segments as the original SID list. If these rules are not followed, the packet may get dropped or misrouted. If an SR source node chooses to compress the SID list, one method is described below for illustrative purposes. Any other method producing a compressed SID list of equal or shorter length than the uncompressed SID list MAY be used. This method walks the uncompressed SID list and compresses each series of consecutive NEXT-CSID flavor SIDs and each series of consecutive REPLACE-CSID flavor SIDs. When the compression method encounters a series of one or more consecutive compressible NEXT-CSID flavor SIDs, it compresses the series as follows. A SID with the NEXT-CSID flavor is compressible if its structure is known to the SR source node and its Argument value is 0.
When the compression method encounters a series of REPLACE-CSID flavor SIDs of the same CSID length in the uncompressed SID list, it compresses the series as per the following high-level pseudo code. A compression checking function ComCheck(F, S) is defined to check if two SIDs F and S share the same SID structure and Locator-Block value, and if S has either no Argument or an Argument with value 0. If the check passes, then ComCheck(F,S) returns true.
In all remaining cases (i.e., when the compression method encounters a SID in the uncompressed SID list that is not handled by any of the previous subroutines), it pushes this SID as is onto the compressed SID list. Regardless of how a compressed SID list is produced, the SR source node writes it in the IPv6 packet as described in Sections 4.1 and 4.1.1 of . The text is reproduced below for reference.
A source node steers a packet into an SR Policy. If the SR Policy results in a Segment List containing a single segment, and there is no need to add information to the SRH flag or add TLV; the DA is set to the single Segment List entry, and the SRH MAY be omitted. When needed, the SRH is created as follows: The Next Header and Hdr Ext Len fields are set as specified in . The Routing Type field is set to 4. The DA of the packet is set with the value of the first segment. The first element of the SRH Segment List is the ultimate segment. The second element is the penultimate segment, and so on. The Segments Left field is set to n-1, where n is the number of elements in the SR Policy. The Last Entry field is set to n-1, where n is the number of elements in the SR Policy. TLVs (including HMAC) may be set according to their specification. The packet is forwarded toward the packet's Destination Address (the first segment). When a source does not require the entire SID list to be preserved in the SRH, a reduced SRH may be used. A reduced SRH does not contain the first segment of the related SR Policy (the first segment is the one already in the DA of the IPv6 header), and the Last Entry field is set to n-2, where n is the number of elements in the SR Policy.
Rules for segment lists containing NEXT-CSID flavor SIDs If a Destination Option header would follow an SRH with a segment list of more than one segment compressed as a single NEXT-CSID container, the SR source node MUST NOT omit the SRH. When the last Segment List entry (index 0) in the SRH is a NEXT-CSID container representing more than one segment, the PSP operation is performed at the segment preceding the first segment of this NEXT-CSID container in the segment list. If the PSP behavior should be performed at the penultimate segment along the path instead, the SR source node MUST NOT compress the ultimate SID of the SID list into a NEXT-CSID container. If a Destination Option header would follow an SRH with a last Segment List entry being a NEXT-CSID container representing more than one segment, the SR source node MUST ensure that the PSP operation is not performed before the penultimate SR segment endpoint node along the path. When the Argument of a NEXT-CSID container is not used to full capacity, the remaining least significant bits of that Argument MUST be set to 0.
Rules for segment lists containing REPLACE-CSID flavor SIDs All SIDs compressed in a REPLACE-CSID sequence MUST share the same Locator-Block and the same compression scheme. All SIDs except the last one in a CSID sequence for REPLACE-CSID MUST have the REPLACE-CSID flavor. If the last REPLACE-CSID container is fully filled (i.e., the last CSID is at position 0 in the REPLACE-CSID container) and the last SID in the CSID sequence is not the last segment in the segment list, the last SID in the CSID sequence MUST NOT have the REPLACE-CSID flavor. When a REPLACE-CSID flavor CSID is present as the last SID in a container that is not the last Segment List entry (index 0) in the SRH, the next element in the SID list MUST be a REPLACE-CSID container in packed format carrying at least one CSID. The SR source node determines the compression scheme of REPLACE-CSID flavor SIDs as follows. When receiving a SID advertisement for a REPLACE-CSID flavor SID with LNL=16, FL=0, AL=128-LBL-NL-FL, and the value of the Argument is all 0, the SR source node marks both the SID and its locator as using 16-bit compression. All other SIDs allocated from this locator with LNL=16, FL=16, AL=128-LBL-NL-FL, and the value of the Argument is all 0 are also marked as using 16-bit compression. When receiving a SID advertisement for a REPLACE-CSID flavor SID with LNFL=32, AL=128-LBL-NL-FL, and the value of the Argument is all 0, the SR source node marks both the SID and its locator as using 32-bit compression.
Upper-Layer Checksums The Destination Address used in the IPv6 pseudo-header (Section 8.1 of ) is that of the ultimate destination. At the SR source node, that address will be the Destination Address as it is expected to be received by the ultimate destination. When the last element in the compressed SID list is a CSID container, this address can be obtained from the last element in the uncompressed SID list or by repeatedly applying the segment behavior as described in . This applies regardless of whether an SRH is present in the IPv6 packet or omitted. At the ultimate destination(s), that address will be in the Destination Address field of the IPv6 header.
Inter-Domain Compression Some SRv6 traffic may need to cross multiple routing domains, such as different Autonomous Systems (ASes) or different routing areas within an SR domain. Different routing domains may use different addressing schema and Locator-Blocks. A property of a CSID sequence is that all CSIDs in the sequence share the same Locator-Block. Therefore, a segment list that spans across multiple routing domains using different Locator-Blocks may need a separate CSID sequence for each domain. This section defines a solution to improve the efficiency of CSID compression in multi-domain environments by enabling a CSID sequence to combine CSIDs having different Locator-Blocks. The solution leverages two new SRv6 endpoint behaviors, "Endpoint with SRv6 Prefix Swap" ("End.PS" for short) and "Endpoint with L3 cross-connect and SRv6 Prefix Swap" ("End.XPS" for short), that enable modifying the Locator-Block for the next CSID in the CSID sequence at the routing domain boundary.
End.PS: Prefix Swap The End.PS behavior is a variant of the End behavior that modifies the Locator-Block of the active CSID sequence. This document defines the End.PS behavior with the NEXT-CSID flavor and the End.PS behavior with the REPLACE-CSID flavor. An End.PS SID is used to transition to a new Locator-Block when the routing domain boundary is on the SR segment endpoint node. Each instance of an End.PS SID is associated with a target Locator-Block B2/m, where B2 is an IPv6 address prefix and m is the associated prefix length. The target Locator-Block is a local property of the End.PS SID on the SR segment endpoint node. The means by which an SR source node learns the target Locator-Block associated with an End.PS SID are outside the scope of this document. As examples, it could be learnt via configuration or signaled by a controller.
End.PS with NEXT-CSID When processing an IPv6 packet that matches a FIB entry locally instantiated as an End.PS SID with the NEXT-CSID flavor and associated with the target Locator-Block B2/m, the SR segment endpoint node applies the procedure specified in with the lines N05 to N06 replaced as follows.
End.PS with REPLACE-CSID When processing an IPv6 packet that matches a FIB entry locally instantiated as an End.PS SID with the REPLACE-CSID flavor and associated with the target Locator-Block B2/m, the SR segment endpoint node applies the procedure specified in with the line R20 replaced as follows.
End.XPS: L3 Cross-Connect and Prefix Swap The End.XPS behavior is a variant of the End.X behavior that modifies the Locator-Block of the active CSID sequence. This document defines the End.XPS behavior with the NEXT-CSID flavor and the End.XPS behavior with the REPLACE-CSID flavor. An End.XPS SID is used to transition to a new Locator-Block when the routing domain boundary is on a link adjacent to the SR segment endpoint node. Each instance of an End.XPS SID is associated with a target Locator-Block B2/m and a set, J, of one or more L3 adjacencies. The target Locator-Block and set of adjacencies are local properties of the End.XPS SID on the SR segment endpoint node. The means by which an SR source node learns the target Locator-Block associated with an End.XPS SID are outside the scope of this document. As examples, it could be learnt via configuration or signaled by a controller.
End.XPS with NEXT-CSID When processing an IPv6 packet that matches a FIB entry locally instantiated as an End.XPS SID with the NEXT-CSID flavor and associated with the target Locator-Block B2/m, the SR segment endpoint node applies the procedure specified in with the lines N05 to N06 (of the pseudocode in ) replaced as follows.
End.XPS with REPLACE-CSID When processing an IPv6 packet that matches a FIB entry locally instantiated as an End.XPS SID with the REPLACE-CSID flavor and associated with the target Locator-Block B2/m, the SR segment endpoint node applies the procedure specified in with the line R20 (of the pseudocode in ) replaced as follows.
Control Plane Section 8 of provides an overview of the control plane protocols used for signaling of the SRv6 endpoint behaviors introduced by that document, including the base SRv6 endpoint behaviors that are extended in the present document. The CSID-flavored behaviors introduced by this document are advertised in the same manner as their base SRv6 endpoint behaviors using the SRv6 extensions for various routing protocols, such as IS-IS OSPFv3 BGP , , BGP-LS PCEP The SR segment endpoint node MUST set the SID Argument bits to 0 when advertising a locally instantiated SID of this document in the routing protocol (e.g., IS-IS , OSPF , or BGP-LS ). Signaling the SRv6 SID Structure is REQUIRED for all the SIDs introduced in this document. It is used by an SR source node to compress a SID list as described in . The node initiating the SID advertisement MUST set the length values in the SRv6 SID Structure to match the format of the SID on the SR segment endpoint node. For example, for a SID of this document instantiated from a /48 SRv6 SID block and a /64 Locator, and having a 16-bit Function, the SRv6 SID Structure advertisement carries the following values. Locator-Block length: 48 Locator-Node length: 16 Function length: 16 Argument length: 48 (= 128-48-16-16) A local CSID may be advertised in the control plane individually and/or in combination with a global CSID instantiated on the same SR segment endpoint node, with the End behavior, and the same Locator-Block and flavor as the local CSID. A combined global and local CSID is advertised as follows. The SID Locator-Block is that shared by the global and local CSIDs The SID Locator-Node is that of global CSID The SID Function is that of the local CSID The SID Argument length is equal to 128-LBL-LNL-FL and the SID Argument value is 0 All other attributes of the SID (e.g., SRv6 endpoint behavior or algorithm) are those of the local CSID The local CSID combined advertisement is needed in particular for control plane protocols mandating that the SID is a subnet of a locator advertised in the same protocol (e.g., Section 8 of and Section 9 of for advertising Adjacency SIDs in IS-IS and OSPFv3, respectively). For a segment list computed by a controller and signaled to an SR source node (e.g., via BGP or PCEP ), the controller provides the ordered segment list comprising the uncompressed SIDs, with their respective behavior and structure, to the SR source node. The SR source node may then compress the SID list as described in . When a node that does not support this specification receives an advertisement of a SID of this document, it handles it as described in the corresponding control plane specification (e.g., Sections 7.2, 8.1, and 8.2 of , Sections 8, 9.1, and 9.2 of , and Section 3.1 of ).
Operational Considerations
Flavor, Block, and CSID Length SRv6 is intended for use in a variety of networks that require different prefix lengths and SID numbering spaces. Each of the two flavors introduced in this document comes with its own recommendations for Locator-Block and CSID length, as specified in and . These flavors are best suited for different environments, depending on the requirements of the network. For instance, larger CSID lengths may be more suitable for networks requiring ample SID numbering space, while smaller CSID lengths are better for compression efficiency. The two compression flavors allow the compressed segment list encoding to adapt to a range of requirements, with support for multiple compression levels. Network operators can choose the flavor that best suits their use case, deployment design, and network scale. Both CSID flavors can coexist in the same SR domain, on the same SR segment endpoint node, and even in the same segment list. However, operators should generally avoid instantiating SIDs of different CSID flavors within the same routing domain or Locator-Block since these SIDs have different length and allocation recommendations (see , , and ). In a multi-domain deployment, different flavors may be used in different routing domains of the SR domain. A deployment should use consistent Locator-Block lengths and CSID lengths for all SIDs within a routing domain. Heterogeneous lengths, while possible, may impact the compression efficiency. The compressed segment list encoding works with various Locator-Block allocations. For example, each routing domain within the SR domain can be allocated a /48 Locator-Block from a global IPv6 block available to the operator, or from a prefix allocated to SRv6 SIDs as discussed in Section 5 of .
GIB/LIB Usage GIB and LIB usage is a local implementation and/or configuration decision, however, some guidelines for determining usage for specific SRv6 endpoint behaviors and recommendations are provided. The GIB number space is shared among all SR segment endpoint nodes using SRv6 locators under a Locator-Block space. The more SIDs assigned from this space, per node, the faster it is exhausted. Therefore, its use is prioritized for global segments, such as SIDs that identify a node. The LIB number space is unique per node. Each node can fully utilize the entire LIB number space without consideration of assignments at other nodes. Therefore, its use is prioritized for local segments, such as SIDs that identify services (of which there may be many) at nodes, cross-connects, or adjacencies. While a longer CSID length permits more flexibility in which SRv6 endpoint behaviors may be assigned from the GIB; it also reduces the compression efficiency. Given the previous Locator-Block and CSID length recommendations, the following GIB/LIB usage is recommended: NEXT-CSID: GIB: End LIB: End.X, End.T, End.DT4/6/46/2U/2M, End.DX4/6/2/2V (including large-scale pseudowire), End.B6.Encaps, End.B6.Encaps.Red, End.BM, End.PS, and End.XPS REPLACE-CSID: GIB: End, End.X, End.T, End.DT4/6/46/2U/2M, End.DX4/6/2/2V, End.B6.Encaps, End.B6.Encaps.Red, End.BM, End.PS, and End.XPS LIB: End.DX2/2V for large-scale pseudowire Any other allocation is possible but may lead to a suboptimal use of the CSID numbering space.
Pinging a SID An SR source node may ping an SRv6 SID by sending an ICMPv6 echo request packet destined to the SRv6 SID. The SR source node may ping the target SID with a SID list comprising only that target SID, or with a longer one that comprises two or more SIDs. In that case, the target SID is the last element in the SID list. This operation is illustrated in Appendix A.1.2 of . When pinging a SID of this document the SR source node MUST construct the IPv6 packet as described in , including computing the ICMPv6 checksum as described in . In particular, when pinging a SID of this document with a SID list comprising only the target SID, the SR source node places the SID with Argument value 0 in the destination address of the ICMPv6 echo request and computes the ICMPv6 checksum using this SID as the destination address in the IPv6 pseudo-header. The Argument value 0 allows the SID SR segment endpoint node () to identify itself as the ultimate destination of the packet and process the ICMPv6 payload. Therefore, any existing IPv6 ping implementation can originate ICMP echo requests to a NEXT-CSID or REPLACE-CSID flavor SID with a SID list comprising only the target SID, provided that the user ensures that the SID Argument is 0.
ICMP Error Processing When an IPv6 node encounters an error while processing a packet, it may report that error by sending an IPv6 error message to the packet source with an enclosed copy of the invoking packet. For the source of an invoking packet to process the ICMP error message, the ultimate destination address of the IPv6 header may be required. Section 5.4 of defines the logic that an SR source node follows to determine the ultimate destination of an invoking packet containing an SRH. For an SR source node that supports the compressed segment list encoding defined in this document, the logic to determine the ultimate destination is generalized as follows. If the destination address of the invoking IPv6 packet matches a known SRv6 SID, modify the invoking IPv6 packet by applying the SRv6 endpoint behavior associated with the matched SRv6 SID; Repeat until the application of the SRv6 endpoint behavior would result in the processing of the upper-layer header. The destination address of the resulting IPv6 packet may be used as the ultimate destination of the invoking IPv6 packet. Since the SR source node that needs to determine the ultimate destination is the same node that originally built the SID list in the invoking packet, it can perform this operation for all the SIDs in the packet.
Upper Layer Checksum Considerations Upper layer checksums are computed by the originator of an IPv6 packet and verified by the ultimate destination(s) as it processes the upper layer protocol. As specified in , SR source nodes originating TCP/UDP packets ensure that the upper layer checksum is correctly calculated based on the ultimate destination of the session, which may be different from the address placed in the IPv6 destination address. Such SR source nodes leveraging TCP/UDP offload engines may require enhancements to convey the ultimate destination address. These implementation enhancements are outside the scope of this document. It was reported that some network node implementations, including middleboxes such as packet sniffers and one software router implementation, may attempt to verify the upper layer checksum of transit IPv6 packets. These nodes, if deployed inside the SR domain, may fail to verify the upper layer checksum of transit SRv6 traffic, possibly resulting in dropped packets or in the inability to carry out their function. Making these implementations SRv6 aware in general or CSID aware in particular is out of the scope of this document.
Implementation Status RFC-Editor: Please clean up the references cited by this section before publication. This section records the status of known implementations of the protocol defined by this specification at the time of posting of this Internet-Draft, and is based on a proposal described in . The description of implementations in this section is intended to assist the IETF in its decision processes in progressing drafts to RFCs. Please note that the listing of any individual implementation here does not imply endorsement by the IETF. Furthermore, no effort has been spent to verify the information presented here that was supplied by IETF contributors. This is not intended as, and must not be construed to be, a catalog of available implementations or their features. Readers are advised to note that other implementations may exist. According to , "this will allow reviewers and working groups to assign due consideration to documents that have the benefit of running code, which may serve as evidence of valuable experimentation and feedback that have made the implemented protocols more mature. It is up to the individual working groups to use this information as they see fit". This section is provided in compliance with the SPRING working group policies ().
Cisco Systems Cisco Systems reported the following implementations of the SR segment endpoint node NEXT-CSID flavor () and the SR source node efficient SID list encoding () for NEXT-CSID flavor SIDs. These are used as part of its SRv6 TI-LFA, micro-loop avoidance, and traffic engineering functionalities. Cisco NCS 540 Series routers running IOS XR 7.3.x or above Cisco NCS 560 Series routers running IOS XR 7.6.x or above Cisco NCS 5500 Series routers running IOS XR 7.3.x or above Cisco NCS 5700 Series routers running IOS XR 7.5.x or above Cisco 8000 Series routers running IOS XR 7.5.x or above Cisco ASR 9000 Series routers running IOS XR 7.5.x or above At the time of this report, all the implementations listed above are in production and follow the specification in the latest version of this document, including all the "MUST" and "SHOULD" clauses for the NEXT-CSID flavor. This report was last updated on January 11, 2023.
Huawei Technologies Huawei Technologies reported the following implementations of the SR segment endpoint node REPLACE-CSID flavor (). These are used as part of its SRv6 TI-LFA, micro-loop avoidance, and traffic engineering functionalities. Huawei ATN8XX,ATN910C,ATN980B routers running VRPV800R021C00 or above. Huawei CX600-M2 routers running VRPV800R021C00 or above. Huawei NE40E,ME60-X1X2,ME60-X3X8X16 routers running VRPV800R021C00 or above. Huawei NE5000E,NE9000 routers running VRPV800R021C00 or above. Huawei NCE-IP Controller running V1R21C00 or above. At the time of this report, all the implementations listed above are in production and follow the specification in the latest version of this document, including all the "MUST" and "SHOULD" clauses for the REPLACE-CSID flavor. This report was last updated on January 11, 2023.
Nokia Nokia reported the following implementations () of the SR segment endpoint node NEXT-CSID flavor (). These are used as part of its shortest path forwarding (in algorithm 0 and Flex-Algo), remote and TI-LFA repair tunnel, and Traffic Engineering functionalities. Nokia 7950 XRS 20/20e routers running SROS Release 22.10 or above Nokia 7750 SR-12e routers running SROS Release 22.10 or above Nokia 7750 SR-7/12 routers running SROS Release 22.10 or above Nokia 7750 SR-7s/14s routers running SROS Release 22.10 or above Nokia 7750 SR-1/1s/2s routers running SROS Release 22.10 or above At the time of this report, all the implementations listed above are in production and follow the specification in the latest version of this document, including all the "MUST" and "SHOULD" clauses for the NEXT-CSID flavor. This report was last updated on February 3, 2023.
Arrcus Arrcus reported the following implementations of the SR segment endpoint node NEXT-CSID flavor (). These are used as part of its SRv6 shortest path forwarding (in algorithm 0 and Flex-Algo), TI-LFA, micro-loop avoidance and Traffic Engineering functionalities. Arrcus running on Ufi Space routers S9510-28DC, S9710-76D, S9600-30DX and S9700-23D with ArcOS v5.2.1 or above Arrcus running n Ufi Space routers S9600-72XC and S9700-53DX with ArcOS v5.1.1D or above Arrcus running on Quanta router IXA and IXAE with ArcOS v5.1.1D or above At the time of this report, all the implementations listed above are in production and follow the specification in the latest version of this document, including all the "MUST" and "SHOULD" clauses for the NEXT-CSID flavor. This report was last updated on March 11, 2023.
Juniper Networks Juniper Networks reported the following implementations of the SR segment endpoint node NEXT-CSID flavor (). These are used as part of its SRv6 shortest path forwarding (in algorithm 0 and Flex-Algo), TI-LFA, micro-loop avoidance, and Traffic Engineering functionalities. Juniper release 23.3 onwards supports this functionality. At the time of this report, all the implementations listed above are in development and follow the specification in the latest version of this document, including all the "MUST" and "SHOULD" clauses for the NEXT-CSID flavor. This report was last updated on May 30, 2023.
Marvell Marvell reported support in the Marvell Prestera Packet Processor for the SR segment endpoint node NEXT-CSID flavor () and REPLACE-CSID flavor (). This report was last updated on February 15, 2023.
Broadcom Broadcom reported the following implementations of the SR segment endpoint node NEXT-CSID flavor () and REPLACE-CSID flavor (). These are used as part of its SRv6 TI-LFA, micro-loop avoidance, and traffic engineering functionalities. All implementation of the following list is in general availability for customers using BCM SDK 6.5.26 or above. 88850 (Jericho2c+) series 88690 (Jericho2) series 88800 (Jericho2c) series 88480 (Qunran2a) series 88280 (Qunran2u) series 88295 (Qunran2n) series 88830 (Jericho2x) series At the time of this report, all the implementations listed above are in production and follow the specification in the latest version of this document, including all the "MUST" and "SHOULD" clauses for the NEXT-CSID and REPLACE-CSID flavors. For 78900 (Tomahawk) series-related support, please contact the Broadcom team. This report was last updated on February 21, 2023.
ZTE Corporation ZTE Corporation reported the following implementations of the SR segment endpoint node REPLACE-CSID flavor (). These are used as part of its SRv6 TI-LFA, micro-loop avoidance, and traffic engineering functionalities. ZTE M6000-18S(BRAS), M6000-8S Plus(BRAS) routers running V5.00.10.09 or above. ZTE M6000-18S(SR), M6000-8S Plus(SR) routers running V5.00.10.80 or above. ZTE T8000-18 routers running V5.00.10.07 or above. This report was last updated on March 29, 2023.
New H3C Technologies New H3C Technologies reported the following implementations of the SR segment endpoint node REPLACE-CSID flavor (). These are used as part of its SRv6 TI-LFA, micro-loop avoidance, and traffic engineering functionalities. H3C CR16000-F, SR8800-X routers running Version 7.1.075 or above. H3C CR18000, CR19000 routers running Version 7.1.071 or above. This report was last updated on March 29, 2023.
Ruijie Network Ruijie Network reported the following implementations of the SR segment endpoint node REPLACE-CSID flavor (). These are used as part of its SRv6 TI-LFA, micro-loop avoidance, and traffic engineering functionalities. RUIJIE RG-N8018-R, RG-N8010-R routers running N8000-R_RGOS 12.8(3)B0801 or above. This report was last updated on March 29, 2023.
Ciena Ciena reported the following implementations of the SR segment endpoint node NEXT-CSID flavor (). These are used as part of its shortest path forwarding (in algorithm 0 and Flex-Algo), remote and TI-LFA repair tunnel, and Traffic Engineering functionalities. The following platforms support implementation of the above. Ciena 5162, 5164, 5166, 5168 routers running SAOS 10.10 or above Ciena 8110, 8112, 8190 routers running SAOS 10.10 or above At the time of this report, all the implementations listed above are in production and follow the specification in the latest version of this document, including all the "MUST" and "SHOULD" clauses for the NEXT-CSID flavor. This report was last updated on February 6, 2024.
Centec Centec reported the following implementations of the SR segment endpoint node REPLACE-CSID flavor (). These are used as part of its SRv6 TI-LFA, micro-loop avoidance, and traffic engineering functionalities. All implementation of the following list is in general availability for customers using Centec SDK 5.6.8 or above. CTC7132 (TsingMa) Series CTC8180 (TsingMa.MX) Series This report was last updated on February 14, 2024.
Open-Source The authors found the following open-source implementations of the SR segment endpoint node NEXT-CSID flavor (). The Linux kernel, version 6.1 The Software for Open Networking in the Cloud (SONiC), version 202212 , and Switch Abstraction Interface (SAI), version 1.9.0 The Vector Packet Processor (VPP), version 20.05 A generic P4 implementation The authors found the following open-source implementations of the SR segment endpoint node REPLACE-CSID flavor (). ONOS and P4 Programmable Switch based Open SRv6 Project This section was last updated on January 11, 2023.
Interoperability Reports
EANTC 2024 In April 2024, the European Advanced Networking Test Center (EANTC) successfully validated multiple implementations of SRv6 NEXT-CSID flavor (a.k.a., SRv6 uSID) . The participating vendors included Arista, Ciena, Cisco, Ericsson, H3C, Huawei, Juniper, Keysight, Nokia, and ZTE.
Bell Canada / Ciena 2023 Bell Canada is currently evaluating interoperability between Ciena and Cisco implementations of the NEXT-CSID flavor defined in this document. Further information will be added to this section when the evaluation is complete.
EANTC 2023 In April 2023, the European Advanced Networking Test Center (EANTC) successfully validated multiple implementations of SRv6 NEXT-CSID flavor (a.k.a., SRv6 uSID) . The participating vendors included Arista, Arrcus, Cisco, Huawei, Juniper, Keysight, Nokia, and Spirent.
China Mobile 2020 In November 2020, China Mobile successfully validated multiple interoperable implementations of the NEXT-CSID and REPLACE-CSID flavors defined in this document. This testing covered two different implementations of the SRv6 endpoint flavors defined in this document: Hardware implementation in Cisco ASR 9000 running IOS XR Software implementation in Cisco IOS XRv9000 virtual appliance Hardware implementation in Huawei NE40E and NE5000E running VRP The interoperability testing consisted of a packet flow sent by an SR source node N0 via an SR traffic engineering policy with a segment list <S1, S2, S3, S4, S5, S6, S7>, where S1..S7 are SIDs instantiated on SR segment endpoint nodes N1..N7, respectively.
N0 N1 N2 N3 N4 N5 N6 N7 (S1) (S2) (S3) (S4) (S5) (S6) (S7)
N0 is a generic packet generator. N1, N2, and N3 are Huawei routers. N4, N5, and N6 are Cisco routers. N7 is a generic traffic generator acting as a packet receiver. The SR source node N0 steers the packets onto the SR policy by setting the IPv6 destination address and creating an SRH (as described in Section 4.1 of ) using a compressed segment list encoding. The length of the compressed segment list encoding varies for each scenario. All SR segment endpoint nodes execute a variant of the End behavior: regular End behavior (as defined in Section 4.1 of ), End behavior with NEXT-CSID flavor, and End behavior with REPLACE-CSID flavor. The variant being used at each SR segment endpoint node varies for each scenario. The interoperability was validated for the following scenarios: Scenario 1: S1 and S2 are associated with the End behavior with the REPLACE-CSID flavor S3 is associated with the regular End behavior (no flavor) S4, S5, and S6 are associated with the End behavior with the NEXT-CSID flavor The SR source node imposes a compressed segment list encoding of 3 SIDs. Scenario 2: S1, S2..., S6 are associated with the End behavior with the NEXT-CSID flavor The SR source node imposes a compressed segment list encoding of 2 SIDs. Scenario 3: S1, S2..., S6 are associated with the End behavior with the REPLACE-CSID flavor The SR source node imposes a compressed segment list encoding of 3 SIDs.
Applicability to other SRv6 Endpoint Behaviors Future documents may extend the applicability of the NEXT-CSID and REPLACE-CSID flavors to other SRv6 endpoint behaviors. For an SRv6 endpoint behavior that can be used before the last position of a segment list, a CSID flavor is defined by reproducing the same logic as described in and of this document to determine the next SID in the SID list.
Security Considerations Section 8 of discusses the security considerations for Segment Routing. Section 5 of describes the intra-SR-domain deployment model and how to secure it. Section 7 of describes the threats applicable to SRv6 and how to mitigate them. Section 9 of discusses the security considerations applicable to the SRv6 network programming framework, as well as the SR source node and SR segment endpoint node behaviors that it defines. This document introduces two new flavors for some of the SRv6 endpoint behaviors defined in and a method by which an SR source node may leverage the SIDs of these flavors to produce a compressed segment list encoding. This document also introduces two new SRv6 endpoint behaviors, End.PS and End.XPS, to preserve the efficiency of CSID compression in multi-domain environments. An SR source node constructs an IPv6 packet with a compressed segment list encoding as defined in Sections 3.1 and 4.1 of and Section 5 of . The paths that an SR source node may enforce using a compressed segment list encoding are the same, from a topology and service perspective, as those that an SR source node could enforce using the SIDs of . An SR segment endpoint node processes an IPv6 packet matching a locally instantiated SID as defined in , with the pseudocode modifications in Section 4 of this document. These modifications change how the SR segment endpoint node determines the next SID in the packet, but not the semantic of either the active or the next SID. For example, an adjacency segment instantiated with the End.X behavior remains an adjacency segment regardless of whether it uses the base End.X behavior defined in Section 4.2 of or a CSID flavor of that behavior. This document does not introduce any new SID semantic. Any other transit node processes the packet as described in Section 4.2 of . This document defines a new method of encoding the SIDs inside a SID list at the SR source node () and decoding them at the SR segment endpoint node ( and ), but it does not change how the SID list itself is encoded in the IPv6 packet nor the semantic of any segment that it comprises. Therefore, this document is subject to the same security considerations that are discussed in , , and .
IANA Considerations
SRv6 Endpoint Behaviors This I-D. requests the IANA to update the reference of the following registrations from the "SRv6 Endpoint Behaviors" registry under the top-level "Segment Routing" registry-group (https://www.iana.org/assignments/segment-routing/) with the RFC number of this document once it is published, and transfer change control to the IETF. Value Description Reference 43 End with NEXT-CSID This I-D. 44 End with NEXT-CSID & PSP This I-D. 45 End with NEXT-CSID & USP This I-D. 46 End with NEXT-CSID, PSP & USP This I-D. 47 End with NEXT-CSID & USD This I-D. 48 End with NEXT-CSID, PSP & USD This I-D. 49 End with NEXT-CSID, USP & USD This I-D. 50 End with NEXT-CSID, PSP, USP & USD This I-D. 52 End.X with NEXT-CSID This I-D. 53 End.X with NEXT-CSID & PSP This I-D. 54 End.X with NEXT-CSID & USP This I-D. 55 End.X with NEXT-CSID, PSP & USP This I-D. 56 End.X with NEXT-CSID & USD This I-D. 57 End.X with NEXT-CSID, PSP & USD This I-D. 58 End.X with NEXT-CSID, USP & USD This I-D. 59 End.X with NEXT-CSID, PSP, USP & USD This I-D. 85 End.T with NEXT-CSID This I-D. 86 End.T with NEXT-CSID & PSP This I-D. 87 End.T with NEXT-CSID & USP This I-D. 88 End.T with NEXT-CSID, PSP & USP This I-D. 89 End.T with NEXT-CSID & USD This I-D. 90 End.T with NEXT-CSID, PSP & USD This I-D. 91 End.T with NEXT-CSID, USP & USD This I-D. 92 End.T with NEXT-CSID, PSP, USP & USD This I-D. 93 End.B6.Encaps with NEXT-CSID This I-D. 94 End.B6.Encaps.Red with NEXT-CSID This I-D. 95 End.BM with NEXT-CSID This I-D. 96 End.PS with NEXT-CSID This I-D. 97 End.XPS with NEXT-CSID This I-D. 101 End with REPLACE-CSID This I-D. 102 End with REPLACE-CSID & PSP This I-D. 103 End with REPLACE-CSID & USP This I-D. 104 End with REPLACE-CSID, PSP & USP This I-D. 105 End.X with REPLACE-CSID This I-D. 106 End.X with REPLACE-CSID & PSP This I-D. 107 End.X with REPLACE-CSID & USP This I-D. 108 End.X with REPLACE-CSID, PSP & USP This I-D. 109 End.T with REPLACE-CSID This I-D. 110 End.T with REPLACE-CSID & PSP This I-D. 111 End.T with REPLACE-CSID & USP This I-D. 112 End.T with REPLACE-CSID, PSP & USP This I-D. 114 End.B6.Encaps with REPLACE-CSID This I-D. 115 End.BM with REPLACE-CSID This I-D. 116 End.DX6 with REPLACE-CSID This I-D. 117 End.DX4 with REPLACE-CSID This I-D. 118 End.DT6 with REPLACE-CSID This I-D. 119 End.DT4 with REPLACE-CSID This I-D. 120 End.DT46 with REPLACE-CSID This I-D. 121 End.DX2 with REPLACE-CSID This I-D. 122 End.DX2V with REPLACE-CSID This I-D. 123 End.DT2U with REPLACE-CSID This I-D. 124 End.DT2M with REPLACE-CSID This I-D. 127 End.B6.Encaps.Red with REPLACE-CSID This I-D. 128 End with REPLACE-CSID & USD This I-D. 129 End with REPLACE-CSID, PSP & USD This I-D. 130 End with REPLACE-CSID, USP & USD This I-D. 131 End with REPLACE-CSID, PSP, USP & USD This I-D. 132 End.X with REPLACE-CSID & USD This I-D. 133 End.X with REPLACE-CSID, PSP & USD This I-D. 134 End.X with REPLACE-CSID, USP & USD This I-D. 135 End.X with REPLACE-CSID, PSP, USP & USD This I-D. 136 End.T with REPLACE-CSID & USD This I-D. 137 End.T with REPLACE-CSID, PSP & USD This I-D. 138 End.T with REPLACE-CSID, USP & USD This I-D. 139 End.T with REPLACE-CSID, PSP, USP & USD This I-D. 140 End.PS with REPLACE-CSID This I-D. 141 End.XPS with REPLACE-CSID This I-D.
Acknowledgements The authors would like to thank Kamran Raza, Xing Jiang, YuanChao Su, Han Li, Yisong Liu, Martin Vigoureux, Joel Halpern, and Tal Mizrahi for their insightful feedback and suggestions. The authors would also like to thank Andrew Alston, Linda Dunbar, Adrian Farrel, Boris Hassanov, Alvaro Retana, and Gunter Van de Velde for their thorough review of this document.
&RFC8200; &RFC8402; &RFC8754; &RFC8986; &RFC2119; &RFC8174; &RFC7942; &RFC9252; &RFC9259; &RFC9350; &RFC9352; &RFC9513; &RFC9514; &RFC9602; &RFC9603; &I-D.ietf-idr-bgp-ls-sr-policy; &I-D.ietf-idr-sr-policy-safi; Concrete Mathematics: A Foundation for Computer Science SPRING Working Group Policies SPRING Working Group Chairs Segment Routing Configuration Guide for Cisco NCS 540 Series Routers Cisco Systems Segment Routing Configuration Guide for Cisco NCS 560 Series Routers Cisco Systems Segment Routing Configuration Guide for Cisco NCS 5500 Series Routers Cisco Systems Segment Routing Configuration Guide for Cisco NCS 5700 Series Routers Cisco Systems Segment Routing Configuration Guide for Cisco 8000 Series Routers Cisco Systems Segment Routing Configuration Guide for Cisco ASR 9000 Series Routers Cisco Systems Segment Routing and PCE User Guide Nokia Add NEXT-CSID support for SRv6 End behavior SONiC uSID Added new behaviors to support uSID instruction Srv6 cli reference FD.io SRv6 uSID (micro SID) implementation on P4 Stratum CMCC G-SRv6 Project Open Networking Foundation Open SRv6 Project Multi-Vendor MPLS SDN Interoperability Test Report 2023 European Advanced Networking Test Center (EANTC) Multi-Vendor MPLS SDN Interoperability Test Report 2024 European Advanced Networking Test Center (EANTC)
Complete pseudocodes The content of this section is purely informative rendering of the pseudocodes of with the modifications in this document. This rendering may not be used as a reference.
End with NEXT-CSID When processing the SRH of a packet matching a FIB entry locally instantiated as an End SID with the NEXT-CSID flavor:
max_LE) or (Segments Left > Last Entry+1)) { S10. Send an ICMP Parameter Problem to the Source Address with Code 0 (Erroneous header field encountered) and Pointer set to the Segments Left field, interrupt packet processing, and discard the packet. S11. } S12. Decrement IPv6 Hop Limit by 1. S13. Decrement Segments Left by 1. S14. Update IPv6 DA with Segment List[Segments Left]. S15. Submit the packet to the egress IPv6 FIB lookup for transmission to the new destination. ]]>
Before processing the Upper-Layer header or any IPv6 extension header other than Hop-by-Hop or Destination Option of a packet matching a FIB entry locally instantiated as an End SID with the NEXT-CSID flavor:
When processing the Upper-Layer header of a packet matching a FIB entry locally instantiated as an End SID with the NEXT-CSID flavor:
End.X with NEXT-CSID When processing the SRH of a packet matching a FIB entry locally instantiated as an End.X SID with the NEXT-CSID flavor:
max_LE) or (Segments Left > Last Entry+1)) { S10. Send an ICMP Parameter Problem to the Source Address with Code 0 (Erroneous header field encountered) and Pointer set to the Segments Left field, interrupt packet processing, and discard the packet. S11. } S12. Decrement IPv6 Hop Limit by 1. S13. Decrement Segments Left by 1. S14. Update IPv6 DA with Segment List[Segments Left]. S15. Submit the packet to the IPv6 module for transmission to the new destination via a member of J. ]]>
Before processing the Upper-Layer header or any IPv6 extension header other than Hop-by-Hop or Destination Option of a packet matching a FIB entry locally instantiated as an End.X SID with the NEXT-CSID flavor:
When processing the Upper-Layer header of a packet matching a FIB entry locally instantiated as an End.X SID with the NEXT-CSID flavor:
End.T with NEXT-CSID When processing the SRH of a packet matching a FIB entry locally instantiated as an End.T SID with the NEXT-CSID flavor:
max_LE) or (Segments Left > Last Entry+1)) { S10. Send an ICMP Parameter Problem to the Source Address with Code 0 (Erroneous header field encountered) and Pointer set to the Segments Left field, interrupt packet processing, and discard the packet. S11. } S12. Decrement IPv6 Hop Limit by 1. S13. Decrement Segments Left by 1. S14. Update IPv6 DA with Segment List[Segments Left]. S15.1. Set the packet's associated FIB table to T. S15.2. Submit the packet to the egress IPv6 FIB lookup for transmission to the new destination. ]]>
Before processing the Upper-Layer header or any IPv6 extension header other than Hop-by-Hop or Destination Option of a packet matching a FIB entry locally instantiated as an End.T SID with the NEXT-CSID flavor:
When processing the Upper-Layer header of a packet matching a FIB entry locally instantiated as an End.T SID with the NEXT-CSID flavor:
End.B6.Encaps with NEXT-CSID When processing the SRH of a packet matching a FIB entry locally instantiated as an End.B6.Encaps SID with the NEXT-CSID flavor:
max_LE) or (Segments Left > Last Entry+1)) { S10. Send an ICMP Parameter Problem to the Source Address with Code 0 (Erroneous header field encountered) and Pointer set to the Segments Left field, interrupt packet processing, and discard the packet. S11. } S12. Decrement IPv6 Hop Limit by 1. S13. Decrement Segments Left by 1. S14. Update IPv6 DA with Segment List[Segments Left]. S15. Push a new IPv6 header with its own SRH containing B. S16. Set the outer IPv6 SA to A. S17. Set the outer IPv6 DA to the first SID of B. S18. Set the outer Payload Length, Traffic Class, Flow Label, Hop Limit, and Next Header fields. S19. Submit the packet to the egress IPv6 FIB lookup for transmission to the new destination. ]]>
Before processing the Upper-Layer header or any IPv6 extension header other than Hop-by-Hop or Destination Option of a packet matching a FIB entry locally instantiated as an End.B6.Encaps SID with the NEXT-CSID flavor:
When processing the Upper-Layer header of a packet matching a FIB entry locally instantiated as an End.B6.Encaps SID with the NEXT-CSID flavor:
End.BM with NEXT-CSID When processing the SRH of a packet matching a FIB entry locally instantiated as an End.BM SID with the NEXT-CSID flavor:
max_LE) or (Segments Left > Last Entry+1)) { S10. Send an ICMP Parameter Problem to the Source Address with Code 0 (Erroneous header field encountered) and Pointer set to the Segments Left field, interrupt packet processing, and discard the packet. S11. } S12. Decrement IPv6 Hop Limit by 1. S13. Decrement Segments Left by 1. S14. Update IPv6 DA with Segment List[Segments Left]. S15. Push the MPLS label stack for B. S16. Submit the packet to the MPLS engine for transmission. ]]>
Before processing the Upper-Layer header or any IPv6 extension header other than Hop-by-Hop or Destination Option of a packet matching a FIB entry locally instantiated as an End.BM SID with the NEXT-CSID flavor:
When processing the Upper-Layer header of a packet matching a FIB entry locally instantiated as an End.BM SID with the NEXT-CSID flavor:
End with REPLACE-CSID When processing the SRH of a packet matching a FIB entry locally instantiated as an End SID with the REPLACE-CSID flavor:
max_LE) or (Segments Left > Last Entry)) { R03. Send an ICMP Parameter Problem to the Source Address, Code 0 (Erroneous header field encountered), Pointer set to the Segments Left field, interrupt packet processing and discard the packet. R04. } R05. Decrement DA.Arg.Index by 1. R06. If (Segment List[Segments Left][DA.Arg.Index] == 0) { R07. Decrement Segments Left by 1. R08. Decrement IPv6 Hop Limit by 1. R09. Update IPv6 DA with Segment List[Segments Left] R10. Submit the packet to the egress IPv6 FIB lookup for transmission to the new destination. R11. } R12. } Else { R13. If((Last Entry > max_LE) or (Segments Left > Last Entry+1)){ R14. Send an ICMP Parameter Problem to the Source Address, Code 0 (Erroneous header field encountered), Pointer set to the Segments Left field, interrupt packet processing and discard the packet. R15. } R16. Decrement Segments Left by 1. R17. Set DA.Arg.Index to (128/LNFL - 1). R18. } R19. Decrement IPv6 Hop Limit by 1. R20. Write Segment List[Segments Left][DA.Arg.Index] into the bits [LBL..LBL+LNFL-1] of the Destination Address of the IPv6 header. R21. Submit the packet to the egress IPv6 FIB lookup for transmission to the new destination. S16. } ]]>
When processing the Upper-Layer header of a packet matching a FIB entry locally instantiated as an End SID with the REPLACE-CSID flavor:
End.X with REPLACE-CSID When processing the SRH of a packet matching a FIB entry locally instantiated as an End.X SID with the REPLACE-CSID flavor:
max_LE) or (Segments Left > Last Entry)) { R03. Send an ICMP Parameter Problem to the Source Address, Code 0 (Erroneous header field encountered), Pointer set to the Segments Left field, interrupt packet processing and discard the packet. R04. } R05. Decrement DA.Arg.Index by 1. R06. If (Segment List[Segments Left][DA.Arg.Index] == 0) { R07. Decrement Segments Left by 1. R08. Decrement IPv6 Hop Limit by 1. R09. Update IPv6 DA with Segment List[Segments Left] R10. Submit the packet to the IPv6 module for transmission to the new destination via a member of J. R11. } R12. } Else { R13. If((Last Entry > max_LE) or (Segments Left > Last Entry+1)){ R14. Send an ICMP Parameter Problem to the Source Address, Code 0 (Erroneous header field encountered), Pointer set to the Segments Left field, interrupt packet processing and discard the packet. R15. } R16. Decrement Segments Left by 1. R17. Set DA.Arg.Index to (128/LNFL - 1). R18. } R19. Decrement IPv6 Hop Limit by 1. R20. Write Segment List[Segments Left][DA.Arg.Index] into the bits [LBL..LBL+LNFL-1] of the Destination Address of the IPv6 header. R21. Submit the packet to the IPv6 module for transmission to the new destination via a member of J. S16. } ]]>
When processing the Upper-Layer header of a packet matching a FIB entry locally instantiated as an End.X SID with the REPLACE-CSID flavor:
End.T with REPLACE-CSID When processing the SRH of a packet matching a FIB entry locally instantiated as an End.T SID with the REPLACE-CSID flavor:
max_LE) or (Segments Left > Last Entry)) { R03. Send an ICMP Parameter Problem to the Source Address, Code 0 (Erroneous header field encountered), Pointer set to the Segments Left field, interrupt packet processing and discard the packet. R04. } R05. Decrement DA.Arg.Index by 1. R06. If (Segment List[Segments Left][DA.Arg.Index] == 0) { R07. Decrement Segments Left by 1. R08. Decrement IPv6 Hop Limit by 1. R09. Update IPv6 DA with Segment List[Segments Left] R10.1. Set the packet's associated FIB table to T. R10.2. Submit the packet to the egress IPv6 FIB lookup for transmission to the new destination. R11. } R12. } Else { R13. If((Last Entry > max_LE) or (Segments Left > Last Entry+1)){ R14. Send an ICMP Parameter Problem to the Source Address, Code 0 (Erroneous header field encountered), Pointer set to the Segments Left field, interrupt packet processing and discard the packet. R15. } R16. Decrement Segments Left by 1. R17. Set DA.Arg.Index to (128/LNFL - 1). R18. } R19. Decrement IPv6 Hop Limit by 1. R20. Write Segment List[Segments Left][DA.Arg.Index] into the bits [LBL..LBL+LNFL-1] of the Destination Address of the IPv6 header. R21.1. Set the packet's associated FIB table to T. R21.2. Submit the packet to the egress IPv6 FIB lookup for transmission to the new destination. S16. } ]]>
When processing the Upper-Layer header of a packet matching a FIB entry locally instantiated as an End.T SID with the REPLACE-CSID flavor:
End.B6.Encaps with REPLACE-CSID When processing the SRH of a packet matching a FIB entry locally instantiated as an End.B6.Encaps SID with the REPLACE-CSID flavor:
max_LE) or (Segments Left > Last Entry)) { R03. Send an ICMP Parameter Problem to the Source Address, Code 0 (Erroneous header field encountered), Pointer set to the Segments Left field, interrupt packet processing and discard the packet. R04. } R05. Decrement DA.Arg.Index by 1. R06. If (Segment List[Segments Left][DA.Arg.Index] == 0) { R07. Decrement Segments Left by 1. R08. Decrement IPv6 Hop Limit by 1. R09. Update IPv6 DA with Segment List[Segments Left] R10.1. Push a new IPv6 header with its own SRH containing B. R10.2. Set the outer IPv6 SA to A. R10.3. Set the outer IPv6 DA to the first SID of B. R10.4. Set the outer Payload Length, Traffic Class, Flow Label, Hop Limit, and Next Header fields. R10.5. Submit the packet to the egress IPv6 FIB lookup for transmission to the next destination. R11. } R12. } Else { R13. If((Last Entry > max_LE) or (Segments Left > Last Entry+1)){ R14. Send an ICMP Parameter Problem to the Source Address, Code 0 (Erroneous header field encountered), Pointer set to the Segments Left field, interrupt packet processing and discard the packet. R15. } R16. Decrement Segments Left by 1. R17. Set DA.Arg.Index to (128/LNFL - 1). R18. } R19. Decrement IPv6 Hop Limit by 1. R20. Write Segment List[Segments Left][DA.Arg.Index] into the bits [LBL..LBL+LNFL-1] of the Destination Address of the IPv6 header. R21.1. Push a new IPv6 header with its own SRH containing B. R21.2. Set the outer IPv6 SA to A. R21.3. Set the outer IPv6 DA to the first SID of B. R21.4. Set the outer Payload Length, Traffic Class, Flow Label, Hop Limit, and Next Header fields. R21.5. Submit the packet to the egress IPv6 FIB lookup for transmission to the next destination. S16. } ]]>
When processing the Upper-Layer header of a packet matching a FIB entry locally instantiated as an End.B6.Encaps SID with the REPLACE-CSID flavor:
End.BM with REPLACE-CSID When processing the SRH of a packet matching a FIB entry locally instantiated as an End.BM SID with the REPLACE-CSID flavor:
max_LE) or (Segments Left > Last Entry)) { R03. Send an ICMP Parameter Problem to the Source Address, Code 0 (Erroneous header field encountered), Pointer set to the Segments Left field, interrupt packet processing and discard the packet. R04. } R05. Decrement DA.Arg.Index by 1. R06. If (Segment List[Segments Left][DA.Arg.Index] == 0) { R07. Decrement Segments Left by 1. R08. Decrement IPv6 Hop Limit by 1. R09. Update IPv6 DA with Segment List[Segments Left] R10.1. Push the MPLS label stack for B. R10.2. Submit the packet to the MPLS engine for transmission. R11. } R12. } Else { R13. If((Last Entry > max_LE) or (Segments Left > Last Entry+1)){ R14. Send an ICMP Parameter Problem to the Source Address, Code 0 (Erroneous header field encountered), Pointer set to the Segments Left field, interrupt packet processing and discard the packet. R15. } R16. Decrement Segments Left by 1. R17. Set DA.Arg.Index to (128/LNFL - 1). R18. } R19. Decrement IPv6 Hop Limit by 1. R20. Write Segment List[Segments Left][DA.Arg.Index] into the bits [LBL..LBL+LNFL-1] of the Destination Address of the IPv6 header. R21.1. Push the MPLS label stack for B. R21.2. Submit the packet to the MPLS engine for transmission. S16. } ]]>
When processing the Upper-Layer header of a packet matching a FIB entry locally instantiated as an End.BM SID with the REPLACE-CSID flavor:
Contributors ZTE Corporation
China liu.aihua@zte.com.cn
Alibaba
USA d.cai@alibaba-inc.com
Cisco Systems, Inc.
Canada ddukes@cisco.com
Futurewei Technologies Ltd.
USA james.n.guichard@futurewei.com
Huawei Technologies
China c.l@huawei.com
NTT Network Innovations
USA robert@raszuk.net
Cisco Systems, Inc.
India ketant.ietf@gmail.com
Bell Canada
Canada daniel.voyer@bell.ca
Broadcom
Israel shay.zadok@broadcom.com