Hierarchy of IP Controllers (HIC)
draft-li-teas-hierarchy-ip-controllers-01

Document Type Active Internet-Draft (individual)
Last updated 2018-09-03
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)
TEAS Working Group                                                 Z. Li
Internet-Draft                                                  D. Dhody
Intended status: Informational                                   H. Chen
Expires: March 7, 2019                               Huawei Technologies
                                                       September 3, 2018

                   Hierarchy of IP Controllers (HIC)
               draft-li-teas-hierarchy-ip-controllers-01

Abstract

   This document describes the interactions between various IP
   controllers in a hierarchical fashion to provide various IP services.
   It describes how the Abstraction and Control of Traffic Engineered
   Networks (ACTN) framework is applied to the Hierarchy of IP
   controllers (HIC) as well as document the interactions with other
   protocols like BGP, Path Computation Element Communication Protocol
   (PCEP) to provide end to end dynamic services spanning multiple
   domains and controllers (e.g.  Layer 3 Virtual Private Network
   (L3VPN), Seamless MPLS etc).

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 March 7, 2019.

Copyright Notice

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

Li, et al.                Expires March 7, 2019                 [Page 1]
Internet-Draft                     HIC                    September 2018

   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.  Overview  . . . . . . . . . . . . . . . . . . . . . . . . . .   4
     2.1.  Mapping to ACTN . . . . . . . . . . . . . . . . . . . . .   4
     2.2.  Interface between Super Controller and Domain Controller
           in HIC  . . . . . . . . . . . . . . . . . . . . . . . . .   5
   3.  Key Concepts  . . . . . . . . . . . . . . . . . . . . . . . .   6
     3.1.  Topology  . . . . . . . . . . . . . . . . . . . . . . . .   6
     3.2.  Path Computation/Path instantiation . . . . . . . . . . .   7
     3.3.  BGP considerations  . . . . . . . . . . . . . . . . . . .   8
   4.  VPN Service . . . . . . . . . . . . . . . . . . . . . . . . .   8
     4.1.  Seamless MPLS . . . . . . . . . . . . . . . . . . . . . .   8
     4.2.  L3VPN . . . . . . . . . . . . . . . . . . . . . . . . . .  10
     4.3.  L2VPN and EVPN service  . . . . . . . . . . . . . . . . .  11
   5.  Possible Features/Extensions  . . . . . . . . . . . . . . . .  11
   6.  Other Considerations  . . . . . . . . . . . . . . . . . . . .  12
     6.1.  Control Plane . . . . . . . . . . . . . . . . . . . . . .  12
       6.1.1.  PCE / PCEP  . . . . . . . . . . . . . . . . . . . . .  12
       6.1.2.  BGP . . . . . . . . . . . . . . . . . . . . . . . . .  13
     6.2.  Management Plane  . . . . . . . . . . . . . . . . . . . .  15
       6.2.1.  YANG Models . . . . . . . . . . . . . . . . . . . . .  15
       6.2.2.  Protocol Considerations . . . . . . . . . . . . . . .  16
   7.  IANA Considerations . . . . . . . . . . . . . . . . . . . . .  16
   8.  Security Considerations . . . . . . . . . . . . . . . . . . .  16
   9.  Acknowledgments . . . . . . . . . . . . . . . . . . . . . . .  16
   10. Contributing Authors  . . . . . . . . . . . . . . . . . . . .  16
   11. References  . . . . . . . . . . . . . . . . . . . . . . . . .  17
     11.1.  Normative References . . . . . . . . . . . . . . . . . .  17
     11.2.  Informative References . . . . . . . . . . . . . . . . .  17
   Authors' Addresses  . . . . . . . . . . . . . . . . . . . . . . .  22

1.  Introduction

   Software-Defined Networking (SDN) refers to a separation between the
   control elements and the forwarding components so that software
   running in a centralized system called a controller, can act to
   program the devices in the network to behave in specific ways.  A
Show full document text