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

Commentary: IESG review comments resolved in this version 
 MPLSoUDP 
 MPLSoUDP : all 01 - 27 changes done . 
 can be merged once comments integrater , per Jan 27th meeting
Paragraph (version A):
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 B):
S-Labels, A-Labels (when present), 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.
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 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):
To support receive processing an implementation MUST also support the
provisioning of received UDP and IP header information.  The
provisioned information MUST be used to identify incoming app-flows
based on the combination of S-Label and incoming encapsulation header
information.  Normal receive processing as defined in I-D.ietf-
detnet-mpls, including PEF and POF, can then take place.
Paragraph (version A):
Label information (S-label or F-label) to be mapped to UDP/IP
flow.  Note that a single S-Label can map to multiple sets of UPD/
IP information when PREOF is used.
Paragraph (version A):
IPv4 Type of Service or IPv6 Traffic Class Fields.
Paragraph (version A):
This information MUST be provisioned per DetNet flow via
configuration, e.g., via the controller or management plane.
Paragraph (version A):
It is the responsibility of the DetNet controller plane to properly
provision both flow identification information and the flow specific
resources needed to provided the traffic treatment needed to meet
each flow's service requirements.  This applies for aggregated and
individual flows.
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, 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 the receive processing defined in this document, an
implementation MUST also support the provisioning of received UDP and
IP header information.  The provisioned information MUST be used to
identify incoming app-flows based on the combination of S-Label and
incoming encapsulation header information.  Normal receive processing
as defined in I-D.ietf-detnet-mpls, including PEF and POF, can then
take place.
Paragraph (version B):
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):
DSCP Field in either IPv4 Type of Service or IPv6 Traffic Class
Fields.
Paragraph (version B):
This information MUST be provisioned per DetNet flow via
configuration, e.g., via the controller RFC8655 or management plane.
Paragraph (version B):
It is the responsibility of the DetNet controller plane to properly
provision both flow identification information and the flow specific
resources needed to provide the traffic treatment needed to meet each
flow's service requirements.  This applies for aggregated and
individual flows.