Re: [RADIR] Should RADir be closed?

Thomas Narten <narten@us.ibm.com> Tue, 15 December 2009 14:18 UTC

Return-Path: <narten@us.ibm.com>
X-Original-To: radir@core3.amsl.com
Delivered-To: radir@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id C42D53A6A2A for <radir@core3.amsl.com>; Tue, 15 Dec 2009 06:18:04 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.558
X-Spam-Level:
X-Spam-Status: No, score=-4.558 tagged_above=-999 required=5 tests=[AWL=-2.042, BAYES_00=-2.599, DIET_1=0.083]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id pBB7Q3LtOQ0a for <radir@core3.amsl.com>; Tue, 15 Dec 2009 06:18:04 -0800 (PST)
Received: from e7.ny.us.ibm.com (e7.ny.us.ibm.com [32.97.182.137]) by core3.amsl.com (Postfix) with ESMTP id E9EE03A68B4 for <radir@ietf.org>; Tue, 15 Dec 2009 06:18:03 -0800 (PST)
Received: from d01relay01.pok.ibm.com (d01relay01.pok.ibm.com [9.56.227.233]) by e7.ny.us.ibm.com (8.14.3/8.13.1) with ESMTP id nBFECYRp018732 for <radir@ietf.org>; Tue, 15 Dec 2009 09:12:34 -0500
Received: from d01av02.pok.ibm.com (d01av02.pok.ibm.com [9.56.224.216]) by d01relay01.pok.ibm.com (8.13.8/8.13.8/NCO v10.0) with ESMTP id nBFEHfL5110002 for <radir@ietf.org>; Tue, 15 Dec 2009 09:17:41 -0500
Received: from d01av02.pok.ibm.com (loopback [127.0.0.1]) by d01av02.pok.ibm.com (8.14.3/8.13.1/NCO v10.0 AVout) with ESMTP id nBFEHf0p016795 for <radir@ietf.org>; Tue, 15 Dec 2009 12:17:41 -0200
Received: from cichlid.raleigh.ibm.com (sig-9-76-142-182.mts.ibm.com [9.76.142.182]) by d01av02.pok.ibm.com (8.14.3/8.13.1/NCO v10.0 AVin) with ESMTP id nBFEHeOW016759 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Tue, 15 Dec 2009 12:17:41 -0200
Received: from cichlid.raleigh.ibm.com (localhost [127.0.0.1]) by cichlid.raleigh.ibm.com (8.14.3/8.12.5) with ESMTP id nBFEHdt7023605; Tue, 15 Dec 2009 09:17:40 -0500
Message-Id: <200912151417.nBFEHdt7023605@cichlid.raleigh.ibm.com>
To: Russ Housley <housley@vigilsec.com>
In-reply-to: <20091129181219.2214C9A4746@odin.smetech.net>
References: <20091129181219.2214C9A4746@odin.smetech.net>
Comments: In-reply-to Russ Housley <housley@vigilsec.com> message dated "Sun, 29 Nov 2009 13:12:17 -0500."
Date: Tue, 15 Dec 2009 09:17:39 -0500
From: Thomas Narten <narten@us.ibm.com>
Cc: radir@ietf.org
Subject: Re: [RADIR] Should RADir be closed?
X-BeenThere: radir@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Routing and Addressing Directorate <radir.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/radir>, <mailto:radir-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/radir>
List-Post: <mailto:radir@ietf.org>
List-Help: <mailto:radir-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/radir>, <mailto:radir-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 15 Dec 2009 14:18:04 -0000

> I have not seen much activity here in quite some time.  Has the 
> directorate outlived its usefulness?

I think there is agreement we don't have a real purpose at this point
and energy seems to have moved elswhere.

But, I think the problem statement document we put together is pretty
good and I think it should get published as an info RFC. The last
version was in pretty good shape (IMO), but hadn't really gotten much
feedback either way, so others may think otherwise. (The main change
in the last revision was to take out more of the "business judgement"
as being out-of-scope.)

Not sure how best to publish it. We can go the independent submission
route, but I think it would better for all if this were IETF approved,
implying it had gotten IETF review and folk were generally supportive
(and more importantly, there was no serious objecting/disagreement
with the content). I have doubts about going further and trying and
get IETF "consensus" and make it a BCP or something stronger, as the
community is likely fundamentally divided on the question of "how
serious" the problem is. I suspect that no one really has the desire
or energy to have that debate yet again.

I do think the document should say that it was put together by the
directorate, listing the members and so forth, but without trying to
claim that because it was done by a directorate, it has some sort of
special cachet or extra weight.  But at the same time, I don't think
we should lose the history of how the document was developed.

Thoughts?

Thomas