IETF Logo Mail Archive

[core] Selecting a WG document for CoAP

Carsten Bormann <cabo@tzi.org> Mon, 10 May 2010 16:51 UTC

Return-Path: <cabo@tzi.org>
X-Original-To: core@core3.amsl.com
Delivered-To: core@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 503643A6A5A for <core@core3.amsl.com>; Mon, 10 May 2010 09:51:30 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.415
X-Spam-Level:
X-Spam-Status: No, score=-4.415 tagged_above=-999 required=5 tests=[AWL=-0.766, BAYES_50=0.001, HELO_EQ_DE=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 Y3RuEcwoyAHq for <core@core3.amsl.com>; Mon, 10 May 2010 09:51:29 -0700 (PDT)
Received: from informatik.uni-bremen.de (mailhost.informatik.uni-bremen.de [IPv6:2001:638:708:30c9:209:3dff:fe00:7136]) by core3.amsl.com (Postfix) with ESMTP id DB0783A6A56 for <core@ietf.org>; Mon, 10 May 2010 09:51:28 -0700 (PDT)
X-Virus-Scanned: amavisd-new at informatik.uni-bremen.de
Received: from smtp-fb3.informatik.uni-bremen.de (smtp-fb3.informatik.uni-bremen.de [134.102.224.120]) by informatik.uni-bremen.de (8.14.3/8.14.3) with ESMTP id o4AGp8Ka012280 for <core@ietf.org>; Mon, 10 May 2010 18:51:08 +0200 (CEST)
Received: from [192.168.217.101] (p5489AF27.dip.t-dialin.net [84.137.175.39]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (No client certificate requested) by smtp-fb3.informatik.uni-bremen.de (Postfix) with ESMTP id C6F2DD7BA; Mon, 10 May 2010 18:51:07 +0200 (CEST)
From: Carsten Bormann <cabo@tzi.org>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Date: Mon, 10 May 2010 18:51:06 +0200
To: core <core@ietf.org>
Message-Id: <3BB5F67A-9E57-4F81-B7C5-ABB1E136DAAC@tzi.org>
Mime-Version: 1.0 (Apple Message framework v1078)
X-Mailer: Apple Mail (2.1078)
Subject: [core] Selecting a WG document for CoAP
X-BeenThere: core@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: "Constrained RESTful Environments \(CoRE\) Working Group list" <core.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/core>, <mailto:core-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/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: Mon, 10 May 2010 16:51:30 -0000

The CORE WG has a milestone to select a WG document for CoAP in April:

http://datatracker.ietf.org/wg/core/charter/
...
Apr 2010	Select WG document for basis of the CoAP protocol

Of the various documents that have been contributed, draft-shelby-core-coap has significant discussion, as well as the largest number of updates (including a previous version that was still called -6lowapp-coap).

Today, another updated version of that draft was announced.  See
http://www.ietf.org/mail-archive/web/core/current/msg00138.html
for the announcement and
http://tools.ietf.org/html/draft-shelby-core-coap-01
for the draft itself.

However, as the authors say, there are still significant TODOs.

Are we in a state yet where we can say whether this is the right direction for the WG to take?
If yes, is it the right direction?  Should we adopt it as a WG document?
If you don't think we can say yet, is there a set of technical decisions you would like the authors to take with priority?

Note that once a document has become a WG document, the authors act as editors for the working group, making (and usually fleshing out the details of) any change that the WG decides it needs.
If you think we can still improve the draft, this is not an obstacle to making it a WG document.
But of course we shouldn't do that if we intend to reverse its fundamental technical direction.

In order to stay roughly in sync with our milestones, we should reach at a decision on how to go forward this week.

Gruesse, Carsten

v2.23.0 | Report a Bug | By Email