Add phone number addressing proposal#145
Open
jamesmunns wants to merge 3 commits into
Open
Conversation
hannobraun
reviewed
Nov 14, 2025
Contributor
hannobraun
left a comment
hannobraun
left a comment
There was a problem hiding this comment.
Just gave the proposal a quick read, and I think it's a stroke of genius! Having networks that can move to other networks is really neat, and this
Under Phone Number Addressing, these concepts are all merged, meaning that a specific address now always refers to a socket.
blew my mind! 🤯
Should work for IPv6 too, though I'm sure that would break all kinds of assumptions at all the layers.
(Despite my enthusiastic response, I'd like to note that I haven't understood this at a deep enough level yet, so I can't say how well it would work in practice.)
Anyway, I found a few minor issues in the document and left comments.
| An Apex entity is able to use the entire 32-bit address space as it sees fit, as it has no upstream network that it needs to "fit within". However, Apex entities may still want to be conservative in how they use this space for two reasons: | ||
|
|
||
| 1. The existence as an "Apex" may be temporary, if they later join a network as a "downstream" or "child" entity | ||
| 2. The smaller addresses uses, the more compact they will be when transmitting. |
Contributor
There was a problem hiding this comment.
Suggested change
| 2. The smaller addresses uses, the more compact they will be when transmitting. | |
| 2. The smaller the addresses they use, the more compact those will be when transmitting. |
| 1. The existence as an "Apex" may be temporary, if they later join a network as a "downstream" or "child" entity | ||
| 2. The smaller addresses uses, the more compact they will be when transmitting. | ||
|
|
||
| Currently, it is suggested that Apex entity make a best guess at the maximum address space needed for all downstream entities, including its own local sockets. |
Contributor
There was a problem hiding this comment.
Suggested change
| Currently, it is suggested that Apex entity make a best guess at the maximum address space needed for all downstream entities, including its own local sockets. | |
| Currently, it is suggested that Apex entities make a best guess at the maximum address space needed for all downstream entities, including their own local sockets. |
|
|
||
| ### Downstream Entities | ||
|
|
||
| Devices that are connected to another device are referred to as "Downstream" entities. They may be directly connected to an Apex entity, or to another Downstream entity with or more "hops" to the Apex entity. |
Contributor
There was a problem hiding this comment.
Suggested change
| Devices that are connected to another device are referred to as "Downstream" entities. They may be directly connected to an Apex entity, or to another Downstream entity with or more "hops" to the Apex entity. | |
| Devices that are connected to another device are referred to as "Downstream" entities. They may be directly connected to an Apex entity, or to another Downstream entity with one or more "hops" to the Apex entity. |
|
|
||
| ## Any/All messages | ||
|
|
||
| In the previous system, port `0` was reserved as the "Any" port, which ergot would attempt to find a single port that matched the requested characteristics. Port `255` was reserved as the "All" port, which ergot would flood to all sockets and interfaces, except for the source interface, until the TTL was consumed. |
Contributor
There was a problem hiding this comment.
which ergot would attempt to find a single port that matched the requested characteristics.
I can tell that the grammar here is not right, but not knowing how the previous system works, I'm not sure how to correct it.
| As descrived, this generally requires: | ||
|
|
||
| 1. All devices know their own range (e.g. E's socket knows it is `03^6`) | ||
| 2. The profile of a device knows it's parents range, and it's own offset in that range (e.g. E's profile knows it is 180^9, so its socket is `183^9` |
Contributor
There was a problem hiding this comment.
Suggested change
| 2. The profile of a device knows it's parents range, and it's own offset in that range (e.g. E's profile knows it is 180^9, so its socket is `183^9` | |
| 2. The profile of a device knows its parent's range, and its own offset in that range (e.g. E's profile knows it is 180^9, so its socket is `183^9` |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
A work in progress proposal to discuss Phone Number Addressing