Re: meta-list (was Re: New Non-WG Mailing List: CACAO)

Melinda Shore <> Thu, 13 September 2018 03:50 UTC

Return-Path: <>
Received: from localhost (localhost []) by (Postfix) with ESMTP id E5370130E10 for <>; Wed, 12 Sep 2018 20:50:52 -0700 (PDT)
X-Virus-Scanned: amavisd-new at
X-Spam-Flag: NO
X-Spam-Score: -1.999
X-Spam-Status: No, score=-1.999 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: (amavisd-new); dkim=pass (2048-bit key)
Received: from ([]) by localhost ( []) (amavisd-new, port 10024) with ESMTP id W5ohx-rnlK3r for <>; Wed, 12 Sep 2018 20:50:51 -0700 (PDT)
Received: from ( [IPv6:2607:f8b0:4864:20::636]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by (Postfix) with ESMTPS id 46084130DEC for <>; Wed, 12 Sep 2018 20:50:51 -0700 (PDT)
Received: by with SMTP id u11-v6so1972673plq.5 for <>; Wed, 12 Sep 2018 20:50:51 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;; s=20161025; h=subject:to:references:from:message-id:date:user-agent:mime-version :in-reply-to:content-language:content-transfer-encoding; bh=HJ8y6yJe+bCw7urpXlTixbPKtQNDv+BRyI59bhs9FcI=; b=jDk7fwGQuv5eWJH65u91lWYtm2FhC6I1tdvSrkL3yGqBBk8xIsWxjjvas27B4PfHVO zkWx6CQFnH8m/L99XAyC6jtm9O68XSDqhpedpnfzG74dPhvVnnoJxfbxGrbEi1yybpoD OXWrxT4JDzMArdvSiekUJ7LaOi1o8NKX6cyoNa+0gI+DLxtSbddinI5saDsHHyWx5Qa4 Gx/Hfsptbe7XL1rWtRIxJ0I8F012a0VZU/XwEWfd2JSVyyuvGaMeSzFvBgjDi/ePvV5s GJuH5ibleYotDRbniJZkk9o9vJj3R++aLXIeDJJqAcQV/T2Liai7kgBr5QJ80rGe5kxJ ZYBg==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;; s=20161025; h=x-gm-message-state:subject:to:references:from:message-id:date :user-agent:mime-version:in-reply-to:content-language :content-transfer-encoding; bh=HJ8y6yJe+bCw7urpXlTixbPKtQNDv+BRyI59bhs9FcI=; b=PjwK1hfXcl6jYLtW4s2/aX1g54uY4vMhxY9vygrCjco/VpmwjDG/PrXI4wlnPvoE9P hsZbBHMso3A1QxAnQ7JdxtMV2GBo0SwxmwUdTsnbeDndjFtStJIeo+BlKpGnIx9rC59T L83nKAlm17tOuqf36c4n3pj16ekDTv+eXfCzo4LW2kR2BzO+qn8usPjKAzehVcmu21o4 EAxNhRM/d2KFHmEZ97AUGJTiyzs5vjgtcxNwP6F67T0UYdu0QMuR7/7Rw5l6xyD/ukHS x6DJ5RToUxu2HdqBYttLncILQV/OMyp7JNFvCD8u4BbvuLGxjUvMXJoq/wLIJBp4+O3z 9PCQ==
X-Gm-Message-State: APzg51AVSjexVqxlvA1dBgg71N+P1C/3m4yaUsd/fyhbQcPz75iTrESK lcwbYbfD9tH7DyV5WwjLuL57lFZs
X-Google-Smtp-Source: ANB0VdZGF6hIiOw8RSORw+ipn/LvHnwRC6BJVBXzYN66YFw0LgFOAFF1wFXtPPtWUy0wafpM2U009Q==
X-Received: by 2002:a17:902:468:: with SMTP id 95-v6mr5104203ple.122.1536810650006; Wed, 12 Sep 2018 20:50:50 -0700 (PDT)
Received: from aspen.local ([]) by with ESMTPSA id f87-v6sm5785291pfh.168.2018. for <> (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Wed, 12 Sep 2018 20:50:48 -0700 (PDT)
Subject: Re: meta-list (was Re: New Non-WG Mailing List: CACAO)
References: <> <> <> <>
From: Melinda Shore <>
Message-ID: <>
Date: Wed, 12 Sep 2018 19:50:45 -0800
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.12; rv:52.0) Gecko/20100101 Thunderbird/52.9.1
MIME-Version: 1.0
In-Reply-To: <>
Content-Type: text/plain; charset=utf-8
Content-Language: en-US
Content-Transfer-Encoding: 7bit
Archived-At: <>
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: IETF-Discussion <>
List-Unsubscribe: <>, <>
List-Archive: <>
List-Post: <>
List-Help: <>
List-Subscribe: <>, <>
X-List-Received-Date: Thu, 13 Sep 2018 03:50:53 -0000

On 9/12/18 7:23 PM, Andrew Sullivan wrote:
> It might be worth asking whether everyone who might care about the
> IETF really needs to know what every mailing list is for.
> If you don't know whether something is worth following, and there's no
> history in the archive, what are the chances that learning about it
> later is going to be fatal for your ability to say something useful
> about the work?

I think it really depends on what the point of announcing
the mailing list is.  If it's to hook up people who are
interested in working on/reading about/taking shots at
some prospective piece of work it doesn't seem to me to
be too much to ask to include a brief description in the

I'll add that I do feel rather strongly about IETF work
being hosted on IETF assets, but the point at which something
becomes "IETF work" is admittedly rather fuzzy.