Re: IETF 112 will be a fully online meeting
Brian Carpenter <brian.e.carpenter@gmail.com> Mon, 06 September 2021 09:07 UTC
Return-Path: <brian.e.carpenter@gmail.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 741DF3A27F0 for <ietf@ietfa.amsl.com>; Mon, 6 Sep 2021 02:07:46 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.097
X-Spam-Level:
X-Spam-Status: No, score=-2.097 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, 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=gmail.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 MYL4xU7oJsqf for <ietf@ietfa.amsl.com>; Mon, 6 Sep 2021 02:07:41 -0700 (PDT)
Received: from mail-lf1-x12b.google.com (mail-lf1-x12b.google.com [IPv6:2a00:1450:4864:20::12b]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 377EF3A27EE for <ietf@ietf.org>; Mon, 6 Sep 2021 02:07:41 -0700 (PDT)
Received: by mail-lf1-x12b.google.com with SMTP id m28so12239944lfj.6 for <ietf@ietf.org>; Mon, 06 Sep 2021 02:07:41 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20210112; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=oucQP8mSDgLsK9FjcgVONoPRAj5d30rock9kjwmGdu0=; b=ZTD+JdYuPDtAunvBJVZ6s1HR8Xp3qO7T7BMz9HZq5nhnWg/WD86MQmsa5nLLMtwIw2 btXVPDfp2BF0j0QkPqsjxgPyDGCZ64/lYJV+8wb2iJ87Jub6cFMJm+4EK5c5COA7P6eJ bssnX25U8TOuFnsII9Gi4FBheQadwGIRwqaD1u46hcTlJR5W/U8YlNY7ugAlslAV3Afg IsCSA7RHdiJsuIHzwbb0ixUKIWYZplN/64Fsu36MYD4RChp0LogxomUaycn812arpPTt gkyVPLkPfO/BF0NQ5kZKptgbmUW4FcxYnhi1N8abYlVMQHT4uaEwSIohNfacw0l2fHH2 bLVQ==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=oucQP8mSDgLsK9FjcgVONoPRAj5d30rock9kjwmGdu0=; b=thHvcEc0RjUzwNLdtTCUfLO3p4NL+48V1NLKkcLMB6yRIyKY/vsHvTYBEI4F+mHmMW a5NlqlmVjAOpHTvryXW/swtZ6Obc1qWR4HwNSqCLuSVW8fJthyaEnmLqtwtH2+2dJliT GWWUvBLnlpKWzJcw3Fjtvv/aHPutBPyES3RXIJAP3TH6bsKSWwML9H0m4VCZ5jVUhCzs SXBYqjOOPbc80XXTP1nFn7v9dojKquSb8vcZnDWQ9GYQaVjtcS1Ce/MYxfAciiZiNJNZ CKgIxcTJoEzblYpF4obh4EVqf8VuHbfu3UW4y3eO6rszUd96hGxA9+zXi0wEyD1XW4+H xsRw==
X-Gm-Message-State: AOAM532lGj+2gWdliAupyYdOErXbZ+8ED9nYPkhKNLtxfyGpnvg2cmxB QMXOMTLFfoEL2iSWv/C1z1CUUEVbgKjvtul5PfI=
X-Google-Smtp-Source: ABdhPJyW6QWghpZrdbYz2BYlLoePwez7Sc9lpRxL+i31+Vxz9dB3VnWWEX/CMouTQV/yuROTeD3RvexXJHBqXHl4iGk=
X-Received: by 2002:ac2:5ec8:: with SMTP id d8mr8345245lfq.579.1630919258133; Mon, 06 Sep 2021 02:07:38 -0700 (PDT)
MIME-Version: 1.0
References: <AA8F6C0130E7BB47D5F8BFB9@PSB> <CAKKJt-dquxfRO7Ja2CrTKsArtt1Qb5LHE=rYnsy7vZC7CAKH4w@mail.gmail.com> <8DC46226B92BBF36C000C0CA@PSB> <CAKXoubvNjdqOYozaoMZd8Obe2jcszEqf=5CjK7L51UvWv-ExcQ@mail.gmail.com> <PAXPR07MB7999E49CA6174EAC117EB00092D29@PAXPR07MB7999.eurprd07.prod.outlook.com>
In-Reply-To: <PAXPR07MB7999E49CA6174EAC117EB00092D29@PAXPR07MB7999.eurprd07.prod.outlook.com>
From: Brian Carpenter <brian.e.carpenter@gmail.com>
Date: Mon, 06 Sep 2021 21:07:26 +1200
Message-ID: <CANMZLAYRP_tyzSzjgGW57qdQRE4wvK=S7FA-voQSCO0jU2JZDQ@mail.gmail.com>
Subject: Re: IETF 112 will be a fully online meeting
To: "Maisonneuve, Julien (Nokia - FR/Paris-Saclay)" <julien.maisonneuve@nokia.com>
Cc: Michael Speer <michael.speer=40pluribusnetworks.com@dmarc.ietf.org>, John C Klensin <john-ietf@jck.com>, IETF list <ietf@ietf.org>, JORDI PALET MARTINEZ <jordi.palet=40consulintel.es@dmarc.ietf.org>
Content-Type: multipart/alternative; boundary="00000000000009d6c105cb4ffb92"
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/rhaV6zg_Z3zBYC4jQjyP_N5zKHk>
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: Mon, 06 Sep 2021 09:07:47 -0000
The virus travels by international flights, without bothering to check in. That makes large international meetings a rather special case. Having invented the Internet, we'd be a bit strange not to use it. Regards, Brian Carpenter (via tiny screen & keyboard) On Mon, 6 Sep 2021, 20:47 Maisonneuve, Julien (Nokia - FR/Paris-Saclay), < julien.maisonneuve@nokia.com> wrote: > Things are worse globally, but not so bad in many places. > > Should we avoid anything that can spread the disease and remain in our > dwellings relying on deliveries because the situation is bad in many places > ? Most governments have taken another approach (vaccination, masks, gel, > some distancing) and allow near-normal life. Surely IETF can learn from > their example. > > Julien. > > > > *From:* ietf <ietf-bounces@ietf.org> *On Behalf Of *Michael Speer > *Sent:* Saturday, September 4, 2021 8:50 PM > *To:* John C Klensin <john-ietf@jck.com> > *Cc:* IETF list <ietf@ietf.org>; JORDI PALET MARTINEZ <jordi.palet= > 40consulintel.es@dmarc.ietf.org> > *Subject:* Re: IETF 112 will be a fully online meeting > > > > Wow! Guys we are in a global pandemic! Common sense says take the least > amount of risk possible for everyone concerned. Things are now worse > globally, so why meet in person and spread the disease even further? > > > > On Sat, Sep 4, 2021 at 08:50 John C Klensin <john-ietf@jck.com> wrote: > > Spencer, > > Your characterization of my comments is correct. The thing you > left out is that most existing such insurance politics contain, > often in fine print, provisions that the insured party is not > allowed to be egregiously stupid and/or to ignore clear legal or > equivalent advice. > > To extend your example into the ridiculous, suppose that, in > addition to declaring consensus, you told the proponents of the > losing proposal to go jump in the lake, a lake that you knew was > infested by deadly and fles-eating bacteria, viruses, or > animals. Suppose they followed your advice and their heirs or > companies then sued. Whether the insurance company would pay up > or defend you would probably depend on the company and the > policy but, if they did, they would almost certainly try to > recover costs (at least) from you and/or whomever was > responsible for putting you in that position. And then the > various lawyers would get rich trying to settle the issue of > whether you were the stupid and irresponsible one for making > such a suggestion or whether the parties who ended up in the > lake were responsible because treating your advice as anything > but metaphor were the stupid ones. > > See Jay's note and, again, changing the organizational location > of the IETF would not change things very much because the issues > from the standpoint of the insurers don't change much even if > explicit government policies do. > > best, > john > > > > > --On Saturday, September 4, 2021 10:20 -0500 Spencer Dawkins at > IETF <spencerdawkins.ietf@gmail.com> wrote: > > > I'm current with the downthread discussion as of me typing > > this, but I'm backing up to John's email, because it mentioned > > an important point, that I happen to know a little, but only a > > little, about, and my experience has been that much of the > > community isn't aware of (and people don't even know that > > they're not aware of it, because the topic doesn't come up in > > discussions very often). > > > > John, please feel free to correct me if I'm misrepresenting > > what you said here. > > > > On Thu, Sep 2, 2021 at 2:02 AM John C Klensin > > <john-ietf@jck.com> wrote: > > > >> IANAL, but I have spent some time dealing with insurance > >> companies, including special risk underwriters, and trying to > >> understand the statistical risk assessments on which > >> willingness to insure and rates are ultimately based. While > >> neither RFC 8717 nor 8718 appear to mention insurance among > >> the criteria, I suppose it is safe to assume that, were an > >> insurer come to the IETF and say, e.g., "if one of your > >> meetings turns into a superspreader event, there will be no > >> coverage for either the LLC or individual IESG or LLC Board > >> members being sued over the irresponsible decision", there > >> would be no f2f meeting. > > > > > > When I went through WG chair training in the late 1990s for > > the first time, I was told (in a different world, of course - > > Steve Coya and Jeff Schiller were doing the training, IIRC) > > that ISOC provided insurance for (at least, not sure who else) > > WG chairs, in case they were sued because of decisions they > > made as part of their responsibilities. > > > > So, > > > > - if my working group considered two individual-draft > > proposals, and > > - one was adopted and the other was not, and > > - the proponents of the proposal that was NOT adopted sued > > me as the working group chair that made that decision > > and/or declared consensus on that decision, > > > > there was an insurance policy that covered me making that > > decision. > > > > (I'm not sure if this is even true these days, because I > > haven't wondered about insurance in nearly two decades, but > > stay with me here). > > > > If there's a similar situation in place these days, and it > > covers (for instance) IESG members and LLC members who would > > be involved in making venue decisions as part of their > > responsibilities, I can EASILY imagine an insurance company > > saying "ya know, defending people who might send hundreds of > > people into harm's way because of a careless decision they > > make during the Age of Plague either isn't something we want > > to do, or we need to talk about how much we'll charge to > > defend them for making those decisions, and the price isn't > > going down". > > > > I THINK that's what John is saying here, and because there are > > people on this list who likely are more current than I am, I > > won't try to do more than provide background from my past > > understanding. > > > > But, please, continue. > > > > Best, > > > > Spencer > >
- Re: IETF 112 will be a fully online meeting JORDI PALET MARTINEZ
- Re: IETF 112 will be a fully online meeting Behcet Sarikaya
- Re: IETF 112 will be a fully online meeting JORDI PALET MARTINEZ
- Re: IETF 112 will be a fully online meeting Michael Richardson
- Re: IETF 112 will be a fully online meeting JORDI PALET MARTINEZ
- Re: IETF 112 will be a fully online meeting Michael Richardson
- Re: IETF 112 will be a fully online meeting John C Klensin
- Re: IETF 112 will be a fully online meeting JORDI PALET MARTINEZ
- Re: IETF 112 will be a fully online meeting JORDI PALET MARTINEZ
- Re: IETF 112 will be a fully online meeting John C Klensin
- Re: IETF 112 will be a fully online meeting Michael Richardson
- Re: IETF 112 will be a fully online meeting tom petch
- Re: IETF 112 will be a fully online meeting Jay Daley
- Re: IETF 112 will be a fully online meeting Spencer Dawkins at IETF
- Re: IETF 112 will be a fully online meeting John C Klensin
- Re: IETF 112 will be a fully online meeting Michael Speer
- Re: IETF 112 will be a fully online meeting John C Klensin
- Re: IETF 112 will be a fully online meeting Lloyd W
- Re: IETF 112 will be a fully online meeting Michael Speer
- RE: IETF 112 will be a fully online meeting Vasilenko Eduard
- RE: IETF 112 will be a fully online meeting Maisonneuve, Julien (Nokia - FR/Paris-Saclay)
- Re: IETF 112 will be a fully online meeting Brian Carpenter
- RE: IETF 112 will be a fully online meeting Vittorio Bertola
- Re: IETF 112 will be a fully online meeting Carsten Bormann
- Re: IETF 112 will be a fully online meeting Lars Eggert