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

peter van der Stok <stokcons@xs4all.nl> Tue, 29 March 2016 12:18 UTC

Return-Path: <stokcons@xs4all.nl>
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 AAC4712D75F for <core@ietfa.amsl.com>; Tue, 29 Mar 2016 05:18:23 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.621
X-Spam-Level:
X-Spam-Status: No, score=-2.621 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_LOW=-0.7, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, SPF_PASS=-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 5t_bn0N2X1ow for <core@ietfa.amsl.com>; Tue, 29 Mar 2016 05:18:22 -0700 (PDT)
Received: from lb2-smtp-cloud6.xs4all.net (lb2-smtp-cloud6.xs4all.net [194.109.24.28]) (using TLSv1 with cipher DHE-RSA-AES128-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id B712E12D75C for <core@ietf.org>; Tue, 29 Mar 2016 05:18:21 -0700 (PDT)
Received: from webmail.xs4all.nl ([194.109.20.208]) by smtp-cloud6.xs4all.net with ESMTP id boJL1s00d4VN29601oJLDg; Tue, 29 Mar 2016 14:18:20 +0200
Received: from 2001:983:a264:1:98c9:ca61:9568:1397 by webmail.xs4all.nl with HTTP (HTTP/1.1 POST); Tue, 29 Mar 2016 14:18:20 +0200
MIME-Version: 1.0
Content-Type: text/plain; charset="US-ASCII"; format="flowed"
Content-Transfer-Encoding: 7bit
Date: Tue, 29 Mar 2016 14:18:20 +0200
From: peter van der Stok <stokcons@xs4all.nl>
To: Hannes Tschofenig <hannes.tschofenig@gmx.net>
Organization: vanderstok consultancy
Mail-Reply-To: consultancy@vanderstok.org
In-Reply-To: <56F94446.7040900@gmx.net>
References: <56F91A0A.5060804@gmx.net> <56F922F2.9060203@tzi.org> <56F94446.7040900@gmx.net>
Message-ID: <cc1185899fa972e20d60272760fe7dce@xs4all.nl>
X-Sender: stokcons@xs4all.nl (Kd9t+Oyovm0/7YU6zyD/xYWIcDYaBZvt)
User-Agent: XS4ALL Webmail
Archived-At: <http://mailarchive.ietf.org/arch/msg/core/DlGOckGhQXJrFfs_G0OEmLU2xlA>
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
Reply-To: consultancy@vanderstok.org
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, 29 Mar 2016 12:18:23 -0000

+1
Peter

Hannes Tschofenig schreef op 2016-03-28 16:48:
> Thanks, Carsten. This has helped me a lot since I have not been
> following the patch debate. It sounds like a challenging task to 
> predict
> the completion date of draft-vanderstok-core-etch.
> 
> I would certainly appreciate if the RD document gets leaves the working
> group at latest end of May.
> 
> On 03/28/2016 02:26 PM, Carsten Bormann wrote:
>> 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.
> 
> 
> _______________________________________________
> core mailing list
> core@ietf.org
> https://www.ietf.org/mailman/listinfo/core