Re: Use of private OIDs in WG (standard-track) documents

Sean Turner <turners@ieca.com> Mon, 30 March 2015 18:43 UTC

Return-Path: <turners@ieca.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 43F471AC3B6 for <ietf@ietfa.amsl.com>; Mon, 30 Mar 2015 11:43:44 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 2.007
X-Spam-Level: **
X-Spam-Status: No, score=2.007 tagged_above=-999 required=5 tests=[BAYES_20=-0.001, FSL_HELO_BARE_IP_2=1.675, IP_NOT_FRIENDLY=0.334, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001] autolearn=no
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 VdRZogh3vTTM for <ietf@ietfa.amsl.com>; Mon, 30 Mar 2015 11:43:43 -0700 (PDT)
Received: from gateway06.websitewelcome.com (gateway06.websitewelcome.com [69.93.35.3]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 5F31B1AC3B5 for <ietf@ietf.org>; Mon, 30 Mar 2015 11:43:43 -0700 (PDT)
Received: by gateway06.websitewelcome.com (Postfix, from userid 5007) id AB5E8C41753CD; Mon, 30 Mar 2015 13:43:42 -0500 (CDT)
Received: from gator3286.hostgator.com (gator3286.hostgator.com [198.57.247.250]) by gateway06.websitewelcome.com (Postfix) with ESMTP id 9BBB4C41753A0 for <ietf@ietf.org>; Mon, 30 Mar 2015 13:43:42 -0500 (CDT)
Received: from [96.231.227.6] (port=54734 helo=192.168.1.10) by gator3286.hostgator.com with esmtpsa (TLSv1:AES128-SHA:128) (Exim 4.82) (envelope-from <turners@ieca.com>) id 1Ycef0-0005b3-0f for ietf@ietf.org; Mon, 30 Mar 2015 13:43:42 -0500
Content-Type: text/plain; charset="windows-1252"
Mime-Version: 1.0 (Mac OS X Mail 7.3 \(1878.6\))
Subject: Re: Use of private OIDs in WG (standard-track) documents
From: Sean Turner <turners@ieca.com>
In-Reply-To: <20150328211906.GI17637@mournblade.imrryr.org>
Date: Mon, 30 Mar 2015 14:43:40 -0400
Content-Transfer-Encoding: quoted-printable
Message-Id: <89D53DE5-4C92-45EB-9C9C-599D9841EB2D@ieca.com>
References: <55163324.6030504@openca.org> <20150328211906.GI17637@mournblade.imrryr.org>
To: ietf@ietf.org
X-Mailer: Apple Mail (2.1878.6)
X-AntiAbuse: This header was added to track abuse, please include it with any abuse report
X-AntiAbuse: Primary Hostname - gator3286.hostgator.com
X-AntiAbuse: Original Domain - ietf.org
X-AntiAbuse: Originator/Caller UID/GID - [47 12] / [47 12]
X-AntiAbuse: Sender Address Domain - ieca.com
X-BWhitelist: no
X-Source-IP: 96.231.227.6
X-Exim-ID: 1Ycef0-0005b3-0f
X-Source:
X-Source-Args:
X-Source-Dir:
X-Source-Sender: (192.168.1.10) [96.231.227.6]:54734
X-Source-Auth: sean.turner@ieca.com
X-Email-Count: 4
X-Source-Cap: ZG9tbWdyNDg7ZG9tbWdyNDg7Z2F0b3IzMjg2Lmhvc3RnYXRvci5jb20=
Archived-At: <http://mailarchive.ietf.org/arch/msg/ietf/9BO42lfQhIz2HtY56d5rAI1DXGc>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 30 Mar 2015 18:43:44 -0000

On Mar 28, 2015, at 17:19, Viktor Dukhovni <ietf-dane@dukhovni.org> wrote:

> On Fri, Mar 27, 2015 at 11:50:44PM -0500, Massimiliano Pala wrote:
> 
>> I do not really feel
>> comfortable adopting OIDs that are under the control of a single
>> organization. Would this be a first case ?
> 
> I don't see any possibility of "control" of a leaf OID once it is
> assigned.  
> 
> All that organizations control s the issuing of new OIDS under
> particular prefixes, and their prerogative is basically limited to
> avoiding collisions with other people assigning OIDs under their
> respective prefixes.  Once you publish an OID as fit for a particular
> purpose, you cannot take it back.
> 
> So I see no risk here.  MIT's and Microsoft's OIDS are used in
> Kerberos, for example.  This has not and cannot cause any problems.

I’m with Victor and don’t see the issue.  We’ve got standards track RFCs with OIDs from NIST, Certicom, RSA, and “infosec” and those are just the ones I can come up with off the top of head.

spt