Posts
april
@april@donotsta.re
donotsta.re
@domi @Mae first of all, what domi already said. but to my actual thoughts: this is intended for static public content of any sort, think indie web pages etc. this is intended as backup behavior for normal user agents like browsers, this does mean tho that long term web pages could be dns only if they just dont have A or AAAA records, but that is outside of my control if thats actually deployed, even tho it would be practical for some. but that would first require wide spread browser support
for encryption: its possible to serve encrypted content via this, but the protocol doesnt specify way of decryption or encryption
for encryption: its possible to serve encrypted content via this, but the protocol doesnt specify way of decryption or encryption
0
0
0
april
@april@donotsta.re
donotsta.re
@domi i left that up for the resolver esp because normal dns implementations dont care about size overhead and just fall back to tcp if its too big, ig if you serve content over dns you can just eyeball it (or go with max udp frame size) and see based on prometheus or other stats how many requests fall back to tcp
0
2
0
april
@april@donotsta.re
donotsta.re
Hey, y'all! Just decided to finally post my IETF draft, that I've been cooking up for the last few months, go check it out, roast me, maybe go implement it and show me your implementations :3 :boost_ok:
Here's the abstract:
This document specifies a mechanism for serving content, such as HTML or JSON, directly via DNS TXT records. This feature is intended as a fallback mechanism when a primary service (A/AAAA record) is unreachable, or as a lightweight hosting solution for parked domains to display landing pages without requiring active HTTP servers or individual SSL certificates. Trust is established via DNSSEC, allowing browsers to treat the content as secure.
https://datatracker.ietf.org/doc/draft-dns-content-delivery/
https://www.ietf.org/archive/id/draft-dns-content-delivery-00.html
Here's the abstract:
This document specifies a mechanism for serving content, such as HTML or JSON, directly via DNS TXT records. This feature is intended as a fallback mechanism when a primary service (A/AAAA record) is unreachable, or as a lightweight hosting solution for parked domains to display landing pages without requiring active HTTP servers or individual SSL certificates. Trust is established via DNSSEC, allowing browsers to treat the content as secure.
https://datatracker.ietf.org/doc/draft-dns-content-delivery/
https://www.ietf.org/archive/id/draft-dns-content-delivery-00.html
0
6
0