Hi Wes, Thanks for responding.
I'll trim to only the the remaining items needing a response, and express my appreciation at the clarified items. On 9/07/2016, 9:53 AM, "iesg on behalf of Wes Hardaker" <[email protected] on behalf of [email protected]> wrote: >"Terry Manderson" <[email protected]> writes: > > >> s1.2 is https://github.com/ogud/DNSSEC_ALG_Check going to be a fully >> stable URL? > >Per discussion in another thread: probably. Olafur certainly won't >delete it as the owner, and I doubt github will die anytime soon. > >The only other choice is to remove the helpful reference. Thanks. > >I've changed it to "validating resolver daemon" instead. Make more sense? It does. > >> s3.1.1, please use the example domain for such examples, ie example.com, >> and once you have used it do you really need to repeat it for each >> 'existing' text until you get to the non-existent tests and so on up to >> 3.1.14. > >Well, here's the deal: example.com won't work and the domain in question >actually does work. Some of them can probably be replaced with the root >server, but many others require somewhat specialized tests pointing to a >special domain. That one is known to be the only one that likely will >work for some tests at this point. The question is, what to do about >that? Can we list a known one? Must we list a useless one instead? >Should we pre-declare the problem? I've been waiting for this to come >up :-) Personally, my advice would be to pre-decalre the issue, and why it's an issue and why some special domain is needed and describe the semantics of the FQDNs needed for the appropriate tests (including an appendix zone file?), and then use example.com as the label which needs to be substituted by the person constructing the tests/zone. The benefit here is that some folks might like to replicate such a construct in their own infrastructure, and this document might give them that guidance. Does that make sense? Thanks Terry
smime.p7s
Description: S/MIME cryptographic signature
_______________________________________________ DNSOP mailing list [email protected] https://www.ietf.org/mailman/listinfo/dnsop
