On 28 Jan 2017, at 12:28, Ralph Droms wrote:
I've submitted three issues to the doc repo:
Issue #8:
https://github.com/DNSOP/draft-ietf-dnsop-terminology-bis/issues/8
<https://github.com/DNSOP/draft-ietf-dnsop-terminology-bis/issues/8>
Add "context" as a facet in the definition of a naming system. A
naming system needs a context in which to perform resolution of a
name. As an example, "locally served DNS zones" (see Issue #10) use
the DNS resolution mechanism through a local context rather than
through the global root.
Is that "context" or "possible contexts"? That is, if you consider
1034/1035 as a naming scheme, it seems like there could be "the global
context" (the root servers that everyone assumed then) and "a local
context" (hosts.txt) or even a mixed context ("first try to resolve in
hosts.txt but then go to the root servers if you get an NXDOMAIN", or
even the reverse of that). Some naming schemes might have other
interesting mixes of context.
But I agree that something like this is a common, and commonly-ignored,
facet that would be useful to list.
--Paul Hoffman
_______________________________________________
DNSOP mailing list
DNSOP@ietf.org
https://www.ietf.org/mailman/listinfo/dnsop
