Re: Registration details for IETF 108

Suresh Krishnan <suresh.krishnan@gmail.com> Mon, 01 June 2020 12:38 UTC

Return-Path: <suresh.krishnan@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 6CCAD3A0FFE for <ietf@ietfa.amsl.com>; Mon, 1 Jun 2020 05:38:42 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.125
X-Spam-Level:
X-Spam-Status: No, score=-0.125 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DEAR_SOMETHING=1.973, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, FREEMAIL_FROM=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-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=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 uvcMxHUCXHAY for <ietf@ietfa.amsl.com>; Mon, 1 Jun 2020 05:38:41 -0700 (PDT)
Received: from mail-qv1-xf34.google.com (mail-qv1-xf34.google.com [IPv6:2607:f8b0:4864:20::f34]) (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 279DF3A0FFC for <ietf@ietf.org>; Mon, 1 Jun 2020 05:38:41 -0700 (PDT)
Received: by mail-qv1-xf34.google.com with SMTP id er17so1627094qvb.8 for <ietf@ietf.org>; Mon, 01 Jun 2020 05:38:41 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:subject:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to; bh=voaJRnnZSN2HoMqA/RNxQmkQtJPcx4ejwsa3HvVC0Ug=; b=MQbnq8P47Ny9v5WnjSeRgZ2Zs9c8lwEGvoE1kgmPR3jn/c1T4DdeJLAxxQGVTZzuyv aCenHRj0qVpP1vwXqVtve3/UnfMoST+lSOz2I/0Ie3fDfUlLlSVSuerhn3hRFzMzdHHT SqWY4MT8DExBwzzUHMZDSLbipRTMYcfcjb1Wsh5ekbZmUaPB88IkFck/PK08yApY6Sfp xZchiQvL8cPDaIy5uNq0uu/jpUPg8MYnFiuZbACy61QxU7SLnVYjx78TphXyKYL/ID5U RAbw5pQOgRBZHQHw5j+GLorI4iGQWN6V6HDSJ3HqHaqEtPLx0Lh6rVNwFZaIsBd2KBL0 dpyQ==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:subject:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to; bh=voaJRnnZSN2HoMqA/RNxQmkQtJPcx4ejwsa3HvVC0Ug=; b=rLAVNhXJg9rJZrfwO1jIwIXPh4qcnzNsL5lDlYOQOgGtQlod0/cXYINHYv1BkSwj/4 NkkQAc8CC9xj5GIFBzl10I52LYO/XR9ma/6q6OwZPYNt7ov0CwjadfAlgR7/6CZRDBsW nStflN3Ntq3m7oii1kDyM7YBREvl+AD3PIdUh3Kf/XniHMoA9g4KcmZP9Ow7st4Hd5P4 3ZRfy8J948pih0c2Kl/UmyITZbwRRH5YYJ/HIQt3SYdup+H0/sDKhcxqOGF+t7ZhVY6C x+NEUultQafUnBp1cjWR+P1+xpS8pnXViM+oXKsosUqulIRxLmHSscdvU2Ob7NK4Co2g yBaw==
X-Gm-Message-State: AOAM533ttRuU2zW9/IsR9czOOzOux6tcnWbRRGfE21s+vuxXXqva0nL7 FV9Dfj8je3OxTGPQqrO8kL+oIdYP
X-Google-Smtp-Source: ABdhPJyxjUdAZNbnD8iv5zOofHzsyoc8VcqmedpFJuIR4w5+hIzqwZwhkX6fKHgLn9kCqjUAe42enQ==
X-Received: by 2002:a05:6214:852:: with SMTP id dg18mr153399qvb.97.1591015120013; Mon, 01 Jun 2020 05:38:40 -0700 (PDT)
Received: from [10.0.0.14] (45-19-110-76.lightspeed.tukrga.sbcglobal.net. [45.19.110.76]) by smtp.gmail.com with ESMTPSA id v53sm15199745qtv.10.2020.06.01.05.38.38 (version=TLS1_2 cipher=ECDHE-ECDSA-AES128-GCM-SHA256 bits=128/128); Mon, 01 Jun 2020 05:38:38 -0700 (PDT)
Content-Type: text/plain; charset=us-ascii
Mime-Version: 1.0 (Mac OS X Mail 13.4 \(3608.80.23.2.2\))
Subject: Re: Registration details for IETF 108
From: Suresh Krishnan <suresh.krishnan@gmail.com>
In-Reply-To: <3f9a0e50-c01b-01c6-ad52-95f370baeb8d@joelhalpern.com>
Date: Mon, 1 Jun 2020 08:38:38 -0400
Cc: S Moonesamy <sm+ietf@elandsys.com>, IETF discussion list <ietf@ietf.org>
Content-Transfer-Encoding: quoted-printable
Message-Id: <B71999A2-3EC6-4649-864F-674BA494B511@gmail.com>
References: <159062833754.6110.5826748635235943562@ietfa.amsl.com> <6.2.5.6.2.20200531121457.0b249858@elandnews.com> <CABcZeBOzVHaSZa0A3eDz12RwNuCiHtiJL8wqvAhhLPN6YEQOkQ@mail.gmail.com> <3f9a0e50-c01b-01c6-ad52-95f370baeb8d@joelhalpern.com>
To: "Joel M. Halpern" <jmh@joelhalpern.com>
X-Mailer: Apple Mail (2.3608.80.23.2.2)
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/YGVlKSFwq9Ov-5xbo980j0NuTUs>
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, 01 Jun 2020 12:38:43 -0000

+1. I think this is a reasonable decision and allows people to participate without financial barriers, while allowing the ongoing activities funded by IETF meeting fees to proceed without interruption.

Regards
Suresh

> On May 31, 2020, at 5:24 PM, Joel M. Halpern <jmh@joelhalpern.com> wrote:
> 
> I agree with Eric in his description.  From where I sit, this seems a reasonable decision by the leadership.
> 
> Yours,
> Joel
> 
> On 5/31/2020 5:13 PM, Eric Rescorla wrote:
>> On Sun, May 31, 2020 at 1:56 PM S Moonesamy <sm+ietf@elandsys.com <mailto:sm%2Bietf@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.
>