From owner-freebsd-arch@FreeBSD.ORG Fri Nov 5 17:12:17 2004 Return-Path: Delivered-To: freebsd-arch@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 69E6B16A4CE; Fri, 5 Nov 2004 17:12:17 +0000 (GMT) Received: from mail.net (custpop.ca.mci.com [142.77.1.111]) by mx1.FreeBSD.org (Postfix) with ESMTP id 7A75B43D5C; Fri, 5 Nov 2004 17:12:16 +0000 (GMT) (envelope-from kfl@xiphos.ca) Received: from [216.95.199.148] (account kfl@xiphos.ca HELO [192.168.1.7]) by mail.net (CommuniGate Pro SMTP 4.2.5) with ESMTP id 26430096; Fri, 05 Nov 2004 12:12:12 -0500 Message-ID: <418BB7BC.3010305@xiphos.ca> Date: Fri, 05 Nov 2004 12:26:20 -0500 From: Karim Fodil-Lemelin User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.7.3) Gecko/20040910 X-Accept-Language: en-us, en MIME-Version: 1.0 To: Andre Oppermann References: <418BB008.6040907@xiphos.ca> <418BAE54.72E4208F@freebsd.org> In-Reply-To: <418BAE54.72E4208F@freebsd.org> Content-Type: text/plain; charset=ISO-8859-1; format=flowed 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-arch@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussion related to FreeBSD architecture List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 05 Nov 2004 17:12:17 -0000 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? 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.