RFC 6249: Metalink/HTTP: Mirrors and Hashes
In plain English — editorial summary, not part of the RFC
This document specifies Metalink/HTTP: Mirrors and Cryptographic Hashes in HTTP header fields, a different way to get information that is usually contained in the Metalink XML-based download description format. Metalink/HTTP describes multiple download locations (mirrors), Peer-to-Peer, cryptographic hashes, digital signatures, and other information using existing standards for HTTP header fields. Metalink clients can use this information to make file transfers more robust and reliable. Normative requirements for Metalink/HTTP clients and servers are described here. [STANDARDS-TRACK]
Document record
- Document ID
- RFC6249
- Published
- June 2011
- Authors
- A. Bryan; N. McNab; T. Tsujikawa; P. Poeml; H. Nordstrom
- Status
- PROPOSED STANDARD
- Stream
- IETF
- Area
- —
- Pages
- 21
- Also known as
- —
Topics
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 5854The Metalink Download Description FormatCurrent
June 2010
- RFC 2585Internet X.509 Public Key Infrastructure Operational Protocols: FTP and HTTPCurrent
May 1999
- RFC 3659Extensions to FTPCurrent
March 2007
- RFC 2640Internationalization of the File Transfer ProtocolCurrent
July 1999
- RFC 2428FTP Extensions for IPv6 and NATsCurrent
September 1998
- RFC 2389Feature negotiation mechanism for the File Transfer ProtocolCurrent
August 1998
- RFC 1545FTP Operation Over Big Address Records (FOOBAR)Obsoleted
November 1993
- RFC 6283Extensible Markup Language Evidence Record Syntax (XMLERS)Current
July 2011
Also filed under
About this page
The document record above — title, authors, date, status, stream, area, relationships, DOI and errata — is imported verbatim from the public RFC Editor index. The “in plain English” section is editorial: written by The metasystema editorial team, not part of the RFC. Where the two differ, the RFC text governs.
Last checked against the RFC Editor index on . RFCs are never revised after publication; changes are issued as new documents.
Data sources · Editorial policy · Report a correction · What is an RFC?