A Layer 2 VPN Network Yang Model
draft-barguil-opsawg-l2sm-l2nm-00

Document Type Active Internet-Draft (individual)
Last updated 2019-12-05
Stream (None)
Intended RFC status (None)
Formats plain text pdf htmlized bibtex
Yang Validation 0 errors, 0 warnings.
Additional URLs
- Yang catalog entry for ietf-l2vpn-ntw@2019-12-05.yang
- Yang impact analysis for draft-barguil-opsawg-l2sm-l2nm
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)
Internet Engineering Task Force                          S. Barguil, Ed.
Internet-Draft                                  O. Gonzalez de Dios, Ed.
Intended status: Standards Track                                V. Lopez
Expires: June 7, 2020                                         Telefonica
                                                                L. Munoz
                                                                Vodafone
                                                                L. Jalil
                                                                 Verizon
                                                        December 5, 2019

                    A Layer 2 VPN Network Yang Model
                   draft-barguil-opsawg-l2sm-l2nm-00

Abstract

   This document defines a Yang Data model, L2NM, that can be used to
   manage the provisioning of Layer 2 VPN services in a Service Provider
   Network.  The Yang module defined in this document provides
   representation of the Layer 2 VPN Service and is aimed at being used
   by a Network Controller, which can derive from it the configuration
   information that will be sent to the network devices, as well the the
   underlay transport network in a service provider environment.

   RFC 8466 defines a Layer 2 VPN service model (L2SM) that can be used
   in the communication between a Customer and the Network Operator.This
   document complements L2SM by creating a network-centric view of the
   service to be used in the communication between the entity that
   interacts directly with the customer, the service orchestrator,
   (either fully automated or a human operator) and the entity in charge
   of network orchestration and control (a.k.a., network controller/
   orchestrator).

   The YANG data model defined in this document conforms to the Network
   Management Datastore Architecture defined in RFC 8342.

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

Barguil, et al.           Expires June 7, 2020                  [Page 1]
Internet-Draft                    L2NM                     December 2019

   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 June 7, 2020.

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  . . . . . . . . . . . . . . . . . . . . . . . .   3
     1.1.  Terminology . . . . . . . . . . . . . . . . . . . . . . .   3
     1.2.  Requirements Language . . . . . . . . . . . . . . . . . .   4
   2.  Reference architecture  . . . . . . . . . . . . . . . . . . .   4
   3.  Description of the L2NM YANG Module . . . . . . . . . . . . .   8
     3.1.  Structure of the Module . . . . . . . . . . . . . . . . .   9
     3.2.  L2 VPN Service  . . . . . . . . . . . . . . . . . . . . .   9
       3.2.1.  L2 VPN Service Types  . . . . . . . . . . . . . . . .  10
       3.2.2.  Underlying Transport Selection  . . . . . . . . . . .  10
       3.2.3.  Other relevant Network Parameters . . . . . . . . . .  11
     3.3.  L2NM Module Tree  . . . . . . . . . . . . . . . . . . . .  12
   4.  Relation with other Yang Models . . . . . . . . . . . . . . .  19
     4.1.  Relation with L2SM  . . . . . . . . . . . . . . . . . . .  20
     4.2.  Relation with Network Topology  . . . . . . . . . . . . .  20
     4.3.  Relation with Device Models . . . . . . . . . . . . . . .  20
   5.  Yang Module . . . . . . . . . . . . . . . . . . . . . . . . .  20
   6.  Acknowledgements  . . . . . . . . . . . . . . . . . . . . . . 104
   7.  Contributors  . . . . . . . . . . . . . . . . . . . . . . . . 104
   8.  IANA Considerations . . . . . . . . . . . . . . . . . . . . . 104
   9.  Security Considerations . . . . . . . . . . . . . . . . . . . 104
   10. References  . . . . . . . . . . . . . . . . . . . . . . . . . 105
Show full document text