Re: [ietf-smtp] Fwd: I-D Action: draft-melnikov-smtp-metadata-00.txt

Alexey Melnikov <alexey.melnikov@isode.com> Sun, 22 March 2015 21:52 UTC

Return-Path: <alexey.melnikov@isode.com>
X-Original-To: ietf-smtp@ietfa.amsl.com
Delivered-To: ietf-smtp@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id AC8101A1DBC for <ietf-smtp@ietfa.amsl.com>; Sun, 22 Mar 2015 14:52:47 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.011
X-Spam-Level:
X-Spam-Status: No, score=-2.011 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, 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 ScqSswfmrpiS for <ietf-smtp@ietfa.amsl.com>; Sun, 22 Mar 2015 14:52:46 -0700 (PDT)
Received: from waldorf.isode.com (ext-bt.isode.com [217.34.220.158]) by ietfa.amsl.com (Postfix) with ESMTP id 929211A1BD7 for <ietf-smtp@ietf.org>; Sun, 22 Mar 2015 14:52:46 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; t=1427061165; d=isode.com; s=selector; i=@isode.com; bh=YRE6xlxGvd9IoV9E2aiT0DoVaDLhKNVZ+PIRAqbSJcg=; 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=r0x2wntgJMrG85b1m1CK1bDgoAbKp7q72+/5Bq/z1dSz8j4jld1MDdLzsqJiXAnfyr3Xhj NuWnkD3FhuaRODLEPLQx4aPnl6JGAarIh1fYDnjIj4VhJB7hFx12GNhCRZASLSb6dkKnKf ZPGQ6frFLXIqmkQtZT8Z/ugi+Uk7eFE=;
Received: from [31.133.180.73] (dhcp-b449.meeting.ietf.org [31.133.180.73]) by waldorf.isode.com (submission channel) via TCP with ESMTPSA id <VQ85rABodVO3@waldorf.isode.com>; Sun, 22 Mar 2015 21:52:45 +0000
X-SMTP-Protocol-Errors: PIPELINING
Message-ID: <550F39AA.1090902@isode.com>
Date: Sun, 22 Mar 2015 21:52:42 +0000
From: Alexey Melnikov <alexey.melnikov@isode.com>
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:17.0) Gecko/20130620 Thunderbird/17.0.7
To: John R Levine <johnl@taugh.com>
References: <20150322201631.37192.qmail@ary.lan> <550F269C.10109@isode.com> <alpine.OSX.2.11.1503221606170.58010@dhcp-b142.meeting.ietf.org>
In-Reply-To: <alpine.OSX.2.11.1503221606170.58010@dhcp-b142.meeting.ietf.org>
MIME-Version: 1.0
Content-Type: text/plain; charset="ISO-8859-1"; format="flowed"
Content-Transfer-Encoding: 7bit
Archived-At: <http://mailarchive.ietf.org/arch/msg/ietf-smtp/1fFNQClFpj5SH1qz6yW_n52EG_A>
Cc: ietf-smtp@ietf.org
Subject: Re: [ietf-smtp] Fwd: I-D Action: draft-melnikov-smtp-metadata-00.txt
X-BeenThere: ietf-smtp@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: "Discussion of issues related to Simple Mail Transfer Protocol \(SMTP\) \[RFC 821, RFC 2821, RFC 5321\]" <ietf-smtp.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf-smtp>, <mailto:ietf-smtp-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf-smtp/>
List-Post: <mailto:ietf-smtp@ietf.org>
List-Help: <mailto:ietf-smtp-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf-smtp>, <mailto:ietf-smtp-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sun, 22 Mar 2015 21:52:47 -0000

On 22/03/2015 21:13, John R Levine wrote:
>>> So I think it would work fine if people implemented it, but unless
>>> there's a very concrete use case and people ready write and deploy
>>> those implementations, I wouldn't bother.
>> Fair comment, see use case examples in the document.
>
> I don't understand the benefit of putting the headers in a separate chunk.
See my reply to Stephan. I admit, I haven't decided myself how useful 
this might be.
> Setting suggested IMAP flags seems easy to do in a header if someone 
> wants to do that.
It bothers me that we keep minting new SMTP extensions. There was an 
SMTP/LMTP extension proposal for passing IMAP flags.
Stuff like DSN parameters could have been done as transaction state 
block 0. I know it is too late to change DSN, but I am wondering if 
doing something more generic would be useful.

The third use case is key material exchange a la DarkMail, but I will 
see if there is any interest in that idea.