Hello, I presented draft-many-dnsop-dns-isolated-networks Tuesday at the end of dnsop meeting. Thanks for letting me present. Wanted to come back to a few points raised.
- About use cases, I see the dnsop Zulip chat that some people were interested in the topic, noting about additional use cases (antarctic for example). I guess I did not touched enough on this because of limited time, but there are many « mostly isolated, often unconnected » networks use cases being discussed in various wgs. I think the best place to see those are in the Time-Varying Routing wg requirements and use cases documents (draft-ietf-tvr-requirements, draft-ietf-tvr-use-cases). Examples such as solar energy powered networks, power savings networks, remote networks, many are the resource constrained networks where connectivity is not permanent, others having dynamic reachability. These drafts were not written for the purpose of DNS, but routing, but they all applied almost as is to the need of what is discussed in the isolated-networks draft. - local names: as these networks are in fact sometimes connected (sometimes meaning more than exceptional), names need to be global so that both networks are able to resolve names. Local scope names may be in addition to global names, but not a replacement. - while some use cases like deepspace will take time to be deployed, those organizations involved are planning years ahead and need stable technical references that are used as requirements to vendors, RFPs, designs, etc…. In fact, it is useful now. Some other use cases could benefit it right away for implementing. Regards, Marc. _______________________________________________ DNSOP mailing list [email protected] https://www.ietf.org/mailman/listinfo/dnsop
