With no hats, I agree with George that I still don't like Do53.
On Thu, Aug 1, 2019 at 6:30 PM Warren Kumari wrote:
>
> I believe that this should be adopted - having consistent and well
> agreed to terminology is important and helpful. I'm also glad that
> there are people willing to do this
On Thu, Aug 1, 2019 at 9:09 AM Tim Wicinski wrote:
> This starts a Call for Adoption for draft-hoffman-dns-terminology-ter
>
> The draft is available here:
> https://datatracker.ietf.org/doc/draft-hoffman-dns-terminology-ter/
>
> Please review this draft to see if you think it is suitable for ado
I believe that this should be adopted - having consistent and well
agreed to terminology is important and helpful. I'm also glad that
there are people willing to do this - I can think of few things more
annoying to write than a terminology document...
W
On Thu, Aug 1, 2019 at 6:27 PM George Mic
despite my comments at the microphone, +1 for adoption. I think this
is good work and should be closed out.
"and I still don't like do53"
-G
On Fri, Aug 2, 2019 at 2:09 AM Tim Wicinski wrote:
>
>
> Back in 2014, we started with "DNS Terminology" which became RFC7719
> Then In 2016, this became
> > In favour of adoption. Simple, short and clear document.
> +1
+1
From: DNSOP on behalf of Jim Reid
Sent: Thursday, August 1, 2019 10:08 AM
To: Paul Wouters
Cc: Tim Wicinski ; dnsop
Subject: Re: [DNSOP] Call for Adoption: draft-hoffman-dns-terminology-ter
> On 1 Aug 2019, at 18:04, Paul Wouters wrote:
>
> In favour of adoption. Simple, short and clear document.
+1
___
DNSOP mailing list
DNSOP@ietf.org
https://www.ietf.org/mailman/listinfo/dnsop
In favour of adoption. Simple, short and clear document.
Paul
Sent from mobile device
> On Aug 1, 2019, at 12:08, Tim Wicinski wrote:
>
>
> Back in 2014, we started with "DNS Terminology" which became RFC7719
> Then In 2016, this became a BCP version of "DNS Terminology" which is now
> RFC8
On Aug 1, 2019, at 9:08 AM, Tim Wicinski wrote:
>
>
> Back in 2014, we started with "DNS Terminology" which became RFC7719
> Then In 2016, this became a BCP version of "DNS Terminology" which is now
> RFC8499
>
> Now, in 2109, there is a request to include additional terms to reflect
> the new
Back in 2014, we started with "DNS Terminology" which became RFC7719
Then In 2016, this became a BCP version of "DNS Terminology" which is now
RFC8499
Now, in 2109, there is a request to include additional terms to reflect
the new transports DNS is being used over.There is still discussion
ove
