Re: [Acme] Draft authors -- please send a status

Alexey Melnikov <alexey.melnikov@isode.com> Sun, 15 July 2018 11:09 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 C20E6130F63 for <acme@ietfa.amsl.com>; Sun, 15 Jul 2018 04:09:10 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.952
X-Spam-Level:
X-Spam-Status: No, score=-0.952 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DATE_IN_PAST_12_24=1.049, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, SPF_PASS=-0.001] autolearn=no 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 onW7hXXYr3Fk for <acme@ietfa.amsl.com>; Sun, 15 Jul 2018 04:09:08 -0700 (PDT)
Received: from waldorf.isode.com (waldorf.isode.com [62.232.206.188]) by ietfa.amsl.com (Postfix) with ESMTP id 9CD28130E79 for <acme@ietf.org>; Sun, 15 Jul 2018 04:09:08 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; t=1531652948; d=isode.com; s=june2016; i=@isode.com; bh=8C6jrg9XS0Z9ci5A36MfGVI/MCY7dnAHChTwH1/KVhE=; 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=ZBJu/8QKlxQ7HoIZiVjnCzHVECxRDO+5B8dEktLpDZn+27lp69Msc7HzO2Tmzc2fk0aPp7 hCdYq7POKZ0AiBXvwneZEdjcyZeN8XjyAH+BX4/750tD/zFciFhGm56xUXp2C6vL8y1BwU Mue390K4ii2RCBjNz7qiv3sP7qwlAZM=;
Received: from [172.16.14.142] ((unknown) [66.171.165.154]) by waldorf.isode.com (submission channel) via TCP with ESMTPSA id <W0srUwAE9VGm@waldorf.isode.com>; Sun, 15 Jul 2018 12:09:07 +0100
X-SMTP-Protocol-Errors: NORDNS
To: Rich Salz <rsalz@akamai.com>, "acme@ietf.org" <acme@ietf.org>
References: <4DDCD470-6E18-4244-8420-EF7F8967AFFC@akamai.com>
From: Alexey Melnikov <alexey.melnikov@isode.com>
Openpgp: preference=signencrypt
Message-ID: <6adad93b-3ac4-3264-c9f2-9bd2a137f835@isode.com>
Date: Sat, 14 Jul 2018 14:19:25 +0100
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:52.0) Gecko/20100101 Thunderbird/52.9.1
In-Reply-To: <4DDCD470-6E18-4244-8420-EF7F8967AFFC@akamai.com>
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Language: en-US
Content-transfer-encoding: quoted-printable
Archived-At: <https://mailarchive.ietf.org/arch/msg/acme/xqnWcwTAQEiYt6A4aVdSBzg9fVs>
Subject: Re: [Acme] Draft authors -- please send a status
X-BeenThere: acme@ietf.org
X-Mailman-Version: 2.1.27
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: Sun, 15 Jul 2018 11:09:11 -0000

On 27/06/2018 16:57, Salz, Rich wrote:
> Can the authors of each draft please send a brief (one or two sentences
> is fine) status to the mailing list about their drafts?  Also indicate
> if you want WG time to present, talk about issues, etc. We are scheduled
> to meet during the Tuesday afternoon session, from 17:20-18:20 (last
> hour, after oauth).

Sadly I have a conflict with ACME, but here is status of my documents:

 [snip]

> draft-ietf-acme-email-smime-02

Details of the challenge email need to be flashed out. I am talking to
people who offered to co-edit the document.

> draft-ietf-acme-email-tls-04

I think this document is ready for WGLC. I have a couple of open issues,
but I don't think they prevent WGLC. The two issues are:

1) Is it possible to make ACME issue a single certificate for multiple
related services running on the same host, e.g. for IMAP and IMAPS or
for IMAP and POP3? A single certificate with DNS-ID would cover all
services automatically, but if we want to allow for a finegrainer
control using SRV-ID, there has to be a way to list all services that a
certificate has to cover. Is this problem worth solving? If yes, what is
the best way of doing this? One possible way of doing this is to
rename/extend "service" JWS header parameter to be a comma separated
list of services.

2) I would like the document to support LMTP (RFC 2033, effectively this
is a variant of SMTP, however in order to do this, I need to register
"lmtp" service and possibly a default port.

Best Regards,
Alexey