rfc8819v4.txt		rfc8819.txt
	Internet Engineering Task Force (IETF) C. Hopps		Internet Engineering Task Force (IETF) C. Hopps
	Request for Comments: 8819 LabN Consulting, L.L.C.		Request for Comments: 8819 L. Berger
	Updates: 8407 L. Berger		Updates: 8407 LabN Consulting, L.L.C.
	Category: Standards Track LabN Consulting, LLC.		Category: Standards Track D. Bogdanovic
	ISSN: 2070-1721 D. Bogdanovic		ISSN: 2070-1721 Volta Networks
	Volta Networks
	December 2020		December 2020
	YANG Module Tags		YANG Module Tags
	Abstract		Abstract
	This document provides for the association of tags with YANG modules.		This document provides for the association of tags with YANG modules.
	The expectation is for such tags to be used to help classify and		The expectation is for such tags to be used to help classify and
	organize modules. A method for defining, reading, and writing		organize modules. A method for defining, reading, and writing
	modules tags is provided. Tags may be registered and assigned during		modules tags is provided. Tags may be registered and assigned during
	skipping to change at line 81 ¶		skipping to change at line 80 ¶
	7. IANA Considerations		7. IANA Considerations
	7.1. YANG Module Tag Prefixes Registry		7.1. YANG Module Tag Prefixes Registry
	7.2. IETF YANG Module Tags Registry		7.2. IETF YANG Module Tags Registry
	7.3. Updates to the IETF XML Registry		7.3. Updates to the IETF XML Registry
	7.4. Updates to the YANG Module Names Registry		7.4. Updates to the YANG Module Names Registry
	8. Security Considerations		8. Security Considerations
	9. References		9. References
	9.1. Normative References		9.1. Normative References
	9.2. Informative References		9.2. Informative References
	Appendix A. Examples		Appendix A. Examples
	Appendix B. Non-NMDA State Module.		Appendix B. Non-NMDA State Module
	Acknowledgements		Acknowledgements
	Authors' Addresses		Authors' Addresses
	1. Introduction		1. Introduction
	The use of tags for classification and organization is fairly		The use of tags for classification and organization is fairly
	ubiquitous not only within IETF protocols but in the internet itself		ubiquitous not only within IETF protocols but in the internet itself
	(e.g., "#hashtags"). One benefit of using tags for organization over		(e.g., "#hashtags"). One benefit of using tags for organization over
	a rigid structure is that it is more flexible and can more easily		a rigid structure is that it is more flexible and can more easily
	adapt over time as technologies evolve. Tags can be usefully		adapt over time as technologies evolve. Tags can be usefully
	skipping to change at line 249 ¶		skipping to change at line 248 ¶
	+--rw module-tags		+--rw module-tags
	+--rw module* [name]		+--rw module* [name]
	+--rw name yang:yang-identifier		+--rw name yang:yang-identifier
	+--rw tag* tag		+--rw tag* tag
	+--rw masked-tag* tag		+--rw masked-tag* tag
	Figure 1: YANG Module Tags Tree Diagram		Figure 1: YANG Module Tags Tree Diagram
	4.2. YANG Module		4.2. YANG Module
	<CODE BEGINS> file "ietf-module-tags@2020-08-05.yang"		<CODE BEGINS> file "ietf-module-tags@2020-12-22.yang"
	module ietf-module-tags {		module ietf-module-tags {
	yang-version 1.1;		yang-version 1.1;
	namespace "urn:ietf:params:xml:ns:yang:ietf-module-tags";		namespace "urn:ietf:params:xml:ns:yang:ietf-module-tags";
	prefix tags;		prefix tags;
	import ietf-yang-types {		import ietf-yang-types {
	prefix yang;		prefix yang;
	}		}
	organization		organization
	skipping to change at line 298 ¶		skipping to change at line 297 ¶
	This version of this YANG module is part of RFC 8819		This version of this YANG module is part of RFC 8819
	(https://www.rfc-editor.org/info/rfc8819); see the RFC itself		(https://www.rfc-editor.org/info/rfc8819); see the RFC itself
	for full legal notices.		for full legal notices.
	The key words 'MUST', 'MUST NOT', 'REQUIRED', 'SHALL', 'SHALL		The key words 'MUST', 'MUST NOT', 'REQUIRED', 'SHALL', 'SHALL
	NOT', 'SHOULD', 'SHOULD NOT', 'RECOMMENDED', 'NOT RECOMMENDED',		NOT', 'SHOULD', 'SHOULD NOT', 'RECOMMENDED', 'NOT RECOMMENDED',
	'MAY', and 'OPTIONAL' in this document are to be interpreted as		'MAY', and 'OPTIONAL' in this document are to be interpreted as
	described in BCP 14 (RFC 2119) (RFC 8174) when, and only when,		described in BCP 14 (RFC 2119) (RFC 8174) when, and only when,
	they appear in all capitals, as shown here.";		they appear in all capitals, as shown here.";
	revision 2020-08-05 {		revision 2020-12-22 {
	description		description
	"Initial revision.";		"Initial revision.";
	reference		reference
	"RFC 8819: YANG Module Tags";		"RFC 8819: YANG Module Tags";
	}		}
	typedef tag {		typedef tag {
	type string {		type string {
	length "1..max";		length "1..max";
	pattern '[\S ]+';		pattern '[\S ]+';
	skipping to change at line 678 ¶		skipping to change at line 677 ¶
	<t:tag>ietf:network-element-class</t:tag>		<t:tag>ietf:network-element-class</t:tag>
	<t:tag>ietf:protocol</t:tag>		<t:tag>ietf:protocol</t:tag>
	<t:tag>ietf:sdo-defined-class</t:tag>		<t:tag>ietf:sdo-defined-class</t:tag>
	<t:tag>ietf:system-management</t:tag>		<t:tag>ietf:system-management</t:tag>
	</t:module>		</t:module>
	</t:module-tags>		</t:module-tags>
	</ns0:data>		</ns0:data>
	Figure 3: Example NETCONF Query Output		Figure 3: Example NETCONF Query Output
	Appendix B. Non-NMDA State Module.		Appendix B. Non-NMDA State Module
	As per [RFC8407], the following is a non-NMDA module to support		As per [RFC8407], the following is a non-NMDA module to support
	viewing the operational state for non-NMDA compliant servers.		viewing the operational state for non-NMDA compliant servers.
	<CODE BEGINS> file "ietf-module-tags-state@2020-08-05.yang"		<CODE BEGINS> file "ietf-module-tags-state@2020-12-22.yang"
	module ietf-module-tags-state {		module ietf-module-tags-state {
	yang-version 1.1;		yang-version 1.1;
	namespace "urn:ietf:params:xml:ns:yang:ietf-module-tags-state";		namespace "urn:ietf:params:xml:ns:yang:ietf-module-tags-state";
	prefix tags-s;		prefix tags-s;
	import ietf-yang-types {		import ietf-yang-types {
	prefix yang;		prefix yang;
	}		}
	import ietf-module-tags {		import ietf-module-tags {
	prefix tags;		prefix tags;
	skipping to change at line 732 ¶		skipping to change at line 731 ¶
	without modification, is permitted pursuant to, and subject to		without modification, is permitted pursuant to, and subject to
	the license terms contained in, the Simplified BSD License set		the license terms contained in, the Simplified BSD License set
	forth in Section 4.c of the IETF Trust's Legal Provisions		forth in Section 4.c of the IETF Trust's Legal Provisions
	Relating to IETF Documents		Relating to IETF Documents
	(https://trustee.ietf.org/license-info).		(https://trustee.ietf.org/license-info).
	This version of this YANG module is part of RFC 8819		This version of this YANG module is part of RFC 8819
	(https://www.rfc-editor.org/info/rfc8819); see the RFC itself		(https://www.rfc-editor.org/info/rfc8819); see the RFC itself
	for full legal notices.";		for full legal notices.";
	revision 2020-08-05 {		revision 2020-12-22 {
	description		description
	"Initial revision.";		"Initial revision.";
	reference		reference
	"RFC 8819: YANG Module Tags";		"RFC 8819: YANG Module Tags";
	}		}
	container module-tags-state {		container module-tags-state {
	config false;		config false;
	status deprecated;		status deprecated;
	description		description
	skipping to change at line 796 ¶		skipping to change at line 795 ¶
	generating the non-NMDA module.		generating the non-NMDA module.
	Authors' Addresses		Authors' Addresses
	Christian Hopps		Christian Hopps
	LabN Consulting, L.L.C.		LabN Consulting, L.L.C.
	Email: chopps@chopps.org		Email: chopps@chopps.org
	Lou Berger		Lou Berger
	LabN Consulting, LLC.		LabN Consulting, L.L.C.
	Email: lberger@labn.net		Email: lberger@labn.net
	Dean Bogdanovic		Dean Bogdanovic
	Volta Networks		Volta Networks
	Email: ivandean@gmail.com		Email: ivandean@gmail.com
End of changes. 8 change blocks.
	12 lines changed or deleted		11 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/