Subject: [BXXPwg] SOAP over BEEP

From: "Eamon O'Tuathail" <[email-masked]>
Date: Fri, 15 Jun 2001 21:29:36 +0100

>> >	beep:			beep over tcp
>> >	beeps:		beep over ssl
>> >	beepsc:		beep over sctp
>>  Please don't do this.

I agree - we should not be combining the names like that.

We need a solution that will work robustly with, say, a couple of dozen
transport mappings and thousands of profiles.

RFC3081 will be the most popular transport mapping by far, so I agree with
the idea of defaulting "beep.tcp" to just "beep", but permitting use  of
"beep.tcp" and "beep.<any-transport-mapping-shortname>".

Eamon

_______________________________________________
BXXPwg mailing list
[email-masked]
http://lists.invisible.net/mailman/listinfo/bxxpwg