Re: BEEP adjustments [was: Re: I-D ACTION:draft-ietf-sacred-protocol-bss-01.txt]

> while a listener should certainly have an idle timeout, it's rather
> presumptuous on the part of the listener to handle one request and then
> exit.

For many protocols that's true I guess. However, since we're just 
handling (almost always) credential downloads I'd have thought it 
was just the right behaviour.

However, if you're saying that BEEP makes this a non-issue since
both sides should gracefully terminate (even if one times out),
then I guess I can buy not being so prescriptive. 

So - if no-one wants to keep 2.4 (or similar language), I'll delete 
it, but will add something about avoiding DoS (listener having a 
timeout etc) to the security considerations section. (That text
must nearly be boilerplate by now - anyone know where I can lift
it from?)

Stephen.

-- 
____________________________________________________________
Stephen Farrell         				   
Baltimore Technologies,   tel: (direct line) +353 1 881 6716
39 Parkgate Street,                     fax: +353 1 881 7000
Dublin 8.                mailto:[email protected]
Ireland                             http://www.baltimore.com