Draft: draft-ietf-detnet-ip-over-mpls

Commentary: Looks good to me .
Paragraph (version A):
This document specifies the DetNet data plane operation for IP hosts
and routers that provide DetNet service to IP encapsulated data.  No
DetNet specific encapsulation is defined to support IP flows, rather
existing IP and higher layer protocol header information is used to
support flow identification and DetNet service delivery.
Paragraph (version A):
The DetNet Architecture decomposes the DetNet related data plane
functions into two sub-layers: a service sub-layer and a forwarding
sub-layer.  The service sub-layer is used to provide DetNet service
protection and reordering.  The forwarding sub-layer is used to
provides congestion protection (low loss, assured latency, and
limited reordering).  Since no DetNet specific headers are added to
support DetNet IP flows, only the forwarding sub-layer functions are
supported using the DetNet IP defined by this document.  Service
protection can be provided on a per sub-net basis using technologies
such as MPLS I-D.ietf-detnet-mpls and IEEE802.1 TSN.
Paragraph (version A):
This document provides an overview of the DetNet IP data plane over
MPLS.
Paragraph (version B):
This document specifies use of the IP DetNet encapsulation over an
MPLS network.  It maps the IP data plane encapsulation described in
I-D.ietf-detnet-ip to the DetNet MPLS data plane defined in I-D.ietf-
detnet-mpls.
Paragraph (version A):
An example use of IP over DetNet MPLS follows below.
Paragraph (version B):
An example use of DetNet IP over DetNet MPLS follows below.
Paragraph (version A):
The basic encapsulation approach is to treat a DetNet IP flow as an
app-flow from the DetNet MPLS app perspective.  The corresponding
example DetNet Sub-Network format is shown in fig_dn_ip_mpls_sn_ex.
Paragraph (version A):
In the figure, "IP App-Flow" indicates the payload carried by the
DetNet IP data plane.  "IP" and "NProto" indicate the fields
described in Section 7.1.1.  IP Header Information and Section 7.1.2.
Other Protocol Header Information in I-D.ietf-detnet-ip,
respectively.  "MPLS App-Flow" indicates that an individual DetNet IP
flow is the payload from the perspective of the DetNet MPLS data
plane defined in I-D.ietf-detnet-mpls.
Paragraph (version B):
The basic encapsulation approach is to treat a DetNet IP flow as an
app-flow from the DetNet MPLS perspective.  The corresponding example
DetNet Sub-Network format is shown in fig_dn_ip_mpls_sn_ex.
Paragraph (version B):
In the figure, "App-Flow" indicates the payload carried by the DetNet
IP data plane.  "IP" and "NProto" indicate the fields described in
Section 7.1.1.  IP Header Information and Section 7.1.2.  Other
Protocol Header Information in I-D.ietf-detnet-ip, respectively.
"MPLS App-Flow" indicates that an individual DetNet IP flow is the
payload from the perspective of the DetNet MPLS data plane defined in
I-D.ietf-detnet-mpls.
Paragraph (version A):
A relay node that sends a DetNet IP flow over a DetNet MPLS network
MUST map that single DetNet IP flow into a single app-flow and MUST
process that app-flow in accordance to the procedures defined in I-
D.ietf-detnet-mpls Section 6.1.  PRF MAY be supported for DetNet IP
flows sent over an DetNet MPLS network.  Aggregation MAY be supported
as defined in I-D.ietf-detnet-mpls Section 5.4.  Aggregation
Considerations in I-D.ietf-detnet-ip MAY be used to identify an
individual DetNet IP flow.  The provisioning of the mapping of DetNet
IP flows to DetNet MPLS app-flows MUST be supported via
configuration, e.g., via the controller plane.
Paragraph (version A):
A relay node MAY be provisioned to handle packets received via the
DetNet MPLS data plane as DetNet IP flows.  A single incoming MPLS
app-flow MAY be treated as a single DetNet IP flow, without
examination of IP headers.  Alternatively, packets received via the
DetNet MPLS data plane MAY follow the normal DetNet IP flow
identification procedures defined in I-D.ietf-detnet-ip Section 7.1.
An implementation MUST support the provisioning for handling any
received DetNet MPLS data plane as DetNet IP flows via configuration.
Note that such configuration MAY include support from PEOF on the
incoming DetNet MPLS flow.
Paragraph (version A):
The traffic treatment required for a particular DetNet IP flow is
provisioned via configuration or the controller plane.  When an
DetNet IP flow is sent over DetNet MPLS, a relay node MUST ensure
that the provisioned DetNet IP traffic treatment is provided at the
forwarding sub-layer as described in I-D.ietf-detnet-mpls
Section 5.2.  Note that the PRF function MAY be utilized when sending
IP over MPLS.
Paragraph (version B):
A DetNet relay node (ingress T-PE) that sends a DetNet IP flow over a
DetNet MPLS network MUST map that single DetNet IP flow into a single
MPLS DetNet flow and MUST process it in accordance to the procedures
defined in I-D.ietf-detnet-mpls Section 6.1.  PRF MAY be supported
for DetNet IP flows sent over an DetNet MPLS network.  Aggregation
MAY be supported as defined in I-D.ietf-detnet-mpls Section 5.4.
Aggregation considerations in I-D.ietf-detnet-ip MAY be used to
identify an individual DetNet IP flow.  The provisioning of the
mapping of DetNet IP flows to DetNet MPLS flows MUST be supported via
configuration, e.g., via the controller plane.
Paragraph (version B):
A DetNet relay node (egress T-PE) MAY be provisioned to handle
packets received via the DetNet MPLS data plane as DetNet IP flows.
A single incoming DetNet MPLS flow MAY be treated as a single DetNet
IP flow, without examination of IP headers.  Alternatively, packets
received via the DetNet MPLS data plane MAY follow the normal DetNet
IP flow identification procedures defined in I-D.ietf-detnet-ip
Section 7.1.  An implementation MUST support the provisioning for
handling any received DetNet MPLS data plane as DetNet IP flows via
configuration.  Note that such configuration MAY include support from
PEOF on the incoming DetNet MPLS flow.
Paragraph (version B):
The traffic treatment required for a particular DetNet IP flow is
provisioned via configuration or the controller plane.  When an
DetNet IP flow is sent over DetNet MPLS, a DetNet relay node MUST
ensure that the provisioned DetNet IP traffic treatment is provided
at the forwarding sub-layer as described in I-D.ietf-detnet-mpls
Section 5.2.  Note that the PRF function MAY be utilized when sending
IP over MPLS.
Paragraph (version A):
The security considerations of DetNet in general are discussed in I-
D.ietf-detnet-architecture and I-D.ietf-detnet-security.  Other
security considerations will be added in a future version of this
draft.
Paragraph (version B):
The security considerations of DetNet in general are discussed in I-
D.ietf-detnet-architecture and I-D.ietf-detnet-security.  MPLS and IP
specific security considerations are described in I-D.ietf-detnet-
mpls and I-D.ietf-detnet-ip.  This draft does not have additional
security considerations.