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

The information below is for an old version of the document
Document Type Active Internet-Draft (l3sm WG)
Last updated 2016-10-27 (latest revision 2016-10-25)
Replaces draft-ltsd-l3sm-l3vpn-service-model
Stream IETF
Intended RFC status Proposed Standard
Formats plain text pdf html bibtex
Reviews
Stream WG state Submitted to IESG for Publication
Document shepherd Qin Wu
Shepherd write-up Show (last changed 2016-09-22)
IESG IESG state IESG Evaluation::AD Followup
Consensus Boilerplate Yes
Telechat date
Needs a YES. Needs 4 more YES or NO OBJECTION positions to pass.
Responsible AD BenoƮt Claise
Send notices to "Qin Wu" <bill.wu@huawei.com>
IANA IANA review state IANA - Not OK
IANA action state None
L3SM Working Group                                          S. Litkowski
Internet-Draft                                  Orange Business Services
Intended status: Standards Track                             L. Tomotaki
Expires: April 28, 2017                                          Verizon
                                                                K. Ogaki
                                                                    KDDI
                                                        October 25, 2016

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

Abstract

   This document defines a YANG data model that can be used for
   communication between customers and network operators and to deliver
   a Layer 3 Provider Provisioned VPN service.  The document is limited
   to the BGP PE-based VPNs as described in [RFC4026], [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
   time.  It is inappropriate to use Internet-Drafts as reference
   material or to cite them other than as "work in progress."

Litkowski, et al.        Expires April 28, 2017                 [Page 1]
Internet-Draft                l3vpn-svc-cfg                 October 2016

   This Internet-Draft will expire on April 28, 2017.

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  . . . . . . . . . . . . . . . . . . . . . .   5
   2.  Definitions . . . . . . . . . . . . . . . . . . . . . . . . .   5
   3.  Layer 3 IP VPN service model  . . . . . . . . . . . . . . . .   6
   4.  Service data model usage  . . . . . . . . . . . . . . . . . .   6
   5.  Design of the Data Model  . . . . . . . . . . . . . . . . . .   7
     5.1.  Features and augmentation . . . . . . . . . . . . . . . .  15
     5.2.  VPN service overview  . . . . . . . . . . . . . . . . . .  16
       5.2.1.  VPN service topology  . . . . . . . . . . . . . . . .  16
         5.2.1.1.  Route Target allocation . . . . . . . . . . . . .  16
         5.2.1.2.  Any to any  . . . . . . . . . . . . . . . . . . .  17
         5.2.1.3.  Hub and Spoke . . . . . . . . . . . . . . . . . .  18
         5.2.1.4.  Hub and Spoke disjoint  . . . . . . . . . . . . .  19
       5.2.2.  Cloud access  . . . . . . . . . . . . . . . . . . . .  19
       5.2.3.  Multicast service . . . . . . . . . . . . . . . . . .  21
       5.2.4.  Extranet VPNs . . . . . . . . . . . . . . . . . . . .  23
     5.3.  Site overview . . . . . . . . . . . . . . . . . . . . . .  24
       5.3.1.  Devices and locations . . . . . . . . . . . . . . . .  25
       5.3.2.  Site network accesses . . . . . . . . . . . . . . . .  26
         5.3.2.1.  Bearer  . . . . . . . . . . . . . . . . . . . . .  27
         5.3.2.2.  Connection  . . . . . . . . . . . . . . . . . . .  27
         5.3.2.3.  Inheritance of parameters between site and site-
                   network-access  . . . . . . . . . . . . . . . . .  28
Show full document text