draft-ietf-lsr-isis-srv6-extensions-08.txt   draft-ietf-lsr-isis-srv6-extensions-09.txt 
Networking Working Group P. Psenak, Ed. Networking Working Group P. Psenak, Ed.
Internet-Draft C. Filsfils Internet-Draft C. Filsfils
Intended status: Standards Track Cisco Systems Intended status: Standards Track Cisco Systems
Expires: October 25, 2020 A. Bashandy Expires: March 12, 2021 A. Bashandy
Individual Individual
B. Decraene B. Decraene
Orange Orange
Z. Hu Z. Hu
Huawei Technologies Huawei Technologies
April 23, 2020 September 8, 2020
IS-IS Extension to Support Segment Routing over IPv6 Dataplane IS-IS Extension to Support Segment Routing over IPv6 Dataplane
draft-ietf-lsr-isis-srv6-extensions-08.txt draft-ietf-lsr-isis-srv6-extensions-09.txt
Abstract Abstract
Segment Routing (SR) allows for a flexible definition of end-to-end Segment Routing (SR) allows for a flexible definition of end-to-end
paths by encoding paths as sequences of topological sub-paths, called paths by encoding paths as sequences of topological sub-paths, called
"segments". Segment routing architecture can be implemented over an "segments". Segment routing architecture can be implemented over an
MPLS data plane as well as an IPv6 data plane. This draft describes MPLS data plane as well as an IPv6 data plane. This draft describes
the IS-IS extensions required to support Segment Routing over an IPv6 the IS-IS extensions required to support Segment Routing over an IPv6
data plane. data plane.
skipping to change at page 1, line 49 skipping to change at page 1, line 49
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 October 25, 2020. This Internet-Draft will expire on March 12, 2021.
Copyright Notice Copyright Notice
Copyright (c) 2020 IETF Trust and the persons identified as the Copyright (c) 2020 IETF Trust and the persons identified as the
document authors. All rights reserved. document authors. All rights reserved.
This document is subject to BCP 78 and the IETF Trust's Legal This document is subject to BCP 78 and the IETF Trust's Legal
Provisions Relating to IETF Documents Provisions Relating to IETF Documents
(https://trustee.ietf.org/license-info) in effect on the date of (https://trustee.ietf.org/license-info) in effect on the date of
publication of this document. Please review these documents publication of this document. Please review these documents
skipping to change at page 2, line 40 skipping to change at page 2, line 40
5. SRv6 SIDs and Reachability . . . . . . . . . . . . . . . . . 6 5. SRv6 SIDs and Reachability . . . . . . . . . . . . . . . . . 6
6. Advertising Anycast Property . . . . . . . . . . . . . . . . 7 6. Advertising Anycast Property . . . . . . . . . . . . . . . . 7
7. Advertising Locators and End SIDs . . . . . . . . . . . . . . 8 7. Advertising Locators and End SIDs . . . . . . . . . . . . . . 8
7.1. SRv6 Locator TLV Format . . . . . . . . . . . . . . . . . 9 7.1. SRv6 Locator TLV Format . . . . . . . . . . . . . . . . . 9
7.2. SRv6 End SID sub-TLV . . . . . . . . . . . . . . . . . . 10 7.2. SRv6 End SID sub-TLV . . . . . . . . . . . . . . . . . . 10
8. Advertising SRv6 Adjacency SIDs . . . . . . . . . . . . . . . 12 8. Advertising SRv6 Adjacency SIDs . . . . . . . . . . . . . . . 12
8.1. SRv6 End.X SID sub-TLV . . . . . . . . . . . . . . . . . 12 8.1. SRv6 End.X SID sub-TLV . . . . . . . . . . . . . . . . . 12
8.2. SRv6 LAN End.X SID sub-TLV . . . . . . . . . . . . . . . 14 8.2. SRv6 LAN End.X SID sub-TLV . . . . . . . . . . . . . . . 14
9. SRv6 SID Structure Sub-Sub-TLV . . . . . . . . . . . . . . . 16 9. SRv6 SID Structure Sub-Sub-TLV . . . . . . . . . . . . . . . 16
10. Advertising Endpoint Behaviors . . . . . . . . . . . . . . . 17 10. Advertising Endpoint Behaviors . . . . . . . . . . . . . . . 17
11. Implementation Status . . . . . . . . . . . . . . . . . . . . 18 11. Implementation Status . . . . . . . . . . . . . . . . . . . . 17
11.1. Cisco . . . . . . . . . . . . . . . . . . . . . . . . . 18 11.1. Cisco . . . . . . . . . . . . . . . . . . . . . . . . . 18
11.2. Huawei . . . . . . . . . . . . . . . . . . . . . . . . . 18 11.2. Huawei . . . . . . . . . . . . . . . . . . . . . . . . . 18
11.3. Juniper . . . . . . . . . . . . . . . . . . . . . . . . 18 11.3. Juniper . . . . . . . . . . . . . . . . . . . . . . . . 18
11.4. Arrcus . . . . . . . . . . . . . . . . . . . . . . . . . 18 11.4. Arrcus . . . . . . . . . . . . . . . . . . . . . . . . . 18
11.5. Interoperability Testing. . . . . . . . . . . . . . . . 19 11.5. Interoperability Testing. . . . . . . . . . . . . . . . 19
12. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 19 12. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 19
12.1. SRv6 Locator TLV . . . . . . . . . . . . . . . . . . . . 19 12.1. SRv6 Locator TLV . . . . . . . . . . . . . . . . . . . . 19
12.1.1. SRv6 End SID sub-TLV . . . . . . . . . . . . . . . . 19 12.1.1. SRv6 End SID sub-TLV . . . . . . . . . . . . . . . . 19
12.1.2. Revised sub-TLV table . . . . . . . . . . . . . . . 19 12.1.2. Revised sub-TLV table . . . . . . . . . . . . . . . 19
12.2. SRv6 Capabilities sub-TLV . . . . . . . . . . . . . . . 20 12.2. SRv6 Capabilities sub-TLV . . . . . . . . . . . . . . . 20
12.3. SRv6 End.X SID and SRv6 LAN End.X SID sub-TLVs . . . . . 20 12.3. SRv6 End.X SID and SRv6 LAN End.X SID sub-TLVs . . . . . 20
12.4. MSD Types . . . . . . . . . . . . . . . . . . . . . . . 21 12.4. MSD Types . . . . . . . . . . . . . . . . . . . . . . . 20
12.5. Sub-Sub-TLVs for SID Sub-TLVs . . . . . . . . . . . . . 21 12.5. Sub-Sub-TLVs for SID Sub-TLVs . . . . . . . . . . . . . 21
12.6. Prefix Attribute Flags Sub-TLV . . . . . . . . . . . . . 21 12.6. Prefix Attribute Flags Sub-TLV . . . . . . . . . . . . . 21
13. Security Considerations . . . . . . . . . . . . . . . . . . . 22 13. Security Considerations . . . . . . . . . . . . . . . . . . . 21
14. Contributors . . . . . . . . . . . . . . . . . . . . . . . . 22 14. Contributors . . . . . . . . . . . . . . . . . . . . . . . . 21
15. References . . . . . . . . . . . . . . . . . . . . . . . . . 23 15. References . . . . . . . . . . . . . . . . . . . . . . . . . 22
15.1. Normative References . . . . . . . . . . . . . . . . . . 23 15.1. Normative References . . . . . . . . . . . . . . . . . . 22
15.2. Informative References . . . . . . . . . . . . . . . . . 25 15.2. Informative References . . . . . . . . . . . . . . . . . 24
15.3. URIs . . . . . . . . . . . . . . . . . . . . . . . . . . 26 15.3. URIs . . . . . . . . . . . . . . . . . . . . . . . . . . 25
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 26 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 25
1. Introduction 1. Introduction
With Segment Routing (SR) [I-D.ietf-spring-segment-routing], a node With Segment Routing (SR) [I-D.ietf-spring-segment-routing], a node
steers a packet through an ordered list of instructions, called steers a packet through an ordered list of instructions, called
segments. segments.
Segments are identified through Segment Identifiers (SIDs). Segments are identified through Segment Identifiers (SIDs).
Segment Routing can be directly instantiated on the IPv6 data plane Segment Routing can be directly instantiated on the IPv6 data plane
skipping to change at page 17, line 17 skipping to change at page 17, line 17
TLV, the parent Sub-TLV MUST be ignored by the receiver. TLV, the parent Sub-TLV MUST be ignored by the receiver.
The sum of all four sizes advertised in ISIS SRv6 SID Structure Sub- The sum of all four sizes advertised in ISIS SRv6 SID Structure Sub-
Sub-TLV must be lower or equal to 128 bits. If the sum of all four Sub-TLV must be lower or equal to 128 bits. If the sum of all four
sizes advertised in the ISIS SRv6 SID Structure Sub-Sub-TLV is larger sizes advertised in the ISIS SRv6 SID Structure Sub-Sub-TLV is larger
than 128 bits, the parent Sub-TLV MUST be ignored by the receiver. than 128 bits, the parent Sub-TLV MUST be ignored by the receiver.
10. Advertising Endpoint Behaviors 10. Advertising Endpoint Behaviors
Endpoint behaviors are defined in Endpoint behaviors are defined in
[I-D.ietf-spring-srv6-network-programming] and [I-D.ietf-spring-srv6-network-programming]. The codepoints for the
[I-D.ietf-6man-spring-srv6-oam]. The codepoints for the Endpoint Endpoint behaviors are defined in the "SRv6 Endpoint Behaviors"
behaviors are defined in the "SRv6 Endpoint Behaviors" registry registry defined in [I-D.ietf-spring-srv6-network-programming]. This
defined in [I-D.ietf-spring-srv6-network-programming]. This section section lists the Endpoint behaviors which MAY be advertised by ISIS,
lists the Endpoint behaviors which MAY be advertised by ISIS,
together with their codepoints. If this behavior is advertised it together with their codepoints. If this behavior is advertised it
MUST only be advertised in the TLV[s] as indicated by "Y" in the MUST only be advertised in the TLV[s] as indicated by "Y" in the
table below, and MUST NOT be advertised in the TLV[s] as indicated by table below, and MUST NOT be advertised in the TLV[s] as indicated by
"N" in the table below. "N" in the table below.
Endpoint |Endpoint | End | End.X | Lan End.X | Endpoint |Endpoint | End | End.X | Lan End.X |
Behavior |Behavior Codepoint | SID | SID | SID | Behavior |Behavior Codepoint | SID | SID | SID |
-----------------------|--------------------|-------|-------|-----------| -----------------------|--------------------|-------|-------|-----------|
End (PSP, USP, USD) | 1-4, 28-31 | Y | N | N | End (PSP, USP, USD) | 1-4, 28-31 | Y | N | N |
-----------------------|--------------------|-------|-------|-----------| -----------------------|--------------------|-------|-------|-----------|
skipping to change at page 17, line 45 skipping to change at page 17, line 44
-----------------------|--------------------|-------|-------|-----------| -----------------------|--------------------|-------|-------|-----------|
End.DX6 | 16 | N | Y | Y | End.DX6 | 16 | N | Y | Y |
-----------------------|--------------------|-------|-------|-----------| -----------------------|--------------------|-------|-------|-----------|
End.DX4 | 17 | N | Y | Y | End.DX4 | 17 | N | Y | Y |
-----------------------|--------------------|-------|-------|-----------| -----------------------|--------------------|-------|-------|-----------|
End.DT6 | 18 | Y | N | N | End.DT6 | 18 | Y | N | N |
-----------------------|--------------------|-------|-------|-----------| -----------------------|--------------------|-------|-------|-----------|
End.DT4 | 19 | Y | N | N | End.DT4 | 19 | Y | N | N |
-----------------------|--------------------|-------|-------|-----------| -----------------------|--------------------|-------|-------|-----------|
End.DT64 | 20 | Y | N | N | End.DT64 | 20 | Y | N | N |
-----------------------|--------------------|-------|-------|-----------|
End.OP | 40 | Y | N | N |
-----------------------|--------------------|-------|-------|-----------|
End.OTP | 41 | Y | N | N |
11. Implementation Status 11. Implementation Status
This section describes the implementation status of the ISIS SRv6 This section describes the implementation status of the ISIS SRv6
extensions. extensions.
11.1. Cisco 11.1. Cisco
Cisco's ISIS SRv6 implementation supports following functionalities: Cisco's ISIS SRv6 implementation supports following functionalities:
skipping to change at page 20, line 7 skipping to change at page 19, line 44
Name: SRv6 End SID Name: SRv6 End SID
12.1.2. Revised sub-TLV table 12.1.2. Revised sub-TLV table
The revised table of sub-TLVs for the (renamed) "Sub-TLVs for TLVs The revised table of sub-TLVs for the (renamed) "Sub-TLVs for TLVs
27, 135, 235, 236 and 237 registry" is shown below: 27, 135, 235, 236 and 237 registry" is shown below:
Type 27 135 235 236 237 Type 27 135 235 236 237
1 n y y y y 1 y y y y y
2 n y y y y 2 y y y y y
3 n y y y y 3 n y y y y
4 y y y y y 4 y y y y y
5 y n n n n 5 y n n n n
6 n y y y y
11 y y y y y 11 y y y y y
12 y y y y y 12 y y y y y
32 n y y y y
12.2. SRv6 Capabilities sub-TLV 12.2. SRv6 Capabilities sub-TLV
This document adds the definition of a new sub-TLV in the "Sub- TLVs This document adds the definition of a new sub-TLV in the "Sub- TLVs
for TLV 242 registry". for TLV 242 registry".
Type: 25 (Suggested - to be assigned by IANA) Type: 25 (Suggested - to be assigned by IANA)
Description: SRv6 Capabilities Description: SRv6 Capabilities
skipping to change at page 24, line 15 skipping to change at page 23, line 15
[I-D.ietf-6man-segment-routing-header] [I-D.ietf-6man-segment-routing-header]
Filsfils, C., Dukes, D., Previdi, S., Leddy, J., Filsfils, C., Dukes, D., Previdi, S., Leddy, J.,
Matsushima, S., and D. Voyer, "IPv6 Segment Routing Header Matsushima, S., and D. Voyer, "IPv6 Segment Routing Header
(SRH)", draft-ietf-6man-segment-routing-header-26 (work in (SRH)", draft-ietf-6man-segment-routing-header-26 (work in
progress), October 2019. progress), October 2019.
[I-D.ietf-6man-spring-srv6-oam] [I-D.ietf-6man-spring-srv6-oam]
Ali, Z., Filsfils, C., Matsushima, S., Voyer, D., and M. Ali, Z., Filsfils, C., Matsushima, S., Voyer, D., and M.
Chen, "Operations, Administration, and Maintenance (OAM) Chen, "Operations, Administration, and Maintenance (OAM)
in Segment Routing Networks with IPv6 Data plane (SRv6)", in Segment Routing Networks with IPv6 Data plane (SRv6)",
draft-ietf-6man-spring-srv6-oam-04 (work in progress), draft-ietf-6man-spring-srv6-oam-07 (work in progress),
March 2020. July 2020.
[I-D.ietf-spring-srv6-network-programming] [I-D.ietf-spring-srv6-network-programming]
Filsfils, C., Camarillo, P., Leddy, J., Voyer, D., Filsfils, C., Camarillo, P., Leddy, J., Voyer, D.,
Matsushima, S., and Z. Li, "SRv6 Network Programming", Matsushima, S., and Z. Li, "SRv6 Network Programming",
draft-ietf-spring-srv6-network-programming-15 (work in draft-ietf-spring-srv6-network-programming-18 (work in
progress), March 2020. progress), August 2020.
[ISO10589] [ISO10589]
Standardization", I. ". O. F., "Intermediate system to Standardization", I. ". O. F., "Intermediate system to
Intermediate system intra-domain routeing information Intermediate system intra-domain routeing information
exchange protocol for use in conjunction with the protocol exchange protocol for use in conjunction with the protocol
for providing the connectionless-mode Network Service (ISO for providing the connectionless-mode Network Service (ISO
8473), ISO/IEC 10589:2002, Second Edition.", Nov 2002. 8473), ISO/IEC 10589:2002, Second Edition.", Nov 2002.
[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,
skipping to change at page 25, line 44 skipping to change at page 24, line 44
Bashandy, A., Gredler, H., and B. Decraene, "IS-IS Bashandy, A., Gredler, H., and B. Decraene, "IS-IS
Extensions for Segment Routing", RFC 8667, Extensions for Segment Routing", RFC 8667,
DOI 10.17487/RFC8667, December 2019, DOI 10.17487/RFC8667, December 2019,
<https://www.rfc-editor.org/info/rfc8667>. <https://www.rfc-editor.org/info/rfc8667>.
15.2. Informative References 15.2. Informative References
[I-D.ietf-lsr-flex-algo] [I-D.ietf-lsr-flex-algo]
Psenak, P., Hegde, S., Filsfils, C., Talaulikar, K., and Psenak, P., Hegde, S., Filsfils, C., Talaulikar, K., and
A. Gulko, "IGP Flexible Algorithm", draft-ietf-lsr-flex- A. Gulko, "IGP Flexible Algorithm", draft-ietf-lsr-flex-
algo-07 (work in progress), April 2020. algo-10 (work in progress), August 2020.
[I-D.ietf-spring-segment-routing] [I-D.ietf-spring-segment-routing]
Filsfils, C., Previdi, S., Ginsberg, L., Decraene, B., Filsfils, C., Previdi, S., Ginsberg, L., Decraene, B.,
Litkowski, S., and R. Shakir, "Segment Routing Litkowski, S., and R. Shakir, "Segment Routing
Architecture", draft-ietf-spring-segment-routing-15 (work Architecture", draft-ietf-spring-segment-routing-15 (work
in progress), January 2018. in progress), January 2018.
[RFC8355] Filsfils, C., Ed., Previdi, S., Ed., Decraene, B., and R. [RFC8355] Filsfils, C., Ed., Previdi, S., Ed., Decraene, B., and R.
Shakir, "Resiliency Use Cases in Source Packet Routing in Shakir, "Resiliency Use Cases in Source Packet Routing in
Networking (SPRING) Networks", RFC 8355, Networking (SPRING) Networks", RFC 8355,
 End of changes. 15 change blocks. 
29 lines changed or deleted 26 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/