From nobody Wed Oct 1 02:21:17 2014 Return-Path: X-Original-To: tools-discuss@ietfa.amsl.com Delivered-To: tools-discuss@ietfa.amsl.com Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 9FE7B1ACD02 for ; Wed, 1 Oct 2014 02:21:15 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -101.9 X-Spam-Level: X-Spam-Status: No, score=-101.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, USER_IN_WHITELIST=-100] autolearn=ham Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id QwO7TRP7-Bue for ; Wed, 1 Oct 2014 02:21:12 -0700 (PDT) Received: from zinfandel.tools.ietf.org (zinfandel.tools.ietf.org [IPv6:2001:1890:123a::1:2a]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id E8D991ACCEA for ; Wed, 1 Oct 2014 02:21:11 -0700 (PDT) Received: from localhost ([::1]:48640 helo=tannat.netnod.se) by zinfandel.tools.ietf.org with esmtp (Exim 4.82_1-5b7a7c0-XX) (envelope-from ) id 1XZG5v-0008NM-4Q; Wed, 01 Oct 2014 02:21:11 -0700 Message-ID: <542BC785.7010400@levkowetz.com> Date: Wed, 01 Oct 2014 11:21:09 +0200 From: Henrik Levkowetz User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.9; rv:24.0) Gecko/20100101 Thunderbird/24.6.0 MIME-Version: 1.0 To: Yaron Sheffer , tools-discuss@ietf.org References: <542AD5A5.4030108@gmail.com> In-Reply-To: <542AD5A5.4030108@gmail.com> Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit X-SA-Exim-Connect-IP: ::1 X-SA-Exim-Rcpt-To: yaronf.ietf@gmail.com, tools-discuss@ietf.org, henrik-sent@levkowetz.com X-SA-Exim-Mail-From: henrik@levkowetz.com X-SA-Exim-Scanned: No (on zinfandel.tools.ietf.org); SAEximRunCond expanded to false Archived-At: http://mailarchive.ietf.org/arch/msg/tools-discuss/S9915QsM3mh7Gs6WansoMBfPW1Q Subject: Re: [Tools-discuss] Outdated I-D reference X-BeenThere: tools-discuss@ietf.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: IETF Tools Discussion List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 01 Oct 2014 09:21:15 -0000 Hi Yaron, On 2014-09-30 18:09 Yaron Sheffer said: > Hi, > > I am running xml2rfc 2.4.8 locally, on Ubuntu. When referencing my own > I-D.ietf-uta-tls-attacks, it insists on generating a ref to version -01 of the > draft, even though -04 is available (and appears on > http://xml2rfc.ietf.org/public/rfc/bibxml3/). The online xml2rfc tool works > fine. Any ideas? If you run xml2rfc while off-line, and it tries to update the reference info, it will make one attempt, but then delay the next attempt until 24 hours has passed, if I recall correctly. You can always clean out your cache, and re- run if you're online. The cache should be in ~/.cache/xml2rfc/. Best regards, Henrik From nobody Wed Oct 15 00:36:04 2014 Return-Path: X-Original-To: tools-discuss@ietfa.amsl.com Delivered-To: tools-discuss@ietfa.amsl.com Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id F2EB51A03AB for ; Wed, 15 Oct 2014 00:36:02 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -1.551 X-Spam-Level: X-Spam-Status: No, score=-1.551 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HELO_EQ_DE=0.35, SPF_HELO_PASS=-0.001] autolearn=no Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id b-C-5itwBGzV for ; Wed, 15 Oct 2014 00:36:02 -0700 (PDT) Received: from informatik.uni-bremen.de (mailhost.informatik.uni-bremen.de [IPv6:2001:638:708:30c9::12]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id C25B11A03A9 for ; Wed, 15 Oct 2014 00:36:01 -0700 (PDT) X-Virus-Scanned: amavisd-new at informatik.uni-bremen.de Received: from smtp-fb3.informatik.uni-bremen.de (smtp-fb3.informatik.uni-bremen.de [134.102.224.120]) by informatik.uni-bremen.de (8.14.5/8.14.5) with ESMTP id s9F7Zw9m022650; Wed, 15 Oct 2014 09:35:58 +0200 (CEST) Received: from [10.0.1.3] (reingewinn.informatik.uni-bremen.de [134.102.218.123]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (No client certificate requested) by smtp-fb3.informatik.uni-bremen.de (Postfix) with ESMTPSA id 98F2E2B5; Wed, 15 Oct 2014 09:35:58 +0200 (CEST) Content-Type: text/plain; charset=windows-1252 Mime-Version: 1.0 (Mac OS X Mail 7.3 \(1878.6\)) From: Carsten Bormann Date: Wed, 15 Oct 2014 09:35:56 +0200 X-Mao-Original-Outgoing-Id: 435051356.698922-9fd20cfa28e1e083df46544dce7dc079 Content-Transfer-Encoding: quoted-printable Message-Id: <63FD6018-C03B-473D-AD28-A06B0E532A6E@tzi.org> References: <4E1F6AAD24975D4BA5B16804296739439BB0F8CD@TK5EX14MBXC286.redmond.corp.microsoft.com> To: Tools Team Discussion X-Mailer: Apple Mail (2.1878.6) Archived-At: http://mailarchive.ietf.org/arch/msg/tools-discuss/vsoUPvLjjy7g2Dt7H50hUkK4i6M Subject: [Tools-discuss] Section references to referenced documents (Fwd: [apps-discuss] AppsDir reviews of draft-ietf-jose-json-web-signature-32) X-BeenThere: tools-discuss@ietf.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: IETF Tools Discussion List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 15 Oct 2014 07:36:03 -0000 =46rom a recent appsdir review and the response to that: Begin forwarded message: >> 4.1.1. & 4.1.2. The links to Section 4.1 and Section 5.1 of JWA are = incorrect. >> They link to JWE instead of JWA. >>=20 >> In 4.1.1. the link is: >> = https://tools.ietf.org/html/draft-ietf-jose-json-web-encryption-32#section= -4.1 >> ...but it should be: >> = https://tools.ietf.org/html/draft-ietf-jose-json-web-algorithms-33#section= -4.1 >>=20 >> In 4.1.2. the link is: >> = https://tools.ietf.org/html/draft-ietf-jose-json-web-encryption-32#section= -5.1 >> ...but it should be: >> = https://tools.ietf.org/html/draft-ietf-jose-json-web-algorithms-33#section= -5 >> (JWA doesn't seem to have an anchor for 5.1) >=20 > These link URLs are actually created by the IETF tools - not in the = draft itself. (You'll see "Html markup produced by rfcmarkup 1.109, = available fromhttps://tools.ietf.org/tools/rfcmarkup/" at the bottom of = the drafts.) I'm not sure who to file a bug on this with. I don=92t quite understand the comment, but it is clear that text like the initial contents of this registry are the values defined in Section 3.1 of the JSON Web Algorithms (JWA) [JWA] specification. is highlighted with a reference to Section 3.1 in the current document, = not in the document being referenced. I have no idea how to fix this = (unless we add significant natural language processing to the rfcmarkup = tool), so I=92m raising this for discussion first before creating a = tracker entry. (Editorially, I believe a reference with an uppercase =93Section=94 = should always be one to the current document; a reference to a section = in a different document should use lower case. But I have no idea how = wide-spread this convention is and whether this is the right thing to = trigger on.) Gr=FC=DFe, Carsten From nobody Thu Oct 16 03:56:34 2014 Return-Path: X-Original-To: tools-discuss@ietfa.amsl.com Delivered-To: tools-discuss@ietfa.amsl.com Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 0D9211AD02E for ; Thu, 16 Oct 2014 03:56:32 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -101.9 X-Spam-Level: X-Spam-Status: No, score=-101.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, USER_IN_WHITELIST=-100] autolearn=ham Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 6wnhQlE6qHXt for ; Thu, 16 Oct 2014 03:56:29 -0700 (PDT) Received: from zinfandel.tools.ietf.org (zinfandel.tools.ietf.org [IPv6:2001:1890:123a::1:2a]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 5398C1AD010 for ; Thu, 16 Oct 2014 03:56:08 -0700 (PDT) Received: from localhost ([::1]:33406 helo=tannat.netnod.se) by zinfandel.tools.ietf.org with esmtp (Exim 4.82_1-5b7a7c0-XX) (envelope-from ) id 1Xeij1-0004Qc-2A; Thu, 16 Oct 2014 03:56:07 -0700 Message-ID: <543FA445.2060704@levkowetz.com> Date: Thu, 16 Oct 2014 12:56:05 +0200 From: Henrik Levkowetz User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.9; rv:24.0) Gecko/20100101 Thunderbird/24.6.0 MIME-Version: 1.0 To: Carsten Bormann , Tools Team Discussion References: <4E1F6AAD24975D4BA5B16804296739439BB0F8CD@TK5EX14MBXC286.redmond.corp.microsoft.com> <63FD6018-C03B-473D-AD28-A06B0E532A6E@tzi.org> In-Reply-To: <63FD6018-C03B-473D-AD28-A06B0E532A6E@tzi.org> Content-Type: multipart/signed; micalg=pgp-sha256; protocol="application/pgp-signature"; boundary="TX0q2xUNwve17eOpwb5ePCW4vwgov7fSG" X-SA-Exim-Connect-IP: ::1 X-SA-Exim-Rcpt-To: cabo@tzi.org, tools-discuss@ietf.org, henrik-sent@levkowetz.com X-SA-Exim-Mail-From: henrik@levkowetz.com X-SA-Exim-Scanned: No (on zinfandel.tools.ietf.org); SAEximRunCond expanded to false Archived-At: http://mailarchive.ietf.org/arch/msg/tools-discuss/9aXn3IaMvC3l1_wPkHnH8M9l4E4 Subject: Re: [Tools-discuss] Section references to referenced documents (Fwd: [apps-discuss] AppsDir reviews of draft-ietf-jose-json-web-signature-32) X-BeenThere: tools-discuss@ietf.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: IETF Tools Discussion List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 16 Oct 2014 10:56:32 -0000 This is an OpenPGP/MIME signed message (RFC 4880 and 3156) --TX0q2xUNwve17eOpwb5ePCW4vwgov7fSG Content-Type: text/plain; charset=windows-1252 Content-Transfer-Encoding: quoted-printable Hi Carsten, On 2014-10-15 09:35 Carsten Bormann said: > From a recent appsdir review and the response to that: >=20 > Begin forwarded message: >=20 >>> 4.1.1. & 4.1.2. The links to Section 4.1 and Section 5.1 of JWA are i= ncorrect. >>> They link to JWE instead of JWA. >>> >>> In 4.1.1. the link is: >>> https://tools.ietf.org/html/draft-ietf-jose-json-web-encryption-32#se= ction-4.1 >>> ...but it should be: >>> https://tools.ietf.org/html/draft-ietf-jose-json-web-algorithms-33#se= ction-4.1 >>> >>> In 4.1.2. the link is: >>> https://tools.ietf.org/html/draft-ietf-jose-json-web-encryption-32#se= ction-5.1 >>> ...but it should be: >>> https://tools.ietf.org/html/draft-ietf-jose-json-web-algorithms-33#se= ction-5 >>> (JWA doesn't seem to have an anchor for 5.1) >> >> These link URLs are actually created by the IETF tools - not in the >> draft itself. (You'll see "Html markup produced by rfcmarkup >> 1.109, available fromhttps://tools.ietf.org/tools/rfcmarkup/" at >> the bottom of the drafts.) I'm not sure who to file a bug on this >> with. >=20 > I don=92t quite understand the comment, but it is clear that text like >=20 > the initial contents of this registry are the values defined in > Section 3.1 of the JSON Web Algorithms (JWA) [JWA] specification. >=20 > is highlighted with a reference to Section 3.1 in the current > document, not in the document being referenced. I have no idea how > to fix this (unless we add significant natural language processing to > the rfcmarkup tool), so I=92m raising this for discussion first before > creating a tracker entry. Right. rfcmarkup handles a number of cases where Section x.y refers to a= nother RFC or draft, but only when the RFC or draft is mentioned as 'rfc NNNN' o= r 'draft-....', and occurs adjacent to the 'Section x.y' words. I can see = that it could be possible to cache the names of all drafts and RFCs, and try t= o match text adjacent to 'Section x.y' to not only RFC... and draft-... but= also to this list of known titles, but some work is needed to make that h= appen. > (Editorially, I believe a reference with an uppercase =93Section=94 > should always be one to the current document; a reference to a > section in a different document should use lower case. But I have no > idea how wide-spread this convention is and whether this is the right > thing to trigger on.) I wasn't aware of this convention, and with the wild variations in text produced by humans, I don't think one can rely on that in this setting. Best regards, Henrik --TX0q2xUNwve17eOpwb5ePCW4vwgov7fSG Content-Type: application/pgp-signature; name="signature.asc" Content-Description: OpenPGP digital signature Content-Disposition: attachment; filename="signature.asc" -----BEGIN PGP SIGNATURE----- iQIcBAEBCAAGBQJUP6RFAAoJEE6bV0uPuxcazEQQAMzlM89od415yB+78QnjsM27 +pu/qnQ35I0vJWkGEFE7a9RwwqMuAeH3VcXfXEcPCkraPKmdXaub5mhm+CuDZrwt Y0ICrzQiXUHtHsqN5VZEstEPXMmA+IglYlSvGWcVhb4Q79flC6V1SPm7vvQmTYf2 ZAovhv24X1s0Lnr0md0j4YAFjK4fk51fbJK0b+QDZVlc52K7E6i0Q85ETJHByf6o E6oubttPOpJC5RR/Gc0Pt642Rdc1AsaQjaCQ3/iLJq3RMsTRzyP6zP5dntXbF7N5 WnE8ZVAgOsiaHDWtVUe/mFKLQo2Ek8uxuGo7HgcVqkv8T6a96nrokzM2Fq7a5WZJ J0UnjUS7Hg+u/ADwz4j9TlYoRKjbxRkF5rAZqo6C0WBXUpPJQUA3qXJWHdyffNfd PQD+0mZ2W2e+mOApZySVJiSxTSWyIfB/EiPafA84CtpOqlT7Gy0jLJndH9Kkadw5 on8Jb08vOl9QPC9vovobG6C1xNSIw9oTSfJk+E8R8jlgwondIofprwWK4XQd2UqS M26RCMINEdBNXsA+GjbzKVf+hqP8619So1Luvaxcw4xibgKMvtZtldS2FFWwqr+t a/XOid9jzHHqJ74CCY6Os90MYV8nrUra1XM9t4XKrEh1P/P4JYKlZXOQHtN5Z5F/ BadsPM+U5BM0BYjkl83/ =sFKq -----END PGP SIGNATURE----- --TX0q2xUNwve17eOpwb5ePCW4vwgov7fSG-- From nobody Thu Oct 16 05:00:52 2014 Return-Path: X-Original-To: tools-discuss@ietfa.amsl.com Delivered-To: tools-discuss@ietfa.amsl.com Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 648D71A1AE5 for ; Thu, 16 Oct 2014 05:00:51 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -1.55 X-Spam-Level: X-Spam-Status: No, score=-1.55 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HELO_EQ_DE=0.35] autolearn=no Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id VmKf5PFBDot5 for ; Thu, 16 Oct 2014 05:00:49 -0700 (PDT) Received: from mailhost.informatik.uni-bremen.de (mailhost.informatik.uni-bremen.de [IPv6:2001:638:708:30c9::12]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 414D71A1A69 for ; Thu, 16 Oct 2014 05:00:49 -0700 (PDT) X-Virus-Scanned: amavisd-new at informatik.uni-bremen.de Received: from smtp-fb3.informatik.uni-bremen.de (smtp-fb3.informatik.uni-bremen.de [134.102.224.120]) by mailhost.informatik.uni-bremen.de (8.14.5/8.14.5) with ESMTP id s9GC0jE9025802; Thu, 16 Oct 2014 14:00:45 +0200 (CEST) Received: from [192.168.217.145] (p5489167A.dip0.t-ipconnect.de [84.137.22.122]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (No client certificate requested) by smtp-fb3.informatik.uni-bremen.de (Postfix) with ESMTPSA id BE4E1FE4; Thu, 16 Oct 2014 14:00:44 +0200 (CEST) Content-Type: text/plain; charset=windows-1252 Mime-Version: 1.0 (Mac OS X Mail 7.3 \(1878.6\)) From: Carsten Bormann In-Reply-To: <543FA445.2060704@levkowetz.com> Date: Thu, 16 Oct 2014 14:00:43 +0200 X-Mao-Original-Outgoing-Id: 435153642.919846-070d219b9e8ad778e50f0db0a5215676 Content-Transfer-Encoding: quoted-printable Message-Id: References: <4E1F6AAD24975D4BA5B16804296739439BB0F8CD@TK5EX14MBXC286.redmond.corp.microsoft.com> <63FD6018-C03B-473D-AD28-A06B0E532A6E@tzi.org> <543FA445.2060704@levkowetz.com> To: Henrik Levkowetz X-Mailer: Apple Mail (2.1878.6) Archived-At: http://mailarchive.ietf.org/arch/msg/tools-discuss/OP_T6y1LWjL7UvRcProDACPJ2mw Cc: Tools Team Discussion Subject: Re: [Tools-discuss] Section references to referenced documents (Fwd: [apps-discuss] AppsDir reviews of draft-ietf-jose-json-web-signature-32) X-BeenThere: tools-discuss@ietf.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: IETF Tools Discussion List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 16 Oct 2014 12:00:51 -0000 On 16 Oct 2014, at 12:56, Henrik Levkowetz wrote: >> (Editorially, I believe a reference with an uppercase =93Section=94 >> should always be one to the current document; a reference to a >> section in a different document should use lower case. But I have no >> idea how wide-spread this convention is and whether this is the right >> thing to trigger on.) >=20 > I wasn't aware of this convention, and with the wild variations in = text > produced by humans, I don't think one can rely on that in this = setting. Indeed, and a co-author just pointed me to: Referring to specific sections within another document This is mostly left to author preference. However, [=85] followed by examples using upper case =93Section=94 in an external = reference: http://www.rfc-editor.org/rfc-style-guide/part2.html (CMOS, which otherwise is generally the source of RFC style, actually = appears to always prefer lower case for references to parts of = documents: = http://www.chicagomanualofstyle.org/qanda/data/faq/topics/Capitalization.h= tml?page=3D1 at the end.) So none of this helps for the heuristics. Gr=FC=DFe, Carsten PS.: historically, the widespread convention to capitalize internal = references was boosted by the use of automation; many notations for = internal references generate snippets such as =93Section 3.6=94 from the = reference but did not have a way to indicate whether the context was = in-sentence (lower case in CMOS) or sentence-start (upper case in = English); that was of course irrelevant for external references. For XML2RFC, one would have to use and = manually prefix that with =93section=94 to get CMOS style for an = internal reference. From nobody Mon Oct 20 06:42:45 2014 Return-Path: X-Original-To: tools-discuss@ietfa.amsl.com Delivered-To: tools-discuss@ietfa.amsl.com Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id E31DC1A877C for ; Mon, 20 Oct 2014 06:42:34 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: 0.098 X-Spam-Level: X-Spam-Status: No, score=0.098 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, MIME_NO_TEXT=1.999, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01, T_TVD_MIME_NO_HEADERS=0.01] autolearn=no Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id xEZffHb2a3oC for ; Mon, 20 Oct 2014 06:42:33 -0700 (PDT) Received: from tuna.sandelman.ca (tuna.sandelman.ca [209.87.249.19]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id D761D1A8795 for ; Mon, 20 Oct 2014 06:41:17 -0700 (PDT) Received: from sandelman.ca (obiwan.sandelman.ca [209.87.249.21]) by tuna.sandelman.ca (Postfix) with ESMTP id 5DF9920012 for ; Mon, 20 Oct 2014 09:42:02 -0400 (EDT) Received: by sandelman.ca (Postfix, from userid 179) id 1F82363A84; Mon, 20 Oct 2014 09:41:15 -0400 (EDT) Received: from sandelman.ca (localhost [127.0.0.1]) by sandelman.ca (Postfix) with ESMTP id 0CCA763A82 for ; Mon, 20 Oct 2014 09:41:15 -0400 (EDT) From: Michael Richardson To: tools-discuss@ietf.org X-Attribution: mcr X-Mailer: MH-E 8.2; nmh 1.3-dev; GNU Emacs 23.4.1 X-Face: $\n1pF)h^`}$H>Hk{L"x@)JS7<%Az}5RyS@k9X%29-lHB$Ti.V>2bi.~ehC0; <'$9xN5Ub# z!G,p`nR&p7Fz@^UXIn156S8.~^@MJ*mMsD7=QFeq%AL4m Sender: mcr@sandelman.ca Archived-At: http://mailarchive.ietf.org/arch/msg/tools-discuss/aX9LKNFeFl1rfbWjh7MW70LII6U Subject: [Tools-discuss] datatracker links to other formats X-BeenThere: tools-discuss@ietf.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: IETF Tools Discussion List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 20 Oct 2014 13:42:35 -0000 --=-=-= The datatracker has links to other versions: Other versions: plain text, xml, pdf, html which links to (for instance): http://www.ietf.org/id/draft-irtf-nmrg-an-gap-analysis-02.txt http://www.ietf.org/id/draft-irtf-nmrg-an-gap-analysis-02.xml http://tools.ietf.org/pdf/draft-irtf-nmrg-an-gap-analysis-02.pdf http://tools.ietf.org/html/draft-irtf-nmrg-an-gap-analysis-02 The last link goes to the 
 wrapped .txt version from tools.ietf.org,
which yes, has a link to the HTML formatted xml2rfc version on it.

I'm wondering if there is a reason, or simply history, why the "html"
version doesn't go to the HTML version directly?

I'm also wondering if there is a reason why the www.ietf.org URL
is used for plain/xml rather than the tools version.

I guess I think about all of this partly from the point of view
of web and browser caches, but also from the point of view that I'm still
irked that it's not all URNs, and that the closest copy is really on my local
disk...

I also wonder if there is some reason, given the presence of the "show me the
whole thing" cookie setting for the datatracker, why that doesn't result in
a 302 to the ?includes_text=1 URL.  The reason this matters is because I
tend to pass that URL to my tablet offline reader (getpocket), although I think
I'll be using the tools.ietf.org HTML copy in future.  (Sadly, pocket still
can't display cached .txt URLs properly.)

--
Michael Richardson , Sandelman Software Works
 -= IPv6 IoT consulting =-




--=-=-=
Content-Type: application/pgp-signature

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.12 (GNU/Linux)

iQEVAwUBVEUQ+oCLcPvd0N1lAQKNywgAt0yWUtYK5v2lz41noXjC6hbpZHDLR2QA
eZO2JC9ymyyNZPe/f8GILDWX+56cv0PVjjeUaGOkCTXpjA9uRK2tT19xPwsQQcQ3
b9VfIisnavYQLPpgsgfwD+RSEbfAU+bpYUVE6fjd3O+saK+D/J9L2oOjC8DHw75Z
J/U/XAhJw5aUWoE+hM38Ler5tEKDOTMomF1Sil50PPUow2aJl5dQFXhlFgwaqqM0
uKHcmOAavER86opvYzW1dnHjVpA+7QvnwwNnbBbQKgRh3GezUl9ZcUi7L3e4EBWz
CRjDp5fLS2WPv70WXyfyK7gKyZPSvZLSt/HGPXcIbY3902sXhgxXTQ==
=LQ2u
-----END PGP SIGNATURE-----
--=-=-=--


From nobody Mon Oct 20 07:20:58 2014
Return-Path: 
X-Original-To: tools-discuss@ietfa.amsl.com
Delivered-To: tools-discuss@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 40FA11A9168 for ; Mon, 20 Oct 2014 07:20:54 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.5
X-Spam-Level: 
X-Spam-Status: No, score=-0.5 tagged_above=-999 required=5 tests=[BAYES_05=-0.5, FREEMAIL_FROM=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id In4uxB4hVA96 for ; Mon, 20 Oct 2014 07:20:47 -0700 (PDT)
Received: from mout.gmx.net (mout.gmx.net [212.227.15.19]) (using TLSv1.2 with cipher DHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 83C5D1A8A4A for ; Mon, 20 Oct 2014 07:05:30 -0700 (PDT)
Received: from [192.168.1.26] ([217.91.35.233]) by mail.gmx.com (mrgmx002) with ESMTPSA (Nemesis) id 0Lhwgc-1YTJi93Dhi-00nB4C; Mon, 20 Oct 2014 16:05:27 +0200
Message-ID: <544516A2.70802@gmx.de>
Date: Mon, 20 Oct 2014 16:05:22 +0200
From: Julian Reschke 
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:31.0) Gecko/20100101 Thunderbird/31.2.0
MIME-Version: 1.0
To: Michael Richardson , tools-discuss@ietf.org
References: <10176.1413812475@sandelman.ca>
In-Reply-To: <10176.1413812475@sandelman.ca>
Content-Type: text/plain; charset=windows-1252; format=flowed
Content-Transfer-Encoding: 7bit
X-Provags-ID: V03:K0:KV3qWKzbR5KZ5wlSFIBUch5ZynPMtvdPlUzJ2FG69HCi7aDszZN QKHscj007jrKLIUWVV+uTPZXrNJDq6VYFJwaOCHBVoQeWkHZGWcAM66rlc1CWj17QvyO3gG K02xlEoL7GpBB/YUtgFioZnGfhYgxzl8w7/FkK9cOcGasuIAiLpTGtDH2kruoMfF4FqS33x Q8cwzvq0uEqtv4C7Df8mQ==
X-UI-Out-Filterresults: notjunk:1;
Archived-At: http://mailarchive.ietf.org/arch/msg/tools-discuss/9N5nI3uA9x1ktcRiaqznzj9Et5o
Subject: Re: [Tools-discuss] datatracker links to other formats
X-BeenThere: tools-discuss@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF Tools Discussion 
List-Unsubscribe: , 
List-Archive: 
List-Post: 
List-Help: 
List-Subscribe: , 
X-List-Received-Date: Mon, 20 Oct 2014 14:20:54 -0000

On 2014-10-20 15:41, Michael Richardson wrote:
>
> The datatracker has links to other versions:
>    Other versions:	plain text, xml, pdf, html
>
> which links to (for instance):
> http://www.ietf.org/id/draft-irtf-nmrg-an-gap-analysis-02.txt
> http://www.ietf.org/id/draft-irtf-nmrg-an-gap-analysis-02.xml
> http://tools.ietf.org/pdf/draft-irtf-nmrg-an-gap-analysis-02.pdf
> http://tools.ietf.org/html/draft-irtf-nmrg-an-gap-analysis-02
>
> The last link goes to the 
 wrapped .txt version from tools.ietf.org,
> which yes, has a link to the HTML formatted xml2rfc version on it.

It *might* be thexml2rfc formatted version.

> I'm wondering if there is a reason, or simply history, why the "html"
> version doesn't go to the HTML version directly?

My guess is that the data tracker allows uploading HTML, but what that 
file contains is under the control of who did the upload, and might not 
have any relation to the actual txt. (which, thiking of it, is true for 
the xml as well).

The right fix would be to change the upload tool to treat the XML as 
first class, and to generate TXT and HTML from it.

> ...

Best regards, Julian


From nobody Tue Oct 28 07:18:16 2014
Return-Path: 
X-Original-To: tools-discuss@ietfa.amsl.com
Delivered-To: tools-discuss@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 114811A890A; Tue, 28 Oct 2014 07:17:54 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.098
X-Spam-Level: 
X-Spam-Status: No, score=0.098 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, MIME_NO_TEXT=1.999, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01, T_TVD_MIME_NO_HEADERS=0.01] autolearn=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id b0-Zk4Nx_O-3; Tue, 28 Oct 2014 07:17:52 -0700 (PDT)
Received: from tuna.sandelman.ca (tuna.sandelman.ca [209.87.249.19]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 337AD1A890C; Tue, 28 Oct 2014 07:17:51 -0700 (PDT)
Received: from sandelman.ca (obiwan.sandelman.ca [IPv6:2607:f0b0:f:2::247]) by tuna.sandelman.ca (Postfix) with ESMTP id 79EED20028; Tue, 28 Oct 2014 10:19:05 -0400 (EDT)
Received: by sandelman.ca (Postfix, from userid 179) id 467BA63A84; Tue, 28 Oct 2014 10:17:50 -0400 (EDT)
Received: from sandelman.ca (localhost [127.0.0.1]) by sandelman.ca (Postfix) with ESMTP id 26F7A63A21; Tue, 28 Oct 2014 10:17:50 -0400 (EDT)
From: Michael Richardson 
To: Glen via 
X-Attribution: mcr
X-Mailer: MH-E 8.2; nmh 1.3-dev; GNU Emacs 23.4.1
X-Face: $\n1pF)h^`}$H>Hk{L"x@)JS7<%Az}5RyS@k9X%29-lHB$Ti.V>2bi.~ehC0; <'$9xN5Ub# z!G,p`nR&p7Fz@^UXIn156S8.~^@MJ*mMsD7=QFeq%AL4m
Sender: mcr@sandelman.ca
Archived-At: http://mailarchive.ietf.org/arch/msg/tools-discuss/5vWZGL3rBzKRseB90hkGarnSB3M
Cc: tools-discuss 
Subject: [Tools-discuss] google thinks etherpad is phising
X-BeenThere: tools-discuss@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF Tools Discussion 
List-Unsubscribe: , 
List-Archive: 
List-Post: 
List-Help: 
List-Subscribe: , 
X-List-Received-Date: Tue, 28 Oct 2014 14:17:54 -0000

--=-=-=


Several people (nomcom call yesterday, 6tisch security team this morning)
get this in the past day from etherpad.tools.ietf.org:
        http://www.sandelman.ca/tmp/mcrcapture/6969.2014-10-28/capture1.png

specifically, a warning that the site is a phising site.

I expect that it's a false positive, but in order to get the details, you
have to connect to the Google web site manager portal to find out.

--
Michael Richardson , Sandelman Software Works
 -= IPv6 IoT consulting =-




--=-=-=
Content-Type: application/pgp-signature

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.12 (GNU/Linux)

iQEVAwUBVE+ljYCLcPvd0N1lAQKjRAgAwHIT53bbqQ3nytbT/ZSla7Yy41ZEO9n9
egd5G8pxLGpBav98lXbtVjq4CPNTlFE4CDuH5KUnOflor7v1OjTPeyIObH8qxbeK
j75N57ezEhrEsNx6jTDH5mSIDueZlffnxWsTgyUv/PgS9vWTOjQAcP8yLENmzlHg
vm8u+eBeqVZnIdJrMNsiDaX81HjdgX8asxDYuc5fASNbO+2987E37JgWb0OF9At5
0gBeTZElpeNDVXM+qSiasv+pFf6IeVhKVWzQqHYWOPApL+o0NxqZAn7ltIF9Sb5r
xbpZsn9hYxfYxaG8pIZ3U3FCzxPIVIKKZtSi8VPkvxOfBPKkRUM4Vw==
=9jxW
-----END PGP SIGNATURE-----
--=-=-=--


From nobody Tue Oct 28 08:36:13 2014
Return-Path: 
X-Original-To: tools-discuss@ietfa.amsl.com
Delivered-To: tools-discuss@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id D773E1A8AA8 for ; Tue, 28 Oct 2014 08:36:11 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.902
X-Spam-Level: 
X-Spam-Status: No, score=-1.902 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_NONE=-0.0001, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id BO-RgXfVDLqH for ; Tue, 28 Oct 2014 08:36:10 -0700 (PDT)
Received: from na01-by2-obe.outbound.protection.outlook.com (mail-by2on0146.outbound.protection.outlook.com [207.46.100.146]) (using TLSv1 with cipher ECDHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 510C21A8AE5 for ; Tue, 28 Oct 2014 08:36:10 -0700 (PDT)
Received: from BY2PR05MB079.namprd05.prod.outlook.com (10.242.38.16) by BY2PR05MB080.namprd05.prod.outlook.com (10.242.38.17) with Microsoft SMTP Server (TLS) id 15.1.6.9; Tue, 28 Oct 2014 15:36:08 +0000
Received: from BY2PR05MB079.namprd05.prod.outlook.com ([169.254.8.16]) by BY2PR05MB079.namprd05.prod.outlook.com ([169.254.8.16]) with mapi id 15.01.0006.000; Tue, 28 Oct 2014 15:36:08 +0000
From: "Jeffrey (Zhaohui) Zhang" 
To: "tools-discuss@ietf.org" 
Thread-Topic: reply button on ietf mail archive
Thread-Index: Ac/yLjD+4m4y83fSS7izZwQZYHufGA==
Date: Tue, 28 Oct 2014 15:36:07 +0000
Message-ID: 
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-ms-exchange-transport-fromentityheader: Hosted
x-originating-ip: [66.129.241.12]
x-microsoft-antispam: BCL:0;PCL:0;RULEID:;SRVR:BY2PR05MB080;
x-forefront-prvs: 0378F1E47A
x-forefront-antispam-report: SFV:NSPM; SFS:(10019020)(6009001)(189002)(199003)(229853001)(64706001)(31966008)(107046002)(2351001)(99286002)(101416001)(20776003)(46102003)(106356001)(21056001)(105586002)(76576001)(33646002)(4396001)(77096002)(110136001)(107886001)(66066001)(76482002)(87936001)(85306004)(2656002)(108616004)(54356999)(86362001)(50986999)(92566001)(95666004)(80022003)(122556002)(85852003)(97736003)(40100003)(74316001)(120916001)(24736002); DIR:OUT; SFP:1102; SCL:1; SRVR:BY2PR05MB080; H:BY2PR05MB079.namprd05.prod.outlook.com; FPR:; MLV:sfv; PTR:InfoNoRecords; MX:1; A:1; LANG:en; 
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-OriginatorOrg: juniper.net
Archived-At: http://mailarchive.ietf.org/arch/msg/tools-discuss/d-3DBbcIhvbeClXecOs2W6sApK4
Subject: [Tools-discuss] reply button on ietf mail archive
X-BeenThere: tools-discuss@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF Tools Discussion 
List-Unsubscribe: , 
List-Archive: 
List-Post: 
List-Help: 
List-Subscribe: , 
X-List-Received-Date: Tue, 28 Oct 2014 15:36:12 -0000

Hi,

For each archived message, could there be a button so that one could "reply=
" to a posted message? I don't keep all mailing list messages, and sometime=
s I need to go back to an archived one and reply to it. Currently there is =
no convenient way to do it.

I suppose this is not an uncommon situation people may run into. How do you=
 deal with it?

Thanks.
Jeffrey


From nobody Tue Oct 28 09:27:06 2014
Return-Path: 
X-Original-To: tools-discuss@ietfa.amsl.com
Delivered-To: tools-discuss@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 1778E1A86F4; Tue, 28 Oct 2014 09:26:56 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -101.9
X-Spam-Level: 
X-Spam-Status: No, score=-101.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, USER_IN_WHITELIST=-100] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 0soIoDWxzxnz; Tue, 28 Oct 2014 09:26:53 -0700 (PDT)
Received: from zinfandel.tools.ietf.org (zinfandel.tools.ietf.org [IPv6:2001:1890:123a::1:2a]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 7F4C51A8F3C; Tue, 28 Oct 2014 09:25:33 -0700 (PDT)
Received: from localhost ([::1]:51130 helo=tannat.netnod.se) by zinfandel.tools.ietf.org with esmtp (Exim 4.82_1-5b7a7c0-XX) (envelope-from ) id 1Xj9aP-00065X-6i; Tue, 28 Oct 2014 09:25:33 -0700
Message-ID: <544FC37B.8010809@levkowetz.com>
Date: Tue, 28 Oct 2014 17:25:31 +0100
From: Henrik Levkowetz 
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.9; rv:24.0) Gecko/20100101 Thunderbird/24.6.0
MIME-Version: 1.0
To: Michael Richardson ,  Glen via 
References: <26675.1414505870@sandelman.ca>
In-Reply-To: <26675.1414505870@sandelman.ca>
Content-Type: multipart/signed; micalg=pgp-sha256; protocol="application/pgp-signature"; boundary="FsC8Svr5FgM8ac8u7q86QW70FCDeNelve"
X-SA-Exim-Connect-IP: ::1
X-SA-Exim-Rcpt-To: mcr+ietf@sandelman.ca, ietf-action@ietf.org, tools-discuss@ietf.org, henrik-sent@levkowetz.com
X-SA-Exim-Mail-From: henrik@levkowetz.com
X-SA-Exim-Scanned: No (on zinfandel.tools.ietf.org); SAEximRunCond expanded to false
Archived-At: http://mailarchive.ietf.org/arch/msg/tools-discuss/H5SZ8d7jEmMlFTe3oxrv8dWDE4g
Cc: tools-discuss 
Subject: Re: [Tools-discuss] google thinks etherpad is phising
X-BeenThere: tools-discuss@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF Tools Discussion 
List-Unsubscribe: , 
List-Archive: 
List-Post: 
List-Help: 
List-Subscribe: , 
X-List-Received-Date: Tue, 28 Oct 2014 16:26:56 -0000

This is an OpenPGP/MIME signed message (RFC 4880 and 3156)
--FsC8Svr5FgM8ac8u7q86QW70FCDeNelve
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

Hi Michael,

On 2014-10-28 15:17 Michael Richardson said:
>=20
> Several people (nomcom call yesterday, 6tisch security team this mornin=
g)
> get this in the past day from etherpad.tools.ietf.org:
>         http://www.sandelman.ca/tmp/mcrcapture/6969.2014-10-28/capture1=
=2Epng
>=20
> specifically, a warning that the site is a phising site.
>=20
> I expect that it's a false positive, but in order to get the details, y=
ou
> have to connect to the Google web site manager portal to find out.

The portal shows no current warnings for ethernet.tools.ietf.org; I just
checked.  Furthermore, I don't get this warning when I open a test docume=
nt
in etherpad; but I do get it for the link visible in your screenshot.

In the webmaster tools for etherpad.tools.ietf.org, under security issues=
,
they mention this (see the second paragraph):

  Security Issues

  Currently, we haven't detected any security issues with your site's con=
tent.
  If you want to learn more about security issues and how they could affe=
ct
  your site, review our resources for hacked sites.

  However, if you see a malware warning in the browser when navigating to=
 your
  site, it's likely that your site is referencing code or content from an=
other
  domain that has malware. Read up on cross-site malware and learn how to=
 address
  it.=20

Could it be that there are links in the xml content of the etherpads whic=
h
google find suspicious?  Or something else related to the content being
an xml document under guise of a html page?


Best regards,

	Henrik




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

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

iQIcBAEBCAAGBQJUT8N7AAoJEE6bV0uPuxcai5AQAMMNxzNDds50PWv+X+jjL4ph
GQ6qV4qhbbrPzu4YWqNZCBYe5vRdv1Ub956hRNfxfLteLtpWtQA7l0odZbImMaOW
+M+PTpQdfP/fFikgtZ7WVSJdmYM2/WLsm+81DIFLlcqZrMh7lud5WQ40BngnPiPs
2LKXYYekCfjQXh0tsa3cqfXdk8bWZ4UJ82+3AOkOWXtZO2B9Q4d0aHpDUbpS43Gf
rBQ+5wS6ZkLFLPJjhGMtBulMJ/4k0LimabfvYm8ESaQkEeAE0z2WYW+IILNW2pH5
YsYmkPkMsTVKGE0oUz/1kIN823LNBDEHl3xFPnNujusgXY7cXYlB7RN5M824nny7
/SQ9zF4a+kHr7DAdaXE4gbu7Q6x8+FuL99FcikoUjP1BXMzZo7LVX+L/3v7xE30p
M07xHxBvrzZb/hwoecaJu09Lph1NLWAZ3n7u0gjtC56MACg3dD5VVhu7SQrJNFtb
84EZpeo1ByX5Q60jsLsL7a/wiPVV3ogFEQrK5i3xq6XqTMs8vt1Tvx1xQ1DebFH7
91BecOB1sAi/szl8TaqgT7bFx00PfbUaL4gFxbmmu0UTmcndCD1i6ccbpaZT1u3d
a74Fxz0vUGO32lD41C3FzzUh3T1BQeDh4BUPIbZR7TViU7K99aHLHCmRRyvLCkQw
ThAZ1Y7ofO5COxYdQirf
=Jjv/
-----END PGP SIGNATURE-----

--FsC8Svr5FgM8ac8u7q86QW70FCDeNelve--


From nobody Tue Oct 28 09:46:28 2014
Return-Path: 
X-Original-To: tools-discuss@ietfa.amsl.com
Delivered-To: tools-discuss@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 65DC31A8F3A for ; Tue, 28 Oct 2014 09:46:27 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.91
X-Spam-Level: 
X-Spam-Status: No, score=-1.91 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, T_RP_MATCHES_RCVD=-0.01] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id AXZ2BfMXsfPk for ; Tue, 28 Oct 2014 09:46:21 -0700 (PDT)
Received: from nostrum.com (raven-v6.nostrum.com [IPv6:2001:470:d:1130::1]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 689FD1A906A for ; Tue, 28 Oct 2014 09:39:39 -0700 (PDT)
Received: from Orochi.local (99-152-145-110.lightspeed.dllstx.sbcglobal.net [99.152.145.110]) (authenticated bits=0) by nostrum.com (8.14.9/8.14.7) with ESMTP id s9SGdbkn046960 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Tue, 28 Oct 2014 11:39:38 -0500 (CDT) (envelope-from adam@nostrum.com)
X-Authentication-Warning: raven.nostrum.com: Host 99-152-145-110.lightspeed.dllstx.sbcglobal.net [99.152.145.110] claimed to be Orochi.local
Message-ID: <544FC6C9.2040503@nostrum.com>
Date: Tue, 28 Oct 2014 11:39:37 -0500
From: Adam Roach 
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.8; rv:31.0) Gecko/20100101 Thunderbird/31.2.0
MIME-Version: 1.0
To: "Jeffrey (Zhaohui) Zhang" , "tools-discuss@ietf.org" 
References: 
In-Reply-To: 
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Transfer-Encoding: 7bit
Archived-At: http://mailarchive.ietf.org/arch/msg/tools-discuss/8aE22QzxhBdbKDqV_EAbI8IO8Yw
Subject: Re: [Tools-discuss] reply button on ietf mail archive
X-BeenThere: tools-discuss@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF Tools Discussion 
List-Unsubscribe: , 
List-Archive: 
List-Post: 
List-Help: 
List-Subscribe: , 
X-List-Received-Date: Tue, 28 Oct 2014 16:46:27 -0000

On 10/28/14 10:36, Jeffrey (Zhaohui) Zhang wrote:
> For each archived message, could there be a button so that one could "reply" to a posted message? I don't keep all mailing list messages, and sometimes I need to go back to an archived one and reply to it. Currently there is no convenient way to do it.
>
> I suppose this is not an uncommon situation people may run into. How do you deal with it?

I know we had put out a bid for an IMAP interface to the messages -- do 
we know where that work stands? It would address Jeffrey's use case.

/a


From nobody Tue Oct 28 09:57:47 2014
Return-Path: 
X-Original-To: tools-discuss@ietfa.amsl.com
Delivered-To: tools-discuss@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 68FFD1A8ACA; Tue, 28 Oct 2014 09:57:43 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.911
X-Spam-Level: 
X-Spam-Status: No, score=-1.911 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id VfBhfm8s48H0; Tue, 28 Oct 2014 09:57:41 -0700 (PDT)
Received: from tuna.sandelman.ca (tuna.sandelman.ca [IPv6:2607:f0b0:f:3:216:3eff:fe7c:d1f3]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 7C0201A8AE5; Tue, 28 Oct 2014 09:57:38 -0700 (PDT)
Received: from sandelman.ca (obiwan.sandelman.ca [IPv6:2607:f0b0:f:2::247]) by tuna.sandelman.ca (Postfix) with ESMTP id 202D5203AA; Tue, 28 Oct 2014 12:58:53 -0400 (EDT)
Received: by sandelman.ca (Postfix, from userid 179) id B50D163A84; Tue, 28 Oct 2014 12:57:37 -0400 (EDT)
Received: from sandelman.ca (localhost [127.0.0.1]) by sandelman.ca (Postfix) with ESMTP id 9DE9A63A21; Tue, 28 Oct 2014 12:57:37 -0400 (EDT)
From: Michael Richardson 
To: Henrik Levkowetz 
In-Reply-To: <544FC37B.8010809@levkowetz.com>
References: <26675.1414505870@sandelman.ca> <544FC37B.8010809@levkowetz.com>
X-Mailer: MH-E 8.2; nmh 1.3-dev; GNU Emacs 23.4.1
X-Face: $\n1pF)h^`}$H>Hk{L"x@)JS7<%Az}5RyS@k9X%29-lHB$Ti.V>2bi.~ehC0; <'$9xN5Ub# z!G,p`nR&p7Fz@^UXIn156S8.~^@MJ*mMsD7=QFeq%AL4m
Sender: mcr@sandelman.ca
Archived-At: http://mailarchive.ietf.org/arch/msg/tools-discuss/PseOLuHCaFm-_oCi_WlXdz57zxY
Cc: Glen via , tools-discuss 
Subject: Re: [Tools-discuss] google thinks etherpad is phising
X-BeenThere: tools-discuss@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF Tools Discussion 
List-Unsubscribe: , 
List-Archive: 
List-Post: 
List-Help: 
List-Subscribe: , 
X-List-Received-Date: Tue, 28 Oct 2014 16:57:43 -0000

Henrik Levkowetz  wrote:
    >> Several people (nomcom call yesterday, 6tisch security team this morning)
    >> get this in the past day from etherpad.tools.ietf.org:
    >> http://www.sandelman.ca/tmp/mcrcapture/6969.2014-10-28/capture1.png
    >>
    >> specifically, a warning that the site is a phising site.
    >>
    >> I expect that it's a false positive, but in order to get the details, you
    >> have to connect to the Google web site manager portal to find out.

    > The portal shows no current warnings for ethernet.tools.ietf.org; I just
    > checked.  Furthermore, I don't get this warning when I open a test document
    > in etherpad; but I do get it for the link visible in your screenshot.

hmm. So it's specific to that link.

    > However, if you see a malware warning in the browser when navigating to your
    > site, it's likely that your site is referencing code or content from another
    > domain that has malware. Read up on cross-site malware and learn how to address
    > it.

    > Could it be that there are links in the xml content of the etherpads which
    > google find suspicious?  Or something else related to the content being
    > an xml document under guise of a html page?

Sounds reasonable, except that it also occured for multiple nomcom members;
we use the etherpad for relatively benign activity of taking attendance.
No xml documents living in etherpad, no links...

And it wasn't just me.






From nobody Tue Oct 28 10:20:44 2014
Return-Path: 
X-Original-To: tools-discuss@ietfa.amsl.com
Delivered-To: tools-discuss@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 950D11A90A3 for ; Tue, 28 Oct 2014 10:20:43 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -101.9
X-Spam-Level: 
X-Spam-Status: No, score=-101.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, USER_IN_WHITELIST=-100] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Balh2CCy_Wtw for ; Tue, 28 Oct 2014 10:20:39 -0700 (PDT)
Received: from zinfandel.tools.ietf.org (zinfandel.tools.ietf.org [IPv6:2001:1890:123a::1:2a]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id ECEB11A9096 for ; Tue, 28 Oct 2014 10:20:38 -0700 (PDT)
Received: from localhost ([::1]:54144 helo=tannat.netnod.se) by zinfandel.tools.ietf.org with esmtp (Exim 4.82_1-5b7a7c0-XX) (envelope-from ) id 1XjARi-0000i2-Kc; Tue, 28 Oct 2014 10:20:38 -0700
Message-ID: <544FD065.8080004@levkowetz.com>
Date: Tue, 28 Oct 2014 18:20:37 +0100
From: Henrik Levkowetz 
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.9; rv:24.0) Gecko/20100101 Thunderbird/24.6.0
MIME-Version: 1.0
To: Michael Richardson 
References: <26675.1414505870@sandelman.ca> <544FC37B.8010809@levkowetz.com> <29944.1414515457@sandelman.ca>
In-Reply-To: <29944.1414515457@sandelman.ca>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
X-SA-Exim-Connect-IP: ::1
X-SA-Exim-Rcpt-To: mcr@sandelman.ca, tools-discuss@ietf.org, henrik-sent@levkowetz.com
X-SA-Exim-Mail-From: henrik@levkowetz.com
X-SA-Exim-Scanned: No (on zinfandel.tools.ietf.org); SAEximRunCond expanded to false
Archived-At: http://mailarchive.ietf.org/arch/msg/tools-discuss/Bcnzr0hrQNpGegqq5j-s4OPnctU
Cc: tools-discuss 
Subject: Re: [Tools-discuss] google thinks etherpad is phising
X-BeenThere: tools-discuss@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF Tools Discussion 
List-Unsubscribe: , 
List-Archive: 
List-Post: 
List-Help: 
List-Subscribe: , 
X-List-Received-Date: Tue, 28 Oct 2014 17:20:43 -0000

On 2014-10-28 17:57 Michael Richardson said:
> Henrik Levkowetz  wrote:
>     >> Several people (nomcom call yesterday, 6tisch security team this morning)
>     >> get this in the past day from etherpad.tools.ietf.org:
>     >> http://www.sandelman.ca/tmp/mcrcapture/6969.2014-10-28/capture1.png
>     >>
>     >> specifically, a warning that the site is a phising site.
>     >>
>     >> I expect that it's a false positive, but in order to get the details, you
>     >> have to connect to the Google web site manager portal to find out.
> 
>     > The portal shows no current warnings for ethernet.tools.ietf.org; I just
>     > checked.  Furthermore, I don't get this warning when I open a test document
>     > in etherpad; but I do get it for the link visible in your screenshot.
> 
> hmm. So it's specific to that link.
> 
>     > However, if you see a malware warning in the browser when navigating to your
>     > site, it's likely that your site is referencing code or content from another
>     > domain that has malware. Read up on cross-site malware and learn how to address
>     > it.
> 
>     > Could it be that there are links in the xml content of the etherpads which
>     > google find suspicious?  Or something else related to the content being
>     > an xml document under guise of a html page?
> 
> Sounds reasonable, except that it also occured for multiple nomcom members;
> we use the etherpad for relatively benign activity of taking attendance.
> No xml documents living in etherpad, no links...
> 
> And it wasn't just me.

Ack; I don't doubt the report; but I'd like to understand.  And if no XML doc
was involved for the nomcom etherpad, then it must be something else.  Mph.


Best regards,

	Henrik


From nobody Wed Oct 29 04:47:39 2014
Return-Path: 
X-Original-To: tools-discuss@ietfa.amsl.com
Delivered-To: tools-discuss@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 263521A0012 for ; Wed, 29 Oct 2014 04:47:37 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -101.9
X-Spam-Level: 
X-Spam-Status: No, score=-101.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, USER_IN_WHITELIST=-100] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Xg7iI4SKA5WP for ; Wed, 29 Oct 2014 04:47:35 -0700 (PDT)
Received: from zinfandel.tools.ietf.org (zinfandel.tools.ietf.org [IPv6:2001:1890:123a::1:2a]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id CEB531A000E for ; Wed, 29 Oct 2014 04:47:35 -0700 (PDT)
Received: from localhost ([::1]:56723 helo=tannat.netnod.se) by zinfandel.tools.ietf.org with esmtp (Exim 4.82_1-5b7a7c0-XX) (envelope-from ) id 1XjRiw-0002cs-Hk; Wed, 29 Oct 2014 04:47:34 -0700
Message-ID: <5450D3D5.80404@levkowetz.com>
Date: Wed, 29 Oct 2014 12:47:33 +0100
From: Henrik Levkowetz 
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.9; rv:24.0) Gecko/20100101 Thunderbird/24.6.0
MIME-Version: 1.0
To: Adam Roach ,  "Jeffrey (Zhaohui) Zhang" , "tools-discuss@ietf.org" 
References:  <544FC6C9.2040503@nostrum.com>
In-Reply-To: <544FC6C9.2040503@nostrum.com>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
X-SA-Exim-Connect-IP: ::1
X-SA-Exim-Rcpt-To: adam@nostrum.com, zzhang@juniper.net, tools-discuss@ietf.org, henrik-sent@levkowetz.com
X-SA-Exim-Mail-From: henrik@levkowetz.com
X-SA-Exim-Scanned: No (on zinfandel.tools.ietf.org); SAEximRunCond expanded to false
Archived-At: http://mailarchive.ietf.org/arch/msg/tools-discuss/RHkZT0yV9sxE2ZaImt7F6eUaCyQ
Subject: Re: [Tools-discuss] reply button on ietf mail archive
X-BeenThere: tools-discuss@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF Tools Discussion 
List-Unsubscribe: , 
List-Archive: 
List-Post: 
List-Help: 
List-Subscribe: , 
X-List-Received-Date: Wed, 29 Oct 2014 11:47:37 -0000

On 2014-10-28 17:39 Adam Roach said:
> On 10/28/14 10:36, Jeffrey (Zhaohui) Zhang wrote:
>> For each archived message, could there be a button so that one could "reply" to a posted message? I don't keep all mailing list messages, and sometimes I need to go back to an archived one and reply to it. Currently there is no convenient way to do it.
>>
>> I suppose this is not an uncommon situation people may run into. How do you deal with it?
> 
> I know we had put out a bid for an IMAP interface to the messages -- do 
> we know where that work stands? It would address Jeffrey's use case.

Bids received, evaluated; awarded to ISODE.

I tried to find pointers to IAOC materials on this, but failed.


Best regards,

	Henrik


From nobody Wed Oct 29 06:49:34 2014
Return-Path: 
X-Original-To: tools-discuss@ietfa.amsl.com
Delivered-To: tools-discuss@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 1531E1A00E8 for ; Wed, 29 Oct 2014 06:49:32 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.912
X-Spam-Level: 
X-Spam-Status: No, score=-1.912 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Cf3VsaeEu7qC for ; Wed, 29 Oct 2014 06:49:30 -0700 (PDT)
Received: from mail.ops-netman.net (mailserver.ops-netman.net [208.76.12.119]) (using TLSv1.1 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 62F051A00EF for ; Wed, 29 Oct 2014 06:49:30 -0700 (PDT)
Received: from donkey.her.corp.google.com (unknown [72.14.227.6]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by mail.ops-netman.net (Postfix) with ESMTPSA id ED52688069C for ; Wed, 29 Oct 2014 13:49:28 +0000 (UTC)
Message-ID: <5450F068.4010502@ops-netman.net>
Date: Wed, 29 Oct 2014 09:49:28 -0400
From: Chris Morrow 
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:31.0) Gecko/20100101 Thunderbird/31.1.1
MIME-Version: 1.0
To: tools-discuss@ietf.org
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit
Archived-At: http://mailarchive.ietf.org/arch/msg/tools-discuss/AiG917FO2wu29PDCffOhG3x1KFc
Subject: [Tools-discuss] 'edit shepherds document' link failure?
X-BeenThere: tools-discuss@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF Tools Discussion 
List-Unsubscribe: , 
List-Archive: 
List-Post: 
List-Help: 
List-Subscribe: , 
X-List-Received-Date: Wed, 29 Oct 2014 13:49:32 -0000

Say from this example:
  

clicking on the little pencil by 'Shepherd Write-Up:' which is:


X-Original-To: tools-discuss@ietfa.amsl.com
Delivered-To: tools-discuss@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 5BB711A0119 for ; Wed, 29 Oct 2014 06:58:17 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -101.9
X-Spam-Level: 
X-Spam-Status: No, score=-101.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, USER_IN_WHITELIST=-100] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id sPGDzYuYQ1LI for ; Wed, 29 Oct 2014 06:58:10 -0700 (PDT)
Received: from zinfandel.tools.ietf.org (zinfandel.tools.ietf.org [IPv6:2001:1890:123a::1:2a]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 63D9F1A010E for ; Wed, 29 Oct 2014 06:58:10 -0700 (PDT)
Received: from localhost ([::1]:36216 helo=tannat.netnod.se) by zinfandel.tools.ietf.org with esmtp (Exim 4.82_1-5b7a7c0-XX) (envelope-from ) id 1XjTlJ-0007GO-Ro; Wed, 29 Oct 2014 06:58:10 -0700
Message-ID: <5450F270.7080000@levkowetz.com>
Date: Wed, 29 Oct 2014 14:58:08 +0100
From: Henrik Levkowetz 
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.9; rv:24.0) Gecko/20100101 Thunderbird/24.6.0
MIME-Version: 1.0
To: Chris Morrow , tools-discuss@ietf.org
References: <5450F068.4010502@ops-netman.net>
In-Reply-To: <5450F068.4010502@ops-netman.net>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 8bit
X-SA-Exim-Connect-IP: ::1
X-SA-Exim-Rcpt-To: morrowc@ops-netman.net, tools-discuss@ietf.org, rjsparks@nostrum.com, henrik-sent@levkowetz.com
X-SA-Exim-Mail-From: henrik@levkowetz.com
X-SA-Exim-Scanned: No (on zinfandel.tools.ietf.org); SAEximRunCond expanded to false
Archived-At: http://mailarchive.ietf.org/arch/msg/tools-discuss/wFDs5gcwf9szfu2T71y3GhHF8Ww
Cc: Robert Sparks 
Subject: Re: [Tools-discuss] 'edit shepherds document' link failure?
X-BeenThere: tools-discuss@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF Tools Discussion 
List-Unsubscribe: , 
List-Archive: 
List-Post: 
List-Help: 
List-Subscribe: , 
X-List-Received-Date: Wed, 29 Oct 2014 13:58:17 -0000

Hi Chris,

This is better reported either to the secretariat or to the issue tracker;
from the tools-discuss list footer:

  Please reports datatracker.ietf.org bugs at http://tools.ietf.org/tools/ietfdb

The server sent us tracebacks which should make it possible to track this
down fairly quickly.  Your description is valuable in showing exactly the
steps leading up to this; thanks for that.

Will send you more info directly once we have a fix.


Regards,

	Henrik




On 2014-10-29 14:49 Chris Morrow said:
> Say from this example:
>   
> 
> clicking on the little pencil by 'Shepherd Write-Up:' which is:
> 
>  
> and ... I get the empty shepherds document page with 'edit', clicking on
> 'edit' gets me:
> 
> "The server encountered an internal error and was unable to complete
> your request. Either the server is overloaded or there was an error in a
> script used to generate the requested page. In case this was an overload
> problem or other temporary error, you may want to try again in a little
> while.
> 
> A failure report with details about what happened has been sent to the
> server administrators. It would be helpful if you would file a bug
> report with additional information at the IETF database issue tracker, too"
> 
> 
> guess it's back to the oldschool email-iesg-secretary path?
> 


From nobody Wed Oct 29 06:59:54 2014
Return-Path: 
X-Original-To: tools-discuss@ietfa.amsl.com
Delivered-To: tools-discuss@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 9483D1A010E for ; Wed, 29 Oct 2014 06:59:51 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.912
X-Spam-Level: 
X-Spam-Status: No, score=-1.912 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id awC8qARJXNxn for ; Wed, 29 Oct 2014 06:59:49 -0700 (PDT)
Received: from mail.ops-netman.net (mailserver.ops-netman.net [208.76.12.119]) (using TLSv1.1 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id E1CA41A00F9 for ; Wed, 29 Oct 2014 06:59:48 -0700 (PDT)
Received: from donkey.her.corp.google.com (unknown [72.14.227.6]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by mail.ops-netman.net (Postfix) with ESMTPSA id 1E8878801A4; Wed, 29 Oct 2014 13:59:48 +0000 (UTC)
Message-ID: <5450F2D3.9050105@ops-netman.net>
Date: Wed, 29 Oct 2014 09:59:47 -0400
From: Chris Morrow 
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:31.0) Gecko/20100101 Thunderbird/31.1.1
MIME-Version: 1.0
To: Henrik Levkowetz , tools-discuss@ietf.org
References: <5450F068.4010502@ops-netman.net> <5450F270.7080000@levkowetz.com>
In-Reply-To: <5450F270.7080000@levkowetz.com>
Content-Type: text/plain; charset=windows-1252
Content-Transfer-Encoding: 7bit
Archived-At: http://mailarchive.ietf.org/arch/msg/tools-discuss/0cKPiPlwybLDSPECiZeyU35ZknI
Cc: Robert Sparks 
Subject: Re: [Tools-discuss] 'edit shepherds document' link failure?
X-BeenThere: tools-discuss@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF Tools Discussion 
List-Unsubscribe: , 
List-Archive: 
List-Post: 
List-Help: 
List-Subscribe: , 
X-List-Received-Date: Wed, 29 Oct 2014 13:59:51 -0000

On 10/29/2014 09:58 AM, Henrik Levkowetz wrote:
> Hi Chris,
> 
> This is better reported either to the secretariat or to the issue tracker;
> from the tools-discuss list footer:
> 
>   Please reports datatracker.ietf.org bugs at http://tools.ietf.org/tools/ietfdb
> 

whoops! ok, thanks.

> The server sent us tracebacks which should make it possible to track this
> down fairly quickly.  Your description is valuable in showing exactly the
> steps leading up to this; thanks for that.
> 
> Will send you more info directly once we have a fix.
> 

ok, cool. It's POSSIBLE that this is that I'm not a co-chair for IDR...
and want to write up the shepherds document. So, this might actually be
working as intended.

-chris

> 
> Regards,
> 
> 	Henrik
> 
> 
> 
> 
> On 2014-10-29 14:49 Chris Morrow said:
>> Say from this example:
>>   
>>
>> clicking on the little pencil by 'Shepherd Write-Up:' which is:
>>
>> >
>> and ... I get the empty shepherds document page with 'edit', clicking on
>> 'edit' gets me:
>>
>> "The server encountered an internal error and was unable to complete
>> your request. Either the server is overloaded or there was an error in a
>> script used to generate the requested page. In case this was an overload
>> problem or other temporary error, you may want to try again in a little
>> while.
>>
>> A failure report with details about what happened has been sent to the
>> server administrators. It would be helpful if you would file a bug
>> report with additional information at the IETF database issue tracker, too"
>>
>>
>> guess it's back to the oldschool email-iesg-secretary path?
>>


From nobody Wed Oct 29 07:12:18 2014
Return-Path: 
X-Original-To: tools-discuss@ietfa.amsl.com
Delivered-To: tools-discuss@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 96DEA1A00E8 for ; Wed, 29 Oct 2014 07:12:16 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -101.9
X-Spam-Level: 
X-Spam-Status: No, score=-101.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, USER_IN_WHITELIST=-100] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id SR8wBgAZAgCi for ; Wed, 29 Oct 2014 07:12:13 -0700 (PDT)
Received: from zinfandel.tools.ietf.org (zinfandel.tools.ietf.org [IPv6:2001:1890:123a::1:2a]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id E123C1A00EF for ; Wed, 29 Oct 2014 07:12:10 -0700 (PDT)
Received: from localhost ([::1]:36956 helo=tannat.netnod.se) by zinfandel.tools.ietf.org with esmtp (Exim 4.82_1-5b7a7c0-XX) (envelope-from ) id 1XjTys-0001Ys-FC; Wed, 29 Oct 2014 07:12:10 -0700
Message-ID: <5450F5B9.7070406@levkowetz.com>
Date: Wed, 29 Oct 2014 15:12:09 +0100
From: Henrik Levkowetz 
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.9; rv:24.0) Gecko/20100101 Thunderbird/24.6.0
MIME-Version: 1.0
To: Chris Morrow , tools-discuss@ietf.org
References: <5450F068.4010502@ops-netman.net> <5450F270.7080000@levkowetz.com> <5450F2D3.9050105@ops-netman.net>
In-Reply-To: <5450F2D3.9050105@ops-netman.net>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
X-SA-Exim-Connect-IP: ::1
X-SA-Exim-Rcpt-To: morrowc@ops-netman.net, tools-discuss@ietf.org, rjsparks@nostrum.com, henrik-sent@levkowetz.com
X-SA-Exim-Mail-From: henrik@levkowetz.com
X-SA-Exim-Scanned: No (on zinfandel.tools.ietf.org); SAEximRunCond expanded to false
Archived-At: http://mailarchive.ietf.org/arch/msg/tools-discuss/d-mTFew4UyHNzuDwkYEK7s0a6QU
Cc: Robert Sparks 
Subject: Re: [Tools-discuss] 'edit shepherds document' link failure?
X-BeenThere: tools-discuss@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF Tools Discussion 
List-Unsubscribe: , 
List-Archive: 
List-Post: 
List-Help: 
List-Subscribe: , 
X-List-Received-Date: Wed, 29 Oct 2014 14:12:17 -0000

On 2014-10-29 14:59 Chris Morrow said:
> 
> 
> On 10/29/2014 09:58 AM, Henrik Levkowetz wrote:

<>

>> The server sent us tracebacks which should make it possible to track this
>> down fairly quickly.  Your description is valuable in showing exactly the
>> steps leading up to this; thanks for that.
>>
>> Will send you more info directly once we have a fix.
>>
> 
> ok, cool. It's POSSIBLE that this is that I'm not a co-chair for IDR...
> and want to write up the shepherds document. So, this might actually be
> working as intended.

Nope; it's a bug all right.  I've applied a patch; please try again now
and let us know how it goes.


Best regards,

	Henrik


> -chris
> 
>>
>> Regards,
>>
>> 	Henrik
>>
>>
>>
>>
>> On 2014-10-29 14:49 Chris Morrow said:
>>> Say from this example:
>>>   
>>>
>>> clicking on the little pencil by 'Shepherd Write-Up:' which is:
>>>
>>> >>
>>> and ... I get the empty shepherds document page with 'edit', clicking on
>>> 'edit' gets me:
>>>
>>> "The server encountered an internal error and was unable to complete
>>> your request. Either the server is overloaded or there was an error in a
>>> script used to generate the requested page. In case this was an overload
>>> problem or other temporary error, you may want to try again in a little
>>> while.
>>>
>>> A failure report with details about what happened has been sent to the
>>> server administrators. It would be helpful if you would file a bug
>>> report with additional information at the IETF database issue tracker, too"
>>>
>>>
>>> guess it's back to the oldschool email-iesg-secretary path?
>>>
> 


From nobody Wed Oct 29 07:19:16 2014
Return-Path: 
X-Original-To: tools-discuss@ietfa.amsl.com
Delivered-To: tools-discuss@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 847351A0113 for ; Wed, 29 Oct 2014 07:19:14 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.912
X-Spam-Level: 
X-Spam-Status: No, score=-1.912 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id r6B9Gwovkj-Z for ; Wed, 29 Oct 2014 07:19:13 -0700 (PDT)
Received: from mail.ops-netman.net (mailserver.ops-netman.net [208.76.12.119]) (using TLSv1.1 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 4F39B1A0125 for ; Wed, 29 Oct 2014 07:19:12 -0700 (PDT)
Received: from donkey.her.corp.google.com (unknown [72.14.227.6]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by mail.ops-netman.net (Postfix) with ESMTPSA id A5B2B88011F; Wed, 29 Oct 2014 14:19:11 +0000 (UTC)
Message-ID: <5450F75F.8000601@ops-netman.net>
Date: Wed, 29 Oct 2014 10:19:11 -0400
From: Chris Morrow 
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:31.0) Gecko/20100101 Thunderbird/31.1.1
MIME-Version: 1.0
To: Henrik Levkowetz , tools-discuss@ietf.org
References: <5450F068.4010502@ops-netman.net> <5450F270.7080000@levkowetz.com> <5450F2D3.9050105@ops-netman.net> <5450F5B9.7070406@levkowetz.com>
In-Reply-To: <5450F5B9.7070406@levkowetz.com>
Content-Type: text/plain; charset=windows-1252
Content-Transfer-Encoding: 7bit
Archived-At: http://mailarchive.ietf.org/arch/msg/tools-discuss/LoDLj60AkIVBTOh2us1U2WCRhro
Cc: Robert Sparks 
Subject: Re: [Tools-discuss] 'edit shepherds document' link failure?
X-BeenThere: tools-discuss@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF Tools Discussion 
List-Unsubscribe: , 
List-Archive: 
List-Post: 
List-Help: 
List-Subscribe: , 
X-List-Received-Date: Wed, 29 Oct 2014 14:19:14 -0000

On 10/29/2014 10:12 AM, Henrik Levkowetz wrote:

> Nope; it's a bug all right.  I've applied a patch; please try again now
> and let us know how it goes.

worx! thanks :)


From nobody Wed Oct 29 07:20:33 2014
Return-Path: 
X-Original-To: tools-discuss@ietfa.amsl.com
Delivered-To: tools-discuss@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 1F4921A0141 for ; Wed, 29 Oct 2014 07:20:32 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.9
X-Spam-Level: 
X-Spam-Status: No, score=-1.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id fpM0zipCNM4K for ; Wed, 29 Oct 2014 07:20:27 -0700 (PDT)
Received: from resqmta-po-12v.sys.comcast.net (resqmta-po-12v.sys.comcast.net [IPv6:2001:558:fe16:19:96:114:154:171]) (using TLSv1 with cipher DHE-RSA-AES128-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id D281B1A0137 for ; Wed, 29 Oct 2014 07:19:57 -0700 (PDT)
Received: from resomta-po-19v.sys.comcast.net ([96.114.154.243]) by resqmta-po-12v.sys.comcast.net with comcast id 92KX1p0025FMDhs012KxTb; Wed, 29 Oct 2014 14:19:57 +0000
Received: from hobgoblin.ariadne.com ([24.34.72.61]) by resomta-po-19v.sys.comcast.net with comcast id 92Kv1p00X1KKtkw012KwtP; Wed, 29 Oct 2014 14:19:57 +0000
Received: from hobgoblin.ariadne.com (hobgoblin.ariadne.com [127.0.0.1]) by hobgoblin.ariadne.com (8.14.7/8.14.7) with ESMTP id s9TEJtjB030399; Wed, 29 Oct 2014 10:19:55 -0400
Received: (from worley@localhost) by hobgoblin.ariadne.com (8.14.7/8.14.7/Submit) id s9TEJtjv030398; Wed, 29 Oct 2014 10:19:55 -0400
Date: Wed, 29 Oct 2014 10:19:55 -0400
Message-Id: <201410291419.s9TEJtjv030398@hobgoblin.ariadne.com>
From: worley@ariadne.com (Dale R. Worley)
Sender: worley@ariadne.com (Dale R. Worley)
To: "Jeffrey \(Zhaohui\) Zhang" 
In-reply-to:  (zzhang@juniper.net)
References: 
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=comcast.net; s=q20140121; t=1414592397; bh=Fz/p+6ncHP5EZK+iYst5uIQCHDhRPGo51yKbFP+Pmhg=; h=Received:Received:Received:Received:Date:Message-Id:From:To: Subject; b=XTOx5uF7yEiYVh4OgOauym5wEeFM93Np3YdelsO6BxOTLc3rXP5T6jcDZ+DoZdkdA qXkrU9BOkIcy5BIgSp5NWqGRRXMHTdLuI7Rl7UO4hFjRADHdheTnIbWHvH1ddvBwmz pVWZkNAPT1SSCk6M8zTc7KANbcaR6RMobU1c4siMB8h7/X0+07JaTyYSdeZgg2TAFn vGO7aNUvHp/CAnvWtDIzJI+KW7bbH7/NZq3k2Xul9Dp67th7sX6G6kI26l6Eb/fW3H FEUHHhekRfVqMvr3ybP0eEb5bbXQq45iPZgkHWNPzoc0m6N9WsugztrcumW5WpZBgM r6IWLeE/d9Y0Q==
Archived-At: http://mailarchive.ietf.org/arch/msg/tools-discuss/KwOpozpbfg5xYan7r5LjzoAUKPE
Cc: tools-discuss@ietf.org
Subject: Re: [Tools-discuss] reply button on ietf mail archive
X-BeenThere: tools-discuss@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF Tools Discussion 
List-Unsubscribe: , 
List-Archive: 
List-Post: 
List-Help: 
List-Subscribe: , 
X-List-Received-Date: Wed, 29 Oct 2014 14:20:32 -0000

> From: "Jeffrey (Zhaohui) Zhang" 
> 
> For each archived message, could there be a button so that one could
> "reply" to a posted message? I don't keep all mailing list messages,
> and sometimes I need to go back to an archived one and reply to
> it. Currently there is no convenient way to do it.

I must be behind the times; how do you use your web browser as a
mailer?

> I suppose this is not an uncommon situation people may run into. How
> do you deal with it?

I'd copy the message into the mail-composition buffer of my
mail-reader (Rmail under Emacs) and construct the reply message there.

Of course, that requires that I can extract the actual original
message out of the archive, including headers like Message-Id.

Dale


From nobody Wed Oct 29 07:40:51 2014
Return-Path: 
X-Original-To: tools-discuss@ietfa.amsl.com
Delivered-To: tools-discuss@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 3B0A01A0166 for ; Wed, 29 Oct 2014 07:40:48 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.902
X-Spam-Level: 
X-Spam-Status: No, score=-1.902 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_NONE=-0.0001, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id MYuErwXKxOh4 for ; Wed, 29 Oct 2014 07:40:46 -0700 (PDT)
Received: from na01-bl2-obe.outbound.protection.outlook.com (mail-bl2on0116.outbound.protection.outlook.com [65.55.169.116]) (using TLSv1 with cipher ECDHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id C96B51A0151 for ; Wed, 29 Oct 2014 07:40:45 -0700 (PDT)
Received: from BY2PR05MB079.namprd05.prod.outlook.com (10.242.38.16) by BY2PR05MB077.namprd05.prod.outlook.com (10.242.38.11) with Microsoft SMTP Server (TLS) id 15.1.6.9; Wed, 29 Oct 2014 14:40:43 +0000
Received: from BY2PR05MB079.namprd05.prod.outlook.com ([169.254.8.16]) by BY2PR05MB079.namprd05.prod.outlook.com ([169.254.8.16]) with mapi id 15.01.0006.000; Wed, 29 Oct 2014 14:40:42 +0000
From: "Jeffrey (Zhaohui) Zhang" 
To: "Dale R. Worley" 
Thread-Topic: [Tools-discuss] reply button on ietf mail archive
Thread-Index: Ac/yLjD+4m4y83fSS7izZwQZYHufGABVTvwnAACns0A=
Date: Wed, 29 Oct 2014 14:40:42 +0000
Message-ID: <324ddf2010c24a8893a843198bfea642@BY2PR05MB079.namprd05.prod.outlook.com>
References:  <201410291419.s9TEJtjv030398@hobgoblin.ariadne.com>
In-Reply-To: <201410291419.s9TEJtjv030398@hobgoblin.ariadne.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-ms-exchange-transport-fromentityheader: Hosted
x-originating-ip: [66.129.232.2]
x-microsoft-antispam: BCL:0;PCL:0;RULEID:;SRVR:BY2PR05MB077;
x-forefront-prvs: 03793408BA
x-forefront-antispam-report: SFV:NSPM; SFS:(10019020)(6009001)(189002)(13464003)(51704005)(377454003)(199003)(76176999)(99286002)(54356999)(99396003)(95666004)(33646002)(85306004)(46102003)(19580395003)(87936001)(2656002)(92566001)(21056001)(50986999)(86362001)(76482002)(120916001)(110136001)(108616004)(97736003)(85852003)(101416001)(4396001)(107046002)(105586002)(106356001)(64706001)(122556002)(66066001)(40100003)(74316001)(77096002)(31966008)(19580405001)(76576001)(80022003)(20776003)(24736002); DIR:OUT; SFP:1102; SCL:1; SRVR:BY2PR05MB077; H:BY2PR05MB079.namprd05.prod.outlook.com; FPR:; MLV:sfv; PTR:InfoNoRecords; MX:1; A:1; LANG:en; 
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-OriginatorOrg: juniper.net
Archived-At: http://mailarchive.ietf.org/arch/msg/tools-discuss/IESWQf2RGYXI_uKo2YceohgVsVo
Cc: "tools-discuss@ietf.org" 
Subject: Re: [Tools-discuss] reply button on ietf mail archive
X-BeenThere: tools-discuss@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF Tools Discussion 
List-Unsubscribe: , 
List-Archive: 
List-Post: 
List-Help: 
List-Subscribe: , 
X-List-Received-Date: Wed, 29 Oct 2014 14:40:48 -0000

Dale,

Basically the button would automate the manual steps you described - it'd b=
ring up a message composition window and pre-poulate it with the correspdon=
ing archived message.

Jeffrey

> -----Original Message-----
> From: Dale R. Worley [mailto:worley@ariadne.com]
> Sent: Wednesday, October 29, 2014 10:20 AM
> To: Jeffrey (Zhaohui) Zhang
> Cc: tools-discuss@ietf.org
> Subject: Re: [Tools-discuss] reply button on ietf mail archive
>=20
> > From: "Jeffrey (Zhaohui) Zhang" 
> >
> > For each archived message, could there be a button so that one could
> > "reply" to a posted message? I don't keep all mailing list messages,
> > and sometimes I need to go back to an archived one and reply to
> > it. Currently there is no convenient way to do it.
>=20
> I must be behind the times; how do you use your web browser as a
> mailer?
>=20
> > I suppose this is not an uncommon situation people may run into. How
> > do you deal with it?
>=20
> I'd copy the message into the mail-composition buffer of my
> mail-reader (Rmail under Emacs) and construct the reply message there.
>=20
> Of course, that requires that I can extract the actual original
> message out of the archive, including headers like Message-Id.
>=20
> Dale


From nobody Wed Oct 29 10:44:33 2014
Return-Path: 
X-Original-To: tools-discuss@ietfa.amsl.com
Delivered-To: tools-discuss@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id C21CC1A8746 for ; Wed, 29 Oct 2014 10:44:31 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.901
X-Spam-Level: 
X-Spam-Status: No, score=-1.901 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01, T_TVD_MIME_NO_HEADERS=0.01] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id ctOjo9i_mq3C for ; Wed, 29 Oct 2014 10:44:28 -0700 (PDT)
Received: from tuna.sandelman.ca (tuna.sandelman.ca [IPv6:2607:f0b0:f:3:216:3eff:fe7c:d1f3]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 9F3BB1A870E for ; Wed, 29 Oct 2014 10:44:28 -0700 (PDT)
Received: from sandelman.ca (obiwan.sandelman.ca [IPv6:2607:f0b0:f:2::247]) by tuna.sandelman.ca (Postfix) with ESMTP id 38EA22002D; Wed, 29 Oct 2014 13:45:46 -0400 (EDT)
Received: by sandelman.ca (Postfix, from userid 179) id 5010563A84; Wed, 29 Oct 2014 13:44:27 -0400 (EDT)
Received: from sandelman.ca (localhost [127.0.0.1]) by sandelman.ca (Postfix) with ESMTP id 3A8B363A80; Wed, 29 Oct 2014 13:44:27 -0400 (EDT)
From: Michael Richardson 
To: worley@ariadne.com (Dale R. Worley)
In-Reply-To: <201410291419.s9TEJtjv030398@hobgoblin.ariadne.com>
References:  <201410291419.s9TEJtjv030398@hobgoblin.ariadne.com>
X-Mailer: MH-E 8.2; nmh 1.3-dev; GNU Emacs 23.4.1
X-Face: $\n1pF)h^`}$H>Hk{L"x@)JS7<%Az}5RyS@k9X%29-lHB$Ti.V>2bi.~ehC0; <'$9xN5Ub# z!G,p`nR&p7Fz@^UXIn156S8.~^@MJ*mMsD7=QFeq%AL4m
Sender: mcr@sandelman.ca
Archived-At: http://mailarchive.ietf.org/arch/msg/tools-discuss/VE-DfORW6VJq3LG4WiOnyJOwuGY
Cc: "Jeffrey \(Zhaohui\) Zhang" , tools-discuss@ietf.org
Subject: Re: [Tools-discuss] reply button on ietf mail archive
X-BeenThere: tools-discuss@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF Tools Discussion 
List-Unsubscribe: , 
List-Archive: 
List-Post: 
List-Help: 
List-Subscribe: , 
X-List-Received-Date: Wed, 29 Oct 2014 17:44:31 -0000

--=-=-=


Dale R. Worley  wrote:
    >> For each archived message, could there be a button so that one could
    >> "reply" to a posted message? I don't keep all mailing list messages,
    >> and sometimes I need to go back to an archived one and reply to
    >> it. Currently there is no convenient way to do it.

    > I must be behind the times; how do you use your web browser as a
    > mailer?

An appropriate mailto: URL ought to invoke your MUA from the browser.
In the days of all-in-one Mozilla this was really easy; then we got Firefox
and IE, and they split apart, and who knows which is the MUA... and Linux
desktops had no way... now with GNOME3 (apparently), there are sane ways to
do this with dbus... and Chrome will ask you if you want to use GMAIL
when it sees a mailto: URL.

    >> I suppose this is not an uncommon situation people may run into. How
    >> do you deal with it?

    > I'd copy the message into the mail-composition buffer of my
    > mail-reader (Rmail under Emacs) and construct the reply message there.

    > Of course, that requires that I can extract the actual original
    > message out of the archive, including headers like Message-Id.

Yes, that's my take too --- if you really want to reply in-thread, you really
need the entire message into your MUA, and I hope that with the IMAP stuff,
that means that it will become a imap:// URL, which maybe our MUAs can cope
with.  I think GNUS can deal with that.

--
]               Never tell me the odds!                 | ipv6 mesh networks [
]   Michael Richardson, Sandelman Software Works        | network architect  [
]     mcr@sandelman.ca  http://www.sandelman.ca/        |   ruby on rails    [


--
Michael Richardson , Sandelman Software Works
 -= IPv6 IoT consulting =-




--=-=-=
Content-Type: application/pgp-signature

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.12 (GNU/Linux)

iQEVAwUBVFEneICLcPvd0N1lAQKdhwf7BOSLg8dNZWvvFEsIjK6EMquKupaCvbSk
kambu1R1OFCaWxwRrSHM6uIwjqxjCjgRZcvINxJCu0PMv4s5ZYoTglGCimtq66jU
uBPPw9SxF5bLJh22qhftaCKMvWygvv2aPdorB5hzMyhBGrtKRESPGO9Gznbyc7Bj
dkOE3iqIi9ZljXzWB0uEirSJAhLKTs6vgDGgkj9CI7RRQ8jjNSlkkM3JTKZdOYu1
sDJrNAVhoqblVL4Fio0Bzyw5ysjyG9eYEwbRfFP0yLjLZhDokGYzpOj+rbtJyTNl
gcB7VX2CTPpU9No21zprWAzPbFT3ryl7u9TXAPdcGO9cnCkOC4wluQ==
=9ldj
-----END PGP SIGNATURE-----
--=-=-=--


From nobody Wed Oct 29 21:02:47 2014
Return-Path: 
X-Original-To: tools-discuss@ietfa.amsl.com
Delivered-To: tools-discuss@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id C154C1AD008 for ; Wed, 29 Oct 2014 21:02:44 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.6
X-Spam-Level: 
X-Spam-Status: No, score=-0.6 tagged_above=-999 required=5 tests=[BAYES_05=-0.5, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, SPF_PASS=-0.001] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id SW1JVpBtYmD0 for ; Wed, 29 Oct 2014 21:02:43 -0700 (PDT)
Received: from mail-lb0-x234.google.com (mail-lb0-x234.google.com [IPv6:2a00:1450:4010:c04::234]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id E2B511AD007 for ; Wed, 29 Oct 2014 21:02:42 -0700 (PDT)
Received: by mail-lb0-f180.google.com with SMTP id z12so3668056lbi.11 for ; Wed, 29 Oct 2014 21:02:40 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;  h=mime-version:date:message-id:subject:from:to:content-type; bh=6cYXi5BgOVOgzU/7yb8xXS1d797njdnygQzZH54VnLw=; b=wHT+8lsVwH8WZlq4PjOo9lwrqNC6D6CrAO9nnKNtp4sFR8/hM8/BA7wADU+WvKa7Lz vDhTOyW1x1g2Cd0VomJHU8O0UML3cD94MhdKAv9A0+I439+zq+wQSZMGcBMJZMxvL/T/ KJ2X/xVTnlqb8VDDMN/TEhCcDX+gsqXqBp/u0hpDXDRe0LPVoajEY1lK9yAg2jqHNhzk Mn6kWqhqJLWDNDM7i5pCyQy04o8eYiqSsaB1zB0a9KJjb3NvahXeLm3we6gQqDz0PD7+ T0051l8uodHcBg7JcKsporggjVu+Eq0vRn7svET5VPdThfLdrrRfeZHA43PW9MPOrz4n CrfQ==
MIME-Version: 1.0
X-Received: by 10.152.23.3 with SMTP id i3mr15890379laf.53.1414641760773; Wed, 29 Oct 2014 21:02:40 -0700 (PDT)
Received: by 10.25.215.134 with HTTP; Wed, 29 Oct 2014 21:02:40 -0700 (PDT)
Date: Wed, 29 Oct 2014 21:02:40 -0700
Message-ID: 
From: Martin Thomson 
To: "tools-discuss@ietf.org Discussion" 
Content-Type: text/plain; charset=UTF-8
Archived-At: http://mailarchive.ietf.org/arch/msg/tools-discuss/w-eFduIdBwTy89Whh-jasEqWKmY
Subject: [Tools-discuss] Github template for drafts
X-BeenThere: tools-discuss@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF Tools Discussion 
List-Unsubscribe: , 
List-Archive: 
List-Post: 
List-Help: 
List-Subscribe: , 
X-List-Received-Date: Thu, 30 Oct 2014 04:02:45 -0000

I've been using github for managing my drafts for a while now.  Github
has been particularly successful in attracting and managing some
fairly broad collaboration in HTTP/2, and several other working groups
are now successfully using the model.

I've prepared a template that makes putting a repository together
extremely simple:

  https://github.com/martinthomson/i-d-template

This has now been used successfully by several people, some of whom
had no background in this at all.  Now I'm sharing this more widely,
since it seems to be pretty stable.

A feature of note is that it can integrate with a continuous
integration system, so you can't bust a draft without noticing
quickly.  It can also automatically generate a nice web page, e.g.,
https://unicorn-wg.github.io/sslv3-diediedie/

And it's on github, so of course it's open to new contributions.


From nobody Thu Oct 30 09:18:36 2014
Return-Path: 
X-Original-To: tools-discuss@ietfa.amsl.com
Delivered-To: tools-discuss@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 76A011A005F for ; Thu, 30 Oct 2014 09:18:34 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.9
X-Spam-Level: 
X-Spam-Status: No, score=-1.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 5c834s7Q7qCt for ; Thu, 30 Oct 2014 09:18:32 -0700 (PDT)
Received: from resqmta-po-07v.sys.comcast.net (resqmta-po-07v.sys.comcast.net [IPv6:2001:558:fe16:19:96:114:154:166]) (using TLSv1 with cipher DHE-RSA-AES128-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id BB3EB1A0058 for ; Thu, 30 Oct 2014 09:18:32 -0700 (PDT)
Received: from resomta-po-05v.sys.comcast.net ([96.114.154.229]) by resqmta-po-07v.sys.comcast.net with comcast id 9UJE1p0064xDoy801UJYNJ; Thu, 30 Oct 2014 16:18:32 +0000
Received: from hobgoblin.ariadne.com ([24.34.72.61]) by resomta-po-05v.sys.comcast.net with comcast id 9UJW1p00A1KKtkw01UJXmb; Thu, 30 Oct 2014 16:18:31 +0000
Received: from hobgoblin.ariadne.com (hobgoblin.ariadne.com [127.0.0.1]) by hobgoblin.ariadne.com (8.14.7/8.14.7) with ESMTP id s9UGITSE023890; Thu, 30 Oct 2014 12:18:29 -0400
Received: (from worley@localhost) by hobgoblin.ariadne.com (8.14.7/8.14.7/Submit) id s9UGITaH023889; Thu, 30 Oct 2014 12:18:29 -0400
Date: Thu, 30 Oct 2014 12:18:29 -0400
Message-Id: <201410301618.s9UGITaH023889@hobgoblin.ariadne.com>
From: worley@ariadne.com (Dale R. Worley)
Sender: worley@ariadne.com (Dale R. Worley)
To: Michael Richardson 
In-reply-to: <20386.1414604667@sandelman.ca> (mcr+ietf@sandelman.ca)
References:  <201410291419.s9TEJtjv030398@hobgoblin.ariadne.com> <20386.1414604667@sandelman.ca>
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=comcast.net; s=q20140121; t=1414685912; bh=KwuQ+M0u9It/4o7gmJ0gPvQiNsUkX7OwEv0jl+or4zo=; h=Received:Received:Received:Received:Date:Message-Id:From:To: Subject; b=HOi4dLDuFSemPPg3RngJtcTRQdDn8J/uM7bQmdwlfrSARle46Q5cSeq7gYHzL5jQc wrEztBVHDoLwoshl8zdFeWfInqt4f0KTtKqyStlSCbV0ixeHJHmT8HE44lkej3fxLJ bAbgUSXYdvzf6szOVgM579E5yacJGTBZ+j70SM/Mp4Dx+YiPvMMKpurxc59rWkXLh+ ZD2X86Ac2ONJddSkxoAF1c0V8HuZtJIZhZ0MTmTV3QAfdNlYF/DO0mF59wmg22sZbU W3Q2B/+tR48DvmzgGXvCQknZpF2vfGyFE28C/yc+469j+Po9czt3I/CI6PPk1HH3UM xj3VHX2IliRHw==
Archived-At: http://mailarchive.ietf.org/arch/msg/tools-discuss/dIGm_aobWPeOYSQuQqBPLOjvX6g
Cc: tools-discuss@ietf.org
Subject: Re: [Tools-discuss] reply button on ietf mail archive
X-BeenThere: tools-discuss@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF Tools Discussion 
List-Unsubscribe: , 
List-Archive: 
List-Post: 
List-Help: 
List-Subscribe: , 
X-List-Received-Date: Thu, 30 Oct 2014 16:18:34 -0000

> From: Michael Richardson 
> 
> An appropriate mailto: URL ought to invoke your MUA from the browser.
> In the days of all-in-one Mozilla this was really easy; then we got Firefox
> and IE, and they split apart, and who knows which is the MUA... and Linux
> desktops had no way... now with GNOME3 (apparently), there are sane ways to
> do this with dbus... and Chrome will ask you if you want to use GMAIL
> when it sees a mailto: URL.

OK, that works well enough for me on Firefox, I can right-click and
select "copy the URI", and then paste that into a mail-composition
window.  But the devil is getting the original message headers and
contents.  But perhaps an imap: URL lets you retrieve that, so all you
need for your MUA is a "set up a reply to the message described by
this URL" operation.

>     > Of course, that requires that I can extract the actual original
>     > message out of the archive, including headers like Message-Id.
> 
> Yes, that's my take too --- if you really want to reply in-thread, you really
> need the entire message into your MUA, and I hope that with the IMAP stuff,
> that means that it will become a imap:// URL, which maybe our MUAs can cope
> with.  I think GNUS can deal with that.

In the short run, it would be helpful if there was a way to get the
original mail message out of the archive web pages.

Dale


From nobody Thu Oct 30 09:39:29 2014
Return-Path: 
X-Original-To: tools-discuss@ietfa.amsl.com
Delivered-To: tools-discuss@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id F116D1A010D for ; Thu, 30 Oct 2014 09:39:26 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.901
X-Spam-Level: 
X-Spam-Status: No, score=-1.901 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01, T_TVD_MIME_NO_HEADERS=0.01] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Bpp1UOyyYj53 for ; Thu, 30 Oct 2014 09:39:24 -0700 (PDT)
Received: from tuna.sandelman.ca (tuna.sandelman.ca [IPv6:2607:f0b0:f:3:216:3eff:fe7c:d1f3]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id B00D31A0081 for ; Thu, 30 Oct 2014 09:39:24 -0700 (PDT)
Received: from sandelman.ca (obiwan.sandelman.ca [IPv6:2607:f0b0:f:2::247]) by tuna.sandelman.ca (Postfix) with ESMTP id 77F7E203AF; Thu, 30 Oct 2014 12:40:43 -0400 (EDT)
Received: by sandelman.ca (Postfix, from userid 179) id 3962463A84; Thu, 30 Oct 2014 12:39:21 -0400 (EDT)
Received: from sandelman.ca (localhost [127.0.0.1]) by sandelman.ca (Postfix) with ESMTP id 22EBD63A21; Thu, 30 Oct 2014 12:39:21 -0400 (EDT)
From: Michael Richardson 
To: worley@ariadne.com (Dale R. Worley)
In-Reply-To: <201410301618.s9UGITaH023889@hobgoblin.ariadne.com>
References:  <201410291419.s9TEJtjv030398@hobgoblin.ariadne.com> <20386.1414604667@sandelman.ca> <201410301618.s9UGITaH023889@hobgoblin.ariadne.com>
X-Mailer: MH-E 8.2; nmh 1.3-dev; GNU Emacs 23.4.1
X-Face: $\n1pF)h^`}$H>Hk{L"x@)JS7<%Az}5RyS@k9X%29-lHB$Ti.V>2bi.~ehC0; <'$9xN5Ub# z!G,p`nR&p7Fz@^UXIn156S8.~^@MJ*mMsD7=QFeq%AL4m
Sender: mcr@sandelman.ca
Archived-At: http://mailarchive.ietf.org/arch/msg/tools-discuss/Wy32RXUwSyZb2UqyWZqX_zdsmfc
Cc: tools-discuss@ietf.org
Subject: Re: [Tools-discuss] reply button on ietf mail archive
X-BeenThere: tools-discuss@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF Tools Discussion 
List-Unsubscribe: , 
List-Archive: 
List-Post: 
List-Help: 
List-Subscribe: , 
X-List-Received-Date: Thu, 30 Oct 2014 16:39:27 -0000

--=-=-=


Dale R. Worley  wrote:
    >> From: Michael Richardson 
    >>
    >> An appropriate mailto: URL ought to invoke your MUA from the browser.
    >> In the days of all-in-one Mozilla this was really easy; then we got Firefox
    >> and IE, and they split apart, and who knows which is the MUA... and Linux
    >> desktops had no way... now with GNOME3 (apparently), there are sane ways to
    >> do this with dbus... and Chrome will ask you if you want to use GMAIL
    >> when it sees a mailto: URL.

    > OK, that works well enough for me on Firefox, I can right-click and
    > select "copy the URI", and then paste that into a mail-composition
    > window.  But the devil is getting the original message headers and
    > contents.  But perhaps an imap: URL lets you retrieve that, so all you
    > need for your MUA is a "set up a reply to the message described by
    > this URL" operation.

Sometimes, you can add headers to mailto:, as in ?subject=foo.. I don't know
if this is specified, or was added ad-hoc.

    >> > Of course, that requires that I can extract the actual original
    >> > message out of the archive, including headers like Message-Id.
    >>
    >> Yes, that's my take too --- if you really want to reply in-thread, you really
    >> need the entire message into your MUA, and I hope that with the IMAP stuff,
    >> that means that it will become a imap:// URL, which maybe our MUAs can cope
    >> with.  I think GNUS can deal with that.

    > In the short run, it would be helpful if there was a way to get the
    > original mail message out of the archive web pages.

https://mailarchive.ietf.org/arch/msg/roll/HBhvfpXCbX193pXtU7IZ7xLZG1c#

it's pretty close to the original... but I agree, .txt extension would be
nice, and I think the IMAP interface will do exactly that for us

--
Michael Richardson , Sandelman Software Works
 -= IPv6 IoT consulting =-




--=-=-=
Content-Type: application/pgp-signature

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.12 (GNU/Linux)

iQEVAwUBVFJptoCLcPvd0N1lAQLY/Af+IJ8JSk6l6/eLDu5zwX+nNKK+B7jUwBYp
/p9AhdHLpO+xc0IyklTYQB8WHFf+W5QEVbzBgwv3v1lSi6By4l7sbTZMcGzAg2fg
zEi2gb97LsFG+prO1C5TUddgj1HSznpEDX1Iq9TPekPxdk+R97a+bINQqtp+gCvp
1zcosP80SBp5eCkyQGdgI7dSdkEGsbMmSxUlXetM6R9rW/b5/FNSg6t6071CBDSu
pWRzHjoNuYcLt1ziHERdL/lRMMbX1KqwRP2OTtTM2HnvhiuXQmgTvgk24Jb8QLD0
vMzRvWO1lBMHkyFh3hiwgIVSiSLvsLK+oIDoTMaI2x6pjjXQR0kQZQ==
=YeFj
-----END PGP SIGNATURE-----
--=-=-=--


From nobody Thu Oct 30 09:44:28 2014
Return-Path: 
X-Original-To: tools-discuss@ietfa.amsl.com
Delivered-To: tools-discuss@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 553C61A00FF for ; Thu, 30 Oct 2014 09:44:26 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2
X-Spam-Level: 
X-Spam-Status: No, score=-2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9,  DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, SPF_PASS=-0.001] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id DcbDFM1b17Yt for ; Thu, 30 Oct 2014 09:44:24 -0700 (PDT)
Received: from mail-la0-x229.google.com (mail-la0-x229.google.com [IPv6:2a00:1450:4010:c03::229]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 5F7A61A010F for ; Thu, 30 Oct 2014 09:44:22 -0700 (PDT)
Received: by mail-la0-f41.google.com with SMTP id s18so173529lam.14 for ; Thu, 30 Oct 2014 09:44:20 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;  h=content-type:mime-version:subject:from:in-reply-to:date:cc :message-id:references:to; bh=Z39n+RqyiXQg0abzAySAqNeXwHM7SI5aK2Akf6Kku8E=; b=H8OH24Y4H0kbh3TFTP/JMaqOrawxtM1KhPJrwCNNffotfzqpohubf7SaOPPvhk0pPi Ncms1QObY7FZQEXsqWYptN+DLr/CR4Q7vrOqvjTQpahr9gwx+MUbVCY4Y6d7Hjhe0uzi w4sB4Fyt2dSZY8eDizUqub9BSG5wZG7Y7+shdraaVqs0Eplq/MuzqQixUiDvNguYC5qa ZcJr4gEPNyDVHyWvPiXcgYa4R5KKaGb4Rugl2fMIT7bjywCBpDpSaOj2OSjQMuRrfJkm aRMEh0fy+4VrcdKJ+kLbG7+aa8kE2MSjLcQF2xkJYfntdVXg1aTjfp10sxjzhXRxWa83 jRlA==
X-Received: by 10.113.5.7 with SMTP id ci7mr20638111lbd.9.1414687460607; Thu, 30 Oct 2014 09:44:20 -0700 (PDT)
Received: from [10.0.0.25] ([98.234.222.98]) by mx.google.com with ESMTPSA id m1sm3387772lbt.22.2014.10.30.09.44.17 for  (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Thu, 30 Oct 2014 09:44:18 -0700 (PDT)
Content-Type: multipart/signed; boundary="Apple-Mail=_F6DBED85-85E6-4ABC-AD06-6431B4D349AD"; protocol="application/pgp-signature"; micalg=pgp-sha512
Mime-Version: 1.0 (Mac OS X Mail 6.6 \(1510\))
From: Bob Hinden 
In-Reply-To: <19509.1414687161@sandelman.ca>
Date: Thu, 30 Oct 2014 09:44:13 -0700
Message-Id: <6948C54E-F6B5-4FE9-853E-6458C7FB754D@gmail.com>
References:  <201410291419.s9TEJtjv030398@hobgoblin.ariadne.com> <20386.1414604667@sandelman.ca> <201410301618.s9UGITaH023889@hobgoblin.ariadne.com> <19509.1414687161@sandelman.ca>
To: Michael Richardson 
X-Mailer: Apple Mail (2.1510)
Archived-At: http://mailarchive.ietf.org/arch/msg/tools-discuss/PpoUUg-JdTrOujM4OMQU9tSg6Fc
Cc: tools-discuss@ietf.org
Subject: Re: [Tools-discuss] reply button on ietf mail archive
X-BeenThere: tools-discuss@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF Tools Discussion 
List-Unsubscribe: , 
List-Archive: 
List-Post: 
List-Help: 
List-Subscribe: , 
X-List-Received-Date: Thu, 30 Oct 2014 16:44:26 -0000

--Apple-Mail=_F6DBED85-85E6-4ABC-AD06-6431B4D349AD
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=us-ascii

Hi,

The more I think about it, the more I like this idea of adding a reply =
button.  If this can be done without a lot of work, then I think it is =
worth adding it to the current tool and not wait for the imap =
capabilities.  I have no plans to use imap to access the IETF lists, but =
would use a reply button in the current web interface.

Bob

On Oct 30, 2014, at 9:39 AM, Michael Richardson  =
wrote:

>=20
> Dale R. Worley  wrote:
>>> From: Michael Richardson 
>>>=20
>>> An appropriate mailto: URL ought to invoke your MUA from the =
browser.
>>> In the days of all-in-one Mozilla this was really easy; then we got =
Firefox
>>> and IE, and they split apart, and who knows which is the MUA... and =
Linux
>>> desktops had no way... now with GNOME3 (apparently), there are sane =
ways to
>>> do this with dbus... and Chrome will ask you if you want to use =
GMAIL
>>> when it sees a mailto: URL.
>=20
>> OK, that works well enough for me on Firefox, I can right-click and
>> select "copy the URI", and then paste that into a mail-composition
>> window.  But the devil is getting the original message headers and
>> contents.  But perhaps an imap: URL lets you retrieve that, so all =
you
>> need for your MUA is a "set up a reply to the message described by
>> this URL" operation.
>=20
> Sometimes, you can add headers to mailto:, as in ?subject=3Dfoo.. I =
don't know
> if this is specified, or was added ad-hoc.
>=20
>>>> Of course, that requires that I can extract the actual original
>>>> message out of the archive, including headers like Message-Id.
>>>=20
>>> Yes, that's my take too --- if you really want to reply in-thread, =
you really
>>> need the entire message into your MUA, and I hope that with the IMAP =
stuff,
>>> that means that it will become a imap:// URL, which maybe our MUAs =
can cope
>>> with.  I think GNUS can deal with that.
>=20
>> In the short run, it would be helpful if there was a way to get the
>> original mail message out of the archive web pages.
>=20
> =
https://mailarchive.ietf.org/arch/msg/roll/HBhvfpXCbX193pXtU7IZ7xLZG1c#
>=20
> it's pretty close to the original... but I agree, .txt extension would =
be
> nice, and I think the IMAP interface will do exactly that for us
>=20
> --
> Michael Richardson , Sandelman Software Works
> -=3D IPv6 IoT consulting =3D-
>=20
>=20
>=20
> --=20
> Tools-discuss mailing list
> Tools-discuss@ietf.org
> https://www.ietf.org/mailman/listinfo/tools-discuss
>=20
> Please reports datatracker.ietf.org bugs at =
http://tools.ietf.org/tools/ietfdb
> Please reports tools.ietf.org bugs at =
http://tools.ietf.org/tools/issues or
> send email to webmaster@tools.ietf.org


--Apple-Mail=_F6DBED85-85E6-4ABC-AD06-6431B4D349AD
Content-Transfer-Encoding: 7bit
Content-Disposition: attachment;
	filename=signature.asc
Content-Type: application/pgp-signature;
	name=signature.asc
Content-Description: Message signed with OpenPGP using GPGMail

-----BEGIN PGP SIGNATURE-----
Comment: GPGTools - https://gpgtools.org

iQEcBAEBCgAGBQJUUmrdAAoJEK7rdBF357uo/HoH/j5vlRmNOlUpQvkiHQWGqrMk
EIJngU/6G/q/MWy64Jc4uYVY28rKF/pRXe5g5IvrA3TMjnuLfe0qGFwgoylsMJUs
ZTjWLG9Dfj7v25cWvmk4/GREQuH1cngRVlp/sep5VNOKCJezH5D4ZF0lcA+LxME/
iQoJ3BnuV5FyLrNLcAvEiOzBH790DSqIhsHnyBa4nxeHQEXo8b8XK5voCk8vsabg
yYKHVT5kJ0HjmP1ADU0HXM2oOwlK7aHB7M9Enjt09nOlwaw7PkR/Q2MPUvFeOfIn
SLoedjpqQrJYS5kNqIUDpFaPW/az4YgdWI4im+/37Qv7w6zJcExn3extUIRyXBU=
=Ckio
-----END PGP SIGNATURE-----

--Apple-Mail=_F6DBED85-85E6-4ABC-AD06-6431B4D349AD--


From nobody Thu Oct 30 10:31:52 2014
Return-Path: 
X-Original-To: tools-discuss@ietfa.amsl.com
Delivered-To: tools-discuss@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id CDB4D1A03FF for ; Thu, 30 Oct 2014 10:31:50 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.666
X-Spam-Level: 
X-Spam-Status: No, score=-1.666 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, IP_NOT_FRIENDLY=0.334, RCVD_IN_DNSWL_NONE=-0.0001] autolearn=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id qECWaFm3uS_k for ; Thu, 30 Oct 2014 10:31:49 -0700 (PDT)
Received: from homiemail-a33.g.dreamhost.com (sub4.mail.dreamhost.com [69.163.253.135]) by ietfa.amsl.com (Postfix) with ESMTP id 3FB641A044D for ; Thu, 30 Oct 2014 10:31:49 -0700 (PDT)
Received: from homiemail-a33.g.dreamhost.com (localhost [127.0.0.1]) by homiemail-a33.g.dreamhost.com (Postfix) with ESMTP id B1595594062; Thu, 30 Oct 2014 10:31:48 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha1; c=relaxed; d=cryptonector.com; h=date :from:to:cc:subject:message-id:references:mime-version :content-type:in-reply-to; s=cryptonector.com; bh=8yFHmXlCMlytkV HZjAGhw7d1OHQ=; b=g5G4bwjH5/3MzJB0eJF1jAudfucmclDc58ZVXBDC7GzZF6 2SHDliZFZrNUzXuFVku9VSjMKmYTIuFN2TmyeC3iQEfAmBRRVCSHaMbKYzBKYhMg BwupxOxwDP1FZUbmDMLajgFNGG252hxYAW11+4DhkyEA+nunufiy5AJ5lwwSQ=
Received: from localhost (108-207-244-174.lightspeed.austtx.sbcglobal.net [108.207.244.174]) (Authenticated sender: nico@cryptonector.com) by homiemail-a33.g.dreamhost.com (Postfix) with ESMTPA id 1C9EE594054; Thu, 30 Oct 2014 10:31:47 -0700 (PDT)
Date: Thu, 30 Oct 2014 12:31:47 -0500
From: Nico Williams 
To: Bob Hinden 
Message-ID: <20141030173146.GN17213@localhost>
References:  <201410291419.s9TEJtjv030398@hobgoblin.ariadne.com> <20386.1414604667@sandelman.ca> <201410301618.s9UGITaH023889@hobgoblin.ariadne.com> <19509.1414687161@sandelman.ca> <6948C54E-F6B5-4FE9-853E-6458C7FB754D@gmail.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <6948C54E-F6B5-4FE9-853E-6458C7FB754D@gmail.com>
User-Agent: Mutt/1.5.21 (2010-09-15)
Archived-At: http://mailarchive.ietf.org/arch/msg/tools-discuss/pn-WN7XK7Dend_yqrw363y79BJk
Cc: Michael Richardson , tools-discuss@ietf.org
Subject: Re: [Tools-discuss] reply button on ietf mail archive
X-BeenThere: tools-discuss@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF Tools Discussion 
List-Unsubscribe: , 
List-Archive: 
List-Post: 
List-Help: 
List-Subscribe: , 
X-List-Received-Date: Thu, 30 Oct 2014 17:31:51 -0000

On Thu, Oct 30, 2014 at 09:44:13AM -0700, Bob Hinden wrote:
> The more I think about it, the more I like this idea of adding a reply
> button.  If this can be done without a lot of work, then I think it is
> worth adding it to the current tool and not wait for the imap
> capabilities.  I have no plans to use imap to access the IETF lists,
> but would use a reply button in the current web interface.

A web forum lite, basically, which would require:

 - we'd have to stop worrying about publishing e-mail addresses in the
   archives; spam is a fact of life

   (or we'd have to have logins (IETF accounts, as it were))

 - the archiver would have to be updated to generate reply-to-list,
   reply-to-sender, reply-to-all buttons with mailto: URIs with
   In-Reply-To set properly and so on and so forth.

The IMAP solution seems best to me, though I'm not opposed to the above.

Or, if not using mailto: URIs, a proper web forum (ick), but let's not
go there please.

Nico
-- 


From nobody Thu Oct 30 10:40:07 2014
Return-Path: 
X-Original-To: tools-discuss@ietfa.amsl.com
Delivered-To: tools-discuss@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 31B601A04BA for ; Thu, 30 Oct 2014 10:40:06 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2
X-Spam-Level: 
X-Spam-Status: No, score=-2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9,  DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, SPF_PASS=-0.001] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id ZBwuv9RxXsno for ; Thu, 30 Oct 2014 10:40:04 -0700 (PDT)
Received: from mail-la0-x230.google.com (mail-la0-x230.google.com [IPv6:2a00:1450:4010:c03::230]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id D08811A0187 for ; Thu, 30 Oct 2014 10:39:58 -0700 (PDT)
Received: by mail-la0-f48.google.com with SMTP id gq15so4744542lab.7 for ; Thu, 30 Oct 2014 10:39:56 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;  h=content-type:mime-version:subject:from:in-reply-to:date:cc :message-id:references:to; bh=1AnD2hEJF2QFN1ZAJwONS/4bOpPMzesK0N0r2Jm5Oqs=; b=XxF6Yxp3JP+GbuYiGRZ6IbMrECkUlD3Wv+jay8P+GvmToW700oil5aiN9A6Wftsbx1 ygMvt6mR5HgcYLM5bbm/sf8zvcoDwv4Tt39dB6a8H9WrqjAPN7cRVXzxFP4/i3GcUMb5 JM4nUTcJBCB6LBXq71iKAdRjJ1BhRVbKvTs98tFuhNwtf0wIgurN5FnRqlVo96BKblhf aDnoWcFhcNZ3Ie6Vsr5XcCTg5RcFe351dlh1+0uxfu1HJxbBIU1rYe7dPOFfTXpLVSrx cX1CvzR0gK3PCHxFBgwWHLbJLoLu16mw4XAm2KyW17Lv9vPBxaLcN5QEDY/fzIlBK+Ha IU1g==
X-Received: by 10.112.77.129 with SMTP id s1mr21116729lbw.36.1414690796769; Thu, 30 Oct 2014 10:39:56 -0700 (PDT)
Received: from ?IPv6:2601:9:500:76b:dad:d1ae:85b1:7e67? ([2601:9:500:76b:dad:d1ae:85b1:7e67]) by mx.google.com with ESMTPSA id x7sm2125226lad.13.2014.10.30.10.39.53 for  (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Thu, 30 Oct 2014 10:39:55 -0700 (PDT)
Content-Type: multipart/signed; boundary="Apple-Mail=_6AF26A5B-43BB-4CDE-9211-FBFB2C46A87E"; protocol="application/pgp-signature"; micalg=pgp-sha512
Mime-Version: 1.0 (Mac OS X Mail 6.6 \(1510\))
From: Bob Hinden 
In-Reply-To: <20141030173146.GN17213@localhost>
Date: Thu, 30 Oct 2014 10:39:45 -0700
Message-Id: <1C9193C3-7E94-4A21-8843-22B43022ED8D@gmail.com>
References:  <201410291419.s9TEJtjv030398@hobgoblin.ariadne.com> <20386.1414604667@sandelman.ca> <201410301618.s9UGITaH023889@hobgoblin.ariadne.com> <19509.1414687161@sandelman.ca> <6948C54E-F6B5-4FE9-853E-6458C7FB754D@gmail.com> <20141030173146.GN17213@localhost>
To: Nico Williams 
X-Mailer: Apple Mail (2.1510)
Archived-At: http://mailarchive.ietf.org/arch/msg/tools-discuss/oSMdTi0PCe-3IRZPzfvIZNk6VU4
Cc: Michael Richardson , tools-discuss@ietf.org
Subject: Re: [Tools-discuss] reply button on ietf mail archive
X-BeenThere: tools-discuss@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF Tools Discussion 
List-Unsubscribe: , 
List-Archive: 
List-Post: 
List-Help: 
List-Subscribe: , 
X-List-Received-Date: Thu, 30 Oct 2014 17:40:06 -0000

--Apple-Mail=_6AF26A5B-43BB-4CDE-9211-FBFB2C46A87E
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=us-ascii

Nico,

On Oct 30, 2014, at 10:31 AM, Nico Williams  =
wrote:

> On Thu, Oct 30, 2014 at 09:44:13AM -0700, Bob Hinden wrote:
>> The more I think about it, the more I like this idea of adding a =
reply
>> button.  If this can be done without a lot of work, then I think it =
is
>> worth adding it to the current tool and not wait for the imap
>> capabilities.  I have no plans to use imap to access the IETF lists,
>> but would use a reply button in the current web interface.
>=20
> A web forum lite, basically, which would require:
>=20
> - we'd have to stop worrying about publishing e-mail addresses in the
>   archives; spam is a fact of life

Aren't email address already in the archives?  I see them.

Now that you mention it, we don't think that spammers will use imap to =
harvest our archives.  Clearly more efficient that having to subscribe =
to each list :-(

>=20
>   (or we'd have to have logins (IETF accounts, as it were))

I log into the tool now to see private lists.  This would be an OK =
restriction.

Bob

>=20
> - the archiver would have to be updated to generate reply-to-list,
>   reply-to-sender, reply-to-all buttons with mailto: URIs with
>   In-Reply-To set properly and so on and so forth.
>=20
> The IMAP solution seems best to me, though I'm not opposed to the =
above.
>=20
> Or, if not using mailto: URIs, a proper web forum (ick), but let's not
> go there please.
>=20
> Nico
> --=20


--Apple-Mail=_6AF26A5B-43BB-4CDE-9211-FBFB2C46A87E
Content-Transfer-Encoding: 7bit
Content-Disposition: attachment;
	filename=signature.asc
Content-Type: application/pgp-signature;
	name=signature.asc
Content-Description: Message signed with OpenPGP using GPGMail

-----BEGIN PGP SIGNATURE-----
Comment: GPGTools - https://gpgtools.org

iQEcBAEBCgAGBQJUUnfhAAoJEK7rdBF357uoIFcH/R5syytHmlBPnz0UwPrnxoCX
MqilXB1SEntkCkoGLuE9meTs9UGuksAl6huN7RNHFMdRKcAY82oiLWG9N4rB+RDD
H8aM1tJy+u4FzHC9CIspEI7lhX91vJgwBrrykklaD4ItG6G4hYTBn67sWfHbupnS
q9bL2dmYd1/GhBYLcqZsm1+8Gf20jd7lXPslxDevpZ194gJajVlN5xcvCKX1RQp3
SOp361ooO5jUju92femDV6+oI1cN1sQukWJ18EarPSnfxg+o650kK68QRjfUfyDQ
nfyXmwqX7xPOBiRzxS5Vg5a2Z1uyXZreDAlCouDlMLsnFxOUEW1+rdFN5KdRarw=
=PPMD
-----END PGP SIGNATURE-----

--Apple-Mail=_6AF26A5B-43BB-4CDE-9211-FBFB2C46A87E--


From nobody Thu Oct 30 19:41:53 2014
Return-Path: 
X-Original-To: tools-discuss@ietfa.amsl.com
Delivered-To: tools-discuss@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 03D1E1A8A93 for ; Thu, 30 Oct 2014 19:41:50 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.2
X-Spam-Level: 
X-Spam-Status: No, score=-4.2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id NdFU8_qjlPFd for ; Thu, 30 Oct 2014 19:41:48 -0700 (PDT)
Received: from sbh17.songbird.com (sbh17.songbird.com [72.52.113.17]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 7E2741A8A90 for ; Thu, 30 Oct 2014 19:41:48 -0700 (PDT)
Received: from [192.168.1.66] (76-218-8-156.lightspeed.sntcca.sbcglobal.net [76.218.8.156]) (authenticated bits=0) by sbh17.songbird.com (8.13.8/8.13.8) with ESMTP id s9V2fhWE017708 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES128-SHA bits=128 verify=NOT); Thu, 30 Oct 2014 19:41:46 -0700
Message-ID: <5452F6E2.1080808@dcrocker.net>
Date: Thu, 30 Oct 2014 19:41:38 -0700
From: Dave Crocker 
Organization: Brandenburg InternetWorking
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:24.0) Gecko/20100101 Thunderbird/24.6.0
MIME-Version: 1.0
To: Nico Williams 
References:  <201410291419.s9TEJtjv030398@hobgoblin.ariadne.com> <20386.1414604667@sandelman.ca> <201410301618.s9UGITaH023889@hobgoblin.ariadne.com> <19509.1414687161@sandelman.ca> <6948C54E-F6B5-4FE9-853E-6458C7FB754D@gmail.com> <20141030173146.GN17213@localhost>
In-Reply-To: <20141030173146.GN17213@localhost>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 8bit
X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.0 (sbh17.songbird.com [72.52.113.66]); Thu, 30 Oct 2014 19:41:46 -0700 (PDT)
Archived-At: http://mailarchive.ietf.org/arch/msg/tools-discuss/QzcoRcNagYYEPaCOzsJVttN0_O0
Cc: tools-discuss@ietf.org
Subject: Re: [Tools-discuss] reply button on ietf mail archive
X-BeenThere: tools-discuss@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
Reply-To: dcrocker@bbiw.net
List-Id: IETF Tools Discussion 
List-Unsubscribe: , 
List-Archive: 
List-Post: 
List-Help: 
List-Subscribe: , 
X-List-Received-Date: Fri, 31 Oct 2014 02:41:50 -0000

On 10/30/2014 10:31 AM, Nico Williams wrote:
> A web forum lite, basically, which would require:
> 
>  - we'd have to stop worrying about publishing e-mail addresses in the
>    archives; spam is a fact of life
> 
>    (or we'd have to have logins (IETF accounts, as it were))
> 
>  - the archiver would have to be updated to generate reply-to-list,
>    reply-to-sender, reply-to-all buttons with mailto: URIs with
>    In-Reply-To set properly and so on and so forth.


That's a nice listing of the issues to worry about:  authenticating the
replying author and their email address, and enabling choice of the
addresses to reply to.

The site already enforced a login requirement for access to some
functions; so requiring it for reply ought to be easy.

The archive already shows addresses, albeit in the amusingly meager
re-coded " at " form.  (What is ironic about that particular attempt at
obfuscation is that the original mail format spec, RFC733, permitted use
of either "@" or " at "...

d/


-- 
Dave Crocker
Brandenburg InternetWorking
bbiw.net


From nobody Fri Oct 31 08:28:14 2014
Return-Path: 
X-Original-To: tools-discuss@ietfa.amsl.com
Delivered-To: tools-discuss@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 414FB1A8AA9 for ; Fri, 31 Oct 2014 08:28:13 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.9
X-Spam-Level: 
X-Spam-Status: No, score=-1.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id iIaw0vFmKGPn for ; Fri, 31 Oct 2014 08:28:11 -0700 (PDT)
Received: from resqmta-po-03v.sys.comcast.net (resqmta-po-03v.sys.comcast.net [IPv6:2001:558:fe16:19:96:114:154:162]) (using TLSv1 with cipher DHE-RSA-AES128-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 8D9461A0115 for ; Fri, 31 Oct 2014 08:28:11 -0700 (PDT)
Received: from resomta-po-13v.sys.comcast.net ([96.114.154.237]) by resqmta-po-03v.sys.comcast.net with comcast id 9rTz1p00157bBgG01rUArN; Fri, 31 Oct 2014 15:28:10 +0000
Received: from hobgoblin.ariadne.com ([24.34.72.61]) by resomta-po-13v.sys.comcast.net with comcast id 9r4A1p00H1KKtkw01r4B0m; Fri, 31 Oct 2014 15:04:11 +0000
Received: from hobgoblin.ariadne.com (hobgoblin.ariadne.com [127.0.0.1]) by hobgoblin.ariadne.com (8.14.7/8.14.7) with ESMTP id s9VF49Yh008228; Fri, 31 Oct 2014 11:04:09 -0400
Received: (from worley@localhost) by hobgoblin.ariadne.com (8.14.7/8.14.7/Submit) id s9VF49PO008227; Fri, 31 Oct 2014 11:04:09 -0400
Date: Fri, 31 Oct 2014 11:04:09 -0400
Message-Id: <201410311504.s9VF49PO008227@hobgoblin.ariadne.com>
From: worley@ariadne.com (Dale R. Worley)
Sender: worley@ariadne.com (Dale R. Worley)
To: Michael Richardson 
In-reply-to: <19509.1414687161@sandelman.ca> (mcr+ietf@sandelman.ca)
References:  <201410291419.s9TEJtjv030398@hobgoblin.ariadne.com> <20386.1414604667@sandelman.ca> <201410301618.s9UGITaH023889@hobgoblin.ariadne.com> <19509.1414687161@sandelman.ca>
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=comcast.net; s=q20140121; t=1414769290; bh=TT2OvdT+8mfkiGCFuJpzC7/kEcisNPJoP3K4CHqYSn8=; h=Received:Received:Received:Received:Date:Message-Id:From:To: Subject; b=At+mwh4ijhm2rJ+vwWK/9P+H/TJWAogsc4ehgM8Pzj5To156hismPo7dvnc61XUte QZy9wQRmNo3KIa/gIacMZfY9mDPBv2qVjKY3xJL+y2mh9rHn9mmIpRC4hvzHfsl0TK FrhGLMDsFtF3qFEKgviSYKOgDKZl8Lq9Mz67zlfkxNCF4abI2TQEu5joUqtKByjFa2 hRbnbuYsQ9nmzlAkLIws9rVQTDPUP4jf9mfi0lyt651eMUlKhj/hLEVPcNsFtt31vB 4GnZGIyyJnpWb3GpCKgaxtzEi/MTA+jqGmQmZbPv8JayIVkszFyFUNYG6dY/zhBCsk f/gAWq3JUfOYw==
Archived-At: http://mailarchive.ietf.org/arch/msg/tools-discuss/Qm4It_j-6Gzl7QlGkkBx1s7OMag
Cc: tools-discuss@ietf.org
Subject: Re: [Tools-discuss] reply button on ietf mail archive
X-BeenThere: tools-discuss@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF Tools Discussion 
List-Unsubscribe: , 
List-Archive: 
List-Post: 
List-Help: 
List-Subscribe: , 
X-List-Received-Date: Fri, 31 Oct 2014 15:28:13 -0000

> From: Michael Richardson 
> 
>     > OK, that works well enough for me on Firefox, I can right-click and
>     > select "copy the URI", and then paste that into a mail-composition
>     > window.  But the devil is getting the original message headers and
>     > contents.  But perhaps an imap: URL lets you retrieve that, so all you
>     > need for your MUA is a "set up a reply to the message described by
>     > this URL" operation.
> 
> Sometimes, you can add headers to mailto:, as in ?subject=foo.. I don't know
> if this is specified, or was added ad-hoc.

Michael's message prompted me to go read the RFC like I should have
before.  RFC 2368 defines the use of "?subject=..." etc.  It also
defines "?body=...", so you can have the URL include the quoted body
of the message to reply to.  (As long as your software handles
infinitely long URLs.)

So maybe this is a lot easier to implement than it looks at first
sight.

Dale


From nobody Fri Oct 31 17:00:01 2014
Return-Path: 
X-Original-To: tools-discuss@ietfa.amsl.com
Delivered-To: tools-discuss@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 6EA131A1B6D for ; Fri, 31 Oct 2014 16:59:59 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.909
X-Spam-Level: 
X-Spam-Status: No, score=-1.909 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, T_RP_MATCHES_RCVD=-0.01] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id lA4wE6IbTEZ0 for ; Fri, 31 Oct 2014 16:59:57 -0700 (PDT)
Received: from nostrum.com (raven-v6.nostrum.com [IPv6:2001:470:d:1130::1]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 7EE1D1A874D for ; Fri, 31 Oct 2014 16:59:57 -0700 (PDT)
Received: from Orochi.local (50-200-68-226-static.hfc.comcastbusiness.net [50.200.68.226]) (authenticated bits=0) by nostrum.com (8.14.9/8.14.7) with ESMTP id s9VNxpMk001405 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Fri, 31 Oct 2014 18:59:52 -0500 (CDT) (envelope-from adam@nostrum.com)
X-Authentication-Warning: raven.nostrum.com: Host 50-200-68-226-static.hfc.comcastbusiness.net [50.200.68.226] claimed to be Orochi.local
Message-ID: <54542273.8080008@nostrum.com>
Date: Fri, 31 Oct 2014 16:59:47 -0700
From: Adam Roach 
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.8; rv:31.0) Gecko/20100101 Thunderbird/31.2.0
MIME-Version: 1.0
To: "Dale R. Worley" , Michael Richardson 
References:  <201410291419.s9TEJtjv030398@hobgoblin.ariadne.com> <20386.1414604667@sandelman.ca> <201410301618.s9UGITaH023889@hobgoblin.ariadne.com> <19509.1414687161@sandelman.ca> <201410311504.s9VF49PO008227@hobgoblin.ariadne.com>
In-Reply-To: <201410311504.s9VF49PO008227@hobgoblin.ariadne.com>
Content-Type: multipart/alternative; boundary="------------020602040901030802020509"
Archived-At: http://mailarchive.ietf.org/arch/msg/tools-discuss/27gI-hMPjSni2IuzrVykoGUqDeI
Cc: tools-discuss@ietf.org
Subject: Re: [Tools-discuss] reply button on ietf mail archive
X-BeenThere: tools-discuss@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF Tools Discussion 
List-Unsubscribe: , 
List-Archive: 
List-Post: 
List-Help: 
List-Subscribe: , 
X-List-Received-Date: Fri, 31 Oct 2014 23:59:59 -0000

This is a multi-part message in MIME format.
--------------020602040901030802020509
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Transfer-Encoding: 7bit

On 10/31/14 08:04, Dale R. Worley wrote:
>> From: Michael Richardson 
>>
>>      > OK, that works well enough for me on Firefox, I can right-click and
>>      > select "copy the URI", and then paste that into a mail-composition
>>      > window.  But the devil is getting the original message headers and
>>      > contents.  But perhaps an imap: URL lets you retrieve that, so all you
>>      > need for your MUA is a "set up a reply to the message described by
>>      > this URL" operation.
>>
>> Sometimes, you can add headers to mailto:, as in ?subject=foo.. I don't know
>> if this is specified, or was added ad-hoc.
> Michael's message prompted me to go read the RFC like I should have
> before.  RFC 2368 defines the use of "?subject=..." etc.  It also
> defines "?body=...", so you can have the URL include the quoted body
> of the message to reply to.  (As long as your software handles
> infinitely long URLs.)
>
> So maybe this is a lot easier to implement than it looks at first
> sight.
>

If someone is thinking about taking this on, please note that RFC 6068 
has obsoleted RFC 2368. The most important difference is a shift from 
ASCII to UTF-8.

/a

--------------020602040901030802020509
Content-Type: text/html; charset=utf-8
Content-Transfer-Encoding: 7bit


  
    
  
  
    
On 10/31/14 08:04, Dale R. Worley
      wrote:

    

    

      

        
From: Michael Richardson <mcr+ietf@sandelman.ca>

    > OK, that works well enough for me on Firefox, I can right-click and
    > select "copy the URI", and then paste that into a mail-composition
    > window.  But the devil is getting the original message headers and
    > contents.  But perhaps an imap: URL lets you retrieve that, so all you
    > need for your MUA is a "set up a reply to the message described by
    > this URL" operation.

Sometimes, you can add headers to mailto:, as in ?subject=foo.. I don't know
if this is specified, or was added ad-hoc.


      

      
Michael's message prompted me to go read the RFC like I should have
before.  RFC 2368 defines the use of "?subject=..." etc.  It also
defines "?body=...", so you can have the URL include the quoted body
of the message to reply to.  (As long as your software handles
infinitely long URLs.)

So maybe this is a lot easier to implement than it looks at first
sight.



    

    

    If someone is thinking about taking this on, please note that RFC
    
    6068 has obsoleted RFC 2368. The most important
      difference is a shift from ASCII to UTF-8.

      

      /a

    
  


--------------020602040901030802020509--


From nobody Fri Oct 31 17:01:22 2014
Return-Path: 
X-Original-To: tools-discuss@ietfa.amsl.com
Delivered-To: tools-discuss@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 1DC831A8749 for ; Fri, 31 Oct 2014 17:01:21 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.91
X-Spam-Level: 
X-Spam-Status: No, score=-1.91 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, T_RP_MATCHES_RCVD=-0.01] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id KoNvVHpp0FIE for ; Fri, 31 Oct 2014 17:01:19 -0700 (PDT)
Received: from nostrum.com (raven-v6.nostrum.com [IPv6:2001:470:d:1130::1]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 58FE71A1B6D for ; Fri, 31 Oct 2014 17:01:19 -0700 (PDT)
Received: from Orochi.local (50-200-68-226-static.hfc.comcastbusiness.net [50.200.68.226]) (authenticated bits=0) by nostrum.com (8.14.9/8.14.7) with ESMTP id sA101FGr001567 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Fri, 31 Oct 2014 19:01:15 -0500 (CDT) (envelope-from adam@nostrum.com)
X-Authentication-Warning: raven.nostrum.com: Host 50-200-68-226-static.hfc.comcastbusiness.net [50.200.68.226] claimed to be Orochi.local
Message-ID: <545422C6.8040601@nostrum.com>
Date: Fri, 31 Oct 2014 17:01:10 -0700
From: Adam Roach 
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.8; rv:31.0) Gecko/20100101 Thunderbird/31.2.0
MIME-Version: 1.0
To: "Dale R. Worley" , Michael Richardson 
References:  <201410291419.s9TEJtjv030398@hobgoblin.ariadne.com> <20386.1414604667@sandelman.ca> <201410301618.s9UGITaH023889@hobgoblin.ariadne.com> <19509.1414687161@sandelman.ca> <201410311504.s9VF49PO008227@hobgoblin.ariadne.com>
In-Reply-To: <201410311504.s9VF49PO008227@hobgoblin.ariadne.com>
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Transfer-Encoding: 7bit
Archived-At: http://mailarchive.ietf.org/arch/msg/tools-discuss/cJvSYdW29a5bn6423lEMQiroGc8
Cc: tools-discuss@ietf.org
Subject: Re: [Tools-discuss] reply button on ietf mail archive
X-BeenThere: tools-discuss@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF Tools Discussion 
List-Unsubscribe: , 
List-Archive: 
List-Post: 
List-Help: 
List-Subscribe: , 
X-List-Received-Date: Sat, 01 Nov 2014 00:01:21 -0000

On 10/31/14 08:04, Dale R. Worley wrote:
>> From: Michael Richardson 
>>
>>      > OK, that works well enough for me on Firefox, I can right-click and
>>      > select "copy the URI", and then paste that into a mail-composition
>>      > window.  But the devil is getting the original message headers and
>>      > contents.  But perhaps an imap: URL lets you retrieve that, so all you
>>      > need for your MUA is a "set up a reply to the message described by
>>      > this URL" operation.
>>
>> Sometimes, you can add headers to mailto:, as in ?subject=foo.. I don't know
>> if this is specified, or was added ad-hoc.
> Michael's message prompted me to go read the RFC like I should have
> before.  RFC 2368 defines the use of "?subject=..." etc.  It also
> defines "?body=...", so you can have the URL include the quoted body
> of the message to reply to.  (As long as your software handles
> infinitely long URLs.)
>
> So maybe this is a lot easier to implement than it looks at first
> sight.
>

Oh, and I forgot to mention -- mailto: only lets you use text/plain 
bodies. Probably not a huge deal, but it does mean that implementing 
this feature would require the ability to flatten HTML mail into text/plain.

/a


From nobody Fri Oct 31 17:33:17 2014
Return-Path: 
X-Original-To: tools-discuss@ietfa.amsl.com
Delivered-To: tools-discuss@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 7BAA11A875A for ; Fri, 31 Oct 2014 17:33:16 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.044
X-Spam-Level: 
X-Spam-Status: No, score=-1.044 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FM_FORGED_GMAIL=0.622, IP_NOT_FRIENDLY=0.334, RCVD_IN_DNSWL_NONE=-0.0001] autolearn=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id hHfo4UPkNk77 for ; Fri, 31 Oct 2014 17:33:15 -0700 (PDT)
Received: from homiemail-a110.g.dreamhost.com (sub4.mail.dreamhost.com [69.163.253.135]) by ietfa.amsl.com (Postfix) with ESMTP id 5FF031A875C for ; Fri, 31 Oct 2014 17:33:15 -0700 (PDT)
Received: from homiemail-a110.g.dreamhost.com (localhost [127.0.0.1]) by homiemail-a110.g.dreamhost.com (Postfix) with ESMTP id 1B6AB20047B89 for ; Fri, 31 Oct 2014 17:33:15 -0700 (PDT)
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=7mK3BmVWMVvuH5ydxj5q FLUxinw=; b=fyBDVxqpeKEMcYHXwQtOwKLRkxhksmSTvXK/kZJ4VPOANfDbfasx MOLujyQHFqSRgfciVub3sjwwviHf1LO1vXt8uS2M8lQcO1o6iYZJSKKUDXQHB5IK 4rvHLQtLSb8TYFZ01CboyN/Td723Jx8YOzjAQcmlZSh/7zsodM6IRdk=
Received: from mail-wg0-f50.google.com (mail-wg0-f50.google.com [74.125.82.50]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) (Authenticated sender: nico@cryptonector.com) by homiemail-a110.g.dreamhost.com (Postfix) with ESMTPSA id C5E8C20047B80 for ; Fri, 31 Oct 2014 17:33:14 -0700 (PDT)
Received: by mail-wg0-f50.google.com with SMTP id z12so9026342wgg.9 for ; Fri, 31 Oct 2014 17:33:13 -0700 (PDT)
MIME-Version: 1.0
X-Received: by 10.180.211.70 with SMTP id na6mr592722wic.3.1414801993702; Fri, 31 Oct 2014 17:33:13 -0700 (PDT)
Received: by 10.216.32.135 with HTTP; Fri, 31 Oct 2014 17:33:13 -0700 (PDT)
In-Reply-To: <545422C6.8040601@nostrum.com>
References:  <201410291419.s9TEJtjv030398@hobgoblin.ariadne.com> <20386.1414604667@sandelman.ca> <201410301618.s9UGITaH023889@hobgoblin.ariadne.com> <19509.1414687161@sandelman.ca> <201410311504.s9VF49PO008227@hobgoblin.ariadne.com> <545422C6.8040601@nostrum.com>
Date: Fri, 31 Oct 2014 19:33:13 -0500
Message-ID: 
From: Nico Williams 
To: Adam Roach 
Content-Type: text/plain; charset=UTF-8
Archived-At: http://mailarchive.ietf.org/arch/msg/tools-discuss/Ms3rsPOTBmM2FEPSwd9y9j_xfko
Cc: Michael Richardson , Tools Team Discussion 
Subject: Re: [Tools-discuss] reply button on ietf mail archive
X-BeenThere: tools-discuss@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF Tools Discussion 
List-Unsubscribe: , 
List-Archive: 
List-Post: 
List-Help: 
List-Subscribe: , 
X-List-Received-Date: Sat, 01 Nov 2014 00:33:16 -0000

Well, I mean, the obvious thing to do is to write a "lite" MUA in
JavaScript and have it produce the completed mailto: and...  never
mind, that's not a good joke.

If anyone does this, I'd say have a button for viewing the message
with an MUA -- an IMAP URL, and then the reply-to-author/list/all
buttons with no body, just subject and in-reply-to (the user can
always cut-n-paste to quote, and there could a
pre-angle-bracket-quoted version of the mail to cut-n-past from).
Besides, that would force users to think about what to quote.  That'd
be the 80% solution that makes most people happy.

Making users think about what to quote would be the Killer App here.
Hmmm, yes, we should definitely do this!

Nico
--