Metalinks Code

A new version of I-D, draft-bryan-metalink-05.txt has been successfuly submitted by Anthony Bryan and posted to the IETF repository.

Filename: draft-bryan-metalink
Revision: 05
Title: The Metalink Download Description Format
Creation_date: 2009-01-13
WG ID: Independent Submission
Number_of_pages: 36

Hampus found things to clarify for metalink:verification & metalink:resources

Added feature to parse a HTML for metalinks and check all of them on the page.

Hampus clarifies:

If an element is listed both under metalink:files and metalink:file, then the element
under metalink:file has precedence and the metalink:files element does not apply to that particular file.

Hampus' comments.

Cleaning 2.0 branch. Better to restart from scratch.

Metalink License bugfix release, 0.3.6

A new version of I-D, draft-bryan-metalink-04.txt has been successfuly submitted by Anthony Bryan and posted to the IETF repository.

Filename: draft-bryan-metalink
Revision: 04
Title: The Metalink Download Description Format
Creation_date: 2008-12-31
WG ID: Independent Submission
Number_of_pages: 36

Abstract:
This document specifies Metalink Documents, an XML-based download
description format.

hash discussion with Nils.

Cryptographic Hashes

Currently, some of the hash types defined in the IANA registry named
"Hash Function Textual Names" are considered insecure. These include
the whole Message Digest family of algorithms which are not suitable
for cryptographically strong verification. Malicious people could
provide files that appear to be identical to another file because of
a collision, i.e. the weak cryptographic hashes match.

Metalink Generators and Processors supporting verification SHOULD at
least implement "sha-1" which is SHA1, as specified in [RFC3174].

Readme GPLv2 to GPLv3