Re: [OSPF] OSPF HMAC-SHA Cryptographic Authentication

"Bhatia, Manav (Manav)" <manav@alcatel-lucent.com> Thu, 19 March 2009 05:07 UTC

Return-Path: <manav@alcatel-lucent.com>
X-Original-To: ospf@core3.amsl.com
Delivered-To: ospf@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 715943A68AA for <ospf@core3.amsl.com>; Wed, 18 Mar 2009 22:07:28 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.249
X-Spam-Level:
X-Spam-Status: No, score=-6.249 tagged_above=-999 required=5 tests=[AWL=-0.000, BAYES_00=-2.599, HELO_EQ_FR=0.35, RCVD_IN_DNSWL_MED=-4]
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 GJjg1ouIlBhf for <ospf@core3.amsl.com>; Wed, 18 Mar 2009 22:07:27 -0700 (PDT)
Received: from smail5.alcatel.fr (smail5.alcatel.fr [64.208.49.27]) by core3.amsl.com (Postfix) with ESMTP id 68ABA3A6877 for <ospf@ietf.org>; Wed, 18 Mar 2009 22:07:27 -0700 (PDT)
Received: from FRMRSSXCHHUB04.dc-m.alcatel-lucent.com (FRMRSSXCHHUB04.dc-m.alcatel-lucent.com [135.120.45.64]) by smail5.alcatel.fr (8.13.8/8.13.8/ICT) with ESMTP id n2J58AJn024641 (version=TLSv1/SSLv3 cipher=RC4-MD5 bits=128 verify=NOT); Thu, 19 Mar 2009 06:08:10 +0100
Received: from INBANSXCHHUB01.in.alcatel-lucent.com (135.250.12.32) by FRMRSSXCHHUB04.dc-m.alcatel-lucent.com (135.120.45.64) with Microsoft SMTP Server (TLS) id 8.1.340.0; Thu, 19 Mar 2009 06:08:10 +0100
Received: from INBANSXCHMBSA1.in.alcatel-lucent.com ([135.250.12.59]) by INBANSXCHHUB01.in.alcatel-lucent.com ([135.250.12.32]) with mapi; Thu, 19 Mar 2009 10:37:49 +0530
From: "Bhatia, Manav (Manav)" <manav@alcatel-lucent.com>
To: John Smith <jsmith4112003@yahoo.co.uk>
Date: Thu, 19 Mar 2009 10:37:45 +0530
Thread-Topic: [OSPF] OSPF HMAC-SHA Cryptographic Authentication
Thread-Index: Acml0wUW3ZYy6sCKQ/C3Mp4As00ZcgCewQdg
Message-ID: <7C362EEF9C7896468B36C9B79200D8357AF6DE47@INBANSXCHMBSA1.in.alcatel-lucent.com>
References: <414371.22999.qm@web27205.mail.ukl.yahoo.com>
In-Reply-To: <414371.22999.qm@web27205.mail.ukl.yahoo.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
acceptlanguage: en-US
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-Scanned-By: MIMEDefang 2.57 on 155.132.188.13
Cc: "ospf@ietf.org" <ospf@ietf.org>
Subject: Re: [OSPF] OSPF HMAC-SHA Cryptographic Authentication
X-BeenThere: ospf@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: The Official IETF OSPG WG Mailing List <ospf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/ospf>, <mailto:ospf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ospf>
List-Post: <mailto:ospf@ietf.org>
List-Help: <mailto:ospf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ospf>, <mailto:ospf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 19 Mar 2009 05:07:28 -0000

Hi John,

> 
> I was reading draft-ietf-ospf-hmac-sha-03.txt and i think its 
> good and very readable.However, a small nit with the draft: 
> All references to other draft sections are off by 1 - thus a 
> reference to section 3 and 5 in section 5.1 should be 4 and 6 
> really. :-)

Thanks. Will fix it.

> 
> Its been around for a long time now and i have never seen any 
> opposition/changes. Is there a reason why its not close to WG LC yet?

There are some folks who believe that we should align our crypto-mathematics with how its done in IS-IS and RIP (https://www.ietf.org/proceedings/08nov/slides/ospf-5.pdf). However, the other argument is that though it did make a trifle bit of sense in doing it for IS-IS and RIP, it makes none, none at all, for OSPF. 

It is only this that's stalling the document from moving ahead which is otherwise ready for WG LC.

Cheers, Manav

> 
> John
> 
> P.S.
> 
> It seems as Dave reflected some time back, that OSPF is 
> lagging far behind IS-IS and RIP as these WGs
> (i know there is none for RIP) have already come out with RFCs
> extending ISIS/RIP for HMAC-SHA support, while OSPF is still 
> struggling on.