IETF Logo Mail Archive

Re: [TLS] [pkix] New version of Multiple OCSP mode of Certificate

"Miller, Timothy J." <tmiller@mitre.org> Mon, 09 August 2010 13:03 UTC

Return-Path: <tmiller@mitre.org>
X-Original-To: tls@core3.amsl.com
Delivered-To: tls@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 5CCF53A6AD1; Mon, 9 Aug 2010 06:03:00 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.599
X-Spam-Level:
X-Spam-Status: No, score=-6.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
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 y0P6IeCeEts1; Mon, 9 Aug 2010 06:02:59 -0700 (PDT)
Received: from smtp-bedford.mitre.org (smtp-bedford.mitre.org [129.83.20.191]) by core3.amsl.com (Postfix) with ESMTP id 842203A68F6; Mon, 9 Aug 2010 06:02:58 -0700 (PDT)
Received: from smtp-bedford.mitre.org (localhost.localdomain [127.0.0.1]) by smtp-bedford.mitre.org (8.13.1/8.13.1) with ESMTP id o79D3V1Z015531; Mon, 9 Aug 2010 09:03:31 -0400
Received: from imchub2.MITRE.ORG (imchub2.mitre.org [129.83.29.74]) by smtp-bedford.mitre.org (8.13.1/8.13.1) with ESMTP id o79D3UIY015509; Mon, 9 Aug 2010 09:03:30 -0400
Received: from IMCMBX2.MITRE.ORG ([129.83.29.205]) by imchub2.MITRE.ORG ([129.83.29.74]) with mapi; Mon, 9 Aug 2010 09:03:30 -0400
From: "Miller, Timothy J." <tmiller@mitre.org>
To: 'Nicolas Williams' <Nicolas.Williams@oracle.com>, Peter Gutmann <pgut001@cs.auckland.ac.nz>
Date: Mon, 09 Aug 2010 09:03:29 -0400
Thread-Topic: [pkix] [TLS] New version of Multiple OCSP mode of Certificate
Thread-Index: Acs1mWMW4k5SIA01SrS/nkb9rbuKnQCKZHFA
Message-ID: <17FD76C1ECD0AB49817637E21809ABF908A316DF8A@IMCMBX2.MITRE.ORG>
References: <20100805183227.GT5213@oracle.com> <E1OhNP9-0002RW-10@wintermute02.cs.auckland.ac.nz> <20100806145134.GS5213@oracle.com>
In-Reply-To: <20100806145134.GS5213@oracle.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
acceptlanguage: en-US
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Cc: "pkix@ietf.org" <pkix@ietf.org>, "tls@ietf.org" <tls@ietf.org>
Subject: Re: [TLS] [pkix] New version of Multiple OCSP mode of Certificate
X-BeenThere: tls@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: "This is the mailing list for the Transport Layer Security working group of the IETF." <tls.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/tls>, <mailto:tls-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/tls>
List-Post: <mailto:tls@ietf.org>
List-Help: <mailto:tls-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/tls>, <mailto:tls-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 09 Aug 2010 13:03:00 -0000

>> What if it's an embedded device on a network with no DNS?

>Why would you use PKI in such a case, and why AIA??

>Let's be reasonable...  :)

Off the top of my head:

1) Regulatory requirements.

2) Because a symmetric key distribution infrastructure might be too hard in the specific environment.

3) Because commercial platforms usually don't grok keys without certs.

-- Tim

v2.23.0 | Report a Bug | By Email