Original text:
TSN capabilities of the TSN sub-network are made available for MPLS (DetNet) flows via the protocol interworking function defined in <del> 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. </del>  Placement of TSN functions depends on the TSN capabilities of nodes. MPLS (DetNet) Nodes may or may not support TSN functions.  For a the active stream identification function is used to modify the Ethernet header according to the ID of the mapped TSN Stream. <del> IEEEP8021CBdb defines a Mask-and-Match Stream identification function that can be used as a passive function for MPLS DetNet flows. </del>  <del> 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. </del>  Active Destination MAC and VLAN Stream identification can be used within a Talker to set flow identity or a Listener to recover the 4.2. This section covers required behavior of a TSN-aware MPLS (DetNet) <del> node using a TSN sub-network. </del>  From the TSN sub-network perspective MPLS (DetNet) nodes are treated as Talker or Listener, that may be (1) TSN-unaware or (2) TSN-aware. A TSN-aware MPLS (DetNet) node implementations MUST support the Sequencing function and the Sequence encode/decode function as <del> defined in IEEE8021CB if FRER is used inside the TSN sub-network. </del>  The Sequence encode/decode function MUST support the Redundancy tag (R-TAG) format as per Clause 7.8 of IEEE8021CB. A TSN-aware MPLS (DetNet) node implementations MUST support the Stream splitting function and the Individual recovery function as <del> defined in IEEE8021CB when the node is a replication or elimination point for FRER. </del>  4.3. TSN Streams supporting DetNet flows may use Frame Replication and <del> 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. </del>  FRER function and the provided service recovery is available only within the TSN sub-network as the TSN Stream-ID and the TSN sequence perspective there is no practical difference based on the origin of flow mapping related information (management plane or control plane).  TSN-aware MPLS DetNet nodes are member of both the DetNet domain and the TSN sub-network.  Within the TSN sub-network the TSN-aware MPLS (DetNet) node has a TSN-aware Talker/Listener role, so TSN specific 6. <del> 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. </del>  7.

Reviewer comments:
Fixing conformance language Adding more definite references for TSN functions (i.e., Clause numbers)

Revised text:
TSN capabilities of the TSN sub-network are made available for MPLS (DetNet) flows via the protocol interworking function defined in  <ins> 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. </ins> Placement of TSN functions depends on the TSN capabilities of nodes. MPLS (DetNet) Nodes may or may not support TSN functions.  For a the active stream identification function is used to modify the Ethernet header according to the ID of the mapped TSN Stream.  <ins> 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. </ins>  <ins> 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. </ins> Active Destination MAC and VLAN Stream identification can be used within a Talker to set flow identity or a Listener to recover the 4.2. This section covers required behavior of a TSN-aware MPLS (DetNet)  <ins> node using a TSN sub-network.  The implementation of TSN packet processing functions MUST be compliant with the relevant IEEE 802.1 standards. </ins> From the TSN sub-network perspective MPLS (DetNet) nodes are treated as Talker or Listener, that may be (1) TSN-unaware or (2) TSN-aware. A TSN-aware MPLS (DetNet) node implementations MUST support the Sequencing function and the Sequence encode/decode function as  <ins> defined in Clause 7.4 and 7.6 of IEEE8021CB if FRER is used inside the TSN sub-network. </ins> The Sequence encode/decode function MUST support the Redundancy tag (R-TAG) format as per Clause 7.8 of IEEE8021CB. A TSN-aware MPLS (DetNet) node implementations MUST support the Stream splitting function and the Individual recovery function as  <ins> defined in Clause 7.7 and 7.5 of IEEE8021CB when the node is a replication or elimination point for FRER. </ins> 4.3. TSN Streams supporting DetNet flows may use Frame Replication and  <ins> 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. </ins> FRER function and the provided service recovery is available only within the TSN sub-network as the TSN Stream-ID and the TSN sequence perspective there is no practical difference based on the origin of flow mapping related information (management plane or control plane). <ins> The following summarizes the set of information that is needed to configure DetNet MPLS over TSN: DetNet MPLS related configuration information according to the DetNet role of the DetNet MPLS node, as per I-D.ietf-detnet-mpls. TSN related configuration information according to the TSN role of the DetNet MPLS node, as per IEEE8021Q, IEEE8021CB and IEEEP8021CBdb. 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. This information MUST be provisioned per DetNet flow. </ins> TSN-aware MPLS DetNet nodes are member of both the DetNet domain and the TSN sub-network.  Within the TSN sub-network the TSN-aware MPLS (DetNet) node has a TSN-aware Talker/Listener role, so TSN specific 6.  <ins> 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. 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. 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). </ins> 7.