Re: coments on draft-ietf-sacred-protocol-bss-00

Bob,

> Typical scenarios for other protocols that use authorization ID are
> administrator access and proxy/middle-tier access.  

Do we have such requirements? Where in 3157 is that mentioned?

> Just because some folks wouldn't use them
> doesn't mean these scenarios should be forbidden.

I'm in "if its not needed, leave it out" mode at the moment:-)

> [...] an example of the
> additional things that have to be reinvented at the application level if
> the unwise course of defining SASL in this protocol is pursued.  Using
> BEEP gives you language about handling authorization ID and error codes
> for free.

Feel free to comment on that in the separate thread "sasl in beep 
or payload",

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