RE: A mailing list protocol

Dave Cridland <dave.cridland@isode.com> Thu, 06 December 2012 12:36 UTC

Return-Path: <dave.cridland@isode.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 9266021F8726 for <ietf@ietfa.amsl.com>; Thu, 6 Dec 2012 04:36:09 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level:
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id w2YEiA0iP7W2 for <ietf@ietfa.amsl.com>; Thu, 6 Dec 2012 04:36:09 -0800 (PST)
Received: from statler.isode.com (statler.isode.com [62.3.217.254]) by ietfa.amsl.com (Postfix) with ESMTP id C926621F86AA for <ietf@ietf.org>; Thu, 6 Dec 2012 04:36:08 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; t=1354797367; d=isode.com; s=selector; i=@isode.com; bh=SCqSUuabTQlBTBN9atTjOdZEtqDUZP2Dwylg72t2mFg=; h=From:Sender:Reply-To:Subject:Date:Message-ID:To:Cc:MIME-Version: In-Reply-To:References:Content-Type:Content-Transfer-Encoding: Content-ID:Content-Description; b=sd+yB4cnD6NLVpy2lA0rz1MTEebmxjOFQlG1Iwzdx2WByvfe1XUXtz6tr6ZqXgKLCLiKWq 6obfVXGwFlGGHxVo/k7Sro9/Jb5dHYCvqP6RwYINTU9rbvb1X0600f7aWCSbvApO0JSxCg BaOxRYKAPhZokrhFDYSdYdGK9hfugug=;
Received: from puncture (br.cridland.net [217.155.137.62]) by statler.isode.com (submission channel) via TCP with ESMTPSA id <UMCRNwBEKGTM@statler.isode.com>; Thu, 6 Dec 2012 12:36:07 +0000
X-SMTP-Protocol-Errors: PIPELINING
Subject: RE: A mailing list protocol
References: <20121204183432.3748.97064.idtracker@ietfa.amsl.com> <6.2.5.6.2.20121204121234.09360870@resistor.net> <2671C6CDFBB59E47B64C10B3E0BD59230338CCCD84@PRVPEXVS15.corp.twcable.com>
In-Reply-To: <2671C6CDFBB59E47B64C10B3E0BD59230338CCCD84@PRVPEXVS15.corp.twcable.com>
Message-Id: <7256.1354797367.419104@puncture>
Date: Thu, 06 Dec 2012 12:36:07 +0000
From: Dave Cridland <dave.cridland@isode.com>
To: "George\, Wes" <wesley.george@twcable.com>, IETF-Discussion <ietf@ietf.org>
MIME-Version: 1.0
Content-Type: text/plain; delsp="yes"; charset="us-ascii"; format="flowed"
X-Mailman-Approved-At: Thu, 06 Dec 2012 09:24:58 -0800
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: Thu, 06 Dec 2012 12:36:09 -0000

On Tue Dec  4 22:19:14 2012, George, Wes wrote:
> Is there an IETF standard format for handling inline quote replies?  
> Is it just not implemented in certain mail clients? 

RFC 3676? (As used here).

It is admittedly primarily useful in simple replies rather than  
quoting (and therefore attribution) from multiple parent messages;  
however that's by far the common case. A further specifcation to  
annotate attribution would be possible, though in principle that  
would be usefully based on the References field.

> Browbeating people into changing mail clients will be less than  
> effective, but something that systematically makes it easier to see  
> who is responsible for what comment in a multi-person thread  
> regardless of source email client would be welcome. While we're at  
> it, we could maybe implement a fix for the common problem of  
> mangled subject lines that make it very difficult to sort by  
> thread, and add a server-side filter that removes the legal  
> bilgewater automatically added to some outgoing messages (example  
> will follow in this very message) before sending it to the rest of  
> the list recipients, etc.

I've not really had a problem with searching for the subject root, in  
general, but I'd be happy to agree despite inexperience with the  
issue that there are standards for reply-mangling of subjects and we  
should note that.

My more common problem is a lack of in-reply-to or references fields  
that I can use for in-thread navigation, which I find particularly  
useful.

In general, there are a number of technical standards and protocols  
which are useful, or essential, for IETF participation; documenting  
these in a single location would seem beneficial.

Dave.