Re: Registration details for IETF 108
tom petch <daedulus@btconnect.com> Fri, 05 June 2020 11:32 UTC
Return-Path: <daedulus@btconnect.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 C36373A1491 for <ietf@ietfa.amsl.com>; Fri, 5 Jun 2020 04:32:46 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.9
X-Spam-Level:
X-Spam-Status: No, score=-1.9 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, URIBL_BLOCKED=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 YlVmws5tW3Ij for <ietf@ietfa.amsl.com>; Fri, 5 Jun 2020 04:32:45 -0700 (PDT)
Received: from EUR04-VI1-obe.outbound.protection.outlook.com (mail-eopbgr80117.outbound.protection.outlook.com [40.107.8.117]) (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 F369B3A148F for <ietf@ietf.org>; Fri, 5 Jun 2020 04:32:44 -0700 (PDT)
ARC-Seal: i=1; a=rsa-sha256; s=arcselector9901; d=microsoft.com; cv=none; b=CR3zD73BvzsMn2FLn4N3LCA++c3pm/Eod13MVUavHaRH5DikpCgjFAE+gcm4pb3syE0KmCgYPfv87wPlfl72e9x4TFVpjOiP78qN6p6X0+2gmGTihOoCZGT5+HS69PnYVTDffPtGTU2ZUMmGMwT4GqWWR/PV3RW2w6Xo4uFDLaS/YHrzJUnt+AIPqW8+TZS/StHWG9+bKMfQbDQ52n4UA+Slf7aXOQPlb+6DAODjyEM/0XsOR5jHZOiVxj0Qu/3DyxqzySiUke8COomk5FXctL+7UfO0QCxkb3GPYfink9eqe0VqU3z5SmZE8hNTJDsELsNkrGEXqpow9qP6ciIxRg==
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=q5rvV72XDH6eDcGOdctoBvRcFhQA2Hg0fGGkiESZEDg=; b=ThXlsbhvyp8uMoy3XrqdCAyxHjkoPHBCpJtbluCcES4aOde55IeEDX6hM+CuwPPJlhAxgNgf3Dq9MXbe6rLZsgMYMzAd6tKstaLbdw3MszSJ8tLw/AN1ycNdH3N+h0FWMyuagMPHC5B07HI3PHvliWgaHW/a/2OsbQEchR6Qu2xzEULqhNpYH6PoskvdC5ox80if5Vsx9xsL666E4mE0gwI1yYqTh004iYh/2+aZQHDNPgzUSuYxES1LYO7MJcS/Hg4R/eQ8YMnvp0D6UDs4lQp8azoM5hDDM4dSFbnQtAYLrbyJF5hPsxuWrbtGMAR5TJzOk0QrWqgDuPs0p56nwQ==
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=q5rvV72XDH6eDcGOdctoBvRcFhQA2Hg0fGGkiESZEDg=; b=TpdgSRoGcG3fDek2sVhiHlEzBnZo+2Xu7fFXLPNsMXoH5L0y6fr52/ctb9reHh6iuXmuIf9JqywCVkZ+7u1y6bfiaECTeIrK3vMfCl/dIhRDIg5ketm8BgglRjUUTJ8NTWaMBZkjiL7qr52ZtcaXSR3KCrWqXNSuYPquDqmb4s0=
Authentication-Results: gmail.com; dkim=none (message not signed) header.d=none;gmail.com; dmarc=none action=none header.from=btconnect.com;
Received: from VI1PR0701MB2480.eurprd07.prod.outlook.com (2603:10a6:800:63::16) by VI1PR07MB5454.eurprd07.prod.outlook.com (2603:10a6:803:c6::29) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.3088.9; Fri, 5 Jun 2020 11:32:42 +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.3088.011; Fri, 5 Jun 2020 11:32:42 +0000
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: quoted-printable
References: <159062833754.6110.5826748635235943562@ietfa.amsl.com> <9F71F116-D7B2-4ECE-9000-957A0C497404@ietf.org> <01d701d638ca$c096b5e0$41c421a0$@gmail.com> <CABcZeBOLAw_9s-gobFYB=5THu_Q70UmDLn_ZhVXhNRHN_nu_0w@mail.gmail.com> <607b7682-0a75-62b6-fd0e-5e2e1171a68b@cs.tcd.ie> <CA+9kkMBEqhn115ToB0SwOGavmXze4DdJdL941J4LeVMRrPngpQ@mail.gmail.com> <e1b804ae-4c2e-fdf3-8804-47820d35facf@cs.tcd.ie> <CA+9kkMC8ZWHaCBg=WzwtriVf-3bq=egupVgAH-J7dSqspwLoFw@mail.gmail.com> <a19c3066-bfa7-ded2-d98f-b5e367645451@cs.tcd.ie> <E8BE49F8-6FE8-4470-9314-21F8BFE9768A@gmail.com>
Date: Fri, 05 Jun 2020 12:32:30 +0100
Message-ID: <1UWAyqDxFn.1IOJoXgqe8i@pc8xp>
In-Reply-To: <E8BE49F8-6FE8-4470-9314-21F8BFE9768A@gmail.com>
From: tom petch <daedulus@btconnect.com>
To: Tim Chown <tjc.ietf@gmail.com>, Stephen Farrell <stephen.farrell@cs.tcd.ie>
Cc: Ted Hardie <ted.ietf@gmail.com>, ietf <ietf@ietf.org>
Subject: Re: Registration details for IETF 108
User-Agent: OEClassic/3.0 (WinXP.2600; F; 2019-11-28)
X-ClientProxiedBy: LO2P265CA0209.GBRP265.PROD.OUTLOOK.COM (2603:10a6:600:9e::29) To VI1PR0701MB2480.eurprd07.prod.outlook.com (2603:10a6:800:63::16)
MIME-Version: 1.0
X-MS-Exchange-MessageSentRepresentingType: 1
Received: from pc8xp (86.139.211.47) by LO2P265CA0209.GBRP265.PROD.OUTLOOK.COM (2603:10a6:600:9e::29) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.3066.18 via Frontend Transport; Fri, 5 Jun 2020 11:32:41 +0000
X-Originating-IP: [86.139.211.47]
X-MS-PublicTrafficType: Email
X-MS-Office365-Filtering-Correlation-Id: 160d0575-c2d4-4bc2-16c7-08d8094428c1
X-MS-TrafficTypeDiagnostic: VI1PR07MB5454:
X-Microsoft-Antispam-PRVS: <VI1PR07MB54548FD4B3D3AA4F4CADE63EC6860@VI1PR07MB5454.eurprd07.prod.outlook.com>
X-MS-Oob-TLC-OOBClassifiers: OLM:10000;
X-Forefront-PRVS: 0425A67DEF
X-MS-Exchange-SenderADCheck: 1
X-Microsoft-Antispam: BCL:0;
X-Microsoft-Antispam-Message-Info: eV7XCNaZcMVCj8QSwdWsvsgVVDEUzDgeoUeRf4CH0uB088NMehQxUG8BDcd7iRbSLJiD2fswf75fpvw6ArGZDuAUtr5IAU62UJNDLS7e/u6/7p63/V4cbLUy6f3oTR57EHlKj3uDBNl0YV3F+lzRIbsoJq6KuqlFuxfu+pRRXJttOLMQawxydKrbDK99/uOtO22quRarDnS0XQRga+voj8fezxjPRVaCzoJhl9BdWNXdeahet+/pZ1QXWCQPITTnkgx7/W+82IAY+MNuakapbpCh+Krz1CwazeyNDUD+BfYrrgtJ8pWqfBvCt7wzJhHpu8WKXmCxlVsWll5Z9AogIDLoJ96Rkclykm/58ebymNVFgcH8+rbPEaRfrgoiazNu4CODWkXzlzyWmQ79YfcrTQ==
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:(39860400002)(376002)(346002)(136003)(366004)(396003)(16526019)(53546011)(9686003)(52230400001)(26005)(54906003)(478600001)(9576002)(55016002)(2906002)(5660300002)(110136005)(83380400001)(8936002)(186003)(66476007)(66556008)(66946007)(4326008)(86362001)(956004)(316002)(6496006)(52116002)(33716001)(45080400002)(8676002)(6666004)(966005); DIR:OUT; SFP:1102;
X-MS-Exchange-AntiSpam-MessageData: ekaQGS3nMXOE888NQc47EwjPLrpnY8xrPlWEYF//bKK12zfi0xALZnL51qtSPLfEHfSsDBnMoTtpcDrPrB2TtNS1jqhP+W9/bzshizuSvJODf4lCWPNchTmpPTfAVxOlEREQzySVxXI4WIpyYunQceNvDsQAf3VXKN8zuX3+CXM6iK4bcmHZ1JaaYMK61LMPCNvnxl3dCGZ+ia7zfQrVB2UeT6TRaJh9+ABs29epptLUtTYLhVYaxLgWwvyNRIgUFjeKmowTu0nE9ME8dI6vME+FXzVzMb12+Ij3Kspy0WAnNLvxxXb2PF+e8lGl/uFIRJ41ZJUB6rP/gqRgMFU1jUIdgKlU3qvEPGJwgUVY0ej7NZGohsvmncRRGSfyGG5zbbBZOdtsFwkEUesT/lH0sq6Al7BPDLy71fbrgeTzbHx6HHbMC3a24tdOIqcgbo4ZYeLlk0oFusDJNgpIH4fMAilKh032HifLKYOff0dSiHg=
X-OriginatorOrg: btconnect.com
X-MS-Exchange-CrossTenant-Network-Message-Id: 160d0575-c2d4-4bc2-16c7-08d8094428c1
X-MS-Exchange-CrossTenant-OriginalArrivalTime: 05 Jun 2020 11:32:42.2482 (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: t+r7lVFMesQxIrWH4LUx4dVPSfHia73SSPdrlqU2o29yka2mjBga+6BVKzP8bd70OHqiLHga/Sl3Xbv4slK0cA==
X-MS-Exchange-Transport-CrossTenantHeadersStamped: VI1PR07MB5454
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/8xQgMKSgm9mTF6NsEYRXALB1mWM>
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: Fri, 05 Jun 2020 11:32:47 -0000
----- Original Message ----- From: Tim Chown tjc.ietf@gmail.com Sent: 04/06/2020 13:28:44 > On 2 Jun 2020, at 22:25, Stephen Farrell <stephen.farrell@cs.tcd.ie> wrote: > > Hiya, > > I think this bit is where our disagreement is most clear: > > On 02/06/2020 22:16, Ted Hardie wrote: >> But somebody has to be the stuckee for the decision on the money side of >> that, and at the moment it is the LLC. > > The move from zero to non-zero is not "on the money > side" as the status-quo involves no fee. (Ignoring > the exception that will be IETF108.) > > FWIW, this discussion is convincing me more that > the LLC definitely ought not be setting such policies. I agree with this, though the IESG may have come to the same conclusion if tasked to consider the matter. As it stands, WG chairs can presumably schedule interims in place of a slot at IETF 108, if they wish to maximise virtual participation, and avoid clashes with other IETF 108 sessions that may draw important contributors away. <tp> I saw a discussion on a WG list yesterday which I would characterise as In person meeting; Cost thousands; Timing chosen to suit others Virtual meeting; Cost hundreds; Timing chosen to suit others Virtual interim; Cost negligible; Timing chosen to suit us which makes me wonder if there will be an increase in requests for Virtual interim, And if they are constrained, will there be an increase in Webex? Tom Petch --- New Outlook Express and Windows Live Mail replacement - get it here: https://www.oeclassic.com/ Tim
- 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