idnits 2.17.1 draft-masinter-url-data-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-16) 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 -- however, there's a paragraph with a matching beginning. Boilerplate error? ** 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 == The page length should not exceed 58 lines per page, but there was 1 longer page, the longest (page 1) being 98 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 an Authors' Addresses Section. ** There is 1 instance of lines with control characters in the document. 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 (February 2, 1996) is 10301 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) No issues found here. Summary: 10 errors (**), 0 flaws (~~), 2 warnings (==), 2 comments (--). Run idnits with the --verbose option for more detailed information about the items above. -------------------------------------------------------------------------------- 1 Internet-Draft 2 draft-masinter-url-data-00.txt 3 February 2, 1996 4 Expires in 6 months 6 "Data: URL scheme" 8 Status of This Memo 10 This document is an Internet-Draft. Internet-Drafts are working 11 documents of the Internet Engineering Task Force (IETF), its 12 areas, and its working groups. Note that other groups may also 13 distribute working documents as Internet-Drafts. 15 Internet-Drafts are draft documents valid for a maximum of six 16 months and may be updated, replaced, or obsoleted by other 17 documents at any time. It is inappropriate to use Internet- 18 Drafts as reference material or to cite them other than as 19 ``work in progress.'' 21 To learn the current status of any Internet-Draft, please check 22 the ``1id-abstracts.txt'' listing contained in the Internet- 23 Drafts Shadow Directories on ftp.is.co.za (Africa), 24 nic.nordu.net (Europe), munnari.oz.au (Pacific Rim), 25 ds.internic.net (US East Coast), or ftp.isi.edu (US West Coast). 27 Abstract 29 A new URL scheme, "data:", is defined. It allows inclusion of small 30 data items as "immediate" data, as if it had been included externally. 32 Description 34 Some applications that use URLs also have a need to embed (small) 35 media type data directly inline. This proposal includes a new 36 URL scheme that would work like 'immediate addressing'. The format 37 of the URL is as follows: 39 data:[;base64], 41 where is a media type (with optional parameters, etc.). 42 The token "base64" means that the value is encoded as base64. 43 Otherwise, the value is encoded with the standard %xx URL encoding. 45 The mediatype, if left blank, defaults to text/plain;charset=US-ASCII. 46 As a shorthand, "text/plain" can be omitted but the charset parameter 47 supplied. 49 Examples: 51 This is only to be used for very short data types. For example, 53 data:,A%20brief%20note 55 encodes the string "A brief note" 57 might be useful in a footnote link, while, 59 Larry 69 could be used for a small inline image in a HTML document. 71 This is only appropriate for delivery of very small inline data. The 72 embedded image above is probably near the limit of utility. For 73 anything else larger, or where the base64 encoding is problematic or 74 cumbersome, immediate data references within URLs are inappropriate. 76 History 78 This idea was originally proposed August 1995 by the author, and 79 recently revised because of the appearance of a (weaker) proposal in 80 a HTML INSERT proposal. This version allows eliding the media type, 81 packs the indication of the base64 encoding more tightly, and 82 eliminates the proposal to allow quoted printable, since the encoding 83 would not easily yield valid URLs without additional %xx encoding, 84 which itself is sufficient. 86 Security 88 Immediate data URLs introduce no new security considerations. 90 Author contact information: 92 Larry Masinter 93 Xerox Palo Alto Research Center 94 3333 Coyote Hill Road 95 Palo Alto, CA 94304 96 masinter@parc.xerox.com