[Date Prev][Date Next] [Chronological] [Thread] [Top]

Re: DC/UID



These are defined in several RFCs. We might as well put them in the LDAP core RFCs as you suggest.

-Mark Smith
Netscape


Kurt D. Zeilenga wrote:

RFC 2253 included DC (domainComponent) and UID (userid) in the
list of attribute types which are be recognized in DNs, but
did not provide a reference to where these attributes are defined.
The most obvious reference would be RFC 1274.

To avoid adding a reference to RFC 1274 and possible other RFCs,
I suggest the specifications for DC and UID be directly incorporated
into draft-ietf-ldapbis-user-schema.

X.Y. dc

The DC (domainComponent) attribute type specifies one
component of a domain name. For example, "example" or "com".
(Source: RFC 1274)
( 0.9.2342.19200300.100.1.25 NAME 'dc'
EQUALITY caseIgnoreIA5Match
SUBSTR caseIgnoreIA5SubstringsMatch
SYNTAX 1.3.6.1.4.1.1466.115.121.1.26 SINGLE-VALUE )


X.Z. uid

The uid (userid) attribute type specifies a computer system
login name. (Source: RFC 1274)
( 0.9.2342.19200300.100.1.1
NAME ( 'uid' 'userid' )
EQUALITY caseIgnoreMatch
SUBSTR caseIgnoreSubstringsMatch
SYNTAX 1.3.6.1.4.1.1466.115.121.1.15{256} )



This will also require adding a description for the caseIgnoreIA5SubstringsMatch rule to draft-ietf-ldapbis-syntax:

   ( 1.3.6.1.4.1.1466.109.114.3
	 NAME 'caseIgnoreIA5SubstringsMatch'
       SYNTAX 1.3.6.1.4.1.1466.115.121.1.58 )

comments?

Kurt