FYI RFC 9602 has been published.
"Segment Routing over IPv6 (SRv6) Segment Identifiers in the IPv6 Addressing
Architecture"
May be relevant for some of our documents (e.g., security)
--Bruno
-----Original Message-----
From: rfc-edi...@rfc-editor.org <rfc-edi...@rfc-editor.org>
Sent: Tuesday, October 22, 2024 2:39 AM
To: ietf-annou...@ietf.org; rfc-d...@rfc-editor.org
Cc: rfc-edi...@rfc-editor.org; drafts-update-...@iana.org; i...@ietf.org
Subject: [IPv6]RFC 9602 on Segment Routing over IPv6 (SRv6) Segment Identifiers
in the IPv6 Addressing Architecture
A new Request for Comments is now available in online RFC libraries.
RFC 9602
Title: Segment Routing over IPv6 (SRv6)
Segment Identifiers in the IPv6 Addressing
Architecture
Author: S. Krishnan
Status: Informational
Stream: IETF
Date: October 2024
Mailbox: suresh.krish...@gmail.com
Pages: 7
Updates/Obsoletes/SeeAlso: None
I-D Tag: draft-ietf-6man-sids-06.txt
URL: https://www.rfc-editor.org/info/rfc9602
DOI: 10.17487/RFC9602
Segment Routing over IPv6 (SRv6) uses IPv6 as the underlying data plane. Thus,
Segment Identifiers (SIDs) used by SRv6 can resemble
IPv6 addresses and behave like them while exhibiting slightly different
behaviors in some situations. This document explores the characteristics of
SRv6 SIDs and focuses on the relationship of SRv6 SIDs to the IPv6 Addressing
Architecture. This document allocates and makes a dedicated prefix available
for SRv6 SIDs.
This document is a product of the IPv6 Maintenance Working Group of the IETF.
INFORMATIONAL: This memo provides information for the Internet community.
It does not specify an Internet standard of any kind. Distribution of this memo
is unlimited.
This announcement is sent to the IETF-Announce and rfc-dist lists.
To subscribe or unsubscribe, see
https://www.ietf.org/mailman/listinfo/ietf-announce
https://mailman.rfc-editor.org/mailman/listinfo/rfc-dist
For searching the RFC series, see https://www.rfc-editor.org/search
For downloading RFCs, see https://www.rfc-editor.org/retrieve/bulk
Requests for special distribution should be addressed to either the author of
the RFC in question, or to rfc-edi...@rfc-editor.org. Unless specifically
noted otherwise on the RFC itself, all RFCs are for unlimited distribution.
The RFC Editor Team
Association Management Solutions, LLC
--------------------------------------------------------------------
IETF IPv6 working group mailing list
i...@ietf.org
List Info: https://mailman3.ietf.org/mailman3/lists/i...@ietf.org/
--------------------------------------------------------------------
____________________________________________________________________________________________________________
Ce message et ses pieces jointes peuvent contenir des informations
confidentielles ou privilegiees et ne doivent donc
pas etre diffuses, exploites ou copies sans autorisation. Si vous avez recu ce
message par erreur, veuillez le signaler
a l'expediteur et le detruire ainsi que les pieces jointes. Les messages
electroniques etant susceptibles d'alteration,
Orange decline toute responsabilite si ce message a ete altere, deforme ou
falsifie. Merci.
This message and its attachments may contain confidential or privileged
information that may be protected by law;
they should not be distributed, used or copied without authorisation.
If you have received this email in error, please notify the sender and delete
this message and its attachments.
As emails may be altered, Orange is not liable for messages that have been
modified, changed or falsified.
Thank you.
_______________________________________________
spring mailing list -- spring@ietf.org
To unsubscribe send an email to spring-le...@ietf.org
