From mnot@mnot.net Tue Jan 1 22:28:10 2013 Return-Path: X-Original-To: tools-discuss@ietfa.amsl.com Delivered-To: tools-discuss@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id DB50221F911F for ; Tue, 1 Jan 2013 22:28:10 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -103.748 X-Spam-Level: X-Spam-Status: No, score=-103.748 tagged_above=-999 required=5 tests=[AWL=-1.149, BAYES_00=-2.599, USER_IN_WHITELIST=-100] Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 0mZlK4yNrH5e for ; Tue, 1 Jan 2013 22:28:10 -0800 (PST) Received: from mxout-08.mxes.net (mxout-08.mxes.net [216.86.168.183]) by ietfa.amsl.com (Postfix) with ESMTP id 42A1E21F911E for ; Tue, 1 Jan 2013 22:28:10 -0800 (PST) Received: from mnot-mini.mnot.net (unknown [118.209.74.65]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (No client certificate requested) by smtp.mxes.net (Postfix) with ESMTPSA id 2E63F509B5 for ; Wed, 2 Jan 2013 01:28:08 -0500 (EST) From: Mark Nottingham Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: quoted-printable Message-Id: Date: Wed, 2 Jan 2013 17:28:05 +1100 To: Tools discussion Mime-Version: 1.0 (Mac OS X Mail 6.2 \(1499\)) X-Mailer: Apple Mail (2.1499) Subject: [Tools-discuss] IDNITs check in submission inexplicably failing X-BeenThere: tools-discuss@ietf.org X-Mailman-Version: 2.1.12 Precedence: list List-Id: IETF Tools Discussion List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 02 Jan 2013 06:28:11 -0000 When I try to submit, I get: Your draft has NOT been verified to meet IDNITS requirements. (View = IDNITS Results) The link to the results shows: ---8<--- idnits 2.12.14=20 /a/www/www6s/staging/draft-ietf-appsawg-json-pointer-08.txt: --->8--- ... which leads me to suspect some sort of error. This is what I get when I run idnits 2.12.13 (latest available on the = site): ---8<--- idnits 2.12.13=20 tmp/draft-ietf-appsawg-json-pointer-08.txt: Checking boilerplate required by RFC 5378 and the IETF Trust (see http://trustee.ietf.org/license-info): = --------------------------------------------------------------------------= -- No issues found here. Checking nits according to = http://www.ietf.org/id-info/1id-guidelines.txt: = --------------------------------------------------------------------------= -- No issues found here. Checking nits according to http://www.ietf.org/id-info/checklist : = --------------------------------------------------------------------------= -- No issues found here. Miscellaneous warnings: = --------------------------------------------------------------------------= -- No issues found here. Checking references for intended status: Proposed Standard = --------------------------------------------------------------------------= -- (See RFCs 3967 and 4897 for information about using normative = references to lower-maturity documents in RFCs) ** Downref: Normative reference to an Informational RFC: RFC 4627 Summary: 1 error (**), 0 warnings (=3D=3D), 0 comments (--). Run idnits with the --verbose option for more detailed information = about the items above. --->8--- The downref hasn't been a problem submitting in the past. Cheers, -- Mark Nottingham http://www.mnot.net/ From ietf@rozanak.com Thu Jan 3 08:06:22 2013 Return-Path: X-Original-To: tools-discuss@ietfa.amsl.com Delivered-To: tools-discuss@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 86B2721F85E2 for ; Thu, 3 Jan 2013 08:06:22 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -1.924 X-Spam-Level: X-Spam-Status: No, score=-1.924 tagged_above=-999 required=5 tests=[AWL=0.675, BAYES_00=-2.599] Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 6r2++XP7LqqQ for ; Thu, 3 Jan 2013 08:06:22 -0800 (PST) Received: from mout.perfora.net (mout.perfora.net [74.208.4.195]) by ietfa.amsl.com (Postfix) with ESMTP id D526321F8C46 for ; Thu, 3 Jan 2013 08:06:21 -0800 (PST) Received: from kopoli (g225034069.adsl.alicedsl.de [92.225.34.69]) by mrelay.perfora.net (node=mrus4) with ESMTP (Nemesis) id 0Lz3f6-1SvVoN0GqO-0142bS; Thu, 03 Jan 2013 11:06:18 -0500 From: "Hosnieh Rafiee" To: References: In-Reply-To: Date: Thu, 3 Jan 2013 17:06:11 +0100 Message-ID: <000001cde9cc$430195f0$c904c1d0$@rozanak.com> MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit X-Mailer: Microsoft Outlook 14.0 Thread-Index: AQFpAABeQJT9r54BEl/0VTLKug7ZS5kBl1EQ Content-Language: en-us X-Provags-ID: V02:K0:tOWVR7qZLw/EEqgzg+HQpat0KNEnFqbXSctcDay/NPt MKRjrksQ73ifEpegFgWENLxbI5y2GYiWyo8RXiYaDJBOAnp+QE T87ZNUA3KcXBNtV+0/+M90YrwIaSn2mWNC6qUspr9GhaMQQv7x kGsYd7GoS6G/rl+Kp+Lk1F22uOv4ZCJAcLv/4kxoOTjQUWMQ6x /PKuPEvZcDRQIAo4M69XDRGNVSl9F7WXM9fSnP3nvikpRAIIbv xWTKAmGsKDXsri4Zoynbe/sc4MHIV2E5yvpmfJTf7mbDfrixk6 F6mBz/wvpPRvykdkhVbj/uDpYR/03YM4po6SF+p8HZLu1iG/0Y rRNiGBTpX1eQ6oUk1iYY= Cc: tools-discuss@ietf.org Subject: Re: [Tools-discuss] Tools-discuss Digest, Vol 99, Issue 1 X-BeenThere: tools-discuss@ietf.org X-Mailman-Version: 2.1.12 Precedence: list List-Id: IETF Tools Discussion List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 03 Jan 2013 16:06:22 -0000 >When I try to submit, I get: >Your draft has NOT been verified to meet IDNITS requirements. (View IDNITS Results) >The link to the results shows: I receive the same error message while I also tried to resolve any error I received during checking it by http://www.ietf.org/tools/idnits/ the last result is as follow. However, I still have problem submitting my draft. I reported that problem to ietf-action. I receive empty message in view idnits results. Yesterday I spent a lot of time to figure out this but I was not successful. No issues found here. Checking nits according to http://www.ietf.org/id-info/1id-guidelines.txt: ---------------------------------------------------------------------------- No issues found here. Checking nits according to http://www.ietf.org/id-info/checklist : ---------------------------------------------------------------------------- No issues found here. Miscellaneous warnings: ---------------------------------------------------------------------------- == Couldn't figure out when the document was first submitted -- there may comments or warnings related to the use of a disclaimer for pre-RFC5378 work that could not be issued because of this. Please check the Legal Provisions document at http://trustee.ietf.org/license-info to determine if you need the pre-RFC5378 disclaimer. Checking references for intended status: Proposed Standard ---------------------------------------------------------------------------- (See RFCs 3967 and 4897 for information about using normative references to lower-maturity documents in RFCs) No issues found here. Summary: 0 errors (**), 0 flaws (~~), 1 warning (==), 0 comments (--). ---------------------------------------------------------------------------- ---- From rcross@amsl.com Thu Jan 3 14:22:02 2013 Return-Path: X-Original-To: tools-discuss@ietfa.amsl.com Delivered-To: tools-discuss@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 4F89E21F876E for ; Thu, 3 Jan 2013 14:22:02 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -2.599 X-Spam-Level: X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599] Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 8SoyRFCt4g38 for ; Thu, 3 Jan 2013 14:22:01 -0800 (PST) Received: from mail.amsl.com (mail.amsl.com [IPv6:2001:1890:123a::1:14]) by ietfa.amsl.com (Postfix) with ESMTP id F320921F87D1 for ; Thu, 3 Jan 2013 14:22:00 -0800 (PST) Received: from localhost (c8a.amsl.com [127.0.0.1]) by c8a.amsl.com (Postfix) with ESMTP id A3DC21243EC; Thu, 3 Jan 2013 14:22:00 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com Received: from c8a.amsl.com ([127.0.0.1]) by localhost (c8a.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id PTHyxzNX4XgT; Thu, 3 Jan 2013 14:22:00 -0800 (PST) Received: from [10.0.1.3] (c-76-104-194-254.hsd1.wa.comcast.net [76.104.194.254]) by c8a.amsl.com (Postfix) with ESMTPSA id 36CAC1243E8; Thu, 3 Jan 2013 14:22:00 -0800 (PST) Mime-Version: 1.0 (Apple Message framework v1085) Content-Type: text/plain; charset=us-ascii From: Ryan Cross In-Reply-To: Date: Thu, 3 Jan 2013 14:21:58 -0800 Content-Transfer-Encoding: quoted-printable Message-Id: <72BBF120-9C2F-4A3B-9122-2B2F39339C2E@amsl.com> References: To: Marc Blanchet X-Mailer: Apple Mail (2.1085) Cc: Tools discussion Subject: Re: [Tools-discuss] material manager X-BeenThere: tools-discuss@ietf.org X-Mailman-Version: 2.1.12 Precedence: list List-Id: IETF Tools Discussion List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 03 Jan 2013 22:22:02 -0000 Hi Marc, Since there is only one "Minutes" and one "Agenda" file per session it = was easy to support the simple re-upload to replace existing files. For = slides this doesn't work as well. The user would have to enter an = identical Name of Presentation which opens the door for typos. So the = replace link seemed appropriate. =20 I see what you are saying about consistency. I can look into adding the = replace link. Thanks, Ryan Cross AMS On Nov 6, 2012, at 6:37 AM, Marc Blanchet wrote: > small UI comment: > if one want to replace slides, there is a "replace" link aside from = the slides. =20 > if one want to replace minutes, one does not know what to do, since = only "delete" is available. So I re-upload the new minutes and they got = replaced. >=20 > for consistency, would probably be good to have a "replace" link for = minutes and agenda. >=20 > (but I can survive with the current UI). >=20 > Marc. >=20 > _______________________________________________ > Tools-discuss mailing list > Tools-discuss@ietf.org > https://www.ietf.org/mailman/listinfo/tools-discuss >=20 From rcross@amsl.com Thu Jan 3 14:39:57 2013 Return-Path: X-Original-To: tools-discuss@ietfa.amsl.com Delivered-To: tools-discuss@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 28AB921F8DD2 for ; Thu, 3 Jan 2013 14:39:57 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -2.599 X-Spam-Level: X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599] Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id JhLVKsXHEB2W for ; Thu, 3 Jan 2013 14:39:56 -0800 (PST) Received: from mail.amsl.com (mail.amsl.com [IPv6:2001:1890:123a::1:14]) by ietfa.amsl.com (Postfix) with ESMTP id 6006E21F8DDA for ; Thu, 3 Jan 2013 14:39:56 -0800 (PST) Received: from localhost (c8a.amsl.com [127.0.0.1]) by c8a.amsl.com (Postfix) with ESMTP id 3CFB0124404; Thu, 3 Jan 2013 14:39:56 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com Received: from c8a.amsl.com ([127.0.0.1]) by localhost (c8a.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Ni72NFkSyR8B; Thu, 3 Jan 2013 14:39:56 -0800 (PST) Received: from [10.0.1.3] (c-76-104-194-254.hsd1.wa.comcast.net [76.104.194.254]) by c8a.amsl.com (Postfix) with ESMTPSA id C7385124401; Thu, 3 Jan 2013 14:39:55 -0800 (PST) Mime-Version: 1.0 (Apple Message framework v1085) Content-Type: text/plain; charset=windows-1252 From: Ryan Cross In-Reply-To: <8C48B86A895913448548E6D15DA7553B19701D@xmb-rcd-x09.cisco.com> Date: Thu, 3 Jan 2013 14:39:54 -0800 Content-Transfer-Encoding: quoted-printable Message-Id: <055F7223-E064-4334-ABF1-6D85EBB2B231@amsl.com> References: <8C48B86A895913448548E6D15DA7553B196887@xmb-rcd-x09.cisco.com> <0F703724-B958-464D-AE20-D651EB035ADE@gmail.com> <609B85CB-7988-4BC8-8BA6-43FDCFD827DF@amsl.com> <5E54BF68-E522-4659-8099-933700C83622@amsl.com> <8C48B86A895913448548E6D15DA7553B19701D@xmb-rcd-x09.cisco.com> To: Fred Baker (fred) X-Mailer: Apple Mail (2.1085) Cc: Alexa Morris , "tools-discuss@ietf.org Discussion" Subject: Re: [Tools-discuss] Comment on new meeting materials manager X-BeenThere: tools-discuss@ietf.org X-Mailman-Version: 2.1.12 Precedence: list List-Id: IETF Tools Discussion List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 03 Jan 2013 22:39:57 -0000 Hi Fred, I've removed the vertical containment on the slide sort so it's easier = to move items to the top or bottom of the list. Ryan On Nov 5, 2012, at 3:24 PM, Fred Baker (fred) wrote: >=20 > On Nov 5, 2012, at 2:13 PM, Ryan Cross wrote: >=20 >> I noticed this too and discovered that you can achieve the desired = results by being precise when "grabbing" the item to be re-ordered. = Clicking on the upper portion of the row when dragging to the top and = the lower portion of the row when dragging to the bottom. >=20 > I don't think my description of that would include the word = "intuitive" :-) >=20 >> Alternatively, I can remove the constraints on the draggable area. = Then you can drag the item beyond the list area (ie, above it) and it = will snap into first place. I felt this behavior was visually = inconsistent though, when a slide item is dragged into adjacent areas of = the page. >=20 > That might make sense. Make it extend beyond the actual list by a = length roughly equal to the width of a line, and you should be OK. It's = more consistent than having to do a completely different action (move to = second-to-last and then move the last) in the special case=85 >=20 > Consider this. Imagine that you have a meeting with two presentations, = and you need to invert their order. Yes, you could use the arrows. But = imagine you're used to drag-and-drop and not thinking about that. You = can't change their order by drag-and-drop. >=20 >> Ryan >>=20 >> On Nov 5, 2012, at 12:18 PM, Alexa Morris wrote: >>=20 >>> That's good feedback and I'm copying Ryan so that he can look into = this when he has time. >>>=20 >>> Alexa >>>=20 >>>=20 >>> On Nov 5, 2012, at 9:14 AM, Bob Hinden wrote: >>>=20 >>>> Fred, >>>>=20 >>>> On Nov 5, 2012, at 12:08 PM, Fred Baker (fred) wrote: >>>>=20 >>>>> (a) I like it.=20 >>>>>=20 >>>>> (b) I do notice one glitch with the "drag" function. This is that = I cannot move a presentation to the first or last positions; I can move = it between any two, but not "before the first" and not "after the last". = What I am doing right now is moving things to the second or = second-to-last position, and then move the first/last to achieve the = intended result. >>>>=20 >>>> I saw that too. >>>>=20 >>>> Bob >>>>=20 >>>>=20 >>>>=20 >>>=20 >>> ---------- >>> Alexa Morris / Executive Director / IETF >>> 48377 Fremont Blvd., Suite 117, Fremont, CA 94538 >>> Phone: +1.510.492.4089 / Fax: +1.510.492.4001 >>> Email: amorris@amsl.com >>>=20 >>> Managed by Association Management Solutions (AMS) >>> Forum Management, Meeting and Event Planning >>> www.amsl.com >>>=20 >>=20 >=20 > ---------------------------------------------------- > The ignorance of how to use new knowledge stockpiles exponentially.=20 > - Marshall McLuhan >=20 From lars@netapp.com Mon Jan 7 04:36:09 2013 Return-Path: X-Original-To: tools-discuss@ietfa.amsl.com Delivered-To: tools-discuss@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 59D5221F859B for ; Mon, 7 Jan 2013 04:36:09 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -10.484 X-Spam-Level: X-Spam-Status: No, score=-10.484 tagged_above=-999 required=5 tests=[AWL=0.115, BAYES_00=-2.599, RCVD_IN_DNSWL_HI=-8] Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id ntGbeADvV2m6 for ; Mon, 7 Jan 2013 04:36:08 -0800 (PST) Received: from mx12.netapp.com (mx12.netapp.com [216.240.18.77]) by ietfa.amsl.com (Postfix) with ESMTP id 7662921F858C for ; Mon, 7 Jan 2013 04:36:08 -0800 (PST) X-IronPort-AV: E=Sophos;i="4.84,424,1355126400"; d="scan'208";a="5324629" Received: from smtp2.corp.netapp.com ([10.57.159.114]) by mx12-out.netapp.com with ESMTP; 07 Jan 2013 04:36:08 -0800 Received: from vmwexceht02-prd.hq.netapp.com (vmwexceht02-prd.hq.netapp.com [10.106.76.240]) by smtp2.corp.netapp.com (8.13.1/8.13.1/NTAP-1.6) with ESMTP id r07Ca8Si008184 for ; Mon, 7 Jan 2013 04:36:08 -0800 (PST) Received: from SACEXCMBX06-PRD.hq.netapp.com ([169.254.8.16]) by vmwexceht02-prd.hq.netapp.com ([10.106.76.240]) with mapi id 14.02.0328.009; Mon, 7 Jan 2013 04:36:07 -0800 From: "Eggert, Lars" To: Tools Team Discussion Thread-Topic: change which stream an ID is on Thread-Index: AQHN7NOQoKD/deJee0Ss6YuX76GxQw== Date: Mon, 7 Jan 2013 12:36:07 +0000 Message-ID: Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: x-originating-ip: [10.106.53.51] Content-Type: text/plain; charset="us-ascii" Content-ID: Content-Transfer-Encoding: quoted-printable MIME-Version: 1.0 Subject: [Tools-discuss] change which stream an ID is on X-BeenThere: tools-discuss@ietf.org X-Mailman-Version: 2.1.12 Precedence: list List-Id: IETF Tools Discussion List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 07 Jan 2013 12:36:09 -0000 Hi, in the datatracker, who can set the stream information for a document? For example, https://datatracker.ietf.org/doc/draft-kutscher-icnrg-netinf-p= roto/ says "No stream defined" and I consequently cannot modify the stream = state like I can for documents on my (the IRTF) stream, such as https://dat= atracker.ietf.org/doc/draft-irtf-cfrg-cipher-catalog/ It would be great if stream owners were allowed to modify the stream a docu= ment is on (maybe only when none is set, if we don't trust these guys). Lars= From olau@iola.dk Mon Jan 7 05:27:27 2013 Return-Path: X-Original-To: tools-discuss@ietfa.amsl.com Delivered-To: tools-discuss@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id B7B5F21F8792 for ; Mon, 7 Jan 2013 05:27:27 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -2.977 X-Spam-Level: X-Spam-Status: No, score=-2.977 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, FM_FORGED_GMAIL=0.622, RCVD_IN_DNSWL_LOW=-1] Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id hbPUfTdc9Cn2 for ; Mon, 7 Jan 2013 05:27:27 -0800 (PST) Received: from mail-we0-f173.google.com (mail-we0-f173.google.com [74.125.82.173]) by ietfa.amsl.com (Postfix) with ESMTP id ED2D121F853C for ; Mon, 7 Jan 2013 05:27:26 -0800 (PST) Received: by mail-we0-f173.google.com with SMTP id z2so9655927wey.4 for ; Mon, 07 Jan 2013 05:27:25 -0800 (PST) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=x-received:mime-version:in-reply-to:references:from:date:message-id :subject:to:content-type:x-gm-message-state; bh=Ag2fb9dMdGNtPQWBXLBndWrqj0k2v8/mLXvDYjZQXmM=; b=jud7Gucqp6rL2lci9E+zEUmx0TQHkutn1IExIiXG3FQNGno22b3Bmk6AjwMt45IyQY mIQfFGZZxWHwz9kvOHstexiMzDilGp6WufqIXaRNk2FKU7XVJvm+0uAcSyqpOkUPrJz0 6Xdqwa+YyXF+o401SRVhDNZ5RxXgDm0oja6Rju8Q/oF8ZP8ymIF/RZl1EiQHNRoZanf+ 6UqO26jgbhMTmtsN+LOymKTP1C3b2FHh0B1F78eDYR5UW64gV9JQcQlp0+AOzsoSV9T4 gG/FeuU5qvYlWo/t1mRzhmUTFco1yiKyOlCp74TPiv5FraRPeLQ1/s49gEVQAr8SAQti jpaQ== X-Received: by 10.180.84.131 with SMTP id z3mr9187222wiy.25.1357565245796; Mon, 07 Jan 2013 05:27:25 -0800 (PST) MIME-Version: 1.0 Received: by 10.194.136.226 with HTTP; Mon, 7 Jan 2013 05:27:05 -0800 (PST) In-Reply-To: References: From: Ole Laursen Date: Mon, 7 Jan 2013 14:27:05 +0100 Message-ID: To: Tools Team Discussion Content-Type: text/plain; charset=ISO-8859-1 X-Gm-Message-State: ALoCoQk8lG2eM2gEtQut37SEOTR6jMqlAkLOHqirTvmhcpZsdRkfYkaHRkBJZ4OENV5jiARe7SG3 Subject: Re: [Tools-discuss] change which stream an ID is on X-BeenThere: tools-discuss@ietf.org X-Mailman-Version: 2.1.12 Precedence: list List-Id: IETF Tools Discussion List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 07 Jan 2013 13:27:27 -0000 2013/1/7 Eggert, Lars : > in the datatracker, who can set the stream information for a document? It looks like ADs and the Secretariat can change the stream the document is on (in change_stream in ietf/idrfc/views_edit.py). I think it should be easy to relax this check enough to let stream owners through. Ole From lars@netapp.com Tue Jan 8 02:53:26 2013 Return-Path: X-Original-To: tools-discuss@ietfa.amsl.com Delivered-To: tools-discuss@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id AF8DA21F8E7D for ; Tue, 8 Jan 2013 02:53:26 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -10.515 X-Spam-Level: X-Spam-Status: No, score=-10.515 tagged_above=-999 required=5 tests=[AWL=0.084, BAYES_00=-2.599, RCVD_IN_DNSWL_HI=-8] Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id gPmMa7fZwMdD for ; Tue, 8 Jan 2013 02:53:26 -0800 (PST) Received: from mx12.netapp.com (mx12.netapp.com [216.240.18.77]) by ietfa.amsl.com (Postfix) with ESMTP id 1674421F8E7C for ; Tue, 8 Jan 2013 02:53:23 -0800 (PST) X-IronPort-AV: E=Sophos;i="4.84,430,1355126400"; d="scan'208";a="5643643" Received: from smtp1.corp.netapp.com ([10.57.156.124]) by mx12-out.netapp.com with ESMTP; 08 Jan 2013 02:53:22 -0800 Received: from vmwexceht02-prd.hq.netapp.com (vmwexceht02-prd.hq.netapp.com [10.106.76.240]) by smtp1.corp.netapp.com (8.13.1/8.13.1/NTAP-1.6) with ESMTP id r08ArMcn024733; Tue, 8 Jan 2013 02:53:22 -0800 (PST) Received: from SACEXCMBX06-PRD.hq.netapp.com ([169.254.8.16]) by vmwexceht02-prd.hq.netapp.com ([10.106.76.240]) with mapi id 14.02.0328.009; Tue, 8 Jan 2013 02:53:22 -0800 From: "Eggert, Lars" To: Ole Laursen Thread-Topic: [Tools-discuss] change which stream an ID is on Thread-Index: AQHN7NOQoKD/deJee0Ss6YuX76GxQ5g+YdOAgAFnYYA= Date: Tue, 8 Jan 2013 10:53:20 +0000 Message-ID: References: In-Reply-To: Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: x-originating-ip: [10.104.60.114] Content-Type: text/plain; charset="us-ascii" Content-ID: <6CD1AACF7421134C8803EA001ABBECF7@tahoe.netapp.com> Content-Transfer-Encoding: quoted-printable MIME-Version: 1.0 Cc: Tools Team Discussion Subject: Re: [Tools-discuss] change which stream an ID is on X-BeenThere: tools-discuss@ietf.org X-Mailman-Version: 2.1.12 Precedence: list List-Id: IETF Tools Discussion List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 08 Jan 2013 10:53:26 -0000 On Jan 7, 2013, at 14:27, Ole Laursen wrote: > 2013/1/7 Eggert, Lars : >> in the datatracker, who can set the stream information for a document? >=20 > It looks like ADs and the Secretariat can change the stream the > document is on (in change_stream in ietf/idrfc/views_edit.py). I think > it should be easy to relax this check enough to let stream owners > through. That would be great. Can we do this? In addition, it would be great if the "Adopt in WG" functionality allowed R= G chairs to adopt IDs into RGs. Currently, they aren't shown in the popup. Lars= From olau@iola.dk Thu Jan 10 04:57:00 2013 Return-Path: X-Original-To: tools-discuss@ietfa.amsl.com Delivered-To: tools-discuss@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 2482621F8496 for ; Thu, 10 Jan 2013 04:57:00 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -1.978 X-Spam-Level: X-Spam-Status: No, score=-1.978 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, FM_FORGED_GMAIL=0.622, NO_RELAYS=-0.001] Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id S77gibVA4V82 for ; Thu, 10 Jan 2013 04:56:59 -0800 (PST) Received: from mail-wi0-x22a.google.com (mail-wi0-x22a.google.com [IPv6:2a00:1450:400c:c05::22a]) by ietfa.amsl.com (Postfix) with ESMTP id EFCFE21F8450 for ; Thu, 10 Jan 2013 04:56:56 -0800 (PST) Received: by mail-wi0-f170.google.com with SMTP id hq7so1221755wib.5 for ; Thu, 10 Jan 2013 04:56:55 -0800 (PST) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc:content-type:x-gm-message-state; bh=mgp5IqeVS+I6AvK3HyQjOH/FbARphLw9UwgMBmO6tiA=; b=VlA9T+8FcXjVRftE/xSlavZCqznuBilsXdiE7WxNEumc4ZpSEJWo/Esv80loNvyDvh P+Hj0qQcHDtA77xP1Yq6ISfAmsck3pAuoKBfWlRkwjqo+eq3kb92B8If/c0pkRzr3mTS bMMi/JuPWIvlv7dEBRDrW8Z8cqo7nYgeCaE3qSBR/F+GH1afbUMfzJ8KPuOqDUWViCUY OmGm+LSyzeZtUUh1J5qXGzV9il9qifsA1enioYM5vs9yvedPnmzyUcDvremCyb/Ta4Fa kIxjI9EJ1f2VM/OnMz3/g18Tf2r2QogFUhgKIwPZSa2OHOLKKOyJfj4S6D4oG5Av4Bru +dqw== Received: by 10.180.24.133 with SMTP id u5mr9177238wif.17.1357822615619; Thu, 10 Jan 2013 04:56:55 -0800 (PST) MIME-Version: 1.0 Received: by 10.194.136.226 with HTTP; Thu, 10 Jan 2013 04:56:35 -0800 (PST) In-Reply-To: References: From: Ole Laursen Date: Thu, 10 Jan 2013 13:56:35 +0100 Message-ID: To: "Eggert, Lars" Content-Type: text/plain; charset=ISO-8859-1 X-Gm-Message-State: ALoCoQkzbP2c6g4nqJfackFcNjEhFC0YAj/cXU8L3TK6f5/T/bMzUCcqidiVqu5ksWSbGJ4p3Mka Cc: Tools Team Discussion Subject: Re: [Tools-discuss] change which stream an ID is on X-BeenThere: tools-discuss@ietf.org X-Mailman-Version: 2.1.12 Precedence: list List-Id: IETF Tools Discussion List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 10 Jan 2013 12:57:00 -0000 2013/1/8 Eggert, Lars : >> It looks like ADs and the Secretariat can change the stream the >> document is on (in change_stream in ietf/idrfc/views_edit.py). I think >> it should be easy to relax this check enough to let stream owners >> through. > > That would be great. Can we do this? I'm currently cleaning up the draft tabs and came across this. It took ten minutes to fix, so unless someone objects, I'll commit it to be rolled out with the cleanup work (which we're planning to do incrementally so I expect it to land within a couple of releases). > In addition, it would be great if the "Adopt in WG" functionality allowed RG chairs to adopt IDs into RGs. Currently, they aren't shown in the popup. Last time I looked at this, the adoption code was a bit of a hairball. But I'm supposed to get to at least some of that later in the cleanup project I think. I'll make a note so I don't forget it and see if it ends up being easily fixable too. Ole From olau@iola.dk Fri Jan 18 04:01:33 2013 Return-Path: X-Original-To: tools-discuss@ietfa.amsl.com Delivered-To: tools-discuss@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id F3C0A21F88B2 for ; Fri, 18 Jan 2013 04:01:32 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -2.478 X-Spam-Level: X-Spam-Status: No, score=-2.478 tagged_above=-999 required=5 tests=[AWL=0.499, BAYES_00=-2.599, FM_FORGED_GMAIL=0.622, RCVD_IN_DNSWL_LOW=-1] Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id nC9NNj8Xldkw for ; Fri, 18 Jan 2013 04:01:30 -0800 (PST) Received: from mail-wi0-f175.google.com (mail-wi0-f175.google.com [209.85.212.175]) by ietfa.amsl.com (Postfix) with ESMTP id 2BB8621F88E3 for ; Fri, 18 Jan 2013 04:01:29 -0800 (PST) Received: by mail-wi0-f175.google.com with SMTP id hm11so5197702wib.8 for ; Fri, 18 Jan 2013 04:01:29 -0800 (PST) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=x-received:mime-version:from:date:message-id:subject:to :content-type:x-gm-message-state; bh=1Uns7mjLQiTFg6tZ6C22sT01DAiQ402OVyhAm+vUAAs=; b=eTCrFkGR0jYQIw3Gt6LabpA/c8WmhMEsJXTOFT/j2N8svHcspp04+6WaBV0NR4z7Dt d5xx+LDOEt7CqMQJmyjB6pq6k5cgcu3V3MjDZ9OvwgzhFQsfH1brJg3fsx4fg/IiysSR IO80glzj56sJnl3kFY/VQcKIicINJC5yxMgw/YmYZrYesEUo7oFviZMBQSMgT/OkbH53 HqKVgTpHV4zEbuQjI81GmA/0uFsyzT/EyLW96d1gDfxfg5a5nwS+GUsFVAHHs6YvjS9S 6KxS3M0PfhiXzOW3/i7RnyzkeStVpoTDKsyuUfzOKeEQSpAiQYGgNJr1K8d+3JciWLzl YyuA== X-Received: by 10.180.87.228 with SMTP id bb4mr3151977wib.31.1358510489015; Fri, 18 Jan 2013 04:01:29 -0800 (PST) MIME-Version: 1.0 Received: by 10.194.10.193 with HTTP; Fri, 18 Jan 2013 04:01:08 -0800 (PST) From: Ole Laursen Date: Fri, 18 Jan 2013 13:01:08 +0100 Message-ID: To: tools-discuss@ietf.org Content-Type: text/plain; charset=ISO-8859-1 X-Gm-Message-State: ALoCoQnIldNsNkEPS5sYkPegPAD2oGS+UqsdpdI4AxFc8ZfLlCBKIr/qsevhztokJ1eCDsFkEFzG Subject: [Tools-discuss] Anyone using /doc/draft-xxxxxx/ballot.json? X-BeenThere: tools-discuss@ietf.org X-Mailman-Version: 2.1.12 Precedence: list List-Id: IETF Tools Discussion List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 18 Jan 2013 12:01:33 -0000 Hi! In the ongoing cleanup effort, I came across a view dumping JSON information on the IESG ballots. Is anyone here using that at the moment? It's available by appending "ballot.json" to an I-D URL. It's not current with the current schema and it's using some soon-to-be-deleted code. Ole From arusso@amsl.com Fri Jan 18 14:06:10 2013 Return-Path: X-Original-To: tools-discuss@ietfa.amsl.com Delivered-To: tools-discuss@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 2162121F8734 for ; Fri, 18 Jan 2013 14:06:10 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -2.599 X-Spam-Level: X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599] Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id wz8xbkVWbFWv for ; Fri, 18 Jan 2013 14:06:09 -0800 (PST) Received: from mail.amsl.com (mail.amsl.com [IPv6:2001:1890:123a::1:14]) by ietfa.amsl.com (Postfix) with ESMTP id 7F91921F8732 for ; Fri, 18 Jan 2013 14:06:09 -0800 (PST) Received: from localhost (c8a.amsl.com [127.0.0.1]) by c8a.amsl.com (Postfix) with ESMTP id 720FF124394; Fri, 18 Jan 2013 14:06:09 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com Received: from c8a.amsl.com ([127.0.0.1]) by localhost (c8a.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id JrmlsZA3rwD1; Fri, 18 Jan 2013 14:06:09 -0800 (PST) Received: from rfc2.home (pool-173-73-60-7.washdc.fios.verizon.net [173.73.60.7]) by c8a.amsl.com (Postfix) with ESMTPSA id EBEF41242B2; Fri, 18 Jan 2013 14:06:08 -0800 (PST) From: Alice Russo Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: quoted-printable Date: Fri, 18 Jan 2013 17:06:07 -0500 Message-Id: <33D6783B-850A-4A7B-9C03-55E73CC14665@amsl.com> To: rfc-interest@rfc-editor.org Mime-Version: 1.0 (Apple Message framework v1085) X-Mailer: Apple Mail (2.1085) Cc: Tools Team Discussion Subject: Re: [Tools-discuss] new RFC search page (beta) X-BeenThere: tools-discuss@ietf.org X-Mailman-Version: 2.1.12 Precedence: list List-Id: IETF Tools Discussion List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 18 Jan 2013 22:06:10 -0000 Greetings, The RFC search page (beta) - = http://www.rfc-editor.org/search/rfc_search.php - has been updated as = detailed below. It will replace the current search page on Jan. 23. As a = reminder, some of the features we think will make the new search page = better are as follows. Additional search criteria: - Status - Stream, Area, or WG that produced the RFC - Publication date - Abstract text Results: - link to RFC info pages (e.g., RFC 2026 links to http://www.rfc-editor.org/info/rfc2026) - link to subseries info pages (new) (e.g., BCP 14 links to http://www.rfc-editor.org/info/bcp14) - clearly show files that are available for a given RFC (e.g., RFC 4601 has 3 files available: = http://www.rfc-editor.org/search/rfc_search_detail.php?4601) - show when an RFC is the same as or part of a subseries identifier (e.g., http://www.rfc-editor.org/search/rfc_search_detail.php?rfc=3Dbcp9) - use URL-encoded parameters=20 (e.g., here are IRTF documents published in 2012: = http://www.rfc-editor.org/search/rfc_search_detail.php?stream_name=3DIRTF&= from_year=3D2012&to_year=3D2012) The following items (as reported by rfc-interest subscribers) were = addressed. - After clicking 'All', another result appears that was not shown in the = initial results. - Oddity with the checkboxes for Status. - Specific date display for April Fools' RFCs. - For "Number" and "Date" sort, the sortkey should not be numeric. - Remove extraneous parens around file formats. - Lack of "alt" for header image. (Note: alt is only visible when 'Load = images automatically' preference is off in the browser.) Items that have not been addressed are listed under 'F. Requested = Changes' on http://www.rfc-editor.org/search/about.html. Further = reports should be sent to rfc-editor@rfc-editor.org. Thank you. RFC Editor/ar= From olau@iola.dk Mon Jan 21 06:10:52 2013 Return-Path: X-Original-To: tools-discuss@ietfa.amsl.com Delivered-To: tools-discuss@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id DE16F21F85B8 for ; Mon, 21 Jan 2013 06:10:52 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -2.977 X-Spam-Level: X-Spam-Status: No, score=-2.977 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, FM_FORGED_GMAIL=0.622, RCVD_IN_DNSWL_LOW=-1] Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id HXbtesiiK8zW for ; Mon, 21 Jan 2013 06:10:46 -0800 (PST) Received: from mail-wg0-f50.google.com (mail-wg0-f50.google.com [74.125.82.50]) by ietfa.amsl.com (Postfix) with ESMTP id 4930B21F85AB for ; Mon, 21 Jan 2013 06:10:45 -0800 (PST) Received: by mail-wg0-f50.google.com with SMTP id es5so3679993wgb.17 for ; Mon, 21 Jan 2013 06:10:45 -0800 (PST) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=x-received:mime-version:from:date:message-id:subject:to :content-type:x-gm-message-state; bh=H2gh6I9mkwHLSRvDGrAZyWdW7o3gxe2ygw8hDGxKs+E=; b=bAIUGfDZQWu0+a9/nvweB3SGkx4bZeKEgHAYjewmIPNKzTUGPyy6gy6BkhBPiNQR+C JvkLtQptb2qGSozrNdo3iV0hGTol/H8NYGHiATYZs3MqfXA1BK9uMUyeOZC/NyHFFKOi eoqR1DG5hfOlpoNUrkSwfr43JISSscQ3q0YHMPJN2ByEcV7fEb4inoZEAULlLb8v3xMi XEGjMvSgk1m9lf0z9Z+jEt2DWfCYR9gp5rD9HNNruSTN4iawg7jXCTIWaAgMk1WXRslo dL0cBq3o7FZH6jkvDnqxk0yP6kApbayqNI7jXjmg/GmPvzKc8XnxicJ2a7PKsxX/UVKv 4Y5Q== X-Received: by 10.180.108.236 with SMTP id hn12mr15719731wib.6.1358777440720; Mon, 21 Jan 2013 06:10:40 -0800 (PST) MIME-Version: 1.0 Received: by 10.194.10.193 with HTTP; Mon, 21 Jan 2013 06:10:20 -0800 (PST) From: Ole Laursen Date: Mon, 21 Jan 2013 15:10:20 +0100 Message-ID: To: Tools Team Discussion Content-Type: text/plain; charset=ISO-8859-1 X-Gm-Message-State: ALoCoQmtwFOiktqVRKslhxS8JJymuEeDSbugvKAg1d4S8SLwvCndyAbkWyJMYy9vLB95VxTQZLMh Subject: [Tools-discuss] Datatracker I-D tabs cleanup X-BeenThere: tools-discuss@ietf.org X-Mailman-Version: 2.1.12 Precedence: list List-Id: IETF Tools Discussion List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 21 Jan 2013 14:10:53 -0000 Hi! I just finished a cleanup of the document tabs for drafts and RFCs, i.e. those available at datatracker.ietf.org/doc/draft-XXXX/. The cleanup is mostly on the code behind, making it much easier to work with, but there are some minor user-visible changes and bug fixes and it's also a fair bit faster. One more notable change is that a published Internet-Draft is no longer presented as two documents, at the I-D URL and the RFC URL. Instead we show a merged view at the RFC URL and redirect from I-D -> RFC. For instance, on the test server http://shimfree.ietf.beta.iola.dk/doc/draft-ietf-isms-dtls-tm/ => http://shimfree.ietf.beta.iola.dk/doc/rfc5953/ I also made sure that BCP and other aliases (FYI and STD) work, so /doc/bcp141/ redirects to /doc/rfc5342/. If anyone here has the time to just quickly check that their pet I-Ds/RFCs are shown correctly, please go to http://shimfree.ietf.beta.iola.dk/ This cleanup is part the first part of a larger effort to get the Datatracker code base cleaned up after the database migration last year. We're aiming for an incremental rollout, so the code on the test server should hit live within in a not-too-distant future. TEST NOTES The test server is running on a local database dump from today, so you can change things as you like. Login with your usual account and blank password. Emails are suppressed, unless you go to http://shimfree.ietf.beta.iola.dk/accounts/testemail/ and fill in your information - then you'll get email you produce forwarded. Also note that some information outside the database dump may be missing from the test server so some links may be dead. In particular, the server is probably missing some of the charter texts. Ole From lars@netapp.com Mon Jan 21 06:16:37 2013 Return-Path: X-Original-To: tools-discuss@ietfa.amsl.com Delivered-To: tools-discuss@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 4F79021F85C3 for ; Mon, 21 Jan 2013 06:16:37 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -10.599 X-Spam-Level: X-Spam-Status: No, score=-10.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_HI=-8] Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id hWO-iovqff8T for ; Mon, 21 Jan 2013 06:16:36 -0800 (PST) Received: from mx12.netapp.com (mx12.netapp.com [216.240.18.77]) by ietfa.amsl.com (Postfix) with ESMTP id 516A021F85C2 for ; Mon, 21 Jan 2013 06:16:36 -0800 (PST) X-IronPort-AV: E=Sophos;i="4.84,506,1355126400"; d="scan'208";a="10037303" Received: from smtp1.corp.netapp.com ([10.57.156.124]) by mx12-out.netapp.com with ESMTP; 21 Jan 2013 06:16:35 -0800 Received: from vmwexceht02-prd.hq.netapp.com (vmwexceht02-prd.hq.netapp.com [10.106.76.240]) by smtp1.corp.netapp.com (8.13.1/8.13.1/NTAP-1.6) with ESMTP id r0LEGYgB014359; Mon, 21 Jan 2013 06:16:35 -0800 (PST) Received: from SACEXCMBX01-PRD.hq.netapp.com ([169.254.2.51]) by vmwexceht02-prd.hq.netapp.com ([10.106.76.240]) with mapi id 14.02.0328.009; Mon, 21 Jan 2013 06:16:34 -0800 From: "Eggert, Lars" To: Ole Laursen Thread-Topic: [Tools-discuss] change which stream an ID is on Thread-Index: AQHN7NOQoKD/deJee0Ss6YuX76GxQ5g+YdOAgAFnYYCAA0cYgIARX/2A Date: Mon, 21 Jan 2013 14:16:33 +0000 Message-ID: References: In-Reply-To: Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: x-originating-ip: [10.106.53.51] Content-Type: text/plain; charset="iso-8859-1" Content-ID: <2B1A16AAC54E734EA0D6B678EB283AE5@tahoe.netapp.com> Content-Transfer-Encoding: quoted-printable MIME-Version: 1.0 Cc: Tools Team Discussion Subject: Re: [Tools-discuss] change which stream an ID is on X-BeenThere: tools-discuss@ietf.org X-Mailman-Version: 2.1.12 Precedence: list List-Id: IETF Tools Discussion List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 21 Jan 2013 14:16:37 -0000 Hi, any idea when these features will hit the running system? Lars On Jan 10, 2013, at 13:56, Ole Laursen wrote: > 2013/1/8 Eggert, Lars : >>> It looks like ADs and the Secretariat can change the stream the >>> document is on (in change_stream in ietf/idrfc/views_edit.py). I think >>> it should be easy to relax this check enough to let stream owners >>> through. >>=20 >> That would be great. Can we do this? >=20 > I'm currently cleaning up the draft tabs and came across this. It took > ten minutes to fix, so unless someone objects, I'll commit it to be > rolled out with the cleanup work (which we're planning to do > incrementally so I expect it to land within a couple of releases). >=20 >> In addition, it would be great if the "Adopt in WG" functionality allowe= d RG chairs to adopt IDs into RGs. Currently, they aren't shown in the popu= p. >=20 > Last time I looked at this, the adoption code was a bit of a hairball. > But I'm supposed to get to at least some of that later in the cleanup > project I think. I'll make a note so I don't forget it and see if it > ends up being easily fixable too. >=20 > Ole From olau@iola.dk Mon Jan 21 06:44:39 2013 Return-Path: X-Original-To: tools-discuss@ietfa.amsl.com Delivered-To: tools-discuss@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 29D5321F8523 for ; Mon, 21 Jan 2013 06:44:39 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -2.977 X-Spam-Level: X-Spam-Status: No, score=-2.977 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, FM_FORGED_GMAIL=0.622, RCVD_IN_DNSWL_LOW=-1] Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id IOLfJNc-KfX3 for ; Mon, 21 Jan 2013 06:44:38 -0800 (PST) Received: from mail-wi0-f182.google.com (mail-wi0-f182.google.com [209.85.212.182]) by ietfa.amsl.com (Postfix) with ESMTP id 6EAFC21F8510 for ; Mon, 21 Jan 2013 06:44:38 -0800 (PST) Received: by mail-wi0-f182.google.com with SMTP id hn14so4993908wib.3 for ; Mon, 21 Jan 2013 06:44:37 -0800 (PST) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=x-received:mime-version:in-reply-to:references:from:date:message-id :subject:to:cc:content-type:x-gm-message-state; bh=9jdXPFXR525NA1j+S0jHU96jVXxr9sKw+bKCXOxvC4w=; b=LyJE7dEuBj/uuC9k9scQcBDWdzcqsBIzxGjvSAuJ7Zq0iIFw4TW4xjPaLJp2R0oTnH KMIcApt0XTKGmfO7M3CHRGjxPnT25zQ9rNkHplhpVeP961X6zzvaEyETYydszw1siCrB sHwCH+G4UEMl5oHy9fenYPTGSDZ15W6eQ2NlV9QePSvMKztfX/tg4K9tKTWv8iA+WdB4 XZo6qqXWfG86Fhyc3tTesYo5sstKkQ8c31Ri/GqvkvL4eLcw1GOj2VFa3iBw0nFXEmtg 27PYHv61UJ/9ist8tuPxjX/M+QSMj8za2gQB41zkNNQg3g3Yl9NaeJevEgfpaDh8kxCS dStA== X-Received: by 10.180.109.195 with SMTP id hu3mr15755375wib.31.1358779475020; Mon, 21 Jan 2013 06:44:35 -0800 (PST) MIME-Version: 1.0 Received: by 10.194.10.193 with HTTP; Mon, 21 Jan 2013 06:44:14 -0800 (PST) In-Reply-To: References: From: Ole Laursen Date: Mon, 21 Jan 2013 15:44:14 +0100 Message-ID: To: "Eggert, Lars" Content-Type: text/plain; charset=ISO-8859-1 X-Gm-Message-State: ALoCoQkPEgXO3r1FDcwSKWVy14Ge4q+PZXefAVnypanwcQ1+URA0eAMVPGH7BoElTmQzACpI0WjD Cc: Tools Team Discussion Subject: Re: [Tools-discuss] change which stream an ID is on X-BeenThere: tools-discuss@ietf.org X-Mailman-Version: 2.1.12 Precedence: list List-Id: IETF Tools Discussion List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 21 Jan 2013 14:44:39 -0000 Hi! I'm done with the first chunk with the permission fix, but it depends on when Henrik has time to merge it, there are a couple of things in front of it in the queue, I think. As for the RG adoption, realistically I'm probably not going to look at that part until at least a month or two from now. Ole 2013/1/21 Eggert, Lars : > Hi, > > any idea when these features will hit the running system? > > Lars > > On Jan 10, 2013, at 13:56, Ole Laursen wrote: > >> 2013/1/8 Eggert, Lars : >>>> It looks like ADs and the Secretariat can change the stream the >>>> document is on (in change_stream in ietf/idrfc/views_edit.py). I think >>>> it should be easy to relax this check enough to let stream owners >>>> through. >>> >>> That would be great. Can we do this? >> >> I'm currently cleaning up the draft tabs and came across this. It took >> ten minutes to fix, so unless someone objects, I'll commit it to be >> rolled out with the cleanup work (which we're planning to do >> incrementally so I expect it to land within a couple of releases). >> >>> In addition, it would be great if the "Adopt in WG" functionality allowed RG chairs to adopt IDs into RGs. Currently, they aren't shown in the popup. >> >> Last time I looked at this, the adoption code was a bit of a hairball. >> But I'm supposed to get to at least some of that later in the cleanup >> project I think. I'll make a note so I don't forget it and see if it >> ends up being easily fixable too. >> >> Ole > From olau@iola.dk Mon Jan 21 07:08:55 2013 Return-Path: X-Original-To: tools-discuss@ietfa.amsl.com Delivered-To: tools-discuss@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id B26F821F882C for ; Mon, 21 Jan 2013 07:08:55 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -1.978 X-Spam-Level: X-Spam-Status: No, score=-1.978 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, FM_FORGED_GMAIL=0.622, NO_RELAYS=-0.001] Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 4hRtHtYeleqN for ; Mon, 21 Jan 2013 07:08:55 -0800 (PST) Received: from mail-wg0-x229.google.com (mail-wg0-x229.google.com [IPv6:2a00:1450:400c:c00::229]) by ietfa.amsl.com (Postfix) with ESMTP id 2790521F8826 for ; Mon, 21 Jan 2013 07:08:55 -0800 (PST) Received: by mail-wg0-f41.google.com with SMTP id ds1so1113601wgb.0 for ; Mon, 21 Jan 2013 07:08:53 -0800 (PST) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=x-received:mime-version:in-reply-to:references:from:date:message-id :subject:to:content-type:x-gm-message-state; bh=n/zSu/Sg/FeT7fG4VareN6ggqBEclc7cstGx3lDTf2A=; b=mOiN07wVW8H9U6EuEhb4xb8DuEkws5tGKvRFxRPYXgPS0mQMmKDbSfYIoqBKLXpwHz W/1m+3dJMJLH9GFqwmBbWfukpoPshPY30jQV8tV4+pvFidoACeYB7wqxCnRJPmyYWkAh 5TPsSzlUOki+d31XYEaRenhHBRBgH/SPqjLMq3+Kt29rnU2XH4jFlwYi89Ev7QDZPhxf pe96gAwIP8y7Hk1p4VrUjB+tNEdd34DJZtrMjCKqkwbMP1Fmzq9UsU95BMhOSPvP9+Kl mAYC168/SrhI0ZVWHn4nJo8rAlAMA27WL3rPXocx/1H+Oskqp8mBNEQhmkkSEKccsYo7 GI7A== X-Received: by 10.194.108.229 with SMTP id hn5mr27143384wjb.8.1358780932968; Mon, 21 Jan 2013 07:08:52 -0800 (PST) MIME-Version: 1.0 Received: by 10.194.10.193 with HTTP; Mon, 21 Jan 2013 07:08:32 -0800 (PST) In-Reply-To: References: From: Ole Laursen Date: Mon, 21 Jan 2013 16:08:32 +0100 Message-ID: To: Tools Team Discussion Content-Type: text/plain; charset=ISO-8859-1 X-Gm-Message-State: ALoCoQm9ZWyVZXwP3+lYHGE77dYyijf4EgNxHKR1WSo+g18Z/HB9e/3jZAar+/BGe5i1an0h2MQB Subject: Re: [Tools-discuss] Datatracker I-D tabs cleanup X-BeenThere: tools-discuss@ietf.org X-Mailman-Version: 2.1.12 Precedence: list List-Id: IETF Tools Discussion List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 21 Jan 2013 15:08:55 -0000 2013/1/21 Ole Laursen : > Also note that some information outside the database dump may be > missing from the test server so some links may be dead. In particular, > the server is probably missing some of the charter texts. The test server is also missing many RFC and Internet-Draft texts. So please ignore errors on the form "Error; cannot read (draft-...)" and "This RFC is not currently available online", and the "Other versions" field will also be inaccurate. Ole From lars@netapp.com Tue Jan 22 07:58:22 2013 Return-Path: X-Original-To: tools-discuss@ietfa.amsl.com Delivered-To: tools-discuss@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id B015121F874B for ; Tue, 22 Jan 2013 07:58:22 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -9.24 X-Spam-Level: X-Spam-Status: No, score=-9.24 tagged_above=-999 required=5 tests=[AWL=-0.860, BAYES_00=-2.599, RCVD_IN_DNSWL_HI=-8, TVD_SPACE_RATIO=2.219] Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id VJKjHEnmPZTW for ; Tue, 22 Jan 2013 07:58:22 -0800 (PST) Received: from mx12.netapp.com (mx12.netapp.com [216.240.18.77]) by ietfa.amsl.com (Postfix) with ESMTP id 1763321F86EF for ; Tue, 22 Jan 2013 07:58:22 -0800 (PST) X-IronPort-AV: E=Sophos;i="4.84,515,1355126400"; d="scan'208";a="10418963" Received: from smtp1.corp.netapp.com ([10.57.156.124]) by mx12-out.netapp.com with ESMTP; 22 Jan 2013 07:58:12 -0800 Received: from vmwexceht02-prd.hq.netapp.com (vmwexceht02-prd.hq.netapp.com [10.106.76.240]) by smtp1.corp.netapp.com (8.13.1/8.13.1/NTAP-1.6) with ESMTP id r0MFwCKu020760 for ; Tue, 22 Jan 2013 07:58:12 -0800 (PST) Received: from SACEXCMBX01-PRD.hq.netapp.com ([169.254.2.51]) by vmwexceht02-prd.hq.netapp.com ([10.106.76.240]) with mapi id 14.02.0328.009; Tue, 22 Jan 2013 07:58:12 -0800 From: "Eggert, Lars" To: Tools Team Discussion Thread-Topic: asciiflow Thread-Index: AQHN+LlHIl98DBWUE0+9J2+ANJXWCg== Date: Tue, 22 Jan 2013 15:58:11 +0000 Message-ID: Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: x-originating-ip: [10.106.53.51] Content-Type: text/plain; charset="us-ascii" Content-ID: Content-Transfer-Encoding: quoted-printable MIME-Version: 1.0 Subject: [Tools-discuss] asciiflow X-BeenThere: tools-discuss@ietf.org X-Mailman-Version: 2.1.12 Precedence: list List-Id: IETF Tools Discussion List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 22 Jan 2013 15:58:22 -0000 Pretty neat: http://www.asciiflow.com/ Lars From bob.hinden@gmail.com Tue Jan 22 08:07:14 2013 Return-Path: X-Original-To: tools-discuss@ietfa.amsl.com Delivered-To: tools-discuss@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 9DA5621F86C9 for ; Tue, 22 Jan 2013 08:07:14 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -103.599 X-Spam-Level: X-Spam-Status: No, score=-103.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1, USER_IN_WHITELIST=-100] Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id jhc55uhjVylU for ; Tue, 22 Jan 2013 08:07:13 -0800 (PST) Received: from mail-lb0-f178.google.com (mail-lb0-f178.google.com [209.85.217.178]) by ietfa.amsl.com (Postfix) with ESMTP id DC86D21F8A64 for ; Tue, 22 Jan 2013 08:06:59 -0800 (PST) Received: by mail-lb0-f178.google.com with SMTP id n1so2985799lba.37 for ; Tue, 22 Jan 2013 08:06:58 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=x-received:subject:mime-version:content-type:from:in-reply-to:date :cc:content-transfer-encoding:message-id:references:to:x-mailer; bh=yLdhvW2LKpQi5v6Id7NZu8TmmZoQFD32jUvFiQpTLWA=; b=hGrID5EisRwvpMOqprUtXMnQdj+0d88aU8QtkM/SSOHLf2QRgYs8tsqzToSKx0vQkv Wqd7Hu+KubjWqfRpLzmBkr5E6Jn8NqF7eqdRhuzNENIvQgr/qKUl5mEi9umAAI3kT8T5 WhQnt/F8AK+rhlDI6A2RBFfxh3SEttfoRWbiOmfH16YYJgq1pNItdjcGfc4ilI1s5VrR RKcFJVsR1QgOO21D4JGtfUQ7vgA8RXXuIr20cI2ArwonfCrxqqYbvDQEe4SZLJYWPBQm 2LU9E0jao7K16+JxzcMxXVxmsmIt275OaVnsbnupgy77UXT3iOUMtL2bCSj/ruMp1GZn /Odg== X-Received: by 10.112.29.229 with SMTP id n5mr9694659lbh.130.1358870818836; Tue, 22 Jan 2013 08:06:58 -0800 (PST) Received: from [10.0.0.23] (c-24-130-151-138.hsd1.ca.comcast.net. [24.130.151.138]) by mx.google.com with ESMTPS id pz15sm7198682lab.3.2013.01.22.08.06.54 (version=TLSv1 cipher=RC4-SHA bits=128/128); Tue, 22 Jan 2013 08:06:56 -0800 (PST) Mime-Version: 1.0 (Apple Message framework v1283) Content-Type: text/plain; charset=us-ascii From: Bob Hinden In-Reply-To: Date: Tue, 22 Jan 2013 08:06:54 -0800 Content-Transfer-Encoding: quoted-printable Message-Id: References: To: "Eggert, Lars" X-Mailer: Apple Mail (2.1283) Cc: Tools Team Discussion Subject: Re: [Tools-discuss] asciiflow X-BeenThere: tools-discuss@ietf.org X-Mailman-Version: 2.1.12 Precedence: list List-Id: IETF Tools Discussion List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 22 Jan 2013 16:07:14 -0000 Lars, Very cool! Please forward to rfc-interest. We might be giving up on = ASCII art prematurely :-) Bob On Jan 22, 2013, at 7:58 AM, Eggert, Lars wrote: > Pretty neat: http://www.asciiflow.com/ >=20 > Lars > _______________________________________________ > Tools-discuss mailing list > Tools-discuss@ietf.org > https://www.ietf.org/mailman/listinfo/tools-discuss From nico@cryptonector.com Tue Jan 22 08:48:26 2013 Return-Path: X-Original-To: tools-discuss@ietfa.amsl.com Delivered-To: tools-discuss@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 93EEB21F8A51 for ; Tue, 22 Jan 2013 08:48:26 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -1.977 X-Spam-Level: X-Spam-Status: No, score=-1.977 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, FM_FORGED_GMAIL=0.622] Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id OHgm2M07FsJE for ; Tue, 22 Jan 2013 08:48:25 -0800 (PST) Received: from homiemail-a33.g.dreamhost.com (caiajhbdcaid.dreamhost.com [208.97.132.83]) by ietfa.amsl.com (Postfix) with ESMTP id CB2D321F8A4F for ; Tue, 22 Jan 2013 08:48:24 -0800 (PST) Received: from homiemail-a33.g.dreamhost.com (localhost [127.0.0.1]) by homiemail-a33.g.dreamhost.com (Postfix) with ESMTP id 2449F594069 for ; Tue, 22 Jan 2013 08:48:24 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha1; c=relaxed; d=cryptonector.com; h= mime-version:in-reply-to:references:date:message-id:subject:from :to:cc:content-type; s=cryptonector.com; bh=glRTC7ShC9TZu/FEyNje LUjTVTo=; b=JnqqM1OEIa8saKBjV1vQT02AF81lcRRODkwSqIUoITEhUbJTxCda Pl3k1sljW2C2oiWMgqbvEfKcVeOtL6KVkQU72ff+S7scEYyCdMNQlQ+yzGoZOBk7 TzskIWRlAl/Ojj5ZHTV65pYNHHFDjf+KLm/m0Ffl6KU/A1eaZAVUTns= Received: from mail-ia0-f179.google.com (mail-ia0-f179.google.com [209.85.210.179]) (using TLSv1 with cipher RC4-SHA (128/128 bits)) (No client certificate requested) (Authenticated sender: nico@cryptonector.com) by homiemail-a33.g.dreamhost.com (Postfix) with ESMTPSA id 6C75B594062 for ; Tue, 22 Jan 2013 08:48:23 -0800 (PST) Received: by mail-ia0-f179.google.com with SMTP id x24so3392270iak.10 for ; Tue, 22 Jan 2013 08:48:22 -0800 (PST) MIME-Version: 1.0 X-Received: by 10.50.57.133 with SMTP id i5mr12238653igq.67.1358873302168; Tue, 22 Jan 2013 08:48:22 -0800 (PST) Received: by 10.64.12.69 with HTTP; Tue, 22 Jan 2013 08:48:21 -0800 (PST) In-Reply-To: References: Date: Tue, 22 Jan 2013 10:48:21 -0600 Message-ID: From: Nico Williams To: Bob Hinden Content-Type: text/plain; charset=UTF-8 Cc: Tools Team Discussion Subject: Re: [Tools-discuss] asciiflow X-BeenThere: tools-discuss@ietf.org X-Mailman-Version: 2.1.12 Precedence: list List-Id: IETF Tools Discussion List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 22 Jan 2013 16:48:26 -0000 On Tue, Jan 22, 2013 at 10:06 AM, Bob Hinden wrote: > Very cool! Please forward to rfc-interest. We might be giving up on ASCII art prematurely :-) Heh, well, there's a better tool that I use: JavE (www.jave.de). Also, there's this: https://9vx.org/~dho/a2s/ and there should be an SVG to ASCII art renderer somewhere.... Nico -- From nico@cryptonector.com Tue Jan 22 08:57:25 2013 Return-Path: X-Original-To: tools-discuss@ietfa.amsl.com Delivered-To: tools-discuss@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 014E421F84C9 for ; Tue, 22 Jan 2013 08:57:25 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -1.977 X-Spam-Level: X-Spam-Status: No, score=-1.977 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, FM_FORGED_GMAIL=0.622] Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id juISP5P25-+C for ; Tue, 22 Jan 2013 08:57:24 -0800 (PST) Received: from homiemail-a64.g.dreamhost.com (caiajhbdcbef.dreamhost.com [208.97.132.145]) by ietfa.amsl.com (Postfix) with ESMTP id 42F2E21F84C7 for ; Tue, 22 Jan 2013 08:57:24 -0800 (PST) Received: from homiemail-a64.g.dreamhost.com (localhost [127.0.0.1]) by homiemail-a64.g.dreamhost.com (Postfix) with ESMTP id 6E0BC438080 for ; Tue, 22 Jan 2013 08:57:23 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha1; c=relaxed; d=cryptonector.com; h= mime-version:in-reply-to:references:date:message-id:subject:from :to:cc:content-type; s=cryptonector.com; bh=9xHl5kcPG4cWkkwQEHRb iMyQnd8=; b=Dfa7DKHlh6Erzsx3hyV4cfJQcOKEefNBmqDBWvI1wqUPITbLAbCN E062Q6+SPMYF0+jlsWuyPv39heFUrPY29DQrJQOehIidx5rvpww6fEDIoNjQZ/eG 1vNpWKyzs0bjZaPZhbMT2I6DnOxovKAUGQS/f3pP6KleMUZznMWeDtQ= Received: from mail-ia0-f171.google.com (mail-ia0-f171.google.com [209.85.210.171]) (using TLSv1 with cipher RC4-SHA (128/128 bits)) (No client certificate requested) (Authenticated sender: nico@cryptonector.com) by homiemail-a64.g.dreamhost.com (Postfix) with ESMTPSA id 84DC143807F for ; Tue, 22 Jan 2013 08:57:22 -0800 (PST) Received: by mail-ia0-f171.google.com with SMTP id z13so2260866iaz.16 for ; Tue, 22 Jan 2013 08:57:21 -0800 (PST) MIME-Version: 1.0 X-Received: by 10.50.161.169 with SMTP id xt9mr12198337igb.62.1358873841184; Tue, 22 Jan 2013 08:57:21 -0800 (PST) Received: by 10.64.12.69 with HTTP; Tue, 22 Jan 2013 08:57:21 -0800 (PST) In-Reply-To: References: Date: Tue, 22 Jan 2013 10:57:21 -0600 Message-ID: From: Nico Williams To: Bob Hinden Content-Type: text/plain; charset=UTF-8 Cc: Tools Team Discussion Subject: Re: [Tools-discuss] asciiflow X-BeenThere: tools-discuss@ietf.org X-Mailman-Version: 2.1.12 Precedence: list List-Id: IETF Tools Discussion List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 22 Jan 2013 16:57:25 -0000 Also, there's: http://www.mediawiki.org/wiki/Extension:Graph http://bloodgate.com/perl/graph/fun.html <--- Really cool examples! which use this: https://metacpan.org/module/Graph::Easy From ietf@rozanak.com Tue Jan 22 12:40:31 2013 Return-Path: X-Original-To: tools-discuss@ietfa.amsl.com Delivered-To: tools-discuss@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 4583721F8992 for ; Tue, 22 Jan 2013 12:40:31 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -2.599 X-Spam-Level: X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599] Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 4g282yvePpDc for ; Tue, 22 Jan 2013 12:40:29 -0800 (PST) Received: from mout.perfora.net (mout.perfora.net [74.208.4.194]) by ietfa.amsl.com (Postfix) with ESMTP id 8D80121F8960 for ; Tue, 22 Jan 2013 12:40:29 -0800 (PST) Received: from kopoli (e179167194.adsl.alicedsl.de [85.179.167.194]) by mrelay.perfora.net (node=mrus3) with ESMTP (Nemesis) id 0MPDNg-1TtKmy2AKW-0058Y5; Tue, 22 Jan 2013 15:40:23 -0500 From: "Hosnieh Rafiee" To: References: In-Reply-To: Date: Tue, 22 Jan 2013 21:40:14 +0100 Message-ID: <000001cdf8e0$b1c98830$155c9890$@rozanak.com> MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit X-Mailer: Microsoft Outlook 14.0 Thread-Index: AQKSFFhWgv6taWwFnQvanqGdDqBo1JbNl/zw Content-Language: en-us X-Provags-ID: V02:K0:iluZXahnee0V3MDwxodRoS5q4SGCTHfKC7ZqCMV7JYR G1+CvyYA949R9yQQI2SPROChYXqynSgdCdCtau2rRUX81fLIwr CjYRVKM4S8WwBrhK5LyCNboid1dUHc42EYJXX65RCBWqFZTFI7 lmeTkvKtucCuAKMJ8KiYsvQ6/PJ8OXgroP3HR73GWDmr9xscaA vY+vQYJGcGvY2xIK1doVvRgeh/w13KIRjE+gZPI9qProXtr4gb h+K1f2hc24gFO3Y01t68vDEibFHw8eei7qvksY0DfBeHLz4768 MTWPkgUHoBd4xjWSEoI++ogWkafqapl+UMZwrH0Eo8FIypk2pg z8eE8lkj/4FYB4O19OQ0= Subject: Re: [Tools-discuss] Tools-discuss Digest, Vol 99, Issue 10 X-BeenThere: tools-discuss@ietf.org X-Mailman-Version: 2.1.12 Precedence: list List-Id: IETF Tools Discussion List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 22 Jan 2013 20:40:31 -0000 Hello, Has anybody ever tried to use my RFC tool after I uploaded a new version? http://editor.rozanak.com Thank you, Hosnieh -----Original Message----- From: tools-discuss-bounces@ietf.org [mailto:tools-discuss-bounces@ietf.org] On Behalf Of tools-discuss-request@ietf.org Sent: Tuesday, January 22, 2013 9:00 PM To: tools-discuss@ietf.org Subject: Tools-discuss Digest, Vol 99, Issue 10 If you have received this digest without all the individual message attachments you will need to update your digest options in your list subscription. To do so, go to https://www.ietf.org/mailman/listinfo/tools-discuss Click the 'Unsubscribe or edit options' button, log in, and set "Get MIME or Plain Text Digests?" to MIME. You can set this option globally for all the list digests you receive at this point. Send Tools-discuss mailing list submissions to tools-discuss@ietf.org To subscribe or unsubscribe via the World Wide Web, visit https://www.ietf.org/mailman/listinfo/tools-discuss or, via email, send a message with subject or body 'help' to tools-discuss-request@ietf.org You can reach the person managing the list at tools-discuss-owner@ietf.org When replying, please edit your Subject line so it is more specific than "Re: Contents of Tools-discuss digest..." Today's Topics: 1. asciiflow (Eggert, Lars) 2. Re: asciiflow (Bob Hinden) 3. Re: asciiflow (Nico Williams) 4. Re: asciiflow (Nico Williams) ---------------------------------------------------------------------- Message: 1 Date: Tue, 22 Jan 2013 15:58:11 +0000 From: "Eggert, Lars" To: Tools Team Discussion Subject: [Tools-discuss] asciiflow Message-ID: Content-Type: text/plain; charset="us-ascii" Pretty neat: http://www.asciiflow.com/ Lars ------------------------------ Message: 2 Date: Tue, 22 Jan 2013 08:06:54 -0800 From: Bob Hinden To: "Eggert, Lars" Cc: Tools Team Discussion Subject: Re: [Tools-discuss] asciiflow Message-ID: Content-Type: text/plain; charset=us-ascii Lars, Very cool! Please forward to rfc-interest. We might be giving up on ASCII art prematurely :-) Bob On Jan 22, 2013, at 7:58 AM, Eggert, Lars wrote: > Pretty neat: http://www.asciiflow.com/ > > Lars > _______________________________________________ > Tools-discuss mailing list > Tools-discuss@ietf.org > https://www.ietf.org/mailman/listinfo/tools-discuss ------------------------------ Message: 3 Date: Tue, 22 Jan 2013 10:48:21 -0600 From: Nico Williams To: Bob Hinden Cc: Tools Team Discussion Subject: Re: [Tools-discuss] asciiflow Message-ID: Content-Type: text/plain; charset=UTF-8 On Tue, Jan 22, 2013 at 10:06 AM, Bob Hinden wrote: > Very cool! Please forward to rfc-interest. We might be giving up on > ASCII art prematurely :-) Heh, well, there's a better tool that I use: JavE (www.jave.de). Also, there's this: https://9vx.org/~dho/a2s/ and there should be an SVG to ASCII art renderer somewhere.... Nico -- ------------------------------ Message: 4 Date: Tue, 22 Jan 2013 10:57:21 -0600 From: Nico Williams To: Bob Hinden Cc: Tools Team Discussion Subject: Re: [Tools-discuss] asciiflow Message-ID: Content-Type: text/plain; charset=UTF-8 Also, there's: http://www.mediawiki.org/wiki/Extension:Graph http://bloodgate.com/perl/graph/fun.html <--- Really cool examples! which use this: https://metacpan.org/module/Graph::Easy ------------------------------ _______________________________________________ Tools-discuss mailing list Tools-discuss@ietf.org https://www.ietf.org/mailman/listinfo/tools-discuss End of Tools-discuss Digest, Vol 99, Issue 10 ********************************************* From ietf@rozanak.com Tue Jan 22 12:43:12 2013 Return-Path: X-Original-To: tools-discuss@ietfa.amsl.com Delivered-To: tools-discuss@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 7129021F8960 for ; Tue, 22 Jan 2013 12:43:12 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -2.599 X-Spam-Level: X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599] Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id fkMZDg0M6vi0 for ; Tue, 22 Jan 2013 12:43:12 -0800 (PST) Received: from mout.perfora.net (mout.perfora.net [74.208.4.194]) by ietfa.amsl.com (Postfix) with ESMTP id C7DDD21F85D2 for ; Tue, 22 Jan 2013 12:43:11 -0800 (PST) Received: from kopoli (e179167194.adsl.alicedsl.de [85.179.167.194]) by mrelay.perfora.net (node=mrus4) with ESMTP (Nemesis) id 0MAhf9-1TmR5V3xUJ-00C5VP; Tue, 22 Jan 2013 15:43:09 -0500 From: "Hosnieh Rafiee" To: References: In-Reply-To: Date: Tue, 22 Jan 2013 21:43:02 +0100 Message-ID: <000101cdf8e1$15902270$40b06750$@rozanak.com> MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit X-Mailer: Microsoft Outlook 14.0 Thread-Index: AQKSFFhWgv6taWwFnQvanqGdDqBo1JbNmR6g Content-Language: en-us X-Provags-ID: V02:K0:rn+mfXNSrH2hdeBY9P3K38pgig7xcVKU5aJTt9yHu/z W87DPL3JInh5Ig3797NApmyfUmfZpg7i/ck5V4+jTe0rNa0jt2 hZytJ7wCLAT33RC3gCJtgfK9ZyYr1sJJxb42KNVVzXpABqnL0E RaiE8gGt5OfwyvXIdtltvwzx7CRD1HRYaLF56M+5OQqN7zToOy pvuOCZMfJybnORXMGqabo6/t2kmXco+3BN7CQPaqCP2I3oGlC1 uZHvKiszebhOO1+z6ePTpsDDNJRGJ69t1WCGZcT278P5MOrhck OZ4kZn4v22zNlsRvUQX5jNF8OGMiqiPpKFgrm46qvTA9KIZe6I XaAYJpbHi97oMrIC8FMU= Cc: tools-discuss@ietf.org Subject: Re: [Tools-discuss] Tools-discuss Digest, Vol 99, Issue 10 X-BeenThere: tools-discuss@ietf.org X-Mailman-Version: 2.1.12 Precedence: list List-Id: IETF Tools Discussion List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 22 Jan 2013 20:43:12 -0000 >Pretty neat: http://www.asciiflow.com/ That's a nice tool :-) Thanks Hosnieh From nico@cryptonector.com Tue Jan 22 12:52:07 2013 Return-Path: X-Original-To: tools-discuss@ietfa.amsl.com Delivered-To: tools-discuss@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 5085521F8A4E for ; Tue, 22 Jan 2013 12:52:07 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -1.977 X-Spam-Level: X-Spam-Status: No, score=-1.977 tagged_above=-999 required=5 tests=[AWL=-0.000, BAYES_00=-2.599, FM_FORGED_GMAIL=0.622] Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id T4MwzPFqnK9D for ; Tue, 22 Jan 2013 12:52:06 -0800 (PST) Received: from homiemail-a28.g.dreamhost.com (caiajhbdcaib.dreamhost.com [208.97.132.81]) by ietfa.amsl.com (Postfix) with ESMTP id BBC3521F8A48 for ; Tue, 22 Jan 2013 12:52:06 -0800 (PST) Received: from homiemail-a28.g.dreamhost.com (localhost [127.0.0.1]) by homiemail-a28.g.dreamhost.com (Postfix) with ESMTP id 667B11B4061 for ; Tue, 22 Jan 2013 12:52:06 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha1; c=relaxed; d=cryptonector.com; h= mime-version:in-reply-to:references:date:message-id:subject:from :to:cc:content-type; s=cryptonector.com; bh=pVkFIB/3zCnW4rgzRwvu bAazUdM=; b=I7ItNi7W4G2si4H1tjvn8jsIjfPnwelOG+Tiu9MeJ/UkBgwrMaZl Hq12bPQ4HbIbYEpyfH0xmr+Kdwf5TGVaqe58PFbgcQ98/W9lpLcDkbX7nVp5dtxc Uj9+gzw3IX79LbS2/wjJfdLkTzB8HzZ4d4Kmlr9x728CN0W2NS7Xbgs= Received: from mail-wi0-f176.google.com (mail-wi0-f176.google.com [209.85.212.176]) (using TLSv1 with cipher RC4-SHA (128/128 bits)) (No client certificate requested) (Authenticated sender: nico@cryptonector.com) by homiemail-a28.g.dreamhost.com (Postfix) with ESMTPSA id 1976E1B4059 for ; Tue, 22 Jan 2013 12:52:05 -0800 (PST) Received: by mail-wi0-f176.google.com with SMTP id hm6so82954wib.9 for ; Tue, 22 Jan 2013 12:52:04 -0800 (PST) MIME-Version: 1.0 X-Received: by 10.194.77.13 with SMTP id o13mr34809428wjw.58.1358887924655; Tue, 22 Jan 2013 12:52:04 -0800 (PST) Received: by 10.217.39.133 with HTTP; Tue, 22 Jan 2013 12:52:04 -0800 (PST) In-Reply-To: <000001cdf8e0$b1c98830$155c9890$@rozanak.com> References: <000001cdf8e0$b1c98830$155c9890$@rozanak.com> Date: Tue, 22 Jan 2013 14:52:04 -0600 Message-ID: From: Nico Williams To: Hosnieh Rafiee Content-Type: text/plain; charset=UTF-8 Cc: tools-discuss@ietf.org Subject: Re: [Tools-discuss] Tools-discuss Digest, Vol 99, Issue 10 X-BeenThere: tools-discuss@ietf.org X-Mailman-Version: 2.1.12 Precedence: list List-Id: IETF Tools Discussion List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 22 Jan 2013 20:52:07 -0000 On Tue, Jan 22, 2013 at 2:40 PM, Hosnieh Rafiee wrote: > Hello, > Has anybody ever tried to use my RFC tool after I uploaded a new version? > http://editor.rozanak.com Yes. There's no ASCII art editor though, right? But I'm sure you'll integrate one shortly! :) Of course, I'm still working on lyx2rfc... From ietf@rozanak.com Tue Jan 22 13:06:03 2013 Return-Path: X-Original-To: tools-discuss@ietfa.amsl.com Delivered-To: tools-discuss@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id AF41921F8684 for ; Tue, 22 Jan 2013 13:06:03 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -2.599 X-Spam-Level: X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599] Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id d8eTx5X461jf for ; Tue, 22 Jan 2013 13:06:03 -0800 (PST) Received: from mout.perfora.net (mout.perfora.net [74.208.4.195]) by ietfa.amsl.com (Postfix) with ESMTP id 0D3B921F8623 for ; Tue, 22 Jan 2013 13:06:00 -0800 (PST) Received: from kopoli (e179167194.adsl.alicedsl.de [85.179.167.194]) by mrelay.perfora.net (node=mrus3) with ESMTP (Nemesis) id 0MX0u4-1TRjeY0GPc-00Wf94; Tue, 22 Jan 2013 16:05:49 -0500 From: "Hosnieh Rafiee" To: "'Nico Williams'" References: <000001cdf8e0$b1c98830$155c9890$@rozanak.com> In-Reply-To: Date: Tue, 22 Jan 2013 22:05:41 +0100 Message-ID: <000201cdf8e4$3fb04140$bf10c3c0$@rozanak.com> MIME-Version: 1.0 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Mailer: Microsoft Outlook 14.0 Thread-Index: AQKSFFhWgv6taWwFnQvanqGdDqBo1AGH6e2gAazp3mWWs/ftwA== Content-Language: en-us X-Provags-ID: V02:K0:qh54Sy9VJSOhQIIigGMyymFCRcweBFm2TMka/U17RXo TZKr00ffdkbAdnwv9xjHnLjfM1HOT6FUnAZSlgxFY35y2xgqKO r3IvPYMrzETZDT5wqfZiED2ycFXz15Ti64mE4FZ6Yc/xI2wv2e f+91kEpq/Ft+uZ6pWznMEShgXZqdjISZzAfLeXWDR2KeEoUgdp 57sqgNPmuKU6rBdKyUvAf0R29E6+b+EK2CVvGF/Kv3pL2c9J0M WuwviXwiA/xANmFz02zlMFphTNttUiwx1kShVBG7LEbAJmhv/a VpXg5y0Y/F+POM8x9WcHgUucLwRxHLonL5r9ai0Grp7Ff1yCKy PiIMiDXg6M3OTbpdhubM= Cc: Tools-discuss@ietf.org Subject: Re: [Tools-discuss] Tools-discuss Digest, Vol 99, Issue 10 X-BeenThere: tools-discuss@ietf.org X-Mailman-Version: 2.1.12 Precedence: list List-Id: IETF Tools Discussion List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 22 Jan 2013 21:06:03 -0000 >Yes. There's no ASCII art editor though, right?=20 Unfortunately true. >But I'm sure you'll integrate one shortly! :) Yes , that was so nice. I will also add something like that to my tool = :-) >Of course, I'm still working on lyx2rfc... Great! I will try it when it is finished=20 Hosnieh -----Original Message----- From: Nico Williams [mailto:nico@cryptonector.com]=20 Sent: Tuesday, January 22, 2013 9:52 PM To: Hosnieh Rafiee Cc: tools-discuss@ietf.org Subject: Re: [Tools-discuss] Tools-discuss Digest, Vol 99, Issue 10 On Tue, Jan 22, 2013 at 2:40 PM, Hosnieh Rafiee = wrote: > Hello, > Has anybody ever tried to use my RFC tool after I uploaded a new = version? > http://editor.rozanak.com Yes. There's no ASCII art editor though, right? But I'm sure you'll = integrate one shortly! :) Of course, I'm still working on lyx2rfc... From nico@cryptonector.com Tue Jan 22 13:09:36 2013 Return-Path: X-Original-To: tools-discuss@ietfa.amsl.com Delivered-To: tools-discuss@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 4055621F8824 for ; Tue, 22 Jan 2013 13:09:36 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -3.615 X-Spam-Level: X-Spam-Status: No, score=-3.615 tagged_above=-999 required=5 tests=[AWL=-1.638, BAYES_00=-2.599, FM_FORGED_GMAIL=0.622] Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Ctv5GwRNYjRo for ; Tue, 22 Jan 2013 13:09:35 -0800 (PST) Received: from homiemail-a74.g.dreamhost.com (mailbigip.dreamhost.com [208.97.132.5]) by ietfa.amsl.com (Postfix) with ESMTP id EC45221F8735 for ; Tue, 22 Jan 2013 13:09:34 -0800 (PST) Received: from homiemail-a74.g.dreamhost.com (localhost [127.0.0.1]) by homiemail-a74.g.dreamhost.com (Postfix) with ESMTP id AEE5D67C076 for ; Tue, 22 Jan 2013 13:09:34 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha1; c=relaxed; d=cryptonector.com; h= mime-version:in-reply-to:references:date:message-id:subject:from :to:cc:content-type; s=cryptonector.com; bh=ZzVdejtcJs20EaQ12DDA P5NVnl4=; b=bpMMqCiRNAqET/ag0W9KCoBU2U8uvSe3CvV85vwvGyY7NOQ50VBo OfTOrbZxwHD/asP3f2B0tnsPhRoUTgEPVN2KHz0w/364zYE290TPQ6VwPRXsiuor GygX+ZRqqgR/VQZ9fAXQybhYWT1QQ/n+0+eLYSEvw7Ntnnws7m/bbP4= Received: from mail-wg0-f54.google.com (mail-wg0-f54.google.com [74.125.82.54]) (using TLSv1 with cipher RC4-SHA (128/128 bits)) (No client certificate requested) (Authenticated sender: nico@cryptonector.com) by homiemail-a74.g.dreamhost.com (Postfix) with ESMTPSA id 538A367C075 for ; Tue, 22 Jan 2013 13:09:34 -0800 (PST) Received: by mail-wg0-f54.google.com with SMTP id fg15so4651645wgb.21 for ; Tue, 22 Jan 2013 13:09:33 -0800 (PST) MIME-Version: 1.0 X-Received: by 10.194.80.73 with SMTP id p9mr35228490wjx.4.1358888973077; Tue, 22 Jan 2013 13:09:33 -0800 (PST) Received: by 10.217.39.133 with HTTP; Tue, 22 Jan 2013 13:09:33 -0800 (PST) In-Reply-To: <000201cdf8e4$3fb04140$bf10c3c0$@rozanak.com> References: <000001cdf8e0$b1c98830$155c9890$@rozanak.com> <000201cdf8e4$3fb04140$bf10c3c0$@rozanak.com> Date: Tue, 22 Jan 2013 15:09:33 -0600 Message-ID: From: Nico Williams To: Hosnieh Rafiee Content-Type: text/plain; charset=UTF-8 Cc: Tools-discuss@ietf.org Subject: Re: [Tools-discuss] Tools-discuss Digest, Vol 99, Issue 10 X-BeenThere: tools-discuss@ietf.org X-Mailman-Version: 2.1.12 Precedence: list List-Id: IETF Tools Discussion List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 22 Jan 2013 21:09:36 -0000 On Tue, Jan 22, 2013 at 3:05 PM, Hosnieh Rafiee wrote: >>Yes. There's no ASCII art editor though, right? > Unfortunately true. > > >But I'm sure you'll integrate one shortly! :) > Yes , that was so nice. I will also add something like that to my tool :-) > >>Of course, I'm still working on lyx2rfc... > Great! I will try it when it is finished Heck, you can try it now as it's quite functional. I've been using it and Yaron Sheffer's been using it. Yaron even has a web page that takes .lyx and formats it as an RFC using lyx2rfc: http://lyx2rfc.d.porticor.net/lyx2rfc/lyx2rfc.html Nico -- From yaronf.ietf@gmail.com Mon Jan 28 07:28:24 2013 Return-Path: X-Original-To: tools-discuss@ietfa.amsl.com Delivered-To: tools-discuss@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 1B61321F8763 for ; Mon, 28 Jan 2013 07:28:24 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -103.598 X-Spam-Level: X-Spam-Status: No, score=-103.598 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1, USER_IN_WHITELIST=-100, WEIRD_PORT=0.001] Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 3DDJJyU+orov for ; Mon, 28 Jan 2013 07:28:23 -0800 (PST) Received: from mail-lb0-f172.google.com (mail-lb0-f172.google.com [209.85.217.172]) by ietfa.amsl.com (Postfix) with ESMTP id 39EAD21F8767 for ; Mon, 28 Jan 2013 07:28:17 -0800 (PST) Received: by mail-lb0-f172.google.com with SMTP id n8so4076234lbj.3 for ; Mon, 28 Jan 2013 07:28:16 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=x-received:message-id:date:from:user-agent:mime-version:to:subject :content-type:content-transfer-encoding; bh=eHB67QJYqLBeJkDkpdRaryKy8p52qh/KSH9TYYLGIxs=; b=RSsAHADR+buS42bMw8dxOzZepaWwCp7DmyaeBVMGVJBG/lzVKEfKKg92Rc0Nm6TK8r dXMb3df7G7TxDNWhIlrt4DBWjzjFRPUI0ioHBYnn/PgeoWErqkyKBJ22K+mAN+rD29yT UqWGBbtgicbQ+ry2YLlR5pxTb00HgVd7tzDvexM/RjD//fGKo5FG2f0cwT2QcGXEMyWX IyHBHAGPzL66CdZU1KQVexdszQ6h39jB8oe5FPjGNIlV52Aa/fcgZUlgKsvfKS50ep+F X9P6qMvE8SXaFQI8FwJvZ6XGPR1zKc2wI9y/nnQbzFXHRlJjZrQuiDu9wIDrb+POr8vt ewKQ== X-Received: by 10.112.42.103 with SMTP id n7mr1251573lbl.52.1359386896134; Mon, 28 Jan 2013 07:28:16 -0800 (PST) Received: from [10.0.0.5] (bzq-79-176-124-5.red.bezeqint.net. [79.176.124.5]) by mx.google.com with ESMTPS id gi3sm3785116lab.7.2013.01.28.07.28.13 (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Mon, 28 Jan 2013 07:28:14 -0800 (PST) Message-ID: <51069907.4030203@gmail.com> Date: Mon, 28 Jan 2013 17:28:07 +0200 From: Yaron Sheffer User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:17.0) Gecko/20130106 Thunderbird/17.0.2 MIME-Version: 1.0 To: tools-discuss@ietf.org Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Subject: [Tools-discuss] RFC comment system X-BeenThere: tools-discuss@ietf.org X-Mailman-Version: 2.1.12 Precedence: list List-Id: IETF Tools Discussion List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 28 Jan 2013 15:28:24 -0000 Hi, a while ago there was a long thread on the IETF-discuss list about "wikis for RFCs". My own take on that ( http://www.ietf.org/mail-archive/web/ietf/current/msg69413.html) was that several projects benefit significantly from allowing the community to comment openly on specifications. One such example is the PHP manual, which is not bad in itself, but is greatly enhanced by numerous comments from the community. I ended up developing such a system specifically for RFCs. It is very basic, and extremely rough around the edges. It is available at http://rfcpop.d.porticor.net:8000/ . The code is available at https://github.com/yaronf/rfcpop. I would appreciate people's comments and suggestions. It would be absolutely awesome if people join in developing the app to the point where it can be used by non-IETF regulars. In case you were wondering, the technology used is Python/Django and JavaScript/JQuery. Thanks, Yaron From nico@cryptonector.com Mon Jan 28 08:06:27 2013 Return-Path: X-Original-To: tools-discuss@ietfa.amsl.com Delivered-To: tools-discuss@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id C2AE321F8821 for ; Mon, 28 Jan 2013 08:06:27 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -4.357 X-Spam-Level: X-Spam-Status: No, score=-4.357 tagged_above=-999 required=5 tests=[AWL=-2.381, BAYES_00=-2.599, FM_FORGED_GMAIL=0.622, WEIRD_PORT=0.001] Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 2sshGPHg6dxz for ; Mon, 28 Jan 2013 08:06:27 -0800 (PST) Received: from homiemail-a24.g.dreamhost.com (caiajhbdcaid.dreamhost.com [208.97.132.83]) by ietfa.amsl.com (Postfix) with ESMTP id A2E0921F870A for ; Mon, 28 Jan 2013 08:06:23 -0800 (PST) Received: from homiemail-a24.g.dreamhost.com (localhost [127.0.0.1]) by homiemail-a24.g.dreamhost.com (Postfix) with ESMTP id 281352C8075 for ; Mon, 28 Jan 2013 08:06:18 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha1; c=relaxed; d=cryptonector.com; h= mime-version:in-reply-to:references:date:message-id:subject:from :to:cc:content-type; s=cryptonector.com; bh=CdTpRw8zCrHubLXkUutS L74Mhcw=; b=pC5rWxbKJVRH3NZwZGGzD5B6MGe9nEhpZ23SqcVbJ6hXeNLrVSh1 yQaKaPG5nRMkxf17lszU8UM6gUnlq9LTCifOihljJ5HA1MzFQHFDuSn6uPjDLu5x FUXDSUrpQu3hEGLee0+/zVBHfQpg9aVY5btfnz4tGMIsI0EbtpawMvE= Received: from mail-wi0-f182.google.com (mail-wi0-f182.google.com [209.85.212.182]) (using TLSv1 with cipher RC4-SHA (128/128 bits)) (No client certificate requested) (Authenticated sender: nico@cryptonector.com) by homiemail-a24.g.dreamhost.com (Postfix) with ESMTPSA id DEB662C806B for ; Mon, 28 Jan 2013 08:06:08 -0800 (PST) Received: by mail-wi0-f182.google.com with SMTP id hn14so1582295wib.15 for ; Mon, 28 Jan 2013 08:06:06 -0800 (PST) MIME-Version: 1.0 X-Received: by 10.194.77.13 with SMTP id o13mr22267247wjw.58.1359389166762; Mon, 28 Jan 2013 08:06:06 -0800 (PST) Received: by 10.217.39.133 with HTTP; Mon, 28 Jan 2013 08:06:06 -0800 (PST) In-Reply-To: <51069907.4030203@gmail.com> References: <51069907.4030203@gmail.com> Date: Mon, 28 Jan 2013 10:06:06 -0600 Message-ID: From: Nico Williams To: Yaron Sheffer Content-Type: text/plain; charset=UTF-8 Cc: tools-discuss@ietf.org Subject: Re: [Tools-discuss] RFC comment system X-BeenThere: tools-discuss@ietf.org X-Mailman-Version: 2.1.12 Precedence: list List-Id: IETF Tools Discussion List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 28 Jan 2013 16:06:27 -0000 On Mon, Jan 28, 2013 at 9:28 AM, Yaron Sheffer wrote: > a while ago there was a long thread on the IETF-discuss list about "wikis > for RFCs". My own take on that ( > http://www.ietf.org/mail-archive/web/ietf/current/msg69413.html) was that > several projects benefit significantly from allowing the community to > comment openly on specifications. One such example is the PHP manual, which > is not bad in itself, but is greatly enhanced by numerous comments from the > community. I agree, a comment system for RFCs would be great to have. It should include links to errata, Internet-Drafts in the works for updates or obsolescence of each RFC, I-D history, working group (possibly concluded), IESG balloting (if relevant), and so on. > I ended up developing such a system specifically for RFCs. It is very basic, > and extremely rough around the edges. It is available at > http://rfcpop.d.porticor.net:8000/ > . The code is available at > https://github.com/yaronf/rfcpop. It'd be nice if comments were viewable without having to login. I'm not sure that this is exactly how I'd like RFC comments to be handled. A wiki wouldn't be quite right either though. We may need frames for this... Nico -- From yaronf.ietf@gmail.com Mon Jan 28 08:17:09 2013 Return-Path: X-Original-To: tools-discuss@ietfa.amsl.com Delivered-To: tools-discuss@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id D4B3421F8507 for ; Mon, 28 Jan 2013 08:17:09 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -102.213 X-Spam-Level: X-Spam-Status: No, score=-102.213 tagged_above=-999 required=5 tests=[AWL=-1.385, BAYES_00=-2.599, FH_HOST_EQ_D_D_D_D=0.765, RCVD_IN_PBL=0.905, RDNS_DYNAMIC=0.1, USER_IN_WHITELIST=-100, WEIRD_PORT=0.001] Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id BBJGxnky8qvK for ; Mon, 28 Jan 2013 08:17:09 -0800 (PST) Received: from mail-la0-x231.google.com (mail-la0-x231.google.com [IPv6:2a00:1450:4010:c03::231]) by ietfa.amsl.com (Postfix) with ESMTP id DE21221F8505 for ; Mon, 28 Jan 2013 08:17:08 -0800 (PST) Received: by mail-la0-f49.google.com with SMTP id fs13so899334lab.22 for ; Mon, 28 Jan 2013 08:17:07 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=x-received:message-id:date:from:user-agent:mime-version:to:cc :subject:references:in-reply-to:content-type :content-transfer-encoding; bh=odw52CU3HUM/b/Hf/h/Ep6DZDo1BGWgw9zFzJATTxrU=; b=WLlJWbdSOizQq5bTtjCeJYqqv/9IL+C597PlSlu6dx/Z5cPDlu0EyfnOSl2GD03Bhm LhDrfit8sGU8ZYseph7bKJOB9pkXve41DppJaaTY1oQ5wrv8zJ4ECpufT7V/W0WGc7AX xQYugdQDs+lL+EHsbPKEraMaxyFQ637Ly8SRBhRhd+hkacy+7ZHFsG1lMDuODIfRDLmC adzItqgreOZsI1Xk5jMDFKVbq0NO+HSKho//SFe4wJZVTNNfeobocO2Kxu1KbXYfKSeh R1J/ApCy/WhoGLUQp7+TOBw6WRHXfeBSxB2sikkJz2QdfW+BwCI/PYChhSEQAFwt83x2 wMgQ== X-Received: by 10.112.45.232 with SMTP id q8mr5946414lbm.23.1359389827756; Mon, 28 Jan 2013 08:17:07 -0800 (PST) Received: from [10.0.0.5] (bzq-79-176-124-5.red.bezeqint.net. [79.176.124.5]) by mx.google.com with ESMTPS id fj2sm3930533lbb.6.2013.01.28.08.17.04 (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Mon, 28 Jan 2013 08:17:06 -0800 (PST) Message-ID: <5106A47B.7060802@gmail.com> Date: Mon, 28 Jan 2013 18:16:59 +0200 From: Yaron Sheffer User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:17.0) Gecko/20130106 Thunderbird/17.0.2 MIME-Version: 1.0 To: Nico Williams References: <51069907.4030203@gmail.com> In-Reply-To: Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit Cc: tools-discuss@ietf.org Subject: Re: [Tools-discuss] RFC comment system X-BeenThere: tools-discuss@ietf.org X-Mailman-Version: 2.1.12 Precedence: list List-Id: IETF Tools Discussion List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 28 Jan 2013 16:17:09 -0000 Hi Nico, comments can be viewed without having to login. Go to http://rfcpop.d.porticor.net:8000/rfcpop/rfc/4041 and scroll down a bit. The idea is that they are visually distinct from the running text, but still in-line. Thanks, Yaron On 01/28/2013 06:06 PM, Nico Williams wrote: > On Mon, Jan 28, 2013 at 9:28 AM, Yaron Sheffer wrote: >> a while ago there was a long thread on the IETF-discuss list about "wikis >> for RFCs". My own take on that ( >> http://www.ietf.org/mail-archive/web/ietf/current/msg69413.html) was that >> several projects benefit significantly from allowing the community to >> comment openly on specifications. One such example is the PHP manual, which >> is not bad in itself, but is greatly enhanced by numerous comments from the >> community. > > I agree, a comment system for RFCs would be great to have. It should > include links to errata, Internet-Drafts in the works for updates or > obsolescence of each RFC, I-D history, working group (possibly > concluded), IESG balloting (if relevant), and so on. > >> I ended up developing such a system specifically for RFCs. It is very basic, >> and extremely rough around the edges. It is available at >> http://rfcpop.d.porticor.net:8000/ >> . The code is available at >> https://github.com/yaronf/rfcpop. > > It'd be nice if comments were viewable without having to login. > > I'm not sure that this is exactly how I'd like RFC comments to be > handled. A wiki wouldn't be quite right either though. We may need > frames for this... > > Nico > -- > From nico@cryptonector.com Mon Jan 28 09:01:02 2013 Return-Path: X-Original-To: tools-discuss@ietfa.amsl.com Delivered-To: tools-discuss@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 0909321F8A0C for ; Mon, 28 Jan 2013 09:01:02 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -4.208 X-Spam-Level: X-Spam-Status: No, score=-4.208 tagged_above=-999 required=5 tests=[AWL=-2.232, BAYES_00=-2.599, FM_FORGED_GMAIL=0.622, WEIRD_PORT=0.001] Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id lBG84nMjczFD for ; Mon, 28 Jan 2013 09:01:01 -0800 (PST) Received: from homiemail-a72.g.dreamhost.com (caiajhbdcaib.dreamhost.com [208.97.132.81]) by ietfa.amsl.com (Postfix) with ESMTP id E879821F8A08 for ; Mon, 28 Jan 2013 09:01:00 -0800 (PST) Received: from homiemail-a72.g.dreamhost.com (localhost [127.0.0.1]) by homiemail-a72.g.dreamhost.com (Postfix) with ESMTP id A19D96B0087 for ; Mon, 28 Jan 2013 09:01:00 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha1; c=relaxed; d=cryptonector.com; h= mime-version:in-reply-to:references:date:message-id:subject:from :to:cc:content-type; s=cryptonector.com; bh=eSq0LBvCzlVROL0/nSvy qmFmErg=; b=y3rCpe5eTY8aAOa4tFZI1BMoEihtyg8furRJ2Fd2R0ko/DDFrW00 YVXe58WBCVD13930J541N2/inMJwTdsaz/PB6f2jXk6s2/Nlt5ccG7HsUq9cG9CU HNWg9Ul71DbJF3Q1jARjlN7opCroW+UUQsT2L5qGAVpf36Z+/PgFwg4= Received: from mail-wi0-f170.google.com (mail-wi0-f170.google.com [209.85.212.170]) (using TLSv1 with cipher RC4-SHA (128/128 bits)) (No client certificate requested) (Authenticated sender: nico@cryptonector.com) by homiemail-a72.g.dreamhost.com (Postfix) with ESMTPSA id 433AC6B0084 for ; Mon, 28 Jan 2013 09:01:00 -0800 (PST) Received: by mail-wi0-f170.google.com with SMTP id cb5so905246wib.1 for ; Mon, 28 Jan 2013 09:00:58 -0800 (PST) MIME-Version: 1.0 X-Received: by 10.180.108.236 with SMTP id hn12mr11070818wib.6.1359392458672; Mon, 28 Jan 2013 09:00:58 -0800 (PST) Received: by 10.217.39.133 with HTTP; Mon, 28 Jan 2013 09:00:58 -0800 (PST) In-Reply-To: <5106A47B.7060802@gmail.com> References: <51069907.4030203@gmail.com> <5106A47B.7060802@gmail.com> Date: Mon, 28 Jan 2013 11:00:58 -0600 Message-ID: From: Nico Williams To: Yaron Sheffer Content-Type: text/plain; charset=UTF-8 Cc: tools-discuss@ietf.org Subject: Re: [Tools-discuss] RFC comment system X-BeenThere: tools-discuss@ietf.org X-Mailman-Version: 2.1.12 Precedence: list List-Id: IETF Tools Discussion List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 28 Jan 2013 17:01:02 -0000 On Mon, Jan 28, 2013 at 10:16 AM, Yaron Sheffer wrote: > comments can be viewed without having to login. Go to > http://rfcpop.d.porticor.net:8000/rfcpop/rfc/4041 and scroll down a bit. Ah, sorry I missed that. > The idea is that they are visually distinct from the running text, but still > in-line. But not all comments should be in-line. For example: general comments, comments on the history of the RFC, and comments on future updates. For those I'd rather have a wiki. I'd also like to have a ticketing system. Hmmm. You know, Fossil is a VCS that includes a wiki and a ticketing system... we might be able to combine that with a tool like yours to make in-line comments just updates (commits) to the HTML renderings of RFCs and then combine that with the wiki and ticketing. With a bit more code we might be able to have several frames, one with the RFC, one with the wiki, and one with a ticket search box. Nico -- From yaronf.ietf@gmail.com Mon Jan 28 09:21:58 2013 Return-Path: X-Original-To: tools-discuss@ietfa.amsl.com Delivered-To: tools-discuss@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 6804921F8718 for ; Mon, 28 Jan 2013 09:21:58 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -101.52 X-Spam-Level: X-Spam-Status: No, score=-101.52 tagged_above=-999 required=5 tests=[AWL=-0.693, BAYES_00=-2.599, FH_HOST_EQ_D_D_D_D=0.765, RCVD_IN_PBL=0.905, RDNS_DYNAMIC=0.1, USER_IN_WHITELIST=-100, WEIRD_PORT=0.001] Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 8jNvqSC0kvJc for ; Mon, 28 Jan 2013 09:21:57 -0800 (PST) Received: from mail-la0-x236.google.com (la-in-x0236.1e100.net [IPv6:2a00:1450:4010:c03::236]) by ietfa.amsl.com (Postfix) with ESMTP id 69C8421F8717 for ; Mon, 28 Jan 2013 09:21:57 -0800 (PST) Received: by mail-la0-f54.google.com with SMTP id gw10so971448lab.27 for ; Mon, 28 Jan 2013 09:21:56 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=x-received:message-id:date:from:user-agent:mime-version:to:cc :subject:references:in-reply-to:content-type :content-transfer-encoding; bh=Fmm91uK50IVJU2mHv0y5FSuLu6qigaGpTu9uOHgXdHM=; b=d/dJG/Na8jr3AgWSyf8P2Ogn/W6MqtKO+0iQG0S6fg7PzONALBL9nmiV7ZG1V+UvUR ut6hwbhPtW/wUTFnrq9usiCtiem2vr6lAqIXRUXvhK81EBvOmLmgcPYLftAwJpJ406rR 9WNk+bPTmAJ4FNx19ju410xiHMR9/sadJ0ZibS0qusZ6MWefsF6Hx0sEyQKGGQNKRkBe 3Ew82mTl5akinLW+MTiq5dumtemsxyZRsbMXkkTQYGuHL6jUbqpV556EIxk/K2mA3gCG be21yS8/1wY3xg4L9Zkk+RDHPBhaiVwbxTLflDJ8P2oxm22KZpVGi7KzhQwJFCAtXr1r EU7w== X-Received: by 10.152.125.237 with SMTP id mt13mr13902250lab.45.1359393716219; Mon, 28 Jan 2013 09:21:56 -0800 (PST) Received: from [10.0.0.5] (bzq-79-176-124-5.red.bezeqint.net. [79.176.124.5]) by mx.google.com with ESMTPS id iw6sm3972079lab.2.2013.01.28.09.21.53 (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Mon, 28 Jan 2013 09:21:54 -0800 (PST) Message-ID: <5106B3AF.7030105@gmail.com> Date: Mon, 28 Jan 2013 19:21:51 +0200 From: Yaron Sheffer User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:17.0) Gecko/20130106 Thunderbird/17.0.2 MIME-Version: 1.0 To: Nico Williams References: <51069907.4030203@gmail.com> <5106A47B.7060802@gmail.com> In-Reply-To: Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit Cc: tools-discuss@ietf.org Subject: Re: [Tools-discuss] RFC comment system X-BeenThere: tools-discuss@ietf.org X-Mailman-Version: 2.1.12 Precedence: list List-Id: IETF Tools Discussion List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 28 Jan 2013 17:21:58 -0000 In the discussion on ietf-discuss people raised some good objections to the idea of associating a wiki with each RFC. I can dig them up, but off the top of my head, people were worried about "edit wars" being used to drag WG arguments forever, where today they are put to rest as soon as the RFC is published. But even if we do add a wiki-per-RFC (and I can see some benefits, too), I don't think that a ticketing system is appropriate. A ticketing system requires some level of accountability. If I open a ticket for a random RFC (e.g. RFC 793), can I expect anything to come out of it? Thanks, Yaron On 01/28/2013 07:00 PM, Nico Williams wrote: > On Mon, Jan 28, 2013 at 10:16 AM, Yaron Sheffer wrote: >> comments can be viewed without having to login. Go to >> http://rfcpop.d.porticor.net:8000/rfcpop/rfc/4041 and scroll down a bit. > > Ah, sorry I missed that. > >> The idea is that they are visually distinct from the running text, but still >> in-line. > > But not all comments should be in-line. For example: general > comments, comments on the history of the RFC, and comments on future > updates. For those I'd rather have a wiki. I'd also like to have a > ticketing system. > > Hmmm. You know, Fossil is a VCS that includes a wiki and a ticketing > system... we might be able to combine that with a tool like yours to > make in-line comments just updates (commits) to the HTML renderings of > RFCs and then combine that with the wiki and ticketing. With a bit > more code we might be able to have several frames, one with the RFC, > one with the wiki, and one with a ticket search box. > > Nico > -- > From nico@cryptonector.com Mon Jan 28 09:41:08 2013 Return-Path: X-Original-To: tools-discuss@ietfa.amsl.com Delivered-To: tools-discuss@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 27EE721F8999 for ; Mon, 28 Jan 2013 09:41:08 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -3.712 X-Spam-Level: X-Spam-Status: No, score=-3.712 tagged_above=-999 required=5 tests=[AWL=-1.735, BAYES_00=-2.599, FM_FORGED_GMAIL=0.622] Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id cdH3dA9Qd1ZH for ; Mon, 28 Jan 2013 09:41:07 -0800 (PST) Received: from homiemail-a31.g.dreamhost.com (caiajhbdccah.dreamhost.com [208.97.132.207]) by ietfa.amsl.com (Postfix) with ESMTP id 8586421F87D5 for ; Mon, 28 Jan 2013 09:41:07 -0800 (PST) Received: from homiemail-a31.g.dreamhost.com (localhost [127.0.0.1]) by homiemail-a31.g.dreamhost.com (Postfix) with ESMTP id 7999E202057 for ; Mon, 28 Jan 2013 09:41:05 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha1; c=relaxed; d=cryptonector.com; h= mime-version:in-reply-to:references:date:message-id:subject:from :to:cc:content-type; s=cryptonector.com; bh=GfZ2lH8PMqNWSiOn1ElO 5Yv7NW0=; b=MonDFHoUK3X+8LB5jQr8WJw91CytVTQAtjTCgL1WW5o6pdTetHil c0AilB5sitw1154Rdni1dR3s6h/mZ6WQXL5QviRP3jxTU9djM//wlvVT0qBLgyRx QOTyHgEjsThObYZ1SDeqHY/BBj/7tVWmtdWBzsxQi31VZ1S6WMW5VPQ= Received: from mail-wg0-f47.google.com (mail-wg0-f47.google.com [74.125.82.47]) (using TLSv1 with cipher RC4-SHA (128/128 bits)) (No client certificate requested) (Authenticated sender: nico@cryptonector.com) by homiemail-a31.g.dreamhost.com (Postfix) with ESMTPSA id EF55A20204F for ; Mon, 28 Jan 2013 09:41:04 -0800 (PST) Received: by mail-wg0-f47.google.com with SMTP id dr13so1840171wgb.2 for ; Mon, 28 Jan 2013 09:41:03 -0800 (PST) MIME-Version: 1.0 X-Received: by 10.180.90.147 with SMTP id bw19mr11302828wib.28.1359394863354; Mon, 28 Jan 2013 09:41:03 -0800 (PST) Received: by 10.217.39.133 with HTTP; Mon, 28 Jan 2013 09:41:03 -0800 (PST) In-Reply-To: <5106B3AF.7030105@gmail.com> References: <51069907.4030203@gmail.com> <5106A47B.7060802@gmail.com> <5106B3AF.7030105@gmail.com> Date: Mon, 28 Jan 2013 11:41:03 -0600 Message-ID: From: Nico Williams To: Yaron Sheffer Content-Type: text/plain; charset=UTF-8 Cc: tools-discuss@ietf.org Subject: Re: [Tools-discuss] RFC comment system X-BeenThere: tools-discuss@ietf.org X-Mailman-Version: 2.1.12 Precedence: list List-Id: IETF Tools Discussion List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 28 Jan 2013 17:41:08 -0000 On Mon, Jan 28, 2013 at 11:21 AM, Yaron Sheffer wrote: > In the discussion on ietf-discuss people raised some good objections to the > idea of associating a wiki with each RFC. I can dig them up, but off the top > of my head, people were worried about "edit wars" being used to drag WG > arguments forever, where today they are put to rest as soon as the RFC is > published. Sure, but anyone can publish whatever the heck they want anyways. A wiki could have a registration and even authorization requirements and then be really useful for, for example. A wiki would be a great place to have tutorials, general introductions to a large topic, lists of [and links to] implementations, implementor advice beyond that given in the RFC(s), ... I understand that policing wikis will add to the burden of WG chairs and ADs, but we could arrange so that RFC authors (where available) do most of the work. > But even if we do add a wiki-per-RFC (and I can see some benefits, too), I > don't think that a ticketing system is appropriate. A ticketing system > requires some level of accountability. If I open a ticket for a random RFC > (e.g. RFC 793), can I expect anything to come out of it? To me this would be much like the errata process. Anyone could create a ticket, but the ticket will only be accepted if the issue is deemed real by a suitable expert selected by the RFC-Editor or relevant AD. Nico -- From yaronf.ietf@gmail.com Mon Jan 28 09:55:11 2013 Return-Path: X-Original-To: tools-discuss@ietfa.amsl.com Delivered-To: tools-discuss@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 53B8C21F8999 for ; Mon, 28 Jan 2013 09:55:11 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -102.675 X-Spam-Level: X-Spam-Status: No, score=-102.675 tagged_above=-999 required=5 tests=[AWL=0.924, BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1, USER_IN_WHITELIST=-100] Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id CY20xTxyTeC3 for ; Mon, 28 Jan 2013 09:55:10 -0800 (PST) Received: from mail-lb0-f177.google.com (mail-lb0-f177.google.com [209.85.217.177]) by ietfa.amsl.com (Postfix) with ESMTP id 8154F21F87E0 for ; Mon, 28 Jan 2013 09:55:10 -0800 (PST) Received: by mail-lb0-f177.google.com with SMTP id go11so4189380lbb.8 for ; Mon, 28 Jan 2013 09:55:09 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=x-received:message-id:date:from:user-agent:mime-version:to:cc :subject:references:in-reply-to:content-type :content-transfer-encoding; bh=4u9Z40iqLSeTW5qTzvruOKbpx1tupq68Uc0rJhLAsaQ=; b=VWv4EoPYBhZYUr6vdr1Lk364RiV1FfpPOPcY7BcCz1etG2b9UVvoE0Lfn+o/GLwsxx 8BxDK3xmG6dD+6W+nZHcidKgQqsJ0odyAYR7vqljnnD4FZGAaEUwTh058/JdeuxD24Yb Xgnt9n8TPc+lm5MUO+xDeWF7z8hETd62hSlwkvcc9oLJH6fdlScYacmAByngXdfP2iX7 WnVGD9JKL7RgsX5QdA2TXfsNPpuV/W4dPvsV1ncXaNe5uNgdRKc2uWLd3Hxl5CzR6ZTq wz5UcEwQo7UwhK32BGlamZhhVgpOmSAhTaYZUqe7Js0uH4BK2sqNn1ITfXRLkaFC43Bn TnsA== X-Received: by 10.152.111.102 with SMTP id ih6mr13966622lab.20.1359395709317; Mon, 28 Jan 2013 09:55:09 -0800 (PST) Received: from [10.0.0.5] (bzq-79-176-124-5.red.bezeqint.net. [79.176.124.5]) by mx.google.com with ESMTPS id tm10sm4008532lab.10.2013.01.28.09.55.06 (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Mon, 28 Jan 2013 09:55:08 -0800 (PST) Message-ID: <5106BB79.6090206@gmail.com> Date: Mon, 28 Jan 2013 19:55:05 +0200 From: Yaron Sheffer User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:17.0) Gecko/20130106 Thunderbird/17.0.2 MIME-Version: 1.0 To: Nico Williams References: <51069907.4030203@gmail.com> <5106A47B.7060802@gmail.com> <5106B3AF.7030105@gmail.com> In-Reply-To: Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit Cc: tools-discuss@ietf.org Subject: Re: [Tools-discuss] RFC comment system X-BeenThere: tools-discuss@ietf.org X-Mailman-Version: 2.1.12 Precedence: list List-Id: IETF Tools Discussion List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 28 Jan 2013 17:55:11 -0000 Just to clarify my (possibly naive) view on this: long term, this should be as unofficial as other "tools" activities, with no new processes imposed on authors or the secretariat (Mr. Bradner, someone just opened a ticket for RFC 2119, do you want to approve it?). The only real maintenance activity that cannot be avoided - but may be somewhat automated - is dealing with spam. Thanks, Yaron On 01/28/2013 07:41 PM, Nico Williams wrote: > On Mon, Jan 28, 2013 at 11:21 AM, Yaron Sheffer wrote: >> In the discussion on ietf-discuss people raised some good objections to the >> idea of associating a wiki with each RFC. I can dig them up, but off the top >> of my head, people were worried about "edit wars" being used to drag WG >> arguments forever, where today they are put to rest as soon as the RFC is >> published. > > Sure, but anyone can publish whatever the heck they want anyways. A > wiki could have a registration and even authorization requirements and > then be really useful for, for example. A wiki would be a great place > to have tutorials, general introductions to a large topic, lists of > [and links to] implementations, implementor advice beyond that given > in the RFC(s), ... I understand that policing wikis will add to the > burden of WG chairs and ADs, but we could arrange so that RFC authors > (where available) do most of the work. > >> But even if we do add a wiki-per-RFC (and I can see some benefits, too), I >> don't think that a ticketing system is appropriate. A ticketing system >> requires some level of accountability. If I open a ticket for a random RFC >> (e.g. RFC 793), can I expect anything to come out of it? > > To me this would be much like the errata process. Anyone could create > a ticket, but the ticket will only be accepted if the issue is deemed > real by a suitable expert selected by the RFC-Editor or relevant AD. > > Nico > -- > From nico@cryptonector.com Mon Jan 28 10:04:16 2013 Return-Path: X-Original-To: tools-discuss@ietfa.amsl.com Delivered-To: tools-discuss@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 01ACA21F87A4 for ; Mon, 28 Jan 2013 10:04:16 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -4.077 X-Spam-Level: X-Spam-Status: No, score=-4.077 tagged_above=-999 required=5 tests=[AWL=-2.100, BAYES_00=-2.599, FM_FORGED_GMAIL=0.622] Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id m7up4Re5DRTK for ; Mon, 28 Jan 2013 10:04:15 -0800 (PST) Received: from homiemail-a77.g.dreamhost.com (caiajhbdcagg.dreamhost.com [208.97.132.66]) by ietfa.amsl.com (Postfix) with ESMTP id 7A7A721F86F6 for ; Mon, 28 Jan 2013 10:04:15 -0800 (PST) Received: from homiemail-a77.g.dreamhost.com (localhost [127.0.0.1]) by homiemail-a77.g.dreamhost.com (Postfix) with ESMTP id A0E3D9406D for ; Mon, 28 Jan 2013 10:04:13 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha1; c=relaxed; d=cryptonector.com; h= mime-version:in-reply-to:references:date:message-id:subject:from :to:cc:content-type; s=cryptonector.com; bh=eUXR3Gki9lTxgKFySvhy eP/gIT8=; b=WhcVmLeFUhDW35BZSVmEIrYr9tvM5Wxx9gAJIO5k87kh5Q9Praes mK+oowzFBQGezx36WMVIMuOceDh8fVP0ADMnXTuQf6dI5nyd9yEYVycVMW99MvN+ q7tEvInsKyIOZr+dbIk0br3ixXl6j7sxizJ3S96NHtVmyZgjOzKP7Vw= Received: from mail-wi0-f177.google.com (mail-wi0-f177.google.com [209.85.212.177]) (using TLSv1 with cipher RC4-SHA (128/128 bits)) (No client certificate requested) (Authenticated sender: nico@cryptonector.com) by homiemail-a77.g.dreamhost.com (Postfix) with ESMTPSA id 4A36A94059 for ; Mon, 28 Jan 2013 10:04:13 -0800 (PST) Received: by mail-wi0-f177.google.com with SMTP id hm14so629934wib.10 for ; Mon, 28 Jan 2013 10:04:12 -0800 (PST) MIME-Version: 1.0 X-Received: by 10.194.77.13 with SMTP id o13mr22928570wjw.58.1359396252075; Mon, 28 Jan 2013 10:04:12 -0800 (PST) Received: by 10.217.39.133 with HTTP; Mon, 28 Jan 2013 10:04:11 -0800 (PST) In-Reply-To: <5106BB79.6090206@gmail.com> References: <51069907.4030203@gmail.com> <5106A47B.7060802@gmail.com> <5106B3AF.7030105@gmail.com> <5106BB79.6090206@gmail.com> Date: Mon, 28 Jan 2013 12:04:11 -0600 Message-ID: From: Nico Williams To: Yaron Sheffer Content-Type: text/plain; charset=UTF-8 Cc: tools-discuss@ietf.org Subject: Re: [Tools-discuss] RFC comment system X-BeenThere: tools-discuss@ietf.org X-Mailman-Version: 2.1.12 Precedence: list List-Id: IETF Tools Discussion List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 28 Jan 2013 18:04:16 -0000 On Mon, Jan 28, 2013 at 11:55 AM, Yaron Sheffer wrote: > Just to clarify my (possibly naive) view on this: long term, this should be > as unofficial as other "tools" activities, with no new processes imposed on > authors or the secretariat (Mr. Bradner, someone just opened a ticket for > RFC 2119, do you want to approve it?). Sure, but as with errata, someone will want to review some of these things. Alternatively we should just not have any such tools hosted by the IETF (and also really not by IETF participants; blogging is one things, but hosting a potentially popular tool that the IETF chooses not to to avoid maintenance burdens will... cause the same maintenance burdens). > The only real maintenance activity that cannot be avoided - but may be > somewhat automated - is dealing with spam. This can probably be helped by having a requirement that one have posted some number of messages to IETF mailing lists in order to register for the wiki. Nico -- From martin.thomson@gmail.com Mon Jan 28 11:39:39 2013 Return-Path: X-Original-To: tools-discuss@ietfa.amsl.com Delivered-To: tools-discuss@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id E05DF21F8783 for ; Mon, 28 Jan 2013 11:39:38 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -2.6 X-Spam-Level: X-Spam-Status: No, score=-2.6 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, NO_RELAYS=-0.001] Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 7kU3ZlEIoKee for ; Mon, 28 Jan 2013 11:39:38 -0800 (PST) Received: from mail-la0-x234.google.com (la-in-x0234.1e100.net [IPv6:2a00:1450:4010:c03::234]) by ietfa.amsl.com (Postfix) with ESMTP id E99D621F8780 for ; Mon, 28 Jan 2013 11:39:37 -0800 (PST) Received: by mail-la0-f52.google.com with SMTP id fs12so1043165lab.39 for ; Mon, 28 Jan 2013 11:39:36 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:x-received:in-reply-to:references:date:message-id :subject:from:to:cc:content-type; bh=xBrJew+MchoGKFz+O5SyakX6Wj8SUXzLh/7Kfo078gw=; b=bHNXQqWQvnUQuDzrAKUo+7Hd7ugXiwde9xcdYDEfOf2ZTuyIDHofZDf1f++TPmAdqv KuMeCevEqEpl69MuUUFyfnhGD2uv4bBDuEih6udEl0dDMW1TPjfCSQE53jMP9j91zMH4 uPe+tXMwNuJ/vOTJlb0zWWozjsdRS/+Ai9V/fWnXyNqFn96xr6aAGVUzay7fA8CE7PuC qBz6A/d+0Zd+ayYG16uLRt3b+2nw2ID+FQapkpDcw/dlkCG7vXlxKhygiFlaJwWD1C4R 2WfabkhamRLGtc7HQ83JpcGH0U2Jdbgpg9cNdN2qWrdgGdv8LuckcFvJciMSjGdOu2cC 5n5g== MIME-Version: 1.0 X-Received: by 10.152.127.202 with SMTP id ni10mr14303369lab.6.1359401976633; Mon, 28 Jan 2013 11:39:36 -0800 (PST) Received: by 10.112.34.114 with HTTP; Mon, 28 Jan 2013 11:39:36 -0800 (PST) In-Reply-To: References: <51069907.4030203@gmail.com> <5106A47B.7060802@gmail.com> <5106B3AF.7030105@gmail.com> <5106BB79.6090206@gmail.com> Date: Mon, 28 Jan 2013 11:39:36 -0800 Message-ID: From: Martin Thomson To: Nico Williams Content-Type: text/plain; charset=UTF-8 Cc: tools-discuss@ietf.org Subject: Re: [Tools-discuss] RFC comment system X-BeenThere: tools-discuss@ietf.org X-Mailman-Version: 2.1.12 Precedence: list List-Id: IETF Tools Discussion List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 28 Jan 2013 19:39:39 -0000 On 28 January 2013 10:04, Nico Williams wrote: > This can probably be helped by having a requirement that one have > posted some number of messages to IETF mailing lists in order to [...] That sounds like a terrible idea. When you want *less* spam, don't create incentives that favour *more*. From nico@cryptonector.com Mon Jan 28 11:45:03 2013 Return-Path: X-Original-To: tools-discuss@ietfa.amsl.com Delivered-To: tools-discuss@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id A992A21F8783 for ; Mon, 28 Jan 2013 11:45:03 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -3.96 X-Spam-Level: X-Spam-Status: No, score=-3.96 tagged_above=-999 required=5 tests=[AWL=-1.983, BAYES_00=-2.599, FM_FORGED_GMAIL=0.622] Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 5Kz-KR5hp22a for ; Mon, 28 Jan 2013 11:45:03 -0800 (PST) Received: from homiemail-a67.g.dreamhost.com (caiajhbdccac.dreamhost.com [208.97.132.202]) by ietfa.amsl.com (Postfix) with ESMTP id 098C421F8763 for ; Mon, 28 Jan 2013 11:45:03 -0800 (PST) Received: from homiemail-a67.g.dreamhost.com (localhost [127.0.0.1]) by homiemail-a67.g.dreamhost.com (Postfix) with ESMTP id B76AC27BC064 for ; Mon, 28 Jan 2013 11:45:02 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha1; c=relaxed; d=cryptonector.com; h= mime-version:in-reply-to:references:date:message-id:subject:from :to:cc:content-type; s=cryptonector.com; bh=6UyWTkziOmBHAzHALY3/ +HTeBnw=; b=c0/IDa7YRo00eyzN/WD0Ctx+Q6p6UzD9V7De2fy6gy/TAxfux8Il gzKxaBhkMEOi+uO9an7m37eGkSDKg4IlFQ6F5K3aioidy+0hlQrjqXhvqyO/YAI+ z8Avhegpa4VgDVyHFAwF5DNNomUQXUS/cs7zDKD4Atj++Dbpx3AYpBI= Received: from mail-wi0-f173.google.com (mail-wi0-f173.google.com [209.85.212.173]) (using TLSv1 with cipher RC4-SHA (128/128 bits)) (No client certificate requested) (Authenticated sender: nico@cryptonector.com) by homiemail-a67.g.dreamhost.com (Postfix) with ESMTPSA id 5F61927BC061 for ; Mon, 28 Jan 2013 11:45:02 -0800 (PST) Received: by mail-wi0-f173.google.com with SMTP id hn17so1765639wib.0 for ; Mon, 28 Jan 2013 11:45:01 -0800 (PST) MIME-Version: 1.0 X-Received: by 10.194.80.73 with SMTP id p9mr23579884wjx.4.1359402301173; Mon, 28 Jan 2013 11:45:01 -0800 (PST) Received: by 10.217.39.133 with HTTP; Mon, 28 Jan 2013 11:45:01 -0800 (PST) In-Reply-To: References: <51069907.4030203@gmail.com> <5106A47B.7060802@gmail.com> <5106B3AF.7030105@gmail.com> <5106BB79.6090206@gmail.com> Date: Mon, 28 Jan 2013 13:45:01 -0600 Message-ID: From: Nico Williams To: Martin Thomson Content-Type: text/plain; charset=UTF-8 Cc: tools-discuss@ietf.org Subject: Re: [Tools-discuss] RFC comment system X-BeenThere: tools-discuss@ietf.org X-Mailman-Version: 2.1.12 Precedence: list List-Id: IETF Tools Discussion List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 28 Jan 2013 19:45:03 -0000 On Mon, Jan 28, 2013 at 1:39 PM, Martin Thomson wrote: > On 28 January 2013 10:04, Nico Williams wrote: >> This can probably be helped by having a requirement that one have >> posted some number of messages to IETF mailing lists in order to > [...] > > That sounds like a terrible idea. When you want *less* spam, don't > create incentives that favour *more*. We already control spam on the lists. Therefore having been able to post N messages/month over the last 12 months seems like a good proxy for "not a spammer". From yaronf.ietf@gmail.com Mon Jan 28 12:07:38 2013 Return-Path: X-Original-To: tools-discuss@ietfa.amsl.com Delivered-To: tools-discuss@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 2682321F8689 for ; Mon, 28 Jan 2013 12:07:37 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -102.906 X-Spam-Level: X-Spam-Status: No, score=-102.906 tagged_above=-999 required=5 tests=[AWL=0.693, BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1, USER_IN_WHITELIST=-100] Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id ulXPdtie0-kf for ; Mon, 28 Jan 2013 12:07:34 -0800 (PST) Received: from mail-bk0-f51.google.com (mail-bk0-f51.google.com [209.85.214.51]) by ietfa.amsl.com (Postfix) with ESMTP id 37BE121F8634 for ; Mon, 28 Jan 2013 12:07:31 -0800 (PST) Received: by mail-bk0-f51.google.com with SMTP id ik5so1603606bkc.24 for ; Mon, 28 Jan 2013 12:07:29 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=x-received:message-id:date:from:user-agent:mime-version:to:cc :subject:references:in-reply-to:content-type :content-transfer-encoding; bh=jtvvgE+hfUjgxrA7EeUDzZXZ4j3UT5MW6drQhSW8thY=; b=qkFaHDUc8KGEU3bFI07J8FZmB567ItGQ1InLvVISgkynlSnv936Ah3kiMdJ+XLKYPz aAzKHo/l80SJiWuouEUR6gdXAZ6lBByxj0D4WmUYFeRQPbTtWWKKwTdmLqeBmB3qENZG qQZ/X3wtASd9l4szb7AELt6cBOnMjgbUMfVPce8qfYiQxLbKjBXDxu+H2xilwMD2h5dI Xu8yYipntJyqUJrCkUkAnMyE18Mo51X3sD1xvDz+im1oiPBQ7tYdQejHDFGRctHu76f1 RxulYf3TTbx0Pu7GAf5SPZiViq0dENyYnQy/J7sALVaZEgdX+AvPktqZ+OsW56d6R5Bv aYwg== X-Received: by 10.205.129.16 with SMTP id hg16mr1983642bkc.11.1359403649630; Mon, 28 Jan 2013 12:07:29 -0800 (PST) Received: from [10.0.0.5] (bzq-79-176-124-5.red.bezeqint.net. [79.176.124.5]) by mx.google.com with ESMTPS id hc16sm7428500bkc.2.2013.01.28.12.07.27 (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Mon, 28 Jan 2013 12:07:28 -0800 (PST) Message-ID: <5106DA7D.60804@gmail.com> Date: Mon, 28 Jan 2013 22:07:25 +0200 From: Yaron Sheffer User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:17.0) Gecko/20130106 Thunderbird/17.0.2 MIME-Version: 1.0 To: Nico Williams References: <51069907.4030203@gmail.com> <5106A47B.7060802@gmail.com> <5106B3AF.7030105@gmail.com> <5106BB79.6090206@gmail.com> In-Reply-To: Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit Cc: tools-discuss@ietf.org Subject: Re: [Tools-discuss] RFC comment system X-BeenThere: tools-discuss@ietf.org X-Mailman-Version: 2.1.12 Precedence: list List-Id: IETF Tools Discussion List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 28 Jan 2013 20:07:38 -0000 Most people who are implementing RFCs (or designing systems based on RFCs, or acquiring such systems) are not IETF insiders, and may never have posted to IETF lists. I think these are the folks we should tap for these comments, instead of the same old IETFers. If this is successful, I would expect at least some authors to subscribe to a feed of their own RFCs, in order to get feedback "from the field". Thanks, Yaron On 01/28/2013 08:04 PM, Nico Williams wrote: > On Mon, Jan 28, 2013 at 11:55 AM, Yaron Sheffer wrote: >> Just to clarify my (possibly naive) view on this: long term, this should be >> as unofficial as other "tools" activities, with no new processes imposed on >> authors or the secretariat (Mr. Bradner, someone just opened a ticket for >> RFC 2119, do you want to approve it?). > > Sure, but as with errata, someone will want to review some of these > things. Alternatively we should just not have any such tools hosted > by the IETF (and also really not by IETF participants; blogging is one > things, but hosting a potentially popular tool that the IETF chooses > not to to avoid maintenance burdens will... cause the same maintenance > burdens). > >> The only real maintenance activity that cannot be avoided - but may be >> somewhat automated - is dealing with spam. > > This can probably be helped by having a requirement that one have > posted some number of messages to IETF mailing lists in order to > register for the wiki. > > Nico > -- > From nico@cryptonector.com Mon Jan 28 12:14:16 2013 Return-Path: X-Original-To: tools-discuss@ietfa.amsl.com Delivered-To: tools-discuss@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 1AF3721F8A08 for ; Mon, 28 Jan 2013 12:14:16 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -3.588 X-Spam-Level: X-Spam-Status: No, score=-3.588 tagged_above=-999 required=5 tests=[AWL=-1.611, BAYES_00=-2.599, FM_FORGED_GMAIL=0.622] Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id hLapTvncyVkE for ; Mon, 28 Jan 2013 12:14:15 -0800 (PST) Received: from homiemail-a70.g.dreamhost.com (caiajhbdcbef.dreamhost.com [208.97.132.145]) by ietfa.amsl.com (Postfix) with ESMTP id BB74421F89E9 for ; Mon, 28 Jan 2013 12:14:14 -0800 (PST) Received: from homiemail-a70.g.dreamhost.com (localhost [127.0.0.1]) by homiemail-a70.g.dreamhost.com (Postfix) with ESMTP id 449D2768064 for ; Mon, 28 Jan 2013 12:14:09 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha1; c=relaxed; d=cryptonector.com; h= mime-version:in-reply-to:references:date:message-id:subject:from :to:cc:content-type; s=cryptonector.com; bh=dclnM4uGUOhyH0rebDMs P0Vl7sQ=; b=Q2W+f1YKeUYNwfOZGpDbPdzvMZjxs88WG3G7YOeWf4Xyxph3zqAg BtKVZYX1uZjrJ2f1i5R9/szAsmCnrwYWeP4ajhlz6KbXucPY8AYnjHi8Kg09RYML l/25NgBImP5butm5PO6JMcdBt0J5oNYvHr7JGvgG7mgdXMt1qohl6D8= Received: from mail-wg0-f42.google.com (mail-wg0-f42.google.com [74.125.82.42]) (using TLSv1 with cipher RC4-SHA (128/128 bits)) (No client certificate requested) (Authenticated sender: nico@cryptonector.com) by homiemail-a70.g.dreamhost.com (Postfix) with ESMTPSA id E2102768059 for ; Mon, 28 Jan 2013 12:14:08 -0800 (PST) Received: by mail-wg0-f42.google.com with SMTP id 12so1498046wgh.1 for ; Mon, 28 Jan 2013 12:14:07 -0800 (PST) MIME-Version: 1.0 X-Received: by 10.194.80.73 with SMTP id p9mr23691024wjx.4.1359404047496; Mon, 28 Jan 2013 12:14:07 -0800 (PST) Received: by 10.217.39.133 with HTTP; Mon, 28 Jan 2013 12:14:07 -0800 (PST) In-Reply-To: <5106DA7D.60804@gmail.com> References: <51069907.4030203@gmail.com> <5106A47B.7060802@gmail.com> <5106B3AF.7030105@gmail.com> <5106BB79.6090206@gmail.com> <5106DA7D.60804@gmail.com> Date: Mon, 28 Jan 2013 14:14:07 -0600 Message-ID: From: Nico Williams To: Yaron Sheffer Content-Type: text/plain; charset=UTF-8 Cc: tools-discuss@ietf.org Subject: Re: [Tools-discuss] RFC comment system X-BeenThere: tools-discuss@ietf.org X-Mailman-Version: 2.1.12 Precedence: list List-Id: IETF Tools Discussion List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 28 Jan 2013 20:14:16 -0000 On Mon, Jan 28, 2013 at 2:07 PM, Yaron Sheffer wrote: > Most people who are implementing RFCs (or designing systems based on RFCs, > or acquiring such systems) are not IETF insiders, and may never have posted > to IETF lists. I think these are the folks we should tap for these comments, > instead of the same old IETFers. Fair enough. We can probably have a system where edits are not accepted automatically but some established IETFer needs to review them. It can't always be RFC authors (they may not be around) or WG chairs (ditto) or past WG chairs (ditto). It can be ADs but they're overworked as it is. Therefore it'd have to be a community. The way it could be done is that wiki updates are sent to the relevant list for any given RFC (e.g., its [possibly concluded] WG's list). I'm sure we could make this work. I see a lot of value in this! Nico -- From brian.e.carpenter@gmail.com Thu Jan 31 04:47:02 2013 Return-Path: X-Original-To: tools-discuss@ietfa.amsl.com Delivered-To: tools-discuss@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id B8D2421F8622 for ; Thu, 31 Jan 2013 04:47:02 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -100.049 X-Spam-Level: X-Spam-Status: No, score=-100.049 tagged_above=-999 required=5 tests=[AWL=-1.128, BAYES_00=-2.599, FH_HOST_EQ_D_D_D_D=0.765, RCVD_ILLEGAL_IP=1.908, RCVD_IN_PBL=0.905, RDNS_DYNAMIC=0.1, USER_IN_WHITELIST=-100] Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id nOrfke8Q4Vtg for ; Thu, 31 Jan 2013 04:47:02 -0800 (PST) Received: from mail-wi0-x229.google.com (wi-in-x0229.1e100.net [IPv6:2a00:1450:400c:c05::229]) by ietfa.amsl.com (Postfix) with ESMTP id 0854421F85A2 for ; Thu, 31 Jan 2013 04:47:01 -0800 (PST) Received: by mail-wi0-f169.google.com with SMTP id hq12so519826wib.2 for ; Thu, 31 Jan 2013 04:47:01 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=x-received:message-id:date:from:organization:user-agent :mime-version:to:subject:content-type:content-transfer-encoding; bh=AbcrknlQG6MTkIgrYVQQL+Mu1ZYgIP3/AmPT5LBfmfQ=; b=RbPwGXXeAoerZ38vlnC7y6SKtK/2DL0vUTih/Agi+FIpCf4lEiLEcOptX6E3yjm1MI tPSs1YF+ysUd/3EgGND5p3MAs6j38w57uhmen18sCRCMK+rhKVV6SoR0E3X7Q2NAh+9c 767hLQXIMacs+/OEN+fguKh1mTEq32o4CU5e0U2pJSHtuZ19snvxRB8GqS1JyQhl7mrx ynVXO/Qi9M5fMnheg+6RLFj/bXMddx9t61ZVKnAaYJK8KCyiMFoEcUMlaPNWkbDXPeql krO0m6bcTHk6u68I+3ybxmkVq5vPJ48KjuCmIxucvb8nct7tXpMwzqqiTqgQ1Wlx7Dxf FgjA== X-Received: by 10.180.78.66 with SMTP id z2mr14917122wiw.23.1359636420810; Thu, 31 Jan 2013 04:47:00 -0800 (PST) Received: from [192.168.1.65] (host-2-102-217-85.as13285.net. [2.102.217.85]) by mx.google.com with ESMTPS id bz12sm9059818wib.5.2013.01.31.04.46.59 (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Thu, 31 Jan 2013 04:46:59 -0800 (PST) Message-ID: <510A67CE.40606@gmail.com> Date: Thu, 31 Jan 2013 12:47:10 +0000 From: Brian E Carpenter Organization: University of Auckland User-Agent: Thunderbird 2.0.0.6 (Windows/20070728) MIME-Version: 1.0 To: Tools Team Discussion Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Subject: [Tools-discuss] Querying a failure mode in I-D submission X-BeenThere: tools-discuss@ietf.org X-Mailman-Version: 2.1.12 Precedence: list List-Id: IETF Tools Discussion List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 31 Jan 2013 12:47:02 -0000 Hi, Is the following a possible bug in the I-D submission system? It's only speculation, but I think this has happened to me twice now. 1. I verify a new (non-WG, -00) draft via http://www.ietf.org/tools/idnits/ (with one warning, see below**). 2. Then I attempt to submit it via https://datatracker.ietf.org/idst/upload.cgi The system comes back with "Your draft has NOT been verified to meet IDNITS requirements. (View IDNITS Results)" and the nits results are completely blank (https://datatracker.ietf.org/submit/status/47888/#) Last time this happened I submitted a ticket without result, and when I tried the submission again a day later, it worked fine. This time, I will try again tomorrow... Is it possible that the manual idnits run is leaving behind some state that causes the idnits run during the upload to fail? ** The warning that I get is: == Couldn't figure out when the document was first submitted -- there may comments or warnings related to the use of a disclaimer for pre-RFC5378 work that could not be issued because of this. Please check the Legal Provisions document at http://trustee.ietf.org/license-info to determine if you need the pre-RFC5378 disclaimer. Regards Brian Carpenter