draft-ietf-spring-sr-replication-segment-02.txt   draft-ietf-spring-sr-replication-segment-03.txt 
skipping to change at page 1, line 15 skipping to change at page 1, line 15
Intended status: Standards Track C. Filsfils Intended status: Standards Track C. Filsfils
Expires: May 2, 2021 R. Parekh Expires: May 2, 2021 R. Parekh
Cisco Systems, Inc. Cisco Systems, Inc.
H. Bidgoli H. Bidgoli
Nokia Nokia
Z. Zhang Z. Zhang
Juniper Networks Juniper Networks
October 29, 2020 October 29, 2020
SR Replication Segment for Multi-point Service Delivery SR Replication Segment for Multi-point Service Delivery
draft-ietf-spring-sr-replication-segment-02 draft-ietf-spring-sr-replication-segment-03
Abstract Abstract
This document describes the SR Replication segment for Multi-point This document describes the SR Replication segment for Multi-point
service delivery. A SR Replication segment allows a packet to be service delivery. A SR Replication segment allows a packet to be
replicated from a replication node to downstream nodes. replicated from a replication node to downstream nodes.
Requirements Language Requirements Language
The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
skipping to change at page 4, line 18 skipping to change at page 4, line 18
plane. At a Replication node, the Replication SID is the equivalent plane. At a Replication node, the Replication SID is the equivalent
of Binding SID [I-D.ietf-spring-segment-routing-policy] of a Segment of Binding SID [I-D.ietf-spring-segment-routing-policy] of a Segment
Routing Policy. Routing Policy.
A packet steered into a Replication segment at a Replication node is A packet steered into a Replication segment at a Replication node is
replicated to each Downstream Node with the Downstream Replication replicated to each Downstream Node with the Downstream Replication
SID that is relevant at that node. A packet is steered into a SID that is relevant at that node. A packet is steered into a
Replication Segment in two ways: Replication Segment in two ways:
o When the Active Segment [RFC8402] is the Replication SID. In this o When the Active Segment [RFC8402] is the Replication SID. In this
case, the operation for a replicated copy is CONTINUE. case, the operation is NEXT followed by a PUSH for a replicated
copy.
o On the root of a multi-point service, based on local policy-based o On the root of a multi-point service, based on local policy-based
routing. In this case, the operation for a replicated copy is routing. In this case, the operation for a replicated copy is
PUSH. PUSH.
If a Downstream Node is an egress (aka leaf) of the multi-point If a Downstream Node is an egress (aka leaf) of the multi-point
service, i.e. no further replication is needed, then that leaf node's service, i.e. no further replication is needed, then that leaf node's
Replication segment will not have any Replication State and the Replication segment will not have any Replication State and the
operation is NEXT. At an egress node, the Replication SID MAY be operation is NEXT. At an egress node, the Replication SID MAY be
used to identify that portion of the multi-point service. Notice used to identify that portion of the multi-point service. Notice
 End of changes. 2 change blocks. 
2 lines changed or deleted 3 lines changed or added

This html diff was produced by rfcdiff 1.48. The latest version is available from http://tools.ietf.org/tools/rfcdiff/