idnits 2.17.1 draft-ietf-mixer-images-00.txt: Checking boilerplate required by RFC 5378 and the IETF Trust (see https://trustee.ietf.org/license-info): ---------------------------------------------------------------------------- ** Cannot find the required boilerplate sections (Copyright, IPR, etc.) in this document. Expected boilerplate is as follows today (2024-04-25) according to https://trustee.ietf.org/license-info : IETF Trust Legal Provisions of 28-dec-2009, Section 6.a: This Internet-Draft is submitted in full conformance with the provisions of BCP 78 and BCP 79. IETF Trust Legal Provisions of 28-dec-2009, Section 6.b(i), paragraph 2: Copyright (c) 2024 IETF Trust and the persons identified as the document authors. All rights reserved. IETF Trust Legal Provisions of 28-dec-2009, Section 6.b(i), paragraph 3: This document is subject to BCP 78 and the IETF Trust's Legal Provisions Relating to IETF Documents (https://trustee.ietf.org/license-info) in effect on the date of publication of this document. Please review these documents carefully, as they describe your rights and restrictions with respect to this document. Code Components extracted from this document must include Simplified BSD License text as described in Section 4.e of the Trust Legal Provisions and are provided without warranty as described in the Simplified BSD License. Checking nits according to https://www.ietf.org/id-info/1id-guidelines.txt: ---------------------------------------------------------------------------- ** Missing document type: Expected "INTERNET-DRAFT" in the upper left hand corner of the first page ** 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 6 months document validity. ** 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 Abstract section. ** The document seems to lack an Introduction section. (A line matching the expected section header was found, but with an unexpected indentation: ' 1. Introduction' ) ** The document seems to lack a Security Considerations section. (A line matching the expected section header was found, but with an unexpected indentation: ' 4. Security considerations' ) ** 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 an Authors' Addresses Section. Miscellaneous warnings: ---------------------------------------------------------------------------- -- 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 () is 739383 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 section? 'MIME' on line 108 looks like a reference Summary: 12 errors (**), 0 flaws (~~), 1 warning (==), 3 comments (--). Run idnits with the --verbose option for more detailed information about the items above. -------------------------------------------------------------------------------- 1 draft X.400 image body parts Nov 95 3 Title 5 Tue Nov 21 15:32:07 MET 1995 7 Harald Tveit Alvestrand 8 UNINETT 9 Harald.T.Alvestrand@uninett.no 11 Status of this Memo 13 This draft document is being circulated for comment. 15 Please send comments to the author, or to the MIXER list . 18 The following text is required by the Internet-draft rules: 20 This document is an Internet Draft. Internet Drafts are working 21 documents of the Internet Engineering Task Force (IETF), its 22 Areas, and its Working Groups. Note that other groups may also 23 distribute working documents as Internet Drafts. 25 Internet Drafts are draft documents valid for a maximum of six 26 months. Internet Drafts may be updated, replaced, or obsoleted by 27 other documents at any time. It is not appropriate to use 28 Internet Drafts as reference material or to cite them other than 29 as a "working draft" or "work in progress." 31 Please check the I-D abstract listing contained in each Internet 32 Draft directory to learn the current status of this or any other 33 Internet Draft. 35 The file name of this version is draft-ietf-mixer-images-00.txt 37 draft X.400 image body parts Nov 95 39 1. Introduction 41 This document contains the body parts defined in RFC 1495 for 42 carrying image formats that were originally defined in MIME 43 through an X.400 system. 45 This document is an Experimental standard; if it turns out to be 46 useful and widely deployed, it can be moved onto the standards 47 track. 49 Editor's note 50 It is trivially easy to define new OIDs for these things as 51 FTAM body parts. This gives us a much more capable (AND 52 complex) encapsulation. Group input into this decision is 53 sought. 55 2. Newly defined X.400 body parts 57 2.1. The JPEG body part 59 The following Extended Body Part is defined for JPEG data streams. 60 It has no parameters. 62 jpeg-body-part EXTENDED-BODY-PART-TYPE 63 DATA OCTET STRING 64 ::= mime-jpeg-body 66 mime-jpeg-body OBJECT IDENTIFIER ::= 67 { mixer-bp-data 3 } 69 The content is as defined in [MIME]. 71 2.2. The GIF body part 73 The following Extended Body Part is defined for GIF data streams. 74 It has no parameters. 76 gif-body-part EXTENDED-BODY-PART-TYPE 77 DATA OCTET STRING 79 draft X.400 image body parts Nov 95 81 ::= mime-gif-body 83 mime-gif-body OBJECT IDENTIFIER ::= 84 { mixer-bp-data 4 } 86 The content is as defined in [MIME]. 88 3. Defined equivalences with MIME types 90 3.1. image/jpeg - jpeg-body-part 92 X.400 Body Part: Extended Body Part, OID jpeg-body-part 93 MIME Content-Type: image/jpeg 94 Conversion: None 96 3.2. image/gif - gif-body-part 98 X.400 Body Part: Extended Body Part, OID gif-body-part 99 MIME Content-Type: image/gif 100 Conversion: None 102 4. Security considerations 104 Security issues are not consiered in this memo. 106 5. REFERENCES 108 [MIME] 109 RFC 1521: N. Borenstein, N. Freed, "MIME (Multipurpose 110 Internet Mail Extensions) Part One: Mechanisms for 111 Specifying and Describing the Format of Internet Message 112 Bodies", 09/23/1993 114 draft X.400 image body parts Nov 95