Re: [DNSOP] Call for Adoption: draft-bortzmeyer-rfc7816bis

Paul Wouters <paul@nohats.ca> Tue, 24 July 2018 17:39 UTC

Return-Path: <paul@nohats.ca>
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 9C021130ED0 for <dnsop@ietfa.amsl.com>; Tue, 24 Jul 2018 10:39:06 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.999
X-Spam-Level:
X-Spam-Status: No, score=-1.999 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=nohats.ca
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 ISEQ-_eRWUqb for <dnsop@ietfa.amsl.com>; Tue, 24 Jul 2018 10:39:05 -0700 (PDT)
Received: from mx.nohats.ca (mx.nohats.ca [193.110.157.68]) (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 D8D2B130E80 for <dnsop@ietf.org>; Tue, 24 Jul 2018 10:39:04 -0700 (PDT)
Received: from localhost (localhost [IPv6:::1]) by mx.nohats.ca (Postfix) with ESMTP id 41Zlw63nTKzKFv; Tue, 24 Jul 2018 19:39:02 +0200 (CEST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=nohats.ca; s=default; t=1532453942; bh=aKeh4a59LSdSGv2+Y1c/mxZAIWd/ZOH7if7j4s7zlzg=; h=Date:From:To:cc:Subject:In-Reply-To:References; b=EHPydA/9Mbi1PzAapOYq/18LYQ6039rcdnQ3ER/rYLgbRXCaqIT0a/tvDz2q5ZgMi fsE5qQPUOxeBuY2lYt9J/3DfuGgtZ8Z4h4YT34S4kLZVcOaBxBGgmSKtJZ+5zeRUI4 LM/p2fy0vBAFOu86egqVZN2RCAtKmDQN3sTXcQ9w=
X-Virus-Scanned: amavisd-new at mx.nohats.ca
Received: from mx.nohats.ca ([IPv6:::1]) by localhost (mx.nohats.ca [IPv6:::1]) (amavisd-new, port 10024) with ESMTP id u2jyIYrkQj4M; Tue, 24 Jul 2018 19:39:00 +0200 (CEST)
Received: from bofh.nohats.ca (bofh.nohats.ca [76.10.157.69]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by mx.nohats.ca (Postfix) with ESMTPS; Tue, 24 Jul 2018 19:39:00 +0200 (CEST)
Received: by bofh.nohats.ca (Postfix, from userid 1000) id EEC50940; Tue, 24 Jul 2018 13:38:58 -0400 (EDT)
DKIM-Filter: OpenDKIM Filter v2.11.0 bofh.nohats.ca EEC50940
Received: from localhost (localhost [127.0.0.1]) by bofh.nohats.ca (Postfix) with ESMTP id C21A44009E77; Tue, 24 Jul 2018 13:38:58 -0400 (EDT)
Date: Tue, 24 Jul 2018 13:38:58 -0400 (EDT)
From: Paul Wouters <paul@nohats.ca>
To: Tim Wicinski <tjw.ietf@gmail.com>
cc: dnsop <dnsop@ietf.org>
In-Reply-To: <CADyWQ+GtnmGruu=X2=Bs-NDLdt5TiYui4qk=AW7rG5jc9-MWKg@mail.gmail.com>
Message-ID: <alpine.LRH.2.21.1807241337250.19044@bofh.nohats.ca>
References: <CADyWQ+GtnmGruu=X2=Bs-NDLdt5TiYui4qk=AW7rG5jc9-MWKg@mail.gmail.com>
User-Agent: Alpine 2.21 (LRH 202 2017-01-01)
MIME-Version: 1.0
Content-Type: text/plain; charset=US-ASCII; format=flowed
Archived-At: <https://mailarchive.ietf.org/arch/msg/dnsop/ZUB_fOBG0RGjKrkuU-MgnuefFiA>
Subject: Re: [DNSOP] Call for Adoption: draft-bortzmeyer-rfc7816bis
X-BeenThere: dnsop@ietf.org
X-Mailman-Version: 2.1.27
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: Tue, 24 Jul 2018 17:39:07 -0000

On Tue, 24 Jul 2018, Tim Wicinski wrote:

> We discussed this and there appears to be support to adopt this, with
> the caveat of adding more content to the section on Operational Considerations.
> 
> 
> This starts a Call for Adoption for draft-bortzmeyer-rfc7816bis
> 
> The draft is available here: https://datatracker.ietf.org/doc/draft-bortzmeyer-rfc7816bis/

I strongly support this effort and would like this work to be adopted by
the WG and will commit to contribute text and reviews.

I would like it if it would update some older core DNS RFCs to ensure
that this method of resolving becomes the preferred and default method
for recursive querying (that is, make this method a SHOULD or MUST)

Paul