Original text:
(PWMCW) defined in RFC4385.  An aggregation label (A-Label) is a special case of S-Label used for aggregation. <del> A node operating on a DetNet flow in the Detnet service sub- layer,uses the local context associated with that S-Label, provided by a received F-Label, to determine what local DetNet operation(s) are applied to that packet.  An S-Label may be taken from the platform label space RFC3031, making it unique, enabling DetNet flow </del>  identification regardless of which input interface or LSP the packet arrives on. be statically or dynamically configured.  Additionally the DetNet- aware forwarder does duplicate frame elimination based on the flow identification and the sequence number combination.  The packet <del> replication is also done within the DetNet-aware forwarder.  During elimination and the replication process the sequence number of the DetNet member flow MUST be preserved and copied to the egress DetNet member flow. </del>  The internal design of a relay node is out of scope of this document. However the reader's attention is drawn to the need to make any PREOF state available to the packet processor(s) dealing with packets to which the PREOF functions must be applied, and to maintain that state <del> is such as way that it is available to the packet processor operation </del>  on the next packet in the DetNet flow (which may be a duplicate, a late packet, or the next packet in sequence. <del> 4.5.2. A DetNet Relay node operates in the DetNet forwarding sub-layer . For DetNet using MPLS this processing is performed on the F-Label. This processing is done within an extended forwarder function. Whether an ingress DetNet member flow receives DetNet specific processing depends on how the forwarding is programmed.  Some relay nodes may be DetNet service aware, while others may be unmodified LSRs that only understand how to switch MPLS-TE LSPs. It is also possible to treat the relay node as a transit node, see FAG.  Again, this is entirely up to how the forwarding has been programmed. </del> 4.6. 4.6.1.

Reviewer comments:
Thanks for Don's fine tuning.
NAME cam you review and merge if you're good with the changes.

Revised text:
(PWMCW) defined in RFC4385.  An aggregation label (A-Label) is a special case of S-Label used for aggregation.  <ins> A node operating on a DetNet flow in the Detnet service sub-layer, uses the local context associated with that S-Label, provided by a received F-Label, to determine what local DetNet operation(s) are applied to that packet.  An S-Label may be taken from the platform label space RFC3031, making it unique, enabling DetNet flow </ins> identification regardless of which input interface or LSP the packet arrives on. be statically or dynamically configured.  Additionally the DetNet- aware forwarder does duplicate frame elimination based on the flow identification and the sequence number combination.  The packet  <ins> replication is also done within the DetNet-aware forwarder. 4.5.2. A DetNet Relay node operates in the DetNet forwarding sub-layer and service sub-layer.  For DetNet using MPLS forwarding related processing is performed on the F-Label.  This processing is done within an extended forwarder function.  Whether an ingress DetNet member flow receives DetNet specific processing depends on how the forwarding is programmed.  Some relay nodes may be DetNet service aware for certain DetNet services, while for other DetNet services these nodes may perform as unmodified LSRs that only understand how to switch MPLS-TE LSPs, i.e., as a transit nodes, see FAG.  Again, this is entirely up to how the forwarding has been programmed. During the elimination and replication process the sequence number of the ingress DetNet member flow MUST be preserved and copied to the corresponding egress DetNet member flow.  Specifically, a relay node sends the same sequence number in an outgoing packet of a DetNet member flow that is received in the corresponding incoming packet of a DetNet compound flow.  This is true whether or not PREOF is performed at the relay node. </ins> The internal design of a relay node is out of scope of this document. However the reader's attention is drawn to the need to make any PREOF state available to the packet processor(s) dealing with packets to which the PREOF functions must be applied, and to maintain that state  <ins> is such away that it is available to the packet processor operation </ins> on the next packet in the DetNet flow (which may be a duplicate, a late packet, or the next packet in sequence.  4.6. 4.6.1.