[RPSEC] I-D Action:draft-ietf-rpsec-bgp-session-sec-req-00.txt

Internet-Drafts@ietf.org Wed, 12 December 2007 22:40 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 1J2aFJ-0002IY-5y; Wed, 12 Dec 2007 17:40:05 -0500
Received: from rpsec by megatron.ietf.org with local (Exim 4.43) id 1J2aFH-00023f-Cr for rpsec-confirm+ok@megatron.ietf.org; Wed, 12 Dec 2007 17:40:03 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1J2aFG-00020i-TR; Wed, 12 Dec 2007 17:40:02 -0500
Received: from ns1.neustar.com ([2001:503:c779:1a::9c9a:108a]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1J2aFG-00059u-H8; Wed, 12 Dec 2007 17:40:02 -0500
Received: from stiedprstage1.ietf.org (stiedprstage1.va.neustar.com [10.31.47.10]) by ns1.neustar.com (Postfix) with ESMTP id 5FD0726E4D; Wed, 12 Dec 2007 22:40:02 +0000 (GMT)
Received: from ietf by stiedprstage1.ietf.org with local (Exim 4.43) id 1J2aFG-0001fG-9m; Wed, 12 Dec 2007 17:40:02 -0500
Content-Type: Multipart/Mixed; Boundary="NextPart"
Mime-Version: 1.0
To: i-d-announce@ietf.org
From: Internet-Drafts@ietf.org
Message-Id: <E1J2aFG-0001fG-9m@stiedprstage1.ietf.org>
Date: Wed, 12 Dec 2007 17:40:02 -0500
X-Spam-Score: -1.4 (-)
X-Scan-Signature: c3a18ef96977fc9bcc21a621cbf1174b
Cc: rpsec@ietf.org
Subject: [RPSEC] I-D Action:draft-ietf-rpsec-bgp-session-sec-req-00.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 Session Security Requirements
	Author(s)       : M. Behringer
	Filename        : draft-ietf-rpsec-bgp-session-sec-req-00.txt
	Pages           : 12
	Date            : 2007-12-12

The document "BGP security requirements" (draft-ietf-rpsec-bgpsecrec)
specifies general security requirements for BGP.  However, specific
security requirements for single BGP sessions, i.e., the connection
between two BGP peers, are only touched on briefly in the section
"transport layer protection".  This document expands on this
particular aspect of BGP security, defining the security requirements
between two BGP peers.

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