[Ietf-not43] Re: Requirement 3.1.8

[Eric A. Hall]

on 8/18/2003 11:14 AM Andrew Newton wrote:

>>> #2 - The implementation of 3.1.8.
>>> 
>>> There was mention of 3.1.8 in the meeting by Peter, but I do not
>>> see it addressed in the drafts.  Looking through the jabber logs,
>>> Peter proposed various methods to do this.  These were defined as:
>>> using the bind operation, special policy entries, and server-side
>>> extended operations.
>> 
>> However, if folks want to go ahead and start working on this, we
>> certainly can. I'd like to get a better analysis on the objective
>> first though. Are we wanting to provide something like a counter ("50
>> out of 50 possible queries already performed, try back tomorrow"), a
>> simple tooManyQueries response, or an array of different responses?
> 
> I don't quite follow this.  It sounds like you are talking about the 
> first part of 3.2.5., which is something that is already defined in 
> stock LDAP (I think).

3.2.5 talks about maximum results in queries, while my understanding of
this particular issue is that it is related to the ability to issue any
queries at all, possibly because of rate-limited (too many queries today
alredy), or possibly because of some other requirements.

The general cases are already defined as bind errors (unwillingToPerform
essentially means "just go away"). I'm trying to get a handle on exactly
what kind of limits we are trying to express so that I can describe them
properly. So, is 3.1.8 specifically about fixed query volume (try again
after HH:MM UCT), the query interval rate (wait five minutes), both of
these, something else, or what?

-- 
Eric A. Hall                                        http://www.ehsco.com/
Internet Core Protocols          http://www.oreilly.com/catalog/coreprot/