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

Re: I-D ACTION:draft-mmeredit-rootdse-vendor-info-00.txt

To: Mark Smith <mcs@netscape.com>
Subject: Re: I-D ACTION:draft-mmeredit-rootdse-vendor-info-00.txt
From: "Kurt D. Zeilenga" <kurt@boolean.net>
Date: Fri, 19 Nov 1999 07:26:37 -0800
Cc: Peter Strong <pestrong@nortelnetworks.com>, "Paul Leach (Exchange)" <paulle@Exchange.Microsoft.com>, Mark Meredith <MMEREDIT@novell.com>, ietf-ldapext <ietf-ldapext@netscape.com>
In-reply-to: <383564D0.41C8281F@netscape.com>
References: <006701bf329a$186d9390$3750fb8d@net-pstrong.corpnorth.baynetworks.com>
Resent-date: Fri, 19 Nov 1999 07:28:48 -0800 (PST)
Resent-from: ietf-ldapext@netscape.com
Resent-message-id: <"vo43tD.A.iK.myWN4"@glacier>
Resent-sender: ietf-ldapext-request@netscape.com

I'm thinking we just need to define an operational attribute for the
root DSE:

supportedFeature
   
   The values of this attribute are OBJECT IDENTIFIERs identifying the
   supported optional or vendor-defined features which the server supports.
   
    ( supportedFeatureOID NAME 'supportedFeature'
     SYNTAX 1.3.6.1.4.1.1466.115.121.1.38 USAGE dSAOperation )

The key is that it lists features directly and eliminates the
need to maintain out of band feature lists for each vendor version.

Kurt


----
Kurt D. Zeilenga		<kurt@boolean.net>
Net Boolean Incorporated	<http://www.boolean.net/>

Follow-Ups:
- Re: I-D ACTION:draft-mmeredit-rootdse-vendor-info-00.txt
  - From: "Kurt D. Zeilenga" <kurt@boolean.net>

References:
- RE: I-D ACTION:draft-mmeredit-rootdse-vendor-info-00.txt
  - From: Peter Strong <pestrong@nortelnetworks.com>
- Re: I-D ACTION:draft-mmeredit-rootdse-vendor-info-00.txt
  - From: Mark Smith <mcs@netscape.com>

Prev by Date: Re: I-D ACTION:draft-mmeredit-rootdse-vendor-info-00.txt
Next by Date: Re: LDAPsubentry
Index(es):
- Chronological
- Thread