Re: OSPFv2 Opaque LSAs in OSPFv3

Alex Zinin <zinin@PSG.COM> Tue, 08 October 2002 01:12 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 VAA12356 for <ospf-archive@LISTS.IETF.ORG>; Mon, 7 Oct 2002 21:12:41 -0400 (EDT)
Received: from walnut (209.119.0.61) by cherry.ease.lsoft.com (LSMTP for Digital Unix v1.1b) with SMTP id <12.0075D334@cherry.ease.lsoft.com>; Mon, 7 Oct 2002 21:14:43 -0400
Received: from DISCUSS.MICROSOFT.COM by DISCUSS.MICROSOFT.COM (LISTSERV-TCP/IP release 1.8e) with spool id 257921 for OSPF@DISCUSS.MICROSOFT.COM; Mon, 7 Oct 2002 21:14:43 -0400
Received: from 147.28.0.62 by WALNUT.EASE.LSOFT.COM (SMTPL release 1.0f) with TCP; Mon, 7 Oct 2002 21:14:43 -0400
Received: from psg.com ([147.28.0.62] helo=127.0.0.1) by psg.com with esmtp (Exim 3.36 #1) id 17yixO-0003PT-00; Mon, 07 Oct 2002 18:14:42 -0700
X-Mailer: The Bat! (v1.51) Personal
X-Priority: 3 (Normal)
References: <200210080018.g980I3Z97797@kummer.juniper.net>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Message-ID: <198381275605.20021007181234@psg.com>
Date: Mon, 07 Oct 2002 18:12:34 -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: <200210080018.g980I3Z97797@kummer.juniper.net>
Precedence: list
Content-Transfer-Encoding: 7bit

Kireeti,

  Hard to talk without seeing the draft, but what problem
  is it trying to address? I mean, we already have a more
  generic "opaque"-like mechanism in OSPFv3, why is it not
  enough?

--
Alex

Monday, October 07, 2002, 5:18:03 PM, Kireeti Kompella wrote:
> Hi All,

> I've just posted draft-kompella-ospf-opaquev2-00.txt that takes
> six pages to say "if you see an OSPF v3 LSA with Function Code 10,
> treat it as you would an OSPF v2 Opaque LSA".

> Comments actively solicited, at least until the negative ones roll in :-)
> The main goal is code reuse between v2 and v3; if that isn't achieved,
> I'd be interested in knowing why, and how it might be fixed.

> Kireeti.
> -------