RE: SACRED Protocol

When I referred to transport protocols, I meant the messaging frameworks
such as SOAP or BEEP.  It is true that BEEP can run on top of different
transport protocols but the issue I was raising was that the current SAML
draft seems to blur the distinction between these frameworks and the
authentication protocols such as SASL.

Sorry for the misunderstanding.

> -----Original Message-----
> From: [email protected]
> [mailto:[email protected]]On Behalf Of Eamon O'Tuathail
> Sent: 22 November 2001 10:20
> To: 'Gareth Richards'; [email protected]
> Subject: RE: SACRED Protocol
>
>
>
>
> BEEP is designed so that it can run across multiple transports, based on
> a transport mapping (section 2.5 of RFC 3080).
>
> RFC3081 defines one transport mapping to TCP, and similar mappings are
> possible for other transports (e.g. SCTP).
>
> Hence, SACRED over BEEP is transport-independent. It can work with any
> transport mapping defined under BEEP.
>
> Eamon O'Tuathail
> http://www.clipcode.com
>
>
>