right, that's what we're doing here, making them a bit more friendly with the web.
good point, there should be a file parameter for selecting one file out of possibly multiple files from a metadata file.
I forgot to include an example here too:
Etag: "thvDyvhfIqlvFe+A9MYgxAfm1q5=" Link: <http://www2.example.com/example.ext>; rel="duplicate" Link: <ftp://ftp.example.com/example.ext>; rel="duplicate" Link: <http://example.com/example.ext.torrent>; rel="describedby"; type="application/x-bittorrent" Link: <http://example.com/example.ext.metalink>; rel="describedby"; type="application/metalink4+xml" Link: <http://example.com/example.ext.asc>; rel="describedby"; type="application/pgp-signature" Digest: SHA-256=MWVkMWQxYTRiMzk5MDQ0MzI3NGU5NDEyZTk5OWY1ZGFmNzgyZTJlO DYzYjRjYzFhOTlmNTQwYzI2M2QwM2U2MQ==
this isn't a BEP exactly, but it's on the way to becoming an RFC.
basically this is a collection of recommendations for improving downloads based on other Internet standards.
the gist is that you get mirrors, p2p info including torrents, hashes, & signatures in HTTP headers. the type of stuff download managers/p2p clients would transparently use...multi-source downloads, error repair, etc.
for instance, a user could start downloading an ISO using an HTTP URI, then the download client could switch over to BitTorrent to finish the download, while also getting a chunk from an FTP server too.