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

Commentary: Looks good to me ,
Paragraph (version A):
Deterministic Networking (DetNet) is a service that can be offered by
a network to DetNet flows.  DetNet provides these flows with a low
packet loss rates and assured maximum end-to-end delivery latency.
General background and concepts of DetNet can be found in I-D.ietf-
detnet-architecture.
Paragraph (version B):
Deterministic Networking (DetNet) is a service that can be offered by
a network to DetNet flows.  DetNet provides these flows extremely low
packet loss rates and assured maximum end-to-end delivery latency.
General background and concepts of DetNet can be found in RFC8655.
Paragraph (version A):
A method of identifying the DetNet flow group to the processing
element.
Paragraph (version A):
A method of carrying the DetNet sequence number.
Paragraph (version A):
A method of distinguishing DetNet OAM packets from DetNet data
packets.
Paragraph (version A):
A method of carrying queuing and forwarding indication.
Paragraph (version B):
A method for identifying DetNet flows to the processing element.
Paragraph (version B):
A method for carrying the DetNet sequence number.
Paragraph (version B):
A method for distinguishing DetNet OAM packets from DetNet data
packets.
Paragraph (version B):
A method for carrying queuing and forwarding indication.
Paragraph (version A):
This document uses the terminology established in the DetNet
architecture I-D.ietf-detnet-architecture, and the reader is assumed
to be familiar with that document and its terminology.
Paragraph (version B):
This document uses the terminology established in the DetNet
architecture RFC8655, and the reader is assumed to be familiar with
that document and its terminology.
Paragraph (version A):
A DetNet "service" label that is used between DetNet nodes that
implement also the DetNet service sub-layer functions.  An S-Label
is also used to identify a DetNet flow at DetNet service sub-
layer.
Paragraph (version B):
Packet Replication, Elimination and Ordering Functions.
Paragraph (version B):
A DetNet "service" label that is used between DetNet nodes that
also implement the DetNet service sub-layer functions.  An S-Label
is also used to identify a DetNet flow at DetNet service sub-
layer.
Paragraph (version A):
d-CW, S-Labels and zero or more F-Labels are used as defined in I-
D.ietf-detnet-mpls and are not modified by this document.  In case of
aggregates the A-Label is treated as an S-Label and it too is not
modified.
Paragraph (version B):
S-Labels, d-CW and zero or more F-Labels are used as defined in I-
D.ietf-detnet-mpls and are not modified by this document.  In case of
aggregates the A-Label is treated as an S-Label and it too is not
modified.
Paragraph (version A):
To support outgoing DetNet MPLS over UDP/IP encapsulation, an
implementation MUST support the provisioning of UDP and IP header
information in addition or in place of F-Label(s).  Note, when PRF is
performed at the MPLS service sub-layer, there will be multiple
member flows, and each member flow will require the provisioning of
their own UDP and IP header information.  The headers for each
outgoing packet MUST be formatted on the configuration information
and as defined in RFC7510, with one exception.  Note that the UDP
Source Port value MUST be set to uniquely identify the DetNet flow.
The packet MUST then be handed as a DetNet IP packet, per I-D.ietf-
detnet-ip.  This includes QoS related traffic treatment.
Paragraph (version B):
To support outgoing DetNet MPLS over UDP/IP encapsulation, an
implementation MUST support the provisioning of UDP and IP header
information in addition or in place of F-Label(s).  Note, when PRF is
performed at the MPLS service sub-layer, there will be multiple
member flows, and each member flow will require the provisioning of
their own UDP and IP header information.  The headers for each
outgoing packet MUST be formatted according to the configuration
information and as defined in RFC7510, with one exception.  Note that
the UDP Source Port value MUST be set to uniquely identify the DetNet
flow.  The packet MUST then be handed as a DetNet IP packet, per I-
D.ietf-detnet-ip.  This includes QoS related traffic treatment.
Paragraph (version A):
IPv4 and IPv6 source address field.
Paragraph (version A):
IPv4 and IPv6 destination address field.
Paragraph (version A):
IPv4 Type of Service and IPv6 Traffic Class Fields.
Paragraph (version B):
IPv4 or IPv6 source address field.
Paragraph (version B):
IPv4 or IPv6 destination address field.
Paragraph (version B):
IPv4 Type of Service or IPv6 Traffic Class Fields.
Paragraph (version A):
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.
Paragraph (version B):
The security considerations of DetNet in general are discussed in
RFC8655 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.