Re: [RPSEC] about the charter and work items

Russ White <riw@cisco.com> Fri, 23 June 2006 00:07 UTC

Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1FtZD9-00063S-Rl; Thu, 22 Jun 2006 20:07:47 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1FtZD8-0005lk-5q for rpsec@ietf.org; Thu, 22 Jun 2006 20:07:46 -0400
Received: from rtp-iport-2.cisco.com ([64.102.122.149]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1FtZD6-0003GB-Us for rpsec@ietf.org; Thu, 22 Jun 2006 20:07:46 -0400
Received: from rtp-core-2.cisco.com ([64.102.124.13]) by rtp-iport-2.cisco.com with ESMTP; 22 Jun 2006 20:07:43 -0400
X-IronPort-AV: i="4.06,167,1149480000"; d="scan'208"; a="90832511:sNHT29271876"
Received: from [10.20.218.174] (rtp-vpn3-395.cisco.com [10.82.217.141]) by rtp-core-2.cisco.com (8.12.10/8.12.6) with ESMTP id k5N07gno028917; Thu, 22 Jun 2006 20:07:42 -0400 (EDT)
Message-ID: <449B30D2.20105@cisco.com>
Date: Thu, 22 Jun 2006 20:07:46 -0400
From: Russ White <riw@cisco.com>
User-Agent: Thunderbird 1.5.0.4 (Macintosh/20060530)
MIME-Version: 1.0
To: sandy@tislabs.com
Subject: Re: [RPSEC] about the charter and work items
References: <200606221408.k5ME8rlQ018182@tislabs.com>
In-Reply-To: <200606221408.k5ME8rlQ018182@tislabs.com>
X-Enigmail-Version: 0.94.0.0
Content-Type: text/plain; charset="ISO-8859-1"
Content-Transfer-Encoding: 7bit
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 7baded97d9887f7a0c7e8a33c2e3ea1b
Cc: rpsec@ietf.org
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

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1


> 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.

I've been getting the ospf vulnerability draft and the existing crypto
drafts mixed up--how about if we ask both to be presented in Montreal,
and then think about (take a hum about) taking them on as WG items? I
think we might have already covered this space before (in terms of
taking them on as WG items), but it might be good to do a level set of
where we are, and what we need to work on.

:-)

Russ


-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.1 (Darwin)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iD8DBQFEmzDRER27sUhU9OQRAt4RAJ9M62fBRabHyoDjPU3xGMycU8M9gACdEcpQ
2RzZrc/n+LTY/RVrJHogy28=
=V/b+
-----END PGP SIGNATURE-----

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