W3C home > Mailing lists > Public > ietf-http-wg@w3.org > January to March 2011

Re: draft-bryan-metalinkhttp-18.txt

From: Julian Reschke <julian.reschke@gmx.de>
Date: Wed, 19 Jan 2011 21:26:38 +0100
Message-ID: <4D3748FE.801@gmx.de>
To: Anthony Bryan <anthonybryan@gmail.com>
CC: ietf-http-wg@w3.org, draft-bryan-metalinkhttp@tools.ietf.org
On 19.01.2011 20:58, Anthony Bryan wrote:
> ...
>>>> Note: it's unfortunate that there doesn't seem to be a registered media
>>>> type
>>>> for torrent files.
>>>
>>> true. I'd fix that if I could. :)
>>
>> Go ahead. You can :-)
>
> any pointers?
> ...

Well, write a spec with a media type reg (yes, not trivial)...

>>>>    ...
>>>>
>>>>    Metalink resources include a Link header [RFC5988] to present a list
>>>>    of mirrors in the response to a client request for the resource.
>>>>    Metalink servers MUST include the cryptographic hash of a resource
>>>>    via Instance Digests in HTTP [RFC3230].  Valid algorithms are found
>>>>    in the IANA registry named "Hypertext Transfer Protocol (HTTP) Digest
>>>>    Algorithm Values" at
>>>>    http://www.iana.org/assignments/http-dig-alg/http-dig-alg.xhtml .
>>>>
>>>> Surplus whitespace. Maybe put the URI into angle brackets.
>>>
>>> I've also seen registries cited in the references. is that better?
>>
>> I think in-lining has a better chance to survive the RFC Editor changes (I
>> believe they don't want to have the URIs in the document at all).
>
> I guess you can always search by the registry name but the URI seems useful?
> ...

It does; I'd leave it in.

>>> ...
>> Also, it appears that you require more than what's needed.
>>
>> For instance, why would it be a problem when byte-for-byte identical files
>> have different ETags on the same server? I think what's relevant is the
>> requirement for the mirror files, not any additional requirements for other
>> files^h^h^h^h^hresources on the server.
>
> is this better?
>
> "To have the same ETag policy means that ETags are synchronized across
> servers for duplicate resources, i.e. byte-for-byte identical files
> will have the same ETag on mirrors that they have on the Metalink
> server."
> ...

It probably would be good to state that this only applies to files that 
are mirrored (and not just "anything" on that server).

 > ...

Best regards, Julian
Received on Wednesday, 19 January 2011 20:27:33 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Friday, 27 April 2012 06:51:36 GMT