Draft: draft-ietf-detnet-mpls

Commentary: Includes changes as asked by  . please do a " make " after review .
Paragraph (version A):
The DetNet Architecture models the DetNet related data plane
functions decomposed into two sub-layers: a service sub-layer and a
forwarding sub-layer.  The service sub-layer is used to provide
DetNet service functions such as protection and reordering.  The
forwarding sub-layer is used to provide forwarding assurance (low
loss, assured latency, and limited reordering).
Paragraph (version B):
The DetNet Architecture models the DetNet related data plane
functions decomposed into two sub-layers: a service sub-layer and a
forwarding sub-layer.  The service sub-layer is used to provide
DetNet service functions such as protection and reordering.  The
forwarding sub-layer is used to provide forwarding assurance (low
loss, assured latency, and limited out-of-order delivery).
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.  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 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 configured, 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):
Note that an implementation MAY wish to constrain the maximum number
sequence numbers that are tracked, on platform-wide or per flow
basis.  Some implementations MAY support the provisioning of the
maximum number sequence numbers that are tracked number on either a
platform-wide or per flow basis.
Paragraph (version B):
Note that an implementation MAY wish to constrain the maximum number
of sequence numbers that are tracked, on platform-wide or per flow
basis.  Some implementations MAY support the provisioning of the
maximum number of sequence numbers that are tracked on either a
platform-wide or per flow basis.
Paragraph (version A):
CoS for DetNet flows carried in PWs and MPLS is provided using the
existing MPLS Differentiated Services (DiffServ) architecture
RFC3270.  Both E-LSP and L-LSP MPLS DiffServ modes MAY be used to
support DetNet flows.  The Traffic Class field (formerly the EXP
field) of an MPLS label follows the definition of RFC5462 and
RFC3270.  The Uniform, Pipe, and Short Pipe DiffServ tunneling and
TTL processing models are described in RFC3270 and RFC3443 and MAY be
used for MPLS LSPs supporting DetNet flows.  MPLS ECN MAY also be
used as defined in ECN RFC5129 and updated by RFC5462.
Paragraph (version B):
CoS for DetNet flows carried in PWs and MPLS is provided using the
existing MPLS Differentiated Services (DiffServ) architecture
RFC3270.  Both E-LSP and L-LSP MPLS DiffServ modes MAY be used to
support DetNet flows.  The Traffic Class field (formerly the EXP
field) of an MPLS label follows the definition of RFC5462 and
RFC3270.  The Uniform, Pipe, and Short Pipe DiffServ tunneling and
TTL processing models are described in RFC3270 and RFC3443 and MAY be
used for MPLS LSPs supporting DetNet flows.  MPLS Explicit Congestion
Notification (ECN) MAY also be used as defined in ECN RFC5129 and
updated by RFC5462.