Re: [Tools-discuss] "Distantly related Internet-Drafts"?

Lucas Pardue <lucaspardue.24.7@gmail.com> Fri, 01 October 2021 12:44 UTC

Return-Path: <lucaspardue.24.7@gmail.com>
X-Original-To: tools-discuss@ietfa.amsl.com
Delivered-To: tools-discuss@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 6EEA53A0C74; Fri, 1 Oct 2021 05:44:27 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.847
X-Spam-Level:
X-Spam-Status: No, score=-1.847 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_ENVFROM_END_DIGIT=0.25, FREEMAIL_FROM=0.001, HTML_MESSAGE=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 oc8xDr1vEdtp; Fri, 1 Oct 2021 05:44:22 -0700 (PDT)
Received: from mail-ed1-x52d.google.com (mail-ed1-x52d.google.com [IPv6:2a00:1450:4864:20::52d]) (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 D2A923A0E03; Fri, 1 Oct 2021 05:44:17 -0700 (PDT)
Received: by mail-ed1-x52d.google.com with SMTP id r18so34217815edv.12; Fri, 01 Oct 2021 05:44:17 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20210112; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=ykfgPpHSrPyyp+f7+5gRvzsGpYQ9Uav1KeW9RGU3H/4=; b=J8DNw3TDrJzjsPyDXUVRVDDRErfnj5039r5o6K7qC72dmi/m79HVZk0hf3ox8tYLhU v4vwdUUP511JgLaxGrZHQudlrtuNwgRNhGtXmnY50pYUrezHQ0LtXx8iE7UXg9uxp29N ypRYw4i1fHwjDwlvfKT4+8M/k2Tey0SHSTgE34Q0zzfjTZw/w39gH6NeL9Ss3Xv+Qe1S QJPKLsQswam31BtkOanSH/q92JgtgRIdJCrb71yilpu9qMz1WH8JWx662rGipVkhVBjG AXJv5xxPcHH+iLbRRrLw5D3nnjOdL9NAWTIz51YUHdW74iNL6epeqgrZAe6BGFQta60f mNpQ==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=ykfgPpHSrPyyp+f7+5gRvzsGpYQ9Uav1KeW9RGU3H/4=; b=U98nhrASvQUVO4SDRNvLbsmJKGdiAMDZ/TpHxkcfnTMW7dNm7NRNgmCYdfBZmKS7ad RUr34hQRjrMwxOF/SIs3OXxYtYurJfkgNoUfb7DamDC99oIj0vvKUEPFYhpnzMlvX8P8 jc42CXLmMW5wgL4NcciDqCzd5HOjf1YrYOVTLmYj2IIlx0COrs/UW6Sw8fNrfPC0XotW 3YKkbbow6Kl9hnY7qORNuu+jpaDFBIf/U2unRghfnSNFkLfqzUHfeUa2Ilo3dthpM8BJ ALDAJmDHiu/n1Zh0PrwqJkpeRGO96k/UGl751KnKU3mXlp3Ys4zG7tPBWsmQaHPvQtaI ZUfg==
X-Gm-Message-State: AOAM533G5fuvGQStYYoUb9oiUgiCWkKFDm7uwyuEhPpgTPpFG8dlhMxD TH48GTfh9GV8tORplTTEuACkOPZkivYo97suXiwkyBhg
X-Google-Smtp-Source: ABdhPJzuYn09jioiK9DGMIUH7KR0mNbu6j7McHa8SMmZFwhY2fwP2J1KADqWhnpZXafS0L72Iuv0a0gGBJyJcIvRK5s=
X-Received: by 2002:a17:906:1146:: with SMTP id i6mr6156196eja.12.1633092254669; Fri, 01 Oct 2021 05:44:14 -0700 (PDT)
MIME-Version: 1.0
References: <CAKKJt-eBA9Anp+JeUkBO5hPBQ5RtaBuvBMtmm1mHh2y2wX0n7w@mail.gmail.com> <DB30D5C1-788A-4BAE-913C-FB335D991C22@eggert.org>
In-Reply-To: <DB30D5C1-788A-4BAE-913C-FB335D991C22@eggert.org>
From: Lucas Pardue <lucaspardue.24.7@gmail.com>
Date: Fri, 01 Oct 2021 13:44:03 +0100
Message-ID: <CALGR9oZYCTrC7Bq940bas0Oyj+0C5e_HF6Xc7JGc+1YuUYEMqQ@mail.gmail.com>
To: Lars Eggert <lars@eggert.org>
Cc: Spencer Dawkins at IETF <spencerdawkins.ietf@gmail.com>, Tools Team Discussion <tools-discuss@ietf.org>, WG Chairs <quic-chairs@ietf.org>
Content-Type: multipart/alternative; boundary="000000000000b99e1b05cd49ebcb"
Archived-At: <https://mailarchive.ietf.org/arch/msg/tools-discuss/IRQO-86dvZZREvylLXRYjdFWG_k>
Subject: Re: [Tools-discuss] "Distantly related Internet-Drafts"?
X-BeenThere: tools-discuss@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: IETF Tools Discussion <tools-discuss.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/tools-discuss>, <mailto:tools-discuss-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/tools-discuss/>
List-Post: <mailto:tools-discuss@ietf.org>
List-Help: <mailto:tools-discuss-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/tools-discuss>, <mailto:tools-discuss-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 01 Oct 2021 12:44:28 -0000

On Fri, 1 Oct 2021, 07:25 Lars Eggert, <lars@eggert.org> wrote:

> Hi,
>
> On 2021-10-1, at 1:59, Spencer Dawkins at IETF <
> spencerdawkins.ietf@gmail.com> wrote:
> > The first document filename starts with "draft-dawkins-quic". I expect
> this one to be listed as a related Internet-Draft. The filename is
> "draft-author-wgname-*", as suggested for Internet-Drafts in
> https://www.ietf.org/standards/ids/guidelines/#7, and it is related to
> the QUIC working group.
> >
> > The second and third document filenames start with
> "draft-dawkins-sdp-rtp-quic". I wasn't expecting to see these listed as
> related to the QUIC working group. These drafts are intended for discussion
> on the MOQ ("Media Over QUIC'') non-WG mailing list, and (if I understand
> the guidance I've gotten from the TSV and ART ADs correctly) are actually
> out of scope for the QUIC working group.
> >
> > Is it possible that the datatracker is scanning the filename looking for
> any occurrence of a working group name, not just in the third position?
>
> IIRC, when I was a QUIC co-chair, I manually tweaked the pattern for the
> QUIC WG in the datatracker settings, because people were submitting
> QUIC-related I-Ds that were not showing up on our datatracker page and we
> hence didn't learn about until (sometimes much) later.
>
> Since I'm not a co-chair anymore, I don't have access to the "manage
> document list" button anymore, so I can't verify this.
>

I've become accustomed to the behaviour now. To my mind out of scope for a
charter doesn't mean unrelated. I think the datatracker does a decent job
with tags that it can let us clearly mark drafts that are serious
contenders for adoption vs other more tangential things.

If there's a problem that the current pattern causes then we can have a
discussion but otherwise I'd leave it as is.


>