A Layer 3 VPN Network YANG Model
draft-ietf-opsawg-l3sm-l3nm-05
|
Document |
Type |
|
Active Internet-Draft (opsawg WG)
|
|
Authors |
|
samier barguil
,
Oscar de Dios
,
Mohamed Boucadair
,
Luis Munoz
,
Alejandro Aguado
|
|
Last updated |
|
2020-10-19
(latest revision 2020-10-16)
|
|
Replaces |
|
draft-aguado-opsawg-l3sm-l3nm
|
|
Stream |
|
IETF
|
|
Intended RFC status |
|
Proposed Standard
|
|
Formats |
|
plain text
pdf
htmlized (tools)
htmlized
bibtex
|
|
Yang Validation |
|
☯
19 errors, 0 warnings.
draft-ietf-opsawg-l3sm-l3nm-05.txt:
xym 0.4.10:
Extracting 'ietf-l3vpn-ntw@2020-10-16.yang'
Removed 0 empty lines
ietf-l3vpn-ntw@2020-10-16.yang:
pyang 2.4.0: pyang --verbose --ietf -p {libs} {model}:
# module search path: a/www/ietf-ftp/yang/rfcmod/:/a/www/ietf-ftp/yang/draftmod/:/a/www/ietf-ftp/yang/ianamod/:/a/www/ietf-ftp/yang/catalogmod/:.:/var/lib/wwwrun/yang/modules:/a/www/ietf-datatracker/7.24.0/env/share/yang/modules
# read ietf-l3vpn-ntw@2020-10-16.yang (CL)
# read /a/www/ietf-ftp/yang/draftmod/ietf-vpn-common@2021-01-14.yang
# read /a/www/ietf-datatracker/7.24.0/env/share/yang/modules/ietf/ietf-netconf-acm.yang
# read /a/www/ietf-ftp/yang/rfcmod/ietf-netconf-acm@2018-02-14.yang
# read /a/www/ietf-datatracker/7.24.0/env/share/yang/modules/ietf/ietf-yang-types.yang
# read /a/www/ietf-ftp/yang/catalogmod/ietf-yang-types@2020-07-06.yang
# read /a/www/ietf-datatracker/7.24.0/env/share/yang/modules/ietf/ietf-routing-types.yang
# read /a/www/ietf-ftp/yang/rfcmod/ietf-routing-types@2017-12-04.yang
# read /a/www/ietf-datatracker/7.24.0/env/share/yang/modules/ietf/ietf-inet-types.yang
# read /a/www/ietf-ftp/yang/catalogmod/ietf-inet-types@2020-07-06.yang
# read /a/www/ietf-datatracker/7.24.0/env/share/yang/modules/ietf/ietf-packet-fields.yang
# read /a/www/ietf-ftp/yang/rfcmod/ietf-packet-fields@2019-03-04.yang
# read /a/www/ietf-datatracker/7.24.0/env/share/yang/modules/ietf/ietf-ethertypes.yang
# read /a/www/ietf-ftp/yang/rfcmod/ietf-ethertypes@2019-03-04.yang
ietf-l3vpn-ntw@2020-10-16.yang:311: error: type "address-family" not found in module "ietf-vpn-common"
ietf-l3vpn-ntw@2020-10-16.yang:335: error: grouping "vpn-node-group" not found in module "ietf-vpn-common"
ietf-l3vpn-ntw@2020-10-16.yang:1256: error: type "address-family" not found in module "ietf-vpn-common"
ietf-l3vpn-ntw@2020-10-16.yang:1340: error: type "address-family" not found in module "ietf-vpn-common"
ietf-l3vpn-ntw@2020-10-16.yang:1504: error: type "address-family" not found in module "ietf-vpn-common"
ietf-l3vpn-ntw@2020-10-16.yang:1635: error: type "address-family" not found in module "ietf-vpn-common"
ietf-l3vpn-ntw@2020-10-16.yang:1654: error: type "address-family" not found in module "ietf-vpn-common"
ietf-l3vpn-ntw@2020-10-16.yang:1888: error: type "address-family" not found in module "ietf-vpn-common"
ietf-l3vpn-ntw@2020-10-16.yang:1946: error: type "address-family" not found in module "ietf-vpn-common"
yanglint SO 1.6.7: yanglint --verbose -p {tmplib} -p {rfclib} -p {draftlib} -p {ianalib} -p {cataloglib} {model} -i:
err : No resolvents found for type "address-family".
err : Failed to resolve uses "vpn-common:vpn-node-group". (/ietf-l3vpn-ntw:l3vpn-ntw/vpn-services/vpn-service/vpn-nodes/vpn-node/vpn-common:vpn-node-group)
err : No resolvents found for type "address-family".
err : No resolvents found for type "address-family".
err : No resolvents found for type "address-family".
err : No resolvents found for type "address-family".
err : No resolvents found for type "address-family".
err : No resolvents found for type "address-family".
err : No resolvents found for type "address-family".
err : Module "ietf-l3vpn-ntw" parsing failed.
|
|
Reviews |
|
|
|
Additional Resources |
|
|
Stream |
WG state
|
|
WG Document
|
|
Document shepherd |
|
No shepherd assigned
|
IESG |
IESG state |
|
I-D Exists
|
|
Consensus Boilerplate |
|
Yes
|
|
Telechat date |
|
|
|
Responsible AD |
|
(None)
|
|
Send notices to |
|
(None)
|
OPSAWG S. Barguil
Internet-Draft O. Gonzalez de Dios, Ed.
Intended status: Standards Track Telefonica
Expires: April 19, 2021 M. Boucadair, Ed.
Orange
L. Munoz
Vodafone
A. Aguado
Nokia
October 16, 2020
A Layer 3 VPN Network YANG Model
draft-ietf-opsawg-l3sm-l3nm-05
Abstract
This document defines a L3VPN Network YANG Model (L3NM) that can be
used to manage the provisioning of Layer 3 Virtual Private Network
(VPN) services within a Service Provider's network. The model
provides a network-centric view of L3VPN services.
L3NM is meant to be used by a Network Controller to derive the
configuration information that will be sent to relevant network
devices. The model can also facilitate the communication between a
service orchestrator and a network controller/orchestrator.
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.
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
Barguil, et al. Expires April 19, 2021 [Page 1]
Internet-Draft L3NM October 2020
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 April 19, 2021.
Copyright Notice
Copyright (c) 2020 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
2. Requirements Language . . . . . . . . . . . . . . . . . . . . 4
3. Terminology . . . . . . . . . . . . . . . . . . . . . . . . . 4
4. L3NM Reference Architecture . . . . . . . . . . . . . . . . . 6
5. Relation with other YANG Models . . . . . . . . . . . . . . . 8
6. Sample Uses of the L3NM Data Model . . . . . . . . . . . . . 10
6.1. Enterprise Layer 3 VPN Services . . . . . . . . . . . . . 10
6.2. Multi-Domain Resource Management . . . . . . . . . . . . 10
6.3. Management of Multicast Services . . . . . . . . . . . . 11
7. Description of the L3NM YANG Module . . . . . . . . . . . . . 11
7.1. Overall Structure of the Module . . . . . . . . . . . . . 11
7.2. VPN Profiles . . . . . . . . . . . . . . . . . . . . . . 12
7.3. Modeling a Layer 3 VPN Service . . . . . . . . . . . . . 13
7.3.1. Service Status . . . . . . . . . . . . . . . . . . . 15
7.3.2. Concept of Import/Export Profiles . . . . . . . . . . 15
7.3.3. Underlay Transport . . . . . . . . . . . . . . . . . 16
7.3.4. VPN Node . . . . . . . . . . . . . . . . . . . . . . 17
7.3.4.1. RT/RD Assignment/auto-assignment . . . . . . . . 19
7.3.4.2. VPN Network Access . . . . . . . . . . . . . . . 20
7.3.4.2.1. Connection . . . . . . . . . . . . . . . . . 21
7.3.4.2.2. IP Connections . . . . . . . . . . . . . . . 23
Barguil, et al. Expires April 19, 2021 [Page 2]
Internet-Draft L3NM October 2020
Show full document text