Re: Clarification in size of Rtr and network LSA

Acee Lindem <acee@REDBACK.COM> Fri, 13 June 2003 18:24 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 OAA16784 for <ospf-archive@LISTS.IETF.ORG>; Fri, 13 Jun 2003 14:24:44 -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 <20.00A135AB@cherry.ease.lsoft.com>; Fri, 13 Jun 2003 14:24:44 -0400
Received: from PEACH.EASE.LSOFT.COM by PEACH.EASE.LSOFT.COM (LISTSERV-TCP/IP release 1.8e) with spool id 45555616 for OSPF@PEACH.EASE.LSOFT.COM; Fri, 13 Jun 2003 14:24:42 -0400
Received: from 155.53.12.9 by WALNUT.EASE.LSOFT.COM (SMTPL release 1.0i) with TCP; Fri, 13 Jun 2003 14:24:42 -0400
Received: from redback.com (login002.redback.com [155.53.12.54]) by prattle.redback.com (Postfix) with ESMTP id 2EC328EAE01 for <OSPF@PEACH.EASE.LSOFT.COM>; Fri, 13 Jun 2003 11:24:41 -0700 (PDT)
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.0.2) Gecko/20030208 Netscape/7.02
X-Accept-Language: en-us, en
MIME-Version: 1.0
References: <20030613181304.D8385299A8@xmxpita.excite.com>
Content-Type: text/plain; charset="us-ascii"; format="flowed"
Content-Transfer-Encoding: 7bit
Message-ID: <3EEA16C8.1020306@redback.com>
Date: Fri, 13 Jun 2003 14:24:08 -0400
Reply-To: Mailing List <OSPF@PEACH.EASE.LSOFT.COM>
Sender: Mailing List <OSPF@PEACH.EASE.LSOFT.COM>
From: Acee Lindem <acee@REDBACK.COM>
Subject: Re: Clarification in size of Rtr and network LSA
To: OSPF@PEACH.EASE.LSOFT.COM
Precedence: list
Content-Transfer-Encoding: 7bit

Don Goodspeed wrote:
> Hmmm.  Would a scheme like ISIS has for extended LSPs
> work for the router LSA?  If we could use a range of
> router IDs that are not assigned, then maybe.  Or we
> could use a non-backward compatible method using opaque
> LSAs.  Any ideas?  -don

Don,

Let's not go there ;^). Every implementation should
support IP fragmentation and reassembly up to a certain
limit (if not the full 64K). This should more than exceed
anybody's requirement for the number of interfaces in a
single area. For example, if one supports IP fragmentation
and reassembly up to 16K (not an unreasonable number since
there are some DLCs that support MTUs this big) one can
support around 1350 numbered P2P interfaces or around
2700 numbered or transit interfaces. Does anyone have
a requirement to support more interfaces
in a single area?

Thanks,
Acee

>
> ================================
> Krishna,
>
> I myself don't like fragmentation, if just due to the fact
> that any fragment gets dropped, then the whole packet/frame
> needs to be rexmit'ed.
>
> Additionally, I would expect at least consistency counts for
> each LSA type. This count should be retrieveable before
> you start filling the LSA. With this count you can allocate
> the proper memory size.
>
> Mitchell Erblich
> Sr Software Engineer
> -------------
>
> Krishna Rao wrote:
>
>>Hi,
>>This is w.r.to the size of the Router LSA to be generated. We can not predict the size of the router LSA initially in the process of forming the Router LSA. Usually we allocate (Max MTU size - (OSPF header size + IP header size + MD5 authentication size) --> 1500 - (28 + 20 + 16)= 1436) and start filling the LSA. For Point to point interface we add two links and need 24 bytes for each point to point interface. That results in supporting only 59 interfaces in a single area. Is this an acceptable argument? or Should we design such that OSPF sends a LSA more than MTU size and gets fragmented in IP.
>>What is the scalabilty figure for Number of interfaces in a area for popular routers?
>>
>>Thanks in advance,
>>Regards,
>>Krishna
>
>
> _______________________________________________
> Join Excite! - http://www.excite.com
> The most personalized portal on the Web!
>


--
Acee