< draft-ietf-rtgwg-yang-rib-extend-09.txt		draft-ietf-rtgwg-yang-rib-extend-10.txt >
	Network Working Group A. Lindem		Network Working Group A. Lindem
	Internet-Draft Cisco Systems		Internet-Draft Cisco Systems
	Intended status: Standards Track Y. Qu		Intended status: Standards Track Y. Qu
	Expires: April 20, 2022 Futurewei		Expires: 20 October 2022 Futurewei
	October 17, 2021		18 April 2022
	RIB Extension YANG Data Model		RIB Extension YANG Data Model
	draft-ietf-rtgwg-yang-rib-extend-09		draft-ietf-rtgwg-yang-rib-extend-10
	Abstract		Abstract
	A Routing Information Base (RIB) is a list of routes and their		A Routing Information Base (RIB) is a list of routes and their
	corresponding administrative data and operational state.		corresponding administrative data and operational state.
	RFC 8349 defines the basic building blocks for RIB, and this model		RFC 8349 defines the basic building blocks for RIB, and this model
	augments it to support multiple next-hops (aka, paths) for each route		augments it to support multiple next-hops (aka, paths) for each route
	as well as additional attributes.		as well as additional attributes.
	skipping to change at page 1, line 36 ¶		skipping to change at page 1, line 36 ¶
	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 https://datatracker.ietf.org/drafts/current/.		Drafts is at https://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 April 20, 2022.		This Internet-Draft will expire on 20 October 2022.
	Copyright Notice		Copyright Notice
	Copyright (c) 2021 IETF Trust and the persons identified as the		Copyright (c) 2022 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 (https://trustee.ietf.org/
	(https://trustee.ietf.org/license-info) in effect on the date of		license-info) in effect on the date of publication of this document.
	publication of this document. Please review these documents		Please review these documents carefully, as they describe your rights
	carefully, as they describe your rights and restrictions with respect		and restrictions with respect to this document. Code Components
	to this document. Code Components extracted from this document must		extracted from this document must include Revised BSD License text as
	include Simplified BSD License text as described in Section 4.e of		described in Section 4.e of the Trust Legal Provisions and are
	the Trust Legal Provisions and are provided without warranty as		provided without warranty as described in the Revised BSD License.
	described in the Simplified BSD License.
	Table of Contents		Table of Contents
	1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 2		1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 2
	2. Terminology and Notation . . . . . . . . . . . . . . . . . . 3		2. Terminology and Notation . . . . . . . . . . . . . . . . . . 3
	2.1. Tree Diagrams . . . . . . . . . . . . . . . . . . . . . . 4		2.1. Tree Diagrams . . . . . . . . . . . . . . . . . . . . . . 4
	2.2. Prefixes in Data Node Names . . . . . . . . . . . . . . . 4		2.2. Prefixes in Data Node Names . . . . . . . . . . . . . . . 4
	3. Design of the Model . . . . . . . . . . . . . . . . . . . . . 4		3. Design of the Model . . . . . . . . . . . . . . . . . . . . . 4
	3.1. Tags and Preference . . . . . . . . . . . . . . . . . . . 4		3.1. Tags and Preference . . . . . . . . . . . . . . . . . . . 4
	3.2. Repair Path . . . . . . . . . . . . . . . . . . . . . . . 5		3.2. Repair Path . . . . . . . . . . . . . . . . . . . . . . . 5
	skipping to change at page 3, line 15 ¶		skipping to change at page 3, line 18 ¶
	2. Terminology and Notation		2. Terminology and Notation
	The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",		The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
	"SHOULD", "SHOULD NOT", "RECOMMENDED", "NOT RECOMMENDED", "MAY", and		"SHOULD", "SHOULD NOT", "RECOMMENDED", "NOT RECOMMENDED", "MAY", and
	"OPTIONAL" in this document are to be interpreted as described in BCP		"OPTIONAL" in this document are to be interpreted as described in BCP
	14 [RFC2119] [RFC8174] when, and only when, they appear in all		14 [RFC2119] [RFC8174] when, and only when, they appear in all
	capitals, as shown here.		capitals, as shown here.
	The following terms are defined in [RFC8342]:		The following terms are defined in [RFC8342]:
	o configuration		* configuration
	o system state		* system state
	o operational state		* operational state
	The following terms are defined in [RFC7950]:		The following terms are defined in [RFC7950]:
	o action		* action
	o augment		* augment
	o container		* container
	o container with presence		* container with presence
	o data model		* data model
	o data node		* data node
	o leaf		* leaf
	o list		* list
	o mandatory node		* mandatory node
	o module		* module
	o schema tree		* schema tree
	o RPC (Remote Procedure Call) operation		* RPC (Remote Procedure Call) operation
	The following terms are defined in [RFC8349] Section 5.2:		The following terms are defined in [RFC8349] Section 5.2:
	o RIB		* RIB
	2.1. Tree Diagrams		2.1. Tree Diagrams
	Tree diagrams used in this document follow the notation defined in		Tree diagrams used in this document follow the notation defined in
	[RFC8340].		[RFC8340].
	2.2. Prefixes in Data Node Names		2.2. Prefixes in Data Node Names
	In this document, names of data nodes, actions, and other data model		In this document, names of data nodes, actions, and other data model
	objects are often used without a prefix, as long as it is clear from		objects are often used without a prefix, as long as it is clear from
	the context in which YANG module each name is defined. Otherwise,		the context in which YANG module each name is defined. Otherwise,
	names are prefixed using the standard prefix associated with the		names are prefixed using the standard prefix associated with the
	corresponding YANG module, as shown in Table 1.		corresponding YANG module, as shown in Table 1.
	+--------+---------------------------+-----------+		+========+===========================+===========+
	| Prefix | YANG module | Reference |		| Prefix | YANG module | Reference |
	+--------+---------------------------+-----------+		+========+===========================+===========+
	| if | ietf-interfaces | [RFC8343] |		| if | ietf-interfaces | [RFC8343] |
	| | | |		+--------+---------------------------+-----------+
	| rt | ietf-routing | [RFC8349] |		| rt | ietf-routing | [RFC8349] |
	| | | |		+--------+---------------------------+-----------+
	| v4ur | ietf-ipv4-unicast-routing | [RFC8349] |		| v4ur | ietf-ipv4-unicast-routing | [RFC8349] |
	| | | |		+--------+---------------------------+-----------+
	| v6ur | ietf-ipv6-unicast-routing | [RFC8349] |		| v6ur | ietf-ipv6-unicast-routing | [RFC8349] |
	| | | |		+--------+---------------------------+-----------+
	| inet | ietf-inet-types | [RFC6991] |		| inet | ietf-inet-types | [RFC6991] |
	+--------+---------------------------+-----------+		+--------+---------------------------+-----------+
	Table 1: Prefixes and Corresponding YANG Modules		Table 1: Prefixes and Corresponding YANG Modules
	3. Design of the Model		3. Design of the Model
	The YANG module defined in this document augments the ietf-routing		The YANG module defined in this document augments the ietf-routing
	YANG model defined in [RFC8349], which provides a basis for routing		YANG model defined in [RFC8349], which provides a basis for routing
	system data model development. Together with YANG modules defined in		system data model development. Together with YANG modules defined in
	skipping to change at page 25, line 35 ¶		skipping to change at page 25, line 35 ¶
	Yoon for their helpful comments and suggestions.		Yoon for their helpful comments and suggestions.
	The authors wish to thank Tom Petch, Rob Wilton and Chris Hopps for		The authors wish to thank Tom Petch, Rob Wilton and Chris Hopps for
	their reviews and comments.		their reviews and comments.
	Authors' Addresses		Authors' Addresses
	Acee Lindem		Acee Lindem
	Cisco Systems		Cisco Systems
	301 Midenhall Way		301 Midenhall Way
	Cary, NC 27513		Cary, NC 27513
	USA		United States of America
			Email: acee@cisco.com
	EMail: acee@cisco.com
	Yingzhen Qu		Yingzhen Qu
	Futurewei		Futurewei
	2330 Central Expressway		2330 Central Expressway
	Santa Clara, CA 95050		Santa Clara, CA 95050
	USA		United States of America
			Email: yingzhen.qu@futurewei.com
	EMail: yingzhen.qu@futurewei.com
End of changes. 29 change blocks.
	39 lines changed or deleted		37 lines changed or added
This html diff was produced by rfcdiff 1.48. The latest version is available from http://tools.ietf.org/tools/rfcdiff/