Re: [Ietf108planning] Registration open for IETF 108
tom petch <daedulus@btconnect.com> Fri, 12 June 2020 10:56 UTC
Return-Path: <daedulus@btconnect.com>
X-Original-To: ietf108planning@ietfa.amsl.com
Delivered-To: ietf108planning@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 8A3D93A0F31; Fri, 12 Jun 2020 03:56:20 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.901
X-Spam-Level:
X-Spam-Status: No, score=-1.901 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, MSGID_FROM_MTA_HEADER=0.001, RCVD_IN_MSPIKE_H2=-0.001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=btconnect.onmicrosoft.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 Ea4WWh04kE3f; Fri, 12 Jun 2020 03:56:18 -0700 (PDT)
Received: from EUR02-HE1-obe.outbound.protection.outlook.com (mail-eopbgr10103.outbound.protection.outlook.com [40.107.1.103]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 1E5E53A0ED4; Fri, 12 Jun 2020 03:56:17 -0700 (PDT)
ARC-Seal: i=1; a=rsa-sha256; s=arcselector9901; d=microsoft.com; cv=none; b=a16cNZlw+DhXMCjaKaaNy80lXdmm465z6VLWPTWoXdz4xCayIDIJYyQ4XPxxq95C+SPCJVQ9abGhs0JpD0WaXj9MINmONTET2fEH83tzDEdHYcn1Y8LKFoECIqAjO9VKc6XNR9vOUrl90QTv33cfEFM6V+1BLcjA1Qm3PK7s32L2BRrcQkJdrYSKyV7YRHZRNJ8IJhnhOQ+Z6I2SZ99mkN6qNzZQ4PDHFazpyFMu9s8r/RbFdhudj06QdH2r9aewAXUTxisXQXyh3spFMLJ4fTRjwCZSNje+iOMrBcfFcRXaQEmJTGyctRNPmcV9xG5+SH3h249Q/HbZIHqgiKWaDQ==
ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=microsoft.com; s=arcselector9901; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-SenderADCheck; bh=6XJwaC/7OBFoR/LPwviqORNLHFcrowmzT+PU9o6LoSQ=; b=B1tKKBCO571tlP94+kXbrvfsouq+FrzIV+KTarIa+y7pIV6VISW1UQhFwHdXJZjsNO5GfJ049rlD7C7hxAhowIY1pCd5cgGk8Ks3MA6ifIVBnErCWGUz/1qMWTPvrpUZuLr6jAkA2XVFe5XXQ8nG3pigyVnZ9Q9tSs9k/OwCY6spcZ+0cVq6vykxfxDaFu1O+Gs/nP3oGj+N3PyZ1EeePEHI+lwW4X4VNKr1eK/9rlNvIZR1cqe6vveLaXXbAvS0g2zgC/EYnBvj0rYmvuqjqcc+kZUmgK6zR9I3Um3AOAsklDIiLZoe5Ngi+zhkjUAefGaUbWQZ9Au6aaJbyaFrUA==
ARC-Authentication-Results: i=1; mx.microsoft.com 1; spf=pass smtp.mailfrom=btconnect.com; dmarc=pass action=none header.from=btconnect.com; dkim=pass header.d=btconnect.com; arc=none
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=btconnect.onmicrosoft.com; s=selector2-btconnect-onmicrosoft-com; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-SenderADCheck; bh=6XJwaC/7OBFoR/LPwviqORNLHFcrowmzT+PU9o6LoSQ=; b=w4suSQiALhEeVxt46vz23kDQ94c74k6ViNJudIi60ajFpbP0PtLWcwXdqyd238HJU2aYgXEfybBSBrWmXH0rESLK86uimXA9LzbddUEb91rBSbxRZBmEgK1lVnoAy3olP/o4of4VmU9uwpBYxbMuSIz/QNdAnVu2Sfk4LEU8EJo=
Authentication-Results: ietf.org; dkim=none (message not signed) header.d=none;ietf.org; dmarc=none action=none header.from=btconnect.com;
Received: from VI1PR0701MB2480.eurprd07.prod.outlook.com (2603:10a6:800:63::16) by VI1PR0701MB2656.eurprd07.prod.outlook.com (2603:10a6:801:c::11) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.3088.9; Fri, 12 Jun 2020 10:56:15 +0000
Received: from VI1PR0701MB2480.eurprd07.prod.outlook.com ([fe80::3474:b82e:e75a:b176]) by VI1PR0701MB2480.eurprd07.prod.outlook.com ([fe80::3474:b82e:e75a:b176%11]) with mapi id 15.20.3109.011; Fri, 12 Jun 2020 10:56:15 +0000
To: Pete Resnick <resnick@episteme.net>
References: <159166311543.4506.736406779378278905@ietfa.amsl.com> <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> <1UWB5RhEL2.1bMPW5hKaR9@pc8xp> <4196EDE2-E81A-4E9B-A78C-37CE89231857@episteme.net>
Cc: Stephen Farrell <stephen.farrell@cs.tcd.ie>, Jay Daley <jay@ietf.org>, ietf <ietf@ietf.org>, ietf108planning@ietf.org
From: tom petch <daedulus@btconnect.com>
Message-ID: <5EE35F46.9060604@btconnect.com>
Date: Fri, 12 Jun 2020 11:56:06 +0100
User-Agent: Mozilla/5.0 (Windows NT 5.1; rv:38.0) Gecko/20100101 Thunderbird/38.5.0
In-Reply-To: <4196EDE2-E81A-4E9B-A78C-37CE89231857@episteme.net>
Content-Type: text/plain; charset="windows-1252"; format="flowed"
Content-Transfer-Encoding: 7bit
X-ClientProxiedBy: LO2P265CA0201.GBRP265.PROD.OUTLOOK.COM (2603:10a6:600:9e::21) To VI1PR0701MB2480.eurprd07.prod.outlook.com (2603:10a6:800:63::16)
MIME-Version: 1.0
X-MS-Exchange-MessageSentRepresentingType: 1
Received: from [192.168.1.65] (86.139.211.47) by LO2P265CA0201.GBRP265.PROD.OUTLOOK.COM (2603:10a6:600:9e::21) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256) id 15.20.3088.18 via Frontend Transport; Fri, 12 Jun 2020 10:56:14 +0000
X-Originating-IP: [86.139.211.47]
X-MS-PublicTrafficType: Email
X-MS-Office365-Filtering-Correlation-Id: a3eef32b-17af-41ad-9efb-08d80ebf39ed
X-MS-TrafficTypeDiagnostic: VI1PR0701MB2656:
X-Microsoft-Antispam-PRVS: <VI1PR0701MB26569530B691BC6829BBF542C6810@VI1PR0701MB2656.eurprd07.prod.outlook.com>
X-MS-Oob-TLC-OOBClassifiers: OLM:10000;
X-Forefront-PRVS: 0432A04947
X-MS-Exchange-SenderADCheck: 1
X-Microsoft-Antispam: BCL:0;
X-Microsoft-Antispam-Message-Info: pq2n1SfI1TNXlekFOv/35AQjLNUJvpHVOBO7jX/NVQvoMG6iZNsJEJuYaGbr46fyOaHPfxqZ3gzdI70xTrIh5KVidyd9rqNkP0v64PcJnwQtMnDbBtT6cD/zAq+zjpIUuLau2CBHzNp+uOXPwFLL8QazBwq/oc+Ir9roRcGAlet1j/bM5g4FrvlfRMFgyhjEJA7FfaBPaSXydokXueHPuGmKdvQLOIvhrJoDMkBcjTmS4Gi+t7gm4ISGSFjKx9xaUBrzPQBT19HhIjkc1alWR2Vulz/V9gnYm8Lt3Y2ykuhG4HExBl8W1dIMr9c5cvL7ei2237HNqutWhTMR0A76vA==
X-Forefront-Antispam-Report: CIP:255.255.255.255; CTRY:; LANG:en; SCL:1; SRV:; IPV:NLI; SFV:NSPM; H:VI1PR0701MB2480.eurprd07.prod.outlook.com; PTR:; CAT:NONE; SFTY:; SFS:(346002)(376002)(366004)(396003)(136003)(39860400002)(6916009)(36756003)(87266011)(8676002)(33656002)(478600001)(5660300002)(52116002)(53546011)(8936002)(54906003)(4326008)(66556008)(6486002)(66476007)(186003)(6666004)(26005)(16576012)(16526019)(316002)(2616005)(86362001)(83380400001)(2906002)(66946007)(956004); DIR:OUT; SFP:1102;
X-MS-Exchange-AntiSpam-MessageData: EmjMEt28U4odoy3oXEyxOO+9CV+Hw2DT6KGN0PmHcyeXrqBlzvUinhP7RJ33yWi9q1gzhAFfvFMSGEvELaikfyN0uYxwv/P4oW3VSRJ/BpdwbMBAxURJt06lljuuXlWbHnrjHSnTJq6AFyPmjfQGnRX9mjSq8t89e8vcp43jTOS0OcquWg8fLcRRZnPqdgwQkXsslSXc4VRSPx3bdlqN14CAmej89fJDEi8BvwrdlLKjZxXgN0GyqaDnZq5VJu5O1AIUl4MvrNn3ZoadNZdeixl7s6vHnDvm6IocpsC+FLc2E3eNitLTPGgzmlrR550cp3eZQPCTKsQRWpe1O4ykIKmfNWVH+ySX1mz8zUKwnPFPX60pQH/LEQ9c8OU1SbBRyPAdOM9FR9N72MNONewGYNuw7wZfRw8HFliwKY0vzEdRzljEXCQZP1/XR3xGSGX/Ks2NR1TmrdtS6i4ln/cSPgyFtt8I+wgv4l2ZjpmmoSc=
X-OriginatorOrg: btconnect.com
X-MS-Exchange-CrossTenant-Network-Message-Id: a3eef32b-17af-41ad-9efb-08d80ebf39ed
X-MS-Exchange-CrossTenant-OriginalArrivalTime: 12 Jun 2020 10:56:14.8840 (UTC)
X-MS-Exchange-CrossTenant-FromEntityHeader: Hosted
X-MS-Exchange-CrossTenant-Id: cf8853ed-96e5-465b-9185-806bfe185e30
X-MS-Exchange-CrossTenant-MailboxType: HOSTED
X-MS-Exchange-CrossTenant-UserPrincipalName: KBdBGkKg0MMJJB5KHxowmrTre1S8ikO6eGZ1en37BrEWVH47Nev4z9GUhTYGb7ONsDZLJJJoaEmrolxixWbKjQ==
X-MS-Exchange-Transport-CrossTenantHeadersStamped: VI1PR0701MB2656
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf108planning/ErC1BTieCl90iUg5IE-wrOYqztI>
Subject: Re: [Ietf108planning] Registration open for IETF 108
X-BeenThere: ietf108planning@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: <ietf108planning.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf108planning>, <mailto:ietf108planning-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf108planning/>
List-Post: <mailto:ietf108planning@ietf.org>
List-Help: <mailto:ietf108planning-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf108planning>, <mailto:ietf108planning-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 12 Jun 2020 10:56:21 -0000
On 11/06/2020 19:34, Pete Resnick wrote: > On 11 Jun 2020, at 11:37, tom petch wrote: > >> Looking at RFC8711 I see >> >> "7.5. IETF Meeting Revenues >> Meeting revenues are another important source of funding that >> supports the IETF, coming mainly from the fees paid by IETF meeting >> participants. The IETF Executive Director sets those meeting fees, >> in consultation with other IETF LLC staff and the IETF community, >> with approval by the IETF LLC Board. Setting these fees and >> projecting the number of participants at future meetings is a key >> part of the annual budget process." >> >> Elsewhere in that cluster of RFC that came out in February, in the >> context of venue, it explicitly calls out the need for consensus as >> declared by the IETF Chair. Here there is no call for consensus. If >> the IETF had wanted more control then it should not have approved >> RFC8711:-) I think that Jay was well within his rights to take the >> actions he did. > > Tom, it was made pretty clear in the discussion of RFC 8788 that when > the IETF referred to "meetings", it did not have in mind the idea of an > entirely remote meeting. Similarly, in the same cluster as 8711, neither > 8718 nor 8719 anticipates the idea that a meeting would be held with no > "location" or "venue" at all. So to say of 8711 that 7.5 clearly > anticipates entirely online meetings is a bit of a stretch. It doesn't > absolutely conclude otherwise, but the discussion of 8788 should have > been a pretty good hint that the community would have been surprised by > the interpretation, and the better course would have been to ask the > community what it intended by the text in 7.5 of 8711. > > Also, I know of several people, and I'm sure others know of similarly > situated folks, who are regular participants but are from > time-to-to-time between jobs or in other financial situations, who have > specifically decided not to attend the physical meeting and instead > participate remotely because of the lack of registration fee (in > addition to not having to pay for travel). Folks have come to expect > that participation in the face-to-face meeting would incur expenses, but > participating remotely, whether by listening to the audio feed and using > jabber or email to send in comments, or more recently by Meetecho, was > going to be free. While not the only reasonable interpretation of our > history and BCPs on the matter, having remote participation be free is > certainly not an unreasonable interpretation of the status quo. > > So "well within his rights" seems a bit of a reach. Perhaps "not > completely unjustified in assuming" is closer. Pete OK. I do see in RFC8719 a reference to virtual meetings, admittedly in the context of these being in addition to the regular cycle of three meetings a year, so it would seem that virtual meetings were seen as possible in this cluster of RFC. And, to state the obvious, this cluster of RFC say that if people want to provide guidance to the LLC then they should gain consensus via an RFC as has been done with RFC8718. So where is the I-D giving LLC guidance on what it is and is not acceptable to charge a fee for in relation to a meeting:-) Tom Petch > > pr
- Re: [Ietf108planning] Registration open for IETF … Dan Romascanu
- Re: [Ietf108planning] Registration open for IETF … Jay Daley
- Re: [Ietf108planning] Registration open for IETF … Ish Sookun
- Re: [Ietf108planning] Registration open for IETF … John C Klensin
- Re: [Ietf108planning] Registration open for IETF … Livingood, Jason
- Re: [Ietf108planning] Registration open for IETF … Livingood, Jason
- Re: [Ietf108planning] Registration open for IETF … Adrian Farrel
- Re: [Ietf108planning] Registration open for IETF … Mary B
- Re: [Ietf108planning] Registration open for IETF … Alissa Cooper
- Re: [Ietf108planning] Registration open for IETF … Mary B
- Re: [Ietf108planning] [EXTERNAL] Re: Registration… Livingood, Jason
- Re: [Ietf108planning] Registration open for IETF … Ish Sookun
- Re: [Ietf108planning] Registration open for IETF … Ish Sookun
- Re: [Ietf108planning] Registration open for IETF … Alissa Cooper
- Re: [Ietf108planning] Registration open for IETF … Alissa Cooper
- Re: [Ietf108planning] Registration open for IETF … Mary B
- Re: [Ietf108planning] Registration open for IETF … Stephen Farrell
- Re: [Ietf108planning] Registration open for IETF … Paul Wouters
- Re: [Ietf108planning] Registration open for IETF … George Michaelson
- Re: [Ietf108planning] Registration open for IETF … Alissa Cooper
- Re: [Ietf108planning] Registration open for IETF … Brian E Carpenter
- Re: [Ietf108planning] Registration open for IETF … Colin Perkins
- Re: [Ietf108planning] Registration open for IETF … Ole Jacobsen
- Re: [Ietf108planning] Registration open for IETF … Colin Perkins
- Re: [Ietf108planning] Registration open for IETF … Stephen Farrell
- Re: [Ietf108planning] Registration open for IETF … Jay Daley
- Re: [Ietf108planning] Registration open for IETF … Ish Sookun
- Re: [Ietf108planning] Registration open for IETF … Alexa Morris
- Re: [Ietf108planning] Registration open for IETF … Randy Bush
- Re: [Ietf108planning] Registration open for IETF … John C Klensin
- Re: [Ietf108planning] Registration open for IETF … Jay Daley
- Re: [Ietf108planning] Registration open for IETF … Lars Eggert
- Re: [Ietf108planning] Registration open for IETF … Adrian Farrel
- Re: [Ietf108planning] Registration open for IETF … Jay Daley
- Re: [Ietf108planning] Registration open for IETF … Stephen Farrell
- Re: [Ietf108planning] Registration open for IETF … Corinne Cath
- Re: [Ietf108planning] Registration open for IETF … John C Klensin
- Re: [Ietf108planning] Registration open for IETF … Colin Perkins
- Re: [Ietf108planning] Registration open for IETF … Corinne Cath
- Re: [Ietf108planning] Registration open for IETF … Gurshabad Grover
- Re: [Ietf108planning] Registration open for IETF … tom petch
- Re: [Ietf108planning] Registration open for IETF … Livingood, Jason
- Re: [Ietf108planning] Registration open for IETF … Pete Resnick
- Re: [Ietf108planning] Registration open for IETF … Toerless Eckert
- Re: [Ietf108planning] Registration open for IETF … tom petch
- Re: [Ietf108planning] Registration open for IETF … Tim Chown
- [Ietf108planning] Fwd: Registration open for IETF… Jay Daley