Debian Codegraph @

rfc2218.html

raw
1 <pre>Network Working Group T. Genovese
2 Request for Comments: 2218 Microsoft
3 Category: Standards Track B. Jennings
4 Sandia National Laboratory
5 October 1997
6
7
8 <span class="h1">A Common Schema for the Internet White Pages Service</span>
9
10
11 Status of this Memo
12
13 This document specifies an Internet standards track protocol for the
14 Internet community, and requests discussion and suggestions for
15 improvements. Please refer to the current edition of the "Internet
16 Official Protocol Standards" (STD 1) for the standardization state
17 and status of this protocol. Distribution of this memo is unlimited.
18
19 Abstract
20
21 This work is the result of the IETF Integrated Directory Services
22 (IDS) Working Group. The IDS Working Group proposes a standard
23 specification for a simple Internet White Pages service by defining a
24 common schema for use by the various White Pages servers. This
25 schema is independent of specific implementations of the White Pages
26 service.
27
28 This document specifies the minimum set of core attributes of a White
29 Pages entry for an individual and describes how new objects with
30 those attributes can be defined and published. It does not describe
31 how to represent other objects in the White Pages service. Further,
32 it does not address the search sort expectations within a particular
33 service.
34
35 <span class="h3"><a class="selflink" id="section-1.0" href="#section-1.0">1.0</a> Introduction to IWPS</span>
36
37 The Internet community has stated a need for the development and
38 deployment of a White Pages service for use in locating information
39 about people in the Internet [<a href="#ref-PA94" title="&quot;WHITE PAGES MEETING REPORT&quot;">PA94</a>]. To facilitate interoperability
40 and to provide a common user experience, the Internet White Pages
41 Service (IWPS) must have a common set of information about each
42 person.
43
44 A common user object would allow a user to go between implementations
45 of the service and to expect consistency in the types of information
46 provided. A common user object would also provide developers with an
47 unambigious method of representing the information managed by the
48 service.
49
50
51
52 <span class="grey">Genovese &amp; Jennings Standards Track [Page 1]</span></pre>
53 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-2" ></span>
54 <span class="grey"><a href="./rfc2218">RFC 2218</a> Common Schema for IWPS October 1997</span>
55
56
57 This document will focus only on common information modeling issues
58 to which all IWPS providers must conform.
59
60 <span class="h3"><a class="selflink" id="section-2.0" href="#section-2.0">2.0</a> Scope</span>
61
62 This document establishes the set of attributes that specify the
63 Common User Information Object for the IWPS. It does not attempt to
64 be an exhaustive specification of all objects that may be stored in
65 the IWPS. The process used by this document to define the user object
66 is recommended to be used to define other information objects used in
67 the IWPS.
68
69 All conforming implementations must support at the minimum, the core
70 attributes listed in <a href="#section-5.0">Section 5.0</a>. Implementations may include local
71 attributes in addition to the core set and still be considered "in
72 conformance".
73
74 This document will not specify rules with respect to information
75 privacy. Each country has its own set of laws and practices.
76 Previous work covering this area has been done by the North American
77 Directory Forum (NADF), whose publication [<a href="#ref-NADF92" title=" North American Directory Forum">NADF92</a>] contain
78 recommendations for registrants' rights in both the USA and Canada.
79
80 This document does not specify a Directory access protocol (i.e.
81 whois++, LDAP, DAP, etc.).
82
83 <span class="h3"><a class="selflink" id="section-3.0" href="#section-3.0">3.0</a> IWPS Schema Considerations</span>
84
85 The description of the IWPS information object consists of the
86 following requirements:
87
88 1. Syntax for definition/representation of information
89 object templates.
90 2. Publication of information object templates, etc.
91 3. Database structure or schema.
92
93 Items 1 and 2 will be covered in this document. Because database
94 structure can potentially restrict implementations (i.e. X.500 schema
95 based versus DNS schema based) it will be treated as a separate
96 research topic and will not be defined in this paper.
97
98 <span class="h3"><a class="selflink" id="section-4.0" href="#section-4.0">4.0</a> Syntax for Definition/Representation of Information Object</span>
99 <span class="h3"> Templates</span>
100
101 A clear, precise, and consistent method must be used when discussing
102 information object templates and their associated attributes.
103 Therefore, this document makes uses of the previously defined syntax
104 used by LDAP. To avoid restrictions on implementations of the IWPS,
105
106
107
108 <span class="grey">Genovese &amp; Jennings Standards Track [Page 2]</span></pre>
109 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-3" ></span>
110 <span class="grey"><a href="./rfc2218">RFC 2218</a> Common Schema for IWPS October 1997</span>
111
112
113 some syntax are listed as requirements vs specific encodings. The
114 general IWPS syntax is included in <a href="#section-6.0">section 6.0</a> for reference.
115
116 The IWPS Person Object specifies a limited set of recommended
117 attributes that a White Pages Service must include. Storage of user
118 attributes are a local issue, therefore, this memo suggests storage
119 sizes but not storage types.
120
121 This document lists the syntax with the attributes for developers of
122 user interface (UIs) to use as a reference, but it does not specify
123 how the UI should display these attributes.
124
125 Attributes that contain multiple-line text (i.e. Address) must use
126 the procedure defined in <a href="./rfc822">RFC 822</a> in <a href="#section-3.1.1">section 3.1.1</a> on "folding" long
127 header lines [<a href="./rfc822" title="&quot;Standard for the Format of ARPA Internet Text Messages&quot;">RFC-822</a>].
128
129 <span class="h3"><a class="selflink" id="section-5.0" href="#section-5.0">5.0</a> Information Object Template Definitions</span>
130
131 This section describes the IWPS Person Information Object Template
132 and its associated attributes. The Person Object is a simple list of
133 attributes, no structure nor object inheritance is implied.
134
135 IWPS client applications should use the following size
136 recommendations as the maximum sizes of the attributes. However,
137 applications should be able to handle attributes of arbitrary size,
138 returned by a server which may not comply with these recommendation.
139 All size recommendations are in characters.
140
141 Note: Because many characters in many encodings require more than one
142 byte, the size recommendations cannot be interpreted as sizes in
143 bytes.
144
145 This set of attributes describes information types, and are not
146 defined attributes in a particular schema. Any technology deploying
147 a White Page service (WHOIS ++, LDAP, vCard, etc.) will need to
148 publish as a companion document, their specific schema detailing how
149 the general attributes of the White Pages schema are expressed.
150
151 SPECIAL CONSIDERATIONS
152
153 Phone number: The full international form is recommended;
154 i.e. +1 206 703 0852. The field may contain
155 additional information following the phone
156 number. For example:
157
158 +1 800 759 7243 #123456
159 +1 505 882 8080 ext. 30852
160
161
162
163
164 <span class="grey">Genovese &amp; Jennings Standards Track [Page 3]</span></pre>
165 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-4" ></span>
166 <span class="grey"><a href="./rfc2218">RFC 2218</a> Common Schema for IWPS October 1997</span>
167
168
169 Email address: Is multivalued.
170
171 Certificate: Is multivalued.
172
173 Common Name: Is multivalued.
174
175 Language Spoken: Is multivalued.
176
177 THE INFORMATION OBJECT TEMPLATE FOR THE IWPS PERSON
178
179 --General Attributes --
180
181 Field Name Size Syntax
182
183 Email 360 Mailbox
184 Cert 4000 Certificate
185 Home Page 128 URI
186 Common Name 64 WhitepageString
187 Given Name 48 WhitepageString
188 Surname 48 WhitepageString
189 Organization 64 WhitepageString
190 Locality 20 WhitepageString
191 Country 2 WhitepageString (ISO 3166)
192 Language Spoken 128 WhitepageString (<a href="./rfc1766">RFC 1766</a>)
193
194 --Personal Attributes
195
196 Personal Phone 30 PrintableString
197 Personal Fax 30 PrintableString
198 Personal Mobile Phone 30 PrintableString
199 Personal Pager Number 30 PrintableString
200 Personal Postal Address 255 Address
201 Description 255 WhitepageString
202
203 --Organizational Attributes
204
205 Title 64 WhitepageString
206 Office Phone 30 PrintableString
207 Office Fax 30 PrintableString
208 Office Mobile Phone 30 PrintableString
209 Office Pager 30 PrintableString
210 Office Postal Address 255 Address
211
212 --Ancillary
213
214 Creation Date 24 GeneralizedTime
215 Creator Name 255 URI
216 Modified Date 24 GeneralizedTime
217
218
219
220 <span class="grey">Genovese &amp; Jennings Standards Track [Page 4]</span></pre>
221 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-5" ></span>
222 <span class="grey"><a href="./rfc2218">RFC 2218</a> Common Schema for IWPS October 1997</span>
223
224
225 Modifier Name 255 URI
226
227 <span class="h3"><a class="selflink" id="section-6.0" href="#section-6.0">6.0</a> IWPS Person Information Object Template Syntax</span>
228
229 This section defines the syntax used by the IWPS person information
230 object template. It is copied in whole from the LDAP attribute
231 working document with some modification for completeness.
232
233 Certificate:
234
235 The certificate field is intended to hold any kind of certificate;
236 X.509 certificates are one example. A specific implementation will
237 specify how to indicate the type of certificate when describing
238 the mapping of the IWPS schema onto the implementation schema.
239
240 WhitepageString:
241
242 This syntax must be able to encode arbitrary ISO 10646 characters.
243 One such encoding is the UTF-8 encoding [<a href="#ref-UTF-8" title="&quot;UTF-8, a transformation format of ISO 10646&quot;">UTF-8</a>].
244
245 GeneralizedTime:
246
247 Values of this syntax are encoded as printable strings,
248 represented as specified in X.208. Note that the time zone must
249 be specified. It is strongly recommended that Zulu time zone be
250 used. For example:
251
252 199412161032Z
253
254 Mailbox:
255
256 here are many kinds of mailbox addresses, including X.400 and
257 Internet mailbox addresses. The implementation must clearly
258 distinguish between different types of mailbox address, for
259 instance by using a textual refix or a set of attribute types.
260 There must be a way to represent any mailbox type.
261
262 Address:
263
264 According to Universal Postal Union standards, this field must be
265 able to represent at least 6 lines of 40 characters.
266
267 PrintableString:
268
269 The encoding of a value with PrintableString syntax is the string
270 value itself. PrintableString is limited to the characters in
271 production &lt;p&gt;. Where production &lt;p&gt; is described by the
272 following:
273
274
275
276 <span class="grey">Genovese &amp; Jennings Standards Track [Page 5]</span></pre>
277 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-6" ></span>
278 <span class="grey"><a href="./rfc2218">RFC 2218</a> Common Schema for IWPS October 1997</span>
279
280
281 &lt;a&gt; ::= 'a' | 'b' | 'c' | 'd' | 'e' | 'f' | 'g' | 'h' | 'i' |
282 'j' | 'k' | 'l' | 'm' | 'n' | 'o' | 'p' | 'q' | 'r' |
283 's' | 't' | 'u' | 'v' | 'w' | 'x' | 'y' | 'z' | 'A' |
284 'B' | 'C' | 'D' | 'E' | 'F' | 'G' | 'H' | 'I' | 'J' |
285 'K' | 'L' | 'M' | 'N' | 'O' | 'P' | 'Q' | 'R' | 'S' |
286 'T' | 'U' | 'V' | 'W' | 'X' | 'Y' | 'Z'
287
288 &lt;d&gt; ::= '0' | '1' | '2' | '3' | '4' | '5' | '6' | '7' | '8' | '9'
289
290
291 &lt;p&gt; ::= &lt;a&gt; | &lt;d&gt; | ''' | '(' | ')' | '+' | ',' | '-' | '.' |
292 '/' | ':' | '?' | ' '
293
294 <span class="h3"><a class="selflink" id="section-7.0" href="#section-7.0">7.0</a> Publication of IWPS Information Object Templates.</span>
295
296 The Working Group recommends that all information object templates
297 used for the IWPS be published.
298
299 Individual organizations may define information object templates that
300 are local in scope as required to meet local organizational needs.
301 All information that the organization wishes to be part of the IWPS
302 must use a published IWPS information object template.
303
304 <span class="h3"><a class="selflink" id="section-8.0" href="#section-8.0">8.0</a> Data Privacy</span>
305
306 Each country, and each state within the US, has legislation defining
307 information privacy. The suggested attributes in <a href="#section-5.0">Section 5.0</a> may be
308 considered private and the directory administrator is strongly
309 advised to verify the privacy legislation for his domain.
310
311 As suggested in "Privacy and Accuracy in NIC Databases" [<a href="./rfc1355" title="&quot;Privacy and Accuracy Issues in Network Information Center Databases&quot;">RFC-1355</a>],
312 each directory provider should provide a clear statement of the
313 purpose of the directory, the information that should be contained in
314 it, and a privacy policy associated with that information. This
315 policy should include restrictions for data dissemination.
316
317 This policy is strongly recommended for the US and Canada and
318 required by many countries in the European Community for data
319 sharing.
320
321 <span class="h3"><a class="selflink" id="section-9.0" href="#section-9.0">9.0</a> Data Integrity</span>
322
323 Data Integrity was first addressed in <a href="./rfc1107">RFC 1107</a> [<a href="#ref-KS89" title="&quot;A Plan for Internet Directory Services&quot;">KS89</a>], which states
324 "a White Pages service will not be used, if the information it
325 provides is out of date or incorrect." Therefore, any production
326 IWPS provider must insure that all data is reasonably correct and
327 up-to-date.
328
329
330
331
332 <span class="grey">Genovese &amp; Jennings Standards Track [Page 6]</span></pre>
333 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-7" ></span>
334 <span class="grey"><a href="./rfc2218">RFC 2218</a> Common Schema for IWPS October 1997</span>
335
336
337 The Ancillary Attributes of the IWPS person template denote the
338 information's source and date of origin, and the source and date of
339 its latest modification. They provide the user with some measurement
340 of the quality of data making it easy to determine the owner and
341 freshness of the data retrieved.
342
343 The IWPS User Agent must be able to retrieve and display Ancillary
344 Attributes. Retrieval and display may be done as separate
345 operations.
346
347 The Ancillary Attributes are recommended as the minimum set of
348 attributes for any new information object template. Each IWPS server
349 may individually decide whether to support the storage and retrieval
350 of this data.
351
352 The Ancillary Attributes (also defined in <a href="#section-5.0">Section 5.0</a>) provide the
353 following information about its associated information object:
354
355 1. The date and time the entry was created; Creation Date.
356
357 2. Owner or individual responsible for the data creation;
358 Creator Name.
359
360 3. The date and time of the last modification;
361 Modified Date.
362
363 4. Individual responsible for the last modification;
364 Modifier Name.
365
366 <span class="h3"><a class="selflink" id="section-10.0" href="#section-10.0">10.0</a> Security Considerations</span>
367
368 Security is implementation and deployment specific and as such is not
369 addressed in this memo. Security must ensure that the constraints
370 mentioned in the Data Privacy <a href="#section-8.0">Section 8.0</a> are complied with.
371
372 <span class="h3"><a class="selflink" id="section-11.0" href="#section-11.0">11.0</a> References</span>
373
374 [<a id="ref-KS89">KS89</a>] Sollins, K., "A Plan for Internet Directory Services", <a href="./rfc1107">RFC</a>
375 <a href="./rfc1107">1107</a>, Laboratory for Computer Science, MIT, July 1989.
376
377 [<a id="ref-NADF92">NADF92</a>] North American Directory Forum, "User Bill of Rights for
378 entries and listings in the Public Directory', <a href="./rfc1295">RFC 1295</a>,
379 North American Directory Forum, January 1992.
380
381
382
383
384
385
386
387
388 <span class="grey">Genovese &amp; Jennings Standards Track [Page 7]</span></pre>
389 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-8" ></span>
390 <span class="grey"><a href="./rfc2218">RFC 2218</a> Common Schema for IWPS October 1997</span>
391
392
393 [<a id="ref-PA94">PA94</a>] Postel, J., and C. Anderson, "WHITE PAGES MEETING REPORT",
394 <a href="./rfc1588">RFC 1588</a>, University of Southern California, February 1994.
395
396 [<a id="ref-RFC-822">RFC-822</a>] Crocker, D., "Standard for the Format of ARPA Internet
397 Text Messages", STD 11, <a href="./rfc822">RFC 822</a>, August 1982.
398
399 [<a id="ref-RFC-1355">RFC-1355</a>] Curran, J., and A. Marine, "Privacy and Accuracy Issues
400 in Network Information Center Databases", FYI 15, <a href="./rfc1355">RFC 1355</a>, August
401 1992.
402
403 [<a id="ref-UCS">UCS</a>] Universal Multiple-Octet Coded Character Set (UCS) -
404 Architecture and Basic Multilingual Plane, ISO/IEC 10646-1, 1993.
405
406 [<a id="ref-RFC-1766">RFC-1766</a>] Alvestrand, H., "Tags for the Identification of
407 Languages", <a href="./rfc1766">RFC 1766</a>, March 1995.
408
409 [<a id="ref-UTF-8">UTF-8</a>] Yergeau, F., <a style="text-decoration: none" href='https://www.google.com/search?sitesearch=datatracker.ietf.org%2Fdoc%2Fhtml%2F&amp;q=inurl:draft-+%22UTF-8%2C+a+transformation+format+of+ISO+10646%22'>"UTF-8, a transformation format of ISO 10646"</a>,
410 Work in Progress.
411
412 <span class="h3"><a class="selflink" id="section-11.0" href="#section-11.0">11.0</a> Authors' Addresses</span>
413
414 Tony Genovese
415 The Microsoft Corporation
416 One Microsoft Way
417 Redmond, Washington 98007
418 USA
419
420 Phone: (206) 703-0852
421 EMail: [email protected]
422
423
424 Barbara Jennings
425 Sandia National Laboratories
426 Albuquerque, New Mexico 87106
427 USA
428
429 Phone: (505) 845-8554
430 EMail: [email protected]
431
432
433
434
435
436
437
438
439
440
441
442
443
444 Genovese &amp; Jennings Standards Track [Page 8]
445 </pre>