RFC 6249 on Metalink/HTTP: Mirrors and Hashes
rfc-editor@rfc-editor.org Fri, 17 June 2011 16:52 UTC
Return-Path: <wwwrun@rfc-editor.org>
X-Original-To: ietf-announce@ietfa.amsl.com
Delivered-To: ietf-announce@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id EE98D11E80E2 for <ietf-announce@ietfa.amsl.com>; Fri, 17 Jun 2011 09:52:09 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.3
X-Spam-Level:
X-Spam-Status: No, score=-102.3 tagged_above=-999 required=5 tests=[AWL=-0.300, BAYES_00=-2.599, J_CHICKENPOX_93=0.6, NO_RELAYS=-0.001, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id S0FTb5lDIuZS for <ietf-announce@ietfa.amsl.com>; Fri, 17 Jun 2011 09:52:09 -0700 (PDT)
Received: from rfc-editor.org (rfc-editor.org [IPv6:2001:1890:1112:1::2f]) by ietfa.amsl.com (Postfix) with ESMTP id 9F87411E80DF for <ietf-announce@ietf.org>; Fri, 17 Jun 2011 09:52:08 -0700 (PDT)
Received: by rfc-editor.org (Postfix, from userid 30) id 4AC1898C1F4; Fri, 17 Jun 2011 09:52:08 -0700 (PDT)
To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org
Subject: RFC 6249 on Metalink/HTTP: Mirrors and Hashes
From: rfc-editor@rfc-editor.org
Message-Id: <20110617165208.4AC1898C1F4@rfc-editor.org>
Date: Fri, 17 Jun 2011 09:52:08 -0700
Cc: rfc-editor@rfc-editor.org
X-BeenThere: ietf-announce@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "IETF announcement list. No discussions." <ietf-announce.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf-announce>, <mailto:ietf-announce-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf-announce>
List-Post: <mailto:ietf-announce@ietf.org>
List-Help: <mailto:ietf-announce-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf-announce>, <mailto:ietf-announce-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 17 Jun 2011 16:52:10 -0000
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@gmail.com,
neil@nabber.org,
tatsuhiro.t@gmail.com, peter@poeml.de,
henrik@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@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