idnits 2.17.1 draft-ietf-svrloc-wpyp-04.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. == 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 (February 1999) is 9202 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 198, 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') ** Downref: Normative reference to an Informational RFC: RFC 2378 (ref. '12') Summary: 12 errors (**), 0 flaws (~~), 4 warnings (==), 6 comments (--). Run idnits with the --verbose option for more detailed information about the items above. -------------------------------------------------------------------------------- 1 Internet-Draft Ryan Moats 2 draft-ietf-svrloc-wpyp-04.txt AT&T 3 Expires in 8/31/99 February 1999 5 The 'wp' and 'yp' Abstract Service Types 6 Filename: draft-ietf-svrloc-wpyp-04.txt 8 Status of This Memo 10 This document is an Internet-Draft and is in full conformance with 11 all provisions of Section 10 of RFC2026. Internet-Drafts are 12 working documents of the Internet Engineering Task Force (IETF), 13 its areas, and its working groups. Note that other groups may 14 also 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 The list of current Internet-Drafts can be accessed at 23 http://www.ietf.org/ietf/1id-abstracts.txt 25 The list of Internet-Draft Shadow Directories can be accessed at 26 http://www.ietf.org/shadow.html. 28 Abstract 30 This document presents definitions for the "wp" and "yp" abstract 31 services. The "wp" service is for finding people, while the "yp" 32 service if for finding general things (including people). 34 1. Introduction 36 In "Advertising Services" [1], several abstract services are 37 proposed. As specified in [2], the "wp" and "yp" abstract services 38 are documented here. The "wp" service is intended for finding 39 people, while the "yp" service is a superset that is intended for 40 finding objects. 42 2. The "wp" Abstract Service 44 The "wp" abstract service is for locating people via a directory. 45 Version 0.0 of this service specifies four protocols for accessing 46 such services: LDAP, WHOIS++, CCSO/Ph and HTTP. 48 ---------------------------template begins here----------------------- 49 template-type = wp 51 template-version = 0.0 53 template-language = EN 55 template-description = 56 The WP Abstract Service is for locating people using either LDAP, WHOIS, CCSO/Ph or HTTP 58 template-url-syntax = 59 url-path = ldapurl / whoisppurl / phurl / httpurl 60 ldapurl = url as defined in [3] 61 whoisppurl = url as defined in [4] 62 httpurl = url as defined in [5] 63 phurl = "ph://" hostport 64 hostport = host [ ":" port ] 65 host = hostname / hostnumber 66 hostname = *( domainlavel "." ) toplabel 67 domainlabel = alphanum / alphanum * [alphanum / "-"] alphanum 68 toplabel = alpha / alpha * [alphanum / "-"] alphanum 69 hostnumber = ipv4-number / ipv6-number 70 ipv4-number = 1*3digit 3*3("." 1*3digit) 71 ipv6-number = 32*hex 72 3digit = digit digit digit 73 port = 1*digit 74 ; A port number must be included if the 75 ; protocol field does not have an IANA 76 ; assigned port number. 77 alphanum = alpha / digit 78 alpha = "a" / "b" / "c" / "d" / "e" / "f" / "g" / 79 "h" / "i" / "j" / "k" / "l" / "m" / "n" / 80 "o" / "p" / "q" / "r" / "s" / "t" / "u" / 81 "v" / "w" / "x" / "y" / "z" / 82 "A" / "B" / "C" / "D" / "E" / "F" / "G" / 83 "H" / "I" / "J" / "K" / "L" / "M" / "N" / 84 "O" / "P" / "Q" / "R" / "S" / "T" / "U" / 85 "V" / "W" / "X" / "Y" / "Z" 86 digit = "0" / "1" / "2" / "3" / "4" / "5" / "6" / 87 "7" / "8" / "9" 88 ---------------------------template ends here------------------------- 90 3. The "yp" Abstract Service 92 The "yp" abstract service is for locating resources on the Internet 93 and is a superset of the "wp" abstract service. Version 0.0 specifies 94 the following protocols for accessing such services in addition to 95 those specified for the "wp" abstract service: Z39.50 and WHOIS++. 97 ---------------------------template begins here----------------------- 98 template-type = yp 100 template-version = 0.0 102 template-language = EN 104 template-description = 105 The yp Abstract Service is for locating general resources on the internet 107 template-url-syntax = 108 url-path = z3950url / httpurl / whoisppurl / ldapurl 109 phurl 110 z3950url = url as defined in [6] 111 httpurl = url as defined in [5] 112 whoisppurl = url as defined in [4] 113 ldapurl = url as defined in [3] 114 phurl = "ph://" hostport 115 hostport = host [ ":" port ] 116 host = hostname / hostnumber 117 hostname = *( domainlavel "." ) toplabel 118 domainlabel = alphanum / alphanum * [alphanum / "-"] alphanum 119 toplabel = alpha / alpha * [alphanum / "-"] alphanum 120 hostnumber = ipv4-number / ipv6-number 121 ipv4-number = 1*3digit 3*3("." 1*3digit) 122 ipv6-number = 32*hex 123 3digit = digit digit digit 124 port = 1*digit 125 ; A port number must be included if the 126 ; protocol field does not have an IANA 127 ; assigned port number. 128 alphanum = alpha / digit 129 alpha = "a" / "b" / "c" / "d" / "e" / "f" / "g" / 130 "h" / "i" / "j" / "k" / "l" / "m" / "n" / 131 "o" / "p" / "q" / "r" / "s" / "t" / "u" / 132 "v" / "w" / "x" / "y" / "z" / 133 "A" / "B" / "C" / "D" / "E" / "F" / "G" / 134 "H" / "I" / "J" / "K" / "L" / "M" / "N" / 135 "O" / "P" / "Q" / "R" / "S" / "T" / "U" / 136 "V" / "W" / "X" / "Y" / "Z" 137 digit = "0" / "1" / "2" / "3" / "4" / "5" / "6" / 138 "7" / "8" / "9" 139 ---------------------------template ends here------------------------- 141 4. Contact Information 143 The contact point for version 0.0 of both of these templates is the 144 author. 146 5. Security Considerations 148 Both of these abstract services inherit the security considerations 149 of the "service:" URL scheme as specified in [2]. As these services 150 are both abstract, they further inherit considerations from the 151 protocol used to provide the underlying concrete services as 152 discussed below. 154 5.1 Considerations for the "wp" service 156 Since the "wp" abstract service can use any of LDAP, HTTP, WHOIS or 157 CCSO/Ph, it inherits the security considerations for each of these 158 protocols. See [3] and [8] for LDAP, [9] and [10] for HTTP, [4] and 159 [11] for WHOIS, and [12] for CCSO/Ph. 161 5.2 Considerations for the "yp" service Since the "yp" abstract service 162 is a superset of the "wp" service, it inherits all the considerations 163 from the above section. In addition, it inherits the security 164 considerations from [6] for Z39.50. 166 6. Acknowledgments 168 This work described in this document is partially supported by the 169 National Science Foundation, Cooperative Agreement NCR-9218179. 171 7. References 173 Request For Comments (RFC) and Internet Drafts documents are 174 available from and numerous mirror sites 176 [1] R. Moats, M. Hamilton, "Advertising Services," 177 Internet Draft (work in progress), September 1998. 179 [2] C. Perkins, E. Guttman, J. Kempf, "Service Tem- 180 plates and 'service:' Schemes," Internet Draft 181 (work in progress), February 1999. 183 [3] T. Howes, M. Smith, "An LDAP URL Format," RFC 1959, 184 June 1996. 186 [4] M. Hamilton, "WHOIS++ URL Specification," Internet 187 Draft (work in progress), March 1998. 189 [5] T. Berners-Lee, R. Fielding, and L. Masinter, "Uni- 190 form Resource Locators (URL): Generic Syntax and 191 Semantics," RFC1738 as amended by RFC1808 and 192 updated by draft-fielding-url-syntax-09.txt, May 193 1997. (work in progress). 195 [6] R. Denenberg, J. Kunze, D. Lynch, "Uniform Resource 196 Locators for Z39.50," RFC 2056, November 1996. 198 [7] J. Veizades, E. Guttman, C. Perkins, S. Kaplan, 199 "Service Location Protocol," RFC 2165, June 1997. 201 [8] W. Yeong, T. Howes, S. Kille, "Lightweight Direc- 202 tory Access Protocol", RFC 1777, March 1995. 204 [9] T. Berners-Lee, R. Fielding, H. Frystyk, "Hypertext 205 Transfer Protocol -- HTTP/1.0", RFC 1945, May 1996. 207 [10] R. Fielding (et.al.), "Hypertext Transfer Protocol 208 -- HTTP/1.1", RFC 2068, January 1997. 210 [11] P. Deutsch, R. Schoultz, P. Faltstrom, C. Weider, 211 "Architecture of the WHOIS++ Service", RFC 1835, 212 August 1995. 214 [12] P. Pomes, R. Hedberg, "The CCSO Nameserver (Ph) 215 Architecture", RFC 2378, August 1998. 217 8. Author's addresses 219 Ryan Moats 220 AT&T 221 15621 Drexel Circle 222 Omaha, NE 68135-2358 223 USA 225 Phone: +1 402 894-9456 226 EMail: jayhawk@att.com 228 Expires 8/31/99.