Internet-Draft                                                Ryan Moats
draft-ietf-svrloc-wpyp-02.txt                                       AT&T
Expires in six months                                       October 1997

                The 'wp:' 'wp' and 'yp:' 'yp' Abstract Service Types
                Filename: draft-ietf-svrloc-wpyp-01.txt draft-ietf-svrloc-wpyp-02.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
      documents at any time.  It is inappropriate to use Internet-
      Drafts as reference material or to cite them other than as ``work
      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 (Africa),
      (Europe), (Pacific Rim), (US East
      Coast), or (US West Coast).


   This document presents definitions for the 'wp:' ''wp'' (white pages) and
   ''yp'' (yellow pages) abstract services.

1. Introduction

   In "Advertising Services" [1], several abstract services are
   proposed. As specified in [2], the "wp:" "wp" (white pages) and "yp:"
   yellow pages "yp"
   (yellow pages) abstract services are documented here.

2. The "wp" Abstract Service

   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

   ---------------------------template begins here-----------------------
    type = wp

    version = 0.0

    language = EN

    description =
    The WP Abstract Service is for locating people via "white pages" services. using either LDAP, WHOIS, CCSO/Ph or HTTP

    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"
   ---------------------------template ends here-------------------------

3. The "yp" Abstract Service

   To locate resource

   The "yp" abstract service is for locating resources on the Internet, a client would use the "Yellow
   Pages" service Internet
   and version 0.0 of the "yp" abstract service specifies
   two three protocols for accessing such
   services: Z39.50  Z39.50, HTTP, and HTTP. WHOIS++.

   ---------------------------template begins here-----------------------
    type = yp

    version = 0.0

    language = EN

    description =
    The yp Abstract Service is for locating resource resources either via "yellow pages" services. Z39.50, HTTP or WHOIS.

    url-syntax =
    url-path       = z3950url / httpurl / whoisppurl
    z3950url       = url as defined in [6]
    httpurl        = url as defined in [5]
    whoisppurl     = url as defined in [4]
   ---------------------------template ends here-------------------------

4. Security Considerations Contact Information

   The contact point for version 0.0 of both of these templates presented here is the

5. Security Considerations

   Both of these abstract services inherit the security considerations
   of the "service:" URL scheme as specified in [2].  As these services
   are subject both abstract, they further inherit considerations from the
   protocol used to provide the same implications underlying concrete services as
   discussed below.

5.1 Considerations for the "wp" service templates specified according to [2]

   Since the "wp" abstract service can use any of LDAP, HTTP, WHOIS or
   CCSO/Ph, it inherits the security considerations for each of these
   protocols.  See [3] and [7].

5. [8] for LDAP, [9] and [10] for HTTP, [4] and
   [11] for WHOIS, and [12] for CCSO/Ph.

5.2 Considerations for the "yp" service Since the "yp" abstract service
can use any of HTTP, Z39.50, or WHOIS, it inherits the security
considerations for each of these protocols.  See [9] and [10] for HTTP,
[6] for Z39.50, and [4] and [11] for WHOIS.

6. Acknowledgments

   This work described in this document is partially supported by the
   National Science Foundation, Cooperative Agreement NCR-9218179.


7. References

   Request For Comments (RFC) and Internet Drafts documents are
   available from <URL:> and numerous mirror sites

         [1]         R. Moats, M. Hamilton, "Advertising Services,"
                     Internet Draft (work in progress), February 1997.

         [2]         C. Perkins, E. Guttman, "The service: URL Scheme," J. Kempf, "Service Tem-
                     plates and 'service:' Schemes," Internet Draft
                     (work in progress), 20 November 1996. October 1997.

         [3]         T. Howes, M. Smith, "An LDAP URL Format," RFC 1959,
                     June 1996.

         [4]         M. Hamilton, "WHOIS++ URL Specification," Internet
                     Draft (work in progress), May 1997.

         [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, draft-fielding-url-syntax-09.txt, May
                     1997.  (work in progress).

         [6]         R. Denenberg, J. Kunze, D. Lynch, "Uniform Resource
                     Locators for Z39.50," RFC 2056, November 1996.

         [7]         J. Veizades, E. Guttman, C. Perkins, S. Kaplan,
                     "Service Location Protocol," RFC 2165, June 1997.

         [8]         W. Yeong, T. Howes, S. Kille, "Lightweight Direc-
                     tory Access Protocol", RFC 1777, March 1995.

         [9]         T. Berners-Lee, R. Fielding, H. Frystyk, "Hypertext
                     Transfer Protocol -- HTTP/1.0", RFC 1945, May 1996.

         [10]        R. Fielding (, "Hypertext Transfer Protocol
                     -- HTTP/1.1", RFC 2068, January 1997.

         [11]        P. Deutsch, R. Schoultz, P. Faltstrom, C. Weider,
                     "Architecture of the WHOIS++ Service", RFC 1835,
                     August 1995.

         [12]        P. Pomes, R. Hedberg, "The CCSO Nameserver (Ph)
                     Architecture", Internet Draft (work in progress), 8 January
                     May 1997.


8. Author's addresses

   Ryan Moats
   15621 Drexel Circle
   Omaha, NE 68135-2358

   Phone:  +1 402 894-9456