Subject: [Ohai] New draft on sending OHTTP configs via SVCB records

From: Tommy Pauly <[email-masked]>
Date: Mon, 07 Mar 2022 19:44:43 -0800

Hi, OHAI,

I wanted to share a new draft that was uploaded a couple of days ago that we’d like to discuss in OHAI.

https://www.ietf.org/archive/id/draft-pauly-ohai-svcb-config-00.html <https://www.ietf.org/archive/id/draft-pauly-ohai-svcb-config-00.html>
https://datatracker.ietf.org/doc/html/draft-pauly-ohai-svcb-config <https://datatracker.ietf.org/doc/html/draft-pauly-ohai-svcb-config>

This defines some new parameters that can be added to SVCB/HTTPS DNS records [1] to communicate OHTTP configs and paths, similar to how TLS ECH configs [2] are sent.

Many uses of OHTTP can use other, bespoke configuration mechanisms, but there are some use cases where discovery over DNS is useful. For example, consider a client that normally uses ODoH/DNS-over-OHTTP to a public server, but discovers via DDR [3] that the local network has designated a resolver that may have some desired properties for the network. A client may not want to downgrade its privacy from using Oblivious DNS, but could be willing to use an Oblivious DNS server advertised by the network as long as that target server is supported by a proxy the client trusts.

This work also fits into one of the deployment models mentioned in the charter, involving "discovery of proxies or servers and their key configurations”.

Please share comments on thoughts on the list, or via GitHub here: https://github.com/tfpauly/draft-ohai-svcb-config <https://github.com/tfpauly/draft-ohai-svcb-config>.

Best,
Tommy

[1] https://datatracker.ietf.org/doc/draft-ietf-dnsop-svcb-https/ <https://datatracker.ietf.org/doc/draft-ietf-dnsop-svcb-https/>
[2] https://datatracker.ietf.org/doc/draft-ietf-tls-esni/ <https://datatracker.ietf.org/doc/draft-ietf-tls-esni/>
[3] https://datatracker.ietf.org/doc/draft-ietf-add-ddr <https://datatracker.ietf.org/doc/draft-ietf-add-ddr>