DetNet Control Plane Signaling
draft-trossen-detnet-control-signaling-00

Document Type Active Internet-Draft (individual)
Authors Dirk Trossen  , J├╝rgen Schmitt 
Last updated 2020-10-23
Stream (None)
Intended RFC status (None)
Formats plain text pdf htmlized (tools) htmlized 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)
DetNet Working Group                                          D. Trossen
INTERNET-DRAFT                                                    Huawei
Intended Status: Standards Track                             F.-J. Goetz
Expires: April 25, 2021                                       J. Schmitt
                                                                 Siemens
                                                        October 23, 2020

                     DetNet Control Plane Signaling
             draft-trossen-detnet-control-signaling-00.txt

Abstract

   This document provides solutions for control plane signaling, in
   accordance with the control plane framework developed in the DetNet
   WG. The solutions cover distributed, centralized, and hybrid
   signaling scenarios in the TSN and SDN domain. We propose changes to
   RSVP IntServ for a better integration with Layer 2 technologies for
   resource reservation, outlining example API specifications for the
   realization of the revised RSVP (called RSVP-detnet in the document).
       

Status of this Memo

   This Internet-Draft is submitted to IETF in full conformance with the
   provisions of BCP 78 and BCP 79.

   Internet-Drafts are working documents of the Internet Engineering
   Task Force (IETF), its areas, and its working groups.  Note that
   other groups may also distribute working documents as
   Internet-Drafts.

   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."

   The list of current Internet-Drafts can be accessed at
   http://www.ietf.org/1id-abstracts.html

   The list of Internet-Draft Shadow Directories can be accessed at
   http://www.ietf.org/shadow.html

 

Trossen, et al.          Expires April 25, 2021                 [Page 1]
INTERNET DRAFT       DetNet Control Plane Signaling                     

Copyright and License 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
   (http://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  . . . . . . . . . . . . . . . . . . . . . . . . .  3
     1.1  Terminology . . . . . . . . . . . . . . . . . . . . . . . .  3
   2  Distributed Control in Bridged TSN-based Ethernet Deployment  .  3
     2.1 Overview . . . . . . . . . . . . . . . . . . . . . . . . . .  3
     2.2 RAP Reservation in TSN vs RSVP IntServ Model . . . . . . . .  4
     2.3 Interactions between L2 and L3 . . . . . . . . . . . . . . .  5
     2.4 Similarities and Differences between RSVP and RAP  . . . . .  6
     2.5. RSVP-DetNet . . . . . . . . . . . . . . . . . . . . . . . .  8
     2.6. API Specifications  . . . . . . . . . . . . . . . . . . . .  9
   3. Centralized Control Signaling in SDN Domain . . . . . . . . . . 16
   4. Hybrid Control Signaling in SDN Domain  . . . . . . . . . . . . 16
   5. Security Considerations . . . . . . . . . . . . . . . . . . . . 16
   6. IANA Considerations . . . . . . . . . . . . . . . . . . . . . . 16
   7. Conclusion  . . . . . . . . . . . . . . . . . . . . . . . . . . 16
   8. References  . . . . . . . . . . . . . . . . . . . . . . . . . . 16
     8.1  Normative References  . . . . . . . . . . . . . . . . . . . 17
     8.2  Informative References  . . . . . . . . . . . . . . . . . . 17
   Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . . 17

 

Trossen, et al.          Expires April 25, 2021                 [Page 2]
INTERNET DRAFT       DetNet Control Plane Signaling                     

1  Introduction

   The authors in [ID.malis-detnet-controller-plane-framework-03]
   provide an overview of the DetNet control plane architecture along
   three possible classes, namely (i) fully distributed control plane
   utilizing dynamic signaling protocols, (ii) a centralized, SDN-like,
   control plane, and (iii) a hybrid control plane. We structure the
   following sections of this draft along those three classes in order
   to present example solutions for each class of the DetNet control
   plane architecture. Specifically, Section 2 will present a solution
   for a Bridged Ethernet deployment scenario. We will introduce changes
Show full document text