From: The IESG <iesg-secretary@ietf.org>
To: IETF-Announce <ietf-announce@ietf.org>
Cc: spring@ietf.org
Reply-To: iesg@ietf.org
Subject: WG Review: Source Packet Routing in Networking (spring)
The Source Packet Routing in Networking (spring) WG in the Routing Area of
the IETF is undergoing rechartering. The IESG has not made any determination
yet. The following draft charter was submitted, and is provided for
informational purposes only. Please send your comments to the IESG mailing
list (iesg@ietf.org) by 2024-10-28.
Source Packet Routing in Networking (spring)
-----------------------------------------------------------------------
Current status: Active WG
Chairs:
Bruno Decraene <bruno.decraene@orange.com>
Alvaro Retana <aretana.ietf@gmail.com>
Joel Halpern <jmh@joelhalpern.com>
Secretaries:
Shuping Peng <pengshuping@huawei.com>
Assigned Area Director:
Jim Guichard <james.n.guichard@futurewei.com>
Routing Area Directors:
John Scudder <jgs@juniper.net>
Jim Guichard <james.n.guichard@futurewei.com>
Gunter Van de Velde <gunter.van_de_velde@nokia.com>
Mailing list:
Address: spring@ietf.org
To subscribe: https://www.ietf.org/mailman/listinfo/spring
Archive: https://mailarchive.ietf.org/arch/browse/spring/
Group page: https://datatracker.ietf.org/group/spring/
Charter: https://datatracker.ietf.org/doc/charter-ietf-spring/
The Source Packet Routing in NetworkinG (SPRING) Working Group is the
home of Segment Routing (SR) using the MPLS (SR-MPLS) and IPv6 (SRv6)
data planes. The SPRING WG is responsible for defining new applications
for, and specifying extensions to, Segment Routing technologies. It also
serves as a forum to discuss SR-MPLS network operations. The SRv6
Operations (srv6ops) WG is dedicated to the operational aspects of
deploying and managing SRv6 networks.
The work in the SPRING WG should avoid modification to existing data
planes that would make them incompatible with existing deployments.
Where possible, existing control and management plane protocols must
be used within existing architectures to implement the SPRING
function. Any modification of -or extension to- existing
architectures, data planes, or control or management plane protocols
should be carried out in the WGs responsible for the architecture,
data plane, or control or management plane protocol being modified
and in coordination with the SPRING WG, but may be done in SPRING WG
after agreement with all the relevant WG chairs and responsible Area
Directors.
The SPRING WG defines procedures that allow an SR node to steer a packet
through an SR Policy instantiated as an ordered list of instructions
called segments without needing per-path state information at transit
nodes. A network comprising only SR nodes can achieve full path
control (through loose or strict path specification). However, SR
nodes must interoperate through loose routing in existing networks.
By default, Segment Routing operates within a trusted domain and
requires the enforcement of a strict boundary to prevent Segment
Routing packets from entering the trusted domain [rfc8402]. Some
deployments may involve multiple trusted domains and the use of
cross/inter-domain segments. Documents which deal with such
situations need to include a risk analysis and use mechanisms to
validate that the segment list is provided by an authorized entity
and has not been modified in transit.
The SPRING WG will manage its specific work items based on WG
engagement and successful adoption.
The SPRING WG is expected to coordinate and collaborate closely
with the following WGs:
* mpls on the MPLS data plane and associated extensions
* 6man on the IPv6 data plane and associated extensions
* srv6ops on SRv6 operations
As needed, the WG will also collaborate with other WGs to develop
extensions and other SR-related solutions.
Milestones:
WG action announcement
WG Action Announcement
From: The IESG <iesg-secretary@ietf.org>
To: IETF-Announce <ietf-announce@ietf.org>
Cc: The IESG <iesg@ietf.org>,
spring-chairs@ietf.org,
spring@ietf.org
Subject: WG Action: Rechartered Source Packet Routing in Networking (spring)
The Source Packet Routing in Networking (spring) WG in the Routing Area of
the IETF has been rechartered. For additional information, please contact the
Area Directors or the WG Chairs.
Source Packet Routing in Networking (spring)
-----------------------------------------------------------------------
Current status: Active WG
Chairs:
Bruno Decraene <bruno.decraene@orange.com>
Alvaro Retana <aretana.ietf@gmail.com>
Joel Halpern <jmh@joelhalpern.com>
Secretaries:
Shuping Peng <pengshuping@huawei.com>
Assigned Area Director:
Jim Guichard <james.n.guichard@futurewei.com>
Routing Area Directors:
John Scudder <jgs@juniper.net>
Jim Guichard <james.n.guichard@futurewei.com>
Gunter Van de Velde <gunter.van_de_velde@nokia.com>
Mailing list:
Address: spring@ietf.org
To subscribe: https://www.ietf.org/mailman/listinfo/spring
Archive: https://mailarchive.ietf.org/arch/browse/spring/
Group page: https://datatracker.ietf.org/group/spring/
Charter: https://datatracker.ietf.org/doc/charter-ietf-spring/
The Source Packet Routing in NetworkinG (SPRING) Working Group is the
home of Segment Routing (SR) using the MPLS (SR-MPLS) and IPv6 (SRv6)
data planes. The SPRING WG is responsible for defining new applications
for, and specifying extensions to, Segment Routing technologies. It also
serves as a forum to discuss SR-MPLS network operations. The SRv6
Operations (srv6ops) WG is dedicated to the operational aspects of
deploying and managing SRv6 networks.
The work in the SPRING WG should avoid modification to existing data
planes that would make them incompatible with existing deployments.
Where possible, existing control and management plane protocols must
be used within existing architectures to implement the SPRING
function. Any modification of -or extension to- existing
architectures, data planes, or control or management plane protocols
should be carried out in the WGs responsible for the architecture,
data plane, or control or management plane protocol being modified
and in coordination with the SPRING WG, but may be done in SPRING WG
after agreement with all the relevant WG chairs and responsible Area
Directors.
The SPRING WG defines procedures that allow an SR node to steer a packet
through an SR Policy instantiated as an ordered list of instructions
called segments without needing per-path state information at transit
nodes. A network comprising only SR nodes can achieve full path
control (through loose or strict path specification). However, SR
nodes must interoperate through loose routing in existing networks.
By default, Segment Routing operates within a trusted domain and
requires the enforcement of a strict boundary to prevent Segment
Routing packets from entering the trusted domain [rfc8402]. Some
deployments may involve multiple trusted domains and the use of
cross/inter-domain segments. Documents which deal with such
situations need to include a risk analysis and use mechanisms to
validate that the segment list is provided by an authorized entity
and has not been modified in transit.
The SPRING WG will manage its specific work items based on WG
engagement and successful adoption.
The SPRING WG is expected to coordinate and collaborate closely
with the following WGs:
* mpls on the MPLS data plane and associated extensions
* 6man on the IPv6 data plane and associated extensions
* srv6ops on SRv6 operations
As needed, the WG will also collaborate with other WGs to develop
extensions and other SR-related solutions.
Milestones: