Layer 3 VPN Network Model
draft-ietf-opsawg-l3sm-l3nm-00

The information below is for an old version of the document
Document Type Active Internet-Draft (opsawg WG)
Last updated 2019-10-18
Replaces draft-aguado-opsawg-l3sm-l3nm
Stream IETF
Intended RFC status (None)
Formats pdf htmlized bibtex
Stream WG state WG Document
Document shepherd No shepherd assigned
IESG IESG state I-D Exists
Consensus Boilerplate Unknown
Telechat date
Responsible AD (None)
Send notices to (None)
Internet Engineering Task Force                                A. Aguado
Internet-Draft                                                     Nokia
Intended status: Standards Track                O. Gonzalez de Dios, Ed.
Expires: April 20, 2020                                         V. Lopez
                                                              Telefonica
                                                                D. Voyer
                                                             Bell Canada
                                                                L. Munoz
                                                                Vodafone
                                                        October 18, 2019

                       Layer 3 VPN Network Model
                     draft-ietf-opsawg-l3sm-l3nm-00

Abstract

   RFC8299 defines a L3VPN Service YANG data Model (L3SM) that can be
   used for communication between customers and network operators.  Such
   model is adequate for the customer to network operator conversation
   and plays the role of a Customer Service Model, according to the
   terminology defined in RFC8309.

   There is a need for a YANG 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 (aka
   network controller / orchestrator).

   This document proposes a L3VPN Network Yang Model (L3NM) to
   facilitate communication between a service orchestrator and a network
   controller / orchestrator.  The resulting model is called the L3VPN
   Network Model (L3NM) and provides a network-centric view of the L3VPN
   services.

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

Aguado, et al.           Expires April 20, 2020                 [Page 1]
Internet-Draft                    l3nm                      October 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 April 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 . . . . . . . . . . . . . . . . . . . . . . .   3
     1.2.  Requirements Language . . . . . . . . . . . . . . . . . .   3
   2.  REFERENCE ARCHITECTURE  . . . . . . . . . . . . . . . . . . .   4
   3.  YANG MODEL EXPLANATION  . . . . . . . . . . . . . . . . . . .   6
     3.1.  STRUCTURE OF THE MODEL  . . . . . . . . . . . . . . . . .   7
     3.2.  SITE AND BEARERS  . . . . . . . . . . . . . . . . . . . .   7
     3.3.  BEARER AND ETHERNET ENCAPSULATION . . . . . . . . . . . .   7
     3.4.  MULTI-DOMAIN RESOURCE MANAGEMENT  . . . . . . . . . . . .   7
     3.5.  REMOTE FAR-END CONFIGURATION  . . . . . . . . . . . . . .   8
     3.6.  PROVIDE EDGE IDENTIFICATION POINT . . . . . . . . . . . .   8
   4.  DESING OF THE DATA MODEL  . . . . . . . . . . . . . . . . . .   9
   5.  YANG MODULE . . . . . . . . . . . . . . . . . . . . . . . . .  20
   6.  IANA CONSIDERATIONS . . . . . . . . . . . . . . . . . . . . .  93
   7.  SECURITY CONSIDERATIONS . . . . . . . . . . . . . . . . . . .  93
   8.  IMPLEMENTATION STATUS . . . . . . . . . . . . . . . . . . . .  93
   9.  ACKNOWLEDGEMENTS  . . . . . . . . . . . . . . . . . . . . . .  94
   10. CONTRIBUTORS  . . . . . . . . . . . . . . . . . . . . . . . .  94
   11. References  . . . . . . . . . . . . . . . . . . . . . . . . .  94
     11.1.  NORMATIVE REFERENCES . . . . . . . . . . . . . . . . . .  94
     11.2.  INFORMATIVE REFERENCES . . . . . . . . . . . . . . . . .  94
   Authors' Addresses  . . . . . . . . . . . . . . . . . . . . . . .  95

Aguado, et al.           Expires April 20, 2020                 [Page 2]
Show full document text