Re: [Curdle] Adam Roach's No Objection on draft-schaad-curdle-oid-registry-02: (with COMMENT)

Russ Housley <housley@vigilsec.com> Fri, 26 January 2018 15:50 UTC

Return-Path: <housley@vigilsec.com>
X-Original-To: curdle@ietfa.amsl.com
Delivered-To: curdle@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id C4E0312DA05 for <curdle@ietfa.amsl.com>; Fri, 26 Jan 2018 07:50:19 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.9
X-Spam-Level:
X-Spam-Status: No, score=-1.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9] autolearn=ham autolearn_force=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 quBXrdejQ1vN for <curdle@ietfa.amsl.com>; Fri, 26 Jan 2018 07:50:18 -0800 (PST)
Received: from mail.smeinc.net (mail.smeinc.net [209.135.209.11]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 5C02512426E for <curdle@ietf.org>; Fri, 26 Jan 2018 07:50:18 -0800 (PST)
Received: from localhost (localhost [127.0.0.1]) by mail.smeinc.net (Postfix) with ESMTP id B3226300F61 for <curdle@ietf.org>; Fri, 26 Jan 2018 10:50:17 -0500 (EST)
X-Virus-Scanned: amavisd-new at mail.smeinc.net
Received: from mail.smeinc.net ([127.0.0.1]) by localhost (mail.smeinc.net [127.0.0.1]) (amavisd-new, port 10026) with ESMTP id yVC6m_9XxNhW for <curdle@ietf.org>; Fri, 26 Jan 2018 10:50:16 -0500 (EST)
Received: from new-host.home (pool-108-45-101-150.washdc.fios.verizon.net [108.45.101.150]) by mail.smeinc.net (Postfix) with ESMTPSA id 984FC300426; Fri, 26 Jan 2018 10:50:16 -0500 (EST)
Content-Type: text/plain; charset="us-ascii"
Mime-Version: 1.0 (Mac OS X Mail 10.3 \(3273\))
From: Russ Housley <housley@vigilsec.com>
In-Reply-To: <57a6ec44-624c-0aeb-1d87-411b10546d52@comodo.com>
Date: Fri, 26 Jan 2018 10:50:21 -0500
Cc: curdle@ietf.org
Content-Transfer-Encoding: quoted-printable
Message-Id: <62FD2C4E-8816-46F9-A2CB-C17FBACCF5A5@vigilsec.com>
References: <151683733787.15895.15630757079242805311.idtracker@ietfa.amsl.com> <009c01d3956e$95866370$c0932a50$@augustcellars.com> <85cc56f1-f50e-db71-042d-87f51b94ab4c@comodo.com> <FB22CBB8-B999-4439-A291-8FAA5C7482F0@vigilsec.com> <72beb5b5-5292-c1dd-b685-d21c3a5e0c20@comodo.com> <041E7976-0522-4C64-98D6-DED3DB482B47@vigilsec.com> <d52c0e14-b793-a745-0178-c652da78e8c2@comodo.com> <278F5125-51EA-4595-BBEE-285E84245DDC@vigilsec.com> <57a6ec44-624c-0aeb-1d87-411b10546d52@comodo.com>
To: Rob Stradling <rob.stradling@comodo.com>
X-Mailer: Apple Mail (2.3273)
Archived-At: <https://mailarchive.ietf.org/arch/msg/curdle/oWN6MWXBkE3ZDX4F9UOcpjrVCwM>
Subject: Re: [Curdle] Adam Roach's No Objection on draft-schaad-curdle-oid-registry-02: (with COMMENT)
X-BeenThere: curdle@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: "List for discussion of potential new security area wg." <curdle.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/curdle>, <mailto:curdle-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/curdle/>
List-Post: <mailto:curdle@ietf.org>
List-Help: <mailto:curdle-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/curdle>, <mailto:curdle-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 26 Jan 2018 15:50:20 -0000

> On Jan 26, 2018, at 10:35 AM, Rob Stradling <rob.stradling@comodo.com> wrote:
> 
> On 26/01/18 15:25, Russ Housley wrote:
>> Rob:
>>> 
>>>> The point of making the IANA registry is so that other groups, even ones that are not chartered yet, can get short OIDs when they need them.
>>> 
>>> Oh, so is this document intended to cover all OIDs and OID ranges under the 1.3.101 arc that have been donated to the IETF by Symantec/DigiCert?
>> They reserved 0-99 for themselves.
>> They offered 100-127 for the IETF.  My understanding is that the desire was to support curves 25519 and 448.
>> They reserved 128 and up for themselves.
>>> If so, please could we add to this document the OIDs and OID ranges that Symantec/DigiCert have donated to the TRANS WG?
>> Was this part of the same arc?
> 
> Yes.  Some in the "0-99" range, and some in the "128 and up" range.

This document could be adjusted to include other parts of the arc, or the TRANS WG could put forward a document to add to the IANA registry.

Russ