idnits 2.17.1 draft-conboy-mime-opf-00.txt: Checking boilerplate required by RFC 5378 and the IETF Trust (see https://trustee.ietf.org/license-info): ---------------------------------------------------------------------------- ** It looks like you're using RFC 3978 boilerplate. You should update this to the boilerplate described in the IETF Trust License Policy document (see https://trustee.ietf.org/license-info), which is required now. -- Found old boilerplate from RFC 3978, Section 5.1 on line 16. -- Found old boilerplate from RFC 3978, Section 5.5 on line 230. -- Found old boilerplate from RFC 3979, Section 5, paragraph 1 on line 199. -- Found old boilerplate from RFC 3979, Section 5, paragraph 2 on line 206. -- Found old boilerplate from RFC 3979, Section 5, paragraph 3 on line 212. ** This document has an original RFC 3978 Section 5.4 Copyright Line, instead of the newer IETF Trust Copyright according to RFC 4748. ** This document has an original RFC 3978 Section 5.5 Disclaimer, instead of the newer disclaimer which includes the IETF Trust according to RFC 4748. Checking nits according to https://www.ietf.org/id-info/1id-guidelines.txt: ---------------------------------------------------------------------------- == No 'Intended status' indicated for this document; assuming Proposed Standard == The page length should not exceed 58 lines per page, but there was 1 longer page, the longest (page 6) being 59 lines Checking nits according to https://www.ietf.org/id-info/checklist : ---------------------------------------------------------------------------- ** There is 1 instance of too long lines in the document, the longest one being 1 character in excess of 72. Miscellaneous warnings: ---------------------------------------------------------------------------- == The copyright year in the RFC 3978 Section 5.4 Copyright Line does not match the current year -- The document seems to lack a disclaimer for pre-RFC5378 work, but may have content which was first submitted before 10 November 2008. If you have contacted all the original authors and they are all willing to grant the BCP78 rights to the IETF Trust, then this is fine, and you can ignore this comment. If not, you may need to add the pre-RFC5378 disclaimer. (See the Legal Provisions document at https://trustee.ietf.org/license-info for more information.) -- The document date (June 22, 2006) is 6490 days in the past. Is this intentional? Checking references for intended status: Proposed Standard ---------------------------------------------------------------------------- (See RFCs 3967 and 4897 for information about using normative references to lower-maturity documents in RFCs) == Unused Reference: 'OEBPS' is defined on line 183, but no explicit reference was found in the text -- Possible downref: Non-RFC (?) normative reference: ref. 'OEBPS' ** Obsolete normative reference: RFC 4288 (Obsoleted by RFC 6838) Summary: 5 errors (**), 0 flaws (~~), 4 warnings (==), 8 comments (--). Run idnits with the --verbose option for more detailed information about the items above. -------------------------------------------------------------------------------- 2 Network Working Group G. Conboy 3 INTERNET-DRAFT J. Rivlin 4 draft-conboy-mime-opf-00 eBook Technologies, Inc. 5 Expires: August 2006 J. Ferraiolo 6 Adobe Systems, Inc. 7 June 22, 2006 9 Media Type Registrations for OEBPS Package File (OPF) 11 Status of this memo 13 By submitting this Internet-Draft, each author represents that any 14 applicable patent or other IPR claims of which he or she is aware 15 have been or will be disclosed, and any of which he or she becomes 16 aware will be disclosed, in accordance with Section 6 of BCP 79. 18 Internet-Drafts are working documents of the Internet Engineering 19 Task Force (IETF), its areas, and its working groups. Note that 20 other groups may also distribute working documents as Internet- 21 Drafts. 23 Internet-Drafts are draft documents valid for a maximum of six 24 months and may be updated, replaced, or obsoleted by other 25 documents at any time. It is inappropriate to use Internet-Drafts 26 as reference material or to cite them other than as "work in 27 progress". 29 The list of current Internet-Drafts can be accessed at 30 http://www.ietf.org/1id-abstracts.txt 32 The list of Internet-Draft Shadow Directories can be accessed at 33 http://www.ietf.org/shadow.html 35 This document is an individual submission to the IETF. Comments 36 should be directed to the author. 38 Abstract 40 This document serves to register a media type for the Open eBook 41 Publication Structure (OEBPS) Package Files. 43 TABLE OF CONTENTS 45 1. Conventions Used.................................................3 46 2. Introduction.....................................................3 47 3. Security Considerations..........................................3 48 4. IANA Considerations..............................................5 49 4.1. Downloadable Sound.............................................5 50 5. Authors' Addresses...............................................5 51 6. References.......................................................5 52 6.1. Normative......................................................5 53 7. IPR Notice.......................................................6 54 8. Copyright Notice.................................................6 56 1. Introduction 58 The present document seeks to register a media type for 59 the Open eBook Publication Structure (OEBPS) Package File (OPF). 60 The OPF file is an XML file that describes an OEBPS Publication. 61 It identifies all other files in the publication and provides 62 descriptive information about them. OPF and its related standards 63 are maintained and defined by the International Digital Publishing 64 Forurm (IDPF). 66 The media type defined here is needed to correctly identify OPF 67 files when they are edited on disk, referenced in OEBPS Container 68 files, or used in other places where media types are used. 70 2. Security Considerations 72 The OPF files contain well formed XML conforming to the XML 1.0 73 specification. 75 Clearly it is possible to author malicious files which, for 76 example, contain malformed data. Most XML parsers protect 77 themselves from such attacks by rigoriously enforcing conformance. 79 All processors that read OPF files should rigourously check the 80 size and validity of data retrieved. 82 There is no current provision in the OEBPS Package File standard 83 for encryption, signing, or authentication within the file format. 85 3. IANA Considerations 87 The present document requests that IANA registers the media type 88 application/oebps-package+xml as specified in Section 3.1. The 89 registration uses the template present in [RFC4288]. 91 3.1. Media Type for Downloadable Sounds 93 Type name: application 95 Subtype name: oebps-package+xml 97 Required parameters: none 99 Optional parameters: none 101 Encoding considerations: OPF files are UTF-8 or UTF-16 102 encoded XML 104 Security considerations: none 106 Interoperability considerations: none 108 Published specification: Specification is published by the 109 International Digital Publishing 110 Forum and can be found at 111 http://www.idpf.org/oebps/oebps1.2/ 112 download/oeb12-xhtml.htm 114 Applications which use this media type: 115 1) eBook Technologies, Inc. 116 eBook reading system. 117 2) Microsoft Reader 118 3) OSoft reader 119 4) Content Reserve Publishing 120 System 121 5) IDPF Container WG 122 6) PC Reader.com 123 7) MobiPocket reader 125 Additional information: 127 Magic number(s): none 129 File extension(s): .opf 131 Macintosh file type code(s): TEXT 133 Person & email address to contact for further information: 134 Nick Bogaty (nbogaty@idpf.org) 136 Intended usage: COMMON 138 Restrictions on usage: None 140 Author: International Digital Publishing 141 Forum (www.idpf.org) 143 Change controller: International Digital Publishing 144 Forum (www.idpf.org) 146 4. RFC Editor Considerations 148 The references to RFC XXXX in the media type registration need to 149 be replaced with the actual RFC number when it is issued. 151 Please remove this section before publication as RFC. 153 5. Authors' Addresses 155 Garth Conboy 156 eBook Technologies, Inc. 157 7745 Herschel Avenue 158 La Jolla, CA 92037 160 Phone: (858) 551-4950 161 EMail: gc@ebooktechnologies.com 163 John Rivlin 164 eBook Technologies, Inc. 165 7745 Herschel Avenue 166 La Jolla, CA 92037 168 Phone: (650) 255-3389 169 EMail: john@ebooktechnologies.com 171 Jon Ferraiolo 172 Adobe Systems, Inc. 173 345 Park Avenue 174 San Jose, CA 95110-2704 176 Phone: (408) 536-2002 177 EMail: johnf@adobe.com 179 6. References 181 6.1. Normative 183 [OEBPS] "Open eBook Publication Structure 1.2", International 184 Digital Publishing Forum (IDPF), New York, NY USA, 2002. 186 [RFC4288] Freed, N. and J. Klensin, "Media Type Specifications 187 and Registration Procedures", BCP 13, RFC 4288, 188 December 2005. 190 7. IPR Notice 192 The IETF takes no position regarding the validity or scope of any 193 Intellectual Property Rights or other rights that might be claimed 194 to pertain to the implementation or use of the technology described 195 in this document or the extent to which any license under such 196 rights might or might not be available; nor does it represent that 197 it has made any independent effort to identify any such rights. 198 Information on the procedures with respect to rights in RFC 199 documents can be found in BCP 78 and BCP 79. 201 Copies of IPR disclosures made to the IETF Secretariat and any 202 assurances of licenses to be made available, or the result of an 203 attempt made to obtain a general license or permission for the use 204 of such proprietary rights by implementers or users of this 205 specification can be obtained from the IETF on-line IPR repository 206 at http://www.ietf.org/ipr. 208 The IETF invites any interested party to bring to its attention any 209 copyrights, patents or patent applications, or other proprietary 210 rights that may cover technology that may be required to implement 211 this standard. Please address the information to the IETF at ietf- 212 ipr@ietf.org. 214 This Internet-Draft expires in August 2006. 216 8. Copyright Notice 218 Copyright (C) The Internet Society (2006). This document is 219 subject to the rights, licenses and restrictions contained in BCP 220 78, and except as set forth therein, the authors retain all their 221 rights. 223 This document and the information contained herein are provided on 224 an "AS IS" basis and THE CONTRIBUTOR, THE ORGANIZATION HE/SHE 225 REPRESENTS OR IS SPONSORED BY (IF ANY), THE INTERNET SOCIETY AND 226 THE INTERNET ENGINEERING TASK FORCE DISCLAIM ALL WARRANTIES, 227 EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO ANY WARRANTY THAT 228 THE USE OF THE INFORMATION HEREIN WILL NOT INFRINGE ANY RIGHTS OR 229 ANY IMPLIED WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A 230 PARTICULAR PURPOSE.