draft-ietf-asid-ldapv3-attributes-00.txt   draft-ietf-asid-ldapv3-attributes-01.txt 
Network Working Group M. Wahl Network Working Group M. Wahl
INTERNET-DRAFT ISODE Consortium INTERNET-DRAFT ISODE Consortium
Obsoletes: RFC 1778 A. Coulbeck Obsoletes: RFC 1778 A. Coulbeck
ISODE Consortium ISODE Consortium
T. Howes T. Howes
University of Michigan Netscape Communications Corp.
S. Kille S. Kille
ISODE Consortium ISODE Consortium
Expires in six months from 23 February 1996
Intended Category: Standards Track Intended Category: Standards Track
Lightweight Directory Access Protocol: Lightweight Directory Access Protocol:
Standard and Pilot Attribute Definitions Standard and Pilot Attribute Definitions
<draft-ietf-asid-ldapv3-attributes-00.txt> <draft-ietf-asid-ldapv3-attributes-01.txt>
1. Status of this Memo 1. Status of this Memo
This document is an Internet-Draft. Internet-Drafts are working This document is an Internet-Draft. Internet-Drafts are working
documents of the Internet Engineering Task Force (IETF), its areas, and documents of the Internet Engineering Task Force (IETF), its areas, and
its working groups. Note that other groups may also distribute working its working groups. Note that other groups may also distribute working
documents as Internet-Drafts. documents as 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
skipping to change at line 38 skipping to change at line 39
To learn the current status of any Internet-Draft, please check the To learn the current status of any Internet-Draft, please check the
"1id-abstracts.txt" listing contained in the Internet-Drafts Shadow "1id-abstracts.txt" listing contained in the Internet-Drafts Shadow
Directories on ds.internic.net (US East Coast), nic.nordu.net (Europe), Directories on ds.internic.net (US East Coast), nic.nordu.net (Europe),
ftp.isi.edu (US West Coast), or munnari.oz.au (Pacific Rim). ftp.isi.edu (US West Coast), or munnari.oz.au (Pacific Rim).
2. Abstract 2. Abstract
The Lightweight Directory Access Protocol (LDAP) [1] requires that the The Lightweight Directory Access Protocol (LDAP) [1] requires that the
contents of AttributeValue fields in protocol elements be octet contents of AttributeValue fields in protocol elements be octet
strings. This document defines the requirements that must be strings. This document defines the requirements that must be
satisfied by encoding rules used to render X.500 Directory attribute satisfied by encoding rules used to render X.500 directory attribute
syntaxes into a form suitable for use in the LDAP, then goes on to syntaxes into a form suitable for use in the LDAP, then goes on to
define the encoding rules for the standard set of attribute syntaxes define the encoding rules for the standard set of attribute syntaxes
of [2],[3] and [4]. of [2],[3] and [4].
3. Table of LDAP Attributes 3. Table of LDAP Attributes
This section lists all Attribute Type names defined for this version of This section lists all Attribute Type names defined for this version of
LDAP. Servers may support additional names and attributes not listed LDAP. Servers may support additional names and attributes not listed
here. Later documents may define additional types. here. Later documents may define additional types.
skipping to change at line 50 skipping to change at line 51
define the encoding rules for the standard set of attribute syntaxes define the encoding rules for the standard set of attribute syntaxes
of [2],[3] and [4]. of [2],[3] and [4].
3. Table of LDAP Attributes 3. Table of LDAP Attributes
This section lists all Attribute Type names defined for this version of This section lists all Attribute Type names defined for this version of
LDAP. Servers may support additional names and attributes not listed LDAP. Servers may support additional names and attributes not listed
here. Later documents may define additional types. here. Later documents may define additional types.
3.1 Standard User Attributes 3.1 Standard User Attributes
The attributes listed in this section are those defined in X.520(1993), The attributes listed in this section are those defined in X.520(1993),
likely to be present in user entries. likely to be present in user entries. Servers must recognize all the
attributes of this section.
Attribute Type Name OID Syntax Attribute Type Name X.500 OID Syntax
==================== =============== ================ ==================== =============== ================
objectClass 2.5.4.0 OID objectClass 2.5.4.0 OID
aliasedObjectName 2.5.4.1 DN aliasedObjectName 2.5.4.1 DN
knowledgeInformation 2.5.4.2 DirectoryString knowledgeInformation 2.5.4.2 DirectoryString
commonName 2.5.4.3 DirectoryString
cn 2.5.4.3 DirectoryString cn 2.5.4.3 DirectoryString
surname 2.5.4.4 DirectoryString
sn 2.5.4.4 DirectoryString sn 2.5.4.4 DirectoryString
serialNumber 2.5.4.5 PrintableString serialNumber 2.5.4.5 PrintableString
countryName 2.5.4.6 CountryString
c 2.5.4.6 CountryString c 2.5.4.6 CountryString
localityName 2.5.4.7 DirectoryString
l 2.5.4.7 DirectoryString l 2.5.4.7 DirectoryString
stateOrProvinceName 2.5.4.8 DirectoryString
st 2.5.4.8 DirectoryString st 2.5.4.8 DirectoryString
streetAddress 2.5.4.9 DirectoryString
street 2.5.4.9 DirectoryString
organizationName 2.5.4.10 DirectoryString
o 2.5.4.10 DirectoryString o 2.5.4.10 DirectoryString
organizationalUnitName 2.5.4.11 DirectoryString
ou 2.5.4.11 DirectoryString ou 2.5.4.11 DirectoryString
title 2.5.4.12 DirectoryString title 2.5.4.12 DirectoryString
description 2.5.4.13 DirectoryString description 2.5.4.13 DirectoryString
searchGuide 2.5.4.14 Guide searchGuide 2.5.4.14 Guide
businessCategory 2.5.4.15 DirectoryString businessCategory 2.5.4.15 DirectoryString
postalAddress 2.5.4.16 PostalAddress postalAddress 2.5.4.16 PostalAddress
postalCode 2.5.4.17 DirectoryString postalCode 2.5.4.17 DirectoryString
postOfficeBox 2.5.4.18 DirectoryString postOfficeBox 2.5.4.18 DirectoryString
physicalDeliveryOfficeName 2.5.4.19 DirectoryString physicalDeliveryOfficeName 2.5.4.19 DirectoryString
telephoneNumber 2.5.4.20 TelephoneNumber telephoneNumber 2.5.4.20 TelephoneNumber
skipping to change at line 108 skipping to change at line 102
userPassword 2.5.4.35 Password userPassword 2.5.4.35 Password
userCertificate 2.5.4.36 Certificate userCertificate 2.5.4.36 Certificate
cACertificate 2.5.4.37 Certificate cACertificate 2.5.4.37 Certificate
authorityRevocationList 2.5.4.38 CertificateList authorityRevocationList 2.5.4.38 CertificateList
certificateRevocationList 2.5.4.39 CertificateList certificateRevocationList 2.5.4.39 CertificateList
crossCertificatePair 2.5.4.40 CertificatePair crossCertificatePair 2.5.4.40 CertificatePair
name 2.5.4.41 DirectoryString name 2.5.4.41 DirectoryString
givenName 2.5.4.42 DirectoryString givenName 2.5.4.42 DirectoryString
initials 2.5.4.43 DirectoryString initials 2.5.4.43 DirectoryString
generationQualifier 2.5.4.44 DirectoryString generationQualifier 2.5.4.44 DirectoryString
ds.4.45 2.5.4.45 BitString x500UniqueIdentifier 2.5.4.45 BitString
dnQualifier 2.5.4.46 PrintableString dnQualifier 2.5.4.46 PrintableString
enhancedSearchGuide 2.5.4.47 EnhancedGuide enhancedSearchGuide 2.5.4.47 EnhancedGuide
protocolInformation 2.5.4.48 ProtocolInformation protocolInformation 2.5.4.48 ProtocolInformation
distinguishedName 2.5.4.49 DN distinguishedName 2.5.4.49 DN
uniqueMember 2.5.4.50 NameAndOptionalUID uniqueMember 2.5.4.50 NameAndOptionalUID
houseIdentifier 2.5.4.51 DirectoryString houseIdentifier 2.5.4.51 DirectoryString
3.2. Pilot User Attributes 3.2. Pilot User Attributes
These attributes are defined in RFC 1274. These attributes are defined in RFC 1274.
Attribute Type Name OID Syntax Attribute Type Name OID Syntax
==================== =============================== ================ ==================== =========================== ================
userid 0.9.2342.19200300.100.1.1 CaseIgnoreString
uid 0.9.2342.19200300.100.1.1 CaseIgnoreString uid 0.9.2342.19200300.100.1.1 CaseIgnoreString
textEncodedORaddress 0.9.2342.19200300.100.1.2 CaseIgnoreString textEncodedORaddress 0.9.2342.19200300.100.1.2 CaseIgnoreString
rfc822Mailbox 0.9.2342.19200300.100.1.3 CaseIgnoreIA5String
mail 0.9.2342.19200300.100.1.3 CaseIgnoreIA5String mail 0.9.2342.19200300.100.1.3 CaseIgnoreIA5String
info 0.9.2342.19200300.100.1.4 CaseIgnoreString info 0.9.2342.19200300.100.1.4 CaseIgnoreString
favouriteDrink 0.9.2342.19200300.100.1.5 CaseIgnoreString
drink 0.9.2342.19200300.100.1.5 CaseIgnoreString drink 0.9.2342.19200300.100.1.5 CaseIgnoreString
roomNumber 0.9.2342.19200300.100.1.6 CaseIgnoreString roomNumber 0.9.2342.19200300.100.1.6 CaseIgnoreString
photo 0.9.2342.19200300.100.1.7 Fax photo 0.9.2342.19200300.100.1.7 Fax
userClass 0.9.2342.19200300.100.1.8 CaseIgnoreString userClass 0.9.2342.19200300.100.1.8 CaseIgnoreString
host 0.9.2342.19200300.100.1.9 CaseIgnoreString host 0.9.2342.19200300.100.1.9 CaseIgnoreString
manager 0.9.2342.19200300.100.1.10 DN manager 0.9.2342.19200300.100.1.10 DN
documentIdentifier 0.9.2342.19200300.100.1.11 CaseIgnoreString documentIdentifier 0.9.2342.19200300.100.1.11 CaseIgnoreString
documentTitle 0.9.2342.19200300.100.1.12 CaseIgnoreString documentTitle 0.9.2342.19200300.100.1.12 CaseIgnoreString
documentVersion 0.9.2342.19200300.100.1.13 CaseIgnoreString documentVersion 0.9.2342.19200300.100.1.13 CaseIgnoreString
documentAuthor 0.9.2342.19200300.100.1.14 DN documentAuthor 0.9.2342.19200300.100.1.14 DN
documentLocation 0.9.2342.19200300.100.1.15 CaseIgnoreString documentLocation 0.9.2342.19200300.100.1.15 CaseIgnoreString
homePhone 0.9.2342.19200300.100.1.20 TelephoneNumber homePhone 0.9.2342.19200300.100.1.20 TelephoneNumber
secretary 0.9.2342.19200300.100.1.21 DN secretary 0.9.2342.19200300.100.1.21 DN
otherMailbox 0.9.2342.19200300.100.1.22 OtherMailbox otherMailbox 0.9.2342.19200300.100.1.22 OtherMailbox
lastModifiedTime 0.9.2342.19200300.100.1.23 UTCTime lastModifiedTime 0.9.2342.19200300.100.1.23 UTCTime
lastModifiedBy 0.9.2342.19200300.100.1.24 DN lastModifiedBy 0.9.2342.19200300.100.1.24 DN
domainComponent 0.9.2342.19200300.100.1.25 CaseIgnoreIA5String
dc 0.9.2342.19200300.100.1.25 CaseIgnoreIA5String dc 0.9.2342.19200300.100.1.25 CaseIgnoreIA5String
dNSRecord 0.9.2342.19200300.100.1.26 IA5String dNSRecord 0.9.2342.19200300.100.1.26 IA5String
mXRecord 0.9.2342.19200300.100.1.28 IA5String mXRecord 0.9.2342.19200300.100.1.28 IA5String
nSRecord 0.9.2342.19200300.100.1.29 IA5String nSRecord 0.9.2342.19200300.100.1.29 IA5String
sOARecord 0.9.2342.19200300.100.1.30 IA5String sOARecord 0.9.2342.19200300.100.1.30 IA5String
cNAMERecord 0.9.2342.19200300.100.1.31 IA5String cNAMERecord 0.9.2342.19200300.100.1.31 IA5String
associatedDomain 0.9.2342.19200300.100.1.37 CaseIgnoreIA5String associatedDomain 0.9.2342.19200300.100.1.37 CaseIgnoreIA5String
associatedName 0.9.2342.19200300.100.1.38 DN associatedName 0.9.2342.19200300.100.1.38 DN
homePostalAddress 0.9.2342.19200300.100.1.39 PostalAddress homePostalAddress 0.9.2342.19200300.100.1.39 PostalAddress
personalTitle 0.9.2342.19200300.100.1.40 CaseIgnoreString personalTitle 0.9.2342.19200300.100.1.40 CaseIgnoreString
mobileTelephoneNumber 0.9.2342.19200300.100.1.41 TelephoneNumber
mobile 0.9.2342.19200300.100.1.41 TelephoneNumber mobile 0.9.2342.19200300.100.1.41 TelephoneNumber
pagerTelephoneNumber 0.9.2342.19200300.100.1.42 TelephoneNumber
pager 0.9.2342.19200300.100.1.42 TelephoneNumber pager 0.9.2342.19200300.100.1.42 TelephoneNumber
friendlyCountryName 0.9.2342.19200300.100.1.43 CaseIgnoreString
co 0.9.2342.19200300.100.1.43 CaseIgnoreString co 0.9.2342.19200300.100.1.43 CaseIgnoreString
ccitt.9.2342.19200300.100.1.44 0.9.2342.19200300.100.1.44 CaseIgnoreString pilotUniqueIdentifier 0.9.2342.19200300.100.1.44 CaseIgnoreString
organizationalStatus 0.9.2342.19200300.100.1.45 CaseIgnoreString organizationalStatus 0.9.2342.19200300.100.1.45 CaseIgnoreString
janetMailbox 0.9.2342.19200300.100.1.46 CaseIgnoreIA5String janetMailbox 0.9.2342.19200300.100.1.46 CaseIgnoreIA5String
mailPreferenceOption 0.9.2342.19200300.100.1.47 MailPreference mailPreferenceOption 0.9.2342.19200300.100.1.47 MailPreference
buildingName 0.9.2342.19200300.100.1.48 CaseIgnoreString buildingName 0.9.2342.19200300.100.1.48 CaseIgnoreString
dSAQuality 0.9.2342.19200300.100.1.49 DSAQualitySyntax dSAQuality 0.9.2342.19200300.100.1.49 DSAQualitySyntax
singleLevelQuality 0.9.2342.19200300.100.1.50 DataQualitySyntax singleLevelQuality 0.9.2342.19200300.100.1.50 DataQualitySyntax
subtreeMinimumQuality 0.9.2342.19200300.100.1.51 DataQualitySyntax subtreeMinimumQuality 0.9.2342.19200300.100.1.51 DataQualitySyntax
subtreeMaximumQuality 0.9.2342.19200300.100.1.52 DataQualitySyntax subtreeMaximumQuality 0.9.2342.19200300.100.1.52 DataQualitySyntax
personalSignature 0.9.2342.19200300.100.1.53 Fax personalSignature 0.9.2342.19200300.100.1.53 Fax
dITRedirect 0.9.2342.19200300.100.1.54 DN dITRedirect 0.9.2342.19200300.100.1.54 DN
audio 0.9.2342.19200300.100.1.55 Audio audio 0.9.2342.19200300.100.1.55 Audio
documentPublisher 0.9.2342.19200300.100.1.56 CaseIgnoreString documentPublisher 0.9.2342.19200300.100.1.56 CaseIgnoreString
jpegPhoto 0.9.2342.19200300.100.1.60 JPEG jpegPhoto 0.9.2342.19200300.100.1.60 JPEG
3.3. Collective Attributes 3.3. Collective Attributes
These attributes are stored in collective attribute subentries, but may These attributes are stored in collective attribute subentries, but may
be visible in user entries if requested. be visible in user entries if requested. Servers which do not support
the X.500 protocols are not required to recognize these attributes, and
non-management clients should not assume they are recognized by the
server.
Attribute Type Name OID Syntax Attribute Type Name OID Syntax
==================== =============== ================ ==================== ========== ================
collectiveLocalityName 2.5.4.7.1 DirectoryString collectiveLocalityName 2.5.4.7.1 DirectoryString
collectiveStateOrProvinceName 2.5.4.8.1 DirectoryString collectiveStateOrProvinceName 2.5.4.8.1 DirectoryString
collectiveStreetAddress 2.5.4.9.1 DirectoryString collectiveStreetAddress 2.5.4.9.1 DirectoryString
collectiveOrganizationName 2.5.4.10.1 DirectoryString collectiveOrganizationName 2.5.4.10.1 DirectoryString
collectiveOrganizationalUnitName 2.5.4.11.1 DirectoryString collectiveOrganizationalUnitName 2.5.4.11.1 DirectoryString
collectivePostalAddress 2.5.4.16.1 PostalAddress collectivePostalAddress 2.5.4.16.1 PostalAddress
collectivePostalCode 2.5.4.17.1 DirectoryString collectivePostalCode 2.5.4.17.1 DirectoryString
collectivePostOfficeBox 2.5.4.18.1 DirectoryString collectivePostOfficeBox 2.5.4.18.1 DirectoryString
collectivePhysicalDeliveryOfficeName 2.5.4.19.1 DirectoryString collectivePhysicalDeliveryOfficeName 2.5.4.19.1 DirectoryString
collectiveTelephoneNumber 2.5.4.20.1 TelephoneNumber collectiveTelephoneNumber 2.5.4.20.1 TelephoneNumber
collectiveTelexNumber 2.5.4.21.1 TelexNumber collectiveTelexNumber 2.5.4.21.1 TelexNumber
collectiveTeletexTerminalIdentifier 2.5.4.22.1 TeletexTerminalIdentifier collectiveTeletexTerminalIdentifier 2.5.4.22.1 TeletexTerminalIdentifier
collectiveFacsimileTelephoneNumber 2.5.4.23.1 FacsimileTelephoneNumber collectiveFacsimileTelephoneNumber 2.5.4.23.1 FacsimileTelephoneNumber
collectiveInternationaliSDNNumber 2.5.4.25.1 NumericString collectiveInternationaliSDNNumber 2.5.4.25.1 NumericString
3.4. Standard Operational Attributes 3.4. Standard Operational Attributes
These attributes are defined in X.501(1993) Annexes B through E. These attributes are defined in X.501(1993) Annexes B through E. All
servers must recognize the attributes "createTimestamp",
"modifyTimestamp", "creatorsName", "modifiersName", "attributeTypes",
"objectClasses" and "subschemaSubentry". Servers implementing X.500
protocols must recognize all of the attributes listed here.
Attribute Type Name OID Syntax Attribute Type Name OID Syntax
==================== =============== ================ ==================== ============ ================
createTimestamp 2.5.18.1 GeneralizedTime createTimestamp 2.5.18.1 GeneralizedTime
modifyTimestamp 2.5.18.2 GeneralizedTime modifyTimestamp 2.5.18.2 GeneralizedTime
creatorsName 2.5.18.3 DN creatorsName 2.5.18.3 DN
modifiersName 2.5.18.4 DN modifiersName 2.5.18.4 DN
administrativeRole 2.5.18.5 OID administrativeRole 2.5.18.5 OID
subtreeSpecification 2.5.18.6 SubtreeSpecification subtreeSpecification 2.5.18.6 SubtreeSpecification
collectiveExclusions 2.5.18.7 OID collectiveExclusions 2.5.18.7 OID
subschemaSubentry 2.5.18.10 DN
dITStructureRules 2.5.21.1 DITStructureRuleDescription dITStructureRules 2.5.21.1 DITStructureRuleDescription
dITContentRules 2.5.21.2 DITContentRuleDescription dITContentRules 2.5.21.2 DITContentRuleDescription
matchingRules 2.5.21.4 MatchingRuleDescription matchingRules 2.5.21.4 MatchingRuleDescription
attributeTypes 2.5.21.5 AttributeTypeDescription attributeTypes 2.5.21.5 AttributeTypeDescription
objectClasses 2.5.21.6 ObjectClassDescription objectClasses 2.5.21.6 ObjectClassDescription
nameForms 2.5.21.7 NameFormDescription nameForms 2.5.21.7 NameFormDescription
matchingRuleUse 2.5.21.8 MatchingRuleUseDescription matchingRuleUse 2.5.21.8 MatchingRuleUseDescription
structuralObjectClass 2.5.21.9 OID structuralObjectClass 2.5.21.9 OID
governingStructureRule 2.5.21.10 INTEGER governingStructureRule 2.5.21.10 INTEGER
accessControlScheme 2.5.24.1 OID accessControlScheme 2.5.24.1 OID
skipping to change at line 234 skipping to change at line 229
subentryACI 2.5.24.6 ACIItem subentryACI 2.5.24.6 ACIItem
dseType 2.5.12.0 DSEType dseType 2.5.12.0 DSEType
myAccessPoint 2.5.12.1 AccessPoint93 myAccessPoint 2.5.12.1 AccessPoint93
superiorKnowledge 2.5.12.2 AccessPoint93 superiorKnowledge 2.5.12.2 AccessPoint93
specificKnowledge 2.5.12.3 MasterAndShadowAccessPoints specificKnowledge 2.5.12.3 MasterAndShadowAccessPoints
nonSpecificKnowledge 2.5.12.4 MasterAndShadowAccessPoints nonSpecificKnowledge 2.5.12.4 MasterAndShadowAccessPoints
supplierKnowledge 2.5.12.5 SupplierInformation supplierKnowledge 2.5.12.5 SupplierInformation
consumerKnowledge 2.5.12.6 SupplierOrConsumer consumerKnowledge 2.5.12.6 SupplierOrConsumer
secondaryShadows 2.5.12.7 SupplierAndConsumers secondaryShadows 2.5.12.7 SupplierAndConsumers
3.5 LDAP-defined attributes
These attributes are defined in [1].
Attribute Type Name Syntax
==================== ============
entryName DN
administratorAddress IA5String
currentTime GeneralizedTime
serverName DN
certificationPath CertificationPath
namingContexts DN
altLdapServer IA5String
altX500Server AccessPoint93
supportedExtension OID
4. Attribute Syntax Encoding Requirements 4. Attribute Syntax Encoding Requirements
This section defines general requirements for LDAP attribute value This section defines general requirements for LDAP attribute value
syntax encodings. All documents defining attribute syntax encodings for syntax encodings. All documents defining attribute syntax encodings for
use with LDAP are expected to conform to these requirements. use with LDAP are expected to conform to these requirements.
The encoding rules defined for a given attribute syntax must produce The encoding rules defined for a given attribute syntax must produce
octet strings. To the greatest extent possible, encoded octet octet strings. To the greatest extent possible, encoded octet
strings should be usable in their native encoded form for display strings should be usable in their native encoded form for display
purposes. In particular, encoding rules for attribute syntaxes purposes. In particular, encoding rules for attribute syntaxes
defining non-binary values should produce strings that can be defining non-binary values should produce strings that can be
displayed with little or no translation by clients implementing displayed with little or no translation by clients implementing
LDAP. However, if it is necessary to obtain the a reversible encoding LDAP.
in order to make of an attribute (e.g. userCertificate) then this
requirement takes precedence over the requirement for the attribute In these examples where a user-specified string is used as part of a
to be human-readable. larger production (other than a Distinguished Name), a backslash quoting
mechanism is used to permit encoding the following separator symbol
character (such as ''' or '$'). The backslash is followed by a pair of
hexidecimal digits representing the next character. A backslash itself
in the string is transmitted as '\5C' or '\5c'.
4.1. Common BNF 4.1. Common BNF
For the purposes of defining the encoding rules for attribute syntaxes, For the purposes of defining the encoding rules for attribute syntaxes,
the following auxiliary BNF definitions will be used: the following auxiliary BNF definitions will be used:
<a> ::= 'a' | 'b' | 'c' | 'd' | 'e' | 'f' | 'g' | 'h' | 'i' | <a> ::= 'a' | 'b' | 'c' | 'd' | 'e' | 'f' | 'g' | 'h' | 'i' |
'j' | 'k' | 'l' | 'm' | 'n' | 'o' | 'p' | 'q' | 'r' | 'j' | 'k' | 'l' | 'm' | 'n' | 'o' | 'p' | 'q' | 'r' |
's' | 't' | 'u' | 'v' | 'w' | 'x' | 'y' | 'z' | 'A' | 's' | 't' | 'u' | 'v' | 'w' | 'x' | 'y' | 'z' | 'A' |
'B' | 'C' | 'D' | 'E' | 'F' | 'G' | 'H' | 'I' | 'J' | 'B' | 'C' | 'D' | 'E' | 'F' | 'G' | 'H' | 'I' | 'J' |
skipping to change at line 286 skipping to change at line 301
<numericstring> ::= <d> | <d> <numericstring> <numericstring> ::= <d> | <d> <numericstring>
<keystring> ::= <a> | <a> <anhstring> <keystring> ::= <a> | <a> <anhstring>
<anhstring> ::= <k> | <k> <anhstring> <anhstring> ::= <k> | <k> <anhstring>
<printablestring> ::= <p> | <p> <printablestring> <printablestring> ::= <p> | <p> <printablestring>
<space> ::= ' ' | ' ' <space> <space> ::= ' ' | ' ' <space>
<utf8> ::= any sequence of octets formed from the UTF-8 transformation
of a BMP character
<dstring> ::= <utf8> | <utf8> <dstring>
4.2. Undefined and Binary 4.2. Undefined and Binary
Values of types not described in this document or not supported by Values of types not described in this document or not supported by
servers are be default encoded as if they were values of type Octet servers are by default encoded as if they were values of type Octet
String, with the string value being the BER-encoded transfer String, with the string value being the BER-encoded transfer
representation of the value. This encoding format is also used if the representation of the value. This encoding format is also used if the
binary encoding is requested by the client for an attribute. binary encoding is requested by the client for an attribute.
All servers must be capable of supporting this form for both generating All servers must be capable of supporting this form for both generating
Search results and parsing Add and Modify requests. Search results and parsing Add and Modify requests.
4.3. Readable
If the client has requested that all attributes be transferred in a
readable form, then undefined values are pretty-printed in ASN.1 value
notation to make an IA5 string. If there are any character string
values which contain non-printing characters, these strings are pretty-
printed in the hexidecimal representation as used for octet strings.
Client applications should only use the readable form when retrieving
attributes from searches. Servers may not be able to handle this form
as input to Add and Modify operations.
5. Standard User Attribute Syntax Encodings 5. Standard User Attribute Syntax Encodings
Servers must recognize all the syntaxes described in this section.
5.1. BitString 5.1. BitString
The encoding of a value with BitString syntax is according to the The encoding of a value with BitString syntax is according to the
following BNF: following BNF:
<bitstring> ::= ''' <binary-digits> ''B' <bitstring> ::= ''' <binary-digits> ''B'
<binary-digits> ::= '0' <binary-digits> | '1' <binary-digits> | <binary-digits> ::= '0' <binary-digits> | '1' <binary-digits> |
empty empty
5.2. PrintableString 5.2. PrintableString
The encoding of a value with PrintableString syntax is the string The encoding of a value with PrintableString syntax is the string
value itself. value itself.
5.3. DirectoryString 5.3. DirectoryString
A string with DirectoryString syntax is encoded depending on the ASN.1 A string with DirectoryString syntax is encoded in the UTF-8 form of
form chosen in that string, and the setting of the preferredSyntax Unicode. For characters in the PrintableString form, the value is
Server Control made by the client earlier in this session. encoded as the string value itself.
If it is of the PrintableString form, the value is encoded as the
string value itself.
If it is of the TeletexString form, then characters which correspond If it is of the TeletexString form, then characters which correspond
to the IA5 subset of TeletexString are mapped directly, those which to the IA5 subset of TeletexString are mapped directly, those which
correspond to ISO-8859-1 are transliterated, and those for which there correspond to ISO-8859-1 are transliterated, and those for which there
is no direct mapping are replaced by a IA5 description of the glyph. is no direct mapping are replaced by a IA5 description of the glyph.
For example, should a TeletexString consist of the symbol for one-half,
this could be converted to the string
[1/2]
Client applications should avoid generating TeletexString characters If it is of the UniversalString or BMPString form, UTF-8 is used to
other than those of IA5. encode them.
If it is of the UniversalString or BMPString form, then implementations
may if they support these forms attempt to convert them to IA5.
Otherwise the encoding should be an empty string.
Subsequent documents may provide additional mechanisms for controlling
how a DirectoryString is transferred, based on alternative encoding
preferences.
5.4. Certificate 5.4. Certificate
Because of the changes from X.509(1988) and X.509(1993) and additional Because of the changes from X.509(1988) and X.509(1993) and additional
planned changes to the syntax to support certificate extensions, no planned changes to the syntax to support certificate extensions, no
string representation is defined, and values with Certificate syntax string representation is defined, and values with Certificate syntax
(userCertificate and caCertificate) are only transferred using the (userCertificate and caCertificate) are only transferred using
Binary encoding. The BNF notation in RFC 1778 for "User Certificate" a binary encoding. The BNF notation in RFC 1778 for "User Certificate"
is not permitted. is not permitted.
5.5. CertificateList 5.5. CertificateList
Because of the incompatibility of the X.509(1988) and X.509(1993) Because of the incompatibility of the X.509(1988) and X.509(1993)
definitions of revocation lists, values with CertificateList syntax definitions of revocation lists, values with CertificateList syntax
(certificateRevocationList and authorityRevocationList) are only (certificateRevocationList and authorityRevocationList) are only
transferred using the Binary encoding. The BNF notation in RFC 1778 transferred using a binary encoding. The BNF notation in RFC 1778
for "Authority Revocation List" is not permitted. for "Authority Revocation List" is not permitted.
5.6. CertificatePair 5.6. CertificatePair
Because the Certificate is being carried in binary, values with Because the Certificate is being carried in binary, values with
CertificatePair syntax (crossCertificatePair) are only transferred CertificatePair syntax (crossCertificatePair) are only transferred
using the Binary encoding. The BNF notation in RFC 1778 for using a binary encoding. The BNF notation in RFC 1778 for
"Certificate Pair" is not permitted. "Certificate Pair" is not permitted.
5.7. CountryString 5.7. CountryString
A value of CountryString syntax is encoded the same as a value of A value of CountryString syntax is encoded the same as a value of
DirectoryString syntax. DirectoryString syntax.
5.8. DN 5.8. DN
Values with DN (Distinguished Name) syntax are encoded to have the Values with DN (Distinguished Name) syntax are encoded to have the
skipping to change at line 449 skipping to change at line 445
<criteria-item> ::= [ '(' ] <attributetype> '$' <match-type> [ ')' ] <criteria-item> ::= [ '(' ] <attributetype> '$' <match-type> [ ')' ]
<match-type> ::= "EQ" | "SUBSTR" | "GE" | "LE" | "APPROX" <match-type> ::= "EQ" | "SUBSTR" | "GE" | "LE" | "APPROX"
5.13. NameAndOptionalUID 5.13. NameAndOptionalUID
The encoding of a value with the NameAndOptionalUID syntax is according The encoding of a value with the NameAndOptionalUID syntax is according
to the following BNF: to the following BNF:
<NameAndOptionalUID> ::= '(' <DistinguishedName> ')' | <NameAndOptionalUID> ::=
['('] <DistinguishedName> '#' <BitString> [')'] <DistinguishedName> [ '#' <BitString> ]
5.14. NumericString 5.14. NumericString
The encoding of a string with the NumericString syntax is the string The encoding of a string with the NumericString syntax is the string
value itself. value itself.
5.15. OID 5.15. OID
Values with OID (Object Identifier) syntax are encoded according to the Values with OID (Object Identifier) syntax are encoded according to the
following BNF: following BNF:
skipping to change at line 479 skipping to change at line 475
object descriptor, which must consist of letters and digits, starting object descriptor, which must consist of letters and digits, starting
with a letter. When encoding values with OID syntax, the first encoding with a letter. When encoding values with OID syntax, the first encoding
option should be used in preference to the second, which should be used option should be used in preference to the second, which should be used
in preference to the third wherever possible. That is, in encoding in preference to the third wherever possible. That is, in encoding
object identifiers, object descriptors (where assigned and known by object identifiers, object descriptors (where assigned and known by
the implementation) should be used in preference to numeric oids to the implementation) should be used in preference to numeric oids to
the greatest extent possible. For example, in encoding the object the greatest extent possible. For example, in encoding the object
identifier representing an organizationName, the descriptor identifier representing an organizationName, the descriptor
"organizationName" is preferable to "ds.4.10", which is in turn "organizationName" is preferable to "ds.4.10", which is in turn
preferable to the string "2.5.4.10". A list of descriptors is given preferable to the string "2.5.4.10". A list of descriptors is given
in Appendix A. in Appendix B.
5.16. Password 5.16. Password
Values with Password syntax are encoded as if they were of type Values with Password syntax are encoded as octet strings.
octetStringSyntax.
5.17. PostalAddress 5.17. PostalAddress
Values with the PostalAddress syntax are encoded according to the Values with the PostalAddress syntax are encoded according to the
following BNF: following BNF:
<postal-address> ::= <t61string> | <t61string> '$' <postal-address> <postal-address> ::= <dstring> | <dstring> '$' <postal-address>
In the above, each <t61string> component of a postal address value is In the above, each <dstring> component of a postal address value is
encoded as a value of type t61StringSyntax. encoded as a value of type DirectoryString syntax.
5.18. PresentationAddress 5.18. PresentationAddress
Values with the PresentationAddress syntax are encoded to have the Values with the PresentationAddress syntax are encoded to have the
representation described in [6]. representation described in [6].
5.19. ProtocolInformation 5.19. ProtocolInformation
A value with the ProtocolInformation syntax is encoded according to the A value with the ProtocolInformation syntax is encoded according to the
following BNF: following BNF:
skipping to change at line 526 skipping to change at line 521
<ProtocolIdentifier> ::= <oid> <ProtocolIdentifier> ::= <oid>
For example, For example,
NS+12345678 # 1.2.3.4.5 NS+12345678 # 1.2.3.4.5
5.20. TelephoneNumber 5.20. TelephoneNumber
Values with the TelephoneNumber syntax are encoded as if they were Values with the TelephoneNumber syntax are encoded as if they were
Printable String types. Printable String types. Telephone numbers are recommended in X.520 to
be in international form, e.g. "+1 512 305 0280".
5.21. TeletexTerminalIdentifier 5.21. TeletexTerminalIdentifier
Values with the TeletexTerminalIdentifier syntax are encoded according Values with the TeletexTerminalIdentifier syntax are encoded according
to the following BNF: to the following BNF:
<teletex-id> ::= <ttex-param> 0*('$' <ttx-param>) <teletex-id> ::= <ttex-param> 0*('$' <ttx-param>)
<ttx-param> ::= <ttx-key> ':' <ttx-value> <ttx-param> ::= <ttx-key> ':' <ttx-value>
skipping to change at line 556 skipping to change at line 552
5.22. TelexNumber 5.22. TelexNumber
Values with the TelexNumber syntax are encoded according to the Values with the TelexNumber syntax are encoded according to the
following BNF: following BNF:
<telex-number> ::= <actual-number> '$' <country> '$' <answerback> <telex-number> ::= <actual-number> '$' <country> '$' <answerback>
<actual-number> ::= <printablestring> <actual-number> ::= <printablestring>
<country> ::= <printablestring> <country> ::= <printablestring>
<answerback> ::= <printablestring> <answerback> ::= <printablestring>
In the above, <actual-number> is the syntactic representation of the In the above, <actual-number> is the syntactic representation of the
number portion of the TELEX number being encoded, <country> is the number portion of the TELEX number being encoded, <country> is the
TELEX country code, and <answerback> is the answerback code of a TELEX country code, and <answerback> is the answerback code of a
TELEX terminal. TELEX terminal.
5.23. UTCTime
Values with UTCTime syntax are encoded as if they were printable
strings with the strings containing a UTCTime value.
5.24. Boolean
Values with Boolean syntax are encoded according to the following
BNF:
<boolean> ::= "TRUE" | "FALSE"
Boolean values have an encoding of "TRUE" if they are logically true,
and have an encoding of "FALSE" otherwise.
6. Pilot Attribute Syntax Encodings 6. Pilot Attribute Syntax Encodings
Servers must recognize all the syntaxes described in this section.
6.1. Audio 6.1. Audio
The encoding of a value with Audio syntax is the octets of the value The encoding of a value with Audio syntax is the octets of the value
itself, a 8KHz encoding compatible with the sun 'play' utility. itself, an 8KHz uncompressed encoding compatible with the SunOS
4.1.3 'play' utility.
6.2. CaseIgnoreIA5String 6.2. CaseIgnoreIA5String
The encoding of a value with CaseIgnoreIA5String syntax is the string The encoding of a value with CaseIgnoreIA5String syntax is the string
value itself. value itself.
6.3. CaseIgnoreString 6.3. CaseIgnoreString
The encoding of a value with CaseIgnoreString syntax is the same as the The encoding of a value with CaseIgnoreString syntax is the same as the
encoding of a value with DirectoryString syntax. Note that for encoding of a value with DirectoryString syntax.
compatibility with X.500(1988) only the PrintableString and
TeletexString forms of DirectoryString should be used.
6.4. DSAQualitySyntax 6.4. DSAQualitySyntax
Values with this syntax are encoded according to the following BNF: Values with this syntax are encoded according to the following BNF:
<DsaQualitySyntax> ::= <DSAKeyword> [ '#' <description> ] <DsaQualitySyntax> ::= <DSAKeyword> [ '#' <description> ]
<DSAKeyword> ::= 'DEFUNCT' | 'EXPERIMENTAL' | 'BEST-EFFORT' | <DSAKeyword> ::= 'DEFUNCT' | 'EXPERIMENTAL' | 'BEST-EFFORT' |
'PILOT-SERVICE' | 'FULL-SERVICE' 'PILOT-SERVICE' | 'FULL-SERVICE'
skipping to change at line 650 skipping to change at line 662
In the above, <mailbox-type> represents the type of mail system in In the above, <mailbox-type> represents the type of mail system in
which the mailbox resides, for example "MCIMail"; and <mailbox> is the which the mailbox resides, for example "MCIMail"; and <mailbox> is the
actual mailbox in the mail system defined by <mailbox-type>. actual mailbox in the mail system defined by <mailbox-type>.
6.10. Fax 6.10. Fax
Values with Fax syntax are encoded as if they were octet strings Values with Fax syntax are encoded as if they were octet strings
containing Group 3 Fax images as defined in [7]. containing Group 3 Fax images as defined in [7].
6.11. UTCTime 6.11. CaseIgnoreList
Values with UTCTime syntax are encoded as if they were printable
strings with the strings containing a UTCTime value.
6.12. OctetString
The encoding of a value with OctetString syntax is the string
value itself.
6.13. T61String
The encoding of a value with T61String syntax is the string value
itself.
6.14. CaseIgnoreList
Values with CaseIgnoreList syntax are encoded according to the Values with CaseIgnoreList syntax are encoded according to the
following BNF: following BNF:
<caseignorelist> ::= <caseignorestring> | <caseignorelist> ::= <caseignorestring> |
<caseignorestring> '$' <caseignorelist> <caseignorestring> '$' <caseignorelist>
<caseignorestring> ::= a string encoded according to the rules for <caseignorestring> ::= a string encoded according to the rules for
DirectoryString as above. DirectoryString as above.
6.15. CaseExactList 6.12. CaseExactList
Values with CaseExactList syntax are encoded according to the Values with CaseExactList syntax are encoded according to the
following BNF: following BNF:
<caseexactlist> ::= <caseexactstring> | <caseexactlist> ::= <caseexactstring> |
<caseexactstring> '$' <caseexactlist> <caseexactstring> '$' <caseexactlist>
<caseexactstring> ::= a string encoded according to the rules for <caseexactstring> ::= a string encoded according to the rules for
DirectoryString as above. DirectoryString as above.
6.16. Boolean 7. Standard Operational Attribute Syntax Encodings
Values with Boolean syntax are encoded according to the following All servers must recognize the syntaxes of AttributeTypeDescription,
BNF: GeneralizedTime, INTEGER, and ObjectClassDescription.
<boolean> ::= "TRUE" | "FALSE" In these syntax definitions the following productions should be used:
Boolean values have an encoding of "TRUE" if they are logically true, <DirectoryStrings> ::= <DirectoryString> | '(' <DirectoryStringList> ')'
and have an encoding of "FALSE" otherwise.
7. Standard Operational Attribute Syntax Encodings <DirectoryStringList> ::= <DirectoryStringList> <DirectoryString> | ""
<DirectoryString> ::= ''' <dstring> '''
<oids> ::= <oid> | '(' <oidlist> ')'
<oidlist> ::= <oidlist> '$' <oid> | <oid>
7.1. ACIItem 7.1. ACIItem
This syntax appears too complicated for a compact string representation This syntax appears too complicated for a compact string representation
be useful. Thus syntax will use the the binary encoding, which be useful. Thus syntax will use the the binary encoding, which
contains a BER encoding of the value. It is recommended that clients contains a BER encoding of the value. It is recommended that clients
that wish to only determine whether they have been granted permission that wish to only determine whether they have been granted permission
to modify an entry use the modifyRightsReq field in the SearchRequest, to modify an entry use the modifyRightsReq field in the SearchRequest,
rather than attempt to parse this syntax. rather than attempt to parse this syntax.
skipping to change at line 730 skipping to change at line 731
<SetOfProtocolInformation> ::= <ProtocolInformation> | <SetOfProtocolInformation> ::= <ProtocolInformation> |
'(' <ProtocolInformationList> ')' '(' <ProtocolInformationList> ')'
<ProtocolInformationList> ::= <ProtocolInformation> | <ProtocolInformationList> ::= <ProtocolInformation> |
<ProtocolInformation> '$' <ProtocolInformation> '$'
<ProtocolInformationList> <ProtocolInformationList>
7.3. AttributeTypeDescription 7.3. AttributeTypeDescription
No printable representation is defined, this syntax uses the binary Values with this syntax are encoded according to the following BNF:
encoding which contains a BER encoding of the value.
<AttributeTypeDescription> ::= "("
<oid> -- AttributeType identifier
[ "NAME" <DirectoryStrings> ]
[ "DESC" <DirectoryString> ]
[ "OBSOLETE" ]
[ "SUP" <oid> ] -- derived from this AttributeType
[ "EQUALITY" <oid> ] -- MatchingRule
[ "ORDERING" <oid> ] -- MatchingRule
[ "SUBSTR" <oid> ] -- MatchingRule
[ "SYNTAX" <DirectoryString> ]
[ "SINGLE-VALUE" ] -- default multi-valued
[ "COLLECTIVE" ] -- default not collective
[ "NO-USER-MODIFICATION" ] -- default user modifiable
[ "USAGE" <AttributeUsage> ] -- default user applications
")"
<AttributeUsage> ::=
"userApplications"
| "directoryOperation"
| "distributedOperation" -- DSA-shared
| "dSAOperation" -- DSA-specific
For example,
( 2.5.4.0 NAME 'objectClass' SYNTAX 'OID' )
7.4. DITContentRuleDescription 7.4. DITContentRuleDescription
No printable representation is defined, this syntax uses the binary Values with this syntax are encoded according to the following BNF:
encoding which contains a BER encoding of the value.
<DITContentRuleDescription> ::= "("
<oid> -- Structural ObjectClass identifier
[ "NAME" <DirectoryStrings> ]
[ "DESC" <DirectoryString> ]
[ "OBSOLETE" ]
[ "AUX" <oids> ] -- Auxiliary ObjectClasses
[ "MUST" <oids> ] -- AttributeType identifiers
[ "MAY" <oids> ] -- AttributeType identifiers
[ "NOT" <oids> ] -- AttributeType identifiers
")"
7.5. DITStructureRuleDescription 7.5. DITStructureRuleDescription
No printable representation is defined, this syntax uses the binary Values with this syntax are encoded according to the following BNF:
encoding which contains a BER encoding of the value.
<DITStructureRuleDescription> ::= "("
<RuleIdentifier> -- DITStructureRule identifier
[ "NAME" <DirectoryStrings> ]
[ "DESC" <DirectoryString> ]
[ "OBSOLETE" ]
"FORM" <oid> -- NameForm
[ "SUP" <RuleIdentifiers> ] -- superior DITStructureRules
")"
<RuleIdentifier> ::= <integer>
<RuleIdentifiers> ::=
<RuleIdentifier>
|
"(" <RuleIdentifierList> ")"
<RuleIdentifierList> ::=
<RuleIdentifierList> <RuleIdentifier>
|
-- empty list
7.6. DSEType 7.6. DSEType
Values with DSEType syntax are encoded according to the following BNF: Values with DSEType syntax are encoded according to the following BNF:
<DSEType> ::= '(' <DSEBitList> ')' <DSEType> ::= '(' <DSEBitList> ')'
<DSEBitList> ::= <DSEBit> | <DSEBit> '$' <DSEBitList> <DSEBitList> ::= <DSEBit> | <DSEBit> '$' <DSEBitList>
<DSEBit> ::= 'root' | 'glue' | 'cp' | 'entry' | 'alias' | 'subr' | <DSEBit> ::= 'root' | 'glue' | 'cp' | 'entry' | 'alias' | 'subr' |
skipping to change at line 787 skipping to change at line 843
<MasterAndShadowAccessPointList> ::= <MasterOrShadowAccessPoint> | <MasterAndShadowAccessPointList> ::= <MasterOrShadowAccessPoint> |
<MasterOrShadowAccessPoint> '$' <MasterAndShadowAccessPointList> <MasterOrShadowAccessPoint> '$' <MasterAndShadowAccessPointList>
<MasterOrShadowAccessPoint> ::= <category> '#' <AccessPoint93> <MasterOrShadowAccessPoint> ::= <category> '#' <AccessPoint93>
<category> ::= 'master' | 'shadow' <category> ::= 'master' | 'shadow'
7.10. MatchingRuleDescription 7.10. MatchingRuleDescription
No printable representation is defined, this syntax uses the binary Values of this syntax are encoded according to the following BNF:
encoding which contains a BER encoding of the value.
<MatchingRuleDescription> ::= "("
<oid> -- MatchingRule identifier
[ "NAME" <DirectoryStrings> ]
[ "DESC" <DirectoryString> ]
[ "OBSOLETE" ]
"SYNTAX" <DirectoryString>
")"
7.11. MatchingRuleUseDescription 7.11. MatchingRuleUseDescription
No printable representation is defined, this syntax uses the binary Values of this syntax are encoded according to the following BNF:
encoding which contains a BER encoding of the value.
<MatchingRuleUseDescription> ::= "("
<oid> -- MatchingRule identifier
[ "NAME" <DirectoryStrings> ]
[ "DESC" <DirectoryString> ]
[ "OBSOLETE" ]
"APPLIES" <oids> -- AttributeType identifiers
")"
7.12. NameFormDescription 7.12. NameFormDescription
No printable representation is defined, this syntax uses the binary Values of this syntax are encoded according to the following BNF:
encoding which contains a BER encoding of the value.
<NameFormDescription> ::= "("
<oid> -- NameForm identifier
[ "NAME" <DirectoryStrings> ]
[ "DESC" <DirectoryString> ]
[ "OBSOLETE" ]
"OC" <oid> -- Structural ObjectClass
"MUST" <oids> -- AttributeTypes
[ "MAY" <oids> ] -- AttributeTypes
")"
7.13. ObjectClassDescription 7.13. ObjectClassDescription
No printable representation is defined, this syntax uses the binary Values of this syntax are encoded according to the following BNF:
encoding which contains a BER encoding of the value.
<ObjectClassDescription> ::= "("
<oid> -- ObjectClass identifier
[ "NAME" <DirectoryStrings> ]
[ "DESC" <DirectoryString> ]
[ "OBSOLETE" ]
[ "SUP" <oids> ] -- Superior ObjectClasses
[ ( "ABSTRACT" | "STRUCTURAL" | "AUXILIARY" ) ] -- default structural
[ "MUST" <oids> ] -- AttributeTypes
[ "MAY" <oids> ] -- AttributeTypes
")"
7.14. SubtreeSpecification 7.14. SubtreeSpecification
Values of this syntax are encoded according to the following BNF: Values of this syntax are encoded according to the following BNF:
<SubtreeSpecification> ::= '(' [<localname>] '#' <SubtreeSpecification> ::= '(' [<localname>] '#'
[<exclusionlist>] '#' [<exclusionlist>] '#'
[<minimum>] '#' [<maximum>] '#' [<minimum>] '#' [<maximum>] '#'
[<refinement>] ')' [<refinement>] ')'
skipping to change at line 898 skipping to change at line 988
Mark Wahl Mark Wahl
ISODE Consortium Inc. ISODE Consortium Inc.
3925 West Braker Lane, Suite 333 3925 West Braker Lane, Suite 333
Austin, TX 78759 Austin, TX 78759
USA USA
Phone: +1 512-305-0280 Phone: +1 512-305-0280
EMail: M.Wahl@isode.com EMail: M.Wahl@isode.com
Andy Coulbeck Andy Coulbeck
ISODE Consortium Ltd. ISODE Consortium
The Dome, The Square The Dome, The Square
Richmond TW9 1DT Richmond TW9 1DT
United Kingdom United Kingdom
Phone: +44 181-332-9091 Phone: +44 181-332-9091
EMail: A.Coulbeck@isode.com EMail: A.Coulbeck@isode.com
Tim Howes Tim Howes
University of Michigan Netscape Communications Corp.
ITD Research Systems 685 Middlefield
535 W William St. Mountain View, CA 94043
Ann Arbor, MI 48103-4943
USA USA
Phone: +1 313 747-4454 Phone: +1 415 254-1900
EMail: tim@umich.edu EMail: howes@netscape.com
Steve Kille Steve Kille
ISODE Consortium ISODE Consortium
The Dome, The Square The Dome, The Square
Richmond Richmond
TW9 1DT TW9 1DT
UK UK
Phone: +44-181-332-9091 Phone: +44-181-332-9091
EMail: S.Kille@isode.com EMail: S.Kille@isode.com
11. Bibliography 11. Bibliography
[1] M.Wahl, W. Yeong, T. Howes, S. Kille, "Lightweight Directory Access [1] M.Wahl, W. Yeong, T. Howes, S. Kille, "Lightweight Directory Access
Protocol (Version 3)". <draft-ietf-asid-ldapv3-protocol-00.txt> Protocol (Version 3)". <draft-ietf-asid-ldapv3-protocol-03.txt>
[2] The Directory: Selected Attribute Types. ITU-T Recommendation [2] The Directory: Selected Attribute Types. ITU-T Recommendation
X.520, 1993. X.520, 1993.
[3] The Directory: Models. ITU-T Recommendation X.501, 1993. [3] The Directory: Models. ITU-T Recommendation X.501, 1993.
[4] P. Barker, S. Kille, "The COSINE and Internet X.500 Schema", RFC [4] P. Barker, S. Kille, "The COSINE and Internet X.500 Schema", RFC
1274, November 1991. 1274, November 1991.
[5] Kille, S., "A String Representation of Distinguished Names", RFC [5] Kille, S., "A String Representation of Distinguished Names", RFC
skipping to change at line 952 skipping to change at line 1040
[6] Kille, S., "A String Representation for Presentation Addresses", [6] Kille, S., "A String Representation for Presentation Addresses",
RFC 1278, University College London, November 1991. RFC 1278, University College London, November 1991.
[7] Terminal Equipment and Protocols for Telematic Services - [7] Terminal Equipment and Protocols for Telematic Services -
Standardization of Group 3 facsimile apparatus for document Standardization of Group 3 facsimile apparatus for document
transmission. CCITT, Recommendation T.4. transmission. CCITT, Recommendation T.4.
[8] JPEG File Interchange Format (Version 1.02). Eric Hamilton, C- [8] JPEG File Interchange Format (Version 1.02). Eric Hamilton, C-
Cube Microsystems, Milpitas, CA, September 1, 1992. Cube Microsystems, Milpitas, CA, September 1, 1992.
Appendix A- Permitted OID descriptors Appendix A- Object Classes
Attribute type names listed above may be used as descriptions for OIDs,
as well as the following.
A.1. Object classes
Descriptor Value Descriptor X.500 OID Value
============================== =========================== ============================== ===========================
top 2.5.6.0 top 2.5.6.0
alias 2.5.6.1 alias 2.5.6.1
country 2.5.6.2 country 2.5.6.2
locality 2.5.6.3 locality 2.5.6.3
organization 2.5.6.4 organization 2.5.6.4
organizationalUnit 2.5.6.5 organizationalUnit 2.5.6.5
person 2.5.6.6 person 2.5.6.6
organizationalPerson 2.5.6.7 organizationalPerson 2.5.6.7
organizationalRole 2.5.6.8 organizationalRole 2.5.6.8
skipping to change at line 995 skipping to change at line 1078
domain 0.9.2342.19200300.100.4.13 domain 0.9.2342.19200300.100.4.13
rFC822localPart 0.9.2342.19200300.100.4.14 rFC822localPart 0.9.2342.19200300.100.4.14
dNSDomain 0.9.2342.19200300.100.4.15 dNSDomain 0.9.2342.19200300.100.4.15
domainRelatedObject 0.9.2342.19200300.100.4.17 domainRelatedObject 0.9.2342.19200300.100.4.17
friendlyCountry 0.9.2342.19200300.100.4.18 friendlyCountry 0.9.2342.19200300.100.4.18
simpleSecurityObject 0.9.2342.19200300.100.4.19 simpleSecurityObject 0.9.2342.19200300.100.4.19
pilotOrganization 0.9.2342.19200300.100.4.20 pilotOrganization 0.9.2342.19200300.100.4.20
pilotDSA 0.9.2342.19200300.100.4.21 pilotDSA 0.9.2342.19200300.100.4.21
qualityLabelledData 0.9.2342.19200300.100.4.23 qualityLabelledData 0.9.2342.19200300.100.4.23
A.2. Other descriptors Appendix B. - Other OID descriptors
In addition, servers should recognize at the minimum the following In addition, servers should recognize at the minimum the following
descriptors as prefixes of other OIDs, e.g. "enterprises.453.13.3". descriptors as prefixes of other OIDs, e.g. "enterprises.453.13.3".
Clients should attempt to ensure that any OIDs they transmit are in Clients should attempt to ensure that any OIDs they transmit are in
terms of only these descriptors, with additional components in numeric terms of only these descriptors, with additional components in numeric
form. form.
Descriptor Value Descriptor Value
============================== =========================== ============================== ===========================
ccitt 0 ccitt 0
iso 1 iso 1
joint 2 joint 2
memberBody 1.2
ansi 1.2.840
identifiedOrganization 1.3 identifiedOrganization 1.3
dod 1.3.6 dod 1.3.6
internet 1.3.6.1 internet 1.3.6.1
private 1.3.6.1.4 private 1.3.6.1.4
enterprises 1.3.6.1.4.1 enterprises 1.3.6.1.4.1
ds 2.5
standardObjectClass 2.5.6 <draft-ietf-asid-ldapv3-attributes-01.txt> Expires: December 5, 1996
 End of changes. 76 change blocks. 
141 lines changed or deleted 220 lines changed or added

This html diff was produced by rfcdiff 1.33. The latest version is available from http://tools.ietf.org/tools/rfcdiff/