Metalink/XML Clients, Publishers, and Caches
draft-bryan-metalink-client-01
| Document | Type |
This is an older version of an Internet-Draft whose latest revision state is "Expired".
Expired & archived
|
|
|---|---|---|---|
| Authors | Anthony Bryan , Tatsuhiro Tsujikawa , Neil McNab | ||
| Last updated | 2013-01-17 (Latest revision 2012-07-16) | ||
| RFC stream | (None) | ||
| Formats | |||
| Stream | Stream state | (No stream defined) | |
| Consensus boilerplate | Unknown | ||
| RFC Editor Note | (None) | ||
| IESG | IESG state | Expired | |
| Telechat date | (None) | ||
| Responsible AD | (None) | ||
| Send notices to | (None) |
This Internet-Draft is no longer active. A copy of the expired Internet-Draft is available in these formats:
Abstract
This document specifies behavior for Metalink/XML clients, publishers, and proxy caches. way to get information that is usually contained in the Metalink XML-based download description format. Metalink XML files contain multiple download locations (mirrors and Peer-to-Peer), cryptographic hashes, digital signatures, and other information. Metalink clients can use this information to make file transfers more robust and reliable. Normative requirements for Metalink/XML clients, publishers, and proxy caches are described here.
Authors
Anthony Bryan
Tatsuhiro Tsujikawa
Neil McNab
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)