From mailnull@www1.ietf.org  Sat Feb  1 07:20:17 2003
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 HAA04958
	for <rpsec-archive@odin.ietf.org>; Sat, 1 Feb 2003 07:20:17 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id h11COHp05357
	for rpsec-archive@odin.ietf.org; Sat, 1 Feb 2003 07:24:17 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h11COHJ05354
	for <rpsec-web-archive@optimus.ietf.org>; Sat, 1 Feb 2003 07:24:17 -0500
Received: from www1.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id HAA04928
	for <rpsec-web-archive@ietf.org>; Sat, 1 Feb 2003 07:18:19 -0500 (EST)
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h11CMaJ05303;
	Sat, 1 Feb 2003 07:22:36 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h11AO6J00773
	for <rpsec@optimus.ietf.org>; Sat, 1 Feb 2003 05:24:06 -0500
Received: from kc-msxproto2.kc.umkc.edu (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id FAA03644
	for <rpsec@ietf.org>; Sat, 1 Feb 2003 05:19:38 -0500 (EST)
Received: from KC-MAIL4.kc.umkc.edu ([134.193.143.111] RDNS failed) by kc-msxproto2.kc.umkc.edu with Microsoft SMTPSVC(5.0.2195.5329);
	 Sat, 1 Feb 2003 04:23:12 -0600
X-MimeOLE: Produced By Microsoft Exchange V6.0.6249.0
Content-Class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="Windows-1252"
Subject: Re: [RPSEC] Accessing topology-related information behind firewalls
Date: Sat, 1 Feb 2003 04:23:11 -0600
Message-ID: <5EF7D95E17BDAD4A968C812E5ABC390B02CF6F@KC-MAIL4.kc.umkc.edu>
Thread-Topic: Re: [RPSEC] Accessing topology-related information behind firewalls
Thread-Index: AcLJ2+wsYHP19osQTcuglMG1KyYjvA==
From: "Ayyasamy, Senthilkumar  (UMKC-Student)" <saq66@umkc.edu>
To: <hgobjuka@yahoo.com>, "riw@cisco.com" <hgobjuka@yahoo.com>, >
Cc: <rpsec@ietf.org>
X-OriginalArrivalTime: 01 Feb 2003 10:23:12.0392 (UTC) FILETIME=[EC93B880:01C2C9DB]
Content-Transfer-Encoding: 8bit
X-MIME-Autoconverted: from quoted-printable to 8bit by www1.ietf.org id h11AO6J00774
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>
Content-Transfer-Encoding: 8bit
Content-Transfer-Encoding: 8bit


> > > Actually I'm trying to develop some algorithm and consecutively some open 
> > > source tool to detect the topology of large multi-subnet netwroks, and 
> > > consecutively the Internet in layer-2 (Data link layer), so that the tools 
> > > will be able to detect non-cooperative nodes like hubs besides routers and 
> > > other cooperative nodes. I'm not worried much about IP level. Instead, I'm 
> > > working in the MAC address level.
> > > So far, I was able to develop some algorithms to detect layer-2 topology for 
> > > networks which are not behind a firewall, 

Can you give some more information on the algorithm off-list? 

> > > but I need to get some method to get 
> > > information about nodes protected by firewall so that I may able to use this 
> > > information to detect such network's layer-2 topology.

But, where is the problem space? who needs to know l2 topology ( other
that the network administrators- who already have a good documentation of 
their l2 topology.)   

Their is enough interest in topology inference at IP path/router level, since it 
gives us lot of useful information. The whole bunch of Content providers like 
akamai depends on such inference methods to place their servers.

As for Russ reply:

> > I don't really think it depends on a firewall in the middle, really. For
> > instance, if you nat'ing, then you lose all sense of what the network
> > inside the nat looks like (moreso if you are pat'ing, rather than nat'ing).
> > If you are not nat'ing, and you are summarizing your advertisements, then
> > you still lose most of the useful routing information, since you've no idea
> > what subnets are actually reachable, what most of the prefix lengths are,
> > etc.
>
> > ie--if you have 10.1.0.0/24, 10.1.1.0/24, 10.1.2.0/24, and 10.1.3.0/24
> > summarizaed into 10.1.0.0/22, then you've lost knowledge of what the
> > broadcast addresses are within the network, and a sense of what servers are
> > ocated on what segments from just the ip addresses.
> >
> > If, however, you are actually advertising destination subnets in your net,
> > you're probably giving away information you should give away.
> > 
> > Hiding information is generally good, I think....

Yes. I accept that *more the aggregation, the lesser the topology details.*

If you go for a tracert based inference, Caida's skitter is the default option. 
The whole research community depends on them. 

Given the aggregation, how much of the backbone topology be inferred?
http://www.cs.washington.edu/research/networking/rocketfuel/interactive/


Their are recent works to walk around the aggregation problem too. 
MIT researchers have worked on inferring topology by observing the frequency 
of BGP updates.
http://www.nms.lcs.mit.edu/papers/clustering-imw2002.html
Their clustering technique was same as the one previously applied by 
ATT researchers to indentify web clusters.

But, still getting the total topology information is difficult. The 
technologies which has a flavour of connection-orientness (mpls etc.) 
become a big stumble block for taking accurate topology measurements. 






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



From mailnull@www1.ietf.org  Sat Feb  1 07:22:38 2003
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 HAA04990
	for <rpsec-archive@odin.ietf.org>; Sat, 1 Feb 2003 07:22:38 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id h11CQbH05423
	for rpsec-archive@odin.ietf.org; Sat, 1 Feb 2003 07:26:37 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h11CQbJ05420
	for <rpsec-web-archive@optimus.ietf.org>; Sat, 1 Feb 2003 07:26:37 -0500
Received: from www1.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id HAA04976
	for <rpsec-web-archive@ietf.org>; Sat, 1 Feb 2003 07:20:47 -0500 (EST)
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h11CP6J05397;
	Sat, 1 Feb 2003 07:25:06 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h11CLSJ05284
	for <rpsec@optimus.ietf.org>; Sat, 1 Feb 2003 07:21:28 -0500
Received: from rtp-msg-core-1.cisco.com (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id HAA04918
	for <rpsec@ietf.org>; Sat, 1 Feb 2003 07:16:57 -0500 (EST)
Received: from cisco.com (localhost [127.0.0.1])
	by rtp-msg-core-1.cisco.com (8.12.2/8.12.6) with ESMTP id h11CLN91021027;
	Sat, 1 Feb 2003 07:21:23 -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 HAA08845;
	Sat, 1 Feb 2003 07:20:31 -0500 (EST)
Date: Sat, 1 Feb 2003 07:20:31 -0500 (EST)
From: Russ White <ruwhite@cisco.com>
Reply-To: Russ White <riw@cisco.com>
To: Hasan Gobjuka <hgobjuka@yahoo.com>
cc: rpsec@ietf.org
Subject: Re: [RPSEC] Accessing topology-related information behind firewalls
In-Reply-To: <20030201031457.96546.qmail@web40501.mail.yahoo.com>
Message-ID: <Pine.GSO.4.51.0302010719570.5974@ruwhite-u10.cisco.com>
References: <20030201031457.96546.qmail@web40501.mail.yahoo.com>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
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>


Hmm.... That sounds quite interesting. Are you gleaning the l2 information
from the subnets shown in the routing protocol? Or?

:-)

Russ

On Fri, 31 Jan 2003, Hasan Gobjuka wrote:

>
> Thank you Russ,
> Actually I'm trying to develop some algorithm and consecutively some open source tool to detect the topology of large multi-subnet netwroks, and consecutively the Internet in layer-2 (Data link layer), so that the tools will be able to detect non-cooperative nodes like hubs besides routers and other cooperative nodes. I'm not worried much about IP level. Instead, I'm working in the MAC address level.
> So far, I was able to develop some algorithms to detect layer-2 topology for networks which are not behind a firewall, but I need to get some method to get information about nodes protected by firewall so that I may able to use this information to detect such network's layer-2 topology.
>
> Russ White <ruwhite@cisco.com> wrote:
> My 2c....
>
> I don't really think it depends on a firewall in the middle, really. For
> instance, if you nat'ing, then you lose all sense of what the network
> inside the nat looks like (moreso if you are pat'ing, rather than nat'ing).
> If you are not nat'ing, and you are summarizing your advertisements, then
> you still lose most of the useful routing information, since you've no idea
> what subnets are actually reachable, what most of the prefix lengths are,
> etc.
>
> ie--if you have 10.1.0.0/24, 10.1.1.0/24, 10.1.2.0/24, and 10.1.3.0/24
> summarizaed into 10.1.0.0/22, then you've lost knowledge of what the
> broadcast addresses are within the network, and a sense of what servers are
> located on what segments from just the ip addresses.
>
> If, however, you are actually advertising destination subnets in your net,
> you're probably giving away information you should give away.
>
> Hiding information is generally good, I think....
>
> :-)
>
> Russ
>
>
> On Fri, 31 Jan 2003, Hasan Gobjuka wrote:
>
> >
> > Hello all,
> >
> >
> >
> > Is there any way to get *useful* topology-related information from a firewall-protected network?
> >
> >
> >
> > Thanks,
> >
> >
> >
> > ---------------------------------
> > Do you Yahoo!?
> > Yahoo! Mail Plus - Powerful. Affordable. Sign up now
>
> __________________________________
> riw@cisco.com CCIE <>< Grace Alone
>
> _______________________________________________
> RPSEC mailing list
> RPSEC@ietf.org
> https://www1.ietf.org/mailman/listinfo/rpsec
>
>
> ---------------------------------
> Do you Yahoo!?
> Yahoo! Mail Plus - Powerful. Affordable. Sign up now

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

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



From mailnull@www1.ietf.org  Tue Feb 18 17:27:50 2003
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 RAA10205
	for <rpsec-archive@odin.ietf.org>; Tue, 18 Feb 2003 17:27:50 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id h1IMXaJ31587
	for rpsec-archive@odin.ietf.org; Tue, 18 Feb 2003 17:33:36 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h1IMXap31584
	for <rpsec-web-archive@optimus.ietf.org>; Tue, 18 Feb 2003 17:33:36 -0500
Received: from www1.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA10191
	for <rpsec-web-archive@ietf.org>; Tue, 18 Feb 2003 17:27:19 -0500 (EST)
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h1IMWQp31527;
	Tue, 18 Feb 2003 17:32:27 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h1IMVqp31503
	for <rpsec@optimus.ietf.org>; Tue, 18 Feb 2003 17:31:52 -0500
Received: from mesa.bbnplanet.com (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA10126
	for <rpsec@ietf.org>; Tue, 18 Feb 2003 17:25:34 -0500 (EST)
Received: from localhost (ttauber@localhost)
	by mesa.bbnplanet.com (8.10.2+Sun/8.10.2) with ESMTP id h1IMTMV06270
	for <rpsec@ietf.org>; Tue, 18 Feb 2003 17:29:22 -0500 (EST)
X-Authentication-Warning: mesa.bbnplanet.com: ttauber owned process doing -bs
Date: Tue, 18 Feb 2003 17:29:22 -0500 (EST)
From: Tony Tauber <ttauber@genuity.net>
X-X-Sender: ttauber@mesa.bbnplanet.com
To: rpsec@ietf.org
Message-ID: <Pine.GSO.4.40.0302181722340.473-100000@mesa.bbnplanet.com>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Subject: [RPSEC] Requirements Subgroup Volunteers
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>

Hi folks,

As we're closing in on the finalization of the merged "Generic
Threats to Routing Protocols" draft (to be posted soon), we have to
get moving on the "Generic Requirements" draft.

Some volunteers are needed to help put this all together and Russ
had the idea, which seems reasonable on the face of it, to form a
"technical subgroup" of perhaps six or eight people to work through
the development of the Requirements draft.

Who would like to work on this thing and can really dedicate some
cycles to it?  Please reply either to the list or to Russ and me
privately.  If there are concerns with this approach or you'd like to
sugggest an alternative, send via the same paths as above.

Thanks,

Tony

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



From mailnull@www1.ietf.org  Wed Feb 19 11:23:11 2003
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 LAA00415
	for <rpsec-archive@odin.ietf.org>; Wed, 19 Feb 2003 11:23:11 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id h1JGTKe23462
	for rpsec-archive@odin.ietf.org; Wed, 19 Feb 2003 11:29:20 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h1JGTKp23459
	for <rpsec-web-archive@optimus.ietf.org>; Wed, 19 Feb 2003 11:29:20 -0500
Received: from www1.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA00405
	for <rpsec-web-archive@ietf.org>; Wed, 19 Feb 2003 11:22:39 -0500 (EST)
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h1JGSMp23418;
	Wed, 19 Feb 2003 11:28:22 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h1JGAsp22182
	for <rpsec@optimus.ietf.org>; Wed, 19 Feb 2003 11:10:54 -0500
Received: from presque.djinesys.com (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA29844
	for <rpsec@ietf.org>; Wed, 19 Feb 2003 11:04:14 -0500 (EST)
Received: (from root@localhost)
	by presque.djinesys.com (8.11.3/8.11.1) id h1JG83112572
	for rpsec@ietf.org; Wed, 19 Feb 2003 11:08:03 -0500 (EST)
	(envelope-from shares@nexthop.com)
Received: from mail.corp.nexthop.com ([64.211.218.233])
	by presque.djinesys.com (8.11.3/8.11.1) with ESMTP id h1JG7uC12559
	for <rpsec@ietf.org>; Wed, 19 Feb 2003 11:07:57 -0500 (EST)
	(envelope-from shares@nexthop.com)
content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Subject: RE: [RPSEC] Requirements Subgroup Volunteers
X-MimeOLE: Produced By Microsoft Exchange V6.0.6249.0
Date: Wed, 19 Feb 2003 11:07:56 -0500
Message-ID: <BE36D687C8CBFA4AB76F5CD3E3C0FB4EA6AB9E@aa-exchange1.corp.nexthop.com>
Thread-Topic: [RPSEC] Requirements Subgroup Volunteers
Thread-Index: AcLXoHl76CD636gHR46LD7jewWGFvQAhU9ZA
From: "Susan Hares" <shares@nexthop.com>
To: "Tony Tauber" <ttauber@genuity.net>, <rpsec@ietf.org>
X-Virus-Scanned: by AMaViS perl-11
Content-Transfer-Encoding: 8bit
X-MIME-Autoconverted: from quoted-printable to 8bit by www1.ietf.org id h1JGAtp22183
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>
Content-Transfer-Encoding: 8bit
Content-Transfer-Encoding: 8bit

Tony:

I'd like to volunteer.

Sue

-----Original Message-----
From: Tony Tauber [mailto:ttauber@genuity.net]
Sent: Tuesday, February 18, 2003 5:29 PM
To: rpsec@ietf.org
Subject: [RPSEC] Requirements Subgroup Volunteers


Hi folks,

As we're closing in on the finalization of the merged "Generic
Threats to Routing Protocols" draft (to be posted soon), we have to
get moving on the "Generic Requirements" draft.

Some volunteers are needed to help put this all together and Russ
had the idea, which seems reasonable on the face of it, to form a
"technical subgroup" of perhaps six or eight people to work through
the development of the Requirements draft.

Who would like to work on this thing and can really dedicate some
cycles to it?  Please reply either to the list or to Russ and me
privately.  If there are concerns with this approach or you'd like to
sugggest an alternative, send via the same paths as above.

Thanks,

Tony

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



From mailnull@www1.ietf.org  Wed Feb 19 12:15:17 2003
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 MAA01876
	for <rpsec-archive@odin.ietf.org>; Wed, 19 Feb 2003 12:15:17 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id h1JHLQa27675
	for rpsec-archive@odin.ietf.org; Wed, 19 Feb 2003 12:21:26 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h1JHLQp27672
	for <rpsec-web-archive@optimus.ietf.org>; Wed, 19 Feb 2003 12:21:26 -0500
Received: from www1.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA01855
	for <rpsec-web-archive@ietf.org>; Wed, 19 Feb 2003 12:14:45 -0500 (EST)
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h1JHJPp27565;
	Wed, 19 Feb 2003 12:19:25 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h1JH8sp26999
	for <rpsec@optimus.ietf.org>; Wed, 19 Feb 2003 12:08:54 -0500
Received: from ims21.stu.nus.edu.sg (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA01542
	for <rpsec@ietf.org>; Wed, 19 Feb 2003 12:02:02 -0500 (EST)
Received: from mbxsrv26.stu.nus.edu.sg ([137.132.14.236]) by ims21.stu.nus.edu.sg with Microsoft SMTPSVC(5.0.2195.5329);
	 Thu, 20 Feb 2003 01:05:47 +0800
content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="utf-8"
X-MimeOLE: Produced By Microsoft Exchange V6.0.6249.0
Subject: [RPSEC] Requirements Subgroup Volunteers
Date: Thu, 20 Feb 2003 01:05:46 +0800
Message-ID: <6330DC96389A924A804F52FA3848930E02E07573@MBXSRV26.stu.nus.edu.sg>
Thread-Topic: [RPSEC] Requirements Subgroup Volunteers
Thread-Index: AcLYOSUbYpBZvrAARxeD/+HyO2Fv9w==
From: "Marwaha Shivanajay" <engp1609@nus.edu.sg>
To: <rpsec@ietf.org>
X-OriginalArrivalTime: 19 Feb 2003 17:05:47.0162 (UTC) FILETIME=[25609FA0:01C2D839]
Content-Transfer-Encoding: 8bit
X-MIME-Autoconverted: from base64 to 8bit by www1.ietf.org id h1JH8sp27000
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>
Content-Transfer-Encoding: 8bit
Content-Transfer-Encoding: 8bit

Hi,

I would like to volunteer for the development of the requirement draft.

Yours truly,

Shivanajay Marwaha

***********************************************
www.geocities.com/shivanajaym
Research Scholar,
Electrical & Computer Engineering Dept.
National University of Singapore.
***********************************************

-----Original Message----- 
From: Tony Tauber [mailto:ttauber@genuity.net] 
Sent: Tuesday, February 18, 2003 5:29 PM 
To: rpsec@ietf.org 
Subject: [RPSEC] Requirements Subgroup Volunteers 


Hi folks, 

As we're closing in on the finalization of the merged "Generic 
Threats to Routing Protocols" draft (to be posted soon), we have to 
get moving on the "Generic Requirements" draft. 

Some volunteers are needed to help put this all together and Russ 
had the idea, which seems reasonable on the face of it, to form a 
"technical subgroup" of perhaps six or eight people to work through 
the development of the Requirements draft. 

Who would like to work on this thing and can really dedicate some 
cycles to it?  Please reply either to the list or to Russ and me 
privately.  If there are concerns with this approach or you'd like to 
sugggest an alternative, send via the same paths as above. 

Thanks, 

Tony 

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

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



From mailnull@www1.ietf.org  Wed Feb 19 12:41:10 2003
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 MAA02719
	for <rpsec-archive@odin.ietf.org>; Wed, 19 Feb 2003 12:41:10 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id h1JHlKu29495
	for rpsec-archive@odin.ietf.org; Wed, 19 Feb 2003 12:47:20 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h1JHlKp29492
	for <rpsec-web-archive@optimus.ietf.org>; Wed, 19 Feb 2003 12:47:20 -0500
Received: from www1.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA02698
	for <rpsec-web-archive@ietf.org>; Wed, 19 Feb 2003 12:40:39 -0500 (EST)
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h1JHkKp29448;
	Wed, 19 Feb 2003 12:46:20 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h1JHjxp29412
	for <rpsec@optimus.ietf.org>; Wed, 19 Feb 2003 12:45:59 -0500
Received: from vmmr7.verisignmail.com (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA02629
	for <rpsec@ietf.org>; Wed, 19 Feb 2003 12:39:10 -0500 (EST)
Received: from vmms1.verisignmail.com (vmms1.verisignmail.com [216.168.230.138] (may be forged))
	by vmmr7.verisignmail.com (Mirapoint Messaging Server MOS 3.2.2-GA)
	with ESMTP id ORT48712;
	Wed, 19 Feb 2003 12:42:34 -0500 (EST)
Received: from vmms1.verisignmail.com (localhost.verisignmail.com [127.0.0.1])
	by vmms1.verisignmail.com (Mirapoint Messaging Server MOS 2.9.3.2)
	with SMTP id QHF46582 (AUTH nigel@forever-networks.com);
	Wed, 19 Feb 2003 12:42:33 -0500 (EST)
Message-Id: <200302191742.QHF46582@vmms1.verisignmail.com>
Received: from 192.77.198.11
	by vmms1.verisignmail.com (Mirapoint Messaging Server MOS 2.9.3.2)
	with HTTP/1.1;
	Wed, 19 Feb 2003 12:42:46 -0500
Date: Wed, 19 Feb 2003 12:42:46 -0500
From: Nigel Clarke <nigel@forever-networks.com>
Subject: Re: [RPSEC] Requirements Subgroup Volunteers
To: rpsec@ietf.org
X-Mailer: Mirapoint Webmail Direct 2.9.3.2
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit
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>
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit

I would like to volunteer. 

How much will I get paid ;-) ...Seriously, I'm interested. 

--

Nigel Clarke
Network Security Engineer
nigel@forever-networks.com
_______________________________________________
RPSEC mailing list
RPSEC@ietf.org
https://www1.ietf.org/mailman/listinfo/rpsec



From mailnull@www1.ietf.org  Wed Feb 19 15:00:40 2003
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 PAA07082
	for <rpsec-archive@odin.ietf.org>; Wed, 19 Feb 2003 15:00:40 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id h1JK6rB06197
	for rpsec-archive@odin.ietf.org; Wed, 19 Feb 2003 15:06:53 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h1JK6rp06194
	for <rpsec-web-archive@optimus.ietf.org>; Wed, 19 Feb 2003 15:06:53 -0500
Received: from www1.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA07071
	for <rpsec-web-archive@ietf.org>; Wed, 19 Feb 2003 15:00:09 -0500 (EST)
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h1JK5Yp06119;
	Wed, 19 Feb 2003 15:05:34 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h1JK4Op06088
	for <rpsec@optimus.ietf.org>; Wed, 19 Feb 2003 15:04:24 -0500
Received: from sequoia.muada.com (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA07017
	for <rpsec@ietf.org>; Wed, 19 Feb 2003 14:57:39 -0500 (EST)
Received: from localhost (iljitsch@localhost)
	by sequoia.muada.com (8.11.3/8.9.3) with ESMTP id h1JK1tS17974;
	Wed, 19 Feb 2003 21:01:55 +0100 (CET)
	(envelope-from iljitsch@muada.com)
Date: Wed, 19 Feb 2003 21:01:55 +0100 (CET)
From: Iljitsch van Beijnum <iljitsch@muada.com>
To: Tony Tauber <ttauber@genuity.net>
cc: <rpsec@ietf.org>
Subject: Re: [RPSEC] Requirements Subgroup Volunteers
In-Reply-To: <Pine.GSO.4.40.0302181722340.473-100000@mesa.bbnplanet.com>
Message-ID: <20030219205039.P61596-100000@sequoia.muada.com>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
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>

On Tue, 18 Feb 2003, Tony Tauber wrote:

> As we're closing in on the finalization of the merged "Generic
> Threats to Routing Protocols" draft (to be posted soon), we have to
> get moving on the "Generic Requirements" draft.

> Some volunteers are needed to help put this all together and Russ
> had the idea, which seems reasonable on the face of it, to form a
> "technical subgroup" of perhaps six or eight people to work through
> the development of the Requirements draft.

> Who would like to work on this thing and can really dedicate some
> cycles to it?  Please reply either to the list or to Russ and me
> privately.  If there are concerns with this approach or you'd like to
> sugggest an alternative, send via the same paths as above.

You guys have more experience with this, so tell me if I'm wrong, but...
what exactly do we gain by working in a 6 - 8 person group rather than
the "entire" working group/list? Obvouisly a small group needs to take
point but I'm thinking more 1 - 2 people than 6 - 8 here.

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



From mailnull@www1.ietf.org  Wed Feb 19 15:36:39 2003
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 PAA08125
	for <rpsec-archive@odin.ietf.org>; Wed, 19 Feb 2003 15:36:39 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id h1JKgrF09018
	for rpsec-archive@odin.ietf.org; Wed, 19 Feb 2003 15:42:53 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h1JKgrp09014
	for <rpsec-web-archive@optimus.ietf.org>; Wed, 19 Feb 2003 15:42:53 -0500
Received: from www1.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA08097
	for <rpsec-web-archive@ietf.org>; Wed, 19 Feb 2003 15:36:07 -0500 (EST)
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h1JKg7p08987;
	Wed, 19 Feb 2003 15:42:07 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h1JKfwp08970
	for <rpsec@optimus.ietf.org>; Wed, 19 Feb 2003 15:41:58 -0500
Received: from presque.djinesys.com (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA08073
	for <rpsec@ietf.org>; Wed, 19 Feb 2003 15:35:13 -0500 (EST)
Received: (from root@localhost)
	by presque.djinesys.com (8.11.3/8.11.1) id h1JKcs222452;
	Wed, 19 Feb 2003 15:38:54 -0500 (EST)
	(envelope-from jhaas@jhaas.nexthop.com)
Received: from jhaas.nexthop.com (jhaas.nexthop.com [64.211.218.31])
	by presque.djinesys.com (8.11.3/8.11.1) with ESMTP id h1JKcoC22444;
	Wed, 19 Feb 2003 15:38:50 -0500 (EST)
	(envelope-from jhaas@jhaas.nexthop.com)
Received: (from jhaas@localhost)
	by jhaas.nexthop.com (8.11.3nb1/8.11.3) id h1JKcoV07438;
	Wed, 19 Feb 2003 15:38:50 -0500 (EST)
Date: Wed, 19 Feb 2003 15:38:50 -0500
From: Jeffrey Haas <jhaas@nexthop.com>
To: Iljitsch van Beijnum <iljitsch@muada.com>
Cc: Tony Tauber <ttauber@genuity.net>, rpsec@ietf.org
Subject: Re: [RPSEC] Requirements Subgroup Volunteers
Message-ID: <20030219153850.E4549@nexthop.com>
References: <Pine.GSO.4.40.0302181722340.473-100000@mesa.bbnplanet.com> <20030219205039.P61596-100000@sequoia.muada.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
User-Agent: Mutt/1.2.5i
In-Reply-To: <20030219205039.P61596-100000@sequoia.muada.com>; from iljitsch@muada.com on Wed, Feb 19, 2003 at 09:01:55PM +0100
X-Virus-Scanned: by AMaViS perl-11
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>

On Wed, Feb 19, 2003 at 09:01:55PM +0100, Iljitsch van Beijnum wrote:
> You guys have more experience with this, so tell me if I'm wrong, but...
> what exactly do we gain by working in a 6 - 8 person group rather than
> the "entire" working group/list? Obvouisly a small group needs to take
> point but I'm thinking more 1 - 2 people than 6 - 8 here.

Not to speak for the WG chairs, but sometimes a focus group can
accomplish a lot of the broad details of spec work in a shorter period
of time.  Once this has been accomplished, the focus group disbands
and the general WG can get the details ironed out.  If the WG 
decides that the focus group had missed basic things, either the WG
can take over the work, or another focus group can be convened in
order to attempt to incorporate the concerns.

Note that those who voice concerns are often asked to be part of the
focus groups. :-)

-- 
Jeff Haas 
NextHop Technologies
_______________________________________________
RPSEC mailing list
RPSEC@ietf.org
https://www1.ietf.org/mailman/listinfo/rpsec



From mailnull@www1.ietf.org  Wed Feb 19 17:42:54 2003
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 RAA11499
	for <rpsec-archive@odin.ietf.org>; Wed, 19 Feb 2003 17:42:54 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id h1JMnAN16647
	for rpsec-archive@odin.ietf.org; Wed, 19 Feb 2003 17:49:10 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h1JMnAp16644
	for <rpsec-web-archive@optimus.ietf.org>; Wed, 19 Feb 2003 17:49:10 -0500
Received: from www1.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA11482
	for <rpsec-web-archive@ietf.org>; Wed, 19 Feb 2003 17:42:21 -0500 (EST)
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h1JMmHp16583;
	Wed, 19 Feb 2003 17:48:17 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h1JMlOp16532
	for <rpsec@optimus.ietf.org>; Wed, 19 Feb 2003 17:47:24 -0500
Received: from pheriche.sun.com (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA11438
	for <rpsec@ietf.org>; Wed, 19 Feb 2003 17:40:36 -0500 (EST)
Received: from sydney.East.Sun.COM ([129.148.9.16])
	by pheriche.sun.com (8.9.3+Sun/8.9.3) with ESMTP id PAA25647
	for <rpsec@ietf.org>; Wed, 19 Feb 2003 15:44:26 -0700 (MST)
Received: from sr1-ubur-05 (sr1-ubur-05 [129.148.9.84])
	by sydney.East.Sun.COM (8.11.6+Sun/8.11.6/ENSMAIL,v2.2) with SMTP id h1JMiPM11691
	for <rpsec@ietf.org>; Wed, 19 Feb 2003 17:44:25 -0500 (EST)
Message-Id: <200302192244.h1JMiPM11691@sydney.East.Sun.COM>
Date: Wed, 19 Feb 2003 17:44:25 -0500 (EST)
From: Radia Perlman - Boston Center for Networking <Radia.Perlman@Sun.COM>
Reply-To: Radia Perlman - Boston Center for Networking <Radia.Perlman@Sun.COM>
Subject: Re: [RPSEC] Requirements Subgroup Volunteers
To: rpsec@ietf.org
MIME-Version: 1.0
Content-Type: TEXT/plain; charset=us-ascii
Content-MD5: Va0TeFMGRMbf7qEzymOY4A==
X-Mailer: dtmail 1.3.0 @(#)CDE Version 1.4.6_06 SunOS 5.8 sun4u sparc 
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>

I guess I'd like to volunteer, but might be a little bit
flaky in terms of time...but I'll try.

Radia

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



From mailnull@www1.ietf.org  Thu Feb 20 00:17:41 2003
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 AAA19740
	for <rpsec-archive@odin.ietf.org>; Thu, 20 Feb 2003 00:17:41 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id h1K5O7q04773
	for rpsec-archive@odin.ietf.org; Thu, 20 Feb 2003 00:24:07 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h1K5O7p04770
	for <rpsec-web-archive@optimus.ietf.org>; Thu, 20 Feb 2003 00:24:07 -0500
Received: from www1.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id AAA19735
	for <rpsec-web-archive@ietf.org>; Thu, 20 Feb 2003 00:17:10 -0500 (EST)
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h1K5NFp04750;
	Thu, 20 Feb 2003 00:23:15 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h1K5Mxp04733
	for <rpsec@optimus.ietf.org>; Thu, 20 Feb 2003 00:22:59 -0500
Received: from wiprom2mx1.wipro.com (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id AAA19728
	for <rpsec@ietf.org>; Thu, 20 Feb 2003 00:16:00 -0500 (EST)
Received: from m2vwall5.wipro.com (m2vwall5.wipro.com [10.115.50.5])
	by wiprom2mx1.wipro.com (8.11.3/8.11.3) with SMTP id h1K5Jmv19582
	for <rpsec@ietf.org>; Thu, 20 Feb 2003 10:49:48 +0530 (IST)
Received: from blr-k1-msg.wipro.com ([10.117.50.99]) by blr-m1-bh1.wipro.com with Microsoft SMTPSVC(5.0.2195.5329);
	 Thu, 20 Feb 2003 10:49:43 +0530
content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Subject: RE: [RPSEC] Requirements Subgroup Volunteers
X-MimeOLE: Produced By Microsoft Exchange V6.0.6249.0
Date: Thu, 20 Feb 2003 10:49:43 +0530
Message-ID: <4D148FEC6C003445B94D5B264288DBE96269A2@blr-k1-msg.wipro.com>
Thread-Topic: [RPSEC] Requirements Subgroup Volunteers
Thread-Index: AcLXoLgLvODpNFqcR3mhBWBOC0DBOgA/t6MA
From: "Shankar Ananthanarayanan Kambat" <shankar.kambat@wipro.com>
To: "Tony Tauber" <ttauber@genuity.net>, <rpsec@ietf.org>
X-OriginalArrivalTime: 20 Feb 2003 05:19:43.0809 (UTC) FILETIME=[AD43B310:01C2D89F]
Content-Transfer-Encoding: 8bit
X-MIME-Autoconverted: from quoted-printable to 8bit by www1.ietf.org id h1K5Mxp04734
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>
Content-Transfer-Encoding: 8bit
Content-Transfer-Encoding: 8bit

Hi,
	I would like to volunteer.

Regards
Shankar K A


-----Original Message-----
From: Tony Tauber [mailto:ttauber@genuity.net] 
Sent: Wednesday, February 19, 2003 3:59 AM
To: rpsec@ietf.org
Subject: [RPSEC] Requirements Subgroup Volunteers


Hi folks,

As we're closing in on the finalization of the merged "Generic
Threats to Routing Protocols" draft (to be posted soon), we have to
get moving on the "Generic Requirements" draft.

Some volunteers are needed to help put this all together and Russ
had the idea, which seems reasonable on the face of it, to form a
"technical subgroup" of perhaps six or eight people to work through
the development of the Requirements draft.

Who would like to work on this thing and can really dedicate some
cycles to it?  Please reply either to the list or to Russ and me
privately.  If there are concerns with this approach or you'd like to
sugggest an alternative, send via the same paths as above.

Thanks,

Tony

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



From mailnull@www1.ietf.org  Thu Feb 20 01:41:37 2003
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 BAA21372
	for <rpsec-archive@odin.ietf.org>; Thu, 20 Feb 2003 01:41:37 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id h1K6m3w09447
	for rpsec-archive@odin.ietf.org; Thu, 20 Feb 2003 01:48:03 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h1K6m3p09444
	for <rpsec-web-archive@optimus.ietf.org>; Thu, 20 Feb 2003 01:48:03 -0500
Received: from www1.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id BAA21364
	for <rpsec-web-archive@ietf.org>; Thu, 20 Feb 2003 01:41:06 -0500 (EST)
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h1K6lHp09423;
	Thu, 20 Feb 2003 01:47:18 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h1K6kup09393
	for <rpsec@optimus.ietf.org>; Thu, 20 Feb 2003 01:46:56 -0500
Received: from hoemail2.firewall.lucent.com (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id BAA21280
	for <rpsec@ietf.org>; Thu, 20 Feb 2003 01:39:59 -0500 (EST)
Received: from ii0015exch002u.wins.lucent.com (h135-254-246-205.lucent.com [135.254.246.205])
	by hoemail2.firewall.lucent.com (Switch-2.2.2/Switch-2.2.0) with ESMTP id h1K6hkF00574
	for <rpsec@ietf.org>; Thu, 20 Feb 2003 01:43:47 -0500 (EST)
Received: from lucent.com (iidcw111.iidc.lucent.com [135.254.214.111]) by ii0015exch002u.wins.lucent.com with SMTP (Microsoft Exchange Internet Mail Service Version 5.5.2653.13)
	id FDRBKQK3; Thu, 20 Feb 2003 12:13:44 +0530
Message-ID: <3E547915.A05773DD@lucent.com>
Date: Thu, 20 Feb 2003 12:13:33 +0530
From: RajKumar <rajkumar@lucent.com>
Organization: Lucent Technologies
X-Mailer: Mozilla 4.76 [en] (X11; U; SunOS 5.8 sun4u)
X-Accept-Language: en
MIME-Version: 1.0
To: Tony Tauber <ttauber@genuity.net>
CC: rpsec@ietf.org
Subject: Re: [RPSEC] Requirements Subgroup Volunteers
References: <Pine.GSO.4.40.0302181722340.473-100000@mesa.bbnplanet.com>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit
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>
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit

Hi Tony,
I would like to volunteer.

Regards,
Rajkumar

Tony Tauber wrote:

> Hi folks,
>
> As we're closing in on the finalization of the merged "Generic
> Threats to Routing Protocols" draft (to be posted soon), we have to
> get moving on the "Generic Requirements" draft.
>
> Some volunteers are needed to help put this all together and Russ
> had the idea, which seems reasonable on the face of it, to form a
> "technical subgroup" of perhaps six or eight people to work through
> the development of the Requirements draft.
>
> Who would like to work on this thing and can really dedicate some
> cycles to it?  Please reply either to the list or to Russ and me
> privately.  If there are concerns with this approach or you'd like to
> sugggest an alternative, send via the same paths as above.
>
> Thanks,
>
> Tony
>
> _______________________________________________
> RPSEC mailing list
> RPSEC@ietf.org
> https://www1.ietf.org/mailman/listinfo/rpsec

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



From mailnull@www1.ietf.org  Thu Feb 20 11:14:54 2003
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 LAA19796
	for <rpsec-archive@odin.ietf.org>; Thu, 20 Feb 2003 11:14:53 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id h1KGLWt25160
	for rpsec-archive@odin.ietf.org; Thu, 20 Feb 2003 11:21:32 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h1KGLWp25157
	for <rpsec-web-archive@optimus.ietf.org>; Thu, 20 Feb 2003 11:21:32 -0500
Received: from www1.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA19772
	for <rpsec-web-archive@ietf.org>; Thu, 20 Feb 2003 11:14:22 -0500 (EST)
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h1KGKbp25074;
	Thu, 20 Feb 2003 11:20:38 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h1KGIVp24901
	for <rpsec@optimus.ietf.org>; Thu, 20 Feb 2003 11:18:31 -0500
Received: from aragorn.bbn.com (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA19556
	for <rpsec@ietf.org>; Thu, 20 Feb 2003 11:11:22 -0500 (EST)
Received: from [128.89.88.34] (comsec.bbn.com [128.89.88.34])
	by aragorn.bbn.com (8.12.7/8.12.7) with ESMTP id h1KG8vpp013779;
	Thu, 20 Feb 2003 11:09:04 -0500 (EST)
Mime-Version: 1.0
X-Sender: kent@po2.bbn.com
Message-Id: <p0510030eba7aad409ab4@[128.89.88.34]>
Date: Thu, 20 Feb 2003 11:05:53 -0500
To: Tony Tauber <ttauber@genuity.net>
From: Stephen Kent <kent@bbn.com>
Subject: Re: [RPSEC] Requirements Subgroup Volunteers
Cc: rpsec@ietf.org
Content-Type: text/plain; charset="us-ascii" ; format="flowed"
X-Scanned-By: MIMEDefang 2.28 (www . roaringpenguin . com / mimedefang)
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>

Tony,

I'll be glad to help out on this task.

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



From mailnull@www1.ietf.org  Thu Feb 20 11:47:45 2003
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 LAA20897
	for <rpsec-archive@odin.ietf.org>; Thu, 20 Feb 2003 11:47:45 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id h1KGsP728044
	for rpsec-archive@odin.ietf.org; Thu, 20 Feb 2003 11:54:25 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h1KGsPp28041
	for <rpsec-web-archive@optimus.ietf.org>; Thu, 20 Feb 2003 11:54:25 -0500
Received: from www1.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA20852
	for <rpsec-web-archive@ietf.org>; Thu, 20 Feb 2003 11:47:14 -0500 (EST)
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h1KGrap27876;
	Thu, 20 Feb 2003 11:53:36 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h1KGnFp27519
	for <rpsec@optimus.ietf.org>; Thu, 20 Feb 2003 11:49:15 -0500
Received: from sparte.int-evry.fr (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA20676
	for <rpsec@ietf.org>; Thu, 20 Feb 2003 11:42:04 -0500 (EST)
Received: from alpes.int-evry.fr (alpes.int-evry.fr [157.159.10.19])
	by spartebis.int-evry.fr (Postfix) with SMTP
	id 00B793F62E; Thu, 20 Feb 2003 17:58:16 +0100 (CET)
Received: from sparte.int-evry.fr ([157.159.10.11])
 by alpes.int-evry.fr (SAVSMTP 3.0.0.44) with SMTP id M2003022017455526437
 ; Thu, 20 Feb 2003 17:45:55 +0100
Received: from cthulhu.int-evry.fr (ivan.int-evry.fr [157.159.100.48])
	by sparte.int-evry.fr (Postfix) with ESMTP
	id B73093F62E; Thu, 20 Feb 2003 17:58:16 +0100 (CET)
Received: from jjp by cthulhu.int-evry.fr with local (Exim 3.36 #1 (Debian))
	id 18ltlr-0008FG-00; Thu, 20 Feb 2003 17:42:03 +0100
Date: Thu, 20 Feb 2003 17:42:03 +0100
From: Jean-Jacques Puig <Jean-Jacques.Puig@int-evry.fr>
To: Tony Tauber <ttauber@genuity.net>
Cc: rpsec@ietf.org
Subject: Re: [RPSEC] Requirements Subgroup Volunteers
Message-ID: <20030220164203.GA31681@ivan.int-evry.fr>
References: <Pine.GSO.4.40.0302181722340.473-100000@mesa.bbnplanet.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <Pine.GSO.4.40.0302181722340.473-100000@mesa.bbnplanet.com>
User-Agent: Mutt/1.4i
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>

On Tue, Feb 18, 2003 at 05:29:22PM -0500, Tony Tauber wrote:
> Hi folks,
> 
> As we're closing in on the finalization of the merged "Generic
> Threats to Routing Protocols" draft (to be posted soon), we have to
> get moving on the "Generic Requirements" draft.
> 
> Some volunteers are needed to help put this all together and Russ
> had the idea, which seems reasonable on the face of it, to form a
> "technical subgroup" of perhaps six or eight people to work through
> the development of the Requirements draft.
> 
> Who would like to work on this thing and can really dedicate some
> cycles to it?  Please reply either to the list or to Russ and me
> privately.  If there are concerns with this approach or you'd like to
> sugggest an alternative, send via the same paths as above.

I would like too volonteer too.
(I surely have some cycles for this and it is directly linked to my
studies)

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



From mailnull@www1.ietf.org  Thu Feb 20 12:23:16 2003
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 MAA22051
	for <rpsec-archive@odin.ietf.org>; Thu, 20 Feb 2003 12:23:16 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id h1KHTud31281
	for rpsec-archive@odin.ietf.org; Thu, 20 Feb 2003 12:29:56 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h1KHTup31278
	for <rpsec-web-archive@optimus.ietf.org>; Thu, 20 Feb 2003 12:29:56 -0500
Received: from www1.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA22034
	for <rpsec-web-archive@ietf.org>; Thu, 20 Feb 2003 12:22:45 -0500 (EST)
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h1KHT9p31240;
	Thu, 20 Feb 2003 12:29:09 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h1KHS2p31158
	for <rpsec@optimus.ietf.org>; Thu, 20 Feb 2003 12:28:02 -0500
Received: from sentry.gw.tislabs.com (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA21964
	for <rpsec@ietf.org>; Thu, 20 Feb 2003 12:20:51 -0500 (EST)
From: sandy@tislabs.com
Received: by sentry.gw.tislabs.com; id MAA19836; Thu, 20 Feb 2003 12:25:25 -0500 (EST)
Received: from raven.gw.tislabs.com(10.33.1.50) by sentry.gw.tislabs.com via smap (V5.5)
	id xma019825; Thu, 20 Feb 03 12:24:35 -0500
Received: (from sandy@localhost)
	by raven.gw.tislabs.com (8.11.6/8.11.6) id h1KHNq010672;
	Thu, 20 Feb 2003 12:23:52 -0500 (EST)
Date: Thu, 20 Feb 2003 12:23:52 -0500 (EST)
Message-Id: <200302201723.h1KHNq010672@raven.gw.tislabs.com>
To: ttauber@genuity.net
Subject: Re: [RPSEC] Requirements Subgroup Volunteers
Cc: rpsec@ietf.org
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>

> Some volunteers are needed to help put this all together and Russ
> had the idea, which seems reasonable on the face of it, to form a
> "technical subgroup" of perhaps six or eight people to work through
> the development of the Requirements draft.

I would like to work on this also.

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



From mailnull@www1.ietf.org  Thu Feb 20 14:25:25 2003
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 OAA26373
	for <rpsec-archive@odin.ietf.org>; Thu, 20 Feb 2003 14:25:25 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id h1KJW7U08363
	for rpsec-archive@odin.ietf.org; Thu, 20 Feb 2003 14:32:07 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h1KJW7p08360
	for <rpsec-web-archive@optimus.ietf.org>; Thu, 20 Feb 2003 14:32:07 -0500
Received: from www1.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA26370
	for <rpsec-web-archive@ietf.org>; Thu, 20 Feb 2003 14:24:54 -0500 (EST)
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h1KJVCp08306;
	Thu, 20 Feb 2003 14:31:12 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h1KJV0p08256
	for <rpsec@optimus.ietf.org>; Thu, 20 Feb 2003 14:31:00 -0500
Received: from sequoia.muada.com (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA26338
	for <rpsec@ietf.org>; Thu, 20 Feb 2003 14:23:48 -0500 (EST)
Received: from localhost (iljitsch@localhost)
	by sequoia.muada.com (8.11.3/8.9.3) with ESMTP id h1KJS7G20259
	for <rpsec@ietf.org>; Thu, 20 Feb 2003 20:28:07 +0100 (CET)
	(envelope-from iljitsch@muada.com)
Date: Thu, 20 Feb 2003 20:28:07 +0100 (CET)
From: Iljitsch van Beijnum <iljitsch@muada.com>
To: <rpsec@ietf.org>
Subject: Re: [RPSEC] Requirements Subgroup Volunteers
In-Reply-To: <200302201723.h1KHNq010672@raven.gw.tislabs.com>
Message-ID: <20030220202323.Q61596-100000@sequoia.muada.com>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
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>

> I would like to work on this also.

See, this is what I mean: pretty much all active members of the group
have volunteered.  :-)

I would also be happy to lend a hand if the fact that I'm not attending
the SF meeting isn't a problem. Or I can wait and provide a fresh point
of view when the subgroup is done.

Iljitsch

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



From mailnull@www1.ietf.org  Thu Feb 20 15:36:23 2003
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 PAA28786
	for <rpsec-archive@odin.ietf.org>; Thu, 20 Feb 2003 15:36:23 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id h1KKh6I14087
	for rpsec-archive@odin.ietf.org; Thu, 20 Feb 2003 15:43:06 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h1KKh6p14084
	for <rpsec-web-archive@optimus.ietf.org>; Thu, 20 Feb 2003 15:43:06 -0500
Received: from www1.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA28778
	for <rpsec-web-archive@ietf.org>; Thu, 20 Feb 2003 15:35:51 -0500 (EST)
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h1KKgDp14013;
	Thu, 20 Feb 2003 15:42:13 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h1KKfmp13954
	for <rpsec@optimus.ietf.org>; Thu, 20 Feb 2003 15:41:48 -0500
Received: from nwkea-mail-2.sun.com (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA28692
	for <rpsec@ietf.org>; Thu, 20 Feb 2003 15:34:34 -0500 (EST)
Received: from sydney.East.Sun.COM ([129.148.9.16])
	by nwkea-mail-2.sun.com (8.9.3+Sun/8.9.3) with ESMTP id MAA07657;
	Thu, 20 Feb 2003 12:38:15 -0800 (PST)
Received: from sr1-ubur-05 (sr1-ubur-05 [129.148.9.84])
	by sydney.East.Sun.COM (8.11.6+Sun/8.11.6/ENSMAIL,v2.2) with SMTP id h1KKcDM18794;
	Thu, 20 Feb 2003 15:38:13 -0500 (EST)
Message-Id: <200302202038.h1KKcDM18794@sydney.East.Sun.COM>
Date: Thu, 20 Feb 2003 15:38:13 -0500 (EST)
From: Radia Perlman - Boston Center for Networking <Radia.Perlman@Sun.COM>
Reply-To: Radia Perlman - Boston Center for Networking <Radia.Perlman@Sun.COM>
Subject: Re: [RPSEC] Requirements Subgroup Volunteers
To: rpsec@ietf.org, iljitsch@muada.com
MIME-Version: 1.0
Content-Type: TEXT/plain; charset=us-ascii
Content-MD5: 7IxRllFy757DxNEedkUIMA==
X-Mailer: dtmail 1.3.0 @(#)CDE Version 1.4.6_06 SunOS 5.8 sun4u sparc 
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>

Iljitsch said:

>>See, this is what I mean: pretty much all active members of the group
>>have volunteered.  :-)

Maybe he's right, and the email list for this document should just
be the regular list. The one nice thing about having specific volunteers
is that people actually feel a sense of responsibility. What would
probably be best is if there is one border collie that coordinates
and nags the rest of us sheep. I'm volunteering to be a sheep.

Radia

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



From mailnull@www1.ietf.org  Tue Feb 25 17:06:57 2003
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 RAA19668
	for <rpsec-archive@odin.ietf.org>; Tue, 25 Feb 2003 17:06:57 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id h1PMGA703750
	for rpsec-archive@odin.ietf.org; Tue, 25 Feb 2003 17:16:10 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h1PMGAp03747
	for <rpsec-web-archive@optimus.ietf.org>; Tue, 25 Feb 2003 17:16:10 -0500
Received: from www1.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA19647
	for <rpsec-web-archive@ietf.org>; Tue, 25 Feb 2003 17:06:26 -0500 (EST)
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h1PMEQp03660;
	Tue, 25 Feb 2003 17:14:29 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h1PFiXp06201
	for <rpsec@optimus.ietf.org>; Tue, 25 Feb 2003 10:44:33 -0500
Received: from polito.it (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA03552
	for <rpsec@ietf.org>; Tue, 25 Feb 2003 10:34:57 -0500 (EST)
Received: from [130.192.1.125] (account d004316 HELO polito.it)
  by polito.it (CommuniGate Pro SMTP 4.0.6)
  with ESMTP-TLS id 4297019; Tue, 25 Feb 2003 16:35:04 +0100
Message-ID: <3E5B8CDC.8010300@polito.it>
Date: Tue, 25 Feb 2003 16:33:48 +0100
From: Marco Aime <m.aime@polito.it>
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.2) Gecko/20021202
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: Tony Tauber <ttauber@genuity.net>
CC: rpsec@ietf.org, Corrado Derenale <derenale@polito.it>,
        Antonio Lioy <lioy@polito.it>
Subject: Re: [RPSEC] Requirements Subgroup Volunteers
References: <Pine.GSO.4.40.0302181722340.473-100000@mesa.bbnplanet.com>
In-Reply-To: <Pine.GSO.4.40.0302181722340.473-100000@mesa.bbnplanet.com>
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit
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>
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit

As members of TORSEC (i.e. the Computer and Network Security Group at
the Polythecnic of Turin, Italy - http://security.polito.it), we'd like
to volunteer to your call.

Two of us will actually work directly on the RPSEC task:

- Marco Domenico Aime - PhD Student - main research interests &
   competencies: network security (current research activity is focused
on
   security requirements in wireless networks, mainly 802.11-based ad-hoc
   networks), symmetric and asymmetric applied cryptography

- Corrado Derenale - PhD Student - main research interests &
   competencies: network security (current research activity is focused
on
   security requirements in IPv6 routing architecture), public-key
   certificate based systems

We are currently involved in the EU funded project "6net" in the
context of routing protocol security for IPv6 networks and our research
activity is heavily focused on RPSEC topic.

We are planning to dedicate, as a whole, a minimum of 30 man-hours per
month directly to the RPSEC activity.

I'm looking forward reading your answer.

Best regards,

Marco Aime

-- 
------------------------------------------------------------------
Marco AIME
Dipartimento di Automatica e Informatica
Politecnico di Torino
Addr: Via Cardinal Massaia 83, Torino, Italy
Tel: +39 011 22102-44
Fax: +39 011 22102-29
Mail: m.aime@polito.it (marcodomenico.aime@polito.it)
------------------------------------------------------------------

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



From mailnull@www1.ietf.org  Thu Feb 27 11:28:16 2003
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 LAA10285
	for <rpsec-archive@odin.ietf.org>; Thu, 27 Feb 2003 11:28:16 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id h1RGcKL00456
	for rpsec-archive@odin.ietf.org; Thu, 27 Feb 2003 11:38:20 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h1RGcJp00453
	for <rpsec-web-archive@optimus.ietf.org>; Thu, 27 Feb 2003 11:38:20 -0500
Received: from www1.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA10253
	for <rpsec-web-archive@ietf.org>; Thu, 27 Feb 2003 11:27:45 -0500 (EST)
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h1RGbLp32564;
	Thu, 27 Feb 2003 11:37:21 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h1RGaop32082
	for <rpsec@optimus.ietf.org>; Thu, 27 Feb 2003 11:36:50 -0500
Received: from relay.pair.com (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id LAA10225
	for <rpsec@ietf.org>; Thu, 27 Feb 2003 11:26:15 -0500 (EST)
Received: (qmail 7098 invoked from network); 27 Feb 2003 16:30:10 -0000
Received: from 208-59-250-149.c3-0.smr-ubr1.sbo-smr.ma.cable.rcn.com (HELO simon.lepp.com) (208.59.250.149)
  by relay.pair.com with SMTP; 27 Feb 2003 16:30:10 -0000
X-pair-Authenticated: 208.59.250.149
Message-Id: <5.0.2.1.2.20030227112935.047e3ee0@lepp.com>
X-Sender: marianne@lepp.com
X-Mailer: QUALCOMM Windows Eudora Version 5.0.2
Date: Thu, 27 Feb 2003 11:30:10 -0500
To: rpsec@ietf.org
From: Marianne Lepp <marianne@lepp.com>
Subject: Re: [RPSEC] Requirements Subgroup Volunteers
In-Reply-To: <200302202038.h1KKcDM18794@sydney.East.Sun.COM>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
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>

I am a very good collie.  And I don't bite.

At 03:38 PM 2/20/2003 -0500, Radia Perlman - Boston Center for Networking 
wrote:

>Iljitsch said:
>
> >>See, this is what I mean: pretty much all active members of the group
> >>have volunteered.  :-)
>
>Maybe he's right, and the email list for this document should just
>be the regular list. The one nice thing about having specific volunteers
>is that people actually feel a sense of responsibility. What would
>probably be best is if there is one border collie that coordinates
>and nags the rest of us sheep. I'm volunteering to be a sheep.
>
>Radia
>
>_______________________________________________
>RPSEC mailing list
>RPSEC@ietf.org
>https://www1.ietf.org/mailman/listinfo/rpsec

Marianne Lepp
617-666-0640    home
617-645-9019    mobile
Marianne@Lepp.com

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



