Draft: draft-ietf-detnet-mpls

Commentary: Clarifying S - Label procedures ( i.e. , allowing S - Label value per outgoing member flow after PRF ) .
Paragraph (version A):
F-Label(s).
Paragraph (version B):
F-Label(s).  In some PREOF topologies, the node performing
replication will be sending to multiple nodes performing PEF or POF,
and may need to send different S-Label values for the different
member flows for the same DetNet service.
Paragraph (version A):
The Packet Replication Function (PRF) function MAY be supported by an
implementation for outgoing DetNet flows.  The use of the PRF for a
particular DetNet service MUST be provisioned via configuration,
e.g., via the controller plane described in I-D.ietf-detnet-data-
plane-framework.  When replication is configure, the same app-flow
data will be sent over multiple outgoing DetNet member flows using
forwarding sub-layer LSPs.  The same d-CW field value MUST be used on
all outgoing member flows for each replicated MPLS packet.
Paragraph (version B):
The Packet Replication Function (PRF) function MAY be supported by an
implementation for outgoing DetNet flows.  The use of the PRF for a
particular DetNet service MUST be provisioned via configuration,
e.g., via the controller plane described in I-D.ietf-detnet-data-
plane-framework.  When replication is configure, the same app-flow
data will be sent over multiple outgoing DetNet member flows using
forwarding sub-layer LSPs.  An S-Label value MUST be configured per
outgoing member flow.  The same d-CW field value MUST be used on all
outgoing member flows for each replicated MPLS packet.
Paragraph (version A):
When sending a DetNet flow, zero or more F-Labels MAY be pushed on
top of an S-Label by the node pushing an S-Label.  The F-Label(s) to
be pushed when sending a particular DetNet service MUST be
provisioned per DetNet service via configuration, e.g., via the
controller plane discussed in I-D.ietf-detnet-data-plane-framework.
F-Label(s) can also provide context for an S-Label.  To allow for the
omission of F-Label(s), an implementation SHOULD also allow an
outgoing interface to be configured.
Paragraph (version A):
When PRF is supported, the same app-flow data will be sent over
multiple outgoing DetNet member flows using forwarding sub-layer
LSPs.  To support PRF an implementation MUST support the setting of
different sets of F-Labels per DetNet member flow.  To allow for the
omission of F-Labels, an implementation SHOULD also allow multiple
outgoing interfaces to be provisioned.
Paragraph (version B):
When sending a DetNet flow, zero or more F-Labels MAY be pushed on
top of an S-Label by the node pushing an S-Label.  The F-Label(s) to
be pushed when sending a particular DetNet service MUST be
provisioned per outgoing S-Label via configuration, e.g., via the
controller plane discussed in I-D.ietf-detnet-data-plane-framework.
F-Label(s) can also provide context for an S-Label.  To allow for the
omission of F-Label(s), an implementation SHOULD also allow an
outgoing interface to be configured per S-Label.
Paragraph (version B):
Note, when PRF is supported, the same app-flow data will be sent over
multiple outgoing DetNet member flows using forwarding sub-layer
LSPs.  This means that implementation may be sending different sets
of F-Labels per DetNet member flow, each with a different S-Label.
Paragraph (version A):
When multiple sets of outgoing F-Labels or interfaces are provisioned
for a particular DetNet service, a copy of the outgoing packet,
including the pushed S-Label, MUST be made per F-label set and
outgoing interface.  Each set of provisioned F-Labels are then pushed
onto a copy of the packet.  Each copy is then forwarded as described
below in f-labels-all.
Paragraph (version B):
When multiple sets of outgoing F-Labels or interfaces are provisioned
for a particular DetNet service, a copy of the outgoing packet,
including the pushed member flow-specific S-Label, MUST be made per
F-label set and outgoing interface.  Each set of provisioned F-Labels
are then pushed onto a copy of the packet.  Each copy is then
forwarded as described below in f-labels-all.
Paragraph (version A):
The outgoing S-Label for the service.
Paragraph (version B):
The outgoing S-Label for each of the service's outgoing DetNet
(member) flow.