Re: [Ietf108planning] Registration details for IETF 108
JORDI PALET MARTINEZ <jordi.palet@consulintel.es> Mon, 01 June 2020 06:46 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 0B6AA3A0D6B for <ietf@ietfa.amsl.com>; Sun, 31 May 2020 23:46:52 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.996
X-Spam-Level:
X-Spam-Status: No, score=-1.996 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_MESSAGE=0.001, MIME_QP_LONG_LINE=0.001, 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 gKGUQ91NDMsH for <ietf@ietfa.amsl.com>; Sun, 31 May 2020 23:46:49 -0700 (PDT)
Received: from mail.consulintel.es (mail.consulintel.es [IPv6:2001:470:1f09:495::5]) by ietfa.amsl.com (Postfix) with ESMTP id C4FF93A0D69 for <ietf@ietf.org>; Sun, 31 May 2020 23:46:48 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=simple; d=consulintel.es; s=MDaemon; t=1590994006; x=1591598806; 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; bh=/krlKJ96KHsVjD12PH6OZOg3Wka/br3LhS UeymvYQqE=; b=N9NeQAXgipzFsIsvMePqie98FOGKaHoJtXw6uglCZJ8g/qgaJT NFSKa1llnVX+Ucb7nlBjSFyLQ8/Qw3/pg2Z27BglE2NsaGA8Uz9bYsmeBoktMVdM Wdg3vBoWF9t6YI5DJbyCLzUwOaz8dRL7sEqdxEqLE/XmSZyBsR2q/wCAs=
X-MDAV-Result: clean
X-MDAV-Processed: mail.consulintel.es, Mon, 01 Jun 2020 08:46:46 +0200
X-Spam-Processed: mail.consulintel.es, Mon, 01 Jun 2020 08:46:45 +0200
Received: from [10.10.10.145] by mail.consulintel.es (MDaemon PRO v16.5.2) with ESMTPA id md50000189967.msg for <ietf@ietf.org>; Mon, 01 Jun 2020 08:46:45 +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:46:45 +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:46:41 +0200
Subject: Re: [Ietf108planning] Registration details for IETF 108
From: JORDI PALET MARTINEZ <jordi.palet@consulintel.es>
To: ietf@ietf.org
Message-ID: <56B99F83-FEF0-4ED0-904C-35BE4FEA684C@consulintel.es>
Thread-Topic: [Ietf108planning] Registration details for IETF 108
References: <159062833754.6110.5826748635235943562@ietfa.amsl.com> <6259FFE3-4CC0-4CC6-8FDE-A054687466CF@consulintel.es> <FACC8430-730D-43D1-AEC1-5C5EF0684661@ietf.org>
In-Reply-To: <FACC8430-730D-43D1-AEC1-5C5EF0684661@ietf.org>
Mime-version: 1.0
Content-type: multipart/alternative; boundary="B_3673846001_632576645"
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/DgBYRLObs6ckP7NxK_iSDAlp4ko>
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:46:52 -0000
Moving this to the general mailing list … See below, in-line. El 28/5/20 22:40, "Jay Daley" <jay@ietf.org> escribió: Jordi (As per our side conversation - feel free to move this to ietf@ietf if you prefer) On 28/05/2020, at 10:06 PM, JORDI PALET MARTINEZ <jordi.palet=40consulintel.es@dmarc.ietf.org> wrote: Hi Jay, In my opinion, it has never been fair that remote participants don't contribute with some fee, and I think we should change that and we must have that decision now. For many of us, the Covid-19 is significantly altering our incomes. Yes, we save in traveling costs (if you can recover the flight tickets and hotels pre-paid and non-refundable), which in my own case, finally worked for IETF107. However, I don't think it will work for IETF109 (according to the web sites of hotel chains and flight companies, at the time being, they are only respecting special waivers until end of June), in case it becomes on-line as well. Clearly the fees (not just now) should be somehow proportional to the turnover of the participant companies. It is not the same for an SME to invest in participating in IETF and more specifically in each IETF meeting (wheater is in-person or on-line), versus a medium, small or international organization. That would contradict what I understand to be one of the central principles of the IETF, which is that people participate as individuals and not representatives of their companies. If that’s the way you would like us to go then I think that would require explicit community consensus before we could even begin. Jay So please, re-consider the numbers assuming that not just IETF108, but also IETF109 and probably IETF110 will be on-line and with fees for remote participants in future meetings. Otherwise, the risk for on-line meetings is that participants from SMEs (and those that pay the IETF costs from our own personal pocket) aren't able to keep participating. Regards, Jordi @jordipalet El 28/5/20 3:12, "IETF-Announce en nombre de IETF Executive Director" <ietf-announce-bounces@ietf.org en nombre de exec-director@ietf.org> escribió: As previously announced [1], IETF 108 is switching to a fully online meeting over 5 days, 25-31 July, with an agenda structure similar to that of an in-person meeting [2]. Registrations will open on 8 June 2020 and the registration fees will be as follows: Early-Bird: USD 230, until 26 June 2020 Standard: USD 280, until 20 July 2020 Late: USD 330, after 20 July 2020 Full-time Student: USD 50 One Day Pass: USD 125 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]. As online participants have until now not had to pay a fee, it is recognised that there may be some for whom the fee presents a barrier to participation and so we will provide up to 100 early bird fee waivers for IETF 108. If the number of waiver requests exceeds the number we can offer, waiver recipients will be chosen at random using a process similar to the one specified in RFC 3797. Details of how to apply for a waiver will be provided when registration opens. No decision has been made on whether or not a fee for online participation is needed when we return to in-person meetings. As this is a fully online meeting, there are two key changes in the meeting process for you to be aware of: 1. When you register you will be able to choose if you want to receive an IETF 108 t-shirt delivered to you at no additional expense. Numbers will be limited to 1000 t-shirts on a first-come-first-served basis with 900 for Early Birds and 100 for Students. 2. All participants will need a Datatracker account in order to authenticate with Meetecho. If you do not already have an account then one will be created for you during registration and you will receive a password setup link by email. As with in-person meetings, a video recording of each scheduled session will be posted after the session concludes and the proceedings will be posted in the normal timeframe following the meeting. Finally, we are still in the process of securing sponsors with some generous contributions already agreed and more under discussion. Full details and thanks will follow later. Please feel free to contact me directly if you have any questions or comments. [1] https://mailarchive.ietf.org/arch/msg/ietf-announce/kzC7M48oKrAwdh9uyOvseeKFW3A/ [2] https://www.ietf.org/blog/ietf108-survey-results-informed-planning/ [3] https://www.ietf.org/blog/ietf108-registration-fees -- Jay Daley IETF Executive Director exec-director@ietf.org _______________________________________________ IETF-Announce mailing list IETF-Announce@ietf.org https://www.ietf.org/mailman/listinfo/ietf-announce ********************************************** 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. -- Ietf108planning mailing list Ietf108planning@ietf.org https://www.ietf.org/mailman/listinfo/ietf108planning -- Jay Daley IETF Executive Director jay@ietf.org ********************************************** 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.
- 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