DetNet Control Plane Framework
draft-geng-detnet-control-plane-00

Document Type Active Internet-Draft (individual)
Last updated 2019-07-04
Stream (None)
Intended RFC status (None)
Formats plain text xml pdf html bibtex
Stream Stream state (No stream defined)
Consensus Boilerplate Unknown
RFC Editor Note (None)
IESG IESG state I-D Exists
Telechat date
Responsible AD (None)
Send notices to (None)
Network Working Group                                            X. Geng
Internet-Draft                                                   M. Chen
Intended status: Experimental                                     Huawei
Expires: January 5, 2020                                          F. Qin
                                                            China Mobile
                                                           July 04, 2019

                     DetNet Control Plane Framework
                   draft-geng-detnet-control-plane-00

Abstract

   This document defines DetNet control plane framework.  It specifies
   the guidance of DetNet control plane implementation.

Requirements Language

   The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
   "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this
   document are to be interpreted as described in RFC 2119 [RFC2119].

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 January 5, 2020.

Copyright Notice

   Copyright (c) 2019 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

Geng, et al.             Expires January 5, 2020                [Page 1]
Internet-Draft              Abbreviated-Title                  July 2019

   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
   2.  Terminologies . . . . . . . . . . . . . . . . . . . . . . . .   3
   3.  DetNet Control Plane Classification . . . . . . . . . . . . .   3
     3.1.  Fully Distributed Control Plane . . . . . . . . . . . . .   3
     3.2.  Fully Centralized Control Plane . . . . . . . . . . . . .   3
     3.3.  Hybrid Control Plane  . . . . . . . . . . . . . . . . . .   4
   4.  DetNet Control Plane Considerations . . . . . . . . . . . . .   5
     4.1.  Explicit Route  . . . . . . . . . . . . . . . . . . . . .   5
     4.2.  Resource Reservation  . . . . . . . . . . . . . . . . . .   6
     4.3.  Seamless Redundancy . . . . . . . . . . . . . . . . . . .   6
   5.  IANA Considerations . . . . . . . . . . . . . . . . . . . . .   7
   6.  Security Considerations . . . . . . . . . . . . . . . . . . .   7
   7.  Acknowledgements  . . . . . . . . . . . . . . . . . . . . . .   7
   8.  Normative References  . . . . . . . . . . . . . . . . . . . .   7
   Authors' Addresses  . . . . . . . . . . . . . . . . . . . . . . .   8

1.  Introduction

   Deterministic Networking (DetNet) provides the capability to carry
   specified unicast or multicast data flows for real-time applications
   with extremely low data loss rates and bounded latency within a
   network domain.  As discussed in the Deterministic Networking
   Architecture[I-D.ietf-detnet-architecture], Techniques used to
   provide this capability include reserving data plane resources for
   individual (or aggregated) DetNet flows in some or all of the
   intermediate nodes along the path of the flow, providing explicit
   routes for DetNet flows, and distributing data from DetNet flow
   packets over time and/or space to ensure delivery of each packet's
   data in spite of the loss of a path.

   All these DetNet specific technologies need support of protocal from
   both data plane and control plane.

   DetNet data plane framework is defined in
   [I-D.ietf-detnet-data-plane-framework].  This document defines DetNet
   control plane framework.  It specifies the guidance of DetNet control
   plane implementation.

Geng, et al.             Expires January 5, 2020                [Page 2]
Internet-Draft              Abbreviated-Title                  July 2019

2.  Terminologies

   The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
   "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this
   document are to be interpreted as described in [RFC2119].
Show full document text