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

Acee Lindem <acee@cisco.com> Mon, 07 November 2005 23:54 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 1EZGp7-0005G0-Na; Mon, 07 Nov 2005 18:54:49 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1EZGp5-0005Fo-Cs for ospf-wireless-design@megatron.ietf.org; Mon, 07 Nov 2005 18:54:47 -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 SAA19120 for <ospf-wireless-design@ietf.org>; Mon, 7 Nov 2005 18:54:21 -0500 (EST)
Received: from sj-iport-4.cisco.com ([171.68.10.86]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1EZH4m-0005Tg-1F for ospf-wireless-design@ietf.org; Mon, 07 Nov 2005 19:11:01 -0500
Received: from sj-core-4.cisco.com ([171.68.223.138]) by sj-iport-4.cisco.com with ESMTP; 07 Nov 2005 15:54:37 -0800
Received: from xbh-rtp-211.amer.cisco.com (xbh-rtp-211.cisco.com [64.102.31.102]) by sj-core-4.cisco.com (8.12.10/8.12.6) with ESMTP id jA7NsEZH025277; Mon, 7 Nov 2005 15:54:35 -0800 (PST)
Received: from xfe-rtp-201.amer.cisco.com ([64.102.31.38]) by xbh-rtp-211.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.211); Mon, 7 Nov 2005 18:54:25 -0500
Received: from [10.82.209.222] ([10.82.209.222]) by xfe-rtp-201.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.211); Mon, 7 Nov 2005 18:54:24 -0500
Message-ID: <436FE92E.8020309@cisco.com>
Date: Mon, 07 Nov 2005 18:54:22 -0500
From: Acee Lindem <acee@cisco.com>
User-Agent: Mozilla Thunderbird 1.0.2 (Windows/20050317)
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: Richard Ogier <rich.ogier@earthlink.net>
Subject: Re: [Ospf-wireless-design] OSPF Flooding and Higher Mobility
References: <77F357662F8BFA4CA7074B0410171B6DC9E60E@XCH-NW-5V1.nw.nos.boeing.com> <436EB634.1000200@cisco.com> <436EBC7D.5030407@earthlink.net>
In-Reply-To: <436EBC7D.5030407@earthlink.net>
Content-Type: text/plain; charset="ISO-8859-1"; format="flowed"
Content-Transfer-Encoding: 7bit
X-OriginalArrivalTime: 07 Nov 2005 23:54:25.0153 (UTC) FILETIME=[95052710:01C5E3F6]
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 9ed51c9d1356100bce94f1ae4ec616a9
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

Hi Richard,

See below.

Richard Ogier wrote:

> 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.)
>
All routable neighbor are advertised.


>>
>> 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?  
>
A U bit is defined in the unused 8 bits in the LSA link.

>> Is a different Link State ID
>> used for real adjacenies versus non-adjacencies?
>
Nope.

>
>
Thanks,
Acee

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