Re: [Acme] Registering a PEM Content-Type

Jacob Hoffman-Andrews <jsha@eff.org> Sun, 12 March 2017 19:35 UTC

Return-Path: <jsha@eff.org>
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 1AE9E1293F4 for <acme@ietfa.amsl.com>; Sun, 12 Mar 2017 12:35:55 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -7.003
X-Spam-Level:
X-Spam-Status: No, score=-7.003 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, RCVD_IN_DNSWL_HI=-5, RCVD_IN_MSPIKE_H2=-0.001, RP_MATCHES_RCVD=-0.001, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=eff.org
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 b1-kxF8AmVZq for <acme@ietfa.amsl.com>; Sun, 12 Mar 2017 12:35:53 -0700 (PDT)
Received: from mail2.eff.org (mail2.eff.org [173.239.79.204]) (using TLSv1.2 with cipher DHE-RSA-AES128-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 9B2781293D6 for <acme@ietf.org>; Sun, 12 Mar 2017 12:35:53 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=eff.org; s=mail2; h=Content-Type:In-Reply-To:MIME-Version:Date:Message-ID:From:Cc:References:To:Subject; bh=PvtSeScL3bSgr377OvbkU+i8ybbl4zG71f/4O8UI0dY=; b=KjolZoSz5yivya9i29XnvvR8lmhiOBSIvsH0kQS1Ir74jJqqMP2PSp2+v9apvr+cEw/hg1ejK+YQUnvs3xqd1McYA/A+rzu0DpACLuQPbdTMEsMDMkpZZb47YhEqEwbCXYA/HgKKNh+6qReMTzdj8yvkZ9lXAJubiE4+8UEBm8E=;
Received: ; Sun, 12 Mar 2017 12:35:54 -0700
To: Clint Wilson <clint.t.wilson@gmail.com>, "Salz, Rich" <rsalz@akamai.com>, Richard Barnes <rlb@ipv.sx>, Daniel McCarney <cpu@letsencrypt.org>
References: <9baa4aca-120c-4ce8-b118-68dca3917f57@eff.org> <CAKnbcLjUjvi5L=bHrj57PE-CqBcms9Fq-JwXNg=82fzXc=OomQ@mail.gmail.com> <CAL02cgQwa=dHouxS2n+NTi82P=4N6YGt_fCGSHinKdK1f1e96Q@mail.gmail.com> <cd6eea24-8234-50f8-2843-18299fcf1f6d@eff.org> <937ffb4e61f745fd844e2c5a04ce26b5@usma1ex-dag1mb3.msg.corp.akamai.com> <CAJ=cBg2x==e9-UZ_4XTPEjvmcdWJwOAyp8C9MrYrwVqLOEF+QA@mail.gmail.com>
From: Jacob Hoffman-Andrews <jsha@eff.org>
Message-ID: <7224f87c-996a-1ab4-1656-204d8067f885@eff.org>
Date: Sun, 12 Mar 2017 12:35:50 -0700
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:45.0) Gecko/20100101 Thunderbird/45.7.0
MIME-Version: 1.0
In-Reply-To: <CAJ=cBg2x==e9-UZ_4XTPEjvmcdWJwOAyp8C9MrYrwVqLOEF+QA@mail.gmail.com>
Content-Type: multipart/alternative; boundary="------------DBFFC8AC9166ED620F7B6C39"
Received-SPF: skipped for local relay
Archived-At: <https://mailarchive.ietf.org/arch/msg/acme/_E_12wPZA-v73JrTyZp14x5HqdE>
Cc: "acme@ietf.org" <acme@ietf.org>
Subject: Re: [Acme] Registering a PEM Content-Type
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: Sun, 12 Mar 2017 19:35:55 -0000

I've got a PR adding application/pem-certificate-chain:
https://github.com/ietf-wg-acme/acme/pull/276.

Note that I chose "pem-certificate-chain" rather than "pem-cert-list",
because it has different semantics. A certificate chain MUST start with
an end-entity certificate, while a certificate list (which has no MIME
type defined at present) can have any type of certificates in any order.
For instance, it's common to have a list of trust anchors in PEM format
concatenated in a single file. That would be considered a "certificate
list" but not a "certificate chain."

What do you all think?

Thanks,
Jacob

On 02/16/2017 06:57 PM, Clint Wilson wrote:
>
> +1 for application/pem-cert-list.
>
>
> On Thu, Feb 16, 2017, 5:11 PM Salz, Rich <rsalz@akamai.com
> <mailto:rsalz@akamai.com>> wrote:
>
>     I think you need application/pem-cert-list, which is a collection
>     of PEM certificates as defined in RFC 7468.
>
>     Should be easy to add that as an appendix to the draft.
>
>     I suggest cert-list not chain, to show that no ordering is implied.
>
>     _______________________________________________
>     Acme mailing list
>     Acme@ietf.org <mailto:Acme@ietf.org>
>     https://www.ietf.org/mailman/listinfo/acme
>
>
>
> _______________________________________________
> Acme mailing list
> Acme@ietf.org
> https://www.ietf.org/mailman/listinfo/acme