Re: [DNSOP] Fw: New Version Notification for draft-arnt-yao-dnsop-root-data-caching-00.txt

Benno Overeinder <benno@NLnetLabs.nl> Thu, 14 February 2019 15:35 UTC

Return-Path: <benno@NLnetLabs.nl>
X-Original-To: dnsop@ietfa.amsl.com
Delivered-To: dnsop@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 92DB4131054 for <dnsop@ietfa.amsl.com>; Thu, 14 Feb 2019 07:35:56 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -7
X-Spam-Level:
X-Spam-Status: No, score=-7 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_HI=-5, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=nlnetlabs.nl
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id jfdzduxupcUX for <dnsop@ietfa.amsl.com>; Thu, 14 Feb 2019 07:35:54 -0800 (PST)
Received: from dicht.nlnetlabs.nl (dicht.nlnetlabs.nl [185.49.140.10]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id A3499130F0E for <dnsop@ietf.org>; Thu, 14 Feb 2019 07:35:54 -0800 (PST)
Received: from [IPv6:2a04:b900::1:7d91:423f:c7fd:5627] (unknown [IPv6:2a04:b900:0:1:7d91:423f:c7fd:5627]) by dicht.nlnetlabs.nl (Postfix) with ESMTPSA id E3A7D1743B; Thu, 14 Feb 2019 16:35:51 +0100 (CET)
Authentication-Results: dicht.nlnetlabs.nl; dmarc=pass (p=none dis=none) header.from=NLnetLabs.nl
Authentication-Results: dicht.nlnetlabs.nl; spf=pass smtp.mailfrom=benno@NLnetLabs.nl
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=nlnetlabs.nl; s=default; t=1550158551; bh=yqcTPNnGxy5736/wtBjugL298r3TNrVi9rzci4Zj0gU=; h=Subject:From:In-Reply-To:Date:Cc:References:To; b=rroVwifo2+2HgxP+J44G1MOlm0Rqyp5kBqn/u++SOWwtyWSN7YJl26X9JBXMgdihA Rlll+3rqK4ruXSeujGBIdAWtDkGAXUsTIJ6URr/lSpgrgffUKh5DjyoXIVJVvJShOe 963MX5Sks7HsWx+FlF7LFddduggMm71XDcCgjqas=
Content-Type: text/plain; charset=utf-8
Mime-Version: 1.0 (Mac OS X Mail 12.2 \(3445.102.3\))
From: Benno Overeinder <benno@NLnetLabs.nl>
In-Reply-To: <CAHw9_i+y0jqzFGShzUmuQ_CUgomnQxacE5DR+xjtgkj0Uoy4mg@mail.gmail.com>
Date: Thu, 14 Feb 2019 16:35:51 +0100
Cc: Tony Finch <dot@dotat.at>, Jiankang Yao <yaojk@cnnic.cn>, arnt <arnt@gulbrandsen.priv.no>, dnsop <dnsop@ietf.org>
Content-Transfer-Encoding: quoted-printable
Message-Id: <D31E0973-1BE0-45F6-8561-453FEEA5276F@NLnetLabs.nl>
References: <4d51e683.32d.168ea651be8.Coremail.yaojk@cnnic.cn> <alpine.DEB.2.20.1902141349060.18720@grey.csi.cam.ac.uk> <CAHw9_i+y0jqzFGShzUmuQ_CUgomnQxacE5DR+xjtgkj0Uoy4mg@mail.gmail.com>
To: Warren Kumari <warren@kumari.net>
X-Mailer: Apple Mail (2.3445.102.3)
Archived-At: <https://mailarchive.ietf.org/arch/msg/dnsop/JCf5XUDdyLsbYVewD03NiBN0eoM>
Subject: Re: [DNSOP] Fw: New Version Notification for draft-arnt-yao-dnsop-root-data-caching-00.txt
X-BeenThere: dnsop@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: IETF DNSOP WG mailing list <dnsop.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dnsop>, <mailto:dnsop-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/dnsop/>
List-Post: <mailto:dnsop@ietf.org>
List-Help: <mailto:dnsop-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dnsop>, <mailto:dnsop-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 14 Feb 2019 15:35:57 -0000

> On 14 Feb 2019, at 16:12, Warren Kumari <warren@kumari.net> wrote:
> 
> 
> 
> On Thu, Feb 14, 2019 at 8:59 AM Tony Finch <dot@dotat.at> wrote:
> Jiankang Yao <yaojk@cnnic.cn> 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
> 
> ... and our plan is to still (in our copious free time!) update this to simplify it, and update it to be more of a "this is how implementations have implemented this" -- the document is close to cooked, and we'd dearly love a short bit from implementers describing how they did it…
> 

<implementers hat on>

Noted.

— Benno


-- 
Benno J. Overeinder
NLnet Labs
https://www.nlnetlabs.nl/