W3C home > Mailing lists > Public > ietf-http-wg@w3.org > July to September 2008

Re: [APPS-REVIEW] Metalink XML Download Description Format (draft-bryan-metalink-01)

From: Anthony Bryan <anthonybryan@gmail.com>
Date: Sat, 20 Sep 2008 19:26:22 -0400
Message-ID: <bb9e09ee0809201626s6b98479cj694ab373624dc9c4@mail.gmail.com>
To: "general discussion of application-layer protocols" <discuss@apps.ietf.org>, "Applications Review List" <apps-review@ietf.org>, xml-dev@lists.xml.org, ietf-http-wg@w3.org

Greetings,

An updated Internet Draft for Metalink is available at
http://tools.ietf.org/html/draft-bryan-metalink-03
with interim revisions at
http://metalinks.svn.sourceforge.net/viewvc/metalinks/internetdraft/ .

We're looking for review and public comments.

  Metalink is an XML-based document format that describes a file or
  lists of files to be added to a download queue.  Lists are composed
  of a number of files, each with an extensible set of attached
  metadata.  For example, each file can have a description, checksum,
  and list of URIs that it is available from.

  The primary use case that Metalink addresses is the description of
  downloadable content in a format so download agents can act
  intelligently and recover from common errors with little or no user
  interaction necessary.  These errors can include multiple servers
  going down and data corrupted in transmission.

This updated version incorporates comments:

- urn:ietf:params:xml:ns:metalink namespace & registration.
- IANA "Operating System Names" registry for listing the OS that a
file listed in a metalink is for. This registry would need to be
updated to be useful.
- new "Client Implementation Considerations" . Currently, this section
mentions transparent content negotiation.

Issues:
- Inclusion of digital signatures other than PGP of files listed in
the Metalink. (Only PGP is currently supported). What do we need to
add and how might we need to restructure this for other digital
signatures to be included/used?
- Proxies. If a file listed in a metalink is already in a cache, but a
different URI is used then I assume it won't be recognized and will be
requested again since it seems to be an uncached file. I'm wondering
if the checksums in a metalink or something else could be used to see
if the file is the same or not.

Thank you,

-- 
(( Anthony Bryan ... Metalink [ http://www.metalinker.org ]
 )) Easier, More Reliable, Self Healing Downloads
Received on Saturday, 20 September 2008 23:27:01 GMT

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