idnits 2.17.1 draft-finseth-eid-url-scheme-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. ** The abstract seems to contain references ([RFC2396]), which it shouldn't. Please replace those with straight textual mentions of the documents in question. 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 (2 November 1998) is 9306 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) ** Obsolete normative reference: RFC 2396 (Obsoleted by RFC 3986) Summary: 10 errors (**), 0 flaws (~~), 2 warnings (==), 2 comments (--). Run idnits with the --verbose option for more detailed information about the items above. -------------------------------------------------------------------------------- 2 INTERNET-DRAFT C. Finseth 3 Expires in six months U.S. Satellite Broadcasting 4 2 November 1998 6 The "eid" URL Scheme 7 draft-finseth-eid-url-scheme-00.txt 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 months 17 and may be updated, replaced, or obsoleted by other documents at any 18 time. It is inappropriate to use Internet-Drafts as reference 19 material or to cite them other than as "work in progress." 21 To view the entire list of current Internet-Drafts, please check the 22 "1id-abstracts.txt" listing contained in the Internet-Drafts Shadow 23 Directories on ftp.is.co.za (Africa), ftp.nordu.net (Northern 24 Europe), ftp.nis.garr.it (Southern Europe), munnari.oz.au (Pacific 25 Rim), ftp.ietf.org (US East Coast), or ftp.isi.edu (US West Coast). 27 Copyright Notice 29 Copyright (C) The Internet Society (1998). All Rights Reserved. 31 Abstract 33 This document defines a new URL scheme, "eid". This scheme provides 34 a mechanism by which the local application can reference data that 35 has been obtained by other, non-URL scheme means. The scheme is 36 intended to provide a general escape mechanism to allow access to 37 information for applications that are too specialized to justify 38 their own schemas. 40 Description 42 Some computer systems have more than one mechansim for obtaining 43 data. The data arrive at different times and use different methods 44 for labelling the information. The "eid" ("External ID") URL schema 45 provides a mechanism for a URL-aware application to specify the 46 identity of this external data. 48 The URLs are of the form: 50 eid: 52 The characters of the must drawn from the standard URL 53 character set. 55 The is interpreted in the application's environment and 56 is meaningful only in that environment. It follows that construction 57 of the requires knowledge of the application's 58 environment. 60 This schema does not specify the mechanism used to acquire the data 61 referenced by the . It assumes that either that data is 62 already available to the application or the contains 63 enough information to allow the application to obtain the data. 65 In sufficiently rich application environments there may be more than 66 one conceptual address space. Such environments may wish to use 67 identifiers of the form: 69 / 71 although any form is acceptable. 73 Syntax 75 eidurl := "eid:" identifier 76 identifier := *urlchar 78 where "urlchar" is imported from [RFC2396]. 80 Examples 82 One use of the eid schema would be to access data stored in 83 application memory. In this case, the could specify a 84 memory address. For example, if there were three fixed buffers at 85 addresses 0x00001000, 0x00002000, and 0x00003000, they could be 86 accessed by: 88 eid:0x00001000 89 eid:0x00002000 90 eid:0x00003000 92 Another example might be an application that reads stock market 93 quotations and stores the current values in a mini-database indexed 94 by the ticker symbol. For example: 96 eid:EK for Eastman Kodak Company 97 eid:F for Ford Motor Company 99 A third example might be a dialup application where the 100 specifies a telephone number, login sequence, and remote command to 101 execute. It might look like: 103 eid:555-1212,sample_user,sample_password,sample_command 105 Security Considerations 107 The very nature of this schema is to provide an escape mechanism and 108 by definition there cannot be a generic implementation of such a 109 mechanism. Thus, many URL-aware applications will not implement this 110 schema and so have no increased exposure. 112 Those applications that do implement this schema will do so in 113 application-specific ways. Hence, there cannot be an "across-the- 114 board" exposure from this schema. However, each application that 115 does implement this schema will have to provide its own security. 117 References 119 [RFC2396] Berners-Lee, T., Fielding, R., and L. Masinter, 120 "Uniform Resource Identifiers (URI): Generic Syntax", RFC 121 2396, August 1998. 123 Author's Address 125 Craig A. Finseth 126 U.S. Satellite Broadcasting 127 3415 University Ave 128 St Paul MN 55114 130 Phone: +1 651-659-7162 132 EMail: craig@finseth.com 134 Full Copyright Statement 136 Copyright (C) The Internet Society (1998). All Rights Reserved. 138 This document and translations of it may be copied and furnished to 139 others, and derivative works that comment on or otherwise explain it 140 or assist in its implmentation may be prepared, copied, published and 141 distributed, in whole or in part, without restriction of any kind, 142 provided that the above copyright notice and this paragraph are 143 included on all such copies and derivative works. However, this 144 document itself may not be modified in any way, such as by removing 145 the copyright notice or references to the Internet Society or other 146 Internet organizations, except as needed for the purpose of 147 developing Internet standards in which case the procedures for 148 copyrights defined in the Internet Standards process must be 149 followed, or as required to translate it into languages other than 150 English. 152 The limited permissions granted above are perpetual and will not be 153 revoked by the Internet Society or its successors or assigns. 155 This document and the information contained herein is provided on an 156 "AS IS" basis and THE INTERNET SOCIETY AND THE INTERNET ENGINEERING 157 TASK FORCE DISCLAIMS ALL WARRANTIES, EXPRESS OR IMPLIED, INCLUDING 158 BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF THE INFORMATION 159 HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED WARRANTIES OF 160 MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE."