This message starts a three week spring WG Call for Adoption of:
draft-cheng-spring-sr-policy-group-09
(The extra time is due to the holidays.)

This Working Group Call for Adoption ends on 2026-01-13

Abstract:
   Segment Routing is a source routing paradigm that explicitly
   indicates the forwarding path for packets at the ingress node. An SR
   Policy is associated with one or more candidate paths, and each
   candidate path is either dynamic, explicit, or composite. This
   document describes SR Policy Group in MPLS and IPv6 environments and
   illustrates some use cases for parent SR Policy and SR Policy Group
   to provide best practice cases for operators.

Please reply to this message and indicate whether or not you support adoption
of this Internet-Draft by the spring WG. Comments to explain your preference
are greatly appreciated. Please reply to all recipients of this message and
include this message in your response.

WG participants in general, are reminded of the Intellectual
Property Rights (IPR) disclosure obligations described in BCP 79 [2].
Appropriate IPR disclosures required for full conformance with the provisions
of BCP 78 [1] and BCP 79 [2] must be filed, if you are aware of any.
Sanctions available for application to violators of IETF IPR Policy can be
found at [3].  (My thanks to the authors and named contributors, who have all
provided the needed IPR confirmations.)

Thank you.
[1] https://datatracker.ietf.org/doc/bcp78/
[2] https://datatracker.ietf.org/doc/bcp79/
[3] https://datatracker.ietf.org/doc/rfc6701/

The IETF datatracker status page for this Internet-Draft is:
https://datatracker.ietf.org/doc/draft-cheng-spring-sr-policy-group/

There is also an HTMLized version available at:
https://datatracker.ietf.org/doc/html/draft-cheng-spring-sr-policy-group-09

A diff from the previous version is available at:
https://author-tools.ietf.org/iddiff?url2=draft-cheng-spring-sr-policy-group-09

_______________________________________________
spring mailing list -- [email protected]
To unsubscribe send an email to [email protected]

Reply via email to