Diff: rfc9602v3.txt - rfc9602.txt

	rfc9602v3.txt	rfc9602.txt

	Internet Engineering Task Force (IETF) S. Krishnan	Internet Engineering Task Force (IETF) S. Krishnan
	Request for Comments: 9602 Cisco	Request for Comments: 9602 Cisco

	Category: Informational September 2024	Category: Informational October 2024
	ISSN: 2070-1721	ISSN: 2070-1721

	Segment Routing over IPv6 (SRv6) Segment Identifiers in the IPv6	Segment Routing over IPv6 (SRv6) Segment Identifiers in the IPv6
	Addressing Architecture	Addressing Architecture

	Abstract	Abstract

	Segment Routing over IPv6 (SRv6) uses IPv6 as the underlying data	Segment Routing over IPv6 (SRv6) uses IPv6 as the underlying data
	plane. Thus, Segment Identifiers (SIDs) used by SRv6 can resemble	plane. Thus, Segment Identifiers (SIDs) used by SRv6 can resemble
	IPv6 addresses and behave like them while exhibiting slightly	IPv6 addresses and behave like them while exhibiting slightly

	skipping to change at line 57 ¶	skipping to change at line 57 ¶
	include Revised BSD License text as described in Section 4.e of the	include Revised BSD License text as described in Section 4.e of the
	Trust Legal Provisions and are provided without warranty as described	Trust Legal Provisions and are provided without warranty as described
	in the Revised BSD License.	in the Revised BSD License.

	Table of Contents	Table of Contents

	1. Introduction	1. Introduction
	2. Terminology	2. Terminology
	3. SRv6 SIDs and the IPv6 Addressing Architecture	3. SRv6 SIDs and the IPv6 Addressing Architecture
	4. Special Considerations for Compressed SIDs	4. Special Considerations for Compressed SIDs

	5. Allocation of a Global Unicast Prefix for SIDs	5. Allocation of a Prefix for SIDs
	6. IANA Considerations	6. IANA Considerations
	7. Security Considerations	7. Security Considerations
	8. References	8. References
	8.1. Normative References	8.1. Normative References
	8.2. Informative References	8.2. Informative References
	Acknowledgments	Acknowledgments
	Author's Address	Author's Address

	1. Introduction	1. Introduction


	skipping to change at line 188 ¶	skipping to change at line 188 ¶
	processing a segment in the SRH.	processing a segment in the SRH.

	One key thing to note here is that the Locator Block at the beginning	One key thing to note here is that the Locator Block at the beginning
	of the address does not get modified by the operations needed for	of the address does not get modified by the operations needed for
	supporting C-SIDs. As we have established that the SRv6 SIDs are	supporting C-SIDs. As we have established that the SRv6 SIDs are
	being treated simply as routing prefixes on transit nodes within the	being treated simply as routing prefixes on transit nodes within the
	SR Domain, this does not constitute a modification to the IPv6 data	SR Domain, this does not constitute a modification to the IPv6 data
	plane on such transit nodes: any changes are restricted to SR-aware	plane on such transit nodes: any changes are restricted to SR-aware
	nodes.	nodes.


	5. Allocation of a Global Unicast Prefix for SIDs	5. Allocation of a Prefix for SIDs

	All of the SRv6-related specifications discussed above are intended	All of the SRv6-related specifications discussed above are intended
	to be applicable to a contained SR Domain or between collaborating SR	to be applicable to a contained SR Domain or between collaborating SR
	Domains. Nodes either inside or outside the SR Domains that are not	Domains. Nodes either inside or outside the SR Domains that are not
	SR-aware will not perform any special behavior for SRv6 SIDs and will	SR-aware will not perform any special behavior for SRv6 SIDs and will
	treat them solely as IPv6 routing prefixes.	treat them solely as IPv6 routing prefixes.

	As an added factor of security, it is desirable to allocate some	As an added factor of security, it is desirable to allocate some
	address space that explicitly signals that the addresses within that	address space that explicitly signals that the addresses within that
	space cannot be expected to comply with [RFC4291]. As described in	space cannot be expected to comply with [RFC4291]. As described in

	skipping to change at line 214 ¶	skipping to change at line 214 ¶

	At the time of writing, global DNS [RFC9499] SHOULD NOT reference	At the time of writing, global DNS [RFC9499] SHOULD NOT reference
	addresses assigned from this block. Further specifications are	addresses assigned from this block. Further specifications are
	needed to describe the conventions and guidelines for the use of this	needed to describe the conventions and guidelines for the use of this
	newly allocated address block. The SRv6 operational community, which	newly allocated address block. The SRv6 operational community, which
	is the first intended user of this block, is requested to come up	is the first intended user of this block, is requested to come up
	with such conventions and guidelines in line with their requirements.	with such conventions and guidelines in line with their requirements.

	6. IANA Considerations	6. IANA Considerations


	IANA has assigned the following /16 address block from the "IPv6	IANA has assigned the following /16 address block for the purposes
	Unicast Address Assignments" registry [UNICAST] for the purposes
	described in Section 5 and recorded the allocation in the "IANA IPv6	described in Section 5 and recorded the allocation in the "IANA IPv6
	Special-Purpose Address Registry" [SPECIAL] as follows:	Special-Purpose Address Registry" [SPECIAL] as follows:

	Address Block:	Address Block:
	5f00::/16	5f00::/16

	Name:	Name:
	Segment Routing (SRv6) SIDs	Segment Routing (SRv6) SIDs

	RFC:	RFC:

	skipping to change at line 340 ¶	skipping to change at line 339 ¶
	2014, <https://www.rfc-editor.org/info/rfc7343>.	2014, <https://www.rfc-editor.org/info/rfc7343>.

	[RFC9499] Hoffman, P. and K. Fujiwara, "DNS Terminology", BCP 219,	[RFC9499] Hoffman, P. and K. Fujiwara, "DNS Terminology", BCP 219,
	RFC 9499, DOI 10.17487/RFC9499, March 2024,	RFC 9499, DOI 10.17487/RFC9499, March 2024,
	<https://www.rfc-editor.org/info/rfc9499>.	<https://www.rfc-editor.org/info/rfc9499>.

	[SPECIAL] IANA, "IANA IPv6 Special-Purpose Address Registry",	[SPECIAL] IANA, "IANA IPv6 Special-Purpose Address Registry",
	<https://www.iana.org/assignments/iana-ipv6-special-	<https://www.iana.org/assignments/iana-ipv6-special-
	registry>.	registry>.


	[UNICAST] IANA, "IPv6 Global Unicast Address Assignments",
	<https://www.iana.org/assignments/ipv6-unicast-address-
	assignments>.

	Acknowledgments	Acknowledgments

	The author would like to extend a special note of thanks to Brian	The author would like to extend a special note of thanks to Brian
	Carpenter and Erik Kline for their precisely summarized thoughts on	Carpenter and Erik Kline for their precisely summarized thoughts on
	this topic that provided the seed of this document. The author would	this topic that provided the seed of this document. The author would
	also like to thank Andrew Alston, Fred Baker, Ron Bonica, Nick	also like to thank Andrew Alston, Fred Baker, Ron Bonica, Nick
	Buraglio, Bruno Decraene, Dhruv Dhody, Darren Dukes, Linda Dunbar,	Buraglio, Bruno Decraene, Dhruv Dhody, Darren Dukes, Linda Dunbar,
	Reese Enghardt, Adrian Farrel, Clarence Filsfils, Jim Guichard, Joel	Reese Enghardt, Adrian Farrel, Clarence Filsfils, Jim Guichard, Joel
	Halpern, Ted Hardie, Bob Hinden, Murray Kucherawy, Cheng Li, Acee	Halpern, Ted Hardie, Bob Hinden, Murray Kucherawy, Cheng Li, Acee
	Lindem, Jen Linkova, Gyan Mishra, Yingzhen Qu, Robert Raszuk, Alvaro	Lindem, Jen Linkova, Gyan Mishra, Yingzhen Qu, Robert Raszuk, Alvaro

End of changes. 5 change blocks.
	9 lines changed or deleted	4 lines changed or added
This html diff was produced by rfcdiff 1.48.