draft-ietf-lsr-isis-srv6-extensions-15.txt   draft-ietf-lsr-isis-srv6-extensions-16.txt 
Networking Working Group P. Psenak, Ed. Networking Working Group P. Psenak, Ed.
Internet-Draft C. Filsfils Internet-Draft C. Filsfils
Updates: 7370 (if approved) Cisco Systems Updates: 7370 (if approved) Cisco Systems
Intended status: Standards Track A. Bashandy Intended status: Standards Track A. Bashandy
Expires: November 22, 2021 Individual Expires: December 20, 2021 Individual
B. Decraene B. Decraene
Orange Orange
Z. Hu Z. Hu
Huawei Technologies Huawei Technologies
May 21, 2021 June 18, 2021
IS-IS Extensions to Support Segment Routing over IPv6 Dataplane IS-IS Extensions to Support Segment Routing over IPv6 Dataplane
draft-ietf-lsr-isis-srv6-extensions-15 draft-ietf-lsr-isis-srv6-extensions-16
Abstract Abstract
The Segment Routing (SR) architecture allows flexible definition of The Segment Routing (SR) architecture allows flexible definition of
the end-to-end path by encoding it as a sequence of topological the end-to-end path by encoding it as a sequence of topological
elements called "segments". It can be implemented over the MPLS or elements called "segments". It can be implemented over the MPLS or
the IPv6 data plane. This document describes the IS-IS extensions the IPv6 data plane. This document describes the IS-IS extensions
required to support Segment Routing over the IPv6 data plane. required to support Segment Routing over the IPv6 data plane.
This document updates RFC 7370 by modifying an existing registry. This document updates RFC 7370 by modifying an existing registry.
skipping to change at page 2, line 4 skipping to change at page 2, line 4
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 November 22, 2021. This Internet-Draft will expire on December 20, 2021.
Copyright Notice Copyright Notice
Copyright (c) 2021 IETF Trust and the persons identified as the Copyright (c) 2021 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.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. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 18 11. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 18
11.1. SRv6 Locator TLV . . . . . . . . . . . . . . . . . . . . 18 11.1. SRv6 Locator TLV . . . . . . . . . . . . . . . . . . . . 18
11.1.1. SRv6 End SID sub-TLV . . . . . . . . . . . . . . . . 18 11.1.1. SRv6 End SID sub-TLV . . . . . . . . . . . . . . . . 18
11.1.2. Revised sub-TLV table . . . . . . . . . . . . . . . 18 11.1.2. Revised sub-TLV table . . . . . . . . . . . . . . . 19
11.2. SRv6 Capabilities sub-TLV . . . . . . . . . . . . . . . 19 11.2. SRv6 Capabilities sub-TLV . . . . . . . . . . . . . . . 19
11.3. Sub-Sub-TLVs of the SRv6 Capability sub-TLV . . . . . . 19 11.3. Sub-Sub-TLVs of the SRv6 Capability sub-TLV . . . . . . 20
11.4. SRv6 End.X SID and SRv6 LAN End.X SID sub-TLVs . . . . . 19 11.4. SRv6 End.X SID and SRv6 LAN End.X SID sub-TLVs . . . . . 20
11.5. MSD Types . . . . . . . . . . . . . . . . . . . . . . . 20 11.5. MSD Types . . . . . . . . . . . . . . . . . . . . . . . 20
11.6. Sub-Sub-TLVs for SID Sub-TLVs . . . . . . . . . . . . . 20 11.6. Sub-Sub-TLVs for SID Sub-TLVs . . . . . . . . . . . . . 21
11.7. Prefix Attribute Flags Sub-TLV . . . . . . . . . . . . . 21 11.7. Prefix Attribute Flags Sub-TLV . . . . . . . . . . . . . 21
11.8. ISIS SRv6 Capabilities sub-TLV Flags Registry . . . . . 21 11.8. ISIS SRv6 Capabilities sub-TLV Flags Registry . . . . . 22
11.9. ISIS SRv6 Locator TLV Flags Registry . . . . . . . . . . 21 11.9. ISIS SRv6 Locator TLV Flags Registry . . . . . . . . . . 22
11.10. ISIS SRv6 End SID sub-TLV Flags Registry . . . . . . . . 22 11.10. ISIS SRv6 End SID sub-TLV Flags Registry . . . . . . . . 22
11.11. ISIS SRv6 End.X SID and LAN End.X SID sub-TLVs Flags 11.11. ISIS SRv6 End.X SID and LAN End.X SID sub-TLVs Flags
Registry . . . . . . . . . . . . . . . . . . . . . . . . 22 Registry . . . . . . . . . . . . . . . . . . . . . . . . 23
12. Security Considerations . . . . . . . . . . . . . . . . . . . 23 12. Security Considerations . . . . . . . . . . . . . . . . . . . 23
13. Contributors . . . . . . . . . . . . . . . . . . . . . . . . 23 13. Contributors . . . . . . . . . . . . . . . . . . . . . . . . 24
14. Acknowledgments . . . . . . . . . . . . . . . . . . . . . . . 24 14. Acknowledgments . . . . . . . . . . . . . . . . . . . . . . . 25
15. References . . . . . . . . . . . . . . . . . . . . . . . . . 25 15. References . . . . . . . . . . . . . . . . . . . . . . . . . 26
15.1. Normative References . . . . . . . . . . . . . . . . . . 25 15.1. Normative References . . . . . . . . . . . . . . . . . . 26
15.2. Informative References . . . . . . . . . . . . . . . . . 27 15.2. Informative References . . . . . . . . . . . . . . . . . 28
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 27 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 28
1. Introduction 1. Introduction
With Segment Routing (SR) [RFC8402], a node steers a packet through With Segment Routing (SR) [RFC8402], a node steers a packet through
an ordered list of instructions, called segments. an ordered list of instructions, called 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
through the use of the Segment Routing Header defined in [RFC8754]. through the use of the Segment Routing Header defined in [RFC8754].
skipping to change at page 17, line 23 skipping to change at page 17, line 23
ISIS SRv6 SID Structure Sub-Sub-TLV MUST NOT appear more than once in ISIS SRv6 SID Structure Sub-Sub-TLV MUST NOT appear more than once in
its parent Sub-TLV. If it appears more than once in its parent Sub- its parent Sub-TLV. If it appears more than once in its parent Sub-
TLV, the parent Sub-TLV MUST be ignored by the receiver. 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 less than or equal to 128 bits. If the sum of all Sub-TLV MUST be less than or equal to 128 bits. If the sum of all
four sizes advertised in the ISIS SRv6 SID Structure Sub-Sub-TLV is four 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 larger than 128 bits, the parent Sub-TLV MUST be ignored by the
receiver. receiver.
The SRv6 SID Structure Sub-Sub-TLV indicates the structure of the SID The SRv6 SID Sub-Sub-TLV is intended for informational use by the
associated with it. Its usage is outside the scope of this document. control and management planes. It MUST NOT be used at a transit node
(as defined in [RFC8754]) for forwarding packets. As an example,
this information could be used for:
o validation of SRv6 SIDs being instantiated in the network and
advertised via ISIS. These can be learnt by controllers via BGP-
LS and then be monitored for conformance to the SRv6 SID
allocation scheme chosen by the operator as described in
Section 3.2 of [RFC8986].
o verification and the automation for securing the SRv6 domain by
provisioning filtering rules at SR domain boundaries as described
in Section 5 of [RFC8754].
The details of these potential applications are outside the scope of
this document.
10. Advertising Endpoint Behaviors 10. Advertising Endpoint Behaviors
Endpoint behaviors are defined in [RFC8986]. The codepoints for the Endpoint behaviors are defined in [RFC8986]. The codepoints for the
Endpoint behaviors are defined in the "SRv6 Endpoint Behaviors" Endpoint behaviors are defined in the "SRv6 Endpoint Behaviors"
registry defined in [RFC8986]. If a behavior is advertised it MUST registry defined in [RFC8986]. If a behavior is advertised it MUST
only be advertised in the TLV[s] as indicated by "Y" in the table 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 "N" below, and MUST NOT be advertised in the TLV[s] as indicated by "N"
in the table below. in the table below.
 End of changes. 11 change blocks. 
19 lines changed or deleted 34 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/