Re: How to implement a fourth protocol

[almut]

Not directly answering your questions, but maybe you are looking for something like port knocking (google for other references, there are plenty...). The idea is to generally keep all ports closed, and only open specific ones (HTTP, SSH, whatever...) temporarily, if a magic pattern of requests is made to selected closed ports (typically only known to the initiated clients).

This isn't supported by any browsers (AFAIK), but there is some prototype code in Perl, in case you want to play with it... Have fun!

[Moron]

I like it. But looking through, I wonder if it is scalable. i.e. I imagine that it would itself deny adequate service above a certain number of concurrent client systems trying to connect.

[almut]

Sure, depending on the implementation, there can be considerable overhead. So, it's generally more intended for the occasional use of some non-advertised service by a few initiated people...

I think it will be very hard to run a regular public service, without at the same time opening up your resources to misuse of some kind, even if it's "only" bad folks clogging up your network bandwidth by sending tons of packets that get rejected at the firewall level...

[Moron]

I don't expect the service to be as accessible as the internet, but at least i could split functionality so that the superficial communicatuions still goes on the internet via https and traffic between contracting parties can move off to the other protocol, much the way two-way radio communication moves off from the public channel to some other frequency for a private chat.