< draft-hansen-media-type-suffix-regs-00.txt		draft-hansen-media-type-suffix-regs-01.txt >
	Network Working Group T. Hansen		Network Working Group T. Hansen
	Internet-Draft AT&T Laboratories		Internet-Draft AT&T Laboratories
	Intended status: Standards Track April 05, 2012		Intended status: Standards Track April 06, 2012
	Expires: October 05, 2012		Expires: October 06, 2012
	Additional Media Type Structured Syntax Suffixes		Additional Media Type Structured Syntax Suffixes
	draft-hansen-media-type-suffix-regs-00		draft-hansen-media-type-suffix-regs-01
	Abstract		Abstract
	This document defines several Structured Syntax Suffixes for use with		This document defines several Structured Syntax Suffixes for use with
	media type registrations. In particular, it defines and registers		media type registrations. In particular, it defines and registers
	the "+json", "+der", "+fastinfoset" and "+wbxml" Structured Syntax		the "+json", "+ber", "+der", "+fastinfoset" and "+wbxml" Structured
	Suffixes.		Syntax Suffixes.
	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
	provisions of BCP 78 and BCP 79.		provisions of BCP 78 and BCP 79.
	Internet-Drafts are working documents of the Internet Engineering		Internet-Drafts are working documents of the Internet Engineering
	Task Force (IETF). Note that other groups may also distribute		Task Force (IETF). Note that other groups may also distribute
	working documents as Internet-Drafts. The list of current Internet-		working documents as Internet-Drafts. The list of current Internet-
	Drafts is at http://datatracker.ietf.org/drafts/current/.		Drafts is at http://datatracker.ietf.org/drafts/current/.
	Internet-Drafts are draft documents valid for a maximum of six months		Internet-Drafts are draft documents valid for a maximum of six months
	and may be updated, replaced, or obsoleted by other documents at any		and may be updated, replaced, or obsoleted by other documents at any
	time. It is inappropriate to use Internet-Drafts as reference		time. It is inappropriate to use Internet-Drafts as reference
	material or to cite them other than as "work in progress."		material or to cite them other than as "work in progress."
	This Internet-Draft will expire on October 05, 2012.		This Internet-Draft will expire on October 06, 2012.
	Copyright Notice		Copyright Notice
	Copyright (c) 2012 IETF Trust and the persons identified as the		Copyright (c) 2012 IETF Trust and the persons identified as the
	document authors. All rights reserved.		document authors. All rights reserved.
	This document is subject to BCP 78 and the IETF Trust's Legal		This document is subject to BCP 78 and the IETF Trust's Legal
	Provisions Relating to IETF Documents (http://trustee.ietf.org/		Provisions Relating to IETF Documents (http://trustee.ietf.org/
	license-info) in effect on the date of publication of this document.		license-info) in effect on the date of publication of this document.
	Please review these documents carefully, as they describe your rights		Please review these documents carefully, as they describe your rights
	and restrictions with respect to this document. Code Components		and restrictions with respect to this document. Code Components
	extracted from this document must include Simplified BSD License text		extracted from this document must include Simplified BSD License text
	as described in Section 4.e of the Trust Legal Provisions and are		as described in Section 4.e of the Trust Legal Provisions and are
	provided without warranty as described in the Simplified BSD License.		provided without warranty as described in the Simplified BSD License.
	Table of Contents		Table of Contents
	1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 2		1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 2
	2. When to Use these Structured Syntax Suffixes . . . . . . . . . 2		2. When to Use these Structured Syntax Suffixes . . . . . . . . . 2
	3. The +json Structured Syntax Suffix . . . . . . . . . . . . . . 2		3. The +json Structured Syntax Suffix . . . . . . . . . . . . . . 2
	4. The +der Structured Syntax Suffix . . . . . . . . . . . . . . 3		4. The +ber and +der Structured Syntax Suffixes . . . . . . . . . 3
	5. The +fastinfoset Structured Syntax Suffix . . . . . . . . . . 3		5. The +fastinfoset Structured Syntax Suffix . . . . . . . . . . 4
	6. The +wbxml Structured Syntax Suffix . . . . . . . . . . . . . 3		6. The +wbxml Structured Syntax Suffix . . . . . . . . . . . . . 4
	7. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 4		7. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 5
	8. Security Considerations . . . . . . . . . . . . . . . . . . . 4		8. Security Considerations . . . . . . . . . . . . . . . . . . . 5
	9. References . . . . . . . . . . . . . . . . . . . . . . . . . . 4		9. References . . . . . . . . . . . . . . . . . . . . . . . . . . 5
	9.1. Normative References . . . . . . . . . . . . . . . . . . . 4		9.1. Normative References . . . . . . . . . . . . . . . . . . . 5
	9.2. Informative References . . . . . . . . . . . . . . . . . . 5		9.2. Informative References . . . . . . . . . . . . . . . . . . 6
	Author's Address . . . . . . . . . . . . . . . . . . . . . . . . . 5		Author's Address . . . . . . . . . . . . . . . . . . . . . . . . . 6
	1. Introduction		1. Introduction
	[RFC3023] created the +xml suffix convention that may be used by		[RFC3023] created the +xml suffix convention that may be used by
	media types whose representation uses XML underneath, that is, they		media types whose representation uses XML underneath, that is, they
	could have been successfully parsed as if the media type had been		could have been successfully parsed as if the media type had been
	application/xml in addition to their being parsed as their media type		application/xml in addition to their being parsed as their media type
	that is using the +xml suffix. [I-D.ietf-appsawg-media-type-regs]		that is using the +xml suffix. [I-D.ietf-appsawg-media-type-regs]
	defines a registry to be used for future Structured Syntax Suffixes.		defines a registry to be used for future Structured Syntax Suffixes.
	A variety of Structured Syntax Suffixes have already been used in		A variety of Structured Syntax Suffixes have already been used in
	some Media Type registration, in particular "+json", "+der",		some Media Type registration, in particular "+json", "+der",
	"+fastinfoset" and "+wbxml". This document defines and registers		"+fastinfoset" and "+wbxml". This document defines and registers
	these four Structured Syntax Suffixes in the Structured Syntax Suffix		these Structured Syntax Suffixes in the Structured Syntax Suffix
	registry.		registry, along with "+ber".
	Discussion of this document should occur in the Apps Area Working		Discussion of this document should occur in the Apps Area Working
	Group (apps-discuss@ietf.org).		Group (apps-discuss@ietf.org).
	2. When to Use these Structured Syntax Suffixes		2. When to Use these Structured Syntax Suffixes
	Each of the Structured Syntax Suffixes defined in this document are		Each of the Structured Syntax Suffixes defined in this document are
	appropriate for use when the media type identifies the semantics of		appropriate for use when the media type identifies the semantics of
	the protocol payload. That is, knowing the semantics of the specific		the protocol payload. That is, knowing the semantics of the specific
	media type provides for more specific processing of the content than		media type provides for more specific processing of the content than
	skipping to change at page 2, line 48 ¶		skipping to change at page 2, line 48 ¶
	At the same time, using the suffix provides receivers of the media		At the same time, using the suffix provides receivers of the media
	types to do generic processing of the underyling representation in		types to do generic processing of the underyling representation in
	cases where they do not need to handle specially the specific		cases where they do not need to handle specially the specific
	semantics of the exact media type.		semantics of the exact media type.
	3. The +json Structured Syntax Suffix		3. The +json Structured Syntax Suffix
	[RFC4627] defines the "application/json" media type. The suffix		[RFC4627] defines the "application/json" media type. The suffix
	"+json" may be used with any media type whose representation follows		"+json" may be used with any media type whose representation follows
	that established for "application/json". The Structured Syntax		that established for "application/json". The Message Type Structured
	Suffix registration form follows:		Syntax Suffix registration form follows:
	Name JavaScript Object Notation (JSON)		Name JavaScript Object Notation (JSON)
	+suffix +json		+suffix +json
	References [RFC4627]		References [RFC4627]
	Encoding considerations Per [RFC4627], JSON may be represented using		Encoding considerations Per [RFC4627], JSON may be represented using
	UTF-8, UTF-16, or UTF-32. When JSON is written		UTF-8, UTF-16, or UTF-32. When JSON is written
	in UTF-8, JSON is 8bit compatible. When JSON is		in UTF-8, JSON is 8bit compatible. When JSON is
	written in UTF-16 or UTF-32, JSON is binary.		written in UTF-16 or UTF-32, JSON is binary.
	Interoperability considerations n/a		Interoperability considerations n/a
	Security considerations See [RFC4627]		Security considerations See [RFC4627]
	Contact Apps Area Working Group (apps-discuss@ietf.org)		Contact Apps Area Working Group (apps-discuss@ietf.org)
	Author/Change controller The Apps Area Working Group has change		Author/Change controller The Apps Area Working Group has change
	control over this registration.		control over this registration.
	4. The +der Structured Syntax Suffix		4. The +ber and +der Structured Syntax Suffixes
	The CCITT defined the Distinguished Encoding Rules (DER) message		The CCITT defined the Basic Encoding Rules (BER) and Distinguished
	transfer syntax in [CCITT.X690.2002]. The suffix "+der" may be used		Encoding Rules (DER) message transfer syntaxes in [CCITT.X690.2002].
	with any media type whose representation follows the DER message		The suffix "+ber" may be used with any media type whose
	transfer syntax. The Structured Syntax Suffix registration form		representation follows the BER message transfer syntax. The suffix
	follows:		"+der" may be used with any media type whose representation follows
			the DER message transfer syntax. The Message Type Structured Syntax
			Suffix registration forms follows:
			Name Basic Encoding Rules (BER) message transfer
			syntax
			+suffix +ber
			References [CCITT.X690.2002]
			Encoding considerations BER is a binary encoding.
			Interoperability considerations n/a
			Security considerations There are no security considerations inherent
			in BER. Each individual media type registered
			with a +ber suffix may have additional security
			considerations.
			Contact Apps Area Working Group (apps-discuss@ietf.org)
			Author/Change controller The Apps Area Working Group has change
			control over this registration.
	Name Distinguished Encoding Rules (DER) message		Name Distinguished Encoding Rules (DER) message
	transfer syntax		transfer syntax
	+suffix +der		+suffix +der
	References [CCITT.X690.2002]		References [CCITT.X690.2002]
	Encoding considerations DER is a binary encoding.		Encoding considerations DER is a binary encoding.
	Interoperability considerations n/a		Interoperability considerations n/a
	Security considerations There are no security considerations inherent		Security considerations There are no security considerations inherent
	in DER. Each individual media type registered		in DER. Each individual media type registered
	with a +der suffix may have additional security		with a +der suffix may have additional security
	considerations.		considerations.
	Contact Apps Area Working Group (apps-discuss@ietf.org)		Contact Apps Area Working Group (apps-discuss@ietf.org)
	Author/Change controller The Apps Area Working Group has change		Author/Change controller The Apps Area Working Group has change
	control over this registration.		control over this registration.
	5. The +fastinfoset Structured Syntax Suffix		5. The +fastinfoset Structured Syntax Suffix
	The ITU-T and ISO have defined the Fast Infoset document format as a		The ITU-T and ISO have defined the Fast Infoset document format as a
	binary representation of the XML Information Set in [ITU.X891.2005]		binary representation of the XML Information Set in [ITU.X891.2005]
	and [ISO.IEC.24824-1.2007]. These documents further define the		and [ISO.IEC.24824-1.2007]. These documents further define the
	"application/fastinfoset" media type. The suffix "+fastinfoset" may		"application/fastinfoset" media type. The suffix "+fastinfoset" may
	be used with any media type whose representation follows that		be used with any media type whose representation follows that
	established for "application/fastinfoset". The Structured Syntax		established for "application/fastinfoset". The Message Type
	Suffix registration form follows:		Structured Syntax Suffix registration form follows:
	Name Fast Infoset document format		Name Fast Infoset document format
	+suffix +infoset		+suffix +infoset
	References [ITU.X891.2005] and [ISO.IEC.24824-1.2007]		References [ITU.X891.2005] and [ISO.IEC.24824-1.2007]
	Encoding considerations Fast Infoset is a binary encoding. The		Encoding considerations Fast Infoset is a binary encoding. The
	binary, quoted-printable and base64 content-		binary, quoted-printable and base64 content-
	transfer-encodings are suitable for use with Fast		transfer-encodings are suitable for use with Fast
	Infoset.		Infoset.
	Interoperability considerations n/a		Interoperability considerations n/a
	Security considerations There are no security considerations inherent		Security considerations There are no security considerations inherent
	in Fast Infoset. Each individual media type		in Fast Infoset. Each individual media type
	registered with a +der suffix may have additional		registered with a +der suffix may have additional
	security considerations.		security considerations.
	Contact Apps Area Working Group (apps-discuss@ietf.org)		Contact Apps Area Working Group (apps-discuss@ietf.org)
	Author/Change controller The Apps Area Working Group has change		Author/Change controller The Apps Area Working Group has change
	control over this registration.		control over this registration.
	6. The +wbxml Structured Syntax Suffix		6. The +wbxml Structured Syntax Suffix
	The WAP Forum has defined the WAP Binary XML (WBXML) document format		The WAP Forum has defined the WAP Binary XML (WBXML) document format
	as a binary representation of XML in [WBXML]. This document further		as a binary representation of XML in [WBXML]. This document further
	defines the "application/vnd.wap.wbxml" media type. The suffix		defines the "application/vnd.wap.wbxml" media type. The suffix
	"+wbxml" may be used with any media type whose representation follows		"+wbxml" may be used with any media type whose representation follows
	that established for "application/vnd.wap.wbxml". The Structured		that established for "application/vnd.wap.wbxml". The Message Type
	Syntax Suffix registration form follows:		Structured Syntax Suffix registration form follows:
	Name WAP Binary XML (WBXML) document format		Name WAP Binary XML (WBXML) document format
	+suffix +wbxml		+suffix +wbxml
	References [WBXML]		References [WBXML]
	Encoding considerations WBXML is a binary encoding.		Encoding considerations WBXML is a binary encoding.
	Interoperability considerations n/a		Interoperability considerations n/a
	Security considerations There are no security considerations inherent		Security considerations There are no security considerations inherent
	in WBXML. Each individual media type registered		in WBXML. Each individual media type registered
	with a +der suffix may have additional security		with a +der suffix may have additional security
	considerations.		considerations.
	Contact Apps Area Working Group (apps-discuss@ietf.org)		Contact Apps Area Working Group (apps-discuss@ietf.org)
	Author/Change controller The Apps Area Working Group has change		Author/Change controller The Apps Area Working Group has change
	control over this registration.		control over this registration.
	7. IANA Considerations		7. IANA Considerations
	See the Structured Syntax Suffix registration forms in sections 2-5.		See the Message Type Structured Syntax Suffix registration forms in
			Section 3 - Section 6.
	8. Security Considerations		8. Security Considerations
	See the Security considerations sections found in the Structured		See the Security considerations sections found in the Message Type
	Syntax Suffix registration forms from sections 2-5.		Structured Syntax Suffix registration forms from Section 3 - Section
			6.
	9. References		9. References
	9.1. Normative References		9.1. Normative References
	[1] Crockford, D., "The application/json Media Type for		[RFC4627] Crockford, D., "The application/json Media Type for
	JavaScript Object Notation (JSON)", RFC 4627, July 2006.		JavaScript Object Notation (JSON)", RFC 4627, July 2006.
	[2] International International Telephone and Telegraph		[CCITT.X690.2002]
			International International Telephone and Telegraph
	Consultative Committee, "AASN.1 encoding rules:		Consultative Committee, "AASN.1 encoding rules:
	Specification of basic encoding Rules (BER), Canonical		Specification of basic encoding Rules (BER), Canonical
	encoding rules (CER) and Distinguished encoding rules		encoding rules (CER) and Distinguished encoding rules
	(DER)", CCITT Recommendation X.680, July 2002.		(DER)", CCITT Recommendation X.680, July 2002.
	[3] International Telecommunications Union, "Information		[ITU.X891.2005]
			International Telecommunications Union, "Information
	Technology - Generic applications of ASN.1: Fast infoset",		Technology - Generic applications of ASN.1: Fast infoset",
	ITU-T Recommendation X.891, May 2005.		ITU-T Recommendation X.891, May 2005.
	[4] International Organization for Standardization,		[ISO.IEC.24824-1.2007]
			International Organization for Standardization,
	"Information Technology - Generic applications of ASN.1:		"Information Technology - Generic applications of ASN.1:
	Fast infoset", ISO Standard 24824-1, May 2007.		Fast infoset", ISO Standard 24824-1, May 2007.
	[5] Open Mobile Alliance, "Binary XML Content Format		[WBXML] Open Mobile Alliance, "Binary XML Content Format
	Specification", OMA Wireless Access Protocol		Specification", OMA Wireless Access Protocol
	WAP-192-WBXML-20010725-a, July 2001.		WAP-192-WBXML-20010725-a, July 2001.
	9.2. Informative References		9.2. Informative References
	[1] Murata, M., St. Laurent, S. and D. Kohn, "XML Media		[RFC3023] Murata, M., St. Laurent, S. and D. Kohn, "XML Media
	Types", RFC 3023, January 2001.		Types", RFC 3023, January 2001.
	[2] Freed, N., Klensin, J. and T. Hansen, "Media Type		[I-D.ietf-appsawg-media-type-regs]
			Freed, N., Klensin, J. and T. Hansen, "Media Type
	Specifications and Registration Procedures", Internet-		Specifications and Registration Procedures", Internet-
	Draft draft-ietf-appsawg-media-type-regs-04, April 2012.		Draft draft-ietf-appsawg-media-type-regs-04, April 2012.
	Author's Address		Author's Address
	Tony Hansen		Tony Hansen
	AT&T Laboratories		AT&T Laboratories
	200 Laurel Ave. South		200 Laurel Ave. South
	Middletown, NJ 07748		Middletown, NJ 07748
	USA		USA
End of changes. 48 change blocks.
	39 lines changed or deleted		96 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/