rfc9025xml2.original.xml   rfc9025.xml 
<?xml version="1.0" encoding="US-ASCII"?> <?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE rfc SYSTEM "rfc2629.dtd" [
]>
<!--
- From 2/25 call:
o finish discussed split/removal of foo (IP and TSN) over MPLS (Lou) <done>
After: All to
o identify missing conformance language, notably WRT forwarding
sub-layer
o Aggregation section needs to be cleaned up
o check conformance language in MPLS over TSN section
Resolved in Mar 5 <!DOCTYPE rfc SYSTEM "rfc2629-xhtml.ent">
- need for S-Labels to be from platform label space (Andy)
Pattern after e-vpn where stack is provided by downstream receiver <rfc xmlns:xi="http://www.w3.org/2001/XInclude" docName="draft-ietf-detnet-mpls-
- Different S-Labels for same application flow (Balazs) over-udp-ip-08" number="9025" ipr="trust200902" submissionType="IETF" category="
clarify that service sub-layer nodes can change s-labels std" consensus="true" obsoletes=""
updates="" xml:lang="en" tocInclude="true" symRefs="true" sortRefs="true" versio
n="3">
<?xml-stylesheet type='text/xsl' href='rfc2629.xslt' ?>
<?rfc toc="yes"?>
<?rfc symrefs="yes"?>
<?rfc sortrefs="yes"?>
<?rfc iprnotified="no"?>
<?rfc strict="yes"?>
<?rfc compact="yes"?>
<?rfc subcompact="no"?>
<rfc category="std"
docName="draft-ietf-detnet-mpls-over-udp-ip-08"
ipr="trust200902"
submissionType="IETF">
<front> <front>
<title abbrev="DetNet MPLS over UDP/IP"> <title abbrev="DetNet MPLS over UDP/IP">
DetNet Data Plane: MPLS over UDP/IP</title> Deterministic Networking (DetNet) Data Plane: MPLS over UDP/IP</title>
<seriesInfo name="RFC" value="9025"/>
<author role="editor" fullname="Bal&aacute;zs Varga" initials="B." surname="Va <author role="editor" fullname="Balázs Varga" initials="B." surname="Varga">
rga"> <organization>Ericsson</organization>
<organization>Ericsson</organization> <address>
<address> <postal>
<postal>
<street>Magyar Tudosok krt. 11.</street> <street>Magyar Tudosok krt. 11.</street>
<city>Budapest</city> <city>Budapest</city>
<country>Hungary</country> <country>Hungary</country>
<code>1117</code> <code>1117</code>
</postal> </postal>
<email>balazs.a.varga@ericsson.com</email> <email>balazs.a.varga@ericsson.com</email>
</address> </address>
</author> </author>
<author fullname="János Farkas" initials="J." surname="Farkas">
<author fullname="J&aacute;nos Farkas" initials="J." surname="Farkas">
<organization>Ericsson</organization> <organization>Ericsson</organization>
<address> <address>
<postal> <postal>
<street>Magyar Tudosok krt. 11.</street> <street>Magyar Tudosok krt. 11.</street>
<city>Budapest</city> <city>Budapest</city>
<country>Hungary</country> <country>Hungary</country>
<code>1117</code> <code>1117</code>
</postal> </postal>
<email>janos.farkas@ericsson.com</email> <email>janos.farkas@ericsson.com</email>
</address> </address>
skipping to change at line 61 skipping to change at line 36
<address> <address>
<postal> <postal>
<street>Magyar Tudosok krt. 11.</street> <street>Magyar Tudosok krt. 11.</street>
<city>Budapest</city> <city>Budapest</city>
<country>Hungary</country> <country>Hungary</country>
<code>1117</code> <code>1117</code>
</postal> </postal>
<email>janos.farkas@ericsson.com</email> <email>janos.farkas@ericsson.com</email>
</address> </address>
</author> </author>
<author fullname="Lou Berger" initials="L." surname="Berger"> <author fullname="Lou Berger" initials="L." surname="Berger">
<organization>LabN Consulting, L.L.C.</organization> <organization>LabN Consulting, L.L.C.</organization>
<address> <address>
<email>lberger@labn.net</email> <email>lberger@labn.net</email>
</address> </address>
</author> </author>
<author fullname="Andrew G. Malis" initials="A." surname="Malis">
<author fullname="Andrew G. Malis" initials="A.G." surname="Malis">
<organization>Malis Consulting</organization> <organization>Malis Consulting</organization>
<address> <address>
<email>agmalis@gmail.com</email> <email>agmalis@gmail.com</email>
</address> </address>
</author> </author>
<author fullname="Stewart Bryant" initials="S." surname="Bryant"> <author fullname="Stewart Bryant" initials="S." surname="Bryant">
<organization>Futurewei Technologies</organization> <organization>Futurewei Technologies</organization>
<address> <address>
<email>stewart.bryant@gmail.com</email> <email>sb@stewartbryant.com</email>
</address> </address>
</author> </author>
<!-- <author fullname="Jouni Korhonen" initials="J." surname="Korhonen"> <date year="2021" month="April" />
organization abbrev="Nordic">Nordic Semiconductor</organization <workgroup>DetNet</workgroup>
<address>
<email>jouni.nospam@gmail.com</email>
</address>
</author>
<!--author fullname="Donald Fauntleroy Duck" initials="D. F." surname="Duck">
<organization abbrev="Royal Bros.">Royal Bros.</organization>
<address>
<postal>
<street>13 Paradise Road</street>
<city>Duckburg</city>
<region>Calisota</region>
<country>USA</country>
</postal>
</address>
</author-->
<date />
<workgroup>DetNet</workgroup>
<abstract> <abstract>
<t> <t>
This document specifies the MPLS Deterministic Networking data plane This document specifies the MPLS Deterministic Networking (DetNet) data pla
ne
operation and encapsulation over an IP network. The approach is based operation and encapsulation over an IP network. The approach is based
on the operation of MPLS-in-UDP technology. on the operation of MPLS-over-UDP technology.
</t> </t>
</abstract> </abstract>
</front> </front>
<middle>
<middle> <section anchor="sec_intro" numbered="true" toc="default">
<section title="Introduction" anchor="sec_intro"> <name>Introduction</name>
<t> <t>
Deterministic Networking (DetNet) is a service that can be offered by a Deterministic Networking (DetNet) is a service that can be offered by a
network to DetNet flows. DetNet provides these flows extremely low packet network to DetNet flows. DetNet provides these flows extremely low packet
loss rates and assured maximum end-to-end delivery latency. loss rates and assured maximum end-to-end delivery latency.
General background General background
and concepts of DetNet can be found in <xref and concepts of DetNet can be found in <xref target="RFC8655" format="defaul
target="RFC8655"/>. t"/>.
</t> </t>
<!-- <t>
The DetNet Architecture decomposes the DetNet related data plane
functions into two sub-layers: a service sub-layer and a forwarding sub-laye
r.
The service sub-layer is used to provide DetNet service protection and
reordering. The forwarding sub-layer is used to provides congestion
protection (low loss, assured latency, and limited reordering)
leveraging MPLS Traffic Engineering mechanisms.
</t> -->
<t> <t>
To carry DetNet MPLS flows with full functionality at the DetNet layer over an IP network, the To carry DetNet MPLS flows with full functionality at the DetNet layer over an IP network, the
following components are required (these are a subset of the requirements for MPLS encapsulation following components are required (these are a subset of the requirements for MPLS encapsulation
listed in <xref target="I-D.ietf-detnet-mpls"/>): listed in <xref target="RFC8964" format="default"/>):
</t> </t>
<t> <ol spacing="normal" type="1"><li>A method for identifying DetNet flows
<list style="numbers"> to the processing element.</li>
<t>A method for identifying DetNet flows to the processing element.</t> <li>A method for carrying the DetNet sequence number.</li>
<t>A method for carrying the DetNet sequence number.</t> <li>A method for distinguishing DetNet Operations, Administration, and
<t>A method for distinguishing DetNet OAM packets from DetNet data packets.< Maintenance (OAM) packets from DetNet data packets.</li>
/t> <li>A method for carrying queuing and forwarding indication.</li>
<t>A method for carrying queueing and forwarding indication.</t> </ol>
</list> <t>
</t>
<t>
These requirements are satisfied by the DetNet over MPLS Encapsulation These requirements are satisfied by the DetNet over MPLS Encapsulation
described in <xref target="I-D.ietf-detnet-mpls"/> and they are partly satisfi described in <xref target="RFC8964" format="default"/> and they are partly
ed satisfied (i.e., IP flows can be identified; however, no DetNet sequence
(i.e., IP flows can be identified however no DetNet sequence number is carried number is carried) by the DetNet IP data plane defined in <xref
) target="RFC8939" format="default"/>.
by the DetNet IP data plane defined in <xref target="I-D.ietf-detnet-ip"/> </t>
</t> <t>
<t> This document specifies use of the MPLS DetNet encapsulation over an IP
This document specifies use of the MPLS DetNet encapsulation over an IP networ network. The approach is modeled on the operation of MPLS over an IP Packet
k. Switched Network (PSN) using UDP encapsulation <xref target="RFC7510"
The approach is modeled on the operation of MPLS over format="default"/>. It maps the MPLS data plane encapsulation described in
an IP Packet Switched Network (PSN) <xref target="RFC7510"/>. <xref target="RFC8964" format="default"/> to the DetNet IP data plane
It maps the MPLS data plane encapsulation described in <xref defined in <xref target="RFC8939" format="default"/>.
target="I-D.ietf-detnet-mpls"/> to the DetNet IP data plane defined in <xref </t>
target="I-D.ietf-detnet-ip"/>. <t>
</t> <xref target="RFC7510"/> specifies that "MPLS-in-UDP <bcp14>MUST
<t> NOT</bcp14> be used over the general Internet, or over non-cooperating
As specified in <xref target="RFC7510"/>: "MPLS-in-UDP MUST NOT be network operators, to carry traffic that is not congestion
used over the general Internet, or over non-cooperating network controlled." This constraint does apply to the use of RFC 7510 in a
operators, to carry traffic that is not congestion controlled." DetNet network because DetNet is constrained to operate within a
This does apply to DetNet networks as this document focuses on solutions single administrative control or within a closed group of
for networks that are under a single administrative control or within a administrative control.
closed group of administrative control.
</t>
</section>
<section title="Terminology"> </t>
<section title="Terms Used in This Document"> </section>
<t> <section numbered="true" toc="default">
<name>Terminology</name>
<section numbered="true" toc="default">
<name>Terms Used in This Document</name>
<t>
This document uses the terminology established in the DetNet architecture This document uses the terminology established in the DetNet architecture
<xref target="RFC8655"/>, and the reader is assumed <xref target="RFC8655" format="default"/>; the reader is assumed
to be familiar with that document and its terminology. to be familiar with that document and its terminology.
</t> </t>
</section> </section>
<section numbered="true" toc="default">
<section title="Abbreviations"> <name>Abbreviations</name>
<t> <t>
The following abbreviations are used in this document: The following abbreviations are used in this document:
<list style="hanging" hangIndent="14"> </t>
<t hangText="d-CW"> <dl newline="false" spacing="normal" indent="14">
<dt>d-CW</dt>
<dd>
A DetNet Control Word (d-CW) is used for sequencing and identifying du plicate packets of a DetNet flow at the DetNet service A DetNet Control Word (d-CW) is used for sequencing and identifying du plicate packets of a DetNet flow at the DetNet service
sub-layer. </t> sub-layer. </dd>
<t hangText="DetNet">Deterministic Networking.</t> <dt>DetNet</dt>
<t hangText="A-Label">A special case of an S-Label, whose properties are kno <dd>Deterministic Networking</dd>
wn only at
the aggregation and deaggregation end-points.</t>
<t hangText="F-Label">A Detnet "forwarding" label that identifies the LSP us
ed to
forward a DetNet flow across an MPLS PSN, e.g., a hop-by-hop
label used between label switching routers.</t>
<t hangText="MPLS">Multiprotocol Label Switching.</t>
<t hangText="OAM">Operations, Administration, and Maintenance.</t>
<t hangText="PEF">Packet Elimination Function.</t>
<t hangText="POF">Packet Ordering Function.</t>
<t hangText="PREOF">Packet Replication, Elimination and Ordering Function
s.</t>
<t hangText="PRF">Packet Replication Function.</t>
<t hangText="PSN">Packet Switched Network.</t>
<t hangText="S-Label">A DetNet "service" label that is used between DetNet
nodes that also implement the DetNet service sub-layer functions. An S-Label
is
also used to identify a DetNet flow at DetNet service sub-layer.</t>
</list>
</t>
</section>
<section title="Requirements Language"> <dt>DSCP
<t> </dt>
The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", <dd>Differentiated Services Code Point
"SHOULD", "SHOULD NOT", "RECOMMENDED", "NOT RECOMMENDED", "MAY", and </dd>
"OPTIONAL" in this document are to be interpreted as described in <dt>A-Label</dt>
BCP 14 <xref target="RFC2119"/> <xref target="RFC8174"/> when, and <dd>A special case of an S-Label, whose properties are known only at
only when, they appear in all capitals, as shown here. the aggregation and deaggregation endpoints.</dd>
</t> <dt>F-Label</dt>
</section> <dd>A DetNet "forwarding" label that identifies the LSP used to
</section> <!-- end of terminology --> forward a DetNet flow across an MPLS PSN, e.g., a hop-by-hop label
used between label-switching routers.</dd>
<dt>MPLS</dt>
<dd>Multiprotocol Label Switching</dd>
<dt>OAM</dt>
<dd>Operations, Administration, and Maintenance</dd>
<dt>PEF</dt>
<dd>Packet Elimination Function</dd>
<dt>POF</dt>
<dd>Packet Ordering Function</dd>
<dt>PREOF</dt>
<dd>Packet Replication, Elimination, and Ordering Functions</dd>
<dt>PRF</dt>
<dd>Packet Replication Function</dd>
<dt>PSN</dt>
<dd>Packet Switched Network</dd>
<dt>S-Label</dt>
<dd>A DetNet "service" label that is used between DetNet
nodes that also implement the DetNet service sub-layer functions. An S-Label
is
also used to identify a DetNet flow at the DetNet service sub-layer.</dd>
</dl>
</section>
<section numbered="true" toc="default">
<name>Requirements Language</name>
<t>
The key words "<bcp14>MUST</bcp14>", "<bcp14>MUST NOT</bcp14>", "<bcp14>REQU
IRED</bcp14>", "<bcp14>SHALL</bcp14>", "<bcp14>SHALL
NOT</bcp14>", "<bcp14>SHOULD</bcp14>", "<bcp14>SHOULD NOT</bcp14>", "<bcp14>
RECOMMENDED</bcp14>", "<bcp14>NOT RECOMMENDED</bcp14>",
"<bcp14>MAY</bcp14>", and "<bcp14>OPTIONAL</bcp14>" in this document are to
be interpreted as
described in BCP&nbsp;14 <xref target="RFC2119"/> <xref target="RFC8174"/>
when, and only when, they appear in all capitals, as shown here.
</t>
<!-- ===================================================================== --> </section>
</section>
<section anchor="mpls-over-ip" title="DetNet MPLS Operation over DetNet <section anchor="mpls-over-ip" numbered="true" toc="default">
IP PSNs"> <name>DetNet MPLS Operation over DetNet
<t> IP PSNs</name>
<t>
This document builds on the specification of MPLS over UDP defined This document builds on the specification of MPLS over UDP defined
in <xref target="RFC7510"/>. It may replace partly or entirely the F-Label(s) in <xref target="RFC7510" format="default"/>. It may partly or entirely repla
used in <xref ce the F-Label(s) used in <xref target="RFC8964" format="default"/> with UDP and
target="I-D.ietf-detnet-mpls"/> with UDP and IP headers. The UDP and IP headers. The UDP and
IP header information is used to identify DetNet flows, including member IP header information is used to identify DetNet flows, including member
flows, per <xref target="I-D.ietf-detnet-ip"/>. The resulting encapsulation flows, per <xref target="RFC8939" format="default"/>. The resulting encapsulat
is shown in <xref target="IP-encap-dn"/>. There may be zero or more F-label(s ion
) is shown in <xref target="IP-encap-dn" format="default"/>. There may be zero o
between the S-label and the UDP header. r more F-Labels
</t> between the S-Label and the UDP header.
</t>
<t> <t>
Note that this encapsulation works equally well with IPv4, IPv6, and Note that this encapsulation works equally well with IPv4, IPv6, and
IPv6-based Segment Routing <xref target="RFC8754"/>. IPv6-based Segment Routing <xref target="RFC8754" format="default"/>.
</t> </t>
<figure anchor="IP-encap-dn">
<figure title="UDP/IP Encapsulation of DetNet MPLS" anchor="IP-encap-dn"> <name>UDP/IP Encapsulation of DetNet MPLS</name>
<artwork align="center"><![CDATA[ <artwork align="center" name="" type="" alt=""><![CDATA[
+---------------------------------+ +---------------------------------+
| | | |
| DetNet App-Flow | | DetNet App-Flow |
| Payload Packet | | Payload Packet |
| | | |
+---------------------------------+ <--\ +---------------------------------+ <--\
| DetNet Control Word | | | DetNet Control Word | |
+---------------------------------+ +--> DetNet data plane +---------------------------------+ +--> DetNet data plane
| S-Label | | MPLS encapsulation | S-Label | | MPLS encapsulation
+---------------------------------+ | +---------------------------------+ |
| [ F-label(s) ] | | | [ F-Label(s) ] | |
+---------------------------------+ <--+ +---------------------------------+ <--+
| UDP Header | | | UDP Header | |
+---------------------------------+ +--> DetNet data plane +---------------------------------+ +--> DetNet data plane
| IP Header | | IP encapsulation | IP Header | | IP encapsulation
+---------------------------------+ <--/ +---------------------------------+ <--/
| Data-Link | | Data-Link |
+---------------------------------+ +---------------------------------+
| Physical | | Physical |
+---------------------------------+ +---------------------------------+
]]>
</artwork></figure>
<t>
S-Labels, A-Labels (when present), d-CW and zero or more F-Labels are used a
s defined in <xref
target="I-D.ietf-detnet-mpls"/> and are not modified by this document.
</t> ]]></artwork>
</section> </figure>
<t>
<section anchor="dp-procs" title="DetNet Data Plane Procedures"> S-Labels, A-Labels (when present), d-CW, and zero or more F-Labels are used
<t> as defined in <xref target="RFC8964" format="default"/> and are not modified by
To support outgoing DetNet MPLS over UDP encapsulation, an implementation MU this document.
ST support the
provisioning of UDP and IP header information in addition to or in place of
F-Label(s).
Note, when PRF is performed at the MPLS service sub-layer, there
will be multiple member flows, and each member flow will require the
provisioning of their own UDP and IP header information.
The headers for each outgoing packet MUST be formatted according to
the configuration information and as defined in <xref
target="RFC7510"/>, and the
UDP Source Port value MUST be set to uniquely identify the DetNet flow.
The packet MUST then be handled
as a DetNet IP packet, per <xref target="I-D.ietf-detnet-ip"/>.
This includes QoS related traffic treatment.
</t>
<t> </t>
</section>
<section anchor="dp-procs" numbered="true" toc="default">
<name>DetNet Data Plane Procedures</name>
<t>
To support outgoing DetNet MPLS over UDP encapsulation, an implementation
<bcp14>MUST</bcp14> support the provisioning of UDP and IP header
information in addition to or in place of F-Label(s). Note, when the PRF
is performed at the MPLS service sub-layer, there will be multiple member
flows, and each member flow will require the provisioning of their own UDP
and IP header information. The headers for each outgoing packet
<bcp14>MUST</bcp14> be formatted according to the configuration
information and as defined in <xref target="RFC7510" format="default"/>,
and the UDP Source Port value <bcp14>MUST</bcp14> be set to uniquely
identify the DetNet flow. The packet <bcp14>MUST</bcp14> then be handled
as a DetNet IP packet, per <xref target="RFC8939" format="default"/>.
This includes QoS-related traffic treatment.
</t>
<t>
To support the receive processing defined in this document, an To support the receive processing defined in this document, an
implementation MUST also support implementation <bcp14>MUST</bcp14> also support
the provisioning of received UDP and IP header information. the provisioning of received UDP and IP header information.
The provisioned information MUST be used to The provisioned information <bcp14>MUST</bcp14> be used to
identify incoming app-flows based on the combination of S-Label and identify incoming app flows based on the combination of S-Label and
incoming encapsulation header information. Normal receive processing as def incoming encapsulation header information. Normal receive processing as def
ined in <xref target="I-D.ietf-detnet-mpls"/>, including PEF and POF, ined in <xref target="RFC8964" format="default"/>, including PEF and POF,
can then take place. can then take place.
</t> </t>
</section>
</section> <section anchor="ip-flow-id-info" numbered="true" toc="default">
<name>Management and Control Information Summary</name>
<section anchor="ip-flow-id-info" <t>
title="Management and Control Information Summary">
<t>
The following summarizes the minimum set of information that is need ed to The following summarizes the minimum set of information that is need ed to
configure DetNet MPLS over UDP/IP: configure DetNet MPLS over UDP/IP:
<list style="symbols"> </t>
<t>Label information (A-labels, S-labels and F-labels) <ul spacing="normal">
to <li>Label information (A-Labels, S-Labels, and F-Labels) to be mapped
be mapped to UDP/IP flows. Note that for example, a si to UDP/IP flows. Note that, for example, a single S-Label can map to
ngle multiple sets of UDP/IP information when PREOF is used.</li>
S-Label can map to multiple sets of UDP/IP <li>IPv4 or IPv6 source address field</li>
information when PREOF is used.</t> <li>IPv4 or IPv6 destination address field</li>
<t>IPv4 or IPv6 source address field.</t> <li>DSCP Field in either IPv4 Type of Service or IPv6 Traffic Class Fiel
<t>IPv4 or IPv6 destination address field.</t> ds</li>
<t>DSCP Field in either IPv4 Type of Service or IPv6 Traffic Class
Fields.</t>
<t>UDP Source Port. </t>
<t>UDP Destination Port. </t>
<t>Use/non-use of UDP checksum. </t>
</list>
This information MUST be provisioned per DetNet flow via
configuration, e.g., via the controller <xref target="RFC8655"/>
or management plane. Not using the UDP checksum has to be
evaluated
on a case-by-case basis for a given network scenario base
d on the
exception criteria's defined in <xref target="RFC7510"/>,
particularly when IPv6 is used.</t>
<t>
It is the responsibility of the DetNet controller plane to
properly provision both flow identification information and
the flow specific resources needed to provide the traffic
treatment needed to meet each flow's service requirements.
This applies for aggregated and individual flows.
</t>
<t>
Note: In the presence of network (and port) address translati
on
devices/functions it would be up to the controller plane
to
determine the appropriate information to ensure proper
mapping at the sender/receiver.
</t>
</section>
<!-- ===================================================================== --> <li>UDP Source Port </li>
<li>UDP Destination Port </li>
<li>Use/non-use of UDP checksum </li>
</ul>
<t>
This information <bcp14>MUST</bcp14> be provisioned per DetNet
flow via configuration, e.g., via the controller <xref
target="RFC8655" format="default"/> or management plane. Not using
the UDP checksum has to be evaluated on a case-by-case basis for a
given network scenario based on the exception criteria defined in
<xref target="RFC7510" format="default"/>, particularly when IPv6
is used.</t>
<t>
It is the responsibility of the DetNet Controller Plane to
properly provision both flow identification information and the
flow-specific resources needed to provide the traffic treatment
needed to meet each flow's service requirements. This applies for
both aggregated and individual flows.
</t>
<aside>
<t> Note: In the presence of network (and port) address translation
devices/functions, it would be up to the Controller Plane to determine
the appropriate information to ensure proper mapping at the
sender/receiver.
</t>
</aside>
</section>
<section title="Security Considerations"> <section numbered="true" toc="default">
<t> <name>Security Considerations</name>
The solution defined in this document reuses mechanisms specified in <t>
other documents, and the security considerations in those documents The solution defined in this document reuses mechanisms specified in other
apply equally to this document. Of particular note is <xref target="RFC7510" documents, and the security considerations in those documents apply
/>, as equally to this document. Of particular note is <xref target="RFC7510"
this document is primarily an application of format="default"/>, as this document is primarily an application of
MPLS-in-UDP. Additionally, the security considerations of DetNet in MPLS-over-UDP. Additionally, the security considerations of DetNet in
general are discussed in <xref target="RFC8655"/> general are discussed in <xref target="RFC8655" format="default"/> and
and <xref target="I-D.ietf-detnet-security"/>. Finally, MPLS and IP specific <xref target="I-D.ietf-detnet-security" format="default"/>. Finally, MPLS-
security considerations are described in <xref target="I-D.ietf-detnet-mpls"/ and IP-specific security considerations are described in <xref
> target="RFC8964" format="default"/> and <xref target="RFC8939"
and <xref target="I-D.ietf-detnet-ip"/>. This draft does not have additional format="default"/>. This document does not have additional security
security considerations. considerations.
</t> </t>
</section> </section>
<section anchor="iana" numbered="true" toc="default">
<name>IANA Considerations</name>
<t>
This document has no IANA actions.
</t>
</section>
<section anchor="iana" title="IANA Considerations"> </middle>
<t> <back>
This document makes no IANA requests.
</t>
</section>
<section anchor="acks" title="Acknowledgements"> <displayreference target="I-D.ietf-detnet-security" to="DETNET-SECURITY"/>
<references>
<name>References</name>
<references>
<name>Normative References</name>
<xi:include href="https://xml2rfc.ietf.org/public/rfc/bibxml/reference.R
FC.2119.xml"/>
<xi:include href="https://xml2rfc.ietf.org/public/rfc/bibxml/reference.R
FC.7510.xml"/>
<xi:include href="https://xml2rfc.ietf.org/public/rfc/bibxml/reference.R
FC.8174.xml"/>
<xi:include href="https://xml2rfc.ietf.org/public/rfc/bibxml/reference.R
FC.8964.xml"/>
<xi:include href="https://xml2rfc.ietf.org/public/rfc/bibxml/reference.R
FC.8939.xml"/>
</references>
<references>
<name>Informative References</name>
<xi:include href="https://xml2rfc.ietf.org/public/rfc/bibxml/reference.R
FC.8655.xml"/>
<xi:include href="https://xml2rfc.ietf.org/public/rfc/bibxml/reference.R
FC.8754.xml"/>
<reference anchor='I-D.ietf-detnet-security'>
<front>
<title>Deterministic Networking (DetNet) Security Considerations</title>
<author initials='E' surname='Grossman' fullname='Ethan Grossman' role="editor">
<organization />
</author>
<author initials='T' surname='Mizrahi' fullname='Tal Mizrahi'>
<organization />
</author>
<author initials='A. J.' surname='Hacker' fullname='Andrew Hacker'>
<organization />
</author>
<date month='February' day='22' year='2021' />
</front>
<seriesInfo name='Internet-Draft' value='draft-ietf-detnet-security-16' />
</reference>
</references>
</references>
<section anchor="acks" numbered="false" toc="default">
<name>Acknowledgements</name>
<t> <t>
The authors wish to thank Pat Thaler, Norman Finn, Loa Anderson, The authors wish to thank <contact fullname="Pat Thaler"/>,
David Black, <contact fullname="Norman Finn"/>, <contact fullname="Loa
Rodney Cummings, Ethan Grossman, Tal Mizrahi, David Mozes, Craig Anderson"/>, <contact fullname="David Black"/>, <contact
Gunther, fullname="Rodney Cummings"/>, <contact fullname="Ethan
George Swallow, Yuanlong Jiang and Carlos J. Bernardos for their Grossman"/>, <contact fullname="Tal Mizrahi"/>, <contact
various contributions to this work. fullname="David Mozes"/>, <contact fullname="Craig Gunther"/>,
<contact fullname="George Swallow"/>, <contact
fullname="Yuanlong Jiang"/>, and <contact fullname="Carlos
J. Bernardos"/> for their various contributions to this work.
</t> </t>
</section> </section>
<section anchor="contrib" numbered="false" toc="default">
<section anchor="contrib" title="Contributors"> <name>Contributors</name>
<t> <t>
This document is derived from an earlier draft that was edited This document is derived from an earlier draft that was edited by <contact
by Jouni Korhonen (jouni.nospam@gmail.com) and as such, he fullname="Jouni Korhonen" /> (jouni.nospam@gmail.com), and as such, he
contributed to and authored text in this document. contributed to and authored text in this document.
</t> </t>
</section> </section>
</middle>
<back> </back>
<references title="Normative References">
<?rfc include="reference.RFC.2119"?>
<?rfc include="reference.RFC.7510"?>
<?rfc include="reference.RFC.8174"?>
<?rfc include="reference.I-D.ietf-detnet-mpls'?>
<?rfc include="reference.I-D.ietf-detnet-ip'?>
</references>
<references title="Informative References">
<?rfc include="reference.RFC.8655"?>
<?rfc include="reference.RFC.8754"?>
<?rfc include="reference.I-D.ietf-detnet-security"?>
</references>
</back>
</rfc> </rfc>
 End of changes. 43 change blocks. 
319 lines changed or deleted 319 lines changed or added

This html diff was produced by rfcdiff 1.48. The latest version is available from http://tools.ietf.org/tools/rfcdiff/