YANG Data Model for L3VPN Service Delivery
RFC 8049

• Status
• IESG evaluation record
• IESG writeups
• Email expansions
• History

• Versions
• 00
• 01
• 02
• 03
• 04
• 05
• 06
• 07
• 08
• 09
• 10
• 11
• 12
• 13
• 14
• 15
• 16
• 17
• 18
• 19

draft-ietf-l3sm-l3vpn-service-model-19.txt:
xym 0.4:
Extracting 'ietf-l3vpn-svc@2016-11-04.yang'
   Removed 20 empty lines


ietf-l3vpn-svc@2016-11-03.yang:
pyang 1.7.3: pyang --verbose --ietf -p {libs} {model}:
No validation errors

yanglint 0.14.53: yanglint --verbose -p {rfclib} -p {draftlib} -p {tmplib} {model} -i:
No validation errors

Internet Engineering Task Force (IETF)                      S. Litkowski
Request for Comments: 8049                      Orange Business Services
Category: Standards Track                                    L. Tomotaki
ISSN: 2070-1721                                                  Verizon
                                                                K. Ogaki
                                                        KDDI Corporation
                                                           February 2017

               YANG Data Model for L3VPN Service Delivery

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.  This document is limited
   to BGP PE-based VPNs as described in RFCs 4026, 4110, and 4364.  This
   model is intended to be instantiated at the management system to
   deliver the overall service.  It is not a configuration model to be
   used directly on network elements.  This model provides an abstracted
   view of the Layer 3 IP VPN service configuration components.  It will
   be up to the management system to take this model as input and use
   specific configuration models to configure the different network
   elements to deliver the service.  How the configuration of network
   elements is done is out of scope for this document.

Status of This Memo

   This is an Internet Standards Track document.

   This document is a product of the Internet Engineering Task Force
   (IETF).  It represents the consensus of the IETF community.  It has
   received public review and has been approved for publication by the
   Internet Engineering Steering Group (IESG).  Further information on
   Internet Standards is available in Section 2 of RFC 7841.

   Information about the current status of this document, any errata,
   and how to provide feedback on it may be obtained at
   http://www.rfc-editor.org/info/rfc8049.

Litkowski, et al.            Standards Track                    [Page 1]
RFC 8049       YANG Data Model for L3VPN Service Delivery  February 2017

Copyright Notice

   Copyright (c) 2017 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. Requirements Language ......................................5
      1.3. Tree Diagrams ..............................................5
   2. Acronyms ........................................................5
   3. Definitions .....................................................7
   4. Layer 3 IP VPN Service Model ....................................8
   5. Service Data Model Usage ........................................9
   6. Design of the Data Model .......................................10
      6.1. Features and Augmentation .................................18
      6.2. VPN Service Overview ......................................18
           6.2.1. VPN Service Topology ...............................18
                  6.2.1.1. Route Target Allocation ...................19
                  6.2.1.2. Any-to-Any ................................20
                  6.2.1.3. Hub and Spoke .............................20
                  6.2.1.4. Hub and Spoke Disjoint ....................21
           6.2.2. Cloud Access .......................................22
           6.2.3. Multicast Service ..................................24
           6.2.4. Extranet VPNs ......................................26
      6.3. Site Overview .............................................27
           6.3.1. Devices and Locations ..............................29
           6.3.2. Site Network Accesses ..............................30
                  6.3.2.1. Bearer ....................................30
                  6.3.2.2. Connection ................................31
                  6.3.2.3. Inheritance of Parameters Defined at
                           Site Level and Site Network Access Level ..32
      6.4. Site Role .................................................32

Litkowski, et al.            Standards Track                    [Page 2]
RFC 8049       YANG Data Model for L3VPN Service Delivery  February 2017

      6.5. Site Belonging to Multiple VPNs ...........................33