{"draft":"draft-bryan-metalinkhttp-22","doc_id":"RFC6249","title":"Metalink\/HTTP: Mirrors and Hashes","authors":["A. Bryan","N. McNab","T. Tsujikawa","P. Poeml","H. Nordstrom"],"format":["ASCII","HTML"],"page_count":"21","pub_status":"PROPOSED STANDARD","status":"PROPOSED STANDARD","source":"IETF - NON WORKING GROUP","abstract":"This document specifies Metalink\/HTTP: Mirrors and Cryptographic\r\nHashes in HTTP header fields, a different way to get information that\r\nis usually contained in the Metalink XML-based download description\r\nformat.  Metalink\/HTTP describes multiple download locations\r\n(mirrors), Peer-to-Peer, cryptographic hashes, digital signatures,\r\nand other information using existing standards for HTTP header\r\nfields.  Metalink clients can use this information to make file\r\ntransfers more robust and reliable.  Normative requirements for\r\nMetalink\/HTTP clients and servers are described here.  [STANDARDS-TRACK]","pub_date":"June 2011","keywords":["[--------]","file transfer","download","link","signature","data integrity","hypertext transfer protocol","ftp","file transfer protocol","metadata","torrent"],"obsoletes":[],"obsoleted_by":[],"updates":[],"updated_by":[],"see_also":[],"doi":"10.17487\/RFC6249","errata_url":"https:\/\/www.rfc-editor.org\/errata\/rfc6249"}