Re: [core] draft-ietf-core-resource-directory-07

Carsten Bormann <cabo@tzi.org> Mon, 28 March 2016 12:26 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 7259912D187 for <core@ietfa.amsl.com>; Mon, 28 Mar 2016 05:26:34 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.601
X-Spam-Level:
X-Spam-Status: No, score=-2.601 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_LOW=-0.7, RCVD_IN_MSPIKE_H2=-0.001] 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 sKSOEMAbqfYP for <core@ietfa.amsl.com>; Mon, 28 Mar 2016 05:26:32 -0700 (PDT)
Received: from relay5-d.mail.gandi.net (relay5-d.mail.gandi.net [217.70.183.197]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id AA55F12D169 for <core@ietf.org>; Mon, 28 Mar 2016 05:26:31 -0700 (PDT)
Received: from mfilter32-d.gandi.net (mfilter32-d.gandi.net [217.70.178.163]) by relay5-d.mail.gandi.net (Postfix) with ESMTP id 405B541C084; Mon, 28 Mar 2016 14:26:30 +0200 (CEST)
X-Virus-Scanned: Debian amavisd-new at mfilter32-d.gandi.net
Received: from relay5-d.mail.gandi.net ([IPv6:::ffff:217.70.183.197]) by mfilter32-d.gandi.net (mfilter32-d.gandi.net [::ffff:10.0.15.180]) (amavisd-new, port 10024) with ESMTP id 55eerTwGUain; Mon, 28 Mar 2016 14:26:28 +0200 (CEST)
X-Originating-IP: 93.199.229.85
Received: from nar.local (p5DC7E555.dip0.t-ipconnect.de [93.199.229.85]) (Authenticated sender: cabo@cabo.im) by relay5-d.mail.gandi.net (Postfix) with ESMTPSA id 853B741C087; Mon, 28 Mar 2016 14:26:28 +0200 (CEST)
Message-ID: <56F922F2.9060203@tzi.org>
Date: Mon, 28 Mar 2016 14:26:26 +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: <56F91A0A.5060804@gmx.net>
In-Reply-To: <56F91A0A.5060804@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/DFwJkxP5ug0QDMfMZAs3H0r3KOk>
Cc: "core@ietf.org WG" <core@ietf.org>
Subject: Re: [core] draft-ietf-core-resource-directory-07
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: Mon, 28 Mar 2016 12:26:34 -0000

Hi Hannes,

thank you for this extremely useful review.
Many great observations, both around terminology and presentation, and
around the relationship to other efforts such as authorization.
Something to chew on for Buenos Aires...

Let me pick one item as it has a direct bearing on the meeting agenda:

Hannes Tschofenig wrote:
> The document notes that there is an open issue regarding patch (see
> Section 5.6). What exactly is the question that needs to be answered?

The question is simply whether we will be able to finish adding the
PATCH methods to CoAP (see draft-vanderstok-core-etch) on the same
timeline as the time needed for completing the RD document.  Some of us
are optimistic that this is possible, some think the way to use PATCH
with RD should be added as a separate document.  But for the discussion
of the functionality of the RD, it makes sense to keep the PATCH
functionality in context, assuming we can always take out section 5.6
even at a late stage if we run into a problem with PATCH.
That's why it is part of -07.

Grüße, Carsten