Re: [RPSEC] Consensus calls

"Tom Petch" <nwnetworks@dial.pipex.com> Thu, 11 December 2003 13:03 UTC

Received: from optimus.ietf.org ([132.151.1.19]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA28679 for <rpsec-archive@odin.ietf.org>; Thu, 11 Dec 2003 08:03:33 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AUQTB-0002eh-4z for rpsec-archive@odin.ietf.org; Thu, 11 Dec 2003 08:03:05 -0500
Received: (from exim@localhost) by www1.ietf.org (8.12.8/8.12.8/Submit) id hBBD358Z010204 for rpsec-archive@odin.ietf.org; Thu, 11 Dec 2003 08:03:05 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AUQTB-0002eV-0b for rpsec-web-archive@optimus.ietf.org; Thu, 11 Dec 2003 08:03:05 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA28663 for <rpsec-web-archive@ietf.org>; Thu, 11 Dec 2003 08:03:03 -0500 (EST)
Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 1AUQTA-0002gu-00 for rpsec-web-archive@ietf.org; Thu, 11 Dec 2003 08:03:04 -0500
Received: from [132.151.1.19] (helo=optimus.ietf.org) by ietf-mx with esmtp (Exim 4.12) id 1AUQT9-0002gr-00 for rpsec-web-archive@ietf.org; Thu, 11 Dec 2003 08:03:03 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AUQT6-0002d5-UK; Thu, 11 Dec 2003 08:03:00 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AUQSx-0002cg-JH for rpsec@optimus.ietf.org; Thu, 11 Dec 2003 08:02:51 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA28653 for <rpsec@ietf.org>; Thu, 11 Dec 2003 08:02:49 -0500 (EST)
Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 1AUQSw-0002gP-00 for rpsec@ietf.org; Thu, 11 Dec 2003 08:02:50 -0500
Received: from colossus.systems.pipex.net ([62.241.160.73]) by ietf-mx with esmtp (Exim 4.12) id 1AUQSv-0002fp-00 for rpsec@ietf.org; Thu, 11 Dec 2003 08:02:49 -0500
Received: from tom3 (1Cust191.tnt29.lnd3.gbr.da.uu.net [62.188.120.191]) by colossus.systems.pipex.net (Postfix) with SMTP id 1EC7316000184; Thu, 11 Dec 2003 13:02:18 +0000 (GMT)
Message-ID: <004801c3bfe7$04f93f60$0301a8c0@tom3>
Reply-To: Tom Petch <nwnetworks@dial.pipex.com>
From: Tom Petch <nwnetworks@dial.pipex.com>
To: Tony Tauber <tony.tauber@level3.com>, rpsec@ietf.org
Subject: Re: [RPSEC] Consensus calls
Date: Thu, 11 Dec 2003 12:47:16 -0000
MIME-Version: 1.0
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 4.72.2106.4
X-MimeOLE: Produced By Microsoft MimeOLE V4.72.2106.4
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

Inline

-----Original Message-----
From: Tony Tauber <tony.tauber@level3.com>
To: rpsec@ietf.org <rpsec@ietf.org>
Date: 10 December 2003 05:09
Subject: [RPSEC] Consensus calls


Yes, I believe that protocol specific work does belong in RPSEC.  The work
spans two distinct areas, routing and security, and so there is not one
clear, right answer.  But on balance I see the security considerations as
the harder to deal with, the one where greater specialist expertise is
needed,  that the security group is more likely to have the necessary
routing skills than the routing group will have adequate security skills.
So do the work in RPSEC.


>2) Should the RPSEC charter be amended to allow for the acceptance of
>   protocol-specific work?  (Removing the sentence below should do that.)
>
>   ++> It is also a non-goal at this point to produce new or change the
>   ++> current security mechanisms in the existing routing protocols.
>
>3) Should draft-convery-bgpattack-01.txt be accepted as a WG work item?
>
>4) Should draft-jones-OSPF-vuln-01.txt be accepted as a WG work item?
>
>(See meeting minutes at
http://ietf.org/proceedings/03nov/minutes/rpsec.htm
>for more details if desired.)
>
>Thanks,
>
>Tony



Tom Petch, Network Consultant
nwnetworks@dial.pipex.com



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