idnits 2.17.1 draft-hoffman-prospero-uri-03.txt: Checking boilerplate required by RFC 5378 and the IETF Trust (see https://trustee.ietf.org/license-info): ---------------------------------------------------------------------------- ** It looks like you're using RFC 3978 boilerplate. You should update this to the boilerplate described in the IETF Trust License Policy document (see https://trustee.ietf.org/license-info), which is required now. -- Found old boilerplate from RFC 3978, Section 5.1.a on line 16. -- Found old boilerplate from RFC 3978, Section 5.5 on line 169. -- Found old boilerplate from RFC 3979, Section 5, paragraph 1 on line 146. -- Found old boilerplate from RFC 3979, Section 5, paragraph 2 on line 153. -- Found old boilerplate from RFC 3979, Section 5, paragraph 3 on line 159. ** The document seems to lack an RFC 3978 Section 5.1 IPR Disclosure Acknowledgement. ** This document has an original RFC 3978 Section 5.4 Copyright Line, instead of the newer IETF Trust Copyright according to RFC 4748. ** This document has an original RFC 3978 Section 5.5 Disclaimer, instead of the newer disclaimer which includes the IETF Trust according to RFC 4748. ** The document uses RFC 3667 boilerplate or RFC 3978-like boilerplate instead of verbatim RFC 3978 boilerplate. After 6 May 2005, submission of drafts without verbatim RFC 3978 boilerplate is not accepted. The following non-3978 patterns matched text found in the document. That text should be removed or replaced: This document is an Internet-Draft and is subject to all provisions of Section 3 of RFC 3667. By submitting this Internet-Draft, each author represents that any applicable patent or other IPR claims of which he or she is aware have been or will be disclosed, and any of which he or she becomes aware will be disclosed, in accordance with Section 6 of BCP 79. Checking nits according to https://www.ietf.org/id-info/1id-guidelines.txt: ---------------------------------------------------------------------------- == 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 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.) 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 (January 2005) is 7040 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 informational reference (is this intentional?): RFC 1738 (Obsoleted by RFC 4248, RFC 4266) -- Obsolete informational reference (is this intentional?): RFC 2396 (Obsoleted by RFC 3986) -- No information found for draft-fielding-uri-rfc2396bis-nn - is the name correct? Summary: 6 errors (**), 0 flaws (~~), 2 warnings (==), 10 comments (--). Run idnits with the --verbose option for more detailed information about the items above. -------------------------------------------------------------------------------- 2 Network Working Group P. Hoffman 3 Internet-Draft VPN Consortium 4 Expires: July 2, 2005 January 2005 6 The prospero URI Scheme 7 draft-hoffman-prospero-uri-03.txt 9 Status of this Memo 11 This document is an Internet-Draft and is subject to all provisions 12 of section 3 of RFC 3667. By submitting this Internet-Draft, each 13 author represents that any applicable patent or other IPR claims of 14 which he or she is aware have been or will be disclosed, and any of 15 which he or she become aware will be disclosed, in accordance with 16 RFC 3668. 18 Internet-Drafts are working documents of the Internet Engineering 19 Task Force (IETF), its areas, and its working groups. Note that 20 other groups may also distribute working documents as 21 Internet-Drafts. 23 Internet-Drafts are draft documents valid for a maximum of six months 24 and may be updated, replaced, or obsoleted by other documents at any 25 time. It is inappropriate to use Internet-Drafts as reference 26 material or to cite them other than as "work in progress." 28 The list of current Internet-Drafts can be accessed at 29 http://www.ietf.org/ietf/1id-abstracts.txt. 31 The list of Internet-Draft Shadow Directories can be accessed at 32 http://www.ietf.org/shadow.html. 34 This Internet-Draft will expire on July 2, 2005. 36 Copyright Notice 38 Copyright (C) The Internet Society (2005). 40 Abstract 42 This document specifies the prospero1 Uniform Resource Identifier 43 (URI) scheme that was originally specified in RFC 1738. The purpose 44 of this document is to allow RFC 1738 to be made obsolete while 45 keeping the information about the scheme on standards track. 47 1. Introduction 49 URIs were previously defined in RFC 2396 [RFC2396], which was updated 50 by draft-fielding-uri-rfc2396bis [2396bis]. Those documents also 51 specify how to define schemes for URIs. 53 The first definition for many URI schemes appeared in RFC 1738 54 [RFC1738]. Because that document has been made obsolete, this 55 document copies the prospero URI scheme from it to allow that 56 material to remain on standards track. 58 2. Scheme Definition 60 The prospero URL scheme is used to designate resources that are 61 accessed through the Prospero Directory Service. The Prospero 62 protocol is described in the original Prospero specification [PROSP]. 64 Historical note: The Prospero protocol was not widely implemented and 65 almost no Prospero servers are in use today. 67 A prospero URL takes the form: 69 prospero://:/;= 71 If : is omitted, the port defaults to 1525. No username or 72 password is allowed. 74 The is the host-specific object name in the Prospero 75 protocol, suitably encoded. This name is opaque and interpreted by 76 the Prospero server. The semicolon ";" is reserved and may not 77 appear without quoting in the . 79 Prospero URLs are interpreted by contacting a Prospero directory 80 server on the specified host and port to determine appropriate access 81 methods for a resource, which might themselves be represented as 82 different URLs. External Prospero links are represented as URLs of 83 the underlying access method and are not represented as Prospero 84 URLs. 86 Note that a slash "/" may appear in the without quoting and 87 no significance may be assumed by the application. Though slashes 88 may indicate hierarchical structure on the server, such structure is 89 not guaranteed. Note that many s begin with a slash, in 90 which case the host or port will be followed by a double slash: the 91 slash from the URL syntax, followed by the initial slash from the 92 . (E.g., designates 93 a of "/pros/name".) 95 In addition, after the , optional fields and values 96 associated with a Prospero link may be specified as part of the URL. 97 When present, each field/value pair is separated from each other and 98 from the rest of the URL by a ";" (semicolon). The name of the field 99 and its value are separated by a "=" (equal sign). If present, these 100 fields serve to identify the target of the URL. For example, the 101 OBJECT-VERSION field can be specified to identify a specific version 102 of an object. 104 3. Security Considerations 106 There are many security considerations for URI schemes discussed in 107 [2396bis]. [PROSP] uses passwords in the clear for authentication, 108 and offers no privacy, both of which are considered extremely unsafe 109 in current practice. 111 4 Informative References 113 [RFC1738] Berners-Lee, T., Masinter, L. and M. McCahill, "Uniform 114 Resource Locators (URL)", RFC 1738, December 1994. 116 [RFC2396] Berners-Lee, T., Fielding, R. and L. Masinter, "Uniform 117 Resource Identifiers (URI): Generic Syntax", RFC 2396, 118 August 1998. 120 [2396bis] Berners-Lee, T., Fielding, R. and L. Masinter, "Uniform 121 Resource Identifiers (URI): Generic Syntax", work in 122 progress, draft-fielding-uri-rfc2396bis-nn.txt, July 2004. 124 [PROSP] Neuman, B. and S. Augart, "The Prospero Protocol", 125 USC/Information Sciences Institute , June 1993. 127 Author's Address 129 Paul Hoffman 130 VPN Consortium 131 127 Segre Place 132 Santa Cruz, CA 95060 133 US 135 EMail: paul.hoffman@vpnc.org 137 Intellectual Property Statement 139 The IETF takes no position regarding the validity or scope of any 140 Intellectual Property Rights or other rights that might be claimed to 141 pertain to the implementation or use of the technology described in 142 this document or the extent to which any license under such rights 143 might or might not be available; nor does it represent that it has 144 made any independent effort to identify any such rights. Information 145 on the procedures with respect to rights in RFC documents can be 146 found in BCP 78 and BCP 79. 148 Copies of IPR disclosures made to the IETF Secretariat and any 149 assurances of licenses to be made available, or the result of an 150 attempt made to obtain a general license or permission for the use of 151 such proprietary rights by implementers or users of this 152 specification can be obtained from the IETF on-line IPR repository at 153 http://www.ietf.org/ipr. 155 The IETF invites any interested party to bring to its attention any 156 copyrights, patents or patent applications, or other proprietary 157 rights that may cover technology that may be required to implement 158 this standard. Please address the information to the IETF at 159 ietf-ipr@ietf.org. 161 Disclaimer of Validity 163 This document and the information contained herein are provided on an 164 "AS IS" basis and THE CONTRIBUTOR, THE ORGANIZATION HE/SHE REPRESENTS 165 OR IS SPONSORED BY (IF ANY), THE INTERNET SOCIETY AND THE INTERNET 166 ENGINEERING TASK FORCE DISCLAIM ALL WARRANTIES, EXPRESS OR IMPLIED, 167 INCLUDING BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF THE 168 INFORMATION HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED 169 WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE. 171 Copyright Statement 173 Copyright (C) The Internet Society (2005). This document is subject 174 to the rights, licenses and restrictions contained in BCP 78, and 175 except as set forth therein, the authors retain all their rights. 177 Acknowledgment 179 Funding for the RFC Editor function is currently provided by the 180 Internet Society.