@@ 1,176 @@
Version 2.0, January 2004
TERMS AND CONDITIONS FOR USE, REPRODUCTION, AND DISTRIBUTION
"License" shall mean the terms and conditions for use, reproduction,
and distribution as defined by Sections 1 through 9 of this document.
"Licensor" shall mean the copyright owner or entity authorized by
the copyright owner that is granting the License.
"Legal Entity" shall mean the union of the acting entity and all
other entities that control, are controlled by, or are under common
control with that entity. For the purposes of this definition,
"control" means (i) the power, direct or indirect, to cause the
direction or management of such entity, whether by contract or
otherwise, or (ii) ownership of fifty percent (50%) or more of the
outstanding shares, or (iii) beneficial ownership of such entity.
"You" (or "Your") shall mean an individual or Legal Entity
exercising permissions granted by this License.
"Source" form shall mean the preferred form for making modifications,
including but not limited to software source code, documentation
source, and configuration files.
"Object" form shall mean any form resulting from mechanical
transformation or translation of a Source form, including but
not limited to compiled object code, generated documentation,
and conversions to other media types.
"Work" shall mean the work of authorship, whether in Source or
Object form, made available under the License, as indicated by a
copyright notice that is included in or attached to the work
(an example is provided in the Appendix below).
"Derivative Works" shall mean any work, whether in Source or Object
form, that is based on (or derived from) the Work and for which the
editorial revisions, annotations, elaborations, or other modifications
represent, as a whole, an original work of authorship. For the purposes
of this License, Derivative Works shall not include works that remain
separable from, or merely link (or bind by name) to the interfaces of,
the Work and Derivative Works thereof.
"Contribution" shall mean any work of authorship, including
the original version of the Work and any modifications or additions
to that Work or Derivative Works thereof, that is intentionally
submitted to Licensor for inclusion in the Work by the copyright owner
or by an individual or Legal Entity authorized to submit on behalf of
the copyright owner. For the purposes of this definition, "submitted"
means any form of electronic, verbal, or written communication sent
to the Licensor or its representatives, including but not limited to
communication on electronic mailing lists, source code control systems,
and issue tracking systems that are managed by, or on behalf of, the
Licensor for the purpose of discussing and improving the Work, but
excluding communication that is conspicuously marked or otherwise
designated in writing by the copyright owner as "Not a Contribution."
"Contributor" shall mean Licensor and any individual or Legal Entity
on behalf of whom a Contribution has been received by Licensor and
subsequently incorporated within the Work.
2. Grant of Copyright License. Subject to the terms and conditions of
this License, each Contributor hereby grants to You a perpetual,
worldwide, non-exclusive, no-charge, royalty-free, irrevocable
copyright license to reproduce, prepare Derivative Works of,
publicly display, publicly perform, sublicense, and distribute the
Work and such Derivative Works in Source or Object form.
3. Grant of Patent License. Subject to the terms and conditions of
this License, each Contributor hereby grants to You a perpetual,
worldwide, non-exclusive, no-charge, royalty-free, irrevocable
(except as stated in this section) patent license to make, have made,
use, offer to sell, sell, import, and otherwise transfer the Work,
where such license applies only to those patent claims licensable
by such Contributor that are necessarily infringed by their
Contribution(s) alone or by combination of their Contribution(s)
with the Work to which such Contribution(s) was submitted. If You
institute patent litigation against any entity (including a
cross-claim or counterclaim in a lawsuit) alleging that the Work
or a Contribution incorporated within the Work constitutes direct
or contributory patent infringement, then any patent licenses
granted to You under this License for that Work shall terminate
as of the date such litigation is filed.
4. Redistribution. You may reproduce and distribute copies of the
Work or Derivative Works thereof in any medium, with or without
modifications, and in Source or Object form, provided that You
meet the following conditions:
(a) You must give any other recipients of the Work or
Derivative Works a copy of this License; and
(b) You must cause any modified files to carry prominent notices
stating that You changed the files; and
(c) You must retain, in the Source form of any Derivative Works
that You distribute, all copyright, patent, trademark, and
attribution notices from the Source form of the Work,
excluding those notices that do not pertain to any part of
the Derivative Works; and
(d) If the Work includes a "NOTICE" text file as part of its
distribution, then any Derivative Works that You distribute must
include a readable copy of the attribution notices contained
within such NOTICE file, excluding those notices that do not
pertain to any part of the Derivative Works, in at least one
of the following places: within a NOTICE text file distributed
as part of the Derivative Works; within the Source form or
documentation, if provided along with the Derivative Works; or,
within a display generated by the Derivative Works, if and
wherever such third-party notices normally appear. The contents
of the NOTICE file are for informational purposes only and
do not modify the License. You may add Your own attribution
notices within Derivative Works that You distribute, alongside
or as an addendum to the NOTICE text from the Work, provided
that such additional attribution notices cannot be construed
as modifying the License.
You may add Your own copyright statement to Your modifications and
may provide additional or different license terms and conditions
for use, reproduction, or distribution of Your modifications, or
for any such Derivative Works as a whole, provided Your use,
reproduction, and distribution of the Work otherwise complies with
the conditions stated in this License.
5. Submission of Contributions. Unless You explicitly state otherwise,
any Contribution intentionally submitted for inclusion in the Work
by You to the Licensor shall be under the terms and conditions of
this License, without any additional terms or conditions.
Notwithstanding the above, nothing herein shall supersede or modify
the terms of any separate license agreement you may have executed
with Licensor regarding such Contributions.
6. Trademarks. This License does not grant permission to use the trade
names, trademarks, service marks, or product names of the Licensor,
except as required for reasonable and customary use in describing the
origin of the Work and reproducing the content of the NOTICE file.
7. Disclaimer of Warranty. Unless required by applicable law or
agreed to in writing, Licensor provides the Work (and each
Contributor provides its Contributions) on an "AS IS" BASIS,
WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or
implied, including, without limitation, any warranties or conditions
of TITLE, NON-INFRINGEMENT, MERCHANTABILITY, or FITNESS FOR A
PARTICULAR PURPOSE. You are solely responsible for determining the
appropriateness of using or redistributing the Work and assume any
risks associated with Your exercise of permissions under this License.
8. Limitation of Liability. In no event and under no legal theory,
whether in tort (including negligence), contract, or otherwise,
unless required by applicable law (such as deliberate and grossly
negligent acts) or agreed to in writing, shall any Contributor be
liable to You for damages, including any direct, indirect, special,
incidental, or consequential damages of any character arising as a
result of this License or out of the use or inability to use the
Work (including but not limited to damages for loss of goodwill,
work stoppage, computer failure or malfunction, or any and all
other commercial damages or losses), even if such Contributor
has been advised of the possibility of such damages.
9. Accepting Warranty or Additional Liability. While redistributing
the Work or Derivative Works thereof, You may choose to offer,
and charge a fee for, acceptance of support, warranty, indemnity,
or other liability obligations and/or rights consistent with this
License. However, in accepting such obligations, You may act only
on Your own behalf and on Your sole responsibility, not on behalf
of any other Contributor, and only if You agree to indemnify,
defend, and hold each Contributor harmless for any liability
incurred by, or claims asserted against, such Contributor by reason
of your accepting any such warranty or additional liability.
END OF TERMS AND CONDITIONS
@@ 1,154 @@
# The SO6-3 S2S protocol
This document describes and specify the *SO6-3*. This protocol is meant to keep
in sync IRC servers that are part of the same IRC network.
Although SO6-3 is primarily used by ellidri, and is developed side-by-side with
this server, it is meant to be implemented by any IRC server that has
To understand this document, it is necessary for the reader to have basic
knowledge on what a IRC network is, how it operates and what are its components.
For a good introduction on this points, see [modern.ircdocs.horse], section
"IRC Concepts". Although not all information in the linked section correlates
with what is described in this document, it provides enough knowledge to
The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", "SHOULD",
"SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this document are to be
interpreted as described in [RFC 2119].
Table of contents:
1. Protocol format
1. List of commands
1. Connection life cycle
1. Bootstrap process
99. Appendix and references
## N. Protocol format
A [character] is a Unicode code point other than `U+0000`. Although some
code points (for example, combining accents) do not correspond to characters in
an intuitive sense, all code points except `U+0000` count as characters for
purposes of this spec.
A [space] (` `) is `U+0020`.
An [at] (`@`) is `U+0040`.
A [colon] (`:`) is `U+003A`.
A [newline] (`\n`) is `U+000A`.
A [carriage return] (`\r`) is `U+000D`.
A [digit] (`0`..`9`) is one of `U+0030` to `U+0039` included.
An [ASCII letter] (`A`..`Z` and `a`..`z`) is one of `U+0041` to `U+005A`
included, or one of `U+0061` to `U+007A` included.
A [word] is a sequence of [characters] other than [space].
A [line ending] is a [newline], a [carriage return] not followed by a
[newline], or a [carriage return] and a following [newline].
A [line] is a sequence of zero or more [characters] other than [newline]
or [carriage return], followed by a [line ending].
A [tag string] is a [word] that starts with an [at].
A [source] is a [word] that starts with a [colon].
A [command] is a [word] made of either 3 [digits], or 1 or more [ASCII
A [parameter] is either a [word] that doesn't start with a [colon], or a
sequence of [characters] that starts with a [colon] up to a [newline] or
A [message] is a [line] that contains, and only contains the following:
- Optionally, a [tag string] followed by a [space], then,
- Optionally, a [source] followed by a [space], then,
- A [command], then,
- Optionally, a [space] followed by 1 to 15 [parameters], each separated by
Here are some examples of messages and how the parameters would be represented
as [JSON] lists:
:irc.example.com CAP * LIST :\r\n -> ["*", "LIST", ""]
CAP * LS :multi-prefix sasl\n -> ["*", "LS", "multi-prefix sasl"]
CAP REQ :sasl message-tags foo\r\n -> ["REQ", "sasl message-tags foo"]
@msgid=2 :dan!d@localhost PRIVMSG #chan :Hey!\r\n ->
:dan!d@localhost PRIVMSG #chan Hey!\n -> ["#chan", "Hey!"]
An [S2S stream] is a [TLS-encrypted][TLS] [TCP stream][TCP] that is entirely
made of [messages]. While the [TLS] link points to TLS version 1.3, other
versions of the protocol MAY be supported, and supporting version 1.3 is
OPTIONAL. Because of how security standards evolve, it is up to the
implementation to choose which [TLS] versions they support. However,
[S2S streams] MUST be encrypted.
## N. Topology
A [server], also called a [node], is a [TCP host][TCP] that is able to
initiate and accept [S2S streams].
A [network ID], abbreviated [NID], is a [word].
Each [node] is assigned a [network ID].
Two [nodes] are part of the same [network], or the same [graph], if both
share the same [network ID].
A [client] is an [IRC client][IRC] that is connected to a [server].
A [leaf node] is a [server] that accepts connections from [clients].
A [core node] is a [server] that does not accept any connection from
TODO: define network/graph, server/node, IRC client, core node, leaf node
TODO: define how servers/nodes are connected to each other
## N. List of commands
TODO: say commands == IRC commands
TODO what information MUST and MAY be attached to a command (e.g. `time` tag)
TODO how rollback of conflicting commands (e.g. two NICK with the same nickname,
or a MODE after a KICK)
## N. Connection life cycle
TODO: define the order messages are issued by servers when they start/stop a
connection with another server.
## N. Bootstrap process
TODO: define how a server/node must join a network
## N. Acknowledgments
Inspiration for this document came from the CommonMark specification, and
## N. Appendix and references
[RFC 2119]: https://tools.ietf.org/html/rfc2119