Closed enygren closed 2 years ago
The SVCB record specification only contains the key and not the targetpath. Ideally we'd reuse something from one of the DoH/DPRIVE/etc SVCB specs for this rather than creating a new SvcParamKey.
Correct, I agree this shouldn't define a new key for the path, but should rely on the encoding for DoH resolvers from draft-schwartz-svcb-dns.
This is no longer part of the spec, so I think we can close this out.
The SVCB record specification only contains the key and not the targetpath. Ideally we'd reuse something from one of the DoH/DPRIVE/etc SVCB specs for this rather than creating a new SvcParamKey.