Upcoming change to the Notify field for some documents
Robert Sparks <rjsparks@nostrum.com> Wed, 15 April 2015 18:40 UTC
Return-Path: <rjsparks@nostrum.com>
X-Original-To: wgchairs@ietfa.amsl.com
Delivered-To: wgchairs@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 7D93E1A19EC; Wed, 15 Apr 2015 11:40:00 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.91
X-Spam-Level:
X-Spam-Status: No, score=-1.91 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, T_RP_MATCHES_RCVD=-0.01] autolearn=ham
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 5glKRDVac6py; Wed, 15 Apr 2015 11:39:58 -0700 (PDT)
Received: from nostrum.com (raven-v6.nostrum.com [IPv6:2001:470:d:1130::1]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 213AC1A0A6A; Wed, 15 Apr 2015 11:39:58 -0700 (PDT)
Received: from unnumerable.local (pool-71-170-237-80.dllstx.fios.verizon.net [71.170.237.80]) (authenticated bits=0) by nostrum.com (8.15.1/8.14.9) with ESMTPSA id t3FIdvpG098504 (version=TLSv1.2 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK); Wed, 15 Apr 2015 13:39:57 -0500 (CDT) (envelope-from rjsparks@nostrum.com)
X-Authentication-Warning: raven.nostrum.com: Host pool-71-170-237-80.dllstx.fios.verizon.net [71.170.237.80] claimed to be unnumerable.local
Message-ID: <552EB078.6090302@nostrum.com>
Date: Wed, 15 Apr 2015 13:39:52 -0500
From: Robert Sparks <rjsparks@nostrum.com>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.10; rv:31.0) Gecko/20100101 Thunderbird/31.6.0
MIME-Version: 1.0
To: "iesg@ietf.org" <iesg@ietf.org>, "<wgchairs@ietf.org>" <wgchairs@ietf.org>
Subject: Upcoming change to the Notify field for some documents
Content-Type: text/plain; charset="utf-8"; format="flowed"
Content-Transfer-Encoding: 7bit
Archived-At: <http://mailarchive.ietf.org/arch/msg/wgchairs/Wivj_AieOs1iYkeVY7LP0qm6lek>
X-BeenThere: wgchairs@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: Working Group Chairs <wgchairs.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/wgchairs>, <mailto:wgchairs-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/wgchairs/>
List-Post: <mailto:wgchairs@ietf.org>
List-Help: <mailto:wgchairs-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/wgchairs>, <mailto:wgchairs-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 15 Apr 2015 18:40:00 -0000
Working group chairs and IESG members - The next release of the datatracker will contain the first steps towards changing how a working group list gets copied when an AD enters a ballot position. Once that release is in place, I will be running a script that will scrub working group lists out of the Notify fields where they occur (276 documents at the moment). This is part of addressing the issue that several of you are experiencing with mail sent to the .all alias for a document going into moderation at your group's list because of an implicit destination. That script will email the WG personnel (chairs, shepherds, ads) to let them know what got changed. Below, you'll find an example of what will be sent to the personnel for one of the groups with the largest count of affected documents. Please read the text of the example - it explains the history leading up to this change in a little more detail. If you do not want the documents for your working group to be changed, reply to me ASAP (and be sure to copy your AD), and I will exclude your group from what the script will work on. If all goes well with the upcoming release, I expect to run this script late in the day tomorrow. RjS --------------------- EXAMPLE MESSAGE FOLLOWS (this is only an example - these changes have not yet been made to the production database) --------------------- To: <loa@pi.nu>, <swallow@cisco.com>, <rcallon@juniper.net>, <db3546@att.com> Subject: Removed the working group list address from the Notify field of 22 mpls drafts The Notify field for the documents listed at the end of this message were changed by removing the mpls mailing list address 'mpls@ietf.org'. For most documents, this address was introduced to the Notify field between November 2014 and March 2015 as part of the default value assigned when the document entered IESG processing. This was a first try at ensuring the working group sees ballot positions as the ADs enter them. However, it had several unintended consequences. In particular, since the contents of the Notify field are expanded into each document's .all alias, messages sent by individuals to the .all alias often ended in the list's moderation queue for having an implicit destination. Instead, the datatracker has been modified to send ballot positions to the working group list explicitly, under the balloting AD's control, and we are scrubbing the list addresses from the Notify fields. If you had included the working group list address in the Notify field for some reason other than it showing up by default during the above period, please use the datatracker to put it back into the field (or ask the secretariat to do so for you), and accept our apologies for the inconvenience. The affected documents for mpls appear below: https://datatracker.ietf.org/doc/draft-ietf-mpls-ldp-ipv6/ https://datatracker.ietf.org/doc/draft-ietf-mpls-lsp-ping-reply-mode-simple/ https://datatracker.ietf.org/doc/draft-ietf-mpls-seamless-mpls/ https://datatracker.ietf.org/doc/draft-ietf-mpls-lsp-ping-mpls-tp-oam-conf/ https://datatracker.ietf.org/doc/draft-kompella-mpls-rsvp-ecmp/ https://datatracker.ietf.org/doc/draft-ietf-mpls-seamless-mcast/ https://datatracker.ietf.org/doc/draft-ietf-mpls-tp-oam-id-mib/ https://datatracker.ietf.org/doc/draft-cheng-mpls-tp-shared-ring-protection/ https://datatracker.ietf.org/doc/rfc7510/ https://datatracker.ietf.org/doc/draft-ravisingh-mpls-el-for-seamless-mpls/ https://datatracker.ietf.org/doc/draft-ietf-mpls-proxy-lsp-ping/ https://datatracker.ietf.org/doc/draft-ietf-mpls-mldp-node-protection/ https://datatracker.ietf.org/doc/draft-mirsky-mpls-residence-time/ https://datatracker.ietf.org/doc/draft-kompella-mpls-larp/ https://datatracker.ietf.org/doc/draft-esale-mpls-app-aware-tldp/ https://datatracker.ietf.org/doc/draft-ietf-mpls-spring-entropy-label/ https://datatracker.ietf.org/doc/draft-bonica-mpls-self-ping/ https://datatracker.ietf.org/doc/draft-decraene-mpls-lsp-ping-registry/ https://datatracker.ietf.org/doc/draft-ietf-mpls-oam-ipv6-rao/ https://datatracker.ietf.org/doc/draft-kompella-mpls-rmr/ https://datatracker.ietf.org/doc/draft-ietf-mpls-lsp-ping-registry/ https://datatracker.ietf.org/doc/draft-ietf-mpls-entropy-lsp-ping/
- Upcoming change to the Notify field for some docu… Robert Sparks
- Re: Upcoming change to the Notify field for some … Robert Sparks
- RE: Upcoming change to the Notify field for some … DRAGE, Keith (Keith)
- Re: Upcoming change to the Notify field for some … Robert Sparks