Re: draft-ietf-ospf-ospfv3-auth-04.txt

Vishwas Manral <Vishwas@SINETT.COM> Tue, 13 July 2004 14:30 UTC

Received: from ( []) by (8.9.1a/8.9.1a) with ESMTP id KAA14572 for <ospf-archive@LISTS.IETF.ORG>; Tue, 13 Jul 2004 10:30:40 -0400 (EDT)
Received: from ( by (LSMTP for Digital Unix v1.1b) with SMTP id <>; Tue, 13 Jul 2004 10:30:40 -0400
Received: from PEACH.EASE.LSOFT.COM by PEACH.EASE.LSOFT.COM (LISTSERV-TCP/IP release 1.8e) with spool id 25740324 for OSPF@PEACH.EASE.LSOFT.COM; Tue, 13 Jul 2004 10:30:39 -0400
Received: from by WALNUT.EASE.LSOFT.COM (SMTPL release 1.0i) with TCP; Tue, 13 Jul 2004 10:30:39 -0400
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
X-MimeOLE: Produced By Microsoft Exchange V6.5.6944.0
Thread-Topic: draft-ietf-ospf-ospfv3-auth-04.txt
Thread-Index: AcRng1qFm0Tkslo7RzyrDXbIrTakBwBX+1Og
Message-ID: <BB6D74C75CC76A419B6D6FA7C38317B22E8377@sinett-sbs.SiNett.LAN>
Date: Tue, 13 Jul 2004 07:33:31 -0700
Reply-To: Mailing List <OSPF@PEACH.EASE.LSOFT.COM>
Sender: Mailing List <OSPF@PEACH.EASE.LSOFT.COM>
From: Vishwas Manral <Vishwas@SINETT.COM>
Subject: Re: draft-ietf-ospf-ospfv3-auth-04.txt
Precedence: list
Content-Transfer-Encoding: quoted-printable

Hi Abhay,

Hmmmm. That way you will have to work on all relevent OSPFv2 RFC's for OSPFv3 for IPv4.(a lot of work). Things like NSSA/TE/Hitless Restart and every new functionality to OSPFv2.

Maybe if a generalized mechanism to carry OSPFv2 LSA's(I think Kireeti pointed this out sometime) in OSPFv3 framework was there, it would be helpful?

Besides that I think a small writeup on the NSSA changes for OSPFv3(because of changes of the NSSA RFC) would be helpful too. Things like Nt bit, optional summary importing, setting of forwarding addresses etc. Anybody else willing?


-----Original Message-----
From: Mailing List [mailto:OSPF@PEACH.EASE.LSOFT.COM]On Behalf Of Abhay
Sent: Monday, July 12, 2004 1:39 AM
Subject: Re: draft-ietf-ospf-ospfv3-auth-04.txt


As the draft stands today, it doesn't venture into the security
mechanism(s). I guess we need to add something. My preference will
be to stick with IPSec even for OSPFv3 IPv4 AF (irrespective of
ipv4 or ipv6 transport).


On 07/05/04-0700 at 10:41pm, Vishwas Manral writes:

> Hi Abhay,
> Good point, didnt know the draft was actually out(actually I
> think Sina/Michael actually started working on it togather a
> long long while back before the idea was dropped). Just curious
> would we still use IPSec or would we use the current
> authentication mechanism?
> To add further, we intend to add a draft to allow out of order
> sequence of packets with authentication enabled like in IPSec
> for OSPFv2 too. (IP does not guarentee inorder dilevery
> anyway/besides we can allow for packet prioritization)
> Thanks,
> Vishwas
> -----Original Message-----
> From: Mailing List [mailto:OSPF@PEACH.EASE.LSOFT.COM]On Behalf Of Abhay
> Roy
> Sent: Tuesday, July 06, 2004 11:04 AM
> Subject: Re: draft-ietf-ospf-ospfv3-auth-04.txt
> On 07/05/04-0500 at 2:19pm, Mukesh.Gupta@NOKIA.COM writes:
> > Hi Vishwas,
> >
> > Thanks for the comments.  Please see my comments inline..
> >
> > > 1. I am not sure we should have a statement which says OSPFv3
> > > is only for IPv6.
> > > "As OSPFv2 is only for IPv4 and OSPFv3 is only for IPv6,
> > > the distinction between the packets can be easily made by
> > > IP version. "
> >
> > Do you have a replacement statement that you would prefer ?
> > As the IP protocol type value for OSPF and OSPFv3 is same,
> > we have to depend upon the IP version to separate OSPF and
> > OSPFv3 packets.
> Just FYI, we can run OSPFv3 using IPv4 transport (see section 9 of
> draft-mirtorabi-ospfv3-af-alt-01.txt). In which case the demux
> will be based on OSPF protocol version.
> Regards,
> -Roy-