The IETF just recently published a new RFC 9540. It introduces a new SVCB parameter ohttp to a service binding DNS RR to indicate Oblivious HTTP is available on the target host. Note that the value is always empty. It can be either used in the HTTPS SVCB or in the SVCBs for DDR (Disovery of Designated Resolvers) (see RFC 9462).
I've added the new SVCB type and added also the tests from the different RFCs.
Hi folks!
The IETF just recently published a new RFC 9540. It introduces a new SVCB parameter
ohttp
to a service binding DNS RR to indicate Oblivious HTTP is available on the target host. Note that the value is always empty. It can be either used in the HTTPS SVCB or in the SVCBs for DDR (Disovery of Designated Resolvers) (see RFC 9462).I've added the new SVCB type and added also the tests from the different RFCs.