From mailnull@www1.ietf.org  Sun Sep  1 06:16:35 2002
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id GAA12676
	for <rpsec-archive@odin.ietf.org>; Sun, 1 Sep 2002 06:16:35 -0400 (EDT)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id g81AHcX24490
	for rpsec-archive@odin.ietf.org; Sun, 1 Sep 2002 06:17:38 -0400
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g81AHco24487
	for <rpsec-web-archive@optimus.ietf.org>; Sun, 1 Sep 2002 06:17:38 -0400
From: sip-admin@ietf.org
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id GAA12640
	for <rpsec-web-archive@ietf.org>; Sun, 1 Sep 2002 06:16:05 -0400 (EDT)
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g81AH7o24338
	for <rpsec-web-archive@ietf.org>; Sun, 1 Sep 2002 06:17:07 -0400
Date: Sun, 01 Sep 2002 06:17:07 -0400
Message-ID: <20020901101707.1916.34673.Mailman@www1.ietf.org>
Subject: ietf.org mailing list memberships reminder
To: rpsec-web-archive@ietf.org
X-No-Archive: yes
X-Ack: no
Sender: sip-admin@ietf.org
Errors-To: sip-admin@ietf.org
X-BeenThere: sip@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk

This is a reminder, sent out once a month, about your ietf.org mailing
list memberships.  It includes your subscription info and how to use
it to change it or unsubscribe from a list.

You can visit the URLs to change your membership status or
configuration, including unsubscribing, setting digest-style delivery
or disabling delivery altogether (e.g., for a vacation), and so on.

In addition to the URL interfaces, you can also use email to make such
changes.  For more info, send a message to the '-request' address of
the list (for example, rpsec-request@ietf.org) containing just the
word 'help' in the message body, and an email message will be sent to
you with instructions.

If you have questions, problems, comments, etc, send them to
mailman-owner@.  Thanks!

Passwords for rpsec-web-archive@ietf.org:

List                                     Password // URL
----                                     --------  
rpsec@ietf.org                           lLFY      
https://www1.ietf.org/mailman/options/rpsec/rpsec-web-archive%40ietf.org



From mailnull@www1.ietf.org  Thu Sep 26 23:12:09 2002
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id XAA29751
	for <rpsec-archive@odin.ietf.org>; Thu, 26 Sep 2002 23:12:09 -0400 (EDT)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id g8R3DeE17139
	for rpsec-archive@odin.ietf.org; Thu, 26 Sep 2002 23:13:40 -0400
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g8R3Ddv17136
	for <rpsec-web-archive@optimus.ietf.org>; Thu, 26 Sep 2002 23:13:39 -0400
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id XAA29744
	for <rpsec-web-archive@ietf.org>; Thu, 26 Sep 2002 23:11:39 -0400 (EDT)
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g8R3CMv17092;
	Thu, 26 Sep 2002 23:12:23 -0400
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g8R3BKv17071
	for <rpsec@optimus.ietf.org>; Thu, 26 Sep 2002 23:11:20 -0400
Received: from kc-msxproto4.kc.umkc.edu (kc-msxproto4.kc.umkc.edu [134.193.143.48])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id XAA29677
	for <rpsec@ietf.org>; Thu, 26 Sep 2002 23:09:19 -0400 (EDT)
Received: from KC-MAIL1.kc.umkc.edu ([134.193.143.161] RDNS failed) by kc-msxproto4.kc.umkc.edu with Microsoft SMTPSVC(5.0.2195.5329);
	 Thu, 26 Sep 2002 22:11:12 -0500
X-MimeOLE: Produced By Microsoft Exchange V6.0.6249.0
content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: multipart/alternative;
	boundary="----_=_NextPart_001_01C265D3.87E08975"
Message-ID: <16D5A1F38B010847B9C50DAF8F64EB56FBBC26@KC-MAIL1.kc.umkc.edu>
Thread-Topic: New here 
Thread-Index: AcJl04fPS40J/mfgT4eKSWJlRR+LGg==
From: "Pandit, Ameya Dilip (UMKC-Student)" <adp7aa@umkc.edu>
To: <rpsec@ietf.org>
X-OriginalArrivalTime: 27 Sep 2002 03:11:12.0162 (UTC) FILETIME=[88744020:01C265D3]
Subject: [RPSEC] New here
Sender: rpsec-admin@ietf.org
Errors-To: rpsec-admin@ietf.org
X-BeenThere: rpsec@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/rpsec>,
	<mailto:rpsec-request@ietf.org?subject=unsubscribe>
List-Id: Routing Protocol Security Requirements  <rpsec.ietf.org>
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>
List-Archive: <https://www1.ietf.org/pipermail/rpsec/>
Date: Thu, 26 Sep 2002 22:11:11 -0500

This is a multi-part message in MIME format.

------_=_NextPart_001_01C265D3.87E08975
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

All,
=20
I am pursuing my research in the field of routing/network security at =
the University of Missouri - KC. Just got subscribed to this group. My =
work involves in providing robustness to routing protocols (typically =
Link State) and OSPF in particular.=20
=20
My view of robustness is some kind of intrusion detection and =
impersonation/modification avoidance. Is this group concentrating on =
providing intrusion detection schemes to the existing routing protocols =
or are we on a track of providing complete prevention only.=20
=20
Any feedback would be welcome.=20
=20
Thanks !!
Ameya

------_=_NextPart_001_01C265D3.87E08975
Content-Type: text/html;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD><TITLE>Message</TITLE>
<META content=3D"text/html; charset=3Diso-8859-1" =
http-equiv=3DContent-Type>
<META content=3D"MSHTML 5.00.3315.2870" name=3DGENERATOR></HEAD>
<BODY>
<DIV><FONT face=3DArial size=3D2><SPAN=20
class=3D962470603-27092002>All,</SPAN></FONT></DIV>
<DIV><FONT face=3DArial size=3D2><SPAN=20
class=3D962470603-27092002></SPAN></FONT>&nbsp;</DIV>
<DIV><FONT face=3DArial size=3D2><SPAN class=3D962470603-27092002>I am =
pursuing my=20
research in the field of routing/network security at the University of =
Missouri=20
- KC. Just got subscribed to this group. My work involves in providing=20
robustness to routing protocols (typically Link State) and OSPF in =
particular.=20
</SPAN></FONT></DIV>
<DIV><FONT face=3DArial size=3D2><SPAN=20
class=3D962470603-27092002></SPAN></FONT>&nbsp;</DIV>
<DIV><FONT face=3DArial size=3D2><SPAN class=3D962470603-27092002>My =
view of=20
robustness is some kind of <EM>intrusion detection </EM>and=20
<EM>impersonation/modification </EM>avoidance. Is this group =
concentrating on=20
providing intrusion detection schemes to the existing routing protocols =
or are=20
we on a track of providing complete <EM>prevention </EM>only.=20
</SPAN></FONT></DIV>
<DIV><FONT face=3DArial size=3D2><SPAN=20
class=3D962470603-27092002></SPAN></FONT>&nbsp;</DIV>
<DIV><FONT face=3DArial size=3D2><SPAN class=3D962470603-27092002>Any =
feedback would=20
be welcome. </SPAN></FONT></DIV>
<DIV><FONT face=3DArial size=3D2><SPAN=20
class=3D962470603-27092002></SPAN></FONT>&nbsp;</DIV>
<DIV><FONT face=3DArial size=3D2><SPAN class=3D962470603-27092002>Thanks =

!!</SPAN></FONT></DIV>
<DIV><FONT face=3DArial size=3D2><SPAN=20
class=3D962470603-27092002>Ameya</SPAN></FONT></DIV></BODY></HTML>
=00
------_=_NextPart_001_01C265D3.87E08975--
_______________________________________________
RPSEC mailing list
RPSEC@ietf.org
https://www1.ietf.org/mailman/listinfo/rpsec



From mailnull@www1.ietf.org  Mon Sep 30 04:55:13 2002
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id EAA26830
	for <rpsec-archive@odin.ietf.org>; Mon, 30 Sep 2002 04:55:13 -0400 (EDT)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id g8U8unl23810
	for rpsec-archive@odin.ietf.org; Mon, 30 Sep 2002 04:56:49 -0400
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g8U8unv23807
	for <rpsec-web-archive@optimus.ietf.org>; Mon, 30 Sep 2002 04:56:49 -0400
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id EAA26822
	for <rpsec-web-archive@ietf.org>; Mon, 30 Sep 2002 04:54:42 -0400 (EDT)
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g8U8qNv23690;
	Mon, 30 Sep 2002 04:52:23 -0400
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g8U8ppv23658
	for <rpsec@optimus.ietf.org>; Mon, 30 Sep 2002 04:51:51 -0400
Received: from mbibipnt08.HC.BT.COM (saturn.bt.com [193.113.57.20])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id EAA26775
	for <rpsec@ietf.org>; Mon, 30 Sep 2002 04:49:44 -0400 (EDT)
From: billie.lateef@bt.com
Received: by mbibipnt08.nat.bt.com with Internet Mail Service (5.5.2653.19)
	id <TXT8H4P0>; Mon, 30 Sep 2002 09:51:15 +0100
Message-ID: <981038F72E40E04D8F80A194E5F7102B02218E@i2km04-ukbr.domain1.systemhost.net>
To: rpsec@ietf.org
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2653.19)
Content-Type: text/plain;
	charset="iso-8859-1"
Subject: [RPSEC] RE: RPSEC digest, Vol 1 #57 - 1 msg
Sender: rpsec-admin@ietf.org
Errors-To: rpsec-admin@ietf.org
X-BeenThere: rpsec@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/rpsec>,
	<mailto:rpsec-request@ietf.org?subject=unsubscribe>
List-Id: Routing Protocol Security Requirements  <rpsec.ietf.org>
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>
List-Archive: <https://www1.ietf.org/pipermail/rpsec/>
Date: Mon, 30 Sep 2002 09:51:03 +0100

I do not believe that we want to provide complete prevention, that will be
impossible for the simple fact that the infrastructure that underpins all
these development are insecure by design and furthermore, to use the
theoretical postulation of risk management, the objective will be to reduce
the frequency of breaches and thus minimise the impact if a breach does
occur. Hence the need to have built in robustness that allow the various
network components to adapt to changing needs - in terms of intrusions
detection and malicious attacks.

Regards

-----Original Message-----
From: rpsec-request@ietf.org [mailto:rpsec-request@ietf.org]
Sent: 27 September 2002 17:00
To: rpsec@ietf.org
Subject: RPSEC digest, Vol 1 #57 - 1 msg


Send RPSEC mailing list submissions to
	rpsec@ietf.org

To subscribe or unsubscribe via the World Wide Web, visit
	https://www1.ietf.org/mailman/listinfo/rpsec
or, via email, send a message with subject or body 'help' to
	rpsec-request@ietf.org

You can reach the person managing the list at
	rpsec-admin@ietf.org

When replying, please edit your Subject line so it is more specific
than "Re: Contents of RPSEC digest..."


Today's Topics:

   1. New here (Pandit, Ameya Dilip (UMKC-Student))

--__--__--

Message: 1
Date: Thu, 26 Sep 2002 22:11:11 -0500
From: "Pandit, Ameya Dilip (UMKC-Student)" <adp7aa@umkc.edu>
To: <rpsec@ietf.org>
Subject: [RPSEC] New here

This is a multi-part message in MIME format.

------_=_NextPart_001_01C265D3.87E08975
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

All,
=20
I am pursuing my research in the field of routing/network security at =
the University of Missouri - KC. Just got subscribed to this group. My =
work involves in providing robustness to routing protocols (typically =
Link State) and OSPF in particular.=20
=20
My view of robustness is some kind of intrusion detection and =
impersonation/modification avoidance. Is this group concentrating on =
providing intrusion detection schemes to the existing routing protocols =
or are we on a track of providing complete prevention only.=20
=20
Any feedback would be welcome.=20
=20
Thanks !!
Ameya

------_=_NextPart_001_01C265D3.87E08975
Content-Type: text/html;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD><TITLE>Message</TITLE>
<META content=3D"text/html; charset=3Diso-8859-1" =
http-equiv=3DContent-Type>
<META content=3D"MSHTML 5.00.3315.2870" name=3DGENERATOR></HEAD>
<BODY>
<DIV><FONT face=3DArial size=3D2><SPAN=20
class=3D962470603-27092002>All,</SPAN></FONT></DIV>
<DIV><FONT face=3DArial size=3D2><SPAN=20
class=3D962470603-27092002></SPAN></FONT>&nbsp;</DIV>
<DIV><FONT face=3DArial size=3D2><SPAN class=3D962470603-27092002>I am =
pursuing my=20
research in the field of routing/network security at the University of =
Missouri=20
- KC. Just got subscribed to this group. My work involves in providing=20
robustness to routing protocols (typically Link State) and OSPF in =
particular.=20
</SPAN></FONT></DIV>
<DIV><FONT face=3DArial size=3D2><SPAN=20
class=3D962470603-27092002></SPAN></FONT>&nbsp;</DIV>
<DIV><FONT face=3DArial size=3D2><SPAN class=3D962470603-27092002>My =
view of=20
robustness is some kind of <EM>intrusion detection </EM>and=20
<EM>impersonation/modification </EM>avoidance. Is this group =
concentrating on=20
providing intrusion detection schemes to the existing routing protocols =
or are=20
we on a track of providing complete <EM>prevention </EM>only.=20
</SPAN></FONT></DIV>
<DIV><FONT face=3DArial size=3D2><SPAN=20
class=3D962470603-27092002></SPAN></FONT>&nbsp;</DIV>
<DIV><FONT face=3DArial size=3D2><SPAN class=3D962470603-27092002>Any =
feedback would=20
be welcome. </SPAN></FONT></DIV>
<DIV><FONT face=3DArial size=3D2><SPAN=20
class=3D962470603-27092002></SPAN></FONT>&nbsp;</DIV>
<DIV><FONT face=3DArial size=3D2><SPAN class=3D962470603-27092002>Thanks =

!!</SPAN></FONT></DIV>
<DIV><FONT face=3DArial size=3D2><SPAN=20
class=3D962470603-27092002>Ameya</SPAN></FONT></DIV></BODY></HTML>
=00
------_=_NextPart_001_01C265D3.87E08975--


--__--__--

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


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



From mailnull@www1.ietf.org  Mon Sep 30 16:54:47 2002
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA21113
	for <rpsec-archive@odin.ietf.org>; Mon, 30 Sep 2002 16:54:47 -0400 (EDT)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id g8UKuHR22920
	for rpsec-archive@odin.ietf.org; Mon, 30 Sep 2002 16:56:17 -0400
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g8UKuHv22917
	for <rpsec-web-archive@optimus.ietf.org>; Mon, 30 Sep 2002 16:56:17 -0400
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA21105
	for <rpsec-web-archive@ietf.org>; Mon, 30 Sep 2002 16:54:16 -0400 (EDT)
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g8UKtOv22858;
	Mon, 30 Sep 2002 16:55:24 -0400
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g8UKsMv22815
	for <rpsec@optimus.ietf.org>; Mon, 30 Sep 2002 16:54:22 -0400
Received: from hotmail.com (f148.pav2.hotmail.com [64.4.37.148])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA21042
	for <rpsec@ietf.org>; Mon, 30 Sep 2002 16:52:21 -0400 (EDT)
Received: from mail pickup service by hotmail.com with Microsoft SMTPSVC;
	 Mon, 30 Sep 2002 13:53:46 -0700
Received: from 134.193.6.40 by pv2fd.pav2.hotmail.msn.com with HTTP;
	Mon, 30 Sep 2002 20:53:45 GMT
X-Originating-IP: [134.193.6.40]
From: "Senthilkumar Ayyasamy" <senthil_gct@hotmail.com>
To: billie.lateef@bt.com, rpsec@ietf.org
Subject: Re: [RPSEC] RE: RPSEC digest, Vol 1 #57 - 1 msg
Mime-Version: 1.0
Content-Type: text/plain; format=flowed
Message-ID: <F148NEOafeJOu7KDSpC00004559@hotmail.com>
X-OriginalArrivalTime: 30 Sep 2002 20:53:46.0316 (UTC) FILETIME=[782160C0:01C268C3]
Sender: rpsec-admin@ietf.org
Errors-To: rpsec-admin@ietf.org
X-BeenThere: rpsec@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/rpsec>,
	<mailto:rpsec-request@ietf.org?subject=unsubscribe>
List-Id: Routing Protocol Security Requirements  <rpsec.ietf.org>
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>
List-Archive: <https://www1.ietf.org/pipermail/rpsec/>
Date: Mon, 30 Sep 2002 15:53:45 -0500


>I do not believe that we want to provide complete prevention, that will be
>impossible for the simple fact that the infrastructure that underpins all
>these development are insecure by design and furthermore, to use the
>theoretical postulation of risk management, the objective will be to reduce
>the frequency of breaches and thus minimise the impact if a breach does
>occur. Hence the need to have built in robustness that allow the various
>network components to adapt to changing needs - in terms of intrusions
>detection and malicious attacks.
   Although intrusion detection and other techniques (solution space) is 
totally out of scope for rpsec, their have been lot of research around 
intrusion detection techniques and some proposals are like solutions 
searching for a problem. Thats why, it is difficult to involve some 
engineering effort (IETF) for IDS schemes. But, output of this group by 
means of requirements and threat models, will help foster research in 
routing & IDS for solving some of the current routing vulnerabilities.
  As for as link state and IDS are concerned, one should be careful  about 
the context. When we talk of security for routing protocols, it is usually 
in control plane. But, most of the IDS implementations for link state 
protocols ( for ex: felix wu's Ji-Nao distributed IDS for link state 
protocols) are management plane work. So, it is more of MIB work with all 
application level agents. But, recently, people are also working on 
backscatter analysis (not DDoS characterization) for Intrusion 
detection/OSPF.

  Then, what is germane to this group? threat models for intra-domain 
routing stuff. Analysis of various fail-stop and byzatine failures which 
lead to lot of vulnerabilities in link state systems. Most of the fail-stop 
failures can be minimized by murphy's digital signature method. The question 
is: what are the vulnerabilities which stand unaffected even with all those 
security mechanisms and MD5 protection schemes?
Most of the protocol security breaches associated with metrics, sequence no 
and age can be prevented by means of keyed-MD5 authentication. So, what are 
the remaining problems which stands to be solved? what are threats due to 
compromised routers, intruding routing process and routing protocol 
poisoning which still stands rigid with all our protection mechanisms? A 
look into security focus vulnerability list will tell you most are just 
configuration or implementation problems. So, one of our work will also be 
listing all these vulnerabilities associated with link state protocols.

- Senthil.

_________________________________________________________________
Chat with friends online, try MSN Messenger: http://messenger.msn.com

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



