IETF Logo Mail Archive

Re: [v6ops] IETF 108 planning

Tim Chown <tjc.ietf@gmail.com> Thu, 04 June 2020 12:18 UTC

Return-Path: <tjc.ietf@gmail.com>
X-Original-To: v6ops@ietfa.amsl.com
Delivered-To: v6ops@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 8385C3A0B34 for <v6ops@ietfa.amsl.com>; Thu, 4 Jun 2020 05:18:52 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.099
X-Spam-Level:
X-Spam-Status: No, score=-2.099 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, FREEMAIL_FROM=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.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 7EPU_urFngB2 for <v6ops@ietfa.amsl.com>; Thu, 4 Jun 2020 05:18:51 -0700 (PDT)
Received: from mail-wr1-x42a.google.com (mail-wr1-x42a.google.com [IPv6:2a00:1450:4864:20::42a]) (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 31D463A0B2A for <v6ops@ietf.org>; Thu, 4 Jun 2020 05:18:51 -0700 (PDT)
Received: by mail-wr1-x42a.google.com with SMTP id q11so5871457wrp.3 for <v6ops@ietf.org>; Thu, 04 Jun 2020 05:18:51 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:subject:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to; bh=vsatb4MbkJ6AtjNLaEnWjzDW05UrAOMWcoDb4NpNtys=; b=F6Mug13V6j52p8SEtx2jgkn1RexPOnCTxwe0jVuljHGp33u+X8SsOfx5HxR6HWU1PW 6aaCBd2YSt/TdB3Pwdzj9nGA1n3Sy4KybnklRFPaUoBmGWt1NaZg/XwOKS6XJFUMYKr/ Z/JWwsHy3150Smo4482DimSPMyozcXzymQraF0yCcEaBdZub9Gb6tUtaFpONZObO7eeM YdA6qcfC0jrLXNO+YOnvkydG3H1dXiU22R6jLjqlpHaN5xT50pWLiHMCTM3OA4zB9NSi kIdtE/qUKV24mZg0R3wGWUWIlZIDsV2DqeyzQ8ks/kjsG+XJXJay7U4COU7y7dt0sui9 BjVg==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:subject:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to; bh=vsatb4MbkJ6AtjNLaEnWjzDW05UrAOMWcoDb4NpNtys=; b=FtVKR1E/BcwDyqRD2MGsQJbMKaJn3uaSr14wqKWX7Txq4FcMbcJCcG4hpOTiZOTz+T dHPCEtt+gB6RC7eZEdxXZb5buUBItUVDypAAJE9Ydsqa4T7ixEEI8V21VZ54FaZV7mSw TQdrCMkT/fq6SR5efVV4hDCtR6r1mqduuHHEwUzX2RIUsF00wvtoyMwfkbEvKj+rAfot dCV3eQClHRjURWMWC2qLAmrHNnd95FIsfy+P/vYhnett9iLw3o67FjKkbXIj9DLxDfXp wmk7FrdUvmujmFlShCChC0x4mMyxeQ/f52wJ/QNAXERPGn356JX0fzledP74XM8J2gfd jhxQ==
X-Gm-Message-State: AOAM533tSgePTMVhV2keQ1/qA9ZzHLnmSORPINqwve0bmRO2PNNf3gjQ mY5FcBOhiUM0GJa11WuJt7M=
X-Google-Smtp-Source: ABdhPJxOpu/DXGgmgG43bZ1Y+8tFaeQsncFJfmvoJStRevCDxUC8SbQwV3ctEUdZHvZnzOE+QzunAQ==
X-Received: by 2002:a5d:4c45:: with SMTP id n5mr4171173wrt.341.1591273129720; Thu, 04 Jun 2020 05:18:49 -0700 (PDT)
Received: from [192.168.0.21] (tchowndsl.claranet.co.uk. [212.188.254.49]) by smtp.gmail.com with ESMTPSA id t13sm7496383wrn.64.2020.06.04.05.18.48 (version=TLS1_2 cipher=ECDHE-ECDSA-AES128-GCM-SHA256 bits=128/128); Thu, 04 Jun 2020 05:18:49 -0700 (PDT)
Content-Type: text/plain; charset="utf-8"
Mime-Version: 1.0 (Mac OS X Mail 13.4 \(3608.80.23.2.2\))
From: Tim Chown <tjc.ietf@gmail.com>
In-Reply-To: <6bcdfb67-6fde-e21d-a86f-1d6aa603fae4@gmail.com>
Date: Thu, 04 Jun 2020 13:18:48 +0100
Cc: Robert Raszuk <robert@raszuk.net>, Fernando Gont <fgont@si6networks.com>, IPv6 Operations <v6ops@ietf.org>
Content-Transfer-Encoding: quoted-printable
Message-Id: <6708B98F-68AF-48B4-B9A9-E3B7EC2D2BCC@gmail.com>
References: <DM6PR05MB63488D0223B3810B3970767CAE880@DM6PR05MB6348.namprd05.prod.outlook.com> <8EDE375B-90F6-4C31-9E4F-019BC42310B4@gmail.com> <135a2584-7831-91cd-cb42-35815125ff87@si6networks.com> <CAOj+MMFhCxVkCegLH3UeDEDKpQ0GZT8Fw553T=3t7NiF8Q51zQ@mail.gmail.com> <6bcdfb67-6fde-e21d-a86f-1d6aa603fae4@gmail.com>
To: Brian E Carpenter <brian.e.carpenter@gmail.com>
X-Mailer: Apple Mail (2.3608.80.23.2.2)
Archived-At: <https://mailarchive.ietf.org/arch/msg/v6ops/shJ7PrFB7BkPCzgC7tTZJMiOJLU>
Subject: Re: [v6ops] IETF 108 planning
X-BeenThere: v6ops@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: v6ops discussion list <v6ops.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/v6ops>, <mailto:v6ops-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/v6ops/>
List-Post: <mailto:v6ops@ietf.org>
List-Help: <mailto:v6ops-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/v6ops>, <mailto:v6ops-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 04 Jun 2020 12:18:53 -0000

> On 4 Jun 2020, at 09:08, Brian E Carpenter <brian.e.carpenter@gmail.com> wrote:
> 
> Please don't overlook the fact that many people are deadline-driven and the 4-monthly I-D cutoff dates are our main deadlines. Taking that away would damage progress. Also, we need a vehicle for BOFs and other mechanisms like HotRFC, and reporting mechanisms to the community. And whether on-line code sprints and hacakathons really work remains to be seen.
> 
> I'm not saying these things can't be done on line, but we need to make sure we find out all the unwritten and community-building functions of the meetings and replace them too.
> 
> A fine topic for the SHMO WG if created.

Well, an interim is $230 (or was it $320?) cheaper for attendees than planning for a session at the main event.  Makes it cheaper and more accessible to attend, and avoids people missing the session due to clashes with other WGs.  No reason we couldn’t have interim meeting cutoffs, if deadlines are deemed useful?

Tim

v2.23.0 | Report a Bug | By Email