RFC1756 on Remote Write Protocol
"Joyce K. Reynolds" <jkrey@isi.edu> Thu, 19 January 1995 18:49 UTC
Received: from ietf.nri.reston.va.us by IETF.CNRI.Reston.VA.US id aa06356; 19 Jan 95 13:49 EST
Received: from CNRI.Reston.VA.US by IETF.CNRI.Reston.VA.US id aa06339; 19 Jan 95 13:49 EST
Received: from ietf.cnri.reston.va.us by CNRI.Reston.VA.US id aa11283; 19 Jan 95 13:49 EST
Received: from ietf.cnri.reston.va.us by IETF.CNRI.Reston.VA.US id aa06268; 19 Jan 95 13:49 EST
Received: from CNRI.Reston.VA.US by IETF.CNRI.Reston.VA.US id aa06123; 19 Jan 95 13:39 EST
Received: from zephyr.isi.edu by CNRI.Reston.VA.US id aa11117; 19 Jan 95 13:39 EST
Received: from akamai.isi.edu by zephyr.isi.edu (5.65c/5.61+local-17) id <AA21599>; Thu, 19 Jan 1995 10:39:27 -0800
Message-Id: <199501191839.AA21599@zephyr.isi.edu>
To: IETF-Announce:;
Subject: RFC1756 on Remote Write Protocol
Cc: jkrey@isi.edu
Mime-Version: 1.0
Content-Type: Multipart/Mixed; Boundary="NextPart"
Date: Thu, 19 Jan 1995 10:40:30 -0800
X-Orig-Sender: ietf-announce-request@IETF.CNRI.Reston.VA.US
Sender: ietf-archive-request@IETF.CNRI.Reston.VA.US
From: "Joyce K. Reynolds" <jkrey@isi.edu>
A new Request for Comments is now available in online RFC libraries. RFC 1756: Title: REMOTE WRITE PROTOCOL - VERSION 1.0 Author: T. Rinne Date: January 1995 Mailbox: Timo.Rinne@hut.fi Pages: 11 Characters: 22,078 Updates/Obsoletes: none URL: ftp://ds.internic.net/rfc/rfc1756.txt It is often convenient to use electronic communication somewhat lighter than electronic mail. Sometimes even the use of the talk(1) *) program seems like overkill. We like to offer to user something like UNIX **) command write(1) ***) except that it can also pass messages through the network instead of the single host. There have been few programs offering this kind of service, but they have either based on SUN-RPC protocol or used a strictly undocumented protocol. This document describes a simple Remote Write Protocol (RWP) that should have been documented at least 10 years ago. But late is better than never. Version number of the RWP protocol in this document is 1.0. 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-REQUEST@CNRI.RESTON.VA.US. Requests to be added to or deleted from the RFC-DIST distribution list should be sent to RFC-REQUEST@NIC.DDN.MIL. Details on obtaining RFCs via FTP or EMAIL may be obtained by sending an EMAIL message to rfc-info@ISI.EDU with the message body help: ways_to_get_rfcs. For example: To: rfc-info@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 admin@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-EDITOR@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.
- RFC1756 on Remote Write Protocol Joyce K. Reynolds