draft-ietf-detnet-flow-information-model-11.txt   draft-ietf-detnet-flow-information-model-12.txt 
DetNet B. Varga DetNet B. Varga
Internet-Draft J. Farkas Internet-Draft J. Farkas
Intended status: Informational Ericsson Intended status: Informational Ericsson
Expires: April 24, 2021 R. Cummings Expires: June 5, 2021 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.
October 21, 2020 December 2, 2020
DetNet Flow Information Model DetNet Flow Information Model
draft-ietf-detnet-flow-information-model-11 draft-ietf-detnet-flow-information-model-12
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 April 24, 2021. This Internet-Draft will expire on June 5, 2021.
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
skipping to change at page 2, line 34 skipping to change at page 2, line 34
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 . . . . 10 5.4. Identification and Specification of DetNet Flows . . . . 10
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
5.7. Rank of the DetNet Flow . . . . . . . . . . . . . . . . . 12 5.7. Rank of the DetNet Flow . . . . . . . . . . . . . . . . . 13
5.8. Status of the DetNet Flow . . . . . . . . . . . . . . . . 12 5.8. Status of the DetNet Flow . . . . . . . . . . . . . . . . 13
5.9. Requirements of the DetNet Flow . . . . . . . . . . . . . 13 5.9. Requirements of the DetNet Flow . . . . . . . . . . . . . 14
5.9.1. Minimum Bandwidth of the DetNet Flow . . . . . . . . 13 5.9.1. Minimum Bandwidth of the DetNet Flow . . . . . . . . 14
5.9.2. Maximum Latency of the DetNet Flow . . . . . . . . . 13 5.9.2. Maximum Latency of the DetNet Flow . . . . . . . . . 14
5.9.3. Maximum Latency Variation of the DetNet Flow . . . . 14 5.9.3. Maximum Latency Variation of the DetNet Flow . . . . 14
5.9.4. Maximum Loss of the DetNet Flow . . . . . . . . . . . 14 5.9.4. Maximum Loss of the DetNet Flow . . . . . . . . . . . 14
5.9.5. Maximum Consecutive Loss of the DetNet Flow . . . . . 14 5.9.5. Maximum Consecutive Loss of the DetNet Flow . . . . . 14
5.9.6. Maximum Misordering Tolerance of the DetNet Flow . . 14 5.9.6. Maximum Misordering Tolerance of the DetNet Flow . . 15
5.10. BiDir requirement of the DetNet Flow . . . . . . . . . . 14 5.10. BiDir requirement of the DetNet Flow . . . . . . . . . . 15
6. DetNet Service Related Parameters . . . . . . . . . . . . . . 14 6. DetNet Service Related Parameters . . . . . . . . . . . . . . 15
6.1. Management ID of the DetNet service . . . . . . . . . . . 15 6.1. Management ID of the DetNet service . . . . . . . . . . . 15
6.2. Delivery Type of the DetNet service . . . . . . . . . . . 15 6.2. Delivery Type of the DetNet service . . . . . . . . . . . 15
6.3. Delivery Profile of the DetNet Service . . . . . . . . . 15 6.3. Delivery Profile of the DetNet Service . . . . . . . . . 16
6.3.1. Minimum Bandwidth of the DetNet Service . . . . . . . 15 6.3.1. Minimum Bandwidth of the DetNet Service . . . . . . . 16
6.3.2. Maximum Latency of the DetNet Service . . . . . . . . 15 6.3.2. Maximum Latency of the DetNet Service . . . . . . . . 16
6.3.3. Maximum Latency Variation of the DetNet Service . . . 15 6.3.3. Maximum Latency Variation of the DetNet Service . . . 16
6.3.4. Maximum Loss of the DetNet Service . . . . . . . . . 15 6.3.4. Maximum Loss of the DetNet Service . . . . . . . . . 16
6.3.5. Maximum Consecutive Loss of the DetNet Service . . . 16 6.3.5. Maximum Consecutive Loss of the DetNet Service . . . 16
6.3.6. Maximum Misordering Tolerance of the DetNet Service . 16 6.3.6. Maximum Misordering Tolerance of the DetNet Service . 17
6.4. Connectivity Type of the DetNet Service . . . . . . . . . 16 6.4. Connectivity Type of the DetNet Service . . . . . . . . . 17
6.5. BiDir requirement of the DetNet Service . . . . . . . . . 16 6.5. BiDir requirement of the DetNet Service . . . . . . . . . 17
6.6. Rank of the DetNet Service . . . . . . . . . . . . . . . 16 6.6. Rank of the DetNet Service . . . . . . . . . . . . . . . 17
6.7. Status of the DetNet Service . . . . . . . . . . . . . . 16 6.7. Status of the DetNet Service . . . . . . . . . . . . . . 17
7. Flow Specific Operations . . . . . . . . . . . . . . . . . . 17 7. Flow Specific Operations . . . . . . . . . . . . . . . . . . 18
7.1. Join Operation . . . . . . . . . . . . . . . . . . . . . 18 7.1. Join Operation . . . . . . . . . . . . . . . . . . . . . 19
7.2. Leave Operation . . . . . . . . . . . . . . . . . . . . . 18 7.2. Leave Operation . . . . . . . . . . . . . . . . . . . . . 19
7.3. Modify Operation . . . . . . . . . . . . . . . . . . . . 18 7.3. Modify Operation . . . . . . . . . . . . . . . . . . . . 19
8. Summary . . . . . . . . . . . . . . . . . . . . . . . . . . . 18 8. Summary . . . . . . . . . . . . . . . . . . . . . . . . . . . 19
9. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 19 9. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 19
10. Security Considerations . . . . . . . . . . . . . . . . . . . 19 10. Security Considerations . . . . . . . . . . . . . . . . . . . 20
11. References . . . . . . . . . . . . . . . . . . . . . . . . . 19 11. References . . . . . . . . . . . . . . . . . . . . . . . . . 20
11.1. Normative References . . . . . . . . . . . . . . . . . . 19 11.1. Normative References . . . . . . . . . . . . . . . . . . 20
11.2. Informative References . . . . . . . . . . . . . . . . . 19 11.2. Informative References . . . . . . . . . . . . . . . . . 20
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 20 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 [RFC8655]. concepts of DetNet can be found in [RFC8655].
This document describes the Detnet Flow and Service Information This document describes the Detnet Flow and Service Information
skipping to change at page 11, line 33 skipping to change at page 11, line 33
c. IPv6FlowLabel c. IPv6FlowLabel
d. Dscp (attribute) d. Dscp (attribute)
e. Protocol e. Protocol
f. SourcePort f. SourcePort
g. DestinationPort g. DestinationPort
h. IPSecSpi h. IPSecSpi
The IP 6-tuple that is used for DetNet IP flow identification The IP 6-tuple that is used for DetNet IP flow identification
consists of items a, b, d, e, f, and g. Items c and h are additional consists of items a, b, d, e, f, and g. Items c and h are additional
attributes that can be used for DetNet flow identification in attributes that can be used for DetNet flow identification in
addition to the 6-tuple. addition to the 6-tuple. Using wild cards for these attributes are
specified in [I-D.ietf-detnet-ip].
5.5. Traffic Specification of the DetNet Flow 5.5. Traffic Specification of the DetNet Flow
DnTrafficSpecification attributes specify how the DN Ingress DnTrafficSpecification attributes specify how the DN Ingress
transmits packets for the DetNet flow. This is effectively the transmits packets for the DetNet flow. This is effectively the
promise/request of the DN Ingress to the network. The network uses promise/request of the DN Ingress to the network. The network uses
this traffic specification to allocate resources and adjust queue this traffic specification to allocate resources and adjust queue
parameters in network nodes. parameters in network nodes.
TrafficSpecification has the following attributes: TrafficSpecification has the following attributes:
a. Interval: the period of time in which the traffic specification a. Interval: the period of time in which the traffic specification
is specified. is specified.
b. MaxPacketsPerInterval: the maximum number of packets that the b. MaxPacketsPerInterval: the maximum number of packets that the
Ingress will transmit in one Interval. Ingress will transmit in one Interval.
c. MaxPayloadSize: the maximum payload size that the Ingress will c. MaxPayloadSize: the maximum payload size that the Ingress will
transmit. transmit.
d. MinPayloadSize: the minimum payload size that the Ingress will
transmit.
e. MinPacketsPerInterval: the minimum number of packets that the
Ingress will transmit in one Interval.
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, VBR, etc.) and can be used during resource allocation to
represent worst case scenarios. represent worst case scenarios. Intervals are specified as an
integer number of nanoseconds. PayloadSizes are specified in octets
per second.
When MinPayloadSize and MinPacketsPerInterval parameters are used,
then all packets less than the MinPayloadSize will be counted as
being of the size MinPayloadSize during packet processing when packet
size matters, e.g., when policing; and all flows having less than
MinPacketsPerInterval will be counted as having MinPacketsPerInterval
when the number of packets per interval matters, e.g., during
resource reservation. However, flows having less than
MinPacketsPerInterval may result in a different network behavior than
the DetNet network has been engineered for. MinPayloadSize and
MinPacketsPerInterval parameters, for example, may be used when
engineering the latency bounds of a DetNet flow when POF is applied
to the given DetNet flow.
Further optional attributes can be considered to achieve more Further optional attributes can be considered to achieve more
efficient resource allocation. Such optional attributes might be efficient resource allocation. Such optional attributes might be
worth for flows with soft requirements (i.e., the flow is only loss worth for flows with soft requirements (i.e., the flow is only loss
sensitive or only delay sensitive, but not both delay-and-loss sensitive or only delay sensitive, but not both delay-and-loss
sensitive). Possible options how to extend DnTrafficSpecification sensitive). Possible options how to extend DnTrafficSpecification
attributes is for further discussion. attributes is for further discussion.
5.6. Endpoints of the DetNet Flow 5.6. Endpoints of the DetNet Flow
skipping to change at page 12, line 35 skipping to change at page 13, line 13
when per platform label space is used. when per platform label space is used.
5.7. Rank of the DetNet Flow 5.7. Rank of the DetNet Flow
The DnFlowRank attribute provides the rank of this flow relative to 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 other flows in the DetNet domain. Rank (range: 0-255) is used by the
DetNet domain to decide which flows can and cannot exist when network DetNet domain to decide which flows can and cannot exist when network
resources reach their limit. Rank is used to help to determine which resources reach their limit. Rank is used to help to determine which
flows can be bumped (i.e., removed from node configuration thereby flows can be bumped (i.e., removed from node configuration thereby
releasing its resources) if for example a port of a node becomes releasing its resources) if for example a port of a node becomes
oversubscribed (e.g., due to network re-configuration). oversubscribed (e.g., due to network re-configuration). DnFlowRank
value 0 is the highest priority.
5.8. Status of the DetNet Flow 5.8. Status of the DetNet Flow
DnFlowStatus provides the status of the DetNet flow with respect to DnFlowStatus provides the status of the DetNet flow with respect to
the establishment of the flow by the DetNet domain. the establishment of the flow by the DetNet domain.
The DnFlowStatus includes the following attributes: The DnFlowStatus includes the following attributes:
a. DnIngressStatus is an enumeration for the status of the flow's a. DnIngressStatus is an enumeration for the status of the flow's
Ingress reference point: Ingress reference point:
skipping to change at page 14, line 14 skipping to change at page 14, line 39
5.9.3. Maximum Latency Variation of the DetNet Flow 5.9.3. Maximum Latency Variation of the DetNet Flow
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.
5.9.4. Maximum Loss of the DetNet Flow 5.9.4. Maximum Loss of the DetNet Flow
MaxLoss defines the maximum Packet Loss Ratio (PLR) requirement for MaxLoss defines the maximum Packet Loss Ratio (PLR) requirement for
the DetNet flow between the Ingress and Egress(es). the DetNet flow between the Ingress and Egress(es) and the loss
measurement interval.
5.9.5. Maximum Consecutive Loss of the DetNet Flow 5.9.5. Maximum Consecutive Loss of the DetNet Flow
Some applications have 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.
5.9.6. Maximum Misordering Tolerance of the DetNet Flow 5.9.6. Maximum Misordering Tolerance of the DetNet Flow
MaxMisordering describes the tolerable maximum number of packets that MaxMisordering describes the tolerable maximum number of packets that
can be received out of order. The maximum allowed misordering can be can be received out of order. The value zero for the maximum allowed
measured for example based on sequence number. The value zero for misordering indicates that in order delivery is required, misordering
the maximum allowed misordering indicates that in order delivery is cannot be tolerated.
required, misordering cannot be tolerated.
The maximum allowed misordering can be measured for example based on
sequence number. The difference of sequence number values in
consecutive packets at the Egress cannot be bigger than
"MaxMisordering + 1".
5.10. BiDir requirement of the DetNet Flow 5.10. BiDir requirement of the DetNet Flow
DnFlowBiDir attribute defines the requirement that the flow and the DnFlowBiDir attribute defines the requirement that the flow and the
corresponding reverse direction flow must share the same path (links corresponding reverse direction flow must share the same path (links
and nodes) through the routed or switch network in the DetNet domain, and nodes) through the routed or switch network in the DetNet domain,
e.g., to provide congruent paths in the two directions that share e.g., to provide congruent paths in the two directions that share
fate and path characteristics. fate and path characteristics.
6. DetNet Service Related Parameters 6. DetNet Service Related Parameters
skipping to change at page 15, line 34 skipping to change at page 16, line 22
a. MinBandwidth(Section 6.3.1) a. MinBandwidth(Section 6.3.1)
b. MaxLatency(Section 6.3.2) b. MaxLatency(Section 6.3.2)
c. MaxLatencyVariation(Section 6.3.3) c. MaxLatencyVariation(Section 6.3.3)
d. MaxLoss(Section 6.3.4) d. MaxLoss(Section 6.3.4)
e. MaxConsecutiveLossTolerance(Section 6.3.5) e. MaxConsecutiveLossTolerance(Section 6.3.5)
f. MaxMisordering(Section 6.3.6) f. MaxMisordering(Section 6.3.6)
6.3.1. Minimum Bandwidth of the DetNet Service 6.3.1. Minimum Bandwidth of the DetNet Service
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).
6.3.2. Maximum Latency of the DetNet Service 6.3.2. Maximum Latency of the DetNet Service
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.
6.3.3. Maximum Latency Variation of the DetNet Service 6.3.3. Maximum Latency Variation of the DetNet Service
MaxLatencyVariation is the difference between the minimum and the MaxLatencyVariation is the difference between the minimum and the
skipping to change at page 16, line 24 skipping to change at page 17, line 16
MaxMisordering describes the tolerable maximum number of packets that MaxMisordering describes the tolerable maximum number of packets that
can be received out of order. The maximum allowed misordering can be can be received out of order. The maximum allowed misordering can be
measured for example based on sequence number. The value zero for measured for example based on sequence number. The value zero for
the maximum allowed misordering indicates that in order delivery is the maximum allowed misordering indicates that in order delivery is
required, misordering cannot be tolerated. required, misordering cannot be tolerated.
6.4. Connectivity Type of the DetNet Service 6.4. Connectivity Type of the DetNet Service
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 is created by a point-to-multipoint (p2mp). Connectivity type p2mp may be created by
transport layer function (e.g., p2mp LSP). (Note: mp2mp connectivity a forwarding function (e.g., p2mp LSP). (Note: from service
is a superposition of p2mp connections.) perspective mp2mp connectivity can be treated as a superposition of
p2mp connections.)
6.5. BiDir requirement of the DetNet Service 6.5. BiDir requirement of the DetNet Service
The DnServiceBiDir attribute defines the requirement that the flow The DnServiceBiDir attribute defines the requirement that the flow
and the corresponding reverse direction flow must share the same path and 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.
6.6. Rank of the DetNet Service 6.6. Rank of the DetNet Service
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. limitation scenarios. DnServiceRank value 0 is the highest priority.
6.7. Status of the DetNet Service 6.7. Status of the DetNet Service
DnServiceStatus information group includes elements that specify the DnServiceStatus information group includes elements that specify the
status of the service specific state of the DetNet domain. This status of the service specific state of the DetNet domain. This
information group informs the user whether or not the service is information group informs the user whether or not the service is
ready for use. ready for use.
The DnServiceStatus includes the following attributes: The DnServiceStatus includes the following attributes:
 End of changes. 18 change blocks. 
45 lines changed or deleted 75 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/