Ben Schwartz <[email protected]> writes: > The list of IANA root zone data publication points, available at TBD- > URL, may be used to discover where the IANA root zone data can be > fetched from. > > Presumably that is an HTTP URL. > > I believe this HTTP dependency could be resolved by encoding this list > into DNS RDATA in some fashion. This would remove the dependency on > HTTP.
That is not needed at run time (but can be used at run time). So a resolver itself need not be dependent on HTTP. As per the document, there are three ways to build the list of sources that a runtime resolver users: local config, a compile time list, and a live list. Only implementations that want to use the live list directly from IANA at runtime need to support HTTP. The rest do not (IE, the ones using a local config or a compile time, default list of sources). -- Wes Hardaker Google _______________________________________________ DNSOP mailing list -- [email protected] To unsubscribe send an email to [email protected]
