[CGA-EXT] FW: RFC 4982 on Support for Multiple Hash Algorithms in Cryptographically Generated Addresses (CGAs)
Jari Arkko <jari.arkko@piuha.net> Mon, 23 July 2007 23:14 UTC
Return-path: <cga-ext-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1ID76h-00035C-Dw; Mon, 23 Jul 2007 19:14:27 -0400
Received: from [10.90.34.44] (helo=chiedprmail1.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1ID76g-00034s-OR for cga-ext@ietf.org; Mon, 23 Jul 2007 19:14:26 -0400
Received: from p130.piuha.net ([193.234.218.130]) by chiedprmail1.ietf.org with esmtp (Exim 4.43) id 1ID76g-0005Jq-1D for cga-ext@ietf.org; Mon, 23 Jul 2007 19:14:26 -0400
Received: from p130.piuha.net (localhost [127.0.0.1]) by p130.piuha.net (Postfix) with ESMTP id 4631C198680 for <cga-ext@ietf.org>; Tue, 24 Jul 2007 02:14:25 +0300 (EEST)
Received: from [127.0.0.1] (p130.piuha.net [193.234.218.130]) by p130.piuha.net (Postfix) with ESMTP id B400B19867D for <cga-ext@ietf.org>; Tue, 24 Jul 2007 02:14:24 +0300 (EEST)
Message-ID: <46A53642.6030704@piuha.net>
Date: Mon, 23 Jul 2007 18:14:10 -0500
From: Jari Arkko <jari.arkko@piuha.net>
User-Agent: Thunderbird 1.5.0.12 (X11/20070604)
MIME-Version: 1.0
To: cga-ext@ietf.org
References: <20070723184530.764D1DA97C@bosco.isi.edu>
In-Reply-To: <20070723184530.764D1DA97C@bosco.isi.edu>
Content-Type: text/plain; charset="ISO-8859-1"
Content-Transfer-Encoding: 7bit
X-Virus-Scanned: ClamAV using ClamSMTP
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 8f374d0786b25a451ef87d82c076f593
Subject: [CGA-EXT] FW: RFC 4982 on Support for Multiple Hash Algorithms in Cryptographically Generated Addresses (CGAs)
X-BeenThere: cga-ext@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: CGA and SeND Extensions <cga-ext.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/cga-ext>, <mailto:cga-ext-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www1.ietf.org/pipermail/cga-ext>
List-Post: <mailto:cga-ext@ietf.org>
List-Help: <mailto:cga-ext-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/cga-ext>, <mailto:cga-ext-request@ietf.org?subject=subscribe>
Errors-To: cga-ext-bounces@ietf.org
FYI > A new Request for Comments is now available in online RFC libraries. > > > > > > RFC 4982 > > > > Title: Support for Multiple Hash Algorithms > > in Cryptographically Generated Addresses (CGAs) > > Author: M. Bagnulo, J. Arkko > > Status: Standards Track > > Date: July 2007 > > Mailbox: marcelo@it.uc3m.es, > > jari.arkko@ericsson.com > > Pages: 9 > > Characters: 20961 > > Updates: RFC3972 > > See-Also: > > > > I-D Tag: draft-bagnulo-multiple-hash-cga-03.txt > > > > URL: http://www.rfc-editor.org/rfc/rfc4982.txt > > > > This document analyzes the implications of recent attacks on commonly > > used hash functions on Cryptographically Generated Addresses (CGAs) > > and updates the CGA specification to support multiple hash > > algorithms. [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 list and the RFC-DIST list. > > Requests to be added to or deleted from the IETF distribution list > > should be sent to IETF-REQUEST@IETF.ORG. Requests to be > > added to or deleted from the RFC-DIST distribution list should > > be sent to RFC-DIST-REQUEST@RFC-EDITOR.ORG. > > > > Details on obtaining RFCs via FTP or EMAIL may be obtained by sending > > an EMAIL message to rfc-info@RFC-EDITOR.ORG with the message body > > > > help: ways_to_get_rfcs. For example: > > > > To: rfc-info@RFC-EDITOR.ORG > > Subject: getting rfcs > > > > help: ways_to_get_rfcs > > > > Requests for special distribution should be addressed to either the > > author of the RFC in question, or to RFC-Manager@RFC-EDITOR.ORG. Unless > > specifically noted otherwise on the RFC itself, all RFCs are for > > unlimited distribution. > > > > Submissions for Requests for Comments should be sent to > > RFC-EDITOR@RFC-EDITOR.ORG. Please consult RFC 2223, Instructions to RFC > > Authors, for further information. > > > > > > The RFC Editor Team > > USC/Information Sciences Institute > > > > ... > > > > > > _______________________________________________ > IETF-Announce mailing list > IETF-Announce@ietf.org > https://www1.ietf.org/mailman/listinfo/ietf-announce > > > _______________________________________________ CGA-EXT mailing list CGA-EXT@ietf.org https://www1.ietf.org/mailman/listinfo/cga-ext