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

Re: object class 'alias'

To: Harald Alvestrand <Harald@Alvestrand.no>
Subject: Re: object class 'alias'
From: "Kurt D. Zeilenga" <Kurt@OpenLDAP.Org>
Date: Wed, 14 Jul 1999 08:21:08 -0700
Cc: Mark Wahl <M.Wahl@INNOSOFT.COM>, Bruce Greenblatt <bgreenblatt@dtasi.com>, ietf-ldapext@netscape.com
In-reply-to: <4.2.0.56.19990713173502.00dca100@dokka.maxware.no>
References: <18738.931782801@threadgill.austin.innosoft.com>
Resent-date: Wed, 14 Jul 1999 08:20:47 -0700 (PDT)
Resent-from: ietf-ldapext@netscape.com
Resent-message-id: <"KxigU.A.GgC.EpKj3"@glacier>
Resent-sender: ietf-ldapext-request@netscape.com

At 05:35 PM 7/13/99 +0200, Harald Alvestrand wrote:
>At 07:33 12.07.99 -0500, Mark Wahl wrote:
>
>>My mistake in 2252: alias is not abstract.  Thanks for finding this , Kurt.
>>In the next release section 4.4 will read
>>
>>    In general every entry will contain an abstract class ("top"),
>>    at least one structural object class, and zero or more auxiliary
>>    object classes.
>
>Does this mean that all objects of type "alias" are also of type "top"?

Yes, rfc2256:
	( 2.5.6.1 NAME 'alias' SUP top STRUCTURAL MUST aliasedObjectName )

Follow-Ups:
- Re: object class 'alias'
  - From: Harald Alvestrand <Harald@Alvestrand.no>

References:
- Re: object class 'alias'
  - From: Mark Wahl <M.Wahl@INNOSOFT.COM>
- Re: object class 'alias'
  - From: Harald Alvestrand <Harald@Alvestrand.no>

Prev by Date: RE: Ignore ing
Next by Date: Re: object class 'alias'
Index(es):
- Chronological
- Thread