RFC 2811 on Internet Relay Chat: Channel Management

RFC Editor <rfc-ed@ISI.EDU> Fri, 28 April 2000 23:46 UTC

Received: from loki.ietf.org (loki [10.27.2.29]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA19889; Fri, 28 Apr 2000 19:46:51 -0400 (EDT)
Received: (from adm@localhost) by loki.ietf.org (8.9.1b+Sun/8.9.1) id TAA09068 for ietf-123-outbound.10@ietf.org; Fri, 28 Apr 2000 19:45:02 -0400 (EDT)
Received: from ietf.org (odin.ietf.org [10.27.2.28]) by loki.ietf.org (8.9.1b+Sun/8.9.1) with ESMTP id TAA08963 for <all-ietf@loki.ietf.org>; Fri, 28 Apr 2000 19:30:13 -0400 (EDT)
Received: from boreas.isi.edu (boreas.isi.edu [128.9.160.161]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA19710 for <all-ietf@ietf.org>; Fri, 28 Apr 2000 19:30:12 -0400 (EDT)
Received: from ISI.EDU (jet.isi.edu [128.9.160.87]) by boreas.isi.edu (8.8.7/8.8.6) with ESMTP id QAA22563; Fri, 28 Apr 2000 16:30:11 -0700 (PDT)
Message-Id: <200004282330.QAA22563@boreas.isi.edu>
To: IETF-Announce:;
Subject: RFC 2811 on Internet Relay Chat: Channel Management
Cc: rfc-ed@ISI.EDU
Mime-Version: 1.0
Content-Type: Multipart/Mixed; Boundary="NextPart"
Date: Fri, 28 Apr 2000 16:30:11 -0700
From: RFC Editor <rfc-ed@ISI.EDU>

A new Request for Comments is now available in online RFC libraries.


        RFC 2811

        Title:	    Internet Relay Chat: Channel Management
        Author(s):  C. Kalt
        Status:     Informational
	Date:       April 2000
        Mailbox:    kalt@stealth.net
        Pages:      19
        Characters: 40788
        Updates:    RFC 1459

        I-D Tag:    draft-kalt-irc-chan-01.txt

        URL:        ftp://ftp.isi.edu/in-notes/rfc2811.txt


One of the most notable characteristics of the IRC (Internet Relay
Chat) protocol is to allow for users to be grouped in forums, called
channels, providing a mean for multiple users to communicate
together.
 
There was originally a unique type of channels, but with the
years, new types appeared either as a response to a need, or for
experimental purposes.
 
This document specifies how channels, their characteristics and
properties are managed by IRC servers.

This memo provides information for the Internet community.  It does
not specify an Internet standard of any kind.  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@IETF.ORG.  Requests to be
added to or deleted from the RFC-DIST distribution list should
be sent to RFC-DIST-REQUEST@RFC-EDITOR.ORG.

Details on obtaining RFCs via FTP or EMAIL may be obtained by sending
an EMAIL message to rfc-info@RFC-EDITOR.ORG with the message body 
help: ways_to_get_rfcs.  For example:

        To: rfc-info@RFC-EDITOR.ORG
        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 RFC-Manager@RFC-EDITOR.ORG.  Unless
specifically noted otherwise on the RFC itself, all RFCs are for
unlimited distribution.echo 
Submissions for Requests for Comments should be sent to
RFC-EDITOR@RFC-EDITOR.ORG.  Please consult RFC 2223, Instructions to RFC
Authors, for further information.


Joyce K. Reynolds and Sandy Ginoza
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.
ftp://ftp.isi.edu/in-notes/rfc2811.txt"><ftp://ftp.isi.edu/in-notes/rfc2811.txt>