[BXXPwg] SOAP over BEEP

Eamon O'Tuathail eamon.otuathail@clipcode.com
Fri, 15 Jun 2001 22:26:52 +0100


>> The vector that I thought needed to be dealt with is the underlying
>> transport mapping.  Let's leave it at TCP and SCTP and ignore SSL for
>> now then.  The question stands.

If we are only ever going to have two transport mappings, I would agree,
but what happens when (not if) we have twenty transport mappings (over the
next
ten years). RFC 3080 is careful to separate out the transport mapping from
the BEEP core, we really need to follow this good practice with the URI.