DetNet Flow Information Model
draft-ietf-detnet-flow-information-model-10
DetNet B. Varga
Internet-Draft J. Farkas
Intended status: Informational Ericsson
Expires: November 16, 2020 R. Cummings
National Instruments
Y. Jiang
Huawei Technologies Co., Ltd.
D. Fedyk
LabN Consulting, L.L.C.
May 15, 2020
DetNet Flow Information Model
draft-ietf-detnet-flow-information-model-10
Abstract
This document describes flow and service information model for
Deterministic Networking (DetNet). These models are defined for IP
and MPLS DetNet data planes
Status of This Memo
This Internet-Draft is submitted in full conformance with the
provisions of BCP 78 and BCP 79.
Internet-Drafts are working documents of the Internet Engineering
Task Force (IETF). Note that other groups may also distribute
working documents as Internet-Drafts. The list of current Internet-
Drafts is at https://datatracker.ietf.org/drafts/current/.
Internet-Drafts are draft documents valid for a maximum of six months
and may be updated, replaced, or obsoleted by other documents at any
time. It is inappropriate to use Internet-Drafts as reference
material or to cite them other than as "work in progress."
This Internet-Draft will expire on November 16, 2020.
Copyright Notice
Copyright (c) 2020 IETF Trust and the persons identified as the
document authors. All rights reserved.
This document is subject to BCP 78 and the IETF Trust's Legal
Provisions Relating to IETF Documents
(https://trustee.ietf.org/license-info) in effect on the date of
publication of this document. Please review these documents
carefully, as they describe your rights and restrictions with respect
Varga, et al. Expires November 16, 2020 [Page 1]
Internet-Draft DetNet Flow Information Model May 2020
to this document. Code Components extracted from this document must
include Simplified BSD License text as described in Section 4.e of
the Trust Legal Provisions and are provided without warranty as
described in the Simplified BSD License.
Table of Contents
1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 3
1.1. Goals . . . . . . . . . . . . . . . . . . . . . . . . . . 5
1.2. Non Goals . . . . . . . . . . . . . . . . . . . . . . . . 5
2. Terminology . . . . . . . . . . . . . . . . . . . . . . . . . 6
2.1. Terms Used in This Document . . . . . . . . . . . . . . . 6
2.2. Abbreviations . . . . . . . . . . . . . . . . . . . . . . 6
2.3. Naming Conventions . . . . . . . . . . . . . . . . . . . 7
3. DetNet Domain and its Modeling . . . . . . . . . . . . . . . 7
3.1. DetNet Service Overview . . . . . . . . . . . . . . . . . 7
3.2. Reference Points Used in Modeling . . . . . . . . . . . . 7
3.3. Information Elements . . . . . . . . . . . . . . . . . . 8
4. App-flow Related Parameters . . . . . . . . . . . . . . . . . 8
4.1. App-flow Characteristics . . . . . . . . . . . . . . . . 8
4.2. App-flow Requirements . . . . . . . . . . . . . . . . . . 9
5. DetNet Flow Related Parameters . . . . . . . . . . . . . . . 9
5.1. Management ID of the DetNet Flow . . . . . . . . . . . . 10
5.2. Payload type of the DetNet Flow . . . . . . . . . . . . . 10
5.3. Format of the DetNet Flow . . . . . . . . . . . . . . . . 10
5.4. Identification and Specification of DetNet Flows . . . . 10
5.4.1. DetNet MPLS Flow Identification and Specification . . 10
5.4.2. DetNet IP Flow Identification and Specification . . . 11
5.5. Traffic Specification of the DetNet Flow . . . . . . . . 11
5.6. Endpoints of the DetNet Flow . . . . . . . . . . . . . . 12
5.7. Rank of the DetNet Flow . . . . . . . . . . . . . . . . . 12
5.8. Status of the DetNet Flow . . . . . . . . . . . . . . . . 12
5.9. Requirements of the DetNet Flow . . . . . . . . . . . . . 13
5.9.1. Minimum Bandwidth of the DetNet Flow . . . . . . . . 13
5.9.2. Maximum Latency of the DetNet Flow . . . . . . . . . 13
5.9.3. Maximum Latency Variation of the DetNet Flow . . . . 13
5.9.4. Maximum Loss of the DetNet Flow . . . . . . . . . . . 13
5.9.5. Maximum Consecutive Loss of the DetNet Flow . . . . . 14
5.9.6. Maximum Misordering Tolerance of the DetNet Flow . . 14
5.10. BiDir requirement of the DetNet Flow . . . . . . . . . . 14
Show full document text