IETF Logo Mail Archive

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

Hannes Tschofenig <hannes.tschofenig@gmx.net> Mon, 28 March 2016 14:49 UTC

Return-Path: <hannes.tschofenig@gmx.net>
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 EA80A12DA66 for <core@ietfa.amsl.com>; Mon, 28 Mar 2016 07:49:46 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.611
X-Spam-Level:
X-Spam-Status: No, score=-2.611 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, FREEMAIL_FROM=0.001, RCVD_IN_DNSWL_LOW=-0.7, RCVD_IN_MSPIKE_H2=-0.001, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01] 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 pkTNPmo4J1MP for <core@ietfa.amsl.com>; Mon, 28 Mar 2016 07:49:45 -0700 (PDT)
Received: from mout.gmx.net (mout.gmx.net [212.227.17.22]) (using TLSv1.2 with cipher DHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 43A0412DA3F for <core@ietf.org>; Mon, 28 Mar 2016 07:48:52 -0700 (PDT)
Received: from [192.168.10.140] ([80.92.115.95]) by mail.gmx.com (mrgmx102) with ESMTPSA (Nemesis) id 0Ld3t6-1a2jLE2OLw-00iByh; Mon, 28 Mar 2016 16:48:43 +0200
To: Carsten Bormann <cabo@tzi.org>
References: <56F91A0A.5060804@gmx.net> <56F922F2.9060203@tzi.org>
From: Hannes Tschofenig <hannes.tschofenig@gmx.net>
Openpgp: id=071A97A9ECBADCA8E31E678554D9CEEF4D776BC9
Message-ID: <56F94446.7040900@gmx.net>
Date: Mon, 28 Mar 2016 16:48:38 +0200
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:38.0) Gecko/20100101 Thunderbird/38.6.0
MIME-Version: 1.0
In-Reply-To: <56F922F2.9060203@tzi.org>
Content-Type: multipart/signed; micalg="pgp-sha512"; protocol="application/pgp-signature"; boundary="LVAJeVehl6TQTSnnQfWqveVAqNBIsAw4b"
X-Provags-ID: V03:K0:wyKSpUD8gseDRAcz7yOUWhgX50utWQVZAb5VEVbQXrl7ZB1u2OY 4TozUlYhoPvSMe0uDabwsTEEbMRaXgQcTfL5Czr2gck+pB2aPGJ/qLIiuRz7B8YGBF82rFF 0C8JauvHnLdo+BcPQp5ekYpInQ1WfQWe0/VjbmXaR4q8jmIpNnJ/Q3xFQS3il3dXRT919if vW+CuMMXvq5e/hYIOH3oA==
X-UI-Out-Filterresults: notjunk:1;V01:K0:WKm9pvkYyi0=:78GksxrRWqb+SwW/JhXE+S wdExoxPJ4vQyrR+Sz3d0hPlcJNW5kTYhdLXxX7tPJhQlxnsopKZJeIIpo2srQrJcSXiT9V5FT VvrR3GGtMExocvHhPdCg6C1wfchKsQrmRmr8yAnUid+cOKqqcVUq99LbxCltdC9j533O/aEIT zD7uECMYk8Xw2uTRLUPBkAh98PMArQcQttDMydsUoDN6UMURsUw6NTmhTmVGaVBpKwZZ7Xx8i rNb76Y117ON+07sUrLac1d73r+TMU9yl+opLuEUWA8eqVhJ4VyZtOjYmFs1strMaJyJld+p7E 8++0hIxWMNhb1U3HsXx0a/kxZ3ZJALIiTl5SGy458vH4rjYtr7Tk6QbhlzRRMJxfoAToHBBEC UpUopHojm+fX706t1qihrqrgu+WLaEju1VF38g8Oa9SWlJBVC8Pz0Tkx2uz8yWbfCTjP52MvV oPZnz2n/WSOAZvRVtcHP4JJCHIgtq8rEjfCXnybYXDySv4dDi3UpuN/gdCqU7YMpOD3LH9Eal AxyludfbUxR9JQT0kINs9+bokbtrdBnzXS2ynfQqNEEdpIcyzjAS5pQznV1JTPDpZu3Rm9iBV h3OR+rNvg5GyI76VuGshEg/j6J6BalOmd5Z7atocCGBBfz1gEXCrBs1Hv/y+tT+38b3YnYZI9 B6eEA4tx/x2p9v5PUpljwQLmvV8uBOEA8pnaatSqNdHKQOkdII0Liw/gnDftc60i+owdiLSad 01SAHxa8/oqsDQCtGcadv04UC9qzf3GB1s9sNkLqlYuZxyAEUlBvBP7b2lg=
Archived-At: <http://mailarchive.ietf.org/arch/msg/core/lzpdgOemv3Vaj30KbfvNsW7fsPQ>
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 14:49:47 -0000

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.

v2.23.0 | Report a Bug | By Email