Re: [Trans] Martin Duke's No Objection on draft-ietf-trans-rfc6962-bis-39: (with COMMENT)

["Salz, Rich" <[e-mail]>]

Added this text:
+One way to get an OID arc, from which OIDs can be created, is to request
+a Private Enterprise Number from IANA, by completing the
+[registration form](https://pen.iana.org/pen/PenApplication.page).

At https://github.com/google/certificate-transparency-rfcs/pull/341


From: Martin Duke <[e-mail]>
Date: Thursday, July 29, 2021 at 6:33 PM
To: Alexey Melnikov <[e-mail]>
Cc: Rich Salz <[e-mail]>, "[e-mail]" <[e-mail]>
Subject: Re: [Trans] Martin Duke's No Objection on draft-ietf-trans-rfc6962-bis-39: (with COMMENT)

SGTM.

On Thu, Jul 29, 2021 at 3:32 PM Alexey Melnikov <[e-mail]<mailto:[e-mail]>> wrote:

On 29/07/2021 23:06, Salz, Rich wrote:


  *   So returning to my previous point, it seems rather heavyweight to update the IANA registry every time this happens, and it would arguably be efficient to assign a given operator a range so that these need not be deconflicted in perpetuity?

The registry is only for those organization that don’t have an OID arc of their own.  Getting one is pretty easy, one possibility is requesting it at https://pen.iana.org/pen/PenApplication.page<https://urldefense.com/v3/__https:/pen.iana.org/pen/PenApplication.page__;!!GjvTz_vk!HWyU0WX7goBE_4CUTk4VYHTqzjPMzA1bGSLCiBEEmLYytv5zZMbuiG29vSps$>
Which is First Come First Served registry, which is a rather low bar.
We could add that to the doc if you think it would be useful.  You get what’s called an “arc” and then you append .1, .2, .3.1, etc., as you want.
Indeed. Org arc only need to be allocated once and can be used for all sort of other protocols as well.