Subject: [RPSEC] Draft minutes for Minneapolis '02 BOF

From: Russ White <[email-masked]>
Date: Sat, 23 Mar 2002 07:15:31 -0500 (EST)

Y'all:

Draft minutes are here:

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

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

Russ

__________________________________
[email-masked] 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
[email-masked]
https://www1.ietf.org/mailman/listinfo/rpsec