[RPSEC] I-D ACTION:draft-beard-rpsec-routing-threats-01.txt

Internet-Drafts@ietf.org Wed, 05 March 2003 11:36 UTC

Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id GAA26932 for <rpsec-archive@odin.ietf.org>; Wed, 5 Mar 2003 06:36:50 -0500 (EST)
Received: (from mailnull@localhost) by www1.ietf.org (8.11.6/8.11.6) id h25Bllh17763 for rpsec-archive@odin.ietf.org; Wed, 5 Mar 2003 06:47:47 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h25Bll517760 for <rpsec-web-archive@optimus.ietf.org>; Wed, 5 Mar 2003 06:47:47 -0500
Received: from www1.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id GAA26902 for <rpsec-web-archive@ietf.org>; Wed, 5 Mar 2003 06:36:19 -0500 (EST)
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h25BkZ517592; Wed, 5 Mar 2003 06:46:35 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h25BeL516912 for <rpsec@optimus.ietf.org>; Wed, 5 Mar 2003 06:40:21 -0500
Received: from CNRI.Reston.VA.US (localhost [127.0.0.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id GAA25589; Wed, 5 Mar 2003 06:28:53 -0500 (EST)
Message-Id: <200303051128.GAA25589@ietf.org>
Mime-Version: 1.0
Content-Type: Multipart/Mixed; Boundary="NextPart"
To: IETF-Announce:;
CC: rpsec@ietf.org
From: Internet-Drafts@ietf.org
Reply-to: Internet-Drafts@ietf.org
Date: Wed, 05 Mar 2003 06:28:52 -0500
Subject: [RPSEC] I-D ACTION:draft-beard-rpsec-routing-threats-01.txt
Sender: rpsec-admin@ietf.org
Errors-To: rpsec-admin@ietf.org
X-BeenThere: rpsec@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/rpsec>, <mailto:rpsec-request@ietf.org?subject=unsubscribe>
List-Id: Routing Protocol Security Requirements <rpsec.ietf.org>
List-Post: <mailto:rpsec@ietf.org>
List-Help: <mailto:rpsec-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/rpsec>, <mailto:rpsec-request@ietf.org?subject=subscribe>

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


	Title		: Generic Threats to Routing Protocols
	Author(s)	: B. Beard et al.
	Filename	: draft-beard-rpsec-routing-threats-01.txt
	Pages		: 34
	Date		: 2003-3-4
	
Routing protocols are subject to attacks that can harm individual
users or the network operations as a whole.  The lack of a common set
of security requirements has led to the use in existing routing
protocol of a variety of different security solutions, which provide
various levels of security coverage.
The RPSEC working group intends to deliver in a separate document a
set of security requirements for consideration of routing protocol
designers.  The first step in developing the security requirements is
to analyze the threats that face routing protocols.  This document
describes the threats, including threat sources and capabilities,
threat actions, and threat consequences as well as a breakdown of
routing functions that might be separately attacked.

A URL for this Internet-Draft is:
http://www.ietf.org/internet-drafts/draft-beard-rpsec-routing-threats-01.txt

To remove yourself from the IETF Announcement list, send a message to 
ietf-announce-request with the word unsubscribe in the body of the message.

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-beard-rpsec-routing-threats-01.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-beard-rpsec-routing-threats-01.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-beard-rpsec-routing-threats-01.txt"><ftp://ftp.ietf.org/internet-drafts/draft-beard-rpsec-routing-threats-01.txt>