YANG Data Model for Composite VPN Service Delivery
draft-chen-opsawg-composite-vpn-dm-00

Document Type Active Internet-Draft (individual)
Last updated 2016-10-27
Stream (None)
Intended RFC status (None)
Formats plain text 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)
OPSA Working Group                                               R. Chen
Internet-Draft                                                  L. Zhang
Intended status: Standards Track                                 H. Deng
Expires: April 27, 2017                              Huawei Technologies
                                                                 L. Geng
                                                            China Mobile
                                                                  C. Xie
                                                           China Telecom
                                                        October 24, 2016

           YANG Data Model for Composite VPN Service Delivery
                 draft-chen-opsawg-composite-vpn-dm-00

Abstract

   The operator facing data model is valuable to reduce the operations
   and management.  This document describes the YANG data model of the
   composite VPN for operators to provision, optimize, monitor and
   diagnose the end to end PE-based VPN services across multiple
   autonomous systems (ASes).  The model from this document are limited
   to multiple ASes within one service provider.

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 http://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 April 27, 2017.

Chen, et al.             Expires April 27, 2017                 [Page 1]
Internet-Draft    Composite VPN Service Delivery Model      October 2016

Copyright Notice

   Copyright (c) 2016 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  . . . . . . . . . . . . . . . . . . . . . . . .   2
   2.  Definitions . . . . . . . . . . . . . . . . . . . . . . . . .   3
   3.  Use Cases and Usage . . . . . . . . . . . . . . . . . . . . .   4
   4.  Data Model Design Requirements  . . . . . . . . . . . . . . .   5
   5.  Design of the Data Model  . . . . . . . . . . . . . . . . . .   7
     5.1.  Composite VPN . . . . . . . . . . . . . . . . . . . . . .   7
     5.2.  Access Point  . . . . . . . . . . . . . . . . . . . . . .   8
       5.2.1.  Termination Point Basic Information . . . . . . . . .  10
       5.2.2.  QoS . . . . . . . . . . . . . . . . . . . . . . . . .  10
       5.2.3.  Routing Protocol  . . . . . . . . . . . . . . . . . .  11
     5.3.  Segmental VPN . . . . . . . . . . . . . . . . . . . . . .  11
   6.  YANG Module . . . . . . . . . . . . . . . . . . . . . . . . .  11
   7.  IANA Considerations . . . . . . . . . . . . . . . . . . . . .  45
   8.  Security Considerations . . . . . . . . . . . . . . . . . . .  45
   9.  Acknowledgements  . . . . . . . . . . . . . . . . . . . . . .  45
   10. References  . . . . . . . . . . . . . . . . . . . . . . . . .  46
     10.1.  Normative References . . . . . . . . . . . . . . . . . .  46
     10.2.  Informative References . . . . . . . . . . . . . . . . .  46
   Authors' Addresses  . . . . . . . . . . . . . . . . . . . . . . .  46

1.  Introduction

   Internet Service Providers (ISPs) have significant interest on
   providing Provider Edge (PE) based virtual private network (VPN)
   services, in which the tunnel endpoints are the PE devices.  In this
   case, the Customer Edge (CE) devices do not need to have any special
   VPN capabilities.  Customers can reduce support costs by outsourcing
Show full document text