home
***
CD-ROM
|
disk
|
FTP
|
other
***
search
/
Internet Info 1997 December
/
Internet_Info_CD-ROM_Walnut_Creek_December_1997.iso
/
drafts
/
draft_ietf_i
/
draft-ietf-ids-iwps-schema-spec-07.txt
< prev
next >
Wrap
Text File
|
1997-10-10
|
2KB
|
68 lines
A new Request for Comments is now available in online RFC libraries.
RFC 2218
Title: A Common Schema for the Internet White Pages
Service
Author: T. Genovese, B. Jennings
Status: Proposed Standard
Date: October 1997
Mailbox: TonyG@Microsoft.com, jennings@sandia.gov
Pages: 8
Characters: 16258
Updates/Obsoletes: None
URL: ftp://ds.internic.net/rfc/rfc2218.txt
This document specifies the minimum set of core attributes of a White
Pages entry for an individual and describes how new objects with those
attributes can be defined and published. It does not describe how to
represent other objects in the White Pages service. Further, it does
not address the search sort expectations within a particular service.
This document is a product of the Integrated Directory Services
Working Group of the IETF.
This is now a Proposed Standard Protocol.
This document specifies an Internet standards track protocol for
the Internet community, and requests discussion and suggestions
for improvements. Please refer to the current edition of the
"Internet Official Protocol Standards" (STD 1) for the
standardization state and status of this protocol. Distribution
of this memo is unlimited.
This announcement is sent to the IETF list and the RFC-DIST list.
Requests to be added to or deleted from the IETF distribution list
should be sent to IETF-REQUEST@IETF.ORG. Requests to be
added to or deleted from the RFC-DIST distribution list should
be sent to RFC-DIST-REQUEST@ISI.EDU.
Details on obtaining RFCs via FTP or EMAIL may be obtained by sending
an EMAIL message to rfc-info@ISI.EDU with the message body
help: ways_to_get_rfcs. For example:
To: rfc-info@ISI.EDU
Subject: getting rfcs
help: ways_to_get_rfcs
Requests for special distribution should be addressed to either the
author of the RFC in question, or to admin@DS.INTERNIC.NET. Unless
specifically noted otherwise on the RFC itself, all RFCs are for
unlimited distribution.
Submissions for Requests for Comments should be sent to
RFC-EDITOR@ISI.EDU. Please consult RFC 1543, Instructions to RFC
Authors, for further information.
Joyce K. Reynolds and Alegre Ramos
USC/Information Sciences Institute