draft-ietf-appsawg-media-type-suffix-regs-05.txt		draft-ietf-appsawg-media-type-suffix-regs-06.txt
	Network Working Group T. Hansen		Network Working Group T. Hansen
	Internet-Draft AT&T Laboratories		Internet-Draft AT&T Laboratories
	Updates: 3023 (if approved) A. Melnikov		Updates: 3023 (if approved) A. Melnikov
	Intended status: BCP Isode Ltd		Intended status: BCP Isode Ltd
	Expires: April 1, 2013 September 28, 2012		Expires: April 8, 2013 October 5, 2012
	Additional Media Type Structured Syntax Suffixes		Additional Media Type Structured Syntax Suffixes
	draft-ietf-appsawg-media-type-suffix-regs-05		draft-ietf-appsawg-media-type-suffix-regs-06
	Abstract		Abstract
	A content media type name sometimes includes partitioned meta-		A content media type name sometimes includes partitioned meta-
	information distinguish by a Structured Syntax, to permit noting an		information distinguish by a Structured Syntax, to permit noting an
	attribute of the media as a suffix to the name. This document		attribute of the media as a suffix to the name. This document
	defines several Structured Syntax Suffixes for use with media type		defines several Structured Syntax Suffixes for use with media type
	registrations. In particular, it defines and registers the "+json",		registrations. In particular, it defines and registers the "+json",
	"+ber", "+der", "+fastinfoset", "+wbxml" and "+zip" Structured Syntax		"+ber", "+der", "+fastinfoset", "+wbxml" and "+zip" Structured Syntax
	Suffixes, and updates the "+xml" Message Type Structured Syntax		Suffixes, and updates the "+xml" Message Type Structured Syntax
	skipping to change at page 1, line 38		skipping to change at page 1, line 38
	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 April 1, 2013.		This Internet-Draft will expire on April 8, 2013.
	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		Provisions Relating to IETF Documents
	(http://trustee.ietf.org/license-info) in effect on the date of		(http://trustee.ietf.org/license-info) in effect on the date of
	publication of this document. Please review these documents		publication of this document. Please review these documents
	skipping to change at page 3, line 21		skipping to change at page 3, line 21
	parsed as their media type that is using the +xml suffix.		parsed as their media type that is using the +xml suffix.
	[I-D.ietf-appsawg-media-type-regs] defines the Message Type		[I-D.ietf-appsawg-media-type-regs] defines the Message Type
	Structured Syntax Suffixes registry to be used for such Structured		Structured Syntax Suffixes registry to be used for such Structured
	Syntax Suffixes.		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 registrations, in particular "+json", "+der",		some media type registrations, in particular "+json", "+der",
	"+fastinfoset" and "+wbxml". This document defines and registers		"+fastinfoset" and "+wbxml". This document defines and registers
	these Structured Syntax Suffixes in the Structured Syntax Suffix		these Structured Syntax Suffixes in the Structured Syntax Suffix
	registry, along with "+ber" and "+zip". In addition, this document		registry, along with "+ber" and "+zip". In addition, this document
	updates the "+xml" Structured Syntax Suffix registration.		updates [RFC3023] to formally register the "+xml" Structured Syntax
			Suffix according to procedure defined in
			[I-D.ietf-appsawg-media-type-regs].
	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). [RFC Editor note: remove this		Group (apps-discuss@ietf.org). [RFC Editor note: remove this
	paragraph.]		paragraph.]
	The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",		The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
	"SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this		"SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this
	document are to be interpreted as described in [RFC2119].		document are to be interpreted as described in [RFC2119].
	2. When to Use these Structured Syntax Suffixes		2. When to Use these Structured Syntax Suffixes
	skipping to change at page 13, line 10		skipping to change at page 13, line 10
	When updating the fragment identifier processing rules for a specific		When updating the fragment identifier processing rules for a specific
	xxx/yyy+<suffix> media type, care should be taken to review the		xxx/yyy+<suffix> media type, care should be taken to review the
	generic fragment identifier processing rules for the +<suffix>		generic fragment identifier processing rules for the +<suffix>
	registration and not introduce any conflicts. Because the generic		registration and not introduce any conflicts. Because the generic
	fragment identifier processing rules take precedence over media-type-		fragment identifier processing rules take precedence over media-type-
	specific rules, such conflicting processing requirements should be		specific rules, such conflicting processing requirements should be
	ignored by an implementation, but such conflicts can introduce		ignored by an implementation, but such conflicts can introduce
	interoperability and security issues.		interoperability and security issues.
	Note that [FRAGID-BP] provides additional advices to designers of		Note that [FRAGID-BP] provides additional advice to designers of
	fragment identifier rules for media type suffixes and specific media		fragment identifier rules for media type suffixes and specific media
	types.		types.
	6. References		6. References
	6.1. Normative References		6.1. Normative References
	[RFC4627] 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.
	skipping to change at page 14, line 22		skipping to change at page 14, line 22
	[FRAGID-BP]		[FRAGID-BP]
	Tennison, J., "Best Practices for Fragment Identifiers and		Tennison, J., "Best Practices for Fragment Identifiers and
	Media Type Definitions", July 2012,		Media Type Definitions", July 2012,
	<http://www.w3.org/TR/fragid-best-practices/>.		<http://www.w3.org/TR/fragid-best-practices/>.
	Appendix A. Change History		Appendix A. Change History
	This section is to be removed before publication.		This section is to be removed before publication.
			draft-ietf-appsawg-media-type-suffix-regs-06 Clarified why this
			document updates RFC 3023.
			draft-ietf-appsawg-media-type-suffix-regs-05 Added an Informative
			reference to
			http://www.w3.org/TR/fragid-best-practices/.
			Minor editorial changes.
	draft-ietf-appsawg-media-type-suffix-regs-03 Added generic fragment		draft-ietf-appsawg-media-type-suffix-regs-03 Added generic fragment
	idenfier rules to +ber/+der to make them		idenfier rules to +ber/+der to make them
	consistant with other registrations.		consistant with other registrations.
	Added some warning about how adding/changing		Added some warning about how adding/changing
	fragment identifier rules for a +suffix can		fragment identifier rules for a +suffix can
	affect fragment identifier processing rules for		affect fragment identifier processing rules for
	previously registered xxx/yyy+suffix media types.		previously registered xxx/yyy+suffix media types.
	draft-ietf-appsawg-media-type-suffix-regs-02 Added BER/DER security		draft-ietf-appsawg-media-type-suffix-regs-02 Added BER/DER security
	considerations.		considerations.
End of changes. 6 change blocks.
	5 lines changed or deleted		15 lines changed or added
This html diff was produced by rfcdiff 1.41. The latest version is available from http://tools.ietf.org/tools/rfcdiff/