RFC1644 on Transaction/TCP
NIC
From jk...@ISI.EDU Wed Jul 13 17:13:25 1994
Message-Id: <1994071321...@zephyr.isi.edu>
To: rfc-...@nic.ddn.mil
Subject: RFC1644 on Transaction/TCP
Cc: jk...@ISI.EDU
Mime-Version: 1.0
Content-Type: Multipart/Mixed; Boundary=NextPart
Date: Wed, 13 Jul 94 14:13:58 PDT
From: "Joyce K. Reynolds" <jk...@ISI.EDU>
--NextPart
A new Request for Comments is now available in online RFC libraries.
RFC 1644:
Title: T/TCP -- TCP Extensions for Transactions
Functional Specification
Author: R. Braden
Mailbox: bra...@isi.edu
Pages: 38
Characters: 87,362
Updates/Obsoletes: none
This memo specifies T/TCP, an experimental TCP extension for efficient
transaction-oriented (request/response) service. This
backwards-compatible extension could fill the gap between the current
connection-oriented TCP and the datagram-based UDP.
This memo defines an Experimental Protocol for the Internet community.
This memo does not specify an Internet standard of any kind.
Discussion and suggestions for improvement are requested.
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 IETF-R...@CNRI.RESTON.VA.US. Requests to be
added to or deleted from the RFC-DIST distribution list should
be sent to RFC-R...@NIC.DDN.MIL.
Details on obtaining RFCs via FTP or EMAIL may be obtained by sending
an EMAIL message to rfc-...@ISI.EDU with the message body
help: ways_to_get_rfcs. For example:
To: rfc-...@ISI.EDU
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 ad...@DS.INTERNIC.NET. Unless
specifically noted otherwise on the RFC itself, all RFCs are for
unlimited distribution.
Submissions for Requests for Comments should be sent to
RFC-E...@ISI.EDU. 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="mail...@ds.internic.net"
Content-Type: text/plain
Content-ID: <94071314...@ISI.EDU>
SEND /rfc/rfc1644.txt
--OtherAccess
Content-Type: Message/External-body;
name="rfc1644.txt";
site="ds.internic.net";
access-type="anon-ftp";
directory="rfc"
Content-Type: text/plain
Content-ID: <94071314...@ISI.EDU>
--OtherAccess--
--NextPart--