YANG Data Model for Composed VPN Service Delivery
draft-evenwu-opsawg-yang-composed-vpn-03

Document Type Active Internet-Draft (individual)
Last updated 2019-03-08
Stream (None)
Intended RFC status (None)
Formats plain text xml pdf html bibtex
Yang Validation 0 errors, 0 warnings.
Additional URLs
- Yang catalog entry for ietf-composed-vpn-svc@2018-08-21.yang
- Yang catalog entry for ietf-segment-vpn@2019-01-30.yang
- Yang impact analysis for draft-evenwu-opsawg-yang-composed-vpn
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)
OPSAWG Working Group                                             R. Even
Internet-Draft                                                     B. Wu
Intended status: Standards Track                                   Q. Wu
Expires: September 9, 2019                                        Huawei
                                                                Y. Cheng
                                                            China Unicom
                                                           March 8, 2019

           YANG Data Model for Composed VPN Service Delivery
                draft-evenwu-opsawg-yang-composed-vpn-03

Abstract

   This document defines a YANG data model that can be used by a network
   operator to configure a VPN service that spans multiple
   administrative domains and that is constructed from component VPNs in
   each of those administrative domains.  The component VPNs may be
   L2VPN or L3VPN or a mixture of the two.  This model is intended to be
   instantiated at the management system to deliver the end to end
   service (i.e., performing service provision and activation functions
   at different levels through a unified interface).

   The model is not a configuration model to be used directly on network
   elements.  This model provides an abstracted common view of VPN
   service configuration components segmented at different layer and
   administrative domain.  It is up to a management system to take this
   as an input and generate specific configurations models to configure
   the different network elements within each administrative domain to
   deliver the service.  How configuration of network elements is done
   is out of scope of the document.

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

   This Internet-Draft will expire on September 9, 2019.

Even, et al.            Expires September 9, 2019               [Page 1]
Internet-Draft           Composed VPN YANG Model              March 2019

Copyright Notice

   Copyright (c) 2019 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  . . . . . . . . . . . . . . . . . . . . . . . .   2
     1.1.  Terminology . . . . . . . . . . . . . . . . . . . . . . .   3
       1.1.1.  Requirements Language . . . . . . . . . . . . . . . .   4
     1.2.  Tree diagram  . . . . . . . . . . . . . . . . . . . . . .   4
   2.  Definitions . . . . . . . . . . . . . . . . . . . . . . . . .   4
   3.  Service Model Usage . . . . . . . . . . . . . . . . . . . . .   6
   4.  The Composed VPN Service Model  . . . . . . . . . . . . . . .   7
     4.1.  VPN Service Types . . . . . . . . . . . . . . . . . . . .   7
     4.2.  Composed VPN Physical Network Topology  . . . . . . . . .   7
   5.  Design of the Data Model  . . . . . . . . . . . . . . . . . .   9
     5.1.  VPN Hierarchy . . . . . . . . . . . . . . . . . . . . . .  15
     5.2.  Access Point(AP)  . . . . . . . . . . . . . . . . . . . .  16
       5.2.1.  AP peering with CE  . . . . . . . . . . . . . . . . .  16
       5.2.2.  AP peering for inter-domains connection . . . . . . .  17
   6.  Composed VPN YANG Module  . . . . . . . . . . . . . . . . . .  19
   7.  Segment VPN YANG Module . . . . . . . . . . . . . . . . . . .  21
   8.  Service Model Usage Example . . . . . . . . . . . . . . . . .  53
   9.  Interaction with other YANG models  . . . . . . . . . . . . .  56
   10. Security Considerations . . . . . . . . . . . . . . . . . . .  57
   11. IANA Considerations . . . . . . . . . . . . . . . . . . . . .  58
   12. References  . . . . . . . . . . . . . . . . . . . . . . . . .  58
     12.1.  Normative References . . . . . . . . . . . . . . . . . .  58
     12.2.  Informative References . . . . . . . . . . . . . . . . .  60
   Appendix A.  Acknowledges . . . . . . . . . . . . . . . . . . . .  60
Show full document text