[RPSEC] No RPSEC meeting in Vancouver (IETF64)

Tony Tauber <ttauber@1-4-5.net> Thu, 27 October 2005 18:55 UTC

Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1EVCu8-0003Wr-WD; Thu, 27 Oct 2005 14:55:13 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1EVCu6-0003Wm-Sk for rpsec@megatron.ietf.org; Thu, 27 Oct 2005 14:55:10 -0400
Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA22394 for <rpsec@ietf.org>; Thu, 27 Oct 2005 14:54:53 -0400 (EDT)
Received: from m106.maoz.com ([205.167.76.9]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1EVD7W-0007O2-LV for rpsec@ietf.org; Thu, 27 Oct 2005 15:09:03 -0400
Received: from m106.maoz.com (localhost.localdomain [127.0.0.1]) by m106.maoz.com (8.13.4/8.13.4) with ESMTP id j9RIt1Ht011200 for <rpsec@ietf.org>; Thu, 27 Oct 2005 11:55:01 -0700
Received: from localhost (ttauber@localhost) by m106.maoz.com (8.13.4/8.12.11/Submit) with ESMTP id j9RIt1VJ011197 for <rpsec@ietf.org>; Thu, 27 Oct 2005 11:55:01 -0700
X-Authentication-Warning: m106.maoz.com: ttauber owned process doing -bs
Date: Thu, 27 Oct 2005 11:55:01 -0700
From: Tony Tauber <ttauber@1-4-5.net>
X-X-Sender: ttauber@m106.maoz.com
To: rpsec@ietf.org
Message-ID: <Pine.LNX.4.64.0510271120550.942@m106.maoz.com>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset="US-ASCII"; format="flowed"
X-Spam-Score: 0.0 (/)
X-Scan-Signature: f60d0f7806b0c40781eee6b9cd0b2135
Subject: [RPSEC] No RPSEC meeting in Vancouver (IETF64)
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>
Sender: rpsec-bounces@ietf.org
Errors-To: rpsec-bounces@ietf.org

Hi All,

Since no one has brought forth new agenda items and other things can
be effectively worked on through the mailing list, RPSEC will not be
meeting at IETF64 in Vancouver.

I'd like to call people's attention, however, to the
SIDR (Secure Inter-Domain Routing) BOF which is scheduled for Thursday
morning.  The thought on the part of the Routing ADs is to start a
parallel effort on possible protocol changes even while some details
of the requirements are being ironed out.

The focus for now will consider points where there does appear to be
clear consensus for possible work.  RPSEC isn't chartered with
protocol changes and IDR has much other work to keep it busy.  For
these reasons, the new BOF is being spun up.

See detailed BOF announcement below.

Cheers,

Tony
----
Name of the BOF: Secure Interdomain Routing (SIDR)
Area: Routing
Chairs: Geoff Houston
Sponsoring ADs: Alex Zinin, Bill Fenner

The RPSEC WG has been working on security requirements for the
Internet routing system in general and the BGP routing protocol in
particular. While some progress has been made, formulation of the
complete set of requirements can take some time. At the same time,
there's a shared understanding in the IETF community that work on
securing interdomain routing needs to start, as it will take time to
develop implementations and see first deployments.

The goal of this BOF is to discuss creation of an extensible
interdomain routing security architecture that would allow to
incrementally define security features to BGP as the discussion on
requirements progresses and new mechanisms become necessary.  The
expected outcome is an agreement on the initial set of security
features that such an architecture would provide.  It is not a goal of
this BOF to choose between SBGP and SoBGP.


Agenda:
  1. Introduction and current status                        [15m]
  2. Brief overview of currently proposed solutions         [30m]
  3. Description of proposed work                           [15m]
  4. Discussion                                             [60m]

Mailing list: sidr@ietf.org
To subscribe: sidr-request@ietf.org

Reading material:

  Requirements:

  http://www.ietf.org/internet-drafts/draft-ietf-rpsec-routing-threats-07.txt
  http://www.ietf.org/internet-drafts/draft-ietf-rpsec-bgpsecrec-02.txt

  SoBGP:
    http://www.ietf.org/internet-drafts/draft-white-sobgp-architecture-01.txt
    http://www.ietf.org/internet-drafts/draft-ng-sobgp-bgp-extensions-01.txt
    http://www.ietf.org/internet-drafts/draft-weis-sobgp-certificates-01.txt

  SBGP:
    SBGP web page: http://www.net-tech.bbn.com/sbgp/sbgp-index.html

_______________________________________________
RPSEC mailing list
RPSEC@ietf.org
https://www1.ietf.org/mailman/listinfo/rpsec