IETF Logo Mail Archive

Re: [OPSEC] draft-bhatia-manral-igp-crypto-requirements-03.txt

"Glen Kent" <glen.kent@gmail.com> Tue, 09 December 2008 22:55 UTC

Return-Path: <opsec-bounces@ietf.org>
X-Original-To: opsec-archive@optimus.ietf.org
Delivered-To: ietfarch-opsec-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 77CA13A6B0E; Tue, 9 Dec 2008 14:55:12 -0800 (PST)
X-Original-To: opsec@core3.amsl.com
Delivered-To: opsec@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 1744D3A6B0E for <opsec@core3.amsl.com>; Tue, 9 Dec 2008 14:55:11 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level:
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id g+L0pYJWcj6C for <opsec@core3.amsl.com>; Tue, 9 Dec 2008 14:55:08 -0800 (PST)
Received: from mail-bw0-f13.google.com (mail-bw0-f13.google.com [209.85.218.13]) by core3.amsl.com (Postfix) with ESMTP id 6127C3A6A5E for <opsec@ietf.org>; Tue, 9 Dec 2008 14:55:08 -0800 (PST)
Received: by bwz6 with SMTP id 6so471459bwz.13 for <opsec@ietf.org>; Tue, 09 Dec 2008 14:55:02 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:message-id:date:from:to :subject:cc:in-reply-to:mime-version:content-type :content-transfer-encoding:content-disposition:references; bh=cWLpE2zOiXcRy2fp6S9Ia46z3yLaCDdMCoy9UuBJQXE=; b=MSjWfgdTT021me6ohfrKSt9vQPTzYVylvRkTP3tvDsaWt8D636CptgE91/kFkJHcYg FalzZNwYMWVFqtlrGlkulEDRuv02J0R22q3a0DWUqe4kDQKYo8IMmIC8aGVTG54HaCvg HUMTRGUzyk1jf7f9jhg2PjWKlT3NaUOSvpfps=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:from:to:subject:cc:in-reply-to:mime-version :content-type:content-transfer-encoding:content-disposition :references; b=RXbkKbuByIaUj9Msy7sRGnpift/jSV1kf3FfLuYYwyiP5aiz4zqpU5HkRM2bd70fHb 0U26ekr3Nner9LVfpvcR1o0x0/3HQ0almETcQVcyfbOuRAh76JLYEa3eO6MPI7f6Ly7D MHWngQhuDJnVyvzDBqh9RsjDj/V5Hd4zJ0J2M=
Received: by 10.103.93.18 with SMTP id v18mr269495mul.111.1228863296872; Tue, 09 Dec 2008 14:54:56 -0800 (PST)
Received: by 10.103.160.12 with HTTP; Tue, 9 Dec 2008 14:54:56 -0800 (PST)
Message-ID: <92c950310812091454u5fc4471dg130563a8bb52c5da@mail.gmail.com>
Date: Wed, 10 Dec 2008 04:24:56 +0530
From: Glen Kent <glen.kent@gmail.com>
To: "Bhatia, Manav (Manav)" <manav@alcatel-lucent.com>
In-Reply-To: <6D26D1FE43A66F439F8109CDD42419650240AF59@INEXC1U01.in.lucent.com>
MIME-Version: 1.0
Content-Disposition: inline
References: <6D26D1FE43A66F439F8109CDD424196502356DBA@INEXC1U01.in.lucent.com> <92c950310812030850q5c76f39ak1754c70dc216a354@mail.gmail.com> <6D26D1FE43A66F439F8109CDD42419650240AF59@INEXC1U01.in.lucent.com>
Cc: opsec wg mailing list <opsec@ietf.org>
Subject: Re: [OPSEC] draft-bhatia-manral-igp-crypto-requirements-03.txt
X-BeenThere: opsec@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: opsec wg mailing list <opsec.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/opsec>, <mailto:opsec-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/pipermail/opsec>
List-Post: <mailto:opsec@ietf.org>
List-Help: <mailto:opsec-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/opsec>, <mailto:opsec-request@ietf.org?subject=subscribe>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: opsec-bounces@ietf.org
Errors-To: opsec-bounces@ietf.org

Hi,

> We have the following text in the Introduction.
>
> "It should however be noted that these attacks may not necessarily
> result in direct vulnerabilities in Keyed-MD5 as used in the routing
> protocols for authentication purposes, because the colliding message may
> not necessarily be a syntactically correct protocol packet. However,
> there is a need felt to move away from MD5 towards more complex and
> difficult to break hash algorithms."

Sorry, i missed this.

>
> Is there something specific that you are looking for?

No, not really.

Glen.
_______________________________________________
OPSEC mailing list
OPSEC@ietf.org
https://www.ietf.org/mailman/listinfo/opsec

v2.23.0 | Report a Bug | By Email