-
Notifications
You must be signed in to change notification settings - Fork 18
Expand file tree
/
Copy pathRFC 1459 - Internet Relay Chat Protocol.htm
More file actions
executable file
·3792 lines (2662 loc) · 167 KB
/
RFC 1459 - Internet Relay Chat Protocol.htm
File metadata and controls
executable file
·3792 lines (2662 loc) · 167 KB
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164
165
166
167
168
169
170
171
172
173
174
175
176
177
178
179
180
181
182
183
184
185
186
187
188
189
190
191
192
193
194
195
196
197
198
199
200
201
202
203
204
205
206
207
208
209
210
211
212
213
214
215
216
217
218
219
220
221
222
223
224
225
226
227
228
229
230
231
232
233
234
235
236
237
238
239
240
241
242
243
244
245
246
247
248
249
250
251
252
253
254
255
256
257
258
259
260
261
262
263
264
265
266
267
268
269
270
271
272
273
274
275
276
277
278
279
280
281
282
283
284
285
286
287
288
289
290
291
292
293
294
295
296
297
298
299
300
301
302
303
304
305
306
307
308
309
310
311
312
313
314
315
316
317
318
319
320
321
322
323
324
325
326
327
328
329
330
331
332
333
334
335
336
337
338
339
340
341
342
343
344
345
346
347
348
349
350
351
352
353
354
355
356
357
358
359
360
361
362
363
364
365
366
367
368
369
370
371
372
373
374
375
376
377
378
379
380
381
382
383
384
385
386
387
388
389
390
391
392
393
394
395
396
397
398
399
400
401
402
403
404
405
406
407
408
409
410
411
412
413
414
415
416
417
418
419
420
421
422
423
424
425
426
427
428
429
430
431
432
433
434
435
436
437
438
439
440
441
442
443
444
445
446
447
448
449
450
451
452
453
454
455
456
457
458
459
460
461
462
463
464
465
466
467
468
469
470
471
472
473
474
475
476
477
478
479
480
481
482
483
484
485
486
487
488
489
490
491
492
493
494
495
496
497
498
499
500
501
502
503
504
505
506
507
508
509
510
511
512
513
514
515
516
517
518
519
520
521
522
523
524
525
526
527
528
529
530
531
532
533
534
535
536
537
538
539
540
541
542
543
544
545
546
547
548
549
550
551
552
553
554
555
556
557
558
559
560
561
562
563
564
565
566
567
568
569
570
571
572
573
574
575
576
577
578
579
580
581
582
583
584
585
586
587
588
589
590
591
592
593
594
595
596
597
598
599
600
601
602
603
604
605
606
607
608
609
610
611
612
613
614
615
616
617
618
619
620
621
622
623
624
625
626
627
628
629
630
631
632
633
634
635
636
637
638
639
640
641
642
643
644
645
646
647
648
649
650
651
652
653
654
655
656
657
658
659
660
661
662
663
664
665
666
667
668
669
670
671
672
673
674
675
676
677
678
679
680
681
682
683
684
685
686
687
688
689
690
691
692
693
694
695
696
697
698
699
700
701
702
703
704
705
706
707
708
709
710
711
712
713
714
715
716
717
718
719
720
721
722
723
724
725
726
727
728
729
730
731
732
733
734
735
736
737
738
739
740
741
742
743
744
745
746
747
748
749
750
751
752
753
754
755
756
757
758
759
760
761
762
763
764
765
766
767
768
769
770
771
772
773
774
775
776
777
778
779
780
781
782
783
784
785
786
787
788
789
790
791
792
793
794
795
796
797
798
799
800
801
802
803
804
805
806
807
808
809
810
811
812
813
814
815
816
817
818
819
820
821
822
823
824
825
826
827
828
829
830
831
832
833
834
835
836
837
838
839
840
841
842
843
844
845
846
847
848
849
850
851
852
853
854
855
856
857
858
859
860
861
862
863
864
865
866
867
868
869
870
871
872
873
874
875
876
877
878
879
880
881
882
883
884
885
886
887
888
889
890
891
892
893
894
895
896
897
898
899
900
901
902
903
904
905
906
907
908
909
910
911
912
913
914
915
916
917
918
919
920
921
922
923
924
925
926
927
928
929
930
931
932
933
934
935
936
937
938
939
940
941
942
943
944
945
946
947
948
949
950
951
952
953
954
955
956
957
958
959
960
961
962
963
964
965
966
967
968
969
970
971
972
973
974
975
976
977
978
979
980
981
982
983
984
985
986
987
988
989
990
991
992
993
994
995
996
997
998
999
1000
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN"
"http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
<html xmlns="http://www.w3.org/1999/xhtml" xml:lang="en" lang="en">
<head profile="http://dublincore.org/documents/2008/08/04/dc-html/">
<meta http-equiv="Content-Type" content="text/html; charset=utf-8" />
<meta name="robots" content="index,follow" />
<meta name="creator" content="rfcmarkup version 1.96" />
<link rel="schema.DC" href="http://purl.org/dc/elements/1.1/" />
<meta name="DC.Identifier" content="urn:ietf:rfc:1459" />
<meta name="DC.Description.Abstract" content="The IRC protocol is a text-based protocol, with the simplest client\nbeing any socket program capable of connecting to the server. This\nmemo defines an Experimental Protocol for the Internet community." />
<meta name="DC.Creator" content="Oikarinen, J." />
<meta name="DC.Creator" content="Reed, D." />
<meta name="DC.Date.Issued" content="May, 1993" />
<meta name="DC.Title" content="Internet Relay Chat Protocol" />
<link rel="icon" href="/images/rfc.png" type="image/png" />
<link rel="shortcut icon" href="/images/rfc.png" type="image/png" />
<title>RFC 1459 - Internet Relay Chat Protocol</title>
<style type="text/css">
body {
margin: 0px 8px;
font-size: 1em;
}
h1, h2, h3, h4, h5, h6, .h1, .h2, .h3, .h4, .h5, .h6 {
font-weight: bold;
line-height: 0pt;
display: inline;
white-space: pre;
font-family: monospace;
font-size: 1em;
font-weight: bold;
}
pre {
font-size: 1em;
margin-top: 0px;
margin-bottom: 0px;
}
.pre {
white-space: pre;
font-family: monospace;
}
.header{
font-weight: bold;
}
.newpage {
page-break-before: always;
}
.invisible {
text-decoration: none;
color: white;
}
@media print {
body {
font-size: 10.5pt;
}
h1, h2, h3, h4, h5, h6 {
font-size: 10.5pt;
}
a:link, a:visited {
color: inherit;
text-decoration: none;
}
.noprint {
display: none;
}
}
@media screen {
.grey, .grey a:link, .grey a:visited {
color: #777;
}
.docinfo {
background-color: #EEE;
}
.top {
border-top: 7px solid #EEE;
}
.bgwhite { background-color: white; }
.bgred { background-color: #F44; }
.bggrey { background-color: #666; }
.bgbrown { background-color: #840; }
.bgorange { background-color: #FA0; }
.bgyellow { background-color: #EE0; }
.bgmagenta{ background-color: #F4F; }
.bgblue { background-color: #66F; }
.bgcyan { background-color: #4DD; }
.bggreen { background-color: #4F4; }
.legend { font-size: 90%; }
.cplate { font-size: 70%; border: solid grey 1px; }
}
</style>
<!--[if IE]>
<style>
body {
font-size: 13px;
margin: 10px 10px;
}
</style>
<![endif]-->
<script type="text/javascript"><!--
function addHeaderTags() {
var spans = document.getElementsByTagName("span");
for (var i=0; i < spans.length; i++) {
var elem = spans[i];
if (elem) {
var level = elem.getAttribute("class");
if (level == "h1" || level == "h2" || level == "h3" || level == "h4" || level == "h5" || level == "h6") {
elem.innerHTML = "<"+level+">"+elem.innerHTML+"</"+level+">";
}
}
}
}
var legend_html = "Colour legend:<br /> <table> <tr><td>Unknown:</td> <td><span class='cplate bgwhite'> </span></td></tr> <tr><td>Draft:</td> <td><span class='cplate bgred'> </span></td></tr> <tr><td>Informational:</td> <td><span class='cplate bgorange'> </span></td></tr> <tr><td>Experimental:</td> <td><span class='cplate bgyellow'> </span></td></tr> <tr><td>Best Common Practice:</td><td><span class='cplate bgmagenta'> </span></td></tr> <tr><td>Proposed Standard:</td><td><span class='cplate bgblue'> </span></td></tr> <tr><td>Draft Standard:</td> <td><span class='cplate bgcyan'> </span></td></tr> <tr><td>Standard:</td> <td><span class='cplate bggreen'> </span></td></tr> <tr><td>Historic:</td> <td><span class='cplate bggrey'> </span></td></tr> <tr><td>Obsolete:</td> <td><span class='cplate bgbrown'> </span></td></tr> </table>";
function showElem(id) {
var elem = document.getElementById(id);
elem.innerHTML = eval(id+"_html");
elem.style.visibility='visible';
}
function hideElem(id) {
var elem = document.getElementById(id);
elem.style.visibility='hidden';
elem.innerHTML = "";
}
// -->
</script>
</head>
<body onload="addHeaderTags()">
<div style="height: 13px;">
<div onmouseover="this.style.cursor='pointer';"
onclick="showElem('legend');"
onmouseout="hideElem('legend')"
style="height: 6px; position: absolute;"
class="pre noprint docinfo bgyellow"
title="Click for colour legend." > </div>
<div id="legend"
class="docinfo noprint pre legend"
style="position:absolute; top: 4px; left: 4ex; visibility:hidden; background-color: white; padding: 4px 9px 5px 7px; border: solid #345 1px; "
onmouseover="showElem('legend');"
onmouseout="hideElem('legend');">
</div>
</div>
<span class="pre noprint docinfo top">[<a href="../html/" title="Document search and retrieval page">Docs</a>] [<a href="/rfc/rfc1459.txt" title="Plaintext version of this document">txt</a>|<a href="/pdf/rfc1459" title="PDF version of this document">pdf</a>] </span><br />
<span class="pre noprint docinfo"> </span><br />
<span class="pre noprint docinfo">Updated by: <a href="./rfc2810">2810</a>, <a href="./rfc2811">2811</a>, <a href="./rfc2812">2812</a>, <a href="./rfc2813">2813</a> EXPERIMENTAL</span><br />
<span class="pre noprint docinfo"> </span><br />
<pre>
Network Working Group J. Oikarinen
Request for Comments: 1459 D. Reed
May 1993
<span class="h1">Internet Relay Chat Protocol</span>
Status of This Memo
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.
Abstract
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.
Table of Contents
<a href="#section-1">1</a>. INTRODUCTION ............................................... <a href="#page-4">4</a>
<a href="#section-1.1">1.1</a> Servers ................................................ <a href="#page-4">4</a>
<a href="#section-1.2">1.2</a> Clients ................................................ <a href="#page-5">5</a>
<a href="#section-1.2.1">1.2.1</a> Operators .......................................... <a href="#page-5">5</a>
<a href="#section-1.3">1.3</a> Channels ................................................ <a href="#page-5">5</a>
<a href="#section-1.3.1">1.3.1</a> Channel Operators .................................... <a href="#page-6">6</a>
<a href="#section-2">2</a>. THE IRC SPECIFICATION ....................................... <a href="#page-7">7</a>
<a href="#section-2.1">2.1</a> Overview ................................................ <a href="#page-7">7</a>
<a href="#section-2.2">2.2</a> Character codes ......................................... <a href="#page-7">7</a>
<a href="#section-2.3">2.3</a> Messages ................................................ <a href="#page-7">7</a>
<a href="#section-2.3.1">2.3.1</a> Message format in 'pseudo' BNF .................... <a href="#page-8">8</a>
<a href="#section-2.4">2.4</a> Numeric replies ......................................... <a href="#page-10">10</a>
<a href="#section-3">3</a>. IRC Concepts ................................................ <a href="#page-10">10</a>
<a href="#section-3.1">3.1</a> One-to-one communication ................................ <a href="#page-10">10</a>
<a href="#section-3.2">3.2</a> One-to-many ............................................. <a href="#page-11">11</a>
<a href="#section-3.2.1">3.2.1</a> To a list .......................................... <a href="#page-11">11</a>
<a href="#section-3.2.2">3.2.2</a> To a group (channel) ............................... <a href="#page-11">11</a>
<a href="#section-3.2.3">3.2.3</a> To a host/server mask .............................. <a href="#page-12">12</a>
<a href="#section-3.3">3.3</a> One to all .............................................. <a href="#page-12">12</a>
<span class="grey">Oikarinen & Reed [Page 1]</span>
</pre><pre class='newpage'><a name="page-2" id="page-2" href="#page-2" class="invisible"> </a>
<span class="grey"><a href="./rfc1459">RFC 1459</a> Internet Relay Chat Protocol May 1993</span>
<a href="#section-3.3.1">3.3.1</a> Client to Client ................................... <a href="#page-12">12</a>
<a href="#section-3.3.2">3.3.2</a> Clients to Server .................................. <a href="#page-12">12</a>
<a href="#section-3.3.3">3.3.3</a> Server to Server ................................... <a href="#page-12">12</a>
<a href="#section-4">4</a>. MESSAGE DETAILS ............................................. <a href="#page-13">13</a>
<a href="#section-4.1">4.1</a> Connection Registration ................................. <a href="#page-13">13</a>
<a href="#section-4.1.1">4.1.1</a> Password message ................................... <a href="#page-14">14</a>
<a href="#section-4.1.2">4.1.2</a> Nickname message ................................... <a href="#page-14">14</a>
<a href="#section-4.1.3">4.1.3</a> User message ....................................... <a href="#page-15">15</a>
<a href="#section-4.1.4">4.1.4</a> Server message ..................................... <a href="#page-16">16</a>
<a href="#section-4.1.5">4.1.5</a> Operator message ................................... <a href="#page-17">17</a>
<a href="#section-4.1.6">4.1.6</a> Quit message ....................................... <a href="#page-17">17</a>
<a href="#section-4.1.7">4.1.7</a> Server Quit message ................................ <a href="#page-18">18</a>
<a href="#section-4.2">4.2</a> Channel operations ...................................... <a href="#page-19">19</a>
<a href="#section-4.2.1">4.2.1</a> Join message ....................................... <a href="#page-19">19</a>
<a href="#section-4.2.2">4.2.2</a> Part message ....................................... <a href="#page-20">20</a>
<a href="#section-4.2.3">4.2.3</a> Mode message ....................................... <a href="#page-21">21</a>
<a href="#section-4.2.3.1">4.2.3.1</a> Channel modes ................................. <a href="#page-21">21</a>
<a href="#section-4.2.3.2">4.2.3.2</a> User modes .................................... <a href="#page-22">22</a>
<a href="#section-4.2.4">4.2.4</a> Topic message ...................................... <a href="#page-23">23</a>
<a href="#section-4.2.5">4.2.5</a> Names message ...................................... <a href="#page-24">24</a>
<a href="#section-4.2.6">4.2.6</a> List message ....................................... <a href="#page-24">24</a>
<a href="#section-4.2.7">4.2.7</a> Invite message ..................................... <a href="#page-25">25</a>
<a href="#section-4.2.8">4.2.8</a> Kick message ....................................... <a href="#page-25">25</a>
<a href="#section-4.3">4.3</a> Server queries and commands ............................. <a href="#page-26">26</a>
<a href="#section-4.3.1">4.3.1</a> Version message .................................... <a href="#page-26">26</a>
<a href="#section-4.3.2">4.3.2</a> Stats message ...................................... <a href="#page-27">27</a>
<a href="#section-4.3.3">4.3.3</a> Links message ...................................... <a href="#page-28">28</a>
<a href="#section-4.3.4">4.3.4</a> Time message ....................................... <a href="#page-29">29</a>
<a href="#section-4.3.5">4.3.5</a> Connect message .................................... <a href="#page-29">29</a>
<a href="#section-4.3.6">4.3.6</a> Trace message ...................................... <a href="#page-30">30</a>
<a href="#section-4.3.7">4.3.7</a> Admin message ...................................... <a href="#page-31">31</a>
<a href="#section-4.3.8">4.3.8</a> Info message ....................................... <a href="#page-31">31</a>
<a href="#section-4.4">4.4</a> Sending messages ........................................ <a href="#page-32">32</a>
<a href="#section-4.4.1">4.4.1</a> Private messages ................................... <a href="#page-32">32</a>
<a href="#section-4.4.2">4.4.2</a> Notice messages .................................... <a href="#page-33">33</a>
<a href="#section-4.5">4.5</a> User-based queries ...................................... <a href="#page-33">33</a>
<a href="#section-4.5.1">4.5.1</a> Who query .......................................... <a href="#page-33">33</a>
<a href="#section-4.5.2">4.5.2</a> Whois query ........................................ <a href="#page-34">34</a>
<a href="#section-4.5.3">4.5.3</a> Whowas message ..................................... <a href="#page-35">35</a>
<a href="#section-4.6">4.6</a> Miscellaneous messages .................................. <a href="#page-35">35</a>
<a href="#section-4.6.1">4.6.1</a> Kill message ....................................... <a href="#page-36">36</a>
<a href="#section-4.6.2">4.6.2</a> Ping message ....................................... <a href="#page-37">37</a>
<a href="#section-4.6.3">4.6.3</a> Pong message ....................................... <a href="#page-37">37</a>
<a href="#section-4.6.4">4.6.4</a> Error message ...................................... <a href="#page-38">38</a>
<a href="#section-5">5</a>. OPTIONAL MESSAGES ........................................... <a href="#page-38">38</a>
<a href="#section-5.1">5.1</a> Away message ............................................ <a href="#page-38">38</a>
<a href="#section-5.2">5.2</a> Rehash command .......................................... <a href="#page-39">39</a>
<a href="#section-5.3">5.3</a> Restart command ......................................... <a href="#page-39">39</a>
<span class="grey">Oikarinen & Reed [Page 2]</span>
</pre><pre class='newpage'><a name="page-3" id="page-3" href="#page-3" class="invisible"> </a>
<span class="grey"><a href="./rfc1459">RFC 1459</a> Internet Relay Chat Protocol May 1993</span>
<a href="#section-5.4">5.4</a> Summon message .......................................... <a href="#page-40">40</a>
<a href="#section-5.5">5.5</a> Users message ........................................... <a href="#page-40">40</a>
<a href="#section-5.6">5.6</a> Operwall command ........................................ <a href="#page-41">41</a>
<a href="#section-5.7">5.7</a> Userhost message ........................................ <a href="#page-42">42</a>
<a href="#section-5.8">5.8</a> Ison message ............................................ <a href="#page-42">42</a>
<a href="#section-6">6</a>. REPLIES ..................................................... <a href="#page-43">43</a>
<a href="#section-6.1">6.1</a> Error Replies ........................................... <a href="#page-43">43</a>
<a href="#section-6.2">6.2</a> Command responses ....................................... <a href="#page-48">48</a>
<a href="#section-6.3">6.3</a> Reserved numerics ....................................... <a href="#page-56">56</a>
<a href="#section-7">7</a>. Client and server authentication ............................ <a href="#page-56">56</a>
<a href="#section-8">8</a>. Current Implementations Details ............................. <a href="#page-56">56</a>
<a href="#section-8.1">8.1</a> Network protocol: TCP ................................... <a href="#page-57">57</a>
<a href="#section-8.1.1">8.1.1</a> Support of Unix sockets ............................ <a href="#page-57">57</a>
<a href="#section-8.2">8.2</a> Command Parsing ......................................... <a href="#page-57">57</a>
<a href="#section-8.3">8.3</a> Message delivery ........................................ <a href="#page-57">57</a>
<a href="#section-8.4">8.4</a> Connection 'Liveness' ................................... <a href="#page-58">58</a>
<a href="#section-8.5">8.5</a> Establishing a server-client connection ................. <a href="#page-58">58</a>
<a href="#section-8.6">8.6</a> Establishing a server-server connection ................. <a href="#page-58">58</a>
<a href="#section-8.6.1">8.6.1</a> State information exchange when connecting ......... <a href="#page-59">59</a>
<a href="#section-8.7">8.7</a> Terminating server-client connections ................... <a href="#page-59">59</a>
<a href="#section-8.8">8.8</a> Terminating server-server connections ................... <a href="#page-59">59</a>
<a href="#section-8.9">8.9</a> Tracking nickname changes ............................... <a href="#page-60">60</a>
<a href="#section-8.10">8.10</a> Flood control of clients ............................... <a href="#page-60">60</a>
<a href="#section-8.11">8.11</a> Non-blocking lookups ................................... <a href="#page-61">61</a>
<a href="#section-8.11.1">8.11.1</a> Hostname (DNS) lookups ............................ <a href="#page-61">61</a>
<a href="#section-8.11.2">8.11.2</a> Username (Ident) lookups .......................... <a href="#page-61">61</a>
<a href="#section-8.12">8.12</a> Configuration file ..................................... <a href="#page-61">61</a>
<a href="#section-8.12.1">8.12.1</a> Allowing clients to connect ....................... <a href="#page-62">62</a>
<a href="#section-8.12.2">8.12.2</a> Operators ......................................... <a href="#page-62">62</a>
<a href="#section-8.12.3">8.12.3</a> Allowing servers to connect ....................... <a href="#page-62">62</a>
<a href="#section-8.12.4">8.12.4</a> Administrivia ..................................... <a href="#page-63">63</a>
<a href="#section-8.13">8.13</a> Channel membership ..................................... <a href="#page-63">63</a>
<a href="#section-9">9</a>. Current problems ............................................ <a href="#page-63">63</a>
<a href="#section-9.1">9.1</a> Scalability ............................................. <a href="#page-63">63</a>
<a href="#section-9.2">9.2</a> Labels .................................................. <a href="#page-63">63</a>
<a href="#section-9.2.1">9.2.1</a> Nicknames .......................................... <a href="#page-63">63</a>
<a href="#section-9.2.2">9.2.2</a> Channels ........................................... <a href="#page-64">64</a>
<a href="#section-9.2.3">9.2.3</a> Servers ............................................ <a href="#page-64">64</a>
<a href="#section-9.3">9.3</a> Algorithms .............................................. <a href="#page-64">64</a>
<a href="#section-10">10</a>. Support and availability ................................... <a href="#page-64">64</a>
<a href="#section-11">11</a>. Security Considerations .................................... <a href="#page-65">65</a>
<a href="#section-12">12</a>. Authors' Addresses ......................................... <a href="#page-65">65</a>
<span class="grey">Oikarinen & Reed [Page 3]</span>
</pre><pre class='newpage'><a name="page-4" id="page-4" href="#page-4" class="invisible"> </a>
<span class="grey"><a href="./rfc1459">RFC 1459</a> Internet Relay Chat Protocol May 1993</span>
<span class="h2"><a name="section-1">1</a>. INTRODUCTION</span>
The IRC (Internet Relay Chat) protocol has been designed over a
number of years for use with text based conferencing. This document
describes the current IRC protocol.
The IRC protocol has been developed on systems using the TCP/IP
network protocol, although there is no requirement that this remain
the only sphere in which it operates.
IRC itself is a teleconferencing system, which (through the use of
the client-server model) is well-suited to running on many machines
in a distributed fashion. A typical setup involves a single process
(the server) forming a central point for clients (or other servers)
to connect to, performing the required message delivery/multiplexing
and other functions.
<span class="h3"><a name="section-1.1">1.1</a> Servers</span>
The server forms the backbone of IRC, providing a point to which
clients may connect to to talk to each other, and a point for other
servers to connect to, forming an IRC network. The only network
configuration allowed for IRC servers is that of a spanning tree [see
Fig. 1] where each server acts as a central node for the rest of the
net it sees.
[ Server 15 ] [ Server 13 ] [ Server 14]
/ \ /
/ \ /
[ Server 11 ] ------ [ Server 1 ] [ Server 12]
/ \ /
/ \ /
[ Server 2 ] [ Server 3 ]
/ \ \
/ \ \
[ Server 4 ] [ Server 5 ] [ Server 6 ]
/ | \ /
/ | \ /
/ | \____ /
/ | \ /
[ Server 7 ] [ Server 8 ] [ Server 9 ] [ Server 10 ]
:
[ etc. ]
:
[ Fig. 1. Format of IRC server network ]
<span class="grey">Oikarinen & Reed [Page 4]</span>
</pre><pre class='newpage'><a name="page-5" id="page-5" href="#page-5" class="invisible"> </a>
<span class="grey"><a href="./rfc1459">RFC 1459</a> Internet Relay Chat Protocol May 1993</span>
<span class="h3"><a name="section-1.2">1.2</a> Clients</span>
A client is anything connecting to a server that is not another
server. Each client is distinguished from other clients by a unique
nickname having a maximum length of nine (9) characters. See the
protocol grammar rules for what may and may not be used in a
nickname. In addition to the nickname, all servers must have the
following information about all clients: the real name of the host
that the client is running on, the username of the client on that
host, and the server to which the client is connected.
<span class="h4"><a name="section-1.2.1">1.2.1</a> Operators</span>
To allow a reasonable amount of order to be kept within the IRC
network, a special class of clients (operators) is allowed to perform
general maintenance functions on the network. Although the powers
granted to an operator can be considered as 'dangerous', they are
nonetheless required. Operators should be able to perform basic
network tasks such as disconnecting and reconnecting servers as
needed to prevent long-term use of bad network routing. In
recognition of this need, the protocol discussed herein provides for
operators only to be able to perform such functions. See sections
4.1.7 (SQUIT) and 4.3.5 (CONNECT).
A more controversial power of operators is the ability to remove a
user from the connected network by 'force', i.e. operators are able
to close the connection between any client and server. The
justification for this is delicate since its abuse is both
destructive and annoying. For further details on this type of
action, see <a href="#section-4.6.1">section 4.6.1</a> (KILL).
<span class="h3"><a name="section-1.3">1.3</a> Channels</span>
A channel is a named group of one or more clients which will all
receive messages addressed to that channel. The channel is created
implicitly when the first client joins it, and the channel ceases to
exist when the last client leaves it. While channel exists, any
client can reference the channel using the name of the channel.
Channels names are strings (beginning with a '&' or '#' character) of
length up to 200 characters. Apart from the the requirement that the
first character being either '&' or '#'; the only restriction on a
channel name is that it may not contain any spaces (' '), a control G
(^G or ASCII 7), or a comma (',' which is used as a list item
separator by the protocol).
There are two types of channels allowed by this protocol. One is a
distributed channel which is known to all the servers that are
<span class="grey">Oikarinen & Reed [Page 5]</span>
</pre><pre class='newpage'><a name="page-6" id="page-6" href="#page-6" class="invisible"> </a>
<span class="grey"><a href="./rfc1459">RFC 1459</a> Internet Relay Chat Protocol May 1993</span>
connected to the network. These channels are marked by the first
character being a only clients on the server where it exists may join
it. These are distinguished by a leading '&' character. On top of
these two types, there are the various channel modes available to
alter the characteristics of individual channels. See <a href="#section-4.2.3">section 4.2.3</a>
(MODE command) for more details on this.
To create a new channel or become part of an existing channel, a user
is required to JOIN the channel. If the channel doesn't exist prior
to joining, the channel is created and the creating user becomes a
channel operator. If the channel already exists, whether or not your
request to JOIN that channel is honoured depends on the current modes
of the channel. For example, if the channel is invite-only, (+i),
then you may only join if invited. As part of the protocol, a user
may be a part of several channels at once, but a limit of ten (10)
channels is recommended as being ample for both experienced and
novice users. See <a href="#section-8.13">section 8.13</a> for more information on this.
If the IRC network becomes disjoint because of a split between two
servers, the channel on each side is only composed of those clients
which are connected to servers on the respective sides of the split,
possibly ceasing to exist on one side of the split. When the split
is healed, the connecting servers announce to each other who they
think is in each channel and the mode of that channel. If the
channel exists on both sides, the JOINs and MODEs are interpreted in
an inclusive manner so that both sides of the new connection will
agree about which clients are in the channel and what modes the
channel has.
<span class="h4"><a name="section-1.3.1">1.3.1</a> Channel Operators</span>
The channel operator (also referred to as a "chop" or "chanop") on a
given channel is considered to 'own' that channel. In recognition of
this status, channel operators are endowed with certain powers which
enable them to keep control and some sort of sanity in their channel.
As an owner of a channel, a channel operator is not required to have
reasons for their actions, although if their actions are generally
antisocial or otherwise abusive, it might be reasonable to ask an IRC
operator to intervene, or for the usersjust leave and go elsewhere
and form their own channel.
The commands which may only be used by channel operators are:
KICK - Eject a client from the channel
MODE - Change the channel's mode
INVITE - Invite a client to an invite-only channel (mode +i)
TOPIC - Change the channel topic in a mode +t channel
<span class="grey">Oikarinen & Reed [Page 6]</span>
</pre><pre class='newpage'><a name="page-7" id="page-7" href="#page-7" class="invisible"> </a>
<span class="grey"><a href="./rfc1459">RFC 1459</a> Internet Relay Chat Protocol May 1993</span>
A channel operator is identified by the '@' symbol next to their
nickname whenever it is associated with a channel (ie replies to the
NAMES, WHO and WHOIS commands).
<span class="h2"><a name="section-2">2</a>. The IRC Specification</span>
<span class="h3"><a name="section-2.1">2.1</a> Overview</span>
The protocol as described herein is for use both with server to
server and client to server connections. There are, however, more
restrictions on client connections (which are considered to be
untrustworthy) than on server connections.
<span class="h3"><a name="section-2.2">2.2</a> Character codes</span>
No specific character set is specified. The protocol is based on a a
set of codes which are composed of eight (8) bits, making up an
octet. Each message may be composed of any number of these octets;
however, some octet values are used for control codes which act as
message delimiters.
Regardless of being an 8-bit protocol, the delimiters and keywords
are such that protocol is mostly usable from USASCII terminal and a
telnet connection.
Because of IRC's scandanavian origin, the characters {}| are
considered to be the lower case equivalents of the characters []\,
respectively. This is a critical issue when determining the
equivalence of two nicknames.
<span class="h3"><a name="section-2.3">2.3</a> Messages</span>
Servers and clients send eachother messages which may or may not
generate a reply. If the message contains a valid command, as
described in later sections, the client should expect a reply as
specified but it is not advised to wait forever for the reply; client
to server and server to server communication is essentially
asynchronous in nature.
Each IRC message may consist of up to three main parts: the prefix
(optional), the command, and the command parameters (of which there
may be up to 15). The prefix, command, and all parameters are
separated by one (or more) ASCII space character(s) (0x20).
The presence of a prefix is indicated with a single leading ASCII
colon character (':', 0x3b), which must be the first character of the
message itself. There must be no gap (whitespace) between the colon
and the prefix. The prefix is used by servers to indicate the true
<span class="grey">Oikarinen & Reed [Page 7]</span>
</pre><pre class='newpage'><a name="page-8" id="page-8" href="#page-8" class="invisible"> </a>
<span class="grey"><a href="./rfc1459">RFC 1459</a> Internet Relay Chat Protocol May 1993</span>
origin of the message. If the prefix is missing from the message, it
is assumed to have originated from the connection from which it was
received. Clients should not use prefix when sending a message from
themselves; if they use a prefix, the only valid prefix is the
registered nickname associated with the client. If the source
identified by the prefix cannot be found from the server's internal
database, or if the source is registered from a different link than
from which the message arrived, the server must ignore the message
silently.
The command must either be a valid IRC command or a three (3) digit
number represented in ASCII text.
IRC messages are always lines of characters terminated with a CR-LF
(Carriage Return - Line Feed) pair, and these messages shall not
exceed 512 characters in length, counting all characters including
the trailing CR-LF. Thus, there are 510 characters maximum allowed
for the command and its parameters. There is no provision for
continuation message lines. See <a href="#section-7">section 7</a> for more details about
current implementations.
<span class="h4"><a name="section-2.3.1">2.3.1</a> Message format in 'pseudo' BNF</span>
The protocol messages must be extracted from the contiguous stream of
octets. The current solution is to designate two characters, CR and
LF, as message separators. Empty messages are silently ignored,
which permits use of the sequence CR-LF between messages
without extra problems.
The extracted message is parsed into the components <prefix>,
<command> and list of parameters matched either by <middle> or
<trailing> components.
The BNF representation for this is:
<message> ::= [':' <prefix> <SPACE> ] <command> <params> <crlf>
<prefix> ::= <servername> | <nick> [ '!' <user> ] [ '@' <host> ]
<command> ::= <letter> { <letter> } | <number> <number> <number>
<SPACE> ::= ' ' { ' ' }
<params> ::= <SPACE> [ ':' <trailing> | <middle> <params> ]
<middle> ::= <Any *non-empty* sequence of octets not including SPACE
or NUL or CR or LF, the first of which may not be ':'>
<trailing> ::= <Any, possibly *empty*, sequence of octets not including
NUL or CR or LF>
<crlf> ::= CR LF
<span class="grey">Oikarinen & Reed [Page 8]</span>
</pre><pre class='newpage'><a name="page-9" id="page-9" href="#page-9" class="invisible"> </a>
<span class="grey"><a href="./rfc1459">RFC 1459</a> Internet Relay Chat Protocol May 1993</span>
NOTES:
1) <SPACE> is consists only of SPACE character(s) (0x20).
Specially notice that TABULATION, and all other control
characters are considered NON-WHITE-SPACE.
2) After extracting the parameter list, all parameters are equal,
whether matched by <middle> or <trailing>. <Trailing> is just
a syntactic trick to allow SPACE within parameter.
3) The fact that CR and LF cannot appear in parameter strings is
just artifact of the message framing. This might change later.
4) The NUL character is not special in message framing, and
basically could end up inside a parameter, but as it would
cause extra complexities in normal C string handling. Therefore
NUL is not allowed within messages.
5) The last parameter may be an empty string.
6) Use of the extended prefix (['!' <user> ] ['@' <host> ]) must
not be used in server to server communications and is only
intended for server to client messages in order to provide
clients with more useful information about who a message is
from without the need for additional queries.
Most protocol messages specify additional semantics and syntax for
the extracted parameter strings dictated by their position in the
list. For example, many server commands will assume that the first
parameter after the command is the list of targets, which can be
described with:
<target> ::= <to> [ "," <target> ]
<to> ::= <channel> | <user> '@' <servername> | <nick> | <mask>
<channel> ::= ('#' | '&') <chstring>
<servername> ::= <host>
<host> ::= see <a href="./rfc952">RFC 952</a> [DNS:4] for details on allowed hostnames
<nick> ::= <letter> { <letter> | <number> | <special> }
<mask> ::= ('#' | '$') <chstring>
<chstring> ::= <any 8bit code except SPACE, BELL, NUL, CR, LF and
comma (',')>
Other parameter syntaxes are:
<user> ::= <nonwhite> { <nonwhite> }
<letter> ::= 'a' ... 'z' | 'A' ... 'Z'
<number> ::= '0' ... '9'
<special> ::= '-' | '[' | ']' | '\' | '`' | '^' | '{' | '}'
<span class="grey">Oikarinen & Reed [Page 9]</span>
</pre><pre class='newpage'><a name="page-10" id="page-10" href="#page-10" class="invisible"> </a>
<span class="grey"><a href="./rfc1459">RFC 1459</a> Internet Relay Chat Protocol May 1993</span>
<nonwhite> ::= <any 8bit code except SPACE (0x20), NUL (0x0), CR
(0xd), and LF (0xa)>
<span class="h3"><a name="section-2.4">2.4</a> Numeric replies</span>
Most of the messages sent to the server generate a reply of some
sort. The most common reply is the numeric reply, used for both
errors and normal replies. The numeric reply must be sent as one
message consisting of the sender prefix, the three digit numeric, and
the target of the reply. A numeric reply is not allowed to originate
from a client; any such messages received by a server are silently
dropped. In all other respects, a numeric reply is just like a normal
message, except that the keyword is made up of 3 numeric digits
rather than a string of letters. A list of different replies is
supplied in <a href="#section-6">section 6</a>.
<span class="h2"><a name="section-3">3</a>. IRC Concepts.</span>
This section is devoted to describing the actual concepts behind the
organization of the IRC protocol and how the current
implementations deliver different classes of messages.
1--\
A D---4
2--/ \ /
B----C
/ \
3 E
Servers: A, B, C, D, E Clients: 1, 2, 3, 4
[ Fig. 2. Sample small IRC network ]
<span class="h3"><a name="section-3.1">3.1</a> One-to-one communication</span>
Communication on a one-to-one basis is usually only performed by
clients, since most server-server traffic is not a result of servers
talking only to each other. To provide a secure means for clients to
talk to each other, it is required that all servers be able to send a
message in exactly one direction along the spanning tree in order to
reach any client. The path of a message being delivered is the
shortest path between any two points on the spanning tree.
The following examples all refer to Figure 2 above.
<span class="grey">Oikarinen & Reed [Page 10]</span>
</pre><pre class='newpage'><a name="page-11" id="page-11" href="#page-11" class="invisible"> </a>
<span class="grey"><a href="./rfc1459">RFC 1459</a> Internet Relay Chat Protocol May 1993</span>
Example 1:
A message between clients 1 and 2 is only seen by server A, which
sends it straight to client 2.
Example 2:
A message between clients 1 and 3 is seen by servers A & B, and
client 3. No other clients or servers are allowed see the message.
Example 3:
A message between clients 2 and 4 is seen by servers A, B, C & D
and client 4 only.
<span class="h3"><a name="section-3.2">3.2</a> One-to-many</span>
The main goal of IRC is to provide a forum which allows easy and
efficient conferencing (one to many conversations). IRC offers
several means to achieve this, each serving its own purpose.
<span class="h4"><a name="section-3.2.1">3.2.1</a> To a list</span>
The least efficient style of one-to-many conversation is through
clients talking to a 'list' of users. How this is done is almost
self explanatory: the client gives a list of destinations to which
the message is to be delivered and the server breaks it up and
dispatches a separate copy of the message to each given destination.
This isn't as efficient as using a group since the destination list
is broken up and the dispatch sent without checking to make sure
duplicates aren't sent down each path.
<span class="h4"><a name="section-3.2.2">3.2.2</a> To a group (channel)</span>
In IRC the channel has a role equivalent to that of the multicast
group; their existence is dynamic (coming and going as people join
and leave channels) and the actual conversation carried out on a
channel is only sent to servers which are supporting users on a given
channel. If there are multiple users on a server in the same
channel, the message text is sent only once to that server and then
sent to each client on the channel. This action is then repeated for
each client-server combination until the original message has fanned
out and reached each member of the channel.
The following examples all refer to Figure 2.
Example 4:
Any channel with 1 client in it. Messages to the channel go to the
server and then nowhere else.
<span class="grey">Oikarinen & Reed [Page 11]</span>
</pre><pre class='newpage'><a name="page-12" id="page-12" href="#page-12" class="invisible"> </a>
<span class="grey"><a href="./rfc1459">RFC 1459</a> Internet Relay Chat Protocol May 1993</span>
Example 5:
2 clients in a channel. All messages traverse a path as if they
were private messages between the two clients outside a channel.
Example 6:
Clients 1, 2 and 3 in a channel. All messages to the channel are
sent to all clients and only those servers which must be traversed
by the message if it were a private message to a single client. If
client 1 sends a message, it goes back to client 2 and then via
server B to client 3.
<span class="h4"><a name="section-3.2.3">3.2.3</a> To a host/server mask</span>
To provide IRC operators with some mechanism to send messages to a
large body of related users, host and server mask messages are
provided. These messages are sent to users whose host or server
information match that of the mask. The messages are only sent to
locations where users are, in a fashion similar to that of channels.
<span class="h3"><a name="section-3.3">3.3</a> One-to-all</span>
The one-to-all type of message is better described as a broadcast
message, sent to all clients or servers or both. On a large network
of users and servers, a single message can result in a lot of traffic
being sent over the network in an effort to reach all of the desired
destinations.
For some messages, there is no option but to broadcast it to all
servers so that the state information held by each server is
reasonably consistent between servers.
<span class="h4"><a name="section-3.3.1">3.3.1</a> Client-to-Client</span>
There is no class of message which, from a single message, results in
a message being sent to every other client.
<span class="h4"><a name="section-3.3.2">3.3.2</a> Client-to-Server</span>
Most of the commands which result in a change of state information
(such as channel membership, channel mode, user status, etc) must be
sent to all servers by default, and this distribution may not be
changed by the client.
<span class="h4"><a name="section-3.3.3">3.3.3</a> Server-to-Server.</span>
While most messages between servers are distributed to all 'other'
servers, this is only required for any message that affects either a
user, channel or server. Since these are the basic items found in
<span class="grey">Oikarinen & Reed [Page 12]</span>
</pre><pre class='newpage'><a name="page-13" id="page-13" href="#page-13" class="invisible"> </a>
<span class="grey"><a href="./rfc1459">RFC 1459</a> Internet Relay Chat Protocol May 1993</span>
IRC, nearly all messages originating from a server are broadcast to
all other connected servers.
<span class="h2"><a name="section-4">4</a>. Message details</span>
On the following pages are descriptions of each message recognized by
the IRC server and client. All commands described in this section
must be implemented by any server for this protocol.
Where the reply ERR_NOSUCHSERVER is listed, it means that the
<server> parameter could not be found. The server must not send any
other replies after this for that command.
The server to which a client is connected is required to parse the
complete message, returning any appropriate errors. If the server
encounters a fatal error while parsing a message, an error must be
sent back to the client and the parsing terminated. A fatal error
may be considered to be incorrect command, a destination which is
otherwise unknown to the server (server, nick or channel names fit
this category), not enough parameters or incorrect privileges.
If a full set of parameters is presented, then each must be checked
for validity and appropriate responses sent back to the client. In
the case of messages which use parameter lists using the comma as an
item separator, a reply must be sent for each item.
In the examples below, some messages appear using the full format:
:Name COMMAND parameter list
Such examples represent a message from "Name" in transit between
servers, where it is essential to include the name of the original
sender of the message so remote servers may send back a reply along
the correct path.
<span class="h3"><a name="section-4.1">4.1</a> Connection Registration</span>
The commands described here are used to register a connection with an
IRC server as either a user or a server as well as correctly
disconnect.
A "PASS" command is not required for either client or server
connection to be registered, but it must precede the server message
or the latter of the NICK/USER combination. It is strongly
recommended that all server connections have a password in order to
give some level of security to the actual connections. The
recommended order for a client to register is as follows:
<span class="grey">Oikarinen & Reed [Page 13]</span>
</pre><pre class='newpage'><a name="page-14" id="page-14" href="#page-14" class="invisible"> </a>
<span class="grey"><a href="./rfc1459">RFC 1459</a> Internet Relay Chat Protocol May 1993</span>
1. Pass message
2. Nick message
3. User message
<span class="h4"><a name="section-4.1.1">4.1.1</a> Password message</span>
Command: PASS
Parameters: <password>
The PASS command is used to set a 'connection password'. The
password can and must be set before any attempt to register the
connection is made. Currently this requires that clients send a PASS
command before sending the NICK/USER combination and servers *must*
send a PASS command before any SERVER command. The password supplied
must match the one contained in the C/N lines (for servers) or I
lines (for clients). It is possible to send multiple PASS commands
before registering but only the last one sent is used for
verification and it may not be changed once registered. Numeric
Replies:
ERR_NEEDMOREPARAMS ERR_ALREADYREGISTRED
Example:
PASS secretpasswordhere
<span class="h4"><a name="section-4.1.2">4.1.2</a> Nick message</span>
Command: NICK
Parameters: <nickname> [ <hopcount> ]
NICK message is used to give user a nickname or change the previous
one. The <hopcount> parameter is only used by servers to indicate
how far away a nick is from its home server. A local connection has
a hopcount of 0. If supplied by a client, it must be ignored.
If a NICK message arrives at a server which already knows about an
identical nickname for another client, a nickname collision occurs.
As a result of a nickname collision, all instances of the nickname
are removed from the server's database, and a KILL command is issued
to remove the nickname from all other server's database. If the NICK
message causing the collision was a nickname change, then the
original (old) nick must be removed as well.
If the server recieves an identical NICK from a client which is
directly connected, it may issue an ERR_NICKCOLLISION to the local
client, drop the NICK command, and not generate any kills.
<span class="grey">Oikarinen & Reed [Page 14]</span>
</pre><pre class='newpage'><a name="page-15" id="page-15" href="#page-15" class="invisible"> </a>
<span class="grey"><a href="./rfc1459">RFC 1459</a> Internet Relay Chat Protocol May 1993</span>
Numeric Replies:
ERR_NONICKNAMEGIVEN ERR_ERRONEUSNICKNAME
ERR_NICKNAMEINUSE ERR_NICKCOLLISION
Example:
NICK Wiz ; Introducing new nick "Wiz".
:WiZ NICK Kilroy ; WiZ changed his nickname to Kilroy.
<span class="h4"><a name="section-4.1.3">4.1.3</a> User message</span>
Command: USER
Parameters: <username> <hostname> <servername> <realname>
The USER message is used at the beginning of connection to specify
the username, hostname, servername and realname of s new user. It is
also used in communication between servers to indicate new user
arriving on IRC, since only after both USER and NICK have been
received from a client does a user become registered.
Between servers USER must to be prefixed with client's NICKname.
Note that hostname and servername are normally ignored by the IRC
server when the USER command comes from a directly connected client
(for security reasons), but they are used in server to server
communication. This means that a NICK must always be sent to a
remote server when a new user is being introduced to the rest of the
network before the accompanying USER is sent.
It must be noted that realname parameter must be the last parameter,
because it may contain space characters and must be prefixed with a
colon (':') to make sure this is recognised as such.
Since it is easy for a client to lie about its username by relying
solely on the USER message, the use of an "Identity Server" is
recommended. If the host which a user connects from has such a
server enabled the username is set to that as in the reply from the
"Identity Server".
Numeric Replies:
ERR_NEEDMOREPARAMS ERR_ALREADYREGISTRED
Examples:
USER guest tolmoon tolsun :Ronnie Reagan
<span class="grey">Oikarinen & Reed [Page 15]</span>
</pre><pre class='newpage'><a name="page-16" id="page-16" href="#page-16" class="invisible"> </a>
<span class="grey"><a href="./rfc1459">RFC 1459</a> Internet Relay Chat Protocol May 1993</span>
; User registering themselves with a
username of "guest" and real name
"Ronnie Reagan".
:testnick USER guest tolmoon tolsun :Ronnie Reagan
; message between servers with the
nickname for which the USER command
belongs to