Hello all, This email is in context of draft-kowalik-domainconnect proposal
https://datatracker.ietf.org/doc/draft-kowalik-domainconnect/ that I hope people receiving this email have heard or might even be somewhat familiar. Proposal has a service discovery mechanism that uses DNS TXT record to locate DNS Provider. Assuming the provider is found Service Provider can proceed checking if DNS Provider has a specific Service Provider template available, and if so apply the changes. That is 99% good and great. My and Cloudflare's problem with the update flow is non-standard DNS extensions. It would be great if the DNS Provider response could have further instructions to Service Providers. At the moment the DNS Provider responses look like this: { "providerId": "cloudflare.com", "providerName": "cloudflare", "providerDisplayName": "Cloudflare", "urlSyncUX": "https://dash.cloudflare.com/domainconnect";, "urlAPI": "https://api.cloudflare.com/client/v4/dns/domainconnect"; } With extensions response could look something like this: { "providerId": "cloudflare.com", "providerName": "cloudflare", "providerDisplayName": "Cloudflare", "urlSyncUX": "https://dash.cloudflare.com/domainconnect";, "urlAPI": "https://api.cloudflare.com/client/v4/dns/domainconnect";, "Extensions": { "settings": [ { "flow": "synchronous", "syncPubKeyDomain": "required", "warnPhishing": "notsupported" } ], "records": [ { "type": "A", "proxied": "bool" }, { "type": "AAAA", "proxied": "bool" }, { "type": "CNAME", "proxied": "bool", "flattened": "bool" } ] } } Extensions have relation to Domain Connect templates. The key-values in settings segment attempt to clarify how things need to be applied to the DNS Provider, and what one can expect as requirement and/or support. In the records list type key is required and it tells what additional apply?[properties] key-values the DNS Provider expects. All the records in an apply set will use the same value for each key, for example the proxied. In case Service Provider wants to mix proxied and unproxied records in an update to Cloudflare then Service Provider must apply template part-by-part. When record specific instructions are not defined as an apply property then DNS Provider can default to whatever makes most sense. These instructions are OPTIONAL. To summarize. Extensions could be quite useful for DNS Provider specific quirks, that are unpredictable in nature. All and each provider can have various extra settings without relation to each other. What do you think, does that make sense? Could the next draft version include DNS Provider extensions? -- Sami Kerola https://kerolasa.iki.fi/
_______________________________________________ DNSOP mailing list -- [email protected] To unsubscribe send an email to [email protected]
