draft-ietf-ldapbis-syntaxes-07.txt   draft-ietf-ldapbis-syntaxes-08.txt 
INTERNET-DRAFT S. Legg, Editor INTERNET-DRAFT S. Legg, Editor
draft-ietf-ldapbis-syntaxes-07.txt Adacel Technologies draft-ietf-ldapbis-syntaxes-08.txt Adacel Technologies
Intended Category: Standards Track K. Dally Intended Category: Standards Track K. Dally
Obsoletes: RFC 2252, RFC 2256 The MITRE Corp. Obsoletes: RFC 2252, RFC 2256 The MITRE Corp.
27 October 2003 21 May 2004
LDAP: Syntaxes and Matching Rules Lightweight Directory Access Protocol (LDAP):
Syntaxes and Matching Rules
Copyright (C) The Internet Society (2003). All Rights Reserved. Copyright (C) The Internet Society (2004). All Rights Reserved.
Status of this Memo Status of this Memo
This document is an Internet-Draft and is in full conformance with This document is an Internet-Draft and is in full conformance with
all provisions of Section 10 of RFC2026. all provisions of Section 10 of RFC2026.
Internet-Drafts are working documents of the Internet Engineering Internet-Drafts are working documents of the Internet Engineering
Task Force (IETF), its areas, and its working groups. Note that Task Force (IETF), its areas, and its working groups. Note that
other groups may also distribute working documents as other groups may also distribute working documents as
Internet-Drafts. Internet-Drafts.
skipping to change at page 1, line 42 skipping to change at page 1, line 43
http://www.ietf.org/shadow.html. http://www.ietf.org/shadow.html.
This document is intended to be, after appropriate review and This document is intended to be, after appropriate review and
revision, submitted to the RFC Editor as a Standard Track document. revision, submitted to the RFC Editor as a Standard Track document.
Distribution of this document is unlimited. Technical discussion of Distribution of this document is unlimited. Technical discussion of
this document should take place on the IETF LDAP Revision Working this document should take place on the IETF LDAP Revision Working
Group (LDAPbis) mailing list <ietf-ldapbis@openldap.org>. Please Group (LDAPbis) mailing list <ietf-ldapbis@openldap.org>. Please
send editorial comments directly to the editor send editorial comments directly to the editor
<steven.legg@adacel.com.au>. <steven.legg@adacel.com.au>.
This Internet-Draft expires on 27 April 2004. This Internet-Draft expires on 21 November 2004.
Abstract Abstract
Each attribute stored in a Lightweight Directory Access Protocol Each attribute stored in a Lightweight Directory Access Protocol
(LDAP) directory, and whose values may be transfered in the LDAP (LDAP) directory, and whose values may be transfered in the LDAP
protocol, has a defined syntax which constrains the structure and protocol, has a defined syntax which constrains the structure and
format of its values. The comparison semantics for values of a format of its values. The comparison semantics for values of a
syntax are not part of the syntax definition but are instead provided syntax are not part of the syntax definition but are instead provided
through separately defined matching rules. Matching rules specify an through separately defined matching rules. Matching rules specify an
argument, an assertion value, which also has a defined syntax. This argument, an assertion value, which also has a defined syntax. This
skipping to change at page 3, line 33 skipping to change at page 3, line 33
3.3.11. Facsimile Telephone Number . . . . . . . . . . . 13 3.3.11. Facsimile Telephone Number . . . . . . . . . . . 13
3.3.12. Fax. . . . . . . . . . . . . . . . . . . . . . . 13 3.3.12. Fax. . . . . . . . . . . . . . . . . . . . . . . 13
3.3.13. Generalized Time . . . . . . . . . . . . . . . . 14 3.3.13. Generalized Time . . . . . . . . . . . . . . . . 14
3.3.14. Guide. . . . . . . . . . . . . . . . . . . . . . 15 3.3.14. Guide. . . . . . . . . . . . . . . . . . . . . . 15
3.3.15. IA5 String . . . . . . . . . . . . . . . . . . . 15 3.3.15. IA5 String . . . . . . . . . . . . . . . . . . . 15
3.3.16. Integer. . . . . . . . . . . . . . . . . . . . . 15 3.3.16. Integer. . . . . . . . . . . . . . . . . . . . . 15
3.3.17. JPEG . . . . . . . . . . . . . . . . . . . . . . 16 3.3.17. JPEG . . . . . . . . . . . . . . . . . . . . . . 16
3.3.18. LDAP Syntax Description. . . . . . . . . . . . . 16 3.3.18. LDAP Syntax Description. . . . . . . . . . . . . 16
3.3.19. Matching Rule Description. . . . . . . . . . . . 17 3.3.19. Matching Rule Description. . . . . . . . . . . . 17
3.3.20. Matching Rule Use Description. . . . . . . . . . 17 3.3.20. Matching Rule Use Description. . . . . . . . . . 17
3.3.21. Name and Optional UID. . . . . . . . . . . . . . 18 3.3.21. Name and Optional UID. . . . . . . . . . . . . . 17
3.3.22. Name Form Description. . . . . . . . . . . . . . 18 3.3.22. Name Form Description. . . . . . . . . . . . . . 18
3.3.23. Numeric String . . . . . . . . . . . . . . . . . 19 3.3.23. Numeric String . . . . . . . . . . . . . . . . . 18
3.3.24. Object Class Description . . . . . . . . . . . . 19 3.3.24. Object Class Description . . . . . . . . . . . . 19
3.3.25. Octet String . . . . . . . . . . . . . . . . . . 19 3.3.25. Octet String . . . . . . . . . . . . . . . . . . 19
3.3.26. OID. . . . . . . . . . . . . . . . . . . . . . . 20 3.3.26. OID. . . . . . . . . . . . . . . . . . . . . . . 20
3.3.27. Other Mailbox. . . . . . . . . . . . . . . . . . 20 3.3.27. Other Mailbox. . . . . . . . . . . . . . . . . . 20
3.3.28. Postal Address . . . . . . . . . . . . . . . . . 21 3.3.28. Postal Address . . . . . . . . . . . . . . . . . 21
3.3.29. Printable String . . . . . . . . . . . . . . . . 22 3.3.29. Printable String . . . . . . . . . . . . . . . . 22
3.3.30. Substring Assertion. . . . . . . . . . . . . . . 22 3.3.30. Substring Assertion. . . . . . . . . . . . . . . 22
3.3.31. Telephone Number . . . . . . . . . . . . . . . . 23 3.3.31. Telephone Number . . . . . . . . . . . . . . . . 23
3.3.32. Teletex Terminal Identifier. . . . . . . . . . . 24 3.3.32. Teletex Terminal Identifier. . . . . . . . . . . 23
3.3.33. Telex Number . . . . . . . . . . . . . . . . . . 24 3.3.33. Telex Number . . . . . . . . . . . . . . . . . . 24
3.3.34. UTC Time . . . . . . . . . . . . . . . . . . . . 25 3.3.34. UTC Time . . . . . . . . . . . . . . . . . . . . 25
4. Matching Rules . . . . . . . . . . . . . . . . . . . . . . . . 25 4. Matching Rules . . . . . . . . . . . . . . . . . . . . . . . . 25
4.1. General Considerations . . . . . . . . . . . . . . . . . 26 4.1. General Considerations . . . . . . . . . . . . . . . . . 26
4.2. Matching Rule Definitions. . . . . . . . . . . . . . . . 27 4.2. Matching Rule Definitions. . . . . . . . . . . . . . . . 27
4.2.1. bitStringMatch . . . . . . . . . . . . . . . . . 27 4.2.1. bitStringMatch . . . . . . . . . . . . . . . . . 27
4.2.2. caseExactIA5Match. . . . . . . . . . . . . . . . 28 4.2.2. caseExactIA5Match. . . . . . . . . . . . . . . . 28
4.2.3. caseIgnoreIA5Match . . . . . . . . . . . . . . . 28 4.2.3. caseIgnoreIA5Match . . . . . . . . . . . . . . . 28
4.2.4. caseIgnoreIA5SubstringsMatch . . . . . . . . . . 29 4.2.4. caseIgnoreIA5SubstringsMatch . . . . . . . . . . 29
4.2.5. caseIgnoreListMatch. . . . . . . . . . . . . . . 29 4.2.5. caseIgnoreListMatch. . . . . . . . . . . . . . . 29
4.2.6. caseIgnoreListSubstringsMatch. . . . . . . . . . 30 4.2.6. caseIgnoreListSubstringsMatch. . . . . . . . . . 30
4.2.7. caseIgnoreMatch. . . . . . . . . . . . . . . . . 31 4.2.7. caseIgnoreMatch. . . . . . . . . . . . . . . . . 30
4.2.8. caseIgnoreOrderingMatch. . . . . . . . . . . . . 31 4.2.8. caseIgnoreOrderingMatch. . . . . . . . . . . . . 31
4.2.9. caseIgnoreSubstringsMatch. . . . . . . . . . . . 32 4.2.9. caseIgnoreSubstringsMatch. . . . . . . . . . . . 31
4.2.10. distinguishedNameMatch . . . . . . . . . . . . . 32 4.2.10. distinguishedNameMatch . . . . . . . . . . . . . 32
4.2.11. generalizedTimeMatch . . . . . . . . . . . . . . 33 4.2.11. generalizedTimeMatch . . . . . . . . . . . . . . 33
4.2.12. generalizedTimeOrderingMatch . . . . . . . . . . 33 4.2.12. generalizedTimeOrderingMatch . . . . . . . . . . 33
4.2.13. integerFirstComponentMatch . . . . . . . . . . . 34 4.2.13. integerFirstComponentMatch . . . . . . . . . . . 33
4.2.14. integerMatch . . . . . . . . . . . . . . . . . . 34 4.2.14. integerMatch . . . . . . . . . . . . . . . . . . 34
4.2.15. numericStringMatch . . . . . . . . . . . . . . . 35 4.2.15. numericStringMatch . . . . . . . . . . . . . . . 34
4.2.16. numericStringSubstringsMatch . . . . . . . . . . 35 4.2.16. numericStringSubstringsMatch . . . . . . . . . . 35
4.2.17. objectIdentifierFirstComponentMatch. . . . . . . 36 4.2.17. objectIdentifierFirstComponentMatch. . . . . . . 35
4.2.18. objectIdentifierMatch. . . . . . . . . . . . . . 36 4.2.18. objectIdentifierMatch. . . . . . . . . . . . . . 36
4.2.19. octetStringMatch . . . . . . . . . . . . . . . . 37 4.2.19. octetStringMatch . . . . . . . . . . . . . . . . 37
4.2.20. telephoneNumberMatch . . . . . . . . . . . . . . 37 4.2.20. telephoneNumberMatch . . . . . . . . . . . . . . 37
4.2.21. telephoneNumberSubstringsMatch . . . . . . . . . 38 4.2.21. telephoneNumberSubstringsMatch . . . . . . . . . 37
4.2.22. uniqueMemberMatch. . . . . . . . . . . . . . . . 38 4.2.22. uniqueMemberMatch. . . . . . . . . . . . . . . . 38
5. Security Considerations. . . . . . . . . . . . . . . . . . . . 39 5. Security Considerations. . . . . . . . . . . . . . . . . . . . 38
6. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . . 39 6. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . . 39
7. IANA Considerations. . . . . . . . . . . . . . . . . . . . . . 39 7. IANA Considerations. . . . . . . . . . . . . . . . . . . . . . 39
8. References . . . . . . . . . . . . . . . . . . . . . . . . . . 41 Appendix A. Summary of Syntax Object Identifiers . . . . . . . . . 41
8.1. Normative References . . . . . . . . . . . . . . . . . . 41 Appendix B. Changes from RFC 2252 & RFC 2256 . . . . . . . . . . . 42
8.2. Informative References . . . . . . . . . . . . . . . . . 42 Normative References . . . . . . . . . . . . . . . . . . . . . . . 44
9. Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . 43 Informative References . . . . . . . . . . . . . . . . . . . . . . 46
10. Intellectual Property Notice . . . . . . . . . . . . . . . . . 44 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . . 46
Appendix A. Summary of Syntax Object Identifiers . . . . . . . . . 44
Appendix B. Changes from RFC 2252 & RFC 2256 . . . . . . . . . . . 45
Full Copyright Statement . . . . . . . . . . . . . . . . . . . . . 47 Full Copyright Statement . . . . . . . . . . . . . . . . . . . . . 47
1. Introduction 1. Introduction
Each attribute stored in a Lightweight Directory Access Protocol Each attribute stored in a Lightweight Directory Access Protocol
(LDAP) directory [ROADMAP], and whose values may be transfered in the (LDAP) directory [ROADMAP], and whose values may be transfered in the
LDAP protocol [PROT], has a defined syntax (i.e., data type) which LDAP protocol [PROT], has a defined syntax (i.e., data type) which
constrains the structure and format of its values. The comparison constrains the structure and format of its values. The comparison
semantics for values of a syntax are not part of the syntax semantics for values of a syntax are not part of the syntax
definition but are instead provided through separately defined definition but are instead provided through separately defined
skipping to change at page 41, line 19 skipping to change at page 41, line 10
Subject: Request for LDAP Descriptor Registration Subject: Request for LDAP Descriptor Registration
Descriptor (short name): caseIgnoreListSubstringsMatch Descriptor (short name): caseIgnoreListSubstringsMatch
Object Identifier: 2.5.13.12 Object Identifier: 2.5.13.12
Person & email address to contact for further information: Person & email address to contact for further information:
Steven Legg <steven.legg@adacel.com.au> Steven Legg <steven.legg@adacel.com.au>
Usage: other (M) Usage: other (M)
Specification: RFC XXXX Specification: RFC XXXX
Author/Change Controller: IESG Author/Change Controller: IESG
8. References
8.1. Normative References
[KEYWORD] Bradner, S., "Key words for use in RFCs to Indicate
Requirement Levels", BCP 14, RFC 2119, March 1997.
[ABNF] Crocker, D. and P. Overell, "Augmented BNF for Syntax
Specifications: ABNF", RFC 2234, November 1997.
[UTF8] Yergeau, F., "UTF-8, a transformation format of ISO
10646", draft-yergeau-rfc2279bis-xx.txt, a work in
progress, June 2003.
[BCP64] Zeilenga, K., "Internet Assigned Numbers Authority (IANA)
Considerations for the Lightweight Directory Access
Protocol (LDAP)", BCP 64, RFC 3383, September 2002.
[LDAPDN] Zeilenga, K., "LDAP: String Representation of
Distinguished Names", draft-ietf-ldapbis-dn-xx.txt, a work
in progress, June 2003.
[PROT] Sermersheim, J., "LDAP: The Protocol", draft-ietf-ldapbis-
protocol-xx.txt, a work in progress, September 2003.
[E.123] Notation for national and international telephone numbers,
ITU-T Recommendation E.123, 1988.
[FAX] Standardization of Group 3 facsimile apparatus for
document transmission - Terminal Equipment and Protocols
for Telematic Services, ITU-T Recommendation T.4, 1993
[T.50] International Reference Alphabet (IRA) (Formerly
International Alphabet No. 5 or IA5) Information
Technology - 7-Bit Coded Character Set for Information
Interchange, ITU-T Recommendation T.50, 1992
[X.420] ITU-T Recommendation X.420 (1996) | ISO/IEC 10021-7:1997,
Information Technology - Message Handling Systems (MHS):
Interpersonal messaging system
[X.501] ITU-T Recommendation X.501 (1993) | ISO/IEC 9594-2:1994,
Information Technology - Open Systems Interconnection -
The Directory: Models
[X.520] ITU-T Recommendation X.520 (1993) | ISO/IEC 9594-6:1994,
Information Technology - Open Systems Interconnection -
The Directory: Selected attribute types
[ASN.1] ITU-T Recommendation X.680 (07/02) | ISO/IEC 8824-1:2002,
Information technology - Abstract Syntax Notation One
(ASN.1): Specification of basic notation
[ISO3166] ISO 3166, "Codes for the representation of names of
countries".
[UCS] Universal Multiple-Octet Coded Character Set (UCS) -
Architecture and Basic Multilingual Plane, ISO/IEC
10646-1: 1993 (with amendments).
[JPEG] JPEG File Interchange Format (Version 1.02). Eric
Hamilton, C-Cube Microsystems, Milpitas, CA, September 1,
1992.
[ROADMAP] Zeilenga, K., "LDAP: Technical Specification Road Map",
draft-ietf-ldapbis-roadmap-xx.txt, a work in progress,
June 2003.
[MODELS] Zeilenga, K., "LDAP: Directory Information Models", draft-
ietf-ldapbis-models-xx.txt, a work in progress, June 2003.
[PREP] Zeilenga, K., "LDAP: Internationalized String
Preparation", draft-ietf-ldapbis-strprep-xx.txt, a work in
progress, June 2003.
8.2. Informative References
[RFC2252] Wahl, M., Coulbeck, A., Howes, T. and S. Kille,
"Lightweight Directory Access Protocol (v3): Attribute
Syntax Definitions", RFC 2252, December 1997.
[RFC2256] Wahl, M., "A Summary of the X.500(96) User Schema for use
with LDAPv3", RFC 2256, December 1997.
[RFC3377] Hodges, J. and R. Morgan, "Lightweight Directory Access
Protocol (v3): Technical Specification", RFC 3377,
September 2002.
[SCHEMA] Dally, K., "LDAP: Schema for User Applications", draft-
ietf-ldapbis-user-schema-xx.txt, a work in progress, June
2003.
[LDAP-PKI] Chadwick, D. W. and S. Legg, "LDAP Schema and Syntaxes for
PKIs", draft-ietf-pkix-ldap-pki-schema-xx.txt, a work in
progress, July 2002.
[X.500] ITU-T Recommendation X.500 (1993) | ISO/IEC 9594-1:1994,
Information Technology - Open Systems Interconnection -
The Directory: Overview of concepts, models and services
[BER] ITU-T Recommendation X.690 (07/02) | ISO/IEC 8825-1:2002,
Information technology - ASN.1 encoding rules:
Specification of Basic Encoding Rules (BER), Canonical
Encoding Rules (CER) and Distinguished Encoding Rules
(DER)
9. Authors' Addresses
Steven Legg
Adacel Technologies Ltd.
250 Bay Street
Brighton, Victoria 3186
AUSTRALIA
Phone: +61 3 8530 7710
Fax: +61 3 8530 7888
Email: steven.legg@adacel.com.au
Kathy Dally
The MITRE Corp.
7515 Colshire Dr., ms-W650
McLean VA 22102
USA
Phone: +1 703 883 6058
Fax: +1 703 883 7142
Email: kdally@mitre.org
10. Intellectual Property Notice
The IETF takes no position regarding the validity or scope of any
intellectual property or other rights that might be claimed to
pertain to the implementation or use of the technology described in
this document or the extent to which any license under such rights
might or might not be available; neither does it represent that it
has made any effort to identify any such rights. Information on the
IETF's procedures with respect to rights in standards-track and
standards-related documentation can be found in BCP-11. Copies of
claims of rights made available for publication and any assurances of
licenses to be made available, or the result of an attempt made to
obtain a general license or permission for the use of such
proprietary rights by implementors or users of this specification can
be obtained from the IETF Secretariat.
The IETF invites any interested party to bring to its attention any
copyrights, patents or patent applications, or other proprietary
rights which may cover technology that may be required to practice
this standard. Please address the information to the IETF Executive
Director.
Appendix A. Summary of Syntax Object Identifiers Appendix A. Summary of Syntax Object Identifiers
The following list summarizes the object identifiers assigned to the The following list summarizes the object identifiers assigned to the
syntaxes defined in this document. syntaxes defined in this document.
Syntax OBJECT IDENTIFIER Syntax OBJECT IDENTIFIER
============================================================== ==============================================================
Attribute Type Description 1.3.6.1.4.1.1466.115.121.1.3 Attribute Type Description 1.3.6.1.4.1.1466.115.121.1.3
Bit String 1.3.6.1.4.1.1466.115.121.1.6 Bit String 1.3.6.1.4.1.1466.115.121.1.6
Boolean 1.3.6.1.4.1.1466.115.121.1.7 Boolean 1.3.6.1.4.1.1466.115.121.1.7
skipping to change at page 47, line 51 skipping to change at page 44, line 36
29. The definitive reference for ASN.1 has been changed from X.208 to 29. The definitive reference for ASN.1 has been changed from X.208 to
X.680 since X.680 is the version of ASN.1 referred to by X.500. X.680 since X.680 is the version of ASN.1 referred to by X.500.
30. The specification of the caseIgnoreListSubstringsMatch matching 30. The specification of the caseIgnoreListSubstringsMatch matching
rule from RFC 2798 & X.520 has been added to this document. rule from RFC 2798 & X.520 has been added to this document.
31. String preparation algorithms have been applied to the character 31. String preparation algorithms have been applied to the character
string matching rules. string matching rules.
Normative References
[KEYWORD] Bradner, S., "Key words for use in RFCs to Indicate
Requirement Levels", BCP 14, RFC 2119, March 1997.
[ABNF] Crocker, D. and P. Overell, "Augmented BNF for Syntax
Specifications: ABNF", RFC 2234, November 1997.
[UTF8] Yergeau, F., "UTF-8, a transformation format of ISO
10646", RFC 3629, November 2003.
[BCP64] Zeilenga, K., "Internet Assigned Numbers Authority (IANA)
Considerations for the Lightweight Directory Access
Protocol (LDAP)", BCP 64, RFC 3383, September 2002.
[LDAPDN] Zeilenga, K., "LDAP: String Representation of
Distinguished Names", draft-ietf-ldapbis-dn-xx.txt, a work
in progress, February 2004.
[PROT] Sermersheim, J., "LDAP: The Protocol", draft-ietf-ldapbis-
protocol-xx.txt, a work in progress, May 2004.
[E.123] Notation for national and international telephone numbers,
ITU-T Recommendation E.123, 1988.
[FAX] Standardization of Group 3 facsimile apparatus for
document transmission - Terminal Equipment and Protocols
for Telematic Services, ITU-T Recommendation T.4, 1993
[T.50] International Reference Alphabet (IRA) (Formerly
International Alphabet No. 5 or IA5) Information
Technology - 7-Bit Coded Character Set for Information
Interchange, ITU-T Recommendation T.50, 1992
[X.420] ITU-T Recommendation X.420 (1996) | ISO/IEC 10021-7:1997,
Information Technology - Message Handling Systems (MHS):
Interpersonal messaging system
[X.501] ITU-T Recommendation X.501 (1993) | ISO/IEC 9594-2:1994,
Information Technology - Open Systems Interconnection -
The Directory: Models
[X.520] ITU-T Recommendation X.520 (1993) | ISO/IEC 9594-6:1994,
Information Technology - Open Systems Interconnection -
The Directory: Selected attribute types
[ASN.1] ITU-T Recommendation X.680 (07/02) | ISO/IEC 8824-1:2002,
Information technology - Abstract Syntax Notation One
(ASN.1): Specification of basic notation
[ISO3166] ISO 3166, "Codes for the representation of names of
countries".
[UCS] Universal Multiple-Octet Coded Character Set (UCS) -
Architecture and Basic Multilingual Plane, ISO/IEC
10646-1: 1993 (with amendments).
[JPEG] JPEG File Interchange Format (Version 1.02). Eric
Hamilton, C-Cube Microsystems, Milpitas, CA, September 1,
1992.
[ROADMAP] Zeilenga, K., "Lightweight Directory Access Protocol
(LDAP): Technical Specification Road Map", draft-ietf-
ldapbis-roadmap-xx.txt, a work in progress, February 2004.
[MODELS] Zeilenga, K., "LDAP: Directory Information Models", draft-
ietf-ldapbis-models-xx.txt, a work in progress, February
2004.
[PREP] Zeilenga, K., "LDAP: Internationalized String
Preparation", draft-ietf-ldapbis-strprep-xx.txt, a work in
progress, February 2004.
Informative References
[RFC2252] Wahl, M., Coulbeck, A., Howes, T. and S. Kille,
"Lightweight Directory Access Protocol (v3): Attribute
Syntax Definitions", RFC 2252, December 1997.
[RFC2256] Wahl, M., "A Summary of the X.500(96) User Schema for use
with LDAPv3", RFC 2256, December 1997.
[RFC3377] Hodges, J. and R. Morgan, "Lightweight Directory Access
Protocol (v3): Technical Specification", RFC 3377,
September 2002.
[SCHEMA] Dally, K., "LDAP: Schema for User Applications", draft-
ietf-ldapbis-user-schema-xx.txt, a work in progress, June
2003.
[LDAP-PKI] Chadwick, D. W. and S. Legg, "LDAP Schema and Syntaxes for
PKIs", draft-ietf-pkix-ldap-pki-schema-xx.txt, a work in
progress, July 2002.
[X.500] ITU-T Recommendation X.500 (1993) | ISO/IEC 9594-1:1994,
Information Technology - Open Systems Interconnection -
The Directory: Overview of concepts, models and services
[BER] ITU-T Recommendation X.690 (07/02) | ISO/IEC 8825-1:2002,
Information technology - ASN.1 encoding rules:
Specification of Basic Encoding Rules (BER), Canonical
Encoding Rules (CER) and Distinguished Encoding Rules
(DER)
Authors' Addresses
Steven Legg
Adacel Technologies Ltd.
250 Bay Street
Brighton, Victoria 3186
AUSTRALIA
Phone: +61 3 8530 7710
Fax: +61 3 8530 7888
Email: steven.legg@adacel.com.au
Kathy Dally
The MITRE Corp.
7515 Colshire Dr., ms-W650
McLean VA 22102
USA
Phone: +1 703 883 6058
Fax: +1 703 883 7142
Email: kdally@mitre.org
Full Copyright Statement Full Copyright Statement
Copyright (C) The Internet Society (2003). All Rights Reserved.
This document and translations of it may be copied and furnished to Copyright (C) The Internet Society (2004). This document is subject
others, and derivative works that comment on or otherwise explain it to the rights, licenses and restrictions contained in BCP 78, and
or assist in its implementation may be prepared, copied, published except as set forth therein, the authors retain all their rights.
and distributed, in whole or in part, without restriction of any
kind, provided that the above copyright notice and this paragraph are
included on all such copies and derivative works. However, this
document itself may not be modified in any way, such as by removing
the copyright notice or references to the Internet Society or other
Internet organizations, except as needed for the purpose of
developing Internet standards in which case the procedures for
copyrights defined in the Internet Standards process must be
followed, or as required to translate it into languages other than
English.
The limited permissions granted above are perpetual and will not be This document and the information contained herein are provided on an
revoked by the Internet Society or its successors or assignees. "AS IS" basis and THE CONTRIBUTOR, THE ORGANIZATION HE/SHE REPRESENTS
OR IS SPONSORED BY (IF ANY), THE INTERNET SOCIETY AND THE INTERNET
ENGINEERING TASK FORCE DISCLAIM ALL WARRANTIES, EXPRESS OR IMPLIED,
INCLUDING BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF THE
INFORMATION HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED
WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE.
This document and the information contained herein is provided on an Intellectual Property
"AS IS" basis and THE INTERNET SOCIETY AND THE INTERNET ENGINEERING
TASK FORCE DISCLAIMS ALL WARRANTIES, EXPRESS OR IMPLIED, INCLUDING The IETF takes no position regarding the validity or scope of any
BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF THE INFORMATION Intellectual Property Rights or other rights that might be claimed to
HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED WARRANTIES OF pertain to the implementation or use of the technology described in
MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE. this document or the extent to which any license under such rights
might or might not be available; nor does it represent that it has
made any independent effort to identify any such rights. Information
on the procedures with respect to rights in RFC documents can be
found in BCP 78 and BCP 79.
Copies of IPR disclosures made to the IETF Secretariat and any
assurances of licenses to be made available, or the result of an
attempt made to obtain a general license or permission for the use of
such proprietary rights by implementers or users of this
specification can be obtained from the IETF on-line IPR repository at
http://www.ietf.org/ipr.
The IETF invites any interested party to bring to its attention any
copyrights, patents or patent applications, or other proprietary
rights that may cover technology that may be required to implement
this standard. Please address the information to the IETF at
ietf-ipr@ietf.org.
 End of changes. 

This html diff was produced by rfcdiff 1.23, available from http://www.levkowetz.com/ietf/tools/rfcdiff/