Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Add DNSLink specs for resolving /ipns/{fqdn} content paths #389

Open
lidel opened this issue Mar 26, 2023 · 0 comments
Open

Add DNSLink specs for resolving /ipns/{fqdn} content paths #389

lidel opened this issue Mar 26, 2023 · 0 comments
Labels
dif/medium Prior experience is likely helpful kind/missing-specs A gap in specs for things already used in the real world P1 High: Likely tackled by core team if no one steps up

Comments

@lidel
Copy link
Member

lidel commented Mar 26, 2023

We have a dedicated https://dnslink.dev website with loose specification, but it lacks necessary maintenance and love.
It is also written from IPFS-agnostic perspective, and does not go too deep into how /ipns/{fqdn} and /dnslink/{fqdn} resolution should work in IPFS ecosystem specifically. Due to this, our stack still only supports the former, and the latter can't be used, blocking people from using DNSLink for more than just IPFS.

Given how important DNSLink is for IPFS ecosystem, we should write proper spec that describes how /ipns/{fqdn} should be resolved and add it to https://specs.ipfs.tech. This way we close the specification gap, and have specs for all identifier types on /ipns/ namespace.

@lidel lidel added P1 High: Likely tackled by core team if no one steps up kind/maintenance Work required to avoid breaking changes or harm to project's status quo dif/medium Prior experience is likely helpful labels Mar 26, 2023
@lidel lidel changed the title Add DNSLink specs for resolving /ipns/{dnslink-fqdn} content paths Add DNSLink specs for resolving /ipns/{fqdn} content paths Mar 26, 2023
@lidel lidel added kind/missing-specs A gap in specs for things already used in the real world and removed kind/maintenance Work required to avoid breaking changes or harm to project's status quo labels Mar 26, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
dif/medium Prior experience is likely helpful kind/missing-specs A gap in specs for things already used in the real world P1 High: Likely tackled by core team if no one steps up
Projects
None yet
Development

No branches or pull requests

1 participant