RE: Possible new Real-Time Applications and Infrastucture (RAI) Area

Bill Sommerfeld <sommerfeld@sun.com> Wed, 21 September 2005 19:54 UTC

Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1EIAg6-0000Xg-Sk; Wed, 21 Sep 2005 15:54:50 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1EIAg4-0000X3-VM for ietf@megatron.ietf.org; Wed, 21 Sep 2005 15:54:49 -0400
Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA15844 for <ietf@ietf.org>; Wed, 21 Sep 2005 15:54:47 -0400 (EDT)
Received: from brmea-mail-3.sun.com ([192.18.98.34]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1EIAm7-00052g-V9 for ietf@ietf.org; Wed, 21 Sep 2005 16:01:06 -0400
Received: from eastmail1bur.East.Sun.COM ([129.148.9.49]) by brmea-mail-3.sun.com (8.12.10/8.12.9) with ESMTP id j8LJsi1L029266 for <ietf@ietf.org>; Wed, 21 Sep 2005 13:54:45 -0600 (MDT)
Received: from thunk.east.sun.com (thunk.East.Sun.COM [129.148.174.66]) by eastmail1bur.East.Sun.COM (8.12.10+Sun/8.12.10/ENSMAIL, v2.2) with ESMTP id j8LJsiUj010513 for <ietf@ietf.org>; Wed, 21 Sep 2005 15:54:44 -0400 (EDT)
Received: from 127.0.0.1 (localhost [127.0.0.1]) by thunk.east.sun.com (8.13.4+Sun/8.13.4) with ESMTP id j8LJsifP133172; Wed, 21 Sep 2005 15:54:44 -0400 (EDT)
From: Bill Sommerfeld <sommerfeld@sun.com>
To: john.loughney@nokia.com
In-Reply-To: <1AA39B75171A7144A73216AED1D7478DD65B2C@esebe100.NOE.Nokia.com>
References: <1AA39B75171A7144A73216AED1D7478DD65B2C@esebe100.NOE.Nokia.com>
Content-Type: text/plain
Message-Id: <1127332483.127264.30.camel@thunk>
Mime-Version: 1.0
X-Mailer: Ximian Evolution 1.4.6.323
Date: Wed, 21 Sep 2005 15:54:43 -0400
Content-Transfer-Encoding: 7bit
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 9182cfff02fae4f1b6e9349e01d62f32
Content-Transfer-Encoding: 7bit
Cc: ietf@ietf.org
Subject: RE: Possible new Real-Time Applications and Infrastucture (RAI) Area
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
Sender: ietf-bounces@ietf.org
Errors-To: ietf-bounces@ietf.org

On Fri, 2005-09-16 at 14:36, john.loughney@nokia.com wrote:
> If there was a way to lighten-up the IESG review process, then this
> would be a good idea. For example, having a single DISCUSS per Area
> would be one way to reduce this could be one solution. 

Why do you think this would make any difference in practice?  chances
are that an AD-pair would agree to hold a DISCUSS if either felt that an
issue should block publication.

>From my point of view, a far greater source of delay is the
extraordinarily rapid change in the standards applied to documents by
the IESG; it seems that, if your document editor is very busy, by the
time a document is reworked to address one set of editorial standards, a
new requirement (leading to a new blocking DISCUSS) is likely to appear.

seems like we could avoid this sort of logrolling by judging a document
based on the rules published and in force at the time it was submitted
to the IESG.

					- Bill






_______________________________________________
Ietf mailing list
Ietf@ietf.org
https://www1.ietf.org/mailman/listinfo/ietf