--- 1/draft-ietf-svrloc-wpyp-00.txt 2008-04-11 10:58:33.000000000 +0200 +++ 2/draft-ietf-svrloc-wpyp-01.txt 2008-04-11 10:58:33.000000000 +0200 @@ -1,17 +1,17 @@ Internet-Draft Ryan Moats -draft-ietf-svrloc-wpyp-00.txt AT&T -Expires in six months February 1997 +draft-ietf-svrloc-wpyp-01.txt AT&T +Expires in six months October 1997 - Defining White Pages and Yellow Pages Services - Filename: draft-ietf-svrloc-wpyp-00.txt + The 'wp:' and 'yp:' Abstract Service Types + Filename: draft-ietf-svrloc-wpyp-01.txt Status of This Memo This document is an Internet-Draft. Internet-Drafts are working documents of the Internet Engineering Task Force (IETF), its areas, and its working groups. Note that other groups may also distribute working documents as Internet-Drafts. Internet-Drafts are draft documents valid for a maximum of six months and may be updated, replaced, or obsoleted by other @@ -20,241 +20,135 @@ in progress.'' To learn the current status of any Internet-Draft, please check the ``1id-abstracts.txt'' listing contained in the Internet- Drafts Shadow Directories on ftp.is.co.za (Africa), nic.nordu.net (Europe), munnari.oz.au (Pacific Rim), ds.internic.net (US East Coast), or ftp.isi.edu (US West Coast). Abstract - Service scheme templates for several different "white" and "yellow" - pages services are presented. + This document presents definitions for the 'wp:' (white pages) and + 'yp:' (yellow pages) abstract services. 1. Introduction - In "Advertising Services" [1], several different types of "service:" - URL schemes are proposed. As specified by [2], the service scheme - templates for several of those services are documented here. For all - the schemes herein, stripping the "service:" and the leading "wp-" or - "yp-" from the service URL results in the URL for the resource.. - -2. Specifying White Pages Services - - To locate people on the Internet, a client connects to a "White - Pages" service. A variety of protocols are available for connecting - to such services. As [2] recommends that service templates be as - protocol-specific as possible, there are multiple templates for white - pages services, specified in this section. - -2.1. WP-LDAP Service - - When LDAP [3] is the protocol for accessing a "White Pages" service, - the "wp-ldap" template is used. Here, the syntax of the URLpath is - specified in [4]. - - "Service Discover Multicast Address = NONE - - Service type = wp-ldap - - Version = 0.0 - - Language tag = en - - Description = - The wp-ldap (or White Pages via LDAP) service type provides - attributes for looking up people via the LDAP protocol. - - Authorization policy = :: NONE :: - A text description of any authentication requirements for use of - this server. - - Use policy = :: NONE :: - A text description of any intended Use policy for this server. - - Access protocol = :: LDAP :: - This white pages server's access protocol, which is used to - distinguish from other white pages servers." - -2.2. WP-WHOIS++ Service - - The "wp-ldap" template is used when WHOIS++ [5] is the access - protocol for a White Pages service. Here, the syntax of the URL path - is specified in [6]. - - "Sevice Discover Multicast Address = NONE - - Service type = wp-whois++ - - Version = 0.0 - - Language tag = en - Description = - The wp-whois++ (or White Pages via WHOIS++) service type provides - attributes for looking up people via the WHOIS++ protocol. - - Authorization policy = :: NONE :: - A text description of any authentication requirements for use of - this server. - - Use policy = :: NONE :: - A text description of any intended Use policy for this server. - - Access protocol = :: WHOIS++ :: - This white pages server's access protocol, which is used to - distinguish from other white pages servers." - -2.3. WP-PH Service - - The "wp-ph" template is used when CCSO/Ph [7] is the access protocol - for a White Pages service. Here, the syntax for the URL path is - undefined. - -4.1 WP-PH Service Template - -Sevice Discover Multicast Address = NONE - - "Service type = wp-ph - - Version = 0.0 - - Language tag = en - - Description = - The wp-ph (or White Pages via PH) service type provides attributes - for defining services for looking up people via the PH protocol. - - Authorization policy = :: NONE :: - A text description of any authentication requirements for use of - this server. - - Use policy = :: NONE :: - A text description of any intended Use policy for this server. - - Access protocol = :: CCSO/PH :: - This white pages server's access protocol, which is used to - distinguish from other white pages servers." - -5. Specification of YP-Z3950R Service - - This section specifies the template for the service "yp-z3950r," - which is for providing a "Yellow Pages" service for locating - documents using Z39.50 [8] as the access protocol. - - The syntax for the URL path is specified in [9]. - -5.1 YP-Z3950R Service Template - - "Sevice Discover Multicast Address = NONE - - Service type = yp-z3950r - - Version = 0.0 - - Language tag = en - - Description = - The yp-z3950r (or Yellow Pages by Z39.50) service type provides - attributes for looking up documents via the Z39.50 protocol. - - Authorization policy = :: NONE :: - A text description of any authentication requirements for use of - this server. + In "Advertising Services" [1], several abstract services are + proposed. As specified in [2], the "wp:" (white pages) and "yp:" + yellow pages abstract services are documented here. - Use policy = :: NONE :: - A text description of any intended Use policy for this server. +2. The "wp" Abstract Service - Access protocol = :: Z39.50 :: - The access protocol used by this server (to - distinguish from other servers)." + The "wp" abstract service is for locating people via directory or + "white pages" services. Version 0.0 of this service specifies four + protocols for accessing such services: LDAP, WHOIS++, CCSO/Ph and + HTTP. -6. Specification of YP-Z3950S Service + type = wp - This section specifies the template for the service "yp-z3950s," - which is for providing a "Yellow Pages" service for locating - documents using Z39.50 [8] as the access protocol. + version = 0.0 - The syntax for the URL path is specified in [9]. + language = EN -6.1 YP-Z3950S Service Template + description = + The WP Abstract Service is for locating people via "white pages" services. - "Sevice Discover Multicast Address = NONE - Service type = yp-z3950s + url-syntax = + url-path = ldapurl / whoisppurl / phurl / httpurl + ldapurl = url as defined in [3] + whoisppurl = url as defined in [4] + httpurl = url as defined in [5] + phurl = "ph://" hostport + hostport = host [ ":" port ] + host = hostname / hostnumber + hostname = *( domainlavel "." ) toplabel + domainlabel = alphanum / alphanum * [alphanum / "-"] alphanum + toplabel = alpha / alpha * [alphanum / "-"] alphanum + hostnumber = ipv4-number / ipv6-number + ipv4-number = 1*3digit 3*3("." 1*3digit) + ipv6-number = 32*hex + 3digit = digit digit digit + port = 1*digit + ; A port number must be included if the + ; protocol field does not have an IANA + ; assigned port number. + alphanum = alpha / digit + alpha = "a" / "b" / "c" / "d" / "e" / "f" / "g" / + "h" / "i" / "j" / "k" / "l" / "m" / "n" / + "o" / "p" / "q" / "r" / "s" / "t" / "u" / + "v" / "w" / "x" / "y" / "z" / + "A" / "B" / "C" / "D" / "E" / "F" / "G" / + "H" / "I" / "J" / "K" / "L" / "M" / "N" / + "O" / "P" / "Q" / "R" / "S" / "T" / "U" / + "V" / "W" / "X" / "Y" / "Z" + digit = "0" / "1" / "2" / "3" / "4" / "5" / "6" / + "7" / "8" / "9" - Version = 0.0 +3. The "yp" Abstract Service - Language tag = en + To locate resource on the Internet, a client would use the "Yellow + Pages" service and version 0.0 of the "yp" abstract service specifies + two protocols for accessing such services: Z39.50 and HTTP. - Description = - The yp-z3950s (or Yellow Pages by Z39.50) service type provides - attributes for looking up documents via the Z39.50 session. + type = yp + version = 0.0 - Authorization policy = :: NONE :: - A text description of any authentication requirements for use of - this server. + language = EN - Use policy = :: NONE :: - A text description of any intended Use policy for this server + description = + The yp Abstract Service is for locating resource via "yellow pages" services. - access protocol = :: Z39.50 :: - The access protocol used by this server (to - distinguish from other servers)." + url-syntax = + url-path = z3950url / httpurl + z3950url = url as defined in [6] + httpurl = url as defined in [5] -7. Security Considerations +4. Security Considerations The templates presented here are subject to the same implications as - other service templates specified according to [2] and [10]. + other service templates specified according to [2] and [7]. -8. Acknowledgments +5. Acknowledgments - This document is partially supported by the National Science - Foundation, Cooperative Agreement NCR-9218179. + This work described in this document is partially supported by the + National Science Foundation, Cooperative Agreement NCR-9218179. -9. References +6. References Request For Comments (RFC) and Internet Drafts documents are available from and numerous mirror sites [1] R. Moats, M. Hamilton, "Advertising Services," Internet Draft (work in progress), February 1997. [2] E. Guttman, "The service: URL Scheme," Internet Draft (work in progress), 20 November 1996. - [3] W. Yeong, T. Howes, S. Kille, "Lightweight Direc- - tory Access Protocol," RFC 1777, March 1995. - - [4] T. Howes, M. Smith, "An LDAP URL Format," RFC 1959, + [3] T. Howes, M. Smith, "An LDAP URL Format," RFC 1959, June 1996. - [5] P. Deutsch, R. Schoultz, P. Falstrom, C. Weider, - "Architecture of the WHOIS++ service," RFC 1835, - August 1995. - - [6] M. Hamilton, "WHOIS++ URL Specification," Internet - Draft (work in progress), July 1996. - - [7] R. Hedberg, S. Dorner, P. Pomes, "The CCSO - Nameserver (Ph) Architecture," Internet Draft (work - in Progress), August 1996. + [4] M. Hamilton, "WHOIS++ URL Specification," Internet + Draft (work in progress), May 1997. - [8] ANSI/NISO Z39.50-1995, "ANSI Z39.50: Information - Retrieval Service and Protocol," 1995. Available - from + [5] T. Berners-Lee, R. Fielding, and L. Masinter, "Uni- + form Resource Locators (URL): Generic Syntax and + Semantics," RFC1738 as amended by RFC1808 and + updated by draft-fielding-url-syntax-05.txt, May + 1997. (work in progress). - [9] R. Denenberg, J. Kunze, D. Lynch, "Uniform Resource + [6] R. Denenberg, J. Kunze, D. Lynch, "Uniform Resource Locators for Z39.50," RFC 2056, November 1996. - [10] J. Veizades, E. Guttman, C. Perkins, S. Kaplan, + [7] J. Veizades, E. Guttman, C. Perkins, S. Kaplan, "Service Location Protocol," Internet Draft (work in progress), 8 January 1997. -10. Author's addresses +7. Author's addresses Ryan Moats AT&T 15621 Drexel Circle Omaha, NE 68135-2358 USA Phone: +1 402 894-9456 - EMail: jayhawk@ds.internic.net + EMail: jayhawk@att.com