I-D ACTION:draft-manral-rpsec-existing-crypto-00.txt

Internet-Drafts@ietf.org Wed, 04 January 2006 20:50 UTC

Received: from localhost.cnri.reston.va.us ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1EuFaG-0001ys-6k; Wed, 04 Jan 2006 15:50:12 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1EuFa8-0001tJ-T4 for i-d-announce@megatron.ietf.org; Wed, 04 Jan 2006 15:50:04 -0500
Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA24133 for <i-d-announce@ietf.org>; Wed, 4 Jan 2006 15:48:48 -0500 (EST)
Received: from [132.151.6.50] (helo=newodin.ietf.org) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1EuFfg-0008LL-HU for i-d-announce@ietf.org; Wed, 04 Jan 2006 15:55:49 -0500
Received: from mlee by newodin.ietf.org with local (Exim 4.43) id 1EuFa5-00080d-HN for i-d-announce@ietf.org; Wed, 04 Jan 2006 15:50:01 -0500
Content-Type: Multipart/Mixed; Boundary="NextPart"
Mime-Version: 1.0
To: i-d-announce@ietf.org
From: Internet-Drafts@ietf.org
Message-Id: <E1EuFa5-00080d-HN@newodin.ietf.org>
Date: Wed, 04 Jan 2006 15:50:01 -0500
X-Spam-Score: 0.4 (/)
X-Scan-Signature: 32b73d73e8047ed17386f9799119ce43
Subject: I-D ACTION:draft-manral-rpsec-existing-crypto-00.txt
X-BeenThere: i-d-announce@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
Reply-To: internet-drafts@ietf.org
List-Id: i-d-announce.ietf.org
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/i-d-announce>, <mailto:i-d-announce-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:i-d-announce@ietf.org>
List-Help: <mailto:i-d-announce-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/i-d-announce>, <mailto:i-d-announce-request@ietf.org?subject=subscribe>
Sender: i-d-announce-bounces@ietf.org
Errors-To: i-d-announce-bounces@ietf.org

A New Internet-Draft is available from the on-line Internet-Drafts directories.


	Title		: Issues with existing Cryptographic Protection 
                          Methods for Routing Protocols
	Author(s)	: V. Manral, et al.
	Filename	: draft-manral-rpsec-existing-crypto-00.txt
	Pages		: 17
	Date		: 2006-1-4
	
   Routing protocols often use cryptographic mechanisms to authenticate
   data being received from a neighboring router has not been modified
   in transit, and actually originated from the nrighboring router
   purporting to have originating the data.  Most of the cryptographic
   mechanisms rely on hash algorithms applied to the data in the routing
   protocol packet, which means the data is transported, in the clear,
   along with the has signature based on the data itself.  These
   mechanisms rely on the manual configuration of the keys used to seed,
   or build, these hash based sigantures.  This document outlines some
   of the problems with manual keying of these cryptographic algorithms.

A URL for this Internet-Draft is:
http://www.ietf.org/internet-drafts/draft-manral-rpsec-existing-crypto-00.txt

To remove yourself from the I-D Announcement list, send a message to 
i-d-announce-request@ietf.org with the word unsubscribe in the body of the message.  
You can also visit https://www1.ietf.org/mailman/listinfo/I-D-announce 
to change your subscription settings.


Internet-Drafts are also available by anonymous FTP. Login with the username
"anonymous" and a password of your e-mail address. After logging in,
type "cd internet-drafts" and then
	"get draft-manral-rpsec-existing-crypto-00.txt".

A list of Internet-Drafts directories can be found in
http://www.ietf.org/shadow.html 
or ftp://ftp.ietf.org/ietf/1shadow-sites.txt


Internet-Drafts can also be obtained by e-mail.

Send a message to:
	mailserv@ietf.org.
In the body type:
	"FILE /internet-drafts/draft-manral-rpsec-existing-crypto-00.txt".
	
NOTE:	The mail server at ietf.org can return the document in
	MIME-encoded form by using the "mpack" utility.  To use this
	feature, insert the command "ENCODING mime" before the "FILE"
	command.  To decode the response(s), you will need "munpack" or
	a MIME-compliant mail reader.  Different MIME-compliant mail readers
	exhibit different behavior, especially when dealing with
	"multipart" MIME messages (i.e. documents which have been split
	up into multiple messages), so check your local documentation on
	how to manipulate these messages.
		
		
Below is the data which will enable a MIME compliant mail reader
implementation to automatically retrieve the ASCII version of the
Internet-Draft.
ftp://ftp.ietf.org/internet-drafts/draft-manral-rpsec-existing-crypto-00.txt"><ftp://ftp.ietf.org/internet-drafts/draft-manral-rpsec-existing-crypto-00.txt>
_______________________________________________
I-D-Announce mailing list
I-D-Announce@ietf.org
https://www1.ietf.org/mailman/listinfo/i-d-announce