rfc9694v5.txt		rfc9694.txt
	skipping to change at line 363 ¶		skipping to change at line 363 ¶
	usage of the type. Comments can be added or updated by the experts		usage of the type. Comments can be added or updated by the experts
	for subtype registrations under the respective top-level type, and by		for subtype registrations under the respective top-level type, and by
	IANA itself.		IANA itself.
	There should be at least one subtype, except for registrations that		There should be at least one subtype, except for registrations that
	are for demonstration purposes only (e.g. the example top-level		are for demonstration purposes only (e.g. the example top-level
	type).		type).
	4.2. Initialization of the Registry of Top-Level Media Types		4.2. Initialization of the Registry of Top-Level Media Types
	IANA has created the "Top-Level Media Types"		IANA has created the "Top-Level Media Types" registry
	(https://www.iana.org/assignments/top-level-media-types) registry and		(https://www.iana.org/assignments/top-level-media-types) and
	populated it with the values in Table 1. IANA also added a pointer		populated it with the values in Table 1. IANA also added a pointer
	to this registry from the "Media Types"		to this registry from the "Media Types" registry group
	(https://www.iana.org/assignments/media-types) registry group, and		(https://www.iana.org/assignments/media-types), and they added
	they added pointers to this document and to the "Top-Level Media		pointers to this document and to the "Top-Level Media Types" registry
	Types" registry in the application for a media type at		in the application for a media type at <https://www.iana.org/form/
	<https://www.iana.org/form/media-types>.		media-types>.
	For each top-level media type, the registry contains the name of the		For each top-level media type, the registry contains the name of the
	type, a pointer to the RFC defining the type, a pointer to IANA's		type, a pointer to the RFC defining the type, a pointer to IANA's
	registry of subtypes for that type, and a comment field.		registry of subtypes for that type, and a comment field.
	The initial state of the registry is as follows:		The initial state of the registry is as follows:
	+=============+==============+==============+===================+		+=============+==============+==============+===================+
	| Name | Defining RFC | Registry of | Comments |		| Name | Defining RFC | Registry of | Comments |
	| | | Subtypes | |		| | | Subtypes | |
End of changes. 2 change blocks.
	7 lines changed or deleted		7 lines changed or added
This html diff was produced by rfcdiff 1.48.