[rfc-dist] RFC 6249 on Metalink/HTTP: Mirrors and Hashes

rfc-editor at rfc-editor.org (rfc-editor at rfc-editor.org) Fri, 17 June 2011 16:52 UTC

From: "rfc-editor at rfc-editor.org"
Date: Fri, 17 Jun 2011 09:52:08 -0700
Subject: [rfc-dist] RFC 6249 on Metalink/HTTP: Mirrors and Hashes
Message-ID: <20110617165208.4AC1898C1F4@rfc-editor.org>

A new Request for Comments is now available in online RFC libraries.

        
        RFC 6249

        Title:      Metalink/HTTP: Mirrors and Hashes 
        Author:     A. Bryan, N. McNab,
                    T. Tsujikawa, P. Poeml,
                    H. Nordstrom
        Status:     Standards Track
        Stream:     IETF
        Date:       June 2011
        Mailbox:    anthonybryan at gmail.com, 
                    neil at nabber.org, 
                    tatsuhiro.t at gmail.com,  peter at poeml.de, 
                    henrik at henriknordstrom.net
        Pages:      21
        Characters: 45303
        Updates/Obsoletes/SeeAlso:   None

        I-D Tag:    draft-bryan-metalinkhttp-22.txt

        URL:        http://www.rfc-editor.org/rfc/rfc6249.txt

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]

This is now a Proposed Standard Protocol.

STANDARDS TRACK: This document specifies an Internet standards track
protocol for the Internet community,and requests discussion and suggestions
for improvements.  Please refer to the current edition of the Internet
Official Protocol Standards (STD 1) for the standardization state and
status of this protocol.  Distribution of this memo is unlimited.

This announcement is sent to the IETF-Announce and rfc-dist lists.
To subscribe or unsubscribe, see
  http://www.ietf.org/mailman/listinfo/ietf-announce
  http://mailman.rfc-editor.org/mailman/listinfo/rfc-dist

For searching the RFC series, see http://www.rfc-editor.org/rfcsearch.html.
For downloading RFCs, see http://www.rfc-editor.org/rfc.html.

Requests for special distribution should be addressed to either the
author of the RFC in question, or to rfc-editor at rfc-editor.org.  Unless
specifically noted otherwise on the RFC itself, all RFCs are for
unlimited distribution.


The RFC Editor Team
Association Management Solutions, LLC