September 2006 - Ietf-types

Preliminary Community Review: text/json
by Douglas Crockford 15 Apr '07

15 Apr '07

This is notice of a potential media type registration. The details may be found here: http://www.ietf.org/internet-drafts/draft-crockford-jsonorg-json-02.txt

10 11

Request for review of 9 MIME type for 3GPP SA4
by Magnus Westerlund 29 Mar '07

29 Mar '07

Hi, attached is a word document with a proposal for 9 MIME type that will go into the 3GPP Technical Specification 26.346 and when present in that be requested to registered. Most of these media types are for XML formats, although not all of them. Please review them, comments received within a week can be directly addressed at the 3GPP SA4 meeting. TS 26.346 can in its latest form be fetched here: http://www.3gpp.org/ftp/Specs/archive/26_series/26.346/26346-610.zip However some of the references in the chapter relate to text that are being specified and added. They are available in the following document: http://www.3gpp.org/ftp/tsg_sa/WG4_CODEC/TSGS4_36/Docs/S4-050514.zip Thanks Magnus Westerlund Multimedia Technologies, Ericsson Research EAB/TVA/A ---------------------------------------------------------------------- Ericsson AB | Phone +46 8 4048287 Torshamsgatan 23 | Fax +46 8 7575550 S-164 80 Stockholm, Sweden | mailto: magnus.westerlund(a)ericsson.com

3 8

Request to review Media Type */rtp-enc-aescm128 for 3GPP
by Magnus Westerlund 29 Mar '07

29 Mar '07

Hi, The following Media Type was discussed on the list at the end of 2004. Time to finally register it. I intend to request IESG to approve registration following the SDO rules on the 6th of October. So if someone has strong objections against this speak up before then. The filled in registration template is from 3GPP TS 26.234 V.6.8.0: http://www.3gpp.org/ftp/Specs/archive/26_series/26.234/26234-680.zip K.1.4.1 MIME type definition MIME media type name: audio, video, text MIME subtype name: rtp-enc-aescm128 Required parameters: opt: The payload type number of the payload type contained in the encrypted payload. An integer value between 0-127. rate: The timestamp rate of this payload type, which shall be the same as that of the original payload type. This is an integer value between 1 and 2^32. ContentID: The OMA DRM content ID [75] used to identify the content when establishing a crypto context. The value is an RFC 2396 [60] URI, which shall be quoted using <">. RightsIssuerURL: The right issuer URL as defined by OMA DRM [75]. The value is an URI in accordance with RFC 2396 [60], which shall be quoted using <">. IVnonce: The value of this parameter is the nonce that forms the IV as specified by the crypto transform, encoded using Base 64 [69]. Optional parameters: SelectiveEncryption: Indicates if this stream is selectively encrypted. Allowed values are 0 (false) and 1 (true). If not present, selective encryption shall not be used. Please note that unless this indicator is integrity protected, it fulfills no purpose. Encoding considerations: This type is only defined for transfer via RTP (RFC 3550). Security considerations: See considerations raised in RTP RFC 3550 [9] and any applicable profile like RFC 3551 [10] or RFC 3711 [72]. Further see 3GPP TS 26.234, Release 6, Annex K for comments on security issues. The main issues that exists are: - This RTP payload format only confidentiality protects the RTP payload, thus header information is leaked, similarly to SRTP. - The use of stream ciphers as AES CM and no integrity protection allows an attacker to purposefully attack the content of the encrypted RTP payload by switching individual bits. - The usage of selective encryption without integrity protection allows for an attacker to perform any replacements of complete RTP payloads and packets it desires. - The payload format makes the receiver vulnerable to denial of service attacks that inserts RTP packets into the stream, that the receiver then interprets as being encrypted thus wasting computational resources. To prevent this attack, authentication needs to be used. Interoperability considerations: Published specification: 3GPP TS 26.234, Release 6. Open Mobile Alliance DRM Content Format V2.0 Applications which use this media type: Third Generation Partnership Project (3GPP) Packet-switched Streaming Service (PSS) clients and servers, which supports the Open Mobile Alliance's specification of Digital Rights Management version 2.0. Additional information: Magic number(s): N/A File extension(s): N/A Macintosh File Type Code(s): N/A Person & email address to contact for further information: magnus.westerlund(a)ericsson.com Intended usage: Common Author/Change controller: 3GPP TSG SA -- Magnus Westerlund Multimedia Technologies, Ericsson Research EAB/TVA/A ---------------------------------------------------------------------- Ericsson AB | Phone +46 8 4048287 Torshamsgatan 23 | Fax +46 8 7575550 S-164 80 Stockholm, Sweden | mailto: magnus.westerlund(a)ericsson.com

2 5

W3C Last Call and Media Type request for comments: XQuery and XQueryX
by Liam Quin 18 Jan '07

18 Jan '07

[ Notes: (1) - I'm trying to follow a new procedure here. Becasue not everything is in place, the documents I refer to probably don't have perfect wording. The documentation on the process was released after the documents were frozen for Last Call, but we can make any needed changes for the next round of publication. I see that we failed to define the correct syntax for parameters, and would welcome comments on any other areas wheer we need to improve. (2) The following text will be inserted in the next published versions of the documents: This registration is for community review and will be (or has been) submitted to the IESG for review, approval, and registration with IANA. (3) We are using Bugzilla to track comments on these documents; comments on these MIME-related pats of the documents may be made on the ietf-types mailing list or in Bugzilla. See the individual documents and their respective "Status of this Document" sections for further information. - Liam ] In accordance with the draft Media Type Specifications and Registration Procedures [1], and on behalf of the W3C XML Query Working Group [2], I hereby give notice that W3C has published two specifications at the stage "Last Call Working Draft" which each incorporate definitions of a standards-tree MIME media type, as allowed for in section 3.1 of [1], and request comments on these definitions. The types and subtypes are application/xquery defined in "XQuery 1.0: An XML Query Language" [3] optional parameter: charset application/xquery+xml defined in "XML Syntax for XQuery 1.0 (XQueryX)" [4] optional parameter: charset **** Registration for application/xquery also at [3] I The application/xquery Media Type (Non-Normative) --------------------------------------------------- This Appendix specifies the media type for XQuery Version 1.0. XQuery is a language for querying over collections of data from XML data sources, as specified in the main body of this document. I.1 Introduction ---------------- This document, together with its normative references, defines the language XQuery Version 1.0. This Appendix provides information about the application/xquery media type, which is intended to be used for transmitting queries written in the XQuery language. This document was prepared by members of the W3C XML Query Working Group. Please send comments to public-qt-comments [at] w3.org, a public mailing list with archives at http://lists.w3.org/Archives/Public/public-qt-comments. I.2 Registration of MIME Media Type application/xquery ------------------------------------------------------ MIME media type name: application MIME subtype name: xquery Required parameters: none Optional parameters: charset The syntax of XQuery is expressed in Unicode but may be written with any Unicode-compatible character encoding, including UTF-8 or UTF-16, or transported as US-ASCII or Latin-1 with Unicode characters outside the range of the given encoding represented using an XML-style ෝ syntax. I.2.1 Interoperability Considerations None known. I.2.2 Applications Using this Media Type The public XQuery Web page lists more than two dozen implementations of the XQuery language, both proprietary and open source. This new media type is being registered to allow for deployment of XQuery on the World Wide Web. I.2.3 File Extensions The most common file extensions in use for XQuery are .xq and .xquery. The appropriate Macintosh file type code is TEXT. I.2.4 Intended Usage The intended usage of this media type is for interchange of XQuery expressions. I.2.5 Author/Change Controller XQuery was produced by, and is maintained by, the World Wide Web Consortium's XML Query Working Group. The W3C has change control over this specification. I.3 Encoding Considerations For use with transports that are not 8-bit clean, quoted-printable encoding is recommended since the XQuery syntax itself uses the US-ASCII-compatible subset of Unicode. An XQuery document may contain an encoding declaration as part of its version declaration: xquery version "1.0" encoding "utf-8"; If an XQuery document contains an encoding declaration, it overrides the default encoding specified by the MIME charset parameter. I.4 Recognizing XQuery Files An XQuery file may have the string xquery version "V.V" near the beginning of the document, where "V.V" is a version number. Currently the version number, if present, must be "1.0". I.5 Charset Default Rules XQuery documents use the Unicode character set and, by default, the UTF-8 encoding. I.6 Security Considerations Queries written in XQuery may cause arbitrary URIs to be dereferenced. Therefore, the security issues of [Uniform Resource Locators (URL)] Section 6 should be considered. In addition, the contents of file: URIs can in some cases be accessed, processed and returned as results. Furthermore, because the XQuery language permits extensions, it is possible that application/xquery may describe content that has security implications beyond those described here. The XML Query Working group is working on a facility to allow XQuery expressions to be used to create and update persistent data. Untrusted queries should not be given write access to data. **** Registration for application/xquery+xml also at [4] C The application/xquery+xml Media Type (Non-Normative) ------------------------------------------------------- This Appendix specifies the media type for XQueryX Version 1.0. XQueryX is the XML syntax of a language, XQuery, for querying over data from XML data sources, as specified in [XQuery 1.0: An XML Query Language]. C.1 Introduction ---------------- This document, together with its normative references, defines the XML syntax for the XML Query language XQuery Version 1.0. This Appendix specifies the application/xquery+xml media type, which is intended to be used for transmitting queries expressed in the XQueryX syntax. This document was prepared by members of the W3C XML Query Working Group. Please send comments to public-qt-comments [at] w3.org, a public mailing list with archives at http://lists.w3.org/Archives/Public/public-qt-comments. C.2 Registration of MIME Media Type application/xquery+xml MIME media type name: application MIME subtype name: xquery+xml Required parameters: none Optional parameters: charset This parameter has identical semantics to the charset parameter of the application/xml media type as specified in [RFC3023]. C.2.1 Encoding Considerations The considerations as specified in RFC 3023 [XMLMIME] also hold for 'application/xquery+xml'. C.2.2 Fragment Identifiers For documents labeled as 'application/xquery+xml', fragment identifiers are handled as specified in RFC 3023 [XMLMIME]. C.2.3 Restrictions on usage The intended usage of this media type is for interchange of XQueryX expressions. C.2.4 Security Considerations Queries written in XQueryX may cause arbitrary URIs to be dereferenced. Therefore, the security issues of [Uniform Resource Locators (URL)] Section 6 should be considered. In addition, the contents of file: URIs can in some cases be accessed, processed and returned as results. Furthermore, because the XQuery language (and thus the XQueryX language) permits extensions, it is possible that application/xquery+xml may describe content that has security implications beyond those described here. However, if the processor follows only the normative semantics of this specification, this content will be ignored. Only in the case where the processor recognizes and processes the additional content, or where further processing of that content is dispatched to other processors, would security issues arise. The XML Query Working group is working on a facility to allow XQuery (and thus XQueryX) expressions to be used to create and update persistent data. Untrusted queries should not be given write access to data. C.2.5 Interoperability Considerations See Section 5 ConformanceXQ. C.2.6 Applications That Use This Media Type The public XQuery Web page lists more than two dozen implementations of the XQuery language, both proprietary and open source. Some of these are known to support XQueryX. This new media type is being registered to allow for deployment of XQueryX on the World Wide Web. There is no experimental, vendor specific, or personal tree predecessor to "application/xquery+xml", reflecting the fact that no applications currently recognize it. This new type is being registered in order to allow for the expected deployment of XQueryX 1.0 on the World Wide Web, as a first class XML application. C.2.7 Additional Information C.2.7.1 Recognizing XQuery Files ("Magic Numbers") Although no byte sequences can be counted on to consistently identify XQueryX, XQueryX documents will have the sequence "http://www.w3.org/yyyy/mm/XQueryX" to identify the XQueryX namespace (where "yyyy" is exactly four decimal digits and "mm" is exactly two decimal digits). This sequence will normally be found in a namespace attribute of the first element in the document. C.2.7.2 File Extensions The most common file extension in use for XQueryX is .xqx. C.2.7.3 Macintosh File Type Code(s) The appropriate Macintosh file type code is TEXT. C.2.8 Person and Email Address to Contact For Further Information Jim Melton, Oracle Corp., jim.melton [at] oracle.com C.2.9 Intended Usage COMMON C.2.10 Author/Change Controller XQuery was produced by, and is maintained by, the World Wide Web Consortium's XML Query Working Group. The W3C has change control over this specification. [1] http://www.ietf.org/internet-drafts/draft-freed-media-type-reg-02.txt [2] http://www.w3.org/XML/Query [3] http://www.w3.org/TR/2005/WD-xquery-20050404/#id-mime-type [4] http://www.w3.org/TR/2005/WD-xqueryx-20050404/#xqueryx-id-mime-type -- Liam Quin, W3C XML Activity Lead, http://www.w3.org/People/Quin/ http://www.holoweb.net/~liam/

8 16

Request preliminary check of 8 personal media types
by Damian Dollahite 24 Sep '06

24 Sep '06

I would like to request a preliminary check of 8 media types collected in this document: http://purl.org/int-fiction/ifmi/documents/mediatypes/ This document is not a registration form or specification, rather it is a discussion of issues that need to be addressed so that these formats can be registered. It does include examples of how the registration forms might be filled out, however. Currently, these file formats are being transferred using "x-" prefixed types; I'm fairly certain that none of the controllers are aware that the prs. tree is open to everyone, or else they just assume that registration will involve too much paperwork to bother with. I plan to contact them and present them with this document, as well as volunteering to handle the paperwork for them. Once I've discussed these types with the format controllers, I'll submit them for another review before proceeding with registration; at this point all I need is a quick look-over to make sure I won't be giving the format controllers bad advice. The thing that especially concerns me is my use of a "+blorb" suffix on some of the types. I realize "+" suffixes are discouraged, but something of that nature is needed to allow correct dispatch of Blorb files. If "+blorb" is simply not appropriate, I'd appreciate suggestions on how else to solve the problem; I do not believe a "." or "-" facet is semantically correct here. Thank you, M.D. Dollahite

2 2

Resend of Media Type Registrations for OEBPS Package File (OPF) - Review of Informational RFC
by Nick Bogaty 15 Sep '06

15 Sep '06

To whom it may concern, Please see below link to Media Type Registration for the OEBPS Package File (OPF) to be processed as an informational RFC. This has been resubmitted because "internet-drafts(a)ietf.org" could not find our second submission and was resubmitted as the wrong format. I-D can be found at: <http://www.idpf.org/draft-conboy-mime-opf-00.txt> http://www.idpf.org/draft-conboy-mime-opf-00.txt <http://www.idpf.org/mime-opf.htmhttp://www.idpf.org/draft-conboy-mime-opf-0 0.txt> The only change is: 1. Names of the authors have been added on the top of the draft text and in the section with contact information. 2. The submission has been resent as ASCII text Please send any questions to myself, Nick Bogaty, at <mailto:nbogaty@idpf.org> nbogaty(a)idpf.org. Thanks, Nick -- Nick Bogaty Executive Director International Digital Publishing Forum (IDPF) nbogaty(a)idpf.org www.idpf.org (212) 924-9081 direct (212) 208-0978 fax

1 0

Resend of Media Type Registrations for OEBPS Package File (OPF) - Review of Informational RFC
by Nick Bogaty 15 Sep '06

15 Sep '06

To whom it may concern, Please see below link to Media Type Registration for the OEBPS Package File (OPF) to be processed as an informational RFC. This has been resubmitted because "internet-drafts(a)ietf.org" could not find our second submission. I-D can be found at: http://www.idpf.org/mime-opf.htm The only change is: 1. Names of the authors have been added on the top of the draft text and in the section with contact information. Please send any questions to myself, Nick Bogaty, at <mailto:nbogaty@idpf.org> nbogaty(a)idpf.org. Thanks, Nick -- Nick Bogaty Executive Director International Digital Publishing Forum (IDPF) nbogaty(a)idpf.org www.idpf.org (212) 924-9081 direct (212) 208-0978 fax

1 0

Media Type Registrations for OEBPS Package File (OPF) - Review of Informational RFC
by Nick Bogaty 05 Sep '06

05 Sep '06

To whom it may concern, Please see below and attached a Media Type Registration for the OEBPS Package File (OPF) to be processed as an informational RFC. This RFC has been submitted to internet-drafts(a)ietf.org. Names of the authors have been added on the top of the draft text and in the section with contact information. Please send any questions to myself, Nick Bogaty, at <mailto:nbogaty@idpf.org> nbogaty(a)idpf.org. Thanks, Nick -- Nick Bogaty Executive Director International Digital Publishing Forum (IDPF) nbogaty(a)idpf.org www.idpf.org (212) 924-9081 direct (212) 208-0978 fax --- Network Working Group G. Conboy INTERNET-DRAFT J. Rivlin draft-conboy-mime-opf-00 eBook Technologies, Inc. Expires: August 2006 J. Ferraiolo Adobe Systems, Inc. June 22, 2006 Media Type Registrations for OEBPS Package File (OPF) Status of this memo By submitting this Internet-Draft, each author represents that any applicable patent or other IPR claims of which he or she is aware have been or will be disclosed, and any of which he or she becomes aware will be disclosed, in accordance with Section 6 of BCP 79. Internet-Drafts are working documents of the Internet Engineering Task Force (IETF), its areas, and its working groups. Note that other groups may also distribute working documents as Internet- Drafts. 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". The list of current Internet-Drafts can be accessed at <http://www.ietf.org/1id-abstracts.txt> http://www.ietf.org/1id-abstracts.txt The list of Internet-Draft Shadow Directories can be accessed at <http://www.ietf.org/shadow.html> http://www.ietf.org/shadow.html This document is an individual submission to the IETF. Comments should be directed to the author. Abstract This document serves to register a media type for the Open eBook Publication Structure (OEBPS) Package Files. Conboy, Rivlin & Ferraiolo [Page 1] INTERNET-DRAFT draft-conboy-mime-opf-00 June 22, 2006 TABLE OF CONTENTS 1. Conventions Used.................................................3 2. Introduction.....................................................3 3. Security Considerations..........................................3 4. IANA Considerations..............................................5 4.1. Downloadable Sound.............................................5 5. Authors' Addresses...............................................5 6. References.......................................................5 6.1. Normative......................................................5 7. IPR Notice.......................................................6 8. Copyright Notice.................................................6 Conboy, Rivlin & Ferraiolo [Page 2] INTERNET-DRAFT draft-conboy-mime-opf-00 June 22, 2006 1. Introduction The present document seeks to register a media type for the Open eBook Publication Structure (OEBPS) Package File (OPF). The OPF file is an XML file that describes an OEBPS Publication. It identifies all other files in the publication and provides descriptive information about them. OPF and its related standards are maintained and defined by the International Digital Publishing Forurm (IDPF). The media type defined here is needed to correctly identify OPF files when they are edited on disk, referenced in OEBPS Container files, or used in other places where media types are used. 2. Security Considerations The OPF files contain well formed XML conforming to the XML 1.0 specification. Clearly it is possible to author malicious files which, for example, contain malformed data. Most XML parsers protect themselves from such attacks by rigoriously enforcing conformance. All processors that read OPF files should rigourously check the size and validity of data retrieved. There is no current provision in the OEBPS Package File standard for encryption, signing, or authentication within the file format. 3. IANA Considerations The present document requests that IANA registers the media type application/oebps-package+xml as specified in Section 3.1. The registration uses the template present in [RFC4288]. 3.1. Media Type for Downloadable Sounds Type name: application Subtype name: oebps-package+xml Required parameters: none Optional parameters: none Encoding considerations: OPF files are UTF-8 or UTF-16 encoded XML Conboy, Rivlin & Ferraiolo [Page 3] INTERNET-DRAFT draft-conboy-mime-opf-00 June 22, 2006 Security considerations: none Interoperability considerations: none Published specification: Specification is published by the International Digital Publishing Forum and can be found at <http://www.idpf.org/oebps/oebps1.2/> http://www.idpf.org/oebps/oebps1.2/ download/oeb12-xhtml.htm Applications which use this media type: 1) eBook Technologies, Inc. eBook reading system. 2) Microsoft Reader 3) OSoft reader 4) Content Reserve Publishing System 5) IDPF Container WG 6) PC Reader.com 7) MobiPocket reader Additional information: Magic number(s): none File extension(s): .opf Macintosh file type code(s): TEXT Person & email address to contact for further information: Nick Bogaty ( <mailto:nbogaty@idpf.org> nbogaty(a)idpf.org) Intended usage: COMMON Restrictions on usage: None Author: International Digital Publishing Forum ( <http://www.idpf.org> www.idpf.org) Change controller: International Digital Publishing Forum ( <http://www.idpf.org> www.idpf.org) Conboy, Rivlin & Ferraiolo [Page 4] INTERNET-DRAFT draft-conboy-mime-opf-00 June 22, 2006 4. RFC Editor Considerations The references to RFC XXXX in the media type registration need to be replaced with the actual RFC number when it is issued. Please remove this section before publication as RFC. 5. Authors' Addresses Garth Conboy eBook Technologies, Inc. 7745 Herschel Avenue La Jolla, CA 92037 Phone: (858) 551-4950 EMail: <mailto:gc@ebooktechnologies.com> gc(a)ebooktechnologies.com John Rivlin eBook Technologies, Inc. 7745 Herschel Avenue La Jolla, CA 92037 Phone: (650) 255-3389 EMail: <mailto:john@ebooktechnologies.com> john(a)ebooktechnologies.com Jon Ferraiolo Adobe Systems, Inc. 345 Park Avenue San Jose, CA 95110-2704 Phone: (408) 536-2002 EMail: <mailto:johnf@adobe.com> johnf(a)adobe.com 6. References 6.1. Normative [OEBPS] "Open eBook Publication Structure 1.2", International Digital Publishing Forum (IDPF), New York, NY USA, 2002. [RFC4288] Freed, N. and J. Klensin, "Media Type Specifications and Registration Procedures", BCP 13, RFC 4288, December 2005. Conboy, Rivlin & Ferraiolo [Page 5] INTERNET-DRAFT draft-conboy-mime-opf-00 June 22, 2006 7. IPR Notice The IETF takes no position regarding the validity or scope of any Intellectual Property Rights or other rights that might be claimed to pertain to the implementation or use of the technology described in this document or the extent to which any license under such rights might or might not be available; nor does it represent that it has made any independent effort to identify any such rights. Information on the procedures with respect to rights in RFC documents can be found in BCP 78 and BCP 79. Copies of IPR disclosures made to the IETF Secretariat and any assurances of licenses to be made available, or the result of an attempt made to obtain a general license or permission for the use of such proprietary rights by implementers or users of this specification can be obtained from the IETF on-line IPR repository at <http://www.ietf.org/ipr> http://www.ietf.org/ipr. The IETF invites any interested party to bring to its attention any copyrights, patents or patent applications, or other proprietary rights that may cover technology that may be required to implement this standard. Please address the information to the IETF at ietf- <mailto:ipr@ietf.org> ipr(a)ietf.org. This Internet-Draft expires in August 2006. 8. Copyright Notice Copyright (C) The Internet Society (2006). This document is subject to the rights, licenses and restrictions contained in BCP 78, and except as set forth therein, the authors retain all their rights. This document and the information contained herein are provided on an "AS IS" basis and THE CONTRIBUTOR, THE ORGANIZATION HE/SHE REPRESENTS OR IS SPONSORED BY (IF ANY), THE INTERNET SOCIETY AND THE INTERNET ENGINEERING TASK FORCE DISCLAIM ALL WARRANTIES, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF THE INFORMATION HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE. Conboy, Rivlin & Ferraiolo [Page 6]

1 0

Typos and outdated references in application/* MIME type index
by Bjoern Hoehrmann 03 Sep '06

03 Sep '06

Hi, http://www.iana.org/assignments/media-types/application/ has a few typos and outdated references; I found the following: * cnrp+xml - the link broken, it should go to RFC 3367. * reginfo+xml - it links to RFC 3608 but should link RFC 3680 * vnd.syncml.+xml - the name is "vnd.syncml+xml" without the "." * simple-filter+xml - the %0D%0A part of the URL must be removed ´ * xv+xml - it should reference RFC 4374 All types that refer to RFC-froumentin-voice-mediatypes-02.txt should refer to RFC 4267. regards, -- Björn Höhrmann · mailto:bjoern@hoehrmann.de · http://bjoern.hoehrmann.de Weinh. Str. 22 · Telefon: +49(0)621/4309674 · http://www.bjoernsworld.de 68309 Mannheim · PGP Pub. KeyID: 0xA4357E78 · http://www.websitedev.de/

1 0

Missing text in application/fastinfoset MIME type registration
by Bjoern Hoehrmann 03 Sep '06

03 Sep '06

Hi, http://www.iana.org/assignments/media-types/application/fastinfoset lacks the following part of the original registration; it seems there might be some software that strips <...> sequences, there might be other registration documents with similar problems. The part is <?xml encoding='finf'?> <?xml encoding='finf' standalone='yes'?> <?xml encoding='finf' standalone='no'?> <?xml version='1.0' encoding='finf'?> <?xml version='1.0' encoding='finf' standalone='yes'?> <?xml version='1.0' encoding='finf' standalone='no'?> <?xml version='1.1' encoding='finf'?> <?xml version='1.1' encoding='finf' standalone='yes'?> <?xml version='1.1' encoding='finf' standalone='no'?> ... as found in the IESG's approval of the type http://www1.ietf.org/mail-archive/web/ietf-announce/current/msg00780.html regards, -- Björn Höhrmann · mailto:bjoern@hoehrmann.de · http://bjoern.hoehrmann.de Weinh. Str. 22 · Telefon: +49(0)621/4309674 · http://www.bjoernsworld.de 68309 Mannheim · PGP Pub. KeyID: 0xA4357E78 · http://www.websitedev.de/

1 0