home
***
CD-ROM
|
disk
|
FTP
|
other
***
search
/
Internet Info 1997 December
/
Internet_Info_CD-ROM_Walnut_Creek_December_1997.iso
/
drafts
/
draft_ietf_q_t
/
draft-ietf-svrloc-wpyp-00.txt
< prev
next >
Wrap
Text File
|
1997-02-11
|
10KB
|
361 lines
Internet-Draft Ryan Moats
draft-ietf-svrloc-wpyp-00.txt AT&T
Expires in six months February 1997
Defining White Pages and Yellow Pages Services
Filename: draft-ietf-svrloc-wpyp-00.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 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.
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
Expires 8/31/97 [Page 1]
INTERNET DRAFT White and Yellow Page Services February 1997
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
Expires 8/31/97 [Page 2]
INTERNET DRAFT White and Yellow Page Services February 1997
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."
Expires 8/31/97 [Page 3]
INTERNET DRAFT White and Yellow Page Services February 1997
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.
Use policy = :: NONE ::
A text description of any intended Use policy for this server.
Access protocol = :: Z39.50 ::
The access protocol used by this server (to
distinguish from other servers)."
6. Specification of YP-Z3950S Service
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.
The syntax for the URL path is specified in [9].
6.1 YP-Z3950S Service Template
"Sevice Discover Multicast Address = NONE
Expires 8/31/97 [Page 4]
INTERNET DRAFT White and Yellow Page Services February 1997
Service type = yp-z3950s
Version = 0.0
Language tag = en
Description =
The yp-z3950s (or Yellow Pages by Z39.50) service type provides
attributes for looking up documents via the Z39.50 session.
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 = :: Z39.50 ::
The access protocol used by this server (to
distinguish from other servers)."
7. Security Considerations
The templates presented here are subject to the same implications as
other service templates specified according to [2] and [10].
8. Acknowledgments
This document is partially supported by the National Science
Foundation, Cooperative Agreement NCR-9218179.
9. References
Request For Comments (RFC) and Internet Drafts documents are
available from <URL:ftp://ftp.internic.net> 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,
June 1996.
Expires 8/31/97 [Page 5]
INTERNET DRAFT White and Yellow Page Services February 1997
[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.
[8] ANSI/NISO Z39.50-1995, "ANSI Z39.50: Information
Retrieval Service and Protocol," 1995. Available
from <ftp://ftp.loc.gov/pub/z3950/>
[9] 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,
"Service Location Protocol," Internet Draft (work
in progress), 8 January 1997.
10. 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
Expires 8/31/97 [Page 6]