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

Commentary: Many small nits .
Paragraph (version A):
This document specifies the MPLS Deterministic Networking data plane
operation and encapsulation over an IP network.  The approach is
modeled on the operation of MPLS and over UDP/IP packet switched
networks.
Paragraph (version B):
This document specifies the MPLS Deterministic Networking data plane
operation and encapsulation over an IP network.  The approach is
based on the operation of MPLS-in-UDP technology.
Paragraph (version A):
A method for carrying queuing and forwarding indication.
Paragraph (version B):
A method for carrying queueing and forwarding indication.
Paragraph (version A):
Note that this encapsulation works equally well with IPv4, IPv6, and
IPv6-based Segment Routing I-D.ietf-6man-segment-routing-header.
Paragraph (version B):
Note that this encapsulation works equally well with IPv4, IPv6, and
IPv6-based Segment Routing RFC8754.
Paragraph (version A):
To support outgoing DetNet MPLS over UDP 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, and the UDP Source Port value
MUST be set to uniquely identify the DetNet flow.  The packet MUST
then be handled 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 encapsulation, an
implementation MUST support the provisioning of UDP and IP header
information in addition to 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, and the UDP Source Port value
MUST be set to uniquely identify the DetNet flow.  The packet MUST
then be handled as a DetNet IP packet, per I-D.ietf-detnet-ip.  This
includes QoS related traffic treatment.
Paragraph (version A):
Label information (A-labels, S-labels and F-labels) to be mapped
to UDP/IP flow.  Note that for example, a single S-Label can map
to multiple sets of UDP/IP information when PREOF is used.
Paragraph (version B):
Label information (A-labels, S-labels and F-labels) to be mapped
to UDP/IP flows.  Note that for example, a single S-Label can map
to multiple sets of UDP/IP information when PREOF is used.
Paragraph (version A):
The solution defined in this document reuses mechanisms specified in
other documents, and the security considerations in those documents
apply equally to this document.  Notably RFC7510, as this document is
primarily an application of MPLS-in-UDP.  Additionally, the security
considerations of DetNet in general are discussed in RFC8655 and I-
D.ietf-detnet-security.  Finally,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 solution defined in this document reuses mechanisms specified in
other documents, and the security considerations in those documents
apply equally to this document.  Of particular note is RFC7510, as
this document is primarily an application of MPLS-in-UDP.
Additionally, the security considerations of DetNet in general are
discussed in RFC8655 and I-D.ietf-detnet-security.  Finally, 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.