Re: WG notifications of new IDs is causing problems

Michael Lee <Michael.Lee@neustar.biz> Fri, 16 November 2007 15:58 UTC

Return-path: <wgchairs-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1It3aY-00041y-Ck; Fri, 16 Nov 2007 10:58:38 -0500
Received: from [10.90.34.44] (helo=chiedprmail1.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1It3aV-0003tR-EB for wgchairs@ietf.org; Fri, 16 Nov 2007 10:58:35 -0500
Received: from ns7.neustar.com ([156.154.24.88] helo=neustar.com) by chiedprmail1.ietf.org with esmtp (Exim 4.43) id 1It3aU-0004dE-M1 for wgchairs@ietf.org; Fri, 16 Nov 2007 10:58:35 -0500
Received: from ([10.31.13.31]) by chihiron1.nc.neustar.com with ESMTP id 5202942.2578789; Fri, 16 Nov 2007 10:58:14 -0500
Received: from [10.31.13.125] ([10.31.13.125]) by stntexch12.cis.neustar.com with Microsoft SMTPSVC(6.0.3790.3959); Fri, 16 Nov 2007 10:58:13 -0500
In-Reply-To: <STNTEXCH11w4hVJbrzv00000dd8@stntexch11.cis.neustar.com>
References: <68tu4f$1lndld@sj-inbound-e.cisco.com> <XFE-SJC-21100zepDI800000ce4@xfe-sjc-211.amer.cisco.com> <473CC388.3090000@piuha.net> <A9678BFA-5B83-4BBF-AABD-7526E453C1C6@neustar.biz> <STNTEXCH11w4hVJbrzv00000dd8@stntexch11.cis.neustar.com>
Mime-Version: 1.0 (Apple Message framework v752.3)
Content-Type: multipart/alternative; boundary="Apple-Mail-2-25639580"
Message-Id: <A6445429-37A2-4945-9928-5326FAAF92D8@neustar.biz>
From: Michael Lee <Michael.Lee@neustar.biz>
Date: Fri, 16 Nov 2007 10:58:07 -0500
To: Russ Housley <housley@vigilsec.com>
X-Mailer: Apple Mail (2.752.3)
X-OriginalArrivalTime: 16 Nov 2007 15:58:13.0665 (UTC) FILETIME=[7E5B5110:01C82869]
X-Spam-Score: 0.0 (/)
X-Scan-Signature: e472ca43d56132790a46d9eefd95f0a5
Cc: Michael Lee <Michael.Lee@neustar.biz>, "Fuller, Barbara" <Barbara.Fuller@neustar.biz>, Jari Arkko <jari.arkko@piuha.net>, "Suleymanova, Dinara" <Dinara.Suleymanova@neustar.biz>, wgchairs@ietf.org
Subject: Re: WG notifications of new IDs is causing problems
X-BeenThere: wgchairs@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Working Group Chairs <wgchairs.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/wgchairs>, <mailto:wgchairs-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:wgchairs@ietf.org>
List-Help: <mailto:wgchairs-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/wgchairs>, <mailto:wgchairs-request@ietf.org?subject=subscribe>
Errors-To: wgchairs-bounces@ietf.org

WG CC on #2 below has been turned off.

Regards,
Michael Lee,
IETF Secretariat.

On Nov 16, 2007, at 9:22 AM, Russ Housley wrote:

> This seems to be the source of the problem, #1 and #2 both include  
> the WG mail list, which is to notices for the same action.  Can we  
> turn off the WG CC on #2?
>
> Russ
>
> At 05:36 PM 11/15/2007, Michael Lee wrote:
>> For a working group document submission, the submission tool send  
>> out following announcement/notifications:
>>
>> 1. I-D Action announcement to the I-D announcement list and wg  
>> mailing list.
>> 2. A new version notification to the submitter and authors of the  
>> document. WG list gets cc'ed.
>> 3. If the document has been requested for publish and evaluated by  
>> the IESG, a notification is sent to the shepherding AD and  
>> whomever the shepherding AD has indicated within the ID Tracker  
>> (WG mailing list is a default list in this field.)
>>
>> Hope this message can clear some vagueness regarding the issue.
>>
>> BTW, draft-ietf-geopriv-revised-civic-lo@tools.ietf.org was cc'ed  
>> because a shepherding AD indicated this address in ID tracker.
>>
>> Best regards,
>> Michael Lee,
>> IETF Secretariat.
>>
>> On Nov 15, 2007, at 5:09 PM, Jari Arkko wrote:
>>
>>> James, Russ,
>>>
>>> > Geopriv and SIPPING have a lot of of these right now, so this  
>>> issue
>>> > isn't just to one draft, it's to an entire class of message  
>>> type - and
>>> > I find it annoying and makes reading through the 150+ messages  
>>> I get
>>> > each day less efficient instead of more efficient *and* makes  
>>> tracking
>>> > threads nearly impossible.
>>>
>>> I looked at geopriv and sipping archives; many of the messages in
>>> recent weeks were sent by the authors themselves, eg.
>>>
>>>   http://www1.ietf.org/mail-archive/web/geopriv/current/ 
>>> msg04649.html
>>>   http://www1.ietf.org/mail-archive/web/geopriv/current/ 
>>> msg04665.html
>>>   http://www1.ietf.org/mail-archive/web/sipping/current/ 
>>> msg14735.html
>>>
>>> But I also found cases where the submission tool sent the message:
>>>
>>>    http://www1.ietf.org/mail-archive/web/geopriv/current/ 
>>> msg04573.html
>>>    http://www1.ietf.org/mail-archive/web/sipping/current/ 
>>> msg14726.html
>>>
>>> Russ' theory was that this could be an error in the tracker's e-mail
>>> notification
>>> field. But at least for this draft (geopriv-revised-civic-lo) the  
>>> data
>>> seemed
>>> correct. I also tested whether the tool used for deriving the  
>>> addresses for
>>> draft-ietf-geopriv-revised-civic-lo@tools.ietf.org was somehow at  
>>> fault, but
>>> it seemed to list just the authors, as it should. Same for  
>>> sipping-pending-
>>> additions.
>>>
>>> So, maybe this comes from the submission tool, an error in the  
>>> secretariat's
>>> internal database (that I can't see), or I missed something.
>>>
>>> Jari