mirror of
https://git.sr.ht/~seirdy/seirdy.one
synced 2024-11-10 00:12:09 +00:00
New note: DNSLink and SVCB DNS resource records
This commit is contained in:
parent
3d95547ede
commit
c3b11d6020
1 changed files with 10 additions and 0 deletions
10
content/notes/dnslink-and-svcb-dns-resource-records.md
Normal file
10
content/notes/dnslink-and-svcb-dns-resource-records.md
Normal file
|
@ -0,0 +1,10 @@
|
|||
---
|
||||
title: "DNSLink and SVCB DNS resource records"
|
||||
date: 2022-10-25T14:50:18-07:00
|
||||
---
|
||||
|
||||
[SVCB DNS resource records](https://datatracker.ietf.org/doc/draft-ietf-dnsop-svcb-https/) (<abbr>RRs</abbr>) were introduced somewhat recently. They inform user-agents that a given resource exists at another endpoint, possibly with extra parameters. Functionality closely mirrors the `Alt-Svc` standard. A profile of SVCB exists in HTTPS <abbr>RRs</abbr>; Encrypted Client Hello and HTTP/3 are the main use-cases today.
|
||||
|
||||
To give <abbr>IPNS</abbr>-accessible service familiar names, I think SVCB is a better long-term solution than [DNSLink](https://www.dnslink.io/).
|
||||
|
||||
A related issue for the InterPlanetary Name System is [Issue 144 for the <abbr>IPFS</abbr> web browsers integration group](https://github.com/ipfs/in-web-browsers/issues/144); it discusses the viability of using `Alt-Svc` for this.
|
Loading…
Reference in a new issue