The chairs spoke with Paul yesterday, and we are in agreement, if the working group feels these are useful terms to be added (and several of them are in common use already), we're good on adopting and fast tracking the whole document.
Tim On Sun, Mar 24, 2019 at 8:02 AM Paul Hoffman <paul.hoff...@icann.org> wrote: > Greetings again. As y'all have seen over the past few weeks, the > discussion of where DNS resolution should happen and over what transports > has caused some people to use conflicting terms. As a possible solution to > the terminology problems, I am proposing a few abbreviations that people > can use in these discussions. The draft below, if adopted by the DNSOP WG, > would update RFC 8499 with a small set of abbreviations. > > --Paul Hoffman > > A New Internet-Draft is available from the on-line Internet-Drafts > directories. > > > Title : Abbreviations for DNS Transports and Location > Author : Paul Hoffman > Filename : draft-hoffman-dns-terminology-ter-00.txt > Pages : 3 > Date : 2019-03-23 > > Abstract: > This document adds abbreviations to "DNS Terminology" (RFC 8499) that > relate to DNS running over various transports, as well as > abbreviations for DNS resolution at traditional and non-traditional > locations. > > [[ This is an early attempt at these terms. They will probably be > improved over time. [] > > > The IETF datatracker status page for this draft is: > https://datatracker.ietf.org/doc/draft-hoffman-dns-terminology-ter/ > > There are also htmlized versions available at: > https://tools.ietf.org/html/draft-hoffman-dns-terminology-ter-00 > https://datatracker.ietf.org/doc/html/draft-hoffman-dns-terminology-ter-00 > > _______________________________________________ > DNSOP mailing list > DNSOP@ietf.org > https://www.ietf.org/mailman/listinfo/dnsop >
_______________________________________________ DNSOP mailing list DNSOP@ietf.org https://www.ietf.org/mailman/listinfo/dnsop
