< draft-ietf-spring-srv6-srh-compression-00.txt   draft-ietf-spring-srv6-srh-compression-01.txt >
SPRING W. Cheng, Ed. SPRING W. Cheng, Ed.
Internet-Draft China Mobile Internet-Draft China Mobile
Intended status: Standards Track C. Filsfils Intended status: Standards Track C. Filsfils
Expires: 15 August 2022 Cisco Systems, Inc. Expires: 22 September 2022 Cisco Systems, Inc.
Z. Li Z. Li
Huawei Technologies Huawei Technologies
B. Decraene B. Decraene
Orange Orange
D. Cai D. Cai
Alibaba Alibaba
D. Voyer D. Voyer
Bell Canada Bell Canada
F. Clad, Ed. F. Clad, Ed.
Cisco Systems, Inc. Cisco Systems, Inc.
S. Zadok S. Zadok
Broadcom Broadcom
J. Guichard J. Guichard
Futurewei Technologies Ltd. Futurewei Technologies Ltd.
L. Aihua L. Aihua
ZTE Corporation ZTE Corporation
R. Raszuk R. Raszuk
NTT Network Innovations NTT Network Innovations
C. Li C. Li
Huawei Technologies Huawei Technologies
11 February 2022 21 March 2022
Compressed SRv6 Segment List Encoding in SRH Compressed SRv6 Segment List Encoding in SRH
draft-ietf-spring-srv6-srh-compression-00 draft-ietf-spring-srv6-srh-compression-01
Abstract Abstract
This document defines a compressed SRv6 Segment List Encoding in the This document specifies new flavors for the SR endpoint behaviors
Segment Routing Header (SRH). This solution does not require any SRH defined in RFC 8986, which enable a compressed SRv6 Segment-List
data plane change nor any SRv6 control plane change. This solution encoding in the Segment Routing Header (SRH).
leverages the SRv6 Network Programming model.
Status of This Memo Status of This Memo
This Internet-Draft is submitted in full conformance with the This Internet-Draft is submitted in full conformance with the
provisions of BCP 78 and BCP 79. provisions of BCP 78 and BCP 79.
Internet-Drafts are working documents of the Internet Engineering Internet-Drafts are working documents of the Internet Engineering
Task Force (IETF). Note that other groups may also distribute Task Force (IETF). Note that other groups may also distribute
working documents as Internet-Drafts. The list of current Internet- working documents as Internet-Drafts. The list of current Internet-
Drafts is at https://datatracker.ietf.org/drafts/current/. Drafts is at https://datatracker.ietf.org/drafts/current/.
Internet-Drafts are draft documents valid for a maximum of six months Internet-Drafts are draft documents valid for a maximum of six months
and may be updated, replaced, or obsoleted by other documents at any and may be updated, replaced, or obsoleted by other documents at any
time. It is inappropriate to use Internet-Drafts as reference time. It is inappropriate to use Internet-Drafts as reference
material or to cite them other than as "work in progress." material or to cite them other than as "work in progress."
This Internet-Draft will expire on 15 August 2022. This Internet-Draft will expire on 22 September 2022.
Copyright Notice Copyright Notice
Copyright (c) 2022 IETF Trust and the persons identified as the Copyright (c) 2022 IETF Trust and the persons identified as the
document authors. All rights reserved. document authors. All rights reserved.
This document is subject to BCP 78 and the IETF Trust's Legal This document is subject to BCP 78 and the IETF Trust's Legal
Provisions Relating to IETF Documents (https://trustee.ietf.org/ Provisions Relating to IETF Documents (https://trustee.ietf.org/
license-info) in effect on the date of publication of this document. license-info) in effect on the date of publication of this document.
Please review these documents carefully, as they describe your rights Please review these documents carefully, as they describe your rights
skipping to change at page 2, line 39 skipping to change at page 2, line 39
2. Terminology . . . . . . . . . . . . . . . . . . . . . . . . . 3 2. Terminology . . . . . . . . . . . . . . . . . . . . . . . . . 3
2.1. Requirements Language . . . . . . . . . . . . . . . . . . 4 2.1. Requirements Language . . . . . . . . . . . . . . . . . . 4
3. Basic Concepts . . . . . . . . . . . . . . . . . . . . . . . 4 3. Basic Concepts . . . . . . . . . . . . . . . . . . . . . . . 4
4. SR Endpoint Flavors . . . . . . . . . . . . . . . . . . . . . 5 4. SR Endpoint Flavors . . . . . . . . . . . . . . . . . . . . . 5
4.1. NEXT-C-SID Flavor . . . . . . . . . . . . . . . . . . . . 5 4.1. NEXT-C-SID Flavor . . . . . . . . . . . . . . . . . . . . 5
4.1.1. End with NEXT-C-SID . . . . . . . . . . . . . . . . . 6 4.1.1. End with NEXT-C-SID . . . . . . . . . . . . . . . . . 6
4.1.2. End.X with NEXT-C-SID . . . . . . . . . . . . . . . . 7 4.1.2. End.X with NEXT-C-SID . . . . . . . . . . . . . . . . 7
4.1.3. Combination with PSP, USP and USD flavors . . . . . . 7 4.1.3. Combination with PSP, USP and USD flavors . . . . . . 7
4.2. REPLACE-C-SID Flavor . . . . . . . . . . . . . . . . . . 7 4.2. REPLACE-C-SID Flavor . . . . . . . . . . . . . . . . . . 7
4.2.1. End with REPLACE-C-SID . . . . . . . . . . . . . . . 8 4.2.1. End with REPLACE-C-SID . . . . . . . . . . . . . . . 8
4.2.2. End.X with REPLACE-C-SID . . . . . . . . . . . . . . 10 4.2.2. End.X with REPLACE-C-SID . . . . . . . . . . . . . . 9
4.2.3. Combination with PSP, USP and USD flavors . . . . . . 10 4.2.3. Combination with PSP, USP and USD flavors . . . . . . 9
4.3. Combined NEXT-and-REPLACE-C-SID Flavor . . . . . . . . . 10 4.3. Combined NEXT-and-REPLACE-C-SID Flavor . . . . . . . . . 9
5. GIB, LIB, global C-SID and local C-SID . . . . . . . . . . . 12 5. GIB, LIB, global C-SID and local C-SID . . . . . . . . . . . 11
5.1. Global C-SID . . . . . . . . . . . . . . . . . . . . . . 12 5.1. Global C-SID . . . . . . . . . . . . . . . . . . . . . . 11
5.2. Local C-SID . . . . . . . . . . . . . . . . . . . . . . . 12 5.2. Local C-SID . . . . . . . . . . . . . . . . . . . . . . . 12
6. C-SID and Block Length . . . . . . . . . . . . . . . . . . . 13 6. C-SID and Block Length . . . . . . . . . . . . . . . . . . . 12
6.1. C-SID Length . . . . . . . . . . . . . . . . . . . . . . 13 6.1. C-SID Length . . . . . . . . . . . . . . . . . . . . . . 12
6.2. Block Length . . . . . . . . . . . . . . . . . . . . . . 13 6.2. Block Length . . . . . . . . . . . . . . . . . . . . . . 12
6.3. GIB/LIB Usage . . . . . . . . . . . . . . . . . . . . . . 13 6.3. GIB/LIB Usage . . . . . . . . . . . . . . . . . . . . . . 13
7. Efficient SID-list Encoding . . . . . . . . . . . . . . . . . 13 7. Efficient SID-list Encoding . . . . . . . . . . . . . . . . . 13
8. Inter Routing Domains with the End.XPS behavior . . . . . . . 13 8. Inter Routing Domains with the End.XPS behavior . . . . . . . 13
9. Control Plane . . . . . . . . . . . . . . . . . . . . . . . . 15 9. Control Plane . . . . . . . . . . . . . . . . . . . . . . . . 15
10. Illustrations . . . . . . . . . . . . . . . . . . . . . . . . 15 10. Illustrations . . . . . . . . . . . . . . . . . . . . . . . . 15
11. Interoperability Status . . . . . . . . . . . . . . . . . . . 15 11. Interoperability Status . . . . . . . . . . . . . . . . . . . 15
12. Security Considerations . . . . . . . . . . . . . . . . . . . 16 12. Deployment Model . . . . . . . . . . . . . . . . . . . . . . 16
13. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . 16 13. Security Considerations . . . . . . . . . . . . . . . . . . . 16
14. References . . . . . . . . . . . . . . . . . . . . . . . . . 16 14. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . 16
14.1. Normative References . . . . . . . . . . . . . . . . . . 16 15. References . . . . . . . . . . . . . . . . . . . . . . . . . 16
14.2. Informative References . . . . . . . . . . . . . . . . . 17 15.1. Normative References . . . . . . . . . . . . . . . . . . 16
15.2. Informative References . . . . . . . . . . . . . . . . . 17
Appendix A. Open Issues . . . . . . . . . . . . . . . . . . . . 18 Appendix A. Open Issues . . . . . . . . . . . . . . . . . . . . 18
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 18 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 18
1. Introduction 1. Introduction
The Segment Routing architecture is defined in [RFC8402]. The Segment Routing architecture is defined in [RFC8402].
SRv6 Network Programming [RFC8986] defines a framework to build a SRv6 Network Programming [RFC8986] defines a framework to build a
network program with topological and service segments carried in a network program with topological and service segments carried in a
Segment Routing header (SRH) [RFC8754]. Segment Routing header (SRH) [RFC8754].
This document adds new flavors to the SR endpoint behaviors defined This document specifies new flavors to the SR endpoint behaviors
in Section 4 of [RFC8986]. These flavors enable a compressed defined in Section 4 of [RFC8986]. These flavors enable a compressed
encoding of the SRv6 Segment-List in the SRH and therefore address encoding of the SRv6 Segment-List in the SRH and therefore address
the requirements described in the requirements described in
[I-D.srcompdt-spring-compression-requirement]. [I-D.srcompdt-spring-compression-requirement].
The flavors defined in this document leverage the SRH data plane The flavors defined in this document leverage the SRv6 data plane
without any change and do not require any SRv6 control plane change. defined in [RFC8754] and [RFC8986], and are compatible with the SRv6
control plane extensions for IS-IS
[I-D.ietf-lsr-isis-srv6-extensions], OSPF
[I-D.ietf-lsr-ospfv3-srv6-extensions], and BGP
[I-D.ietf-bess-srv6-services].
2. Terminology 2. Terminology
This document leverages the terms defined in [RFC8402], [RFC8754] and This document leverages the terms defined in [RFC8402], [RFC8754] and
[RFC8986]. The reader is assumed to be familiar with this [RFC8986]. The reader is assumed to be familiar with this
terminology. terminology.
This document introduces the following new terms: This document introduces the following new terms:
* Compressed-SID (C-SID): A C-SID is a short encoding of a SID in * Compressed-SID (C-SID): A C-SID is a short encoding of a SID in
skipping to change at page 4, line 36 skipping to change at page 4, line 43
When a sequence of consecutive SIDs in a Segment List shares a common When a sequence of consecutive SIDs in a Segment List shares a common
Locator-Block, a compressed SRv6 Segment-List encoding can optimize Locator-Block, a compressed SRv6 Segment-List encoding can optimize
the packet header length by avoiding the repetition of the Locator- the packet header length by avoiding the repetition of the Locator-
Block and trailing bits with each individual SID. Block and trailing bits with each individual SID.
The compressed Segment List encoding is fully compliant with the The compressed Segment List encoding is fully compliant with the
specifications in [RFC8402], [RFC8754] and [RFC8986]. Efficient specifications in [RFC8402], [RFC8754] and [RFC8986]. Efficient
encoding is achieved by combining a compressed Segment List encoding encoding is achieved by combining a compressed Segment List encoding
logic on the SR policy headend with new flavors of the base SRv6 logic on the SR policy headend with new flavors of the base SRv6
endpoint behaviors that decode this compressed encoding. No SRv6 SRH endpoint behaviors that decode this compressed encoding.
data plane change nor control plane extension is required.
A Segment List can be encoded in the packet header using any A Segment List can be encoded in the packet header using any
combination of compressed and uncompressed sequences. The C-SID combination of compressed and uncompressed sequences. The C-SID
sequences leverage the flavors defined in this document, while the sequences leverage the flavors defined in this document, while the
uncompressed sequences use behaviors and flavors defined in other uncompressed sequences use behaviors and flavors defined in other
documents, such as [RFC8986]. An SR Policy headend constructs and documents, such as [RFC8986]. An SR Policy headend constructs and
compresses the SID-list depending on the capabilities of each SR compresses the SID-list depending on the capabilities of each SR
endpoint node that the packet should traverse, as well as its own endpoint node that the packet should traverse, as well as its own
compression capabilities. compression capabilities.
skipping to change at page 6, line 15 skipping to change at page 6, line 15
+------------------------------------------------------------------+ +------------------------------------------------------------------+
| Locator-Block |Loc-Node| Argument | | Locator-Block |Loc-Node| Argument |
| |Function| | | |Function| |
+------------------------------------------------------------------+ +------------------------------------------------------------------+
<--------- B ----------> <- NF -> <------------- A --------------> <--------- B ----------> <- NF -> <------------- A -------------->
Figure 1: Example of a NEXT-C-SID flavored SID structure using a Figure 1: Example of a NEXT-C-SID flavored SID structure using a
48-bit block, 16-bit combined locator and function, and 64-bit 48-bit block, 16-bit combined locator and function, and 64-bit
argument argument
The NEXT-C-SID flavor has been previously documented in
[I-D.filsfils-spring-net-pgm-extension-srv6-usid] under the name
"SHIFT" flavor. In that context, a C-SID and a C-SID-sequence are
respectively named a Micro-Segment (uSID) and a Micro-Program.
4.1.1. End with NEXT-C-SID 4.1.1. End with NEXT-C-SID
When processing an IPv6 packet that matches a FIB entry locally When processing an IPv6 packet that matches a FIB entry locally
instantiated as an End SID with the NEXT-C-SID flavor, the procedure instantiated as an End SID with the NEXT-C-SID flavor, the procedure
described in Section 4.1 of [RFC8986] is executed with the following described in Section 4.1 of [RFC8986] is executed with the following
modifications. modifications.
The below pseudocode is inserted between lines S01 and S02 of the SRH The below pseudocode is inserted between lines S01 and S02 of the SRH
processing in Section 4.1 of [RFC8986], and a second time before line processing in Section 4.1 of [RFC8986], and a second time before line
S01 of the upper-layer header processing in Section 4.1.1 of S01 of the upper-layer header processing in Section 4.1.1 of
skipping to change at page 8, line 5 skipping to change at page 8, line 5
+-------------------------------------------------------------------+ +-------------------------------------------------------------------+
| Locator-Block | Locator-Node |Argument| 0 | | Locator-Block | Locator-Node |Argument| 0 |
| | + Function | | | | | + Function | | |
+-------------------------------------------------------------------+ +-------------------------------------------------------------------+
<--------- B ----------> <----- NF -----> <- A --> <--------- B ----------> <----- NF -----> <- A -->
Figure 2: Example of a REPLACE-C-SID flavored SID structure using Figure 2: Example of a REPLACE-C-SID flavored SID structure using
a 48-bit block, 32-bit combined locator and function, and 16-bit a 48-bit block, 32-bit combined locator and function, and 16-bit
argument argument
The REPLACE-C-SID flavor has been previously documented in
[I-D.cl-spring-generalized-srv6-for-cmpr] under the name
"COC(Continue of Compression)" flavor. In that context, a C-SID and
a C-SID-sequence are respectively named a G-SID and G-SRv6
compression sub-path.
4.2.1. End with REPLACE-C-SID 4.2.1. End with REPLACE-C-SID
When processing an IPv6 packet that matches a FIB entry locally When processing an IPv6 packet that matches a FIB entry locally
instantiated as an End SID with the REPLACE-C-SID flavor, the SRH instantiated as an End SID with the REPLACE-C-SID flavor, the SRH
processing described in Section 4.1 of [RFC8986] is replaced as processing described in Section 4.1 of [RFC8986] is replaced as
follows. follows.
S01. When an SRH is processed { S01. When an SRH is processed {
S02. If (Segments Left == 0 and DA.Argument == 0) { S02. If (Segments Left == 0 and DA.Argument == 0) {
S03. Stop processing the SRH, and proceed to process the next S03. Stop processing the SRH, and proceed to process the next
skipping to change at page 15, line 43 skipping to change at page 15, line 38
length for the REPLACE-C-SID and the NEXT-and-REPLACE-C-SID flavors length for the REPLACE-C-SID and the NEXT-and-REPLACE-C-SID flavors
is relaxed and becomes: all SID the are part of a C-SID sequence is relaxed and becomes: all SID the are part of a C-SID sequence
*within a domain* MUST have the same SID length NF. *within a domain* MUST have the same SID length NF.
9. Control Plane 9. Control Plane
This document does not require any control plane modification. This document does not require any control plane modification.
10. Illustrations 10. Illustrations
Illustrations will be provided in a separate document. Illustrations for the functionalities defined in this document are
provided in [I-D.clad-spring-srv6-srh-compression-illus].
11. Interoperability Status 11. Interoperability Status
In November 2020, China Mobile successfully validated multiple In November 2020, China Mobile successfully validated multiple
interoperable implementations of the NEXT-C-SID and REPLACE-C-SID interoperable implementations of the NEXT-C-SID and REPLACE-C-SID
flavors defined in this document. flavors defined in this document.
This testing covered two different implementations of the SRv6 This testing covered two different implementations of the SRv6
endpoint flavors defined in this document: endpoint flavors defined in this document:
skipping to change at page 16, line 8 skipping to change at page 16, line 4
In November 2020, China Mobile successfully validated multiple In November 2020, China Mobile successfully validated multiple
interoperable implementations of the NEXT-C-SID and REPLACE-C-SID interoperable implementations of the NEXT-C-SID and REPLACE-C-SID
flavors defined in this document. flavors defined in this document.
This testing covered two different implementations of the SRv6 This testing covered two different implementations of the SRv6
endpoint flavors defined in this document: endpoint flavors defined in this document:
* Hardware implementation in Cisco ASR 9000 running IOS XR * Hardware implementation in Cisco ASR 9000 running IOS XR
* Software implementation in Cisco IOS XRv9000 virtual appliance * Software implementation in Cisco IOS XRv9000 virtual appliance
* Hardware implementation in Huawei NE40E and NE5000E running VRP * Hardware implementation in Huawei NE40E and NE5000E running VRP
The interoperability was validated for the following scenario: The interoperability was validated for the following scenario:
* Packet forwarding through a traffic engineering segment list * Packet forwarding through a traffic engineering segment list
combining, in the same SRH ([RFC8754]), SRv6 SIDs bound to an combining, in the same SRH ([RFC8754]), SRv6 SIDs bound to an
endpoint behavior with the NEXT-C-SID flavor and SRv6 SIDs bound endpoint behavior with the NEXT-C-SID flavor and SRv6 SIDs bound
to an endpoint behavior with the REPLACE-C-SID flavor. to an endpoint behavior with the REPLACE-C-SID flavor.
Further interoperability testing is ongoing and will be reported in Further interoperability testing is ongoing and will be reported in
this document as the work progresses. this document as the work progresses.
12. Security Considerations 12. Deployment Model
Section 5 of [RFC8754] defines the intra-SR-domain deployment model
and associated security procedures.
The same deployment model apply to the SIDs defined in this document.
13. Security Considerations
The security requirements and mechanisms described in [RFC8402] and The security requirements and mechanisms described in [RFC8402] and
[RFC8754] also apply to this document. [RFC8754] also apply to this document.
This document does not introduce any new security consideration. This document does not introduce any new security consideration.
13. Acknowledgements 14. Acknowledgements
The authors would like to thank Kamran Raza, Xing Jiang, YuanChao Su, The authors would like to thank Kamran Raza, Xing Jiang, YuanChao Su,
Han Li and Yisong Liu. Han Li and Yisong Liu.
14. References 15. References
14.1. Normative References 15.1. Normative References
[RFC2119] Bradner, S., "Key words for use in RFCs to Indicate [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate
Requirement Levels", BCP 14, RFC 2119, Requirement Levels", BCP 14, RFC 2119,
DOI 10.17487/RFC2119, March 1997, DOI 10.17487/RFC2119, March 1997,
<https://www.rfc-editor.org/info/rfc2119>. <https://www.rfc-editor.org/info/rfc2119>.
[RFC8174] Leiba, B., "Ambiguity of Uppercase vs Lowercase in RFC [RFC8174] Leiba, B., "Ambiguity of Uppercase vs Lowercase in RFC
2119 Key Words", BCP 14, RFC 8174, DOI 10.17487/RFC8174, 2119 Key Words", BCP 14, RFC 8174, DOI 10.17487/RFC8174,
May 2017, <https://www.rfc-editor.org/info/rfc8174>. May 2017, <https://www.rfc-editor.org/info/rfc8174>.
skipping to change at page 17, line 16 skipping to change at page 17, line 16
Matsushima, S., and D. Voyer, "IPv6 Segment Routing Header Matsushima, S., and D. Voyer, "IPv6 Segment Routing Header
(SRH)", RFC 8754, DOI 10.17487/RFC8754, March 2020, (SRH)", RFC 8754, DOI 10.17487/RFC8754, March 2020,
<https://www.rfc-editor.org/info/rfc8754>. <https://www.rfc-editor.org/info/rfc8754>.
[RFC8986] Filsfils, C., Ed., Camarillo, P., Ed., Leddy, J., Voyer, [RFC8986] Filsfils, C., Ed., Camarillo, P., Ed., Leddy, J., Voyer,
D., Matsushima, S., and Z. Li, "Segment Routing over IPv6 D., Matsushima, S., and Z. Li, "Segment Routing over IPv6
(SRv6) Network Programming", RFC 8986, (SRv6) Network Programming", RFC 8986,
DOI 10.17487/RFC8986, February 2021, DOI 10.17487/RFC8986, February 2021,
<https://www.rfc-editor.org/info/rfc8986>. <https://www.rfc-editor.org/info/rfc8986>.
14.2. Informative References 15.2. Informative References
[EMAIL1] "SPRING chairs email on the adoption of draft- [EMAIL1] "SPRING chairs email on the adoption of draft-
filsfilscheng-spring-srv6-srh-compression-02", October filsfilscheng-spring-srv6-srh-compression-02", October
2021, <https://mailarchive.ietf.org/arch/msg/spring/ 2021, <https://mailarchive.ietf.org/arch/msg/spring/
VjVIxo7fZFhsIHJ5wFQXIBvvtNM/>. VjVIxo7fZFhsIHJ5wFQXIBvvtNM/>.
[EMAIL2] "SPRING chairs email on working group process", February [EMAIL2] "SPRING chairs email on working group process", February
2022, <https://mailarchive.ietf.org/arch/msg/spring/ 2022, <https://mailarchive.ietf.org/arch/msg/spring/
vCc9Ckvwu5HA-RCleV712dsA5OA/>. vCc9Ckvwu5HA-RCleV712dsA5OA/>.
[I-D.cl-spring-generalized-srv6-for-cmpr] [I-D.clad-spring-srv6-srh-compression-illus]
(editor), W. C., Li, Z., (editor), C. L., Clad, F., Liu, Clad, F. and D. Dukes, "Illustrations for Compressed SRv6
A., Xie, C., Liu, Y., and S. Zadok, "Generalized SRv6 Segment List Encoding in SRH", Work in Progress, Internet-
Network Programming for SRv6 Compression", Work in Draft, draft-clad-spring-srv6-srh-compression-illus-00, 15
Progress, Internet-Draft, draft-cl-spring-generalized- October 2021, <https://www.ietf.org/archive/id/draft-clad-
srv6-for-cmpr-04, 24 October 2021, spring-srv6-srh-compression-illus-00.txt>.
<https://www.ietf.org/archive/id/draft-cl-spring-
generalized-srv6-for-cmpr-04.txt>.
[I-D.filsfils-spring-net-pgm-extension-srv6-usid] [I-D.ietf-bess-srv6-services]
Filsfils, C., Garvia, P. C., Cai, D., Voyer, D., Meilik, Dawra, G., Filsfils, C., Talaulikar, K., Raszuk, R.,
I., Patel, K., Henderickx, W., Jonnalagadda, P., Melman, Decraene, B., Zhuang, S., and J. Rabadan, "SRv6 BGP based
D., Liu, Y., and J. Guichard, "Network Programming Overlay Services", Work in Progress, Internet-Draft,
extension: SRv6 uSID instruction", Work in Progress, draft-ietf-bess-srv6-services-13, 19 March 2022,
Internet-Draft, draft-filsfils-spring-net-pgm-extension- <https://www.ietf.org/archive/id/draft-ietf-bess-srv6-
srv6-usid-12, 13 December 2021, services-13.txt>.
<https://www.ietf.org/archive/id/draft-filsfils-spring-
net-pgm-extension-srv6-usid-12.txt>. [I-D.ietf-lsr-isis-srv6-extensions]
Psenak, P., Filsfils, C., Bashandy, A., Decraene, B., and
Z. Hu, "IS-IS Extensions to Support Segment Routing over
IPv6 Dataplane", Work in Progress, Internet-Draft, draft-
ietf-lsr-isis-srv6-extensions-18, 20 October 2021,
<https://www.ietf.org/archive/id/draft-ietf-lsr-isis-srv6-
extensions-18.txt>.
[I-D.ietf-lsr-ospfv3-srv6-extensions]
Li, Z., Hu, Z., Cheng, D., Talaulikar, K., and P. Psenak,
"OSPFv3 Extensions for SRv6", Work in Progress, Internet-
Draft, draft-ietf-lsr-ospfv3-srv6-extensions-03, 19
November 2021, <https://www.ietf.org/archive/id/draft-
ietf-lsr-ospfv3-srv6-extensions-03.txt>.
[I-D.srcompdt-spring-compression-requirement] [I-D.srcompdt-spring-compression-requirement]
Cheng, W., Xie, C., Bonica, R., Dukes, D., Li, C., Shaofu, Cheng, W., Xie, C., Bonica, R., Dukes, D., Li, C., Shaofu,
P., and W. Henderickx, "Compressed SRv6 SID List P., and W. Henderickx, "Compressed SRv6 SID List
Requirements", Work in Progress, Internet-Draft, draft- Requirements", Work in Progress, Internet-Draft, draft-
srcompdt-spring-compression-requirement-07, 11 July 2021, srcompdt-spring-compression-requirement-07, 11 July 2021,
<https://www.ietf.org/archive/id/draft-srcompdt-spring- <https://www.ietf.org/archive/id/draft-srcompdt-spring-
compression-requirement-07.txt>. compression-requirement-07.txt>.
Appendix A. Open Issues Appendix A. Open Issues
 End of changes. 22 change blocks. 
62 lines changed or deleted 72 lines changed or added

This html diff was produced by rfcdiff 1.48. The latest version is available from http://tools.ietf.org/tools/rfcdiff/