From turners@ieca.com Wed Feb 5 06:04:19 2014 Return-Path: X-Original-To: smime@ietfa.amsl.com Delivered-To: smime@ietfa.amsl.com Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 8268E1A0150; Wed, 5 Feb 2014 06:04:19 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -1.9 X-Spam-Level: X-Spam-Status: No, score=-1.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9] 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 vpXS2es5uX4O; Wed, 5 Feb 2014 06:04:18 -0800 (PST) Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id 4B1731A0148; Wed, 5 Feb 2014 06:04:18 -0800 (PST) MIME-Version: 1.0 Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: 7bit From: "Sean Turner" To: turners@ieca.com X-Test-IDTracker: no X-IETF-IDTracker: 5.0.0 Auto-Submitted: auto-generated Precedence: bulk Message-ID: <20140205140418.6605.46720.idtracker@ietfa.amsl.com> Date: Wed, 05 Feb 2014 06:04:18 -0800 Cc: smime@ietf.org, sec-chairs@tools.ietf.org, wjottaway@qinetiq.com, draft-melnikov-smime-msa-to-mda@tools.ietf.org, iesg-secretary@ietf.org Subject: [smime] Publication has been requested for draft-melnikov-smime-msa-to-mda-02 X-BeenThere: smime@ietf.org X-Mailman-Version: 2.1.15 List-Id: SMIME Working Group List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 05 Feb 2014 14:04:19 -0000 Sean Turner has requested publication of draft-melnikov-smime-msa-to-mda-02 as Proposed Standard on behalf of the SEC working group. Please verify the document's state at http://datatracker.ietf.org/doc/draft-melnikov-smime-msa-to-mda/ From ietf-secretariat-reply@ietf.org Wed Feb 5 06:07:05 2014 Return-Path: X-Original-To: smime@ietfa.amsl.com Delivered-To: smime@ietfa.amsl.com Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id A858E1A015E for ; Wed, 5 Feb 2014 06:07:05 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -1.899 X-Spam-Level: X-Spam-Status: No, score=-1.899 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, TVD_SPACE_RATIO=0.001] 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 8kC_MywmiZIt; Wed, 5 Feb 2014 06:07:04 -0800 (PST) Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id 780911A00A2; Wed, 5 Feb 2014 06:07:04 -0800 (PST) MIME-Version: 1.0 Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: 7bit To: alexey.melnikov@isode.com, wjottaway@qinetiq.com, draft-melnikov-smime-msa-to-mda@tools.ietf.org, smime@ietf.org, stephen.farrell@cs.tcd.ie X-Test-IDTracker: no X-IETF-IDTracker: 5.0.0 Auto-Submitted: auto-generated Precedence: bulk Message-ID: <20140205140704.7477.76702.idtracker@ietfa.amsl.com> Date: Wed, 05 Feb 2014 06:07:04 -0800 From: IETF Secretariat X-Mailman-Approved-At: Wed, 05 Feb 2014 08:57:09 -0800 Subject: [smime] ID Tracker State Update Notice: X-BeenThere: smime@ietf.org X-Mailman-Version: 2.1.15 List-Id: SMIME Working Group List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 05 Feb 2014 14:07:05 -0000 IESG state changed to Last Call Requested from Publication Requested ID Tracker URL: http://datatracker.ietf.org/doc/draft-melnikov-smime-msa-to-mda/ From ietf-secretariat-reply@ietf.org Wed Feb 5 06:24:08 2014 Return-Path: X-Original-To: smime@ietfa.amsl.com Delivered-To: smime@ietfa.amsl.com Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 0251D1A0194 for ; Wed, 5 Feb 2014 06:24:08 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -1.9 X-Spam-Level: X-Spam-Status: No, score=-1.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9] 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 8_ew2e23DxkU; Wed, 5 Feb 2014 06:24:06 -0800 (PST) Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id 8DE9E1A0177; Wed, 5 Feb 2014 06:24:05 -0800 (PST) MIME-Version: 1.0 Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: 7bit To: alexey.melnikov@isode.com, wjottaway@qinetiq.com, draft-melnikov-smime-msa-to-mda@tools.ietf.org, smime@ietf.org, stephen.farrell@cs.tcd.ie X-Test-IDTracker: no X-IETF-IDTracker: 5.0.0 Auto-Submitted: auto-generated Precedence: bulk Message-ID: <20140205142405.9589.30408.idtracker@ietfa.amsl.com> Date: Wed, 05 Feb 2014 06:24:05 -0800 From: IETF Secretariat X-Mailman-Approved-At: Wed, 05 Feb 2014 08:57:09 -0800 Subject: [smime] ID Tracker State Update Notice: X-BeenThere: smime@ietf.org X-Mailman-Version: 2.1.15 List-Id: SMIME Working Group List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 05 Feb 2014 14:24:08 -0000 Last call has been made for draft-melnikov-smime-msa-to-mda and state has been changed to In Last Call ID Tracker URL: http://datatracker.ietf.org/doc/draft-melnikov-smime-msa-to-mda/ From paul.hoffman@vpnc.org Wed Feb 5 08:59:37 2014 Return-Path: X-Original-To: smime@ietfa.amsl.com Delivered-To: smime@ietfa.amsl.com Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 419031A019C for ; Wed, 5 Feb 2014 08:59:37 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: 0.153 X-Spam-Level: X-Spam-Status: No, score=0.153 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HELO_MISMATCH_COM=0.553, IXHASH_X1=1.5] 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 p_85cw1ARnYm for ; Wed, 5 Feb 2014 08:59:36 -0800 (PST) Received: from hoffman.proper.com (IPv6.Hoffman.Proper.COM [IPv6:2605:8e00:100:41::81]) by ietfa.amsl.com (Postfix) with ESMTP id 8CBA21A0159 for ; Wed, 5 Feb 2014 08:59:36 -0800 (PST) Received: from [10.20.30.90] (50-1-98-67.dsl.dynamic.sonic.net [50.1.98.67]) (authenticated bits=0) by hoffman.proper.com (8.14.7/8.14.7) with ESMTP id s15GdWfg027618 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NO) for ; Wed, 5 Feb 2014 09:39:33 -0700 (MST) (envelope-from paul.hoffman@vpnc.org) X-Authentication-Warning: hoffman.proper.com: Host 50-1-98-67.dsl.dynamic.sonic.net [50.1.98.67] claimed to be [10.20.30.90] Content-Type: text/plain; charset=us-ascii Mime-Version: 1.0 (Mac OS X Mail 7.1 \(1827\)) From: Paul Hoffman In-Reply-To: <20140205140418.6605.46720.idtracker@ietfa.amsl.com> Date: Wed, 5 Feb 2014 08:59:35 -0800 Content-Transfer-Encoding: quoted-printable Message-Id: <569490B7-B09B-459D-B171-92C469243AF5@vpnc.org> References: <20140205140418.6605.46720.idtracker@ietfa.amsl.com> To: smime@ietf.org X-Mailer: Apple Mail (2.1827) Subject: [smime] Discussion of draft-melnikov-smime-msa-to-mda X-BeenThere: smime@ietf.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: SMIME Working Group List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 05 Feb 2014 16:59:37 -0000 This document should be of obvious interest to anyone on this mailing = list. Please review it and send comments here to the list for = discussion. --Paul Hoffman= From hallam@gmail.com Wed Feb 5 09:42:03 2014 Return-Path: X-Original-To: smime@ietfa.amsl.com Delivered-To: smime@ietfa.amsl.com Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 50BEE1A011C for ; Wed, 5 Feb 2014 09:42:03 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -1.998 X-Spam-Level: X-Spam-Status: No, score=-1.998 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, LOTS_OF_MONEY=0.001, SPF_PASS=-0.001] 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 h1pJcuZc-N0k for ; Wed, 5 Feb 2014 09:42:00 -0800 (PST) Received: from mail-la0-x234.google.com (mail-la0-x234.google.com [IPv6:2a00:1450:4010:c03::234]) by ietfa.amsl.com (Postfix) with ESMTP id 304931A0122 for ; Wed, 5 Feb 2014 09:42:00 -0800 (PST) Received: by mail-la0-f52.google.com with SMTP id c6so576831lan.25 for ; Wed, 05 Feb 2014 09:41:58 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=Q5xfzoe6Ux+SLl09b12IqCgTGrFW3ql3Nqdy1oHIR3w=; b=qe4odeOeyTHk8JsahNWUz3ODQcVzRfMXUPoBlCdpxeBeOZfsHFaXly0tmZH+4D56T3 0Rp44DZwRUocotsTvUoEC6Vge9v4jyZJuxw9OJAkD9lg0V+6jqIya8e1UD6oeBhm9zIk VgtRhoR5MMgUh4EpOzM2pYHnQ0G1PuEnTfgB9S9Z3pYUy3PMOopV/0S51aWDrULnsvht GTCbrDF6LRYRegnYAWPUwNHF6oKFbZbv+TNWRpYiw+LaVhsdOtQyJePAFz4I8f0lrz7m BLV/FAAU9lfAgOggwrs4SlV7k9NsJ1wwY2GzVFx49mwALQ0b14Zz7gY/4TJ/gNOShMb0 v8aw== MIME-Version: 1.0 X-Received: by 10.112.211.233 with SMTP id nf9mr1838001lbc.50.1391622118579; Wed, 05 Feb 2014 09:41:58 -0800 (PST) Received: by 10.112.37.168 with HTTP; Wed, 5 Feb 2014 09:41:58 -0800 (PST) In-Reply-To: <569490B7-B09B-459D-B171-92C469243AF5@vpnc.org> References: <20140205140418.6605.46720.idtracker@ietfa.amsl.com> <569490B7-B09B-459D-B171-92C469243AF5@vpnc.org> Date: Wed, 5 Feb 2014 12:41:58 -0500 Message-ID: From: Phillip Hallam-Baker To: Paul Hoffman Content-Type: multipart/alternative; boundary=001a11c3c8a60a245704f1ac4692 Cc: smime@ietf.org Subject: Re: [smime] Discussion of draft-melnikov-smime-msa-to-mda X-BeenThere: smime@ietf.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: SMIME Working Group List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 05 Feb 2014 17:42:03 -0000 --001a11c3c8a60a245704f1ac4692 Content-Type: text/plain; charset=ISO-8859-1 On Wed, Feb 5, 2014 at 11:59 AM, Paul Hoffman wrote: > This document should be of obvious interest to anyone on this mailing > list. Please review it and send comments here to the list for discussion. > +1 One toplevel comment is that the only real challenge here is working around the constraints of the legacy installed base. That is part of what makes S/MIME so attractive. It is also what shots you in the foot. this is one of those cases where pushing for a big change or several changes at once might actually be easier than a small one. The difficulty of the deployment problem comes from the diversity and ambiguities of the deployed base. Getting signature to work right when the mail is received by an application or service that does the right thing is easy. The problem comes when the receiver does not understand what the right thing is. Working domain to domain is a good idea. We have infrastructures that work very well making domain level assertions. So lets imagine that Bank of Ethel, a major money center bank with $100 billion under management decides to send all their mail signed with S/MIME. That can't work today because if even 0.01% of that mail is received by faulty mail clients that give a terrible user experience, that is several million dollars worth of customer support calls. Now lets imagine that we work at the domain level. We have two infrastructures available: DNS allows us to make domain level statements about the Internet infrastructure, DNSSEC allows us to authenticate those statements. WebPKI allows us to make statements about the accountability of organizations and tie them to domains. Ideally I would want to use EV certificates with logotype data embedded to show the logo of the organization sending mail. DNS does not really help us very much when making statements about the sender of a message because the mail protocols don't really require the sender to have a DNS domain at all. On the receiver side, the DNS is the maypole around which the mail protocols dance. This is not an accident, email is the killer application that made the DNS necessary in the first place. Lets imagine that we have a statement from the MDA (i.e. receiver) that says 'please send all mail to me with group S/MIME signatures and/or encryption, I will make sure that all the necessary transformations get done to ensure that the receiving MUA gets the message in a form that it can understand.' The logical place to make that statement is actually an SMTP extension. But we would ideally want to authenticate that statement under STARTTLS and then tie the STATTLS credentials back to the DNS domain with something like DANE or WebPKI or both. I won't go into it here, but a lot of my objections to DNSSEC under the ICANN hierarchy, the fact that many registrars are crooks etc. etc. are answered if we tie DNSSEC authentication inside a domain to a certificate that is published in a Certificate Transparency log. That one statement allows us to unlock the deployment deadlock that makes progress in the S/MIME world so difficult. The changes that we then need on the protocol side are a few flags in the IMAP and SMTP services. The workings of these flags is essentially no different to the internationalization flags that already exist and Paul H. can probably tell us how these work. -- Website: http://hallambaker.com/ --001a11c3c8a60a245704f1ac4692 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable
On W= ed, Feb 5, 2014 at 11:59 AM, Paul Hoffman <paul.hoffman@vpnc.org&g= t; wrote:
This document should be of obvious interest = to anyone on this mailing list. Please review it and send comments here to = the list for discussion.

+1

One t= oplevel comment is that the only real challenge here is working around the = constraints of the legacy installed base. That is part of what makes S/MIME= so attractive. It is also what shots you in the foot.

this is one of those cases where pushing for a big chan= ge or several changes at once might actually be easier than a small one. Th= e difficulty of the deployment problem comes from the diversity and ambigui= ties of the deployed base.=A0


Getting signature to work right when the= mail is received by an application or service that does the right thing is= easy. The problem comes when the receiver does not understand what the rig= ht thing is.

Working domain to domain is a good idea. We have infras= tructures that work very well making domain level assertions. So lets imagi= ne that Bank of Ethel, a major money center bank with $100 billion under ma= nagement decides to send all their mail signed with S/MIME. That can't = work today because if even 0.01% of that mail is received by faulty mail cl= ients that give a terrible user experience, that is several million dollars= worth of customer support calls.

Now lets imagine that we work at the domain level. We h= ave two infrastructures available:

DNS allows us t= o make domain level statements about the Internet infrastructure, DNSSEC al= lows us to authenticate those statements.
WebPKI allows us to make statements about the accountability of organi= zations and tie them to domains.

Ideally I would w= ant to use EV certificates with logotype data embedded to show the logo of = the organization sending mail. DNS does not really help us very much when m= aking statements about the sender of a message because the mail protocols d= on't really require the sender to have a DNS domain at all.


On the receiver side, the DNS is the may= pole around which the mail protocols dance. This is not an accident, email = is the killer application that made the DNS necessary in the first place.

Lets imagine that we have a statement from the MDA (i.e= . receiver) that says 'please send all mail to me with group S/MIME sig= natures and/or encryption, I will make sure that all the necessary transfor= mations get done to ensure that the receiving MUA gets the message in a for= m that it can understand.' The logical place to make that statement is = actually an SMTP extension. But we would ideally want to authenticate that = statement under STARTTLS and then tie the STATTLS credentials back to the D= NS domain with something like DANE or WebPKI or both.

I won't go into it here, but a lot of my objections= to DNSSEC under the ICANN hierarchy, the fact that many registrars are cro= oks etc. etc. are answered if we tie DNSSEC authentication inside a domain = to a certificate that is published in a Certificate Transparency log.=A0


That one statement allows us to unlock t= he deployment deadlock that makes progress in the S/MIME world so difficult= . The changes that we then need on the protocol side are a few flags in the= IMAP and SMTP services. The workings of these flags is essentially no diff= erent to the internationalization flags that already exist and Paul H. can = probably tell us how these work.

--
Website: http://h= allambaker.com/
--001a11c3c8a60a245704f1ac4692-- From paul.hoffman@vpnc.org Thu Feb 6 10:15:35 2014 Return-Path: X-Original-To: smime@ietfa.amsl.com Delivered-To: smime@ietfa.amsl.com Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 8FAC71A044C for ; Thu, 6 Feb 2014 10:15:35 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -1.347 X-Spam-Level: X-Spam-Status: No, score=-1.347 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HELO_MISMATCH_COM=0.553] 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 L84IYVl3_oVJ for ; Thu, 6 Feb 2014 10:15:34 -0800 (PST) Received: from hoffman.proper.com (IPv6.Hoffman.Proper.COM [IPv6:2605:8e00:100:41::81]) by ietfa.amsl.com (Postfix) with ESMTP id 5E8061A03CD for ; Thu, 6 Feb 2014 10:15:34 -0800 (PST) Received: from [10.20.30.90] (50-1-98-67.dsl.dynamic.sonic.net [50.1.98.67]) (authenticated bits=0) by hoffman.proper.com (8.14.7/8.14.7) with ESMTP id s16HtSw0080567 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NO) for ; Thu, 6 Feb 2014 10:55:30 -0700 (MST) (envelope-from paul.hoffman@vpnc.org) X-Authentication-Warning: hoffman.proper.com: Host 50-1-98-67.dsl.dynamic.sonic.net [50.1.98.67] claimed to be [10.20.30.90] From: Paul Hoffman Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: quoted-printable Date: Thu, 6 Feb 2014 10:15:31 -0800 References: <20140206173436.11443.53939.idtracker@ietfa.amsl.com> To: smime@ietf.org Message-Id: <37BD4AAF-C86A-4003-AE61-19526328DED1@vpnc.org> Mime-Version: 1.0 (Mac OS X Mail 7.1 \(1827\)) X-Mailer: Apple Mail (2.1827) Subject: [smime] Fwd: Document Action: 'The application/cms media type' to Informational RFC (draft-turner-application-cms-media-type-08.txt) X-BeenThere: smime@ietf.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: SMIME Working Group List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 06 Feb 2014 18:15:35 -0000 Begin forwarded message: > From: The IESG > Subject: Document Action: 'The application/cms media type' to = Informational RFC (draft-turner-application-cms-media-type-08.txt) > Date: February 6, 2014 at 9:34:36 AM PST > To: IETF-Announce > Cc: RFC Editor > Reply-To: ietf@ietf.org >=20 > The IESG has approved the following document: > - 'The application/cms media type' > (draft-turner-application-cms-media-type-08.txt) as Informational RFC >=20 > This document has been reviewed in the IETF but is not the product of = an > IETF Working Group. >=20 > The IESG contact person is Stephen Farrell. >=20 > A URL of this Internet Draft is: > = http://datatracker.ietf.org/doc/draft-turner-application-cms-media-type/ >=20 >=20 >=20 >=20 > Technical Summary >=20 > This document registers the application/cms media types for use with > the corresponding CMS (Cryptographic Message Syntax) content types. >=20 > Working Group Summary >=20 > This document is an independent submission and not part of any WG.=20 >=20 >=20 > Document Quality >=20 > The draft was brought to the attention of the AppsAWG list, but got=20= > no response. It was also discussed on the media-types@ietf.org lisit.=20= > It didn't get any more notice in IETF Last Call, but is a boring = media=20 > type request. >=20 > Personnel >=20 > Paul Hoffman is the document shepherd. > Stephen Farrell is the responsible area director. >=20 From nobody Fri Feb 14 01:12:24 2014 Return-Path: X-Original-To: smime@ietfa.amsl.com Delivered-To: smime@ietfa.amsl.com Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 8AF861A01E4 for ; Fri, 14 Feb 2014 01:12:21 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -1.9 X-Spam-Level: X-Spam-Status: No, score=-1.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9] 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 YCzGx-dnCbCM; Fri, 14 Feb 2014 01:12:20 -0800 (PST) Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id 52C931A01EA; Fri, 14 Feb 2014 01:12:11 -0800 (PST) MIME-Version: 1.0 Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: 7bit From: internet-drafts@ietf.org To: alexey.melnikov@isode.com, wjottaway@qinetiq.com, draft-melnikov-smime-msa-to-mda@tools.ietf.org, smime@ietf.org, stephen.farrell@cs.tcd.ie, turners@ieca.com X-Test-IDTracker: no X-IETF-IDTracker: 5.0.0.p1 Auto-Submitted: auto-generated Precedence: bulk Message-ID: <20140214091211.14757.94800.idtracker@ietfa.amsl.com> Date: Fri, 14 Feb 2014 01:12:11 -0800 Archived-At: http://mailarchive.ietf.org/arch/msg/smime/qzmEcCoTdGLK7xB2TssO3ZZuFW0 Subject: [smime] New Version Notification - draft-melnikov-smime-msa-to-mda-03.txt X-BeenThere: smime@ietf.org X-Mailman-Version: 2.1.15 List-Id: SMIME Working Group List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 14 Feb 2014 09:12:21 -0000 A new version (-03) has been submitted for draft-melnikov-smime-msa-to-mda: http://www.ietf.org/internet-drafts/draft-melnikov-smime-msa-to-mda-03.txt The IETF datatracker page for this Internet-Draft is: https://datatracker.ietf.org/doc/draft-melnikov-smime-msa-to-mda/ Diff from previous version: http://www.ietf.org/rfcdiff?url2=draft-melnikov-smime-msa-to-mda-03 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. IETF Secretariat.