Re: Using AH for Authentication for OSPFv3

Ramana Yarlagadda <ramana.yarlagadda@analog.com> Tue, 14 May 2002 18:26 UTC

Received: from lists.tislabs.com (portal.gw.tislabs.com [192.94.214.101]) by above.proper.com (8.11.6/8.11.3) with ESMTP id g4EIQQL15334; Tue, 14 May 2002 11:26:26 -0700 (PDT)
Received: by lists.tislabs.com (8.9.1/8.9.1) id NAA01485 Tue, 14 May 2002 13:38:54 -0400 (EDT)
Message-Id: <4.3.2.7.1.20020514102916.00ae88a0@golf.cpgdesign.analog.com>
X-Sender: ramana@golf.cpgdesign.analog.com
X-Mailer: QUALCOMM Windows Eudora Version 4.3.2
Date: Tue, 14 May 2002 10:49:30 -0700
To: Mukesh Gupta <mgupta@iprg.nokia.com>, ospf@discuss.microsoft.com, ipsec@lists.tislabs.com
From: Ramana Yarlagadda <ramana.yarlagadda@analog.com>
Subject: Re: Using AH for Authentication for OSPFv3
In-Reply-To: <3CE04B50.63529636@iprg.nokia.com>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format="flowed"
Sender: owner-ipsec@lists.tislabs.com
Precedence: bulk

HI,


>I am working on providing authentication for OSPFv3 using IPv6 AH
>extension header.
>
>RFC 2740 suggests using AH/ESP extension headers of IPv6 for OSPF
>authentication but doesn't provide details about how exactly this needs
>to be done.
>
>It seems that OSPFv3 shouldn't need to worry about it and it is kernel's
>responsibility to provide AH authentication for all OSPFv3 packets. This
>way OSPFv3 only receives authenticated packets.

IPSec provides security at IP level so the OSPF may not need any special
mechanism  to provide security services to OSPF data. All you might need
is to configure a policy.


>OSPFv3 uses both multicast and unicast packets. Is there any standard
>way of handling these packets using IPsec AH ??
>
>Is there any standard way of implementing OSPFv3 Authentication using AH
>extension header ?? Is there any vendor out there who has implemented it
>??

The RFC2740 clearly says that OSPF is not doing any Authentication part.
For your reference i am copying the RFC...

Authentication has been removed from the OSPF protocol   itself, instead 
relying
on IPv6's Authentication Header and Encapsulating Security Payload.


>Comments/Suggestions would be highly appreciated.

-cheers
-ramana