[Gendispatch] Re: Derivative Works: draft-sayre-gendispatc h-derivative-01

S Moonesamy <sm+ietf@elandsys.com> Wed, 15 July 2026 07:34 UTC

Return-Path: <sm@elandsys.com>
X-Original-To: gendispatch@mail2.ietf.org
Delivered-To: gendispatch@mail2.ietf.org
Received: from localhost (localhost [127.0.0.1]) by mail2.ietf.org (Postfix) with ESMTP id 3DD751170B21B; Wed, 15 Jul 2026 00:34:04 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=ietf.org; s=ietf1; t=1784100844; bh=Zfj8sFLeKeSPzMvZc/GedqBlxWE74n99fwbSPlc20oc=; h=Date:To:From:Subject:In-Reply-To:References; b=IV9drfhzve5YTISsJBHkfM0mq0xVUNCSWsOOPnURcbFof5ILVc7JIcjWJwl+kLdeZ T3It4KLNx7Od21/8DMmkeafEuYW83AWlD1UpcqEb54wvHiorGo1kJ5R3rsCQFhK2od 7vLTRoWk8xCSQoEi5uJH9OPqYF+aE4bm3dgcJSIo=
X-Virus-Scanned: amavisd-new at ietf.org
X-Spam-Flag: NO
X-Spam-Score: -2.1
X-Spam-Level:
X-Spam-Status: No, score=-2.1 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, SPF_HELO_NONE=0.001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: mail2.ietf.org (amavisd-new); dkim=pass (1024-bit key) header.d=elandsys.com
Received: from mail2.ietf.org ([166.84.6.31]) by localhost (mail2.ietf.org [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id iZWpUiwyEavJ; Wed, 15 Jul 2026 00:34:03 -0700 (PDT)
Received: from mx.ipv6.elandsys.com (mx.ipv6.elandsys.com [IPv6:2001:470:f329:1::1]) by mail2.ietf.org (Postfix) with ESMTP id 899301170B216; Wed, 15 Jul 2026 00:34:03 -0700 (PDT)
Received: from DESKTOP-K6V9C2L.elandsys.com ([197.226.13.252]) (authenticated bits=0) by mx.elandsys.com (8.15.2/8.14.5) with ESMTPSA id 66F7XIhF003546 (version=TLSv1 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Wed, 15 Jul 2026 00:33:52 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=elandsys.com; s=mail; t=1784100833; x=1784187233; i=@elandsys.com; bh=Zfj8sFLeKeSPzMvZc/GedqBlxWE74n99fwbSPlc20oc=; h=Date:To:From:Subject:In-Reply-To:References; b=suIm0GTDLkdILYgUlowcUI2eOd7H0ntN6uajvZuPXfgPQdJr9xmRG5fM2KqyJbgyL +CV/HZPJKM2AINneDS9qQbmiWuHUgpD+WlZpU3df7GJgPwz3dStFhBPJ4U8IrcT31Y aRdRHhjX+JzESKsYBwRuLuwOWl+1fwiYP9lf64CY=
Message-Id: <6.2.5.6.2.20260714230335.0b2cb0e0@elandnews.com>
X-Mailer: QUALCOMM Windows Eudora Version 6.2.5.6
Date: Wed, 15 Jul 2026 00:15:12 -0700
To: Simon Josefsson <simon=40josefsson.org@dmarc.ietf.org>, gendispatch@ietf.org
From: S Moonesamy <sm+ietf@elandsys.com>
In-Reply-To: <87mrvsrejy.fsf@josefsson.org>
References: <20260714235449.817865.qmail@cr.yp.to> <7f05b921-a716-4f4f-9838-59e2ec57d8a1@cs.tcd.ie> <87mrvsrejy.fsf@josefsson.org>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format="flowed"
Message-ID-Hash: P2KVQKIJEPENWDP6LBKEYZBKI7KOB7AC
X-Message-ID-Hash: P2KVQKIJEPENWDP6LBKEYZBKI7KOB7AC
X-MailFrom: sm@elandsys.com
X-Mailman-Rule-Misses: dmarc-mitigation; no-senders; approved; emergency; loop; banned-address; member-moderation; nonmember-moderation; administrivia; implicit-dest; max-recipients; max-size; news-moderation; no-subject; digests; suspicious-header
X-Mailman-Version: 3.3.9rc6
Precedence: list
Subject: [Gendispatch] Re: Derivative Works: draft-sayre-gendispatc h-derivative-01
List-Id: General Area Dispatch <gendispatch.ietf.org>
Archived-At: <https://mailarchive.ietf.org/arch/msg/gendispatch/N2fArkbivziSK2-MtgFeoZz1ypM>
List-Archive: <https://mailarchive.ietf.org/arch/browse/gendispatch>
List-Help: <mailto:gendispatch-request@ietf.org?subject=help>
List-Owner: <mailto:gendispatch-owner@ietf.org>
List-Post: <mailto:gendispatch@ietf.org>
List-Subscribe: <mailto:gendispatch-join@ietf.org>
List-Unsubscribe: <mailto:gendispatch-leave@ietf.org>

Hi Simon,
At 10:45 PM 14-07-2026, Simon Josefsson wrote:
>I've seen (and been guilty of) document feedback being ignored because
>it wasn't systematically tracked.

I've seen it happening before.

>It mostly comes down to author diligence, which seems weak if we claim
>to conduct an open transparent standardization process.
>
>I would support IETF introducing systematic public issue tracking for
>(WG)LC comments.

Software for issue tracking has been publicly available since a long 
time (it's mentioned below)

>Why?
>
>I am guessing the primary reason we don't track concerns in any
>systematic way is because WG Chairs find this too much work.
>
>Any random free software project on GitHub, GitLab, Codeberg etc has an
>issue tracker were issues can be opened, browsed and discussed.  There
>is no membership requirement.
>
>I can think of lots of argument against systematically tracked issues --
>IMHO most boils down to "too much work" -- but membership concerns
>haven't been on my radar for that.

The membership question depends on whether one requires on a fixed 
number of persons to work on a draft.  The number would be point in 
time within an IETF context, i.e. it would be different one month 
earlier or one month later.  For what it is worth, there isn't any 
publicly-accessible information about the mailing list composition nowadays.

Regards,
S. Moonesamy