--- 1/draft-ietf-netmod-intf-ext-yang-00.txt 2016-07-07 08:16:09.744968905 -0700 +++ 2/draft-ietf-netmod-intf-ext-yang-01.txt 2016-07-07 08:16:09.808970504 -0700 @@ -1,21 +1,21 @@ Internet Engineering Task Force R. Wilton, Ed. Internet-Draft D. Ball -Intended status: Standards Track Cisco Systems -Expires: October 23, 2016 T. Singh +Intended status: Standards Track T. Singh +Expires: January 8, 2017 Cisco Systems S. Sivaraj Juniper Networks - April 21, 2016 + July 7, 2016 Common Interface Extension YANG Data Models - draft-ietf-netmod-intf-ext-yang-00 + draft-ietf-netmod-intf-ext-yang-01 Abstract This document defines two YANG modules that augment the Interfaces data model defined in the "YANG Data Model for Interface Management" with additional configuration and operational data nodes to support common lower layer interface properties, such as interface MTU. These properties are common to many types of interfaces on network routers and switches and are implemented by multiple network equipment vendors with similar semantics, even though some of the @@ -29,21 +29,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 23, 2016. + This Internet-Draft will expire on January 8, 2017. Copyright Notice Copyright (c) 2016 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 @@ -68,29 +68,29 @@ 3.3.3. Reuse Threshold . . . . . . . . . . . . . . . . . . . 8 3.3.4. Maximum Suppress Time . . . . . . . . . . . . . . . . 8 3.4. Encapsulation . . . . . . . . . . . . . . . . . . . . . . 8 3.5. Loopback . . . . . . . . . . . . . . . . . . . . . . . . 8 3.6. MTU . . . . . . . . . . . . . . . . . . . . . . . . . . . 8 3.7. Sub-interface . . . . . . . . . . . . . . . . . . . . . . 9 3.8. Transport Layer . . . . . . . . . . . . . . . . . . . . . 10 4. Interfaces Ethernet-Like Module . . . . . . . . . . . . . . . 10 5. Interfaces Common YANG Module . . . . . . . . . . . . . . . . 10 6. Interfaces Ethernet-Like YANG Module . . . . . . . . . . . . 19 - 7. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . 21 - 8. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 21 - 9. Security Considerations . . . . . . . . . . . . . . . . . . . 22 - 9.1. interfaces-common.yang . . . . . . . . . . . . . . . . . 22 - 9.2. interfaces-ethernet-like.yang . . . . . . . . . . . . . . 23 - 10. References . . . . . . . . . . . . . . . . . . . . . . . . . 23 - 10.1. Normative References . . . . . . . . . . . . . . . . . . 24 - 10.2. Informative References . . . . . . . . . . . . . . . . . 24 - Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 24 + 7. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . 22 + 8. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 22 + 9. Security Considerations . . . . . . . . . . . . . . . . . . . 23 + 9.1. interfaces-common.yang . . . . . . . . . . . . . . . . . 23 + 9.2. interfaces-ethernet-like.yang . . . . . . . . . . . . . . 24 + 10. References . . . . . . . . . . . . . . . . . . . . . . . . . 24 + 10.1. Normative References . . . . . . . . . . . . . . . . . . 25 + 10.2. Informative References . . . . . . . . . . . . . . . . . 25 + Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 25 1. Introduction This document defines two YANG RFC 6020 [RFC6020] modules for the management of network interfaces. It defines various augmentations to the generic interfaces data model defined in RFC 7223 [RFC7223] to support configuration of lower layer interface properties that are common across many types of network interface. One of the aims of this draft is to provide a standard namespace and @@ -196,21 +196,21 @@ interfaces. o A transport layer leaf to indicate whether the interface handles traffic at L1, L2 or L3. o A parent interface leaf useable for all types of sub-interface that are children of parent interfaces. The "interface-extensions" YANG module has the following structure: - module: interfaces-common + module: ietf-interfaces-common augment /if:interfaces/if:interface: +--rw bandwidth? uint64 augment /if:interfaces/if:interface: +--rw carrier-delay +--rw down? uint32 +--rw up? uint32 augment /if:interfaces/if:interface: +--rw dampening! +--rw half-life? uint32 +--rw reuse? uint32 @@ -371,23 +371,23 @@ 3.6. MTU Two MTU configuration leaves are provided to program the layer 2 interface in two different ways. Different mechanisms are provided to reflect the fact that devices handle their MTU configuration in different ways. A given device would only normally be expected to support MTU configuration using one of these mechanisms. The preferable way to configure MTU is using the l2-mtu leaf that specifies the maximum size of a layer 2 frame including header and - payload, but excluding any frame checksum (FCS) bytes. The payload - MTU available to higher layer protocols is calculated from the l2-mtu - after taking the layer 2 header size into account. + payload, but excluding any frame check sequence (FCS) bytes. The + payload MTU available to higher layer protocols is calculated from + the l2-mtu after taking the layer 2 header size into account. For Ethernet interfaces carrying 802.1Q VLAN tagged frames, the l2-mtu excludes the 4-8 byte overhead of any known (e.g. explicitly matched by a child sub-interface) 801.1Q VLAN tags. The alternative way to configure MTU is using the l3-mtu leaf that specifies the maximum size of payload carried by a layer 2 frame. The maximum size of the layer 2 frame can then be derived by adding on the size of the layer 2 header overheads. @@ -447,65 +447,89 @@ interface types that use Ethernet framing as their datalink layer encapsulation. This module currently contains leaves for the configuration and reporting of the operational MAC address and the burnt-in MAC address (BIA) associated with any interface using Ethernet framing. The "interfaces-ethernet-like" YANG module has the following structure: - module: interfaces-ethernet-like + module: ietf-interfaces-ethernet-like augment /if:interfaces/if:interface: +--rw ethernet-like +--rw mac-address? yang:mac-address augment /if:interfaces-state/if:interface: +--ro ethernet-like +--ro mac-address? yang:mac-address +--ro bia-mac-address? yang:mac-address 5. Interfaces Common YANG Module This YANG module augments the interface container defined in RFC 7223 [RFC7223]. - file "interfaces-common@2015-10-19.yang" - module interfaces-common { + file "ietf-interfaces-common@2016-07-07.yang" + module ietf-interfaces-common { yang-version 1.1; - namespace "urn:ietf:params:xml:ns:yang:interfaces-common"; + namespace "urn:ietf:params:xml:ns:yang:ietf-interfaces-common"; prefix if-cmn; import ietf-interfaces { prefix if; } import iana-if-type { prefix ianaift; } organization - "Cisco Systems, Inc. - Customer Service + "IETF NETMOD (NETCONF Data Modeling Language) Working Group"; - Postal: 170 W Tasman Drive - San Jose, CA 95134 + contact + "WG Web: + WG List: - Tel: +1 1800 553-NETS + WG Chair: Lou Berger + - E-mail: cs-yang@cisco.com"; + WG Chair: Kent Watsen + - contact - "Robert Wilton - rwilton@cisco.com"; + Editor: Robert Wilton + "; description "This module contains common definitions for extending the IETF interface YANG model (RFC 7223) with common configurable layer 2 - properties."; + properties. + + Copyright (c) 2016 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 XXX; see the RFC + itself for full legal notices."; + + revision 2016-07-07 { + description + "Update module title and description text to IETF standard + text"; + + reference "Internet draft: draft-ietf-netmod-intf-ext-yang-01"; + + } revision 2015-10-19 { description "Add support for various common interface configuration parameters that are likely to be widely implemented by various network device vendors."; reference "Internet draft: draft-wilton-netmod-intf-ext-yang-01"; } @@ -813,23 +841,21 @@ } } /* * Add generic support for sub-interfaces. * * This should be extended to cover all interface types that are * child interfaces of other interfaces. */ augment "/if:interfaces/if:interface" { - when "derived-from(if:type, - 'ietf-if-cmn', - 'sub-interface') or + when "derived-from(if:type, 'sub-interface') or if:type = 'ianaift:atmSubInterface' or if:type = 'ianaift:frameRelay'" { description "Any ianaift:types that explicitly represent sub-interfaces or any types that derive from the sub-interface identity"; } if-feature "sub-interfaces"; description "Add a parent interface field to interfaces that model sub-interfaces"; leaf parent-interface { @@ -875,57 +900,82 @@ } 6. Interfaces Ethernet-Like YANG Module This YANG module augments the interface container defined in RFC 7223 [RFC7223] for Etherlike interfaces. This includes Ethernet interfaces, 802.3 LAG (802.1AX) interfaces, VLAN sub-interfaces, Switch Virtual interfaces, and Pseudo-Wire Head-End interfaces. - file "interfaces-ethernet-like@2015-06-26.yang" - module interfaces-ethernet-like { - namespace "urn:ietf:params:xml:ns:yang:interfaces-ethernet-like"; + file "ietf-interfaces-ethernet-like@2016-07-07.yang" + module ietf-interfaces-ethernet-like { + namespace + "urn:ietf:params:xml:ns:yang:ietf-interfaces-ethernet-like"; + prefix ethlike; import ietf-interfaces { prefix if; } import ietf-yang-types { prefix yang; } import iana-if-type { prefix ianaift; } organization - "Cisco Systems, Inc. - Customer Service + "IETF NETMOD (NETCONF Data Modeling Language) Working Group"; - Postal: 170 W Tasman Drive - San Jose, CA 95134 + contact + "WG Web: + WG List: - Tel: +1 1800 553-NETS + WG Chair: Lou Berger + - E-mail: cs-yang@cisco.com"; + WG Chair: Kent Watsen + - contact - "Robert Wilton - rwilton@cisco.com"; + Editor: Robert Wilton + "; description "This module contains YANG definitions for configuration for 'Ethernet-like' interfaces. It is applicable to all interface types that use Ethernet framing and expose an Ethernet MAC layer, and includes such interfaces as physical Ethernet - interfaces, Ethernet LAG interfaces and VLAN sub-interfaces."; + interfaces, Ethernet LAG interfaces and VLAN sub-interfaces. + + Copyright (c) 2016 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 XXX; see the RFC + itself for full legal notices."; + + revision 2016-07-07 { + description + "Update module title and description text to IETF standard + text"; + + reference "Internet draft: draft-ietf-netmod-intf-ext-yang-01"; + } revision 2015-06-26 { description "Updated reference to new internet draft name."; reference "Internet draft: draft-wilton-netmod-intf-ext-yang-00"; } /* * Configuration parameters for Etherlike interfaces. @@ -1132,18 +1183,18 @@ Robert Wilton (editor) Cisco Systems Email: rwilton@cisco.com David Ball Cisco Systems Email: daviball@cisco.com Tapraj Singh - Juniper Networks + Cisco Systems - Email: tsingh@juniper.net + Email: tapsingh@juniper.net Selvakumar Sivaraj Juniper Networks Email: ssivaraj@juniper.net