IETF Logo Mail Archive

Re: [Acme] Registering a PEM Content-Type

Jacob Hoffman-Andrews <jsha@eff.org> Sun, 12 March 2017 19:54 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 15B131294EC for <acme@ietfa.amsl.com>; Sun, 12 Mar 2017 12:54:28 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -7.004
X-Spam-Level:
X-Spam-Status: No, score=-7.004 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, 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 7i9K8F2nrpee for <acme@ietfa.amsl.com>; Sun, 12 Mar 2017 12:54:27 -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 54D2B1294C7 for <acme@ietf.org>; Sun, 12 Mar 2017 12:54:27 -0700 (PDT)
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=AvQok9m4hKjZ0sON0vd4OYsnoxrCeWQNh3XPT8f81uM=; b=Izgovha28WWpnVF7HTLDbwTQV/xDGEs6Y7Vp+exMTs2hQfGN2+vacWFsd4YVtLjRqS69M8yRE1IELEjw+QIfncv7ENdzuNhvwmBwQoKjkdNoBxfC7YYrn3PfqxQwVhBOmsE5XALA859u1ZJGKj0Yn+Er62tYAYWo+C9aVGinVBM=;
Received: ; Sun, 12 Mar 2017 12:54:28 -0700
To: "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> <0af75256fcfd40b580b8e5696d8b0e00@usma1ex-dag1mb1.msg.corp.akamai.com>
From: Jacob Hoffman-Andrews <jsha@eff.org>
Message-ID: <5a413c90-e2d6-12c8-174f-540fed9b7a58@eff.org>
Date: Sun, 12 Mar 2017 12:54:25 -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: <0af75256fcfd40b580b8e5696d8b0e00@usma1ex-dag1mb1.msg.corp.akamai.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/hRO2rQWpRMcdqTuEPKVljDjfiI4>
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:54:28 -0000

On 03/12/2017 12:50 PM, Salz, Rich wrote:
> What about saying each certificate SHOULD be a signer on *A* preceding certificate?  This allows us to serve a single cert chain for both MD5  and SHA1, for example.  (Contrived examples of course.)
I think the current language (copied from TLS 1.3) conveys that, though
it's a bit subtle:

> Each following certificate SHOULD directly certify one preceding it.

v2.23.0 | Report a Bug | By Email