IETF Logo Mail Archive

Re: [Trans] Use of private OIDs in WG document

Russ Housley <housley@vigilsec.com> Mon, 30 March 2015 15:26 UTC

Return-Path: <housley@vigilsec.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 3AE051AD06B for <trans@ietfa.amsl.com>; Mon, 30 Mar 2015 08:26:48 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -101.9
X-Spam-Level:
X-Spam-Status: No, score=-101.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, USER_IN_WHITELIST=-100] 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 TaG_FXohdL0y for <trans@ietfa.amsl.com>; Mon, 30 Mar 2015 08:26:47 -0700 (PDT)
Received: from odin.smetech.net (x-bolt-wan.smeinc.net [209.135.219.146]) by ietfa.amsl.com (Postfix) with ESMTP id D4E401AC40C for <trans@ietf.org>; Mon, 30 Mar 2015 08:26:46 -0700 (PDT)
Received: from localhost (unknown [209.135.209.5]) by odin.smetech.net (Postfix) with ESMTP id 6AEEF9A404A; Mon, 30 Mar 2015 11:26:36 -0400 (EDT)
X-Virus-Scanned: amavisd-new at smetech.net
Received: from odin.smetech.net ([209.135.209.4]) by localhost (ronin.smeinc.net [209.135.209.5]) (amavisd-new, port 10024) with ESMTP id HRIk-vkxUNjI; Mon, 30 Mar 2015 11:26:15 -0400 (EDT)
Received: from [192.168.2.100] (pool-96-255-133-185.washdc.fios.verizon.net [96.255.133.185]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (No client certificate requested) by odin.smetech.net (Postfix) with ESMTP id 67B509A404D; Mon, 30 Mar 2015 11:26:15 -0400 (EDT)
Mime-Version: 1.0 (Apple Message framework v1085)
Content-Type: multipart/signed; boundary="Apple-Mail-88-597882501"; protocol="application/pkcs7-signature"; micalg="sha1"
From: Russ Housley <housley@vigilsec.com>
In-Reply-To: <55190F7B.4050001@comodo.com>
Date: Mon, 30 Mar 2015 11:26:04 -0400
Message-Id: <C501DE59-265D-46FB-9387-DAE4DA62EF14@vigilsec.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><2ebf955d99414800bfefd7a6edd814dd@usma1ex-dag1mb2.msg.corp.akamai.com><551638A0.5060007@openca.org> <D7A1D4A7-AF13-4116-B6D1-4AE71D55DF5D@vigilsec.com> <55190F7B.4050001@comodo.com>
To: Rob Stradling <rob.stradling@comodo.com>
X-Mailer: Apple Mail (2.1085)
Archived-At: <http://mailarchive.ietf.org/arch/msg/trans/8COKt67AaQDaT-bF463BeJvlb24>
Cc: trans@ietf.org
Subject: Re: [Trans] Use of private OIDs in WG document
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 15:26:48 -0000

The assignment of OIDs is handled by IANA.  See RFC 7299 for the official handover from the PKIX WG to IANA, which provides the policy for new OIDs in each part of the PKIX arc.

In addition, RFC 7120 provides the procedure for early assignments of IANA code points.  This applies to lots of different code points, not just OIDs in the PKIX arc.

Russ


On Mar 30, 2015, at 4:55 AM, Rob Stradling wrote:

> I am working on the assumption that "Russ, we're gonna need some OIDs for some cert/OCSP extensions - please can you assign some now, even though we haven't finished specifying the contents of these extensions yet?" would be greeted by a firm "No".  Hence why the draft is still using OIDs under Google's OID arc.

v2.23.0 | Report a Bug | By Email