summaryrefslogtreecommitdiffstats
diff options
context:
space:
mode:
authorbt <bt@rctt.net>2026-04-08 15:31:58 +0200
committerbt <bt@rctt.net>2026-04-14 22:16:45 +0200
commitf66e28aa88a5f4176934001fa9e4967ddccde4a9 (patch)
tree12506a815a2c67ec412fa2b4b8efe3f8a0833a21
parentb9d3b7ea9df409794eefe48ae1003e8444f519bb (diff)
downloadsolec-f66e28aa88a5f4176934001fa9e4967ddccde4a9.tar.gz
solec-f66e28aa88a5f4176934001fa9e4967ddccde4a9.zip
[docs] Describe connection types
-rw-r--r--docs/rfc.html54
-rw-r--r--docs/rfc.md13
-rw-r--r--docs/rfc.txt29
-rw-r--r--solec.ksy8
4 files changed, 89 insertions, 15 deletions
diff --git a/docs/rfc.html b/docs/rfc.html
index aaa92ce..84b5c0a 100644
--- a/docs/rfc.html
+++ b/docs/rfc.html
@@ -1220,7 +1220,7 @@ li > p:last-of-type:only-child {
</tr></thead>
<tfoot><tr>
<td class="left">bt</td>
-<td class="center">Expires 12 October 2026</td>
+<td class="center">Expires 16 October 2026</td>
<td class="right">[Page]</td>
</tr></tfoot>
</table>
@@ -1233,12 +1233,12 @@ li > p:last-of-type:only-child {
<dd class="internet-draft">SOLEC</dd>
<dt class="label-published">Published:</dt>
<dd class="published">
-<time datetime="2026-04-10" class="published">10 April 2026</time>
+<time datetime="2026-04-14" class="published">14 April 2026</time>
</dd>
<dt class="label-intended-status">Intended Status:</dt>
<dd class="intended-status">Experimental</dd>
<dt class="label-expires">Expires:</dt>
-<dd class="expires"><time datetime="2026-10-12">12 October 2026</time></dd>
+<dd class="expires"><time datetime="2026-10-16">16 October 2026</time></dd>
<dt class="label-authors">Author:</dt>
<dd class="authors">
<div class="author">
@@ -1274,7 +1274,7 @@ SOLEC system.<a href="#section-abstract-1" class="pilcrow">¶</a></p>
time. It is inappropriate to use Internet-Drafts as reference
material or to cite them other than as "work in progress."<a href="#section-boilerplate.1-3" class="pilcrow">¶</a></p>
<p id="section-boilerplate.1-4">
- This Internet-Draft will expire on 12 October 2026.<a href="#section-boilerplate.1-4" class="pilcrow">¶</a></p>
+ This Internet-Draft will expire on 16 October 2026.<a href="#section-boilerplate.1-4" class="pilcrow">¶</a></p>
</section>
</div>
<div id="copyright">
@@ -1675,8 +1675,42 @@ Text is encoded using UTF-8.<a href="#section-2.3.3-1" class="pilcrow">¶</a></p
<td class="text-left" rowspan="1" colspan="1">uint8</td>
<td class="text-left" rowspan="1" colspan="1">ver_minor</td>
</tr>
+ <tr>
+ <td class="text-left" rowspan="1" colspan="1">uint8</td>
+ <td class="text-left" rowspan="1" colspan="1">conn_type</td>
+ </tr>
</tbody>
</table>
+<div id="connection-types">
+<section id="section-2.4.3.1">
+ <h5 id="name-connection-types">
+<a href="#section-2.4.3.1" class="section-number selfRef">2.4.3.1. </a><a href="#name-connection-types" class="section-name selfRef">Connection types</a>
+ </h5>
+<p id="section-2.4.3.1-1"><code>conn_type</code> specifies type of the connection. User connecting to server
+should use <code>0x01</code>. If connection is initialize between two servers to exchange
+message connection type should be <code>0x02</code>. Depending on connection type
+different auth method will be used.<a href="#section-2.4.3.1-1" class="pilcrow">¶</a></p>
+<table class="center" id="table-5">
+ <caption><a href="#table-5" class="selfRef">Table 5</a></caption>
+<thead>
+ <tr>
+ <th class="text-left" rowspan="1" colspan="1">Type</th>
+ <th class="text-left" rowspan="1" colspan="1">Connection type</th>
+ </tr>
+ </thead>
+ <tbody>
+ <tr>
+ <td class="text-left" rowspan="1" colspan="1">0x01</td>
+ <td class="text-left" rowspan="1" colspan="1">User -&gt; Server</td>
+ </tr>
+ <tr>
+ <td class="text-left" rowspan="1" colspan="1">0x02</td>
+ <td class="text-left" rowspan="1" colspan="1">Server -&gt; Server</td>
+ </tr>
+ </tbody>
+ </table>
+</section>
+</div>
</section>
</div>
<div id="auth">
@@ -1684,8 +1718,8 @@ Text is encoded using UTF-8.<a href="#section-2.3.3-1" class="pilcrow">¶</a></p
<h4 id="name-auth">
<a href="#section-2.4.4" class="section-number selfRef">2.4.4. </a><a href="#name-auth" class="section-name selfRef">Auth</a>
</h4>
-<table class="center" id="table-5">
- <caption><a href="#table-5" class="selfRef">Table 5</a></caption>
+<table class="center" id="table-6">
+ <caption><a href="#table-6" class="selfRef">Table 6</a></caption>
<thead>
<tr>
<th class="text-left" rowspan="1" colspan="1">Type</th>
@@ -1710,8 +1744,8 @@ Text is encoded using UTF-8.<a href="#section-2.3.3-1" class="pilcrow">¶</a></p
<h4 id="name-message">
<a href="#section-2.4.5" class="section-number selfRef">2.4.5. </a><a href="#name-message" class="section-name selfRef">Message</a>
</h4>
-<table class="center" id="table-6">
- <caption><a href="#table-6" class="selfRef">Table 6</a></caption>
+<table class="center" id="table-7">
+ <caption><a href="#table-7" class="selfRef">Table 7</a></caption>
<thead>
<tr>
<th class="text-left" rowspan="1" colspan="1">Type</th>
@@ -1746,8 +1780,8 @@ Text is encoded using UTF-8.<a href="#section-2.3.3-1" class="pilcrow">¶</a></p
</h4>
<p id="section-2.4.6-1">Test payload is used for encoder and decoders testing. Clients and servers
should ignore this kind of payload.<a href="#section-2.4.6-1" class="pilcrow">¶</a></p>
-<table class="center" id="table-7">
- <caption><a href="#table-7" class="selfRef">Table 7</a></caption>
+<table class="center" id="table-8">
+ <caption><a href="#table-8" class="selfRef">Table 8</a></caption>
<thead>
<tr>
<th class="text-left" rowspan="1" colspan="1">Type</th>
diff --git a/docs/rfc.md b/docs/rfc.md
index eb8f5c1..8c5818e 100644
--- a/docs/rfc.md
+++ b/docs/rfc.md
@@ -186,6 +186,19 @@ Payload is always empty for this type.
|-------|-----------|
| uint8 | ver_major |
| uint8 | ver_minor |
+| uint8 | conn_type |
+
+#### Connection types
+
+`conn_type` specifies type of the connection. User connecting to server
+should use `0x01`. If connection is initialize between two servers to exchange
+message connection type should be `0x02`. Depending on connection type
+different auth method will be used.
+
+| Type | Connection type |
+|------|------------------|
+| 0x01 | User -> Server |
+| 0x02 | Server -> Server |
### Auth
diff --git a/docs/rfc.txt b/docs/rfc.txt
index a19de19..f9e8bca 100644
--- a/docs/rfc.txt
+++ b/docs/rfc.txt
@@ -1,7 +1,7 @@
SOLEC Working Group bt, Ed.
Internet-Draft RCTT.net
-Intended status: Experimental 10 April 2026
-Expires: 12 October 2026
+Intended status: Experimental 14 April 2026
+Expires: 16 October 2026
System of Lightweight Electronic Communication
@@ -209,9 +209,28 @@ Table of Contents
+-------+-----------+
| uint8 | ver_minor |
+-------+-----------+
+ | uint8 | conn_type |
+ +-------+-----------+
Table 4
+2.4.3.1. Connection types
+
+ conn_type specifies type of the connection. User connecting to
+ server should use 0x01. If connection is initialize between two
+ servers to exchange message connection type should be 0x02.
+ Depending on connection type different auth method will be used.
+
+ +======+==================+
+ | Type | Connection type |
+ +======+==================+
+ | 0x01 | User -> Server |
+ +------+------------------+
+ | 0x02 | Server -> Server |
+ +------+------------------+
+
+ Table 5
+
2.4.4. Auth
+========+==========+
@@ -222,7 +241,7 @@ Table of Contents
| string | password |
+--------+----------+
- Table 5
+ Table 6
2.4.5. Message
@@ -238,7 +257,7 @@ Table of Contents
| string | message_content |
+-----------+-----------------+
- Table 6
+ Table 7
2.4.6. Test
@@ -265,7 +284,7 @@ Table of Contents
| uint64 | num4 |
+-----------+-------+
- Table 7
+ Table 8
2.5. Sequential operations
diff --git a/solec.ksy b/solec.ksy
index 2a4a346..7117413 100644
--- a/solec.ksy
+++ b/solec.ksy
@@ -35,6 +35,11 @@ enums:
error_type:
0x01: auth_failed
+ 0x02: not_found
+
+ conn_type:
+ 0x01: user_conn
+ 0x02: server_conn
types:
string:
@@ -67,6 +72,9 @@ types:
type: u1
- id: proto_ver_minor
type: u1
+ - id: conn_type
+ type: u1
+ enum: conn_type
auth:
seq: