YANG Data Model for L3VPN service delivery
draft-ietf-l3sm-l3vpn-service-model-08

The information below is for an old version of the document
Document Type Active Internet-Draft (l3sm WG)
Last updated 2016-06-09
Replaces draft-ltsd-l3sm-l3vpn-service-model
Stream IETF
Intended RFC status (None)
Formats plain text pdf html bibtex
Reviews
Stream WG state WG Document
Document shepherd No shepherd assigned
IESG IESG state I-D Exists
Consensus Boilerplate Unknown
Telechat date
Responsible AD (None)
Send notices to (None)
L3SM Working Group                                          S. Litkowski
Internet-Draft                                  Orange Business Services
Intended status: Standards Track                               R. Shakir
Expires: December 11, 2016                           Jive Communications
                                                             L. Tomotaki
                                                                 Verizon
                                                                K. Ogaki
                                                                    KDDI
                                                              K. D'Souza
                                                                     ATT
                                                           June 09, 2016

               YANG Data Model for L3VPN service delivery
                 draft-ietf-l3sm-l3vpn-service-model-08

Abstract

   This document defines a YANG data model that can be used to deliver a
   Layer 3 Provider Provisioned VPN service.  The document is limited to
   the BGP PE-based VPNs as described in RFC4110 and RFC4364.  This
   model is intended to be instantiated at management system to deliver
   the overall service.  This model is not a configuration model to be
   used directly on network elements.  This model provides an abstracted
   view of the Layer 3 IPVPN service configuration components.  It will
   be up to a management system to take this as an input and use
   specific configurations models to configure the different network
   elements to deliver the service.  How configuration of network
   elements is done is out of scope of the document.

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 [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

Litkowski, et al.       Expires December 11, 2016               [Page 1]
Internet-Draft                l3vpn-svc-cfg                    June 2016

   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 December 11, 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  . . . . . . . . . . . . . . . . . . . . . . . .   4
     1.1.  Terminology . . . . . . . . . . . . . . . . . . . . . . .   4
     1.2.  Tree diagram  . . . . . . . . . . . . . . . . . . . . . .   4
   2.  Definitions . . . . . . . . . . . . . . . . . . . . . . . . .   5
   3.  Layer 3 IP VPN service model  . . . . . . . . . . . . . . . .   5
   4.  Service data model usage  . . . . . . . . . . . . . . . . . .   6
   5.  Design of the Data Model  . . . . . . . . . . . . . . . . . .   7
     5.1.  VPN service overview  . . . . . . . . . . . . . . . . . .  20
       5.1.1.  VPN service topology  . . . . . . . . . . . . . . . .  20
         5.1.1.1.  Route Target allocation . . . . . . . . . . . . .  20
         5.1.1.2.  Any to any  . . . . . . . . . . . . . . . . . . .  21
         5.1.1.3.  Hub and Spoke . . . . . . . . . . . . . . . . . .  22
         5.1.1.4.  Hub and Spoke disjoint  . . . . . . . . . . . . .  23
       5.1.2.  Cloud access  . . . . . . . . . . . . . . . . . . . .  23
       5.1.3.  Multicast service . . . . . . . . . . . . . . . . . .  26
       5.1.4.  Extranet VPNs . . . . . . . . . . . . . . . . . . . .  27
     5.2.  Site overview . . . . . . . . . . . . . . . . . . . . . .  28
       5.2.1.  Site network accesses . . . . . . . . . . . . . . . .  30
         5.2.1.1.  Bearer  . . . . . . . . . . . . . . . . . . . . .  30
         5.2.1.2.  Connection  . . . . . . . . . . . . . . . . . . .  30
         5.2.1.3.  Inheritance of parameters between site and site-
Show full document text