Re: A mailing list protocol

Randall Gellens <randy@qti.qualcomm.com> Mon, 10 December 2012 02:28 UTC

Return-Path: <randy@qti.qualcomm.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 48D8321F8DB7 for <ietf@ietfa.amsl.com>; Sun, 9 Dec 2012 18:28:51 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.467
X-Spam-Level:
X-Spam-Status: No, score=-102.467 tagged_above=-999 required=5 tests=[AWL=0.132, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id HUjfovd7fp79 for <ietf@ietfa.amsl.com>; Sun, 9 Dec 2012 18:28:50 -0800 (PST)
Received: from sabertooth01.qualcomm.com (sabertooth01.qualcomm.com [65.197.215.72]) by ietfa.amsl.com (Postfix) with ESMTP id 9BFF021F8DA0 for <ietf@ietf.org>; Sun, 9 Dec 2012 18:28:50 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=qti.qualcomm.com; i=@qti.qualcomm.com; q=dns/txt; s=qcdkim; t=1355105537; x=1386641537; h=message-id:in-reply-to:references:date:to:from:subject: mime-version; bh=ZtF9J55sv8eq+J4IPE7ClPKJeXT7W35aK9Y2Yp8/xW0=; b=gXG2erPaP+XIzL8qvXqXqdy1rzc1Pl3gEweLbMI2PyXKQLoDiAPMmHM0 M/8JXNOh8ea9maQY+jQoDVQMIHBKjWXj5orH4YZKSOdJC4zGTpO8MiWNf Xwuf1dJ+hwlkIfIsMR2xI088DZA42sD/KAIV8Iut/kR0B3fEigQg4oK8F 8=;
X-IronPort-AV: E=McAfee;i="5400,1158,6921"; a="11210369"
Received: from ironmsg04-l.qualcomm.com ([172.30.48.19]) by sabertooth01.qualcomm.com with ESMTP; 09 Dec 2012 18:12:13 -0800
X-IronPort-AV: E=McAfee;i="5400,1158,6921"; a="356147438"
Received: from nasanexhc08.na.qualcomm.com ([172.30.39.7]) by Ironmsg04-L.qualcomm.com with ESMTP/TLS/RC4-SHA; 09 Dec 2012 18:28:46 -0800
Received: from [99.111.97.136] (172.30.39.5) by qcmail1.qualcomm.com (172.30.39.7) with Microsoft SMTP Server (TLS) id 14.2.318.4; Sun, 9 Dec 2012 18:28:46 -0800
Message-ID: <p06240601cceaf832172f@[99.111.97.136]>
In-Reply-To: <6.2.5.6.2.20121209105838.09574c88@resistor.net>
References: <2671C6CDFBB59E47B64C10B3E0BD59230338CCCD84@PRVPEXVS15.corp.twcable.co m> <20121206212400.10366.qmail@joyce.lan> <6.2.5.6.2.20121209105838.09574c88@resistor.net>
X-Mailer: Eudora for Mac OS X
Date: Sun, 9 Dec 2012 18:28:44 -0800
To: S Moonesamy <sm+ietf@elandsys.com>, <ietf@ietf.org>
From: Randall Gellens <randy@qti.qualcomm.com>
Subject: Re: A mailing list protocol
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
X-Random-Sig-Tag: 1.0b28
X-Originating-IP: [172.30.39.5]
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 10 Dec 2012 02:28:51 -0000

At 11:43 AM -0800 12/9/12, S Moonesamy wrote:

>  Dave Cridland mentioned RFC 3676 [3].  He pointed out that it 
> primarily useful in simple replies rather than quoting.

Just to clarify: Dave didn't say that RFC 3676 is not useful for 
quoting (indeed, quoting is one of it's main points).  Dave pointed 
out that RFC 3676 didn't include a mechanism to attribute each quote 
to a specific author, which is true.  Dave also pointed out that this 
attribution could in theory be accomplished by matching the quote 
level (which is included) to the 'References:' chain, although this 
would be fragile in practice because so few clients correctly 
implement 'References:'.

>  One of the problem he encounters is a lack of in-reply-to or 
> references fields that I can use for in-thread navigation.

Used for threading in general, not in-thread navigation (I'm not sure 
I understand the difference, but to me, threading is the ability to 
group together messages in a logical thread or discussion, while 
in-thread navigation would be the ability to jump around within a 
thread).

-- 
Randall Gellens
Opinions are personal;    facts are suspect;    I speak for myself only
-------------- Randomly selected tag: ---------------
With most men, life is like backgammon -- half skill and half luck.
                                           --Oliver Wendell Holmes