Deterministic Networking (DetNet) Controller Plane Framework
draft-malis-detnet-controller-plane-framework-02

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

• Versions
• 00
• 01
• 02

Network Working Group                                           A. Malis
Internet-Draft                                               Independent
Intended status: Informational                                   X. Geng
Expires: January 25, 2020                                        M. Chen
                                                                  Huawei
                                                                  F. Qin
                                                            China Mobile
                                                           July 24, 2019

      Deterministic Networking (DetNet) Controller Plane Framework
            draft-malis-detnet-controller-plane-framework-02

Abstract

   This document provides a framework overview for the Deterministic
   Networking (DetNet) controller plane.  It discusses concepts and
   requirements that will be basis for Detnet controller plane solution
   documents.

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 25, 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
   carefully, as they describe your rights and restrictions with respect
   to this document.  Code Components extracted from this document must

Malis, et al.           Expires January 25, 2020                [Page 1]
Internet-Draft           DetNet Controller Plane               July 2019

   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
     1.1.  Terminology . . . . . . . . . . . . . . . . . . . . . . .   3
   2.  DetNet Controller Plane Requirements  . . . . . . . . . . . .   4
   3.  DetNet Control Plane Architecture . . . . . . . . . . . . . .   5
     3.1.  Distributed Control Plane and Signaling Protocols . . . .   5
     3.2.  SDN/Fully Centralized Control Plane . . . . . . . . . . .   6
     3.3.  Hybrid Control Plane  . . . . . . . . . . . . . . . . . .   7
   4.  DetNet Control Plane Additional Details and Issues  . . . . .   8
     4.1.  Explicit Paths  . . . . . . . . . . . . . . . . . . . . .   8
     4.2.  Resource Reservation  . . . . . . . . . . . . . . . . . .   8
     4.3.  PREOF Support . . . . . . . . . . . . . . . . . . . . . .   9
     4.4.  DetNet in a Traditional MPLS Domain . . . . . . . . . . .   9
     4.5.  IP  . . . . . . . . . . . . . . . . . . . . . . . . . . .  10
     4.6.  DetNet with Segment Routing (SR)  . . . . . . . . . . . .  10
   5.  Management Plane Overview . . . . . . . . . . . . . . . . . .  12
     5.1.  Provisioning  . . . . . . . . . . . . . . . . . . . . . .  12
     5.2.  DetNet Operations, Administration and Maintenance (OAM) .  12
       5.2.1.  OAM for Performance Monitoring (PM) . . . . . . . . .  12
       5.2.2.  OAM for Fault/Defect Management (FM)  . . . . . . . .  13
   6.  IANA Considerations . . . . . . . . . . . . . . . . . . . . .  13
   7.  Security Considerations . . . . . . . . . . . . . . . . . . .  13
   8.  Acknowledgments . . . . . . . . . . . . . . . . . . . . . . .  13
   9.  References  . . . . . . . . . . . . . . . . . . . . . . . . .  13
     9.1.  Normative References  . . . . . . . . . . . . . . . . . .  14
     9.2.  Informative References  . . . . . . . . . . . . . . . . .  15
   Authors' Addresses  . . . . . . . . . . . . . . . . . . . . . . .  19

1.  Introduction

   Deterministic Networking (DetNet) provides the capability to carry
   specified unicast and/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 that do not immediately change with