commit d329a961bd7153754fe587c14719d68a0ea422a0 from: Alexander Barton date: Sun Nov 30 20:30:56 2003 UTC Updated, corrected and extended (examples!) protocol documentation. commit - 606cdb69bfd65a41bfcef6c909e289ff6a38baf2 commit + d329a961bd7153754fe587c14719d68a0ea422a0 blob - e3c6bbfe417d0cd56b64b149e9f3faec745ad40e blob + 9858e9ed4980159324d8b3a730b8611e2a7f997f --- doc/Protocol.txt +++ doc/Protocol.txt @@ -22,9 +22,10 @@ in all details. But because the ngIRCd should be a ful replacement for this server ("ircd") it tries to emulate these differences. If you don't like this behavior please ./configure the ngIRCd using the -"--enable-strict-rfc" command line option. But please note: not all IRC -clients are compatible with such an server, some can't even connect at all! -Therefore this option isn't desired for "normal operation". +"--enable-strict-rfc" command line option. But keep in mind: not all IRC +clients are compatible with a server configured that way, some can't even +connect at all! Therefore this option usually isn't desired for "normal +server operation". II. The IRC+ Protocol @@ -35,8 +36,8 @@ as defined in RFC 2810-2813. This enhanced protocol is backwards compatible to the "plain" IRC protocol and will only be used by the ngIRCd if it detects that the peer supports it as well. -The "PASSV" command is used to detect the protocol and peer versions (see -RFC 2813, section 4.1.1). +The "PASS" command is used to detect the protocol and peer versions see +RFC 2813 (section 4.1.1) and below. II.1 Register new server link @@ -57,9 +58,11 @@ The following optional(!) 10 bytes contain an implemen version number. Servers supporting the IRC+ protocol as defined in this document provide the string "-IRC+" here. +Example for : "0210-IRC+". + consists of two parts separated with the character "|" and is at most 100 bytes long. The first part contains the name of the implementation -(ngIRCd sets this to "ngIRCd", the original ircd to "IRC", e.g.). The second +(ngIRCd sets this to "ngircd", the original ircd to "IRC", e.g.). The second part is implementation-dependent and should only be parsed if the peer supports the IRC+ protocol as well. In this case the following syntax is used: "[:]". @@ -68,17 +71,21 @@ used: "[:]". number, indicates the supported IRC+ protocol extensions (and may be empty!). -The optional parameter is used to propagate server options as -defined in RFC 2813, section 4.1.1. - The following are defined at the moment: +- C: The server supports the CHANINFO command. + - o: IRC operators are allowed to change channel- and channel-user-modes even if they aren't channel-operator of the affected channel. -- C: The server supports the CHANINFO command. +- Z: Compressed server links are supported by the server. +Example for a complete string: "ngircd|0.7.5:CZ". +The optional parameter is used to propagate server options as +defined in RFC 2813, section 4.1.1. + + II.2 Exchange channel-modes, topics, and persistent channels Command: CHANINFO @@ -104,4 +111,4 @@ channel mode). In this case should be "0". -- -$Id: Protocol.txt,v 1.10 2003/04/29 13:37:36 goetz Exp $ +$Id: Protocol.txt,v 1.11 2003/11/30 20:30:56 alex Exp $