IETF Logo Mail Archive

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

Jim Schaad <ietf@augustcellars.com> Wed, 10 May 2017 20:10 UTC

Return-Path: <ietf@augustcellars.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 4F7F6129C5A for <curdle@ietfa.amsl.com>; Wed, 10 May 2017 13:10:40 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.001
X-Spam-Level:
X-Spam-Status: No, score=-2.001 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RP_MATCHES_RCVD=-0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=augustcellars.com
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 OOKhmJS1tFIr for <curdle@ietfa.amsl.com>; Wed, 10 May 2017 13:10:38 -0700 (PDT)
Received: from mail4.augustcellars.com (augustcellars.com [50.45.239.150]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 69998129649 for <curdle@ietf.org>; Wed, 10 May 2017 13:10:38 -0700 (PDT)
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Content-Language: en-us
DKIM-Signature: v=1; a=rsa-sha256; d=augustcellars.com; s=winery; c=simple/simple; t=1494447033; h=from:subject:to:date:message-id; bh=Jbw3CIVpbBrIFsyrTccFJw4Ysc0kmlsbm8h0JaQ7xY4=; b=PRvS0Q0o3kAsWJywbflc7wxJpqlBYx/m7/wcC4su6El1Nhwf/+dQ91E4+rTrl/k5YNulyqcw262 1KxPJIpdCyJG0bDPyDyTJMde/2USuOLQJHgKWwaNSBr9aCpqOYK6FXEu2ZbRPpMe8p58h2Dob/4ro /tOg2bEalOqhBXwJe/hGmbhmQa+SWtH3iBUYf9vsi4Rf9yAbqtw9PDTbUF/S478ujWZtBV8W7x6c1 2p2ID23RRjjgqI5i2fcS71gBUKlQdjFGfZRcxOcqTQQA4cbRJUQUv9mIWGqRTpvzEh1keuIxuuu+J c70B/cW7vGlLWlSSLKMJdDUMYzP93YJCeipw==
Received: from mail2.augustcellars.com (192.168.1.201) by mail4.augustcellars.com (192.168.1.153) with Microsoft SMTP Server (TLS) id 15.0.1263.5; Wed, 10 May 2017 13:10:33 -0700
Received: from Hebrews (24.21.96.37) by mail2.augustcellars.com (192.168.0.56) with Microsoft SMTP Server (TLS) id 15.0.1263.5; Wed, 10 May 2017 13:10:23 -0700
From: Jim Schaad <ietf@augustcellars.com>
To: mdb@juniper.net
CC: 'curdle' <curdle@ietf.org>
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>
In-Reply-To: <92705.1494427787@eng-mail01.juniper.net>
Date: Wed, 10 May 2017 13:10:43 -0700
Message-ID: <004e01d2c9c9$8290e8b0$87b2ba10$@augustcellars.com>
MIME-Version: 1.0
X-Mailer: Microsoft Outlook 16.0
Thread-Index: AQHJVRMoP3cq4mnmyrtsRHkX9DmppwI228pxAWt1TpUBWsHjHAN7FOQdAZi7CHQBRXVEwwHSbWjqAhDWZLYBJz7gxAIubzaEoWxuOnA=
X-Originating-IP: [24.21.96.37]
Archived-At: <https://mailarchive.ietf.org/arch/msg/curdle/VqVnSUQGReS9bs2EUyB040L3Rbk>
Subject: Re: [Curdle] FW: 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 20:10:40 -0000

I think what you are looking for is the ASN.1 module which is residing in
draft-ietf-curdle-pkix.  This is where the assignment is actually being
done.  The IANA work is really just booking to make sure we don't re-use an
OID value.

Jim

-----Original Message-----
From: mdb@juniper.net [mailto:mdb@juniper.net] 
Sent: Wednesday, May 10, 2017 7:50 AM
To: Jim Schaad <ietf@augustcellars.com>
Cc: Daniel Migault <daniel.migault@ericsson.com>; Eric Rescorla
<ekr@rtfm.com>; Benjamin Kaduk <kaduk@mit.edu>; Martin Thomson
<martin.thomson@gmail.com>; curdle <curdle@ietf.org>
Subject: Re: [Curdle] FW: New Version Notification for
draft-schaad-curdle-oid-registry-00.txt 

Jim Schaad <ietf@augustcellars.com> writes:

> 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?

MIBs do exist under the IANA.org site:

  https://www.iana.org/assignments/ianacharset-mib/ianacharset-mib

I know I have seen MIBs with a copyright of "The Internet Society" in the
past as well as the IANAifType-MIB.mib with types that are prefixed with the
'IANA' string and

       ORGANIZATION "IANA"
       CONTACT-INFO "        Internet Assigned Numbers Authority

                     Postal: ICANN
                             4676 Admiralty Way, Suite 330
                             Marina del Rey, CA 90292

                     Tel:    +1 310 823 9358
                     E-Mail: iana&iana.org"

inside of the various MIBs.

It seems imprudent for there not to be a machine readable record of the
1.3.101.100 .. 1.3.101.127 OIDs.

I sort of expect a section of this draft to have the OID assignments that
may be extracted.

Something along the lines of RFC 3560 perhaps?

id-X25519 OBJECT IDENTIFIER  ::=  { iso(1) dentified-organization(3)
  thawte(101) 110 }

id-X448 OBJECT IDENTIFIER  ::=  { iso(1) dentified-organization(3)
  thawte(101) 111 }
 
id-EdDSA25519 OBJECT IDENTIFIER  ::=  { iso(1) dentified-organization(3)
  thawte(101) 112 }

id-EdDS448 OBJECT IDENTIFIER  ::=  { iso(1) dentified-organization(3)
  thawte(101) 113 }

id-EdDSA25519-ph OBJECT IDENTIFIER  ::=  { iso(1) dentified-organization(3)
  thawte(101) 114 }

id-EdDS448-ph OBJECT IDENTIFIER  ::=  { iso(1) dentified-organization(3)
  thawte(101) 115 }

Safecurves-pkix-0  OBJECT IDENTIFIER  ::=  { iso(1)
dentified-organization(3)
   thawte(101) 120 }

along with all of the other book-keeping needed to deal with the reserved
for future sub-registry and unallocated 116 thru 119 and 121 thru 127
values.

If this is all wrong, please feel free to suggest the right way to do it.

	-- Mark

v2.23.0 | Report a Bug | By Email