Re: Useful summary for ietf@ietf.org

Stephane Bortzmeyer <bortzmeyer@nic.fr> Mon, 21 April 2008 15:04 UTC

Return-Path: <ietf-bounces@ietf.org>
X-Original-To: ietf-archive@megatron.ietf.org
Delivered-To: ietfarch-ietf-archive@core3.amsl.com
Received: from core3.amsl.com (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 1A9BB28C2BD; Mon, 21 Apr 2008 08:04:42 -0700 (PDT)
X-Original-To: ietf@core3.amsl.com
Delivered-To: ietf@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 62F8F3A6970 for <ietf@core3.amsl.com>; Mon, 21 Apr 2008 08:04:40 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.249
X-Spam-Level:
X-Spam-Status: No, score=-6.249 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HELO_EQ_FR=0.35, RCVD_IN_DNSWL_MED=-4]
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 zce1Ryj9m2LO for <ietf@core3.amsl.com>; Mon, 21 Apr 2008 08:04:36 -0700 (PDT)
Received: from mx2.nic.fr (mx2.nic.fr [192.134.4.11]) by core3.amsl.com (Postfix) with ESMTP id 2209E3A6CAE for <ietf@ietf.org>; Mon, 21 Apr 2008 08:04:36 -0700 (PDT)
Received: from mx2.nic.fr (localhost [127.0.0.1]) by mx2.nic.fr (Postfix) with SMTP id 12DB71C011A; Mon, 21 Apr 2008 17:04:42 +0200 (CEST)
Received: from relay2.nic.fr (relay2.nic.fr [192.134.4.163]) by mx2.nic.fr (Postfix) with ESMTP id 0DD821C0117; Mon, 21 Apr 2008 17:04:42 +0200 (CEST)
Received: from bortzmeyer.nic.fr (batilda.nic.fr [192.134.4.69]) by relay2.nic.fr (Postfix) with ESMTP id 0B7C158EBF0; Mon, 21 Apr 2008 17:04:42 +0200 (CEST)
Date: Mon, 21 Apr 2008 17:04:41 +0200
From: Stephane Bortzmeyer <bortzmeyer@nic.fr>
To: Hannes Tschofenig <Hannes.Tschofenig@gmx.net>
Subject: Re: Useful summary for ietf@ietf.org
Message-ID: <20080421150441.GA15263@nic.fr>
References: <200804180453.m3I4r1Yl031403@rotala.raleigh.ibm.com> <8c99930d0804181104r20a2d7d3iac0ee5b5a8a195de@mail.gmail.com> <ab5568160804181121h5b93282cl5bf26cf251ec45c9@mail.gmail.com> <4808EB5D.80705@gmx.net>
MIME-Version: 1.0
Content-Disposition: inline
In-Reply-To: <4808EB5D.80705@gmx.net>
X-Operating-System: Debian GNU/Linux 4.0
X-Kernel: Linux 2.6.18-6-686 i686
Organization: NIC France
X-URL: http://www.nic.fr/
User-Agent: Mutt/1.5.13 (2006-08-11)
Cc: ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: IETF Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.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://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: ietf-bounces@ietf.org
Errors-To: ietf-bounces@ietf.org

On Fri, Apr 18, 2008 at 09:41:33PM +0300,
 Hannes Tschofenig <Hannes.Tschofenig@gmx.net> wrote 
 a message of 46 lines which said:

> Rather than providing these types of summaries it would make more
> sense to provide a conclusion of the individual discussions. This,
> btw, often does not happen in working groups either. As a consequent
> nobody knows (after a long discussion) whether there was a
> conclusion or what the conclusion could have been.

Before trying to summarize the (very open) discussions on the IETF
general mailing list, a good start would be to summarize IESG
evaluations... I would be interested to know, for instance, why
draft-ietf-mboned-addrarch or draft-michaelson-4byte-as-representation
were not approved by IESG (there is certainly a good reason, but to
extract it from datatracker is not obvious).

_______________________________________________
IETF mailing list
IETF@ietf.org
https://www.ietf.org/mailman/listinfo/ietf