draft-ietf-asid-whois-schema-01.txt   draft-ietf-asid-whois-schema-02.txt 
ASID Working Group Patrik Faltstrom ASID Working Group Patrik Faltstrom
INTERNET-DRAFT Tele2/Swipnet INTERNET-DRAFT Tele2/Swipnet
Expires January 1998 Martin Hamilton Expires April 1998 Martin Hamilton
Loughborough University Loughborough University
Leslie L. Daigle Leslie L. Daigle
Bunyip Information Systems, Inc. Bunyip Information Systems, Inc.
Jon Knight Jon Knight
Loughborough University Loughborough University
October 1997
WHOIS++ templates WHOIS++ templates
Filename: draft-ietf-asid-whois-schema-01.txt Filename: draft-ietf-asid-whois-schema-02.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 2, line 19 skipping to change at line 62
5. Cluster definitions 5. Cluster definitions
6. Template definitions 6. Template definitions
7. System templates 7. System templates
8. Security considerations 8. Security considerations
9. Conclusions 9. Conclusions
10. Acknowledgements 10. Acknowledgements
11. References 11. References
12. Authors' addresses 12. Authors' addresses
A. APPENDIX A: Description of elementary attribute values A. APPENDIX A: Description of elementary attribute values
B. APPENDIX B: Representing the Dublin Core in WHOIS++ B. APPENDIX B: Representing the Dublin Core in WHOIS++
C. APPENDIX C: Representing the Internet Whitepages Schema (IWPS) in
WHOIS++
1. Purpose and motivation 1. Purpose and motivation
The goal of this document is to stimulate discussion on the issue of The goal of this document is to stimulate discussion on the issue of
templates for WHOIS++ [1] databases. templates for WHOIS++ [1] databases.
In particular we would like to recommend a few typical templates and In particular we would like to recommend a few typical templates and
a set of attributes for them. By recommending the use of particular a set of attributes for them. By recommending the use of particular
templates, we hope to standardize WHOIS++ databases and thus make templates, we hope to standardize WHOIS++ databases and thus make
them easier to search. them easier to search.
skipping to change at page 4, line 34 skipping to change at line 176
+------------------+--------+-------------------------------+ +------------------+--------+-------------------------------+
|Address: | R | Full address | |Address: | R | Full address |
|Address-Type: | | Type of address, e.g. Work or | |Address-Type: | | Type of address, e.g. Work or |
| | | Home | | | | Home |
|Address-City: | R | City | |Address-City: | R | City |
|Address-Country: | R | Country | |Address-Country: | R | Country |
|Address-Room: | | Room | |Address-Room: | | Room |
|Address-State: | | State, county or province | |Address-State: | | State, county or province |
|Address-Street: | | Street | |Address-Street: | | Street |
|Address-Zip-Code: | | Zip code | |Address-Zip-Code: | | Zip code |
|Address-Locality: | | Geographic region |
+------------------+--------+-------------------------------+ +------------------+--------+-------------------------------+
CERTNAME cluster CERTNAME cluster
This cluster is used to describe the name of an organization issuing This cluster is used to describe the name of an organization issuing
a certificate, Certificate Revocation List (CRL) or the name of a a certificate, Certificate Revocation List (CRL) or the name of a
certificate holder. certificate holder.
+------------+--------+---------------------+ +------------+--------+---------------------+
|Name | Rec. ? | Description | |Name | Rec. ? | Description |
skipping to change at page 7, line 39 skipping to change at line 301
|(NAME*) | R | Name of person | |(NAME*) | R | Name of person |
|(ORG-PERSON*) | R | Organization related | |(ORG-PERSON*) | R | Organization related |
| | | personal contact | | | | personal contact |
| | | information | | | | information |
|Homepage-URI: | | Uniform Resource | |Homepage-URI: | | Uniform Resource |
| | | Identifier of person's | | | | Identifier of person's |
| | | home page | | | | home page |
|Picture-URI: | | Uniform Resource | |Picture-URI: | | Uniform Resource |
| | | Identifier of person's | | | | Identifier of person's |
| | | picture | | | | picture |
|Language-pref:| | Person's language of |
| | | preference |
+--------------+--------+-------------------------------+ +--------------+--------+-------------------------------+
PHONE cluster PHONE cluster
This cluster is used to hold telephone contact details for an object. This cluster is used to hold telephone contact details for an object.
+------------+--------+----------------------------------+ +------------+--------+----------------------------------+
|Name | Rec. ? | Description | |Name | Rec. ? | Description |
+------------+--------+----------------------------------+ +------------+--------+----------------------------------+
|Phone-Type: | | Type of phone, e.g. Work or Home | |Phone-Type: | | Type of phone, e.g. Work or Home |
skipping to change at page 11, line 4 skipping to change at line 439
| | | durations characteristic of the | | | | durations characteristic of the |
| | | resource | | | | resource |
|Rights: | | Information concerning the | |Rights: | | Information concerning the |
| | | intellectual property rights that | | | | intellectual property rights that |
| | | are being exercised over the | | | | are being exercised over the |
| | | resource (including access terms) | | | | resource (including access terms) |
|(RECORD*) | | Record information | |(RECORD*) | | Record information |
+--------------------------+--------+-------------------------------------+ +--------------------------+--------+-------------------------------------+
ORGANIZATION template ORGANIZATION template
This template is used to hold details about an organization. In This template is used to hold details about an organization. In
practice both spellings - "ORGANISATION" and "ORGANIZATION" - may be practice both spellings - "ORGANISATION" and "ORGANIZATION" - may be
in use. We recommend that ORGANIZATION be given preference to avoid in use. We recommend that ORGANIZATION be given preference to avoid
confusion. confusion.
+--------------------------+--------+---------------------------------+ +-----------------------------+--------+---------------------------------+
|Name | Rec. ? | Description | |Name | Rec. ? | Description |
+--------------------------+--------+---------------------------------+ +-----------------------------+--------+---------------------------------+
|Keywords: | | Any keywords which might | |Keywords: | | Any keywords which might |
| | | facilitate finding this | | | | facilitate finding this |
| | | record | | | | record |
|Internet-Domain: | | Organization's Internet | |Internet-Domain: | | Organization's Internet |
| | | domain name | | | | domain name |
|Domain-Contact-(PERSON*): | | Admin contact for this | |Domain-Contact-(PERSON*): | | Admin contact for this |
| | | domain | | | | domain |
|(ORGANIZATION*) | | Actual organization information | |(ORGANIZATIION*) | | Actual organization information |
|(RECORD*) | | Record information | |(RECORD*) | | Record information |
+--------------------------+--------+---------------------------------+ +-----------------------------+--------+---------------------------------+
ORG-ROLE template
This template is used to hold details about a particular role within
an organization. These roles (like "president", "front desk",
"service counter") may or may not be associated with a person or
persons. This template will contain necessary contact information
for the role irrespective of the (current) incumbent person, if any.
+------------------------------+--------+-------------------------------+
|Name | Rec. ? | Description |
+------------------------------+--------+-------------------------------+
|Keywords: | | Any keywords which might |
| | | facilitate finding this |
| | | record |
|Org-Role: | R | Name of the role |
|(EMAIL*) | | E-mail contact info for role |
|(PHONE*) | | Phone contact info for role |
|Organization-(ORGANIZATION*) | | The organization to which |
| | | this role belongs |
|(NAME*) | | Name of person in role |
|(PGP-PUBLIC-KEY*) | | The role's PGP public key(s) |
|(RECORD*) | | Record information |
+------------------------------+--------+-------------------------------+
SERVICE template SERVICE template
This template is used to describe an on-line service. This template is used to describe an on-line service.
+---------------------------+--------+---------------------------------+ +---------------------------+--------+---------------------------------+
|Name | Rec. ? | Description | |Name | Rec. ? | Description |
+---------------------------+--------+---------------------------------+ +---------------------------+--------+---------------------------------+
|Title: | R | Title of object | |Title: | R | Title of object |
|Category: | | Type of object | |Category: | | Type of object |
skipping to change at page 13, line 4 skipping to change at line 534
| | | mark for this resource | | | | mark for this resource |
|To-Be-Reviewed-Date: | | Date on which the | |To-Be-Reviewed-Date: | | Date on which the |
| | | resource is to be re-assessed | | | | resource is to be re-assessed |
|Comments: | | Comments by the template | |Comments: | | Comments by the template |
| | | creators | | | | creators |
|Destination: | | Which database the | |Destination: | | Which database the |
| | | template is destined for | | | | template is destined for |
|(PGP-PUBLIC-KEY*) | | PGP public key(s) | |(PGP-PUBLIC-KEY*) | | PGP public key(s) |
|(RECORD*) | | Record information | |(RECORD*) | | Record information |
+---------------------------+--------+---------------------------------+ +---------------------------+--------+---------------------------------+
USER template USER template
This template is used to hold details about a person. This template is used to hold details about a person.
The IDS Working Group of the IETF has proposed an abstract schema for
Internet white pages services [11]; the details of how that abstract schema
can be represented in a WHOIS++ USER template are provided in
Appendix C.
+------------------+--------+-------------------------------------+ +------------------+--------+-------------------------------------+
|Name | Rec. ? | Description | |Name | Rec. ? | Description |
+------------------+--------+-------------------------------------+ +------------------+--------+-------------------------------------+
|Keywords: | | Any keywords which might facilitate | |Keywords: | | Any keywords which might facilitate |
| | | finding this record | | | | finding this record |
|(PERSON*) | | Actual user information | |(PERSON*) | | Actual user information |
|(PGP-PUBLIC-KEY*) | | Their PGP public | |(PGP-PUBLIC-KEY*) | | Their PGP public |
| | | key(s) | | | | key(s) |
|X509-CERT-URI | | URI for the USER's X.509 certificate|
| | | (May be a Whois++ URI for the |
| | | appropriate X509-CERT template) |
|(RECORD*) | | Record information | |(RECORD*) | | Record information |
+------------------+--------+-------------------------------------+ +------------------+--------+-------------------------------------+
X509-CERT template X509-CERT template
This template is used to describe an X.509 [5] certificate. This template is used to describe an X.509 [5] certificate.
+--------------------+--------+--------------------------------+ +--------------------+--------+--------------------------------+
|Name | Rec. ? | Description | |Name | Rec. ? | Description |
+--------------------+--------+--------------------------------+ +--------------------+--------+--------------------------------+
skipping to change at page 16, line 45 skipping to change at line 707
mailing list - whoispp-schema@bunyip.com. Send mail to major- mailing list - whoispp-schema@bunyip.com. Send mail to major-
domo@bunyip.com with the message body "subscribe whoispp-schema" to domo@bunyip.com with the message body "subscribe whoispp-schema" to
join the list. join the list.
10. Acknowledgements 10. Acknowledgements
Thanks to Lorcan Dempsey and Rachel Heery for their comments on draft Thanks to Lorcan Dempsey and Rachel Heery for their comments on draft
versions of this document, and to Francois Perrault for initial work versions of this document, and to Francois Perrault for initial work
on WHOIS++ template usage. on WHOIS++ template usage.
This work was supported by UK Electronic Libraries Programme (eLib) This work was supported in part by UK Electronic Libraries Programme
grant 12/39/01, the European Commission's Telematics for Research (eLib) grant 12/39/01, the European Commission's Telematics for Research
Programme, grant RE 1004, and National Science Foundation grant Programme, grant RE 1004, and National Science Foundation grant
NCR-9521074. NCR-9521074.
11. References 11. References
Request for Comments (RFC) documents and Internet Drafts are available Request for Comments (RFC) documents and Internet Drafts are available
from <URL:ftp://ftp.internic.net/rfc/>, and numerous mirror sites. from <URL:ftp://ftp.internic.net/rfc/>, and numerous mirror sites.
[1] P. Deutsch, R. Schoultz, P. Faltstrom and C. Weider. "Archi- [1] P. Deutsch, R. Schoultz, P. Faltstrom and C. Weider. "Archi-
tecture of the WHOIS++ service", RFC 1835. August 1995. tecture of the WHOIS++ service", RFC 1835. August 1995.
skipping to change at page 17, line 46 skipping to change at line 753
[9] S. Weibel, E. Miller. Dublin Core Home Page. [9] S. Weibel, E. Miller. Dublin Core Home Page.
<URL:http://purl.org/metadata/dublin_core> <URL:http://purl.org/metadata/dublin_core>
[10] L. Dempsey, S. Weibel. "The Warwick Metadata Workshop: A [10] L. Dempsey, S. Weibel. "The Warwick Metadata Workshop: A
Framework for the Deployment of Resource Description", D-Lib Maga- Framework for the Deployment of Resource Description", D-Lib Maga-
zine, July/August 1996. zine, July/August 1996.
<URL:http://www.ukoln.ac.uk/dlib/dlib/july96/07weibel.html> <URL:http://www.ukoln.ac.uk/dlib/dlib/july96/07weibel.html>
<URL:http://www.dlib.org/dlib/july96/07weibel.html> <URL:http://www.dlib.org/dlib/july96/07weibel.html>
[11] T. Genovese, Barbara Jennings, "A Common Schema for the Internet
White Pages Service", IETF IDS Working Group draft, June 1997.
12. Authors' addresses 12. Authors' addresses
Patrik Faltstrom Patrik Faltstrom
Tele2/Swipnet Tele2/Swipnet
Box 62 Box 62
Borgarfjordsgatan 16 Borgarfjordsgatan 16
S-164 94 Kista S-164 94 Kista
Sweden Sweden
Email: paf@swip.net Email: paf@swip.net
skipping to change at line 915 skipping to change at line 961
for use in describing document-like objects, and not as a means of for use in describing document-like objects, and not as a means of
describing arbitrary objects. Furthermore, the number of elements is describing arbitrary objects. Furthermore, the number of elements is
strictly limited in the interests of interoperability. strictly limited in the interests of interoperability.
Work is ongoing on the Warwick Framework [10], which attempts to pro- Work is ongoing on the Warwick Framework [10], which attempts to pro-
vide a mechanism for packaging together collections of descriptive vide a mechanism for packaging together collections of descriptive
information. It is envisaged that this would be used in cases where information. It is envisaged that this would be used in cases where
the Dublin Core element set did not provide enough descriptive capa- the Dublin Core element set did not provide enough descriptive capa-
bility. This is a subject for further study and is beyond the scope bility. This is a subject for further study and is beyond the scope
of this specification. of this specification.
APPENDIX C: Representing the Internet Whitepages Schema (IWPS) in WHOIS++
The IETF's IDS working group has defined a standardized abstract schema
for "a simple Internet Whitepages Service". The reader is referred to
the documentation describing that schema ([11]) for details on the expected
syntax, precise content and length limitations for individual attributes.
+-------------------------+-----------------------------------+
| IWPS Field | WHOIS++ USER Template Attribute |
+-------------------------+-----------------------------------+
| Email | Email or Email-X400 |
| Cert | (* see below) |
| Home Page | Homepage-URI |
| Common Name | Name |
| Given Name | Name-First |
| Surname | Name-Last |
| Organization | Organization-Name |
| Locality | Address-Locality |
| Country | Address-Country |
| Language Spoken | Language-Pref |
| Personal Phone | Phone |
| Personal Fax | Fax |
| Personal Mobile Phone | Cellular |
| Personal Pager Number | Pager |
| Personal Postal Address | Address |
| Description | Picture-URI |
| Title | Title |
| Office Phone | Organization-Phone |
| Office Fax | Organization-Fax |
| Office Mobile Phone | Organization-Cellular |
| Office Pager | Organization-Page |
| Office Postal Address | Organization-Address |
| Creation Date | Record-Creation-Date |
| Creator Name | Record-Creation-Contact-Name |
| Modified Date | Record-Last-Modified-Date |
| Modifier Name | Record-Last-Modified-Contact-Name|
+-------------------------+-----------------------------------+
The "Cert" attribute, as described by the IWPS document, is as follows:
"The certificate field is intended to hold any kind of certificate; X.509
certificates are one example. A specific implementation will specify
how to indicate the type of certificate when describing the mapping of
the IWPS schema onto the implementation schema."
As the Whois++ USER certificate is set up to accommodate both PGP
keys and X.509 pointers, this one IWPS field is defined to conditionally
be mapped to the appropriate fields for each technology:
PGP-Version
PGP-Key-Length
PGP-Key-ID
PGP-Fingerprint
PGP-Public-Key
and/or
PGP-Public-Key-URI
and/or
X509-CERT-URI
with appropriate attendant information (e.g. PGP-NAME, etc) as appropriate.
 End of changes. 17 change blocks. 
8 lines changed or deleted 52 lines changed or added

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