IETF Logo Mail Archive

[Acme] Registering a PEM Content-Type

Jacob Hoffman-Andrews <jsha@eff.org> Mon, 13 February 2017 21:51 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 47D5012998B for <acme@ietfa.amsl.com>; Mon, 13 Feb 2017 13:51:18 -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 tUKAfpASffk1 for <acme@ietfa.amsl.com>; Mon, 13 Feb 2017 13:51:16 -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 ABC79129984 for <acme@ietf.org>; Mon, 13 Feb 2017 13:51:16 -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:MIME-Version:Date:Message-ID:Subject:From:To; bh=X1SpbLCQ+AlTMGSsTVninaOv7qSjalVkK+CtMh/r6VA=; b=xZyZ+zf3PnAD83WGhTiDhWtWfB2G3rXbbJtBO1g3TqS2w1G9fTtiRIkO/501leZvt6CTbbFfEahaJxEZfQtvfaWSU5gPI650hyS7FoL1TzVjp/j2NfjLOKjdvqTWw2QCs6NuxH2XW1uLLVF/6qM9Hn93b5IJEdxyVgce7sWKXLE=;
Received: ; Mon, 13 Feb 2017 13:51:18 -0800
To: "acme@ietf.org" <acme@ietf.org>
From: Jacob Hoffman-Andrews <jsha@eff.org>
Message-ID: <9baa4aca-120c-4ce8-b118-68dca3917f57@eff.org>
Date: Mon, 13 Feb 2017 13:51:16 -0800
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:45.0) Gecko/20100101 Thunderbird/45.7.0
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
Received-SPF: skipped for local relay
Archived-At: <https://mailarchive.ietf.org/arch/msg/acme/BhpiZzP32toHpWYa716dyh7zxkg>
Subject: [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: Mon, 13 Feb 2017 21:51:18 -0000

>From the WGLC thread, Russ Housley said:

> Section 6.4.2 says:
>  The default format of the certificate is PEM (application/x-pem-file)
>  as specified by [RFC7468]. ... The client may request other formats by
>  including an Accept header in its request.  For example, the client
>  may use the media type application/pkix-cert to request the end-
>  entity certificate in DER format.
>
> RFC 7468 defines the textual encoding for certificates, but it does not define the application/x-pem-file media type.  I cannot find a registration for the application/x-pem-file media type.

This is a good point. Should we register x-pem-file as part of this RFC? Or come up with a new, more specific media type, like application/pem-certificate-chain?

v2.23.0 | Report a Bug | By Email