Re: Registration details for IETF 108
Eric Rescorla <ekr@rtfm.com> Tue, 02 June 2020 13:28 UTC
Return-Path: <ekr@rtfm.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 3E7313A0917 for <ietf@ietfa.amsl.com>; Tue, 2 Jun 2020 06:28:41 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.268
X-Spam-Level:
X-Spam-Status: No, score=-0.268 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, HTML_IMAGE_ONLY_24=1.618, HTML_MESSAGE=0.001, SPF_HELO_NONE=0.001, SPF_NONE=0.001, T_REMOTE_IMAGE=0.01, URIBL_BLOCKED=0.001] autolearn=no autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=rtfm-com.20150623.gappssmtp.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 OUfNB7igxrOR for <ietf@ietfa.amsl.com>; Tue, 2 Jun 2020 06:28:40 -0700 (PDT)
Received: from mail-lj1-x229.google.com (mail-lj1-x229.google.com [IPv6:2a00:1450:4864:20::229]) (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 9295F3A0916 for <ietf@ietf.org>; Tue, 2 Jun 2020 06:28:39 -0700 (PDT)
Received: by mail-lj1-x229.google.com with SMTP id e4so12594934ljn.4 for <ietf@ietf.org>; Tue, 02 Jun 2020 06:28:39 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=rtfm-com.20150623.gappssmtp.com; s=20150623; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=LNnaixUPeQkyqIB7IIg7reVxlIo3uxbcpvR/wdYG6rA=; b=1MdTvWcsbgMpYwqYsLGYkvplu2xNwpxEdMaV8lofMqeUHaSrPeOIOOMwZORAOtQZB/ Uo4DWNqjy1NYewQCWQBGzz7ViMrpsfEbOfN8fz1AeR3fM+13oJ5WYGbva99965c7sr9n 6GZ0fUGkKKnXGwHlCBaDyNenOtdHk6XmkUNm4TSWmoDCpKbm3CrU2bNhxjUBmDSZvxj2 BgrJFv/EpIELK+iqFgqJ2gkjcvANNbeJSe4/w+VtnXbnbdErInwUEtR4e9wPObEnrrJk 6Dikr/RNxYKx7ImkUh6yRQh+4rYkc2lSIOKCSTcYVFxe/vkqbMq05yKltSX+wPWaXWZ4 xjkg==
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=LNnaixUPeQkyqIB7IIg7reVxlIo3uxbcpvR/wdYG6rA=; b=pi1iwuU/SQWp478q9dgw4CCX+jxN79xiV1HR11jJmFjQvBu9frRgPpn74u+TQRE0S+ K7itPG9jjqyXE4RJsILk6S1BWGqvlR4SdI4GcsyrWEWU2BbJxIfK5LKEIB0tWvBX3eG5 Kix8fDIOhgagziqLFPzNLzElhut1IuajbsP8I9Yc0r46Si8s6cYN3ZhlK/qxachQDh9o fIV/kPoET5ttVjcNFYCFlVu4laL0kOXMfK1gl8x2MpgeM2o6azVs+zVQVNGFOq6mNDCu 28F+mZBvxDsCxguG4dmwHulQfj8EirE23pCPyHIgh2LJXwm6XA2lnmc6KqQJj+ov9xsG lPEQ==
X-Gm-Message-State: AOAM533LAvcAgHKPXqeI4gUrIwrsFTDxmFHef77uEjzeMC7UlQk0dLtt k7BI11XTM5LrErW5k0SKzKQ7fkG81Ijvz6vyq76h5Q==
X-Google-Smtp-Source: ABdhPJyZcKdMrLvLbwvtW2G5NXUvMGI6sFQUjuVjaoO0PikgGnBNzam4lJwpe/Moy3jrtOfId6aB7nzDUW9f6SyB4VQ=
X-Received: by 2002:a05:651c:2c6:: with SMTP id f6mr12724312ljo.371.1591104512683; Tue, 02 Jun 2020 06:28:32 -0700 (PDT)
MIME-Version: 1.0
References: <159062833754.6110.5826748635235943562@ietfa.amsl.com> <6.2.5.6.2.20200531121457.0b249858@elandnews.com> <CABcZeBOzVHaSZa0A3eDz12RwNuCiHtiJL8wqvAhhLPN6YEQOkQ@mail.gmail.com> <3f9a0e50-c01b-01c6-ad52-95f370baeb8d@joelhalpern.com> <B71999A2-3EC6-4649-864F-674BA494B511@gmail.com> <616FD1DE-C25F-44CE-9FA3-CC00943FC98B@cable.comcast.com> <A9DBD8B0-01B3-4C68-91B3-BD1E99E226BA@gmail.com> <70d1493c-4c00-f32e-8996-72d0a8369571@comcast.net> <D3BA93CD3D2D101946F35024@PSB> <9F71F116-D7B2-4ECE-9000-957A0C497404@ietf.org> <01d701d638ca$c096b5e0$41c421a0$@gmail.com> <CABcZeBOLAw_9s-gobFYB=5THu_Q70UmDLn_ZhVXhNRHN_nu_0w@mail.gmail.com> <0da9f8f0-867e-cd18-3fd9-39cabe0208a0@foobar.org>
In-Reply-To: <0da9f8f0-867e-cd18-3fd9-39cabe0208a0@foobar.org>
From: Eric Rescorla <ekr@rtfm.com>
Date: Tue, 02 Jun 2020 06:27:56 -0700
Message-ID: <CABcZeBM2CNHcC0UxLZdkQ3xbtpsnWkUqeSuCyFjCFeEENNKnrg@mail.gmail.com>
Subject: Re: Registration details for IETF 108
To: Nick Hilliard <nick@foobar.org>
Cc: Mehmet Ersue <mersue@gmail.com>, ietf <ietf@ietf.org>
Content-Type: multipart/alternative; boundary="00000000000047877e05a719e32e"
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/zRNTw-CT-vUJovR0uCmX1qfKqNA>
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: Tue, 02 Jun 2020 13:28:41 -0000
On Tue, Jun 2, 2020 at 6:16 AM Nick Hilliard <nick@foobar.org> wrote: > Eric Rescorla wrote on 02/06/2020 13:57: > > This seems like entirely appropriate practice on short notice. > > neither side's position seems unreasonable from their own point of view: > the LLC needs to make executive decisions and sometimes these will be > problematic. Conversely, the IETF community has an expectation that > there's engagement about policy changes before they happen. > Hmm... This doesn't seem like the right framing to me in several respects: First, I think everyone agrees that some kinds of policy changes would need consultation. For instance, if the LLC were to decide that in perpetuity we were not to havemeetings or that we were to have 6 a year, that would clearly need consultation. On the other hand, I (would hope) that everyone agrees that some changes could be made by executive decision. For instance, moving the refund date forward or back by a day would I hope not require community consultation. So the question at hand is what kind of decision this is. Second, as you can see from the thread above, it's not correct that "the iETF community" has an expectation they should have been consulted about this in advance. Rather, part of the IETF community does and some of it thinks this was fine. -Ekr
- 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