Re: [v6ops] IETF 108 planning

Tim Chown <tjc.ietf@gmail.com> Thu, 04 June 2020 12:37 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 AD2BD3A0B35 for <v6ops@ietfa.amsl.com>; Thu, 4 Jun 2020 05:37:18 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.098
X-Spam-Level:
X-Spam-Status: No, score=-2.098 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, URIBL_BLOCKED=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 83VVEzzyIvun for <v6ops@ietfa.amsl.com>; Thu, 4 Jun 2020 05:37:17 -0700 (PDT)
Received: from mail-wr1-x431.google.com (mail-wr1-x431.google.com [IPv6:2a00:1450:4864:20::431]) (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 DC2E23A1054 for <v6ops@ietf.org>; Thu, 4 Jun 2020 05:35:54 -0700 (PDT)
Received: by mail-wr1-x431.google.com with SMTP id h5so5907415wrc.7 for <v6ops@ietf.org>; Thu, 04 Jun 2020 05:35:54 -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=HpcvMUDm09bw5RoxTcentjgmx6FWmmlytcB0irO69Pg=; b=sAgEPfoEiqmbn20mb5hIIMev13GtbAgLWrK2YLCFeOUQf3m8X4cXPUSAvxpvgQOFXN rbcqMKsKEdNzQBM3MsmTiEgK8lES1cKNNGHnDVBnGmmit4V4lBG2NbQPWu4kRlJasWii j1q3JfEJ1Zc4MrpInWj08FHaXev8gp+0owYQKPy5iRJVmEmvvR82xYMoidcz+r39vk5y l9XUc/8jNnpta1ymD2fQb2FzZMEqNf1T3vvO8JBKBNcNjRONNxKG6OmM2HHh2lAi9D3E 1TSSxV45X3QyyngLGTMW/5Nh14/CdEz9Pniq5qznHUEROnoH2POIRqUssKeBZFFy3mgC JdRQ==
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=HpcvMUDm09bw5RoxTcentjgmx6FWmmlytcB0irO69Pg=; b=RgGFLCHlR31BO9WgpBDMjGrTkNnQWYCPg6GmyCS/WsLAzillssyWQKtJQs8ZA9yj08 GoQLFDJ/d8y9BgHB4XjBY4+5iNKRULI0rr/CSz5d6s2nNYz4tr37MD7JjwEejOpsiLlj C6rNyjyOrDPmsyRABnhIpv1O21+L8sSJMkY5WgHhckvXqyenVjr5ZXC3wmRUIcdGKttw FEJsYCt7n7VcWN16Va80RSDZF4IUxL9J/01XnO7pq7Nwzc7OTCJj9P6nL/7KI6EXGxuK px/kj4fPD5G+Eo9SERx3HEuxu3tJzdCmdA4c5c1V4y11bnZOeQ5Ev0YwMfU8v+p8jXvg Mqvw==
X-Gm-Message-State: AOAM531gYO7r05Pb6svXubsfJsmVIvSwM0AseVKwm8t2tpIPfBhVHyNc mGdTcPYs2iqbIBtnVMDNPw6oCS0q
X-Google-Smtp-Source: ABdhPJyFz04rvitrQv4NLLDFsnJXkJ2X1Ai4VR1LdpT9jXW+JVYPOzolv6BV2U/dr1GxiqLt4O5qwQ==
X-Received: by 2002:a05:6000:4c:: with SMTP id k12mr4183131wrx.215.1591274153399; Thu, 04 Jun 2020 05:35:53 -0700 (PDT)
Received: from [192.168.0.21] (tchowndsl.claranet.co.uk. [212.188.254.49]) by smtp.gmail.com with ESMTPSA id s132sm7604434wmf.12.2020.06.04.05.35.52 (version=TLS1_2 cipher=ECDHE-ECDSA-AES128-GCM-SHA256 bits=128/128); Thu, 04 Jun 2020 05:35:52 -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: <CAOj+MME1Q+yyFoWX4Ho=JZ20LoCUi4Oqh1_q9YB-OxFYXQAsjA@mail.gmail.com>
Date: Thu, 04 Jun 2020 13:35:52 +0100
Cc: Brian E Carpenter <brian.e.carpenter@gmail.com>, Fernando Gont <fgont@si6networks.com>, IPv6 Operations <v6ops@ietf.org>
Content-Transfer-Encoding: quoted-printable
Message-Id: <70B1E0C8-87E4-496F-82B9-157760EF45B5@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> <6708B98F-68AF-48B4-B9A9-E3B7EC2D2BCC@gmail.com> <CAOj+MME1Q+yyFoWX4Ho=JZ20LoCUi4Oqh1_q9YB-OxFYXQAsjA@mail.gmail.com>
To: Robert Raszuk <robert@raszuk.net>
X-Mailer: Apple Mail (2.3608.80.23.2.2)
Archived-At: <https://mailarchive.ietf.org/arch/msg/v6ops/PFSgWExzLOewO2ZBoTBId-iWRYI>
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:37:19 -0000

> On 4 Jun 2020, at 13:24, Robert Raszuk <robert@raszuk.net> wrote:
> 
>  No reason we couldn’t have interim meeting cutoffs, if deadlines are deemed useful?
> 
> Tim
> 
> Spot on ! Besides if cutoffs are distributed in time (say per WG or per Area) it gives much more time for folks interested in BGP or IPv6 to also catch-up with Quic or HTML progress.

Actually, this is a really good point; as it is you see maybe 300-500 (?) drafts appear in 24 hours.  No way you can read everything you might like to. Stagger them and it becomes possible.

Tim