RE: SACRED Protocol

"Eamon O'Tuathail" <[email protected]> Thu, 22 Nov 2001 10:20:13 -0000
Newsgroups gmane.ietf.sacred
Message-ID <000001c1733f$47c792c0$56c8fea9@central>

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