jiebi/ids-paragraph-commentary-corpus huggingface dataset:
Draft: draft-ietf-detnet-dp-sol-ip-00

Commentary: merging - per e - mail ...
Packet Replication and Elimination Function.
fig_ip_detnet illustrates a more complex DetNet enabled IP network
where an IP flow is mapped to one or more PWs and MPLS (TE) LSPs.
The end systems still originate IP encapsulated traffic that is
identified as DetNet flows.  The relay nodes follow procedures
defined in I-D.ietf-detnet-dp-sol-mpls to map each DetNet flow to
MPLS LSPs.  While not shown, relay nodes can provide service layer
functions such as PREF and PROEF over the MPLS transport layer, and
this is indicated by the solid line for the MPLS facing portion of
the Service component.  Note that the Transit node is MPLS (TE) LSP
aware and performs switching based on MPLS labels, and need not have
any specific knowledge of the DetNet service or the corresponding
DetNet flow identification.  See I-D.ietf-detnet-dp-sol-mpls for
details on the mapping of IP flows to MPLS as well as general support
for DetNet services using MPLS.
fig_ip_detnet illustrates a more complex DetNet enabled IP network
where an IP flow is mapped to one or more PWs and MPLS (TE) LSPs.
The end systems still originate IP encapsulated traffic that is
identified as DetNet flows.  The relay nodes follow procedures
defined in I-D.ietf-detnet-dp-sol-mpls to map each DetNet flow to
MPLS LSPs.  While not shown, relay nodes can provide service layer
functions such as PREOF over the MPLS transport layer, and this is
indicated by the solid line for the MPLS facing portion of the
Service component.  Note that the Transit node is MPLS (TE) LSP aware
and performs switching based on MPLS labels, and need not have any
specific knowledge of the DetNet service or the corresponding DetNet
flow identification.  See I-D.ietf-detnet-dp-sol-mpls for details on
the mapping of IP flows to MPLS as well as general support for DetNet
services using MPLS.
DetNet IP flows are identified based on IP, both IPv4 RFC0791 and
IPv6 RFC2460, header information.  6 header fields are used and this
set of fields is commonly referred to as the IP header "6-tuple".
The 6 fields include the IP source and destination address fields,
the next level protocol or header field, the next level protocol
(e.g.  TCP or UDP) source and destination ports, and the IPv4 Type of
Service or IPv6 Traffic Class field (i.e., DSCP).  As part of single
DetNet flow identification, any of the fields can be ignored
(wildcarded), and bit masks, prefix based longest match, and ranges
can also be used.
DetNet IP flows are identified based on IP, both IPv4 RFC0791 and
IPv6 RFC8200, header information.  6 header fields are used and this
set of fields is commonly referred to as the IP header "6-tuple".
The 6 fields include the IP source and destination address fields,
the next level protocol or header field, the next level protocol
(e.g.  TCP or UDP) source and destination ports, and the IPv4 Type of
Service or IPv6 Traffic Class field (i.e., DSCP).  As part of single
DetNet flow identification, any of the fields can be ignored
(wildcarded), and bit masks, prefix based longest match, and ranges
can also be used.