TMux is now RFC 1692

[Pete Cameron <[e-mail]>]

For those of you not on the ietf-announce mailing list, here
is the official announcement that TMux has been moved to the
standards track and allocated an RFC number.

Pete Cameron

---------  Received message begins Here  ---------

> From [e-mail] Wed Aug 17 20:59 BST 1994
> Return-Path: <[e-mail]>
> To: IETF-Announce:;@IETF.CNRI.Reston.VA.US
> Subject: RFC1692 on TMux
> Cc: [e-mail]
> Mime-Version: 1.0
> Date: Wed, 17 Aug 94 10:41:47 PDT
> Sender: [e-mail]
> From: "Joyce K. Reynolds" <[e-mail]>
> Content-Type: Multipart/Mixed; Boundary=NextPart
> 
> 
> --NextPart
> 
> 
> A new Request for Comments is now available in online RFC libraries.
> 
> 
>         RFC 1692:
> 
>         Title:      Transport Multiplexing Protocol (TMux)
>         Author:     P. Cameron, D. Crocker, D. Cohen & J. Postel
>         Mailbox:    [e-mail], [e-mail],
>                     [e-mail], [e-mail]
>         Pages:      12      
>         Characters: 26,163
>         Updates/Obsoletes:  none
> 
> 
> One of the problems with the use of terminal servers is the large
> number of small packets they can generate.  Frequently, most of these
> packets are destined for only one or two hosts.  TMux is a protocol
> which allows multiple short transport segments, independent of
> application type, to be combined between a server and host pair.  This
> RFC is not a product of an IETF Working Group, but has been reviewed
> in the Transport Area of the IETF.
> 
> This is now a Proposed Standard Protocol.
> 
> This document specifies an Internet standards track protocol for the
> Internet community, and requests discussion and suggestions for
> improvements.  Please refer to the current edition of the "Internet
> Official Protocol Standards" (STD 1) for the standardization state and
> status of this protocol.  Distribution of this memo is unlimited.
> 
> This announcement is sent to the IETF list and the RFC-DIST list.
> Requests to be added to or deleted from the IETF distribution list
> should be sent to [e-mail].  Requests to be
> added to or deleted from the RFC-DIST distribution list should
> be sent to [e-mail].
> 
> Details on obtaining RFCs via FTP or EMAIL may be obtained by sending
> an EMAIL message to [e-mail] with the message body 
> help: ways_to_get_rfcs.  For example:
> 
>         To: [e-mail]
>         Subject: getting rfcs
> 
>         help: ways_to_get_rfcs
> 
> Requests for special distribution should be addressed to either the
> author of the RFC in question, or to [e-mail].  Unless
> specifically noted otherwise on the RFC itself, all RFCs are for
> unlimited distribution.
> 
> Submissions for Requests for Comments should be sent to
> [e-mail].  Please consult RFC 1543, Instructions to RFC
> Authors, for further information.
> 
> 
> Joyce K. Reynolds
> USC/Information Sciences Institute
> 
> ...
> 
> Below is the data which will enable a MIME compliant Mail Reader 
> implementation to automatically retrieve the ASCII version
> of the RFCs.
> 
> --NextPart
> Content-Type: Multipart/Alternative; Boundary="OtherAccess"
> 
> --OtherAccess
> Content-Type:  Message/External-body;
>         access-type="mail-server";
>         server="[e-mail]"
> 
> Content-Type: text/plain
> Content-ID: <[e-mail]>
> 
> SEND /rfc/rfc1692.txt
> 
> --OtherAccess
> Content-Type:   Message/External-body;
>         name="rfc1692.txt";
>         site="ds.internic.net";
>         access-type="anon-ftp";
>         directory="rfc"
> 
> Content-Type: text/plain
> Content-ID: <[e-mail]>
> 
> --OtherAccess--
> --NextPart--
> 

Pete Cameron                                            tel: [phone]
Consulting Engineer                                     fax: [phone]
Xylogics International Limited                  email: [e-mail]
Featherstone Rd, Wolverton Mill, MK12 5RD, UK.         [e-mail]