59 messages in org.freebsd.freebsd-archRemoving T/TCP and replacing it with ...| From | Sent On | Attachments |
|---|---|---|
| Andre Oppermann | Oct 21, 2004 7:33 am | |
| Poul-Henning Kamp | Oct 21, 2004 7:41 am | |
| Andre Oppermann | Oct 21, 2004 7:46 am | |
| Richard Wendland | Oct 21, 2004 7:59 am | |
| Mike Silbersack | Oct 21, 2004 8:23 am | |
| Andre Oppermann | Oct 21, 2004 8:37 am | |
| Bruce M Simpson | Oct 21, 2004 8:40 am | |
| Andre Oppermann | Oct 21, 2004 9:23 am | |
| Garrett Wollman | Oct 21, 2004 9:27 am | |
| Mark Allman | Oct 21, 2004 10:31 am | |
| Andre Oppermann | Oct 21, 2004 10:56 am | |
| Matt Emmerton | Oct 21, 2004 11:31 am | |
| Sean Chittenden | Oct 21, 2004 11:31 am | |
| Mark Allman | Oct 21, 2004 11:32 am | |
| David O'Brien | Oct 21, 2004 11:51 am | |
| Andre Oppermann | Oct 21, 2004 11:56 am | |
| Julian Elischer | Oct 21, 2004 11:59 am | |
| Garrett Wollman | Oct 21, 2004 12:02 pm | |
| Andre Oppermann | Oct 21, 2004 12:02 pm | |
| Andre Oppermann | Oct 21, 2004 12:04 pm | |
| Sean Chittenden | Oct 21, 2004 12:24 pm | |
| Marco Molteni | Oct 21, 2004 12:34 pm | |
| Igor Sysoev | Oct 21, 2004 12:41 pm | |
| Craig Rodrigues | Oct 21, 2004 6:46 pm | |
| Russell L. Carter | Oct 21, 2004 7:02 pm | |
| Julian Elischer | Oct 21, 2004 8:24 pm | |
| SUZUKI Shinsuke | Oct 22, 2004 12:47 am | |
| Dag-Erling Smørgrav | Oct 22, 2004 5:06 am | |
| Dag-Erling Smørgrav | Oct 22, 2004 5:47 am | |
| Andre Oppermann | Oct 22, 2004 8:14 am | |
| Andre Oppermann | Oct 22, 2004 8:17 am | |
| Brian Fundakowski Feldman | Oct 22, 2004 8:44 am | |
| Andre Oppermann | Oct 22, 2004 8:55 am | |
| Mark Allman | Oct 22, 2004 11:24 am | |
| Peter Lei | Oct 22, 2004 5:59 pm | |
| Randall Stewart | Oct 23, 2004 6:07 am | |
| Randall Stewart | Oct 23, 2004 6:16 am | |
| Randall Stewart | Oct 23, 2004 6:17 am | |
| Randall Stewart | Oct 23, 2004 6:20 am | |
| Andre Oppermann | Oct 23, 2004 7:16 am | |
| Randy Bush | Oct 23, 2004 9:01 am | |
| SUZUKI Shinsuke | Oct 25, 2004 10:18 pm | |
| Randall Stewart | Oct 26, 2004 3:41 am | |
| Peter Lei | Oct 26, 2004 7:44 am | |
| Karim Fodil-Lemelin | Nov 4, 2004 9:52 am | |
| Andre Oppermann | Nov 4, 2004 10:50 am | |
| Julian Elischer | Nov 4, 2004 12:52 pm | |
| Matt Sealey | Nov 4, 2004 12:58 pm | |
| Karim Fodil-Lemelin | Nov 5, 2004 8:08 am | |
| Karim Fodil-Lemelin | Nov 5, 2004 8:39 am | |
| Andre Oppermann | Nov 5, 2004 8:45 am | |
| Karim Fodil-Lemelin | Nov 5, 2004 9:12 am | |
| Andre Oppermann | Nov 5, 2004 9:31 am | |
| Karim Fodil-Lemelin | Nov 5, 2004 1:45 pm | |
| Andre Oppermann | Nov 5, 2004 2:16 pm | |
| Mark Allman | Nov 8, 2004 8:08 pm | |
| Andre Oppermann | Jul 3, 2005 12:08 am | |
| Andre Oppermann | Jul 3, 2005 11:43 am | |
| Randall Stewart | Jul 3, 2005 11:44 am |
| Subject: | Removing T/TCP and replacing it with something simpler | |
|---|---|---|
| From: | Andre Oppermann (and...@freebsd.org) | |
| Date: | Nov 5, 2004 2:16:45 pm | |
| List: | org.freebsd.freebsd-arch | |
Karim Fodil-Lemelin wrote:
Ok here is an example, just to make sure I understand:
CLI1 : SERVER1 (first connection, option negociated, tuple hash created) CLI1 : SERVER1 (second connection, sending payload in first packet, using previously negotiated cookie) ... CLI1 : SERVER1 ( nth connection, sending payload in first packet, using previously negotiated cookie )
CLI1 : SERVER2 (first connection, option negociated, tuple created) CLI1 : SERVER2 (second connection, sending payload in first packet, using previously negotiated cookie) ... CLI1 : SERVER2 ( nth connection, sending payload in first packet, using previously negotiated cookie ) ... CLIX : SERVERY ( if first connection create cookie, store tuple. if tuple exists send payload in first packet)
So, each time CL1 goes to a different server it pay the 3WSH tax only once. This is very alike how T/TCP works right now (beside the cookie thing).
Yes, exactly. Actually the new T/TCP thing works the same as the old one from a functional point of view. What changes is the implementation. The original one was quite intrusive to the TCP code and generated many special cases which made it hard to maintain and to put new code in. In addition it CC* stuff is a rather weak and fragile mechanism. That's why we go with cookies this time and there are only a few places where the code has to be aware of it. Much less intrusive and more easy to maintain properly.
What I am wondering is how can we avoid as much as possible the "learning" of the different servers since I know that CLIs will have to go through two gateways running transparent proxies that support the option (T/TCP). But since they are transparent (using forward rules) the gateway don't talk to each other but to the SERVERs (from an IP standpoint).
For example, if the cookie was per machine and not tuples, you could have something like this:
step 1: CLI1 : SERVER1 (first connection, option negociated, cookie negotiated) CLI1 : SERVER1 (second connection, sending payload in first packet, using previously negotiated cookie) ... step2: CLI1 : SERVER2 (first connection, option negociated, get the same machine cookie from "SERVER1" (found a transparent proxy))
(From now on CL1 assumes its going through a transparent proxy that can do T/TCP)
CLI1 : SERVER3 (first connection, sending payload in first packet, using previously negotiated machine cookie, validating transparent proxy)
(If the cookie returned by SERVER3 does not match the"machine cookie it found in SERVER1" then go back to step 1)
This way the protocol would use knowledge that there is a transparent proxy (found at step2) that is doing T/TCP on behalf of the SERVERs.
What do you think?
I think that is nice. Sounds like homework for you. ;-)
-- Andre
Regards,
Andre Oppermann wrote:
Karim Fodil-Lemelin wrote:
In the case where all connections go through the SATLINK and are splitted by proxies, it make sense to use this knowledge and not renegotiate cookies for every connections since we know there is only one path to the internet and that all SATLINK connections will support (T/TCP or whatever name it will have). Do you have any plan to include that knowledge in your design or is it too much of a special case to really care?
It does not renegotiate cookies for every connection. Only the first connection will do that. Re-seeding of the cookies will happen trans- parently. You pay the 3WSH tax only once for the first connection, or the first connection after a longer idle time when the cookie expired.
-- Karim Fodil-Lemelin Lead Programmer
Xiphos Technologies Inc. (514) 848-9640 x223 (514) 848-9644 fax www.xiplink.com
-------------------------------------------------------------- The information transmitted is intended only for the person or entity to which it is addressed and may contain confidential and/or privileged material. If you have received this in error, please contact the sender and delete this communication and any copy immediately. Thank you.