A YANG Data Model for Optical Transport Network Topology
draft-ietf-ccamp-otn-topo-yang-02
|
| Document |
Type |
|
Active Internet-Draft (ccamp WG)
|
|
Last updated |
|
2017-10-30
|
|
Replaces |
|
draft-zhang-ccamp-l1-topo-yang
|
|
Stream |
|
IETF
|
|
Intended RFC status |
|
(None)
|
|
Formats |
|
plain text
pdf
html
bibtex
|
|
Yang Validation |
|
☯
0 errors, 0 warnings.
draft-ietf-ccamp-otn-topo-yang-02.txt:
xym 0.4:
Extracting 'ietf-otn-topology@2017-10-30.yang'
Removed 0 empty lines
ietf-otn-topology@2017-10-30.yang:
pyang 1.7.4: pyang --verbose --ietf -p {libs} {model}:
No validation errors
yanglint 0.14.78: yanglint --verbose -p {rfclib} -p {draftlib} -p {tmplib} {model} -i:
No validation errors
|
|
Additional URLs |
|
|
| 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)
|
CCAMP Working Group H. Zheng
Internet-Draft Z. Fan
Intended status: Standards Track Huawei Technologies
Expires: May 3, 2018 A. Sharma
Google
X. Liu
Jabil
S. Belotti
Nokia
Y. Xu
CAICT
L. Wang
China Mobile
O. Gonzalez de Dios
Telefonica
October 30, 2017
A YANG Data Model for Optical Transport Network Topology
draft-ietf-ccamp-otn-topo-yang-02
Abstract
A transport network is a server-layer network designed to provide
connectivity services for a client-layer network to carry the client
traffic transparently across the server-layer network resources. A
transport network can be constructed from equipments utilizing any of
a number of different transport technologies such as the evolving
Optical Transport Networks (OTN) or packet transport as provided by
the MPLS-Transport Profile (MPLS-TP).
This document describes a YANG data model to describe the topologies
of an Optical Transport Network (OTN). It is independent of control
plane protocols and captures topological and resource related
information pertaining to OTN. This model enables clients, which
interact with a transport domain controller via a REST interface, for
OTN topology related operations such as obtaining the relevant
topology resource information.
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/.
Zheng, et al. Expires May 3, 2018 [Page 1]
Internet-Draft OTN Topology YANG Model October 2017
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 3, 2018.
Copyright Notice
Copyright (c) 2017 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 . . . . . . . . . . . . . . . . . . . . . . . . 2
2. Terminology and Notations . . . . . . . . . . . . . . . . . . 3
3. YANG Data Model for OTN Topology . . . . . . . . . . . . . . 4
3.1. the YANG Tree . . . . . . . . . . . . . . . . . . . . . . 4
3.2. Explanation of the OTN Topology Data Model . . . . . . . 4
3.3. The YANG Code . . . . . . . . . . . . . . . . . . . . . . 5
4. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 9
5. Manageability Considerations . . . . . . . . . . . . . . . . 9
6. Security Considerations . . . . . . . . . . . . . . . . . . . 9
7. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . 10
8. Contributors . . . . . . . . . . . . . . . . . . . . . . . . 10
9. References . . . . . . . . . . . . . . . . . . . . . . . . . 10
9.1. Normative References . . . . . . . . . . . . . . . . . . 10
9.2. Informative References . . . . . . . . . . . . . . . . . 11
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 12
1. Introduction
Show full document text