Re: [Tools-discuss] Include mail archive permalinks in mailing list messages

Dave Crocker <dhc2@dcrocker.net> Wed, 26 June 2013 17:58 UTC

Return-Path: <dhc2@dcrocker.net>
X-Original-To: tools-discuss@ietfa.amsl.com
Delivered-To: tools-discuss@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id E6C2411E8115 for <tools-discuss@ietfa.amsl.com>; Wed, 26 Jun 2013 10:58:38 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.599
X-Spam-Level:
X-Spam-Status: No, score=-6.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
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 je3t2NBiahiz for <tools-discuss@ietfa.amsl.com>; Wed, 26 Jun 2013 10:58:27 -0700 (PDT)
Received: from sbh17.songbird.com (sbh17.songbird.com [72.52.113.17]) by ietfa.amsl.com (Postfix) with ESMTP id 426F511E8110 for <tools-discuss@ietf.org>; Wed, 26 Jun 2013 10:58:27 -0700 (PDT)
Received: from [10.58.167.33] (72-254-23-2.client.stsn.net [72.254.23.2]) (authenticated bits=0) by sbh17.songbird.com (8.13.8/8.13.8) with ESMTP id r5QHwNUE022354 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT); Wed, 26 Jun 2013 10:58:27 -0700
Message-ID: <51CB2BBA.4060402@dcrocker.net>
Date: Wed, 26 Jun 2013 10:58:18 -0700
From: Dave Crocker <dhc2@dcrocker.net>
Organization: Brandenburg InternetWorking
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:17.0) Gecko/20130509 Thunderbird/17.0.6
MIME-Version: 1.0
To: Carsten Bormann <cabo@tzi.org>
References: <1BFB4A37-5930-410D-A1D6-C1DD509F4DA5@tzi.org> <8D23D4052ABE7A4490E77B1A012B6307751ECD67@mbx-01.win.nominum.com> <51CB2740.7040108@dcrocker.net> <5F8F93DC-9C63-450B-9AF4-698D0DA164AB@tzi.org>
In-Reply-To: <5F8F93DC-9C63-450B-9AF4-698D0DA164AB@tzi.org>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.0 (sbh17.songbird.com [72.52.113.66]); Wed, 26 Jun 2013 10:58:27 -0700 (PDT)
Cc: "tools-discuss@ietf.org Discussion" <tools-discuss@ietf.org>
Subject: Re: [Tools-discuss] Include mail archive permalinks in mailing list messages
X-BeenThere: tools-discuss@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
Reply-To: dcrocker@bbiw.net
List-Id: IETF Tools Discussion <tools-discuss.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/tools-discuss>, <mailto:tools-discuss-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/tools-discuss>
List-Post: <mailto:tools-discuss@ietf.org>
List-Help: <mailto:tools-discuss-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/tools-discuss>, <mailto:tools-discuss-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 26 Jun 2013 17:58:39 -0000

On 6/26/2013 10:53 AM, Carsten Bormann wrote:
> On Jun 26, 2013, at 19:39, Dave Crocker <dhc2@dcrocker.net> wrote:
>
>> On 6/26/2013 10:17 AM, Ted Lemon wrote:
>>> On Jun 26, 2013, at 12:51 PM, Carsten Bormann <cabo@tzi.org> wrote:
>>>> Why doesn't each message carry its own permalink at the time I get it?
>>>
>>> This would certainly be a useful feature.
>> As I understand the current system architecture, there's a technical challenge to this.
>
> I know, the "why" was more of a rhetorical question.
>
> It is not something that can be implemented in an afternoon, but generating some form of per-mailing-list auto-incrementing serial during distribution that is then added to a database similar to the way Bjoern proposed to add message-ids to a database wouldn't be too hard.  Maybe two afternoons, including documentation :-).  Another afternoon to make the mail-archive HTML actually use those URIs.


I think it's a good thing to pursue.

When i posted my note, I hadn't seen the one that also cited a mapping 
mechanism, such as between a url based on message id and the underlying 
key into the archive database.  That's the sort of mechanism I meant.

I just wanted to make sure folk understood that it would require its 
own, special and additional mechanism.

In a different system design, one could imagine that the capability 
would essentially be free.  But we don't have that sort of integrated 
environment.


d/

-- 
Dave Crocker
Brandenburg InternetWorking
bbiw.net