Re: OSPFv2 Opaque LSAs in OSPFv3

Alex Zinin <zinin@PSG.COM> Mon, 14 October 2002 17:55 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 NAA27941 for <ospf-archive@LISTS.IETF.ORG>; Mon, 14 Oct 2002 13:55:44 -0400 (EDT)
Received: from walnut (209.119.0.61) by cherry.ease.lsoft.com (LSMTP for Digital Unix v1.1b) with SMTP id <12.0076F28A@cherry.ease.lsoft.com>; Mon, 14 Oct 2002 13:57:53 -0400
Received: from DISCUSS.MICROSOFT.COM by DISCUSS.MICROSOFT.COM (LISTSERV-TCP/IP release 1.8e) with spool id 292598 for OSPF@DISCUSS.MICROSOFT.COM; Mon, 14 Oct 2002 13:57:53 -0400
Received: from 147.28.0.62 by WALNUT.EASE.LSOFT.COM (SMTPL release 1.0f) with TCP; Mon, 14 Oct 2002 13:57:53 -0400
Received: from psg.com ([147.28.0.62] helo=127.0.0.1 ident=zinin) by psg.com with esmtp (Exim 3.36 #2) id 1819TT-000220-00; Mon, 14 Oct 2002 10:57:51 -0700
X-Mailer: The Bat! (v1.51) Personal
X-Priority: 3 (Normal)
References: <39469E08BD83D411A3D900204840EC557633DC@vie-msgusr-01.dc.fore.com>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Message-ID: <4472366557.20021014105552@psg.com>
Date: Mon, 14 Oct 2002 10:55:52 -0700
Reply-To: Mailing List <OSPF@DISCUSS.MICROSOFT.COM>
Sender: Mailing List <OSPF@DISCUSS.MICROSOFT.COM>
From: Alex Zinin <zinin@PSG.COM>
Subject: Re: OSPFv2 Opaque LSAs in OSPFv3
Comments: To: "Naidu, Venkata" <Venkata.Naidu@MARCONI.COM>
To: OSPF@DISCUSS.MICROSOFT.COM
In-Reply-To: <39469E08BD83D411A3D900204840EC557633DC@vie-msgusr-01.dc.fore.com>
Precedence: list
Content-Transfer-Encoding: 7bit

Venkata,

Monday, October 14, 2002, 7:09:59 AM, Naidu, Venkata wrote:
...
>   That view of looking at IGPs as just "hop-by-hop routing protocols"
>   should go away. Now with the new opened doors in Optical networking,
>   Advanced (diffserv) TE enhancements, VPNs, those good old IGPs became
>   like transport protocols. The applicability of these IGPs for
>   transportation of transparent data will increase in future years.
>   May be, we (IGP guys) should get a big picture of how/why/what TSVWG
>   is doing for new requirement in transport protocols (such as SCTP
>   etc etc). How can we do the same stuff with minimal changes in IGPs
>   for the benefit of our "IGPs applications" ?

IGPs (and EGPs for that matter) are _routing_ protocols, they are
_not_ a universal transport system.

>   Finally, the % of code in IGPs used for SPF and hop-by-hop routing
>   table calculations is decreased. That % is grabbed by other
>   purposes. IGPs are no more self-driven, rather dictated by some new
>   applications requirements.

>   If we fail to tune our IGPs for all such applications then, new
>   protocols will emerge (for example, LDP). Those new XXX protocols
>   will look exactly like "stripped OSPF" - in 1000ft view.

And this is the right thing to do. There are reasons we don't
distribute DNS records through routing. Unfortunately, we keep
forgetting these reasons and concentrate on reusing existing packet
parsing code...

Alex