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
--- Begin Message ---
A new version of I-D, draft-shane-dns-manifesto-00.txt
has been successfully submitted by Shane Kerr and posted to the
IETF repository.

Name:           draft-shane-dns-manifesto
Revision:       00
Title:          A DNS Manifesto
Document date:  2016-07-08
Group:          Individual Submission
Pages:          9
URL:            
https://www.ietf.org/internet-drafts/draft-shane-dns-manifesto-00.txt
Status:         https://datatracker.ietf.org/doc/draft-shane-dns-manifesto/
Htmlized:       https://tools.ietf.org/html/draft-shane-dns-manifesto-00


Abstract:
   The DNS protocol has many things to fix or improve, but this is
   difficult to do because changing the protocol is very hard.  This
   paper explores the good and bad features of the protocol, and calls
   for an effort too make the protocol flexible enough that it can
   evolve in the future.

                                                                                
  


Please note that it may take a couple of minutes from the time of submission
until the htmlized version and diff are available at tools.ietf.org.

The IETF Secretariat


--- End Message ---

Attachment: pgpoQLQ0pPMGR.pgp
Description: OpenPGP digital signature

_______________________________________________
DNSOP mailing list
DNSOP@ietf.org
https://www.ietf.org/mailman/listinfo/dnsop

Reply via email to