draft-ietf-appsawg-media-type-suffix-regs-03.txt   draft-ietf-appsawg-media-type-suffix-regs-04.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 15, 2013 September 11, 2012 Expires: March 17, 2013 September 13, 2012
Additional Media Type Structured Syntax Suffixes Additional Media Type Structured Syntax Suffixes
draft-ietf-appsawg-media-type-suffix-regs-03 draft-ietf-appsawg-media-type-suffix-regs-04
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 15, 2013. This Internet-Draft will expire on March 17, 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 24 skipping to change at page 2, line 24
3.1. The +json Structured Syntax Suffix . . . . . . . . . . . . 4 3.1. The +json Structured Syntax Suffix . . . . . . . . . . . . 4
3.2. The +ber Structured Syntax Suffixes . . . . . . . . . . . 5 3.2. The +ber Structured Syntax Suffixes . . . . . . . . . . . 5
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 . . . . . . . . . . . . . . . . . . 13 6.2. Informative References . . . . . . . . . . . . . . . . . . 14
Appendix A. Change History . . . . . . . . . . . . . . . . . . . 13 Appendix A. Change History . . . . . . . . . . . . . . . . . . . 14
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . . 14 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . . 14
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
skipping to change at page 12, line 38 skipping to change at page 12, line 38
For cases not defined in +xml, then as For cases not defined in +xml, then as
specified in "xxx/yyy+xml". specified in "xxx/yyy+xml".
5. Security Considerations 5. Security Considerations
See the Security considerations sections found in the Message Type See the Security considerations sections found in the Message Type
Structured Syntax Suffix registration forms from Section 3.1 - Structured Syntax Suffix registration forms from Section 3.1 -
Section 3.5. Section 3.5.
When updating a +<suffix> registration care should be taken to review When updating a +<suffix> registration, care should be taken to
all previously registered xxx/yyy+<suffix> media types regarding 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.
in particular by introduction of new or changing generic fragment Because the generic fragment identifier processing rules take
identifier processing rules, as such rules take precedence over precedence over media-type-specific rules, introducing new or
media-type-specific rules and thus might break existing registrations changing existing definitions may break the existing registrations of
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
media type, care should be taken to review the generic fragment
identifier processing rules for the +<suffix> 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.
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
ITU-T X.690 | ISO/IEC 8825-1 (2008), ASN.1 encoding rules: ITU-T X.690 | ISO/IEC 8825-1 (2008), ASN.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
skipping to change at page 14, line 5 skipping to change at page 14, line 17
[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.
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
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
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.
Reworked fragment identifier wording some more. Reworked fragment identifier wording some more.
draft-ietf-appsawg-media-type-suffix-regs-01 Reordered the sections. draft-ietf-appsawg-media-type-suffix-regs-01 Reordered the sections.
Cleaned up some MUSTard. Cleaned up some MUSTard.
Fixed some references. Fixed some references.
Added encoding considerations. Added encoding considerations.
Reworked fragment identifier wording. Reworked fragment identifier wording.
 End of changes. 8 change blocks. 
12 lines changed or deleted 30 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/