Re: [Manycouches] John Scudder's No Objection on draft-ietf-shmoo-cancel-meeting-05: (with COMMENT)

Martin Duke <martin.h.duke@gmail.com> Tue, 13 July 2021 20:47 UTC

Return-Path: <martin.h.duke@gmail.com>
X-Original-To: manycouches@ietfa.amsl.com
Delivered-To: manycouches@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 635423A090F; Tue, 13 Jul 2021 13:47:21 -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 18pPTvoBJTP1; Tue, 13 Jul 2021 13:47:17 -0700 (PDT)
Received: from mail-il1-x12e.google.com (mail-il1-x12e.google.com [IPv6:2607:f8b0:4864:20::12e]) (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 64B373A0909; Tue, 13 Jul 2021 13:47:16 -0700 (PDT)
Received: by mail-il1-x12e.google.com with SMTP id w1so22535396ilg.10; Tue, 13 Jul 2021 13:47:16 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=2TTtRF2dNmxqa2pFqZeJH429+yZQzbUmL5nfhZS0UGE=; b=OcPsCSauvL9x3Zb71r4oVDCDYSmWZfRO/wDLzIglBFcJT11jTrPbqoEDfbMwiLd1qO ZAKcGZ4XaYKqUt2SEkokzNoeeINsEz6JhqYUqk420vjcICWz3WNBm8OqL8fw+saITy/o vTBZioFzXNOM+4YYyii9xU7naQtt7NvRxDnPRJ0uOg/MHpua3Zjs8mZa8UsrymymJhRd nBS83q9lh23zrnwBP/WPeBP5widJsGuRl31UnbRnu1EtM5VcWn4mUlwFrn0jNsAHaKuH kSITxfr4zWC4KoP3dRgfpzTvUYbTi7no/M1gpj0UO4oq/fTk2GLe10deE+bZjcz32+GU aJlg==
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=2TTtRF2dNmxqa2pFqZeJH429+yZQzbUmL5nfhZS0UGE=; b=FYQJDXc2EUQWP87d5/3bLuioghGRYJwNQN/wGLn3+upgjhNXpYAV/IjgayKQEstWE/ bzcAv5J+GYkas9o70Yq3EDD0fcmmPR8ogEFrZ2DiWhyMATt74VNiArzPLm6eBn17mVk5 GJwGrruEOK8tYoJcQ+SfAGoVhUknO8S544b/PsqteFBXkrBzUKKPjJ6OZjcqnGVoq7IZ +o2h9lM/roQIlac+kKVMHjXU7RI7Y40c/h/o5Nw5MBOS6Jltc8r48w3sE9LblashMYgH /lDweT8+7z+vvsjdYbo9sOHR9DfA5/z7WQFjw/W+iCNLX5/Dj65dQQpbaGJmY5bdJGtr SJSg==
X-Gm-Message-State: AOAM531aSKZI4+kDSm2CVBgueP1L+jYWTbNAH43TPCONfcvo6PqT3xig fdISeqemvTCYqxrgV3YXmZpf0cE07UHTwncEvfw=
X-Google-Smtp-Source: ABdhPJxYNKwBuc7Bq6SFDtwFohAEWx1rmAOg6sTtezGkfNZ58TbWgz6m0FP9zuMmFrWFPE8FIaf/wjqmz4yZUxIEX8o=
X-Received: by 2002:a92:8e10:: with SMTP id c16mr4198798ild.237.1626209234834; Tue, 13 Jul 2021 13:47:14 -0700 (PDT)
MIME-Version: 1.0
References: <162620801812.6466.1160695712719551591@ietfa.amsl.com>
In-Reply-To: <162620801812.6466.1160695712719551591@ietfa.amsl.com>
From: Martin Duke <martin.h.duke@gmail.com>
Date: Tue, 13 Jul 2021 13:47:03 -0700
Message-ID: <CAM4esxQTFJ3onOBhpPAPZYPnwrDTLbJPanzZ-tO8q82HMGM5xg@mail.gmail.com>
To: John Scudder <jgs@juniper.net>
Cc: The IESG <iesg@ietf.org>, draft-ietf-shmoo-cancel-meeting@ietf.org, shmoo-chairs@ietf.org, manycouches@ietf.org, Amelia Andersdotter <amelia@centr.org>
Content-Type: multipart/alternative; boundary="000000000000c5d92605c7075729"
Archived-At: <https://mailarchive.ietf.org/arch/msg/manycouches/5v_lQLBNAA7Hn8NC6VAc_-2bHcM>
Subject: Re: [Manycouches] John Scudder's No Objection on draft-ietf-shmoo-cancel-meeting-05: (with COMMENT)
X-BeenThere: manycouches@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: "List for discussion of remote meeting attendance and virtual IETF meetings, as well as for SHMOO working group" <manycouches.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/manycouches>, <mailto:manycouches-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/manycouches/>
List-Post: <mailto:manycouches@ietf.org>
List-Help: <mailto:manycouches-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/manycouches>, <mailto:manycouches-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 13 Jul 2021 20:47:22 -0000

Thanks John,

This PR is merged:
https://github.com/martinduke/draft-ietf-shmoo-cancel-meeting/pull/15


On Tue, Jul 13, 2021 at 1:26 PM John Scudder via Datatracker <
noreply@ietf.org> wrote:

> 3. I reviewed the Github Editor's copy (as of July 13 16:00 EDT or so) and
> noticed that the text "These remedies are listed in approximate declining
> order
> of preference" was added to the end of §4. That directly conflicts with
> version
> 5's "presented in no particular order". I like the text in v5 and don't
> particularly like the proposed edit.
>

So the principles are in no particular order and the remedies are in rough
order. I don't feel
strongly one way or the other as to whether this sentence stays in. IIUC
this is the one thing
that may still need attention having merged the PR.


>
> 4. Regarding
>
>    The IETF SHOULD NOT reimburse registered attendees for unrecoverable
>    travel expenses (airfare, hotel deposits, etc).
>
> Has any consideration been given to adding some kind of text to the effect
> that
> attendees might choose to protect themselves against such losses with
> appropriate travel insurance? I appreciate that it would represent scope
> creep
> (it's not directly germane to "providing criteria for making this
> judgement")
> so I'm not bothered if this isn't adopted; however, I can see some
> benefits to
> including it.
>

I consider it out of scope, and I'd rather not recommend travel insurance
to people.


>
> 5. Regarding
>
>    *  Cancellation SHOULD result in a full refund to all participants.
>       It MAY be prorated if some portion of the sessions completed
>       without incident.
>
> I presume this has been discussed to death, and it's understood this may
> result
> in the IETF eating sunk costs? (Similar applies to the rest of the bullets
> in
> the list.) I do see there's an escape clause for "extraordinary threats to
> the
> solvency of the organization".
>

There was some discussion but this bit was not all that controversial. Jay
did a review and thought it was fine.


> 7. Is the Acknowledgements section empty deliberately?
>

D'oh! Fixed now.