On 10/13/2011 10:21 AM, Claus Assmann wrote:
It would be nice to have a standard for a server to tell a client
which restrictions it triggered, what the limits are, and what it
should do to avoid this from happening again. For example:
What client implementors will add this to their code? What server implementers
will add this to their code? What sysadmins will configure to use this?
Why?
What's your empirical basis for making these claims?
In other words, no matter how nice this all sounds -- and I happen to agree that
it does sound nice -- it's /very/ expensive to add to the infrastructure and it
needs a good indication that it will be adopted. Where is the market 'pull' for
the benefits this will provide?
d/
--
Dave Crocker
Brandenburg InternetWorking
bbiw.net