Re: [RPSEC] about the charter and work items

Tony Tauber <ttauber@1-4-5.net> Fri, 23 June 2006 17:28 UTC

Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1FtpS6-0000TT-6f; Fri, 23 Jun 2006 13:28:18 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1FtpS5-0000TH-3L for rpsec@ietf.org; Fri, 23 Jun 2006 13:28:17 -0400
Received: from m106.maoz.com ([205.167.76.9]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1FtpS3-0007aV-Mm for rpsec@ietf.org; Fri, 23 Jun 2006 13:28:17 -0400
Received: from m106.maoz.com (localhost.localdomain [127.0.0.1]) by m106.maoz.com (8.13.6/8.13.6) with ESMTP id k5NHSEud021538; Fri, 23 Jun 2006 10:28:14 -0700
Received: from localhost (ttauber@localhost) by m106.maoz.com (8.13.6/8.12.11/Submit) with ESMTP id k5NHSA04021535; Fri, 23 Jun 2006 10:28:10 -0700
X-Authentication-Warning: m106.maoz.com: ttauber owned process doing -bs
Date: Fri, 23 Jun 2006 10:28:10 -0700
From: Tony Tauber <ttauber@1-4-5.net>
X-X-Sender: ttauber@m106.maoz.com
To: Russ White <riw@cisco.com>
Subject: Re: [RPSEC] about the charter and work items
In-Reply-To: <449B30D2.20105@cisco.com>
Message-ID: <Pine.LNX.4.64.0606231011160.12931@m106.maoz.com>
References: <200606221408.k5ME8rlQ018182@tislabs.com> <449B30D2.20105@cisco.com>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset="US-ASCII"; format="flowed"
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 538aad3a3c4f01d8b6a6477ca4248793
Cc: rpsec@ietf.org, sandy@tislabs.com
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

On Thu, 22 Jun 2006, Russ White wrote:

>> 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 agree the Manral draft appears relevant, however, I'm not sure your
characterization of it's thrust is accurate.

The OSPF vulnerability draft is already a WG document.

As for presentation ideas for Montreal, bring 'em on.

Tony

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

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