Re: [dnsext] Progress on moving the mailing list

Ted Hardie <> Thu, 30 September 2010 21:51 UTC

Return-Path: <>
Received: from localhost (localhost []) by (Postfix) with ESMTP id 9D37F3A6C7D; Thu, 30 Sep 2010 14:51:44 -0700 (PDT)
X-Virus-Scanned: amavisd-new at
X-Spam-Flag: NO
X-Spam-Score: -2.079
X-Spam-Status: No, score=-2.079 tagged_above=-999 required=5 tests=[AWL=0.520, BAYES_00=-2.599]
Received: from ([]) by localhost ( []) (amavisd-new, port 10024) with ESMTP id NnG4kfpgPt2p; Thu, 30 Sep 2010 14:51:43 -0700 (PDT)
Received: from ( [IPv6:2001:418:1::62]) by (Postfix) with ESMTP id 881FB3A6C5E; Thu, 30 Sep 2010 14:51:43 -0700 (PDT)
Received: from majordom by with local (Exim 4.72 (FreeBSD)) (envelope-from <>) id 1P1QzO-000Hr9-H0 for; Thu, 30 Sep 2010 21:48:30 +0000
Received: from ([]) by with esmtp (Exim 4.72 (FreeBSD)) (envelope-from <>) id 1P1QzG-000HoA-KE for; Thu, 30 Sep 2010 21:48:23 +0000
Received: by qyk5 with SMTP id 5so2478342qyk.11 for <>; Thu, 30 Sep 2010 14:48:21 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;; s=gamma; h=domainkey-signature:mime-version:received:received:in-reply-to :references:date:message-id:subject:from:to:cc:content-type :content-transfer-encoding; bh=U1j4/P73urIM43942winBAD/UaijPrn8e4uZWTfJ/cQ=; b=CA8W2VkJuHjwlL3D8jb35McsA11qvxHdrDVLv4l8DykV7R3TqX/3oNOwrSUZ6d+ldT 1duJKacQ0tHSFXlAp/WRj1ZSa+269vQHgrSZt93shwoqut5KxEqYydCNGHWiX3zRPgUq FXoqpfh7Ny8M1Hnrp0Zuc8Sztt9eFtE8d7okY=
DomainKey-Signature: a=rsa-sha1; c=nofws;; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type:content-transfer-encoding; b=a7U4mQzf4k637MIrGk2jlepekAVz98UerSTdRBSFLTgV+V0cFIxQORspzyAeuB3fUC MRaVk9eVFSXo9lbMZbDpuHC1yg0IW/PblCduJ69o5mHfPeQBaXkJUQlbORpq/5gXBDwr 688dwRp2fPi7YwWR7gNJDoxipUT986X3/bGqE=
MIME-Version: 1.0
Received: by with SMTP id hm21mr3183721qcb.121.1285883301480; Thu, 30 Sep 2010 14:48:21 -0700 (PDT)
Received: by with HTTP; Thu, 30 Sep 2010 14:48:21 -0700 (PDT)
In-Reply-To: <>
References: <>
Date: Thu, 30 Sep 2010 14:48:21 -0700
Message-ID: <>
Subject: Re: [dnsext] Progress on moving the mailing list
From: Ted Hardie <>
To: Andrew Sullivan <>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable
Precedence: bulk
List-ID: <>
List-Unsubscribe: To unsubscribe send a message to with
List-Unsubscribe: the word 'unsubscribe' in a single line as the message text body.
List-Archive: <>


Any strong reason it shouldn't be ""?  That list
name has a lot of history behind it, and having a consistent thread of
conversation connected to the name, if not its host, seems to me worth it.
An alias from to could be kept for
those wanting the WG Name pointer.

Full disclosure:  I was briefly the list monkey at SRI who kept
up, and I am likely being nostalgic.


On Thu, Sep 30, 2010 at 2:21 PM, Andrew Sullivan <>; wrote:
> Dear colleagues,
> Some time ago, we said we were going to move the WG mailing list from
> to  This sort of fell off
> the radar as it looked like the WG was running out of things to do & I
> absurdly thought we might actually wind up or go back to sleep or
> something.  But with the rechartering in motion, it seemed to me we
> ought to make good on this.
> We've started the process, so the list has been created.
> At the moment, it has no members, and if you post to it your message
> will be moderated (and then we'll reject it).
> Over the coming period, we will subscribe all the existing
> namedroppers members to the list.  You will receive a
> message when this happens.  If you don't want to receive dnsext mail
> messages, then please unsubscribe then, or unsubscribe from
> namedroppers now.
> We will ask the operators of the namedroppers list to put an alias
> forwarding messaages to namedroppers instead to the dnsext list, and
> not to accept new subscriptions to namedroppers.  You won't get
> duplicate messages during the change over, and you won't lose mail to
> the list.  There will probably be a short period when new messages to
> the list are disallowed, and if you have filters that are using the
> exiting namedroppers headers, you will need to update them.
> I will post another announcement in the future with firm dates for the
> cutover.  I will give people ample notice of the cutover date so that
> they may update their filters.  In the meantime, the mail address will
> be and the RFC 2369 headers will follow the pattern of
> all the other lists hosted in the IETF mail infrastructure.
> Best regards,
> A
> --
> Andrew Sullivan
> Shinkuro, Inc.