Re: [Add] new draft: draft-grover-add-policy-detection-00

Vittorio Bertola <vittorio.bertola@open-xchange.com> Tue, 09 July 2019 09:26 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 2B9AE1203F8 for <add@ietfa.amsl.com>; Tue, 9 Jul 2019 02:26:34 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.299
X-Spam-Level:
X-Spam-Status: No, score=-4.299 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_MED=-2.3, 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 (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 0ovoXKUEvh1e for <add@ietfa.amsl.com>; Tue, 9 Jul 2019 02:26:32 -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 396FB1203E8 for <add@ietf.org>; Tue, 9 Jul 2019 02:26:32 -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 0A0646A234; Tue, 9 Jul 2019 11:26:30 +0200 (CEST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=open-xchange.com; s=201705; t=1562664390; bh=JquWR4Jr58JLT/LDHC8UkaaDeC5KLWkSEBbiiLI3k/8=; h=Date:From:Reply-To:To:In-Reply-To:References:Subject:From; b=vn3MzieQ3+RrhbZeI9NETQbTzeV7hMWS8qoNEm+pjCmvaThFm8pg7qybN53JPWtys TQ7yOZzDkOVS4NydzTMtyUOCjzp0zXOA5Ma2jBxcQlG84/jKvMyVzjxoIBaNOp9rUT xDWI2FnDn13L3mKH2lZVNTgn1emiXZ9DPTEJj5X0L4j8wzi+CT+GE9TSBDE8fSwhp+ fpcp5/EMrSYx6apkdvWXEYOy7rr20ZvVFwzHIxNN+ZJhnvmN8bR0Kwte/t2UrASAI0 bJbKJKOmhxrks5qYhpwqPdm6mI8exLujZXlRdM8KLe9LvZFyq58TKg787vM5yDQ0we CtDVh5yUo5vhQ==
Received: from appsuite-gw1.open-xchange.com (appsuite-gw1.open-xchange.com [10.20.28.81]) (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 F24193C03A4; Tue, 9 Jul 2019 11:26:29 +0200 (CEST)
Date: Tue, 09 Jul 2019 11:26:29 +0200
From: Vittorio Bertola <vittorio.bertola@open-xchange.com>
Reply-To: Vittorio Bertola <vittorio.bertola@open-xchange.com>
To: Peter Saint-Andre <stpeter@mozilla.com>, Andy Grover <andy@pmtu.dev>, add@ietf.org
Message-ID: <690466758.309.1562664389937@appsuite-gw1.open-xchange.com>
In-Reply-To: <5a6eb897-56b2-b0c4-9710-7df95dfe844d@mozilla.com>
References: <156260800560.777.13636536980052967232.idtracker@ietfa.amsl.com> <65f155e9-81c7-daac-8e77-e366d0f924fb@pmtu.dev> <5a6eb897-56b2-b0c4-9710-7df95dfe844d@mozilla.com>
MIME-Version: 1.0
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: 7bit
X-Priority: 3
Importance: Medium
X-Mailer: Open-Xchange Mailer v7.10.2-Rev6
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/2ePzF4cRHg1qVWnEJiG3PDD69_0>
Subject: Re: [Add] new draft: draft-grover-add-policy-detection-00
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: Tue, 09 Jul 2019 09:26:34 -0000


> Il 8 luglio 2019 22:42 Peter Saint-Andre <stpeter@mozilla.com> ha scritto:
> 
>  
> A point of clarification...
> 
> Paul Hoffman was kind enough to point us to
> draft-sah-resolver-information and draft-sah-resinfo-doh just now, which
> intend to solve a similar problem. It's not that we think those I-Ds
> define a bad approach, instead we missed them entirely. We will read
> them between now and the Montreal meeting so that we can discuss them
> intelligently in person and on the relevant discussion lists.
> 
> Sorry about the lack of due diligence!

Still, if I remember the two sah drafts correctly, they define the basic framework for discovering information about the local resolver, but neither deals with discovering local policy, so we could still turn this effort into an additional document building on sah-resolver to add that piece of information.

If we do, however, I would suggest that we work on a much more nuanced expression of policy behaviour, including the origin of the policy (user, network or law) and perhaps even a description of the reasons and of the types of destinations that are affected. While "neutral" applications might just want to discover that policy exists and avoid Do*-to-the-cloud in any such case, I would expect "opinionated" applications ;-) to behave differently depending on specific policy types and sources, as well as, maybe, the location of the user and other factors. In such case, and barring the problem of lying resolvers, having more detailed information would lead to matching the expectations of the user much more precisely.

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