Re: [Ospf-manet] URL for MPR-extension software
Richard Ogier <rich.ogier@earthlink.net> Mon, 11 December 2006 23:19 UTC
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1GtuQu-00086D-7U; Mon, 11 Dec 2006 18:19:40 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1GtuQs-000865-GG for ospf-manet@ietf.org; Mon, 11 Dec 2006 18:19:38 -0500
Received: from pop-tawny.atl.sa.earthlink.net ([207.69.195.67]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1GtuQq-0006em-6i for ospf-manet@ietf.org; Mon, 11 Dec 2006 18:19:38 -0500
Received: from dialup-4.243.128.197.dial1.sanfrancisco1.level3.net ([4.243.128.197] helo=earthlink.net) by pop-tawny.atl.sa.earthlink.net with esmtp (Exim 3.36 #1) id 1GtuQn-0004RT-00; Mon, 11 Dec 2006 18:19:34 -0500
Message-ID: <457DE785.3050008@earthlink.net>
Date: Mon, 11 Dec 2006 15:19:33 -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: Emmanuel Baccelli <Emmanuel.Baccelli@inria.fr>
Subject: Re: [Ospf-manet] URL for MPR-extension software
References: <77F357662F8BFA4CA7074B0410171B6D01A2F921@XCH-NW-5V1.nw.nos.boeing.com> <456CA642.60908@cisco.com> <456D58DD.4050700@inria.fr>
Content-Type: text/plain; charset="us-ascii"; format="flowed"
Content-Transfer-Encoding: 7bit
X-Spam-Score: 0.1 (/)
X-Scan-Signature: 41c17b4b16d1eedaa8395c26e9a251c4
Cc: ospf-manet@ietf.org
X-BeenThere: ospf-manet@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Discussions of OSPFv3 extensions supporting MANET <ospf-manet.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ospf-manet>, <mailto:ospf-manet-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www1.ietf.org/pipermail/ospf-manet>
List-Post: <mailto:ospf-manet@ietf.org>
List-Help: <mailto:ospf-manet-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ospf-manet>, <mailto:ospf-manet-request@ietf.org?subject=subscribe>
Errors-To: ospf-manet-bounces@ietf.org
Emmanuel Baccelli wrote: > Hi Acee, > here is a link to the source code http://ndquan.free.fr/gtnets.tar.bz2 > I must have missed Tom's post in the usual after-IETF email avalanche, > sorry about that ;) > Emmanuel Emmanuel, I looked at your code. It looks like all you did was modify Cisco's Overlapping Relay (OR) code to generate LSAs that include only MPRs and MPR selectors. So, your GTNetS implementation is essentially just a modification or extension of Cisco's OR solution. In particular, you have not implemented adjacency reduction based on MPRs, which is needed in order to compare your solution to the MDR and OR/SP solutions with adjacency reduction. As Boeing has shown, both adjacency reduction and LSA reduction are needed to achieve scalability to 100 or more nodes. Recall the 100-node example that would have 2384 adjacencies without adjacency reduction: http://www3.ietf.org/proceedings/05mar/slides/ospf-5/sld17.htm When do you plan to release code that implements adjacency reduction based on MPRs, as described in your draft? Since your GTNetS implementation is simply an extension of Cisco's OR implementation, this makes me think that a separate draft is not needed, i.e., that Cisco's OR draft and INRIA's draft can be combined into a single draft. Can you give any reason why this is not possible? In any case, INRIA still needs to provide GTNetS code that implements their solution (including adjacency reduction) so that it can be compared to the other proposals. Without such a comparison, it is possible (and I think likely) that INRIA's solution will generate more than 10 times as much overhead as MDR in a dense 100-node network, possibly consuming all the network bandwidth. The burden of proof is on INRIA. Unless they can provide evidence that their solution can support networks that are roughly as large as those supportable by MDR, then I don't think there is justification for accepting their draft as an experimental WG document. I think we should set a deadline to share current GTNetS code before the next IETF meeting. I plan to release updated GTnetS for MDR in mid February. This will be able to support more than 100 nodes, using min-cost LSAs. I hope that INRIA will also release code that includes adjacency reduction. Richard P.S. Regarding terminology. The term "topology reduction", similar to "topology control", means that the actual network topology is limited, i.e., the set of bidirectional neighbors, or perhaps the set of adjacent neighbors. But if you are only reducing the set of neighbors that are advertised in LSAs, you are not reducing the topology, but are reducing the *advertised* topology. Therefore, I prefer to call this LSA reduction. Put another way, "topology reduction" is ambiguous because it can refer to the topology defined by bidirectional links, or by adjacencies, or by advertised links. > _______________________________________________ Ospf-manet mailing list Ospf-manet@ietf.org https://www1.ietf.org/mailman/listinfo/ospf-manet
- Re: [Ospf-manet] URL for MPR-extension software Emmanuel Baccelli
- [Ospf-manet] URL for MPR-extension software Henderson, Thomas R
- Re: [Ospf-manet] URL for MPR-extension software Acee Lindem
- Re: [Ospf-manet] URL for MPR-extension software Emmanuel Baccelli
- Re: [Ospf-manet] URL for MPR-extension software Richard Ogier
- Re: [Ospf-manet] URL for MPR-extension software Emmanuel Baccelli
- RE: [Ospf-manet] URL for MPR-extension software Henderson, Thomas R
- RE: [Ospf-manet] URL for MPR-extension software Emmanuel Baccelli
- Re: [Ospf-manet] URL for MPR-extension software Richard Ogier
- RE: [Ospf-manet] URL for MPR-extension software Emmanuel Baccelli
- RE: [Ospf-manet] URL for MPR-extension software Henderson, Thomas R
- Re: [Ospf-manet] URL for MPR-extension software Richard Ogier
- Re: [Ospf-manet] URL for MPR-extension software Richard Ogier