|
FTP might be interesting. It should be able to do everything on one port, by doing file transfers in a separate stream. And it should be able to background each file transfer.
Telnet? Let's do SSH instead. It already has a means to do separate subchannels. Those can just be done over separate SCTP streams and benefit from the separated packet loss recovery.
HTTP makes some sense. It seems to me the best way is to just do more requests in more streams as needed.
HTTPS and other TLS/SSL things over SCTP is where more thought might need to happen. What I have read is that they are wanting to restart from scratch with TLS/SSL within each separate stream. That just seems wrong to me. Instead, a "TLS over SCTP" should claim the first stream to manage the session security. Over this stream, now secured, simpler quick key exchanges can be done with a stream identity associated with that key exchange. Then the traffic on the other stream can just proceed in an encrypted state much like a non-negotiated share key.
Sorry I don't have a specific answer as to whether implementations are in progress or done. I have found that my firewall, a commercial product, won't do SCTP at all, not even passing it along blindly. Of course, it shouldn't pass it along blindly as that would be a new security hole. But they do need to implement the various access rules and translation, including port translation. They also need to do IPv6, but that's another issue.
|
