Re: [dns-privacy] DPRIVE Interim: 10/29
"Eric Vyncke (evyncke)" <evyncke@cisco.com> Tue, 29 October 2019 11:30 UTC
Return-Path: <evyncke@cisco.com>
X-Original-To: dns-privacy@ietfa.amsl.com
Delivered-To: dns-privacy@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id AFE30120154 for <dns-privacy@ietfa.amsl.com>; Tue, 29 Oct 2019 04:30:21 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -14.5
X-Spam-Level:
X-Spam-Status: No, score=-14.5 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_HI=-5, SPF_PASS=-0.001, URIBL_BLOCKED=0.001, USER_IN_DEF_DKIM_WL=-7.5] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=cisco.com header.b=O8lki8K9; dkim=pass (1024-bit key) header.d=cisco.onmicrosoft.com header.b=Lx0nc1wD
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 aEDPG2BcGCgq for <dns-privacy@ietfa.amsl.com>; Tue, 29 Oct 2019 04:30:20 -0700 (PDT)
Received: from rcdn-iport-5.cisco.com (rcdn-iport-5.cisco.com [173.37.86.76]) (using TLSv1.2 with cipher DHE-RSA-SEED-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 2266B120041 for <dns-privacy@ietf.org>; Tue, 29 Oct 2019 04:30:20 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=2858; q=dns/txt; s=iport; t=1572348619; x=1573558219; h=from:to:subject:date:message-id:references:in-reply-to: content-id:content-transfer-encoding:mime-version; bh=G2uddfXIjz5APL3DZfFs/06eogWOLXwSAzBFy8T+N9A=; b=O8lki8K9BBRJXsdyt3SoIUB49sjQmQyzUZ3qLgx0pdOoGl7v+HzgUxGL g7XxNTaCc1u9yHqvsffv9COA4r95uxr+EMAWOCe5926mTYSFszZyg3li2 entultDioeDuOZVZRf6/yyY5qKHE6eaNW/RMJw8m9x0LJCECChj2IGStv E=;
X-IronPort-AV: E=Sophos;i="5.68,243,1569283200"; d="scan'208";a="432141228"
Received: from rcdn-core-5.cisco.com ([173.37.93.156]) by rcdn-iport-5.cisco.com with ESMTP/TLS/DHE-RSA-SEED-SHA; 29 Oct 2019 11:29:53 +0000
Received: from XCH-ALN-007.cisco.com (xch-aln-007.cisco.com [173.36.7.17]) by rcdn-core-5.cisco.com (8.15.2/8.15.2) with ESMTPS id x9TBTsZv022664 (version=TLSv1.2 cipher=AES256-SHA bits=256 verify=FAIL); Tue, 29 Oct 2019 11:29:54 GMT
Received: from xhs-rcd-003.cisco.com (173.37.227.248) by XCH-ALN-007.cisco.com (173.36.7.17) with Microsoft SMTP Server (TLS) id 15.0.1473.3; Tue, 29 Oct 2019 06:29:53 -0500
Received: from xhs-rcd-001.cisco.com (173.37.227.246) by xhs-rcd-003.cisco.com (173.37.227.248) with Microsoft SMTP Server (TLS) id 15.0.1473.3; Tue, 29 Oct 2019 06:29:53 -0500
Received: from NAM01-SN1-obe.outbound.protection.outlook.com (72.163.14.9) by xhs-rcd-001.cisco.com (173.37.227.246) with Microsoft SMTP Server (TLS) id 15.0.1473.3 via Frontend Transport; Tue, 29 Oct 2019 06:29:52 -0500
ARC-Seal: i=1; a=rsa-sha256; s=arcselector9901; d=microsoft.com; cv=none; b=iSob8ggaKbyZNcjOxQxtLEkS8E72w6f5w2XQSnPKQ7dgd2M5SiaWCvM2TmlJLB/Pgoe0l2s6in0sffw7xTZ95PkF5VpoSW36AOKp9e3WHSn8QSlCBKsa8+5/PVzm0p4Ru0z/OPwite+D+C0K5tA4vMseDHMoPV2o636X3J5NiY2MhWMwGpRihsejGWf8g8Ewn6h5oHiFw8tKua3g4kDPV+bCAFqNCFhv6LQXrhLprPimkHMJlrreNCkqN1odzbkjfEz6UNLdYCn0g6RBsw8cOg/WOu79yWy+72eNzAcmggCZklAeFf10zP9yFmXqVFs0KpicReECPD2bV+RIkBj9TQ==
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=G2uddfXIjz5APL3DZfFs/06eogWOLXwSAzBFy8T+N9A=; b=T5T/5W8tP7VC8C7Om32k9Q552lrJVMpj1R6VU++sDvh2ev7/wPTn/i2YladRWV+VRSe9yy3fuLuuHvmfLFpylYmJ2jZuVgDDFWHu5p1n2n9KzoqSRkjGSsjfWZFVgWEid2ZXmuioH46tL2m8IySZQDoxCt2/tRsjljnlZIhG8Brul/9RI7fpd2O6f3K+n05I3M/ZaoSoPEyWrk+HSXsbL9g62sY7viF+9v8YDQSx123lVgygqMPlnpPk1ph/Ieson+ngnMpAh4kUK1GQBqCCz9TkiCN5KIbVhl43kEYjze5pJs0wPk21IVER3rDXYwjfHEgApp7vyJqLxNlguM2KzQ==
ARC-Authentication-Results: i=1; mx.microsoft.com 1; spf=pass smtp.mailfrom=cisco.com; dmarc=pass action=none header.from=cisco.com; dkim=pass header.d=cisco.com; arc=none
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=cisco.onmicrosoft.com; s=selector2-cisco-onmicrosoft-com; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-SenderADCheck; bh=G2uddfXIjz5APL3DZfFs/06eogWOLXwSAzBFy8T+N9A=; b=Lx0nc1wD80Rt6jr5m5wdJzcru7EXwcKhaDrK1B+dxvUARyN4pCk8Y1x7Q8t3svfHBYp+2clYB7pUmzh6GCxQs5i486tsmp7f3rhmEilmKMcBNXD+zWpTyu0mvua8/gGIUNXgIVQ4LIyIaCLyOOrflGIG786/I3q+T/e6Bsz0NSg=
Received: from DM5PR11MB1753.namprd11.prod.outlook.com (10.175.88.141) by DM5PR11MB2043.namprd11.prod.outlook.com (10.168.105.21) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.2387.22; Tue, 29 Oct 2019 11:29:52 +0000
Received: from DM5PR11MB1753.namprd11.prod.outlook.com ([fe80::c1f1:d33a:2203:5a39]) by DM5PR11MB1753.namprd11.prod.outlook.com ([fe80::c1f1:d33a:2203:5a39%7]) with mapi id 15.20.2387.025; Tue, 29 Oct 2019 11:29:52 +0000
From: "Eric Vyncke (evyncke)" <evyncke@cisco.com>
To: Brian Haberman <brian@innovationslab.net>, "dns-privacy@ietf.org" <dns-privacy@ietf.org>
Thread-Topic: [dns-privacy] DPRIVE Interim: 10/29
Thread-Index: AQHVc6/453gCcRDtNkab1QRdaZ45d6driACAgATypACAAUcagA==
Date: Tue, 29 Oct 2019 11:29:52 +0000
Message-ID: <B2902554-6FBF-4C82-96FF-D90A1FDE70AF@cisco.com>
References: <943e3973-f6a7-9f6e-a66a-33aff835bd5e@innovationslab.net> <503df6fb-b653-476f-055f-15c1a668ba36@innovationslab.net> <88d7b819-5ff2-d696-d064-247f88d31c6f@innovationslab.net>
In-Reply-To: <88d7b819-5ff2-d696-d064-247f88d31c6f@innovationslab.net>
Accept-Language: fr-BE, en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
user-agent: Microsoft-MacOutlook/10.1e.0.191013
authentication-results: spf=none (sender IP is ) smtp.mailfrom=evyncke@cisco.com;
x-originating-ip: [2001:420:c0c1:36:643a:1945:22f7:9c4d]
x-ms-publictraffictype: Email
x-ms-office365-filtering-correlation-id: 52099c2d-ff67-46bc-a796-08d75c6350cd
x-ms-traffictypediagnostic: DM5PR11MB2043:
x-ms-exchange-purlcount: 2
x-microsoft-antispam-prvs: <DM5PR11MB2043F480E85EB840F6895632A9610@DM5PR11MB2043.namprd11.prod.outlook.com>
x-ms-oob-tlc-oobclassifiers: OLM:9508;
x-forefront-prvs: 0205EDCD76
x-forefront-antispam-report: SFV:NSPM; SFS:(10009020)(4636009)(376002)(346002)(366004)(39860400002)(396003)(136003)(189003)(199004)(966005)(99286004)(256004)(6116002)(305945005)(478600001)(36756003)(53546011)(6436002)(6506007)(2906002)(110136005)(71200400001)(7736002)(229853002)(71190400001)(102836004)(6486002)(76176011)(316002)(5660300002)(66574012)(6512007)(186003)(76116006)(91956017)(14454004)(33656002)(6306002)(86362001)(58126008)(2501003)(66446008)(64756008)(25786009)(11346002)(2616005)(476003)(486006)(8676002)(46003)(446003)(81156014)(66556008)(66946007)(66476007)(8936002)(6246003)(81166006); DIR:OUT; SFP:1101; SCL:1; SRVR:DM5PR11MB2043; H:DM5PR11MB1753.namprd11.prod.outlook.com; FPR:; SPF:None; LANG:en; PTR:InfoNoRecords; MX:1; A:1;
received-spf: None (protection.outlook.com: cisco.com does not designate permitted sender hosts)
x-ms-exchange-senderadcheck: 1
x-microsoft-antispam: BCL:0;
x-microsoft-antispam-message-info: tNXVVQhMn7sGIUVfXgHcgLoABGPTWZak/rJrTujVDNyML/Gi1Uc4KG12GJ1kDxrrrvlQpNxRKPT8dUCwb5lt0EUtlroiE+OSZP7m3+CUX5ByYPEG5/L38L/Ttp4DOQv3vcJHiiqaf9kA+ZuRPH+ueV82DQWmYy3/Ap4EO/T0wN3Y0ZWRKKrOCT0fEm+dViKU4dupl7jYCfy6Ub5A8/PzGnUV6OlP2LoRwyaf4pyPfwD2WsHmbqi6/fqILYVVDxcTj75eNKW7Nlv7iwS+YcB65BmIDZmqxEA0EdW38zqlIwST2VTxJtQCR3xwjUE+YwmS+MgP8r2Bo2aCG7Ezz9wlNYLuznAMMP9nyfmzoL3XMgCXePv5eFkbwMZq3b9D4aqi1DbxlxJoVe/xKV/MynQ4/BiPLMiVte7QG4ECR5geyiwpYGLxlbGhXQy93aW4bX/vHToeQkQmTvxw7VDu3iYTLjbLO91nOpQ03rrj2bzJP9E=
x-ms-exchange-transport-forked: True
Content-Type: text/plain; charset="utf-8"
Content-ID: <63796443A365804F80F3A82D25174051@namprd11.prod.outlook.com>
Content-Transfer-Encoding: base64
MIME-Version: 1.0
X-MS-Exchange-CrossTenant-Network-Message-Id: 52099c2d-ff67-46bc-a796-08d75c6350cd
X-MS-Exchange-CrossTenant-originalarrivaltime: 29 Oct 2019 11:29:52.2927 (UTC)
X-MS-Exchange-CrossTenant-fromentityheader: Hosted
X-MS-Exchange-CrossTenant-id: 5ae1af62-9505-4097-a69a-c1553ef7840e
X-MS-Exchange-CrossTenant-mailboxtype: HOSTED
X-MS-Exchange-CrossTenant-userprincipalname: p3y0VH4oo+fMEAwfPS62NyyM2sO4COrDMmRxcRfteH9v8IvNZqUh/yIMCAFSKpw7udrlbiJijFEMA1rqRjghTg==
X-MS-Exchange-Transport-CrossTenantHeadersStamped: DM5PR11MB2043
X-OriginatorOrg: cisco.com
X-Outbound-SMTP-Client: 173.36.7.17, xch-aln-007.cisco.com
X-Outbound-Node: rcdn-core-5.cisco.com
Archived-At: <https://mailarchive.ietf.org/arch/msg/dns-privacy/3jIXdMzvRc1iSUrv1eMD1TYCsjQ>
Subject: Re: [dns-privacy] DPRIVE Interim: 10/29
X-BeenThere: dns-privacy@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: <dns-privacy.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dns-privacy>, <mailto:dns-privacy-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/dns-privacy/>
List-Post: <mailto:dns-privacy@ietf.org>
List-Help: <mailto:dns-privacy-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dns-privacy>, <mailto:dns-privacy-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 29 Oct 2019 11:30:22 -0000
Another experience return (being on a couple of those 'broken' calls): - audio can become one-way: participants can hear but not talk (cannot remove the mute button in my case !) => use chat / jabber to pass your message could be a work-around - if Internet audio does not work, then use your phone to call webex (but $ in some cases) Let's hope that we will not experiment problems later today -éric On 28/10/2019, 17:59, "dns-privacy on behalf of Brian Haberman" <dns-privacy-bounces@ietf.org on behalf of brian@innovationslab.net> wrote: All, The Secretariat has been investigating intermittent audio issues during recent meetings and they are working with the WebEx team to find the source of the problem. If you encounter audio issues during the DPRIVE interim on 10/29, please report the problem *during* the meeting. To do that within WebEx, you can: 1. Select 'Help'. 2. Select the 'Send Problem Report', under Help’s drop-down options. 3. Click 'Send a Problem Report' and wait for the process to complete and generate the report. 4. Please provide the network logs by following: https://help.webex.com/en-us/WBX000026383/WBX-Tracer Regards, Brian On 10/25/19 9:25 AM, Brian Haberman wrote: > https://datatracker.ietf.org/doc/agenda-interim-2019-dprive-01-dprive-01/ > > On 9/25/19 10:45 AM, Brian Haberman wrote: >> All, >> We are going to hold a DPRIVE virtual interim meeting on Oct. 29th >> at 4:00pm CET / 11:00am EDT / 8:00am PDT. The three agenda items are: >> >> - Review updates to the BCP based on WGLC comments, >> - Review updates to 7626bis based on WGLC comments, >> - Discuss recursive-to-authoritative requirements (-00 draft forthcoming). >> >> The conference call details will be forthcoming. >> >> If there are other topics of pressing nature, please let the chairs know. >> >> Regards, >> Brian & Tim >> >
- [dns-privacy] DPRIVE Interim: 10/29 Brian Haberman
- Re: [dns-privacy] DPRIVE Interim: 10/29 Allison Mankin
- Re: [dns-privacy] DPRIVE Interim: 10/29 tjw ietf
- Re: [dns-privacy] DPRIVE Interim: 10/29 Brian Haberman
- Re: [dns-privacy] [Ext] Re: DPRIVE Interim: 10/29 Paul Hoffman
- Re: [dns-privacy] [Ext] Re: DPRIVE Interim: 10/29 Brian Haberman
- Re: [dns-privacy] [Ext] Re: DPRIVE Interim: 10/29 Livingood, Jason
- Re: [dns-privacy] [Ext] Re: DPRIVE Interim: 10/29 Alexander Mayrhofer
- Re: [dns-privacy] DPRIVE Interim: 10/29 Brian Haberman
- Re: [dns-privacy] [Ext] Re: DPRIVE Interim: 10/29 Brian Dickson
- Re: [dns-privacy] [Ext] Re: DPRIVE Interim: 10/29 Rob Sayre
- Re: [dns-privacy] DPRIVE Interim: 10/29 Eric Vyncke (evyncke)
- Re: [dns-privacy] [Ext] Re: DPRIVE Interim: 10/29 Paul Hoffman
- [dns-privacy] ADoT requirements for authenticatio… Paul Hoffman
- Re: [dns-privacy] ADoT requirements for authentic… Ted Hardie
- Re: [dns-privacy] [Ext] Re: ADoT requirements for… Paul Hoffman
- Re: [dns-privacy] [Ext] Re: ADoT requirements for… Ted Hardie
- Re: [dns-privacy] [Ext] Re: ADoT requirements for… Ben Schwartz
- Re: [dns-privacy] [Ext] Re: ADoT requirements for… Brian Dickson
- Re: [dns-privacy] [Ext] Re: ADoT requirements for… Paul Wouters
- Re: [dns-privacy] [Ext] Re: DPRIVE Interim: 10/29 Brian Dickson
- Re: [dns-privacy] [Ext] Re: ADoT requirements for… Ted Hardie
- Re: [dns-privacy] [Ext] Re: ADoT requirements for… Brian Dickson
- Re: [dns-privacy] [Ext] Re: ADoT requirements for… Ben Schwartz
- Re: [dns-privacy] [Ext] Re: ADoT requirements for… Ted Hardie
- Re: [dns-privacy] [Ext] Re: ADoT requirements for… Eric Rescorla
- Re: [dns-privacy] [Ext] Re: ADoT requirements for… Ben Schwartz
- Re: [dns-privacy] [Ext] Re: ADoT requirements for… Eric Rescorla
- Re: [dns-privacy] [Ext] Re: ADoT requirements for… Brian Dickson
- Re: [dns-privacy] [Ext] Re: ADoT requirements for… Ben Schwartz
- Re: [dns-privacy] [Ext] Re: ADoT requirements for… Eric Rescorla
- Re: [dns-privacy] [Ext] Re: ADoT requirements for… Christian Huitema
- Re: [dns-privacy] [Ext] Re: ADoT requirements for… John Levine
- Re: [dns-privacy] [Ext] Re: ADoT requirements for… Jim Reid
- [dns-privacy] DoT at the DNS root Jim Reid
- Re: [dns-privacy] DoT at the DNS root Jim Reid
- Re: [dns-privacy] [Ext] Re: ADoT requirements for… Watson Ladd
- Re: [dns-privacy] [Ext] Re: DPRIVE Interim: 10/29 Alexander Mayrhofer
- Re: [dns-privacy] [Ext] Re: ADoT requirements for… Ralf Weber
- Re: [dns-privacy] [Ext] Re: ADoT requirements for… Paul Wouters
- Re: [dns-privacy] ADoT requirements for authentic… Tony Finch
- Re: [dns-privacy] [EXTERNAL] Re: [Ext] Re: DPRIVE… Livingood, Jason
- Re: [dns-privacy] [Ext] Re: DPRIVE Interim: 10/29 Livingood, Jason
- Re: [dns-privacy] [Ext] Re: ADoT requirements for… Livingood, Jason
- Re: [dns-privacy] [Ext] Re: ADoT requirements for… John Levine
- Re: [dns-privacy] [Ext] Re: ADoT requirements for… Jim Reid
- [dns-privacy] ADoT deployment at the root Jim Reid
- Re: [dns-privacy] [Ext] Re: ADoT requirements for… Jim Reid
- Re: [dns-privacy] [Ext] Re: ADoT requirements for… Brian Dickson
- Re: [dns-privacy] ADoT deployment at the root Ted Hardie
- Re: [dns-privacy] ADoT deployment at the root Warren Kumari
- Re: [dns-privacy] [Ext] Re: ADoT requirements for… John Levine
- Re: [dns-privacy] ADoT deployment at the root John Levine
- Re: [dns-privacy] [Ext] Re: ADoT requirements for… John Levine
- Re: [dns-privacy] [Ext] Re: ADoT requirements for… Ben Schwartz
- Re: [dns-privacy] [Ext] Re: ADoT requirements for… Stephen Farrell
- Re: [dns-privacy] [Ext] Re: ADoT requirements for… Brian Dickson
- Re: [dns-privacy] [Ext] Re: ADoT requirements for… John R Levine
- Re: [dns-privacy] [Ext] Re: ADoT requirements for… Eric Rescorla
- Re: [dns-privacy] [Ext] Re: ADoT requirements for… Vladimír Čunát
- Re: [dns-privacy] [Ext] Re: ADoT requirements for… Vladimír Čunát
- Re: [dns-privacy] [Ext] Re: ADoT requirements for… Hollenbeck, Scott
- Re: [dns-privacy] [Ext] Re: ADoT requirements for… Eric Rescorla
- Re: [dns-privacy] [Ext] Re: ADoT requirements for… Vladimír Čunát
- Re: [dns-privacy] [Ext] Re: ADoT requirements for… Brian Dickson
- Re: [dns-privacy] [Ext] Re: ADoT requirements for… Eric Rescorla
- Re: [dns-privacy] [Ext] Re: ADoT requirements for… Eric Rescorla
- Re: [dns-privacy] [Ext] Re: ADoT requirements for… Brian Dickson
- Re: [dns-privacy] [Ext] Re: ADoT requirements for… Brian Dickson
- Re: [dns-privacy] [Ext] Re: ADoT requirements for… Vladimír Čunát
- Re: [dns-privacy] [Ext] Re: ADoT requirements for… John R Levine
- Re: [dns-privacy] [Ext] Re: ADoT requirements for… Ted Hardie
- Re: [dns-privacy] [Ext] Re: ADoT requirements for… Brian Dickson
- Re: [dns-privacy] [Ext] Re: ADoT requirements for… John R Levine
- Re: [dns-privacy] DPRIVE Interim: 10/29 Brian Haberman