Skip to content

docs: say that peers adapt to a libe3 agent, and that a response code can be proposed - #150

Draft
Thecave3 wants to merge 1 commit into
docs/111-control-answerfrom
docs/85-115-positions
Draft

Thecave3 wants to merge 1 commit into
docs/111-control-answerfrom
docs/85-115-positions

Conversation

@Thecave3

@Thecave3 Thecave3 commented Nov 7, 2026

Copy link
Copy Markdown
Collaborator

Summary

The interop page said a libe3 RAN agent's one-link, one-encoding limit was libe3's to fix (#85). It now says that agents with different configurations can run at the same time, each with its own ports or endpoints and ran_identifier, and that a RAN with Aerial and OCUDU peers creates one agent for each. That wiring belongs to the RAN application, not to the library. The multi-RAN topology job in CI runs two agents this way. Mixed links in one RAN have not been run, because SCTP is off in CI (#81).

For E3-ResponseCode (#115) the page already asked OCUDU to close its enumeration. It now adds that if OCUDU needs a third code it can propose it on the page, and libe3 is open to adding the extension marker together with the code as one wire change, and to reading an unknown value as a refusal.

The ledger gets a documentation row.

What changes

Documentation only: docs/interop.md. No code, no grammar, no VERSION change. #85 and #115 can close with no libe3 change once this merges.

Stack

Based on #149, which also edits the interop page. Stack: #146, #147, #148, #149, this PR.

@github-actions

github-actions Bot commented Nov 7, 2026 •

Copy link
Copy Markdown
Contributor

CI report — f6021c0 — ✅ all checks passed

Workflow Result Time Run
CI ✅ success 0m18s #13
Docs ✅ success 0m28s #87
Docs

Doxygen warnings

0 warning(s) in the files this pull request changes, which fail the check; 48 more elsewhere, which do not. The full list is in the job log and the doxygen-warnings artifact of the Docs workflow.

Gaps in files this pull request does not change, by file:

Warnings File
17 include/libe3/logger.hpp
9 include/libe3/dapp_subscription_state.hpp
7 include/libe3/lockfree_queue.hpp
6 include/libe3/mpmc_queue.hpp
1 include/libe3/error_codes.h
1 include/libe3/libe3.hpp
1 src/connector/zmq_connector.hpp

Ready to merge (fast-forward only)

A maintainer can land the reviewed commits with:

git fetch origin
git checkout main && git merge --ff-only f6021c0cc4dae017452c7e962dec75a484f1e6dd && git push origin main

Head: f6021c0cc4dae017452c7e962dec75a484f1e6dd (branch docs/85-115-positions). If --ff-only fails as non-fast-forward, the branch must be rebased on the latest main.

One comment per PR, rewritten in place once every workflow for f6021c0 finished.

… can be proposed

A libe3 RAN agent serves one link and one encoding, set in its E3Config (#85). The
interop page said the limit was libe3's to fix, so that one RAN could not face
Aerial and OCUDU at once. Agents with different configurations can run at the same
time, each with its own ports or endpoints and ran_identifier, and the multi-RAN
topology job in CI runs two of them. A RAN with peers on different links or
encodings creates one agent for each, and that wiring belongs to the RAN
application, not to the library. The page now says so, and that mixed links in one
RAN have not been run because SCTP is off in CI.

For E3-ResponseCode (#115) the page already asked OCUDU to close its enumeration.
It now adds that if OCUDU needs a third code it can propose it on the page, and
libe3 is open to adding the extension marker together with the code as one wire
change, and to reading an unknown value as a refusal.

The ledger gets a documentation row. No code, no grammar and no VERSION change.

Assisted-by: Claude:claude-sonnet-5-5
Signed-off-by: Thecave3 <thecave003@gmail.com>
@Thecave3
Thecave3 force-pushed the docs/111-control-answer branch from 36f90d4 to 0a27fb7 Compare November 11, 2026 02:04
@Thecave3
Thecave3 force-pushed the docs/85-115-positions branch from e86c612 to f6021c0 Compare November 11, 2026 02:04

This branch has not been deployed

No deployments
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant