draft-ietf-lsr-isis-srv6-extensions-16.txt		draft-ietf-lsr-isis-srv6-extensions-17.txt
	skipping to change at page 1, line 15 ¶		skipping to change at page 1, line 15 ¶
	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: December 20, 2021 Individual		Expires: December 20, 2021 Individual
	B. Decraene		B. Decraene
	Orange		Orange
	Z. Hu		Z. Hu
	Huawei Technologies		Huawei Technologies
	June 18, 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-16		draft-ietf-lsr-isis-srv6-extensions-17
	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 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 Sub-Sub-TLV is intended for informational use by the		The SRv6 SID Structure Sub-Sub-TLV is intended for informational use
	control and management planes. It MUST NOT be used at a transit node		by the control and management planes. It MUST NOT be used at a
	(as defined in [RFC8754]) for forwarding packets. As an example,		transit node (as defined in [RFC8754]) for forwarding packets. As an
	this information could be used for:		example, this information could be used for:
	o validation of SRv6 SIDs being instantiated in the network and		o validation of SRv6 SIDs being instantiated in the network and
	advertised via ISIS. These can be learnt by controllers via BGP-		advertised via ISIS. These can be learnt by controllers via BGP-
	LS and then be monitored for conformance to the SRv6 SID		LS and then be monitored for conformance to the SRv6 SID
	allocation scheme chosen by the operator as described in		allocation scheme chosen by the operator as described in
	Section 3.2 of [RFC8986].		Section 3.2 of [RFC8986].
	o verification and the automation for securing the SRv6 domain by		o verification and the automation for securing the SRv6 domain by
	provisioning filtering rules at SR domain boundaries as described		provisioning filtering rules at SR domain boundaries as described
	in Section 5 of [RFC8754].		in Section 5 of [RFC8754].
End of changes. 2 change blocks.
	5 lines changed or deleted		5 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/