[mdx] Joe on section 2.1

[Leif Johansson]

On 09/27/2013 05:08 PM, Ian Young wrote:
> On 26 Sep 2013, at 19:34, "Cantor, Scott" <cantor.2 at osu.edu> wrote:
>
>> On 9/26/13 2:14 PM, "Ian Young" <ian at iay.org.uk> wrote:
>>
>>> On re-reading this, it strikes me that this may be trickier than it first
>>> appears. Is anyone here familiar enough with the http2 draft to know
>>> whether it provides all of what we're requiring?  As an example, if http2
>>> didn't allow for ETag then saying that you could use a later version of
>>> HTTP would be contradicted given that we require that facility.
>>>
>>> I guess if no-one knows, I should try and skim that spec and get an
>>> impression.
>> I'm not sure that the value warrants the time spent, we can always
>> evaluate and update the wording once HTTP 2.0 is real and relevant.
> I think that's reasonable.  I did do a little more investigation anyway, because I was curious. I found that there is some standard guidance on this stuff provided in RFC 2616 section 3.1 ("HTTP Version") and elaborated in RFC 2145 ("Use and Interpretation of HTTP Version Numbers"), which is referenced by RFC 2616:
>
>     http://tools.ietf.org/html/rfc2145
>
> However, I also read enough of the HTTP/2.0 draft to know that you start HTTP/2.0 not by sending your version as HTTP/2.0 but by sending HTTP/1.1 and including an Upgrade header (which is also defined in HTTP/1.1).  So HTTP/2.0 is NOT intended as a linearly upgradeable protocol but a step change, and it may or may not be compatible with the rest of what we've specified when it finally hits the streets. We obviously can't reference that work in progress, though.
>
> Having read all this, I think I'd like to replace this current text:
>
>> Metadata retrieval protocol responders MUST use <xref target="RFC2616">HTTP, version 1.1</xref>
> with something like this for now:
>
> -----
> Requests from clients MUST NOT use an HTTP version prior to version 1.1.  Responders MUST reply to such requests using status code 505, "HTTP Version Not Supported".
>
> Protocol responders MUST support requests using HTTP version 1.1, and MAY support later versions.
> -----
>
> Comments?

+1
> 	-- Ian
>
>
>
>
>
> _______________________________________________
> mdx mailing list
> mdx at lists.iay.org.uk
> http://lists.iay.org.uk/listinfo.cgi/mdx-iay.org.uk

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.iay.org.uk/pipermail/mdx-iay.org.uk/attachments/20131102/592c1b7b/attachment.htm>