IETF Logo Mail Archive

Re: [Trans] Draft agenda

Ben Laurie <benl@google.com> Wed, 26 February 2014 11:29 UTC

Return-Path: <benl@google.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 E076B1A0270 for <trans@ietfa.amsl.com>; Wed, 26 Feb 2014 03:29:03 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.926
X-Spam-Level:
X-Spam-Status: No, score=-1.926 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FM_FORGED_GMAIL=0.622, RP_MATCHES_RCVD=-0.547, 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 lGyfI5_9ocZm for <trans@ietfa.amsl.com>; Wed, 26 Feb 2014 03:29:01 -0800 (PST)
Received: from mail-ve0-x22d.google.com (mail-ve0-x22d.google.com [IPv6:2607:f8b0:400c:c01::22d]) by ietfa.amsl.com (Postfix) with ESMTP id 018C71A0252 for <trans@ietf.org>; Wed, 26 Feb 2014 03:29:00 -0800 (PST)
Received: by mail-ve0-f173.google.com with SMTP id jw12so2007888veb.32 for <trans@ietf.org>; Wed, 26 Feb 2014 03:28:59 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=FGhgWj24lgqHdAEaonaomUdzt3qTy5ogit2wW0yz61U=; b=UB7t5Za6Oov6Osd55DaETodJtWQ+cvIvdQF5BtQzZXw38F/k6GhE3oJEICwvplHtRL eLJT6z30lcJZZhrMVFv0ajNmoruIDz9EQeulLvlvCLtf81edTSrO9unjJiP+PKJhYotr 9YkxrmX5dojMRsUP5CYs9g6D/OXSwinVyBksbRzWK9e5E0Qv68dryUnB2qirCaDPvIAX bQNeC/uJYnjAyXvFMkymsthEuwmq9KEGZTVoSsekPv18fo2MK3bcx1Vmvem3xRsnCVzg HJx5XwkXyibMFarJwm9XQvbguRy6wKUheq2hIy9Pm/J0AtHmP9kOrBCZQ3erap6FIKNc 8SdQ==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:in-reply-to:references:date :message-id:subject:from:to:cc:content-type; bh=FGhgWj24lgqHdAEaonaomUdzt3qTy5ogit2wW0yz61U=; b=gbSZHu0vbvQ8S+k4Y9CdxEal6cI72vuboPqqPBuiYz2VRgJv0TEKuA9B+CihKYqm6U +nDGtpcWb+3dhmAzayAJVIFOpzI34OAKMuO5VUL4kY3RGSr/7AOkdOjO1xwg/lB2YytW gbscSR+cMs/nIi01CN0rRvwgYifPZp57F9pLn5jn5d/eIHh4Fos29r3k5KNQCarlEO1p BGL9krERiNyHPBFVzkj5XP3MdVTniBDbdch8J2CzwGphOFtNiuCFsQg2UVEvrDQInWej mhj+/0d/0iM5c5Xo9HKrwesAdK2SOjEx9VtV/IlzVENTu5GlvDwzY+yZ75CovjSmt8pT Rp1A==
X-Gm-Message-State: ALoCoQkK+BwM+NVrTeujjXEFFQAAXWX3M+Cr25rEwVu7uDcTKE0VLaLQpWoGa5jTeYGKIRzYmkA+7EFx4A/ocNPfVVrc8+wJ6bO/b40HkxwTM51ajdJfuDi9quhpDS2Pa3jR7VXraXg5GaKep+nxZBvzkbZq0fyYLkwB1DtzNvOmDvGZFPhs5no0NrWp7leD4A1A4aksJoN2
MIME-Version: 1.0
X-Received: by 10.221.37.1 with SMTP id tc1mr357198vcb.32.1393414139594; Wed, 26 Feb 2014 03:28:59 -0800 (PST)
Received: by 10.52.230.105 with HTTP; Wed, 26 Feb 2014 03:28:59 -0800 (PST)
In-Reply-To: <CAMm+LwgT8MEG+Svr3zmMYYPrQNEXwtNPL0m7CjYFHKUAKKbfFQ@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> <CAMm+LwgT8MEG+Svr3zmMYYPrQNEXwtNPL0m7CjYFHKUAKKbfFQ@mail.gmail.com>
Date: Wed, 26 Feb 2014 11:28:59 +0000
Message-ID: <CABrd9STQQ69cPo3F5c22__aGbPAKV3AXnTFB47yd3s7+SQOpww@mail.gmail.com>
From: Ben Laurie <benl@google.com>
To: Phillip Hallam-Baker <hallam@gmail.com>
Content-Type: text/plain; charset="UTF-8"
Archived-At: http://mailarchive.ietf.org/arch/msg/trans/wAOevqKVfiYcCJjPs6_I-cYsFfs
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: Wed, 26 Feb 2014 11:29:04 -0000

On 25 February 2014 12:36, Phillip Hallam-Baker <hallam@gmail.com> wrote:
>
>
>
> 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.

Not for ritual compliance. Same serial number _and issuer_ is a
problem. CT does not require this.

>> > 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.

But not by the right key - i.e. a change of spec would be required. I
think you might be able to cram the missing fields into attributes in
PKCS#10, though (which would also require additional spec).

v2.23.0 | Report a Bug | By Email