RFC1459 on Internet Relay Chat Protocol
"Joyce K. Reynolds" <jkrey@isi.edu> Wed, 26 May 1993 19:36 UTC
Received: from CNRI.RESTON.VA.US by IETF.CNRI.Reston.VA.US id aa13494; 26 May 93 15:36 EDT
Received: from ietf.cnri.reston.va.us by CNRI.Reston.VA.US id aa21280; 26 May 93 15:36 EDT
Received: from ietf.cnri.reston.va.us by IETF.CNRI.Reston.VA.US id aa13477; 26 May 93 15:36 EDT
Received: from CNRI.RESTON.VA.US by IETF.CNRI.Reston.VA.US id aa13394; 26 May 93 15:34 EDT
Received: from zephyr.isi.edu by CNRI.Reston.VA.US id aa21193; 26 May 93 15:34 EDT
Received: from akamai.isi.edu by zephyr.isi.edu (5.65c/5.61+local-10) id <AA29082>; Wed, 26 May 1993 12:35:08 -0700
Message-Id: <199305261935.AA29082@zephyr.isi.edu>
To: IETF-Announce:;
Subject: RFC1459 on Internet Relay Chat Protocol
Cc: jkrey@isi.edu
Mime-Version: 1.0
Content-Type: Multipart/Mixed; Boundary="NextPart"
Date: Wed, 26 May 1993 12:35:06 -0700
Sender: ietf-announce-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 1459: Title: Internet Relay Chat Protocol Author: J. Oikarinen & D. Reed Mailbox: jto@tolsun.oulu.fi, avalon@coombs.anu.edu.au Pages: 65 Characters: 138,964 Updates/Obsoletes: none The IRC protocol was developed over the last 4 years since it was first implemented as a means for users on a BBS to chat amongst themselves. Now it supports a world-wide network of servers and clients, and is stringing to cope with growth. Over the past 2 years, the average number of users connected to the main IRC network has grown by a factor of 10. The IRC protocol is a text-based protocol, with the simplest client being any socket program capable of connecting to the server. This memo defines an Experimental Protocol for the Internet community. Discussion and suggestions for improvement are requested. Please refer to the current edition of the "IAB Official Protocol Standards" 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 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 NIC@NIC.DDN.MIL. 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 1111, "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.
- RFC1459 on Internet Relay Chat Protocol Joyce K. Reynolds