Re: sasl in beep or payload

Hi Dave,

Dave Crocker wrote:
> 
> At 02:42 PM 12/19/2001 +0000, Stephen Farrell wrote:
> >I agree with Keith and since no-one else seems to be arguing for
> >sticking with the sasl-in-beep approach, I'll push those up to
> >the payload in the next version.
> 
> I beg your pardon?  

Granted:-)

> It appears that you have been participating in a very
> different discussion than I have.

Well, I don't think so. A week ago I posted [1], and only Marshall (and 
now you) seemed to differ from that. If others do, then I'd have hoped 
they'd have spoken up by now. (I'll also note that has been no comment 
at all on the draft minutes [2], which contain similar details of the 
strawpoll we held at the meeting.)

> The one I have been participating in had some vigorous proponents for using
> the sasl mechanism in beep, rather than expending the effort to create its
> integration with sacred.

Actually, most of the vigour has been related to http vs beep, from
my reading of the meeting and subsequent mail.

> In fact I seem to recall a presentation that argued for this re-use.

Yes (and I liked your presentaion btw). There was also another one 
(Magnus') calling for a quite different approach.

> Please note that if the working group takes the very strong AD guidance to
> choose a single "transport" then there is no reason at all to create sasl
> integration into the application, unless the working group chooses a
> "transport" that does not already supply that functionality.

I have some sympathy for this myself, but judging by the raised
hands, the consensus amongst those who'd implement sacred was to
include the sasl pdus in the payload.

Stephen.

[1] http://www.imc.org/ietf-sacred/mail-archive/msg00362.html
[2] http://www.imc.org/ietf-sacred/mail-archive/msg00363.html


-- 
____________________________________________________________
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