Skip to content

dataplane, transport: node keys -> peer ids#173

Draft
npry wants to merge 3 commits intomainfrom
npry/peer_ids
Draft

dataplane, transport: node keys -> peer ids#173
npry wants to merge 3 commits intomainfrom
npry/peer_ids

Conversation

@npry
Copy link
Copy Markdown
Collaborator

@npry npry commented May 7, 2026

wip, still validating

npry added 2 commits May 7, 2026 08:19
Signed-off-by: Nathan Perry <nathan@tailscale.com>
Change-Id: I4bf750ea2de19b720cd9525852a5268f6a6a6964
The transport implementation is secondary, now in an especially
meaningful sense given that transports communicate over PeerIds, while
derp uses NodePublicKeys. This rename aligns with separation of the
client into the core non-transport functionality, and a transport
wrapper that handles translating to and from PeerId (forthcoming in a
future commit).

Signed-off-by: Nathan Perry <nathan@tailscale.com>
Change-Id: If5dd9a39d4e1299fe999f8457e38e94a6a6a6964
@npry npry force-pushed the npry/peer_ids branch from 89ea7b2 to 9bd650d Compare May 7, 2026 12:29
The baseline derp client doesn't need to know about translating NodeKeys
to transport `PeerId`s, that's a higher level concern now provided by
`ts_derp::Transport`, which wraps the underlying client (abstracted
behind `NodekeyTransport`) with a `PeerLookup` in order to provide
`UnderlayTransport`. This keeps the examples and other functionality
dependent on bare derp working without needing to bring in a dummy
peer id lookup layer.

Signed-off-by: Nathan Perry <nathan@tailscale.com>
Change-Id: Ib965f787e92880ac3d74c364760acc546a6a6964
@npry npry force-pushed the npry/peer_ids branch from 9bd650d to d290ae3 Compare May 7, 2026 12:30
Base automatically changed from npry/keys.randomize-disco to main May 7, 2026 20:03
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