idnits 2.17.1 draft-needleman-mime-ill-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-26) 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 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. == The page length should not exceed 58 lines per page, but there was 1 longer page, the longest (page 1) being 212 lines 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 are 19 instances of too long lines in the document, the longest one being 4 characters in excess of 72. ** There are 67 instances of lines with control characters in the document. ** The abstract seems to contain references ([BER]), which it shouldn't. Please replace those with straight textual mentions of the documents in question. Miscellaneous warnings: ---------------------------------------------------------------------------- == Line 70 has weird spacing: '...ptional param...' == Line 144 has weird spacing: '...rmation and D...' == Unrecognized Status in 'Category: Informational United Kingdom', assuming Proposed Standard (Expected one of 'Standards Track', 'Full Standard', 'Draft Standard', 'Proposed Standard', 'Best Current Practice', 'Informational', 'Experimental', 'Informational', 'Historic'.) -- 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 (September 1998) is 9355 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) -- Possible downref: Non-RFC (?) normative reference: ref. 'BER' Summary: 12 errors (**), 0 flaws (~~), 4 warnings (==), 3 comments (--). Run idnits with the --verbose option for more detailed information about the items above. -------------------------------------------------------------------------------- 1 INTERNET DRAFT EXPIRES in six months INTERNET DRAFT 3 Internet Draft Ruth Moulton 4 Category: Informational United Kingdom 6 Mark Needleman 7 University of California 9 September 1998 11 MIME Types for Use with the ISO ILL Protocol 12 14 Status of This Memo 16 This document is an Internet-Draft. Internet-Drafts are working documents 17 of the Internet Engineering Task Force (IETF), its areas, and its working 18 groups. Note that other groups may also distribute working documents as 19 Internet-Drafts. 21 Internet-Drafts are draft documents valid for a maximum of six months and 22 may be updated, replaced, or obsoleted by other documents at any time. It 23 is inappropriate to use Internet-Drafts as reference material or to cite 24 them other than as "work in progress." 26 To learn the current status of any Internet-Draft, please check the 27 "1id-abstracts.txt" listing contained in the Internet-Drafts Shadow 28 Directories on ftp.is.co.za (Africa), nic.nordu.net (Europe), 29 munnari.oz.au (Pacific Rim), ds.internic.net (US East Coast), or 30 ftp.isi.edu (US West Coast). 32 Distribution of this document is unlimited. 34 Abstract 36 This memorandum describes a set of MIME types for use with the ISO 37 Interlibrary Loan Protocol (ISO 10160/10160). Two mime types are specified 38 below. 40 The first is a media type to carry objects which are BER [BER] encoded 41 ISO ILL Protocol Data Units (PDU's). BER are the basic Encoding Rules used 42 to encode PDU's which have been described using ASN.1 (Abstract Syntax 43 Notation 1) [ASN.1] . 45 The second is for use with the associated document delivery instructions. 46 Document Delivery Instructions (DDI) is an emerging protocol which enables 47 automatic electronic delivery of items. It allows a request management 48 system (which might have received a request for an item via the ISO 49 Interlibrary Loan Protocol (ISO 10160/10161)) to pass details of the 50 request, item, and delivery, to a delivery module, and to receive back 51 reports on the delivery process or arrival of an item. It is currently 52 being submitted to the ISO TC46/SC4/WG4 committee for approval as an ISO 53 standard. 55 Registration Information 57 Media type name: application 58 Media subtype name: iso-10161-1-ill - for BER encoded ISO ILL APDU's 60 Media type name: application 61 Media subtype name: ill-ddi - For associated Document Delivery Instructions 63 Required Parameter: transfer-encoding 65 For BER-encoded PDU's or DDI's, the only current legal value of this 66 parameter is: 68 iso-8825-ber 70 Optional parameter: iso-10161-apdu-type 72 Valid values are: 74 ILL-Request 75 Forward-Notification 76 Shipped 77 IL-Answer 78 Conditional-Reply 79 Cancel 80 Cancel-Reply 81 Received 82 Recall 83 Returned 84 Checked-In 85 Overdue 86 Renew 87 Renew-Answer 88 Lost 89 Damaged 90 Message 91 Status-Query 92 Status-Or-Error-Report 93 Expired 95 This parameter is optional and can be provided for informational or 96 diagnostic purposes. The value of the PDU or DDI type can be determined 97 from the actual data sent. The use and format of the PDU's and DDI's is 98 defined in the relevant protocol documents which describe them. 100 Examples 102 Content-Type: application/iso-10161-1-ill; transfer-encoding=iso-8825-ber; 103 iso-10161-apdu-type=Recall; 105 Content-Type: application/ill-ddi; transfer-encoding=iso-8825-ber; 107 Encoding 109 The recommended encoding for BER encoded PDU's is Base64 111 PDU's per Message 113 When used to send BER encoded PDU's or DDI's. Each MIME body part will 114 carry at most one BER encoded PDU or DDI. However, a single MIME message 115 containing multiple body parts can be used to transport more than one BER 116 PDU and or DDI. 118 Security Considerations 120 There are no known security risks associated with transmitting BER encoded 121 PDU's in general. However, a particular BER encoded PDU or DDI may have 122 security considerations that make it inappropriate for transmittal through 123 public data networks unless appropriate protection mechanisms, like 124 encryption, are used. Such a situation might occur, for example, when 125 organizations are exchanging documents that contain secure or classified 126 information and it is necessary to keep information about both the material 127 being exchanged and the exchanging partners confidential. 129 Interoperability Considerations 131 BER is an international standard for encoding data meant to be transferred 132 between two systems that may store data in different local formats 133 internally [BER]. 135 References 137 [BER] ISO/IEC 8825:1990 Information Technology - Open Systems 138 Interconnection - Specification of Basic Encoding Rules for Abstract Syntax 139 Notation One (ASN.1) 141 [ASN.1] ISO/IEC 8824:1990 Information Technology - Open Systems 142 Interconnection - Specification of Abstract Syntax Notation One (ASN.1) 144 ISO 10160:1997 Information and Documentation - Open Systems 145 Interconnection - Interlibrary Loan Application Service Definition 147 ISO 10161-1:1997 Information and Documentation - Open Systems 148 Interconnection - Interlibrary Loan Application Protocol Specification - 149 Part 1: Protocol Specification 151 Additional Information: 153 The National Library of Canada has been designated the maintenance agency 154 for the ISO ILL protocol. For more information on this MIME type contact: 156 Barbara Shuh 157 Library Systems Analyst 158 Information Analysis and Standards 159 Information and Technology Services 160 National Library of Canada 162 Telephone: (819) 994-6969 163 Fax: (819) 994-6835 164 email: barbara.shuh@nlc-bnc.ca 166 Mailing Address: 167 395 Wellington Street 168 Ottawa, Ontario CANADA 169 K1A 0N4 171 Authors' Addresses 173 Ruth Moulton 174 Consultant 175 65 Tetherdown 176 London N10 1NH 177 United Kingdom 178 Phone: +44 (181) 883 5823 179 Email: ruth@muswell.demon.co.uk 181 Mark Needleman 182 University of California 183 California Digital Library 184 1111 Franklin Street Room 7305 185 Oakland, CA 94607-5200 186 USA 187 Phone: +1 (510) 987-0530 188 Fax: +1 (510) 763-2471 189 Email: Mark.Needleman@ucop.edu