[Manycouches] AD review: draft-ietf-shmoo-remote-fee-04
Lars Eggert <lars@eggert.org> Thu, 08 December 2022 12:58 UTC
Return-Path: <lars@eggert.org>
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 A1EA1C1516F4; Thu, 8 Dec 2022 04:58:40 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.096
X-Spam-Level:
X-Spam-Status: No, score=-2.096 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, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001, URIBL_DBL_BLOCKED_OPENDNS=0.001, URIBL_ZEN_BLOCKED_OPENDNS=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=eggert.org
Received: from mail.ietf.org ([50.223.129.194]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id gliEFTlwk2Ch; Thu, 8 Dec 2022 04:58:36 -0800 (PST)
Received: from mail.eggert.org (mail.eggert.org [91.190.195.94]) (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 368CBC14CE53; Thu, 8 Dec 2022 04:58:36 -0800 (PST)
Received: from smtpclient.apple (unknown [IPv6:2a00:ac00:4000:400:4d1c:18e3:378c:fa95]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by mail.eggert.org (Postfix) with ESMTPSA id 9701D1D914C; Thu, 8 Dec 2022 14:58:26 +0200 (EET)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=eggert.org; s=dkim; t=1670504306; bh=3I0go0uaTFQod7EJtyRkth62ARevc0fP1cMTgNPf2S4=; h=Subject:From:In-Reply-To:Date:Cc:References:To; b=iyZfwgwhVwrQSDPjQHBhbj6GPNaDOT8/c3kKCtASCyPYJVcE645/4vEmFv2Y9CHH6 M7NA1jU4tGCvx4T4zKTQoSdrjKgSIsjhfAXxj/kne950xR1Gz4GpCcfdc3xkIbuu2x 9qK+Y48GfHSIUEopi5065IeorwpPBY+v45WwLtW4=
Content-Type: multipart/signed; boundary="Apple-Mail=_EE064D17-2E6E-47BC-A718-7294BF0CA15B"; protocol="application/pgp-signature"; micalg="pgp-sha512"
Mime-Version: 1.0 (Mac OS X Mail 16.0 \(3731.200.110.1.12\))
From: Lars Eggert <lars@eggert.org>
In-Reply-To: <167046836387.29741.3254288906554935906@ietfa.amsl.com>
Date: Thu, 08 Dec 2022 14:58:17 +0200
Cc: shmoo-chairs@ietf.org, draft-ietf-shmoo-remote-fee@ietf.org
Message-Id: <62E4F044-3C40-4653-8E6E-DDCEAD6E2347@eggert.org>
References: <167046836387.29741.3254288906554935906@ietfa.amsl.com>
To: manycouches@ietf.org
X-MailScanner-ID: 9701D1D914C.A402E
X-MailScanner: Not scanned: please contact your Internet E-Mail Service Provider for details
X-MailScanner-From: lars@eggert.org
Archived-At: <https://mailarchive.ietf.org/arch/msg/manycouches/Xe9Cw8fg2puFIBJad2fvqhcJlkg>
Subject: [Manycouches] AD review: draft-ietf-shmoo-remote-fee-04
X-BeenThere: manycouches@ietf.org
X-Mailman-Version: 2.1.39
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: Thu, 08 Dec 2022 12:58:40 -0000
# GEN AD review of draft-ietf-shmoo-remote-fee-04 CC @larseggert ## Comments ### Section 1, paragraph 2 ``` Remote participation for IETF in-person meetings has evolved over time from email-only to live chat and audio streaming, and, subsequently, to a full online meeting system that is tightly integrated with the in-room session and enables interactive participation by audio and video. Due to this evolution, and because most in-person attendees paid registration fees and this has been sufficient to support the meeting, online participation has historically been free for remote attendees. ``` The meeting fees have never been sufficient to support the meetings - meeting sponsors and the ISOC support are critical. I think it may be better to replace the entire final sentence with simply "Online participation has historically been free for remote attendees", sidestepping all of this. ### Section 1, paragraph 3 ``` With the move to fully online meetings in 2020, however, there is no longer a distinction between remote and on-site participants. Since IETF meeting costs and other costs still had to be covered, there was the need for a meeting fee for remote participants, which risks the removal of the free remote option. ``` Would rephrase the last sentence as "Since IETF meeting costs and other costs still had to be recovered, a meeting fee was charged for remote participants, eliminating the free remote participation option (for a time)." ### Section 2, paragraph 3 ``` The principle this document states is simple: there must always be an option for free remote participation in any IETF meeting, regardless of whether the meeting has a physical presence. Related events of a meeting for which the IETF provides remote participation services and are therefore part of the IETF's open process [RFC3935] are encouraged to follow this principle as well. ``` Suggest to rephrase the last sentence as "Related events collocated with an IETF meeting are part of the IETF's open process [RFC3935] and are encouraged to follow this principle as well."" ### Section 3, paragraph 2 ``` Online meetings can have lower costs than in-person meetings, however, they still come with expenses, as do other services that the IETF provides such as mailing lists, document access via the datatracker or other online platforms, or support for videoconferencing, e.g., with Webex accounts for working groups and other roles in the IETF. ``` Webex is not a good example, since it's an in-kind donation. We do pay for Meetecho, that would be a better example. ### Section 3, paragraph 2 ``` These and other operating costs of the IETF are also cross-financed by income generated through meeting fees. The intention of this document and the principle stated herein is not to make participation free for everyone, but to always offer a free remote participation option that a potential attendee can apply for without any barriers other than the registration procedure itself. As long as the overall meeting expenses are covered by paid registrations, sponsorships and other sources of revenue, additional remote participants usually impose very low additional expenses. ``` "without any barriers other than the registration procedure" - this seems to prevent requiring fee waiver requests? ### Inclusive language Found terminology that should be reviewed for inclusivity; see https://www.rfc-editor.org/part2/#inclusive_language for background and more guidance: * Terms `his` and `her`; alternatives might be `they`, `them`, `their` ## Nits All comments below are about very minor potential issues that you may choose to address in some way - or ignore - as you see fit. Some were flagged by automated tools (via https://github.com/larseggert/ietf-reviewtool), so there will likely be some false positives. There is no need to let me know what you did with these suggestions. ### Typos #### Section 1, paragraph 2 ``` - seen an increasing number of remote participants. This increase can + seeing an increasing number of remote participants. This increase can + + + ``` #### Section 1, paragraph 2 ``` - better understand these trends the IETF started requiring + better understand these trends, the IETF started requiring + + ``` #### Section 1, paragraph 3 ``` - With the move to fully online meetings in 2020, however, there is no - ^ + With the move to fully online meetings in 2020, however, there was no + ^^ ``` #### Section 1, paragraph 4 ``` - about the potential impact on both, those who regularly remotely - - ``` #### Section 1, paragraph 4 ``` - attend IETF meetings as well as people considering attending an IETF - -------------- + attend IETF meetings and those considering attending an IETF + ++++++ ``` #### Section 2, paragraph 5 ``` - and documentation and making them accessible over the Internet, it - ---- --- ^^ ^^^ + and materials and to make them accessible over the Internet, it + ++ ^^^ +++ ^ ``` #### Section 2, paragraph 6 ``` - possible. This document rather says that if remote participation is - ^ + possible. This document rather states that if remote participation is + + ^^ ``` #### Section 3, paragraph 1 ``` - however, they still come with expenses, as do other services that the - -- ^^^ ^^^^^^^^ - IETF provides such as mailing lists, document access via the + however, they incur expenses, as do other services that the + ^ ^^ + IETF provides, such as mailing lists, document access via the + + ``` #### Section 3, paragraph 2 ``` - These and other operating costs of the IETF are also cross-financed - ^^ + These and other operating costs of the IETF are partially cross-financed + +++++ ^^ ``` #### Section 3, paragraph 3 ``` - the cost of free participation emerges to a signification factor, the + the cost of free participation emerges to be a signification factor, the + +++ ``` #### Section 4, paragraph 1 ``` - This document does not provide specific requirements on when to use - ^ ----- ^^^ ^^^ + This document does not offer specific guidance to participants on when to use + ^^^^ ^ +++++++++++ ^^^^^^ ``` #### Section 4, paragraph 1 ``` - participants, nor to any specific other restrictions like the number - --- ----- - ------ ^^^^^^ + participants, nor to any criteria, like the number + + ^^ ``` #### Section 4, paragraph 2 ``` - It is expected that participants who have financial support to use - ^^^ ^ --- - the regular registration option will do so. Paying a registration - ----------- + It is encouraged that participants who have financial support use + ^ ^^^^^ + the regular paid registration option. Paying a registration + +++++ ``` #### Section 4, paragraph 3 ``` - the number and percentage of free registrations used should be - ----- ``` #### Section 4, paragraph 3 ``` - published, as this will permit analysis of the use and change in use - ------------------ ``` #### Section 4, paragraph 4 ``` - As the principle defined in this document aims to promote openness - -- ---- - and thereby enhance participation, an increase in use of free - ^^^^^^^^^^^ + As the principle defined in this document aims to promote participation + +++++++++++ + and thereby enhance openness, an increase in use of free + + ^ ++++ ``` #### Section 4, paragraph 4 ``` - registrations stays stable and retains the projected needed income. - If the number of paid registrations, however, decreases, this can - ^ ---------- - still also have various reasons other than misuse, such as - ^ ------- ----- + registrations stays stable and the needed registration revenue is realized. + However, if the number of paid registrations decreases, this can + ^^^^^^^^^^ + be due to various reasons other than misuse, such as + ^^^^^^^ ``` ## Notes This review is in the ["IETF Comments" Markdown format][ICMF], You can use the [`ietf-comments` tool][ICT] to automatically convert this review into individual GitHub issues. Review generated by the [`ietf-reviewtool`][IRT]. [ICMF]: https://github.com/mnot/ietf-comments/blob/main/format.md [ICT]: https://github.com/mnot/ietf-comments [IRT]: https://github.com/larseggert/ietf-reviewtool
- [Manycouches] Publication has been requested for … Suresh Krishnan via Datatracker
- [Manycouches] AD review: draft-ietf-shmoo-remote-… Lars Eggert
- Re: [Manycouches] AD review: draft-ietf-shmoo-rem… Mirja Kuehlewind
- Re: [Manycouches] AD review: draft-ietf-shmoo-rem… Lars Eggert
- Re: [Manycouches] AD review: draft-ietf-shmoo-rem… Mirja Kuehlewind
- Re: [Manycouches] AD review: draft-ietf-shmoo-rem… Lars Eggert
- Re: [Manycouches] AD review: draft-ietf-shmoo-rem… Mirja Kuehlewind
- Re: [Manycouches] AD review: draft-ietf-shmoo-rem… Lars Eggert
- Re: [Manycouches] AD review: draft-ietf-shmoo-rem… Mirja Kuehlewind
- Re: [Manycouches] AD review: draft-ietf-shmoo-rem… John C Klensin
- Re: [Manycouches] AD review: draft-ietf-shmoo-rem… Mirja Kuehlewind
- Re: [Manycouches] AD review: draft-ietf-shmoo-rem… Barry Leiba
- Re: [Manycouches] AD review: draft-ietf-shmoo-rem… Mirja Kuehlewind
- Re: [Manycouches] AD review: draft-ietf-shmoo-rem… John C Klensin
- Re: [Manycouches] AD review: draft-ietf-shmoo-rem… Mirja Kuehlewind
- Re: [Manycouches] AD review: draft-ietf-shmoo-rem… John C Klensin
- Re: [Manycouches] AD review: draft-ietf-shmoo-rem… Mirja Kuehlewind
- Re: [Manycouches] AD review: draft-ietf-shmoo-rem… Lars Eggert
- Re: [Manycouches] AD review: draft-ietf-shmoo-rem… Michael Richardson
- Re: [Manycouches] AD review: draft-ietf-shmoo-rem… Lars Eggert