
From nobody Thu Oct  1 14:26:51 2015
Return-Path: <rse@rfc-editor.org>
X-Original-To: tools-development@ietfa.amsl.com
Delivered-To: tools-development@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id D7FD81A898F; Thu,  1 Oct 2015 14:26:46 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.901
X-Spam-Level: 
X-Spam-Status: No, score=-1.901 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, SPF_PASS=-0.001] 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 mIBJ-YoShHHI; Thu,  1 Oct 2015 14:26:44 -0700 (PDT)
Received: from mail.amsl.com (mail.amsl.com [IPv6:2001:1900:3001:11::28]) by ietfa.amsl.com (Postfix) with ESMTP id A90891A8990; Thu,  1 Oct 2015 14:26:44 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by c8a.amsl.com (Postfix) with ESMTP id B7C7A1E5A21; Thu,  1 Oct 2015 14:26:23 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
Received: from c8a.amsl.com ([127.0.0.1]) by localhost (c8a.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id lW5OlXYBq40M; Thu,  1 Oct 2015 14:26:23 -0700 (PDT)
Received: from Heathers-MacBook-Pro.local (174-125-126-229.dyn.centurytel.net [174.125.126.229]) by c8a.amsl.com (Postfix) with ESMTPSA id 6A6A11E5A07; Thu,  1 Oct 2015 14:26:23 -0700 (PDT)
From: "Heather Flanagan (RFC Series Editor)" <rse@rfc-editor.org>
X-Enigmail-Draft-Status: N1110
To: iab@iab.org, iesg@ietf.org, rsoc@iab.org, tools-development@ietf.org
Message-ID: <560DA517.9010004@rfc-editor.org>
Date: Thu, 1 Oct 2015 14:26:47 -0700
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.10; rv:38.0) Gecko/20100101 Thunderbird/38.2.0
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: quoted-printable
Archived-At: <http://mailarchive.ietf.org/arch/msg/tools-development/7t29WwNI6UJPfrZydDvfXqd7Cjk>
Subject: [TOOLS-DEVELOPMENT] New RFC Editor Website - Live!
X-BeenThere: tools-development@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: Tools Development list server <tools-development.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/tools-development>, <mailto:tools-development-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/tools-development/>
List-Post: <mailto:tools-development@ietf.org>
List-Help: <mailto:tools-development-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/tools-development>, <mailto:tools-development-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 01 Oct 2015 21:26:47 -0000

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256

Hello RSOC, IAB, IESG, and Tools team,

Below is a note I'm about to send out to rfc-interest. Many thanks to
the project team that made this happen!

- ------

The new RFC Editor website <https://www.rfc-editor.org> is up and
running. Thank you to all who have submitted comments against the
preview. We are tracking the comments on the RFC Series Editor wiki
<https://www.rfc-editor.org/rse/wiki/doku.php?id=3Dwebfeedback> and
reviewing them as part of our ongoing plans to improve the site.

Because this is an entirely new site, and new deployment, we expect that
there will be the odd problem discovered.  AMS staff will be working to
resolve any issues as soon as possible.

If you have additional feedback about the new website, please post to
rfc-interest@rfc-editor.org. If you have a bug report, please send it to
webmaster@rfc-editor.org.

Thank you again for your support during this transition,
Heather Flanagan
-----BEGIN PGP SIGNATURE-----
Version: GnuPG/MacGPG2 v2
Comment: GPGTools - http://gpgtools.org

iQEcBAEBCAAGBQJWDaUXAAoJEER/xjINbZoGSm8IAIlly9GgpmvPvi5Uhmh+LUuV
YX2KOGhl+gKj3+bjq8W5wshjIAdIfXIMY4un+DH/h20kAHPoVR0b1hS8pdXi50ZQ
AEokoI5U8lKKneFSbor3kLZh/x7STh00v64isB3G/1wU3t2hZ/1bLiS/ZwZXn2BS
2+wH+ry0XXZ2yV/Z3T0+rGDH8eO2zC3ZsqKbjZLFnW1NEF/PJPowSKA3t9CCu88f
JtWtps+HdHK90hayPihxyFwUCDk/kaY6Jt84PO/at4cMW0rZZhRpDddI387tYf/c
jpdsunfUDKnhHBLlJ/vj4V/6e+Ebqb4RJt4oNlIYd/6oR4tT2Ur2EhIuiZhjlg0=3D
=3Dx9Ru
-----END PGP SIGNATURE-----



From nobody Fri Oct  2 13:40:55 2015
Return-Path: <lberger@labn.net>
X-Original-To: tools-development@ietfa.amsl.com
Delivered-To: tools-development@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id DB9471B2DC6 for <tools-development@ietfa.amsl.com>; Fri,  2 Oct 2015 13:40:54 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 1.033
X-Spam-Level: *
X-Spam-Status: No, score=1.033 tagged_above=-999 required=5 tests=[BAYES_50=0.8, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, IP_NOT_FRIENDLY=0.334, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001] autolearn=no
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 9KHI109svEJs for <tools-development@ietfa.amsl.com>; Fri,  2 Oct 2015 13:40:53 -0700 (PDT)
Received: from gproxy2-pub.mail.unifiedlayer.com (gproxy2-pub.mail.unifiedlayer.com [69.89.18.3]) by ietfa.amsl.com (Postfix) with SMTP id 9B8E81B2DC2 for <tools-development@ietf.org>; Fri,  2 Oct 2015 13:40:53 -0700 (PDT)
Received: (qmail 29903 invoked by uid 0); 2 Oct 2015 20:40:53 -0000
Received: from unknown (HELO cmgw3) (10.0.90.84) by gproxy2.mail.unifiedlayer.com with SMTP; 2 Oct 2015 20:40:53 -0000
Received: from box313.bluehost.com ([69.89.31.113]) by cmgw3 with  id QSgn1r00E2SSUrH01SgqCN; Fri, 02 Oct 2015 20:40:51 -0600
X-Authority-Analysis: v=2.1 cv=Zs1+dbLG c=1 sm=1 tr=0 a=h1BC+oY+fLhyFmnTBx92Jg==:117 a=wU2YTnxGAAAA:8 a=cNaOj0WVAAAA:8 a=IkcTkHD0fZMA:10 a=-NfooI8aBGcA:10 a=uEJ9t1CZtbIA:10 a=5lJygRwiOn0A:10 a=RrtgN0fCtKN0uuJudJMA:9 a=QEXdDO2ut3YA:10
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=labn.net; s=default;  h=Content-Transfer-Encoding:Content-Type:MIME-Version:Date:Message-ID:Subject:From:To; bh=yzKXDYNHloCyPL9jLlKX27oJBh5d9aZmMOJIEqbKXNM=;  b=SKimYMwfe42afph3u8Um82d3Acl7o1INYUVf551p6pp5G5vn30k9pFpL/n+JW17nlr/HwdCvL3j9C3U7uq23TsDwe0wtTy7ArVH9+8BHvp+sFHl9FS7lDg2xOKv7+l/I;
Received: from box313.bluehost.com ([69.89.31.113]:45025 helo=[127.0.0.1]) by box313.bluehost.com with esmtpa (Exim 4.84) (envelope-from <lberger@labn.net>) id 1Zi78K-0007VI-RX for tools-development@ietf.org; Fri, 02 Oct 2015 14:40:48 -0600
To: IETF Tools Development <tools-development@ietf.org>
From: Lou Berger <lberger@labn.net>
Message-ID: <560EEBCA.2020409@labn.net>
Date: Fri, 2 Oct 2015 16:40:42 -0400
User-Agent: Mozilla/5.0 (Windows NT 6.3; WOW64; rv:38.0) Gecko/20100101 Thunderbird/38.2.0
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit
X-Identified-User: {1038:box313.bluehost.com:labnmobi:labn.net} {sentby:smtp auth 69.89.31.113 authed with lberger@labn.net}
Archived-At: <http://mailarchive.ietf.org/arch/msg/tools-development/6MH6vs8jIZiLQg7qNgTVmaboeE8>
Subject: [TOOLS-DEVELOPMENT] milestones listed in reverse?
X-BeenThere: tools-development@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: Tools Development list server <tools-development.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/tools-development>, <mailto:tools-development-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/tools-development/>
List-Post: <mailto:tools-development@ietf.org>
List-Help: <mailto:tools-development-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/tools-development>, <mailto:tools-development-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 02 Oct 2015 20:40:55 -0000

Hi,
    Does anyone know why the data tracker has started listing milestones
in reverse (with last date first)?

Thanks,
Lou



From nobody Fri Oct  2 14:15:34 2015
Return-Path: <rjsparks@nostrum.com>
X-Original-To: tools-development@ietfa.amsl.com
Delivered-To: tools-development@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 7B86C1B2ED7 for <tools-development@ietfa.amsl.com>; Fri,  2 Oct 2015 14:15:33 -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 OmzK03vbuj6r for <tools-development@ietfa.amsl.com>; Fri,  2 Oct 2015 14:15:32 -0700 (PDT)
Received: from nostrum.com (raven-v6.nostrum.com [IPv6:2001:470:d:1130::1]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 5FE681B2ED5 for <tools-development@ietf.org>; Fri,  2 Oct 2015 14:15:32 -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.2/8.14.9) with ESMTPSA id t92LFTVI076885 (version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128 verify=OK); Fri, 2 Oct 2015 16:15:31 -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
To: Lou Berger <lberger@labn.net>, IETF Tools Development <tools-development@ietf.org>, "Eggert, Lars" <lars@netapp.com>
References: <560EEBCA.2020409@labn.net>
From: Robert Sparks <rjsparks@nostrum.com>
Message-ID: <560EF3EC.6060608@nostrum.com>
Date: Fri, 2 Oct 2015 16:15:24 -0500
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.10; rv:38.0) Gecko/20100101 Thunderbird/38.3.0
MIME-Version: 1.0
In-Reply-To: <560EEBCA.2020409@labn.net>
Content-Type: text/plain; charset=windows-1252; format=flowed
Content-Transfer-Encoding: 7bit
Archived-At: <http://mailarchive.ietf.org/arch/msg/tools-development/4AAgaVQgMm1JV7fUy43if_1P294>
Subject: Re: [TOOLS-DEVELOPMENT] milestones listed in reverse?
X-BeenThere: tools-development@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: Tools Development list server <tools-development.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/tools-development>, <mailto:tools-development-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/tools-development/>
List-Post: <mailto:tools-development@ietf.org>
List-Help: <mailto:tools-development-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/tools-development>, <mailto:tools-development-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 02 Oct 2015 21:15:33 -0000

Well, it's not super recent - it came in with the facelift, so it should 
have been this way since April.

Digging into the history, it looks like the change came from Lars' 
original facelift work.

Thinking a bit about it, I think having them listed in the current order 
(future things first, very old things last) is more useful than the 
other way around - a reader looking at most charters will find the 
relevant things more quickly.

RjS




On 10/2/15 3:40 PM, Lou Berger wrote:
> Hi,
>      Does anyone know why the data tracker has started listing milestones
> in reverse (with last date first)?
>
> Thanks,
> Lou
>
>
> _______________________________________________
> TOOLS-DEVELOPMENT mailing list
> TOOLS-DEVELOPMENT@ietf.org
> https://www.ietf.org/mailman/listinfo/tools-development


From nobody Fri Oct  2 14:28:51 2015
Return-Path: <lberger@labn.net>
X-Original-To: tools-development@ietfa.amsl.com
Delivered-To: tools-development@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id BE4671A893E for <tools-development@ietfa.amsl.com>; Fri,  2 Oct 2015 14:28:50 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.267
X-Spam-Level: 
X-Spam-Status: No, score=-0.267 tagged_above=-999 required=5 tests=[BAYES_05=-0.5, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, IP_NOT_FRIENDLY=0.334, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001] autolearn=no
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 x5b_k9QtfMR9 for <tools-development@ietfa.amsl.com>; Fri,  2 Oct 2015 14:28:49 -0700 (PDT)
Received: from gproxy1-pub.mail.unifiedlayer.com (gproxy1-pub.mail.unifiedlayer.com [69.89.25.95]) by ietfa.amsl.com (Postfix) with SMTP id EB3271A88F6 for <tools-development@ietf.org>; Fri,  2 Oct 2015 14:28:47 -0700 (PDT)
Received: (qmail 19831 invoked by uid 0); 2 Oct 2015 21:28:37 -0000
Received: from unknown (HELO cmgw3) (10.0.90.84) by gproxy1.mail.unifiedlayer.com with SMTP; 2 Oct 2015 21:28:37 -0000
Received: from box313.bluehost.com ([69.89.31.113]) by cmgw3 with  id QTUW1r00j2SSUrH01TUZRa; Fri, 02 Oct 2015 21:28:35 -0600
X-Authority-Analysis: v=2.1 cv=Zs1+dbLG c=1 sm=1 tr=0 a=h1BC+oY+fLhyFmnTBx92Jg==:117 a=wU2YTnxGAAAA:8 a=cNaOj0WVAAAA:8 a=N659UExz7-8A:10 a=-NfooI8aBGcA:10 a=uEJ9t1CZtbIA:10 a=5lJygRwiOn0A:10 a=48vgC7mUAAAA:8 a=8-s8CV-4f3AND3vTMSkA:9 a=pILNOxqGKmIA:10
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=labn.net; s=default;  h=Content-Transfer-Encoding:Content-Type:In-Reply-To:MIME-Version:Date:Message-ID:From:References:To:Subject; bh=uJR0dOF7rF+rrvtLkDLX1W7JLfP98cO94fVDP5AhnMA=;  b=fHekRJL34oBA4vZSz4Z5YnMbPAGlxdci4JxoPmrtKuD49g02pSIGzEHKFFQH7SJN4h8ug8M/FVT7EapHYqiHoxXCIG03a+RUAHJV+I8qgFFnSjsVcwV8+sJ3ri13Litk;
Received: from box313.bluehost.com ([69.89.31.113]:48082 helo=[127.0.0.1]) by box313.bluehost.com with esmtpa (Exim 4.84) (envelope-from <lberger@labn.net>) id 1Zi7sW-0007FJ-0P; Fri, 02 Oct 2015 15:28:32 -0600
To: Robert Sparks <rjsparks@nostrum.com>, IETF Tools Development <tools-development@ietf.org>, "Eggert, Lars" <lars@netapp.com>
References: <560EEBCA.2020409@labn.net> <560EF3EC.6060608@nostrum.com>
From: Lou Berger <lberger@labn.net>
X-Enigmail-Draft-Status: N1110
Message-ID: <560EF6F8.7020908@labn.net>
Date: Fri, 2 Oct 2015 17:28:24 -0400
User-Agent: Mozilla/5.0 (Windows NT 6.3; WOW64; rv:38.0) Gecko/20100101 Thunderbird/38.2.0
MIME-Version: 1.0
In-Reply-To: <560EF3EC.6060608@nostrum.com>
Content-Type: text/plain; charset=windows-1252
Content-Transfer-Encoding: 7bit
X-Identified-User: {1038:box313.bluehost.com:labnmobi:labn.net} {sentby:smtp auth 69.89.31.113 authed with lberger@labn.net}
Archived-At: <http://mailarchive.ietf.org/arch/msg/tools-development/9g_hOtmU0Pm8VRKWhJPtAJPt_rg>
Subject: Re: [TOOLS-DEVELOPMENT] milestones listed in reverse?
X-BeenThere: tools-development@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: Tools Development list server <tools-development.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/tools-development>, <mailto:tools-development-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/tools-development/>
List-Post: <mailto:tools-development@ietf.org>
List-Help: <mailto:tools-development-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/tools-development>, <mailto:tools-development-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 02 Oct 2015 21:28:50 -0000

Hi Robert,

On 10/2/2015 5:15 PM, Robert Sparks wrote:
> Well, it's not super recent - it came in with the facelift, so it should 
> have been this way since April.

Frankly, I typically look at charter and deliverables via the tools page
and it still has it the old way.  I had to review the milestones for a
new WG and this is the first time I noticed it.  The AD I was talking to
must do things the same way I do as she too commented on the surprising
ordering.

> Digging into the history, it looks like the change came from Lars' 
> original facelift work.
>
> Thinking a bit about it, I think having them listed in the current order 
> (future things first, very old things last) is more useful than the 
> other way around - a reader looking at most charters will find the 
> relevant things more quickly.

I guess this is a matter of personal preference and habit.  I typically
only look at milestones to see what needs updating and what's coming
up.  This typically involves looking for the first not 'done' items.   
The new order makes this more cumbersome (need to go the end and read
up.)  It's not really a big deal for me as I really just use the tools
page. 

Note that when you go to edit the milestones, they are still
(thankfully) in chronological order.

Although the new UI is really painful when entering multiple new
milestones -- a tsv or csv upload feature would be really nice -- just
wishful thinking.

Thanks,
Lou

>
> RjS
>
>
>
>
> On 10/2/15 3:40 PM, Lou Berger wrote:
>> Hi,
>>      Does anyone know why the data tracker has started listing milestones
>> in reverse (with last date first)?
>>
>> Thanks,
>> Lou
>>
>>
>> _______________________________________________
>> TOOLS-DEVELOPMENT mailing list
>> TOOLS-DEVELOPMENT@ietf.org
>> https://www.ietf.org/mailman/listinfo/tools-development
>



From nobody Fri Oct  9 09:29:53 2015
Return-Path: <messenger@webex.com>
X-Original-To: tools-development@ietfa.amsl.com
Delivered-To: tools-development@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 0742F1B46DF for <tools-development@ietfa.amsl.com>; Fri,  9 Oct 2015 09:29:51 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -8.91
X-Spam-Level: 
X-Spam-Status: No, score=-8.91 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, GB_I_INVITATION=-2, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_HI=-5, SPF_PASS=-0.001, 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 OSZR7qaEnaD9 for <tools-development@ietfa.amsl.com>; Fri,  9 Oct 2015 09:29:49 -0700 (PDT)
Received: from sjmda11.webex.com (sjmda11.webex.com [64.68.124.128]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 44B731B465E for <tools-development@ietf.org>; Fri,  9 Oct 2015 09:29:49 -0700 (PDT)
Received: from jsj2tc402.webex.com (sjc02-wxp00-lbace03-core-vl120-np10b-1.webex.com [64.68.121.236]) by sjmda11.webex.com (Postfix) with ESMTP id E9C52C5199 for <tools-development@ietf.org>; Fri,  9 Oct 2015 16:29:48 +0000 (GMT)
Received: from jsj2tc402.webex.com (localhost [127.0.0.1]) by jsj2tc402.webex.com (Postfix) with ESMTP id E18EB80043 for <tools-development@ietf.org>; Fri,  9 Oct 2015 16:29:48 +0000 (GMT)
Date: Fri, 9 Oct 2015 16:29:48 +0000 (GMT)
From: Ray Pelletier <messenger@webex.com>
To: tools-development@ietf.org
Message-ID: <788772041.32647.1444408188922.JavaMail.nobody@jsj2tc402.webex.com>
MIME-Version: 1.0
Content-Type: multipart/Mixed;  boundary="----=_Part_32645_117498147.1444408188921"
X-Priority: 3
Importance: normal
Archived-At: <http://mailarchive.ietf.org/arch/msg/tools-development/tEATrJ5s9BqtF1QY0vr_Y-Jy8dc>
Subject: [TOOLS-DEVELOPMENT] WebEx meeting invitation: Tools Cmte
X-BeenThere: tools-development@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
Reply-To: rpelletier@isoc.org
List-Id: Tools Development list server <tools-development.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/tools-development>, <mailto:tools-development-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/tools-development/>
List-Post: <mailto:tools-development@ietf.org>
List-Help: <mailto:tools-development-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/tools-development>, <mailto:tools-development-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 09 Oct 2015 16:29:51 -0000

------=_Part_32645_117498147.1444408188921
Content-Type: multipart/Alternative; 
	boundary="----=_Part_32646_1253885036.1444408188921"

------=_Part_32646_1253885036.1444408188921
Content-Type: text/plain;charset=UTF-8
Content-Transfer-Encoding: base64

CkhlbGxvLAoKUmF5IFBlbGxldGllciBpbnZpdGVzIHlvdSB0byBqb2luIHRoaXMgV2ViRXggbWVl
dGluZy4KCgpUb29scyBDbXRlClR1ZXNkYXksIE9jdG9iZXIgMTMsIDIwMTUKMTowMCBwbSAgfCAg
RWFzdGVybiBEYXlsaWdodCBUaW1lIChOZXcgWW9yaywgR01ULTA0OjAwKSAgfCAgMSBocgoKCkpP
SU4gV0VCRVggTUVFVElORwpodHRwczovL3dvcmtncmVlbi53ZWJleC5jb20vd29ya2dyZWVuL2ou
cGhwP01USUQ9bWQwM2Y1NzhmNDZkYjljZDNjMzAxMmZmZjUxMTU3ZjI3Ck1lZXRpbmcgbnVtYmVy
OiA4MjQgNTc1IDk4NQoKDQpKT0lOIEJZIFBIT05FDQoxLTg3Ny02NjgtNDQ5MCBDYWxsLWluIHRv
bGwtZnJlZSBudW1iZXIgKFVTL0NhbmFkYSkgCjEtNDA4LTc5Mi02MzAwIENhbGwtaW4gdG9sbCBu
dW1iZXIgKFVTL0NhbmFkYSkKQWNjZXNzIGNvZGU6IDgyNCA1NzUgOTg1CgpHbG9iYWwgY2FsbC1p
biBudW1iZXJzOgpodHRwczovL3dvcmtncmVlbi53ZWJleC5jb20vd29ya2dyZWVuL2dsb2JhbGNh
bGxpbi5waHA/c2VydmljZVR5cGU9TUMmRUQ9MzE3OTM0NDI3JnRvbGxGcmVlPTEKClRvbGwtZnJl
ZSBkaWFsaW5nIHJlc3RyaWN0aW9uczogCmh0dHA6Ly93d3cud2ViZXguY29tL3BkZi90b2xsZnJl
ZV9yZXN0cmljdGlvbnMucGRmDQoNCgpBZGQgdGhpcyBtZWV0aW5nIHRvIHlvdXIgY2FsZW5kYXI6
Cmh0dHBzOi8vd29ya2dyZWVuLndlYmV4LmNvbS93b3JrZ3JlZW4vai5waHA/TVRJRD1tN2MyN2Q3
NDI4N2RhNjFmZWUxNzVjYWJlYmZhNDkwYzINCg0KCkNhbid0IGpvaW4gdGhlIG1lZXRpbmc/IENv
bnRhY3Qgc3VwcG9ydCBoZXJlOgpodHRwczovL3dvcmtncmVlbi53ZWJleC5jb20vd29ya2dyZWVu
L21jCgoKSU1QT1JUQU5UIE5PVElDRTogUGxlYXNlIG5vdGUgdGhhdCB0aGlzIFdlYkV4IHNlcnZp
Y2UgYWxsb3dzIGF1ZGlvIGFuZCBvdGhlciBpbmZvcm1hdGlvbiBzZW50IGR1cmluZyB0aGUgc2Vz
c2lvbiB0byBiZSByZWNvcmRlZCwgd2hpY2ggbWF5IGJlIGRpc2NvdmVyYWJsZSBpbiBhIGxlZ2Fs
IG1hdHRlci4gQnkgam9pbmluZyB0aGlzIHNlc3Npb24sIHlvdSBhdXRvbWF0aWNhbGx5IGNvbnNl
bnQgdG8gc3VjaCByZWNvcmRpbmdzLiBJZiB5b3UgZG8gbm90IGNvbnNlbnQgdG8gYmVpbmcgcmVj
b3JkZWQsIGRpc2N1c3MgeW91ciBjb25jZXJucyB3aXRoIHRoZSBob3N0IG9yIGRvIG5vdCBqb2lu
IHRoZSBzZXNzaW9uLgo=
------=_Part_32646_1253885036.1444408188921
Content-Type: text/html;charset=UTF-8
Content-Transfer-Encoding: base64

PG1ldGEgaHR0cC1lcXVpdj0iQ29udGVudC1UeXBlIiBjb250ZW50PSJ0ZXh0L2h0bWw7IGNoYXJz
ZXQ9dXRmLTgiPjxtZXRhIG5hbWU9InZpZXdwb3J0IiBjb250ZW50PSJ3aWR0aD1kZXZpY2Utd2lk
dGgsIGluaXRpYWwtc2NhbGU9MSIgLz48Ym9keT48c3R5bGUgdHlwZT0idGV4dC9jc3MiPgpkaXYs
cCx0ZCxzcGFuIHt3b3JkLXdyYXA6IGJyZWFrLXdvcmQ7d29yZC1icmVhazogbm9ybWFsO30KCnRh
YmxlIHtib3JkZXItY29sbGFwc2U6IHNlcGFyYXRlOyBib3JkZXI6IDA7Ym9yZGVyLXNwYWNpbmc6
IDA7Ym9yZGVyLWNvbG9yOiB3aGl0ZTsgd2lkdGg6MTAwJSFpbXBvcnRhbnQ7d2lkdGg6NTI1cHg7
IG1heC13aWR0aDo1MjVweCFpbXBvcnRhbnQ7IG1pbi13aWR0aDogMjc5cHghaW1wb3J0YW50O30K
dHIge2xpbmUtaGVpZ2h0OiAyMHB4O30KCnRkLGEge2ZvbnQtc2l6ZTogMTVweDtmb250LWZhbWls
eTogQXJpYWw7Y29sb3I6ICM2NjY2NjY7cGFkZGluZzowO30KPC9zdHlsZT4KCjx0YWJsZSBzdHls
ZT0icGFkZGluZzowOyBtYXJnaW46MCIgd2lkdGg9IjEwMCUiIGFsaWduPSJsZWZ0Ij4KICAgPHRy
PgogICAgICA8dGQgc3R5bGU9InBhZGRpbmctdG9wOjVweDsiPgogICAgICAgIDx0YWJsZSBzdHls
ZT0id2lkdGg6IDUyNXB4O21hcmdpbi1sZWZ0OjVweCIgYWxpZ249ImxlZnQiPgoJCQk8dHI+CgkJ
CQk8dGQgdmFsaWduPSJ0b3AiPgoKPHRhYmxlPgogICAgICAgPHRyPgogICAgICAgICAgPHRkIHN0
eWxlPSJmb250LXNpemU6IDE1cHg7Zm9udC1mYW1pbHk6IEFyaWFsO2NvbG9yOiM0RDRENEQiPgog
ICAgICAgICAgICAgSGVsbG8sCiAgICAgICAgICA8L3RkPgogICAgICAgPC90cj4KICAgICAgIDx0
cj4KICAgICAgICAgICA8dGQgc3R5bGU9ImZvbnQtc2l6ZTogMTVweDtmb250LWZhbWlseTogQXJp
YWw7Y29sb3I6IzRENEQ0RDtwYWRkaW5nLXRvcDoxMHB4OyI+CiAgICAgICAgICAgICAgICBSYXkg
UGVsbGV0aWVyIGludml0ZXMgeW91IHRvIGpvaW4gdGhpcyBXZWJFeCBtZWV0aW5nLgogICAgICAg
ICAgICAgICAgCSAgICAgICAgICAgPC90ZD4KICAgICAgPC90cj4KPC90YWJsZT4KCgoKCjx0YWJs
ZT48dHIgc3R5bGU9ImxpbmUtaGVpZ2h0OiAyMHB4OyI+PHRkIHN0eWxlPSJoZWlnaHQ6MjBweCI+
Jm5ic3A7PC90ZD48L3RyPjwvdGFibGU+CgkJCQkJCTx0YWJsZSAgd2lkdGg9IjEwMCUiPgoJCQkJ
CQkJPHRyPgoJCQkJCQkJCTx0ZCBzdHlsZT0iZm9udC1zaXplOjE2cHg7IGNvbG9yOiM0RDRENEQi
PgoJCQkJCQkJCQk8Yj5Ub29scyBDbXRlPC9iPgoJCQkJCQkJCTwvdGQ+CgkJCQkJCQk8L3RyPgoJ
CQkJCQkJPHRyIHN0eWxlPSJtYXJnaW46MHB4Ij4KCQkJCQkJCQk8dGQ+VHVlc2RheSwgT2N0b2Jl
ciAxMywgMjAxNQoJCQkJCQkJCTwvdGQ+CgkJCQkJCQk8L3RyPgoJCQkJCQkJPHRyIHN0eWxlPSJt
YXJnaW46MHB4Ij4KCQkJCQkJCQk8dGQ+MTowMCBwbSZuYnNwOyZuYnNwO3wmbmJzcDsmbmJzcDtF
YXN0ZXJuIERheWxpZ2h0IFRpbWUgKE5ldyBZb3JrLCBHTVQtMDQ6MDApJm5ic3A7Jm5ic3A7fCZu
YnNwOyZuYnNwOzEgaHIKCQkJCQkJCQk8L3RkPgoJCQkJCQkJPC90cj4KCQkJCQkJPC90YWJsZT4K
Cjx0YWJsZT48dHIgc3R5bGU9ImxpbmUtaGVpZ2h0OiAyMHB4OyI+PHRkIHN0eWxlPSJoZWlnaHQ6
MjBweCI+Jm5ic3A7PC90ZD48L3RyPjwvdGFibGU+CgkJCQkJCTx0YWJsZSBzdHlsZT0id2lkdGg6
YXV0bzsgd2lkdGg6YXV0byFpbXBvcnRhbnQiPgoJCQkJCQkJPHRyPgoJCQkJCQkJCTx0ZCBzdHls
ZT0iY29sb3I6IzAwQUZGOTtmb250LXNpemU6MTZweCI+CgkJCQkJCQkJCTxhIGhyZWY9Imh0dHBz
Oi8vd29ya2dyZWVuLndlYmV4LmNvbS93b3JrZ3JlZW4vai5waHA/TVRJRD1tZDAzZjU3OGY0NmRi
OWNkM2MzMDEyZmZmNTExNTdmMjciCgkJCQkJCQkJCQlzdHlsZT0idGV4dC1kZWNvcmF0aW9uOm5v
bmU7Zm9udC1zaXplOjE2cHg7Y29sb3I6IzAwQUZGOSI+CgkJCQkJCQkJCQk8Yj5Kb2luIFdlYkV4
IG1lZXRpbmc8L2I+CgkJCQkJCQkJCTwvYT4KCQkJCQkJCQk8L3RkPgoJCQkJCQkJPC90cj4KCQkJ
CQkJPC90YWJsZT4KCQkJCQkJPHRhYmxlIHN0eWxlPSJ3aWR0aDphdXRvOyB3aWR0aDphdXRvIWlt
cG9ydGFudCI+CgkJCQkJCQk8dHIgc3R5bGU9Im1hcmdpbjowcHgiPgoJCQkJCQkJCTx0ZCBzdHls
ZT0icGFkZGluZy1yaWdodDogNXB4OyI+CgkJCQkJCQkJCU1lZXRpbmcgbnVtYmVyOgoJCQkJCQkJ
CTwvdGQ+CgkJCQkJCQkJPHRkPjgyNCA1NzUgOTg1CgkJCQkJCQkJPC90ZD4KCQkJCQkJCTwvdHI+
CgkJCQkJCQk8dHI+CgkJCQkJCQkJPHRkIHN0eWxlPSJwYWRkaW5nLXJpZ2h0OiA1cHg7Ij48L3Rk
PgoJCQkJCQkJCTx0ZD48L3RkPgoJCQkJCQkJPC90cj4KCQkJCQkJPC90YWJsZT4KCgoKCQoKCTx0
YWJsZT48dHIgc3R5bGU9ImxpbmUtaGVpZ2h0OjIwcHgiPjx0ZCBzdHlsZT0iaGVpZ2h0OjIwcHgi
PiZuYnNwOzwvdGQ+PC90cj48L3RhYmxlPjx0YWJsZT48dHI+PHRkIHN0eWxlPSJmb250LXNpemU6
MTZweCI+PGI+Sm9pbiBieSBwaG9uZTwvYj48L3RkPjwvdHI+PHRyIHN0eWxlPSJtYXJnaW46MHB4
Ij48dGQ+PGI+MS04NzctNjY4LTQ0OTA8L2I+Jm5ic3A7Q2FsbC1pbiB0b2xsLWZyZWUgbnVtYmVy
IChVUy9DYW5hZGEpPC90ZD48L3RyPjx0ciBzdHlsZT0ibWFyZ2luOjBweCI+PHRkPjxiPjEtNDA4
LTc5Mi02MzAwPC9iPiZuYnNwO0NhbGwtaW4gdG9sbCBudW1iZXIgKFVTL0NhbmFkYSk8L3RkPjwv
dHI+PHRyIHN0eWxlPSJtYXJnaW46MHB4Ij48dGQ+QWNjZXNzIGNvZGU6Jm5ic3A7ODI0IDU3NSA5
ODU8L3RkPjwvdHI+PHRyIHN0eWxlPSJtYXJnaW46MHB4Ij48dGQ+PGEgaHJlZj0iaHR0cHM6Ly93
b3JrZ3JlZW4ud2ViZXguY29tL3dvcmtncmVlbi9nbG9iYWxjYWxsaW4ucGhwP3NlcnZpY2VUeXBl
PU1DJkVEPTMxNzkzNDQyNyZ0b2xsRnJlZT0xIiBzdHlsZT0idGV4dC1kZWNvcmF0aW9uOm5vbmU7
Zm9udC1zaXplOjEzcHg7Y29sb3I6IzAwQUZGOSI+R2xvYmFsIGNhbGwtaW4gbnVtYmVyczwvYT4m
bmJzcDsmbmJzcDt8Jm5ic3A7Jm5ic3A7PGEgaHJlZj0iaHR0cDovL3d3dy53ZWJleC5jb20vcGRm
L3RvbGxmcmVlX3Jlc3RyaWN0aW9ucy5wZGYiIHN0eWxlPSJ0ZXh0LWRlY29yYXRpb246bm9uZTtm
b250LXNpemU6MTNweDtjb2xvcjojMDBBRkY5OyI+VG9sbC1mcmVlIGNhbGxpbmcgcmVzdHJpY3Rp
b25zPC9hPjwvdGQ+PC90cj48L3RhYmxlPgoKCQkJCQk8dGFibGU+PHRyIHN0eWxlPSJsaW5lLWhl
aWdodDoyMHB4Ij48dGQgc3R5bGU9ImhlaWdodDoyMHB4Ij4mbmJzcDs8L3RkPjwvdHI+PC90YWJs
ZT48dGFibGU+PHRyPjx0ZCBzdHlsZT0iZm9udC1zaXplOjEzcHgiPjxhIGhyZWY9Imh0dHBzOi8v
d29ya2dyZWVuLndlYmV4LmNvbS93b3JrZ3JlZW4vai5waHA/TVRJRD1tN2MyN2Q3NDI4N2RhNjFm
ZWUxNzVjYWJlYmZhNDkwYzIiIHN0eWxlPSJ0ZXh0LWRlY29yYXRpb246bm9uZTtjb2xvcjojMDBB
RkY5OyBmb250LXNpemU6MTNweCI+QWRkIHRoaXMgbWVldGluZzwvYT4gdG8geW91ciBjYWxlbmRh
ci48L3RkPjwvdHI+PC90YWJsZT4KPHRhYmxlPjx0ciBzdHlsZT0ibGluZS1oZWlnaHQ6IDIwcHg7
Ij48dGQgc3R5bGU9ImhlaWdodDoyMHB4Ij4mbmJzcDs8L3RkPjwvdHI+PC90YWJsZT4KPHRhYmxl
PgogICAgPHRyPgogICAgICAgPHRkIHN0eWxlPSJmb250LXNpemU6IDEzcHg7Zm9udC1mYW1pbHk6
IEFyaWFsO2NvbG9yOiAjNjY2NjY2OyI+CiAgICAgICAgQ2FuJ3Qgam9pbiB0aGUgbWVldGluZz8K
ICAgICAJPGEgaHJlZj0iaHR0cHM6Ly93b3JrZ3JlZW4ud2ViZXguY29tL3dvcmtncmVlbi9tYyIg
c3R5bGU9InRleHQtZGVjb3JhdGlvbjpub25lO2ZvbnQtc2l6ZToxM3B4O2ZvbnQtZmFtaWx5OkFy
aWFsO2NvbG9yOiMwMEFGRjk7Zm9udC1jb2xvcjojMDBBRkY5OyI+CiAgICAgICAgCUNvbnRhY3Qg
c3VwcG9ydC48L2E+CgkJPC90ZD4KICAgIDwvdHI+CjwvdGFibGU+Cjx0YWJsZT48dHIgc3R5bGU9
ImxpbmUtaGVpZ2h0OiAxMHB4OyI+PHRkIHN0eWxlPSJoZWlnaHQ6MTBweCI+Jm5ic3A7PC90ZD48
L3RyPjwvdGFibGU+CgkJCQkJCTx0YWJsZT4KCQkJCQkJCTx0cj4KCQkJCQkJCQk8dGQgc3R5bGU9
ImZvbnQtc2l6ZToxMnB4O2NvbG9yOiAjQTBBMEEwOyI+CgkJCQkJCQkJCUlNUE9SVEFOVCBOT1RJ
Q0U6IFBsZWFzZSBub3RlIHRoYXQgdGhpcyBXZWJFeCBzZXJ2aWNlIGFsbG93cyBhdWRpbyBhbmQg
b3RoZXIgaW5mb3JtYXRpb24gc2VudCBkdXJpbmcgdGhlIHNlc3Npb24gdG8gYmUgcmVjb3JkZWQs
IHdoaWNoIG1heSBiZSBkaXNjb3ZlcmFibGUgaW4gYSBsZWdhbCBtYXR0ZXIuIEJ5IGpvaW5pbmcg
dGhpcyBzZXNzaW9uLCB5b3UgYXV0b21hdGljYWxseSBjb25zZW50IHRvIHN1Y2ggcmVjb3JkaW5n
cy4gSWYgeW91IGRvIG5vdCBjb25zZW50IHRvIGJlaW5nIHJlY29yZGVkLCBkaXNjdXNzIHlvdXIg
Y29uY2VybnMgd2l0aCB0aGUgaG9zdCBvciBkbyBub3Qgam9pbiB0aGUgc2Vzc2lvbi48L3RkPgoJ
CQkJCQkJPC90cj4KCQkJCQkJPC90YWJsZT4KCQkJCTwvdGQ+CgkJCTwvdHI+CgkJPC90YWJsZT4K
CTwvdGQ+CiAgIDwvdHI+CjwvdGFibGU+Cgo8L2JvZHk+
------=_Part_32646_1253885036.1444408188921--

------=_Part_32645_117498147.1444408188921
Content-Type: application/octet-stream;
	name="WebEx_Meeting.ics"
Content-Transfer-Encoding: base64
Content-Disposition: attachment;
	filename="WebEx_Meeting.ics"

QkVHSU46VkNBTEVOREFSClBST0RJRDotLy9NaWNyb3NvZnQgQ29ycG9yYXRpb24vL091dGxvb2sg
MTAuMCBNSU1FRElSLy9FTgpWRVJTSU9OOjIuMApNRVRIT0Q6UkVRVUVTVApCRUdJTjpWVElNRVpP
TkUKVFpJRDpFYXN0ZXJuIFRpbWUKQkVHSU46U1RBTkRBUkQKRFRTVEFSVDoyMDEzMTEwMVQwMjAw
MDAKUlJVTEU6RlJFUT1ZRUFSTFk7SU5URVJWQUw9MTtCWURBWT0xU1U7QllNT05USD0xMQpUWk9G
RlNFVEZST006LTA0MDAKVFpPRkZTRVRUTzotMDUwMApUWk5BTUU6U3RhbmRhcmQgVGltZQpFTkQ6
U1RBTkRBUkQKQkVHSU46REFZTElHSFQKRFRTVEFSVDoyMDEzMDMwMVQwMjAwMDAKUlJVTEU6RlJF
UT1ZRUFSTFk7SU5URVJWQUw9MTtCWURBWT0yU1U7QllNT05USD0zClRaT0ZGU0VURlJPTTotMDUw
MApUWk9GRlNFVFRPOi0wNDAwClRaTkFNRTpEYXlsaWdodCBTYXZpbmdzIFRpbWUKRU5EOkRBWUxJ
R0hUCkVORDpWVElNRVpPTkUKQkVHSU46VkVWRU5UCkFUVEVOREVFO0NOPSIiO1JPTEU9UkVRLVBB
UlRJQ0lQQU5UO1JTVlA9VFJVRTpNQUlMVE86dG9vbHMtZGV2ZWxvcG1lbnRAaWV0Zi5vcmcKT1JH
QU5JWkVSO0NOPSJSYXkgUGVsbGV0aWVyIjpNQUlMVE86cnBlbGxldGllckBpc29jLm9yZwpEVFNU
QVJUO1RaSUQ9IkVhc3Rlcm4gVGltZSI6MjAxNTEwMTNUMTMwMDAwCkRURU5EO1RaSUQ9IkVhc3Rl
cm4gVGltZSI6MjAxNTEwMTNUMTQwMDAwCkxPQ0FUSU9OOmh0dHBzOi8vd29ya2dyZWVuLndlYmV4
LmNvbS93b3JrZ3JlZW4KVFJBTlNQOk9QQVFVRQpTRVFVRU5DRToxNDQ0NDA4MTg4ClVJRDo3MTdh
YzVkNy1iYWI3LTQzMzYtYmU5Zi1hZWFkZWRlMjVkMzMKRFRTVEFNUDoyMDE1MTAxM1QxNzAwMDBa
CkRFU0NSSVBUSU9OOlxuXG5cbkpPSU4gV0VCRVggTUVFVElOR1xuaHR0cHM6Ly93b3JrZ3JlZW4u
d2ViZXguY29tL3dvcmtncmVlbi9qLnBocD9NVElEPW1mYzcxYWQ2Yjg0YTBhZjQwY2VmMDkzMDBm
MGZjMzQyYVxuTWVldGluZyBudW1iZXI6IDgyNCA1NzUgOTg1XG5cblxuSk9JTiBCWSBQSE9ORVxu
MS04NzctNjY4LTQ0OTAgQ2FsbC1pbiB0b2xsLWZyZWUgbnVtYmVyIChVUy9DYW5hZGEpIFxuMS00
MDgtNzkyLTYzMDAgQ2FsbC1pbiB0b2xsIG51bWJlciAoVVMvQ2FuYWRhKVxuQWNjZXNzIGNvZGU6
IDgyNCA1NzUgOTg1XG5cbkdsb2JhbCBjYWxsLWluIG51bWJlcnM6XG5odHRwczovL3dvcmtncmVl
bi53ZWJleC5jb20vd29ya2dyZWVuL2dsb2JhbGNhbGxpbi5waHA/c2VydmljZVR5cGU9TUMmRUQ9
MzE3OTM0NDI3JnRvbGxGcmVlPTFcblxuVG9sbC1mcmVlIGRpYWxpbmcgcmVzdHJpY3Rpb25zOiBc
bmh0dHA6Ly93d3cud2ViZXguY29tL3BkZi90b2xsZnJlZV9yZXN0cmljdGlvbnMucGRmXG5cblxu
XG5DYW4ndCBqb2luIHRoZSBtZWV0aW5nPyBDb250YWN0IHN1cHBvcnQgaGVyZTpcbmh0dHBzOi8v
d29ya2dyZWVuLndlYmV4LmNvbS93b3JrZ3JlZW4vbWNcblxuXG5JTVBPUlRBTlQgTk9USUNFOiBQ
bGVhc2Ugbm90ZSB0aGF0IHRoaXMgV2ViRXggc2VydmljZSBhbGxvd3MgYXVkaW8gYW5kIG90aGVy
IGluZm9ybWF0aW9uIHNlbnQgZHVyaW5nIHRoZSBzZXNzaW9uIHRvIGJlIHJlY29yZGVkLCB3aGlj
aCBtYXkgYmUgZGlzY292ZXJhYmxlIGluIGEgbGVnYWwgbWF0dGVyLiBCeSBqb2luaW5nIHRoaXMg
c2Vzc2lvbiwgeW91IGF1dG9tYXRpY2FsbHkgY29uc2VudCB0byBzdWNoIHJlY29yZGluZ3MuIElm
IHlvdSBkbyBub3QgY29uc2VudCB0byBiZWluZyByZWNvcmRlZCwgZGlzY3VzcyB5b3VyIGNvbmNl
cm5zIHdpdGggdGhlIGhvc3Qgb3IgZG8gbm90IGpvaW4gdGhlIHNlc3Npb24uXG4KWC1BTFQtREVT
QztGTVRUWVBFPXRleHQvaHRtbDoJPEZPTlQgU0laRT0iMSIgRkFDRT0iQVJJQUwiPiZuYnNwOzxC
Uj4gPEZPTlQgU0laRT0iNCIgRkFDRT0iQVJJQUwiPgkJPGEJCQkJCWhyZWY9Imh0dHBzOi8vd29y
a2dyZWVuLndlYmV4LmNvbS93b3JrZ3JlZW4vai5waHA/TVRJRD1tZmM3MWFkNmI4NGEwYWY0MGNl
ZjA5MzAwZjBmYzM0MmEiPjxGT05UIFNJWkU9IjMiIENPTE9SPSIjMDBBRkY5IiBGQUNFPSJBcmlh
bCI+Sm9pbiBXZWJFeCBtZWV0aW5nPC9GT05UPjwvYT4JCQk8dGFibGU+CQkJCTx0cj4JCQkJCTx0
ZD4JCQkJCQk8Rk9OVCBTSVpFPSIyIiBDT0xPUj0iIzY2NjY2NiIgRkFDRT0iYXJpYWwiPk1lZXRp
bmcgbnVtYmVyOjwvRk9OVD4JCQkJCTwvdGQ+CQkJCQk8dGQ+CQkJCQkJPEZPTlQgU0laRT0iMiIg
Q09MT1I9IiM2NjY2NjYiIEZBQ0U9ImFyaWFsIj44MjQgNTc1IDk4NTwvRk9OVD4JCQkJCTwvdGQ+
CQkJCTwvdHI+CQkJPC90YWJsZT4JCQkJCTwvRk9OVD48Rk9OVCBTSVpFPSIxIiBGQUNFPSJBUklB
TCI+Jm5ic3A7PEJSPiZuYnNwOzxCUj48L0ZPTlQ+PEZPTlQgU0laRT0iNCIgRkFDRT0iQVJJQUwi
PjxGT05UIFNJWkU9IjMiIENPTE9SPSIjNjY2NjY2IiBGQUNFPSJhcmlhbCI+Sm9pbiBieSBwaG9u
ZTwvRk9OVD4mbmJzcDsgPEJSPjxGT05UIFNJWkU9IjIiIENPTE9SPSIjNjY2NjY2IiBGQUNFPSJh
cmlhbCI+PHN0cm9uZz4xLTg3Ny02NjgtNDQ5MDwvc3Ryb25nPiZuYnNwO0NhbGwtaW4gdG9sbC1m
cmVlIG51bWJlciAoVVMvQ2FuYWRhKTwvRk9OVD4mbmJzcDsgPEJSPjxGT05UIFNJWkU9IjIiIENP
TE9SPSIjNjY2NjY2IiBGQUNFPSJhcmlhbCI+PHN0cm9uZz4xLTQwOC03OTItNjMwMDwvc3Ryb25n
PiZuYnNwO0NhbGwtaW4gdG9sbCBudW1iZXIgKFVTL0NhbmFkYSk8L0ZPTlQ+Jm5ic3A7IDxCUj48
Rk9OVCBTSVpFPSIyIiBDT0xPUj0iIzY2NjY2NiIgRkFDRT0iYXJpYWwiPkFjY2VzcyBjb2RlOiA4
MjQgNTc1IDk4NTwvRk9OVD4mbmJzcDsgPEJSPjxhIGhyZWY9Imh0dHBzOi8vd29ya2dyZWVuLndl
YmV4LmNvbS93b3JrZ3JlZW4vZ2xvYmFsY2FsbGluLnBocD9zZXJ2aWNlVHlwZT1NQyZFRD0zMTc5
MzQ0MjcmdG9sbEZyZWU9MSI+PEZPTlQgU0laRT0iMSIgQ09MT1I9IiMwMEFGRjkiIEZBQ0U9ImFy
aWFsIj5HbG9iYWwgY2FsbC1pbiBudW1iZXJzPC9GT05UPjwvYT48Rk9OVCBTSVpFPSIxIiBGQUNF
PSJBUklBTCI+Jm5ic3A7Jm5ic3A7fCZuYnNwOyZuYnNwOzwvRk9OVD48YSBocmVmPSJodHRwOi8v
d3d3LndlYmV4LmNvbS9wZGYvdG9sbGZyZWVfcmVzdHJpY3Rpb25zLnBkZiI+PEZPTlQgU0laRT0i
MSIgQ09MT1I9IiMwMEFGRjkiIEZBQ0U9ImFyaWFsIj5Ub2xsLWZyZWUgY2FsbGluZyByZXN0cmlj
dGlvbnM8L0ZPTlQ+PC9hPiAmbmJzcDsgPEJSPjwvRk9OVD48QlI+PEJSPgkmbmJzcDs8QlI+CTxG
T05UIFNJWkU9IjEiIENPTE9SPSIjNjY2NjY2IiBGQUNFPSJhcmlhbCI+CQkJCUNhbid0IGpvaW4g
dGhlIG1lZXRpbmc/PC9GT05UPgk8YSBocmVmPSJodHRwczovL3dvcmtncmVlbi53ZWJleC5jb20v
d29ya2dyZWVuL21jIj4JPEZPTlQgU0laRT0iMSIgQ09MT1I9IiMwMEFGRjkiIEZBQ0U9IkFyaWFs
Ij5Db250YWN0IHN1cHBvcnQuPC9GT05UPjwvYT4JJm5ic3A7PEJSPiZuYnNwOzxCUj48Rk9OVCBD
T0xPUj0iI0EwQTBBMCIgc2l6ZT0iMSIgRkFDRT0iYXJpYWwiPklNUE9SVEFOVCBOT1RJQ0U6IFBs
ZWFzZSBub3RlIHRoYXQgdGhpcyBXZWJFeCBzZXJ2aWNlIGFsbG93cyBhdWRpbyBhbmQgb3RoZXIg
aW5mb3JtYXRpb24gc2VudCBkdXJpbmcgdGhlIHNlc3Npb24gdG8gYmUgcmVjb3JkZWQsIHdoaWNo
IG1heSBiZSBkaXNjb3ZlcmFibGUgaW4gYSBsZWdhbCBtYXR0ZXIuIEJ5IGpvaW5pbmcgdGhpcyBz
ZXNzaW9uLCB5b3UgYXV0b21hdGljYWxseSBjb25zZW50IHRvIHN1Y2ggcmVjb3JkaW5ncy4gSWYg
eW91IGRvIG5vdCBjb25zZW50IHRvIGJlaW5nIHJlY29yZGVkLCBkaXNjdXNzIHlvdXIgY29uY2Vy
bnMgd2l0aCB0aGUgaG9zdCBvciBkbyBub3Qgam9pbiB0aGUgc2Vzc2lvbi48L0ZPTlQ+PC9GT05U
PgpTVU1NQVJZOlRvb2xzIENtdGUKUFJJT1JJVFk6NQpDTEFTUzpQVUJMSUMKQkVHSU46VkFMQVJN
ClRSSUdHRVI6LVBUNU0KQUNUSU9OOkRJU1BMQVkKREVTQ1JJUFRJT046UmVtaW5kZXIKRU5EOlZB
TEFSTQpFTkQ6VkVWRU5UCkVORDpWQ0FMRU5EQVIK
------=_Part_32645_117498147.1444408188921--


From nobody Fri Oct  9 11:14:48 2015
Return-Path: <housley@vigilsec.com>
X-Original-To: tools-development@ietfa.amsl.com
Delivered-To: tools-development@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 6AA601B2C80 for <tools-development@ietfa.amsl.com>; Fri,  9 Oct 2015 11:14:47 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -101.9
X-Spam-Level: 
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 mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id gRQl24toOBcn for <tools-development@ietfa.amsl.com>; Fri,  9 Oct 2015 11:14:45 -0700 (PDT)
Received: from odin.smetech.net (x-bolt-wan.smeinc.net [209.135.219.146]) by ietfa.amsl.com (Postfix) with ESMTP id A70BD1B4939 for <tools-development@ietf.org>; Fri,  9 Oct 2015 11:14:45 -0700 (PDT)
Received: from localhost (unknown [209.135.209.5]) by odin.smetech.net (Postfix) with ESMTP id E93449A4019; Fri,  9 Oct 2015 14:14:34 -0400 (EDT)
X-Virus-Scanned: amavisd-new at smetech.net
Received: from odin.smetech.net ([209.135.209.4]) by localhost (ronin.smeinc.net [209.135.209.5]) (amavisd-new, port 10024) with ESMTP id N+rECFtDHssv; Fri,  9 Oct 2015 14:13:18 -0400 (EDT)
Received: from [192.168.2.104] (pool-108-51-128-219.washdc.fios.verizon.net [108.51.128.219]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (No client certificate requested) by odin.smetech.net (Postfix) with ESMTP id 2C8FA9A400D; Fri,  9 Oct 2015 14:14:14 -0400 (EDT)
Mime-Version: 1.0 (Apple Message framework v1085)
Content-Type: text/plain; charset=us-ascii
From: Russ Housley <housley@vigilsec.com>
In-Reply-To: <43A5C436-707E-4D7A-B792-FFB033BCD4B7@vigilsec.com>
Date: Fri, 9 Oct 2015 14:14:02 -0400
Content-Transfer-Encoding: 7bit
Message-Id: <761D8062-AFBB-4F7F-A167-5C7C23F98ADF@vigilsec.com>
References: <43A5C436-707E-4D7A-B792-FFB033BCD4B7@vigilsec.com>
To: IETF Tools Development <tools-development@ietf.org>
X-Mailer: Apple Mail (2.1085)
Archived-At: <http://mailarchive.ietf.org/arch/msg/tools-development/QZdougMX15Bb0qXMWm2js57rSaw>
Subject: [TOOLS-DEVELOPMENT] Tools Call Agenda -- 13 October 2015 at 13:00 Eastern
X-BeenThere: tools-development@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: Tools Development list server <tools-development.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/tools-development>, <mailto:tools-development-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/tools-development/>
List-Post: <mailto:tools-development@ietf.org>
List-Help: <mailto:tools-development-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/tools-development>, <mailto:tools-development-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 09 Oct 2015 18:14:47 -0000

I have not seem much discussion of the draft SOWs.

For the RFC Editor tools, the SOWs are here:
http://www.nostrum.com/~rjsparks/rfced/

In addition, Robert asked for review of three additional SOWs:
http://www.nostrum.com/~rjsparks/pmsow/

Please send comments before the tools call scheduled for next Tuesday.

Russ

= = = = = = = = 

Tools Call Agenda -- 13 October 2015 at 13:00 Eastern

1. Datatracker Projects
   - Expected Datatracker Releases -- Robert and Henrik
     -- http://trac.tools.ietf.org/tools/ietfdb/wiki/MergePlan
   - Update instructions for I-D Submission tool -- Robert
   - Liaison Tool improvements -- Robert
   - Tracking Internet-Draft Manual Post Requests -- Robert
   - Interim Meeting Management -- Robert
   - Review Tracking -- Robert
   - Author Statistics -- Russ

2. Community & Other Projects
   - Improve infrastructure for finding and fetching artifacts -- Robert
   - IETF Website Makeover -- Joe and Greg

3. RFC Services Projects
   - RFC Editor Website Makeover -- Alice and Heather
   - RSE's Design Teams -- Heather
   - RFC Format-related SOWs -- Robert

4. Transition of Mission Critical Tools
   - Moving issue trackers and wikis for IETF WGs on ietf.org

5. Server Infrastructure
   - File sync from Sunnyvale to Orlando -- Henrik
   - IMAP access to the email archives -- Robert

6. IDIQ Contractors
   - RFP for more IDIQ contractors -- Ray

7. Parking Lot
   - Mentor Support Tool -- AMS
   - RFC Editor automatic stats and reporting RFP -- Heather
   - Author information for very old I-Ds in the datatracker -- Robert
   - Replace I-Ds in proceedings with links to archive copy?
   - Can the test process for the NomCom Tool be more comprehensive?
   - Performance improvements and transition to Postgres -- Henrik
   - VM Architecture for Servers -- Robert
   - Add the YANG checker to the I-D Submission Tool
   - Submit an I-D directly from GitHub

8. AOB


From nobody Mon Oct 12 12:20:09 2015
Return-Path: <rjsparks@nostrum.com>
X-Original-To: tools-development@ietfa.amsl.com
Delivered-To: tools-development@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 571EE1B358C for <tools-development@ietfa.amsl.com>; Mon, 12 Oct 2015 12:20:07 -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 bRixhggRBRja for <tools-development@ietfa.amsl.com>; Mon, 12 Oct 2015 12:20:05 -0700 (PDT)
Received: from nostrum.com (raven-v6.nostrum.com [IPv6:2001:470:d:1130::1]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 8273E1B3589 for <tools-development@ietf.org>; Mon, 12 Oct 2015 12:20:05 -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.2/8.14.9) with ESMTPSA id t9CJK464002379 (version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128 verify=OK); Mon, 12 Oct 2015 14:20:04 -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
To: Russ Housley <housley@vigilsec.com>, IETF Tools Development <tools-development@ietf.org>
References: <43A5C436-707E-4D7A-B792-FFB033BCD4B7@vigilsec.com> <761D8062-AFBB-4F7F-A167-5C7C23F98ADF@vigilsec.com>
From: Robert Sparks <rjsparks@nostrum.com>
Message-ID: <561C07DF.8020103@nostrum.com>
Date: Mon, 12 Oct 2015 14:19:59 -0500
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.10; rv:38.0) Gecko/20100101 Thunderbird/38.3.0
MIME-Version: 1.0
In-Reply-To: <761D8062-AFBB-4F7F-A167-5C7C23F98ADF@vigilsec.com>
Content-Type: text/plain; charset=windows-1252; format=flowed
Content-Transfer-Encoding: 7bit
Archived-At: <http://mailarchive.ietf.org/arch/msg/tools-development/5oYUQz9uBCZOc6mbWRb1symDigg>
Subject: Re: [TOOLS-DEVELOPMENT] Tools Call Agenda -- 13 October 2015 at 13:00 Eastern
X-BeenThere: tools-development@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: Tools Development list server <tools-development.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/tools-development>, <mailto:tools-development-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/tools-development/>
List-Post: <mailto:tools-development@ietf.org>
List-Help: <mailto:tools-development-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/tools-development>, <mailto:tools-development-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 12 Oct 2015 19:20:07 -0000

Some notes (and questions) to try to help make tomorrow's call efficient:

On 10/9/15 1:14 PM, Russ Housley wrote:
> I have not seem much discussion of the draft SOWs.
>
> For the RFC Editor tools, the SOWs are here:
> http://www.nostrum.com/~rjsparks/rfced/
>
> In addition, Robert asked for review of three additional SOWs:
> http://www.nostrum.com/~rjsparks/pmsow/
>
> Please send comments before the tools call scheduled for next Tuesday.
>
> Russ
>
> = = = = = = = =
>
> Tools Call Agenda -- 13 October 2015 at 13:00 Eastern
>
> 1. Datatracker Projects
>     - Expected Datatracker Releases -- Robert and Henrik
>       -- http://trac.tools.ietf.org/tools/ietfdb/wiki/MergePlan
We've issued a bugfix release and a major functionality release 
(liaision tool) so far this month.
The new email management framework should be released very soon (maybe 
before tomorrow's call).
We have some big work from Iola ready to merge:
* improvements to saving things like Documents, capturing events and 
history more consistently
* improvements to the test crawler to cover pages when logged in as the 
secretariat, and fixes to the bugs exposed by doing that crawl
More are expected soon.

We need to identify the release we will have in hand for the codesprint.
>     - Update instructions for I-D Submission tool -- Robert
I think Henrik was addressing this? (It may have been part of the recent 
bugfix release).
>     - Liaison Tool improvements -- Robert
Released Saturday - deployed today.
>     - Tracking Internet-Draft Manual Post Requests -- Robert
>     - Interim Meeting Management -- Robert
>     - Review Tracking -- Robert
>     - Author Statistics -- Russ
>
> 2. Community & Other Projects
>     - Improve infrastructure for finding and fetching artifacts -- Robert
Nothing new to discuss.
>     - IETF Website Makeover -- Joe and Greg
>
> 3. RFC Services Projects
>     - RFC Editor Website Makeover -- Alice and Heather
>     - RSE's Design Teams -- Heather
>     - RFC Format-related SOWs -- Robert
>
> 4. Transition of Mission Critical Tools
>     - Moving issue trackers and wikis for IETF WGs on ietf.org
Requires datatracker work, slated for after we work on integrating YANG 
checkers.
>
> 5. Server Infrastructure
>     - File sync from Sunnyvale to Orlando -- Henrik
>     - IMAP access to the email archives -- Robert
The production instance is deployed. We need to build a documentation 
page for it (similar to the testing page).
We may need to tweak the MySQL timeout settings, or cron a periodic 
restart until we get traffic onto it - otherwise, logins stop working 
when the connection times out.
>
> 6. IDIQ Contractors
>     - RFP for more IDIQ contractors -- Ray
>
> 7. Parking Lot
>     - Mentor Support Tool -- AMS
>     - RFC Editor automatic stats and reporting RFP -- Heather
This should come out of the parking lot.
>     - Author information for very old I-Ds in the datatracker -- Robert
>     - Replace I-Ds in proceedings with links to archive copy?
>     - Can the test process for the NomCom Tool be more comprehensive?
>     - Performance improvements and transition to Postgres -- Henrik
>     - VM Architecture for Servers -- Robert
>     - Add the YANG checker to the I-D Submission Tool
>     - Submit an I-D directly from GitHub
>
> 8. AOB
I have an outstanding task that is not moving that I want to report on.

We need to refactor the meeting materials.

We decided not to burden the Interim Meeting Management project with 
changes to the materials pages because we're expecting this refactor.

This would also be where we address the request from the IESG to capture 
meeting summaries, and slides (or other artifacts) that should be 
attached to a meeting even if they weren't presented (see the discussion 
in http://wiki.tools.ietf.org/tools/ietfdb/ticket/1773)

We have a start towards the necessary refactor that we released to 
support the EDU team. Unfortunately, it's not been obvious when upload 
things using the new forms there, and when to keep using the old meeting 
materials page. Some of both has been happening, resulting in a small 
mess that will take a data migration to straighten out. I had hoped to 
do that before Yokohama, but that's not how it looks like it will turn 
out. I will work with Mirja to get the team through Yokohama with as 
little impedance as possible, while keeping the eventual fix migration 
feasible.

I have a start at some more major work which I showed folks at the 
Prague codesprint, but have not kept it up to date with trunk, and it 
has not gotten any real cycles since Prague.

I think this should be a high priority task after Yokohama. How do we 
prioritize it against, say, the YANG work?

It will require attention from the Secretariat (mostly Ryan I think), 
and me and Henrik.


>
> _______________________________________________
> TOOLS-DEVELOPMENT mailing list
> TOOLS-DEVELOPMENT@ietf.org
> https://www.ietf.org/mailman/listinfo/tools-development


From nobody Mon Oct 12 14:55:20 2015
Return-Path: <rjsparks@nostrum.com>
X-Original-To: tools-development@ietfa.amsl.com
Delivered-To: tools-development@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id F2D6D1A1BAF for <tools-development@ietfa.amsl.com>; Mon, 12 Oct 2015 14:55:18 -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 hUja_woKVN7V for <tools-development@ietfa.amsl.com>; Mon, 12 Oct 2015 14:55:17 -0700 (PDT)
Received: from nostrum.com (raven-v6.nostrum.com [IPv6:2001:470:d:1130::1]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id D520E1A1B53 for <tools-development@ietf.org>; Mon, 12 Oct 2015 14:55:17 -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.2/8.14.9) with ESMTPSA id t9CLtGTC015708 (version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128 verify=OK) for <tools-development@ietf.org>; Mon, 12 Oct 2015 16:55:16 -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
To: IETF Tools Development <tools-development@ietf.org>
From: Robert Sparks <rjsparks@nostrum.com>
Message-ID: <561C2C3F.2050100@nostrum.com>
Date: Mon, 12 Oct 2015 16:55:11 -0500
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.10; rv:38.0) Gecko/20100101 Thunderbird/38.3.0
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Transfer-Encoding: 7bit
Archived-At: <http://mailarchive.ietf.org/arch/msg/tools-development/rRB5Hyq5ajZG4uvMTmU-bVIsIqU>
Subject: [TOOLS-DEVELOPMENT] Instructions for configuring clients to use the production IMAP instance
X-BeenThere: tools-development@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: Tools Development list server <tools-development.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/tools-development>, <mailto:tools-development-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/tools-development/>
List-Post: <mailto:tools-development@ietf.org>
List-Help: <mailto:tools-development-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/tools-development>, <mailto:tools-development-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 12 Oct 2015 21:55:19 -0000

Let me know if you see anything that needs to change at
<http://trac.tools.ietf.org/group/tools/trac/wiki/Imap>

RjS


From nobody Tue Oct 13 10:55:12 2015
Return-Path: <rse@rfc-editor.org>
X-Original-To: tools-development@ietfa.amsl.com
Delivered-To: tools-development@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id EDB1F1A020A for <tools-development@ietfa.amsl.com>; Tue, 13 Oct 2015 10:55:06 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.201
X-Spam-Level: 
X-Spam-Status: No, score=-4.201 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, SPF_PASS=-0.001] 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 3X--rot0YXCq for <tools-development@ietfa.amsl.com>; Tue, 13 Oct 2015 10:55:01 -0700 (PDT)
Received: from mail.amsl.com (mail.amsl.com [4.31.198.40]) by ietfa.amsl.com (Postfix) with ESMTP id 6CD341A0264 for <tools-development@ietf.org>; Tue, 13 Oct 2015 10:55:01 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by c8a.amsl.com (Postfix) with ESMTP id AA6ED1E59F0 for <tools-development@ietf.org>; Tue, 13 Oct 2015 10:54:37 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
Received: from c8a.amsl.com ([127.0.0.1]) by localhost (c8a.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id GDv4_0rSHCBR for <tools-development@ietf.org>; Tue, 13 Oct 2015 10:54:37 -0700 (PDT)
Received: from Heathers-MacBook-Pro.local (unknown [98.125.214.91]) by c8a.amsl.com (Postfix) with ESMTPSA id 692771E59EE for <tools-development@ietf.org>; Tue, 13 Oct 2015 10:54:37 -0700 (PDT)
To: tools-development@ietf.org
References: <43A5C436-707E-4D7A-B792-FFB033BCD4B7@vigilsec.com> <761D8062-AFBB-4F7F-A167-5C7C23F98ADF@vigilsec.com>
From: "Heather Flanagan (RFC Series Editor)" <rse@rfc-editor.org>
X-Enigmail-Draft-Status: N1110
Message-ID: <561D457B.80700@rfc-editor.org>
Date: Tue, 13 Oct 2015 10:55:07 -0700
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.10; rv:38.0) Gecko/20100101 Thunderbird/38.3.0
MIME-Version: 1.0
In-Reply-To: <761D8062-AFBB-4F7F-A167-5C7C23F98ADF@vigilsec.com>
Content-Type: text/plain; charset=windows-1252
Content-Transfer-Encoding: quoted-printable
Archived-At: <http://mailarchive.ietf.org/arch/msg/tools-development/dp5PIqkw9Ftq9J9hF7uE-04YpEQ>
Subject: [TOOLS-DEVELOPMENT] Tools Call Notes -- 13 October 2015 at 13:00 Eastern
X-BeenThere: tools-development@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: Tools Development list server <tools-development.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/tools-development>, <mailto:tools-development-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/tools-development/>
List-Post: <mailto:tools-development@ietf.org>
List-Help: <mailto:tools-development-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/tools-development>, <mailto:tools-development-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 13 Oct 2015 17:55:07 -0000

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256

1. Datatracker Projects
   - Expected Datatracker Releases -- Robert and Henrik
     -- http://trac.tools.ietf.org/tools/ietfdb/wiki/MergePlan
   - Update instructions for I-D Submission tool -- Robert
   - Liaison Tool improvements -- Robert
   - Tracking Internet-Draft Manual Post Requests -- Robert
   - Interim Meeting Management -- Robert
   - Review Tracking -- Robert
   - Author Statistics -- Russ

* Liaison tool is deployed, no major issues. Can be removed from future
agenda.
* Update to the datatracker later today will include email changes, as
discussed on list.
* Expect 2-3 (or more) releases before we get to the Codesprint.
* Instructions for I-D submission were added in the very latest release;
can remove from future agenda.
* Tracking I-D manual post requests; Robert has incorporated the
comments received from the Secretariat. Benson to review sometime in the
next 24 hours, and unless he has comments, this and the Interim Meeting
Management SOW are ready to send to the IAOC and ask that they start the
community feedback process.
* Review Tracking SOW: This is a wrapper around the RFC that has already
been through community review. OK for the IAOC to move this forward as we=
ll.
* Author stats: community review is complete, waiting for write up. Russ
to nudge Jari.


 2. Community & Other Projects
   - Improve infrastructure for finding and fetching artifacts -- Robert
   - IETF Website Makeover -- Joe and Greg

* Nothing new to report on infrastructure for finding and fetching
artifacts.
* IETF website makeover: project is on track in terms of time. We have
decided to push the rollover to after IETF 94. Alexa is working with
Torchbox to schedule the training around the new CMS for the
Secretariat. Note that there have been URLs changed, and some have been
given redirects, but some have not. Content team has made that evaluation=
=2E


3. RFC Services Projects
   - RFC Editor Website Makeover -- Alice and Heather
   - Stats and Metrics
   - RSE's Design Teams -- Heather
   - RFC Format-related SOWs -- Robert

* Website makeover went well. Collecting feedback on the RSE wiki. Will
be meeting this afternoon with Sandy and Alice to discuss and prioritize
any changes as a result of that feedback. There are 65 scripts (PHP) are
now in one place (underlying reorg). The static pages, about 42, were
all migrated from hand-edited HTML files.
* Stats and Metrics: any objection to asking the IAOC that the SOW,
which has gone through community review last year, be moved into the RFP
process? No objections
* RSE Design team - Format work: the bundle of drafts have been
completed and sent to the RSOC this morning to start their review
process. They have a reading order and description; you can see that on
the design team wiki along with a pointer to the SOWs
(https://www.rfc-editor.org/rse/wiki/doku.php?id=3Ddesign:start)
* RFC Format-related SOWs: review the SOWs as part of the drafts
* Codesprint: Heather and Robert working together to identify an RFC
Editor-requested project that can be handled through the codesprint.
=20
4. Transition of Mission Critical Tools
   - Moving issue trackers and wikis for IETF WGs on ietf.org

* This hasn't moved much since last call. All work currently on Henrik's
plate; he has to write the glue code. It is behind integrating the YANG
checkers.

5. Server Infrastructure
   - File sync from Sunnyvale to Orlando -- Henrik
   - IMAP access to the email archives -- Robert

* New version of ghostlinkd; it is able to do the rsyncs every time a
doc lands in the watched directory. Henrik has configured this for new
drafts; may want to do this for other docs as well (e.g., new charters,
assignment). Tool is ready, policy decisions regarding what else should
be synced need to happen. Glen to look at the non-rsynced directories
and which of those things are on the "normal" run and will send to Russ
and Henrik. Go ahead and keep the existing rsyncs going for now.
* IMAP: production server is deployed since end of last week. Link send
to Tools Dev with instructions. Would like to introduce a few users, but
haven't found the correct volunteers. Hoping to announce this between
now and Yokohama (mid-next week?). Side issue, need to change the
timeout between the MySQL and Django. Glen to review and set timeout to
a week.

6. IDIQ Contractors
   - RFP for more IDIQ contractors -- Ray

* No update.

7. Parking Lot
   - Mentor Support Tool -- AMS
   - RFC Editor automatic stats and reporting RFP -- Heather **moved out
of parking lot**
   - Author information for very old I-Ds in the datatracker -- Robert
   - Replace I-Ds in proceedings with links to archive copy?
   - Can the test process for the NomCom Tool be more comprehensive?
   - Performance improvements and transition to Postgres -- Henrik
   - VM Architecture for Servers -- Robert
   - Add the YANG checker to the I-D Submission Tool
   - Submit an I-D directly from GitHub

8. AOB
* xml2rfc - please release code with bug fixes

* "We need to refactor the meeting materials" (See Robert's email on 12
October 2015)
Where should this be prioritized? Should this go to an IDIQ contractor
(that would require an SOW). Next step: Robert to write out the
requirements and what needs to happen; try to have the first draft by
Yokohama.
=20
-----BEGIN PGP SIGNATURE-----
Version: GnuPG/MacGPG2 v2
Comment: GPGTools - http://gpgtools.org

iQEcBAEBCAAGBQJWHUV7AAoJEER/xjINbZoG4DIH+gOXi9gspnS02RVK3h5wRGOT
iG7X0vjwNWMDebWdNG7v6F73+ci8SbhHR03vfrJnrt6Q0Ag1SbD5o9pMtiTjRcbI
XwnQxyG7kg7hK4jlOsSo7NIgQxi3h4ny5s5vgMPm/E4ovqQCJl+eCkyVvYFOoaWQ
akmInjz6dStdKIvqyA9ROHbPSAnlv+ILpoMV4UlPh1u74bpZ9u0HzMwbO3q1W+/j
BVuAdODM63Iv6KkKYwG1UHA6oDax2eWaKsW17Y7w5hz7LKE6ZN7JNq8VQW6SW/2N
4BuTgFjoyPiqQKRCqKbamBUqTXHMIH5Zk7W0yvIKYpeU/8XUoVqxOatZ8EsdFrg=3D
=3D/a6i
-----END PGP SIGNATURE-----



From nobody Tue Oct 20 06:07:49 2015
Return-Path: <housley@vigilsec.com>
X-Original-To: tools-development@ietfa.amsl.com
Delivered-To: tools-development@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 5A3311A8949 for <tools-development@ietfa.amsl.com>; Tue, 20 Oct 2015 06:07:41 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -101.9
X-Spam-Level: 
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 mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 9DVlTDQS91nf for <tools-development@ietfa.amsl.com>; Tue, 20 Oct 2015 06:07:34 -0700 (PDT)
Received: from odin.smetech.net (x-bolt-wan.smeinc.net [209.135.219.146]) by ietfa.amsl.com (Postfix) with ESMTP id 91DCE1A0469 for <tools-development@ietf.org>; Tue, 20 Oct 2015 06:06:18 -0700 (PDT)
Received: from localhost (unknown [209.135.209.5]) by odin.smetech.net (Postfix) with ESMTP id E04A49A4051 for <tools-development@ietf.org>; Tue, 20 Oct 2015 09:06:07 -0400 (EDT)
X-Virus-Scanned: amavisd-new at smetech.net
Received: from odin.smetech.net ([209.135.209.4]) by localhost (ronin.smeinc.net [209.135.209.5]) (amavisd-new, port 10024) with ESMTP id HFdLpkjYljod for <tools-development@ietf.org>; Tue, 20 Oct 2015 09:04:46 -0400 (EDT)
Received: from [10.196.207.51] (196-194.icannmeeting.org [199.91.194.196]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (No client certificate requested) by odin.smetech.net (Postfix) with ESMTP id 88E199A4029 for <tools-development@ietf.org>; Tue, 20 Oct 2015 09:05:46 -0400 (EDT)
From: Russ Housley <housley@vigilsec.com>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: quoted-printable
Date: Tue, 20 Oct 2015 09:05:34 -0400
References: <D15EC0E0-9078-4FC1-9D42-45A3709A4091@ietf.org>
To: IETF Tools Development <tools-development@ietf.org>
Message-Id: <251ADADA-03DE-43E3-8AB4-C47812EA3D3D@vigilsec.com>
Mime-Version: 1.0 (Apple Message framework v1085)
X-Mailer: Apple Mail (2.1085)
Archived-At: <http://mailarchive.ietf.org/arch/msg/tools-development/UP0FUK3VwZfpHZa0zczxe853SAc>
Subject: [TOOLS-DEVELOPMENT] Fwd: Call for Review: <draft-sparks-genarea-manualpost-tracking-00.txt> (Tracking Manual I-D Post Requests)
X-BeenThere: tools-development@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: Tools Development list server <tools-development.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/tools-development>, <mailto:tools-development-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/tools-development/>
List-Post: <mailto:tools-development@ietf.org>
List-Help: <mailto:tools-development-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/tools-development>, <mailto:tools-development-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 20 Oct 2015 13:07:41 -0000

> From: IETF Chair <chair@ietf.org>
> Date: October 20, 2015 8:03:47 AM EDT
> To: IETF Announcement List <ietf-announce@ietf.org>
> Cc: IETF <ietf@ietf.org>, Russ Housley <housley@vigilsec.com>
> Subject: Call for Review: =
<draft-sparks-genarea-manualpost-tracking-00.txt> (Tracking Manual I-D =
Post Requests)
> Reply-To: IETF <ietf@ietf.org>, Russ Housley <housley@vigilsec.com>
>=20
> This is a request for a review of a Statement of Work from the IAOC
> Tools Committee. Please take a look at the document and provide the
> committee feedback.
>=20
> Jari Arkko
>=20
> ----
>=20
> The IAOC Tools Committee has developed a Statement of Work (SoW) for
> an enhancement to the IETF Datatracker to assist in requests for
> manual Internet-Draft posting.  We are asking for review by the
> IETF community before seeking a vendor to write the software to
> implement the new Datatracker features described in the document.
>=20
> The transparency of the I-D submission process needs to be improved,
> particularly for those submissions that are handled directly by the
> IETF Secretariat.  These are referred to as "manual" and "forced"
> I-D submissions.
>=20
> When an author uses the IETF Datatracker I-D submission tool, some
> information is captures about the event, including when the I-D was
> submitted, when it was approved, and who made the submission.
> Currently, the document history shows only that a new version is
> available.
>=20
> The I-D submission tool presents an option for authors to request the
> IETF Secretariat finish the submission process.  When this option is
> exercised, the Datatracker captures the candidate document and then
> sends email to the Secretariat.  Often the request is made because the
> I-D submission tool was unable to extract correct meta-data from the
> document.  In this case, the Secretariat populates the meta-data, and
> then forces the post.  Currently, normal submission event information
> is not collected when the Secretariat forces the post; this effort
> will allow it to be collected.
>=20
> The Secretariat also receives email requests to post an I-D, bypassing
> the I-D submission tool altogether.  Currently, the Secretariat =
receives
> about 10 such requests each meeting cycle.  When this happens, the
> Secretariat operates the I-D submission tool on behalf of the author,
> and as a result, the submission event information does not reflect =
that
> a manual I-D submission request was processed ob behalf of the author.
> This effort will allow accurate submission event information to be
> collected for manual I-D submission.
>=20
> The Secretariat currently relies on a combination of RT and personal
> email archives to keep track of the outstanding manual I-D submission
> requests.  This effort will provide proper workflow tracking of these
> requests.
>=20
> The file can be obtained via
> =
https://datatracker.ietf.org/doc/draft-sparks-genarea-manualpost-tracking-=
00.txt/
>=20
> No IPR declarations have been submitted directly on this I-D.
>=20
> The IAOC plans to solicit bids for the development of these new =
features
> in the next few weeks, and solicits comments on this SoW. Please send
> comments to the ietf@ietf.org mailing lists by November 10, 2015.
> Exceptionally, comments may be sent to iaoc@ietf.org instead.  In =
either
> case, please retain the beginning of the Subject line to allow =
automated
> sorting.
>=20
> Thank you,
> Russ Housley
> Chair of the IAOC Tools Committee


From nobody Tue Oct 20 06:11:26 2015
Return-Path: <housley@vigilsec.com>
X-Original-To: tools-development@ietfa.amsl.com
Delivered-To: tools-development@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 507AF1A0AC8 for <tools-development@ietfa.amsl.com>; Tue, 20 Oct 2015 06:11:25 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -101.9
X-Spam-Level: 
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 mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id dBxr65-vsgu3 for <tools-development@ietfa.amsl.com>; Tue, 20 Oct 2015 06:11:21 -0700 (PDT)
Received: from odin.smetech.net (x-bolt-wan.smeinc.net [209.135.219.146]) by ietfa.amsl.com (Postfix) with ESMTP id 3281B1A0469 for <tools-development@ietf.org>; Tue, 20 Oct 2015 06:11:21 -0700 (PDT)
Received: from localhost (unknown [209.135.209.5]) by odin.smetech.net (Postfix) with ESMTP id DF1029A4049 for <tools-development@ietf.org>; Tue, 20 Oct 2015 09:11:10 -0400 (EDT)
X-Virus-Scanned: amavisd-new at smetech.net
Received: from odin.smetech.net ([209.135.209.4]) by localhost (ronin.smeinc.net [209.135.209.5]) (amavisd-new, port 10024) with ESMTP id Ej6afOMSClv6 for <tools-development@ietf.org>; Tue, 20 Oct 2015 09:09:38 -0400 (EDT)
Received: from [10.196.207.51] (196-194.icannmeeting.org [199.91.194.196]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (No client certificate requested) by odin.smetech.net (Postfix) with ESMTP id 9AABC9A4019 for <tools-development@ietf.org>; Tue, 20 Oct 2015 09:10:38 -0400 (EDT)
From: Russ Housley <housley@vigilsec.com>
Content-Type: text/plain; charset=windows-1252
Content-Transfer-Encoding: quoted-printable
Date: Tue, 20 Oct 2015 09:10:26 -0400
References: <E1BF02D0-08D8-4732-AB7C-6E3C64A422DC@ietf.org>
To: IETF Tools Development <tools-development@ietf.org>
Message-Id: <0A85B717-933E-41F7-BEF9-C5AB788DE9FB@vigilsec.com>
Mime-Version: 1.0 (Apple Message framework v1085)
X-Mailer: Apple Mail (2.1085)
Archived-At: <http://mailarchive.ietf.org/arch/msg/tools-development/6A5BltKxh2VkVcEF8azU6z78B4k>
Subject: [TOOLS-DEVELOPMENT] Fwd: Call for Review: <draft-sparks-genarea-interim-management-00.txt> (Interim Meeting Management)
X-BeenThere: tools-development@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: Tools Development list server <tools-development.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/tools-development>, <mailto:tools-development-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/tools-development/>
List-Post: <mailto:tools-development@ietf.org>
List-Help: <mailto:tools-development-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/tools-development>, <mailto:tools-development-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 20 Oct 2015 13:11:25 -0000

> From: IETF Chair <chair@ietf.org>
> Date: October 20, 2015 8:04:37 AM EDT
> To: IETF Announcement List <ietf-announce@ietf.org>
> Cc: IETF <ietf@ietf.org>, Russ Housley <housley@vigilsec.com>
> Subject: Call for Review: =
<draft-sparks-genarea-interim-management-00.txt> (Interim Meeting =
Management)
> Reply-To: IETF <ietf@ietf.org>, Russ Housley <housley@vigilsec.com>
>=20
> This is a request for a review of a Statement of Work from the IAOC
> Tools Committee. Please take a look at the document and provide the
> committee feedback.
>=20
> Jari Arkko
>=20
> =97=97
>=20
> The IAOC Tools Committee has developed a Statement of Work (SoW) for
> an enhancement to the IETF Datatracker to assist in managing interim
> meetings and virtual interim meetings.  We are asking for review by =
the
> IETF community before seeking a vendor to write the software to
> implement the new Datatracker features described in the document.
>=20
> Much of the effort in scheduling interim meetings and virtual interim
> meetings is performed manually by the IETF Secretariat.  With the
> increase in the number of virtual interims, remaining consistent is
> becoming difficult.  The Secretariat frequently has to spend time
> correcting errors in requests, usually as a result of incorrect or
> missing information.  Better automated tools could greatly increase
> the consistency of information provided in the requests and greatly
> improve consistency in the processing of those requests.
>=20
> Managing announcements and maintaining a list of upcoming interim
> meetings are largely manual efforts.  There is currently no calendar
> for subscriptions to upcoming interim meetings and virtual interim
> meetings; this effort will provide one.
>=20
> Management of interim meeting materials (agendas, slides, and minutes)
> is decoupled from the management of the meeting itself, leading to the
> situation where chairs can create interim meeting objects in the
> Datatracker, inadvertently bypassing the current steps designed to
> ensure approval, when needed, and proper announcement.  This effort
> will provide better meeting management for the Secretariat, Area
> Directors, and Working Group Chairs.
>=20
> The file can be obtained via
> =
https://datatracker.ietf.org/doc/draft-sparks-genarea-interim-management-0=
0.txt/
>=20
> No IPR declarations have been submitted directly on this I-D.
>=20
> The IAOC plans to solicit bids for the development of these new =
features
> in the next few weeks, and solicits comments on this SoW. Please send
> comments to the ietf@ietf.org mailing lists by November 10, 2015.
> Exceptionally, comments may be sent to iaoc@ietf.org instead.  In =
either
> case, please retain the beginning of the Subject line to allow =
automated
> sorting.
>=20
> Thank you,
> Russ Housley
> Chair of the IAOC Tools Committee
>=20


From nobody Wed Oct 21 02:30:25 2015
Return-Path: <housley@vigilsec.com>
X-Original-To: tools-development@ietfa.amsl.com
Delivered-To: tools-development@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id B62B01A03E1 for <tools-development@ietfa.amsl.com>; Wed, 21 Oct 2015 02:30:23 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -101.9
X-Spam-Level: 
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 mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Y4arJ8yzGnFw for <tools-development@ietfa.amsl.com>; Wed, 21 Oct 2015 02:30:22 -0700 (PDT)
Received: from odin.smetech.net (x-bolt-wan.smeinc.net [209.135.219.146]) by ietfa.amsl.com (Postfix) with ESMTP id 520861A040C for <tools-development@ietf.org>; Wed, 21 Oct 2015 02:30:22 -0700 (PDT)
Received: from localhost (unknown [209.135.209.5]) by odin.smetech.net (Postfix) with ESMTP id 9A6339A403B for <tools-development@ietf.org>; Wed, 21 Oct 2015 05:30:11 -0400 (EDT)
X-Virus-Scanned: amavisd-new at smetech.net
Received: from odin.smetech.net ([209.135.209.4]) by localhost (ronin.smeinc.net [209.135.209.5]) (amavisd-new, port 10024) with ESMTP id xMvyYiZavbHL for <tools-development@ietf.org>; Wed, 21 Oct 2015 05:28:50 -0400 (EDT)
Received: from [10.196.207.51] (153-194.icannmeeting.org [199.91.194.153]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (No client certificate requested) by odin.smetech.net (Postfix) with ESMTP id C5C179A402E for <tools-development@ietf.org>; Wed, 21 Oct 2015 05:29:50 -0400 (EDT)
From: Russ Housley <housley@vigilsec.com>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: quoted-printable
Date: Wed, 21 Oct 2015 05:29:38 -0400
Message-Id: <02653933-8DFC-40C0-8BB7-B65EA8F46473@vigilsec.com>
To: IETF Tools Development <tools-development@ietf.org>
Mime-Version: 1.0 (Apple Message framework v1085)
X-Mailer: Apple Mail (2.1085)
Archived-At: <http://mailarchive.ietf.org/arch/msg/tools-development/7xhFUECMJmrfqdmkVnxJXpAvnO8>
Subject: [TOOLS-DEVELOPMENT] Cloudflare and DNSSEC
X-BeenThere: tools-development@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: Tools Development list server <tools-development.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/tools-development>, <mailto:tools-development-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/tools-development/>
List-Post: <mailto:tools-development@ietf.org>
List-Help: <mailto:tools-development-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/tools-development>, <mailto:tools-development-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 21 Oct 2015 09:30:23 -0000

https://blog.cloudflare.com/dnssec-is-open-for-beta/

The capability that we have been using is being rolled out for all of =
the Cloudflare customers.

Russ


From nobody Thu Oct 22 05:34:29 2015
Return-Path: <lberger@labn.net>
X-Original-To: tools-development@ietfa.amsl.com
Delivered-To: tools-development@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 53EAC1B3671 for <tools-development@ietfa.amsl.com>; Thu, 22 Oct 2015 05:34:27 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.067
X-Spam-Level: 
X-Spam-Status: No, score=-1.067 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, IP_NOT_FRIENDLY=0.334, J_CHICKENPOX_42=0.6, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001] autolearn=no
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 XywCjlyNOCJs for <tools-development@ietfa.amsl.com>; Thu, 22 Oct 2015 05:34:26 -0700 (PDT)
Received: from gproxy8-pub.mail.unifiedlayer.com (gproxy8-pub.mail.unifiedlayer.com [67.222.33.93]) by ietfa.amsl.com (Postfix) with SMTP id 0FD3D1B366E for <tools-development@ietf.org>; Thu, 22 Oct 2015 05:34:25 -0700 (PDT)
Received: (qmail 9596 invoked by uid 0); 22 Oct 2015 12:34:22 -0000
Received: from unknown (HELO cmgw3) (10.0.90.84) by gproxy8.mail.unifiedlayer.com with SMTP; 22 Oct 2015 12:34:21 -0000
Received: from box313.bluehost.com ([69.89.31.113]) by cmgw3 with  id YJaH1r0032SSUrH01JaLBS; Thu, 22 Oct 2015 12:34:20 -0600
X-Authority-Analysis: v=2.1 cv=Zs1+dbLG c=1 sm=1 tr=0 a=h1BC+oY+fLhyFmnTBx92Jg==:117 a=wU2YTnxGAAAA:8 a=cNaOj0WVAAAA:8 a=IkcTkHD0fZMA:10 a=-NfooI8aBGcA:10 a=uEJ9t1CZtbIA:10 a=5lJygRwiOn0A:10 a=pGLkceISAAAA:8 a=48vgC7mUAAAA:8 a=fWD_b17KTKnYUSesttAA:9 a=QEXdDO2ut3YA:10
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=labn.net; s=default;  h=Content-Transfer-Encoding:Content-Type:In-Reply-To:MIME-Version:Date:Message-ID:References:To:Subject:From; bh=e8OiSKZkvC9pjzCVedTJptXq2P6oiioD5Uq+GoNvzVY=;  b=dHpLQJJMQ+1R0SrVQg0jGekxYdtn4bUU607NjTIJtP5RgFQYQRyi4YgS/xym+0KlzZInds80PU/1GfECvfhTCZgapVaGllX8j/mDQ6TYkzzrYQuMe5aa4eJgWPaSAPKn;
Received: from box313.bluehost.com ([69.89.31.113]:47555 helo=[127.0.0.1]) by box313.bluehost.com with esmtpa (Exim 4.84) (envelope-from <lberger@labn.net>) id 1ZpF4U-0001r0-J5 for tools-development@ietf.org; Thu, 22 Oct 2015 06:34:18 -0600
From: Lou Berger <lberger@labn.net>
To: IETF Tools Development <tools-development@ietf.org>
References: <55CA09A7.1030801@nostrum.com> <55DF7527.1020201@nostrum.com> <CABtrr-Vh-+hLwYX8qjqC5rYrkE-8WZqy0YCgwHquFMAsdFqBaA@mail.gmail.com> <5628284D.3040808@gmail.com> <EC751011-9ABC-456B-A428-C305EB86F5ED@live555.com> <56284812.2000307@gmail.com> <CAA=duU1Mh1YWegXcVrxtDJi5roiBmTTxFg49AJL79oRJDy=V4g@mail.gmail.com>
Message-ID: <5628D7C6.1090401@labn.net>
Date: Thu, 22 Oct 2015 08:34:14 -0400
User-Agent: Mozilla/5.0 (Windows NT 6.3; WOW64; rv:38.0) Gecko/20100101 Thunderbird/38.3.0
MIME-Version: 1.0
In-Reply-To: <CAA=duU1Mh1YWegXcVrxtDJi5roiBmTTxFg49AJL79oRJDy=V4g@mail.gmail.com>
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 8bit
X-Identified-User: {1038:box313.bluehost.com:labnmobi:labn.net} {sentby:smtp auth 69.89.31.113 authed with lberger@labn.net}
Archived-At: <http://mailarchive.ietf.org/arch/msg/tools-development/dNrmx0Ocp4JxzThN5nLHpdOkWmE>
Subject: [TOOLS-DEVELOPMENT] Fwd: Re: Google threatens to break Gmail
X-BeenThere: tools-development@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: Tools Development list server <tools-development.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/tools-development>, <mailto:tools-development-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/tools-development/>
List-Post: <mailto:tools-development@ietf.org>
List-Help: <mailto:tools-development-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/tools-development>, <mailto:tools-development-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 22 Oct 2015 12:34:27 -0000

Hello,

Does anyone know if Andy's statement correct?  Are there any plans for
this upgrade?

Thanks,
Lou
PS this  is not a thread I'm really paying too much attention to...

--- Forwarded message ---
*From: * 	Andrew G. Malis <agmalis@gmail.com>
*Date: * 	October 22, 2015 6:05:59 AM
*Subject: * 	Re: Google threatens to break Gmail
*To: * 	Brian E Carpenter <brian.e.carpenter@gmail.com>
*CC: * 	IETF Discussion Mailing List <ietf@ietf.org>


There is an easy answer to this, that we discussed on this list over a
year ago - just bring mailman up to a more recent revision. It can
handle DMARC re-writing just fine.

Cheers,
Andy


On Wed, Oct 21, 2015 at 10:21 PM, Brian E Carpenter
<brian.e.carpenter@gmail.com <mailto:brian.e.carpenter@gmail.com>> wrote:

    On 22/10/2015 14:59, Ross Finlayson wrote:
    >> Will the problem with Mailman distribution of DMARC-contaminated
    messages
    >> be fixed in time for this,or must we gmail users start to look for a
    >> more reasonable provider?
    >
    > Or perhaps people who subscribe to IETF mailing lists can start
    doing so using more professional-looking email addresses :-)

    Um, why? We don't represent our employers here, and many people change
    jobs or even countries but prefer their IETF email to continue
    uninterrupted.
    I started using gmail precisely to avoid the problems and
    stupidities of corporate
    email, and of access across travel and relocation, and I know I'm
    not alone.

    > (Note that it’s possible, I think, to continue to use 3rd-party
    email services like ‘Gmail’ with email addresses that use your own
    domain name rather than “@gmail.com <http://gmail.com>" (and, as a
    beneficial side effect, you won’t be subject to DMARC).)

    Only, I think, if your corporate provider has made a suitable deal
    with G.

        Brian




From nobody Thu Oct 22 06:40:07 2015
Return-Path: <housley@vigilsec.com>
X-Original-To: tools-development@ietfa.amsl.com
Delivered-To: tools-development@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id E73BB1A8AD2 for <tools-development@ietfa.amsl.com>; Thu, 22 Oct 2015 06:40:06 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -101.3
X-Spam-Level: 
X-Spam-Status: No, score=-101.3 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, J_CHICKENPOX_42=0.6, USER_IN_WHITELIST=-100] autolearn=no
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 ndPeKD2JqrXx for <tools-development@ietfa.amsl.com>; Thu, 22 Oct 2015 06:40:05 -0700 (PDT)
Received: from odin.smetech.net (x-bolt-wan.smeinc.net [209.135.219.146]) by ietfa.amsl.com (Postfix) with ESMTP id 4F85D1A8AB7 for <tools-development@ietf.org>; Thu, 22 Oct 2015 06:40:05 -0700 (PDT)
Received: from localhost (unknown [209.135.209.5]) by odin.smetech.net (Postfix) with ESMTP id 883B29A4020; Thu, 22 Oct 2015 09:39:54 -0400 (EDT)
X-Virus-Scanned: amavisd-new at smetech.net
Received: from odin.smetech.net ([209.135.209.4]) by localhost (ronin.smeinc.net [209.135.209.5]) (amavisd-new, port 10024) with ESMTP id c8awOCDYoIwl; Thu, 22 Oct 2015 09:38:33 -0400 (EDT)
Received: from [10.196.207.51] (82-194.icannmeeting.org [199.91.194.82]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (No client certificate requested) by odin.smetech.net (Postfix) with ESMTP id 2BF019A4019; Thu, 22 Oct 2015 09:39:33 -0400 (EDT)
Mime-Version: 1.0 (Apple Message framework v1085)
Content-Type: text/plain; charset=windows-1252
From: Russ Housley <housley@vigilsec.com>
In-Reply-To: <5628D7C6.1090401@labn.net>
Date: Thu, 22 Oct 2015 09:39:21 -0400
Content-Transfer-Encoding: quoted-printable
Message-Id: <624168FF-40DA-43B3-A129-F91FD3C4304D@vigilsec.com>
References: <55CA09A7.1030801@nostrum.com> <55DF7527.1020201@nostrum.com> <CABtrr-Vh-+hLwYX8qjqC5rYrkE-8WZqy0YCgwHquFMAsdFqBaA@mail.gmail.com> <5628284D.3040808@gmail.com> <EC751011-9ABC-456B-A428-C305EB86F5ED@live555.com> <56284812.2000307@gmail.com> <CAA=duU1Mh1YWegXcVrxtDJi5roiBmTTxFg49AJL79oRJDy=V4g@mail.gmail.com> <5628D7C6.1090401@labn.net>
To: Lou Berger <lberger@labn.net>
X-Mailer: Apple Mail (2.1085)
Archived-At: <http://mailarchive.ietf.org/arch/msg/tools-development/kqIxx5DqcAqC78vNAZEy0P6CSDM>
Cc: IETF Tools Development <tools-development@ietf.org>
Subject: Re: [TOOLS-DEVELOPMENT] Fwd: Re: Google threatens to break Gmail
X-BeenThere: tools-development@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: Tools Development list server <tools-development.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/tools-development>, <mailto:tools-development-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/tools-development/>
List-Post: <mailto:tools-development@ietf.org>
List-Help: <mailto:tools-development-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/tools-development>, <mailto:tools-development-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 22 Oct 2015 13:40:07 -0000

My understanding is that we are using Mailman 2.1.15.  Mailman 2.1.20 =
and 3.0.0 are available.  We have not asked the Secretariat to reviewed =
every change, but I am told that they are comfortable that Mailman =
2.1.20 is fine.  We have not looked at Mailman 3.0.0 at all.

The version of Mailman beyond 2.1.15 have no capacity for sending out =
password reminders; it was removed.  Brian Carpenter has very loudly =
argued for this capability to be retained.

Russ

On Oct 22, 2015, at 8:34 AM, Lou Berger wrote:

> Hello,
>=20
> Does anyone know if Andy's statement correct?  Are there any plans for
> this upgrade?
>=20
> Thanks,
> Lou
> PS this  is not a thread I'm really paying too much attention to...
>=20
> --- Forwarded message ---
> *From: * 	Andrew G. Malis <agmalis@gmail.com>
> *Date: * 	October 22, 2015 6:05:59 AM
> *Subject: * 	Re: Google threatens to break Gmail
> *To: * 	Brian E Carpenter <brian.e.carpenter@gmail.com>
> *CC: * 	IETF Discussion Mailing List <ietf@ietf.org>
>=20
>=20
> There is an easy answer to this, that we discussed on this list over a
> year ago - just bring mailman up to a more recent revision. It can
> handle DMARC re-writing just fine.
>=20
> Cheers,
> Andy
>=20
>=20
> On Wed, Oct 21, 2015 at 10:21 PM, Brian E Carpenter
> <brian.e.carpenter@gmail.com <mailto:brian.e.carpenter@gmail.com>> =
wrote:
>=20
>    On 22/10/2015 14:59, Ross Finlayson wrote:
>>> Will the problem with Mailman distribution of DMARC-contaminated
>    messages
>>> be fixed in time for this,or must we gmail users start to look for a
>>> more reasonable provider?
>>=20
>> Or perhaps people who subscribe to IETF mailing lists can start
>    doing so using more professional-looking email addresses :-)
>=20
>    Um, why? We don't represent our employers here, and many people =
change
>    jobs or even countries but prefer their IETF email to continue
>    uninterrupted.
>    I started using gmail precisely to avoid the problems and
>    stupidities of corporate
>    email, and of access across travel and relocation, and I know I'm
>    not alone.
>=20
>> (Note that it=92s possible, I think, to continue to use 3rd-party
>    email services like =91Gmail=92 with email addresses that use your =
own
>    domain name rather than =93@gmail.com <http://gmail.com>" (and, as =
a
>    beneficial side effect, you won=92t be subject to DMARC).)
>=20
>    Only, I think, if your corporate provider has made a suitable deal
>    with G.
>=20
>        Brian
>=20
>=20
>=20
> _______________________________________________
> TOOLS-DEVELOPMENT mailing list
> TOOLS-DEVELOPMENT@ietf.org
> https://www.ietf.org/mailman/listinfo/tools-development


From nobody Thu Oct 22 06:46:16 2015
Return-Path: <henrik@levkowetz.com>
X-Original-To: tools-development@ietfa.amsl.com
Delivered-To: tools-development@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 0BC691A9060 for <tools-development@ietfa.amsl.com>; Thu, 22 Oct 2015 06:46:15 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -101.3
X-Spam-Level: 
X-Spam-Status: No, score=-101.3 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, J_CHICKENPOX_42=0.6, USER_IN_WHITELIST=-100] autolearn=no
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 zkaBNQ8PorwX for <tools-development@ietfa.amsl.com>; Thu, 22 Oct 2015 06:46:13 -0700 (PDT)
Received: from zinfandel.tools.ietf.org (zinfandel.tools.ietf.org [IPv6:2001:1890:123a::1:2a]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 999861A904E for <tools-development@ietf.org>; Thu, 22 Oct 2015 06:46:13 -0700 (PDT)
Received: from tannat.netnod.se ([77.72.226.96]:64493) by zinfandel.tools.ietf.org with esmtpsa (TLS1.2:ECDHE_RSA_AES_128_GCM_SHA256:128) (Exim 4.82_1-5b7a7c0-XX) (envelope-from <henrik@levkowetz.com>) id 1ZpGC1-0001Ua-MM; Thu, 22 Oct 2015 06:46:11 -0700
To: Russ Housley <housley@vigilsec.com>, Lou Berger <lberger@labn.net>
References: <55CA09A7.1030801@nostrum.com> <55DF7527.1020201@nostrum.com> <CABtrr-Vh-+hLwYX8qjqC5rYrkE-8WZqy0YCgwHquFMAsdFqBaA@mail.gmail.com> <5628284D.3040808@gmail.com> <EC751011-9ABC-456B-A428-C305EB86F5ED@live555.com> <56284812.2000307@gmail.com> <CAA=duU1Mh1YWegXcVrxtDJi5roiBmTTxFg49AJL79oRJDy=V4g@mail.gmail.com> <5628D7C6.1090401@labn.net> <624168FF-40DA-43B3-A129-F91FD3C4304D@vigilsec.com>
From: Henrik Levkowetz <henrik@levkowetz.com>
Message-ID: <5628E89E.9090609@levkowetz.com>
Date: Thu, 22 Oct 2015 15:46:06 +0200
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.9; rv:38.0) Gecko/20100101 Thunderbird/38.3.0
MIME-Version: 1.0
In-Reply-To: <624168FF-40DA-43B3-A129-F91FD3C4304D@vigilsec.com>
Content-Type: multipart/signed; micalg=pgp-sha256; protocol="application/pgp-signature"; boundary="C5cGv79nmTPv52qsQmONVpQVn33FAjNv4"
X-SA-Exim-Connect-IP: 77.72.226.96
X-SA-Exim-Rcpt-To: henrik-sent@levkowetz.com, tools-development@ietf.org, lberger@labn.net, housley@vigilsec.com
X-SA-Exim-Mail-From: henrik@levkowetz.com
X-SA-Exim-Version: 4.2.1 (built Mon, 26 Dec 2011 16:24:06 +0000)
X-SA-Exim-Scanned: Yes (on zinfandel.tools.ietf.org)
Archived-At: <http://mailarchive.ietf.org/arch/msg/tools-development/CS0ZCMWtRFEsvZ7Yz7eaoOYfmDA>
Cc: IETF Tools Development <tools-development@ietf.org>
Subject: Re: [TOOLS-DEVELOPMENT] Fwd: Re: Google threatens to break Gmail
X-BeenThere: tools-development@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: Tools Development list server <tools-development.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/tools-development>, <mailto:tools-development-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/tools-development/>
List-Post: <mailto:tools-development@ietf.org>
List-Help: <mailto:tools-development-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/tools-development>, <mailto:tools-development-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 22 Oct 2015 13:46:15 -0000

This is an OpenPGP/MIME signed message (RFC 4880 and 3156)
--C5cGv79nmTPv52qsQmONVpQVn33FAjNv4
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: quoted-printable



On 2015-10-22 15:39, Russ Housley wrote:
> My understanding is that we are using Mailman 2.1.15. Mailman 2.1.20
> and 3.0.0 are available. We have not asked the Secretariat to
> reviewed every change, but I am told that they are comfortable that
> Mailman 2.1.20 is fine. We have not looked at Mailman 3.0.0 at all.
>=20
> The version of Mailman beyond 2.1.15 have no capacity for sending out
> password reminders; it was removed. Brian Carpenter has very loudly
> argued for this capability to be retained.

It looks as if 2.1.18 or later in the 2.x.x series may improve things:

	http://wiki.list.org/DEV/DMARC

Regards,

	Henrik



>=20
> Russ
>=20
> On Oct 22, 2015, at 8:34 AM, Lou Berger wrote:
>=20
>> Hello,
>>
>> Does anyone know if Andy's statement correct?  Are there any plans for=

>> this upgrade?
>>
>> Thanks,
>> Lou
>> PS this  is not a thread I'm really paying too much attention to...
>>
>> --- Forwarded message ---
>> *From: * 	Andrew G. Malis <agmalis@gmail.com>
>> *Date: * 	October 22, 2015 6:05:59 AM
>> *Subject: * 	Re: Google threatens to break Gmail
>> *To: * 	Brian E Carpenter <brian.e.carpenter@gmail.com>
>> *CC: * 	IETF Discussion Mailing List <ietf@ietf.org>
>>
>>
>> There is an easy answer to this, that we discussed on this list over a=

>> year ago - just bring mailman up to a more recent revision. It can
>> handle DMARC re-writing just fine.
>>
>> Cheers,
>> Andy
>>
>>
>> On Wed, Oct 21, 2015 at 10:21 PM, Brian E Carpenter
>> <brian.e.carpenter@gmail.com <mailto:brian.e.carpenter@gmail.com>> wro=
te:
>>
>>    On 22/10/2015 14:59, Ross Finlayson wrote:
>>>> Will the problem with Mailman distribution of DMARC-contaminated
>>    messages
>>>> be fixed in time for this,or must we gmail users start to look for a=

>>>> more reasonable provider?
>>>
>>> Or perhaps people who subscribe to IETF mailing lists can start
>>    doing so using more professional-looking email addresses :-)
>>
>>    Um, why? We don't represent our employers here, and many people cha=
nge
>>    jobs or even countries but prefer their IETF email to continue
>>    uninterrupted.
>>    I started using gmail precisely to avoid the problems and
>>    stupidities of corporate
>>    email, and of access across travel and relocation, and I know I'm
>>    not alone.
>>
>>> (Note that it=E2=80=99s possible, I think, to continue to use 3rd-par=
ty
>>    email services like =E2=80=98Gmail=E2=80=99 with email addresses th=
at use your own
>>    domain name rather than =E2=80=9C@gmail.com <http://gmail.com>" (an=
d, as a
>>    beneficial side effect, you won=E2=80=99t be subject to DMARC).)
>>
>>    Only, I think, if your corporate provider has made a suitable deal
>>    with G.
>>
>>        Brian
>>
>>
>>
>> _______________________________________________
>> TOOLS-DEVELOPMENT mailing list
>> TOOLS-DEVELOPMENT@ietf.org
>> https://www.ietf.org/mailman/listinfo/tools-development
>=20
> _______________________________________________
> TOOLS-DEVELOPMENT mailing list
> TOOLS-DEVELOPMENT@ietf.org
> https://www.ietf.org/mailman/listinfo/tools-development
>=20


--C5cGv79nmTPv52qsQmONVpQVn33FAjNv4
Content-Type: application/pgp-signature; name="signature.asc"
Content-Description: OpenPGP digital signature
Content-Disposition: attachment; filename="signature.asc"

-----BEGIN PGP SIGNATURE-----

iQIcBAEBCAAGBQJWKOieAAoJEE6bV0uPuxcaEG0P/ipORztbtosz7BZ4/euWomFA
iK/IDmiv2WqYsrwLVQ3tVIYXL3V0JEm7IM0qNq0F0GESm2P03ty5by1ar0QGd2uY
HnLIF/NoiB7UBF1DMs2z0KN0KXueahUVnfFVBhqB1B52qyO6HDWe5kEzQiFsU/AL
ZVrHsoRhuZkXgs6Cvz9tr7YUyk3cIavUbwoGagM+x/f38uFX0nL1h826GvlajCtJ
H6Rk2sALUSaGY5HM8aSQC72XhUkBLzO5skYrf4f1ziLnPYyzgEDyBHGmjNrHLqph
vS4WSRGgcXFX68J8pu6ZeTdHKsK/Fb8g+HRVHN73teRwsww1DPHWgPXxLVsIprNt
PZJ3uHiRpDc+5ejSNaQM6opmE5EHYAPCbKCngWQdZar6asdqcLcm6NMBtDPvyE/i
OflaKEOJg9lNqSh9IskRyvaAON+uf+P8OdqfERYcVi0EkUOGAhMH0FwhUKBMZuuA
pzmka1+g67tTRIQqRJJSiDfPdNudX3+zor6M1vfRKHVpRsJHoFTG2HWh3TDP4vDP
5UTtLP2RNCE/Pz3CLmd8ASbRw9QXvGfnrljsIRGoceFlWsSsUJLjptkkpXZoiHmz
9EFKj6HE+yn8w3MgKfQ9m8YiHpoVadjs/k9leeu0sT1tj21ehhxXmS30R9wn5yRz
Y/0Zf1NVZrNFflIEJ2Nw
=qfSh
-----END PGP SIGNATURE-----

--C5cGv79nmTPv52qsQmONVpQVn33FAjNv4--


From nobody Thu Oct 22 06:56:12 2015
Return-Path: <glen@amsl.com>
X-Original-To: tools-development@ietfa.amsl.com
Delivered-To: tools-development@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 2CEAC1AC3E1 for <tools-development@ietfa.amsl.com>; Thu, 22 Oct 2015 06:56:11 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -100.688
X-Spam-Level: 
X-Spam-Status: No, score=-100.688 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, FM_FORGED_GMAIL=0.622, HTML_MESSAGE=0.001, J_CHICKENPOX_42=0.6, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01, USER_IN_WHITELIST=-100] autolearn=no
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 qtcQm31Nck_k for <tools-development@ietfa.amsl.com>; Thu, 22 Oct 2015 06:56:09 -0700 (PDT)
Received: from mail.amsl.com (mail.amsl.com [IPv6:2001:1900:3001:11::28]) by ietfa.amsl.com (Postfix) with ESMTP id 3DCDE1AC3DE for <tools-development@ietf.org>; Thu, 22 Oct 2015 06:56:09 -0700 (PDT)
Received: from mail.amsl.com (localhost [127.0.0.1]) by c8a.amsl.com (Postfix) with ESMTP id 081A51E59E4 for <tools-development@ietf.org>; Thu, 22 Oct 2015 06:55:10 -0700 (PDT)
Received: from mail-oi0-f53.google.com (mail-oi0-f53.google.com [209.85.218.53]) by c8a.amsl.com (Postfix) with ESMTPSA id CD6661E59F6 for <tools-development@ietf.org>; Thu, 22 Oct 2015 06:55:09 -0700 (PDT)
Received: by oiao187 with SMTP id o187so47745266oia.3 for <tools-development@ietf.org>; Thu, 22 Oct 2015 06:56:08 -0700 (PDT)
X-Received: by 10.202.67.194 with SMTP id q185mr9299791oia.106.1445522168327;  Thu, 22 Oct 2015 06:56:08 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.202.176.197 with HTTP; Thu, 22 Oct 2015 06:55:49 -0700 (PDT)
In-Reply-To: <5628E89E.9090609@levkowetz.com>
References: <55CA09A7.1030801@nostrum.com> <55DF7527.1020201@nostrum.com> <CABtrr-Vh-+hLwYX8qjqC5rYrkE-8WZqy0YCgwHquFMAsdFqBaA@mail.gmail.com> <5628284D.3040808@gmail.com> <EC751011-9ABC-456B-A428-C305EB86F5ED@live555.com> <56284812.2000307@gmail.com> <CAA=duU1Mh1YWegXcVrxtDJi5roiBmTTxFg49AJL79oRJDy=V4g@mail.gmail.com> <5628D7C6.1090401@labn.net> <624168FF-40DA-43B3-A129-F91FD3C4304D@vigilsec.com> <5628E89E.9090609@levkowetz.com>
From: Glen <glen@amsl.com>
Date: Thu, 22 Oct 2015 06:55:49 -0700
Message-ID: <CABL0ig5MePhrHhCierOpwDEwLg-2Cdg2eQ2=ehb7BUYN2OUFpA@mail.gmail.com>
To: Henrik Levkowetz <henrik@levkowetz.com>
Content-Type: multipart/alternative; boundary=001a113cd06a5bd88d0522b1db28
Archived-At: <http://mailarchive.ietf.org/arch/msg/tools-development/sQODiJ2H-20e_eL55XRC28HzaVk>
Cc: IETF Tools Development <tools-development@ietf.org>
Subject: Re: [TOOLS-DEVELOPMENT] Fwd: Re: Google threatens to break Gmail
X-BeenThere: tools-development@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
Reply-To: glen@amsl.com
List-Id: Tools Development list server <tools-development.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/tools-development>, <mailto:tools-development-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/tools-development/>
List-Post: <mailto:tools-development@ietf.org>
List-Help: <mailto:tools-development-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/tools-development>, <mailto:tools-development-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 22 Oct 2015 13:56:11 -0000

--001a113cd06a5bd88d0522b1db28
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

Yes, it seems that development of the 2.1 branch continued.  Previously the
talk had been halting at 2.1.15 and going straight to 3.0.0.  (There wasn't
previously much movement on or support for Mailman; pleasantly, that
appears to have changed.)

The latest version is 2.1.20, and the .19 and .20 releases contain
bugfixes, so I would think that, if we are going to do an in-place upgrade
of Mailman, we should just go directly to .20

Since Google doesn't plan to do this until next year, there is also the
possibility that we can do the Mailman upgrade as a part of a larger
server/OS upgrade.  Timing and direction of this are still TBD.

Glen



On Thu, Oct 22, 2015 at 6:46 AM, Henrik Levkowetz <henrik@levkowetz.com>
wrote:

>
>
> On 2015-10-22 15:39, Russ Housley wrote:
> > My understanding is that we are using Mailman 2.1.15. Mailman 2.1.20
> > and 3.0.0 are available. We have not asked the Secretariat to
> > reviewed every change, but I am told that they are comfortable that
> > Mailman 2.1.20 is fine. We have not looked at Mailman 3.0.0 at all.
> >
> > The version of Mailman beyond 2.1.15 have no capacity for sending out
> > password reminders; it was removed. Brian Carpenter has very loudly
> > argued for this capability to be retained.
>
> It looks as if 2.1.18 or later in the 2.x.x series may improve things:
>
>         http://wiki.list.org/DEV/DMARC
>
> Regards,
>
>         Henrik
>
>
>
> >
> > Russ
> >
> > On Oct 22, 2015, at 8:34 AM, Lou Berger wrote:
> >
> >> Hello,
> >>
> >> Does anyone know if Andy's statement correct?  Are there any plans for
> >> this upgrade?
> >>
> >> Thanks,
> >> Lou
> >> PS this  is not a thread I'm really paying too much attention to...
> >>
> >> --- Forwarded message ---
> >> *From: *     Andrew G. Malis <agmalis@gmail.com>
> >> *Date: *     October 22, 2015 6:05:59 AM
> >> *Subject: *  Re: Google threatens to break Gmail
> >> *To: *       Brian E Carpenter <brian.e.carpenter@gmail.com>
> >> *CC: *       IETF Discussion Mailing List <ietf@ietf.org>
> >>
> >>
> >> There is an easy answer to this, that we discussed on this list over a
> >> year ago - just bring mailman up to a more recent revision. It can
> >> handle DMARC re-writing just fine.
> >>
> >> Cheers,
> >> Andy
> >>
> >>
> >> On Wed, Oct 21, 2015 at 10:21 PM, Brian E Carpenter
> >> <brian.e.carpenter@gmail.com <mailto:brian.e.carpenter@gmail.com>>
> wrote:
> >>
> >>    On 22/10/2015 14:59, Ross Finlayson wrote:
> >>>> Will the problem with Mailman distribution of DMARC-contaminated
> >>    messages
> >>>> be fixed in time for this,or must we gmail users start to look for a
> >>>> more reasonable provider?
> >>>
> >>> Or perhaps people who subscribe to IETF mailing lists can start
> >>    doing so using more professional-looking email addresses :-)
> >>
> >>    Um, why? We don't represent our employers here, and many people
> change
> >>    jobs or even countries but prefer their IETF email to continue
> >>    uninterrupted.
> >>    I started using gmail precisely to avoid the problems and
> >>    stupidities of corporate
> >>    email, and of access across travel and relocation, and I know I'm
> >>    not alone.
> >>
> >>> (Note that it=E2=80=99s possible, I think, to continue to use 3rd-par=
ty
> >>    email services like =E2=80=98Gmail=E2=80=99 with email addresses th=
at use your own
> >>    domain name rather than =E2=80=9C@gmail.com <http://gmail.com>" (an=
d, as a
> >>    beneficial side effect, you won=E2=80=99t be subject to DMARC).)
> >>
> >>    Only, I think, if your corporate provider has made a suitable deal
> >>    with G.
> >>
> >>        Brian
> >>
> >>
> >>
> >> _______________________________________________
> >> TOOLS-DEVELOPMENT mailing list
> >> TOOLS-DEVELOPMENT@ietf.org
> >> https://www.ietf.org/mailman/listinfo/tools-development
> >
> > _______________________________________________
> > TOOLS-DEVELOPMENT mailing list
> > TOOLS-DEVELOPMENT@ietf.org
> > https://www.ietf.org/mailman/listinfo/tools-development
> >
>
>
> _______________________________________________
> TOOLS-DEVELOPMENT mailing list
> TOOLS-DEVELOPMENT@ietf.org
> https://www.ietf.org/mailman/listinfo/tools-development
>
>

--001a113cd06a5bd88d0522b1db28
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr">Yes, it seems that development of the 2.1 branch continued=
.=C2=A0 Previously the talk had been halting at 2.1.15 and going straight t=
o 3.0.0.=C2=A0 (There wasn&#39;t previously much movement on or support for=
 Mailman; pleasantly, that appears to have changed.)<br><div><div><br>The l=
atest version is 2.1.20, and the .19 and .20 releases contain bugfixes, so =
I would think that, if we are going to do an in-place upgrade of Mailman, w=
e should just go directly to .20<br><br></div><div>Since Google doesn&#39;t=
 plan to do this until next year, there is also the possibility that we can=
 do the Mailman upgrade as a part of a larger server/OS upgrade.=C2=A0 Timi=
ng and direction of this are still TBD.<br><br></div><div>Glen<br></div><di=
v><br><br></div></div></div><div class=3D"gmail_extra"><br><div class=3D"gm=
ail_quote">On Thu, Oct 22, 2015 at 6:46 AM, Henrik Levkowetz <span dir=3D"l=
tr">&lt;<a href=3D"mailto:henrik@levkowetz.com" target=3D"_blank">henrik@le=
vkowetz.com</a>&gt;</span> wrote:<br><blockquote class=3D"gmail_quote" styl=
e=3D"margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><br>
<br>
On 2015-10-22 15:39, Russ Housley wrote:<br>
&gt; My understanding is that we are using Mailman 2.1.15. Mailman 2.1.20<b=
r>
&gt; and 3.0.0 are available. We have not asked the Secretariat to<br>
&gt; reviewed every change, but I am told that they are comfortable that<br=
>
&gt; Mailman 2.1.20 is fine. We have not looked at Mailman 3.0.0 at all.<br=
>
&gt;<br>
&gt; The version of Mailman beyond 2.1.15 have no capacity for sending out<=
br>
&gt; password reminders; it was removed. Brian Carpenter has very loudly<br=
>
&gt; argued for this capability to be retained.<br>
<br>
It looks as if 2.1.18 or later in the 2.x.x series may improve things:<br>
<br>
=C2=A0 =C2=A0 =C2=A0 =C2=A0 <a href=3D"http://wiki.list.org/DEV/DMARC" rel=
=3D"noreferrer" target=3D"_blank">http://wiki.list.org/DEV/DMARC</a><br>
<br>
Regards,<br>
<br>
=C2=A0 =C2=A0 =C2=A0 =C2=A0 Henrik<br>
<br>
<br>
<br>
&gt;<br>
&gt; Russ<br>
&gt;<br>
&gt; On Oct 22, 2015, at 8:34 AM, Lou Berger wrote:<br>
&gt;<br>
&gt;&gt; Hello,<br>
&gt;&gt;<br>
&gt;&gt; Does anyone know if Andy&#39;s statement correct?=C2=A0 Are there =
any plans for<br>
&gt;&gt; this upgrade?<br>
&gt;&gt;<br>
&gt;&gt; Thanks,<br>
&gt;&gt; Lou<br>
&gt;&gt; PS this=C2=A0 is not a thread I&#39;m really paying too much atten=
tion to...<br>
&gt;&gt;<br>
&gt;&gt; --- Forwarded message ---<br>
&gt;&gt; *From: *=C2=A0 =C2=A0 =C2=A0Andrew G. Malis &lt;<a href=3D"mailto:=
agmalis@gmail.com">agmalis@gmail.com</a>&gt;<br>
&gt;&gt; *Date: *=C2=A0 =C2=A0 =C2=A0October 22, 2015 6:05:59 AM<br>
&gt;&gt; *Subject: *=C2=A0 Re: Google threatens to break Gmail<br>
&gt;&gt; *To: *=C2=A0 =C2=A0 =C2=A0 =C2=A0Brian E Carpenter &lt;<a href=3D"=
mailto:brian.e.carpenter@gmail.com">brian.e.carpenter@gmail.com</a>&gt;<br>
&gt;&gt; *CC: *=C2=A0 =C2=A0 =C2=A0 =C2=A0IETF Discussion Mailing List &lt;=
<a href=3D"mailto:ietf@ietf.org">ietf@ietf.org</a>&gt;<br>
&gt;&gt;<br>
&gt;&gt;<br>
&gt;&gt; There is an easy answer to this, that we discussed on this list ov=
er a<br>
&gt;&gt; year ago - just bring mailman up to a more recent revision. It can=
<br>
&gt;&gt; handle DMARC re-writing just fine.<br>
&gt;&gt;<br>
&gt;&gt; Cheers,<br>
&gt;&gt; Andy<br>
&gt;&gt;<br>
&gt;&gt;<br>
&gt;&gt; On Wed, Oct 21, 2015 at 10:21 PM, Brian E Carpenter<br>
&gt;&gt; &lt;<a href=3D"mailto:brian.e.carpenter@gmail.com">brian.e.carpent=
er@gmail.com</a> &lt;mailto:<a href=3D"mailto:brian.e.carpenter@gmail.com">=
brian.e.carpenter@gmail.com</a>&gt;&gt; wrote:<br>
&gt;&gt;<br>
&gt;&gt;=C2=A0 =C2=A0 On 22/10/2015 14:59, Ross Finlayson wrote:<br>
&gt;&gt;&gt;&gt; Will the problem with Mailman distribution of DMARC-contam=
inated<br>
&gt;&gt;=C2=A0 =C2=A0 messages<br>
&gt;&gt;&gt;&gt; be fixed in time for this,or must we gmail users start to =
look for a<br>
&gt;&gt;&gt;&gt; more reasonable provider?<br>
&gt;&gt;&gt;<br>
&gt;&gt;&gt; Or perhaps people who subscribe to IETF mailing lists can star=
t<br>
&gt;&gt;=C2=A0 =C2=A0 doing so using more professional-looking email addres=
ses :-)<br>
&gt;&gt;<br>
&gt;&gt;=C2=A0 =C2=A0 Um, why? We don&#39;t represent our employers here, a=
nd many people change<br>
&gt;&gt;=C2=A0 =C2=A0 jobs or even countries but prefer their IETF email to=
 continue<br>
&gt;&gt;=C2=A0 =C2=A0 uninterrupted.<br>
&gt;&gt;=C2=A0 =C2=A0 I started using gmail precisely to avoid the problems=
 and<br>
&gt;&gt;=C2=A0 =C2=A0 stupidities of corporate<br>
&gt;&gt;=C2=A0 =C2=A0 email, and of access across travel and relocation, an=
d I know I&#39;m<br>
&gt;&gt;=C2=A0 =C2=A0 not alone.<br>
&gt;&gt;<br>
&gt;&gt;&gt; (Note that it=E2=80=99s possible, I think, to continue to use =
3rd-party<br>
&gt;&gt;=C2=A0 =C2=A0 email services like =E2=80=98Gmail=E2=80=99 with emai=
l addresses that use your own<br>
&gt;&gt;=C2=A0 =C2=A0 domain name rather than =E2=80=9C@<a href=3D"http://g=
mail.com" rel=3D"noreferrer" target=3D"_blank">gmail.com</a> &lt;<a href=3D=
"http://gmail.com" rel=3D"noreferrer" target=3D"_blank">http://gmail.com</a=
>&gt;&quot; (and, as a<br>
&gt;&gt;=C2=A0 =C2=A0 beneficial side effect, you won=E2=80=99t be subject =
to DMARC).)<br>
&gt;&gt;<br>
&gt;&gt;=C2=A0 =C2=A0 Only, I think, if your corporate provider has made a =
suitable deal<br>
&gt;&gt;=C2=A0 =C2=A0 with G.<br>
&gt;&gt;<br>
&gt;&gt;=C2=A0 =C2=A0 =C2=A0 =C2=A0 Brian<br>
&gt;&gt;<br>
&gt;&gt;<br>
&gt;&gt;<br>
&gt;&gt; _______________________________________________<br>
&gt;&gt; TOOLS-DEVELOPMENT mailing list<br>
&gt;&gt; <a href=3D"mailto:TOOLS-DEVELOPMENT@ietf.org">TOOLS-DEVELOPMENT@ie=
tf.org</a><br>
&gt;&gt; <a href=3D"https://www.ietf.org/mailman/listinfo/tools-development=
" rel=3D"noreferrer" target=3D"_blank">https://www.ietf.org/mailman/listinf=
o/tools-development</a><br>
&gt;<br>
&gt; _______________________________________________<br>
&gt; TOOLS-DEVELOPMENT mailing list<br>
&gt; <a href=3D"mailto:TOOLS-DEVELOPMENT@ietf.org">TOOLS-DEVELOPMENT@ietf.o=
rg</a><br>
&gt; <a href=3D"https://www.ietf.org/mailman/listinfo/tools-development" re=
l=3D"noreferrer" target=3D"_blank">https://www.ietf.org/mailman/listinfo/to=
ols-development</a><br>
&gt;<br>
<br>
<br>_______________________________________________<br>
TOOLS-DEVELOPMENT mailing list<br>
<a href=3D"mailto:TOOLS-DEVELOPMENT@ietf.org">TOOLS-DEVELOPMENT@ietf.org</a=
><br>
<a href=3D"https://www.ietf.org/mailman/listinfo/tools-development" rel=3D"=
noreferrer" target=3D"_blank">https://www.ietf.org/mailman/listinfo/tools-d=
evelopment</a><br>
<br></blockquote></div><br></div>

--001a113cd06a5bd88d0522b1db28--


From nobody Fri Oct 30 16:38:21 2015
Return-Path: <glen@amsl.com>
X-Original-To: tools-development@ietfa.amsl.com
Delivered-To: tools-development@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 681801A049A; Fri, 30 Oct 2015 16:38:19 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -99.389
X-Spam-Level: 
X-Spam-Status: No, score=-99.389 tagged_above=-999 required=5 tests=[BAYES_20=-0.001, FM_FORGED_GMAIL=0.622, HTML_MESSAGE=0.001, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01, USER_IN_WHITELIST=-100] autolearn=no
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 nW1d5dOcZ-Ch; Fri, 30 Oct 2015 16:38:18 -0700 (PDT)
Received: from mail.amsl.com (mail.amsl.com [IPv6:2001:1900:3001:11::28]) by ietfa.amsl.com (Postfix) with ESMTP id 4B91E1A03C7; Fri, 30 Oct 2015 16:38:18 -0700 (PDT)
Received: from mail.amsl.com (localhost [127.0.0.1]) by c8a.amsl.com (Postfix) with ESMTP id D75EA1E5A28; Fri, 30 Oct 2015 16:37:56 -0700 (PDT)
Received: from mail-ob0-f169.google.com (mail-ob0-f169.google.com [209.85.214.169]) by c8a.amsl.com (Postfix) with ESMTPSA id B09671E5A2B; Fri, 30 Oct 2015 16:37:56 -0700 (PDT)
Received: by obbza9 with SMTP id za9so56238747obb.1; Fri, 30 Oct 2015 16:38:17 -0700 (PDT)
X-Received: by 10.60.157.131 with SMTP id wm3mr7438467oeb.26.1446248297422; Fri, 30 Oct 2015 16:38:17 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.202.60.87 with HTTP; Fri, 30 Oct 2015 16:37:58 -0700 (PDT)
From: Glen <glen@amsl.com>
Date: Fri, 30 Oct 2015 16:37:58 -0700
Message-ID: <CABL0ig7ikUvaBasPfrTm97ha=zcFMnQezquDS_O1PPQguQ39DA@mail.gmail.com>
To: IESG <iesg@ietf.org>, IAOC IAOC <iaoc@ietf.org>, wgchairs@ietf.org,  IAB IAB <iab@iab.org>
Content-Type: multipart/alternative; boundary=047d7bd6beda06672205235aec83
Archived-At: <http://mailarchive.ietf.org/arch/msg/tools-development/b-TKq3bXgauO9tlSXJWaUXRgDEA>
Cc: IETF Tools Development <tools-development@ietf.org>
Subject: [TOOLS-DEVELOPMENT] Mailman moderation message issue
X-BeenThere: tools-development@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
Reply-To: glen@amsl.com
List-Id: Tools Development list server <tools-development.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/tools-development>, <mailto:tools-development-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/tools-development/>
List-Post: <mailto:tools-development@ietf.org>
List-Help: <mailto:tools-development-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/tools-development>, <mailto:tools-development-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 30 Oct 2015 23:38:19 -0000

--047d7bd6beda06672205235aec83
Content-Type: text/plain; charset=UTF-8

Dear IETF Leadership:

A problem has been discovered wherein Mailman list moderation alert
messages were not being sent to mailing list owners.  This was being caused
by list owner aliases not being recognized by the mail transport system.

We have regenerated the mail transport configuration and rebuilt the alias
tables, and the issue has been resolved..

In the meantime, any of you who run mailing lists should check your list
moderation queues, when you have time, to ensure that any old messages are
processed or cleared.

We apologize for the inconvenience here.

Glen
Glen Barney
IT Director
AMS (IETF Secretariat)

--047d7bd6beda06672205235aec83
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr"><div><div><div><div><div><div><div><div>Dear IETF Leadersh=
ip:<br><br></div>A problem has been discovered wherein Mailman list moderat=
ion alert messages were not being sent to mailing list owners.=C2=A0 This w=
as being caused by list owner aliases not being recognized by the mail tran=
sport system.<br><br></div>We have regenerated the mail transport configura=
tion and rebuilt the alias tables, and the issue has been resolved..<br><br=
></div>In the meantime, any of you who run mailing lists should check your =
list moderation queues, when you have time, to ensure that any old messages=
 are processed or cleared.<br><br></div>We apologize for the inconvenience =
here.<br><br></div>Glen<br></div>Glen Barney<br></div>IT Director<br></div>=
AMS (IETF Secretariat)<br><br><div><div><div><div><div><div><div><div><br><=
br></div></div></div></div></div></div></div></div></div>

--047d7bd6beda06672205235aec83--


From nobody Sat Oct 31 18:31:37 2015
Return-Path: <glen@amsl.com>
X-Original-To: tools-development@ietfa.amsl.com
Delivered-To: tools-development@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 118D71B4C9A; Sat, 31 Oct 2015 18:31:30 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -101.288
X-Spam-Level: 
X-Spam-Status: No, score=-101.288 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, FM_FORGED_GMAIL=0.622, HTML_MESSAGE=0.001, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01, USER_IN_WHITELIST=-100] autolearn=no
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 42gbV8zx9zNu; Sat, 31 Oct 2015 18:31:29 -0700 (PDT)
Received: from mail.amsl.com (mail.amsl.com [IPv6:2001:1900:3001:11::28]) by ietfa.amsl.com (Postfix) with ESMTP id EB7371B4C99; Sat, 31 Oct 2015 18:31:28 -0700 (PDT)
Received: from mail.amsl.com (localhost [127.0.0.1]) by c8a.amsl.com (Postfix) with ESMTP id 40B291E59F2; Sat, 31 Oct 2015 18:31:03 -0700 (PDT)
Received: from mail-oi0-f50.google.com (mail-oi0-f50.google.com [209.85.218.50]) by c8a.amsl.com (Postfix) with ESMTPSA id 1FC321E59F6; Sat, 31 Oct 2015 18:31:03 -0700 (PDT)
Received: by oiao187 with SMTP id o187so78637647oia.3; Sat, 31 Oct 2015 18:31:28 -0700 (PDT)
X-Received: by 10.202.108.139 with SMTP id h133mr9853911oic.53.1446341488172;  Sat, 31 Oct 2015 18:31:28 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.202.60.87 with HTTP; Sat, 31 Oct 2015 18:31:08 -0700 (PDT)
In-Reply-To: <20151101003318.GE9839@mx2.yitter.info>
References: <CABL0ig7ikUvaBasPfrTm97ha=zcFMnQezquDS_O1PPQguQ39DA@mail.gmail.com> <20151101003318.GE9839@mx2.yitter.info>
From: Glen <glen@amsl.com>
Date: Sat, 31 Oct 2015 18:31:08 -0700
Message-ID: <CABL0ig5AcfMXEKxH8OXK3sV8W+28gkUYRkN4Bdm3jtGmJqAjuA@mail.gmail.com>
To: Andrew Sullivan <ajs@anvilwalrusden.com>
Content-Type: multipart/alternative; boundary=001a1142ef90a066720523709e8d
Archived-At: <http://mailarchive.ietf.org/arch/msg/tools-development/7LRYrYLsy7rHFSoBefZo6bZlxs0>
Cc: IETF Tools Development <tools-development@ietf.org>, IAOC IAOC <iaoc@ietf.org>, IAB IAB <iab@iab.org>, IESG <iesg@ietf.org>, wgchairs@ietf.org
Subject: Re: [TOOLS-DEVELOPMENT] [IAB] Mailman moderation message issue
X-BeenThere: tools-development@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
Reply-To: glen@amsl.com
List-Id: Tools Development list server <tools-development.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/tools-development>, <mailto:tools-development-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/tools-development/>
List-Post: <mailto:tools-development@ietf.org>
List-Help: <mailto:tools-development-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/tools-development>, <mailto:tools-development-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sun, 01 Nov 2015 01:31:30 -0000

--001a1142ef90a066720523709e8d
Content-Type: text/plain; charset=UTF-8

I'll follow up with Andrew directly now, and if there's anything else to
report, we will send an update to this group.

Glen


On Sat, Oct 31, 2015 at 5:33 PM, Andrew Sullivan <ajs@anvilwalrusden.com>
wrote:

> I'm still hearing reports from moderators that iab@iab.org messages
> aren't happening.  Could there be an additional thing for iab.org?
>
> A
>
> On Fri, Oct 30, 2015 at 04:37:58PM -0700, Glen wrote:
> > Dear IETF Leadership:
> >
> > A problem has been discovered wherein Mailman list moderation alert
> > messages were not being sent to mailing list owners.  This was being
> caused
> > by list owner aliases not being recognized by the mail transport system.
> >
> > We have regenerated the mail transport configuration and rebuilt the
> alias
> > tables, and the issue has been resolved..
> >
> > In the meantime, any of you who run mailing lists should check your list
> > moderation queues, when you have time, to ensure that any old messages
> are
> > processed or cleared.
> >
> > We apologize for the inconvenience here.
> >
> > Glen
> > Glen Barney
> > IT Director
> > AMS (IETF Secretariat)
>
> --
> Andrew Sullivan
> ajs@anvilwalrusden.com
>
>

--001a1142ef90a066720523709e8d
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr"><div>I&#39;ll follow up with Andrew directly now, and if t=
here&#39;s anything else to report, we will send an update to this group.<b=
r><br></div>Glen<br><br></div><div class=3D"gmail_extra"><br><div class=3D"=
gmail_quote">On Sat, Oct 31, 2015 at 5:33 PM, Andrew Sullivan <span dir=3D"=
ltr">&lt;<a href=3D"mailto:ajs@anvilwalrusden.com" target=3D"_blank">ajs@an=
vilwalrusden.com</a>&gt;</span> wrote:<br><blockquote class=3D"gmail_quote"=
 style=3D"margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">I&=
#39;m still hearing reports from moderators that <a href=3D"mailto:iab@iab.=
org">iab@iab.org</a> messages<br>
aren&#39;t happening.=C2=A0 Could there be an additional thing for <a href=
=3D"http://iab.org" rel=3D"noreferrer" target=3D"_blank">iab.org</a>?<br>
<br>
A<br>
<br>
On Fri, Oct 30, 2015 at 04:37:58PM -0700, Glen wrote:<br>
&gt; Dear IETF Leadership:<br>
&gt;<br>
&gt; A problem has been discovered wherein Mailman list moderation alert<br=
>
&gt; messages were not being sent to mailing list owners.=C2=A0 This was be=
ing caused<br>
&gt; by list owner aliases not being recognized by the mail transport syste=
m.<br>
&gt;<br>
&gt; We have regenerated the mail transport configuration and rebuilt the a=
lias<br>
&gt; tables, and the issue has been resolved..<br>
&gt;<br>
&gt; In the meantime, any of you who run mailing lists should check your li=
st<br>
&gt; moderation queues, when you have time, to ensure that any old messages=
 are<br>
&gt; processed or cleared.<br>
&gt;<br>
&gt; We apologize for the inconvenience here.<br>
&gt;<br>
&gt; Glen<br>
&gt; Glen Barney<br>
&gt; IT Director<br>
&gt; AMS (IETF Secretariat)<br>
<span class=3D"HOEnZb"><font color=3D"#888888"><br>
--<br>
Andrew Sullivan<br>
<a href=3D"mailto:ajs@anvilwalrusden.com">ajs@anvilwalrusden.com</a><br>
<br>
</font></span></blockquote></div><br></div>

--001a1142ef90a066720523709e8d--


From nobody Sat Oct 31 18:58:03 2015
Return-Path: <glen@amsl.com>
X-Original-To: tools-development@ietfa.amsl.com
Delivered-To: tools-development@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 489E71B4F52; Sat, 31 Oct 2015 18:57:55 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -101.288
X-Spam-Level: 
X-Spam-Status: No, score=-101.288 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, FM_FORGED_GMAIL=0.622, HTML_MESSAGE=0.001, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01, USER_IN_WHITELIST=-100] autolearn=no
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 2WMudFeVhTXv; Sat, 31 Oct 2015 18:57:54 -0700 (PDT)
Received: from mail.amsl.com (mail.amsl.com [IPv6:2001:1900:3001:11::28]) by ietfa.amsl.com (Postfix) with ESMTP id 1FA831B4F4F; Sat, 31 Oct 2015 18:57:54 -0700 (PDT)
Received: from mail.amsl.com (localhost [127.0.0.1]) by c8a.amsl.com (Postfix) with ESMTP id 56A601E59FA; Sat, 31 Oct 2015 18:57:28 -0700 (PDT)
Received: from mail-oi0-f53.google.com (mail-oi0-f53.google.com [209.85.218.53]) by c8a.amsl.com (Postfix) with ESMTPSA id 312BD1E59FB; Sat, 31 Oct 2015 18:57:28 -0700 (PDT)
Received: by oiao187 with SMTP id o187so78775575oia.3; Sat, 31 Oct 2015 18:57:53 -0700 (PDT)
X-Received: by 10.202.189.65 with SMTP id n62mr2749214oif.87.1446343073465; Sat, 31 Oct 2015 18:57:53 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.202.60.87 with HTTP; Sat, 31 Oct 2015 18:57:34 -0700 (PDT)
In-Reply-To: <CABL0ig5AcfMXEKxH8OXK3sV8W+28gkUYRkN4Bdm3jtGmJqAjuA@mail.gmail.com>
References: <CABL0ig7ikUvaBasPfrTm97ha=zcFMnQezquDS_O1PPQguQ39DA@mail.gmail.com> <20151101003318.GE9839@mx2.yitter.info> <CABL0ig5AcfMXEKxH8OXK3sV8W+28gkUYRkN4Bdm3jtGmJqAjuA@mail.gmail.com>
From: Glen <glen@amsl.com>
Date: Sat, 31 Oct 2015 18:57:34 -0700
Message-ID: <CABL0ig4J+JMJFMM4k9XzSv_R-QPtS8kTFEtOf43iL32JG9U=Rw@mail.gmail.com>
To: Andrew Sullivan <ajs@anvilwalrusden.com>
Content-Type: multipart/alternative; boundary=001a113d69fe1e0a60052370fd19
Archived-At: <http://mailarchive.ietf.org/arch/msg/tools-development/_Gfdjg83TxeeYCRMM9usLZLAyVw>
Cc: IETF Tools Development <tools-development@ietf.org>, IAOC IAOC <iaoc@ietf.org>, IAB IAB <iab@iab.org>, IESG <iesg@ietf.org>, wgchairs@ietf.org
Subject: Re: [TOOLS-DEVELOPMENT] [IAB] Mailman moderation message issue
X-BeenThere: tools-development@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
Reply-To: glen@amsl.com
List-Id: Tools Development list server <tools-development.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/tools-development>, <mailto:tools-development-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/tools-development/>
List-Post: <mailto:tools-development@ietf.org>
List-Help: <mailto:tools-development-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/tools-development>, <mailto:tools-development-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sun, 01 Nov 2015 01:57:55 -0000

--001a113d69fe1e0a60052370fd19
Content-Type: text/plain; charset=UTF-8

Just so nobody worries...

Andrew's problem turned out to be just Mary not receiving moderation
messages - that was due to a test alias I had put in during debugging
yesterday.  I've cleared that up, and have checked the logs and confirmed
that all other lists are receiving moderation messages normally now (as was
the IAB list - just not Mary.)  She's fixed now.

Glen

On Sat, Oct 31, 2015 at 6:31 PM, Glen <glen@amsl.com> wrote:

> I'll follow up with Andrew directly now, and if there's anything else to
> report, we will send an update to this group.
>
> Glen
>
>
> On Sat, Oct 31, 2015 at 5:33 PM, Andrew Sullivan <ajs@anvilwalrusden.com>
> wrote:
>
>> I'm still hearing reports from moderators that iab@iab.org messages
>> aren't happening.  Could there be an additional thing for iab.org?
>>
>> A
>>
>> On Fri, Oct 30, 2015 at 04:37:58PM -0700, Glen wrote:
>> > Dear IETF Leadership:
>> >
>> > A problem has been discovered wherein Mailman list moderation alert
>> > messages were not being sent to mailing list owners.  This was being
>> caused
>> > by list owner aliases not being recognized by the mail transport system.
>> >
>> > We have regenerated the mail transport configuration and rebuilt the
>> alias
>> > tables, and the issue has been resolved..
>> >
>> > In the meantime, any of you who run mailing lists should check your list
>> > moderation queues, when you have time, to ensure that any old messages
>> are
>> > processed or cleared.
>> >
>> > We apologize for the inconvenience here.
>> >
>> > Glen
>> > Glen Barney
>> > IT Director
>> > AMS (IETF Secretariat)
>>
>> --
>> Andrew Sullivan
>> ajs@anvilwalrusden.com
>>
>>
>

--001a113d69fe1e0a60052370fd19
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr"><div>Just so nobody worries...<br></div><div><br>Andrew&#3=
9;s problem turned out to be just Mary not receiving moderation messages - =
that was due to a test alias I had put in during debugging yesterday.=C2=A0=
 I&#39;ve cleared that up, and have checked the logs and confirmed that all=
 other lists are receiving moderation messages normally now (as was the IAB=
 list - just not Mary.)=C2=A0 She&#39;s fixed now.<br><br></div>Glen<br></d=
iv><div class=3D"gmail_extra"><br><div class=3D"gmail_quote">On Sat, Oct 31=
, 2015 at 6:31 PM, Glen <span dir=3D"ltr">&lt;<a href=3D"mailto:glen@amsl.c=
om" target=3D"_blank">glen@amsl.com</a>&gt;</span> wrote:<br><blockquote cl=
ass=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1px #ccc solid;p=
adding-left:1ex"><div dir=3D"ltr"><div>I&#39;ll follow up with Andrew direc=
tly now, and if there&#39;s anything else to report, we will send an update=
 to this group.<br><br></div>Glen<br><br></div><div class=3D"gmail_extra"><=
br><div class=3D"gmail_quote">On Sat, Oct 31, 2015 at 5:33 PM, Andrew Sulli=
van <span dir=3D"ltr">&lt;<a href=3D"mailto:ajs@anvilwalrusden.com" target=
=3D"_blank">ajs@anvilwalrusden.com</a>&gt;</span> wrote:<br><blockquote cla=
ss=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1px #ccc solid;pa=
dding-left:1ex">I&#39;m still hearing reports from moderators that <a href=
=3D"mailto:iab@iab.org" target=3D"_blank">iab@iab.org</a> messages<br>
aren&#39;t happening.=C2=A0 Could there be an additional thing for <a href=
=3D"http://iab.org" rel=3D"noreferrer" target=3D"_blank">iab.org</a>?<br>
<br>
A<br>
<br>
On Fri, Oct 30, 2015 at 04:37:58PM -0700, Glen wrote:<br>
&gt; Dear IETF Leadership:<br>
&gt;<br>
&gt; A problem has been discovered wherein Mailman list moderation alert<br=
>
&gt; messages were not being sent to mailing list owners.=C2=A0 This was be=
ing caused<br>
&gt; by list owner aliases not being recognized by the mail transport syste=
m.<br>
&gt;<br>
&gt; We have regenerated the mail transport configuration and rebuilt the a=
lias<br>
&gt; tables, and the issue has been resolved..<br>
&gt;<br>
&gt; In the meantime, any of you who run mailing lists should check your li=
st<br>
&gt; moderation queues, when you have time, to ensure that any old messages=
 are<br>
&gt; processed or cleared.<br>
&gt;<br>
&gt; We apologize for the inconvenience here.<br>
&gt;<br>
&gt; Glen<br>
&gt; Glen Barney<br>
&gt; IT Director<br>
&gt; AMS (IETF Secretariat)<span class=3D"HOEnZb"><font color=3D"#888888"><=
br>
<span><font color=3D"#888888"><br>
--<br>
Andrew Sullivan<br>
<a href=3D"mailto:ajs@anvilwalrusden.com" target=3D"_blank">ajs@anvilwalrus=
den.com</a><br>
<br>
</font></span></font></span></blockquote></div><br></div>
</blockquote></div><br></div>

--001a113d69fe1e0a60052370fd19--

