--- 1/draft-ietf-appsawg-media-type-suffix-regs-04.txt 2012-09-28 20:14:11.369425770 +0200 +++ 2/draft-ietf-appsawg-media-type-suffix-regs-05.txt 2012-09-28 20:14:11.401425240 +0200 @@ -1,19 +1,19 @@ Network Working Group T. Hansen Internet-Draft AT&T Laboratories Updates: 3023 (if approved) A. Melnikov Intended status: BCP Isode Ltd -Expires: March 17, 2013 September 13, 2012 +Expires: April 1, 2013 September 28, 2012 Additional Media Type Structured Syntax Suffixes - draft-ietf-appsawg-media-type-suffix-regs-04 + draft-ietf-appsawg-media-type-suffix-regs-05 Abstract A content media type name sometimes includes partitioned meta- information distinguish by a Structured Syntax, to permit noting an attribute of the media as a suffix to the name. This document defines several Structured Syntax Suffixes for use with media type registrations. In particular, it defines and registers the "+json", "+ber", "+der", "+fastinfoset", "+wbxml" and "+zip" Structured Syntax Suffixes, and updates the "+xml" Message Type Structured Syntax @@ -27,21 +27,21 @@ Internet-Drafts are working documents of the Internet Engineering Task Force (IETF). Note that other groups may also distribute working documents as Internet-Drafts. The list of current Internet- Drafts is at http://datatracker.ietf.org/drafts/current/. Internet-Drafts are draft documents valid for a maximum of six months and may be updated, replaced, or obsoleted by other documents at any time. It is inappropriate to use Internet-Drafts as reference material or to cite them other than as "work in progress." - This Internet-Draft will expire on March 17, 2013. + This Internet-Draft will expire on April 1, 2013. Copyright Notice Copyright (c) 2012 IETF Trust and the persons identified as the document authors. All rights reserved. This document is subject to BCP 78 and the IETF Trust's Legal Provisions Relating to IETF Documents (http://trustee.ietf.org/license-info) in effect on the date of publication of this document. Please review these documents @@ -61,21 +61,21 @@ 3.3. The +der Structured Syntax Suffixes . . . . . . . . . . . 6 3.4. The +fastinfoset Structured Syntax Suffix . . . . . . . . 8 3.5. The +wbxml Structured Syntax Suffix . . . . . . . . . . . 9 3.6. The +zip Structured Syntax Suffix . . . . . . . . . . . . 10 4. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 11 5. Security Considerations . . . . . . . . . . . . . . . . . . . 12 6. References . . . . . . . . . . . . . . . . . . . . . . . . . . 13 6.1. Normative References . . . . . . . . . . . . . . . . . . . 13 6.2. Informative References . . . . . . . . . . . . . . . . . . 14 Appendix A. Change History . . . . . . . . . . . . . . . . . . . 14 - Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . . 14 + Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . . 15 1. Introduction [RFC3023] created the +xml suffix convention that can be used when defining names for media types whose representation uses XML underneath. That is, they could have been successfully parsed as if the media type had been 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] defines the Message Type Structured Syntax Suffixes registry to be used for such Structured @@ -518,27 +518,31 @@ review all previously-registered xxx/yyy+ media types as to whether they might be affected by the updated + registration. Because the generic fragment identifier processing rules take precedence over media-type-specific rules, introducing new or changing existing definitions may break the existing registrations of specific media types, as well as particular implementations of applications that process affected media types. Such changes can introduce interoperability and security issues. When updating the fragment identifier processing rules for a specific - media type, care should be taken to review the generic fragment - identifier processing rules for the + registration and not - introduce any conflicts. Because the generic fragment identifier - processing rules take precedence over media-type-specific rules, such - conflicting processing requirements should be ignored by an - implementation, but such conflicts can introduce interoperability and - security issues. + xxx/yyy+ media type, care should be taken to review the + generic fragment identifier processing rules for the + + registration and not introduce any conflicts. Because the generic + fragment identifier processing rules take precedence over media-type- + specific rules, such conflicting processing requirements should be + ignored by an implementation, but such conflicts can introduce + interoperability and security issues. + + Note that [FRAGID-BP] provides additional advices to designers of + fragment identifier rules for media type suffixes and specific media + types. 6. References 6.1. Normative References [RFC4627] Crockford, D., "The application/json Media Type for JavaScript Object Notation (JSON)", RFC 4627, July 2006. [ITU.X690.2008] International Telecommunications Union, "Recommendation @@ -572,20 +576,25 @@ Types", RFC 3023, January 2001. 6.2. Informative References [I-D.ietf-appsawg-media-type-regs] Freed, N., Klensin, J., and T. Hansen, "Media Type Specifications and Registration Procedures", draft-ietf-appsawg-media-type-regs-14 (work in progress), June 2012. + [FRAGID-BP] + Tennison, J., "Best Practices for Fragment Identifiers and + Media Type Definitions", July 2012, + . + Appendix A. Change History This section is to be removed before publication. draft-ietf-appsawg-media-type-suffix-regs-03 Added generic fragment idenfier rules to +ber/+der to make them consistant with other registrations. Added some warning about how adding/changing fragment identifier rules for a +suffix can affect fragment identifier processing rules for