Draft: draft-ietf-detnet-mpls

Commentary: Thanks for  's fine tuning . 
 cam you review and merge if you 're good with the changes .
Paragraph (version A):
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
identification regardless of which input interface or LSP the packet
arrives on.
Paragraph (version B):
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
identification regardless of which input interface or LSP the packet
arrives on.
Paragraph (version A):
The DetNet-aware forwarder selects the egress DetNet member flow
segment based on the flow identification.  The mapping of ingress
DetNet member flow segment to egress DetNet member flow segment may
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
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.
Paragraph (version A):
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
is such as way that it is available to the packet processor operation
on the next packet in the DetNet flow (which may be a duplicate, a
late packet, or the next packet in sequence.
Paragraph (version A):
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.
Paragraph (version A):
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.
Paragraph (version B):
The DetNet-aware forwarder selects the egress DetNet member flow
segment based on the flow identification.  The mapping of ingress
DetNet member flow segment to egress DetNet member flow segment may
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
replication is also done within the DetNet-aware forwarder.
Paragraph (version B):
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.
Paragraph (version B):
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.
Paragraph (version B):
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
is such away that it is available to the packet processor operation
on the next packet in the DetNet flow (which may be a duplicate, a
late packet, or the next packet in sequence.