rfc9016xml2.original.xml   rfc9016.xml 
<?xml version="1.0" encoding="US-ASCII"?> <?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE rfc SYSTEM "rfc2629.dtd" [ <!DOCTYPE rfc SYSTEM "rfc2629-xhtml.ent">
]>
<?xml-stylesheet type='text/xsl' href='rfc2629.xslt' ?> <rfc xmlns:xi="http://www.w3.org/2001/XInclude" docName="draft-ietf-detnet-flow-
<?rfc strict="yes" ?> information-model-14" number="9016" ipr="trust200902" obsoletes="" updates="" su
<?rfc toc="yes"?> bmissionType="IETF" category="info" consensus="true" xml:lang="en" tocInclude="t
<?rfc tocdepth="4"?> rue" tocDepth="4" symRefs="true" sortRefs="true" version="3">
<?rfc symrefs="yes"?>
<?rfc sortrefs="yes" ?>
<?rfc compact="yes" ?>
<?rfc subcompact="no" ?>
<rfc category="info" docName="draft-ietf-detnet-flow-information-model-14" ipr="
trust200902">
<!-- ***** FRONT MATTER ***** --> <!-- xml2rfc v2v3 conversion 3.5.0 -->
<front> <front>
<title abbrev="DetNet Flow Information Model">Flow and Service Information M
<title abbrev="DetNet Flow Information Model">DetNet Flow and Service Informatio odel for Deterministic Networking (DetNet)</title>
n Model</title> <seriesInfo name="RFC" value="9016"/>
<author fullname="Balázs Varga" initials="B." surname="Varga">
<author fullname="Bal&aacute;zs Varga" initials="B." surname="Varga"> <organization>Ericsson</organization>
<organization>Ericsson</organization> <address>
<address> <postal>
<postal> <street>Magyar Tudosok krt. 11.</street>
<street>Magyar tudosok korutja 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">
<organization>Ericsson</organization>
<author fullname="J&aacute;nos Farkas" initials="J." surname="Farkas"> <address>
<organization>Ericsson</organization> <postal>
<address> <street>Magyar Tudosok krt. 11.</street>
<postal> <city>Budapest</city>
<street>Magyar tudosok korutja 11</street> <country>Hungary</country>
<city>Budapest</city> <code>1117</code>
<country>Hungary</country> </postal>
<code>1117</code> <email>janos.farkas@ericsson.com</email>
</postal> </address>
<email>janos.farkas@ericsson.com</email> </author>
</address> <author fullname="Rodney Cummings" initials="R." surname="Cummings">
</author> <organization>National Instruments</organization>
<address>
<author fullname="Rodney Cummings" initials="R." surname="Cummings"> <postal>
<organization>National Instruments</organization> <street>11500 N. Mopac Expwy</street>
<address> <extaddr>Bldg. C</extaddr>
<postal> <city>Austin</city>
<street>11500 N. Mopac Expwy</street> <region>TX</region>
<street>Bldg. C</street> <country>United States of America</country>
<city>Austin, TX</city> <code>78759-3504</code>
<country>USA</country> </postal>
<code>78759-3504</code> <email>rodney.cummings@ni.com</email>
</postal> </address>
<email>rodney.cummings@ni.com</email> </author>
</address> <author fullname="Yuanlong Jiang" initials="Y." surname="Jiang">
</author> <organization abbrev="Huawei">Huawei</organization>
<address>
<author fullname="Yuanlong Jiang" initials="Y." surname="Jiang"> <postal>
<organization>Huawei Technologies Co., Ltd.</organization> <street>Bantian, Longgang district</street>
<address> <city>Shenzhen</city>
<postal> <country>China</country>
<street>Bantian, Longgang district</street> <code>518129</code>
<street> </street> </postal>
<city>Shenzhen</city> <email>jiangyuanlong@huawei.com</email>
<country>China</country> </address>
<code>518129</code> </author>
</postal> <author fullname="Don Fedyk" initials="D." surname="Fedyk">
<email>jiangyuanlong@huawei.com</email> <organization abbrev="LabN Consulting">LabN Consulting, L.L.C.</organizati
</address> on>
</author> <address>
<author fullname="Don Fedyk" initials="D." surname="Fedyk">
<organization>LabN Consulting, L.L.C.</organization>
<address>
<email>dfedyk@labn.net</email> <email>dfedyk@labn.net</email>
</address> </address>
</author> </author>
<date year="2021" month="March" />
<date /> <area>Routing</area>
<workgroup>DetNet</workgroup>
<area>Routing</area> <keyword>DetNet</keyword>
<keyword>Flow and Service Information Model</keyword>
<workgroup>DetNet</workgroup> <abstract>
<t>This document describes the flow and service information model for Dete
<keyword>DetNet, Flow and Service Information Model</keyword> rministic Networking (DetNet).
These models are defined for IP and MPLS DetNet data planes.</t>
<abstract> </abstract>
<t>This document describes flow and service information model for Determinis </front>
tic Networking (DetNet).
These models are defined for IP and MPLS DetNet data planes</t>
</abstract>
</front>
<!-- ***** MIDDLE MATTER ***** -->
<middle> <middle>
<section numbered="true" toc="default">
<!-- +++++++++++++++++++++++++++++++++++++++++++++++++++++++ --> <name>Introduction</name>
<!-- +++++++ INTRODUCTION +++++++ --> <t>
<!-- +++++++++++++++++++++++++++++++++++++++++++++++++++++++ -->
<section title="Introduction">
<t>
Deterministic Networking (DetNet) provides a capability to carry Deterministic Networking (DetNet) provides a capability to carry
specified unicast or multicast data flows for real-time applications specified unicast or multicast data flows for real-time applications
with extremely low packet loss rates and assured maximum end-to-end with extremely low packet loss rates and assured maximum end-to-end
delivery latency. A description of the general background and concepts delivery latency. A description of the general background and concepts
of DetNet can be found in <xref target="RFC8655"/>. of DetNet can be found in <xref target="RFC8655" format="default"/>.
</t> </t>
<t> <t>
This document describes the Detnet Flow and Service Information Model. This document describes the DetNet flow and service information model.
For reference <xref target="RFC3444"/> describes the rationale behind In For reference, <xref target="RFC3444" format="default"/> describes the r
formation ationale behind information
Models in general. This document describes the Flow and Service informati models in general. This document describes the flow and service informati
on on
models for operators and users to understand Detnet services, and for imp models for operators and users to understand DetNet services and for impl
lementors ementors
as a guide to the functionality required by Detnet services. as a guide to the functionality required by DetNet services.
</t> </t>
<t> <t>
The DetNet Architecture treats the DetNet related data plane functions The DetNet architecture treats the DetNet-related data plane functions
decomposed into two sub-layers: a service sub-layer and a forwarding decomposed into two sub-layers: a service sub-layer and a forwarding
sub-layer. The service sub-layer is used to provide DetNet service sub-layer. The service sub-layer is used to provide DetNet service
protection and reordering. The forwarding sub-layer provides protection and reordering. The forwarding sub-layer provides
resource allocation (to ensure low loss, assured latency, and limited resource allocation (to ensure low loss, assured latency, and limited
out-of-order delivery) and leverages Traffic Engineering mechanisms. out-of-order delivery) and leverages traffic engineering mechanisms.
</t> </t>
<t> <t>
DetNet service utilizes IP or MPLS and DetNet is currently DetNet service utilizes IP or MPLS, and DetNet is currently
defined for IP and MPLS networks as shown in Figure 1 based on Figure 2 defined for IP and MPLS networks, as shown in
and Figure 3 of <xref target="RFC8938"/>. <xref target="dn_svc_encaps" format="default"/>, which is a reprint of Fi
IEEE 802.1 Time Sensitive Networking (TSN) utilizes Ethernet and gure 2
from <xref target="RFC8938" format="default"/>.
IEEE 802.1 Time-Sensitive Networking (TSN) utilizes Ethernet and
is defined over Ethernet networks. A DetNet flow includes one or more is defined over Ethernet networks. A DetNet flow includes one or more
App-flow(s) as payload. App-flows can be Ethernet, MPLS, or IP flows, application-level flow (App-flow) as payload. App-flows can be Ethernet, MPLS, or IP flows,
which impacts which header fields are utilized to identify a flow. which impacts which header fields are utilized to identify a flow.
DetNet flows are identified by the DetNet encapsulation of App-flow(s) ( e.g., DetNet flows are identified by the DetNet encapsulation of App-flow(s) ( e.g.,
MPLS labels, IP 6-tuple etc.). In some scenarios App-flow and DetNet MPLS labels, IP 6-tuples, etc.). In some scenarios, App-flow and DetNet
flow look similar on the wire (e.g., L3 App-flow over a DetNet IP flow look similar on the wire (e.g., Layer 3 (L3) App-flow over a DetNet
IP
network). </t> network). </t>
<figure anchor="dn_svc_encaps">
<figure anchor="dn_svc_encaps" align="center" <name>DetNet Service Examples as per Data Plane Framework</name>
title="DetNet Service Examples as per Data Plane Framework"> <artwork align="center" name="" type="" alt=""><![CDATA[
<artwork align="center"><![CDATA[
+-----+ +-----+
| TSN | | TSN |
+-------+ +-+-----+-+ +-------+ +-+-----+-+
| DN IP | | DN MPLS | | DN IP | | DN MPLS |
+--+--+----+----+ +-+---+-----+-+ +--+--+----+----+ +-+---+-----+-+
| TSN | DN MPLS | | TSN | DN IP | | TSN | DN MPLS | | TSN | DN IP |
+-----+---------+ +-----+-------+ +-----+---------+ +-----+-------+
]]></artwork>
]]></artwork> </figure>
</figure> <t>
As shown in <xref target="dn_svc_encaps" format="default"/> and as descr
<t> ibed in
<xref target="RFC8938" format="default"/>, a DetNet flow
As shown in <xref target="dn_svc_encaps"/> as per <xref can be treated as an App-flow, e.g., at DetNet
target="RFC8938"/> a DetNet flow
can be treated as an application level flow (App-flow) e.g., at DetNet
flow aggregation or in a sub-network that interconnects DetNet nodes. flow aggregation or in a sub-network that interconnects DetNet nodes.
</t> </t>
<t>
<t>
The DetNet flow and service information model provided by this document The DetNet flow and service information model provided by this document
contains both DetNet flow and App-flow specific information in an contains both DetNet-flow- and App-flow-specific information in an
integrated fashion. integrated fashion.
</t> </t>
<t>In a given network scenario three information models can be distinguished <t>In a given network scenario, three information models can be distinguis
: hed:
</t>
<list style="symbols"> <ul spacing="normal">
<li>
<t> Flow information models that describe characteristics of data flows. The
Flow models that describe characteristics of data flows. These models se models
describe in detail all relevant aspects of a flow that are needed to describe, in detail, all relevant aspects of a flow that are needed to
support the flow properly by the network between the source and the support the flow properly by the network between the source and the
destination(s). destination(s).
</t> </li>
<t> <li>
Service models that describe characteristics of services being provided Service information models that describe characteristics of services bei
for data flows over a network. These models can be treated as a network ng provided
operator independent information model. for data flows over a network. These models can be treated as an informa
</t> tion model that is
<t> network operator independent.
Configuration models that describe in detail the settings required on </li>
network nodes to provide a data flow proper service. <li>
</t> Configuration information models that describe, in detail, the settings
</list> required on
</t> network nodes to provide proper service to a data flow.
</li>
<t> </ul>
<t>
Service and flow information models are used between the user and the Service and flow information models are used between the user and the
network operator. Configuration information models are used between network operator. Configuration information models are used between
the management/control plane entity of the network and the network the management/control plane entity of the network and the network
nodes. They are shown in <xref target="fig_infomodels"/>. nodes. They are shown in <xref target="fig_infomodels" format="default"
</t> />.
</t>
<figure title="Usage of Information models (flow, service and configurat <figure anchor="fig_infomodels">
ion)" anchor="fig_infomodels"> <name>Usage of Information Models (Flow, Service, and Configuration)</na
<artwork><![CDATA[ me>
<artwork name="" type="" align="center" alt=""><![CDATA[
User Network Operator User Network Operator
flow/service flow/service
/\ info model +---+ /\ info model +---+
/ \ <---------------> | X | management/control / \ <---------------> | X | management/control
---- +-+-+ plane entity ---- +-+-+ plane entity
^ ^
| configuration | configuration
| info model | info model
+------------+ +------------+
v | | v | |
+-+ | v Network +-+ | v network
+-+ v +-+ nodes +-+ v +-+ nodes
+-+ +-+ +-+ +-+
+-+ +-+
]]></artwork> ]]></artwork>
</figure> </figure>
<t> <t>
DetNet flow and service information model is based on <xref The DetNet flow and service information model is based on <xref target="
target="RFC8655"/> and on the concept of RFC8655"
data model specified by <xref target="IEEE8021Qcc"/>. format="default"/> and the concept of the
<!-- Furthermore, the data model specified by <xref target="IEEE8021Qcc" format="default"/>.
DetNet flow and service information models described in this docu
ment
are based on <xref target="IEEE8021Qcc"/>. -->
In addition to In addition to
the TSN data model, <xref target="IEEE8021Qcc"/> also specifies the TSN data model, <xref target="IEEE8021Qcc" format="default"/> also s pecifies
configuration of TSN features (e.g., traffic scheduling specified by configuration of TSN features (e.g., traffic scheduling specified by
<xref target="IEEE8021Qbv"/>). The common architecture and flow <xref target="IEEE8021Qbv" format="default"/>). The common architecture
model, allow configured features to be consistent in certain deployment and flow information
model allow configured features to be consistent in certain deployment
scenarios, e.g., when the network that provides the DetNet service scenarios, e.g., when the network that provides the DetNet service
includes both L3 and L2 network segments. includes both L3 and L2 network segments.
</t> </t>
<section numbered="true" toc="default">
<section title="Goals"> <name>Goals</name>
<t> <t>
As expressed in the <xref target="IETFDetNet"/> Charter, the DetNet As expressed in the DetNet WG Charter <xref target="IETFDetNet" format
="default"/>, the DetNet
WG collaborates with IEEE 802.1 TSN in order to define a common WG collaborates with IEEE 802.1 TSN in order to define a common
architecture for both Layer 2 and Layer 3. This is beneficial for architecture for both Layers 2 and 3. This is beneficial for
several reasons, e.g., in order to simplify implementations and several reasons, e.g., in order to simplify implementations and
maintain consistency across diverse networks. The flow and service maintain consistency across diverse networks. The flow and service
information models are also aligned for those reasons. Therefore, the information models are also aligned for those reasons. Therefore, the
DetNet flow and service information models described in this document DetNet flow and service information models described in this document
are based on <xref target="IEEE8021Qcc"/>, which is an amendment to are based on <xref target="IEEE8021Qcc" format="default"/>, which is a
<xref target="IEEE8021Q"/>.</t> n amendment to
<xref target="IEEE8021Q" format="default"/>.</t>
<t> <t>
This document specifies flow and service information models only. This document specifies flow and service information models only.
</t> </t>
</section> </section>
<section numbered="true" toc="default">
<section title="Non Goals"> <name>Non-Goals</name>
<t> <t>
This document does not specify flow data models or This document does not specify flow data models or
DetNet configuration. Therefore, the goals of this document DetNet configuration. Therefore, the goals of this document
differ from the goals of <xref target="IEEE8021Qcc"/>, which also differ from the goals of <xref target="IEEE8021Qcc" format="default"/ >, which also
specifies the TSN data model and configuration of certain TSN feature s. specifies the TSN data model and configuration of certain TSN feature s.
</t> </t>
<t>The DetNet-specific YANG data model is described in
<t>The DetNet specific YANG data model is described in <xref target="I-D.ietf-detnet-yang" format="default"/>.
<xref target="I-D.ietf-detnet-yang"/>. </t>
</t> </section>
</section> </section>
<section numbered="true" toc="default">
</section> <name>Terminology</name>
<section numbered="true" toc="default">
<!-- +++++++++++++++++++++++++++++++++++++++++++++++++++++++ --> <name>Terms Used in This Document</name>
<!-- +++++++ CONFORMANCE CONVENTIONS +++++++ --> <t>
<!-- +++++++ TERMINOLOGY +++++++ -->
<!-- +++++++++++++++++++++++++++++++++++++++++++++++++++++++ -->
<section title="Terminology">
<section title="Terms Used in This Document">
<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 DetNet Data Plane <xref target="RFC8655" format="default"/> and the DetNet data plane
Framework <xref target="RFC8938"/>. The reader framework <xref target="RFC8938" format="default"/>. The reader
is assumed to be familiar with these documents and any terminology defined is assumed to be familiar with these documents and any terminology defined
therein. The DetNet &lt;=&gt; TSN dictionary of <xref therein. The DetNet &lt;=&gt; TSN dictionary of <xref target="RFC8655" forma
target="RFC8655"/> is used to perform t="default"/> is used to perform
translation from <xref target="IEEE8021Qcc"/> to this document. translation from <xref target="IEEE8021Qcc" format="default"/> to this docume
</t> nt.
<t> </t>
The following terminology is used in accordance with <xref target="RFC8655"/> <t>
: The following terminology is used in accordance with <xref target="RFC8655" f
<list style="hanging" hangIndent="14"> ormat="default"/>:
<t hangText="App-flow"> </t>
<dl newline="false" spacing="normal" indent="14">
<dt>App-flow</dt>
<dd>
The payload (data) carried over a DetNet service. The payload (data) carried over a DetNet service.
</t> </dd>
<t hangText="DetNet flow"> <dt>DetNet flow</dt>
A DetNet flow is a sequence of packets which conform uniquely <dd>
to a flow identifier, and to which the DetNet service is to A sequence of packets that conform uniquely
to a flow identifier and to which the DetNet service is to
be provided. It includes any DetNet headers added to support be provided. It includes any DetNet headers added to support
the DetNet service and forwarding sub-layers. the DetNet service and forwarding sub-layers.
</t> </dd>
</list> </dl>
</t> <t>The following terminology is introduced in this document:</t>
<dl newline="false" spacing="normal" indent="14">
<t> <dt>Source</dt>
The following terminology is introduced in this document: <dd>
<list style="hanging" hangIndent="14">
<t hangText="Source">
Reference point for an App-flow, where the flow starts. Reference point for an App-flow, where the flow starts.
</t> </dd>
<dt>Destination</dt>
<t hangText="Destination"> <dd>
Reference point for an App-flow, where the flow terminates. Reference point for an App-flow, where the flow terminates.
</t> </dd>
<dt>DN Ingress</dt>
<t hangText="DN Ingress"> <dd>
Reference point for the start of a DetNet flow. Networking Reference point for the start of a DetNet flow. Networking technolog
technology specific encapsulation may be added here to the served y-specific
App-flow(s). encapsulation may be added here to the served App-flow(s).
</t> </dd>
<dt>DN Egress</dt>
<t hangText="DN Egress"> <dd>
Reference point for the termination of a DetNet flow. Networking Reference point for the end of a DetNet flow. Networking technology-
technology specific encapsulation may be removed here from the specific
served App-flow(s). encapsulation may be removed here from the served App-flow(s).
</t> </dd>
</dl>
</list> </section>
</t> <section numbered="true" toc="default">
</section> <name>Abbreviations</name>
<t>
<section title="Abbreviations">
<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="DetNet">Deterministic Networking.</t> <dl newline="false" spacing="normal" indent="14">
<t hangText="DN">DetNet.</t> <dt>DetNet</dt>
<t hangText="MPLS">Multiprotocol Label Switching.</t> <dd>Deterministic Networking</dd>
<t hangText="PSN">Packet Switched Network.</t> <dt>DN</dt>
<t hangText="TSN">Time-Sensitive Networking.</t> <dd>DetNet</dd>
</list> <dt>MPLS</dt>
</t> <dd>Multiprotocol Label Switching</dd>
</section> <dt>PSN</dt>
<dd>Packet Switched Network</dd>
<section title="Naming Conventions"> <dt>TSN</dt>
<t> <dd>Time-Sensitive Networking</dd>
</dl>
</section>
<section numbered="true" toc="default">
<name>Naming Conventions</name>
<t>
The following naming conventions were used for naming information model The following naming conventions were used for naming information model
components in this document. It is recommended that extensions of the components in this document. It is recommended that extensions of the
model use the same conventions. model use the same conventions.
<list style="symbols"> </t>
<t>Descriptive names are used.</t> <ul spacing="normal">
<t>Names start with uppercase letters.</t> <li>Descriptive names are used.</li>
<t> <li>Names start with uppercase letters.</li>
<li>
Composed names use capital letters for the first letter of each Composed names use capital letters for the first letter of each
component. All other letters are lowercase, even for acronyms. component. All other letters are lowercase, even for abbreviations.
Exceptions are made for acronyms containing a mixture of lowercase and Exceptions are made for abbreviations containing a mixture of lowercase
and
capital letters, such as IPv6. Example composed names are SourceMacAddre ss and capital letters, such as IPv6. Example composed names are SourceMacAddre ss and
DestinationIPv6Address. </t> DestinationIPv6Address. </li>
</list> </ul>
</t> </section>
</section> </section>
<section anchor="sec_modeling" numbered="true" toc="default">
</section> <!-- end of terminology --> <name>DetNet Domain and Its Modeling</name>
<section anchor="sec_soverview" numbered="true" toc="default">
<!-- +++++++++++++++++++++++++++++++++++++++++++++++++++++++ --> <name>DetNet Service Overview</name>
<!-- +++++++ DETNET DOMAIN MODELING +++++++ -->
<!-- +++++++++++++++++++++++++++++++++++++++++++++++++++++++ -->
<section anchor="sec_modeling" title="DetNet Domain and its Modeling">
<section anchor="sec_soverview" title="DetNet Service Overview">
<t> <t>
The DetNet service can be defined as a service that provides a The DetNet service can be defined as a service that provides a
capability to carry a unicast or a multicast data flow for an capability to carry a unicast or a multicast data flow for an
application with constrained requirements on network performance, application with constrained requirements on network performance,
e.g., low packet loss rate and/or latency. e.g., low packet loss rate and/or latency.
</t> </t>
<t> <t>
Figure 5 and Figure 8 in <xref Figures 5 and 8 in <xref target="RFC8655" format="default"/> show the
target="RFC8655"/> show the DetNet DetNet service-related reference points and main components.
service related reference points and main components.
</t> </t>
</section> </section>
<section anchor="sec_srefpoints" numbered="true" toc="default">
<section anchor="sec_srefpoints" title="Reference Points Used in Modeling"> <name>Reference Points Used in Modeling</name>
<t> <t>
From service design perspective a fundamental question is the From a service-design perspective, a fundamental question is the
location of the service/flow endpoints, i.e., where the service/flow location of the service/flow endpoints, i.e., where the service/flow
starts and ends. starts and ends.
</t> </t>
<t> <t>
App-flow specific reference points are the Source (where it starts) App-flow-specific reference points are the source (where it starts)
and the Destination (where it terminates). Similarly a DetNet flow and the destination (where it terminates). Similarly, a DetNet flow
has reference points termed DN Ingress (where a DetNet flow starts) an has reference points termed "DN Ingress" (where a DetNet flow starts)
d DN and "DN
Egress (where a DetNet flow ends). These reference points may coexist Egress" (where a DetNet flow ends). These reference points may coexist
in the in the
same node (e.g., in a DetNet IP end system). DN Ingress and DN Egress same node (e.g., in a DetNet IP end system). DN Ingress and DN Egress
reference points are intermediate reference points for a served reference points are intermediate reference points for a served
App-flow. App-flow.
</t> </t>
<t> <t>
All reference points are assumed in this document to be packet-based In this document, all reference points are assumed to be packet-based
reference points. A DN Ingress may add and a DN Egress may remove reference points. A DN Ingress may add and a DN Egress may remove
networking technology specific encapsulation to/from the served networking technology-specific encapsulation to/from the served
App-flow(s) (e.g., MPLS label(s), UDP and IP headers). App-flow(s) (e.g., MPLS label(s), UDP, and IP headers).
</t> </t>
</section> </section>
<section anchor="sec_sinfoelements" numbered="true" toc="default">
<section anchor="sec_sinfoelements" title="Information Elements"> <name>Information Elements</name>
<t> <t>
The DetNet flow information model and the service model relies on The DetNet flow information model and the service information model rel
y on
three groups of information elements: three groups of information elements:
<list style="symbols"> </t>
<t> <dl newline="false" spacing="normal">
App-flow related parameters: these describe the App-flow <dt>App-flow-related parameters:</dt>
<dd>These describe the App-flow
characteristics (e.g., identification, encapsulation, traffic characteristics (e.g., identification, encapsulation, traffic
specification, endpoints, status, etc.) and the App-flow specification, endpoints, status, etc.) and the App-flow
service expectations (e.g., delay, loss, etc.). service expectations (e.g., delay, loss, etc.).</dd>
</t> <dt>DetNet flow-related parameters:</dt>
<t> <dd>These describe the DetNet flow
DetNet flow related parameters: these describe the DetNet flow
characteristics (e.g., identification, format, traffic characteristics (e.g., identification, format, traffic
specification, endpoints, rank, etc.). specification, endpoints, rank, etc.).</dd>
</t> <dt>DetNet service-related parameters:</dt>
<t> <dd>These describe the expected
DetNet service related parameters: these describe the expected
service characteristics (e.g., delivery type, connectivity service characteristics (e.g., delivery type, connectivity
delay/loss, status, rank, etc.). delay/loss, status, rank, etc.).</dd>
</t> </dl>
</list>
</t>
<t> <t>
In the information model a DetNet flow contains one or more (aggregate In the information model, a DetNet flow contains one or more (aggregat
d) App-flows ed) App-flows
(N:1 mapping). During DetNet aggregation the aggregated DetNet flows (N:1 mapping). During DetNet aggregation, the aggregated DetNet flows
are treated simply as App-flows and the aggregate is the DetNet flow, which are treated simply as App-flows and the aggregate is the DetNet flow, which
provides N:1 mapping. Similarly, there is an aggregated many to one re provides N:1 mapping. Similarly, there is an aggregated many-to-one re
lationship for lationship for
the DetNet flow(s) to the DetNet Service. the DetNet flow(s) to the DetNet service.
</t> </t>
</section> </section>
</section>
</section> <!-- end detnet domain modeling --> <section anchor="sec_appflow" numbered="true" toc="default">
<name>App-Flow-Related Parameters</name>
<!-- +++++++++++++++++++++++++++++++++++++++++++++++++++++++ --> <t>
<!-- +++++++ APP-FLOW +++++++ --> When DetNet service is required by time-/loss-sensitive
<!-- +++++++++++++++++++++++++++++++++++++++++++++++++++++++ -->
<section anchor="sec_appflow" title="App-flow Related Parameters">
<t>
When Deterministic service is required by time/loss sensitive
application(s) running on an end system during communication with its application(s) running on an end system during communication with its
peer(s), the resulting data exchange has various requirements on delay peer(s), the resulting data exchange has various requirements on delay
and/or loss parameters. and/or loss parameters.
</t> </t>
<section anchor="sec_appflowchar" numbered="true" toc="default">
<section anchor="sec_appflowchar" title="App-flow Characteristics"> <name>App-Flow Characteristics</name>
<t>App-flow characteristics are described by the following parameters: <t>App-flow characteristics are described by the following parameters:
<list style="symbols"> </t>
<t>FlowID: a unique (management) identifier of the App-flow. <dl newline="false" spacing="normal" indent="14">
It can be used to define the N:1 mapping of App-flows to a Det <dt>FlowID:</dt>
Net flow.</t> <dd>a unique (management) identifier of the App-flow, which can be used
<t>FlowType: set by the encapsulation format of the flow. to define the N:1 mapping of App-flows to a DetNet flow</dd>
It can be Ethernet (TSN), MPLS, or IP.</t> <dt>FlowType:</dt>
<t>DataFlowSpecification: a flow descriptor, defining which packet <dd>set by the encapsulation format of the flow, which can be Ethernet
s (TSN), MPLS, or IP</dd>
belongs to a flow, using specific packet header fields such as <dt>DataFlowSpecification:</dt>
src-addr, dst-addr, label, VLAN-ID, etc.</t> <dd>a flow descriptor, defining which packets
<t>TrafficSpecification: a flow descriptor, defining traffic belongs to a flow, using specific packet header fields, such a
parameters such as packet size, transmission time s
interval, and maximum packets per time interval.</t> src-addr, dst-addr, label, VLAN-ID, etc.</dd>
<t>FlowEndpoints: delineate the start and termination reference <dt>TrafficSpecification:</dt>
<dd>a flow descriptor, defining traffic
parameters, such as packet size, transmission time
interval, and maximum packets per time interval</dd>
<dt>FlowEndpoints:</dt>
<dd>delineates the start and end reference
points of the App-flow by pointing to the source points of the App-flow by pointing to the source
interface/node and destination interface(s)/node(s).</t> interface/node and destination interface(s)/node(s)</dd>
<t>FlowStatus: indicates the status of the App-flow with respect t <dt>FlowStatus:</dt>
o <dd>indicates the status of the App-flow with respect to
the establishment of the flow by the connected network, e.g., the establishment of the flow by the connected network, e.g.,
ready, failed, etc.</t> ready, failed, etc.</dd>
<t>FlowRank: indicates the rank of this flow relative to other <dt>FlowRank:</dt>
flows in the connected network.</t> <dd>indicates the rank of this flow relative to other
</list> flows in the connected network</dd>
</t> </dl>
<t> <aside>
Note: When defining the N:1 mapping of App-flows to a DetNet fl <t>Note: When defining the N:1 mapping of App-flows to a DetNet flow,
ow,
the App-flows must have the same FlowType and different the App-flows must have the same FlowType and different
DataFlowSpecification parameters DataFlowSpecification parameters.</t>
</t> </aside>
</section> </section>
<section anchor="sec_appflowreq" numbered="true" toc="default">
<section anchor="sec_appflowreq" title="App-flow Requirements"> <name>App-Flow Requirements</name>
<t>App-flow requirements are described by the following parameters: <t>App-flow requirements are described by the following parameters:
<list style="symbols"> </t>
<t>FlowRequirements: defines the attributes of the App-flow regard <dl newline="false" spacing="normal" indent="14">
ing <dt>FlowRequirements:</dt>
bandwidth, latency, latency variation, loss, and misordering t <dd>defines the attributes of the App-flow regarding
olerance.</t> bandwidth, latency, latency variation, loss, and misordering t
<t>FlowBiDir: defines the data path requirement of the App-flow olerance</dd>
<dt>FlowBiDir:</dt>
<dd>defines the data path requirement of the App-flow
whether it must share the same data path and physical whether it must share the same data path and physical
path for both directions through the network, e.g., to path for both directions through the network, e.g., to
provide congruent paths in the two directions. </t> provide congruent paths in the two directions</dd>
</list> </dl>
</t> </section>
</section> </section>
<section anchor="sec_dnflow" numbered="true" toc="default">
</section> <!-- end App-flow modeling --> <name>DetNet Flow-Related Parameters</name>
<t>
<!-- +++++++++++++++++++++++++++++++++++++++++++++++++++++++ --> The data model specified by <xref target="IEEE8021Qcc" format="default"/
<!-- +++++++ DETNET-FLOW +++++++ --> > describes data
<!-- +++++++++++++++++++++++++++++++++++++++++++++++++++++++ -->
<section anchor="sec_dnflow" title="DetNet Flow Related Parameters">
<t>
The Data model specified by <xref target="IEEE8021Qcc"/> describes data
flows using TSN service as periodic flows with fixed packet size (i.e., flows using TSN service as periodic flows with fixed packet size (i.e.,
Constant Bit Rate (CBR) flows) or with variable packet size. The same Constant Bitrate (CBR) flows) or with variable packet size. The same
concept is applied for flows using DetNet service. concept is applied for flows using DetNet service.
</t> </t>
<t>
<t>
Latency and loss parameters are correlated because the effect of late Latency and loss parameters are correlated because the effect of late
delivery can result in data loss for an application. However, not all delivery can result in data loss for an application. However, not all
applications require hard limits on both latency and loss. applications require hard limits on both latency and loss.
For example, some real-time applications allow graceful degradation if For example, some real-time applications allow graceful degradation if
loss happens (e.g., sample-based data processing, media distribution). S ome loss happens (e.g., sample-based data processing and media distribution) . Some
other applications may require high-bandwidth connections that make use of other applications may require high-bandwidth connections that make use of
packet replication techniques which are economically challenging or even packet replication techniques that are economically challenging or even
impossible. Some applications may not tolerate loss, but are not impossible. Some applications may not tolerate loss but are not
delay sensitive (e.g., bufferless sensors). Time or loss sensitive delay sensitive (e.g., bufferless sensors). Time- or loss-sensitive
applications may have somewhat special requirements especially for loss applications may have somewhat special requirements, especially for loss
(e.g., no loss over two consecutive communication cycles; very low outag (e.g., no loss over two consecutive communication cycles, very low outag
e e
time, etc.).</t> time, etc.).</t>
<t>DetNet flows have the following attributes:
<?rfc subcompact="yes" ?> </t>
<ol spacing="compact" type="a">
<t>DetNet flows have the following attributes: <li>DnFlowID (<xref target="sec_dnflowid" format="default"/>)</li>
<list style="letters"> <li>DnPayloadType (<xref target="sec_dnpayloadtype" format="default"/>)<
<t>DnFlowID (<xref target="sec_dnflowid"/>)</t> /li>
<t>DnPayloadType (<xref target="sec_dnpayloadtype"/>)</t> <li>DnFlowFormat (<xref target="sec_dnflowformat" format="default"/>)</l
<t>DnFlowFormat (<xref target="sec_dnflowformat"/>)</t> i>
<t>DnFlowSpecification (<xref target="sec_dnflowspec"/>)</t> <li>DnFlowSpecification (<xref target="sec_dnflowspec" format="default"/
<t>DnTrafficSpecification (<xref target="sec_dntrafficspec"/>)</ >)</li>
t> <li>DnTrafficSpecification (<xref target="sec_dntrafficspec" format="def
<t>DnFlowEndpoints (<xref target="sec_dnflowendp"/>)</t> ault"/>)</li>
<t>DnFlowRank (<xref target="sec_dnflowrank"/>)</t> <li>DnFlowEndpoints (<xref target="sec_dnflowendp" format="default"/>)</
<t>DnFlowStatus (<xref target="sec_dnflowstatus"/>)</t> li>
</list> <li>DnFlowRank (<xref target="sec_dnflowrank" format="default"/>)</li>
</t> <li>DnFlowStatus (<xref target="sec_dnflowstatus" format="default"/>)</l
i>
<t>DetNet flows have the following requirement attributes: </ol>
<list style="symbols"> <t>DetNet flows have the following requirement attributes:
<t>DnFlowRequirements (<xref target="sec_dnflowreq"/>)</t> </t>
<t>DnFlowBiDir (<xref target="sec_dnflowbidir"/>)</t> <ol spacing="compact" type="a">
</list> <li>DnFlowRequirements (<xref target="sec_dnflowreq" format="default"/>)
</t> </li>
<li>DnFlowBiDir (<xref target="sec_dnflowbidir" format="default"/>)</li>
<t>Flow attributes are described in the following sections.</t> </ol>
<t>Flow attributes are described in the following sections.</t>
<section anchor="sec_dnflowid" title="Management ID of the DetNet Flow"> <section anchor="sec_dnflowid" numbered="true" toc="default">
<name>Management ID of the DetNet Flow</name>
<t>A unique (management) identifier is needed for each DetNet flow withi n the <t>A unique (management) identifier is needed for each DetNet flow withi n the
DetNet domain. It is specified by DnFlowID. It can be used to define the N:1 DetNet domain. It is specified by DnFlowID. It can be used to define the N:1
mapping of DetNet flows to a DetNet service.</t> mapping of DetNet flows to a DetNet service.</t>
</section> </section>
<section anchor="sec_dnpayloadtype" numbered="true" toc="default">
<section anchor="sec_dnpayloadtype" title="Payload type of the DetNet Flow"> <name>Payload Type of the DetNet Flow</name>
<t>The DnPayloadType attribute is set according to the encapsulated App- flow format. <t>The DnPayloadType attribute is set according to the encapsulated App- flow format.
The attribute can be Ethernet, MPLS, or IP.</t> The attribute can be Ethernet, MPLS, or IP.</t>
</section> </section>
<section anchor="sec_dnflowformat" numbered="true" toc="default">
<section anchor="sec_dnflowformat" title="Format of the DetNet Flow"> <name>Format of the DetNet Flow</name>
<t>The DnFlowFormat attribute is set according to the DetNet PSN technol ogy. <t>The DnFlowFormat attribute is set according to the DetNet PSN technol ogy.
The attribute can be MPLS or IP.</t> The attribute can be MPLS or IP.</t>
</section> </section>
<section anchor="sec_dnflowspec" numbered="true" toc="default">
<section anchor="sec_dnflowspec" title="Identification and Specification of D <name>Identification and Specification of DetNet Flows</name>
etNet Flows"> <t>Identification options for DetNet flows at the Ingress/Egress and wit
<t>Identification options for DetNet flows at the Ingress/Egress and withi hin the DetNet
n the DetNet domain are specified as follows; see <xref target="sec_flowspecmpls" f
domain are specified as follows; see <xref target="sec_flowspecmpls"/> ormat="default"/> for
for DetNet MPLS flows and <xref target="sec_flowspecip" format="default"/>
DetNet MPLS flows and <xref target="sec_flowspecip"/> for DetNetw IP f for DetNet IP flows.</t>
lows.</t> <section anchor="sec_flowspecmpls" numbered="true" toc="default">
<name>DetNet MPLS Flow Identification and Specification</name>
<!-- +++++++ DETNET MPLS FLOW ID & SPEC +++++++ -->
<section anchor="sec_flowspecmpls" title="DetNet MPLS Flow Identification
and Specification">
<t> <t>
The identification of DetNet MPLS flows within the DetNet domain is The identification of DetNet MPLS flows within the DetNet domain is
based on the MPLS context in the service information model. The based on the MPLS context in the service information model. The
attributes are specific to the MPLS forwarding paradigm within the attributes are specific to the MPLS forwarding paradigm within the
DetNet domain <xref target="I-D.ietf-detnet-mpls"/>. DetNet MPLS DetNet domain <xref target="RFC8964" format="default"/>. DetNet MPLS
flows can be identified and specified by the following attributes: flows can be identified and specified by the following attributes:
<list style="letters"> </t>
<t>SLabel</t> <ol spacing="compact" type="a">
<t>FLabelStack</t> <li>SLabel</li>
</list> <li>FLabelStack</li>
</t> </ol>
</section> </section>
<!-- +++++++ DETNET IP FLOW ID & SPEC +++++++ --> <section anchor="sec_flowspecip" numbered="true" toc="default">
<section anchor="sec_flowspecip" title="DetNet IP Flow Identification and <name>DetNet IP Flow Identification and Specification</name>
Specification"> <t>DetNet IP flows can be identified and specified by the following at
<t>DetNet IP flows can be identified and specified by the following tributes
attributes <xref target="RFC8939" format="default"/>:
<xref target="RFC8939"/>: </t>
<list style="letters"> <ol spacing="compact" type="a">
<t>SourceIpAddress</t> <li>SourceIpAddress</li>
<t>DestinationIpAddress</t> <li>DestinationIpAddress</li>
<t>IPv6FlowLabel</t> <li>IPv6FlowLabel</li>
<t>Dscp (attribute)</t> <li>Dscp</li>
<t>Protocol</t> <li>Protocol</li>
<t>SourcePort</t> <li>SourcePort</li>
<t>DestinationPort</t> <li>DestinationPort</li>
<t>IPSecSpi</t> <li>IPSecSpi</li>
</list> </ol>
</t> <t>The IP 6-tuple that is used for DetNet IP flow identification consi
<t>The IP 6-tuple that is used for DetNet IP flow identi sts
fication consists
of items a, b, d, e, f, and g. Items c and h are additi onal attributes of items a, b, d, e, f, and g. Items c and h are additi onal attributes
that can be used for DetNet flow identification in addit ion to the 6-tuple. that can be used for DetNet flow identification in addit ion to the 6-tuple.
6-tuple and use of wild cards for these attributes are s The 6-tuple and use of wild cards for these attributes a
pecified in re specified in
<xref target="RFC8939"/>. <xref target="RFC8939" format="default"/>.
</t> </t>
</section>
</section> </section>
<section anchor="sec_dntrafficspec" numbered="true" toc="default">
</section> <!-- +++++++ FLOW SPEC +++++++ --> <name>Traffic Specification of the DetNet Flow</name>
<?rfc subcompact="no" ?> <t>The DnTrafficSpecification attributes specify how the DN Ingress tran
smits packets
<!-- +++++++ TRAFFIC SPEC +++++++ --> for the DetNet flow.
<section anchor="sec_dntrafficspec" title="Traffic Specification of the DetNe
t Flow">
<t>DnTrafficSpecification attributes specify how the DN Ingress transmits
packets for the DetNet flow.
This is effectively the promise/request of the DN Ingress to the netwo rk. The network uses This is effectively the promise/request of the DN Ingress to the netwo rk. The network uses
this traffic specification to allocate resources and adjust queue para meters in network this traffic specification to allocate resources and adjust queue para meters in network
nodes.</t> nodes.</t>
<t>TrafficSpecification has the following attributes:
<t>TrafficSpecification has the following attributes: </t>
<list style="letters"> <ol spacing="normal" type="a">
<t> <li>
Interval: the period of time in which the traffic Interval: the period of time in which the traffic
specification is specified. specification is specified
</t> </li>
<t> <li>
MaxPacketsPerInterval: the maximum number of packets that the MaxPacketsPerInterval: the maximum number of packets that the
Ingress will transmit in one Interval. Ingress will transmit in one Interval
</t> </li>
<t> <li>
MaxPayloadSize: the maximum payload size that the Ingress MaxPayloadSize: the maximum payload size that the Ingress
will transmit. will transmit
</t> </li>
<t> <li>
MinPayloadSize: the minimum payload size that the Ingress MinPayloadSize: the minimum payload size that the Ingress
will transmit. will transmit
</t> </li>
<t> <li>
MinPacketsPerInterval: the minimum number of packets that the MinPacketsPerInterval: the minimum number of packets that the
Ingress will transmit in one Interval. Ingress will transmit in one Interval
</t> </li>
</list> </ol>
</t> <t>
<t>
These attributes can be used to describe any type of traffic (e.g., These attributes can be used to describe any type of traffic (e.g.,
CBR, VBR, etc.) and can be used during resource allocation to CBR, Variable Bitrate (VBR), etc.) and can be used during resource all
represent worst case scenarios. Intervals are specified as an integer ocation to
represent worst-case scenarios. Intervals are specified as an integer
number of nanoseconds. PayloadSizes are specified in octets. number of nanoseconds. PayloadSizes are specified in octets.
</t> </t>
<t> <t>
Flows exceeding the traffic specification (i.e., having more tr affic Flows exceeding the traffic specification (i.e., having more tr affic
than defined by the maximum attributes) may receive a different than defined by the maximum attributes) may receive a different
network behavior than the DetNet network has been engineered fo r. network behavior than the DetNet network has been engineered fo r.
Excess traffic due to malicious or malfunctioning devices can b e Excess traffic due to malicious or malfunctioning devices can b e
prevented or mitigated (e.g., through the use of existing mecha nisms prevented or mitigated (e.g., through the use of existing mecha nisms,
such as policing and shaping). such as policing and shaping).
</t> </t>
<t> <t>
When MinPayloadSize and MinPacketsPerInterval parameters are used, When MinPayloadSize and MinPacketsPerInterval parameters are used,
then all packets less than the MinPayloadSize will be counted a s all packets less than the MinPayloadSize will be counted as
being of the size MinPayloadSize during packet processing when being of the size MinPayloadSize during packet processing when
packet size matters, e.g., when policing; and all flows having less packet size matters, e.g., when policing; all flows having less
than MinPacketsPerInterval will be counted as having than MinPacketsPerInterval will be counted as having
MinPacketsPerInterval when the number of packets per interval MinPacketsPerInterval when the number of packets per interval
matters, e.g., during resource reservation. However, flows havi ng matters, e.g., during resource reservation. However, flows havi ng
less than MinPacketsPerInterval may result in a different netwo rk less than MinPacketsPerInterval may result in a different netwo rk
behavior than the DetNet network has been engineered for. behavior than the DetNet network has been engineered for.
MinPayloadSize and MinPacketsPerInterval parameters, for exampl e, MinPayloadSize and MinPacketsPerInterval parameters, for exampl e,
may be used when engineering the latency bounds of a DetNet flo w may be used when engineering the latency bounds of a DetNet flo w
when POF is applied to the given DetNet flow. when Packet Ordering Function (POF) is applied to the given Det
</t> Net flow.
</t>
<t> Further optional <t> Further optional
attributes can be considered to achieve more efficient resource alloca tion. attributes can be considered to achieve more efficient resource alloca tion.
Such optional attributes might be worth for flows with soft requiremen ts (i.e., Such optional attributes might be worth for flows with soft requiremen ts (i.e.,
the flow is only loss sensitive or only delay sensitive, but not both the flow is only loss sensitive or only delay sensitive but not both
delay-and-loss sensitive). Possible options how to extend delay and loss sensitive). Possible options about how to extend
DnTrafficSpecification attributes is for further discussion. DnTrafficSpecification attributes is for further discussion.
</t> </t>
</section> <!-- +++++++ TRAFFIC SPEC +++++++ --> </section>
<section anchor="sec_dnflowendp" numbered="true" toc="default">
<section anchor="sec_dnflowendp" title="Endpoints of the DetNet Flow"> <name>Endpoints of the DetNet Flow</name>
<t> <t>
The DnFlowEndpoints attribute defines the starting and termination The DnFlowEndpoints attribute defines the start and end
reference points of the DetNet flow by pointing to the ingress reference points of the DetNet flow by pointing to the ingress
interface/node and egress interface(s)/node(s). Depending on the interface/node and egress interface(s)/node(s). Depending on the
network scenario it defines an interface or a node. Interface can be network scenario, it defines an interface or a node. Interface can be
defined for example if the App-flow is a TSN Stream and it is received defined, for example, if the App-flow is a TSN Stream, and it is receive
over a well defined UNI (User-to-Network Interface). For example, for Ap d
p-flows with MPLS over a well-defined User-to-Network Interface (UNI). For example, for Ap
encapsulation defining an ingress node is more common when per platform p-flows with MPLS
encapsulation, defining an ingress node is more common when a per-platfo
rm
label space is used. label space is used.
</t> </t>
</section> </section>
<section anchor="sec_dnflowrank" numbered="true" toc="default">
<section anchor="sec_dnflowrank" title="Rank of the DetNet Flow"> <name>Rank of the DetNet Flow</name>
<t> <t>
The DnFlowRank attribute provides the rank of this flow relative to other flows in the The DnFlowRank attribute provides the rank of this flow relative to other flows in the
DetNet domain. Rank (range: 0-255) is used by the DetNet domain to DetNet domain. Rank (range: 0-255) is used by the DetNet domain to
decide which flows can and cannot exist when network resources reach decide which flows can and cannot exist when network resources reach
their limit. Rank is used to help to determine which flows can be their limit. Rank is used to help to determine which flows can be
bumped (i.e., removed from node configuration thereby releasing its bumped (i.e., removed from node configuration thereby releasing its
resources) if for example a port of a node becomes oversubscribed (e.g., resources) if, for example, a port of a node becomes oversubscribed (e.g.
due to network re-configuration). DnFlowRank value 0 is the highest prior ,
ity. due to network reconfiguration). DnFlowRank value 0 is the highest priori
</t> ty.
</section> </t>
</section>
<section anchor="sec_dnflowstatus" title="Status of the DetNet Flow"> <section anchor="sec_dnflowstatus" numbered="true" toc="default">
<t>DnFlowStatus provides the status of the DetNet flow with respect to t <name>Status of the DetNet Flow</name>
he <t>The DnFlowStatus attribute provides the status of the DetNet flow wit
h respect to the
establishment of the flow by the DetNet domain. </t> establishment of the flow by the DetNet domain. </t>
<t>DnFlowStatus includes the following attributes:
<?rfc subcompact="yes" ?> </t>
<t>The DnFlowStatus includes the following attributes: <ol spacing="normal" type="a"><li>
<list style="letters"> <t>
<t>
DnIngressStatus is an enumeration for the status of the DnIngressStatus is an enumeration for the status of the
flow&acute;s Ingress reference point: flow's Ingress reference point:
<list style="symbols"> </t>
<t>None: no Ingress.</t> <dl newline="false" spacing="compact">
<t>Ready: Ingress is ready.</t> <dt>None:</dt> <dd>No Ingress.</dd>
<t>Failed: Ingress failed.</t> <dt>Ready:</dt> <dd>Ingress is ready.</dd>
<t>OutOfService: Administratively blocked.</t> <dt>Failed:</dt> <dd>Ingress failed.</dd>
<?rfc subcompact="no" ?> <dt>OutOfService:</dt> <dd>Administratively blocked.</dd>
</list> </dl>
</li>
</t> <li>
<t> <t>
DnEgressStatus is an enumeration for the status of the DnEgressStatus is an enumeration for the status of the
flow&acute;s Egress reference points: flow's Egress reference points:
<list style="symbols"> </t>
<?rfc subcompact="yes" ?> <dl newline="false" spacing="compact">
<t>None: no Egress.</t> <dt>None:</dt> <dd>No Egress.</dd>
<t>Ready: all Egresses are ready.</t> <dt>Ready:</dt> <dd>All Egresses are ready.</dd>
<t>PartialFailed: One or more Egress ready, and one or <dt>PartialFailed:</dt> <dd>One or more Egress is ready, and one o
r
more Egress failed. The DetNet flow can be used more Egress failed. The DetNet flow can be used
if the Ingress is Ready.</t> if the Ingress is Ready.</dd>
<t>Failed: All Egresses failed.</t> <dt>Failed:</dt> <dd>All Egresses failed.</dd>
<t>OutOfService: All Egresses are administratively blocked <dt>OutOfService:</dt> <dd>All Egresses are administratively block
.</t> ed.</dd>
<?rfc subcompact="no" ?> </dl>
</list> </li>
</t> <li>
<t> FailureCode is a nonzero code that specifies the error
FailureCode: A non-zero code that specifies the error
if the DetNet flow encounters a failure (e.g., packet if the DetNet flow encounters a failure (e.g., packet
replication and elimination is requested but not replication and elimination is requested but not
possible, or DnIngressStatus is Failed, or possible or DnIngressStatus is Failed,
DnEgressStatus is Failed, or DnEgressStatus is DnEgressStatus is Failed, or DnEgressStatus is
PartialFailed). PartialFailed).
</t> </li>
</list> </ol>
</t> <t>
<t> Defining FailureCodes for DetNet is out of scope for this document.
Defining FailureCodes for DetNet is out-of-scope in this document. Table 46-1 of <xref target="IEEE8021Qcc" format="default"/> des
Table 46-1 of <xref target="IEEE8021Qcc"/> describes TSN failur cribes TSN failure codes.
e codes. </t>
</t> </section>
</section> <section anchor="sec_dnflowreq" numbered="true" toc="default">
<name>Requirements of the DetNet Flow</name>
<!-- +++++++ DETNET FLOW REQUIREMENTS +++++++ --> <t>
<section anchor="sec_dnflowreq" title="Requirements of the DetNet Flow"> The DnFlowRequirements attribute specifies requirements to ensure t
he service level
<t>
DnFlowRequirements specifies requirements to ensure the service lev
el
desired for the DetNet flow. desired for the DetNet flow.
</t> </t>
<t>DnFlowRequirements includes the following attributes:
<?rfc subcompact="yes" ?> </t>
<t>The DnFlowRequirements includes the following attributes: <ol spacing="compact" type="a">
<list style="letters"> <li>MinBandwidth (<xref target="sec_flowminband" format="default"/>)</l
<t>MinBandwidth(<xref target="sec_flowminband"/>)</t> i>
<t>MaxLatency(<xref target="sec_flowmaxlatency"/>)</t> <li>MaxLatency (<xref target="sec_flowmaxlatency" format="default"/>)<
<t>MaxLatencyVariation(<xref target="sec_flowmaxlatencyvari"/>)< /li>
/t> <li>MaxLatencyVariation (<xref target="sec_flowmaxlatencyvari" format=
<t>MaxLoss(<xref target="sec_flowmaxloss"/>)</t> "default"/>)</li>
<t>MaxConsecutiveLossTolerance(<xref target="sec_flowmaxconsloss <li>MaxLoss (<xref target="sec_flowmaxloss" format="default"/>)</li>
"/>)</t> <li>MaxConsecutiveLossTolerance (<xref target="sec_flowmaxconsloss" fo
<t>MaxMisordering(<xref target="sec_flowmaxmisorder"/>)</t> rmat="default"/>)</li>
</list> <li>MaxMisordering (<xref target="sec_flowmaxmisorder" format="default
</t> "/>)</li>
</ol>
<section anchor="sec_flowminband" title="Minimum Bandwidth of the DetNet Flow <section anchor="sec_flowminband" numbered="true" toc="default">
"> <name>Minimum Bandwidth of the DetNet Flow</name>
<t> <t>
MinBandwidth is the minimum bandwidth that has to be guaranteed for MinBandwidth is the minimum bandwidth that has to be guaranteed for
the DetNet flow. MinBandwidth is specified in octets per second. the DetNet flow. MinBandwidth is specified in octets per second.
</t> </t>
</section> </section>
<section anchor="sec_flowmaxlatency" numbered="true" toc="default">
<section anchor="sec_flowmaxlatency" title="Maximum Latency of the DetNet Flo <name>Maximum Latency of the DetNet Flow</name>
w"> <t>
<t>
MaxLatency is the maximum latency from Ingress to Egress(es) for a MaxLatency is the maximum latency from Ingress to Egress(es) for a
single packet of the DetNet flow. MaxLatency is specified as an single packet of the DetNet flow. MaxLatency is specified as an
integer number of nanoseconds. integer number of nanoseconds.
</t> </t>
</section> </section>
<section anchor="sec_flowmaxlatencyvari" numbered="true" toc="default">
<section anchor="sec_flowmaxlatencyvari" title="Maximum Latency Variation of <name>Maximum Latency Variation of the DetNet Flow</name>
the DetNet Flow"> <t>
<t>
MaxLatencyVariation is the difference between the minimum and the MaxLatencyVariation is the difference between the minimum and the
maximum end-to-end one-way latency. MaxLatencyVariation is specified as an maximum end-to-end, one-way latency. MaxLatencyVariation is specified a s an
integer number of nanoseconds. integer number of nanoseconds.
</t> </t>
</section> </section>
<section anchor="sec_flowmaxloss" numbered="true" toc="default">
<section anchor="sec_flowmaxloss" title="Maximum Loss of the DetNet Flow"> <name>Maximum Loss of the DetNet Flow</name>
<t> <t>
MaxLoss defines the maximum Packet Loss Ratio (PLR) requirement for MaxLoss defines the maximum Packet Loss Rate (PLR) requirement for
the DetNet flow between the Ingress and Egress(es) and the loss the DetNet flow between the Ingress and Egress(es) and the loss
measurement interval. measurement interval.
</t> </t>
</section> </section>
<section anchor="sec_flowmaxconsloss" numbered="true" toc="default">
<section anchor="sec_flowmaxconsloss" title="Maximum Consecutive Loss of the <name>Maximum Consecutive Loss of the DetNet Flow</name>
DetNet Flow"> <t>
<t> Some applications have special loss requirements, such as
Some applications have special loss requirement, such as
MaxConsecutiveLossTolerance. The maximum consecutive loss tolerance MaxConsecutiveLossTolerance. The maximum consecutive loss tolerance
parameter describes the maximum number of consecutive packets whose parameter describes the maximum number of consecutive packets whose
loss can be tolerated. The maximum consecutive loss tolerance can be loss can be tolerated. The maximum consecutive loss tolerance can be
measured for example based on sequence number. measured, for example, based on sequence number.
</t> </t>
</section> </section>
<section anchor="sec_flowmaxmisorder" numbered="true" toc="default">
<section anchor="sec_flowmaxmisorder" title="Maximum Misordering Tolerance of <name>Maximum Misordering Tolerance of the DetNet Flow</name>
the DetNet Flow"> <t>
<t>
MaxMisordering describes the tolerable maximum number of packets MaxMisordering describes the tolerable maximum number of packets
that can be received out of order. The value zero for the maximum that can be received out of order. The value zero for the maximum
allowed misordering indicates that in order delivery is requir ed, allowed misordering indicates that in-order delivery is requir ed;
misordering cannot be tolerated. misordering cannot be tolerated.
</t> </t>
<t> <t>
The maximum allowed misordering can be measured for example ba The maximum allowed misordering can be measured, for example,
sed based
on sequence numbers. When a packet arrives at the egress after a on sequence numbers. When a packet arrives at the egress after a
packet with a higher sequence number, the difference between t he packet with a higher sequence number, the difference between t he
sequence number values cannot be bigger than sequence number values cannot be bigger than
"MaxMisordering + 1". "MaxMisordering + 1".
</t> </t>
</section> </section>
</section>
</section> <!-- end DETNET FLOW REQUIREMENTS --> <section anchor="sec_dnflowbidir" numbered="true" toc="default">
<name>BiDir Requirement of the DetNet Flow</name>
<section anchor="sec_dnflowbidir" title="BiDir requirement of the DetNet Flow <t>
"> The DnFlowBiDir attribute defines the requirement that the flow and
<t>
DnFlowBiDir attribute defines the requirement that the flow and
the corresponding reverse direction flow must share the same path the corresponding reverse direction flow must share the same path
(links and nodes) through the routed or switch network in the DetNet (links and nodes) through the routed or switch network in the DetNet
domain, e.g., to provide congruent paths in the two directions that domain, e.g., to provide congruent paths in the two directions that
share fate and path characteristics. share fate and path characteristics.
</t>
</section>
</section> <!-- end DetNet flow modeling -->
<!-- +++++++++++++++++++++++++++++++++++++++++++++++++++++++ -->
<!-- +++++++ DETNET SERVICE +++++++ -->
<!-- +++++++++++++++++++++++++++++++++++++++++++++++++++++++ -->
<section anchor="sec_servicemodel" title="DetNet Service Related Parameters">
<t>DetNet service have the following attributes:
<list style="letters">
<t>DnServiceID (<xref target="sec_dnserviceid"/>)</t>
<t>DnServiceDeliveryType (<xref target="sec_dnservdelivtype"/>)<
/t>
<t>DnServiceDeliveryProfile (<xref target="sec_dnservdelivprof"/
>)</t>
<t>DNServiceConnectivity (<xref target="sec_dnservcon"/>)</t>
<t>DnServiceBiDir (<xref target="sec_dnservbidir"/>)</t>
<t>DnServiceRank (<xref target="sec_dnservrank"/>)</t>
<t>DnServiceStatus (<xref target="sec_dnservstat"/>)</t>
</list>
</t> </t>
</section>
<t>Service attributes are described in the following sections.</t> </section>
<section anchor="sec_servicemodel" numbered="true" toc="default">
<section anchor="sec_dnserviceid" title="Management ID of the DetNet service" <name>DetNet Service-Related Parameters</name>
> <t>The DetNet service has the following attributes:</t>
<t> <ol spacing="compact" type="a">
A unique (management) identifier for each DetNet service within <li>DnServiceID (<xref target="sec_dnserviceid" format="default"/>)</li>
the DetNet domain. It can be used to define the many to one <li>DnServiceDeliveryType (<xref target="sec_dnservdelivtype" format="de
fault"/>)</li>
<li>DnServiceDeliveryProfile (<xref target="sec_dnservdelivprof" format=
"default"/>)</li>
<li>DNServiceConnectivity (<xref target="sec_dnservcon" format="default"
/>)</li>
<li>DnServiceBiDir (<xref target="sec_dnservbidir" format="default"/>)</
li>
<li>DnServiceRank (<xref target="sec_dnservrank" format="default"/>)</li
>
<li>DnServiceStatus (<xref target="sec_dnservstat" format="default"/>)</
li>
</ol>
<t>Service attributes are described in the following sections.</t>
<section anchor="sec_dnserviceid" numbered="true" toc="default">
<name>Management ID of the DetNet Service</name>
<t>
The DnServiceId attribute is a unique (management) identifier for e
ach DetNet service within
the DetNet domain. It can be used to define the many-to-one
mapping of DetNet flows to a DetNet service. mapping of DetNet flows to a DetNet service.
</t> </t>
</section> </section>
<section anchor="sec_dnservdelivtype" numbered="true" toc="default">
<section anchor="sec_dnservdelivtype" title="Delivery Type of the DetNet serv <name>Delivery Type of the DetNet Service</name>
ice"> <t>
<t>
The DnServiceDeliveryType attribute is set according to the payload of The DnServiceDeliveryType attribute is set according to the payload of
the served DetNet flow (i.e., the encapsulated App-flow format). the served DetNet flow (i.e., the encapsulated App-flow format).
The attribute can be Ethernet, MPLS, or IP. The attribute can be Ethernet, MPLS, or IP.
</t> </t>
</section> </section>
<section anchor="sec_dnservdelivprof" numbered="true" toc="default">
<!-- +++++++ DETNET SERVICE REQUIREMENTS +++++++ --> <name>Delivery Profile of the DetNet Service</name>
<section anchor="sec_dnservdelivprof" title="Delivery Profile of the DetNet S <t>The DnServiceDeliveryProfile attribute specifies the delivery profile
ervice"> to ensure proper serving of
<t>DnServiceDeliveryProfile specifies delivery profile to ensure prope
r serving of
the DetNet flow.</t> the DetNet flow.</t>
<t>DnServiceDeliveryProfile includes the following attributes:
<t>The DnServiceDeliveryProfile includes the following attributes: </t>
<list style="letters"> <ol spacing="compact" type="a">
<t>MinBandwidth(<xref target="sec_minband"/>)</t> <li>MinBandwidth (<xref target="sec_minband" format="default"/>)</li>
<t>MaxLatency(<xref target="sec_maxlatency"/>)</t> <li>MaxLatency (<xref target="sec_maxlatency" format="default"/>)</li>
<t>MaxLatencyVariation(<xref target="sec_maxlatencyvari"/>)</t> <li>MaxLatencyVariation (<xref target="sec_maxlatencyvari" format="def
<t>MaxLoss(<xref target="sec_maxloss"/>)</t> ault"/>)</li>
<t>MaxConsecutiveLossTolerance(<xref target="sec_maxlconsloss"/>) <li>MaxLoss (<xref target="sec_maxloss" format="default"/>)</li>
</t> <li>MaxConsecutiveLossTolerance (<xref target="sec_maxlconsloss" forma
<t>MaxMisordering(<xref target="sec_maxmisorder"/>)</t> t="default"/>)</li>
</list> <li>MaxMisordering (<xref target="sec_maxmisorder" format="default"/>)
</t> </li>
</ol>
<section anchor="sec_minband" title="Minimum Bandwidth of the DetNet Service" <section anchor="sec_minband" numbered="true" toc="default">
> <name>Minimum Bandwidth of the DetNet Service</name>
<t> <t>
MinBandwidth is the minimum bandwidth that has to be guaranteed for MinBandwidth is the minimum bandwidth that has to be guaranteed for
the DetNet service. MinBandwidth is specified in octets per second the DetNet service. MinBandwidth is specified in octets per second
and excludes additional DetNet header (if any). and excludes additional DetNet header (if any).
</t> </t>
</section> </section>
<section anchor="sec_maxlatency" numbered="true" toc="default">
<section anchor="sec_maxlatency" title="Maximum Latency of the DetNet Service <name>Maximum Latency of the DetNet Service</name>
"> <t>
<t>
MaxLatency is the maximum latency from Ingress to Egress(es) for a MaxLatency is the maximum latency from Ingress to Egress(es) for a
single packet of the DetNet flow. MaxLatency is specified as an single packet of the DetNet flow. MaxLatency is specified as an
integer number of nanoseconds. integer number of nanoseconds.
</t> </t>
</section> </section>
<section anchor="sec_maxlatencyvari" numbered="true" toc="default">
<section anchor="sec_maxlatencyvari" title="Maximum Latency Variation of the <name>Maximum Latency Variation of the DetNet Service</name>
DetNet Service"> <t>
<t>
MaxLatencyVariation is the difference between the minimum and the MaxLatencyVariation is the difference between the minimum and the
maximum end-to-end one-way latency. MaxLatencyVariation is specified maximum end-to-end, one-way latency. MaxLatencyVariation is specified
as an integer number of nanoseconds. as an integer number of nanoseconds.
</t> </t>
</section> </section>
<section anchor="sec_maxloss" numbered="true" toc="default">
<section anchor="sec_maxloss" title="Maximum Loss of the DetNet Service"> <name>Maximum Loss of the DetNet Service</name>
<t> <t>
MaxLoss defines the maximum Packet Loss Ratio (PLR) parameter for the MaxLoss defines the maximum Packet Loss Rate (PLR) parameter for the
DetNet service between the Ingress and Egress(es) of the DetNet DetNet service between the Ingress and Egress(es) of the DetNet
domain. domain.
</t> </t>
</section> </section>
<section anchor="sec_maxlconsloss" numbered="true" toc="default">
<section anchor="sec_maxlconsloss" title="Maximum Consecutive Loss of the Det <name>Maximum Consecutive Loss of the DetNet Service</name>
Net Service"> <t>
<t> Some applications have a special loss requirement, such as
Some applications have special loss requirement, such as
MaxConsecutiveLossTolerance. The maximum consecutive loss tolerance MaxConsecutiveLossTolerance. The maximum consecutive loss tolerance
parameter describes the maximum number of consecutive packets whose parameter describes the maximum number of consecutive packets whose
loss can be tolerated. The maximum consecutive loss tolerance can be loss can be tolerated. The maximum consecutive loss tolerance can be
measured for example based on sequence number. measured, for example, based on sequence number.
</t> </t>
</section> </section>
<section anchor="sec_maxmisorder" numbered="true" toc="default">
<section anchor="sec_maxmisorder" title="Maximum Misordering Tolerance of the <name>Maximum Misordering Tolerance of the DetNet Service</name>
DetNet Service"> <t>
<t>
MaxMisordering describes the tolerable maximum number of packets MaxMisordering describes the tolerable maximum number of packets
that can be received out of order. The maximum allowed misordering that can be received out of order. The maximum allowed misordering
can be measured for example based on sequence number. The value zero can be measured, for example, based on sequence number. The value zer
for the maximum allowed misordering indicates that in order delivery o
is required, misordering cannot be tolerated. for the maximum allowed misordering indicates that in-order delivery
</t> is required; misordering cannot be tolerated.
</section> </t>
</section>
</section> <!-- end DETNET SERVICE REQUIREMENTS --> </section>
<section anchor="sec_dnservcon" numbered="true" toc="default">
<section anchor="sec_dnservcon" title="Connectivity Type of the DetNet Servic <name>Connectivity Type of the DetNet Service</name>
e"> <t>
<t>
Two connectivity types are distinguished: point-to-point (p2p) and Two connectivity types are distinguished: point-to-point (p2p) and
point-to-multipoint (p2mp). Connectivity type p2mp may be crea ted by point-to-multipoint (p2mp). Connectivity type p2mp may be crea ted by
a forwarding function (e.g., p2mp LSP). (Note: from service a forwarding function (e.g., p2mp LSP). (Note that from a serv
perspective mp2mp connectivity can be treated as a superpositio ice
n of perspective, mp2mp connectivity can be treated as a superpositi
on of
p2mp connections.) p2mp connections.)
</t> </t>
</section> </section>
<section anchor="sec_dnservbidir" numbered="true" toc="default">
<section anchor="sec_dnservbidir" title="BiDir requirement of the DetNet Serv <name>BiDir Requirement of the DetNet Service</name>
ice"> <t>
<t>
The DnServiceBiDir attribute defines the requirement that the flow an d The DnServiceBiDir attribute defines the requirement that the flow an d
the corresponding reverse direction flow must share the same path the corresponding reverse direction flow must share the same path
(links and nodes) through the routed or switch network in the DetNet (links and nodes) through the routed or switch network in the DetNet
domain, e.g., to provide congruent paths in the two directions that domain, e.g., to provide congruent paths in the two directions that
share fate and path characteristics. share fate and path characteristics.
</t> </t>
</section> </section>
<section anchor="sec_dnservrank" numbered="true" toc="default">
<section anchor="sec_dnservrank" title="Rank of the DetNet Service"> <name>Rank of the DetNet Service</name>
<t> <t>
The DnServiceRank attribute provides the rank of a service instance The DnServiceRank attribute provides the rank of a service instance
relative to other services in the DetNet domain. DnServiceRank relative to other services in the DetNet domain. DnServiceRank
(range: 0-255) is used by the network in case of network resource (range: 0-255) is used by the network in case of network resource
limitation scenarios. DnServiceRank value 0 is the highest priority. limitation scenarios. DnServiceRank value 0 is the highest priority.
</t> </t>
</section> </section>
<section anchor="sec_dnservstat" numbered="true" toc="default">
<section anchor="sec_dnservstat" title="Status of the DetNet Service"> <name>Status of the DetNet Service</name>
<t> <t>
DnServiceStatus information group includes elements that specify the The DnServiceStatus information group includes elements that specify th
status of the service specific state of the DetNet domain. This e
status of the service-specific state of the DetNet domain. This
information group informs the user whether or not the service is ready information group informs the user whether or not the service is ready
for use. for use.
</t> </t>
<t>DnServiceStatus includes the following attributes:</t>
<t> The DnServiceStatus includes the following attributes: <ol spacing="normal" type="a"><li>
<?rfc subcompact="yes" ?> <t>DnServiceIngressStatus is an enumeration for the status of the se
<list style="letters"> rvice's Ingress:
<t>DnServiceIngressStatus is an enumeration for the status of th </t>
e service&acute;s Ingress: <dl newline="false" spacing="compact">
<list style="symbols"> <dt>None:</dt> <dd>No Ingress.</dd>
<t>None: no Ingress.</t> <dt>Ready:</dt> <dd>Ingress is ready.</dd>
<t>Ready: Ingress is ready.</t> <dt>Failed:</dt> <dd>Ingress failed.</dd>
<t>Failed: Ingress failed.</t> <dt>OutOfService:</dt> <dd>Administratively blocked.</dd>
<t>OutOfService: Administratively blocked.</t> </dl>
<?rfc subcompact="no" ?> </li>
</list> <li>
</t> <t>DnServiceEgressStatus is an enumeration for the status of the ser
<t>DnServiceEgressStatus is an enumeration for the status of the vice's Egress:
service&acute;s Egress: </t>
<list style="symbols"> <dl newline="false" spacing="compact">
<?rfc subcompact="yes" ?> <dt>None:</dt> <dd>No Egress.</dd>
<t>None: no Egress.</t> <dt>Ready:</dt> <dd>All Egresses are ready.</dd>
<t>Ready: all Egresses are ready.</t> <dt>PartialFailed:</dt> <dd>One or more Egress is ready, and one o
<t>PartialFailed: One or more Egress ready, and one or mor r more Egress failed.
e Egress failed. The DetNet flow can be used if the Ingress is
The DetNet flow can be used if the Ingress is Ready.</dd>
Ready.</t> <dt>Failed:</dt> <dd>All Egresses failed.</dd>
<t>Failed: All Egresses failed.</t> <dt>OutOfService:</dt> <dd>Administratively blocked.</dd>
<t>OutOfService: Administratively blocked.</t> </dl>
<?rfc subcompact="no" ?> </li>
</list> <li>
</t> DnServiceFailureCode is a nonzero code that specifies
<t>
DnServiceFailureCode: A non-zero code that specifies
the error if the DetNet service encounters a failure the error if the DetNet service encounters a failure
(e.g., packet replication and elimination is requested (e.g., packet replication and elimination is requested
but not possible, or DnServiceIngressStatus is Failed, but not possible or DnServiceIngressStatus is Failed,
or DnServiceEgressStatus is Failed, or DnServiceEgressStatus is Failed, or
DnServiceEgressStatus is PartialFailed). DnServiceEgressStatus is PartialFailed).
</t> </li>
</list> </ol>
</t> <t>
<t> Defining DnServiceFailureCodes for DetNet service is out of scope
Defining DnServiceFailureCodes for DetNet service is out-of-scope for this document. Table 46-1 of <xref target="IEEE8021Q
in this document. Table 46-1 of <xref target="IEEE8021Qc cc" format="default"/>
c"/>
describes TSN failure codes. describes TSN failure codes.
</t> </t>
</section>
</section> </section>
</section> <!-- end DetNet service modeling -->
<section anchor="sec_flowspecoper" title="Flow Specific Operations">
<t>The DetNet flow information model relies on three high level informat <section anchor="sec_flowspecoper" numbered="true" toc="default">
ion groups: <name>Flow-Specific Operations</name>
<list style="symbols"> <t>The DetNet flow information model relies on three high-level informatio
<t> n groups:
DnIngress: The DnIngress information group includes elements that </t>
<dl newline="false" spacing="normal">
<dt>DnIngress:</dt>
<dd>The DnIngress information group includes elements that
specify the source for a single DetNet flow. This information specify the source for a single DetNet flow. This information
group is applied from the user of the DetNet service to the group is applied from the user of the DetNet service to the
network. network.</dd>
</t> <dt>DnEgress:</dt>
<t> <dd>The DnEgress information group includes elements that
DnEgress: The DnEgress information group includes elements that
specify the destination for a single DetNet flow. This specify the destination for a single DetNet flow. This
information group is applied from the user of the DetNet information group is applied from the user of the DetNet
service to the network. service to the network.</dd>
</t> <dt>DnFlowStatus:</dt>
<t> <dd>The DnFlowStatus information group includes elements that
DnFlowStatus: The status information group includes elements that
specify the status of the flow in the network. This information specify the status of the flow in the network. This information
group is applied from the network to the user of the DetNet group is applied from the network to the user of the DetNet
service. This information group informs the user whether or not service. This information group informs the user whether or not
the DetNet flow is ready for use. the DetNet flow is ready for use.</dd>
</t> </dl>
</list> <t>
</t>
<t>
There are three possible operations for each DetNet flow with There are three possible operations for each DetNet flow with
respect to its DetNet service at a DN Ingress or a DN Egress respect to its DetNet service at a DN Ingress or a DN Egress
(similarly to App-flows at a Source or a Destination): (similar to App-flows at a source or a destination):
<?rfc subcompact="yes" ?>
<list style="symbols">
<t>Join: DN Ingress/DN Egress intends to join the flow.</t>
<t>Leave: DN Ingress/DN Egress intends to leave the flow.</t>
<t>Modify: DN Ingress/DN Egress intends to change the flow.</t>
</list>
<?rfc subcompact="no" ?>
</t>
<section anchor="sec_flowjoin" title="Join Operation"> </t>
<t> <dl newline="false" spacing="compact">
<dt>Join:</dt>
<dd>DN Ingress/DN Egress intends to join the flow.</dd>
<dt>Leave: </dt>
<dd>DN Ingress/DN Egress intends to leave the flow.</dd>
<dt>Modify:</dt>
<dd>DN Ingress/DN Egress intends to change the flow.</dd>
</dl>
<section anchor="sec_flowjoin" numbered="true" toc="default">
<name>Join Operation</name>
<t>
For the join operation, the DnFlowSpecification, DnFlowRank, For the join operation, the DnFlowSpecification, DnFlowRank,
DnFlowEndpoint, and DnTrafficSpecification are included within DnFlowEndpoint, and DnTrafficSpecification are included within
the DnIngress or DnEgress information group. For the join operation, the DnIngress or DnEgress information groups. For the join operation,
the DnServiceRequirements groups can be included. the DnServiceRequirements groups can be included.
</t> </t>
</section> </section>
<section anchor="sec_flowleave" numbered="true" toc="default">
<section anchor="sec_flowleave" title="Leave Operation"> <name>Leave Operation</name>
<t>For the leave operation, the DnFlowSpecification and DnFlowEndpoint are <t>For the leave operation, the DnFlowSpecification and DnFlowEndpoint a
included within the DnIngress or DnEgress information group.</t> re
</section> included within the DnIngress or DnEgress information groups.</t>
</section>
<section anchor="sec_flowmodify" title="Modify Operation"> <section anchor="sec_flowmodify" numbered="true" toc="default">
<t>For the modify operation, the DnFlowSpecification, DnFlowRank, DnFlowEndp <name>Modify Operation</name>
oint, <t>For the modify operation, the DnFlowSpecification, DnFlowRank, DnFlow
Endpoint,
and DnTrafficSpecification are included within the DnIngress or DnEgress and DnTrafficSpecification are included within the DnIngress or DnEgress
information group. For the join operation, the DnServiceRequirements gro ups information group. For the join operation, the DnServiceRequirements gro ups
can be included. can be included.
</t> </t>
<t> <t>
The Modify operation can be considered to address cases when a flow is The Modify operation can be considered to address cases when a flow is
slightly changed, e.g., only MaxPayloadSize (<xref slightly changed, e.g., only MaxPayloadSize (<xref target="sec_dntraffic
target="sec_dntrafficspec"/>) has been changed. The advantage spec" format="default"/>) has been changed. The advantage
of having a Modify is that it allows initiation of a change of flow spec of having a Modify is that it allows initiation of a change of flow spec
while leaving the current flow is operating until the change is while leaving the current flow operating until the change is
accepted. If there is no linkage between the Join and the Leave, then accepted. If there is no linkage between the Join and the Leave, then
while figuring out whether the new flow spec can be supported, the while figuring out whether the new flow spec can be supported, the
controller entity has to assume that the resources committed to the controller entity has to assume that the resources committed to the
current flow are in use. By using Modify the controller entity knows tha t current flow are in use. By using Modify, the controller entity knows th at
the resources supporting the current flow can be available for the resources supporting the current flow can be available for
supporting the altered flow. Modify is considered to be an optional supporting the altered flow. Modify is considered to be an optional
operation due to possible controller plane limitations. operation due to possible controller plane limitations.
</t> </t>
<t></t> </section>
</section> </section>
<section anchor="sec_sum" numbered="true" toc="default">
</section> <name>Summary</name>
<t>This document describes the DetNet flow information model and the servi
<!-- +++++++++++++++++++++++++++++++++++++++++++++++++++++++ --> ce
<!-- +++++++ SUMMARY +++++++ -->
<!-- +++++++++++++++++++++++++++++++++++++++++++++++++++++++ -->
<section anchor="sec_sum" title="Summary">
<t>This document describes the DetNet flow information model and the ser
vice
information model for DetNet IP networks and DetNet MPLS networks . information model for DetNet IP networks and DetNet MPLS networks .
These models are used as input for creating the DetNet specific These models are used as input for creating the DetNet-specific
YANG model. YANG module.
</t> </t>
</section>
</section> <section anchor="IANA" numbered="true" toc="default">
<name>IANA Considerations</name>
<!-- +++++++++++++++++++++++++++++++++++++++++++++++++++++++ --> <t>This document has no IANA actions.</t>
<!-- +++++++ IANA +++++++ --> </section>
<!-- +++++++++++++++++++++++++++++++++++++++++++++++++++++++ --> <section anchor="Security" numbered="true" toc="default">
<section anchor="IANA" title="IANA Considerations"> <name>Security Considerations</name>
<t>N/A.</t> <t>
</section>
<!-- +++++++++++++++++++++++++++++++++++++++++++++++++++++++ -->
<!-- +++++++ SECURITY +++++++ -->
<!-- +++++++++++++++++++++++++++++++++++++++++++++++++++++++ -->
<section anchor="Security" title="Security Considerations">
<t>
The external interfaces of the DetNet domain need to be subject to The external interfaces of the DetNet domain need to be subject to
appropriate confidentiality. Additionally, knowledge of which flows/servi ces appropriate confidentiality. Additionally, knowledge of which flows/servi ces
are provided to a customer or delivered by a network operator may supply are provided to a customer or delivered by a network operator may supply
information that can be used in a variety of security attacks. information that can be used in a variety of security attacks.
Security considerations for DetNet are described in detail in Security considerations for DetNet are described in detail in
<xref target="I-D.ietf-detnet-security"/>. General security considerations <xref target="I-D.ietf-detnet-security" format="default"/>. General security
are described in <xref target="RFC8655"/>. considerations
are described in <xref target="RFC8655" format="default"/>.
This document discusses modeling the information, not how it is This document discusses modeling the information, not how it is
exchanged. exchanged.
</t> </t>
</section> </section>
</middle>
</middle>
<!-- *****BACK MATTER ***** -->
<back> <back>
<references title="Normative References"> <displayreference target="I-D.ietf-detnet-security" to="DETNET-SECURITY"/>
<!-- <?rfc include='reference.RFC.6003'?> --> <displayreference target="I-D.ietf-detnet-yang" to="DETNET-YANG"/>
<?rfc include='reference.RFC.8655'?>
<?rfc include='reference.I-D.ietf-detnet-mpls'?> <references>
<?rfc include='reference.RFC.8939'?> <name>References</name>
<references>
<name>Normative 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.8964.xml"/>
<xi:include href="https://xml2rfc.ietf.org/public/rfc/bibxml/reference.R
FC.8939.xml"/>
<reference anchor="IEEE8021Qcc" target="https://ieeexplore.ieee.org/docu ment/8514112/"> <reference anchor="IEEE8021Qcc" target="https://ieeexplore.ieee.org/docu ment/8514112/">
<front> <front>
<title>IEEE Std 802.1Qcc-2018: IEEE Standard for Local and metropolita <title>IEEE Standard for Local and Metropolitan Area Networks--Bridg
n area networks - Bridges and Bridged Networks -- Amendment 31: Stream Reservati es and Bridged Networks -- Amendment 31: Stream Reservation Protocol (SRP) Enhan
on Protocol (SRP) Enhancements and Performance Improvements</title> cements and Performance Improvements</title>
<author> <author>
<organization>IEEE Standards Association</organization> <organization>IEEE</organization>
</author> </author>
<date year="2018" /> <date month="October" year="2013"/>
</front> </front>
<seriesInfo name="DOI" value="10.1109/IEEESTD.2018.8514112"/>
<seriesInfo name="IEEE" value="802.1Qcc-2018"/>
</reference> </reference>
</references>
<references>
<name>Informative References</name>
<xi:include href="https://xml2rfc.ietf.org/public/rfc/bibxml/reference.R
FC.8938.xml"/>
</references> <xi:include href="https://datatracker.ietf.org/doc/bibxml3/draft-ietf-de
tnet-security.xml"/>
<references title="Informative References">
<?rfc include='reference.RFC.8938'?> <xi:include href="https://datatracker.ietf.org/doc/bibxml3/reference.I-D
<?rfc include="reference.I-D.ietf-detnet-security"?> .ietf-detnet-yang.xml"/>
<?rfc include="reference.I-D.ietf-detnet-yang"?> <xi:include href="https://xml2rfc.ietf.org/public/rfc/bibxml/reference.R
<?rfc include='reference.RFC.3444'?> FC.3444.xml"/>
<reference anchor="IETFDetNet" target="https://datatracker.ietf.org/wg/d etnet/charter/"> <reference anchor="IETFDetNet" target="https://datatracker.ietf.org/wg/d etnet/charter/">
<front> <front>
<title>IETF Deterministic Networking (DetNet) Working Group</title> <title>Deterministic Networking (detnet)</title>
<author> <author>
<organization>IETF</organization> <organization>IETF</organization>
</author> </author>
<date /> <date/>
</front> </front>
</reference> </reference>
<reference anchor="IEEE8021Q" target="https://ieeexplore.ieee.org/docume nt/8403927"> <reference anchor="IEEE8021Q" target="https://ieeexplore.ieee.org/docume nt/8403927">
<front> <front>
<title>IEEE Std 802.1Q-2018 IEEE Standard for Local and metropolit <title>IEEE Standard for Local and Metropolitan Area Networks--Bridg
an area networks - Bridges and Bridged Networks</title> es and Bridged Networks</title>
<author> <author>
<organization>IEEE Standards Association</organization> <organization>IEEE</organization>
</author> </author>
<date year="2018" /> <date month="July" year="2018"/>
</front> </front>
</reference> <seriesInfo name="DOI" value="10.1109/IEEESTD.2018.8403927"/>
<seriesInfo name="IEEE" value="802.1Q-2018"/>
<reference anchor="IEEE8021Qbv" target="https://ieeexplore.ieee.org/docu </reference>
ment/7572858/">
<front>
<title>IEEE Std 802.1Qbv-2015 IEEE Standard for Local and metropol
itan area networks - Bridges and Bridged Networks - Amendment 25: Enhancements f
or Scheduled Traffic</title>
<author>
<organization>IEEE Standards Association</orga
nization>
</author>
<date year="2015" />
</front>
</reference>
</references>
</back> <reference anchor="IEEE8021Qbv" target="https://ieeexplore.ieee.org/docu
ment/8613095">
<front>
<title>IEEE Standard for Local and metropolitan area networks -- Bri
dges and Bridged Networks - Amendment 25: Enhancements for Scheduled Traffic</ti
tle>
<author>
<organization>IEEE</organization>
</author>
<date month="March" year="2016"/>
</front>
<seriesInfo name="DOI" value="10.1109/IEEESTD.2016.8613095"/>
<seriesInfo name="IEEE" value="802.1Qbv-2015"/>
</reference>
</references>
</references>
</back>
</rfc> </rfc>
 End of changes. 146 change blocks. 
986 lines changed or deleted 917 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/