draft-ietf-lsr-isis-srv6-extensions-07.txt   draft-ietf-lsr-isis-srv6-extensions-08.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: September 24, 2020 A. Bashandy Expires: October 25, 2020 A. Bashandy
Individual Individual
B. Decraene B. Decraene
Orange Orange
Z. Hu Z. Hu
Huawei Technologies Huawei Technologies
March 23, 2020 April 23, 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-07.txt draft-ietf-lsr-isis-srv6-extensions-08.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 September 24, 2020. This Internet-Draft will expire on October 25, 2020.
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 44 skipping to change at page 2, line 44
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 . . . . . . . . . . . . . . . . . . . . 18
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. Interoperability Testing. . . . . . . . . . . . . . . . 18 11.4. Arrcus . . . . . . . . . . . . . . . . . . . . . . . . . 18
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 . . . . . . . . . . . . . . . 19 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 . . . . . . . . . . . . . . . . . . . . . . . 20 12.4. MSD Types . . . . . . . . . . . . . . . . . . . . . . . 21
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 . . . . . . . . . . . . . . . . . . . 21 13. Security Considerations . . . . . . . . . . . . . . . . . . . 22
14. Contributors . . . . . . . . . . . . . . . . . . . . . . . . 21 14. Contributors . . . . . . . . . . . . . . . . . . . . . . . . 22
15. References . . . . . . . . . . . . . . . . . . . . . . . . . 22 15. References . . . . . . . . . . . . . . . . . . . . . . . . . 23
15.1. Normative References . . . . . . . . . . . . . . . . . . 22 15.1. Normative References . . . . . . . . . . . . . . . . . . 23
15.2. Informative References . . . . . . . . . . . . . . . . . 24 15.2. Informative References . . . . . . . . . . . . . . . . . 25
15.3. URIs . . . . . . . . . . . . . . . . . . . . . . . . . . 25 15.3. URIs . . . . . . . . . . . . . . . . . . . . . . . . . . 26
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 25 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 26
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 18, line 32 skipping to change at page 18, line 32
11.2. Huawei 11.2. Huawei
Huawei's ISIS SRv6 implementation supports following functionalities: Huawei's ISIS SRv6 implementation supports following functionalities:
Types of SID supported: End, End.X, LAN End.X Types of SID supported: End, End.X, LAN End.X
Intra/Inter area/level support: Yes Intra/Inter area/level support: Yes
Anycast SID support: Yes, no A-flag support (Section 6) Anycast SID support: Yes, no A-flag support (Section 6)
SID Structure Sub-Sub-TLV: No SID Structure Sub-Sub-TLV: Yes
11.3. Juniper 11.3. Juniper
Juniper's ISIS SRv6 implementation supports following Juniper's ISIS SRv6 implementation supports following
functionalities: functionalities:
Types of SID supported: End, End.X, LAN End.X Types of SID supported: End, End.X, LAN End.X
Intra/Inter area/level support: Yes Intra/Inter area/level support: Yes
Anycast SID support: Yes, no A-flag support (Section 6) Anycast SID support: Yes, no A-flag support (Section 6)
SID Structure Sub-Sub-TLV: No SID Structure Sub-Sub-TLV: No
11.4. Interoperability Testing. 11.4. Arrcus
Arrcus's ISIS SRv6 implementation supports following functionalities:
Types of SID supported: End, End.X, LAN End.X
Intra/Inter area/level support: Yes
Anycast SID support: No (Section 6)
SID Structure Sub-Sub-TLV: Yes
11.5. Interoperability Testing.
EANTC interoperability testing has been performed in April 2019. EANTC interoperability testing has been performed in April 2019.
Results can be found at EANTC site [1]. Results can be found at EANTC site [1].
12. IANA Considerations 12. IANA Considerations
This document requests allocation for the following TLVs, sub- TLVs, This document requests allocation for the following TLVs, sub- TLVs,
and sub-sub-TLVs as well updating the ISIS TLV registry and defining and sub-sub-TLVs as well updating the ISIS TLV registry and defining
a new registry. a new registry.
skipping to change at page 23, line 15 skipping to change at page 24, 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-03 (work in progress), draft-ietf-6man-spring-srv6-oam-04 (work in progress),
December 2019. March 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-14 (work in draft-ietf-spring-srv6-network-programming-15 (work in
progress), March 2020. progress), March 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
skipping to change at page 24, line 44 skipping to change at page 25, 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-06 (work in progress), February 2020. algo-07 (work in progress), April 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. 13 change blocks. 
20 lines changed or deleted 32 lines changed or added

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