idnits 2.17.1 draft-ietf-svrloc-wpyp-02.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-19) 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 4 longer pages, the longest (page 2) being 60 lines == It seems as if not all pages are separated by form feeds - found 0 form feeds but 5 pages 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.) ** The document seems to lack separate sections for Informative/Normative References. All references will be assumed normative when checking for downward references. ** There are 6 instances of too long lines in the document, the longest one being 20 characters in excess of 72. 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 (October 1997) is 9683 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) == Unused Reference: '7' is defined on line 168, but no explicit reference was found in the text -- Possible downref: Non-RFC (?) normative reference: ref. '1' -- Possible downref: Non-RFC (?) normative reference: ref. '2' ** Obsolete normative reference: RFC 1959 (ref. '3') (Obsoleted by RFC 2255) -- Possible downref: Non-RFC (?) normative reference: ref. '4' -- Possible downref: Normative reference to a draft: ref. '5' ** Obsolete normative reference: RFC 1777 (ref. '8') (Obsoleted by RFC 3494) ** Downref: Normative reference to an Informational RFC: RFC 1945 (ref. '9') ** Obsolete normative reference: RFC 2068 (ref. '10') (Obsoleted by RFC 2616) ** Downref: Normative reference to an Historic RFC: RFC 1835 (ref. '11') -- Possible downref: Non-RFC (?) normative reference: ref. '12' Summary: 14 errors (**), 0 flaws (~~), 4 warnings (==), 7 comments (--). Run idnits with the --verbose option for more detailed information about the items above. -------------------------------------------------------------------------------- 2 Internet-Draft Ryan Moats 3 draft-ietf-svrloc-wpyp-02.txt AT&T 4 Expires in six months October 1997 6 The 'wp' and 'yp' Abstract Service Types 7 Filename: draft-ietf-svrloc-wpyp-02.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 13 areas, and its working groups. Note that other groups may also 14 distribute working documents as Internet-Drafts. 16 Internet-Drafts are draft documents valid for a maximum of six 17 months and may be updated, replaced, or obsoleted by other 18 documents at any time. It is inappropriate to use Internet- 19 Drafts as reference material or to cite them other than as ``work 20 in progress.'' 22 To learn the current status of any Internet-Draft, please check 23 the ``1id-abstracts.txt'' listing contained in the Internet- 24 Drafts Shadow Directories on ftp.is.co.za (Africa), nic.nordu.net 25 (Europe), munnari.oz.au (Pacific Rim), ds.internic.net (US East 26 Coast), or ftp.isi.edu (US West Coast). 28 Abstract 30 This document presents definitions for the ''wp'' (white pages) and 31 ''yp'' (yellow pages) abstract services. 33 1. Introduction 35 In "Advertising Services" [1], several abstract services are 36 proposed. As specified in [2], the "wp" (white pages) and "yp" 37 (yellow pages) abstract services are documented here. 39 2. The "wp" Abstract Service 41 The "wp" abstract service is for locating people via directory or 42 "white pages" services. Version 0.0 of this service specifies four 43 protocols for accessing such services: LDAP, WHOIS++, CCSO/Ph and 44 HTTP. 46 ---------------------------template begins here----------------------- 47 type = wp 49 version = 0.0 51 language = EN 53 description = 54 The WP Abstract Service is for locating people using either LDAP, WHOIS, CCSO/Ph or HTTP 56 url-syntax = 57 url-path = ldapurl / whoisppurl / phurl / httpurl 58 ldapurl = url as defined in [3] 59 whoisppurl = url as defined in [4] 60 httpurl = url as defined in [5] 61 phurl = "ph://" hostport 62 hostport = host [ ":" port ] 63 host = hostname / hostnumber 64 hostname = *( domainlavel "." ) toplabel 65 domainlabel = alphanum / alphanum * [alphanum / "-"] alphanum 66 toplabel = alpha / alpha * [alphanum / "-"] alphanum 67 hostnumber = ipv4-number / ipv6-number 68 ipv4-number = 1*3digit 3*3("." 1*3digit) 69 ipv6-number = 32*hex 70 3digit = digit digit digit 71 port = 1*digit 72 ; A port number must be included if the 73 ; protocol field does not have an IANA 74 ; assigned port number. 75 alphanum = alpha / digit 76 alpha = "a" / "b" / "c" / "d" / "e" / "f" / "g" / 77 "h" / "i" / "j" / "k" / "l" / "m" / "n" / 78 "o" / "p" / "q" / "r" / "s" / "t" / "u" / 79 "v" / "w" / "x" / "y" / "z" / 80 "A" / "B" / "C" / "D" / "E" / "F" / "G" / 81 "H" / "I" / "J" / "K" / "L" / "M" / "N" / 82 "O" / "P" / "Q" / "R" / "S" / "T" / "U" / 83 "V" / "W" / "X" / "Y" / "Z" 84 digit = "0" / "1" / "2" / "3" / "4" / "5" / "6" / 85 "7" / "8" / "9" 86 ---------------------------template ends here------------------------- 88 3. The "yp" Abstract Service 90 The "yp" abstract service is for locating resources on the Internet 91 and version 0.0 specifies three protocols for accessing such 92 services: Z39.50, HTTP, and WHOIS++. 94 ---------------------------template begins here----------------------- 95 type = yp 97 version = 0.0 99 language = EN 101 description = 102 The yp Abstract Service is for locating resources either via Z39.50, HTTP or WHOIS. 104 url-syntax = 105 url-path = z3950url / httpurl / whoisppurl 106 z3950url = url as defined in [6] 107 httpurl = url as defined in [5] 108 whoisppurl = url as defined in [4] 109 ---------------------------template ends here------------------------- 111 4. Contact Information 113 The contact point for version 0.0 of both of these templates is the 114 author. 116 5. Security Considerations 118 Both of these abstract services inherit the security considerations 119 of the "service:" URL scheme as specified in [2]. As these services 120 are both abstract, they further inherit considerations from the 121 protocol used to provide the underlying concrete services as 122 discussed below. 124 5.1 Considerations for the "wp" service 126 Since the "wp" abstract service can use any of LDAP, HTTP, WHOIS or 127 CCSO/Ph, it inherits the security considerations for each of these 128 protocols. See [3] and [8] for LDAP, [9] and [10] for HTTP, [4] and 129 [11] for WHOIS, and [12] for CCSO/Ph. 131 5.2 Considerations for the "yp" service Since the "yp" abstract service 132 can use any of HTTP, Z39.50, or WHOIS, it inherits the security 133 considerations for each of these protocols. See [9] and [10] for HTTP, 134 [6] for Z39.50, and [4] and [11] for WHOIS. 136 6. Acknowledgments 138 This work described in this document is partially supported by the 139 National Science Foundation, Cooperative Agreement NCR-9218179. 141 7. References 143 Request For Comments (RFC) and Internet Drafts documents are 144 available from and numerous mirror sites 146 [1] R. Moats, M. Hamilton, "Advertising Services," 147 Internet Draft (work in progress), February 1997. 149 [2] C. Perkins, E. Guttman, J. Kempf, "Service Tem- 150 plates and 'service:' Schemes," Internet Draft 151 (work in progress), October 1997. 153 [3] T. Howes, M. Smith, "An LDAP URL Format," RFC 1959, 154 June 1996. 156 [4] M. Hamilton, "WHOIS++ URL Specification," Internet 157 Draft (work in progress), May 1997. 159 [5] T. Berners-Lee, R. Fielding, and L. Masinter, "Uni- 160 form Resource Locators (URL): Generic Syntax and 161 Semantics," RFC1738 as amended by RFC1808 and 162 updated by draft-fielding-url-syntax-09.txt, May 163 1997. (work in progress). 165 [6] R. Denenberg, J. Kunze, D. Lynch, "Uniform Resource 166 Locators for Z39.50," RFC 2056, November 1996. 168 [7] J. Veizades, E. Guttman, C. Perkins, S. Kaplan, 169 "Service Location Protocol," RFC 2165, June 1997. 171 [8] W. Yeong, T. Howes, S. Kille, "Lightweight Direc- 172 tory Access Protocol", RFC 1777, March 1995. 174 [9] T. Berners-Lee, R. Fielding, H. Frystyk, "Hypertext 175 Transfer Protocol -- HTTP/1.0", RFC 1945, May 1996. 177 [10] R. Fielding (et.al.), "Hypertext Transfer Protocol 178 -- HTTP/1.1", RFC 2068, January 1997. 180 [11] P. Deutsch, R. Schoultz, P. Faltstrom, C. Weider, 181 "Architecture of the WHOIS++ Service", RFC 1835, 182 August 1995. 184 [12] P. Pomes, R. Hedberg, "The CCSO Nameserver (Ph) 185 Architecture", Internet Draft (work in progress), 186 May 1997. 188 8. Author's addresses 190 Ryan Moats 191 AT&T 192 15621 Drexel Circle 193 Omaha, NE 68135-2358 194 USA 196 Phone: +1 402 894-9456 197 EMail: jayhawk@att.com