Re: Clarification in size of Rtr and network LSA

Erblichs <erblichs@EARTHLINK.NET> Fri, 13 June 2003 16:52 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 MAA11776 for <ospf-archive@LISTS.IETF.ORG>; Fri, 13 Jun 2003 12:52:39 -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 <4.00A133E4@cherry.ease.lsoft.com>; Fri, 13 Jun 2003 12:52:39 -0400
Received: from PEACH.EASE.LSOFT.COM by PEACH.EASE.LSOFT.COM (LISTSERV-TCP/IP release 1.8e) with spool id 45546362 for OSPF@PEACH.EASE.LSOFT.COM; Fri, 13 Jun 2003 12:52:38 -0400
Received: from 207.217.120.46 by WALNUT.EASE.LSOFT.COM (SMTPL release 1.0i) with TCP; Fri, 13 Jun 2003 12:52:38 -0400
Received: from user-2ivfj0k.dialup.mindspring.com ([165.247.204.20] helo=earthlink.net) by grebe.mail.pas.earthlink.net with esmtp (Exim 3.33 #1) id 19Qrn2-0007jP-00 for OSPF@PEACH.EASE.LSOFT.COM; Fri, 13 Jun 2003 09:52:37 -0700
X-Sender: "Erblichs" <@smtp.earthlink.net> (Unverified)
X-Mailer: Mozilla 4.72 [en]C-gatewaynet (Win98; I)
X-Accept-Language: en
MIME-Version: 1.0
References: <20030613102350.21479.qmail@webmail16.rediffmail.com>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Message-ID: <3EEA01C1.1DAE8F69@earthlink.net>
Date: Fri, 13 Jun 2003 09:54:25 -0700
Reply-To: Mailing List <OSPF@PEACH.EASE.LSOFT.COM>
Sender: Mailing List <OSPF@PEACH.EASE.LSOFT.COM>
From: Erblichs <erblichs@EARTHLINK.NET>
Subject: Re: Clarification in size of Rtr and network LSA
To: OSPF@PEACH.EASE.LSOFT.COM
Precedence: list
Content-Transfer-Encoding: 7bit

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
>
>   ------------------------------------------------------------------------
> [Image]