Re: [apps-discuss] Fwd: New Version Notification for draft-wilde-accept-post-01.txt

An Accept-Put (or Accept-{whatever}) would be useful if and only if
there are practical known use cases where we know they'd be used. The
two we currently have (Accept-Patch and Accept-Post) have very clear,
specific real world use cases that solve immediate non-theoretical
needs. If someone eventually finds need for Accept-Put, they can
easily draft up a quick I-D that defines it :-)

On Mon, Sep 9, 2013 at 11:42 AM, Martin Thomson
<martin.thomson@gmail.com> wrote:
> Apologies if I missed an earlier discussion, but why is this
> restricted specifically to POST requests?  Is there value in also
> having Accept-Put (useful if the resource can be retrieved in multiple
> forms, but only uploaded in a subset of those, such that it is
> difficult to learn what types are acceptable), as well as Accept-Blah,
> for any future method that contains a body or any request that might
> return 415?
>
> On 6 September 2013 18:58, Erik Wilde <dret@berkeley.edu> wrote:
>> changes from -00 to -01
>> (http://tools.ietf.org/html/draft-wilde-accept-post-01#section-9.1):
>>
>>    o  Changed ABNF for header field from RFC 2616 to HTTPbis convention
>> (only specify the header field value grammar).
>>    o  Added implementations (all from the LDP community for now).
>>    o  Added open issue for aligning accept-post as defined by the "HTTP Link
>> Hints" draft.
>>
>>
>> -------- Original Message --------
>> Subject: New Version Notification for draft-wilde-accept-post-01.txt
>> Date: Fri, 06 Sep 2013 18:41:29 -0700
>> From: internet-drafts@ietf.org
>>
>> A new version of I-D, draft-wilde-accept-post-01.txt
>> has been successfully submitted by John Arwe and posted to the
>> IETF repository.
>>
>> Filename:        draft-wilde-accept-post
>> Revision:        01
>> Title:           The Accept-Post HTTP Header
>> Creation date:   2013-09-06
>> Group:           Individual Submission
>> Number of pages: 10
>> URL: http://www.ietf.org/internet-drafts/draft-wilde-accept-post-01.txt
>> Status:          http://datatracker.ietf.org/doc/draft-wilde-accept-post
>> Htmlized:        http://tools.ietf.org/html/draft-wilde-accept-post-01
>> Diff:            http://www.ietf.org/rfcdiff?url2=draft-wilde-accept-post-01
>>
>> Abstract:
>>    This specification defines a new HTTP response header field Accept-
>>    Post, which indicates server support for specific media types for
>>    entity bodies in HTTP POST requests.
>>
>> Note to Readers
>>
>>    This draft should be discussed on the apps-discuss mailing list [1].
>>    Online access to all versions and files is available on github [2].
>> _______________________________________________
>> apps-discuss mailing list
>> apps-discuss@ietf.org
>> https://www.ietf.org/mailman/listinfo/apps-discuss
> _______________________________________________
> apps-discuss mailing list
> apps-discuss@ietf.org
> https://www.ietf.org/mailman/listinfo/apps-discuss