draft-ietf-svrloc-wpyp-02.txt   draft-ietf-svrloc-wpyp-03.txt 
Internet-Draft Ryan Moats Internet-Draft Ryan Moats
draft-ietf-svrloc-wpyp-02.txt AT&T draft-ietf-svrloc-wpyp-03.txt AT&T
Expires in six months October 1997 Expires in six months January 1998
The 'wp' and 'yp' Abstract Service Types The 'wp' and 'yp' Abstract Service Types
Filename: draft-ietf-svrloc-wpyp-02.txt Filename: draft-ietf-svrloc-wpyp-03.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. Internet-Drafts are working
documents of the Internet Engineering Task Force (IETF), its documents of the Internet Engineering Task Force (IETF), its
areas, and its working groups. Note that other groups may also areas, and its working groups. Note that other groups may also
distribute working documents as Internet-Drafts. 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
skipping to change at page 1, line 31 skipping to change at page 1, line 31
in progress.'' in progress.''
To learn the current status of any Internet-Draft, please check To learn the current status of any Internet-Draft, please check
the ``1id-abstracts.txt'' listing contained in the Internet- the ``1id-abstracts.txt'' listing contained in the Internet-
Drafts Shadow Directories on ftp.is.co.za (Africa), nic.nordu.net Drafts Shadow Directories on ftp.is.co.za (Africa), nic.nordu.net
(Europe), munnari.oz.au (Pacific Rim), ds.internic.net (US East (Europe), munnari.oz.au (Pacific Rim), ds.internic.net (US East
Coast), or ftp.isi.edu (US West Coast). Coast), or ftp.isi.edu (US West Coast).
Abstract Abstract
This document presents definitions for the ''wp'' (white pages) and This document presents definitions for the ''wp'' and ''yp'' abstract
''yp'' (yellow pages) abstract services. services. The ''wp'' service is for finding people, while the ''yp''
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" (white pages) and "yp" proposed. As specified in [2], the "wp" and "yp" abstract services
(yellow pages) abstract services are documented here. are documented here. The "wp" service is intended for finding
people, while the "yp" service is a superset that is intended for
finding objects.
2. The "wp" Abstract Service 2. The "wp" Abstract Service
The "wp" abstract service is for locating people via directory or The "wp" abstract service is for locating people via a directory.
"white pages" services. Version 0.0 of this service specifies four Version 0.0 of this service specifies four protocols for accessing
protocols for accessing such services: LDAP, WHOIS++, CCSO/Ph and such services: LDAP, WHOIS++, CCSO/Ph and HTTP.
HTTP.
---------------------------template begins here----------------------- ---------------------------template begins here-----------------------
type = wp type = wp
version = 0.0 version = 0.0
language = EN language = EN
description = 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
skipping to change at page 2, line 50 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 version 0.0 specifies three protocols for accessing such and is a superset of the "wp" abstract service. Version 0.0
services: Z39.50, HTTP, and WHOIS++. specifies the following protocols for accessing such services in
addition to those specified for the "wp" abstract service: Z39.50 and
WHOIS++.
---------------------------template begins here----------------------- ---------------------------template begins here-----------------------
type = yp type = yp
version = 0.0 version = 0.0
language = EN language = EN
description = description =
The yp Abstract Service is for locating resources either via Z39.50, HTTP or WHOIS. The yp Abstract Service is for locating general resources on the internet
url-syntax = url-syntax =
url-path = z3950url / httpurl / whoisppurl url-path = z3950url / httpurl / whoisppurl / ldapurl
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]
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------------------------- ---------------------------template ends here-------------------------
4. Contact Information 4. Contact Information
The contact point for version 0.0 of both of these templates is the The contact point for version 0.0 of both of these templates is the
author. author.
5. Security Considerations 5. Security Considerations
Both of these abstract services inherit the security considerations Both of these abstract services inherit the security considerations
skipping to change at page 3, line 44 skipping to change at page 4, line 29
discussed below. discussed below.
5.1 Considerations for the "wp" service 5.1 Considerations for the "wp" service
Since the "wp" abstract service can use any of LDAP, HTTP, WHOIS or Since the "wp" abstract service can use any of LDAP, HTTP, WHOIS or
CCSO/Ph, it inherits the security considerations for each of these CCSO/Ph, it inherits the security considerations for each of these
protocols. See [3] and [8] for LDAP, [9] and [10] for HTTP, [4] and protocols. See [3] and [8] for LDAP, [9] and [10] for HTTP, [4] and
[11] for WHOIS, and [12] for CCSO/Ph. [11] for WHOIS, and [12] for CCSO/Ph.
5.2 Considerations for the "yp" service Since the "yp" abstract service 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 is a superset of the "wp" service, it inherits all the considerations
considerations for each of these protocols. See [9] and [10] for HTTP, from the above section. In addition, it inherits the security
[6] for Z39.50, and [4] and [11] for WHOIS. considerations from [6] for Z39.50.
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," [1] R. Moats, M. Hamilton, "Advertising Services," Internet
Internet Draft (work in progress), February 1997. Draft (work in progress), February 1997.
[2] C. Perkins, E. Guttman, J. Kempf, "Service Tem- [2] C. Perkins, E. Guttman, J. Kempf, "Service Templates and
plates and 'service:' Schemes," Internet Draft 'service:' Schemes," Internet Draft (work in progress),
(work in progress), October 1997. October 1997.
[3] T. Howes, M. Smith, "An LDAP URL Format," RFC 1959, [3] T. Howes, M. Smith, "An LDAP URL Format," RFC 1959, June
June 1996. 1996.
[4] M. Hamilton, "WHOIS++ URL Specification," Internet [4] M. Hamilton, "WHOIS++ URL Specification," Internet Draft
Draft (work in progress), May 1997. (work in progress), May 1997.
[5] T. Berners-Lee, R. Fielding, and L. Masinter, "Uni- [5] T. Berners-Lee, R. Fielding, and L. Masinter, "Uniform
form Resource Locators (URL): Generic Syntax and Resource Locators (URL): Generic Syntax and Semantics,"
Semantics," RFC1738 as amended by RFC1808 and RFC1738 as amended by RFC1808 and updated by draft-fielding-
updated by draft-fielding-url-syntax-09.txt, May url-syntax-09.txt, May 1997. (work in progress).
1997. (work in progress).
[6] R. Denenberg, J. Kunze, D. Lynch, "Uniform Resource [6] R. Denenberg, J. Kunze, D. Lynch, "Uniform Resource Locators
Locators for Z39.50," RFC 2056, November 1996. for Z39.50," RFC 2056, November 1996.
[7] J. Veizades, E. Guttman, C. Perkins, S. Kaplan, [7] J. Veizades, E. Guttman, C. Perkins, S. Kaplan, "Service
"Service Location Protocol," RFC 2165, June 1997. Location Protocol," RFC 2165, June 1997.
[8] W. Yeong, T. Howes, S. Kille, "Lightweight Direc- [8] W. Yeong, T. Howes, S. Kille, "Lightweight Directory Access
tory Access Protocol", RFC 1777, March 1995. Protocol", RFC 1777, March 1995.
[9] T. Berners-Lee, R. Fielding, H. Frystyk, "Hypertext [9] T. Berners-Lee, R. Fielding, H. Frystyk, "Hypertext Transfer
Transfer Protocol -- HTTP/1.0", RFC 1945, May 1996. 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, [11] P. Deutsch, R. Schoultz, P. Faltstrom, C. Weider, "Architec-
"Architecture of the WHOIS++ Service", RFC 1835, ture of the WHOIS++ Service", RFC 1835, August 1995.
August 1995.
[12] P. Pomes, R. Hedberg, "The CCSO Nameserver (Ph) [12] P. Pomes, R. Hedberg, "The CCSO Nameserver (Ph) Architec-
Architecture", Internet Draft (work in progress), ture", Internet Draft (work in progress), May 1997.
May 1997.
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
 End of changes. 22 change blocks. 
48 lines changed or deleted 76 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/