Re: [Acme] Adopt two email-related drafts

Alexey Melnikov <alexey.melnikov@isode.com> Fri, 09 June 2017 09:10 UTC

Return-Path: <alexey.melnikov@isode.com>
X-Original-To: acme@ietfa.amsl.com
Delivered-To: acme@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id B166F12956D for <acme@ietfa.amsl.com>; Fri, 9 Jun 2017 02:10:43 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2
X-Spam-Level:
X-Spam-Status: No, score=-2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_MESSAGE=0.001, RP_MATCHES_RCVD=-0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=isode.com
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 ZecoN53OxSsF for <acme@ietfa.amsl.com>; Fri, 9 Jun 2017 02:10:42 -0700 (PDT)
Received: from statler.isode.com (Statler.isode.com [62.232.206.189]) by ietfa.amsl.com (Postfix) with ESMTP id 0AE76126CD8 for <acme@ietf.org>; Fri, 9 Jun 2017 02:10:42 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; t=1496999440; d=isode.com; s=june2016; i=@isode.com; bh=9fXT3sWIP8cSSRQ9kP3T8XlI8O3fx/Mnd0Llfsbbx8w=; 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=l2fFDv9ui74qjLQQHQbu0+pksIm+JeaamjbD28dBJ/IM4euix8bRH98BMjmiWtHdjLln0N KWiQfWZOwpiWQMhxg2oMF8TM7dShdXtKezGeqB6CtJq5fpu6oTuxaFyqC7SdmbvCLlzZPF Cu0b1DSFosJ7IglUECGhkcO7ryCUdgo=;
Received: from [172.20.1.215] (dhcp-215.isode.net [172.20.1.215]) by statler.isode.com (submission channel) via TCP with ESMTPSA id <WTpmDwB2RwfS@statler.isode.com>; Fri, 9 Jun 2017 10:10:40 +0100
To: Russ Housley <housley@vigilsec.com>, Rich Salz <rsalz@akamai.com>
Cc: IETF ACME <acme@ietf.org>
References: <80560dd786e74f0c89f8858a7f1981d1@usma1ex-dag1mb1.msg.corp.akamai.com> <BC484323-CE4F-4CA2-AD20-A7640CE0DE42@vigilsec.com>
From: Alexey Melnikov <alexey.melnikov@isode.com>
Message-ID: <5c2648a6-0a42-fb78-aa0c-3f7d678ae19f@isode.com>
Date: Fri, 09 Jun 2017 10:10:10 +0100
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:52.0) Gecko/20100101 Thunderbird/52.1.1
In-Reply-To: <BC484323-CE4F-4CA2-AD20-A7640CE0DE42@vigilsec.com>
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="------------3F23D814245B2AC649CE6C81"
Content-Language: en-US
Archived-At: <https://mailarchive.ietf.org/arch/msg/acme/oXsunSPQ_ArhWo4KmUZuuRRFnY0>
Subject: Re: [Acme] Adopt two email-related drafts
X-BeenThere: acme@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: Automated Certificate Management Environment <acme.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/acme>, <mailto:acme-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/acme/>
List-Post: <mailto:acme@ietf.org>
List-Help: <mailto:acme-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/acme>, <mailto:acme-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 09 Jun 2017 09:10:44 -0000

Russ,

On 08/06/2017 20:50, Russ Housley wrote:

>> At the interim, we had strong consensus to adopt Alexsey’s draft (was 
>> one, is now two) on ACME challenges and certs for email services and 
>> users:
>> _https://datatracker.ietf.org/doc/draft-melnikov-acme-email-smime/_
>
> Why is the email address limited to all ASCII?  The LAMPS WG is almost 
> done with the document for a certificate to include internationalized 
> email addresses in certificates, so I would like to see them included 
> here too.

I've done the quickest job I could do to get something published before 
the ACME Interim. As email addresses require new ACME identity type 
anyway, supporting Internationalized Emails should be relatively 
straightforward.
So yes, I am happy to do that.
>
>> _https://datatracker.ietf.org/doc/draft-melnikov-acme-email-tls/_
>
> I hope we are not depended in any way on AUTH=SCRAM-SHA-1.

There is no obvious dependency on SCRAM at this point. If you are 
talking about example EHLO response, it includes all sort of other 
capabilities that are not relevant. I am happy to clarify this in the 
document.

Best Regards,
Alexey