docs: move implemented rfcs

2026-05-14 22:45:06 +00:00 · 2026-03-10 19:18:34 +00:00
parent 98351cf097
commit b81670c414
14 changed files with 71 additions and 4 deletions
@@ -1,3 +1,4 @@
+
 # SMP router message storage

 ## Problem
@@ -1,3 +1,4 @@
+
 # Sharing protocol ports with HTTPS

 Some networks block all ports other than web ports, including port 5223 used for SMP protocol by default. Running SMP routers on a common web port 443 would allow them to work on more networks. The routers would need to provide an HTTPS page for browsers (and probes).
@@ -65,8 +66,6 @@ The implementation relies on a few modification to upstream code:
 - `warp`: Only the re-export of `serveConnection` is needed.
  Unfortunately the most recent `warp` version can't be used right away due to dependency cascade around `http-5` and `auto-update-2`.
  So a fork containing the backported re-export has to be used until the dependencies are refreshed.
-
-
 ### TLS.ServerParams

 When a router has port sharing enabled, a new set of TLS params is loaded and combined with transport params:
@@ -1,3 +1,4 @@
+
 # Expiring messages in journal storage

 ## Problem
@@ -1,3 +1,4 @@
+
 # Fix subQ deadlock: blocking writeTBQueue inside connLock

 ## Problem
@@ -145,6 +145,6 @@ As more protocols are designated as Core IP, development naturally transitions t
 |----------|----------|-------|
 | `protocol/` | Consolidated specs (SMP v19, Agent v7, XFTP v3, XRCP v1, NTF v3, PQDR v1) | 6 specs + overview |
 | `rfcs/` root | Active draft proposals | 10 |
-| `rfcs/done/` | Implemented, not yet verified | 12 |
-| `rfcs/standard/` | Verified against implementation | 25 |
+| `rfcs/done/` | Implemented, not yet verified | 1 (+10 sub-RFCs) |
+| `rfcs/standard/` | Verified against implementation | 31 |
 | `rfcs/rejected/` | Draft proposals not accepted | 7 |
@@ -1,3 +1,4 @@
+
 # Send File Page — Web-based XFTP File Transfer

 ## 1. Problem & Business Case
@@ -1,3 +1,4 @@
+
 # Browser Transport & Web Worker Architecture

 ## TOC
@@ -1,3 +1,12 @@
+---
+Proposed: 2024-06-01
+Implemented: ~2024
+Standardized: 2026-03-10
+Protocol: agent-protocol
+---
+
+> **Implementation note:** This RFC was promoted from done/ to standard/ based on verification that the described feature exists in the codebase. The RFC text reflects the original proposal and may not match the actual implementation in all details. The consolidated protocol specifications in `protocol/` are the authoritative reference for current behavior.
+
 # Evolving agent API

 ## Problem
@@ -1,3 +1,12 @@
+---
+Proposed: 2025-05-05
+Implemented: ~2025 (SMP v16)
+Standardized: 2026-03-10
+Protocol: simplex-messaging
+---
+
+> **Implementation note:** This RFC was promoted from done/ to standard/ based on verification that the described feature exists in the codebase. The RFC text reflects the original proposal and may not match the actual implementation in all details. The consolidated protocol specifications in `protocol/` are the authoritative reference for current behavior.
+
 # Service certificates for high volume routers and services connecting to SMP routers

 ## Problem
@@ -1,3 +1,12 @@
+---
+Proposed: 2024-02-12
+Implemented: ~2024 (SMP v11)
+Standardized: 2026-03-10
+Protocol: simplex-messaging
+---
+
+> **Implementation note:** This RFC was promoted from done/ to standard/ based on verification that the described feature exists in the codebase. The RFC text reflects the original proposal and may not match the actual implementation in all details. The consolidated protocol specifications in `protocol/` are the authoritative reference for current behavior.
+
 # Transmission encryption

 ## Problems
@@ -1,3 +1,12 @@
+---
+Proposed: 2024-03-20
+Implemented: ~2024
+Standardized: 2026-03-10
+Protocol: simplex-messaging
+---
+
+> **Implementation note:** This RFC was promoted from done/ to standard/ based on verification that the described feature exists in the codebase. The RFC text reflects the original proposal and may not match the actual implementation in all details. The consolidated protocol specifications in `protocol/` are the authoritative reference for current behavior.
+
 # Relay metadata and SimpleX network decentralization

 ## Problem
@@ -1,3 +1,12 @@
+---
+Proposed: 2024-06-21
+Implemented: ~2025 (SMP v15)
+Standardized: 2026-03-10
+Protocol: simplex-messaging + agent-protocol
+---
+
+> **Implementation note:** This RFC was promoted from done/ to standard/ based on verification that the described feature exists in the codebase. The RFC text reflects the original proposal and may not match the actual implementation in all details. The consolidated protocol specifications in `protocol/` are the authoritative reference for current behavior.
+
 # Short invitation links

 ## Problem
@@ -1,3 +1,12 @@
+---
+Proposed: 2024-09-09
+Implemented: ~2025 (SMP v15)
+Standardized: 2026-03-10
+Protocol: simplex-messaging + agent-protocol
+---
+
+> **Implementation note:** This RFC was promoted from done/ to standard/ based on verification that the described feature exists in the codebase. The RFC text reflects the original proposal and may not match the actual implementation in all details. The consolidated protocol specifications in `protocol/` are the authoritative reference for current behavior.
+
 # Blob extensions for SMP queues

 Evolution of the design for short links, see [here](./2024-06-21-short-links.md) and [here](./2024-09-05-queue-storage.md).
@@ -1,3 +1,12 @@
+---
+Proposed: 2025-03-16
+Implemented: ~2025 (SMP v15)
+Standardized: 2026-03-10
+Protocol: simplex-messaging + agent-protocol
+---
+
+> **Implementation note:** This RFC was promoted from done/ to standard/ based on verification that the described feature exists in the codebase. The RFC text reflects the original proposal and may not match the actual implementation in all details. The consolidated protocol specifications in `protocol/` are the authoritative reference for current behavior.
+
 # Protocol changes for creating and connecting to SMP queues

 ## Problems