[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [INDEP] [rfc-i] RFC Editor Structure
Dear hmdmhdfmhdjmzdtjmzdtzktdkztdjz,
You wrote:
*>
*> Thanks for info. Some quick observations while looking at the
*> picture of your model: You don't cover the rather convoluted
*> interactions between IESG and "ISS", to fix that please sort
See RFC 3932.
*> the "stream" columns like that: IAB | IETF | community | IRTF.
I am not aware of any implied ordering, and I don't know
what it would mean.
*>
*> RFC number assignment should be the privilege of the RFC editor,
*> not of some "outsourced" RFC production entity. This used to be
*> great magic in the past, and it is a completely subjective magic.
It is not a "privilege", but a duty. And not exactly magic, but the
community likes it that RFC 2822 was an update to RFC 822, for example.
Not an accident, though Joyce used to like to pretend it was.
The RFC Editor organization believes that RFC number assignment is
inextricably bound with the production process, so it would make
little sense to separate these functions. This assumes that
the RFC publication model continues to use late binding for RFC
numbers, as it always has. Another choice (which I believe has
some serious flaws) would be to change to early RFC number binding --
say, RFC numbers are assigned by the IESG before the document
enters the publication process. The IESG could go as far as it
wanted towards structuring the number space (and how long would
it be before a Dewey decimal numbering scheFrom independent-bounces at ietf.org Wed Jun 4 13:34:54 2008
Return-Path: <independent-bounces at ietf.org>
X-Original-To: independent-archive at optimus.ietf.org
Delivered-To: ietfarch-independent-archive at core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
by core3.amsl.com (Postfix) with ESMTP id 515433A6D12;
Wed, 4 Jun 2008 13:34:54 -0700 (PDT)
X-Original-To: independent at core3.amsl.com
Delivered-To: independent at core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
by core3.amsl.com (Postfix) with ESMTP id E517C3A6CFA
for <independent at core3.amsl.com>; Wed, 4 Jun 2008 13:34:52 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.299
X-Spam-Level:
X-Spam-Status: No, score=-2.299 tagged_above=-999 required=5 tests=[AWL=0.300,
BAYES_00=-2.599]
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 1vt3rTKKjCDx for <independent at core3.amsl.com>;
Wed, 4 Jun 2008 13:34:52 -0700 (PDT)
Received: from boreas.isi.edu (boreas.isi.edu [128.9.160.161])
by core3.amsl.com (Postfix) with ESMTP id 1BB1928C249
for <independent at ietf.org>; Wed, 4 Jun 2008 13:34:49 -0700 (PDT)
Received: from gra.isi.edu (gra.isi.edu [128.9.160.133])
by boreas.isi.edu (8.13.8/8.13.8) with ESMTP id m54KXiSa013407;
Wed, 4 Jun 2008 13:33:45 -0700 (PDT)
From: Bob Braden <braden at ISI.EDU>
Received: (from braden at localhost) by gra.isi.edu (8.9.3/8.8.6) id NAA05882;
Wed, 4 Jun 2008 13:33:44 -0700 (PDT)
Date: Wed, 4 Jun 2008 13:33:44 -0700 (PDT)
Message-Id: <200806042033.NAA05882 at gra.isi.edu>
To: rfc-interest at rfc-editor.org, hmdmhdfmhdjmzdtjmzdtzktdkztdjz at gmail.com
X-Sun-Charset: US-ASCII
X-ISI-4-43-8-MailScanner: Found to be clean
X-MailScanner-From: braden at isi.edu
Cc: independent at ietf.org
Subject: Re: [INDEP] [rfc-i] RFC Editor Structure
X-BeenThere: independent at ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Discussion of RFC Editor independent submissions proposal
<independent.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/independent>,
<mailto:independent-request at ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/pipermail/independent>
List-Post: <mailto:independent at ietf.org>
List-Help: <mailto:independent-request at ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/independent>,
<mailto:independent-request at ietf.org?subject=subscribe>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: independent-bounces at ietf.org
Errors-To: independent-bounces at ietf.org
Dear hmdmhdfmhdjmzdtjmzdtzktdkztdjz,
You wrote:
*>
*> Thanks for info. Some quick observations while looking at the
*> picture of your model: You don't cover the rather convoluted
*> interactions between IESG and "ISS", to fix that please sort
See RFC 3932.
*> the "stream" columns like that: IAB | IETF | community | IRTF.
I am not aware of any implied ordering, and I don't know
what it would mean.
*>
*> RFC number assignment should be the privilege of the RFC editor,
*> not of some "outsourced" RFC production entity. This used to be
*> great magic in the past, and it is a completely subjective magic.
It is not a "privilege", but a duty. And not exactly magic, but the
community likes it that RFC 2822 was an update to RFC 822, for example.
Not an accident, though Joyce used to like to pretend it was.
The RFC Editor organization believes that RFC number assignment is
inextricably bound with the production process, so it would make
little sense to separate these functions. This assumes that
the RFC publication model continues to use late binding for RFC
numbers, as it always has. Another choice (which I believe has
some serious flaws) would be to change to early RFC number binding --
say, RFC numbers are assigned by the IESG before the document
enters the publication process. The IESG could go as far as it
wanted towards structuring the number space (and how long would
it be before a Dewey decimal numbering scheme appeame appeared?).
Bob Braden
_______________________________________________
INDEPENDENT mailing list
INDEPENDENT at ietf.org
https://www.ietf.org/mailman/listinfo/independent
red?).
Bob Braden
_______________________________________________
INDEPENDENT mailing list
INDEPENDENT at ietf.org
https://www.ietf.org/mailman/listinfo/independent