Re: Registration details for IETF 108

JORDI PALET MARTINEZ <jordi.palet@consulintel.es> Mon, 01 June 2020 06:55 UTC

Return-Path: <prvs=142140f461=jordi.palet@consulintel.es>
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 4DEEF3A0D77 for <ietf@ietfa.amsl.com>; Sun, 31 May 2020 23:55:13 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.998
X-Spam-Level:
X-Spam-Status: No, score=-1.998 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, SPF_HELO_NONE=0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=consulintel.es
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 8vy7T6BY9UKT for <ietf@ietfa.amsl.com>; Sun, 31 May 2020 23:55:12 -0700 (PDT)
Received: from mail.consulintel.es (mail.consulintel.es [IPv6:2001:470:1f09:495::5]) by ietfa.amsl.com (Postfix) with ESMTP id A87883A0D74 for <ietf@ietf.org>; Sun, 31 May 2020 23:55:11 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=simple; d=consulintel.es; s=MDaemon; t=1590994510; x=1591599310; i=jordi.palet@consulintel.es; 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=QoW7gw6a yBBlKwWN9yHYuaL6ISgd81RSxoEh0PxqA3M=; b=PdmHJth6cWmi/6d1eFF3W1cB +ZwRZd15nHDrrN5KeCXKPIWIjyoebli6hYXuDxkz/zju2s9tjJdMP2iqKbXoiAVk SA+nPeT+euaaHmy9CmLnn3GZxXSvl36HyhhnnShI0afUP3cKX7o9IPmHYaqe4Dkh u1nGet78WSdMUFcMeY0=
X-MDAV-Result: clean
X-MDAV-Processed: mail.consulintel.es, Mon, 01 Jun 2020 08:55:10 +0200
X-Spam-Processed: mail.consulintel.es, Mon, 01 Jun 2020 08:55:10 +0200
Received: from [10.10.10.145] by mail.consulintel.es (MDaemon PRO v16.5.2) with ESMTPA id md50000189993.msg for <ietf@ietf.org>; Mon, 01 Jun 2020 08:55:10 +0200
X-MDRemoteIP: 2001:470:1f09:495:d547:7a0d:6390:20cd
X-MDHelo: [10.10.10.145]
X-MDArrival-Date: Mon, 01 Jun 2020 08:55:10 +0200
X-Authenticated-Sender: jordi.palet@consulintel.es
X-Return-Path: prvs=142140f461=jordi.palet@consulintel.es
X-Envelope-From: jordi.palet@consulintel.es
X-MDaemon-Deliver-To: ietf@ietf.org
User-Agent: Microsoft-MacOutlook/16.37.20051002
Date: Mon, 01 Jun 2020 08:55:06 +0200
Subject: Re: Registration details for IETF 108
From: JORDI PALET MARTINEZ <jordi.palet@consulintel.es>
To: <ietf@ietf.org>
Message-ID: <377DFD4C-F43C-425A-8C48-66CABD1BD0AE@consulintel.es>
Thread-Topic: Registration details for IETF 108
References: <159062833754.6110.5826748635235943562@ietfa.amsl.com> <6.2.5.6.2.20200531121457.0b249858@elandnews.com> <CABcZeBOzVHaSZa0A3eDz12RwNuCiHtiJL8wqvAhhLPN6YEQOkQ@mail.gmail.com> <afa11959-3348-4054-409c-803824a2f332@gmail.com> <b31bc70b-cc73-45e4-9449-d85313a88037@gmail.com>
In-Reply-To: <b31bc70b-cc73-45e4-9449-d85313a88037@gmail.com>
Mime-version: 1.0
Content-type: text/plain; charset="UTF-8"
Content-transfer-encoding: quoted-printable
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/wBHfX4D8iQRT7KkA7LZOMN4stXc>
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 06:55:13 -0000

I think one of those additional questions is:

Are authors of documents being presented, able to participate at no cost, at least in the relevant WGs?

I fully understand that our consensus decisions are taken in the list but meetings provide a better venue for discussing the documents, as some times, discussion only happens with the presentation. I'm not saying this is right, however, is the reality.

Regards,
Jordi
@jordipalet
 
 

El 1/6/20 0:34, "ietf en nombre de Brian E Carpenter" <ietf-bounces@ietf.org en nombre de brian.e.carpenter@gmail.com> escribió:

    On 01-Jun-20 09:44, Melinda Shore wrote:
    > On 5/31/20 1:13 PM, Eric Rescorla wrote:
    >> 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.
    > 
    > I'm somewhat troubled by this, as well, tbh.  

    What troubles me is the lack of a debate in the community before this
    was announced with about a week's notice.

    For my own part, I have no idea whether I would have to pay this out
    of my own pocket or not, and determining that would take more rounds of
    email than can happen before registration opens. Since this isn't a
    travel-related fee, the procedures many of us are used to for meeting
    fees don't apply. I'm very much aware that this is the new normal,
    but it's going to take a while for employers' approval procedures to
    catch up. How many people will be excluded for that reason?

    It probably doesn't matter in my case since the announced timezone
    for the meeting rules it out anyway, but as a matter of principle,
    we haven't had a debate about the principle, and that seems wrong.
    For example, 

    1) Is listen-only attendance charged the same fee as listen-and-speak?
    If so, is that right or wrong?

    2) Why is there a late fee? It's not as if extra cookies have to
    be bought at the last minute.

    And I'm sure there are other questions.

       Brian

    > To the extent that
    > the IETF has gradually and effectively moved to having decisions
    > made in meetings it would be unfortunate indeed to exclude
    > people based on financial circumstances.  I'd like to see the
    > decision-making situation fixed but given the history of that
    > discussion I think we are where we are, and free remote participation
    > provides at least some mitigation.  I also tend to think that
    > saying that meeting participation isn't necessary because {mailing
    > lists,Github,whatever} is incompatible with the insistence that
    > the IETF continue to meet because it's not really possible to
    > progress work without real-time discussion.  I'll also note that
    > for as long as there's been a remote participation option available
    > it's been free.  We're now in the odd position of having all-remote
    > meetings absorb what used to be "remote participants" into the
    > group of "participants," with some consequential side-effects
    > (although arguably there are no such things as side-effects, just
    > effects).
    > 
    > I do think this decision has some unintended consequences.
    > Scholarships or other subsidy might provide some mitigation
    > but would potentially be messy/awkward.  The organization
    > is long overdue for some navel-gazing about working methods.
    > It's unreasonable to expect perfect consistency but I think
    > things have gotten a little more incoherent than they should
    > be.
    > 
    > Melinda
    > 




**********************************************
IPv4 is over
Are you ready for the new Internet ?
http://www.theipv6company.com
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.