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

Re: [ldapext] objectIdentifierMatch

To: Howard Chu <hyc@highlandsun.com>
Subject: Re: [ldapext] objectIdentifierMatch
From: "Kurt D. Zeilenga" <Kurt@OpenLDAP.org>
Date: Sun, 08 Oct 2006 15:47:36 +0200
Cc: Ldapext <ldapext@ietf.org>
In-reply-to: <4526A2DD.1070001@highlandsun.com>
References: <4526A2DD.1070001@highlandsun.com>

At 04:39 AM 10/7/2006, Howard Chu wrote:
>RFC4512 and RFC4517  allow OIDs to be either numeric or short-name descriptors, but the objectIdentifierMatch and objectIdentifierFirstComponentMatch matching rules have no way to determine in what context a descriptor resides.

For operational attributes, the context is implicit.

>That makes it pretty much impossible to validate these descriptors in arbitrary attributes.

For user application attributes, it is not possible for the server
to know what the context is without some additional information
I think it reasonable to provide this information in an attribute
type description extension as you propose.

Kurt 

_______________________________________________
Ldapext mailing list
Ldapext@ietf.org
https://www1.ietf.org/mailman/listinfo/ldapext

References:
- [ldapext] objectIdentifierMatch
  - From: Howard Chu <hyc@highlandsun.com>

Prev by Date: [ldapext] objectIdentifierMatch
Next by Date: Re: [ldapext] objectIdentifierMatch
Index(es):
- Chronological
- Thread