From tools-discuss-bounces@ietf.org Tue Jul 03 09:52:27 2007 Return-path: Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1I5inr-0000rQ-3V; Tue, 03 Jul 2007 09:52:27 -0400 Received: from tools-discuss by megatron.ietf.org with local (Exim 4.43) id 1I5inl-0000af-RP for tools-discuss-confirm+ok@megatron.ietf.org; Tue, 03 Jul 2007 09:52:22 -0400 Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1I5inl-0000WJ-9t for tools-discuss@ietf.org; Tue, 03 Jul 2007 09:52:21 -0400 Received: from [2001:698:9:31:214:22ff:fe21:bb] (helo=merlot.tools.ietf.org) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1I5inE-0007Dq-94 for tools-discuss@ietf.org; Tue, 03 Jul 2007 09:52:21 -0400 Received: from localhost ([127.0.0.1] helo=marsanne.levkowetz.com ident=henrik) by merlot.tools.ietf.org with esmtp (Exim 4.67) (envelope-from ) id 1I5inD-0002xB-Pr; Tue, 03 Jul 2007 15:51:47 +0200 Message-ID: <468A5473.6040306@levkowetz.com> Date: Tue, 03 Jul 2007 15:51:47 +0200 From: Henrik Levkowetz User-Agent: Thunderbird 2.0.0.4 (Macintosh/20070604) MIME-Version: 1.0 To: Paul Aitken References: <468A517D.1020700@cisco.com> In-Reply-To: <468A517D.1020700@cisco.com> X-Enigmail-Version: 0.95.2 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit X-SA-Exim-Connect-IP: 127.0.0.1 X-SA-Exim-Rcpt-To: paitken@cisco.com, tools-discuss@ietf.org, henrik-sent@levkowetz.com X-SA-Exim-Mail-From: henrik@levkowetz.com X-SA-Exim-Scanned: No (on merlot.tools.ietf.org); SAEximRunCond expanded to false X-Spam-Score: -2.8 (--) X-Scan-Signature: 79899194edc4f33a41f49410777972f8 Cc: tools-discuss@ietf.org Subject: [Tools-discuss] Re: Idnits-2.04.09 feedback 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 Paul, On 2007-07-03 15:39 Paul Aitken said the following: > Hi. > > I just found a problem with a draft that's just about to become an RFC, > where it claims RFC 2119 compliance but uses the term "MAY NOT" which is > not defined in RFC 2119. > > This is leading to two different interpretations - one believing MAY NOT > == MUST NOT, the other believing MAY NOT == SHOULD NOT. > > Could idnits be updated to check for such errors? Thats sounds like a reasonable and helpful idea. I'll see if I can come up with something to address this. Henrik _______________________________________________ Tools-discuss mailing list Tools-discuss@ietf.org https://www1.ietf.org/mailman/listinfo/tools-discuss From tools-discuss-bounces@ietf.org Tue Jul 03 10:35:57 2007 Return-path: Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1I5jTx-0002Lj-7B; Tue, 03 Jul 2007 10:35:57 -0400 Received: from tools-discuss by megatron.ietf.org with local (Exim 4.43) id 1I5jTv-0002D7-F4 for tools-discuss-confirm+ok@megatron.ietf.org; Tue, 03 Jul 2007 10:35:55 -0400 Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1I5jTv-00029j-1B for tools-discuss@ietf.org; Tue, 03 Jul 2007 10:35:55 -0400 Received: from ug-out-1314.google.com ([66.249.92.174]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1I5jSr-0005AK-0x for tools-discuss@ietf.org; Tue, 03 Jul 2007 10:35:55 -0400 Received: by ug-out-1314.google.com with SMTP id u2so245746uge for ; Tue, 03 Jul 2007 07:34:48 -0700 (PDT) DKIM-Signature: a=rsa-sha1; c=relaxed/relaxed; d=gmail.com; s=beta; h=domainkey-signature:received:received:message-id:date:from:user-agent:mime-version:to:cc:subject:references:in-reply-to:content-type:content-transfer-encoding; b=XyAKG8066d6PBtrind+ut0/DWG1VTnAUt3kDhaopnJgYt5HBFjwjxObcmapcElfB2k/L6V9OIsZDuI2RKy3KjC5yiZAYYw6ouO2W2HL7XEHb8bliHfiBJbF59/X4vgnkttGSNltX6F06vTJgcY5P8hPou3Za/AVIwSTdMVWHNXI= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=beta; h=received:message-id:date:from:user-agent:mime-version:to:cc:subject:references:in-reply-to:content-type:content-transfer-encoding; b=YYkF5ViiqisypptBjPiEp7ZCnnJPCKEBgDeBPO544f6egeXN4vxrA6A7edhXUu2F5t1e3OrQovJMdNniMrNPe6iEID2EJ3dNFvP8lIkmZ2Nn5oLGvnBA3jluWOw1OBgkuCGG9NAeZmomsqDYLRCdjuaQ8oNRBwLfkLJTKHesdY8= Received: by 10.66.225.1 with SMTP id x1mr437336ugg.1183473277315; Tue, 03 Jul 2007 07:34:37 -0700 (PDT) Received: from ?10.10.50.1? ( [213.3.13.1]) by mx.google.com with ESMTP id i57sm2562939uga.2007.07.03.07.34.35 (version=SSLv3 cipher=RC4-MD5); Tue, 03 Jul 2007 07:34:36 -0700 (PDT) Message-ID: <468A5E7D.6040601@gmail.com> Date: Tue, 03 Jul 2007 16:34:37 +0200 From: Brian E Carpenter User-Agent: Thunderbird 1.5.0.12 (Windows/20070509) MIME-Version: 1.0 To: Henrik Levkowetz Subject: Re: [Tools-discuss] Re: Idnits-2.04.09 feedback References: <468A517D.1020700@cisco.com> <468A5473.6040306@levkowetz.com> In-Reply-To: <468A5473.6040306@levkowetz.com> Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit X-Spam-Score: 0.0 (/) X-Scan-Signature: 0bc60ec82efc80c84b8d02f4b0e4de22 Cc: Paul Aitken , 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 On 2007-07-03 15:51, Henrik Levkowetz wrote: > Hi Paul, > > On 2007-07-03 15:39 Paul Aitken said the following: >> Hi. >> >> I just found a problem with a draft that's just about to become an RFC, >> where it claims RFC 2119 compliance but uses the term "MAY NOT" which is >> not defined in RFC 2119. >> >> This is leading to two different interpretations - one believing MAY NOT >> == MUST NOT, the other believing MAY NOT == SHOULD NOT. By the way, the meaning is very clear in English, as in "You MAY NOT have another ice cream." But I think it is to avoid this argument that the phrase is not present in 2119. >> >> Could idnits be updated to check for such errors? > > Thats sounds like a reasonable and helpful idea. I'll see if I can come > up with something to address this. You do have one little twist to watch out for. 2119 defines "NOT RECOMMENDED" but the recommended boilerplate fails to include it. So "NOT RECOMMENDED" is allowed. Brian _______________________________________________ Tools-discuss mailing list Tools-discuss@ietf.org https://www1.ietf.org/mailman/listinfo/tools-discuss From tools-discuss-bounces@ietf.org Tue Jul 03 10:53:29 2007 Return-path: Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1I5jkv-0004op-08; Tue, 03 Jul 2007 10:53:29 -0400 Received: from tools-discuss by megatron.ietf.org with local (Exim 4.43) id 1I5jku-0004ok-2v for tools-discuss-confirm+ok@megatron.ietf.org; Tue, 03 Jul 2007 10:53:28 -0400 Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1I5jkt-0004oc-PV for tools-discuss@ietf.org; Tue, 03 Jul 2007 10:53:27 -0400 Received: from [2001:698:9:31:214:22ff:fe21:bb] (helo=merlot.tools.ietf.org) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1I5jkH-0001ey-KQ for tools-discuss@ietf.org; Tue, 03 Jul 2007 10:53:27 -0400 Received: from localhost ([127.0.0.1] helo=marsanne.levkowetz.com ident=henrik) by merlot.tools.ietf.org with esmtp (Exim 4.67) (envelope-from ) id 1I5jkG-0001yu-2E; Tue, 03 Jul 2007 16:52:48 +0200 Message-ID: <468A62BF.3090601@levkowetz.com> Date: Tue, 03 Jul 2007 16:52:47 +0200 From: Henrik Levkowetz User-Agent: Thunderbird 2.0.0.4 (Macintosh/20070604) MIME-Version: 1.0 To: Brian E Carpenter Subject: Re: [Tools-discuss] Re: Idnits-2.04.09 feedback References: <468A517D.1020700@cisco.com> <468A5473.6040306@levkowetz.com> <468A5E7D.6040601@gmail.com> In-Reply-To: <468A5E7D.6040601@gmail.com> X-Enigmail-Version: 0.95.2 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit X-SA-Exim-Connect-IP: 127.0.0.1 X-SA-Exim-Rcpt-To: brian.e.carpenter@gmail.com, paitken@cisco.com, tools-discuss@ietf.org, henrik-sent@levkowetz.com X-SA-Exim-Mail-From: henrik@levkowetz.com X-SA-Exim-Scanned: No (on merlot.tools.ietf.org); SAEximRunCond expanded to false X-Spam-Score: -2.8 (--) X-Scan-Signature: 856eb5f76e7a34990d1d457d8e8e5b7f Cc: Paul Aitken , 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 On 2007-07-03 16:34 Brian E Carpenter said the following: ... > You do have one little twist to watch out for. 2119 defines "NOT RECOMMENDED" > but the recommended boilerplate fails to include it. So "NOT RECOMMENDED" > is allowed. Good point. Idnits actually accepts a variation of the recommended boilerplate which includes "NOT RECOMMENDED", for this reason. I'm thinking a bit now about what kind of algorithm to use in order to catch both "MAY NOT" and similar phrases while accepting those which are defined in 2119. Henrik _______________________________________________ Tools-discuss mailing list Tools-discuss@ietf.org https://www1.ietf.org/mailman/listinfo/tools-discuss From tools-discuss-bounces@ietf.org Tue Jul 03 22:17:13 2007 Return-path: Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1I5uQa-00020I-Jw; Tue, 03 Jul 2007 22:17:12 -0400 Received: from tools-discuss by megatron.ietf.org with local (Exim 4.43) id 1I5uQZ-00020A-Ag for tools-discuss-confirm+ok@megatron.ietf.org; Tue, 03 Jul 2007 22:17:11 -0400 Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1I5uQY-0001zz-OZ for tools-discuss@ietf.org; Tue, 03 Jul 2007 22:17:10 -0400 Received: from vapor.isi.edu ([128.9.64.64]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1I5uQC-0001Dt-B7 for tools-discuss@ietf.org; Tue, 03 Jul 2007 22:17:10 -0400 Received: from [192.168.1.45] (pool-72-81-85-53.phlapa.east.verizon.net [72.81.85.53]) by vapor.isi.edu (8.13.8/8.13.8) with ESMTP id l642GR0Q010940; Tue, 3 Jul 2007 19:16:28 -0700 (PDT) Message-ID: <468B02F9.1080005@isi.edu> Date: Tue, 03 Jul 2007 19:16:25 -0700 From: Joe Touch User-Agent: Thunderbird 2.0.0.4 (Windows/20070604) MIME-Version: 1.0 To: Brian E Carpenter Subject: Re: [Tools-discuss] Re: Idnits-2.04.09 feedback References: <468A517D.1020700@cisco.com> <468A5473.6040306@levkowetz.com> <468A5E7D.6040601@gmail.com> In-Reply-To: <468A5E7D.6040601@gmail.com> X-Enigmail-Version: 0.95.1 X-ISI-4-43-8-MailScanner: Found to be clean X-MailScanner-From: touch@isi.edu X-Spam-Score: 0.0 (/) X-Scan-Signature: 8b431ad66d60be2d47c7bfeb879db82c Cc: Henrik Levkowetz , tools-discuss@ietf.org, Paul Aitken 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="===============0073582078==" Errors-To: tools-discuss-bounces@ietf.org This is an OpenPGP/MIME signed message (RFC 2440 and 3156) --===============0073582078== Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="------------enigE9F64758C499027AA753E4DF" This is an OpenPGP/MIME signed message (RFC 2440 and 3156) --------------enigE9F64758C499027AA753E4DF Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Brian E Carpenter wrote: > On 2007-07-03 15:51, Henrik Levkowetz wrote: >> Hi Paul, >> >> On 2007-07-03 15:39 Paul Aitken said the following: >>> Hi. >>> >>> I just found a problem with a draft that's just about to become an >>> RFC, where it claims RFC 2119 compliance but uses the term "MAY NOT" >>> which is not defined in RFC 2119. >>> >>> This is leading to two different interpretations - one believing MAY >>> NOT =3D=3D MUST NOT, the other believing MAY NOT =3D=3D SHOULD NOT. >=20 > By the way, the meaning is very clear in English, as in > "You MAY NOT have another ice cream." The safety harness MAY NOT work. Which also means it may. It's not so clear. When it's a imperative, it may be unambiguous as equivalent to MUST NOT, but imperatives aren't a common part of written English except as narrative. When used in a declarative (as I have used it), it often means SHOULD NOT. Joe --------------enigE9F64758C499027AA753E4DF Content-Type: application/pgp-signature; name="signature.asc" Content-Description: OpenPGP digital signature Content-Disposition: attachment; filename="signature.asc" -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.3 (MingW32) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iD8DBQFGiwL6E5f5cImnZrsRAqfZAJsHQcpankJeBgsl1VbvNX9ur4PabACg+nnj xjTmpqBZcnp5AmB/joOtVYg= =smaG -----END PGP SIGNATURE----- --------------enigE9F64758C499027AA753E4DF-- --===============0073582078== 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 --===============0073582078==-- From tools-discuss-bounces@ietf.org Wed Jul 04 03:46:04 2007 Return-path: Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1I5zYm-0004Mt-UP; Wed, 04 Jul 2007 03:46:00 -0400 Received: from tools-discuss by megatron.ietf.org with local (Exim 4.43) id 1I5zYm-0004KW-F5 for tools-discuss-confirm+ok@megatron.ietf.org; Wed, 04 Jul 2007 03:46:00 -0400 Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1I5zYm-0004KO-3W for tools-discuss@ietf.org; Wed, 04 Jul 2007 03:46:00 -0400 Received: from ug-out-1314.google.com ([66.249.92.173]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1I5zYi-0005Ly-Or for tools-discuss@ietf.org; Wed, 04 Jul 2007 03:46:00 -0400 Received: by ug-out-1314.google.com with SMTP id u2so691884uge for ; Wed, 04 Jul 2007 00:45:56 -0700 (PDT) DKIM-Signature: a=rsa-sha1; c=relaxed/relaxed; d=gmail.com; s=beta; h=domainkey-signature:received:received:message-id:date:from:user-agent:mime-version:to:subject:content-type:content-transfer-encoding; b=FHJ0bfJPcQRBQvdnkeGMGU5Sw/48Cg+AdLk4vEM3SVmfAOHxq68200yYxBC4VccOrNFrvTaktYGhl6Qz5cdhay+Q0keMyNXSCynjiRuJnk3JWZ42Q5kXQGvZSY8RB1nQllTrsqxqBjUKqCtCQlc/6PuLhms2qHNYRqotWhnFAYA= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=beta; h=received:message-id:date:from:user-agent:mime-version:to:subject:content-type:content-transfer-encoding; b=kYqjrdzQqoLyovR8mDMMDQzibkAAD0AnHmSNvzTprvoG3x3+vCmKKh4rchjw54nIQE2H5W00GlRGKNdOo1XfZQEu5egpsOwBMUlKE83l+T6odTzjXNKq9sWXgJ3+ZgTs8oK7KMfJUo4pFgRTqd9+/0O0V/PmLtuDUOzwj4eKugo= Received: by 10.67.95.3 with SMTP id x3mr985044ugl.1183535155877; Wed, 04 Jul 2007 00:45:55 -0700 (PDT) Received: from ?10.10.50.1? ( [213.3.13.1]) by mx.google.com with ESMTPS id x33sm262091ugc.2007.07.04.00.45.54 (version=SSLv3 cipher=RC4-MD5); Wed, 04 Jul 2007 00:45:55 -0700 (PDT) Message-ID: <468B502F.3050705@gmail.com> Date: Wed, 04 Jul 2007 09:45:51 +0200 From: Brian E Carpenter User-Agent: Thunderbird 1.5.0.12 (Windows/20070509) MIME-Version: 1.0 To: tools-discuss@ietf.org Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit X-Spam-Score: 0.0 (/) X-Scan-Signature: 7d33c50f3756db14428398e2bdedd581 Subject: [Tools-discuss] tools.ietf.org/id anomaly 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 http://tools.ietf.org/id/draft-ietf-mmusic-ice-16.txt http://tools.ietf.org/id/draft-ietf-mmusic-ice-1 http://tools.ietf.org/id/draft-ietf-mmusic-ice all work, but http://tools.ietf.org/id/draft-ietf-mmusic-ice-16 hits an error. I find this a bit disconcerting, since it doesn't seem to fail for other drafts draft-ietf-mmusic-ice-tcp also exists. I don't know if that's relevant Brian XML Parsing Error: xml declaration not at start of external entity Location: http://tools.ietf.org/id/draft-ietf-mmusic-ice-16 Line Number 2, Column 1: ^ _______________________________________________ Tools-discuss mailing list Tools-discuss@ietf.org https://www1.ietf.org/mailman/listinfo/tools-discuss From tools-discuss-bounces@ietf.org Wed Jul 04 06:01:41 2007 Return-path: Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1I61g5-0005hJ-Fe; Wed, 04 Jul 2007 06:01:41 -0400 Received: from tools-discuss by megatron.ietf.org with local (Exim 4.43) id 1I61g3-0005gT-Qx for tools-discuss-confirm+ok@megatron.ietf.org; Wed, 04 Jul 2007 06:01:39 -0400 Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1I61g3-0005gG-H7 for tools-discuss@ietf.org; Wed, 04 Jul 2007 06:01:39 -0400 Received: from [2001:698:9:31:214:22ff:fe21:bb] (helo=merlot.tools.ietf.org) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1I61g1-0002mb-K2 for tools-discuss@ietf.org; Wed, 04 Jul 2007 06:01:39 -0400 Received: from localhost ([127.0.0.1] helo=marsanne.levkowetz.com ident=henrik) by merlot.tools.ietf.org with esmtp (Exim 4.67) (envelope-from ) id 1I61g0-0008GW-Bu; Wed, 04 Jul 2007 12:01:36 +0200 Message-ID: <468B7000.6010805@levkowetz.com> Date: Wed, 04 Jul 2007 12:01:36 +0200 From: Henrik Levkowetz User-Agent: Thunderbird 2.0.0.4 (Macintosh/20070604) MIME-Version: 1.0 To: Brian E Carpenter Subject: Re: [Tools-discuss] tools.ietf.org/id anomaly References: <468B502F.3050705@gmail.com> In-Reply-To: <468B502F.3050705@gmail.com> X-Enigmail-Version: 0.95.2 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit X-SA-Exim-Connect-IP: 127.0.0.1 X-SA-Exim-Rcpt-To: brian.e.carpenter@gmail.com, tools-discuss@ietf.org, henrik-sent@levkowetz.com X-SA-Exim-Mail-From: henrik@levkowetz.com X-SA-Exim-Scanned: No (on merlot.tools.ietf.org); SAEximRunCond expanded to false X-Spam-Score: -2.8 (--) X-Scan-Signature: e5ba305d0e64821bf3d8bc5d3bb07228 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 Brian, On 2007-07-04 09:45 Brian E Carpenter said the following: > http://tools.ietf.org/id/draft-ietf-mmusic-ice-16.txt > http://tools.ietf.org/id/draft-ietf-mmusic-ice-1 > http://tools.ietf.org/id/draft-ietf-mmusic-ice > > all work, but > > http://tools.ietf.org/id/draft-ietf-mmusic-ice-16 > > hits an error. I find this a bit disconcerting, since it > doesn't seem to fail for other drafts > > draft-ietf-mmusic-ice-tcp also exists. I don't know if > that's relevant I don't think so; but what's very relevant is that an XML version of draft-ietf-mmusic-ice-16 exists, and content negotiation results in this being returned, rather than the .txt file which also exists. I'm turning off content negotiation for this directory; testing seems to show that everything then works as expected. You may need to force reload your browser for the page (http://tools.ietf.org/id/draft-ietf-mmusic-ice-16) to see the text document rather than the browser's attempt at rendering the XML document, though. Henrik _______________________________________________ Tools-discuss mailing list Tools-discuss@ietf.org https://www1.ietf.org/mailman/listinfo/tools-discuss From tools-discuss-bounces@ietf.org Wed Jul 04 06:57:51 2007 Return-path: Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1I62YQ-0007FB-UH; Wed, 04 Jul 2007 06:57:50 -0400 Received: from tools-discuss by megatron.ietf.org with local (Exim 4.43) id 1I62YP-0007F6-HJ for tools-discuss-confirm+ok@megatron.ietf.org; Wed, 04 Jul 2007 06:57:49 -0400 Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1I62YO-0007Ey-Vz for tools-discuss@ietf.org; Wed, 04 Jul 2007 06:57:49 -0400 Received: from ug-out-1314.google.com ([66.249.92.175]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1I62YK-000668-K3 for tools-discuss@ietf.org; Wed, 04 Jul 2007 06:57:48 -0400 Received: by ug-out-1314.google.com with SMTP id u2so728144uge for ; Wed, 04 Jul 2007 03:57:43 -0700 (PDT) DKIM-Signature: a=rsa-sha1; c=relaxed/relaxed; d=gmail.com; s=beta; h=domainkey-signature:received:received:message-id:date:from:user-agent:mime-version:to:cc:subject:references:in-reply-to:content-type:content-transfer-encoding; b=DO1AQLm1KN4VJSqFuZe+fnEUbNRBs0ve2/4Y2r5rE0fa9MkotLt2N4CGinTcOHhSfLE2KCDnlTXU6sGUMDfJM+TY4Ns3f4PfMHrXu1sjxWZ1quiSIlkXTwYQ5yOvfJXnhqgCWG2I4dzfGvpyJ21ypuUUvEN8vSTwQWLp1zBWsFY= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=beta; h=received:message-id:date:from:user-agent:mime-version:to:cc:subject:references:in-reply-to:content-type:content-transfer-encoding; b=UI2Etunm1BEabwGMY9fTqJRe8hzEpBi4LXLNvDIyJ79zPIn/BgoEQeaTAzNYJghmmcBCaZIWFeSIIslYYeH7x3jZAy4sACHPfUh7eL+YuOmBP+3YM3VKxgrfWvBKTcXDUPHOF2IrzqWLnIFdc9m3g+MuAJ8cTvorUKWroag3W8o= Received: by 10.67.99.4 with SMTP id b4mr1080023ugm.1183546663886; Wed, 04 Jul 2007 03:57:43 -0700 (PDT) Received: from ?10.10.50.1? ( [213.3.13.1]) by mx.google.com with ESMTPS id q57sm342468uga.2007.07.04.03.57.42 (version=SSLv3 cipher=RC4-MD5); Wed, 04 Jul 2007 03:57:43 -0700 (PDT) Message-ID: <468B7D24.4000906@gmail.com> Date: Wed, 04 Jul 2007 12:57:40 +0200 From: Brian E Carpenter User-Agent: Thunderbird 1.5.0.12 (Windows/20070509) MIME-Version: 1.0 To: Henrik Levkowetz Subject: Re: [Tools-discuss] tools.ietf.org/id anomaly References: <468B502F.3050705@gmail.com> <468B7000.6010805@levkowetz.com> In-Reply-To: <468B7000.6010805@levkowetz.com> Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit X-Spam-Score: 0.0 (/) X-Scan-Signature: 97adf591118a232206bdb5a27b217034 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 On 2007-07-04 12:01, Henrik Levkowetz wrote: > Hi Brian, > > On 2007-07-04 09:45 Brian E Carpenter said the following: >> http://tools.ietf.org/id/draft-ietf-mmusic-ice-16.txt >> http://tools.ietf.org/id/draft-ietf-mmusic-ice-1 >> http://tools.ietf.org/id/draft-ietf-mmusic-ice >> >> all work, but >> >> http://tools.ietf.org/id/draft-ietf-mmusic-ice-16 >> >> hits an error. I find this a bit disconcerting, since it >> doesn't seem to fail for other drafts >> >> draft-ietf-mmusic-ice-tcp also exists. I don't know if >> that's relevant > > I don't think so; but what's very relevant is that an XML version > of draft-ietf-mmusic-ice-16 exists, and content negotiation results > in this being returned, rather than the .txt file which also exists. > > I'm turning off content negotiation for this directory; testing > seems to show that everything then works as expected. Yes. In this case, Firefox has a rather misleading error behaviour. IE is much clearer ("The XML page cannot be displayed"). In the IETF context, I think you have to default to txt, unfortunately. Thanks! Brian _______________________________________________ Tools-discuss mailing list Tools-discuss@ietf.org https://www1.ietf.org/mailman/listinfo/tools-discuss From tools-discuss-bounces@ietf.org Fri Jul 06 07:37:39 2007 Return-path: Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1I6m82-0008Gt-Ru; Fri, 06 Jul 2007 07:37:38 -0400 Received: from tools-discuss by megatron.ietf.org with local (Exim 4.43) id 1I6m81-0008Gk-43 for tools-discuss-confirm+ok@megatron.ietf.org; Fri, 06 Jul 2007 07:37:37 -0400 Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1I6m80-0008Gb-QS for tools-discuss@ietf.org; Fri, 06 Jul 2007 07:37:36 -0400 Received: from [2001:698:9:31:214:22ff:fe21:bb] (helo=merlot.tools.ietf.org) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1I6m7z-0003oZ-Dh for tools-discuss@ietf.org; Fri, 06 Jul 2007 07:37:36 -0400 Received: from localhost ([127.0.0.1] helo=marsanne.levkowetz.com ident=henrik) by merlot.tools.ietf.org with esmtp (Exim 4.67) (envelope-from ) id 1I6m7y-0001cY-O1; Fri, 06 Jul 2007 13:37:34 +0200 Message-ID: <468E297E.4020905@levkowetz.com> Date: Fri, 06 Jul 2007 13:37:34 +0200 From: Henrik Levkowetz User-Agent: Thunderbird 2.0.0.4 (Macintosh/20070604) MIME-Version: 1.0 To: Paul Aitken Subject: Re: [Tools-discuss] Re: Idnits-2.04.09 feedback References: <468A517D.1020700@cisco.com> <468A5473.6040306@levkowetz.com> In-Reply-To: <468A5473.6040306@levkowetz.com> X-Enigmail-Version: 0.95.2 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit X-SA-Exim-Connect-IP: 127.0.0.1 X-SA-Exim-Rcpt-To: paitken@cisco.com, tools-discuss@ietf.org, henrik-sent@levkowetz.com X-SA-Exim-Mail-From: henrik@levkowetz.com X-SA-Exim-Scanned: No (on merlot.tools.ietf.org); SAEximRunCond expanded to false X-Spam-Score: -2.8 (--) 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 Revisiting this: On 2007-07-03 15:51 Henrik Levkowetz said the following: > Hi Paul, > > On 2007-07-03 15:39 Paul Aitken said the following: >> Hi. >> >> I just found a problem with a draft that's just about to become an RFC, >> where it claims RFC 2119 compliance but uses the term "MAY NOT" which is >> not defined in RFC 2119. >> >> This is leading to two different interpretations - one believing MAY NOT >> == MUST NOT, the other believing MAY NOT == SHOULD NOT. >> >> Could idnits be updated to check for such errors? > > Thats sounds like a reasonable and helpful idea. I'll see if I can come > up with something to address this. Idnits v2.04.10, which I'm just releasing, looks for and comments on the presence of "MAY NOT", "NOT REQUIRED" and "NOT OPTIONAL". I tried a solution which more generally looked for uppercase words adjacent to a 2119 keyword, but that resulted in too many false positives, so I restricted the check to the 3 expressions listed above. It is trivial to extend the list if needed. Henrik _______________________________________________ Tools-discuss mailing list Tools-discuss@ietf.org https://www1.ietf.org/mailman/listinfo/tools-discuss From tools-discuss-bounces@ietf.org Fri Jul 06 16:26:38 2007 Return-path: Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1I6uNw-0002sA-5u; Fri, 06 Jul 2007 16:26:36 -0400 Received: from tools-discuss by megatron.ietf.org with local (Exim 4.43) id 1I6uNu-0002s5-K8 for tools-discuss-confirm+ok@megatron.ietf.org; Fri, 06 Jul 2007 16:26:34 -0400 Received: from [10.90.34.44] (helo=chiedprmail1.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1I6uNu-0002rx-9E for tools-discuss@ietf.org; Fri, 06 Jul 2007 16:26:34 -0400 Received: from shaman.nostrum.com ([72.232.15.10] helo=nostrum.com) by chiedprmail1.ietf.org with esmtp (Exim 4.43) id 1I6uNY-0001vk-0O for tools-discuss@ietf.org; Fri, 06 Jul 2007 16:26:34 -0400 Received: from [172.17.1.65] (vicuna-alt.estacado.net [75.53.54.121]) (authenticated bits=0) by nostrum.com (8.14.1/8.14.1) with ESMTP id l66KPQDI015878 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NO) for ; Fri, 6 Jul 2007 15:25:26 -0500 (CDT) (envelope-from rjsparks@nostrum.com) Mime-Version: 1.0 (Apple Message framework v752.3) To: Tools Message-Id: Content-Type: multipart/mixed; boundary=Apple-Mail-18--712104891 From: Robert Sparks Date: Fri, 6 Jul 2007 15:25:25 -0500 X-Mailer: Apple Mail (2.752.3) Received-SPF: pass (nostrum.com: 75.53.54.121 is authenticated by a trusted mechanism) X-Spam-Score: 0.0 (/) X-Scan-Signature: 2beba50d0fcdeee5f091c59f204d4365 Subject: [Tools-discuss] RFC-Ed queue munger 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 --Apple-Mail-18--712104891 Content-Transfer-Encoding: 7bit Content-Type: text/plain; charset=US-ASCII; delsp=yes; format=flowed I'm still trying to figure out what all the information in the RFC Editor's queue really means. Phil Kizer and I have written a short perl script that will tell me things about any given draft that's in there. I figured I'd share in case this is useful to someone else, or in case someone looking at it can steer me to better ways to understand the document. You run this with any subset of a draft name, and it will produce output like: $ edq.pl message-sessions draft-ietf-simple-message-sessions is in the WORKING GROUP STANDARDS TRACK (by date received) queue at position 45 in state EDIT behind 4 AUTH 16 AUTH48 5 EDIT 15 MISSREF 3 REF 1 RFC-EDITOR Thoughts? RjS (script attached is also available at http://www.nostrum.com/ ~rjsparks/edq.pl) --Apple-Mail-18--712104891 Content-Transfer-Encoding: 7bit Content-Type: text/x-perl-script; x-unix-mode=0755; name=edq.pl Content-Disposition: attachment; filename=edq.pl #!/usr/bin/perl -w use IO::Socket; die "Usage $0 draftname\nBe sure to leave off the version\n" unless ($#ARGV==0); $target = $ARGV[0]; $host = "www.rfc-editor.org"; $request= "/queue.html"; $remote = IO::Socket::INET->new( Proto => "tcp", PeerAddr => $host, PeerPort => "http(80)", ); unless ($remote) { die "cannot connect to http daemon on $host" } $remote->autoflush(1); print $remote "GET $request HTTP/1.1\r\n"; print $remote "Host: $host\r\n"; print $remote "Connection: close\n\n\r\n"; while (<$remote>) { last if ($_=~/-------------------------------------------------------------------/) } $section = <$remote>; chomp $section; $drop = <$remote>; my $pos = 0; while (<$remote>) { if ($_=~/-------------------------------------------------------------------/) { $section = <$remote>; chomp $section; $drop = <$remote>; $pos = 0; undef %a; } if ($_=~/a name=\"(.*)\"/) { $pos++; if (index($1,$target)>=0) { $target = $1; $drop=<$remote>; $_=<$remote>; die "Couldn't find status" unless (/(\S+)/); print "$target is in the \n$section queue \nat position $pos in state $1 behind \n"; foreach $i (sort keys %a) { print "$a{$i}\t$i\n"; } last; } $drop=<$remote>;$_=<$remote>; if (/(\S+)/) { $a{$1}++;} } } close $remote; # Copyright (c) 2007 Robert James Sparks and Philip Kizer # # Permission is hereby granted, free of charge, to any person obtaining a copy of # this software and associated documentation files (the "Software"), to deal in # the Software without restriction, including without limitation the rights to # use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies # of the Software, and to permit persons to whom the Software is furnished to do # so, subject to the following conditions: # # The above copyright notice and this permission notice shall be included in all # copies or substantial portions of the Software. # # THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR # IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, # FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE # AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER # LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, # OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE # SOFTWARE. --Apple-Mail-18--712104891 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 --Apple-Mail-18--712104891-- From tools-discuss-bounces@ietf.org Fri Jul 06 17:07:55 2007 Return-path: Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1I6v1v-00077Z-3X; Fri, 06 Jul 2007 17:07:55 -0400 Received: from tools-discuss by megatron.ietf.org with local (Exim 4.43) id 1I6v1u-00074e-Gu for tools-discuss-confirm+ok@megatron.ietf.org; Fri, 06 Jul 2007 17:07:54 -0400 Received: from [10.90.34.44] (helo=chiedprmail1.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1I6v1u-00072w-6L for tools-discuss@ietf.org; Fri, 06 Jul 2007 17:07:54 -0400 Received: from mail.gmx.net ([213.165.64.20]) by chiedprmail1.ietf.org with smtp (Exim 4.43) id 1I6v1e-0004m4-OL for tools-discuss@ietf.org; Fri, 06 Jul 2007 17:07:54 -0400 Received: (qmail invoked by alias); 06 Jul 2007 21:06:57 -0000 Received: from p508F8FD6.dip0.t-ipconnect.de (EHLO [192.168.178.22]) [80.143.143.214] by mail.gmx.net (mp017) with SMTP; 06 Jul 2007 23:06:57 +0200 X-Authenticated: #1915285 X-Provags-ID: V01U2FsdGVkX18LgkA3RNQLPpsnUzMzFKEsOuk45S0U26yWasDXqE X+Pdy8pw3msBVs Message-ID: <468EAEED.7000107@gmx.de> Date: Fri, 06 Jul 2007 23:06:53 +0200 From: Julian Reschke User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; de; rv:1.8.0.4) Gecko/20060516 Thunderbird/1.5.0.4 Mnenhy/0.7.4.666 MIME-Version: 1.0 To: Robert Sparks Subject: Re: [Tools-discuss] RFC-Ed queue munger References: In-Reply-To: Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Y-GMX-Trusted: 0 X-Spam-Score: 0.0 (/) X-Scan-Signature: 7a6398bf8aaeabc7a7bb696b6b0a2aad Cc: 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 Robert Sparks wrote: > I'm still trying to figure out what all the information in the RFC > Editor's queue really means. > Phil Kizer and I have written a short perl script that will tell me > things about any given draft that's in there. > I figured I'd share in case this is useful to someone else, or in case > someone looking at it > can steer me to better ways to understand the document. > ... Are you aware of ? Best regards, Julian _______________________________________________ Tools-discuss mailing list Tools-discuss@ietf.org https://www1.ietf.org/mailman/listinfo/tools-discuss From tools-discuss-bounces@ietf.org Sat Jul 07 09:06:37 2007 Return-path: Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1I79zg-0003v8-Nf; Sat, 07 Jul 2007 09:06:36 -0400 Received: from tools-discuss by megatron.ietf.org with local (Exim 4.43) id 1I5j1n-0002I4-2a for tools-discuss-confirm+ok@megatron.ietf.org; Tue, 03 Jul 2007 10:06:51 -0400 Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1I5j1m-0002Hb-P7 for tools-discuss@ietf.org; Tue, 03 Jul 2007 10:06:50 -0400 Received: from ams-iport-1.cisco.com ([144.254.224.140]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1I5j0w-0003oS-GH for tools-discuss@ietf.org; Tue, 03 Jul 2007 10:06:50 -0400 Received: from ams-dkim-1.cisco.com ([144.254.224.138]) by ams-iport-1.cisco.com with ESMTP; 03 Jul 2007 16:05:58 +0200 X-IronPort-Anti-Spam-Filtered: true X-IronPort-Anti-Spam-Result: AgAAAPzziUaQ/uCKh2dsb2JhbACPJAIJDiw X-IronPort-AV: i="4.16,492,1175464800"; d="scan'208"; a="147124764:sNHT26839876" Received: from ams-core-1.cisco.com (ams-core-1.cisco.com [144.254.224.150]) by ams-dkim-1.cisco.com (8.12.11/8.12.11) with ESMTP id l63E5vLk018711; Tue, 3 Jul 2007 16:05:57 +0200 Received: from cisco.com (mrwint.cisco.com [64.103.71.48]) by ams-core-1.cisco.com (8.12.10/8.12.6) with ESMTP id l63E5vTC001366; Tue, 3 Jul 2007 14:05:57 GMT Received: from [10.61.81.196] (ams3-vpn-dhcp4549.cisco.com [10.61.81.196]) by cisco.com (8.8.8-Cisco List Logging/8.8.8) with ESMTP id PAA28051; Tue, 3 Jul 2007 15:05:56 +0100 (BST) Message-ID: <468A57C8.7020101@cisco.com> Date: Tue, 03 Jul 2007 15:06:00 +0100 From: Paul Aitken User-Agent: Mozilla/5.0 (X11; U; Linux i686 (x86_64); en-GB; rv:1.8.1.4) Gecko/20070509 SeaMonkey/1.1.2 MIME-Version: 1.0 To: Henrik Levkowetz References: <468A517D.1020700@cisco.com> <468A5473.6040306@levkowetz.com> In-Reply-To: <468A5473.6040306@levkowetz.com> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit DKIM-Signature: v=0.5; a=rsa-sha256; q=dns/txt; l=195; t=1183471557; x=1184335557; c=relaxed/simple; s=amsdkim1002; h=Content-Type:From:Subject:Content-Transfer-Encoding:MIME-Version; d=cisco.com; i=paitken@cisco.com; z=From:=20Paul=20Aitken=20 |Subject:=20Re=3A=20Idnits-2.04.09=20feedback |Sender:=20; bh=AmFuWZqJOSQrcztSTdgtgNnXhW2DXineAg1IZCeX10A=; b=eJq3qKq9zh5kNs1oY6ue8DMtwWZABIHSvF3ZVedpvJh3Oo3VNeQ57RkQCc7lzSVaYaKccI29 uFX5NbN0ihrOkDBqWeCXTUkNi9UhQvJAzxwYaqRhnnm5dRjlKr86PvwL; Authentication-Results: ams-dkim-1; header.From=paitken@cisco.com; dkim=pass ( sig from cisco.com/amsdkim1002 verified; ); X-Spam-Score: 0.0 (/) X-Scan-Signature: 30ac594df0e66ffa5a93eb4c48bcb014 X-Mailman-Approved-At: Sat, 07 Jul 2007 09:06:35 -0400 Cc: tools-discuss@ietf.org Subject: [Tools-discuss] Re: Idnits-2.04.09 feedback 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 > Thats sounds like a reasonable and helpful idea. I'll see if I can come > up with something to address this. Thanks Henrik. -- Paul Aitken Cisco Systems Ltd, Edinburgh, Scotland. _______________________________________________ Tools-discuss mailing list Tools-discuss@ietf.org https://www1.ietf.org/mailman/listinfo/tools-discuss From tools-discuss-bounces@ietf.org Sat Jul 07 09:06:42 2007 Return-path: Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1I79zg-0003vN-Qx; Sat, 07 Jul 2007 09:06:36 -0400 Received: from tools-discuss by megatron.ietf.org with local (Exim 4.43) id 1I5lIz-0003T2-8d for tools-discuss-confirm+ok@megatron.ietf.org; Tue, 03 Jul 2007 12:32:45 -0400 Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1I5lIy-0003Su-VB for tools-discuss@ietf.org; Tue, 03 Jul 2007 12:32:44 -0400 Received: from ams-iport-1.cisco.com ([144.254.224.140]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1I5lIK-0004Jq-1V for tools-discuss@ietf.org; Tue, 03 Jul 2007 12:32:44 -0400 Received: from ams-dkim-2.cisco.com ([144.254.224.139]) by ams-iport-1.cisco.com with ESMTP; 03 Jul 2007 18:32:02 +0200 X-IronPort-Anti-Spam-Filtered: true X-IronPort-Anti-Spam-Result: AgAAABoXikaQ/uCLh2dsb2JhbACPJAIJDiw X-IronPort-AV: i="4.16,492,1175464800"; d="scan'208"; a="147142662:sNHT28143212" Received: from ams-core-1.cisco.com (ams-core-1.cisco.com [144.254.224.150]) by ams-dkim-2.cisco.com (8.12.11/8.12.11) with ESMTP id l63GW0B1018905; Tue, 3 Jul 2007 18:32:00 +0200 Received: from cisco.com (mrwint.cisco.com [64.103.71.48]) by ams-core-1.cisco.com (8.12.10/8.12.6) with ESMTP id l63GW0TC019749; Tue, 3 Jul 2007 16:32:00 GMT Received: from [10.61.81.196] (ams3-vpn-dhcp4549.cisco.com [10.61.81.196]) by cisco.com (8.8.8-Cisco List Logging/8.8.8) with ESMTP id RAA13035; Tue, 3 Jul 2007 17:31:59 +0100 (BST) Message-ID: <468A7A03.8080804@cisco.com> Date: Tue, 03 Jul 2007 17:32:03 +0100 From: Paul Aitken User-Agent: Mozilla/5.0 (X11; U; Linux i686 (x86_64); en-GB; rv:1.8.1.4) Gecko/20070509 SeaMonkey/1.1.2 MIME-Version: 1.0 To: Brian E Carpenter Subject: Re: [Tools-discuss] Re: Idnits-2.04.09 feedback References: <468A517D.1020700@cisco.com> <468A5473.6040306@levkowetz.com> <468A5E7D.6040601@gmail.com> In-Reply-To: <468A5E7D.6040601@gmail.com> Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit DKIM-Signature: v=0.5; a=rsa-sha256; q=dns/txt; l=1473; t=1183480320; x=1184344320; c=relaxed/simple; s=amsdkim2001; h=Content-Type:From:Subject:Content-Transfer-Encoding:MIME-Version; d=cisco.com; i=paitken@cisco.com; z=From:=20Paul=20Aitken=20 |Subject:=20Re=3A=20[Tools-discuss]=20Re=3A=20Idnits-2.04.09=20feedback |Sender:=20; bh=iTb1AN4eZWmhBplu+oow9SYJ3IOVqMlnUqN32l2fXjE=; b=oHwgjLDC20YW08EgvZsUzci9Nof/d9apC2QDE7d+KNViB6J7zwbZivYDI6x9vg2N9UohIz0A fLzIbrOpFTXmfBL2PJTbicMkCkAQlvQQL3/rpX27PFCW7GttSB7wS7zj; Authentication-Results: ams-dkim-2; header.From=paitken@cisco.com; dkim=pass ( sig from cisco.com/amsdkim2001 verified; ); X-Spam-Score: 0.0 (/) X-Scan-Signature: bb8f917bb6b8da28fc948aeffb74aa17 X-Mailman-Approved-At: Sat, 07 Jul 2007 09:06:35 -0400 Cc: Henrik Levkowetz , 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 Brian, >>> I just found a problem with a draft that's just about to become an >>> RFC, where it claims RFC 2119 compliance but uses the term "MAY NOT" >>> which is not defined in RFC 2119. >>> >>> This is leading to two different interpretations - one believing MAY >>> NOT == MUST NOT, the other believing MAY NOT == SHOULD NOT. > > By the way, the meaning is very clear in English, as in > "You MAY NOT have another ice cream." But I think it is to avoid > this argument that the phrase is not present in 2119. Well I thought so, as did the other authors and implementors of this protocol. But today someone else (possibly a non-native English speaker, though obviously with an excellent command of English) interpreted "MAY NOT" as "SHOULD NOT", or "MIGHT NOT", ie "I understood it has a possibility of ..." Thinking about it, everyday we use phrases such as "I may not go ..." or "I may not do that" when we actually mean "might not", since "may" indicates permission, whereas "might" indicates probability. However, in terms of RFC 2119, "MAY NOT" doesn't make much sense: my guess is that it'd indicate that it's optional NOT to do something, which is about the same as being optional that you do it. Bottom line is that we should highlight such mistakes to authors so they can tighten up their drafts - and idnits seems the perfect way to do that. Cheers. -- Paul Aitken Cisco Systems Ltd, Edinburgh, Scotland. _______________________________________________ Tools-discuss mailing list Tools-discuss@ietf.org https://www1.ietf.org/mailman/listinfo/tools-discuss From tools-discuss-bounces@ietf.org Sat Jul 07 09:06:42 2007 Return-path: Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1I79zg-0003v3-K3; Sat, 07 Jul 2007 09:06:36 -0400 Received: from tools-discuss by megatron.ietf.org with local (Exim 4.43) id 1I5iby-0001kd-Gn for tools-discuss-confirm+ok@megatron.ietf.org; Tue, 03 Jul 2007 09:40:10 -0400 Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1I5iby-0001kD-56 for tools-discuss@ietf.org; Tue, 03 Jul 2007 09:40:10 -0400 Received: from ams-iport-1.cisco.com ([144.254.224.140]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1I5ibO-0004Hb-Fx for tools-discuss@ietf.org; Tue, 03 Jul 2007 09:40:10 -0400 Received: from ams-dkim-1.cisco.com ([144.254.224.138]) by ams-iport-1.cisco.com with ESMTP; 03 Jul 2007 15:39:12 +0200 X-IronPort-Anti-Spam-Filtered: true X-IronPort-Anti-Spam-Result: AgAAABbuiUaQ/uCKh2dsb2JhbACPJAIJDiw X-IronPort-AV: i="4.16,492,1175464800"; d="scan'208"; a="147121348:sNHT3478900860" Received: from ams-core-1.cisco.com (ams-core-1.cisco.com [144.254.224.150]) by ams-dkim-1.cisco.com (8.12.11/8.12.11) with ESMTP id l63DdBJo010007; Tue, 3 Jul 2007 15:39:11 +0200 Received: from cisco.com (mrwint.cisco.com [64.103.71.48]) by ams-core-1.cisco.com (8.12.10/8.12.6) with ESMTP id l63Dd6TC022331; Tue, 3 Jul 2007 13:39:11 GMT Received: from [10.61.81.196] (ams3-vpn-dhcp4549.cisco.com [10.61.81.196]) by cisco.com (8.8.8-Cisco List Logging/8.8.8) with ESMTP id OAA24965; Tue, 3 Jul 2007 14:39:06 +0100 (BST) Message-ID: <468A517D.1020700@cisco.com> Date: Tue, 03 Jul 2007 14:39:09 +0100 From: Paul Aitken User-Agent: Mozilla/5.0 (X11; U; Linux i686 (x86_64); en-GB; rv:1.8.1.4) Gecko/20070509 SeaMonkey/1.1.2 MIME-Version: 1.0 To: tools-discuss@ietf.org Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit DKIM-Signature: v=0.5; a=rsa-sha256; q=dns/txt; l=439; t=1183469951; x=1184333951; c=relaxed/simple; s=amsdkim1002; h=Content-Type:From:Subject:Content-Transfer-Encoding:MIME-Version; d=cisco.com; i=paitken@cisco.com; z=From:=20Paul=20Aitken=20 |Subject:=20Idnits-2.04.09=20feedback |Sender:=20; bh=15OH78Oc3HB8FOcyl64b9cmAN0aWJBBadxkyTst338w=; b=XLk+97VpKLSio9iopwA/JCVfgnxR6OZRh4pKe1vERA6ugurmmCzzPzoZ9QODIPbcpJUIyu8Z oxzUWg6l8Y0bp168z35vhW+aqx5+eUif2Q4ggKlb5bbvAM16w8PuJNwa; Authentication-Results: ams-dkim-1; header.From=paitken@cisco.com; dkim=pass ( sig from cisco.com/amsdkim1002 verified; ); X-Spam-Score: 0.0 (/) X-Scan-Signature: 08170828343bcf1325e4a0fb4584481c X-Mailman-Approved-At: Sat, 07 Jul 2007 09:06:35 -0400 Cc: Henrik Levkowetz Subject: [Tools-discuss] Idnits-2.04.09 feedback 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. I just found a problem with a draft that's just about to become an RFC, where it claims RFC 2119 compliance but uses the term "MAY NOT" which is not defined in RFC 2119. This is leading to two different interpretations - one believing MAY NOT == MUST NOT, the other believing MAY NOT == SHOULD NOT. Could idnits be updated to check for such errors? Thanks. -- Paul Aitken Cisco Systems Ltd, Edinburgh, Scotland. _______________________________________________ Tools-discuss mailing list Tools-discuss@ietf.org https://www1.ietf.org/mailman/listinfo/tools-discuss From tools-discuss-bounces@ietf.org Sat Jul 07 09:06:42 2007 Return-path: Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1I79zg-0003vN-Qx; Sat, 07 Jul 2007 09:06:36 -0400 Received: from tools-discuss by megatron.ietf.org with local (Exim 4.43) id 1I5lIz-0003T2-8d for tools-discuss-confirm+ok@megatron.ietf.org; Tue, 03 Jul 2007 12:32:45 -0400 Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1I5lIy-0003Su-VB for tools-discuss@ietf.org; Tue, 03 Jul 2007 12:32:44 -0400 Received: from ams-iport-1.cisco.com ([144.254.224.140]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1I5lIK-0004Jq-1V for tools-discuss@ietf.org; Tue, 03 Jul 2007 12:32:44 -0400 Received: from ams-dkim-2.cisco.com ([144.254.224.139]) by ams-iport-1.cisco.com with ESMTP; 03 Jul 2007 18:32:02 +0200 X-IronPort-Anti-Spam-Filtered: true X-IronPort-Anti-Spam-Result: AgAAABoXikaQ/uCLh2dsb2JhbACPJAIJDiw X-IronPort-AV: i="4.16,492,1175464800"; d="scan'208"; a="147142662:sNHT28143212" Received: from ams-core-1.cisco.com (ams-core-1.cisco.com [144.254.224.150]) by ams-dkim-2.cisco.com (8.12.11/8.12.11) with ESMTP id l63GW0B1018905; Tue, 3 Jul 2007 18:32:00 +0200 Received: from cisco.com (mrwint.cisco.com [64.103.71.48]) by ams-core-1.cisco.com (8.12.10/8.12.6) with ESMTP id l63GW0TC019749; Tue, 3 Jul 2007 16:32:00 GMT Received: from [10.61.81.196] (ams3-vpn-dhcp4549.cisco.com [10.61.81.196]) by cisco.com (8.8.8-Cisco List Logging/8.8.8) with ESMTP id RAA13035; Tue, 3 Jul 2007 17:31:59 +0100 (BST) Message-ID: <468A7A03.8080804@cisco.com> Date: Tue, 03 Jul 2007 17:32:03 +0100 From: Paul Aitken User-Agent: Mozilla/5.0 (X11; U; Linux i686 (x86_64); en-GB; rv:1.8.1.4) Gecko/20070509 SeaMonkey/1.1.2 MIME-Version: 1.0 To: Brian E Carpenter Subject: Re: [Tools-discuss] Re: Idnits-2.04.09 feedback References: <468A517D.1020700@cisco.com> <468A5473.6040306@levkowetz.com> <468A5E7D.6040601@gmail.com> In-Reply-To: <468A5E7D.6040601@gmail.com> Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit DKIM-Signature: v=0.5; a=rsa-sha256; q=dns/txt; l=1473; t=1183480320; x=1184344320; c=relaxed/simple; s=amsdkim2001; h=Content-Type:From:Subject:Content-Transfer-Encoding:MIME-Version; d=cisco.com; i=paitken@cisco.com; z=From:=20Paul=20Aitken=20 |Subject:=20Re=3A=20[Tools-discuss]=20Re=3A=20Idnits-2.04.09=20feedback |Sender:=20; bh=iTb1AN4eZWmhBplu+oow9SYJ3IOVqMlnUqN32l2fXjE=; b=oHwgjLDC20YW08EgvZsUzci9Nof/d9apC2QDE7d+KNViB6J7zwbZivYDI6x9vg2N9UohIz0A fLzIbrOpFTXmfBL2PJTbicMkCkAQlvQQL3/rpX27PFCW7GttSB7wS7zj; Authentication-Results: ams-dkim-2; header.From=paitken@cisco.com; dkim=pass ( sig from cisco.com/amsdkim2001 verified; ); X-Spam-Score: 0.0 (/) X-Scan-Signature: bb8f917bb6b8da28fc948aeffb74aa17 X-Mailman-Approved-At: Sat, 07 Jul 2007 09:06:35 -0400 Cc: Henrik Levkowetz , 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 Brian, >>> I just found a problem with a draft that's just about to become an >>> RFC, where it claims RFC 2119 compliance but uses the term "MAY NOT" >>> which is not defined in RFC 2119. >>> >>> This is leading to two different interpretations - one believing MAY >>> NOT == MUST NOT, the other believing MAY NOT == SHOULD NOT. > > By the way, the meaning is very clear in English, as in > "You MAY NOT have another ice cream." But I think it is to avoid > this argument that the phrase is not present in 2119. Well I thought so, as did the other authors and implementors of this protocol. But today someone else (possibly a non-native English speaker, though obviously with an excellent command of English) interpreted "MAY NOT" as "SHOULD NOT", or "MIGHT NOT", ie "I understood it has a possibility of ..." Thinking about it, everyday we use phrases such as "I may not go ..." or "I may not do that" when we actually mean "might not", since "may" indicates permission, whereas "might" indicates probability. However, in terms of RFC 2119, "MAY NOT" doesn't make much sense: my guess is that it'd indicate that it's optional NOT to do something, which is about the same as being optional that you do it. Bottom line is that we should highlight such mistakes to authors so they can tighten up their drafts - and idnits seems the perfect way to do that. Cheers. -- Paul Aitken Cisco Systems Ltd, Edinburgh, Scotland. _______________________________________________ Tools-discuss mailing list Tools-discuss@ietf.org https://www1.ietf.org/mailman/listinfo/tools-discuss From tools-discuss-bounces@ietf.org Sat Jul 07 09:06:42 2007 Return-path: Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1I79zg-0003v3-K3; Sat, 07 Jul 2007 09:06:36 -0400 Received: from tools-discuss by megatron.ietf.org with local (Exim 4.43) id 1I5iby-0001kd-Gn for tools-discuss-confirm+ok@megatron.ietf.org; Tue, 03 Jul 2007 09:40:10 -0400 Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1I5iby-0001kD-56 for tools-discuss@ietf.org; Tue, 03 Jul 2007 09:40:10 -0400 Received: from ams-iport-1.cisco.com ([144.254.224.140]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1I5ibO-0004Hb-Fx for tools-discuss@ietf.org; Tue, 03 Jul 2007 09:40:10 -0400 Received: from ams-dkim-1.cisco.com ([144.254.224.138]) by ams-iport-1.cisco.com with ESMTP; 03 Jul 2007 15:39:12 +0200 X-IronPort-Anti-Spam-Filtered: true X-IronPort-Anti-Spam-Result: AgAAABbuiUaQ/uCKh2dsb2JhbACPJAIJDiw X-IronPort-AV: i="4.16,492,1175464800"; d="scan'208"; a="147121348:sNHT3478900860" Received: from ams-core-1.cisco.com (ams-core-1.cisco.com [144.254.224.150]) by ams-dkim-1.cisco.com (8.12.11/8.12.11) with ESMTP id l63DdBJo010007; Tue, 3 Jul 2007 15:39:11 +0200 Received: from cisco.com (mrwint.cisco.com [64.103.71.48]) by ams-core-1.cisco.com (8.12.10/8.12.6) with ESMTP id l63Dd6TC022331; Tue, 3 Jul 2007 13:39:11 GMT Received: from [10.61.81.196] (ams3-vpn-dhcp4549.cisco.com [10.61.81.196]) by cisco.com (8.8.8-Cisco List Logging/8.8.8) with ESMTP id OAA24965; Tue, 3 Jul 2007 14:39:06 +0100 (BST) Message-ID: <468A517D.1020700@cisco.com> Date: Tue, 03 Jul 2007 14:39:09 +0100 From: Paul Aitken User-Agent: Mozilla/5.0 (X11; U; Linux i686 (x86_64); en-GB; rv:1.8.1.4) Gecko/20070509 SeaMonkey/1.1.2 MIME-Version: 1.0 To: tools-discuss@ietf.org Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit DKIM-Signature: v=0.5; a=rsa-sha256; q=dns/txt; l=439; t=1183469951; x=1184333951; c=relaxed/simple; s=amsdkim1002; h=Content-Type:From:Subject:Content-Transfer-Encoding:MIME-Version; d=cisco.com; i=paitken@cisco.com; z=From:=20Paul=20Aitken=20 |Subject:=20Idnits-2.04.09=20feedback |Sender:=20; bh=15OH78Oc3HB8FOcyl64b9cmAN0aWJBBadxkyTst338w=; b=XLk+97VpKLSio9iopwA/JCVfgnxR6OZRh4pKe1vERA6ugurmmCzzPzoZ9QODIPbcpJUIyu8Z oxzUWg6l8Y0bp168z35vhW+aqx5+eUif2Q4ggKlb5bbvAM16w8PuJNwa; Authentication-Results: ams-dkim-1; header.From=paitken@cisco.com; dkim=pass ( sig from cisco.com/amsdkim1002 verified; ); X-Spam-Score: 0.0 (/) X-Scan-Signature: 08170828343bcf1325e4a0fb4584481c X-Mailman-Approved-At: Sat, 07 Jul 2007 09:06:35 -0400 Cc: Henrik Levkowetz Subject: [Tools-discuss] Idnits-2.04.09 feedback 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. I just found a problem with a draft that's just about to become an RFC, where it claims RFC 2119 compliance but uses the term "MAY NOT" which is not defined in RFC 2119. This is leading to two different interpretations - one believing MAY NOT == MUST NOT, the other believing MAY NOT == SHOULD NOT. Could idnits be updated to check for such errors? Thanks. -- Paul Aitken Cisco Systems Ltd, Edinburgh, Scotland. _______________________________________________ Tools-discuss mailing list Tools-discuss@ietf.org https://www1.ietf.org/mailman/listinfo/tools-discuss From tools-discuss-bounces@ietf.org Thu Jul 12 08:25:51 2007 Return-path: Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1I8xjy-0004Cp-Kj; Thu, 12 Jul 2007 08:25:50 -0400 Received: from tools-discuss by megatron.ietf.org with local (Exim 4.43) id 1I8eXo-0005cM-UP for tools-discuss-confirm+ok@megatron.ietf.org; Wed, 11 Jul 2007 11:56:00 -0400 Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1I8eXo-0005cD-Kj for tools-discuss@ietf.org; Wed, 11 Jul 2007 11:56:00 -0400 Received: from lemland.kurtis.pp.se ([2001:670:87:2:20e:a6ff:fe3c:6a8b]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1I8eXk-0004Dx-8A for tools-discuss@ietf.org; Wed, 11 Jul 2007 11:56:00 -0400 Received: from [192.71.80.74] (laptop2.kurtis.autonomica.se [192.71.80.74]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (Client did not present a certificate) by lemland.kurtis.pp.se (Postfix) with ESMTP id 9AFA278C52 for ; Wed, 11 Jul 2007 17:55:52 +0200 (CEST) Mime-Version: 1.0 (Apple Message framework v752.2) Content-Transfer-Encoding: 7bit Message-Id: <44849987-492C-48D8-B7D2-4B135952A340@kurtis.pp.se> Content-Type: text/plain; charset=US-ASCII; delsp=yes; format=flowed To: tools-discuss@ietf.org From: Kurt Erik Lindqvist Date: Wed, 11 Jul 2007 17:55:48 +0200 X-Mailer: Apple Mail (2.752.2) X-Spam-Score: 0.0 (/) X-Scan-Signature: 08e48e05374109708c00c6208b534009 X-Mailman-Approved-At: Thu, 12 Jul 2007 08:25:50 -0400 Subject: [Tools-discuss] Agenda RSS feed 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 Would it be possible to have an RSS feed for WG agenda postings as they become available. Preferably the same feed for all meetings... This is so that I know when to run the getdrafts tool the next time... - kurtis - _______________________________________________ Tools-discuss mailing list Tools-discuss@ietf.org https://www1.ietf.org/mailman/listinfo/tools-discuss From tools-discuss-bounces@ietf.org Thu Jul 12 10:34:32 2007 Return-path: Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1I8zkV-00056k-Vk; Thu, 12 Jul 2007 10:34:31 -0400 Received: from tools-discuss by megatron.ietf.org with local (Exim 4.43) id 1I8zkV-00052u-4L for tools-discuss-confirm+ok@megatron.ietf.org; Thu, 12 Jul 2007 10:34:31 -0400 Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1I8zkU-00051f-PY for tools-discuss@ietf.org; Thu, 12 Jul 2007 10:34:30 -0400 Received: from [2001:698:9:31:214:22ff:fe21:bb] (helo=merlot.tools.ietf.org) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1I8zkT-0004MV-Cx for tools-discuss@ietf.org; Thu, 12 Jul 2007 10:34:30 -0400 Received: from localhost ([127.0.0.1] helo=marsanne.levkowetz.com ident=henrik) by merlot.tools.ietf.org with esmtp (Exim 4.67) (envelope-from ) id 1I8zkS-0000CY-MQ; Thu, 12 Jul 2007 16:34:28 +0200 Message-ID: <46963BF4.7070809@levkowetz.com> Date: Thu, 12 Jul 2007 16:34:28 +0200 From: Henrik Levkowetz User-Agent: Thunderbird 2.0.0.4 (Macintosh/20070604) MIME-Version: 1.0 To: Kurt Erik Lindqvist Subject: Re: [Tools-discuss] Agenda RSS feed References: <44849987-492C-48D8-B7D2-4B135952A340@kurtis.pp.se> In-Reply-To: <44849987-492C-48D8-B7D2-4B135952A340@kurtis.pp.se> X-Enigmail-Version: 0.95.2 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit X-SA-Exim-Connect-IP: 127.0.0.1 X-SA-Exim-Rcpt-To: kurtis@kurtis.pp.se, tools-discuss@ietf.org, henrik-sent@levkowetz.com X-SA-Exim-Mail-From: henrik@levkowetz.com X-SA-Exim-Scanned: No (on merlot.tools.ietf.org); SAEximRunCond expanded to false X-Spam-Score: -2.8 (--) X-Scan-Signature: 08170828343bcf1325e4a0fb4584481c 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 On 2007-07-11 17:55 Kurt Erik Lindqvist said the following: > > Would it be possible to have an RSS feed for WG agenda postings as > they become available. Preferably the same feed for all meetings... > > This is so that I know when to run the getdrafts tool the next time... I'd be happy to host such a feed and the script(s) to create it, but I'm not sufficiently familiar with RSS/Atom to whip one up swiftly. If someone else puts a script together, I can adapt it if needed to use information already available on the servers, and deploy it swiftly. Henrik _______________________________________________ Tools-discuss mailing list Tools-discuss@ietf.org https://www1.ietf.org/mailman/listinfo/tools-discuss From tools-discuss-bounces@ietf.org Fri Jul 13 13:49:07 2007 Return-path: Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1I9PGN-0008Qy-8a; Fri, 13 Jul 2007 13:49:07 -0400 Received: from tools-discuss by megatron.ietf.org with local (Exim 4.43) id 1I9PGL-0008Qr-Ua for tools-discuss-confirm+ok@megatron.ietf.org; Fri, 13 Jul 2007 13:49:05 -0400 Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1I9PGL-0008Qj-Kl for tools-discuss@ietf.org; Fri, 13 Jul 2007 13:49:05 -0400 Received: from newdev.eecs.harvard.edu ([140.247.60.212] helo=newdev.harvard.edu) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1I9PGH-0000cN-Eh for tools-discuss@ietf.org; Fri, 13 Jul 2007 13:49:05 -0400 Received: by newdev.harvard.edu (Postfix, from userid 501) id 1600442170A; Fri, 13 Jul 2007 13:48:18 -0400 (EDT) To: brian.e.carpenter@gmail.com, paitken@cisco.com Subject: Re: [Tools-discuss] Re: Idnits-2.04.09 feedback In-Reply-To: <468A7A03.8080804@cisco.com> Message-Id: <20070713174818.1600442170A@newdev.harvard.edu> Date: Fri, 13 Jul 2007 13:48:18 -0400 (EDT) From: sob@harvard.edu (Scott O. Bradner) X-Spam-Score: 0.0 (/) X-Scan-Signature: 7aefe408d50e9c7c47615841cb314bed Cc: henrik@levkowetz.com, 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 > However, in terms of RFC 2119, "MAY NOT" doesn't make much sense: that is what the author thought when writing RFC 2119 Scott _______________________________________________ Tools-discuss mailing list Tools-discuss@ietf.org https://www1.ietf.org/mailman/listinfo/tools-discuss From tools-discuss-bounces@ietf.org Fri Jul 13 14:44:44 2007 Return-path: Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1I9Q8B-0007Zx-KJ; Fri, 13 Jul 2007 14:44:43 -0400 Received: from tools-discuss by megatron.ietf.org with local (Exim 4.43) id 1I9Q8B-0007Zi-3n for tools-discuss-confirm+ok@megatron.ietf.org; Fri, 13 Jul 2007 14:44:43 -0400 Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1I9Q8A-0007Za-QZ for tools-discuss@ietf.org; Fri, 13 Jul 2007 14:44:42 -0400 Received: from [2001:698:9:31:214:22ff:fe21:bb] (helo=merlot.tools.ietf.org) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1I9Q89-00034Y-C0 for tools-discuss@ietf.org; Fri, 13 Jul 2007 14:44:42 -0400 Received: from localhost ([127.0.0.1] helo=marsanne.levkowetz.com ident=henrik) by merlot.tools.ietf.org with esmtp (Exim 4.67) (envelope-from ) id 1I9Q88-0005Ji-Dj; Fri, 13 Jul 2007 20:44:40 +0200 Message-ID: <4697C818.9090401@levkowetz.com> Date: Fri, 13 Jul 2007 20:44:40 +0200 From: Henrik Levkowetz User-Agent: Thunderbird 2.0.0.4 (Macintosh/20070604) MIME-Version: 1.0 To: Kurt Erik Lindqvist Subject: Re: [Tools-discuss] Agenda RSS feed References: <44849987-492C-48D8-B7D2-4B135952A340@kurtis.pp.se> In-Reply-To: <44849987-492C-48D8-B7D2-4B135952A340@kurtis.pp.se> X-Enigmail-Version: 0.95.2 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit X-SA-Exim-Connect-IP: 127.0.0.1 X-SA-Exim-Rcpt-To: kurtis@kurtis.pp.se, tools-discuss@ietf.org, henrik-sent@levkowetz.com X-SA-Exim-Mail-From: henrik@levkowetz.com X-SA-Exim-Scanned: No (on merlot.tools.ietf.org); SAEximRunCond expanded to false X-Spam-Score: -2.8 (--) X-Scan-Signature: 2409bba43e9c8d580670fda8b695204a 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 Kurtis, On 2007-07-11 17:55 Kurt Erik Lindqvist said the following: > > Would it be possible to have an RSS feed for WG agenda postings as > they become available. Preferably the same feed for all meetings... > > This is so that I know when to run the getdrafts tool the next time... Carsten Bormann has contributed a nice little ruby script which will generate an Atom feed. I've integrated this with the rest of the agenda handling on tools.ietf.org, so go ahead and try it out. If you go to: http://tools.ietf.org/agenda/69 you should see the agenda, and if your browser understands feeds, you should also see an feed indication in the address field, which you can click and subscribe to. Alternatively, you can give your feed reader the appropriate url directly: http://tools.ietf.org/agenda/69/atom Let us know how this works! Henrik _______________________________________________ Tools-discuss mailing list Tools-discuss@ietf.org https://www1.ietf.org/mailman/listinfo/tools-discuss From tools-discuss-bounces@ietf.org Sat Jul 14 14:14:44 2007 Return-path: Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1I9m8h-0007z9-BD; Sat, 14 Jul 2007 14:14:43 -0400 Received: from tools-discuss by megatron.ietf.org with local (Exim 4.43) id 1I9TJq-0007R1-TM for tools-discuss-confirm+ok@megatron.ietf.org; Fri, 13 Jul 2007 18:08:58 -0400 Received: from [10.90.34.44] (helo=chiedprmail1.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1I9TJq-0007MW-4S for tools-discuss@ietf.org; Fri, 13 Jul 2007 18:08:58 -0400 Received: from ithilien.qualcomm.com ([129.46.51.59]) by chiedprmail1.ietf.org with esmtp (Exim 4.43) id 1I9TJb-0002nk-Pi for tools-discuss@ietf.org; Fri, 13 Jul 2007 18:08:58 -0400 Received: from totoro.qualcomm.com (totoro.qualcomm.com [129.46.61.158]) by ithilien.qualcomm.com (8.13.6/8.12.5/1.0) with ESMTP id l6DM7U0P029469 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=FAIL) for ; Fri, 13 Jul 2007 15:07:30 -0700 Received: from [129.46.78.141] (ldondeti.na.qualcomm.com [129.46.78.141]) by totoro.qualcomm.com (8.13.6/8.13.6/1.0) with ESMTP id l6DM7TiM006982 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT) for ; Fri, 13 Jul 2007 15:07:30 -0700 (PDT) Message-ID: <4697F79D.7020806@qualcomm.com> Date: Fri, 13 Jul 2007 15:07:25 -0700 From: Lakshminath Dondeti User-Agent: Thunderbird 2.0.0.4 (Windows/20070604) MIME-Version: 1.0 To: tools-discuss@ietf.org Content-Type: text/plain; charset=ISO-8859-15; format=flowed Content-Transfer-Encoding: 7bit X-Spam-Score: 0.0 (/) X-Scan-Signature: 93238566e09e6e262849b4f805833007 X-Mailman-Approved-At: Sat, 14 Jul 2007 14:14:42 -0400 Subject: [Tools-discuss] Tools Team Support for Nomcom 2007-8 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 all, Andrew spoke very highly of your support for the Nomcom process last year and suggested that I contact you as soon as possible. Specifically, he noted that the nomcom Wiki and comment tracking tools were very useful. Would you be able to provide similar support to the Nomcom this year? All Nomcom material needs to be handled within RFC 3777's confidentiality rules. If Henrik/Don/Bill (from my recollection of the tools team members who volunteered) gets selected as a voting member and they can support the nomcom at the same time, that'll be great :). Of course, we wouldn't know that until later today. Next, some of you may be nominated for one or more of the open positions, so we need to take that into account as well. The voting members make the decisions on the specific requirements, but in the meanwhile I would like to get a sense of what you may have the bandwidth for. Hope you can offer a similar support as you provided to the previous nomcom. thanks, Lakshminath _______________________________________________ Tools-discuss mailing list Tools-discuss@ietf.org https://www1.ietf.org/mailman/listinfo/tools-discuss From tools-discuss-bounces@ietf.org Mon Jul 16 05:25:35 2007 Return-path: Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1IAMpe-0007gB-Ps; Mon, 16 Jul 2007 05:25:30 -0400 Received: from tools-discuss by megatron.ietf.org with local (Exim 4.43) id 1IAMpc-0007Yv-Q9 for tools-discuss-confirm+ok@megatron.ietf.org; Mon, 16 Jul 2007 05:25:29 -0400 Received: from [10.90.34.44] (helo=chiedprmail1.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1IAMpb-0007XA-Nr for tools-discuss@ietf.org; Mon, 16 Jul 2007 05:25:28 -0400 Received: from defiant.autonomica.se ([192.71.80.105]) by chiedprmail1.ietf.org with esmtp (Exim 4.43) id 1IAMpQ-00089z-EZ for tools-discuss@ietf.org; Mon, 16 Jul 2007 05:25:27 -0400 Received: from [192.71.80.74] (laptop2.kurtis.autonomica.se [192.71.80.74]) by defiant.autonomica.se (Postfix) with ESMTP id 540CB18F59E; Mon, 16 Jul 2007 11:24:43 +0200 (CEST) In-Reply-To: <4697C818.9090401@levkowetz.com> References: <44849987-492C-48D8-B7D2-4B135952A340@kurtis.pp.se> <4697C818.9090401@levkowetz.com> Mime-Version: 1.0 (Apple Message framework v752.2) Content-Type: text/plain; charset=US-ASCII; delsp=yes; format=flowed Message-Id: Content-Transfer-Encoding: 7bit From: Kurt Erik Lindqvist Subject: Re: [Tools-discuss] Agenda RSS feed Date: Mon, 16 Jul 2007 11:24:44 +0200 To: Henrik Levkowetz X-Mailer: Apple Mail (2.752.2) X-Spam-Score: 0.0 (/) X-Scan-Signature: 39bd8f8cbb76cae18b7e23f7cf6b2b9f 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! On 13 jul 2007, at 20.44, Henrik Levkowetz wrote: > Hi Kurtis, > > On 2007-07-11 17:55 Kurt Erik Lindqvist said the following: >> >> Would it be possible to have an RSS feed for WG agenda postings as >> they become available. Preferably the same feed for all meetings... >> >> This is so that I know when to run the getdrafts tool the next >> time... > > Carsten Bormann has contributed a nice little ruby script which will > generate an Atom feed. I've integrated this with the rest of the > agenda handling on tools.ietf.org, so go ahead and try it out. If you > go to: > http://tools.ietf.org/agenda/69 > you should see the agenda, and if your browser understands feeds, you > should also see an feed indication in the address field, which you can > click and subscribe to. > > Alternatively, you can give your feed reader the appropriate url > directly: > http://tools.ietf.org/agenda/69/atom > > > Let us know how this works! This is great! Thanks a lot for this tool! Best regards, - kurtis - _______________________________________________ Tools-discuss mailing list Tools-discuss@ietf.org https://www1.ietf.org/mailman/listinfo/tools-discuss From tools-discuss-bounces@ietf.org Mon Jul 16 09:06:29 2007 Return-path: Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1IAQHV-0002oR-JT; Mon, 16 Jul 2007 09:06:29 -0400 Received: from tools-discuss by megatron.ietf.org with local (Exim 4.43) id 1IAQHV-0002oG-9h for tools-discuss-confirm+ok@megatron.ietf.org; Mon, 16 Jul 2007 09:06:29 -0400 Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1IAQHV-0002o8-0D for tools-discuss@ietf.org; Mon, 16 Jul 2007 09:06:29 -0400 Received: from [2001:698:9:31:214:22ff:fe21:bb] (helo=merlot.tools.ietf.org) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1IAQHT-0001RK-Ip for tools-discuss@ietf.org; Mon, 16 Jul 2007 09:06:28 -0400 Received: from localhost ([127.0.0.1] helo=marsanne.levkowetz.com ident=henrik) by merlot.tools.ietf.org with esmtp (Exim 4.67) (envelope-from ) id 1IAQHR-0007UA-Tv; Mon, 16 Jul 2007 15:06:26 +0200 Message-ID: <469B6D51.8030607@levkowetz.com> Date: Mon, 16 Jul 2007 15:06:25 +0200 From: Henrik Levkowetz User-Agent: Thunderbird 2.0.0.4 (Macintosh/20070604) MIME-Version: 1.0 To: Kurt Erik Lindqvist Subject: Re: [Tools-discuss] Agenda RSS feed References: <44849987-492C-48D8-B7D2-4B135952A340@kurtis.pp.se> <4697C818.9090401@levkowetz.com> In-Reply-To: X-Enigmail-Version: 0.95.2 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit X-SA-Exim-Connect-IP: 127.0.0.1 X-SA-Exim-Rcpt-To: kurtis@kurtis.pp.se, tools-discuss@ietf.org, henrik-sent@levkowetz.com X-SA-Exim-Mail-From: henrik@levkowetz.com X-SA-Exim-Scanned: No (on merlot.tools.ietf.org); SAEximRunCond expanded to false X-Spam-Score: -2.8 (--) X-Scan-Signature: cf4fa59384e76e63313391b70cd0dd25 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 On 2007-07-16 11:24 Kurt Erik Lindqvist said the following: ... > This is great! Thanks a lot for this tool! Excellent. For early adopters, please note that I've now changed the feed URL to http://tools.ietf.org/agenda/atom, and arranged for the feed to be valid also for coming meetings. That way you shouldn't have to re-subscribe to a new feed for each meeting. Henrik _______________________________________________ Tools-discuss mailing list Tools-discuss@ietf.org https://www1.ietf.org/mailman/listinfo/tools-discuss From tools-discuss-bounces@ietf.org Sun Jul 22 16:12:54 2007 Return-path: Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1IChnR-0004NB-Kl; Sun, 22 Jul 2007 16:12:53 -0400 Received: from tools-discuss by megatron.ietf.org with local (Exim 4.43) id 1IChnQ-0004Kl-B8 for tools-discuss-confirm+ok@megatron.ietf.org; Sun, 22 Jul 2007 16:12:52 -0400 Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1IChnP-0004K0-VQ for tools-discuss@ietf.org; Sun, 22 Jul 2007 16:12:51 -0400 Received: from lemland.kurtis.pp.se ([2001:670:87:2::25]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1IChnP-0004Ha-H3 for tools-discuss@ietf.org; Sun, 22 Jul 2007 16:12:51 -0400 Received: from [130.129.16.192] (dhcp-10c0.ietf69.org [130.129.16.192]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (Client did not present a certificate) by lemland.kurtis.pp.se (Postfix) with ESMTP id 22BAF78C97; Sun, 22 Jul 2007 23:12:46 +0300 (EEST) In-Reply-To: <469B6D51.8030607@levkowetz.com> References: <44849987-492C-48D8-B7D2-4B135952A340@kurtis.pp.se> <4697C818.9090401@levkowetz.com> <469B6D51.8030607@levkowetz.com> Mime-Version: 1.0 (Apple Message framework v752.2) Content-Type: text/plain; charset=US-ASCII; format=flowed Message-Id: <5EE4C585-7BF2-4250-AD89-AD88343691E3@kurtis.pp.se> Content-Transfer-Encoding: 7bit From: Kurt Erik Lindqvist Subject: Re: [Tools-discuss] Agenda RSS feed Date: Sun, 22 Jul 2007 22:11:57 +0200 To: Henrik Levkowetz X-Mailer: Apple Mail (2.752.2) X-Spam-Score: 0.1 (/) X-Scan-Signature: 7655788c23eb79e336f5f8ba8bce7906 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 On 16 jul 2007, at 15.06, Henrik Levkowetz wrote: > > > On 2007-07-16 11:24 Kurt Erik Lindqvist said the following: > ... > >> This is great! Thanks a lot for this tool! > > Excellent. > > For early adopters, please note that I've now changed the feed URL > to http://tools.ietf.org/agenda/atom, and arranged for the feed to > be valid also for coming meetings. That way you shouldn't have to > re-subscribe to a new feed for each meeting. cool, this has been really useful! Thanks again! Best regards, - kurtis - _______________________________________________ Tools-discuss mailing list Tools-discuss@ietf.org https://www1.ietf.org/mailman/listinfo/tools-discuss From tools-discuss-bounces@ietf.org Fri Jul 27 01:38:08 2007 Return-path: Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1IEIWd-0003yt-Ti; Fri, 27 Jul 2007 01:38:07 -0400 Received: from tools-discuss by megatron.ietf.org with local (Exim 4.43) id 1IDigz-0001g6-JP for tools-discuss-confirm+ok@megatron.ietf.org; Wed, 25 Jul 2007 11:22:25 -0400 Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1IDigz-0001fy-9P for tools-discuss@ietf.org; Wed, 25 Jul 2007 11:22:25 -0400 Received: from smtp5.smtp.bt.com ([217.32.164.139]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1IDigx-0001cM-Ef for tools-discuss@ietf.org; Wed, 25 Jul 2007 11:22:24 -0400 Received: from E03MVZ4-UKDY.domain1.systemhost.net ([193.113.30.64]) by smtp5.smtp.bt.com with Microsoft SMTPSVC(6.0.3790.1830); Wed, 25 Jul 2007 16:22:22 +0100 X-MimeOLE: Produced By Microsoft Exchange V6.5 Content-class: urn:content-classes:message MIME-Version: 1.0 Date: Wed, 25 Jul 2007 16:22:32 +0100 Message-ID: X-MS-Has-Attach: X-MS-TNEF-Correlator: Thread-Topic: Agenda links from tools pages Thread-Index: AcfOz58AOa0w1vjPTZiSCTNEM65EZg== From: To: X-OriginalArrivalTime: 25 Jul 2007 15:22:22.0370 (UTC) FILETIME=[98FE4020:01C7CECF] X-Spam-Score: 0.0 (/) X-Scan-Signature: f60d0f7806b0c40781eee6b9cd0b2135 X-Mailman-Approved-At: Fri, 27 Jul 2007 01:38:06 -0400 Subject: [Tools-discuss] Agenda links from tools pages 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="===============2140873046==" Errors-To: tools-discuss-bounces@ietf.org This is a multi-part message in MIME format. --===============2140873046== Content-class: urn:content-classes:message Content-Type: multipart/alternative; boundary="----_=_NextPart_001_01C7CECF.98C85B70" This is a multi-part message in MIME format. ------_=_NextPart_001_01C7CECF.98C85B70 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable Hi, The HTML meeting agenda pages from the tools pages are really useful, particularly the links to the actual drafts under discussion. However I would find it even more useful if you gave links to the HTML versions of the drafts as well as the text version... (hope this makes sense) Toby ________________________________________________________________________ ____ Toby Moncaster, Networks Research Centre, BT Research B54/70 Adastral Park, Martlesham Heath, Ipswich, IP53RE, UK. +44 1473 648734=20 ------_=_NextPart_001_01C7CECF.98C85B70 Content-Type: text/html; charset="us-ascii" Content-Transfer-Encoding: quoted-printable Agenda links from tools pages

Hi,

The HTML meeting agenda pages from the = tools pages are really useful, particularly the links to the actual = drafts under discussion. However I would find it even more useful if you = gave links to the HTML versions of the drafts as well as the text = version… (hope this makes sense)

Toby
____________________________________________________________________= ________
Toby Moncaster, = <toby.moncaster@bt.com> Networks Research Centre, BT = Research
B54/70 Adastral Park, Martlesham = Heath, Ipswich, IP53RE, UK.  +44 1473 648734=20

------_=_NextPart_001_01C7CECF.98C85B70-- --===============2140873046== 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 --===============2140873046==-- From tools-discuss-bounces@ietf.org Fri Jul 27 11:45:36 2007 Return-path: Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1IES0W-0007Jd-OF; Fri, 27 Jul 2007 11:45:36 -0400 Received: from tools-discuss by megatron.ietf.org with local (Exim 4.43) id 1IES0V-0007JR-9F for tools-discuss-confirm+ok@megatron.ietf.org; Fri, 27 Jul 2007 11:45:35 -0400 Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1IES0U-0007JJ-Vx for tools-discuss@ietf.org; Fri, 27 Jul 2007 11:45:34 -0400 Received: from [2001:698:9:31:214:22ff:fe21:bb] (helo=merlot.tools.ietf.org) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1IES0T-0007HZ-Ci for tools-discuss@ietf.org; Fri, 27 Jul 2007 11:45:34 -0400 Received: from localhost ([127.0.0.1] helo=chardonnay.local ident=henrik) by merlot.tools.ietf.org with esmtp (Exim 4.67) (envelope-from ) id 1IES0S-0002AC-4l; Fri, 27 Jul 2007 17:45:32 +0200 Message-ID: <46AA131A.6060807@levkowetz.com> Date: Fri, 27 Jul 2007 10:45:30 -0500 From: Henrik Levkowetz User-Agent: Thunderbird 2.0.0.5 (Macintosh/20070716) MIME-Version: 1.0 To: toby.moncaster@bt.com Subject: Re: [Tools-discuss] Agenda links from tools pages References: In-Reply-To: X-Enigmail-Version: 0.95.2 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit X-SA-Exim-Connect-IP: 127.0.0.1 X-SA-Exim-Rcpt-To: toby.moncaster@bt.com, tools-discuss@ietf.org, henrik-sent@levkowetz.com X-SA-Exim-Mail-From: henrik@levkowetz.com X-SA-Exim-Scanned: No (on merlot.tools.ietf.org); SAEximRunCond expanded to false X-Spam-Score: -1.4 (-) X-Scan-Signature: 769a46790fb42fbb0b0cc700c82f7081 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 Toby, On 2007-07-25 10:22 toby.moncaster@bt.com said the following: > Hi, > > The HTML meeting agenda pages from the tools pages are really useful, > particularly the links to the actual drafts under discussion. However I > would find it even more useful if you gave links to the HTML versions of > the drafts as well as the text version... (hope this makes sense) Currently, what happens is this: drafts which are mentioned in the agenda by name (simply "draft-ietf-foo-barbar.txt") are given a link to the HTML version, while drafts which are listed on the agenda with a complete URL are given a link to that URL, which mostly is to a text version of the document, rather than a HTML version. It would be possible to refine this by doing one of the following alternatives: a) Try to convince WG Chairs to list draft names only on the agenda, rather than URLs to drafts -- the draft names would then be linked to the HTML versions. b) Download a copy of the remote URL, convert the text to HTML, and link to the HTML version, rather than to the explicitly given URL. c) See if the last URL path component matches the name of a draft in the archive, and if so, download it and compare the downloaded version to the one in the archive, and if it matches, link to the HTML version in the archive. Otherwise, link to the original URL. d) Do the same verification as in c), but provide a link to a tool which will dynamically generate the html version from the original URL -- this would be more processing intensive, but would not 'lie' quite as much about the URL, since the original URL would be part of the query argument to the linked URL. There may be other alternatives, but there is always a potential issue with letting a generated link point to a different location than the explicitly listed URL. From this perspective, alternative a) above is the best one -- but it is also the one that requires most education and cooperation from all the WG chairs... Viewpoints on which of the above alternatives (or something else entirely) would be most acceptable would be most welcome. Henrik _______________________________________________ Tools-discuss mailing list Tools-discuss@ietf.org https://www1.ietf.org/mailman/listinfo/tools-discuss From tools-discuss-bounces@ietf.org Fri Jul 27 15:34:43 2007 Return-path: Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1IEVaF-00027A-Aa; Fri, 27 Jul 2007 15:34:43 -0400 Received: from tools-discuss by megatron.ietf.org with local (Exim 4.43) id 1IEVaD-000261-Um for tools-discuss-confirm+ok@megatron.ietf.org; Fri, 27 Jul 2007 15:34:41 -0400 Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1IEVaD-00025t-LK for tools-discuss@ietf.org; Fri, 27 Jul 2007 15:34:41 -0400 Received: from balder-227.proper.com ([192.245.12.227]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1IEVaC-0004rJ-7f for tools-discuss@ietf.org; Fri, 27 Jul 2007 15:34:41 -0400 Received: from [130.129.20.216] ([66.103.88.193]) (authenticated bits=0) by balder-227.proper.com (8.13.5/8.13.5) with ESMTP id l6RJYbji084945 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO) for ; Fri, 27 Jul 2007 12:34:38 -0700 (MST) (envelope-from paul.hoffman@vpnc.org) Mime-Version: 1.0 Message-Id: Date: Fri, 27 Jul 2007 14:33:37 -0500 To: tools-discuss@ietf.org From: Paul Hoffman Content-Type: text/plain; charset="us-ascii" ; format="flowed" X-Spam-Score: 0.0 (/) X-Scan-Signature: 9182cfff02fae4f1b6e9349e01d62f32 Subject: [Tools-discuss] Thoughts on an "expert review" 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: , Errors-To: tools-discuss-bounces@ietf.org Hi again. Sam's message on ietf-general a few weeks ago about a mailing list being too heavy-weight for expert review struck a chord. Here is a quick proposal. - The tools team creates a tracker for all expert reviews - Each registry for which there is an expert review has a section in that tracker - When the expert gets a request, they put the request in the tracker - When the expert acts on a request, they update the request's entry - People can follow all sections, or just individual sections, with an Atom feed - No outside comments in the tracker; it is just for telling interested folks what is going on, and to show when things happened Hope this isn't too heavy-weight. The Atom feed in particular would help a bunch of us who have documents with experts where there is only a bit of traffic. --Paul Hoffman, Director --VPN Consortium _______________________________________________ Tools-discuss mailing list Tools-discuss@ietf.org https://www1.ietf.org/mailman/listinfo/tools-discuss From tools-discuss-bounces@ietf.org Fri Jul 27 15:53:27 2007 Return-path: Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1IEVsM-0007uD-Bv; Fri, 27 Jul 2007 15:53:26 -0400 Received: from tools-discuss by megatron.ietf.org with local (Exim 4.43) id 1IEVsK-0007u6-Pa for tools-discuss-confirm+ok@megatron.ietf.org; Fri, 27 Jul 2007 15:53:24 -0400 Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1IEVsK-0007ty-3Z for tools-discuss@ietf.org; Fri, 27 Jul 2007 15:53:24 -0400 Received: from [2001:698:9:31:214:22ff:fe21:bb] (helo=merlot.tools.ietf.org) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1IEVsJ-0005ET-KS for tools-discuss@ietf.org; Fri, 27 Jul 2007 15:53:24 -0400 Received: from localhost ([127.0.0.1] helo=chardonnay.local ident=henrik) by merlot.tools.ietf.org with esmtp (Exim 4.67) (envelope-from ) id 1IEVsI-0002f0-Dh; Fri, 27 Jul 2007 21:53:22 +0200 Message-ID: <46AA4D31.4030101@levkowetz.com> Date: Fri, 27 Jul 2007 14:53:21 -0500 From: Henrik Levkowetz User-Agent: Thunderbird 2.0.0.5 (Macintosh/20070716) MIME-Version: 1.0 To: Paul Hoffman Subject: Re: [Tools-discuss] Thoughts on an "expert review" tracker References: In-Reply-To: X-Enigmail-Version: 0.95.2 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit X-SA-Exim-Connect-IP: 127.0.0.1 X-SA-Exim-Rcpt-To: paul.hoffman@vpnc.org, tools-discuss@ietf.org, henrik-sent@levkowetz.com X-SA-Exim-Mail-From: henrik@levkowetz.com X-SA-Exim-Scanned: No (on merlot.tools.ietf.org); SAEximRunCond expanded to false X-Spam-Score: -1.4 (-) X-Scan-Signature: 8b431ad66d60be2d47c7bfeb879db82c 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, On 2007-07-27 14:33 Paul Hoffman said the following: > Hi again. Sam's message on ietf-general a few weeks ago about a > mailing list being too heavy-weight for expert review struck a chord. > Here is a quick proposal. > > - The tools team creates a tracker for all expert reviews Syncronicity. As it happens, I got a request for a way to support review handling for an area directorate earlier this week, with the added specification that the particular requirements and tools support considered for the GenArt review team wasn't quite what was needed and wanted. After some discussion it seemed that Trac's issue tracker, possibly enhanced by a plugin for some special support functions, would work just fine. Since each area already has a Trac instance (although they are not widely known and used yet) it was dead easy to point to that. > - Each registry for which there is an expert review has a section in > that tracker Would this be orthogonal to area review teams, or overlapping? > - When the expert gets a request, they put the request in the tracker > > - When the expert acts on a request, they update the request's entry > > - People can follow all sections, or just individual sections, with > an Atom feed Right. The current Trac feed is RSS, but I think we can easily fix that. > - No outside comments in the tracker; it is just for telling > interested folks what is going on, and to show when things happened > > Hope this isn't too heavy-weight. The Atom feed in particular would > help a bunch of us who have documents with experts where there is > only a bit of traffic. Given the syncronicity noted above, I think this is a good track to explore. Henrik _______________________________________________ Tools-discuss mailing list Tools-discuss@ietf.org https://www1.ietf.org/mailman/listinfo/tools-discuss From tools-discuss-bounces@ietf.org Sat Jul 28 10:15:51 2007 Return-path: Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1IEn59-0005Eo-N7; Sat, 28 Jul 2007 10:15:47 -0400 Received: from tools-discuss by megatron.ietf.org with local (Exim 4.43) id 1IEn58-0005Bh-Ru for tools-discuss-confirm+ok@megatron.ietf.org; Sat, 28 Jul 2007 10:15:46 -0400 Received: from [10.90.34.44] (helo=chiedprmail1.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1IEn58-00059G-Gq for tools-discuss@ietf.org; Sat, 28 Jul 2007 10:15:46 -0400 Received: from balder-227.proper.com ([192.245.12.227]) by chiedprmail1.ietf.org with esmtp (Exim 4.43) id 1IEn58-0004tH-4M for tools-discuss@ietf.org; Sat, 28 Jul 2007 10:15:46 -0400 Received: from [10.20.30.108] (dsl-63-249-108-169.cruzio.com [63.249.108.169]) (authenticated bits=0) by balder-227.proper.com (8.13.5/8.13.5) with ESMTP id l6SEFg4l060248 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Sat, 28 Jul 2007 07:15:44 -0700 (MST) (envelope-from paul.hoffman@vpnc.org) Mime-Version: 1.0 Message-Id: In-Reply-To: <46AA4D31.4030101@levkowetz.com> References: <46AA4D31.4030101@levkowetz.com> Date: Fri, 27 Jul 2007 13:18:32 -0700 To: Henrik Levkowetz From: Paul Hoffman Subject: Re: [Tools-discuss] Thoughts on an "expert review" tracker Content-Type: text/plain; charset="us-ascii" ; format="flowed" X-Spam-Score: 1.8 (+) X-Scan-Signature: cf4fa59384e76e63313391b70cd0dd25 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 At 2:53 PM -0500 7/27/07, Henrik Levkowetz wrote: > > - Each registry for which there is an expert review has a section in >> that tracker > >Would this be orthogonal to area review teams, or overlapping? Orthogonal. Expert review is for IANA registries, which is unrelated to area review teams. >Right. The current Trac feed is RSS, but I think we can easily fix >that. Dogfood. Let's eat our own dogfood. --Paul Hoffman, Director --VPN Consortium _______________________________________________ Tools-discuss mailing list Tools-discuss@ietf.org https://www1.ietf.org/mailman/listinfo/tools-discuss From tools-discuss-bounces@ietf.org Tue Jul 31 07:34:00 2007 Return-path: Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1IFpzC-0005RF-RO; Tue, 31 Jul 2007 07:33:58 -0400 Received: from tools-discuss by megatron.ietf.org with local (Exim 4.43) id 1IFpzB-0005Ha-7f for tools-discuss-confirm+ok@megatron.ietf.org; Tue, 31 Jul 2007 07:33:57 -0400 Received: from [10.90.34.44] (helo=chiedprmail1.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1IFpz9-0005Gu-6P for tools-discuss@ietf.org; Tue, 31 Jul 2007 07:33:56 -0400 Received: from sj-iport-6.cisco.com ([171.71.176.117]) by chiedprmail1.ietf.org with esmtp (Exim 4.43) id 1IFpz8-0005aO-OL for tools-discuss@ietf.org; Tue, 31 Jul 2007 07:33:55 -0400 Received: from sj-dkim-4.cisco.com ([171.71.179.196]) by sj-iport-6.cisco.com with ESMTP; 31 Jul 2007 04:33:54 -0700 X-IronPort-Anti-Spam-Filtered: true X-IronPort-Anti-Spam-Result: Ah4FABa6rkarR7PE/2dsb2JhbABC X-IronPort-AV: i="4.19,203,1183359600"; d="scan'208"; a="191668456:sNHT25622955" Received: from sj-core-1.cisco.com (sj-core-1.cisco.com [171.71.177.237]) by sj-dkim-4.cisco.com (8.12.11/8.12.11) with ESMTP id l6VBXsi0021439; Tue, 31 Jul 2007 04:33:54 -0700 Received: from xbh-sjc-231.amer.cisco.com (xbh-sjc-231.cisco.com [128.107.191.100]) by sj-core-1.cisco.com (8.12.10/8.12.6) with ESMTP id l6VBXqA0015596; Tue, 31 Jul 2007 11:33:52 GMT Received: from xfe-sjc-212.amer.cisco.com ([171.70.151.187]) by xbh-sjc-231.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.1830); Tue, 31 Jul 2007 04:33:51 -0700 Received: from [222.66.35.150] ([10.21.81.174]) by xfe-sjc-212.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.1830); Tue, 31 Jul 2007 04:33:51 -0700 In-Reply-To: References: Mime-Version: 1.0 (Apple Message framework v752.3) Content-Type: text/plain; charset=US-ASCII; delsp=yes; format=flowed Message-Id: <908DE784-1783-4E09-9268-F328DA3C9A27@cisco.com> Content-Transfer-Encoding: 7bit From: Fred Baker Subject: Re: [Tools-discuss] Thoughts on an "expert review" tracker Date: Tue, 31 Jul 2007 16:21:09 +0800 To: Paul Hoffman X-Mailer: Apple Mail (2.752.3) X-OriginalArrivalTime: 31 Jul 2007 11:33:51.0692 (UTC) FILETIME=[AB4550C0:01C7D366] DKIM-Signature: v=0.5; a=rsa-sha256; q=dns/txt; l=1468; t=1185881634; x=1186745634; c=relaxed/simple; s=sjdkim4002; h=Content-Type:From:Subject:Content-Transfer-Encoding:MIME-Version; d=cisco.com; i=fred@cisco.com; z=From:=20Fred=20Baker=20 |Subject:=20Re=3A=20[Tools-discuss]=20Thoughts=20on=20an=20=22expert=20re view=22=20tracker |Sender:=20; bh=9l7sqeflZG9JlLit4wHrfJ1Nh7DkymSolTrbtEgeRAs=; b=mSCI5zdBrUDIW4uZRCfEO4Ji5VCBp9lNn29foBUoiMCSzNLk//r7a+I8RgZBQt8XpcEys0TR 9rdM/3gcnZeIZBvSI5XNaO2CgPrmu4IPJgSxjVW4hXOuT8t9UC8KOORk; Authentication-Results: sj-dkim-4; header.From=fred@cisco.com; dkim=pass (si g from cisco.com/sjdkim4002 verified; ); X-Spam-Score: 3.1 (+++) X-Scan-Signature: 8b30eb7682a596edff707698f4a80f7d 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 would like to have a general "review tracker" usable by the WGs. In the WGs, it would be nice if folks making specific comments on a draft could log them and the author could log his response. Not that every one would get "updated in version 12", but we would have a record of the discussion. On Jul 28, 2007, at 3:33 AM, Paul Hoffman wrote: > Hi again. Sam's message on ietf-general a few weeks ago about a > mailing list being too heavy-weight for expert review struck a > chord. Here is a quick proposal. > > - The tools team creates a tracker for all expert reviews > > - Each registry for which there is an expert review has a section > in that tracker > > - When the expert gets a request, they put the request in the tracker > > - When the expert acts on a request, they update the request's entry > > - People can follow all sections, or just individual sections, with > an Atom feed > > - No outside comments in the tracker; it is just for telling > interested folks what is going on, and to show when things happened > > Hope this isn't too heavy-weight. The Atom feed in particular would > help a bunch of us who have documents with experts where there is > only a bit of traffic. > > --Paul Hoffman, Director > --VPN Consortium > > > _______________________________________________ > 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 Tue Jul 31 10:14:24 2007 Return-path: Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1IFsUR-0000a9-OA; Tue, 31 Jul 2007 10:14:23 -0400 Received: from tools-discuss by megatron.ietf.org with local (Exim 4.43) id 1IFsUP-0000a4-DZ for tools-discuss-confirm+ok@megatron.ietf.org; Tue, 31 Jul 2007 10:14:21 -0400 Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1IFsUP-0000Zw-47 for tools-discuss@ietf.org; Tue, 31 Jul 2007 10:14:21 -0400 Received: from balder-227.proper.com ([192.245.12.227]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1IFsUN-0001VL-K5 for tools-discuss@ietf.org; Tue, 31 Jul 2007 10:14:21 -0400 Received: from [10.20.30.108] (dsl-63-249-108-169.cruzio.com [63.249.108.169]) (authenticated bits=0) by balder-227.proper.com (8.13.5/8.13.5) with ESMTP id l6VEEDbR043582 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Tue, 31 Jul 2007 07:14:16 -0700 (MST) (envelope-from paul.hoffman@vpnc.org) Mime-Version: 1.0 Message-Id: In-Reply-To: <908DE784-1783-4E09-9268-F328DA3C9A27@cisco.com> References: <908DE784-1783-4E09-9268-F328DA3C9A27@cisco.com> Date: Tue, 31 Jul 2007 07:14:05 -0700 To: Fred Baker From: Paul Hoffman Subject: Re: [Tools-discuss] Thoughts on an "expert review" tracker Content-Type: text/plain; charset="us-ascii" ; format="flowed" X-Spam-Score: 0.0 (/) X-Scan-Signature: 39bd8f8cbb76cae18b7e23f7cf6b2b9f 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 Please note that these are orthogonal requests. When I was asking for a tracker for "expert reviews", I was talking about experts in the IANA sense, people who are gateways to (some) IANA registries. --Paul Hoffman At 4:21 PM +0800 7/31/07, Fred Baker wrote: >I would like to have a general "review tracker" usable by the WGs. >In the WGs, it would be nice if folks making specific comments on a >draft could log them and the author could log his response. Not that >every one would get "updated in version 12", but we would have a >record of the discussion. > >On Jul 28, 2007, at 3:33 AM, Paul Hoffman wrote: > >>Hi again. Sam's message on ietf-general a few weeks ago about a >>mailing list being too heavy-weight for expert review struck a >>chord. Here is a quick proposal. >> >>- The tools team creates a tracker for all expert reviews >> >>- Each registry for which there is an expert review has a section >>in that tracker >> >>- When the expert gets a request, they put the request in the tracker >> >>- When the expert acts on a request, they update the request's entry >> >>- People can follow all sections, or just individual sections, with >>an Atom feed >> >>- No outside comments in the tracker; it is just for telling >>interested folks what is going on, and to show when things happened >> >>Hope this isn't too heavy-weight. The Atom feed in particular would >>help a bunch of us who have documents with experts where there is >>only a bit of traffic. _______________________________________________ Tools-discuss mailing list Tools-discuss@ietf.org https://www1.ietf.org/mailman/listinfo/tools-discuss