Re: [Add] Proposed charter and BoF request for IETF 106

Vittorio Bertola <vittorio.bertola@open-xchange.com> Wed, 09 October 2019 16:47 UTC

Return-Path: <vittorio.bertola@open-xchange.com>
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 2414B120096 for <add@ietfa.amsl.com>; Wed, 9 Oct 2019 09:47:58 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.199
X-Spam-Level:
X-Spam-Status: No, score=-4.199 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_MESSAGE=0.001, MIME_HTML_ONLY=0.1, RCVD_IN_DNSWL_MED=-2.3, SPF_HELO_NONE=0.001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=open-xchange.com
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 NMJYucnMrlaA for <add@ietfa.amsl.com>; Wed, 9 Oct 2019 09:47:56 -0700 (PDT)
Received: from mx4.open-xchange.com (alcatraz.open-xchange.com [87.191.39.187]) (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 60F6B12089B for <add@ietf.org>; Wed, 9 Oct 2019 09:47:56 -0700 (PDT)
Received: from open-xchange.com (imap.open-xchange.com [10.20.30.10]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by mx4.open-xchange.com (Postfix) with ESMTPS id 8620E6A284; Wed, 9 Oct 2019 18:47:54 +0200 (CEST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=open-xchange.com; s=201705; t=1570639674; bh=CU/2F4qf1r+EbLtnywTCJ8eKb/2RXuydKo2bNPDUHCw=; h=Date:From:Reply-To:To:In-Reply-To:References:Subject:From; b=VGNTXI8KnsxJ5FU74FgHSSia3D5vH7LvGKVjRXrKgzqBnwzKO0cKJ3FIFoCOsAHAT zP7MCVwN+BKtdF3dwl/vEonrSLSj2G/pwkxVzGyRy6omizUi/JowVbsurxi780hPah PBkgx9cgcqR2mBH5bfj7Uy4G0Z4+cnwmNEU9oDTrEIHWDcVBAy3RXfS/mbJiOX1ck/ FTuRwpXfiGSaCp5fjU0lYrbNyoNNS5DamAXZQfhPE4mO+aAMBXgvhDtXk3I8pLIk3P EqhkpZyosSzYKkzPrE9i3S/FUL28iLlM8j2nCiR/ckoyMOj/HTDPNhW/uVmYEIjMVD S/c+Occ4MrxZA==
Received: from appsuite-gw2.open-xchange.com (appsuite-gw2.open-xchange.com [10.20.28.82]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by open-xchange.com (Postfix) with ESMTPSA id 7957B3C04BB; Wed, 9 Oct 2019 18:47:54 +0200 (CEST)
Date: Wed, 09 Oct 2019 18:47:54 +0200
From: Vittorio Bertola <vittorio.bertola@open-xchange.com>
Reply-To: Vittorio Bertola <vittorio.bertola@open-xchange.com>
To: Richard Barnes <rlb@ipv.sx>, add@ietf.org
Message-ID: <1286342342.28404.1570639674402@appsuite-gw2.open-xchange.com>
In-Reply-To: <CAL02cgR_61TNnPy=ios+hQFs_tjfYNXu-sBpbDL-HBY+QsY40A@mail.gmail.com>
References: <CALaySJLxXVuHQNfTnaeKZ_R9xtBYWfbta+A1bWcE-ZQZwd3VZg@mail.gmail.com> <CABcZeBMkAFZW9mWjw92v+OR0Fa8ed+P80yc78eY07hCpsCNY6Q@mail.gmail.com> <CABcZeBOOq4FHVoxsyApzOc4VtTbMwZn7858-E+4kr21Z0r5wrA@mail.gmail.com> <CAL02cgR_61TNnPy=ios+hQFs_tjfYNXu-sBpbDL-HBY+QsY40A@mail.gmail.com>
MIME-Version: 1.0
Content-Type: text/html; charset="UTF-8"
Content-Transfer-Encoding: 7bit
X-Priority: 3
Importance: Normal
X-Mailer: Open-Xchange Mailer v7.10.2-Rev13
X-Originating-Client: open-xchange-appsuite
Autocrypt: addr=vittorio.bertola@open-xchange.com; prefer-encrypt=mutual; keydata= mQENBFhFR+UBCACfoywFKBRfzasiiR9/6dwY36eLePXcdScumDMR8qoXvRS55QYDjp5bs+yMq41qWV9 xp/cqryY9jnvHbeF3TsE5yEazpD1dleRbkpElUBpPwXqkrSP8uXO9KkS9KoX6gdml6M4L+F82WpqYC1 uTzOE6HPmhmQ4cGSgoia2jolxAhRpzoYN99/BwpvoZeTSLP5K6yPlMPYkMev/uZlAkMMhelli9IN6yA yxcC0AeHSnOAcNKUr13yXyMlTyi1cdMJ4sk88zIbefxwg3PAtYjkz3wgvP96cNVwAgSt4+j/ZuVaENP pgVuM512m051j9SlspWDHtzrci5pBKKFsibnTelrABEBAAG0NUJlcnRvbGEsIFZpdHRvcmlvIDx2aXR 0b3Jpby5iZXJ0b2xhQG9wZW4teGNoYW5nZS5jb20+iQFABBMBAgAqBAsJCAcGFQoJCAsCBRYCAwEAAp 4BAhsDBYkSzAMABQMAAAAABYJYRUflAAoJEIU2cHmzj8qNaG0H/ROY+suCP86hoN+9RIV66Ej8b3sb8 UgwFJOJMupZfeb9yTIJwE4VQT5lTt146CcJJ5jvxD6FZn1Htw9y4/45pPAF7xLE066jg3OqRvzeWRZ3 IDUfJJIiM5YGk1xWxDqppSwhnKcMOuI72iioWxX0nGQrWxpnWJsjt08IEEwuYucDkul1PHsrLJbTd58 fiMKLVwag+IE1SPHOwkPF6arZQZIfB5ThtOZV+36Jn8Hok9XfeXWBVyPkiWCQYVX39QsIbr0JNR9kQy 4g2ZFexOcTe8Jo12jPRL7V8OqStdDes3cje9lWFLnX05nrfLuE0l0JKWEg8akN+McFXc+oV68h7nu5A Q0EWEVH5QEIAIDKanNBe1uRfk8AjLirflZO291VNkOAeUu+dIhecGnZeQW6htlDinlYOnXhtsY1mK9W PUu+xshDq7lXn2G0LxldYwyJYZaJtDgIKqVqwxfA34Lj27oqPuXwcvGhdCgt0SW/YcalRdAi0/AzUCu 5GSaj2kaGUSnBYYUP4szGJXjaK2psP5toQSCtx2pfSXQ6MaqPK9Zzy+D5xc6VWQRp/iRImodAcPf8fg JJvRyJ8Jla3lKWyvBBzJDg6MOf6Fts78bJSt23X0uPp93g7GgbYkuRMnFI4RGoTVkxjD/HBEJ0CNg22 hoHJondhmKnZVrHEluFuSnW0wBEIYomcPSPB+cAEQEAAYkBMQQYAQIAGwUCWEVH5QIbDAQLCQgHBhUK CQgLAgUJEswDAAAKCRCFNnB5s4/KjdO8B/wNpvWtOpLdotR/Xh4fu08Fd63nnNfbIGIETWsVi0Sbr8i E5duuGaaWIcMmUvgKe/BM0Fpj9X01Zjm90uoPrlVVuQWrf+vFlbalUYVZr51gl5UyUFHk+iAZCAA0WB rsmACKvuV1P7GuiX3UV9b59T9taYJxN3dNFuftrEuvsqHimFtlekUjUwoCekTJdncFusBhwz2OrKhHr WWrEsXkfh0+pURWYAlKlTxvXuI7gAfHEQM+6OnrWvXYtlhd0M1sBPnCjbyG63Qws7Rek9bEWKtH6dA6 dmT2FQT+g1S9Mdf0WkPTQNX0x24dm8IoHuD3KYwX7Svx43Xa17aZnXqUjtj1
Archived-At: <https://mailarchive.ietf.org/arch/msg/add/5BpLUV6QEj5SK1T61qrAZhRHuB4>
Subject: Re: [Add] Proposed charter and BoF request for IETF 106
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: Wed, 09 Oct 2019 16:47:58 -0000


Il 9 ottobre 2019 16:21 Richard Barnes <rlb@ipv.sx> ha scritto:


I think EKR is on the right track here. 

There is a bright line here between technology and deployment policy.  The former we have some hope of progressing on, and there are meaty questions around how applications can discover local network capabilities and preferences in a way that is not open to abuse like the mechanisms we have today.  On questions of the latter form, the entire history of this list, and the meeting that preceded it demonstrate, that there is very little hope of consensus. 

The charter right now has some of both.  If this charter is to go forward, it should be refactored to focus on engineering questions, and avoid policy questions.  In particular, the BCP item needs to be struck.
I see the reasons behind this line of thought, but honestly, seen from my viewpoint, it looks like the IETF is playing hide and seek on the non-technical issues. It starts a deep change in a basic technology for the entire Internet, with at least one AD stating in public things like "we're going to save dissidents and journalists with this new technology", then when the real world problems of that approach come up, the IETF backs away and says "sorry, we only deal with the engineering questions". So yes, you can strike any policy and deployment model discussion from the charter, but then you should also strike RFC 7258 - what is it, if not a policy statement?

(Before someone jumps at my throat, I'll stress that I'm not actually arguing against RFC 7258, I'm just noting that it's too late to claim that the IETF does not do policy, at least in this area.)

This said, I do not have a firm opinion yet on this; I see that having the deployment model in the charter might derail technical developments that could instead get to consensus. So it might still be a wise decision for the IETF to say "we have realized that there are complex policy and juridical issues stemming from this and we are not well equipped to deal with them, so we declare them out of scope".

The unavoidable consequence, however, would be that the policy discussion moves somewhere else, possibly somewhere in the I* galaxy, for the global, non-binding and opinion-making debates, and into national Parliaments for any hard law if required. So the IETF must then be prepared to accept that other parts of the ecosystem might have other views on how the DNS should work and which use cases it should support, and cooperate with their conclusions.

And to be honest, even if the IETF decided to tackle the policy issues and managed to come up with a best practice, it could easily be that other policymaking entities got to different conclusions and asked the engineers to align.

--

Vittorio Bertola | Head of Policy & Innovation, Open-Xchange
vittorio.bertola@open-xchange.com
Office @ Via Treviso 12, 10144 Torino, Italy