draft-ietf-detnet-flow-information-model-07.txt   draft-ietf-detnet-flow-information-model-08.txt 
DetNet J. Farkas DetNet J. Farkas
Internet-Draft B. Varga Internet-Draft B. Varga
Intended status: Informational Ericsson Intended status: Informational Ericsson
Expires: September 2, 2020 R. Cummings Expires: November 7, 2020 R. Cummings
National Instruments National Instruments
Y. Jiang Y. Jiang
Huawei Technologies Co., Ltd. Huawei Technologies Co., Ltd.
D. Fedyk D. Fedyk
LabN Consulting, L.L.C. LabN Consulting, L.L.C.
March 1, 2020 May 6, 2020
DetNet Flow Information Model DetNet Flow Information Model
draft-ietf-detnet-flow-information-model-07 draft-ietf-detnet-flow-information-model-08
Abstract Abstract
This document describes flow and service information model for This document describes flow and service information model for
Deterministic Networking (DetNet). These models are defined for IP Deterministic Networking (DetNet). These models are defined for IP
and MPLS DetNet data planes and MPLS DetNet data planes
Status of This Memo Status of This Memo
This Internet-Draft is submitted in full conformance with the This Internet-Draft is submitted in full conformance with the
skipping to change at page 1, line 38 skipping to change at page 1, line 38
Internet-Drafts are working documents of the Internet Engineering Internet-Drafts are working documents of the Internet Engineering
Task Force (IETF). Note that other groups may also distribute Task Force (IETF). Note that other groups may also distribute
working documents as Internet-Drafts. The list of current Internet- working documents as Internet-Drafts. The list of current Internet-
Drafts is at https://datatracker.ietf.org/drafts/current/. Drafts is at https://datatracker.ietf.org/drafts/current/.
Internet-Drafts are draft documents valid for a maximum of six months Internet-Drafts are draft documents valid for a maximum of six months
and may be updated, replaced, or obsoleted by other documents at any and may be updated, replaced, or obsoleted by other documents at any
time. It is inappropriate to use Internet-Drafts as reference time. It is inappropriate to use Internet-Drafts as reference
material or to cite them other than as "work in progress." material or to cite them other than as "work in progress."
This Internet-Draft will expire on September 2, 2020. This Internet-Draft will expire on November 7, 2020.
Copyright Notice Copyright Notice
Copyright (c) 2020 IETF Trust and the persons identified as the Copyright (c) 2020 IETF Trust and the persons identified as the
document authors. All rights reserved. document authors. All rights reserved.
This document is subject to BCP 78 and the IETF Trust's Legal This document is subject to BCP 78 and the IETF Trust's Legal
Provisions Relating to IETF Documents Provisions Relating to IETF Documents
(https://trustee.ietf.org/license-info) in effect on the date of (https://trustee.ietf.org/license-info) in effect on the date of
publication of this document. Please review these documents publication of this document. Please review these documents
carefully, as they describe your rights and restrictions with respect carefully, as they describe your rights and restrictions with respect
to this document. Code Components extracted from this document must to this document. Code Components extracted from this document must
include Simplified BSD License text as described in Section 4.e of include Simplified BSD License text as described in Section 4.e of
the Trust Legal Provisions and are provided without warranty as the Trust Legal Provisions and are provided without warranty as
described in the Simplified BSD License. described in the Simplified BSD License.
Table of Contents Table of Contents
1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 3 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 3
1.1. Goals . . . . . . . . . . . . . . . . . . . . . . . . . . 5 1.1. Goals . . . . . . . . . . . . . . . . . . . . . . . . . . 5
1.2. Non Goals . . . . . . . . . . . . . . . . . . . . . . . . 6 1.2. Non Goals . . . . . . . . . . . . . . . . . . . . . . . . 5
2. Terminology . . . . . . . . . . . . . . . . . . . . . . . . . 6 2. Terminology . . . . . . . . . . . . . . . . . . . . . . . . . 6
2.1. Terms Used in This Document . . . . . . . . . . . . . . . 6 2.1. Terms Used in This Document . . . . . . . . . . . . . . . 6
2.2. Abbreviations . . . . . . . . . . . . . . . . . . . . . . 7 2.2. Abbreviations . . . . . . . . . . . . . . . . . . . . . . 6
2.3. Naming Conventions . . . . . . . . . . . . . . . . . . . 7 2.3. Requirements Language . . . . . . . . . . . . . . . . . . 7
2.4. Naming Conventions . . . . . . . . . . . . . . . . . . . 7
3. DetNet Domain and its Modeling . . . . . . . . . . . . . . . 7 3. DetNet Domain and its Modeling . . . . . . . . . . . . . . . 7
3.1. DetNet Service Overview . . . . . . . . . . . . . . . . . 7 3.1. DetNet Service Overview . . . . . . . . . . . . . . . . . 7
3.2. Reference Points Used in Modeling . . . . . . . . . . . . 7 3.2. Reference Points Used in Modeling . . . . . . . . . . . . 7
3.3. Information Elements . . . . . . . . . . . . . . . . . . 8 3.3. Information Elements . . . . . . . . . . . . . . . . . . 8
4. App-flow Related Parameters . . . . . . . . . . . . . . . . . 8 4. App-flow Related Parameters . . . . . . . . . . . . . . . . . 8
4.1. App-flow Characteristics . . . . . . . . . . . . . . . . 9 4.1. App-flow Characteristics . . . . . . . . . . . . . . . . 8
4.2. App-flow Requirements . . . . . . . . . . . . . . . . . . 9 4.2. App-flow Requirements . . . . . . . . . . . . . . . . . . 9
5. DetNet Flow Related Parameters . . . . . . . . . . . . . . . 9 5. DetNet Flow Related Parameters . . . . . . . . . . . . . . . 9
5.1. Management ID of the DetNet Flow . . . . . . . . . . . . 10 5.1. Management ID of the DetNet Flow . . . . . . . . . . . . 10
5.2. Payload type of the DetNet Flow . . . . . . . . . . . . . 10 5.2. Payload type of the DetNet Flow . . . . . . . . . . . . . 10
5.3. Format of the DetNet Flow . . . . . . . . . . . . . . . . 10 5.3. Format of the DetNet Flow . . . . . . . . . . . . . . . . 10
5.4. Identification and Specification of DetNet Flows . . . . 11 5.4. Identification and Specification of DetNet Flows . . . . 11
5.4.1. DetNet MPLS Flow Identification and Specification . . 11 5.4.1. DetNet MPLS Flow Identification and Specification . . 11
5.4.2. DetNet IP Flow Identification and Specification . . . 11 5.4.2. DetNet IP Flow Identification and Specification . . . 11
5.5. Traffic Specification of the DetNet Flow . . . . . . . . 11 5.5. Traffic Specification of the DetNet Flow . . . . . . . . 11
5.6. Endpoints of the DetNet Flow . . . . . . . . . . . . . . 12 5.6. Endpoints of the DetNet Flow . . . . . . . . . . . . . . 12
skipping to change at page 3, line 28 skipping to change at page 3, line 29
11.1. Normative References . . . . . . . . . . . . . . . . . . 19 11.1. Normative References . . . . . . . . . . . . . . . . . . 19
11.2. Informative References . . . . . . . . . . . . . . . . . 20 11.2. Informative References . . . . . . . . . . . . . . . . . 20
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 21 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 21
1. Introduction 1. Introduction
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 delivery latency. A description of the general background and
concepts of DetNet can be found in [I-D.ietf-detnet-architecture]. concepts of DetNet can be found in [RFC8655].
This document describes the Detnet Flow Service Information Model. This document describes the Detnet Flow Service Information Model.
For reference [RFC3444] describes the rational behind Information For reference [RFC3444] describes the rational behind Information
Models in general. This document describes the Flow and Service Models in general. This document describes the Flow and Service
information models for operators and users to understand Detnet information models for operators and users to understand Detnet
services, and for implementors as a guide to the functionality services, and for implementors as a guide to the functionality
required by Detnet services. required by Detnet services.
The DetNet Architecture treats the DetNet related data plane The DetNet Architecture treats the DetNet related data plane
functions decomposed into two sub-layers: a service sub-layer and a functions decomposed into two sub-layers: a service sub-layer and a
skipping to change at page 5, line 23 skipping to change at page 5, line 23
+------------+ +------------+
v | | v | |
+-+ | v Network +-+ | v Network
+-+ v +-+ nodes +-+ v +-+ nodes
+-+ +-+ +-+ +-+
+-+ +-+
Figure 2: Usage of Information models (flow, service and Figure 2: Usage of Information models (flow, service and
configuration) configuration)
DetNet flow and service information model is based on DetNet flow and service information model is based on [RFC8655] and
[I-D.ietf-detnet-architecture] and on the concept of data model on the concept of data model specified by [IEEE8021Qcc].
specified by [IEEE8021Qcc]. Furthermore, the origination of the Furthermore, the origination of the DetNet flow information model was
DetNet flow information model was the flow identification the flow identification possibilities described in [IEEE8021CB],
possibilities described in [IEEE8021CB], which is used by which is used by [IEEE8021Qcc] as well. In addition to the TSN data
[IEEE8021Qcc] as well. In addition to the TSN data model, model, [IEEE8021Qcc] also specifies configuration of TSN features
[IEEE8021Qcc] also specifies configuration of TSN features (e.g., (e.g., traffic scheduling specified by [IEEE8021Qbv]). The common
traffic scheduling specified by [IEEE8021Qbv]). The common
architecture and flow model, allow configured features to be architecture and flow model, allow configured features to be
consistent in certain deployment scenarios, e.g., when the network consistent in certain deployment scenarios, e.g., when the network
that provides the DetNet service includes both L3 and L2 network that provides the DetNet service includes both L3 and L2 network
segments. segments.
1.1. Goals 1.1. Goals
As expressed in the [IETFDetNet] Charter, the DetNet WG collaborates As expressed in the [IETFDetNet] Charter, the DetNet WG collaborates
with IEEE 802.1 TSN in order to define a common architecture for both with IEEE 802.1 TSN in order to define a common architecture for both
Layer 2 and Layer 3. This is beneficial for several reasons, e.g., Layer 2 and Layer 3. This is beneficial for several reasons, e.g.,
skipping to change at page 6, line 17 skipping to change at page 6, line 12
This document (this revision) does not specify flow data models or This document (this revision) does not specify flow data models or
DetNet configuration. Therefore, the goals of this document differ DetNet configuration. Therefore, the goals of this document differ
from the goals of [IEEE8021Qcc], which also specifies the TSN data from the goals of [IEEE8021Qcc], which also specifies the TSN data
model and configuration of certain TSN features. model and configuration of certain TSN features.
2. Terminology 2. Terminology
2.1. Terms Used in This Document 2.1. Terms Used in This Document
This document uses the terminology established in the DetNet This document uses the terminology established in the DetNet
architecture [I-D.ietf-detnet-architecture] and the DetNet Data Plane architecture [RFC8655] and the DetNet Data Plane Framework
Framework [I-D.ietf-detnet-data-plane-framework]. The reader is [I-D.ietf-detnet-data-plane-framework]. The reader is assumed to be
assumed to be familiar with these documents and any terminology familiar with these documents and any terminology defined therein.
defined therein. The DetNet <=> TSN dictionary of The DetNet <=> TSN dictionary of [RFC8655] is used to perform
[I-D.ietf-detnet-architecture] is used to perform translation from translation from [IEEE8021Qcc] to this document.
[IEEE8021Qcc] to this document.
The following terminology is used in accordance with The following terminology is used in accordance with [RFC8655]:
[I-D.ietf-detnet-architecture]:
App-flow The payload (data) carried over a DetNet service. App-flow The payload (data) carried over a DetNet service.
DetNet flow A DetNet flow is a sequence of packets which conform DetNet flow A DetNet flow is a sequence of packets which conform
uniquely to a flow identifier, and to which the DetNet uniquely to a flow identifier, and to which the DetNet
service is to be provided. It includes any DetNet service is to be provided. It includes any DetNet
headers added to support the DetNet service and headers added to support the DetNet service and
forwarding sub-layers. forwarding sub-layers.
The following terminology is introduced in this document: The following terminology is introduced in this document:
skipping to change at page 7, line 19 skipping to change at page 7, line 9
DetNet Deterministic Networking. DetNet Deterministic Networking.
DN DetNet. DN DetNet.
MPLS Multiprotocol Label Switching. MPLS Multiprotocol Label Switching.
PSN Packet Switched Network. PSN Packet Switched Network.
TSN Time-Sensitive Networking. TSN Time-Sensitive Networking.
2.3. Naming Conventions 2.3. Requirements Language
The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
"SHOULD", "SHOULD NOT", "RECOMMENDED", "NOT RECOMMENDED", "MAY", and
"OPTIONAL" in this document are to be interpreted as described in BCP
14 [RFC2119] [RFC8174] when, and only when, they appear in all
capitals, as shown here.
2.4. Naming Conventions
The following naming conventions were used for naming information The following naming conventions were used for naming information
model components in this document. It is recommended that extensions model components in this document. It is recommended that extensions
of the model use the same conventions. of the model use the same conventions.
o Names SHOULD be descriptive. o Names SHOULD be descriptive.
o Names MUST start with uppercase letters. o Names MUST start with uppercase letters.
o Composed names MUST use capital letters for the first letter of o Composed names MUST use capital letters for the first letter of
skipping to change at page 7, line 44 skipping to change at page 7, line 42
3. DetNet Domain and its Modeling 3. DetNet Domain and its Modeling
3.1. DetNet Service Overview 3.1. DetNet Service Overview
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.
Figure 5 and Figure 8 in [I-D.ietf-detnet-architecture] show the Figure 5 and Figure 8 in [RFC8655] show the DetNet service related
DetNet service related reference points and main components. reference points and main components.
3.2. Reference Points Used in Modeling 3.2. Reference Points Used in Modeling
From service design perspective a fundamental question is the From 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.
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) has reference points termed DN Ingress (where a DetNet flow starts)
skipping to change at page 19, line 23 skipping to change at page 19, line 23
information model for DetNet IP networks and DetNet MPLS networks. information model for DetNet IP networks and DetNet MPLS networks.
9. IANA Considerations 9. IANA Considerations
N/A. N/A.
10. Security Considerations 10. Security Considerations
Security considerations for DetNet are described in detail in Security considerations for DetNet are described in detail in
[I-D.ietf-detnet-security]. General security considerations are [I-D.ietf-detnet-security]. General security considerations are
described in [I-D.ietf-detnet-architecture]. This section covers described in [RFC8655]. This section covers security for the Flow
security for the Flow Information Model and there are no additional Information Model and there are no additional security considerations
security considerations introduced by this document. introduced by this document.
11. References 11. References
11.1. Normative References 11.1. Normative References
[I-D.ietf-detnet-architecture]
Finn, N., Thubert, P., Varga, B., and J. Farkas,
"Deterministic Networking Architecture", draft-ietf-
detnet-architecture-13 (work in progress), May 2019.
[I-D.ietf-detnet-ip] [I-D.ietf-detnet-ip]
Varga, B., Farkas, J., Berger, L., Fedyk, D., Malis, A., Varga, B., Farkas, J., Berger, L., Fedyk, D., Malis, A.,
and S. Bryant, "DetNet Data Plane: IP", draft-ietf-detnet- and S. Bryant, "DetNet Data Plane: IP", draft-ietf-detnet-
ip-05 (work in progress), February 2020. ip-05 (work in progress), February 2020.
[I-D.ietf-detnet-mpls] [I-D.ietf-detnet-mpls]
Varga, B., Farkas, J., Berger, L., Fedyk, D., Malis, A., Varga, B., Farkas, J., Berger, L., Fedyk, D., Malis, A.,
Bryant, S., and J. Korhonen, "DetNet Data Plane: MPLS", Bryant, S., and J. Korhonen, "DetNet Data Plane: MPLS",
draft-ietf-detnet-mpls-05 (work in progress), February draft-ietf-detnet-mpls-05 (work in progress), February
2020. 2020.
[RFC2119] Bradner, S., "Key words for use in RFCs to Indicate [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate
Requirement Levels", BCP 14, RFC 2119, Requirement Levels", BCP 14, RFC 2119,
DOI 10.17487/RFC2119, March 1997, DOI 10.17487/RFC2119, March 1997,
<https://www.rfc-editor.org/info/rfc2119>. <https://www.rfc-editor.org/info/rfc2119>.
[RFC8174] Leiba, B., "Ambiguity of Uppercase vs Lowercase in RFC [RFC8174] Leiba, B., "Ambiguity of Uppercase vs Lowercase in RFC
2119 Key Words", BCP 14, RFC 8174, DOI 10.17487/RFC8174, 2119 Key Words", BCP 14, RFC 8174, DOI 10.17487/RFC8174,
May 2017, <https://www.rfc-editor.org/info/rfc8174>. May 2017, <https://www.rfc-editor.org/info/rfc8174>.
[RFC8655] Finn, N., Thubert, P., Varga, B., and J. Farkas,
"Deterministic Networking Architecture", RFC 8655,
DOI 10.17487/RFC8655, October 2019,
<https://www.rfc-editor.org/info/rfc8655>.
11.2. Informative References 11.2. Informative References
[I-D.ietf-detnet-data-plane-framework] [I-D.ietf-detnet-data-plane-framework]
Varga, B., Farkas, J., Berger, L., Malis, A., and S. Varga, B., Farkas, J., Berger, L., Malis, A., and S.
Bryant, "DetNet Data Plane Framework", draft-ietf-detnet- Bryant, "DetNet Data Plane Framework", draft-ietf-detnet-
data-plane-framework-04 (work in progress), February 2020. data-plane-framework-04 (work in progress), February 2020.
[I-D.ietf-detnet-security] [I-D.ietf-detnet-security]
Mizrahi, T., Grossman, E., Hacker, A., Das, S., Dowdell, Mizrahi, T. and E. Grossman, "Deterministic Networking
J., Austad, H., and N. Finn, "Deterministic Networking
(DetNet) Security Considerations", draft-ietf-detnet- (DetNet) Security Considerations", draft-ietf-detnet-
security-08 (work in progress), February 2020. security-09 (work in progress), March 2020.
[IEEE8021CB] [IEEE8021CB]
IEEE Standards Association, "IEEE Std 802.1CB-2017 IEEE IEEE Standards Association, "IEEE Std 802.1CB-2017 IEEE
Standard for Local and metropolitan area networks - Frame Standard for Local and metropolitan area networks - Frame
Replication and Elimination for Reliability", 2017, Replication and Elimination for Reliability", 2017,
<https://ieeexplore.ieee.org/document/8091139/>. <https://ieeexplore.ieee.org/document/8091139/>.
[IEEE8021Q] [IEEE8021Q]
IEEE Standards Association, "IEEE Std 802.1Q-2018 IEEE IEEE Standards Association, "IEEE Std 802.1Q-2018 IEEE
Standard for Local and metropolitan area networks - Standard for Local and metropolitan area networks -
 End of changes. 18 change blocks. 
39 lines changed or deleted 44 lines changed or added

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