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

<chris.box@bt.com> Wed, 09 October 2019 13:36 UTC

Return-Path: <chris.box@bt.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 2C781120108 for <add@ietfa.amsl.com>; Wed, 9 Oct 2019 06:36:13 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.701
X-Spam-Level:
X-Spam-Status: No, score=-2.701 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_LOW=-0.7, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=bt.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 kE8GdaAMR02U for <add@ietfa.amsl.com>; Wed, 9 Oct 2019 06:36:11 -0700 (PDT)
Received: from smtpe1.intersmtp.com (smtpe1.intersmtp.com [213.121.35.77]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id BAD31120106 for <add@ietf.org>; Wed, 9 Oct 2019 06:36:10 -0700 (PDT)
Received: from tpw09926dag06g.domain1.systemhost.net (10.9.202.29) by BWP09926082.bt.com (10.36.82.113) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA384_P256) id 15.1.1713.5; Wed, 9 Oct 2019 14:36:03 +0100
Received: from tpw09926dag18e.domain1.systemhost.net (10.9.212.18) by tpw09926dag06g.domain1.systemhost.net (10.9.202.29) with Microsoft SMTP Server (TLS) id 15.0.1395.4; Wed, 9 Oct 2019 14:36:07 +0100
Received: from RDW083A011ED67.bt.com (10.187.98.37) by tpw09926dag18e.domain1.systemhost.net (10.9.212.18) with Microsoft SMTP Server (TLS) id 15.0.1395.4 via Frontend Transport; Wed, 9 Oct 2019 14:36:07 +0100
Received: from GBR01-CWL-obe.outbound.protection.outlook.com (104.47.20.50) by smtpe1.intersmtp.com (62.239.224.235) with Microsoft SMTP Server (TLS) id 14.3.439.0; Wed, 9 Oct 2019 14:42:31 +0100
ARC-Seal: i=1; a=rsa-sha256; s=arcselector9901; d=microsoft.com; cv=none; b=mk7gq/DRdPkJ15isa3h977DPsNlTDmnf7orJB4xrXuMqxzKTW2aCp+PZuXTIRzkWms1ZpWd2PBBUrZSr9tu+PP62vxwNg2cSR5N3MKWRl23YOfgFSS/wUitSp91JTshkaqU9zt8E35kCr88Ae8S37AkX/tHDHAQAtmgLPbQdBior6Or/mL2v+P3DFzRkUgDgCkqUqLwKgxA5v5d5YditD7X3HaFS13/m4bHTSRXjuVsJmVCSirlYNqZN8bpYYWirYY5fJJTGuyECQXgP9IGE3Budzoc3Z83ciTo5EqbGUIq0tEMMiUCd7aLkOxcq7IsSvJt7TTKVC0jTrTEUTIDznQ==
ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=microsoft.com; s=arcselector9901; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-SenderADCheck; bh=oD8CF+Pg7rGgCwMoku05amQCoP41sEHKjUYb7KP/5Y0=; b=RINJGXT1eNDWnuxCOHexYOkROkN7ZdFD2NNiteMkEdvDNPtauqWXsGwLmRpTo4LJqSkh9LgcOEPnona5AWiQbbL8DkIKl9B5IDZn6uLycgtRupJ386UAtD01CQ0R2z+W4LGzWDQAHiFGwq8wKyqkG2LyJvj+BgetubEKYI9MBvjJPUZQFbtwbKcWqcedtVozSXaI/OWWmQvhd3WmBokvkQyLrsJWfOWlAIvfVel7dokaobqE2xQNidxxZGffeV56+VKpJfljmULdIVobcIX0/sN0YsKSxWJUVFPDZBg12rgMOTuDr85IsN16KWmwa1wZAgkhJgZjLNazVUF0SUzIHg==
ARC-Authentication-Results: i=1; mx.microsoft.com 1; spf=pass smtp.mailfrom=bt.com; dmarc=pass action=none header.from=bt.com; dkim=pass header.d=bt.com; arc=none
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=bt.com; s=selector2; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-SenderADCheck; bh=oD8CF+Pg7rGgCwMoku05amQCoP41sEHKjUYb7KP/5Y0=; b=LQwLJUvQAw5Qf4MQftcVsRxvd3TD/uTiZoRykHC2+zMiS+Lw6EQXHnmB20u78b27wSjcKsbuF/yfMBjHY8/qkj4+36R4VfWlCY3dKqPOy2eBqMZPhVeDm1BiQkmKsIZJiSrNn2QF9Aq+JyJXbBgc/eEYPQvGBvN0/oiY/UV5jlQ=
Received: from LO2P123MB2256.GBRP123.PROD.OUTLOOK.COM (20.176.158.15) by LO2P123MB2221.GBRP123.PROD.OUTLOOK.COM (20.176.156.143) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.2327.24; Wed, 9 Oct 2019 13:36:06 +0000
Received: from LO2P123MB2256.GBRP123.PROD.OUTLOOK.COM ([fe80::dd6a:f080:9df6:1f56]) by LO2P123MB2256.GBRP123.PROD.OUTLOOK.COM ([fe80::dd6a:f080:9df6:1f56%7]) with mapi id 15.20.2305.023; Wed, 9 Oct 2019 13:36:05 +0000
From: chris.box@bt.com
To: add@ietf.org
Thread-Topic: [Add] Proposed charter and BoF request for IETF 106
Thread-Index: AQHVfnSoqWCRx2OPVUOUSXPqDCOCg6dSNM6AgAAV++A=
Date: Wed, 09 Oct 2019 13:36:05 +0000
Message-ID: <LO2P123MB2256A416C25822B08BCCF9409B950@LO2P123MB2256.GBRP123.PROD.OUTLOOK.COM>
References: <CALaySJLxXVuHQNfTnaeKZ_R9xtBYWfbta+A1bWcE-ZQZwd3VZg@mail.gmail.com> <CABcZeBMkAFZW9mWjw92v+OR0Fa8ed+P80yc78eY07hCpsCNY6Q@mail.gmail.com>
In-Reply-To: <CABcZeBMkAFZW9mWjw92v+OR0Fa8ed+P80yc78eY07hCpsCNY6Q@mail.gmail.com>
Accept-Language: en-GB, en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
authentication-results: spf=none (sender IP is ) smtp.mailfrom=chris.box@bt.com;
x-originating-ip: [217.39.12.16]
x-ms-publictraffictype: Email
x-ms-office365-filtering-correlation-id: d759edc3-bcce-4b46-e6f7-08d74cbda2c8
x-ms-traffictypediagnostic: LO2P123MB2221:
x-microsoft-antispam-prvs: <LO2P123MB22216586726E7A3B979D2B809B950@LO2P123MB2221.GBRP123.PROD.OUTLOOK.COM>
x-antispam-2: 1
x-ms-oob-tlc-oobclassifiers: OLM:10000;
x-forefront-prvs: 018577E36E
x-forefront-antispam-report: SFV:NSPM; SFS:(10009020)(4636009)(136003)(376002)(346002)(396003)(366004)(39860400002)(51914003)(189003)(199004)(55016002)(229853002)(6246003)(316002)(81156014)(52536014)(81166006)(66066001)(71200400001)(99286004)(76116006)(14454004)(64756008)(66556008)(33656002)(66476007)(66446008)(66946007)(256004)(6116002)(71190400001)(6916009)(3846002)(8676002)(478600001)(2906002)(26005)(9686003)(86362001)(5660300002)(186003)(305945005)(446003)(476003)(25786009)(11346002)(486006)(7736002)(6506007)(102836004)(7696005)(6436002)(8936002)(74316002)(76176011); DIR:OUT; SFP:1101; SCL:1; SRVR:LO2P123MB2221; H:LO2P123MB2256.GBRP123.PROD.OUTLOOK.COM; FPR:; SPF:None; LANG:en; PTR:InfoNoRecords; MX:1; A:1;
received-spf: None (protection.outlook.com: bt.com does not designate permitted sender hosts)
x-ms-exchange-senderadcheck: 1
x-microsoft-antispam: BCL:0;
x-microsoft-antispam-message-info: qqOYtwcK7coqZszAxMIX+xhgpdcMRwXo/Ya/NJgGn3LCVAxKSW9XOXJvwdH/5y1KhnwSYrn8NvKZxZGEh0PVrxTf66ZXPOpuSpqrhhPFqIEI7kkR6n64/BkNKGneC1abLQf8O8yn2dpgaWSLbenQyMDR+EICpFg65P4cQBodXoM+1inyhBwXV/oZ7scfGrSZFzUesj8THiCPla9cVbAS5Nqt+UiQ0Fy6Af6UonkkTbJkwCFTlE2YVD9PaWL+CfgqmdwbtlGn6ztaF3XQiBElAhDwLkyf/8tqYbvcnSYTRjBbcRQUAMrB3okK+ERIUNo7GnB2uw6ry3qMr9FjpKhwV1WVGCfLZwiQGwZdrCctJ6qvOpdO8Pk3HdvdFDQav78Qe0xBhtEQW5daKGhkH97lILtwRP0jn4cN2nYjXe8BrQo=
x-ms-exchange-transport-forked: True
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64
MIME-Version: 1.0
X-MS-Exchange-CrossTenant-Network-Message-Id: d759edc3-bcce-4b46-e6f7-08d74cbda2c8
X-MS-Exchange-CrossTenant-originalarrivaltime: 09 Oct 2019 13:36:05.9140 (UTC)
X-MS-Exchange-CrossTenant-fromentityheader: Hosted
X-MS-Exchange-CrossTenant-id: a7f35688-9c00-4d5e-ba41-29f146377ab0
X-MS-Exchange-CrossTenant-mailboxtype: HOSTED
X-MS-Exchange-CrossTenant-userprincipalname: /bFix9ugTl0hkhzw0OqgDesKLJO5roAHhvjsX//FxbbxnMhlWD4Y56Om12bUKpnWEpmnBE8OyprylIItzKrN+w==
X-MS-Exchange-Transport-CrossTenantHeadersStamped: LO2P123MB2221
X-OriginatorOrg: bt.com
Archived-At: <https://mailarchive.ietf.org/arch/msg/add/ufXcWc2L55uj3DbJXlJ_urjlm-g>
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 13:36:13 -0000

Barry, I second the thanks for the charter, which in general looks to me that it could be a good way forward.

I'll pick up on a couple of Ekr's points:

> I think we should stay away from
> anything that is about specifying best current practices because as
> far as I can tell all but the most trivial ones (here is how to safely
> run a TLS server or something) are contested. For instance, even
> retention period has very strong views on both sides.

In my view BCPs are clearly needed, as a means of resolving the contested areas. If I thought rough concensus was impossible I would agree with Eric, but I'm more optimistic.

> This list of practices would be much more accurate if it included the
> resolver-level DNS practices that we are trying to mitigate using DoH,
> including NXDOMAIN synthesis and collection of user browsing history
> data.
> Just having network operators transition to secure transports while
> continuing their current practices does not address the issue.

Please point me to an operator that is arguing for the continuing of NXDOMAIN monetisation. BT is not, nor is Comcast. I don't see why we can't have ABCD work on a declaration that these practises are not permissible except in defined circumstances (e.g. user's express wish, perhaps others). The signalling of policies that you refer to could be part of that statement.

> This seems like it leaves all of the contested issues firmly
> in scope. I can't imagine how we're going to get consensus on
> best current practices, when we can't even agree on the terms
> for resolver selection.

Yes it's hard, and some compromise will be required, but it's worth attempting this in ABCD.

Chris