Re: [Acme] Add a special token parameter in ACME registration
Martin Thomson <martin.thomson@gmail.com> Wed, 17 August 2016 01:11 UTC
Return-Path: <martin.thomson@gmail.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 CCDA812D0CD for <acme@ietfa.amsl.com>; Tue, 16 Aug 2016 18:11:23 -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, FREEMAIL_FROM=0.001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.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 4Hh41t6bftFk for <acme@ietfa.amsl.com>; Tue, 16 Aug 2016 18:11:22 -0700 (PDT)
Received: from mail-qk0-x229.google.com (mail-qk0-x229.google.com [IPv6:2607:f8b0:400d:c09::229]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 4B6B212B01A for <acme@ietf.org>; Tue, 16 Aug 2016 18:11:22 -0700 (PDT)
Received: by mail-qk0-x229.google.com with SMTP id z190so56314121qkc.0 for <acme@ietf.org>; Tue, 16 Aug 2016 18:11:22 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=LlY3Ofaqj0mgyICD5ZNVG/ygpHRylgQNbDGYeUiEoeU=; b=xb+S7ZUNlBBgiTPDBSjeZ+AC0LxegBfXKXDg+VusQktXUuc+mo/kPxffqKbuQ8TrP8 p5CtzPfeVAmZAn+a1rwH7eZQ3Bn1Cz042Y7T7ND+Ft0VJsBi64ax0Lv7N2wdO18PT1q5 FCaU0zo+BpaUzVwzxllkScscDZZRnOUPuyfQ1BNH0UHs/0Oc0IokQQVv+HQB7L9ZDaAk PMsNmtMFxTJZjK7ciQ6nZWrmY61AHAuAhQ/+hQ5QMjFwbGXplKMPNficp4OxFVtj4gB8 srbKPfFwTrZLBD0RxOIvd65BgaQB+DPvOmd6dV+6U9zdcWTiGui8zEzACJDyKToDbdcn M5tw==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc; bh=LlY3Ofaqj0mgyICD5ZNVG/ygpHRylgQNbDGYeUiEoeU=; b=EjDCRgWpDj16iG95WeZHBSgKzyx9MQTkcT/R2C2AIDrT7lJkC6IeCcvm+KPTvcIsLU Z5Sez+THlXjtaTsCxT7V6uR4lJwjTeKVEq/3L0KM86quWCxrlVGFuYUfsJwwb40tybyO zu2Ol6JovS0ziz/5LBZPJR0vSDaijYU2t94OVJ3xcBPQuWKlKyuHL503tCihVc4DxR35 Ebixnt8ubaFb3tnIBOElNNjat/obWLE2K2RvBvP2bEnRQvMRF6dminQv+LYxXY8Hvxfc OwiQciw4zb1XFsSCGePSzdrB9bUdwNXwW6ae58WJ1Cr1unrHbJWkIhpOQ2yHTo/Ou1kX BNqw==
X-Gm-Message-State: AEkooutARckbJXVpdcXRract/UYEw+eYBCJijnDpvPvZWho4eZZ7QkFPMS5qb0/tebPGd2VojEvcdE0khqxG/A==
X-Received: by 10.55.75.76 with SMTP id y73mr45103064qka.12.1471396281446; Tue, 16 Aug 2016 18:11:21 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.140.22.146 with HTTP; Tue, 16 Aug 2016 18:11:20 -0700 (PDT)
In-Reply-To: <CAL02cgTedv63cgjxDf3eNWANnVSG1zDkDDzUHrv0XVHb5ooJWg@mail.gmail.com>
References: <236F64DDDC83C742A24E89E6E215CFC7E4CFB7@mx3.startssl.com> <CAObDDPAEaiWE0Apao_sWin2njhC+CjQuw1D07upTsn4=BQQZnQ@mail.gmail.com> <d729f81d-44a7-7e64-a528-a43df5e6dd69@eff.org> <010e01d1f7d0$dcd3c7a0$967b56e0$@startssl.com> <c81aa0ec-4d8b-8e9f-cba3-d6205e466e53@eff.org> <CAL02cgTedv63cgjxDf3eNWANnVSG1zDkDDzUHrv0XVHb5ooJWg@mail.gmail.com>
From: Martin Thomson <martin.thomson@gmail.com>
Date: Wed, 17 Aug 2016 11:11:20 +1000
Message-ID: <CABkgnnVUE+pSrxibP=P_O3LLrhVE63j4ZEWPR9VdcA_AA5zpSA@mail.gmail.com>
To: Richard Barnes <rlb@ipv.sx>
Content-Type: text/plain; charset="UTF-8"
Archived-At: <https://mailarchive.ietf.org/arch/msg/acme/tdj6uWnjK-1-rnA1rr0vog-NKFM>
Cc: "acme@ietf.org" <acme@ietf.org>, Jacob Hoffman-Andrews <jsha@eff.org>
Subject: Re: [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: Wed, 17 Aug 2016 01:11:24 -0000
On 17 August 2016 at 06:48, Richard Barnes <rlb@ipv.sx> wrote: > a. Infer the certificate type from the CSR. For example, if the Subject in > the CSR has (C, O, CN), infer that the applicant wants EV. > b. Have a field in the new-application request that the client can use to > indicate what type of certificate, e.g., {"certType": "ev"} to indicate EV. > c. Have a field in the new-application request that indicates which CA the > applicant would like to issue the certificate, e.g., {"ca": > "identifier-for-CA"}. Or have entirely separate ACME endpoints for the DV and EV CA. i.e., https://acme.example/dv will issue DV certs, and https://acme.example/ev will issue EV certs.
- Re: [Acme] Add a special token parameter in ACME … Andrew Ayer
- Re: [Acme] Add a special token parameter in ACME … Andy Ligg
- Re: [Acme] Add a special token parameter in ACME … Andy Ligg
- Re: [Acme] Add a special token parameter in ACME … Richard Barnes
- Re: [Acme] Add a special token parameter in ACME … Martin Thomson
- Re: [Acme] Add a special token parameter in ACME … Richard Barnes
- Re: [Acme] Add a special token parameter in ACME … Jacob Hoffman-Andrews
- Re: [Acme] Add a special token parameter in ACME … Andy Ligg
- Re: [Acme] Add a special token parameter in ACME … Andy Ligg
- Re: [Acme] Add a special token parameter in ACME … Jacob Hoffman-Andrews
- Re: [Acme] Add a special token parameter in ACME … J.C. Jones
- [Acme] Add a special token parameter in ACME regi… Andy Ligg