Petr Špaček <[email protected]> writes: > Anyway, I second Ben Schwarz's opinion that we really need > self-contained DNS solution. HTTP can be optional in case given DNS > implementation has to deal with HTTP because of other reasons.
So there are multiple aspects to this, but I added this point to the draft-hardaker-dnsop-root-zone-publication-list-guidelines document: - the publication list should contain a variety of protocols for LocalRoot implementations to make use of based on implementation and operator preference. For example, the list should contain URLs of "http", "https", "axfr", "xot" and "xoh" schemes if possible. I don't think we can force a wealth of options for each, as that becomes a combination of provider and client preferences that should overlap. We could (though I don't currently) request that IANA host the domain on a list of specific services. I suspect that's really what you would prefer? -- Wes Hardaker Google _______________________________________________ DNSOP mailing list -- [email protected] To unsubscribe send an email to [email protected]
