From nobody Tue Apr 1 12:22:21 2014 Return-Path: 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 4D0461A09E1 for ; Tue, 1 Apr 2014 12:22:17 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -2.61 X-Spam-Level: X-Spam-Status: No, score=-2.61 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_LOW=-0.7, 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 RhJkRJPPdMUY for ; Tue, 1 Apr 2014 12:22:15 -0700 (PDT) Received: from egssmtp03.att.com (egssmtp03.att.com [144.160.128.152]) by ietfa.amsl.com (Postfix) with ESMTP id 63DC31A098F for ; Tue, 1 Apr 2014 12:22:15 -0700 (PDT) Received: from mailgw1.maillennium.att.com (maillennium.att.com [135.25.114.99]) by egssmtp03.att.com ( egs 8.14.5/8.14.5) with ESMTP id s31JM9oU005438 for ; Tue, 1 Apr 2014 12:22:11 -0700 Received: from vpn-135-70-96-167.vpn.swst.att.com ([135.70.96.167]) by maillennium.att.com (mailgw1) with ESMTP id <20140401192208gw100j0cece>; Tue, 1 Apr 2014 19:22:09 +0000 X-Originating-IP: [135.70.96.167] Message-ID: <533B11E4.5070408@att.com> Date: Tue, 01 Apr 2014 15:22:12 -0400 From: Tony Hansen User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.9; rv:24.0) Gecko/20100101 Thunderbird/24.4.0 MIME-Version: 1.0 To: Henrik Levkowetz , IETF Tools Development Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit Archived-At: http://mailarchive.ietf.org/arch/msg/tools-development/0UtBVTCmXYoFhPHLHz9HywroT7Y Subject: [TOOLS-DEVELOPMENT] empty files under tools.ietf.org/html X-BeenThere: tools-development@ietf.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: Tools Development list server List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 01 Apr 2014 19:22:17 -0000 I noticed this when I tried to look at a recent RFC, RFC 7190. The file that I got via rsync tools.ietf.org/html/rfc7190.html is 0 length. Looking further, there a whole bunch of files under that directory that are 0 length. Tony From nobody Wed Apr 2 15:26:40 2014 Return-Path: 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 86B8A1A03E1 for ; Wed, 2 Apr 2014 15:26:39 -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 GqRnOnJUHHt2 for ; Wed, 2 Apr 2014 15:26:35 -0700 (PDT) Received: from nostrum.com (raven-v6.nostrum.com [IPv6:2001:470:d:1130::1]) by ietfa.amsl.com (Postfix) with ESMTP id E9BF61A0403 for ; Wed, 2 Apr 2014 15:26:31 -0700 (PDT) Received: from unnumerable.local (pool-173-71-10-88.dllstx.fios.verizon.net [173.71.10.88]) (authenticated bits=0) by nostrum.com (8.14.8/8.14.7) with ESMTP id s32MQRT5093210 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES128-SHA bits=128 verify=OK) for ; Wed, 2 Apr 2014 17:26:27 -0500 (CDT) (envelope-from rjsparks@nostrum.com) X-Authentication-Warning: raven.nostrum.com: Host pool-173-71-10-88.dllstx.fios.verizon.net [173.71.10.88] claimed to be unnumerable.local Message-ID: <533C8E92.3040805@nostrum.com> Date: Wed, 02 Apr 2014 17:26:26 -0500 From: Robert Sparks User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.9; rv:24.0) Gecko/20100101 Thunderbird/24.4.0 MIME-Version: 1.0 To: IETF Tools Development References: <533C8A8E.3050507@nostrum.com> In-Reply-To: <533C8A8E.3050507@nostrum.com> X-Forwarded-Message-Id: <533C8A8E.3050507@nostrum.com> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Archived-At: http://mailarchive.ietf.org/arch/msg/tools-development/ALrn9BDzJyFXrgJitfV81R90wOg Subject: [TOOLS-DEVELOPMENT] Community tracker utilization X-BeenThere: tools-development@ietf.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: Tools Development list server List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 02 Apr 2014 22:26:39 -0000 Ray asked me recently whether the community tracker (the extension that lets you create a personal list of drafts and subscribe to changes, etc.) is getting used. It's hard to get a solid view, but here are some stats that should help. 261 people have added documents manually to their list. 81 people have set up rules that add documents to their list. Accesses to datatracker URLs under datatracker.ietf.org/community have been averaging around 316 hits per day this week (and only two of those seem to be from bots). So, the personal list part is getting used. The WG list part is harder to get statistics on. 29 Groups have added rules. None have added individual drafts, but tickets like suggest it's hard to do so. Is there anything we need to do to make this subsection of the tracker even more useful and used? RjS From nobody Fri Apr 4 10:21:14 2014 Return-Path: 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 3EE091A020A for ; Fri, 4 Apr 2014 10:21:11 -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 lUJlwo5oHVZc for ; Fri, 4 Apr 2014 10:21:06 -0700 (PDT) Received: from odin.smetech.net (mail.smetech.net [209.135.209.4]) by ietfa.amsl.com (Postfix) with ESMTP id 9CF301A0211 for ; Fri, 4 Apr 2014 10:21:06 -0700 (PDT) Received: from localhost (unknown [209.135.209.5]) by odin.smetech.net (Postfix) with ESMTP id 0CA2FF3C005 for ; Fri, 4 Apr 2014 13:20:52 -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 8EBF0z+0PwJj for ; Fri, 4 Apr 2014 13:20:31 -0400 (EDT) Received: from [192.168.2.100] (pool-96-241-160-129.washdc.fios.verizon.net [96.241.160.129]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (No client certificate requested) by odin.smetech.net (Postfix) with ESMTP id 49E36F2C071 for ; Fri, 4 Apr 2014 13:20:31 -0400 (EDT) From: Russ Housley Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: quoted-printable Date: Fri, 4 Apr 2014 13:20:20 -0400 Message-Id: <58B26FB1-F4CF-41BD-A5FB-61C154F5AA4E@vigilsec.com> To: IETF Tools Development Mime-Version: 1.0 (Apple Message framework v1085) X-Mailer: Apple Mail (2.1085) Archived-At: http://mailarchive.ietf.org/arch/msg/tools-development/E-6T-snjgzrNx9PtF9VmMo7X7Tg Subject: [TOOLS-DEVELOPMENT] DRAFT Agenda for Tools Call X-BeenThere: tools-development@ietf.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: Tools Development list server List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 04 Apr 2014 17:21:11 -0000 Please review and comment. The IESG is planning to make greater use of wikis. Last Thursday, the = IESG decided to encourage each directorate to use a wiki. Given this = greater dependence on wikis, I have moved the transition of wikis from = tools.ietf.org to ietf.org out of the parking lot. Russ =3D =3D =3D =3D =3D =3D =3D =3D =3D=20 Tools Call Agenda -- 15 April 2014 at 13:00 Eastern 1. Datatracker Projects - Expected Datatracker Releases -- Robert and Henrik - Agenda Scheduling Development -- Robert - Agenda Display -- Robert - Improved test environment -- Henrik - IPR Tool improvements -- Robert - Liaison Tool improvements -- Robert - Transition to Django authorization model -- Robert - Sandbox Datatracker for WG chairs -- Robert 2. Community & Other Projects - Pre-MHonArc Messages from mbox files for Mail Search & Archive Tool = -- AMS - IETF Website Makeover 3. RFC Services Projects - xml2rfc bug fixes -- Alice and Henrik - RSE Design Team -- Heather 4. Transition of Mission Critical Tools - Moving mail aliases to ietf.org and link them to datatracker = database - Moving issue trackers and wikis for IETF WGs on ietf.org 5. Server Infrastructure - Automatic failover from Sunnyvale to Orlando -- AMS - Support from a Content Distribution Network -- AMS 6. Parking Lot - Currently empty =20 7. AOB From nobody Fri Apr 4 11:41:03 2014 Return-Path: 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 8522D1A0231 for ; Fri, 4 Apr 2014 11:40:58 -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 DOMcvlr0QC5q for ; Fri, 4 Apr 2014 11:40:53 -0700 (PDT) Received: from grenache.tools.ietf.org (grenache.tools.ietf.org [IPv6:2a01:3f0:1:2::30]) by ietfa.amsl.com (Postfix) with ESMTP id 9681E1A022B for ; Fri, 4 Apr 2014 11:40:53 -0700 (PDT) Received: from h25n7-s-oev-a31.ias.bredband.telia.com ([81.229.146.25]:58759 helo=vigonier.tools.ietf.org) by grenache.tools.ietf.org with esmtpsa (TLS1.0:DHE_RSA_AES_128_CBC_SHA1:128) (Exim 4.80) (envelope-from ) id 1WW92X-0000g7-6U; Fri, 04 Apr 2014 20:40:48 +0200 Message-ID: <533EFC9B.1050608@levkowetz.com> Date: Fri, 04 Apr 2014 20:40:27 +0200 From: Henrik Levkowetz User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.9; rv:24.0) Gecko/20100101 Thunderbird/24.4.0 MIME-Version: 1.0 To: Russ Housley , IETF Tools Development References: <58B26FB1-F4CF-41BD-A5FB-61C154F5AA4E@vigilsec.com> In-Reply-To: <58B26FB1-F4CF-41BD-A5FB-61C154F5AA4E@vigilsec.com> X-Enigmail-Version: 1.6 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit X-SA-Exim-Connect-IP: 81.229.146.25 X-SA-Exim-Rcpt-To: housley@vigilsec.com, tools-development@ietf.org 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 grenache.tools.ietf.org) Archived-At: http://mailarchive.ietf.org/arch/msg/tools-development/tnao7cyjRYrREdC87r2erBCuHpU Subject: Re: [TOOLS-DEVELOPMENT] DRAFT Agenda for Tools Call X-BeenThere: tools-development@ietf.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: Tools Development list server List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 04 Apr 2014 18:40:58 -0000 On 2014-04-04 19:20 Russ Housley said the following: > Please review and comment. > > The IESG is planning to make greater use of wikis. Last Thursday, the > IESG decided to encourage each directorate to use a wiki. Given this > greater dependence on wikis, I have moved the transition of wikis > from tools.ietf.org to ietf.org out of the parking lot. Makes sense. And I think we can take a first step for non-wg wikis without diving into all the scripts that tie into the WG wikis. No particular comments on the agenda, otherwise. Henrik > > Russ > > = = = = = = = = = > > Tools Call Agenda -- 15 April 2014 at 13:00 Eastern > > 1. Datatracker Projects > - Expected Datatracker Releases -- Robert and Henrik > - Agenda Scheduling Development -- Robert > - Agenda Display -- Robert > - Improved test environment -- Henrik > - IPR Tool improvements -- Robert > - Liaison Tool improvements -- Robert > - Transition to Django authorization model -- Robert > - Sandbox Datatracker for WG chairs -- Robert > > 2. Community & Other Projects > - Pre-MHonArc Messages from mbox files for Mail Search & Archive Tool -- AMS > - IETF Website Makeover > > 3. RFC Services Projects > - xml2rfc bug fixes -- Alice and Henrik > - RSE Design Team -- Heather > > 4. Transition of Mission Critical Tools > - Moving mail aliases to ietf.org and link them to datatracker database > - Moving issue trackers and wikis for IETF WGs on ietf.org > > 5. Server Infrastructure > - Automatic failover from Sunnyvale to Orlando -- AMS > - Support from a Content Distribution Network -- AMS > > 6. Parking Lot > - Currently empty > > 7. AOB > > _______________________________________________ > TOOLS-DEVELOPMENT mailing list > TOOLS-DEVELOPMENT@ietf.org > https://www.ietf.org/mailman/listinfo/tools-development > From nobody Wed Apr 9 07:58:45 2014 Return-Path: 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 7870A1A028F for ; Wed, 9 Apr 2014 07:58:40 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -101.892 X-Spam-Level: X-Spam-Status: No, score=-101.892 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_NONE=-0.0001, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001, T_FILL_THIS_FORM_SHORT=0.01, 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 o9DL10NAo7ve for ; Wed, 9 Apr 2014 07:58:35 -0700 (PDT) Received: from na01-bn1-obe.outbound.protection.outlook.com (mail-bn1lp0145.outbound.protection.outlook.com [207.46.163.145]) by ietfa.amsl.com (Postfix) with ESMTP id 08B771A0260 for ; Wed, 9 Apr 2014 07:58:35 -0700 (PDT) Received: from [192.168.0.34] (69.131.53.57) by CO1PR06MB238.namprd06.prod.outlook.com (10.242.166.144) with Microsoft SMTP Server (TLS) id 15.0.918.8; Wed, 9 Apr 2014 14:58:33 +0000 From: Ray Pelletier Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable Message-ID: <2352EE8D-D566-4679-8D28-118E6618302D@isoc.org> Date: Wed, 9 Apr 2014 10:58:26 -0400 To: IETF Tools Development MIME-Version: 1.0 (Mac OS X Mail 7.2 \(1874\)) X-Mailer: Apple Mail (2.1874) X-Originating-IP: [69.131.53.57] X-ClientProxiedBy: BLUPR01CA020.prod.exchangelabs.com (10.141.30.50) To CO1PR06MB238.namprd06.prod.outlook.com (10.242.166.144) X-Forefront-PRVS: 01762B0D64 X-Forefront-Antispam-Report: =?us-ascii?Q?SFV:NSPM; SFS:(10019001)(6049001)(6009001)(428001)(189002)(15?= =?us-ascii?Q?594002)(243025003)(199002)(377454003)(53806002)(47736002)(50?= =?us-ascii?Q?986002)(47446003)(59766002)(65816002)(56816006)(56776002)(47?= =?us-ascii?Q?976003)(63696004)(54316003)(92566001)(95666003)(97186001)(97?= =?us-ascii?Q?336001)(97756001)(92726001)(87286001)(83716003)(95416001)(94?= =?us-ascii?Q?316002)(88136002)(87266001)(94946001)(87976001)(15975445006)?= =?us-ascii?Q?(85306002)(90146001)(89996001)(81816001)(81686001)(82746002)?= =?us-ascii?Q?(85852003)(83072002)(93136001)(86362001)(93916002)(575784001?= =?us-ascii?Q?)(93516002)(46102001)(76176001)(76786001)(76796001)(77982001?= =?us-ascii?Q?)(36756003)(15202345003)(77156001)(77096001)(33656001)(16601?= =?us-ascii?Q?075003)(66066001)(69226001)(76482001)(74876001)(79102001)(47?= =?us-ascii?Q?776003)(20776003)(80022001)(74706001)(42186004)(16799955002)?= =?us-ascii?Q?(50466002)(19273905006)(57306001)(74366001)(23726002)(813420?= =?us-ascii?Q?01)(98676001)(74502001)(83322001)(99396002)(80976001)(195804?= =?us-ascii?Q?05001)(74662001)(62966002)(19580395003)(81542001)(49866001)(?= =?us-ascii?Q?31966008)(4396001)(50226001)(551544002)(46406003)(563064011)?= =?us-ascii?Q?;DIR:OUT;SFP:1102;SCL:1;SRVR:CO1PR06MB238;H:[192.168.0.34];F?= =?us-ascii?Q?PR:3C9F55EF.98269F22.B8C79233.84E8D9FD.2037E;MLV:sfv;PTR:Inf?= =?us-ascii?Q?oNoRecords;MX:1;A:1;LANG:en;?= Received-SPF: None (: isoc.org does not designate permitted sender hosts) X-OriginatorOrg: isoc.org Archived-At: http://mailarchive.ietf.org/arch/msg/tools-development/1NMke6nZUajzEYaBLfekBkvQP2o Subject: [TOOLS-DEVELOPMENT] Tools Call Tuesday 15 April at 1:00 PM EDT: WebEx Details X-BeenThere: tools-development@ietf.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: Tools Development list server List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 09 Apr 2014 14:58:40 -0000 All; Here are the WebEx details for our call next week. =20 An Agenda will be sent out separately. Ray Topic: Tools Cmte=20 Date: Tuesday, April 15, 2014=20 Time: 1:00 pm, Eastern Daylight Time (New York, GMT-04:00)=20 Meeting Number: 967 883 620=20 Meeting Password: Tools=20 -------------------------------------------------------=20 To join the online meeting (Now from mobile devices!)=20 -------------------------------------------------------=20 1. Go to = https://workgreen.webex.com/workgreen/j.php?MTID=3Dmad0452eb93ee939c6b5d53= fee9364496=20 2. If requested, enter your name and email address.=20 3. If a password is required, enter the meeting password: Tools=20 4. Click "Join".=20 To view in other time zones or languages, please click the link:=20 = https://workgreen.webex.com/workgreen/j.php?MTID=3Dm61d170576856bd429b77f3= feed009b29=20 -------------------------------------------------------=20 To join the audio conference only=20 -------------------------------------------------------=20 To receive a call back, provide your phone number when you join the = meeting, or call the number below and enter the access code.=20 Call-in toll-free number (US/Canada): 1-877-668-4490=20 Call-in toll number (US/Canada): 1-408-792-6300=20 Global call-in numbers: = https://workgreen.webex.com/workgreen/globalcallin.php?serviceType=3DMC&ED= =3D272001492&tollFree=3D1=20 Toll-free dialing restrictions: = http://www.webex.com/pdf/tollfree_restrictions.pdf=20 Access code:967 883 620=20 -------------------------------------------------------=20 For assistance=20 -------------------------------------------------------=20 1. Go to https://workgreen.webex.com/workgreen/mc=20 2. On the left navigation bar, click "Support".=20 You can contact me at:=20 rpelletier@isoc.org=20 1-703-652-9534=20 To update this meeting to your calendar program (for example Microsoft = Outlook), click this link:=20 = https://workgreen.webex.com/workgreen/j.php?MTID=3Dma0d901f75ac867163126a2= eed38e32f9=20 WebEx will automatically setup Meeting Manager for Windows the first = time you join a meeting. To save time, you can setup prior to the = meeting by clicking this link:=20 https://workgreen.webex.com/workgreen/meetingcenter/mcsetup.php=20 The playback of UCF (Universal Communications Format) rich media files = requires appropriate players. To view this type of rich media files in = the meeting, please check whether you have the players installed on your = computer by going to = https://workgreen.webex.com/workgreen/systemdiagnosis.php.=20 Sign up for a free trial of WebEx=20 http://www.webex.com/go/mcemfreetrial=20 http://www.webex.com=20 CCP:+14087926300x967883620#=20 IMPORTANT NOTICE: This WebEx service includes a feature that allows = audio and any documents and other materials exchanged or viewed during = the session to be recorded. By joining this session, you automatically = consent to such recordings. If you do not consent to the recording, = discuss your concerns with the meeting host prior to the start of the = recording or do not join the session. Please note that any such = recordings may be subject to discovery in the event of litigation.= From nobody Thu Apr 10 08:35:15 2014 Return-Path: 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 A3ED81A0281 for ; Thu, 10 Apr 2014 08:35:11 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -99.2 X-Spam-Level: X-Spam-Status: No, score=-99.2 tagged_above=-999 required=5 tests=[BAYES_50=0.8, 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 7HBKHMJu2doa for ; Thu, 10 Apr 2014 08:35:10 -0700 (PDT) Received: from odin.smetech.net (mail.smetech.net [209.135.209.4]) by ietfa.amsl.com (Postfix) with ESMTP id 56ABF1A027C for ; Thu, 10 Apr 2014 08:35:10 -0700 (PDT) Received: from localhost (unknown [209.135.209.5]) by odin.smetech.net (Postfix) with ESMTP id 67457F3C009 for ; Thu, 10 Apr 2014 11:34:59 -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 WWnFsGYU2B5O for ; Thu, 10 Apr 2014 11:34:38 -0400 (EDT) Received: from [192.168.2.100] (pool-96-241-160-129.washdc.fios.verizon.net [96.241.160.129]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (No client certificate requested) by odin.smetech.net (Postfix) with ESMTP id 558F9F2C077 for ; Thu, 10 Apr 2014 11:34:38 -0400 (EDT) Content-Type: text/plain; charset=us-ascii Mime-Version: 1.0 (Apple Message framework v1085) From: Russ Housley In-Reply-To: <58B26FB1-F4CF-41BD-A5FB-61C154F5AA4E@vigilsec.com> Date: Thu, 10 Apr 2014 11:34:23 -0400 Content-Transfer-Encoding: quoted-printable Message-Id: <6FE01668-7A6E-44C0-B304-FE12CED2DAB0@vigilsec.com> References: <58B26FB1-F4CF-41BD-A5FB-61C154F5AA4E@vigilsec.com> To: IETF Tools Development X-Mailer: Apple Mail (2.1085) Archived-At: http://mailarchive.ietf.org/arch/msg/tools-development/ZWnPx9dG9dpOerjbOmkQP0YXLoA Subject: [TOOLS-DEVELOPMENT] Agenda for Tools Call on 15 April 2014 X-BeenThere: tools-development@ietf.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: Tools Development list server List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 10 Apr 2014 15:35:11 -0000 Tools Call Agenda -- 15 April 2014 at 13:00 Eastern 1. Datatracker Projects - Expected Datatracker Releases -- Robert and Henrik - Agenda Scheduling Development -- Robert - Agenda Display -- Robert - Improved test environment -- Henrik - IPR Tool improvements -- Robert - Liaison Tool improvements -- Robert - Transition to Django authorization model -- Robert - Sandbox Datatracker for WG chairs -- Robert 2. Community & Other Projects - Pre-MHonArc Messages from mbox files for Mail Search & Archive Tool = -- AMS - Present a directory view of active, archived, and unknown I-Ds = -- AMS - IETF Website Makeover 3. RFC Services Projects - xml2rfc bug fixes -- Alice and Henrik - RSE Design Team -- Heather 4. Transition of Mission Critical Tools - Moving mail aliases to ietf.org and link them to datatracker = database - Moving issue trackers and wikis for IETF WGs on ietf.org 5. Server Infrastructure - Automatic failover from Sunnyvale to Orlando -- AMS - Support from a Content Distribution Network -- AMS 6. Parking Lot - IMAP access to the email archives =20 7. AOB From nobody Thu Apr 10 09:35:41 2014 Return-Path: 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 3DD751A032B for ; Thu, 10 Apr 2014 09:35:40 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -102.592 X-Spam-Level: X-Spam-Status: No, score=-102.592 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_LOW=-0.7, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001, T_FILL_THIS_FORM_SHORT=0.01, 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 zYMYK2sZrHeO for ; Thu, 10 Apr 2014 09:35:33 -0700 (PDT) Received: from na01-by2-obe.outbound.protection.outlook.com (mail-by2lp0237.outbound.protection.outlook.com [207.46.163.237]) by ietfa.amsl.com (Postfix) with ESMTP id B9C1B1A0299 for ; Thu, 10 Apr 2014 09:35:33 -0700 (PDT) Received: from [192.168.0.34] (69.131.53.57) by CO1PR06MB239.namprd06.prod.outlook.com (10.242.166.146) with Microsoft SMTP Server (TLS) id 15.0.918.8; Thu, 10 Apr 2014 16:35:31 +0000 Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 (Mac OS X Mail 7.2 \(1874\)) From: Ray Pelletier In-Reply-To: <6FE01668-7A6E-44C0-B304-FE12CED2DAB0@vigilsec.com> Date: Thu, 10 Apr 2014 12:35:21 -0400 Content-Transfer-Encoding: quoted-printable Message-ID: <6A32277D-E147-4E4E-A04E-7EA2ADBA4FA5@isoc.org> References: <58B26FB1-F4CF-41BD-A5FB-61C154F5AA4E@vigilsec.com> <6FE01668-7A6E-44C0-B304-FE12CED2DAB0@vigilsec.com> To: Russ Housley X-Mailer: Apple Mail (2.1874) X-Originating-IP: [69.131.53.57] X-ClientProxiedBy: BLUPR01CA013.prod.exchangelabs.com (10.141.30.43) To CO1PR06MB239.namprd06.prod.outlook.com (10.242.166.146) X-Forefront-PRVS: 0177904E6B X-Forefront-Antispam-Report: SFV:NSPM; SFS:(10019001)(6009001)(6049001)(428001)(24454002)(199002)(189002)(51704005)(15594002)(377454003)(243025003)(4396001)(76176999)(50226001)(81342001)(50986999)(76482001)(66066001)(97756001)(80022001)(33656001)(16601075003)(42186004)(19580405001)(77982001)(19580395003)(79102001)(83322001)(31966008)(74502001)(36756003)(74662001)(46102001)(19273905006)(16799955002)(83716003)(57306001)(81542001)(99396002)(46406003)(80976001)(50466002)(15202345003)(20776003)(47776003)(92566001)(87976001)(23726002)(92726001)(85852003)(551544002)(77156001)(62966002)(93916002)(89996001)(82746002)(88136002)(86362001)(575784001)(83072002)(15975445006)(87286001)(563064011); DIR:OUT; SFP:1102; SCL:1; SRVR:CO1PR06MB239; H:[192.168.0.34]; FPR:3C9F71EF.98E69CC2.B8C79EB3.84E8D98D.204C7; MLV:sfv; PTR:InfoNoRecords; A:1; MX:1; LANG:en; Received-SPF: None (: isoc.org does not designate permitted sender hosts) X-OriginatorOrg: isoc.org Archived-At: http://mailarchive.ietf.org/arch/msg/tools-development/oY5B3Pfk3CHbeWSI8lnV4FWIY24 Cc: IETF Tools Development Subject: [TOOLS-DEVELOPMENT] WebEx Details was Re: Agenda for Tools Call on 15 April 2014 X-BeenThere: tools-development@ietf.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: Tools Development list server List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 10 Apr 2014 16:35:40 -0000 Topic: Tools Cmte=20 Date: Tuesday, April 15, 2014=20 Time: 1:00 pm, Eastern Daylight Time (New York, GMT-04:00)=20 Meeting Number: 967 883 620=20 Meeting Password: Tools=20 -------------------------------------------------------=20 To join the online meeting (Now from mobile devices!)=20 -------------------------------------------------------=20 1. Go to = https://workgreen.webex.com/workgreen/j.php?MTID=3Dmad0452eb93ee939c6b5d53= fee9364496=20 2. If requested, enter your name and email address.=20 3. If a password is required, enter the meeting password: Tools=20 4. Click "Join".=20 To view in other time zones or languages, please click the link:=20 = https://workgreen.webex.com/workgreen/j.php?MTID=3Dm61d170576856bd429b77f3= feed009b29=20 -------------------------------------------------------=20 To join the audio conference only=20 -------------------------------------------------------=20 To receive a call back, provide your phone number when you join the = meeting, or call the number below and enter the access code.=20 Call-in toll-free number (US/Canada): 1-877-668-4490=20 Call-in toll number (US/Canada): 1-408-792-6300=20 Global call-in numbers: = https://workgreen.webex.com/workgreen/globalcallin.php?serviceType=3DMC&ED= =3D272001492&tollFree=3D1=20 Toll-free dialing restrictions: = http://www.webex.com/pdf/tollfree_restrictions.pdf=20 Access code:967 883 620=20 -------------------------------------------------------=20 For assistance=20 -------------------------------------------------------=20 1. Go to https://workgreen.webex.com/workgreen/mc=20 2. On the left navigation bar, click "Support".=20 You can contact me at:=20 rpelletier@isoc.org=20 1-703-652-9534=20 To update this meeting to your calendar program (for example Microsoft = Outlook), click this link:=20 = https://workgreen.webex.com/workgreen/j.php?MTID=3Dma0d901f75ac867163126a2= eed38e32f9=20 WebEx will automatically setup Meeting Manager for Windows the first = time you join a meeting. To save time, you can setup prior to the = meeting by clicking this link:=20 https://workgreen.webex.com/workgreen/meetingcenter/mcsetup.php=20 The playback of UCF (Universal Communications Format) rich media files = requires appropriate players. To view this type of rich media files in = the meeting, please check whether you have the players installed on your = computer by going to = https://workgreen.webex.com/workgreen/systemdiagnosis.php.=20 Sign up for a free trial of WebEx=20 http://www.webex.com/go/mcemfreetrial=20 http://www.webex.com=20 CCP:+14087926300x967883620#=20 IMPORTANT NOTICE: This WebEx service includes a feature that allows = audio and any documents and other materials exchanged or viewed during = the session to be recorded. By joining this session, you automatically = consent to such recordings. If you do not consent to the recording, = discuss your concerns with the meeting host prior to the start of the = recording or do not join the session. Please note that any such = recordings may be subject to discovery in the event of litigation. On Apr 10, 2014, at 11:34 AM, Russ Housley wrote: > Tools Call Agenda -- 15 April 2014 at 13:00 Eastern >=20 > 1. Datatracker Projects > - Expected Datatracker Releases -- Robert and Henrik > - Agenda Scheduling Development -- Robert > - Agenda Display -- Robert > - Improved test environment -- Henrik > - IPR Tool improvements -- Robert > - Liaison Tool improvements -- Robert > - Transition to Django authorization model -- Robert > - Sandbox Datatracker for WG chairs -- Robert >=20 > 2. Community & Other Projects > - Pre-MHonArc Messages from mbox files for Mail Search & Archive = Tool -- AMS > - Present a directory view of active, archived, and unknown I-Ds = -- AMS > - IETF Website Makeover >=20 > 3. RFC Services Projects > - xml2rfc bug fixes -- Alice and Henrik > - RSE Design Team -- Heather >=20 > 4. Transition of Mission Critical Tools > - Moving mail aliases to ietf.org and link them to datatracker = database > - Moving issue trackers and wikis for IETF WGs on ietf.org >=20 > 5. Server Infrastructure > - Automatic failover from Sunnyvale to Orlando -- AMS > - Support from a Content Distribution Network -- AMS >=20 > 6. Parking Lot > - IMAP access to the email archives >=20 > 7. AOB >=20 > _______________________________________________ > TOOLS-DEVELOPMENT mailing list > TOOLS-DEVELOPMENT@ietf.org > https://www.ietf.org/mailman/listinfo/tools-development From nobody Sun Apr 13 09:27:07 2014 Return-Path: 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 F204D1A06F4 for ; Tue, 1 Apr 2014 07:55:33 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -2 X-Spam-Level: X-Spam-Status: No, score=-2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, 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 mLRMaVXuRnOk for ; Tue, 1 Apr 2014 07:55:32 -0700 (PDT) Received: from mail-yk0-x22e.google.com (mail-yk0-x22e.google.com [IPv6:2607:f8b0:4002:c07::22e]) by ietfa.amsl.com (Postfix) with ESMTP id 899B91A06DC for ; Tue, 1 Apr 2014 07:55:32 -0700 (PDT) Received: by mail-yk0-f174.google.com with SMTP id 20so7584257yks.33 for ; Tue, 01 Apr 2014 07:55:29 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:date:message-id:subject:from:to:content-type; bh=BIETtlusz36CEas582vBU9baHj42aTgGOVxXZuMW69s=; b=Knb6XaeoT+8jg26JNMJp/CqXdqQ0DDIHF0Dx/C0fe5HCp+RMhRKD85XK91jtRII7aD OI7voFrN9Z+/tG1CGdnuDgr+k0RONVw4iIZub4M1+4ewGaS7h3LgWU4mNVdSjo8Phc9T NsWcUtnIflwPY+BjkEZiYeEwkXux5M4fQz8iuogZzzMCr8XN4tkEdXu7DHQJr/85GX26 a+2yDMDpuAhZc5+t8O18XO8rESJODZdwK10SOxgn5EhK9mt4MN9pDdCXfVs0uGBivjcL dR0FNWBvlAU27gSmEbaguFC2BW+YzEL3YEoZmOXmmu3XHgSAUFhNKtFxnGBYfCkQwsYx YYCg== MIME-Version: 1.0 X-Received: by 10.236.120.66 with SMTP id o42mr46462306yhh.66.1396364128877; Tue, 01 Apr 2014 07:55:28 -0700 (PDT) Received: by 10.170.63.197 with HTTP; Tue, 1 Apr 2014 07:55:28 -0700 (PDT) Date: Tue, 1 Apr 2014 07:55:28 -0700 Message-ID: From: Watson Ladd To: tools-development@ietf.org Content-Type: text/plain; charset=UTF-8 Archived-At: http://mailarchive.ietf.org/arch/msg/tools-development/PnqSMlPJxbvry4d0_Jb2a0NLgj8 X-Mailman-Approved-At: Sun, 13 Apr 2014 09:27:02 -0700 Subject: [TOOLS-DEVELOPMENT] Searching mailing lists X-BeenThere: tools-development@ietf.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: Tools Development list server List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 01 Apr 2014 14:55:34 -0000 To whom it may concern, I am a newcommer to the IETF and am participating in WGs where searching the mailing list is important. This is a bit painful for several reasons. Firstly, searching chronologically is hard because there is no date index. Secondly there doesn't appear a way to go from the archive page to a fulltext search of only that archive. Sincerely, Watson Ladd From nobody Mon Apr 14 08:42:23 2014 Return-Path: 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 DF67C1A0515 for ; Mon, 14 Apr 2014 08:42:16 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: 0.528 X-Spam-Level: X-Spam-Status: No, score=0.528 tagged_above=-999 required=5 tests=[BAYES_50=0.8, RP_MATCHES_RCVD=-0.272] 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 mfupEBRPPU82 for ; Mon, 14 Apr 2014 08:42:15 -0700 (PDT) Received: from nostrum.com (raven-v6.nostrum.com [IPv6:2001:470:d:1130::1]) by ietfa.amsl.com (Postfix) with ESMTP id E90FA1A04E9 for ; Mon, 14 Apr 2014 08:42:13 -0700 (PDT) Received: from unnumerable.local (pool-173-71-50-89.dllstx.fios.verizon.net [173.71.50.89]) (authenticated bits=0) by nostrum.com (8.14.8/8.14.7) with ESMTP id s3EFg9fC079794 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES128-SHA bits=128 verify=OK) for ; Mon, 14 Apr 2014 10:42:10 -0500 (CDT) (envelope-from rjsparks@nostrum.com) X-Authentication-Warning: raven.nostrum.com: Host pool-173-71-50-89.dllstx.fios.verizon.net [173.71.50.89] claimed to be unnumerable.local Message-ID: <534C01D0.8030606@nostrum.com> Date: Mon, 14 Apr 2014 10:42:08 -0500 From: Robert Sparks User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.9; rv:24.0) Gecko/20100101 Thunderbird/24.4.0 MIME-Version: 1.0 To: tools-development@ietf.org References: <58B26FB1-F4CF-41BD-A5FB-61C154F5AA4E@vigilsec.com> <6FE01668-7A6E-44C0-B304-FE12CED2DAB0@vigilsec.com> In-Reply-To: <6FE01668-7A6E-44C0-B304-FE12CED2DAB0@vigilsec.com> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Archived-At: http://mailarchive.ietf.org/arch/msg/tools-development/F_MM5hyyG2LsZ43oVnMy2KY1nC8 Subject: Re: [TOOLS-DEVELOPMENT] Agenda for Tools Call on 15 April 2014 X-BeenThere: tools-development@ietf.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: Tools Development list server List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 14 Apr 2014 15:42:17 -0000 To try to help keep the call within it's allotted length, here's a summary for several items. Please skim before we get to the meeting. On 4/10/14, 10:34 AM, Russ Housley wrote: > Tools Call Agenda -- 15 April 2014 at 13:00 Eastern > > 1. Datatracker Projects > - Expected Datatracker Releases -- Robert and Henrik The imminent releases in the queue are: * Agenda fixes * IRTF RG Functionality * Schema changes (ScheduledSession rename, expanding slug length limits to 16 chars, allowing Consensus DocEvents to return to "Unknown") The other known upcoming releases are documented at Recently completed releases can be seen at > - Agenda Scheduling Development -- Robert The primary (and extensive) round of fixes are ready and next in the merge queue. See Stephanie and I will go through an end-to-end simulation of setting up the schedule for IETF90 tomorrow. > - Agenda Display -- Robert I have been gathering a list of the places that need to be fixed still (there aren't many). Work on fixing them will start after the primary agenda fixes release. > - Improved test environment -- Henrik > - IPR Tool improvements -- Robert Bids are due today. > - Liaison Tool improvements -- Robert RFB sent - questions due Apr 21. > - Transition to Django authorization model -- Robert Deployed today. > - Sandbox Datatracker for WG chairs -- Robert Nothing done (at least by me). Will work with Alexa before the next tools call to build out a plan for having a sandbox during the Sunday chair training session at IETF 90. > > 2. Community & Other Projects > - Pre-MHonArc Messages from mbox files for Mail Search & Archive Tool -- AMS The reload is expected to happen over the next weekend. > - Present a directory view of active, archived, and unknown I-Ds -- AMS > - IETF Website Makeover The design team is working on incorporating the community comments. We have a call tomorrow before this team's call. I'll provide a readout of that call when we talk. One thing I expect we will need discuss is this current text: "Key milestones and deliverables during the redesign process (e.g. site architecture, technology, wireframes, page design, content updates) should be identified in the proposal. These items will be reviewed and approved by a committee identified by the IETF." What does "identified by the IETF." mean practically? > > 3. RFC Services Projects > - xml2rfc bug fixes -- Alice and Henrik > - RSE Design Team -- Heather > > 4. Transition of Mission Critical Tools > - Moving mail aliases to ietf.org and link them to datatracker database > - Moving issue trackers and wikis for IETF WGs on ietf.org > > 5. Server Infrastructure > - Automatic failover from Sunnyvale to Orlando -- AMS > - Support from a Content Distribution Network -- AMS > > 6. Parking Lot > - IMAP access to the email archives > > 7. AOB The mentoring program is ready for some lightweight tooling to assist with gathering mentor requests and doing matching. > > _______________________________________________ > TOOLS-DEVELOPMENT mailing list > TOOLS-DEVELOPMENT@ietf.org > https://www.ietf.org/mailman/listinfo/tools-development From nobody Tue Apr 15 09:50:29 2014 Return-Path: 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 8B4971A0499 for ; Tue, 15 Apr 2014 09:50:25 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: 0.528 X-Spam-Level: X-Spam-Status: No, score=0.528 tagged_above=-999 required=5 tests=[BAYES_50=0.8, RP_MATCHES_RCVD=-0.272] 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 67TTOl75kFLG for ; Tue, 15 Apr 2014 09:50:23 -0700 (PDT) Received: from nostrum.com (raven-v6.nostrum.com [IPv6:2001:470:d:1130::1]) by ietfa.amsl.com (Postfix) with ESMTP id B5F491A01CB for ; Tue, 15 Apr 2014 09:50:23 -0700 (PDT) Received: from unnumerable.local (pool-173-57-107-66.dllstx.fios.verizon.net [173.57.107.66]) (authenticated bits=0) by nostrum.com (8.14.8/8.14.7) with ESMTP id s3FGoJQg048211 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES128-SHA bits=128 verify=OK) for ; Tue, 15 Apr 2014 11:50:20 -0500 (CDT) (envelope-from rjsparks@nostrum.com) X-Authentication-Warning: raven.nostrum.com: Host pool-173-57-107-66.dllstx.fios.verizon.net [173.57.107.66] claimed to be unnumerable.local Message-ID: <534D634B.1070202@nostrum.com> Date: Tue, 15 Apr 2014 11:50:19 -0500 From: Robert Sparks User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.9; rv:24.0) Gecko/20100101 Thunderbird/24.4.0 MIME-Version: 1.0 To: IETF Tools Development Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Archived-At: http://mailarchive.ietf.org/arch/msg/tools-development/zS5TMDPxL5CTcTkbtXEKVbmNzVg Subject: [TOOLS-DEVELOPMENT] Thoughts on path forward on tools to support the new rfc format X-BeenThere: tools-development@ietf.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: Tools Development list server List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 15 Apr 2014 16:50:25 -0000 Trying to look at the horizon for a moment: When we are at the point we are producing RFCs in XML, the workflow will look like this: - Authors create content in potentially many formats, one of which might be the new XML. (The others include text, word, nroff, and any other currently accepted formats). Authors need to be able to tell, and the submission point needs to check, whether the document meets the requirements for being accepted as input into publication process. - The RFC Editor will work in the new XML format * Converting other input formats to the XML format * Refining the xml into a proposed final canonical RFC product - The proposed canonical product will be rendered into several publication formats - The authors and the RFC Editor will iterate on reviews of the proposed product. (We expect the authors will use the derived publication formats primarily for their review.) Both the authors and the rfc editor need to be able to quickly tell that the document is still acceptable for publication as they edit the proposed final result. - The end result of that editing round will be published as the RFC (a frozen canonical XML document), and it's derived publication formats. I think this flow would best be supported by these tools: * A tool that converts text documents that are in close-to-internet-draft form into the new XML format. We can utilize the exisiting tools that render text from the other input formats for submission to get those formats. * A tool that points out what needs to change in order for the xml document to be ready. This is likely a combination of the functionality (think in terms of functionality, not implementation for the moment) in id-nits, the first part of xml2rfc (that parses the document) and several of the standalone programs in the current production workflow, This should be usable by the rfc editor and document authors, and should be useful at any point in the development of the document, from initial version to published RFC. * One or more tools that create the derived publication formats. These also need to be available to both the rfc editor and the authors. * Diff tools to help compare versions. I think these are the steps we should take towards acquiring those tools (If you've seen Heather's email discussing threads of next steps, this is intended to incorporate them.) 1) The volunteer community (primarily Henrik and Julian if I understand correctly) will be prototyping the production of an example publication format (HTML) from a well-formed example input document in the canonical format. (A text format is likely to also fall out, but is not going to be the primary focus.) This work is expected to sanity check that the new grammar allows authors to express what we intended, and that it can be rendered as expected. Its focus won't be on solving rendering for arbitrary inputs however - they'll be concentrating on what needs to be done perform the sanity check and make the example publication format document so we can iterate with the community on those quickly. It may be that they discover that this production step is easy, and that it's essentially done when they're through, or it may be that they develop requirements for a larger effort. 2) We can start developing an SoW for the tool that would point out what needs to change. I see this as a single tool with switches to control the level of verification. It will at a minimum check for well-formed XML. It can be told to look for spelling errors and make grammar checks (such as duplicated words). It can be told to highlight where non-ascii UTF-8 is used. It _might_ also be the thing that can be told to verify any SVG satisfies our profile, and that and that other included things (like mibs or abnf) check out, but while developing the SoW we may decide to keep these as separate tools. 3) We can start developing an SoW for an xml diff tool (and continue discussing whether we really need such a thing as part of that development). 4) We can start developing an SoW for the tool that converts text documents that are in close-to-internet-draft form into the new XML format. Early results from the prototyping effort in 1) will feed into 2). Once the prototyping is fairly far along, we'll know if we need a 5) or not for specing the publication format converters. What am I missing? Does anyone think this is the wrong way to approach this? RjS From nobody Tue Apr 15 10:14:44 2014 Return-Path: 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 986311A04C8 for ; Tue, 15 Apr 2014 10:14:42 -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 uPrx7aNBk0yP for ; Tue, 15 Apr 2014 10:14:39 -0700 (PDT) Received: from grenache.tools.ietf.org (grenache.tools.ietf.org [IPv6:2a01:3f0:1:2::30]) by ietfa.amsl.com (Postfix) with ESMTP id 03A9E1A053B for ; Tue, 15 Apr 2014 10:14:38 -0700 (PDT) Received: from h25n7-s-oev-a31.ias.bredband.telia.com ([81.229.146.25]:58925 helo=vigonier.tools.ietf.org) by grenache.tools.ietf.org with esmtpsa (TLS1.0:DHE_RSA_AES_128_CBC_SHA1:128) (Exim 4.80) (envelope-from ) id 1Wa6wL-0008Mh-GP; Tue, 15 Apr 2014 19:14:34 +0200 Message-ID: <534D68F4.40404@levkowetz.com> Date: Tue, 15 Apr 2014 19:14:28 +0200 From: Henrik Levkowetz User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.9; rv:24.0) Gecko/20100101 Thunderbird/24.4.0 MIME-Version: 1.0 To: Robert Sparks , IETF Tools Development References: <534D634B.1070202@nostrum.com> In-Reply-To: <534D634B.1070202@nostrum.com> X-Enigmail-Version: 1.6 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit X-SA-Exim-Connect-IP: 81.229.146.25 X-SA-Exim-Rcpt-To: rjsparks@nostrum.com, tools-development@ietf.org 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 grenache.tools.ietf.org) Archived-At: http://mailarchive.ietf.org/arch/msg/tools-development/WxGFnNalv65_BcIUQwBVQJIJN_I Subject: Re: [TOOLS-DEVELOPMENT] Thoughts on path forward on tools to support the new rfc format X-BeenThere: tools-development@ietf.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: Tools Development list server List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 15 Apr 2014 17:14:42 -0000 Hi Robert, One point inline, and one at the end: On 2014-04-15 18:50 Robert Sparks said the following: > Trying to look at the horizon for a moment: > > When we are at the point we are producing RFCs in XML, the workflow > will look like this: > > - Authors create content in potentially many formats, one of which > might be the new XML. (The others include text, word, nroff, and > any other currently accepted formats). > Authors need to be able to tell, and the submission point needs to > check, > whether the document meets the requirements for being accepted as input > into publication process. > > - The RFC Editor will work in the new XML format > * Converting other input formats to the XML format > * Refining the xml into a proposed final canonical RFC product > > - The proposed canonical product will be rendered into several > publication formats > > - The authors and the RFC Editor will iterate on reviews of the proposed > product. (We expect the authors will use the derived publication formats > primarily for their review.) Both the authors and the rfc editor need to > be able to quickly tell that the document is still acceptable for > publication as they edit the proposed final result. > > - The end result of that editing round will be published as the RFC > (a frozen canonical XML document), and it's derived publication formats. > > > I think this flow would best be supported by these tools: > > * A tool that converts text documents that are in close-to-internet-draft > form into the new XML format. We can utilize the exisiting tools that > render text from the other input formats for submission to get those > formats. > > * A tool that points out what needs to change in order for the xml document > to be ready. This is likely a combination of the functionality (think in > terms of functionality, not implementation for the moment) in id-nits, > the first part of xml2rfc (that parses the document) and several of > the standalone programs in the current production workflow, > This should be usable by the rfc editor and document authors, and should > be useful at any point in the development of the document, from initial > version to published RFC. > > * One or more tools that create the derived publication formats. These also > need to be available to both the rfc editor and the authors. > > * Diff tools to help compare versions. > > I think these are the steps we should take towards acquiring those tools > (If you've seen Heather's email discussing threads of next steps, this > is intended to incorporate them.) > > 1) The volunteer community (primarily Henrik and Julian if I understand > correctly) will be prototyping the production of an example publication > format (HTML) from a well-formed example input document in the canonical > format. (A text format is likely to also fall out, but is not going > to be the primary focus.) This doesn't match my understanding -- needs discussion. I think Julian was looking explicitly at extending xml2rfc's text mode, as that's what gets used most. > This work is expected to sanity check that > the new grammar allows authors to express what we intended, and that > it can be rendered as expected. Its focus > won't be on solving rendering for arbitrary inputs however - they'll be > concentrating on what needs to be done perform the sanity check and make > the example publication format document so we can iterate with the > community on those quickly. It may be that they discover that this > production step is easy, and that it's essentially done when they're > through, or it may be that they develop requirements for a larger > effort. > > 2) We can start developing an SoW for the tool that would point out > what needs to change. I see this as a single tool with switches > to control the level of verification. It will at a minimum check > for well-formed XML. It can be told to look for spelling errors and > make grammar checks (such as duplicated words). It can be told to > highlight where non-ascii UTF-8 is used. It _might_ also be the thing > that can be told to verify any SVG satisfies our profile, and that > and that other included things (like mibs or abnf) check out, but > while developing the SoW we may decide to keep these as separate > tools. > > 3) We can start developing an SoW for an xml diff tool (and continue > discussing whether we really need such a thing as part of that > development). > > 4) We can start developing an SoW for the tool that converts text > documents that are in close-to-internet-draft form into the > new XML format. > > Early results from the prototyping effort in 1) will feed into 2). > Once the prototyping is fairly far along, we'll know if we need a > 5) or not for specing the publication format converters. >From the viewpoint of xml2rfc, it currently can produce 3 of the 5 reading formats (paginated and unpaginated text, and html) but neither pdf or epub is handled at all, and will be a substantial effort. I think we can safely say that we'll need a step 5) for that. > > What am I missing? Does anyone think this is the wrong way to > approach this? Seems fairly good overall. I'm a bit concerned about the approach to things like spell checking is to build it into a custom tool, instead of using something like aspell in html mode. Custom tools always cost more in maintenance than an off-the-shelf tool. Best regards, Henrik From nobody Tue Apr 15 11:52:37 2014 Return-Path: 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 090C51A011A for ; Tue, 15 Apr 2014 11:52:35 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -2.172 X-Spam-Level: X-Spam-Status: No, score=-2.172 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RP_MATCHES_RCVD=-0.272] 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 nzhX9Fj-H9EJ for ; Tue, 15 Apr 2014 11:52:32 -0700 (PDT) Received: from nostrum.com (raven-v6.nostrum.com [IPv6:2001:470:d:1130::1]) by ietfa.amsl.com (Postfix) with ESMTP id 836541A0262 for ; Tue, 15 Apr 2014 11:52:32 -0700 (PDT) Received: from unnumerable.local (pool-173-57-107-66.dllstx.fios.verizon.net [173.57.107.66]) (authenticated bits=0) by nostrum.com (8.14.8/8.14.7) with ESMTP id s3FIqR1A058356 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES128-SHA bits=128 verify=OK); Tue, 15 Apr 2014 13:52:28 -0500 (CDT) (envelope-from rjsparks@nostrum.com) X-Authentication-Warning: raven.nostrum.com: Host pool-173-57-107-66.dllstx.fios.verizon.net [173.57.107.66] claimed to be unnumerable.local Message-ID: <534D7FEB.4080804@nostrum.com> Date: Tue, 15 Apr 2014 13:52:27 -0500 From: Robert Sparks User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.9; rv:24.0) Gecko/20100101 Thunderbird/24.4.0 MIME-Version: 1.0 To: Henrik Levkowetz , IETF Tools Development References: <534D634B.1070202@nostrum.com> <534D68F4.40404@levkowetz.com> In-Reply-To: <534D68F4.40404@levkowetz.com> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Archived-At: http://mailarchive.ietf.org/arch/msg/tools-development/x3P93OxzCV-71XAl5jpoAoeCcTI Subject: Re: [TOOLS-DEVELOPMENT] Thoughts on path forward on tools to support the new rfc format X-BeenThere: tools-development@ietf.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: Tools Development list server List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 15 Apr 2014 18:52:35 -0000 On 4/15/14, 12:14 PM, Henrik Levkowetz wrote: > Hi Robert, > > One point inline, and one at the end: > > On 2014-04-15 18:50 Robert Sparks said the following: >> Trying to look at the horizon for a moment: >> >> When we are at the point we are producing RFCs in XML, the workflow >> will look like this: >> >> - Authors create content in potentially many formats, one of which >> might be the new XML. (The others include text, word, nroff, and >> any other currently accepted formats). >> Authors need to be able to tell, and the submission point needs to >> check, >> whether the document meets the requirements for being accepted as input >> into publication process. >> >> - The RFC Editor will work in the new XML format >> * Converting other input formats to the XML format >> * Refining the xml into a proposed final canonical RFC product >> >> - The proposed canonical product will be rendered into several >> publication formats >> >> - The authors and the RFC Editor will iterate on reviews of the proposed >> product. (We expect the authors will use the derived publication formats >> primarily for their review.) Both the authors and the rfc editor need to >> be able to quickly tell that the document is still acceptable for >> publication as they edit the proposed final result. >> >> - The end result of that editing round will be published as the RFC >> (a frozen canonical XML document), and it's derived publication formats. >> >> >> I think this flow would best be supported by these tools: >> >> * A tool that converts text documents that are in close-to-internet-draft >> form into the new XML format. We can utilize the exisiting tools that >> render text from the other input formats for submission to get those >> formats. >> >> * A tool that points out what needs to change in order for the xml document >> to be ready. This is likely a combination of the functionality (think in >> terms of functionality, not implementation for the moment) in id-nits, >> the first part of xml2rfc (that parses the document) and several of >> the standalone programs in the current production workflow, >> This should be usable by the rfc editor and document authors, and should >> be useful at any point in the development of the document, from initial >> version to published RFC. >> >> * One or more tools that create the derived publication formats. These also >> need to be available to both the rfc editor and the authors. >> >> * Diff tools to help compare versions. >> >> I think these are the steps we should take towards acquiring those tools >> (If you've seen Heather's email discussing threads of next steps, this >> is intended to incorporate them.) >> >> 1) The volunteer community (primarily Henrik and Julian if I understand >> correctly) will be prototyping the production of an example publication >> format (HTML) from a well-formed example input document in the canonical >> format. (A text format is likely to also fall out, but is not going >> to be the primary focus.) > This doesn't match my understanding -- needs discussion. I think Julian > was looking explicitly at extending xml2rfc's text mode, as that's what > gets used most. Ack. >> This work is expected to sanity check that >> the new grammar allows authors to express what we intended, and that >> it can be rendered as expected. Its focus >> won't be on solving rendering for arbitrary inputs however - they'll be >> concentrating on what needs to be done perform the sanity check and make >> the example publication format document so we can iterate with the >> community on those quickly. It may be that they discover that this >> production step is easy, and that it's essentially done when they're >> through, or it may be that they develop requirements for a larger >> effort. >> >> 2) We can start developing an SoW for the tool that would point out >> what needs to change. I see this as a single tool with switches >> to control the level of verification. It will at a minimum check >> for well-formed XML. It can be told to look for spelling errors and >> make grammar checks (such as duplicated words). It can be told to >> highlight where non-ascii UTF-8 is used. It _might_ also be the thing >> that can be told to verify any SVG satisfies our profile, and that >> and that other included things (like mibs or abnf) check out, but >> while developing the SoW we may decide to keep these as separate >> tools. >> >> 3) We can start developing an SoW for an xml diff tool (and continue >> discussing whether we really need such a thing as part of that >> development). >> >> 4) We can start developing an SoW for the tool that converts text >> documents that are in close-to-internet-draft form into the >> new XML format. >> >> Early results from the prototyping effort in 1) will feed into 2). >> Once the prototyping is fairly far along, we'll know if we need a >> 5) or not for specing the publication format converters. > From the viewpoint of xml2rfc, it currently can produce 3 of the 5 > reading formats (paginated and unpaginated text, and html) but neither > pdf or epub is handled at all, and will be a substantial effort. I think > we can safely say that we'll need a step 5) for that. > >> What am I missing? Does anyone think this is the wrong way to >> approach this? > Seems fairly good overall. I'm a bit concerned about the approach to things > like spell checking is to build it into a custom tool, instead of using > something like aspell in html mode. Understood - I was anticipating this code would _use_ aspell, not re-implement it's functionality (perhaps via its library rather than it's command-line interface). > Custom tools always cost more in > maintenance than an off-the-shelf tool. > > > Best regards, > > Henrik > From nobody Tue Apr 15 12:24:59 2014 Return-Path: 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 16A471A0675 for ; Tue, 15 Apr 2014 12:24:58 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -1.9 X-Spam-Level: X-Spam-Status: No, score=-1.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, FREEMAIL_FROM=0.001, RCVD_IN_DNSWL_NONE=-0.0001, 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 xCkccbqHfMFE for ; Tue, 15 Apr 2014 12:24:56 -0700 (PDT) Received: from mout.gmx.net (mout.gmx.net [212.227.15.19]) by ietfa.amsl.com (Postfix) with ESMTP id 9B3891A0186 for ; Tue, 15 Apr 2014 12:24:56 -0700 (PDT) Received: from [192.168.2.117] ([93.217.104.232]) by mail.gmx.com (mrgmx103) with ESMTPSA (Nemesis) id 0MUHbK-1WRzjs0P46-00Qxrz; Tue, 15 Apr 2014 21:24:42 +0200 Message-ID: <534D8776.9060209@gmx.de> Date: Tue, 15 Apr 2014 21:24:38 +0200 From: Julian Reschke User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:24.0) Gecko/20100101 Thunderbird/24.4.0 MIME-Version: 1.0 To: Henrik Levkowetz , Robert Sparks , IETF Tools Development References: <534D634B.1070202@nostrum.com> <534D68F4.40404@levkowetz.com> In-Reply-To: <534D68F4.40404@levkowetz.com> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Provags-ID: V03:K0:9ExI6OnfKFJfenVdaQWIGjAzC4lBuEUaqkYAp808cSD8NRagV2u 1ITKMTnxsGsPSPXhRbjOrQ2ahNhiwrInPrenu29/yMQR/MhkiF7EHGPSgTCx4a2UZ7LfcCh +CTgqG1rgh018ZPsoauvv5HInRB8TcWltpe1Q7i9AEuFhRiuiIhJsakiMfIRMMLcK8LGxSN l/rVFzfVHGCsAi+Z9HL+A== Archived-At: http://mailarchive.ietf.org/arch/msg/tools-development/o1xnuqaJFbPZ4Wwa3JPn3kwn_dg Subject: Re: [TOOLS-DEVELOPMENT] Thoughts on path forward on tools to support the new rfc format X-BeenThere: tools-development@ietf.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: Tools Development list server List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 15 Apr 2014 19:24:58 -0000 On 2014-04-15 19:14, Henrik Levkowetz wrote: > ... >> 1) The volunteer community (primarily Henrik and Julian if I understand >> correctly) will be prototyping the production of an example publication >> format (HTML) from a well-formed example input document in the canonical >> format. (A text format is likely to also fall out, but is not going >> to be the primary focus.) > > This doesn't match my understanding -- needs discussion. I think Julian > was looking explicitly at extending xml2rfc's text mode, as that's what > gets used most. > ... Actually, I was mainly thinking about rfc2629.xslt's HTML generation (and maybe EPub). Best regards, Julian