< draft-ietf-appsawg-media-type-regs-02.txt		draft-ietf-appsawg-media-type-regs-03.txt >
	Network Working Group N. Freed		Network Working Group N. Freed
	Internet-Draft Oracle		Internet-Draft Oracle
	Obsoletes: 4288 (if approved) J. Klensin		Obsoletes: 4288 (if approved) J. Klensin
	Expires: September 13, 2012		Expires: September 13, 2012
	T. Hansen		T. Hansen
	AT&T Laboratories		AT&T Laboratories
	March 12, 2012		March 12, 2012
	Media Type Specifications and Registration Procedures		Media Type Specifications and Registration Procedures
	draft-ietf-appsawg-media-type-regs-02		draft-ietf-appsawg-media-type-regs-03
	Abstract		Abstract
	This document defines procedures for the specification and		This document defines procedures for the specification and
	registration of media types for use in HTTP, MIME and other Internet		registration of media types for use in HTTP, MIME and other Internet
	protocols.		protocols.
	Status of this Memo		Status of this Memo
	This Internet-Draft is submitted in full conformance with the		This Internet-Draft is submitted in full conformance with the
	skipping to change at page 8, line 48 ¶		skipping to change at page 8, line 48 ¶
	This requirement applies regardless of the registration tree		This requirement applies regardless of the registration tree
	involved.		involved.
	4.2. Naming Requirements		4.2. Naming Requirements
	All registered media types MUST be assigned type and subtype names.		All registered media types MUST be assigned type and subtype names.
	The combination of these names serves to uniquely identify the media		The combination of these names serves to uniquely identify the media
	type, and the format of the subtype name identifies the registration		type, and the format of the subtype name identifies the registration
	tree. Both type and subtype names are case-insensitive.		tree. Both type and subtype names are case-insensitive.
	Type and subtype names beginning with "x-" are reserved for
	experimental use and MUST NOT be registered. This parallels the
	restriction on the x. tree, as discussed in Section 3.4.
	Type and subtype names MUST conform to the following ABNF:		Type and subtype names MUST conform to the following ABNF:
	type-name = restricted-name		type-name = restricted-name
	subtype-name = restricted-name		subtype-name = restricted-name
	restricted-name = 1*127restricted-name-chars		restricted-name = 1*127restricted-name-chars
	restricted-name-chars = ALPHA / DIGIT / "!" /		restricted-name-chars = ALPHA / DIGIT / "!" /
	"#" / "$" / "&" / "." /		"#" / "$" / "&" / "." /
	"+" / "-" / "^" / "_"		"+" / "-" / "^" / "_"
	skipping to change at page 29, line 5 ¶		skipping to change at page 29, line 5 ¶
	registration template.		registration template.
	o The specification requirements for personal tree registrations		o The specification requirements for personal tree registrations
	have been changed to be the same as those for the vendor tree.		have been changed to be the same as those for the vendor tree.
	The text has been changed to encourage (but not require)		The text has been changed to encourage (but not require)
	specification availability.		specification availability.
	o The definition of additional trees has been clarified to state		o The definition of additional trees has been clarified to state
	that an IETF Standards Action is required.		that an IETF Standards Action is required.
	o Widely deployed types with "X-" names can now be registered as an		o Widely deployed types with "x-" names can now be registered as an
	exception in the vendor tree.		exception in the vendor tree.
	o The reqiremeents on changes to registrations have been loosened so		o The reqiremeents on changes to registrations have been loosened so
	minor changes are easier to make.		minor changes are easier to make.
	o The registration process has been completely restructured so that		o The registration process has been completely restructured so that
	with the exception of IETF-generated types in the standards tree,		with the exception of IETF-generated types in the standards tree,
	all requests are procesed by IANA and not the IESG.		all requests are procesed by IANA and not the IESG.
	o A provisional registration process has been added for early		o A provisional registration process has been added for early
End of changes. 3 change blocks.
	6 lines changed or deleted		2 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/