Re: [jdev] XMPP Ping method?
On Wednesday 01 November 2006 9:17 am, Peter Saint-Andre wrote: > Justin Karneges wrote: > > This seems unlikely > > though, as I think the RFC revision has already been made, and there was > > no consideration for these features. > > It is not accurate to say that "the RFC revision has already been made". > I published -00 versions of rfc3920bis and rfc3921bis, but that is the > start of discussion, not the end. Well let's test the waters. :) I've put together some RFC text that unifies the acking mechanisms proposed by myself and Dave Cridland. I'll post it to standards-jig. -Justin
Re: [jdev] Re: XMPP Ping method?
Hi Dave! Dave Cridland schrieb: > I don't think it's a solution, as such, and the multi-homing/mobility > capabilities that have been mentioned exist in several forms at the IP > layer, such as MIP6, and perhaps most interestingly HIP. Yes, MIP6 is what I meant, when I said, that you get mobility automatically if you use a full IPv6 inmplementation. ... and the nice thing about it: We have already servers that support IPv6 ... therefore we already support mobility, it's just that you have to enable MIP6 on the client's operating system. Tot kijk Matthias -- Matthias Wimmer Fon +49-700 77 00 77 70 Züricher Str. 243Fax +49-89 95 89 91 56 81476 Münchenhttp://ma.tthias.eu/
Re: [jdev] Re: XMPP Ping method?
Hello, On Sat, Nov 04, 2006 at 09:26:40AM +, Dave Cridland wrote: > On Fri Nov 3 22:48:32 2006, Tobias Markmann wrote: > >I didn't know SCTP since you've mentioned it and have some > >questions: > > > > 1. Is SCTP TCP compatible? When a server provides SCTP protocol on > > port 5222 for example normal TCP clients can still connect? > > Nope. Or yes. It depends on what you're asking for. "port 5222" is > transport-protocol specific, so SCTP, TCP, and UDP can all co-exist > on that port, but the server needs to listen to those ports > independently. > > SCTP is also message based, which means it can cope with stanza ACKs > by using one message per N stanzas, but on the other hand it means > it's very different to TCP. Well, I more thought using one message per stanza, so you do not have to think about where one starts and another ends. It could help the client to apply DOM-parsing on each stanza separately. Maybe even the multi-streaming capability could be nice. > I don't think it's a solution, as such, and the multi-homing/mobility > capabilities that have been mentioned exist in several forms at the > IP layer, such as MIP6, and perhaps most interestingly HIP. > -- You can fool some of the people all of the time, and all of the people some of the time, but you can make a fool of yourself anytime. Michal "vorner" Vaner pgptk6Mm9fKm3.pgp Description: PGP signature
Re: [jdev] Re: XMPP Ping method?
On Fri Nov 3 22:48:32 2006, Tobias Markmann wrote: I didn't know SCTP since you've mentioned it and have some questions: 1. Is SCTP TCP compatible? When a server provides SCTP protocol on port 5222 for example normal TCP clients can still connect? Nope. Or yes. It depends on what you're asking for. "port 5222" is transport-protocol specific, so SCTP, TCP, and UDP can all co-exist on that port, but the server needs to listen to those ports independently. SCTP is also message based, which means it can cope with stanza ACKs by using one message per N stanzas, but on the other hand it means it's very different to TCP. I don't think it's a solution, as such, and the multi-homing/mobility capabilities that have been mentioned exist in several forms at the IP layer, such as MIP6, and perhaps most interestingly HIP. Dave. -- Dave Cridland - mailto:[EMAIL PROTECTED] - xmpp:[EMAIL PROTECTED] - acap://acap.dave.cridland.net/byowner/user/dwd/bookmarks/ - http://dave.cridland.net/ Infotrope Polymer - ACAP, IMAP, ESMTP, and Lemonade
