From owner-freebsd-current Tue Mar 12 00:04:11 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id AAA13339 for current-outgoing; Tue, 12 Mar 1996 00:04:11 -0800 (PST) Received: from utrhcs.cs.utwente.nl (utrhcs.cs.utwente.nl [130.89.10.247]) by freefall.freebsd.org (8.7.3/8.7.3) with SMTP id AAA13326 for ; Tue, 12 Mar 1996 00:04:04 -0800 (PST) Received: from myrtilos.cs.utwente.nl by utrhcs.cs.utwente.nl (SMI-8.6/csrelay-SVR4_1.3/RBCS) id JAA06671; Tue, 12 Mar 1996 09:03:22 +0100 Received: from curie.cs.utwente.nl by myrtilos.cs.utwente.nl (SMI-8.6/csrelay-Sol1.4/RB) id JAA18605; Tue, 12 Mar 1996 09:03:19 +0100 Received: from localhost by curie.cs.utwente.nl (SMI-8.6/SMI-SVR4) id JAA26728; Tue, 12 Mar 1996 09:03:18 +0100 To: current@FreeBSD.org Subject: Fwd: Draft of T/TCP BOF minutes (was: finger...) Date: Tue, 12 Mar 1996 09:03:16 +0100 Message-ID: <26727.826617796@curie.cs.utwente.nl> From: Andras Olah Sender: owner-current@FreeBSD.org X-Loop: FreeBSD.org Precedence: bulk For those who are sceptic about having T/TCP in our system, here's some extra information from the recent IETF meeting. T/TCP has a good chance to become a standard. The problems people experience come from the fact that ours is the first widely deployed T/TCP implementation. Thus the unpleasant job of discovering all the problems with non-conformant TCP implementations is also our `honor'. (Non-conformant here means non-conformant to the plain old TCP specifications.) Andras ------- Forwarded Message From: braden@ISI.EDU To: mankin@ISI.EDU Cc: end2end-interest@ISI.EDU, braden@ISI.EDU Subject: Draft of T/TCP BOF minutes Date: Sun, 10 Mar 1996 15:22:25 PST Los Angeles IETF Proceedings Transport Services Area Minutes of the Transaction TCP BOF (ttcp) Reported by: Bob Braden/USC Information Sciences Institute This BOF was convened to discuss a set of TCP extensions for efficient transaction-mode communication, i.e., request-response mode, which is currently documented in an Experimental RFC [Braden, R., "T/TCP -- TCP Extensions for Transactions, Functional Specification", RFC-1644, ISI, July 1994]. There has recently been interest in using T/TCP, especially as a component of performance improvements for the World Wide Web. As a result, some have suggested starting a working group to create a standard. [details deleted] The group consensus was that it would be useful to have a working group to consider standardization of T/TCP. Roughly a dozen people out of the 60 attendees indicated that they would participate in such a working group. The chair promised to report this to the Area Director. ------- End of Forwarded Message