7 INTERNET-DRAFT Editor: Kurt D. Zeilenga
8 Intended Category: Standard Track OpenLDAP Foundation
9 Expires in six months 9 December 2002
13 Language Tags and Ranges in LDAP
14 draft-zeilenga-ldap-rfc2596-04.txt
19 This document is an Internet-Draft and is in full conformance with all
20 provisions of Section 10 of RFC2026.
22 This document is intended to be, after appropriate review and
23 revision, submitted to the RFC Editor as a Standard Track document.
24 Distribution of this memo is unlimited. Technical discussion of this
25 document will take place on the IETF LDAP Extensions Working Group
26 (LDAPext) mailing list <ldapext@ietf.org>. Please send editorial
27 comments directly to the document editor <Kurt@OpenLDAP.org>.
29 Internet-Drafts are working documents of the Internet Engineering Task
30 Force (IETF), its areas, and its working groups. Note that other
31 groups may also distribute working documents as Internet-Drafts.
32 Internet-Drafts are draft documents valid for a maximum of six months
33 and may be updated, replaced, or obsoleted by other documents at any
34 time. It is inappropriate to use Internet-Drafts as reference
35 material or to cite them other than as ``work in progress.''
37 The list of current Internet-Drafts can be accessed at
38 <http://www.ietf.org/ietf/1id-abstracts.txt>. The list of
39 Internet-Draft Shadow Directories can be accessed at
40 <http://www.ietf.org/shadow.html>.
42 Copyright 2002, The Internet Society. All Rights Reserved.
44 Please see the Copyright section near the end of this document for
49 It is often desirable to to be able to indicate the natural language
50 associated with values held in a directory and to be able to query the
51 directory for values which fulfill the user's language needs. This
52 document details the use of Language Tags and Ranges in the
53 Lightweight Directory Access Protocol (LDAP).
58 Zeilenga Language Tags and Ranges in LDAP [Page 1]
60 INTERNET-DRAFT draft-zeilenga-ldap-rfc2596-04.txt 9 December 2002
65 The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
66 "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this
67 document are to be interpreted as described in BCP 14 [RFC2119].
70 1. Background and Intended Use
72 The Lightweight Directory Access Protocol (LDAP) [RFC3377] provides a
73 means for clients to interrogate and modify information stored in a
74 distributed directory system. The information in the directory is
75 maintained as attributes of entries. Most of these attributes have
76 syntaxes which are human-readable strings, and it is desirable to be
77 able to indicate the natural language associated with attribute
80 This document describes how language tags and ranges [RFC3066] are
81 carried in LDAP and are to be interpreted by LDAP implementations.
82 All LDAP implementations MUST be prepared to accept language tags and
85 This document replaces RFC 2596. Appendix A summaries changes made
88 Appendix B discusses differences from X.500(1997) "contexts"
91 Appendix A and B are provided for informational purposes only.
93 The remainder of this section provides a summary of Language Tags,
94 Language Ranges, and Attribute Descriptions.
99 Section 2 of BCP 47 [RFC3066] describes the language tag format which
100 is used in LDAP. Briefly, it is a string of ASCII letters and
101 hyphens. Examples include "fr", "en-US" and "ja-JP". Language tags
102 are case insensitive. That is, the language tag "en-us" is the same
105 Section 2 of this document details use of language tags in LDAP.
110 Section 2.5 of BCP 47 [RFC3066] describes the language ranges.
114 Zeilenga Language Tags and Ranges in LDAP [Page 2]
116 INTERNET-DRAFT draft-zeilenga-ldap-rfc2596-04.txt 9 December 2002
119 Language ranges are used to specify sets of language tags.
121 A language range matches a language tag if it is exactly equal to the
122 tag, or if it is exactly equal to a prefix of the tag such that the
123 first character following the prefix is "-". That is, the language
124 range "de" matches the language tags "de" and "de-CH" but not "den".
125 The special language range "*" matches all language tags.
127 Due to attribute description option naming restrictions in LDAP, this
128 document defines a different language range syntax. However, the
129 semantics of language ranges in LDAP is consistent with BCP 47.
131 Section 3 of this document details use of language ranges in LDAP.
134 1.3. Attribute Descriptions
136 This section provides an overview of attribute descriptions in LDAP.
137 LDAP attributes and attribute descriptions are defined in [RFC2251].
139 An attribute consists of a type, a set of zero or more associated
140 tagging options, and a set of one or more values. The type and the
141 options are combined into the AttributeDescription.
142 AttributeDescriptions can also contain options which are not part of
143 the attribute, but indicate some other function (such as range
144 assertion or transfer encoding).
146 An AttributeDescription with one or more tagging options is a direct
147 subtype of each AttributeDescription of the same type with all but one
148 of the tagging options. If the AttributeDescription's type is a
149 direct subtype of some other type, then the AttributeDescription is
150 also a direct subtype of the AttributeDescription which consists of
151 the supertype and all of the tagging options. That is,
152 "CN;x-bar;x-foo" is a direct subtype of "CN;x-bar", "CN;x-foo", and
153 "name;x-bar;x-foo". Note that "CN" is a subtype of "name".
156 2. Use of Language Tags in LDAP
158 This section describes how LDAP implementations MUST interpret
159 language tags in performing operations.
161 Servers which support storing attributes with language tag options in
162 the Directory Information Tree (DIT) SHOULD allow any attribute type
163 it recognizes that has the Directory String, IA5 String, or other
164 textual string syntaxes to have language tag options associated with
165 it. Servers MAY allow language options to be associated with other
170 Zeilenga Language Tags and Ranges in LDAP [Page 3]
172 INTERNET-DRAFT draft-zeilenga-ldap-rfc2596-04.txt 9 December 2002
175 Clients SHOULD NOT assume servers are capable of storing attributes
176 with language tags in the directory.
178 Implementations MUST NOT otherwise interpret the structure of the tag
179 when comparing two tag, and MUST treat them simply as strings of
180 characters. Implementations MUST allow any arbitrary string which
181 conforms to the syntax defined in BCP 47 [RFC3066] to be used as a
185 2.1. Language Tag Options
187 A language tag option associates a natural language with values of an
188 attribute. An attribute description may contain multiple language tag
189 options. An entry may contain multiple attributes with same attribute
190 type but different combinations of language tag (and other) options.
192 A language tag option conforms to the following ABNF [RFC2234]:
194 language-tag-option = "lang-" Language-Tag
196 where the Language-Tag production is as defined in BCP 47 [RFC3066].
197 This production and those it imports from [RFC2234] are provided here
200 Language-Tag = Primary-subtag *( "-" Subtag )
202 Primary-subtag = 1*8ALPHA
204 Subtag = 1*8(ALPHA / DIGIT)
206 ALPHA = %x41-5A / %x61-7A ; A-Z / a-z
208 DIGIT = %x30-39 ; 0-9
210 A language tag option is a tagging option. A language tag option has
211 no effect on the syntax of the attribute's values nor their transfer
214 Examples of valid AttributeDescription:
218 SN;lang-de;lang-gem-PFL
219 O;lang-i-klingon;x-foobar
226 Zeilenga Language Tags and Ranges in LDAP [Page 4]
228 INTERNET-DRAFT draft-zeilenga-ldap-rfc2596-04.txt 9 December 2002
231 Notes: The last two have no language tag options. The x-foobar option
232 is fictious and used for example purposes.
237 If language tag options are present in an AttributeDescription in an
238 assertion, then for each entry within scope, the values of each
239 attribute whose AttributeDescription consists of the same attribute
240 type or its subtypes and contains each of the presented (and possibly
241 other) options is to be matched.
243 Thus, for example, a filter of an equality match of type
244 "name;lang-en-US" and assertion value "Billy Ray", against the
245 following directory entry:
247 dn: SN=Ray,DC=example,DC=com
248 objectclass: person DOES NOT MATCH (wrong type)
249 objectclass: extensibleObject DOES NOT MATCH (wrong type)
250 name;lang-en-US: Billy Ray MATCHES
251 name;lang-en-US: Billy Bob DOES NOT MATCH (wrong value)
252 CN;lang-en-US: Billy Ray MATCHES
253 CN;lang-en-US;x-foobar: Billy Ray MATCHES
254 CN;lang-en;x-foobar: Billy Ray DOES NOT MATCH (differing lang-)
255 CN;x-foobar: Billy Ray DOES NOT MATCH (no lang-)
256 name: Billy Ray DOES NOT MATCH (no lang-)
257 SN;lang-en-GB;lang-en-US: Billy Ray MATCHES
258 SN: Ray DOES NOT MATCH (no lang-,
261 Note that "CN" and "SN" are subtypes of "name".
263 It is noted that providing a language tag option in a search filter
264 AttributeDescription will filter out desirable values where the tag
265 does not match exactly. For example, the filter (name;lang-en=Billy
266 Ray) does NOT match the attribute "name;lang-en-US: Billy Ray".
268 If the server does not support storing attributes with language tag
269 options in the DIT, then any assertion which includes a language tag
270 option will not match as such it is an unrecognized attribute type.
271 No error would be returned because of this; a presence assertion would
272 evaluate to FALSE and all other assertions to Undefined.
274 If no options are specified in the assertion, then only the base
275 attribute type and the assertion value need match the value in the
278 Thus, for example, a filter of an equality match of type "name" and
282 Zeilenga Language Tags and Ranges in LDAP [Page 5]
284 INTERNET-DRAFT draft-zeilenga-ldap-rfc2596-04.txt 9 December 2002
287 assertion value "Billy Ray", against the following directory entry:
289 dn: SN=Ray,DC=example,DC=com
290 objectclass: person DOES NOT MATCH (wrong type)
291 objectclass: extensibleObject DOES NOT MATCH (wrong type)
292 name;lang-en-US: Billy Ray MATCHES
293 name;lang-en-US: Billy Bob DOES NOT MATCH (wrong value)
294 CN;lang-en-US;x-foobar: Billy Ray MATCHES
295 CN;lang-en;x-foobar: Billy Ray MATCHES
296 CN;x-foobar: Billy Ray MATCHES
297 name: Billy Ray MATCHES
298 SN;lang-en-GB;lang-en-US: Billy Ray MATCHES
299 SN: Ray DOES NOT MATCH (wrong value)
302 2.3. Requested Attributes in Search
304 Clients can provide language tag options in each AttributeDescription
305 in the requested attribute list in a search request.
307 If language tag options are provided in an attribute description, then
308 only attributes in a directory entry whose attribute descriptions have
309 the same attribute type or its subtype and contains each of the
310 presented (and possibly other) language tag options are to be
311 returned. Thus if a client requests just the attribute
312 "name;lang-en", the server would return "name;lang-en" and
313 "CN;lang-en;lang-ja" but not "SN" nor "name;lang-fr".
315 Clients can provide in the attribute list multiple
316 AttributeDescriptions which have the same base attribute type but
317 different options. For example, a client could provide both
318 "name;lang-en" and "name;lang-fr", and this would permit an attribute
319 with either language tag option to be returned. Note there would be
320 no need to provide both "name" and "name;lang-en" since all subtypes
321 of name would match "name".
323 If a server does not support storing attributes with language tag
324 options in the DIT, then any attribute descriptions in the list which
325 include language tag options are to be ignored, just as if they were
326 unknown attribute types.
328 If a request is made specifying all attributes or an attribute is
329 requested without providing a language tag option, then all attribute
330 values regardless of their language tag option are returned.
332 For example, if the client requests a "description" attribute, and a
333 matching entry contains the following attributes:
338 Zeilenga Language Tags and Ranges in LDAP [Page 6]
340 INTERNET-DRAFT draft-zeilenga-ldap-rfc2596-04.txt 9 December 2002
344 objectclass: organization
346 description: software products
347 description;lang-en: software products
348 description;lang-de: Softwareprodukte
350 The server would return:
352 description: software products
353 description;lang-en: software products
354 description;lang-de: Softwareprodukte
359 Language tag options can be present in an AttributeDescription used in
360 a compare request AttributeValueAssertion. This is to be treated by
361 servers the same as the use of language tag options in a search filter
362 with an equality match, as described in Section 2.2. If there is no
363 attribute in the entry with the same attribute type or its subtype and
364 and contains each of the presented (or possibly other) language tag
365 options, the noSuchAttributeType error will be returned.
367 Thus, for example, a compare request of type "name" and assertion
368 value "Johann", against an entry containing the following attributes:
372 givenName;lang-de-DE: Johann
376 would cause the server to return compareTrue.
378 However, if the client issued a compare request of type "name;lang-de"
379 and assertion value "Johann" against the above entry, the request
380 would fail with the noSuchAttributeType error.
382 If the server does not support storing attributes with language tag
383 options in the DIT, then any comparison which includes a language tag
384 option will always fail to locate an attribute, and
385 noSuchAttributeType will be returned.
390 Clients can provide language options in AttributeDescription in
394 Zeilenga Language Tags and Ranges in LDAP [Page 7]
396 INTERNET-DRAFT draft-zeilenga-ldap-rfc2596-04.txt 9 December 2002
399 attributes of a new entry to be created.
401 A client can provide multiple attributes with the same attribute type
402 and value, so long as each attribute has a different set of language
405 For example, the following is a valid request:
407 dn: CN=John Smith,DC=example,DC=com
408 objectclass: residentialPerson
410 CN;lang-en: John Smith
413 streetAddress: 1 University Street
414 streetAddress;lang-en-US: 1 University Street
415 streetAddress;lang-fr: 1 rue Universite
416 houseIdentifier;lang-fr: 9e etage
418 If a server does not support storing language tag options with
419 attribute values in the DIT, then it MUST treat an
420 AttributeDescription with a language tag option as an unrecognized
421 attribute. If the server forbids the addition of unrecognized
422 attributes then it MUST fail the add request with an appropriate
426 2.6. Modify Operation
428 A client can provide language tag options in an AttributeDescription
429 as part of a modification element in the modify operation.
431 Attribute types and language tag options MUST match exactly against
432 values stored in the directory. For example, if the modification is a
433 "delete", then if the stored values to be deleted have language tag
434 options, then those language tag options MUST be provided in the
435 modify operation, and if the stored values to be deleted do not have
436 any language tag option, then no language tag option is to be
439 If the server does not support storing language tag options with
440 attribute values in the DIT, then it MUST treat an
441 AttributeDescription with a language tag option as an unrecognized
442 attribute, and MUST fail the request with an appropriate result code.
445 3. Use of Language Ranges in LDAP
450 Zeilenga Language Tags and Ranges in LDAP [Page 8]
452 INTERNET-DRAFT draft-zeilenga-ldap-rfc2596-04.txt 9 December 2002
455 Since the publication of RFC 2596, it has become apparent that there
456 is a need to provide a mechanism for a client to request attributes
457 based upon set of language tag options whose tags all begin with the
458 same sequence of language sub-tags.
460 AttributeDescriptions containing language range options are intended
461 to be used in attribute value assertions, search attribute lists, and
462 other places where the client desires to provide an attribute
463 description matching of a range of language tags associated with
466 A language range option conforms to the following ABNF [RFC2234]:
468 language-range-option = "lang-" [ Language-Tag "-" ]
470 where the Language-Tag production is as defined in BCP 47 [RFC3066].
471 This production and those it imports from [RFC2234] are provided in
472 Section 2.1 for convenience.
474 A language range option matches a language tag option if the language
475 range option less the trailing "-" matches exactly the language tag or
476 if the language range option (including the trailing "-") matches a
477 prefix of the language tag option. Note that the language range
478 option "lang-" matches all language tag options.
480 Examples of valid AttributeDescription containing language range
485 SN;lang-de-;lang-gem-
488 A language range option is not a tagging option. Attributes cannot be
489 stored with language range options. Any attempt to add or update an
490 attribute description with a language range option SHALL be treated as
491 an undefined attribute type and result in an error.
493 A language range option has no effect on the transfer encoding nor on
494 the syntax of the attribute values.
496 Servers SHOULD support assertion of language ranges for any attribute
497 type which they allow to be stored with language tags.
502 If a language range option is present in an AttributeDescription in an
506 Zeilenga Language Tags and Ranges in LDAP [Page 9]
508 INTERNET-DRAFT draft-zeilenga-ldap-rfc2596-04.txt 9 December 2002
511 assertion, then for each entry within scope, the values of each
512 attribute whose AttributeDescription consists of the same attribute
513 type or its subtypes and contains a language tag option matching the
514 language range option are to be returned.
516 Thus, for example, a filter of an equality match of type
517 "name;lang-en-" and assertion value "Billy Ray", against the following
520 dn: SN=Ray,DC=example,DC=com
521 objectclass: person DOES NOT MATCH (wrong type)
522 objectclass: extensibleObject DOES NOT MATCH (wrong type)
523 name;lang-en-US: Billy Ray MATCHES
524 name;lang-en-US: Billy Bob DOES NOT MATCH (wrong value)
525 CN;lang-en-US: Billy Ray MATCHES
526 CN;lang-en-US;x-foobar: Billy Ray MATCHES
527 CN;lang-en;x-foobar: Billy Ray MATCHES
528 CN;x-foobar: Billy Ray DOES NOT MATCH (no lang-)
529 name: Billy Ray DOES NOT MATCH (no lang-)
530 SN;lang-en-GB;lang-en-US: Billy Ray MATCHES
531 SN: Ray DOES NOT MATCH (no lang-,
534 Note that "CN" and "SN" are subtypes of "name".
536 If the server does not support storing attributes with language tag
537 options in the DIT, then any assertion which includes a language range
538 option will not match as it is an unrecognized attribute type. No
539 error would be returned because of this; a presence filter would
540 evaluate to FALSE and all other assertions to Undefined.
543 3.2. Requested Attributes in Search
545 Clients can provide language range options in each
546 AttributeDescription in the requested attribute list in a search
549 If a language range option is provided in an attribute description,
550 then only attributes in a directory entry whose attribute descriptions
551 have the same attribute type or its subtype and a language tag option
552 matching the provided language range option are to be returned. Thus
553 if a client requests just the attribute "name;lang-en-", the server
554 would return "name;lang-en-US" and "CN;lang-en;lang-ja" but not "SN"
557 Clients can provide in the attribute list multiple
558 AttributeDescriptions which have the same base attribute type but
562 Zeilenga Language Tags and Ranges in LDAP [Page 10]
564 INTERNET-DRAFT draft-zeilenga-ldap-rfc2596-04.txt 9 December 2002
567 different options. For example a client could provide both
568 "name;lang-en-" and "name;lang-fr-", and this would permit an
569 attribute whose type was name or subtype of name and with a language
570 tag option matching either language range option to be returned.
572 If a server does not support storing attributes with language tag
573 options in the DIT, then any attribute descriptions in the list which
574 include language range options are to be ignored, just as if they were
575 unknown attribute types.
580 Language range options can be present in an AttributeDescription used
581 in a compare request AttributeValueAssertion. This is to be treated
582 by servers the same as the use of language range options in a search
583 filter with an equality match, as described in Section 3.1. If there
584 is no attribute in the entry with the same subtype and a matching
585 language tag option, the noSuchAttributeType error will be returned.
587 Thus, for example, a compare request of type "name;lang-" and
588 assertion value "Johann", against the entry with the following
593 givenName;lang-de-DE: Johann
597 will cause the server to return compareTrue. (Note that the language
598 range option "lang-" matches any language tag option.)
600 However, if the client issued a compare request of type "name;lang-de"
601 and assertion value "Sibelius" against the above entry, the request
602 would fail with the noSuchAttributeType error.
604 If the server does not support storing attributes with language tag
605 options in the DIT, then any comparison which includes a language
606 range option will always fail to locate an attribute, and
607 noSuchAttributeType will be returned.
610 4. Discovering Language Option Support
612 A server SHOULD indicate that it supports storing attributes with
613 language tag options in the DIT by publishing 1.3.6.1.4.1.4203.1.5.4
614 as a value of the "supportedFeatures" [FEATURES] attribute in the root
618 Zeilenga Language Tags and Ranges in LDAP [Page 11]
620 INTERNET-DRAFT draft-zeilenga-ldap-rfc2596-04.txt 9 December 2002
625 A server SHOULD indicate that it supports language range matching of
626 attributes with language tag options stored in the DIT by publishing
627 1.3.6.1.4.1.4203.1.5.5 as a value of the "supportedFeatures"
628 [FEATURES] attribute in the root DSE.
630 A server MAY restrict use of language tag options to a subset of the
631 attribute types it recognizes. This document does not define a
632 mechanism for determining which subset of attribute types can be used
633 with language tag options.
636 5. Security Considerations
638 Language tags and range options are used solely to indicate the native
639 language of values and in querying the directory for values which
640 fulfill the user's language needed. These options are not known to
641 raise specific security considerations. However, the reader should
642 consider general directory security issues detailed in the LDAP
643 technical specification [RFC3377].
646 6. IANA Considerations
648 The OIDs 1.3.6.1.4.1.4203.1.5.4 and 1.3.6.1.4.1.4203.1.5.5 identify
649 the features described above. These OIDs were assigned [ASSIGN] by
650 OpenLDAP Foundation, under its IANA-assigned private enterprise
651 allocation [PRIVATE], for use in this specification.
653 Registration of these protocol mechanisms [RFC3383] is requested.
655 Subject: Request for LDAP Protocol Mechanism Registration
657 Object Identifier: 1.3.6.1.4.1.4203.1.5.4
658 Description: Language Tag Options
660 Object Identifier: 1.3.6.1.4.1.4203.1.5.5
661 Description: Language Range Options
663 Person & email address to contact for further information:
664 Kurt Zeilenga <kurt@openldap.org>
668 Specification: RFCxxxx
670 Author/Change Controller: IESG
674 Zeilenga Language Tags and Ranges in LDAP [Page 12]
676 INTERNET-DRAFT draft-zeilenga-ldap-rfc2596-04.txt 9 December 2002
684 This document is a revision of RFC 2596 by Mark Wahl and Tim Howes.
685 RFC 2596 was a product of the IETF ASID and LDAPEXT working groups.
686 This document also borrows from a number of IETF documents including
687 BCP 47 by H. Alvestrand.
690 8. Normative References
692 [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate
693 Requirement Levels", BCP 14 (also RFC 2119), March 1997.
695 [RFC2234] D. Crocker, P. Overell, "Augmented BNF for Syntax
696 Specifications: ABNF", RFC 2234, November 1997.
698 [RFC2251] M. Wahl, T. Howes, S. Kille, "Lightweight Directory Access
699 Protocol (v3)", RFC 2251, December 1997.
701 [RFC3066] Alvestrand, H., "Tags for the Identification of Languages",
702 BCP 47 (also RFC 3066), January 2001.
704 [RFC3377] J. Hodges, R. Morgan, "Lightweight Directory Access
705 Protocol (v3): Technical Specification", RFC 3377,
708 [FEATURES] K. Zeilenga, "Feature Discovery in LDAP",
709 draft-zeilenga-ldap-features-xx.txt (a work in progress).
712 9. Informative References
714 [X.501] ITU, "The Directory: Models", ITU-T Recommendation X.501,
717 [RFC3383] K. Zeilenga, "IANA Considerations for LDAP", BCP 64 (also
718 RFC 3383), September 2002.
720 [ASSIGN] OpenLDAP Foundation, "OpenLDAP OID Delegations",
721 http://www.openldap.org/foundation/oid-delegate.txt.
723 [PRIVATE] IANA, "Private Enterprise Numbers",
724 http://www.iana.org/assignments/enterprise-numbers.
730 Zeilenga Language Tags and Ranges in LDAP [Page 13]
732 INTERNET-DRAFT draft-zeilenga-ldap-rfc2596-04.txt 9 December 2002
735 Appendix A. Differences from RFC 2596
737 This document adds support for language ranges, provides a mechanism
738 that a client can use to discover whether a server supports language
739 tags and ranges, and clarifies how attributes with multiple language
740 tags are to be treated. This document is a significant rewrite of RFC
744 Appendix B. Differences from X.500(1997)
746 X.500(1997) [X.501] defines a different mechanism, contexts, as the
747 means of representing language tags (codes). This section summarizes
748 the major differences in approach.
750 a) An X.500 operation which has specified a language code on a value
751 matches a value in the directory without a language code.
752 b) LDAP references BCP 47 [RFC3066], which allows for IANA
753 registration of new tags as well as unregistered tags.
754 c) LDAP supports language ranges (new in this revision).
755 d) LDAP does not allow language tags (and ranges) in distinguished
757 e) X.500 describes subschema administration procedures to allow
758 language codes to be associated with particular attributes types.
761 Copyright 2002, The Internet Society. All Rights Reserved.
763 This document and translations of it may be copied and furnished to
764 others, and derivative works that comment on or otherwise explain it
765 or assist in its implementation may be prepared, copied, published and
766 distributed, in whole or in part, without restriction of any kind,
767 provided that the above copyright notice and this paragraph are
768 included on all such copies and derivative works. However, this
769 document itself may not be modified in any way, such as by removing
770 the copyright notice or references to the Internet Society or other
771 Internet organizations, except as needed for the purpose of
772 developing Internet standards in which case the procedures for
773 copyrights defined in the Internet Standards process must be followed,
774 or as required to translate it into languages other than English.
776 The limited permissions granted above are perpetual and will not be
777 revoked by the Internet Society or its successors or assigns.
779 This document and the information contained herein is provided on an
780 "AS IS" basis and THE AUTHORS, THE INTERNET SOCIETY, AND THE INTERNET
781 ENGINEERING TASK FORCE DISCLAIMS ALL WARRANTIES, EXPRESS OR IMPLIED,
782 INCLUDING BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF THE
786 Zeilenga Language Tags and Ranges in LDAP [Page 14]
788 INTERNET-DRAFT draft-zeilenga-ldap-rfc2596-04.txt 9 December 2002
791 INFORMATION HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED
792 WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE.
842 Zeilenga Language Tags and Ranges in LDAP [Page 15]