Re: [Add] meeting hum: should the IETF take up this work?
Tommy Jensen <Jensen.Thomas@microsoft.com> Wed, 31 July 2019 17:41 UTC
Return-Path: <Jensen.Thomas@microsoft.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 DFB3512064A for <add@ietfa.amsl.com>; Wed, 31 Jul 2019 10:41:27 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.001
X-Spam-Level:
X-Spam-Status: No, score=-2.001 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIMWL_WL_HIGH=-0.001, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=microsoft.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 PXYs2des6iBQ for <add@ietfa.amsl.com>; Wed, 31 Jul 2019 10:41:25 -0700 (PDT)
Received: from NAM04-SN1-obe.outbound.protection.outlook.com (mail-eopbgr700131.outbound.protection.outlook.com [40.107.70.131]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 31915120637 for <add@ietf.org>; Wed, 31 Jul 2019 10:41:25 -0700 (PDT)
ARC-Seal: i=1; a=rsa-sha256; s=arcselector9901; d=microsoft.com; cv=none; b=hYgHQ2opnypU9o/+vh3ownLS8aoOHtSGoHmNgdCQItyGWUzFPYWHggoCQf1BWi/+3o40fIKuCOR59zSaDGUAT5bPWv+2P3Mz9LaF/oTc/YouNKLP1XTGSaK+IHAfJMTS3ZXXqecsovIkc63HbpmKxkCiAhVMXmAv2S5n7LdCWC+8HMD2SuzCusuW6xIthDTRnubb/aXMzIANlOw2bbGj/tQi6nhtxXueVsbfBVy0RQpIYf+I4NdlQ2r6+Hwnu9J6AM/ocqLDuAUJwetp+sWgjQrkrqUveXo6pCUTQvZG/nkw8mfb0FceKY4iBOe9edq39QinReYVtuPLlxyAVIPuBQ==
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=m0vBkZO0tzsXCdUHXnuuo4IK+g9M/RGHdrfonFn6A9A=; b=h6o53I9pB0Y6+6bD43EnmtfDorEXeP+wpfBt2IgQFRaqWyCaKWJQkwR/OZWbYQAMrFavrCzVSqi0K6wji8Bfpgemih13VcYfbm97tpUZSoiEbx1kz00lM0BXQEWz0GckQp2kahMittvYNlQdkVvCBs4VKKm+yYN6Bmw/qUpBu5vw1/AIUgoXyyxWLmJzAe07pogVCcbhDn79uA9VW19KuaJ7BtsHRf7QI9siCliezMloIYEsYEh1amRT9K4Bls4/C6P+8Hhh1maPB830eZkMvTlt5Tdcf0GcCPSZLVREzhRdYZJoXGVoRdK95l5p/5o25fFV9yTCLkl/tY1lha7r4w==
ARC-Authentication-Results: i=1; mx.microsoft.com 1; spf=pass smtp.mailfrom=microsoft.com; dmarc=pass action=none header.from=microsoft.com; dkim=pass header.d=microsoft.com; arc=none
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=microsoft.com; s=selector1; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-SenderADCheck; bh=m0vBkZO0tzsXCdUHXnuuo4IK+g9M/RGHdrfonFn6A9A=; b=kiQOLy8lXDon+7rH5DowP3JNlpcY3Thzk49gDdJ63E1j8WqEFOsKHCUtYE08OBm3A5p1jv17usR3IVykfRiMR3l+NLClx5WLWNlTBtoapOxDT9n9C7mwoWPN+9YrxJMltAthrw+mLjamF69DV6O8+3ZvsjyazUaazg6PckHziZQ=
Received: from MN2PR21MB1213.namprd21.prod.outlook.com (20.179.20.141) by MN2PR21MB1215.namprd21.prod.outlook.com (20.179.20.143) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.2157.2; Wed, 31 Jul 2019 17:41:23 +0000
Received: from MN2PR21MB1213.namprd21.prod.outlook.com ([fe80::24eb:3b4c:428b:8fde]) by MN2PR21MB1213.namprd21.prod.outlook.com ([fe80::24eb:3b4c:428b:8fde%9]) with mapi id 15.20.2157.001; Wed, 31 Jul 2019 17:41:23 +0000
From: Tommy Jensen <Jensen.Thomas@microsoft.com>
To: "Livingood, Jason" <Jason_Livingood@comcast.com>, "add@ietf.org" <add@ietf.org>
Thread-Topic: [Add] meeting hum: should the IETF take up this work?
Thread-Index: AQHVR8V1WrgBv7BM8EegWWPMEALeFKbk++tU
Date: Wed, 31 Jul 2019 17:41:23 +0000
Message-ID: <MN2PR21MB1213BD37BAC684B31414A47DFADF0@MN2PR21MB1213.namprd21.prod.outlook.com>
References: <745AC544-A6E0-45E4-A571-4EF2A47F77CA@cable.comcast.com>
In-Reply-To: <745AC544-A6E0-45E4-A571-4EF2A47F77CA@cable.comcast.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
authentication-results: spf=none (sender IP is ) smtp.mailfrom=Jensen.Thomas@microsoft.com;
x-originating-ip: [2001:4898:80e8:b:e0c1:731b:6166:2f2d]
x-ms-publictraffictype: Email
x-ms-office365-filtering-correlation-id: 97ed34d9-4154-4903-ad9c-08d715de4e48
x-ms-office365-filtering-ht: Tenant
x-microsoft-antispam: BCL:0; PCL:0; RULEID:(2390118)(7020095)(4652040)(8989299)(5600148)(711020)(4605104)(1401327)(4618075)(4534185)(4627221)(201703031133081)(201702281549075)(8990200)(2017052603328)(7193020); SRVR:MN2PR21MB1215;
x-ms-traffictypediagnostic: MN2PR21MB1215:
x-ms-exchange-purlcount: 1
x-microsoft-antispam-prvs: <MN2PR21MB121538C93AF110C5BB724CE8FADF0@MN2PR21MB1215.namprd21.prod.outlook.com>
x-ms-oob-tlc-oobclassifiers: OLM:8882;
x-forefront-prvs: 011579F31F
x-forefront-antispam-report: SFV:NSPM; SFS:(10019020)(4636009)(136003)(366004)(376002)(396003)(39860400002)(346002)(189003)(199004)(110136005)(102836004)(6116002)(81156014)(81166006)(8676002)(8936002)(14454004)(52536014)(25786009)(7696005)(33656002)(99286004)(316002)(478600001)(9686003)(53546011)(966005)(68736007)(54896002)(2906002)(22452003)(7736002)(53936002)(186003)(6506007)(236005)(10090500001)(55016002)(6436002)(76176011)(105004)(91956017)(2501003)(5660300002)(86362001)(6246003)(6306002)(76116006)(10290500003)(8990500004)(66946007)(64756008)(66476007)(66446008)(66556008)(66574012)(74316002)(256004)(46003)(476003)(446003)(11346002)(606006)(486006)(19627405001)(229853002)(71190400001)(71200400001); DIR:OUT; SFP:1102; SCL:1; SRVR:MN2PR21MB1215; H:MN2PR21MB1213.namprd21.prod.outlook.com; FPR:; SPF:None; LANG:en; PTR:InfoNoRecords; MX:1; A:1;
received-spf: None (protection.outlook.com: microsoft.com does not designate permitted sender hosts)
x-ms-exchange-senderadcheck: 1
x-microsoft-antispam-message-info: r4iBedOvMyUXPyWv61ZBSkcInheo1q9GS9C/H9bVJZrog/Dh7xGOUA+zW1nHECR34TmK2hvlto0EpI8dJTBrKLFlp4oK/N7hR/ZtC7cgfuPPZdBIwDOGI+q/KHJVjBKKzp5s3tMc+zZGmqHp7IGSo+5NmchabfQiqQKdofY+g8oRotZM3Q8sOHYSn3rgWTnXs3rzMEImYi1oR0dAd+oAjXX1f3/rfsn0zox2HG6DcmXNGFT3inr5IMTvD9v9wBzZVwP153M8pfPYxCsfleCcg5M37GtTSkrDkWn4KVM2HVducI+ynRIn0tnRJ9eaYCOGauuDZn41rcCTVDGHYgl8Ay5uvgebJ9tQa/Dcu8YAVAYABAyQU3a46MniOk+zXsgMZ1+tGC/bzm7m9hol+s/GK8L/sHs6nRl/sp6UwuwDaCw=
x-ms-exchange-transport-forked: True
Content-Type: multipart/alternative; boundary="_000_MN2PR21MB1213BD37BAC684B31414A47DFADF0MN2PR21MB1213namp_"
MIME-Version: 1.0
X-OriginatorOrg: microsoft.com
X-MS-Exchange-CrossTenant-Network-Message-Id: 97ed34d9-4154-4903-ad9c-08d715de4e48
X-MS-Exchange-CrossTenant-originalarrivaltime: 31 Jul 2019 17:41:23.4184 (UTC)
X-MS-Exchange-CrossTenant-fromentityheader: Hosted
X-MS-Exchange-CrossTenant-id: 72f988bf-86f1-41af-91ab-2d7cd011db47
X-MS-Exchange-CrossTenant-mailboxtype: HOSTED
X-MS-Exchange-CrossTenant-userprincipalname: p54ZytJqAhSP+H54ZdtoZqPw7FwK810mq+giLVgcDPvv4ifxTsgyJyIHudjXnAI5WC63DNfJCbEUzsZ+/FO0EQ==
X-MS-Exchange-Transport-CrossTenantHeadersStamped: MN2PR21MB1215
Archived-At: <https://mailarchive.ietf.org/arch/msg/add/exRNVLLMj4yc9RRwLx8wllaApWk>
Subject: Re: [Add] meeting hum: should the IETF take up this work?
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, 31 Jul 2019 17:41:36 -0000
Maybe a good way to empower UXs, app or platform, to inform the user about their different DNS options would be to build user-centric information into a feature discovery protocol for RRs. This would allow RRs committed to user value to advertise the features they want the user to know about. For example, RRs could provide answers to stub questions such as: * Maximum length of time (in seconds) personal data is retained * Maximum length of time (in seconds) anonymized data is retained * URL where RRs privacy or other legal policies can be discovered * Does or does not (boolean) filter or block results from authoritative sources * Might be expected to be true for "clean filter" DNS services * ... This would allow stubs to build UXs that provide red/green checkmarks and recommendations such as "Your current DNS server keeps your data longer than this other server we recommend configuring instead". This would help separate privacy friendly ISPs from the rogue airport/coffee shop Wi-Fi ISPs that couldn't care less at run time. Thanks, Tommy ________________________________ From: Add <add-bounces@ietf.org> on behalf of Livingood, Jason <Jason_Livingood@comcast.com> Sent: Wednesday, July 31, 2019 10:29 AM To: add@ietf.org <add@ietf.org> Subject: Re: [Add] meeting hum: should the IETF take up this work? From: Eric Rescorla <ekr@rtfm.com> > This seems to be assuming a number of facts about how ISPs behave that are not in evidence. ISPs, like browsers and search portals, do not all have the same business models, practices, and cultures. Just as the Firefox browser is very different from Google Chrome, then so too is ISP-1 from ISP-2. -- Add mailing list Add@ietf.org https://nam06.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.ietf.org%2Fmailman%2Flistinfo%2Fadd&data=02%7C01%7CJensen.Thomas%40microsoft.com%7C913ab902f70043663d5608d715dca716%7C72f988bf86f141af91ab2d7cd011db47%7C1%7C0%7C637001909757322923&sdata=QASynB6%2BqiWTpU%2FE9WipAaBLRxnB3Lxmvo%2FTAPFCg2U%3D&reserved=0
- [Add] meeting hum: should the IETF take up this w… Rob Sayre
- Re: [Add] meeting hum: should the IETF take up th… Jim Reid
- Re: [Add] meeting hum: should the IETF take up th… Rob Sayre
- Re: [Add] meeting hum: should the IETF take up th… Michael Sinatra
- Re: [Add] meeting hum: should the IETF take up th… Tommy Jensen
- Re: [Add] meeting hum: should the IETF take up th… Jim Reid
- Re: [Add] meeting hum: should the IETF take up th… STARK, BARBARA H
- Re: [Add] meeting hum: should the IETF take up th… Rob Sayre
- Re: [Add] meeting hum: should the IETF take up th… Michael Richardson
- Re: [Add] meeting hum: should the IETF take up th… Reed, Jon
- Re: [Add] meeting hum: should the IETF take up th… Rob Sayre
- [Add] fixing coffee shop brokenness with DoH Jim Reid
- Re: [Add] meeting hum: should the IETF take up th… Bret Jordan
- Re: [Add] fixing coffee shop brokenness with DoH Rob Sayre
- Re: [Add] meeting hum: should the IETF take up th… Rob Sayre
- Re: [Add] fixing coffee shop brokenness with DoH Bret Jordan
- Re: [Add] fixing coffee shop brokenness with DoH Rob Sayre
- Re: [Add] fixing coffee shop brokenness with DoH Tommy Jensen
- Re: [Add] fixing coffee shop brokenness with DoH Rob Sayre
- Re: [Add] fixing coffee shop brokenness with DoH Tommy Jensen
- Re: [Add] fixing coffee shop brokenness with DoH Rob Sayre
- Re: [Add] fixing coffee shop brokenness with DoH Tommy Jensen
- Re: [Add] fixing coffee shop brokenness with DoH Bret Jordan
- Re: [Add] fixing coffee shop brokenness with DoH Rob Sayre
- Re: [Add] fixing coffee shop brokenness with DoH Alec Muffett
- Re: [Add] fixing coffee shop brokenness with DoH sthaug
- Re: [Add] fixing coffee shop brokenness with DoH Rob Sayre
- Re: [Add] meeting hum: should the IETF take up th… Brett Carr
- Re: [Add] fixing coffee shop brokenness with DoH Joseph Lorenzo Hall
- Re: [Add] fixing coffee shop brokenness with DoH Lars Eggert
- Re: [Add] fixing coffee shop brokenness with DoH Eric Rescorla
- Re: [Add] fixing coffee shop brokenness with DoH Ted Lemon
- Re: [Add] fixing coffee shop brokenness with DoH Diego R. Lopez
- Re: [Add] fixing coffee shop brokenness with DoH Bret Jordan
- Re: [Add] fixing coffee shop brokenness with DoH Joseph Lorenzo Hall
- Re: [Add] fixing coffee shop brokenness with DoH Bret Jordan
- Re: [Add] fixing coffee shop brokenness with DoH Joseph Lorenzo Hall
- Re: [Add] fixing coffee shop brokenness with DoH chris.box
- Re: [Add] fixing coffee shop brokenness with DoH Vittorio Bertola
- Re: [Add] fixing coffee shop brokenness with DoH Eric Rescorla
- Re: [Add] meeting hum: should the IETF take up th… Vittorio Bertola
- Re: [Add] meeting hum: should the IETF take up th… Eric Rescorla
- Re: [Add] fixing coffee shop brokenness with DoH Ted Lemon
- Re: [Add] fixing coffee shop brokenness with DoH Joseph Lorenzo Hall
- Re: [Add] fixing coffee shop brokenness with DoH Ted Lemon
- Re: [Add] fixing coffee shop brokenness with DoH Jim Reid
- Re: [Add] fixing coffee shop brokenness with DoH Diego R. Lopez
- Re: [Add] fixing coffee shop brokenness with DoH Brian Dickson
- Re: [Add] fixing coffee shop brokenness with DoH Eric Rescorla
- Re: [Add] fixing coffee shop brokenness with DoH Ted Lemon
- Re: [Add] fixing coffee shop brokenness with DoH Eric Rescorla
- Re: [Add] fixing coffee shop brokenness with DoH Tony Finch
- [Add] Trust and control on the Internet (was Re: … Vittorio Bertola
- Re: [Add] fixing coffee shop brokenness with DoH Jim Reid
- Re: [Add] Trust and control on the Internet (was … Ted Lemon
- Re: [Add] fixing coffee shop brokenness with DoH Eric Rescorla
- Re: [Add] fixing coffee shop brokenness with DoH Eric Rescorla
- Re: [Add] fixing coffee shop brokenness with DoH Ted Lemon
- Re: [Add] fixing coffee shop brokenness with DoH Eric Rescorla
- Re: [Add] fixing coffee shop brokenness with DoH Ted Lemon
- Re: [Add] fixing coffee shop brokenness with DoH Jim Reid
- Re: [Add] fixing coffee shop brokenness with DoH Jim Reid
- Re: [Add] meeting hum: should the IETF take up th… Stephane Bortzmeyer
- Re: [Add] meeting hum: should the IETF take up th… Stephane Bortzmeyer
- Re: [Add] fixing coffee shop brokenness with DoH Eric Rescorla
- Re: [Add] fixing coffee shop brokenness with DoH Eric Rescorla
- Re: [Add] meeting hum: should the IETF take up th… Stephane Bortzmeyer
- Re: [Add] fixing coffee shop brokenness with DoH Brian Dickson
- Re: [Add] fixing coffee shop brokenness with DoH Ted Lemon
- Re: [Add] Trust and control on the Internet (was … Andrew Campling
- Re: [Add] Trust and control on the Internet (was … Andrew Campling
- Re: [Add] fixing coffee shop brokenness with DoH Brian Dickson
- Re: [Add] fixing coffee shop brokenness with DoH Eric Rescorla
- Re: [Add] fixing coffee shop brokenness with DoH Brian Dickson
- Re: [Add] fixing coffee shop brokenness with DoH Eric Rescorla
- Re: [Add] fixing coffee shop brokenness with DoH Jim Reid
- Re: [Add] fixing coffee shop brokenness with DoH Michael Richardson
- Re: [Add] fixing coffee shop brokenness with DoH Ted Lemon
- Re: [Add] fixing coffee shop brokenness with DoH Eric Rescorla
- Re: [Add] fixing coffee shop brokenness with DoH Eric Rescorla
- Re: [Add] fixing coffee shop brokenness with DoH Ted Lemon
- Re: [Add] fixing coffee shop brokenness with DoH Jim Reid
- Re: [Add] fixing coffee shop brokenness with DoH Michael Richardson
- Re: [Add] fixing coffee shop brokenness with DoH Eric Rescorla
- Re: [Add] fixing coffee shop brokenness with DoH Stephane Bortzmeyer
- Re: [Add] fixing coffee shop brokenness with DoH Stephane Bortzmeyer
- Re: [Add] fixing coffee shop brokenness with DoH Stephane Bortzmeyer
- Re: [Add] fixing coffee shop brokenness with DoH Jim Reid
- Re: [Add] fixing coffee shop brokenness with DoH Rob Sayre
- Re: [Add] fixing coffee shop brokenness with DoH Brian Dickson
- Re: [Add] fixing coffee shop brokenness with DoH Rob Sayre
- Re: [Add] fixing coffee shop brokenness with DoH chris.box
- Re: [Add] fixing coffee shop brokenness with DoH Jim Reid
- Re: [Add] fixing coffee shop brokenness with DoH Rob Sayre
- Re: [Add] fixing coffee shop brokenness with DoH Petr Špaček
- Re: [Add] meeting hum: should the IETF take up th… Neil Cook
- Re: [Add] fixing coffee shop brokenness with DoH Normen Kowalewski
- Re: [Add] fixing coffee shop brokenness with DoH Joe Abley
- Re: [Add] fixing coffee shop brokenness with DoH Normen Kowalewski
- Re: [Add] fixing coffee shop brokenness with DoH Eric Rescorla
- Re: [Add] fixing coffee shop brokenness with DoH Paul Ebersman
- Re: [Add] fixing coffee shop brokenness with DoH Jim Reid
- Re: [Add] fixing coffee shop brokenness with DoH Petr Špaček
- Re: [Add] meeting hum: should the IETF take up th… Adam Roach
- Re: [Add] meeting hum: should the IETF take up th… Neil Cook
- Re: [Add] fixing coffee shop brokenness with DoH Paul Ebersman
- Re: [Add] fixing coffee shop brokenness with DoH Eric Rescorla
- Re: [Add] fixing coffee shop brokenness with DoH Paul Ebersman
- Re: [Add] fixing coffee shop brokenness with DoH Eric Rescorla
- Re: [Add] meeting hum: should the IETF take up th… Vittorio Bertola
- Re: [Add] fixing coffee shop brokenness with DoH Paul Wouters
- Re: [Add] fixing coffee shop brokenness with DoH Michael Richardson
- Re: [Add] fixing coffee shop brokenness with DoH Brian Dickson
- Re: [Add] fixing coffee shop brokenness with DoH Eric Rescorla
- Re: [Add] meeting hum: should the IETF take up th… Andrew Campling
- Re: [Add] fixing coffee shop brokenness with DoH Eric Rescorla
- Re: [Add] meeting hum: should the IETF take up th… Adam Roach
- Re: [Add] meeting hum: should the IETF take up th… Stephen Farrell
- Re: [Add] meeting hum: should the IETF take up th… Adam Roach
- Re: [Add] fixing coffee shop brokenness with DoH Andrew Campling
- Re: [Add] fixing coffee shop brokenness with DoH Eric Rescorla
- Re: [Add] meeting hum: should the IETF take up th… Andrew Campling
- Re: [Add] meeting hum: should the IETF take up th… Vittorio Bertola
- Re: [Add] meeting hum: should the IETF take up th… Michael Richardson
- Re: [Add] meeting hum: should the IETF take up th… Ben Schwartz
- Re: [Add] meeting hum: should the IETF take up th… Rob Sayre
- Re: [Add] meeting hum: should the IETF take up th… Eric Rescorla
- Re: [Add] meeting hum: should the IETF take up th… Michael Richardson
- Re: [Add] meeting hum: should the IETF take up th… Michael Richardson
- Re: [Add] meeting hum: should the IETF take up th… Stephen Farrell
- Re: [Add] meeting hum: should the IETF take up th… Eric Rescorla
- Re: [Add] meeting hum: should the IETF take up th… Rob Sayre
- Re: [Add] meeting hum: should the IETF take up th… Stephen Farrell
- Re: [Add] meeting hum: should the IETF take up th… Rob Sayre
- Re: [Add] meeting hum: should the IETF take up th… Michael Richardson
- Re: [Add] meeting hum: should the IETF take up th… Vittorio Bertola
- Re: [Add] meeting hum: should the IETF take up th… Valentin Gosu
- Re: [Add] meeting hum: should the IETF take up th… Eric Rescorla
- Re: [Add] meeting hum: should the IETF take up th… Livingood, Jason
- Re: [Add] meeting hum: should the IETF take up th… Paul Ebersman
- Re: [Add] meeting hum: should the IETF take up th… Rob Sayre
- Re: [Add] meeting hum: should the IETF take up th… Eric Rescorla
- Re: [Add] meeting hum: should the IETF take up th… Diego R. Lopez
- Re: [Add] meeting hum: should the IETF take up th… Eric Rescorla
- Re: [Add] meeting hum: should the IETF take up th… Eric Orth
- Re: [Add] meeting hum: should the IETF take up th… Diego R. Lopez
- Re: [Add] meeting hum: should the IETF take up th… Thomas Peterson
- Re: [Add] meeting hum: should the IETF take up th… Jim Reid
- Re: [Add] meeting hum: should the IETF take up th… Livingood, Jason
- Re: [Add] meeting hum: should the IETF take up th… Tommy Jensen
- Re: [Add] meeting hum: should the IETF take up th… Ólafur Guðmundsson
- Re: [Add] [EXT] Re: meeting hum: should the IETF … Jacques Latour
- Re: [Add] [EXT] Re: meeting hum: should the IETF … Joe Abley
- Re: [Add] [EXT] Re: meeting hum: should the IETF … Ralf Weber
- [Add] point of deploying DoH in access network (R… 神明達哉
- Re: [Add] point of deploying DoH in access networ… Joe Abley
- Re: [Add] [EXT] Re: meeting hum: should the IETF … Eric Orth
- Re: [Add] [EXT] Re: meeting hum: should the IETF … Christian Huitema
- Re: [Add] [EXT] Re: meeting hum: should the IETF … Mikael Abrahamsson
- Re: [Add] point of deploying DoH in access networ… Tony Finch
- Re: [Add] point of deploying DoH in access networ… Robert Mortimer
- Re: [Add] point of deploying DoH in access networ… Alec Muffett
- Re: [Add] point of deploying DoH in access networ… Ted Lemon
- Re: [Add] point of deploying DoH in access networ… Simon Hicks
- Re: [Add] point of deploying DoH in access networ… Vladimír Čunát