draft-ietf-pkix-ldap-pmi-schema-00.txt

PKIX的RFC英文文档

The syntax definition of 1.2.36.79672281.1.5.1 (NULL) is given in [3].


6 PMI Object Classes

The definitions of the PMI directory object classes can be found in 
section 17.1 of [9]. They are repeated here for the convenience of the 
reader.

pmiUser OBJECT-CLASS ::= {
 -- a privilege holder
	SUBCLASS OF	{top}
	KIND		auxiliary
	MAY CONTAIN	{attributeCertificateAttribute}
	ID { joint-iso-ccitt(2) ds(5) objectClass(6) pmiUser (24) } }


pmiAA OBJECT-CLASS ::= {
 -- an attribute authority
	SUBCLASS OF	{top}
	KIND		auxiliary
	MAY CONTAIN	{aACertificate |
			attributeCertificateRevocationList |
			attributeAuthorityRevocationList}
  	ID { joint-iso-ccitt(2) ds(5) objectClass(6) pmiAA (25) } }


pmiSOA OBJECT-CLASS ::= {
 -- a PMI Source of Authority
	SUBCLASS OF	{top}
	KIND		auxiliary
	MAY CONTAIN	{attributeCertificateRevocationList |
			attributeAuthorityRevocationList |
			attributeDescriptorCertificate}
  	ID { joint-iso-ccitt(2) ds(5) objectClass(6) pmiSOA (26) } }

attCertCRLDistributionPt	OBJECT-CLASS ::= {  
-- an AC CRL distribution point
   SUBCLASS OF  	{top}
   KIND         	auxiliary
   MAY CONTAIN  	{ attributeCertificateRevocationList |
                		attributeAuthorityRevocationList }
   ID { joint-iso-ccitt(2) ds(5) objectClass(6) 
attCertCRLDistributionPts (27) } }

pmiDelegationPath   OBJECT-CLASS	::= {
-- an object that may contain a delegation path
	SUBCLASS OF	{top}
	KIND			auxiliary
	MAY CONTAIN	{ delegationPath }
ID { joint-iso-ccitt(2) ds(5) objectClass(6) delegationPath (33) } }

privilegePolicy	OBJECT-CLASS	::= {
-- an object that may contain privilege policy information
	SUBCLASS OF	{top}
	KIND			auxiliary
	MAY CONTAIN	{privPolicy }
ID { joint-iso-ccitt(2) ds(5) objectClass(6) privilegePolicy (32) } }


7. Filter Examples

The following examples are written using the string representation of 
Search filters defined in [14]. Line-breaks have been added as an aid to 
readability.

i) To exactly match one attribute certificate using equalityMatch with 
attributeCertificateExactMatch and 
GSERAttributeCertificateExactAssertion

      (attributeCertificateAttribute={serialNumber 12345 , issuer { 
issuerName { directoryName rdnSequence:"O=truetrust ltd, C=GB" })


ii) To exactly match one attribute certificate using equalityMatch with 
attributeCertificateExactMatch and SimpleCertificateExactAssertion

      (attributeCertificateAttribute=12345$O=truetrust ltd, C=GB)


iii) To match on the serial number of an attribute certificate using 
extensibleMatch with component matching [13]

(attributeCertificateAttribute:componentFilterMatch:=
       item:{ component "serialNumber", rule integerMatch, 
value 12345 })


iv) To exactly match one attribute certificate using extensibleMatch 
with component matching

(attributeCertificateAttribute:componentFilterMatch:=and:{
item:{ component "serialNumber", rule integerMatch, value 12345 }
item:{ component "issuer.issuerName.directoryName.rdnSequence", rule 
distinguishedNameMatch, value "O=truetrust ltd, C=GB"  } })

v) To match attribute certificates containing a certain role

To Be Worked Out Later#

8. Security Considerations

This [Internet Draft/Standard] describes the schema for the storage
and matching of PMI attributes (attribute certificates, revocation lists 
etc.) in an LDAP directory server. It does not address the protocol for 
the retrieval of this information.

LDAP servers SHOULD use authentication and access control methods to 
protect this information during its storage from unauthorised 
modification and retrieval. In addition, clients MAY choose to
encrypt the attributes in the attribute certificates before storing
them in an LDAP server to ensure their confidentiality.


9. References

Normative

[1] Bradner, S. The Internet Standards Process -- Revision 3. RFC
2026  October 1996.

[2] Chadwick, D.W., Legg, S. "Internet X.509 Public Key Infrastructure
LDAP Schema and Syntaxes for PKIs" <draft-pkix-ldap-pki-schema-00.txt>, 
June 2002

[3] S. Legg, "Generic String Encoding Rules", <draft-legg-ldap-gser-
XX.txt>, March 2002, a work in progress

[4] J. Sermersheim "Lightweight Directory Access Protocol (v3)" <draft-
ietf-ldapbis-protocol-02.txt> July 2001

[5] S.Bradner. "Key words for use in RFCs to Indicate Requirement
Levels", RFC 2119, March 1997.

[6] S. Legg, "Common Elements of GSER Encodings", <draft-legg-ldap-gser-
abnf-XX.txt>, March 2002, a work in progress

[7] ITU-T Rec. X.520(2000) The  Directory: Selected Attribute Types

[9] ITU-T Rec. X.509(2000) The  Directory:  Authentication
Framework

[10] D. Crocker, P. Overell, "Augmented BNF for Syntax
Specifications: ABNF", RFC 2234, November 1997

Informative

[13] S. Legg, "LDAP & X.500 Component Matching Rules", <draft-legg-
ldapext-component-matching-04.txt>, November 2001, a work in progress

[14] Howes, T. "The String Representation of LDAP Search Filters". RFC 
2254, December 1997.
 


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. [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.


11. Copyright


Copyright (C) The Internet Society (2002). All Rights Reserved.

This document and translations of it may be copied and furnished to
others, and derivative works that comment on or otherwise explain it
or assist in its implementation may be prepared, copied, published
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
revoked by the Internet Society or its successors or assigns.

This document and the information contained herein is provided on an
"AS IS" basis and THE INTERNET SOCIETY AND THE INTERNET ENGINEERING
TASK FORCE DISCLAIMS 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.


12. Authors' Addresses

David Chadwick
IS Institute
University of Salford
Salford
England
M5 4WT

Email: [e-mail]


Steven Legg
Adacel Technologies Ltd.
405-409 Ferntree Gully Road,
Mount Waverley,
Victoria, 3149
Australia

Email: [e-mail]


13. Changes
 
>From Version 00

i) Added ABNF notation for all of the syntaxes.

ii) Removed the restriction on the syntax of Distribution Point Names.

iii) Removed constraints on IssuerSerial.

iv) Bug detected in X.509 AttributeCertificateExactMatch that will need
resolving.

v) Changed the string encodings for non-exact matches to keywords for 
each component instead of $ separators.

>From Version 01

i)	Added and corrected all X.509 PKI schema definitions, since these 
have been removed from RFC2252-bis.
ii)	Changed assertion syntaxes to use the syntax defined by Component 
Matching Rules
iii)	Included all the matching rules for AC extensions

>From Version 02 of <draft-pkix-ldap-schema-02.txt>

i)	PKI and PMI schema has been split into separate IDs
ii)	Example have been added
iii)	Text has been added to mandate that servers must store and 
retrieve syntaxes containing digital signatures exactly as given.
iv)	Text has been removed concerning the use of the ;binary encoding 
option, as per the decision of the LDAPBIS group.

14. Outstanding Issues

i.	There is still a bug in the X.509 
AttributeCertificateExactAssertion. It reads:

AttributeCertificateExactAssertion ::= SEQUENCE {
	serialNumber	CertificateSerialNumber OPTIONAL,
	issuer		IssuerSerial }
OPTIONAL should be removed from the serialNumber. IssuerSerial should be 
replaced by AttCertIssuer. This ID has assumed that the change will be 
made.

ii.	Should the AttributeType in Attribute Certificate Match allow the 
LDAP <descr> encoding option for describing attribute type OIDs 
(i.e. user friendly names instead of object identifiers)? Note 
that attribute names are not guaranteed to be unique, whereas OIDs 
are.

iii.	The Source of Authority Match is not defined in X.509. Do we 
prefer compatibility with X.509 and remove it, or get X.509 to add 
it.


15. Table of Contents
1. Introduction	1
2. Subschema Publishing	2
3. PMI Attributes and Syntaxes	2
3.1 Attribute Certificate Attribute	2
3.2 Attribute Authority Certificate Attribute	2
3.3 Attribute Descriptor Certificate Attribute	3
3.4 Attribute  Certificate Syntax	3
3.5 Attribute Certificate Revocation List Attribute	3
3.6 Attribute Authority Certificate Revocation List Attribute	4
3.7 Delegation Path Attribute	4
3.8 Delegation Path Syntax	4
4 PMI Matching Rules	5
4.1 Attribute Certificate Exact Match	5
4.2 Attribute Certificate Match	9
5 AC Extensions Matching Rules	10
5.1 Holder Issuer Match	10
5.2 Delegation Path Match	10
5.3 Authority Attribute Identifier Match	11
5.4 Role Specification Certificate Identifier Match	11
5.5	Basic Attribute Constraints Match	12
5.6	Delegated Name Constraints Match	12
5.7  Time Specification Match	13
5.8	Acceptable Certificate Policies Match	16
5.9 Attribute Descriptor Match	16
5.10 Source of Authority Match	17
6 PMI Object Classes	18
7. Filter Examples	19
8. Security Considerations	19
9. References	20
Normative	20
Informative	20
10. Intellectual Property Notice	20
11. Copyright	21
12. Authors' Addresses	21
13. Changes	22
14. Outstanding Issues	22
15. Table of Contents	23