Draft: draft-ietf-detnet-mpls-over-tsn

Commentary: Fixing conformance language Adding more definite references for TSN functions ( i.e. , Clause numbers )
Paragraph (version A):
TSN capabilities of the TSN sub-network are made available for MPLS
(DetNet) flows via the protocol interworking function defined in
IEEE8021CB.  For example, applied on the TSN edge port it can convert
an ingress unicast MPLS (DetNet) flow to use a specific Layer-2
multicast destination MAC address and a VLAN, in order to direct the
packet through a specific path inside the bridged network.  A similar
interworking function pair at the other end of the TSN sub-network
would restore the packet to its original Layer-2 destination MAC
address and VLAN.
Paragraph (version B):
TSN capabilities of the TSN sub-network are made available for MPLS
(DetNet) flows via the protocol interworking function defined in
Annex C.5 of IEEE8021CB.  For example, applied on the TSN edge port
it can convert an ingress unicast MPLS (DetNet) flow to use a
specific Layer-2 multicast destination MAC address and a VLAN, in
order to direct the packet through a specific path inside the bridged
network.  A similar interworking function pair at the other end of
the TSN sub-network would restore the packet to its original Layer-2
destination MAC address and VLAN.
Paragraph (version A):
IEEEP8021CBdb defines a Mask-and-Match Stream identification function
that can be used as a passive function for MPLS DetNet flows.
Paragraph (version A):
IEEE8021CB defines an Active Destination MAC and VLAN Stream
identification function, what can replace some Ethernet header fields
namely (1) the destination MAC-address, (2) the VLAN-ID and (3)
priority parameters with alternate values.  Replacement is provided
for the frame passed down the stack from the upper layers or up the
stack from the lower layers.
Paragraph (version B):
Clause 6.8 of IEEEP8021CBdb defines a Mask-and-Match Stream
identification function that can be used as a passive function for
MPLS DetNet flows.
Paragraph (version B):
Clause 6.6 of IEEE8021CB defines an Active Destination MAC and VLAN
Stream identification function, what can replace some Ethernet header
fields namely (1) the destination MAC-address, (2) the VLAN-ID and
(3) priority parameters with alternate values.  Replacement is
provided for the frame passed down the stack from the upper layers or
up the stack from the lower layers.
Paragraph (version A):
This section covers required behavior of a TSN-aware MPLS (DetNet)
node using a TSN sub-network.
Paragraph (version B):
This section covers required behavior of a TSN-aware MPLS (DetNet)
node using a TSN sub-network.  The implementation of TSN packet
processing functions MUST be compliant with the relevant IEEE 802.1
standards.
Paragraph (version A):
A TSN-aware MPLS (DetNet) node implementations MUST support the
Sequencing function and the Sequence encode/decode function as
defined in IEEE8021CB if FRER is used inside the TSN sub-network.
Paragraph (version A):
A TSN-aware MPLS (DetNet) node implementations MUST support the
Stream splitting function and the Individual recovery function as
defined in IEEE8021CB when the node is a replication or elimination
point for FRER.
Paragraph (version A):
TSN Streams supporting DetNet flows may use Frame Replication and
Elimination for Redundancy (FRER) as defined in IEEE8021CB based on
the loss service requirements of the TSN Stream, which is derived
from the DetNet service requirements of the DetNet mapped flow.  The
specific operation of FRER is not modified by the use of DetNet and
follows IEEE8021CB.
Paragraph (version B):
A TSN-aware MPLS (DetNet) node implementations MUST support the
Sequencing function and the Sequence encode/decode function as
defined in Clause 7.4 and 7.6 of IEEE8021CB if FRER is used inside
the TSN sub-network.
Paragraph (version B):
A TSN-aware MPLS (DetNet) node implementations MUST support the
Stream splitting function and the Individual recovery function as
defined in Clause 7.7 and 7.5 of IEEE8021CB when the node is a
replication or elimination point for FRER.
Paragraph (version B):
TSN Streams supporting DetNet flows may use Frame Replication and
Elimination for Redundancy (FRER) as defined in Clause 8. of
IEEE8021CB based on the loss service requirements of the TSN Stream,
which is derived from the DetNet service requirements of the DetNet
mapped flow.  The specific operation of FRER is not modified by the
use of DetNet and follows IEEE8021CB.
Paragraph (version B):
DetNet MPLS related configuration information according to the
DetNet role of the DetNet MPLS node, as per I-D.ietf-detnet-mpls.
Paragraph (version B):
TSN related configuration information according to the TSN role of
the DetNet MPLS node, as per IEEE8021Q, IEEE8021CB and
IEEEP8021CBdb.
Paragraph (version B):
Mapping between DetNet MPLS flow(s) (label information: A-labels,
S-labels and F-labels as defined in I-D.ietf-detnet-mpls) and TSN
Stream(s) (as stream identification information defined in
IEEEP8021CBdb).  Note, that managed objects for TSN Stream
identification can be found in IEEEP8021CBcv.
Paragraph (version B):
This information MUST be provisioned per DetNet flow.
Paragraph (version A):
The security considerations of DetNet in general are discussed in
RFC8655 and I-D.ietf-detnet-security.  DetNet IP data plane specific
considerations are summarized in I-D.ietf-detnet-ip.  Encryption may
provided by an underlying sub-net using MACSec IEEE802.1AE-2018 for
DetNet IP over TSN flows.
Paragraph (version B):
Security considerations for DetNet are described in detail in I-
D.ietf-detnet-security.  General security considerations are
described in RFC8655.  DetNet MPLS data plane specific considerations
are summarized in I-D.ietf-detnet-mpls.  This section considers
exclusively security considerations which are specific to the DetNet
MPLS over TSN sub-network scenario.
Paragraph (version B):
The sub-network between DetNet nodes needs to be subject to
appropriate confidentiality.  Additionally, knowledge of what DetNet/
TSN services are provided by a sub-network may supply information
that can be used in a variety of security attacks.  The ability to
modify information exchanges between connected DetNet nodes may
result in bogus operations.  Therefore, it is important that the
interface between DetNet nodes and TSN sub-network are subject to
authorization, authentication, and encryption.
Paragraph (version B):
The TSN sub-network operates at Layer-2 so various security
mechanisms defined by IEEE can be used to secure the connection
between the DetNet nodes (e.g., encryption may be provided using
MACSec IEEE802.1AE-2018).