<html><head></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; color: rgb(0, 0, 0); font-size: 22px; font-family: Calibri, sans-serif;"><div>On 9/11/15, 8:27, "dns-operations on behalf of George Michaelson" <<a href="mailto:dns-operations-bounces@dns-oarc.net">dns-operations-bounces@dns-oarc.net</a> on behalf of <a href="mailto:ggm@apnic.net">ggm@apnic.net</a>> wrote:</div><span id="OLK_SRC_BODY_SECTION"><div><br></div><blockquote id="MAC_OUTLOOK_ATTRIBUTION_BLOCKQUOTE" style="BORDER-LEFT: #b5c4df 5 solid; PADDING:0 0 0 5; MARGIN:0 0 0 5;"><div><meta http-equiv="Content-Type" content="text/html; charset=utf-8"><div><div dir="ltr">the recoil is every bit as dangerous as the projectile.</div></div></div></blockquote></span><div><br></div><div>I've worked as a protocol designer/engineer and an operator over the years. I am familiar with various code bases implementing the protocol, some open source, some proprietary, some general purpose, some turn key.</div><div><br></div><div>I've seen the DNS as it is operated on the global public Internet. I am familiar with the growing trend of general purpose, open-source implementations burning into their code "the way the DNS is used" in the global public internet.</div><div><br></div><div>I've seen the DNS operated on distinct inter-networks and in other environments. In those use cases, general purpose, open-source implementations with the code burned (as in previous paragraph) are,well, a pain.</div><div><br></div><div>There's certainly a need to operate the DNS on the global public Internet using general purpose, open source implementations. If there was a better way to separate the management plane from the data plane, people, okay !, would be happier.</div><div><br></div><div><br></div><div><br></div></body></html>