< draft-freed-charset-reg-02.txt		draft-freed-charset-reg-03.txt >
	Network Working Group Ned Freed, Innosoft		Network Working Group Ned Freed, Innosoft
	Internet Draft Jon Postel, ISI		Internet Draft Jon Postel, ISI
	<draft-freed-charset-reg-02.txt>		<draft-freed-charset-reg-03.txt>
	IANA Charset		IANA Charset
	Registration Procedures		Registration Procedures
	July 1997		September 1997
	Status of this Memo		Status of this Memo
	This document is an Internet-Draft. Internet-Drafts are		This document is an Internet-Draft. Internet-Drafts are
	working documents of the Internet Engineering Task Force		working documents of the Internet Engineering Task Force
	(IETF), its areas, and its working groups. Note that other		(IETF), its areas, and its working groups. Note that other
	groups may also distribute working documents as Internet-		groups may also distribute working documents as Internet-
	Drafts.		Drafts.
	Internet-Drafts are draft documents valid for a maximum of six		Internet-Drafts are draft documents valid for a maximum of six
	skipping to change at page 2, line ? ¶		skipping to change at page 2, line ? ¶
	issue, and is not dealt with by this registration procedure.		issue, and is not dealt with by this registration procedure.
	2. Definitions and Notation		2. Definitions and Notation
	The following sections define various terms used in this		The following sections define various terms used in this
	document.		document.
	2.1. Requirements Notation		2.1. Requirements Notation
	This document occasionally uses terms that appear in capital		This document occasionally uses terms that appear in capital
	letters. When the terms "MUST", "SHOULD", "MUST NOT", "SHOULD		letters. When the terms "MUST", "SHOULD", "MUST NOT", "SHOULD
	NOT", and "MAY" appear capitalized, they are being used to		NOT", and "MAY" appear capitalized, they are being used to
	indicate particular requirements of this specification. A		indicate particular requirements of this specification. A
	discussion of the meanings of these terms appears in [RFC-		discussion of the meanings of these terms appears in [RFC-
	2119].		2119].
	2.2. Character		2.2. Character
	A single graphic symbol.		A member of a set of elements used for the organisation,
			control, or representation of data.
	2.3. Charset		2.3. Charset
	The term "charset" (referred to as a "character set" in		The term "charset" (referred to as a "character set" in
	previous versions of this document) is used here to refer to a		previous versions of this document) is used here to refer to a
	method of converting a sequence of octets into a sequence of		method of converting a sequence of octets into a sequence of
	characters. This conversion may also optionally produce		characters. This conversion may also optionally produce
	additional control information such as directionality		additional control information such as directionality
	indicators.		indicators.
	skipping to change at page 4, line 10 ¶		skipping to change at page 4, line 10 ¶
	in MIME content types under the "text" top-level type must		in MIME content types under the "text" top-level type must
	conform to the restrictions on that type described in RFC		conform to the restrictions on that type described in RFC
	2045. All registered charsets MUST note whether or not they		2045. All registered charsets MUST note whether or not they
	are suitable for use in MIME.		are suitable for use in MIME.
	All charsets which are constructed as a composition of a CCS		All charsets which are constructed as a composition of a CCS
	and a CES MUST either include the CCS and CES they are based		and a CES MUST either include the CCS and CES they are based
	on in their registration or else cite a definition of their		on in their registration or else cite a definition of their
	CCS and CES that appears elsewhere.		CCS and CES that appears elsewhere.
	All registered charsets MUST be specified in an openly		All registered charsets MUST be specified in a stable, openly
	available specification. Registration of charsets whose		available specification. Registration of charsets whose
	specifications aren't readily available is forbidden.		specifications aren't stable and openly available is
			forbidden.
	3.2. New Charsets		3.2. New Charsets
	This registration mechanism is not intended to be a vehicle		This registration mechanism is not intended to be a vehicle
	for the definition of entirely new charsets. This is due to		for the definition of entirely new charsets. This is due to
	the fact that the registration process does NOT contain		the fact that the registration process does NOT contain
	adequate review mechanisims for such undertakings.		adequate review mechanisims for such undertakings.
	As such, only charsets defined by other processes and		As such, only charsets defined by other processes and
	standards bodies, or specific profiles of such charsets, are		standards bodies, or specific profiles of such charsets, are
	skipping to change at page 5, line 5 ¶		skipping to change at page 4, line 42 ¶
	be aliases for the primary name and use of the primary name is		be aliases for the primary name and use of the primary name is
	preferred over use of any of the aliases.		preferred over use of any of the aliases.
	Each assigned name MUST uniquely identify a single charset.		Each assigned name MUST uniquely identify a single charset.
	All charset names MUST be suitable for use as the value of a		All charset names MUST be suitable for use as the value of a
	MIME content type charset parameter and hence MUST conform to		MIME content type charset parameter and hence MUST conform to
	MIME parameter value syntax. This applies even if the specific		MIME parameter value syntax. This applies even if the specific
	charset being registered is not suitable for use with the		charset being registered is not suitable for use with the
	"text" media type.		"text" media type.
			Finally, charsets being registered for use with the "text"
			media type MUST have a primary name that conforms to the more
			restrictive syntax of the charset field in a MIME encoded-word
			[RFC-2047].
	3.4. Functionality Requirement		3.4. Functionality Requirement
	Charsets must function as actual charsets: Registration of		Charsets must function as actual charsets: Registration of
	things that are better thought of as a transfer encoding, as a		things that are better thought of as a transfer encoding, as a
	media type, or as a collection of separate entities of another		media type, or as a collection of separate entities of another
	type, is not allowed. For example, although HTML could		type, is not allowed. For example, although HTML could
	theoretically be thought of as a charset, it is really better		theoretically be thought of as a charset, it is really better
	thought of as a media type and as such it cannot be registered		thought of as a media type and as such it cannot be registered
	as a charset.		as a charset.
	skipping to change at page 7, line 19 ¶		skipping to change at page 7, line 19 ¶
	4.3. IANA Registration		4.3. IANA Registration
	Provided that the charset registration has either passed		Provided that the charset registration has either passed
	review or has been successfully appealed to the IESG, the IANA		review or has been successfully appealed to the IESG, the IANA
	will register the charset, assign a MIBenum value, and make		will register the charset, assign a MIBenum value, and make
	its registration available to the community.		its registration available to the community.
	5. Location of Registered Charset List		5. Location of Registered Charset List
	Charset registrations will be posted in the anonymous FTP file		Charset registrations will be posted in the anonymous FTP file
	"ftp://ftp.isi.edu/in-notes/iana/assignment/character-sets/"		"ftp://ftp.isi.edu/in-notes/iana/assignments/character-sets"
	and all registered charsets will be listed in the periodically		and all registered charsets will be listed in the periodically
	issued "Assigned Numbers" RFC [currently RFC-1700]. The		issued "Assigned Numbers" RFC [currently RFC-1700]. The
	description of the charset may also be published as an		description of the charset may also be published as an
	Informational RFC by sending it to "rfc-editor@isi.edu"		Informational RFC by sending it to "rfc-editor@isi.edu"
	(please follow the instructions to RFC authors [RFC-1543]).		(please follow the instructions to RFC authors [RFC-1543]).
	6. Registration Template		6. Registration Template
	To: ietf-charsets@innosoft.com		To: ietf-charsets@iana.org
	Subject: Registration of new charset		Subject: Registration of new charset
	Charset name(s):		Charset name(s):
	(All names must be suitable for use as the value of a		(All names must be suitable for use as the value of a
	MIME content-type parameter.)		MIME content-type parameter.)
	Published specification(s):		Published specification(s):
	(A specification for the charset must be		(A specification for the charset must be
	skipping to change at page 10, line 35 ¶		skipping to change at page 10, line 35 ¶
	email: Postel@ISI.EDU		email: Postel@ISI.EDU
	Appendix A -- IANA and RFC Editor To-Do List		Appendix A -- IANA and RFC Editor To-Do List
	VERY IMPORTANT NOTE: This appendix is intended to communicate		VERY IMPORTANT NOTE: This appendix is intended to communicate
	various editorial and procedural tasks the IANA and the RFC		various editorial and procedural tasks the IANA and the RFC
	Editor should undertake prior to publication of this document		Editor should undertake prior to publication of this document
	as an RFC. This appendix should NOT appear in the actual RFC		as an RFC. This appendix should NOT appear in the actual RFC
	version of this document!		version of this document!
	This document refers to the media types mailing list ietf-		This document refers to the character set mailing list ietf-
	charsets@iana.org. This alias needs to be established and		charsets@iana.org. This alias needs to be established and
	should initially point to ietf-charsets@innosoft.com.		should initially point to ietf-charsets@innosoft.com.
End of changes. 9 change blocks.
	10 lines changed or deleted		17 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/