IETF Logo Mail Archive

Re: OSPFv2 Opaque LSAs in OSPFv3

Kireeti Kompella <kireeti@JUNIPER.NET> Tue, 08 October 2002 02:56 UTC

Received: from cherry.ease.lsoft.com (cherry.ease.lsoft.com [209.119.0.109]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id WAA15777 for <ospf-archive@LISTS.IETF.ORG>; Mon, 7 Oct 2002 22:56:28 -0400 (EDT)
Received: from walnut (209.119.0.61) by cherry.ease.lsoft.com (LSMTP for Digital Unix v1.1b) with SMTP id <0.0075D749@cherry.ease.lsoft.com>; Mon, 7 Oct 2002 22:58:31 -0400
Received: from DISCUSS.MICROSOFT.COM by DISCUSS.MICROSOFT.COM (LISTSERV-TCP/IP release 1.8e) with spool id 258241 for OSPF@DISCUSS.MICROSOFT.COM; Mon, 7 Oct 2002 22:58:31 -0400
Received: from 207.17.136.129 by WALNUT.EASE.LSOFT.COM (SMTPL release 1.0f) with TCP; Mon, 7 Oct 2002 22:58:30 -0400
Received: from kummer.juniper.net (kummer.juniper.net [172.17.12.90]) by merlot.juniper.net (8.11.3/8.11.3) with ESMTP id g982wUm43538 for <OSPF@DISCUSS.MICROSOFT.COM>; Mon, 7 Oct 2002 19:58:30 -0700 (PDT) (envelope-from kireeti@juniper.net)
Received: (from kireeti@localhost) by kummer.juniper.net (8.11.6/8.9.3) id g982wUg98298 for OSPF@DISCUSS.MICROSOFT.COM; Mon, 7 Oct 2002 19:58:30 -0700 (PDT) (envelope-from kireeti)
Message-ID: <200210080258.g982wUg98298@kummer.juniper.net>
Date: Mon, 07 Oct 2002 19:58:30 -0700
Reply-To: Mailing List <OSPF@DISCUSS.MICROSOFT.COM>
Sender: Mailing List <OSPF@DISCUSS.MICROSOFT.COM>
From: Kireeti Kompella <kireeti@JUNIPER.NET>
Subject: Re: OSPFv2 Opaque LSAs in OSPFv3
To: OSPF@DISCUSS.MICROSOFT.COM
In-Reply-To: <m2adlp1xlb.wl@titanium.zebra.org>
Precedence: list

Hi Kunihiro,

> BTW I haven't submitted the draft but I prepared TE extensions to
> OSPFv3.  I just define a new LS type for TE then use OSPFv3 built in
> flooding mechanism.  I believe this is straight forward way to do it.

The draft I submitted also uses the OSPFv3 built in flooding.  It is the
only way to do it.

>  LSA function code  LS Type  Description
>  --------------------------------------------------------------------
>  10                 0x2000a  Traffic-Engineering-LSA

Do you plan to have a different Function Code for each OSPFv2 Opaque LSA
Type?

It seems to me to be much easier to have a single code point for all
OSPFv2 Opaque LSAs.  This way, all defined OSPFv2 Opaque LSAs get
automatically defined in v3; moreover, if a new Opaque LSA seems to be
useful for both v2 and v3, it can be defined as an OSPFv2 Opaque LSA.

Kireeti.

v2.39.1 | Report a Bug | By Email | System Status