[RPSEC] I-D ACTION:draft-ietf-rpsec-bgpsecrec-09.txt

Internet-Drafts@ietf.org Mon, 19 November 2007 20:44 UTC

Return-path: <rpsec-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1IuDTN-0006Rr-2M; Mon, 19 Nov 2007 15:44:01 -0500
Received: from rpsec by megatron.ietf.org with local (Exim 4.43) id 1IuDTM-0006PQ-79 for rpsec-confirm+ok@megatron.ietf.org; Mon, 19 Nov 2007 15:44:00 -0500
Received: from [10.90.34.44] (helo=chiedprmail1.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1IuDTL-0006PH-Rm; Mon, 19 Nov 2007 15:43:59 -0500
Received: from ns3.neustar.com ([156.154.24.138]) by chiedprmail1.ietf.org with esmtp (Exim 4.43) id 1IuDTL-0001fC-Fb; Mon, 19 Nov 2007 15:43:59 -0500
Received: from stiedprstage1.ietf.org (stiedprstage1.va.neustar.com [10.31.47.10]) by ns3.neustar.com (Postfix) with ESMTP id 664C9175BF; Mon, 19 Nov 2007 20:15:02 +0000 (GMT)
Received: from ietf by stiedprstage1.ietf.org with local (Exim 4.43) id 1IuD1J-0003gg-T7; Mon, 19 Nov 2007 15:15: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: <E1IuD1J-0003gg-T7@stiedprstage1.ietf.org>
Date: Mon, 19 Nov 2007 15:15:01 -0500
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 73734d43604d52d23b3eba644a169745
Cc: rpsec@ietf.org
Subject: [RPSEC] I-D ACTION:draft-ietf-rpsec-bgpsecrec-09.txt
X-BeenThere: rpsec@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Routing Protocol Security Requirements <rpsec.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/rpsec>, <mailto:rpsec-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www1.ietf.org/pipermail/rpsec>
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>
Errors-To: rpsec-bounces@ietf.org

A New Internet-Draft is available from the on-line Internet-Drafts 
directories.
This draft is a work item of the Routing Protocol Security Requirements Working Group of the IETF.

	Title		: BGP Security Requirements
	Author(s)	: B. Christian, T. Tauber
	Filename	: draft-ietf-rpsec-bgpsecrec-09.txt
	Pages		: 19
	Date		: 2007-11-19
	
The security of BGP, the Border Gateway Protocol, is critical to the
   proper operation of large-scale internetworks, both public and
   private.  While securing the information transmitted between two BGP
   speakers is a relatively easy technical matter, securing BGP, as a
   routing system, is more complex.  This document describes a set of
   requirements for securing BGP, including communications between BGP
   speakers, and the routing information carried within BGP.

A URL for this Internet-Draft is:
http://www.ietf.org/internet-drafts/draft-ietf-rpsec-bgpsecrec-09.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-ietf-rpsec-bgpsecrec-09.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-ietf-rpsec-bgpsecrec-09.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-ietf-rpsec-bgpsecrec-09.txt"><ftp://ftp.ietf.org/internet-drafts/draft-ietf-rpsec-bgpsecrec-09.txt>
_______________________________________________
RPSEC mailing list
RPSEC@ietf.org
https://www1.ietf.org/mailman/listinfo/rpsec