Draft: draft-ietf-detnet-dp-sol-mpls-00

Commentary: Hopefully my original was synced . If not reject the changes and I will fix up the fork and reapply the changes . 
 Jouni and  , I just downloaded the xml and tried to compile it on the IETF tools site . It fails on line 1143 : [  's note : when this section is re - written a reference to <     be included ] " PTI - section " is undefined . Cheers ,  
 ack . i ’ll check this . 
 The missing declaration is : < section title="Indication of the DetNet Payload Type " anchor="PTI - section"-  
 A bit more context < section title="DetNet data plane overview " anchor="secdtdp"within the DetNet domain . Thus the S - label can only be used to identify the DetNet flow at the intended receiving node . < /t</section < section title="Indication of the DetNet Payload Type " anchor="PTI - section"<tThe only nodes that needs to know the payload type of a flow are the DetNet ingress node and the DetNet egress nodes . The ingress node has to know how to process the packet it receives from the ingress AC , and egress edge node has to know how to < t[Editor 's note : quite a bit of unfinished and old text in the following sections . ] < /t < t</t < t[Editor 's note : when this section is re - written a reference to <     be included ] < /t < tThe edge and relay node internal procedures of the PROEF are implementation specific . The order    again . 
 Thanks ! Mostly looks great . I just noticed a typo on p. 29 : As in Section 6.2 , the S - Label is used to identify a DetNet flow to the peer node that processes it , in this case the node addressed by the IP Header in Figure 14 . The S - Label is allocated from the receiving  platform label space [ RFC3031 ] . In the last line of that paragraph , the second word should be “ node ’s ” . Obviously a character set error . Cheers ,  ,   < :
The simplest DetNet service is to provide bridging (i.e., tunneling
for L2), where the connected hosts are in the same broadcast (BC)
domain.  Forwarding over the DetNet domain is based on L2 (MAC)
addresses (i.e. dst-MAC), so L2 headers MUST be kept.  For both IP
and MPLS PSN a DetNet specific tunnel encapsulation MUST be
introduced.
As shown on the figure both L2 and L3 end-systems can be served by
such a DetNet Bridging service.
DetNet Routing service provides routing, therefore available only for
L3 hosts that are in different BC domains.  Forwarding over the
DetNet domain is based on L3 (IP) addresses (i.e. dst-IP).
In case of an MPLS PSN at the ingress/egress (i.e., PE nodes of
DetNet domain) the IP packets are encapsulated in MPLS.  The data-
flow IP header MUST be preserved as-is.
The simplest DetNet service is to provide tunneling for layer two,
where the connected hosts are in the same broadcast (BC) domain.
Forwarding over the DetNet domain is based on L2 (MAC) addresses
(i.e. dst-MAC), or on received interface RFC3985.  In both cases the
L2 headers MUST either be kept, or provision must be made for their
reconstruction at egress from the DetNet domain.
DetNet Routing service provides routing.  Forwarding over the DetNet
domain is based on L3 (IP) addresses (i.e. dst-IP).  In case of an
MPLS PSN at the ingress/egress (i.e., PE nodes of DetNet domain) the
IP packets are encapsulated in MPLS.  The data-flow IP header MUST be
preserved as-is.
This section specifies the DetNet encapsulation over an IP transport
network.  The approach is modeled on the operation of MPLS and
PseudoWires (PW) over an IP Packet Switched Network (PSN) RFC7510.
It is also based on the MPLS data plane encapsulation described in
pwSolution.
A method of identifying the DetNet flow group to the processing
element.
A method of carrying the DetNet sequence number.
A method of distinguishing DetNet OAM packets from DetNet data
packets.
A method of carrying queuing and forwarding indication.
These requirements are satisfied by the DetNet over MPLS
Encapsulation described in pwSolution.
Where the UDP header is used as defined in Section 3 of RFC7510.
As in pwSolution, the S-Label is used to identify a DetNet flow to
the peer node that processes it, in this case the node addressed by
the IP Header in IP-encap-dn.  The S-Label is allocated from the
receiving node?s platform label space RFC3031.
In ingress Edge Nodes, the encapsulation in IP-encap-dn will be
imposed on Detnet Flow Payload Packets as received from DetNet End
Systems, and the encapsulation will be removed in egress Edge Nodes
as they transmit the Payload Packets to the End Systems.
Note that this encapsulation works equally well with IPv4 and IPv6.
Again, the UDP header is used as defined in Section 3 of RFC7510.