draft-ietf-i2rs-rib-data-model-00.txt		draft-ietf-i2rs-rib-data-model-01.txt
	Network Working Group L. Wang		Network Working Group L. Wang
	Internet-Draft Huawei		Internet-Draft Huawei
	Intended status: Standards Track H. Ananthakrishnan		Intended status: Standards Track H. Ananthakrishnan
	Expires: October 5, 2015 Packet Design		Expires: April 1, 2016 Packet Design
	M. Chen		M. Chen
	Huawei		Huawei
	A. Dass		A. Dass
	S. Kini		S. Kini
	Ericsson		Ericsson
	N. Bahadur		N. Bahadur
	Bracket Computing		Bracket Computing
	April 03, 2015		September 29, 2015
	A YANG Data Model for Routing Information Base (RIB)		A YANG Data Model for Routing Information Base (RIB)
	draft-ietf-i2rs-rib-data-model-00		draft-ietf-i2rs-rib-data-model-01
	Abstract		Abstract
	This document defines a YANG data model for Routing Information Base		This document defines a YANG data model for Routing Information Base
	(RIB) that aligns with the I2RS RIB information model.		(RIB) that aligns with the I2RS RIB information model.
	Requirements Language		Requirements Language
	The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",		The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
	"SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this		"SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this
	skipping to change at page 1, line 45		skipping to change at page 1, line 45
	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 October 5, 2015.		This Internet-Draft will expire on April 1, 2016.
	Copyright Notice		Copyright Notice
	Copyright (c) 2015 IETF Trust and the persons identified as the		Copyright (c) 2015 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 37		skipping to change at page 2, line 37
	2.2. Routing Instance and Rib . . . . . . . . . . . . . . . . 6		2.2. Routing Instance and Rib . . . . . . . . . . . . . . . . 6
	2.3. Route . . . . . . . . . . . . . . . . . . . . . . . . . . 7		2.3. Route . . . . . . . . . . . . . . . . . . . . . . . . . . 7
	2.4. Nexthop . . . . . . . . . . . . . . . . . . . . . . . . . 8		2.4. Nexthop . . . . . . . . . . . . . . . . . . . . . . . . . 8
	2.5. Notifications . . . . . . . . . . . . . . . . . . . . . . 12		2.5. Notifications . . . . . . . . . . . . . . . . . . . . . . 12
	3. YANG Modules . . . . . . . . . . . . . . . . . . . . . . . . 14		3. YANG Modules . . . . . . . . . . . . . . . . . . . . . . . . 14
	4. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 37		4. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 37
	5. Security Considerations . . . . . . . . . . . . . . . . . . . 37		5. Security Considerations . . . . . . . . . . . . . . . . . . . 37
	6. References . . . . . . . . . . . . . . . . . . . . . . . . . 37		6. References . . . . . . . . . . . . . . . . . . . . . . . . . 37
	6.1. Normative References . . . . . . . . . . . . . . . . . . 37		6.1. Normative References . . . . . . . . . . . . . . . . . . 37
	6.2. Informative References . . . . . . . . . . . . . . . . . 37		6.2. Informative References . . . . . . . . . . . . . . . . . 37
	Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 37		Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 38
	1. Introduction		1. Introduction
	The Interface to the Routing System (I2RS)		The Interface to the Routing System (I2RS)
	[I-D.ietf-i2rs-architecture] provides read and write access to the		[I-D.ietf-i2rs-architecture] provides read and write access to the
	information and state within the routing process that exists inside		information and state within the routing process that exists inside
	the routing elements, this is achieved via the protocol message		the routing elements, this is achieved via the protocol message
	exchange between I2RS clients and I2RS agents associated with the		exchange between I2RS clients and I2RS agents associated with the
	routing system. One of the functions of I2RS is to read and write		routing system. One of the functions of I2RS is to read and write
	data of Routing Information Base (RIB).		data of Routing Information Base (RIB).
	skipping to change at page 14, line 20		skipping to change at page 14, line 20
	| +--:(interface-route)		| +--:(interface-route)
	| +--ro interface-identifier if:interface-ref		| +--ro interface-identifier if:interface-ref
	+--ro route-installed-state route-installed-state-def		+--ro route-installed-state route-installed-state-def
	+--ro route-state route-state-def		+--ro route-state route-state-def
	+--ro route-reason route-reason-def		+--ro route-reason route-reason-def
	Figure 7 Notifications		Figure 7 Notifications
	3. YANG Modules		3. YANG Modules
	//<code begins> file "i2rs rib@2015-03-09.yang"		<CODE BEGINS> file "i2rs rib@2015-04-03.yang"
	module i2rs-rib {		module i2rs-rib {
	namespace "urn:TBD1:params:xml:ns:yang:rt:i2rs:rib";		namespace "urn:TBD1:params:xml:ns:yang:rt:i2rs:rib";
	// replace with iana namespace when assigned		// replace with iana namespace when assigned
	prefix "i2rs-rib";		prefix "i2rs-rib";
	import ietf-inet-types {		import ietf-inet-types {
	prefix inet;		prefix inet;
	//rfc6991		//rfc6991
	}		}
	skipping to change at page 36, line 50		skipping to change at page 36, line 50
	mandatory true;		mandatory true;
	}		}
	leaf route-reason {		leaf route-reason {
	description		description
	"Need to be added.";		"Need to be added.";
	type route-reason-def;		type route-reason-def;
	mandatory true;		mandatory true;
	}		}
	}		}
	}		}
	// </code ends>
			<CODE ENDS>
	4. IANA Considerations		4. IANA Considerations
	TBD.		TBD.
	5. Security Considerations		5. Security Considerations
	This document introduces no new security threat and SHOULD follow the		This document introduces no new security threat and SHOULD follow the
	security requirements as stated in [I-D.ietf-i2rs-architecture].		security requirements as stated in [I-D.ietf-i2rs-architecture].
	6. References		6. References
	6.1. Normative References		6.1. Normative References
	[RFC2119] Bradner, S., "Key words for use in RFCs to Indicate		[RFC2119] Bradner, S., "Key words for use in RFCs to Indicate
	Requirement Levels", BCP 14, RFC 2119, March 1997.		Requirement Levels", BCP 14, RFC 2119,
			DOI 10.17487/RFC2119, March 1997,
			<http://www.rfc-editor.org/info/rfc2119>.
	6.2. Informative References		6.2. Informative References
	[I-D.ietf-i2rs-architecture]		[I-D.ietf-i2rs-architecture]
	Atlas, A., Halpern, J., Hares, S., Ward, D., and T.		Atlas, A., Halpern, J., Hares, S., Ward, D., and T.
	Nadeau, "An Architecture for the Interface to the Routing		Nadeau, "An Architecture for the Interface to the Routing
	System", draft-ietf-i2rs-architecture-09 (work in		System", draft-ietf-i2rs-architecture-09 (work in
	progress), March 2015.		progress), March 2015.
	[I-D.ietf-i2rs-rib-info-model]		[I-D.ietf-i2rs-rib-info-model]
	Bahadur, N., Folkes, R., Kini, S., and J. Medved, "Routing		Bahadur, N., Folkes, R., Kini, S., and J. Medved, "Routing
	Information Base Info Model", draft-ietf-i2rs-rib-info-		Information Base Info Model", draft-ietf-i2rs-rib-info-
	model-06 (work in progress), March 2015.		model-06 (work in progress), March 2015.
	[I-D.ietf-i2rs-usecase-reqs-summary]		[I-D.ietf-i2rs-usecase-reqs-summary]
	Hares, S. and M. Chen, "Summary of I2RS Use Case		Hares, S. and M. Chen, "Summary of I2RS Use Case
	Requirements", draft-ietf-i2rs-usecase-reqs-summary-00		Requirements", draft-ietf-i2rs-usecase-reqs-summary-01
	(work in progress), November 2014.		(work in progress), May 2015.
	[RFC6020] Bjorklund, M., "YANG - A Data Modeling Language for the		[RFC6020] Bjorklund, M., Ed., "YANG - A Data Modeling Language for
	Network Configuration Protocol (NETCONF)", RFC 6020,		the Network Configuration Protocol (NETCONF)", RFC 6020,
	October 2010.		DOI 10.17487/RFC6020, October 2010,
			<http://www.rfc-editor.org/info/rfc6020>.
	[RFC6021] Schoenwaelder, J., "Common YANG Data Types", RFC 6021,		[RFC6021] Schoenwaelder, J., Ed., "Common YANG Data Types",
	October 2010.		RFC 6021, DOI 10.17487/RFC6021, October 2010,
			<http://www.rfc-editor.org/info/rfc6021>.
	Authors' Addresses		Authors' Addresses
	Lixing Wang		Lixing Wang
	Huawei		Huawei
	Email: wang_little_star@sina.com		Email: wang_little_star@sina.com
	Hariharan Ananthakrishnan		Hariharan Ananthakrishnan
	Packet Design		Packet Design
	Email: hari@packetdesign.com		Email: hari@packetdesign.com
	Mach(Guoyi) Chen		Mach(Guoyi) Chen
	Huawei		Huawei
	Email: mach.chen@huawei.com		Email: mach.chen@huawei.com
End of changes. 12 change blocks.
	15 lines changed or deleted		21 lines changed or added
This html diff was produced by rfcdiff 1.42. The latest version is available from http://tools.ietf.org/tools/rfcdiff/