draft-ietf-svrloc-wpyp-03.txt   draft-ietf-svrloc-wpyp-04.txt 
Internet-Draft Ryan Moats Internet-Draft Ryan Moats
draft-ietf-svrloc-wpyp-03.txt AT&T draft-ietf-svrloc-wpyp-04.txt AT&T
Expires in six months January 1998 Expires in 8/31/99 February 1999
The 'wp' and 'yp' Abstract Service Types The 'wp' and 'yp' Abstract Service Types
Filename: draft-ietf-svrloc-wpyp-03.txt Filename: draft-ietf-svrloc-wpyp-04.txt
Status of This Memo Status of This Memo
This document is an Internet-Draft. Internet-Drafts are working This document is an Internet-Draft and is in full conformance with
documents of the Internet Engineering Task Force (IETF), its all provisions of Section 10 of RFC2026. Internet-Drafts are
areas, and its working groups. Note that other groups may also working documents of the Internet Engineering Task Force (IETF),
distribute working documents as Internet-Drafts. 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 Internet-Drafts are draft documents valid for a maximum of six
months and may be updated, replaced, or obsoleted by other months and may be updated, replaced, or obsoleted by other
documents at any time. It is inappropriate to use Internet- documents at any time. It is inappropriate to use Internet-
Drafts as reference material or to cite them other than as ``work Drafts as reference material or to cite them other than as "work
in progress.'' in progress."
To learn the current status of any Internet-Draft, please check The list of current Internet-Drafts can be accessed at
the ``1id-abstracts.txt'' listing contained in the Internet- http://www.ietf.org/ietf/1id-abstracts.txt
Drafts Shadow Directories on ftp.is.co.za (Africa), nic.nordu.net
(Europe), munnari.oz.au (Pacific Rim), ds.internic.net (US East The list of Internet-Draft Shadow Directories can be accessed at
Coast), or ftp.isi.edu (US West Coast). http://www.ietf.org/shadow.html.
Abstract Abstract
This document presents definitions for the ''wp'' and ''yp'' abstract This document presents definitions for the "wp" and "yp" abstract
services. The ''wp'' service is for finding people, while the ''yp'' services. The "wp" service is for finding people, while the "yp"
service if for finding general things (including people). service if for finding general things (including people).
1. Introduction 1. Introduction
In "Advertising Services" [1], several abstract services are In "Advertising Services" [1], several abstract services are
proposed. As specified in [2], the "wp" and "yp" abstract services proposed. As specified in [2], the "wp" and "yp" abstract services
are documented here. The "wp" service is intended for finding are documented here. The "wp" service is intended for finding
people, while the "yp" service is a superset that is intended for people, while the "yp" service is a superset that is intended for
finding objects. finding objects.
2. The "wp" Abstract Service 2. The "wp" Abstract Service
The "wp" abstract service is for locating people via a directory. The "wp" abstract service is for locating people via a directory.
Version 0.0 of this service specifies four protocols for accessing Version 0.0 of this service specifies four protocols for accessing
such services: LDAP, WHOIS++, CCSO/Ph and HTTP. such services: LDAP, WHOIS++, CCSO/Ph and HTTP.
---------------------------template begins here----------------------- ---------------------------template begins here-----------------------
type = wp template-type = wp
version = 0.0 template-version = 0.0
language = EN template-language = EN
description = template-description =
The WP Abstract Service is for locating people using either LDAP, WHOIS, CCSO/Ph or HTTP The WP Abstract Service is for locating people using either LDAP, WHOIS, CCSO/Ph or HTTP
url-syntax = template-url-syntax =
url-path = ldapurl / whoisppurl / phurl / httpurl url-path = ldapurl / whoisppurl / phurl / httpurl
ldapurl = url as defined in [3] ldapurl = url as defined in [3]
whoisppurl = url as defined in [4] whoisppurl = url as defined in [4]
httpurl = url as defined in [5] httpurl = url as defined in [5]
phurl = "ph://" hostport phurl = "ph://" hostport
hostport = host [ ":" port ] hostport = host [ ":" port ]
host = hostname / hostnumber host = hostname / hostnumber
hostname = *( domainlavel "." ) toplabel hostname = *( domainlavel "." ) toplabel
domainlabel = alphanum / alphanum * [alphanum / "-"] alphanum domainlabel = alphanum / alphanum * [alphanum / "-"] alphanum
toplabel = alpha / alpha * [alphanum / "-"] alphanum toplabel = alpha / alpha * [alphanum / "-"] alphanum
skipping to change at page 3, line 8 skipping to change at page 3, line 8
"H" / "I" / "J" / "K" / "L" / "M" / "N" / "H" / "I" / "J" / "K" / "L" / "M" / "N" /
"O" / "P" / "Q" / "R" / "S" / "T" / "U" / "O" / "P" / "Q" / "R" / "S" / "T" / "U" /
"V" / "W" / "X" / "Y" / "Z" "V" / "W" / "X" / "Y" / "Z"
digit = "0" / "1" / "2" / "3" / "4" / "5" / "6" / digit = "0" / "1" / "2" / "3" / "4" / "5" / "6" /
"7" / "8" / "9" "7" / "8" / "9"
---------------------------template ends here------------------------- ---------------------------template ends here-------------------------
3. The "yp" Abstract Service 3. The "yp" Abstract Service
The "yp" abstract service is for locating resources on the Internet The "yp" abstract service is for locating resources on the Internet
and is a superset of the "wp" abstract service. Version 0.0 and is a superset of the "wp" abstract service. Version 0.0 specifies
specifies the following protocols for accessing such services in the following protocols for accessing such services in addition to
addition to those specified for the "wp" abstract service: Z39.50 and those specified for the "wp" abstract service: Z39.50 and WHOIS++.
WHOIS++.
---------------------------template begins here----------------------- ---------------------------template begins here-----------------------
type = yp template-type = yp
version = 0.0 template-version = 0.0
language = EN template-language = EN
description = template-description =
The yp Abstract Service is for locating general resources on the internet The yp Abstract Service is for locating general resources on the internet
url-syntax = template-url-syntax =
url-path = z3950url / httpurl / whoisppurl / ldapurl url-path = z3950url / httpurl / whoisppurl / ldapurl
phurl phurl
z3950url = url as defined in [6] z3950url = url as defined in [6]
httpurl = url as defined in [5] httpurl = url as defined in [5]
whoisppurl = url as defined in [4] whoisppurl = url as defined in [4]
ldapurl = url as defined in [3] ldapurl = url as defined in [3]
phurl = "ph://" hostport phurl = "ph://" hostport
hostport = host [ ":" port ] hostport = host [ ":" port ]
host = hostname / hostnumber host = hostname / hostnumber
hostname = *( domainlavel "." ) toplabel hostname = *( domainlavel "." ) toplabel
skipping to change at page 4, line 43 skipping to change at page 4, line 42
6. Acknowledgments 6. Acknowledgments
This work described in this document is partially supported by the This work described in this document is partially supported by the
National Science Foundation, Cooperative Agreement NCR-9218179. National Science Foundation, Cooperative Agreement NCR-9218179.
7. References 7. References
Request For Comments (RFC) and Internet Drafts documents are Request For Comments (RFC) and Internet Drafts documents are
available from <URL:ftp://ftp.internic.net> and numerous mirror sites available from <URL:ftp://ftp.internic.net> and numerous mirror sites
[1] R. Moats, M. Hamilton, "Advertising Services," Internet [1] R. Moats, M. Hamilton, "Advertising Services,"
Draft (work in progress), February 1997. Internet Draft (work in progress), September 1998.
[2] C. Perkins, E. Guttman, J. Kempf, "Service Templates and [2] C. Perkins, E. Guttman, J. Kempf, "Service Tem-
'service:' Schemes," Internet Draft (work in progress), plates and 'service:' Schemes," Internet Draft
October 1997. (work in progress), February 1999.
[3] T. Howes, M. Smith, "An LDAP URL Format," RFC 1959, June [3] T. Howes, M. Smith, "An LDAP URL Format," RFC 1959,
1996. June 1996.
[4] M. Hamilton, "WHOIS++ URL Specification," Internet Draft [4] M. Hamilton, "WHOIS++ URL Specification," Internet
(work in progress), May 1997. Draft (work in progress), March 1998.
[5] T. Berners-Lee, R. Fielding, and L. Masinter, "Uniform [5] T. Berners-Lee, R. Fielding, and L. Masinter, "Uni-
Resource Locators (URL): Generic Syntax and Semantics," form Resource Locators (URL): Generic Syntax and
RFC1738 as amended by RFC1808 and updated by draft-fielding- Semantics," RFC1738 as amended by RFC1808 and
url-syntax-09.txt, May 1997. (work in progress). updated by draft-fielding-url-syntax-09.txt, May
1997. (work in progress).
[6] R. Denenberg, J. Kunze, D. Lynch, "Uniform Resource Locators [6] R. Denenberg, J. Kunze, D. Lynch, "Uniform Resource
for Z39.50," RFC 2056, November 1996. Locators for Z39.50," RFC 2056, November 1996.
[7] J. Veizades, E. Guttman, C. Perkins, S. Kaplan, "Service [7] J. Veizades, E. Guttman, C. Perkins, S. Kaplan,
Location Protocol," RFC 2165, June 1997. "Service Location Protocol," RFC 2165, June 1997.
[8] W. Yeong, T. Howes, S. Kille, "Lightweight Directory Access [8] W. Yeong, T. Howes, S. Kille, "Lightweight Direc-
Protocol", RFC 1777, March 1995. tory Access Protocol", RFC 1777, March 1995.
[9] T. Berners-Lee, R. Fielding, H. Frystyk, "Hypertext Transfer [9] T. Berners-Lee, R. Fielding, H. Frystyk, "Hypertext
Protocol -- HTTP/1.0", RFC 1945, May 1996. Transfer Protocol -- HTTP/1.0", RFC 1945, May 1996.
[10] R. Fielding (et.al.), "Hypertext Transfer Protocol -- [10] R. Fielding (et.al.), "Hypertext Transfer Protocol
HTTP/1.1", RFC 2068, January 1997. -- HTTP/1.1", RFC 2068, January 1997.
[11] P. Deutsch, R. Schoultz, P. Faltstrom, C. Weider, "Architec- [11] P. Deutsch, R. Schoultz, P. Faltstrom, C. Weider,
ture of the WHOIS++ Service", RFC 1835, August 1995. "Architecture of the WHOIS++ Service", RFC 1835,
August 1995.
[12] P. Pomes, R. Hedberg, "The CCSO Nameserver (Ph) Architec- [12] P. Pomes, R. Hedberg, "The CCSO Nameserver (Ph)
ture", Internet Draft (work in progress), May 1997. Architecture", RFC 2378, August 1998.
8. Author's addresses 8. Author's addresses
Ryan Moats Ryan Moats
AT&T AT&T
15621 Drexel Circle 15621 Drexel Circle
Omaha, NE 68135-2358 Omaha, NE 68135-2358
USA USA
Phone: +1 402 894-9456 Phone: +1 402 894-9456
EMail: jayhawk@att.com EMail: jayhawk@att.com
Expires 8/31/99.
 End of changes. 30 change blocks. 
57 lines changed or deleted 59 lines changed or added

This html diff was produced by rfcdiff 1.34. The latest version is available from http://tools.ietf.org/tools/rfcdiff/