Re: Strong objection to draft-ietf-WG-*.all noise levels

Henrik Levkowetz <> Wed, 11 February 2015 16:52 UTC

Return-Path: <>
Received: from localhost ( []) by (Postfix) with ESMTP id 8F05E1A89A8 for <>; Wed, 11 Feb 2015 08:52:50 -0800 (PST)
X-Virus-Scanned: amavisd-new at
X-Spam-Flag: NO
X-Spam-Score: -101.9
X-Spam-Status: No, score=-101.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, USER_IN_WHITELIST=-100] autolearn=ham
Received: from ([]) by localhost ( []) (amavisd-new, port 10024) with ESMTP id 3CUN1ZIOoRje for <>; Wed, 11 Feb 2015 08:52:42 -0800 (PST)
Received: from ( [IPv6:2001:1890:123a::1:2a]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by (Postfix) with ESMTPS id A96CD1A0AF8 for <>; Wed, 11 Feb 2015 08:52:42 -0800 (PST)
Received: from localhost ([::1]:44565 by with esmtps (TLS1.2:ECDHE_RSA_AES_128_GCM_SHA256:128) (Exim 4.82_1-5b7a7c0-XX) (envelope-from <>) id 1YLaWk-0004Zo-ON; Wed, 11 Feb 2015 08:52:41 -0800
Message-ID: <>
Date: Wed, 11 Feb 2015 17:52:09 +0100
From: Henrik Levkowetz <>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.9; rv:31.0) Gecko/20100101 Thunderbird/31.4.0
MIME-Version: 1.0
To: "Dearlove, Christopher (UK)" <>, Brian E Carpenter <>
Subject: Re: Strong objection to draft-ietf-WG-*.all noise levels
References: <> <> <>
In-Reply-To: <>
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 8bit
X-SA-Exim-Connect-IP: ::1
X-SA-Exim-Scanned: No (on; SAEximRunCond expanded to false
Archived-At: <>
Cc: IETF discussion list <>
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <>
List-Unsubscribe: <>, <>
List-Archive: <>
List-Post: <>
List-Help: <>
List-Subscribe: <>, <>
X-List-Received-Date: Wed, 11 Feb 2015 16:52:50 -0000

Hi Christopher, Brian,

On 2015-02-10 10:41, Dearlove, Christopher (UK) wrote:
> Fred Baker
>> I use the draft-*.all mailing lists to do what their description
>> says they do - copy the authors, working group chairs, and relevant
>> ADs on something specific to the draft.
> The document shepherd should also be on that list. I've seen a case
> where he missed something he should have seen due to a similar list
> being used.

The shepherd is on the .all list, and this has been the case since the
.shepherd alias was introduced, which was about a year or year and a half
ago.  The aliases that are created currently are as follows (except that
aliases that have empty expansions are not created):

	<draftname>		Authors
	<draftname>.authors	Authors
	<draftname>.chairs	WG Chairs (for WG drafts)
	<draftname>.ad		AD/ADs (if any)
	<draftname>.shepherd	Shepherd (if any)
	<draftname>.notify	As set in the document's notify field in the DB

and finally

	<draftname>.all		All of the above

Setting the notify field to contain .all or all of the components of .all,
which is the default now, essentially makes the notify field and the .all
aliases have the same semantics.  I think that's a mistake.

A better solution would be to tease apart which kind of notifications
should be sent to all, and which need go only to people more closely
involved in the day-to-day handling of a draft, and have the datatracker
send notifications either to .notify or .all, depending on the kind of

Possibly an additional alias  <draftname>.group would turn out to be
useful in order to populate .all with the WG list, if that is deemed

Best regards,