--- 1/draft-ietf-spring-sr-replication-segment-02.txt	2020-10-29 16:13:10.350586076 -0700
+++ 2/draft-ietf-spring-sr-replication-segment-03.txt	2020-10-29 16:13:10.370586579 -0700
@@ -4,21 +4,21 @@
 Intended status: Standards Track                             C. Filsfils
 Expires: May 2, 2021                                           R. Parekh
                                                      Cisco Systems, Inc.
                                                               H. Bidgoli
                                                                    Nokia
                                                                 Z. Zhang
                                                         Juniper Networks
                                                         October 29, 2020
 
         SR Replication Segment for Multi-point Service Delivery
-              draft-ietf-spring-sr-replication-segment-02
+              draft-ietf-spring-sr-replication-segment-03
 
 Abstract
 
    This document describes the SR Replication segment for Multi-point
    service delivery.  A SR Replication segment allows a packet to be
    replicated from a replication node to downstream nodes.
 
 Requirements Language
 
    The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
@@ -140,21 +140,22 @@
    plane.  At a Replication node, the Replication SID is the equivalent
    of Binding SID [I-D.ietf-spring-segment-routing-policy] of a Segment
    Routing Policy.
 
    A packet steered into a Replication segment at a Replication node is
    replicated to each Downstream Node with the Downstream Replication
    SID that is relevant at that node.  A packet is steered into a
    Replication Segment in two ways:
 
    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
       routing.  In this case, the operation for a replicated copy is
       PUSH.
 
    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
    Replication segment will not have any Replication State and the
    operation is NEXT.  At an egress node, the Replication SID MAY be
    used to identify that portion of the multi-point service.  Notice