Re: Easier access to diffs, etc.

Robert Sparks <rjsparks@nostrum.com> Tue, 13 March 2012 22:40 UTC

Return-Path: <rjsparks@nostrum.com>
X-Original-To: wgchairs@ietfa.amsl.com
Delivered-To: wgchairs@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id BED1D21E8028 for <wgchairs@ietfa.amsl.com>; Tue, 13 Mar 2012 15:40:42 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.552
X-Spam-Level:
X-Spam-Status: No, score=-102.552 tagged_above=-999 required=5 tests=[AWL=0.048, BAYES_00=-2.599, SPF_PASS=-0.001, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id pSmRWoNHxHdw for <wgchairs@ietfa.amsl.com>; Tue, 13 Mar 2012 15:40:42 -0700 (PDT)
Received: from nostrum.com (nostrum-pt.tunnel.tserv2.fmt.ipv6.he.net [IPv6:2001:470:1f03:267::2]) by ietfa.amsl.com (Postfix) with ESMTP id EACCB21E8037 for <wgchairs@ietf.org>; Tue, 13 Mar 2012 15:40:41 -0700 (PDT)
Received: from unexplicable.local (pool-71-170-125-181.dllstx.fios.verizon.net [71.170.125.181]) (authenticated bits=0) by nostrum.com (8.14.3/8.14.3) with ESMTP id q2DMeYUK094544 (version=TLSv1/SSLv3 cipher=DHE-RSA-CAMELLIA256-SHA bits=256 verify=NO); Tue, 13 Mar 2012 17:40:35 -0500 (CDT) (envelope-from rjsparks@nostrum.com)
Message-ID: <4F5FCCE2.4020902@nostrum.com>
Date: Tue, 13 Mar 2012 17:40:34 -0500
From: Robert Sparks <rjsparks@nostrum.com>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.6; rv:10.0.2) Gecko/20120216 Thunderbird/10.0.2
MIME-Version: 1.0
To: Warren Kumari <warren@kumari.net>
Subject: Re: Easier access to diffs, etc.
References: <25477_1331633317_q2DA8Z8h025995_4F5F1CA0.1010602@cisco.com> <1331658531.3570.122.camel@destiny.pc.cs.cmu.edu> <4F5F82C7.40401@alum.mit.edu> <310097CF-365A-40A4-9F89-2F48FC253FEF@kumari.net>
In-Reply-To: <310097CF-365A-40A4-9F89-2F48FC253FEF@kumari.net>
Content-Type: text/plain; charset="windows-1252"; format="flowed"
Content-Transfer-Encoding: 8bit
Received-SPF: pass (nostrum.com: 71.170.125.181 is authenticated by a trusted mechanism)
Cc: wgchairs@ietf.org
X-BeenThere: wgchairs@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Working Group Chairs <wgchairs.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/wgchairs>, <mailto:wgchairs-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/wgchairs>
List-Post: <mailto:wgchairs@ietf.org>
List-Help: <mailto:wgchairs-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/wgchairs>, <mailto:wgchairs-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 13 Mar 2012 22:40:42 -0000

Popping back in the thread several messages:

I agree that the announcement / revised-id messages should point to 
better places.

Warren's redirect is interesting. I've seen a suggestion that stopped 
just short of asking that
we configure www.ietf.org to do exactly that kind of redirect on 
/id/<blah>. That would
produce unexpected results.

One thing to keep in mind -  What if you really are looking for the .txt 
version of the document
(to feed into some other tool for instance). What link do you use?

Warren - Your plugin probably does the right thing, but if you haven't 
tested it already you might want
to check - if you have the default you point to below set to 
datatracker.ietf.org, does the right thing
happen when you click the "plain text" link in the first block of a 
datatracker's main view for a document?

RjS


On 3/13/12 3:10 PM, Warren Kumari wrote:
> On Mar 13, 2012, at 11:24 AM, Paul Kyzivat wrote:
>
>> On a related note, I've been wishing that the I-D Action announcement messages provided more convenient access to info about the draft.
>> A link to the diff with the previous version would be nice,
>> as would a link to the html version of the document in the tools area (which in turn has links to all sorts of renditions of the doc.)
>>
>> I find that the link that is currently provided is rarely the one I want, so I'm always having to copy the name, and then search for the form I want. Its easier to just click. :-)
>>
> It you use Chrome, I have written an extension that does jus this…
> It is linked to from the Tools page (http://tools.ietf.org/), or a direct link: https://chrome.google.com/webstore/detail/aiccdpabeagpjcebilebhlifplfkinao
>
> This simply watches for a URL of the form http://www.ietf.org/id/foo-04.txt and replaces it with http://tools.ietf/org/html/foo (or, if you change the default in the options page, datatracker.ietf.org).
>
>
> W
>
>
>
>
>
>> 	Thanks,
>> 	Paul
>>
>> On 3/13/12 1:08 PM, Jeffrey Hutzelman wrote:
>>> On Tue, 2012-03-13 at 11:08 +0100, Benoit Claise wrote:
>>>> Dear all,
>>>>
>>>> I'm wondering how to do, with the IETF tools, a diff between a WG
>>>> document "RFC bis" and the "RFC" in the following example:
>>>>
>>>>       1. RFC 5101 was published
>>>>       2. And individual draft was published to update it
>>>> http://tools.ietf.org/html/draft-claise-ipfix-protocol-rfc5101bis-02
>>>>       3.
>>>> http://tools.ietf.org/html/draft-ietf-ipfix-protocol-rfc5101bis-01 was
>>>> accepted as a WG document
>>>>
>>>> The tools
>>>> (http://tools.ietf.org/html/draft-ietf-ipfix-protocol-rfc5101bis-01)
>>>> allows the diffs between the 2. and 3.. And I would like the automatic
>>>> diff between 1. and .3
>>>>
>>>> Any other ways than loading the different versions in
>>>> http://www.ietf.org/tools/rfcdiff/?
>>> As you probably know, the tools page for an internet-draft, like
>>> http://tools.ietf.org/html/draft-ietf-ipfix-protocol-rfc5101bis-01
>>> includes links for jumping from one version to the next, and for showing
>>> the differences between the version you're viewing and the previous
>>> version.  When one document succeeds another, such as a WG document
>>> replacing an individual one or, in this case, the individual document
>>> being the start of a revision of RFC5101, those links inlcude the
>>> ability to jump from one document to the next, and to compare the first
>>> version of one document with the last version of the document before it.
>>>
>>> So, if you go to the page for draft-claise-ipfix-protocol-rfc5101bis-00
>>> and click the "Diff1" link, you'll see differences in that document
>>> since RFC5101.
>>>
>>> As far as I know, there is no "friendly" way to click on something and
>>> see differences between two documents that are not immediately adjacent
>>> versions.  However, you can fairly easily edit the URL to get what you
>>> want.  Simply bring up the diff page for the later document, and add
>>> "&url1=XXX" to the end of the URL, where XXX is the document you want to
>>> compare against.  Acceptable forms include draft-foo-bar-00 and rfcXXXX.
>>>
>>> So, to see the differences between the most recent rfc5101bis and the
>>> original rfc5101, try this:
>>>
>>>
>>> http://tools.ietf.org/rfcdiff?url2=draft-ietf-ipfix-protocol-rfc5101bis-01.txt&url1=rfc5101
>>>
>>> -- Jeff
>>>
>>>
> --
> Don't be impressed with unintelligible stuff said condescendingly.
>      -- Radia Perlman.
>
>
>
>
>