Re: [Ietf108planning] Registration open for IETF 108
tom petch <daedulus@btconnect.com> Thu, 11 June 2020 09:57 UTC
Return-Path: <daedulus@btconnect.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 081EB3A07DE for <ietf@ietfa.amsl.com>; Thu, 11 Jun 2020 02:57:31 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.9
X-Spam-Level:
X-Spam-Status: No, score=-1.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, MSGID_FROM_MTA_HEADER=0.001, RCVD_IN_MSPIKE_H2=-0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=btconnect.onmicrosoft.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 PdK6JnpOE-jm for <ietf@ietfa.amsl.com>; Thu, 11 Jun 2020 02:57:29 -0700 (PDT)
Received: from EUR04-VI1-obe.outbound.protection.outlook.com (mail-eopbgr80120.outbound.protection.outlook.com [40.107.8.120]) (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 D333C3A07DC for <ietf@ietf.org>; Thu, 11 Jun 2020 02:57:28 -0700 (PDT)
ARC-Seal: i=1; a=rsa-sha256; s=arcselector9901; d=microsoft.com; cv=none; b=oXroPgGXvDzoKMKPdIzqXN0HHR4byg8fiCjb9M1ToT+8SbJIEE4RijvEw4iTNltn1NV/nVa6ygG32OVCA3NHT/UVbIMkffXwgojSEx18cZ4GPnT42ZJ+/MgvURcTf6Pihs4LJtNKQgR+D/XdjVoiq/7rTS5FimSa9G7l20t/MDE8fmI5BSQZNSWK4FyJJWCq1dudBDFIHyd5QfJM4oFD+boyrSR+tWkMI5x5VPgYvgg6vXWFaTsbfK/LubZpzupmeIhcBOB/Nryzpl2iQbMAoLaN2M2odnEfd62NajlAgEYerByJcQZlTp7dl1rCFsfrG2A/O+3VQvVA1zTT42FmCQ==
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=Hgen5a5CxgfbiFyvwXqcyvsoSLoThc34g0/A4TPOknU=; b=lHi+I+ZpEJSH7gSlEM/baFkMzSd8DpjeTTD9SkLdA3qi/oG3Hr6y8JP07kjozAFr+J89ao4HA+Cs7jTgmLuzCreEaQvi09/KpOkWQEQthGQg61uTF1ZNiqAM03/cElAfaTx42U7/c75U5ZmBjLXBpDVhgCuYi8QwSEtRi+JBOT5Yctur91RKsauaOOCQBeO/25Xx9AGXcEtH/oMAkSBR1eqamLxmvmuklusCY0oPr0ZVFu4PhbkDpZu5V5Sa4hI2HWBzuH1Bu0+bh7hQ4PXPGs85ktppnb6l62Tgvf2GMxipPC2JPhhrA0dQXHendbVOBFnwrOCEkEzFuyo7VrEV9w==
ARC-Authentication-Results: i=1; mx.microsoft.com 1; spf=pass smtp.mailfrom=btconnect.com; dmarc=pass action=none header.from=btconnect.com; dkim=pass header.d=btconnect.com; arc=none
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=btconnect.onmicrosoft.com; s=selector2-btconnect-onmicrosoft-com; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-SenderADCheck; bh=Hgen5a5CxgfbiFyvwXqcyvsoSLoThc34g0/A4TPOknU=; b=g7XZgieCRw848j2Ups9joCEpwizeLebMJkcKEsZ/noa9XO4TXaUY0KXwJk14mS4vcVqG4GgV1+IqRiGeFkgYwD9VQaG5Z8jjcnazo7PDTdBh2NNULuXGYnVkZ5TiJb819UbFCGPwEFVXefarnvo/PDNpopHJHEq24gbUVgOg4ek=
Authentication-Results: gmail.com; dkim=none (message not signed) header.d=none;gmail.com; dmarc=none action=none header.from=btconnect.com;
Received: from VI1PR0701MB2480.eurprd07.prod.outlook.com (2603:10a6:800:63::16) by VI1PR07MB3197.eurprd07.prod.outlook.com (2603:10a6:802:25::24) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.3109.7; Thu, 11 Jun 2020 09:57:26 +0000
Received: from VI1PR0701MB2480.eurprd07.prod.outlook.com ([fe80::3474:b82e:e75a:b176]) by VI1PR0701MB2480.eurprd07.prod.outlook.com ([fe80::3474:b82e:e75a:b176%11]) with mapi id 15.20.3109.007; Thu, 11 Jun 2020 09:57:26 +0000
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: quoted-printable
References: <159166311543.4506.736406779378278905@ietfa.amsl.com> <B4293B17-6F83-4B9E-89BF-C0B1388F346F@cable.comcast.com> <CABmDk8=gxXiQ60hpdCNB6jK0EG_ssAQnzjgJp=c9yXNKabHKeA@mail.gmail.com> <CABmDk8mwVfWZQmBwZ9c4xaoStwv7CeRRceihTR846iq_LYPFFw@mail.gmail.com> <F6BFB099-2526-4EEB-A267-F2A1D0A7DDFB@cooperw.in> <35fb0076-a240-096a-de7f-280d5e7ad1e3@cs.tcd.ie> <2F0FDD2B-03C8-4E76-9149-A2666147C66E@csperkins.org> <27875646-243d-8d03-b588-866b883fea7c@cs.tcd.ie> <8C935847-70C8-439B-8F4C-83DB9A43E4DF@ietf.org> <46159495-3bef-be6d-31f7-1b83737359ad@gmail.com>
Date: Thu, 11 Jun 2020 10:57:15 +0100
Message-ID: <1UWB5N5qp3.1XJo2s8wcp8@pc8xp>
In-Reply-To: <46159495-3bef-be6d-31f7-1b83737359ad@gmail.com>
From: tom petch <daedulus@btconnect.com>
To: Melinda Shore <melinda.shore@gmail.com>, "ietf@ietf.org" <ietf@ietf.org>
Subject: Re: [Ietf108planning] Registration open for IETF 108
User-Agent: OEClassic/3.0 (WinXP.2600; F; 2019-11-28)
X-ClientProxiedBy: LO2P265CA0160.GBRP265.PROD.OUTLOOK.COM (2603:10a6:600:9::28) To VI1PR0701MB2480.eurprd07.prod.outlook.com (2603:10a6:800:63::16)
MIME-Version: 1.0
X-MS-Exchange-MessageSentRepresentingType: 1
Received: from pc8xp (86.139.211.47) by LO2P265CA0160.GBRP265.PROD.OUTLOOK.COM (2603:10a6:600:9::28) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.3088.19 via Frontend Transport; Thu, 11 Jun 2020 09:57:25 +0000
X-Originating-IP: [86.139.211.47]
X-MS-PublicTrafficType: Email
X-MS-Office365-Filtering-Correlation-Id: cc157549-1d2c-451f-542d-08d80dedd7e1
X-MS-TrafficTypeDiagnostic: VI1PR07MB3197:
X-Microsoft-Antispam-PRVS: <VI1PR07MB31971FD9479F54C0E9E686D2C6800@VI1PR07MB3197.eurprd07.prod.outlook.com>
X-MS-Oob-TLC-OOBClassifiers: OLM:10000;
X-Forefront-PRVS: 0431F981D8
X-MS-Exchange-SenderADCheck: 1
X-Microsoft-Antispam: BCL:0;
X-Microsoft-Antispam-Message-Info: 5IRn7xn18wxdMaKwmD9pb+PSFbXke6cY8W4bFWKOG9UJcu2iViot6uqlKNqX1MoUhz+FHf7dgWusQDkKhmmXAjtWIz9tPFUouAZwgA3r71LzBkqY7Yid9ls0Qnsb3YYgSAY0617LeVA/YPfniEM1NsrNO6bu2zBDRZKcZy0xdfZRoDRstwe5t/GB+KXPYpb/9x/E31fNPc59DTGVIO8/NUHncD9I1G25BykwgEcreebD3B/t6aBFvmQ3jMIUK1+GfxrNB9WqpjLYV2egYk+sTjwYVkGVVSi1iaKTysUkIx232wDXLhZUapSFQVtdq4ovntIMIcV6hqpwm/UAuLPp3bK9Uio7olRhpXKdBxrDhWM/CjOC0pkqcBhkHT0tq9W7SNrNTIHAGsna1Kse4qCapQ==
X-Forefront-Antispam-Report: CIP:255.255.255.255; CTRY:; LANG:en; SCL:1; SRV:; IPV:NLI; SFV:NSPM; H:VI1PR0701MB2480.eurprd07.prod.outlook.com; PTR:; CAT:NONE; SFTY:; SFS:(376002)(346002)(396003)(366004)(136003)(39860400002)(966005)(478600001)(6666004)(26005)(186003)(8676002)(52230400001)(9686003)(66946007)(66476007)(66556008)(33716001)(2906002)(53546011)(5660300002)(45080400002)(956004)(52116002)(8936002)(9576002)(6496006)(110136005)(66574014)(16526019)(55016002)(316002)(86362001)(83380400001); DIR:OUT; SFP:1102;
X-MS-Exchange-AntiSpam-MessageData: WFfU/SI1E0wizr6CPoUL4/IKwSEHR/iaX3Uk9zrQ+YGGarw/jBr4OJRrSVEz4D6Lf/xOgGuNytTmY6CgqUoaMI0ZGQ2v4q0wHBnmJqTEmEu8D7Se2yZeRasP4RBK8s1ZwinCvyE9noATRdC2o1BEjMaX12fI26BhJbqAFUOwsN0bHReL1arFpWIZBct2fE2JMQxVi9TGlix9Nlk3x3xONQO5nSpx8Fm4OzochlpOTzRSxIFmXUi36uPZ6y/kUbgmKusoaBOPKij+B5A5YHrm0vUTHqU2zA6pirIj5sGJo9CwVavZFsIsgXANh/kZMUjNowX2MMctmJQxC+u47Wx3aol/Tak4DJI+xM6/rVSjfcAVkJdw3oSOgGnRjtDwcWE03I74vpSc2VGbn1sBJBAxuLxgt/fj890OQxNA6KmSeWxKi4xyu+TyEwBNjmL9IdGMN9+Fqeq7z+nkrZG1RM3ImS+tsVjF3QjM4ckwc8G8uaQ=
X-OriginatorOrg: btconnect.com
X-MS-Exchange-CrossTenant-Network-Message-Id: cc157549-1d2c-451f-542d-08d80dedd7e1
X-MS-Exchange-CrossTenant-OriginalArrivalTime: 11 Jun 2020 09:57:25.8971 (UTC)
X-MS-Exchange-CrossTenant-FromEntityHeader: Hosted
X-MS-Exchange-CrossTenant-Id: cf8853ed-96e5-465b-9185-806bfe185e30
X-MS-Exchange-CrossTenant-MailboxType: HOSTED
X-MS-Exchange-CrossTenant-UserPrincipalName: rRRMzNzKfbzbi3PLKYrNKv6k1PBVq/B1AjULSbmhH5Wc6vP8h++FmyQxfvlLuRWK+GKTecL1f+bpLfQJlOIExw==
X-MS-Exchange-Transport-CrossTenantHeadersStamped: VI1PR07MB3197
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/MeGKkijtegkq_lEzsbbCIyuKbMM>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 11 Jun 2020 09:57:31 -0000
----- Original Message ----- From: Melinda Shore <melinda.shore@gmail.com> To: <ietf@ietf.org> Sent: 11/06/2020 03:39:51 On 6/10/20 6:21 PM, Jay Daley wrote: > As well as stating that you see this a switch from a zero to non-zero > fee, I think you’ve also stated that such a switch can only be made with > community consensus. Given that you and some others firmly oppose this > switch it would seem that community consensus could not be achieved > within the necessary timeframe to make such as switch for IETF 108, if > at all, no matter what process was used to try to find consensus. Well, I don't know about that. Stephen can (and does, with admirable vigor) make his own arguments but from my perspective this discussion really hasn't grappled in any meaningful way with the question of openness and the IETF's working method. Introducing a fee for all remote participation in IETF meetings introduces a new barrier to participation[*]. It's not simply about the money, per se. And if we're introducing barriers to participation in ways that impact the openness of the process, it does seem inappropriate to do that without some fairly deliberate community discussion. <tp> Melinda Some time ago, access to the datatracker was changed such that it is inaccessible to older PC such as I sometimes use. I can access IETF, FTP, IANA, e-mail ... along with lots of websites for businesses that want me to buy something from them but not the datatracker. I assume that this was an update to the security, a new level of TLS or a new ciphersuite or .... To overcome this I have to spend hundreds, maybe a thousand or so dollars to upgrade hardware and software which I currently choose not to. Doubtless the Security Area could give me an irrelevant explanation of how much better things are - I just see another barrier to participation introduced without any explanation that I can recall. I put the use of I-D in ASCII as one of the great features of the IETF making access easy - by contrast, the increased use of GitHub takes the IETF in the opposite direction. So the Jay has expressed surprise at the views expressed at what the LLC has or has not a remit to do but that is widely true; there is a folk memory of how things used to be and a resistance to changing some of them :-) I do think that the LLC has taken pragmatic, I might say engineering, decisions in the face of the unknown and that the procedures of the IETF make it rather slow to turn the juggernaut around. Tom Petch ps Software longa, hardware brevis I do not understand this and yes I do know Latin --- New Outlook Express and Windows Live Mail replacement - get it here: https://www.oeclassic.com/ Melinda [*] The fee waiver program strikes me as a bandaid, not a solution. -- Melinda Shore melinda.shore@gmail.com Software longa, hardware brevis
- Re: [Ietf108planning] Registration open for IETF … Toerless Eckert
- Re: Registration open for IETF 108 Dan Romascanu
- Re: [Ietf108planning] Registration open for IETF … Jay Daley
- Re: [Ietf108planning] Registration open for IETF … Melinda Shore
- Re: [Ietf108planning] Registration open for IETF … Jay Daley
- Re: Registration open for IETF 108 Ish Sookun
- Re: Registration open for IETF 108 John C Klensin
- Re: Registration open for IETF 108 Livingood, Jason
- RE: Registration open for IETF 108 Adrian Farrel
- Re: [Ietf108planning] Registration open for IETF … Bajpai, Vaibhav
- Re: Registration open for IETF 108 Mary B
- Re: [Ietf108planning] Registration open for IETF … Alissa Cooper
- Re: [Ietf108planning] Registration open for IETF … Livingood, Jason
- Re: Registration open for IETF 108 Mary B
- Re: [EXTERNAL] Re: Registration open for IETF 108 Livingood, Jason
- Re: [Ietf108planning] Registration open for IETF … Joel M. Halpern
- Re: Registration open for IETF 108 Livingood, Jason
- Re: Registration open for IETF 108 Ish Sookun
- Re: Registration open for IETF 108 Ish Sookun
- Re: [Ietf108planning] Registration open for IETF … Alissa Cooper
- Re: [Ietf108planning] Registration open for IETF … Joel M. Halpern
- Re: [Ietf108planning] Registration open for IETF … Alissa Cooper
- Re: [Ietf108planning] Registration open for IETF … Alissa Cooper
- Re: [Ietf108planning] Registration open for IETF … Mary B
- Re: [Ietf108planning] Registration open for IETF … Stephen Farrell
- Re: [Ietf108planning] Registration open for IETF … Paul Wouters
- Re: [Ietf108planning] Registration open for IETF … George Michaelson
- Re: [Ietf108planning] Registration open for IETF … Alissa Cooper
- Re: [Ietf108planning] Registration open for IETF … Brian E Carpenter
- Re: [Ietf108planning] Registration open for IETF … Ole Jacobsen
- Re: [Ietf108planning] Registration open for IETF … Colin Perkins
- Re: [Ietf108planning] Registration open for IETF … Colin Perkins
- Re: [Ietf108planning] Registration open for IETF … Stephen Farrell
- Re: [Ietf108planning] Registration open for IETF … John Levine
- Re: [Ietf108planning] Registration open for IETF … Ole Jacobsen
- Re: [Ietf108planning] Registration open for IETF … Jay Daley
- Re: [Ietf108planning] Registration open for IETF … Jay Daley
- Re: [Ietf108planning] Registration open for IETF … Melinda Shore
- Re: [Ietf108planning] Registration open for IETF … Jay Daley
- Re: [Ietf108planning] Registration open for IETF … Melinda Shore
- Re: [Ietf108planning] Registration open for IETF … Ish Sookun
- Re: [Ietf108planning] Registration open for IETF … Alexa Morris
- Re: [Ietf108planning] Registration open for IETF … Randy Bush
- Re: [Ietf108planning] Registration open for IETF … John C Klensin
- Re: [Ietf108planning] Registration open for IETF … Jay Daley
- Re: [Ietf108planning] Registration open for IETF … Lars Eggert
- Re: [Ietf108planning] Registration open for IETF … Tim Chown
- RE: [Ietf108planning] Registration open for IETF … Adrian Farrel
- Re: [Ietf108planning] Registration open for IETF … Jay Daley
- Re: [Ietf108planning] Registration open for IETF … S Moonesamy
- Re: [Ietf108planning] Registration open for IETF … tom petch
- Re: [Ietf108planning] Registration open for IETF … Stephen Farrell
- Re: [Ietf108planning] Registration open for IETF … Corinne Cath
- Re: [Ietf108planning] Registration open for IETF … John C Klensin
- Re: [Ietf108planning] Registration open for IETF … Colin Perkins
- Re: [Ietf108planning] Registration open for IETF … Corinne Cath
- Re: [Ietf108planning] Registration open for IETF … Gurshabad Grover
- Re: [Ietf108planning] Registration open for IETF … tom petch
- Re: [Ietf108planning] Registration open for IETF … Livingood, Jason
- Re: [Ietf108planning] Registration open for IETF … Bob Hinden
- Re: [Ietf108planning] Registration open for IETF … Phillip Hallam-Baker
- Re: [Ietf108planning] Registration open for IETF … Pete Resnick
- RE: [Ietf108planning] Registration open for IETF … STARK, BARBARA H
- Re: [Ietf108planning] Registration open for IETF … Lucy Lynch
- Re: [Ietf108planning] Registration open for IETF … Michael Richardson
- Re: [Ietf108planning] Registration open for IETF … Ole Jacobsen
- Re: [Ietf108planning] Registration open for IETF … Russ Housley
- Re: [Ietf108planning] Registration open for IETF … Joel M. Halpern
- Re: [Ietf108planning] Registration open for IETF … Mary B
- Re: [Ietf108planning] Registration open for IETF … Michael Thomas
- Re: [Ietf108planning] Registration open for IETF … Phillip Hallam-Baker
- RE: [Ietf108planning] Registration open for IETF … STARK, BARBARA H
- Re: [Ietf108planning] Registration open for IETF … Michael Thomas
- RE: [Ietf108planning] Registration open for IETF … STARK, BARBARA H
- Re: [Ietf108planning] Registration open for IETF … Mary B
- Re: [Ietf108planning] Registration open for IETF … John Levine
- Re: [Ietf108planning] Registration open for IETF … Ole Jacobsen
- Re: [Ietf108planning] Registration open for IETF … Brian E Carpenter
- Re: [Ietf108planning] Registration open for IETF … Spencer Dawkins at IETF
- Re: [Ietf108planning] Registration open for IETF … Phillip Hallam-Baker
- Re: [Ietf108planning] Registration open for IETF … Michael Thomas
- Re: [Ietf108planning] Registration open for IETF … Stephen Farrell
- Re: [Ietf108planning] Registration open for IETF … Michael Thomas
- Re: [Ietf108planning] Registration open for IETF … Carsten Bormann
- Re: [Ietf108planning] Registration open for IETF … Michael Thomas
- Re: [Ietf108planning] Registration open for IETF … Michael StJohns
- Re: [Ietf108planning] Registration open for IETF … Toerless Eckert
- Re: [Ietf108planning] Registration open for IETF … Jay Daley
- RE: [Ietf108planning] Registration open for IETF … John C Klensin
- Re: [Ietf108planning] Registration open for IETF … Toerless Eckert
- Re: Re: [Ietf108planning] Registration open for I… tom petch
- Re: [Ietf108planning] Registration open for IETF … Jay Daley
- Re: [Ietf108planning] Registration open for IETF … Toerless Eckert
- RE: [Ietf108planning] Registration open for IETF … S Moonesamy
- Re: [Ietf108planning] Registration open for IETF … Michael Richardson
- Re: [Ietf108planning] Registration open for IETF … Randy Bush
- Re: [Ietf108planning] Registration open for IETF … Christian Huitema
- Re: [Ietf108planning] Registration open for IETF … Carsten Bormann
- RE: [Ietf108planning] Registration open for IETF … Adrian Farrel
- Re: [Ietf108planning] Registration open for IETF … S Moonesamy
- Re: [Ietf108planning] Registration open for IETF … Tim Chown
- Re: [Ietf108planning] Registration open for IETF … S Moonesamy
- Re: [Ietf108planning] Registration open for IETF … Jay Daley
- Re: [Ietf108planning] Registration open for IETF … S Moonesamy