idnits 2.17.1 draft-newman-mime-cdisp-metadata-00.txt: Checking boilerplate required by RFC 5378 and the IETF Trust (see https://trustee.ietf.org/license-info): ---------------------------------------------------------------------------- ** Looks like you're using RFC 2026 boilerplate. This must be updated to follow RFC 3978/3979, as updated by RFC 4748. Checking nits according to https://www.ietf.org/id-info/1id-guidelines.txt: ---------------------------------------------------------------------------- ** Missing expiration date. The document expiration date should appear on the first and last page. ** The document seems to lack a 1id_guidelines paragraph about Internet-Drafts being working documents. ** The document seems to lack a 1id_guidelines paragraph about the list of current Internet-Drafts. ** The document seems to lack a 1id_guidelines paragraph about the list of Shadow Directories. == No 'Intended status' indicated for this document; assuming Proposed Standard Checking nits according to https://www.ietf.org/id-info/checklist : ---------------------------------------------------------------------------- ** The document seems to lack an Introduction section. ** The document seems to lack an IANA Considerations section. (See Section 2.2 of https://www.ietf.org/id-info/checklist for how to handle the case when there are no actions for IANA.) ** The document seems to lack separate sections for Informative/Normative References. All references will be assumed normative when checking for downward references. ** There is 1 instance of too long lines in the document, the longest one being 3 characters in excess of 72. ** The abstract seems to contain references ([CDISP], [MIME-IMB]), which it shouldn't. Please replace those with straight textual mentions of the documents in question. ** The document seems to lack a both a reference to RFC 2119 and the recommended RFC 2119 boilerplate, even if it appears to use RFC 2119 keywords -- however, there's a paragraph with a matching beginning. Boilerplate error? RFC 2119 keyword, line 57: '...osition type, it SHOULD indicate in so...' RFC 2119 keyword, line 61: '...lefile body part SHOULD have a "metada...' 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 (November 1997) is 9658 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) == Missing Reference: 'KEYWORDS' is mentioned on line 50, but not defined -- No information found for draft-ietf-drums-abnf-xx - is the name correct? -- Possible downref: Normative reference to a draft: ref. 'ABNF' Summary: 11 errors (**), 0 flaws (~~), 3 warnings (==), 4 comments (--). Run idnits with the --verbose option for more detailed information about the items above. -------------------------------------------------------------------------------- 2 Network Working Group C. Newman 3 Internet Draft: Metadata Content-Disposition Type Innosoft 4 Document: draft-newman-mime-cdisp-metadata-00.txt November 1997 5 Expires in six months 7 Metadata Content-Disposition Type 9 Status of this memo 11 This document is an Internet-Draft. Internet-Drafts are working 12 documents of the Internet Engineering Task Force (IETF), its areas, 13 and its working groups. Note that other groups may also distribute 14 working documents as Internet-Drafts. 16 Internet-Drafts are draft documents valid for a maximum of six 17 months and may be updated, replaced, or obsoleted by other 18 documents at any time. It is inappropriate to use Internet-Drafts 19 as reference material or to cite them other than as "work in 20 progress." 22 To view the entire list of current Internet-Drafts, please check 23 the "1id-abstracts.txt" listing contained in the Internet-Drafts 24 Shadow Directories on ftp.is.co.za (Africa), ftp.nordu.net 25 (Europe), munnari.oz.au (Pacific Rim), ds.internic.net (US East 26 Coast), or ftp.isi.edu (US West Coast). 28 Copyright Notice 30 Copyright (C) The Internet Society 1997. All Rights Reserved. 32 Abstract 34 The Content-Disposition [CDISP] header defines two disposition 35 types: ''inline'' and ''attachment'' which can affect presentation of 36 a MIME [MIME-IMB] body part. There have been a number of cases 37 where one MIME body part contains metadata for another MIME body 38 part and is neither suitable for inline display by itself, nor is 39 it useful if treated as an independent attachment and saved to a 40 file by itself. If the recipient UA is not familiar with the 41 specific media type, the user often is presented with a useless 42 unrecognizable attachment. This memo proposes a third disposition 43 type, ''metadata'', to address this situation. 45 1. Conventions Used in this Document 47 The key words "MUST", "MUST NOT", "SHOULD", "SHOULD NOT", and "MAY" 48 in this document are to be interpreted as defined in "Key words for 49 use in RFCs to Indicate Requirement Levels" [KEYWORDS]. 51 2. The Metadata Disposition Type 53 A body part can be designated "metadata" if it contains metadata 54 for one or more other body parts in the containing multipart and is 55 unlikely to be useful if saved to a file by itself or viewed 56 independently. If an interpreting user agent sees an unknown media 57 type with a "metadata" disposition type, it SHOULD indicate in some 58 way that the body part is unlikely to be useful to the user. 60 For example, in a multipart/appledouble [MACMIME], the 61 application/applefile body part SHOULD have a "metadata" 62 disposition type as it is usually useless by itself. 64 In a multipart/security [MIME-SEC], the signature body part is 65 usually useless without the text it signs and thus would usually 66 have a disposition type of "metadata." 68 2. Amended Formal Syntax 70 This amends the formal syntax [ABNF] for "disposition-type" 71 [CDISP]: 73 disposition-type =/ "metadata" 75 3. Security Considerations 77 This does not add additional security considerations beyond those 78 which already apply to the Content-Disposition header field 79 [CDISP]. 81 4. References 83 [ABNF] Crocker, Overell, "Augmented BNF for Syntax Specifications: 84 ABNF", Work in progress: draft-ietf-drums-abnf-xx.txt 86 [CDISP] Troost, Dorner, Moore, "Communicating Presentation 87 Information in Internet Messages: The Content-Disposition Header 88 Field", RFC 2183, New Century Systems, Qualcomm Incorporated, 89 University of Tennessee, August 1997. 91 93 [MACMIME] Faltstrom P., Crocker, D., and E. Fair, "MIME 94 Encapsulation of Macintosh Files - MacMIME", RFC 1740, KTH, 95 Brandenburg Consulting, Apple Computer Inc., December 1994. 97 99 [MIME-IMB] Freed, Borenstein, "Mulitpurpose Internet Mail 100 Extensions (MIME) Part One: Format of Internet Message Bodies", RFC 101 2045, Innosoft, First Virtual, November 1996. 103 105 [MIME-SEC] Galvin, Murphy, Crocker, Freed, "Security Multiparts for 106 MIME: Multipart/Signed and Multipart/Encrypted", RFC 1847, Trusted 107 Information Systems, CyberCash, Innosoft International, October 108 1995. 110 112 5. Full Copyright Statement 114 Copyright (C) The Internet Society 1997. All Rights Reserved. 116 This document and translations of it may be copied and furnished to 117 others, and derivative works that comment on or otherwise explain 118 it or assist in its implmentation may be prepared, copied, 119 published and distributed, in whole or in part, without restriction 120 of any kind, provided that the above copyright notice and this 121 paragraph are included on all such copies and derivative works. 122 However, this document itself may not be modified in any way, such 123 as by removing the copyright notice or references to the Internet 124 Society or other Internet organizations, except as needed for the 125 purpose of developing Internet standards in which case the 126 procedures for copyrights defined in the Internet Standards process 127 must be followed, or as required to translate it into languages 128 other than English. 130 The limited permissions granted above are perpetual and will not be 131 revoked by the Internet Society or its successors or assigns. 133 This document and the information contained herein is provided on 134 an "AS IS" basis and THE INTERNET SOCIETY AND THE INTERNET 135 ENGINEERING TASK FORCE DISCLAIMS ALL WARRANTIES, EXPRESS OR 136 IMPLIED, INCLUDING BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF 137 THE INFORMATION HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED 138 WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE. 140 6. Author's Address 142 Chris Newman 143 Innosoft International, Inc. 144 1050 Lakes Drive 145 West Covina, CA 91790 USA 147 Email: chris.newman@innosoft.com