Re: Address Family Support in OSPFv3

Sina Mirtorabi <sina@CISCO.COM> Mon, 16 June 2003 17:59 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 NAA22921 for <ospf-archive@LISTS.IETF.ORG>; Mon, 16 Jun 2003 13:59:23 -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 <8.00A1996E@cherry.ease.lsoft.com>; Mon, 16 Jun 2003 13:59:22 -0400
Received: from PEACH.EASE.LSOFT.COM by PEACH.EASE.LSOFT.COM (LISTSERV-TCP/IP release 1.8e) with spool id 45787645 for OSPF@PEACH.EASE.LSOFT.COM; Mon, 16 Jun 2003 13:59:20 -0400
Received: from 171.68.227.73 by WALNUT.EASE.LSOFT.COM (SMTPL release 1.0i) with TCP; Mon, 16 Jun 2003 13:59:20 -0400
Received: from smirtoraw2k03 (dhcp-171-69-101-56.cisco.com [171.69.101.56]) by fire.cisco.com (8.11.6+Sun/8.8.8) with ESMTP id h5GHxK023121 for <OSPF@PEACH.EASE.LSOFT.COM>; Mon, 16 Jun 2003 10:59:20 -0700 (PDT)
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
X-Priority: 3 (Normal)
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook, Build 10.0.4024
Importance: Normal
X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4910.0300
Message-ID: <001001c33431$02ac8b50$386545ab@amer.cisco.com>
Date: Mon, 16 Jun 2003 10:59:19 -0700
Reply-To: Mailing List <OSPF@PEACH.EASE.LSOFT.COM>
Sender: Mailing List <OSPF@PEACH.EASE.LSOFT.COM>
From: Sina Mirtorabi <sina@CISCO.COM>
Subject: Re: Address Family Support in OSPFv3
To: OSPF@PEACH.EASE.LSOFT.COM
In-Reply-To: <3EEAF9C9.8090601@redback.com>
Precedence: list
Content-Transfer-Encoding: 7bit

Acee, all


Let me summarize what are the disadvantages of using Instance-ID to run
multiple AF


running multiple instance will

a) require to maintain more adjacencies, in fact to add N AF you may
have to add N adjacencies. This will increase sending and processing of
Hello packet by N for each node

b) require to maintain more LSDB, in fact type 1 & 2 LSA ( which are Not
AF specific) are used again in each instance for each overlapping AF
topology

c) increase the flooding and processing of OSPF packets, this result
from an increase in adjacency and regeneration of type 1&2 LSA within
each instance

D) need a mapping of instance-ID to AF which is user dependent and can
be prone to misconfiguration and increase troubleshooting.

Further other routing protocols ( ISIS, BGP, EIGRP) have adopted AF,
although OSPFv2 -> OSPFv3 transition went with SIN ( ship in the night)
because of inability of v2 to add AF, OSPFv3 separated topology
information and AF specific information and move toward AF integration.
I am not sure we want to fall back to SIN by using instance_ID

Thanks
Sina