Re: Last Call: <draft-ietf-core-etch-02.txt> (Patch and Fetch Methods for Constrained Application Protocol (CoAP)) to Proposed Standard

"Roy T. Fielding" <fielding@gbiv.com> Wed, 24 August 2016 16:32 UTC

Content-Type: text/plain; charset="us-ascii"
Mime-Version: 1.0 (Mac OS X Mail 8.2 \(2104\))
Subject: Re: Last Call: <draft-ietf-core-etch-02.txt> (Patch and Fetch Methods for Constrained Application Protocol (CoAP)) to Proposed Standard
From: "Roy T. Fielding" <fielding@gbiv.com>
In-Reply-To: <147204440644.13256.15079860829265270933.idtracker@ietfa.amsl.com>
Date: Wed, 24 Aug 2016 09:32:17 -0700
Content-Transfer-Encoding: 7bit
Message-Id: <0DCA59AF-6DC5-421A-A907-7C1BF173C99B@gbiv.com>
References: <147204440644.13256.15079860829265270933.idtracker@ietfa.amsl.com>
To: ietf@ietf.org
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/AAyWr3V4cJCDhW3uFG8NM4ACfMU>
Cc: draft-ietf-core-etch@ietf.org, core@ietf.org
Precedence: list

> On Aug 24, 2016, at 6:13 AM, The IESG <iesg-secretary@ietf.org> wrote:
> 
> 
> The IESG has received a request from the Constrained RESTful Environments
> WG (core) to consider the following document:
> - 'Patch and Fetch Methods for Constrained Application Protocol (CoAP)'
>  <draft-ietf-core-etch-02.txt> as Proposed Standard
> 
> The IESG plans to make a decision in the next few weeks, and solicits
> final comments on this action. Please send substantive comments to the
> ietf@ietf.org mailing lists by 2016-09-07. Exceptionally, comments may be
> sent to iesg@ietf.org instead. In either case, please retain the
> beginning of the Subject line to allow automated sorting.
> 
> Abstract
> 
> 
>   The existing Constrained Application Protocol (CoAP) methods only
>   allow access to a complete resource, not to parts of a resource.  In
>   case of resources with larger or complex data, or in situations where
>   a resource continuity is required, replacing or requesting the whole
>   resource is undesirable.  Several applications using CoAP will need
>   to perform partial resource accesses.
> 
>   Similar to HTTP, the existing Constrained Application Protocol (CoAP)
>   GET method only allows the specification of a URI and request
>   parameters in CoAP options, not the transfer of a request payload
>   detailing the request.  This leads to some applications to using POST
>   where actually a cacheable, idempotent, safe request is desired.
> 
>   Again similar to HTTP, the existing Constrained Application Protocol
>   (CoAP) PUT method only allows to replace a complete resource.  This
>   also leads applications to use POST where actually a cacheable,
>   possibly idempotent request is desired.
> 
>   This specification adds new CoAP methods, FETCH, to perform the
>   equivalent of a GET with a request body; and the twin methods PATCH
>   and iPATCH, to modify parts of a CoAP resource.
> 
> The file can be obtained via
> https://datatracker.ietf.org/doc/draft-ietf-core-etch/
> 
> IESG discussion can be tracked via
> https://datatracker.ietf.org/doc/draft-ietf-core-etch/ballot/
> 
> 
> No IPR declarations have been submitted directly on this I-D.
> 
> The document has a reference to obsolete RFC 2616, this is intentional.

What is that supposed to mean?  The reference is intentionally wrong?

I looked at the text and it should be referencing section 9 of RFC7231,
not section 15 of RFC2616.  Just fix the reference or remove it entirely
(since RFC7252 already forked HTTP semantics for no reason whatsoever).

....Roy

Re: Last Call: <draft-ietf-core-etch-02.txt> (Pat… Roy T. Fielding
Re: [core] Last Call: <draft-ietf-core-etch-02.tx… Carsten Bormann
Re: [core] Last Call: <draft-ietf-core-etch-02.tx… Roy T. Fielding