Re: [Ietf108planning] Registration open for IETF 108

Corinne Cath <corinnecath@gmail.com> Thu, 11 June 2020 10:45 UTC

Return-Path: <cattekwaad@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 02DB63A084D; Thu, 11 Jun 2020 03:45:42 -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 gL8rh6D54GFw; Thu, 11 Jun 2020 03:45:39 -0700 (PDT)
Received: from mail-qt1-x830.google.com (mail-qt1-x830.google.com [IPv6:2607:f8b0:4864:20::830]) (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 A38CE3A0829; Thu, 11 Jun 2020 03:45:35 -0700 (PDT)
Received: by mail-qt1-x830.google.com with SMTP id u17so4196994qtq.1; Thu, 11 Jun 2020 03:45:35 -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=FDRhltmF/+PHiImHET7x0y58osuF7bKM+IixgCkHgdc=; b=BW2G7dCXpUZW1aP2cz2Y2uo2vLpqyAQ3AJ2kzZPi92++b1zbLmQOblCCNHGZuYbzxD 2FKQBgBs0pjl5Ufay33y8uGtqt3deE+rHNqnJez1/46ziUc/eYBixBnRT8kRgGsz3vls +pbC6na+HTPy+Uhc5EBAoPzEWmStSwC5xnsSeAgD0G7Ka1RBOwEGXMGsnZa5ew6gW+Bb 37yXMfNwWDid6sbSBuJteoD5u8ChAi5TR/bdXsvoEEm/caYUxW57e8efXpScWCzB/dQP sKgfwchj2qLS9EEi+COpGEyDy2PQWzkpFE++2aZLWb8iupEsTwTKkBIvPZcePZZ4NP9v TrGg==
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=FDRhltmF/+PHiImHET7x0y58osuF7bKM+IixgCkHgdc=; b=q+H9p3V6vYfVbchMvvx5jnnu2YxW+b5g4G3iI741xPQRnRjwVgEArG3Y8jmp7za5EH A4kNt4uNkDPwyKlNT1mFfQN8isxfPm8dCXIb8aK4kDMXGPxMMxmxK15cKxVy4DvSWCra /aqAcCuDqNXCefxKtU/32T8nsiLUg81ROYHc4GUztpXVHfQZsH3bmft14LIgV+UcIwwN eCwke4pFpidcQ3xWcRjpj8x1JL74evB/1jS0YO6duPiN9EXp7402MMZfhC+nIL4mWkcn j10o9rQivH/2K7BmD4Y7PXtlQCESYHH3dSxKnKctd1hrH2MsGGQUnDu/kuDgJOEpDDAi rh8w==
X-Gm-Message-State: AOAM532f43OTZ2CJh8uW70v10Du7DmCMzEf7e+lv5P0ezOTGcOZUaOg0 VquNvzRmRiOy1XdZCD9Ha0sbcO+eI8FxJM8hTos=
X-Google-Smtp-Source: ABdhPJzFURVu5Q+DZogAwPAmMh9wqWp4UE/YeVrqG2p99NBZN+UIdzBXvSCWdrG62G9b1jcQWtCb77B6dx9pOFV7qg8=
X-Received: by 2002:ac8:3984:: with SMTP id v4mr7969041qte.267.1591872334496; Thu, 11 Jun 2020 03:45:34 -0700 (PDT)
MIME-Version: 1.0
References: <159166311543.4506.736406779378278905@ietfa.amsl.com> <CAFgnS4WOjmNOf_MRfms1RD0e15xYP-xcfNiyqS7p5ofYBEQPdw@mail.gmail.com> <d65a8aeffc61b6d069afa87f3c91b10496c4d5b2.camel@lsl.digital> <5FCC8656386268B41681E1DE@PSB> <B4293B17-6F83-4B9E-89BF-C0B1388F346F@cable.comcast.com> <CABmDk8=gxXiQ60hpdCNB6jK0EG_ssAQnzjgJp=c9yXNKabHKeA@mail.gmail.com> <CABmDk8mwVfWZQmBwZ9c4xaoStwv7CeRRceihTR846iq_LYPFFw@mail.gmail.com> <F6BFB099-2526-4EEB-A267-F2A1D0A7DDFB@cooperw.in> <35fb0076-a240-096a-de7f-280d5e7ad1e3@cs.tcd.ie> <2F0FDD2B-03C8-4E76-9149-A2666147C66E@csperkins.org> <27875646-243d-8d03-b588-866b883fea7c@cs.tcd.ie> <8C935847-70C8-439B-8F4C-83DB9A43E4DF@ietf.org> <c1b11160-c50b-9434-6ba8-9ec587a17743@cs.tcd.ie>
In-Reply-To: <c1b11160-c50b-9434-6ba8-9ec587a17743@cs.tcd.ie>
From: Corinne Cath <corinnecath@gmail.com>
Date: Thu, 11 Jun 2020 12:44:57 +0200
Message-ID: <CAD499e+MCvF_D0oTHxi9UfgTRgzcPWrb-qaQNFPZxUeeUodHsg@mail.gmail.com>
Subject: Re: [Ietf108planning] Registration open for IETF 108
To: Stephen Farrell <stephen.farrell@cs.tcd.ie>
Cc: Jay Daley <jay@ietf.org>, ietf <ietf@ietf.org>, "ietf108planning@ietf.org" <ietf108planning@ietf.org>
Content-Type: multipart/alternative; boundary="00000000000006893b05a7cca9db"
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/9lk3YBpuQzWT21TRsOtv8UF3Wlg>
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: Thu, 11 Jun 2020 10:45:42 -0000

Hi all,

Just wanted to add a quick data points to this conversation: as a PhD
student, 200$ is a fifth of the total research + travel budget I get from
my university per year.

In comparison to other universities, I am given a royal research budget.
But giving up 1/5 to attend an online IETF meeting makes a big dent.
Doubly-so because I (and I assume other graduate students) had not planned
for such expenses, given online participation is usually free of cost. If I
am not randomly assigned a waiver, I will probably not be able to attend.

Now I am not under any illusion that my personal attendance (or lack there
off) matters much - however, I know my case (i.e. graduate student on a
limited budget) is not unique. And many others like me will struggle to
participate in this meeting because of the unexpected costs. This is not
even including what the online fee means for some of my colleagues working
in academia or for civil society in the Global South.

I agree with Stephen that this step might be hard to avoid, but that it
would benefit from robust community debate beforehand. I also agree with
Melinda that this is a real move away from the openness from which the IETF
derives its legitimacy. And while the recordings will be available to all
post-meeting, this is not a substitute for open attendance.

Kind regards,

Corinne



On Thu, Jun 11, 2020 at 12:39 PM Stephen Farrell <stephen.farrell@cs.tcd.ie>
wrote:

>
> Hiya,
>
> On 11/06/2020 03:21, Jay Daley wrote:
>
> > As well as stating that you see this a switch from a zero to non-zero
> > fee, I think you’ve also stated that such a switch can only be made
> > with community consensus.
>
> Rough consensus, yes. I doubt it could be other, in this
> case. (Along the lines of rfc7282.) There are many reasons,
> minimally because it affects the standards process in a
> lot of ways.
>
> > Given that you and some others firmly
> > oppose this switch
>
> You may consider that you know what outcome I want. In
> fact I do not think that I know the answer here, but I
> do know it affects the standards process and so needs
> a debate before a change is made, except in an emergency
> as happened with IETF 107. (I will say that I'm fairly
> convinced that charging to join tens of hours of calls
> during one week a few times a year is not likely to be
> sustainable.)
>
> I just re-read your blog, and while that is convincing
> that we need to change how the IETF is funded, it does
> not make the case that we need to do that in emergency mode,
> for IETF108, without community involvement.
>
> The blog also does not say that policies about fees that
> have an effect on the standards process need to be decided
> by the community and not the LLC. I hope you do share that
> last opinion. (You may notice that I haven't once mentioned
> the numeric amounts that are proposed to be imposed here
> for example, so I'm not trying to haggle for a cheaper phone
> call experience:-)
>
> > it would seem that community consensus could not
> > be achieved within the necessary timeframe to make such as switch for
> > IETF 108, if at all, no matter what process was used to try to find
> > consensus.  That would then mean that if your initial premise is
> > accepted, IETF 108 would have to have a zero fee for all, no choice
> > in the matter.
>
> If there is no emergency need to change the funding model
> for IETF108, then the status quo ante is the right position
> until there has been a debate at least. (I do agree that
> we probably can't wait a full year for an outcome from that
> debate. I do not agree that "we haven't time to talk" is a
> sufficient excuse for imposing fees for remote registration.)
>
> If there is an emergency for IETF108 then that needs to be
> stated clearly and that the arrangements imposed will not
> apply to future meetings before the community get to debate
> matters. (Or similar.)
>
> > Do you agree with that so far or is there a way, hypothetical of
> > course, that you could see the switch happening in the face of some
> > determined opposition?
>
> Determined opposition is not how I would frame this. I
> think you're again assuming you know what outcome I want.
>
> > Starting from the same uncontentious statement that "in-person
> > meetings have a non-zero fee for in-person participation while
> > remote-only participation has a zero fee", the alternative view
>
> There are many alternatives to the historic funding model, not
> just one, which is what's implied by "the alternative." That
> flaw in the argument seems to affect most of the text below, so
> I won't try blow-by-blow answers.
>
> > is
> > that moving to a fully online meeting does not simply delete the
> > first clause of that statement to leave only the second clause and so
> > conclude that as everyone is now remote-only, everyone should have a
> > zero fee.  To put it another way, the alternative view says that
> > there is no community consensus that tells us what to do with that
> > statement in the event of moving to a fully online meeting.
>
> There may be rough consensus in the community for something. We
> do not know as people have not been asked to debate it. (A
> survey does not count, though does provide some input.) The
> "something" for which there may be consensus e.g. might not be
> a specific billing model, but rather some principles that
> could be met in various ways, and that could allow for various
> experiments in adapting as the situation changes. I do think
> it may be feasible to establish some such principles on which
> we could reach rough consensus in a relatively short time.
> Trying to reverse engineer such principles from an imposed or
> proposed billing model seems like a bad plan to me.
>
> > Again, a check-in - are we still on the same page in describing this
> > alternative view so far?
>
> No. Your assumption that you know what outcome I want is
> incorrect and I don't agree that there is one singular
> "alternative view."
>
> > The next stage to the alternative view, is to interpret that
> > uncontentious statement in the context of a fully online meeting as
> > saying "there is a fee to participate in a meeting, with a mechanism
> > for those that cannot afford it to still participate".  If one
> > accepts that interpretation, as the IESG and LLC do, then it is
> > possible to discuss what that fee should be, what the mechanism
> > should be for supporting those who cannot afford it, etc.
>
> In logic, false => anything, so I'm not sure that's a good
> starting point.
>
> >
> > Having said that, there are other interpretations out there, such as
> > "there is a non-zero fee for fully featured participation, while
> > reduced feature participation has a zero fee’.  While I don’t
> > agree with that as an interpretation, it also allows for a debate on
> > various aspects of the overall construct.
> >
> >
> > A final question for you - if the IESG/LLC had had the time to open
> > up a debate/discussion on this and the IESG/LLC had gone ahead with
> > this despite your opposition, would we be anywhere different from
> > where we are now?
>
> Yes. (Bearing in mind that I don't accept your premises, but
> won't repeat all that.)
>
> S.
>
> >
> > Jay
> >
>


-- 
Corinne Cath - Speth
Ph.D. Candidate, Oxford Internet Institute & Alan Turing Institute

Web: www.oii.ox.ac.uk/people/corinne-cath
Email: ccath@turing.ac.uk & corinnecath@gmail.com
Twitter: @C_CS