Re: feedback on draft-murchison-webdav-prefer-09

>>    methods can be used to create or update a resource.  In some
>>    instances, such as with CalDAV Scheduling [RFC6638], the created or
>>    updated resource representation may differ from the representation
>>    sent in the body of the request or referenced by the effective
>>    request URI.  In cases where the client would normally issue a
>>    subsequent GET request to retrieve the current representation of the
>>    resource, the client SHOULD instead include a Prefer header field
>>
>> I don't think we need a SHOULD here for the client.
>
> What do you suggest instead?  MAY?

Or RECOMMENDED?


-- 
Kenneth Murchison
Principal Systems Software Engineer
Carnegie Mellon University

Received on Monday, 14 November 2016 14:24:29 UTC