A YANG Model for User-Network Interface (UNI) Topologies
draft-ogondio-opsawg-uni-topology-00
|
Document |
Type |
|
Active Internet-Draft (individual)
|
|
Last updated |
|
2019-11-18
|
|
Stream |
|
(None)
|
|
Intended RFC status |
|
(None)
|
|
Formats |
|
plain text
pdf
htmlized
bibtex
|
|
Yang Validation |
|
☯
0 errors, 0 warnings.
draft-ogondio-opsawg-uni-topology-00.txt:
xym 0.4:
Extracting 'ietf-uni-topology@2019-11-19.yang'
Removed 0 empty lines
ietf-uni-topology@2019-11-19.yang:
pyang 2.1: pyang --verbose --ietf -p {libs} {model}:
# read ietf-uni-topology@2019-11-19.yang (CL)
# read /a/www/ietf-datatracker/6.113.0/env/share/yang/modules/ietf/ietf-interfaces.yang
# read /a/www/ietf-ftp/yang/rfcmod/ietf-interfaces@2018-02-20.yang
# read /a/www/ietf-datatracker/6.113.0/env/share/yang/modules/ietf/ietf-yang-types.yang
# read /a/www/ietf-ftp/yang/draftmod/ietf-yang-types@2019-11-04.yang
# read /a/www/ietf-datatracker/6.113.0/env/share/yang/modules/ietf/ietf-network-topology.yang
# read /a/www/ietf-ftp/yang/rfcmod/ietf-network-topology@2018-02-26.yang
# read /a/www/ietf-datatracker/6.113.0/env/share/yang/modules/ietf/ietf-inet-types.yang
# read /a/www/ietf-ftp/yang/draftmod/ietf-inet-types@2019-11-04.yang
# read /a/www/ietf-datatracker/6.113.0/env/share/yang/modules/ietf/ietf-network.yang
# read /a/www/ietf-ftp/yang/rfcmod/ietf-network@2018-02-26.yang
yanglint 0.14.80: yanglint --verbose -p {rfclib} -p {draftlib} -p {tmplib} {model} -i:
No validation errors
|
|
Additional URLs |
|
|
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 O. Gonzalez de Dios, Ed.
Internet-Draft S. Barguil
Intended status: Standards Track Telefonica
Expires: May 22, 2020 Q. Wu
Huawei
M. Boucadair
Orange
November 19, 2019
A YANG Model for User-Network Interface (UNI) Topologies
draft-ogondio-opsawg-uni-topology-00
Abstract
This document defines a YANG data model for representing an abstract
view of the Service Provider network topology containing the points
from which its services can be attached (e.g., basic connectivity,
VPN, SDWAN). The data model augments ietf-network model by adding
the concept of service-attachment-points.The service-attachment-
points are an abstraction of the points to which network services
(such as L3 VPNs or L2 VPNs) can be attached.
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 22, 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
Gonzalez de Dios, et al. Expires May 22, 2020 [Page 1]
Internet-Draft uni-topo November 2019
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.2. Requirements Language . . . . . . . . . . . . . . . . . . 4
2. UNI Topology Model Usage . . . . . . . . . . . . . . . . . . 4
3. Yang Module Structure Details . . . . . . . . . . . . . . . . 5
4. YANG module . . . . . . . . . . . . . . . . . . . . . . . . . 6
5. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 9
6. Security Considerations . . . . . . . . . . . . . . . . . . . 9
7. Implementation Status . . . . . . . . . . . . . . . . . . . . 10
8. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . 10
9. References . . . . . . . . . . . . . . . . . . . . . . . . . 10
9.1. Normative References . . . . . . . . . . . . . . . . . . 10
9.2. Informative References . . . . . . . . . . . . . . . . . 11
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 12
1. Introduction
The User-Network Interface (UNI) is an important architectural
concept in many implementations and deployments of services such as
VPNs or managed VoIP services.
This document defines a YANG data model for representing, managing
and controlling the User Network Interface (UNI) topology. The data
model augments ietf-network module [RFC8345] by adding the concept of
service attachment points. The service attachment points are
abstraction of the points where network services such as L3 VPNs or
L2 VPNs can be attached.
This document does not make any assumption about the service provided
by the network to the users. VPN service is used for illustration
purposes.
In the context of Software-Defined Networking (SDN) [RFC7149]
[RFC7426], the defined YANG data model in this document can be used
to exchange information between control elements, so as to support
VPN service provision and resource management discussed in
[I-D.ietf-opsawg-l3sm-l3nm]. Through this model, the service
orchestration layer can learn the capability and available
endpoint(s) of interconnection resource of the underlying network.
Gonzalez de Dios, et al. Expires May 22, 2020 [Page 2]
Show full document text