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

Stephan Bosch <stephan@rename-it.nl> Sun, 22 March 2015 21:15 UTC

Return-Path: <stephan@rename-it.nl>
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 759CE1A1B9A for <ietf-smtp@ietfa.amsl.com>; Sun, 22 Mar 2015 14:15:25 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.786
X-Spam-Level:
X-Spam-Status: No, score=0.786 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HELO_EQ_NL=0.55, HOST_EQ_NL=1.545, HTML_MESSAGE=0.001, J_CHICKENPOX_45=0.6, T_RP_MATCHES_RCVD=-0.01] autolearn=no
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 pWPt7pqSA7ib for <ietf-smtp@ietfa.amsl.com>; Sun, 22 Mar 2015 14:15:23 -0700 (PDT)
Received: from drpepper.rename-it.nl (drpepper.rename-it.nl [217.119.238.16]) (using TLSv1 with cipher AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id E30151A1BAE for <ietf-smtp@ietf.org>; Sun, 22 Mar 2015 14:15:21 -0700 (PDT)
Received: from klara.student.utwente.nl ([130.89.162.218]:49830 helo=[10.168.3.2]) by drpepper.rename-it.nl with esmtpsa (TLS1.0:DHE_RSA_AES_128_CBC_SHA1:16) (Exim 4.72) (envelope-from <stephan@rename-it.nl>) id 1YZnDJ-0004CM-0p; Sun, 22 Mar 2015 22:15:19 +0100
Message-ID: <550F30C9.30202@rename-it.nl>
Date: Sun, 22 Mar 2015 22:14:49 +0100
From: Stephan Bosch <stephan@rename-it.nl>
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:31.0) Gecko/20100101 Thunderbird/31.5.0
MIME-Version: 1.0
To: Alexey Melnikov <alexey.melnikov@isode.com>, ietf-smtp@ietf.org
References: <20150307202540.13358.58739.idtracker@ietfa.amsl.com> <550EE444.4040507@isode.com>
In-Reply-To: <550EE444.4040507@isode.com>
Content-Type: multipart/alternative; boundary="------------000303070706020607050007"
X-RenameIT-MailScanner-SpamScore: -2.3 (--)
X-RenameIT-MailScanner-SpamCheck: No, score=-2.3 required=5.0 tests=ALL_TRUSTED, BAYES_00, HTML_MESSAGE autolearn=ham version=3.3.1
Archived-At: <http://mailarchive.ietf.org/arch/msg/ietf-smtp/Z2SNmRiLJYimbOXwcDmFW9xSjpY>
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:15:25 -0000

Hi,

On 3/22/2015 4:48 PM, Alexey Melnikov wrote:
> Constructive feedback would be very much appreciated!
>

I think this document can benefit from a more extensive introduction. I
mainly like to know why a `clean separation of transaction-related state
from the message itself' is necessary. What can go wrong if it isn't
passed separately? What are the main benefits? What are the applications
where this is relevant? I can take a few guesses for things like keying
material, but the rationale for passing trace information like that is
much less obvious. I see some hints throughout the text, but I think
making this clear in the induction is important.

Also, what is the application of being able to pass IMAP flags in SMTP?
Normally, I wouldn't want to give the sender the ability to assign flags
directly. And how would these flags interact with Sieve imap4flags?

Regards,

Stephan.


> -------- Original Message --------
> Subject: 	I-D Action: draft-melnikov-smtp-metadata-00.txt
> Date: 	Sat, 07 Mar 2015 12:25:40 -0800
> From: 	internet-drafts@ietf.org
> Reply-To: 	internet-drafts@ietf.org
> To: 	<i-d-announce@ietf.org>
>
>
>
> A New Internet-Draft is available from the on-line Internet-Drafts directories.
>
>
>         Title           : Simple Mail Transfer Protocol extension for relaying Metadata
>         Author          : Alexey Melnikov
> 	Filename        : draft-melnikov-smtp-metadata-00.txt
> 	Pages           : 11
> 	Date            : 2015-03-07
>
> Abstract:
>    This memo defines an extension to the SMTP (Simple Mail Transfer
>    Protocol) service whereby message metadata (such as Trace header
>    fields, IMAP flags, Keying material, etc) can be transferred in
>    separate containers similar to BDAT (RFC 3030, SMTP CHUNKING)
>    command.  This allows clean separation of transaction related state
>    from the message itself.
>
>
> The IETF datatracker status page for this draft is:
> https://datatracker.ietf.org/doc/draft-melnikov-smtp-metadata/
>
> There's also a htmlized version available at:
> http://tools.ietf.org/html/draft-melnikov-smtp-metadata-00
>
>
> Please note that it may take a couple of minutes from the time of submission
> until the htmlized version and diff are available at tools.ietf.org.
>
> Internet-Drafts are also available by anonymous FTP at:
> ftp://ftp.ietf.org/internet-drafts/
>
> _______________________________________________
> I-D-Announce mailing list
> I-D-Announce@ietf.org
> https://www.ietf.org/mailman/listinfo/i-d-announce
> Internet-Draft directories: http://www.ietf.org/shadow.html
> or ftp://ftp.ietf.org/ietf/1shadow-sites.txt
>
>
>
>
> _______________________________________________
> ietf-smtp mailing list
> ietf-smtp@ietf.org
> https://www.ietf.org/mailman/listinfo/ietf-smtp