#svcb — Public Fediverse posts

My final #IETF draft submission for the day -- this one being #IPv6 related!

"Indicating IPv6-only SVCB Endpoints and IPv4 Deprecation in the DNS"

https://datatracker.ietf.org/doc/html/draft-nygren-dnsop-ipv6only-indicator-00

(Likely for @ietf_wg_dnsop given it is extending #DNS #SVCB, although it ties into v6ops and happy as well.)

Abstract: As the DNS is the primary mechanism for translating from hostnames to IP addresses, it is a logical place to signal that endpoints are IPv6-only. It is thus also a logical place to signal that legacy endpoints supporting IPv4 are being deprecated. This specification introduces two SvcParams for SVCB-compatible RR types that signal IPv6-only endpoints ("ipv6only") as well as deprecated endpoints ("deprecated").

#sunset4 #ToTheUniversalDeprecationOfIPv4

je découvre le truc et je vois pas l'info, mais est-ce qu'il est possible d'utiliser #svcb pour par exemple permettre à un client openvpn de se connecter automatiquement à un lien de secours si le lien principal ne répond pas ?

Ca pourrait marcher ou je capte pas le truc ?

@cks @lanodan

Missing from @drscriptt 's list are AAAA, HTTPS, and SVCB records.

AAAA has plenty of obvious choices.

You'll know the . convention for SRV, SVCB, and MX resource record sets, of course.

I shall just drop in my personal experience from earlier this year that an accidentally supplied HTTPS resource record can *definitely* break WWW traffic; because browsers in practice do not obey RFC9460 §2.4.2.

#djbdns
#DomainNameSystem
#SplitHorizon
#ReservedSuperDomains #DNS #HTTPS #SVCB

🚨 BREAKING: #RFC9460 claims to revolutionize the #DNS landscape with #SVCB and #HTTPS records, but spoiler alert—it's just another jargon-filled proposal destined to collect digital dust. 🌐📜 Meanwhile, DNS admins everywhere are thrilled to have more acronyms to ignore. 🙄✨
https://datatracker.ietf.org/doc/html/rfc9460 #DigitalDust #DNSAdmins #HackerNews #ngated

RFC9460: SVCB and HTTPS DNS Records

https://datatracker.ietf.org/doc/html/rfc9460

#HackerNews #RFC9460 #SVCB #HTTPS #DNS #Records #IETF #TechNews #Networking

@ermo

There are a much smaller number of people doing SVCB lookups, too. But, interestingly, they are doing them wrongly.

And with a direct correlation to some other abuses.

Which does make me think that, in an ironic twist, it is the bad actors running robot vulnerability probes and scrapers that are the early adopters of SVCB, here.

#djbwares #DomainNameSystem #svcb

Today I discovered the RFC 9460 and therefore the SVCB and HTTPS resource records. Very interesting and useful innovation :)

https://www.rfc-editor.org/rfc/rfc9460

#RFC9460 #RFC #DNS #SVCB #HTTPS

We now publish DNS HTTPS IP hint records for all #OpenStreetMap web services per #RFC9460 Why? Small incremental improvement to performance and privacy. Our DNS handles over 2,000 requests per second. DNS HTTPS query is our 2nd most common query. #DNScontrol #SVCB 🚀 🤓

@shaft Tiens, puisque tu parlais de #SVCB en mode alias : https://lists.dns-oarc.net/pipermail/dns-operations/2024-April/022531.html

#DNS

"ohttp" is now officialy the 8th wonder of the "Service Parameter Keys (SvcParamKeys)" registry :)

(And is the easiest to process when decoding a #SVCB RR :) )

#RFC 9540: Discovery of Oblivious Services via Service Binding Records
https://www.rfc-editor.org/info/rfc9540

There is a great summary of the state of HTTPS RRs (#SVCB style records) at https://netmeister.org/blog/https-rrs.html
Thanks @jschauma for writing this – it also explains in its footnotes why Chromium so far fails my https://svcbtest.amsuess.com/ test site – it doesn't allow setting a different target name.

Oh, and lastly, this whole Mastodon thread as a much more convenient blog post 😜:

https://www.netmeister.org/blog/https-rrs.html

#dns #svcb #https #rfc9460 ✌️

@jschauma They’re pretty great. #HTTPS records are self-explanatory, but do you know of any services using #SVCB yet?

Woohoo! #IETF #RFC9460 has been published: "Service Binding and Parameter Specification via the #DNS (#SVCB and #HTTPS Resource Records)". https://www.rfc-editor.org/rfc/rfc9460.html

Thank you to everyone has supported and contributed to this over the past almost nine years since the initial seeds were planted during discussions at a TLS 1.3 interim meeting.

SVCB has potential to have substantial impact across a wide range of Internet protocols. I'm thrilled to see how many drafts are already building on it.

Finally! RFC 9460 "Service Binding and Parameter Specification via the DNS (SVCB and HTTPS Resource Records)" #dns #https #svcb

We've completely refactored the handling of #SVCB record data in the domain crate. #DNS #rustlang #OpenSource https://github.com/NLnetLabs/domain/pull/176

@partim has refactored the #SVCB record data to work along the same lines as all the other TLV-style types in the domain crate. #DNS #rustlang https://github.com/NLnetLabs/domain/pull/176

Curious what's coming up in the next release of your favourite #DNS resolver? #Unbound #EDE #SVCB #NAT64 #OpenSource https://github.com/NLnetLabs/unbound/milestone/2

Let's kick off the day with a new release of our authoritative #DNS server, NSD 4.6.1. This version sets the ALPN "dot" token during connection establishment as per RFC 9103, and it introduces #SVCB dohpath support. #OpenSource https://github.com/NLnetLabs/nsd/releases/tag/NSD_4_6_1_REL

The first Release Candidate for authoritative #DNS server NSD 4.6.1 is out. It adds #SVCB dohpath support and sets the ALPN "dot" token during connection establishment as per RFC9103, section 7.1. https://lists.nlnetlabs.nl/pipermail/nsd-users/2022-November/003167.html

We've released version 0.2 of our experimental connectbyname library, which is meant to simplify application code to set up a #TLS connection when given a #DNS name and a port.

The library takes care of resolving A and AAAA addresses, Happy Eyeballs, and #DANE validation.

Together with changes to Stubby, the library also provides control over connections to upstream DNS resolvers, for example, whether encryption is mandatory or not. #IPv6 #SVCB #DoT #DoH

https://nlnetlabs.nl/projects/connectbyname/about/