A Layer 3 VPN Network YANG Model
draft-ietf-opsawg-l3sm-l3nm-01
Document Type Active Internet-Draft (opsawg WG)
Last updated 2019-11-17
Replaces draft-aguado-opsawg-l3sm-l3nm
Stream IETF
Intended RFC status (None)
Formats plain text pdf htmlized bibtex
Yang Validation ☯ 0 errors, 0 warnings.
Additional URLs
- Yang catalog entry for ietf-l3vpn-ntw@2019-11-17.yang
- Yang impact analysis for draft-ietf-opsawg-l3sm-l3nm
- Mailing list discussion
Stream WG state WG Document
On Agenda opsawg at IETF-106
Document shepherd No shepherd assigned
IESG IESG state I-D Exists
Consensus Boilerplate Unknown
Telechat date
Responsible AD (None)
Send notices to (None)
Email authors Email WG IPR References Referenced by Nits 
OPSAWG                                                         A. Aguado
Internet-Draft                                                     Nokia
Intended status: Standards Track                O. Gonzalez de Dios, Ed.
Expires: May 20, 2020                                           V. Lopez
                                                              Telefonica
                                                                D. Voyer
                                                             Bell Canada
                                                                L. Munoz
                                                                Vodafone
                                                       November 17, 2019

                    A Layer 3 VPN Network YANG Model
                     draft-ietf-opsawg-l3sm-l3nm-01

Abstract

   RFC8299 defines a L3VPN Service YANG data Model (L3SM) that can be
   used for communication between customers and VPN service providers.
   That data model plays the role of a Customer Service Model, according
   to the terminology defined in RFC8309, and is as such adequate for
   service negotiation and order handling matters.

   There is a need for a more network-centric YANG data model 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).

   This document specifies a L3VPN Network YANG Model (L3NM) to
   facilitate communication between a service orchestrator and a network
   controller/orchestrator.  Such data model provides a network-centric
   view of the L3VPN services.  The Yang model proposed is limited to
   BGP PE-based VPNs as described in RFCs 4026, 4110, and 4364.

Editorial Note (To be removed by RFC Editor)

   Please update these statements within the document with the RFC
   number to be assigned to this document:

   o  "This version of this YANG module is part of RFC XXXX;"

   o  "RFC XXXX: Layer 3 VPN Network Model";

   o  reference: RFC XXXX

   Also, please update the "revision" date of the YANG module.

Aguado, et al.            Expires May 20, 2020                  [Page 1]
Internet-Draft                    l3nm                     November 2019

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 May 20, 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 . . . . . . . . . . . . . . . . . . . . . . .   4
     1.2.  Requirements Language . . . . . . . . . . . . . . . . . .   5
   2.  Reference Architecture  . . . . . . . . . . . . . . . . . . .   6
   3.  Description of the L3NM YANG Module . . . . . . . . . . . . .   8
     3.1.  Structure of the Module . . . . . . . . . . . . . . . . .   9
     3.2.  Modeling a L3 VPN Service . . . . . . . . . . . . . . . .   9
       3.2.1.  VPN node  . . . . . . . . . . . . . . . . . . . . . .  10
         3.2.1.1.  VPN Network Access  . . . . . . . . . . . . . . .  11
           3.2.1.1.1.  Connection  . . . . . . . . . . . . . . . . .  11
           3.2.1.1.2.  IP Connection . . . . . . . . . . . . . . . .  13
           3.2.1.1.3.  Routing Protocols . . . . . . . . . . . . . .  14
       3.2.2.  Concept of Import/Export Profiles . . . . . . . . . .  15
       3.2.3.  Multicast . . . . . . . . . . . . . . . . . . . . . .  16

Aguado, et al.            Expires May 20, 2020                  [Page 2]
Internet-Draft                    l3nm                     November 2019

     3.3.  VPN profiles  . . . . . . . . . . . . . . . . . . . . . .  16
Show full document text
RFC Editor IASA & IETF LLC IETF Trust IRTF IETF IESG IAB IANA Privacy Statement IETF Tools