IETF Logo Mail Archive

Re: [Trans] Draft agenda

Phillip Hallam-Baker <hallam@gmail.com> Tue, 25 February 2014 12:36 UTC

Return-Path: <hallam@gmail.com>
X-Original-To: trans@ietfa.amsl.com
Delivered-To: trans@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 492461A06CC for <trans@ietfa.amsl.com>; Tue, 25 Feb 2014 04:36:27 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.999
X-Spam-Level:
X-Spam-Status: No, score=-1.999 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, SPF_PASS=-0.001] autolearn=ham
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 LQu9WyZdBmgH for <trans@ietfa.amsl.com>; Tue, 25 Feb 2014 04:36:25 -0800 (PST)
Received: from mail-la0-x22d.google.com (mail-la0-x22d.google.com [IPv6:2a00:1450:4010:c03::22d]) by ietfa.amsl.com (Postfix) with ESMTP id 6E8DA1A03F0 for <trans@ietf.org>; Tue, 25 Feb 2014 04:36:25 -0800 (PST)
Received: by mail-la0-f45.google.com with SMTP id hr17so1198453lab.18 for <trans@ietf.org>; Tue, 25 Feb 2014 04:36:24 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=Du4qWlShtMwPRIK6LJoK113irVgrY4IWHMLx6kgSLUo=; b=xsy/lbg8DYL6CTqAR33N+IXMvwik1ZsBLxp2CY0Bw2P6K3RwuyzDCJnv0IQzc1050b 30j+S1RdpRzJNXu9bQXgJ9j+OCfKZlteNHULi9XoN3ZAhY1qSKP1PNLfK7VlTZjPK9yg mQVgDiqTbMR2ktye7TNzwSi7t+zKOxemDKA0I4AiCdc8wNgcsR2YENsRKsOkkntHz9rw zSXt4XUlfsdEk5kdf4XJCMHpWiJl5kM/2cyo0NBMb+nBkTQ3encZV46xTKja9Rep5COP VX+bbq5vr+htRFL1iRQnw2BPKoVNCSLibZYcUCKii+YlbWVWopcfCwj3s/JH4nVsAXsA BvlQ==
MIME-Version: 1.0
X-Received: by 10.152.44.225 with SMTP id h1mr141775lam.71.1393331783946; Tue, 25 Feb 2014 04:36:23 -0800 (PST)
Received: by 10.112.37.168 with HTTP; Tue, 25 Feb 2014 04:36:23 -0800 (PST)
In-Reply-To: <CABrd9STabJA4Fp75HfC7ORR1LQZT+q0DDuB61O0JGBOt31cpmQ@mail.gmail.com>
References: <53063600.4020102@gmail.com> <CALzYgEe0XrQdKDZN3_dwFLnM87+TXyYRMzj4ZGe5xKi-T_5V+g@mail.gmail.com> <530B86F6.5040201@gmail.com> <CABrd9SSpyw4nJ9t7X0WDeN+1MnhD+__-QXLOQXYs=h2JCUrwDg@mail.gmail.com> <CAMm+Lwj4XniVS_n+M3TmT_LM+P6H6HGgcnhMezUjnupKXzwwdg@mail.gmail.com> <CABrd9STabJA4Fp75HfC7ORR1LQZT+q0DDuB61O0JGBOt31cpmQ@mail.gmail.com>
Date: Tue, 25 Feb 2014 07:36:23 -0500
Message-ID: <CAMm+LwgT8MEG+Svr3zmMYYPrQNEXwtNPL0m7CjYFHKUAKKbfFQ@mail.gmail.com>
From: Phillip Hallam-Baker <hallam@gmail.com>
To: Ben Laurie <benl@google.com>
Content-Type: multipart/alternative; boundary="089e0160b7be09560004f33a560c"
Archived-At: http://mailarchive.ietf.org/arch/msg/trans/LCfNzCS44NU86qekhX11C2jSvBM
Cc: Melinda Shore <melinda.shore@gmail.com>, "trans@ietf.org" <trans@ietf.org>, Eran Messeri <eranm@google.com>
Subject: Re: [Trans] Draft agenda
X-BeenThere: trans@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: Public Notary Transparency working group discussion list <trans.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/trans>, <mailto:trans-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/trans/>
List-Post: <mailto:trans@ietf.org>
List-Help: <mailto:trans-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/trans>, <mailto:trans-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 25 Feb 2014 12:36:27 -0000

On Tue, Feb 25, 2014 at 2:23 AM, Ben Laurie <benl@google.com> wrote:

> On 24 February 2014 19:17, Phillip Hallam-Baker <hallam@gmail.com> wrote:
> > What exactly is a 'precertificate'. Either something is a cert or it is
> not.
> >
> > If it parses as an X.509v3 certificate then it is an X.509v3 certificate
> and
> > thats an end to it.
>
> Indeed, and a precertificate is a certificate. RFC 6962 defines what
> exactly it is.
>
> Not sure where you're going with this.


Ritual compliance with the existing PKIX spec.

Having two end entity certs with the same serial number is going to be a
problem.



> > If it is not then it is probably a CSR which would seem to be the
> existing
> > PKIX structure that fits its purpose.
>
> Not really - a precertificate needs to be signed.
>

CSRs are signed.

-- 
Website: http://hallambaker.com/

v2.23.0 | Report a Bug | By Email