[RPSEC] about the charter and work items
sandy@tislabs.com Thu, 22 June 2006 15:12 UTC
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1FtQrO-0001f4-Br; Thu, 22 Jun 2006 11:12:46 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1FtQrM-0001dF-Vt for rpsec@ietf.org; Thu, 22 Jun 2006 11:12:44 -0400
Received: from nutshell.tislabs.com ([192.94.214.100]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1FtQrL-00087r-12 for rpsec@ietf.org; Thu, 22 Jun 2006 11:12:44 -0400
Received: (from uucp@localhost) by nutshell.tislabs.com (8.12.9/8.12.9) id k5MEpPtp019047 for <rpsec@ietf.org>; Thu, 22 Jun 2006 10:51:26 -0400 (EDT)
Received: from filbert.tislabs.com(10.66.1.10) by nutshell.tislabs.com via csmap (V6.0) id srcAAASvaOiL; Thu, 22 Jun 06 10:51:11 -0400
Received: (from sandy@localhost) by tislabs.com (8.12.9/8.12.9) id k5ME8rlQ018182; Thu, 22 Jun 2006 10:08:53 -0400 (EDT)
Date: Thu, 22 Jun 2006 10:08:53 -0400
Message-Id: <200606221408.k5ME8rlQ018182@tislabs.com>
From: sandy@tislabs.com
To: rpsec@ietf.org
X-Spam-Score: 0.2 (/)
X-Scan-Signature: d6b246023072368de71562c0ab503126
Cc: sandy@tislabs.com
Subject: [RPSEC] about the charter and work items
X-BeenThere: rpsec@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Routing Protocol Security Requirements <rpsec.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/rpsec>, <mailto:rpsec-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www1.ietf.org/pipermail/rpsec>
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>
Errors-To: rpsec-bounces@ietf.org
Russ said that he was going to check about the status of charter changes. I'd like also to mention one possible additional work item. At the mike at the last IETF, I mentioned taking on the draft that looks at damage if MD5 is broken. The response was that this was probably the OSPF vulnerability analysis mentioned in the slides. (Unfortunately, this comment was too small to make it to the minutes, so I'm working off memory here.) But I was speaking of draft-manral-rpsec-existing-crypto-02.txt, not the recently announced draft-ietf-rpsec-ospf-vuln-02.txt I believe that there is value in looking at the damage to various protocols that use keyed MD5 as an authentication mechanism - as an impetus to change and as a warning to operators while MD5 is still used. So I'm in favor of taking on the Manral draft. Comments? --Sandy _______________________________________________ RPSEC mailing list RPSEC@ietf.org https://www1.ietf.org/mailman/listinfo/rpsec
- [RPSEC] about the charter and work items sandy
- Re: [RPSEC] about the charter and work items Russ White
- Re: [RPSEC] about the charter and work items Tony Tauber
- Re: [RPSEC] about the charter and work items sandy
- Re: [RPSEC] about the charter and work items Vishwas Manral