< draft-ietf-ldapbis-syntaxes-10.txt		draft-ietf-ldapbis-syntaxes-11.txt >
	INTERNET-DRAFT S. Legg, Editor		INTERNET-DRAFT S. Legg
	draft-ietf-ldapbis-syntaxes-10.txt eB2Bcom		draft-ietf-ldapbis-syntaxes-11.txt eB2Bcom
	Intended Category: Standards Track K. Dally		Intended Category: Standards Track 23 June 2005
	Obsoletes: RFC 2252, RFC 2256 The MITRE Corp.		Obsoletes: RFC 2252, RFC 2256 Updates: RFC 3698
	Updates: RFC 3698 18 February 2005
	Lightweight Directory Access Protocol (LDAP):		Lightweight Directory Access Protocol (LDAP):
	Syntaxes and Matching Rules		Syntaxes and Matching Rules
	Copyright (C) The Internet Society (2005). All Rights Reserved.		Copyright (C) The Internet Society (2005). All Rights Reserved.
	Status of this Memo		Status of this Memo
	By submitting this Internet-draft, we certify that any applicable		By submitting this Internet-draft, each author represents that any
	patent or other IPR claims of which we are aware have been disclosed,		applicable patent or other IPR claims of which he or she is aware
	or will be disclosed, and any of which we become aware will be		have been or will be disclosed, and any of which he or she becomes
	disclosed, in accordance with RFC 3668.		aware will be disclosed, in accordance with Section 6 of BCP 79.
	By submitting this Internet-draft, we accept the provisions of		By submitting this Internet-draft, I accept the provisions of Section
	Section 3 of RFC 3667.		3 of BCP 78.
	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.
	Internet-Drafts are draft documents valid for a maximum of six months		Internet-Drafts are draft documents valid for a maximum of six months
	and may be updated, replaced, or obsoleted by other documents at any		and may be updated, replaced, or obsoleted by other documents at any
	time. It is inappropriate to use Internet-Drafts as reference		time. It is inappropriate to use Internet-Drafts as reference
	material or to cite them other than as "work in progress".		material or to cite them other than as "work in progress".
	The list of current Internet-Drafts can be accessed at		The list of current Internet-Drafts can be accessed at
	http://www.ietf.org/ietf/1id-abstracts.txt		http://www.ietf.org/1id-abstracts.html
	The list of Internet-Draft Shadow Directories can be accessed at		The list of Internet-Draft Shadow Directories can be accessed at
	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@eb2bcom.com>.		<steven.legg@eb2bcom.com>.
	This Internet-Draft expires on 18 August 2005.		This Internet-Draft expires on 23 December 2005.
	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
	document defines a base set of syntaxes and matching rules for use in		document defines a base set of syntaxes and matching rules for use in
	defining attributes for LDAP directories.		defining attributes for LDAP directories.
	skipping to change at page 3, line 42 ¶		skipping to change at page 3, line 42 ¶
	3.3.20. Matching Rule Use Description. . . . . . . . . . 18		3.3.20. Matching Rule Use Description. . . . . . . . . . 18
	3.3.21. Name and Optional UID. . . . . . . . . . . . . . 18		3.3.21. Name and Optional UID. . . . . . . . . . . . . . 18
	3.3.22. Name Form Description. . . . . . . . . . . . . . 19		3.3.22. Name Form Description. . . . . . . . . . . . . . 19
	3.3.23. Numeric String . . . . . . . . . . . . . . . . . 19		3.3.23. Numeric String . . . . . . . . . . . . . . . . . 19
	3.3.24. Object Class Description . . . . . . . . . . . . 19		3.3.24. Object Class Description . . . . . . . . . . . . 19
	3.3.25. Octet String . . . . . . . . . . . . . . . . . . 20		3.3.25. Octet String . . . . . . . . . . . . . . . . . . 20
	3.3.26. OID. . . . . . . . . . . . . . . . . . . . . . . 20		3.3.26. OID. . . . . . . . . . . . . . . . . . . . . . . 20
	3.3.27. Other Mailbox. . . . . . . . . . . . . . . . . . 21		3.3.27. Other Mailbox. . . . . . . . . . . . . . . . . . 21
	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. . . . . . . . . . . . . . . 23
	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. . . . . . . . . . . 24
	3.3.33. Telex Number . . . . . . . . . . . . . . . . . . 25		3.3.33. Telex Number . . . . . . . . . . . . . . . . . . 25
	3.3.34. UTC Time . . . . . . . . . . . . . . . . . . . . 25		3.3.34. UTC Time . . . . . . . . . . . . . . . . . . . . 25
	4. Matching Rules . . . . . . . . . . . . . . . . . . . . . . . . 26		4. Matching Rules . . . . . . . . . . . . . . . . . . . . . . . . 26
	4.1. General Considerations . . . . . . . . . . . . . . . . . 26		4.1. General Considerations . . . . . . . . . . . . . . . . . 26
	4.2. Matching Rule Definitions. . . . . . . . . . . . . . . . 28		4.2. Matching Rule Definitions. . . . . . . . . . . . . . . . 28
	4.2.1. bitStringMatch . . . . . . . . . . . . . . . . . 28		4.2.1. bitStringMatch . . . . . . . . . . . . . . . . . 28
	4.2.2. booleanMatch . . . . . . . . . . . . . . . . . . 29		4.2.2. booleanMatch . . . . . . . . . . . . . . . . . . 29
	4.2.3. caseExactIA5Match. . . . . . . . . . . . . . . . 29		4.2.3. caseExactIA5Match. . . . . . . . . . . . . . . . 29
	4.2.4. caseExactMatch . . . . . . . . . . . . . . . . . 29		4.2.4. caseExactMatch . . . . . . . . . . . . . . . . . 30
	4.2.5. caseExactOrderingMatch . . . . . . . . . . . . . 30		4.2.5. caseExactOrderingMatch . . . . . . . . . . . . . 30
	4.2.6. caseExactSubstringsMatch . . . . . . . . . . . . 30		4.2.6. caseExactSubstringsMatch . . . . . . . . . . . . 31
	4.2.7. caseIgnoreIA5Match . . . . . . . . . . . . . . . 31		4.2.7. caseIgnoreIA5Match . . . . . . . . . . . . . . . 31
	4.2.8. caseIgnoreIA5SubstringsMatch . . . . . . . . . . 32		4.2.8. caseIgnoreIA5SubstringsMatch . . . . . . . . . . 32
	4.2.9. caseIgnoreListMatch. . . . . . . . . . . . . . . 32		4.2.9. caseIgnoreListMatch. . . . . . . . . . . . . . . 32
	4.2.10. caseIgnoreListSubstringsMatch. . . . . . . . . . 33		4.2.10. caseIgnoreListSubstringsMatch. . . . . . . . . . 33
	4.2.11. caseIgnoreMatch. . . . . . . . . . . . . . . . . 33		4.2.11. caseIgnoreMatch. . . . . . . . . . . . . . . . . 33
	4.2.12. caseIgnoreOrderingMatch. . . . . . . . . . . . . 34		4.2.12. caseIgnoreOrderingMatch. . . . . . . . . . . . . 34
	4.2.13. caseIgnoreSubstringsMatch. . . . . . . . . . . . 34		4.2.13. caseIgnoreSubstringsMatch. . . . . . . . . . . . 34
	4.2.14. directoryStringFirstComponentMatch . . . . . . . 35		4.2.14. directoryStringFirstComponentMatch . . . . . . . 35
	4.2.15. distinguishedNameMatch . . . . . . . . . . . . . 35		4.2.15. distinguishedNameMatch . . . . . . . . . . . . . 36
	4.2.16. generalizedTimeMatch . . . . . . . . . . . . . . 36		4.2.16. generalizedTimeMatch . . . . . . . . . . . . . . 36
	4.2.17. generalizedTimeOrderingMatch . . . . . . . . . . 36		4.2.17. generalizedTimeOrderingMatch . . . . . . . . . . 37
	4.2.18. integerFirstComponentMatch . . . . . . . . . . . 37		4.2.18. integerFirstComponentMatch . . . . . . . . . . . 37
	4.2.19. integerMatch . . . . . . . . . . . . . . . . . . 37		4.2.19. integerMatch . . . . . . . . . . . . . . . . . . 38
	4.2.20. integerOrderingMatch . . . . . . . . . . . . . . 38		4.2.20. integerOrderingMatch . . . . . . . . . . . . . . 38
	4.2.21. keywordMatch . . . . . . . . . . . . . . . . . . 38		4.2.21. keywordMatch . . . . . . . . . . . . . . . . . . 38
	4.2.22. numericStringMatch . . . . . . . . . . . . . . . 38		4.2.22. numericStringMatch . . . . . . . . . . . . . . . 39
	4.2.23. numericStringOrderingMatch . . . . . . . . . . . 39		4.2.23. numericStringOrderingMatch . . . . . . . . . . . 39
	4.2.24. numericStringSubstringsMatch . . . . . . . . . . 40		4.2.24. numericStringSubstringsMatch . . . . . . . . . . 40
	4.2.25. objectIdentifierFirstComponentMatch. . . . . . . 40		4.2.25. objectIdentifierFirstComponentMatch. . . . . . . 40
	4.2.26. objectIdentifierMatch. . . . . . . . . . . . . . 41		4.2.26. objectIdentifierMatch. . . . . . . . . . . . . . 41
	4.2.27. octetStringMatch . . . . . . . . . . . . . . . . 41		4.2.27. octetStringMatch . . . . . . . . . . . . . . . . 41
	4.2.28. octetStringOrderingMatch . . . . . . . . . . . . 42		4.2.28. octetStringOrderingMatch . . . . . . . . . . . . 42
	4.2.29. telephoneNumberMatch . . . . . . . . . . . . . . 42		4.2.29. telephoneNumberMatch . . . . . . . . . . . . . . 42
	4.2.30. telephoneNumberSubstringsMatch . . . . . . . . . 43		4.2.30. telephoneNumberSubstringsMatch . . . . . . . . . 43
	4.2.31. uniqueMemberMatch. . . . . . . . . . . . . . . . 43		4.2.31. uniqueMemberMatch. . . . . . . . . . . . . . . . 44
	4.2.32. wordMatch. . . . . . . . . . . . . . . . . . . . 44		4.2.32. wordMatch. . . . . . . . . . . . . . . . . . . . 44
	5. Security Considerations. . . . . . . . . . . . . . . . . . . . 44		5. Security Considerations. . . . . . . . . . . . . . . . . . . . 44
	6. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . . 45		6. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . . 45
	7. IANA Considerations. . . . . . . . . . . . . . . . . . . . . . 45		7. IANA Considerations. . . . . . . . . . . . . . . . . . . . . . 45
	Appendix A. Summary of Syntax Object Identifiers . . . . . . . . . 46		Appendix A. Summary of Syntax Object Identifiers . . . . . . . . . 47
	Appendix B. Changes from RFC 2252. . . . . . . . . . . . . . . . . 47		Appendix B. Changes from RFC 2252. . . . . . . . . . . . . . . . . 48
	Normative References . . . . . . . . . . . . . . . . . . . . . . . 50		Normative References . . . . . . . . . . . . . . . . . . . . . . . 50
	Informative References . . . . . . . . . . . . . . . . . . . . . . 52		Informative References . . . . . . . . . . . . . . . . . . . . . . 52
	Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . . 52		Author's Address . . . . . . . . . . . . . . . . . . . . . . . . . 53
	Full Copyright Statement . . . . . . . . . . . . . . . . . . . . . 53		Full Copyright Statement . . . . . . . . . . . . . . . . . . . . . 53
	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 15, line 18 ¶		skipping to change at page 15, line 18 ¶
	this syntax.		this syntax.
	The time value represents coordinated universal time (equivalent to		The time value represents coordinated universal time (equivalent to
	Greenwich Mean Time) if the "Z" form of <g-time-zone> is used,		Greenwich Mean Time) if the "Z" form of <g-time-zone> is used,
	otherwise the value represents a local time in the time zone		otherwise the value represents a local time in the time zone
	indicated by <g-differential>. In the latter case, coordinated		indicated by <g-differential>. In the latter case, coordinated
	universal time can be calculated by subtracting the differential from		universal time can be calculated by subtracting the differential from
	the local time. The "Z" form of <g-time-zone> SHOULD be used in		the local time. The "Z" form of <g-time-zone> SHOULD be used in
	preference to <g-differential>.		preference to <g-differential>.
			If <minute> is omitted then <fraction> represents a fraction of an
			hour, otherwise if <second> and <leap-second> are omitted then
			<fraction> represents a fraction of a minute, otherwise <fraction>
			represents a fraction of a second.
	Examples:		Examples:
	199412161032Z		199412161032Z
	199412160532-0500		199412160532-0500
	Both example values represent the same coordinated universal time:		Both example values represent the same coordinated universal time:
	10:32 AM, December 16, 1994.		10:32 AM, December 16, 1994.
	The LDAP definition for the Generalized Time syntax is:		The LDAP definition for the Generalized Time syntax is:
	( 1.3.6.1.4.1.1466.115.121.1.24 DESC 'Generalized Time' )		( 1.3.6.1.4.1.1466.115.121.1.24 DESC 'Generalized Time' )
	skipping to change at page 45, line 21 ¶		skipping to change at page 45, line 33 ¶
	matching rule comparisons are done on the underlying abstract value,		matching rule comparisons are done on the underlying abstract value,
	regardless of the particular encoding used.		regardless of the particular encoding used.
	6. Acknowledgements		6. Acknowledgements
	This document is primarily a revision of RFC 2252 by M. Wahl, A.		This document is primarily a revision of RFC 2252 by M. Wahl, A.
	Coulbeck, T. Howes, and S. Kille. RFC 2252 was a product of the IETF		Coulbeck, T. Howes, and S. Kille. RFC 2252 was a product of the IETF
	ASID Working Group.		ASID Working Group.
	This document is based upon input of the IETF LDAPBIS working group.		This document is based upon input of the IETF LDAPBIS working group.
	The authors wish to thank J. Sermersheim and K. Zeilenga for their		The author would like to thank Kathy Dally for editing the early
	significant contribution to this revision.		drafts of this revision, and Jim Sermersheim and Kurt Zeilenga for
			their significant contributions to this revision.
	7. IANA Considerations		7. IANA Considerations
	The Internet Assigned Numbers Authority (IANA) is requested to update		The Internet Assigned Numbers Authority (IANA) is requested to update
	the LDAP descriptors registry [BCP64] as indicated by the following		the LDAP descriptors registry [BCP64] as indicated by the following
	templates:		templates:
	Subject: Request for LDAP Descriptor Registration Update		Subject: Request for LDAP Descriptor Registration Update
	Descriptor (short name): see comment		Descriptor (short name): see comment
	Object Identifier: see comment		Object Identifier: see comment
	skipping to change at page 50, line 36 ¶		skipping to change at page 50, line 46 ¶
	directoryStringFirstComponentMatch, integerOrderingMatch,		directoryStringFirstComponentMatch, integerOrderingMatch,
	keywordMatch, numericStringOrderingMatch,		keywordMatch, numericStringOrderingMatch,
	octetStringOrderingMatch and wordMatch matching rules from		octetStringOrderingMatch and wordMatch matching rules from
	RFC 3698 & X.520 have been added.		RFC 3698 & X.520 have been added.
	Normative References		Normative References
	[KEYWORD] Bradner, S., "Key words for use in RFCs to Indicate		[KEYWORD] Bradner, S., "Key words for use in RFCs to Indicate
	Requirement Levels", BCP 14, RFC 2119, March 1997.		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		[UTF8] Yergeau, F., "UTF-8, a transformation format of ISO
	10646", RFC 3629, November 2003.		10646", RFC 3629, November 2003.
	[BCP64] Zeilenga, K., "Internet Assigned Numbers Authority (IANA)		[BCP64] Zeilenga, K., "Internet Assigned Numbers Authority (IANA)
	Considerations for the Lightweight Directory Access		Considerations for the Lightweight Directory Access
	Protocol (LDAP)", BCP 64, RFC 3383, September 2002.		Protocol (LDAP)", BCP 64, RFC 3383, September 2002.
			[ABNF] Crocker, D. and P. Overell, "Augmented BNF for Syntax
			Specifications: ABNF", draft-crocker-abnf-rfc2234bis-
			xx.txt, a work in progress, March 2005.
			[ROADMAP] Zeilenga, K., "Lightweight Directory Access Protocol
			(LDAP): Technical Specification Road Map", draft-ietf-
			ldapbis-roadmap-xx.txt, a work in progress, February 2005.
			[MODELS] Zeilenga, K., "LDAP: Directory Information Models", draft-
			ietf-ldapbis-models-xx.txt, a work in progress, February
			2005.
			[PROT] Sermersheim, J., "LDAP: The Protocol", draft-ietf-ldapbis-
			protocol-xx.txt, a work in progress, May 2005.
	[LDAPDN] Zeilenga, K., "LDAP: String Representation of		[LDAPDN] Zeilenga, K., "LDAP: String Representation of
	Distinguished Names", draft-ietf-ldapbis-dn-xx.txt, a work		Distinguished Names", draft-ietf-ldapbis-dn-xx.txt, a work
	in progress, February 2005.		in progress, February 2005.
	[PROT] Sermersheim, J., "LDAP: The Protocol", draft-ietf-ldapbis-		[PREP] Zeilenga, K., "LDAP: Internationalized String
	protocol-xx.txt, a work in progress, February 2005.		Preparation", draft-ietf-ldapbis-strprep-xx.txt, a work in
			progress, February 2005.
	[E.123] Notation for national and international telephone numbers,		[E.123] Notation for national and international telephone numbers,
	ITU-T Recommendation E.123, 1988.		ITU-T Recommendation E.123, 1988.
	[FAX] Standardization of Group 3 facsimile apparatus for		[FAX] Standardization of Group 3 facsimile apparatus for
	document transmission - Terminal Equipment and Protocols		document transmission - Terminal Equipment and Protocols
	for Telematic Services, ITU-T Recommendation T.4, 1993		for Telematic Services, ITU-T Recommendation T.4, 1993
	[T.50] International Reference Alphabet (IRA) (Formerly		[T.50] International Reference Alphabet (IRA) (Formerly
	International Alphabet No. 5 or IA5) Information		International Alphabet No. 5 or IA5) Information
	skipping to change at page 51, line 36 ¶		skipping to change at page 52, line 10 ¶
	Information Technology - Open Systems Interconnection -		Information Technology - Open Systems Interconnection -
	The Directory: Selected attribute types		The Directory: Selected attribute types
	[ASN.1] ITU-T Recommendation X.680 (07/02) | ISO/IEC 8824-1:2002,		[ASN.1] ITU-T Recommendation X.680 (07/02) | ISO/IEC 8824-1:2002,
	Information technology - Abstract Syntax Notation One		Information technology - Abstract Syntax Notation One
	(ASN.1): Specification of basic notation		(ASN.1): Specification of basic notation
	[ISO3166] ISO 3166, "Codes for the representation of names of		[ISO3166] ISO 3166, "Codes for the representation of names of
	countries".		countries".
			[ISO8601] ISO 8601:2004, "Data elements and interchange formats --
			Information interchange -- Representation of dates and
			times".
	[UCS] Universal Multiple-Octet Coded Character Set (UCS) -		[UCS] Universal Multiple-Octet Coded Character Set (UCS) -
	Architecture and Basic Multilingual Plane, ISO/IEC		Architecture and Basic Multilingual Plane, ISO/IEC
	10646-1: 1993 (with amendments).		10646-1: 1993 (with amendments).
	[JPEG] JPEG File Interchange Format (Version 1.02). Eric		[JPEG] JPEG File Interchange Format (Version 1.02). Eric
	Hamilton, C-Cube Microsystems, Milpitas, CA, September 1,		Hamilton, C-Cube Microsystems, Milpitas, CA, September 1,
	1992.		1992.
	[ROADMAP] Zeilenga, K., "Lightweight Directory Access Protocol
	(LDAP): Technical Specification Road Map", draft-ietf-
	ldapbis-roadmap-xx.txt, a work in progress, February 2005.
	[MODELS] Zeilenga, K., "LDAP: Directory Information Models", draft-
	ietf-ldapbis-models-xx.txt, a work in progress, February
	2005.
	[PREP] Zeilenga, K., "LDAP: Internationalized String
	Preparation", draft-ietf-ldapbis-strprep-xx.txt, a work in
	progress, February 2005.
	Informative References		Informative References
	[RFC2252] Wahl, M., Coulbeck, A., Howes, T. and S. Kille,		[RFC2252] Wahl, M., Coulbeck, A., Howes, T. and S. Kille,
	"Lightweight Directory Access Protocol (v3): Attribute		"Lightweight Directory Access Protocol (v3): Attribute
	Syntax Definitions", RFC 2252, December 1997.		Syntax Definitions", RFC 2252, December 1997.
	[RFC2256] Wahl, M., "A Summary of the X.500(96) User Schema for use		[RFC2256] Wahl, M., "A Summary of the X.500(96) User Schema for use
	with LDAPv3", RFC 2256, December 1997.		with LDAPv3", RFC 2256, December 1997.
	[RFC3377] Hodges, J. and R. Morgan, "Lightweight Directory Access		[RFC3377] Hodges, J. and R. Morgan, "Lightweight Directory Access
	Protocol (v3): Technical Specification", RFC 3377,		Protocol (v3): Technical Specification", RFC 3377,
	September 2002.		September 2002.
	[RFC3698] Zeilenga, K., "Lightweight Directory Access Protocol		[RFC3698] Zeilenga, K., "Lightweight Directory Access Protocol
	(LDAP): Additional Matching Rules", RFC 3698, February		(LDAP): Additional Matching Rules", RFC 3698, February
	2004.		2004.
	[SCHEMA] Dally, K., "LDAP: Schema for User Applications", draft-		[SCHEMA] Sciberras, A., "LDAP: Schema for User Applications",
	ietf-ldapbis-user-schema-xx.txt, a work in progress, July		draft-ietf-ldapbis-user-schema-xx.txt, a work in progress,
	2004.		April 2005.
	[LDAP-PKI] Zeilenga, K. D., "Lightweight Directory Access Protocol		[LDAP-PKI] Zeilenga, K. D., "Lightweight Directory Access Protocol
	(LDAP) schema definitions for X.509 Certificates", draft-		(LDAP) schema definitions for X.509 Certificates", draft-
	zeilenga-ldap-x509-xx.txt, a work in progress, February		zeilenga-ldap-x509-xx.txt, a work in progress, February
	2005.		2005.
	[X.500] ITU-T Recommendation X.500 (1993) | ISO/IEC 9594-1:1994,		[X.500] ITU-T Recommendation X.500 (1993) | ISO/IEC 9594-1:1994,
	Information Technology - Open Systems Interconnection -		Information Technology - Open Systems Interconnection -
	The Directory: Overview of concepts, models and services		The Directory: Overview of concepts, models and services
	[BER] ITU-T Recommendation X.690 (07/02) | ISO/IEC 8825-1:2002,		[BER] ITU-T Recommendation X.690 (07/02) | ISO/IEC 8825-1:2002,
	Information technology - ASN.1 encoding rules:		Information technology - ASN.1 encoding rules:
	Specification of Basic Encoding Rules (BER), Canonical		Specification of Basic Encoding Rules (BER), Canonical
	Encoding Rules (CER) and Distinguished Encoding Rules		Encoding Rules (CER) and Distinguished Encoding Rules
	(DER)		(DER)
	Authors' Addresses		Author's Address
	Steven Legg		Steven Legg
	eB2Bcom		eB2Bcom
	Suite3, Woodhouse Corporate Centre		Suite3, Woodhouse Corporate Centre
	935 Station Street		935 Station Street
	Box Hill North, Victoria 3129		Box Hill North, Victoria 3129
	AUSTRALIA		AUSTRALIA
	Phone: +61 3 9896 7830		Phone: +61 3 9896 7830
	Fax: +61 3 9896 7801		Fax: +61 3 9896 7801
	EMail: steven.legg@eb2bcom.com		EMail: steven.legg@eb2bcom.com
	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 (2005). This document is subject		Copyright (C) The Internet Society (2005).
	to the rights, licenses and restrictions contained in BCP 78, and
	except as set forth therein, the authors retain all their rights.		This document is subject to the rights, licenses and restrictions
			contained in BCP 78, and except as set forth therein, the authors
			retain all their rights.
	This document and the information contained herein are provided on an		This document and the information contained herein are provided on an
	"AS IS" basis and THE CONTRIBUTOR, THE ORGANIZATION HE/SHE REPRESENTS		"AS IS" basis and THE CONTRIBUTOR, THE ORGANIZATION HE/SHE REPRESENTS
	OR IS SPONSORED BY (IF ANY), THE INTERNET SOCIETY AND THE INTERNET		OR IS SPONSORED BY (IF ANY), THE INTERNET SOCIETY AND THE INTERNET
	ENGINEERING TASK FORCE DISCLAIM ALL WARRANTIES, EXPRESS OR IMPLIED,		ENGINEERING TASK FORCE DISCLAIM ALL WARRANTIES, EXPRESS OR IMPLIED,
	INCLUDING BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF THE		INCLUDING BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF THE
	INFORMATION HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED		INFORMATION HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED
	WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE.		WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE.
	Intellectual Property		Intellectual Property
	skipping to change at page 54, line 8 ¶		skipping to change at line 2523 ¶
	attempt made to obtain a general license or permission for the use of		attempt made to obtain a general license or permission for the use of
	such proprietary rights by implementers or users of this		such proprietary rights by implementers or users of this
	specification can be obtained from the IETF on-line IPR repository at		specification can be obtained from the IETF on-line IPR repository at
	http://www.ietf.org/ipr.		http://www.ietf.org/ipr.
	The IETF invites any interested party to bring to its attention any		The IETF invites any interested party to bring to its attention any
	copyrights, patents or patent applications, or other proprietary		copyrights, patents or patent applications, or other proprietary
	rights that may cover technology that may be required to implement		rights that may cover technology that may be required to implement
	this standard. Please address the information to the IETF at		this standard. Please address the information to the IETF at
	ietf-ipr@ietf.org.		ietf-ipr@ietf.org.
	This Internet-Draft expires on 18 August 2005.
End of changes. 30 change blocks.
	62 lines changed or deleted		64 lines changed or added
This html diff was produced by rfcdiff 1.48. The latest version is available from http://tools.ietf.org/tools/rfcdiff/