Re: sacred again

> Now that I've found the expired SASL SRP draft (I found it at
> http://www.forge.com.au/products/Papers/Secure_Remote_Password.htm),
> and re-read rfc2222, I tend to agree with you and Bob. The sasl-srp
> draft does include a security layer.

Glad to hear it.

> So - in the (probably likely;-) absence of further inputs, I'll try to
> draft up a protocol with beep+sasl+sasl-srp+sacred-messages-in-xml and
> we can then see whether it meets the requirements in rfc3157.

I would think of this in two parts:

 * how to carry SACRED messages in BEEP

 * a "profile" of the SASL-SRP mechanism with enough defined to make
   interoperability likely for SACRED purposes

 - RL "Bob"