idnits 2.17.1 draft-hoffman-wais-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 159. -- Found old boilerplate from RFC 3979, Section 5, paragraph 1 on line 136. -- Found old boilerplate from RFC 3979, Section 5, paragraph 2 on line 143. -- Found old boilerplate from RFC 3979, Section 5, paragraph 3 on line 149. ** 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 7041 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 wais URI Scheme 7 draft-hoffman-wais-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 wais Uniform Resource Identifier (URI) 43 scheme that was originally specified in RFC 1738. The purpose of 44 this document is to allow RFC 1738 to be made obsolete while keeping 45 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 wais URI scheme from it to allow that material to 56 remain on standards track. 58 2. Scheme Definition 60 The WAIS URL scheme is used to designate WAIS databases, searches, or 61 individual documents available from a WAIS database. The WAIS 62 protocol is described in RFC 1625 [RFC1625]. Although the WAIS 63 protocol is based on Z39.50-1988, the WAIS URL scheme is not intended 64 for use with arbitrary Z39.50 services. 66 Historical note: The WAIS protocol was not widely implemented and 67 almost no WAIS servers are in use today. 69 A WAIS URL takes one of the following forms: 71 wais://:/ 72 wais://:/? 73 wais://:/// 75 If : is omitted, the port defaults to 210. The first form 76 designates a WAIS database that is available for searching. The 77 second form designates a particular search. is the name 78 of the WAIS database being queried. 80 The third form designates a particular document within a WAIS 81 database to be retrieved. In this form is the WAIS 82 designation of the type of the object. Many WAIS implementations 83 require that a client know the "type" of an object prior to 84 retrieval, the type being returned along with the internal object 85 identifier in the search response. The is included in the 86 URL in order to allow the client interpreting the URL adequate 87 information to actually retrieve the document. 89 The of a WAIS URL consists of the WAIS document-id. The WAIS 90 document-id should be treated opaquely; it may only be decomposed by 91 the server that issued it. 93 3. Security Considerations 95 There are many security considerations for URI schemes discussed in 96 [2396bis]. There are no security considerations listed in [RFC1625], 97 but it should be noted that there is no privacy nor authentication 98 specified in the WAIS protocol. 100 4 Informative References 102 [RFC1738] Berners-Lee, T., Masinter, L. and M. McCahill, "Uniform 103 Resource Locators (URL)", RFC 1738, December 1994. 105 [RFC2396] Berners-Lee, T., Fielding, R. and L. Masinter, "Uniform 106 Resource Identifiers (URI): Generic Syntax", RFC 2396, 107 August 1998. 109 [2396bis] Berners-Lee, T., Fielding, R. and L. Masinter, "Uniform 110 Resource Identifiers (URI): Generic Syntax", work in 111 progress, draft-fielding-uri-rfc2396bis-nn.txt. 113 [RFC1625] St. Pierre, M., Fullton, J., Gamiel, K., Goldman, J., 114 Kahle, B., Kunze, J., Morris, H. and F. Schiettecatte, 115 "WAIS over Z39.50-1988", RFC 1625, June 1994. 117 Author's Address 119 Paul Hoffman 120 VPN Consortium 121 127 Segre Place 122 Santa Cruz, CA 95060 123 US 125 EMail: paul.hoffman@vpnc.org 127 Intellectual Property Statement 129 The IETF takes no position regarding the validity or scope of any 130 Intellectual Property Rights or other rights that might be claimed to 131 pertain to the implementation or use of the technology described in 132 this document or the extent to which any license under such rights 133 might or might not be available; nor does it represent that it has 134 made any independent effort to identify any such rights. Information 135 on the procedures with respect to rights in RFC documents can be 136 found in BCP 78 and BCP 79. 138 Copies of IPR disclosures made to the IETF Secretariat and any 139 assurances of licenses to be made available, or the result of an 140 attempt made to obtain a general license or permission for the use of 141 such proprietary rights by implementers or users of this 142 specification can be obtained from the IETF on-line IPR repository at 143 http://www.ietf.org/ipr. 145 The IETF invites any interested party to bring to its attention any 146 copyrights, patents or patent applications, or other proprietary 147 rights that may cover technology that may be required to implement 148 this standard. Please address the information to the IETF at 149 ietf-ipr@ietf.org. 151 Disclaimer of Validity 153 This document and the information contained herein are provided on an 154 "AS IS" basis and THE CONTRIBUTOR, THE ORGANIZATION HE/SHE REPRESENTS 155 OR IS SPONSORED BY (IF ANY), THE INTERNET SOCIETY AND THE INTERNET 156 ENGINEERING TASK FORCE DISCLAIM ALL WARRANTIES, EXPRESS OR IMPLIED, 157 INCLUDING BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF THE 158 INFORMATION HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED 159 WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE. 161 Copyright Statement 163 Copyright (C) The Internet Society (2005). This document is subject 164 to the rights, licenses and restrictions contained in BCP 78, and 165 except as set forth therein, the authors retain all their rights. 167 Acknowledgment 169 Funding for the RFC Editor function is currently provided by the 170 Internet Society.