Re: [Add] What to do in this potential working group
"Livingood, Jason" <Jason_Livingood@comcast.com> Thu, 22 August 2019 23:48 UTC
Return-Path: <Jason_Livingood@comcast.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 43D5112011B for <add@ietfa.amsl.com>; Thu, 22 Aug 2019 16:48:24 -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, 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=comcast.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 4bn46IdB0gJv for <add@ietfa.amsl.com>; Thu, 22 Aug 2019 16:48:22 -0700 (PDT)
Received: from copdcmhout02.cable.comcast.com (copdcmhout02.cable.comcast.com [96.114.158.212]) (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 7FB69120089 for <add@ietf.org>; Thu, 22 Aug 2019 16:48:22 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; d=comcast.com; s=20190412; c=relaxed/simple; q=dns/txt; i=@comcast.com; t=1566517701; x=2430431301; h=From:Sender:Reply-To:Subject:Date:Message-ID:To:Cc:MIME-Version:Content-Type: Content-Transfer-Encoding:Content-ID:Content-Description:Resent-Date:Resent-From: Resent-Sender:Resent-To:Resent-Cc:Resent-Message-ID:In-Reply-To:References:List-Id: List-Help:List-Unsubscribe:List-Subscribe:List-Post:List-Owner:List-Archive; bh=PCPRJ1yZuOg/tibJflZgTdaf4RhoEAY0oYFo2R7G7i8=; b=i6OchnyfM8qNsTY6UTkSkWN4NsjTGpD9CfHQBHslkKz0GU1nRIsL9U+COpv7fsMP qqFdFkG78LMRZXnhyai++LvsXuyADuDg28hIWOTX31zrakZHljjOfs9A4iBe2dPy IMbnBzud97cG4CJoUdNIoNI6A8ffIzs06+RAaj5PL+ebovtgzIb490zAHGTFX7FH 723RtsHIWc/1MS3akCtC+pK5lBGvGHXD1Xdl4IyVYRnBDzaG820GWMvLfQ32CESW Acd45fwW3/cBCnxI1aPFOsbzfMxXRC/rb30YUo2c1SPpgdumT5J+8+SCZWyjw+Fw 1XRDpTGGj3RZf66mnwkZKg==;
X-AuditID: 60729ed4-227ff700000013e0-05-5d5f29c5770a
Received: from COPDCEXC37.cable.comcast.com (copdcmhoutvip.cable.comcast.com [96.114.156.147]) (using TLS with cipher ECDHE-RSA-AES256-SHA384 (256/256 bits)) (Client did not present a certificate) by copdcmhout02.cable.comcast.com (SMTP Gateway) with SMTP id 0B.1E.05088.5C92F5D5; Thu, 22 Aug 2019 17:48:21 -0600 (MDT)
Received: from COPDCEXC37.cable.comcast.com (147.191.125.136) by COPDCEXC37.cable.comcast.com (147.191.125.136) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA256_P256) id 15.1.1713.5; Thu, 22 Aug 2019 19:48:20 -0400
Received: from COPDCEXC37.cable.comcast.com ([fe80::3aea:a7ff:fe36:8a94]) by COPDCEXC37.cable.comcast.com ([fe80::3aea:a7ff:fe36:8a94%15]) with mapi id 15.01.1713.008; Thu, 22 Aug 2019 19:48:20 -0400
From: "Livingood, Jason" <Jason_Livingood@comcast.com>
To: Adam Roach <adam@nostrum.com>, "add@ietf.org" <add@ietf.org>
Thread-Topic: [Add] What to do in this potential working group
Thread-Index: AQHVV5Ij9AP+pxnvJEqQu+QNkzMYhKcFiL2AgAAo9ICAAHAxAIAAO8gAgAAEp4CAAXawgA==
Date: Thu, 22 Aug 2019 23:48:20 +0000
Message-ID: <E317C0A3-D243-4287-9D93-42F4DB58202A@cable.comcast.com>
References: <A1128702-1E19-4657-9740-E84AE09992F2@piuha.net> <CABcZeBMfOTjq-8hDDoKMtJvfHUA5nC8o60zuk-2Xe-ZhfwriJQ@mail.gmail.com> <766112E1-F532-4C6B-8CA8-A096671E02EE@piuha.net> <CA+9kkMAfuOwJu8_qJTuhAY4mUwR+tVUxr+k3QFHBk3byV672Ow@mail.gmail.com> <E83D9594-E7CB-4DAC-8EDC-333E9B0964F1@piuha.net> <279abf8c-198b-5da8-1cb9-4f86bf1f37c7@nostrum.com>
In-Reply-To: <279abf8c-198b-5da8-1cb9-4f86bf1f37c7@nostrum.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
user-agent: Microsoft-MacOutlook/10.1c.0.190812
x-originating-ip: [96.115.73.253]
Content-Type: text/plain; charset="utf-8"
Content-ID: <B26DAC35117BC24781EC6DCF0C6EA01F@comcast.com>
Content-Transfer-Encoding: base64
MIME-Version: 1.0
X-CFilter-Loop: Forward
X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFprHKsWRmVeSWpSXmKPExsWSUDRnsu5RzfhYg73/+C32/F3EbvH/9Do2 ByaPJUt+MnnM2vmEJYApqoHRpiSjKDWxxCU1LTWvONWOSwED2CSlpuUXpbomFuVUBqXmpCZi VwZSmZKak1mWWqSP1Rh9rOYkdDFl/Nh+k73gAl/F/SWz2BsYF/B1MXJySAiYSGxYPIWpi5GL Q0jgCJPEzK1rWCGcFiaJfW1bGSGc04wSa/fvZwNpYRMwk7i78AoziC0i4CAx/f8VFhBbWMBW Ym7nbXaIuJ3E05/7mCDsMInlf56zgtgsAqoSty5+ALN5BVwkplzcww6x4CmTxOlll8AWcArY S9ydfhSsmVFATOL7qTVgNrOAuMStJ/OZIO4WkFiy5zwzhC0q8fLxP7ChogL6Ekt+bGaFiCtK 7PuwAqiGA6hXU2L9Ln2IMVYSa99vYoSwFSWmdD9kh7hHUOLkzCcsEK3iEoeP7GCdwCgxC8nm WQiTZiGZNAvJpFlIJi1gZF3FyGdppmdoaKJnaGqhZ2RotIkRnGrmXdnBeHm6xyFGAQ5GJR7e 5SrxsUKsiWXFlbmHGCU4mJVEeMsmxsUK8aYkVlalFuXHF5XmpBYfYpTmYFES52Xtjo0VEkhP LEnNTk0tSC2CyTJxcEo1MJa/Ob+AZ2/ZVMXl3384WX1iTd395B9v0M5rnokt5g7vxF6tlT31 /V7lyqS1IrbaBybLH53R+ijO/tSkJstUq++pWu+Wd7DLp9kqhcbv+fSV40xv6xrWsAi5b4F3 O2sUc30WL7bkLb5RbZ6d3l4WucSlb+lqAW0mr8ZWextHxc5rnSJO7jqGSizFGYmGWsxFxYkA 8pb+oDEDAAA=
Archived-At: <https://mailarchive.ietf.org/arch/msg/add/OpzQ3m0U51M93zqlNBuhm71_Cc4>
Subject: Re: [Add] What to do in this potential working group
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, 22 Aug 2019 23:48:24 -0000
On 8/21/19, 5:34 PM, "Add on behalf of Adam Roach" <add-bounces@ietf.org on behalf of adam@nostrum.com> wrote: > I really wish people wouldn't persist in ignoring repeated explanations that Firefox (at least) will have actual user interaction at the time that DoH is made available in a user's region, with a one-click option to turn it off. [JL] It might be useful, when your UX team is ready, to share what the user interaction flow will look like, how the choices are presented, and what the defaults are. This could lead the way for others and help establish best practices and transparency. Certainly there's been lots of discussions on 'dark patterns' in UX design (see https://gizmodo.com/senators-introduce-bill-to-stop-dark-patterns-huge-plat-1833929276), so I think end users are getting increasingly sensitized to how interface design choices can drive user selections/behavior. [JL] If the TRR program is successful then you'll be adding new TRRs all the time. As a result, it might also be useful to describe whether users will be prompted again/periodically in the future, such as when a new TRR was detected that is local to them (e.g. on-network via their ISP) and suggesting they may wish to switch to that one -- or what happens when a change in geography is detected (e.g. the user has moved from NYC to Tokyo).
- [Add] What to do in this potential working group Jari Arkko
- Re: [Add] What to do in this potential working gr… Eric Orth
- Re: [Add] What to do in this potential working gr… Jari Arkko
- Re: [Add] What to do in this potential working gr… Eric Rescorla
- Re: [Add] What to do in this potential working gr… Jim Reid
- Re: [Add] What to do in this potential working gr… Vittorio Bertola
- Re: [Add] What to do in this potential working gr… Jari Arkko
- Re: [Add] What to do in this potential working gr… Eric Vyncke (evyncke)
- Re: [Add] What to do in this potential working gr… Ted Lemon
- Re: [Add] What to do in this potential working gr… Jim Reid
- Re: [Add] What to do in this potential working gr… Ted Lemon
- Re: [Add] What to do in this potential working gr… Tommy Jensen
- Re: [Add] What to do in this potential working gr… Jari Arkko
- Re: [Add] What to do in this potential working gr… Eric Rescorla
- Re: [Add] What to do in this potential working gr… Ray Bellis
- Re: [Add] What to do in this potential working gr… Eric Rescorla
- Re: [Add] What to do in this potential working gr… Ray Bellis
- Re: [Add] What to do in this potential working gr… Eric Rescorla
- Re: [Add] What to do in this potential working gr… Ted Hardie
- Re: [Add] What to do in this potential working gr… David Conrad
- Re: [Add] What to do in this potential working gr… Alec Muffett
- Re: [Add] What to do in this potential working gr… Ted Hardie
- Re: [Add] What to do in this potential working gr… David Conrad
- Re: [Add] What to do in this potential working gr… Brian Dickson
- Re: [Add] What to do in this potential working gr… Brian Dickson
- Re: [Add] What to do in this potential working gr… Stephen Farrell
- Re: [Add] What to do in this potential working gr… Ted Hardie
- Re: [Add] What to do in this potential working gr… Alec Muffett
- Re: [Add] What to do in this potential working gr… Stephen Farrell
- Re: [Add] What to do in this potential working gr… David Conrad
- Re: [Add] What to do in this potential working gr… Rob Sayre
- Re: [Add] What to do in this potential working gr… Jari Arkko
- Re: [Add] What to do in this potential working gr… Stephen Farrell
- Re: [Add] What to do in this potential working gr… Alec Muffett
- Re: [Add] What to do in this potential working gr… Ted Hardie
- Re: [Add] What to do in this potential working gr… Adam Roach
- Re: [Add] What to do in this potential working gr… Ted Hardie
- Re: [Add] What to do in this potential working gr… David Conrad
- Re: [Add] What to do in this potential working gr… Rob Sayre
- Re: [Add] What to do in this potential working gr… Stephen Farrell
- Re: [Add] What to do in this potential working gr… Alec Muffett
- Re: [Add] What to do in this potential working gr… David Conrad
- [Add] data integrity and DNSSEC or DoH/DoT Jim Reid
- Re: [Add] What to do in this potential working gr… Rob Sayre
- Re: [Add] data integrity and DNSSEC or DoH/DoT Stephen Farrell
- Re: [Add] data integrity and DNSSEC or DoH/DoT David Conrad
- Re: [Add] data integrity and DNSSEC or DoH/DoT Rob Sayre
- Re: [Add] data integrity and DNSSEC or DoH/DoT Stephen Farrell
- Re: [Add] Unstated assumptions in What to do in t… John Levine
- Re: [Add] data integrity and DNSSEC or DoH/DoT Brian Dickson
- Re: [Add] What to do in this potential working gr… Patrik Fältström
- Re: [Add] What to do in this potential working gr… Patrik Fältström
- Re: [Add] What to do in this potential working gr… Rob Sayre
- Re: [Add] What to do in this potential working gr… Eric Rescorla
- Re: [Add] What to do in this potential working gr… Martin Thomson
- Re: [Add] data integrity and DNSSEC or DoH/DoT Eric Rescorla
- Re: [Add] What to do in this potential working gr… Eric Rescorla
- Re: [Add] What to do in this potential working gr… Jari Arkko
- Re: [Add] What to do in this potential working gr… Daniel Stenberg
- Re: [Add] What to do in this potential working gr… Jari Arkko
- Re: [Add] data integrity and DNSSEC or DoH/DoT Stephen Farrell
- Re: [Add] What to do in this potential working gr… Ray Bellis
- Re: [Add] What to do in this potential working gr… Martin J. Dürst
- Re: [Add] What to do in this potential working gr… Stephen Farrell
- Re: [Add] What to do in this potential working gr… Vittorio Bertola
- Re: [Add] What to do in this potential working gr… Eric Rescorla
- Re: [Add] What to do in this potential working gr… Ralf Weber
- Re: [Add] data integrity and DNSSEC or DoH/DoT Ralf Weber
- Re: [Add] data integrity and DNSSEC or DoH/DoT Willem Toorop
- Re: [Add] data integrity and DNSSEC or DoH/DoT Jim Reid
- Re: [Add] What to do in this potential working gr… Rubens Kuhl
- Re: [Add] data integrity and DNSSEC or DoH/DoT Paul Wouters
- Re: [Add] What to do in this potential working gr… Paul Wouters
- Re: [Add] data integrity and DNSSEC or DoH/DoT Livingood, Jason
- Re: [Add] What to do in this potential working gr… Livingood, Jason
- Re: [Add] What to do in this potential working gr… Livingood, Jason
- Re: [Add] What to do in this potential working gr… Livingood, Jason
- Re: [Add] What to do in this potential working gr… Adam Roach
- Re: [Add] What to do in this potential working gr… Eric Rescorla
- Re: [Add] data integrity and DNSSEC or DoH/DoT Eric Rescorla
- Re: [Add] data integrity and DNSSEC or DoH/DoT Rob Sayre
- Re: [Add] data integrity and DNSSEC or DoH/DoT Jim Reid
- Re: [Add] What to do in this potential working gr… Vittorio Bertola
- Re: [Add] data integrity and DNSSEC or DoH/DoT Eric Rescorla
- Re: [Add] data integrity and DNSSEC or DoH/DoT Brian Dickson
- Re: [Add] data integrity and DNSSEC or DoH/DoT Jim Reid
- Re: [Add] data integrity and DNSSEC or DoH/DoT Eric Rescorla
- Re: [Add] data integrity and DNSSEC or DoH/DoT Neil Cook
- Re: [Add] data integrity and DNSSEC or DoH/DoT Neil Cook
- Re: [Add] data integrity and DNSSEC or DoH/DoT Neil Cook
- Re: [Add] data integrity and DNSSEC or DoH/DoT Paul Wouters
- Re: [Add] data integrity and DNSSEC or DoH/DoT Christian Huitema
- Re: [Add] data integrity and DNSSEC or DoH/DoT Christian Huitema
- Re: [Add] data integrity and DNSSEC or DoH/DoT Brian Dickson
- Re: [Add] data integrity and DNSSEC or DoH/DoT Andrew Campling
- Re: [Add] data integrity and DNSSEC or DoH/DoT Vittorio Bertola
- Re: [Add] data integrity and DNSSEC or DoH/DoT Paul Wouters
- Re: [Add] data integrity and DNSSEC or DoH/DoT Vittorio Bertola
- Re: [Add] data integrity and DNSSEC or DoH/DoT Alec Muffett
- Re: [Add] data integrity and DNSSEC or DoH/DoT Alec Muffett