draft-ietf-netmod-interfaces-cfg-06.txt   draft-ietf-netmod-interfaces-cfg-07.txt 
Network Working Group M. Bjorklund Network Working Group M. Bjorklund
Internet-Draft Tail-f Systems Internet-Draft Tail-f Systems
Intended status: Standards Track September 5, 2012 Intended status: Standards Track October 22, 2012
Expires: March 9, 2013 Expires: April 25, 2013
A YANG Data Model for Interface Management A YANG Data Model for Interface Management
draft-ietf-netmod-interfaces-cfg-06 draft-ietf-netmod-interfaces-cfg-07
Abstract Abstract
This document defines a YANG data model for the management of network This document defines a YANG data model for the management of network
interfaces. It is expected that interface type specific data models interfaces. It is expected that interface type specific data models
augment the generic interfaces data model defined in this document. augment the generic interfaces data model defined in this document.
Status of this Memo Status of this Memo
This Internet-Draft is submitted in full conformance with the This Internet-Draft is submitted in full conformance with the
skipping to change at page 1, line 32 skipping to change at page 1, line 32
Internet-Drafts are working documents of the Internet Engineering Internet-Drafts are working documents of the Internet Engineering
Task Force (IETF). Note that other groups may also distribute Task Force (IETF). Note that other groups may also distribute
working documents as Internet-Drafts. The list of current Internet- working documents as Internet-Drafts. The list of current Internet-
Drafts is at http://datatracker.ietf.org/drafts/current/. Drafts is at http://datatracker.ietf.org/drafts/current/.
Internet-Drafts are draft documents valid for a maximum of six months Internet-Drafts are draft documents valid for a maximum of six months
and may be updated, replaced, or obsoleted by other documents at any and may be updated, replaced, or obsoleted by other documents at any
time. It is inappropriate to use Internet-Drafts as reference time. It is inappropriate to use Internet-Drafts as reference
material or to cite them other than as "work in progress." material or to cite them other than as "work in progress."
This Internet-Draft will expire on March 9, 2013. This Internet-Draft will expire on April 25, 2013.
Copyright Notice Copyright Notice
Copyright (c) 2012 IETF Trust and the persons identified as the Copyright (c) 2012 IETF Trust and the persons identified as the
document authors. All rights reserved. document authors. All rights reserved.
This document is subject to BCP 78 and the IETF Trust's Legal This document is subject to BCP 78 and the IETF Trust's Legal
Provisions Relating to IETF Documents Provisions Relating to IETF Documents
(http://trustee.ietf.org/license-info) in effect on the date of (http://trustee.ietf.org/license-info) in effect on the date of
publication of this document. Please review these documents publication of this document. Please review these documents
skipping to change at page 2, line 27 skipping to change at page 2, line 27
7. Security Considerations . . . . . . . . . . . . . . . . . . . 24 7. Security Considerations . . . . . . . . . . . . . . . . . . . 24
8. Acknowledgments . . . . . . . . . . . . . . . . . . . . . . . 25 8. Acknowledgments . . . . . . . . . . . . . . . . . . . . . . . 25
9. References . . . . . . . . . . . . . . . . . . . . . . . . . . 26 9. References . . . . . . . . . . . . . . . . . . . . . . . . . . 26
9.1. Normative References . . . . . . . . . . . . . . . . . . . 26 9.1. Normative References . . . . . . . . . . . . . . . . . . . 26
9.2. Informative References . . . . . . . . . . . . . . . . . . 26 9.2. Informative References . . . . . . . . . . . . . . . . . . 26
Appendix A. Example: Ethernet Interface Module . . . . . . . . . 27 Appendix A. Example: Ethernet Interface Module . . . . . . . . . 27
Appendix B. Example: Ethernet Bonding Interface Module . . . . . 29 Appendix B. Example: Ethernet Bonding Interface Module . . . . . 29
Appendix C. Example: VLAN Interface Module . . . . . . . . . . . 30 Appendix C. Example: VLAN Interface Module . . . . . . . . . . . 30
Appendix D. Example: NETCONF <get> reply . . . . . . . . . . . . 31 Appendix D. Example: NETCONF <get> reply . . . . . . . . . . . . 31
Appendix E. ChangeLog . . . . . . . . . . . . . . . . . . . . . . 32 Appendix E. ChangeLog . . . . . . . . . . . . . . . . . . . . . . 32
E.1. Version -06 . . . . . . . . . . . . . . . . . . . . . . . 32 E.1. Version -07 . . . . . . . . . . . . . . . . . . . . . . . 32
E.2. Version -05 . . . . . . . . . . . . . . . . . . . . . . . 32 E.2. Version -06 . . . . . . . . . . . . . . . . . . . . . . . 32
E.3. Version -04 . . . . . . . . . . . . . . . . . . . . . . . 32 E.3. Version -05 . . . . . . . . . . . . . . . . . . . . . . . 32
E.4. Version -03 . . . . . . . . . . . . . . . . . . . . . . . 32 E.4. Version -04 . . . . . . . . . . . . . . . . . . . . . . . 32
E.5. Version -02 . . . . . . . . . . . . . . . . . . . . . . . 32 E.5. Version -03 . . . . . . . . . . . . . . . . . . . . . . . 32
E.6. Version -01 . . . . . . . . . . . . . . . . . . . . . . . 32 E.6. Version -02 . . . . . . . . . . . . . . . . . . . . . . . 32
Author's Address . . . . . . . . . . . . . . . . . . . . . . . . . 33 E.7. Version -01 . . . . . . . . . . . . . . . . . . . . . . . 33
Author's Address . . . . . . . . . . . . . . . . . . . . . . . . . 34
1. Introduction 1. Introduction
This document defines a YANG [RFC6020] data model for the management This document defines a YANG [RFC6020] data model for the management
of network interfaces. It is expected that interface type specific of network interfaces. It is expected that interface type specific
data models augment the generic interfaces data model defined in this data models augment the generic interfaces data model defined in this
document. document.
Network interfaces are central to the management of many Internet Network interfaces are central to the management of many Internet
protocols. Thus, it is important to establish a common data model protocols. Thus, it is important to establish a common data model
skipping to change at page 5, line 26 skipping to change at page 5, line 26
+--rw location? string +--rw location? string
+--rw enabled? boolean +--rw enabled? boolean
+--ro oper-status? enumeration +--ro oper-status? enumeration
+--ro last-change? yang:date-and-time +--ro last-change? yang:date-and-time
+--ro if-index? int32 +--ro if-index? int32
+--rw mtu? uint32 +--rw mtu? uint32
+--rw link-up-down-trap-enable? enumeration +--rw link-up-down-trap-enable? enumeration
+--ro phys-address? yang:phys-address +--ro phys-address? yang:phys-address
+--ro higher-layer-if* interface-ref +--ro higher-layer-if* interface-ref
+--ro lower-layer-if* interface-ref +--ro lower-layer-if* interface-ref
+--rw speed? yang:gauge64 +--ro speed? yang:gauge64
+--ro statistics +--ro statistics
+--ro discontinuity-time? yang:date-and-time +--ro discontinuity-time? yang:date-and-time
+--ro in-octets? yang:counter64 +--ro in-octets? yang:counter64
+--ro in-unicast-pkts? yang:counter64 +--ro in-unicast-pkts? yang:counter64
+--ro in-broadcast-pkts? yang:counter64 +--ro in-broadcast-pkts? yang:counter64
+--ro in-multicast-pkts? yang:counter64 +--ro in-multicast-pkts? yang:counter64
+--ro in-discards? yang:counter32 +--ro in-discards? yang:counter32
+--ro in-errors? yang:counter32 +--ro in-errors? yang:counter32
+--ro in-unknown-protos? yang:counter32 +--ro in-unknown-protos? yang:counter32
+--ro out-octets? yang:counter64 +--ro out-octets? yang:counter64
skipping to change at page 10, line 13 skipping to change at page 10, line 13
Mapping of YANG data nodes to IF-MIB objects Mapping of YANG data nodes to IF-MIB objects
5. Interfaces YANG Module 5. Interfaces YANG Module
This YANG module imports a typedef from This YANG module imports a typedef from
[I-D.ietf-netmod-iana-if-type]. [I-D.ietf-netmod-iana-if-type].
RFC Ed.: update the date below with the date of RFC publication and RFC Ed.: update the date below with the date of RFC publication and
remove this note. remove this note.
<CODE BEGINS> file "ietf-interfaces@2012-09-05.yang" <CODE BEGINS> file "ietf-interfaces@2012-10-22.yang"
module ietf-interfaces { module ietf-interfaces {
namespace "urn:ietf:params:xml:ns:yang:ietf-interfaces"; namespace "urn:ietf:params:xml:ns:yang:ietf-interfaces";
prefix if; prefix if;
import ietf-yang-types { import ietf-yang-types {
prefix yang; prefix yang;
} }
import iana-if-type { import iana-if-type {
skipping to change at page 11, line 16 skipping to change at page 11, line 16
(http://trustee.ietf.org/license-info). (http://trustee.ietf.org/license-info).
This version of this YANG module is part of RFC XXXX; see This version of this YANG module is part of RFC XXXX; see
the RFC itself for full legal notices."; the RFC itself for full legal notices.";
// RFC Ed.: replace XXXX with actual RFC number and remove this // RFC Ed.: replace XXXX with actual RFC number and remove this
// note. // note.
// RFC Ed.: update the date below with the date of RFC publication // RFC Ed.: update the date below with the date of RFC publication
// and remove this note. // and remove this note.
revision 2012-09-05 { revision 2012-10-22 {
description description
"Initial revision."; "Initial revision.";
reference reference
"RFC XXXX: A YANG Data Model for Interface Management"; "RFC XXXX: A YANG Data Model for Interface Management";
} }
/* Typedefs */ /* Typedefs */
typedef interface-ref { typedef interface-ref {
type leafref { type leafref {
skipping to change at page 17, line 13 skipping to change at page 17, line 13
config false; config false;
description description
"A list of references to interfaces layered underneath this "A list of references to interfaces layered underneath this
interface."; interface.";
reference reference
"RFC 2863: The Interfaces Group MIB - ifStackTable"; "RFC 2863: The Interfaces Group MIB - ifStackTable";
} }
leaf speed { leaf speed {
type yang:gauge64; type yang:gauge64;
config false;
units "bits / second"; units "bits / second";
description description
"An estimate of the interface's current bandwidth in bits "An estimate of the interface's current bandwidth in bits
per second. For interfaces which do not vary in per second. For interfaces which do not vary in
bandwidth or for those where no accurate estimation can bandwidth or for those where no accurate estimation can
be made, this node should contain the nominal bandwidth. be made, this node should contain the nominal bandwidth.
For interfaces that has no concept of bandwidth, this For interfaces that has no concept of bandwidth, this
node is not present."; node is not present.";
reference reference
"RFC 2863: The Interfaces Group MIB - "RFC 2863: The Interfaces Group MIB -
skipping to change at page 32, line 9 skipping to change at page 32, line 9
xmlns="http://example.com/vlan">true</vlan-tagging> xmlns="http://example.com/vlan">true</vlan-tagging>
</interface> </interface>
</interfaces> </interfaces>
</data> </data>
</rpc-reply> </rpc-reply>
Appendix E. ChangeLog Appendix E. ChangeLog
RFC Editor: remove this section upon publication as an RFC. RFC Editor: remove this section upon publication as an RFC.
E.1. Version -06 E.1. Version -07
o Made leaf speed config false.
E.2. Version -06
o Added oper-status leaf. o Added oper-status leaf.
o Added leaf-lists higher-layer-if and lower-layer-if, that show the o Added leaf-lists higher-layer-if and lower-layer-if, that show the
interface layering. interface layering.
o Added container statistics with counters. o Added container statistics with counters.
E.2. Version -05 E.3. Version -05
o Added an Informative References section. o Added an Informative References section.
o Updated the Security Considerations section. o Updated the Security Considerations section.
o Clarified the behavior of an NETCONF server when invalid values o Clarified the behavior of an NETCONF server when invalid values
are received. are received.
E.3. Version -04 E.4. Version -04
o Clarified why ifPromiscuousMode is not part of this data model. o Clarified why ifPromiscuousMode is not part of this data model.
o Added a table that shows the mapping between this YANG data model o Added a table that shows the mapping between this YANG data model
and IF-MIB. and IF-MIB.
E.4. Version -03 E.5. Version -03
o Added the section Relationship to the IF-MIB. o Added the section Relationship to the IF-MIB.
o Changed if-index to be a leaf instead of leaf-list. o Changed if-index to be a leaf instead of leaf-list.
o Explained the notation used in the data model tree picture. o Explained the notation used in the data model tree picture.
E.5. Version -02 E.6. Version -02
o Editorial fixes o Editorial fixes
E.6. Version -01 E.7. Version -01
o Changed leaf "if-admin-status" to leaf "enabled". o Changed leaf "if-admin-status" to leaf "enabled".
o Added Security Considerations o Added Security Considerations
Author's Address Author's Address
Martin Bjorklund Martin Bjorklund
Tail-f Systems Tail-f Systems
 End of changes. 14 change blocks. 
20 lines changed or deleted 26 lines changed or added

This html diff was produced by rfcdiff 1.41. The latest version is available from http://tools.ietf.org/tools/rfcdiff/