IETF Logo Mail Archive

Re: The "Clerk" function and Standards throughput and quality

John C Klensin <john-ietf@jck.com> Wed, 06 October 2004 22:10 UTC

Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA22621; Wed, 6 Oct 2004 18:10:41 -0400 (EDT)
Received: from megatron.ietf.org ([132.151.6.71]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CFK9D-0006iy-75; Wed, 06 Oct 2004 18:20:38 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CFJqd-00063q-Mo; Wed, 06 Oct 2004 18:01:23 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CFJfv-00014E-PN for ietf@megatron.ietf.org; Wed, 06 Oct 2004 17:50:19 -0400
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA19769 for <ietf@ietf.org>; Wed, 6 Oct 2004 17:50:16 -0400 (EDT)
Received: from ns.jck.com ([209.187.148.211] helo=bs.jck.com) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CFJpS-0004yA-90 for ietf@ietf.org; Wed, 06 Oct 2004 18:00:13 -0400
Received: from [127.0.0.1] (helo=localhost) by bs.jck.com with esmtp (Exim 4.34) id 1CFJfo-000B50-D6; Wed, 06 Oct 2004 17:50:12 -0400
Date: Wed, 06 Oct 2004 17:50:04 -0400
From: John C Klensin <john-ietf@jck.com>
To: Harald Tveit Alvestrand <harald@alvestrand.no>, ietf@ietf.org
Message-ID: <57088C56997A0D4816E39CE8@[192.168.2.227]>
In-Reply-To: <A8EF0E1A5432B71E3F9AA932@askvoll.hjemme.alvestrand.no>
References: <23AB4F180D939FC980291347@scan.jck.com> <990C270B37EED7014A53D4E3@B50854F0A9192E8EC6CDA126> <BC3CD23742524284F7EC44AC@scan.jck.com> <A8EF0E1A5432B71E3F9AA932@askvoll.hjemme.alvestrand.no>
X-Mailer: Mulberry/3.1.6 (Win32)
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format="flowed"
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 856eb5f76e7a34990d1d457d8e8e5b7f
Content-Transfer-Encoding: 7bit
Subject: Re: The "Clerk" function and Standards throughput and quality
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
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 7655788c23eb79e336f5f8ba8bce7906
Content-Transfer-Encoding: 7bit


--On Wednesday, October 06, 2004 1:07 PM +0200 Harald Tveit 
Alvestrand <harald@alvestrand.no> wrote:

>
> I do think our thoughts run very much in parallel - I'll be
> interested to hear more of why you think the "scenario O"
> organizational format will make it hard to make those support
> functions work.

Again a misunderstanding -- I don't see "Scenario O" as being 
either better or worse in regard to the above than any other 
scenario.  My concern is with the definition of the Clerk 
function, which is scenario-independent.

    john


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

v2.23.0 | Report a Bug | By Email