rfc9907v7.txt		rfc9907.txt
	skipping to change at line 951 ¶		skipping to change at line 951 ¶
	For every normative "reference" statement that appears in a module		For every normative "reference" statement that appears in a module
	contained in the specification that identifies a separate document, a		contained in the specification that identifies a separate document, a
	corresponding normative reference to that document SHOULD appear in		corresponding normative reference to that document SHOULD appear in
	the Normative References section. The reference SHOULD correspond to		the Normative References section. The reference SHOULD correspond to
	the specific document version actually used within the specification.		the specific document version actually used within the specification.
	If the "reference" statement identifies an informative reference that		If the "reference" statement identifies an informative reference that
	identifies a separate document, a corresponding informative reference		identifies a separate document, a corresponding informative reference
	to that document MAY appear in the Informative References section.		to that document MAY appear in the Informative References section.
	Except the "import" and "revision" statements, note that it is
	acceptable to reference RFCs with their labels and without expanding
	their titles. An example of such use is as follows:
	leaf site-of-origin {
	type rt-types:route-origin;
	description
	"The Site of Origin attribute is encoded as a Route Origin
	Extended Community. It is meant to uniquely identify the
	set of routes learned from a site via a particular AC and
	is used to prevent routing loops.";
	reference
	"RFC 4364, Section 7";
	}
	leaf ipv6-site-of-origin {
	type rt-types:ipv6-route-origin;
	description
	"The IPv6 Site of Origin attribute is encoded as an IPv6
	Route Origin Extended Community. It is meant to uniquely
	identify the set of routes learned from a site.";
	reference
	"RFC 5701";
	}
	3.10. Validation Tools		3.10. Validation Tools
	All modules need to be validated before submission in an I-D. The		All modules need to be validated before submission in an I-D. The
	'pyang' YANG compiler is freely available from GitHub:		'pyang' YANG compiler is freely available from GitHub:
	<https://github.com/mbj4668/pyang>.		<https://github.com/mbj4668/pyang>.
	If the 'pyang' compiler is used to validate a normative module, then		If the 'pyang' compiler is used to validate a normative module, then
	the "--ietf" command-line option MUST be used to identify any IETF		the "--ietf" command-line option MUST be used to identify any IETF
	guideline issues.		guideline issues.
	skipping to change at line 3428 ¶		skipping to change at line 3404 ¶
	"IpSec tunnel mode encapsulation.";		"IpSec tunnel mode encapsulation.";
	reference		reference
	"RFC 4301: Security Architecture for the Internet Protocol";		"RFC 4301: Security Architecture for the Internet Protocol";
	}		}
	The templates in the following subsections are to be considered in		The templates in the following subsections are to be considered in
	addition to the required information that is provided in Section 3.8.		addition to the required information that is provided in Section 3.8.
	4.30.3.1. Template for IANA-Maintained YANG Modules with Identities		4.30.3.1. Template for IANA-Maintained YANG Modules with Identities
	This template ends with a section labeled "Optional".
	<BEGIN TEMPLATE TEXT>		<BEGIN TEMPLATE TEXT>
	This document defines the initial version of the IANA-maintained		This document defines the initial version of the IANA-maintained
	"iana-foo" YANG module. The most recent version of the YANG module		"iana-foo" YANG module. The most recent version of the YANG module
	is available from the "YANG Parameters" registry group		is available from the "YANG Parameters" registry group
	[IANA-YANG-PARAMETERS].		[IANA-YANG-PARAMETERS].
	IANA is requested to add this note to the registry:		IANA is requested to add this note to the registry:
	New values must not be directly added to the "iana-foo" YANG		New values must not be directly added to the "iana-foo" YANG
	skipping to change at line 3507 ¶		skipping to change at line 3481 ¶
	-- If a name in the IANA registry does not comply with the		-- If a name in the IANA registry does not comply with the
	-- YANG naming conventions, add details how IANA can generate		-- YANG naming conventions, add details how IANA can generate
	-- legal identifiers. For example, if the name begins with		-- legal identifiers. For example, if the name begins with
	-- a number, indicate a preference to spell out the number when		-- a number, indicate a preference to spell out the number when
	-- used as an identifier.		-- used as an identifier.
	<END TEMPLATE TEXT>		<END TEMPLATE TEXT>
	4.30.3.2. Template for IANA-Maintained YANG Modules with Enumerations		4.30.3.2. Template for IANA-Maintained YANG Modules with Enumerations
	This template ends with a section labeled "Optional".
	<BEGIN TEMPLATE TEXT>		<BEGIN TEMPLATE TEXT>
	This document defines the initial version of the IANA-maintained		This document defines the initial version of the IANA-maintained
	"iana-foo" YANG module. The most recent version of the YANG module		"iana-foo" YANG module. The most recent version of the YANG module
	is available from the "YANG Parameters" registry group		is available from the "YANG Parameters" registry group
	[IANA-YANG-PARAMETERS].		[IANA-YANG-PARAMETERS].
	IANA is requested to add this note to the registry:		IANA is requested to add this note to the registry:
	New values must not be directly added to the "iana-foo" YANG		New values must not be directly added to the "iana-foo" YANG
End of changes. 3 change blocks.
	28 lines changed or deleted		0 lines changed or added
This html diff was produced by rfcdiff 1.48.