IETF Logo Mail Archive

Re: [Acme] Registering a PEM Content-Type

Jacob Hoffman-Andrews <jsha@eff.org> Thu, 16 February 2017 23:01 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 BF1E5129455 for <acme@ietfa.amsl.com>; Thu, 16 Feb 2017 15:01:11 -0800 (PST)
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, RCVD_IN_DNSWL_HI=-5, 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 vTUt6zVS7ivi for <acme@ietfa.amsl.com>; Thu, 16 Feb 2017 15:01:10 -0800 (PST)
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 E148B124281 for <acme@ietf.org>; Thu, 16 Feb 2017 15:01:10 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=eff.org; s=mail2; h=Content-Transfer-Encoding:Content-Type:In-Reply-To:MIME-Version:Date:Message-ID:From:Cc:References:To:Subject; bh=7Cb2YjlrZ/F/ZgcLz1KFX/VjNTyWNx1pk3ENidMb2+M=; b=vhksvGSdKYM0GfVYpqLmJ3pT+x6pkky3tjYeV6KiT0VKka2kBYKNTuA5djiRslIzkhwNGNA/NZZcKL+Pv0SBem4v/g9E8TDaZxGbfVxOYqB3eLbB9+ArbRzmHTAyYXyV4PXBCCYx4t1Y1WAF+y+NBVXMyATapR9Omc8AimQ/dTc=;
Received: ; Thu, 16 Feb 2017 15:01:12 -0800
To: 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>
From: Jacob Hoffman-Andrews <jsha@eff.org>
Message-ID: <cd6eea24-8234-50f8-2843-18299fcf1f6d@eff.org>
Date: Thu, 16 Feb 2017 15:01:10 -0800
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: <CAL02cgQwa=dHouxS2n+NTi82P=4N6YGt_fCGSHinKdK1f1e96Q@mail.gmail.com>
Content-Type: text/plain; charset="windows-1252"
Content-Transfer-Encoding: 7bit
Received-SPF: skipped for local relay
Archived-At: <https://mailarchive.ietf.org/arch/msg/acme/w4w1Xksvr4yO7gHL62lpxHpG8dY>
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: Thu, 16 Feb 2017 23:01:12 -0000

On 02/16/2017 02:41 PM, Richard Barnes wrote:
> It seems simplest to me to just register "application/x-pem-file" with
> a pointer to RFC 7468.
Why that as opposed to application/pem-certificate-chain. x-pem-file has
some existing use but it is very small, and pem-certificate-chain is
much more specific. A pem file can contain any number of things: a
certificate, a private key, a CSR, etc.

v2.23.0 | Report a Bug | By Email