IETF Logo Mail Archive

Re: [keyassure] Interpreting certificates (and summary)

Zack Weinberg <zack.weinberg@sv.cmu.edu> Wed, 23 February 2011 21:03 UTC

Return-Path: <zack.weinberg@gmail.com>
X-Original-To: keyassure@core3.amsl.com
Delivered-To: keyassure@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id D4B663A68C6 for <keyassure@core3.amsl.com>; Wed, 23 Feb 2011 13:03:12 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.977
X-Spam-Level:
X-Spam-Status: No, score=-2.977 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, FM_FORGED_GMAIL=0.622, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id cgHzp+Jw3+Hv for <keyassure@core3.amsl.com>; Wed, 23 Feb 2011 13:03:12 -0800 (PST)
Received: from mail-ww0-f44.google.com (mail-ww0-f44.google.com [74.125.82.44]) by core3.amsl.com (Postfix) with ESMTP id EC4AC3A6891 for <keyassure@ietf.org>; Wed, 23 Feb 2011 13:03:11 -0800 (PST)
Received: by wwb39 with SMTP id 39so1773583wwb.13 for <keyassure@ietf.org>; Wed, 23 Feb 2011 13:03:59 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:sender:in-reply-to:references:date :x-google-sender-auth:message-id:subject:from:to:cc:content-type; bh=g2kXWakV9MDMgxfSkr1mUK3h4ydYnY7rLIrsn2Ar1C8=; b=E7F//YSCTKx2joq4iOwgKCN23IPfoQIIUbtCYczUn+DYFS8jL6Cs1ceQwq5RGLgHbR nWbHT5C2b3jI16AkjmMdK1bC/ZVnIkSSljm3O0Fku1MzkDnaeAfs5Czhh+yDiETa1jDd UYmnBnn1wWz1GSLDH1y5Ni4MIuB0HsB3lCJTU=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:sender:in-reply-to:references:date :x-google-sender-auth:message-id:subject:from:to:cc:content-type; b=mN5xBgL1tIQQB2Bvo86qK4bC0E8lvXq+4sh1H5eMF7Cc15/2qVB/KQHZHIkyBbIb7F F6tk1vYbEJdSMWIIC2Qv4vJbNanZXsdXrHRoZVmhzYTng7P54mjHSYO84GAskFHsqq+t 9TVAUlmr22nv3O6hAY+OoH1JwhjgMgLLvnPD8=
MIME-Version: 1.0
Received: by 10.227.136.70 with SMTP id q6mr4100933wbt.165.1298495039123; Wed, 23 Feb 2011 13:03:59 -0800 (PST)
Sender: zack.weinberg@gmail.com
Received: by 10.227.155.85 with HTTP; Wed, 23 Feb 2011 13:03:58 -0800 (PST)
In-Reply-To: <201102232039.p1NKdXR2008868@fs4113.wdf.sap.corp>
References: <AANLkTi=-bGc1ws0VvrsudV55GRk6KasSsydtiWMTNyua@mail.gmail.com> <201102232039.p1NKdXR2008868@fs4113.wdf.sap.corp>
Date: Wed, 23 Feb 2011 13:03:58 -0800
X-Google-Sender-Auth: xjj8heUFDhDaFG2Ij9V8qQyFhZo
Message-ID: <AANLkTikXbsQuLRaaj54ZcH6=Be8JYZjEnXs5GkwHPKAa@mail.gmail.com>
From: Zack Weinberg <zack.weinberg@sv.cmu.edu>
To: mrex@sap.com
Content-Type: text/plain; charset="UTF-8"
Cc: keyassure@ietf.org, i.grok@comcast.net, Phillip Hallam-Baker <hallam@gmail.com>
Subject: Re: [keyassure] Interpreting certificates (and summary)
X-BeenThere: keyassure@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Key Assurance With DNSSEC <keyassure.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/keyassure>, <mailto:keyassure-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/keyassure>
List-Post: <mailto:keyassure@ietf.org>
List-Help: <mailto:keyassure-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/keyassure>, <mailto:keyassure-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 23 Feb 2011 21:03:13 -0000

Could we short-circuit this entire argument by deferring to the
protocol being secured for the certificate format?  Concretely,
wording like

      [...] The types defined in this document are:

         1 -- An end-entity certificate, in the wire format used by
the protocol being secured
         2 -- A certification authority's certificate, ditto

zw

v2.23.0 | Report a Bug | By Email