Draft: draft-ietf-detnet-ip

Commentary: ready for merge - per list discussion 
 Thanks . Changes are OK .
Paragraph (version A):
Explicit Congestion Notification.
Paragraph (version A):
The DetNet IP data plane also allows for optional matching on two
additional data fields.  The optional fields are the ECN Field, as in
RFC3168, and the IPv6 flow label field, as defined in RFC8200.
Paragraph (version B):
The DetNet IP data plane also allows for optional matching on the
IPv6 flow label field, as defined in RFC8200.
Paragraph (version A):
Class of Service (CoS) for DetNet flows carried in IPv6 is provided
using the standard differentiated services code point (DSCP) field
RFC2474 and related mechanisms.  The 2-bit explicit congestion
notification (ECN) RFC3168 field MAY also be used.
Paragraph (version B):
Class of Service (CoS) for DetNet flows carried in IPv6 is provided
using the standard differentiated services code point (DSCP) field
RFC2474 and related mechanisms.
Paragraph (version A):
Quality of Service (QoS) for DetNet service flows carried in IP MUST
be provided locally by the DetNet-aware hosts and routers supporting
DetNet flows.  Such support leverages the underlying network layer
such as 802.1 TSN.  The traffic control mechanisms used to deliver
QoS for IP encapsulated DetNet flows are expected to be defined in a
future document.  From an encapsulation perspective, the combination
of the 6-tuple i.e., the typical 5-tuple enhanced with the DSCP and
previously mentioned two optional fields, uniquely identifies a
DetNet service flow.
Paragraph (version B):
Quality of Service (QoS) for DetNet service flows carried in IP MUST
be provided locally by the DetNet-aware hosts and routers supporting
DetNet flows.  Such support leverages the underlying network layer
such as 802.1 TSN.  The traffic control mechanisms used to deliver
QoS for IP encapsulated DetNet flows are expected to be defined in a
future document.  From an encapsulation perspective, the combination
of the 6-tuple i.e., the typical 5-tuple enhanced with the DSCP and
previously mentioned optional field, uniquely identifies a DetNet
service flow.
Paragraph (version A):
While path selection algorithms and mechanisms are out of scope of
the DetNet data plane definition, it is important to highlight the
implications of DetNet IP flow identification on path selection and
next hops.  As mentioned above, the DetNet IP data plane identifies
flows using "6-tuple" header information as well as two additional
optional header fields.  DetNet generally allows for both flow-
specific traffic treatment and flow-specific next-hops.
Paragraph (version B):
While path selection algorithms and mechanisms are out of scope of
the DetNet data plane definition, it is important to highlight the
implications of DetNet IP flow identification on path selection and
next hops.  As mentioned above, the DetNet IP data plane identifies
flows using "6-tuple" header information as well as the additional
optional header field.  DetNet generally allows for both flow-
specific traffic treatment and flow-specific next-hops.
Paragraph (version A):
From a single node perspective, the aggregation of IP flows impacts
DetNet IP data plane flow identification and resource allocation.  As
discussed above, IP flow identification uses the IP "6-tuple" for
flow identification.  DetNet IP flows can be aggregated using any of
the 6-tuple, or two additional optional fields defined in ip-flow-id.
The use of prefixes, wildcards, lists, and value ranges allows a
DetNet node to identify aggregate DetNet flows.  From a resource
allocation perspective, DetNet nodes must provide service to a
aggregate and not on a component flow basis.
Paragraph (version B):
From a single node perspective, the aggregation of IP flows impacts
DetNet IP data plane flow identification and resource allocation.  As
discussed above, IP flow identification uses the IP "6-tuple" for
flow identification.  DetNet IP flows can be aggregated using any of
the 6-tuple, and an additional optional field defined in ip-flow-id.
The use of prefixes, wildcards, lists, and value ranges allows a
DetNet node to identify aggregate DetNet flows.  From a resource
allocation perspective, DetNet nodes must provide service to a
aggregate and not on a component flow basis.
Paragraph (version A):
These fields are used to support Differentiated Services RFC2474 and
Explicit Congestion Notification RFC3168.  Implementations of this
document MUST support DetNet flow identification based on the IPv4
Type of Service field when processing IPv4 packets, and the IPv6
Traffic Class Field when processing IPv6 packets.  Implementations
MUST support list based matching of DSCP values, where the list is
composed of possible field values that are to be considered when
identifying a specific DetNet flow.  Implementations SHOULD allow for
this field to be ignored for a specific DetNet flow.
Paragraph (version A):
Implementations of this document MUST allow the ECN field to be
ignored as part of DetNet flow identification.  Additionally,
implementations SHOULD support identification of DetNet flows based
on the value carried in the ECN field.  When this field is used to
identify a specific DetNet flow, implementations MUST support a list
of ECN values that match a specific slow.
Paragraph (version B):
These fields are used to support Differentiated Services RFC2474
RFC2475.  Implementations of this document MUST support DetNet flow
identification based on the DSCP field in the IPv4 Type of Service
field when processing IPv4 packets, and the DSCP field in the IPv6
Traffic Class Field when processing IPv6 packets.  Implementations
MUST support list based matching of DSCP values, where the list is
composed of possible field values that are to be considered when
identifying a specific DetNet flow.  Implementations SHOULD allow for
this field to be ignored for a specific DetNet flow.
Paragraph (version A):
If the ECN field is to be used in flow identification.
Matching based on ECN filed values is optional.
Paragraph (version A):
When ECN field is used in flow identification, a list of field
values that may be used by a specific flow.