When I first looked into DNS, I was recommended with a complex figure of DNS protocol family describing the dependency and activeness of many RFC documents. I'm wondering if it is possible to attach versions to DNS protocol similar like IPv4 and IPv6, http/1.1 and HTTP/2 which can give clear path of DNS evolution and help to keep protocol conformance.
Davey -----邮件原件----- 发件人: DNSOP [mailto:dnsop-boun...@ietf.org] 代表 Shane Kerr 发送时间: 2016年7月8日 22:39 收件人: dnsop@ietf.org 主题: [DNSOP] Fw: New Version Notification for draft-shane-dns-manifesto-00. txt Hello, I've put together some high-level thoughts I had about DNS. I started thinking about this a year or so ago, and typed up an earlier version 9 months ago, but wasn't sure what to do with it. I've been struggling to figure out how to actually make the types of changes that I am thinking of - in the end I guess that the IETF is the best place for this work, if it is possible. So I finally turned them into a draft. My main goal is to try to make the DNS a more agile protocol. Until this is done, working in DNS will always be an exercise in pushing boulders uphill. GitHub page here for pull requests: https://github.com/shane-kerr/DNSManifesto I'm not really sure what the next steps are, if any. One fear I have is that nobody is looking at the overall architecture of the DNS, and so we'll end up muddling along one patch at a time, forever. Hopefully not! Please let me know what you think. Also, I'll be in Berlin for the IETF and happy to discuss things there, with or without beer. ;) Cheers, -- Shane p.s. I did this using Miek Gieben's awesome mmark tool. Writing a Internet Draft in Markdown instead of XML is awesome. AWE-SOME. https://github.com/miekg/mmark _______________________________________________ DNSOP mailing list DNSOP@ietf.org https://www.ietf.org/mailman/listinfo/dnsop
