A YANG Data Model for Network Topologies
RFC 8345
|
| Document |
Type |
|
RFC - Proposed Standard
(March 2018; No errata)
|
|
Last updated |
|
2018-03-16
|
|
Replaces |
|
draft-clemm-i2rs-yang-network-topo
|
|
Stream |
|
IETF
|
|
Formats |
|
plain text
pdf
html
bibtex
|
|
Yang Validation |
|
☯
0 errors, 0 warnings.
draft-ietf-i2rs-yang-network-topo-20.txt:
xym 0.4:
Extracting 'ietf-network@2017-12-18.yang'
Removed 0 empty lines
Extracting 'ietf-network-topology@2017-12-18.yang'
Removed 0 empty lines
Extracting 'ietf-network-state@2017-12-18.yang'
Removed 0 empty lines
Extracting 'ietf-network-topology-state@2017-12-18.yang'
Removed 0 empty lines
ietf-network-topology@2017-12-18.yang:
pyang 1.7.4: pyang --verbose --ietf -p {libs} {model}:
No validation errors
yanglint 0.14.73: yanglint --verbose -p {rfclib} -p {draftlib} -p {tmplib} {model} -i:
No validation errors
ietf-network-topology-state@2017-12-18.yang:
pyang 1.7.4: pyang --verbose --ietf -p {libs} {model}:
No validation errors
yanglint 0.14.73: yanglint --verbose -p {rfclib} -p {draftlib} -p {tmplib} {model} -i:
No validation errors
ietf-network@2017-12-18.yang:
pyang 1.7.4: pyang --verbose --ietf -p {libs} {model}:
No validation errors
yanglint 0.14.73: yanglint --verbose -p {rfclib} -p {draftlib} -p {tmplib} {model} -i:
No validation errors
ietf-network-state@2017-12-18.yang:
pyang 1.7.4: pyang --verbose --ietf -p {libs} {model}:
No validation errors
yanglint 0.14.73: yanglint --verbose -p {rfclib} -p {draftlib} -p {tmplib} {model} -i:
No validation errors
|
|
Reviews |
|
|
|
Additional URLs |
|
|
| Stream |
WG state
|
|
Submitted to IESG for Publication
(wg milestone:
Dec 2016 - Request Publication ...
)
|
|
Document shepherd |
|
Susan Hares
|
|
Shepherd write-up |
|
Show
(last changed 2017-11-15)
|
| IESG |
IESG state |
|
RFC 8345 (Proposed Standard)
|
|
Consensus Boilerplate |
|
Yes
|
|
Telechat date |
|
|
|
Responsible AD |
|
Alia Atlas
|
|
Send notices to |
|
"Susan Hares" <shares@ndzh.com>
|
| IANA |
IANA review state |
|
Version Changed - Review Needed
|
|
IANA action state |
|
RFC-Ed-Ack
|
Internet Engineering Task Force (IETF) A. Clemm
Request for Comments: 8345 Huawei
Category: Standards Track J. Medved
ISSN: 2070-1721 Cisco
R. Varga
Pantheon Technologies SRO
N. Bahadur
Bracket Computing
H. Ananthakrishnan
Packet Design
X. Liu
Jabil
March 2018
A YANG Data Model for Network Topologies
Abstract
This document defines an abstract (generic, or base) YANG data model
for network/service topologies and inventories. The data model
serves as a base model that is augmented with technology-specific
details in other, more specific topology and inventory data models.
Status of This Memo
This is an Internet Standards Track document.
This document is a product of the Internet Engineering Task Force
(IETF). It represents the consensus of the IETF community. It has
received public review and has been approved for publication by the
Internet Engineering Steering Group (IESG). Further information on
Internet Standards is available in Section 2 of RFC 7841.
Information about the current status of this document, any errata,
and how to provide feedback on it may be obtained at
https://www.rfc-editor.org/info/rfc8345.
Clemm, et al. Standards Track [Page 1]
RFC 8345 YANG Data Model for Network Topologies March 2018
Copyright Notice
Copyright (c) 2018 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.
Clemm, et al. Standards Track [Page 2]
RFC 8345 YANG Data Model for Network Topologies March 2018
Table of Contents
1. Introduction ....................................................4
2. Key Words .......................................................8
3. Definitions and Abbreviations ...................................9
4. Model Structure Details .........................................9
4.1. Base Network Model .........................................9
4.2. Base Network Topology Data Model ..........................12
4.3. Extending the Data Model ..................................13
4.4. Discussion and Selected Design Decisions ..................14
4.4.1. Container Structure ................................14
4.4.2. Underlay Hierarchies and Mappings ..................14
4.4.3. Dealing with Changes in Underlay Networks ..........15
4.4.4. Use of Groupings ...................................15
4.4.5. Cardinality and Directionality of Links ............16
4.4.6. Multihoming and Link Aggregation ...................16
4.4.7. Mapping Redundancy .................................16
4.4.8. Typing .............................................17
4.4.9. Representing the Same Device in Multiple Networks ..17
4.4.10. Supporting Client-Configured and
System-Controlled Network Topologies ..............18
4.4.11. Identifiers of String or URI Type .................19
5. Interactions with Other YANG Modules ...........................19
6. YANG Modules ...................................................20
6.1. Defining the Abstract Network: ietf-network ...............20
6.2. Creating Abstract Network Topology:
ietf-network-topology .....................................25
7. IANA Considerations ............................................32
8. Security Considerations ........................................33
9. References .....................................................35
9.1. Normative References ......................................35
Show full document text