Re: Core draft last call update.

["Andersson, Mats" <mats.andersson%appgate.com@localhost>]

On Fri, 8 Mar 2002, Bill Sommerfeld wrote:
> > Maybe I'm missing something,  but I can't see the need to disconnect in this
> > case,  as opposed to simply discarding these messages.  
> 
> I don't think think it's that simple.  Have you actually prototyped
> this?  
> 
> Many of these message types are ones for which the client expects a
> response -- simply discarding such requests on the server will confuse
> and/or hang clients which were expecting responses.
> 
> Any implementors want to comment on this in more detail?

I can't see a big win in discard versus disconnect (especially since we
are in last-call now, considering the earlier comments on last minute
changes to the drafts...). Disconnect seems safer and easier to handle
from a protocol-perspective. If you want to optimistally assume the
authentication goes well and start higher-level traffic based on this
assumption it is better to handle this by queueing this traffic until the
authentication stage is done. There would be a marginal performance win of
course, however the complexity in handling potentially discarded messages
seems a high price for this. Since the whole transport setup and
authentication stages are pretty slimmed down anyway, this wouldn't add
much IMHO.

Cheers,

/Mats