agenda for Houston IETF
Jim Barnes <barnes@xylogics.com> Wed, 20 October 1993 11:47 UTC
Received: from ietf.nri.reston.va.us by IETF.CNRI.Reston.VA.US id aa02292; 20 Oct 93 7:47 EDT
Received: from CNRI.RESTON.VA.US by IETF.CNRI.Reston.VA.US id aa02288; 20 Oct 93 7:47 EDT
Received: from basil.xylint.co.uk by CNRI.Reston.VA.US id aa07571; 20 Oct 93 7:47 EDT
Received: from atlas.xylogics.com by basil.xylint.co.uk (4.1/SMI-4.1) id AA26240; Wed, 20 Oct 93 12:28:16 BST
Received: from spock.xylogics.com by atlas.xylogics.com with SMTP id AA17264 (5.65c/UK-2.1-930726); Wed, 20 Oct 1993 07:32:11 -0400
Received: by spock.xylogics.com id AA13072 (4.1/UK-2.1-921215); Wed, 20 Oct 93 07:28:26 EDT
Message-Id: <13072.9310201128@spock.xylogics.com>
Sender: ietf-archive-request@IETF.CNRI.Reston.VA.US
From: Jim Barnes <barnes@xylogics.com>
Date: Wed, 20 Oct 1993 07:28:25 -0400
X-Mailer: Mail User's Shell (7.1.0 4/25/90)
To: cmp-id@xylint.co.uk
Subject: agenda for Houston IETF
In case you missed the announcement: tmux BOF Wednesday, November 3, 1993 0930-1200 One of the problems with terminal servers attached to a LAN is the large number of small packets they can generate. Frequently, most of these packets are destined for only one or two hosts. The large number of small packets causes performance problems not only with the terminal servers generating the packets, but also with the hosts receiving the packets. The receiving hosts must pass all these small packets through their TCP/IP protocol stacks and send the data to the destination applications. A standard solution to this overhead problem would be useful to both terminal servers and host nodes. At the Amsterdam IETF, the CMP protocol (multiplexing on top of the TCP layer) was discussed. This protocol is described in the Internet draft document draft-cameron-cmp.01.txt. An alternative proposal (known as TMux) was presented that multiplexed small packets between the IP and TCP layers. This protocol is described in the Internet draft document draft-cameron-tmux.01.txt. The general consensus of those attending the Amsterdam BOF was that the TMux proposal was superior to the CMP proposal. The purpose of this BOF is two-fold. First, to report on implementation experience for TMux. This report will include observed performance of the TMux implementation. Second, to consider whether the TMux protocol definition should be moved forward to Proposed Standard status. An email list has been set up for discussions of this protocol. To join the list, send a request to cmp-id-request@xylint.co.uk Please read the TMux protocol document (draft-cameron-tmux-01.txt) before the meeting. You may also wish to read the CMP protocol document (draft-cameron-cmp-01.txt) for historical purposes. Agenda for the BOF: - Introduction - CMP and TMux: How we got here - TMux implementation experience - What next? Should TMux be submitted to the IESG for elevation to Proposed Standard status?
- agenda for Houston IETF Jim Barnes