Re: [Ospf-wireless-design] OSPF Flooding and Higher Mobility

Richard Ogier <rich.ogier@earthlink.net> Mon, 07 November 2005 02:31 UTC

Received: from localhost.cnri.reston.va.us ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1EYwn9-0001wt-0x; Sun, 06 Nov 2005 21:31:27 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1EYwn7-0001wo-NE for ospf-wireless-design@megatron.ietf.org; Sun, 06 Nov 2005 21:31:25 -0500
Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id VAA06193 for <ospf-wireless-design@ietf.org>; Sun, 6 Nov 2005 21:31:01 -0500 (EST)
Received: from pop-altamira.atl.sa.earthlink.net ([207.69.195.62]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1EYx2e-000424-6u for ospf-wireless-design@ietf.org; Sun, 06 Nov 2005 21:47:28 -0500
Received: from dialup-4.246.30.156.dial1.sanjose1.level3.net ([4.246.30.156] helo=earthlink.net) by pop-altamira.atl.sa.earthlink.net with esmtp (Exim 3.36 #10) id 1EYwn4-00079o-00; Sun, 06 Nov 2005 21:31:23 -0500
Message-ID: <436EBC7D.5030407@earthlink.net>
Date: Sun, 06 Nov 2005 18:31:25 -0800
From: Richard Ogier <rich.ogier@earthlink.net>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:0.9.4) Gecko/20011128 Netscape6/6.2.1 (emach0202)
X-Accept-Language: en-us
MIME-Version: 1.0
To: Acee Lindem <acee@cisco.com>
Subject: Re: [Ospf-wireless-design] OSPF Flooding and Higher Mobility
References: <77F357662F8BFA4CA7074B0410171B6DC9E60E@XCH-NW-5V1.nw.nos.boeing.com> <436EB634.1000200@cisco.com>
Content-Type: text/plain; charset="us-ascii"; format="flowed"
Content-Transfer-Encoding: 7bit
X-Spam-Score: 0.1 (/)
X-Scan-Signature: 9182cfff02fae4f1b6e9349e01d62f32
Content-Transfer-Encoding: 7bit
Cc: ospf-wireless-design@ietf.org
X-BeenThere: ospf-wireless-design@lists.ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: OSPF Wireless Design Team <ospf-wireless-design.lists.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ospf-wireless-design>, <mailto:ospf-wireless-design-request@lists.ietf.org?subject=unsubscribe>
List-Archive: <https://www1.ietf.org/mailman/private/ospf-wireless-design>
List-Post: <mailto:ospf-wireless-design@lists.ietf.org>
List-Help: <mailto:ospf-wireless-design-request@lists.ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ospf-wireless-design>, <mailto:ospf-wireless-design-request@lists.ietf.org?subject=subscribe>
Sender: ospf-wireless-design-bounces@lists.ietf.org
Errors-To: ospf-wireless-design-bounces@lists.ietf.org

Acee,

Can you answer my questions below?

Thanks,
Richard

> In the simulations for Smart Peering, what neighbors were included in
> the router-LSAs?  If only adjacent neighbors were included,
> then that could explain the lower overhead obtained for Smart Peering,
> and would also result in highly suboptimal paths
> (much longer than shortest paths).  That is why simulation
> results are not very meaningful unless other measures such
> as average path length and delivery ratio are also presented.
> (The average path length can be obtained from the numbers of UDP
> packets sent/forwarded/received, but I did not see those numbers.)
>
> Also, since Cisco is running SPF twice, once for real adjacencies
> and once for all acceptable links, I would like to know how
> a router knows which non-local links are real adjacencies.
> Does the LSA somehow indicate this?  Is a different Link State ID
> used for real adjacenies versus non-adjacencies? 




_______________________________________________
Ospf-wireless-design mailing list
Ospf-wireless-design@lists.ietf.org
https://www1.ietf.org/mailman/listinfo/ospf-wireless-design