IETF Logo Mail Archive

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

Stephen Farrell <stephen.farrell@cs.tcd.ie> Mon, 30 March 2015 19:50 UTC

Return-Path: <stephen.farrell@cs.tcd.ie>
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 240101ACCE4 for <ietf@ietfa.amsl.com>; Mon, 30 Mar 2015 12:50:01 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.21
X-Spam-Level:
X-Spam-Status: No, score=-4.21 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, T_RP_MATCHES_RCVD=-0.01] autolearn=ham
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 CE_luh11st3O for <ietf@ietfa.amsl.com>; Mon, 30 Mar 2015 12:50:00 -0700 (PDT)
Received: from mercury.scss.tcd.ie (mercury.scss.tcd.ie [134.226.56.6]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id BBE2B1ACCEB for <ietf@ietf.org>; Mon, 30 Mar 2015 12:49:59 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by mercury.scss.tcd.ie (Postfix) with ESMTP id 85559BEEF; Mon, 30 Mar 2015 20:49:58 +0100 (IST)
X-Virus-Scanned: Debian amavisd-new at scss.tcd.ie
Received: from mercury.scss.tcd.ie ([127.0.0.1]) by localhost (mercury.scss.tcd.ie [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Quu0wMWTy7om; Mon, 30 Mar 2015 20:49:57 +0100 (IST)
Received: from [10.87.48.73] (unknown [86.46.29.244]) by mercury.scss.tcd.ie (Postfix) with ESMTPSA id 75EE5BE3F; Mon, 30 Mar 2015 20:49:57 +0100 (IST)
Message-ID: <5519A8E3.3000605@cs.tcd.ie>
Date: Mon, 30 Mar 2015 20:49:55 +0100
From: Stephen Farrell <stephen.farrell@cs.tcd.ie>
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:31.0) Gecko/20100101 Thunderbird/31.5.0
MIME-Version: 1.0
To: Nico Williams <nico@cryptonector.com>, Sean Turner <turners@ieca.com>
Subject: Re: Use of private OIDs in WG (standard-track) documents
References: <55163324.6030504@openca.org> <20150328211906.GI17637@mournblade.imrryr.org> <89D53DE5-4C92-45EB-9C9C-599D9841EB2D@ieca.com> <20150330192905.GS10960@localhost>
In-Reply-To: <20150330192905.GS10960@localhost>
OpenPGP: id=D66EA7906F0B897FB2E97D582F3C8736805F8DA2; url=
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
Archived-At: <http://mailarchive.ietf.org/arch/msg/ietf/V7bbcY4A__HHZ3f4gzxsMCK1ZCc>
Cc: ietf@ietf.org
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 19:50:01 -0000


On 30/03/15 20:29, Nico Williams wrote:
>  that
> would effectively require having procedures for *early* IANA assignment
> of IETF OID arcs to upcoming Internet-Drafts.  As it is I don't think we
> have procedures for that,

See RFC7120 and RFC7299 (as Russ pointed out on the trans list).
We have those procedures now.

There is still, however, no real issue to be dealt with here.

S.

v2.23.0 | Report a Bug | By Email