rfc9758v2.txt		rfc9758.txt
	skipping to change at line 451 ¶		skipping to change at line 451 ¶
	represented by a scheme identifier and a scheme-specific part. The		represented by a scheme identifier and a scheme-specific part. The
	scheme identifier is ipn, and the scheme-specific parts are		scheme identifier is ipn, and the scheme-specific parts are
	represented as a sequence of numeric components separated with the		represented as a sequence of numeric components separated with the
	'.' character. A formal definition is provided below (see		'.' character. A formal definition is provided below (see
	Section 4.1) and can be informally considered as:		Section 4.1) and can be informally considered as:
	ipn:[<allocator-identifier>.]<node-number>.<service-number>		ipn:[<allocator-identifier>.]<node-number>.<service-number>
	To keep the text representation concise, the following rules apply:		To keep the text representation concise, the following rules apply:
	1. All leading 0 characters MUST be omitted. A single '0' is valid.		1. All leading '0' characters MUST be omitted. A single '0' is
			valid.
	2. If the Allocator Identifier is zero (0), then the <allocator-		2. If the Allocator Identifier is zero (0), then the <allocator-
	identifier> and '.' MAY be omitted.		identifier> and '.' MAY be omitted.
	3. If the Allocator Identifier is zero (0), and the Node Number is		3. If the Allocator Identifier is zero (0), and the Node Number is
	2^(32-1) (i.e., the URI is a LocalNode ipn URI (Section 3.4.2)),		2^(32-1) (i.e., the URI is a LocalNode ipn URI (Section 3.4.2)),
	then the character '!' SHOULD be used instead of the digits		then the character '!' SHOULD be used instead of the digits
	4294967295, although both forms are valid encodings.		4294967295, although both forms are valid encodings.
	Examples of the textual representation of ipn URIs can be found in		Examples of the textual representation of ipn URIs can be found in
	skipping to change at line 1134 ¶		skipping to change at line 1135 ¶
	+---------------------+-------------------------------+		+---------------------+-------------------------------+
	| >= 2^32 | Reserved for future expansion |		| >= 2^32 | Reserved for future expansion |
	+---------------------+-------------------------------+		+---------------------+-------------------------------+
	Table 6: Registration Procedures for the 'ipn'		Table 6: Registration Procedures for the 'ipn'
	Scheme URI Well-Known Service Numbers for BPv7		Scheme URI Well-Known Service Numbers for BPv7
	Registry		Registry
	The initial values in the registry are:		The initial values in the registry are:
	+=====================+====================+===================+		+================+=============================+===================+
	| Value | Description | Reference |		| Value | Description | Reference |
	+=====================+====================+===================+		+================+=============================+===================+
	| 0 | The Administrative | [RFC9171] and RFC |		| 0 | The Administrative Endpoint | [RFC9171] and RFC |
	| | Endpoint | 9758, Section 5.7 |		| | | 9758, Section 5.7 |
	+---------------------+--------------------+-------------------+		+----------------+-----------------------------+-------------------+
	| 1..27 | Reserved for | RFC 9758 |		| 0xEEE0..0xEEEF | Example Range | RFC 9758 |
	| | Private Use | |		+----------------+-----------------------------+-------------------+
	+---------------------+--------------------+-------------------+
	| 0x0100..0x7FFF | Reserved for | RFC 9758 |
	| | Private Use | |
	+---------------------+--------------------+-------------------+
	| 0xEEE0..0xEEEF | Example Range | RFC 9758 |
	+---------------------+--------------------+-------------------+
	| 0x10000..0xFFFFFFFF | Reserved for | RFC 9758 |
	| | Private Use | |
	+---------------------+--------------------+-------------------+
	Table 7: Initial Values in the 'ipn' Scheme URI Well-Known		Table 7: Initial Values in the 'ipn' Scheme URI Well-Known
	Service Numbers for BPv7 Registry		Service Numbers for BPv7 Registry
	The "Example Range" is assigned for use in examples in documentation		The "Example Range" is assigned for use in examples in documentation
	and sample code.		and sample code.
	9.3.1. Guidance for Designated Experts		9.3.1. Guidance for Designated Experts
	This registry is intended to record the default Service Numbers for		This registry is intended to record the default Service Numbers for
End of changes. 2 change blocks.
	18 lines changed or deleted		10 lines changed or added
This html diff was produced by rfcdiff 1.48.