From tools-discuss-bounces@ietf.org Fri Mar 10 10:58:41 2006 Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1FHk0m-0008M7-7Y; Fri, 10 Mar 2006 10:58:40 -0500 Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1FHk0l-0008Lr-1e for tools-discuss@ietf.org; Fri, 10 Mar 2006 10:58:39 -0500 Received: from p-mail2.rd.francetelecom.com ([195.101.245.16]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1FHk0j-00031K-N1 for tools-discuss@ietf.org; Fri, 10 Mar 2006 10:58:39 -0500 Received: from ftrdmel10.rd.francetelecom.fr ([10.193.117.156]) by ftrdsmtp1.rd.francetelecom.fr with Microsoft SMTPSVC(6.0.3790.1830); Fri, 10 Mar 2006 16:58:27 +0100 Received: from l-at8613.rd.francetelecom.fr ([10.193.15.71]) by ftrdmel10.rd.francetelecom.fr with Microsoft SMTPSVC(6.0.3790.211); Fri, 10 Mar 2006 16:58:27 +0100 Subject: Re: [Tools-discuss] Comments on wg status pages From: Thomas Morin To: Henrik Levkowetz In-Reply-To: <437E2214.6070201@levkowetz.com> References: <1132247369.20783.37.camel@wintermute> <437E2214.6070201@levkowetz.com> Content-Type: text/plain Organization: France Telecom R&D Date: Fri, 10 Mar 2006 16:58:40 +0100 Message-Id: <1142006321.27118.115.camel@wintermute> Mime-Version: 1.0 X-Mailer: Evolution 2.4.2.1 Content-Transfer-Encoding: 7bit X-OriginalArrivalTime: 10 Mar 2006 15:58:27.0579 (UTC) FILETIME=[78306CB0:01C6445B] X-Spam-Score: 0.0 (/) X-Scan-Signature: ffa9dfbbe7cc58b3fa6b8ae3e57b0aa3 Cc: tools-discuss@ietf.org X-BeenThere: tools-discuss@ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: IETF Tools Discussion List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: tools-discuss-bounces@ietf.org Hi Henritz, Henrik Levkowetz, 2005-11-18: > Hi Thomas, > > on 2005-11-17 18:09 Thomas Morin said the following: > > > 1) About wg status pages, I have one comment : the nice upload feature > > that allows me to upload an XML version of my draft, doesn't seem to > > really work. The page I've got after the upload contains a link to the > > doc, but when I come back (later) on the draft page, that link is gone. > > Is this a bug ? > > Yes. The probable cause is that we now have two tools servers, and > I've not arranged for two-way replication; quite to the contrary there's > deletion of non-matching files on the secondary server. > I'll have a look at this. It looks like "deletion of non-matching files" has been solved, but not the "two-way replication". Is this something just not-done-yet, or a bug ? Cheers, -Thomas _______________________________________________ Tools-discuss mailing list Tools-discuss@ietf.org https://www1.ietf.org/mailman/listinfo/tools-discuss From tools-discuss-bounces@ietf.org Sat Mar 11 10:16:16 2006 Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1FI5pF-0008Tb-F3; Sat, 11 Mar 2006 10:16:13 -0500 Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1FI5pE-0008TW-3L for tools-discuss@ietf.org; Sat, 11 Mar 2006 10:16:12 -0500 Received: from mailgw3.ericsson.se ([193.180.251.60]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1FI5pC-00087P-FO for tools-discuss@ietf.org; Sat, 11 Mar 2006 10:16:12 -0500 Received: from esealmw127.eemea.ericsson.se (unknown [153.88.254.122]) by mailgw3.ericsson.se (Symantec Mail Security) with ESMTP id 09E39187; Sat, 11 Mar 2006 16:16:07 +0100 (CET) Received: from esealmw129.eemea.ericsson.se ([153.88.254.173]) by esealmw127.eemea.ericsson.se with Microsoft SMTPSVC(6.0.3790.1830); Sat, 11 Mar 2006 16:16:06 +0100 Received: from [147.214.237.61] ([147.214.237.61]) by esealmw129.eemea.ericsson.se with Microsoft SMTPSVC(6.0.3790.1830); Sat, 11 Mar 2006 16:16:06 +0100 Message-ID: <4412E8F5.107@levkowetz.com> Date: Sat, 11 Mar 2006 16:12:53 +0100 From: Henrik Levkowetz User-Agent: Thunderbird 1.5 (Macintosh/20051201) MIME-Version: 1.0 To: Thomas Morin Subject: Re: [Tools-discuss] Comments on wg status pages References: <1132247369.20783.37.camel@wintermute> <437E2214.6070201@levkowetz.com> <1142006321.27118.115.camel@wintermute> In-Reply-To: <1142006321.27118.115.camel@wintermute> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-OriginalArrivalTime: 11 Mar 2006 15:16:06.0523 (UTC) FILETIME=[B803CCB0:01C6451E] X-Brightmail-Tracker: AAAAAA== X-Spam-Score: 0.0 (/) X-Scan-Signature: 8abaac9e10c826e8252866cbe6766464 Cc: tools-discuss@ietf.org X-BeenThere: tools-discuss@ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: IETF Tools Discussion List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: tools-discuss-bounces@ietf.org Hi Thomas, On 2006-03-10 16:58 Thomas Morin said the following: > Hi Henritz, > > Henrik Levkowetz, 2005-11-18: >> Hi Thomas, >> >> on 2005-11-17 18:09 Thomas Morin said the following: >> >>> 1) About wg status pages, I have one comment : the nice upload feature >>> that allows me to upload an XML version of my draft, doesn't seem to >>> really work. The page I've got after the upload contains a link to the >>> doc, but when I come back (later) on the draft page, that link is gone. >>> Is this a bug ? >> Yes. The probable cause is that we now have two tools servers, and >> I've not arranged for two-way replication; quite to the contrary there's >> deletion of non-matching files on the secondary server. >> I'll have a look at this. > > It looks like "deletion of non-matching files" has been solved, but not > the "two-way replication". Is this something just not-done-yet, or a > bug ? Not done yet. I'll be replacing the primary tools server within a few weeks, and wanted to wait till that was done until I arranged for two-way replication. Sorry for the delay. Henrik _______________________________________________ Tools-discuss mailing list Tools-discuss@ietf.org https://www1.ietf.org/mailman/listinfo/tools-discuss From tools-discuss-bounces@ietf.org Mon Mar 13 03:34:17 2006 Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1FIiVD-0000w0-NT; Mon, 13 Mar 2006 03:34:07 -0500 Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1FIiVC-0000ud-19 for tools-discuss@ietf.org; Mon, 13 Mar 2006 03:34:06 -0500 Received: from av7-1-sn3.vrr.skanova.net ([81.228.9.181]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1FIiVA-0005qa-MA for tools-discuss@ietf.org; Mon, 13 Mar 2006 03:34:05 -0500 Received: by av7-1-sn3.vrr.skanova.net (Postfix, from userid 502) id 2B15337EDB; Mon, 13 Mar 2006 09:15:23 +0100 (CET) Received: from smtp3-1-sn3.vrr.skanova.net (smtp3-1-sn3.vrr.skanova.net [81.228.9.101]) by av7-1-sn3.vrr.skanova.net (Postfix) with ESMTP id 64D2E37EDB; Mon, 13 Mar 2006 09:15:22 +0100 (CET) Received: from shiraz.levkowetz.com (81-224-201-50-no45.tbcn.telia.com [81.224.201.50]) by smtp3-1-sn3.vrr.skanova.net (Postfix) with ESMTP id AE58D37E60; Mon, 13 Mar 2006 09:34:02 +0100 (CET) Received: from localhost ([127.0.0.1]) by shiraz.levkowetz.com with esmtp (Exim 4.60) (envelope-from ) id 1FIiV8-0004TK-3i; Mon, 13 Mar 2006 09:34:02 +0100 Message-ID: <44152E79.8040306@levkowetz.com> Date: Mon, 13 Mar 2006 09:34:01 +0100 From: Henrik Levkowetz User-Agent: Thunderbird 1.5 (Macintosh/20051201) MIME-Version: 1.0 To: Allison Mankin Subject: Re: [Tools-discuss] Idnits-1.85 - requesting a further feature References: <200601151954.OAA11113@ietf.org> In-Reply-To: <200601151954.OAA11113@ietf.org> X-Enigmail-Version: 0.94.0.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit X-SA-Exim-Connect-IP: 127.0.0.1 X-SA-Exim-Mail-From: henrik@levkowetz.com X-SA-Exim-Scanned: No (on shiraz.levkowetz.com); SAEximRunCond expanded to false X-Spam-Score: 0.1 (/) X-Scan-Signature: bb8f917bb6b8da28fc948aeffb74aa17 Cc: tools-discuss@ietf.org X-BeenThere: tools-discuss@ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: IETF Tools Discussion List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: tools-discuss-bounces@ietf.org Hi Allison, on 2006-01-15 20:55 Allison Mankin said the following: > Hi, Henrik, > > Would it be hard to add checking of Section 6A and 6B of > http://www.ietf.org/ID-Checklist.html to Idnits when you next > update? I've added the first part of this (check for RFC 2606 compliance for FQDNs) in v1.87, if you'd like to try it out. I'll get to the second part (check of literals) eventually, too ;-) Regards, Henrik > The shepherds and ADs vet a lot of example addresses. It's > pretty easy to catch problem FQDNs by eye, but problem literals > can slip through more readily, especially if most of the literals > in a document have been switched to comply with RFC 3330/RFC 3849, > but a few have been missed. > > The IESG ends up catching 6A/6B nits often. > > Allison > > > > _______________________________________________ > Tools-discuss mailing list > Tools-discuss@ietf.org > https://www1.ietf.org/mailman/listinfo/tools-discuss > _______________________________________________ Tools-discuss mailing list Tools-discuss@ietf.org https://www1.ietf.org/mailman/listinfo/tools-discuss From tools-discuss-bounces@ietf.org Fri Mar 17 17:36:25 2006 Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1FKNYW-0001HJ-1g; Fri, 17 Mar 2006 17:36:24 -0500 Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1FKNYU-0001Cv-PD for tools-discuss@ietf.org; Fri, 17 Mar 2006 17:36:22 -0500 Received: from sj-iport-2-in.cisco.com ([171.71.176.71] helo=sj-iport-2.cisco.com) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1FKNYT-0008AR-GM for tools-discuss@ietf.org; Fri, 17 Mar 2006 17:36:22 -0500 Received: from sj-core-2.cisco.com ([171.71.177.254]) by sj-iport-2.cisco.com with ESMTP; 17 Mar 2006 14:36:21 -0800 X-IronPort-AV: i="4.03,106,1141632000"; d="scan'208"; a="315629995:sNHT317104748" Received: from imail.cisco.com (sjc12-sbr-sw3-3f5.cisco.com [172.19.96.182]) by sj-core-2.cisco.com (8.12.10/8.12.6) with ESMTP id k2HMaKGv009148 for ; Fri, 17 Mar 2006 14:36:20 -0800 (PST) Received: from [10.32.244.218] (stealth-10-32-244-218.cisco.com [10.32.244.218]) by imail.cisco.com (8.12.11/8.12.10) with ESMTP id k2HMbZkW026284 for ; Fri, 17 Mar 2006 14:37:35 -0800 Mime-Version: 1.0 (Apple Message framework v746.2) Content-Transfer-Encoding: 7bit Message-Id: <6C2E5AA5-8DF2-4DDF-A08C-9641A9742013@cisco.com> Content-Type: text/plain; charset=US-ASCII; delsp=yes; format=flowed To: tools-discuss@ietf.org From: Fred Baker Date: Fri, 17 Mar 2006 14:36:19 -0800 X-Mailer: Apple Mail (2.746.2) DKIM-Signature: a=rsa-sha1; q=dns; l=741; t=1142635055; x=1143067255; c=relaxed/simple; s=nebraska; h=Subject:From:Date:Content-Type:Content-Transfer-Encoding:Mime-Version; d=cisco.com; i=fred@cisco.com; z=From:Fred=20Baker=20 |Subject:Text=20Format=20of=20the=20Agenda |To:tools-discuss@ietf.org; X=v=3Dmtcc.com=3B=20h=3DjcagXQMA1yB0O6Y/ooZHqgLmkO0=3D; b=sH9e2q7CnU1uwKycb1cVc5++lneg+/ubIu8srhw2YTULoEBvf9WReXEBuH9xdIiv27H31eZ0 Q3gdPUaCxH+cYiopk4vwyyu1sFehzI1tUwEWkpgqZpPeEuRQZSMb2NL3ZEHMnYt8azw0ubIOYHL k3MgUi1Uzwi1AoXYyTkhzBvM=; Authentication-Results: imail.cisco.com; header.From=fred@cisco.com; dkim=pass ( message from cisco.com verified; ); X-Spam-Score: 0.0 (/) X-Scan-Signature: 7a6398bf8aaeabc7a7bb696b6b0a2aad Subject: [Tools-discuss] Text Format of the Agenda X-BeenThere: tools-discuss@ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: IETF Tools Discussion List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: tools-discuss-bounces@ietf.org If you go to http://www.ietf.org/meetings/IETF-65.html and click on "Meeting Agenda", you get a web page whose URL is https:// datatracker.ietf.org/public/meeting_agenda_html.cgi?meeting_num=65. At the top of that, there is a link to the "(Text Format of the Agenda)", which gets you to https://datatracker.ietf.org/public/ meeting_agenda_text.cgi?meeting_num=65. If I download that, the file is named meeting_agenda_text.cgi.html, and is indeed in html format. Near as I can tell the difference between the "text" format and the "html" format is that the "text" format has URLs for the working group charters but not the agendas. Am I missing something? Any idea why the "text" file would be in html format? _______________________________________________ Tools-discuss mailing list Tools-discuss@ietf.org https://www1.ietf.org/mailman/listinfo/tools-discuss From tools-discuss-bounces@ietf.org Fri Mar 17 18:06:17 2006 Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1FKO1Q-0004fL-SG; Fri, 17 Mar 2006 18:06:16 -0500 Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1FKO1O-0004LX-Vf for tools-discuss@ietf.org; Fri, 17 Mar 2006 18:06:14 -0500 Received: from boreas.isi.edu ([128.9.160.161]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1FKO1N-0000MX-Im for tools-discuss@ietf.org; Fri, 17 Mar 2006 18:06:14 -0500 Received: from [128.9.168.55] (upn.isi.edu [128.9.168.55]) by boreas.isi.edu (8.11.6p2+0917/8.11.2) with ESMTP id k2HN5cG08781; Fri, 17 Mar 2006 15:05:38 -0800 (PST) Message-ID: <441B4043.40400@isi.edu> Date: Fri, 17 Mar 2006 15:03:31 -0800 From: Joe Touch User-Agent: Thunderbird 1.5 (Windows/20051201) MIME-Version: 1.0 To: Fred Baker Subject: Re: [Tools-discuss] Text Format of the Agenda References: <6C2E5AA5-8DF2-4DDF-A08C-9641A9742013@cisco.com> In-Reply-To: <6C2E5AA5-8DF2-4DDF-A08C-9641A9742013@cisco.com> X-Enigmail-Version: 0.94.0.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit X-ISI-4-43-8-MailScanner: Found to be clean X-MailScanner-From: touch@isi.edu X-Spam-Score: 0.0 (/) X-Scan-Signature: a7d6aff76b15f3f56fcb94490e1052e4 Cc: tools-discuss@ietf.org X-BeenThere: tools-discuss@ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: IETF Tools Discussion List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: tools-discuss-bounces@ietf.org -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 That might be for some of us, including Eliot Lear, Lars Eggert, and myself, who use the text as input to software to generate Calendar entries (Eliod does .ics; I convert them to .vcs, and Lars had a native .vcs one too). I.e., the text is de-HTML'd, but still includes body. It would have been equally useful to have provided an XML of the calendar which could be converted into whatever desired format (HTML, ics, vcs, etc.), but that may be a while off. Joe Fred Baker wrote: > If you go to http://www.ietf.org/meetings/IETF-65.html and click on > "Meeting Agenda", you get a web page whose URL is > https://datatracker.ietf.org/public/meeting_agenda_html.cgi?meeting_num=65. > At the top of that, there is a link to the "(Text Format of the > Agenda)", which gets you to > https://datatracker.ietf.org/public/meeting_agenda_text.cgi?meeting_num=65. > If I download that, the file is named meeting_agenda_text.cgi.html, and > is indeed in html format. Near as I can tell the difference between the > "text" format and the "html" format is that the "text" format has URLs > for the working group charters but not the agendas. > > Am I missing something? Any idea why the "text" file would be in html > format? > > _______________________________________________ > Tools-discuss mailing list > Tools-discuss@ietf.org > https://www1.ietf.org/mailman/listinfo/tools-discuss -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.4 (MingW32) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iD8DBQFEG0BDE5f5cImnZrsRAsgAAJ41bF2RY2qTAK1yoYuKCwfVt4plMACeNdod htoNDG6efOn7x+VbdMRvEpw= =OTYt -----END PGP SIGNATURE----- _______________________________________________ Tools-discuss mailing list Tools-discuss@ietf.org https://www1.ietf.org/mailman/listinfo/tools-discuss From tools-discuss-bounces@ietf.org Fri Mar 17 18:26:28 2006 Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1FKOKv-0007rA-Mn; Fri, 17 Mar 2006 18:26:25 -0500 Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1FKOKv-0007r5-3H for tools-discuss@ietf.org; Fri, 17 Mar 2006 18:26:25 -0500 Received: from sj-iport-1-in.cisco.com ([171.71.176.70] helo=sj-iport-1.cisco.com) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1FKOKt-0001Uk-Os for tools-discuss@ietf.org; Fri, 17 Mar 2006 18:26:25 -0500 Received: from sj-core-2.cisco.com ([171.71.177.254]) by sj-iport-1.cisco.com with ESMTP; 17 Mar 2006 15:26:23 -0800 Received: from imail.cisco.com (sjc12-sbr-sw3-3f5.cisco.com [172.19.96.182]) by sj-core-2.cisco.com (8.12.10/8.12.6) with ESMTP id k2HNQNGv010281; Fri, 17 Mar 2006 15:26:23 -0800 (PST) Received: from [10.32.244.218] (stealth-10-32-244-218.cisco.com [10.32.244.218]) by imail.cisco.com (8.12.11/8.12.10) with ESMTP id k2HNRcaa026568; Fri, 17 Mar 2006 15:27:38 -0800 In-Reply-To: <441B4043.40400@isi.edu> References: <6C2E5AA5-8DF2-4DDF-A08C-9641A9742013@cisco.com> <441B4043.40400@isi.edu> Mime-Version: 1.0 (Apple Message framework v746.2) Content-Type: text/plain; charset=US-ASCII; delsp=yes; format=flowed Message-Id: <6D8C0E2E-8184-4F1C-927F-859452179E8A@cisco.com> Content-Transfer-Encoding: 7bit From: Fred Baker Subject: Re: [Tools-discuss] Text Format of the Agenda Date: Fri, 17 Mar 2006 15:26:21 -0800 To: Joe Touch X-Mailer: Apple Mail (2.746.2) DKIM-Signature: a=rsa-sha1; q=dns; l=2662; t=1142638058; x=1143070258; c=relaxed/simple; s=nebraska; h=Subject:From:Date:Content-Type:Content-Transfer-Encoding:Mime-Version; d=cisco.com; i=fred@cisco.com; z=From:Fred=20Baker=20 |Subject:Re=3A=20[Tools-discuss]=20Text=20Format=20of=20the=20Agenda |To:Joe=20Touch=20; X=v=3Dmtcc.com=3B=20h=3Dg4CVZyr0609a5UH4/OWNzfRw0ik=3D; b=bREiLbC2kXo8HayFbKkEbLfTqplhW0uwU73NGsXX1kVgD2HNlcCvbV8Qm3OtVoFzl3VsRlCr uFtfQQTGfMjl+XTZvcqtszehlNrf8tqxokZ7YOV8vsmYuGsEk00mTIufAnOwaVxUgpbe2+teC0p qYMrWMKt+RhYIlK3BNmK0bGw=; Authentication-Results: imail.cisco.com; header.From=fred@cisco.com; dkim=pass ( 31 extraneous bytes; message from cisco.com verified; ); X-Spam-Score: 0.0 (/) X-Scan-Signature: 41c17b4b16d1eedaa8395c26e9a251c4 Cc: tools-discuss@ietf.org X-BeenThere: tools-discuss@ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: IETF Tools Discussion List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: tools-discuss-bounces@ietf.org I do the same (generate .ics from text), but start from TEXT and don't particularly want the markup stuff. I'm going to have to edit the TEXT format back to TEXT before feeding it into my TEXT tool. When I see something that is marked TEXT, I don't especially expect to find HTML -= especially when for the previous month the page has been in flat ASCII. I expect to get TEXT. What's the chance of getting a TEXT file when I download the file marked "TEXT file"? Wouldn't it be nice if we could simply get an RFC 2445-compliant calendar up there? Like, maybe we could subscribe to it? In my dream world, I guess I would like to have a web page that I could go to, click on radio dials next to the things I care about, and get downloaded to me an RFC 2445 calendar that I can import. On Mar 17, 2006, at 3:03 PM, Joe Touch wrote: > -----BEGIN PGP SIGNED MESSAGE----- > Hash: SHA1 > > That might be for some of us, including Eliot Lear, Lars Eggert, and > myself, who use the text as input to software to generate Calendar > entries (Eliod does .ics; I convert them to .vcs, and Lars had a > native > .vcs one too). > > I.e., the text is de-HTML'd, but still includes body. It would have > been > equally useful to have provided an XML of the calendar which could be > converted into whatever desired format (HTML, ics, vcs, etc.), but > that > may be a while off. > > Joe > > Fred Baker wrote: >> If you go to http://www.ietf.org/meetings/IETF-65.html and click on >> "Meeting Agenda", you get a web page whose URL is >> https://datatracker.ietf.org/public/meeting_agenda_html.cgi? >> meeting_num=65. >> At the top of that, there is a link to the "(Text Format of the >> Agenda)", which gets you to >> https://datatracker.ietf.org/public/meeting_agenda_text.cgi? >> meeting_num=65. >> If I download that, the file is named >> meeting_agenda_text.cgi.html, and >> is indeed in html format. Near as I can tell the difference >> between the >> "text" format and the "html" format is that the "text" format has >> URLs >> for the working group charters but not the agendas. >> >> Am I missing something? Any idea why the "text" file would be in html >> format? >> >> _______________________________________________ >> Tools-discuss mailing list >> Tools-discuss@ietf.org >> https://www1.ietf.org/mailman/listinfo/tools-discuss > -----BEGIN PGP SIGNATURE----- > Version: GnuPG v1.2.4 (MingW32) > Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org > > iD8DBQFEG0BDE5f5cImnZrsRAsgAAJ41bF2RY2qTAK1yoYuKCwfVt4plMACeNdod > htoNDG6efOn7x+VbdMRvEpw= > =OTYt > -----END PGP SIGNATURE----- _______________________________________________ Tools-discuss mailing list Tools-discuss@ietf.org https://www1.ietf.org/mailman/listinfo/tools-discuss From tools-discuss-bounces@ietf.org Fri Mar 17 18:45:28 2006 Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1FKOdL-00045v-Gc; Fri, 17 Mar 2006 18:45:27 -0500 Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1FKOdJ-00045q-Mf for tools-discuss@ietf.org; Fri, 17 Mar 2006 18:45:25 -0500 Received: from p130.piuha.net ([193.234.218.130]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1FKOdI-0002Dp-6S for tools-discuss@ietf.org; Fri, 17 Mar 2006 18:45:25 -0500 Received: from p130.piuha.net (localhost [127.0.0.1]) by p130.piuha.net (Postfix) with ESMTP id 7E46E898A0; Sat, 18 Mar 2006 01:45:22 +0200 (EET) Received: from [127.0.0.1] (p130.piuha.net [193.234.218.130]) by p130.piuha.net (Postfix) with ESMTP id E67B28988D; Sat, 18 Mar 2006 01:45:20 +0200 (EET) Message-ID: <441B4A0A.8080205@piuha.net> Date: Sat, 18 Mar 2006 01:45:14 +0200 From: Jari Arkko User-Agent: Mozilla Thunderbird 1.0.7 (X11/20051013) X-Accept-Language: en-us, en MIME-Version: 1.0 To: Fred Baker Subject: Re: [Tools-discuss] Text Format of the Agenda References: <6C2E5AA5-8DF2-4DDF-A08C-9641A9742013@cisco.com> <441B4043.40400@isi.edu> <6D8C0E2E-8184-4F1C-927F-859452179E8A@cisco.com> In-Reply-To: <6D8C0E2E-8184-4F1C-927F-859452179E8A@cisco.com> Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit X-Virus-Scanned: ClamAV using ClamSMTP X-Spam-Score: 0.0 (/) X-Scan-Signature: bdc523f9a54890b8a30dd6fd53d5d024 Cc: tools-discuss@ietf.org, Joe Touch X-BeenThere: tools-discuss@ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: IETF Tools Discussion List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: tools-discuss-bounces@ietf.org If you want pure text, cut & paste from the browser may work for you... it did work for me. At other times I have sometimes used an emacs macro to get rid of html directives... But yes, if your desired end result is a calendar, it would be much better to start from a calendar format. --Jari Fred Baker wrote: > I do the same (generate .ics from text), but start from TEXT and don't particularly want the markup stuff. I'm going to have to edit the TEXT format back to TEXT before feeding it into my TEXT tool. When I see something that is marked TEXT, I don't especially expect to find HTML -= especially when for the previous month the page has been in flat ASCII. I expect to get TEXT. > > What's the chance of getting a TEXT file when I download the file marked "TEXT file"? > > Wouldn't it be nice if we could simply get an RFC 2445-compliant calendar up there? Like, maybe we could subscribe to it? > > In my dream world, I guess I would like to have a web page that I could go to, click on radio dials next to the things I care about, and get downloaded to me an RFC 2445 calendar that I can import. > > On Mar 17, 2006, at 3:03 PM, Joe Touch wrote: > > That might be for some of us, including Eliot Lear, Lars Eggert, and > myself, who use the text as input to software to generate Calendar > entries (Eliod does .ics; I convert them to .vcs, and Lars had a native > .vcs one too). > > I.e., the text is de-HTML'd, but still includes body. It would have been > equally useful to have provided an XML of the calendar which could be > converted into whatever desired format (HTML, ics, vcs, etc.), but that > may be a while off. > > Joe > > Fred Baker wrote: > > >>> If you go to http://www.ietf.org/meetings/IETF-65.html and click on > >>> "Meeting Agenda", you get a web page whose URL is > >>> https://datatracker.ietf.org/public/meeting_agenda_html.cgi? > meeting_num=65. > >>> At the top of that, there is a link to the "(Text Format of the > >>> Agenda)", which gets you to > >>> https://datatracker.ietf.org/public/meeting_agenda_text.cgi? > meeting_num=65. > >>> If I download that, the file is named > meeting_agenda_text.cgi.html, and > >>> is indeed in html format. Near as I can tell the difference > between the > >>> "text" format and the "html" format is that the "text" format has > URLs > >>> for the working group charters but not the agendas. > >>> > >>> Am I missing something? Any idea why the "text" file would be in html > >>> format? > >>> > >>> _______________________________________________ > >>> Tools-discuss mailing list > >>> Tools-discuss@ietf.org > >>> https://www1.ietf.org/mailman/listinfo/tools-discuss > > _______________________________________________ > Tools-discuss mailing list > Tools-discuss@ietf.org > https://www1.ietf.org/mailman/listinfo/tools-discuss _______________________________________________ Tools-discuss mailing list Tools-discuss@ietf.org https://www1.ietf.org/mailman/listinfo/tools-discuss From tools-discuss-bounces@ietf.org Fri Mar 17 19:09:10 2006 Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1FKP0G-0002kJ-1x; Fri, 17 Mar 2006 19:09:08 -0500 Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1FKP0F-0002kE-DT for tools-discuss@ietf.org; Fri, 17 Mar 2006 19:09:07 -0500 Received: from boreas.isi.edu ([128.9.160.161]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1FKP0C-0003R5-VN for tools-discuss@ietf.org; Fri, 17 Mar 2006 19:09:07 -0500 Received: from [128.9.168.55] (upn.isi.edu [128.9.168.55]) by boreas.isi.edu (8.11.6p2+0917/8.11.2) with ESMTP id k2I07LG26661; Fri, 17 Mar 2006 16:07:21 -0800 (PST) Message-ID: <441B4EC0.7040508@isi.edu> Date: Fri, 17 Mar 2006 16:05:20 -0800 From: Joe Touch User-Agent: Thunderbird 1.5 (Windows/20051201) MIME-Version: 1.0 To: Fred Baker Subject: Re: [Tools-discuss] Text Format of the Agenda References: <6C2E5AA5-8DF2-4DDF-A08C-9641A9742013@cisco.com> <441B4043.40400@isi.edu> <6D8C0E2E-8184-4F1C-927F-859452179E8A@cisco.com> In-Reply-To: <6D8C0E2E-8184-4F1C-927F-859452179E8A@cisco.com> X-Enigmail-Version: 0.94.0.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit X-ISI-4-43-8-MailScanner: Found to be clean X-MailScanner-From: touch@isi.edu X-Spam-Score: 0.0 (/) X-Scan-Signature: b280b4db656c3ca28dd62e5e0b03daa8 Cc: tools-discuss@ietf.org X-BeenThere: tools-discuss@ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: IETF Tools Discussion List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: tools-discuss-bounces@ietf.org -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Fred Baker wrote: > I do the same (generate .ics from text), but start from TEXT and don't > particularly want the markup stuff. We want to insert the URLs in the .ics/.vcs entries, which have a corresponding field for it. > I'm going to have to edit the TEXT > format back to TEXT before feeding it into my TEXT tool. When I see > something that is marked TEXT, I don't especially expect to find HTML -= Agreed - I would expect the URL, but not the HTML markup. > especially when for the previous month the page has been in flat ASCII. > I expect to get TEXT. > > What's the chance of getting a TEXT file when I download the file marked > "TEXT file"? > > Wouldn't it be nice if we could simply get an RFC 2445-compliant > calendar up there? Like, maybe we could subscribe to it? That's what Eliot posts at http://www.ofcourseimright.com/ietf65-draft.ics I provide a .vcs translation (for Palm users) at: http://www.ofcourseimright.com/ietf65-draft-palm.vcs as well as at my tools page (www.isi.edu/touch/tools) > In my dream world, I guess I would like to have a web page that I could > go to, click on radio dials next to the things I care about, and get > downloaded to me an RFC 2445 calendar that I can import. > > On Mar 17, 2006, at 3:03 PM, Joe Touch wrote: > > That might be for some of us, including Eliot Lear, Lars Eggert, and > myself, who use the text as input to software to generate Calendar > entries (Eliod does .ics; I convert them to .vcs, and Lars had a native > .vcs one too). > > I.e., the text is de-HTML'd, but still includes body. It would have been > equally useful to have provided an XML of the calendar which could be > converted into whatever desired format (HTML, ics, vcs, etc.), but that > may be a while off. > > Joe > > Fred Baker wrote: >>>> If you go to http://www.ietf.org/meetings/IETF-65.html and click on >>>> "Meeting Agenda", you get a web page whose URL is >>>> https://datatracker.ietf.org/public/meeting_agenda_html.cgi?meeting_num=65. >>>> >>>> At the top of that, there is a link to the "(Text Format of the >>>> Agenda)", which gets you to >>>> https://datatracker.ietf.org/public/meeting_agenda_text.cgi?meeting_num=65. >>>> >>>> If I download that, the file is named meeting_agenda_text.cgi.html, and >>>> is indeed in html format. Near as I can tell the difference between the >>>> "text" format and the "html" format is that the "text" format has URLs >>>> for the working group charters but not the agendas. >>>> >>>> Am I missing something? Any idea why the "text" file would be in html >>>> format? >>>> >>>> _______________________________________________ >>>> Tools-discuss mailing list >>>> Tools-discuss@ietf.org >>>> https://www1.ietf.org/mailman/listinfo/tools-discuss -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.4 (MingW32) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iD8DBQFEG07AE5f5cImnZrsRAur1AJ9eMdQc4L0auPPWFULuENfjIxgP7gCeI3Bg c+TKcwJO3OQaMdsDuWggXSw= =RAal -----END PGP SIGNATURE----- _______________________________________________ Tools-discuss mailing list Tools-discuss@ietf.org https://www1.ietf.org/mailman/listinfo/tools-discuss From tools-discuss-bounces@ietf.org Fri Mar 17 20:07:45 2006 Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1FKPuz-0001QL-I1; Fri, 17 Mar 2006 20:07:45 -0500 Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1FKPuy-0001QG-F2 for tools-discuss@ietf.org; Fri, 17 Mar 2006 20:07:44 -0500 Received: from av10-2-sn2.hy.skanova.net ([81.228.8.182]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1FKPux-0004pH-44 for tools-discuss@ietf.org; Fri, 17 Mar 2006 20:07:44 -0500 Received: by av10-2-sn2.hy.skanova.net (Postfix, from userid 502) id E41B137F61; Sat, 18 Mar 2006 02:07:41 +0100 (CET) Received: from smtp4-2-sn2.hy.skanova.net (smtp4-2-sn2.hy.skanova.net [81.228.8.93]) by av10-2-sn2.hy.skanova.net (Postfix) with ESMTP id CA01837F61; Sat, 18 Mar 2006 02:07:41 +0100 (CET) Received: from shiraz.levkowetz.com (81-224-201-50-no45.tbcn.telia.com [81.224.201.50]) by smtp4-2-sn2.hy.skanova.net (Postfix) with ESMTP id BC90937E43; Sat, 18 Mar 2006 02:07:41 +0100 (CET) Received: from localhost ([127.0.0.1]) by shiraz.levkowetz.com with esmtp (Exim 4.60) (envelope-from ) id 1FKPuv-0006aY-9U; Sat, 18 Mar 2006 02:07:41 +0100 Message-ID: <441B5D5C.5080903@levkowetz.com> Date: Sat, 18 Mar 2006 02:07:40 +0100 From: Henrik Levkowetz User-Agent: Thunderbird 1.5 (Macintosh/20051201) MIME-Version: 1.0 To: Fred Baker Subject: Re: [Tools-discuss] Text Format of the Agenda References: <6C2E5AA5-8DF2-4DDF-A08C-9641A9742013@cisco.com> In-Reply-To: <6C2E5AA5-8DF2-4DDF-A08C-9641A9742013@cisco.com> X-Enigmail-Version: 0.94.0.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit X-SA-Exim-Connect-IP: 127.0.0.1 X-SA-Exim-Mail-From: henrik@levkowetz.com X-SA-Exim-Scanned: No (on shiraz.levkowetz.com); SAEximRunCond expanded to false X-Spam-Score: 0.1 (/) X-Scan-Signature: 9466e0365fc95844abaf7c3f15a05c7d Cc: tools-discuss@ietf.org X-BeenThere: tools-discuss@ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: IETF Tools Discussion List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: tools-discuss-bounces@ietf.org Hmm!! That's a bit odd. It's obviously not a straight text file. The text file agenda is available at http://www.ietf.org/meetings/agenda_65.txt, but that's not really the point -- a link to a text format agenda should not give you a differently formatted html format agenda. Henrik on 2006-03-17 23:36 Fred Baker said the following: > If you go to http://www.ietf.org/meetings/IETF-65.html and click on > "Meeting Agenda", you get a web page whose URL is https:// > datatracker.ietf.org/public/meeting_agenda_html.cgi?meeting_num=65. > At the top of that, there is a link to the "(Text Format of the > Agenda)", which gets you to https://datatracker.ietf.org/public/ > meeting_agenda_text.cgi?meeting_num=65. If I download that, the file > is named meeting_agenda_text.cgi.html, and is indeed in html format. > Near as I can tell the difference between the "text" format and the > "html" format is that the "text" format has URLs for the working > group charters but not the agendas. > > Am I missing something? Any idea why the "text" file would be in html > format? > > _______________________________________________ > Tools-discuss mailing list > Tools-discuss@ietf.org > https://www1.ietf.org/mailman/listinfo/tools-discuss > _______________________________________________ Tools-discuss mailing list Tools-discuss@ietf.org https://www1.ietf.org/mailman/listinfo/tools-discuss From tools-discuss-bounces@ietf.org Fri Mar 17 20:08:38 2006 Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1FKPvq-0001Xy-PM; Fri, 17 Mar 2006 20:08:38 -0500 Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1FKPvo-0001XX-Ss for tools-discuss@ietf.org; Fri, 17 Mar 2006 20:08:36 -0500 Received: from av12-2-sn2.hy.skanova.net ([81.228.8.186]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1FKPvo-0004s5-Do for tools-discuss@ietf.org; Fri, 17 Mar 2006 20:08:36 -0500 Received: by av12-2-sn2.hy.skanova.net (Postfix, from userid 502) id B509438025; Sat, 18 Mar 2006 02:08:35 +0100 (CET) Received: from smtp4-2-sn2.hy.skanova.net (smtp4-2-sn2.hy.skanova.net [81.228.8.93]) by av12-2-sn2.hy.skanova.net (Postfix) with ESMTP id 51B4237E8A; Sat, 18 Mar 2006 02:08:35 +0100 (CET) Received: from shiraz.levkowetz.com (81-224-201-50-no45.tbcn.telia.com [81.224.201.50]) by smtp4-2-sn2.hy.skanova.net (Postfix) with ESMTP id 3E63837E45; Sat, 18 Mar 2006 02:08:35 +0100 (CET) Received: from localhost ([127.0.0.1]) by shiraz.levkowetz.com with esmtp (Exim 4.60) (envelope-from ) id 1FKPvm-0006ct-TE; Sat, 18 Mar 2006 02:08:35 +0100 Message-ID: <441B5D92.6080607@levkowetz.com> Date: Sat, 18 Mar 2006 02:08:34 +0100 From: Henrik Levkowetz User-Agent: Thunderbird 1.5 (Macintosh/20051201) MIME-Version: 1.0 To: Fred Baker Subject: Re: [Tools-discuss] Text Format of the Agenda References: <6C2E5AA5-8DF2-4DDF-A08C-9641A9742013@cisco.com> <441B4043.40400@isi.edu> <6D8C0E2E-8184-4F1C-927F-859452179E8A@cisco.com> In-Reply-To: <6D8C0E2E-8184-4F1C-927F-859452179E8A@cisco.com> X-Enigmail-Version: 0.94.0.0 X-SA-Exim-Connect-IP: 127.0.0.1 X-SA-Exim-Mail-From: henrik@levkowetz.com X-SA-Exim-Scanned: No (on shiraz.levkowetz.com); SAEximRunCond expanded to false X-Spam-Score: 0.1 (/) X-Scan-Signature: 34d35111647d654d033d58d318c0d21a Cc: tools-discuss@ietf.org, Joe Touch X-BeenThere: tools-discuss@ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: IETF Tools Discussion List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Content-Type: multipart/mixed; boundary="===============0996507758==" Errors-To: tools-discuss-bounces@ietf.org This is an OpenPGP/MIME signed message (RFC 2440 and 3156) --===============0996507758== Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="------------enig5F3AFD2B4F7570E1E71D7119" This is an OpenPGP/MIME signed message (RFC 2440 and 3156) --------------enig5F3AFD2B4F7570E1E71D7119 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Hi Fred, on 2006-03-18 00:26 Fred Baker said the following: > I do the same (generate .ics from text), but start from TEXT and =20 > don't particularly want the markup stuff. I'm going to have to edit =20 > the TEXT format back to TEXT before feeding it into my TEXT tool. =20 > When I see something that is marked TEXT, I don't especially expect =20 > to find HTML -=3D especially when for the previous month the page has = > been in flat ASCII. I expect to get TEXT. >=20 > What's the chance of getting a TEXT file when I download the file =20 > marked "TEXT file"? >=20 > Wouldn't it be nice if we could simply get an RFC 2445-compliant =20 > calendar up there? Like, maybe we could subscribe to it? >=20 > In my dream world, I guess I would like to have a web page that I =20 > could go to, click on radio dials next to the things I care about, =20 > and get downloaded to me an RFC 2445 calendar that I can import. I'm working on this. Maybe by Sunday. Henrik =09 > On Mar 17, 2006, at 3:03 PM, Joe Touch wrote: >=20 > That might be for some of us, including Eliot Lear, Lars Eggert, and > myself, who use the text as input to software to generate Calendar > entries (Eliod does .ics; I convert them to .vcs, and Lars had a =20 > native > .vcs one too). >=20 > I.e., the text is de-HTML'd, but still includes body. It would have =20 > been > equally useful to have provided an XML of the calendar which could be > converted into whatever desired format (HTML, ics, vcs, etc.), but =20 > that > may be a while off. >=20 > Joe >=20 > Fred Baker wrote: >>>> If you go to http://www.ietf.org/meetings/IETF-65.html and click on >>>> "Meeting Agenda", you get a web page whose URL is >>>> https://datatracker.ietf.org/public/meeting_agenda_html.cgi?=20 >>>> meeting_num=3D65. >>>> At the top of that, there is a link to the "(Text Format of the >>>> Agenda)", which gets you to >>>> https://datatracker.ietf.org/public/meeting_agenda_text.cgi?=20 >>>> meeting_num=3D65. >>>> If I download that, the file is named =20 >>>> meeting_agenda_text.cgi.html, and >>>> is indeed in html format. Near as I can tell the difference =20 >>>> between the >>>> "text" format and the "html" format is that the "text" format has =20 >>>> URLs >>>> for the working group charters but not the agendas. >>>> >>>> Am I missing something? Any idea why the "text" file would be in htm= l >>>> format? >>>> >>>> _______________________________________________ >>>> Tools-discuss mailing list >>>> Tools-discuss@ietf.org >>>> https://www1.ietf.org/mailman/listinfo/tools-discuss > _______________________________________________ > Tools-discuss mailing list > Tools-discuss@ietf.org > https://www1.ietf.org/mailman/listinfo/tools-discuss --------------enig5F3AFD2B4F7570E1E71D7119 Content-Type: application/pgp-signature; name="signature.asc" Content-Description: OpenPGP digital signature Content-Disposition: attachment; filename="signature.asc" -----BEGIN PGP SIGNATURE----- iD8DBQFEG12SeVhrtTJkXCMRAvvTAKCzL1unqr7oo+qbfES7YPdiMqvssQCfSXWg MGE3b2XMULKO/WXmIvPeCEE= =Mxbx -----END PGP SIGNATURE----- --------------enig5F3AFD2B4F7570E1E71D7119-- --===============0996507758== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ Tools-discuss mailing list Tools-discuss@ietf.org https://www1.ietf.org/mailman/listinfo/tools-discuss --===============0996507758==-- From tools-discuss-bounces@ietf.org Mon Mar 20 15:34:35 2006 Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1FLR5G-0006IZ-Nv; Mon, 20 Mar 2006 15:34:34 -0500 Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1FLR5F-0006IB-KG for tools-discuss@ietf.org; Mon, 20 Mar 2006 15:34:33 -0500 Received: from av6-1-sn3.vrr.skanova.net ([81.228.9.179]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1FLR5F-00024t-2v for tools-discuss@ietf.org; Mon, 20 Mar 2006 15:34:33 -0500 Received: by av6-1-sn3.vrr.skanova.net (Postfix, from userid 502) id 603E937ED0; Mon, 20 Mar 2006 21:34:32 +0100 (CET) Received: from smtp3-2-sn3.vrr.skanova.net (smtp3-2-sn3.vrr.skanova.net [81.228.9.102]) by av6-1-sn3.vrr.skanova.net (Postfix) with ESMTP id 0A84337E8A; Mon, 20 Mar 2006 21:34:32 +0100 (CET) Received: from shiraz.levkowetz.com (81-224-201-50-no45.tbcn.telia.com [81.224.201.50]) by smtp3-2-sn3.vrr.skanova.net (Postfix) with ESMTP id C9F9137E4E; Mon, 20 Mar 2006 21:34:31 +0100 (CET) Received: from localhost ([127.0.0.1]) by shiraz.levkowetz.com with esmtp (Exim 4.60) (envelope-from ) id 1FLR57-0002Ac-2M; Mon, 20 Mar 2006 21:34:27 +0100 Message-ID: <441F11CF.7080603@levkowetz.com> Date: Mon, 20 Mar 2006 14:34:23 -0600 From: Henrik Levkowetz User-Agent: Thunderbird 1.5 (Macintosh/20051201) MIME-Version: 1.0 To: Henrik Levkowetz Subject: Re: [Tools-discuss] Text Format of the Agenda References: <6C2E5AA5-8DF2-4DDF-A08C-9641A9742013@cisco.com> <441B4043.40400@isi.edu> <6D8C0E2E-8184-4F1C-927F-859452179E8A@cisco.com> <441B5D92.6080607@levkowetz.com> In-Reply-To: <441B5D92.6080607@levkowetz.com> X-Enigmail-Version: 0.94.0.0 X-SA-Exim-Connect-IP: 127.0.0.1 X-SA-Exim-Mail-From: henrik@levkowetz.com X-SA-Exim-Scanned: No (on shiraz.levkowetz.com); SAEximRunCond expanded to false X-Spam-Score: 0.1 (/) X-Scan-Signature: b2809b6f39decc6de467dcf252f42af1 Cc: Fred Baker , tools-discuss@ietf.org, Joe Touch X-BeenThere: tools-discuss@ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: IETF Tools Discussion List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Content-Type: multipart/mixed; boundary="===============1766031520==" Errors-To: tools-discuss-bounces@ietf.org This is an OpenPGP/MIME signed message (RFC 2440 and 3156) --===============1766031520== Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="------------enig2B9D3884B541ABF2BB17B62E" This is an OpenPGP/MIME signed message (RFC 2440 and 3156) --------------enig2B9D3884B541ABF2BB17B62E Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Hi Fred (and all others on the list :) I now have a first version of this in place. There's a new link in the right-hand menu column of the WG and Agenda pages on tools.ietf.org, e.g.= , http://www1.tools.ietf.org/agenda/65/ which reads "Calendar" and currently points to http://www1.tools.ietf.org/agenda/65/ics/ If you follow this, you'll get a version of the agenda which has a check-= box in front of each session, letting you select which sessions to includ= e in a calendar file. Submitting this will return a page with a link to an iCalendar file which you can download or subscribe to. Henrik on 2006-03-17 19:08 Henrik Levkowetz said the following: > Hi Fred, >=20 > on 2006-03-18 00:26 Fred Baker said the following: >> I do the same (generate .ics from text), but start from TEXT and =20 >> don't particularly want the markup stuff. I'm going to have to edit =20 >> the TEXT format back to TEXT before feeding it into my TEXT tool. =20 >> When I see something that is marked TEXT, I don't especially expect =20 >> to find HTML -=3D especially when for the previous month the page has = =20 >> been in flat ASCII. I expect to get TEXT. >>=20 >> What's the chance of getting a TEXT file when I download the file =20 >> marked "TEXT file"? >>=20 >> Wouldn't it be nice if we could simply get an RFC 2445-compliant =20 >> calendar up there? Like, maybe we could subscribe to it? >>=20 >> In my dream world, I guess I would like to have a web page that I =20 >> could go to, click on radio dials next to the things I care about, =20 >> and get downloaded to me an RFC 2445 calendar that I can import. >=20 > I'm working on this. Maybe by Sunday. >=20 >=20 > Henrik > =09 >=20 >> On Mar 17, 2006, at 3:03 PM, Joe Touch wrote: >>=20 >> That might be for some of us, including Eliot Lear, Lars Eggert, and >> myself, who use the text as input to software to generate Calendar >> entries (Eliod does .ics; I convert them to .vcs, and Lars had a =20 >> native >> .vcs one too). >>=20 >> I.e., the text is de-HTML'd, but still includes body. It would have =20 >> been >> equally useful to have provided an XML of the calendar which could be >> converted into whatever desired format (HTML, ics, vcs, etc.), but =20 >> that >> may be a while off. >>=20 >> Joe >>=20 >> Fred Baker wrote: >>>>> If you go to http://www.ietf.org/meetings/IETF-65.html and click on= >>>>> "Meeting Agenda", you get a web page whose URL is >>>>> https://datatracker.ietf.org/public/meeting_agenda_html.cgi?=20 >>>>> meeting_num=3D65. >>>>> At the top of that, there is a link to the "(Text Format of the >>>>> Agenda)", which gets you to >>>>> https://datatracker.ietf.org/public/meeting_agenda_text.cgi?=20 >>>>> meeting_num=3D65. >>>>> If I download that, the file is named =20 >>>>> meeting_agenda_text.cgi.html, and >>>>> is indeed in html format. Near as I can tell the difference =20 >>>>> between the >>>>> "text" format and the "html" format is that the "text" format has = >>>>> URLs >>>>> for the working group charters but not the agendas. >>>>> >>>>> Am I missing something? Any idea why the "text" file would be in ht= ml >>>>> format? >>>>> >>>>> _______________________________________________ >>>>> Tools-discuss mailing list >>>>> Tools-discuss@ietf.org >>>>> https://www1.ietf.org/mailman/listinfo/tools-discuss >=20 >> _______________________________________________ >> Tools-discuss mailing list >> Tools-discuss@ietf.org >> https://www1.ietf.org/mailman/listinfo/tools-discuss >=20 >=20 >=20 >=20 > -----------------------------------------------------------------------= - >=20 > _______________________________________________ > Tools-discuss mailing list > Tools-discuss@ietf.org > https://www1.ietf.org/mailman/listinfo/tools-discuss --------------enig2B9D3884B541ABF2BB17B62E Content-Type: application/pgp-signature; name="signature.asc" Content-Description: OpenPGP digital signature Content-Disposition: attachment; filename="signature.asc" -----BEGIN PGP SIGNATURE----- iD8DBQFEHxHPeVhrtTJkXCMRAlxxAJ4wuh6uhl3yX7AIWNuFIcAsbxM3iQCg3sge VVCGNFsi0W/kA88aCAGyXVE= =Rwgo -----END PGP SIGNATURE----- --------------enig2B9D3884B541ABF2BB17B62E-- --===============1766031520== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ Tools-discuss mailing list Tools-discuss@ietf.org https://www1.ietf.org/mailman/listinfo/tools-discuss --===============1766031520==-- From tools-discuss-bounces@ietf.org Mon Mar 20 15:43:17 2006 Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1FLRDh-00041u-Ac; Mon, 20 Mar 2006 15:43:17 -0500 Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1FLRDg-000419-Iu for tools-discuss@ietf.org; Mon, 20 Mar 2006 15:43:16 -0500 Received: from sj-iport-2-in.cisco.com ([171.71.176.71] helo=sj-iport-2.cisco.com) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1FLRDg-0002Fh-5v for tools-discuss@ietf.org; Mon, 20 Mar 2006 15:43:16 -0500 Received: from sj-core-5.cisco.com ([171.71.177.238]) by sj-iport-2.cisco.com with ESMTP; 20 Mar 2006 12:43:16 -0800 X-IronPort-AV: i="4.03,112,1141632000"; d="scan'208"; a="316369182:sNHT28085612" Received: from imail.cisco.com (sjc12-sbr-sw3-3f5.cisco.com [172.19.96.182]) by sj-core-5.cisco.com (8.12.10/8.12.6) with ESMTP id k2KKhF7T026297; Mon, 20 Mar 2006 12:43:15 -0800 (PST) Received: from [204.96.114.235] (sjc-vpn2-151.cisco.com [10.21.112.151]) by imail.cisco.com (8.12.11/8.12.10) with ESMTP id k2KKiIMM013180; Mon, 20 Mar 2006 12:44:18 -0800 In-Reply-To: <441F11CF.7080603@levkowetz.com> References: <6C2E5AA5-8DF2-4DDF-A08C-9641A9742013@cisco.com> <441B4043.40400@isi.edu> <6D8C0E2E-8184-4F1C-927F-859452179E8A@cisco.com> <441B5D92.6080607@levkowetz.com> <441F11CF.7080603@levkowetz.com> Mime-Version: 1.0 (Apple Message framework v746.3) Content-Type: text/plain; charset=US-ASCII; delsp=yes; format=flowed Message-Id: Content-Transfer-Encoding: 7bit From: Fred Baker Subject: Re: [Tools-discuss] Text Format of the Agenda Date: Mon, 20 Mar 2006 14:43:13 -0600 To: Henrik Levkowetz X-Mailer: Apple Mail (2.746.3) DKIM-Signature: a=rsa-sha1; q=dns; l=3952; t=1142887459; x=1143319659; c=relaxed/simple; s=nebraska; h=Subject:From:Date:Content-Type:Content-Transfer-Encoding:Mime-Version; d=cisco.com; i=fred@cisco.com; z=From:Fred=20Baker=20 |Subject:Re=3A=20[Tools-discuss]=20Text=20Format=20of=20the=20Agenda |To:Henrik=20Levkowetz=20; X=v=3Dmtcc.com=3B=20h=3D6WSDeMAWpSFdIfmEG/BxNLbBvmk=3D; b=nDdRhfoe1Iir8eLAKWgof+MszO3f+JC+sM63GE4PElC4FfhTWf3cANUxPvW7+u8TczNAlxt0 FzMKvBtPFOV3OGfkHLtKqxXUnn1xgzMscdkhYmkweM4B29oiCaITXdZ+Kv5dPekBOy4xF1e9a8d lGj6x81SD+JuVuHq0dmYkfM8=; Authentication-Results: imail.cisco.com; header.From=fred@cisco.com; dkim=pass ( message from cisco.com verified; ); X-Spam-Score: 0.0 (/) X-Scan-Signature: 5ebbf074524e58e662bc8209a6235027 Cc: tools-discuss@ietf.org, Joe Touch X-BeenThere: tools-discuss@ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: IETF Tools Discussion List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: tools-discuss-bounces@ietf.org thanks much On Mar 20, 2006, at 2:34 PM, Henrik Levkowetz wrote: > Hi Fred (and all others on the list :) > > I now have a first version of this in place. There's a new link in > the > right-hand menu column of the WG and Agenda pages on > tools.ietf.org, e.g., > http://www1.tools.ietf.org/agenda/65/ > which reads "Calendar" and currently points to > http://www1.tools.ietf.org/agenda/65/ics/ > > If you follow this, you'll get a version of the agenda which has a > check- > box in front of each session, letting you select which sessions to > include > in a calendar file. Submitting this will return a page with a link to > an iCalendar file which you can download or subscribe to. > > > Henrik > > > on 2006-03-17 19:08 Henrik Levkowetz said the following: >> Hi Fred, >> >> on 2006-03-18 00:26 Fred Baker said the following: >>> I do the same (generate .ics from text), but start from TEXT and >>> don't particularly want the markup stuff. I'm going to have to edit >>> the TEXT format back to TEXT before feeding it into my TEXT tool. >>> When I see something that is marked TEXT, I don't especially expect >>> to find HTML -= especially when for the previous month the page has >>> been in flat ASCII. I expect to get TEXT. >>> >>> What's the chance of getting a TEXT file when I download the file >>> marked "TEXT file"? >>> >>> Wouldn't it be nice if we could simply get an RFC 2445-compliant >>> calendar up there? Like, maybe we could subscribe to it? >>> >>> In my dream world, I guess I would like to have a web page that I >>> could go to, click on radio dials next to the things I care about, >>> and get downloaded to me an RFC 2445 calendar that I can import. >> >> I'm working on this. Maybe by Sunday. >> >> >> Henrik >> >> >>> On Mar 17, 2006, at 3:03 PM, Joe Touch wrote: >>> >>> That might be for some of us, including Eliot Lear, Lars Eggert, and >>> myself, who use the text as input to software to generate Calendar >>> entries (Eliod does .ics; I convert them to .vcs, and Lars had a >>> native >>> .vcs one too). >>> >>> I.e., the text is de-HTML'd, but still includes body. It would have >>> been >>> equally useful to have provided an XML of the calendar which >>> could be >>> converted into whatever desired format (HTML, ics, vcs, etc.), but >>> that >>> may be a while off. >>> >>> Joe >>> >>> Fred Baker wrote: >>>>>> If you go to http://www.ietf.org/meetings/IETF-65.html and >>>>>> click on >>>>>> "Meeting Agenda", you get a web page whose URL is >>>>>> https://datatracker.ietf.org/public/meeting_agenda_html.cgi? >>>>>> meeting_num=65. >>>>>> At the top of that, there is a link to the "(Text Format of the >>>>>> Agenda)", which gets you to >>>>>> https://datatracker.ietf.org/public/meeting_agenda_text.cgi? >>>>>> meeting_num=65. >>>>>> If I download that, the file is named >>>>>> meeting_agenda_text.cgi.html, and >>>>>> is indeed in html format. Near as I can tell the difference >>>>>> between the >>>>>> "text" format and the "html" format is that the "text" format has >>>>>> URLs >>>>>> for the working group charters but not the agendas. >>>>>> >>>>>> Am I missing something? Any idea why the "text" file would be >>>>>> in html >>>>>> format? >>>>>> >>>>>> _______________________________________________ >>>>>> Tools-discuss mailing list >>>>>> Tools-discuss@ietf.org >>>>>> https://www1.ietf.org/mailman/listinfo/tools-discuss >> >>> _______________________________________________ >>> Tools-discuss mailing list >>> Tools-discuss@ietf.org >>> https://www1.ietf.org/mailman/listinfo/tools-discuss >> >> >> >> >> --------------------------------------------------------------------- >> --- >> >> _______________________________________________ >> Tools-discuss mailing list >> Tools-discuss@ietf.org >> https://www1.ietf.org/mailman/listinfo/tools-discuss > _______________________________________________ Tools-discuss mailing list Tools-discuss@ietf.org https://www1.ietf.org/mailman/listinfo/tools-discuss From tools-discuss-bounces@ietf.org Wed Mar 22 15:47:06 2006 Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1FMAET-0001Vj-UC; Wed, 22 Mar 2006 15:47:05 -0500 Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1FMAET-0001Ve-DG for tools-discuss@ietf.org; Wed, 22 Mar 2006 15:47:05 -0500 Received: from shaman.nostrum.com ([72.232.15.10] helo=nostrum.com) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1FMAES-0001NK-2g for tools-discuss@ietf.org; Wed, 22 Mar 2006 15:47:05 -0500 Received: from [130.129.129.164] (DHCP-Wireless-129-164.ietf65.org [130.129.129.164]) (authenticated bits=0) by nostrum.com (8.13.4/8.13.4) with ESMTP id k2MKl0Lo025213 (version=TLSv1/SSLv3 cipher=RC4-SHA bits=128 verify=NO) for ; Wed, 22 Mar 2006 14:47:01 -0600 (CST) (envelope-from rjsparks@nostrum.com) Mime-Version: 1.0 (Apple Message framework v746.2) References: Content-Type: text/plain; charset=US-ASCII; delsp=yes; format=flowed Message-Id: <92164A50-1DAC-4C90-A1F8-CFA3631AB916@nostrum.com> Content-Transfer-Encoding: 7bit From: Robert Sparks Date: Wed, 22 Mar 2006 14:47:06 -0600 To: tools-discuss@ietf.org X-Mailer: Apple Mail (2.746.2) Received-SPF: pass (nostrum.com: 130.129.129.164 is authenticated by a trusted mechanism) X-Spam-Score: 0.0 (/) X-Scan-Signature: 7aafa0432175920a4b3e118e16c5cb64 Subject: [Tools-discuss] 2119 keyword counting/enumeration X-BeenThere: tools-discuss@ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: IETF Tools Discussion List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: tools-discuss-bounces@ietf.org Paul suggested I send these scripts to this list. I've found them useful - maybe others will too. count_reqs run over any document counts the number of occurrences of "MUST", "MAY", etc. enum_reqs pulls out the sentence each of those occurs in, highlighting the instance, and giving it a label you can refer to. These are perl. You can retrieve them from: http://www.nostrum.com/~rjsparks/count_reqs http://www.nostrum.com/~rjsparks/enum_reqs RjS ------------- p.s. Here's some sample output: Robert-Sparks-Computer:~/ietf/rfc rjsparks$ count_reqs rfc2409.txt 14 MUST NOT 0 NOT REQUIRED 2 SHOULD NOT 0 NOT RECOMMENDED 49 MUST 1 REQUIRED 8 SHOULD 0 RECOMMENDED 15 MAY 0 OPTIONAL Robert-Sparks-Computer:~/ietf/rfc rjsparks$ enum_reqs rfc2409.txt MUST NOT Requirements: MN-1: Keywords "MUST", "**MUST NOT**", "REQUIRED", "SHOULD", "SHOULD NOT" and "MAY" that appear in this document are to be interpreted as described in [Bra97]. MN-2: For PFS to exist the key used to protect transmission of data **MUST NOT** be used to derive any additional keys, and if the key used to protect transmission of data was derived from some other keying material, that material MUST NOT be used to derive any more keys. MN-3: For PFS to exist the key used to protect transmission of data MUST NOT be used to derive any additional keys, and if the key used to protect transmission of data was derived from some other keying material, that material **MUST NOT** be used to derive any more keys. (and so on...) _______________________________________________ Tools-discuss mailing list Tools-discuss@ietf.org https://www1.ietf.org/mailman/listinfo/tools-discuss From tools-discuss-bounces@ietf.org Sat Mar 25 16:28:01 2006 Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1FNGIi-0001gc-4n; Sat, 25 Mar 2006 16:28:00 -0500 Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1FM6EF-0006b7-7g for tools-discuss@ietf.org; Wed, 22 Mar 2006 11:30:35 -0500 Received: from radmail2.rad.co.il ([80.74.100.136] helo=antivir1.rad.co.il) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1FM6EB-0006fl-Mb for tools-discuss@ietf.org; Wed, 22 Mar 2006 11:30:35 -0500 Received: from antivir1.rad.co.il (localhost [127.0.0.1]) by antivir1.rad.co.il (8.12.10/8.12.10) with ESMTP id k2MGPuxH024629 for ; Wed, 22 Mar 2006 18:25:57 +0200 (IST) Received: from exrad2.ad.rad.co.il (exrad2 [192.114.24.112]) by antivir1.rad.co.il (8.12.10/8.12.10) with ESMTP id k2MGPuPX024626; Wed, 22 Mar 2006 18:25:56 +0200 (IST) X-MIMEOLE: Produced By Microsoft Exchange V6.5.7226.0 Content-class: urn:content-classes:message MIME-Version: 1.0 Date: Wed, 22 Mar 2006 18:30:28 +0200 Message-ID: <27A0F290348F8E45AEF79889DDE65A5206589E9B@exrad2.ad.rad.co.il> X-MS-Has-Attach: X-MS-TNEF-Correlator: Thread-Topic: liaison statement tracker Thread-Index: AcZNze3+UBrpAb4aRYWyvWUnFJvpng== From: "Yaakov Stein" To: X-Spam-Score: 0.0 (/) X-Scan-Signature: 057ebe9b96adec30a7efb2aeda4c26a4 X-Mailman-Approved-At: Sat, 25 Mar 2006 16:27:58 -0500 Cc: Yaakov Stein , Stewart Bryant Subject: [Tools-discuss] liaison statement tracker X-BeenThere: tools-discuss@ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: IETF Tools Discussion List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Content-Type: multipart/mixed; boundary="===============1003549964==" Errors-To: tools-discuss-bounces@ietf.org This is a multi-part message in MIME format. --===============1003549964== Content-class: urn:content-classes:message Content-Type: multipart/alternative; boundary="----_=_NextPart_001_01C64DCD.EE27AD7F" This is a multi-part message in MIME format. ------_=_NextPart_001_01C64DCD.EE27AD7F Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable Hi all,=20 =20 Stewart brought this issue up at the general area session this morning. =20 We really do need some sort of tracking tool to ensure that incoming liasons from other SDOs get to the proper people=20 (e.g. ADs, WG chairs, official liaison to and from that SDO)=20 and are properly handled.=20 =20 Similarly, it would be good for outgoing liaisons to be consistently handled,=20 and for a tracker to show when such a liaison was sent and to whom. =20 It goes without saying that links to the liaison text would be useful. =20 A web-based tool indexed by liaison statement,=20 similar to the ID tracker, would probably do it. =20 Y(J)S =20 =20 ------_=_NextPart_001_01C64DCD.EE27AD7F Content-Type: text/html; charset="us-ascii" Content-Transfer-Encoding: quoted-printable
Hi = all,=20
 
Stewart brought this=20 issue up at the general area session this morning.
; Wed, 22 Mar 2006 18:25:57 +0200 (IST) Received: from exrad2.ad.rad.co.il (exrad2 [192.114.24.112]) by antivir1.rad.co.il (8.12.10/8.12.10) with ESMTP id k2MGPuPX024626; Wed, 22 Mar 2006 18:25:56 +0200 (IST) X-MIMEOLE: Produced By Microsoft Exchange V6.5.7226.0 Content-class: urn:content-classes:message MIME-Version: 1.0 Date: Wed, 22 Mar 2006 18:30:28 +0200 Message-ID: <27A0F290348F8E45AEF79889DDE65A5206589E9B@exrad2.ad.rad.co.il> X-MS-Has-Attach: X-MS-TNEF-Correlator: Thread-Topic: liaison statement tracker Thread-Index: AcZNze3+UBrpAb4aRYWyvWUnFJvpng== From: "Yaakov Stein" To: X-Spam-Score: 0.0 (/) X-Scan-Signature: 057ebe9b96adec30a7efb2aeda4c26a4 X-Mailman-Approved-At: Sat, 25 Mar 2006 16:27:58 -0500 Cc: Yaakov Stein , Stewart Bryant Subject: [Tools-discuss] liaison statement tracker X-BeenThere: tools-discuss@ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: IETF Tools Discussion List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Content-Type: multipart/mixed; boundary="===============1003549964==" Errors-To: tools-discuss-bounces@ietf.org This is a multi-part message in MIME format. --===============1003549964== Content-class: urn:content-classes:message Content-Type: multipart/alternative; boundary="----_=_NextPart_001_01C64DCD.EE27AD7F" This is a multi-part message in MIME format. ------_=_NextPart_001_01C64DCD.EE27AD7F Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable Hi all,=20 =20 Stewart brought this issue up at the general area session this morning. =20 We really do need some sort of tracking tool to ensure that incoming liasons from other SDOs get to the proper people=20 (e.g. ADs, WG chairs, official liaison to and from that SDO)=20 and are properly handled.=20 =20 Similarly, it would be good for outgoing liaisons to be consistently handled,=20 and for a tracker to show when such a liaison was sent and to whom. =20 It goes without saying that links to the liaison text would be useful. =20 A web-based tool indexed by liaison statement,=20 similar to the ID tracker, would probably do it. =20 Y(J)S =20 =20 ------_=_NextPart_001_01C64DCD.EE27AD7F Content-Type: text/html; charset="us-ascii" Content-Transfer-Encoding: quoted-printable
Hi = all,=20
 
Stewart brought this=20 issue up at the general area session this morning.
 
We = really do need=20 some sort of tracking tool to ensure that incoming
liasons from other=20 SDOs get to the proper people
(e.g. = ADs, WG=20 chairs, official liaison to and from that SDO)=20
and are properly = handled.=20
 
Similarly, it would=20 be good for outgoing liaisons to be consistently handled, =
and = for a tracker to=20 show when such a liaison was sent and to whom.
 
It = goes without=20 saying that links to the liaison text would be = useful.
 
A = web-based tool=20 indexed by liaison statement,
similar to the=20 ID tracker,=20 would probably do it.
 
Y(J)S
 
 
------_=_NextPart_001_01C64DCD.EE27AD7F-- --===============1003549964== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ Tools-discuss mailing list Tools-discuss@ietf.org https://www1.ietf.org/mailman/listinfo/tools-discuss --===============1003549964==-- From tools-discuss-bounces@ietf.org Sat Mar 25 16:28:01 2006 Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1FNGIi-0001gK-0o; Sat, 25 Mar 2006 16:28:00 -0500 Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1FLxJC-0000Zv-Qv for tools-discuss@ietf.org; Wed, 22 Mar 2006 01:59:06 -0500 Received: from smtpout.mac.com ([17.250.248.45]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1FLxJB-000103-FS for tools-discuss@ietf.org; Wed, 22 Mar 2006 01:59:06 -0500 Received: from mac.com (smtpin08-en2 [10.13.10.153]) by smtpout.mac.com (Xserve/8.12.11/smtpout11/MantshX 4.0) with ESMTP id k2M6x4Yu007371 for ; Tue, 21 Mar 2006 22:59:04 -0800 (PST) Received: from [192.168.201.100] (c-71-198-181-161.hsd1.ca.comcast.net [71.198.181.161]) (authenticated bits=0) by mac.com (Xserve/smtpin08/MantshX 4.0) with ESMTP id k2M6x3EU028108 for ; Tue, 21 Mar 2006 22:59:04 -0800 (PST) Mime-Version: 1.0 (Apple Message framework v746.3) References: <17EB8D95-2380-41C7-B0AF-AA69F0483680@musecurity.com> Content-Type: text/plain; charset=US-AS=3DArial size=3D2> 
We = really do need=20 some sort of tracking tool to ensure that incoming
liasons from other=20 SDOs get to the proper people
(e.g. = ADs, WG=20 chairs, official liaison to and from that SDO)=20
and are properly = handled.=20
 
Similarly, it would=20 be good for outgoing liaisons to be consistently handled, =
and = for a tracker to=20 show when such a liaison was sent and to whom.
 
It = goes without=20 saying that links to the liaison text would be = useful.
 
A = web-based tool=20 indexed by liaison statement,
similar to the=20 ID tracker,=20 would probably do it.
 
Y(J)S
 
 
------_=_NextPart_001_01C64DCD.EE27AD7F-- --===============1003549964== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ Tools-discuss mailing list Tools-discuss@ietf.org https://www1.ietf.org/mailman/listinfo/tools-discuss --===============1003549964==-- From tools-discuss-bounces@ietf.org Sat Mar 25 16:28:01 2006 Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1FNGIi-0001gK-0o; Sat, 25 Mar 2006 16:28:00 -0500 Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1FLxJC-0000Zv-Qv for tools-discuss@ietf.org; Wed, 22 Mar 2006 01:59:06 -0500 Received: from smtpout.mac.com ([17.250.248.45]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1FLxJB-000103-FS for tools-discuss@ietf.org; Wed, 22 Mar 2006 01:59:06 -0500 Received: from mac.com (smtpin08-en2 [10.13.10.153]) by smtpout.mac.com (Xserve/8.12.11/smtpout11/MantshX 4.0) with ESMTP id k2M6x4Yu007371 for ; Tue, 21 Mar 2006 22:59:04 -0800 (PST) Received: from [192.168.201.100] (c-71-198-181-161.hsd1.ca.comcast.net [71.198.181.161]) (authenticated bits=0) by mac.com (Xserve/smtpin08/MantshX 4.0) with ESMTP id k2M6x3EU028108 for ; Tue, 21 Mar 2006 22:59:04 -0800 (PST) Mime-Version: 1.0 (Apple Message framework v746.3) References: <17EB8D95-2380-41C7-B0AF-AA69F0483680@musecurity.com> Content-Type: text/plain; charset=US-ASCII; format=flowed Message-Id: Content-Transfer-Encoding: 7bit From: Thomas Maufer Date: Tue, 21 Mar 2006 22:59:02 -0800 To: tools-discuss@ietf.org X-Mailer: Apple Mail (2.746.3) X-Spam-Score: 0.0 (/) X-Scan-Signature: 6d62ab47271805379d7172ee693a45db X-Mailman-Approved-At: Sat, 25 Mar 2006 16:27:58 -0500 Subject: [Tools-discuss] please consider adding an RFC dependencies tool... X-BeenThere: tools-discuss@ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: IETF Tools Discussion List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: tools-discuss-bounces@ietf.org ...like your drafts dependencies tool. Thanks, Tom _______________________________________________ Tools-discuss mailing list Tools-discuss@ietf.org https://www1.ietf.org/mailman/listinfo/tools-discuss CII; format=flowed Message-Id: Content-Transfer-Encoding: 7bit From: Thomas Maufer Date: Tue, 21 Mar 2006 22:59:02 -0800 To: tools-discuss@ietf.org X-Mailer: Apple Mail (2.746.3) X-Spam-Score: 0.0 (/) X-Scan-Signature: 6d62ab47271805379d7172ee693a45db X-Mailman-Approved-At: Sat, 25 Mar 2006 16:27:58 -0500 Subject: [Tools-discuss] please consider adding an RFC dependencies tool... X-BeenThere: tools-discuss@ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: IETF Tools Discussion List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: tools-discuss-bounces@ietf.org ...like your drafts dependencies tool. Thanks, Tom _______________________________________________ Tools-discuss mailing list Tools-discuss@ietf.org https://www1.ietf.org/mailman/listinfo/tools-discuss From tools-discuss-bounces@ietf.org Mon Mar 27 04:19:31 2006 Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1FNnsp-0005Jz-5j; Mon, 27 Mar 2006 04:19:31 -0500 Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1FNnso-0005Ju-6a for tools-discuss@ietf.org; Mon, 27 Mar 2006 04:19:30 -0500 Received: from mtagate4.de.ibm.com ([195.212.29.153]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1FNnsm-0004Eu-OY for tools-discuss@ietf.org; Mon, 27 Mar 2006 04:19:30 -0500 Received: from d12nrmr1607.megacenter.de.ibm.com (d12nrmr1607.megacenter.de.ibm.com [9.149.167.49]) by mtagate4.de.ibm.com (8.13.6/8.13.6) with ESMTP id k2R9JR3c107344 for ; Mon, 27 Mar 2006 09:19:27 GMT Received: from d12av01.megacenter.de.ibm.com (d12av01.megacenter.de.ibm.com [9.149.165.212]) by d12nrmr1607.megacenter.de.ibm.com (8.12.10/NCO/VER6.8) with ESMTP id k2R9K49V245320 for ; Mon, 27 Mar 2006 11:20:04 +0200 Received: from d12av01.megacenter.de.ibm.com (loopback [127.0.0.1]) by d12av01.megacenter.de.ibm.com (8.12.11/8.13.3) with ESMTP id k2R9JRRi008452 for ; Mon, 27 Mar 2006 11:19:27 +0200 Received: from sihl.zurich.ibm.com (sihl.zurich.ibm.com [9.4.16.232]) by d12av01.megacenter.de.ibm.com (8.12.11/8.12.11) with ESMTP id k2R9JQ7S008433; Mon, 27 Mar 2006 11:19:26 +0200 Received: from zurich.ibm.com (sig-9-146-220-165.de.ibm.com [9.146.220.165]) by sihl.zurich.ibm.com (AIX4.3/8.9.3p2/8.9.3) with ESMTP id LAA45168; Mon, 27 Mar 2006 11:19:25 +0200 Message-ID: <4427AE20.4060705@zurich.ibm.com> Date: Mon, 27 Mar 2006 11:19:28 +0200 From: Brian E Carpenter Organization: IBM User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.6) Gecko/20040113 X-Accept-Language: en, fr, de MIME-Version: 1.0 To: Yaakov Stein Subject: Re: [Tools-discuss] liaison statement tracker References: <27A0F290348F8E45AEF79889DDE65A5206589E9B@exrad2.ad.rad.co.il> In-Reply-To: <27A0F290348F8E45AEF79889DDE65A5206589E9B@exrad2.ad.rad.co.il> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-Spam-Score: 0.0 (/) X-Scan-Signature: 9ed51c9d1356100bce94f1ae4ec616a9 Cc: tools-discuss@ietf.org, Stewart Bryant X-BeenThere: tools-discuss@ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: IETF Tools Discussion List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: tools-discuss-bounces@ietf.org The liaison posting tool does have relevant features I think. If you look at recent statements such as https://datatracker.ietf.org/public/liaison_detail.cgi?detail_id=206 https://datatracker.ietf.org/public/liaison_detail.cgi?detail_id=199 you can see who they were cc'ed to. This doesn't apply to statements sent the old-fashioned way, by email, but that is something to be discouraged. Brian Yaakov Stein wrote: > Hi all, > > Stewart brought this issue up at the general area session this morning. > > We really do need some sort of tracking tool to ensure that incoming > liasons from other SDOs get to the proper people > (e.g. ADs, WG chairs, official liaison to and from that SDO) > and are properly handled. > > Similarly, it would be good for outgoing liaisons to be consistently > handled, > and for a tracker to show when such a liaison was sent and to whom. > > It goes without saying that links to the liaison text would be useful. > > A web-based tool indexed by liaison statement, > similar to the ID tracker, would probably do it. > > Y(J)S > > > > > > ------------------------------------------------------------------------ > > _______________________________________________ > Tools-discuss mailing list > Tools-discuss@ietf.org > https://www1.ietf.org/mailman/listinfo/tools-discuss _______________________________________________ Tools-discuss mailing list Tools-discuss@ietf.org https://www1.ietf.org/mailman/listinfo/tools-discuss From tools-discuss-bounces@ietf.org Thu Mar 30 06:53:41 2006 Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1FOvif-0000N1-23; Thu, 30 Mar 2006 06:53:41 -0500 Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1FOvid-0000Mw-MO for tools-discuss@ietf.org; Thu, 30 Mar 2006 06:53:39 -0500 Received: from radmail1.rad.co.il ([62.0.23.193] helo=antivir1.rad.co.il) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1FOvia-0007Wq-1l for tools-discuss@ietf.org; Thu, 30 Mar 2006 06:53:39 -0500 Received: from antivir1.rad.co.il (localhost [127.0.0.1]) by antivir1.rad.co.il (8.12.10/8.12.10) with ESMTP id k2UBmkxH012328 for ; Thu, 30 Mar 2006 13:48:51 +0200 (IST) Received: from exrad2.ad.rad.co.il (exrad2 [192.114.24.112]) by antivir1.rad.co.il (8.12.10/8.12.10) with ESMTP id k2UBmkPX012325; Thu, 30 Mar 2006 13:48:46 +0200 (IST) Content-class: urn:content-classes:message MIME-Version: 1.0 Subject: RE: [Tools-discuss] liaison statement tracker Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable X-MimeOLE: Produced By Microsoft Exchange V6.5.7226.0 Date: Thu, 30 Mar 2006 13:53:21 +0200 Message-ID: <27A0F290348F8E45AEF79889DDE65A5206824EFC@exrad2.ad.rad.co.il> X-MS-Has-Attach: X-MS-TNEF-Correlator: Thread-Topic: [Tools-discuss] liaison statement tracker Thread-Index: AcZRf44l7p89Z9EdTnGc4e+g+qOixQCcBqtQ From: "Yaakov Stein" To: "Brian E Carpenter" X-Spam-Score: 0.0 (/) X-Scan-Signature: 39bd8f8cbb76cae18b7e23f7cf6b2b9f Cc: tools-discuss@ietf.org, Stewart Bryant X-BeenThere: tools-discuss@ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: IETF Tools Discussion List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: tools-discuss-bounces@ietf.org Brian,=20 The two liaisons you linked are much better=20 than any of the ones I have seen to date, e.g.=20 https://datatracker.ietf.org/documents/LIAISON/file163.pdf https://datatracker.ietf.org/documents/LIAISON/file169.txt . It is not clear to me how the incoming statements were entered into the tracker. Does the other SDO enter them directly, or is there a shepherd at the IETF ? And is it sufficient to enter an outgoing liaison into the system, and then rely on the system to send the liaison to the intended recipients,=20 or is the entering for tracking only, and email needs to be sent separately? Y(J)S -----Original Message----- From: Brian E Carpenter [mailto:brc@zurich.ibm.com]=20 Sent: Monday, March 27, 2006 11:19 To: Yaakov Stein Cc: tools-discuss@ietf.org; Stewart Bryant Subject: Re: [Tools-discuss] liaison statement tracker The liaison posting tool does have relevant features I think. If you look at recent statements such as https://datatracker.ietf.org/public/liaison_detail.cgi?detail_id=3D206 https://datatracker.ietf.org/public/liaison_detail.cgi?detail_id=3D199 you can see who they were cc'ed to. This doesn't apply to statements sent the old-fashioned way, by email, but that is something to be discouraged. Brian _______________________________________________ Tools-discuss mailing list Tools-discuss@ietf.org https://www1.ietf.org/mailman/listinfo/tools-discuss From tools-discuss-bounces@ietf.org Thu Mar 30 20:22:36 2006 Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1FP8LQ-0007wT-Vu; Thu, 30 Mar 2006 20:22:32 -0500 Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1FP8LP-0007wL-Vx for tools-discuss@ietf.org; Thu, 30 Mar 2006 20:22:31 -0500 Received: from boreas.isi.edu ([128.9.160.161]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1FP8LN-0003au-KL for tools-discuss@ietf.org; Thu, 30 Mar 2006 20:22:31 -0500 Received: from [128.9.168.55] (upn.isi.edu [128.9.168.55]) by boreas.isi.edu (8.11.6p2+0917/8.11.2) with ESMTP id k2V1LkG04534; Thu, 30 Mar 2006 17:21:46 -0800 (PST) Message-ID: <442C83B1.2090708@isi.edu> Date: Thu, 30 Mar 2006 17:19:45 -0800 From: Joe Touch User-Agent: Thunderbird 1.5 (Windows/20051201) MIME-Version: 1.0 To: tools-discuss@ietf.org X-Enigmail-Version: 0.94.0.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit X-ISI-4-43-8-MailScanner: Found to be clean X-MailScanner-From: touch@isi.edu X-Spam-Score: 0.0 (/) X-Scan-Signature: e1e48a527f609d1be2bc8d8a70eb76cb Subject: [Tools-discuss] updated Word template and tools X-BeenThere: tools-discuss@ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: IETF Tools Discussion List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: tools-discuss-bounces@ietf.org -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hi, all, A new version of my Word template is now available; it includes: - updated boilerplate - IANA considerations section - bug fixes - updated post-processing script which is now also available as a web-form at http://www.isi.edu/touch/tools#rfc updated ID: http://www.isi.edu/touch/pubs/draft-touch-msword-template-v2.0-04.txt updated template: http://www.isi.edu/touch/tools/2-Word-v2.0.template.dot (this is always the most up-to-date one, if you just want to link it in) perl post-processor: http://www.isi.edu/touch/tools/2-Word-post-v2.0.pl (same thing - always updated) Feedback would be appreciated. I would also be interested in possibly providing a brief intro to the template and its use at the next IETF, if there would be interest. Joe -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.4 (MingW32) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iD8DBQFELIOxE5f5cImnZrsRAsP5AKDDLujQl0f9/GSfFb12h1+5LE4gZQCglxg6 GnBflCDfQP7nR0Eq0MzFrfc= =GVA3 -----END PGP SIGNATURE----- _______________________________________________ Tools-discuss mailing list Tools-discuss@ietf.org https://www1.ietf.org/mailman/listinfo/tools-discuss