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

Spencer Dawkins at IETF <spencerdawkins.ietf@gmail.com> Fri, 01 October 2021 13:26 UTC

Return-Path: <spencerdawkins.ietf@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 E628C3A00CF; Fri, 1 Oct 2021 06:26:20 -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, 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 MEuMoellJyIa; Fri, 1 Oct 2021 06:26:16 -0700 (PDT)
Received: from mail-ua1-x933.google.com (mail-ua1-x933.google.com [IPv6:2607:f8b0:4864:20::933]) (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 36EED3A00B2; Fri, 1 Oct 2021 06:26:16 -0700 (PDT)
Received: by mail-ua1-x933.google.com with SMTP id t36so6670400uad.4; Fri, 01 Oct 2021 06:26:16 -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=068Z0nC6cgQdvpH0+BpzG/1Liu5jKAH6KS18jUekd6Y=; b=KkRe+PkdpO/kQbBfKMyJuHHhnvXWTu1ya4F7JvWIeHUJMBBeY/5bwfmDNR6O/mct9Q sjPEiGbSZiU7AyEzlUGZkYGbdnUdOe6KSH9Bict4WyPoIT3hkRhrxTJWEeRz1JtpsdfU WEdA2Pn6X8YHhvoKjf/FPXBnboSSGpf/YuGrfgQLh/MtfHIyzeq+pN4vkXAOwHwzRVxl lA6N1jHkNX/zYUzuAuWbCoM1oJnY3LXyKUIbC/QB/b5KMCUlckVKMkCaRYUD1XcdkK7J Kf1GEj4ZaQBSXBeVlooPwkhMTpVyb+UPso46H5cUzHI4IbYVg5MN+rna+f4R8YcFZ9Qf J01Q==
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=068Z0nC6cgQdvpH0+BpzG/1Liu5jKAH6KS18jUekd6Y=; b=NK/lzsjAJ8DhyHUfBqXldqNmjhCcbjMM1dzR3qBXFCOf1bmNSYOUc1EvpPedKlapM/ Y/k2C+poDdZyFuzGpEQJnrodvtLc4PMyq0APRJgmXgRsVL7GkHCpSdkSv1ulFjTMmYAM x6prU83EjCdJd70OBzF6Gc1Ws0ClB7tiWXKrgoMZgz+Y4T7000xLuO6QKk7BTlDCmvsL JJKbGylZ4uyqo8ZnWprGCnmnWfUFcVPRNhYkb4swJVxAd8rBFoUlxxJIssPSAFEOhPyM u2PyaThoo6xU2C7EJQRfPtNaziXR5eP5Mn3AKldZThUwfe6Tks01vgLqA080u3h4RYsZ a/hg==
X-Gm-Message-State: AOAM531mthv3NMr/g377d0oEEEbM0YamApHUVpsbGcopFM+jRA7i68vP V0oDA3+puowpVklnM6BCuFurOznOBqPX0uhs9inMh9UY628=
X-Google-Smtp-Source: ABdhPJz+XGHsQcjbMCH1YD7MGgSfm5SiwCXAntxA/wj6DU2R+ncT3rXFCH1sYMP/7L5QRuBYraoGa6A5vJBWRYbtJss=
X-Received: by 2002:ab0:5448:: with SMTP id o8mr10025350uaa.59.1633094774477; Fri, 01 Oct 2021 06:26:14 -0700 (PDT)
MIME-Version: 1.0
References: <CAKKJt-eBA9Anp+JeUkBO5hPBQ5RtaBuvBMtmm1mHh2y2wX0n7w@mail.gmail.com> <DB30D5C1-788A-4BAE-913C-FB335D991C22@eggert.org> <CALGR9oZYCTrC7Bq940bas0Oyj+0C5e_HF6Xc7JGc+1YuUYEMqQ@mail.gmail.com>
In-Reply-To: <CALGR9oZYCTrC7Bq940bas0Oyj+0C5e_HF6Xc7JGc+1YuUYEMqQ@mail.gmail.com>
From: Spencer Dawkins at IETF <spencerdawkins.ietf@gmail.com>
Date: Fri, 01 Oct 2021 08:25:48 -0500
Message-ID: <CAKKJt-fuJyi7sk8rkEY8FZxTUVvw_3d05ANyefmY_gFe9nrLVQ@mail.gmail.com>
To: Lucas Pardue <lucaspardue.24.7@gmail.com>
Cc: Lars Eggert <lars@eggert.org>, Tools Team Discussion <tools-discuss@ietf.org>, WG Chairs <quic-chairs@ietf.org>
Content-Type: multipart/alternative; boundary="000000000000ead6e705cd4a814f"
Archived-At: <https://mailarchive.ietf.org/arch/msg/tools-discuss/jdAMNxfSB2uFFUbAPIURiuR7BUA>
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 13:26:21 -0000

Dear All, but especially Lars,

On Fri, Oct 1, 2021 at 7:44 AM Lucas Pardue <lucaspardue.24.7@gmail.com>
wrote:

>
>
> 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.
>

Thanks for helping me understand - and I feel much better about asking this
question in my original post:

>From the "Spencer is not the center of the universe" department, is it
reasonable to list individual drafts as "related", if the filename includes
the working group name in any position? If so, maybe that just needs to be
documented someplace (it doesn't look like
https://www.ietf.org/standards/ids/guidelines has been updated since Russ
Housley was IETF Chair), and I should be aware of that when choosing
filenames.


It looks like the current behavior in some working groups is actually MORE
helpful than what I thought the datatracker-wide behavior was - and I
didn't know that the behavior wasn't datatracker-wide, either.(*)

So, no, please don't change the behavior just to match
https://www.ietf.org/standards/ids/guidelines! You guys are Doing The Right
Thing.

(this is the "Lars" part) But it might be a good thing to update
https://www.ietf.org/standards/ids/guidelines to match current practice -
the only problem I'm seeing is that the current behavior violates the
Principle of Least Astonishment. I thought I knew where my drafts would
appear, but I was wrong.

Best,

Spencer

 (*) I've been co-chair for something like 5 working groups, but 4 of them
were before the datatracker had significant support for working group
chairs, and (as Lars noted) ADs don't see the "manage document list"
button, so I COMPLETELY missed that I have access to
https://datatracker.ietf.org/wg/cellar/documents/manage/. Seriously, thanks
for catching me up. And everyone who knows me, knows that "catching Spencer
up" is a full-time job ...