IETF Logo Mail Archive

Re: [Trans] [pkix] a question of cert (and OCSP) extension syntax

"Salz, Rich" <rsalz@akamai.com> Mon, 30 March 2015 16:18 UTC

Return-Path: <rsalz@akamai.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 1CC821A1AC2 for <trans@ietfa.amsl.com>; Mon, 30 Mar 2015 09:18:59 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.611
X-Spam-Level:
X-Spam-Status: No, score=-2.611 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01] 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 bocTh3cFTaQX for <trans@ietfa.amsl.com>; Mon, 30 Mar 2015 09:18:57 -0700 (PDT)
Received: from prod-mail-xrelay07.akamai.com (prod-mail-xrelay07.akamai.com [72.246.2.115]) by ietfa.amsl.com (Postfix) with ESMTP id 6CCD71A1ADC for <trans@ietf.org>; Mon, 30 Mar 2015 09:18:56 -0700 (PDT)
Received: from prod-mail-xrelay07.akamai.com (localhost.localdomain [127.0.0.1]) by postfix.imss70 (Postfix) with ESMTP id 673E3477E6; Mon, 30 Mar 2015 16:18:55 +0000 (GMT)
Received: from prod-mail-relay07.akamai.com (prod-mail-relay07.akamai.com [172.17.121.112]) by prod-mail-xrelay07.akamai.com (Postfix) with ESMTP id 585BA477E5; Mon, 30 Mar 2015 16:18:55 +0000 (GMT)
Received: from email.msg.corp.akamai.com (usma1ex-cas1.msg.corp.akamai.com [172.27.123.30]) by prod-mail-relay07.akamai.com (Postfix) with ESMTP id 5243E800A7; Mon, 30 Mar 2015 16:18:55 +0000 (GMT)
Received: from USMA1EX-DAG1MB2.msg.corp.akamai.com (172.27.123.102) by usma1ex-dag1mb4.msg.corp.akamai.com (172.27.123.104) with Microsoft SMTP Server (TLS) id 15.0.913.22; Mon, 30 Mar 2015 12:18:46 -0400
Received: from USMA1EX-DAG1MB2.msg.corp.akamai.com ([172.27.123.102]) by usma1ex-dag1mb2.msg.corp.akamai.com ([172.27.123.102]) with mapi id 15.00.0913.011; Mon, 30 Mar 2015 12:18:46 -0400
From: "Salz, Rich" <rsalz@akamai.com>
To: Massimiliano Pala <director@openca.org>, "trans@ietf.org" <trans@ietf.org>
Thread-Topic: [Trans] [pkix] a question of cert (and OCSP) extension syntax
Thread-Index: AQHQaOf6ve3CVsJiUk6+j2Vm8uDnCZ0xRm2AgAAH3ICAA+lyAA==
Date: Mon, 30 Mar 2015 16:18:46 +0000
Message-ID: <807d7643db7d451ea77a27966c7c571c@usma1ex-dag1mb2.msg.corp.akamai.com>
References: <9A043F3CF02CD34C8E74AC1594475C73AAFB6418@uxcn10-5.UoA.auckland.ac.nz> <C961CE34-4F55-4B11-86D7-1566B701911D@seantek.com> <5512C9C7.70202@comodo.com> <55159714.1070902@openca.org> <5515EB25.2090206@openca.org> <5515EFC5.6040908@gmail.com> <5515F65D.3000301@openca.org>
In-Reply-To: <5515F65D.3000301@openca.org>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [172.19.36.0]
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Archived-At: <http://mailarchive.ietf.org/arch/msg/trans/aaCH0w_ZuNwUEFuncTuJDo7TtfI>
Subject: Re: [Trans] [pkix] a question of cert (and OCSP) extension syntax
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: Mon, 30 Mar 2015 16:18:59 -0000

> I am sorry but I disagree. This should have been fixed long time ago - no
> Google private OIDs should have been put in a WG document in the first
> place.

Are you also bothered by the OID's in CMS S/MIME and other pkcs-derived RFC's?

At any rate,  Russ has already responded on the issue of existing OID's: leave as-is to avoid confusion and disrupting implementations.

	/r$

v2.23.0 | Report a Bug | By Email