Re: Address Family Support in OSPFv3

Russ White <ruwhite@CISCO.COM> Wed, 09 July 2003 23: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 TAA29604 for <ospf-archive@LISTS.IETF.ORG>; Wed, 9 Jul 2003 19:55:46 -0400 (EDT)
Received: from PEAR.EASE.LSOFT.COM (209.119.0.19) by cherry.ease.lsoft.com (LSMTP for Digital Unix v1.1b) with SMTP id <15.00A5CAE7@cherry.ease.lsoft.com>; Wed, 9 Jul 2003 19:55:45 -0400
Received: from PEACH.EASE.LSOFT.COM by PEACH.EASE.LSOFT.COM (LISTSERV-TCP/IP release 1.8e) with spool id 47964747 for OSPF@PEACH.EASE.LSOFT.COM; Wed, 9 Jul 2003 19:55:44 -0400
Received: from 64.102.124.12 by WALNUT.EASE.LSOFT.COM (SMTPL release 1.0i) with TCP; Wed, 9 Jul 2003 19:55:44 -0400
Received: from cisco.com (uzura.cisco.com [64.102.17.77]) by rtp-core-1.cisco.com (8.12.9/8.12.6) with ESMTP id h69Ntffq015191 for <OSPF@PEACH.EASE.LSOFT.COM>; Wed, 9 Jul 2003 19:55:42 -0400 (EDT)
Received: from [10.10.2.239] (rtp-vpn2-471.cisco.com [10.82.241.215]) by cisco.com (8.8.8/2.6/Cisco List Logging/8.8.8) with ESMTP id TAA19073 for <OSPF@PEACH.EASE.LSOFT.COM>; Wed, 9 Jul 2003 19:55:41 -0400 (EDT)
X-X-Sender: ruwhite@rwlaptop.local
References: <000401c34650$4bfce9e0$386545ab@amer.cisco.com> <3F0C756D.6000308@redback.com>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset="US-ASCII"
Message-ID: <Pine.OSX.4.51.0307091954210.28357@rwlaptop.local>
Date: Wed, 09 Jul 2003 19:55:50 -0400
Reply-To: Mailing List <OSPF@PEACH.EASE.LSOFT.COM>
Sender: Mailing List <OSPF@PEACH.EASE.LSOFT.COM>
From: Russ White <ruwhite@CISCO.COM>
Subject: Re: Address Family Support in OSPFv3
To: OSPF@PEACH.EASE.LSOFT.COM
In-Reply-To: <3F0C756D.6000308@redback.com>
Precedence: list

> For example, to support the OSPFv3 IPv6 multicast topology with the
> multi-AF approach one must implement the two drafts you've posted plus
> deal with all the issues related to the AF layer in configuration and
> management (i.e., show commands, etc). To do it with multiple instances,
> all you have to do is configure the address family and default OSPFv3
> interface ID at the instance level. I haven't thought about this at great
> depth but on the surface I can't see why it wouldn't work. There will be
> no protocol changes and I'll submit to you that the implementation cost
> is less.
>
> At this point, I'm not saying that one approach is obviously better or
> trying to precisely quantify the relative efficiencies when multiple AFs
> are used. All I'm saying is that you can't completely discount the
> associated costs.

But, if you are carrying something which doesn't necessarily fit into the
ipv6 address format, then you need the new instance, and the new tlv's
anyway, correct? So, you've now gained the additional complexity on all
sides, and gained nothing, it seems to me.

:-)

Russ

__________________________________
riw@cisco.com CCIE <>< Grace Alone