IETF Logo Mail Archive

Re: [Curdle] New Version Notification for draft-schaad-curdle-oid-registry-00.txt

Russ Housley <housley@vigilsec.com> Wed, 10 May 2017 21:26 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 CB1F412EAD8 for <curdle@ietfa.amsl.com>; Wed, 10 May 2017 14:26:24 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.899
X-Spam-Level:
X-Spam-Status: No, score=-1.899 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001] 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 WYhNLVonxRLn for <curdle@ietfa.amsl.com>; Wed, 10 May 2017 14:26:23 -0700 (PDT)
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 B96C1128616 for <curdle@ietf.org>; Wed, 10 May 2017 14:26:23 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by mail.smeinc.net (Postfix) with ESMTP id 26E0B30050D for <curdle@ietf.org>; Wed, 10 May 2017 17:26:23 -0400 (EDT)
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 hZZ9dTU3K4xd for <curdle@ietf.org>; Wed, 10 May 2017 17:26:22 -0400 (EDT)
Received: from a860b60074bd.home (pool-108-45-101-150.washdc.fios.verizon.net [108.45.101.150]) by mail.smeinc.net (Postfix) with ESMTPSA id F24333004B6; Wed, 10 May 2017 17:26:21 -0400 (EDT)
From: Russ Housley <housley@vigilsec.com>
Message-Id: <DA715285-FE29-480D-9334-77604D4D92DA@vigilsec.com>
Content-Type: multipart/alternative; boundary="Apple-Mail=_5B0E6820-6F04-49B1-AD26-457B573EDF9F"
Mime-Version: 1.0 (Mac OS X Mail 10.3 \(3273\))
Date: Wed, 10 May 2017 17:26:22 -0400
In-Reply-To: <92705.1494427787@eng-mail01.juniper.net>
Cc: curdle <curdle@ietf.org>
To: "Mark D. Baushke" <mdb@juniper.net>
References: <149426463707.11242.13594573268237847336.idtracker@ietfa.amsl.com> <007b01d2c821$5f8eb670$1eac2350$@augustcellars.com> <CABkgnnXzpw_WuRJFptEME0kL=fmaRQkpFn4O7zQFPed3eThX4Q@mail.gmail.com> <20170509051032.GZ30306@kduck.kaduk.org> <CABkgnnXLws6SA4ppqtyDFLnVLHysvR4QGjf2_zXfV4=gKnxS6g@mail.gmail.com> <20170509055301.GB30306@kduck.kaduk.org> <CABcZeBNFUR+v5kY4DQjqsvKrE+cZ2O96Y4mmjoZNQb6V3wsKhg@mail.gmail.com> <2DD56D786E600F45AC6BDE7DA4E8A8C118BD8F66@eusaamb107.ericsson.se> <13876.1494379636@eng-mail01.juniper.net> <000501d2c988$e6c681f0$b45385d0$@augustcellars.com> <92705.1494427787@eng-mail01.juniper.net>
X-Mailer: Apple Mail (2.3273)
Archived-At: <https://mailarchive.ietf.org/arch/msg/curdle/HneKkG3FpUFKVavfqfgTE5cMIQw>
Subject: Re: [Curdle] New Version Notification for draft-schaad-curdle-oid-registry-00.txt
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: Wed, 10 May 2017 21:26:25 -0000

Mark:

>> I do not believe that this has historically been part of the IANA
>> mission.
> 
> How have OID assignments for RFC standards been handled in the past?

The closest example to this situation lead to the publication of RFC 7107.

   When the S/MIME Mail Security Working Group was chartered, an object
   identifier arc was donated by RSA Data Security for use by that
   working group.  This document describes the object identifiers that
   were assigned in that donated arc, transfers control of that arc to
   IANA, and establishes IANA allocation policies for any future
   assignments within that arc.

Russ

v2.23.0 | Report a Bug | By Email