--- 1/draft-ietf-netmod-interfaces-cfg-00.txt 2011-05-20 15:15:21.000000000 +0200 +++ 2/draft-ietf-netmod-interfaces-cfg-01.txt 2011-05-20 15:15:22.000000000 +0200 @@ -1,18 +1,18 @@ Network Working Group M. Bjorklund Internet-Draft Tail-f Systems -Intended status: Standards Track April 11, 2011 -Expires: October 13, 2011 +Intended status: Standards Track May 20, 2011 +Expires: November 21, 2011 A YANG Data Model for Interface Configuration - draft-ietf-netmod-interfaces-cfg-00 + draft-ietf-netmod-interfaces-cfg-01 Abstract This document defines a YANG data model for the configuration of network interfaces. It is expected that interface type specific configuration data models augment the generic interfaces data model defined in this document. Status of this Memo @@ -22,21 +22,21 @@ 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 http://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 October 13, 2011. + This Internet-Draft will expire on November 21, 2011. Copyright Notice Copyright (c) 2011 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 @@ -45,33 +45,35 @@ 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 . . . . . . . . . . . . . . . . . . . . . . . . . 3 2. Objectives . . . . . . . . . . . . . . . . . . . . . . . . . . 4 3. Interfaces Data Model . . . . . . . . . . . . . . . . . . . . 5 3.1. The interface List . . . . . . . . . . . . . . . . . . . . 5 - 3.2. Interface References . . . . . . . . . . . . . . . . . . . 5 + 3.2. Interface References . . . . . . . . . . . . . . . . . . . 6 3.3. Interface Layering . . . . . . . . . . . . . . . . . . . . 6 4. Interfaces YANG Module . . . . . . . . . . . . . . . . . . . . 7 5. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 12 6. Security Considerations . . . . . . . . . . . . . . . . . . . 13 7. Acknowledgments . . . . . . . . . . . . . . . . . . . . . . . 14 8. Normative References . . . . . . . . . . . . . . . . . . . . . 15 Appendix A. Example: Ethernet Interface Module . . . . . . . . . 16 Appendix B. Example: Ethernet Bonding Interface Module . . . . . 18 Appendix C. Example: VLAN Interface Module . . . . . . . . . . . 19 Appendix D. Example: IP Module . . . . . . . . . . . . . . . . . 20 Appendix E. Example: NETCONF reply . . . . . . . . . . . . 21 - Author's Address . . . . . . . . . . . . . . . . . . . . . . . . . 22 + Appendix F. ChangeLog . . . . . . . . . . . . . . . . . . . . . . 22 + F.1. Version -01 . . . . . . . . . . . . . . . . . . . . . . . 22 + Author's Address . . . . . . . . . . . . . . . . . . . . . . . . . 23 1. Introduction This document defines a YANG [RFC6020] data model for the configuration of network interfaces. It is expected that interface type specific configuration data models augment the generic interfaces data model defined in this document. Network interfaces are central to the configuration of many Internet protocols. Thus, it is important to establish a common data model @@ -112,20 +114,37 @@ o The data model should support the pre-provisioning of interface configuration, i.e., it should be possible to configure an interface whose physical interface hardware is not present on the device. It is recommended that devices that support dynamic addition and removal of physical interfaces also support pre- provisioning. 3. Interfaces Data Model + The module "ietf-interfaces" has the following structure: + + +--rw interfaces + +--rw interface [name] + +--rw name string + +--rw description? string + +--rw type ift:iana-if-type + +--rw location? string + +--rw enabled? boolean + +--ro if-index* int32 + +--rw mtu? uint32 + +--rw link-up-down-trap-enable? enumeration + + This module defines one YANG feature: + + snmp-if-mib: Indicates that the server implements IF-MIB [RFC2863]. + 3.1. The interface List The data model for interface configuration presented in this document uses a flat list of interfaces. Each interface in the list is identified by its name. Furthermore, each interface has a mandatory "type" leaf, and a "location" leaf. The combination of "type" and "location" is unique within the interface list. It is expected that interface type specific data models augment the interface list, and use the "type" leaf to make the augmentation @@ -189,28 +208,26 @@ } } // other bonding config params, failover times etc. } 4. Interfaces YANG Module RFC Ed.: update the date below with the date of RFC publication and remove this note. - This YANG module references [RFC2863]. - - file "ietf-interfaces@2011-03-30.yang" + file "ietf-interfaces@2011-05-20.yang" module ietf-interfaces { namespace "urn:ietf:params:xml:ns:yang:ietf-interfaces"; - prefix "if"; + prefix if; import iana-if-type { prefix ift; } organization "IETF NETMOD (NETCONF Data Modeling Language) Working Group"; contact "WG Web: @@ -231,29 +248,30 @@ Copyright (c) 2011 IETF Trust and the persons identified as authors of the code. All rights reserved. Redistribution and use in source and binary forms, with or without modification, is permitted pursuant to, and subject to the license terms contained in, the Simplified BSD License set forth in Section 4.c of the IETF Trust's Legal Provisions Relating to IETF Documents (http://trustee.ietf.org/license-info). + This version of this YANG module is part of RFC XXXX; see the RFC itself for full legal notices."; // RFC Ed.: replace XXXX with actual RFC number and remove this // note. // RFC Ed.: update the date below with the date of RFC publication // and remove this note. - revision 2011-03-29 { + revision 2011-05-20 { description "Initial revision."; reference "RFC XXXX: A YANG Data Model for Interface Configuration"; } /* Typedefs */ typedef interface-ref { type leafref { @@ -261,22 +279,21 @@ } description "This type is used by data models that need to reference interfaces."; } /* Features */ feature snmp-if-mib { description - "This feature indicates that the server implements IF-MIB, - accessible over SNMP."; + "This feature indicates that the server implements IF-MIB."; reference "RFC 2863: The Interfaces Group MIB"; } /* Data nodes */ container interfaces { description "Interface parameters."; @@ -341,42 +359,30 @@ ports, the location can be one of '1' to '8'. As another example, if a device has N cards of M ports, the location can be on the form 'n/m'. When an interface entry is created, a server MAY initialize the location leaf with a valid value, e.g., if it is possible to derive the location from the name of the interface."; } - leaf admin-status { - type enumeration { - enum "up" { - value 1; - } - enum "down" { - value 2; - } - } - default "up"; + leaf enabled { + type boolean; + default "true"; description "The desired state of the interface. This leaf contains the configured, desired state of the interface. Systems that implement the IF-MIB use the value of this leaf to set IF-MIB.ifAdminStatus after an ifEntry has been initialized, as described in RFC 2863."; - // FIXME: Can we say that changing ifAdminStatus does NOT - // change this object? If not, is the opposite - // always true, i.e. that changing ifAdminStatus - // results in a change of this object (in running)? - // Or should we be silent? reference "RFC 2863: The Interfaces Group MIB - ifAdminStatus"; } leaf-list if-index { if-feature snmp-if-mib; type int32 { range "1..2147483647"; } config false; @@ -446,29 +452,60 @@ This document registers a YANG module in the YANG Module Names registry [RFC6020]. name: ietf-interfaces namespace: urn:ietf:params:xml:ns:yang:ietf-interfaces prefix: if reference: RFC XXXX 6. Security Considerations - TBD. + The YANG module and submodules defined in this memo are designed to + be accessed via the NETCONF protocol [I-D.ietf-netconf-4741bis]. The + lowest NETCONF layer is the secure transport layer and the mandatory- + to-implement secure transport is SSH [I-D.ietf-netconf-rfc4742bis]. + + There are a number of data nodes defined in the YANG module and + submodules which are writable/creatable/deletable (i.e., config true, + which is the default). These data nodes may be considered sensitive + or vulnerable in some network environments. Write operations (e.g., + edit-config) to these data nodes without proper protection can have a + negative effect on network operations. These are the subtrees and + data nodes and their sensitivity/vulnerability: + + /interfaces/interface: This list specify the configured interfaces + on a device. Unauthorized access to this list could cause the + device to ignore packets destined to it. + + /interfaces/interface/enabled: This leaf controls if an interface is + enabled or not. Unauthorized access to this leaf could cause the + device to ignore packets destined to it. 7. Acknowledgments The author wishes to thank Per Hedeland, Ladislav Lhotka, and Juergen Schoenwaelder for their helpful comments. 8. Normative References + [I-D.ietf-netconf-4741bis] + Enns, R., Bjorklund, M., Schoenwaelder, J., and A. + Bierman, "Network Configuration Protocol (NETCONF)", + draft-ietf-netconf-4741bis-10 (work in progress), + March 2011. + + [I-D.ietf-netconf-rfc4742bis] + Wasserman, M. and T. Goddard, "Using the NETCONF + Configuration Protocol over Secure Shell (SSH)", + draft-ietf-netconf-rfc4742bis-08 (work in progress), + March 2011. + [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate Requirement Levels", BCP 14, RFC 2119, March 1997. [RFC2863] McCloghrie, K. and F. Kastenholz, "The Interfaces Group MIB", RFC 2863, June 2000. [RFC3688] Mealling, M., "The IETF XML Registry", BCP 81, RFC 3688, January 2004. [RFC6020] Bjorklund, M., "YANG - A Data Modeling Language for the @@ -670,16 +710,26 @@
192.168.1.1 24
+Appendix F. ChangeLog + + RFC Editor: remove this section upon publication as an RFC. + +F.1. Version -01 + + o Changed leaf "if-admin-status" to leaf "enabled". + + o Added Security Considerations + Author's Address Martin Bjorklund Tail-f Systems Email: mbj@tail-f.com