draft-ietf-netmod-interfaces-cfg-08.txt		draft-ietf-netmod-interfaces-cfg-09.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 November 15, 2012		Intended status: Standards Track February 6, 2013
	Expires: May 19, 2013		Expires: August 10, 2013
	A YANG Data Model for Interface Management		A YANG Data Model for Interface Management
	draft-ietf-netmod-interfaces-cfg-08		draft-ietf-netmod-interfaces-cfg-09
	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 May 19, 2013.		This Internet-Draft will expire on August 10, 2013.
	Copyright Notice		Copyright Notice
	Copyright (c) 2012 IETF Trust and the persons identified as the		Copyright (c) 2013 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
	carefully, as they describe your rights and restrictions with respect		carefully, as they describe your rights and restrictions with respect
	to this document. Code Components extracted from this document must		to this document. Code Components extracted from this document must
	include Simplified BSD License text as described in Section 4.e of		include Simplified BSD License text as described in Section 4.e of
	the Trust Legal Provisions and are provided without warranty as		the Trust Legal Provisions and are provided without warranty as
	skipping to change at page 7, line 23		skipping to change at page 7, line 23
	type if:interface-ref;		type if:interface-ref;
	must "/if:interfaces/if:interface[if:name = current()]"		must "/if:interfaces/if:interface[if:name = current()]"
	+ "/if:type = 'ethernetCsmacd'" {		+ "/if:type = 'ethernetCsmacd'" {
	description		description
	"The type of a slave interface must be ethernet";		"The type of a slave interface must be ethernet";
	}		}
	}		}
	// other bonding config params, failover times etc.		// other bonding config params, failover times etc.
	}		}
	There are two state data leaf-list nodes "higher-layer-if" and		Two state data leaf-lists, "higher-layer-if" and "lower-layer-if",
	"lower-layer-if" defined, that contains a read-only view of the		represent a read-only view of the interface layering hierarchy.
	interface layering hierarchy.
	4. Relationship to the IF-MIB		4. Relationship to the IF-MIB
	If the device implements IF-MIB [RFC2863], each entry in the		If the device implements IF-MIB [RFC2863], each entry in the
	"interface" list is typically mapped to one ifEntry. The "if-index"		"interface" list is typically mapped to one ifEntry. The "if-index"
	leaf contains the value of the corresponding ifEntry's ifIndex.		leaf contains the value of the corresponding ifEntry's ifIndex.
	In most cases, the "name" of an "interface" entry is mapped to		In most cases, the "name" of an "interface" entry is mapped to
	ifName. ifName is defined as an DisplayString [RFC2579] which uses a		ifName. ifName is defined as an DisplayString [RFC2579] which uses a
	7-bit ASCII character set. An implementation MAY restrict the		7-bit ASCII character set. An implementation MAY restrict the
	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-11-15.yang"		<CODE BEGINS> file "ietf-interfaces@2013-02-06.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-11-15 {		revision 2013-02-06 {
	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 13, line 23		skipping to change at page 13, line 23
	interface.";		interface.";
	reference		reference
	"RFC 2863: The Interfaces Group MIB - ifType";		"RFC 2863: The Interfaces Group MIB - ifType";
	}		}
	leaf location {		leaf location {
	type string;		type string;
	description		description
	"The device-specific location of the interface of a		"The device-specific location of the interface of a
	particular type. The format of the location string		particular type. The format of the location string
	depends on the interface type and the device.		depends on the interface type and the device. If a
			NETCONF server is sent a value that doesn't match this
			format, it MUST reply with an rpc-error with the error-tag
			'invalid-value'.
	If the interface's type represents a physical interface,		If the interface's type represents a physical interface,
	this leaf MUST be set.		this leaf MUST be set.
	When an interface entry is created, a server MAY		When an interface entry is created, a server MAY
	initialize the location leaf with a valid value, e.g., if		initialize the location leaf with a valid value, e.g., if
	it is possible to derive the location from the name of		it is possible to derive the location from the name of
	the interface.";		the interface.";
	}		}
	skipping to change at page 14, line 32		skipping to change at page 14, line 35
	"Status cannot be determined for some reason.";		"Status cannot be determined for some reason.";
	}		}
	enum dormant {		enum dormant {
	value 5;		value 5;
	description		description
	"Waiting for some external event.";		"Waiting for some external event.";
	}		}
	enum not-present {		enum not-present {
	value 6;		value 6;
	description		description
	"Some component is missing.";		"Some component (typically hardware) is missing.";
	}		}
	enum lower-layer-down {		enum lower-layer-down {
	value 7;		value 7;
	description		description
	"Down due to state of lower-layer interface(s).";		"Down due to state of lower-layer interface(s).";
	}		}
	}		}
	config false;		config false;
	description		description
	"The current operational state of the interface.		"The current operational state of the interface.
End of changes. 9 change blocks.
	12 lines changed or deleted		14 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/