Requirement that the first character is either '&', '#', '+' or '!', See the protocolĬhannels names are strings (beginning with a '&', '#', '+' or '!'Ĭharacter) of length up to fifty (50) characters. Has a maximum length of nine (9) characters. Forįurther details on this type of action, see section 3.7.1 (KILL).Įach service is distinguished from other services by a service nameĬomposed of a nickname and a server name. Justification for this is very delicate since its abuse is bothĭestructive and annoying, and its benefits close to inexistent. To close the connection between any client and server. User from the connected network by 'force', i.e., operators are able See sections 3.1.8 (SQUIT) and 3.4.7 (CONNECT).Ī more controversial power of operators is the ability to remove a Provides for operators only to be able to perform such functions. In recognition of this need, the protocol discussed herein Operators SHOULD be able to performīasic network tasks such as disconnecting and reconnecting servers as Granted to an operator can be considered as 'dangerous', they are General maintenance functions on the network. Network, a special class of users (operators) is allowed to perform To allow a reasonable amount of order to be kept within the IRC SHOULD accept longer strings as they may become used in future While the maximum length is limited to nine characters, clients Grammar rules ( section 2.3.1) for what may and may not be used in a Having a maximum length of nine (9) characters. RFC 2812 Internet Relay Chat: Client Protocol April 2000 1.2.1 UsersĮach user is distinguished from other users by a unique nickname Netwide unique identifier (whose format depends on the type ofĬlient) and the server which introduced the client. Rules ( section 2.3.1) for what may and may not be used in a serverįor each client all servers MUST have the following information: a Servers are uniquely identified by their name, which has a maximum This section defines the identifiers used for the various components RFC 2812 Internet Relay Chat: Client Protocol April 2000 4. RFC 2812 Internet Relay Chat: Client Protocol April 2000 2.3.1 Message format in Augmented BNF. Reader is familiar with the IRC Architecture. This document defines the Client Protocol, and assumes that the The IRC (Internet Relay Chat) protocol is for use with text basedĬonferencing the simplest client being any socket program capable of For more information on security issues with the IRC Like email, the receiver of the data has to be careful about how theĭata is handled.

The IRC protocol itself enables several possibilities of transferringĭata between clients, and just like with other transfer mechanisms Distribution of thisĬopyright (C) The Internet Society (2000). Not specify an Internet standard of any kind. This memo provides information for the Internet community. RFC 2812: Internet Relay Chat: Client Protocol Įrrata Exist Network Working Group C.

Limechat host mask