Re: OSPFv2 Opaque LSAs in OSPFv3

Alex Zinin <zinin@PSG.COM> Sat, 12 October 2002 01:10 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 VAA08496 for <ospf-archive@LISTS.IETF.ORG>; Fri, 11 Oct 2002 21:10:59 -0400 (EDT)
Received: from walnut (209.119.0.61) by cherry.ease.lsoft.com (LSMTP for Digital Unix v1.1b) with SMTP id <8.00768CC9@cherry.ease.lsoft.com>; Fri, 11 Oct 2002 21:13:02 -0400
Received: from DISCUSS.MICROSOFT.COM by DISCUSS.MICROSOFT.COM (LISTSERV-TCP/IP release 1.8e) with spool id 283680 for OSPF@DISCUSS.MICROSOFT.COM; Fri, 11 Oct 2002 21:13:02 -0400
Received: from 147.28.0.62 by WALNUT.EASE.LSOFT.COM (SMTPL release 1.0f) with TCP; Fri, 11 Oct 2002 21:13:02 -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 180Apx-000BOl-00; Fri, 11 Oct 2002 18:13:01 -0700
X-Mailer: The Bat! (v1.51) Personal
X-Priority: 3 (Normal)
References: <200210101854.g9AIsNu09615@kummer.juniper.net>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Message-ID: <4417570605.20021011181015@psg.com>
Date: Fri, 11 Oct 2002 18:10:15 -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: Kireeti Kompella <kireeti@JUNIPER.NET>
To: OSPF@DISCUSS.MICROSOFT.COM
In-Reply-To: <200210101854.g9AIsNu09615@kummer.juniper.net>
Precedence: list
Content-Transfer-Encoding: 7bit

Thursday, October 10, 2002, 11:54:23 AM, Kireeti Kompella wrote:
> Thanks for your support, Venkata!

> One thing I would like to reiterate: there are a *small* number of
> currently defined Opaque LSAs -- TE, Grace LSA, and perhaps one more.
> If we analyse the applicability of those LSAs to OSPF v3, and mandate
> that any future definition of an OSPFv2 Opaque LSA MUST have a similar
> analysis, that seems to me to address the "backdoor" problem.

> The "backdoor" issue is an excellent example of a *theoretical*
> problem that has little *practical* relevance, given the above mandate.

It's an excellent example of the type of hidden problems that ADs have
to think about and that to them has a very practical relevance.

> As a consequence, we have at least two independent efforts to migrate
> just the TE document to v3, when in fact it should be really simple.
> Then we do it again for Grace LSAs.  And possibly again in the future.

OSPFv3- and IPv6-related issues should be considered and specified for
each feature independently, because OSPFv? are not just two versions
of a transport mechanism, they are two different routing protocols
providing connectivity for different types of environment.

> And then we hear that the IETF is overloaded, and the IESG overburdened.
> Oh, well ...

Thanks for thinking about the IESG. I can assure you that it will be
much less controversial (and hence faster) for the IESG to deal with
drafts explicitly specifying IPv6/OSPFv3 considerations for specific
features, than it will be to waste time arguing about a draft that
collectively migrates all present and future OSPFv2-based features and
"applications" to the IPv6/OSPFv3 environment.

Alex