IETF Logo Mail Archive

[Acme] Add a special token parameter in ACME registration

Andy Ligg <andy@startssl.com> Mon, 15 August 2016 04:03 UTC

Return-Path: <andy@startssl.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 1F60812D662 for <acme@ietfa.amsl.com>; Sun, 14 Aug 2016 21:03:51 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -8.148
X-Spam-Level:
X-Spam-Status: No, score=-8.148 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_HI=-5, RP_MATCHES_RCVD=-1.247, SPF_PASS=-0.001] autolearn=ham autolearn_force=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 DHKWBKloAZ5v for <acme@ietfa.amsl.com>; Sun, 14 Aug 2016 21:03:50 -0700 (PDT)
Received: from mx3.startssl.com (mx3.startssl.com [124.251.21.41]) (using TLSv1 with cipher ECDHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 96FA712B00E for <Acme@ietf.org>; Sun, 14 Aug 2016 21:03:46 -0700 (PDT)
Received: from mx3.startssl.com ([fe80::bd1d:eeaf:a825:d540]) by mx3.startssl.com ([fe80::bd1d:eeaf:a825:d540%13]) with mapi id 14.02.0247.003; Mon, 15 Aug 2016 12:10:10 +0800
From: Andy Ligg <andy@startssl.com>
To: "Acme@ietf.org" <Acme@ietf.org>
Thread-Topic: Add a special token parameter in ACME registration
Thread-Index: AdH2qiLlvbBbPFlgSfuiGbJhgk1r0g==
Date: Mon, 15 Aug 2016 04:10:10 +0000
Message-ID: <236F64DDDC83C742A24E89E6E215CFC7E4CFB7@mx3.startssl.com>
Accept-Language: en-US, zh-CN
Content-Language: zh-CN
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [113.92.254.224]
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64
MIME-Version: 1.0
Archived-At: <https://mailarchive.ietf.org/arch/msg/acme/GBMkbbacl6lvMMGIsJrhIYUtek8>
Subject: [Acme] Add a special token parameter in ACME registration
X-BeenThere: acme@ietf.org
X-Mailman-Version: 2.1.17
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: Mon, 15 Aug 2016 04:03:51 -0000

Hi all,

StartCom plan to use ACME protocol for StartEncrypt, we need to identify the client's validation level, so the subscriber administration can generate a special token in the StartSSL.com account that send this token to the email address used in the ACME registration.

At the registration, user need to enter email and this token with the certificate to let the CA system know this customer's validation level. 
After the CA system receive the email, the token and signing certificate, CA system know what type of certificate we can issue to this client; if this client account is class 4 validated, then the client can get EV SSL certificate, not DV SSL.
please add this a parameter to the ACME protocol, thanks.

Best Regards,

Andy Ligg
StartCom

v2.23.0 | Report a Bug | By Email