Re: [DNSOP] IETF 111 DNSOP WG session II agenda updated

Joe Abley <jabley@hopcount.ca> Thu, 29 July 2021 19:03 UTC

Return-Path: <jabley@hopcount.ca>
X-Original-To: dnsop@ietfa.amsl.com
Delivered-To: dnsop@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 4E6D43A1654 for <dnsop@ietfa.amsl.com>; Thu, 29 Jul 2021 12:03:38 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.097
X-Spam-Level:
X-Spam-Status: No, score=-2.097 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, RCVD_IN_DNSWL_NONE=-0.0001, SPF_HELO_NONE=0.001, SPF_NONE=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=hopcount.ca
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 RuM9YIP1rF9L for <dnsop@ietfa.amsl.com>; Thu, 29 Jul 2021 12:03:32 -0700 (PDT)
Received: from mail-qk1-x735.google.com (mail-qk1-x735.google.com [IPv6:2607:f8b0:4864:20::735]) (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 9E2173A1665 for <dnsop@ietf.org>; Thu, 29 Jul 2021 12:03:32 -0700 (PDT)
Received: by mail-qk1-x735.google.com with SMTP id t68so7021951qkf.8 for <dnsop@ietf.org>; Thu, 29 Jul 2021 12:03:32 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=hopcount.ca; s=google; h=mime-version:subject:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to; bh=zxJ7p2lw+vOR5gBhkIvdhsRn5oudHm3et9ub1MAYtXA=; b=fSMoWy4j/EP2aNp4zzHmpT95EAcgVmeMg5zN86rTKux8RPxRKojQ+Blq4KmaPVQWoA VlPCZ4kr9KJOwjAd2+lKF1XwhW7YP5GrdKAWSACuOaNyYTRzlCUtaVpq7KVQV3dQMnOY PG82k9fNXHNSo00pwpDSjCkCg7Sk6P42szNWw=
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=zxJ7p2lw+vOR5gBhkIvdhsRn5oudHm3et9ub1MAYtXA=; b=tZppMvlOxkf3EBH3c+B2Mh/Gqv0XfIruPHXgWqp19qFx6u1+pbyTDinQQ3uyxm1cfv mXH+qTEmGkBtU+3CLbJFhvJuUD6agDeheOiFwdVA/9fcP4HlzKtC46+fRlmIngy2xJGI vZZZPKy77dBuUW6s8UeBxyIguu4fvnOu5WYt+lMV78se6QwF0r22feFV8H2jzlWyV/Ls Rkh4cbXAihEgsqLORtwoaGRKC9ANUOw02ckiBt88hdnKTYUxZV0hfygr8kbFWSqxXrIE B872YLfC0FBDrzVYMOHabxzee78gGq/wknvyA6kLuvHPG1rxk/2snDvaQCJJRf+UTW5h P4pw==
X-Gm-Message-State: AOAM533SjxBP/dHMWPlMKuXN2s2hkYFYlPgPdz9OEZ7QL37L8FD/7ILK nFJBvYEubG7RcX+x6RXdzD7T4pt4+eGJxSsiBRs=
X-Google-Smtp-Source: ABdhPJwiHtRo8DRcalzn62JEh7lP5xh8ssqUFmkp7436UtUK57cpbtejGmBZ8ggUtkbyv+MdLnFrMg==
X-Received: by 2002:a37:a252:: with SMTP id l79mr6801396qke.128.1627585410794; Thu, 29 Jul 2021 12:03:30 -0700 (PDT)
Received: from smtpclient.apple ([2607:f2c0:e784:c7:65aa:d8f1:1577:33ec]) by smtp.gmail.com with ESMTPSA id m19sm1560074qtx.84.2021.07.29.12.03.29 (version=TLS1_2 cipher=ECDHE-ECDSA-AES128-GCM-SHA256 bits=128/128); Thu, 29 Jul 2021 12:03:30 -0700 (PDT)
Content-Type: text/plain; charset=us-ascii
Mime-Version: 1.0 (Mac OS X Mail 14.0 \(3654.120.0.1.13\))
From: Joe Abley <jabley@hopcount.ca>
In-Reply-To: <b9af7b62d0fd1697eb8988d4edc5ef7284e28957.camel@powerdns.com>
Date: Thu, 29 Jul 2021 15:03:28 -0400
Cc: DNSOP Working Group <dnsop@ietf.org>
Content-Transfer-Encoding: quoted-printable
Message-Id: <DFA7EBC3-FE61-4F75-A60F-B6A376013A89@hopcount.ca>
References: <0000061c-6125-3abf-4338-3163532624b0@NLnetLabs.nl> <b9af7b62d0fd1697eb8988d4edc5ef7284e28957.camel@powerdns.com>
To: Peter van Dijk <peter.van.dijk@powerdns.com>
X-Mailer: Apple Mail (2.3654.120.0.1.13)
Archived-At: <https://mailarchive.ietf.org/arch/msg/dnsop/bEgh8g4cmRj6cJVJdM74NEGEQfY>
Subject: Re: [DNSOP] IETF 111 DNSOP WG session II agenda updated
X-BeenThere: dnsop@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: IETF DNSOP WG mailing list <dnsop.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dnsop>, <mailto:dnsop-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/dnsop/>
List-Post: <mailto:dnsop@ietf.org>
List-Help: <mailto:dnsop-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dnsop>, <mailto:dnsop-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 29 Jul 2021 19:03:38 -0000

Hi Peter,

On 29 Jul 2021, at 14:39, Peter van Dijk <peter.van.dijk@powerdns.com> wrote:

> On this version, I see under New Working Group Business a draft (the
> black lies sentinel) that was posted two days ago. Can somebody please
> explain to me what the purpose of the draft cutoff is, if drafts can
> appear in the datatracker, and on an agenda, after the cutoff?

I believe it has long been the case that the IETF resumes accepting new documents at the start of IETF week. This allows people to document ideas that come up in corridors and in the bar during the actual event.

(Remember actual events? In the Before Times, we had them.)

The purpose of the cut-off as I understand it is that agendas and meeting slots are supposed to be organised long in advance of that, and that it's useful to suspend new documents to avoid the rug being pulled out from that administrative process.

The case where a document is submitted before the deadline and gets agenda time but is updated before the meeting is not unremarkable either, I think, although I think references to the new version would properly be made informally and obviously not in the slides that were definitely submitted well in advance.

I can't speak to the black lies draft, for which I understand new terminology is eagerly anticipated before anybody else mentions it, but that's my general idea of what is going on in the world.

I miss actual events.


Joe