On Fri, Feb 15, 2019 at 7:49 AM Arnt Gulbrandsen
wrote:
> On Thursday 14 February 2019 22:41:56 CET, Bob Harold wrote:
> > The draft assumes typical TTL is a week, but what I see in the root zone
> is:
> ...
>
> I hoped noone would notice. It's good rather than bad, overall, but it
> complicates
On Thursday 14 February 2019 22:41:56 CET, Bob Harold wrote:
The draft assumes typical TTL is a week, but what I see in the root zone is:
I hoped noone would notice. It's good rather than bad, overall, but it
complicates the description.
A good resolver verifies DNSSEC, so the two-day R
On Thu, Feb 14, 2019 at 12:29 PM Arnt Gulbrandsen
wrote:
> On Thursday 14 February 2019 14:58:58 CET, Tony Finch wrote:
> > How does this relate to:
> >
> > https://tools.ietf.org/html/draft-wkumari-dnsop-hammer
> > https://tools.ietf.org/html/draft-ietf-dnsop-7706bis
>
> It originates in various
On Thursday 14 February 2019 14:58:58 CET, Tony Finch wrote:
How does this relate to:
https://tools.ietf.org/html/draft-wkumari-dnsop-hammer
https://tools.ietf.org/html/draft-ietf-dnsop-7706bis
It originates in various ideas Jiankang and I have chatted about.
I didn't like 7706, because I fee
> On 14 Feb 2019, at 16:12, Warren Kumari wrote:
>
>
>
> On Thu, Feb 14, 2019 at 8:59 AM Tony Finch wrote:
> Jiankang Yao wrote:
> >
> >A new draft about root data caching is proposed, which aims to solve
> >the similar problem presented in RFC7706 and gives the DNS
> >administra
On Thu, Feb 14, 2019 at 8:59 AM Tony Finch wrote:
> Jiankang Yao wrote:
> >
> >A new draft about root data caching is proposed, which aims to solve
> >the similar problem presented in RFC7706 and gives the DNS
> >administrator one more option.
>
> How does this relate to:
>
> https:/
Jiankang Yao wrote:
>
>A new draft about root data caching is proposed, which aims to solve
>the similar problem presented in RFC7706 and gives the DNS
>administrator one more option.
How does this relate to:
https://tools.ietf.org/html/draft-wkumari-dnsop-hammer
https://tools.ietf.o
