Deterministic Networking (DetNet) Data Plane Framework
RFC 8938

• Status
• IESG evaluation record
• IESG writeups
• Email expansions
• History

• Versions
• 00
• 01
• 02
• 03
• 04
• 05
• 06



Internet Engineering Task Force (IETF)                     B. Varga, Ed.
Request for Comments: 8938                                     J. Farkas
Category: Informational                                         Ericsson
ISSN: 2070-1721                                                L. Berger
                                                 LabN Consulting, L.L.C.
                                                                A. Malis
                                                        Malis Consulting
                                                               S. Bryant
                                                  Futurewei Technologies
                                                           November 2020

         Deterministic Networking (DetNet) Data Plane Framework

Abstract

   This document provides an overall framework for the Deterministic
   Networking (DetNet) data plane.  It covers concepts and
   considerations that are generally common to any DetNet data plane
   specification.  It describes related Controller Plane considerations
   as well.

Status of This Memo

   This document is not an Internet Standards Track specification; it is
   published for informational purposes.

   This document is a product of the Internet Engineering Task Force
   (IETF).  It represents the consensus of the IETF community.  It has
   received public review and has been approved for publication by the
   Internet Engineering Steering Group (IESG).  Not all documents
   approved by the IESG are candidates for any level of Internet
   Standard; see Section 2 of RFC 7841.

   Information about the current status of this document, any errata,
   and how to provide feedback on it may be obtained at
   https://www.rfc-editor.org/info/rfc8938.

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
   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
   2.  Terminology
     2.1.  Terms Used in This Document
     2.2.  Abbreviations
   3.  Overview of the DetNet Data Plane
     3.1.  Data Plane Characteristics
       3.1.1.  Data Plane Technology
       3.1.2.  Encapsulation
     3.2.  DetNet-Specific Metadata
     3.3.  DetNet IP Data Plane
     3.4.  DetNet MPLS Data Plane
     3.5.  Further DetNet Data Plane Considerations
       3.5.1.  Functions Provided on a Per-Flow Basis
       3.5.2.  Service Protection
       3.5.3.  Aggregation Considerations
       3.5.4.  End-System-Specific Considerations
       3.5.5.  Sub-network Considerations
   4.  Controller Plane (Management and Control) Considerations
     4.1.  DetNet Controller Plane Requirements
     4.2.  Generic Controller Plane Considerations
       4.2.1.  Flow Aggregation Control
       4.2.2.  Explicit Routes
       4.2.3.  Contention Loss and Jitter Reduction
       4.2.4.  Bidirectional Traffic
     4.3.  Packet Replication, Elimination, and Ordering Functions
           (PREOF)
   5.  Security Considerations
   6.  IANA Considerations
   7.  References
     7.1.  Normative References
     7.2.  Informative References
   Acknowledgements
   Contributors
   Authors' Addresses

1.  Introduction

   DetNet (Deterministic Networking) provides the ability to carry
   specified unicast or multicast data flows for real-time applications
   with extremely low packet loss rates and assured maximum end-to-end
   delivery latency.  A description of the general background and
   concepts of DetNet can be found in [RFC8655].

   This document describes the concepts needed by any DetNet data plane
   specification (i.e., the DetNet-specific use of packet header fields)
   and provides considerations for any corresponding implementation.  It
   covers the building blocks that provide the DetNet service, the
   DetNet service sub-layer, and the DetNet forwarding sub-layer
   functions as described in the DetNet architecture [RFC8655].

   The DetNet architecture models the DetNet-related data plane
   functions as being decomposed into two sub-layers: a service
   sub-layer and a forwarding sub-layer.  The service sub-layer is used
   to provide DetNet service protection and reordering.  The forwarding
   sub-layer leverages traffic engineering mechanisms and provides
   congestion protection (low loss, assured latency, and limited out-of-
   order delivery).  A particular forwarding sub-layer may have
   capabilities that are not available on other forwarding sub-layers.