From rpsec-admin@ietf.org  Tue Mar 12 17:16:38 2002
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA10169
	for <rpsec-archive@odin.ietf.org>; Tue, 12 Mar 2002 17:16:38 -0500 (EST)
Received: from optimus.ietf.org (localhost [127.0.0.1])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id RAA18264
	for <rpsec-web-archive@ietf.org>; Tue, 12 Mar 2002 17:16:38 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id RAA18248
	for <rpsec@optimus.ietf.org>; Tue, 12 Mar 2002 17:16:37 -0500 (EST)
Received: from cnri.reston.va.us (cnri.reston.va.us [132.151.1.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA10160
	for <rpsec@ietf.org>; Tue, 12 Mar 2002 17:16:24 -0500 (EST)
Received: from hubris.cnri.reston.va.us (cnri-7-251.cnri.reston.va.us [132.151.7.251])
	by cnri.reston.va.us (8.11.6/8.11.3) with ESMTP id g2CMGRF12594
	for <rpsec@ietf.org>; Tue, 12 Mar 2002 17:16:28 -0500 (EST)
Message-Id: <5.0.0.25.2.20020312171123.00adab20@mailbox.cnri.reston.va.us>
X-Sender: gcunning@mailbox.cnri.reston.va.us
X-Mailer: QUALCOMM Windows Eudora Version 5.0
Date: Tue, 12 Mar 2002 17:11:30 -0500
To: rpsec@ietf.org
From: Greg Cunningham <gcunning@foretec.com>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
Subject: [Rpsec] test 3
Sender: rpsec-admin@ietf.org
Errors-To: rpsec-admin@ietf.org
X-Mailman-Version: 1.0
Precedence: bulk
List-Id: Routing Protocol Security Requirements  <rpsec.ietf.org>
X-BeenThere: rpsec@ietf.org

test 3


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


From rpsec-admin@ietf.org  Sat Mar 23 09:32:53 2002
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA21965
	for <rpsec-archive@odin.ietf.org>; Sat, 23 Mar 2002 09:32:53 -0500 (EST)
Received: from optimus.ietf.org (localhost [127.0.0.1])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id JAA00635;
	Sat, 23 Mar 2002 09:32:48 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id HAA14418
	for <rpsec@optimus.ietf.org>; Sat, 23 Mar 2002 07:16:03 -0500 (EST)
Received: from cisco.com (uzura.cisco.com [64.102.17.77])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id HAA20928
	for <rpsec@ietf.org>; Sat, 23 Mar 2002 07:15:59 -0500 (EST)
Received: from ruwhite-u10.cisco.com (ruwhite-u10.cisco.com [64.102.48.251])
	by cisco.com (8.8.8/2.6/Cisco List Logging/8.8.8) with ESMTP id HAA12083
	for <rpsec@ietf.org>; Sat, 23 Mar 2002 07:15:31 -0500 (EST)
Date: Sat, 23 Mar 2002 07:15:31 -0500 (EST)
From: Russ White <ruwhite@cisco.com>
Reply-To: Russ White <riw@cisco.com>
To: rpsec@ietf.org
Message-ID: <Pine.GSO.4.21.0203230712390.2937-100000@ruwhite-u10.cisco.com>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Subject: [RPSEC] Draft minutes for Minneapolis '02 BOF
Sender: rpsec-admin@ietf.org
Errors-To: rpsec-admin@ietf.org
X-Mailman-Version: 1.0
Precedence: bulk
List-Id: Routing Protocol Security Requirements  <rpsec.ietf.org>
X-BeenThere: rpsec@ietf.org

Y'all:

Draft minutes are here:

http://www.riw.to/rpsec/minutes-draft-mar02-01.txt

And below.... Comments/thoughts/flames welcome.

Russ

__________________________________
riw@cisco.com CCIE <>< Grace Alone

-----

Routing Protocol Security BOF
Minutes from March 2002 IETF
Minneapolis, Minnesota

-----

Open the Meeting

Presentation: Demensions of Routing Security 
  Radia Perlman
  http://www.riw.to/rpsec/perlman-rpsec-mar02.pdf

Presentation: Routing Protocol Security Requirements
  Sandy Murphy
  http://www.riw.to/rpsec/murphy-rpsec-mar02.ppt

Comments from the microphone on the presenations
  (I probably didn't catch all of these)
  Other things that could be detected
    Anomolous route distribution
    Router which has been broken in to
      It's very hard to detect a subverting router (Radia)
    BGP can detect anomolies in data
  Registry of data isn't necessarily fast enough
    Things sometimes change too fast for the database to keep up
    9/11, for instance
  Wireless topology and network mobility are important
   considerations

Charter
  http://www.riw.to/rpsec/charter-rpsec-mar02.ppt
  http://www.riw.to/rpsec/charter-rpsec-draft-06.txt

Comments from the micropohne on the charter
  What is it we're after? Attacks, mistakes, or....? (Sandy)
    Everything which affects routing protocols security at a 
     protocol level
  Comments from Alex Z on the BOF
  Should we include attacking routing platforms?
    No, this is outside the protocols themselves
  Routing protocol authors need security direction
  Instead of focusing on requirements, focus on assets and risks
  Multicast routing security
    The MSEC group focuses on secure distribution in multicast
    Multicast routing protocol security should be included here
  Where should specific mechanisms be provided?
    Specific protocol changes should be done in the protocol
     working groups
  Frameworks should be here
  Routing protocols security related drafts can be presented here
   to focus on the security aspects, but they won't be WG items
  Should look beyond requirements, into architectures
    This relates specifically to building security into the
     architecture of the protocols themselves
  It's good to have a specific place to focus interaction between
   routing protocols and security folks
  Make certain we have a direction (Sue H)
  Survivability should be addressed
  If we document threats without documenting solutions, are we
   helping or not?

Should this be a working group?
  Concensus through hum

Should we work on charter before presenting to IESG?
  Concensus through hum  




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


From rpsec-admin@ietf.org  Sun Mar 31 07:06:17 2002
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id HAA22595
	for <rpsec-archive@odin.ietf.org>; Sun, 31 Mar 2002 07:06:17 -0500 (EST)
Received: from optimus.ietf.org (localhost [127.0.0.1])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id HAA21214;
	Sun, 31 Mar 2002 07:05:17 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id HAA21178
	for <rpsec@optimus.ietf.org>; Sun, 31 Mar 2002 07:05:15 -0500 (EST)
Received: from cisco.com (uzura.cisco.com [64.102.17.77])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id HAA22580
	for <rpsec@ietf.org>; Sun, 31 Mar 2002 07:05:13 -0500 (EST)
Received: from ruwhite-u10.cisco.com (ruwhite-u10.cisco.com [64.102.48.251])
	by cisco.com (8.8.8/2.6/Cisco List Logging/8.8.8) with ESMTP id HAA27278
	for <rpsec@ietf.org>; Sun, 31 Mar 2002 07:04:44 -0500 (EST)
Date: Sun, 31 Mar 2002 07:04:44 -0500 (EST)
From: Russ White <ruwhite@cisco.com>
Reply-To: Russ White <riw@cisco.com>
To: rpsec@ietf.org
Message-ID: <Pine.GSO.4.21.0203310703560.4891-100000@ruwhite-u10.cisco.com>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Subject: [RPSEC] test.... (nonull)
Sender: rpsec-admin@ietf.org
Errors-To: rpsec-admin@ietf.org
X-Mailman-Version: 1.0
Precedence: bulk
List-Id: Routing Protocol Security Requirements  <rpsec.ietf.org>
X-BeenThere: rpsec@ietf.org


Testing.... one.... two..... three.... <squeeekkk!>

Can everyone hear me in the back?

:-)

Russ


__________________________________
riw@cisco.com CCIE <>< Grace Alone



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


