YANG Data Model for L3VPN Service Delivery
draft-wu-l3sm-rfc8049bis-11

Document Type Active Internet-Draft (individual in ops area)
Last updated 2017-12-14 (latest revision 2017-12-04)
Stream IETF
Intended RFC status Proposed Standard
Formats plain text xml pdf html bibtex
Yang Validation 0 errors, 0 warnings.
Reviews GENART, OPSDIR, SECDIR will not review this version
Additional URLs
- Yang catalog entry for ietf-l3vpn-svc@2017-12-04.yang
- Yang impact analysis for draft-wu-l3sm-rfc8049bis
Stream WG state (None)
Document shepherd Adrian Farrel
Shepherd write-up Show (last changed 2017-09-12)
IESG IESG state RFC Ed Queue
Consensus Boilerplate Yes
Telechat date
Responsible AD Alissa Cooper
Send notices to adrian@olddog.co.uk, aretana.ietf@gmail.com, alissa@cooperw.in
IANA IANA review state IANA OK - Actions Needed
IANA action state RFC-Ed-Ack
RFC Editor RFC Editor state EDIT
Network Working Group                                         Q. Wu, Ed.
Internet-Draft                                                    Huawei
Obsoletes: 8049 (if approved)                               S. Litkowski
Intended status: Standards Track                                  Orange
Expires: June 7, 2018                                        L. Tomotaki
                                                                 Verizon
                                                                K. Ogaki
                                                        KDDI Corporation
                                                        December 4, 2017

               YANG Data Model for L3VPN Service Delivery
                      draft-wu-l3sm-rfc8049bis-11

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.

   This document obsoletes RFC 8049 to replace the unimplementable
   module in that RFC with a new module with the same name that is not
   backward compatible.  The changes are a series of small fixes to the
   YANG module, and some clarifications to the text.

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."

Wu, et al.                Expires June 7, 2018                  [Page 1]
Internet-Draft YANG Data Model for L3VPN Service Delivery  December 2017

   This Internet-Draft will expire on June 7, 2018.

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
   (https://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  . . . . . . . . . . . . . . . . . . . . . . . .   3
     1.1.  Terminology . . . . . . . . . . . . . . . . . . . . . . .   4
     1.2.  Requirements Language . . . . . . . . . . . . . . . . . .   5
     1.3.  Tree Diagrams . . . . . . . . . . . . . . . . . . . . . .   5
     1.4.  Summary of Changes from RFC 8049  . . . . . . . . . . . .   5
       1.4.1.  Implementation Issues with RFC 8049 . . . . . . . . .   7
       1.4.2.  Impact Assessment . . . . . . . . . . . . . . . . . .   7
   2.  Acronyms  . . . . . . . . . . . . . . . . . . . . . . . . . .   8
   3.  Definitions . . . . . . . . . . . . . . . . . . . . . . . . .  10
   4.  Layer 3 IP VPN Service Model  . . . . . . . . . . . . . . . .  10
   5.  Service Data Model Usage  . . . . . . . . . . . . . . . . . .  10
   6.  Design of the Data Model  . . . . . . . . . . . . . . . . . .  12
     6.1.  Features and Augmentation . . . . . . . . . . . . . . . .  21
     6.2.  VPN Service Overview  . . . . . . . . . . . . . . . . . .  21
       6.2.1.  VPN Service Topology  . . . . . . . . . . . . . . . .  21
       6.2.2.  Cloud Access  . . . . . . . . . . . . . . . . . . . .  24
       6.2.3.  Multicast Service . . . . . . . . . . . . . . . . . .  27
       6.2.4.  Extranet VPNs . . . . . . . . . . . . . . . . . . . .  29
     6.3.  Site Overview . . . . . . . . . . . . . . . . . . . . . .  30
       6.3.1.  Devices and Locations . . . . . . . . . . . . . . . .  32
       6.3.2.  Site Network Accesses . . . . . . . . . . . . . . . .  32
     6.4.  Site Role . . . . . . . . . . . . . . . . . . . . . . . .  35
Show full document text