Re: [Add] The ADD WG has placed draft-box-add-requirements in state "Call For Adoption By WG Issued"

Stephen Farrell <stephen.farrell@cs.tcd.ie> Thu, 28 January 2021 20:57 UTC

Return-Path: <stephen.farrell@cs.tcd.ie>
X-Original-To: add@ietfa.amsl.com
Delivered-To: add@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 0EF043A1755 for <add@ietfa.amsl.com>; Thu, 28 Jan 2021 12:57:29 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2
X-Spam-Level:
X-Spam-Status: No, score=-2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, NICE_REPLY_A=-0.001, SPF_HELO_NONE=0.001, 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=cs.tcd.ie
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 U0NyLat5lh9r for <add@ietfa.amsl.com>; Thu, 28 Jan 2021 12:57:26 -0800 (PST)
Received: from mercury.scss.tcd.ie (mercury.scss.tcd.ie [134.226.56.6]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 891273A1754 for <add@ietf.org>; Thu, 28 Jan 2021 12:57:26 -0800 (PST)
Received: from localhost (localhost [127.0.0.1]) by mercury.scss.tcd.ie (Postfix) with ESMTP id 68BD7BE2E for <add@ietf.org>; Thu, 28 Jan 2021 20:57:24 +0000 (GMT)
X-Virus-Scanned: Debian amavisd-new at scss.tcd.ie
Received: from mercury.scss.tcd.ie ([127.0.0.1]) by localhost (mercury.scss.tcd.ie [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id ud04UGVPvkM5 for <add@ietf.org>; Thu, 28 Jan 2021 20:57:22 +0000 (GMT)
Received: from [10.244.2.242] (95-45-153-252-dynamic.agg2.phb.bdt-fng.eircom.net [95.45.153.252]) by mercury.scss.tcd.ie (Postfix) with ESMTPSA id 40E8CBE2C for <add@ietf.org>; Thu, 28 Jan 2021 20:57:22 +0000 (GMT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cs.tcd.ie; s=mail; t=1611867442; bh=X6n/LQpG59pwIO/ieZtuJuOtP5hTGQqGsuRKqYiILcU=; h=Subject:To:References:From:Date:In-Reply-To:From; b=DuqH4mSIz02WBspiY9LWOzbfyukJGZuYi+gsYywyrtemlv2wUr03FdICDAUGpE4Vz Zq7AsbU583Iu8SjDpsxAYMXxjlvsrTNBdNAyxPk3pMdBQQSCguMIYZXK5S05umAkzg 2Svt+dGWzkc0tW0m9lpjzQyqL9fOeKcGfA7IdzlY=
To: add@ietf.org
References: <161178940346.18100.17762769750369649470@ietfa.amsl.com>
From: Stephen Farrell <stephen.farrell@cs.tcd.ie>
Message-ID: <05616977-0b14-3890-3349-8fbd09657693@cs.tcd.ie>
Date: Thu, 28 Jan 2021 20:57:21 +0000
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:78.0) Gecko/20100101 Thunderbird/78.6.1
MIME-Version: 1.0
In-Reply-To: <161178940346.18100.17762769750369649470@ietfa.amsl.com>
Content-Type: multipart/signed; micalg="pgp-sha256"; protocol="application/pgp-signature"; boundary="DcUePG4Dye7qDtfvGGkTPYjsloxeHaCfc"
Archived-At: <https://mailarchive.ietf.org/arch/msg/add/TaWg4_PNi8BWSHsXCQq9y5DaDR8>
Subject: Re: [Add] The ADD WG has placed draft-box-add-requirements in state "Call For Adoption By WG Issued"
X-BeenThere: add@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Applications Doing DNS <add.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/add>, <mailto:add-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/add/>
List-Post: <mailto:add@ietf.org>
List-Help: <mailto:add-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/add>, <mailto:add-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 28 Jan 2021 20:57:29 -0000


On 27/01/2021 23:16, IETF Secretariat wrote:
> 
> The ADD WG has placed draft-box-add-requirements in state
> Call For Adoption By WG Issued (entered by Glenn Deen)

I just had a read.

I'm ambivalent as to whether it ought be adopted. I don't
think it needs to end up as an RFC in either case. I guess
that the WG might have an easier time and be more productive
if it did not need to reach consensus on the text of this
draft. As I'm not sure that the WG needs to reach such a
consensus, in the end I'd be a little bit against
adoption.

If adopted, I will argue that we need a requirement that
clients should to be able to select a recursive based on
the client's evaluation of the network, e.g. I might like
a client that picked a well-known Irish recursive when
the client thinks it is in Ireland but does not pick a
local recursive when the client in in some other locale
renowned for censorship. I think stating such a requirement
would be in scope should this be adopted, whether or not
that leads to a need for some new protocol. (I could
envisage some futures in which some new protocol would
be useful to meet this requirement, perhaps if desirable
recursive locators changed very frequently, but equally
there might not be a need in the end, e.g. if clients tend
to include the required information as part of their install
and updates.)

Cheers,
S.

> 
> The document is available at
> https://datatracker.ietf.org/doc/draft-box-add-requirements/
> 
> Comment:
> Based on list and discussion during the January 27th ADD Interim this
> document is being put up for call for WG Adoption.
> 
> WG Call for adoption is open until February 10th, 2021
>