Skip to content
This repository has been archived by the owner on Dec 29, 2023. It is now read-only.

A whimsical point: GNS #37

Closed
elear opened this issue Apr 8, 2022 · 1 comment
Closed

A whimsical point: GNS #37

elear opened this issue Apr 8, 2022 · 1 comment
Labels
work item Well-defined issue that need spec text

Comments

@elear
Copy link

elear commented Apr 8, 2022

4.2 necessary centralization and DNS cover good ground in your draft. Right now, draft-schanzen-gns exists. Here we have the PGP web of trust of naming. The value of this draft is that it attempts to provide a way around centralized authorities and is very relevant in a world where belligerent governments try to impose controls on DNS. They turn DNS on its head and make every resolver the root.

You are already hitting at one of the two weakpoints that draft has: how do you do that first rendezvous? The other weakpoint may also be worth mentioning here: without some sort of trusted introducer model, if keys are lost, that really is the ballgame. And those keys have to be properly managed. I asked the authors to undertake a thought experiment: what would it be like for FB to run GNS? You may want to touch on some of this as a complication.

@elear
Copy link
Author

elear commented Apr 8, 2022

I would imagine that this could be a bit of additional text in Section 5.3 (Blockchains are not magical).

@mnot mnot added the work item Well-defined issue that need spec text label May 15, 2022
@mnot mnot closed this as completed in e015aad May 15, 2022
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
work item Well-defined issue that need spec text
Projects
None yet
Development

No branches or pull requests

2 participants