From ospf-manet-bounces@ietf.org Mon Apr 03 04:42:35 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1FQKdv-0002Y6-Ox; Mon, 03 Apr 2006 04:42:35 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1FQKdu-0002XD-Ha
	for ospf-manet@ietf.org; Mon, 03 Apr 2006 04:42:34 -0400
Received: from nez-perce.inria.fr ([192.93.2.78])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1FQKdt-0006fP-5d
	for ospf-manet@ietf.org; Mon, 03 Apr 2006 04:42:34 -0400
Received: from [192.168.112.160] (sphinx.lix.polytechnique.fr [129.104.11.1])
	(authenticated bits=0)
	by nez-perce.inria.fr (8.13.0/8.13.0) with ESMTP id k338gV1w007024
	(version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO);
	Mon, 3 Apr 2006 10:42:32 +0200
Message-ID: <4430DFFF.4010104@inria.fr>
Date: Mon, 03 Apr 2006 10:42:39 +0200
From: Philippe Jacquet <philippe.jacquet@inria.fr>
Organization: inria
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US;
	rv:1.7.1) Gecko/20040707
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: ospf-manet@ietf.org
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
X-j-chkmail-Score: MSGID : 4430DFF7.000 on nez-perce : j-chkmail score : X :
	0/20 1
X-Miltered: at nez-perce with ID 4430DFF7.000 by Joe's j-chkmail
	(http://j-chkmail.ensmp.fr)!
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 08e48e05374109708c00c6208b534009
Cc: Hakim.Badis@lix.polytechnique.fr
Subject: [Ospf-manet] How can we get GTNet software?
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

Sorry, I may have lost the posts which detailled the status and 
directions aboutGTNet software downloads. Can anyone update me on that 
subject?

Thanks in advance,

Best regards,
Philippe

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



From ospf-manet-bounces@ietf.org Mon Apr 03 06:28:06 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1FQMI2-0007aJ-Ot; Mon, 03 Apr 2006 06:28:06 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1FQMI2-0007a1-2I
	for ospf-manet@ietf.org; Mon, 03 Apr 2006 06:28:06 -0400
Received: from rtp-iport-2.cisco.com ([64.102.122.149])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1FQMI0-0003fi-On
	for ospf-manet@ietf.org; Mon, 03 Apr 2006 06:28:06 -0400
Received: from rtp-core-2.cisco.com ([64.102.124.13])
	by rtp-iport-2.cisco.com with ESMTP; 03 Apr 2006 06:28:04 -0400
X-IronPort-AV: i="4.03,157,1141621200"; 
	d="scan'208"; a="85552110:sNHT30875044"
Received: from xbh-rtp-211.amer.cisco.com (xbh-rtp-211.cisco.com
	[64.102.31.102])
	by rtp-core-2.cisco.com (8.12.10/8.12.6) with ESMTP id k33AS4VU003710; 
	Mon, 3 Apr 2006 06:28:04 -0400 (EDT)
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, 3 Apr 2006 06:28:03 -0400
Received: from [10.82.225.3] ([10.82.225.3]) by xfe-rtp-201.amer.cisco.com
	with Microsoft SMTPSVC(6.0.3790.211); Mon, 3 Apr 2006 06:28:03 -0400
Message-ID: <4430F8B2.2020103@cisco.com>
Date: Mon, 03 Apr 2006 06:28:02 -0400
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: Philippe Jacquet <philippe.jacquet@inria.fr>
Subject: Re: [Ospf-manet] How can we get GTNet software?
References: <4430DFFF.4010104@inria.fr>
In-Reply-To: <4430DFFF.4010104@inria.fr>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-OriginalArrivalTime: 03 Apr 2006 10:28:03.0271 (UTC)
	FILETIME=[49E51570:01C65709]
X-Spam-Score: 0.0 (/)
X-Scan-Signature: ffa9dfbbe7cc58b3fa6b8ae3e57b0aa3
Cc: Hakim.Badis@lix.polytechnique.fr, 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

Philippe Jacquet wrote:

> Sorry, I may have lost the posts which detailled the status and 
> directions aboutGTNet software downloads. Can anyone update me on that 
> subject?

Hi Philippe,

Here is the link:

<http://hipserver.mct.phantomworks.org/ietf/ospf/>

Thanks,
Acee 

>
> Thanks in advance,
>
> Best regards,
> Philippe
>
> _______________________________________________
> Ospf-manet mailing list
> Ospf-manet@ietf.org
> https://www1.ietf.org/mailman/listinfo/ospf-manet
>

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



From ospf-manet-bounces@ietf.org Mon Apr 03 09:49:45 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1FQPRB-0000lg-Hg; Mon, 03 Apr 2006 09:49:45 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1FQPR9-0000lb-R3
	for ospf-manet@ietf.org; Mon, 03 Apr 2006 09:49:43 -0400
Received: from blv-smtpout-01.boeing.com ([130.76.32.69])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1FQPR8-0003b3-FR
	for ospf-manet@ietf.org; Mon, 03 Apr 2006 09:49:43 -0400
Received: from stl-av-01.boeing.com ([192.76.190.6])
	by blv-smtpout-01.boeing.com (8.9.2.MG.10092003/8.8.5-M2) with ESMTP id
	GAA09739; Mon, 3 Apr 2006 06:49:28 -0700 (PDT)
Received: from XCH-NWBH-11.nw.nos.boeing.com (localhost [127.0.0.1])
	by stl-av-01.boeing.com (8.11.3/8.11.3/MBS-AV-LDAP-01) with ESMTP id
	k33DnSN17148; Mon, 3 Apr 2006 08:49:28 -0500 (CDT)
Received: from XCH-NW-5V1.nw.nos.boeing.com ([130.247.55.44]) by
	XCH-NWBH-11.nw.nos.boeing.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Mon, 3 Apr 2006 06:49:27 -0700
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Subject: RE: [Ospf-manet] How can we get GTNet software?
Date: Mon, 3 Apr 2006 06:49:27 -0700
Message-ID: <77F357662F8BFA4CA7074B0410171B6D01A2EF66@XCH-NW-5V1.nw.nos.boeing.com>
In-Reply-To: <4430DFFF.4010104@inria.fr>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [Ospf-manet] How can we get GTNet software?
Thread-Index: AcZW+pDyvd8jwTglTYKQduF23js/fQAKrbEQ
From: "Henderson, Thomas R" <thomas.r.henderson@boeing.com>
To: "Philippe Jacquet" <philippe.jacquet@inria.fr>, <ospf-manet@ietf.org>
X-OriginalArrivalTime: 03 Apr 2006 13:49:27.0562 (UTC)
	FILETIME=[6CB18EA0:01C65725]
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 2409bba43e9c8d580670fda8b695204a
Cc: Hakim.Badis@lix.polytechnique.fr
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

Philippe, if you are interested, we can work with you to incorporate a
model of your draft in the quagga code.

Tom=20

> -----Original Message-----
> From: Philippe Jacquet [mailto:philippe.jacquet@inria.fr]=20
> Sent: Monday, April 03, 2006 1:43 AM
> To: ospf-manet@ietf.org
> Cc: Hakim.Badis@lix.polytechnique.fr
> Subject: [Ospf-manet] How can we get GTNet software?
>=20
> Sorry, I may have lost the posts which detailled the status and=20
> directions aboutGTNet software downloads. Can anyone update=20
> me on that=20
> subject?
>=20
> Thanks in advance,
>=20
> Best regards,
> Philippe
>=20
> _______________________________________________
> Ospf-manet mailing list
> Ospf-manet@ietf.org
> https://www1.ietf.org/mailman/listinfo/ospf-manet
>=20

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



From ospf-manet-bounces@ietf.org Wed Apr 05 16:57:19 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1FRF43-00022H-Ac; Wed, 05 Apr 2006 16:57:19 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1FRF42-000226-2n
	for ospf-manet@ietf.org; Wed, 05 Apr 2006 16:57:18 -0400
Received: from concorde.inria.fr ([192.93.2.39])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1FRF3z-0004ay-Mb
	for ospf-manet@ietf.org; Wed, 05 Apr 2006 16:57:18 -0400
Received: from [192.168.0.4] (AVelizy-152-1-44-164.w82-120.abo.wanadoo.fr
	[82.120.247.164]) (authenticated bits=0)
	by concorde.inria.fr (8.13.0/8.13.0) with ESMTP id k35KvCTt013586
	(version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO);
	Wed, 5 Apr 2006 22:57:13 +0200
Message-ID: <44342F32.4080309@inria.fr>
Date: Wed, 05 Apr 2006 22:57:22 +0200
From: Philippe Jacquet <philippe.jacquet@inria.fr>
Organization: inria
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US;
	rv:1.7.1) Gecko/20040707
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: Acee Lindem <acee@cisco.com>
Subject: Re: [Ospf-manet] How can we get GTNet software?
References: <4430DFFF.4010104@inria.fr> <4430F8B2.2020103@cisco.com>
In-Reply-To: <4430F8B2.2020103@cisco.com>
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
X-j-chkmail-Score: MSGID : 44342F28.000 on concorde : j-chkmail score : X :
	0/20 1
X-Miltered: at concorde with ID 44342F28.000 by Joe's j-chkmail
	(http://j-chkmail.ensmp.fr)!
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 9ed51c9d1356100bce94f1ae4ec616a9
Cc: Hakim.Badis@lix.polytechnique.fr, 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

Thanks, Acee, thanks Tom,

Sorry for the delay. I just have realized why these emails got lost, I 
have a zealous anti-spammer that systematically dropped the emails.

Yes it would be great to synchronize our efforts on GTNet. Let's see how 
to proceed.

Best regards,
Philippe

Acee Lindem wrote:

> Philippe Jacquet wrote:
>
>> Sorry, I may have lost the posts which detailled the status and 
>> directions aboutGTNet software downloads. Can anyone update me on 
>> that subject?
>
>
> Hi Philippe,
>
> Here is the link:
>
> <http://hipserver.mct.phantomworks.org/ietf/ospf/>
>
> Thanks,
> Acee
>
>>
>> Thanks in advance,
>>
>> Best regards,
>> Philippe
>>
>> _______________________________________________
>> Ospf-manet mailing list
>> Ospf-manet@ietf.org
>> https://www1.ietf.org/mailman/listinfo/ospf-manet
>>
>
>


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



From ospf-manet-bounces@ietf.org Tue Apr 11 13:38:26 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1FTMos-0001JP-PJ; Tue, 11 Apr 2006 13:38:26 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1FTMor-0001JK-L6
	for ospf-manet@ietf.org; Tue, 11 Apr 2006 13:38:25 -0400
Received: from pop-siberian.atl.sa.earthlink.net ([207.69.195.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1FTMop-0002iG-Da
	for ospf-manet@ietf.org; Tue, 11 Apr 2006 13:38:25 -0400
Received: from dialup-4.243.128.37.dial1.sanfrancisco1.level3.net
	([4.243.128.37] helo=earthlink.net)
	by pop-siberian.atl.sa.earthlink.net with esmtp (Exim 3.36 #10)
	id 1FTMoo-0003ko-00
	for ospf-manet@ietf.org; Tue, 11 Apr 2006 13:38:22 -0400
Message-ID: <443BE984.9030803@earthlink.net>
Date: Tue, 11 Apr 2006 10:38:12 -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: ospf-manet@ietf.org
Subject: Re: [Ospf-manet] How can we get GTNet software?
References: <4430DFFF.4010104@inria.fr> <4430F8B2.2020103@cisco.com>
	<44342F32.4080309@inria.fr>
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
X-Spam-Score: 0.1 (/)
X-Scan-Signature: 8b30eb7682a596edff707698f4a80f7d
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

> Thanks, Acee, thanks Tom,
>
> Sorry for the delay. I just have realized why these emails got lost, I 
> have a zealous anti-spammer that systematically dropped the emails.
>
> Yes it would be great to synchronize our efforts on GTNet. Let's see 
> how to proceed.
>
> Best regards,
> Philippe 



I am glad that INRIA is finally joining the simulation evaluation
effort.  I am not opposed to using MPRs (in addition to a CDS),
but we need to evaluate them to see how they perform.

At the IETF meeting, Bill Fenner encouraged us to work together, so
I guess there was a perception at the meeting that we have not been
working together.  I think we have been working together, since both
Cisco and I have been working with Boeing to compare the two proposals
that have been around for the last year.

INRIA submitted their proposal only just before the last meeting, about
a year after the other two proposals, and it is still not completely
defined.  I am not sure why INRIA waited so long, but it is difficult
to evaluate their proposal when it is the only one that has not yet
been implemented in GTNetS (or even completely described).
If INRIA had submitted their (fully defined) proposal a year ago, then
we might have been able to fully evaluate it by now.

But if the consensus is that we should evaluate INRIA's proposal
(despite its late entry) then we should go ahead and do that, and also
evaluate methods that use a combination of MPRs and a CDS (MDRs),
before we make any decisions.  In this way, we should be able to
work together to decide on the best solution.

Richard


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



From ospf-manet-bounces@ietf.org Fri Apr 21 11:14:58 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1FWxLW-00021E-R2; Fri, 21 Apr 2006 11:14:58 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1FWxLV-000219-Gk
	for ospf-manet@ietf.org; Fri, 21 Apr 2006 11:14:57 -0400
Received: from concorde.inria.fr ([192.93.2.39])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1FWxLU-0005pM-Vg
	for ospf-manet@ietf.org; Fri, 21 Apr 2006 11:14:57 -0400
Received: from [128.93.17.113] (zephyrin4.inria.fr [128.93.17.113])
	by concorde.inria.fr (8.13.0/8.13.0) with ESMTP id k3LFEsZr014509
	(version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO);
	Fri, 21 Apr 2006 17:14:54 +0200
Message-ID: <4448F6FA.7020106@inria.fr>
Date: Fri, 21 Apr 2006 17:15:06 +0200
From: Philippe Jacquet <philippe.jacquet@inria.fr>
Organization: inria
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US;
	rv:1.7.1) Gecko/20040707
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: Richard Ogier <rich.ogier@earthlink.net>
Subject: Re: [Ospf-manet] How can we get GTNet software?
References: <4430DFFF.4010104@inria.fr>
	<4430F8B2.2020103@cisco.com>	<44342F32.4080309@inria.fr>
	<443BE984.9030803@earthlink.net>
In-Reply-To: <443BE984.9030803@earthlink.net>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-Miltered: at concorde with ID 4448F6EE.000 by Joe's j-chkmail
	(http://j-chkmail.ensmp.fr)!
X-Spam-Score: 0.0 (/)
X-Scan-Signature: b280b4db656c3ca28dd62e5e0b03daa8
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

Dear Richard,

I am glad that you consider our contribution as an interesting item. We 
have produced this draft after the design team called for short 
contributions on the subject. We apologize that we publish the draft a 
little late, but we wanted to have something clean and we thank you 
again for having immediately pointed last minute mistakes in the text. 
However most of the items that are describing in our draft were already 
intensively discussed on the mailing list for a long time, and of them 
were already simulated. In particular:

1. Robustness of MPR flooding
2. Topology reduction and synchronization of advertized links.

I recognize that the concept of MDR has interesting feature in providing 
a reduced synchronizing backbone, but one must investigate the effect of 
advertizing non synchronized links in the core OSPF. Maybe we could give 
less synchronization priority degree to other synchronized links. Maybe 
some interesting combinations are possible.

My first rule of the thumb evaluation let me think that advertizing full 
LSA's everytime there is a change may lead to a tremendous overhead, 
comparable to the of cost of synchronizing all links. Or we should 
accept that wireless OSPF would work on slow moving or quasi static 
wireless networks, and not on all kinds of MANETs.

I am looking forward the simulation results.

Best regards,
Philippe


Richard Ogier wrote:

>> Thanks, Acee, thanks Tom,
>>
>> Sorry for the delay. I just have realized why these emails got lost, 
>> I have a zealous anti-spammer that systematically dropped the emails.
>>
>> Yes it would be great to synchronize our efforts on GTNet. Let's see 
>> how to proceed.
>>
>> Best regards,
>> Philippe 
>
>
>
>
> I am glad that INRIA is finally joining the simulation evaluation
> effort.  I am not opposed to using MPRs (in addition to a CDS),
> but we need to evaluate them to see how they perform.
>
> At the IETF meeting, Bill Fenner encouraged us to work together, so
> I guess there was a perception at the meeting that we have not been
> working together.  I think we have been working together, since both
> Cisco and I have been working with Boeing to compare the two proposals
> that have been around for the last year.
>
> INRIA submitted their proposal only just before the last meeting, about
> a year after the other two proposals, and it is still not completely
> defined.  I am not sure why INRIA waited so long, but it is difficult
> to evaluate their proposal when it is the only one that has not yet
> been implemented in GTNetS (or even completely described).
> If INRIA had submitted their (fully defined) proposal a year ago, then
> we might have been able to fully evaluate it by now.
>
> But if the consensus is that we should evaluate INRIA's proposal
> (despite its late entry) then we should go ahead and do that, and also
> evaluate methods that use a combination of MPRs and a CDS (MDRs),
> before we make any decisions.  In this way, we should be able to
> work together to decide on the best solution.
>
> Richard
>
>
> _______________________________________________
> Ospf-manet mailing list
> Ospf-manet@ietf.org
> https://www1.ietf.org/mailman/listinfo/ospf-manet
>
>


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



From ospf-manet-bounces@ietf.org Fri Apr 21 18:53:21 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1FX4V6-0002Ho-2P; Fri, 21 Apr 2006 18:53:20 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1FX4V1-00022u-1X
	for ospf-manet@ietf.org; Fri, 21 Apr 2006 18:53:15 -0400
Received: from blv-smtpout-01.boeing.com ([130.76.32.69])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1FX4Ij-0004sF-90
	for ospf-manet@ietf.org; Fri, 21 Apr 2006 18:40:35 -0400
Received: from blv-av-01.boeing.com ([192.42.227.216])
	by blv-smtpout-01.boeing.com (8.9.2.MG.10092003/8.8.5-M2) with ESMTP id
	PAA28531; Fri, 21 Apr 2006 15:40:25 -0700 (PDT)
Received: from XCH-NWBH-11.nw.nos.boeing.com (localhost [127.0.0.1])
	by blv-av-01.boeing.com (8.11.3/8.11.3/MBS-AV-LDAP-01) with ESMTP id
	k3LMePr22654; Fri, 21 Apr 2006 15:40:25 -0700 (PDT)
Received: from XCH-NW-5V1.nw.nos.boeing.com ([130.247.55.44]) by
	XCH-NWBH-11.nw.nos.boeing.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Fri, 21 Apr 2006 15:40:23 -0700
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Subject: advertising non-adjacent links (was RE: [Ospf-manet] How can we get
	GTNet software?)
Date: Fri, 21 Apr 2006 15:40:23 -0700
Message-ID: <77F357662F8BFA4CA7074B0410171B6D01A2F0A5@XCH-NW-5V1.nw.nos.boeing.com>
In-Reply-To: <4448F6FA.7020106@inria.fr>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: advertising non-adjacent links (was RE: [Ospf-manet] How can we
	get GTNet software?)
Thread-Index: AcZlVl8p9kz5Sby2TLqAhnav29SwvgAOtuOA
From: "Henderson, Thomas R" <thomas.r.henderson@boeing.com>
To: "Philippe Jacquet" <philippe.jacquet@inria.fr>
X-OriginalArrivalTime: 21 Apr 2006 22:40:23.0807 (UTC)
	FILETIME=[93EE48F0:01C66594]
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 0a7aa2e6e558383d84476dc338324fab
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

=20

> -----Original Message-----
> From: Philippe Jacquet [mailto:philippe.jacquet@inria.fr]=20
> Sent: Friday, April 21, 2006 8:15 AM
> To: Richard Ogier
> Cc: ospf-manet@ietf.org
> Subject: Re: [Ospf-manet] How can we get GTNet software?
>=20
>=20
> I recognize that the concept of MDR has interesting feature=20
> in providing=20
> a reduced synchronizing backbone, but one must investigate=20
> the effect of=20
> advertizing non synchronized links in the core OSPF. Maybe we=20
> could give=20
> less synchronization priority degree to other synchronized=20
> links. Maybe=20
> some interesting combinations are possible.

This comment causes me to ask (perhaps more broadly of the OSPF MANET
list than just of Philippe) how one should evaluate the effect of
advertising these non-adjacent neighbors?  I have heard several people
declare general discomfort with this strategy without being able to
precisely describe why there is a problem.

Of course, in an unconstrained situation, we can form adjacencies with
everyone and advertise full topology and run sub-second Hellos, but this
is OSPF MANET and we have to trade off some of these items to achieve
better scalability. =20

I think that two separate issues are being conflated in this discussion.
Adjacencies are used to preserve database synchronization in an OSPF
network.  Type 1 links are advertised in LSAs to provide a graph upon
which to build paths.  I fail to see why it should be the case that all
advertised links should be adjacent links.  If anything, it should be
the link or neighbor quality that governs whether the link is included
in the data plane, not whether it exists in the OSPF control plan.  What
is the problem here? =20

>=20
> My first rule of the thumb evaluation let me think that=20
> advertizing full=20
> LSA's everytime there is a change may lead to a tremendous overhead,=20
> comparable to the of cost of synchronizing all links.=20

Exactly.

> Or we should=20
> accept that wireless OSPF would work on slow moving or quasi static=20
> wireless networks, and not on all kinds of MANETs.
>=20

I don't think we have to accept that.  However, I do think that if we
declare that OSPF MANET will only work on quasi-static or sparse MANETs,
and we do not allow for strategies to intelligently prune dense
topologies when they arise, OSPF MANET will have been a wasted effort.

Tom=20

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



From ospf-manet-bounces@ietf.org Sun Apr 23 20:14:52 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1FXoj6-00050q-PN; Sun, 23 Apr 2006 20:14:52 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1FXoj6-00050l-5W
	for ospf-manet@ietf.org; Sun, 23 Apr 2006 20:14:52 -0400
Received: from enterprise58.opnet.com ([192.104.65.21])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1FXoj5-0002Q7-Q9
	for ospf-manet@ietf.org; Sun, 23 Apr 2006 20:14:52 -0400
Received: from email.opnet.com (enterprise53-bak.opnet.com [172.16.1.44])
	by enterprise58.opnet.com (8.13.6/8.12.10) with SMTP id k3O0Digl007117; 
	Sun, 23 Apr 2006 20:13:44 -0400
Received: from 172.16.1.45 (SquirrelMail authenticated user adesai)
	by email.opnet.com with HTTP; Sun, 23 Apr 2006 20:14:49 -0400 (EDT)
Message-ID: <42615.172.16.1.45.1145837689.squirrel@email.opnet.com>
In-Reply-To: <E1FXKWx-0006fM-5n@megatron.ietf.org>
References: <E1FXKWx-0006fM-5n@megatron.ietf.org>
Date: Sun, 23 Apr 2006 20:14:49 -0400 (EDT)
From: adesai@opnet.com
To: ospf-manet@ietf.org
Cc: ospf-manet@ietf.org
User-Agent: SquirrelMail/1.4.2-1
MIME-Version: 1.0
Content-Type: text/plain;charset=iso-8859-1
Content-Transfer-Encoding: 8bit
X-Priority: 3
Importance: Normal
X-OPNET-MailScanner: Found to be clean
X-MailScanner-From: adesai@opnet.com
X-Spam-Score: 0.2 (/)
X-Scan-Signature: e472ca43d56132790a46d9eefd95f0a5
Subject: [Ospf-manet] Re: Ospf-manet Digest, Vol 6, Issue 5
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

Hello everyone,

This is the first time I am sending an email to this mailing list. So
greetings:) There is much I have learned simply by following the
discussion on this list.

I would first like to point out another argument to favor reduced set of
adjacencies: retransmissions. If we allowed the adjacency graph to be 
denser, redundant retransmissions would have an adverse effect. Also, we
should consider that battery life is an important parameter in MANET
routers, and relieving nodes to maintain expensive state information would
prove beneficial. Thus it seems to me that "minimal set of adjacencies" is
perhaps more essential than has been discussed. Also as Richard Ogier
correctly pointed out, "rate of change of adjacencies" (which would
determine database description traffic) is very important. Finally, nodes
having too many adjacencies would result in nodes generating too many LSA
(at the behest of every change in adjacency), which would have a further
effect in nodes having to share too many LSA headers in database
synchronization. The thing about MDR solution is that MDR selection is
persistent and as long as nodes are within reach of each other, MDR-other
nodes will not change their (backup) parent frequently, and will not
generate unnecessary LSA. Since in denser networks MDR-other nodes
constiture almost 80% of nodes, this feature is of great importance. It
offers both things: reduced set of adjacencies (helps retransmissions),
and reduced rate of LSA generation (which helps everything - LSU traffic,
database description traffic and LSU acknowledgement traffic).

If I understand correctly, the argument against the strategy of "minimal
adjacency graph and maximal routing graph" is that of routing loops. But
consider the fact that according to Ogier's published results (which I
have verified), the rate of change of adjacencies over the whole network
is not more than a few adjacencies (I remember figures such as 4-5
adjacencies for a 50 node biconnected network, which averages to about 10
seconds per node per adjacency change). Thus even if routing loops
existed, they could be temporary. But this should ofcourse be evaluated
more closely by introducing some advanced statistics.

However, if the network is too dynamic, obviously the strategies that
would boggle it down with protocol overhead are going to perform subpar.
In that case, we should evaluate whether delivery ratio would be more
adversely affected by a) possible routing loops, or b) more protocol
overhead. If the network is not too dynamic, then most of the 2-way
neighbors will be indirectly synchronized almost all the time, and minimal
adjacency graph solution would be superior without question. Thus an
evaluation in the spectrum towards more dynamic networks would be
extremely helpful.

Of course if we have on the order of 50 MBPS datarate (wimax), then a
protocol overhead of 100 KBPS versus 1 MBPS will not matter that much.
However a) OSPF should not make any assumption about layer 2 and should
only perform to the best of its ability to guarantee best service at
minimal overhead, and b) Battery life will still be a factor in high
datarate environments and nodes having to maintain more adjacencies and
perform more operations will drain their batteries that much faster.

Best regards,

Aniket Desai

> Send Ospf-manet mailing list submissions to
> 	ospf-manet@ietf.org
>
> To subscribe or unsubscribe via the World Wide Web, visit
> 	https://www1.ietf.org/mailman/listinfo/ospf-manet
> or, via email, send a message with subject or body 'help' to
> 	ospf-manet-request@ietf.org
>
> You can reach the person managing the list at
> 	ospf-manet-owner@ietf.org
>
> When replying, please edit your Subject line so it is more specific
> than "Re: Contents of Ospf-manet digest..."
>
>
> Today's Topics:
>
>    1. advertising non-adjacent links (was RE: [Ospf-manet] How can
>       we get	GTNet software?) (Henderson, Thomas R)
>
>
> ----------------------------------------------------------------------
>
> Message: 1
> Date: Fri, 21 Apr 2006 15:40:23 -0700
> From: "Henderson, Thomas R" <thomas.r.henderson@boeing.com>
> Subject: advertising non-adjacent links (was RE: [Ospf-manet] How can
> 	we get	GTNet software?)
> To: "Philippe Jacquet" <philippe.jacquet@inria.fr>
> Cc: ospf-manet@ietf.org
> Message-ID:
> 	<77F357662F8BFA4CA7074B0410171B6D01A2F0A5@XCH-NW-5V1.nw.nos.boeing.com>
>
> Content-Type: text/plain;	charset="us-ascii"
>
>
>
>> -----Original Message-----
>> From: Philippe Jacquet [mailto:philippe.jacquet@inria.fr]
>> Sent: Friday, April 21, 2006 8:15 AM
>> To: Richard Ogier
>> Cc: ospf-manet@ietf.org
>> Subject: Re: [Ospf-manet] How can we get GTNet software?
>>
>>
>> I recognize that the concept of MDR has interesting feature
>> in providing
>> a reduced synchronizing backbone, but one must investigate
>> the effect of
>> advertizing non synchronized links in the core OSPF. Maybe we
>> could give
>> less synchronization priority degree to other synchronized
>> links. Maybe
>> some interesting combinations are possible.
>
> This comment causes me to ask (perhaps more broadly of the OSPF MANET
> list than just of Philippe) how one should evaluate the effect of
> advertising these non-adjacent neighbors?  I have heard several people
> declare general discomfort with this strategy without being able to
> precisely describe why there is a problem.
>
> Of course, in an unconstrained situation, we can form adjacencies with
> everyone and advertise full topology and run sub-second Hellos, but this
> is OSPF MANET and we have to trade off some of these items to achieve
> better scalability.
>
> I think that two separate issues are being conflated in this discussion.
> Adjacencies are used to preserve database synchronization in an OSPF
> network.  Type 1 links are advertised in LSAs to provide a graph upon
> which to build paths.  I fail to see why it should be the case that all
> advertised links should be adjacent links.  If anything, it should be
> the link or neighbor quality that governs whether the link is included
> in the data plane, not whether it exists in the OSPF control plan.  What
> is the problem here?
>
>>
>> My first rule of the thumb evaluation let me think that
>> advertizing full
>> LSA's everytime there is a change may lead to a tremendous overhead,
>> comparable to the of cost of synchronizing all links.
>
> Exactly.
>
>> Or we should
>> accept that wireless OSPF would work on slow moving or quasi static
>> wireless networks, and not on all kinds of MANETs.
>>
>
> I don't think we have to accept that.  However, I do think that if we
> declare that OSPF MANET will only work on quasi-static or sparse MANETs,
> and we do not allow for strategies to intelligently prune dense
> topologies when they arise, OSPF MANET will have been a wasted effort.
>
> Tom
>
>
>
> ------------------------------
>
> _______________________________________________
> Ospf-manet mailing list
> Ospf-manet@ietf.org
> https://www1.ietf.org/mailman/listinfo/ospf-manet
>
>
> End of Ospf-manet Digest, Vol 6, Issue 5
> ****************************************
>


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



From ospf-manet-bounces@ietf.org Mon Apr 24 15:27:50 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1FY6is-0001zl-82; Mon, 24 Apr 2006 15:27:50 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1FY6ir-0001zf-1Y
	for ospf-manet@ietf.org; Mon, 24 Apr 2006 15:27:49 -0400
Received: from pop-savannah.atl.sa.earthlink.net ([207.69.195.69])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1FY6ip-00059F-MO
	for ospf-manet@ietf.org; Mon, 24 Apr 2006 15:27:49 -0400
Received: from dialup-4.243.128.203.dial1.sanfrancisco1.level3.net
	([4.243.128.203] helo=earthlink.net)
	by pop-savannah.atl.sa.earthlink.net with esmtp (Exim 3.36 #10)
	id 1FY6ij-0001P4-00
	for ospf-manet@ietf.org; Mon, 24 Apr 2006 15:27:42 -0400
Message-ID: <444D268B.8060602@earthlink.net>
Date: Mon, 24 Apr 2006 12:27:07 -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: ospf-manet@ietf.org
Subject: Re: [Ospf-manet] How can we get GTNet software?
References: <4430DFFF.4010104@inria.fr>
	<4430F8B2.2020103@cisco.com>	<44342F32.4080309@inria.fr>
	<443BE984.9030803@earthlink.net> <4448F6FA.7020106@inria.fr>
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
X-Spam-Score: 0.1 (/)
X-Scan-Signature: 7da5a831c477fb6ef97f379a05fb683c
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

Philippe,

Philippe Jacquet wrote:

> Dear Richard,
>
> I am glad that you consider our contribution as an interesting item. 
> We have produced this draft after the design team called for short 
> contributions on the subject. We apologize that we publish the draft a 
> little late, but we wanted to have something clean and we thank you 
> again for having immediately pointed last minute mistakes in the text. 
> However most of the items that are describing in our draft were 
> already intensively discussed on the mailing list for a long time, and 
> of them were already simulated. In particular:
>
> 1. Robustness of MPR flooding
> 2. Topology reduction and synchronization of advertized links.


I was referring to a detailed specification of your solution, which
did not come until just before the last IETF meeting. (Actually, it
probably still needs some more details before it is fully specified.)
Also, your simulations used abstract, simplified models.
Both the MDR and OR solutions have been implemented in GTNetS for
about a year.  Hopefully, INRIA's solution will be implemented in
GTNetS soon.

>
>
> I recognize that the concept of MDR has interesting feature in 
> providing a reduced synchronizing backbone, but one must investigate 
> the effect of advertizing non synchronized links in the core OSPF.


There is a common misconception here, which has been discussed.
OSPF does advertise links that are not synchronized (but are indirectly
synchronized). I mentioned this in Section 2.4 of the MDR draft.
(Note that I modified the overview of OSPF-MDR in the draft
to provide more motivation.)  The network-LSA of OSPF implies there is
a direct connection between any two routers attached to the same
broadcast network, if both routers are synchronized with the DR.
This implies that any such router can use any other such routeras a next 
hop (in the SPF calculation). Of course, a network-LSA cannot
describe the general topology of a MANET, so it is necessary to
explicitly include non-adjacent neighbors in the router-LSA.
In both cases, the LSA does imply that unsynchronized links can be
used for routing (even beyond the first hop).

Of course, even in your solution the first hop of a route need not
be synchronized, which could cause a problem unless you use a
routability condition as in OSPF-MDR.

Anyway, the simulation results will show how performance is affected
when unsynchronized links are advertised.  I think the main difference
will be that the solution will not be as scalable if all MPRs are
required to be synchronized.


> Maybe we could give less synchronization priority degree to other 
> synchronized links. Maybe some interesting combinations are possible.


The GTNetS simulations already assign a slightly larger metric to
unsynchronized links.

Richard

>
>
> My first rule of the thumb evaluation let me think that advertizing 
> full LSA's everytime there is a change may lead to a tremendous 
> overhead, comparable to the of cost of synchronizing all links. Or we 
> should accept that wireless OSPF would work on slow moving or quasi 
> static wireless networks, and not on all kinds of MANETs.
>
> I am looking forward the simulation results.
>
> Best regards,
> Philippe
>
>
> Richard Ogier wrote:
>
>>> Thanks, Acee, thanks Tom,
>>>
>>> Sorry for the delay. I just have realized why these emails got lost, 
>>> I have a zealous anti-spammer that systematically dropped the emails.
>>>
>>> Yes it would be great to synchronize our efforts on GTNet. Let's see 
>>> how to proceed.
>>>
>>> Best regards,
>>> Philippe 
>>
>>
>>
>>
>>
>> I am glad that INRIA is finally joining the simulation evaluation
>> effort.  I am not opposed to using MPRs (in addition to a CDS),
>> but we need to evaluate them to see how they perform.
>>
>> At the IETF meeting, Bill Fenner encouraged us to work together, so
>> I guess there was a perception at the meeting that we have not been
>> working together.  I think we have been working together, since both
>> Cisco and I have been working with Boeing to compare the two proposals
>> that have been around for the last year.
>>
>> INRIA submitted their proposal only just before the last meeting, about
>> a year after the other two proposals, and it is still not completely
>> defined.  I am not sure why INRIA waited so long, but it is difficult
>> to evaluate their proposal when it is the only one that has not yet
>> been implemented in GTNetS (or even completely described).
>> If INRIA had submitted their (fully defined) proposal a year ago, then
>> we might have been able to fully evaluate it by now.
>>
>> But if the consensus is that we should evaluate INRIA's proposal
>> (despite its late entry) then we should go ahead and do that, and also
>> evaluate methods that use a combination of MPRs and a CDS (MDRs),
>> before we make any decisions.  In this way, we should be able to
>> work together to decide on the best solution.
>>
>> Richard
>>
>>
>> _______________________________________________
>> Ospf-manet mailing list
>> Ospf-manet@ietf.org
>> https://www1.ietf.org/mailman/listinfo/ospf-manet
>>
>>
>
>
>



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



From ospf-manet-bounces@ietf.org Fri Apr 28 09:07:41 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1FZShB-00033x-Of; Fri, 28 Apr 2006 09:07:41 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1FZShA-00033s-Va
	for ospf-manet@ietf.org; Fri, 28 Apr 2006 09:07:40 -0400
Received: from concorde.inria.fr ([192.93.2.39])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1FZSh7-0000eK-IX
	for ospf-manet@ietf.org; Fri, 28 Apr 2006 09:07:40 -0400
Received: from [192.168.112.160] ([129.104.11.1]) (authenticated bits=0)
	by concorde.inria.fr (8.13.0/8.13.0) with ESMTP id k3SD7Yxn018384
	(version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO);
	Fri, 28 Apr 2006 15:07:34 +0200
Message-ID: <4452137E.6030008@inria.fr>
Date: Fri, 28 Apr 2006 15:07:10 +0200
From: Philippe Jacquet <philippe.jacquet@inria.fr>
Organization: inria
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US;
	rv:1.7.1) Gecko/20040707
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: "Henderson, Thomas R" <thomas.r.henderson@boeing.com>
Subject: Re: advertising non-adjacent links (was RE: [Ospf-manet] How can
	we get GTNet software?)
References: <77F357662F8BFA4CA7074B0410171B6D01A2F0A5@XCH-NW-5V1.nw.nos.boeing.com>
In-Reply-To: <77F357662F8BFA4CA7074B0410171B6D01A2F0A5@XCH-NW-5V1.nw.nos.boeing.com>
Content-Type: text/plain; charset=windows-1252; format=flowed
X-j-chkmail-Score: MSGID : 44521396.000 on concorde : j-chkmail score : XX :
	0/20 2
X-Miltered: at concorde with ID 44521396.000 by Joe's j-chkmail
	(http://j-chkmail.ensmp.fr)!
Content-Transfer-Encoding: quoted-printable
X-MIME-Autoconverted: from 8bit to quoted-printable by concorde.inria.fr id
	k3SD7Yxn018384
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 6e922792024732fb1bb6f346e63517e4
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

Dear Tom,

Maybe the discomfort comes from the fact that we tried to go too fast on=20
MANET over OSPF. Since people seem already reluctant to have flooding on=20
non adjacent links, we may expect even more reluctance to have data=20
routed over non adjacent links. Indeed data doesn=92t have sequence numbe=
r=20
and loops of data packets could be possible (although it is rather=20
unlikely). I would say that MANET belongs more to the land of best=20
effort, and OSPF belongs more to the land of exactitude, so to speak, in=20
terms of routing. I am sure that MANET-OSPF can find a good compromise=20
in between.

For example, I don=92t think that we have to sacrifice some performance=20
for exactitude (or not more than temporarily). In particular,=20
synchronization overhead can be greatly reduced by using signature=20
exchange between direct neighbors. If in the near future there is a=20
trend towards using such an optimization, then the performance issues=20
related to synchronization overhead will disappear.

Best regards,
Philippe


Henderson, Thomas R wrote:

>=20
>
> =20
>
>>-----Original Message-----
>>From: Philippe Jacquet [mailto:philippe.jacquet@inria.fr]=20
>>Sent: Friday, April 21, 2006 8:15 AM
>>To: Richard Ogier
>>Cc: ospf-manet@ietf.org
>>Subject: Re: [Ospf-manet] How can we get GTNet software?
>>
>>
>>I recognize that the concept of MDR has interesting feature=20
>>in providing=20
>>a reduced synchronizing backbone, but one must investigate=20
>>the effect of=20
>>advertizing non synchronized links in the core OSPF. Maybe we=20
>>could give=20
>>less synchronization priority degree to other synchronized=20
>>links. Maybe=20
>>some interesting combinations are possible.
>>   =20
>>
>
>This comment causes me to ask (perhaps more broadly of the OSPF MANET
>list than just of Philippe) how one should evaluate the effect of
>advertising these non-adjacent neighbors?  I have heard several people
>declare general discomfort with this strategy without being able to
>precisely describe why there is a problem.
>
>Of course, in an unconstrained situation, we can form adjacencies with
>everyone and advertise full topology and run sub-second Hellos, but this
>is OSPF MANET and we have to trade off some of these items to achieve
>better scalability. =20
>
>I think that two separate issues are being conflated in this discussion.
>Adjacencies are used to preserve database synchronization in an OSPF
>network.  Type 1 links are advertised in LSAs to provide a graph upon
>which to build paths.  I fail to see why it should be the case that all
>advertised links should be adjacent links.  If anything, it should be
>the link or neighbor quality that governs whether the link is included
>in the data plane, not whether it exists in the OSPF control plan.  What
>is the problem here? =20
>
> =20
>
>>My first rule of the thumb evaluation let me think that=20
>>advertizing full=20
>>LSA's everytime there is a change may lead to a tremendous overhead,=20
>>comparable to the of cost of synchronizing all links.=20
>>   =20
>>
>
>Exactly.
>
> =20
>
>>Or we should=20
>>accept that wireless OSPF would work on slow moving or quasi static=20
>>wireless networks, and not on all kinds of MANETs.
>>
>>   =20
>>
>
>I don't think we have to accept that.  However, I do think that if we
>declare that OSPF MANET will only work on quasi-static or sparse MANETs,
>and we do not allow for strategies to intelligently prune dense
>topologies when they arise, OSPF MANET will have been a wasted effort.
>
>Tom=20
>
>
> =20
>


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



From ospf-manet-bounces@ietf.org Fri Apr 28 13:44:29 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1FZX13-0006aB-Dw; Fri, 28 Apr 2006 13:44:29 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1FZX12-0006a1-Cs
	for ospf-manet@ietf.org; Fri, 28 Apr 2006 13:44:28 -0400
Received: from blv-smtpout-01.boeing.com ([130.76.32.69])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1FZX11-0007cV-Sv
	for ospf-manet@ietf.org; Fri, 28 Apr 2006 13:44:28 -0400
Received: from stl-av-01.boeing.com ([192.76.190.6])
	by blv-smtpout-01.boeing.com (8.9.2.MG.10092003/8.8.5-M2) with ESMTP id
	KAA25649; Fri, 28 Apr 2006 10:44:19 -0700 (PDT)
Received: from XCH-NWBH-11.nw.nos.boeing.com (localhost [127.0.0.1])
	by stl-av-01.boeing.com (8.11.3/8.11.3/MBS-AV-LDAP-01) with ESMTP id
	k3SHiIG22968; Fri, 28 Apr 2006 12:44:18 -0500 (CDT)
Received: from XCH-NW-5V1.nw.nos.boeing.com ([130.247.55.44]) by
	XCH-NWBH-11.nw.nos.boeing.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Fri, 28 Apr 2006 10:44:11 -0700
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Subject: RE: advertising non-adjacent links (was RE: [Ospf-manet] How canwe
	get GTNet software?)
Date: Fri, 28 Apr 2006 10:44:10 -0700
Message-ID: <77F357662F8BFA4CA7074B0410171B6D01A2F10A@XCH-NW-5V1.nw.nos.boeing.com>
In-Reply-To: <4452137E.6030008@inria.fr>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: advertising non-adjacent links (was RE: [Ospf-manet] How canwe
	get GTNet software?)
Thread-Index: AcZqxRNaOgebO5zoShGOloYjoJuzlwAI7P7g
From: "Henderson, Thomas R" <thomas.r.henderson@boeing.com>
To: "Philippe Jacquet" <philippe.jacquet@inria.fr>
X-OriginalArrivalTime: 28 Apr 2006 17:44:11.0351 (UTC)
	FILETIME=[5B9CF670:01C66AEB]
X-Spam-Score: 0.0 (/)
X-Scan-Signature: f4c2cf0bccc868e4cc88dace71fb3f44
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

Philippe, comments inline:

> -----Original Message-----
> From: Philippe Jacquet [mailto:philippe.jacquet@inria.fr]=20
> Sent: Friday, April 28, 2006 6:07 AM
> To: Henderson, Thomas R
> Cc: ospf-manet@ietf.org
> Subject: Re: advertising non-adjacent links (was RE:=20
> [Ospf-manet] How canwe get GTNet software?)
>=20
> Dear Tom,
>=20
> Maybe the discomfort comes from the fact that we tried to go=20
> too fast on=20
> MANET over OSPF. Since people seem already reluctant to have=20
> flooding on=20
> non adjacent links, we may expect even more reluctance to have data=20
> routed over non adjacent links.=20

I do not think these issues are the same.  Retransmissions are related
to preserving database synchronization and are hence related to
adjacencies.  When the topic of flooding over non-adjacent links has
arisen in the past, an implementor complained that it would be too
disruptive to their implementations to decouple retransmissions from
adjacencies.  Richard has also pointed out numerous times that OSPF
already allows data to be forwarded over non-adjacent links.

I am not disputing that there may be reluctance to forward data over non
adjacent links, only that this reluctance has never been justified
adequately in my opinion (including this message).

> Indeed data doesn't have=20
> sequence number=20
> and loops of data packets could be possible (although it is rather=20
> unlikely). I would say that MANET belongs more to the land of best=20
> effort, and OSPF belongs more to the land of exactitude, so=20
> to speak, in=20
> terms of routing. I am sure that MANET-OSPF can find a good=20
> compromise=20
> in between.
>=20
> For example, I don't think that we have to sacrifice some performance=20
> for exactitude (or not more than temporarily). In particular,=20
> synchronization overhead can be greatly reduced by using signature=20
> exchange between direct neighbors. If in the near future there is a=20
> trend towards using such an optimization, then the performance issues=20
> related to synchronization overhead will disappear.

You seem to be suggesting that the reduction of synchronization overhead
by making the existing process more efficient can approach the
efficiency of just suppressing some of the adjacencies.  I think that
remains to be seen and would add that it is may be the combination of
both that would be the most efficient.  I don't know what the level of
acceptance of changes to database synchronization procedures would be,
relative to the acceptance of procedures to suppress some adjacencies =20

Regards,
Tom

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



