Re: [core] Issue Tracking of Working Group Items

Carsten Bormann <cabo@tzi.org> Tue, 19 April 2016 12:49 UTC

Return-Path: <cabo@tzi.org>
X-Original-To: core@ietfa.amsl.com
Delivered-To: core@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 36CE512DBB7 for <core@ietfa.amsl.com>; Tue, 19 Apr 2016 05:49:51 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.9
X-Spam-Level:
X-Spam-Status: No, score=-1.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id k21ZMveH12WA for <core@ietfa.amsl.com>; Tue, 19 Apr 2016 05:49:45 -0700 (PDT)
Received: from relay6-d.mail.gandi.net (relay6-d.mail.gandi.net [IPv6:2001:4b98:c:538::198]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id B546F12DB55 for <core@ietf.org>; Tue, 19 Apr 2016 05:49:45 -0700 (PDT)
Received: from mfilter18-d.gandi.net (mfilter18-d.gandi.net [217.70.178.146]) by relay6-d.mail.gandi.net (Postfix) with ESMTP id BC1F2FB8CF; Tue, 19 Apr 2016 14:49:43 +0200 (CEST)
X-Virus-Scanned: Debian amavisd-new at mfilter18-d.gandi.net
Received: from relay6-d.mail.gandi.net ([IPv6:::ffff:217.70.183.198]) by mfilter18-d.gandi.net (mfilter18-d.gandi.net [::ffff:10.0.15.180]) (amavisd-new, port 10024) with ESMTP id f73QLJiu8Wpx; Tue, 19 Apr 2016 14:49:42 +0200 (CEST)
X-Originating-IP: 93.199.242.26
Received: from nar-3.local (p5DC7F21A.dip0.t-ipconnect.de [93.199.242.26]) (Authenticated sender: cabo@cabo.im) by relay6-d.mail.gandi.net (Postfix) with ESMTPSA id 0F526FB8DA; Tue, 19 Apr 2016 14:49:34 +0200 (CEST)
Message-ID: <5716295D.7010204@tzi.org>
Date: Tue, 19 Apr 2016 14:49:33 +0200
From: Carsten Bormann <cabo@tzi.org>
User-Agent: Postbox 4.0.8 (Macintosh/20151105)
MIME-Version: 1.0
To: Hannes Tschofenig <hannes.tschofenig@gmx.net>
References: <57161AFB.5040804@gmx.net>
In-Reply-To: <57161AFB.5040804@gmx.net>
X-Enigmail-Version: 1.2.3
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: 8bit
Archived-At: <http://mailarchive.ietf.org/arch/msg/core/82NqaXsjTCFCuaqxWJyaULfxi6s>
Cc: "core@ietf.org WG" <core@ietf.org>
Subject: Re: [core] Issue Tracking of Working Group Items
X-BeenThere: core@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: "Constrained RESTful Environments \(CoRE\) Working Group list" <core.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/core>, <mailto:core-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/core/>
List-Post: <mailto:core@ietf.org>
List-Help: <mailto:core-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/core>, <mailto:core-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 19 Apr 2016 12:49:51 -0000

Willst Du die Entscheidung zu #396 eintragen oder soll ich das tun?
(#397 wird da auch gleich erledigt, aber das haken wir dann am besten
mit -02 ab.)

Grüße, Carsten


Hannes Tschofenig wrote:
> Hi all,
> 
> at the last IETF meeting we talked about the open issues with the
> working group items and identified various issues that need to be
> tackled with high priority.
> 
> The document editors wanted to add the open issues to the WG tracker.
> 
> I have just looked at the tracker at
> https://trac.tools.ietf.org/wg/core/trac/report/1 and, unfortunately,
> nobody has added any issues.
> 
> If we indeed want to complete many of the WG items by the Berlin IETF
> meeting then we should at least add the open issues to the tracker
> before we can resolve them one-by-one.
> 
> It is not even clear to me who is in charge (editor) for each of the WG
> documents.
> 
> If there isn't even enough energy by the authors to identify the open
> issues and to add them to the tracker then the group is in trouble and
> IMHO should definitely not adopt new WG documents.
> 
> Ciao
> Hannes
> 
> 
> _______________________________________________
> core mailing list
> core@ietf.org
> https://www.ietf.org/mailman/listinfo/core