Network Working Group G. ConboyINTERNET-DRAFTRequest for Comments: 4839 J. Rivlindraft-conboy-mime-opf-00Category: Informational eBook Technologies, Inc.Expires: August 2006J. Ferraiolo Adobe Systems, Inc.June 22, 2006April 2007 Media Type Registrations forOEBPSthe Open eBook Publication Structure (OEBPS) Package File (OPF) Status ofthisThis Memo This memoBy 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 ofprovides information for the InternetEngineering 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.community. Itis inappropriate to use Internet-Drafts as reference material or to cite them other than as "work in progress". The listdoes not specify an Internet standard ofcurrent Internet-Drafts can be accessed at http://www.ietf.org/1id-abstracts.txt The listany kind. Distribution ofInternet-Draft Shadow Directories can be accessed at http://www.ietf.org/shadow.html This documentthis memo isan individual submission to the IETF. Comments should be directed to the author.unlimited. Copyright Notice Copyright (C) The IETF Trust (2007). Abstract This document serves to register a media type for the Open eBook Publication Structure (OEBPS) Package Files.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.................................................61. Introduction The present documentseeks to registerregisters a media type for the Open eBook Publication Structure (OEBPS) Package File (OPF). The OPF file is an XML file that describes an OEBPSPublication.Publication [OEBPS]. 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 PublishingForurmForum (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 containwell formedwell-formed XML conforming to the XML 1.0 specification.ClearlyClearly, it is possible to author malicious files which, for example, contain malformed data. Most XML parsers protect themselves from such attacks byrigoriouslyrigorously enforcing conformance. All processors that read OPF files shouldrigourouslyrigorously 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 ConsiderationsThe present document requests thatIANAregistershas registered 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 Security considerations: none Interoperability considerations: none Published specification: Specification is published by the International Digital Publishing Forum and can be found athttp://www.idpf.org/oebps/oebps1.2/ download/oeb12-xhtml.htmhttp://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 (nbogaty@idpf.org) Intended usage: COMMON Restrictions on usage: None Author: International Digital Publishing Forum (www.idpf.org) Change controller: International Digital Publishing Forum (www.idpf.org) 4. Normative References [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, RFCEditor 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.4288, December 2005. Authors' Addresses Garth Conboy eBook Technologies, Inc. 7745 Herschel Avenue La Jolla, CA 92037 Phone: (858) 551-4950 EMail: gc@ebooktechnologies.com John Rivlin eBook Technologies, Inc. 7745 Herschel Avenue La Jolla, CA 92037 Phone: (650) 255-3389 EMail: john@ebooktechnologies.com Jon Ferraiolo Adobe Systems, Inc. 345 Park Avenue San Jose, CA 95110-2704 Phone: (408) 536-2002 EMail: johnf@adobe.com6. 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 SpecificationsFull Copyright Statement Copyright (C) The IETF Trust (2007). This document is subject to the rights, licenses andRegistration Procedures",restrictions contained in BCP13, RFC 4288, December 2005. 7. IPR Notice78, 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, THE IETF TRUST 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. Intellectual Property 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. 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 atietf- ipr@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 andietf-ipr@ietf.org. Acknowledgement Funding for theinformation contained herein areRFC Editor function is currently providedon 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.by the Internet Society.