From owner-freebsd-net@FreeBSD.ORG Fri Nov 5 17:31:47 2004 Return-Path: Delivered-To: freebsd-net@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id D59BF16A4CF for ; Fri, 5 Nov 2004 17:31:47 +0000 (GMT) Received: from c00l3r.networx.ch (c00l3r.networx.ch [62.48.2.2]) by mx1.FreeBSD.org (Postfix) with ESMTP id 08C4143D58 for ; Fri, 5 Nov 2004 17:31:47 +0000 (GMT) (envelope-from andre@freebsd.org) Received: (qmail 8018 invoked from network); 5 Nov 2004 17:27:40 -0000 Received: from unknown (HELO freebsd.org) ([62.48.0.53]) (envelope-sender ) by c00l3r.networx.ch (qmail-ldap-1.03) with SMTP for ; 5 Nov 2004 17:27:40 -0000 Message-ID: <418BB909.501CC9FD@freebsd.org> Date: Fri, 05 Nov 2004 18:31:53 +0100 From: Andre Oppermann X-Mailer: Mozilla 4.8 [en] (Windows NT 5.0; U) X-Accept-Language: en MIME-Version: 1.0 To: Karim Fodil-Lemelin References: <418BB008.6040907@xiphos.ca> <418BAE54.72E4208F@freebsd.org> <418BB7BC.3010305@xiphos.ca> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit cc: freebsd-net@freebsd.org cc: Matt Sealey cc: mallman@icir.org cc: Julian Elischer cc: freebsd-arch@freebsd.org Subject: Re: Removing T/TCP and replacing it with something simpler X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 05 Nov 2004 17:31:48 -0000 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. -- Andre > Andre Oppermann wrote: > > >Karim Fodil-Lemelin wrote: > > > > > >>Now, > >> > >> I have a question. In our application which can be described as: > >> > >>Client ----> (Client Gateway) -------> SATLINK ------> (Server Gateway) > >>-----> Internet > >> > >>We act as the Internet servers (transparent proxies) and therefore T/TCP > >>traffic is only sent over the SATLINK. In the current T/TCP > >>implementation the sender has to send a ccnew option to discover that > >>the server side supports T/TCP. Now we had to modify this so the > >>gateways uses the knowledge that they work together and they don't need > >>to send a ccnew option everytime a client makes a connection to a new > >>server. > >> > >>My question is: In the new implementation does the cookie will be > >>generated per machine or like the tao mecanism will it be based on a src > >>/ dst tuple? > >> > >> > > > >The new cookie system will use the src-host/dst-host tuple. The first > >tcp connection between two hosts (port numbers are irrelevant) is a > >normal three-way handshake and the cookie is exchanged. From then on > >it skips over 3WHS on the server if the cookie matches. > > > > > > > > -- > 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.