draft-ietf-appsawg-media-type-suffix-regs-04.txt   draft-ietf-appsawg-media-type-suffix-regs-05.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: March 17, 2013 September 13, 2012 Expires: April 1, 2013 September 28, 2012
Additional Media Type Structured Syntax Suffixes Additional Media Type Structured Syntax Suffixes
draft-ietf-appsawg-media-type-suffix-regs-04 draft-ietf-appsawg-media-type-suffix-regs-05
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 March 17, 2013. This Internet-Draft will expire on April 1, 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 2, line 26 skipping to change at page 2, line 26
3.3. The +der Structured Syntax Suffixes . . . . . . . . . . . 6 3.3. The +der Structured Syntax Suffixes . . . . . . . . . . . 6
3.4. The +fastinfoset Structured Syntax Suffix . . . . . . . . 8 3.4. The +fastinfoset Structured Syntax Suffix . . . . . . . . 8
3.5. The +wbxml Structured Syntax Suffix . . . . . . . . . . . 9 3.5. The +wbxml Structured Syntax Suffix . . . . . . . . . . . 9
3.6. The +zip Structured Syntax Suffix . . . . . . . . . . . . 10 3.6. The +zip Structured Syntax Suffix . . . . . . . . . . . . 10
4. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 11 4. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 11
5. Security Considerations . . . . . . . . . . . . . . . . . . . 12 5. Security Considerations . . . . . . . . . . . . . . . . . . . 12
6. References . . . . . . . . . . . . . . . . . . . . . . . . . . 13 6. References . . . . . . . . . . . . . . . . . . . . . . . . . . 13
6.1. Normative References . . . . . . . . . . . . . . . . . . . 13 6.1. Normative References . . . . . . . . . . . . . . . . . . . 13
6.2. Informative References . . . . . . . . . . . . . . . . . . 14 6.2. Informative References . . . . . . . . . . . . . . . . . . 14
Appendix A. Change History . . . . . . . . . . . . . . . . . . . 14 Appendix A. Change History . . . . . . . . . . . . . . . . . . . 14
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . . 14 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . . 15
1. Introduction 1. Introduction
[RFC3023] created the +xml suffix convention that can be used when [RFC3023] created the +xml suffix convention that can be used when
defining names for media types whose representation uses XML defining names for media types whose representation uses XML
underneath. That is, they could have been successfully parsed as if underneath. That is, they could have been successfully parsed as if
the media type had been application/xml in addition to their being the media type had been application/xml in addition to their being
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
skipping to change at page 12, line 49 skipping to change at page 12, line 49
review all previously-registered xxx/yyy+<suffix> media types as to review all previously-registered xxx/yyy+<suffix> media types as to
whether they might be affected by the updated +<suffix> registration. whether they might be affected by the updated +<suffix> registration.
Because the generic fragment identifier processing rules take Because the generic fragment identifier processing rules take
precedence over media-type-specific rules, introducing new or precedence over media-type-specific rules, introducing new or
changing existing definitions may break the existing registrations of changing existing definitions may break the existing registrations of
specific media types, as well as particular implementations of specific media types, as well as particular implementations of
applications that process affected media types. Such changes can applications that process affected media types. Such changes can
introduce interoperability and security issues. introduce interoperability and security issues.
When updating the fragment identifier processing rules for a specific When updating the fragment identifier processing rules for a specific
media type, care should be taken to review the generic fragment xxx/yyy+<suffix> media type, care should be taken to review the
identifier processing rules for the +<suffix> registration and not generic fragment identifier processing rules for the +<suffix>
introduce any conflicts. Because the generic fragment identifier registration and not introduce any conflicts. Because the generic
processing rules take precedence over media-type-specific rules, such fragment identifier processing rules take precedence over media-type-
conflicting processing requirements should be ignored by an specific rules, such conflicting processing requirements should be
implementation, but such conflicts can introduce interoperability and ignored by an implementation, but such conflicts can introduce
security issues. 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. 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.
[ITU.X690.2008] [ITU.X690.2008]
International Telecommunications Union, "Recommendation International Telecommunications Union, "Recommendation
skipping to change at page 14, line 13 skipping to change at page 14, line 13
Types", RFC 3023, January 2001. Types", RFC 3023, January 2001.
6.2. Informative References 6.2. Informative References
[I-D.ietf-appsawg-media-type-regs] [I-D.ietf-appsawg-media-type-regs]
Freed, N., Klensin, J., and T. Hansen, "Media Type Freed, N., Klensin, J., and T. Hansen, "Media Type
Specifications and Registration Procedures", Specifications and Registration Procedures",
draft-ietf-appsawg-media-type-regs-14 (work in progress), draft-ietf-appsawg-media-type-regs-14 (work in progress),
June 2012. June 2012.
[FRAGID-BP]
Tennison, J., "Best Practices for Fragment Identifiers and
Media Type Definitions", July 2012,
<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-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
 End of changes. 6 change blocks. 
11 lines changed or deleted 20 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/