Re: OSPFv2 Opaque LSAs in OSPFv3

"Manral, Vishwas" <VishwasM@NETPLANE.COM> Thu, 10 October 2002 07:31 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 DAA24680 for <ospf-archive@LISTS.IETF.ORG>; Thu, 10 Oct 2002 03:31:08 -0400 (EDT)
Received: from walnut (209.119.0.61) by cherry.ease.lsoft.com (LSMTP for Digital Unix v1.1b) with SMTP id <4.007643BF@cherry.ease.lsoft.com>; Thu, 10 Oct 2002 3:33:13 -0400
Received: from DISCUSS.MICROSOFT.COM by DISCUSS.MICROSOFT.COM (LISTSERV-TCP/IP release 1.8e) with spool id 275237 for OSPF@DISCUSS.MICROSOFT.COM; Thu, 10 Oct 2002 03:33:13 -0400
Received: from 12.27.183.253 by WALNUT.EASE.LSOFT.COM (SMTPL release 1.0f) with TCP; Thu, 10 Oct 2002 03:33:13 -0400
Received: by XOVER.dedham.mindspeed.com with Internet Mail Service (5.5.2653.19) id <4B0H3PB5>; Thu, 10 Oct 2002 03:33:12 -0400
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2653.19)
Content-Type: text/plain; charset="iso-8859-1"
Message-ID: <E7E13AAF2F3ED41197C100508BD6A3287917C9@india_exch.hyderabad.mindspeed.com>
Date: Thu, 10 Oct 2002 03:35:31 -0400
Reply-To: Mailing List <OSPF@DISCUSS.MICROSOFT.COM>
Sender: Mailing List <OSPF@DISCUSS.MICROSOFT.COM>
From: "Manral, Vishwas" <VishwasM@NETPLANE.COM>
Subject: Re: OSPFv2 Opaque LSAs in OSPFv3
To: OSPF@DISCUSS.MICROSOFT.COM
Precedence: list

Hi Kireeti,

>> To summarize the discussion I guess Kireeti's approach helps in reducing
the
>> workload for the working group and getting the specs out
faster(especially
>> TE). I do not think "mapping" can cause problems as long as in each draft
>> using opaque LSA's we give information for both v2 and v3.

>You'll make yourself pretty unpopular with the AD if you keep that up :-)
I guess I m just voicing my opinion and the AD's understand that.;-)

>> a) How would we want to go ahead with docs like "Graceful Restart" which
are
>> still in draft state and haven't gone LC etc? We could as well have v3
>> additions in the existing drafts.

> Consider for example a network with an IPv4 control plane and IPv6
> data plane.  RSVP-TE already has support for signaling in IPv4 an ERO
> with IPv6 addresses; all it needs is a TE database with IPv6.  So
> making the new TLVs v3-only is unnecessary and unhelpful.  This can
> of course be taken care of with careful wording in the v3 TE draft.
Ok will do that.

> Since we're already on the path of maximal work, why don't you and
> Kunihiro get together and bash out one TE draft instead of two?
I am ok with merging the two drafts to prevent any duplication of work.
Kunihiro?

Thanks,
Vishwas