Original text:
IEEE8021CB and IEEEP8021CBdb) whether the packet belongs to a configured TSN Stream (i.e., App-flow from DetNet perspective).  If no Stream ID is matched and no other (VPN) service is configured for <del> the AC then packet MUST be dropped.  If there is a matching TSN Stream then the Stream ID specific TSN functions are executed (e.g., </del>  ingress policing, header field manipulation in case of active Stream Identification, FRER, etc.).  Source MAC lookup may also be used for local MAC address learning. according to the TSN Stream specific configuration to connected CE(s) (in case of local bridging) and/or to the DetNet Service Proxy (in case of forwarding to remote CE(s)).  If there are no TSN Stream <del> specific forwarding configurations the PE MUST flood the packet to </del>  other locally attached CE(s) and to the DetNet Service Proxy.  If the <del> administrative policy on the PE does not allow flooding the PE MUST </del>  drop the packet. When a TSN entity of the PE receives a packet from the DetNet Service Proxy, it first checks via Stream Identification (see Clause 6. of IEEE8021CB and IEEEP8021CBdb) whether the packet belongs to a <del> configured TSN Stream.  If no Stream ID is matched then packet is dropped.  If there is a matching TSN Stream then the Stream ID </del>  specific TSN functions are executed (e.g., header field manipulation in case of active Stream Identification, FRER, etc.).  Source MAC lookup may also be used for local MAC address learning. If the PE decides to forward the packet, the packet is forwarded according to the TSN Stream specific configuration to connected <del> CE(s).  If there are no TSN Stream specific forwarding configurations the PE floods the packet to locally attached CE(s).  If the administrative policy on the PE does not allow flooding the PE drops the packet. </del>  Implementations of this document SHALL use management and control information to ensure TSN specific functions of the Edge Node

Reviewer comments:
Adding commas, the editor will probably catch these.
Hi Don, many thanks for the review. Cheers Bala'zs

Revised text:
IEEE8021CB and IEEEP8021CBdb) whether the packet belongs to a configured TSN Stream (i.e., App-flow from DetNet perspective).  If no Stream ID is matched and no other (VPN) service is configured for  <ins> the AC, then packet MUST be dropped.  If there is a matching TSN Stream, then the Stream ID specific TSN functions are executed (e.g., </ins> ingress policing, header field manipulation in case of active Stream Identification, FRER, etc.).  Source MAC lookup may also be used for local MAC address learning. according to the TSN Stream specific configuration to connected CE(s) (in case of local bridging) and/or to the DetNet Service Proxy (in case of forwarding to remote CE(s)).  If there are no TSN Stream  <ins> specific forwarding configurations, the PE MUST flood the packet to </ins> other locally attached CE(s) and to the DetNet Service Proxy.  If the  <ins> administrative policy on the PE does not allow flooding, the PE MUST </ins> drop the packet. When a TSN entity of the PE receives a packet from the DetNet Service Proxy, it first checks via Stream Identification (see Clause 6. of IEEE8021CB and IEEEP8021CBdb) whether the packet belongs to a  <ins> configured TSN Stream.  If no Stream ID is matched, then packet is dropped.  If there is a matching TSN Stream, then the Stream ID </ins> specific TSN functions are executed (e.g., header field manipulation in case of active Stream Identification, FRER, etc.).  Source MAC lookup may also be used for local MAC address learning. If the PE decides to forward the packet, the packet is forwarded according to the TSN Stream specific configuration to connected  <ins> CE(s).  If there are no TSN Stream specific forwarding configurations, the PE floods the packet to locally attached CE(s). If the administrative policy on the PE does not allow flooding, the PE drops the packet. </ins> Implementations of this document SHALL use management and control information to ensure TSN specific functions of the Edge Node