[BEEPwg] SASL server response to <blob status='abort'/>

Marshall Rose mrose at dbc.mtview.ca.us
Mon Aug 30 12:03:18 PDT 2004


On Aug 30, 2004, at 09:32, james woodyatt wrote:

> I suggest that, when we revise the specification for consideration as 
> a draft standard (or whatever the new IETF standards process is when 
> we do the next revision), we should amend the following language in 
> section 4.1.3 to more clearly describe the use of the 'complete' 
> status attribute value:
>
>       complete: used by a server to indicate that the exchange is
>          complete and successful;
>
> It should probably read:
>
>       complete: used by a server to indicate that the exchange is
>          complete with the result that a user is either
>          successfully authenticated or the exchange has been
>          aborted by the client;
>
> The implication is that a <blob status='complete'> element does *not* 
> signal a tuning reset when the client has requested to abort the 
> exchange.  I wish that were more clear in the specification.

i agree.

/mtr



More information about the BEEPwg mailing list