Hi Momoka, I see that your draft often uses “in-bailiwick” or “out-of-bailiwick”. If you are not already aware, the latest version of the DNS terminology document (draft-ietf-dnsop-rfc8499bis) notes that “bailiwick” should be considered historic at this point. The preferred language is to refer to the relationship between the NS record owner name, the name in the NS RDATA and the zone origin as either in-domain, sibling domain, or unrelated.
DW From: DNSOP <dnsop-boun...@ietf.org> on behalf of Momoka Yamamoto <momoka....@gmail.com> Date: Sunday, October 22, 2023 at 11:13 AM To: dnsop <dnsop@ietf.org> Cc: "tfie...@mpi-inf.mpg.de" <tfie...@mpi-inf.mpg.de> Subject: [EXTERNAL] [DNSOP] DNS IPv6 Transport Operational Guidelines (draft-momoka-dnsop-3901bis-00) Caution: This email originated from outside the organization. Do not click links or open attachments unless you recognize the sender and know the content is safe. Hello DNSOP Working Group, My name is Momoka Yamamoto and I've recently submitted an Internet-Draft titled "DNS IPv6 Transport Operational Guidelines" (draft-momoka-dnsop-3901bis-00) with my co-author Tobias tfie...@mpi-inf.mpg.de<mailto:tfie...@mpi-inf.mpg.de>. This draft discusses the operational guidelines for operating authoritative and recursive DNS servers in mixed IPv4 and IPv6 environments, expanding on RFC3910 to address the progressing IPv4 exhaustion and the long-term necessity of IPv6-only resolvers. I would greatly appreciate any feedback, comments, or questions you may have regarding this draft. I believe this document could contribute significantly to the current discussions and work of the DNSOP working group, especially in light of the wide adoption of IPv6 over the last 20 years since BCP91 was written. The draft is open for discussion and I am looking forward to engaging with the community to refine and improve it. Momoka Y ---------- Forwarded message --------- From: <internet-dra...@ietf.org<mailto:internet-dra...@ietf.org>> Date: Mon, Oct 23, 2023 at 3:02 AM Subject: New Version Notification for draft-momoka-dnsop-3901bis-00.txt To: Momoka Yamamoto <momoka....@gmail.com<mailto:momoka....@gmail.com>>, Tobias Fiebig <tfie...@mpi-inf.mpg.de<mailto:tfie...@mpi-inf.mpg.de>> A new version of Internet-Draft draft-momoka-dnsop-3901bis-00.txt has been successfully submitted by Momoka Yamamoto and posted to the IETF repository. Name: draft-momoka-dnsop-3901bis Revision: 00 Title: DNS IPv6 Transport Operational Guidelines Date: 2023-10-20 Group: Individual Submission Pages: 9 URL: https://www.ietf.org/archive/id/draft-momoka-dnsop-3901bis-00.txt<https://secure-web.cisco.com/1WMEgDzNtGlz-wElmNGvqrbmvek1FrrN6hpGMOB0HXct2bWQ5eclrKy0sSIyIr5fLwn6G01cug4fyXmPexGcsF_Rm7MxHq-o4tzGHqTD7ouDAStpXu-iTFhj6vNiP-y72QytHuNUN8-mRdIE627xDmmTeLH70xmrdtVJOJM72rt2cel_2rv4oWPKq7XFhZD97AXiaDGmFb9sclX1jT2HmV9tQkZdajVGVKjx9AKzbz62xeB7aDswlmqzyRMqicGDCNK3PZykqbfURaN59egG4khPzqkhhRsLPw1-3lRRvIPo/https%3A%2F%2Fwww.ietf.org%2Farchive%2Fid%2Fdraft-momoka-dnsop-3901bis-00.txt> Status: https://datatracker.ietf.org/doc/draft-momoka-dnsop-3901bis/<https://secure-web.cisco.com/1CYQ6wghi7KM-lLwdkZhqWYxjiLmNA48h8ly5C8ug2j2BRQiX4hRBw5xnCH6mRDgZHjJrlMomQQ2S6YGgkoLYYMcXlFQAGFy1-y-KcKNnU7DZxu8CAS7kAHc5o_Q6hzcF8b-YJu283kAGkb85XcLDeTGZzsEtDAhXEzhwgyEapiKdPxAZRgvF7LSOum2pwWGgZhqUqg0vZY0SrPO4YLTwc_jBcNl4tSTYwXJsH2F2FmeoFttb29_ZCxktCWwkbGf4yoWzpRa2y5B95jH7frwWvn6s8-VNLBAt4fN87P8c_dA/https%3A%2F%2Fdatatracker.ietf.org%2Fdoc%2Fdraft-momoka-dnsop-3901bis%2F> HTML: https://www.ietf.org/archive/id/draft-momoka-dnsop-3901bis-00.html<https://secure-web.cisco.com/1_MVcKP9IPgG_TWZ8qWPF45uedr1VX_eQbY6J0uOVr7WF0yJQ0-jwq-JpIh6iUJKEcIOKtkLpzNBwhqCZqk3g6DvlJpXf7rlPt4axLpZKJnmFtE2zgyTxPp3yA8qRpo7shv8c6oCcT5uSP3RyXQL1UWO6g5JMsOAV_DDKdoocshQHR_sQIczmwXn40eTb83rqvxIu5VKHlnlP1SosSspjjA0fCRKEPry43mOJQMRuvxiEMbINg-8NEmF2IaVIeQIobePMvxnOWJm__TpO4Rp30McJ3PHjuAhk61EdgXzQDHQ/https%3A%2F%2Fwww.ietf.org%2Farchive%2Fid%2Fdraft-momoka-dnsop-3901bis-00.html> HTMLized: https://datatracker.ietf.org/doc/html/draft-momoka-dnsop-3901bis<https://secure-web.cisco.com/1bhZB-VPC1HybZX0MBp43vTwsOSVOFUfbRDxDSwy38R3GC5iA-S6Dy9neUilft0xHI4LwQmry3dfa46A8dCVqseh8yCwaxbIXChgZISaHzhBCXvFe2Q7X7BjAeL4PMJQ_r50vTr1fYKrqBTTk37sXMW-AgbwkZsiNA5E55yUyYQdULPvpkAT1hlVfFVBfhrgbLoV8pyVjSSMhkZkScQZ3-4gZ27MuTdOcszkRzTrkjgCrTWZXoS8XJSLdgf4DC8wv_3QLP2rKq0W36rzJl3UGLm0pJRhk2GVFVUEeM_EO_4A/https%3A%2F%2Fdatatracker.ietf.org%2Fdoc%2Fhtml%2Fdraft-momoka-dnsop-3901bis> Abstract: This memo provides guidelines and documents Best Current Practice for operating authoritative and recursive DNS servers given that queries and responses are carried in a mixed environment of IPv4 and IPv6 networks. It expands beyond [RFC3910] in so far that it now considers the reality of progressing IPv4 exhaustion, which will make IPv6-only resolvers necessary in the long-term. Discussion Venues This note is to be removed before publishing as an RFC. Source for this draft and an issue tracker can be found at https://github.com/momoka0122y/draft-dnsop-3901bis<https://secure-web.cisco.com/1Pd20yC2wWtixnapEVOqvKoj7Gutz9YDm0_y0MhvNFw1aMEM1QJj-Ah5PQNvDYxXIfsnTvRHe-WOzDHmwO2jjRPTo0vww7E4TKi90xsQmiurgIJt2UraS56Gha_WdFg-L7onbULjjytP7-x0F4z392P_-_hzoC8LYtGVqldy4GfyW7K-7Xp4jTufF4VcWOYBFmTYQqa-WfochJYV_CFma6ET5OLrk5eML2bqzwUdFF_CYD6udlz0zCubfo2vPTUV0mcogR65k_7aA47BpswGdKGoVwSas5t0cgjP1ChYF494/https%3A%2F%2Fgithub.com%2Fmomoka0122y%2Fdraft-dnsop-3901bis>. The IETF Secretariat
_______________________________________________ DNSOP mailing list DNSOP@ietf.org https://www.ietf.org/mailman/listinfo/dnsop
