[RPSEC] Consensus calls

Tony Tauber <tony.tauber@level3.com> Wed, 10 December 2003 05:09 UTC

Received: from optimus.ietf.org ([132.151.1.19]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id AAA02406 for <rpsec-archive@odin.ietf.org>; Wed, 10 Dec 2003 00:09:25 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1ATwb1-00010x-UF for rpsec-archive@odin.ietf.org; Wed, 10 Dec 2003 00:09:12 -0500
Received: (from exim@localhost) by www1.ietf.org (8.12.8/8.12.8/Submit) id hBA59Bi7003893 for rpsec-archive@odin.ietf.org; Wed, 10 Dec 2003 00:09:11 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1ATwb1-00010i-PI for rpsec-web-archive@optimus.ietf.org; Wed, 10 Dec 2003 00:09:11 -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 AAA02402 for <rpsec-web-archive@ietf.org>; Wed, 10 Dec 2003 00:08:54 -0500 (EST)
Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 1ATwaz-0002gy-00 for rpsec-web-archive@ietf.org; Wed, 10 Dec 2003 00:09:09 -0500
Received: from [132.151.1.19] (helo=optimus.ietf.org) by ietf-mx with esmtp (Exim 4.12) id 1ATway-0002gu-00 for rpsec-web-archive@ietf.org; Wed, 10 Dec 2003 00:09:08 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1ATwar-0000zS-1X; Wed, 10 Dec 2003 00:09:01 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1ATwad-0000zB-Mr for rpsec@optimus.ietf.org; Wed, 10 Dec 2003 00:08:47 -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 AAA02394 for <rpsec@ietf.org>; Wed, 10 Dec 2003 00:08:30 -0500 (EST)
Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 1ATwab-0002gQ-00 for rpsec@ietf.org; Wed, 10 Dec 2003 00:08:45 -0500
Received: from machine77.level3.com ([209.244.4.106] helo=scanner1.l3.com) by ietf-mx with esmtp (Exim 4.12) id 1ATwaa-0002fu-00 for rpsec@ietf.org; Wed, 10 Dec 2003 00:08:44 -0500
Received: from scanner1.l3.com (localhost [127.0.0.1]) by localhost.l3.com (Postfix) with ESMTP id A6B6578B51E for <rpsec@ietf.org>; Wed, 10 Dec 2003 05:08:15 +0000 (GMT)
Received: from buzz.idc1.level3.com (qfe0.buzz.idc1.oss.level3.com [10.1.116.4]) by scanner1.l3.com (Postfix) with ESMTP id 6669778B499 for <rpsec@ietf.org>; Wed, 10 Dec 2003 05:08:15 +0000 (GMT)
Received: from localhost (ttauber@localhost) by buzz.idc1.level3.com (8.8.8p2+Sun/8.8.8) with ESMTP id FAA26502 for <rpsec@ietf.org>; Wed, 10 Dec 2003 05:08:15 GMT
X-Authentication-Warning: buzz.idc1.level3.com: ttauber owned process doing -bs
Date: Wed, 10 Dec 2003 05:08:14 +0000
From: Tony Tauber <tony.tauber@level3.com>
X-X-Sender: ttauber@buzz.idc1.level3.com
To: rpsec@ietf.org
Message-ID: <Pine.GSO.4.58.0312100455260.28563@buzz.idc1.level3.com>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset="US-ASCII"
Subject: [RPSEC] Consensus calls
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>

Folks,

At the meeting in Minneapolis, the sense of the room was that there
was positive support for these proposals:

1) Should draft-puig-rpsec-generic-requirements-01.txt be accepted as
   a WG work item?

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?

Please respond with your opinions.

(See meeting minutes at http://ietf.org/proceedings/03nov/minutes/rpsec.htm
for more details if desired.)

Thanks,

Tony

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