rope-protocol 0.1.1__tar.gz

rope_protocol-0.1.1/LICENSE

@@ -0,0 +1,201 @@
+                                 Apache License
+                           Version 2.0, January 2004
+                        http://www.apache.org/licenses/
+
+   TERMS AND CONDITIONS FOR USE, REPRODUCTION, AND DISTRIBUTION
+
+   1. Definitions.
+
+      "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
+
+   APPENDIX: How to apply the Apache License to your work.
+
+      To apply the Apache License to your work, attach the following
+      boilerplate notice, with the fields enclosed by brackets "[]"
+      replaced with your own identifying information. (Don't include
+      the brackets!)  The text should be enclosed in the appropriate
+      comment syntax for the file format. We also recommend that a
+      file or class name and description of purpose be included on the
+      same "printed page" as the copyright notice for easier
+      identification within third-party archives.
+
+   Copyright [yyyy] [name of copyright owner]
+
+   Licensed under the Apache License, Version 2.0 (the "License");
+   you may not use this file except in compliance with the License.
+   You may obtain a copy of the License at
+
+       http://www.apache.org/licenses/LICENSE-2.0
+
+   Unless required by applicable law or agreed to in writing, software
+   distributed under the License is distributed on an "AS IS" BASIS,
+   WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
+   See the License for the specific language governing permissions and
+   limitations under the License.

rope_protocol-0.1.1/NOTICE

@@ -0,0 +1,4 @@
+ROPE – Resumable Offline Protocol for Emergencies
+Copyright 2026 Daniel Fankhauser
+
+This product is licensed under the Apache License, Version 2.0 (see LICENSE).

rope_protocol-0.1.1/PKG-INFO

@@ -0,0 +1,171 @@
+Metadata-Version: 2.4
+Name: rope-protocol
+Version: 0.1.1
+Summary: ROPE - Resumable Offline Protocol for Emergencies
+Author: Daniel Fankhauser
+License-Expression: Apache-2.0
+Project-URL: Homepage, https://github.com/d-fankhauser/rope
+Project-URL: Specification, https://github.com/d-fankhauser/rope/blob/main/docs/spec.md
+Project-URL: Changelog, https://github.com/d-fankhauser/rope/blob/main/CHANGELOG.md
+Project-URL: Issues, https://github.com/d-fankhauser/rope/issues
+Keywords: resumable,transfer,offline,custody,radio,store-and-forward
+Classifier: Development Status :: 3 - Alpha
+Classifier: Intended Audience :: Developers
+Classifier: Operating System :: Microsoft :: Windows
+Classifier: Operating System :: POSIX :: Linux
+Classifier: Programming Language :: Python :: 3
+Classifier: Topic :: System :: Networking
+Requires-Python: >=3.11
+Description-Content-Type: text/markdown
+License-File: LICENSE
+License-File: NOTICE
+Dynamic: license-file
+
+<h1>
+  <picture>
+    <source media="(prefers-color-scheme: dark)" srcset="https://raw.githubusercontent.com/d-fankhauser/rope/main/docs/images/rope-logo-dark.svg">
+    <img alt="ROPE" src="https://raw.githubusercontent.com/d-fankhauser/rope/main/docs/images/rope-logo.svg" height="72">
+  </picture>
+</h1>
+
+**Resumable Offline Protocol for Emergencies**
+
+[![Tests](https://github.com/d-fankhauser/rope/actions/workflows/tests.yml/badge.svg)](https://github.com/d-fankhauser/rope/actions/workflows/tests.yml)
+[![PyPI](https://img.shields.io/pypi/v/rope-protocol.svg)](https://pypi.org/project/rope-protocol/)
+[![License: Apache-2.0](https://img.shields.io/badge/License-Apache_2.0-blue.svg)](https://github.com/d-fankhauser/rope/blob/main/LICENSE)
+![Python 3.11+](https://img.shields.io/badge/Python-3.11%2B-blue.svg)
+![Status: early development](https://img.shields.io/badge/status-early_development-orange.svg)
+
+ROPE transfers growing files and small messages between a small, closed group of devices over unreliable local
+networks – radio links, Wi-Fi, no internet. Like a rescue line it holds the connection even when it is pulled:
+an interruption costs time, never data.
+
+> **Status:** early development. The [specification](https://github.com/d-fankhauser/rope/blob/main/docs/spec.md) is draft 1 with a proposed wire format. Streams
+> from sources via the hub to consumers work, including resume after disconnects and restarts and block repair, and
+> so do messages with custody and offline media (e.g. a USB stick) as a second path. Interfaces will change.
+
+## Why
+
+Field teams record large files (for example sonar recordings) on one device and want to evaluate them somewhere else
+while they are still being recorded. The link in between drops out regularly, and there is no internet. Plain TCP does
+not resume across connections and acknowledges data before it is safely stored; UDP loses data during outages. ROPE
+adds the missing pieces on top of TCP, borrowing ideas – not code – from space communication (CFDP class 2, DTN custody
+transfer).
+
+## Key properties
+
+- **Resumable** – after any interruption, transfer continues from the last durably stored byte, never from zero.
+- **Custody** – a receiver acknowledges only after the data is on disk (flush + fsync). The sender of a message
+  learns which recipients have it.
+- **End-to-end verified** – checksums per segment and per complete file; bit-for-bit identical results. If bytes
+  changed after they were sent (e.g. a header updated at the end of a recording), only the differing blocks travel
+  again.
+- **Never blocks the producer** – separate process, read-only file access without locks, bounded memory.
+- **Offline** – no internet, no cloud, no external services.
+- **Small groups** – star topology with a hub and a closed participant list: source, consumer and recipient roles,
+  names for the operator, and per consumer a choice of which streams it receives.
+- **Application-agnostic core** – the core knows nothing about the data; applications define streams and messages.
+- **Standard library only** – no third-party runtime dependencies.
+- **Two paths** – the same segments and messages can also travel on removable media and mix with the network.
+
+ROPE has **no encryption** by design and is meant for closed networks – see
+[Security considerations](https://github.com/d-fankhauser/rope/blob/main/docs/spec.md#11-security-considerations).
+
+## How it works (in short)
+
+```
+ source ──TCP──▶ hub ──TCP──▶ consumer(s)
+                  │
+                  └──TCP──▶ recipient(s)   (messages only)
+```
+
+1. Every participant connects to the hub and greets it (identifier, role, protocol version). The hub checks its
+   participant list and tells everybody the names and roles of the group.
+2. The hub reports how far it has stored each stream (*committed offset*).
+3. The source sends segments from there; the hub writes, syncs, then acknowledges.
+4. When a stream is complete, a final checksum confirms the whole file; on a difference, only the differing blocks
+   are resent.
+5. On any disconnect: reconnect, greet, continue from the committed offset.
+6. Without a network, a participant and the hub exchange the same frames as bundles on removable media
+   (`export_media`, `import_media`); network and media mix freely.
+
+Details: [docs/spec.md](https://github.com/d-fankhauser/rope/blob/main/docs/spec.md).
+
+## Requirements
+
+- Python 3.11 or newer, on Windows or Linux
+- Nothing else at runtime
+
+## Installation
+
+```
+python -m pip install rope-protocol
+```
+
+The package is named `rope-protocol` (import `rope_protocol`), because the name `rope` on PyPI belongs to a
+well-known refactoring library. Versions and changes: [CHANGELOG.md](https://github.com/d-fankhauser/rope/blob/main/CHANGELOG.md). While ROPE is in early
+development, pin the version you tested with (e.g. `rope-protocol==0.1.1`).
+
+For development:
+
+```
+git clone https://github.com/d-fankhauser/rope.git
+cd rope
+python -m pip install pytest pyflakes
+python -m pytest
+```
+
+### Simulating an unreliable link
+
+No radio link at hand? The link simulator sits between two programs and adds bandwidth limits, latency, blackouts
+and disconnects:
+
+```
+python -m rope_protocol.linksim --listen 127.0.0.1:47311 --target 127.0.0.1:47310 --profile radio
+```
+
+Profiles are `lan`, `wifi`, `radio` and `radio-bad`; `--seed` makes the fault schedule reproducible. All profile
+values are assumptions until measured on real links (see spec §13).
+
+ROPE's default port is **47310**; applications can override it.
+
+## Repository layout
+
+| Path | Content |
+|---|---|
+| `docs/spec.md` | Protocol specification (draft) |
+| `docs/decisions.md` | Decisions with date and reason |
+| `docs/ideas.md` | Ideas not yet planned |
+| `docs/images/` | Logo and symbol (SVG; light and dark variant) |
+| `TASKS.md` | Task board |
+| `CHANGELOG.md` | Changes per version |
+| `src/rope_protocol/` | Package: frame codec (`frames.py`), link simulator (`linksim.py`), durable store (`store.py`), sending and receiving side of streams (`sender.py`, `receiver.py`), messages (`messages.py`), offline media (`media.py`), participant list (`roster.py`), participants (`hub.py`, `source.py`, `consumer.py`, `recipient.py`, base `participant.py`) |
+| `tests/` | Unit tests and the fault-injection test bench (`framefault.py`, `test_faults.py`) |
+| `AGENTS.md` | Guidelines for contributors and coding agents |
+
+## Testing
+
+Every change runs `pyflakes` and `pytest` on Windows and Linux (Python 3.11–3.13). The test bench injects faults – a
+simulated radio link with blackouts and disconnects, restarts, and one fault at every step of the procedure (connection
+cut before or in the middle of a frame, frame duplicated or damaged, participant or hub restarted) – and checks that every file arrives bit-for-bit
+identical and every message exactly once. The full set of faults at every step runs with:
+
+```
+ROPE_SOAK=1 python -m pytest tests/test_faults.py
+```
+
+## Limitations
+
+- Early development: streams, messages and offline media work. Interfaces and the wire format may still change.
+- Not a general file synchronisation tool and not meant for the internet.
+- No encryption, no authentication beyond a participant list.
+- Not compatible with CFDP or DTN software; only the ideas are borrowed.
+
+## Contributing
+
+Contributions are welcome – please read [CONTRIBUTING.md](https://github.com/d-fankhauser/rope/blob/main/CONTRIBUTING.md). Questions and ideas: open an issue.
+
+## License
+
+Copyright 2026 Daniel Fankhauser. Licensed under the [Apache License, Version 2.0](https://github.com/d-fankhauser/rope/blob/main/LICENSE); see also [NOTICE](https://github.com/d-fankhauser/rope/blob/main/NOTICE).
+The name "ROPE" in connection with this protocol is not covered by the licence (Apache-2.0, section 6).

rope_protocol-0.1.1/README.md

@@ -0,0 +1,148 @@
+<h1>
+  <picture>
+    <source media="(prefers-color-scheme: dark)" srcset="https://raw.githubusercontent.com/d-fankhauser/rope/main/docs/images/rope-logo-dark.svg">
+    <img alt="ROPE" src="https://raw.githubusercontent.com/d-fankhauser/rope/main/docs/images/rope-logo.svg" height="72">
+  </picture>
+</h1>
+
+**Resumable Offline Protocol for Emergencies**
+
+[![Tests](https://github.com/d-fankhauser/rope/actions/workflows/tests.yml/badge.svg)](https://github.com/d-fankhauser/rope/actions/workflows/tests.yml)
+[![PyPI](https://img.shields.io/pypi/v/rope-protocol.svg)](https://pypi.org/project/rope-protocol/)
+[![License: Apache-2.0](https://img.shields.io/badge/License-Apache_2.0-blue.svg)](https://github.com/d-fankhauser/rope/blob/main/LICENSE)
+![Python 3.11+](https://img.shields.io/badge/Python-3.11%2B-blue.svg)
+![Status: early development](https://img.shields.io/badge/status-early_development-orange.svg)
+
+ROPE transfers growing files and small messages between a small, closed group of devices over unreliable local
+networks – radio links, Wi-Fi, no internet. Like a rescue line it holds the connection even when it is pulled:
+an interruption costs time, never data.
+
+> **Status:** early development. The [specification](https://github.com/d-fankhauser/rope/blob/main/docs/spec.md) is draft 1 with a proposed wire format. Streams
+> from sources via the hub to consumers work, including resume after disconnects and restarts and block repair, and
+> so do messages with custody and offline media (e.g. a USB stick) as a second path. Interfaces will change.
+
+## Why
+
+Field teams record large files (for example sonar recordings) on one device and want to evaluate them somewhere else
+while they are still being recorded. The link in between drops out regularly, and there is no internet. Plain TCP does
+not resume across connections and acknowledges data before it is safely stored; UDP loses data during outages. ROPE
+adds the missing pieces on top of TCP, borrowing ideas – not code – from space communication (CFDP class 2, DTN custody
+transfer).
+
+## Key properties
+
+- **Resumable** – after any interruption, transfer continues from the last durably stored byte, never from zero.
+- **Custody** – a receiver acknowledges only after the data is on disk (flush + fsync). The sender of a message
+  learns which recipients have it.
+- **End-to-end verified** – checksums per segment and per complete file; bit-for-bit identical results. If bytes
+  changed after they were sent (e.g. a header updated at the end of a recording), only the differing blocks travel
+  again.
+- **Never blocks the producer** – separate process, read-only file access without locks, bounded memory.
+- **Offline** – no internet, no cloud, no external services.
+- **Small groups** – star topology with a hub and a closed participant list: source, consumer and recipient roles,
+  names for the operator, and per consumer a choice of which streams it receives.
+- **Application-agnostic core** – the core knows nothing about the data; applications define streams and messages.
+- **Standard library only** – no third-party runtime dependencies.
+- **Two paths** – the same segments and messages can also travel on removable media and mix with the network.
+
+ROPE has **no encryption** by design and is meant for closed networks – see
+[Security considerations](https://github.com/d-fankhauser/rope/blob/main/docs/spec.md#11-security-considerations).
+
+## How it works (in short)
+
+```
+ source ──TCP──▶ hub ──TCP──▶ consumer(s)
+                  │
+                  └──TCP──▶ recipient(s)   (messages only)
+```
+
+1. Every participant connects to the hub and greets it (identifier, role, protocol version). The hub checks its
+   participant list and tells everybody the names and roles of the group.
+2. The hub reports how far it has stored each stream (*committed offset*).
+3. The source sends segments from there; the hub writes, syncs, then acknowledges.
+4. When a stream is complete, a final checksum confirms the whole file; on a difference, only the differing blocks
+   are resent.
+5. On any disconnect: reconnect, greet, continue from the committed offset.
+6. Without a network, a participant and the hub exchange the same frames as bundles on removable media
+   (`export_media`, `import_media`); network and media mix freely.
+
+Details: [docs/spec.md](https://github.com/d-fankhauser/rope/blob/main/docs/spec.md).
+
+## Requirements
+
+- Python 3.11 or newer, on Windows or Linux
+- Nothing else at runtime
+
+## Installation
+
+```
+python -m pip install rope-protocol
+```
+
+The package is named `rope-protocol` (import `rope_protocol`), because the name `rope` on PyPI belongs to a
+well-known refactoring library. Versions and changes: [CHANGELOG.md](https://github.com/d-fankhauser/rope/blob/main/CHANGELOG.md). While ROPE is in early
+development, pin the version you tested with (e.g. `rope-protocol==0.1.1`).
+
+For development:
+
+```
+git clone https://github.com/d-fankhauser/rope.git
+cd rope
+python -m pip install pytest pyflakes
+python -m pytest
+```
+
+### Simulating an unreliable link
+
+No radio link at hand? The link simulator sits between two programs and adds bandwidth limits, latency, blackouts
+and disconnects:
+
+```
+python -m rope_protocol.linksim --listen 127.0.0.1:47311 --target 127.0.0.1:47310 --profile radio
+```
+
+Profiles are `lan`, `wifi`, `radio` and `radio-bad`; `--seed` makes the fault schedule reproducible. All profile
+values are assumptions until measured on real links (see spec §13).
+
+ROPE's default port is **47310**; applications can override it.
+
+## Repository layout
+
+| Path | Content |
+|---|---|
+| `docs/spec.md` | Protocol specification (draft) |
+| `docs/decisions.md` | Decisions with date and reason |
+| `docs/ideas.md` | Ideas not yet planned |
+| `docs/images/` | Logo and symbol (SVG; light and dark variant) |
+| `TASKS.md` | Task board |
+| `CHANGELOG.md` | Changes per version |
+| `src/rope_protocol/` | Package: frame codec (`frames.py`), link simulator (`linksim.py`), durable store (`store.py`), sending and receiving side of streams (`sender.py`, `receiver.py`), messages (`messages.py`), offline media (`media.py`), participant list (`roster.py`), participants (`hub.py`, `source.py`, `consumer.py`, `recipient.py`, base `participant.py`) |
+| `tests/` | Unit tests and the fault-injection test bench (`framefault.py`, `test_faults.py`) |
+| `AGENTS.md` | Guidelines for contributors and coding agents |
+
+## Testing
+
+Every change runs `pyflakes` and `pytest` on Windows and Linux (Python 3.11–3.13). The test bench injects faults – a
+simulated radio link with blackouts and disconnects, restarts, and one fault at every step of the procedure (connection
+cut before or in the middle of a frame, frame duplicated or damaged, participant or hub restarted) – and checks that every file arrives bit-for-bit
+identical and every message exactly once. The full set of faults at every step runs with:
+
+```
+ROPE_SOAK=1 python -m pytest tests/test_faults.py
+```
+
+## Limitations
+
+- Early development: streams, messages and offline media work. Interfaces and the wire format may still change.
+- Not a general file synchronisation tool and not meant for the internet.
+- No encryption, no authentication beyond a participant list.
+- Not compatible with CFDP or DTN software; only the ideas are borrowed.
+
+## Contributing
+
+Contributions are welcome – please read [CONTRIBUTING.md](https://github.com/d-fankhauser/rope/blob/main/CONTRIBUTING.md). Questions and ideas: open an issue.
+
+## License
+
+Copyright 2026 Daniel Fankhauser. Licensed under the [Apache License, Version 2.0](https://github.com/d-fankhauser/rope/blob/main/LICENSE); see also [NOTICE](https://github.com/d-fankhauser/rope/blob/main/NOTICE).
+The name "ROPE" in connection with this protocol is not covered by the licence (Apache-2.0, section 6).

rope_protocol-0.1.1/pyproject.toml

@@ -0,0 +1,41 @@
+[build-system]
+requires = ["setuptools>=77"]
+build-backend = "setuptools.build_meta"
+
+[project]
+name = "rope-protocol"
+dynamic = ["version"]
+description = "ROPE - Resumable Offline Protocol for Emergencies"
+readme = "README.md"
+license = "Apache-2.0"
+license-files = ["LICENSE", "NOTICE"]
+authors = [{ name = "Daniel Fankhauser" }]
+keywords = ["resumable", "transfer", "offline", "custody", "radio", "store-and-forward"]
+requires-python = ">=3.11"
+dependencies = []
+classifiers = [
+    "Development Status :: 3 - Alpha",
+    "Intended Audience :: Developers",
+    "Operating System :: Microsoft :: Windows",
+    "Operating System :: POSIX :: Linux",
+    "Programming Language :: Python :: 3",
+    "Topic :: System :: Networking",
+]
+
+[project.urls]
+Homepage = "https://github.com/d-fankhauser/rope"
+Specification = "https://github.com/d-fankhauser/rope/blob/main/docs/spec.md"
+Changelog = "https://github.com/d-fankhauser/rope/blob/main/CHANGELOG.md"
+Issues = "https://github.com/d-fankhauser/rope/issues"
+
+[tool.setuptools.dynamic]
+version = { attr = "rope_protocol.__version__" }
+
+[tool.setuptools.packages.find]
+where = ["src"]
+
+[tool.pytest.ini_options]
+pythonpath = ["src"]
+testpaths = ["tests"]
+# network tests: print every thread's stack instead of hanging silently
+faulthandler_timeout = 120

rope_protocol-0.1.1/setup.cfg

@@ -0,0 +1,4 @@
+[egg_info]
+tag_build = 
+tag_date = 0
+

rope_protocol-0.1.1/src/rope_protocol/__init__.py

@@ -0,0 +1,17 @@
+"""ROPE - Resumable Offline Protocol for Emergencies.
+
+Specification: docs/spec.md. Implemented so far: the frame codec of the wire format (``rope_protocol.frames``), the
+link simulator for tests (``rope_protocol.linksim``) and streams from sources via a hub to consumers
+(``rope_protocol.source``, ``rope_protocol.hub``, ``rope_protocol.consumer``; shared parts in ``sender``,
+``receiver``, ``participant``, ``store``), messages with custody (``rope_protocol.messages``,
+``rope_protocol.recipient``), offline media as a second path (``rope_protocol.media``) and the participant list
+with names and a stream selection per consumer (``rope_protocol.roster``).
+"""
+
+__version__ = "0.1.1"
+
+#: Protocol version announced in the greeting (spec 14.5). Increase on incompatible changes.
+PROTOCOL_VERSION = 1
+
+#: Default TCP port of the hub (spec 14.1). Applications must allow overriding it.
+DEFAULT_PORT = 47310