Re: [dhcwg] LDAP Schema for DHCP

On Nov 19, 2003, at 5:46 PM, Barr Hibbs wrote:
> so before over specifying an LDAP schema, one probably should define 
> the
> problem space a bit taking into account actual usage patterns that 
> would
> have to be accommodated, rather than just devising something in the 
> abstract
> that might not be implementable.

On the other hand, there's no technical reason why an LDAP server can't 
handle 3k updates per second - it's just a stereotype that LDAP servers 
can't do that.   I don't even know if it's still true.   So if what's 
desired is to keep a complete lease record in LDAP, or if that's one 
part of an LDAP schema that can also be used just for configuration 
information, I think it's fine.

The real question is, is this actually something that people want?   If 
not, why not wait until people want it?   If so, do people want the 
whole thing, or just configuration information?   If they just want 
configuration information, why not define that schema now but leave 
room to add more later?

As to Bernie's point, I think you can make the case that conditional 
behavior is something that can be thought of as separate from actual 
configuration, and there are ways to write the LDAP schema so that it 
provides support for whatever conditional behavior the server offers, 
without actually encoding that behavior - that is, you don't have to 
stuff the ISC config language, python code, or whatever into the LDAP 
database - just the objects that that code manipulates.

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