Re: Registration details for IETF 108

JORDI PALET MARTINEZ <> Mon, 01 June 2020 19:13 UTC

Return-Path: <>
Received: from localhost (localhost []) by (Postfix) with ESMTP id 4BA433A14D3 for <>; Mon, 1 Jun 2020 12:13:38 -0700 (PDT)
X-Virus-Scanned: amavisd-new at
X-Spam-Flag: NO
X-Spam-Score: -0.024
X-Spam-Status: No, score=-0.024 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, LOTS_OF_MONEY=0.001, SPF_HELO_NONE=0.001, URIBL_BLOCKED=0.001] autolearn=no autolearn_force=no
Authentication-Results: (amavisd-new); dkim=pass (1024-bit key)
Received: from ([]) by localhost ( []) (amavisd-new, port 10024) with ESMTP id nOw27qBoI4UT for <>; Mon, 1 Jun 2020 12:13:36 -0700 (PDT)
Received: from ( [IPv6:2001:470:1f09:495::5]) by (Postfix) with ESMTP id C50953A14D1 for <>; Mon, 1 Jun 2020 12:13:35 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=simple;; s=MDaemon; t=1591038814; x=1591643614;; q=dns/txt; h=User-Agent:Date: Subject:From:To:Message-ID:Thread-Topic:References:In-Reply-To: Mime-version:Content-type:Content-transfer-encoding; bh=THQTEvOs pD5qteX0a7/cvugoxxxocVP/dRK43fVA6co=; b=ISD/TW4HfkHsRdNIUc2LF2Y4 MwaCP7Dbucfdm8OBE8BI3qTmk1dYVDmFRE9ZtONRmbhjjYzwtnM/ZNGgI3Uva8yt Prup6D7GpJs3ec80mRPWqUoC+0LEuyLmilRK4hRwvGYkLy0wGktE2jCgtGfTT1sd WMFX/wrITZ1bMwMrAWY=
X-MDAV-Result: clean
X-MDAV-Processed:, Mon, 01 Jun 2020 21:13:34 +0200
X-Spam-Processed:, Mon, 01 Jun 2020 21:13:33 +0200
Received: from [] by (MDaemon PRO v16.5.2) with ESMTPA id md50000191244.msg for <>; Mon, 01 Jun 2020 21:13:33 +0200
X-MDRemoteIP: 2001:470:1f09:495:55b5:12fb:6700:3aa
X-MDHelo: []
X-MDArrival-Date: Mon, 01 Jun 2020 21:13:33 +0200
User-Agent: Microsoft-MacOutlook/16.37.20051002
Date: Mon, 01 Jun 2020 21:13:31 +0200
Subject: Re: Registration details for IETF 108
To: IETF <>
Message-ID: <>
Thread-Topic: Registration details for IETF 108
References: <> <> <> <> <> <> <>
In-Reply-To: <>
Mime-version: 1.0
Content-type: text/plain; charset="UTF-8"
Content-transfer-encoding: quoted-printable
Archived-At: <>
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: IETF-Discussion <>
List-Unsubscribe: <>, <>
List-Archive: <>
List-Post: <>
List-Help: <>
List-Subscribe: <>, <>
X-List-Received-Date: Mon, 01 Jun 2020 19:13:38 -0000

Exactly. As I mention in my previous email, this is not really about "this" meeting, it is about next meetings (in person and online, with and without Covid19), it is about how to cover *all* our expenses.

It is unfair that people that contributes more, pay traveling expenses and attendance fees, and may have similar problems to cover all that cost as people that is participating remotely, which only will need to pay for a registration fee.

How we compensate all the people that have attended meetings for tens of years? In my own case my first meeting was summer 2001, and I never missed one, so I've contributed with about 34.000 USD (just in attendance fees!). For an individual or an SME, this is not the same as for a participant that works for a medium or big size organization, that is covering all the expenses for him/her.

So, this is a discussion about IETF budged in general. It is about what the PIR/.org was created for (cover IETF costs), and if this is sufficient to fund *all the IETF* costs, and reduce the meeting fees for *all* to a very minimum, for both, in-person and online meetings/participants, may be considering what "backup" participants from big organizations have (or as an alternative, providing 1-2 free registration or very low cost fees for each organization and then increase the cost for others, etc.). There are many ways to do that and be fair with people that is contributing vs only "attending".


El 1/6/20 17:40, "ietf en nombre de Bob Hinden" < en nombre de> escribió:


    I think the issue here is that we are now charging for something we didn’t before.  That is, we allowed remote participation at IETF meetings without a fee unto and including IETF 107.   As Brian points out, this change in policy was done with out any discussion.

    I also note that everything we do in the IETF has a cost to it.  Every email, internet draft, submission to the IESG, working group charter, IETF tool, etc., etc.  We can see all these costs in the IETF LLC budget.    None of it is free.

    The question is which of these do we charge for?    According the budget at:

    the non-meeting operating expenses are about $5.1 million per year.   Even the meeting revenue (including registration fees) doesn’t cover all of the meeting expenses.   That is, $3.8M revenue vs. $4.1M costs.

    How do we decide what to charge for?   What is the policy?

    Also, what does the budget look like without face to face meetings?


    > On Jun 1, 2020, at 8:07 AM, Livingood, Jason <> wrote:
    > It's interesting that the issue has been framed as a new fee will be charged to participate in an IETF meeting. But there's been a fee to attend an IETF meeting for as long as I've participated in the IETF. I might suggest that another way of considering this is that the typical meeting fee is being discounted for the virtual meeting.
    > Jason
    > (not speaking for the IETF LLC - personal view)
    > On 6/1/20, 8:39 AM, "ietf on behalf of Suresh Krishnan" < on behalf of> wrote:
    >    +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 <> 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 < <>> 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.

IPv4 is over
Are you ready for the new Internet ?
The IPv6 Company

This electronic message contains information which may be privileged or confidential. The information is intended to be for the exclusive use of the individual(s) named above and further non-explicilty authorized disclosure, copying, distribution or use of the contents of this information, even if partially, including attached files, is strictly prohibited and will be considered a criminal offense. If you are not the intended recipient be aware that any disclosure, copying, distribution or use of the contents of this information, even if partially, including attached files, is strictly prohibited, will be considered a criminal offense, so you must reply to the original sender to inform about this communication and delete it.