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

Tony Tauber <ttauber@1-4-5.net> Mon, 17 November 2008 03:54 UTC

Return-Path: <rpsec-bounces@ietf.org>
X-Original-To: rpsec-archive@megatron.ietf.org
Delivered-To: ietfarch-rpsec-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 798943A683F; Sun, 16 Nov 2008 19:54:10 -0800 (PST)
X-Original-To: rpsec@core3.amsl.com
Delivered-To: rpsec@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 5D07C3A683F for <rpsec@core3.amsl.com>; Sun, 16 Nov 2008 19:54:09 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level:
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id V54EYPti5DyJ for <rpsec@core3.amsl.com>; Sun, 16 Nov 2008 19:54:08 -0800 (PST)
Received: from m106.maoz.com (m106.maoz.com [205.167.76.9]) by core3.amsl.com (Postfix) with ESMTP id 9FAA23A681C for <rpsec@ietf.org>; Sun, 16 Nov 2008 19:54:08 -0800 (PST)
Received: from m106.maoz.com (localhost [127.0.0.1]) by m106.maoz.com (8.14.3/8.14.3/Debian-4) with ESMTP id mAH3s770009448; Sun, 16 Nov 2008 19:54:07 -0800
Received: (from ttauber@localhost) by m106.maoz.com (8.14.3/8.14.3/Submit) id mAH3s7ib009447; Sun, 16 Nov 2008 19:54:07 -0800
Date: Sun, 16 Nov 2008 19:54:07 -0800
From: Tony Tauber <ttauber@1-4-5.net>
To: rpsec@ietf.org, Russ White <riw@cisco.com>
Message-ID: <20081117035407.GB28269@1-4-5.net>
References: <20081103183001.907703A6BB4@core3.amsl.com>
MIME-Version: 1.0
Content-Disposition: inline
In-Reply-To: <20081103183001.907703A6BB4@core3.amsl.com>
User-Agent: Mutt/1.5.18 (2008-05-17)
Subject: Re: [RPSEC] I-D ACTION:draft-ietf-rpsec-bgpsecrec-10.txt
X-BeenThere: rpsec@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Routing Protocol Security Requirements <rpsec.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/rpsec>, <mailto:rpsec-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/pipermail/rpsec>
List-Post: <mailto:rpsec@ietf.org>
List-Help: <mailto:rpsec-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/rpsec>, <mailto:rpsec-request@ietf.org?subject=subscribe>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: rpsec-bounces@ietf.org
Errors-To: rpsec-bounces@ietf.org

Hi Folks,

[WG Chair hat off]

The WG is winding down but it'd be nice to just put a stake in this
draft.

Russ, can we move forward with this?

Unfortunately, I won't be in Minneapolis.

Thanks,

Tony

On Mon, Nov 03, 2008 at 10:30:01AM -0800, Internet-Drafts@ietf.org wrote:
> 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-10.txt
> 	Pages		: 18
> 	Date		: 2008-11-3
> 	
> 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 and the routing information carried
>    within BGP.
_______________________________________________
RPSEC mailing list
RPSEC@ietf.org
https://www.ietf.org/mailman/listinfo/rpsec