A YANG Data Model for Interface Management
RFC 7223
|
Document |
Type |
|
RFC - Proposed Standard
(May 2014; Errata)
|
|
Author |
|
Martin Björklund
|
|
Last updated |
|
2020-01-21
|
|
Replaces |
|
draft-bjorklund-netmod-interfaces-cfg
|
|
Stream |
|
IETF
|
|
Formats |
|
plain text
html
pdf
htmlized
with errata
bibtex
|
|
Yang Validation |
|
☯
0 errors, 2 warnings.
draft-ietf-netmod-interfaces-cfg-16.txt:
xym 0.4:
Extracting 'ietf-interfaces@2013-12-23.yang'
Removed 0 empty lines
Extracting 'ex-ethernet'
Getting YANG file name from module name: ex-ethernet.yang
Extracting 'ex-ethernet-bonding'
Getting YANG file name from module name: ex-ethernet-bonding.yang
Extracting 'ex-vlan'
Getting YANG file name from module name: ex-vlan.yang
ietf-interfaces@2013-12-23.yang:
pyang 1.7.3: pyang --verbose --ietf -p {libs} {model}:
ietf-interfaces@2013-12-23.yang:247: warning: RFC 6087: 4.10,4.12: statement "enum" should have a "description" substatement
ietf-interfaces@2013-12-23.yang:250: warning: RFC 6087: 4.10,4.12: statement "enum" should have a "description" substatement
yanglint 0.14.53: yanglint --verbose -p {rfclib} -p {draftlib} -p {tmplib} {model} -i:
No validation errors
|
|
Reviews |
|
|
|
Additional Resources |
|
|
Stream |
WG state
|
|
Submitted to IESG for Publication
|
|
Document shepherd |
|
Thomas Nadeau
|
|
Shepherd write-up |
|
Show
(last changed 2014-01-14)
|
IESG |
IESG state |
|
RFC 7223 (Proposed Standard)
|
|
Consensus Boilerplate |
|
Yes
|
|
Telechat date |
|
|
|
Responsible AD |
|
Benoît Claise
|
|
Send notices to |
|
(None)
|
IANA |
IANA review state |
|
Version Changed - Review Needed
|
|
IANA action state |
|
RFC-Ed-Ack
|
Internet Engineering Task Force (IETF) M. Bjorklund
Request for Comments: 7223 Tail-f Systems
Category: Standards Track May 2014
ISSN: 2070-1721
A YANG Data Model for Interface Management
Abstract
This document defines a YANG data model for the management of network
interfaces. It is expected that interface-type-specific data models
augment the generic interfaces data model defined in this document.
The data model includes configuration data and state data (status
information and counters for the collection of statistics).
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 5741.
Information about the current status of this document, any errata,
and how to provide feedback on it may be obtained at
http://www.rfc-editor.org/info/rfc7223.
Copyright Notice
Copyright (c) 2014 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
(http://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.
Bjorklund Standards Track [Page 1]
RFC 7223 YANG Interface Management May 2014
Table of Contents
1. Introduction ....................................................2
1.1. Terminology ................................................3
1.2. Tree Diagrams ..............................................4
2. Objectives ......................................................4
3. Interfaces Data Model ...........................................5
3.1. The Interface Lists ........................................6
3.2. Interface References .......................................7
3.3. Interface Layering .........................................7
4. Relationship to the IF-MIB ......................................8
5. Interfaces YANG Module .........................................11
6. IANA Considerations ............................................26
7. Security Considerations ........................................26
8. Acknowledgments ................................................27
9. References .....................................................27
9.1. Normative References ......................................27
9.2. Informative References ....................................28
Appendix A. Example: Ethernet Interface Module ....................29
Appendix B. Example: Ethernet Bonding Interface Module ............30
Appendix C. Example: VLAN Interface Module ........................31
Appendix D. Example: NETCONF <get> Reply ..........................32
Appendix E. Examples: Interface Naming Schemes ....................35
E.1. Router with Restricted Interface Names .....................35
E.2. Router with Arbitrary Interface Names ......................36
E.3. Ethernet Switch with Restricted Interface Names ............37
E.4. Generic Host with Restricted Interface Names ...............38
E.5. Generic Host with Arbitrary Interface Names ................39
1. Introduction
This document defines a YANG [RFC6020] data model for the management
of network interfaces. It is expected that interface-type-specific
data models augment the generic interfaces data model defined in this
document.
Network interfaces are central to the management of many Internet
protocols. Thus, it is important to establish a common data model
for how interfaces are identified, configured, and monitored.
The data model includes configuration data and state data (status
information and counters for the collection of statistics).
Bjorklund Standards Track [Page 2]
RFC 7223 YANG Interface Management May 2014
1.1. Terminology
The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
"SHOULD", "SHOULD NOT", "RECOMMENDED", "NOT RECOMMENDED", "MAY", and
"OPTIONAL" in this document are to be interpreted as described in
BCP 14 [RFC2119].
Show full document text