Re: Registration details for IETF 108
Eric Rescorla <ekr@rtfm.com> Sun, 31 May 2020 21:14 UTC
Return-Path: <ekr@rtfm.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 10D943A0A3C for <ietf@ietfa.amsl.com>; Sun, 31 May 2020 14:14:40 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.077
X-Spam-Level:
X-Spam-Status: No, score=0.077 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DEAR_SOMETHING=1.973, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, HTML_MESSAGE=0.001, SPF_HELO_NONE=0.001, SPF_NONE=0.001, URIBL_BLOCKED=0.001] autolearn=no autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=rtfm-com.20150623.gappssmtp.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 SI0vW80iKZRF for <ietf@ietfa.amsl.com>; Sun, 31 May 2020 14:14:34 -0700 (PDT)
Received: from mail-lj1-x231.google.com (mail-lj1-x231.google.com [IPv6:2a00:1450:4864:20::231]) (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 188A63A0A3B for <ietf@ietf.org>; Sun, 31 May 2020 14:14:34 -0700 (PDT)
Received: by mail-lj1-x231.google.com with SMTP id s1so5729785ljo.0 for <ietf@ietf.org>; Sun, 31 May 2020 14:14:34 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=rtfm-com.20150623.gappssmtp.com; s=20150623; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=/BRHvU6bLE66CGi487DHZ40YFloI5FVwx+WY/PRMXwk=; b=QDabJ0VcNbu5tu6DG2faKTojFTxeUl18AcvQhXdHTXaLMuEx+j4B4a0I0DrPkYMGT+ ELcCTkiIWLU42XKDVkZ3JrwuceHgzFuobVpjdpT0EiEB0FTz8QFCgxXt9qhHTr9BCeV3 f8HcT/yF0ueYOb8PT/xEgj8yx6w3cyLLeb/A8K9lDTJqUOFfc/s+9gXQwfctlmujngv1 z7lbdWlDCJ9svuqya9S+8j2LQUrgVum7VFuPOjNCHNNIOhh7NqPMNY5nEBkMkx/Hcgju KnkSZJt8Qq3L7q9IkTWDENjd9ULmKMh0VEbCIPKIxnJDmIbvsQr8k8h68tNX65KxSxQ8 +kcA==
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=/BRHvU6bLE66CGi487DHZ40YFloI5FVwx+WY/PRMXwk=; b=GtB4vYYh/tvo0S1R85uM/J7Y9GrsnYj0ZRI3+N7xbIherkg+efqwv0KrtHSSkj7BVv n7eo0iyOWafTYX6sgnXIrVK3sGpMFtQNN6q24WZ5hSKAVRkarQrMWebC6JZB/H89aAGj 9YSWDjjuN4ZuZqpKEdZFbm+9bcFYdoB/PAMXqUEMq0D5w+bEK3naTPgEZRcA+tGaX8MM zgBX5mOV/4BSpTfJCS2B927h/n/VJuQ35hQfKYDjH2WeBZrfDRRTv1sTlwQZG6TMq/kv jsB9Pg5ujuuRgw4F3Cq3TPEXgH7SD+5EX1QFGlLYpRJHZaIn/JxgJ5UdYpg2feJDhKNC lQnA==
X-Gm-Message-State: AOAM531OjOvvQf2r8jpQsBHb0FKO0MH1bnGA75CSD/n0rj96h7ub6nAp St0fnos7A6cq5Y950PER/CQnmwKVzOk9UDNoe2OKX7lr498=
X-Google-Smtp-Source: ABdhPJzfxL1F1sjJiZKtWC6rhKYc2an047IRsdtHtLsWmSIyoU+TOqs9t8uScG4yh2JoCCknL3JP14dumNN7eGkOOks=
X-Received: by 2002:a2e:8897:: with SMTP id k23mr9042002lji.184.1590959671996; Sun, 31 May 2020 14:14:31 -0700 (PDT)
MIME-Version: 1.0
References: <159062833754.6110.5826748635235943562@ietfa.amsl.com> <6.2.5.6.2.20200531121457.0b249858@elandnews.com>
In-Reply-To: <6.2.5.6.2.20200531121457.0b249858@elandnews.com>
From: Eric Rescorla <ekr@rtfm.com>
Date: Sun, 31 May 2020 14:13:55 -0700
Message-ID: <CABcZeBOzVHaSZa0A3eDz12RwNuCiHtiJL8wqvAhhLPN6YEQOkQ@mail.gmail.com>
Subject: Re: Registration details for IETF 108
To: S Moonesamy <sm+ietf@elandsys.com>
Cc: IETF discussion list <ietf@ietf.org>
Content-Type: multipart/alternative; boundary="0000000000001a063605a6f82ad6"
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/MpXaBuGjGrfu9iiMgyYrJ-EzG-Y>
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: Sun, 31 May 2020 21:14:40 -0000
On Sun, May 31, 2020 at 1:56 PM S Moonesamy <sm+ietf@elandsys.com> wrote: > Dear Internet Engineering Steering Group, > > [Reply-To override] > > At 06:12 PM 27-05-2020, IETF Executive Director wrote: > >This meeting will have a substantial agenda but as the cost of an > >online meeting is lower, the registration fees have been set at > >approximately one-third of those for an in-person meeting. A > >detailed explanation of why we charge a fee for meetings and how the > >fee reduction was set for IETF 108 is provided in a separate blog post > [3]. > > In 2013, the IETF Chair affirmed that the Internet Engineering Task > Force embraced the modern paradigm for standards. One of the points > in the document is the standards process being open to all interested > and informed parties. If I recall correctly, I raised a point a few > months before 2013 about the IETF allowing free access to its > meetings through the Internet. I could not help noticing that there > is now a required fee to access the next IETF meeting. Was that > approved by the IESG? > > I took a look at the meeting policy for the IETF. I never understood > why that policy is described as an ambition. Anyway, as that policy > does not specify anything about changing the existing practice for > fees, it is unlikely that the decision to charge for online meetings > can be challenged. > > I would like to thank the IETF LLC Directors for acknowledging that > the fee presents a barrier to participation and their charitable > offer. I'll leave the charitable offer to those who are in need. > > It took a decade for the IETF to take this pay-to-play decision. Was > there any discussion about it? > I don't think the characterization of this as "pay-to-play" is accurate. You are certainly free to participate in mailing lists, github, etc. What is being charged here is a fee to participate [0] in real-time virtual meetings, just as there is one charged for attending in-person meetings. -Ekr [0] I emphasize "real-time" as I expect that the recordings will be available after the fact as usual.
- Re: Registration details for IETF 108 Brian E Carpenter
- Re: Registration details for IETF 108 S Moonesamy
- Re: Registration details for IETF 108 Eric Rescorla
- Re: Registration details for IETF 108 Joel M. Halpern
- Re: Registration details for IETF 108 Melinda Shore
- Re: Registration details for IETF 108 S Moonesamy
- Re: Registration details for IETF 108 Brian E Carpenter
- Re: Registration details for IETF 108 Stephen Farrell
- Re: Registration details for IETF 108 Brian E Carpenter
- Re: Registration details for IETF 108 Alissa Cooper
- Re: Registration details for IETF 108 Alissa Cooper
- Re: Registration details for IETF 108 S Moonesamy
- Re: Registration details for IETF 108 Brian E Carpenter
- Re: [Ietf108planning] Registration details for IE… JORDI PALET MARTINEZ
- Re: Registration details for IETF 108 JORDI PALET MARTINEZ
- Re: Registration details for IETF 108 S Moonesamy
- Re: Registration details for IETF 108 tom petch
- Re: Registration details for IETF 108 Suresh Krishnan
- Re: Registration details for IETF 108 Livingood, Jason
- Re: Registration details for IETF 108 Livingood, Jason
- Re: Registration details for IETF 108 Bob Hinden
- Re: Registration details for IETF 108 Ole Jacobsen
- Re: Registration details for IETF 108 Lixia Zhang
- Re: Registration details for IETF 108 Scott Kitterman
- Re: Registration details for IETF 108 Robert Raszuk
- Re: Registration details for IETF 108 John C Klensin
- Re: Registration details for IETF 108 Michael StJohns
- Re: Registration details for IETF 108 Vittorio Bertola
- Re: Registration details for IETF 108 Joseph Touch
- Re: Registration details for IETF 108 John Scudder
- Re: Registration details for IETF 108 Vittorio Bertola
- Re: Registration details for IETF 108 Joseph Touch
- Re: Registration details for IETF 108 Colin Perkins
- RE: Registration details for IETF 108 Larry Masinter
- Re: Registration details for IETF 108 John C Klensin
- Re: Registration details for IETF 108 JORDI PALET MARTINEZ
- Re: Registration details for IETF 108 Joseph Touch
- Re: Registration details for IETF 108 Behcet Sarikaya
- Re: Registration details for IETF 108 Andrew Sullivan
- Re: Registration details for IETF 108 John C Klensin
- Re: Registration details for IETF 108 Jay Daley
- Re: Registration details for IETF 108 Jay Daley
- RE: Registration details for IETF 108 Adrian Farrel
- Re: Registration details for IETF 108 Jay Daley
- Re: Registration details for IETF 108 Stephen Farrell
- Re: Registration details for IETF 108 Jay Daley
- Re: Registration details for IETF 108 Stephen Farrell
- Re: Registration details for IETF 108 John Levine
- Re: Registration details for IETF 108 S Moonesamy
- Re: Registration details for IETF 108 Jay Daley
- RE: Registration details for IETF 108 Mehmet Ersue
- Re: Registration details for IETF 108 Eric Rescorla
- Re: Registration details for IETF 108 Nick Hilliard
- Re: Registration details for IETF 108 Eric Rescorla
- Re: Registration details for IETF 108 Stephen Farrell
- Re: Registration details for IETF 108 John Levine
- Re: Registration details for IETF 108 Phillip Hallam-Baker
- Re: Registration details for IETF 108 Phillip Hallam-Baker
- Re: Registration details for IETF 108 Spencer Dawkins at IETF
- Re: Registration details for IETF 108 Phillip Hallam-Baker
- Re: Registration details for IETF 108 S Moonesamy
- Re: Registration details for IETF 108 Ted Hardie
- Re: Registration details for IETF 108 Stephen Farrell
- Re: Registration details for IETF 108 Pete Resnick
- Re: Registration details for IETF 108 Jay Daley
- Re: Registration details for IETF 108 Ted Hardie
- Re: Registration details for IETF 108 Ted Hardie
- Re: Registration details for IETF 108 Stephen Farrell
- Re: Registration details for IETF 108 Pete Resnick
- Fees after IETF 108 [Registration details for IET… Brian E Carpenter
- Re: Registration details for IETF 108 Ted Hardie
- Re: Registration details for IETF 108 Ted Hardie
- Re: Registration details for IETF 108 Stephen Farrell
- Re: Registration details for IETF 108 Ted Hardie
- Re: Registration details for IETF 108 Stephen Farrell
- Fees after IETF 108 [Registration details for IET… Brian E Carpenter
- Re: Fees after IETF 108 [Registration details for… Brian E Carpenter
- Re: Fees after IETF 108 [Registration details for… Joel M. Halpern
- Re: Fees after IETF 108 [Registration details for… Robert Raszuk
- Re: Fees after IETF 108 [Registration details for… Joel M. Halpern
- Re: Fees after IETF 108 [Registration details for… Robert Raszuk
- Re: Fees after IETF 108 [Registration details for… Joel M. Halpern
- Re: Fees after IETF 108 [Registration details for… Alissa Cooper
- Re: Registration details for IETF 108 S Moonesamy
- Re: Registration details for IETF 108 Ted Hardie
- Re: Fees after IETF 108 [Registration details for… Ted Hardie
- Re: Fees after IETF 108 [Registration details for… Brian E Carpenter
- Re: Registration details for IETF 108 S Moonesamy
- Re: Fees after IETF 108 [Registration details for… Phillip Hallam-Baker
- Re: Fees after IETF 108 [Registration details for… tom petch
- Re: Registration details for IETF 108 Tim Chown
- Re: Registration details for IETF 108 Nick Hilliard
- Re: Registration details for IETF 108 tom petch
- Re: Registration details for IETF 108 Randy Bush
- Re: Registration details for IETF 108 Robert Raszuk
- Re: Registration details for IETF 108 Brian E Carpenter
- Re: Registration details for IETF 108 Randy Bush
- Re: Registration details for IETF 108 Bajpai, Vaibhav
- Re: Registration details for IETF 108 Daniel Karrenberg
- Re: Registration details for IETF 108 Tim Chown
- Re: Registration details for IETF 108 Randy Bush
- Re: Registration details for IETF 108 Colin Perkins
- Re: Registration details for IETF 108 Tim Chown
- Re: Registration details for IETF 108 Randy Bush
- Re: Registration details for IETF 108 Jay Daley
- RE: Registration details for IETF 108 Larry Masinter
- RE: Registration details for IETF 108 John C Klensin
- Re: Registration details for IETF 108 Randy Bush
- RE: Registration details for IETF 108 Larry Masinter
- Re: Registration details for IETF 108 Ole Jacobsen
- Re: Registration details for IETF 108 Michael Richardson
- Re: Registration details for IETF 108 Michael Richardson
- RE: Registration details for IETF 108 Larry Masinter
- standards? (was: Registration details for IETF 10… Randy Bush
- Re: standards? (was: Registration details for IET… Phillip Hallam-Baker
- Re: standards? (was: Registration details for IET… Michael Richardson
- Re: standards? (was: Registration details for IET… Phillip Hallam-Baker