[rtgwg] Re: draft-ietf-rtgwg-srv6-egress-protection-21.txt

[[e-mail]]

From: 何涛(联通集团本部) <[e-mail]>
Sent: Wednesday, November 19, 2025 4:09 AM
To: DECRAENE Bruno INNOV/NET <[e-mail]>
Cc: rtgwg <[e-mail]>
Subject: Re: [rtgwg] draft-ietf-rtgwg-srv6-egress-protection-21.txt

Hi Bruno，
          The code point values for ISIS and OSPFv3 have not yet been officially assigned by IANA. I will update the draft to remove them.

Thank you.
Are you aware of implementations using those code points?

Additionally, please let us know that as the draft progresses, should we apply for these code point values ourselves through IANA, or will the working group handle the application? Thank you!

I guess you should see this with the chairs.
Possibly one related question is whether you have a (planned) implementation or not. (as a priori, early allocation mostly make sense for (a production grade) implementation).

--Bruno


In the IANA website, we can see the Registration Procedures as below,
[cid:[e-mail]418E0]

[cid:[e-mail]418E0]

Best Regards！

===============================================
Tao He
Next Generation Internet Research Department
Research Institute
CHINA UNITED NETWORK COMMUNICATIONS CORPORATION LIMITED
Mobile: [phone]
E-mail: [e-mail]<mailto:[e-mail]>

From: bruno.decraene<mailto:[e-mail]>
Date: 2025-11-17 19:01
To: [e-mail]<mailto:[e-mail]>
Subject: [rtgwg] draft-ietf-rtgwg-srv6-egress-protection-21.txt
【本邮件为外部邮件，请注意核实发件人身份，并谨慎处理邮件内容中的链接及附件】
Hi authors,

The draft and the IANA section is listing code points values for IS-IS and OSPF.

Have those been allocated by the IANA?

If not, this is squatting on code points and typically leads to issues in live networks (plus burning of useful code points).
Please remove those code points from the draft.

Thanks,
Regards,
--Bruno
-----Original Message-----
From: [e-mail]<mailto:[e-mail]> <[e-mail]<mailto:[e-mail]>>
Sent: Sunday, November 16, 2025 9:49 AM
To: [e-mail]<mailto:[e-mail]>
Cc: [e-mail]<mailto:[e-mail]>
Subject: [rtgwg] I-D Action: draft-ietf-rtgwg-srv6-egress-protection-21.txt

--------------------------------------------------------------------------------------------------------------
CAUTION : This email originated outside the company. Do not click on any links or open attachments unless you are expecting them from the sender.

ATTENTION : Cet e-mail provient de l'extérieur de l'entreprise. Ne cliquez pas sur les liens ou n'ouvrez pas les pièces jointes à moins de connaitre l'expéditeur.
--------------------------------------------------------------------------------------------------------------

Internet-Draft draft-ietf-rtgwg-srv6-egress-protection-21.txt is now
available. It is a work item of the Routing Area Working Group (RTGWG) WG of
the IETF.

   Title:   SRv6 Path Egress Protection
   Authors: Tao He
            Zhibo Hu
            Huaimo Chen
            Mehmet Toy
            Chang Cao
   Name:    draft-ietf-rtgwg-srv6-egress-protection-21.txt
   Pages:   22
   Dates:   2025-11-16

Abstract:

   TI-LFA specifies fast protections for transit nodes and links of an
   SR path.  However, it does not present any fast protections for the
   egress node of the SR path.  This document describes protocol
   extensions for fast protecting the egress node and link of a Segment
   Routing for IPv6 (SRv6) path.  The solution uses IGP extensions and a
   Mirror SID (End.M) behavior to steer traffic to a protector egress
   upon failure of the primary egress.

   This document operates within a single link-state IGP area/level and
   uses IS-IS/OSPFv3 to advertise a Mirror SID and the protected
   locators for egress node/link protection.  While the mechanism can
   protect traffic whose active segment at the egress is a Service SID
   (e.g., VPN SID), it is not suitable for large-scale deployments with
   a high cardinality of VPN/service instances or random multi-homing
   patterns, because the amount of egress-protection information to be
   flooded in the IGP increases and may impact convergence and control-
   plane load.

The IETF datatracker status page for this Internet-Draft is:
https://datatracker.ietf.org/doc/draft-ietf-rtgwg-srv6-egress-protection/

There is also an HTML version available at:
https://www.ietf.org/archive/id/draft-ietf-rtgwg-srv6-egress-protection-21.html

A diff from the previous version is available at:
https://author-tools.ietf.org/iddiff?url2=draft-ietf-rtgwg-srv6-egress-protection-21

Internet-Drafts are also available by rsync at:
rsync.ietf.org::internet-drafts


_______________________________________________
rtgwg mailing list -- [e-mail]<mailto:[e-mail]>
To unsubscribe send an email to [e-mail]<mailto:[e-mail]>
____________________________________________________________________________________________________________
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.

_______________________________________________
rtgwg mailing list -- [e-mail]<mailto:[e-mail]>
To unsubscribe send an email to [e-mail]<mailto:[e-mail]>
____________________________________________________________________________________________________________
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.