RE: [Ospf-wireless-design] Design Team slides for IETF 63
Richard Ogier <rich.ogier@earthlink.net> Wed, 03 August 2005 05:25 UTC
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1E0Bkd-00053B-DM; Wed, 03 Aug 2005 01:25:11 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1E0Bkb-00051S-MW for ospf-wireless-design@megatron.ietf.org; Wed, 03 Aug 2005 01:25:10 -0400
Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id BAA08885 for <ospf-wireless-design@ietf.org>; Wed, 3 Aug 2005 01:25:09 -0400 (EDT)
Received: from rly-ip04.mx.aol.com ([64.12.138.8]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1E0CHC-0003l6-FS for ospf-wireless-design@ietf.org; Wed, 03 Aug 2005 01:58:52 -0400
Received: from smtp-rtc02.proxy.aol.com (smtp-rtc02.proxy.aol.com [152.163.102.81]) by rly-ip04.mx.aol.com (v98.19) with ESMTP id RELAYIN10-b42f0551e1ec; Wed, 03 Aug 2005 01:24:46 -0400
Received: from earthlink.net (ACC2B20A.ipt.aol.com [172.194.178.10]) by smtp-rtc02.proxy.aol.com (8.12.11/8.12.11) with ESMTP id j735OXAX021958; Wed, 3 Aug 2005 01:24:34 -0400
Message-ID: <42F05516.5040403@earthlink.net>
Date: Tue, 02 Aug 2005 22:24:38 -0700
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: phillip.a.spagnolo@boeing.com
Subject: RE: [Ospf-wireless-design] Design Team slides for IETF 63
Content-Type: text/plain; charset="us-ascii"; format="flowed"
Content-Transfer-Encoding: 7bit
X-Scanned-By: MIMEDefang 2.43
X-Apparently-From: ERR_USER_NULL
X-AOL-IP: 152.163.102.81
X-Spam-Score: 0.2 (/)
X-Scan-Signature: 538aad3a3c4f01d8b6a6477ca4248793
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
Phil wrote: > Specifically, I don't see a clear winner on how to do backup/pushback > relaying. The ORs design requires an ack to be received by each > adjacent neighbor for the flooded LSA while the MDRs design requires an > ack or hearing a flood of the LSA to all covered neighbors. The result > is that ORs have more backup floods while MDRs have more retransmissions > due to the loss of the first flooded LSA. If the design team would like > to compare these mechanism, I don't see any reason why the pushback > mechanism is precluded from the MDR approach or the backup mechanism is > precluded from the OR approach. In my previous message, I mentioned a modification of the MDR BackupWait mechanism which requires a (Backup) MDR to receive an ACK from each adjacent neighbor in order to suppress flooding the LSA (out the receiving interface). In the current mechanism, a (Backup) MDR will suppress flooding the LSA as long as all adjacent and dependent neighbors are covered, even if an ACK was not received from an adjacent neighbor. I ran some simulations that show that the modified mechanism usually results in more overhead (which is contrary to the purpose of the modification). I will now explain why this might happen. If an ACK is not received from an adjacent neighbor, then it is possible that the neighbor received (and ACKed) the LSA but the router did not hear the ACK. In this case, flooding the LSA as a multicast only wastes overhead since the neighbor will not ACK a multicast LSA (so the router must then retransmit the LSA as a unicast). Therefore, in this case, overhead is saved by suppressing the flood (and instead retransmitting the LSA as a unicast) even though an ACK was not received. Also, when partial adjacencies are used, there are fewer adjacent neighbors to which an LSA may need to be retransmitted. Therefore, it is not as important to minimize unicast retransmissions when partial adjacencies are used. I am not saying that the mechanism should not be modified - only that there may be reasons to keep it as is. Future simulation comparisons may show that a different mechanism is preferable. Richard _______________________________________________ Ospf-wireless-design mailing list Ospf-wireless-design@lists.ietf.org https://www1.ietf.org/mailman/listinfo/ospf-wireless-design
- [Ospf-wireless-design] Design Team slides for IET… Henderson, Thomas R
- Re: [Ospf-wireless-design] Design Team slides for… Tony Przygienda
- RE: [Ospf-wireless-design] Design Team slides for… Henderson, Thomas R
- RE: [Ospf-wireless-design] Design Team slides for… Joe Macker
- Re: [Ospf-wireless-design] Design Team slides for… Richard Ogier
- Re: [Ospf-wireless-design] Design Team slides for… Acee Lindem
- RE: [Ospf-wireless-design] Design Team slides for… Spagnolo, Phillip A
- Re: [Ospf-wireless-design] Design Team slides for… Richard Ogier
- RE: [Ospf-wireless-design] Design Team slides for… Henderson, Thomas R
- RE: [Ospf-wireless-design] Design Team slides for… Richard Ogier
- Re: [Ospf-wireless-design] Design Team slides for… Richard Ogier
- RE: [Ospf-wireless-design] Design Team slides for… Henderson, Thomas R
- Re: [Ospf-wireless-design] Design Team slides for… Richard Ogier
- Re: [Ospf-wireless-design] Design Team slides for… Richard Ogier
- RE: [Ospf-wireless-design] Design Team slides for… Joe Macker
- [Ospf-wireless-design] Two clarifications about O… Richard Ogier