From mailnull@www1.ietf.org  Fri Nov  1 04:57:22 2002
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id EAA02408
	for <manet-archive@odin.ietf.org>; Fri, 1 Nov 2002 04:57:21 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id gA19xRg13328
	for manet-archive@odin.ietf.org; Fri, 1 Nov 2002 04:59:27 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gA19xRv13325
	for <manet-web-archive@optimus.ietf.org>; Fri, 1 Nov 2002 04:59:27 -0500
Received: from www1.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id EAA02392
	for <manet-web-archive@ietf.org>; Fri, 1 Nov 2002 04:56:50 -0500 (EST)
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gA19pav12893;
	Fri, 1 Nov 2002 04:51:36 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gA19kiv12661
	for <manet@optimus.ietf.org>; Fri, 1 Nov 2002 04:46:44 -0500
Received: from Tempo.Update.UU.SE (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id EAA02183
	for <manet@ietf.org>; Fri, 1 Nov 2002 04:44:07 -0500 (EST)
Received: from Tempo.Update.UU.SE (localhost [127.0.0.1])
	by Tempo.Update.UU.SE (8.12.3/8.12.3/Update-Iltempogigante) with ESMTP id gA19kT8S029396
	(version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO);
	Fri, 1 Nov 2002 10:46:29 +0100
Received: from localhost (davidl@localhost)
	by Tempo.Update.UU.SE (8.12.3/8.12.3/Update-Iltempogigante-submit) with ESMTP id gA19kSd4029393;
	Fri, 1 Nov 2002 10:46:28 +0100
X-Authentication-Warning: Tempo.Update.UU.SE: davidl owned process doing -bs
Date: Fri, 1 Nov 2002 10:46:27 +0100 (CET)
From: David Lundberg <davidl@update.uu.se>
To: manet@ietf.org
Message-ID: <Pine.LNX.4.21.0211011022170.3818-100000@Tempo.Update.UU.SE>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=iso-8859-1
Content-Transfer-Encoding: 8bit
X-MIME-Autoconverted: from QUOTED-PRINTABLE to 8bit by www1.ietf.org id gA19kiv12662
Subject: [manet] MANET - List of routing protocols
Sender: manet-admin@ietf.org
Errors-To: manet-admin@ietf.org
X-BeenThere: manet@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/manet>,
	<mailto:manet-request@ietf.org?subject=unsubscribe>
List-Id: Mobile Ad-hoc Networks  <manet.ietf.org>
List-Post: <mailto:manet@ietf.org>
List-Help: <mailto:manet-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/manet>,
	<mailto:manet-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 8bit
Content-Transfer-Encoding: 8bit


Hi all!

During the summer I published a list of the existing I had found on the
net and asked for comments. I got great response and added the changes to
my "little" list. Now I have realized that I won't have time to keep it
updated and thought that I should try to add it to one of these Wiki-sites
to let other interested people use/update it. Now I have published the
list along with the references I had. PSE have a look and feel free to
correct/change the list. I don't claim that I have sorted them correctly..
That could be something for people to discuss. :)

The list itself:

http://www.wikipedia.org/wiki/Ad_hoc_protocol_list

Short summary of implementations, pse add more:

http://www.wikipedia.org/wiki/Ad_hoc_protocols_implementations

Comments are as always very welcome!

Regards,

// David //


--------------------------------------------------------------
David Lundberg            Phone: Home(Uppsala)   +46-18-460356
Mail: davidl@update.uu.se        Home(Gävle)     +46-26-146743
Http: www.update.uu.se/~davidl   Cellular       +46-70-3531696
ICQ:  13440550                   IT-Dept. @ UU  +46-18-4716231
--------------------------------------------------------------



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



From manet-admin@ietf.org  Fri Nov  1 04:57:23 2002
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id EAA02421
	for <manet-archive@lists.ietf.org>; Fri, 1 Nov 2002 04:57:23 -0500 (EST)
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gA19pav12893;
	Fri, 1 Nov 2002 04:51:36 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gA19kiv12661
	for <manet@optimus.ietf.org>; Fri, 1 Nov 2002 04:46:44 -0500
Received: from Tempo.Update.UU.SE (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id EAA02183
	for <manet@ietf.org>; Fri, 1 Nov 2002 04:44:07 -0500 (EST)
Received: from Tempo.Update.UU.SE (localhost [127.0.0.1])
	by Tempo.Update.UU.SE (8.12.3/8.12.3/Update-Iltempogigante) with ESMTP id gA19kT8S029396
	(version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO);
	Fri, 1 Nov 2002 10:46:29 +0100
Received: from localhost (davidl@localhost)
	by Tempo.Update.UU.SE (8.12.3/8.12.3/Update-Iltempogigante-submit) with ESMTP id gA19kSd4029393;
	Fri, 1 Nov 2002 10:46:28 +0100
X-Authentication-Warning: Tempo.Update.UU.SE: davidl owned process doing -bs
Date: Fri, 1 Nov 2002 10:46:27 +0100 (CET)
From: David Lundberg <davidl@update.uu.se>
To: manet@ietf.org
Message-ID: <Pine.LNX.4.21.0211011022170.3818-100000@Tempo.Update.UU.SE>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=iso-8859-1
Content-Transfer-Encoding: 8bit
X-MIME-Autoconverted: from QUOTED-PRINTABLE to 8bit by www1.ietf.org id gA19kiv12662
Subject: [manet] MANET - List of routing protocols
Sender: manet-admin@ietf.org
Errors-To: manet-admin@ietf.org
X-BeenThere: manet@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/manet>,
	<mailto:manet-request@ietf.org?subject=unsubscribe>
List-Id: Mobile Ad-hoc Networks  <manet.ietf.org>
List-Post: <mailto:manet@ietf.org>
List-Help: <mailto:manet-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/manet>,
	<mailto:manet-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 8bit


Hi all!

During the summer I published a list of the existing I had found on the
net and asked for comments. I got great response and added the changes to
my "little" list. Now I have realized that I won't have time to keep it
updated and thought that I should try to add it to one of these Wiki-sites
to let other interested people use/update it. Now I have published the
list along with the references I had. PSE have a look and feel free to
correct/change the list. I don't claim that I have sorted them correctly..
That could be something for people to discuss. :)

The list itself:

http://www.wikipedia.org/wiki/Ad_hoc_protocol_list

Short summary of implementations, pse add more:

http://www.wikipedia.org/wiki/Ad_hoc_protocols_implementations

Comments are as always very welcome!

Regards,

// David //


--------------------------------------------------------------
David Lundberg            Phone: Home(Uppsala)   +46-18-460356
Mail: davidl@update.uu.se        Home(Gävle)     +46-26-146743
Http: www.update.uu.se/~davidl   Cellular       +46-70-3531696
ICQ:  13440550                   IT-Dept. @ UU  +46-18-4716231
--------------------------------------------------------------



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


From mailnull@www1.ietf.org  Fri Nov  1 07:27:17 2002
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id HAA04678
	for <manet-archive@odin.ietf.org>; Fri, 1 Nov 2002 07:27:17 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id gA1CTDS20669
	for manet-archive@odin.ietf.org; Fri, 1 Nov 2002 07:29:13 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gA1CTDv20666
	for <manet-web-archive@optimus.ietf.org>; Fri, 1 Nov 2002 07:29:13 -0500
Received: from www1.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id HAA04667
	for <manet-web-archive@ietf.org>; Fri, 1 Nov 2002 07:26:46 -0500 (EST)
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gA1CLJv20403;
	Fri, 1 Nov 2002 07:21:19 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gA1CIcv20327
	for <manet@optimus.ietf.org>; Fri, 1 Nov 2002 07:18:38 -0500
Received: from cgprelay.ua.pt (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id HAA04529
	for <manet@ietf.org>; Fri, 1 Nov 2002 07:16:11 -0500 (EST)
Received: from [192.168.69.129] (HELO frontend-1.cgpmail.ua.pt)
  by cgprelay.ua.pt (CommuniGate Pro SMTP 4.0)
  with ESMTP id 5227537 for manet@ietf.org; Fri, 01 Nov 2002 12:18:34 +0000
Received: from [192.168.69.132] (HELO backend-2.cgpmail.ua.pt)
  by frontend-1.cgpmail.ua.pt (CommuniGate Pro SMTP 4.0)
  with ESMTP id 5011069 for manet@ietf.org; Fri, 01 Nov 2002 12:18:34 +0000
X-UA: Message Inspected for Viruses by RAV
Received: from [213.30.47.91] (account <etgirao@ua.pt>)
  by backend-2.cgpmail.ua.pt (CommuniGate Pro WebUser 4.0)
  with HTTP id 3893059 for <manet@ietf.org>; Fri, 01 Nov 2002 12:18:34 +0000
From: Joao Francisco de Lima Lobo Girao <etgirao@ua.pt>
Subject: Re: [manet] MANET - List of routing protocols
To: manet@ietf.org
X-Mailer: CommuniGate Pro Web Mailer v.4.0
Date: Fri, 01 Nov 2002 12:18:34 +0000
Message-ID: <web-3893059@backend-2.cgpmail.ua.pt>
In-Reply-To: <Pine.LNX.4.21.0211011022170.3818-100000@Tempo.Update.UU.SE>
MIME-Version: 1.0
Content-Type: text/plain; charset="ISO-8859-1"; format="flowed"
Content-Transfer-Encoding: 8bit
Content-Transfer-Encoding: 8bit
Sender: manet-admin@ietf.org
Errors-To: manet-admin@ietf.org
X-BeenThere: manet@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/manet>,
	<mailto:manet-request@ietf.org?subject=unsubscribe>
List-Id: Mobile Ad-hoc Networks  <manet.ietf.org>
List-Post: <mailto:manet@ietf.org>
List-Help: <mailto:manet-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/manet>,
	<mailto:manet-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 8bit
Content-Transfer-Encoding: 8bit

Why not include INRIA's implementation for OLSR on your 
list? 

http://hipercom.inria.fr/olsr

On Fri, 1 Nov 2002 10:46:27 +0100 (CET)
  David Lundberg <davidl@update.uu.se> wrote:
>
>Hi all!
>
>During the summer I published a list of the existing I 
>had found on the
>net and asked for comments. I got great response and 
>added the changes to
>my "little" list. Now I have realized that I won't have 
>time to keep it
>updated and thought that I should try to add it to one of 
>these Wiki-sites
>to let other interested people use/update it. Now I have 
>published the
>list along with the references I had. PSE have a look and 
>feel free to
>correct/change the list. I don't claim that I have sorted 
>them correctly..
>That could be something for people to discuss. :)
>
>The list itself:
>
>http://www.wikipedia.org/wiki/Ad_hoc_protocol_list
>
>Short summary of implementations, pse add more:
>
>http://www.wikipedia.org/wiki/Ad_hoc_protocols_implementations
>
>Comments are as always very welcome!
>
>Regards,
>
>// David //
>
>
>--------------------------------------------------------------
>David Lundberg            Phone: Home(Uppsala) 
>  +46-18-460356
>Mail: davidl@update.uu.se        Home(Gävle) 
>    +46-26-146743
>Http: www.update.uu.se/~davidl   Cellular 
>      +46-70-3531696
>ICQ:  13440550                   IT-Dept. @ UU 
> +46-18-4716231
>--------------------------------------------------------------
>
>
>
>_______________________________________________
>manet mailing list
>manet@ietf.org
>https://www1.ietf.org/mailman/listinfo/manet

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



From manet-admin@ietf.org  Fri Nov  1 07:27:19 2002
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id HAA04692
	for <manet-archive@lists.ietf.org>; Fri, 1 Nov 2002 07:27:19 -0500 (EST)
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gA1CLJv20403;
	Fri, 1 Nov 2002 07:21:19 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gA1CIcv20327
	for <manet@optimus.ietf.org>; Fri, 1 Nov 2002 07:18:38 -0500
Received: from cgprelay.ua.pt (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id HAA04529
	for <manet@ietf.org>; Fri, 1 Nov 2002 07:16:11 -0500 (EST)
Received: from [192.168.69.129] (HELO frontend-1.cgpmail.ua.pt)
  by cgprelay.ua.pt (CommuniGate Pro SMTP 4.0)
  with ESMTP id 5227537 for manet@ietf.org; Fri, 01 Nov 2002 12:18:34 +0000
Received: from [192.168.69.132] (HELO backend-2.cgpmail.ua.pt)
  by frontend-1.cgpmail.ua.pt (CommuniGate Pro SMTP 4.0)
  with ESMTP id 5011069 for manet@ietf.org; Fri, 01 Nov 2002 12:18:34 +0000
X-UA: Message Inspected for Viruses by RAV
Received: from [213.30.47.91] (account <etgirao@ua.pt>)
  by backend-2.cgpmail.ua.pt (CommuniGate Pro WebUser 4.0)
  with HTTP id 3893059 for <manet@ietf.org>; Fri, 01 Nov 2002 12:18:34 +0000
From: Joao Francisco de Lima Lobo Girao <etgirao@ua.pt>
Subject: Re: [manet] MANET - List of routing protocols
To: manet@ietf.org
X-Mailer: CommuniGate Pro Web Mailer v.4.0
Date: Fri, 01 Nov 2002 12:18:34 +0000
Message-ID: <web-3893059@backend-2.cgpmail.ua.pt>
In-Reply-To: <Pine.LNX.4.21.0211011022170.3818-100000@Tempo.Update.UU.SE>
MIME-Version: 1.0
Content-Type: text/plain; charset="ISO-8859-1"; format="flowed"
Content-Transfer-Encoding: 8bit
Content-Transfer-Encoding: 8bit
Sender: manet-admin@ietf.org
Errors-To: manet-admin@ietf.org
X-BeenThere: manet@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/manet>,
	<mailto:manet-request@ietf.org?subject=unsubscribe>
List-Id: Mobile Ad-hoc Networks  <manet.ietf.org>
List-Post: <mailto:manet@ietf.org>
List-Help: <mailto:manet-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/manet>,
	<mailto:manet-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 8bit

Why not include INRIA's implementation for OLSR on your 
list? 

http://hipercom.inria.fr/olsr

On Fri, 1 Nov 2002 10:46:27 +0100 (CET)
  David Lundberg <davidl@update.uu.se> wrote:
>
>Hi all!
>
>During the summer I published a list of the existing I 
>had found on the
>net and asked for comments. I got great response and 
>added the changes to
>my "little" list. Now I have realized that I won't have 
>time to keep it
>updated and thought that I should try to add it to one of 
>these Wiki-sites
>to let other interested people use/update it. Now I have 
>published the
>list along with the references I had. PSE have a look and 
>feel free to
>correct/change the list. I don't claim that I have sorted 
>them correctly..
>That could be something for people to discuss. :)
>
>The list itself:
>
>http://www.wikipedia.org/wiki/Ad_hoc_protocol_list
>
>Short summary of implementations, pse add more:
>
>http://www.wikipedia.org/wiki/Ad_hoc_protocols_implementations
>
>Comments are as always very welcome!
>
>Regards,
>
>// David //
>
>
>--------------------------------------------------------------
>David Lundberg            Phone: Home(Uppsala) 
>  +46-18-460356
>Mail: davidl@update.uu.se        Home(Gävle) 
>    +46-26-146743
>Http: www.update.uu.se/~davidl   Cellular 
>      +46-70-3531696
>ICQ:  13440550                   IT-Dept. @ UU 
> +46-18-4716231
>--------------------------------------------------------------
>
>
>
>_______________________________________________
>manet mailing list
>manet@ietf.org
>https://www1.ietf.org/mailman/listinfo/manet

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


From sip-admin@ietf.org  Fri Nov  1 09:04:37 2002
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA07738
	for <manet-archive@lists.ietf.org>; Fri, 1 Nov 2002 09:04:37 -0500 (EST)
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gA1E6Zv29155
	for <manet-archive@lists.ietf.org>; Fri, 1 Nov 2002 09:06:35 -0500
Date: Fri, 01 Nov 2002 09:06:35 -0500
Message-ID: <20021101140635.25483.28315.Mailman@www1.ietf.org>
Subject: ietf.org mailing list memberships reminder
From: mailman-owner@www1.ietf.org
To: manet-archive@ietf.org
X-No-Archive: yes
X-Ack: no
Sender: sip-admin@ietf.org
Errors-To: sip-admin@ietf.org
X-BeenThere: sip@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk

This is a reminder, sent out once a month, about your ietf.org mailing
list memberships.  It includes your subscription info and how to use
it to change it or unsubscribe from a list.

You can visit the URLs to change your membership status or
configuration, including unsubscribing, setting digest-style delivery
or disabling delivery altogether (e.g., for a vacation), and so on.

In addition to the URL interfaces, you can also use email to make such
changes.  For more info, send a message to the '-request' address of
the list (for example, manet-request@ietf.org) containing just the
word 'help' in the message body, and an email message will be sent to
you with instructions.

***************************************************************************


                              Note Well

All statements related to the activities of the IETF and addressed to
the IETF are subject to all provisions of Section 10 of RFC 2026,
which grants to the IETF and its participants certain licenses and
rights in such statements. Such statements include verbal statements
in IETF meetings, as well as written and electronic communications
made at any time or place, which are addressed to

        * the IETF plenary session,
        * any IETF working group or portion thereof,
        * the IESG, or any member thereof on behalf of the IESG,
        * the IAB or any member thereof on behalf of the IAB,
        * any IETF mailing list, including the IETF list itself, any
working
            group or design team list, or any other list functioning
under IETF
            auspices,
        * the RFC Editor or the Internet-Drafts function

Statements made outside of an IETF meeting, mailing list or other
function, that are clearly not intended to be input to an IETF
activity, group or function, are not subject to these provisions.

   
***************************************************************************


If you have questions, problems, comments, etc, send them to
mailman-owner@www1.ietf.org.  Thanks!

Passwords for manet-archive@lists.ietf.org:

List                                     Password // URL
----                                     --------  
manet@ietf.org                           FtOz      
https://www1.ietf.org/mailman/options/manet/manet-archive%40lists.ietf.org


From mailnull@www1.ietf.org  Fri Nov  1 11:00:41 2002
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA18736
	for <manet-archive@odin.ietf.org>; Fri, 1 Nov 2002 11:00:40 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id gA1G2b206704
	for manet-archive@odin.ietf.org; Fri, 1 Nov 2002 11:02:37 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gA1G2bv06701
	for <manet-web-archive@optimus.ietf.org>; Fri, 1 Nov 2002 11:02:37 -0500
Received: from www1.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA18705
	for <manet-web-archive@ietf.org>; Fri, 1 Nov 2002 11:00:09 -0500 (EST)
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gA1Frvv02922;
	Fri, 1 Nov 2002 10:53:57 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gA1FpVv02309
	for <manet@optimus.ietf.org>; Fri, 1 Nov 2002 10:51:31 -0500
Received: from web40509.mail.yahoo.com (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id KAA17842
	for <manet@ietf.org>; Fri, 1 Nov 2002 10:49:03 -0500 (EST)
Message-ID: <20021101155123.51423.qmail@web40509.mail.yahoo.com>
Received: from [128.138.86.144] by web40509.mail.yahoo.com via HTTP; Fri, 01 Nov 2002 07:51:23 PST
Date: Fri, 1 Nov 2002 07:51:23 -0800 (PST)
From: Sagar Sanghani <sanghani_s@yahoo.com>
To: manet@ietf.org
In-Reply-To: <20021101094801.12758.35602.Mailman@www1.ietf.org>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Subject: [manet] Re: Testing DSR over ethernet
Sender: manet-admin@ietf.org
Errors-To: manet-admin@ietf.org
X-BeenThere: manet@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/manet>,
	<mailto:manet-request@ietf.org?subject=unsubscribe>
List-Id: Mobile Ad-hoc Networks  <manet.ietf.org>
List-Post: <mailto:manet@ietf.org>
List-Help: <mailto:manet-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/manet>,
	<mailto:manet-request@ietf.org?subject=subscribe>


There has been some work in building a testbed
over ethernet. 
This one deals with similar stuff to what you
guys are trying to do.
Zhang, Y., Li, W., “An Integrated Environment for
Testing Mobile Ad-Hoc Networks,” Proceedings of
MOBIHOC ’02,

Obviously you'll be ignoring RF effects over ETHERNET
and we have found that this makes a HUGE difference.

Actually we already have a working version of DSR
on CLICK. Our current work is focused on developing
an energy aware version of DSR.
We have developed a testbed using attenuators. This
testbed emulates RF effects as well as a limited form
of mobility. Our entire design fits onto a single
table. Let me know if you guys want some more info.


Sagar Sanghani
University of Colorado
http://pecolab.colorado.edu


__________________________________________________
Do you Yahoo!?
HotJobs - Search new jobs daily now
http://hotjobs.yahoo.com/
_______________________________________________
manet mailing list
manet@ietf.org
https://www1.ietf.org/mailman/listinfo/manet



From manet-admin@ietf.org  Fri Nov  1 11:00:44 2002
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA18749
	for <manet-archive@lists.ietf.org>; Fri, 1 Nov 2002 11:00:44 -0500 (EST)
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gA1Frvv02922;
	Fri, 1 Nov 2002 10:53:57 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gA1FpVv02309
	for <manet@optimus.ietf.org>; Fri, 1 Nov 2002 10:51:31 -0500
Received: from web40509.mail.yahoo.com (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id KAA17842
	for <manet@ietf.org>; Fri, 1 Nov 2002 10:49:03 -0500 (EST)
Message-ID: <20021101155123.51423.qmail@web40509.mail.yahoo.com>
Received: from [128.138.86.144] by web40509.mail.yahoo.com via HTTP; Fri, 01 Nov 2002 07:51:23 PST
Date: Fri, 1 Nov 2002 07:51:23 -0800 (PST)
From: Sagar Sanghani <sanghani_s@yahoo.com>
To: manet@ietf.org
In-Reply-To: <20021101094801.12758.35602.Mailman@www1.ietf.org>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Subject: [manet] Re: Testing DSR over ethernet
Sender: manet-admin@ietf.org
Errors-To: manet-admin@ietf.org
X-BeenThere: manet@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/manet>,
	<mailto:manet-request@ietf.org?subject=unsubscribe>
List-Id: Mobile Ad-hoc Networks  <manet.ietf.org>
List-Post: <mailto:manet@ietf.org>
List-Help: <mailto:manet-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/manet>,
	<mailto:manet-request@ietf.org?subject=subscribe>


There has been some work in building a testbed
over ethernet. 
This one deals with similar stuff to what you
guys are trying to do.
Zhang, Y., Li, W., “An Integrated Environment for
Testing Mobile Ad-Hoc Networks,” Proceedings of
MOBIHOC ’02,

Obviously you'll be ignoring RF effects over ETHERNET
and we have found that this makes a HUGE difference.

Actually we already have a working version of DSR
on CLICK. Our current work is focused on developing
an energy aware version of DSR.
We have developed a testbed using attenuators. This
testbed emulates RF effects as well as a limited form
of mobility. Our entire design fits onto a single
table. Let me know if you guys want some more info.


Sagar Sanghani
University of Colorado
http://pecolab.colorado.edu


__________________________________________________
Do you Yahoo!?
HotJobs - Search new jobs daily now
http://hotjobs.yahoo.com/
_______________________________________________
manet mailing list
manet@ietf.org
https://www1.ietf.org/mailman/listinfo/manet


From mailnull@www1.ietf.org  Fri Nov  1 11:00:49 2002
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA18762
	for <manet-archive@odin.ietf.org>; Fri, 1 Nov 2002 11:00:49 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id gA1G2kx06721
	for manet-archive@odin.ietf.org; Fri, 1 Nov 2002 11:02:46 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gA1G2jv06718
	for <manet-web-archive@optimus.ietf.org>; Fri, 1 Nov 2002 11:02:45 -0500
Received: from www1.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA18727
	for <manet-web-archive@ietf.org>; Fri, 1 Nov 2002 11:00:18 -0500 (EST)
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gA1Ft4v03571;
	Fri, 1 Nov 2002 10:55:04 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gA1Fs1v03032
	for <manet@optimus.ietf.org>; Fri, 1 Nov 2002 10:54:01 -0500
Received: from web40506.mail.yahoo.com (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id KAA17945
	for <manet@ietf.org>; Fri, 1 Nov 2002 10:51:33 -0500 (EST)
Message-ID: <20021101155357.22052.qmail@web40506.mail.yahoo.com>
Received: from [128.138.86.144] by web40506.mail.yahoo.com via HTTP; Fri, 01 Nov 2002 07:53:57 PST
Date: Fri, 1 Nov 2002 07:53:57 -0800 (PST)
From: Sagar Sanghani <sanghani_s@yahoo.com>
To: manet@ietf.org
In-Reply-To: <20021031170003.12340.76608.Mailman@www1.ietf.org>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Subject: [manet] CISCO on iPAQ
Sender: manet-admin@ietf.org
Errors-To: manet-admin@ietf.org
X-BeenThere: manet@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/manet>,
	<mailto:manet-request@ietf.org?subject=unsubscribe>
List-Id: Mobile Ad-hoc Networks  <manet.ietf.org>
List-Post: <mailto:manet@ietf.org>
List-Help: <mailto:manet-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/manet>,
	<mailto:manet-request@ietf.org?subject=subscribe>


This is probably not the best place for this question.
But has anyone had any sucess in getting a CISCO 350
series card to work with an iPAQ running Linux?

Thanks in advance,
sagar

__________________________________________________
Do you Yahoo!?
HotJobs - Search new jobs daily now
http://hotjobs.yahoo.com/
_______________________________________________
manet mailing list
manet@ietf.org
https://www1.ietf.org/mailman/listinfo/manet



From manet-admin@ietf.org  Fri Nov  1 11:00:51 2002
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA18775
	for <manet-archive@lists.ietf.org>; Fri, 1 Nov 2002 11:00:51 -0500 (EST)
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gA1Ft4v03571;
	Fri, 1 Nov 2002 10:55:04 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gA1Fs1v03032
	for <manet@optimus.ietf.org>; Fri, 1 Nov 2002 10:54:01 -0500
Received: from web40506.mail.yahoo.com (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id KAA17945
	for <manet@ietf.org>; Fri, 1 Nov 2002 10:51:33 -0500 (EST)
Message-ID: <20021101155357.22052.qmail@web40506.mail.yahoo.com>
Received: from [128.138.86.144] by web40506.mail.yahoo.com via HTTP; Fri, 01 Nov 2002 07:53:57 PST
Date: Fri, 1 Nov 2002 07:53:57 -0800 (PST)
From: Sagar Sanghani <sanghani_s@yahoo.com>
To: manet@ietf.org
In-Reply-To: <20021031170003.12340.76608.Mailman@www1.ietf.org>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Subject: [manet] CISCO on iPAQ
Sender: manet-admin@ietf.org
Errors-To: manet-admin@ietf.org
X-BeenThere: manet@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/manet>,
	<mailto:manet-request@ietf.org?subject=unsubscribe>
List-Id: Mobile Ad-hoc Networks  <manet.ietf.org>
List-Post: <mailto:manet@ietf.org>
List-Help: <mailto:manet-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/manet>,
	<mailto:manet-request@ietf.org?subject=subscribe>


This is probably not the best place for this question.
But has anyone had any sucess in getting a CISCO 350
series card to work with an iPAQ running Linux?

Thanks in advance,
sagar

__________________________________________________
Do you Yahoo!?
HotJobs - Search new jobs daily now
http://hotjobs.yahoo.com/
_______________________________________________
manet mailing list
manet@ietf.org
https://www1.ietf.org/mailman/listinfo/manet


From mailnull@www1.ietf.org  Fri Nov  1 11:55:42 2002
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA22297
	for <manet-archive@odin.ietf.org>; Fri, 1 Nov 2002 11:55:42 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id gA1Gvdb27265
	for manet-archive@odin.ietf.org; Fri, 1 Nov 2002 11:57:39 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gA1Gvdv27262
	for <manet-web-archive@optimus.ietf.org>; Fri, 1 Nov 2002 11:57:39 -0500
Received: from www1.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA22258
	for <manet-web-archive@ietf.org>; Fri, 1 Nov 2002 11:55:11 -0500 (EST)
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gA1Gn1v24655;
	Fri, 1 Nov 2002 11:49:01 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gA1Gluv24193
	for <manet@optimus.ietf.org>; Fri, 1 Nov 2002 11:47:56 -0500
Received: from m1.cs.man.ac.uk (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA21614
	for <manet@ietf.org>; Fri, 1 Nov 2002 11:45:23 -0500 (EST)
Received: from eng001.cs.man.ac.uk by m1.cs.man.ac.uk (8.8.8/AL/MJK-2.0)
	id QAA22986; Fri, 1 Nov 2002 16:47:46 GMT
Received: (from tapselj0@localhost)
	by eng001.cs.man.ac.uk (8.11.6/8.9.3) id gA1Glj016877
	for manet@ietf.org; Fri, 1 Nov 2002 16:47:45 GMT
Date: Fri, 1 Nov 2002 16:47:45 +0000
From: John Tapsell <tapselj0@cs.man.ac.uk>
To: manet@ietf.org
Subject: Re: [manet] CISCO on iPAQ
Message-ID: <20021101164745.I16296@eng001.cs.man.ac.uk>
References: <20021031170003.12340.76608.Mailman@www1.ietf.org> <20021101155357.22052.qmail@web40506.mail.yahoo.com>
Mime-Version: 1.0
Content-Type: multipart/signed; micalg=pgp-sha1;
	protocol="application/pgp-signature"; boundary="m0vRWufqUC70IDnR"
Content-Disposition: inline
User-Agent: Mutt/1.2.5.1i
In-Reply-To: <20021101155357.22052.qmail@web40506.mail.yahoo.com>; from sanghani_s@yahoo.com on Fri, Nov 01, 2002 at 07:53:57AM -0800
Sender: manet-admin@ietf.org
Errors-To: manet-admin@ietf.org
X-BeenThere: manet@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/manet>,
	<mailto:manet-request@ietf.org?subject=unsubscribe>
List-Id: Mobile Ad-hoc Networks  <manet.ietf.org>
List-Post: <mailto:manet@ietf.org>
List-Help: <mailto:manet-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/manet>,
	<mailto:manet-request@ietf.org?subject=subscribe>


--m0vRWufqUC70IDnR
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable

On Fri, Nov 01, 2002 at 07:53:57AM -0800, Sagar Sanghani wrote:
>=20
> This is probably not the best place for this question.
> But has anyone had any sucess in getting a CISCO 350
> series card to work with an iPAQ running Linux?

This list isn't the best place to ask probably..

You can get various cases for the ipaq to allow you to plug pcmcia cards
into an ipaq, however it will eat your batteries, and make the ipaq bigger.

The way that I am going to do it is to use a old Compaq Concerto
(sorta like a laptop, but uses a magnetic pen for the mouse and has a
detachable keyboard) and add a bluetooth card and a wireless card in that.

Then the ipaq can use its built in bluetooth (assuming you have built in
bluetooth) to talk to the compaq at a distance of 10m or so (i.e. snug in
my backback) and the compaq just forwards the packets back and forth thru
the wireless card.

Better take this off the list tho if you have any more questions.

JohnFlux

=20
> Thanks in advance,
> sagar
>=20

--m0vRWufqUC70IDnR
Content-Type: application/pgp-signature
Content-Disposition: inline

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.0.6 (GNU/Linux)
Comment: For info see http://www.gnupg.org

iD8DBQE9wrAxoRvfZQkd7qoRArdmAJ42O3wr2+7toreEvq4SqtrKbaooHACdFL5M
jDutjwagIDnAZBwwSHhOq7g=
=6TrZ
-----END PGP SIGNATURE-----

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



From manet-admin@ietf.org  Fri Nov  1 11:55:44 2002
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA22311
	for <manet-archive@lists.ietf.org>; Fri, 1 Nov 2002 11:55:44 -0500 (EST)
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gA1Gn1v24655;
	Fri, 1 Nov 2002 11:49:01 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gA1Gluv24193
	for <manet@optimus.ietf.org>; Fri, 1 Nov 2002 11:47:56 -0500
Received: from m1.cs.man.ac.uk (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA21614
	for <manet@ietf.org>; Fri, 1 Nov 2002 11:45:23 -0500 (EST)
Received: from eng001.cs.man.ac.uk by m1.cs.man.ac.uk (8.8.8/AL/MJK-2.0)
	id QAA22986; Fri, 1 Nov 2002 16:47:46 GMT
Received: (from tapselj0@localhost)
	by eng001.cs.man.ac.uk (8.11.6/8.9.3) id gA1Glj016877
	for manet@ietf.org; Fri, 1 Nov 2002 16:47:45 GMT
Date: Fri, 1 Nov 2002 16:47:45 +0000
From: John Tapsell <tapselj0@cs.man.ac.uk>
To: manet@ietf.org
Subject: Re: [manet] CISCO on iPAQ
Message-ID: <20021101164745.I16296@eng001.cs.man.ac.uk>
References: <20021031170003.12340.76608.Mailman@www1.ietf.org> <20021101155357.22052.qmail@web40506.mail.yahoo.com>
Mime-Version: 1.0
Content-Type: multipart/signed; micalg=pgp-sha1;
	protocol="application/pgp-signature"; boundary="m0vRWufqUC70IDnR"
Content-Disposition: inline
User-Agent: Mutt/1.2.5.1i
In-Reply-To: <20021101155357.22052.qmail@web40506.mail.yahoo.com>; from sanghani_s@yahoo.com on Fri, Nov 01, 2002 at 07:53:57AM -0800
Sender: manet-admin@ietf.org
Errors-To: manet-admin@ietf.org
X-BeenThere: manet@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/manet>,
	<mailto:manet-request@ietf.org?subject=unsubscribe>
List-Id: Mobile Ad-hoc Networks  <manet.ietf.org>
List-Post: <mailto:manet@ietf.org>
List-Help: <mailto:manet-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/manet>,
	<mailto:manet-request@ietf.org?subject=subscribe>


--m0vRWufqUC70IDnR
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable

On Fri, Nov 01, 2002 at 07:53:57AM -0800, Sagar Sanghani wrote:
>=20
> This is probably not the best place for this question.
> But has anyone had any sucess in getting a CISCO 350
> series card to work with an iPAQ running Linux?

This list isn't the best place to ask probably..

You can get various cases for the ipaq to allow you to plug pcmcia cards
into an ipaq, however it will eat your batteries, and make the ipaq bigger.

The way that I am going to do it is to use a old Compaq Concerto
(sorta like a laptop, but uses a magnetic pen for the mouse and has a
detachable keyboard) and add a bluetooth card and a wireless card in that.

Then the ipaq can use its built in bluetooth (assuming you have built in
bluetooth) to talk to the compaq at a distance of 10m or so (i.e. snug in
my backback) and the compaq just forwards the packets back and forth thru
the wireless card.

Better take this off the list tho if you have any more questions.

JohnFlux

=20
> Thanks in advance,
> sagar
>=20

--m0vRWufqUC70IDnR
Content-Type: application/pgp-signature
Content-Disposition: inline

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.0.6 (GNU/Linux)
Comment: For info see http://www.gnupg.org

iD8DBQE9wrAxoRvfZQkd7qoRArdmAJ42O3wr2+7toreEvq4SqtrKbaooHACdFL5M
jDutjwagIDnAZBwwSHhOq7g=
=6TrZ
-----END PGP SIGNATURE-----

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


From mailnull@www1.ietf.org  Fri Nov  1 11:57:08 2002
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA22366
	for <manet-archive@odin.ietf.org>; Fri, 1 Nov 2002 11:57:08 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id gA1Gx6x27374
	for manet-archive@odin.ietf.org; Fri, 1 Nov 2002 11:59:06 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gA1Gx6v27371
	for <manet-web-archive@optimus.ietf.org>; Fri, 1 Nov 2002 11:59:06 -0500
Received: from www1.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA22343
	for <manet-web-archive@ietf.org>; Fri, 1 Nov 2002 11:56:37 -0500 (EST)
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gA1Gp7v25289;
	Fri, 1 Nov 2002 11:51:07 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gA1GoUv25238
	for <manet@optimus.ietf.org>; Fri, 1 Nov 2002 11:50:30 -0500
Received: from cheech.nmsu.edu (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA21728
	for <manet@ietf.org>; Fri, 1 Nov 2002 11:48:01 -0500 (EST)
From: jomullen@nmsu.edu
Received: (from nobody@localhost)
	by cheech.nmsu.edu (8.11.6/8.11.6) id gA1H3kF03200;
	Fri, 1 Nov 2002 10:03:46 -0700
Received: from 155.148.36.131 ( [155.148.36.131])
	as user jomullen@imap.nmsu.edu by webmail.nmsu.edu with HTTP;
	Fri,  1 Nov 2002 10:03:45 -0700
Message-ID: <1036170225.3dc2b3f1e9ed2@webmail.nmsu.edu>
Date: Fri,  1 Nov 2002 10:03:45 -0700
To: Sagar Sanghani <sanghani_s@yahoo.com>
Cc: manet@ietf.org
Subject: Re: [manet] Re: Testing DSR over ethernet
References: <20021101155123.51423.qmail@web40509.mail.yahoo.com>
In-Reply-To: <20021101155123.51423.qmail@web40509.mail.yahoo.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 8bit
User-Agent: Internet Messaging Program (IMP) 3.0
X-Originating-IP: 155.148.36.131
Content-Transfer-Encoding: 8bit
Sender: manet-admin@ietf.org
Errors-To: manet-admin@ietf.org
X-BeenThere: manet@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/manet>,
	<mailto:manet-request@ietf.org?subject=unsubscribe>
List-Id: Mobile Ad-hoc Networks  <manet.ietf.org>
List-Post: <mailto:manet@ietf.org>
List-Help: <mailto:manet-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/manet>,
	<mailto:manet-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 8bit
Content-Transfer-Encoding: 8bit

Hi Sagar,

This sounds interesting.  I would like to hear more details.

Thanks,

John Mullen

Quoting Sagar Sanghani <sanghani_s@yahoo.com>:

> 
> <snip>
>
> We have developed a testbed using attenuators. This
> testbed emulates RF effects as well as a limited form
> of mobility. Our entire design fits onto a single
> table. Let me know if you guys want some more info.
> 
> 
> Sagar Sanghani
> University of Colorado
> http://pecolab.colorado.edu
> 
> 
> __________________________________________________
> Do you Yahoo!?
> HotJobs - Search new jobs daily now
> http://hotjobs.yahoo.com/
> _______________________________________________
> manet mailing list
> manet@ietf.org
> https://www1.ietf.org/mailman/listinfo/manet
> 


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



From manet-admin@ietf.org  Fri Nov  1 11:57:11 2002
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA22387
	for <manet-archive@lists.ietf.org>; Fri, 1 Nov 2002 11:57:11 -0500 (EST)
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gA1Gp7v25289;
	Fri, 1 Nov 2002 11:51:07 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gA1GoUv25238
	for <manet@optimus.ietf.org>; Fri, 1 Nov 2002 11:50:30 -0500
Received: from cheech.nmsu.edu (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA21728
	for <manet@ietf.org>; Fri, 1 Nov 2002 11:48:01 -0500 (EST)
From: jomullen@nmsu.edu
Received: (from nobody@localhost)
	by cheech.nmsu.edu (8.11.6/8.11.6) id gA1H3kF03200;
	Fri, 1 Nov 2002 10:03:46 -0700
Received: from 155.148.36.131 ( [155.148.36.131])
	as user jomullen@imap.nmsu.edu by webmail.nmsu.edu with HTTP;
	Fri,  1 Nov 2002 10:03:45 -0700
Message-ID: <1036170225.3dc2b3f1e9ed2@webmail.nmsu.edu>
Date: Fri,  1 Nov 2002 10:03:45 -0700
To: Sagar Sanghani <sanghani_s@yahoo.com>
Cc: manet@ietf.org
Subject: Re: [manet] Re: Testing DSR over ethernet
References: <20021101155123.51423.qmail@web40509.mail.yahoo.com>
In-Reply-To: <20021101155123.51423.qmail@web40509.mail.yahoo.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 8bit
User-Agent: Internet Messaging Program (IMP) 3.0
X-Originating-IP: 155.148.36.131
Content-Transfer-Encoding: 8bit
Sender: manet-admin@ietf.org
Errors-To: manet-admin@ietf.org
X-BeenThere: manet@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/manet>,
	<mailto:manet-request@ietf.org?subject=unsubscribe>
List-Id: Mobile Ad-hoc Networks  <manet.ietf.org>
List-Post: <mailto:manet@ietf.org>
List-Help: <mailto:manet-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/manet>,
	<mailto:manet-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 8bit

Hi Sagar,

This sounds interesting.  I would like to hear more details.

Thanks,

John Mullen

Quoting Sagar Sanghani <sanghani_s@yahoo.com>:

> 
> <snip>
>
> We have developed a testbed using attenuators. This
> testbed emulates RF effects as well as a limited form
> of mobility. Our entire design fits onto a single
> table. Let me know if you guys want some more info.
> 
> 
> Sagar Sanghani
> University of Colorado
> http://pecolab.colorado.edu
> 
> 
> __________________________________________________
> Do you Yahoo!?
> HotJobs - Search new jobs daily now
> http://hotjobs.yahoo.com/
> _______________________________________________
> manet mailing list
> manet@ietf.org
> https://www1.ietf.org/mailman/listinfo/manet
> 


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


From mailnull@www1.ietf.org  Fri Nov  1 13:04:41 2002
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA26338
	for <manet-archive@odin.ietf.org>; Fri, 1 Nov 2002 13:04:41 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id gA1I6ep19627
	for manet-archive@odin.ietf.org; Fri, 1 Nov 2002 13:06:40 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gA1I6dv19624
	for <manet-web-archive@optimus.ietf.org>; Fri, 1 Nov 2002 13:06:39 -0500
Received: from www1.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA26295
	for <manet-web-archive@ietf.org>; Fri, 1 Nov 2002 13:04:10 -0500 (EST)
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gA1Hw8v15185;
	Fri, 1 Nov 2002 12:58:08 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gA1HsNv12988
	for <manet@optimus.ietf.org>; Fri, 1 Nov 2002 12:54:23 -0500
Received: from sinai.grupotba (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA25399
	for <manet@ietf.org>; Fri, 1 Nov 2002 12:51:53 -0500 (EST)
Received: from megryan.tac ([10.10.1.3]) by sinai.grupotba with Microsoft SMTPSVC(5.0.2195.5329);
	 Fri, 1 Nov 2002 14:58:34 -0300
X-MimeOLE: Produced By Microsoft Exchange V6.0.6249.0
content-class: urn:content-classes:message
Subject: RE: [manet] MANET - List of routing protocols
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Date: Fri, 1 Nov 2002 14:58:33 -0300
Message-ID: <4E2143E0BD5FEF44A3A86524A005E803404615@megryan.tac>
Thread-Topic: [manet] MANET - List of routing protocols
Thread-Index: AcKBmSbMyy41m0qkQnOHTm0q4A3Z4wAP4F6w
From: "Raoni Timo de Castro" <raonit@trueaccess.com.br>
To: <manet@ietf.org>
X-OriginalArrivalTime: 01 Nov 2002 17:58:34.0013 (UTC) FILETIME=[4B873CD0:01C281D0]
Content-Transfer-Encoding: 8bit
X-MIME-Autoconverted: from quoted-printable to 8bit by www1.ietf.org id gA1HsNv12989
Sender: manet-admin@ietf.org
Errors-To: manet-admin@ietf.org
X-BeenThere: manet@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/manet>,
	<mailto:manet-request@ietf.org?subject=unsubscribe>
List-Id: Mobile Ad-hoc Networks  <manet.ietf.org>
List-Post: <mailto:manet@ietf.org>
List-Help: <mailto:manet-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/manet>,
	<mailto:manet-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 8bit
Content-Transfer-Encoding: 8bit

Hello Everyone,

I'd like to use this subject to ask another question. Does anybody know which of these routing protocols are available in ns-2 for simulation of a mobile ad hoc network? I know that AODV, DSR, TORA, and DSDV were implemented by the monarch research project.

TIA,
Raoni Castro.

-----Original Message-----
From: David Lundberg [mailto:davidl@update.uu.se]
Sent: Friday, November 01, 2002 6:46 AM
To: manet@ietf.org
Subject: [manet] MANET - List of routing protocols



Hi all!

During the summer I published a list of the existing I had found on the
net and asked for comments. I got great response and added the changes to
my "little" list. Now I have realized that I won't have time to keep it
updated and thought that I should try to add it to one of these Wiki-sites
to let other interested people use/update it. Now I have published the
list along with the references I had. PSE have a look and feel free to
correct/change the list. I don't claim that I have sorted them correctly..
That could be something for people to discuss. :)

The list itself:

http://www.wikipedia.org/wiki/Ad_hoc_protocol_list

Short summary of implementations, pse add more:

http://www.wikipedia.org/wiki/Ad_hoc_protocols_implementations

Comments are as always very welcome!

Regards,

// David //


--------------------------------------------------------------
David Lundberg            Phone: Home(Uppsala)   +46-18-460356
Mail: davidl@update.uu.se        Home(Gävle)     +46-26-146743
Http: www.update.uu.se/~davidl   Cellular       +46-70-3531696
ICQ:  13440550                   IT-Dept. @ UU  +46-18-4716231
--------------------------------------------------------------



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



From manet-admin@ietf.org  Fri Nov  1 13:04:44 2002
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA26354
	for <manet-archive@lists.ietf.org>; Fri, 1 Nov 2002 13:04:43 -0500 (EST)
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gA1Hw8v15185;
	Fri, 1 Nov 2002 12:58:08 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gA1HsNv12988
	for <manet@optimus.ietf.org>; Fri, 1 Nov 2002 12:54:23 -0500
Received: from sinai.grupotba (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA25399
	for <manet@ietf.org>; Fri, 1 Nov 2002 12:51:53 -0500 (EST)
Received: from megryan.tac ([10.10.1.3]) by sinai.grupotba with Microsoft SMTPSVC(5.0.2195.5329);
	 Fri, 1 Nov 2002 14:58:34 -0300
X-MimeOLE: Produced By Microsoft Exchange V6.0.6249.0
content-class: urn:content-classes:message
Subject: RE: [manet] MANET - List of routing protocols
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Date: Fri, 1 Nov 2002 14:58:33 -0300
Message-ID: <4E2143E0BD5FEF44A3A86524A005E803404615@megryan.tac>
Thread-Topic: [manet] MANET - List of routing protocols
Thread-Index: AcKBmSbMyy41m0qkQnOHTm0q4A3Z4wAP4F6w
From: "Raoni Timo de Castro" <raonit@trueaccess.com.br>
To: <manet@ietf.org>
X-OriginalArrivalTime: 01 Nov 2002 17:58:34.0013 (UTC) FILETIME=[4B873CD0:01C281D0]
Content-Transfer-Encoding: 8bit
X-MIME-Autoconverted: from quoted-printable to 8bit by www1.ietf.org id gA1HsNv12989
Sender: manet-admin@ietf.org
Errors-To: manet-admin@ietf.org
X-BeenThere: manet@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/manet>,
	<mailto:manet-request@ietf.org?subject=unsubscribe>
List-Id: Mobile Ad-hoc Networks  <manet.ietf.org>
List-Post: <mailto:manet@ietf.org>
List-Help: <mailto:manet-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/manet>,
	<mailto:manet-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 8bit

Hello Everyone,

I'd like to use this subject to ask another question. Does anybody know which of these routing protocols are available in ns-2 for simulation of a mobile ad hoc network? I know that AODV, DSR, TORA, and DSDV were implemented by the monarch research project.

TIA,
Raoni Castro.

-----Original Message-----
From: David Lundberg [mailto:davidl@update.uu.se]
Sent: Friday, November 01, 2002 6:46 AM
To: manet@ietf.org
Subject: [manet] MANET - List of routing protocols



Hi all!

During the summer I published a list of the existing I had found on the
net and asked for comments. I got great response and added the changes to
my "little" list. Now I have realized that I won't have time to keep it
updated and thought that I should try to add it to one of these Wiki-sites
to let other interested people use/update it. Now I have published the
list along with the references I had. PSE have a look and feel free to
correct/change the list. I don't claim that I have sorted them correctly..
That could be something for people to discuss. :)

The list itself:

http://www.wikipedia.org/wiki/Ad_hoc_protocol_list

Short summary of implementations, pse add more:

http://www.wikipedia.org/wiki/Ad_hoc_protocols_implementations

Comments are as always very welcome!

Regards,

// David //


--------------------------------------------------------------
David Lundberg            Phone: Home(Uppsala)   +46-18-460356
Mail: davidl@update.uu.se        Home(Gävle)     +46-26-146743
Http: www.update.uu.se/~davidl   Cellular       +46-70-3531696
ICQ:  13440550                   IT-Dept. @ UU  +46-18-4716231
--------------------------------------------------------------



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


From manet-admin@ietf.org  Fri Nov  1 14:53:19 2002
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA01061
	for <manet-archive@lists.ietf.org>; Fri, 1 Nov 2002 14:53:18 -0500 (EST)
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gA1JkWv31774;
	Fri, 1 Nov 2002 14:46:32 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gA1JgQv31640
	for <manet@optimus.ietf.org>; Fri, 1 Nov 2002 14:42:26 -0500
Received: from memphis.ece.cornell.edu (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA00642
	for <manet@ietf.org>; Fri, 1 Nov 2002 14:39:55 -0500 (EST)
From: haas@ece.cornell.edu
Received: from verdi.ece.cornell.edu (verdi.ece.cornell.edu [128.84.210.27])
	by memphis.ece.cornell.edu (8.11.6/8.11.2) with ESMTP id gA1JgI524426;
	Fri, 1 Nov 2002 14:42:19 -0500
Date: Fri, 1 Nov 2002 14:42:03 -0500 (EST)
To: Raoni Timo de Castro <raonit@trueaccess.com.br>
cc: manet@ietf.org
Subject: RE: [manet] MANET - List of routing protocols
In-Reply-To: <4E2143E0BD5FEF44A3A86524A005E803404615@megryan.tac>
Message-ID: <Pine.GSO.4.05.10211011439450.19974-100000@verdi.ece.cornell.edu>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=X-UNKNOWN
Content-Transfer-Encoding: 8bit
X-MIME-Autoconverted: from QUOTED-PRINTABLE to 8bit by www1.ietf.org id gA1JgRv31641
Sender: manet-admin@ietf.org
Errors-To: manet-admin@ietf.org
X-BeenThere: manet@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/manet>,
	<mailto:manet-request@ietf.org?subject=unsubscribe>
List-Id: Mobile Ad-hoc Networks  <manet.ietf.org>
List-Post: <mailto:manet@ietf.org>
List-Help: <mailto:manet-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/manet>,
	<mailto:manet-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 8bit

Hi Raoni,

Can't speak for the rest, but we have just recently revised our NS2
implementation and it is ready for distribution.

We also have OPNET implementation as well.

Ciao,

Zygmunt.
==-=-=-=-==
~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-
Prof. Zygmunt J. Haas                    http://people.ece.cornell.edu/haas 
Wireless Networks Laboratory		 http://wnl.ece.cornell.edu
School of Electrical Engineering         
Cornell University			 tel: +1-607-255-3454
323 Frank Rhodes Hall			 fax: +1-607-255-9072
Ithaca, NY 14853			 e-mail: haas@ece.cornell.edu
U.S.A                             
	WNL web page: http://wnl.ece.cornell.edu
~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-

On Fri, 1 Nov 2002, Raoni Timo de Castro wrote:

> Hello Everyone,
> 
> I'd like to use this subject to ask another question. Does anybody know which of these routing protocols are available in ns-2 for simulation of a mobile ad hoc network? I know that AODV, DSR, TORA, and DSDV were implemented by the monarch research project.
> 
> TIA,
> Raoni Castro.
> 
> -----Original Message-----
> From: David Lundberg [mailto:davidl@update.uu.se]
> Sent: Friday, November 01, 2002 6:46 AM
> To: manet@ietf.org
> Subject: [manet] MANET - List of routing protocols
> 
> 
> 
> Hi all!
> 
> During the summer I published a list of the existing I had found on the
> net and asked for comments. I got great response and added the changes to
> my "little" list. Now I have realized that I won't have time to keep it
> updated and thought that I should try to add it to one of these Wiki-sites
> to let other interested people use/update it. Now I have published the
> list along with the references I had. PSE have a look and feel free to
> correct/change the list. I don't claim that I have sorted them correctly..
> That could be something for people to discuss. :)
> 
> The list itself:
> 
> http://www.wikipedia.org/wiki/Ad_hoc_protocol_list
> 
> Short summary of implementations, pse add more:
> 
> http://www.wikipedia.org/wiki/Ad_hoc_protocols_implementations
> 
> Comments are as always very welcome!
> 
> Regards,
> 
> // David //
> 
> 
> --------------------------------------------------------------
> David Lundberg            Phone: Home(Uppsala)   +46-18-460356
> Mail: davidl@update.uu.se        Home(Gävle)     +46-26-146743
> Http: www.update.uu.se/~davidl   Cellular       +46-70-3531696
> ICQ:  13440550                   IT-Dept. @ UU  +46-18-4716231
> --------------------------------------------------------------
> 
> 
> 
> _______________________________________________
> manet mailing list
> manet@ietf.org
> https://www1.ietf.org/mailman/listinfo/manet
> _______________________________________________
> manet mailing list
> manet@ietf.org
> https://www1.ietf.org/mailman/listinfo/manet
> 


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


From mailnull@www1.ietf.org  Fri Nov  1 14:56:23 2002
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA01131
	for <manet-archive@odin.ietf.org>; Fri, 1 Nov 2002 14:56:23 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id gA1JwNU32201
	for manet-archive@odin.ietf.org; Fri, 1 Nov 2002 14:58:23 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gA1JwNv32198
	for <manet-web-archive@optimus.ietf.org>; Fri, 1 Nov 2002 14:58:23 -0500
Received: from www1.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA01122
	for <manet-web-archive@ietf.org>; Fri, 1 Nov 2002 14:55:52 -0500 (EST)
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gA1JkWv31774;
	Fri, 1 Nov 2002 14:46:32 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gA1JgQv31640
	for <manet@optimus.ietf.org>; Fri, 1 Nov 2002 14:42:26 -0500
Received: from memphis.ece.cornell.edu (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA00642
	for <manet@ietf.org>; Fri, 1 Nov 2002 14:39:55 -0500 (EST)
From: haas@ece.cornell.edu
Received: from verdi.ece.cornell.edu (verdi.ece.cornell.edu [128.84.210.27])
	by memphis.ece.cornell.edu (8.11.6/8.11.2) with ESMTP id gA1JgI524426;
	Fri, 1 Nov 2002 14:42:19 -0500
Date: Fri, 1 Nov 2002 14:42:03 -0500 (EST)
To: Raoni Timo de Castro <raonit@trueaccess.com.br>
cc: manet@ietf.org
Subject: RE: [manet] MANET - List of routing protocols
In-Reply-To: <4E2143E0BD5FEF44A3A86524A005E803404615@megryan.tac>
Message-ID: <Pine.GSO.4.05.10211011439450.19974-100000@verdi.ece.cornell.edu>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=X-UNKNOWN
Content-Transfer-Encoding: 8bit
X-MIME-Autoconverted: from QUOTED-PRINTABLE to 8bit by www1.ietf.org id gA1JgRv31641
Sender: manet-admin@ietf.org
Errors-To: manet-admin@ietf.org
X-BeenThere: manet@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/manet>,
	<mailto:manet-request@ietf.org?subject=unsubscribe>
List-Id: Mobile Ad-hoc Networks  <manet.ietf.org>
List-Post: <mailto:manet@ietf.org>
List-Help: <mailto:manet-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/manet>,
	<mailto:manet-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 8bit
Content-Transfer-Encoding: 8bit

Hi Raoni,

Can't speak for the rest, but we have just recently revised our NS2
implementation and it is ready for distribution.

We also have OPNET implementation as well.

Ciao,

Zygmunt.
==-=-=-=-==
~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-
Prof. Zygmunt J. Haas                    http://people.ece.cornell.edu/haas 
Wireless Networks Laboratory		 http://wnl.ece.cornell.edu
School of Electrical Engineering         
Cornell University			 tel: +1-607-255-3454
323 Frank Rhodes Hall			 fax: +1-607-255-9072
Ithaca, NY 14853			 e-mail: haas@ece.cornell.edu
U.S.A                             
	WNL web page: http://wnl.ece.cornell.edu
~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-

On Fri, 1 Nov 2002, Raoni Timo de Castro wrote:

> Hello Everyone,
> 
> I'd like to use this subject to ask another question. Does anybody know which of these routing protocols are available in ns-2 for simulation of a mobile ad hoc network? I know that AODV, DSR, TORA, and DSDV were implemented by the monarch research project.
> 
> TIA,
> Raoni Castro.
> 
> -----Original Message-----
> From: David Lundberg [mailto:davidl@update.uu.se]
> Sent: Friday, November 01, 2002 6:46 AM
> To: manet@ietf.org
> Subject: [manet] MANET - List of routing protocols
> 
> 
> 
> Hi all!
> 
> During the summer I published a list of the existing I had found on the
> net and asked for comments. I got great response and added the changes to
> my "little" list. Now I have realized that I won't have time to keep it
> updated and thought that I should try to add it to one of these Wiki-sites
> to let other interested people use/update it. Now I have published the
> list along with the references I had. PSE have a look and feel free to
> correct/change the list. I don't claim that I have sorted them correctly..
> That could be something for people to discuss. :)
> 
> The list itself:
> 
> http://www.wikipedia.org/wiki/Ad_hoc_protocol_list
> 
> Short summary of implementations, pse add more:
> 
> http://www.wikipedia.org/wiki/Ad_hoc_protocols_implementations
> 
> Comments are as always very welcome!
> 
> Regards,
> 
> // David //
> 
> 
> --------------------------------------------------------------
> David Lundberg            Phone: Home(Uppsala)   +46-18-460356
> Mail: davidl@update.uu.se        Home(Gävle)     +46-26-146743
> Http: www.update.uu.se/~davidl   Cellular       +46-70-3531696
> ICQ:  13440550                   IT-Dept. @ UU  +46-18-4716231
> --------------------------------------------------------------
> 
> 
> 
> _______________________________________________
> manet mailing list
> manet@ietf.org
> https://www1.ietf.org/mailman/listinfo/manet
> _______________________________________________
> manet mailing list
> manet@ietf.org
> https://www1.ietf.org/mailman/listinfo/manet
> 


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



From mailnull@www1.ietf.org  Fri Nov  1 15:11:07 2002
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA02385
	for <manet-archive@odin.ietf.org>; Fri, 1 Nov 2002 15:11:07 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id gA1KD7A00978
	for manet-archive@odin.ietf.org; Fri, 1 Nov 2002 15:13:07 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gA1KD7v00975
	for <manet-web-archive@optimus.ietf.org>; Fri, 1 Nov 2002 15:13:07 -0500
Received: from www1.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA02370
	for <manet-web-archive@ietf.org>; Fri, 1 Nov 2002 15:10:36 -0500 (EST)
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gA1K5Tv32502;
	Fri, 1 Nov 2002 15:05:29 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gA1K2Gv32406
	for <manet@optimus.ietf.org>; Fri, 1 Nov 2002 15:02:16 -0500
Received: from sj-msg-core-1.cisco.com (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA01224
	for <manet@ietf.org>; Fri, 1 Nov 2002 14:59:44 -0500 (EST)
Received: from sharahma-ultra.cisco.com (sharahma-ultra.cisco.com [171.69.58.239])
	by sj-msg-core-1.cisco.com (8.12.2/8.12.2) with ESMTP id gA1K23PQ008354;
	Fri, 1 Nov 2002 12:02:04 -0800 (PST)
Date: Fri, 1 Nov 2002 12:02:12 -0800 (PST)
From: Shahriar Rahman <sharahma@cisco.com>
To: haas@ece.cornell.edu
cc: Raoni Timo de Castro <raonit@trueaccess.com.br>, <manet@ietf.org>
Subject: RE: [manet] MANET - List of routing protocols
In-Reply-To: <Pine.GSO.4.05.10211011439450.19974-100000@verdi.ece.cornell.edu>
Message-ID: <Pine.GSO.4.44.0211011200470.965-100000@sharahma-ultra.cisco.com>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=iso-8859-1
Content-Transfer-Encoding: 8bit
X-MIME-Autoconverted: from QUOTED-PRINTABLE to 8bit by www1.ietf.org id gA1K2Gv32407
Sender: manet-admin@ietf.org
Errors-To: manet-admin@ietf.org
X-BeenThere: manet@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/manet>,
	<mailto:manet-request@ietf.org?subject=unsubscribe>
List-Id: Mobile Ad-hoc Networks  <manet.ietf.org>
List-Post: <mailto:manet@ietf.org>
List-Help: <mailto:manet-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/manet>,
	<mailto:manet-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 8bit
Content-Transfer-Encoding: 8bit


While on this thread, let me ask a further Q. Do you any of you have CGSR
implementation in either NS-2 or OPNET? Comparing these two, which one is
more straigthforward?

regards,
Shahriar

On Fri, 1 Nov 2002 haas@ece.cornell.edu wrote:

> Hi Raoni,
>
> Can't speak for the rest, but we have just recently revised our NS2
> implementation and it is ready for distribution.
>
> We also have OPNET implementation as well.
>
> Ciao,
>
> Zygmunt.
> ==-=-=-=-==
> ~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-
> Prof. Zygmunt J. Haas                    http://people.ece.cornell.edu/haas
> Wireless Networks Laboratory		 http://wnl.ece.cornell.edu
> School of Electrical Engineering
> Cornell University			 tel: +1-607-255-3454
> 323 Frank Rhodes Hall			 fax: +1-607-255-9072
> Ithaca, NY 14853			 e-mail: haas@ece.cornell.edu
> U.S.A
> 	WNL web page: http://wnl.ece.cornell.edu
> ~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-
>
> On Fri, 1 Nov 2002, Raoni Timo de Castro wrote:
>
> > Hello Everyone,
> >
> > I'd like to use this subject to ask another question. Does anybody know which of these routing protocols are available in ns-2 for simulation of a mobile ad hoc network? I know that AODV, DSR, TORA, and DSDV were implemented by the monarch research project.
> >
> > TIA,
> > Raoni Castro.
> >
> > -----Original Message-----
> > From: David Lundberg [mailto:davidl@update.uu.se]
> > Sent: Friday, November 01, 2002 6:46 AM
> > To: manet@ietf.org
> > Subject: [manet] MANET - List of routing protocols
> >
> >
> >
> > Hi all!
> >
> > During the summer I published a list of the existing I had found on the
> > net and asked for comments. I got great response and added the changes to
> > my "little" list. Now I have realized that I won't have time to keep it
> > updated and thought that I should try to add it to one of these Wiki-sites
> > to let other interested people use/update it. Now I have published the
> > list along with the references I had. PSE have a look and feel free to
> > correct/change the list. I don't claim that I have sorted them correctly..
> > That could be something for people to discuss. :)
> >
> > The list itself:
> >
> > http://www.wikipedia.org/wiki/Ad_hoc_protocol_list
> >
> > Short summary of implementations, pse add more:
> >
> > http://www.wikipedia.org/wiki/Ad_hoc_protocols_implementations
> >
> > Comments are as always very welcome!
> >
> > Regards,
> >
> > // David //
> >
> >
> > --------------------------------------------------------------
> > David Lundberg            Phone: Home(Uppsala)   +46-18-460356
> > Mail: davidl@update.uu.se        Home(Gävle)     +46-26-146743
> > Http: www.update.uu.se/~davidl   Cellular       +46-70-3531696
> > ICQ:  13440550                   IT-Dept. @ UU  +46-18-4716231
> > --------------------------------------------------------------
> >
> >
> >
> > _______________________________________________
> > manet mailing list
> > manet@ietf.org
> > https://www1.ietf.org/mailman/listinfo/manet
> > _______________________________________________
> > manet mailing list
> > manet@ietf.org
> > https://www1.ietf.org/mailman/listinfo/manet
> >
>
>
> _______________________________________________
> manet mailing list
> manet@ietf.org
> https://www1.ietf.org/mailman/listinfo/manet
>

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



From manet-admin@ietf.org  Fri Nov  1 15:11:09 2002
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA02398
	for <manet-archive@lists.ietf.org>; Fri, 1 Nov 2002 15:11:09 -0500 (EST)
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gA1K5Tv32502;
	Fri, 1 Nov 2002 15:05:29 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gA1K2Gv32406
	for <manet@optimus.ietf.org>; Fri, 1 Nov 2002 15:02:16 -0500
Received: from sj-msg-core-1.cisco.com (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA01224
	for <manet@ietf.org>; Fri, 1 Nov 2002 14:59:44 -0500 (EST)
Received: from sharahma-ultra.cisco.com (sharahma-ultra.cisco.com [171.69.58.239])
	by sj-msg-core-1.cisco.com (8.12.2/8.12.2) with ESMTP id gA1K23PQ008354;
	Fri, 1 Nov 2002 12:02:04 -0800 (PST)
Date: Fri, 1 Nov 2002 12:02:12 -0800 (PST)
From: Shahriar Rahman <sharahma@cisco.com>
To: haas@ece.cornell.edu
cc: Raoni Timo de Castro <raonit@trueaccess.com.br>, <manet@ietf.org>
Subject: RE: [manet] MANET - List of routing protocols
In-Reply-To: <Pine.GSO.4.05.10211011439450.19974-100000@verdi.ece.cornell.edu>
Message-ID: <Pine.GSO.4.44.0211011200470.965-100000@sharahma-ultra.cisco.com>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=iso-8859-1
Content-Transfer-Encoding: 8bit
X-MIME-Autoconverted: from QUOTED-PRINTABLE to 8bit by www1.ietf.org id gA1K2Gv32407
Sender: manet-admin@ietf.org
Errors-To: manet-admin@ietf.org
X-BeenThere: manet@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/manet>,
	<mailto:manet-request@ietf.org?subject=unsubscribe>
List-Id: Mobile Ad-hoc Networks  <manet.ietf.org>
List-Post: <mailto:manet@ietf.org>
List-Help: <mailto:manet-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/manet>,
	<mailto:manet-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 8bit


While on this thread, let me ask a further Q. Do you any of you have CGSR
implementation in either NS-2 or OPNET? Comparing these two, which one is
more straigthforward?

regards,
Shahriar

On Fri, 1 Nov 2002 haas@ece.cornell.edu wrote:

> Hi Raoni,
>
> Can't speak for the rest, but we have just recently revised our NS2
> implementation and it is ready for distribution.
>
> We also have OPNET implementation as well.
>
> Ciao,
>
> Zygmunt.
> ==-=-=-=-==
> ~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-
> Prof. Zygmunt J. Haas                    http://people.ece.cornell.edu/haas
> Wireless Networks Laboratory		 http://wnl.ece.cornell.edu
> School of Electrical Engineering
> Cornell University			 tel: +1-607-255-3454
> 323 Frank Rhodes Hall			 fax: +1-607-255-9072
> Ithaca, NY 14853			 e-mail: haas@ece.cornell.edu
> U.S.A
> 	WNL web page: http://wnl.ece.cornell.edu
> ~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-
>
> On Fri, 1 Nov 2002, Raoni Timo de Castro wrote:
>
> > Hello Everyone,
> >
> > I'd like to use this subject to ask another question. Does anybody know which of these routing protocols are available in ns-2 for simulation of a mobile ad hoc network? I know that AODV, DSR, TORA, and DSDV were implemented by the monarch research project.
> >
> > TIA,
> > Raoni Castro.
> >
> > -----Original Message-----
> > From: David Lundberg [mailto:davidl@update.uu.se]
> > Sent: Friday, November 01, 2002 6:46 AM
> > To: manet@ietf.org
> > Subject: [manet] MANET - List of routing protocols
> >
> >
> >
> > Hi all!
> >
> > During the summer I published a list of the existing I had found on the
> > net and asked for comments. I got great response and added the changes to
> > my "little" list. Now I have realized that I won't have time to keep it
> > updated and thought that I should try to add it to one of these Wiki-sites
> > to let other interested people use/update it. Now I have published the
> > list along with the references I had. PSE have a look and feel free to
> > correct/change the list. I don't claim that I have sorted them correctly..
> > That could be something for people to discuss. :)
> >
> > The list itself:
> >
> > http://www.wikipedia.org/wiki/Ad_hoc_protocol_list
> >
> > Short summary of implementations, pse add more:
> >
> > http://www.wikipedia.org/wiki/Ad_hoc_protocols_implementations
> >
> > Comments are as always very welcome!
> >
> > Regards,
> >
> > // David //
> >
> >
> > --------------------------------------------------------------
> > David Lundberg            Phone: Home(Uppsala)   +46-18-460356
> > Mail: davidl@update.uu.se        Home(Gävle)     +46-26-146743
> > Http: www.update.uu.se/~davidl   Cellular       +46-70-3531696
> > ICQ:  13440550                   IT-Dept. @ UU  +46-18-4716231
> > --------------------------------------------------------------
> >
> >
> >
> > _______________________________________________
> > manet mailing list
> > manet@ietf.org
> > https://www1.ietf.org/mailman/listinfo/manet
> > _______________________________________________
> > manet mailing list
> > manet@ietf.org
> > https://www1.ietf.org/mailman/listinfo/manet
> >
>
>
> _______________________________________________
> manet mailing list
> manet@ietf.org
> https://www1.ietf.org/mailman/listinfo/manet
>

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


From manet-admin@ietf.org  Fri Nov  1 17:00:29 2002
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA06092
	for <manet-archive@lists.ietf.org>; Fri, 1 Nov 2002 17:00:29 -0500 (EST)
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gA1LsQv06701;
	Fri, 1 Nov 2002 16:54:26 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gA1Lq1v06615
	for <manet@optimus.ietf.org>; Fri, 1 Nov 2002 16:52:01 -0500
Received: from itd.nrl.navy.mil (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA05688
	for <manet@ietf.org>; Fri, 1 Nov 2002 16:49:30 -0500 (EST)
Received: from smtp.itd.nrl.navy.mil (smtp.itd.nrl.navy.mil [132.250.86.3])
	by itd.nrl.navy.mil (8.8.8+Sun/8.8.8) with SMTP id QAA25957;
	Fri, 1 Nov 2002 16:48:34 -0500 (EST)
Received: from SEXTANT.itd.nrl.navy.mil ([132.250.92.22])
 by smtp.itd.nrl.navy.mil (SAVSMTP 3.0.0.44) with SMTP id M2002110116483409289
 ; Fri, 01 Nov 2002 16:48:34 -0500
Message-Id: <5.1.1.5.2.20021101164408.032769d0@pop.itd.nrl.navy.mil>
X-Sender: macker@pop.itd.nrl.navy.mil
X-Mailer: QUALCOMM Windows Eudora Version 5.1.1
Date: Fri, 01 Nov 2002 16:48:26 -0500
To: Shahriar Rahman <sharahma@cisco.com>, haas@ece.cornell.edu
From: Joe Macker <macker@itd.nrl.navy.mil>
Subject: RE: [manet] MANET - List of routing protocols
Cc: Raoni Timo de Castro <raonit@trueaccess.com.br>, <manet@ietf.org>
In-Reply-To: <Pine.GSO.4.44.0211011200470.965-100000@sharahma-ultra.cisc
 o.com>
References: <Pine.GSO.4.05.10211011439450.19974-100000@verdi.ece.cornell.edu>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Sender: manet-admin@ietf.org
Errors-To: manet-admin@ietf.org
X-BeenThere: manet@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/manet>,
	<mailto:manet-request@ietf.org?subject=unsubscribe>
List-Id: Mobile Ad-hoc Networks  <manet.ietf.org>
List-Post: <mailto:manet@ietf.org>
List-Help: <mailto:manet-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/manet>,
	<mailto:manet-request@ietf.org?subject=subscribe>

At 12:02 PM 11/1/2002 -0800, Shahriar Rahman wrote:

>While on this thread, let me ask a further Q. Do you any of you have CGSR
>implementation in either NS-2 or OPNET? Comparing these two, which one is
>more straigthforward?

Let's keep list discussions related to manet IETF work.

wikipedia is freely editable by all so have at it!
If something is missing add it yourself.

This may be a better general method than the previously managed implementation page I was keeping for IETF manet protocols which is out-of-date.

-Joe


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


From mailnull@www1.ietf.org  Fri Nov  1 17:04:12 2002
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA06246
	for <manet-archive@odin.ietf.org>; Fri, 1 Nov 2002 17:04:12 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id gA1M6CT07649
	for manet-archive@odin.ietf.org; Fri, 1 Nov 2002 17:06:12 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gA1M6Cv07646
	for <manet-web-archive@optimus.ietf.org>; Fri, 1 Nov 2002 17:06:12 -0500
Received: from www1.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA06199
	for <manet-web-archive@ietf.org>; Fri, 1 Nov 2002 17:03:41 -0500 (EST)
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gA1LsQv06701;
	Fri, 1 Nov 2002 16:54:26 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gA1Lq1v06615
	for <manet@optimus.ietf.org>; Fri, 1 Nov 2002 16:52:01 -0500
Received: from itd.nrl.navy.mil (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA05688
	for <manet@ietf.org>; Fri, 1 Nov 2002 16:49:30 -0500 (EST)
Received: from smtp.itd.nrl.navy.mil (smtp.itd.nrl.navy.mil [132.250.86.3])
	by itd.nrl.navy.mil (8.8.8+Sun/8.8.8) with SMTP id QAA25957;
	Fri, 1 Nov 2002 16:48:34 -0500 (EST)
Received: from SEXTANT.itd.nrl.navy.mil ([132.250.92.22])
 by smtp.itd.nrl.navy.mil (SAVSMTP 3.0.0.44) with SMTP id M2002110116483409289
 ; Fri, 01 Nov 2002 16:48:34 -0500
Message-Id: <5.1.1.5.2.20021101164408.032769d0@pop.itd.nrl.navy.mil>
X-Sender: macker@pop.itd.nrl.navy.mil
X-Mailer: QUALCOMM Windows Eudora Version 5.1.1
Date: Fri, 01 Nov 2002 16:48:26 -0500
To: Shahriar Rahman <sharahma@cisco.com>, haas@ece.cornell.edu
From: Joe Macker <macker@itd.nrl.navy.mil>
Subject: RE: [manet] MANET - List of routing protocols
Cc: Raoni Timo de Castro <raonit@trueaccess.com.br>, <manet@ietf.org>
In-Reply-To: <Pine.GSO.4.44.0211011200470.965-100000@sharahma-ultra.cisc
 o.com>
References: <Pine.GSO.4.05.10211011439450.19974-100000@verdi.ece.cornell.edu>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Sender: manet-admin@ietf.org
Errors-To: manet-admin@ietf.org
X-BeenThere: manet@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/manet>,
	<mailto:manet-request@ietf.org?subject=unsubscribe>
List-Id: Mobile Ad-hoc Networks  <manet.ietf.org>
List-Post: <mailto:manet@ietf.org>
List-Help: <mailto:manet-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/manet>,
	<mailto:manet-request@ietf.org?subject=subscribe>

At 12:02 PM 11/1/2002 -0800, Shahriar Rahman wrote:

>While on this thread, let me ask a further Q. Do you any of you have CGSR
>implementation in either NS-2 or OPNET? Comparing these two, which one is
>more straigthforward?

Let's keep list discussions related to manet IETF work.

wikipedia is freely editable by all so have at it!
If something is missing add it yourself.

This may be a better general method than the previously managed implementation page I was keeping for IETF manet protocols which is out-of-date.

-Joe


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



From mailnull@www1.ietf.org  Fri Nov  1 19:54:48 2002
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA10662
	for <manet-archive@odin.ietf.org>; Fri, 1 Nov 2002 19:54:48 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id gA20uo317298
	for manet-archive@odin.ietf.org; Fri, 1 Nov 2002 19:56:50 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gA20uov17295
	for <manet-web-archive@optimus.ietf.org>; Fri, 1 Nov 2002 19:56:50 -0500
Received: from www1.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA10640
	for <manet-web-archive@ietf.org>; Fri, 1 Nov 2002 19:54:17 -0500 (EST)
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gA20nQv17021;
	Fri, 1 Nov 2002 19:49:26 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gA20l3v16969
	for <manet@optimus.ietf.org>; Fri, 1 Nov 2002 19:47:03 -0500
Received: from web11105.mail.yahoo.com (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id TAA10497
	for <manet@ietf.org>; Fri, 1 Nov 2002 19:44:30 -0500 (EST)
Message-ID: <20021102004655.31723.qmail@web11105.mail.yahoo.com>
Received: from [128.32.39.59] by web11105.mail.yahoo.com via HTTP; Fri, 01 Nov 2002 16:46:55 PST
Date: Fri, 1 Nov 2002 16:46:55 -0800 (PST)
From: Wei Wei <derekwei77@yahoo.com>
To: manet@ietf.org
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Subject: [manet] Building an Ad hoc experimental network using iPAQs.
Sender: manet-admin@ietf.org
Errors-To: manet-admin@ietf.org
X-BeenThere: manet@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/manet>,
	<mailto:manet-request@ietf.org?subject=unsubscribe>
List-Id: Mobile Ad-hoc Networks  <manet.ietf.org>
List-Post: <mailto:manet@ietf.org>
List-Help: <mailto:manet-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/manet>,
	<mailto:manet-request@ietf.org?subject=subscribe>

Hi, All,

I'm thinking about building an ad hoc experimental 
network using iPAQs running linux. I need to modify 
linux kernel so that I can test different routing 
protocols. Do you think this is a reasonable way 
to build an experimental ad hoc networks? I 
appreciate any suggestions from you.

Thanks,

Wei

__________________________________________________
Do you Yahoo!?
HotJobs - Search new jobs daily now
http://hotjobs.yahoo.com/
_______________________________________________
manet mailing list
manet@ietf.org
https://www1.ietf.org/mailman/listinfo/manet



From manet-admin@ietf.org  Fri Nov  1 19:54:50 2002
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA10675
	for <manet-archive@lists.ietf.org>; Fri, 1 Nov 2002 19:54:50 -0500 (EST)
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gA20nQv17021;
	Fri, 1 Nov 2002 19:49:26 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gA20l3v16969
	for <manet@optimus.ietf.org>; Fri, 1 Nov 2002 19:47:03 -0500
Received: from web11105.mail.yahoo.com (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id TAA10497
	for <manet@ietf.org>; Fri, 1 Nov 2002 19:44:30 -0500 (EST)
Message-ID: <20021102004655.31723.qmail@web11105.mail.yahoo.com>
Received: from [128.32.39.59] by web11105.mail.yahoo.com via HTTP; Fri, 01 Nov 2002 16:46:55 PST
Date: Fri, 1 Nov 2002 16:46:55 -0800 (PST)
From: Wei Wei <derekwei77@yahoo.com>
To: manet@ietf.org
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Subject: [manet] Building an Ad hoc experimental network using iPAQs.
Sender: manet-admin@ietf.org
Errors-To: manet-admin@ietf.org
X-BeenThere: manet@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/manet>,
	<mailto:manet-request@ietf.org?subject=unsubscribe>
List-Id: Mobile Ad-hoc Networks  <manet.ietf.org>
List-Post: <mailto:manet@ietf.org>
List-Help: <mailto:manet-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/manet>,
	<mailto:manet-request@ietf.org?subject=subscribe>

Hi, All,

I'm thinking about building an ad hoc experimental 
network using iPAQs running linux. I need to modify 
linux kernel so that I can test different routing 
protocols. Do you think this is a reasonable way 
to build an experimental ad hoc networks? I 
appreciate any suggestions from you.

Thanks,

Wei

__________________________________________________
Do you Yahoo!?
HotJobs - Search new jobs daily now
http://hotjobs.yahoo.com/
_______________________________________________
manet mailing list
manet@ietf.org
https://www1.ietf.org/mailman/listinfo/manet


From manet-admin@ietf.org  Fri Nov  1 20:30:25 2002
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id UAA11653
	for <manet-archive@lists.ietf.org>; Fri, 1 Nov 2002 20:30:25 -0500 (EST)
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gA21OYv19112;
	Fri, 1 Nov 2002 20:24:34 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gA21NWv19062
	for <manet@optimus.ietf.org>; Fri, 1 Nov 2002 20:23:32 -0500
Received: from psg.com (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id UAA11370
	for <manet@ietf.org>; Fri, 1 Nov 2002 20:20:59 -0500 (EST)
Received: from psg.com
	([147.28.0.62] helo=127.0.0.1 ident=zinin)
	by psg.com with esmtp (Exim 3.36 #2)
	id 187n0V-0002Bc-00; Fri, 01 Nov 2002 17:23:23 -0800
Date: Fri, 1 Nov 2002 17:23:11 -0800
From: Alex Zinin <zinin@psg.com>
X-Mailer: The Bat! (v1.51) Personal
Reply-To: Alex Zinin <zinin@psg.com>
X-Priority: 3 (Normal)
Message-ID: <15889338942.20021101172311@psg.com>
To: manet@ietf.org
CC: Vern Paxson <vern@icir.org>, Bill Fenner <fenner@research.att.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit
Subject: [manet] IMPORTANT: MANET WG Strategy
Sender: manet-admin@ietf.org
Errors-To: manet-admin@ietf.org
X-BeenThere: manet@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/manet>,
	<mailto:manet-request@ietf.org?subject=unsubscribe>
List-Id: Mobile Ad-hoc Networks  <manet.ietf.org>
List-Post: <mailto:manet@ietf.org>
List-Help: <mailto:manet-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/manet>,
	<mailto:manet-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 7bit

Folks-

 [AD hat on]

 For a long while the MANET WG has been struggling through a number of
 problems. After analyzing the situation, it appears that the main
 reason behind this is the fact that the WG was created and has been
 operating as a research type of group, producing multiple possible
 solutions for a very wide set of similar problems. At the time of
 creation, IETF was the only reasonable home for this sort of work,
 mainly because the IRTF was largely dysfunctional. However, the
 research nature of the WG did not work well in the IETF environment,
 where we would normally like members of the WGs to focus on a
 relatively narrow, well defined problem, and work closely together on
 the solution(s).

 This situation obviously needs to be resolved if we want the MANET WG
 to produce IETF standards track specification(s) for mobile ad hoc
 networks.

 After talking to the WG chairs and some people within the WG (I
 definitely couldn't have talked to all of you guys), I believe that
 the following plan should be executed to solve the problem.

 Goals:

  1. Convert the WG to operate in the engineering (IETF) mode
     and produce the IETF standard specification(s) for MANETs.
     This requires:
       o clear and focused problem statement
       o focused WG charter with clear milestones
       o WG members working closely together towards consensus

  2. For the work that will benefit from further research work,
     and would be affected by focusing the WG charter, if possible
     find a better home that will match the research nature of the
     work. Given that the IRTF has been brought back to real life and
     there's actually useful work happening within it, the IRTF would
     be the logical choice for this.

 Steps:

  1. A new Research Group (or a sub-group of the Routing RG) is created
     within the IRTF. The group will be the home for MANET research
     work. Since a longer, more research-oriented work is needed for
     extended salability mechanisms that LANMAR, FSR, ZRP, and TORA
     are attempting to provide, these protocols are relocated from the
     MANET WG to the IRTF, where they will benefit the research
     environment without the pressure of having to converge on a
     single protocol. As work in the IRTF matures, creation of IETF
     WGs maybe explored through the regular IETF BOF or WG
     rechartering procedures.

     /* The WG chairs are currently working with the IRTF chair
      * (I'm cc'ing Vern) on creating a forum for MANET research
      *  work.
      */

  2. The charter of the MANET WG is changed to complete the work
     on four protocols--DSR, AODV, OLSR, and TBRPF--and submit them
     for publication as Experimental to the IESG.

  3. When done with the Experimental documents, the WG transitions
     to the engineering mode with the first step of documenting the
     engineering problem statement describing the applicability
     aspects of the protocol to be designed, such as the type of ad
     hoc networks that need to be supported, number of nodes, level of
     mobility, etc. The scope of the problem is expected to be much
     narrower than the implicit problem statement that the current
     research activity is trying to cover. This step is required for
     the WG to continue its existence; the WG's potential will be
     reevaluated based on the produced problem statement and the
     charter will be updated accordingly.

  4. If consensus on the problem statement is reached, the WG (including
     the members of the current subgroups) will work together on the
     design of the IETF protocol(s) (either a single one with
     proactive and reactive modes, or one proactive, one reactive, for
     example; depending on what the WG decides is required) for ad hoc
     networks that will be progressed along the IETF standards tracks.
     Note that this protocol(s) will not be a recompilation of one of the
     four experimental protocols, but will be a true product of the
     engineering discussion within the WG, potentially incorporating
     features from all of them. Also note, that it will be an explicit
     non-goal for this IETF WG to choose and use the latest and
     greatest techniques that are currently being worked on or
     explored in the research community. Instead, the protocol(s) should
     be based on the mechanisms that the engineering community is most
     comfortable and has had sufficient experience with. Research work
     will continue happening in the IRTF.

 I had an opportunity to discuss this proposal with some of the WG
 members and the chairs and got considerable support. I am sending
 this message to understand the feeling of the wider WG community
 about the proposed strategy. I would also like us to discuss this in
 Atlanta before the decision is finalized. Scott, Joe, please allocate
 a time slot for this.

 Thank you.

Alex


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


From mailnull@www1.ietf.org  Fri Nov  1 20:36:40 2002
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id UAA11894
	for <manet-archive@odin.ietf.org>; Fri, 1 Nov 2002 20:36:40 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id gA21chJ20204
	for manet-archive@odin.ietf.org; Fri, 1 Nov 2002 20:38:43 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gA21chv20201
	for <manet-web-archive@optimus.ietf.org>; Fri, 1 Nov 2002 20:38:43 -0500
Received: from www1.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id UAA11884
	for <manet-web-archive@ietf.org>; Fri, 1 Nov 2002 20:36:08 -0500 (EST)
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gA21OYv19112;
	Fri, 1 Nov 2002 20:24:34 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gA21NWv19062
	for <manet@optimus.ietf.org>; Fri, 1 Nov 2002 20:23:32 -0500
Received: from psg.com (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id UAA11370
	for <manet@ietf.org>; Fri, 1 Nov 2002 20:20:59 -0500 (EST)
Received: from psg.com
	([147.28.0.62] helo=127.0.0.1 ident=zinin)
	by psg.com with esmtp (Exim 3.36 #2)
	id 187n0V-0002Bc-00; Fri, 01 Nov 2002 17:23:23 -0800
Date: Fri, 1 Nov 2002 17:23:11 -0800
From: Alex Zinin <zinin@psg.com>
X-Mailer: The Bat! (v1.51) Personal
Reply-To: Alex Zinin <zinin@psg.com>
X-Priority: 3 (Normal)
Message-ID: <15889338942.20021101172311@psg.com>
To: manet@ietf.org
CC: Vern Paxson <vern@icir.org>, Bill Fenner <fenner@research.att.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit
Subject: [manet] IMPORTANT: MANET WG Strategy
Sender: manet-admin@ietf.org
Errors-To: manet-admin@ietf.org
X-BeenThere: manet@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/manet>,
	<mailto:manet-request@ietf.org?subject=unsubscribe>
List-Id: Mobile Ad-hoc Networks  <manet.ietf.org>
List-Post: <mailto:manet@ietf.org>
List-Help: <mailto:manet-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/manet>,
	<mailto:manet-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit

Folks-

 [AD hat on]

 For a long while the MANET WG has been struggling through a number of
 problems. After analyzing the situation, it appears that the main
 reason behind this is the fact that the WG was created and has been
 operating as a research type of group, producing multiple possible
 solutions for a very wide set of similar problems. At the time of
 creation, IETF was the only reasonable home for this sort of work,
 mainly because the IRTF was largely dysfunctional. However, the
 research nature of the WG did not work well in the IETF environment,
 where we would normally like members of the WGs to focus on a
 relatively narrow, well defined problem, and work closely together on
 the solution(s).

 This situation obviously needs to be resolved if we want the MANET WG
 to produce IETF standards track specification(s) for mobile ad hoc
 networks.

 After talking to the WG chairs and some people within the WG (I
 definitely couldn't have talked to all of you guys), I believe that
 the following plan should be executed to solve the problem.

 Goals:

  1. Convert the WG to operate in the engineering (IETF) mode
     and produce the IETF standard specification(s) for MANETs.
     This requires:
       o clear and focused problem statement
       o focused WG charter with clear milestones
       o WG members working closely together towards consensus

  2. For the work that will benefit from further research work,
     and would be affected by focusing the WG charter, if possible
     find a better home that will match the research nature of the
     work. Given that the IRTF has been brought back to real life and
     there's actually useful work happening within it, the IRTF would
     be the logical choice for this.

 Steps:

  1. A new Research Group (or a sub-group of the Routing RG) is created
     within the IRTF. The group will be the home for MANET research
     work. Since a longer, more research-oriented work is needed for
     extended salability mechanisms that LANMAR, FSR, ZRP, and TORA
     are attempting to provide, these protocols are relocated from the
     MANET WG to the IRTF, where they will benefit the research
     environment without the pressure of having to converge on a
     single protocol. As work in the IRTF matures, creation of IETF
     WGs maybe explored through the regular IETF BOF or WG
     rechartering procedures.

     /* The WG chairs are currently working with the IRTF chair
      * (I'm cc'ing Vern) on creating a forum for MANET research
      *  work.
      */

  2. The charter of the MANET WG is changed to complete the work
     on four protocols--DSR, AODV, OLSR, and TBRPF--and submit them
     for publication as Experimental to the IESG.

  3. When done with the Experimental documents, the WG transitions
     to the engineering mode with the first step of documenting the
     engineering problem statement describing the applicability
     aspects of the protocol to be designed, such as the type of ad
     hoc networks that need to be supported, number of nodes, level of
     mobility, etc. The scope of the problem is expected to be much
     narrower than the implicit problem statement that the current
     research activity is trying to cover. This step is required for
     the WG to continue its existence; the WG's potential will be
     reevaluated based on the produced problem statement and the
     charter will be updated accordingly.

  4. If consensus on the problem statement is reached, the WG (including
     the members of the current subgroups) will work together on the
     design of the IETF protocol(s) (either a single one with
     proactive and reactive modes, or one proactive, one reactive, for
     example; depending on what the WG decides is required) for ad hoc
     networks that will be progressed along the IETF standards tracks.
     Note that this protocol(s) will not be a recompilation of one of the
     four experimental protocols, but will be a true product of the
     engineering discussion within the WG, potentially incorporating
     features from all of them. Also note, that it will be an explicit
     non-goal for this IETF WG to choose and use the latest and
     greatest techniques that are currently being worked on or
     explored in the research community. Instead, the protocol(s) should
     be based on the mechanisms that the engineering community is most
     comfortable and has had sufficient experience with. Research work
     will continue happening in the IRTF.

 I had an opportunity to discuss this proposal with some of the WG
 members and the chairs and got considerable support. I am sending
 this message to understand the feeling of the wider WG community
 about the proposed strategy. I would also like us to discuss this in
 Atlanta before the decision is finalized. Scott, Joe, please allocate
 a time slot for this.

 Thank you.

Alex


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



From mailnull@www1.ietf.org  Sat Nov  2 05:27:02 2002
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id FAA01490
	for <manet-archive@odin.ietf.org>; Sat, 2 Nov 2002 05:27:02 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id gA2ASu221625
	for manet-archive@odin.ietf.org; Sat, 2 Nov 2002 05:28:56 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gA2ASuv21622
	for <manet-web-archive@optimus.ietf.org>; Sat, 2 Nov 2002 05:28:56 -0500
Received: from www1.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id FAA01478
	for <manet-web-archive@ietf.org>; Sat, 2 Nov 2002 05:26:31 -0500 (EST)
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gA2ALUv21447;
	Sat, 2 Nov 2002 05:21:30 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gA2AHJv21325
	for <manet@optimus.ietf.org>; Sat, 2 Nov 2002 05:17:19 -0500
Received: from m1.cs.man.ac.uk (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id FAA01311
	for <manet@ietf.org>; Sat, 2 Nov 2002 05:14:53 -0500 (EST)
Received: from eng001.cs.man.ac.uk by m1.cs.man.ac.uk (8.8.8/AL/MJK-2.0)
	id KAA14827; Sat, 2 Nov 2002 10:17:12 GMT
Received: (from tapselj0@localhost)
	by eng001.cs.man.ac.uk (8.11.6/8.9.3) id gA2AGq722375
	for manet@ietf.org; Sat, 2 Nov 2002 10:16:52 GMT
Date: Sat, 2 Nov 2002 10:16:52 +0000
From: John Tapsell <tapselj0@cs.man.ac.uk>
To: manet@ietf.org
Message-ID: <20021102101652.A22365@eng001.cs.man.ac.uk>
Mime-Version: 1.0
Content-Type: multipart/signed; micalg=pgp-sha1;
	protocol="application/pgp-signature"; boundary="45Z9DzgjV8m4Oswq"
Content-Disposition: inline
User-Agent: Mutt/1.2.5.1i
Subject: [manet] Re: Building an Ad hoc experimental network using iPAQs.
Sender: manet-admin@ietf.org
Errors-To: manet-admin@ietf.org
X-BeenThere: manet@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/manet>,
	<mailto:manet-request@ietf.org?subject=unsubscribe>
List-Id: Mobile Ad-hoc Networks  <manet.ietf.org>
List-Post: <mailto:manet@ietf.org>
List-Help: <mailto:manet-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/manet>,
	<mailto:manet-request@ietf.org?subject=subscribe>


--45Z9DzgjV8m4Oswq
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable

You could use bluetooth to communicate between them.
That has the advantage of having a distance of only 10m, so you could play
about with moving them in and out of range of each other.

JohnFlux

--=20

--45Z9DzgjV8m4Oswq
Content-Type: application/pgp-signature
Content-Disposition: inline

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.0.6 (GNU/Linux)
Comment: For info see http://www.gnupg.org

iD8DBQE9w6YUoRvfZQkd7qoRAsk5AJ4+ToDQP3I3yVIBLynGsuEosLfbtwCcCm8I
270tBMZMEYL+3vQQUXowGjY=
=hded
-----END PGP SIGNATURE-----

--45Z9DzgjV8m4Oswq--
_______________________________________________
manet mailing list
manet@ietf.org
https://www1.ietf.org/mailman/listinfo/manet



From manet-admin@ietf.org  Sat Nov  2 05:27:05 2002
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id FAA01503
	for <manet-archive@lists.ietf.org>; Sat, 2 Nov 2002 05:27:05 -0500 (EST)
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gA2ALUv21447;
	Sat, 2 Nov 2002 05:21:30 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gA2AHJv21325
	for <manet@optimus.ietf.org>; Sat, 2 Nov 2002 05:17:19 -0500
Received: from m1.cs.man.ac.uk (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id FAA01311
	for <manet@ietf.org>; Sat, 2 Nov 2002 05:14:53 -0500 (EST)
Received: from eng001.cs.man.ac.uk by m1.cs.man.ac.uk (8.8.8/AL/MJK-2.0)
	id KAA14827; Sat, 2 Nov 2002 10:17:12 GMT
Received: (from tapselj0@localhost)
	by eng001.cs.man.ac.uk (8.11.6/8.9.3) id gA2AGq722375
	for manet@ietf.org; Sat, 2 Nov 2002 10:16:52 GMT
Date: Sat, 2 Nov 2002 10:16:52 +0000
From: John Tapsell <tapselj0@cs.man.ac.uk>
To: manet@ietf.org
Message-ID: <20021102101652.A22365@eng001.cs.man.ac.uk>
Mime-Version: 1.0
Content-Type: multipart/signed; micalg=pgp-sha1;
	protocol="application/pgp-signature"; boundary="45Z9DzgjV8m4Oswq"
Content-Disposition: inline
User-Agent: Mutt/1.2.5.1i
Subject: [manet] Re: Building an Ad hoc experimental network using iPAQs.
Sender: manet-admin@ietf.org
Errors-To: manet-admin@ietf.org
X-BeenThere: manet@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/manet>,
	<mailto:manet-request@ietf.org?subject=unsubscribe>
List-Id: Mobile Ad-hoc Networks  <manet.ietf.org>
List-Post: <mailto:manet@ietf.org>
List-Help: <mailto:manet-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/manet>,
	<mailto:manet-request@ietf.org?subject=subscribe>


--45Z9DzgjV8m4Oswq
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable

You could use bluetooth to communicate between them.
That has the advantage of having a distance of only 10m, so you could play
about with moving them in and out of range of each other.

JohnFlux

--=20

--45Z9DzgjV8m4Oswq
Content-Type: application/pgp-signature
Content-Disposition: inline

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.0.6 (GNU/Linux)
Comment: For info see http://www.gnupg.org

iD8DBQE9w6YUoRvfZQkd7qoRAsk5AJ4+ToDQP3I3yVIBLynGsuEosLfbtwCcCm8I
270tBMZMEYL+3vQQUXowGjY=
=hded
-----END PGP SIGNATURE-----

--45Z9DzgjV8m4Oswq--
_______________________________________________
manet mailing list
manet@ietf.org
https://www1.ietf.org/mailman/listinfo/manet


From manet-admin@ietf.org  Sat Nov  2 09:17:17 2002
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA05624
	for <manet-archive@lists.ietf.org>; Sat, 2 Nov 2002 09:17:17 -0500 (EST)
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gA2EB4v00428;
	Sat, 2 Nov 2002 09:11:04 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gA2E8nv00347
	for <manet@optimus.ietf.org>; Sat, 2 Nov 2002 09:08:49 -0500
Received: from cheviot1.ncl.ac.uk (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA05260
	for <manet@ietf.org>; Sat, 2 Nov 2002 09:06:20 -0500 (EST)
Received: from stavanger (msvpn2-3.ncl.ac.uk [128.240.230.3])
	by cheviot1.ncl.ac.uk (8.10.1/8.10.1) with ESMTP id gA2E8HC20123;
	Sat, 2 Nov 2002 14:08:17 GMT
From: "Einar Vollset" <einar.vollset@ncl.ac.uk>
To: <manet@ietf.org>
Cc: "'John Tapsell'" <tapselj0@cs.man.ac.uk>
Subject: RE: [manet] Re: Building an Ad hoc experimental network using iPAQs.
Date: Sat, 2 Nov 2002 14:07:59 -0000
Organization: University of Newcastle upon Tyne
Message-ID: <003101c28279$433cb1a0$6200a8c0@stavanger>
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: 7bit
X-Priority: 3 (Normal)
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook, Build 10.0.3416
In-Reply-To: <20021102101652.A22365@eng001.cs.man.ac.uk>
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2600.0000
Importance: Normal
X-Newcastle-MailScanner: Found to be clean (of known viruses)
Content-Transfer-Encoding: 7bit
Sender: manet-admin@ietf.org
Errors-To: manet-admin@ietf.org
X-BeenThere: manet@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/manet>,
	<mailto:manet-request@ietf.org?subject=unsubscribe>
List-Id: Mobile Ad-hoc Networks  <manet.ietf.org>
List-Post: <mailto:manet@ietf.org>
List-Help: <mailto:manet-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/manet>,
	<mailto:manet-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 7bit




> You could use bluetooth to communicate between them.

How well suited is Bluetooth to building MANET testbeds?
According to IBM's DEAPspace whitepaper, they didn't consider
Bluetooth very useful for their work (which involved rapid
service discovery, and not pure MANETs), because of the long
time taken to establish a new connection (they quoted up to
5 seconds (seems very long..)).
I have also heard other objections to using Bluetooth, something
to do with it being unsuitable for group communications such as
broadcast due to its inherent Master-Slave setup.

Anyone have any further insights into this?

Cheers,

Einar


----------------------------
Einar Vollset
PhD Student
School of Computing Science
University of Newcastle, UK
http://vollset.org
----------------------------

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


From mailnull@www1.ietf.org  Sat Nov  2 09:25:16 2002
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA05740
	for <manet-archive@odin.ietf.org>; Sat, 2 Nov 2002 09:25:15 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id gA2ERDU00881
	for manet-archive@odin.ietf.org; Sat, 2 Nov 2002 09:27:13 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gA2ERDv00878
	for <manet-web-archive@optimus.ietf.org>; Sat, 2 Nov 2002 09:27:13 -0500
Received: from www1.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA05731
	for <manet-web-archive@ietf.org>; Sat, 2 Nov 2002 09:24:44 -0500 (EST)
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gA2EB4v00428;
	Sat, 2 Nov 2002 09:11:04 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gA2E8nv00347
	for <manet@optimus.ietf.org>; Sat, 2 Nov 2002 09:08:49 -0500
Received: from cheviot1.ncl.ac.uk (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA05260
	for <manet@ietf.org>; Sat, 2 Nov 2002 09:06:20 -0500 (EST)
Received: from stavanger (msvpn2-3.ncl.ac.uk [128.240.230.3])
	by cheviot1.ncl.ac.uk (8.10.1/8.10.1) with ESMTP id gA2E8HC20123;
	Sat, 2 Nov 2002 14:08:17 GMT
From: "Einar Vollset" <einar.vollset@ncl.ac.uk>
To: <manet@ietf.org>
Cc: "'John Tapsell'" <tapselj0@cs.man.ac.uk>
Subject: RE: [manet] Re: Building an Ad hoc experimental network using iPAQs.
Date: Sat, 2 Nov 2002 14:07:59 -0000
Organization: University of Newcastle upon Tyne
Message-ID: <003101c28279$433cb1a0$6200a8c0@stavanger>
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: 7bit
X-Priority: 3 (Normal)
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook, Build 10.0.3416
In-Reply-To: <20021102101652.A22365@eng001.cs.man.ac.uk>
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2600.0000
Importance: Normal
X-Newcastle-MailScanner: Found to be clean (of known viruses)
Content-Transfer-Encoding: 7bit
Sender: manet-admin@ietf.org
Errors-To: manet-admin@ietf.org
X-BeenThere: manet@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/manet>,
	<mailto:manet-request@ietf.org?subject=unsubscribe>
List-Id: Mobile Ad-hoc Networks  <manet.ietf.org>
List-Post: <mailto:manet@ietf.org>
List-Help: <mailto:manet-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/manet>,
	<mailto:manet-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit




> You could use bluetooth to communicate between them.

How well suited is Bluetooth to building MANET testbeds?
According to IBM's DEAPspace whitepaper, they didn't consider
Bluetooth very useful for their work (which involved rapid
service discovery, and not pure MANETs), because of the long
time taken to establish a new connection (they quoted up to
5 seconds (seems very long..)).
I have also heard other objections to using Bluetooth, something
to do with it being unsuitable for group communications such as
broadcast due to its inherent Master-Slave setup.

Anyone have any further insights into this?

Cheers,

Einar


----------------------------
Einar Vollset
PhD Student
School of Computing Science
University of Newcastle, UK
http://vollset.org
----------------------------

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



From mailnull@www1.ietf.org  Sun Nov  3 00:48:28 2002
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id AAA20381
	for <manet-archive@odin.ietf.org>; Sun, 3 Nov 2002 00:48:28 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id gA35oXs13152
	for manet-archive@odin.ietf.org; Sun, 3 Nov 2002 00:50:33 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gA35oXv13149
	for <manet-web-archive@optimus.ietf.org>; Sun, 3 Nov 2002 00:50:33 -0500
Received: from www1.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id AAA20374
	for <manet-web-archive@ietf.org>; Sun, 3 Nov 2002 00:47:57 -0500 (EST)
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gA35gKv12898;
	Sun, 3 Nov 2002 00:42:20 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gA35cdv12778
	for <manet@optimus.ietf.org>; Sun, 3 Nov 2002 00:38:39 -0500
Received: from cse.uta.edu (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id AAA20240
	for <manet@ietf.org>; Sun, 3 Nov 2002 00:36:03 -0500 (EST)
Received: from localhost by cse.uta.edu (8.9.0/8.9.0) with SMTP id XAA08626
	for <manet@ietf.org>; Sat, 2 Nov 2002 23:40:26 -0600 (CST)
Date: Sat, 2 Nov 2002 23:40:25 -0600 (CST)
From: Kumaran Sambandan <sambanda@cse.uta.edu>
X-Sender: sambanda@cse
To: manet@ietf.org
Message-ID: <Pine.GSO.3.96.1021102233722.8585A-100000@cse>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Subject: [manet] Help regarding MAODV and ODRMP implementation
Sender: manet-admin@ietf.org
Errors-To: manet-admin@ietf.org
X-BeenThere: manet@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/manet>,
	<mailto:manet-request@ietf.org?subject=unsubscribe>
List-Id: Mobile Ad-hoc Networks  <manet.ietf.org>
List-Post: <mailto:manet@ietf.org>
List-Help: <mailto:manet-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/manet>,
	<mailto:manet-request@ietf.org?subject=subscribe>

	
Hi All,

Iam currently working on improving the performance of multicasting
protocols in ad hoc networks.It will be lot helpful if i could get the
implementation of these protocols in ns-2 or Glomosim or OPNET.

-Regards,
kumaran.

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



From manet-admin@ietf.org  Sun Nov  3 00:48:31 2002
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id AAA20394
	for <manet-archive@lists.ietf.org>; Sun, 3 Nov 2002 00:48:31 -0500 (EST)
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gA35gKv12898;
	Sun, 3 Nov 2002 00:42:20 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gA35cdv12778
	for <manet@optimus.ietf.org>; Sun, 3 Nov 2002 00:38:39 -0500
Received: from cse.uta.edu (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id AAA20240
	for <manet@ietf.org>; Sun, 3 Nov 2002 00:36:03 -0500 (EST)
Received: from localhost by cse.uta.edu (8.9.0/8.9.0) with SMTP id XAA08626
	for <manet@ietf.org>; Sat, 2 Nov 2002 23:40:26 -0600 (CST)
Date: Sat, 2 Nov 2002 23:40:25 -0600 (CST)
From: Kumaran Sambandan <sambanda@cse.uta.edu>
X-Sender: sambanda@cse
To: manet@ietf.org
Message-ID: <Pine.GSO.3.96.1021102233722.8585A-100000@cse>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Subject: [manet] Help regarding MAODV and ODRMP implementation
Sender: manet-admin@ietf.org
Errors-To: manet-admin@ietf.org
X-BeenThere: manet@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/manet>,
	<mailto:manet-request@ietf.org?subject=unsubscribe>
List-Id: Mobile Ad-hoc Networks  <manet.ietf.org>
List-Post: <mailto:manet@ietf.org>
List-Help: <mailto:manet-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/manet>,
	<mailto:manet-request@ietf.org?subject=subscribe>

	
Hi All,

Iam currently working on improving the performance of multicasting
protocols in ad hoc networks.It will be lot helpful if i could get the
implementation of these protocols in ns-2 or Glomosim or OPNET.

-Regards,
kumaran.

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


From manet-admin@ietf.org  Mon Nov  4 02:13:23 2002
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id CAA04832
	for <manet-archive@lists.ietf.org>; Mon, 4 Nov 2002 02:13:23 -0500 (EST)
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gA476bv32149;
	Mon, 4 Nov 2002 02:06:37 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gA46tBv30101
	for <manet@optimus.ietf.org>; Mon, 4 Nov 2002 01:55:11 -0500
Received: from patty.levels.unisa.edu.au (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id BAA24845;
	Mon, 4 Nov 2002 01:52:33 -0500 (EST)
Received: from sdingpc (sdingpc [172.17.0.113])
	by patty.levels.unisa.edu.au (8.12.2/8.12.2) with ESMTP id gA46svrK024921;
	Mon, 4 Nov 2002 17:24:57 +1030 (CST)
Message-Id: <200211040654.gA46svrK024921@patty.levels.unisa.edu.au>
Date: Mon, 4 Nov 2002 17:22:37 +0900
From: "S. Ding " <sding@spri.levels.unisa.edu.au>
To: "manet@ietf.org" <manet@ietf.org>
CC: "manet-request@ietf.org" <manet-request@ietf.org>
X-mailer: Foxmail 4.1 [cn]
Mime-Version: 1.0
Content-Type: text/plain;
      charset="GB2312"
Content-Transfer-Encoding: 8bit
X-MIME-Autoconverted: from quoted-printable to 8bit by www1.ietf.org id gA46tCv30104
Subject: [manet] help: The IPv6 model in OPNET or NS2
Sender: manet-admin@ietf.org
Errors-To: manet-admin@ietf.org
X-BeenThere: manet@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/manet>,
	<mailto:manet-request@ietf.org?subject=unsubscribe>
List-Id: Mobile Ad-hoc Networks  <manet.ietf.org>
List-Post: <mailto:manet@ietf.org>
List-Help: <mailto:manet-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/manet>,
	<mailto:manet-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 8bit

manet-request,

      Hello. The standard model library in OPNET doesn't include the IPv6 model. Does anybody know where can I download one?
Or in NS2.
   

				 
ˇˇˇˇˇˇˇˇˇˇˇˇˇˇˇˇS. Ding 
ˇˇˇˇˇˇˇˇˇˇˇˇˇˇˇˇsding@spri.levels.unisa.edu.au
ˇˇˇˇˇˇˇˇˇˇˇˇˇˇˇˇˇˇˇˇ2002-11-04



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


From mailnull@www1.ietf.org  Mon Nov  4 02:22:23 2002
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id CAA04955
	for <manet-archive@odin.ietf.org>; Mon, 4 Nov 2002 02:22:23 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id gA47OTj07754
	for manet-archive@odin.ietf.org; Mon, 4 Nov 2002 02:24:29 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gA47OTv07751
	for <manet-web-archive@optimus.ietf.org>; Mon, 4 Nov 2002 02:24:29 -0500
Received: from www1.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id CAA04951
	for <manet-web-archive@ietf.org>; Mon, 4 Nov 2002 02:21:52 -0500 (EST)
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gA476bv32149;
	Mon, 4 Nov 2002 02:06:37 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gA46tBv30101
	for <manet@optimus.ietf.org>; Mon, 4 Nov 2002 01:55:11 -0500
Received: from patty.levels.unisa.edu.au (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id BAA24845;
	Mon, 4 Nov 2002 01:52:33 -0500 (EST)
Received: from sdingpc (sdingpc [172.17.0.113])
	by patty.levels.unisa.edu.au (8.12.2/8.12.2) with ESMTP id gA46svrK024921;
	Mon, 4 Nov 2002 17:24:57 +1030 (CST)
Message-Id: <200211040654.gA46svrK024921@patty.levels.unisa.edu.au>
Date: Mon, 4 Nov 2002 17:22:37 +0900
From: "S. Ding " <sding@spri.levels.unisa.edu.au>
To: "manet@ietf.org" <manet@ietf.org>
CC: "manet-request@ietf.org" <manet-request@ietf.org>
X-mailer: Foxmail 4.1 [cn]
Mime-Version: 1.0
Content-Type: text/plain;
      charset="GB2312"
Content-Transfer-Encoding: 8bit
X-MIME-Autoconverted: from quoted-printable to 8bit by www1.ietf.org id gA46tCv30104
Subject: [manet] help: The IPv6 model in OPNET or NS2
Sender: manet-admin@ietf.org
Errors-To: manet-admin@ietf.org
X-BeenThere: manet@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/manet>,
	<mailto:manet-request@ietf.org?subject=unsubscribe>
List-Id: Mobile Ad-hoc Networks  <manet.ietf.org>
List-Post: <mailto:manet@ietf.org>
List-Help: <mailto:manet-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/manet>,
	<mailto:manet-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 8bit
Content-Transfer-Encoding: 8bit

manet-request,

      Hello. The standard model library in OPNET doesn't include the IPv6 model. Does anybody know where can I download one?
Or in NS2.
   

				 
ˇˇˇˇˇˇˇˇˇˇˇˇˇˇˇˇS. Ding 
ˇˇˇˇˇˇˇˇˇˇˇˇˇˇˇˇsding@spri.levels.unisa.edu.au
ˇˇˇˇˇˇˇˇˇˇˇˇˇˇˇˇˇˇˇˇ2002-11-04



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



From mailnull@www1.ietf.org  Mon Nov  4 09:59:20 2002
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA15463
	for <manet-archive@odin.ietf.org>; Mon, 4 Nov 2002 09:59:20 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id gA4F1JS30155
	for manet-archive@odin.ietf.org; Mon, 4 Nov 2002 10:01:19 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gA4F1Jv30152
	for <manet-web-archive@optimus.ietf.org>; Mon, 4 Nov 2002 10:01:19 -0500
Received: from www1.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA15437
	for <manet-web-archive@ietf.org>; Mon, 4 Nov 2002 09:58:49 -0500 (EST)
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gA4ErCv29722;
	Mon, 4 Nov 2002 09:53:12 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gA4EoVv29645
	for <manet@optimus.ietf.org>; Mon, 4 Nov 2002 09:50:31 -0500
Received: from mail.scires.com (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA14809
	for <manet@ietf.org>; Mon, 4 Nov 2002 09:48:01 -0500 (EST)
Received: from SRCATL-MTA by mail.scires.com
	with Novell_GroupWise; Mon, 04 Nov 2002 09:51:27 -0500
Message-Id: <sdc6431f.091@mail.scires.com>
X-Mailer: Novell GroupWise Internet Agent 6.0.2 Beta
Date: Mon, 04 Nov 2002 09:51:05 -0500
From: "Pete Sholander" <psholand@scires.com>
To: <manet@ietf.org>
Mime-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Disposition: inline
Content-Transfer-Encoding: 8bit
X-MIME-Autoconverted: from quoted-printable to 8bit by www1.ietf.org id gA4EoVv29646
Subject: [manet] Test Post to MANET List -- Sorry!
Sender: manet-admin@ietf.org
Errors-To: manet-admin@ietf.org
X-BeenThere: manet@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/manet>,
	<mailto:manet-request@ietf.org?subject=unsubscribe>
List-Id: Mobile Ad-hoc Networks  <manet.ietf.org>
List-Post: <mailto:manet@ietf.org>
List-Help: <mailto:manet-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/manet>,
	<mailto:manet-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 8bit
Content-Transfer-Encoding: 8bit

Testing posting after a recent ISP change.  Sorry for the bother ...

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



From manet-admin@ietf.org  Mon Nov  4 09:59:22 2002
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA15476
	for <manet-archive@lists.ietf.org>; Mon, 4 Nov 2002 09:59:22 -0500 (EST)
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gA4ErCv29722;
	Mon, 4 Nov 2002 09:53:12 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gA4EoVv29645
	for <manet@optimus.ietf.org>; Mon, 4 Nov 2002 09:50:31 -0500
Received: from mail.scires.com (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA14809
	for <manet@ietf.org>; Mon, 4 Nov 2002 09:48:01 -0500 (EST)
Received: from SRCATL-MTA by mail.scires.com
	with Novell_GroupWise; Mon, 04 Nov 2002 09:51:27 -0500
Message-Id: <sdc6431f.091@mail.scires.com>
X-Mailer: Novell GroupWise Internet Agent 6.0.2 Beta
Date: Mon, 04 Nov 2002 09:51:05 -0500
From: "Pete Sholander" <psholand@scires.com>
To: <manet@ietf.org>
Mime-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Disposition: inline
Content-Transfer-Encoding: 8bit
X-MIME-Autoconverted: from quoted-printable to 8bit by www1.ietf.org id gA4EoVv29646
Subject: [manet] Test Post to MANET List -- Sorry!
Sender: manet-admin@ietf.org
Errors-To: manet-admin@ietf.org
X-BeenThere: manet@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/manet>,
	<mailto:manet-request@ietf.org?subject=unsubscribe>
List-Id: Mobile Ad-hoc Networks  <manet.ietf.org>
List-Post: <mailto:manet@ietf.org>
List-Help: <mailto:manet-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/manet>,
	<mailto:manet-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 8bit

Testing posting after a recent ISP change.  Sorry for the bother ...

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


From manet-admin@ietf.org  Mon Nov  4 11:04:15 2002
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA19613
	for <manet-archive@lists.ietf.org>; Mon, 4 Nov 2002 11:04:15 -0500 (EST)
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gA4FwNv02119;
	Mon, 4 Nov 2002 10:58:23 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gA4Fsbv01967
	for <manet@optimus.ietf.org>; Mon, 4 Nov 2002 10:54:37 -0500
Received: from itd.nrl.navy.mil (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA19130
	for <manet@ietf.org>; Mon, 4 Nov 2002 10:52:05 -0500 (EST)
Received: from smtp.itd.nrl.navy.mil (smtp.itd.nrl.navy.mil [132.250.86.3])
	by itd.nrl.navy.mil (8.8.8+Sun/8.8.8) with SMTP id KAA05488;
	Mon, 4 Nov 2002 10:54:26 -0500 (EST)
Received: from SEXTANT.itd.nrl.navy.mil ([132.250.92.22])
 by smtp.itd.nrl.navy.mil (SAVSMTP 3.0.0.44) with SMTP id M2002110410542718251
 ; Mon, 04 Nov 2002 10:54:27 -0500
Message-Id: <5.1.1.5.2.20021104105317.0352eeb0@pop.itd.nrl.navy.mil>
X-Sender: macker@pop.itd.nrl.navy.mil
X-Mailer: QUALCOMM Windows Eudora Version 5.1.1
Date: Mon, 04 Nov 2002 10:54:07 -0500
To: Wei Wei <derekwei77@yahoo.com>, manet@ietf.org
From: Joe Macker <macker@itd.nrl.navy.mil>
Subject: Re: [manet] Building an Ad hoc experimental network using
  iPAQs.
In-Reply-To: <20021102004655.31723.qmail@web11105.mail.yahoo.com>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Sender: manet-admin@ietf.org
Errors-To: manet-admin@ietf.org
X-BeenThere: manet@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/manet>,
	<mailto:manet-request@ietf.org?subject=unsubscribe>
List-Id: Mobile Ad-hoc Networks  <manet.ietf.org>
List-Post: <mailto:manet@ietf.org>
List-Help: <mailto:manet-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/manet>,
	<mailto:manet-request@ietf.org?subject=subscribe>

At 04:46 PM 11/1/2002 -0800, Wei Wei wrote:
>Hi, All,
>
>I'm thinking about building an ad hoc experimental 
>network using iPAQs running linux. I need to modify 
>linux kernel so that I can test different routing 
>protocols. Do you think this is a reasonable way 

Many of us have run various manet protocols on IPAQs, Zauruses,etc.
Should be fine.  I never had to modify the kernel...


>to build an experimental ad hoc networks? I 
>appreciate any suggestions from you.
>
>Thanks,
>
>Wei
>
>__________________________________________________
>Do you Yahoo!?
>HotJobs - Search new jobs daily now
>http://hotjobs.yahoo.com/
>_______________________________________________
>manet mailing list
>manet@ietf.org
>https://www1.ietf.org/mailman/listinfo/manet


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


From mailnull@www1.ietf.org  Mon Nov  4 11:06:00 2002
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA19741
	for <manet-archive@odin.ietf.org>; Mon, 4 Nov 2002 11:06:00 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id gA4G81f03209
	for manet-archive@odin.ietf.org; Mon, 4 Nov 2002 11:08:01 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gA4G80v03204
	for <manet-web-archive@optimus.ietf.org>; Mon, 4 Nov 2002 11:08:00 -0500
Received: from www1.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA19596
	for <manet-web-archive@ietf.org>; Mon, 4 Nov 2002 11:03:40 -0500 (EST)
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gA4FwNv02119;
	Mon, 4 Nov 2002 10:58:23 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gA4Fsbv01967
	for <manet@optimus.ietf.org>; Mon, 4 Nov 2002 10:54:37 -0500
Received: from itd.nrl.navy.mil (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA19130
	for <manet@ietf.org>; Mon, 4 Nov 2002 10:52:05 -0500 (EST)
Received: from smtp.itd.nrl.navy.mil (smtp.itd.nrl.navy.mil [132.250.86.3])
	by itd.nrl.navy.mil (8.8.8+Sun/8.8.8) with SMTP id KAA05488;
	Mon, 4 Nov 2002 10:54:26 -0500 (EST)
Received: from SEXTANT.itd.nrl.navy.mil ([132.250.92.22])
 by smtp.itd.nrl.navy.mil (SAVSMTP 3.0.0.44) with SMTP id M2002110410542718251
 ; Mon, 04 Nov 2002 10:54:27 -0500
Message-Id: <5.1.1.5.2.20021104105317.0352eeb0@pop.itd.nrl.navy.mil>
X-Sender: macker@pop.itd.nrl.navy.mil
X-Mailer: QUALCOMM Windows Eudora Version 5.1.1
Date: Mon, 04 Nov 2002 10:54:07 -0500
To: Wei Wei <derekwei77@yahoo.com>, manet@ietf.org
From: Joe Macker <macker@itd.nrl.navy.mil>
Subject: Re: [manet] Building an Ad hoc experimental network using
  iPAQs.
In-Reply-To: <20021102004655.31723.qmail@web11105.mail.yahoo.com>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Sender: manet-admin@ietf.org
Errors-To: manet-admin@ietf.org
X-BeenThere: manet@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/manet>,
	<mailto:manet-request@ietf.org?subject=unsubscribe>
List-Id: Mobile Ad-hoc Networks  <manet.ietf.org>
List-Post: <mailto:manet@ietf.org>
List-Help: <mailto:manet-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/manet>,
	<mailto:manet-request@ietf.org?subject=subscribe>

At 04:46 PM 11/1/2002 -0800, Wei Wei wrote:
>Hi, All,
>
>I'm thinking about building an ad hoc experimental 
>network using iPAQs running linux. I need to modify 
>linux kernel so that I can test different routing 
>protocols. Do you think this is a reasonable way 

Many of us have run various manet protocols on IPAQs, Zauruses,etc.
Should be fine.  I never had to modify the kernel...


>to build an experimental ad hoc networks? I 
>appreciate any suggestions from you.
>
>Thanks,
>
>Wei
>
>__________________________________________________
>Do you Yahoo!?
>HotJobs - Search new jobs daily now
>http://hotjobs.yahoo.com/
>_______________________________________________
>manet mailing list
>manet@ietf.org
>https://www1.ietf.org/mailman/listinfo/manet


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



From manet-admin@ietf.org  Mon Nov  4 19:38:46 2002
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA16352
	for <manet-archive@lists.ietf.org>; Mon, 4 Nov 2002 19:38:46 -0500 (EST)
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gA50Whv17998;
	Mon, 4 Nov 2002 19:32:43 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gA4Djhv26229
	for <manet@optimus.ietf.org>; Mon, 4 Nov 2002 08:45:43 -0500
Received: from pulsar.univ-valenciennes.fr (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA12429
	for <manet@ietf.org>; Mon, 4 Nov 2002 08:43:13 -0500 (EST)
Received: from dief (gaia.univ-valenciennes.fr [193.50.192.113])
          by pulsar.univ-valenciennes.fr (8.12.3/jtpda-5.4) with SMTP id gA4EZqkd511232
          for <manet@ietf.org>; Mon, 4 Nov 2002 14:35:52 GMT
From: Francois Cartegnie <Francois.Cartegnie@univ-valenciennes.fr>
To: manet@ietf.org
Date: Mon, 4 Nov 2002 15:45:21 +0000
X-Mailer: KMail [version 1.1.95.2]
Content-Type: text/plain
References: <20021028170005.2758.18418.Mailman@www1.ietf.org>
In-Reply-To: <20021028170005.2758.18418.Mailman@www1.ietf.org>
MIME-Version: 1.0
Message-Id: <02110415452100.20930@dief>
Content-Transfer-Encoding: 8bit
X-MailScanner: Found to be clean
Content-Transfer-Encoding: 8bit
Subject: [manet] RTS/CTS in wireless MAC
Sender: manet-admin@ietf.org
Errors-To: manet-admin@ietf.org
X-BeenThere: manet@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/manet>,
	<mailto:manet-request@ietf.org?subject=unsubscribe>
List-Id: Mobile Ad-hoc Networks  <manet.ietf.org>
List-Post: <mailto:manet@ietf.org>
List-Help: <mailto:manet-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/manet>,
	<mailto:manet-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 8bit

Hi,

I got a question about the 802.11b behaviour in adhoc wireless networks.
How does the RTS/CTS is done when sending broadcast data over 802.11b ?
I mean, who replies to the RTS ?

Thanks
_______________________________________________
manet mailing list
manet@ietf.org
https://www1.ietf.org/mailman/listinfo/manet


From mailnull@www1.ietf.org  Mon Nov  4 19:45:17 2002
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA16481
	for <manet-archive@odin.ietf.org>; Mon, 4 Nov 2002 19:45:17 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id gA50lLb19308
	for manet-archive@odin.ietf.org; Mon, 4 Nov 2002 19:47:21 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gA50lKv19305
	for <manet-web-archive@optimus.ietf.org>; Mon, 4 Nov 2002 19:47:20 -0500
Received: from www1.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA16472
	for <manet-web-archive@ietf.org>; Mon, 4 Nov 2002 19:44:46 -0500 (EST)
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gA50dFv18871;
	Mon, 4 Nov 2002 19:39:15 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gA50cFv18829
	for <manet@optimus.ietf.org>; Mon, 4 Nov 2002 19:38:15 -0500
Received: from mail.engr.ucsb.edu (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA16302
	for <manet@ietf.org>; Mon, 4 Nov 2002 19:35:38 -0500 (EST)
Received: from linux23.engr.ucsb.edu ([128.111.53.125] helo=MESA.cs.ucsb.edu)
	by mail.engr.ucsb.edu with esmtp (Exim 4.10)
	id 188rjF-00046f-00; Mon, 04 Nov 2002 16:38:01 -0800
From: <idc@engineering.ucsb.edu>
MIME-Version: 1.0
Message-ID: <15815.4836.486000.805580@gargle.gargle.HOWL>
Date: Mon, 4 Nov 2002 16:37:56 -0800
To: Francois Cartegnie <Francois.Cartegnie@univ-valenciennes.fr>
Cc: manet@ietf.org
In-Reply-To: <02110415452100.20930@dief>
References: <20021028170005.2758.18418.Mailman@www1.ietf.org>
	<02110415452100.20930@dief>
X-Mailer: VM 7.07 under Emacs 21.1.1
Reply-To: idc@engineering.ucsb.edu
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Subject: RE:[manet] RTS/CTS in wireless MAC
X-Spam-Status: No, hits=-2.9 required=8.0
	tests=IN_REP_TO,NO_REAL_NAME
	version=2.31
Content-Transfer-Encoding: 7bit
Sender: manet-admin@ietf.org
Errors-To: manet-admin@ietf.org
X-BeenThere: manet@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/manet>,
	<mailto:manet-request@ietf.org?subject=unsubscribe>
List-Id: Mobile Ad-hoc Networks  <manet.ietf.org>
List-Post: <mailto:manet@ietf.org>
List-Help: <mailto:manet-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/manet>,
	<mailto:manet-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit

DCF (RTS-CTS-Data-ACK) is used only for unicast data.  CSMA/CA is used
for broadcast packets.

Ian Chakeres

Francois Cartegnie wrote:
>Hi,
>
>I got a question about the 802.11b behaviour in adhoc wireless networks.
>How does the RTS/CTS is done when sending broadcast data over 802.11b ?
>I mean, who replies to the RTS ?
>
>Thanks
>_______________________________________________
>manet mailing list
>manet@ietf.org
>https://www1.ietf.org/mailman/listinfo/manet

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



From manet-admin@ietf.org  Mon Nov  4 19:45:19 2002
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA16495
	for <manet-archive@lists.ietf.org>; Mon, 4 Nov 2002 19:45:19 -0500 (EST)
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gA50dFv18871;
	Mon, 4 Nov 2002 19:39:15 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gA50cFv18829
	for <manet@optimus.ietf.org>; Mon, 4 Nov 2002 19:38:15 -0500
Received: from mail.engr.ucsb.edu (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA16302
	for <manet@ietf.org>; Mon, 4 Nov 2002 19:35:38 -0500 (EST)
Received: from linux23.engr.ucsb.edu ([128.111.53.125] helo=MESA.cs.ucsb.edu)
	by mail.engr.ucsb.edu with esmtp (Exim 4.10)
	id 188rjF-00046f-00; Mon, 04 Nov 2002 16:38:01 -0800
From: <idc@engineering.ucsb.edu>
MIME-Version: 1.0
Message-ID: <15815.4836.486000.805580@gargle.gargle.HOWL>
Date: Mon, 4 Nov 2002 16:37:56 -0800
To: Francois Cartegnie <Francois.Cartegnie@univ-valenciennes.fr>
Cc: manet@ietf.org
In-Reply-To: <02110415452100.20930@dief>
References: <20021028170005.2758.18418.Mailman@www1.ietf.org>
	<02110415452100.20930@dief>
X-Mailer: VM 7.07 under Emacs 21.1.1
Reply-To: idc@engineering.ucsb.edu
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Subject: RE:[manet] RTS/CTS in wireless MAC
X-Spam-Status: No, hits=-2.9 required=8.0
	tests=IN_REP_TO,NO_REAL_NAME
	version=2.31
Content-Transfer-Encoding: 7bit
Sender: manet-admin@ietf.org
Errors-To: manet-admin@ietf.org
X-BeenThere: manet@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/manet>,
	<mailto:manet-request@ietf.org?subject=unsubscribe>
List-Id: Mobile Ad-hoc Networks  <manet.ietf.org>
List-Post: <mailto:manet@ietf.org>
List-Help: <mailto:manet-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/manet>,
	<mailto:manet-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 7bit

DCF (RTS-CTS-Data-ACK) is used only for unicast data.  CSMA/CA is used
for broadcast packets.

Ian Chakeres

Francois Cartegnie wrote:
>Hi,
>
>I got a question about the 802.11b behaviour in adhoc wireless networks.
>How does the RTS/CTS is done when sending broadcast data over 802.11b ?
>I mean, who replies to the RTS ?
>
>Thanks
>_______________________________________________
>manet mailing list
>manet@ietf.org
>https://www1.ietf.org/mailman/listinfo/manet

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


From mailnull@www1.ietf.org  Mon Nov  4 19:45:54 2002
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA16520
	for <manet-archive@odin.ietf.org>; Mon, 4 Nov 2002 19:45:54 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id gA50lvb19333
	for manet-archive@odin.ietf.org; Mon, 4 Nov 2002 19:47:57 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gA50lvv19330
	for <manet-web-archive@optimus.ietf.org>; Mon, 4 Nov 2002 19:47:57 -0500
Received: from www1.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA16509
	for <manet-web-archive@ietf.org>; Mon, 4 Nov 2002 19:45:23 -0500 (EST)
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gA50Whv17998;
	Mon, 4 Nov 2002 19:32:43 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gA4Djhv26229
	for <manet@optimus.ietf.org>; Mon, 4 Nov 2002 08:45:43 -0500
Received: from pulsar.univ-valenciennes.fr (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA12429
	for <manet@ietf.org>; Mon, 4 Nov 2002 08:43:13 -0500 (EST)
Received: from dief (gaia.univ-valenciennes.fr [193.50.192.113])
          by pulsar.univ-valenciennes.fr (8.12.3/jtpda-5.4) with SMTP id gA4EZqkd511232
          for <manet@ietf.org>; Mon, 4 Nov 2002 14:35:52 GMT
From: Francois Cartegnie <Francois.Cartegnie@univ-valenciennes.fr>
To: manet@ietf.org
Date: Mon, 4 Nov 2002 15:45:21 +0000
X-Mailer: KMail [version 1.1.95.2]
Content-Type: text/plain
References: <20021028170005.2758.18418.Mailman@www1.ietf.org>
In-Reply-To: <20021028170005.2758.18418.Mailman@www1.ietf.org>
MIME-Version: 1.0
Message-Id: <02110415452100.20930@dief>
Content-Transfer-Encoding: 8bit
X-MailScanner: Found to be clean
Content-Transfer-Encoding: 8bit
Subject: [manet] RTS/CTS in wireless MAC
Sender: manet-admin@ietf.org
Errors-To: manet-admin@ietf.org
X-BeenThere: manet@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/manet>,
	<mailto:manet-request@ietf.org?subject=unsubscribe>
List-Id: Mobile Ad-hoc Networks  <manet.ietf.org>
List-Post: <mailto:manet@ietf.org>
List-Help: <mailto:manet-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/manet>,
	<mailto:manet-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 8bit
Content-Transfer-Encoding: 8bit

Hi,

I got a question about the 802.11b behaviour in adhoc wireless networks.
How does the RTS/CTS is done when sending broadcast data over 802.11b ?
I mean, who replies to the RTS ?

Thanks
_______________________________________________
manet mailing list
manet@ietf.org
https://www1.ietf.org/mailman/listinfo/manet



From mailnull@www1.ietf.org  Mon Nov  4 19:55:43 2002
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA16962
	for <manet-archive@odin.ietf.org>; Mon, 4 Nov 2002 19:55:43 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id gA50vj819988
	for manet-archive@odin.ietf.org; Mon, 4 Nov 2002 19:57:45 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gA50vjv19985
	for <manet-web-archive@optimus.ietf.org>; Mon, 4 Nov 2002 19:57:45 -0500
Received: from www1.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA16947
	for <manet-web-archive@ietf.org>; Mon, 4 Nov 2002 19:55:10 -0500 (EST)
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gA50oOv19526;
	Mon, 4 Nov 2002 19:50:24 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gA50nmv19438
	for <manet@optimus.ietf.org>; Mon, 4 Nov 2002 19:49:48 -0500
Received: from hades.snrc.uow.edu.au (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA16583
	for <manet@ietf.org>; Mon, 4 Nov 2002 19:47:12 -0500 (EST)
Received: from there (justin@eros [130.130.10.74])
	by hades.snrc.uow.edu.au (8.11.2/8.11.2) with SMTP id gA50miB15253;
	Tue, 5 Nov 2002 11:48:44 +1100 (EST)
Message-Id: <200211050048.gA50miB15253@hades.snrc.uow.edu.au>
Content-Type: text/plain;
  charset="iso-8859-1"
From: Justin Lipman <justin@titr.uow.edu.au>
Reply-To: justin@titr.uow.edu.au
Organization: TITR
To: Francois Cartegnie <Francois.Cartegnie@univ-valenciennes.fr>,
        manet@ietf.org
Subject: Re: [manet] RTS/CTS in wireless MAC
Date: Tue, 5 Nov 2002 11:52:48 +1100
X-Mailer: KMail [version 1.3.2]
References: <20021028170005.2758.18418.Mailman@www1.ietf.org> <02110415452100.20930@dief>
In-Reply-To: <02110415452100.20930@dief>
MIME-Version: 1.0
Content-Transfer-Encoding: 8bit
X-MIME-Autoconverted: from quoted-printable to 8bit by www1.ietf.org id gA50nmv19439
Sender: manet-admin@ietf.org
Errors-To: manet-admin@ietf.org
X-BeenThere: manet@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/manet>,
	<mailto:manet-request@ietf.org?subject=unsubscribe>
List-Id: Mobile Ad-hoc Networks  <manet.ietf.org>
List-Post: <mailto:manet@ietf.org>
List-Help: <mailto:manet-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/manet>,
	<mailto:manet-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 8bit
Content-Transfer-Encoding: 8bit

Hi,

When performing a broadcast there is no RTS/CTS mechanism used in 802.11.
This is only done in with unicasting.

regards,
Justin

-- 
Telecommunications & Information Technology Research Institute
University of Wollongong, Australia 
http://www.titr.uow.edu.au


On Tue, 5 Nov 2002 02:45, Francois Cartegnie wrote:
> Hi,
>
> I got a question about the 802.11b behaviour in adhoc wireless networks.
> How does the RTS/CTS is done when sending broadcast data over 802.11b ?
> I mean, who replies to the RTS ?
>
> Thanks
> _______________________________________________
> manet mailing list
> manet@ietf.org
> https://www1.ietf.org/mailman/listinfo/manet


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



From manet-admin@ietf.org  Mon Nov  4 19:55:43 2002
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA16964
	for <manet-archive@lists.ietf.org>; Mon, 4 Nov 2002 19:55:43 -0500 (EST)
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gA50oOv19526;
	Mon, 4 Nov 2002 19:50:24 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gA50nmv19438
	for <manet@optimus.ietf.org>; Mon, 4 Nov 2002 19:49:48 -0500
Received: from hades.snrc.uow.edu.au (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA16583
	for <manet@ietf.org>; Mon, 4 Nov 2002 19:47:12 -0500 (EST)
Received: from there (justin@eros [130.130.10.74])
	by hades.snrc.uow.edu.au (8.11.2/8.11.2) with SMTP id gA50miB15253;
	Tue, 5 Nov 2002 11:48:44 +1100 (EST)
Message-Id: <200211050048.gA50miB15253@hades.snrc.uow.edu.au>
Content-Type: text/plain;
  charset="iso-8859-1"
From: Justin Lipman <justin@titr.uow.edu.au>
Reply-To: justin@titr.uow.edu.au
Organization: TITR
To: Francois Cartegnie <Francois.Cartegnie@univ-valenciennes.fr>,
        manet@ietf.org
Subject: Re: [manet] RTS/CTS in wireless MAC
Date: Tue, 5 Nov 2002 11:52:48 +1100
X-Mailer: KMail [version 1.3.2]
References: <20021028170005.2758.18418.Mailman@www1.ietf.org> <02110415452100.20930@dief>
In-Reply-To: <02110415452100.20930@dief>
MIME-Version: 1.0
Content-Transfer-Encoding: 8bit
X-MIME-Autoconverted: from quoted-printable to 8bit by www1.ietf.org id gA50nmv19439
Sender: manet-admin@ietf.org
Errors-To: manet-admin@ietf.org
X-BeenThere: manet@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/manet>,
	<mailto:manet-request@ietf.org?subject=unsubscribe>
List-Id: Mobile Ad-hoc Networks  <manet.ietf.org>
List-Post: <mailto:manet@ietf.org>
List-Help: <mailto:manet-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/manet>,
	<mailto:manet-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 8bit

Hi,

When performing a broadcast there is no RTS/CTS mechanism used in 802.11.
This is only done in with unicasting.

regards,
Justin

-- 
Telecommunications & Information Technology Research Institute
University of Wollongong, Australia 
http://www.titr.uow.edu.au


On Tue, 5 Nov 2002 02:45, Francois Cartegnie wrote:
> Hi,
>
> I got a question about the 802.11b behaviour in adhoc wireless networks.
> How does the RTS/CTS is done when sending broadcast data over 802.11b ?
> I mean, who replies to the RTS ?
>
> Thanks
> _______________________________________________
> manet mailing list
> manet@ietf.org
> https://www1.ietf.org/mailman/listinfo/manet


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


From manet-admin@ietf.org  Mon Nov  4 20:01:49 2002
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id UAA17201
	for <manet-archive@lists.ietf.org>; Mon, 4 Nov 2002 20:01:49 -0500 (EST)
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gA50uDv19867;
	Mon, 4 Nov 2002 19:56:14 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gA50t9v19790
	for <manet@optimus.ietf.org>; Mon, 4 Nov 2002 19:55:09 -0500
Received: from web14906.mail.yahoo.com (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id TAA16799
	for <manet@ietf.org>; Mon, 4 Nov 2002 19:52:35 -0500 (EST)
Message-ID: <20021105005501.70510.qmail@web14906.mail.yahoo.com>
Received: from [66.69.159.142] by web14906.mail.yahoo.com via HTTP; Mon, 04 Nov 2002 16:55:01 PST
Date: Mon, 4 Nov 2002 16:55:01 -0800 (PST)
From: prashanth kumar <prashanth2713@yahoo.com>
To: manet@ietf.org
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Subject: [manet] network models
Sender: manet-admin@ietf.org
Errors-To: manet-admin@ietf.org
X-BeenThere: manet@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/manet>,
	<mailto:manet-request@ietf.org?subject=unsubscribe>
List-Id: Mobile Ad-hoc Networks  <manet.ietf.org>
List-Post: <mailto:manet@ietf.org>
List-Help: <mailto:manet-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/manet>,
	<mailto:manet-request@ietf.org?subject=subscribe>

 
 

__________________________________________________
Do you Yahoo!?
HotJobs - Search new jobs daily now
http://hotjobs.yahoo.com/
_______________________________________________
manet mailing list
manet@ietf.org
https://www1.ietf.org/mailman/listinfo/manet


From mailnull@www1.ietf.org  Mon Nov  4 20:11:31 2002
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id UAA17491
	for <manet-archive@odin.ietf.org>; Mon, 4 Nov 2002 20:11:30 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id gA51DYC21532
	for manet-archive@odin.ietf.org; Mon, 4 Nov 2002 20:13:34 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gA51DYv21529
	for <manet-web-archive@optimus.ietf.org>; Mon, 4 Nov 2002 20:13:34 -0500
Received: from www1.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id UAA17478
	for <manet-web-archive@ietf.org>; Mon, 4 Nov 2002 20:10:59 -0500 (EST)
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gA516Hv20559;
	Mon, 4 Nov 2002 20:06:17 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gA5144v20433
	for <manet@optimus.ietf.org>; Mon, 4 Nov 2002 20:04:04 -0500
Received: from web14904.mail.yahoo.com (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id UAA17182
	for <manet@ietf.org>; Mon, 4 Nov 2002 20:01:30 -0500 (EST)
Message-ID: <20021105010356.92831.qmail@web14904.mail.yahoo.com>
Received: from [66.69.159.142] by web14904.mail.yahoo.com via HTTP; Mon, 04 Nov 2002 17:03:56 PST
Date: Mon, 4 Nov 2002 17:03:56 -0800 (PST)
From: prashanth kumar <prashanth2713@yahoo.com>
To: manet@ietf.org
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Subject: [manet] network models
Sender: manet-admin@ietf.org
Errors-To: manet-admin@ietf.org
X-BeenThere: manet@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/manet>,
	<mailto:manet-request@ietf.org?subject=unsubscribe>
List-Id: Mobile Ad-hoc Networks  <manet.ietf.org>
List-Post: <mailto:manet@ietf.org>
List-Help: <mailto:manet-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/manet>,
	<mailto:manet-request@ietf.org?subject=subscribe>

hi all,
   sorry for the previous blank mail. Does anyone know
of any analytical expressions for the probability
distribution of the minimum hop distance between two
arbitrary nodes in an adhoc network under a realistic
network model? The Erdos results are not very
helpful..link probability does not decay with
distance. Has anyone come across any paper which
places a probability distribution on the space of
random graphs and calcutes some interesting average
quantities? 
Thanks in advance,
Prash. 

__________________________________________________
Do you Yahoo!?
HotJobs - Search new jobs daily now
http://hotjobs.yahoo.com/
_______________________________________________
manet mailing list
manet@ietf.org
https://www1.ietf.org/mailman/listinfo/manet



From manet-admin@ietf.org  Mon Nov  4 20:11:32 2002
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id UAA17504
	for <manet-archive@lists.ietf.org>; Mon, 4 Nov 2002 20:11:32 -0500 (EST)
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gA516Hv20559;
	Mon, 4 Nov 2002 20:06:17 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gA5144v20433
	for <manet@optimus.ietf.org>; Mon, 4 Nov 2002 20:04:04 -0500
Received: from web14904.mail.yahoo.com (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id UAA17182
	for <manet@ietf.org>; Mon, 4 Nov 2002 20:01:30 -0500 (EST)
Message-ID: <20021105010356.92831.qmail@web14904.mail.yahoo.com>
Received: from [66.69.159.142] by web14904.mail.yahoo.com via HTTP; Mon, 04 Nov 2002 17:03:56 PST
Date: Mon, 4 Nov 2002 17:03:56 -0800 (PST)
From: prashanth kumar <prashanth2713@yahoo.com>
To: manet@ietf.org
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Subject: [manet] network models
Sender: manet-admin@ietf.org
Errors-To: manet-admin@ietf.org
X-BeenThere: manet@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/manet>,
	<mailto:manet-request@ietf.org?subject=unsubscribe>
List-Id: Mobile Ad-hoc Networks  <manet.ietf.org>
List-Post: <mailto:manet@ietf.org>
List-Help: <mailto:manet-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/manet>,
	<mailto:manet-request@ietf.org?subject=subscribe>

hi all,
   sorry for the previous blank mail. Does anyone know
of any analytical expressions for the probability
distribution of the minimum hop distance between two
arbitrary nodes in an adhoc network under a realistic
network model? The Erdos results are not very
helpful..link probability does not decay with
distance. Has anyone come across any paper which
places a probability distribution on the space of
random graphs and calcutes some interesting average
quantities? 
Thanks in advance,
Prash. 

__________________________________________________
Do you Yahoo!?
HotJobs - Search new jobs daily now
http://hotjobs.yahoo.com/
_______________________________________________
manet mailing list
manet@ietf.org
https://www1.ietf.org/mailman/listinfo/manet


From mailnull@www1.ietf.org  Mon Nov  4 20:15:02 2002
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id UAA17603
	for <manet-archive@odin.ietf.org>; Mon, 4 Nov 2002 20:15:02 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id gA51H6X21681
	for manet-archive@odin.ietf.org; Mon, 4 Nov 2002 20:17:06 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gA51H6v21678
	for <manet-web-archive@optimus.ietf.org>; Mon, 4 Nov 2002 20:17:06 -0500
Received: from www1.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id UAA17593
	for <manet-web-archive@ietf.org>; Mon, 4 Nov 2002 20:14:31 -0500 (EST)
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gA50uDv19867;
	Mon, 4 Nov 2002 19:56:14 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gA50t9v19790
	for <manet@optimus.ietf.org>; Mon, 4 Nov 2002 19:55:09 -0500
Received: from web14906.mail.yahoo.com (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id TAA16799
	for <manet@ietf.org>; Mon, 4 Nov 2002 19:52:35 -0500 (EST)
Message-ID: <20021105005501.70510.qmail@web14906.mail.yahoo.com>
Received: from [66.69.159.142] by web14906.mail.yahoo.com via HTTP; Mon, 04 Nov 2002 16:55:01 PST
Date: Mon, 4 Nov 2002 16:55:01 -0800 (PST)
From: prashanth kumar <prashanth2713@yahoo.com>
To: manet@ietf.org
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Subject: [manet] network models
Sender: manet-admin@ietf.org
Errors-To: manet-admin@ietf.org
X-BeenThere: manet@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/manet>,
	<mailto:manet-request@ietf.org?subject=unsubscribe>
List-Id: Mobile Ad-hoc Networks  <manet.ietf.org>
List-Post: <mailto:manet@ietf.org>
List-Help: <mailto:manet-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/manet>,
	<mailto:manet-request@ietf.org?subject=subscribe>

 
 

__________________________________________________
Do you Yahoo!?
HotJobs - Search new jobs daily now
http://hotjobs.yahoo.com/
_______________________________________________
manet mailing list
manet@ietf.org
https://www1.ietf.org/mailman/listinfo/manet



From mailnull@www1.ietf.org  Mon Nov  4 23:26:04 2002
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id XAA22589
	for <manet-archive@odin.ietf.org>; Mon, 4 Nov 2002 23:26:04 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id gA54SAX31665
	for manet-archive@odin.ietf.org; Mon, 4 Nov 2002 23:28:10 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gA54SAv31662
	for <manet-web-archive@optimus.ietf.org>; Mon, 4 Nov 2002 23:28:10 -0500
Received: from www1.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id XAA22563
	for <manet-web-archive@ietf.org>; Mon, 4 Nov 2002 23:25:33 -0500 (EST)
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gA54Jiv31176;
	Mon, 4 Nov 2002 23:19:44 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gA54DJv31043
	for <manet@optimus.ietf.org>; Mon, 4 Nov 2002 23:13:19 -0500
Received: from ponyexpress.ee.columbia.edu (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id XAA22262
	for <manet@ietf.org>; Mon, 4 Nov 2002 23:10:42 -0500 (EST)
Received: from ORC (dhcp-65-69.ee.columbia.edu [128.59.65.69])
	by ponyexpress.ee.columbia.edu (8.12.1/8.12.1) with SMTP id gA54DAGR018948
	for <manet@ietf.org>; Mon, 4 Nov 2002 23:13:11 -0500
Message-ID: <003901c28481$9d1d83c0$45413b80@ORC>
Reply-To: "Gahng-Seop Ahn" <ahngang@ee.columbia.edu>
From: "Gahng-Seop Ahn" <ahngang@ee.columbia.edu>
To: <manet@ietf.org>
References: <20021105014901.23648.74736.Mailman@www1.ietf.org>
Date: Mon, 4 Nov 2002 23:12:53 -0500
Organization: COMET
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 6.00.2800.1106
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1106
Content-Transfer-Encoding: 7bit
Subject: [manet] SWAN
Sender: manet-admin@ietf.org
Errors-To: manet-admin@ietf.org
X-BeenThere: manet@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/manet>,
	<mailto:manet-request@ietf.org?subject=unsubscribe>
List-Id: Mobile Ad-hoc Networks  <manet.ietf.org>
List-Post: <mailto:manet@ietf.org>
List-Help: <mailto:manet-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/manet>,
	<mailto:manet-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit

Folks:

We have developed a stateless approach to QOS in MANETs that supports
real-time services and service differentiation called SWAN.

We were late in submitting the SWAN ID which you can find along with ns-2
code at:

http://comet.columbia.edu/swan/

For those interested in simulation and experimental testbed results see:

http://comet.columbia.edu/swan/swan-tmc.pdf

G.-S. Ahn, A. T. Campbell, Andras Veres and Li-Hsiang Sun, "Supporting
Service Differentiation for Real-Time and Best Effort Traffic in Stateless
Wireless Ad Hoc Networks (SWAN)", IEEE Transactions on Mobile Computing,
September 2002.

We plan to release the Linux source code toward end of this year off the
same web page.

Thanks,
Gahng-Seop Ahn
--
http://comet.columbia.edu/~ahngang/

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



From manet-admin@ietf.org  Mon Nov  4 23:26:07 2002
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id XAA22602
	for <manet-archive@lists.ietf.org>; Mon, 4 Nov 2002 23:26:07 -0500 (EST)
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gA54Jiv31176;
	Mon, 4 Nov 2002 23:19:44 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gA54DJv31043
	for <manet@optimus.ietf.org>; Mon, 4 Nov 2002 23:13:19 -0500
Received: from ponyexpress.ee.columbia.edu (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id XAA22262
	for <manet@ietf.org>; Mon, 4 Nov 2002 23:10:42 -0500 (EST)
Received: from ORC (dhcp-65-69.ee.columbia.edu [128.59.65.69])
	by ponyexpress.ee.columbia.edu (8.12.1/8.12.1) with SMTP id gA54DAGR018948
	for <manet@ietf.org>; Mon, 4 Nov 2002 23:13:11 -0500
Message-ID: <003901c28481$9d1d83c0$45413b80@ORC>
Reply-To: "Gahng-Seop Ahn" <ahngang@ee.columbia.edu>
From: "Gahng-Seop Ahn" <ahngang@ee.columbia.edu>
To: <manet@ietf.org>
References: <20021105014901.23648.74736.Mailman@www1.ietf.org>
Date: Mon, 4 Nov 2002 23:12:53 -0500
Organization: COMET
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 6.00.2800.1106
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1106
Content-Transfer-Encoding: 7bit
Subject: [manet] SWAN
Sender: manet-admin@ietf.org
Errors-To: manet-admin@ietf.org
X-BeenThere: manet@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/manet>,
	<mailto:manet-request@ietf.org?subject=unsubscribe>
List-Id: Mobile Ad-hoc Networks  <manet.ietf.org>
List-Post: <mailto:manet@ietf.org>
List-Help: <mailto:manet-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/manet>,
	<mailto:manet-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 7bit

Folks:

We have developed a stateless approach to QOS in MANETs that supports
real-time services and service differentiation called SWAN.

We were late in submitting the SWAN ID which you can find along with ns-2
code at:

http://comet.columbia.edu/swan/

For those interested in simulation and experimental testbed results see:

http://comet.columbia.edu/swan/swan-tmc.pdf

G.-S. Ahn, A. T. Campbell, Andras Veres and Li-Hsiang Sun, "Supporting
Service Differentiation for Real-Time and Best Effort Traffic in Stateless
Wireless Ad Hoc Networks (SWAN)", IEEE Transactions on Mobile Computing,
September 2002.

We plan to release the Linux source code toward end of this year off the
same web page.

Thanks,
Gahng-Seop Ahn
--
http://comet.columbia.edu/~ahngang/

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


From mailnull@www1.ietf.org  Tue Nov  5 09:11:56 2002
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA19390
	for <manet-archive@odin.ietf.org>; Tue, 5 Nov 2002 09:11:56 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id gA5EDt113951
	for manet-archive@odin.ietf.org; Tue, 5 Nov 2002 09:13:55 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gA5EDtv13948
	for <manet-web-archive@optimus.ietf.org>; Tue, 5 Nov 2002 09:13:55 -0500
Received: from www1.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA19363
	for <manet-web-archive@ietf.org>; Tue, 5 Nov 2002 09:11:25 -0500 (EST)
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gA5E5pv12918;
	Tue, 5 Nov 2002 09:05:51 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gA5DuTv12607
	for <manet@optimus.ietf.org>; Tue, 5 Nov 2002 08:56:29 -0500
Received: from mion.elka.pw.edu.pl (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA18682
	for <manet@ietf.org>; Tue, 5 Nov 2002 08:53:58 -0500 (EST)
Received: (from localhost user: 'gbanasia' uid#8789 fake: STDIN
	(gbanasia@mion.elka.pw.edu.pl)) by mion.elka.pw.edu.pl
	id <S314196AbSKENx5>; Tue, 5 Nov 2002 14:53:57 +0100
Date: 	Tue, 5 Nov 2002 14:52:06 +0100
From: Grzegorz Banasiak <G.Banasiak@elka.pw.edu.pl>
To: manet@ietf.org
Subject: Re: [manet] RTS/CTS in wireless MAC
Message-ID: <20021105145206.A28125@mion.elka.pw.edu.pl>
References: <20021028170005.2758.18418.Mailman@www1.ietf.org> <02110415452100.20930@dief> <15815.4836.486000.805580@gargle.gargle.HOWL>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
User-Agent: Mutt/1.2.5i
In-Reply-To: <15815.4836.486000.805580@gargle.gargle.HOWL>; from idc@engineering.ucsb.edu on Mon, Nov 04, 2002 at 04:37:56PM -0800
X-Virus-Scanned: by AMaViS perl-11 mion
Sender: manet-admin@ietf.org
Errors-To: manet-admin@ietf.org
X-BeenThere: manet@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/manet>,
	<mailto:manet-request@ietf.org?subject=unsubscribe>
List-Id: Mobile Ad-hoc Networks  <manet.ietf.org>
List-Post: <mailto:manet@ietf.org>
List-Help: <mailto:manet-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/manet>,
	<mailto:manet-request@ietf.org?subject=subscribe>

On Mon, Nov 04, 2002 at 04:37:56PM -0800, idc@engineering.ucsb.edu wrote:
> DCF (RTS-CTS-Data-ACK) is used only for unicast data.  CSMA/CA is used
> for broadcast packets.
DCF is a kind of CSMA/CA scheme (and so do PCF). I presume that broadcast
packets are sent with CSMA/CD (i.e.  without any RTS/CTS/ACK handshake). Am I
right?

-- 
Grzegorz Banasiak
_______________________________________________
manet mailing list
manet@ietf.org
https://www1.ietf.org/mailman/listinfo/manet



From manet-admin@ietf.org  Tue Nov  5 09:11:58 2002
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA19403
	for <manet-archive@lists.ietf.org>; Tue, 5 Nov 2002 09:11:58 -0500 (EST)
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gA5E5pv12918;
	Tue, 5 Nov 2002 09:05:51 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gA5DuTv12607
	for <manet@optimus.ietf.org>; Tue, 5 Nov 2002 08:56:29 -0500
Received: from mion.elka.pw.edu.pl (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA18682
	for <manet@ietf.org>; Tue, 5 Nov 2002 08:53:58 -0500 (EST)
Received: (from localhost user: 'gbanasia' uid#8789 fake: STDIN
	(gbanasia@mion.elka.pw.edu.pl)) by mion.elka.pw.edu.pl
	id <S314196AbSKENx5>; Tue, 5 Nov 2002 14:53:57 +0100
Date: 	Tue, 5 Nov 2002 14:52:06 +0100
From: Grzegorz Banasiak <G.Banasiak@elka.pw.edu.pl>
To: manet@ietf.org
Subject: Re: [manet] RTS/CTS in wireless MAC
Message-ID: <20021105145206.A28125@mion.elka.pw.edu.pl>
References: <20021028170005.2758.18418.Mailman@www1.ietf.org> <02110415452100.20930@dief> <15815.4836.486000.805580@gargle.gargle.HOWL>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
User-Agent: Mutt/1.2.5i
In-Reply-To: <15815.4836.486000.805580@gargle.gargle.HOWL>; from idc@engineering.ucsb.edu on Mon, Nov 04, 2002 at 04:37:56PM -0800
X-Virus-Scanned: by AMaViS perl-11 mion
Sender: manet-admin@ietf.org
Errors-To: manet-admin@ietf.org
X-BeenThere: manet@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/manet>,
	<mailto:manet-request@ietf.org?subject=unsubscribe>
List-Id: Mobile Ad-hoc Networks  <manet.ietf.org>
List-Post: <mailto:manet@ietf.org>
List-Help: <mailto:manet-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/manet>,
	<mailto:manet-request@ietf.org?subject=subscribe>

On Mon, Nov 04, 2002 at 04:37:56PM -0800, idc@engineering.ucsb.edu wrote:
> DCF (RTS-CTS-Data-ACK) is used only for unicast data.  CSMA/CA is used
> for broadcast packets.
DCF is a kind of CSMA/CA scheme (and so do PCF). I presume that broadcast
packets are sent with CSMA/CD (i.e.  without any RTS/CTS/ACK handshake). Am I
right?

-- 
Grzegorz Banasiak
_______________________________________________
manet mailing list
manet@ietf.org
https://www1.ietf.org/mailman/listinfo/manet


From manet-admin@ietf.org  Tue Nov  5 10:26:33 2002
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA23435
	for <manet-archive@lists.ietf.org>; Tue, 5 Nov 2002 10:26:32 -0500 (EST)
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gA5FGov18366;
	Tue, 5 Nov 2002 10:16:50 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gA5F4ev17318
	for <manet@optimus.ietf.org>; Tue, 5 Nov 2002 10:04:40 -0500
Received: from liman.rutgers.edu (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA21740
	for <manet@ietf.org>; Tue, 5 Nov 2002 10:02:09 -0500 (EST)
Received: from liman1 (sachin@liman1 [128.6.110.14])
	by liman.rutgers.edu (8.12.2/8.12.2) with ESMTP id gA5F4UWq029169;
	Tue, 5 Nov 2002 10:04:30 -0500 (EST)
Date: Tue, 5 Nov 2002 10:04:30 -0500 (EST)
From: Sachin Ganu <sachin@liman.rutgers.edu>
X-Sender: sachin@liman1
To: Grzegorz Banasiak <G.Banasiak@elka.pw.edu.pl>
cc: manet@ietf.org
Subject: Re: [manet] RTS/CTS in wireless MAC
In-Reply-To: <20021105145206.A28125@mion.elka.pw.edu.pl>
Message-ID: <Pine.GSO.4.05.10211051003420.26532-100000@liman1>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: manet-admin@ietf.org
Errors-To: manet-admin@ietf.org
X-BeenThere: manet@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/manet>,
	<mailto:manet-request@ietf.org?subject=unsubscribe>
List-Id: Mobile Ad-hoc Networks  <manet.ietf.org>
List-Post: <mailto:manet@ietf.org>
List-Help: <mailto:manet-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/manet>,
	<mailto:manet-request@ietf.org?subject=subscribe>


I do not think CSMA/CD is possible in MANET

On Tue, 5 Nov 2002, Grzegorz Banasiak wrote:

> On Mon, Nov 04, 2002 at 04:37:56PM -0800, idc@engineering.ucsb.edu wrote:
> > DCF (RTS-CTS-Data-ACK) is used only for unicast data.  CSMA/CA is used
> > for broadcast packets.
> DCF is a kind of CSMA/CA scheme (and so do PCF). I presume that broadcast
> packets are sent with CSMA/CD (i.e.  without any RTS/CTS/ACK handshake). Am I
> right?
> 
> -- 
> Grzegorz Banasiak
> _______________________________________________
> manet mailing list
> manet@ietf.org
> https://www1.ietf.org/mailman/listinfo/manet
> 

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


From mailnull@www1.ietf.org  Tue Nov  5 10:30:07 2002
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA23655
	for <manet-archive@odin.ietf.org>; Tue, 5 Nov 2002 10:30:07 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id gA5FW7x19416
	for manet-archive@odin.ietf.org; Tue, 5 Nov 2002 10:32:07 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gA5FW7v19413
	for <manet-web-archive@optimus.ietf.org>; Tue, 5 Nov 2002 10:32:07 -0500
Received: from www1.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA23562
	for <manet-web-archive@ietf.org>; Tue, 5 Nov 2002 10:29:36 -0500 (EST)
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gA5FGov18366;
	Tue, 5 Nov 2002 10:16:50 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gA5F4ev17318
	for <manet@optimus.ietf.org>; Tue, 5 Nov 2002 10:04:40 -0500
Received: from liman.rutgers.edu (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA21740
	for <manet@ietf.org>; Tue, 5 Nov 2002 10:02:09 -0500 (EST)
Received: from liman1 (sachin@liman1 [128.6.110.14])
	by liman.rutgers.edu (8.12.2/8.12.2) with ESMTP id gA5F4UWq029169;
	Tue, 5 Nov 2002 10:04:30 -0500 (EST)
Date: Tue, 5 Nov 2002 10:04:30 -0500 (EST)
From: Sachin Ganu <sachin@liman.rutgers.edu>
X-Sender: sachin@liman1
To: Grzegorz Banasiak <G.Banasiak@elka.pw.edu.pl>
cc: manet@ietf.org
Subject: Re: [manet] RTS/CTS in wireless MAC
In-Reply-To: <20021105145206.A28125@mion.elka.pw.edu.pl>
Message-ID: <Pine.GSO.4.05.10211051003420.26532-100000@liman1>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: manet-admin@ietf.org
Errors-To: manet-admin@ietf.org
X-BeenThere: manet@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/manet>,
	<mailto:manet-request@ietf.org?subject=unsubscribe>
List-Id: Mobile Ad-hoc Networks  <manet.ietf.org>
List-Post: <mailto:manet@ietf.org>
List-Help: <mailto:manet-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/manet>,
	<mailto:manet-request@ietf.org?subject=subscribe>


I do not think CSMA/CD is possible in MANET

On Tue, 5 Nov 2002, Grzegorz Banasiak wrote:

> On Mon, Nov 04, 2002 at 04:37:56PM -0800, idc@engineering.ucsb.edu wrote:
> > DCF (RTS-CTS-Data-ACK) is used only for unicast data.  CSMA/CA is used
> > for broadcast packets.
> DCF is a kind of CSMA/CA scheme (and so do PCF). I presume that broadcast
> packets are sent with CSMA/CD (i.e.  without any RTS/CTS/ACK handshake). Am I
> right?
> 
> -- 
> Grzegorz Banasiak
> _______________________________________________
> manet mailing list
> manet@ietf.org
> https://www1.ietf.org/mailman/listinfo/manet
> 

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



From mailnull@www1.ietf.org  Tue Nov  5 16:16:08 2002
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA15229
	for <manet-archive@odin.ietf.org>; Tue, 5 Nov 2002 16:16:08 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id gA5LIBF09980
	for manet-archive@odin.ietf.org; Tue, 5 Nov 2002 16:18:11 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gA5LIBv09977
	for <manet-web-archive@optimus.ietf.org>; Tue, 5 Nov 2002 16:18:11 -0500
Received: from www1.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA15219
	for <manet-web-archive@ietf.org>; Tue, 5 Nov 2002 16:15:37 -0500 (EST)
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gA5L47v08755;
	Tue, 5 Nov 2002 16:04:07 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gA5Kxav08597
	for <manet@optimus.ietf.org>; Tue, 5 Nov 2002 15:59:36 -0500
Received: from barney.usu.edu (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA14053
	for <manet@ietf.org>; Tue, 5 Nov 2002 15:57:03 -0500 (EST)
Received: from D7KQ4P01 ("port 3632"@maxwell-6.ece.usu.edu [129.123.85.141])
 by cc.usu.edu (PMDF V5.2-32 #39089)
 with SMTP id <01KOIEZHB20490O07J@cc.usu.edu> for manet@ietf.org; Tue,
 5 Nov 2002 13:59:18 MST
Date: Tue, 05 Nov 2002 14:01:07 -0700
From: Sumeeth Nagaraj <snagaraj@cc.usu.edu>
Subject: Re: [manet] RTS/CTS in wireless MAC
To: Sachin Ganu <sachin@liman.rutgers.edu>,
        Grzegorz Banasiak <G.Banasiak@elka.pw.edu.pl>
Cc: manet@ietf.org
Message-id: <05c001c2850e$762a3870$8d557b81@D7KQ4P01>
MIME-version: 1.0
X-MIMEOLE: Produced By Microsoft MimeOLE V6.00.2800.1106
X-Mailer: Microsoft Outlook Express 6.00.2800.1106
Content-type: text/plain;	charset="iso-8859-1"
Content-transfer-encoding: 7bit
X-Priority: 3
X-MSMail-priority: Normal
References: <Pine.GSO.4.05.10211051003420.26532-100000@liman1>
Content-Transfer-Encoding: 7bit
Sender: manet-admin@ietf.org
Errors-To: manet-admin@ietf.org
X-BeenThere: manet@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/manet>,
	<mailto:manet-request@ietf.org?subject=unsubscribe>
List-Id: Mobile Ad-hoc Networks  <manet.ietf.org>
List-Post: <mailto:manet@ietf.org>
List-Help: <mailto:manet-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/manet>,
	<mailto:manet-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit

CSMA/ CD is used in the Ethernet, Collision Detection is not possible
because of the Half-Duplex nature of the nodes. The wireless nodes can
either transmit or receive and hence cannot detect collisions at the
destination(receiver). CSMA/CA is used and not CSMA/CD.

Best Regards,
Sumeeth


----- Original Message -----
From: "Sachin Ganu" <sachin@liman.rutgers.edu>
To: "Grzegorz Banasiak" <G.Banasiak@elka.pw.edu.pl>
Cc: <manet@ietf.org>
Sent: Tuesday, November 05, 2002 8:04 AM
Subject: Re: [manet] RTS/CTS in wireless MAC


>
> I do not think CSMA/CD is possible in MANET
>
> On Tue, 5 Nov 2002, Grzegorz Banasiak wrote:
>
> > On Mon, Nov 04, 2002 at 04:37:56PM -0800, idc@engineering.ucsb.edu
wrote:
> > > DCF (RTS-CTS-Data-ACK) is used only for unicast data.  CSMA/CA is used
> > > for broadcast packets.
> > DCF is a kind of CSMA/CA scheme (and so do PCF). I presume that
broadcast
> > packets are sent with CSMA/CD (i.e.  without any RTS/CTS/ACK handshake).
Am I
> > right?
> >
> > --
> > Grzegorz Banasiak
> > _______________________________________________
> > manet mailing list
> > manet@ietf.org
> > https://www1.ietf.org/mailman/listinfo/manet
> >
>
> _______________________________________________
> manet mailing list
> manet@ietf.org
> https://www1.ietf.org/mailman/listinfo/manet

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



From manet-admin@ietf.org  Tue Nov  5 16:16:09 2002
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA15242
	for <manet-archive@lists.ietf.org>; Tue, 5 Nov 2002 16:16:09 -0500 (EST)
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gA5L47v08755;
	Tue, 5 Nov 2002 16:04:07 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gA5Kxav08597
	for <manet@optimus.ietf.org>; Tue, 5 Nov 2002 15:59:36 -0500
Received: from barney.usu.edu (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA14053
	for <manet@ietf.org>; Tue, 5 Nov 2002 15:57:03 -0500 (EST)
Received: from D7KQ4P01 ("port 3632"@maxwell-6.ece.usu.edu [129.123.85.141])
 by cc.usu.edu (PMDF V5.2-32 #39089)
 with SMTP id <01KOIEZHB20490O07J@cc.usu.edu> for manet@ietf.org; Tue,
 5 Nov 2002 13:59:18 MST
Date: Tue, 05 Nov 2002 14:01:07 -0700
From: Sumeeth Nagaraj <snagaraj@cc.usu.edu>
Subject: Re: [manet] RTS/CTS in wireless MAC
To: Sachin Ganu <sachin@liman.rutgers.edu>,
        Grzegorz Banasiak <G.Banasiak@elka.pw.edu.pl>
Cc: manet@ietf.org
Message-id: <05c001c2850e$762a3870$8d557b81@D7KQ4P01>
MIME-version: 1.0
X-MIMEOLE: Produced By Microsoft MimeOLE V6.00.2800.1106
X-Mailer: Microsoft Outlook Express 6.00.2800.1106
Content-type: text/plain;	charset="iso-8859-1"
Content-transfer-encoding: 7bit
X-Priority: 3
X-MSMail-priority: Normal
References: <Pine.GSO.4.05.10211051003420.26532-100000@liman1>
Content-Transfer-Encoding: 7bit
Sender: manet-admin@ietf.org
Errors-To: manet-admin@ietf.org
X-BeenThere: manet@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/manet>,
	<mailto:manet-request@ietf.org?subject=unsubscribe>
List-Id: Mobile Ad-hoc Networks  <manet.ietf.org>
List-Post: <mailto:manet@ietf.org>
List-Help: <mailto:manet-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/manet>,
	<mailto:manet-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 7bit

CSMA/ CD is used in the Ethernet, Collision Detection is not possible
because of the Half-Duplex nature of the nodes. The wireless nodes can
either transmit or receive and hence cannot detect collisions at the
destination(receiver). CSMA/CA is used and not CSMA/CD.

Best Regards,
Sumeeth


----- Original Message -----
From: "Sachin Ganu" <sachin@liman.rutgers.edu>
To: "Grzegorz Banasiak" <G.Banasiak@elka.pw.edu.pl>
Cc: <manet@ietf.org>
Sent: Tuesday, November 05, 2002 8:04 AM
Subject: Re: [manet] RTS/CTS in wireless MAC


>
> I do not think CSMA/CD is possible in MANET
>
> On Tue, 5 Nov 2002, Grzegorz Banasiak wrote:
>
> > On Mon, Nov 04, 2002 at 04:37:56PM -0800, idc@engineering.ucsb.edu
wrote:
> > > DCF (RTS-CTS-Data-ACK) is used only for unicast data.  CSMA/CA is used
> > > for broadcast packets.
> > DCF is a kind of CSMA/CA scheme (and so do PCF). I presume that
broadcast
> > packets are sent with CSMA/CD (i.e.  without any RTS/CTS/ACK handshake).
Am I
> > right?
> >
> > --
> > Grzegorz Banasiak
> > _______________________________________________
> > manet mailing list
> > manet@ietf.org
> > https://www1.ietf.org/mailman/listinfo/manet
> >
>
> _______________________________________________
> manet mailing list
> manet@ietf.org
> https://www1.ietf.org/mailman/listinfo/manet

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


From mailnull@www1.ietf.org  Tue Nov  5 17:55:57 2002
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA22863
	for <manet-archive@odin.ietf.org>; Tue, 5 Nov 2002 17:55:57 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id gA5Mw2416802
	for manet-archive@odin.ietf.org; Tue, 5 Nov 2002 17:58:02 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gA5Mw1v16799
	for <manet-web-archive@optimus.ietf.org>; Tue, 5 Nov 2002 17:58:01 -0500
Received: from www1.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA22836
	for <manet-web-archive@ietf.org>; Tue, 5 Nov 2002 17:55:26 -0500 (EST)
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gA5MjWv16135;
	Tue, 5 Nov 2002 17:45:32 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gA5Mfnv15994
	for <manet@optimus.ietf.org>; Tue, 5 Nov 2002 17:41:49 -0500
Received: from itd.nrl.navy.mil (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA21560
	for <manet@ietf.org>; Tue, 5 Nov 2002 17:39:14 -0500 (EST)
Received: from smtp.itd.nrl.navy.mil (smtp.itd.nrl.navy.mil [132.250.86.3])
	by itd.nrl.navy.mil (8.8.8+Sun/8.8.8) with SMTP id RAA20243
	for <manet@ietf.org>; Tue, 5 Nov 2002 17:41:42 -0500 (EST)
Received: from SEXTANT.itd.nrl.navy.mil ([132.250.92.22])
 by smtp.itd.nrl.navy.mil (SAVSMTP 3.0.0.44) with SMTP id M2002110517414230303
 for <manet@ietf.org>; Tue, 05 Nov 2002 17:41:42 -0500
Message-Id: <5.1.1.5.2.20021105174051.0366fe98@pop.itd.nrl.navy.mil>
X-Sender: macker@pop.itd.nrl.navy.mil
X-Mailer: QUALCOMM Windows Eudora Version 5.1.1
Date: Tue, 05 Nov 2002 17:41:17 -0500
To: manet@ietf.org
From: Joe Macker <macker@itd.nrl.navy.mil>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Subject: [manet] Rough Agenda for Atlanta
Sender: manet-admin@ietf.org
Errors-To: manet-admin@ietf.org
X-BeenThere: manet@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/manet>,
	<mailto:manet-request@ietf.org?subject=unsubscribe>
List-Id: Mobile Ad-hoc Networks  <manet.ietf.org>
List-Post: <mailto:manet@ietf.org>
List-Help: <mailto:manet-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/manet>,
	<mailto:manet-request@ietf.org?subject=subscribe>

-------------------------------------------------------------
Mobile Ad Hoc Networks (manet) Agenda 
Thursday, Nov 21, 1500-1700

1. Agenda Bashing (5 min)
2. Proposed Manet WG Direction (20 min)
3. Strawman Proposal for Charter and Milestone Update (10 min)
4. Related IRTF Activity Announcement (10 min)
5. Open Discussion of Proposal and Issues (15 min)

Core ID Progress Updates

6. TBRPF Update (15 min)
	<draft-ietf-manet-tbrpf-06.txt>
7. DSR Update (15 min)
	<draft-ietf-manet-dsr-07.txt>
8. OLSR Update (15 min)
	<draft-ietf-manet-olsr-07.txt>
9. AODV Update (15 min)
	<draft-ietf-manet-aodv-12.txt>

10. Closing Discussion (10 min)
-----------------------------------------------------

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



From manet-admin@ietf.org  Tue Nov  5 17:55:59 2002
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA22876
	for <manet-archive@lists.ietf.org>; Tue, 5 Nov 2002 17:55:59 -0500 (EST)
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gA5MjWv16135;
	Tue, 5 Nov 2002 17:45:32 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gA5Mfnv15994
	for <manet@optimus.ietf.org>; Tue, 5 Nov 2002 17:41:49 -0500
Received: from itd.nrl.navy.mil (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA21560
	for <manet@ietf.org>; Tue, 5 Nov 2002 17:39:14 -0500 (EST)
Received: from smtp.itd.nrl.navy.mil (smtp.itd.nrl.navy.mil [132.250.86.3])
	by itd.nrl.navy.mil (8.8.8+Sun/8.8.8) with SMTP id RAA20243
	for <manet@ietf.org>; Tue, 5 Nov 2002 17:41:42 -0500 (EST)
Received: from SEXTANT.itd.nrl.navy.mil ([132.250.92.22])
 by smtp.itd.nrl.navy.mil (SAVSMTP 3.0.0.44) with SMTP id M2002110517414230303
 for <manet@ietf.org>; Tue, 05 Nov 2002 17:41:42 -0500
Message-Id: <5.1.1.5.2.20021105174051.0366fe98@pop.itd.nrl.navy.mil>
X-Sender: macker@pop.itd.nrl.navy.mil
X-Mailer: QUALCOMM Windows Eudora Version 5.1.1
Date: Tue, 05 Nov 2002 17:41:17 -0500
To: manet@ietf.org
From: Joe Macker <macker@itd.nrl.navy.mil>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Subject: [manet] Rough Agenda for Atlanta
Sender: manet-admin@ietf.org
Errors-To: manet-admin@ietf.org
X-BeenThere: manet@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/manet>,
	<mailto:manet-request@ietf.org?subject=unsubscribe>
List-Id: Mobile Ad-hoc Networks  <manet.ietf.org>
List-Post: <mailto:manet@ietf.org>
List-Help: <mailto:manet-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/manet>,
	<mailto:manet-request@ietf.org?subject=subscribe>

-------------------------------------------------------------
Mobile Ad Hoc Networks (manet) Agenda 
Thursday, Nov 21, 1500-1700

1. Agenda Bashing (5 min)
2. Proposed Manet WG Direction (20 min)
3. Strawman Proposal for Charter and Milestone Update (10 min)
4. Related IRTF Activity Announcement (10 min)
5. Open Discussion of Proposal and Issues (15 min)

Core ID Progress Updates

6. TBRPF Update (15 min)
	<draft-ietf-manet-tbrpf-06.txt>
7. DSR Update (15 min)
	<draft-ietf-manet-dsr-07.txt>
8. OLSR Update (15 min)
	<draft-ietf-manet-olsr-07.txt>
9. AODV Update (15 min)
	<draft-ietf-manet-aodv-12.txt>

10. Closing Discussion (10 min)
-----------------------------------------------------

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


From mailnull@www1.ietf.org  Tue Nov  5 18:42:50 2002
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA25175
	for <manet-archive@odin.ietf.org>; Tue, 5 Nov 2002 18:42:50 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id gA5Nitc19749
	for manet-archive@odin.ietf.org; Tue, 5 Nov 2002 18:44:55 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gA5Nitv19746
	for <manet-web-archive@optimus.ietf.org>; Tue, 5 Nov 2002 18:44:55 -0500
Received: from www1.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA25148
	for <manet-web-archive@ietf.org>; Tue, 5 Nov 2002 18:42:19 -0500 (EST)
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gA5NWFv18713;
	Tue, 5 Nov 2002 18:32:15 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gA5NR3v18494
	for <manet@optimus.ietf.org>; Tue, 5 Nov 2002 18:27:03 -0500
Received: from exstudent9.city.unisa.edu.au (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA24246
	for <manet@ietf.org>; Tue, 5 Nov 2002 18:24:27 -0500 (EST)
Received: by exstudent9.city.unisa.edu.au with Internet Mail Service (5.5.2656.59)
	id <V7J7T9KG>; Wed, 6 Nov 2002 09:56:45 +1030
Message-ID: <EF0CD96D4570FB4C9DD1E0E0D4F8031D0270A6E6@EXSTUDENTA.city.unisa.edu.au>
From: "Liaw, Yong Shyang - LIAYS001" <Yong.Liaw@postgrads.unisa.edu.au>
To: "'Sumeeth Nagaraj'" <snagaraj@cc.usu.edu>,
        Sachin Ganu
	 <sachin@liman.rutgers.edu>,
        Grzegorz Banasiak
	 <G.Banasiak@elka.pw.edu.pl>
Cc: manet@ietf.org
Subject: RE: [manet] RTS/CTS in wireless MAC
Date: Wed, 6 Nov 2002 10:00:16 +1030 
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2656.59)
Content-Type: text/plain;
	charset="iso-8859-1"
Sender: manet-admin@ietf.org
Errors-To: manet-admin@ietf.org
X-BeenThere: manet@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/manet>,
	<mailto:manet-request@ietf.org?subject=unsubscribe>
List-Id: Mobile Ad-hoc Networks  <manet.ietf.org>
List-Post: <mailto:manet@ietf.org>
List-Help: <mailto:manet-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/manet>,
	<mailto:manet-request@ietf.org?subject=subscribe>


So then how can the receiver knows if there is a collosion? Does it just check
the "checksum" of the data packet?  Another question. If the wireless LAN i/f
(i.e. waveLan) is put into promiscuous mode, it can receive all data
transmissions that reach it. But can it also send data (in promiscuous mode)
when it is not receiving data?

Thank in advance.



-----Original Message-----
From: Sumeeth Nagaraj [mailto:snagaraj@cc.usu.edu]
Sent: Wednesday, 6 November 2002 7:31
To: Sachin Ganu; Grzegorz Banasiak
Cc: manet@ietf.org
Subject: Re: [manet] RTS/CTS in wireless MAC


CSMA/ CD is used in the Ethernet, Collision Detection is not possible
because of the Half-Duplex nature of the nodes. The wireless nodes can
either transmit or receive and hence cannot detect collisions at the
destination(receiver). CSMA/CA is used and not CSMA/CD.

Best Regards,
Sumeeth


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



From manet-admin@ietf.org  Tue Nov  5 18:42:52 2002
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA25188
	for <manet-archive@lists.ietf.org>; Tue, 5 Nov 2002 18:42:51 -0500 (EST)
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gA5NWFv18713;
	Tue, 5 Nov 2002 18:32:15 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gA5NR3v18494
	for <manet@optimus.ietf.org>; Tue, 5 Nov 2002 18:27:03 -0500
Received: from exstudent9.city.unisa.edu.au (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA24246
	for <manet@ietf.org>; Tue, 5 Nov 2002 18:24:27 -0500 (EST)
Received: by exstudent9.city.unisa.edu.au with Internet Mail Service (5.5.2656.59)
	id <V7J7T9KG>; Wed, 6 Nov 2002 09:56:45 +1030
Message-ID: <EF0CD96D4570FB4C9DD1E0E0D4F8031D0270A6E6@EXSTUDENTA.city.unisa.edu.au>
From: "Liaw, Yong Shyang - LIAYS001" <Yong.Liaw@postgrads.unisa.edu.au>
To: "'Sumeeth Nagaraj'" <snagaraj@cc.usu.edu>,
        Sachin Ganu
	 <sachin@liman.rutgers.edu>,
        Grzegorz Banasiak
	 <G.Banasiak@elka.pw.edu.pl>
Cc: manet@ietf.org
Subject: RE: [manet] RTS/CTS in wireless MAC
Date: Wed, 6 Nov 2002 10:00:16 +1030 
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2656.59)
Content-Type: text/plain;
	charset="iso-8859-1"
Sender: manet-admin@ietf.org
Errors-To: manet-admin@ietf.org
X-BeenThere: manet@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/manet>,
	<mailto:manet-request@ietf.org?subject=unsubscribe>
List-Id: Mobile Ad-hoc Networks  <manet.ietf.org>
List-Post: <mailto:manet@ietf.org>
List-Help: <mailto:manet-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/manet>,
	<mailto:manet-request@ietf.org?subject=subscribe>


So then how can the receiver knows if there is a collosion? Does it just check
the "checksum" of the data packet?  Another question. If the wireless LAN i/f
(i.e. waveLan) is put into promiscuous mode, it can receive all data
transmissions that reach it. But can it also send data (in promiscuous mode)
when it is not receiving data?

Thank in advance.



-----Original Message-----
From: Sumeeth Nagaraj [mailto:snagaraj@cc.usu.edu]
Sent: Wednesday, 6 November 2002 7:31
To: Sachin Ganu; Grzegorz Banasiak
Cc: manet@ietf.org
Subject: Re: [manet] RTS/CTS in wireless MAC


CSMA/ CD is used in the Ethernet, Collision Detection is not possible
because of the Half-Duplex nature of the nodes. The wireless nodes can
either transmit or receive and hence cannot detect collisions at the
destination(receiver). CSMA/CA is used and not CSMA/CD.

Best Regards,
Sumeeth


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


From mailnull@www1.ietf.org  Tue Nov  5 19:00:20 2002
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA26158
	for <manet-archive@odin.ietf.org>; Tue, 5 Nov 2002 19:00:20 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id gA602PG20531
	for manet-archive@odin.ietf.org; Tue, 5 Nov 2002 19:02:25 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gA602Pv20528
	for <manet-web-archive@optimus.ietf.org>; Tue, 5 Nov 2002 19:02:25 -0500
Received: from www1.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA26142
	for <manet-web-archive@ietf.org>; Tue, 5 Nov 2002 18:59:49 -0500 (EST)
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gA5Nnxv19936;
	Tue, 5 Nov 2002 18:49:59 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gA5NjYv19787
	for <manet@optimus.ietf.org>; Tue, 5 Nov 2002 18:45:34 -0500
Received: from sneezy.usu.edu (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA25207
	for <manet@ietf.org>; Tue, 5 Nov 2002 18:42:58 -0500 (EST)
Received: from D7KQ4P01 ("port 4432"@maxwell-6.ece.usu.edu [129.123.85.141])
 by cc.usu.edu (PMDF V5.2-32 #39089)
 with SMTP id <01KOIKS9YBB48WWXR0@cc.usu.edu> for manet@ietf.org; Tue,
 5 Nov 2002 16:45:17 MST
Date: Tue, 05 Nov 2002 16:47:05 -0700
From: Sumeeth Nagaraj <snagaraj@cc.usu.edu>
Subject: Re: [manet] RTS/CTS in wireless MAC
To: "Liaw, Yong Shyang - LIAYS001" <Yong.Liaw@postgrads.unisa.edu.au>
Cc: manet@ietf.org
Message-id: <065201c28525$a64e2ae0$8d557b81@D7KQ4P01>
MIME-version: 1.0
X-MIMEOLE: Produced By Microsoft MimeOLE V6.00.2800.1106
X-Mailer: Microsoft Outlook Express 6.00.2800.1106
Content-type: text/plain;	charset="iso-8859-1"
Content-transfer-encoding: 7bit
X-Priority: 3
X-MSMail-priority: Normal
References: 
 <EF0CD96D4570FB4C9DD1E0E0D4F8031D0270A6E6@EXSTUDENTA.city.unisa.edu.au>
Content-Transfer-Encoding: 7bit
Sender: manet-admin@ietf.org
Errors-To: manet-admin@ietf.org
X-BeenThere: manet@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/manet>,
	<mailto:manet-request@ietf.org?subject=unsubscribe>
List-Id: Mobile Ad-hoc Networks  <manet.ietf.org>
List-Post: <mailto:manet@ietf.org>
List-Help: <mailto:manet-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/manet>,
	<mailto:manet-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit

CSMA-CA in Broadcast and not CSMA-CD?

I was referring to the transmitting node(Source) not being able to detect
collision at the destination node because of the half duplex nature of the
nodes and also because the source will not be knowing if the receiver(s) are
busy or idle and hence collision cannot be detected.

At the destination, collision is detected by checking the FCS field of the
received packet.

Best Regards,
Sumeeth

----- Original Message -----
From: "Liaw, Yong Shyang - LIAYS001" <Yong.Liaw@postgrads.unisa.edu.au>
To: "'Sumeeth Nagaraj'" <snagaraj@cc.usu.edu>; "Sachin Ganu"
<sachin@liman.rutgers.edu>; "Grzegorz Banasiak" <G.Banasiak@elka.pw.edu.pl>
Cc: <manet@ietf.org>
Sent: Tuesday, November 05, 2002 4:30 PM
Subject: RE: [manet] RTS/CTS in wireless MAC


>
> So then how can the receiver knows if there is a collosion? Does it just
check
> the "checksum" of the data packet?  Another question. If the wireless LAN
i/f
> (i.e. waveLan) is put into promiscuous mode, it can receive all data
> transmissions that reach it. But can it also send data (in promiscuous
mode)
> when it is not receiving data?
>
> Thank in advance.
>
>
>
> -----Original Message-----
> From: Sumeeth Nagaraj [mailto:snagaraj@cc.usu.edu]
> Sent: Wednesday, 6 November 2002 7:31
> To: Sachin Ganu; Grzegorz Banasiak
> Cc: manet@ietf.org
> Subject: Re: [manet] RTS/CTS in wireless MAC
>
>
> CSMA/ CD is used in the Ethernet, Collision Detection is not possible
> because of the Half-Duplex nature of the nodes. The wireless nodes can
> either transmit or receive and hence cannot detect collisions at the
> destination(receiver). CSMA/CA is used and not CSMA/CD.
>
> Best Regards,
> Sumeeth
>
>

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



From manet-admin@ietf.org  Tue Nov  5 19:00:22 2002
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA26172
	for <manet-archive@lists.ietf.org>; Tue, 5 Nov 2002 19:00:22 -0500 (EST)
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gA5Nnxv19936;
	Tue, 5 Nov 2002 18:49:59 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gA5NjYv19787
	for <manet@optimus.ietf.org>; Tue, 5 Nov 2002 18:45:34 -0500
Received: from sneezy.usu.edu (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA25207
	for <manet@ietf.org>; Tue, 5 Nov 2002 18:42:58 -0500 (EST)
Received: from D7KQ4P01 ("port 4432"@maxwell-6.ece.usu.edu [129.123.85.141])
 by cc.usu.edu (PMDF V5.2-32 #39089)
 with SMTP id <01KOIKS9YBB48WWXR0@cc.usu.edu> for manet@ietf.org; Tue,
 5 Nov 2002 16:45:17 MST
Date: Tue, 05 Nov 2002 16:47:05 -0700
From: Sumeeth Nagaraj <snagaraj@cc.usu.edu>
Subject: Re: [manet] RTS/CTS in wireless MAC
To: "Liaw, Yong Shyang - LIAYS001" <Yong.Liaw@postgrads.unisa.edu.au>
Cc: manet@ietf.org
Message-id: <065201c28525$a64e2ae0$8d557b81@D7KQ4P01>
MIME-version: 1.0
X-MIMEOLE: Produced By Microsoft MimeOLE V6.00.2800.1106
X-Mailer: Microsoft Outlook Express 6.00.2800.1106
Content-type: text/plain;	charset="iso-8859-1"
Content-transfer-encoding: 7bit
X-Priority: 3
X-MSMail-priority: Normal
References: 
 <EF0CD96D4570FB4C9DD1E0E0D4F8031D0270A6E6@EXSTUDENTA.city.unisa.edu.au>
Content-Transfer-Encoding: 7bit
Sender: manet-admin@ietf.org
Errors-To: manet-admin@ietf.org
X-BeenThere: manet@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/manet>,
	<mailto:manet-request@ietf.org?subject=unsubscribe>
List-Id: Mobile Ad-hoc Networks  <manet.ietf.org>
List-Post: <mailto:manet@ietf.org>
List-Help: <mailto:manet-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/manet>,
	<mailto:manet-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 7bit

CSMA-CA in Broadcast and not CSMA-CD?

I was referring to the transmitting node(Source) not being able to detect
collision at the destination node because of the half duplex nature of the
nodes and also because the source will not be knowing if the receiver(s) are
busy or idle and hence collision cannot be detected.

At the destination, collision is detected by checking the FCS field of the
received packet.

Best Regards,
Sumeeth

----- Original Message -----
From: "Liaw, Yong Shyang - LIAYS001" <Yong.Liaw@postgrads.unisa.edu.au>
To: "'Sumeeth Nagaraj'" <snagaraj@cc.usu.edu>; "Sachin Ganu"
<sachin@liman.rutgers.edu>; "Grzegorz Banasiak" <G.Banasiak@elka.pw.edu.pl>
Cc: <manet@ietf.org>
Sent: Tuesday, November 05, 2002 4:30 PM
Subject: RE: [manet] RTS/CTS in wireless MAC


>
> So then how can the receiver knows if there is a collosion? Does it just
check
> the "checksum" of the data packet?  Another question. If the wireless LAN
i/f
> (i.e. waveLan) is put into promiscuous mode, it can receive all data
> transmissions that reach it. But can it also send data (in promiscuous
mode)
> when it is not receiving data?
>
> Thank in advance.
>
>
>
> -----Original Message-----
> From: Sumeeth Nagaraj [mailto:snagaraj@cc.usu.edu]
> Sent: Wednesday, 6 November 2002 7:31
> To: Sachin Ganu; Grzegorz Banasiak
> Cc: manet@ietf.org
> Subject: Re: [manet] RTS/CTS in wireless MAC
>
>
> CSMA/ CD is used in the Ethernet, Collision Detection is not possible
> because of the Half-Duplex nature of the nodes. The wireless nodes can
> either transmit or receive and hence cannot detect collisions at the
> destination(receiver). CSMA/CA is used and not CSMA/CD.
>
> Best Regards,
> Sumeeth
>
>

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


From mailnull@www1.ietf.org  Wed Nov  6 03:57:41 2002
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id DAA09583
	for <manet-archive@odin.ietf.org>; Wed, 6 Nov 2002 03:57:41 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id gA68xol27216
	for manet-archive@odin.ietf.org; Wed, 6 Nov 2002 03:59:50 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gA68xov27213
	for <manet-web-archive@optimus.ietf.org>; Wed, 6 Nov 2002 03:59:50 -0500
Received: from www1.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id DAA09565
	for <manet-web-archive@ietf.org>; Wed, 6 Nov 2002 03:57:10 -0500 (EST)
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gA68kWv26509;
	Wed, 6 Nov 2002 03:46:32 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gA68hBv26403
	for <manet@optimus.ietf.org>; Wed, 6 Nov 2002 03:43:11 -0500
Received: from sm181.163.com (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id DAA09261
	for <manet@ietf.org>; Wed, 6 Nov 2002 03:40:27 -0500 (EST)
Received: from localhost (localhost [127.0.0.1])
	by sm181.163.com (Postfix) with SMTP id DC7961C660C60
	for <manet@ietf.org>; Wed,  6 Nov 2002 16:42:30 +0800 (CST)
Received: from RavProxy (unknown [61.187.64.26])
	by 192.168.1.181 (Coremail) with SMTP id f/4AAPXVyD2KAUAa.1
	for <manet@ietf.org>; Wed, 06 Nov 2002 16:42:30 +0800 (CST)
Message-ID: <002701c2856f$ef3a88d0$7600a8c0@zyn>
From: "Zhang Yanan" <csu_zyn@163.com>
To: <manet@ietf.org>
Date: Wed, 6 Nov 2002 16:38:51 +0800
MIME-Version: 1.0
Content-Type: multipart/alternative;
	boundary="----=_NextPart_000_0024_01C285B2.FD411910"
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 6.00.2600.0000
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2600.0000
Subject: [manet] How can I change the speed of delivered packet in glomosim?
Sender: manet-admin@ietf.org
Errors-To: manet-admin@ietf.org
X-BeenThere: manet@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/manet>,
	<mailto:manet-request@ietf.org?subject=unsubscribe>
List-Id: Mobile Ad-hoc Networks  <manet.ietf.org>
List-Post: <mailto:manet@ietf.org>
List-Help: <mailto:manet-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/manet>,
	<mailto:manet-request@ietf.org?subject=subscribe>

This is a multi-part message in MIME format.

------=_NextPart_000_0024_01C285B2.FD411910
Content-Type: text/plain;
	charset="gb2312"
Content-Transfer-Encoding: base64

SSB3YW50IHRvIGRvIGEgZXhwZXJpbWVudCB3aXRoIDQwIHRyYWZmaWMgc291cmNlcyBhbmQgYSBw
YWNrZXQgcmF0ZSBvZiBzb21lIHBhY2tldHMvcy4gd2hlcmUgY2FuIEkgY2hhbmdlIHRoaXMgcmF0
ZT8NCg==

------=_NextPart_000_0024_01C285B2.FD411910
Content-Type: text/html;
	charset="gb2312"
Content-Transfer-Encoding: base64

PCFET0NUWVBFIEhUTUwgUFVCTElDICItLy9XM0MvL0RURCBIVE1MIDQuMCBUcmFuc2l0aW9uYWwv
L0VOIj4NCjxIVE1MPjxIRUFEPg0KPE1FVEEgaHR0cC1lcXVpdj1Db250ZW50LVR5cGUgY29udGVu
dD0idGV4dC9odG1sOyBjaGFyc2V0PWdiMjMxMiI+DQo8TUVUQSBjb250ZW50PSJNU0hUTUwgNi4w
MC4yNjAwLjAiIG5hbWU9R0VORVJBVE9SPg0KPFNUWUxFPjwvU1RZTEU+DQo8L0hFQUQ+DQo8Qk9E
WSBiZ0NvbG9yPSNmZmZmZmY+DQo8RElWPg0KPERJVj48Rk9OVCBzaXplPTI+SSB3YW50IHRvIGRv
IGEgZXhwZXJpbWVudCB3aXRoIDQwIHRyYWZmaWMgc291cmNlcyBhbmQgYSBwYWNrZXQgDQpyYXRl
IG9mIHNvbWUgcGFja2V0cy9zLiB3aGVyZSZuYnNwO2NhbiBJIGNoYW5nZSB0aGlzIA0KcmF0ZT88
L0ZPTlQ+PC9ESVY+PC9ESVY+PC9CT0RZPjwvSFRNTD4NCg==

------=_NextPart_000_0024_01C285B2.FD411910--

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



From manet-admin@ietf.org  Wed Nov  6 03:57:43 2002
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id DAA09596
	for <manet-archive@lists.ietf.org>; Wed, 6 Nov 2002 03:57:43 -0500 (EST)
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gA68kWv26509;
	Wed, 6 Nov 2002 03:46:32 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gA68hBv26403
	for <manet@optimus.ietf.org>; Wed, 6 Nov 2002 03:43:11 -0500
Received: from sm181.163.com (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id DAA09261
	for <manet@ietf.org>; Wed, 6 Nov 2002 03:40:27 -0500 (EST)
Received: from localhost (localhost [127.0.0.1])
	by sm181.163.com (Postfix) with SMTP id DC7961C660C60
	for <manet@ietf.org>; Wed,  6 Nov 2002 16:42:30 +0800 (CST)
Received: from RavProxy (unknown [61.187.64.26])
	by 192.168.1.181 (Coremail) with SMTP id f/4AAPXVyD2KAUAa.1
	for <manet@ietf.org>; Wed, 06 Nov 2002 16:42:30 +0800 (CST)
Message-ID: <002701c2856f$ef3a88d0$7600a8c0@zyn>
From: "Zhang Yanan" <csu_zyn@163.com>
To: <manet@ietf.org>
Date: Wed, 6 Nov 2002 16:38:51 +0800
MIME-Version: 1.0
Content-Type: multipart/alternative;
	boundary="----=_NextPart_000_0024_01C285B2.FD411910"
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 6.00.2600.0000
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2600.0000
Subject: [manet] How can I change the speed of delivered packet in glomosim?
Sender: manet-admin@ietf.org
Errors-To: manet-admin@ietf.org
X-BeenThere: manet@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/manet>,
	<mailto:manet-request@ietf.org?subject=unsubscribe>
List-Id: Mobile Ad-hoc Networks  <manet.ietf.org>
List-Post: <mailto:manet@ietf.org>
List-Help: <mailto:manet-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/manet>,
	<mailto:manet-request@ietf.org?subject=subscribe>

This is a multi-part message in MIME format.

------=_NextPart_000_0024_01C285B2.FD411910
Content-Type: text/plain;
	charset="gb2312"
Content-Transfer-Encoding: base64

SSB3YW50IHRvIGRvIGEgZXhwZXJpbWVudCB3aXRoIDQwIHRyYWZmaWMgc291cmNlcyBhbmQgYSBw
YWNrZXQgcmF0ZSBvZiBzb21lIHBhY2tldHMvcy4gd2hlcmUgY2FuIEkgY2hhbmdlIHRoaXMgcmF0
ZT8NCg==

------=_NextPart_000_0024_01C285B2.FD411910
Content-Type: text/html;
	charset="gb2312"
Content-Transfer-Encoding: base64

PCFET0NUWVBFIEhUTUwgUFVCTElDICItLy9XM0MvL0RURCBIVE1MIDQuMCBUcmFuc2l0aW9uYWwv
L0VOIj4NCjxIVE1MPjxIRUFEPg0KPE1FVEEgaHR0cC1lcXVpdj1Db250ZW50LVR5cGUgY29udGVu
dD0idGV4dC9odG1sOyBjaGFyc2V0PWdiMjMxMiI+DQo8TUVUQSBjb250ZW50PSJNU0hUTUwgNi4w
MC4yNjAwLjAiIG5hbWU9R0VORVJBVE9SPg0KPFNUWUxFPjwvU1RZTEU+DQo8L0hFQUQ+DQo8Qk9E
WSBiZ0NvbG9yPSNmZmZmZmY+DQo8RElWPg0KPERJVj48Rk9OVCBzaXplPTI+SSB3YW50IHRvIGRv
IGEgZXhwZXJpbWVudCB3aXRoIDQwIHRyYWZmaWMgc291cmNlcyBhbmQgYSBwYWNrZXQgDQpyYXRl
IG9mIHNvbWUgcGFja2V0cy9zLiB3aGVyZSZuYnNwO2NhbiBJIGNoYW5nZSB0aGlzIA0KcmF0ZT88
L0ZPTlQ+PC9ESVY+PC9ESVY+PC9CT0RZPjwvSFRNTD4NCg==

------=_NextPart_000_0024_01C285B2.FD411910--

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


From manet-admin@ietf.org  Wed Nov  6 11:05:19 2002
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA29193
	for <manet-archive@lists.ietf.org>; Wed, 6 Nov 2002 11:05:19 -0500 (EST)
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gA6Fwav23059;
	Wed, 6 Nov 2002 10:58:36 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gA6FqBv22874
	for <manet@optimus.ietf.org>; Wed, 6 Nov 2002 10:52:11 -0500
Received: from itd.nrl.navy.mil (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA28140
	for <manet@ietf.org>; Wed, 6 Nov 2002 10:49:38 -0500 (EST)
Received: from smtp.itd.nrl.navy.mil (smtp.itd.nrl.navy.mil [132.250.86.3])
	by itd.nrl.navy.mil (8.8.8+Sun/8.8.8) with SMTP id KAA23878
	for <manet@ietf.org>; Wed, 6 Nov 2002 10:52:05 -0500 (EST)
Received: from SEXTANT.itd.nrl.navy.mil ([132.250.92.22])
 by smtp.itd.nrl.navy.mil (SAVSMTP 3.0.0.44) with SMTP id M2002110610520532024
 for <manet@ietf.org>; Wed, 06 Nov 2002 10:52:05 -0500
Message-Id: <5.1.1.5.2.20021106103420.0390a3c0@pop.itd.nrl.navy.mil>
X-Sender: macker@pop.itd.nrl.navy.mil
X-Mailer: QUALCOMM Windows Eudora Version 5.1.1
Date: Wed, 06 Nov 2002 10:51:36 -0500
To: <manet@ietf.org>
From: Joe Macker <macker@itd.nrl.navy.mil>
In-Reply-To: <002701c2856f$ef3a88d0$7600a8c0@zyn>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Subject: [manet] Increasing number of simulation questions on manet list
Sender: manet-admin@ietf.org
Errors-To: manet-admin@ietf.org
X-BeenThere: manet@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/manet>,
	<mailto:manet-request@ietf.org?subject=unsubscribe>
List-Id: Mobile Ad-hoc Networks  <manet.ietf.org>
List-Post: <mailto:manet@ietf.org>
List-Help: <mailto:manet-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/manet>,
	<mailto:manet-request@ietf.org?subject=subscribe>

REMINDER:
I am noticing an increasing number of broad-based simulator questions to this list.  There are other appropriate forums for detailed simulation environment related technical questions.
There is an ns2 mailing list, etc..and this list is responsive typically....

Let's try to limit manet list discussions to IETF related work issues..WG related protocol questions/discussions and announcements are fine. Use your best judgement there.
-joe 

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


From mailnull@www1.ietf.org  Wed Nov  6 11:16:36 2002
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA29776
	for <manet-archive@odin.ietf.org>; Wed, 6 Nov 2002 11:16:36 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id gA6GIb724807
	for manet-archive@odin.ietf.org; Wed, 6 Nov 2002 11:18:37 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gA6GIbv24804
	for <manet-web-archive@optimus.ietf.org>; Wed, 6 Nov 2002 11:18:37 -0500
Received: from www1.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA29740
	for <manet-web-archive@ietf.org>; Wed, 6 Nov 2002 11:16:05 -0500 (EST)
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gA6Fwav23059;
	Wed, 6 Nov 2002 10:58:36 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gA6FqBv22874
	for <manet@optimus.ietf.org>; Wed, 6 Nov 2002 10:52:11 -0500
Received: from itd.nrl.navy.mil (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA28140
	for <manet@ietf.org>; Wed, 6 Nov 2002 10:49:38 -0500 (EST)
Received: from smtp.itd.nrl.navy.mil (smtp.itd.nrl.navy.mil [132.250.86.3])
	by itd.nrl.navy.mil (8.8.8+Sun/8.8.8) with SMTP id KAA23878
	for <manet@ietf.org>; Wed, 6 Nov 2002 10:52:05 -0500 (EST)
Received: from SEXTANT.itd.nrl.navy.mil ([132.250.92.22])
 by smtp.itd.nrl.navy.mil (SAVSMTP 3.0.0.44) with SMTP id M2002110610520532024
 for <manet@ietf.org>; Wed, 06 Nov 2002 10:52:05 -0500
Message-Id: <5.1.1.5.2.20021106103420.0390a3c0@pop.itd.nrl.navy.mil>
X-Sender: macker@pop.itd.nrl.navy.mil
X-Mailer: QUALCOMM Windows Eudora Version 5.1.1
Date: Wed, 06 Nov 2002 10:51:36 -0500
To: <manet@ietf.org>
From: Joe Macker <macker@itd.nrl.navy.mil>
In-Reply-To: <002701c2856f$ef3a88d0$7600a8c0@zyn>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Subject: [manet] Increasing number of simulation questions on manet list
Sender: manet-admin@ietf.org
Errors-To: manet-admin@ietf.org
X-BeenThere: manet@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/manet>,
	<mailto:manet-request@ietf.org?subject=unsubscribe>
List-Id: Mobile Ad-hoc Networks  <manet.ietf.org>
List-Post: <mailto:manet@ietf.org>
List-Help: <mailto:manet-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/manet>,
	<mailto:manet-request@ietf.org?subject=subscribe>

REMINDER:
I am noticing an increasing number of broad-based simulator questions to this list.  There are other appropriate forums for detailed simulation environment related technical questions.
There is an ns2 mailing list, etc..and this list is responsive typically....

Let's try to limit manet list discussions to IETF related work issues..WG related protocol questions/discussions and announcements are fine. Use your best judgement there.
-joe 

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



From mailnull@www1.ietf.org  Wed Nov  6 11:43:32 2002
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA00933
	for <manet-archive@odin.ietf.org>; Wed, 6 Nov 2002 11:43:32 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id gA6GjYQ27060
	for manet-archive@odin.ietf.org; Wed, 6 Nov 2002 11:45:34 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gA6GjYv27057
	for <manet-web-archive@optimus.ietf.org>; Wed, 6 Nov 2002 11:45:34 -0500
Received: from www1.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA00925
	for <manet-web-archive@ietf.org>; Wed, 6 Nov 2002 11:43:01 -0500 (EST)
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gA6Gbiv26584;
	Wed, 6 Nov 2002 11:37:44 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gA6GaAv25929
	for <manet@optimus.ietf.org>; Wed, 6 Nov 2002 11:36:10 -0500
Received: from meryl.it.uu.se (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA00534
	for <manet@ietf.org>; Wed, 6 Nov 2002 11:33:37 -0500 (EST)
Received: from nebulosa.it.uu.se (nebulosa.it.uu.se [130.238.8.24])
	by meryl.it.uu.se (8.8.5/8.8.5) with ESMTP id RAA02065;
	Wed, 6 Nov 2002 17:36:05 +0100 (MET)
From: Erik =?ISO-8859-1?Q?Nordstr=F6m?= <erik.nordstrom@it.uu.se>
To: MANET LIST <manet@ietf.org>
Cc: Aodvimpl-Public <aodvimpl-public@lists.sourceforge.net>
Content-Type: text/plain; charset=ISO-8859-1
Message-Id: <1036600565.26947.61.camel@nebulosa.it.uu.se>
Mime-Version: 1.0
X-Mailer: Ximian Evolution 1.1.90 (Preview Release)
Date: 06 Nov 2002 17:36:05 +0100
Content-Transfer-Encoding: 8bit
Content-Transfer-Encoding: 8bit
Subject: [manet] AODV-UU v0.6 released!
Sender: manet-admin@ietf.org
Errors-To: manet-admin@ietf.org
X-BeenThere: manet@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/manet>,
	<mailto:manet-request@ietf.org?subject=unsubscribe>
List-Id: Mobile Ad-hoc Networks  <manet.ietf.org>
List-Post: <mailto:manet@ietf.org>
List-Help: <mailto:manet-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/manet>,
	<mailto:manet-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 8bit
Content-Transfer-Encoding: 8bit

Hello

I would like to announce the availability of version 0.6 of AODV-UU.

AODV-UU is an AODV implementation that runs both in a real world setting
on Linux and in the ns-2 simulation environment. From our experience the
performance of AODV-UU is equal to or better than the AODV
implementation in ns-2. Furthermore, it is more compliant to the draft
and therefore better reflects the real performance of the AODV protocol.

This version complies with version 11 of the AODV draft.

The code also contains custom modifications and extensions to deal with
"Communication Gray Zones": 
http://www.docs.uu.se/docs/research/projects/scanet/aodv/grayzones.pdf

You can find information and source code to download at the AODV-UU
webpage:

http://www.docs.uu.se/docs/research/projects/scanet/aodv/

-- 
Erik Nordström <erik.nordstrom@it.uu.se>, Uppsala University, Sweden.



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



From manet-admin@ietf.org  Wed Nov  6 11:43:34 2002
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA00946
	for <manet-archive@lists.ietf.org>; Wed, 6 Nov 2002 11:43:34 -0500 (EST)
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gA6Gbiv26584;
	Wed, 6 Nov 2002 11:37:44 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gA6GaAv25929
	for <manet@optimus.ietf.org>; Wed, 6 Nov 2002 11:36:10 -0500
Received: from meryl.it.uu.se (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA00534
	for <manet@ietf.org>; Wed, 6 Nov 2002 11:33:37 -0500 (EST)
Received: from nebulosa.it.uu.se (nebulosa.it.uu.se [130.238.8.24])
	by meryl.it.uu.se (8.8.5/8.8.5) with ESMTP id RAA02065;
	Wed, 6 Nov 2002 17:36:05 +0100 (MET)
From: Erik =?ISO-8859-1?Q?Nordstr=F6m?= <erik.nordstrom@it.uu.se>
To: MANET LIST <manet@ietf.org>
Cc: Aodvimpl-Public <aodvimpl-public@lists.sourceforge.net>
Content-Type: text/plain; charset=ISO-8859-1
Message-Id: <1036600565.26947.61.camel@nebulosa.it.uu.se>
Mime-Version: 1.0
X-Mailer: Ximian Evolution 1.1.90 (Preview Release)
Date: 06 Nov 2002 17:36:05 +0100
Content-Transfer-Encoding: 8bit
Content-Transfer-Encoding: 8bit
Subject: [manet] AODV-UU v0.6 released!
Sender: manet-admin@ietf.org
Errors-To: manet-admin@ietf.org
X-BeenThere: manet@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/manet>,
	<mailto:manet-request@ietf.org?subject=unsubscribe>
List-Id: Mobile Ad-hoc Networks  <manet.ietf.org>
List-Post: <mailto:manet@ietf.org>
List-Help: <mailto:manet-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/manet>,
	<mailto:manet-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 8bit

Hello

I would like to announce the availability of version 0.6 of AODV-UU.

AODV-UU is an AODV implementation that runs both in a real world setting
on Linux and in the ns-2 simulation environment. From our experience the
performance of AODV-UU is equal to or better than the AODV
implementation in ns-2. Furthermore, it is more compliant to the draft
and therefore better reflects the real performance of the AODV protocol.

This version complies with version 11 of the AODV draft.

The code also contains custom modifications and extensions to deal with
"Communication Gray Zones": 
http://www.docs.uu.se/docs/research/projects/scanet/aodv/grayzones.pdf

You can find information and source code to download at the AODV-UU
webpage:

http://www.docs.uu.se/docs/research/projects/scanet/aodv/

-- 
Erik Nordström <erik.nordstrom@it.uu.se>, Uppsala University, Sweden.



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


From manet-admin@ietf.org  Wed Nov  6 17:06:52 2002
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA14835
	for <manet-archive@lists.ietf.org>; Wed, 6 Nov 2002 17:06:52 -0500 (EST)
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gA6Llpv14592;
	Wed, 6 Nov 2002 16:47:51 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gA6LjYv14490
	for <manet@optimus.ietf.org>; Wed, 6 Nov 2002 16:45:34 -0500
Received: from strix.ciens.ucv.ve (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA13770
	for <manet@ietf.org>; Wed, 6 Nov 2002 16:42:54 -0500 (EST)
Received: from dircompucv2.strix.ciens.ucv.ve (dircompucv.ciens.ucv.ve [150.185.75.85])
	by strix.ciens.ucv.ve (SGI-8.9.3/8.9.3) with ESMTP id RAA33410
	for <manet@ietf.org>; Wed, 6 Nov 2002 17:46:10 -0800 (PST)
Message-Id: <5.0.0.25.0.20021106173135.0266aeb0@strix.ciens.ucv.ve>
X-Sender: dcobos@strix.ciens.ucv.ve
X-Mailer: QUALCOMM Windows Eudora Version 5.0
Date: Wed, 06 Nov 2002 17:48:08 -0400
To: manet@ietf.org
From: Denis Cobos <dcobos@strix.ciens.ucv.ve>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
Subject: [manet] !!!About simulation's methodology!!
Sender: manet-admin@ietf.org
Errors-To: manet-admin@ietf.org
X-BeenThere: manet@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/manet>,
	<mailto:manet-request@ietf.org?subject=unsubscribe>
List-Id: Mobile Ad-hoc Networks  <manet.ietf.org>
List-Post: <mailto:manet@ietf.org>
List-Help: <mailto:manet-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/manet>,
	<mailto:manet-request@ietf.org?subject=subscribe>

Hi
Does anyone know some reference about methodology of simulation for mobile 
ad hoc network, also I want to know about another simulators like NS-2 y OPNET

thanks

Central University of Venezuela
sciences faculty
Computation's School
ICARO

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


From mailnull@www1.ietf.org  Wed Nov  6 17:10:32 2002
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA14904
	for <manet-archive@odin.ietf.org>; Wed, 6 Nov 2002 17:10:32 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id gA6MCaR16837
	for manet-archive@odin.ietf.org; Wed, 6 Nov 2002 17:12:36 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gA6MCav16834
	for <manet-web-archive@optimus.ietf.org>; Wed, 6 Nov 2002 17:12:36 -0500
Received: from www1.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA14897
	for <manet-web-archive@ietf.org>; Wed, 6 Nov 2002 17:10:01 -0500 (EST)
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gA6Llpv14592;
	Wed, 6 Nov 2002 16:47:51 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gA6LjYv14490
	for <manet@optimus.ietf.org>; Wed, 6 Nov 2002 16:45:34 -0500
Received: from strix.ciens.ucv.ve (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA13770
	for <manet@ietf.org>; Wed, 6 Nov 2002 16:42:54 -0500 (EST)
Received: from dircompucv2.strix.ciens.ucv.ve (dircompucv.ciens.ucv.ve [150.185.75.85])
	by strix.ciens.ucv.ve (SGI-8.9.3/8.9.3) with ESMTP id RAA33410
	for <manet@ietf.org>; Wed, 6 Nov 2002 17:46:10 -0800 (PST)
Message-Id: <5.0.0.25.0.20021106173135.0266aeb0@strix.ciens.ucv.ve>
X-Sender: dcobos@strix.ciens.ucv.ve
X-Mailer: QUALCOMM Windows Eudora Version 5.0
Date: Wed, 06 Nov 2002 17:48:08 -0400
To: manet@ietf.org
From: Denis Cobos <dcobos@strix.ciens.ucv.ve>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
Subject: [manet] !!!About simulation's methodology!!
Sender: manet-admin@ietf.org
Errors-To: manet-admin@ietf.org
X-BeenThere: manet@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/manet>,
	<mailto:manet-request@ietf.org?subject=unsubscribe>
List-Id: Mobile Ad-hoc Networks  <manet.ietf.org>
List-Post: <mailto:manet@ietf.org>
List-Help: <mailto:manet-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/manet>,
	<mailto:manet-request@ietf.org?subject=subscribe>

Hi
Does anyone know some reference about methodology of simulation for mobile 
ad hoc network, also I want to know about another simulators like NS-2 y OPNET

thanks

Central University of Venezuela
sciences faculty
Computation's School
ICARO

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



From mailnull@www1.ietf.org  Wed Nov  6 21:16:05 2002
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id VAA20070
	for <manet-archive@odin.ietf.org>; Wed, 6 Nov 2002 21:16:05 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id gA72IAo29711
	for manet-archive@odin.ietf.org; Wed, 6 Nov 2002 21:18:10 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gA72IAv29708
	for <manet-web-archive@optimus.ietf.org>; Wed, 6 Nov 2002 21:18:10 -0500
Received: from www1.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id VAA20047
	for <manet-web-archive@ietf.org>; Wed, 6 Nov 2002 21:15:34 -0500 (EST)
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gA725Xv28600;
	Wed, 6 Nov 2002 21:05:33 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gA723Yv28461
	for <manet@optimus.ietf.org>; Wed, 6 Nov 2002 21:03:34 -0500
Received: from sm181.163.com (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id VAA19707
	for <manet@ietf.org>; Wed, 6 Nov 2002 21:00:55 -0500 (EST)
Received: from localhost (localhost [127.0.0.1])
	by sm181.163.com (Postfix) with SMTP id 282D81C959584
	for <manet@ietf.org>; Thu,  7 Nov 2002 10:03:14 +0800 (CST)
Received: from RavProxy (unknown [61.187.64.26])
	by 192.168.1.181 (Coremail) with SMTP id 6gIAAODJyT2vEEAa.1
	for <manet@ietf.org>; Thu, 07 Nov 2002 10:03:14 +0800 (CST)
Message-ID: <000c01c28601$4a805990$7600a8c0@zyn>
From: "Zhang Yanan" <csu_zyn@163.com>
To: <manet@ietf.org>
Date: Thu, 7 Nov 2002 09:59:21 +0800
MIME-Version: 1.0
Content-Type: multipart/alternative;
	boundary="----=_NextPart_000_0009_01C28644.58718D10"
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 6.00.2600.0000
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2600.0000
Subject: [manet] Change the rate of delivered packet
Sender: manet-admin@ietf.org
Errors-To: manet-admin@ietf.org
X-BeenThere: manet@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/manet>,
	<mailto:manet-request@ietf.org?subject=unsubscribe>
List-Id: Mobile Ad-hoc Networks  <manet.ietf.org>
List-Post: <mailto:manet@ietf.org>
List-Help: <mailto:manet-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/manet>,
	<mailto:manet-request@ietf.org?subject=subscribe>

This is a multi-part message in MIME format.

------=_NextPart_000_0009_01C28644.58718D10
Content-Type: text/plain;
	charset="gb2312"
Content-Transfer-Encoding: base64

aGksDQpJJ20gZG9pbmcgc29tZXRoaW5nIG9uIGdsb21vc2ltLg0KSSB3YW50IHRvIGRvIGEgZXhw
ZXJpbWVudCB3aXRoIDQwIHRyYWZmaWMgc291cmNlcyBhbmQgYSBwYWNrZXQgcmF0ZSBvZiA0IHBh
Y2tldHMvcy4gd2hlcmUgY2FuIEkgY2hhbmdlIHRoaXMgcmF0ZT8gDQpJIGZpbmQgdGhlcmUncyBh
IENCUiBpbnRlcnZhbCwgaXMgdGhpcz8NCg==

------=_NextPart_000_0009_01C28644.58718D10
Content-Type: text/html;
	charset="gb2312"
Content-Transfer-Encoding: base64

PCFET0NUWVBFIEhUTUwgUFVCTElDICItLy9XM0MvL0RURCBIVE1MIDQuMCBUcmFuc2l0aW9uYWwv
L0VOIj4NCjxIVE1MPjxIRUFEPg0KPE1FVEEgaHR0cC1lcXVpdj1Db250ZW50LVR5cGUgY29udGVu
dD0idGV4dC9odG1sOyBjaGFyc2V0PWdiMjMxMiI+DQo8TUVUQSBjb250ZW50PSJNU0hUTUwgNi4w
MC4yNjAwLjAiIG5hbWU9R0VORVJBVE9SPg0KPFNUWUxFPjwvU1RZTEU+DQo8L0hFQUQ+DQo8Qk9E
WSBiZ0NvbG9yPSNmZmZmZmY+DQo8RElWPjxGT05UIHNpemU9Mj5oaSw8L0ZPTlQ+PC9ESVY+DQo8
RElWPjxGT05UIHNpemU9Mj5JJ20gZG9pbmcgc29tZXRoaW5nIG9uIGdsb21vc2ltLjwvRk9OVD48
L0RJVj4NCjxESVY+DQo8RElWPjxGT05UIHNpemU9Mj5JIHdhbnQgdG8gZG8gYSBleHBlcmltZW50
IHdpdGggNDAgdHJhZmZpYyBzb3VyY2VzIGFuZCBhIHBhY2tldCANCnJhdGUgb2YmbmJzcDs0IHBh
Y2tldHMvcy4gd2hlcmUmbmJzcDtjYW4gSSBjaGFuZ2UgdGhpcyByYXRlPyA8L0ZPTlQ+PC9ESVY+
DQo8RElWPjxGT05UIHNpemU9Mj5JIGZpbmQgdGhlcmUncyBhIENCUiBpbnRlcnZhbCwgaXMgDQp0
aGlzPzwvRk9OVD48L0RJVj48L0RJVj48L0JPRFk+PC9IVE1MPg0K

------=_NextPart_000_0009_01C28644.58718D10--

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



From manet-admin@ietf.org  Wed Nov  6 21:16:07 2002
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id VAA20083
	for <manet-archive@lists.ietf.org>; Wed, 6 Nov 2002 21:16:07 -0500 (EST)
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gA725Xv28600;
	Wed, 6 Nov 2002 21:05:33 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gA723Yv28461
	for <manet@optimus.ietf.org>; Wed, 6 Nov 2002 21:03:34 -0500
Received: from sm181.163.com (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id VAA19707
	for <manet@ietf.org>; Wed, 6 Nov 2002 21:00:55 -0500 (EST)
Received: from localhost (localhost [127.0.0.1])
	by sm181.163.com (Postfix) with SMTP id 282D81C959584
	for <manet@ietf.org>; Thu,  7 Nov 2002 10:03:14 +0800 (CST)
Received: from RavProxy (unknown [61.187.64.26])
	by 192.168.1.181 (Coremail) with SMTP id 6gIAAODJyT2vEEAa.1
	for <manet@ietf.org>; Thu, 07 Nov 2002 10:03:14 +0800 (CST)
Message-ID: <000c01c28601$4a805990$7600a8c0@zyn>
From: "Zhang Yanan" <csu_zyn@163.com>
To: <manet@ietf.org>
Date: Thu, 7 Nov 2002 09:59:21 +0800
MIME-Version: 1.0
Content-Type: multipart/alternative;
	boundary="----=_NextPart_000_0009_01C28644.58718D10"
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 6.00.2600.0000
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2600.0000
Subject: [manet] Change the rate of delivered packet
Sender: manet-admin@ietf.org
Errors-To: manet-admin@ietf.org
X-BeenThere: manet@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/manet>,
	<mailto:manet-request@ietf.org?subject=unsubscribe>
List-Id: Mobile Ad-hoc Networks  <manet.ietf.org>
List-Post: <mailto:manet@ietf.org>
List-Help: <mailto:manet-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/manet>,
	<mailto:manet-request@ietf.org?subject=subscribe>

This is a multi-part message in MIME format.

------=_NextPart_000_0009_01C28644.58718D10
Content-Type: text/plain;
	charset="gb2312"
Content-Transfer-Encoding: base64

aGksDQpJJ20gZG9pbmcgc29tZXRoaW5nIG9uIGdsb21vc2ltLg0KSSB3YW50IHRvIGRvIGEgZXhw
ZXJpbWVudCB3aXRoIDQwIHRyYWZmaWMgc291cmNlcyBhbmQgYSBwYWNrZXQgcmF0ZSBvZiA0IHBh
Y2tldHMvcy4gd2hlcmUgY2FuIEkgY2hhbmdlIHRoaXMgcmF0ZT8gDQpJIGZpbmQgdGhlcmUncyBh
IENCUiBpbnRlcnZhbCwgaXMgdGhpcz8NCg==

------=_NextPart_000_0009_01C28644.58718D10
Content-Type: text/html;
	charset="gb2312"
Content-Transfer-Encoding: base64

PCFET0NUWVBFIEhUTUwgUFVCTElDICItLy9XM0MvL0RURCBIVE1MIDQuMCBUcmFuc2l0aW9uYWwv
L0VOIj4NCjxIVE1MPjxIRUFEPg0KPE1FVEEgaHR0cC1lcXVpdj1Db250ZW50LVR5cGUgY29udGVu
dD0idGV4dC9odG1sOyBjaGFyc2V0PWdiMjMxMiI+DQo8TUVUQSBjb250ZW50PSJNU0hUTUwgNi4w
MC4yNjAwLjAiIG5hbWU9R0VORVJBVE9SPg0KPFNUWUxFPjwvU1RZTEU+DQo8L0hFQUQ+DQo8Qk9E
WSBiZ0NvbG9yPSNmZmZmZmY+DQo8RElWPjxGT05UIHNpemU9Mj5oaSw8L0ZPTlQ+PC9ESVY+DQo8
RElWPjxGT05UIHNpemU9Mj5JJ20gZG9pbmcgc29tZXRoaW5nIG9uIGdsb21vc2ltLjwvRk9OVD48
L0RJVj4NCjxESVY+DQo8RElWPjxGT05UIHNpemU9Mj5JIHdhbnQgdG8gZG8gYSBleHBlcmltZW50
IHdpdGggNDAgdHJhZmZpYyBzb3VyY2VzIGFuZCBhIHBhY2tldCANCnJhdGUgb2YmbmJzcDs0IHBh
Y2tldHMvcy4gd2hlcmUmbmJzcDtjYW4gSSBjaGFuZ2UgdGhpcyByYXRlPyA8L0ZPTlQ+PC9ESVY+
DQo8RElWPjxGT05UIHNpemU9Mj5JIGZpbmQgdGhlcmUncyBhIENCUiBpbnRlcnZhbCwgaXMgDQp0
aGlzPzwvRk9OVD48L0RJVj48L0RJVj48L0JPRFk+PC9IVE1MPg0K

------=_NextPart_000_0009_01C28644.58718D10--

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


From mailnull@www1.ietf.org  Wed Nov  6 21:42:52 2002
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id VAA21121
	for <manet-archive@odin.ietf.org>; Wed, 6 Nov 2002 21:42:51 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id gA72ivY31443
	for manet-archive@odin.ietf.org; Wed, 6 Nov 2002 21:44:57 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gA72ivv31440
	for <manet-web-archive@optimus.ietf.org>; Wed, 6 Nov 2002 21:44:57 -0500
Received: from www1.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id VAA21106
	for <manet-web-archive@ietf.org>; Wed, 6 Nov 2002 21:42:20 -0500 (EST)
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gA72YGv30386;
	Wed, 6 Nov 2002 21:34:16 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gA72X7v30339
	for <manet@optimus.ietf.org>; Wed, 6 Nov 2002 21:33:07 -0500
Received: from bjapp7.163.net (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id VAA20387
	for <manet@ietf.org>; Wed, 6 Nov 2002 21:30:25 -0500 (EST)
Received: from localhost (localhost [127.0.0.1])
	by bjapp7.163.net (Postfix) with SMTP id 1C4091C85FC61
	for <manet@ietf.org>; Thu,  7 Nov 2002 10:32:51 +0800 (CST)
Received: from befine (unknown [211.71.13.13])
	by bjapp7.163.net (Coremail) with SMTP id XgIAANLQyT30RQ0N.1
	for <manet@ietf.org>; Thu, 07 Nov 2002 10:32:51 +0800 (CST)
Date: Thu, 7 Nov 2002 10:30:58 +0800
From: "Harry" <hr_befine@163.net>
Reply-To: hr_befine@163.net
To: MANET mail list <manet@ietf.org>
X-mailer: Foxmail 4.1 [cn]
Mime-Version: 1.0
Content-Type: text/plain;
      charset="GB2312"
Message-Id: <20021107023251.1C4091C85FC61@bjapp7.163.net>
Content-Transfer-Encoding: 8bit
X-MIME-Autoconverted: from quoted-printable to 8bit by www1.ietf.org id gA72X7v30340
Subject: [manet] Why cant i build ns2-allinone-2.1ba9 in Redhat 8.0?
Sender: manet-admin@ietf.org
Errors-To: manet-admin@ietf.org
X-BeenThere: manet@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/manet>,
	<mailto:manet-request@ietf.org?subject=unsubscribe>
List-Id: Mobile Ad-hoc Networks  <manet.ietf.org>
List-Post: <mailto:manet@ietf.org>
List-Help: <mailto:manet-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/manet>,
	<mailto:manet-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 8bit
Content-Transfer-Encoding: 8bit

hi,all,
	I come into trouble when i build   ns2-allinone-2.1ba9 in Redhat 8.0, and the ns cant be built and installing aborts. Neither i notice Xgraph can be built correctly.  But the same copy can be installed in RedHat 7.2 and 7.3.
	Anybody can tell me Why? And when will the lasted version of ns be distributed?
	thx so much.	

	

best regards 				
ˇˇˇˇˇˇˇˇˇˇˇˇˇˇˇˇHarry
ˇˇˇˇˇˇˇˇˇˇˇˇˇˇˇˇˇˇˇˇ2002-11-07


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



From manet-admin@ietf.org  Wed Nov  6 21:42:53 2002
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id VAA21135
	for <manet-archive@lists.ietf.org>; Wed, 6 Nov 2002 21:42:53 -0500 (EST)
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gA72YGv30386;
	Wed, 6 Nov 2002 21:34:16 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gA72X7v30339
	for <manet@optimus.ietf.org>; Wed, 6 Nov 2002 21:33:07 -0500
Received: from bjapp7.163.net (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id VAA20387
	for <manet@ietf.org>; Wed, 6 Nov 2002 21:30:25 -0500 (EST)
Received: from localhost (localhost [127.0.0.1])
	by bjapp7.163.net (Postfix) with SMTP id 1C4091C85FC61
	for <manet@ietf.org>; Thu,  7 Nov 2002 10:32:51 +0800 (CST)
Received: from befine (unknown [211.71.13.13])
	by bjapp7.163.net (Coremail) with SMTP id XgIAANLQyT30RQ0N.1
	for <manet@ietf.org>; Thu, 07 Nov 2002 10:32:51 +0800 (CST)
Date: Thu, 7 Nov 2002 10:30:58 +0800
From: "Harry" <hr_befine@163.net>
Reply-To: hr_befine@163.net
To: MANET mail list <manet@ietf.org>
X-mailer: Foxmail 4.1 [cn]
Mime-Version: 1.0
Content-Type: text/plain;
      charset="GB2312"
Message-Id: <20021107023251.1C4091C85FC61@bjapp7.163.net>
Content-Transfer-Encoding: 8bit
X-MIME-Autoconverted: from quoted-printable to 8bit by www1.ietf.org id gA72X7v30340
Subject: [manet] Why cant i build ns2-allinone-2.1ba9 in Redhat 8.0?
Sender: manet-admin@ietf.org
Errors-To: manet-admin@ietf.org
X-BeenThere: manet@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/manet>,
	<mailto:manet-request@ietf.org?subject=unsubscribe>
List-Id: Mobile Ad-hoc Networks  <manet.ietf.org>
List-Post: <mailto:manet@ietf.org>
List-Help: <mailto:manet-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/manet>,
	<mailto:manet-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 8bit

hi,all,
	I come into trouble when i build   ns2-allinone-2.1ba9 in Redhat 8.0, and the ns cant be built and installing aborts. Neither i notice Xgraph can be built correctly.  But the same copy can be installed in RedHat 7.2 and 7.3.
	Anybody can tell me Why? And when will the lasted version of ns be distributed?
	thx so much.	

	

best regards 				
ˇˇˇˇˇˇˇˇˇˇˇˇˇˇˇˇHarry
ˇˇˇˇˇˇˇˇˇˇˇˇˇˇˇˇˇˇˇˇ2002-11-07


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


From manet-admin@ietf.org  Thu Nov  7 02:10:59 2002
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id CAA05642
	for <manet-archive@lists.ietf.org>; Thu, 7 Nov 2002 02:10:59 -0500 (EST)
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gA774uv13334;
	Thu, 7 Nov 2002 02:04:56 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gA772ov12333
	for <manet@optimus.ietf.org>; Thu, 7 Nov 2002 02:02:50 -0500
Received: from nathan.informatik.uni-ulm.de (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id CAA25969
	for <manet@ietf.org>; Thu, 7 Nov 2002 02:00:09 -0500 (EST)
Received: from orca.informatik.uni-ulm.de (orca.informatik.uni-ulm.de [134.60.70.16])
	by nathan.informatik.uni-ulm.de (8.11.3/any version) with ESMTP id gA772ba32475;
	Thu, 7 Nov 2002 08:02:37 +0100
Received: by orca.informatik.uni-ulm.de (Postfix on SuSE Linux 8.0 (i386), from userid 508)
	id AA7F61C7AD; Thu,  7 Nov 2002 08:02:37 +0100 (CET)
Date: Thu, 7 Nov 2002 08:02:37 +0100
From: Stefan Schlott <stefan.schlott@informatik.uni-ulm.de>
To: Rakesh Kumar Banka <Rakesh@asu.edu>
Cc: manet@ietf.org
Subject: Re: [manet] Heterogeneous networks
Message-ID: <20021107070237.GB22699@orca.informatik.uni-ulm.de>
References: <Pine.GSO.4.21.0210282255480.25827-100000@general1.asu.edu>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <Pine.GSO.4.21.0210282255480.25827-100000@general1.asu.edu>
User-Agent: Mutt/1.4i
Sender: manet-admin@ietf.org
Errors-To: manet-admin@ietf.org
X-BeenThere: manet@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/manet>,
	<mailto:manet-request@ietf.org?subject=unsubscribe>
List-Id: Mobile Ad-hoc Networks  <manet.ietf.org>
List-Post: <mailto:manet@ietf.org>
List-Help: <mailto:manet-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/manet>,
	<mailto:manet-request@ietf.org?subject=subscribe>

On Mon, Oct 28, 2002 at 10:58:57PM -0700, Rakesh Kumar Banka wrote:

>  Can someone tell me how to change the transmission
> ranges of the nodes in the NS-2 simulator? 

I've been stuck with that, too... our current workaround: Don't change
the transmission intensity, but modify the receive threshold instead:
  Phy/WirelessPhy set RXThresh_ 3.07645e-07
The threshold value was computed using the threshold program from the
ns2/indep-utils/propagation directory. This setting determines the threshold
for all nodes - I haven't tried setting it for individual nodes.

If you find a better solution, please let me know.

Stefan.

-- 
*--- please cut here... -------------------------------------- thanks! ---*
|-> E-Mail: stefan.schlott@informatik.uni-ulm.de    PGP-Key: 0x2F36F4FE <-|
| They that can give up essential liberty to obtain a little temporary    |
| safety deserve neither liberty nor safety.                              |
|   -- Ben Franklin                                                       |
*-------------------------------------------------------------------------*
_______________________________________________
manet mailing list
manet@ietf.org
https://www1.ietf.org/mailman/listinfo/manet


From mailnull@www1.ietf.org  Thu Nov  7 02:16:49 2002
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id CAA05806
	for <manet-archive@odin.ietf.org>; Thu, 7 Nov 2002 02:16:49 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id gA77IxN21852
	for manet-archive@odin.ietf.org; Thu, 7 Nov 2002 02:18:59 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gA77Iwv21849
	for <manet-web-archive@optimus.ietf.org>; Thu, 7 Nov 2002 02:18:58 -0500
Received: from www1.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id CAA05803
	for <manet-web-archive@ietf.org>; Thu, 7 Nov 2002 02:16:18 -0500 (EST)
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gA774uv13334;
	Thu, 7 Nov 2002 02:04:56 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gA772ov12333
	for <manet@optimus.ietf.org>; Thu, 7 Nov 2002 02:02:50 -0500
Received: from nathan.informatik.uni-ulm.de (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id CAA25969
	for <manet@ietf.org>; Thu, 7 Nov 2002 02:00:09 -0500 (EST)
Received: from orca.informatik.uni-ulm.de (orca.informatik.uni-ulm.de [134.60.70.16])
	by nathan.informatik.uni-ulm.de (8.11.3/any version) with ESMTP id gA772ba32475;
	Thu, 7 Nov 2002 08:02:37 +0100
Received: by orca.informatik.uni-ulm.de (Postfix on SuSE Linux 8.0 (i386), from userid 508)
	id AA7F61C7AD; Thu,  7 Nov 2002 08:02:37 +0100 (CET)
Date: Thu, 7 Nov 2002 08:02:37 +0100
From: Stefan Schlott <stefan.schlott@informatik.uni-ulm.de>
To: Rakesh Kumar Banka <Rakesh@asu.edu>
Cc: manet@ietf.org
Subject: Re: [manet] Heterogeneous networks
Message-ID: <20021107070237.GB22699@orca.informatik.uni-ulm.de>
References: <Pine.GSO.4.21.0210282255480.25827-100000@general1.asu.edu>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <Pine.GSO.4.21.0210282255480.25827-100000@general1.asu.edu>
User-Agent: Mutt/1.4i
Sender: manet-admin@ietf.org
Errors-To: manet-admin@ietf.org
X-BeenThere: manet@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/manet>,
	<mailto:manet-request@ietf.org?subject=unsubscribe>
List-Id: Mobile Ad-hoc Networks  <manet.ietf.org>
List-Post: <mailto:manet@ietf.org>
List-Help: <mailto:manet-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/manet>,
	<mailto:manet-request@ietf.org?subject=subscribe>

On Mon, Oct 28, 2002 at 10:58:57PM -0700, Rakesh Kumar Banka wrote:

>  Can someone tell me how to change the transmission
> ranges of the nodes in the NS-2 simulator? 

I've been stuck with that, too... our current workaround: Don't change
the transmission intensity, but modify the receive threshold instead:
  Phy/WirelessPhy set RXThresh_ 3.07645e-07
The threshold value was computed using the threshold program from the
ns2/indep-utils/propagation directory. This setting determines the threshold
for all nodes - I haven't tried setting it for individual nodes.

If you find a better solution, please let me know.

Stefan.

-- 
*--- please cut here... -------------------------------------- thanks! ---*
|-> E-Mail: stefan.schlott@informatik.uni-ulm.de    PGP-Key: 0x2F36F4FE <-|
| They that can give up essential liberty to obtain a little temporary    |
| safety deserve neither liberty nor safety.                              |
|   -- Ben Franklin                                                       |
*-------------------------------------------------------------------------*
_______________________________________________
manet mailing list
manet@ietf.org
https://www1.ietf.org/mailman/listinfo/manet



From mailnull@www1.ietf.org  Thu Nov  7 04:19:26 2002
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id EAA07835
	for <manet-archive@odin.ietf.org>; Thu, 7 Nov 2002 04:19:26 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id gA79LZk30377
	for manet-archive@odin.ietf.org; Thu, 7 Nov 2002 04:21:35 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gA79LZv30373
	for <manet-web-archive@optimus.ietf.org>; Thu, 7 Nov 2002 04:21:35 -0500
Received: from www1.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id EAA07826
	for <manet-web-archive@ietf.org>; Thu, 7 Nov 2002 04:18:54 -0500 (EST)
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gA79DCv29996;
	Thu, 7 Nov 2002 04:13:12 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gA798sv29835
	for <manet@optimus.ietf.org>; Thu, 7 Nov 2002 04:08:54 -0500
Received: from mailf.telia.com (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id EAA07661
	for <manet@ietf.org>; Thu, 7 Nov 2002 04:06:13 -0500 (EST)
Received: from d1o1121.telia.com (d1o1121.telia.com [217.208.140.241])
	by mailf.telia.com (8.12.5/8.12.5) with ESMTP id gA796XIZ009477;
	Thu, 7 Nov 2002 10:06:33 +0100 (CET)
X-Original-Recipient: manet@ietf.org
Received: from h168n2fls35o1121.telia.com (h168n2fls35o1121.telia.com [217.211.83.168])
	by d1o1121.telia.com (8.10.2/8.10.1) with ESMTP id gA796NB21287;
	Thu, 7 Nov 2002 10:06:33 +0100 (CET)
Subject: Re: [manet] Why cant i build ns2-allinone-2.1ba9 in Redhat 8.0?
From: Erik =?ISO-8859-1?Q?Nordstr=F6m?= <erik.nordstrom@it.uu.se>
To: hr_befine@163.net
Cc: MANET mail list <manet@ietf.org>
In-Reply-To: <20021107023251.1C4091C85FC61@bjapp7.163.net>
References: <20021107023251.1C4091C85FC61@bjapp7.163.net>
Content-Type: text/plain; charset=UTF-8
X-Mailer: Ximian Evolution 1.0.8 (1.0.8-10) 
Date: 07 Nov 2002 10:06:22 +0100
Message-Id: <1036659992.1241.6.camel@replicator.hn.org>
Mime-Version: 1.0
Content-Transfer-Encoding: 8bit
X-MIME-Autoconverted: from quoted-printable to 8bit by www1.ietf.org id gA798tv29836
Sender: manet-admin@ietf.org
Errors-To: manet-admin@ietf.org
X-BeenThere: manet@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/manet>,
	<mailto:manet-request@ietf.org?subject=unsubscribe>
List-Id: Mobile Ad-hoc Networks  <manet.ietf.org>
List-Post: <mailto:manet@ietf.org>
List-Help: <mailto:manet-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/manet>,
	<mailto:manet-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 8bit
Content-Transfer-Encoding: 8bit

As Joe Macker recently pointed out on this list, this is not the right
forum for questions like this. However, your problems are due to the new
compiler used in Red Hat 8.0 (gcc 3.2). The new compiler has better
conformance to the ISO C++ standard, but apparently the ns-2 code is not
up to scratch. I am sure you can find some help about this problem by
browsing the ns-2 mailing list archives.

Erik NordstrĂ¶m

On Thu, 2002-11-07 at 03:30, Harry wrote:
> hi,all,
> 	I come into trouble when i build   ns2-allinone-2.1ba9 in Redhat 8.0, and the ns cant be built and installing aborts. Neither i notice Xgraph can be built correctly.  But the same copy can be installed in RedHat 7.2 and 7.3.
> 	Anybody can tell me Why? And when will the lasted version of ns be distributed?
> 	thx so much.	
> 
> 	
> 
> best regards 				
> ă€€ă€€ă€€ă€€ă€€ă€€ă€€ă€€Harry
> ă€€ă€€ă€€ă€€ă€€ă€€ă€€ă€€ă€€ă€€2002-11-07
> 
> 
> _______________________________________________
> manet mailing list
> manet@ietf.org
> https://www1.ietf.org/mailman/listinfo/manet


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



From manet-admin@ietf.org  Thu Nov  7 04:19:30 2002
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id EAA07848
	for <manet-archive@lists.ietf.org>; Thu, 7 Nov 2002 04:19:30 -0500 (EST)
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gA79DCv29996;
	Thu, 7 Nov 2002 04:13:12 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gA798sv29835
	for <manet@optimus.ietf.org>; Thu, 7 Nov 2002 04:08:54 -0500
Received: from mailf.telia.com (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id EAA07661
	for <manet@ietf.org>; Thu, 7 Nov 2002 04:06:13 -0500 (EST)
Received: from d1o1121.telia.com (d1o1121.telia.com [217.208.140.241])
	by mailf.telia.com (8.12.5/8.12.5) with ESMTP id gA796XIZ009477;
	Thu, 7 Nov 2002 10:06:33 +0100 (CET)
X-Original-Recipient: manet@ietf.org
Received: from h168n2fls35o1121.telia.com (h168n2fls35o1121.telia.com [217.211.83.168])
	by d1o1121.telia.com (8.10.2/8.10.1) with ESMTP id gA796NB21287;
	Thu, 7 Nov 2002 10:06:33 +0100 (CET)
Subject: Re: [manet] Why cant i build ns2-allinone-2.1ba9 in Redhat 8.0?
From: Erik =?ISO-8859-1?Q?Nordstr=F6m?= <erik.nordstrom@it.uu.se>
To: hr_befine@163.net
Cc: MANET mail list <manet@ietf.org>
In-Reply-To: <20021107023251.1C4091C85FC61@bjapp7.163.net>
References: <20021107023251.1C4091C85FC61@bjapp7.163.net>
Content-Type: text/plain; charset=UTF-8
X-Mailer: Ximian Evolution 1.0.8 (1.0.8-10) 
Date: 07 Nov 2002 10:06:22 +0100
Message-Id: <1036659992.1241.6.camel@replicator.hn.org>
Mime-Version: 1.0
Content-Transfer-Encoding: 8bit
X-MIME-Autoconverted: from quoted-printable to 8bit by www1.ietf.org id gA798tv29836
Sender: manet-admin@ietf.org
Errors-To: manet-admin@ietf.org
X-BeenThere: manet@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/manet>,
	<mailto:manet-request@ietf.org?subject=unsubscribe>
List-Id: Mobile Ad-hoc Networks  <manet.ietf.org>
List-Post: <mailto:manet@ietf.org>
List-Help: <mailto:manet-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/manet>,
	<mailto:manet-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 8bit

As Joe Macker recently pointed out on this list, this is not the right
forum for questions like this. However, your problems are due to the new
compiler used in Red Hat 8.0 (gcc 3.2). The new compiler has better
conformance to the ISO C++ standard, but apparently the ns-2 code is not
up to scratch. I am sure you can find some help about this problem by
browsing the ns-2 mailing list archives.

Erik NordstrĂ¶m

On Thu, 2002-11-07 at 03:30, Harry wrote:
> hi,all,
> 	I come into trouble when i build   ns2-allinone-2.1ba9 in Redhat 8.0, and the ns cant be built and installing aborts. Neither i notice Xgraph can be built correctly.  But the same copy can be installed in RedHat 7.2 and 7.3.
> 	Anybody can tell me Why? And when will the lasted version of ns be distributed?
> 	thx so much.	
> 
> 	
> 
> best regards 				
> ă€€ă€€ă€€ă€€ă€€ă€€ă€€ă€€Harry
> ă€€ă€€ă€€ă€€ă€€ă€€ă€€ă€€ă€€ă€€2002-11-07
> 
> 
> _______________________________________________
> manet mailing list
> manet@ietf.org
> https://www1.ietf.org/mailman/listinfo/manet


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


From manet-admin@ietf.org  Thu Nov  7 06:37:50 2002
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id GAA12148
	for <manet-archive@lists.ietf.org>; Thu, 7 Nov 2002 06:37:50 -0500 (EST)
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gA7BVfv06710;
	Thu, 7 Nov 2002 06:31:41 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gA7BSVv06429
	for <manet@optimus.ietf.org>; Thu, 7 Nov 2002 06:28:31 -0500
Received: from CNRI.Reston.VA.US (localhost [127.0.0.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id GAA11011;
	Thu, 7 Nov 2002 06:26:00 -0500 (EST)
Message-Id: <200211071126.GAA11011@ietf.org>
Mime-Version: 1.0
Content-Type: Multipart/Mixed; Boundary="NextPart"
To: IETF-Announce: ;
Cc: manet@ietf.org
From: Internet-Drafts@ietf.org
Reply-to: Internet-Drafts@ietf.org
Date: Thu, 07 Nov 2002 06:26:00 -0500
Subject: [manet] I-D ACTION:draft-ietf-manet-aodv-12.txt
Sender: manet-admin@ietf.org
Errors-To: manet-admin@ietf.org
X-BeenThere: manet@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/manet>,
	<mailto:manet-request@ietf.org?subject=unsubscribe>
List-Id: Mobile Ad-hoc Networks  <manet.ietf.org>
List-Post: <mailto:manet@ietf.org>
List-Help: <mailto:manet-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/manet>,
	<mailto:manet-request@ietf.org?subject=subscribe>

--NextPart

A New Internet-Draft is available from the on-line Internet-Drafts directories.
This draft is a work item of the Mobile Ad-hoc Networks Working Group of the IETF.

	Title		: Ad Hoc On Demand Distance Vector (AODV) Routing
	Author(s)	: C. Perkins, E. Royer, S. Das
	Filename	: draft-ietf-manet-aodv-12.txt
	Pages		: 33
	Date		: 2002-11-6
	
The Ad hoc On-Demand Distance Vector (AODV) routing protocol
is intended for use by mobile nodes in an ad hoc network.  It
offers quick adaptation to dynamic link conditions, low processing
and memory overhead, low network utilization, and determines
unicast routes to destinations within the ad hoc network.  It uses
destination sequence numbers to ensure loop freedom at all times
(even in the face of anomalous delivery of routing control messages),
avoiding problems (such as 'counting to infinity') associated with
classical distance vector protocols.

A URL for this Internet-Draft is:
http://www.ietf.org/internet-drafts/draft-ietf-manet-aodv-12.txt

To remove yourself from the IETF Announcement list, send a message to 
ietf-announce-request with the word unsubscribe in the body of the message.

Internet-Drafts are also available by anonymous FTP. Login with the username
"anonymous" and a password of your e-mail address. After logging in,
type "cd internet-drafts" and then
	"get draft-ietf-manet-aodv-12.txt".

A list of Internet-Drafts directories can be found in
http://www.ietf.org/shadow.html 
or ftp://ftp.ietf.org/ietf/1shadow-sites.txt


Internet-Drafts can also be obtained by e-mail.

Send a message to:
	mailserv@ietf.org.
In the body type:
	"FILE /internet-drafts/draft-ietf-manet-aodv-12.txt".
	
NOTE:	The mail server at ietf.org can return the document in
	MIME-encoded form by using the "mpack" utility.  To use this
	feature, insert the command "ENCODING mime" before the "FILE"
	command.  To decode the response(s), you will need "munpack" or
	a MIME-compliant mail reader.  Different MIME-compliant mail readers
	exhibit different behavior, especially when dealing with
	"multipart" MIME messages (i.e. documents which have been split
	up into multiple messages), so check your local documentation on
	how to manipulate these messages.
		
		
Below is the data which will enable a MIME compliant mail reader
implementation to automatically retrieve the ASCII version of the
Internet-Draft.

--NextPart
Content-Type: Multipart/Alternative; Boundary="OtherAccess"

--OtherAccess
Content-Type: Message/External-body;
	access-type="mail-server";
	server="mailserv@ietf.org"

Content-Type: text/plain
Content-ID:	<2002-11-6174959.I-D@ietf.org>

ENCODING mime
FILE /internet-drafts/draft-ietf-manet-aodv-12.txt

--OtherAccess
Content-Type: Message/External-body;
	name="draft-ietf-manet-aodv-12.txt";
	site="ftp.ietf.org";
	access-type="anon-ftp";
	directory="internet-drafts"

Content-Type: text/plain
Content-ID:	<2002-11-6174959.I-D@ietf.org>

--OtherAccess--

--NextPart--


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


From manet-admin@ietf.org  Thu Nov  7 06:38:16 2002
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id GAA12163
	for <manet-archive@lists.ietf.org>; Thu, 7 Nov 2002 06:38:16 -0500 (EST)
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gA7BW5v06757;
	Thu, 7 Nov 2002 06:32:05 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gA7BSav06435
	for <manet@optimus.ietf.org>; Thu, 7 Nov 2002 06:28:36 -0500
Received: from CNRI.Reston.VA.US (localhost [127.0.0.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id GAA11037;
	Thu, 7 Nov 2002 06:26:05 -0500 (EST)
Message-Id: <200211071126.GAA11037@ietf.org>
Mime-Version: 1.0
Content-Type: Multipart/Mixed; Boundary="NextPart"
To: IETF-Announce: ;
Cc: manet@ietf.org
From: Internet-Drafts@ietf.org
Reply-to: Internet-Drafts@ietf.org
Date: Thu, 07 Nov 2002 06:26:05 -0500
Subject: [manet] I-D ACTION:draft-ietf-manet-tbrpf-06.txt
Sender: manet-admin@ietf.org
Errors-To: manet-admin@ietf.org
X-BeenThere: manet@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/manet>,
	<mailto:manet-request@ietf.org?subject=unsubscribe>
List-Id: Mobile Ad-hoc Networks  <manet.ietf.org>
List-Post: <mailto:manet@ietf.org>
List-Help: <mailto:manet-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/manet>,
	<mailto:manet-request@ietf.org?subject=subscribe>

--NextPart

A New Internet-Draft is available from the on-line Internet-Drafts directories.
This draft is a work item of the Mobile Ad-hoc Networks Working Group of the IETF.

	Title		: Topology Broadcast based on Reverse-Path Forwarding 
                          (TBRPF)
	Author(s)	: R. Ogier, M. Lewis, F. Templin, B. Bellur
	Filename	: draft-ietf-manet-tbrpf-06.txt
	Pages		: 44
	Date		: 2002-11-6
	
TBRPF is a proactive, link-state routing protocol designed for mobile
ad-hoc networks, which provides hop-by-hop routing along shortest
paths to each destination.  Each node running TBRPF computes a source
tree (providing paths to all reachable nodes) based on partial
topology information stored in its topology table, using a
modification of Dijkstra's algorithm.  To minimize overhead, each
node reports only *part* of its source tree to neighbors. This is in
contrast to other protocols in which each node reports its *entire*
source tree to neighbors.  TBRPF uses a combination of periodic and
differential updates to keep all neighbors informed of the reportable
part of its source tree.  Each node also has the option to report
additional topology information (up to the full topology), to provide
improved robustness in highly mobile networks.  TBRPF performs
neighbor discovery using 'differential' HELLO messages which report
only *changes* in the status of neighbors.  This results in HELLO
messages that are much smaller than those of other link-state routing
protocols such as OSPF.

A URL for this Internet-Draft is:
http://www.ietf.org/internet-drafts/draft-ietf-manet-tbrpf-06.txt

To remove yourself from the IETF Announcement list, send a message to 
ietf-announce-request with the word unsubscribe in the body of the message.

Internet-Drafts are also available by anonymous FTP. Login with the username
"anonymous" and a password of your e-mail address. After logging in,
type "cd internet-drafts" and then
	"get draft-ietf-manet-tbrpf-06.txt".

A list of Internet-Drafts directories can be found in
http://www.ietf.org/shadow.html 
or ftp://ftp.ietf.org/ietf/1shadow-sites.txt


Internet-Drafts can also be obtained by e-mail.

Send a message to:
	mailserv@ietf.org.
In the body type:
	"FILE /internet-drafts/draft-ietf-manet-tbrpf-06.txt".
	
NOTE:	The mail server at ietf.org can return the document in
	MIME-encoded form by using the "mpack" utility.  To use this
	feature, insert the command "ENCODING mime" before the "FILE"
	command.  To decode the response(s), you will need "munpack" or
	a MIME-compliant mail reader.  Different MIME-compliant mail readers
	exhibit different behavior, especially when dealing with
	"multipart" MIME messages (i.e. documents which have been split
	up into multiple messages), so check your local documentation on
	how to manipulate these messages.
		
		
Below is the data which will enable a MIME compliant mail reader
implementation to automatically retrieve the ASCII version of the
Internet-Draft.

--NextPart
Content-Type: Multipart/Alternative; Boundary="OtherAccess"

--OtherAccess
Content-Type: Message/External-body;
	access-type="mail-server";
	server="mailserv@ietf.org"

Content-Type: text/plain
Content-ID:	<2002-11-6175013.I-D@ietf.org>

ENCODING mime
FILE /internet-drafts/draft-ietf-manet-tbrpf-06.txt

--OtherAccess
Content-Type: Message/External-body;
	name="draft-ietf-manet-tbrpf-06.txt";
	site="ftp.ietf.org";
	access-type="anon-ftp";
	directory="internet-drafts"

Content-Type: text/plain
Content-ID:	<2002-11-6175013.I-D@ietf.org>

--OtherAccess--

--NextPart--


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


From mailnull@www1.ietf.org  Thu Nov  7 06:45:10 2002
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id GAA12780
	for <manet-archive@odin.ietf.org>; Thu, 7 Nov 2002 06:45:10 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id gA7BlAB08429
	for manet-archive@odin.ietf.org; Thu, 7 Nov 2002 06:47:10 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gA7Bl9v08426
	for <manet-web-archive@optimus.ietf.org>; Thu, 7 Nov 2002 06:47:09 -0500
Received: from www1.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id GAA12430
	for <manet-web-archive@ietf.org>; Thu, 7 Nov 2002 06:44:16 -0500 (EST)
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gA7BVfv06710;
	Thu, 7 Nov 2002 06:31:41 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gA7BSVv06429
	for <manet@optimus.ietf.org>; Thu, 7 Nov 2002 06:28:31 -0500
Received: from CNRI.Reston.VA.US (localhost [127.0.0.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id GAA11011;
	Thu, 7 Nov 2002 06:26:00 -0500 (EST)
Message-Id: <200211071126.GAA11011@ietf.org>
Mime-Version: 1.0
Content-Type: Multipart/Mixed; Boundary="NextPart"
To: IETF-Announce: ;
Cc: manet@ietf.org
From: Internet-Drafts@ietf.org
Reply-to: Internet-Drafts@ietf.org
Date: Thu, 07 Nov 2002 06:26:00 -0500
Subject: [manet] I-D ACTION:draft-ietf-manet-aodv-12.txt
Sender: manet-admin@ietf.org
Errors-To: manet-admin@ietf.org
X-BeenThere: manet@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/manet>,
	<mailto:manet-request@ietf.org?subject=unsubscribe>
List-Id: Mobile Ad-hoc Networks  <manet.ietf.org>
List-Post: <mailto:manet@ietf.org>
List-Help: <mailto:manet-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/manet>,
	<mailto:manet-request@ietf.org?subject=subscribe>

--NextPart

A New Internet-Draft is available from the on-line Internet-Drafts directories.
This draft is a work item of the Mobile Ad-hoc Networks Working Group of the IETF.

	Title		: Ad Hoc On Demand Distance Vector (AODV) Routing
	Author(s)	: C. Perkins, E. Royer, S. Das
	Filename	: draft-ietf-manet-aodv-12.txt
	Pages		: 33
	Date		: 2002-11-6
	
The Ad hoc On-Demand Distance Vector (AODV) routing protocol
is intended for use by mobile nodes in an ad hoc network.  It
offers quick adaptation to dynamic link conditions, low processing
and memory overhead, low network utilization, and determines
unicast routes to destinations within the ad hoc network.  It uses
destination sequence numbers to ensure loop freedom at all times
(even in the face of anomalous delivery of routing control messages),
avoiding problems (such as 'counting to infinity') associated with
classical distance vector protocols.

A URL for this Internet-Draft is:
http://www.ietf.org/internet-drafts/draft-ietf-manet-aodv-12.txt

To remove yourself from the IETF Announcement list, send a message to 
ietf-announce-request with the word unsubscribe in the body of the message.

Internet-Drafts are also available by anonymous FTP. Login with the username
"anonymous" and a password of your e-mail address. After logging in,
type "cd internet-drafts" and then
	"get draft-ietf-manet-aodv-12.txt".

A list of Internet-Drafts directories can be found in
http://www.ietf.org/shadow.html 
or ftp://ftp.ietf.org/ietf/1shadow-sites.txt


Internet-Drafts can also be obtained by e-mail.

Send a message to:
	mailserv@ietf.org.
In the body type:
	"FILE /internet-drafts/draft-ietf-manet-aodv-12.txt".
	
NOTE:	The mail server at ietf.org can return the document in
	MIME-encoded form by using the "mpack" utility.  To use this
	feature, insert the command "ENCODING mime" before the "FILE"
	command.  To decode the response(s), you will need "munpack" or
	a MIME-compliant mail reader.  Different MIME-compliant mail readers
	exhibit different behavior, especially when dealing with
	"multipart" MIME messages (i.e. documents which have been split
	up into multiple messages), so check your local documentation on
	how to manipulate these messages.
		
		
Below is the data which will enable a MIME compliant mail reader
implementation to automatically retrieve the ASCII version of the
Internet-Draft.

--NextPart
Content-Type: Multipart/Alternative; Boundary="OtherAccess"

--OtherAccess
Content-Type: Message/External-body;
	access-type="mail-server";
	server="mailserv@ietf.org"

Content-Type: text/plain
Content-ID:	<2002-11-6174959.I-D@ietf.org>

ENCODING mime
FILE /internet-drafts/draft-ietf-manet-aodv-12.txt

--OtherAccess
Content-Type: Message/External-body;
	name="draft-ietf-manet-aodv-12.txt";
	site="ftp.ietf.org";
	access-type="anon-ftp";
	directory="internet-drafts"

Content-Type: text/plain
Content-ID:	<2002-11-6174959.I-D@ietf.org>

--OtherAccess--

--NextPart--


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



From mailnull@www1.ietf.org  Thu Nov  7 06:46:31 2002
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id GAA12906
	for <manet-archive@odin.ietf.org>; Thu, 7 Nov 2002 06:46:31 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id gA7BmVk08519
	for manet-archive@odin.ietf.org; Thu, 7 Nov 2002 06:48:31 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gA7BmVv08516
	for <manet-web-archive@optimus.ietf.org>; Thu, 7 Nov 2002 06:48:31 -0500
Received: from www1.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id GAA12898
	for <manet-web-archive@ietf.org>; Thu, 7 Nov 2002 06:45:54 -0500 (EST)
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gA7BW5v06757;
	Thu, 7 Nov 2002 06:32:05 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gA7BSav06435
	for <manet@optimus.ietf.org>; Thu, 7 Nov 2002 06:28:36 -0500
Received: from CNRI.Reston.VA.US (localhost [127.0.0.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id GAA11037;
	Thu, 7 Nov 2002 06:26:05 -0500 (EST)
Message-Id: <200211071126.GAA11037@ietf.org>
Mime-Version: 1.0
Content-Type: Multipart/Mixed; Boundary="NextPart"
To: IETF-Announce: ;
Cc: manet@ietf.org
From: Internet-Drafts@ietf.org
Reply-to: Internet-Drafts@ietf.org
Date: Thu, 07 Nov 2002 06:26:05 -0500
Subject: [manet] I-D ACTION:draft-ietf-manet-tbrpf-06.txt
Sender: manet-admin@ietf.org
Errors-To: manet-admin@ietf.org
X-BeenThere: manet@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/manet>,
	<mailto:manet-request@ietf.org?subject=unsubscribe>
List-Id: Mobile Ad-hoc Networks  <manet.ietf.org>
List-Post: <mailto:manet@ietf.org>
List-Help: <mailto:manet-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/manet>,
	<mailto:manet-request@ietf.org?subject=subscribe>

--NextPart

A New Internet-Draft is available from the on-line Internet-Drafts directories.
This draft is a work item of the Mobile Ad-hoc Networks Working Group of the IETF.

	Title		: Topology Broadcast based on Reverse-Path Forwarding 
                          (TBRPF)
	Author(s)	: R. Ogier, M. Lewis, F. Templin, B. Bellur
	Filename	: draft-ietf-manet-tbrpf-06.txt
	Pages		: 44
	Date		: 2002-11-6
	
TBRPF is a proactive, link-state routing protocol designed for mobile
ad-hoc networks, which provides hop-by-hop routing along shortest
paths to each destination.  Each node running TBRPF computes a source
tree (providing paths to all reachable nodes) based on partial
topology information stored in its topology table, using a
modification of Dijkstra's algorithm.  To minimize overhead, each
node reports only *part* of its source tree to neighbors. This is in
contrast to other protocols in which each node reports its *entire*
source tree to neighbors.  TBRPF uses a combination of periodic and
differential updates to keep all neighbors informed of the reportable
part of its source tree.  Each node also has the option to report
additional topology information (up to the full topology), to provide
improved robustness in highly mobile networks.  TBRPF performs
neighbor discovery using 'differential' HELLO messages which report
only *changes* in the status of neighbors.  This results in HELLO
messages that are much smaller than those of other link-state routing
protocols such as OSPF.

A URL for this Internet-Draft is:
http://www.ietf.org/internet-drafts/draft-ietf-manet-tbrpf-06.txt

To remove yourself from the IETF Announcement list, send a message to 
ietf-announce-request with the word unsubscribe in the body of the message.

Internet-Drafts are also available by anonymous FTP. Login with the username
"anonymous" and a password of your e-mail address. After logging in,
type "cd internet-drafts" and then
	"get draft-ietf-manet-tbrpf-06.txt".

A list of Internet-Drafts directories can be found in
http://www.ietf.org/shadow.html 
or ftp://ftp.ietf.org/ietf/1shadow-sites.txt


Internet-Drafts can also be obtained by e-mail.

Send a message to:
	mailserv@ietf.org.
In the body type:
	"FILE /internet-drafts/draft-ietf-manet-tbrpf-06.txt".
	
NOTE:	The mail server at ietf.org can return the document in
	MIME-encoded form by using the "mpack" utility.  To use this
	feature, insert the command "ENCODING mime" before the "FILE"
	command.  To decode the response(s), you will need "munpack" or
	a MIME-compliant mail reader.  Different MIME-compliant mail readers
	exhibit different behavior, especially when dealing with
	"multipart" MIME messages (i.e. documents which have been split
	up into multiple messages), so check your local documentation on
	how to manipulate these messages.
		
		
Below is the data which will enable a MIME compliant mail reader
implementation to automatically retrieve the ASCII version of the
Internet-Draft.

--NextPart
Content-Type: Multipart/Alternative; Boundary="OtherAccess"

--OtherAccess
Content-Type: Message/External-body;
	access-type="mail-server";
	server="mailserv@ietf.org"

Content-Type: text/plain
Content-ID:	<2002-11-6175013.I-D@ietf.org>

ENCODING mime
FILE /internet-drafts/draft-ietf-manet-tbrpf-06.txt

--OtherAccess
Content-Type: Message/External-body;
	name="draft-ietf-manet-tbrpf-06.txt";
	site="ftp.ietf.org";
	access-type="anon-ftp";
	directory="internet-drafts"

Content-Type: text/plain
Content-ID:	<2002-11-6175013.I-D@ietf.org>

--OtherAccess--

--NextPart--


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



From manet-admin@ietf.org  Thu Nov  7 11:55:00 2002
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA01717
	for <manet-archive@lists.ietf.org>; Thu, 7 Nov 2002 11:55:00 -0500 (EST)
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gA7Gm6v30799;
	Thu, 7 Nov 2002 11:48:06 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gA7Gcmv30453
	for <manet@optimus.ietf.org>; Thu, 7 Nov 2002 11:38:48 -0500
Received: from mail.cit.ie (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA01291
	for <manet@ietf.org>; Thu, 7 Nov 2002 11:36:11 -0500 (EST)
Received: from eeb253w2kjpg (unverified [157.190.41.56]) by cit.ie
 (Rockliffe SMTPRA 5.2.3) with SMTP id <B0000233972@mail.cit.ie> for <manet@ietf.org>;
 Thu, 7 Nov 2002 16:34:40 +0000
Message-ID: <008701c2867c$278e5060$3829be9d@eeb253w2kjpg>
From: "John Paul O Grady" <jpogrady@cit.ie>
To: <manet@ietf.org>
Date: Thu, 7 Nov 2002 16:38:51 -0000
MIME-Version: 1.0
Content-Type: multipart/alternative;
	boundary="----=_NextPart_000_0084_01C2867C.276F2FA0"
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 6.00.2800.1106
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1106
Subject: [manet] Source Routing
Sender: manet-admin@ietf.org
Errors-To: manet-admin@ietf.org
X-BeenThere: manet@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/manet>,
	<mailto:manet-request@ietf.org?subject=unsubscribe>
List-Id: Mobile Ad-hoc Networks  <manet.ietf.org>
List-Post: <mailto:manet@ietf.org>
List-Help: <mailto:manet-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/manet>,
	<mailto:manet-request@ietf.org?subject=subscribe>

This is a multi-part message in MIME format.

------=_NextPart_000_0084_01C2867C.276F2FA0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

Hello

I need to do a bit of research on the different source routing protocols =
that have been proposed for use in ad hoc networks. I was wondering if =
anyone has a list of the  protocols that have been proposed

Regards

John Paul O Grady
CIT
Ireland

=
-------------------Legal  Disclaimer-------------------------------------=
--

The above electronic mail transmission is confidential and intended only =
for the person to whom it is addressed. Its contents may be protected by =
legal and/or professional privilege. Should it be received by you in erro=
r please contact the sender at the above quoted email address. Any unauth=
orised form of reproduction of this message is strictly prohibited. The I=
nstitute does not guarantee the security of any information electronicall=
y transmitted and is not liable if the information contained in this comm=
unication is not a proper and complete record of the message as transmitt=
ed by the sender nor for any delay in its receipt.

-------------------------------------------------------------------------=
---------------=


------=_NextPart_000_0084_01C2867C.276F2FA0
Content-Type: text/html;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META http-equiv=3DContent-Type content=3D"text/html; =
charset=3Diso-8859-1">
<META content=3D"MSHTML 6.00.2800.1106" name=3DGENERATOR>
<STYLE></STYLE>
</HEAD>
<BODY bgColor=3D#ffffff>
<DIV><FONT face=3DArial size=3D2>Hello</FONT></DIV>
<DIV><FONT face=3DArial size=3D2></FONT>&nbsp;</DIV>
<DIV><FONT face=3DArial size=3D2>I&nbsp;need to do a bit of research on =
the=20
different source routing protocols that have been&nbsp;proposed for use =
in ad=20
hoc networks. I was wondering if anyone has a list of the&nbsp; =
protocols that=20
have been proposed</FONT></DIV>
<DIV><FONT face=3DArial size=3D2></FONT>&nbsp;</DIV>
<DIV><FONT face=3DArial size=3D2>Regards</FONT></DIV>
<DIV><FONT face=3DArial size=3D2></FONT>&nbsp;</DIV>
<DIV><FONT face=3DArial size=3D2>John Paul O Grady</FONT></DIV>
<DIV><FONT face=3DArial size=3D2>CIT</FONT></DIV>
<DIV><FONT face=3DArial size=3D2>Ireland</FONT></DIV>
=
-------------------Legal  Disclaimer-------------------------------------=
--

The above electronic mail transmission is confidential and intended only =
for the person to whom it is addressed. Its contents may be protected by =
legal and/or professional privilege. Should it be received by you in erro=
r please contact the sender at the above quoted email address. Any unauth=
orised form of reproduction of this message is strictly prohibited. The I=
nstitute does not guarantee the security of any information electronicall=
y transmitted and is not liable if the information contained in this comm=
unication is not a proper and complete record of the message as transmitt=
ed by the sender nor for any delay in its receipt.

-------------------------------------------------------------------------=
---------------=


</BODY></HTML>

------=_NextPart_000_0084_01C2867C.276F2FA0--

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


From mailnull@www1.ietf.org  Thu Nov  7 12:01:07 2002
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA02046
	for <manet-archive@odin.ietf.org>; Thu, 7 Nov 2002 12:01:07 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id gA7H39V31765
	for manet-archive@odin.ietf.org; Thu, 7 Nov 2002 12:03:09 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gA7H39v31760
	for <manet-web-archive@optimus.ietf.org>; Thu, 7 Nov 2002 12:03:09 -0500
Received: from www1.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA02007
	for <manet-web-archive@ietf.org>; Thu, 7 Nov 2002 12:00:36 -0500 (EST)
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gA7Gm6v30799;
	Thu, 7 Nov 2002 11:48:06 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gA7Gcmv30453
	for <manet@optimus.ietf.org>; Thu, 7 Nov 2002 11:38:48 -0500
Received: from mail.cit.ie (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA01291
	for <manet@ietf.org>; Thu, 7 Nov 2002 11:36:11 -0500 (EST)
Received: from eeb253w2kjpg (unverified [157.190.41.56]) by cit.ie
 (Rockliffe SMTPRA 5.2.3) with SMTP id <B0000233972@mail.cit.ie> for <manet@ietf.org>;
 Thu, 7 Nov 2002 16:34:40 +0000
Message-ID: <008701c2867c$278e5060$3829be9d@eeb253w2kjpg>
From: "John Paul O Grady" <jpogrady@cit.ie>
To: <manet@ietf.org>
Date: Thu, 7 Nov 2002 16:38:51 -0000
MIME-Version: 1.0
Content-Type: multipart/alternative;
	boundary="----=_NextPart_000_0084_01C2867C.276F2FA0"
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 6.00.2800.1106
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1106
Subject: [manet] Source Routing
Sender: manet-admin@ietf.org
Errors-To: manet-admin@ietf.org
X-BeenThere: manet@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/manet>,
	<mailto:manet-request@ietf.org?subject=unsubscribe>
List-Id: Mobile Ad-hoc Networks  <manet.ietf.org>
List-Post: <mailto:manet@ietf.org>
List-Help: <mailto:manet-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/manet>,
	<mailto:manet-request@ietf.org?subject=subscribe>

This is a multi-part message in MIME format.

------=_NextPart_000_0084_01C2867C.276F2FA0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

Hello

I need to do a bit of research on the different source routing protocols =
that have been proposed for use in ad hoc networks. I was wondering if =
anyone has a list of the  protocols that have been proposed

Regards

John Paul O Grady
CIT
Ireland

=
-------------------Legal  Disclaimer-------------------------------------=
--

The above electronic mail transmission is confidential and intended only =
for the person to whom it is addressed. Its contents may be protected by =
legal and/or professional privilege. Should it be received by you in erro=
r please contact the sender at the above quoted email address. Any unauth=
orised form of reproduction of this message is strictly prohibited. The I=
nstitute does not guarantee the security of any information electronicall=
y transmitted and is not liable if the information contained in this comm=
unication is not a proper and complete record of the message as transmitt=
ed by the sender nor for any delay in its receipt.

-------------------------------------------------------------------------=
---------------=


------=_NextPart_000_0084_01C2867C.276F2FA0
Content-Type: text/html;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META http-equiv=3DContent-Type content=3D"text/html; =
charset=3Diso-8859-1">
<META content=3D"MSHTML 6.00.2800.1106" name=3DGENERATOR>
<STYLE></STYLE>
</HEAD>
<BODY bgColor=3D#ffffff>
<DIV><FONT face=3DArial size=3D2>Hello</FONT></DIV>
<DIV><FONT face=3DArial size=3D2></FONT>&nbsp;</DIV>
<DIV><FONT face=3DArial size=3D2>I&nbsp;need to do a bit of research on =
the=20
different source routing protocols that have been&nbsp;proposed for use =
in ad=20
hoc networks. I was wondering if anyone has a list of the&nbsp; =
protocols that=20
have been proposed</FONT></DIV>
<DIV><FONT face=3DArial size=3D2></FONT>&nbsp;</DIV>
<DIV><FONT face=3DArial size=3D2>Regards</FONT></DIV>
<DIV><FONT face=3DArial size=3D2></FONT>&nbsp;</DIV>
<DIV><FONT face=3DArial size=3D2>John Paul O Grady</FONT></DIV>
<DIV><FONT face=3DArial size=3D2>CIT</FONT></DIV>
<DIV><FONT face=3DArial size=3D2>Ireland</FONT></DIV>
=
-------------------Legal  Disclaimer-------------------------------------=
--

The above electronic mail transmission is confidential and intended only =
for the person to whom it is addressed. Its contents may be protected by =
legal and/or professional privilege. Should it be received by you in erro=
r please contact the sender at the above quoted email address. Any unauth=
orised form of reproduction of this message is strictly prohibited. The I=
nstitute does not guarantee the security of any information electronicall=
y transmitted and is not liable if the information contained in this comm=
unication is not a proper and complete record of the message as transmitt=
ed by the sender nor for any delay in its receipt.

-------------------------------------------------------------------------=
---------------=


</BODY></HTML>

------=_NextPart_000_0084_01C2867C.276F2FA0--

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



From manet-admin@ietf.org  Thu Nov  7 19:23:11 2002
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA19276
	for <manet-archive@lists.ietf.org>; Thu, 7 Nov 2002 19:23:11 -0500 (EST)
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gA80HKv32194;
	Thu, 7 Nov 2002 19:17:20 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gA809fv31934
	for <manet@optimus.ietf.org>; Thu, 7 Nov 2002 19:09:41 -0500
Received: from Tempo.Update.UU.SE (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA19002
	for <manet@ietf.org>; Thu, 7 Nov 2002 19:07:03 -0500 (EST)
Received: from Tempo.Update.UU.SE (localhost [127.0.0.1])
	by Tempo.Update.UU.SE (8.12.3/8.12.3/Update-Iltempogigante) with ESMTP id gA809UaG010904
	(version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO);
	Fri, 8 Nov 2002 01:09:30 +0100
Received: from localhost (davidl@localhost)
	by Tempo.Update.UU.SE (8.12.3/8.12.3/Update-Iltempogigante-submit) with ESMTP id gA809TDR010901;
	Fri, 8 Nov 2002 01:09:29 +0100
X-Authentication-Warning: Tempo.Update.UU.SE: davidl owned process doing -bs
Date: Fri, 8 Nov 2002 01:09:28 +0100 (CET)
From: David Lundberg <davidl@update.uu.se>
To: John Paul O Grady <jpogrady@cit.ie>
cc: manet@ietf.org
Subject: Re: [manet] Source Routing
In-Reply-To: <008701c2867c$278e5060$3829be9d@eeb253w2kjpg>
Message-ID: <Pine.LNX.4.21.0211080108090.16597-100000@Tempo.Update.UU.SE>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=iso-8859-1
Content-Transfer-Encoding: 8bit
X-MIME-Autoconverted: from QUOTED-PRINTABLE to 8bit by www1.ietf.org id gA809fv31935
Sender: manet-admin@ietf.org
Errors-To: manet-admin@ietf.org
X-BeenThere: manet@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/manet>,
	<mailto:manet-request@ietf.org?subject=unsubscribe>
List-Id: Mobile Ad-hoc Networks  <manet.ietf.org>
List-Post: <mailto:manet@ietf.org>
List-Help: <mailto:manet-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/manet>,
	<mailto:manet-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 8bit

On Thu, 7 Nov 2002, John Paul O Grady wrote:

> Hello
> 
> I need to do a bit of research on the different source routing protocols that have been proposed for use in ad hoc networks. I was wondering if anyone has a list of the  protocols that have been proposed

Have a look at this list announced last week:

http://www.wikipedia.org/wiki/Ad_hoc_protocol_list

// David //


--------------------------------------------------------------
David Lundberg            Phone: Home(Uppsala)   +46-18-460356
Mail: davidl@update.uu.se        Home(Gävle)     +46-26-146743
Http: www.update.uu.se/~davidl   Cellular       +46-70-3531696
ICQ:  13440550                   IT-Dept. @ UU  +46-18-4716231
--------------------------------------------------------------

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


From mailnull@www1.ietf.org  Thu Nov  7 19:30:58 2002
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA19447
	for <manet-archive@odin.ietf.org>; Thu, 7 Nov 2002 19:30:58 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id gA80X4D00521
	for manet-archive@odin.ietf.org; Thu, 7 Nov 2002 19:33:04 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gA80X4v00518
	for <manet-web-archive@optimus.ietf.org>; Thu, 7 Nov 2002 19:33:04 -0500
Received: from www1.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA19444
	for <manet-web-archive@ietf.org>; Thu, 7 Nov 2002 19:30:27 -0500 (EST)
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gA80HKv32194;
	Thu, 7 Nov 2002 19:17:20 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gA809fv31934
	for <manet@optimus.ietf.org>; Thu, 7 Nov 2002 19:09:41 -0500
Received: from Tempo.Update.UU.SE (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA19002
	for <manet@ietf.org>; Thu, 7 Nov 2002 19:07:03 -0500 (EST)
Received: from Tempo.Update.UU.SE (localhost [127.0.0.1])
	by Tempo.Update.UU.SE (8.12.3/8.12.3/Update-Iltempogigante) with ESMTP id gA809UaG010904
	(version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO);
	Fri, 8 Nov 2002 01:09:30 +0100
Received: from localhost (davidl@localhost)
	by Tempo.Update.UU.SE (8.12.3/8.12.3/Update-Iltempogigante-submit) with ESMTP id gA809TDR010901;
	Fri, 8 Nov 2002 01:09:29 +0100
X-Authentication-Warning: Tempo.Update.UU.SE: davidl owned process doing -bs
Date: Fri, 8 Nov 2002 01:09:28 +0100 (CET)
From: David Lundberg <davidl@update.uu.se>
To: John Paul O Grady <jpogrady@cit.ie>
cc: manet@ietf.org
Subject: Re: [manet] Source Routing
In-Reply-To: <008701c2867c$278e5060$3829be9d@eeb253w2kjpg>
Message-ID: <Pine.LNX.4.21.0211080108090.16597-100000@Tempo.Update.UU.SE>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=iso-8859-1
Content-Transfer-Encoding: 8bit
X-MIME-Autoconverted: from QUOTED-PRINTABLE to 8bit by www1.ietf.org id gA809fv31935
Sender: manet-admin@ietf.org
Errors-To: manet-admin@ietf.org
X-BeenThere: manet@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/manet>,
	<mailto:manet-request@ietf.org?subject=unsubscribe>
List-Id: Mobile Ad-hoc Networks  <manet.ietf.org>
List-Post: <mailto:manet@ietf.org>
List-Help: <mailto:manet-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/manet>,
	<mailto:manet-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 8bit
Content-Transfer-Encoding: 8bit

On Thu, 7 Nov 2002, John Paul O Grady wrote:

> Hello
> 
> I need to do a bit of research on the different source routing protocols that have been proposed for use in ad hoc networks. I was wondering if anyone has a list of the  protocols that have been proposed

Have a look at this list announced last week:

http://www.wikipedia.org/wiki/Ad_hoc_protocol_list

// David //


--------------------------------------------------------------
David Lundberg            Phone: Home(Uppsala)   +46-18-460356
Mail: davidl@update.uu.se        Home(Gävle)     +46-26-146743
Http: www.update.uu.se/~davidl   Cellular       +46-70-3531696
ICQ:  13440550                   IT-Dept. @ UU  +46-18-4716231
--------------------------------------------------------------

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



From manet-admin@ietf.org  Thu Nov  7 20:22:22 2002
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id UAA20255
	for <manet-archive@lists.ietf.org>; Thu, 7 Nov 2002 20:22:21 -0500 (EST)
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gA81Gsv03290;
	Thu, 7 Nov 2002 20:16:54 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gA81CGv03127
	for <manet@optimus.ietf.org>; Thu, 7 Nov 2002 20:12:16 -0500
Received: from smtp.x263.net (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id UAA20025
	for <manet@ietf.org>; Thu, 7 Nov 2002 20:09:36 -0500 (EST)
Received: from befine (mta5 [127.0.0.1])
	by smtp.x263.net (Postfix) with ESMTP id 17C292F77E
	for <manet@ietf.org>; Fri,  8 Nov 2002 08:58:27 +0800 (CST)
Received: from befine (unknown [211.71.13.13])
	by antispam-5 (Coremail) with SMTP id QLC3BzEMyz34JA0N.1
	for <manet@ietf.org>; Fri, 08 Nov 2002 08:58:28 +0800 (CST)
Date: Fri, 8 Nov 2002 9:10:14 +0800
From: "Harry" <hr_befine@263.net>
To: MANET mail list <manet@ietf.org>
X-mailer: Foxmail 4.1 [cn]
Mime-Version: 1.0
Content-Type: text/plain;
      charset="GB2312"
Message-Id: <20021108005827.17C292F77E@smtp.x263.net>
Content-Transfer-Encoding: 8bit
X-MIME-Autoconverted: from quoted-printable to 8bit by www1.ietf.org id gA81CGv03128
Subject: [manet] Emulate MANET
Sender: manet-admin@ietf.org
Errors-To: manet-admin@ietf.org
X-BeenThere: manet@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/manet>,
	<mailto:manet-request@ietf.org?subject=unsubscribe>
List-Id: Mobile Ad-hoc Networks  <manet.ietf.org>
List-Post: <mailto:manet@ietf.org>
List-Help: <mailto:manet-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/manet>,
	<mailto:manet-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 8bit

hi,allŁˇ
	I want to emulate MANET in a wired network environment. Who could recommend some softwares to me? I konw NS2 do. Are there anything else?
	Thank u in advance.


best regards 				
ˇˇˇˇˇˇˇˇˇˇˇˇˇˇˇˇHarry
ˇˇˇˇˇˇˇˇˇˇˇˇˇˇˇˇˇˇˇˇ2002-11-08


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


From manet-admin@ietf.org  Thu Nov  7 21:00:56 2002
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id VAA21000
	for <manet-archive@lists.ietf.org>; Thu, 7 Nov 2002 21:00:55 -0500 (EST)
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gA81tKv05549;
	Thu, 7 Nov 2002 20:55:20 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gA81pCv05423
	for <manet@optimus.ietf.org>; Thu, 7 Nov 2002 20:51:12 -0500
Received: from gandalf.icr.a-star.edu.sg (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id UAA20788
	for <manet@ietf.org>; Thu, 7 Nov 2002 20:48:30 -0500 (EST)
Received: from gwserver.icr.a-star.edu.sg (gwserver.icr.a-star.edu.sg [137.132.31.253])
	by gandalf.icr.a-star.edu.sg (8.12.2+Sun/8.12.2) with ESMTP id gA81q3iP008497
	for <manet@ietf.org>; Fri, 8 Nov 2002 09:52:03 +0800 (SGT)
Received: from swl1002
	([172.16.3.193])
	by gwserver.icr.a-star.edu.sg; Fri, 08 Nov 2002 09:44:54 +0800
Message-ID: <002601c286c8$70dfede0$c10310ac@icr.astar.edu.sg>
Reply-To: "Ankur Jain" <stujaina@icr.a-star.edu.sg>
From: "Ankur Jain" <stujaina@icr.a-star.edu.sg>
To: "Harry" <hr_befine@263.net>, "MANET mail list" <manet@ietf.org>
References: <20021108005827.17C292F77E@smtp.x263.net>
Subject: Re: [manet] Emulate MANET
Date: Fri, 8 Nov 2002 09:44:51 +0800
Organization: Institute for Communications Research, Singapore
MIME-Version: 1.0
Content-Type: text/plain;
	charset="GB2312"
Content-Transfer-Encoding: 8bit
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 5.00.2615.200
X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2615.200
Content-Transfer-Encoding: 8bit
Sender: manet-admin@ietf.org
Errors-To: manet-admin@ietf.org
X-BeenThere: manet@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/manet>,
	<mailto:manet-request@ietf.org?subject=unsubscribe>
List-Id: Mobile Ad-hoc Networks  <manet.ietf.org>
List-Post: <mailto:manet@ietf.org>
List-Help: <mailto:manet-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/manet>,
	<mailto:manet-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 8bit

Hi harry,

For emulating MANET in a wired environment, MobiEmu is the best software. I
think it will satisfy all your needs of emulating the adhoc in a lab
setting.

You can find it at http://mobiemu.sourceforge.net/

Regards
Ankur






----- Original Message -----
From: Harry <hr_befine@263.net>
To: MANET mail list <manet@ietf.org>
Sent: Friday, November 08, 2002 9:10 AM
Subject: [manet] Emulate MANET


> hi,allŁˇ
> I want to emulate MANET in a wired network environment. Who could
recommend some softwares to me? I konw NS2 do. Are there anything else?
> Thank u in advance.
>
>
> best regards
> ˇˇˇˇˇˇˇˇˇˇˇˇˇˇˇˇHarry
> ˇˇˇˇˇˇˇˇˇˇˇˇˇˇˇˇˇˇˇˇ2002-11-08
>
>
> _______________________________________________
> manet mailing list
> manet@ietf.org
> https://www1.ietf.org/mailman/listinfo/manet

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


From mailnull@www1.ietf.org  Thu Nov  7 21:01:02 2002
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id VAA21022
	for <manet-archive@odin.ietf.org>; Thu, 7 Nov 2002 21:01:02 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id gA823AE05902
	for manet-archive@odin.ietf.org; Thu, 7 Nov 2002 21:03:10 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gA8232v05898
	for <manet-web-archive@optimus.ietf.org>; Thu, 7 Nov 2002 21:03:02 -0500
Received: from www1.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id VAA20993
	for <manet-web-archive@ietf.org>; Thu, 7 Nov 2002 21:00:22 -0500 (EST)
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gA81tKv05549;
	Thu, 7 Nov 2002 20:55:20 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gA81pCv05423
	for <manet@optimus.ietf.org>; Thu, 7 Nov 2002 20:51:12 -0500
Received: from gandalf.icr.a-star.edu.sg (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id UAA20788
	for <manet@ietf.org>; Thu, 7 Nov 2002 20:48:30 -0500 (EST)
Received: from gwserver.icr.a-star.edu.sg (gwserver.icr.a-star.edu.sg [137.132.31.253])
	by gandalf.icr.a-star.edu.sg (8.12.2+Sun/8.12.2) with ESMTP id gA81q3iP008497
	for <manet@ietf.org>; Fri, 8 Nov 2002 09:52:03 +0800 (SGT)
Received: from swl1002
	([172.16.3.193])
	by gwserver.icr.a-star.edu.sg; Fri, 08 Nov 2002 09:44:54 +0800
Message-ID: <002601c286c8$70dfede0$c10310ac@icr.astar.edu.sg>
Reply-To: "Ankur Jain" <stujaina@icr.a-star.edu.sg>
From: "Ankur Jain" <stujaina@icr.a-star.edu.sg>
To: "Harry" <hr_befine@263.net>, "MANET mail list" <manet@ietf.org>
References: <20021108005827.17C292F77E@smtp.x263.net>
Subject: Re: [manet] Emulate MANET
Date: Fri, 8 Nov 2002 09:44:51 +0800
Organization: Institute for Communications Research, Singapore
MIME-Version: 1.0
Content-Type: text/plain;
	charset="GB2312"
Content-Transfer-Encoding: 8bit
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 5.00.2615.200
X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2615.200
Content-Transfer-Encoding: 8bit
Sender: manet-admin@ietf.org
Errors-To: manet-admin@ietf.org
X-BeenThere: manet@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/manet>,
	<mailto:manet-request@ietf.org?subject=unsubscribe>
List-Id: Mobile Ad-hoc Networks  <manet.ietf.org>
List-Post: <mailto:manet@ietf.org>
List-Help: <mailto:manet-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/manet>,
	<mailto:manet-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 8bit
Content-Transfer-Encoding: 8bit

Hi harry,

For emulating MANET in a wired environment, MobiEmu is the best software. I
think it will satisfy all your needs of emulating the adhoc in a lab
setting.

You can find it at http://mobiemu.sourceforge.net/

Regards
Ankur






----- Original Message -----
From: Harry <hr_befine@263.net>
To: MANET mail list <manet@ietf.org>
Sent: Friday, November 08, 2002 9:10 AM
Subject: [manet] Emulate MANET


> hi,allŁˇ
> I want to emulate MANET in a wired network environment. Who could
recommend some softwares to me? I konw NS2 do. Are there anything else?
> Thank u in advance.
>
>
> best regards
> ˇˇˇˇˇˇˇˇˇˇˇˇˇˇˇˇHarry
> ˇˇˇˇˇˇˇˇˇˇˇˇˇˇˇˇˇˇˇˇ2002-11-08
>
>
> _______________________________________________
> manet mailing list
> manet@ietf.org
> https://www1.ietf.org/mailman/listinfo/manet

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



From mailnull@www1.ietf.org  Thu Nov  7 21:10:23 2002
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id UAA20257
	for <manet-archive@odin.ietf.org>; Thu, 7 Nov 2002 20:22:22 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id gA81OT803728
	for manet-archive@odin.ietf.org; Thu, 7 Nov 2002 20:24:29 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gA81ORv03724
	for <manet-web-archive@optimus.ietf.org>; Thu, 7 Nov 2002 20:24:27 -0500
Received: from www1.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id UAA20249
	for <manet-web-archive@ietf.org>; Thu, 7 Nov 2002 20:21:48 -0500 (EST)
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gA81Gsv03290;
	Thu, 7 Nov 2002 20:16:54 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gA81CGv03127
	for <manet@optimus.ietf.org>; Thu, 7 Nov 2002 20:12:16 -0500
Received: from smtp.x263.net (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id UAA20025
	for <manet@ietf.org>; Thu, 7 Nov 2002 20:09:36 -0500 (EST)
Received: from befine (mta5 [127.0.0.1])
	by smtp.x263.net (Postfix) with ESMTP id 17C292F77E
	for <manet@ietf.org>; Fri,  8 Nov 2002 08:58:27 +0800 (CST)
Received: from befine (unknown [211.71.13.13])
	by antispam-5 (Coremail) with SMTP id QLC3BzEMyz34JA0N.1
	for <manet@ietf.org>; Fri, 08 Nov 2002 08:58:28 +0800 (CST)
Date: Fri, 8 Nov 2002 9:10:14 +0800
From: "Harry" <hr_befine@263.net>
To: MANET mail list <manet@ietf.org>
X-mailer: Foxmail 4.1 [cn]
Mime-Version: 1.0
Content-Type: text/plain;
      charset="GB2312"
Message-Id: <20021108005827.17C292F77E@smtp.x263.net>
Content-Transfer-Encoding: 8bit
X-MIME-Autoconverted: from quoted-printable to 8bit by www1.ietf.org id gA81CGv03128
Subject: [manet] Emulate MANET
Sender: manet-admin@ietf.org
Errors-To: manet-admin@ietf.org
X-BeenThere: manet@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/manet>,
	<mailto:manet-request@ietf.org?subject=unsubscribe>
List-Id: Mobile Ad-hoc Networks  <manet.ietf.org>
List-Post: <mailto:manet@ietf.org>
List-Help: <mailto:manet-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/manet>,
	<mailto:manet-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 8bit
Content-Transfer-Encoding: 8bit

hi,allŁˇ
	I want to emulate MANET in a wired network environment. Who could recommend some softwares to me? I konw NS2 do. Are there anything else?
	Thank u in advance.


best regards 				
ˇˇˇˇˇˇˇˇˇˇˇˇˇˇˇˇHarry
ˇˇˇˇˇˇˇˇˇˇˇˇˇˇˇˇˇˇˇˇ2002-11-08


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



From manet-admin@ietf.org  Fri Nov  8 05:02:26 2002
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id FAA11939
	for <manet-archive@lists.ietf.org>; Fri, 8 Nov 2002 05:02:26 -0500 (EST)
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gA89u6v10466;
	Fri, 8 Nov 2002 04:56:06 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gA89lIv10194
	for <manet@optimus.ietf.org>; Fri, 8 Nov 2002 04:47:18 -0500
Received: from concorde.inria.fr (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id EAA11632
	for <manet@ietf.org>; Fri, 8 Nov 2002 04:44:37 -0500 (EST)
Received: from zephyrin (byzantium.inria.fr [128.93.17.6])
	by concorde.inria.fr (8.11.1/8.11.1) with SMTP id gA89l5511158
	for <manet@ietf.org>; Fri, 8 Nov 2002 10:47:05 +0100 (MET)
Message-ID: <000901c2870f$76ff57a0$1f175d80@inria.fr>
From: "Philippe Jacquet" <philippe.jacquet@inria.fr>
To: <manet@ietf.org>
Date: Fri, 8 Nov 2002 11:13:14 +0100
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 5.00.2615.200
X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2615.200
Content-Transfer-Encoding: 7bit
Subject: [manet] draft-ietf-manet-olsr-07.txt
Sender: manet-admin@ietf.org
Errors-To: manet-admin@ietf.org
X-BeenThere: manet@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/manet>,
	<mailto:manet-request@ietf.org?subject=unsubscribe>
List-Id: Mobile Ad-hoc Networks  <manet.ietf.org>
List-Post: <mailto:manet@ietf.org>
List-Help: <mailto:manet-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/manet>,
	<mailto:manet-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 7bit

Hello,

Due to a technical problem of last minute, our draft submission of OLSR v7
failed (again). Sorry for this inconvenience. Anyhow  the draft is available
on the following URL:
http://hipercom.inria.fr/olsr/draft-ietf-manet-olsr-07.txt
Please take a look at it. We will be happy to discuss it during the Atlanta
meeting. There are not big changes from what has already been presented in
Yokohama.

Major changes from version 06 to version 07

     -    Introduction of relay willingness in hellos

     -    Introduction of redundant link set in TC messages

     -    Introduction of packet sequence number in order to clarify
          link management

Philippe


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


From mailnull@www1.ietf.org  Fri Nov  8 05:08:06 2002
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id FAA12007
	for <manet-archive@odin.ietf.org>; Fri, 8 Nov 2002 05:08:06 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id gA8AA6711763
	for manet-archive@odin.ietf.org; Fri, 8 Nov 2002 05:10:06 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gA8AA6v11760
	for <manet-web-archive@optimus.ietf.org>; Fri, 8 Nov 2002 05:10:06 -0500
Received: from www1.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id FAA12004
	for <manet-web-archive@ietf.org>; Fri, 8 Nov 2002 05:07:35 -0500 (EST)
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gA89u6v10466;
	Fri, 8 Nov 2002 04:56:06 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gA89lIv10194
	for <manet@optimus.ietf.org>; Fri, 8 Nov 2002 04:47:18 -0500
Received: from concorde.inria.fr (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id EAA11632
	for <manet@ietf.org>; Fri, 8 Nov 2002 04:44:37 -0500 (EST)
Received: from zephyrin (byzantium.inria.fr [128.93.17.6])
	by concorde.inria.fr (8.11.1/8.11.1) with SMTP id gA89l5511158
	for <manet@ietf.org>; Fri, 8 Nov 2002 10:47:05 +0100 (MET)
Message-ID: <000901c2870f$76ff57a0$1f175d80@inria.fr>
From: "Philippe Jacquet" <philippe.jacquet@inria.fr>
To: <manet@ietf.org>
Date: Fri, 8 Nov 2002 11:13:14 +0100
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 5.00.2615.200
X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2615.200
Content-Transfer-Encoding: 7bit
Subject: [manet] draft-ietf-manet-olsr-07.txt
Sender: manet-admin@ietf.org
Errors-To: manet-admin@ietf.org
X-BeenThere: manet@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/manet>,
	<mailto:manet-request@ietf.org?subject=unsubscribe>
List-Id: Mobile Ad-hoc Networks  <manet.ietf.org>
List-Post: <mailto:manet@ietf.org>
List-Help: <mailto:manet-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/manet>,
	<mailto:manet-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit

Hello,

Due to a technical problem of last minute, our draft submission of OLSR v7
failed (again). Sorry for this inconvenience. Anyhow  the draft is available
on the following URL:
http://hipercom.inria.fr/olsr/draft-ietf-manet-olsr-07.txt
Please take a look at it. We will be happy to discuss it during the Atlanta
meeting. There are not big changes from what has already been presented in
Yokohama.

Major changes from version 06 to version 07

     -    Introduction of relay willingness in hellos

     -    Introduction of redundant link set in TC messages

     -    Introduction of packet sequence number in order to clarify
          link management

Philippe


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



From mailnull@www1.ietf.org  Fri Nov  8 05:53:56 2002
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id FAA12737
	for <manet-archive@odin.ietf.org>; Fri, 8 Nov 2002 05:53:56 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id gA8Atvr14068
	for manet-archive@odin.ietf.org; Fri, 8 Nov 2002 05:55:57 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gA8Atvv14065
	for <manet-web-archive@optimus.ietf.org>; Fri, 8 Nov 2002 05:55:57 -0500
Received: from www1.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id FAA12731
	for <manet-web-archive@ietf.org>; Fri, 8 Nov 2002 05:53:25 -0500 (EST)
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gA8AmWv13762;
	Fri, 8 Nov 2002 05:48:32 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gA8AjCv13643
	for <manet@optimus.ietf.org>; Fri, 8 Nov 2002 05:45:12 -0500
Received: from gomez.cs.pitt.edu (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id FAA12531
	for <manet@ietf.org>; Fri, 8 Nov 2002 05:42:41 -0500 (EST)
Received: from rhenium.cs.pitt.edu (rhenium.cs.pitt.edu [136.142.79.12])
	by gomez.cs.pitt.edu (8.11.6/8.11.5) with ESMTP id gA8AjB830397
	for <manet@ietf.org>; Fri, 8 Nov 2002 05:45:11 -0500
	(envelope-from skhattab@cs.pitt.edu)
Date: Fri, 8 Nov 2002 05:45:11 -0500 (EST)
From: "Sherif E. Mohamed Khattab" <skhattab@cs.pitt.edu>
To: manet@ietf.org
In-Reply-To: <20021108005827.17C292F77E@smtp.x263.net>
Message-ID: <Pine.LNX.4.21.0211080539590.14677-100000@rhenium.cs.pitt.edu>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Subject: [manet] Node misbehavior
Sender: manet-admin@ietf.org
Errors-To: manet-admin@ietf.org
X-BeenThere: manet@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/manet>,
	<mailto:manet-request@ietf.org?subject=unsubscribe>
List-Id: Mobile Ad-hoc Networks  <manet.ietf.org>
List-Post: <mailto:manet@ietf.org>
List-Help: <mailto:manet-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/manet>,
	<mailto:manet-request@ietf.org?subject=subscribe>

Hi All,

   Regarding the problem of a node participating in routing functions
(e.g., route discovery and maintenance) but failing to perform packet
forwarding (dropping packets), due to malice or selfishness. Is
there any routing protocol that addresses this problem?

Thanks,

Sherif
*---------------------------------*
    Sherif E. Mohamed Khattab       
         Ph.D. Student		      
   Department of Computer Science  
     University of Pittsburgh        
 http://www.cs.pitt.edu/~skhattab
*---------------------------------*




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



From manet-admin@ietf.org  Fri Nov  8 05:53:59 2002
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id FAA12750
	for <manet-archive@lists.ietf.org>; Fri, 8 Nov 2002 05:53:59 -0500 (EST)
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gA8AmWv13762;
	Fri, 8 Nov 2002 05:48:32 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gA8AjCv13643
	for <manet@optimus.ietf.org>; Fri, 8 Nov 2002 05:45:12 -0500
Received: from gomez.cs.pitt.edu (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id FAA12531
	for <manet@ietf.org>; Fri, 8 Nov 2002 05:42:41 -0500 (EST)
Received: from rhenium.cs.pitt.edu (rhenium.cs.pitt.edu [136.142.79.12])
	by gomez.cs.pitt.edu (8.11.6/8.11.5) with ESMTP id gA8AjB830397
	for <manet@ietf.org>; Fri, 8 Nov 2002 05:45:11 -0500
	(envelope-from skhattab@cs.pitt.edu)
Date: Fri, 8 Nov 2002 05:45:11 -0500 (EST)
From: "Sherif E. Mohamed Khattab" <skhattab@cs.pitt.edu>
To: manet@ietf.org
In-Reply-To: <20021108005827.17C292F77E@smtp.x263.net>
Message-ID: <Pine.LNX.4.21.0211080539590.14677-100000@rhenium.cs.pitt.edu>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Subject: [manet] Node misbehavior
Sender: manet-admin@ietf.org
Errors-To: manet-admin@ietf.org
X-BeenThere: manet@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/manet>,
	<mailto:manet-request@ietf.org?subject=unsubscribe>
List-Id: Mobile Ad-hoc Networks  <manet.ietf.org>
List-Post: <mailto:manet@ietf.org>
List-Help: <mailto:manet-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/manet>,
	<mailto:manet-request@ietf.org?subject=subscribe>

Hi All,

   Regarding the problem of a node participating in routing functions
(e.g., route discovery and maintenance) but failing to perform packet
forwarding (dropping packets), due to malice or selfishness. Is
there any routing protocol that addresses this problem?

Thanks,

Sherif
*---------------------------------*
    Sherif E. Mohamed Khattab       
         Ph.D. Student		      
   Department of Computer Science  
     University of Pittsburgh        
 http://www.cs.pitt.edu/~skhattab
*---------------------------------*




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


From mailnull@www1.ietf.org  Fri Nov  8 06:19:42 2002
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id GAA13128
	for <manet-archive@odin.ietf.org>; Fri, 8 Nov 2002 06:19:42 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id gA8BLhC15529
	for manet-archive@odin.ietf.org; Fri, 8 Nov 2002 06:21:43 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gA8BLhv15526
	for <manet-web-archive@optimus.ietf.org>; Fri, 8 Nov 2002 06:21:43 -0500
Received: from www1.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id GAA13118
	for <manet-web-archive@ietf.org>; Fri, 8 Nov 2002 06:19:11 -0500 (EST)
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gA8B9pv15089;
	Fri, 8 Nov 2002 06:09:51 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gA8B66v14416
	for <manet@optimus.ietf.org>; Fri, 8 Nov 2002 06:06:06 -0500
Received: from cheviot3.ncl.ac.uk (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id GAA12906
	for <manet@ietf.org>; Fri, 8 Nov 2002 06:03:34 -0500 (EST)
Received: from stavanger (stavanger.ncl.ac.uk [128.240.149.6])
	by cheviot3.ncl.ac.uk (8.10.1/8.10.1) with ESMTP id gA8B5VF28503;
	Fri, 8 Nov 2002 11:05:31 GMT
From: "Einar Vollset" <einar.vollset@ncl.ac.uk>
To: "'Sherif E. Mohamed Khattab'" <skhattab@cs.pitt.edu>
Cc: <manet@ietf.org>
Subject: RE: [manet] Node misbehavior
Date: Fri, 8 Nov 2002 11:05:20 -0000
Message-ID: <000d01c28716$ba9f0850$0695f080@stavanger>
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: 7bit
X-Priority: 3 (Normal)
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook, Build 10.0.3416
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2600.0000
In-Reply-To: <Pine.LNX.4.21.0211080539590.14677-100000@rhenium.cs.pitt.edu>
Importance: Normal
X-Newcastle-MailScanner: Found to be clean (of known viruses)
Content-Transfer-Encoding: 7bit
Sender: manet-admin@ietf.org
Errors-To: manet-admin@ietf.org
X-BeenThere: manet@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/manet>,
	<mailto:manet-request@ietf.org?subject=unsubscribe>
List-Id: Mobile Ad-hoc Networks  <manet.ietf.org>
List-Post: <mailto:manet@ietf.org>
List-Help: <mailto:manet-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/manet>,
	<mailto:manet-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit




If my memory serves me right, I think the CONFIDANT protocol presented
at this year's MobiHoc deals with it.

Cheers,

Einar

---------------------------- 
Einar Vollset
PhD Student
University of Newcastle, UK
http://vollset.org
---------------------------- 

> -----Original Message-----
> From: manet-admin@ietf.org [mailto:manet-admin@ietf.org] On 
> Behalf Of Sherif E. Mohamed Khattab
> Sent: 08 November 2002 10:45
> To: manet@ietf.org
> Subject: [manet] Node misbehavior
> 
> 
> Hi All,
> 
>    Regarding the problem of a node participating in routing 
> functions (e.g., route discovery and maintenance) but failing 
> to perform packet forwarding (dropping packets), due to 
> malice or selfishness. Is there any routing protocol that 
> addresses this problem?
> 
> Thanks,
> 
> Sherif
> *---------------------------------*
>     Sherif E. Mohamed Khattab       
>          Ph.D. Student		      
>    Department of Computer Science  
>      University of Pittsburgh        
>  http://www.cs.pitt.edu/~skhattab
> *---------------------------------*
> 
> 
> 
> 
> _______________________________________________
> manet mailing list
> manet@ietf.org
> https://www1.ietf.org/mailman/listinfo/manet
> 

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



From manet-admin@ietf.org  Fri Nov  8 06:19:44 2002
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id GAA13141
	for <manet-archive@lists.ietf.org>; Fri, 8 Nov 2002 06:19:44 -0500 (EST)
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gA8B9pv15089;
	Fri, 8 Nov 2002 06:09:51 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gA8B66v14416
	for <manet@optimus.ietf.org>; Fri, 8 Nov 2002 06:06:06 -0500
Received: from cheviot3.ncl.ac.uk (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id GAA12906
	for <manet@ietf.org>; Fri, 8 Nov 2002 06:03:34 -0500 (EST)
Received: from stavanger (stavanger.ncl.ac.uk [128.240.149.6])
	by cheviot3.ncl.ac.uk (8.10.1/8.10.1) with ESMTP id gA8B5VF28503;
	Fri, 8 Nov 2002 11:05:31 GMT
From: "Einar Vollset" <einar.vollset@ncl.ac.uk>
To: "'Sherif E. Mohamed Khattab'" <skhattab@cs.pitt.edu>
Cc: <manet@ietf.org>
Subject: RE: [manet] Node misbehavior
Date: Fri, 8 Nov 2002 11:05:20 -0000
Message-ID: <000d01c28716$ba9f0850$0695f080@stavanger>
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: 7bit
X-Priority: 3 (Normal)
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook, Build 10.0.3416
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2600.0000
In-Reply-To: <Pine.LNX.4.21.0211080539590.14677-100000@rhenium.cs.pitt.edu>
Importance: Normal
X-Newcastle-MailScanner: Found to be clean (of known viruses)
Content-Transfer-Encoding: 7bit
Sender: manet-admin@ietf.org
Errors-To: manet-admin@ietf.org
X-BeenThere: manet@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/manet>,
	<mailto:manet-request@ietf.org?subject=unsubscribe>
List-Id: Mobile Ad-hoc Networks  <manet.ietf.org>
List-Post: <mailto:manet@ietf.org>
List-Help: <mailto:manet-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/manet>,
	<mailto:manet-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 7bit




If my memory serves me right, I think the CONFIDANT protocol presented
at this year's MobiHoc deals with it.

Cheers,

Einar

---------------------------- 
Einar Vollset
PhD Student
University of Newcastle, UK
http://vollset.org
---------------------------- 

> -----Original Message-----
> From: manet-admin@ietf.org [mailto:manet-admin@ietf.org] On 
> Behalf Of Sherif E. Mohamed Khattab
> Sent: 08 November 2002 10:45
> To: manet@ietf.org
> Subject: [manet] Node misbehavior
> 
> 
> Hi All,
> 
>    Regarding the problem of a node participating in routing 
> functions (e.g., route discovery and maintenance) but failing 
> to perform packet forwarding (dropping packets), due to 
> malice or selfishness. Is there any routing protocol that 
> addresses this problem?
> 
> Thanks,
> 
> Sherif
> *---------------------------------*
>     Sherif E. Mohamed Khattab       
>          Ph.D. Student		      
>    Department of Computer Science  
>      University of Pittsburgh        
>  http://www.cs.pitt.edu/~skhattab
> *---------------------------------*
> 
> 
> 
> 
> _______________________________________________
> manet mailing list
> manet@ietf.org
> https://www1.ietf.org/mailman/listinfo/manet
> 

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


From mailnull@www1.ietf.org  Fri Nov  8 07:48:14 2002
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id HAA16848
	for <manet-archive@odin.ietf.org>; Fri, 8 Nov 2002 07:48:14 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id gA8CoGh21480
	for manet-archive@odin.ietf.org; Fri, 8 Nov 2002 07:50:16 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gA8CoGv21477
	for <manet-web-archive@optimus.ietf.org>; Fri, 8 Nov 2002 07:50:16 -0500
Received: from www1.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id HAA16812
	for <manet-web-archive@ietf.org>; Fri, 8 Nov 2002 07:47:43 -0500 (EST)
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gA8Cfxv20877;
	Fri, 8 Nov 2002 07:41:59 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gA8Cbev20456
	for <manet@optimus.ietf.org>; Fri, 8 Nov 2002 07:37:40 -0500
Received: from CNRI.Reston.VA.US (localhost [127.0.0.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id HAA15720;
	Fri, 8 Nov 2002 07:35:08 -0500 (EST)
Message-Id: <200211081235.HAA15720@ietf.org>
Mime-Version: 1.0
Content-Type: Multipart/Mixed; Boundary="NextPart"
To: IETF-Announce: ;
Cc: manet@ietf.org
From: Internet-Drafts@ietf.org
Reply-to: Internet-Drafts@ietf.org
Date: Fri, 08 Nov 2002 07:35:08 -0500
Subject: [manet] I-D ACTION:draft-ietf-manet-odmrp-04.txt
Sender: manet-admin@ietf.org
Errors-To: manet-admin@ietf.org
X-BeenThere: manet@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/manet>,
	<mailto:manet-request@ietf.org?subject=unsubscribe>
List-Id: Mobile Ad-hoc Networks  <manet.ietf.org>
List-Post: <mailto:manet@ietf.org>
List-Help: <mailto:manet-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/manet>,
	<mailto:manet-request@ietf.org?subject=subscribe>

--NextPart

A New Internet-Draft is available from the on-line Internet-Drafts directories.
This draft is a work item of the Mobile Ad-hoc Networks Working Group of the IETF.

	Title		: On-Demand Multicast Routing Protocol (ODMRP) for 
                          Ad-Hoc Networks
	Author(s)	: Y. Yi, S. Lee
	Filename	: draft-ietf-manet-odmrp-04.txt
	Pages		: 29
	Date		: 2002-11-7
	
On-Demand Multicast Routing Protocol (ODMRP) is a multicast routing
protocol designed for ad-hoc networks with mobile hosts. ODMRP is
a mesh-based, rather than a conventional tree-based, multicast
scheme and uses a Forwarding Group concept (only a subset of nodes
forwards the multicast packets via scoped flooding). It applies
on-demand procedures to dynamically set up routes and maintain
multicast group membership. ODMRP is well suited for ad-hoc
wireless networks with mobile hosts where bandwidth is limited,
topology changes frequently and rapidly, and power is constrained.

A URL for this Internet-Draft is:
http://www.ietf.org/internet-drafts/draft-ietf-manet-odmrp-04.txt

To remove yourself from the IETF Announcement list, send a message to 
ietf-announce-request with the word unsubscribe in the body of the message.

Internet-Drafts are also available by anonymous FTP. Login with the username
"anonymous" and a password of your e-mail address. After logging in,
type "cd internet-drafts" and then
	"get draft-ietf-manet-odmrp-04.txt".

A list of Internet-Drafts directories can be found in
http://www.ietf.org/shadow.html 
or ftp://ftp.ietf.org/ietf/1shadow-sites.txt


Internet-Drafts can also be obtained by e-mail.

Send a message to:
	mailserv@ietf.org.
In the body type:
	"FILE /internet-drafts/draft-ietf-manet-odmrp-04.txt".
	
NOTE:	The mail server at ietf.org can return the document in
	MIME-encoded form by using the "mpack" utility.  To use this
	feature, insert the command "ENCODING mime" before the "FILE"
	command.  To decode the response(s), you will need "munpack" or
	a MIME-compliant mail reader.  Different MIME-compliant mail readers
	exhibit different behavior, especially when dealing with
	"multipart" MIME messages (i.e. documents which have been split
	up into multiple messages), so check your local documentation on
	how to manipulate these messages.
		
		
Below is the data which will enable a MIME compliant mail reader
implementation to automatically retrieve the ASCII version of the
Internet-Draft.

--NextPart
Content-Type: Multipart/Alternative; Boundary="OtherAccess"

--OtherAccess
Content-Type: Message/External-body;
	access-type="mail-server";
	server="mailserv@ietf.org"

Content-Type: text/plain
Content-ID:	<2002-11-7160211.I-D@ietf.org>

ENCODING mime
FILE /internet-drafts/draft-ietf-manet-odmrp-04.txt

--OtherAccess
Content-Type: Message/External-body;
	name="draft-ietf-manet-odmrp-04.txt";
	site="ftp.ietf.org";
	access-type="anon-ftp";
	directory="internet-drafts"

Content-Type: text/plain
Content-ID:	<2002-11-7160211.I-D@ietf.org>

--OtherAccess--

--NextPart--


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



From manet-admin@ietf.org  Fri Nov  8 07:48:16 2002
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id HAA16862
	for <manet-archive@lists.ietf.org>; Fri, 8 Nov 2002 07:48:16 -0500 (EST)
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gA8Cfxv20877;
	Fri, 8 Nov 2002 07:41:59 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gA8Cbev20456
	for <manet@optimus.ietf.org>; Fri, 8 Nov 2002 07:37:40 -0500
Received: from CNRI.Reston.VA.US (localhost [127.0.0.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id HAA15720;
	Fri, 8 Nov 2002 07:35:08 -0500 (EST)
Message-Id: <200211081235.HAA15720@ietf.org>
Mime-Version: 1.0
Content-Type: Multipart/Mixed; Boundary="NextPart"
To: IETF-Announce: ;
Cc: manet@ietf.org
From: Internet-Drafts@ietf.org
Reply-to: Internet-Drafts@ietf.org
Date: Fri, 08 Nov 2002 07:35:08 -0500
Subject: [manet] I-D ACTION:draft-ietf-manet-odmrp-04.txt
Sender: manet-admin@ietf.org
Errors-To: manet-admin@ietf.org
X-BeenThere: manet@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/manet>,
	<mailto:manet-request@ietf.org?subject=unsubscribe>
List-Id: Mobile Ad-hoc Networks  <manet.ietf.org>
List-Post: <mailto:manet@ietf.org>
List-Help: <mailto:manet-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/manet>,
	<mailto:manet-request@ietf.org?subject=subscribe>

--NextPart

A New Internet-Draft is available from the on-line Internet-Drafts directories.
This draft is a work item of the Mobile Ad-hoc Networks Working Group of the IETF.

	Title		: On-Demand Multicast Routing Protocol (ODMRP) for 
                          Ad-Hoc Networks
	Author(s)	: Y. Yi, S. Lee
	Filename	: draft-ietf-manet-odmrp-04.txt
	Pages		: 29
	Date		: 2002-11-7
	
On-Demand Multicast Routing Protocol (ODMRP) is a multicast routing
protocol designed for ad-hoc networks with mobile hosts. ODMRP is
a mesh-based, rather than a conventional tree-based, multicast
scheme and uses a Forwarding Group concept (only a subset of nodes
forwards the multicast packets via scoped flooding). It applies
on-demand procedures to dynamically set up routes and maintain
multicast group membership. ODMRP is well suited for ad-hoc
wireless networks with mobile hosts where bandwidth is limited,
topology changes frequently and rapidly, and power is constrained.

A URL for this Internet-Draft is:
http://www.ietf.org/internet-drafts/draft-ietf-manet-odmrp-04.txt

To remove yourself from the IETF Announcement list, send a message to 
ietf-announce-request with the word unsubscribe in the body of the message.

Internet-Drafts are also available by anonymous FTP. Login with the username
"anonymous" and a password of your e-mail address. After logging in,
type "cd internet-drafts" and then
	"get draft-ietf-manet-odmrp-04.txt".

A list of Internet-Drafts directories can be found in
http://www.ietf.org/shadow.html 
or ftp://ftp.ietf.org/ietf/1shadow-sites.txt


Internet-Drafts can also be obtained by e-mail.

Send a message to:
	mailserv@ietf.org.
In the body type:
	"FILE /internet-drafts/draft-ietf-manet-odmrp-04.txt".
	
NOTE:	The mail server at ietf.org can return the document in
	MIME-encoded form by using the "mpack" utility.  To use this
	feature, insert the command "ENCODING mime" before the "FILE"
	command.  To decode the response(s), you will need "munpack" or
	a MIME-compliant mail reader.  Different MIME-compliant mail readers
	exhibit different behavior, especially when dealing with
	"multipart" MIME messages (i.e. documents which have been split
	up into multiple messages), so check your local documentation on
	how to manipulate these messages.
		
		
Below is the data which will enable a MIME compliant mail reader
implementation to automatically retrieve the ASCII version of the
Internet-Draft.

--NextPart
Content-Type: Multipart/Alternative; Boundary="OtherAccess"

--OtherAccess
Content-Type: Message/External-body;
	access-type="mail-server";
	server="mailserv@ietf.org"

Content-Type: text/plain
Content-ID:	<2002-11-7160211.I-D@ietf.org>

ENCODING mime
FILE /internet-drafts/draft-ietf-manet-odmrp-04.txt

--OtherAccess
Content-Type: Message/External-body;
	name="draft-ietf-manet-odmrp-04.txt";
	site="ftp.ietf.org";
	access-type="anon-ftp";
	directory="internet-drafts"

Content-Type: text/plain
Content-ID:	<2002-11-7160211.I-D@ietf.org>

--OtherAccess--

--NextPart--


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


From mailnull@www1.ietf.org  Fri Nov  8 07:48:42 2002
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id HAA16888
	for <manet-archive@odin.ietf.org>; Fri, 8 Nov 2002 07:48:42 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id gA8Coij21523
	for manet-archive@odin.ietf.org; Fri, 8 Nov 2002 07:50:44 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gA8Cohv21520
	for <manet-web-archive@optimus.ietf.org>; Fri, 8 Nov 2002 07:50:43 -0500
Received: from www1.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id HAA16842
	for <manet-web-archive@ietf.org>; Fri, 8 Nov 2002 07:48:11 -0500 (EST)
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gA8CfAv20838;
	Fri, 8 Nov 2002 07:41:10 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gA8Cbbv20449
	for <manet@optimus.ietf.org>; Fri, 8 Nov 2002 07:37:37 -0500
Received: from CNRI.Reston.VA.US (localhost [127.0.0.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id HAA15708;
	Fri, 8 Nov 2002 07:35:04 -0500 (EST)
Message-Id: <200211081235.HAA15708@ietf.org>
Mime-Version: 1.0
Content-Type: Multipart/Mixed; Boundary="NextPart"
To: IETF-Announce: ;
Cc: manet@ietf.org
From: Internet-Drafts@ietf.org
Reply-to: Internet-Drafts@ietf.org
Date: Fri, 08 Nov 2002 07:35:04 -0500
Subject: [manet] I-D ACTION:draft-ietf-manet-lanmar-05.txt
Sender: manet-admin@ietf.org
Errors-To: manet-admin@ietf.org
X-BeenThere: manet@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/manet>,
	<mailto:manet-request@ietf.org?subject=unsubscribe>
List-Id: Mobile Ad-hoc Networks  <manet.ietf.org>
List-Post: <mailto:manet@ietf.org>
List-Help: <mailto:manet-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/manet>,
	<mailto:manet-request@ietf.org?subject=subscribe>

--NextPart

A New Internet-Draft is available from the on-line Internet-Drafts directories.
This draft is a work item of the Mobile Ad-hoc Networks Working Group of the IETF.

	Title		: Landmark Routing Protocol (LANMAR) for Large Scale Ad 
                          Hoc Networks
	Author(s)	: M. Gerla et al.
	Filename	: draft-ietf-manet-lanmar-05.txt
	Pages		: 21
	Date		: 2002-11-7
	
The Landmark Routing Protocol (LANMAR) utilizes the concept of 
landmark for scalable routing in large, mobile ad hoc networks.  
It relies on the notion of group mobility: i.e., a logical group 
(for example a team of coworkers at a convention) moves in a 
coordinated fashion.  The existence of such logical group can be 
efficiently reflected in the addressing scheme.  It assumes that 
an IP like address is used consisting of a group ID (or subnet ID)
and a host ID, i.e. <Group ID, Host ID>.  A landmark is dynamically
elected in each group.  The route to a landmark is propagated 
throughout the network using a Distance Vector mechanism.  
Separately, each node in the network uses a scoped routing 
algorithm (e.g., FSR) to learn about routes within a given (max 
number of hops) scope.  To route a packet to a destination outside
its scope, a node will direct the packet to the landmark 
corresponding to the group ID of such destination.  Once the packet
approaches the landmark, it will typically be routed directly to 
the destination.  A solution to nodes outside of the scope of their 
landmark (i.e., drifters) is also addressed in the draft.  Thus, 
by summarizing in the corresponding landmarks the routing 
information of remote groups of nodes  and by using the truncated 
local routing table, LANMAR dramatically reduces routing table size
and routing update overhead in large networks.  The dynamic 
election of landmarks enables LANMAR to cope with mobile 
environments.  LANMAR is well suited to provide an efficient and 
scalable routing solution in large, mobile, ad hoc environments in
which group behavior applies and high mobility renders traditional 
routing schemes inefficient.

A URL for this Internet-Draft is:
http://www.ietf.org/internet-drafts/draft-ietf-manet-lanmar-05.txt

To remove yourself from the IETF Announcement list, send a message to 
ietf-announce-request with the word unsubscribe in the body of the message.

Internet-Drafts are also available by anonymous FTP. Login with the username
"anonymous" and a password of your e-mail address. After logging in,
type "cd internet-drafts" and then
	"get draft-ietf-manet-lanmar-05.txt".

A list of Internet-Drafts directories can be found in
http://www.ietf.org/shadow.html 
or ftp://ftp.ietf.org/ietf/1shadow-sites.txt


Internet-Drafts can also be obtained by e-mail.

Send a message to:
	mailserv@ietf.org.
In the body type:
	"FILE /internet-drafts/draft-ietf-manet-lanmar-05.txt".
	
NOTE:	The mail server at ietf.org can return the document in
	MIME-encoded form by using the "mpack" utility.  To use this
	feature, insert the command "ENCODING mime" before the "FILE"
	command.  To decode the response(s), you will need "munpack" or
	a MIME-compliant mail reader.  Different MIME-compliant mail readers
	exhibit different behavior, especially when dealing with
	"multipart" MIME messages (i.e. documents which have been split
	up into multiple messages), so check your local documentation on
	how to manipulate these messages.
		
		
Below is the data which will enable a MIME compliant mail reader
implementation to automatically retrieve the ASCII version of the
Internet-Draft.

--NextPart
Content-Type: Multipart/Alternative; Boundary="OtherAccess"

--OtherAccess
Content-Type: Message/External-body;
	access-type="mail-server";
	server="mailserv@ietf.org"

Content-Type: text/plain
Content-ID:	<2002-11-7160202.I-D@ietf.org>

ENCODING mime
FILE /internet-drafts/draft-ietf-manet-lanmar-05.txt

--OtherAccess
Content-Type: Message/External-body;
	name="draft-ietf-manet-lanmar-05.txt";
	site="ftp.ietf.org";
	access-type="anon-ftp";
	directory="internet-drafts"

Content-Type: text/plain
Content-ID:	<2002-11-7160202.I-D@ietf.org>

--OtherAccess--

--NextPart--


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



From manet-admin@ietf.org  Fri Nov  8 07:48:44 2002
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id HAA16901
	for <manet-archive@lists.ietf.org>; Fri, 8 Nov 2002 07:48:44 -0500 (EST)
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gA8CfAv20838;
	Fri, 8 Nov 2002 07:41:10 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gA8Cbbv20449
	for <manet@optimus.ietf.org>; Fri, 8 Nov 2002 07:37:37 -0500
Received: from CNRI.Reston.VA.US (localhost [127.0.0.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id HAA15708;
	Fri, 8 Nov 2002 07:35:04 -0500 (EST)
Message-Id: <200211081235.HAA15708@ietf.org>
Mime-Version: 1.0
Content-Type: Multipart/Mixed; Boundary="NextPart"
To: IETF-Announce: ;
Cc: manet@ietf.org
From: Internet-Drafts@ietf.org
Reply-to: Internet-Drafts@ietf.org
Date: Fri, 08 Nov 2002 07:35:04 -0500
Subject: [manet] I-D ACTION:draft-ietf-manet-lanmar-05.txt
Sender: manet-admin@ietf.org
Errors-To: manet-admin@ietf.org
X-BeenThere: manet@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/manet>,
	<mailto:manet-request@ietf.org?subject=unsubscribe>
List-Id: Mobile Ad-hoc Networks  <manet.ietf.org>
List-Post: <mailto:manet@ietf.org>
List-Help: <mailto:manet-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/manet>,
	<mailto:manet-request@ietf.org?subject=subscribe>

--NextPart

A New Internet-Draft is available from the on-line Internet-Drafts directories.
This draft is a work item of the Mobile Ad-hoc Networks Working Group of the IETF.

	Title		: Landmark Routing Protocol (LANMAR) for Large Scale Ad 
                          Hoc Networks
	Author(s)	: M. Gerla et al.
	Filename	: draft-ietf-manet-lanmar-05.txt
	Pages		: 21
	Date		: 2002-11-7
	
The Landmark Routing Protocol (LANMAR) utilizes the concept of 
landmark for scalable routing in large, mobile ad hoc networks.  
It relies on the notion of group mobility: i.e., a logical group 
(for example a team of coworkers at a convention) moves in a 
coordinated fashion.  The existence of such logical group can be 
efficiently reflected in the addressing scheme.  It assumes that 
an IP like address is used consisting of a group ID (or subnet ID)
and a host ID, i.e. <Group ID, Host ID>.  A landmark is dynamically
elected in each group.  The route to a landmark is propagated 
throughout the network using a Distance Vector mechanism.  
Separately, each node in the network uses a scoped routing 
algorithm (e.g., FSR) to learn about routes within a given (max 
number of hops) scope.  To route a packet to a destination outside
its scope, a node will direct the packet to the landmark 
corresponding to the group ID of such destination.  Once the packet
approaches the landmark, it will typically be routed directly to 
the destination.  A solution to nodes outside of the scope of their 
landmark (i.e., drifters) is also addressed in the draft.  Thus, 
by summarizing in the corresponding landmarks the routing 
information of remote groups of nodes  and by using the truncated 
local routing table, LANMAR dramatically reduces routing table size
and routing update overhead in large networks.  The dynamic 
election of landmarks enables LANMAR to cope with mobile 
environments.  LANMAR is well suited to provide an efficient and 
scalable routing solution in large, mobile, ad hoc environments in
which group behavior applies and high mobility renders traditional 
routing schemes inefficient.

A URL for this Internet-Draft is:
http://www.ietf.org/internet-drafts/draft-ietf-manet-lanmar-05.txt

To remove yourself from the IETF Announcement list, send a message to 
ietf-announce-request with the word unsubscribe in the body of the message.

Internet-Drafts are also available by anonymous FTP. Login with the username
"anonymous" and a password of your e-mail address. After logging in,
type "cd internet-drafts" and then
	"get draft-ietf-manet-lanmar-05.txt".

A list of Internet-Drafts directories can be found in
http://www.ietf.org/shadow.html 
or ftp://ftp.ietf.org/ietf/1shadow-sites.txt


Internet-Drafts can also be obtained by e-mail.

Send a message to:
	mailserv@ietf.org.
In the body type:
	"FILE /internet-drafts/draft-ietf-manet-lanmar-05.txt".
	
NOTE:	The mail server at ietf.org can return the document in
	MIME-encoded form by using the "mpack" utility.  To use this
	feature, insert the command "ENCODING mime" before the "FILE"
	command.  To decode the response(s), you will need "munpack" or
	a MIME-compliant mail reader.  Different MIME-compliant mail readers
	exhibit different behavior, especially when dealing with
	"multipart" MIME messages (i.e. documents which have been split
	up into multiple messages), so check your local documentation on
	how to manipulate these messages.
		
		
Below is the data which will enable a MIME compliant mail reader
implementation to automatically retrieve the ASCII version of the
Internet-Draft.

--NextPart
Content-Type: Multipart/Alternative; Boundary="OtherAccess"

--OtherAccess
Content-Type: Message/External-body;
	access-type="mail-server";
	server="mailserv@ietf.org"

Content-Type: text/plain
Content-ID:	<2002-11-7160202.I-D@ietf.org>

ENCODING mime
FILE /internet-drafts/draft-ietf-manet-lanmar-05.txt

--OtherAccess
Content-Type: Message/External-body;
	name="draft-ietf-manet-lanmar-05.txt";
	site="ftp.ietf.org";
	access-type="anon-ftp";
	directory="internet-drafts"

Content-Type: text/plain
Content-ID:	<2002-11-7160202.I-D@ietf.org>

--OtherAccess--

--NextPart--


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


From manet-admin@ietf.org  Fri Nov  8 08:17:46 2002
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA17853
	for <manet-archive@lists.ietf.org>; Fri, 8 Nov 2002 08:17:46 -0500 (EST)
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gA8DBRv23400;
	Fri, 8 Nov 2002 08:11:27 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gA8DB0v23362
	for <manet@optimus.ietf.org>; Fri, 8 Nov 2002 08:11:00 -0500
Received: from smtp.covadmail.net (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id IAA17661
	for <manet@ietf.org>; Fri, 8 Nov 2002 08:08:26 -0500 (EST)
Received: (covad.net 3655 invoked from network); 8 Nov 2002 13:10:57 -0000
Received: from h-64-105-46-73.mclnva23.covad.net (HELO amd2100) (64.105.46.73)
  by sun-qmail16 with SMTP; 8 Nov 2002 13:10:57 -0000
Reply-To: <herb@cnds.jhu.edu>
From: "Herbert Rubens" <herb@cnds.jhu.edu>
To: "'Sherif E. Mohamed Khattab'" <skhattab@cs.pitt.edu>, <manet@ietf.org>
Subject: RE: [manet] Node misbehavior
Date: Fri, 8 Nov 2002 08:11:03 -0500
Organization: Center for Networking and Distributed Systems
Message-ID: <001401c28728$4d94e380$0300a8c0@amd2100>
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: 7bit
X-Priority: 3 (Normal)
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook, Build 10.0.2627
In-reply-to: <Pine.LNX.4.21.0211080539590.14677-100000@rhenium.cs.pitt.edu>
X-MIMEOLE: Produced By Microsoft MimeOLE V6.00.2800.1106
Importance: Normal
Content-Transfer-Encoding: 7bit
Sender: manet-admin@ietf.org
Errors-To: manet-admin@ietf.org
X-BeenThere: manet@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/manet>,
	<mailto:manet-request@ietf.org?subject=unsubscribe>
List-Id: Mobile Ad-hoc Networks  <manet.ietf.org>
List-Post: <mailto:manet@ietf.org>
List-Help: <mailto:manet-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/manet>,
	<mailto:manet-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 7bit

You may also want to take a look at our paper from the security workshop
at MobiCom 2002.

http://www.cnds.jhu.edu/pub/papers/wise2002_sec_routing.pdf

Hope this helps,

-Herb



-----Original Message-----
From: manet-admin@ietf.org [mailto:manet-admin@ietf.org] On Behalf Of
Sherif E. Mohamed Khattab
Sent: Friday, November 08, 2002 5:45 AM
To: manet@ietf.org
Subject: [manet] Node misbehavior

Hi All,

   Regarding the problem of a node participating in routing functions
(e.g., route discovery and maintenance) but failing to perform packet
forwarding (dropping packets), due to malice or selfishness. Is
there any routing protocol that addresses this problem?

Thanks,

Sherif
*---------------------------------*
    Sherif E. Mohamed Khattab       
         Ph.D. Student		      
   Department of Computer Science  
     University of Pittsburgh        
 http://www.cs.pitt.edu/~skhattab
*---------------------------------*




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



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


From mailnull@www1.ietf.org  Fri Nov  8 08:20:11 2002
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA17946
	for <manet-archive@odin.ietf.org>; Fri, 8 Nov 2002 08:20:11 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id gA8DMEr23898
	for manet-archive@odin.ietf.org; Fri, 8 Nov 2002 08:22:14 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gA8DMDv23895
	for <manet-web-archive@optimus.ietf.org>; Fri, 8 Nov 2002 08:22:13 -0500
Received: from www1.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA17926
	for <manet-web-archive@ietf.org>; Fri, 8 Nov 2002 08:19:40 -0500 (EST)
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gA8DBRv23400;
	Fri, 8 Nov 2002 08:11:27 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gA8DB0v23362
	for <manet@optimus.ietf.org>; Fri, 8 Nov 2002 08:11:00 -0500
Received: from smtp.covadmail.net (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id IAA17661
	for <manet@ietf.org>; Fri, 8 Nov 2002 08:08:26 -0500 (EST)
Received: (covad.net 3655 invoked from network); 8 Nov 2002 13:10:57 -0000
Received: from h-64-105-46-73.mclnva23.covad.net (HELO amd2100) (64.105.46.73)
  by sun-qmail16 with SMTP; 8 Nov 2002 13:10:57 -0000
Reply-To: <herb@cnds.jhu.edu>
From: "Herbert Rubens" <herb@cnds.jhu.edu>
To: "'Sherif E. Mohamed Khattab'" <skhattab@cs.pitt.edu>, <manet@ietf.org>
Subject: RE: [manet] Node misbehavior
Date: Fri, 8 Nov 2002 08:11:03 -0500
Organization: Center for Networking and Distributed Systems
Message-ID: <001401c28728$4d94e380$0300a8c0@amd2100>
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: 7bit
X-Priority: 3 (Normal)
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook, Build 10.0.2627
In-reply-to: <Pine.LNX.4.21.0211080539590.14677-100000@rhenium.cs.pitt.edu>
X-MIMEOLE: Produced By Microsoft MimeOLE V6.00.2800.1106
Importance: Normal
Content-Transfer-Encoding: 7bit
Sender: manet-admin@ietf.org
Errors-To: manet-admin@ietf.org
X-BeenThere: manet@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/manet>,
	<mailto:manet-request@ietf.org?subject=unsubscribe>
List-Id: Mobile Ad-hoc Networks  <manet.ietf.org>
List-Post: <mailto:manet@ietf.org>
List-Help: <mailto:manet-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/manet>,
	<mailto:manet-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit

You may also want to take a look at our paper from the security workshop
at MobiCom 2002.

http://www.cnds.jhu.edu/pub/papers/wise2002_sec_routing.pdf

Hope this helps,

-Herb



-----Original Message-----
From: manet-admin@ietf.org [mailto:manet-admin@ietf.org] On Behalf Of
Sherif E. Mohamed Khattab
Sent: Friday, November 08, 2002 5:45 AM
To: manet@ietf.org
Subject: [manet] Node misbehavior

Hi All,

   Regarding the problem of a node participating in routing functions
(e.g., route discovery and maintenance) but failing to perform packet
forwarding (dropping packets), due to malice or selfishness. Is
there any routing protocol that addresses this problem?

Thanks,

Sherif
*---------------------------------*
    Sherif E. Mohamed Khattab       
         Ph.D. Student		      
   Department of Computer Science  
     University of Pittsburgh        
 http://www.cs.pitt.edu/~skhattab
*---------------------------------*




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



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



From manet-admin@ietf.org  Fri Nov  8 09:36:02 2002
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA19971
	for <manet-archive@lists.ietf.org>; Fri, 8 Nov 2002 09:36:02 -0500 (EST)
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gA8EScv28585;
	Fri, 8 Nov 2002 09:28:38 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gA8ENav28289
	for <manet@optimus.ietf.org>; Fri, 8 Nov 2002 09:23:36 -0500
Received: from d12lmsgate-5.de.ibm.com (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA19455
	for <manet@ietf.org>; Fri, 8 Nov 2002 09:21:02 -0500 (EST)
Received: from d12relay02.de.ibm.com (d12relay02.de.ibm.com [9.165.215.23])
	by d12lmsgate-5.de.ibm.com (8.12.3/8.12.3) with ESMTP id gA8ENSvx026198;
	Fri, 8 Nov 2002 15:23:28 +0100
Received: from sihl.zurich.ibm.com (sihl.zurich.ibm.com [9.4.16.232])
	by d12relay02.de.ibm.com (8.12.3/NCO/VER6.4) with SMTP id gA8ENSCZ064768;
	Fri, 8 Nov 2002 15:23:28 +0100
Received: from dhcp70-158.zurich.ibm.com by sihl.zurich.ibm.com (AIX 4.3/UCB 5.64/4.03)
          id AA61438 from <sob@zurich.ibm.com>; Fri, 8 Nov 2002 15:23:27 +0100
Subject: RE: [manet] Node misbehavior
From: Sonja Buchegger <sob@zurich.ibm.com>
To: "\"'Sherif E. Mohamed  \"Khattab'" <skhattab@cs.pitt.edu>,
        Einar Vollset
	 <einar.vollset@ncl.ac.uk>
Cc: manet@ietf.org
In-Reply-To: <000d01c28716$ba9f0850$0695f080@stavanger>
References: <000d01c28716$ba9f0850$0695f080@stavanger>
Content-Type: text/plain
Content-Transfer-Encoding: 7bit
X-Mailer: Ximian Evolution 1.0.3 (1.0.3-4) 
Date: 08 Nov 2002 15:23:26 +0100
Message-Id: <1036765407.15766.205.camel@donoratico>
Mime-Version: 1.0
Content-Transfer-Encoding: 7bit
Sender: manet-admin@ietf.org
Errors-To: manet-admin@ietf.org
X-BeenThere: manet@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/manet>,
	<mailto:manet-request@ietf.org?subject=unsubscribe>
List-Id: Mobile Ad-hoc Networks  <manet.ietf.org>
List-Post: <mailto:manet@ietf.org>
List-Help: <mailto:manet-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/manet>,
	<mailto:manet-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 7bit

Hi,
yes, Einar's memory is correct. CONFIDANT (Cooperation of Nodes,
Fairness in Dynamic Ad-hoc NeTworks) works as an extension to a routing
protocol, in the MobiHOC 2002 paper we applied it to DSR and showed
simulation results for the "no forwarding" type of misbehavior. You can
download the paper (and also a short survey paper on related work) from
my website at http://www.zurich.ibm.com/~sob/books.html . 

To get an overview of some other solutions, have a look at the current
issue  of ACM SIGMOBILE's Mobile Computing and Communications Review
volume 6 number 4 containing a report edited by Levente Buttyan and
Jean-Pierre Hubaux on a working session on security in mobile ad-hoc
networks held at EPFL in June. You can download the report and
presentation slides from http://icawww.epfl.ch/buttyan/June12/index.html

As posted previously on this list, Feng Zhu maintains a list of papers
dealing with security/cooperation/malice/selfishness at
http://www.ccs.neu.edu/home/zhufeng/security_manet.html .

best regards,
sonja
-- 
_/  _/  _/  _/  _/  _/  _/  _/  _/  _/  _/  _/  _/  _/  _/  _/  _/  _/  

 Sonja Buchegger
 IBM Zurich Research Lab    email: sob@zurich.ibm.com
 Saeumerstr. 4              phone: +41/1/724 82 37
 CH-8803 Rueschlikon        fax : +41/1/724 89 55
 Switzerland                http://www.zurich.ibm.com/~sob
             

On Fri, 2002-11-08 at 12:05, Einar Vollset wrote:
> 
> 
> 
> If my memory serves me right, I think the CONFIDANT protocol presented
> at this year's MobiHoc deals with it.
> 
> Cheers,
> 
> Einar
> 
> ---------------------------- 
> Einar Vollset
> PhD Student
> University of Newcastle, UK
> http://vollset.org
> ---------------------------- 
> 
> > -----Original Message-----
> > From: manet-admin@ietf.org [mailto:manet-admin@ietf.org] On 
> > Behalf Of Sherif E. Mohamed Khattab
> > Sent: 08 November 2002 10:45
> > To: manet@ietf.org
> > Subject: [manet] Node misbehavior
> > 
> > 
> > Hi All,
> > 
> >    Regarding the problem of a node participating in routing 
> > functions (e.g., route discovery and maintenance) but failing 
> > to perform packet forwarding (dropping packets), due to 
> > malice or selfishness. Is there any routing protocol that 
> > addresses this problem?
> > 
> > Thanks,
> > 
> > Sherif
> > *---------------------------------*
> >     Sherif E. Mohamed Khattab       
> >          Ph.D. Student		      
> >    Department of Computer Science  
> >      University of Pittsburgh        
> >  http://www.cs.pitt.edu/~skhattab
> > *---------------------------------*
> > 
> > 
> > 
> > 
> > _______________________________________________
> > manet mailing list
> > manet@ietf.org
> > https://www1.ietf.org/mailman/listinfo/manet
> > 
> 
> _______________________________________________
> manet mailing list
> manet@ietf.org
> https://www1.ietf.org/mailman/listinfo/manet
> 


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


From mailnull@www1.ietf.org  Fri Nov  8 09:47:28 2002
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA20229
	for <manet-archive@odin.ietf.org>; Fri, 8 Nov 2002 09:47:28 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id gA8EnUo30545
	for manet-archive@odin.ietf.org; Fri, 8 Nov 2002 09:49:30 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gA8EnTv30542
	for <manet-web-archive@optimus.ietf.org>; Fri, 8 Nov 2002 09:49:29 -0500
Received: from www1.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA20225
	for <manet-web-archive@ietf.org>; Fri, 8 Nov 2002 09:46:57 -0500 (EST)
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gA8EScv28585;
	Fri, 8 Nov 2002 09:28:38 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gA8ENav28289
	for <manet@optimus.ietf.org>; Fri, 8 Nov 2002 09:23:36 -0500
Received: from d12lmsgate-5.de.ibm.com (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA19455
	for <manet@ietf.org>; Fri, 8 Nov 2002 09:21:02 -0500 (EST)
Received: from d12relay02.de.ibm.com (d12relay02.de.ibm.com [9.165.215.23])
	by d12lmsgate-5.de.ibm.com (8.12.3/8.12.3) with ESMTP id gA8ENSvx026198;
	Fri, 8 Nov 2002 15:23:28 +0100
Received: from sihl.zurich.ibm.com (sihl.zurich.ibm.com [9.4.16.232])
	by d12relay02.de.ibm.com (8.12.3/NCO/VER6.4) with SMTP id gA8ENSCZ064768;
	Fri, 8 Nov 2002 15:23:28 +0100
Received: from dhcp70-158.zurich.ibm.com by sihl.zurich.ibm.com (AIX 4.3/UCB 5.64/4.03)
          id AA61438 from <sob@zurich.ibm.com>; Fri, 8 Nov 2002 15:23:27 +0100
Subject: RE: [manet] Node misbehavior
From: Sonja Buchegger <sob@zurich.ibm.com>
To: "\"'Sherif E. Mohamed  \"Khattab'" <skhattab@cs.pitt.edu>,
        Einar Vollset
	 <einar.vollset@ncl.ac.uk>
Cc: manet@ietf.org
In-Reply-To: <000d01c28716$ba9f0850$0695f080@stavanger>
References: <000d01c28716$ba9f0850$0695f080@stavanger>
Content-Type: text/plain
Content-Transfer-Encoding: 7bit
X-Mailer: Ximian Evolution 1.0.3 (1.0.3-4) 
Date: 08 Nov 2002 15:23:26 +0100
Message-Id: <1036765407.15766.205.camel@donoratico>
Mime-Version: 1.0
Content-Transfer-Encoding: 7bit
Sender: manet-admin@ietf.org
Errors-To: manet-admin@ietf.org
X-BeenThere: manet@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/manet>,
	<mailto:manet-request@ietf.org?subject=unsubscribe>
List-Id: Mobile Ad-hoc Networks  <manet.ietf.org>
List-Post: <mailto:manet@ietf.org>
List-Help: <mailto:manet-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/manet>,
	<mailto:manet-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit

Hi,
yes, Einar's memory is correct. CONFIDANT (Cooperation of Nodes,
Fairness in Dynamic Ad-hoc NeTworks) works as an extension to a routing
protocol, in the MobiHOC 2002 paper we applied it to DSR and showed
simulation results for the "no forwarding" type of misbehavior. You can
download the paper (and also a short survey paper on related work) from
my website at http://www.zurich.ibm.com/~sob/books.html . 

To get an overview of some other solutions, have a look at the current
issue  of ACM SIGMOBILE's Mobile Computing and Communications Review
volume 6 number 4 containing a report edited by Levente Buttyan and
Jean-Pierre Hubaux on a working session on security in mobile ad-hoc
networks held at EPFL in June. You can download the report and
presentation slides from http://icawww.epfl.ch/buttyan/June12/index.html

As posted previously on this list, Feng Zhu maintains a list of papers
dealing with security/cooperation/malice/selfishness at
http://www.ccs.neu.edu/home/zhufeng/security_manet.html .

best regards,
sonja
-- 
_/  _/  _/  _/  _/  _/  _/  _/  _/  _/  _/  _/  _/  _/  _/  _/  _/  _/  

 Sonja Buchegger
 IBM Zurich Research Lab    email: sob@zurich.ibm.com
 Saeumerstr. 4              phone: +41/1/724 82 37
 CH-8803 Rueschlikon        fax : +41/1/724 89 55
 Switzerland                http://www.zurich.ibm.com/~sob
             

On Fri, 2002-11-08 at 12:05, Einar Vollset wrote:
> 
> 
> 
> If my memory serves me right, I think the CONFIDANT protocol presented
> at this year's MobiHoc deals with it.
> 
> Cheers,
> 
> Einar
> 
> ---------------------------- 
> Einar Vollset
> PhD Student
> University of Newcastle, UK
> http://vollset.org
> ---------------------------- 
> 
> > -----Original Message-----
> > From: manet-admin@ietf.org [mailto:manet-admin@ietf.org] On 
> > Behalf Of Sherif E. Mohamed Khattab
> > Sent: 08 November 2002 10:45
> > To: manet@ietf.org
> > Subject: [manet] Node misbehavior
> > 
> > 
> > Hi All,
> > 
> >    Regarding the problem of a node participating in routing 
> > functions (e.g., route discovery and maintenance) but failing 
> > to perform packet forwarding (dropping packets), due to 
> > malice or selfishness. Is there any routing protocol that 
> > addresses this problem?
> > 
> > Thanks,
> > 
> > Sherif
> > *---------------------------------*
> >     Sherif E. Mohamed Khattab       
> >          Ph.D. Student		      
> >    Department of Computer Science  
> >      University of Pittsburgh        
> >  http://www.cs.pitt.edu/~skhattab
> > *---------------------------------*
> > 
> > 
> > 
> > 
> > _______________________________________________
> > manet mailing list
> > manet@ietf.org
> > https://www1.ietf.org/mailman/listinfo/manet
> > 
> 
> _______________________________________________
> manet mailing list
> manet@ietf.org
> https://www1.ietf.org/mailman/listinfo/manet
> 


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



From mailnull@www1.ietf.org  Fri Nov  8 10:51:06 2002
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA24140
	for <manet-archive@odin.ietf.org>; Fri, 8 Nov 2002 10:51:05 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id gA8Fr8x05131
	for manet-archive@odin.ietf.org; Fri, 8 Nov 2002 10:53:08 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gA8Fr8v05128
	for <manet-web-archive@optimus.ietf.org>; Fri, 8 Nov 2002 10:53:08 -0500
Received: from www1.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA24108
	for <manet-web-archive@ietf.org>; Fri, 8 Nov 2002 10:50:34 -0500 (EST)
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gA8FjMv04591;
	Fri, 8 Nov 2002 10:45:22 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gA8FhJv04473
	for <manet@optimus.ietf.org>; Fri, 8 Nov 2002 10:43:19 -0500
Received: from meryl.it.uu.se (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA23579
	for <manet@ietf.org>; Fri, 8 Nov 2002 10:40:45 -0500 (EST)
Received: from nebulosa.it.uu.se (nebulosa.it.uu.se [130.238.8.24])
	by meryl.it.uu.se (8.8.5/8.8.5) with ESMTP id QAA05143;
	Fri, 8 Nov 2002 16:43:14 +0100 (MET)
From: Erik =?ISO-8859-1?Q?Nordstr=F6m?= <erik.nordstrom@it.uu.se>
To: MANET LIST <manet@ietf.org>
Cc: Aodvimpl-Public <aodvimpl-public@lists.sourceforge.net>
Content-Type: text/plain; charset=ISO-8859-1
Message-Id: <1036770193.18890.6.camel@nebulosa.it.uu.se>
Mime-Version: 1.0
X-Mailer: Ximian Evolution 1.1.90 (Preview Release)
Date: 08 Nov 2002 16:43:14 +0100
Content-Transfer-Encoding: 8bit
Content-Transfer-Encoding: 8bit
Subject: [manet] New release: APE Testbed v0.4, now boots from live CD-ROM!
Sender: manet-admin@ietf.org
Errors-To: manet-admin@ietf.org
X-BeenThere: manet@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/manet>,
	<mailto:manet-request@ietf.org?subject=unsubscribe>
List-Id: Mobile Ad-hoc Networks  <manet.ietf.org>
List-Post: <mailto:manet@ietf.org>
List-Help: <mailto:manet-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/manet>,
	<mailto:manet-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 8bit
Content-Transfer-Encoding: 8bit

Hello

I would like to announce a new release of the APE Testbed. APE is the
Ad-hoc Protocol Evaluation Testbed, developed at Uppsala University in
Sweden. The purpose of APE is to be able to perform large scale real
world tests of ad-hoc routing protocols. APE is not necessarily just
for ad-hoc - use the source code to build your own customized test
environment.

Key Features:

* Use APE to easily distribute and install a pre-configured test
environment based on Linux. APE tests are easy to run - use students
or colleagues as test monkeys!

* APE can be easily installed and run from within an existing Linux or
Windows (DOS) environment

* Alternatively, run APE from the APE bootable live CD-ROM (ISO image
available on the APE download page).

* APE has a scripting system which is used to create scenarios that
can be run over and over again, so that tests can be reproduced as
accurately as possible. Participants are given instructions generated
from the scenario file during the tests.

* APE has the "Virtual Mobility" metric, that can characterize the
degree of mobility of a testrun.

* Use APE log files to re-run a test in APE-view, a graphical
application that show topological configurations of the ad-hoc
network.

* Collect log files and analyze them with the APE analysis
tools. Calculate packet delivery ratio and much more.

* APE runs most available ad-hoc routing protocols.


For more information, see:

http://apetestbed.sourceforge.net

Documentation:

http://apetestbed.sourceforge.net/ape-testbed.pdf

Downloads:

http://sourceforge.net/projects/apetestbed

-- 
Erik Nordström <erik.nordstrom@it.uu.se>

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



From manet-admin@ietf.org  Fri Nov  8 10:51:32 2002
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA24185
	for <manet-archive@lists.ietf.org>; Fri, 8 Nov 2002 10:51:32 -0500 (EST)
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gA8FjMv04591;
	Fri, 8 Nov 2002 10:45:22 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gA8FhJv04473
	for <manet@optimus.ietf.org>; Fri, 8 Nov 2002 10:43:19 -0500
Received: from meryl.it.uu.se (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA23579
	for <manet@ietf.org>; Fri, 8 Nov 2002 10:40:45 -0500 (EST)
Received: from nebulosa.it.uu.se (nebulosa.it.uu.se [130.238.8.24])
	by meryl.it.uu.se (8.8.5/8.8.5) with ESMTP id QAA05143;
	Fri, 8 Nov 2002 16:43:14 +0100 (MET)
From: Erik =?ISO-8859-1?Q?Nordstr=F6m?= <erik.nordstrom@it.uu.se>
To: MANET LIST <manet@ietf.org>
Cc: Aodvimpl-Public <aodvimpl-public@lists.sourceforge.net>
Content-Type: text/plain; charset=ISO-8859-1
Message-Id: <1036770193.18890.6.camel@nebulosa.it.uu.se>
Mime-Version: 1.0
X-Mailer: Ximian Evolution 1.1.90 (Preview Release)
Date: 08 Nov 2002 16:43:14 +0100
Content-Transfer-Encoding: 8bit
Content-Transfer-Encoding: 8bit
Subject: [manet] New release: APE Testbed v0.4, now boots from live CD-ROM!
Sender: manet-admin@ietf.org
Errors-To: manet-admin@ietf.org
X-BeenThere: manet@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/manet>,
	<mailto:manet-request@ietf.org?subject=unsubscribe>
List-Id: Mobile Ad-hoc Networks  <manet.ietf.org>
List-Post: <mailto:manet@ietf.org>
List-Help: <mailto:manet-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/manet>,
	<mailto:manet-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 8bit

Hello

I would like to announce a new release of the APE Testbed. APE is the
Ad-hoc Protocol Evaluation Testbed, developed at Uppsala University in
Sweden. The purpose of APE is to be able to perform large scale real
world tests of ad-hoc routing protocols. APE is not necessarily just
for ad-hoc - use the source code to build your own customized test
environment.

Key Features:

* Use APE to easily distribute and install a pre-configured test
environment based on Linux. APE tests are easy to run - use students
or colleagues as test monkeys!

* APE can be easily installed and run from within an existing Linux or
Windows (DOS) environment

* Alternatively, run APE from the APE bootable live CD-ROM (ISO image
available on the APE download page).

* APE has a scripting system which is used to create scenarios that
can be run over and over again, so that tests can be reproduced as
accurately as possible. Participants are given instructions generated
from the scenario file during the tests.

* APE has the "Virtual Mobility" metric, that can characterize the
degree of mobility of a testrun.

* Use APE log files to re-run a test in APE-view, a graphical
application that show topological configurations of the ad-hoc
network.

* Collect log files and analyze them with the APE analysis
tools. Calculate packet delivery ratio and much more.

* APE runs most available ad-hoc routing protocols.


For more information, see:

http://apetestbed.sourceforge.net

Documentation:

http://apetestbed.sourceforge.net/ape-testbed.pdf

Downloads:

http://sourceforge.net/projects/apetestbed

-- 
Erik Nordström <erik.nordstrom@it.uu.se>

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


From manet-admin@ietf.org  Fri Nov  8 13:16:19 2002
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA04203
	for <manet-archive@lists.ietf.org>; Fri, 8 Nov 2002 13:16:19 -0500 (EST)
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gA8IA9v17097;
	Fri, 8 Nov 2002 13:10:09 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gA8I6Sv16390
	for <manet@optimus.ietf.org>; Fri, 8 Nov 2002 13:06:28 -0500
Received: from mail.scires.com (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA03383
	for <manet@ietf.org>; Fri, 8 Nov 2002 13:03:52 -0500 (EST)
Received: from SRCATL-MTA by mail.scires.com
	with Novell_GroupWise; Fri, 08 Nov 2002 13:07:24 -0500
Message-Id: <sdcbb70c.065@mail.scires.com>
X-Mailer: Novell GroupWise Internet Agent 6.0.2 Beta
Date: Fri, 08 Nov 2002 13:07:18 -0500
From: "Pete Sholander" <psholand@scires.com>
To: <manet@ietf.org>
Mime-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
Content-Transfer-Encoding: 7bit
Subject: [manet] ZRP / Hybrid Routing Protocol Implementation
Sender: manet-admin@ietf.org
Errors-To: manet-admin@ietf.org
X-BeenThere: manet@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/manet>,
	<mailto:manet-request@ietf.org?subject=unsubscribe>
List-Id: Mobile Ad-hoc Networks  <manet.ietf.org>
List-Post: <mailto:manet@ietf.org>
List-Help: <mailto:manet-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/manet>,
	<mailto:manet-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 7bit

Dear Gentle Posters,

SRC has worked with Zygmunt Haas and Marc Pearlman over the past 2+
years to develop a commercial-grade implementation of a "ZRP-esque"
hybrid routing protocol.  That software currently runs on Red Hat Linux,
Debian Linux, Windows 2000, Windows CE (PocketPC 2002), and a JTRS
Step2C radio emulator.  The Linux code has also been ported to run in
QualNet 3.1.  

Implementation overviews and *initial* performance results have been
published in MILCOM 2002 and 2002 SDR Technical Conference.  (The MILCOM
paper compares versus an *old* version of OLSR, so the results are
illustrative and *not* definitive!!!)  In brief, the proactive component
is a QoS-aware, timer-based link-state algorithm.  The reactive
component provides explicit source-routing based on QoS metrics.  The
"bordercasting algorithm" is simplified from the current IETF I-D from
Cornell.  We have plans to replace (or supplement) those
proactive/reactive components with some of the IETF standards
(TBRPF/OLSR/AODV/DSR ?).

Gov't funding sponsors were AFRL/IF, DARPA ATO, CECOM, and STRICOM. 
Beta code has been shipped to some gov't orgs and several other U.S. DoD
contractors.  (I'm working the "open-source", academic users, non-US
users, ... issues with my SRC management at present.)  An open-demo of
20-50 nodes might should happen at Fort Hood in 2003.

So, Marc Pearlman and I will be at Atlanta meeting to opine about
whether the ZRP / hybrid-routing work should continue in the IETF for a
bit (e.g., generate updated/simplified I-Ds that focus on the
hybrid-routing framework and bordercast mechanism for the SF Meeting)
... or just move to IRTF.  

Cya' at the ATL meeting:)
Pete Sholander
Scientific Research Corporation		
Atlanta, GA		

E: psholander@scires.com
V: 770-989-9551
  

  

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


From mailnull@www1.ietf.org  Fri Nov  8 14:21:17 2002
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA09231
	for <manet-archive@odin.ietf.org>; Fri, 8 Nov 2002 14:21:17 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id gA8JNMx23251
	for manet-archive@odin.ietf.org; Fri, 8 Nov 2002 14:23:22 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gA8JNMv23248
	for <manet-web-archive@optimus.ietf.org>; Fri, 8 Nov 2002 14:23:22 -0500
Received: from www1.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA09201
	for <manet-web-archive@ietf.org>; Fri, 8 Nov 2002 14:20:46 -0500 (EST)
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gA8IA9v17097;
	Fri, 8 Nov 2002 13:10:09 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gA8I6Sv16390
	for <manet@optimus.ietf.org>; Fri, 8 Nov 2002 13:06:28 -0500
Received: from mail.scires.com (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA03383
	for <manet@ietf.org>; Fri, 8 Nov 2002 13:03:52 -0500 (EST)
Received: from SRCATL-MTA by mail.scires.com
	with Novell_GroupWise; Fri, 08 Nov 2002 13:07:24 -0500
Message-Id: <sdcbb70c.065@mail.scires.com>
X-Mailer: Novell GroupWise Internet Agent 6.0.2 Beta
Date: Fri, 08 Nov 2002 13:07:18 -0500
From: "Pete Sholander" <psholand@scires.com>
To: <manet@ietf.org>
Mime-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
Content-Transfer-Encoding: 7bit
Subject: [manet] ZRP / Hybrid Routing Protocol Implementation
Sender: manet-admin@ietf.org
Errors-To: manet-admin@ietf.org
X-BeenThere: manet@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/manet>,
	<mailto:manet-request@ietf.org?subject=unsubscribe>
List-Id: Mobile Ad-hoc Networks  <manet.ietf.org>
List-Post: <mailto:manet@ietf.org>
List-Help: <mailto:manet-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/manet>,
	<mailto:manet-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit

Dear Gentle Posters,

SRC has worked with Zygmunt Haas and Marc Pearlman over the past 2+
years to develop a commercial-grade implementation of a "ZRP-esque"
hybrid routing protocol.  That software currently runs on Red Hat Linux,
Debian Linux, Windows 2000, Windows CE (PocketPC 2002), and a JTRS
Step2C radio emulator.  The Linux code has also been ported to run in
QualNet 3.1.  

Implementation overviews and *initial* performance results have been
published in MILCOM 2002 and 2002 SDR Technical Conference.  (The MILCOM
paper compares versus an *old* version of OLSR, so the results are
illustrative and *not* definitive!!!)  In brief, the proactive component
is a QoS-aware, timer-based link-state algorithm.  The reactive
component provides explicit source-routing based on QoS metrics.  The
"bordercasting algorithm" is simplified from the current IETF I-D from
Cornell.  We have plans to replace (or supplement) those
proactive/reactive components with some of the IETF standards
(TBRPF/OLSR/AODV/DSR ?).

Gov't funding sponsors were AFRL/IF, DARPA ATO, CECOM, and STRICOM. 
Beta code has been shipped to some gov't orgs and several other U.S. DoD
contractors.  (I'm working the "open-source", academic users, non-US
users, ... issues with my SRC management at present.)  An open-demo of
20-50 nodes might should happen at Fort Hood in 2003.

So, Marc Pearlman and I will be at Atlanta meeting to opine about
whether the ZRP / hybrid-routing work should continue in the IETF for a
bit (e.g., generate updated/simplified I-Ds that focus on the
hybrid-routing framework and bordercast mechanism for the SF Meeting)
... or just move to IRTF.  

Cya' at the ATL meeting:)
Pete Sholander
Scientific Research Corporation		
Atlanta, GA		

E: psholander@scires.com
V: 770-989-9551
  

  

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



From mailnull@www1.ietf.org  Fri Nov  8 15:50:49 2002
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA13412
	for <manet-archive@odin.ietf.org>; Fri, 8 Nov 2002 15:50:49 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id gA8KqtR28342
	for manet-archive@odin.ietf.org; Fri, 8 Nov 2002 15:52:55 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gA8Kqtv28339
	for <manet-web-archive@optimus.ietf.org>; Fri, 8 Nov 2002 15:52:55 -0500
Received: from www1.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA13377
	for <manet-web-archive@ietf.org>; Fri, 8 Nov 2002 15:50:18 -0500 (EST)
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gA8KjTv28054;
	Fri, 8 Nov 2002 15:45:29 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gA8KhRv27995
	for <manet@optimus.ietf.org>; Fri, 8 Nov 2002 15:43:27 -0500
Received: from mail.qual-pro.com (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA12944
	for <manet@ietf.org>; Fri, 8 Nov 2002 15:40:49 -0500 (EST)
Received: from qual-pro.com (yokneam.ecm.qual-pro.com [192.168.1.3])
	by mail.qual-pro.com (8.12.1/8.12.1) with ESMTP id gA8KhKJE002998
	(version=TLSv1/SSLv3 cipher=RC4-MD5 bits=128 verify=NO)
	for <manet@ietf.org>; Fri, 8 Nov 2002 12:43:20 -0800
Message-ID: <3DCC21E8.4000700@qual-pro.com>
Date: Fri, 08 Nov 2002 12:43:20 -0800
From: Darrell Shane <Darrell.Shane@qual-pro.com>
Organization: Qual-Pro Corporation
User-Agent: Mozilla/5.0 (Windows; U; WinNT4.0; en-US; rv:1.0.1) Gecko/20020823 Netscape/7.0
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: manet@ietf.org
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit
Subject: [manet] Looking for the right forum to publish a new ad hoc routing protocol
Sender: manet-admin@ietf.org
Errors-To: manet-admin@ietf.org
X-BeenThere: manet@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/manet>,
	<mailto:manet-request@ietf.org?subject=unsubscribe>
List-Id: Mobile Ad-hoc Networks  <manet.ietf.org>
List-Post: <mailto:manet@ietf.org>
List-Help: <mailto:manet-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/manet>,
	<mailto:manet-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit

Hello, I am interested in publishing some work on a new ad hoc
routing protocol, and I am looking for the right forum.  Including
illustrations, the paper is around 30 pages, and it was difficult
to trim the page count down that low.  The abstract follows.


The Dynamic Mobility (DynaMo) routing protocol is a new reactive,
location based, ad hoc, wireless routing protocol.  The key features
of DynaMo are its tight integration with wired networks (such as the
Internet) and multi-hopping.  Peer-to-peer and region casting
communications through either persistent or transient routes are
supported.  DynaMo is designed for hybrid wired/wireless networks,
such as vehicle transportation systems, where resiliency, robustness
and security are critical.

DynaMo enables packets to hop from vehicle to vehicle along the route
that connects the source to the destination.  Tight integration with
TCP/IP wired networks is achieved through the novel use of the Domain
Name Services (DNS) to locate a node.  Network resiliency is a direct
result of overlapping coverage.  Robustness is achieved through
DynaMo's flexibility.  Routes can be through moving or stationary
nodes, and regardless of the node's mobility, route maintenance is a
localized process.  Each participating node optimizes its portion of
the route.  The foundation of secure communication is based on a
hybrid public/private key encryption system; a node's public key is
available through a query to DNS.


What forums do you recommend?

Thank you,
Darrell
Qual-Pro Corporation

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



From manet-admin@ietf.org  Fri Nov  8 15:51:13 2002
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA13439
	for <manet-archive@lists.ietf.org>; Fri, 8 Nov 2002 15:51:13 -0500 (EST)
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gA8KjTv28054;
	Fri, 8 Nov 2002 15:45:29 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gA8KhRv27995
	for <manet@optimus.ietf.org>; Fri, 8 Nov 2002 15:43:27 -0500
Received: from mail.qual-pro.com (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA12944
	for <manet@ietf.org>; Fri, 8 Nov 2002 15:40:49 -0500 (EST)
Received: from qual-pro.com (yokneam.ecm.qual-pro.com [192.168.1.3])
	by mail.qual-pro.com (8.12.1/8.12.1) with ESMTP id gA8KhKJE002998
	(version=TLSv1/SSLv3 cipher=RC4-MD5 bits=128 verify=NO)
	for <manet@ietf.org>; Fri, 8 Nov 2002 12:43:20 -0800
Message-ID: <3DCC21E8.4000700@qual-pro.com>
Date: Fri, 08 Nov 2002 12:43:20 -0800
From: Darrell Shane <Darrell.Shane@qual-pro.com>
Organization: Qual-Pro Corporation
User-Agent: Mozilla/5.0 (Windows; U; WinNT4.0; en-US; rv:1.0.1) Gecko/20020823 Netscape/7.0
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: manet@ietf.org
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit
Subject: [manet] Looking for the right forum to publish a new ad hoc routing protocol
Sender: manet-admin@ietf.org
Errors-To: manet-admin@ietf.org
X-BeenThere: manet@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/manet>,
	<mailto:manet-request@ietf.org?subject=unsubscribe>
List-Id: Mobile Ad-hoc Networks  <manet.ietf.org>
List-Post: <mailto:manet@ietf.org>
List-Help: <mailto:manet-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/manet>,
	<mailto:manet-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 7bit

Hello, I am interested in publishing some work on a new ad hoc
routing protocol, and I am looking for the right forum.  Including
illustrations, the paper is around 30 pages, and it was difficult
to trim the page count down that low.  The abstract follows.


The Dynamic Mobility (DynaMo) routing protocol is a new reactive,
location based, ad hoc, wireless routing protocol.  The key features
of DynaMo are its tight integration with wired networks (such as the
Internet) and multi-hopping.  Peer-to-peer and region casting
communications through either persistent or transient routes are
supported.  DynaMo is designed for hybrid wired/wireless networks,
such as vehicle transportation systems, where resiliency, robustness
and security are critical.

DynaMo enables packets to hop from vehicle to vehicle along the route
that connects the source to the destination.  Tight integration with
TCP/IP wired networks is achieved through the novel use of the Domain
Name Services (DNS) to locate a node.  Network resiliency is a direct
result of overlapping coverage.  Robustness is achieved through
DynaMo's flexibility.  Routes can be through moving or stationary
nodes, and regardless of the node's mobility, route maintenance is a
localized process.  Each participating node optimizes its portion of
the route.  The foundation of secure communication is based on a
hybrid public/private key encryption system; a node's public key is
available through a query to DNS.


What forums do you recommend?

Thank you,
Darrell
Qual-Pro Corporation

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


From manet-admin@ietf.org  Fri Nov  8 21:31:41 2002
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id VAA27541
	for <manet-archive@lists.ietf.org>; Fri, 8 Nov 2002 21:31:41 -0500 (EST)
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gA92PTv17704;
	Fri, 8 Nov 2002 21:25:29 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gA92Miv17579
	for <manet@optimus.ietf.org>; Fri, 8 Nov 2002 21:22:44 -0500
Received: from mail5 (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id VAA26683
	for <manet@ietf.org>; Fri, 8 Nov 2002 21:20:03 -0500 (EST)
Received: from commlablorry ([61.129.42.18])
 by mail5.eastday.com (iPlanet Messaging Server 5.2 (built Feb 21 2002))
 with ESMTPA id <0H5A005AIEMUT9@mail5.eastday.com> for manet@ietf.org; Sat,
 09 Nov 2002 10:23:18 +0800 (CST)
Date: Sat, 09 Nov 2002 09:52:30 +0800
From: Ruiliang Chen <chenrlk@eastday.com>
Subject: Re: [manet] ZRP / Hybrid Routing Protocol Implementation
To: Pete Sholander <psholand@scires.com>
Cc: manet@ietf.org
Message-id: <028501c28797$084f9580$1616270a@commlablorry>
MIME-version: 1.0
X-MIMEOLE: Produced By Microsoft MimeOLE V6.00.2462.0000
X-Mailer: Microsoft Outlook Express 6.00.2462.0000
Content-type: text/plain; charset=iso-8859-1
Content-transfer-encoding: 7BIT
X-Priority: 3
X-MSMail-priority: Normal
References: <sdcbb70c.065@mail.scires.com>
Content-Transfer-Encoding: 7BIT
Sender: manet-admin@ietf.org
Errors-To: manet-admin@ietf.org
X-BeenThere: manet@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/manet>,
	<mailto:manet-request@ietf.org?subject=unsubscribe>
List-Id: Mobile Ad-hoc Networks  <manet.ietf.org>
List-Post: <mailto:manet@ietf.org>
List-Help: <mailto:manet-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/manet>,
	<mailto:manet-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 7BIT

Dear Pete,

I'm interested in what physical layer and data link layer you are using for implementing ZRP. Is that 802.11 compatible? Thanks!

Ruiliang Chen
Fudan University, P.R. China

----- Original Message ----- 
From: "Pete Sholander" <psholand@scires.com>
To: <manet@ietf.org>
Sent: Saturday, November 09, 2002 2:07 AM
Subject: [manet] ZRP / Hybrid Routing Protocol Implementation


> Dear Gentle Posters,
> 
> SRC has worked with Zygmunt Haas and Marc Pearlman over the past 2+
> years to develop a commercial-grade implementation of a "ZRP-esque"
> hybrid routing protocol.  That software currently runs on Red Hat Linux,
> Debian Linux, Windows 2000, Windows CE (PocketPC 2002), and a JTRS
> Step2C radio emulator.  The Linux code has also been ported to run in
> QualNet 3.1.  
> 
> Implementation overviews and *initial* performance results have been
> published in MILCOM 2002 and 2002 SDR Technical Conference.  (The MILCOM
> paper compares versus an *old* version of OLSR, so the results are
> illustrative and *not* definitive!!!)  In brief, the proactive component
> is a QoS-aware, timer-based link-state algorithm.  The reactive
> component provides explicit source-routing based on QoS metrics.  The
> "bordercasting algorithm" is simplified from the current IETF I-D from
> Cornell.  We have plans to replace (or supplement) those
> proactive/reactive components with some of the IETF standards
> (TBRPF/OLSR/AODV/DSR ?).
> 
> Gov't funding sponsors were AFRL/IF, DARPA ATO, CECOM, and STRICOM. 
> Beta code has been shipped to some gov't orgs and several other U.S. DoD
> contractors.  (I'm working the "open-source", academic users, non-US
> users, ... issues with my SRC management at present.)  An open-demo of
> 20-50 nodes might should happen at Fort Hood in 2003.
> 
> So, Marc Pearlman and I will be at Atlanta meeting to opine about
> whether the ZRP / hybrid-routing work should continue in the IETF for a
> bit (e.g., generate updated/simplified I-Ds that focus on the
> hybrid-routing framework and bordercast mechanism for the SF Meeting)
> ... or just move to IRTF.  
> 
> Cya' at the ATL meeting:)
> Pete Sholander
> Scientific Research Corporation 
> Atlanta, GA 
> 
> E: psholander@scires.com
> V: 770-989-9551
>   
> 
>   
> 
> _______________________________________________
> manet mailing list
> manet@ietf.org
> https://www1.ietf.org/mailman/listinfo/manet
_______________________________________________
manet mailing list
manet@ietf.org
https://www1.ietf.org/mailman/listinfo/manet


From mailnull@www1.ietf.org  Fri Nov  8 21:34:46 2002
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id VAA27805
	for <manet-archive@odin.ietf.org>; Fri, 8 Nov 2002 21:34:46 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id gA92atE18378
	for manet-archive@odin.ietf.org; Fri, 8 Nov 2002 21:36:55 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gA92atv18375
	for <manet-web-archive@optimus.ietf.org>; Fri, 8 Nov 2002 21:36:55 -0500
Received: from www1.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id VAA27738
	for <manet-web-archive@ietf.org>; Fri, 8 Nov 2002 21:34:15 -0500 (EST)
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gA92PTv17704;
	Fri, 8 Nov 2002 21:25:29 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gA92Miv17579
	for <manet@optimus.ietf.org>; Fri, 8 Nov 2002 21:22:44 -0500
Received: from mail5 (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id VAA26683
	for <manet@ietf.org>; Fri, 8 Nov 2002 21:20:03 -0500 (EST)
Received: from commlablorry ([61.129.42.18])
 by mail5.eastday.com (iPlanet Messaging Server 5.2 (built Feb 21 2002))
 with ESMTPA id <0H5A005AIEMUT9@mail5.eastday.com> for manet@ietf.org; Sat,
 09 Nov 2002 10:23:18 +0800 (CST)
Date: Sat, 09 Nov 2002 09:52:30 +0800
From: Ruiliang Chen <chenrlk@eastday.com>
Subject: Re: [manet] ZRP / Hybrid Routing Protocol Implementation
To: Pete Sholander <psholand@scires.com>
Cc: manet@ietf.org
Message-id: <028501c28797$084f9580$1616270a@commlablorry>
MIME-version: 1.0
X-MIMEOLE: Produced By Microsoft MimeOLE V6.00.2462.0000
X-Mailer: Microsoft Outlook Express 6.00.2462.0000
Content-type: text/plain; charset=iso-8859-1
Content-transfer-encoding: 7BIT
X-Priority: 3
X-MSMail-priority: Normal
References: <sdcbb70c.065@mail.scires.com>
Content-Transfer-Encoding: 7BIT
Sender: manet-admin@ietf.org
Errors-To: manet-admin@ietf.org
X-BeenThere: manet@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/manet>,
	<mailto:manet-request@ietf.org?subject=unsubscribe>
List-Id: Mobile Ad-hoc Networks  <manet.ietf.org>
List-Post: <mailto:manet@ietf.org>
List-Help: <mailto:manet-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/manet>,
	<mailto:manet-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 7BIT
Content-Transfer-Encoding: 7BIT

Dear Pete,

I'm interested in what physical layer and data link layer you are using for implementing ZRP. Is that 802.11 compatible? Thanks!

Ruiliang Chen
Fudan University, P.R. China

----- Original Message ----- 
From: "Pete Sholander" <psholand@scires.com>
To: <manet@ietf.org>
Sent: Saturday, November 09, 2002 2:07 AM
Subject: [manet] ZRP / Hybrid Routing Protocol Implementation


> Dear Gentle Posters,
> 
> SRC has worked with Zygmunt Haas and Marc Pearlman over the past 2+
> years to develop a commercial-grade implementation of a "ZRP-esque"
> hybrid routing protocol.  That software currently runs on Red Hat Linux,
> Debian Linux, Windows 2000, Windows CE (PocketPC 2002), and a JTRS
> Step2C radio emulator.  The Linux code has also been ported to run in
> QualNet 3.1.  
> 
> Implementation overviews and *initial* performance results have been
> published in MILCOM 2002 and 2002 SDR Technical Conference.  (The MILCOM
> paper compares versus an *old* version of OLSR, so the results are
> illustrative and *not* definitive!!!)  In brief, the proactive component
> is a QoS-aware, timer-based link-state algorithm.  The reactive
> component provides explicit source-routing based on QoS metrics.  The
> "bordercasting algorithm" is simplified from the current IETF I-D from
> Cornell.  We have plans to replace (or supplement) those
> proactive/reactive components with some of the IETF standards
> (TBRPF/OLSR/AODV/DSR ?).
> 
> Gov't funding sponsors were AFRL/IF, DARPA ATO, CECOM, and STRICOM. 
> Beta code has been shipped to some gov't orgs and several other U.S. DoD
> contractors.  (I'm working the "open-source", academic users, non-US
> users, ... issues with my SRC management at present.)  An open-demo of
> 20-50 nodes might should happen at Fort Hood in 2003.
> 
> So, Marc Pearlman and I will be at Atlanta meeting to opine about
> whether the ZRP / hybrid-routing work should continue in the IETF for a
> bit (e.g., generate updated/simplified I-Ds that focus on the
> hybrid-routing framework and bordercast mechanism for the SF Meeting)
> ... or just move to IRTF.  
> 
> Cya' at the ATL meeting:)
> Pete Sholander
> Scientific Research Corporation 
> Atlanta, GA 
> 
> E: psholander@scires.com
> V: 770-989-9551
>   
> 
>   
> 
> _______________________________________________
> manet mailing list
> manet@ietf.org
> https://www1.ietf.org/mailman/listinfo/manet
_______________________________________________
manet mailing list
manet@ietf.org
https://www1.ietf.org/mailman/listinfo/manet



From manet-admin@ietf.org  Fri Nov  8 23:28:50 2002
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id XAA01132
	for <manet-archive@lists.ietf.org>; Fri, 8 Nov 2002 23:28:50 -0500 (EST)
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gA94NNv24787;
	Fri, 8 Nov 2002 23:23:23 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gA94Lev24730
	for <manet@optimus.ietf.org>; Fri, 8 Nov 2002 23:21:40 -0500
Received: from ims21.stu.nus.edu.sg (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id XAA00920
	for <manet@ietf.org>; Fri, 8 Nov 2002 23:18:59 -0500 (EST)
Received: from mbxsrv26.stu.nus.edu.sg ([137.132.14.236]) by ims21.stu.nus.edu.sg with Microsoft SMTPSVC(5.0.2195.4905);
	 Sat, 9 Nov 2002 12:21:25 +0800
X-MimeOLE: Produced By Microsoft Exchange V6.0.6249.0
content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: multipart/alternative;
	boundary="----_=_NextPart_001_01C287A7.6C9E4118"
Date: Sat, 9 Nov 2002 12:21:07 +0800
Message-ID: <6330DC96389A924A804F52FA3848930E703DA8@MBXSRV26.stu.nus.edu.sg>
Thread-Topic: Energy of mobile nodes in MANET simuaion
Thread-Index: AcKHp24FDxqhn/eaSDOD8LB/RZYzTg==
From: "Marwaha Shivanajay" <engp1609@nus.edu.sg>
To: <manet@ietf.org>
X-OriginalArrivalTime: 09 Nov 2002 04:21:25.0319 (UTC) FILETIME=[77743D70:01C287A7]
Subject: [manet] Energy of mobile nodes in MANET simuaion
Sender: manet-admin@ietf.org
Errors-To: manet-admin@ietf.org
X-BeenThere: manet@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/manet>,
	<mailto:manet-request@ietf.org?subject=unsubscribe>
List-Id: Mobile Ad-hoc Networks  <manet.ietf.org>
List-Post: <mailto:manet@ietf.org>
List-Help: <mailto:manet-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/manet>,
	<mailto:manet-request@ietf.org?subject=subscribe>

This is a multi-part message in MIME format.

------_=_NextPart_001_01C287A7.6C9E4118
Content-Type: text/plain;
	charset="US-ASCII"
Content-Transfer-Encoding: quoted-printable

Hi,
I want to know how much should be the initial node energy in joules for
a MANET simulation (in NS-2)??
Also kindly advice how much should is the energy expended for the
transmission and reception of packets by a mobile node.

In case we do not set the initial node energy in MANET simulation, would
the nodes be having infinite energy??

Thanks and best regrads,
Shivanajay=20
National University of S'pore.


------_=_NextPart_001_01C287A7.6C9E4118
Content-Type: text/html;
	charset="US-ASCII"
Content-Transfer-Encoding: quoted-printable

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD><TITLE>Message</TITLE>
<META http-equiv=3DContent-Type content=3D"text/html; =
charset=3Dus-ascii">
<META content=3D"MSHTML 6.00.2800.1106" name=3DGENERATOR></HEAD>
<BODY>
<DIV><FONT face=3DArial size=3D2>Hi,<BR>I want to know how much should =
be the=20
initial node<SPAN class=3D785461504-09112002> </SPAN>energy&nbsp;<SPAN=20
class=3D785461504-09112002>in joules&nbsp;for</SPAN> a MANET =
simulation&nbsp;<SPAN=20
class=3D785461504-09112002>(</SPAN>in NS<SPAN=20
class=3D785461504-09112002>-2</SPAN><SPAN=20
class=3D785461504-09112002>)</SPAN>??<BR><SPAN=20
class=3D785461504-09112002></SPAN>A<SPAN class=3D785461504-09112002>lso =
kindly=20
advice how much should&nbsp;is the energy&nbsp;expended for&nbsp;the=20
transmission and reception of packets by a mobile =
node.</SPAN><BR></FONT></DIV>
<DIV><FONT><FONT face=3DArial size=3D2>In case we do not set the initial =
node energy=20
in<SPAN class=3D785461504-09112002> </SPAN>MANET<SPAN =
class=3D785461504-09112002>=20
simulation</SPAN>, would the nodes be having infinite en<SPAN=20
class=3D785461504-09112002>e</SPAN>rgy??<BR><BR>Thanks and best=20
regrads,<BR>Shivanajay&nbsp;<BR>National University of=20
S'pore.<BR></FONT></DIV></FONT></BODY></HTML>
=00
------_=_NextPart_001_01C287A7.6C9E4118--
_______________________________________________
manet mailing list
manet@ietf.org
https://www1.ietf.org/mailman/listinfo/manet


From mailnull@www1.ietf.org  Fri Nov  8 23:34:54 2002
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id XAA01347
	for <manet-archive@odin.ietf.org>; Fri, 8 Nov 2002 23:34:53 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id gA94b2m25426
	for manet-archive@odin.ietf.org; Fri, 8 Nov 2002 23:37:02 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gA94b2v25422
	for <manet-web-archive@optimus.ietf.org>; Fri, 8 Nov 2002 23:37:02 -0500
Received: from www1.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id XAA01336
	for <manet-web-archive@ietf.org>; Fri, 8 Nov 2002 23:34:22 -0500 (EST)
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gA94NNv24787;
	Fri, 8 Nov 2002 23:23:23 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gA94Lev24730
	for <manet@optimus.ietf.org>; Fri, 8 Nov 2002 23:21:40 -0500
Received: from ims21.stu.nus.edu.sg (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id XAA00920
	for <manet@ietf.org>; Fri, 8 Nov 2002 23:18:59 -0500 (EST)
Received: from mbxsrv26.stu.nus.edu.sg ([137.132.14.236]) by ims21.stu.nus.edu.sg with Microsoft SMTPSVC(5.0.2195.4905);
	 Sat, 9 Nov 2002 12:21:25 +0800
X-MimeOLE: Produced By Microsoft Exchange V6.0.6249.0
content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: multipart/alternative;
	boundary="----_=_NextPart_001_01C287A7.6C9E4118"
Date: Sat, 9 Nov 2002 12:21:07 +0800
Message-ID: <6330DC96389A924A804F52FA3848930E703DA8@MBXSRV26.stu.nus.edu.sg>
Thread-Topic: Energy of mobile nodes in MANET simuaion
Thread-Index: AcKHp24FDxqhn/eaSDOD8LB/RZYzTg==
From: "Marwaha Shivanajay" <engp1609@nus.edu.sg>
To: <manet@ietf.org>
X-OriginalArrivalTime: 09 Nov 2002 04:21:25.0319 (UTC) FILETIME=[77743D70:01C287A7]
Subject: [manet] Energy of mobile nodes in MANET simuaion
Sender: manet-admin@ietf.org
Errors-To: manet-admin@ietf.org
X-BeenThere: manet@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/manet>,
	<mailto:manet-request@ietf.org?subject=unsubscribe>
List-Id: Mobile Ad-hoc Networks  <manet.ietf.org>
List-Post: <mailto:manet@ietf.org>
List-Help: <mailto:manet-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/manet>,
	<mailto:manet-request@ietf.org?subject=subscribe>

This is a multi-part message in MIME format.

------_=_NextPart_001_01C287A7.6C9E4118
Content-Type: text/plain;
	charset="US-ASCII"
Content-Transfer-Encoding: quoted-printable

Hi,
I want to know how much should be the initial node energy in joules for
a MANET simulation (in NS-2)??
Also kindly advice how much should is the energy expended for the
transmission and reception of packets by a mobile node.

In case we do not set the initial node energy in MANET simulation, would
the nodes be having infinite energy??

Thanks and best regrads,
Shivanajay=20
National University of S'pore.


------_=_NextPart_001_01C287A7.6C9E4118
Content-Type: text/html;
	charset="US-ASCII"
Content-Transfer-Encoding: quoted-printable

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD><TITLE>Message</TITLE>
<META http-equiv=3DContent-Type content=3D"text/html; =
charset=3Dus-ascii">
<META content=3D"MSHTML 6.00.2800.1106" name=3DGENERATOR></HEAD>
<BODY>
<DIV><FONT face=3DArial size=3D2>Hi,<BR>I want to know how much should =
be the=20
initial node<SPAN class=3D785461504-09112002> </SPAN>energy&nbsp;<SPAN=20
class=3D785461504-09112002>in joules&nbsp;for</SPAN> a MANET =
simulation&nbsp;<SPAN=20
class=3D785461504-09112002>(</SPAN>in NS<SPAN=20
class=3D785461504-09112002>-2</SPAN><SPAN=20
class=3D785461504-09112002>)</SPAN>??<BR><SPAN=20
class=3D785461504-09112002></SPAN>A<SPAN class=3D785461504-09112002>lso =
kindly=20
advice how much should&nbsp;is the energy&nbsp;expended for&nbsp;the=20
transmission and reception of packets by a mobile =
node.</SPAN><BR></FONT></DIV>
<DIV><FONT><FONT face=3DArial size=3D2>In case we do not set the initial =
node energy=20
in<SPAN class=3D785461504-09112002> </SPAN>MANET<SPAN =
class=3D785461504-09112002>=20
simulation</SPAN>, would the nodes be having infinite en<SPAN=20
class=3D785461504-09112002>e</SPAN>rgy??<BR><BR>Thanks and best=20
regrads,<BR>Shivanajay&nbsp;<BR>National University of=20
S'pore.<BR></FONT></DIV></FONT></BODY></HTML>
=00
------_=_NextPart_001_01C287A7.6C9E4118--
_______________________________________________
manet mailing list
manet@ietf.org
https://www1.ietf.org/mailman/listinfo/manet



From manet-admin@ietf.org  Sun Nov 10 22:56:17 2002
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id WAA00497
	for <manet-archive@lists.ietf.org>; Sun, 10 Nov 2002 22:56:17 -0500 (EST)
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gAB3kLv07273;
	Sun, 10 Nov 2002 22:46:22 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gAB3TXv06388
	for <manet@optimus.ietf.org>; Sun, 10 Nov 2002 22:29:33 -0500
Received: from mails.tsinghua.edu.cn (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id WAA29816
	for <manet@ietf.org>; Sun, 10 Nov 2002 22:26:51 -0500 (EST)
Message-Id: <200211110326.WAA29816@ietf.org>
Received: (eyou send program); Mon, 11 Nov 2002 11:26:46 +0800
Received: from unknown (HELO yangwh) (unknown@166.111.67.88)
 by 166.111.8.16 with SMTP; Mon, 11 Nov 2002 11:26:46 +0800
Date: Mon, 11 Nov 2002 11:30:39 +0800
From: "yang weihua" <yangwh00@mails.tsinghua.edu.cn>
To: "manet@ietf.org" <manet@ietf.org>
X-mailer: Foxmail 4.1 [cn]
Mime-Version: 1.0
Content-Type: text/plain;
      charset="GB2312"
Content-Transfer-Encoding: 8bit
X-MIME-Autoconverted: from quoted-printable to 8bit by www1.ietf.org id gAB3TXv06389
Subject: [manet] (no subject)
Sender: manet-admin@ietf.org
Errors-To: manet-admin@ietf.org
X-BeenThere: manet@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/manet>,
	<mailto:manet-request@ietf.org?subject=unsubscribe>
List-Id: Mobile Ad-hoc Networks  <manet.ietf.org>
List-Post: <mailto:manet@ietf.org>
List-Help: <mailto:manet-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/manet>,
	<mailto:manet-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 8bit

hiŁ¬
	I have one question to refer to you. I modified the common header of AODV 
by adding a variable. I did it like this in "aodv_packet.h"
    struct hdr_aodfv {
        ...
        double ah_energy;    // added by myself, what else shoud i do?
        ...
		}
     
    What relevant changes shoud do in order to get it work?
Because I found nowhere to indicate the size change of the header to compiler,
it does not work correctly.
    Thanks in advance.
	

	

Best regards! 				

yang weihua
yangwh00@mails.tsinghua.edu.cn
2002-11-11


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


From mailnull@www1.ietf.org  Sun Nov 10 23:00:58 2002
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id XAA00579
	for <manet-archive@odin.ietf.org>; Sun, 10 Nov 2002 23:00:58 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id gAB438307859
	for manet-archive@odin.ietf.org; Sun, 10 Nov 2002 23:03:08 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gAB438v07856
	for <manet-web-archive@optimus.ietf.org>; Sun, 10 Nov 2002 23:03:08 -0500
Received: from www1.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id XAA00573
	for <manet-web-archive@ietf.org>; Sun, 10 Nov 2002 23:00:27 -0500 (EST)
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gAB3kLv07273;
	Sun, 10 Nov 2002 22:46:22 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gAB3TXv06388
	for <manet@optimus.ietf.org>; Sun, 10 Nov 2002 22:29:33 -0500
Received: from mails.tsinghua.edu.cn (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id WAA29816
	for <manet@ietf.org>; Sun, 10 Nov 2002 22:26:51 -0500 (EST)
Message-Id: <200211110326.WAA29816@ietf.org>
Received: (eyou send program); Mon, 11 Nov 2002 11:26:46 +0800
Received: from unknown (HELO yangwh) (unknown@166.111.67.88)
 by 166.111.8.16 with SMTP; Mon, 11 Nov 2002 11:26:46 +0800
Date: Mon, 11 Nov 2002 11:30:39 +0800
From: "yang weihua" <yangwh00@mails.tsinghua.edu.cn>
To: "manet@ietf.org" <manet@ietf.org>
X-mailer: Foxmail 4.1 [cn]
Mime-Version: 1.0
Content-Type: text/plain;
      charset="GB2312"
Content-Transfer-Encoding: 8bit
X-MIME-Autoconverted: from quoted-printable to 8bit by www1.ietf.org id gAB3TXv06389
Subject: [manet] (no subject)
Sender: manet-admin@ietf.org
Errors-To: manet-admin@ietf.org
X-BeenThere: manet@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/manet>,
	<mailto:manet-request@ietf.org?subject=unsubscribe>
List-Id: Mobile Ad-hoc Networks  <manet.ietf.org>
List-Post: <mailto:manet@ietf.org>
List-Help: <mailto:manet-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/manet>,
	<mailto:manet-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 8bit
Content-Transfer-Encoding: 8bit

hiŁ¬
	I have one question to refer to you. I modified the common header of AODV 
by adding a variable. I did it like this in "aodv_packet.h"
    struct hdr_aodfv {
        ...
        double ah_energy;    // added by myself, what else shoud i do?
        ...
		}
     
    What relevant changes shoud do in order to get it work?
Because I found nowhere to indicate the size change of the header to compiler,
it does not work correctly.
    Thanks in advance.
	

	

Best regards! 				

yang weihua
yangwh00@mails.tsinghua.edu.cn
2002-11-11


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



From mailnull@www1.ietf.org  Mon Nov 11 15:20:25 2002
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA00051
	for <manet-archive@odin.ietf.org>; Mon, 11 Nov 2002 15:20:25 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id gABKMWd00841
	for manet-archive@odin.ietf.org; Mon, 11 Nov 2002 15:22:32 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gABKMWv00838
	for <manet-web-archive@optimus.ietf.org>; Mon, 11 Nov 2002 15:22:32 -0500
Received: from www1.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA00030
	for <manet-web-archive@ietf.org>; Mon, 11 Nov 2002 15:19:54 -0500 (EST)
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gABKEvv00540;
	Mon, 11 Nov 2002 15:14:57 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gABK9uv00336
	for <manet@optimus.ietf.org>; Mon, 11 Nov 2002 15:09:56 -0500
Received: from ms-sm2.uncc.edu (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA29558
	for <manet@ietf.org>; Mon, 11 Nov 2002 15:07:18 -0500 (EST)
Received: from lxs-kenn3.uncc.edu (lxs-kenn3.uncc.edu [152.15.35.13])
	by ms-sm2.uncc.edu (8.10.2+Sun/8.9.0) with ESMTP id gABK9n414476
	for <manet@ietf.org>; Mon, 11 Nov 2002 15:09:50 -0500 (EST)
Content-Type: text/plain;
  charset="us-ascii"
From: Navatha Tirunagarivishwanatham <ntirunag@uncc.edu>
To: manet@ietf.org
Date: Mon, 11 Nov 2002 15:09:48 -0500
User-Agent: KMail/1.4.1
MIME-Version: 1.0
Content-Transfer-Encoding: 8bit
Message-Id: <200211111509.48743.ntirunag@uncc.edu>
Content-Transfer-Encoding: 8bit
Subject: [manet] Security in MANET routing
Sender: manet-admin@ietf.org
Errors-To: manet-admin@ietf.org
X-BeenThere: manet@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/manet>,
	<mailto:manet-request@ietf.org?subject=unsubscribe>
List-Id: Mobile Ad-hoc Networks  <manet.ietf.org>
List-Post: <mailto:manet@ietf.org>
List-Help: <mailto:manet-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/manet>,
	<mailto:manet-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 8bit
Content-Transfer-Encoding: 8bit

I am presently investigating on different methods proposed to enhance
security in MANET routing protocols. Some of these methods are non-disclosure 
method, threshold cryptography , watchdog and pathrater and mulitpath 
routing. My plan is to simulate all these using ns-2 and draw a performance 
related study. But I have not been able to get much information on how to 
proceed with the simulation part. Is anyone working in the same field. If so, 
can u please point me to the relevant documentation or direct me on how to 
proceed about this ?
I would deeply appreciate any help. 


Thanks in advance,
Navatha



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



From manet-admin@ietf.org  Mon Nov 11 15:27:26 2002
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA00238
	for <manet-archive@lists.ietf.org>; Mon, 11 Nov 2002 15:27:26 -0500 (EST)
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gABKEvv00540;
	Mon, 11 Nov 2002 15:14:57 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gABK9uv00336
	for <manet@optimus.ietf.org>; Mon, 11 Nov 2002 15:09:56 -0500
Received: from ms-sm2.uncc.edu (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA29558
	for <manet@ietf.org>; Mon, 11 Nov 2002 15:07:18 -0500 (EST)
Received: from lxs-kenn3.uncc.edu (lxs-kenn3.uncc.edu [152.15.35.13])
	by ms-sm2.uncc.edu (8.10.2+Sun/8.9.0) with ESMTP id gABK9n414476
	for <manet@ietf.org>; Mon, 11 Nov 2002 15:09:50 -0500 (EST)
Content-Type: text/plain;
  charset="us-ascii"
From: Navatha Tirunagarivishwanatham <ntirunag@uncc.edu>
To: manet@ietf.org
Date: Mon, 11 Nov 2002 15:09:48 -0500
User-Agent: KMail/1.4.1
MIME-Version: 1.0
Content-Transfer-Encoding: 8bit
Message-Id: <200211111509.48743.ntirunag@uncc.edu>
Content-Transfer-Encoding: 8bit
Subject: [manet] Security in MANET routing
Sender: manet-admin@ietf.org
Errors-To: manet-admin@ietf.org
X-BeenThere: manet@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/manet>,
	<mailto:manet-request@ietf.org?subject=unsubscribe>
List-Id: Mobile Ad-hoc Networks  <manet.ietf.org>
List-Post: <mailto:manet@ietf.org>
List-Help: <mailto:manet-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/manet>,
	<mailto:manet-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 8bit

I am presently investigating on different methods proposed to enhance
security in MANET routing protocols. Some of these methods are non-disclosure 
method, threshold cryptography , watchdog and pathrater and mulitpath 
routing. My plan is to simulate all these using ns-2 and draw a performance 
related study. But I have not been able to get much information on how to 
proceed with the simulation part. Is anyone working in the same field. If so, 
can u please point me to the relevant documentation or direct me on how to 
proceed about this ?
I would deeply appreciate any help. 


Thanks in advance,
Navatha



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


From mailnull@www1.ietf.org  Mon Nov 11 17:23:02 2002
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA04432
	for <manet-archive@odin.ietf.org>; Mon, 11 Nov 2002 17:23:02 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id gABMPBK09173
	for manet-archive@odin.ietf.org; Mon, 11 Nov 2002 17:25:11 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gABMPBv09170
	for <manet-web-archive@optimus.ietf.org>; Mon, 11 Nov 2002 17:25:11 -0500
Received: from www1.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA04415
	for <manet-web-archive@ietf.org>; Mon, 11 Nov 2002 17:22:31 -0500 (EST)
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gABMHav08831;
	Mon, 11 Nov 2002 17:17:36 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gABMFGv08772
	for <manet@optimus.ietf.org>; Mon, 11 Nov 2002 17:15:16 -0500
Received: from memphis.ece.cornell.edu (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA04094
	for <manet@ietf.org>; Mon, 11 Nov 2002 17:12:36 -0500 (EST)
Received: from Sior_Panagakhs.cornell.edu (dhcp-128-84-210-254-r3a-desktop.ece.cornell.edu [128.84.210.254])
	by memphis.ece.cornell.edu (8.11.6/8.11.2) with ESMTP id gABMF7X24286;
	Mon, 11 Nov 2002 17:15:07 -0500
Message-Id: <5.1.0.14.2.20021111164707.025aac98@memphis.ece.cornell.edu>
X-Sender: papadp@memphis.ece.cornell.edu
X-Mailer: QUALCOMM Windows Eudora Version 5.1
Date: Mon, 11 Nov 2002 17:16:42 -0500
To: Navatha Tirunagarivishwanatham <ntirunag@uncc.edu>, manet@ietf.org
From: Panos Papadimitratos <papadp@ece.cornell.edu>
Subject: Re: [manet] Security in MANET routing
Cc: haas@ece.cornell.edu, papadp@ece.cornell.edu
In-Reply-To: <200211111509.48743.ntirunag@uncc.edu>
Mime-Version: 1.0
Content-Type: multipart/alternative;
	boundary="=====================_22317734==_.ALT"
Sender: manet-admin@ietf.org
Errors-To: manet-admin@ietf.org
X-BeenThere: manet@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/manet>,
	<mailto:manet-request@ietf.org?subject=unsubscribe>
List-Id: Mobile Ad-hoc Networks  <manet.ietf.org>
List-Post: <mailto:manet@ietf.org>
List-Help: <mailto:manet-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/manet>,
	<mailto:manet-request@ietf.org?subject=subscribe>

--=====================_22317734==_.ALT
Content-Type: text/plain; charset="us-ascii"; format=flowed

Hi Navatha,

please see the performance evaluation of our secure routing protocol (SRP) 
for mobile
ad hoc networks. URL: http://wnl.ece.cornell.edu/Publications/wise02.ps

In short, we first evaluate SRP in a range of settings with only benign 
nodes present.
This gives us a benchmark and shows that a protocol with security 
enhancements remains
efficient.

Then, we implement two attacks and evaluate the performance for an increasing
number of attackers. Note that SRP does not rely on detecting the adversaries,
which implies that persistent attacks are most "effective," from the 
attacker's point of view.
SRP operates successfully, even with a very large number of attackers that 
actively
disrupt the route discovery.

Best Regards,

Panos

At 03:09 PM 11/11/2002 -0500, Navatha Tirunagarivishwanatham wrote:
>I am presently investigating on different methods proposed to enhance
>security in MANET routing protocols. Some of these methods are non-disclosure
>method, threshold cryptography , watchdog and pathrater and mulitpath
>routing. My plan is to simulate all these using ns-2 and draw a performance
>related study. But I have not been able to get much information on how to
>proceed with the simulation part. Is anyone working in the same field. If so,
>can u please point me to the relevant documentation or direct me on how to
>proceed about this ?
>I would deeply appreciate any help.
>
>
>Thanks in advance,
>Navatha
>
>
>
>_______________________________________________
>manet mailing list
>manet@ietf.org
>https://www1.ietf.org/mailman/listinfo/manet

----------------------------------------------------------------------------------------------------------
Panagiotis 
Papadimitratos               http://www.people.cornell.edu/pages/pp59
Wireless Networks Laboratory    http://wnl.ece.cornell.edu
School of Electrical 
Engineering
Cornell 
University 

374 Frank Rhodes Hall           Tel: +1-607-255-9068
Ithaca, NY 14853                        Fax: +1-607-255-9072
U.S.A                                   E-mail: papadp@ece.cornell.edu
----------------------------------------------------------------------------------------------------------
--=====================_22317734==_.ALT
Content-Type: text/html; charset="us-ascii"

<html>
Hi Navatha, <br><br>
please see the performance evaluation of our secure routing protocol
(SRP) for mobile <br>
ad hoc networks. URL:
<a href="http://wnl.ece.cornell.edu/Publications/wise02.ps" eudora="autourl">http://wnl.ece.cornell.edu/Publications/wise02.</a><a href="http://wnl.ece.cornell.edu/Publications/wise02.ps" eudora="autourl">ps<br><br>
</a>In short, we first evaluate SRP in a range of settings with only
benign nodes present.<br>
This gives us a benchmark and shows that a protocol with security
enhancements remains <br>
efficient. <br><br>
Then, we implement two attacks and evaluate the performance for an
increasing <br>
number of attackers. Note that SRP does not rely on detecting the
adversaries, <br>
which implies that persistent attacks are most &quot;effective,&quot;
from the attacker's point of view.<br>
SRP operates successfully, even with a very large number of attackers
that actively <br>
disrupt the route discovery. <br><br>
Best Regards, <br><br>
Panos<br><br>
At 03:09 PM 11/11/2002 -0500, Navatha Tirunagarivishwanatham wrote:<br>
<blockquote type=cite class=cite cite>I am presently investigating on
different methods proposed to enhance<br>
security in MANET routing protocols. Some of these methods are
non-disclosure <br>
method, threshold cryptography , watchdog and pathrater and mulitpath
<br>
routing. My plan is to simulate all these using ns-2 and draw a
performance <br>
related study. But I have not been able to get much information on how to
<br>
proceed with the simulation part. Is anyone working in the same field. If
so, <br>
can u please point me to the relevant documentation or direct me on how
to <br>
proceed about this ?<br>
I would deeply appreciate any help. <br><br>
<br>
Thanks in advance,<br>
Navatha<br><br>
<br><br>
_______________________________________________<br>
manet mailing list<br>
manet@ietf.org<br>
<a href="https://www1.ietf.org/mailman/listinfo/manet" eudora="autourl">https://www1.ietf.org/mailman/listinfo/manet</a>
</blockquote>
<x-sigsep><p></x-sigsep>
<font face="Times New Roman CE, Times">----------------------------------------------------------------------------------------------------------<br>
Panagiotis Papadimitratos<x-tab>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;</x-tab><x-tab>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;</x-tab><a href="http://www.people.cornell.edu/pages/pp59" eudora="autourl">http://www.people.cornell.edu/pages/pp59</a> <br>
Wireless Networks Laboratory<x-tab>&nbsp;&nbsp;&nbsp;&nbsp;</x-tab><a href="http://wnl.ece.cornell.edu/" eudora="autourl">http://wnl.ece.cornell.edu</a><br>
School of Electrical Engineering&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; <br>
Cornell University&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; <br>
374 Frank Rhodes Hall<x-tab>&nbsp;&nbsp;&nbsp;</x-tab><x-tab>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;</x-tab>Tel: +1-607-255-9068<x-tab>&nbsp;&nbsp;&nbsp;&nbsp;</x-tab><br>
Ithaca, NY 14853<x-tab>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;</x-tab><x-tab>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;</x-tab><x-tab>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;</x-tab>Fax: +1-607-255-9072<br>
U.S.A<x-tab>&nbsp;&nbsp;&nbsp;</x-tab><x-tab>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;</x-tab><x-tab>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;</x-tab><x-tab>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;</x-tab><x-tab>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;</x-tab>E-mail: papadp@ece.cornell.edu<br>
----------------------------------------------------------------------------------------------------------</font></html>

--=====================_22317734==_.ALT--

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



From manet-admin@ietf.org  Mon Nov 11 17:23:35 2002
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA04453
	for <manet-archive@lists.ietf.org>; Mon, 11 Nov 2002 17:23:35 -0500 (EST)
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gABMHav08831;
	Mon, 11 Nov 2002 17:17:36 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gABMFGv08772
	for <manet@optimus.ietf.org>; Mon, 11 Nov 2002 17:15:16 -0500
Received: from memphis.ece.cornell.edu (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA04094
	for <manet@ietf.org>; Mon, 11 Nov 2002 17:12:36 -0500 (EST)
Received: from Sior_Panagakhs.cornell.edu (dhcp-128-84-210-254-r3a-desktop.ece.cornell.edu [128.84.210.254])
	by memphis.ece.cornell.edu (8.11.6/8.11.2) with ESMTP id gABMF7X24286;
	Mon, 11 Nov 2002 17:15:07 -0500
Message-Id: <5.1.0.14.2.20021111164707.025aac98@memphis.ece.cornell.edu>
X-Sender: papadp@memphis.ece.cornell.edu
X-Mailer: QUALCOMM Windows Eudora Version 5.1
Date: Mon, 11 Nov 2002 17:16:42 -0500
To: Navatha Tirunagarivishwanatham <ntirunag@uncc.edu>, manet@ietf.org
From: Panos Papadimitratos <papadp@ece.cornell.edu>
Subject: Re: [manet] Security in MANET routing
Cc: haas@ece.cornell.edu, papadp@ece.cornell.edu
In-Reply-To: <200211111509.48743.ntirunag@uncc.edu>
Mime-Version: 1.0
Content-Type: multipart/alternative;
	boundary="=====================_22317734==_.ALT"
Sender: manet-admin@ietf.org
Errors-To: manet-admin@ietf.org
X-BeenThere: manet@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/manet>,
	<mailto:manet-request@ietf.org?subject=unsubscribe>
List-Id: Mobile Ad-hoc Networks  <manet.ietf.org>
List-Post: <mailto:manet@ietf.org>
List-Help: <mailto:manet-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/manet>,
	<mailto:manet-request@ietf.org?subject=subscribe>

--=====================_22317734==_.ALT
Content-Type: text/plain; charset="us-ascii"; format=flowed

Hi Navatha,

please see the performance evaluation of our secure routing protocol (SRP) 
for mobile
ad hoc networks. URL: http://wnl.ece.cornell.edu/Publications/wise02.ps

In short, we first evaluate SRP in a range of settings with only benign 
nodes present.
This gives us a benchmark and shows that a protocol with security 
enhancements remains
efficient.

Then, we implement two attacks and evaluate the performance for an increasing
number of attackers. Note that SRP does not rely on detecting the adversaries,
which implies that persistent attacks are most "effective," from the 
attacker's point of view.
SRP operates successfully, even with a very large number of attackers that 
actively
disrupt the route discovery.

Best Regards,

Panos

At 03:09 PM 11/11/2002 -0500, Navatha Tirunagarivishwanatham wrote:
>I am presently investigating on different methods proposed to enhance
>security in MANET routing protocols. Some of these methods are non-disclosure
>method, threshold cryptography , watchdog and pathrater and mulitpath
>routing. My plan is to simulate all these using ns-2 and draw a performance
>related study. But I have not been able to get much information on how to
>proceed with the simulation part. Is anyone working in the same field. If so,
>can u please point me to the relevant documentation or direct me on how to
>proceed about this ?
>I would deeply appreciate any help.
>
>
>Thanks in advance,
>Navatha
>
>
>
>_______________________________________________
>manet mailing list
>manet@ietf.org
>https://www1.ietf.org/mailman/listinfo/manet

----------------------------------------------------------------------------------------------------------
Panagiotis 
Papadimitratos               http://www.people.cornell.edu/pages/pp59
Wireless Networks Laboratory    http://wnl.ece.cornell.edu
School of Electrical 
Engineering
Cornell 
University 

374 Frank Rhodes Hall           Tel: +1-607-255-9068
Ithaca, NY 14853                        Fax: +1-607-255-9072
U.S.A                                   E-mail: papadp@ece.cornell.edu
----------------------------------------------------------------------------------------------------------
--=====================_22317734==_.ALT
Content-Type: text/html; charset="us-ascii"

<html>
Hi Navatha, <br><br>
please see the performance evaluation of our secure routing protocol
(SRP) for mobile <br>
ad hoc networks. URL:
<a href="http://wnl.ece.cornell.edu/Publications/wise02.ps" eudora="autourl">http://wnl.ece.cornell.edu/Publications/wise02.</a><a href="http://wnl.ece.cornell.edu/Publications/wise02.ps" eudora="autourl">ps<br><br>
</a>In short, we first evaluate SRP in a range of settings with only
benign nodes present.<br>
This gives us a benchmark and shows that a protocol with security
enhancements remains <br>
efficient. <br><br>
Then, we implement two attacks and evaluate the performance for an
increasing <br>
number of attackers. Note that SRP does not rely on detecting the
adversaries, <br>
which implies that persistent attacks are most &quot;effective,&quot;
from the attacker's point of view.<br>
SRP operates successfully, even with a very large number of attackers
that actively <br>
disrupt the route discovery. <br><br>
Best Regards, <br><br>
Panos<br><br>
At 03:09 PM 11/11/2002 -0500, Navatha Tirunagarivishwanatham wrote:<br>
<blockquote type=cite class=cite cite>I am presently investigating on
different methods proposed to enhance<br>
security in MANET routing protocols. Some of these methods are
non-disclosure <br>
method, threshold cryptography , watchdog and pathrater and mulitpath
<br>
routing. My plan is to simulate all these using ns-2 and draw a
performance <br>
related study. But I have not been able to get much information on how to
<br>
proceed with the simulation part. Is anyone working in the same field. If
so, <br>
can u please point me to the relevant documentation or direct me on how
to <br>
proceed about this ?<br>
I would deeply appreciate any help. <br><br>
<br>
Thanks in advance,<br>
Navatha<br><br>
<br><br>
_______________________________________________<br>
manet mailing list<br>
manet@ietf.org<br>
<a href="https://www1.ietf.org/mailman/listinfo/manet" eudora="autourl">https://www1.ietf.org/mailman/listinfo/manet</a>
</blockquote>
<x-sigsep><p></x-sigsep>
<font face="Times New Roman CE, Times">----------------------------------------------------------------------------------------------------------<br>
Panagiotis Papadimitratos<x-tab>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;</x-tab><x-tab>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;</x-tab><a href="http://www.people.cornell.edu/pages/pp59" eudora="autourl">http://www.people.cornell.edu/pages/pp59</a> <br>
Wireless Networks Laboratory<x-tab>&nbsp;&nbsp;&nbsp;&nbsp;</x-tab><a href="http://wnl.ece.cornell.edu/" eudora="autourl">http://wnl.ece.cornell.edu</a><br>
School of Electrical Engineering&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; <br>
Cornell University&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; <br>
374 Frank Rhodes Hall<x-tab>&nbsp;&nbsp;&nbsp;</x-tab><x-tab>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;</x-tab>Tel: +1-607-255-9068<x-tab>&nbsp;&nbsp;&nbsp;&nbsp;</x-tab><br>
Ithaca, NY 14853<x-tab>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;</x-tab><x-tab>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;</x-tab><x-tab>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;</x-tab>Fax: +1-607-255-9072<br>
U.S.A<x-tab>&nbsp;&nbsp;&nbsp;</x-tab><x-tab>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;</x-tab><x-tab>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;</x-tab><x-tab>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;</x-tab><x-tab>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;</x-tab>E-mail: papadp@ece.cornell.edu<br>
----------------------------------------------------------------------------------------------------------</font></html>

--=====================_22317734==_.ALT--

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


From mailnull@www1.ietf.org  Mon Nov 11 21:37:13 2002
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id VAA09349
	for <manet-archive@odin.ietf.org>; Mon, 11 Nov 2002 21:37:13 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id gAC2dOk21965
	for manet-archive@odin.ietf.org; Mon, 11 Nov 2002 21:39:24 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gAC2dOv21962
	for <manet-web-archive@optimus.ietf.org>; Mon, 11 Nov 2002 21:39:24 -0500
Received: from www1.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id VAA09338
	for <manet-web-archive@ietf.org>; Mon, 11 Nov 2002 21:36:42 -0500 (EST)
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gAC2VBv21077;
	Mon, 11 Nov 2002 21:31:11 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gAC2UXv21033
	for <manet@optimus.ietf.org>; Mon, 11 Nov 2002 21:30:33 -0500
Received: from web14402.mail.yahoo.com (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id VAA08921
	for <manet@ietf.org>; Mon, 11 Nov 2002 21:27:52 -0500 (EST)
Message-ID: <20021112023024.64079.qmail@web14402.mail.yahoo.com>
Received: from [155.69.5.222] by web14402.mail.yahoo.com via HTTP; Mon, 11 Nov 2002 18:30:24 PST
Date: Mon, 11 Nov 2002 18:30:24 -0800 (PST)
From: lijuan zhu <ljzhu80@yahoo.com>
To: manet@ietf.org
Cc: yangwh00@mails.tsinghua.edu.cn
In-Reply-To: <20021111170003.22287.78829.Mailman@www1.ietf.org>
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="0-1942103720-1037068224=:63763"
Subject: [manet] Re: manet digest, Vol 1 #252 - 1 msg
Sender: manet-admin@ietf.org
Errors-To: manet-admin@ietf.org
X-BeenThere: manet@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/manet>,
	<mailto:manet-request@ietf.org?subject=unsubscribe>
List-Id: Mobile Ad-hoc Networks  <manet.ietf.org>
List-Post: <mailto:manet@ietf.org>
List-Help: <mailto:manet-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/manet>,
	<mailto:manet-request@ietf.org?subject=subscribe>

--0-1942103720-1037068224=:63763
Content-Type: text/plain; charset=us-ascii


hihi 
in aodv.h, AODV_HDR_LEN indicate the length of the header to the compiler and used in aodv.cc, but this size is much bigger than the acutall size needed, so u need not change it
what u need to change is to add the same line to the similar place of hdr_aodv_request, hdr_aodv_reply, because they share the same structure (hdr_aodv is the common section of all the header)

hope this can help u

Rgds

Dr. Lijuan Zhu

 manet-request@ietf.org wrote: 
Send manet mailing list submissions to
manet@ietf.org

To subscribe or unsubscribe via the World Wide Web, visit
https://www1.ietf.org/mailman/listinfo/manet
or, via email, send a message with subject or body 'help' to
manet-request@ietf.org

You can reach the person managing the list at
manet-admin@ietf.org

When replying, please edit your Subject line so it is more specific
than "Re: Contents of manet digest..."


Today's Topics:

1. (no subject) (yang weihua)

--__--__--

Message: 1
Date: Mon, 11 Nov 2002 11:30:39 +0800
From: "yang weihua" 
To: "manet@ietf.org" 
Subject: [manet] (no subject)

hiŁ¬
I have one question to refer to you. I modified the common header of AODV 
by adding a variable. I did it like this in "aodv_packet.h"
struct hdr_aodfv {
...
double ah_energy; // added by myself, what else shoud i do?
...
}

What relevant changes shoud do in order to get it work?
Because I found nowhere to indicate the size change of the header to 

compiler,
it does not work correctly.
Thanks in advance.




Best regards! 

yang weihua
yangwh00@mails.tsinghua.edu.cn
2002-11-11




--__--__--

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


End of manet Digest



---------------------------------
Do you Yahoo!?
U2 on LAUNCH - Exclusive medley & videos from Greatest Hits CD
--0-1942103720-1037068224=:63763
Content-Type: text/html; charset=us-ascii

<P>hihi&nbsp;
<P>in aodv.h, AODV_HDR_LEN indicate the length of the header to the compiler and used in aodv.cc, but this size is much bigger than the acutall size needed, so u need not change it
<P>what u need to change is to add the same line to the similar place of hdr_aodv_request, hdr_aodv_reply, because they share the same structure (hdr_aodv is the common section of all the header)</P>
<P>hope this can help u</P>
<P>Rgds</P>
<P>Dr. Lijuan Zhu</P>
<P>&nbsp;<B><I>manet-request@ietf.org</I></B> wrote: 
<BLOCKQUOTE style="PADDING-LEFT: 5px; MARGIN-LEFT: 5px; BORDER-LEFT: #1010ff 2px solid">
<P>Send manet mailing list submissions to<BR>manet@ietf.org<BR><BR>To subscribe or unsubscribe via the World Wide Web, visit<BR>https://www1.ietf.org/mailman/listinfo/manet<BR>or, via email, send a message with subject or body 'help' to<BR>manet-request@ietf.org<BR><BR>You can reach the person managing the list at<BR>manet-admin@ietf.org<BR><BR>When replying, please edit your Subject line so it is more specific<BR>than "Re: Contents of manet digest..."<BR><BR><BR>Today's Topics:<BR><BR>1. (no subject) (yang weihua)<BR><BR>--__--__--<BR><BR>Message: 1<BR>Date: Mon, 11 Nov 2002 11:30:39 +0800<BR>From: "yang weihua" <YANGWH00@MAILS.TSINGHUA.EDU.CN><BR>To: "manet@ietf.org" <MANET@IETF.ORG><BR>Subject: [manet] (no subject)<BR><BR>hiŁ¬<BR>I have one question to refer to you. I modified the common header of AODV <BR>by adding a variable. I did it like this in "aodv_packet.h"<BR>struct hdr_aodfv {<BR>...<BR>double ah_energy; // added by myself, what else shoud i do?<BR>...<BR>}<BR><!
 BR>What relevant changes shoud do in order to get it work?<BR>Because I found nowhere to indicate the size change of the header to </P>
<P>compiler,<BR>it does not work correctly.<BR>Thanks in advance.<BR><BR><BR><BR><BR>Best regards! <BR><BR>yang weihua<BR>yangwh00@mails.tsinghua.edu.cn<BR>2002-11-11<BR><BR><BR><BR><BR>--__--__--<BR><BR>_______________________________________________<BR>manet mailing list<BR>manet@ietf.org<BR>https://www1.ietf.org/mailman/listinfo/manet<BR><BR><BR>End of manet Digest</P></BLOCKQUOTE><p><br><hr size=1>Do you Yahoo!?<br>
<a href="http://rd.yahoo.com/launch/mailsig/*http://launch.yahoo.com/u2">U2 on LAUNCH</a> - Exclusive medley & videos from Greatest Hits CD
--0-1942103720-1037068224=:63763--
_______________________________________________
manet mailing list
manet@ietf.org
https://www1.ietf.org/mailman/listinfo/manet



From manet-admin@ietf.org  Mon Nov 11 21:37:42 2002
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id VAA09362
	for <manet-archive@lists.ietf.org>; Mon, 11 Nov 2002 21:37:42 -0500 (EST)
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gAC2VBv21077;
	Mon, 11 Nov 2002 21:31:11 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gAC2UXv21033
	for <manet@optimus.ietf.org>; Mon, 11 Nov 2002 21:30:33 -0500
Received: from web14402.mail.yahoo.com (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id VAA08921
	for <manet@ietf.org>; Mon, 11 Nov 2002 21:27:52 -0500 (EST)
Message-ID: <20021112023024.64079.qmail@web14402.mail.yahoo.com>
Received: from [155.69.5.222] by web14402.mail.yahoo.com via HTTP; Mon, 11 Nov 2002 18:30:24 PST
Date: Mon, 11 Nov 2002 18:30:24 -0800 (PST)
From: lijuan zhu <ljzhu80@yahoo.com>
To: manet@ietf.org
Cc: yangwh00@mails.tsinghua.edu.cn
In-Reply-To: <20021111170003.22287.78829.Mailman@www1.ietf.org>
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="0-1942103720-1037068224=:63763"
Subject: [manet] Re: manet digest, Vol 1 #252 - 1 msg
Sender: manet-admin@ietf.org
Errors-To: manet-admin@ietf.org
X-BeenThere: manet@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/manet>,
	<mailto:manet-request@ietf.org?subject=unsubscribe>
List-Id: Mobile Ad-hoc Networks  <manet.ietf.org>
List-Post: <mailto:manet@ietf.org>
List-Help: <mailto:manet-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/manet>,
	<mailto:manet-request@ietf.org?subject=subscribe>

--0-1942103720-1037068224=:63763
Content-Type: text/plain; charset=us-ascii


hihi 
in aodv.h, AODV_HDR_LEN indicate the length of the header to the compiler and used in aodv.cc, but this size is much bigger than the acutall size needed, so u need not change it
what u need to change is to add the same line to the similar place of hdr_aodv_request, hdr_aodv_reply, because they share the same structure (hdr_aodv is the common section of all the header)

hope this can help u

Rgds

Dr. Lijuan Zhu

 manet-request@ietf.org wrote: 
Send manet mailing list submissions to
manet@ietf.org

To subscribe or unsubscribe via the World Wide Web, visit
https://www1.ietf.org/mailman/listinfo/manet
or, via email, send a message with subject or body 'help' to
manet-request@ietf.org

You can reach the person managing the list at
manet-admin@ietf.org

When replying, please edit your Subject line so it is more specific
than "Re: Contents of manet digest..."


Today's Topics:

1. (no subject) (yang weihua)

--__--__--

Message: 1
Date: Mon, 11 Nov 2002 11:30:39 +0800
From: "yang weihua" 
To: "manet@ietf.org" 
Subject: [manet] (no subject)

hiŁ¬
I have one question to refer to you. I modified the common header of AODV 
by adding a variable. I did it like this in "aodv_packet.h"
struct hdr_aodfv {
...
double ah_energy; // added by myself, what else shoud i do?
...
}

What relevant changes shoud do in order to get it work?
Because I found nowhere to indicate the size change of the header to 

compiler,
it does not work correctly.
Thanks in advance.




Best regards! 

yang weihua
yangwh00@mails.tsinghua.edu.cn
2002-11-11




--__--__--

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


End of manet Digest



---------------------------------
Do you Yahoo!?
U2 on LAUNCH - Exclusive medley & videos from Greatest Hits CD
--0-1942103720-1037068224=:63763
Content-Type: text/html; charset=us-ascii

<P>hihi&nbsp;
<P>in aodv.h, AODV_HDR_LEN indicate the length of the header to the compiler and used in aodv.cc, but this size is much bigger than the acutall size needed, so u need not change it
<P>what u need to change is to add the same line to the similar place of hdr_aodv_request, hdr_aodv_reply, because they share the same structure (hdr_aodv is the common section of all the header)</P>
<P>hope this can help u</P>
<P>Rgds</P>
<P>Dr. Lijuan Zhu</P>
<P>&nbsp;<B><I>manet-request@ietf.org</I></B> wrote: 
<BLOCKQUOTE style="PADDING-LEFT: 5px; MARGIN-LEFT: 5px; BORDER-LEFT: #1010ff 2px solid">
<P>Send manet mailing list submissions to<BR>manet@ietf.org<BR><BR>To subscribe or unsubscribe via the World Wide Web, visit<BR>https://www1.ietf.org/mailman/listinfo/manet<BR>or, via email, send a message with subject or body 'help' to<BR>manet-request@ietf.org<BR><BR>You can reach the person managing the list at<BR>manet-admin@ietf.org<BR><BR>When replying, please edit your Subject line so it is more specific<BR>than "Re: Contents of manet digest..."<BR><BR><BR>Today's Topics:<BR><BR>1. (no subject) (yang weihua)<BR><BR>--__--__--<BR><BR>Message: 1<BR>Date: Mon, 11 Nov 2002 11:30:39 +0800<BR>From: "yang weihua" <YANGWH00@MAILS.TSINGHUA.EDU.CN><BR>To: "manet@ietf.org" <MANET@IETF.ORG><BR>Subject: [manet] (no subject)<BR><BR>hiŁ¬<BR>I have one question to refer to you. I modified the common header of AODV <BR>by adding a variable. I did it like this in "aodv_packet.h"<BR>struct hdr_aodfv {<BR>...<BR>double ah_energy; // added by myself, what else shoud i do?<BR>...<BR>}<BR><!
 BR>What relevant changes shoud do in order to get it work?<BR>Because I found nowhere to indicate the size change of the header to </P>
<P>compiler,<BR>it does not work correctly.<BR>Thanks in advance.<BR><BR><BR><BR><BR>Best regards! <BR><BR>yang weihua<BR>yangwh00@mails.tsinghua.edu.cn<BR>2002-11-11<BR><BR><BR><BR><BR>--__--__--<BR><BR>_______________________________________________<BR>manet mailing list<BR>manet@ietf.org<BR>https://www1.ietf.org/mailman/listinfo/manet<BR><BR><BR>End of manet Digest</P></BLOCKQUOTE><p><br><hr size=1>Do you Yahoo!?<br>
<a href="http://rd.yahoo.com/launch/mailsig/*http://launch.yahoo.com/u2">U2 on LAUNCH</a> - Exclusive medley & videos from Greatest Hits CD
--0-1942103720-1037068224=:63763--
_______________________________________________
manet mailing list
manet@ietf.org
https://www1.ietf.org/mailman/listinfo/manet


From manet-admin@ietf.org  Mon Nov 11 21:38:46 2002
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id VAA09390
	for <manet-archive@lists.ietf.org>; Mon, 11 Nov 2002 21:38:46 -0500 (EST)
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gAC2SVv20910;
	Mon, 11 Nov 2002 21:28:31 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gAC2QUv20863
	for <manet@optimus.ietf.org>; Mon, 11 Nov 2002 21:26:30 -0500
Received: from bjapp9.163.net (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id VAA08820
	for <manet@ietf.org>; Mon, 11 Nov 2002 21:23:47 -0500 (EST)
Received: from localhost (localhost [127.0.0.1])
	by bjapp9.163.net (Postfix) with SMTP id A99921CB4C8F3
	for <manet@ietf.org>; Tue, 12 Nov 2002 10:26:14 +0800 (CST)
Received: from befine (unknown [211.71.13.13])
	by bjapp9.163.net (Coremail) with SMTP id SAEAAMZm0D0cMw0N.1
	for <manet@ietf.org>; Tue, 12 Nov 2002 10:26:14 +0800 (CST)
Date: Tue, 12 Nov 2002 10:24:26 +0800
From: "Harry" <hr_befine@163.net>
Reply-To: hr_befine@163.net
To: MANET mail list <manet@ietf.org>
X-mailer: Foxmail 4.1 [cn]
Mime-Version: 1.0
Content-Type: text/plain;
      charset="GB2312"
Message-Id: <20021112022614.A99921CB4C8F3@bjapp9.163.net>
Content-Transfer-Encoding: 8bit
X-MIME-Autoconverted: from quoted-printable to 8bit by www1.ietf.org id gAC2QUv20864
Subject: [manet] Any more Qos Models?
Sender: manet-admin@ietf.org
Errors-To: manet-admin@ietf.org
X-BeenThere: manet@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/manet>,
	<mailto:manet-request@ietf.org?subject=unsubscribe>
List-Id: Mobile Ad-hoc Networks  <manet.ietf.org>
List-Post: <mailto:manet@ietf.org>
List-Help: <mailto:manet-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/manet>,
	<mailto:manet-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 8bit

Hi,all:
	Besides FQMM, are there other Qos model proposed  till now?

Best Regards 				

ˇˇˇˇˇˇˇˇˇˇˇˇˇˇˇˇHarry
ˇˇˇˇˇˇˇˇˇˇˇˇˇˇˇˇhr_befine@163.net
ˇˇˇˇˇˇˇˇˇˇˇˇˇˇˇˇˇˇˇˇ2002-11-12


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


From mailnull@www1.ietf.org  Mon Nov 11 21:47:06 2002
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id VAA09561
	for <manet-archive@odin.ietf.org>; Mon, 11 Nov 2002 21:47:05 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id gAC2nGS22381
	for manet-archive@odin.ietf.org; Mon, 11 Nov 2002 21:49:16 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gAC2nFv22378
	for <manet-web-archive@optimus.ietf.org>; Mon, 11 Nov 2002 21:49:15 -0500
Received: from www1.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id VAA09550
	for <manet-web-archive@ietf.org>; Mon, 11 Nov 2002 21:46:33 -0500 (EST)
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gAC2SVv20910;
	Mon, 11 Nov 2002 21:28:31 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gAC2QUv20863
	for <manet@optimus.ietf.org>; Mon, 11 Nov 2002 21:26:30 -0500
Received: from bjapp9.163.net (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id VAA08820
	for <manet@ietf.org>; Mon, 11 Nov 2002 21:23:47 -0500 (EST)
Received: from localhost (localhost [127.0.0.1])
	by bjapp9.163.net (Postfix) with SMTP id A99921CB4C8F3
	for <manet@ietf.org>; Tue, 12 Nov 2002 10:26:14 +0800 (CST)
Received: from befine (unknown [211.71.13.13])
	by bjapp9.163.net (Coremail) with SMTP id SAEAAMZm0D0cMw0N.1
	for <manet@ietf.org>; Tue, 12 Nov 2002 10:26:14 +0800 (CST)
Date: Tue, 12 Nov 2002 10:24:26 +0800
From: "Harry" <hr_befine@163.net>
Reply-To: hr_befine@163.net
To: MANET mail list <manet@ietf.org>
X-mailer: Foxmail 4.1 [cn]
Mime-Version: 1.0
Content-Type: text/plain;
      charset="GB2312"
Message-Id: <20021112022614.A99921CB4C8F3@bjapp9.163.net>
Content-Transfer-Encoding: 8bit
X-MIME-Autoconverted: from quoted-printable to 8bit by www1.ietf.org id gAC2QUv20864
Subject: [manet] Any more Qos Models?
Sender: manet-admin@ietf.org
Errors-To: manet-admin@ietf.org
X-BeenThere: manet@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/manet>,
	<mailto:manet-request@ietf.org?subject=unsubscribe>
List-Id: Mobile Ad-hoc Networks  <manet.ietf.org>
List-Post: <mailto:manet@ietf.org>
List-Help: <mailto:manet-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/manet>,
	<mailto:manet-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 8bit
Content-Transfer-Encoding: 8bit

Hi,all:
	Besides FQMM, are there other Qos model proposed  till now?

Best Regards 				

ˇˇˇˇˇˇˇˇˇˇˇˇˇˇˇˇHarry
ˇˇˇˇˇˇˇˇˇˇˇˇˇˇˇˇhr_befine@163.net
ˇˇˇˇˇˇˇˇˇˇˇˇˇˇˇˇˇˇˇˇ2002-11-12


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



From mailnull@www1.ietf.org  Tue Nov 12 04:09:54 2002
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id EAA25640
	for <manet-archive@odin.ietf.org>; Tue, 12 Nov 2002 04:09:54 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id gAC9C8g18849
	for manet-archive@odin.ietf.org; Tue, 12 Nov 2002 04:12:08 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gAC9C8v18846
	for <manet-web-archive@optimus.ietf.org>; Tue, 12 Nov 2002 04:12:08 -0500
Received: from www1.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id EAA25627
	for <manet-web-archive@ietf.org>; Tue, 12 Nov 2002 04:09:23 -0500 (EST)
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gAC8xxv17401;
	Tue, 12 Nov 2002 03:59:59 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gAC8nQv17091
	for <manet@optimus.ietf.org>; Tue, 12 Nov 2002 03:49:26 -0500
Received: from hotmail.com (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id DAA25268
	for <manet@ietf.org>; Tue, 12 Nov 2002 03:46:41 -0500 (EST)
Received: from mail pickup service by hotmail.com with Microsoft SMTPSVC;
	 Tue, 12 Nov 2002 00:49:13 -0800
Received: from 218.22.21.2 by lw9fd.law9.hotmail.msn.com with HTTP;
	Tue, 12 Nov 2002 08:49:13 GMT
X-Originating-IP: [218.22.21.2]
From: =?gb2312?B?zuIg0ce35Q==?= <wyfmanet@hotmail.com>
To: manet@ietf.org
Date: Tue, 12 Nov 2002 08:49:13 +0000
Mime-Version: 1.0
Content-Type: text/plain; charset=gb2312; format=flowed
Message-ID: <F162uLn5U9T3TGJ2TUS0000003c@hotmail.com>
X-OriginalArrivalTime: 12 Nov 2002 08:49:13.0825 (UTC) FILETIME=[6044ED10:01C28A28]
Subject: [manet] economic models and game theory
Sender: manet-admin@ietf.org
Errors-To: manet-admin@ietf.org
X-BeenThere: manet@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/manet>,
	<mailto:manet-request@ietf.org?subject=unsubscribe>
List-Id: Mobile Ad-hoc Networks  <manet.ietf.org>
List-Post: <mailto:manet@ietf.org>
List-Help: <mailto:manet-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/manet>,
	<mailto:manet-request@ietf.org?subject=subscribe>

Hi All,

I am presently investigating on economic models for manet and game theory 
in manet.Is anyone working in the same field. If so, can u recommend some 
related paper to me or direct me on how to proceed about this.

Thanks, 

Wu yafeng

Univerity of Science and Technology of China
Department of Computer Science






_________________________________________________________________
ÓëÁŞ»úµÄĹóÓŃ˝řĐĐ˝»Á÷Ł¬ÇëĘąÓĂ MSN Messenger: http://messenger.msn.com/lccn/ 

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



From manet-admin@ietf.org  Tue Nov 12 04:10:50 2002
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id EAA25680
	for <manet-archive@lists.ietf.org>; Tue, 12 Nov 2002 04:10:50 -0500 (EST)
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gAC8xxv17401;
	Tue, 12 Nov 2002 03:59:59 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gAC8nQv17091
	for <manet@optimus.ietf.org>; Tue, 12 Nov 2002 03:49:26 -0500
Received: from hotmail.com (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id DAA25268
	for <manet@ietf.org>; Tue, 12 Nov 2002 03:46:41 -0500 (EST)
Received: from mail pickup service by hotmail.com with Microsoft SMTPSVC;
	 Tue, 12 Nov 2002 00:49:13 -0800
Received: from 218.22.21.2 by lw9fd.law9.hotmail.msn.com with HTTP;
	Tue, 12 Nov 2002 08:49:13 GMT
X-Originating-IP: [218.22.21.2]
From: =?gb2312?B?zuIg0ce35Q==?= <wyfmanet@hotmail.com>
To: manet@ietf.org
Date: Tue, 12 Nov 2002 08:49:13 +0000
Mime-Version: 1.0
Content-Type: text/plain; charset=gb2312; format=flowed
Message-ID: <F162uLn5U9T3TGJ2TUS0000003c@hotmail.com>
X-OriginalArrivalTime: 12 Nov 2002 08:49:13.0825 (UTC) FILETIME=[6044ED10:01C28A28]
Subject: [manet] economic models and game theory
Sender: manet-admin@ietf.org
Errors-To: manet-admin@ietf.org
X-BeenThere: manet@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/manet>,
	<mailto:manet-request@ietf.org?subject=unsubscribe>
List-Id: Mobile Ad-hoc Networks  <manet.ietf.org>
List-Post: <mailto:manet@ietf.org>
List-Help: <mailto:manet-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/manet>,
	<mailto:manet-request@ietf.org?subject=subscribe>

Hi All,

I am presently investigating on economic models for manet and game theory 
in manet.Is anyone working in the same field. If so, can u recommend some 
related paper to me or direct me on how to proceed about this.

Thanks, 

Wu yafeng

Univerity of Science and Technology of China
Department of Computer Science






_________________________________________________________________
ÓëÁŞ»úµÄĹóÓŃ˝řĐĐ˝»Á÷Ł¬ÇëĘąÓĂ MSN Messenger: http://messenger.msn.com/lccn/ 

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


From manet-admin@ietf.org  Tue Nov 12 06:25:41 2002
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id GAA27380
	for <manet-archive@lists.ietf.org>; Tue, 12 Nov 2002 06:25:41 -0500 (EST)
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gACBK5v25002;
	Tue, 12 Nov 2002 06:20:05 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gACBAfv24758
	for <manet@optimus.ietf.org>; Tue, 12 Nov 2002 06:10:41 -0500
Received: from mailhub.unibe.ch (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id GAA27148
	for <manet@ietf.org>; Tue, 12 Nov 2002 06:08:06 -0500 (EST)
Received: from CONVERSION-DAEMON.mailhub.unibe.ch by mailhub.unibe.ch
 (PMDF V6.1 #40086) id <0H5G00A01N1P5Z@mailhub.unibe.ch> for manet@ietf.org;
 Tue, 12 Nov 2002 12:10:39 +0100 (MET)
Received: from iam.unibe.ch (asterix.unibe.ch [130.92.64.4])
 by mailhub.unibe.ch (PMDF V6.1 #40086)
 with ESMTP id <0H5G00MHSN1PKF@mailhub.unibe.ch> for manet@ietf.org; Tue,
 12 Nov 2002 12:10:37 +0100 (MET)
Received: from iam.unibe.ch (kirok [130.92.65.230])
	by iam.unibe.ch (8.11.6+Sun/8.11.6) with ESMTP id gACBAac28305	for
 <manet@ietf.org>; Tue, 12 Nov 2002 12:10:36 +0100 (MET)
Date: Tue, 12 Nov 2002 12:10:12 +0100
From: =?ISO-8859-1?Q?Marc_Heissenb=FCttel?= <heissen@iam.unibe.ch>
To: manet@ietf.org
Message-id: <3DD0E194.3010602@iam.unibe.ch>
Organization: Dept. of CS, University of Bern, Switzerland
MIME-version: 1.0
Content-type: text/plain; charset=ISO-8859-1; format=flowed
Content-transfer-encoding: 8BIT
X-Accept-Language: en-us, en
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.2b)
 Gecko/20021016
Content-Transfer-Encoding: 8BIT
Subject: [manet] Looking for simple network simulator
Sender: manet-admin@ietf.org
Errors-To: manet-admin@ietf.org
X-BeenThere: manet@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/manet>,
	<mailto:manet-request@ietf.org?subject=unsubscribe>
List-Id: Mobile Ad-hoc Networks  <manet.ietf.org>
List-Post: <mailto:manet@ietf.org>
List-Help: <mailto:manet-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/manet>,
	<mailto:manet-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 8BIT


Hi,

I doing some research with routing protocols.
Now, I wonder, if there is any simple, basic network simulator, which 
allows fast implementing and testing of new protocols? (Not like ns-2, 
QualNet, ... which also implements e.g. all the other layers). Just a 
very simple simulator, to get an idea of how a new manet routing protcol 
behaves.

Thanks and best regards,

	Marc


-- 

Marc Heissenbüttel
Computer Networks and Distributed Systems
Institute of Computer Science and Applied Mathematics
University of Bern
Neubrückstrasse 10
CH-3012 Bern
Switzerland

Tel: +41 31 631 86 91 (Direct)
Tel: +41 31 631 89 57 (Secretary)
Fax: +41 31 631 32 61

Email: heissen@iam.unibe.ch
http://www.iam.unibe.ch

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


From mailnull@www1.ietf.org  Tue Nov 12 06:37:55 2002
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id GAA27736
	for <manet-archive@odin.ietf.org>; Tue, 12 Nov 2002 06:37:55 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id gACBe0B26457
	for manet-archive@odin.ietf.org; Tue, 12 Nov 2002 06:40:00 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gACBdxv26454
	for <manet-web-archive@optimus.ietf.org>; Tue, 12 Nov 2002 06:39:59 -0500
Received: from www1.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id GAA27721
	for <manet-web-archive@ietf.org>; Tue, 12 Nov 2002 06:37:24 -0500 (EST)
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gACBK5v25002;
	Tue, 12 Nov 2002 06:20:05 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gACBAfv24758
	for <manet@optimus.ietf.org>; Tue, 12 Nov 2002 06:10:41 -0500
Received: from mailhub.unibe.ch (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id GAA27148
	for <manet@ietf.org>; Tue, 12 Nov 2002 06:08:06 -0500 (EST)
Received: from CONVERSION-DAEMON.mailhub.unibe.ch by mailhub.unibe.ch
 (PMDF V6.1 #40086) id <0H5G00A01N1P5Z@mailhub.unibe.ch> for manet@ietf.org;
 Tue, 12 Nov 2002 12:10:39 +0100 (MET)
Received: from iam.unibe.ch (asterix.unibe.ch [130.92.64.4])
 by mailhub.unibe.ch (PMDF V6.1 #40086)
 with ESMTP id <0H5G00MHSN1PKF@mailhub.unibe.ch> for manet@ietf.org; Tue,
 12 Nov 2002 12:10:37 +0100 (MET)
Received: from iam.unibe.ch (kirok [130.92.65.230])
	by iam.unibe.ch (8.11.6+Sun/8.11.6) with ESMTP id gACBAac28305	for
 <manet@ietf.org>; Tue, 12 Nov 2002 12:10:36 +0100 (MET)
Date: Tue, 12 Nov 2002 12:10:12 +0100
From: =?ISO-8859-1?Q?Marc_Heissenb=FCttel?= <heissen@iam.unibe.ch>
To: manet@ietf.org
Message-id: <3DD0E194.3010602@iam.unibe.ch>
Organization: Dept. of CS, University of Bern, Switzerland
MIME-version: 1.0
Content-type: text/plain; charset=ISO-8859-1; format=flowed
Content-transfer-encoding: 8BIT
X-Accept-Language: en-us, en
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.2b)
 Gecko/20021016
Content-Transfer-Encoding: 8BIT
Subject: [manet] Looking for simple network simulator
Sender: manet-admin@ietf.org
Errors-To: manet-admin@ietf.org
X-BeenThere: manet@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/manet>,
	<mailto:manet-request@ietf.org?subject=unsubscribe>
List-Id: Mobile Ad-hoc Networks  <manet.ietf.org>
List-Post: <mailto:manet@ietf.org>
List-Help: <mailto:manet-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/manet>,
	<mailto:manet-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 8BIT
Content-Transfer-Encoding: 8BIT


Hi,

I doing some research with routing protocols.
Now, I wonder, if there is any simple, basic network simulator, which 
allows fast implementing and testing of new protocols? (Not like ns-2, 
QualNet, ... which also implements e.g. all the other layers). Just a 
very simple simulator, to get an idea of how a new manet routing protcol 
behaves.

Thanks and best regards,

	Marc


-- 

Marc Heissenbüttel
Computer Networks and Distributed Systems
Institute of Computer Science and Applied Mathematics
University of Bern
Neubrückstrasse 10
CH-3012 Bern
Switzerland

Tel: +41 31 631 86 91 (Direct)
Tel: +41 31 631 89 57 (Secretary)
Fax: +41 31 631 32 61

Email: heissen@iam.unibe.ch
http://www.iam.unibe.ch

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



From mailnull@www1.ietf.org  Tue Nov 12 16:30:53 2002
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA16825
	for <manet-archive@odin.ietf.org>; Tue, 12 Nov 2002 16:30:53 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id gACLX2l32139
	for manet-archive@odin.ietf.org; Tue, 12 Nov 2002 16:33:02 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gACLX2v32136
	for <manet-web-archive@optimus.ietf.org>; Tue, 12 Nov 2002 16:33:02 -0500
Received: from www1.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA16812
	for <manet-web-archive@ietf.org>; Tue, 12 Nov 2002 16:30:22 -0500 (EST)
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gACLFLv31037;
	Tue, 12 Nov 2002 16:15:21 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gACL75v30388
	for <manet@optimus.ietf.org>; Tue, 12 Nov 2002 16:07:05 -0500
Received: from ece.rice.edu (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA15741
	for <manet@ietf.org>; Tue, 12 Nov 2002 16:04:26 -0500 (EST)
Received: from localhost (localhost [127.0.0.1])
	by ece.rice.edu (Postfix) with SMTP id B6EEB68B59
	for <manet@ietf.org>; Tue, 12 Nov 2002 15:06:55 -0600 (CST)
Received: from localhost (localhost [127.0.0.1])
	by ece.rice.edu (Postfix) with ESMTP id 6ADF668B01
	for <manet@ietf.org>; Tue, 12 Nov 2002 15:06:55 -0600 (CST)
Received: from egress.ece.rice.edu (egress.ece.rice.edu [128.42.12.74])
	by ece.rice.edu (Postfix) with ESMTP id 9537068A89
	for <manet@ietf.org>; Tue, 12 Nov 2002 15:06:54 -0600 (CST)
Received: from localhost (kanodia@localhost)
	by egress.ece.rice.edu (8.9.3/8.9.3) with ESMTP id PAA13524
	for <manet@ietf.org>; Tue, 12 Nov 2002 15:06:54 -0600
X-Authentication-Warning: egress.ece.rice.edu: kanodia owned process doing -bs
Date: Tue, 12 Nov 2002 15:06:54 -0600 (CST)
From: Vikram Kanodia <kanodia@rice.edu>
X-Sender: kanodia@egress.ece.rice.edu
To: manet@ietf.org
In-Reply-To: <200211110326.WAA29816@ietf.org>
Message-ID: <Pine.LNX.4.21.0211121504380.13137-100000@egress.ece.rice.edu>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
X-Virus-Scanned: by AMaViS snapshot-20020300
X-DCC--Metrics: ece.rice.edu 1066; Body=1 Fuz1=1 Fuz2=1
Subject: [manet] directional antennae
Sender: manet-admin@ietf.org
Errors-To: manet-admin@ietf.org
X-BeenThere: manet@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/manet>,
	<mailto:manet-request@ietf.org?subject=unsubscribe>
List-Id: Mobile Ad-hoc Networks  <manet.ietf.org>
List-Post: <mailto:manet@ietf.org>
List-Help: <mailto:manet-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/manet>,
	<mailto:manet-request@ietf.org?subject=subscribe>

Hi,

This question is with regard to all the directional antennae work going on
in the community. Most of the works I have seen depend on the capability
of a node to detect the Angle-of-Arrival for an incoming beam
correctly. Does anybody have an idea how hard it is to do this in an
indoor environment where there is no single line-of-sight component and
multipath is the order of the day ?

Thanks,
-Vikram


------
Department of ECE, Rice University | 713 348 3786 (O)| 713 664 5650(H)
WWW: http://www.ece.rice.edu/~kanodia 

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



From manet-admin@ietf.org  Tue Nov 12 16:31:20 2002
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA16884
	for <manet-archive@lists.ietf.org>; Tue, 12 Nov 2002 16:31:20 -0500 (EST)
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gACLFLv31037;
	Tue, 12 Nov 2002 16:15:21 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gACL75v30388
	for <manet@optimus.ietf.org>; Tue, 12 Nov 2002 16:07:05 -0500
Received: from ece.rice.edu (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA15741
	for <manet@ietf.org>; Tue, 12 Nov 2002 16:04:26 -0500 (EST)
Received: from localhost (localhost [127.0.0.1])
	by ece.rice.edu (Postfix) with SMTP id B6EEB68B59
	for <manet@ietf.org>; Tue, 12 Nov 2002 15:06:55 -0600 (CST)
Received: from localhost (localhost [127.0.0.1])
	by ece.rice.edu (Postfix) with ESMTP id 6ADF668B01
	for <manet@ietf.org>; Tue, 12 Nov 2002 15:06:55 -0600 (CST)
Received: from egress.ece.rice.edu (egress.ece.rice.edu [128.42.12.74])
	by ece.rice.edu (Postfix) with ESMTP id 9537068A89
	for <manet@ietf.org>; Tue, 12 Nov 2002 15:06:54 -0600 (CST)
Received: from localhost (kanodia@localhost)
	by egress.ece.rice.edu (8.9.3/8.9.3) with ESMTP id PAA13524
	for <manet@ietf.org>; Tue, 12 Nov 2002 15:06:54 -0600
X-Authentication-Warning: egress.ece.rice.edu: kanodia owned process doing -bs
Date: Tue, 12 Nov 2002 15:06:54 -0600 (CST)
From: Vikram Kanodia <kanodia@rice.edu>
X-Sender: kanodia@egress.ece.rice.edu
To: manet@ietf.org
In-Reply-To: <200211110326.WAA29816@ietf.org>
Message-ID: <Pine.LNX.4.21.0211121504380.13137-100000@egress.ece.rice.edu>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
X-Virus-Scanned: by AMaViS snapshot-20020300
X-DCC--Metrics: ece.rice.edu 1066; Body=1 Fuz1=1 Fuz2=1
Subject: [manet] directional antennae
Sender: manet-admin@ietf.org
Errors-To: manet-admin@ietf.org
X-BeenThere: manet@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/manet>,
	<mailto:manet-request@ietf.org?subject=unsubscribe>
List-Id: Mobile Ad-hoc Networks  <manet.ietf.org>
List-Post: <mailto:manet@ietf.org>
List-Help: <mailto:manet-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/manet>,
	<mailto:manet-request@ietf.org?subject=subscribe>

Hi,

This question is with regard to all the directional antennae work going on
in the community. Most of the works I have seen depend on the capability
of a node to detect the Angle-of-Arrival for an incoming beam
correctly. Does anybody have an idea how hard it is to do this in an
indoor environment where there is no single line-of-sight component and
multipath is the order of the day ?

Thanks,
-Vikram


------
Department of ECE, Rice University | 713 348 3786 (O)| 713 664 5650(H)
WWW: http://www.ece.rice.edu/~kanodia 

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


From manet-admin@ietf.org  Tue Nov 12 21:18:29 2002
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id VAA23632
	for <manet-archive@lists.ietf.org>; Tue, 12 Nov 2002 21:18:29 -0500 (EST)
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gAD2Cwv16656;
	Tue, 12 Nov 2002 21:12:58 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gAD254v15830
	for <manet@optimus.ietf.org>; Tue, 12 Nov 2002 21:05:04 -0500
Received: from web14408.mail.yahoo.com (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id VAA23318
	for <manet@ietf.org>; Tue, 12 Nov 2002 21:02:23 -0500 (EST)
Message-ID: <20021113020455.85543.qmail@web14408.mail.yahoo.com>
Received: from [155.69.5.222] by web14408.mail.yahoo.com via HTTP; Tue, 12 Nov 2002 18:04:55 PST
Date: Tue, 12 Nov 2002 18:04:55 -0800 (PST)
From: lijuan zhu <ljzhu80@yahoo.com>
Subject: [manet] economic models and game theory
To: manet@ietf.org
Cc: wyfmanet@hotmail.com
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="0-1110533558-1037153095=:84683"
Sender: manet-admin@ietf.org
Errors-To: manet-admin@ietf.org
X-BeenThere: manet@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/manet>,
	<mailto:manet-request@ietf.org?subject=unsubscribe>
List-Id: Mobile Ad-hoc Networks  <manet.ietf.org>
List-Post: <mailto:manet@ietf.org>
List-Help: <mailto:manet-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/manet>,
	<mailto:manet-request@ietf.org?subject=subscribe>

--0-1110533558-1037153095=:84683
Content-Type: text/plain; charset=us-ascii

http://www.economics.harvard.edu/~aroth/alroth.html
http://www.comsoc.org/iscc/2000/ISCC'2000_files/report/Hubeaux-ISCC2000-AntibesJul00.PDF
http://www.eurecom.fr/~michiard/pub/michpi-020301.pdf


---------------------------------
Do you Yahoo!?
U2 on LAUNCH - Exclusive medley & videos from Greatest Hits CD
--0-1110533558-1037153095=:84683
Content-Type: text/html; charset=us-ascii

<A href="http://www.economics.harvard.edu/~aroth/alroth.html">http://www.economics.harvard.edu/~aroth/alroth.html</A><BR><A href="http://www.comsoc.org/iscc/2000/ISCC'2000_files/report/Hubeaux-ISCC2000-AntibesJul00.PDF">http://www.comsoc.org/iscc/2000/ISCC'2000_files/report/Hubeaux-ISCC2000-AntibesJul00.PDF</A><BR><A href="http://www.eurecom.fr/~michiard/pub/michpi-020301.pdf">http://www.eurecom.fr/~michiard/pub/michpi-020301.pdf</A><p><br><hr size=1>Do you Yahoo!?<br>
<a href="http://rd.yahoo.com/launch/mailsig/*http://launch.yahoo.com/u2">U2 on LAUNCH</a> - Exclusive medley & videos from Greatest Hits CD
--0-1110533558-1037153095=:84683--
_______________________________________________
manet mailing list
manet@ietf.org
https://www1.ietf.org/mailman/listinfo/manet


From mailnull@www1.ietf.org  Tue Nov 12 21:22:54 2002
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id VAA23841
	for <manet-archive@odin.ietf.org>; Tue, 12 Nov 2002 21:22:54 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id gAD2P5817373
	for manet-archive@odin.ietf.org; Tue, 12 Nov 2002 21:25:05 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gAD2P4v17370
	for <manet-web-archive@optimus.ietf.org>; Tue, 12 Nov 2002 21:25:04 -0500
Received: from www1.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id VAA23808
	for <manet-web-archive@ietf.org>; Tue, 12 Nov 2002 21:22:23 -0500 (EST)
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gAD2Cwv16656;
	Tue, 12 Nov 2002 21:12:58 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gAD254v15830
	for <manet@optimus.ietf.org>; Tue, 12 Nov 2002 21:05:04 -0500
Received: from web14408.mail.yahoo.com (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id VAA23318
	for <manet@ietf.org>; Tue, 12 Nov 2002 21:02:23 -0500 (EST)
Message-ID: <20021113020455.85543.qmail@web14408.mail.yahoo.com>
Received: from [155.69.5.222] by web14408.mail.yahoo.com via HTTP; Tue, 12 Nov 2002 18:04:55 PST
Date: Tue, 12 Nov 2002 18:04:55 -0800 (PST)
From: lijuan zhu <ljzhu80@yahoo.com>
Subject: [manet] economic models and game theory
To: manet@ietf.org
Cc: wyfmanet@hotmail.com
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="0-1110533558-1037153095=:84683"
Sender: manet-admin@ietf.org
Errors-To: manet-admin@ietf.org
X-BeenThere: manet@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/manet>,
	<mailto:manet-request@ietf.org?subject=unsubscribe>
List-Id: Mobile Ad-hoc Networks  <manet.ietf.org>
List-Post: <mailto:manet@ietf.org>
List-Help: <mailto:manet-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/manet>,
	<mailto:manet-request@ietf.org?subject=subscribe>

--0-1110533558-1037153095=:84683
Content-Type: text/plain; charset=us-ascii

http://www.economics.harvard.edu/~aroth/alroth.html
http://www.comsoc.org/iscc/2000/ISCC'2000_files/report/Hubeaux-ISCC2000-AntibesJul00.PDF
http://www.eurecom.fr/~michiard/pub/michpi-020301.pdf


---------------------------------
Do you Yahoo!?
U2 on LAUNCH - Exclusive medley & videos from Greatest Hits CD
--0-1110533558-1037153095=:84683
Content-Type: text/html; charset=us-ascii

<A href="http://www.economics.harvard.edu/~aroth/alroth.html">http://www.economics.harvard.edu/~aroth/alroth.html</A><BR><A href="http://www.comsoc.org/iscc/2000/ISCC'2000_files/report/Hubeaux-ISCC2000-AntibesJul00.PDF">http://www.comsoc.org/iscc/2000/ISCC'2000_files/report/Hubeaux-ISCC2000-AntibesJul00.PDF</A><BR><A href="http://www.eurecom.fr/~michiard/pub/michpi-020301.pdf">http://www.eurecom.fr/~michiard/pub/michpi-020301.pdf</A><p><br><hr size=1>Do you Yahoo!?<br>
<a href="http://rd.yahoo.com/launch/mailsig/*http://launch.yahoo.com/u2">U2 on LAUNCH</a> - Exclusive medley & videos from Greatest Hits CD
--0-1110533558-1037153095=:84683--
_______________________________________________
manet mailing list
manet@ietf.org
https://www1.ietf.org/mailman/listinfo/manet



From mailnull@www1.ietf.org  Tue Nov 12 21:32:39 2002
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id VAA24078
	for <manet-archive@odin.ietf.org>; Tue, 12 Nov 2002 21:32:39 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id gAD2Ynf17849
	for manet-archive@odin.ietf.org; Tue, 12 Nov 2002 21:34:49 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gAD2Ykv17846
	for <manet-web-archive@optimus.ietf.org>; Tue, 12 Nov 2002 21:34:46 -0500
Received: from www1.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id VAA24069
	for <manet-web-archive@ietf.org>; Tue, 12 Nov 2002 21:32:03 -0500 (EST)
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gAD2Qnv17423;
	Tue, 12 Nov 2002 21:26:49 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gAD2Kcv17157
	for <manet@optimus.ietf.org>; Tue, 12 Nov 2002 21:20:38 -0500
Received: from smtp.x263.net (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id VAA23602
	for <manet@ietf.org>; Tue, 12 Nov 2002 21:17:55 -0500 (EST)
Received: from befine (mta5 [127.0.0.1])
	by smtp.x263.net (Postfix) with ESMTP id B7FB42F77F
	for <manet@ietf.org>; Wed, 13 Nov 2002 10:05:58 +0800 (CST)
Received: from befine (unknown [211.71.13.13])
	by antispam-5 (Coremail) with SMTP id 7oBXAISz0T2uJA0N.1
	for <manet@ietf.org>; Wed, 13 Nov 2002 10:06:01 +0800 (CST)
Date: Wed, 13 Nov 2002 10:18:26 +0800
From: "Harry" <hr_befine@263.net>
To: MANET mail list <manet@ietf.org>
X-mailer: Foxmail 4.1 [cn]
Mime-Version: 1.0
Content-Type: text/plain;
      charset="GB2312"
Message-Id: <20021113020558.B7FB42F77F@smtp.x263.net>
Content-Transfer-Encoding: 8bit
X-MIME-Autoconverted: from quoted-printable to 8bit by www1.ietf.org id gAD2Kcv17158
Subject: [manet] Qos Issues
Sender: manet-admin@ietf.org
Errors-To: manet-admin@ietf.org
X-BeenThere: manet@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/manet>,
	<mailto:manet-request@ietf.org?subject=unsubscribe>
List-Id: Mobile Ad-hoc Networks  <manet.ietf.org>
List-Post: <mailto:manet@ietf.org>
List-Help: <mailto:manet-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/manet>,
	<mailto:manet-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 8bit
Content-Transfer-Encoding: 8bit

Hi,all:
	As a new researcher on QoS issues of MANETs, i find that most of the researchers are focused on QoS routing and less on QoS Model or signal protocols. Since just only FQMM has been proposed these years, i wonder what qos models have the qos routing researchers used while simulating. Or is it necesary to develope a novel Qos Model for MANETs?
	And would u pls give me some advises about my research on QoS of MANETs.
	Any points will be appreciated!
	Thx a lot.


Best Regards 				

ˇˇˇˇˇˇˇˇˇˇˇˇˇˇˇˇHarry
ˇˇˇˇˇˇˇˇˇˇˇˇˇˇˇˇˇˇˇˇ2002-11-13


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



From manet-admin@ietf.org  Tue Nov 12 21:33:06 2002
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id VAA24133
	for <manet-archive@lists.ietf.org>; Tue, 12 Nov 2002 21:33:06 -0500 (EST)
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gAD2Qnv17423;
	Tue, 12 Nov 2002 21:26:49 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gAD2Kcv17157
	for <manet@optimus.ietf.org>; Tue, 12 Nov 2002 21:20:38 -0500
Received: from smtp.x263.net (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id VAA23602
	for <manet@ietf.org>; Tue, 12 Nov 2002 21:17:55 -0500 (EST)
Received: from befine (mta5 [127.0.0.1])
	by smtp.x263.net (Postfix) with ESMTP id B7FB42F77F
	for <manet@ietf.org>; Wed, 13 Nov 2002 10:05:58 +0800 (CST)
Received: from befine (unknown [211.71.13.13])
	by antispam-5 (Coremail) with SMTP id 7oBXAISz0T2uJA0N.1
	for <manet@ietf.org>; Wed, 13 Nov 2002 10:06:01 +0800 (CST)
Date: Wed, 13 Nov 2002 10:18:26 +0800
From: "Harry" <hr_befine@263.net>
To: MANET mail list <manet@ietf.org>
X-mailer: Foxmail 4.1 [cn]
Mime-Version: 1.0
Content-Type: text/plain;
      charset="GB2312"
Message-Id: <20021113020558.B7FB42F77F@smtp.x263.net>
Content-Transfer-Encoding: 8bit
X-MIME-Autoconverted: from quoted-printable to 8bit by www1.ietf.org id gAD2Kcv17158
Subject: [manet] Qos Issues
Sender: manet-admin@ietf.org
Errors-To: manet-admin@ietf.org
X-BeenThere: manet@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/manet>,
	<mailto:manet-request@ietf.org?subject=unsubscribe>
List-Id: Mobile Ad-hoc Networks  <manet.ietf.org>
List-Post: <mailto:manet@ietf.org>
List-Help: <mailto:manet-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/manet>,
	<mailto:manet-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 8bit

Hi,all:
	As a new researcher on QoS issues of MANETs, i find that most of the researchers are focused on QoS routing and less on QoS Model or signal protocols. Since just only FQMM has been proposed these years, i wonder what qos models have the qos routing researchers used while simulating. Or is it necesary to develope a novel Qos Model for MANETs?
	And would u pls give me some advises about my research on QoS of MANETs.
	Any points will be appreciated!
	Thx a lot.


Best Regards 				

ˇˇˇˇˇˇˇˇˇˇˇˇˇˇˇˇHarry
ˇˇˇˇˇˇˇˇˇˇˇˇˇˇˇˇˇˇˇˇ2002-11-13


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


From mailnull@www1.ietf.org  Tue Nov 12 23:57:07 2002
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id XAA27094
	for <manet-archive@odin.ietf.org>; Tue, 12 Nov 2002 23:57:07 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id gAD4xKQ25470
	for manet-archive@odin.ietf.org; Tue, 12 Nov 2002 23:59:20 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gAD4xKv25466
	for <manet-web-archive@optimus.ietf.org>; Tue, 12 Nov 2002 23:59:20 -0500
Received: from www1.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id XAA27072
	for <manet-web-archive@ietf.org>; Tue, 12 Nov 2002 23:56:36 -0500 (EST)
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gAD4pEv25199;
	Tue, 12 Nov 2002 23:51:14 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gAD4hNv25044
	for <manet@optimus.ietf.org>; Tue, 12 Nov 2002 23:43:23 -0500
Received: from relay1.san1.aens.net (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id XAA26743
	for <manet@ietf.org>; Tue, 12 Nov 2002 23:40:39 -0500 (EST)
Received: from cs.ucla.edu (2005host232.starwoodbroadband.com [12.160.3.232])
	by relay1.san1.aens.net (8.11.6/8.9.3) with ESMTP id gAD4jYt16643;
	Wed, 13 Nov 2002 04:45:34 GMT
Message-ID: <3DD1D849.B15DA755@cs.ucla.edu>
Date: Tue, 12 Nov 2002 20:42:49 -0800
From: Mineo Takai <mineo@cs.ucla.edu>
X-Mailer: Mozilla 4.79 [en] (Windows NT 5.0; U)
X-Accept-Language: en
MIME-Version: 1.0
To: Vikram Kanodia <kanodia@rice.edu>
CC: manet@ietf.org
Subject: Re: [manet] directional antennae
References: <Pine.LNX.4.21.0211121504380.13137-100000@egress.ece.rice.edu>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit
Sender: manet-admin@ietf.org
Errors-To: manet-admin@ietf.org
X-BeenThere: manet@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/manet>,
	<mailto:manet-request@ietf.org?subject=unsubscribe>
List-Id: Mobile Ad-hoc Networks  <manet.ietf.org>
List-Post: <mailto:manet@ietf.org>
List-Help: <mailto:manet-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/manet>,
	<mailto:manet-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit

Hello Vikram,

(I would use "antennas" rather than "antennae" for wireless
communications.)

If AOAs of multipath components are equally spread over 360 degrees, and
no ray is significantly stronger than the others, it is difficult to
identify an effective AOA for beamforming. However, the antenna system
does not need to estimate AOA if the pattern adaptation objective
function is the maximization of SIR (Signal to Interference Ratio). Some
of the proposed ideas (like DNAV) can be adapted to support these kinds
of adaptive antenna systems.

Mineo

Vikram Kanodia wrote:
> 
> Hi,
> 
> This question is with regard to all the directional antennae work going on
> in the community. Most of the works I have seen depend on the capability
> of a node to detect the Angle-of-Arrival for an incoming beam
> correctly. Does anybody have an idea how hard it is to do this in an
> indoor environment where there is no single line-of-sight component and
> multipath is the order of the day ?
> 
> Thanks,
> -Vikram
> 
> ------
> Department of ECE, Rice University | 713 348 3786 (O)| 713 664 5650(H)
> WWW: http://www.ece.rice.edu/~kanodia
> 
> _______________________________________________
> manet mailing list
> manet@ietf.org
> https://www1.ietf.org/mailman/listinfo/manet
_______________________________________________
manet mailing list
manet@ietf.org
https://www1.ietf.org/mailman/listinfo/manet



From manet-admin@ietf.org  Tue Nov 12 23:57:35 2002
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id XAA27108
	for <manet-archive@lists.ietf.org>; Tue, 12 Nov 2002 23:57:35 -0500 (EST)
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gAD4pEv25199;
	Tue, 12 Nov 2002 23:51:14 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gAD4hNv25044
	for <manet@optimus.ietf.org>; Tue, 12 Nov 2002 23:43:23 -0500
Received: from relay1.san1.aens.net (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id XAA26743
	for <manet@ietf.org>; Tue, 12 Nov 2002 23:40:39 -0500 (EST)
Received: from cs.ucla.edu (2005host232.starwoodbroadband.com [12.160.3.232])
	by relay1.san1.aens.net (8.11.6/8.9.3) with ESMTP id gAD4jYt16643;
	Wed, 13 Nov 2002 04:45:34 GMT
Message-ID: <3DD1D849.B15DA755@cs.ucla.edu>
Date: Tue, 12 Nov 2002 20:42:49 -0800
From: Mineo Takai <mineo@cs.ucla.edu>
X-Mailer: Mozilla 4.79 [en] (Windows NT 5.0; U)
X-Accept-Language: en
MIME-Version: 1.0
To: Vikram Kanodia <kanodia@rice.edu>
CC: manet@ietf.org
Subject: Re: [manet] directional antennae
References: <Pine.LNX.4.21.0211121504380.13137-100000@egress.ece.rice.edu>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit
Sender: manet-admin@ietf.org
Errors-To: manet-admin@ietf.org
X-BeenThere: manet@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/manet>,
	<mailto:manet-request@ietf.org?subject=unsubscribe>
List-Id: Mobile Ad-hoc Networks  <manet.ietf.org>
List-Post: <mailto:manet@ietf.org>
List-Help: <mailto:manet-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/manet>,
	<mailto:manet-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 7bit

Hello Vikram,

(I would use "antennas" rather than "antennae" for wireless
communications.)

If AOAs of multipath components are equally spread over 360 degrees, and
no ray is significantly stronger than the others, it is difficult to
identify an effective AOA for beamforming. However, the antenna system
does not need to estimate AOA if the pattern adaptation objective
function is the maximization of SIR (Signal to Interference Ratio). Some
of the proposed ideas (like DNAV) can be adapted to support these kinds
of adaptive antenna systems.

Mineo

Vikram Kanodia wrote:
> 
> Hi,
> 
> This question is with regard to all the directional antennae work going on
> in the community. Most of the works I have seen depend on the capability
> of a node to detect the Angle-of-Arrival for an incoming beam
> correctly. Does anybody have an idea how hard it is to do this in an
> indoor environment where there is no single line-of-sight component and
> multipath is the order of the day ?
> 
> Thanks,
> -Vikram
> 
> ------
> Department of ECE, Rice University | 713 348 3786 (O)| 713 664 5650(H)
> WWW: http://www.ece.rice.edu/~kanodia
> 
> _______________________________________________
> manet mailing list
> manet@ietf.org
> https://www1.ietf.org/mailman/listinfo/manet
_______________________________________________
manet mailing list
manet@ietf.org
https://www1.ietf.org/mailman/listinfo/manet


From manet-admin@ietf.org  Wed Nov 13 11:59:30 2002
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA08362
	for <manet-archive@lists.ietf.org>; Wed, 13 Nov 2002 11:59:30 -0500 (EST)
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gADGqUv11969;
	Wed, 13 Nov 2002 11:52:31 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gADGmXv11815
	for <manet@optimus.ietf.org>; Wed, 13 Nov 2002 11:48:33 -0500
Received: from angelo.kcl.ac.uk (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA07753
	for <manet@ietf.org>; Wed, 13 Nov 2002 11:45:54 -0500 (EST)
Received:  from qifan (EE189.eee.kcl.ac.uk [137.73.11.245])
	by angelo.kcl.ac.uk  with SMTP id gADGh3GD017478
	for <manet@ietf.org>; Wed, 13 Nov 2002 16:43:03 GMT
Message-ID: <001f01c28b33$dc3837e0$f50b4989@qifan>
From: "Qi Fan" <qi.fan@kcl.ac.uk>
To: "MANET Mailing List" <manet@ietf.org>
Date: Wed, 13 Nov 2002 16:43:57 -0000
MIME-Version: 1.0
Content-Type: text/plain;
	charset="gb2312"
Content-Transfer-Encoding: 7bit
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 6.00.2600.0000
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2600.0000
X-MailScanner: Found to be clean
Content-Transfer-Encoding: 7bit
Subject: [manet] Fw: help
Sender: manet-admin@ietf.org
Errors-To: manet-admin@ietf.org
X-BeenThere: manet@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/manet>,
	<mailto:manet-request@ietf.org?subject=unsubscribe>
List-Id: Mobile Ad-hoc Networks  <manet.ietf.org>
List-Post: <mailto:manet@ietf.org>
List-Help: <mailto:manet-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/manet>,
	<mailto:manet-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 7bit


Warm regards, and have a nice day!

Boris
------------------------------------
Qi Fan
Ph.D Research Student

Center for Telecommunications Research
King's College
University of London
Strand
London WC2R 2LS
United Kingdom

Tel:    +44 (0)20 7848 1859
Fax:   +44 (0)20 7848 2664
Email:  Qi.Fan@kcl.ac.uk
----- Original Message -----
From: "Qi Fan" <fanqi@msn.com>
To: <mark.earlam@onestopphoneshop.co.uk>
Cc: <qi.fan@kcl.ac.uk>
Sent: Wednesday, November 13, 2002 3:04 PM
Subject: help


> I have ordered a phone on 11 NOV, from you onestopphoneshop.co.uk. While i
> am tracking the progress of my order, the Status indecated me: Network
> connection failed. I am not sure what dose this means. Is that means i
> cannot buy a new one?
>
> Look forward for your help.
>
> Order Date:             11NOV02
> Order Reference No.:   OR218077
> Customer No.:            283805
>
>
> _________________________________________________________________
> Protect your PC - get McAfee.com VirusScan Online
> http://clinic.mcafee.com/clinic/ibuy/campaign.asp?cid=3963
>
>

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


From mailnull@www1.ietf.org  Wed Nov 13 12:03:42 2002
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA08565
	for <manet-archive@odin.ietf.org>; Wed, 13 Nov 2002 12:03:42 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id gADH5ot13112
	for manet-archive@odin.ietf.org; Wed, 13 Nov 2002 12:05:50 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gADH5ov13109
	for <manet-web-archive@optimus.ietf.org>; Wed, 13 Nov 2002 12:05:50 -0500
Received: from www1.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA08553
	for <manet-web-archive@ietf.org>; Wed, 13 Nov 2002 12:03:11 -0500 (EST)
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gADGqUv11969;
	Wed, 13 Nov 2002 11:52:31 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gADGmXv11815
	for <manet@optimus.ietf.org>; Wed, 13 Nov 2002 11:48:33 -0500
Received: from angelo.kcl.ac.uk (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA07753
	for <manet@ietf.org>; Wed, 13 Nov 2002 11:45:54 -0500 (EST)
Received:  from qifan (EE189.eee.kcl.ac.uk [137.73.11.245])
	by angelo.kcl.ac.uk  with SMTP id gADGh3GD017478
	for <manet@ietf.org>; Wed, 13 Nov 2002 16:43:03 GMT
Message-ID: <001f01c28b33$dc3837e0$f50b4989@qifan>
From: "Qi Fan" <qi.fan@kcl.ac.uk>
To: "MANET Mailing List" <manet@ietf.org>
Date: Wed, 13 Nov 2002 16:43:57 -0000
MIME-Version: 1.0
Content-Type: text/plain;
	charset="gb2312"
Content-Transfer-Encoding: 7bit
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 6.00.2600.0000
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2600.0000
X-MailScanner: Found to be clean
Content-Transfer-Encoding: 7bit
Subject: [manet] Fw: help
Sender: manet-admin@ietf.org
Errors-To: manet-admin@ietf.org
X-BeenThere: manet@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/manet>,
	<mailto:manet-request@ietf.org?subject=unsubscribe>
List-Id: Mobile Ad-hoc Networks  <manet.ietf.org>
List-Post: <mailto:manet@ietf.org>
List-Help: <mailto:manet-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/manet>,
	<mailto:manet-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit


Warm regards, and have a nice day!

Boris
------------------------------------
Qi Fan
Ph.D Research Student

Center for Telecommunications Research
King's College
University of London
Strand
London WC2R 2LS
United Kingdom

Tel:    +44 (0)20 7848 1859
Fax:   +44 (0)20 7848 2664
Email:  Qi.Fan@kcl.ac.uk
----- Original Message -----
From: "Qi Fan" <fanqi@msn.com>
To: <mark.earlam@onestopphoneshop.co.uk>
Cc: <qi.fan@kcl.ac.uk>
Sent: Wednesday, November 13, 2002 3:04 PM
Subject: help


> I have ordered a phone on 11 NOV, from you onestopphoneshop.co.uk. While i
> am tracking the progress of my order, the Status indecated me: Network
> connection failed. I am not sure what dose this means. Is that means i
> cannot buy a new one?
>
> Look forward for your help.
>
> Order Date:             11NOV02
> Order Reference No.:   OR218077
> Customer No.:            283805
>
>
> _________________________________________________________________
> Protect your PC - get McAfee.com VirusScan Online
> http://clinic.mcafee.com/clinic/ibuy/campaign.asp?cid=3963
>
>

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



From mailnull@www1.ietf.org  Wed Nov 13 12:46:51 2002
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA10236
	for <manet-archive@odin.ietf.org>; Wed, 13 Nov 2002 12:46:51 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id gADHmx216810
	for manet-archive@odin.ietf.org; Wed, 13 Nov 2002 12:48:59 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gADHmxv16807
	for <manet-web-archive@optimus.ietf.org>; Wed, 13 Nov 2002 12:48:59 -0500
Received: from www1.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA10202
	for <manet-web-archive@ietf.org>; Wed, 13 Nov 2002 12:46:20 -0500 (EST)
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gADHeiv16294;
	Wed, 13 Nov 2002 12:40:44 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gADHdnv16210
	for <manet@optimus.ietf.org>; Wed, 13 Nov 2002 12:39:49 -0500
Received: from angelo.kcl.ac.uk (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA09715
	for <manet@ietf.org>; Wed, 13 Nov 2002 12:37:10 -0500 (EST)
Received:  from qifan (EE189.eee.kcl.ac.uk [137.73.11.245])
	by angelo.kcl.ac.uk  with SMTP id gADHQrGD007405
	for <manet@ietf.org>; Wed, 13 Nov 2002 17:26:53 GMT
Message-ID: <004b01c28b39$fba9c840$f50b4989@qifan>
From: "Qi Fan" <qi.fan@kcl.ac.uk>
To: "MANET Mailing List" <manet@ietf.org>
Date: Wed, 13 Nov 2002 17:27:46 -0000
MIME-Version: 1.0
Content-Type: multipart/related;
	type="multipart/alternative";
	boundary="----=_NextPart_000_0047_01C28B39.FB992670"
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 6.00.2600.0000
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2600.0000
X-MailScanner: Found to be clean
Subject: [manet] Fw: help
Sender: manet-admin@ietf.org
Errors-To: manet-admin@ietf.org
X-BeenThere: manet@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/manet>,
	<mailto:manet-request@ietf.org?subject=unsubscribe>
List-Id: Mobile Ad-hoc Networks  <manet.ietf.org>
List-Post: <mailto:manet@ietf.org>
List-Help: <mailto:manet-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/manet>,
	<mailto:manet-request@ietf.org?subject=subscribe>

This is a multi-part message in MIME format.

------=_NextPart_000_0047_01C28B39.FB992670
Content-Type: multipart/alternative;
	boundary="----=_NextPart_001_0048_01C28B39.FB992670"


------=_NextPart_001_0048_01C28B39.FB992670
Content-Type: text/plain;
	charset="gb2312"
Content-Transfer-Encoding: quoted-printable

Blank
Warm regards, and have a nice day!
    =20
Boris
------------------------------------
Qi Fan
Ph.D Research Student
=20
Center for Telecommunications Research
King's College
University of London
Strand=20
London WC2R 2LS=20
United Kingdom
=20
Tel:    +44 (0)20 7848 1859
Fax:   +44 (0)20 7848 2664
Email:  Qi.Fan@kcl.ac.uk
----- Original Message -----=20
From: Qi Fan=20
To: Mailing list for all CTR members=20
Sent: Wednesday, November 13, 2002 4:03 PM
Subject: help


I am presently investigating on An IP Address Configuration Algorithm =
with Key Management in MANET which is proposed to enhance security in =
MANET address configuration.

In my plan, I need to simulate the new algorithm by using ns-2 and draw =
a performance figures. But I have not been able to get much information =
on how to=20
proceed with the simulation part. Is anyone know any information about =
this? If so, can u please point me to the relevant documentation or =
direct me on how to=20
proceed about this?

I would deeply appreciate any help.=20

Warm regards, and have a nice day!
    =20
Boris
------------------------------------
Qi Fan
Ph.D Research Student
=20
Center for Telecommunications Research
King's College
University of London
Strand=20
London WC2R 2LS=20
United Kingdom
=20
Tel:    +44 (0)20 7848 1859
Fax:   +44 (0)20 7848 2664
Email:  Qi.Fan@kcl.ac.uk



------=_NextPart_001_0048_01C28B39.FB992670
Content-Type: text/html;
	charset="gb2312"
Content-Transfer-Encoding: quoted-printable

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD><TITLE id=3DridTitle>Blank</TITLE>
<META http-equiv=3DContent-Type content=3D"text/html; =
charset=3Dgb2312"><BASE=20
href=3D"file://C:\Program Files\Common Files\Microsoft =
Shared\Stationery\">
<STYLE>BODY {
	MARGIN-TOP: 25px; FONT-SIZE: 10pt; MARGIN-LEFT: 25px; COLOR: #000000; =
FONT-FAMILY: Arial, Helvetica
}
P.msoNormal {
	MARGIN-TOP: 0px; FONT-SIZE: 10pt; MARGIN-LEFT: 0px; COLOR: #ffffcc; =
FONT-FAMILY: Helvetica, "Times New Roman"
}
LI.msoNormal {
	MARGIN-TOP: 0px; FONT-SIZE: 10pt; MARGIN-LEFT: 0px; COLOR: #ffffcc; =
FONT-FAMILY: Helvetica, "Times New Roman"
}
</STYLE>

<META content=3D"MSHTML 6.00.2600.0" name=3DGENERATOR></HEAD>
<BODY id=3DridBody bgColor=3D#ffffff=20
background=3Dcid:004601c28b39$fb8f8980$f50b4989@qifan>
<DIV>&nbsp;</DIV>
<DIV>Warm regards, and have a nice day!<BR>&nbsp;&nbsp;&nbsp;&nbsp;=20
<BR>Boris<BR>------------------------------------<BR>Qi Fan<BR>Ph.D =
Research=20
Student<BR>&nbsp;<BR>Center for Telecommunications Research<BR>King's=20
College<BR>University of London<BR>Strand <BR>London WC2R 2LS <BR>United =

Kingdom<BR>&nbsp;<BR>Tel:&nbsp;&nbsp;&nbsp; +44 (0)20 7848=20
1859<BR>Fax:&nbsp;&nbsp; +44 (0)20 7848 2664<BR>Email:&nbsp; <A=20
href=3D"mailto:Qi.Fan@kcl.ac.uk">Qi.Fan@kcl.ac.uk</A></DIV>
<DIV style=3D"FONT: 10pt arial">----- Original Message -----=20
<DIV style=3D"BACKGROUND: #e4e4e4; font-color: black"><B>From:</B> <A=20
title=3Dqi.fan@kcl.ac.uk href=3D"mailto:qi.fan@kcl.ac.uk">Qi Fan</A> =
</DIV>
<DIV><B>To:</B> <A title=3Dctr@www.ctr.kcl.ac.uk=20
href=3D"mailto:ctr@www.ctr.kcl.ac.uk">Mailing list for all CTR =
members</A> </DIV>
<DIV><B>Sent:</B> Wednesday, November 13, 2002 4:03 PM</DIV>
<DIV><B>Subject:</B> help</DIV></DIV>
<DIV><BR></DIV>
<DIV>I am presently investigating on <SPAN=20
style=3D"FONT-SIZE: 12pt; FONT-FAMILY: 'Times New Roman'; =
mso-fareast-font-family: =CB=CE=CC=E5; mso-ansi-language: EN-GB; =
mso-fareast-language: ZH-CN; mso-bidi-language: AR-SA">An=20
IP Address Configuration Algorithm with Key Management in MANET which is =

</SPAN>proposed to enhance security in MANET address =
configuration.</DIV>
<DIV>&nbsp;</DIV>
<DIV>In my plan, I need to&nbsp;simulate&nbsp;the new algorithm =
by&nbsp;using=20
ns-2 and draw a performance figures. But I have not been able to get =
much=20
information on how to <BR>proceed with the simulation part. Is anyone =
know any=20
information about this? If so, can u please point me to the relevant=20
documentation or direct me on how to <BR>proceed about this?<BR></DIV>
<DIV>I would deeply appreciate any help. <BR></DIV>
<DIV>Warm regards, and have a nice day!<BR>&nbsp;&nbsp;&nbsp;&nbsp;=20
<BR>Boris<BR>------------------------------------<BR>Qi Fan<BR>Ph.D =
Research=20
Student<BR>&nbsp;<BR>Center for Telecommunications Research<BR>King's=20
College<BR>University of London<BR>Strand <BR>London WC2R 2LS <BR>United =

Kingdom<BR>&nbsp;<BR>Tel:&nbsp;&nbsp;&nbsp; +44 (0)20 7848=20
1859<BR>Fax:&nbsp;&nbsp; +44 (0)20 7848 2664<BR>Email:&nbsp; <A=20
href=3D"mailto:Qi.Fan@kcl.ac.uk">Qi.Fan@kcl.ac.uk</A></DIV>
<P>&nbsp;</P></BODY></HTML>

------=_NextPart_001_0048_01C28B39.FB992670--

------=_NextPart_000_0047_01C28B39.FB992670
Content-Type: image/gif;
	name="Blank Bkgrd.gif"
Content-Transfer-Encoding: base64
Content-ID: <004601c28b39$fb8f8980$f50b4989@qifan>
Content-Transfer-Encoding: base64
Content-Transfer-Encoding: base64
Content-Transfer-Encoding: base64

R0lGODlhLQAtAID/AP////f39ywAAAAALQAtAEACcAxup8vtvxKQsFon6d02898pGkgiYoCm6sq2
7iqWcmzOsmeXeA7uPJd5CYdD2g9oPF58ygqz+XhCG9JpJGmlYrPXGlfr/Yo/VW45e7amp2tou/lW
xo/zX513z+Vt+1n/tiX2pxP4NUhy2FM4xtjIUQAAOw==

------=_NextPart_000_0047_01C28B39.FB992670--

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



From manet-admin@ietf.org  Wed Nov 13 12:52:23 2002
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA10444
	for <manet-archive@lists.ietf.org>; Wed, 13 Nov 2002 12:52:23 -0500 (EST)
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gADHeiv16294;
	Wed, 13 Nov 2002 12:40:44 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gADHdnv16210
	for <manet@optimus.ietf.org>; Wed, 13 Nov 2002 12:39:49 -0500
Received: from angelo.kcl.ac.uk (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA09715
	for <manet@ietf.org>; Wed, 13 Nov 2002 12:37:10 -0500 (EST)
Received:  from qifan (EE189.eee.kcl.ac.uk [137.73.11.245])
	by angelo.kcl.ac.uk  with SMTP id gADHQrGD007405
	for <manet@ietf.org>; Wed, 13 Nov 2002 17:26:53 GMT
Message-ID: <004b01c28b39$fba9c840$f50b4989@qifan>
From: "Qi Fan" <qi.fan@kcl.ac.uk>
To: "MANET Mailing List" <manet@ietf.org>
Date: Wed, 13 Nov 2002 17:27:46 -0000
MIME-Version: 1.0
Content-Type: multipart/related;
	type="multipart/alternative";
	boundary="----=_NextPart_000_0047_01C28B39.FB992670"
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 6.00.2600.0000
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2600.0000
X-MailScanner: Found to be clean
Subject: [manet] Fw: help
Sender: manet-admin@ietf.org
Errors-To: manet-admin@ietf.org
X-BeenThere: manet@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/manet>,
	<mailto:manet-request@ietf.org?subject=unsubscribe>
List-Id: Mobile Ad-hoc Networks  <manet.ietf.org>
List-Post: <mailto:manet@ietf.org>
List-Help: <mailto:manet-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/manet>,
	<mailto:manet-request@ietf.org?subject=subscribe>

This is a multi-part message in MIME format.

------=_NextPart_000_0047_01C28B39.FB992670
Content-Type: multipart/alternative;
	boundary="----=_NextPart_001_0048_01C28B39.FB992670"


------=_NextPart_001_0048_01C28B39.FB992670
Content-Type: text/plain;
	charset="gb2312"
Content-Transfer-Encoding: quoted-printable

Blank
Warm regards, and have a nice day!
    =20
Boris
------------------------------------
Qi Fan
Ph.D Research Student
=20
Center for Telecommunications Research
King's College
University of London
Strand=20
London WC2R 2LS=20
United Kingdom
=20
Tel:    +44 (0)20 7848 1859
Fax:   +44 (0)20 7848 2664
Email:  Qi.Fan@kcl.ac.uk
----- Original Message -----=20
From: Qi Fan=20
To: Mailing list for all CTR members=20
Sent: Wednesday, November 13, 2002 4:03 PM
Subject: help


I am presently investigating on An IP Address Configuration Algorithm =
with Key Management in MANET which is proposed to enhance security in =
MANET address configuration.

In my plan, I need to simulate the new algorithm by using ns-2 and draw =
a performance figures. But I have not been able to get much information =
on how to=20
proceed with the simulation part. Is anyone know any information about =
this? If so, can u please point me to the relevant documentation or =
direct me on how to=20
proceed about this?

I would deeply appreciate any help.=20

Warm regards, and have a nice day!
    =20
Boris
------------------------------------
Qi Fan
Ph.D Research Student
=20
Center for Telecommunications Research
King's College
University of London
Strand=20
London WC2R 2LS=20
United Kingdom
=20
Tel:    +44 (0)20 7848 1859
Fax:   +44 (0)20 7848 2664
Email:  Qi.Fan@kcl.ac.uk



------=_NextPart_001_0048_01C28B39.FB992670
Content-Type: text/html;
	charset="gb2312"
Content-Transfer-Encoding: quoted-printable

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD><TITLE id=3DridTitle>Blank</TITLE>
<META http-equiv=3DContent-Type content=3D"text/html; =
charset=3Dgb2312"><BASE=20
href=3D"file://C:\Program Files\Common Files\Microsoft =
Shared\Stationery\">
<STYLE>BODY {
	MARGIN-TOP: 25px; FONT-SIZE: 10pt; MARGIN-LEFT: 25px; COLOR: #000000; =
FONT-FAMILY: Arial, Helvetica
}
P.msoNormal {
	MARGIN-TOP: 0px; FONT-SIZE: 10pt; MARGIN-LEFT: 0px; COLOR: #ffffcc; =
FONT-FAMILY: Helvetica, "Times New Roman"
}
LI.msoNormal {
	MARGIN-TOP: 0px; FONT-SIZE: 10pt; MARGIN-LEFT: 0px; COLOR: #ffffcc; =
FONT-FAMILY: Helvetica, "Times New Roman"
}
</STYLE>

<META content=3D"MSHTML 6.00.2600.0" name=3DGENERATOR></HEAD>
<BODY id=3DridBody bgColor=3D#ffffff=20
background=3Dcid:004601c28b39$fb8f8980$f50b4989@qifan>
<DIV>&nbsp;</DIV>
<DIV>Warm regards, and have a nice day!<BR>&nbsp;&nbsp;&nbsp;&nbsp;=20
<BR>Boris<BR>------------------------------------<BR>Qi Fan<BR>Ph.D =
Research=20
Student<BR>&nbsp;<BR>Center for Telecommunications Research<BR>King's=20
College<BR>University of London<BR>Strand <BR>London WC2R 2LS <BR>United =

Kingdom<BR>&nbsp;<BR>Tel:&nbsp;&nbsp;&nbsp; +44 (0)20 7848=20
1859<BR>Fax:&nbsp;&nbsp; +44 (0)20 7848 2664<BR>Email:&nbsp; <A=20
href=3D"mailto:Qi.Fan@kcl.ac.uk">Qi.Fan@kcl.ac.uk</A></DIV>
<DIV style=3D"FONT: 10pt arial">----- Original Message -----=20
<DIV style=3D"BACKGROUND: #e4e4e4; font-color: black"><B>From:</B> <A=20
title=3Dqi.fan@kcl.ac.uk href=3D"mailto:qi.fan@kcl.ac.uk">Qi Fan</A> =
</DIV>
<DIV><B>To:</B> <A title=3Dctr@www.ctr.kcl.ac.uk=20
href=3D"mailto:ctr@www.ctr.kcl.ac.uk">Mailing list for all CTR =
members</A> </DIV>
<DIV><B>Sent:</B> Wednesday, November 13, 2002 4:03 PM</DIV>
<DIV><B>Subject:</B> help</DIV></DIV>
<DIV><BR></DIV>
<DIV>I am presently investigating on <SPAN=20
style=3D"FONT-SIZE: 12pt; FONT-FAMILY: 'Times New Roman'; =
mso-fareast-font-family: =CB=CE=CC=E5; mso-ansi-language: EN-GB; =
mso-fareast-language: ZH-CN; mso-bidi-language: AR-SA">An=20
IP Address Configuration Algorithm with Key Management in MANET which is =

</SPAN>proposed to enhance security in MANET address =
configuration.</DIV>
<DIV>&nbsp;</DIV>
<DIV>In my plan, I need to&nbsp;simulate&nbsp;the new algorithm =
by&nbsp;using=20
ns-2 and draw a performance figures. But I have not been able to get =
much=20
information on how to <BR>proceed with the simulation part. Is anyone =
know any=20
information about this? If so, can u please point me to the relevant=20
documentation or direct me on how to <BR>proceed about this?<BR></DIV>
<DIV>I would deeply appreciate any help. <BR></DIV>
<DIV>Warm regards, and have a nice day!<BR>&nbsp;&nbsp;&nbsp;&nbsp;=20
<BR>Boris<BR>------------------------------------<BR>Qi Fan<BR>Ph.D =
Research=20
Student<BR>&nbsp;<BR>Center for Telecommunications Research<BR>King's=20
College<BR>University of London<BR>Strand <BR>London WC2R 2LS <BR>United =

Kingdom<BR>&nbsp;<BR>Tel:&nbsp;&nbsp;&nbsp; +44 (0)20 7848=20
1859<BR>Fax:&nbsp;&nbsp; +44 (0)20 7848 2664<BR>Email:&nbsp; <A=20
href=3D"mailto:Qi.Fan@kcl.ac.uk">Qi.Fan@kcl.ac.uk</A></DIV>
<P>&nbsp;</P></BODY></HTML>

------=_NextPart_001_0048_01C28B39.FB992670--

------=_NextPart_000_0047_01C28B39.FB992670
Content-Type: image/gif;
	name="Blank Bkgrd.gif"
Content-Transfer-Encoding: base64
Content-ID: <004601c28b39$fb8f8980$f50b4989@qifan>
Content-Transfer-Encoding: base64
Content-Transfer-Encoding: base64

R0lGODlhLQAtAID/AP////f39ywAAAAALQAtAEACcAxup8vtvxKQsFon6d02898pGkgiYoCm6sq2
7iqWcmzOsmeXeA7uPJd5CYdD2g9oPF58ygqz+XhCG9JpJGmlYrPXGlfr/Yo/VW45e7amp2tou/lW
xo/zX513z+Vt+1n/tiX2pxP4NUhy2FM4xtjIUQAAOw==

------=_NextPart_000_0047_01C28B39.FB992670--

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


From mailnull@www1.ietf.org  Wed Nov 13 14:28:52 2002
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA14055
	for <manet-archive@odin.ietf.org>; Wed, 13 Nov 2002 14:28:52 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id gADJV0M23952
	for manet-archive@odin.ietf.org; Wed, 13 Nov 2002 14:31:00 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gADJV0v23949
	for <manet-web-archive@optimus.ietf.org>; Wed, 13 Nov 2002 14:31:00 -0500
Received: from www1.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA14031
	for <manet-web-archive@ietf.org>; Wed, 13 Nov 2002 14:28:21 -0500 (EST)
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gADJNCv23608;
	Wed, 13 Nov 2002 14:23:12 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gADJLLv23526
	for <manet@optimus.ietf.org>; Wed, 13 Nov 2002 14:21:21 -0500
Received: from web14914.mail.yahoo.com (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id OAA13753
	for <manet@ietf.org>; Wed, 13 Nov 2002 14:18:43 -0500 (EST)
Message-ID: <20021113192115.22729.qmail@web14914.mail.yahoo.com>
Received: from [66.69.159.142] by web14914.mail.yahoo.com via HTTP; Wed, 13 Nov 2002 11:21:15 PST
Date: Wed, 13 Nov 2002 11:21:15 -0800 (PST)
From: prashanth kumar <prashanth2713@yahoo.com>
Subject: Re: [manet] directional antennae
To: manet@ietf.org
In-Reply-To: <3DD1D849.B15DA755@cs.ucla.edu>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Sender: manet-admin@ietf.org
Errors-To: manet-admin@ietf.org
X-BeenThere: manet@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/manet>,
	<mailto:manet-request@ietf.org?subject=unsubscribe>
List-Id: Mobile Ad-hoc Networks  <manet.ietf.org>
List-Post: <mailto:manet@ietf.org>
List-Help: <mailto:manet-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/manet>,
	<mailto:manet-request@ietf.org?subject=subscribe>

The DOA of the strongest multipath is the direction of
the virtual node which corresponds to the real node
whose signal is received over this multipath. So, I
think, one can treat multipaths as if that were the
LOS path.

> Vikram Kanodia wrote:
> > 
> > Hi,
> > 
> > This question is with regard to all the
> directional antennae work going on
> > in the community. Most of the works I have seen
> depend on the capability
> > of a node to detect the Angle-of-Arrival for an
> incoming beam
> > correctly. Does anybody have an idea how hard it
> is to do this in an
> > indoor environment where there is no single
> line-of-sight component and
> > multipath is the order of the day ?
> > 
> > Thanks,
> > -Vikram
> > 
> > ------
> > Department of ECE, Rice University | 713 348 3786
> (O)| 713 664 5650(H)
> > WWW: http://www.ece.rice.edu/~kanodia
> > 
> > _______________________________________________
> > manet mailing list
> > manet@ietf.org
> > https://www1.ietf.org/mailman/listinfo/manet
> _______________________________________________
> manet mailing list
> manet@ietf.org
> https://www1.ietf.org/mailman/listinfo/manet


__________________________________________________
Do you Yahoo!?
U2 on LAUNCH - Exclusive greatest hits videos
http://launch.yahoo.com/u2
_______________________________________________
manet mailing list
manet@ietf.org
https://www1.ietf.org/mailman/listinfo/manet



From manet-admin@ietf.org  Wed Nov 13 14:29:15 2002
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA14070
	for <manet-archive@lists.ietf.org>; Wed, 13 Nov 2002 14:29:15 -0500 (EST)
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gADJNCv23608;
	Wed, 13 Nov 2002 14:23:12 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gADJLLv23526
	for <manet@optimus.ietf.org>; Wed, 13 Nov 2002 14:21:21 -0500
Received: from web14914.mail.yahoo.com (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id OAA13753
	for <manet@ietf.org>; Wed, 13 Nov 2002 14:18:43 -0500 (EST)
Message-ID: <20021113192115.22729.qmail@web14914.mail.yahoo.com>
Received: from [66.69.159.142] by web14914.mail.yahoo.com via HTTP; Wed, 13 Nov 2002 11:21:15 PST
Date: Wed, 13 Nov 2002 11:21:15 -0800 (PST)
From: prashanth kumar <prashanth2713@yahoo.com>
Subject: Re: [manet] directional antennae
To: manet@ietf.org
In-Reply-To: <3DD1D849.B15DA755@cs.ucla.edu>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Sender: manet-admin@ietf.org
Errors-To: manet-admin@ietf.org
X-BeenThere: manet@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/manet>,
	<mailto:manet-request@ietf.org?subject=unsubscribe>
List-Id: Mobile Ad-hoc Networks  <manet.ietf.org>
List-Post: <mailto:manet@ietf.org>
List-Help: <mailto:manet-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/manet>,
	<mailto:manet-request@ietf.org?subject=subscribe>

The DOA of the strongest multipath is the direction of
the virtual node which corresponds to the real node
whose signal is received over this multipath. So, I
think, one can treat multipaths as if that were the
LOS path.

> Vikram Kanodia wrote:
> > 
> > Hi,
> > 
> > This question is with regard to all the
> directional antennae work going on
> > in the community. Most of the works I have seen
> depend on the capability
> > of a node to detect the Angle-of-Arrival for an
> incoming beam
> > correctly. Does anybody have an idea how hard it
> is to do this in an
> > indoor environment where there is no single
> line-of-sight component and
> > multipath is the order of the day ?
> > 
> > Thanks,
> > -Vikram
> > 
> > ------
> > Department of ECE, Rice University | 713 348 3786
> (O)| 713 664 5650(H)
> > WWW: http://www.ece.rice.edu/~kanodia
> > 
> > _______________________________________________
> > manet mailing list
> > manet@ietf.org
> > https://www1.ietf.org/mailman/listinfo/manet
> _______________________________________________
> manet mailing list
> manet@ietf.org
> https://www1.ietf.org/mailman/listinfo/manet


__________________________________________________
Do you Yahoo!?
U2 on LAUNCH - Exclusive greatest hits videos
http://launch.yahoo.com/u2
_______________________________________________
manet mailing list
manet@ietf.org
https://www1.ietf.org/mailman/listinfo/manet


From mailnull@www1.ietf.org  Wed Nov 13 17:44:08 2002
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA20829
	for <manet-archive@odin.ietf.org>; Wed, 13 Nov 2002 17:44:08 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id gADMkJS05103
	for manet-archive@odin.ietf.org; Wed, 13 Nov 2002 17:46:19 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gADMkIv05100
	for <manet-web-archive@optimus.ietf.org>; Wed, 13 Nov 2002 17:46:18 -0500
Received: from www1.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA20824
	for <manet-web-archive@ietf.org>; Wed, 13 Nov 2002 17:43:37 -0500 (EST)
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gADMcUv04729;
	Wed, 13 Nov 2002 17:38:30 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gADMZRv04061
	for <manet@optimus.ietf.org>; Wed, 13 Nov 2002 17:35:27 -0500
Received: from ece.rice.edu (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA20504
	for <manet@ietf.org>; Wed, 13 Nov 2002 17:32:46 -0500 (EST)
Received: from localhost (localhost [127.0.0.1])
	by ece.rice.edu (Postfix) with SMTP
	id 4608268AF5; Wed, 13 Nov 2002 16:35:20 -0600 (CST)
Received: from localhost (localhost [127.0.0.1])
	by ece.rice.edu (Postfix) with ESMTP
	id DE09568AE8; Wed, 13 Nov 2002 16:35:19 -0600 (CST)
Received: from egress.ece.rice.edu (egress.ece.rice.edu [128.42.12.74])
	by ece.rice.edu (Postfix) with ESMTP
	id EC96168A7D; Wed, 13 Nov 2002 16:35:18 -0600 (CST)
Received: from localhost (kanodia@localhost)
	by egress.ece.rice.edu (8.9.3/8.9.3) with ESMTP id QAA01121;
	Wed, 13 Nov 2002 16:35:18 -0600
X-Authentication-Warning: egress.ece.rice.edu: kanodia owned process doing -bs
Date: Wed, 13 Nov 2002 16:35:13 -0600 (CST)
From: Vikram Kanodia <kanodia@rice.edu>
X-Sender: kanodia@egress.ece.rice.edu
To: prashanth kumar <prashanth2713@yahoo.com>
Cc: manet@ietf.org
Subject: Re: [manet] directional antennae
In-Reply-To: <20021113192115.22729.qmail@web14914.mail.yahoo.com>
Message-ID: <Pine.LNX.4.21.0211131625380.13137-100000@egress.ece.rice.edu>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
X-Virus-Scanned: by AMaViS snapshot-20020300
X-DCC--Metrics: ece.rice.edu 1066; Body=1 Fuz1=1 Fuz2=1
Sender: manet-admin@ietf.org
Errors-To: manet-admin@ietf.org
X-BeenThere: manet@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/manet>,
	<mailto:manet-request@ietf.org?subject=unsubscribe>
List-Id: Mobile Ad-hoc Networks  <manet.ietf.org>
List-Post: <mailto:manet@ietf.org>
List-Help: <mailto:manet-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/manet>,
	<mailto:manet-request@ietf.org?subject=subscribe>

 
This would assume that if the node were to beamform towards this virtual
node, it would be able to reach the real node (that is the reflection off
surfaces resulting in the multipath is symmetric).......not a bad
assumption but one which might now work in certain environments. Moreover,
for certain directional MAC protocols this might result in a larger
deferrring region which may offset some of the spatial reuse gain....

-Vikram


> The DOA of the strongest multipath is the direction of
> the virtual node which corresponds to the real node
> whose signal is received over this multipath. So, I
> think, one can treat multipaths as if that were the
> LOS path.
> 
> > Vikram Kanodia wrote:
> > > 
> > > Hi,
> > > 
> > > This question is with regard to all the
> > directional antennae work going on
> > > in the community. Most of the works I have seen
> > depend on the capability
> > > of a node to detect the Angle-of-Arrival for an
> > incoming beam
> > > correctly. Does anybody have an idea how hard it
> > is to do this in an
> > > indoor environment where there is no single
> > line-of-sight component and
> > > multipath is the order of the day ?
> > > 
> > > Thanks,
> > > -Vikram
> > > 
> > > ------
> > > Department of ECE, Rice University | 713 348 3786
> > (O)| 713 664 5650(H)
> > > WWW: http://www.ece.rice.edu/~kanodia
> > > 
> > > _______________________________________________
> > > manet mailing list
> > > manet@ietf.org
> > > https://www1.ietf.org/mailman/listinfo/manet
> > _______________________________________________
> > manet mailing list
> > manet@ietf.org
> > https://www1.ietf.org/mailman/listinfo/manet
> 
> 
> __________________________________________________
> Do you Yahoo!?
> U2 on LAUNCH - Exclusive greatest hits videos
> http://launch.yahoo.com/u2
> _______________________________________________
> manet mailing list
> manet@ietf.org
> https://www1.ietf.org/mailman/listinfo/manet
> 

-- 

Department of ECE, Rice University | 713 348 3786 (O)| 713 664 5650(H)
WWW: http://www.ece.rice.edu/~kanodia 


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



From manet-admin@ietf.org  Wed Nov 13 17:44:38 2002
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA20846
	for <manet-archive@lists.ietf.org>; Wed, 13 Nov 2002 17:44:38 -0500 (EST)
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gADMcUv04729;
	Wed, 13 Nov 2002 17:38:30 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gADMZRv04061
	for <manet@optimus.ietf.org>; Wed, 13 Nov 2002 17:35:27 -0500
Received: from ece.rice.edu (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA20504
	for <manet@ietf.org>; Wed, 13 Nov 2002 17:32:46 -0500 (EST)
Received: from localhost (localhost [127.0.0.1])
	by ece.rice.edu (Postfix) with SMTP
	id 4608268AF5; Wed, 13 Nov 2002 16:35:20 -0600 (CST)
Received: from localhost (localhost [127.0.0.1])
	by ece.rice.edu (Postfix) with ESMTP
	id DE09568AE8; Wed, 13 Nov 2002 16:35:19 -0600 (CST)
Received: from egress.ece.rice.edu (egress.ece.rice.edu [128.42.12.74])
	by ece.rice.edu (Postfix) with ESMTP
	id EC96168A7D; Wed, 13 Nov 2002 16:35:18 -0600 (CST)
Received: from localhost (kanodia@localhost)
	by egress.ece.rice.edu (8.9.3/8.9.3) with ESMTP id QAA01121;
	Wed, 13 Nov 2002 16:35:18 -0600
X-Authentication-Warning: egress.ece.rice.edu: kanodia owned process doing -bs
Date: Wed, 13 Nov 2002 16:35:13 -0600 (CST)
From: Vikram Kanodia <kanodia@rice.edu>
X-Sender: kanodia@egress.ece.rice.edu
To: prashanth kumar <prashanth2713@yahoo.com>
Cc: manet@ietf.org
Subject: Re: [manet] directional antennae
In-Reply-To: <20021113192115.22729.qmail@web14914.mail.yahoo.com>
Message-ID: <Pine.LNX.4.21.0211131625380.13137-100000@egress.ece.rice.edu>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
X-Virus-Scanned: by AMaViS snapshot-20020300
X-DCC--Metrics: ece.rice.edu 1066; Body=1 Fuz1=1 Fuz2=1
Sender: manet-admin@ietf.org
Errors-To: manet-admin@ietf.org
X-BeenThere: manet@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/manet>,
	<mailto:manet-request@ietf.org?subject=unsubscribe>
List-Id: Mobile Ad-hoc Networks  <manet.ietf.org>
List-Post: <mailto:manet@ietf.org>
List-Help: <mailto:manet-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/manet>,
	<mailto:manet-request@ietf.org?subject=subscribe>

 
This would assume that if the node were to beamform towards this virtual
node, it would be able to reach the real node (that is the reflection off
surfaces resulting in the multipath is symmetric).......not a bad
assumption but one which might now work in certain environments. Moreover,
for certain directional MAC protocols this might result in a larger
deferrring region which may offset some of the spatial reuse gain....

-Vikram


> The DOA of the strongest multipath is the direction of
> the virtual node which corresponds to the real node
> whose signal is received over this multipath. So, I
> think, one can treat multipaths as if that were the
> LOS path.
> 
> > Vikram Kanodia wrote:
> > > 
> > > Hi,
> > > 
> > > This question is with regard to all the
> > directional antennae work going on
> > > in the community. Most of the works I have seen
> > depend on the capability
> > > of a node to detect the Angle-of-Arrival for an
> > incoming beam
> > > correctly. Does anybody have an idea how hard it
> > is to do this in an
> > > indoor environment where there is no single
> > line-of-sight component and
> > > multipath is the order of the day ?
> > > 
> > > Thanks,
> > > -Vikram
> > > 
> > > ------
> > > Department of ECE, Rice University | 713 348 3786
> > (O)| 713 664 5650(H)
> > > WWW: http://www.ece.rice.edu/~kanodia
> > > 
> > > _______________________________________________
> > > manet mailing list
> > > manet@ietf.org
> > > https://www1.ietf.org/mailman/listinfo/manet
> > _______________________________________________
> > manet mailing list
> > manet@ietf.org
> > https://www1.ietf.org/mailman/listinfo/manet
> 
> 
> __________________________________________________
> Do you Yahoo!?
> U2 on LAUNCH - Exclusive greatest hits videos
> http://launch.yahoo.com/u2
> _______________________________________________
> manet mailing list
> manet@ietf.org
> https://www1.ietf.org/mailman/listinfo/manet
> 

-- 

Department of ECE, Rice University | 713 348 3786 (O)| 713 664 5650(H)
WWW: http://www.ece.rice.edu/~kanodia 


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


From manet-admin@ietf.org  Wed Nov 13 20:32:37 2002
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id UAA23905
	for <manet-archive@lists.ietf.org>; Wed, 13 Nov 2002 20:32:37 -0500 (EST)
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gAE1Qlv12981;
	Wed, 13 Nov 2002 20:26:47 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gAE1OFv12882
	for <manet@optimus.ietf.org>; Wed, 13 Nov 2002 20:24:15 -0500
Received: from web40305.mail.yahoo.com (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id UAA23691
	for <manet@ietf.org>; Wed, 13 Nov 2002 20:21:33 -0500 (EST)
Message-ID: <20021114012405.8029.qmail@web40305.mail.yahoo.com>
Received: from [130.126.136.80] by web40305.mail.yahoo.com via HTTP; Wed, 13 Nov 2002 17:24:05 PST
Date: Wed, 13 Nov 2002 17:24:05 -0800 (PST)
From: romit roychoudhury <romit_rc@yahoo.com>
Subject: Re: [manet] directional antennae
To: Vikram Kanodia <kanodia@rice.edu>
Cc: manet@ietf.org
In-Reply-To: <Pine.LNX.4.21.0211131625380.13137-100000@egress.ece.rice.edu>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Sender: manet-admin@ietf.org
Errors-To: manet-admin@ietf.org
X-BeenThere: manet@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/manet>,
	<mailto:manet-request@ietf.org?subject=unsubscribe>
List-Id: Mobile Ad-hoc Networks  <manet.ietf.org>
List-Post: <mailto:manet@ietf.org>
List-Help: <mailto:manet-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/manet>,
	<mailto:manet-request@ietf.org?subject=subscribe>

Hi Vikram,

A few comments:
Yes, I agree that with multipath, a node that receives
several signal components, would have to set up
multiple DNAVs.
But, the DNAVs now can be more aggresive.
More clearly, the deferring region can now be several
narrower regions around the direction of arrival (DoA)
of each signal component.
Ideally, if the relative strengths of each of the
signal components are available, we could set up the
DNAV angles accordingly - wider DNAV angle for a
stronger signal and the vice versa.

Now, the new problem that arises because of this may
be as follows:
If a node has fragmented-DNAVs set up in different
directions, the regions in which the node need not
defer may no longer be wide enough to fit in a
beamwidth. In such cases, spatial reuse may indeed get
affected.
Observe that this happens not because the total
deferring region has increased, but because the
deferring region is now fragmented into several
narrower regions.

hope i made some sense there :)

regards,
romit

--------------------------------------------------
Romit Roy Choudhury
Graduate Student, UIUC.
www.crhc.uiuc.edu/~croy
---------------------------------------------------


--- Vikram Kanodia <kanodia@rice.edu> wrote:
>  
> This would assume that if the node were to beamform
> towards this virtual
> node, it would be able to reach the real node (that
> is the reflection off
> surfaces resulting in the multipath is
> symmetric).......not a bad
> assumption but one which might now work in certain
> environments. Moreover,
> for certain directional MAC protocols this might
> result in a larger
> deferrring region which may offset some of the
> spatial reuse gain....
> 
> -Vikram
> 
> 
> > The DOA of the strongest multipath is the
> direction of
> > the virtual node which corresponds to the real
> node
> > whose signal is received over this multipath. So,
> I
> > think, one can treat multipaths as if that were
> the
> > LOS path.
> > 
> > > Vikram Kanodia wrote:
> > > > 
> > > > Hi,
> > > > 
> > > > This question is with regard to all the
> > > directional antennae work going on
> > > > in the community. Most of the works I have
> seen
> > > depend on the capability
> > > > of a node to detect the Angle-of-Arrival for
> an
> > > incoming beam
> > > > correctly. Does anybody have an idea how hard
> it
> > > is to do this in an
> > > > indoor environment where there is no single
> > > line-of-sight component and
> > > > multipath is the order of the day ?
> > > > 
> > > > Thanks,
> > > > -Vikram
> > > > 
> > > > ------
> > > > Department of ECE, Rice University | 713 348
> 3786
> > > (O)| 713 664 5650(H)
> > > > WWW: http://www.ece.rice.edu/~kanodia
> > > > 
> > > >
> _______________________________________________
> > > > manet mailing list
> > > > manet@ietf.org
> > > > https://www1.ietf.org/mailman/listinfo/manet
> > > _______________________________________________
> > > manet mailing list
> > > manet@ietf.org
> > > https://www1.ietf.org/mailman/listinfo/manet
> > 
> > 
> > __________________________________________________
> > Do you Yahoo!?
> > U2 on LAUNCH - Exclusive greatest hits videos
> > http://launch.yahoo.com/u2
> > _______________________________________________
> > manet mailing list
> > manet@ietf.org
> > https://www1.ietf.org/mailman/listinfo/manet
> > 
> 
> -- 
> 
> Department of ECE, Rice University | 713 348 3786
> (O)| 713 664 5650(H)
> WWW: http://www.ece.rice.edu/~kanodia 
> 
> 
> _______________________________________________
> manet mailing list
> manet@ietf.org
> https://www1.ietf.org/mailman/listinfo/manet


__________________________________________________
Do you Yahoo!?
U2 on LAUNCH - Exclusive greatest hits videos
http://launch.yahoo.com/u2
_______________________________________________
manet mailing list
manet@ietf.org
https://www1.ietf.org/mailman/listinfo/manet


From mailnull@www1.ietf.org  Wed Nov 13 20:40:03 2002
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id UAA24025
	for <manet-archive@odin.ietf.org>; Wed, 13 Nov 2002 20:40:03 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id gAE1gEm14251
	for manet-archive@odin.ietf.org; Wed, 13 Nov 2002 20:42:14 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gAE1gEv14248
	for <manet-web-archive@optimus.ietf.org>; Wed, 13 Nov 2002 20:42:14 -0500
Received: from www1.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id UAA24016
	for <manet-web-archive@ietf.org>; Wed, 13 Nov 2002 20:39:32 -0500 (EST)
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gAE1Qlv12981;
	Wed, 13 Nov 2002 20:26:47 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gAE1OFv12882
	for <manet@optimus.ietf.org>; Wed, 13 Nov 2002 20:24:15 -0500
Received: from web40305.mail.yahoo.com (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id UAA23691
	for <manet@ietf.org>; Wed, 13 Nov 2002 20:21:33 -0500 (EST)
Message-ID: <20021114012405.8029.qmail@web40305.mail.yahoo.com>
Received: from [130.126.136.80] by web40305.mail.yahoo.com via HTTP; Wed, 13 Nov 2002 17:24:05 PST
Date: Wed, 13 Nov 2002 17:24:05 -0800 (PST)
From: romit roychoudhury <romit_rc@yahoo.com>
Subject: Re: [manet] directional antennae
To: Vikram Kanodia <kanodia@rice.edu>
Cc: manet@ietf.org
In-Reply-To: <Pine.LNX.4.21.0211131625380.13137-100000@egress.ece.rice.edu>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Sender: manet-admin@ietf.org
Errors-To: manet-admin@ietf.org
X-BeenThere: manet@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/manet>,
	<mailto:manet-request@ietf.org?subject=unsubscribe>
List-Id: Mobile Ad-hoc Networks  <manet.ietf.org>
List-Post: <mailto:manet@ietf.org>
List-Help: <mailto:manet-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/manet>,
	<mailto:manet-request@ietf.org?subject=subscribe>

Hi Vikram,

A few comments:
Yes, I agree that with multipath, a node that receives
several signal components, would have to set up
multiple DNAVs.
But, the DNAVs now can be more aggresive.
More clearly, the deferring region can now be several
narrower regions around the direction of arrival (DoA)
of each signal component.
Ideally, if the relative strengths of each of the
signal components are available, we could set up the
DNAV angles accordingly - wider DNAV angle for a
stronger signal and the vice versa.

Now, the new problem that arises because of this may
be as follows:
If a node has fragmented-DNAVs set up in different
directions, the regions in which the node need not
defer may no longer be wide enough to fit in a
beamwidth. In such cases, spatial reuse may indeed get
affected.
Observe that this happens not because the total
deferring region has increased, but because the
deferring region is now fragmented into several
narrower regions.

hope i made some sense there :)

regards,
romit

--------------------------------------------------
Romit Roy Choudhury
Graduate Student, UIUC.
www.crhc.uiuc.edu/~croy
---------------------------------------------------


--- Vikram Kanodia <kanodia@rice.edu> wrote:
>  
> This would assume that if the node were to beamform
> towards this virtual
> node, it would be able to reach the real node (that
> is the reflection off
> surfaces resulting in the multipath is
> symmetric).......not a bad
> assumption but one which might now work in certain
> environments. Moreover,
> for certain directional MAC protocols this might
> result in a larger
> deferrring region which may offset some of the
> spatial reuse gain....
> 
> -Vikram
> 
> 
> > The DOA of the strongest multipath is the
> direction of
> > the virtual node which corresponds to the real
> node
> > whose signal is received over this multipath. So,
> I
> > think, one can treat multipaths as if that were
> the
> > LOS path.
> > 
> > > Vikram Kanodia wrote:
> > > > 
> > > > Hi,
> > > > 
> > > > This question is with regard to all the
> > > directional antennae work going on
> > > > in the community. Most of the works I have
> seen
> > > depend on the capability
> > > > of a node to detect the Angle-of-Arrival for
> an
> > > incoming beam
> > > > correctly. Does anybody have an idea how hard
> it
> > > is to do this in an
> > > > indoor environment where there is no single
> > > line-of-sight component and
> > > > multipath is the order of the day ?
> > > > 
> > > > Thanks,
> > > > -Vikram
> > > > 
> > > > ------
> > > > Department of ECE, Rice University | 713 348
> 3786
> > > (O)| 713 664 5650(H)
> > > > WWW: http://www.ece.rice.edu/~kanodia
> > > > 
> > > >
> _______________________________________________
> > > > manet mailing list
> > > > manet@ietf.org
> > > > https://www1.ietf.org/mailman/listinfo/manet
> > > _______________________________________________
> > > manet mailing list
> > > manet@ietf.org
> > > https://www1.ietf.org/mailman/listinfo/manet
> > 
> > 
> > __________________________________________________
> > Do you Yahoo!?
> > U2 on LAUNCH - Exclusive greatest hits videos
> > http://launch.yahoo.com/u2
> > _______________________________________________
> > manet mailing list
> > manet@ietf.org
> > https://www1.ietf.org/mailman/listinfo/manet
> > 
> 
> -- 
> 
> Department of ECE, Rice University | 713 348 3786
> (O)| 713 664 5650(H)
> WWW: http://www.ece.rice.edu/~kanodia 
> 
> 
> _______________________________________________
> manet mailing list
> manet@ietf.org
> https://www1.ietf.org/mailman/listinfo/manet


__________________________________________________
Do you Yahoo!?
U2 on LAUNCH - Exclusive greatest hits videos
http://launch.yahoo.com/u2
_______________________________________________
manet mailing list
manet@ietf.org
https://www1.ietf.org/mailman/listinfo/manet



From manet-admin@ietf.org  Thu Nov 14 12:48:58 2002
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA25328
	for <manet-archive@lists.ietf.org>; Thu, 14 Nov 2002 12:48:58 -0500 (EST)
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gAEHdmv11605;
	Thu, 14 Nov 2002 12:39:48 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gAEHTVv10722
	for <manet@optimus.ietf.org>; Thu, 14 Nov 2002 12:29:31 -0500
Received: from ece.rice.edu (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA24900
	for <manet@ietf.org>; Thu, 14 Nov 2002 12:26:52 -0500 (EST)
Received: from localhost (localhost [127.0.0.1])
	by ece.rice.edu (Postfix) with SMTP
	id 9777868A78; Thu, 14 Nov 2002 11:29:23 -0600 (CST)
Received: from localhost (localhost [127.0.0.1])
	by ece.rice.edu (Postfix) with ESMTP
	id 2077668A76; Thu, 14 Nov 2002 11:29:23 -0600 (CST)
Received: from egress.ece.rice.edu (egress.ece.rice.edu [128.42.12.74])
	by ece.rice.edu (Postfix) with ESMTP
	id 3547D68A75; Thu, 14 Nov 2002 11:29:22 -0600 (CST)
Received: from localhost (kanodia@localhost)
	by egress.ece.rice.edu (8.9.3/8.9.3) with ESMTP id LAA05343;
	Thu, 14 Nov 2002 11:29:22 -0600
X-Authentication-Warning: egress.ece.rice.edu: kanodia owned process doing -bs
Date: Thu, 14 Nov 2002 11:29:22 -0600 (CST)
From: Vikram Kanodia <kanodia@rice.edu>
X-Sender: kanodia@egress.ece.rice.edu
To: Mineo Takai <mineo@cs.ucla.edu>
Cc: manet@ietf.org
Subject: Re: [manet] directional antennae
In-Reply-To: <3DD1D849.B15DA755@cs.ucla.edu>
Message-ID: <Pine.LNX.4.21.0211131636110.13137-100000@egress.ece.rice.edu>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
X-Virus-Scanned: by AMaViS snapshot-20020300
X-DCC--Metrics: ece.rice.edu 1066; Body=1 Fuz1=1 Fuz2=1
Sender: manet-admin@ietf.org
Errors-To: manet-admin@ietf.org
X-BeenThere: manet@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/manet>,
	<mailto:manet-request@ietf.org?subject=unsubscribe>
List-Id: Mobile Ad-hoc Networks  <manet.ietf.org>
List-Post: <mailto:manet@ietf.org>
List-Help: <mailto:manet-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/manet>,
	<mailto:manet-request@ietf.org?subject=subscribe>


Mineo,

> 
> (I would use "antennas" rather than "antennae" for wireless
> communications.)

whoops ...I did not realize that antennas was the correct plural
here...live and learn, I guess :)

> If AOAs of multipath components are equally spread over 360 degrees, and
> no ray is significantly stronger than the others, it is difficult to
> identify an effective AOA for beamforming. However, the antenna system
> does not need to estimate AOA if the pattern adaptation objective
> function is the maximization of SIR (Signal to Interference Ratio). Some
> of the proposed ideas (like DNAV) can be adapted to support these kinds
> of adaptive antenna systems.

I am not sure I totally understand what you mean here. I am guessing that
whay you mean is that the antenna should beamform towards the strongest
component (among all the multipath components) - which obviously maximizes
the SIR (right?). However this still requires one to select the direction
of strongest component and beamform towrads it etc etc....or am i totally
out of tune with what you said ?

-Vikram


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


From mailnull@www1.ietf.org  Thu Nov 14 12:59:07 2002
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA25602
	for <manet-archive@odin.ietf.org>; Thu, 14 Nov 2002 12:59:07 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id gAEI1Gx12432
	for manet-archive@odin.ietf.org; Thu, 14 Nov 2002 13:01:16 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gAEI1Gv12429
	for <manet-web-archive@optimus.ietf.org>; Thu, 14 Nov 2002 13:01:16 -0500
Received: from www1.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA25581
	for <manet-web-archive@ietf.org>; Thu, 14 Nov 2002 12:58:36 -0500 (EST)
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gAEHdmv11605;
	Thu, 14 Nov 2002 12:39:48 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gAEHTVv10722
	for <manet@optimus.ietf.org>; Thu, 14 Nov 2002 12:29:31 -0500
Received: from ece.rice.edu (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA24900
	for <manet@ietf.org>; Thu, 14 Nov 2002 12:26:52 -0500 (EST)
Received: from localhost (localhost [127.0.0.1])
	by ece.rice.edu (Postfix) with SMTP
	id 9777868A78; Thu, 14 Nov 2002 11:29:23 -0600 (CST)
Received: from localhost (localhost [127.0.0.1])
	by ece.rice.edu (Postfix) with ESMTP
	id 2077668A76; Thu, 14 Nov 2002 11:29:23 -0600 (CST)
Received: from egress.ece.rice.edu (egress.ece.rice.edu [128.42.12.74])
	by ece.rice.edu (Postfix) with ESMTP
	id 3547D68A75; Thu, 14 Nov 2002 11:29:22 -0600 (CST)
Received: from localhost (kanodia@localhost)
	by egress.ece.rice.edu (8.9.3/8.9.3) with ESMTP id LAA05343;
	Thu, 14 Nov 2002 11:29:22 -0600
X-Authentication-Warning: egress.ece.rice.edu: kanodia owned process doing -bs
Date: Thu, 14 Nov 2002 11:29:22 -0600 (CST)
From: Vikram Kanodia <kanodia@rice.edu>
X-Sender: kanodia@egress.ece.rice.edu
To: Mineo Takai <mineo@cs.ucla.edu>
Cc: manet@ietf.org
Subject: Re: [manet] directional antennae
In-Reply-To: <3DD1D849.B15DA755@cs.ucla.edu>
Message-ID: <Pine.LNX.4.21.0211131636110.13137-100000@egress.ece.rice.edu>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
X-Virus-Scanned: by AMaViS snapshot-20020300
X-DCC--Metrics: ece.rice.edu 1066; Body=1 Fuz1=1 Fuz2=1
Sender: manet-admin@ietf.org
Errors-To: manet-admin@ietf.org
X-BeenThere: manet@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/manet>,
	<mailto:manet-request@ietf.org?subject=unsubscribe>
List-Id: Mobile Ad-hoc Networks  <manet.ietf.org>
List-Post: <mailto:manet@ietf.org>
List-Help: <mailto:manet-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/manet>,
	<mailto:manet-request@ietf.org?subject=subscribe>


Mineo,

> 
> (I would use "antennas" rather than "antennae" for wireless
> communications.)

whoops ...I did not realize that antennas was the correct plural
here...live and learn, I guess :)

> If AOAs of multipath components are equally spread over 360 degrees, and
> no ray is significantly stronger than the others, it is difficult to
> identify an effective AOA for beamforming. However, the antenna system
> does not need to estimate AOA if the pattern adaptation objective
> function is the maximization of SIR (Signal to Interference Ratio). Some
> of the proposed ideas (like DNAV) can be adapted to support these kinds
> of adaptive antenna systems.

I am not sure I totally understand what you mean here. I am guessing that
whay you mean is that the antenna should beamform towards the strongest
component (among all the multipath components) - which obviously maximizes
the SIR (right?). However this still requires one to select the direction
of strongest component and beamform towrads it etc etc....or am i totally
out of tune with what you said ?

-Vikram


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



From mailnull@www1.ietf.org  Thu Nov 14 15:58:16 2002
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA00600
	for <manet-archive@odin.ietf.org>; Thu, 14 Nov 2002 15:58:16 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id gAEL0P924463
	for manet-archive@odin.ietf.org; Thu, 14 Nov 2002 16:00:25 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gAEL0Pv24460
	for <manet-web-archive@optimus.ietf.org>; Thu, 14 Nov 2002 16:00:25 -0500
Received: from www1.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA00576
	for <manet-web-archive@ietf.org>; Thu, 14 Nov 2002 15:57:45 -0500 (EST)
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gAEKnAv23923;
	Thu, 14 Nov 2002 15:49:10 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gAEKgqv23777
	for <manet@optimus.ietf.org>; Thu, 14 Nov 2002 15:42:52 -0500
Received: from zrtps0kp.nortelnetworks.com (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA00158
	for <manet@ietf.org>; Thu, 14 Nov 2002 15:40:13 -0500 (EST)
Received: from zrtpd0j7.us.nortel.com (zrtpd0j7.us.nortel.com [47.140.203.25])
	by zrtps0kp.nortelnetworks.com (Switch-2.2.0/Switch-2.2.0) with ESMTP id gAEKgjv10989
	for <manet@ietf.org>; Thu, 14 Nov 2002 15:42:45 -0500 (EST)
Received: from zrtpd0j9.us.nortel.com ([47.140.203.27]) by zrtpd0j7.us.nortel.com with SMTP (Microsoft Exchange Internet Mail Service Version 5.5.2653.13)
	id VLB0VJR9; Thu, 14 Nov 2002 15:42:46 -0500
Received: from americasm01.nt.com (wnc1h04q.us.nortel.com [47.142.211.72]) by zrtpd0j9.us.nortel.com with SMTP (Microsoft Exchange Internet Mail Service Version 5.5.2653.13)
	id TL2NF727; Thu, 14 Nov 2002 15:42:45 -0500
Message-ID: <3DD40AC4.E7C8CBE2@americasm01.nt.com>
Date: Thu, 14 Nov 2002 15:42:44 -0500
From: "He Huang" <huanghe@nortelnetworks.com>
Organization: Nortel Networks
X-Mailer: Mozilla 4.72 [en] (X11; I; HP-UX B.10.20 9000/785)
X-Accept-Language: en
MIME-Version: 1.0
To: manet@ietf.org
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit
Subject: [manet] Protocol Correctness and Complexity
Sender: manet-admin@ietf.org
Errors-To: manet-admin@ietf.org
X-BeenThere: manet@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/manet>,
	<mailto:manet-request@ietf.org?subject=unsubscribe>
List-Id: Mobile Ad-hoc Networks  <manet.ietf.org>
List-Post: <mailto:manet@ietf.org>
List-Help: <mailto:manet-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/manet>,
	<mailto:manet-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit

Hello,

I'm looking for the papers or resources  on analyzing protocol
correctness and complexity, especially for MANET protocols.
I'd appreciate if you could provide me some information. Thanks in
advance,

He Huang



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



From manet-admin@ietf.org  Thu Nov 14 15:58:41 2002
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA00617
	for <manet-archive@lists.ietf.org>; Thu, 14 Nov 2002 15:58:41 -0500 (EST)
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gAEKnAv23923;
	Thu, 14 Nov 2002 15:49:10 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gAEKgqv23777
	for <manet@optimus.ietf.org>; Thu, 14 Nov 2002 15:42:52 -0500
Received: from zrtps0kp.nortelnetworks.com (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA00158
	for <manet@ietf.org>; Thu, 14 Nov 2002 15:40:13 -0500 (EST)
Received: from zrtpd0j7.us.nortel.com (zrtpd0j7.us.nortel.com [47.140.203.25])
	by zrtps0kp.nortelnetworks.com (Switch-2.2.0/Switch-2.2.0) with ESMTP id gAEKgjv10989
	for <manet@ietf.org>; Thu, 14 Nov 2002 15:42:45 -0500 (EST)
Received: from zrtpd0j9.us.nortel.com ([47.140.203.27]) by zrtpd0j7.us.nortel.com with SMTP (Microsoft Exchange Internet Mail Service Version 5.5.2653.13)
	id VLB0VJR9; Thu, 14 Nov 2002 15:42:46 -0500
Received: from americasm01.nt.com (wnc1h04q.us.nortel.com [47.142.211.72]) by zrtpd0j9.us.nortel.com with SMTP (Microsoft Exchange Internet Mail Service Version 5.5.2653.13)
	id TL2NF727; Thu, 14 Nov 2002 15:42:45 -0500
Message-ID: <3DD40AC4.E7C8CBE2@americasm01.nt.com>
Date: Thu, 14 Nov 2002 15:42:44 -0500
From: "He Huang" <huanghe@nortelnetworks.com>
Organization: Nortel Networks
X-Mailer: Mozilla 4.72 [en] (X11; I; HP-UX B.10.20 9000/785)
X-Accept-Language: en
MIME-Version: 1.0
To: manet@ietf.org
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit
Subject: [manet] Protocol Correctness and Complexity
Sender: manet-admin@ietf.org
Errors-To: manet-admin@ietf.org
X-BeenThere: manet@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/manet>,
	<mailto:manet-request@ietf.org?subject=unsubscribe>
List-Id: Mobile Ad-hoc Networks  <manet.ietf.org>
List-Post: <mailto:manet@ietf.org>
List-Help: <mailto:manet-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/manet>,
	<mailto:manet-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 7bit

Hello,

I'm looking for the papers or resources  on analyzing protocol
correctness and complexity, especially for MANET protocols.
I'd appreciate if you could provide me some information. Thanks in
advance,

He Huang



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


From manet-admin@ietf.org  Thu Nov 14 19:36:40 2002
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA10486
	for <manet-archive@lists.ietf.org>; Thu, 14 Nov 2002 19:36:40 -0500 (EST)
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gAF0V5v04035;
	Thu, 14 Nov 2002 19:31:05 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gAF0O1v03812
	for <manet@optimus.ietf.org>; Thu, 14 Nov 2002 19:24:01 -0500
Received: from memphis.ece.cornell.edu (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA09942
	for <manet@ietf.org>; Thu, 14 Nov 2002 19:21:19 -0500 (EST)
From: haas@ece.cornell.edu
Received: from verdi.ece.cornell.edu (verdi.ece.cornell.edu [128.84.210.27])
	by memphis.ece.cornell.edu (8.11.6/8.11.2) with ESMTP id gAF0NoX03403;
	Thu, 14 Nov 2002 19:23:50 -0500
Date: Thu, 14 Nov 2002 19:23:33 -0500 (EST)
To: He Huang <huanghe@nortelnetworks.com>
cc: manet@ietf.org
Subject: Re: [manet] Protocol Correctness and Complexity
In-Reply-To: <3DD40AC4.E7C8CBE2@americasm01.nt.com>
Message-ID: <Pine.GSO.4.05.10211141912040.27664-100000@verdi.ece.cornell.edu>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: manet-admin@ietf.org
Errors-To: manet-admin@ietf.org
X-BeenThere: manet@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/manet>,
	<mailto:manet-request@ietf.org?subject=unsubscribe>
List-Id: Mobile Ad-hoc Networks  <manet.ietf.org>
List-Post: <mailto:manet@ietf.org>
List-Help: <mailto:manet-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/manet>,
	<mailto:manet-request@ietf.org?subject=subscribe>

Hi He,

For correctness proof of ZRP, please e-mail Marc Pearlman
<pearlman@ece.cornell.edu> . The proof is part of his thesis, but
I do not recall whether it was published anywhere else.

Best,

Zygmunt.
===--==-==
~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-
Prof. Zygmunt J. Haas                    http://people.ece.cornell.edu/haas 
Wireless Networks Laboratory		 http://wnl.ece.cornell.edu
School of Electrical Engineering         
Cornell University			 tel: +1-607-255-3454
323 Frank Rhodes Hall			 fax: +1-607-255-9072
Ithaca, NY 14853			 e-mail: haas@ece.cornell.edu
U.S.A                             
	WNL web page: http://wnl.ece.cornell.edu
~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-

On Thu, 14 Nov 2002, He Huang wrote:

> Hello,
> 
> I'm looking for the papers or resources  on analyzing protocol
> correctness and complexity, especially for MANET protocols.
> I'd appreciate if you could provide me some information. Thanks in
> advance,
> 
> He Huang
> 
> 
> 
> _______________________________________________
> manet mailing list
> manet@ietf.org
> https://www1.ietf.org/mailman/listinfo/manet
> 

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


From mailnull@www1.ietf.org  Thu Nov 14 19:46:33 2002
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA10824
	for <manet-archive@odin.ietf.org>; Thu, 14 Nov 2002 19:46:33 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id gAF0mjj05585
	for manet-archive@odin.ietf.org; Thu, 14 Nov 2002 19:48:45 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gAF0mjv05582
	for <manet-web-archive@optimus.ietf.org>; Thu, 14 Nov 2002 19:48:45 -0500
Received: from www1.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA10807
	for <manet-web-archive@ietf.org>; Thu, 14 Nov 2002 19:46:02 -0500 (EST)
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gAF0V5v04035;
	Thu, 14 Nov 2002 19:31:05 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gAF0O1v03812
	for <manet@optimus.ietf.org>; Thu, 14 Nov 2002 19:24:01 -0500
Received: from memphis.ece.cornell.edu (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA09942
	for <manet@ietf.org>; Thu, 14 Nov 2002 19:21:19 -0500 (EST)
From: haas@ece.cornell.edu
Received: from verdi.ece.cornell.edu (verdi.ece.cornell.edu [128.84.210.27])
	by memphis.ece.cornell.edu (8.11.6/8.11.2) with ESMTP id gAF0NoX03403;
	Thu, 14 Nov 2002 19:23:50 -0500
Date: Thu, 14 Nov 2002 19:23:33 -0500 (EST)
To: He Huang <huanghe@nortelnetworks.com>
cc: manet@ietf.org
Subject: Re: [manet] Protocol Correctness and Complexity
In-Reply-To: <3DD40AC4.E7C8CBE2@americasm01.nt.com>
Message-ID: <Pine.GSO.4.05.10211141912040.27664-100000@verdi.ece.cornell.edu>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: manet-admin@ietf.org
Errors-To: manet-admin@ietf.org
X-BeenThere: manet@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/manet>,
	<mailto:manet-request@ietf.org?subject=unsubscribe>
List-Id: Mobile Ad-hoc Networks  <manet.ietf.org>
List-Post: <mailto:manet@ietf.org>
List-Help: <mailto:manet-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/manet>,
	<mailto:manet-request@ietf.org?subject=subscribe>

Hi He,

For correctness proof of ZRP, please e-mail Marc Pearlman
<pearlman@ece.cornell.edu> . The proof is part of his thesis, but
I do not recall whether it was published anywhere else.

Best,

Zygmunt.
===--==-==
~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-
Prof. Zygmunt J. Haas                    http://people.ece.cornell.edu/haas 
Wireless Networks Laboratory		 http://wnl.ece.cornell.edu
School of Electrical Engineering         
Cornell University			 tel: +1-607-255-3454
323 Frank Rhodes Hall			 fax: +1-607-255-9072
Ithaca, NY 14853			 e-mail: haas@ece.cornell.edu
U.S.A                             
	WNL web page: http://wnl.ece.cornell.edu
~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-

On Thu, 14 Nov 2002, He Huang wrote:

> Hello,
> 
> I'm looking for the papers or resources  on analyzing protocol
> correctness and complexity, especially for MANET protocols.
> I'd appreciate if you could provide me some information. Thanks in
> advance,
> 
> He Huang
> 
> 
> 
> _______________________________________________
> manet mailing list
> manet@ietf.org
> https://www1.ietf.org/mailman/listinfo/manet
> 

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



From mailnull@www1.ietf.org  Fri Nov 15 00:14:11 2002
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id AAA18881
	for <manet-archive@odin.ietf.org>; Fri, 15 Nov 2002 00:14:11 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id gAF5GOl21093
	for manet-archive@odin.ietf.org; Fri, 15 Nov 2002 00:16:24 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gAF5GOv21090
	for <manet-web-archive@optimus.ietf.org>; Fri, 15 Nov 2002 00:16:24 -0500
Received: from www1.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id AAA18868
	for <manet-web-archive@ietf.org>; Fri, 15 Nov 2002 00:13:40 -0500 (EST)
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gAF58Tv20743;
	Fri, 15 Nov 2002 00:08:29 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gAF51Fv19962
	for <manet@optimus.ietf.org>; Fri, 15 Nov 2002 00:01:15 -0500
Received: from relay1.san1.aens.net (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id XAA18459
	for <manet@ietf.org>; Thu, 14 Nov 2002 23:58:30 -0500 (EST)
Received: from cs.ucla.edu (2005host231.starwoodbroadband.com [12.160.3.231])
	by relay1.san1.aens.net (8.11.6/8.9.3) with ESMTP id gAF53Rt21084;
	Fri, 15 Nov 2002 05:03:27 GMT
Message-ID: <3DD47F79.89D68B1D@cs.ucla.edu>
Date: Thu, 14 Nov 2002 21:00:42 -0800
From: Mineo Takai <mineo@cs.ucla.edu>
X-Mailer: Mozilla 4.79 [en] (Windows NT 5.0; U)
X-Accept-Language: en
MIME-Version: 1.0
To: Vikram Kanodia <kanodia@rice.edu>
CC: manet@ietf.org
Subject: Re: [manet] directional antennae
References: <Pine.LNX.4.21.0211131636110.13137-100000@egress.ece.rice.edu>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit
Sender: manet-admin@ietf.org
Errors-To: manet-admin@ietf.org
X-BeenThere: manet@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/manet>,
	<mailto:manet-request@ietf.org?subject=unsubscribe>
List-Id: Mobile Ad-hoc Networks  <manet.ietf.org>
List-Post: <mailto:manet@ietf.org>
List-Help: <mailto:manet-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/manet>,
	<mailto:manet-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit

Vikram:

Beamforming towards the strongest multipath (or LOS) component does not always
maximize SIR. It would probably maximize (S)ignal power, but you may be
increasing (I)nterference power at the same time (e.g., a strong interfering
signal coming from the same direction).

Since your original question was about the AOA estimation, I wanted to mention
beam adaptation algorithms called "blind" that do not estimate AOA of the
desired signal for beamforming. It adapts the beam pattern to maximize SIR
rather than estimating AOA and beamforming towards the estimated direction,
because the reception quality is ultimately determined by SIR. Blind algorithms
may end up creating the same patterns as other non-blind algorithms, but again,
they do not estimate AOA for beamforming.

Mineo

Vikram Kanodia wrote:
> 
> Mineo,
> 
> > If AOAs of multipath components are equally spread over 360 degrees, and
> > no ray is significantly stronger than the others, it is difficult to
> > identify an effective AOA for beamforming. However, the antenna system
> > does not need to estimate AOA if the pattern adaptation objective
> > function is the maximization of SIR (Signal to Interference Ratio). Some
> > of the proposed ideas (like DNAV) can be adapted to support these kinds
> > of adaptive antenna systems.
> 
> I am not sure I totally understand what you mean here. I am guessing that
> whay you mean is that the antenna should beamform towards the strongest
> component (among all the multipath components) - which obviously maximizes
> the SIR (right?). However this still requires one to select the direction
> of strongest component and beamform towrads it etc etc....or am i totally
> out of tune with what you said ?
> 
> -Vikram
> 
> _______________________________________________
> manet mailing list
> manet@ietf.org
> https://www1.ietf.org/mailman/listinfo/manet
_______________________________________________
manet mailing list
manet@ietf.org
https://www1.ietf.org/mailman/listinfo/manet



From manet-admin@ietf.org  Fri Nov 15 00:14:38 2002
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id AAA18894
	for <manet-archive@lists.ietf.org>; Fri, 15 Nov 2002 00:14:38 -0500 (EST)
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gAF58Tv20743;
	Fri, 15 Nov 2002 00:08:29 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gAF51Fv19962
	for <manet@optimus.ietf.org>; Fri, 15 Nov 2002 00:01:15 -0500
Received: from relay1.san1.aens.net (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id XAA18459
	for <manet@ietf.org>; Thu, 14 Nov 2002 23:58:30 -0500 (EST)
Received: from cs.ucla.edu (2005host231.starwoodbroadband.com [12.160.3.231])
	by relay1.san1.aens.net (8.11.6/8.9.3) with ESMTP id gAF53Rt21084;
	Fri, 15 Nov 2002 05:03:27 GMT
Message-ID: <3DD47F79.89D68B1D@cs.ucla.edu>
Date: Thu, 14 Nov 2002 21:00:42 -0800
From: Mineo Takai <mineo@cs.ucla.edu>
X-Mailer: Mozilla 4.79 [en] (Windows NT 5.0; U)
X-Accept-Language: en
MIME-Version: 1.0
To: Vikram Kanodia <kanodia@rice.edu>
CC: manet@ietf.org
Subject: Re: [manet] directional antennae
References: <Pine.LNX.4.21.0211131636110.13137-100000@egress.ece.rice.edu>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit
Sender: manet-admin@ietf.org
Errors-To: manet-admin@ietf.org
X-BeenThere: manet@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/manet>,
	<mailto:manet-request@ietf.org?subject=unsubscribe>
List-Id: Mobile Ad-hoc Networks  <manet.ietf.org>
List-Post: <mailto:manet@ietf.org>
List-Help: <mailto:manet-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/manet>,
	<mailto:manet-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 7bit

Vikram:

Beamforming towards the strongest multipath (or LOS) component does not always
maximize SIR. It would probably maximize (S)ignal power, but you may be
increasing (I)nterference power at the same time (e.g., a strong interfering
signal coming from the same direction).

Since your original question was about the AOA estimation, I wanted to mention
beam adaptation algorithms called "blind" that do not estimate AOA of the
desired signal for beamforming. It adapts the beam pattern to maximize SIR
rather than estimating AOA and beamforming towards the estimated direction,
because the reception quality is ultimately determined by SIR. Blind algorithms
may end up creating the same patterns as other non-blind algorithms, but again,
they do not estimate AOA for beamforming.

Mineo

Vikram Kanodia wrote:
> 
> Mineo,
> 
> > If AOAs of multipath components are equally spread over 360 degrees, and
> > no ray is significantly stronger than the others, it is difficult to
> > identify an effective AOA for beamforming. However, the antenna system
> > does not need to estimate AOA if the pattern adaptation objective
> > function is the maximization of SIR (Signal to Interference Ratio). Some
> > of the proposed ideas (like DNAV) can be adapted to support these kinds
> > of adaptive antenna systems.
> 
> I am not sure I totally understand what you mean here. I am guessing that
> whay you mean is that the antenna should beamform towards the strongest
> component (among all the multipath components) - which obviously maximizes
> the SIR (right?). However this still requires one to select the direction
> of strongest component and beamform towrads it etc etc....or am i totally
> out of tune with what you said ?
> 
> -Vikram
> 
> _______________________________________________
> manet mailing list
> manet@ietf.org
> https://www1.ietf.org/mailman/listinfo/manet
_______________________________________________
manet mailing list
manet@ietf.org
https://www1.ietf.org/mailman/listinfo/manet


From manet-admin@ietf.org  Fri Nov 15 01:54:48 2002
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id BAA21243
	for <manet-archive@lists.ietf.org>; Fri, 15 Nov 2002 01:54:47 -0500 (EST)
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gAF6ljv25227;
	Fri, 15 Nov 2002 01:47:45 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gAF6hwv25122
	for <manet@optimus.ietf.org>; Fri, 15 Nov 2002 01:43:58 -0500
Received: from web11102.mail.yahoo.com (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id BAA20985
	for <manet@ietf.org>; Fri, 15 Nov 2002 01:41:12 -0500 (EST)
Message-ID: <20021115064347.87998.qmail@web11102.mail.yahoo.com>
Received: from [128.32.43.36] by web11102.mail.yahoo.com via HTTP; Thu, 14 Nov 2002 22:43:47 PST
Date: Thu, 14 Nov 2002 22:43:47 -0800 (PST)
From: Wei Wei <derekwei77@yahoo.com>
To: qi.fan@kcl.ac.uk
Cc: manet@ietf.org
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Subject: [manet] Re: Fw Help
Sender: manet-admin@ietf.org
Errors-To: manet-admin@ietf.org
X-BeenThere: manet@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/manet>,
	<mailto:manet-request@ietf.org?subject=unsubscribe>
List-Id: Mobile Ad-hoc Networks  <manet.ietf.org>
List-Post: <mailto:manet@ietf.org>
List-Help: <mailto:manet-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/manet>,
	<mailto:manet-request@ietf.org?subject=subscribe>

Hi Qi,

There are bunch of NS sources in the net. You can 
begin with http://nile.wpi.edu/NS/.

Good luck,

Wei

__________________________________________________
Do you Yahoo!?
Yahoo! Web Hosting - Let the expert host your site
http://webhosting.yahoo.com
_______________________________________________
manet mailing list
manet@ietf.org
https://www1.ietf.org/mailman/listinfo/manet


From mailnull@www1.ietf.org  Fri Nov 15 02:02:10 2002
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id CAA22977
	for <manet-archive@odin.ietf.org>; Fri, 15 Nov 2002 02:02:10 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id gAF74P526567
	for manet-archive@odin.ietf.org; Fri, 15 Nov 2002 02:04:25 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gAF74Ov26564
	for <manet-web-archive@optimus.ietf.org>; Fri, 15 Nov 2002 02:04:24 -0500
Received: from www1.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id CAA22582
	for <manet-web-archive@ietf.org>; Fri, 15 Nov 2002 02:01:38 -0500 (EST)
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gAF6ljv25227;
	Fri, 15 Nov 2002 01:47:45 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gAF6hwv25122
	for <manet@optimus.ietf.org>; Fri, 15 Nov 2002 01:43:58 -0500
Received: from web11102.mail.yahoo.com (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id BAA20985
	for <manet@ietf.org>; Fri, 15 Nov 2002 01:41:12 -0500 (EST)
Message-ID: <20021115064347.87998.qmail@web11102.mail.yahoo.com>
Received: from [128.32.43.36] by web11102.mail.yahoo.com via HTTP; Thu, 14 Nov 2002 22:43:47 PST
Date: Thu, 14 Nov 2002 22:43:47 -0800 (PST)
From: Wei Wei <derekwei77@yahoo.com>
To: qi.fan@kcl.ac.uk
Cc: manet@ietf.org
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Subject: [manet] Re: Fw Help
Sender: manet-admin@ietf.org
Errors-To: manet-admin@ietf.org
X-BeenThere: manet@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/manet>,
	<mailto:manet-request@ietf.org?subject=unsubscribe>
List-Id: Mobile Ad-hoc Networks  <manet.ietf.org>
List-Post: <mailto:manet@ietf.org>
List-Help: <mailto:manet-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/manet>,
	<mailto:manet-request@ietf.org?subject=subscribe>

Hi Qi,

There are bunch of NS sources in the net. You can 
begin with http://nile.wpi.edu/NS/.

Good luck,

Wei

__________________________________________________
Do you Yahoo!?
Yahoo! Web Hosting - Let the expert host your site
http://webhosting.yahoo.com
_______________________________________________
manet mailing list
manet@ietf.org
https://www1.ietf.org/mailman/listinfo/manet



From manet-admin@ietf.org  Fri Nov 15 08:44:40 2002
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA08079
	for <manet-archive@lists.ietf.org>; Fri, 15 Nov 2002 08:44:40 -0500 (EST)
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gAFDd9v23731;
	Fri, 15 Nov 2002 08:39:09 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gAFDT8v22892
	for <manet@optimus.ietf.org>; Fri, 15 Nov 2002 08:29:08 -0500
Received: from memphis.ece.cornell.edu (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA07716
	for <manet@ietf.org>; Fri, 15 Nov 2002 08:26:29 -0500 (EST)
From: haas@ece.cornell.edu
Received: from verdi.ece.cornell.edu (verdi.ece.cornell.edu [128.84.210.27])
	by memphis.ece.cornell.edu (8.11.6/8.11.2) with ESMTP id gAFDT5X16738
	for <manet@ietf.org>; Fri, 15 Nov 2002 08:29:05 -0500
Date: Fri, 15 Nov 2002 08:28:46 -0500 (EST)
To: manet@ietf.org
Subject: RE: [manet] Protocol Correctness and Complexity
Message-ID: <Pine.GSO.4.05.10211150826170.28060-100000@verdi.ece.cornell.edu>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: manet-admin@ietf.org
Errors-To: manet-admin@ietf.org
X-BeenThere: manet@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/manet>,
	<mailto:manet-request@ietf.org?subject=unsubscribe>
List-Id: Mobile Ad-hoc Networks  <manet.ietf.org>
List-Post: <mailto:manet@ietf.org>
List-Help: <mailto:manet-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/manet>,
	<mailto:manet-request@ietf.org?subject=subscribe>

Hi He,

Regarding my previous message on ZRP correctness proof - I stand corrected
(;-) ... the ZRP correctness proof was published in "Ad Hoc Networking" 
by Charlie Perkins, editor, Addison-Wesley, 2000.

Best,

Zygmunt.
==--==-=-=
~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-
Prof. Zygmunt J. Haas                    http://people.ece.cornell.edu/haas 
Wireless Networks Laboratory		 http://wnl.ece.cornell.edu
School of Electrical Engineering         
Cornell University			 tel: +1-607-255-3454
323 Frank Rhodes Hall			 fax: +1-607-255-9072
Ithaca, NY 14853			 e-mail: haas@ece.cornell.edu
U.S.A                             
	WNL web page: http://wnl.ece.cornell.edu
~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-

-----Original Message-----
From: manet-admin@ietf.org [mailto:manet-admin@ietf.org] On Behalf Of
haas@ece.cornell.edu
Sent: Thursday, November 14, 2002 7:24 PM
To: He Huang
Cc: manet@ietf.org
Subject: Re: [manet] Protocol Correctness and Complexity


Hi He,

For correctness proof of ZRP, please e-mail Marc Pearlman
<pearlman@ece.cornell.edu> . The proof is part of his thesis, but I do
not recall whether it was published anywhere else.

Best,

Zygmunt.
===--==-==
~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-
~-
Prof. Zygmunt J. Haas
http://people.ece.cornell.edu/haas 
Wireless Networks Laboratory		 http://wnl.ece.cornell.edu
School of Electrical Engineering         
Cornell University			 tel: +1-607-255-3454
323 Frank Rhodes Hall			 fax: +1-607-255-9072
Ithaca, NY 14853			 e-mail: haas@ece.cornell.edu
U.S.A                             
	WNL web page: http://wnl.ece.cornell.edu
~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-
~-

On Thu, 14 Nov 2002, He Huang wrote:

> Hello,
> 
> I'm looking for the papers or resources  on analyzing protocol 
> correctness and complexity, especially for MANET protocols. I'd 
> appreciate if you could provide me some information. Thanks in 
> advance,
> 
> He Huang
> 
> 
> 
> _______________________________________________
> manet mailing list
> manet@ietf.org
> https://www1.ietf.org/mailman/listinfo/manet
> 

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

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


From mailnull@www1.ietf.org  Fri Nov 15 08:50:58 2002
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA08225
	for <manet-archive@odin.ietf.org>; Fri, 15 Nov 2002 08:50:58 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id gAFDr6k24194
	for manet-archive@odin.ietf.org; Fri, 15 Nov 2002 08:53:06 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gAFDr6v24191
	for <manet-web-archive@optimus.ietf.org>; Fri, 15 Nov 2002 08:53:06 -0500
Received: from www1.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA08210
	for <manet-web-archive@ietf.org>; Fri, 15 Nov 2002 08:50:26 -0500 (EST)
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gAFDd9v23731;
	Fri, 15 Nov 2002 08:39:09 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gAFDT8v22892
	for <manet@optimus.ietf.org>; Fri, 15 Nov 2002 08:29:08 -0500
Received: from memphis.ece.cornell.edu (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA07716
	for <manet@ietf.org>; Fri, 15 Nov 2002 08:26:29 -0500 (EST)
From: haas@ece.cornell.edu
Received: from verdi.ece.cornell.edu (verdi.ece.cornell.edu [128.84.210.27])
	by memphis.ece.cornell.edu (8.11.6/8.11.2) with ESMTP id gAFDT5X16738
	for <manet@ietf.org>; Fri, 15 Nov 2002 08:29:05 -0500
Date: Fri, 15 Nov 2002 08:28:46 -0500 (EST)
To: manet@ietf.org
Subject: RE: [manet] Protocol Correctness and Complexity
Message-ID: <Pine.GSO.4.05.10211150826170.28060-100000@verdi.ece.cornell.edu>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: manet-admin@ietf.org
Errors-To: manet-admin@ietf.org
X-BeenThere: manet@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/manet>,
	<mailto:manet-request@ietf.org?subject=unsubscribe>
List-Id: Mobile Ad-hoc Networks  <manet.ietf.org>
List-Post: <mailto:manet@ietf.org>
List-Help: <mailto:manet-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/manet>,
	<mailto:manet-request@ietf.org?subject=subscribe>

Hi He,

Regarding my previous message on ZRP correctness proof - I stand corrected
(;-) ... the ZRP correctness proof was published in "Ad Hoc Networking" 
by Charlie Perkins, editor, Addison-Wesley, 2000.

Best,

Zygmunt.
==--==-=-=
~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-
Prof. Zygmunt J. Haas                    http://people.ece.cornell.edu/haas 
Wireless Networks Laboratory		 http://wnl.ece.cornell.edu
School of Electrical Engineering         
Cornell University			 tel: +1-607-255-3454
323 Frank Rhodes Hall			 fax: +1-607-255-9072
Ithaca, NY 14853			 e-mail: haas@ece.cornell.edu
U.S.A                             
	WNL web page: http://wnl.ece.cornell.edu
~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-

-----Original Message-----
From: manet-admin@ietf.org [mailto:manet-admin@ietf.org] On Behalf Of
haas@ece.cornell.edu
Sent: Thursday, November 14, 2002 7:24 PM
To: He Huang
Cc: manet@ietf.org
Subject: Re: [manet] Protocol Correctness and Complexity


Hi He,

For correctness proof of ZRP, please e-mail Marc Pearlman
<pearlman@ece.cornell.edu> . The proof is part of his thesis, but I do
not recall whether it was published anywhere else.

Best,

Zygmunt.
===--==-==
~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-
~-
Prof. Zygmunt J. Haas
http://people.ece.cornell.edu/haas 
Wireless Networks Laboratory		 http://wnl.ece.cornell.edu
School of Electrical Engineering         
Cornell University			 tel: +1-607-255-3454
323 Frank Rhodes Hall			 fax: +1-607-255-9072
Ithaca, NY 14853			 e-mail: haas@ece.cornell.edu
U.S.A                             
	WNL web page: http://wnl.ece.cornell.edu
~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-
~-

On Thu, 14 Nov 2002, He Huang wrote:

> Hello,
> 
> I'm looking for the papers or resources  on analyzing protocol 
> correctness and complexity, especially for MANET protocols. I'd 
> appreciate if you could provide me some information. Thanks in 
> advance,
> 
> He Huang
> 
> 
> 
> _______________________________________________
> manet mailing list
> manet@ietf.org
> https://www1.ietf.org/mailman/listinfo/manet
> 

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

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



From manet-admin@ietf.org  Fri Nov 15 16:16:37 2002
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA19406
	for <manet-archive@lists.ietf.org>; Fri, 15 Nov 2002 16:16:36 -0500 (EST)
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gAFL2Jv15919;
	Fri, 15 Nov 2002 16:02:19 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gA84tIv15841
	for <manet@optimus.ietf.org>; Thu, 7 Nov 2002 23:55:18 -0500
Received: from lennier.cc.vt.edu (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id XAA25311
	for <manet@ietf.org>; Thu, 7 Nov 2002 23:52:40 -0500 (EST)
Received: from steiner.cc.vt.edu (IDENT:mirapoint@steiner-lb.cc.vt.edu [10.1.1.14])
	by lennier.cc.vt.edu (8.11.4/8.11.4) with ESMTP id gA84t8c282023;
	Thu, 7 Nov 2002 23:55:08 -0500 (EST)
Received: from zathras (zathras.cc.vt.edu [198.82.162.117])
	by steiner.cc.vt.edu (Mirapoint Messaging Server MOS 3.2.1-GA)
	with ESMTP id ARZ93956;
	Thu, 7 Nov 2002 23:55:07 -0500 (EST)
X-WebMail-UserID:  talin
Date: Thu, 7 Nov 2002 23:55:07 -0500
From: Tao Lin <talin@vt.edu>
To: Harry <hr_befine@263.net>, MANET mail list <manet@ietf.org>
X-EXP32-SerialNo: 00002964
Subject: RE: [manet] Emulate MANET
Message-ID: <3DCBE9F0@zathras>
Mime-Version: 1.0
Content-Type: text/plain; charset="ISO-8859-1"
X-Mailer: WebMail (Hydra) SMTP v3.61.08
Content-Transfer-Encoding: 8bit
X-MIME-Autoconverted: from quoted-printable to 8bit by www1.ietf.org id gA84tPv15845
Sender: manet-admin@ietf.org
Errors-To: manet-admin@ietf.org
X-BeenThere: manet@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/manet>,
	<mailto:manet-request@ietf.org?subject=unsubscribe>
List-Id: Mobile Ad-hoc Networks  <manet.ietf.org>
List-Post: <mailto:manet@ietf.org>
List-Help: <mailto:manet-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/manet>,
	<mailto:manet-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 8bit

We developed a free tool and a corresponding paper at:
io.irean.vt.edu/~tlin
It has over 197 downloads till now.

It is simple a easy tool to emulate MANET in wired testbed without any
modification at mobile nodes.


>===== Original Message From Harry <hr_befine@263.net> =====
>hi,allŁˇ
>	I want to emulate MANET in a wired network environment. Who could recommend 
some softwares to me? I konw NS2 do. Are there anything else?
>	Thank u in advance.
>
>
>best regards
>ˇˇˇˇˇˇˇˇˇˇˇˇˇˇˇˇHarry
>ˇˇˇˇˇˇˇˇˇˇˇˇˇˇˇˇˇˇˇˇ2002-11-08
>
>
>_______________________________________________
>manet mailing list
>manet@ietf.org
>https://www1.ietf.org/mailman/listinfo/manet

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


From mailnull@www1.ietf.org  Fri Nov 15 16:23:18 2002
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA19623
	for <manet-archive@odin.ietf.org>; Fri, 15 Nov 2002 16:23:18 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id gAFLPSL17378
	for manet-archive@odin.ietf.org; Fri, 15 Nov 2002 16:25:28 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gAFLPSv17375
	for <manet-web-archive@optimus.ietf.org>; Fri, 15 Nov 2002 16:25:28 -0500
Received: from www1.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA19605
	for <manet-web-archive@ietf.org>; Fri, 15 Nov 2002 16:22:32 -0500 (EST)
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gAFL2Jv15919;
	Fri, 15 Nov 2002 16:02:19 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gA84tIv15841
	for <manet@optimus.ietf.org>; Thu, 7 Nov 2002 23:55:18 -0500
Received: from lennier.cc.vt.edu (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id XAA25311
	for <manet@ietf.org>; Thu, 7 Nov 2002 23:52:40 -0500 (EST)
Received: from steiner.cc.vt.edu (IDENT:mirapoint@steiner-lb.cc.vt.edu [10.1.1.14])
	by lennier.cc.vt.edu (8.11.4/8.11.4) with ESMTP id gA84t8c282023;
	Thu, 7 Nov 2002 23:55:08 -0500 (EST)
Received: from zathras (zathras.cc.vt.edu [198.82.162.117])
	by steiner.cc.vt.edu (Mirapoint Messaging Server MOS 3.2.1-GA)
	with ESMTP id ARZ93956;
	Thu, 7 Nov 2002 23:55:07 -0500 (EST)
X-WebMail-UserID:  talin
Date: Thu, 7 Nov 2002 23:55:07 -0500
From: Tao Lin <talin@vt.edu>
To: Harry <hr_befine@263.net>, MANET mail list <manet@ietf.org>
X-EXP32-SerialNo: 00002964
Subject: RE: [manet] Emulate MANET
Message-ID: <3DCBE9F0@zathras>
Mime-Version: 1.0
Content-Type: text/plain; charset="ISO-8859-1"
X-Mailer: WebMail (Hydra) SMTP v3.61.08
Content-Transfer-Encoding: 8bit
X-MIME-Autoconverted: from quoted-printable to 8bit by www1.ietf.org id gA84tPv15845
Sender: manet-admin@ietf.org
Errors-To: manet-admin@ietf.org
X-BeenThere: manet@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/manet>,
	<mailto:manet-request@ietf.org?subject=unsubscribe>
List-Id: Mobile Ad-hoc Networks  <manet.ietf.org>
List-Post: <mailto:manet@ietf.org>
List-Help: <mailto:manet-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/manet>,
	<mailto:manet-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 8bit
Content-Transfer-Encoding: 8bit

We developed a free tool and a corresponding paper at:
io.irean.vt.edu/~tlin
It has over 197 downloads till now.

It is simple a easy tool to emulate MANET in wired testbed without any
modification at mobile nodes.


>===== Original Message From Harry <hr_befine@263.net> =====
>hi,allŁˇ
>	I want to emulate MANET in a wired network environment. Who could recommend 
some softwares to me? I konw NS2 do. Are there anything else?
>	Thank u in advance.
>
>
>best regards
>ˇˇˇˇˇˇˇˇˇˇˇˇˇˇˇˇHarry
>ˇˇˇˇˇˇˇˇˇˇˇˇˇˇˇˇˇˇˇˇ2002-11-08
>
>
>_______________________________________________
>manet mailing list
>manet@ietf.org
>https://www1.ietf.org/mailman/listinfo/manet

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



From manet-admin@ietf.org  Fri Nov 15 16:27:17 2002
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA19742
	for <manet-archive@lists.ietf.org>; Fri, 15 Nov 2002 16:27:17 -0500 (EST)
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gAFLGfv16976;
	Fri, 15 Nov 2002 16:16:41 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gA7HU3v01487
	for <manet@optimus.ietf.org>; Thu, 7 Nov 2002 12:30:03 -0500
Received: from letters.cs.ucsb.edu (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA03123
	for <manet@ietf.org>; Thu, 7 Nov 2002 12:27:24 -0500 (EST)
Received: from saguaro (saguaro [128.111.40.82])
	by letters.cs.ucsb.edu (8.11.6+Sun/8.11.6) with SMTP id gA7HTrm24121
	for <manet@ietf.org>; Thu, 7 Nov 2002 09:29:53 -0800 (PST)
Message-Id: <200211071729.gA7HTrm24121@letters.cs.ucsb.edu>
Date: Thu, 7 Nov 2002 09:29:53 -0800 (PST)
From: "Elizabeth M. Belding-Royer" <ebelding@cs.ucsb.edu>
Reply-To: "Elizabeth M. Belding-Royer" <ebelding@cs.ucsb.edu>
To: manet@ietf.org
MIME-Version: 1.0
Content-Type: MULTIPART/mixed; BOUNDARY=Covey_of_Quail_388_000
X-Mailer: dtmail 1.3.0 @(#)CDE Version 1.3.5 SunOS 5.7 sun4u sparc 
Subject: [manet] New AODV draft
Sender: manet-admin@ietf.org
Errors-To: manet-admin@ietf.org
X-BeenThere: manet@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/manet>,
	<mailto:manet-request@ietf.org?subject=unsubscribe>
List-Id: Mobile Ad-hoc Networks  <manet.ietf.org>
List-Post: <mailto:manet@ietf.org>
List-Help: <mailto:manet-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/manet>,
	<mailto:manet-request@ietf.org?subject=subscribe>

--Covey_of_Quail_388_000
Content-Type: TEXT/plain; charset=us-ascii
Content-MD5: C9+DARvbzHh+1W0nuzZmxg==

Hi,

The AODV draft version 12 that was just announced does not have
the updated list of changes at the end.  We resubmitted the 
correct version before the deadline, but I guess it hasn't been
processed yet.  In the meantime, attached is the version we
resubmitted to the IETF directory.  It has the updated list of
changes; otherwise, its identical to the draft that was announced
early this morning.

Elizabeth

--Covey_of_Quail_388_000
Content-Type: TEXT/plain; name="aodvid.txt"; charset=us-ascii; x-unix-mode=0600
Content-Description: aodvid.txt
Content-MD5: NLP/O9yDLmBB92/3A24OsA==


Mobile Ad Hoc Networking Working Group                Charles E. Perkins
INTERNET DRAFT                                     Nokia Research Center
4 November 2002                               Elizabeth M. Belding-Royer
                                 University of California, Santa Barbara
                                                            Samir R. Das
                                                University of Cincinnati

            Ad hoc On-Demand Distance Vector (AODV) Routing
                      draft-ietf-manet-aodv-12.txt


Status of This Memo

   This document is a submission by the Mobile Ad Hoc Networking Working
   Group of the Internet Engineering Task Force (IETF).  Comments should
   be submitted to the manet@ietf.org mailing list.

   Distribution of this memo is unlimited.

   This document is an Internet-Draft and is in full conformance with
   all provisions of Section 10 of RFC2026.  Internet-Drafts are working
   documents of the Internet Engineering Task Force (IETF), its areas,
   and its working groups.  Note that other groups may also distribute
   working documents as Internet-Drafts.

   Internet-Drafts are draft documents valid for a maximum of six months
   and may be updated, replaced, or obsoleted by other documents at
   any time.  It is inappropriate to use Internet-Drafts as reference
   material or to cite them other than as "work in progress."

   The list of current Internet-Drafts can be accessed at:
        http://www.ietf.org/ietf/1id-abstracts.txt
   The list of Internet-Draft Shadow Directories can be accessed at:
        http://www.ietf.org/shadow.html.


Abstract

   The Ad hoc On-Demand Distance Vector (AODV) routing protocol
   is intended for use by mobile nodes in an ad hoc network.  It
   offers quick adaptation to dynamic link conditions, low processing
   and memory overhead, low network utilization, and determines
   unicast routes to destinations within the ad hoc network.  It uses
   destination sequence numbers to ensure loop freedom at all times
   (even in the face of anomalous delivery of routing control messages),
   avoiding problems (such as ``counting to infinity'') associated with
   classical distance vector protocols.








Perkins, Belding-Royer, Das         Expires 4 May 2003          [Page i]

Internet Draft                   AODV                    4 November 2002




                                Contents


Status of This Memo                                                    i

Abstract                                                               i

 1. Introduction                                                       1

 2. Overview                                                           1

 3. AODV Terminology                                                   3

 4. Message Formats                                                    5
     4.1. Route Request (RREQ) Message Format . . . . . . . . . . .    5
     4.2. Route Reply (RREP) Message Format . . . . . . . . . . . .    6
     4.3. Route Error (RERR) Message Format . . . . . . . . . . . .    8
     4.4. Route Reply Acknowledgment (RREP-ACK) Message Format  . .    9

 5. AODV Operation                                                     9
     5.1. Maintaining Sequence Numbers  . . . . . . . . . . . . . .    9
     5.2. Route Table Entries and Precursor Lists . . . . . . . . .   11
     5.3. Generating Route Requests . . . . . . . . . . . . . . . .   12
     5.4. Controlling Dissemination of Route Request Messages . . .   13
     5.5. Processing and Forwarding Route Requests  . . . . . . . .   14
     5.6. Generating Route Replies  . . . . . . . . . . . . . . . .   15
           5.6.1. Route Reply Generation by the Destination . . . .   16
           5.6.2. Route Reply Generation by an Intermediate Node  .   16
           5.6.3. Generating Gratuitous RREPs . . . . . . . . . . .   17
     5.7. Receiving and Forwarding Route Replies  . . . . . . . . .   17
     5.8. Operation over Unidirectional Links . . . . . . . . . . .   19
     5.9. Hello Messages  . . . . . . . . . . . . . . . . . . . . .   19
    5.10. Maintaining Local Connectivity  . . . . . . . . . . . . .   20
    5.11. Route Error Messages, Route Expiry and Route Deletion . .   21
    5.12. Local Repair  . . . . . . . . . . . . . . . . . . . . . .   23
    5.13. Actions After Reboot  . . . . . . . . . . . . . . . . . .   24
    5.14. Interfaces  . . . . . . . . . . . . . . . . . . . . . . .   25

 6. AODV and Aggregated Networks                                      25

 7. Using AODV with Other Networks                                    26

 8. Extensions                                                        26
     8.1. Hello Interval Extension Format . . . . . . . . . . . . .   27

 9. Configuration Parameters                                          27




Perkins, Belding-Royer, Das         Expires 4 May 2003         [Page ii]

Internet Draft                   AODV                    4 November 2002


10. Security Considerations                                           29

11. IPv6 Considerations                                               30

12. Acknowledgments                                                   30

 A. Draft Modifications                                               32


1. Introduction

   The Ad hoc On-Demand Distance Vector (AODV) algorithm enables
   dynamic, self-starting, multihop routing between participating mobile
   nodes wishing to establish and maintain an ad hoc network.  AODV
   allows mobile nodes to obtain routes quickly for new destinations,
   and does not require nodes to maintain routes to destinations that
   are not in active communication.  AODV allows mobile nodes to respond
   to link breakages and changes in network topology in a timely manner.
   The operation of AODV is loop-free, and by avoiding the Bellman-Ford
   ``counting to infinity'' problem offers quick convergence when the
   ad hoc network topology changes (typically, when a node moves in the
   network).  When links break, AODV causes the affected set of nodes to
   be notified so that they are able to invalidate the routes using the
   lost link.

   One distinguishing feature of AODV is its use of a destination
   sequence number for each route entry.  The destination sequence
   number is created by the destination for any route information it
   sends to requesting nodes.  Using destination sequence numbers
   ensures loop freedom and is simple to program.  Given the choice
   between two routes to a destination, a requesting node always selects
   the one with the greatest sequence number.


2. Overview

   Route Requests (RREQs), Route Replies (RREPs), and Route Errors
   (RERRs) are the message types defined by AODV. These message types
   are received via UDP, and normal IP header processing applies.
   So, for instance, the requesting node is expected to use its IP
   address as the Originator IP address for the messages.  For broadcast
   messages, the IP limited broadcast address (255.255.255.255) is used.
   This means that such messages are not blindly forwarded.  However,
   AODV operation does require certain messages (e.g., RREQ) to be
   disseminated widely, perhaps throughout the ad hoc network.  The
   range of dissemination of such RREQs is indicated by the TTL in the
   IP header.  Fragmentation is typically not required.





Perkins, Belding-Royer, Das         Expires 4 May 2003          [Page 1]

Internet Draft                   AODV                    4 November 2002


   As long as the endpoints of a communication connection have valid
   routes to each other, AODV does not play any role.  When a route to a
   new destination is needed, the node broadcasts a RREQ to find a route
   to the destination.  A route can be determined when the RREQ reaches
   either the destination itself, or an intermediate node with a 'fresh
   enough' route to the destination.  A 'fresh enough' route is a valid
   route entry for the destination whose associated sequence number is
   at least as great as that contained in the RREQ. The route is made
   available by unicasting a RREP back to the origination of the RREQ.
   Each node receiving the request caches a route back to the originator
   of the request, so that the RREP can be unicast from the destination
   along a path to that originator, or likewise from any intermediate
   node that is able to satisfy the request.

   Nodes monitor the link status of next hops in active routes.  When a
   link break in an active route is detected, a RERR message is used to
   notify other nodes that the loss of that link has occurred.  The RERR
   message indicates those destinations which are now unreachable due to
   the loss of the link.  In order to enable this reporting mechanism,
   each node keeps a ``precursor list'', containing the IP address for
   each its neighbors that are likely to use it as a next hop towards
   the destination that is now unreachable.  The information in the
   precursor lists is most easily acquired during the processing for
   generation of a RREP message, which by definition has to be sent to a
   node in a precursor list (see section 5.6).

   A RREQ may also be received for a multicast IP address.  In this
   document, full processing for such messages is not specified.  For
   example, the originator of such a RREQ for a multicast IP address
   may have to follow special rules.  However, it is important to
   enable correct multicast operation by intermediate nodes that are
   not enabled as originating or destination nodes for IP multicast
   addresses, and likewise are not equipped for any special multicast
   protocol processing.  For such multicast-unaware nodes, processing
   for a multicast IP address as a destination IP address MUST be
   carried out in the same way as for any other destination IP address.

   AODV is a routing protocol, and it deals with route table
   management.  Route table information must be kept even
   for short-lived routes, such as are created to temporarily
   store reverse paths towards nodes originating RREQs.  AODV











Perkins, Belding-Royer, Das         Expires 4 May 2003          [Page 2]

Internet Draft                   AODV                    4 November 2002


   uses the following fields with each route table entry:

       -  Destination IP Address
       -  Destination Sequence Number
       -  Valid Destination Sequence Number
       -  Interface
       -  Hop Count (number of hops needed to reach destination)
       -  Next Hop
       -  List of Precursors (described in Section 5.2)
       -  Lifetime (expiration or deletion time of the route)
       -  Routing Flags
       -  State

   Managing the sequence number is crucial to avoiding routing loops,
   even when links break and a node is no longer reachable to supply
   its own information about its sequence number.  A destination
   becomes unreachable when a link breaks or is deactivated.  When these
   conditions occur, the route is invalidated by operations involving
   the sequence number and marking the route table entry state as
   invalid.  See section 5.1 for details.


3. AODV Terminology

   This protocol specification uses conventional meanings [2] for
   capitalized words such as MUST, SHOULD, etc., to indicate requirement
   levels for various protocol features.  This section defines other
   terminology used with AODV that is not already defined in [3].

      active route

         A route towards a destination that has a routing table entry
         that is marked as valid.  Only active routes can be used to
         forward data packets.

      broadcast

         Broadcasting means transmitting to the IP Limited Broadcast
         address, 255.255.255.255.  A broadcast packet may not be
         blindly forwarded, but broadcasting is useful to enable
         dissemination of AODV messages throughout the ad hoc network.

      destination

         An IP address to which data packets are to be transmitted.
         Same as "destination node".  A node knows it is the destination
         node for a data packet when its address appears in the
         appropriate field of the IP header.  Routes for destination
         nodes are supplied by action of the AODV protocol, which



Perkins, Belding-Royer, Das         Expires 4 May 2003          [Page 3]

Internet Draft                   AODV                    4 November 2002


         carries the IP address of the destination node in route
         discovery messages.

      forwarding node

         A node that agrees to forward packets destined for another
         node, by retransmitting them to a next hop that is closer to
         the unicast destination along a path that has been set up using
         routing control messages.

      forward route

         A route set up to send data packets from a node originating a
         Route Discovery operation towards its desired destination.

      invalid route

         A route that has expired, denoted by a state of invalid in
         the routing table.  An invalid route is used to store the
         previously valid route information for an extended period
         of time.  An invalid route may not be used to forward data
         packets.

      originating node

         A node that initiates an AODV message to be processed and
         possibly retransmitted by other nodes in the ad hoc network.
         For instance, the node initiating a Route Discovery process and
         broadcasting the RREQ message is called the originating node of
         the RREQ message.

      reverse route

         A route set up to forward a reply (RREP) packet back to the
         originator from the destination or from an intermediate node
         having a route to the destination.

      sequence number

         An increasing number maintained by each originating node.  When
         used in control messages it is used by other nodes to determine
         the freshness of the information contained from the originating
         node.

      valid route

         See active route.





Perkins, Belding-Royer, Das         Expires 4 May 2003          [Page 4]

Internet Draft                   AODV                    4 November 2002


4. Message Formats

4.1. Route Request (RREQ) Message Format

    0                   1                   2                   3
    0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
   +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
   |     Type      |J|R|G|D|U|   Reserved          |   Hop Count   |
   +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
   |                            RREQ ID                            |
   +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
   |                    Destination IP Address                     |
   +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
   |                  Destination Sequence Number                  |
   +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
   |                    Originator IP Address                      |
   +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
   |                  Originator Sequence Number                   |
   +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+

   The format of the Route Request message is illustrated above, and
   contains the following fields:

      Type           1

      J              Join flag; reserved for multicast.

      R              Repair flag; reserved for multicast.

      G              Gratuitous RREP flag; indicates whether a
                     gratuitous RREP should be unicast to the node
                     specified in the Destination IP Address field (see
                     sections 5.3, 5.6.3)

      D              Destination only flag; indicates only the
                     destination may respond to this RREQ (see
                     section 5.5).

      U              Unknown sequence number; indicates the destination
                     sequence number is unknown(see section 5.3).

      Reserved       Sent as 0; ignored on reception.

      Hop Count      The number of hops from the Originator IP Address
                     to the node handling the request.

      RREQ ID        A sequence number uniquely identifying the
                     particular RREQ when taken in conjunction with the
                     originating node's IP address.



Perkins, Belding-Royer, Das         Expires 4 May 2003          [Page 5]

Internet Draft                   AODV                    4 November 2002


      Destination IP Address
                     The IP address of the destination for which a route
                     is desired.

      Destination Sequence Number
                     The greatest sequence number received in the
                     past by the originator for any route towards the
                     destination.

      Originator IP Address
                     The IP address of the node which originated the
                     Route Request.

      Originator Sequence Number
                     The current sequence number to be used for
                     route entries pointing to (and generated by) the
                     originator of the route request.


4.2. Route Reply (RREP) Message Format

    0                   1                   2                   3
    0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
   +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
   |     Type      |R|A|    Reserved     |Prefix Sz|   Hop Count   |
   +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
   |                     Destination IP address                    |
   +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
   |                  Destination Sequence Number                  |
   +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
   |                    Originator IP address                      |
   +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
   |                           Lifetime                            |
   +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+

   The format of the Route Reply message is illustrated above, and
   contains the following fields:

      Type          2

      R             Repair flag; used for multicast.

      A             Acknowledgment required; see sections 4.4 and 5.7.

      Reserved      Sent as 0; ignored on reception.

      Prefix Size   If nonzero, the 5-bit Prefix Size specifies that the
                    indicated next hop may be used for any nodes with




Perkins, Belding-Royer, Das         Expires 4 May 2003          [Page 6]

Internet Draft                   AODV                    4 November 2002


                    the same routing prefix (as defined by the Prefix
                    Size) as the requested destination.

      Hop Count     The number of hops from the Originator IP Address
                    to the Destination IP Address.  For multicast route
                    requests this indicates the number of hops to the
                    multicast tree member sending the RREP.

      Destination IP Address
                    The IP address of the destination for which a route
                    is supplied.

      Destination Sequence Number
                    The destination sequence number associated to the
                    route.

      Originator IP Address
                    The IP address of the node which originated the RREQ
                    for which the route is supplied.

      Lifetime      The time in milliseconds for which nodes receiving
                    the RREP consider the route to be valid.

   Note that the Prefix Size allows a Subnet Leader to supply a route
   for every host in the subnet defined by the routing prefix, which
   is determined by the IP address of the Subnet Leader and the Prefix
   Size.  In order to make use of this feature, the Subnet Leader has to
   guarantee reachability to all the hosts sharing the indicated subnet
   prefix.  The Subnet Leader is also responsible for maintaining the
   Destination Sequence Number for the whole subnet.  See section 6 for
   details.

   The 'A' bit is used in cases where the link over which the RREP
   message is sent may be unreliable or unidirectional.  When the
   RREP message contains the 'A' bit set, the receiver of the RREP is
   expected to return a RREP-ACK message.  See section 5.8.
















Perkins, Belding-Royer, Das         Expires 4 May 2003          [Page 7]

Internet Draft                   AODV                    4 November 2002


4.3. Route Error (RERR) Message Format

    0                   1                   2                   3
    0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
   +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
   |     Type      |N|          Reserved           |   DestCount   |
   +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
   |            Unreachable Destination IP Address (1)             |
   +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
   |         Unreachable Destination Sequence Number (1)           |
   +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-|
   |  Additional Unreachable Destination IP Addresses (if needed)  |
   +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
   |Additional Unreachable Destination Sequence Numbers (if needed)|
   +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+


   The format of the Route Error message is illustrated above, and
   contains the following fields:

      Type        3

      N           No delete flag; set when a node has performed a local
                  repair of a link, and upstream nodes should not delete
                  the route.

      Reserved    Sent as 0; ignored on reception.

      DestCount   The number of unreachable destinations included in the
                  message; MUST be at least 1.

      Unreachable Destination IP Address
                  The IP address of the destination that has become
                  unreachable due to a link break.

      Unreachable Destination Sequence Number
                  The sequence number in the route table entry for
                  the destination listed in the previous Unreachable
                  Destination IP Address field.

   The RERR message is sent whenever a link break causes one or more
   destinations to become unreachable from some of the node's neighbors.
   See section 5.2 for information about how to maintain the appropriate
   records for this determination, and section 5.11 for specification
   about how to create the list of destinations.







Perkins, Belding-Royer, Das         Expires 4 May 2003          [Page 8]

Internet Draft                   AODV                    4 November 2002


4.4. Route Reply Acknowledgment (RREP-ACK) Message Format

   The Route Reply Acknowledgment (RREP-ACK) message MUST be sent in
   response to a RREP message with the 'A' bit set (see section 4.2.
   This is typically done when there is danger of unidirectional
   links preventing the completion of a Route Discovery cycle (see
   section 5.8).

    0                   1
    0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5
   +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
   |     Type      |   Reserved    |
   +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+


      Type        4

      Reserved    Sent as 0; ignored on reception.


5. AODV Operation

   This section describes the scenarios under which nodes generate Route
   Request (RREQ), Route Reply (RREP) and Route Error (RERR) messages
   for unicast communication towards a destination, and how the message
   data are handled.  In order to process the messages correctly,
   certain state information has to be maintained in the route table
   entries for the destinations of interest.

   All AODV messages are sent to port 654 using UDP.


5.1. Maintaining Sequence Numbers

   Every route table entry at every node MUST include the latest
   information available about the sequence number for the IP address of
   the destination node for which the route table entry is maintained.
   This sequence number is called the "destination sequence number".  It
   is updated whenever a node receives new (i.e., not stale) information
   about the sequence number from RREQ, RREP, or RERR messages that
   may be received related to that destination.  AODV depends on each
   node in the network to own and maintain its destination sequence
   number to guarantee the loop-freedom of all routes towards that
   node.  A destination node increments its own sequence number in two
   circumstances:

    -  Immediately before a node originates a route discovery, it MUST
       increment its own sequence number.  This prevents problems with
       deleted reverse routes to the originator of a RREQ.



Perkins, Belding-Royer, Das         Expires 4 May 2003          [Page 9]

Internet Draft                   AODV                    4 November 2002


    -  Immediately before a destination node originates a RREP in
       response to a RREQ, it MUST update its own sequence number to
       the maximum of its current sequence number and the destination
       sequence number in the RREQ packet.

   When the destination increments its sequence number, it MUST do so
   by treating the sequence number value as if it were an unsigned
   number.  To accomplish sequence number rollover, if the sequence
   number has already been assigned to be the largest possible number
   representable as a 32-bit unsigned integer (i.e., 4294967295), then
   when it is incremented it will then have a value of zero (0).  On
   the other hand, if the sequence number currently has the value
   2147483647, which is the largest possible positive integer if 2's
   complement arithmetic is in use with 32-bit integers, the next value
   will be 2147483648, which is the most negative possible integer in
   the same numbering system.  The representation of negative numbers
   is not relevant to the increment of AODV sequence numbers.  This is
   in contrast to the manner in which the result of comparing two AODV
   sequence numbers is to be treated (see below).

   In order to ascertain that information about a destination is not
   stale, the node compares its current numerical value for the sequence
   number with that obtained from the incoming AODV message.  This
   comparison MUST be done using signed 32-bit arithmetic, this is
   necessary to accomplish sequence number rollover.  If the result of
   subtracting the currently stored sequence number from the value of
   the incoming sequence number is less than zero, then the information
   related to that destination in the AODV message MUST be discarded,
   since that information is stale compared to the node's currently
   stored information.

   The only other circumstance in which a node may change the
   destination sequence number in one of its route table entries is
   in response to a lost or expired link to the next hop towards that
   destination.  The node determines which destinations use a particular
   next hop by consulting its routing table.  In this case, for each
   destination that uses the next hop, the node increments the sequence
   number and marks the route as invalid (see also sections 5.11, 5.12).
   Whenever any fresh enough (i.e., containing a sequence number at
   least equal to the recorded sequence number) routing information for
   an affected destination is received by a node that has marked that
   route table entry as invalid, the node SHOULD update its route table
   information according to the information contained in the update.

   A node may change the sequence number in the routing table entry of a
   destination only if:

    -  it is itself the destination node, and offers a new route to
       itself, or



Perkins, Belding-Royer, Das         Expires 4 May 2003         [Page 10]

Internet Draft                   AODV                    4 November 2002


    -  it receives an AODV message with new information about the
       sequence number for a destination node, or

    -  the path towards the destination node expires or breaks.


5.2. Route Table Entries and Precursor Lists

   When a node receives an AODV control packet from a neighbor, or
   creates or updates a route for a particular destination, it checks
   its route table for an entry for the destination.  In the event
   that there is no corresponding entry for that destination, an entry
   is created.  The sequence number is either determined from the
   information contained in the control packet, or else the valid
   sequence number field is set to false.  The route is only updated if
   the new sequence number is either

      (i)       higher than the destination sequence number in the route
                table, or

      (ii)      the sequence numbers are equal, but the hop count (of
                the new information) plus one, is smaller than the
                existing hop count in the routing table, or

      (iii)     the sequence number is unknown.

   The Lifetime field of the routing table entry is either
   determined from the control packet, or it is initialized to
   ACTIVE_ROUTE_TIMEOUT. This route may now be used to send any queued
   data packets and fulfills any outstanding route requests.

   Each time a route is used to forward a data packet, its Active
   Route Lifetime field of the source, destination and the next hop
   on the path to the destination is updated to be no less than the
   current time plus ACTIVE_ROUTE_TIMEOUT. Since the route between each
   originator and destination pair are expected to be symmetric, the
   Active Route Lifetime for the previous hop, along the reverse path
   back to the IP source, is also updated to be no less than the current
   time plus ACTIVE_ROUTE_TIMEOUT.

   For each valid route maintained by a node as a routing table entry,
   the node also maintains a list of precursors that may be forwarding
   packets on this route.  These precursors will receive notifications
   from the node in the event of detection of the loss of the next hop
   link.  The list of precursors in a routing table entry contains those
   neighboring nodes to which a route reply was generated or forwarded.






Perkins, Belding-Royer, Das         Expires 4 May 2003         [Page 11]

Internet Draft                   AODV                    4 November 2002


5.3. Generating Route Requests

   A node disseminates a RREQ when it determines that it needs a route
   to a destination and does not have one available.  This can happen if
   the destination is previously unknown to the node, or if a previously
   valid route to the destination expires or is marked as invalid.  The
   Destination Sequence Number field in the RREQ message is the last
   known destination sequence number for this destination and is copied
   from the Destination Sequence Number field in the routing table.  If
   no sequence number is known, the unknown sequence number flag MUST
   be set.  The Originator Sequence Number in the RREQ message is the
   node's own sequence number, which is incremented prior to insertion
   in a RREQ. The RREQ ID field is incremented by one from the last RREQ
   ID used by the current node.  Each node maintains only one RREQ ID.
   The Hop Count field is set to zero.

   Before broadcasting the RREQ, the originating node buffers the RREQ
   ID and the Originator IP address (its own address) of the RREQ for
   PATH_DISCOVERY_TIME. In this way, when the node receives the packet
   again from its neighbors, it will not reprocess and re-forward the
   packet.

   An originating node often expects to have bidirectional
   communications with a destination node.  In such cases, it is
   not sufficient for the originating node to have a route to the
   destination node; the destination must also have a route back to
   the originating node.  In order for this to happen as efficiently
   as possible, any generation of a RREP by an intermediate node (as
   in section 5.6) for delivery to the originating node SHOULD be
   accompanied by some action that notifies the destination about a
   route back to the originating node.  The originating node selects
   this mode of operation in the intermediate nodes by setting the `G'
   flag.  See section 5.6.3 for details about actions taken by the
   intermediate node in response to a RREQ with the `G' flag set.

   A node SHOULD NOT generate more than RREQ_RATELIMIT RREQ messages
   per second.  After broadcasting a RREQ, a node waits for a RREP (or
   other control message with current information regarding a route to
   the appropriate destination).  If a route is not received within
   NET_TRAVERSAL_TIME milliseconds, the node MAY try again to discover a
   route by broadcasting another RREQ, up to a maximum of RREQ_RETRIES
   times at the maximum TTL value.  Each new attempt MUST increment and
   update the RREQ ID. For each attempt, the TTL field of the IP header
   is set according to the mechanism specified in section 5.4, in order
   to enable control over how far the RREQ is disseminated for the each
   retry.

   Data packets waiting for a route (i.e., waiting for a RREP after a
   RREQ has been sent) SHOULD be buffered.  The buffering SHOULD be



Perkins, Belding-Royer, Das         Expires 4 May 2003         [Page 12]

Internet Draft                   AODV                    4 November 2002


   "first-in, first-out" (FIFO). If a route discovery has been attempted
   RREQ_RETRIES times at the maximum TTL without receiving any RREP, all
   data packets destined for the corresponding destination SHOULD be
   dropped from the buffer and a Destination Unreachable message SHOULD
   be delivered to the application.

   To reduce congestion in a network, repeated attempts by a source
   node at route discovery for a single destination MUST utilize a
   binary exponential backoff.  The first time a source node broadcasts
   a RREQ, it waits NET_TRAVERSAL_TIME milliseconds for the reception
   of a RREP. If a RREP is not received within that time, the source
   node sends a new RREQ. When calculating the time to wait for
   the RREP after sending the second RREQ, the source node MUST use
   a binary exponential backoff.  Hence, the waiting time for the
   RREP corresponding to the second RREQ is 2 * NET_TRAVERSAL_TIME
   milliseconds.  If a RREP is not receivied within this time period,
   another RREQ may be sent, up to RREQ_RETRIES additional attempts
   after the first RREQ. For each additional attempt, the waiting time
   for the RREP is multiplied by 2, so that the time conforms to a
   binary exponential backoff.


5.4. Controlling Dissemination of Route Request Messages

   To prevent unnecessary network-wide dissemination of RREQs, the
   originating node SHOULD use an expanding ring search technique.
   In an expanding ring search, the originating node initially
   uses a TTL = TTL_START in the RREQ packet IP header and sets the
   timeout for receiving a RREP to RING_TRAVERSAL_TIME milliseconds.
   RING_TRAVERSAL_TIME is calculcated as described in section 9.  The
   TTL_VALUE used in calculating RING_TRAVERSAL_TIME is set equal to
   the value of the TTL field in the IP header.  If the RREQ times out
   without a corresponding RREP, the originator broadcasts the RREQ
   again with the TTL incremented by TTL_INCREMENT. This continues until
   the TTL set in the RREQ reaches TTL_THRESHOLD, beyond which a TTL =
   NET_DIAMETER is used for each attempt.  Each time, the timeout for
   receiving a RREP is RING_TRAVERSAL_TIME. When it is desired to have
   all retries traverse the entire ad hoc network, this can be achieved
   by configuring TTL_START and TTL_INCREMENT both to be the same value
   as NET_DIAMETER.

   The Hop Count stored in an invalid routing table entry indicates
   the last known hop count to that destination in the routing table.
   When a new route to the same destination is required at a later time
   (e.g., upon route loss), the TTL in the RREQ IP header is initially
   set to the Hop Count plus TTL_INCREMENT. Thereafter, following
   each timeout the TTL is incremented by TTL_INCREMENT until TTL =
   TTL_THRESHOLD is reached.  Beyond this TTL = NET_DIAMETER is used.




Perkins, Belding-Royer, Das         Expires 4 May 2003         [Page 13]

Internet Draft                   AODV                    4 November 2002


   Once TTL = NET_DIAMETER, the timeout for waiting for the RREP is set
   to NET_TRAVERSAL_TIME, as specified in section 5.3.

   An expired routing table entry SHOULD NOT be expunged before
   (current_time + DELETE_PERIOD) (see section 5.11).  Otherwise, the
   soft state corresponding to the route (e.g., last known hop count)
   will be lost.  Furthermore, a longer routing table entry expunge time
   MAY be configured.  Any routing table entry waiting for a RREP SHOULD
   NOT be expunged before (current_time + 2 * NET_TRAVERSAL_TIME).


5.5. Processing and Forwarding Route Requests

   When a node receives a RREQ, it first creates or updates a route to
   the previous hop without a valid sequence number (see section 5.2)
   then checks to determine whether it has received a RREQ with
   the same Originator IP Address and RREQ ID within at least the
   last PATH_DISCOVERY_TIME. If such a RREQ has been received, the
   node silently discards the newly received RREQ. The rest of this
   subsection describes actions taken for RREQs that are not discarded.

   First, it first increments the hop count value in the RREQ by one,
   to account for the new hop through the intermediate node.  Then the
   node creates or updates a reverse route to the Originator IP Address
   (see section 5.2) using the Originator Sequence Number from the RREQ
   in its routing table.  This reverse route will be needed if the node
   receives a RREP back to the node that originated the RREQ (identified
   by the Originator IP Address).  When the reverse route is created or
   updated, the following actions on the route are also carried out:

    1. the Originator Sequence Number from the RREQ is copied to the
       corresponding destination sequence number in the route table
       entry and the valid sequence number field is set to true;

    2. the next hop in the routing table becomes the node from which the
       RREQ was received (it is obtained from the source IP address in
       the IP header and is often not equal to the Originator IP Address
       field in the RREQ message);

    3. the hop count is copied from the Hop Count in the RREQ message;

   Whenever a RREQ message is received, the Lifetime of the reverse
   route entry for the Originator IP address is set to be the maximum of
   (ExistingLifetime, MinimalLifetime), where

      MinimalLifetime =    (current time + 2*NET_TRAVERSAL_TIME -
                           2*HopCount*NODE_TRAVERSAL_TIME).





Perkins, Belding-Royer, Das         Expires 4 May 2003         [Page 14]

Internet Draft                   AODV                    4 November 2002


   The current node can now begin using the reverse route to forward
   data packets.

   The node generates a RREP (as discussed further in section 5.6) if
   either:

      (i)       it is itself the destination (see section 5.6.1), or

      (ii)      it has an active route to the destination, the
                destination sequence number in the node's existing route
                table entry for the destination is valid and greater
                than or equal to the Destination Sequence Number of the
                RREQ (comparison using signed 32-bit arithmetic), and
                the ``destination only'' ('D') flag is NOT set.  See
                section 5.6.2 for further information about generating
                the RREP in this case.

   When either of these conditions is satisfied, the node does not
   rebroadcast the RREQ.

   Otherwise, if the incoming IP header has TTL larger than 1, the node
   updates and broadcasts the RREQ to address 255.255.255.255 on all of
   its configured interface(s) (see section 5.14).  To update the RREQ,
   the TTL or hop limit field in the outgoing IP header is decreased
   by one, and the Hop Count field in the RREQ message is incremented
   by one, to account for the new hop through the intermediate node.
   Lastly, the Destination Sequence number for the requested destination
   is set to the maximum of the corresponding value received in the RREQ
   message, and the destination sequence value currently maintained by
   the node for the requested destination.  However, the forwarding node
   MUST NOT modify its maintained value for the destination sequence
   number, even if the value received in the incoming RREQ is larger
   than the value currently maintained by the forwarding node.


5.6. Generating Route Replies

   If a node receives a route request for a destination, and either
   has a fresh enough route to satisfy the request or is itself the
   destination, the node generates a RREP message.  This node copies
   the Destination IP Address and the Originator Sequence Number in
   RREQ message into the corresponding fields in the RREP message.
   Processing is slightly different, depending on whether the node is
   itself the requested destination, or instead if it is an intermediate
   node with an fresh enough route to the destination.  These scenarios
   are described in the sections below.

   Once created, the RREP is unicast to the next hop toward the
   originator of the RREQ, as indicated by the route table entry for



Perkins, Belding-Royer, Das         Expires 4 May 2003         [Page 15]

Internet Draft                   AODV                    4 November 2002


   that originator.  As the RREP is forwarded back towards the node
   which originated the RREQ message, the Hop Count field is incremented
   by one at each hop.  Thus, when the RREP reaches the originator, the
   Hop Count represents the distance, in hops, of the destination from
   the originator.


5.6.1. Route Reply Generation by the Destination

   If the generating node is the destination itself, it MUST increment
   its own sequence number by one if the sequence number in the
   RREQ packet is equal to that incremented value.  Otherwise, the
   destination does not change its sequence number before generating
   the RREP message.  The destination node places its (perhaps newly
   incremented) sequence number into the Destination Sequence Number
   field of the RREP, and enters the value zero in the Hop Count field
   of the RREP.

   The destination node copies the value MY_ROUTE_TIMEOUT (see
   section 9) into the Lifetime field of the RREP. Each node MAY
   reconfigure its value for MY_ROUTE_TIMEOUT, within mild constraints
   (see section 9).


5.6.2. Route Reply Generation by an Intermediate Node

   If the node generating the RREP is not the destination node, but
   instead is an intermediate hop along the path from the originator
   to the destination, it copies its known sequence number for the
   destination into the Destination Sequence Number field in the RREP
   message.

   The intermediate node updates the forward route entry by placing the
   last hop node (from which it received the RREQ, as indicated by the
   source IP address field in the IP header) into the precursor list for
   the forward route entry -- i.e., the entry for the Destination IP
   Address.  The intermediate node also updates its route table entry
   for the node originating the RREQ by placing the next hop towards
   the destination in the precursor list for the reverse route entry
   -- i.e., the entry for the Originator IP Address field of the RREQ
   message data.

   The intermediate node places its distance in hops from the
   destination (indicated by the hop count in the routing table) Count
   field in the RREP. The Lifetime field of the RREP is calculated by
   subtracting the current time from the expiration time in its route
   table entry.





Perkins, Belding-Royer, Das         Expires 4 May 2003         [Page 16]

Internet Draft                   AODV                    4 November 2002


5.6.3. Generating Gratuitous RREPs

   After a node receives a RREQ and responds with a RREP, it discards
   the RREQ. If intermediate nodes reply to every transmission of a
   given RREQ, the destination does not receive any copies of it.  In
   this situation, the destination does not learn of a route to the
   originating node.  This could cause the destination to initiate a
   route discovery (for example, if the originator is attempting to
   establish a TCP session).  In order that the destination learn of
   routes to the originating node, the originating node SHOULD set
   the ``gratuitous RREP'' ('G') flag in the RREQ if for any reason
   the destination is likely to need a route to the originating node.
   If, in response to a RREQ with the 'G' flag set, an intermediate
   node returns a RREP, it MUST also unicast a gratuitous RREP to the
   destination node.

   The RREP that is sent to the originator of the RREQ is the same
   as before.  The gratuitous RREP that is to be sent to the desired
   destination contains the following values in the RREP message fields:

      Hop Count  The Hop Count as indicated in the node's route table
                 entry for the originator

      Destination IP Address
                 The IP address of the node that originated the RREQ

      Destination Sequence Number
                 The Originator Sequence Number from the RREQ

      Originator IP Address
                 The IP address of the Destination node in the RREQ

      Lifetime   The remaining lifetime of the route towards the
                 originator of the RREQ, as known by the intermediate
                 node.

   The gratuitous RREP is then sent to the next hop along the path to
   the destination node, just as if the destination node had already
   issued a RREQ for the originating node and this RREP was produced in
   response to that (fictitious) RREQ.


5.7. Receiving and Forwarding Route Replies

   When a node receives a RREP message, it first creates or updates
   a route to the previous hop without a valid sequence number (see
   section 5.2) then increments the hop count value in the RREP by one,
   to account for the new hop through the intermediate node.  Call this
   incremented value the "New Hop Count".  Then the forward route for



Perkins, Belding-Royer, Das         Expires 4 May 2003         [Page 17]

Internet Draft                   AODV                    4 November 2002


   this destination is created if it does not already exist.  Otherwise,
   the node compares the Destination Sequence Number in the message with
   its own stored destination sequence number for the Destination IP
   Address in the RREP message.  Upon comparison, the existing entry is
   updated only if either

      (i)       the sequence number in the routing table is invalid in
                route table entry.

      (ii)      the Destination Sequence Number in the RREP is greater
                than the node's copy of the destination sequence number
                and the known value is valid, or

      (iii)     the sequence numbers are the same, but the route is no
                longer active, or

      (iv)      the sequence numbers are the same, and the New Hop Count
                is smaller than the hop count in route table entry.

   If either the route table entry to the destination is created or
   updated, the next hop in the route entry is assigned to be the node
   from which the RREP is received, which is indicated by the source IP
   address field in the IP header; the hop count is the New Hop Count;
   the expiry time is the current time plus the Lifetime in the RREP
   message; and the destination sequence number is the Destination
   Sequence Number in the RREP message.  The current node can now begin
   using this route to forward data packets to the destination.

   If the current node is not the node indicated by the Originator IP
   Address in the RREP message AND a forward route has been created or
   updated as described above, the node consults its route table entry
   for the originating node to determine the next hop for the RREP
   packet, and then forwards the RREP towards the originator using the
   information in that route table entry.  If a node forwards a RREP
   over a link that is likely to have errors or be unidirectional, the
   node SHOULD set the `A' flag to require that the recipient of the
   RREP acknowledge receipt of the RREP by sending a RREP-ACK message
   back (see section 5.8).

   When any node transmits a RREP, the precursor list for the
   corresponding destination node is updated by adding to it the
   next hop node to which the RREP is forwarded.  Also, at each
   node the (reverse) route used to forward a RREP has its lifetime
   changed to be the maximum of (existing-lifetime, (current time +
   ACTIVE_ROUTE_TIMEOUT)). Finally, the precursor list for the next hop
   towards the destination is updated to contain the next hop towards
   the source.





Perkins, Belding-Royer, Das         Expires 4 May 2003         [Page 18]

Internet Draft                   AODV                    4 November 2002


5.8. Operation over Unidirectional Links

   It is possible that a RREP transmission may fail, especially if the
   RREQ transmission triggering the RREP occurs over a unidirectional
   link.  If no other RREP generated from the same route discovery
   attempt reaches the node which originated the RREQ message, the
   originator will reattempt route discovery after a timeout (see
   section 5.3).  However, the same scenario might well be repeated, and
   no route would be discovered even after repeated retries.  Unless
   corrective action is taken, this can happen even when bidirectional
   routes between originator and destination do exist.  Link layers
   using broadcast transmissions for the RREQ will not be able to detect
   the presence of such unidirectional links.  In AODV, any node acts on
   only the first RREQ with the same RREQ ID and ignores any subsequent
   RREQs.  Suppose, for example, that the first RREQ arrives along a
   path that has one or more unidirectional link(s).  A subsequent RREQ
   may arrive via a bidirectional path (assuming such paths exist), but
   it will be ignored.

   To prevent this problem, when a node detects that its transmission of
   a RREP message has failed, it remembers the next-hop of the failed
   RREP in a ``blacklist'' set.  Such failures can be detected via
   the absence of a link-layer or network-layer acknowledgment (e.g.,
   RREP-ACK). A node ignores all RREQs received from any node in its
   blacklist set.  Nodes are removed from the blacklist set after a
   BLACKLIST_TIMEOUT period (see section 9).  This period should be set
   to the upper bound of the time it takes to perform the allowed number
   of route request retry attempts as described in section 5.3.

   Note that the RREP-ACK packet does not contain any information about
   which RREP it is acknowledging.  The time at which the RREP-ACK is
   received will likely come just after the time when the RREP was sent
   with the 'A' bit.  This information is expected to be sufficient
   to provide assurance to the sender of the RREP that the link is
   currently bidirectional.  However, that assurance cannot be always
   expected to remain permanently.


5.9. Hello Messages

   A node MAY offer connectivity information by broadcasting local Hello
   messages.  A node SHOULD only use hello messages if it is part of an
   active route.  Every HELLO_INTERVAL milliseconds, the node checks
   whether it has sent a broadcast (e.g., a RREQ or an appropriate layer
   2 message) within the last HELLO_INTERVAL. If it has not, it MAY
   broadcast a RREP with TTL = 1, called a Hello message, with the RREP
   message fields set as follows:





Perkins, Belding-Royer, Das         Expires 4 May 2003         [Page 19]

Internet Draft                   AODV                    4 November 2002


      Destination IP Address
                  The node's IP address.

      Destination Sequence Number
                  The node's latest sequence number.

      Hop Count   0

      Lifetime    ALLOWED_HELLO_LOSS * HELLO_INTERVAL

   A node MAY determine connectivity by listening for packets from its
   set of neighbors.  If, within the past DELETE_PERIOD, it has received
   a Hello message from a neighbor, and then for that neighbor does
   not receive any packets (Hello messages or otherwise) for more than
   ALLOWED_HELLO_LOSS * HELLO_INTERVAL milliseconds, the node SHOULD
   assume that the link to this neighbor is currently lost.  When this
   happens, the node SHOULD proceed as in Section 5.11.

   Whenever a node receives a Hello message from a neighbor, the
   node SHOULD make sure that it has an active route to the neighbor,
   and create one if necessary.  If a route already exists, then the
   Lifetime for the route should be increased, if necessary, to be at
   least ALLOWED_HELLO_LOSS * HELLO_INTERVAL. The route to the neighbor,
   if it exists, MUST subsequently contain the latest Destination
   Sequence Number from the Hello message.  The current node can now
   begin using this route to forward data packets.  Routes that are
   created by hello messages and not used by any other active routes
   will have empty precursor lists and would not trigger a RERR message
   when the neighbor moves away and a neighbor timeout occurs.

   Also, whenever a node receives any control packet it has the same
   meaning as the reception of an explicit Hello message, in that it
   signifies an active connection to the node indicated by the Source IP
   Address of the IP header of the control message packet.


5.10. Maintaining Local Connectivity

   Each forwarding node SHOULD keep track of its continued connectivity
   to its active next hops (i.e., which next hops or precursors have
   forwarded packets to or from the forwarding node during the last
   ACTIVE_ROUTE_TIMEOUT), as well as neighbors that have transmitted
   Hello messages during the last (ALLOWED_HELLO_LOSS * HELLO_INTERVAL).
   A node can maintain accurate information about its continued
   connectivity to these active next hops, using one or more of the
   available link or network layer mechanisms, as described below.

    -  Any suitable link layer notification, such as those provided by
       IEEE 802.11, can be used to determine connectivity, each time



Perkins, Belding-Royer, Das         Expires 4 May 2003         [Page 20]

Internet Draft                   AODV                    4 November 2002


       a packet is transmitted to an active next hop.  For example,
       absence of a link layer ACK or failure to get a CTS after sending
       RTS, even after the maximum number of retransmission attempts,
       indicates loss of the link to this active next hop.

    -  If possible, passive acknowledgment SHOULD be used when the
       next hop is expected to forward the packet, by listening to the
       channel for a transmission attempt made by the next hop.  If
       transmission is not detected within NEXT_HOP_WAIT milliseconds or
       the next hop is the destination (and thus is never supposed to
       transmit the packet) one of the following methods should be used
       to determine connectivity.

        *  Receiving any packet (including a Hello message) from the
           next hop.

        *  A RREQ unicast to the next hop, asking for a route to the
           next hop.

        *  An ICMP Echo Request message unicast to the next hop.

   If a link to the next hop cannot be detected by any of these methods,
   the forwarding node SHOULD assume that the link is lost, and take
   corrective action by following the methods specified in Section 5.11.


5.11. Route Error Messages, Route Expiry and Route Deletion

   A Route Error (RERR) message MAY be either broadcast (if there
   are many precursors), unicast (if there is only 1 precursor),
   or iteratively unicast to all precursors (if broadcast is
   inappropriate).  Even when the RERR message is iteratively unicast
   to several precursors, it is considered to be a single control
   message for the purposes of the description in the text that follows.
   With that understanding, a node SHOULD NOT generate more than
   RERR_RATELIMIT RERR messages per second.

   A node initiates processing for a RERR message in three situations:

      (i)       if it detects a link break for the next hop of an active
                route in its routing table while transmitting data, or

      (ii)      if it gets a data packet destined to a node for which it
                does not have an active route and is not repairing (if
                using local repair), or

      (iii)     if it receives a RERR from a neighbor for one or more
                active routes.




Perkins, Belding-Royer, Das         Expires 4 May 2003         [Page 21]

Internet Draft                   AODV                    4 November 2002


   For case (i), the node first makes a list of unreachable destinations
   consisting of the unreachable neighbor and any additional
   destinations in the local routing table that use the unreachable
   neighbor as the next hop.  For case (ii), there is only one
   unreachable destination, which is the destination of the data packet
   that cannot be delivered.  For case (iii), the list should consist of
   those destinations in the RERR for which there exists a corresponding
   entry in the local routing table that has the transmitter of the
   received RERR as the next hop.

   Some of the unreachable destinations in the list could be used by
   neighboring nodes, and it may therefore be necessary to send a (new)
   RERR. The RERR should contain those destinations that are part of
   the created list of unreachable destinations and have a non-empty
   precursor list.

   The neighboring node(s) that should receive the RERR are all those
   that belong to a precursor list of at least one of the unreachable
   destination(s) in the newly created RERR. In case there is only
   one unique neighbor that needs to receive the RERR, the RERR
   SHOULD be unicast toward that destination.  Otherwise the RERR is
   typically sent to the local broadcast address (Destination IP ==
   255.255.255.255, TTL == 1) with the unreachable destinations, and
   their corresponding destination sequence numbers, included in the
   packet.  The DestCount field of the RERR packet indicates the number
   of unreachable destinations included in the packet.

   Just before transmitting the RERR, certain updates are made on the
   routing table that may affect the destination sequence numbers for
   the unreachable destinations.  For each one of these destinations,
   the corresponding routing table entry is updated as follows:

    1. The destination sequence number of this routing entry, if it
       exists and is valid, is incremented for cases (i) and (ii) above,
       and copied from the incoming RERR in case (iii) above.

    2. The entry is invalidated by marking the route entry as invalid

    3. The Lifetime field is updated to current time plus DELETE_PERIOD.
       Before this time, the entry SHOULD NOT be deleted.

   Note that the Lifetime field in the routing table plays dual role
   -- for an active route it is the expiry time, and for an invalid
   route it is the deletion time.  If a data packet is received for an
   invalid route, the Lifetime field is updated to current time plus
   DELETE_PERIOD. The determination of DELETE_PERIOD is discussed in
   Section 9.





Perkins, Belding-Royer, Das         Expires 4 May 2003         [Page 22]

Internet Draft                   AODV                    4 November 2002


5.12. Local Repair

   When a link break in an active route occurs, the node upstream of
   that break MAY choose to repair the link locally if the destination
   was no farther than MAX_REPAIR_TTL hops away.  To repair the link
   break, the node increments the sequence number for the destination
   and then broadcasts a RREQ for that destination.  The TTL of the RREQ
   should initially be set to the following value:

      max(MIN_REPAIR_TTL, 0.5 * #hops) + LOCAL_ADD_TTL,

   where #hops is the number of hops to the sender (originator) of the
   currently undeliverable packet.  Thus, local repair attempts will
   often be invisible to the originating node, and will always have TTL
   >= MIN_REPAIR_TTL + LOCAL_ADD_TTL. The node initiating the repair
   then waits the discovery period to receive RREPs in response to the
   RREQ. During local repair data packets SHOULD be buffered.  If, at
   the end of the discovery period, it has not received a RREP (or other
   control message creating or updating the route) for that destination,
   it proceeds as described in Section 5.11 by transmitting a RERR
   message for that destination.

   On the other hand, if the node receives one or more RREPs (or
   other control message creating or updating the route to the desired
   destination) during the discovery period, it first compares the hop
   count of the new route with the value in the hop count field of the
   invalid route table entry for that destination.  If the hop count of
   the newly determined route to the destination is greater than the
   hop count of the previously known route the node SHOULD issue a RERR
   message for the destination, with the 'N' bit set.  Then it proceeds
   as described in Section 5.7, updating its route table entry for that
   destination.

   A node that receives a RERR message with the 'N' flag set MUST NOT
   delete the route to that destination.  The only action taken should
   be the retransmission of the message, if the RERR arrived from the
   next hop along that route, and if there are one or more precursor
   nodes for that route to the destination.  When the originating node
   receives a RERR message with the 'N' flag set, if this message
   came from its next hop along its route to the destination then
   the originating node MAY choose to reinitiate route discovery, as
   described in Section 5.3.

   Local repair of link breaks in routes sometimes results in increased
   path lengths to those destinations.  Repairing the link locally is
   likely to increase the number of data packets that are able to be
   delivered to the destinations, since data packets will not be dropped
   as the RERR travels to the originating node.  Sending a RERR to the
   originating node after locally repairing the link break may allow the



Perkins, Belding-Royer, Das         Expires 4 May 2003         [Page 23]

Internet Draft                   AODV                    4 November 2002


   originator to find a fresh route to the destination that is better,
   based on current node positions.  However, it does not require the
   originating node to rebuild the route, as the originator may be done,
   or nearly done, with the data session.

   When a link breaks along an active route, there are often multiple
   destinations that become unreachable.  The node that is upstream
   of the lost link tries an immediate local repair for only the one
   destination towards which the data packet was traveling.  Other
   routes using the same link MUST be marked as invalid, but the node
   handling the local repair MAY flag each such newly lost route as
   locally repairable; this local repair flag in the route table MUST be
   reset when the route times out (e.g., after the route has been not
   been active for ACTIVE_ROUTE_TIMEOUT). Before the timeout occurs,
   these other routes will be repaired as needed when packets arrive for
   the other destinations.  Hence, these routes are repaired as needed;
   if a data packet does not arrive for the route, then that route will
   not be repaired.  Alternatively, depending upon local congestion,
   the node MAY begin the process of establishing local repairs for
   the other routes, without waiting for new packets to arrive.  By
   proactively repairing the routes that have broken due to the loss
   of the link, incoming data packets for those routes will not be
   subject to the delay of repairing the route and can be immediately
   forwarded.  However, repairing the route before a data packet is
   received for it runs the risk of repairing routes that are no longer
   in use.  Therefore, depending upon the local traffic in the network
   and whether congestion is being experienced, the node MAY elect to
   proactively repair the routes before a data packet is received;
   otherwise, it can wait until a data is received, and then commence
   the repair of the route.


5.13. Actions After Reboot

   A node participating in the ad hoc network must take certain actions
   after reboot as it might lose all sequence number records for all
   destinations, including its own sequence number.  However, there
   may be neighboring nodes that are using this node as an active next
   hop.  This can potentially create routing loops.  To prevent this
   possibility, each node on reboot waits for DELETE_PERIOD. During this
   time, the node does not transmit any RREP messages.  If the node
   receives a RREQ, RREP, or RERR control packet, it SHOULD create route
   entries as appropriate given the sequence number information in the
   control packets, but MUST not forward any control packets.  If the
   node receives a data packet for some other destination, it SHOULD
   broadcast a RERR as described in subsection 5.11 and MUST reset the
   waiting timer to expire after current time plus DELETE_PERIOD.





Perkins, Belding-Royer, Das         Expires 4 May 2003         [Page 24]

Internet Draft                   AODV                    4 November 2002


   It can be shown [1] that by the time the rebooted node comes out of
   the waiting phase and becomes an active router again, none of its
   neighbors will be using it as an active next hop any more.  Its own
   sequence number gets updated once it receives a RREQ from any other
   node, as the RREQ always carries the maximum destination sequence
   number seen en route.


5.14. Interfaces

   Because AODV should operate smoothly over wired, as well as wireless,
   networks, and because it is likely that AODV will also be used with
   multi-homed radios, the interface over which packets arrive must
   be known to AODV whenever a packet is received.  This includes the
   reception of RREQ, RREP, and RERR messages.  Whenever a packet is
   received from a new neighbor, the interface on which that packet was
   received is recorded into the route table entry for that neighbor,
   along with all the other appropriate routing information.  Similarly,
   whenever a route to a new destination is learned, the interface
   through which the destination can be reached is also recorded into
   the destination's route table entry.

   When multiple interfaces are available, a node retransmitting a RREQ
   message rebroadcasts that message on all interfaces that have been
   configured for operation in the ad-hoc network, except those on which
   it is known that all of the nodes neighbors have already received
   the RREQ For instance, for some broadcast media (e.g., Ethernet) it
   may be presumed that all nodes on the same link receive a broadcast
   message at the same time.  When a node needs to transmit a RERR, it
   SHOULD only transmit it on those interfaces that have precursor nodes
   for that route.


6. AODV and Aggregated Networks

   AODV has been designed for use by mobile nodes with IP addresses
   that are not necessarily related to each other, to create an ad hoc
   network.  However, in some cases a collection of mobile nodes MAY
   operate in a fixed relationship to each other and share a common
   subnet prefix, moving together within an area where an ad hoc network
   has formed.  Call such a collection of nodes a ``subnet''.  In this
   case, it is possible for a single node within the subnet to advertise
   reachability for all other nodes on the subnet, by responding with
   a RREP message to any RREQ message requesting a route to any node
   with the subnet routing prefix.  Call the single node the ``subnet
   router''.  In order for a subnet router to operate the AODV protocol
   for the whole subnet, it has to maintain a destination sequence
   number for the entire subnet.  In any such RREP message sent by the
   subnet router, the Prefix Size field of the RREP message MUST be



Perkins, Belding-Royer, Das         Expires 4 May 2003         [Page 25]

Internet Draft                   AODV                    4 November 2002


   set to the length of the subnet prefix.  Other nodes sharing the
   subnet prefix SHOULD NOT issue RREP messages, and SHOULD forward RREQ
   messages to the subnet leader.

   If several nodes in the subnet advertise reachability to the subnet
   defined by the subnet prefix, the node with the lowest IP address
   is elected to be the subnet leader, and all other nodes MUST stop
   advertising reachability.

   The behavior of default routes (i.e., routes with routing prefix
   length 0) is not defined in this specification.  Selection of routes
   sharing prefix bits should be according to longest match first.


7. Using AODV with Other Networks

   In some configurations, an ad hoc network may be able to provide
   connectivity between external routing domains that do not use AODV.
   If the points of contact to the other networks can act as subnet
   routers (see Section 6) for any relevant networks within the external
   routing domains, then the ad hoc network can maintain connectivity to
   the external routing domains.  Indeed, the external routing networks
   can use the ad hoc network defined by AODV as a transit network.

   In order to provide this feature, a point of contact to an external
   network (call it an Infrastructure Router) has to act as the subnet
   router for every subnet of interest within the external network for
   which the Infrastructure Router can provide reachability.  This
   includes the need for maintaining a destination sequence number for
   that external subnet.

   If multiple Infrastructure Routers offer reachability to the same
   external subnet, those Infrastructure Routers have to cooperate (by
   means outside the scope of this specification) to provide consistent
   AODV semantics for ad hoc access to those subnets.


8. Extensions

   In this section, the format of extensions to the RREQ and RREP
   messages is specified.  All such extensions appear after the message
   data, and have the following format:

    0                   1                   2                   3
    0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
   +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
   |     Type      |    Length     |     type-specific data ...
   +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+




Perkins, Belding-Royer, Das         Expires 4 May 2003         [Page 26]

Internet Draft                   AODV                    4 November 2002


   where:

      Type     1-255

      Length   The length of the type-specific data, not including the
               Type and Length fields of the extension in bytes.

   Extensions with types between 128 and 255 may NOT be skipped.  The
   rules for extensions will be spelled out more fully, and conform to
   the rules for handling IPv6 options.


8.1. Hello Interval Extension Format

    0                   1                   2                   3
    0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
   +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
   |     Type      |    Length     |       Hello Interval ...      |
   +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
   | ... Hello Interval, continued |
   +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+

      Type     2

      Length   4

      Hello Interval
               The number of milliseconds between successive
               transmissions of a Hello message.

   The Hello Interval extension MAY be appended to a RREP message with
   TTL == 1, to be used by a neighboring receiver in determine how long
   to wait for subsequent such RREP messages (i.e., Hello messages; see
   section 5.9).


9. Configuration Parameters

   This section gives default values for some important parameters
   associated with AODV protocol operations.  A particular mobile node
   may wish to change certain of the parameters, in particular the
   NET_DIAMETER, MY_ROUTE_TIMEOUT, ALLOWED_HELLO_LOSS, RREQ_RETRIES,
   and possibly the HELLO_INTERVAL. In the latter case, the node
   should advertise the HELLO_INTERVAL in its Hello messages, by
   appending a Hello Interval Extension to the RREP message.  Choice
   of these parameters may affect the performance of the protocol.
   Changing NODE_TRAVERSAL_TIME also changes the node's estimate
   of the NET_TRAVERSAL_TIME, and so can only be done with suitable
   knowledge about the behavior of other nodes in the ad hoc network.



Perkins, Belding-Royer, Das         Expires 4 May 2003         [Page 27]

Internet Draft                   AODV                    4 November 2002


   The configured value for MY_ROUTE_TIMEOUT MUST be at least 2 *
   PATH_DISCOVERY_TIME.

      Parameter Name           Value
      ----------------------   -----
      ACTIVE_ROUTE_TIMEOUT     3,000 Milliseconds
      ALLOWED_HELLO_LOSS       2
      BLACKLIST_TIMEOUT        RREQ_RETRIES * NET_TRAVERSAL_TIME
      DELETE_PERIOD            see note below
      HELLO_INTERVAL           1,000 Milliseconds
      LOCAL_ADD_TTL            2
      MAX_REPAIR_TTL           0.3 * NET_DIAMETER
      MIN_REPAIR_TTL           see note below
      MY_ROUTE_TIMEOUT         2 * ACTIVE_ROUTE_TIMEOUT
      NET_DIAMETER             35
      NET_TRAVERSAL_TIME       2 * NODE_TRAVERSAL_TIME * NET_DIAMETER
      NEXT_HOP_WAIT            NODE_TRAVERSAL_TIME + 10
      NODE_TRAVERSAL_TIME      40
      PATH_DISCOVERY_TIME      2 * NET_TRAVERSAL_TIME
      RERR_RATELIMIT           10
      RING_TRAVERSAL_TIME      2 * NODE_TRAVERSAL_TIME * (TTL_VALUE + TIMEOUT_BUFFER)
      RREQ_RETRIES             2
      RREQ_RATELIMIT           10
      TIMEOUT_BUFFER           2
      TTL_START                1
      TTL_INCREMENT            2
      TTL_THRESHOLD            7
      TTL_VALUE                see note below


   The MIN_REPAIR_TTL should be the last known hop count to
   the destination.  If Hello messages are used, then the
   ACTIVE_ROUTE_TIMEOUT parameter value MUST be more than the
   value (ALLOWED_HELLO_LOSS * HELLO_INTERVAL).

   TTL_VALUE is the value of the TTL field in the IP header while the
   expanding ring search is being performed.  This is described further
   in section 5.4.  The TIMEOUT_BUFFER is configurable.  Its purpose is
   to provide a buffer for the timeout so that if the RREP is delayed
   due to congestion, a timeout is less likely to occur while the RREP
   is still en route back to the source.  To omit this buffer, set
   TIMEOUT_BUFFER = 0.

   DELETE_PERIOD should be an upper bound on the time for which an
   upstream node A can have a neighbor B as an active next hop for
   destination D, while B has invalidated the route to D. Beyond this
   time B can delete the route to D. The determination of the upper
   bound somewhat depends on the characteristics of the underlying
   link layer.  If Hello messages are used to determine the continued



Perkins, Belding-Royer, Das         Expires 4 May 2003         [Page 28]

Internet Draft                   AODV                    4 November 2002


   availability of links to next hop nodes, DELETE_PERIOD must be at
   least ALLOWED_HELLO_LOSS * HELLO_INTERVAL. If the link layer feedback
   is used to detect loss of link, DELETE_PERIOD must be at least
   ACTIVE_ROUTE_TIMEOUT. If hello messages are received from a neighbor
   but data packets to that neighbor are lost, (due to temporary link
   asymmetry, e.g.)  we have to make more concrete assumptions about
   the underlying link layer.  We assume that such asymmetry cannot
   persist beyond a certain time, say, a multiple K of HELLO_INTERVAL.
   In other words, a node will invariably receive at least one out
   of K subsequent Hello messages from a neighbor if the link is
   working and the neighbor is sending no other traffic.  Covering all
   possibilities,

DELETE_PERIOD = K * max (ACTIVE_ROUTE_TIMEOUT, HELLO_INTERVAL) (K = 5 is
                             recommended).

   NET_DIAMETER measures the maximum possible number of hops between
   two nodes in the network.  NODE_TRAVERSAL_TIME is a conservative
   estimate of the average one hop traversal time for packets and should
   include queuing delays, interrupt processing times and transfer
   times.  ACTIVE_ROUTE_TIMEOUT SHOULD be set to a longer value (at
   least 10,000 milliseconds) if link-layer indications are used to
   detect link breakages such as in IEEE 802.11 [4] standard.  TTL_START
   should be set to at least 2 if Hello messages are used for local
   connectivity information.  Performance of the AODV protocol is
   sensitive to the chosen values of these constants, which often depend
   on the characteristics of the underlying link layer protocol, radio
   technologies etc.  BLACKLIST_TIMEOUT should be suitably increased
   if an expanding ring search is used.  In such cases, it should be
   [(TTL_THRESHOLD - TTL_START)/TTL_INCREMENT] + 1 + RREQ_RETRIES *
   NET_TRAVERSAL_TIME. This is to account for possible additional route
   discovery attempts.


10. Security Considerations

   Currently, AODV does not specify any special security measures.
   Route protocols, however, are prime targets for impersonation
   attacks.  If there is danger of such attacks, AODV control messages
   must be protected by use of authentication techniques, such as those
   involving generation of unforgeable and cryptographically strong
   message digests or digital signatures.  In particular, RREP messages
   SHOULD be authenticated to avoid creation of spurious routes to a
   desired destination.  Otherwise, an attacker could masquerade as the
   desired destination, and maliciously deny service to the destination
   and/or maliciously inspect and consume traffic intended for delivery
   to the destination.  RERR messages, while less dangerous, SHOULD be
   authenticated in order to prevent malicious nodes from disrupting
   valid routes between nodes that are communication partners.



Perkins, Belding-Royer, Das         Expires 4 May 2003         [Page 29]

Internet Draft                   AODV                    4 November 2002


   Since AODV does not make any assumption about the nature of the
   address assignment to the mobile nodes except that they are presumed
   to have unique IP addresses, no definite statements can be made about
   the applicability of IPsec authentication headers or key exchange
   mechanisms.  However, if the mobile nodes in the ad hoc network have
   pre-established security associations, they should be able to use the
   same authentication mechanisms based on their IP addresses as they
   would have used otherwise.


11. IPv6 Considerations

   See [6] for detailed operation for IPv6.  The only changes to the
   protocol are that the address fields are enlarged.


12. Acknowledgments

   Special thanks to Ian Chakeres, UCSB, for his extensive suggestions
   and contributions to this revision.

   We acknowledge with gratitude the work done at University of
   Pennsylvania within Carl Gunter's group, as well as at Stanford and
   CMU, to determine some conditions (especially involving reboots and
   lost RERRs) under which previous versions of AODV could suffer from
   routing loops.  Contributors to those efforts include Karthikeyan
   Bhargavan, Joshua Broch, Dave Maltz, Madanlal Musuvathi, and
   Davor Obradovic.  The idea of a DELETE_PERIOD, for which expired
   routes (and, in particular, the sequence numbers) to a particular
   destination must be maintained, was also suggested by them.

   We also acknowledge the comments and improvements suggested by
   Sung-Ju Lee (especially regarding local repair), Mahesh Marina, Erik
   Nordstrom (who provided text for section 5.11), Yves Prelot, Marc
   Mosko, Manel Guerrero Zapata, Philippe Jacquet, and Fred Baker.


References

   [1] Karthikeyan Bhargavan, Carl A. Gunter, and Davor Obradovic.
       Fault Origin Adjudication.  In Proceedings of the Workshop on
       Formal Methods in Software Practice, Portland, OR, August 2000.

   [2] S. Bradner.  Key words for use in RFCs to Indicate Requirement
       Levels.  Request for Comments (Best Current Practice) 2119,
       Internet Engineering Task Force, March 1997.

   [3] J. Manner et al.  Mobility Related Terminology (work in
       progress).  draft-manner-seamoby-terms-02.txt, July 2001.



Perkins, Belding-Royer, Das         Expires 4 May 2003         [Page 30]

Internet Draft                   AODV                    4 November 2002


   [4] IEEE 802.11 Committee, AlphaGraphics #35, 10201 N.35th Avenue,
       Phoenix AZ 85051.  Wireless LAN Medium Access Control MAC and
       Physical Layer PHY Specifications, June 1997.  IEEE Standard
       802.11-97.

   [5] D. Mills.  Simple Network Time Protocol (SNTP) Version 4 for
       IPv4, IPv6 and OSI.  Request for Comments (Informational) 2030,
       Internet Engineering Task Force, October 1996.

   [6] C. Perkins, E. Royer, and S. Das.  Ad Hoc On Demand Distance
       Vector (AODV) Routing for IP version 6 (work in progress).
       Internet Draft, Internet Engineering Task Force.
       draft-perkins-manet-aodv6-01.txt, November 2001.







































Perkins, Belding-Royer, Das         Expires 4 May 2003         [Page 31]

Internet Draft                   AODV                    4 November 2002


A. Draft Modifications

   The following are major changes between this version (12) of the AODV
   draft and the previous version (11):

	- Added binary exponential backoff to repeated RREQ attempts
   for the same destination.

	- Included a mechanism for dynamically calculating the waiting
   time for a RREP during an expanding ring search.  This includes the
   addition of a new parameter, RING_TRAVERSAL_TIME.

	- Added the TTL_VALUE and TIMEOUT_BUFFER parameters to help
   dynamically calculate the waiting time for a RREP during an
   expanding ring search.

	- Clarified the option of proactive local repair for recently
   broken routes.









	




Perkins, Belding-Royer, Das         Expires 4 May 2003         [Page 32]

Internet Draft                   AODV                    4 November 2002


Author's Addresses

   Questions about this memo can be directed to:

      Charles E. Perkins
      Communications Systems Laboratory
      Nokia Research Center
      313 Fairchild Drive
      Mountain View, CA 94303
      USA
      +1 650 625 2986
      +1 650 691 2170 (fax)
      charliep@iprg.nokia.com


      Elizabeth M. Belding-Royer
      Department of Computer Science
      University of California, Santa Barbara
      Santa Barbara, CA 93106
      +1 805 893 3411
      +1 805 893 8553 (fax)
      ebelding@cs.ucsb.edu


      Samir R. Das
      Department of Electrical and Computer Engineering
      & Computer Science
      University of Cincinnati
      Cincinnati, OH 45221-0030
      +1 513 556 2594
      +1 513 556 7326 (fax)
      sdas@ececs.uc.edu




















Perkins, Belding-Royer, Das         Expires 4 May 2003         [Page 33]

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


From mailnull@www1.ietf.org  Fri Nov 15 16:37:43 2002
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA20211
	for <manet-archive@odin.ietf.org>; Fri, 15 Nov 2002 16:37:43 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id gAFLdrH18931
	for manet-archive@odin.ietf.org; Fri, 15 Nov 2002 16:39:53 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gAFLdrv18928
	for <manet-web-archive@optimus.ietf.org>; Fri, 15 Nov 2002 16:39:53 -0500
Received: from www1.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA20193
	for <manet-web-archive@ietf.org>; Fri, 15 Nov 2002 16:37:07 -0500 (EST)
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gAFLGfv16976;
	Fri, 15 Nov 2002 16:16:41 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gA7HU3v01487
	for <manet@optimus.ietf.org>; Thu, 7 Nov 2002 12:30:03 -0500
Received: from letters.cs.ucsb.edu (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA03123
	for <manet@ietf.org>; Thu, 7 Nov 2002 12:27:24 -0500 (EST)
Received: from saguaro (saguaro [128.111.40.82])
	by letters.cs.ucsb.edu (8.11.6+Sun/8.11.6) with SMTP id gA7HTrm24121
	for <manet@ietf.org>; Thu, 7 Nov 2002 09:29:53 -0800 (PST)
Message-Id: <200211071729.gA7HTrm24121@letters.cs.ucsb.edu>
Date: Thu, 7 Nov 2002 09:29:53 -0800 (PST)
From: "Elizabeth M. Belding-Royer" <ebelding@cs.ucsb.edu>
Reply-To: "Elizabeth M. Belding-Royer" <ebelding@cs.ucsb.edu>
To: manet@ietf.org
MIME-Version: 1.0
Content-Type: MULTIPART/mixed; BOUNDARY=Covey_of_Quail_388_000
X-Mailer: dtmail 1.3.0 @(#)CDE Version 1.3.5 SunOS 5.7 sun4u sparc 
Subject: [manet] New AODV draft
Sender: manet-admin@ietf.org
Errors-To: manet-admin@ietf.org
X-BeenThere: manet@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/manet>,
	<mailto:manet-request@ietf.org?subject=unsubscribe>
List-Id: Mobile Ad-hoc Networks  <manet.ietf.org>
List-Post: <mailto:manet@ietf.org>
List-Help: <mailto:manet-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/manet>,
	<mailto:manet-request@ietf.org?subject=subscribe>

--Covey_of_Quail_388_000
Content-Type: TEXT/plain; charset=us-ascii
Content-MD5: C9+DARvbzHh+1W0nuzZmxg==

Hi,

The AODV draft version 12 that was just announced does not have
the updated list of changes at the end.  We resubmitted the 
correct version before the deadline, but I guess it hasn't been
processed yet.  In the meantime, attached is the version we
resubmitted to the IETF directory.  It has the updated list of
changes; otherwise, its identical to the draft that was announced
early this morning.

Elizabeth

--Covey_of_Quail_388_000
Content-Type: TEXT/plain; name="aodvid.txt"; charset=us-ascii; x-unix-mode=0600
Content-Description: aodvid.txt
Content-MD5: NLP/O9yDLmBB92/3A24OsA==


Mobile Ad Hoc Networking Working Group                Charles E. Perkins
INTERNET DRAFT                                     Nokia Research Center
4 November 2002                               Elizabeth M. Belding-Royer
                                 University of California, Santa Barbara
                                                            Samir R. Das
                                                University of Cincinnati

            Ad hoc On-Demand Distance Vector (AODV) Routing
                      draft-ietf-manet-aodv-12.txt


Status of This Memo

   This document is a submission by the Mobile Ad Hoc Networking Working
   Group of the Internet Engineering Task Force (IETF).  Comments should
   be submitted to the manet@ietf.org mailing list.

   Distribution of this memo is unlimited.

   This document is an Internet-Draft and is in full conformance with
   all provisions of Section 10 of RFC2026.  Internet-Drafts are working
   documents of the Internet Engineering Task Force (IETF), its areas,
   and its working groups.  Note that other groups may also distribute
   working documents as Internet-Drafts.

   Internet-Drafts are draft documents valid for a maximum of six months
   and may be updated, replaced, or obsoleted by other documents at
   any time.  It is inappropriate to use Internet-Drafts as reference
   material or to cite them other than as "work in progress."

   The list of current Internet-Drafts can be accessed at:
        http://www.ietf.org/ietf/1id-abstracts.txt
   The list of Internet-Draft Shadow Directories can be accessed at:
        http://www.ietf.org/shadow.html.


Abstract

   The Ad hoc On-Demand Distance Vector (AODV) routing protocol
   is intended for use by mobile nodes in an ad hoc network.  It
   offers quick adaptation to dynamic link conditions, low processing
   and memory overhead, low network utilization, and determines
   unicast routes to destinations within the ad hoc network.  It uses
   destination sequence numbers to ensure loop freedom at all times
   (even in the face of anomalous delivery of routing control messages),
   avoiding problems (such as ``counting to infinity'') associated with
   classical distance vector protocols.








Perkins, Belding-Royer, Das         Expires 4 May 2003          [Page i]

Internet Draft                   AODV                    4 November 2002




                                Contents


Status of This Memo                                                    i

Abstract                                                               i

 1. Introduction                                                       1

 2. Overview                                                           1

 3. AODV Terminology                                                   3

 4. Message Formats                                                    5
     4.1. Route Request (RREQ) Message Format . . . . . . . . . . .    5
     4.2. Route Reply (RREP) Message Format . . . . . . . . . . . .    6
     4.3. Route Error (RERR) Message Format . . . . . . . . . . . .    8
     4.4. Route Reply Acknowledgment (RREP-ACK) Message Format  . .    9

 5. AODV Operation                                                     9
     5.1. Maintaining Sequence Numbers  . . . . . . . . . . . . . .    9
     5.2. Route Table Entries and Precursor Lists . . . . . . . . .   11
     5.3. Generating Route Requests . . . . . . . . . . . . . . . .   12
     5.4. Controlling Dissemination of Route Request Messages . . .   13
     5.5. Processing and Forwarding Route Requests  . . . . . . . .   14
     5.6. Generating Route Replies  . . . . . . . . . . . . . . . .   15
           5.6.1. Route Reply Generation by the Destination . . . .   16
           5.6.2. Route Reply Generation by an Intermediate Node  .   16
           5.6.3. Generating Gratuitous RREPs . . . . . . . . . . .   17
     5.7. Receiving and Forwarding Route Replies  . . . . . . . . .   17
     5.8. Operation over Unidirectional Links . . . . . . . . . . .   19
     5.9. Hello Messages  . . . . . . . . . . . . . . . . . . . . .   19
    5.10. Maintaining Local Connectivity  . . . . . . . . . . . . .   20
    5.11. Route Error Messages, Route Expiry and Route Deletion . .   21
    5.12. Local Repair  . . . . . . . . . . . . . . . . . . . . . .   23
    5.13. Actions After Reboot  . . . . . . . . . . . . . . . . . .   24
    5.14. Interfaces  . . . . . . . . . . . . . . . . . . . . . . .   25

 6. AODV and Aggregated Networks                                      25

 7. Using AODV with Other Networks                                    26

 8. Extensions                                                        26
     8.1. Hello Interval Extension Format . . . . . . . . . . . . .   27

 9. Configuration Parameters                                          27




Perkins, Belding-Royer, Das         Expires 4 May 2003         [Page ii]

Internet Draft                   AODV                    4 November 2002


10. Security Considerations                                           29

11. IPv6 Considerations                                               30

12. Acknowledgments                                                   30

 A. Draft Modifications                                               32


1. Introduction

   The Ad hoc On-Demand Distance Vector (AODV) algorithm enables
   dynamic, self-starting, multihop routing between participating mobile
   nodes wishing to establish and maintain an ad hoc network.  AODV
   allows mobile nodes to obtain routes quickly for new destinations,
   and does not require nodes to maintain routes to destinations that
   are not in active communication.  AODV allows mobile nodes to respond
   to link breakages and changes in network topology in a timely manner.
   The operation of AODV is loop-free, and by avoiding the Bellman-Ford
   ``counting to infinity'' problem offers quick convergence when the
   ad hoc network topology changes (typically, when a node moves in the
   network).  When links break, AODV causes the affected set of nodes to
   be notified so that they are able to invalidate the routes using the
   lost link.

   One distinguishing feature of AODV is its use of a destination
   sequence number for each route entry.  The destination sequence
   number is created by the destination for any route information it
   sends to requesting nodes.  Using destination sequence numbers
   ensures loop freedom and is simple to program.  Given the choice
   between two routes to a destination, a requesting node always selects
   the one with the greatest sequence number.


2. Overview

   Route Requests (RREQs), Route Replies (RREPs), and Route Errors
   (RERRs) are the message types defined by AODV. These message types
   are received via UDP, and normal IP header processing applies.
   So, for instance, the requesting node is expected to use its IP
   address as the Originator IP address for the messages.  For broadcast
   messages, the IP limited broadcast address (255.255.255.255) is used.
   This means that such messages are not blindly forwarded.  However,
   AODV operation does require certain messages (e.g., RREQ) to be
   disseminated widely, perhaps throughout the ad hoc network.  The
   range of dissemination of such RREQs is indicated by the TTL in the
   IP header.  Fragmentation is typically not required.





Perkins, Belding-Royer, Das         Expires 4 May 2003          [Page 1]

Internet Draft                   AODV                    4 November 2002


   As long as the endpoints of a communication connection have valid
   routes to each other, AODV does not play any role.  When a route to a
   new destination is needed, the node broadcasts a RREQ to find a route
   to the destination.  A route can be determined when the RREQ reaches
   either the destination itself, or an intermediate node with a 'fresh
   enough' route to the destination.  A 'fresh enough' route is a valid
   route entry for the destination whose associated sequence number is
   at least as great as that contained in the RREQ. The route is made
   available by unicasting a RREP back to the origination of the RREQ.
   Each node receiving the request caches a route back to the originator
   of the request, so that the RREP can be unicast from the destination
   along a path to that originator, or likewise from any intermediate
   node that is able to satisfy the request.

   Nodes monitor the link status of next hops in active routes.  When a
   link break in an active route is detected, a RERR message is used to
   notify other nodes that the loss of that link has occurred.  The RERR
   message indicates those destinations which are now unreachable due to
   the loss of the link.  In order to enable this reporting mechanism,
   each node keeps a ``precursor list'', containing the IP address for
   each its neighbors that are likely to use it as a next hop towards
   the destination that is now unreachable.  The information in the
   precursor lists is most easily acquired during the processing for
   generation of a RREP message, which by definition has to be sent to a
   node in a precursor list (see section 5.6).

   A RREQ may also be received for a multicast IP address.  In this
   document, full processing for such messages is not specified.  For
   example, the originator of such a RREQ for a multicast IP address
   may have to follow special rules.  However, it is important to
   enable correct multicast operation by intermediate nodes that are
   not enabled as originating or destination nodes for IP multicast
   addresses, and likewise are not equipped for any special multicast
   protocol processing.  For such multicast-unaware nodes, processing
   for a multicast IP address as a destination IP address MUST be
   carried out in the same way as for any other destination IP address.

   AODV is a routing protocol, and it deals with route table
   management.  Route table information must be kept even
   for short-lived routes, such as are created to temporarily
   store reverse paths towards nodes originating RREQs.  AODV











Perkins, Belding-Royer, Das         Expires 4 May 2003          [Page 2]

Internet Draft                   AODV                    4 November 2002


   uses the following fields with each route table entry:

       -  Destination IP Address
       -  Destination Sequence Number
       -  Valid Destination Sequence Number
       -  Interface
       -  Hop Count (number of hops needed to reach destination)
       -  Next Hop
       -  List of Precursors (described in Section 5.2)
       -  Lifetime (expiration or deletion time of the route)
       -  Routing Flags
       -  State

   Managing the sequence number is crucial to avoiding routing loops,
   even when links break and a node is no longer reachable to supply
   its own information about its sequence number.  A destination
   becomes unreachable when a link breaks or is deactivated.  When these
   conditions occur, the route is invalidated by operations involving
   the sequence number and marking the route table entry state as
   invalid.  See section 5.1 for details.


3. AODV Terminology

   This protocol specification uses conventional meanings [2] for
   capitalized words such as MUST, SHOULD, etc., to indicate requirement
   levels for various protocol features.  This section defines other
   terminology used with AODV that is not already defined in [3].

      active route

         A route towards a destination that has a routing table entry
         that is marked as valid.  Only active routes can be used to
         forward data packets.

      broadcast

         Broadcasting means transmitting to the IP Limited Broadcast
         address, 255.255.255.255.  A broadcast packet may not be
         blindly forwarded, but broadcasting is useful to enable
         dissemination of AODV messages throughout the ad hoc network.

      destination

         An IP address to which data packets are to be transmitted.
         Same as "destination node".  A node knows it is the destination
         node for a data packet when its address appears in the
         appropriate field of the IP header.  Routes for destination
         nodes are supplied by action of the AODV protocol, which



Perkins, Belding-Royer, Das         Expires 4 May 2003          [Page 3]

Internet Draft                   AODV                    4 November 2002


         carries the IP address of the destination node in route
         discovery messages.

      forwarding node

         A node that agrees to forward packets destined for another
         node, by retransmitting them to a next hop that is closer to
         the unicast destination along a path that has been set up using
         routing control messages.

      forward route

         A route set up to send data packets from a node originating a
         Route Discovery operation towards its desired destination.

      invalid route

         A route that has expired, denoted by a state of invalid in
         the routing table.  An invalid route is used to store the
         previously valid route information for an extended period
         of time.  An invalid route may not be used to forward data
         packets.

      originating node

         A node that initiates an AODV message to be processed and
         possibly retransmitted by other nodes in the ad hoc network.
         For instance, the node initiating a Route Discovery process and
         broadcasting the RREQ message is called the originating node of
         the RREQ message.

      reverse route

         A route set up to forward a reply (RREP) packet back to the
         originator from the destination or from an intermediate node
         having a route to the destination.

      sequence number

         An increasing number maintained by each originating node.  When
         used in control messages it is used by other nodes to determine
         the freshness of the information contained from the originating
         node.

      valid route

         See active route.





Perkins, Belding-Royer, Das         Expires 4 May 2003          [Page 4]

Internet Draft                   AODV                    4 November 2002


4. Message Formats

4.1. Route Request (RREQ) Message Format

    0                   1                   2                   3
    0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
   +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
   |     Type      |J|R|G|D|U|   Reserved          |   Hop Count   |
   +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
   |                            RREQ ID                            |
   +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
   |                    Destination IP Address                     |
   +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
   |                  Destination Sequence Number                  |
   +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
   |                    Originator IP Address                      |
   +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
   |                  Originator Sequence Number                   |
   +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+

   The format of the Route Request message is illustrated above, and
   contains the following fields:

      Type           1

      J              Join flag; reserved for multicast.

      R              Repair flag; reserved for multicast.

      G              Gratuitous RREP flag; indicates whether a
                     gratuitous RREP should be unicast to the node
                     specified in the Destination IP Address field (see
                     sections 5.3, 5.6.3)

      D              Destination only flag; indicates only the
                     destination may respond to this RREQ (see
                     section 5.5).

      U              Unknown sequence number; indicates the destination
                     sequence number is unknown(see section 5.3).

      Reserved       Sent as 0; ignored on reception.

      Hop Count      The number of hops from the Originator IP Address
                     to the node handling the request.

      RREQ ID        A sequence number uniquely identifying the
                     particular RREQ when taken in conjunction with the
                     originating node's IP address.



Perkins, Belding-Royer, Das         Expires 4 May 2003          [Page 5]

Internet Draft                   AODV                    4 November 2002


      Destination IP Address
                     The IP address of the destination for which a route
                     is desired.

      Destination Sequence Number
                     The greatest sequence number received in the
                     past by the originator for any route towards the
                     destination.

      Originator IP Address
                     The IP address of the node which originated the
                     Route Request.

      Originator Sequence Number
                     The current sequence number to be used for
                     route entries pointing to (and generated by) the
                     originator of the route request.


4.2. Route Reply (RREP) Message Format

    0                   1                   2                   3
    0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
   +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
   |     Type      |R|A|    Reserved     |Prefix Sz|   Hop Count   |
   +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
   |                     Destination IP address                    |
   +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
   |                  Destination Sequence Number                  |
   +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
   |                    Originator IP address                      |
   +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
   |                           Lifetime                            |
   +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+

   The format of the Route Reply message is illustrated above, and
   contains the following fields:

      Type          2

      R             Repair flag; used for multicast.

      A             Acknowledgment required; see sections 4.4 and 5.7.

      Reserved      Sent as 0; ignored on reception.

      Prefix Size   If nonzero, the 5-bit Prefix Size specifies that the
                    indicated next hop may be used for any nodes with




Perkins, Belding-Royer, Das         Expires 4 May 2003          [Page 6]

Internet Draft                   AODV                    4 November 2002


                    the same routing prefix (as defined by the Prefix
                    Size) as the requested destination.

      Hop Count     The number of hops from the Originator IP Address
                    to the Destination IP Address.  For multicast route
                    requests this indicates the number of hops to the
                    multicast tree member sending the RREP.

      Destination IP Address
                    The IP address of the destination for which a route
                    is supplied.

      Destination Sequence Number
                    The destination sequence number associated to the
                    route.

      Originator IP Address
                    The IP address of the node which originated the RREQ
                    for which the route is supplied.

      Lifetime      The time in milliseconds for which nodes receiving
                    the RREP consider the route to be valid.

   Note that the Prefix Size allows a Subnet Leader to supply a route
   for every host in the subnet defined by the routing prefix, which
   is determined by the IP address of the Subnet Leader and the Prefix
   Size.  In order to make use of this feature, the Subnet Leader has to
   guarantee reachability to all the hosts sharing the indicated subnet
   prefix.  The Subnet Leader is also responsible for maintaining the
   Destination Sequence Number for the whole subnet.  See section 6 for
   details.

   The 'A' bit is used in cases where the link over which the RREP
   message is sent may be unreliable or unidirectional.  When the
   RREP message contains the 'A' bit set, the receiver of the RREP is
   expected to return a RREP-ACK message.  See section 5.8.
















Perkins, Belding-Royer, Das         Expires 4 May 2003          [Page 7]

Internet Draft                   AODV                    4 November 2002


4.3. Route Error (RERR) Message Format

    0                   1                   2                   3
    0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
   +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
   |     Type      |N|          Reserved           |   DestCount   |
   +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
   |            Unreachable Destination IP Address (1)             |
   +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
   |         Unreachable Destination Sequence Number (1)           |
   +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-|
   |  Additional Unreachable Destination IP Addresses (if needed)  |
   +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
   |Additional Unreachable Destination Sequence Numbers (if needed)|
   +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+


   The format of the Route Error message is illustrated above, and
   contains the following fields:

      Type        3

      N           No delete flag; set when a node has performed a local
                  repair of a link, and upstream nodes should not delete
                  the route.

      Reserved    Sent as 0; ignored on reception.

      DestCount   The number of unreachable destinations included in the
                  message; MUST be at least 1.

      Unreachable Destination IP Address
                  The IP address of the destination that has become
                  unreachable due to a link break.

      Unreachable Destination Sequence Number
                  The sequence number in the route table entry for
                  the destination listed in the previous Unreachable
                  Destination IP Address field.

   The RERR message is sent whenever a link break causes one or more
   destinations to become unreachable from some of the node's neighbors.
   See section 5.2 for information about how to maintain the appropriate
   records for this determination, and section 5.11 for specification
   about how to create the list of destinations.







Perkins, Belding-Royer, Das         Expires 4 May 2003          [Page 8]

Internet Draft                   AODV                    4 November 2002


4.4. Route Reply Acknowledgment (RREP-ACK) Message Format

   The Route Reply Acknowledgment (RREP-ACK) message MUST be sent in
   response to a RREP message with the 'A' bit set (see section 4.2.
   This is typically done when there is danger of unidirectional
   links preventing the completion of a Route Discovery cycle (see
   section 5.8).

    0                   1
    0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5
   +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
   |     Type      |   Reserved    |
   +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+


      Type        4

      Reserved    Sent as 0; ignored on reception.


5. AODV Operation

   This section describes the scenarios under which nodes generate Route
   Request (RREQ), Route Reply (RREP) and Route Error (RERR) messages
   for unicast communication towards a destination, and how the message
   data are handled.  In order to process the messages correctly,
   certain state information has to be maintained in the route table
   entries for the destinations of interest.

   All AODV messages are sent to port 654 using UDP.


5.1. Maintaining Sequence Numbers

   Every route table entry at every node MUST include the latest
   information available about the sequence number for the IP address of
   the destination node for which the route table entry is maintained.
   This sequence number is called the "destination sequence number".  It
   is updated whenever a node receives new (i.e., not stale) information
   about the sequence number from RREQ, RREP, or RERR messages that
   may be received related to that destination.  AODV depends on each
   node in the network to own and maintain its destination sequence
   number to guarantee the loop-freedom of all routes towards that
   node.  A destination node increments its own sequence number in two
   circumstances:

    -  Immediately before a node originates a route discovery, it MUST
       increment its own sequence number.  This prevents problems with
       deleted reverse routes to the originator of a RREQ.



Perkins, Belding-Royer, Das         Expires 4 May 2003          [Page 9]

Internet Draft                   AODV                    4 November 2002


    -  Immediately before a destination node originates a RREP in
       response to a RREQ, it MUST update its own sequence number to
       the maximum of its current sequence number and the destination
       sequence number in the RREQ packet.

   When the destination increments its sequence number, it MUST do so
   by treating the sequence number value as if it were an unsigned
   number.  To accomplish sequence number rollover, if the sequence
   number has already been assigned to be the largest possible number
   representable as a 32-bit unsigned integer (i.e., 4294967295), then
   when it is incremented it will then have a value of zero (0).  On
   the other hand, if the sequence number currently has the value
   2147483647, which is the largest possible positive integer if 2's
   complement arithmetic is in use with 32-bit integers, the next value
   will be 2147483648, which is the most negative possible integer in
   the same numbering system.  The representation of negative numbers
   is not relevant to the increment of AODV sequence numbers.  This is
   in contrast to the manner in which the result of comparing two AODV
   sequence numbers is to be treated (see below).

   In order to ascertain that information about a destination is not
   stale, the node compares its current numerical value for the sequence
   number with that obtained from the incoming AODV message.  This
   comparison MUST be done using signed 32-bit arithmetic, this is
   necessary to accomplish sequence number rollover.  If the result of
   subtracting the currently stored sequence number from the value of
   the incoming sequence number is less than zero, then the information
   related to that destination in the AODV message MUST be discarded,
   since that information is stale compared to the node's currently
   stored information.

   The only other circumstance in which a node may change the
   destination sequence number in one of its route table entries is
   in response to a lost or expired link to the next hop towards that
   destination.  The node determines which destinations use a particular
   next hop by consulting its routing table.  In this case, for each
   destination that uses the next hop, the node increments the sequence
   number and marks the route as invalid (see also sections 5.11, 5.12).
   Whenever any fresh enough (i.e., containing a sequence number at
   least equal to the recorded sequence number) routing information for
   an affected destination is received by a node that has marked that
   route table entry as invalid, the node SHOULD update its route table
   information according to the information contained in the update.

   A node may change the sequence number in the routing table entry of a
   destination only if:

    -  it is itself the destination node, and offers a new route to
       itself, or



Perkins, Belding-Royer, Das         Expires 4 May 2003         [Page 10]

Internet Draft                   AODV                    4 November 2002


    -  it receives an AODV message with new information about the
       sequence number for a destination node, or

    -  the path towards the destination node expires or breaks.


5.2. Route Table Entries and Precursor Lists

   When a node receives an AODV control packet from a neighbor, or
   creates or updates a route for a particular destination, it checks
   its route table for an entry for the destination.  In the event
   that there is no corresponding entry for that destination, an entry
   is created.  The sequence number is either determined from the
   information contained in the control packet, or else the valid
   sequence number field is set to false.  The route is only updated if
   the new sequence number is either

      (i)       higher than the destination sequence number in the route
                table, or

      (ii)      the sequence numbers are equal, but the hop count (of
                the new information) plus one, is smaller than the
                existing hop count in the routing table, or

      (iii)     the sequence number is unknown.

   The Lifetime field of the routing table entry is either
   determined from the control packet, or it is initialized to
   ACTIVE_ROUTE_TIMEOUT. This route may now be used to send any queued
   data packets and fulfills any outstanding route requests.

   Each time a route is used to forward a data packet, its Active
   Route Lifetime field of the source, destination and the next hop
   on the path to the destination is updated to be no less than the
   current time plus ACTIVE_ROUTE_TIMEOUT. Since the route between each
   originator and destination pair are expected to be symmetric, the
   Active Route Lifetime for the previous hop, along the reverse path
   back to the IP source, is also updated to be no less than the current
   time plus ACTIVE_ROUTE_TIMEOUT.

   For each valid route maintained by a node as a routing table entry,
   the node also maintains a list of precursors that may be forwarding
   packets on this route.  These precursors will receive notifications
   from the node in the event of detection of the loss of the next hop
   link.  The list of precursors in a routing table entry contains those
   neighboring nodes to which a route reply was generated or forwarded.






Perkins, Belding-Royer, Das         Expires 4 May 2003         [Page 11]

Internet Draft                   AODV                    4 November 2002


5.3. Generating Route Requests

   A node disseminates a RREQ when it determines that it needs a route
   to a destination and does not have one available.  This can happen if
   the destination is previously unknown to the node, or if a previously
   valid route to the destination expires or is marked as invalid.  The
   Destination Sequence Number field in the RREQ message is the last
   known destination sequence number for this destination and is copied
   from the Destination Sequence Number field in the routing table.  If
   no sequence number is known, the unknown sequence number flag MUST
   be set.  The Originator Sequence Number in the RREQ message is the
   node's own sequence number, which is incremented prior to insertion
   in a RREQ. The RREQ ID field is incremented by one from the last RREQ
   ID used by the current node.  Each node maintains only one RREQ ID.
   The Hop Count field is set to zero.

   Before broadcasting the RREQ, the originating node buffers the RREQ
   ID and the Originator IP address (its own address) of the RREQ for
   PATH_DISCOVERY_TIME. In this way, when the node receives the packet
   again from its neighbors, it will not reprocess and re-forward the
   packet.

   An originating node often expects to have bidirectional
   communications with a destination node.  In such cases, it is
   not sufficient for the originating node to have a route to the
   destination node; the destination must also have a route back to
   the originating node.  In order for this to happen as efficiently
   as possible, any generation of a RREP by an intermediate node (as
   in section 5.6) for delivery to the originating node SHOULD be
   accompanied by some action that notifies the destination about a
   route back to the originating node.  The originating node selects
   this mode of operation in the intermediate nodes by setting the `G'
   flag.  See section 5.6.3 for details about actions taken by the
   intermediate node in response to a RREQ with the `G' flag set.

   A node SHOULD NOT generate more than RREQ_RATELIMIT RREQ messages
   per second.  After broadcasting a RREQ, a node waits for a RREP (or
   other control message with current information regarding a route to
   the appropriate destination).  If a route is not received within
   NET_TRAVERSAL_TIME milliseconds, the node MAY try again to discover a
   route by broadcasting another RREQ, up to a maximum of RREQ_RETRIES
   times at the maximum TTL value.  Each new attempt MUST increment and
   update the RREQ ID. For each attempt, the TTL field of the IP header
   is set according to the mechanism specified in section 5.4, in order
   to enable control over how far the RREQ is disseminated for the each
   retry.

   Data packets waiting for a route (i.e., waiting for a RREP after a
   RREQ has been sent) SHOULD be buffered.  The buffering SHOULD be



Perkins, Belding-Royer, Das         Expires 4 May 2003         [Page 12]

Internet Draft                   AODV                    4 November 2002


   "first-in, first-out" (FIFO). If a route discovery has been attempted
   RREQ_RETRIES times at the maximum TTL without receiving any RREP, all
   data packets destined for the corresponding destination SHOULD be
   dropped from the buffer and a Destination Unreachable message SHOULD
   be delivered to the application.

   To reduce congestion in a network, repeated attempts by a source
   node at route discovery for a single destination MUST utilize a
   binary exponential backoff.  The first time a source node broadcasts
   a RREQ, it waits NET_TRAVERSAL_TIME milliseconds for the reception
   of a RREP. If a RREP is not received within that time, the source
   node sends a new RREQ. When calculating the time to wait for
   the RREP after sending the second RREQ, the source node MUST use
   a binary exponential backoff.  Hence, the waiting time for the
   RREP corresponding to the second RREQ is 2 * NET_TRAVERSAL_TIME
   milliseconds.  If a RREP is not receivied within this time period,
   another RREQ may be sent, up to RREQ_RETRIES additional attempts
   after the first RREQ. For each additional attempt, the waiting time
   for the RREP is multiplied by 2, so that the time conforms to a
   binary exponential backoff.


5.4. Controlling Dissemination of Route Request Messages

   To prevent unnecessary network-wide dissemination of RREQs, the
   originating node SHOULD use an expanding ring search technique.
   In an expanding ring search, the originating node initially
   uses a TTL = TTL_START in the RREQ packet IP header and sets the
   timeout for receiving a RREP to RING_TRAVERSAL_TIME milliseconds.
   RING_TRAVERSAL_TIME is calculcated as described in section 9.  The
   TTL_VALUE used in calculating RING_TRAVERSAL_TIME is set equal to
   the value of the TTL field in the IP header.  If the RREQ times out
   without a corresponding RREP, the originator broadcasts the RREQ
   again with the TTL incremented by TTL_INCREMENT. This continues until
   the TTL set in the RREQ reaches TTL_THRESHOLD, beyond which a TTL =
   NET_DIAMETER is used for each attempt.  Each time, the timeout for
   receiving a RREP is RING_TRAVERSAL_TIME. When it is desired to have
   all retries traverse the entire ad hoc network, this can be achieved
   by configuring TTL_START and TTL_INCREMENT both to be the same value
   as NET_DIAMETER.

   The Hop Count stored in an invalid routing table entry indicates
   the last known hop count to that destination in the routing table.
   When a new route to the same destination is required at a later time
   (e.g., upon route loss), the TTL in the RREQ IP header is initially
   set to the Hop Count plus TTL_INCREMENT. Thereafter, following
   each timeout the TTL is incremented by TTL_INCREMENT until TTL =
   TTL_THRESHOLD is reached.  Beyond this TTL = NET_DIAMETER is used.




Perkins, Belding-Royer, Das         Expires 4 May 2003         [Page 13]

Internet Draft                   AODV                    4 November 2002


   Once TTL = NET_DIAMETER, the timeout for waiting for the RREP is set
   to NET_TRAVERSAL_TIME, as specified in section 5.3.

   An expired routing table entry SHOULD NOT be expunged before
   (current_time + DELETE_PERIOD) (see section 5.11).  Otherwise, the
   soft state corresponding to the route (e.g., last known hop count)
   will be lost.  Furthermore, a longer routing table entry expunge time
   MAY be configured.  Any routing table entry waiting for a RREP SHOULD
   NOT be expunged before (current_time + 2 * NET_TRAVERSAL_TIME).


5.5. Processing and Forwarding Route Requests

   When a node receives a RREQ, it first creates or updates a route to
   the previous hop without a valid sequence number (see section 5.2)
   then checks to determine whether it has received a RREQ with
   the same Originator IP Address and RREQ ID within at least the
   last PATH_DISCOVERY_TIME. If such a RREQ has been received, the
   node silently discards the newly received RREQ. The rest of this
   subsection describes actions taken for RREQs that are not discarded.

   First, it first increments the hop count value in the RREQ by one,
   to account for the new hop through the intermediate node.  Then the
   node creates or updates a reverse route to the Originator IP Address
   (see section 5.2) using the Originator Sequence Number from the RREQ
   in its routing table.  This reverse route will be needed if the node
   receives a RREP back to the node that originated the RREQ (identified
   by the Originator IP Address).  When the reverse route is created or
   updated, the following actions on the route are also carried out:

    1. the Originator Sequence Number from the RREQ is copied to the
       corresponding destination sequence number in the route table
       entry and the valid sequence number field is set to true;

    2. the next hop in the routing table becomes the node from which the
       RREQ was received (it is obtained from the source IP address in
       the IP header and is often not equal to the Originator IP Address
       field in the RREQ message);

    3. the hop count is copied from the Hop Count in the RREQ message;

   Whenever a RREQ message is received, the Lifetime of the reverse
   route entry for the Originator IP address is set to be the maximum of
   (ExistingLifetime, MinimalLifetime), where

      MinimalLifetime =    (current time + 2*NET_TRAVERSAL_TIME -
                           2*HopCount*NODE_TRAVERSAL_TIME).





Perkins, Belding-Royer, Das         Expires 4 May 2003         [Page 14]

Internet Draft                   AODV                    4 November 2002


   The current node can now begin using the reverse route to forward
   data packets.

   The node generates a RREP (as discussed further in section 5.6) if
   either:

      (i)       it is itself the destination (see section 5.6.1), or

      (ii)      it has an active route to the destination, the
                destination sequence number in the node's existing route
                table entry for the destination is valid and greater
                than or equal to the Destination Sequence Number of the
                RREQ (comparison using signed 32-bit arithmetic), and
                the ``destination only'' ('D') flag is NOT set.  See
                section 5.6.2 for further information about generating
                the RREP in this case.

   When either of these conditions is satisfied, the node does not
   rebroadcast the RREQ.

   Otherwise, if the incoming IP header has TTL larger than 1, the node
   updates and broadcasts the RREQ to address 255.255.255.255 on all of
   its configured interface(s) (see section 5.14).  To update the RREQ,
   the TTL or hop limit field in the outgoing IP header is decreased
   by one, and the Hop Count field in the RREQ message is incremented
   by one, to account for the new hop through the intermediate node.
   Lastly, the Destination Sequence number for the requested destination
   is set to the maximum of the corresponding value received in the RREQ
   message, and the destination sequence value currently maintained by
   the node for the requested destination.  However, the forwarding node
   MUST NOT modify its maintained value for the destination sequence
   number, even if the value received in the incoming RREQ is larger
   than the value currently maintained by the forwarding node.


5.6. Generating Route Replies

   If a node receives a route request for a destination, and either
   has a fresh enough route to satisfy the request or is itself the
   destination, the node generates a RREP message.  This node copies
   the Destination IP Address and the Originator Sequence Number in
   RREQ message into the corresponding fields in the RREP message.
   Processing is slightly different, depending on whether the node is
   itself the requested destination, or instead if it is an intermediate
   node with an fresh enough route to the destination.  These scenarios
   are described in the sections below.

   Once created, the RREP is unicast to the next hop toward the
   originator of the RREQ, as indicated by the route table entry for



Perkins, Belding-Royer, Das         Expires 4 May 2003         [Page 15]

Internet Draft                   AODV                    4 November 2002


   that originator.  As the RREP is forwarded back towards the node
   which originated the RREQ message, the Hop Count field is incremented
   by one at each hop.  Thus, when the RREP reaches the originator, the
   Hop Count represents the distance, in hops, of the destination from
   the originator.


5.6.1. Route Reply Generation by the Destination

   If the generating node is the destination itself, it MUST increment
   its own sequence number by one if the sequence number in the
   RREQ packet is equal to that incremented value.  Otherwise, the
   destination does not change its sequence number before generating
   the RREP message.  The destination node places its (perhaps newly
   incremented) sequence number into the Destination Sequence Number
   field of the RREP, and enters the value zero in the Hop Count field
   of the RREP.

   The destination node copies the value MY_ROUTE_TIMEOUT (see
   section 9) into the Lifetime field of the RREP. Each node MAY
   reconfigure its value for MY_ROUTE_TIMEOUT, within mild constraints
   (see section 9).


5.6.2. Route Reply Generation by an Intermediate Node

   If the node generating the RREP is not the destination node, but
   instead is an intermediate hop along the path from the originator
   to the destination, it copies its known sequence number for the
   destination into the Destination Sequence Number field in the RREP
   message.

   The intermediate node updates the forward route entry by placing the
   last hop node (from which it received the RREQ, as indicated by the
   source IP address field in the IP header) into the precursor list for
   the forward route entry -- i.e., the entry for the Destination IP
   Address.  The intermediate node also updates its route table entry
   for the node originating the RREQ by placing the next hop towards
   the destination in the precursor list for the reverse route entry
   -- i.e., the entry for the Originator IP Address field of the RREQ
   message data.

   The intermediate node places its distance in hops from the
   destination (indicated by the hop count in the routing table) Count
   field in the RREP. The Lifetime field of the RREP is calculated by
   subtracting the current time from the expiration time in its route
   table entry.





Perkins, Belding-Royer, Das         Expires 4 May 2003         [Page 16]

Internet Draft                   AODV                    4 November 2002


5.6.3. Generating Gratuitous RREPs

   After a node receives a RREQ and responds with a RREP, it discards
   the RREQ. If intermediate nodes reply to every transmission of a
   given RREQ, the destination does not receive any copies of it.  In
   this situation, the destination does not learn of a route to the
   originating node.  This could cause the destination to initiate a
   route discovery (for example, if the originator is attempting to
   establish a TCP session).  In order that the destination learn of
   routes to the originating node, the originating node SHOULD set
   the ``gratuitous RREP'' ('G') flag in the RREQ if for any reason
   the destination is likely to need a route to the originating node.
   If, in response to a RREQ with the 'G' flag set, an intermediate
   node returns a RREP, it MUST also unicast a gratuitous RREP to the
   destination node.

   The RREP that is sent to the originator of the RREQ is the same
   as before.  The gratuitous RREP that is to be sent to the desired
   destination contains the following values in the RREP message fields:

      Hop Count  The Hop Count as indicated in the node's route table
                 entry for the originator

      Destination IP Address
                 The IP address of the node that originated the RREQ

      Destination Sequence Number
                 The Originator Sequence Number from the RREQ

      Originator IP Address
                 The IP address of the Destination node in the RREQ

      Lifetime   The remaining lifetime of the route towards the
                 originator of the RREQ, as known by the intermediate
                 node.

   The gratuitous RREP is then sent to the next hop along the path to
   the destination node, just as if the destination node had already
   issued a RREQ for the originating node and this RREP was produced in
   response to that (fictitious) RREQ.


5.7. Receiving and Forwarding Route Replies

   When a node receives a RREP message, it first creates or updates
   a route to the previous hop without a valid sequence number (see
   section 5.2) then increments the hop count value in the RREP by one,
   to account for the new hop through the intermediate node.  Call this
   incremented value the "New Hop Count".  Then the forward route for



Perkins, Belding-Royer, Das         Expires 4 May 2003         [Page 17]

Internet Draft                   AODV                    4 November 2002


   this destination is created if it does not already exist.  Otherwise,
   the node compares the Destination Sequence Number in the message with
   its own stored destination sequence number for the Destination IP
   Address in the RREP message.  Upon comparison, the existing entry is
   updated only if either

      (i)       the sequence number in the routing table is invalid in
                route table entry.

      (ii)      the Destination Sequence Number in the RREP is greater
                than the node's copy of the destination sequence number
                and the known value is valid, or

      (iii)     the sequence numbers are the same, but the route is no
                longer active, or

      (iv)      the sequence numbers are the same, and the New Hop Count
                is smaller than the hop count in route table entry.

   If either the route table entry to the destination is created or
   updated, the next hop in the route entry is assigned to be the node
   from which the RREP is received, which is indicated by the source IP
   address field in the IP header; the hop count is the New Hop Count;
   the expiry time is the current time plus the Lifetime in the RREP
   message; and the destination sequence number is the Destination
   Sequence Number in the RREP message.  The current node can now begin
   using this route to forward data packets to the destination.

   If the current node is not the node indicated by the Originator IP
   Address in the RREP message AND a forward route has been created or
   updated as described above, the node consults its route table entry
   for the originating node to determine the next hop for the RREP
   packet, and then forwards the RREP towards the originator using the
   information in that route table entry.  If a node forwards a RREP
   over a link that is likely to have errors or be unidirectional, the
   node SHOULD set the `A' flag to require that the recipient of the
   RREP acknowledge receipt of the RREP by sending a RREP-ACK message
   back (see section 5.8).

   When any node transmits a RREP, the precursor list for the
   corresponding destination node is updated by adding to it the
   next hop node to which the RREP is forwarded.  Also, at each
   node the (reverse) route used to forward a RREP has its lifetime
   changed to be the maximum of (existing-lifetime, (current time +
   ACTIVE_ROUTE_TIMEOUT)). Finally, the precursor list for the next hop
   towards the destination is updated to contain the next hop towards
   the source.





Perkins, Belding-Royer, Das         Expires 4 May 2003         [Page 18]

Internet Draft                   AODV                    4 November 2002


5.8. Operation over Unidirectional Links

   It is possible that a RREP transmission may fail, especially if the
   RREQ transmission triggering the RREP occurs over a unidirectional
   link.  If no other RREP generated from the same route discovery
   attempt reaches the node which originated the RREQ message, the
   originator will reattempt route discovery after a timeout (see
   section 5.3).  However, the same scenario might well be repeated, and
   no route would be discovered even after repeated retries.  Unless
   corrective action is taken, this can happen even when bidirectional
   routes between originator and destination do exist.  Link layers
   using broadcast transmissions for the RREQ will not be able to detect
   the presence of such unidirectional links.  In AODV, any node acts on
   only the first RREQ with the same RREQ ID and ignores any subsequent
   RREQs.  Suppose, for example, that the first RREQ arrives along a
   path that has one or more unidirectional link(s).  A subsequent RREQ
   may arrive via a bidirectional path (assuming such paths exist), but
   it will be ignored.

   To prevent this problem, when a node detects that its transmission of
   a RREP message has failed, it remembers the next-hop of the failed
   RREP in a ``blacklist'' set.  Such failures can be detected via
   the absence of a link-layer or network-layer acknowledgment (e.g.,
   RREP-ACK). A node ignores all RREQs received from any node in its
   blacklist set.  Nodes are removed from the blacklist set after a
   BLACKLIST_TIMEOUT period (see section 9).  This period should be set
   to the upper bound of the time it takes to perform the allowed number
   of route request retry attempts as described in section 5.3.

   Note that the RREP-ACK packet does not contain any information about
   which RREP it is acknowledging.  The time at which the RREP-ACK is
   received will likely come just after the time when the RREP was sent
   with the 'A' bit.  This information is expected to be sufficient
   to provide assurance to the sender of the RREP that the link is
   currently bidirectional.  However, that assurance cannot be always
   expected to remain permanently.


5.9. Hello Messages

   A node MAY offer connectivity information by broadcasting local Hello
   messages.  A node SHOULD only use hello messages if it is part of an
   active route.  Every HELLO_INTERVAL milliseconds, the node checks
   whether it has sent a broadcast (e.g., a RREQ or an appropriate layer
   2 message) within the last HELLO_INTERVAL. If it has not, it MAY
   broadcast a RREP with TTL = 1, called a Hello message, with the RREP
   message fields set as follows:





Perkins, Belding-Royer, Das         Expires 4 May 2003         [Page 19]

Internet Draft                   AODV                    4 November 2002


      Destination IP Address
                  The node's IP address.

      Destination Sequence Number
                  The node's latest sequence number.

      Hop Count   0

      Lifetime    ALLOWED_HELLO_LOSS * HELLO_INTERVAL

   A node MAY determine connectivity by listening for packets from its
   set of neighbors.  If, within the past DELETE_PERIOD, it has received
   a Hello message from a neighbor, and then for that neighbor does
   not receive any packets (Hello messages or otherwise) for more than
   ALLOWED_HELLO_LOSS * HELLO_INTERVAL milliseconds, the node SHOULD
   assume that the link to this neighbor is currently lost.  When this
   happens, the node SHOULD proceed as in Section 5.11.

   Whenever a node receives a Hello message from a neighbor, the
   node SHOULD make sure that it has an active route to the neighbor,
   and create one if necessary.  If a route already exists, then the
   Lifetime for the route should be increased, if necessary, to be at
   least ALLOWED_HELLO_LOSS * HELLO_INTERVAL. The route to the neighbor,
   if it exists, MUST subsequently contain the latest Destination
   Sequence Number from the Hello message.  The current node can now
   begin using this route to forward data packets.  Routes that are
   created by hello messages and not used by any other active routes
   will have empty precursor lists and would not trigger a RERR message
   when the neighbor moves away and a neighbor timeout occurs.

   Also, whenever a node receives any control packet it has the same
   meaning as the reception of an explicit Hello message, in that it
   signifies an active connection to the node indicated by the Source IP
   Address of the IP header of the control message packet.


5.10. Maintaining Local Connectivity

   Each forwarding node SHOULD keep track of its continued connectivity
   to its active next hops (i.e., which next hops or precursors have
   forwarded packets to or from the forwarding node during the last
   ACTIVE_ROUTE_TIMEOUT), as well as neighbors that have transmitted
   Hello messages during the last (ALLOWED_HELLO_LOSS * HELLO_INTERVAL).
   A node can maintain accurate information about its continued
   connectivity to these active next hops, using one or more of the
   available link or network layer mechanisms, as described below.

    -  Any suitable link layer notification, such as those provided by
       IEEE 802.11, can be used to determine connectivity, each time



Perkins, Belding-Royer, Das         Expires 4 May 2003         [Page 20]

Internet Draft                   AODV                    4 November 2002


       a packet is transmitted to an active next hop.  For example,
       absence of a link layer ACK or failure to get a CTS after sending
       RTS, even after the maximum number of retransmission attempts,
       indicates loss of the link to this active next hop.

    -  If possible, passive acknowledgment SHOULD be used when the
       next hop is expected to forward the packet, by listening to the
       channel for a transmission attempt made by the next hop.  If
       transmission is not detected within NEXT_HOP_WAIT milliseconds or
       the next hop is the destination (and thus is never supposed to
       transmit the packet) one of the following methods should be used
       to determine connectivity.

        *  Receiving any packet (including a Hello message) from the
           next hop.

        *  A RREQ unicast to the next hop, asking for a route to the
           next hop.

        *  An ICMP Echo Request message unicast to the next hop.

   If a link to the next hop cannot be detected by any of these methods,
   the forwarding node SHOULD assume that the link is lost, and take
   corrective action by following the methods specified in Section 5.11.


5.11. Route Error Messages, Route Expiry and Route Deletion

   A Route Error (RERR) message MAY be either broadcast (if there
   are many precursors), unicast (if there is only 1 precursor),
   or iteratively unicast to all precursors (if broadcast is
   inappropriate).  Even when the RERR message is iteratively unicast
   to several precursors, it is considered to be a single control
   message for the purposes of the description in the text that follows.
   With that understanding, a node SHOULD NOT generate more than
   RERR_RATELIMIT RERR messages per second.

   A node initiates processing for a RERR message in three situations:

      (i)       if it detects a link break for the next hop of an active
                route in its routing table while transmitting data, or

      (ii)      if it gets a data packet destined to a node for which it
                does not have an active route and is not repairing (if
                using local repair), or

      (iii)     if it receives a RERR from a neighbor for one or more
                active routes.




Perkins, Belding-Royer, Das         Expires 4 May 2003         [Page 21]

Internet Draft                   AODV                    4 November 2002


   For case (i), the node first makes a list of unreachable destinations
   consisting of the unreachable neighbor and any additional
   destinations in the local routing table that use the unreachable
   neighbor as the next hop.  For case (ii), there is only one
   unreachable destination, which is the destination of the data packet
   that cannot be delivered.  For case (iii), the list should consist of
   those destinations in the RERR for which there exists a corresponding
   entry in the local routing table that has the transmitter of the
   received RERR as the next hop.

   Some of the unreachable destinations in the list could be used by
   neighboring nodes, and it may therefore be necessary to send a (new)
   RERR. The RERR should contain those destinations that are part of
   the created list of unreachable destinations and have a non-empty
   precursor list.

   The neighboring node(s) that should receive the RERR are all those
   that belong to a precursor list of at least one of the unreachable
   destination(s) in the newly created RERR. In case there is only
   one unique neighbor that needs to receive the RERR, the RERR
   SHOULD be unicast toward that destination.  Otherwise the RERR is
   typically sent to the local broadcast address (Destination IP ==
   255.255.255.255, TTL == 1) with the unreachable destinations, and
   their corresponding destination sequence numbers, included in the
   packet.  The DestCount field of the RERR packet indicates the number
   of unreachable destinations included in the packet.

   Just before transmitting the RERR, certain updates are made on the
   routing table that may affect the destination sequence numbers for
   the unreachable destinations.  For each one of these destinations,
   the corresponding routing table entry is updated as follows:

    1. The destination sequence number of this routing entry, if it
       exists and is valid, is incremented for cases (i) and (ii) above,
       and copied from the incoming RERR in case (iii) above.

    2. The entry is invalidated by marking the route entry as invalid

    3. The Lifetime field is updated to current time plus DELETE_PERIOD.
       Before this time, the entry SHOULD NOT be deleted.

   Note that the Lifetime field in the routing table plays dual role
   -- for an active route it is the expiry time, and for an invalid
   route it is the deletion time.  If a data packet is received for an
   invalid route, the Lifetime field is updated to current time plus
   DELETE_PERIOD. The determination of DELETE_PERIOD is discussed in
   Section 9.





Perkins, Belding-Royer, Das         Expires 4 May 2003         [Page 22]

Internet Draft                   AODV                    4 November 2002


5.12. Local Repair

   When a link break in an active route occurs, the node upstream of
   that break MAY choose to repair the link locally if the destination
   was no farther than MAX_REPAIR_TTL hops away.  To repair the link
   break, the node increments the sequence number for the destination
   and then broadcasts a RREQ for that destination.  The TTL of the RREQ
   should initially be set to the following value:

      max(MIN_REPAIR_TTL, 0.5 * #hops) + LOCAL_ADD_TTL,

   where #hops is the number of hops to the sender (originator) of the
   currently undeliverable packet.  Thus, local repair attempts will
   often be invisible to the originating node, and will always have TTL
   >= MIN_REPAIR_TTL + LOCAL_ADD_TTL. The node initiating the repair
   then waits the discovery period to receive RREPs in response to the
   RREQ. During local repair data packets SHOULD be buffered.  If, at
   the end of the discovery period, it has not received a RREP (or other
   control message creating or updating the route) for that destination,
   it proceeds as described in Section 5.11 by transmitting a RERR
   message for that destination.

   On the other hand, if the node receives one or more RREPs (or
   other control message creating or updating the route to the desired
   destination) during the discovery period, it first compares the hop
   count of the new route with the value in the hop count field of the
   invalid route table entry for that destination.  If the hop count of
   the newly determined route to the destination is greater than the
   hop count of the previously known route the node SHOULD issue a RERR
   message for the destination, with the 'N' bit set.  Then it proceeds
   as described in Section 5.7, updating its route table entry for that
   destination.

   A node that receives a RERR message with the 'N' flag set MUST NOT
   delete the route to that destination.  The only action taken should
   be the retransmission of the message, if the RERR arrived from the
   next hop along that route, and if there are one or more precursor
   nodes for that route to the destination.  When the originating node
   receives a RERR message with the 'N' flag set, if this message
   came from its next hop along its route to the destination then
   the originating node MAY choose to reinitiate route discovery, as
   described in Section 5.3.

   Local repair of link breaks in routes sometimes results in increased
   path lengths to those destinations.  Repairing the link locally is
   likely to increase the number of data packets that are able to be
   delivered to the destinations, since data packets will not be dropped
   as the RERR travels to the originating node.  Sending a RERR to the
   originating node after locally repairing the link break may allow the



Perkins, Belding-Royer, Das         Expires 4 May 2003         [Page 23]

Internet Draft                   AODV                    4 November 2002


   originator to find a fresh route to the destination that is better,
   based on current node positions.  However, it does not require the
   originating node to rebuild the route, as the originator may be done,
   or nearly done, with the data session.

   When a link breaks along an active route, there are often multiple
   destinations that become unreachable.  The node that is upstream
   of the lost link tries an immediate local repair for only the one
   destination towards which the data packet was traveling.  Other
   routes using the same link MUST be marked as invalid, but the node
   handling the local repair MAY flag each such newly lost route as
   locally repairable; this local repair flag in the route table MUST be
   reset when the route times out (e.g., after the route has been not
   been active for ACTIVE_ROUTE_TIMEOUT). Before the timeout occurs,
   these other routes will be repaired as needed when packets arrive for
   the other destinations.  Hence, these routes are repaired as needed;
   if a data packet does not arrive for the route, then that route will
   not be repaired.  Alternatively, depending upon local congestion,
   the node MAY begin the process of establishing local repairs for
   the other routes, without waiting for new packets to arrive.  By
   proactively repairing the routes that have broken due to the loss
   of the link, incoming data packets for those routes will not be
   subject to the delay of repairing the route and can be immediately
   forwarded.  However, repairing the route before a data packet is
   received for it runs the risk of repairing routes that are no longer
   in use.  Therefore, depending upon the local traffic in the network
   and whether congestion is being experienced, the node MAY elect to
   proactively repair the routes before a data packet is received;
   otherwise, it can wait until a data is received, and then commence
   the repair of the route.


5.13. Actions After Reboot

   A node participating in the ad hoc network must take certain actions
   after reboot as it might lose all sequence number records for all
   destinations, including its own sequence number.  However, there
   may be neighboring nodes that are using this node as an active next
   hop.  This can potentially create routing loops.  To prevent this
   possibility, each node on reboot waits for DELETE_PERIOD. During this
   time, the node does not transmit any RREP messages.  If the node
   receives a RREQ, RREP, or RERR control packet, it SHOULD create route
   entries as appropriate given the sequence number information in the
   control packets, but MUST not forward any control packets.  If the
   node receives a data packet for some other destination, it SHOULD
   broadcast a RERR as described in subsection 5.11 and MUST reset the
   waiting timer to expire after current time plus DELETE_PERIOD.





Perkins, Belding-Royer, Das         Expires 4 May 2003         [Page 24]

Internet Draft                   AODV                    4 November 2002


   It can be shown [1] that by the time the rebooted node comes out of
   the waiting phase and becomes an active router again, none of its
   neighbors will be using it as an active next hop any more.  Its own
   sequence number gets updated once it receives a RREQ from any other
   node, as the RREQ always carries the maximum destination sequence
   number seen en route.


5.14. Interfaces

   Because AODV should operate smoothly over wired, as well as wireless,
   networks, and because it is likely that AODV will also be used with
   multi-homed radios, the interface over which packets arrive must
   be known to AODV whenever a packet is received.  This includes the
   reception of RREQ, RREP, and RERR messages.  Whenever a packet is
   received from a new neighbor, the interface on which that packet was
   received is recorded into the route table entry for that neighbor,
   along with all the other appropriate routing information.  Similarly,
   whenever a route to a new destination is learned, the interface
   through which the destination can be reached is also recorded into
   the destination's route table entry.

   When multiple interfaces are available, a node retransmitting a RREQ
   message rebroadcasts that message on all interfaces that have been
   configured for operation in the ad-hoc network, except those on which
   it is known that all of the nodes neighbors have already received
   the RREQ For instance, for some broadcast media (e.g., Ethernet) it
   may be presumed that all nodes on the same link receive a broadcast
   message at the same time.  When a node needs to transmit a RERR, it
   SHOULD only transmit it on those interfaces that have precursor nodes
   for that route.


6. AODV and Aggregated Networks

   AODV has been designed for use by mobile nodes with IP addresses
   that are not necessarily related to each other, to create an ad hoc
   network.  However, in some cases a collection of mobile nodes MAY
   operate in a fixed relationship to each other and share a common
   subnet prefix, moving together within an area where an ad hoc network
   has formed.  Call such a collection of nodes a ``subnet''.  In this
   case, it is possible for a single node within the subnet to advertise
   reachability for all other nodes on the subnet, by responding with
   a RREP message to any RREQ message requesting a route to any node
   with the subnet routing prefix.  Call the single node the ``subnet
   router''.  In order for a subnet router to operate the AODV protocol
   for the whole subnet, it has to maintain a destination sequence
   number for the entire subnet.  In any such RREP message sent by the
   subnet router, the Prefix Size field of the RREP message MUST be



Perkins, Belding-Royer, Das         Expires 4 May 2003         [Page 25]

Internet Draft                   AODV                    4 November 2002


   set to the length of the subnet prefix.  Other nodes sharing the
   subnet prefix SHOULD NOT issue RREP messages, and SHOULD forward RREQ
   messages to the subnet leader.

   If several nodes in the subnet advertise reachability to the subnet
   defined by the subnet prefix, the node with the lowest IP address
   is elected to be the subnet leader, and all other nodes MUST stop
   advertising reachability.

   The behavior of default routes (i.e., routes with routing prefix
   length 0) is not defined in this specification.  Selection of routes
   sharing prefix bits should be according to longest match first.


7. Using AODV with Other Networks

   In some configurations, an ad hoc network may be able to provide
   connectivity between external routing domains that do not use AODV.
   If the points of contact to the other networks can act as subnet
   routers (see Section 6) for any relevant networks within the external
   routing domains, then the ad hoc network can maintain connectivity to
   the external routing domains.  Indeed, the external routing networks
   can use the ad hoc network defined by AODV as a transit network.

   In order to provide this feature, a point of contact to an external
   network (call it an Infrastructure Router) has to act as the subnet
   router for every subnet of interest within the external network for
   which the Infrastructure Router can provide reachability.  This
   includes the need for maintaining a destination sequence number for
   that external subnet.

   If multiple Infrastructure Routers offer reachability to the same
   external subnet, those Infrastructure Routers have to cooperate (by
   means outside the scope of this specification) to provide consistent
   AODV semantics for ad hoc access to those subnets.


8. Extensions

   In this section, the format of extensions to the RREQ and RREP
   messages is specified.  All such extensions appear after the message
   data, and have the following format:

    0                   1                   2                   3
    0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
   +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
   |     Type      |    Length     |     type-specific data ...
   +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+




Perkins, Belding-Royer, Das         Expires 4 May 2003         [Page 26]

Internet Draft                   AODV                    4 November 2002


   where:

      Type     1-255

      Length   The length of the type-specific data, not including the
               Type and Length fields of the extension in bytes.

   Extensions with types between 128 and 255 may NOT be skipped.  The
   rules for extensions will be spelled out more fully, and conform to
   the rules for handling IPv6 options.


8.1. Hello Interval Extension Format

    0                   1                   2                   3
    0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
   +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
   |     Type      |    Length     |       Hello Interval ...      |
   +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
   | ... Hello Interval, continued |
   +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+

      Type     2

      Length   4

      Hello Interval
               The number of milliseconds between successive
               transmissions of a Hello message.

   The Hello Interval extension MAY be appended to a RREP message with
   TTL == 1, to be used by a neighboring receiver in determine how long
   to wait for subsequent such RREP messages (i.e., Hello messages; see
   section 5.9).


9. Configuration Parameters

   This section gives default values for some important parameters
   associated with AODV protocol operations.  A particular mobile node
   may wish to change certain of the parameters, in particular the
   NET_DIAMETER, MY_ROUTE_TIMEOUT, ALLOWED_HELLO_LOSS, RREQ_RETRIES,
   and possibly the HELLO_INTERVAL. In the latter case, the node
   should advertise the HELLO_INTERVAL in its Hello messages, by
   appending a Hello Interval Extension to the RREP message.  Choice
   of these parameters may affect the performance of the protocol.
   Changing NODE_TRAVERSAL_TIME also changes the node's estimate
   of the NET_TRAVERSAL_TIME, and so can only be done with suitable
   knowledge about the behavior of other nodes in the ad hoc network.



Perkins, Belding-Royer, Das         Expires 4 May 2003         [Page 27]

Internet Draft                   AODV                    4 November 2002


   The configured value for MY_ROUTE_TIMEOUT MUST be at least 2 *
   PATH_DISCOVERY_TIME.

      Parameter Name           Value
      ----------------------   -----
      ACTIVE_ROUTE_TIMEOUT     3,000 Milliseconds
      ALLOWED_HELLO_LOSS       2
      BLACKLIST_TIMEOUT        RREQ_RETRIES * NET_TRAVERSAL_TIME
      DELETE_PERIOD            see note below
      HELLO_INTERVAL           1,000 Milliseconds
      LOCAL_ADD_TTL            2
      MAX_REPAIR_TTL           0.3 * NET_DIAMETER
      MIN_REPAIR_TTL           see note below
      MY_ROUTE_TIMEOUT         2 * ACTIVE_ROUTE_TIMEOUT
      NET_DIAMETER             35
      NET_TRAVERSAL_TIME       2 * NODE_TRAVERSAL_TIME * NET_DIAMETER
      NEXT_HOP_WAIT            NODE_TRAVERSAL_TIME + 10
      NODE_TRAVERSAL_TIME      40
      PATH_DISCOVERY_TIME      2 * NET_TRAVERSAL_TIME
      RERR_RATELIMIT           10
      RING_TRAVERSAL_TIME      2 * NODE_TRAVERSAL_TIME * (TTL_VALUE + TIMEOUT_BUFFER)
      RREQ_RETRIES             2
      RREQ_RATELIMIT           10
      TIMEOUT_BUFFER           2
      TTL_START                1
      TTL_INCREMENT            2
      TTL_THRESHOLD            7
      TTL_VALUE                see note below


   The MIN_REPAIR_TTL should be the last known hop count to
   the destination.  If Hello messages are used, then the
   ACTIVE_ROUTE_TIMEOUT parameter value MUST be more than the
   value (ALLOWED_HELLO_LOSS * HELLO_INTERVAL).

   TTL_VALUE is the value of the TTL field in the IP header while the
   expanding ring search is being performed.  This is described further
   in section 5.4.  The TIMEOUT_BUFFER is configurable.  Its purpose is
   to provide a buffer for the timeout so that if the RREP is delayed
   due to congestion, a timeout is less likely to occur while the RREP
   is still en route back to the source.  To omit this buffer, set
   TIMEOUT_BUFFER = 0.

   DELETE_PERIOD should be an upper bound on the time for which an
   upstream node A can have a neighbor B as an active next hop for
   destination D, while B has invalidated the route to D. Beyond this
   time B can delete the route to D. The determination of the upper
   bound somewhat depends on the characteristics of the underlying
   link layer.  If Hello messages are used to determine the continued



Perkins, Belding-Royer, Das         Expires 4 May 2003         [Page 28]

Internet Draft                   AODV                    4 November 2002


   availability of links to next hop nodes, DELETE_PERIOD must be at
   least ALLOWED_HELLO_LOSS * HELLO_INTERVAL. If the link layer feedback
   is used to detect loss of link, DELETE_PERIOD must be at least
   ACTIVE_ROUTE_TIMEOUT. If hello messages are received from a neighbor
   but data packets to that neighbor are lost, (due to temporary link
   asymmetry, e.g.)  we have to make more concrete assumptions about
   the underlying link layer.  We assume that such asymmetry cannot
   persist beyond a certain time, say, a multiple K of HELLO_INTERVAL.
   In other words, a node will invariably receive at least one out
   of K subsequent Hello messages from a neighbor if the link is
   working and the neighbor is sending no other traffic.  Covering all
   possibilities,

DELETE_PERIOD = K * max (ACTIVE_ROUTE_TIMEOUT, HELLO_INTERVAL) (K = 5 is
                             recommended).

   NET_DIAMETER measures the maximum possible number of hops between
   two nodes in the network.  NODE_TRAVERSAL_TIME is a conservative
   estimate of the average one hop traversal time for packets and should
   include queuing delays, interrupt processing times and transfer
   times.  ACTIVE_ROUTE_TIMEOUT SHOULD be set to a longer value (at
   least 10,000 milliseconds) if link-layer indications are used to
   detect link breakages such as in IEEE 802.11 [4] standard.  TTL_START
   should be set to at least 2 if Hello messages are used for local
   connectivity information.  Performance of the AODV protocol is
   sensitive to the chosen values of these constants, which often depend
   on the characteristics of the underlying link layer protocol, radio
   technologies etc.  BLACKLIST_TIMEOUT should be suitably increased
   if an expanding ring search is used.  In such cases, it should be
   [(TTL_THRESHOLD - TTL_START)/TTL_INCREMENT] + 1 + RREQ_RETRIES *
   NET_TRAVERSAL_TIME. This is to account for possible additional route
   discovery attempts.


10. Security Considerations

   Currently, AODV does not specify any special security measures.
   Route protocols, however, are prime targets for impersonation
   attacks.  If there is danger of such attacks, AODV control messages
   must be protected by use of authentication techniques, such as those
   involving generation of unforgeable and cryptographically strong
   message digests or digital signatures.  In particular, RREP messages
   SHOULD be authenticated to avoid creation of spurious routes to a
   desired destination.  Otherwise, an attacker could masquerade as the
   desired destination, and maliciously deny service to the destination
   and/or maliciously inspect and consume traffic intended for delivery
   to the destination.  RERR messages, while less dangerous, SHOULD be
   authenticated in order to prevent malicious nodes from disrupting
   valid routes between nodes that are communication partners.



Perkins, Belding-Royer, Das         Expires 4 May 2003         [Page 29]

Internet Draft                   AODV                    4 November 2002


   Since AODV does not make any assumption about the nature of the
   address assignment to the mobile nodes except that they are presumed
   to have unique IP addresses, no definite statements can be made about
   the applicability of IPsec authentication headers or key exchange
   mechanisms.  However, if the mobile nodes in the ad hoc network have
   pre-established security associations, they should be able to use the
   same authentication mechanisms based on their IP addresses as they
   would have used otherwise.


11. IPv6 Considerations

   See [6] for detailed operation for IPv6.  The only changes to the
   protocol are that the address fields are enlarged.


12. Acknowledgments

   Special thanks to Ian Chakeres, UCSB, for his extensive suggestions
   and contributions to this revision.

   We acknowledge with gratitude the work done at University of
   Pennsylvania within Carl Gunter's group, as well as at Stanford and
   CMU, to determine some conditions (especially involving reboots and
   lost RERRs) under which previous versions of AODV could suffer from
   routing loops.  Contributors to those efforts include Karthikeyan
   Bhargavan, Joshua Broch, Dave Maltz, Madanlal Musuvathi, and
   Davor Obradovic.  The idea of a DELETE_PERIOD, for which expired
   routes (and, in particular, the sequence numbers) to a particular
   destination must be maintained, was also suggested by them.

   We also acknowledge the comments and improvements suggested by
   Sung-Ju Lee (especially regarding local repair), Mahesh Marina, Erik
   Nordstrom (who provided text for section 5.11), Yves Prelot, Marc
   Mosko, Manel Guerrero Zapata, Philippe Jacquet, and Fred Baker.


References

   [1] Karthikeyan Bhargavan, Carl A. Gunter, and Davor Obradovic.
       Fault Origin Adjudication.  In Proceedings of the Workshop on
       Formal Methods in Software Practice, Portland, OR, August 2000.

   [2] S. Bradner.  Key words for use in RFCs to Indicate Requirement
       Levels.  Request for Comments (Best Current Practice) 2119,
       Internet Engineering Task Force, March 1997.

   [3] J. Manner et al.  Mobility Related Terminology (work in
       progress).  draft-manner-seamoby-terms-02.txt, July 2001.



Perkins, Belding-Royer, Das         Expires 4 May 2003         [Page 30]

Internet Draft                   AODV                    4 November 2002


   [4] IEEE 802.11 Committee, AlphaGraphics #35, 10201 N.35th Avenue,
       Phoenix AZ 85051.  Wireless LAN Medium Access Control MAC and
       Physical Layer PHY Specifications, June 1997.  IEEE Standard
       802.11-97.

   [5] D. Mills.  Simple Network Time Protocol (SNTP) Version 4 for
       IPv4, IPv6 and OSI.  Request for Comments (Informational) 2030,
       Internet Engineering Task Force, October 1996.

   [6] C. Perkins, E. Royer, and S. Das.  Ad Hoc On Demand Distance
       Vector (AODV) Routing for IP version 6 (work in progress).
       Internet Draft, Internet Engineering Task Force.
       draft-perkins-manet-aodv6-01.txt, November 2001.







































Perkins, Belding-Royer, Das         Expires 4 May 2003         [Page 31]

Internet Draft                   AODV                    4 November 2002


A. Draft Modifications

   The following are major changes between this version (12) of the AODV
   draft and the previous version (11):

	- Added binary exponential backoff to repeated RREQ attempts
   for the same destination.

	- Included a mechanism for dynamically calculating the waiting
   time for a RREP during an expanding ring search.  This includes the
   addition of a new parameter, RING_TRAVERSAL_TIME.

	- Added the TTL_VALUE and TIMEOUT_BUFFER parameters to help
   dynamically calculate the waiting time for a RREP during an
   expanding ring search.

	- Clarified the option of proactive local repair for recently
   broken routes.









	




Perkins, Belding-Royer, Das         Expires 4 May 2003         [Page 32]

Internet Draft                   AODV                    4 November 2002


Author's Addresses

   Questions about this memo can be directed to:

      Charles E. Perkins
      Communications Systems Laboratory
      Nokia Research Center
      313 Fairchild Drive
      Mountain View, CA 94303
      USA
      +1 650 625 2986
      +1 650 691 2170 (fax)
      charliep@iprg.nokia.com


      Elizabeth M. Belding-Royer
      Department of Computer Science
      University of California, Santa Barbara
      Santa Barbara, CA 93106
      +1 805 893 3411
      +1 805 893 8553 (fax)
      ebelding@cs.ucsb.edu


      Samir R. Das
      Department of Electrical and Computer Engineering
      & Computer Science
      University of Cincinnati
      Cincinnati, OH 45221-0030
      +1 513 556 2594
      +1 513 556 7326 (fax)
      sdas@ececs.uc.edu




















Perkins, Belding-Royer, Das         Expires 4 May 2003         [Page 33]

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



From mailnull@www1.ietf.org  Fri Nov 15 17:01:56 2002
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA21161
	for <manet-archive@odin.ietf.org>; Fri, 15 Nov 2002 17:01:56 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id gAFM46N20583
	for manet-archive@odin.ietf.org; Fri, 15 Nov 2002 17:04:06 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gAFM46v20580
	for <manet-web-archive@optimus.ietf.org>; Fri, 15 Nov 2002 17:04:06 -0500
Received: from www1.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA21135
	for <manet-web-archive@ietf.org>; Fri, 15 Nov 2002 17:01:25 -0500 (EST)
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gAFKstv15584;
	Fri, 15 Nov 2002 15:54:55 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gA7KZ3v15464
	for <manet@optimus.ietf.org>; Thu, 7 Nov 2002 15:35:03 -0500
Received: from CNRI.Reston.VA.US (localhost [127.0.0.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA08965
	for <1timer>; Thu, 7 Nov 2002 15:11:40 -0500 (EST)
Message-Id: <200211072011.PAA08965@ietf.org>
From: The IESG <iesg-secretary@ietf.org>
To: All IETF Working Groups: ;
x-msg: NoteWell
Date: Thu, 07 Nov 2002 15:11:40 -0500
Subject: [manet] Note Well Statement
Sender: manet-admin@ietf.org
Errors-To: manet-admin@ietf.org
X-BeenThere: manet@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/manet>,
	<mailto:manet-request@ietf.org?subject=unsubscribe>
List-Id: Mobile Ad-hoc Networks  <manet.ietf.org>
List-Post: <mailto:manet@ietf.org>
List-Help: <mailto:manet-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/manet>,
	<mailto:manet-request@ietf.org?subject=subscribe>


From time to time, especially just before a meeting, this statement is to
be sent to each and every IETF working group mailing list.
===========================================================================

				NOTE WELL

All statements related to the activities of the IETF and addressed to the
IETF are subject to all provisions of Section 10 of RFC 2026, which grants
to the IETF and its participants certain licenses and rights in such
statements.

Such statements include verbal statements in IETF meetings, as well as
written and electronic communications made at any time or place, which are
addressed to

    - the IETF plenary session,
    - any IETF working group or portion thereof,
    - the IESG, or any member thereof on behalf of the IESG,
    - the IAB or any member thereof on behalf of the IAB,
    - any IETF mailing list, including the IETF list itself,
      any working group or design team list, or any other list
      functioning under IETF auspices,
    - the RFC Editor or the Internet-Drafts function

Statements made outside of an IETF meeting, mailing list or other function,
that are clearly not intended to be input to an IETF activity, group or
function, are not subject to these provisions.
_______________________________________________
manet mailing list
manet@ietf.org
https://www1.ietf.org/mailman/listinfo/manet



From manet-admin@ietf.org  Fri Nov 15 17:02:25 2002
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA21178
	for <manet-archive@lists.ietf.org>; Fri, 15 Nov 2002 17:02:25 -0500 (EST)
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gAFKstv15584;
	Fri, 15 Nov 2002 15:54:55 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gA7KZ3v15464
	for <manet@optimus.ietf.org>; Thu, 7 Nov 2002 15:35:03 -0500
Received: from CNRI.Reston.VA.US (localhost [127.0.0.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA08965
	for <1timer>; Thu, 7 Nov 2002 15:11:40 -0500 (EST)
Message-Id: <200211072011.PAA08965@ietf.org>
From: The IESG <iesg-secretary@ietf.org>
To: All IETF Working Groups: ;
x-msg: NoteWell
Date: Thu, 07 Nov 2002 15:11:40 -0500
Subject: [manet] Note Well Statement
Sender: manet-admin@ietf.org
Errors-To: manet-admin@ietf.org
X-BeenThere: manet@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/manet>,
	<mailto:manet-request@ietf.org?subject=unsubscribe>
List-Id: Mobile Ad-hoc Networks  <manet.ietf.org>
List-Post: <mailto:manet@ietf.org>
List-Help: <mailto:manet-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/manet>,
	<mailto:manet-request@ietf.org?subject=subscribe>


From time to time, especially just before a meeting, this statement is to
be sent to each and every IETF working group mailing list.
===========================================================================

				NOTE WELL

All statements related to the activities of the IETF and addressed to the
IETF are subject to all provisions of Section 10 of RFC 2026, which grants
to the IETF and its participants certain licenses and rights in such
statements.

Such statements include verbal statements in IETF meetings, as well as
written and electronic communications made at any time or place, which are
addressed to

    - the IETF plenary session,
    - any IETF working group or portion thereof,
    - the IESG, or any member thereof on behalf of the IESG,
    - the IAB or any member thereof on behalf of the IAB,
    - any IETF mailing list, including the IETF list itself,
      any working group or design team list, or any other list
      functioning under IETF auspices,
    - the RFC Editor or the Internet-Drafts function

Statements made outside of an IETF meeting, mailing list or other function,
that are clearly not intended to be input to an IETF activity, group or
function, are not subject to these provisions.
_______________________________________________
manet mailing list
manet@ietf.org
https://www1.ietf.org/mailman/listinfo/manet


From manet-admin@ietf.org  Fri Nov 15 17:43:33 2002
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA22317
	for <manet-archive@lists.ietf.org>; Fri, 15 Nov 2002 17:43:33 -0500 (EST)
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gAFLN9v17227;
	Fri, 15 Nov 2002 16:23:09 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gAEGm8v08121
	for <manet@optimus.ietf.org>; Thu, 14 Nov 2002 11:48:09 -0500
Received: from web12708.mail.yahoo.com (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id LAA24021
	for <manet@ietf.org>; Thu, 14 Nov 2002 11:45:30 -0500 (EST)
Message-ID: <20021114164804.73682.qmail@web12708.mail.yahoo.com>
Received: from [47.234.0.51] by web12708.mail.yahoo.com via HTTP; Thu, 14 Nov 2002 08:48:04 PST
Date: Thu, 14 Nov 2002 08:48:04 -0800 (PST)
From: He Huang <huanghe_1@yahoo.com>
To: manet@ietf.org
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Subject: [manet] Protocol Correctness and Complexity
Sender: manet-admin@ietf.org
Errors-To: manet-admin@ietf.org
X-BeenThere: manet@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/manet>,
	<mailto:manet-request@ietf.org?subject=unsubscribe>
List-Id: Mobile Ad-hoc Networks  <manet.ietf.org>
List-Post: <mailto:manet@ietf.org>
List-Help: <mailto:manet-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/manet>,
	<mailto:manet-request@ietf.org?subject=subscribe>

Hello,

Could anyone point out the papers or resources on
analyzing protocol correctness and complexity,
especially in MANET? Thanks in advance,

He Huang

__________________________________________________
Do you Yahoo!?
Yahoo! Web Hosting - Let the expert host your site
http://webhosting.yahoo.com
_______________________________________________
manet mailing list
manet@ietf.org
https://www1.ietf.org/mailman/listinfo/manet


From mailnull@www1.ietf.org  Fri Nov 15 17:50:58 2002
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA22611
	for <manet-archive@odin.ietf.org>; Fri, 15 Nov 2002 17:50:57 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id gAFMr9j24045
	for manet-archive@odin.ietf.org; Fri, 15 Nov 2002 17:53:09 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gAFMr9v24042
	for <manet-web-archive@optimus.ietf.org>; Fri, 15 Nov 2002 17:53:09 -0500
Received: from www1.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA22592
	for <manet-web-archive@ietf.org>; Fri, 15 Nov 2002 17:50:26 -0500 (EST)
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gAFLN9v17227;
	Fri, 15 Nov 2002 16:23:09 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gAEGm8v08121
	for <manet@optimus.ietf.org>; Thu, 14 Nov 2002 11:48:09 -0500
Received: from web12708.mail.yahoo.com (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id LAA24021
	for <manet@ietf.org>; Thu, 14 Nov 2002 11:45:30 -0500 (EST)
Message-ID: <20021114164804.73682.qmail@web12708.mail.yahoo.com>
Received: from [47.234.0.51] by web12708.mail.yahoo.com via HTTP; Thu, 14 Nov 2002 08:48:04 PST
Date: Thu, 14 Nov 2002 08:48:04 -0800 (PST)
From: He Huang <huanghe_1@yahoo.com>
To: manet@ietf.org
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Subject: [manet] Protocol Correctness and Complexity
Sender: manet-admin@ietf.org
Errors-To: manet-admin@ietf.org
X-BeenThere: manet@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/manet>,
	<mailto:manet-request@ietf.org?subject=unsubscribe>
List-Id: Mobile Ad-hoc Networks  <manet.ietf.org>
List-Post: <mailto:manet@ietf.org>
List-Help: <mailto:manet-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/manet>,
	<mailto:manet-request@ietf.org?subject=subscribe>

Hello,

Could anyone point out the papers or resources on
analyzing protocol correctness and complexity,
especially in MANET? Thanks in advance,

He Huang

__________________________________________________
Do you Yahoo!?
Yahoo! Web Hosting - Let the expert host your site
http://webhosting.yahoo.com
_______________________________________________
manet mailing list
manet@ietf.org
https://www1.ietf.org/mailman/listinfo/manet



From manet-admin@ietf.org  Sat Nov 16 22:21:27 2002
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id WAA00166
	for <manet-archive@lists.ietf.org>; Sat, 16 Nov 2002 22:21:27 -0500 (EST)
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gAH3FOv12433;
	Sat, 16 Nov 2002 22:15:24 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gAH2wcv11566
	for <manet@optimus.ietf.org>; Sat, 16 Nov 2002 21:58:38 -0500
Received: from smtp-send.myrealbox.com (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id VAA29860
	for <manet@ietf.org>; Sat, 16 Nov 2002 21:55:52 -0500 (EST)
Received: from nppham [130.220.36.156] by myrealbox.com
	with NetMail ModWeb Module; Sun, 17 Nov 2002 13:28:31 +1050
From: "Peter Pham" <nppham@myrealbox.com>
To: manet@ietf.org
Date: Sun, 17 Nov 2002 13:28:31 +1050
X-Mailer: NetMail ModWeb Module
X-Sender: nppham
MIME-Version: 1.0
Message-ID: <1037501911.55676860nppham@myrealbox.com>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: 8bit
X-MIME-Autoconverted: from quoted-printable to 8bit by www1.ietf.org id gAH2wcv11567
Subject: [manet] Analytical Model for TCP in Wireless Environment
Sender: manet-admin@ietf.org
Errors-To: manet-admin@ietf.org
X-BeenThere: manet@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/manet>,
	<mailto:manet-request@ietf.org?subject=unsubscribe>
List-Id: Mobile Ad-hoc Networks  <manet.ietf.org>
List-Post: <mailto:manet@ietf.org>
List-Help: <mailto:manet-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/manet>,
	<mailto:manet-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 8bit

Hi 

Has anyone read the paper "new analytical model fr TCP throughput in Wireless environment" from Katsuhiro Naito, Hiraku Okada, Takaya...et al..
I am intending to verify the model using simulation.
I will really appreciate comments on the model proposed in this paper.
Please email directly to me. 
Thank you very much for your help

Peter Pham
Institute for Telecommunications Research
University of South Australia
Peter Phuc Pham
University of South Australia
Institute for Telecommunication Research
Phone: 61-883023869
Email: ppham@spri.levels.unisa.edu.au
WWW:   www.itr.unisa.edu.au/~ppham
_______________________________________________
manet mailing list
manet@ietf.org
https://www1.ietf.org/mailman/listinfo/manet


From mailnull@www1.ietf.org  Sat Nov 16 22:39:56 2002
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id WAA00761
	for <manet-archive@odin.ietf.org>; Sat, 16 Nov 2002 22:39:56 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id gAH3gC113679
	for manet-archive@odin.ietf.org; Sat, 16 Nov 2002 22:42:12 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gAH3gCv13676
	for <manet-web-archive@optimus.ietf.org>; Sat, 16 Nov 2002 22:42:12 -0500
Received: from www1.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id WAA00755
	for <manet-web-archive@ietf.org>; Sat, 16 Nov 2002 22:39:25 -0500 (EST)
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gAH3FOv12433;
	Sat, 16 Nov 2002 22:15:24 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gAH2wcv11566
	for <manet@optimus.ietf.org>; Sat, 16 Nov 2002 21:58:38 -0500
Received: from smtp-send.myrealbox.com (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id VAA29860
	for <manet@ietf.org>; Sat, 16 Nov 2002 21:55:52 -0500 (EST)
Received: from nppham [130.220.36.156] by myrealbox.com
	with NetMail ModWeb Module; Sun, 17 Nov 2002 13:28:31 +1050
From: "Peter Pham" <nppham@myrealbox.com>
To: manet@ietf.org
Date: Sun, 17 Nov 2002 13:28:31 +1050
X-Mailer: NetMail ModWeb Module
X-Sender: nppham
MIME-Version: 1.0
Message-ID: <1037501911.55676860nppham@myrealbox.com>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: 8bit
X-MIME-Autoconverted: from quoted-printable to 8bit by www1.ietf.org id gAH2wcv11567
Subject: [manet] Analytical Model for TCP in Wireless Environment
Sender: manet-admin@ietf.org
Errors-To: manet-admin@ietf.org
X-BeenThere: manet@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/manet>,
	<mailto:manet-request@ietf.org?subject=unsubscribe>
List-Id: Mobile Ad-hoc Networks  <manet.ietf.org>
List-Post: <mailto:manet@ietf.org>
List-Help: <mailto:manet-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/manet>,
	<mailto:manet-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 8bit
Content-Transfer-Encoding: 8bit

Hi 

Has anyone read the paper "new analytical model fr TCP throughput in Wireless environment" from Katsuhiro Naito, Hiraku Okada, Takaya...et al..
I am intending to verify the model using simulation.
I will really appreciate comments on the model proposed in this paper.
Please email directly to me. 
Thank you very much for your help

Peter Pham
Institute for Telecommunications Research
University of South Australia
Peter Phuc Pham
University of South Australia
Institute for Telecommunication Research
Phone: 61-883023869
Email: ppham@spri.levels.unisa.edu.au
WWW:   www.itr.unisa.edu.au/~ppham
_______________________________________________
manet mailing list
manet@ietf.org
https://www1.ietf.org/mailman/listinfo/manet



From mailnull@www1.ietf.org  Mon Nov 18 07:48:04 2002
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id HAA19326
	for <manet-archive@odin.ietf.org>; Mon, 18 Nov 2002 07:48:04 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id gAICoCN20878
	for manet-archive@odin.ietf.org; Mon, 18 Nov 2002 07:50:12 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gAICoBv20875
	for <manet-web-archive@optimus.ietf.org>; Mon, 18 Nov 2002 07:50:11 -0500
Received: from www1.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id HAA19305
	for <manet-web-archive@ietf.org>; Mon, 18 Nov 2002 07:47:33 -0500 (EST)
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gAICd8v20517;
	Mon, 18 Nov 2002 07:39:08 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gAICW9v19820
	for <manet@optimus.ietf.org>; Mon, 18 Nov 2002 07:32:09 -0500
Received: from mailgw1.atr.co.jp (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id HAA19033
	for <manet@ietf.org>; Mon, 18 Nov 2002 07:29:30 -0500 (EST)
Received: from vcms.atr.co.jp (beta.atr.co.jp [133.186.254.11])
	by mailgw1.atr.co.jp (Postfix) with ESMTP id 7926618AE8
	for <manet@ietf.org>; Mon, 18 Nov 2002 20:14:32 +0900 (JST)
Received: from acr.acr.atr.co.jp (localhost [127.0.0.1])
	by vcms.atr.co.jp (Postfix) with ESMTP id DA37EDBD3
	for <manet@ietf.org>; Mon, 18 Nov 2002 20:14:31 +0900 (JST)
Received: from rpc41 by acr.acr.atr.co.jp (8.9.3/3.7W)
	id UAA14376; Mon, 18 Nov 2002 20:14:41 +0900 (JST)
From: "Shingo HORISAWA" <horisawa@atr.co.jp>
To: "MANET Mailing List" <manet@ietf.org>
Date: Mon, 18 Nov 2002 20:14:31 +0900
Message-ID: <HEEGKKKPEHOBJFHFEPAPMEGPCNAA.horisawa@atr.co.jp>
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-2022-jp"
Content-Transfer-Encoding: 7bit
X-Priority: 3 (Normal)
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook IMO, Build 9.0.2416 (9.0.2911.0)
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1106
Importance: Normal
Content-Transfer-Encoding: 7bit
Subject: [manet] GSR/FSR implementation on Linux
Sender: manet-admin@ietf.org
Errors-To: manet-admin@ietf.org
X-BeenThere: manet@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/manet>,
	<mailto:manet-request@ietf.org?subject=unsubscribe>
List-Id: Mobile Ad-hoc Networks  <manet.ietf.org>
List-Post: <mailto:manet@ietf.org>
List-Help: <mailto:manet-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/manet>,
	<mailto:manet-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit

Hi all.

I developed GSR/FSR implementations which run on Linux.

These implementations are based on FSR Internet-Draft version 2,
but are different from the Draft in the following points:

- "destination sequence number" field length (draft: 24 bits, our
implementations: 16 bits)
- "N_neighbors" field length (draft: 8 bits, our implementations: 16 bits)
- We use the normal Dijkstra instead of the modified-Dijkstra when
calculating routes
- and some other details...

You can download and use them from the following page:

GSR/FSR implementation on Linux
http://www.acr.atr.co.jp/~horisawa/download/gsrfsr.html

If you find ny problems, please point them out.

Thanks !

**********************************************************
   Shingo Horisawa

     Researcher
     Department 1

     ATR Adaptive Communications Research Laboratories

     2-2-2 Hikaridai, Seika-cho, Soraku-gun, Kyoto 619-0288, Japan
     TEL +81-774-95-2720   FAX +81-774-95-1509
     E-MAIL  horisawa@atr.co.jp
     URL : http://www.acr.atr.co.jp/acr/
**********************************************************

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



From manet-admin@ietf.org  Mon Nov 18 07:48:37 2002
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id HAA19363
	for <manet-archive@lists.ietf.org>; Mon, 18 Nov 2002 07:48:37 -0500 (EST)
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gAICd8v20517;
	Mon, 18 Nov 2002 07:39:08 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gAICW9v19820
	for <manet@optimus.ietf.org>; Mon, 18 Nov 2002 07:32:09 -0500
Received: from mailgw1.atr.co.jp (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id HAA19033
	for <manet@ietf.org>; Mon, 18 Nov 2002 07:29:30 -0500 (EST)
Received: from vcms.atr.co.jp (beta.atr.co.jp [133.186.254.11])
	by mailgw1.atr.co.jp (Postfix) with ESMTP id 7926618AE8
	for <manet@ietf.org>; Mon, 18 Nov 2002 20:14:32 +0900 (JST)
Received: from acr.acr.atr.co.jp (localhost [127.0.0.1])
	by vcms.atr.co.jp (Postfix) with ESMTP id DA37EDBD3
	for <manet@ietf.org>; Mon, 18 Nov 2002 20:14:31 +0900 (JST)
Received: from rpc41 by acr.acr.atr.co.jp (8.9.3/3.7W)
	id UAA14376; Mon, 18 Nov 2002 20:14:41 +0900 (JST)
From: "Shingo HORISAWA" <horisawa@atr.co.jp>
To: "MANET Mailing List" <manet@ietf.org>
Date: Mon, 18 Nov 2002 20:14:31 +0900
Message-ID: <HEEGKKKPEHOBJFHFEPAPMEGPCNAA.horisawa@atr.co.jp>
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-2022-jp"
Content-Transfer-Encoding: 7bit
X-Priority: 3 (Normal)
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook IMO, Build 9.0.2416 (9.0.2911.0)
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1106
Importance: Normal
Content-Transfer-Encoding: 7bit
Subject: [manet] GSR/FSR implementation on Linux
Sender: manet-admin@ietf.org
Errors-To: manet-admin@ietf.org
X-BeenThere: manet@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/manet>,
	<mailto:manet-request@ietf.org?subject=unsubscribe>
List-Id: Mobile Ad-hoc Networks  <manet.ietf.org>
List-Post: <mailto:manet@ietf.org>
List-Help: <mailto:manet-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/manet>,
	<mailto:manet-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 7bit

Hi all.

I developed GSR/FSR implementations which run on Linux.

These implementations are based on FSR Internet-Draft version 2,
but are different from the Draft in the following points:

- "destination sequence number" field length (draft: 24 bits, our
implementations: 16 bits)
- "N_neighbors" field length (draft: 8 bits, our implementations: 16 bits)
- We use the normal Dijkstra instead of the modified-Dijkstra when
calculating routes
- and some other details...

You can download and use them from the following page:

GSR/FSR implementation on Linux
http://www.acr.atr.co.jp/~horisawa/download/gsrfsr.html

If you find ny problems, please point them out.

Thanks !

**********************************************************
   Shingo Horisawa

     Researcher
     Department 1

     ATR Adaptive Communications Research Laboratories

     2-2-2 Hikaridai, Seika-cho, Soraku-gun, Kyoto 619-0288, Japan
     TEL +81-774-95-2720   FAX +81-774-95-1509
     E-MAIL  horisawa@atr.co.jp
     URL : http://www.acr.atr.co.jp/acr/
**********************************************************

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


From manet-admin@ietf.org  Mon Nov 18 16:07:22 2002
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA03516
	for <manet-archive@lists.ietf.org>; Mon, 18 Nov 2002 16:07:22 -0500 (EST)
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gAIKvav18370;
	Mon, 18 Nov 2002 15:57:36 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gAIKo3v18014
	for <manet@optimus.ietf.org>; Mon, 18 Nov 2002 15:50:03 -0500
Received: from gta.ufrj.br (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA02972
	for <manet@ietf.org>; Mon, 18 Nov 2002 15:47:18 -0500 (EST)
Received: from localhost (bernardo@localhost)
	by gta.ufrj.br (8.11.6/8.11.6) with ESMTP id gAIJoIF13310
	for <manet@ietf.org>; Mon, 18 Nov 2002 17:50:18 -0200
Date: Mon, 18 Nov 2002 17:50:18 -0200 (BRST)
From: Bernardo Antunes Maciel Villela <bernardo@gta.ufrj.br>
To: manet@ietf.org
In-Reply-To: <200211071729.gA7HTrm24121@letters.cs.ucsb.edu>
Message-ID: <Pine.LNX.4.44.0211181732030.13048-100000@recreio.gta.ufrj.br>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Subject: [manet] Simulating AODV in NS
Sender: manet-admin@ietf.org
Errors-To: manet-admin@ietf.org
X-BeenThere: manet@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/manet>,
	<mailto:manet-request@ietf.org?subject=unsubscribe>
List-Id: Mobile Ad-hoc Networks  <manet.ietf.org>
List-Post: <mailto:manet@ietf.org>
List-Help: <mailto:manet-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/manet>,
	<mailto:manet-request@ietf.org?subject=subscribe>

Hi,

I have this question: the AODV version implemented in NS today is the 
version made by Monarch and called AODV-LL in their paper "A 
Performance Comparison of Multi-hop Wireless Ad Hoc Network Routing 
Protocols" (by J. Broch, D. Maltz, D. Johnson, Y. Hu and J. Jetcheva)?

I'd like to be sure about that because this AODV-LL version uses
no hello AODV mechanism. Instead it utilizes link layer 
feedback from 802.11. BUT SUCH APPROACH CHANGES AODV PROTOCOL, because
 this way all link breakage is only on-demand and we only know about
a broken link when we have a packet to send through this link.

If anyone knows this answer, please let me know.
Thanks.
Bernardo.

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


From mailnull@www1.ietf.org  Mon Nov 18 16:31:31 2002
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA04188
	for <manet-archive@odin.ietf.org>; Mon, 18 Nov 2002 16:31:31 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id gAILXiZ20568
	for manet-archive@odin.ietf.org; Mon, 18 Nov 2002 16:33:44 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gAILXhv20565
	for <manet-web-archive@optimus.ietf.org>; Mon, 18 Nov 2002 16:33:43 -0500
Received: from www1.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA04173
	for <manet-web-archive@ietf.org>; Mon, 18 Nov 2002 16:31:00 -0500 (EST)
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gAIKvav18370;
	Mon, 18 Nov 2002 15:57:36 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gAIKo3v18014
	for <manet@optimus.ietf.org>; Mon, 18 Nov 2002 15:50:03 -0500
Received: from gta.ufrj.br (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA02972
	for <manet@ietf.org>; Mon, 18 Nov 2002 15:47:18 -0500 (EST)
Received: from localhost (bernardo@localhost)
	by gta.ufrj.br (8.11.6/8.11.6) with ESMTP id gAIJoIF13310
	for <manet@ietf.org>; Mon, 18 Nov 2002 17:50:18 -0200
Date: Mon, 18 Nov 2002 17:50:18 -0200 (BRST)
From: Bernardo Antunes Maciel Villela <bernardo@gta.ufrj.br>
To: manet@ietf.org
In-Reply-To: <200211071729.gA7HTrm24121@letters.cs.ucsb.edu>
Message-ID: <Pine.LNX.4.44.0211181732030.13048-100000@recreio.gta.ufrj.br>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Subject: [manet] Simulating AODV in NS
Sender: manet-admin@ietf.org
Errors-To: manet-admin@ietf.org
X-BeenThere: manet@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/manet>,
	<mailto:manet-request@ietf.org?subject=unsubscribe>
List-Id: Mobile Ad-hoc Networks  <manet.ietf.org>
List-Post: <mailto:manet@ietf.org>
List-Help: <mailto:manet-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/manet>,
	<mailto:manet-request@ietf.org?subject=subscribe>

Hi,

I have this question: the AODV version implemented in NS today is the 
version made by Monarch and called AODV-LL in their paper "A 
Performance Comparison of Multi-hop Wireless Ad Hoc Network Routing 
Protocols" (by J. Broch, D. Maltz, D. Johnson, Y. Hu and J. Jetcheva)?

I'd like to be sure about that because this AODV-LL version uses
no hello AODV mechanism. Instead it utilizes link layer 
feedback from 802.11. BUT SUCH APPROACH CHANGES AODV PROTOCOL, because
 this way all link breakage is only on-demand and we only know about
a broken link when we have a packet to send through this link.

If anyone knows this answer, please let me know.
Thanks.
Bernardo.

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



From manet-admin@ietf.org  Mon Nov 18 21:19:34 2002
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id VAA11137
	for <manet-archive@lists.ietf.org>; Mon, 18 Nov 2002 21:19:34 -0500 (EST)
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gAJ2Abv04313;
	Mon, 18 Nov 2002 21:10:37 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gAJ25ov03594
	for <manet@optimus.ietf.org>; Mon, 18 Nov 2002 21:05:50 -0500
Received: from gandalf.icr.a-star.edu.sg (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id VAA10896
	for <manet@ietf.org>; Mon, 18 Nov 2002 21:03:01 -0500 (EST)
Received: from gwserver.icr.a-star.edu.sg (gwserver.icr.a-star.edu.sg [137.132.31.253])
	by gandalf.icr.a-star.edu.sg (8.12.2+Sun/8.12.2) with ESMTP id gAJ26hXw005834
	for <manet@ietf.org>; Tue, 19 Nov 2002 10:06:43 +0800 (SGT)
Received: from yoyo
	([204.42.66.233])
	by gwserver.icr.a-star.edu.sg; Tue, 19 Nov 2002 09:59:19 +0800
Message-ID: <001401c28f70$0ffbe230$e9422acc@yoyo>
From: "Paul" <tanpaul@cwc.nus.edu.sg>
To: <manet@ietf.org>
Date: Mon, 18 Nov 2002 21:04:50 -0500
MIME-Version: 1.0
Content-Type: multipart/alternative;
	boundary="----=_NextPart_000_0011_01C28F46.228D3F40"
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 6.00.2600.0000
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2600.0000
Subject: [manet] 802.11 API
Sender: manet-admin@ietf.org
Errors-To: manet-admin@ietf.org
X-BeenThere: manet@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/manet>,
	<mailto:manet-request@ietf.org?subject=unsubscribe>
List-Id: Mobile Ad-hoc Networks  <manet.ietf.org>
List-Post: <mailto:manet@ietf.org>
List-Help: <mailto:manet-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/manet>,
	<mailto:manet-request@ietf.org?subject=subscribe>

This is a multi-part message in MIME format.

------=_NextPart_000_0011_01C28F46.228D3F40
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

Hi all,

Currently, are there any API support for 802.11 wireless interface =
device
driver (Linux) which allows me to register the assoc/de-assoc events? =
How
(currently) can MANET protocols (if any) interacts with these events.

Cheers,
Paul


------=_NextPart_000_0011_01C28F46.228D3F40
Content-Type: text/html;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META http-equiv=3DContent-Type content=3D"text/html; =
charset=3Diso-8859-1">
<META content=3D"MSHTML 6.00.2600.0" name=3DGENERATOR>
<STYLE></STYLE>
</HEAD>
<BODY bgColor=3D#a6caf0>Hi all,<BR><BR>Currently, are there any API =
support for=20
802.11 wireless interface device<BR>driver (Linux) which allows me to =
register=20
the assoc/de-assoc events? How<BR>(currently) can MANET protocols (if =
any)=20
interacts with these events.<BR><BR>Cheers,<BR>Paul<BR></BODY></HTML>

------=_NextPart_000_0011_01C28F46.228D3F40--


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


From mailnull@www1.ietf.org  Mon Nov 18 21:30:09 2002
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id VAA11514
	for <manet-archive@odin.ietf.org>; Mon, 18 Nov 2002 21:30:09 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id gAJ2WOn05158
	for manet-archive@odin.ietf.org; Mon, 18 Nov 2002 21:32:24 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gAJ2WMv05142
	for <manet-web-archive@optimus.ietf.org>; Mon, 18 Nov 2002 21:32:22 -0500
Received: from www1.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id VAA11477
	for <manet-web-archive@ietf.org>; Mon, 18 Nov 2002 21:29:36 -0500 (EST)
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gAJ2Abv04313;
	Mon, 18 Nov 2002 21:10:37 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gAJ25ov03594
	for <manet@optimus.ietf.org>; Mon, 18 Nov 2002 21:05:50 -0500
Received: from gandalf.icr.a-star.edu.sg (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id VAA10896
	for <manet@ietf.org>; Mon, 18 Nov 2002 21:03:01 -0500 (EST)
Received: from gwserver.icr.a-star.edu.sg (gwserver.icr.a-star.edu.sg [137.132.31.253])
	by gandalf.icr.a-star.edu.sg (8.12.2+Sun/8.12.2) with ESMTP id gAJ26hXw005834
	for <manet@ietf.org>; Tue, 19 Nov 2002 10:06:43 +0800 (SGT)
Received: from yoyo
	([204.42.66.233])
	by gwserver.icr.a-star.edu.sg; Tue, 19 Nov 2002 09:59:19 +0800
Message-ID: <001401c28f70$0ffbe230$e9422acc@yoyo>
From: "Paul" <tanpaul@cwc.nus.edu.sg>
To: <manet@ietf.org>
Date: Mon, 18 Nov 2002 21:04:50 -0500
MIME-Version: 1.0
Content-Type: multipart/alternative;
	boundary="----=_NextPart_000_0011_01C28F46.228D3F40"
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 6.00.2600.0000
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2600.0000
Subject: [manet] 802.11 API
Sender: manet-admin@ietf.org
Errors-To: manet-admin@ietf.org
X-BeenThere: manet@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/manet>,
	<mailto:manet-request@ietf.org?subject=unsubscribe>
List-Id: Mobile Ad-hoc Networks  <manet.ietf.org>
List-Post: <mailto:manet@ietf.org>
List-Help: <mailto:manet-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/manet>,
	<mailto:manet-request@ietf.org?subject=subscribe>

This is a multi-part message in MIME format.

------=_NextPart_000_0011_01C28F46.228D3F40
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

Hi all,

Currently, are there any API support for 802.11 wireless interface =
device
driver (Linux) which allows me to register the assoc/de-assoc events? =
How
(currently) can MANET protocols (if any) interacts with these events.

Cheers,
Paul


------=_NextPart_000_0011_01C28F46.228D3F40
Content-Type: text/html;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META http-equiv=3DContent-Type content=3D"text/html; =
charset=3Diso-8859-1">
<META content=3D"MSHTML 6.00.2600.0" name=3DGENERATOR>
<STYLE></STYLE>
</HEAD>
<BODY bgColor=3D#a6caf0>Hi all,<BR><BR>Currently, are there any API =
support for=20
802.11 wireless interface device<BR>driver (Linux) which allows me to =
register=20
the assoc/de-assoc events? How<BR>(currently) can MANET protocols (if =
any)=20
interacts with these events.<BR><BR>Cheers,<BR>Paul<BR></BODY></HTML>

------=_NextPart_000_0011_01C28F46.228D3F40--


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



From mailnull@www1.ietf.org  Tue Nov 19 06:13:23 2002
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id GAA01669
	for <manet-archive@odin.ietf.org>; Tue, 19 Nov 2002 06:13:23 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id gAJBFWR09639
	for manet-archive@odin.ietf.org; Tue, 19 Nov 2002 06:15:32 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gAJBFWv09636
	for <manet-web-archive@optimus.ietf.org>; Tue, 19 Nov 2002 06:15:32 -0500
Received: from www1.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id GAA01641
	for <manet-web-archive@ietf.org>; Tue, 19 Nov 2002 06:12:52 -0500 (EST)
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gAJB1Jv08347;
	Tue, 19 Nov 2002 06:01:19 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gAJAftv07791
	for <manet@optimus.ietf.org>; Tue, 19 Nov 2002 05:41:55 -0500
Received: from gta.ufrj.br (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id FAA00979
	for <manet@ietf.org>; Tue, 19 Nov 2002 05:39:15 -0500 (EST)
Received: from tijuca.gta.ufrj.br (tijuca.gta.ufrj.br [146.164.69.28])
	by gta.ufrj.br (8.11.6/8.11.6) with ESMTP id gAJ9g9P17795;
	Tue, 19 Nov 2002 07:42:12 -0200
Received: from localhost (bernardo@localhost)
	by tijuca.gta.ufrj.br (8.11.6/8.11.6) with ESMTP id gAJAiIV25629;
	Tue, 19 Nov 2002 08:44:21 -0200
Date: Tue, 19 Nov 2002 08:44:18 -0200 (BRST)
From: Bernardo Antunes Maciel Villela <bernardo@gta.ufrj.br>
To: Moustafa Hasnaa <moustafa@enst.fr>
cc: manet@ietf.org
Subject: Re: [manet] Simulating AODV in NS
In-Reply-To: <002901c28fab$ed3ad2b0$dda2c289@galaxy.enst.fr>
Message-ID: <Pine.LNX.4.44.0211190837210.25553-100000@tijuca.gta.ufrj.br>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
X-MailScanner: Found to be clean
Sender: manet-admin@ietf.org
Errors-To: manet-admin@ietf.org
X-BeenThere: manet@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/manet>,
	<mailto:manet-request@ietf.org?subject=unsubscribe>
List-Id: Mobile Ad-hoc Networks  <manet.ietf.org>
List-Post: <mailto:manet@ietf.org>
List-Help: <mailto:manet-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/manet>,
	<mailto:manet-request@ietf.org?subject=subscribe>

On Tue, 19 Nov 2002, Moustafa Hasnaa wrote:

Hello,

Sorry, I didn't mention the version. The version I'm using is 
ns 2.1b7. Then I'm probably using AODV with hello message ...
I wonder anyway if they've built in ns distribution
a version for AODV with hello message and without hello message.

Thanks,
Bernardo.

> Hello,
>  I need to know you are talking about which Ns version, as i work with ns
> version7
>  And it contains AODV simulated with hello message...;
> 
> Regards.
> Hasnaa Moustafa
> ----- Original Message -----
> From: "Bernardo Antunes Maciel Villela" <bernardo@gta.ufrj.br>
> To: <manet@ietf.org>
> Sent: Monday, November 18, 2002 8:50 PM
> Subject: [manet] Simulating AODV in NS
> 
> 
> > Hi,
> >
> > I have this question: the AODV version implemented in NS today is the
> > version made by Monarch and called AODV-LL in their paper "A
> > Performance Comparison of Multi-hop Wireless Ad Hoc Network Routing
> > Protocols" (by J. Broch, D. Maltz, D. Johnson, Y. Hu and J. Jetcheva)?
> >
> > I'd like to be sure about that because this AODV-LL version uses
> > no hello AODV mechanism. Instead it utilizes link layer
> > feedback from 802.11. BUT SUCH APPROACH CHANGES AODV PROTOCOL, because
> >  this way all link breakage is only on-demand and we only know about
> > a broken link when we have a packet to send through this link.
> >
> > If anyone knows this answer, please let me know.
> > Thanks.
> > Bernardo.
> >
> > _______________________________________________
> > manet mailing list
> > manet@ietf.org
> > https://www1.ietf.org/mailman/listinfo/manet
> >
> 
> 
> --
> This message has been scanned for viruses and
> dangerous content by MailScanner, and is
> believed to be clean.
> 


--
This message has been scanned for viruses and
dangerous content by MailScanner, and is
believed to be clean.

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



From manet-admin@ietf.org  Tue Nov 19 06:14:12 2002
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id GAA01686
	for <manet-archive@lists.ietf.org>; Tue, 19 Nov 2002 06:14:12 -0500 (EST)
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gAJB1Jv08347;
	Tue, 19 Nov 2002 06:01:19 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gAJAftv07791
	for <manet@optimus.ietf.org>; Tue, 19 Nov 2002 05:41:55 -0500
Received: from gta.ufrj.br (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id FAA00979
	for <manet@ietf.org>; Tue, 19 Nov 2002 05:39:15 -0500 (EST)
Received: from tijuca.gta.ufrj.br (tijuca.gta.ufrj.br [146.164.69.28])
	by gta.ufrj.br (8.11.6/8.11.6) with ESMTP id gAJ9g9P17795;
	Tue, 19 Nov 2002 07:42:12 -0200
Received: from localhost (bernardo@localhost)
	by tijuca.gta.ufrj.br (8.11.6/8.11.6) with ESMTP id gAJAiIV25629;
	Tue, 19 Nov 2002 08:44:21 -0200
Date: Tue, 19 Nov 2002 08:44:18 -0200 (BRST)
From: Bernardo Antunes Maciel Villela <bernardo@gta.ufrj.br>
To: Moustafa Hasnaa <moustafa@enst.fr>
cc: manet@ietf.org
Subject: Re: [manet] Simulating AODV in NS
In-Reply-To: <002901c28fab$ed3ad2b0$dda2c289@galaxy.enst.fr>
Message-ID: <Pine.LNX.4.44.0211190837210.25553-100000@tijuca.gta.ufrj.br>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
X-MailScanner: Found to be clean
Sender: manet-admin@ietf.org
Errors-To: manet-admin@ietf.org
X-BeenThere: manet@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/manet>,
	<mailto:manet-request@ietf.org?subject=unsubscribe>
List-Id: Mobile Ad-hoc Networks  <manet.ietf.org>
List-Post: <mailto:manet@ietf.org>
List-Help: <mailto:manet-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/manet>,
	<mailto:manet-request@ietf.org?subject=subscribe>

On Tue, 19 Nov 2002, Moustafa Hasnaa wrote:

Hello,

Sorry, I didn't mention the version. The version I'm using is 
ns 2.1b7. Then I'm probably using AODV with hello message ...
I wonder anyway if they've built in ns distribution
a version for AODV with hello message and without hello message.

Thanks,
Bernardo.

> Hello,
>  I need to know you are talking about which Ns version, as i work with ns
> version7
>  And it contains AODV simulated with hello message...;
> 
> Regards.
> Hasnaa Moustafa
> ----- Original Message -----
> From: "Bernardo Antunes Maciel Villela" <bernardo@gta.ufrj.br>
> To: <manet@ietf.org>
> Sent: Monday, November 18, 2002 8:50 PM
> Subject: [manet] Simulating AODV in NS
> 
> 
> > Hi,
> >
> > I have this question: the AODV version implemented in NS today is the
> > version made by Monarch and called AODV-LL in their paper "A
> > Performance Comparison of Multi-hop Wireless Ad Hoc Network Routing
> > Protocols" (by J. Broch, D. Maltz, D. Johnson, Y. Hu and J. Jetcheva)?
> >
> > I'd like to be sure about that because this AODV-LL version uses
> > no hello AODV mechanism. Instead it utilizes link layer
> > feedback from 802.11. BUT SUCH APPROACH CHANGES AODV PROTOCOL, because
> >  this way all link breakage is only on-demand and we only know about
> > a broken link when we have a packet to send through this link.
> >
> > If anyone knows this answer, please let me know.
> > Thanks.
> > Bernardo.
> >
> > _______________________________________________
> > manet mailing list
> > manet@ietf.org
> > https://www1.ietf.org/mailman/listinfo/manet
> >
> 
> 
> --
> This message has been scanned for viruses and
> dangerous content by MailScanner, and is
> believed to be clean.
> 


--
This message has been scanned for viruses and
dangerous content by MailScanner, and is
believed to be clean.

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


From mailnull@www1.ietf.org  Tue Nov 19 08:02:13 2002
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA03974
	for <manet-archive@odin.ietf.org>; Tue, 19 Nov 2002 08:02:12 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id gAJD4La15158
	for manet-archive@odin.ietf.org; Tue, 19 Nov 2002 08:04:21 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gAJD4Lv15155
	for <manet-web-archive@optimus.ietf.org>; Tue, 19 Nov 2002 08:04:21 -0500
Received: from www1.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA03968
	for <manet-web-archive@ietf.org>; Tue, 19 Nov 2002 08:01:41 -0500 (EST)
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gAJCqxv14622;
	Tue, 19 Nov 2002 07:52:59 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gAJCijv14286
	for <manet@optimus.ietf.org>; Tue, 19 Nov 2002 07:44:45 -0500
Received: from anyida.tts.lth.se (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id HAA03472
	for <manet@ietf.org>; Tue, 19 Nov 2002 07:42:05 -0500 (EST)
Received: from telecom.lth.se (lina23.tts.lth.se [130.235.18.83])
	by anyida.tts.lth.se (8.9.3/8.9.3) with ESMTP id NAA17188;
	Tue, 19 Nov 2002 13:44:27 +0100 (MET)
Message-ID: <3DDA3239.9090800@telecom.lth.se>
Date: Tue, 19 Nov 2002 13:44:41 +0100
From: Alex Hamidian <alexh@telecom.lth.se>
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:0.9.4) Gecko/20011126 Netscape6/6.2.1
X-Accept-Language: en-us
MIME-Version: 1.0
To: Bernardo Antunes Maciel Villela <bernardo@gta.ufrj.br>
CC: Moustafa Hasnaa <moustafa@enst.fr>, manet@ietf.org
Subject: Re: [manet] Simulating AODV in NS
References: <Pine.LNX.4.44.0211190837210.25553-100000@tijuca.gta.ufrj.br>
Content-Type: multipart/alternative;
 boundary="------------020107000403090400040404"
Sender: manet-admin@ietf.org
Errors-To: manet-admin@ietf.org
X-BeenThere: manet@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/manet>,
	<mailto:manet-request@ietf.org?subject=unsubscribe>
List-Id: Mobile Ad-hoc Networks  <manet.ietf.org>
List-Post: <mailto:manet@ietf.org>
List-Help: <mailto:manet-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/manet>,
	<mailto:manet-request@ietf.org?subject=subscribe>


--------------020107000403090400040404
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit

Hi!

I think it's better if you search the mailing list of ns: 
http://www.isi.edu/nsnam/htdig/search.html for finding the answer to 
these questions. You could also mail the ns users: ns-users@isi.edu .

The AODV implementation in ns-2 (from ns-2.1b6 to ns-2.1b9; I don't know 
about earlier ns versions) can be run both with and without Hello 
messages. In aodv.h you can find:
/*
  Allows AODV to use link-layer (802.11) feedback in determining when
  links are up/down.
*/
#define AODV_LINK_LAYER_DETECTION

So you can choose between using link-layer feedback and Hello messages. 
For Hello messages you must comment the line  #define 
AODV_LINK_LAYER_DETECTION ; otherwise link-layer feedback is used.

Hope it helps
Ali Hamidian

Bernardo Antunes Maciel Villela wrote:

>On Tue, 19 Nov 2002, Moustafa Hasnaa wrote:
>
>Hello,
>
>Sorry, I didn't mention the version. The version I'm using is 
>ns 2.1b7. Then I'm probably using AODV with hello message ...
>I wonder anyway if they've built in ns distribution
>a version for AODV with hello message and without hello message.
>
>Thanks,
>Bernardo.
>
>>Hello,
>> I need to know you are talking about which Ns version, as i work with ns
>>version7
>> And it contains AODV simulated with hello message...;
>>
>>Regards.
>>Hasnaa Moustafa
>>----- Original Message -----
>>From: "Bernardo Antunes Maciel Villela" <bernardo@gta.ufrj.br>
>>To: <manet@ietf.org>
>>Sent: Monday, November 18, 2002 8:50 PM
>>Subject: [manet] Simulating AODV in NS
>>
>>
>>>Hi,
>>>
>>>I have this question: the AODV version implemented in NS today is the
>>>version made by Monarch and called AODV-LL in their paper "A
>>>Performance Comparison of Multi-hop Wireless Ad Hoc Network Routing
>>>Protocols" (by J. Broch, D. Maltz, D. Johnson, Y. Hu and J. Jetcheva)?
>>>
>>>I'd like to be sure about that because this AODV-LL version uses
>>>no hello AODV mechanism. Instead it utilizes link layer
>>>feedback from 802.11. BUT SUCH APPROACH CHANGES AODV PROTOCOL, because
>>> this way all link breakage is only on-demand and we only know about
>>>a broken link when we have a packet to send through this link.
>>>
>>>If anyone knows this answer, please let me know.
>>>Thanks.
>>>Bernardo.
>>>
>>>_______________________________________________
>>>manet mailing list
>>>manet@ietf.org
>>>https://www1.ietf.org/mailman/listinfo/manet
>>>
>>
>>--
>>This message has been scanned for viruses and
>>dangerous content by MailScanner, and is
>>believed to be clean.
>>
>
>
>--
>This message has been scanned for viruses and
>dangerous content by MailScanner, and is
>believed to be clean.
>
>_______________________________________________
>manet mailing list
>manet@ietf.org
>https://www1.ietf.org/mailman/listinfo/manet
>


--------------020107000403090400040404
Content-Type: text/html; charset=us-ascii
Content-Transfer-Encoding: 7bit

<html>
<head>
</head>
<body>
Hi!<br>
<br>
I think it's better if you search the mailing list of ns: <a href="http://www.isi.edu/nsnam/htdig/search.html">
http://www.isi.edu/nsnam/htdig/search.html</a>
 for finding the answer to these questions. You could also mail the ns users:
<a href="ns-users@isi.edu">ns-users@isi.edu</a>
.<br>
<br>
The AODV implementation in ns-2 (from ns-2.1b6 to ns-2.1b9; I don't know
about earlier ns versions) can be run both with and without Hello messages.
In aodv.h you can find:<br>
<font color="#3333ff">/*<br>
&nbsp; Allows AODV to use link-layer (802.11) feedback in determining when<br>
&nbsp; links are up/down.<br>
*/<br>
#define AODV_LINK_LAYER_DETECTION</font><br>
<br>
So you can choose between using link-layer feedback and Hello messages. For
Hello messages you must comment the line&nbsp; <font color="#3333ff">#define AODV_LINK_LAYER_DETECTION</font>
; otherwise link-layer feedback is used. <br>
<br>
Hope it helps<br>
Ali Hamidian<br>
<br>
Bernardo Antunes Maciel Villela wrote:<br>
<blockquote type="cite" cite="mid:Pine.LNX.4.44.0211190837210.25553-100000@tijuca.gta.ufrj.br">
  <pre wrap="">On Tue, 19 Nov 2002, Moustafa Hasnaa wrote:<br><br>Hello,<br><br>Sorry, I didn't mention the version. The version I'm using is <br>ns 2.1b7. Then I'm probably using AODV with hello message ...<br>I wonder anyway if they've built in ns distribution<br>a version for AODV with hello message and without hello message.<br><br>Thanks,<br>Bernardo.<br><br></pre>
  <blockquote type="cite">
    <pre wrap="">Hello,<br> I need to know you are talking about which Ns version, as i work with ns<br>version7<br> And it contains AODV simulated with hello message...;<br><br>Regards.<br>Hasnaa Moustafa<br>----- Original Message -----<br>From: "Bernardo Antunes Maciel Villela" <a class="moz-txt-link-rfc2396E" href="mailto:bernardo@gta.ufrj.br">&lt;bernardo@gta.ufrj.br&gt;</a><br>To: <a class="moz-txt-link-rfc2396E" href="mailto:manet@ietf.org">&lt;manet@ietf.org&gt;</a><br>Sent: Monday, November 18, 2002 8:50 PM<br>Subject: [manet] Simulating AODV in NS<br><br><br></pre>
    <blockquote type="cite">
      <pre wrap="">Hi,<br><br>I have this question: the AODV version implemented in NS today is the<br>version made by Monarch and called AODV-LL in their paper "A<br>Performance Comparison of Multi-hop Wireless Ad Hoc Network Routing<br>Protocols" (by J. Broch, D. Maltz, D. Johnson, Y. Hu and J. Jetcheva)?<br><br>I'd like to be sure about that because this AODV-LL version uses<br>no hello AODV mechanism. Instead it utilizes link layer<br>feedback from 802.11. BUT SUCH APPROACH CHANGES AODV PROTOCOL, because<br> this way all link breakage is only on-demand and we only know about<br>a broken link when we have a packet to send through this link.<br><br>If anyone knows this answer, please let me know.<br>Thanks.<br>Bernardo.<br><br>_______________________________________________<br>manet mailing list<br><a class="moz-txt-link-abbreviated" href="mailto:manet@ietf.org">manet@ietf.org</a><br><a class="moz-txt-link-freetext" href="https://www1.ietf.org/mailman/listinfo/manet">https:
//www1.ietf.org/mailman/listinfo/manet</a><br><br></pre>
      </blockquote>
      <pre wrap=""><br>--<br>This message has been scanned for viruses and<br>dangerous content by MailScanner, and is<br>believed to be clean.<br><br></pre>
      </blockquote>
      <pre wrap=""><!----><br><br>--<br>This message has been scanned for viruses and<br>dangerous content by MailScanner, and is<br>believed to be clean.<br><br>_______________________________________________<br>manet mailing list<br><a class="moz-txt-link-abbreviated" href="mailto:manet@ietf.org">manet@ietf.org</a><br><a class="moz-txt-link-freetext" href="https://www1.ietf.org/mailman/listinfo/manet">https://www1.ietf.org/mailman/listinfo/manet</a><br><br></pre>
      </blockquote>
      <br>
      </body>
      </html>

--------------020107000403090400040404--

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



From manet-admin@ietf.org  Tue Nov 19 08:02:42 2002
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA04003
	for <manet-archive@lists.ietf.org>; Tue, 19 Nov 2002 08:02:42 -0500 (EST)
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gAJCqxv14622;
	Tue, 19 Nov 2002 07:52:59 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gAJCijv14286
	for <manet@optimus.ietf.org>; Tue, 19 Nov 2002 07:44:45 -0500
Received: from anyida.tts.lth.se (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id HAA03472
	for <manet@ietf.org>; Tue, 19 Nov 2002 07:42:05 -0500 (EST)
Received: from telecom.lth.se (lina23.tts.lth.se [130.235.18.83])
	by anyida.tts.lth.se (8.9.3/8.9.3) with ESMTP id NAA17188;
	Tue, 19 Nov 2002 13:44:27 +0100 (MET)
Message-ID: <3DDA3239.9090800@telecom.lth.se>
Date: Tue, 19 Nov 2002 13:44:41 +0100
From: Alex Hamidian <alexh@telecom.lth.se>
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:0.9.4) Gecko/20011126 Netscape6/6.2.1
X-Accept-Language: en-us
MIME-Version: 1.0
To: Bernardo Antunes Maciel Villela <bernardo@gta.ufrj.br>
CC: Moustafa Hasnaa <moustafa@enst.fr>, manet@ietf.org
Subject: Re: [manet] Simulating AODV in NS
References: <Pine.LNX.4.44.0211190837210.25553-100000@tijuca.gta.ufrj.br>
Content-Type: multipart/alternative;
 boundary="------------020107000403090400040404"
Sender: manet-admin@ietf.org
Errors-To: manet-admin@ietf.org
X-BeenThere: manet@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/manet>,
	<mailto:manet-request@ietf.org?subject=unsubscribe>
List-Id: Mobile Ad-hoc Networks  <manet.ietf.org>
List-Post: <mailto:manet@ietf.org>
List-Help: <mailto:manet-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/manet>,
	<mailto:manet-request@ietf.org?subject=subscribe>


--------------020107000403090400040404
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit

Hi!

I think it's better if you search the mailing list of ns: 
http://www.isi.edu/nsnam/htdig/search.html for finding the answer to 
these questions. You could also mail the ns users: ns-users@isi.edu .

The AODV implementation in ns-2 (from ns-2.1b6 to ns-2.1b9; I don't know 
about earlier ns versions) can be run both with and without Hello 
messages. In aodv.h you can find:
/*
  Allows AODV to use link-layer (802.11) feedback in determining when
  links are up/down.
*/
#define AODV_LINK_LAYER_DETECTION

So you can choose between using link-layer feedback and Hello messages. 
For Hello messages you must comment the line  #define 
AODV_LINK_LAYER_DETECTION ; otherwise link-layer feedback is used.

Hope it helps
Ali Hamidian

Bernardo Antunes Maciel Villela wrote:

>On Tue, 19 Nov 2002, Moustafa Hasnaa wrote:
>
>Hello,
>
>Sorry, I didn't mention the version. The version I'm using is 
>ns 2.1b7. Then I'm probably using AODV with hello message ...
>I wonder anyway if they've built in ns distribution
>a version for AODV with hello message and without hello message.
>
>Thanks,
>Bernardo.
>
>>Hello,
>> I need to know you are talking about which Ns version, as i work with ns
>>version7
>> And it contains AODV simulated with hello message...;
>>
>>Regards.
>>Hasnaa Moustafa
>>----- Original Message -----
>>From: "Bernardo Antunes Maciel Villela" <bernardo@gta.ufrj.br>
>>To: <manet@ietf.org>
>>Sent: Monday, November 18, 2002 8:50 PM
>>Subject: [manet] Simulating AODV in NS
>>
>>
>>>Hi,
>>>
>>>I have this question: the AODV version implemented in NS today is the
>>>version made by Monarch and called AODV-LL in their paper "A
>>>Performance Comparison of Multi-hop Wireless Ad Hoc Network Routing
>>>Protocols" (by J. Broch, D. Maltz, D. Johnson, Y. Hu and J. Jetcheva)?
>>>
>>>I'd like to be sure about that because this AODV-LL version uses
>>>no hello AODV mechanism. Instead it utilizes link layer
>>>feedback from 802.11. BUT SUCH APPROACH CHANGES AODV PROTOCOL, because
>>> this way all link breakage is only on-demand and we only know about
>>>a broken link when we have a packet to send through this link.
>>>
>>>If anyone knows this answer, please let me know.
>>>Thanks.
>>>Bernardo.
>>>
>>>_______________________________________________
>>>manet mailing list
>>>manet@ietf.org
>>>https://www1.ietf.org/mailman/listinfo/manet
>>>
>>
>>--
>>This message has been scanned for viruses and
>>dangerous content by MailScanner, and is
>>believed to be clean.
>>
>
>
>--
>This message has been scanned for viruses and
>dangerous content by MailScanner, and is
>believed to be clean.
>
>_______________________________________________
>manet mailing list
>manet@ietf.org
>https://www1.ietf.org/mailman/listinfo/manet
>


--------------020107000403090400040404
Content-Type: text/html; charset=us-ascii
Content-Transfer-Encoding: 7bit

<html>
<head>
</head>
<body>
Hi!<br>
<br>
I think it's better if you search the mailing list of ns: <a href="http://www.isi.edu/nsnam/htdig/search.html">
http://www.isi.edu/nsnam/htdig/search.html</a>
 for finding the answer to these questions. You could also mail the ns users:
<a href="ns-users@isi.edu">ns-users@isi.edu</a>
.<br>
<br>
The AODV implementation in ns-2 (from ns-2.1b6 to ns-2.1b9; I don't know
about earlier ns versions) can be run both with and without Hello messages.
In aodv.h you can find:<br>
<font color="#3333ff">/*<br>
&nbsp; Allows AODV to use link-layer (802.11) feedback in determining when<br>
&nbsp; links are up/down.<br>
*/<br>
#define AODV_LINK_LAYER_DETECTION</font><br>
<br>
So you can choose between using link-layer feedback and Hello messages. For
Hello messages you must comment the line&nbsp; <font color="#3333ff">#define AODV_LINK_LAYER_DETECTION</font>
; otherwise link-layer feedback is used. <br>
<br>
Hope it helps<br>
Ali Hamidian<br>
<br>
Bernardo Antunes Maciel Villela wrote:<br>
<blockquote type="cite" cite="mid:Pine.LNX.4.44.0211190837210.25553-100000@tijuca.gta.ufrj.br">
  <pre wrap="">On Tue, 19 Nov 2002, Moustafa Hasnaa wrote:<br><br>Hello,<br><br>Sorry, I didn't mention the version. The version I'm using is <br>ns 2.1b7. Then I'm probably using AODV with hello message ...<br>I wonder anyway if they've built in ns distribution<br>a version for AODV with hello message and without hello message.<br><br>Thanks,<br>Bernardo.<br><br></pre>
  <blockquote type="cite">
    <pre wrap="">Hello,<br> I need to know you are talking about which Ns version, as i work with ns<br>version7<br> And it contains AODV simulated with hello message...;<br><br>Regards.<br>Hasnaa Moustafa<br>----- Original Message -----<br>From: "Bernardo Antunes Maciel Villela" <a class="moz-txt-link-rfc2396E" href="mailto:bernardo@gta.ufrj.br">&lt;bernardo@gta.ufrj.br&gt;</a><br>To: <a class="moz-txt-link-rfc2396E" href="mailto:manet@ietf.org">&lt;manet@ietf.org&gt;</a><br>Sent: Monday, November 18, 2002 8:50 PM<br>Subject: [manet] Simulating AODV in NS<br><br><br></pre>
    <blockquote type="cite">
      <pre wrap="">Hi,<br><br>I have this question: the AODV version implemented in NS today is the<br>version made by Monarch and called AODV-LL in their paper "A<br>Performance Comparison of Multi-hop Wireless Ad Hoc Network Routing<br>Protocols" (by J. Broch, D. Maltz, D. Johnson, Y. Hu and J. Jetcheva)?<br><br>I'd like to be sure about that because this AODV-LL version uses<br>no hello AODV mechanism. Instead it utilizes link layer<br>feedback from 802.11. BUT SUCH APPROACH CHANGES AODV PROTOCOL, because<br> this way all link breakage is only on-demand and we only know about<br>a broken link when we have a packet to send through this link.<br><br>If anyone knows this answer, please let me know.<br>Thanks.<br>Bernardo.<br><br>_______________________________________________<br>manet mailing list<br><a class="moz-txt-link-abbreviated" href="mailto:manet@ietf.org">manet@ietf.org</a><br><a class="moz-txt-link-freetext" href="https://www1.ietf.org/mailman/listinfo/manet">https:
//www1.ietf.org/mailman/listinfo/manet</a><br><br></pre>
      </blockquote>
      <pre wrap=""><br>--<br>This message has been scanned for viruses and<br>dangerous content by MailScanner, and is<br>believed to be clean.<br><br></pre>
      </blockquote>
      <pre wrap=""><!----><br><br>--<br>This message has been scanned for viruses and<br>dangerous content by MailScanner, and is<br>believed to be clean.<br><br>_______________________________________________<br>manet mailing list<br><a class="moz-txt-link-abbreviated" href="mailto:manet@ietf.org">manet@ietf.org</a><br><a class="moz-txt-link-freetext" href="https://www1.ietf.org/mailman/listinfo/manet">https://www1.ietf.org/mailman/listinfo/manet</a><br><br></pre>
      </blockquote>
      <br>
      </body>
      </html>

--------------020107000403090400040404--

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


From mailnull@www1.ietf.org  Tue Nov 19 10:21:18 2002
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA07228
	for <manet-archive@odin.ietf.org>; Tue, 19 Nov 2002 10:21:17 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id gAJFNSi24299
	for manet-archive@odin.ietf.org; Tue, 19 Nov 2002 10:23:28 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gAJFNSv24296
	for <manet-web-archive@optimus.ietf.org>; Tue, 19 Nov 2002 10:23:28 -0500
Received: from www1.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA07224
	for <manet-web-archive@ietf.org>; Tue, 19 Nov 2002 10:20:45 -0500 (EST)
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gAJF9Cv23697;
	Tue, 19 Nov 2002 10:09:12 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gAJ0fmv31553
	for <manet@optimus.ietf.org>; Mon, 18 Nov 2002 19:41:48 -0500
Received: from gandalf.icr.a-star.edu.sg (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA09015
	for <manet@ietf.org>; Mon, 18 Nov 2002 19:39:01 -0500 (EST)
Received: from gwserver.icr.a-star.edu.sg (gwserver.icr.a-star.edu.sg [137.132.31.253])
	by gandalf.icr.a-star.edu.sg (8.12.2+Sun/8.12.2) with ESMTP id gAJ0ghXw004430
	for <manet@ietf.org>; Tue, 19 Nov 2002 08:42:43 +0800 (SGT)
Received: from yoyo
	([204.42.66.233])
	by gwserver.icr.a-star.edu.sg; Tue, 19 Nov 2002 08:35:23 +0800
Message-ID: <022801c28f64$562df830$e9422acc@yoyo>
From: "Paul Tan" <tanpaul@icr.a-star.edu.sg>
To: <manet@ietf.org>
References: <45EA1063C2F8D211915800204808343B02F8B8C7@exchange1.lancs.ac.uk>
Date: Mon, 18 Nov 2002 19:40:55 -0500
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 6.00.2600.0000
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2600.0000
Content-Transfer-Encoding: 7bit
Subject: [manet] Questions on 802.11b on MANETs
Sender: manet-admin@ietf.org
Errors-To: manet-admin@ietf.org
X-BeenThere: manet@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/manet>,
	<mailto:manet-request@ietf.org?subject=unsubscribe>
List-Id: Mobile Ad-hoc Networks  <manet.ietf.org>
List-Post: <mailto:manet@ietf.org>
List-Help: <mailto:manet-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/manet>,
	<mailto:manet-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit

Hi all,

Currently, are there any API support for 802.11 wireless interface device
driver (Linux) which allows me to register the assoc/de-assoc events? How
(currently) can MANET protocols (if any) interacts with these events.

Cheers,
Paul


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



From manet-admin@ietf.org  Tue Nov 19 10:21:46 2002
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA07256
	for <manet-archive@lists.ietf.org>; Tue, 19 Nov 2002 10:21:45 -0500 (EST)
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gAJF9Cv23697;
	Tue, 19 Nov 2002 10:09:12 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gAJ0fmv31553
	for <manet@optimus.ietf.org>; Mon, 18 Nov 2002 19:41:48 -0500
Received: from gandalf.icr.a-star.edu.sg (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA09015
	for <manet@ietf.org>; Mon, 18 Nov 2002 19:39:01 -0500 (EST)
Received: from gwserver.icr.a-star.edu.sg (gwserver.icr.a-star.edu.sg [137.132.31.253])
	by gandalf.icr.a-star.edu.sg (8.12.2+Sun/8.12.2) with ESMTP id gAJ0ghXw004430
	for <manet@ietf.org>; Tue, 19 Nov 2002 08:42:43 +0800 (SGT)
Received: from yoyo
	([204.42.66.233])
	by gwserver.icr.a-star.edu.sg; Tue, 19 Nov 2002 08:35:23 +0800
Message-ID: <022801c28f64$562df830$e9422acc@yoyo>
From: "Paul Tan" <tanpaul@icr.a-star.edu.sg>
To: <manet@ietf.org>
References: <45EA1063C2F8D211915800204808343B02F8B8C7@exchange1.lancs.ac.uk>
Date: Mon, 18 Nov 2002 19:40:55 -0500
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 6.00.2600.0000
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2600.0000
Content-Transfer-Encoding: 7bit
Subject: [manet] Questions on 802.11b on MANETs
Sender: manet-admin@ietf.org
Errors-To: manet-admin@ietf.org
X-BeenThere: manet@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/manet>,
	<mailto:manet-request@ietf.org?subject=unsubscribe>
List-Id: Mobile Ad-hoc Networks  <manet.ietf.org>
List-Post: <mailto:manet@ietf.org>
List-Help: <mailto:manet-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/manet>,
	<mailto:manet-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 7bit

Hi all,

Currently, are there any API support for 802.11 wireless interface device
driver (Linux) which allows me to register the assoc/de-assoc events? How
(currently) can MANET protocols (if any) interacts with these events.

Cheers,
Paul


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


From manet-admin@ietf.org  Wed Nov 20 04:03:32 2002
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id EAA15037
	for <manet-archive@lists.ietf.org>; Wed, 20 Nov 2002 04:03:32 -0500 (EST)
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gAK8rxv30230;
	Wed, 20 Nov 2002 03:53:59 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gAK8m8v29978
	for <manet@optimus.ietf.org>; Wed, 20 Nov 2002 03:48:08 -0500
Received: from mailgw1.atr.co.jp (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id DAA14681
	for <manet@ietf.org>; Wed, 20 Nov 2002 03:45:13 -0500 (EST)
Received: from vcms.atr.co.jp (epsilon.atr.co.jp [133.186.254.10])
	by mailgw1.atr.co.jp (Postfix) with ESMTP id B83BD18B01
	for <manet@ietf.org>; Wed, 20 Nov 2002 17:47:50 +0900 (JST)
Received: from acr.acr.atr.co.jp (localhost [127.0.0.1])
	by vcms.atr.co.jp (Postfix) with ESMTP id 0FFB1397CD
	for <manet@ietf.org>; Wed, 20 Nov 2002 17:47:50 +0900 (JST)
Received: from rpc41 by acr.acr.atr.co.jp (8.9.3/3.7W)
	id RAA10481; Wed, 20 Nov 2002 17:47:58 +0900 (JST)
From: "Shingo HORISAWA" <horisawa@atr.co.jp>
To: "MANET Mailing List" <manet@ietf.org>
Date: Wed, 20 Nov 2002 17:47:42 +0900
Message-ID: <HEEGKKKPEHOBJFHFEPAPGEHHCNAA.horisawa@atr.co.jp>
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-2022-jp"
Content-Transfer-Encoding: 7bit
X-Priority: 3 (Normal)
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook IMO, Build 9.0.2416 (9.0.2911.0)
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1106
Importance: Normal
Content-Transfer-Encoding: 7bit
Subject: [manet] GSR/FSR implementation on Linux
Sender: manet-admin@ietf.org
Errors-To: manet-admin@ietf.org
X-BeenThere: manet@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/manet>,
	<mailto:manet-request@ietf.org?subject=unsubscribe>
List-Id: Mobile Ad-hoc Networks  <manet.ietf.org>
List-Post: <mailto:manet@ietf.org>
List-Help: <mailto:manet-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/manet>,
	<mailto:manet-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 7bit

Hi all.

I developed GSR/FSR implementations which run on Linux.

These implementations are based on FSR Internet-Draft version 2,
but are different from the Draft in the following points:

- "destination sequence number" field length (draft: 24 bits, our
implementations: 16 bits)
- "N_neighbors" field length (draft: 8 bits, our implementations: 16 bits)
- We use the normal Dijkstra instead of the modified-Dijkstra when
calculating routes
- and some other details...

You can download and use them from the following page:

GSR/FSR implementation on Linux
http://www.acr.atr.co.jp/~horisawa/download/gsrfsr.html

If you find any problems, please point them out.

Thanks !

**********************************************************
   Shingo Horisawa

     Researcher
     Department 1

     ATR Adaptive Communications Research Laboratories

     2-2-2 Hikaridai, Seika-cho, Soraku-gun, Kyoto 619-0288, Japan
     TEL +81-774-95-2720   FAX +81-774-95-1509
     E-MAIL  horisawa@atr.co.jp
     URL : http://www.acr.atr.co.jp/acr/
**********************************************************
_______________________________________________
manet mailing list
manet@ietf.org
https://www1.ietf.org/mailman/listinfo/manet


From mailnull@www1.ietf.org  Wed Nov 20 04:24:51 2002
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id EAA15311
	for <manet-archive@odin.ietf.org>; Wed, 20 Nov 2002 04:24:51 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id gAK9RAk32484
	for manet-archive@odin.ietf.org; Wed, 20 Nov 2002 04:27:10 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gAK9RAv32481
	for <manet-web-archive@optimus.ietf.org>; Wed, 20 Nov 2002 04:27:10 -0500
Received: from www1.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id EAA15306
	for <manet-web-archive@ietf.org>; Wed, 20 Nov 2002 04:24:20 -0500 (EST)
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gAK8rxv30230;
	Wed, 20 Nov 2002 03:53:59 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gAK8m8v29978
	for <manet@optimus.ietf.org>; Wed, 20 Nov 2002 03:48:08 -0500
Received: from mailgw1.atr.co.jp (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id DAA14681
	for <manet@ietf.org>; Wed, 20 Nov 2002 03:45:13 -0500 (EST)
Received: from vcms.atr.co.jp (epsilon.atr.co.jp [133.186.254.10])
	by mailgw1.atr.co.jp (Postfix) with ESMTP id B83BD18B01
	for <manet@ietf.org>; Wed, 20 Nov 2002 17:47:50 +0900 (JST)
Received: from acr.acr.atr.co.jp (localhost [127.0.0.1])
	by vcms.atr.co.jp (Postfix) with ESMTP id 0FFB1397CD
	for <manet@ietf.org>; Wed, 20 Nov 2002 17:47:50 +0900 (JST)
Received: from rpc41 by acr.acr.atr.co.jp (8.9.3/3.7W)
	id RAA10481; Wed, 20 Nov 2002 17:47:58 +0900 (JST)
From: "Shingo HORISAWA" <horisawa@atr.co.jp>
To: "MANET Mailing List" <manet@ietf.org>
Date: Wed, 20 Nov 2002 17:47:42 +0900
Message-ID: <HEEGKKKPEHOBJFHFEPAPGEHHCNAA.horisawa@atr.co.jp>
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-2022-jp"
Content-Transfer-Encoding: 7bit
X-Priority: 3 (Normal)
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook IMO, Build 9.0.2416 (9.0.2911.0)
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1106
Importance: Normal
Content-Transfer-Encoding: 7bit
Subject: [manet] GSR/FSR implementation on Linux
Sender: manet-admin@ietf.org
Errors-To: manet-admin@ietf.org
X-BeenThere: manet@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/manet>,
	<mailto:manet-request@ietf.org?subject=unsubscribe>
List-Id: Mobile Ad-hoc Networks  <manet.ietf.org>
List-Post: <mailto:manet@ietf.org>
List-Help: <mailto:manet-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/manet>,
	<mailto:manet-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit

Hi all.

I developed GSR/FSR implementations which run on Linux.

These implementations are based on FSR Internet-Draft version 2,
but are different from the Draft in the following points:

- "destination sequence number" field length (draft: 24 bits, our
implementations: 16 bits)
- "N_neighbors" field length (draft: 8 bits, our implementations: 16 bits)
- We use the normal Dijkstra instead of the modified-Dijkstra when
calculating routes
- and some other details...

You can download and use them from the following page:

GSR/FSR implementation on Linux
http://www.acr.atr.co.jp/~horisawa/download/gsrfsr.html

If you find any problems, please point them out.

Thanks !

**********************************************************
   Shingo Horisawa

     Researcher
     Department 1

     ATR Adaptive Communications Research Laboratories

     2-2-2 Hikaridai, Seika-cho, Soraku-gun, Kyoto 619-0288, Japan
     TEL +81-774-95-2720   FAX +81-774-95-1509
     E-MAIL  horisawa@atr.co.jp
     URL : http://www.acr.atr.co.jp/acr/
**********************************************************
_______________________________________________
manet mailing list
manet@ietf.org
https://www1.ietf.org/mailman/listinfo/manet



From manet-admin@ietf.org  Wed Nov 20 07:13:12 2002
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id HAA17223
	for <manet-archive@lists.ietf.org>; Wed, 20 Nov 2002 07:13:12 -0500 (EST)
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gAKBoBv07718;
	Wed, 20 Nov 2002 06:50:11 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gAKBh2v07496
	for <manet@optimus.ietf.org>; Wed, 20 Nov 2002 06:43:02 -0500
Received: from mail-relay-1.warwick.ac.uk (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id GAA16701
	for <manet@ietf.org>; Wed, 20 Nov 2002 06:40:17 -0500 (EST)
Received: from mail.csv.warwick.ac.uk (host-97-8-205-137 [137.205.8.97])
	by mail-relay-1.csv.warwick.ac.uk (8.12.5/8.12.5) with ESMTP id gAKBgtRf028369
	for <manet@ietf.org>; Wed, 20 Nov 2002 11:42:56 GMT
Received: from pces247 (pces247 [137.205.144.247])
	by mail.csv.warwick.ac.uk (8.12.5/8.12.5) with SMTP id gAKBgsWT016389
	for <manet@ietf.org>; Wed, 20 Nov 2002 11:42:54 GMT
Message-ID: <019b01c2908a$57edbd00$f790cd89@warwick.ac.uk>
From: "Lei Xue" <l.xue@warwick.ac.uk>
To: <manet@ietf.org>
Date: Wed, 20 Nov 2002 11:45:37 -0000
MIME-Version: 1.0
Content-Type: multipart/alternative;
	boundary="----=_NextPart_000_0198_01C2908A.57C77050"
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 5.50.4522.1200
X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4522.1200
X-Virus-Scanned: by amavisd-milter (http://amavis.org/)
Subject: [manet] Ad Hoc mode in 802.11
Sender: manet-admin@ietf.org
Errors-To: manet-admin@ietf.org
X-BeenThere: manet@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/manet>,
	<mailto:manet-request@ietf.org?subject=unsubscribe>
List-Id: Mobile Ad-hoc Networks  <manet.ietf.org>
List-Post: <mailto:manet@ietf.org>
List-Help: <mailto:manet-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/manet>,
	<mailto:manet-request@ietf.org?subject=subscribe>

This is a multi-part message in MIME format.

------=_NextPart_000_0198_01C2908A.57C77050
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

Dear friends,

In Ad Hoc mode of 802.11, any node that is within range of any other can =
communicate if they agree some basic rules. I wonder in this mode, if =
the node can be routed by the neighbor nodes to the one out of its =
range, like the pure Ad Hoc network does? Please kindly give your =
advice. Thanks.

Best Regards,

Lei

------=_NextPart_000_0198_01C2908A.57C77050
Content-Type: text/html;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META content=3D"text/html; charset=3Diso-8859-1" =
http-equiv=3DContent-Type>
<META content=3D"MSHTML 5.00.3314.2100" name=3DGENERATOR>
<STYLE></STYLE>
</HEAD>
<BODY bgColor=3D#ffffff>
<DIV><FONT face=3DArial size=3D2>Dear friends,</FONT></DIV>
<DIV>&nbsp;</DIV>
<DIV><FONT face=3DArial size=3D2>In Ad Hoc mode of 802.11, any node that =
is within=20
range of any other can communicate if they agree some basic rules. I =
wonder in=20
this mode, if the node can be routed by the neighbor nodes to the one =
out of its=20
range, like the pure Ad Hoc network does? Please kindly give your =
advice.=20
Thanks.</FONT></DIV>
<DIV>&nbsp;</DIV>
<DIV><FONT face=3DArial size=3D2>Best Regards,</FONT></DIV>
<DIV><FONT face=3DArial size=3D2><BR>Lei</FONT></DIV></BODY></HTML>

------=_NextPart_000_0198_01C2908A.57C77050--

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


From mailnull@www1.ietf.org  Wed Nov 20 07:23:33 2002
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id HAA17346
	for <manet-archive@odin.ietf.org>; Wed, 20 Nov 2002 07:23:33 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id gAKCPi209418
	for manet-archive@odin.ietf.org; Wed, 20 Nov 2002 07:25:44 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gAKCPiv09415
	for <manet-web-archive@optimus.ietf.org>; Wed, 20 Nov 2002 07:25:44 -0500
Received: from www1.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id HAA17340
	for <manet-web-archive@ietf.org>; Wed, 20 Nov 2002 07:23:02 -0500 (EST)
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gAKBoBv07718;
	Wed, 20 Nov 2002 06:50:11 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gAKBh2v07496
	for <manet@optimus.ietf.org>; Wed, 20 Nov 2002 06:43:02 -0500
Received: from mail-relay-1.warwick.ac.uk (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id GAA16701
	for <manet@ietf.org>; Wed, 20 Nov 2002 06:40:17 -0500 (EST)
Received: from mail.csv.warwick.ac.uk (host-97-8-205-137 [137.205.8.97])
	by mail-relay-1.csv.warwick.ac.uk (8.12.5/8.12.5) with ESMTP id gAKBgtRf028369
	for <manet@ietf.org>; Wed, 20 Nov 2002 11:42:56 GMT
Received: from pces247 (pces247 [137.205.144.247])
	by mail.csv.warwick.ac.uk (8.12.5/8.12.5) with SMTP id gAKBgsWT016389
	for <manet@ietf.org>; Wed, 20 Nov 2002 11:42:54 GMT
Message-ID: <019b01c2908a$57edbd00$f790cd89@warwick.ac.uk>
From: "Lei Xue" <l.xue@warwick.ac.uk>
To: <manet@ietf.org>
Date: Wed, 20 Nov 2002 11:45:37 -0000
MIME-Version: 1.0
Content-Type: multipart/alternative;
	boundary="----=_NextPart_000_0198_01C2908A.57C77050"
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 5.50.4522.1200
X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4522.1200
X-Virus-Scanned: by amavisd-milter (http://amavis.org/)
Subject: [manet] Ad Hoc mode in 802.11
Sender: manet-admin@ietf.org
Errors-To: manet-admin@ietf.org
X-BeenThere: manet@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/manet>,
	<mailto:manet-request@ietf.org?subject=unsubscribe>
List-Id: Mobile Ad-hoc Networks  <manet.ietf.org>
List-Post: <mailto:manet@ietf.org>
List-Help: <mailto:manet-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/manet>,
	<mailto:manet-request@ietf.org?subject=subscribe>

This is a multi-part message in MIME format.

------=_NextPart_000_0198_01C2908A.57C77050
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

Dear friends,

In Ad Hoc mode of 802.11, any node that is within range of any other can =
communicate if they agree some basic rules. I wonder in this mode, if =
the node can be routed by the neighbor nodes to the one out of its =
range, like the pure Ad Hoc network does? Please kindly give your =
advice. Thanks.

Best Regards,

Lei

------=_NextPart_000_0198_01C2908A.57C77050
Content-Type: text/html;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META content=3D"text/html; charset=3Diso-8859-1" =
http-equiv=3DContent-Type>
<META content=3D"MSHTML 5.00.3314.2100" name=3DGENERATOR>
<STYLE></STYLE>
</HEAD>
<BODY bgColor=3D#ffffff>
<DIV><FONT face=3DArial size=3D2>Dear friends,</FONT></DIV>
<DIV>&nbsp;</DIV>
<DIV><FONT face=3DArial size=3D2>In Ad Hoc mode of 802.11, any node that =
is within=20
range of any other can communicate if they agree some basic rules. I =
wonder in=20
this mode, if the node can be routed by the neighbor nodes to the one =
out of its=20
range, like the pure Ad Hoc network does? Please kindly give your =
advice.=20
Thanks.</FONT></DIV>
<DIV>&nbsp;</DIV>
<DIV><FONT face=3DArial size=3D2>Best Regards,</FONT></DIV>
<DIV><FONT face=3DArial size=3D2><BR>Lei</FONT></DIV></BODY></HTML>

------=_NextPart_000_0198_01C2908A.57C77050--

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



From manet-admin@ietf.org  Wed Nov 20 08:16:00 2002
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA18301
	for <manet-archive@lists.ietf.org>; Wed, 20 Nov 2002 08:15:59 -0500 (EST)
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gAKClpv10733;
	Wed, 20 Nov 2002 07:47:51 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gAKCgav10572
	for <manet@optimus.ietf.org>; Wed, 20 Nov 2002 07:42:36 -0500
Received: from mail.agderweb.no (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id HAA17569
	for <manet@ietf.org>; Wed, 20 Nov 2002 07:39:53 -0500 (EST)
Received: from beritpc82 [212.4.33.133] by mail.agderweb.no with ESMTP
  (SMTPD32-7.13) id A20F95C0132; Wed, 20 Nov 2002 13:37:35 +0100
Reply-To: <geir.gyland@bigfoot.com>
From: "Geir Gyland" <geir.gyland@applica.no>
To: <manet@ietf.org>
Date: Wed, 20 Nov 2002 13:41:41 +0100
Message-ID: <002601c29092$2e0500e0$1f2304d4@beritpc82>
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: 7bit
X-Priority: 3 (Normal)
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook, Build 10.0.2627
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2600.0000
Content-Transfer-Encoding: 7bit
Subject: [manet] Test: change in rute for an OLSR net
Sender: manet-admin@ietf.org
Errors-To: manet-admin@ietf.org
X-BeenThere: manet@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/manet>,
	<mailto:manet-request@ietf.org?subject=unsubscribe>
List-Id: Mobile Ad-hoc Networks  <manet.ietf.org>
List-Post: <mailto:manet@ietf.org>
List-Help: <mailto:manet-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/manet>,
	<mailto:manet-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 7bit

Hi all!


We did some simple static test of route change using 4 nodes set up like
this:

      .  3   .
   .             .
1                   4
   .             .
      .  2   .

Node 1 and 4 are out of reach for each other (2 hops)

We generated CBR traffic with a speed of 11Mb/s (UDP) traffic and sent
it through the network. Initially the route was 1 - 3 - 4 then we
stopped the interface on node 3 and observed when the traffic started
passing over the route 1 - 2 - 4

I would have believed the route change to take 4 - 6 seconds (Neighbor
hold time + TC) but we observed twice as much time (between 12 and 15
sec) before the traffic was traveling over node 2.

Does anyone have an explanation to justify the time? 
 
At the moment we do not trust our results!

Additional information:
 
All nodes are laptops, running Red Hat 7.3 using the NLR (nolsrd)
modified version of the INRIA olsrd code version 1.0a9. 

OLSR parameters were set to the default values of the NRL version 
HELLO interval 0.5
HELLO multiplier 8
TC intereval 3
TC multiplier 5

-----------------------------
Geir Gyland
E-mail: geir.gyland@bigfoot.com



---
[This E-mail was scanned for viruses by Declude Virus]

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


From mailnull@www1.ietf.org  Wed Nov 20 08:34:03 2002
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA18755
	for <manet-archive@odin.ietf.org>; Wed, 20 Nov 2002 08:34:03 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id gAKDaCM13066
	for manet-archive@odin.ietf.org; Wed, 20 Nov 2002 08:36:12 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gAKDaCv13063
	for <manet-web-archive@optimus.ietf.org>; Wed, 20 Nov 2002 08:36:12 -0500
Received: from www1.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA18733
	for <manet-web-archive@ietf.org>; Wed, 20 Nov 2002 08:33:27 -0500 (EST)
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gAKClpv10733;
	Wed, 20 Nov 2002 07:47:51 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gAKCgav10572
	for <manet@optimus.ietf.org>; Wed, 20 Nov 2002 07:42:36 -0500
Received: from mail.agderweb.no (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id HAA17569
	for <manet@ietf.org>; Wed, 20 Nov 2002 07:39:53 -0500 (EST)
Received: from beritpc82 [212.4.33.133] by mail.agderweb.no with ESMTP
  (SMTPD32-7.13) id A20F95C0132; Wed, 20 Nov 2002 13:37:35 +0100
Reply-To: <geir.gyland@bigfoot.com>
From: "Geir Gyland" <geir.gyland@applica.no>
To: <manet@ietf.org>
Date: Wed, 20 Nov 2002 13:41:41 +0100
Message-ID: <002601c29092$2e0500e0$1f2304d4@beritpc82>
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: 7bit
X-Priority: 3 (Normal)
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook, Build 10.0.2627
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2600.0000
Content-Transfer-Encoding: 7bit
Subject: [manet] Test: change in rute for an OLSR net
Sender: manet-admin@ietf.org
Errors-To: manet-admin@ietf.org
X-BeenThere: manet@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/manet>,
	<mailto:manet-request@ietf.org?subject=unsubscribe>
List-Id: Mobile Ad-hoc Networks  <manet.ietf.org>
List-Post: <mailto:manet@ietf.org>
List-Help: <mailto:manet-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/manet>,
	<mailto:manet-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit

Hi all!


We did some simple static test of route change using 4 nodes set up like
this:

      .  3   .
   .             .
1                   4
   .             .
      .  2   .

Node 1 and 4 are out of reach for each other (2 hops)

We generated CBR traffic with a speed of 11Mb/s (UDP) traffic and sent
it through the network. Initially the route was 1 - 3 - 4 then we
stopped the interface on node 3 and observed when the traffic started
passing over the route 1 - 2 - 4

I would have believed the route change to take 4 - 6 seconds (Neighbor
hold time + TC) but we observed twice as much time (between 12 and 15
sec) before the traffic was traveling over node 2.

Does anyone have an explanation to justify the time? 
 
At the moment we do not trust our results!

Additional information:
 
All nodes are laptops, running Red Hat 7.3 using the NLR (nolsrd)
modified version of the INRIA olsrd code version 1.0a9. 

OLSR parameters were set to the default values of the NRL version 
HELLO interval 0.5
HELLO multiplier 8
TC intereval 3
TC multiplier 5

-----------------------------
Geir Gyland
E-mail: geir.gyland@bigfoot.com



---
[This E-mail was scanned for viruses by Declude Virus]

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



From manet-admin@ietf.org  Wed Nov 20 10:41:07 2002
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA22355
	for <manet-archive@lists.ietf.org>; Wed, 20 Nov 2002 10:41:07 -0500 (EST)
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gAKEL6v16421;
	Wed, 20 Nov 2002 09:21:06 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gAKEDFv16105
	for <manet@optimus.ietf.org>; Wed, 20 Nov 2002 09:13:15 -0500
Received: from sm205.163.com (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA19384
	for <manet@ietf.org>; Wed, 20 Nov 2002 09:09:53 -0500 (EST)
Received: from localhost (localhost [127.0.0.1])
	by sm205.163.com (Postfix) with SMTP id 4B5271C67D0C4
	for <manet@ietf.org>; Wed, 20 Nov 2002 22:11:22 +0800 (CST)
Received: from RavProxy (unknown [61.187.64.26])
	by 192.168.1.205 (Coremail) with SMTP id lAoBAAiY2z1uBEAa.1
	for <manet@ietf.org>; Wed, 20 Nov 2002 22:11:22 +0800 (CST)
Message-ID: <000001c2909e$370b11a0$7600a8c0@zyn>
From: "Zhang Yanan" <csu_zyn@163.com>
To: <manet@ietf.org>
Date: Wed, 20 Nov 2002 19:19:30 +0800
MIME-Version: 1.0
Content-Type: multipart/alternative;
	boundary="----=_NextPart_000_0009_01C290C9.C032DBE0"
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 6.00.2600.0000
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2600.0000
Subject: [manet] who can help me about power-range in glomo?
Sender: manet-admin@ietf.org
Errors-To: manet-admin@ietf.org
X-BeenThere: manet@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/manet>,
	<mailto:manet-request@ietf.org?subject=unsubscribe>
List-Id: Mobile Ad-hoc Networks  <manet.ietf.org>
List-Post: <mailto:manet@ietf.org>
List-Help: <mailto:manet-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/manet>,
	<mailto:manet-request@ietf.org?subject=subscribe>

This is a multi-part message in MIME format.

------=_NextPart_000_0009_01C290C9.C032DBE0
Content-Type: text/plain;
	charset="gb2312"
Content-Transfer-Encoding: base64

aGksDQpJIGNhbid0IGZpbmQgUE9XRVItUkFOR0UgaW4gY29uZmlnLmluIG9mIEdsb21vc2ltLiBG
cm9tIHRoZSBtYW51YWwgb2YgZ2xvbW8xLjAsIEkgY2FuIGZpbmQgdGhlIHBhcmFtZXRlciwgYnV0
IEkgY2FuJ3QgZmluZCBpbiB0aGUgVmVyc2lvbiAyLjAzLiANClRoYW5rcyBpbiBhZHZhbmNlLg0K

------=_NextPart_000_0009_01C290C9.C032DBE0
Content-Type: text/html;
	charset="gb2312"
Content-Transfer-Encoding: base64

PCFET0NUWVBFIEhUTUwgUFVCTElDICItLy9XM0MvL0RURCBIVE1MIDQuMCBUcmFuc2l0aW9uYWwv
L0VOIj4NCjxIVE1MPjxIRUFEPg0KPE1FVEEgaHR0cC1lcXVpdj1Db250ZW50LVR5cGUgY29udGVu
dD0idGV4dC9odG1sOyBjaGFyc2V0PWdiMjMxMiI+DQo8TUVUQSBjb250ZW50PSJNU0hUTUwgNi4w
MC4yNjAwLjAiIG5hbWU9R0VORVJBVE9SPg0KPFNUWUxFPjwvU1RZTEU+DQo8L0hFQUQ+DQo8Qk9E
WSBiZ0NvbG9yPSNmZmZmZmY+DQo8RElWPjxGT05UIHNpemU9Mj5oaSw8L0ZPTlQ+PC9ESVY+DQo8
RElWPjxGT05UIHNpemU9Mj5JIGNhbid0IGZpbmQgUE9XRVItUkFOR0UgaW4gY29uZmlnLmluIG9m
IEdsb21vc2ltLiBGcm9tIHRoZSANCm1hbnVhbCBvZiBnbG9tbzEuMCwgSSBjYW4gZmluZCB0aGUg
cGFyYW1ldGVyLCBidXQgSSBjYW4ndCBmaW5kIGluIHRoZSBWZXJzaW9uIA0KMi4wMy4gPC9GT05U
PjwvRElWPg0KPERJVj48Rk9OVCBzaXplPTI+VGhhbmtzIGluIGFkdmFuY2UuPC9GT05UPjwvRElW
PjwvQk9EWT48L0hUTUw+DQo=

------=_NextPart_000_0009_01C290C9.C032DBE0--

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


From manet-admin@ietf.org  Wed Nov 20 10:50:38 2002
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA22738
	for <manet-archive@lists.ietf.org>; Wed, 20 Nov 2002 10:50:38 -0500 (EST)
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gAKFSAv21510;
	Wed, 20 Nov 2002 10:28:10 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gAKFIpv21100
	for <manet@optimus.ietf.org>; Wed, 20 Nov 2002 10:18:51 -0500
Received: from luna.tlmat.unican.es (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA21418
	for <manet@ietf.org>; Wed, 20 Nov 2002 10:16:08 -0500 (EST)
Received: from mizar (mizar.tlmat.unican.es [193.144.186.38]) by luna.tlmat.unican.es with SMTP (8.7.6/8.7.1) id QAA11060; Wed, 20 Nov 2002 16:56:54 +0100 (MET)
Message-ID: <00a201c290a8$72a18a50$26ba90c1@mizar>
From: =?iso-8859-1?Q?Ram=F3n_Ag=FCero?= <ramon@tlmat.unican.es>
To: "Lei Xue" <l.xue@warwick.ac.uk>
Cc: <manet@ietf.org>
References: <019b01c2908a$57edbd00$f790cd89@warwick.ac.uk>
Subject: Re: [manet] Ad Hoc mode in 802.11
Date: Wed, 20 Nov 2002 16:21:05 +0100
MIME-Version: 1.0
Content-Type: multipart/alternative;
	boundary="----=_NextPart_000_009F_01C290B0.D3517510"
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 6.00.2600.0000
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2600.0000
Sender: manet-admin@ietf.org
Errors-To: manet-admin@ietf.org
X-BeenThere: manet@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/manet>,
	<mailto:manet-request@ietf.org?subject=unsubscribe>
List-Id: Mobile Ad-hoc Networks  <manet.ietf.org>
List-Post: <mailto:manet@ietf.org>
List-Help: <mailto:manet-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/manet>,
	<mailto:manet-request@ietf.org?subject=subscribe>

This is a multi-part message in MIME format.

------=_NextPart_000_009F_01C290B0.D3517510
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

Dear Lei,

it is possible, although it is not a built-in functionality. The packet =
can be routed at layer three, but that is independent from the IEEE =
802.11 wireless cards, it is more an Operating System functionality, =
which you have to activate and configure.

HTH

Ram=F3n
  ----- Original Message -----=20
  From: Lei Xue=20
  To: manet@ietf.org=20
  Sent: Wednesday, November 20, 2002 12:45 PM
  Subject: [manet] Ad Hoc mode in 802.11


  Dear friends,

  In Ad Hoc mode of 802.11, any node that is within range of any other =
can communicate if they agree some basic rules. I wonder in this mode, =
if the node can be routed by the neighbor nodes to the one out of its =
range, like the pure Ad Hoc network does? Please kindly give your =
advice. Thanks.

  Best Regards,

  Lei

------=_NextPart_000_009F_01C290B0.D3517510
Content-Type: text/html;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META http-equiv=3DContent-Type content=3D"text/html; =
charset=3Diso-8859-1">
<META content=3D"MSHTML 6.00.2600.0" name=3DGENERATOR>
<STYLE></STYLE>
</HEAD>
<BODY bgColor=3D#ffffff>
<DIV><FONT face=3DCourier size=3D2>Dear Lei,</FONT></DIV>
<DIV><FONT face=3DCourier size=3D2></FONT>&nbsp;</DIV>
<DIV><FONT face=3DCourier size=3D2>it is possible, although it is not a =
built-in=20
functionality. The packet can be routed at layer three, but that is =
independent=20
from the IEEE 802.11 wireless cards, it is more an Operating System=20
functionality, which you have to activate and configure.</FONT></DIV>
<DIV><FONT face=3DCourier size=3D2></FONT>&nbsp;</DIV>
<DIV><FONT face=3DCourier size=3D2>HTH</FONT></DIV>
<DIV><FONT face=3DCourier size=3D2></FONT>&nbsp;</DIV>
<DIV><FONT face=3DCourier size=3D2>Ram=F3n</FONT></DIV>
<BLOCKQUOTE dir=3Dltr=20
style=3D"PADDING-RIGHT: 0px; PADDING-LEFT: 5px; MARGIN-LEFT: 5px; =
BORDER-LEFT: #000000 2px solid; MARGIN-RIGHT: 0px">
  <DIV style=3D"FONT: 10pt arial">----- Original Message ----- </DIV>
  <DIV=20
  style=3D"BACKGROUND: #e4e4e4; FONT: 10pt arial; font-color: =
black"><B>From:</B>=20
  <A title=3Dl.xue@warwick.ac.uk href=3D"mailto:l.xue@warwick.ac.uk">Lei =
Xue</A>=20
  </DIV>
  <DIV style=3D"FONT: 10pt arial"><B>To:</B> <A title=3Dmanet@ietf.org=20
  href=3D"mailto:manet@ietf.org">manet@ietf.org</A> </DIV>
  <DIV style=3D"FONT: 10pt arial"><B>Sent:</B> Wednesday, November 20, =
2002 12:45=20
  PM</DIV>
  <DIV style=3D"FONT: 10pt arial"><B>Subject:</B> [manet] Ad Hoc mode in =

  802.11</DIV>
  <DIV><BR></DIV>
  <DIV><FONT face=3DArial size=3D2>Dear friends,</FONT></DIV>
  <DIV>&nbsp;</DIV>
  <DIV><FONT face=3DArial size=3D2>In Ad Hoc mode of 802.11, any node =
that is within=20
  range of any other can communicate if they agree some basic rules. I =
wonder in=20
  this mode, if the node can be routed by the neighbor nodes to the one =
out of=20
  its range, like the pure Ad Hoc network does? Please kindly give your =
advice.=20
  Thanks.</FONT></DIV>
  <DIV>&nbsp;</DIV>
  <DIV><FONT face=3DArial size=3D2>Best Regards,</FONT></DIV>
  <DIV><FONT face=3DArial =
size=3D2><BR>Lei</FONT></DIV></BLOCKQUOTE></BODY></HTML>

------=_NextPart_000_009F_01C290B0.D3517510--

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


From mailnull@www1.ietf.org  Wed Nov 20 10:57:41 2002
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA22950
	for <manet-archive@odin.ietf.org>; Wed, 20 Nov 2002 10:57:41 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id gAKFxrS24252
	for manet-archive@odin.ietf.org; Wed, 20 Nov 2002 10:59:53 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gAKFxrv24249
	for <manet-web-archive@optimus.ietf.org>; Wed, 20 Nov 2002 10:59:53 -0500
Received: from www1.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA22930
	for <manet-web-archive@ietf.org>; Wed, 20 Nov 2002 10:57:10 -0500 (EST)
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gAKEL6v16421;
	Wed, 20 Nov 2002 09:21:06 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gAKEDFv16105
	for <manet@optimus.ietf.org>; Wed, 20 Nov 2002 09:13:15 -0500
Received: from sm205.163.com (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA19384
	for <manet@ietf.org>; Wed, 20 Nov 2002 09:09:53 -0500 (EST)
Received: from localhost (localhost [127.0.0.1])
	by sm205.163.com (Postfix) with SMTP id 4B5271C67D0C4
	for <manet@ietf.org>; Wed, 20 Nov 2002 22:11:22 +0800 (CST)
Received: from RavProxy (unknown [61.187.64.26])
	by 192.168.1.205 (Coremail) with SMTP id lAoBAAiY2z1uBEAa.1
	for <manet@ietf.org>; Wed, 20 Nov 2002 22:11:22 +0800 (CST)
Message-ID: <000001c2909e$370b11a0$7600a8c0@zyn>
From: "Zhang Yanan" <csu_zyn@163.com>
To: <manet@ietf.org>
Date: Wed, 20 Nov 2002 19:19:30 +0800
MIME-Version: 1.0
Content-Type: multipart/alternative;
	boundary="----=_NextPart_000_0009_01C290C9.C032DBE0"
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 6.00.2600.0000
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2600.0000
Subject: [manet] who can help me about power-range in glomo?
Sender: manet-admin@ietf.org
Errors-To: manet-admin@ietf.org
X-BeenThere: manet@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/manet>,
	<mailto:manet-request@ietf.org?subject=unsubscribe>
List-Id: Mobile Ad-hoc Networks  <manet.ietf.org>
List-Post: <mailto:manet@ietf.org>
List-Help: <mailto:manet-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/manet>,
	<mailto:manet-request@ietf.org?subject=subscribe>

This is a multi-part message in MIME format.

------=_NextPart_000_0009_01C290C9.C032DBE0
Content-Type: text/plain;
	charset="gb2312"
Content-Transfer-Encoding: base64

aGksDQpJIGNhbid0IGZpbmQgUE9XRVItUkFOR0UgaW4gY29uZmlnLmluIG9mIEdsb21vc2ltLiBG
cm9tIHRoZSBtYW51YWwgb2YgZ2xvbW8xLjAsIEkgY2FuIGZpbmQgdGhlIHBhcmFtZXRlciwgYnV0
IEkgY2FuJ3QgZmluZCBpbiB0aGUgVmVyc2lvbiAyLjAzLiANClRoYW5rcyBpbiBhZHZhbmNlLg0K

------=_NextPart_000_0009_01C290C9.C032DBE0
Content-Type: text/html;
	charset="gb2312"
Content-Transfer-Encoding: base64

PCFET0NUWVBFIEhUTUwgUFVCTElDICItLy9XM0MvL0RURCBIVE1MIDQuMCBUcmFuc2l0aW9uYWwv
L0VOIj4NCjxIVE1MPjxIRUFEPg0KPE1FVEEgaHR0cC1lcXVpdj1Db250ZW50LVR5cGUgY29udGVu
dD0idGV4dC9odG1sOyBjaGFyc2V0PWdiMjMxMiI+DQo8TUVUQSBjb250ZW50PSJNU0hUTUwgNi4w
MC4yNjAwLjAiIG5hbWU9R0VORVJBVE9SPg0KPFNUWUxFPjwvU1RZTEU+DQo8L0hFQUQ+DQo8Qk9E
WSBiZ0NvbG9yPSNmZmZmZmY+DQo8RElWPjxGT05UIHNpemU9Mj5oaSw8L0ZPTlQ+PC9ESVY+DQo8
RElWPjxGT05UIHNpemU9Mj5JIGNhbid0IGZpbmQgUE9XRVItUkFOR0UgaW4gY29uZmlnLmluIG9m
IEdsb21vc2ltLiBGcm9tIHRoZSANCm1hbnVhbCBvZiBnbG9tbzEuMCwgSSBjYW4gZmluZCB0aGUg
cGFyYW1ldGVyLCBidXQgSSBjYW4ndCBmaW5kIGluIHRoZSBWZXJzaW9uIA0KMi4wMy4gPC9GT05U
PjwvRElWPg0KPERJVj48Rk9OVCBzaXplPTI+VGhhbmtzIGluIGFkdmFuY2UuPC9GT05UPjwvRElW
PjwvQk9EWT48L0hUTUw+DQo=

------=_NextPart_000_0009_01C290C9.C032DBE0--

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



From mailnull@www1.ietf.org  Wed Nov 20 11:02:07 2002
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA23106
	for <manet-archive@odin.ietf.org>; Wed, 20 Nov 2002 11:02:07 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id gAKG4JE24652
	for manet-archive@odin.ietf.org; Wed, 20 Nov 2002 11:04:19 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gAKG4Jv24649
	for <manet-web-archive@optimus.ietf.org>; Wed, 20 Nov 2002 11:04:19 -0500
Received: from www1.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA23082
	for <manet-web-archive@ietf.org>; Wed, 20 Nov 2002 11:01:36 -0500 (EST)
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gAKFSAv21510;
	Wed, 20 Nov 2002 10:28:10 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gAKFIpv21100
	for <manet@optimus.ietf.org>; Wed, 20 Nov 2002 10:18:51 -0500
Received: from luna.tlmat.unican.es (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA21418
	for <manet@ietf.org>; Wed, 20 Nov 2002 10:16:08 -0500 (EST)
Received: from mizar (mizar.tlmat.unican.es [193.144.186.38]) by luna.tlmat.unican.es with SMTP (8.7.6/8.7.1) id QAA11060; Wed, 20 Nov 2002 16:56:54 +0100 (MET)
Message-ID: <00a201c290a8$72a18a50$26ba90c1@mizar>
From: =?iso-8859-1?Q?Ram=F3n_Ag=FCero?= <ramon@tlmat.unican.es>
To: "Lei Xue" <l.xue@warwick.ac.uk>
Cc: <manet@ietf.org>
References: <019b01c2908a$57edbd00$f790cd89@warwick.ac.uk>
Subject: Re: [manet] Ad Hoc mode in 802.11
Date: Wed, 20 Nov 2002 16:21:05 +0100
MIME-Version: 1.0
Content-Type: multipart/alternative;
	boundary="----=_NextPart_000_009F_01C290B0.D3517510"
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 6.00.2600.0000
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2600.0000
Sender: manet-admin@ietf.org
Errors-To: manet-admin@ietf.org
X-BeenThere: manet@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/manet>,
	<mailto:manet-request@ietf.org?subject=unsubscribe>
List-Id: Mobile Ad-hoc Networks  <manet.ietf.org>
List-Post: <mailto:manet@ietf.org>
List-Help: <mailto:manet-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/manet>,
	<mailto:manet-request@ietf.org?subject=subscribe>

This is a multi-part message in MIME format.

------=_NextPart_000_009F_01C290B0.D3517510
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

Dear Lei,

it is possible, although it is not a built-in functionality. The packet =
can be routed at layer three, but that is independent from the IEEE =
802.11 wireless cards, it is more an Operating System functionality, =
which you have to activate and configure.

HTH

Ram=F3n
  ----- Original Message -----=20
  From: Lei Xue=20
  To: manet@ietf.org=20
  Sent: Wednesday, November 20, 2002 12:45 PM
  Subject: [manet] Ad Hoc mode in 802.11


  Dear friends,

  In Ad Hoc mode of 802.11, any node that is within range of any other =
can communicate if they agree some basic rules. I wonder in this mode, =
if the node can be routed by the neighbor nodes to the one out of its =
range, like the pure Ad Hoc network does? Please kindly give your =
advice. Thanks.

  Best Regards,

  Lei

------=_NextPart_000_009F_01C290B0.D3517510
Content-Type: text/html;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META http-equiv=3DContent-Type content=3D"text/html; =
charset=3Diso-8859-1">
<META content=3D"MSHTML 6.00.2600.0" name=3DGENERATOR>
<STYLE></STYLE>
</HEAD>
<BODY bgColor=3D#ffffff>
<DIV><FONT face=3DCourier size=3D2>Dear Lei,</FONT></DIV>
<DIV><FONT face=3DCourier size=3D2></FONT>&nbsp;</DIV>
<DIV><FONT face=3DCourier size=3D2>it is possible, although it is not a =
built-in=20
functionality. The packet can be routed at layer three, but that is =
independent=20
from the IEEE 802.11 wireless cards, it is more an Operating System=20
functionality, which you have to activate and configure.</FONT></DIV>
<DIV><FONT face=3DCourier size=3D2></FONT>&nbsp;</DIV>
<DIV><FONT face=3DCourier size=3D2>HTH</FONT></DIV>
<DIV><FONT face=3DCourier size=3D2></FONT>&nbsp;</DIV>
<DIV><FONT face=3DCourier size=3D2>Ram=F3n</FONT></DIV>
<BLOCKQUOTE dir=3Dltr=20
style=3D"PADDING-RIGHT: 0px; PADDING-LEFT: 5px; MARGIN-LEFT: 5px; =
BORDER-LEFT: #000000 2px solid; MARGIN-RIGHT: 0px">
  <DIV style=3D"FONT: 10pt arial">----- Original Message ----- </DIV>
  <DIV=20
  style=3D"BACKGROUND: #e4e4e4; FONT: 10pt arial; font-color: =
black"><B>From:</B>=20
  <A title=3Dl.xue@warwick.ac.uk href=3D"mailto:l.xue@warwick.ac.uk">Lei =
Xue</A>=20
  </DIV>
  <DIV style=3D"FONT: 10pt arial"><B>To:</B> <A title=3Dmanet@ietf.org=20
  href=3D"mailto:manet@ietf.org">manet@ietf.org</A> </DIV>
  <DIV style=3D"FONT: 10pt arial"><B>Sent:</B> Wednesday, November 20, =
2002 12:45=20
  PM</DIV>
  <DIV style=3D"FONT: 10pt arial"><B>Subject:</B> [manet] Ad Hoc mode in =

  802.11</DIV>
  <DIV><BR></DIV>
  <DIV><FONT face=3DArial size=3D2>Dear friends,</FONT></DIV>
  <DIV>&nbsp;</DIV>
  <DIV><FONT face=3DArial size=3D2>In Ad Hoc mode of 802.11, any node =
that is within=20
  range of any other can communicate if they agree some basic rules. I =
wonder in=20
  this mode, if the node can be routed by the neighbor nodes to the one =
out of=20
  its range, like the pure Ad Hoc network does? Please kindly give your =
advice.=20
  Thanks.</FONT></DIV>
  <DIV>&nbsp;</DIV>
  <DIV><FONT face=3DArial size=3D2>Best Regards,</FONT></DIV>
  <DIV><FONT face=3DArial =
size=3D2><BR>Lei</FONT></DIV></BLOCKQUOTE></BODY></HTML>

------=_NextPart_000_009F_01C290B0.D3517510--

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



From manet-admin@ietf.org  Wed Nov 20 11:03:01 2002
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA23125
	for <manet-archive@lists.ietf.org>; Wed, 20 Nov 2002 11:03:01 -0500 (EST)
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gAKFgWv23107;
	Wed, 20 Nov 2002 10:42:32 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gAKFdov22944
	for <manet@optimus.ietf.org>; Wed, 20 Nov 2002 10:39:50 -0500
Received: from hades.snrc.uow.edu.au (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA22220
	for <manet@ietf.org>; Wed, 20 Nov 2002 10:37:06 -0500 (EST)
Received: from there (justin@eros [130.130.10.74])
	by hades.snrc.uow.edu.au (8.11.2/8.11.2) with SMTP id gAKFcjB26105;
	Thu, 21 Nov 2002 02:38:45 +1100 (EST)
Message-Id: <200211201538.gAKFcjB26105@hades.snrc.uow.edu.au>
Content-Type: text/plain;
  charset="gb2312"
From: Justin Lipman <justin@titr.uow.edu.au>
Reply-To: justin@titr.uow.edu.au
Organization: TITR
To: "Zhang Yanan" <csu_zyn@163.com>, <manet@ietf.org>
Subject: Re: [manet] who can help me about power-range in glomo?
Date: Thu, 21 Nov 2002 02:42:51 +1100
X-Mailer: KMail [version 1.3.2]
References: <000001c2909e$370b11a0$7600a8c0@zyn>
In-Reply-To: <000001c2909e$370b11a0$7600a8c0@zyn>
MIME-Version: 1.0
Content-Transfer-Encoding: 8bit
X-MIME-Autoconverted: from quoted-printable to 8bit by www1.ietf.org id gAKFdov22945
Sender: manet-admin@ietf.org
Errors-To: manet-admin@ietf.org
X-BeenThere: manet@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/manet>,
	<mailto:manet-request@ietf.org?subject=unsubscribe>
List-Id: Mobile Ad-hoc Networks  <manet.ietf.org>
List-Post: <mailto:manet@ietf.org>
List-Help: <mailto:manet-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/manet>,
	<mailto:manet-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 8bit

Hi,

Look through your "config.in" file.

#
# RADIO-TX-POWER: radio transmition power (in dBm)
#
RADIO-TX-POWER        8.0

You may then use the "radio_range" program that comes with glomosim in the 
"bin" directory to see the resultant range.

Hope this helps,
Justin

-- 
Telecommunications & Information Technology Research Institute
University of Wollongong, Australia 
http://www.titr.uow.edu.au


On Wed, 20 Nov 2002 22:19, Zhang Yanan wrote:
> hi,
> I can't find POWER-RANGE in config.in of Glomosim. From the manual of
> glomo1.0, I can find the parameter, but I can't find in the Version 2.03. 
> Thanks in advance.

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


From mailnull@www1.ietf.org  Wed Nov 20 11:21:49 2002
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA23674
	for <manet-archive@odin.ietf.org>; Wed, 20 Nov 2002 11:21:44 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id gAKGNuV26424
	for manet-archive@odin.ietf.org; Wed, 20 Nov 2002 11:23:56 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gAKGNVv26416
	for <manet-web-archive@optimus.ietf.org>; Wed, 20 Nov 2002 11:23:31 -0500
Received: from www1.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA23653
	for <manet-web-archive@ietf.org>; Wed, 20 Nov 2002 11:20:46 -0500 (EST)
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gAKFgWv23107;
	Wed, 20 Nov 2002 10:42:32 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gAKFdov22944
	for <manet@optimus.ietf.org>; Wed, 20 Nov 2002 10:39:50 -0500
Received: from hades.snrc.uow.edu.au (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA22220
	for <manet@ietf.org>; Wed, 20 Nov 2002 10:37:06 -0500 (EST)
Received: from there (justin@eros [130.130.10.74])
	by hades.snrc.uow.edu.au (8.11.2/8.11.2) with SMTP id gAKFcjB26105;
	Thu, 21 Nov 2002 02:38:45 +1100 (EST)
Message-Id: <200211201538.gAKFcjB26105@hades.snrc.uow.edu.au>
Content-Type: text/plain;
  charset="gb2312"
From: Justin Lipman <justin@titr.uow.edu.au>
Reply-To: justin@titr.uow.edu.au
Organization: TITR
To: "Zhang Yanan" <csu_zyn@163.com>, <manet@ietf.org>
Subject: Re: [manet] who can help me about power-range in glomo?
Date: Thu, 21 Nov 2002 02:42:51 +1100
X-Mailer: KMail [version 1.3.2]
References: <000001c2909e$370b11a0$7600a8c0@zyn>
In-Reply-To: <000001c2909e$370b11a0$7600a8c0@zyn>
MIME-Version: 1.0
Content-Transfer-Encoding: 8bit
X-MIME-Autoconverted: from quoted-printable to 8bit by www1.ietf.org id gAKFdov22945
Sender: manet-admin@ietf.org
Errors-To: manet-admin@ietf.org
X-BeenThere: manet@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/manet>,
	<mailto:manet-request@ietf.org?subject=unsubscribe>
List-Id: Mobile Ad-hoc Networks  <manet.ietf.org>
List-Post: <mailto:manet@ietf.org>
List-Help: <mailto:manet-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/manet>,
	<mailto:manet-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 8bit
Content-Transfer-Encoding: 8bit

Hi,

Look through your "config.in" file.

#
# RADIO-TX-POWER: radio transmition power (in dBm)
#
RADIO-TX-POWER        8.0

You may then use the "radio_range" program that comes with glomosim in the 
"bin" directory to see the resultant range.

Hope this helps,
Justin

-- 
Telecommunications & Information Technology Research Institute
University of Wollongong, Australia 
http://www.titr.uow.edu.au


On Wed, 20 Nov 2002 22:19, Zhang Yanan wrote:
> hi,
> I can't find POWER-RANGE in config.in of Glomosim. From the manual of
> glomo1.0, I can find the parameter, but I can't find in the Version 2.03. 
> Thanks in advance.

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



From manet-admin@ietf.org  Wed Nov 20 13:20:27 2002
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA26618
	for <manet-archive@lists.ietf.org>; Wed, 20 Nov 2002 13:20:27 -0500 (EST)
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gAKHsiv00609;
	Wed, 20 Nov 2002 12:54:44 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gAKHgDv32669
	for <manet@optimus.ietf.org>; Wed, 20 Nov 2002 12:42:13 -0500
Received: from che.onthejob.net (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA25725
	for <manet@ietf.org>; Wed, 20 Nov 2002 12:39:29 -0500 (EST)
Received: (from dyoung@localhost)
	by che.onthejob.net (8.9.3/8.9.3) id LAA21528
	for manet@ietf.org; Wed, 20 Nov 2002 11:42:08 -0600
Date: Wed, 20 Nov 2002 11:42:08 -0600
From: David Young <dyoung@ojctech.com>
To: manet@ietf.org
Subject: Re: [manet] Test: change in rute for an OLSR net
Message-ID: <20021120114208.A20817@che.onthejob.net>
Reply-To: dyoung@pobox.com
Mail-Followup-To: David Young <dyoung@che.onthejob.net>, manet@ietf.org
References: <002601c29092$2e0500e0$1f2304d4@beritpc82>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
User-Agent: Mutt/1.2.5i
In-Reply-To: <002601c29092$2e0500e0$1f2304d4@beritpc82>; from geir.gyland@applica.no on Wed, Nov 20, 2002 at 01:41:41PM +0100
Sender: manet-admin@ietf.org
Errors-To: manet-admin@ietf.org
X-BeenThere: manet@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/manet>,
	<mailto:manet-request@ietf.org?subject=unsubscribe>
List-Id: Mobile Ad-hoc Networks  <manet.ietf.org>
List-Post: <mailto:manet@ietf.org>
List-Help: <mailto:manet-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/manet>,
	<mailto:manet-request@ietf.org?subject=subscribe>


On Wed, Nov 20, 2002 at 01:41:41PM +0100, Geir Gyland wrote:
> 
> Does anyone have an explanation to justify the time? 
>  
> At the moment we do not trust our results!
> 

What do the debug outputs from OLSR say? What does tcpdump say is
happening "on the air" ?

Dave

-- 
David Young             OJC Technologies
dyoung@ojctech.com      Engineering from the Right Brain
                        Urbana, IL * (217) 278-3933
_______________________________________________
manet mailing list
manet@ietf.org
https://www1.ietf.org/mailman/listinfo/manet


From mailnull@www1.ietf.org  Wed Nov 20 13:40:30 2002
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA26980
	for <manet-archive@odin.ietf.org>; Wed, 20 Nov 2002 13:40:29 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id gAKIgiQ04064
	for manet-archive@odin.ietf.org; Wed, 20 Nov 2002 13:42:44 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gAKIghv04061
	for <manet-web-archive@optimus.ietf.org>; Wed, 20 Nov 2002 13:42:43 -0500
Received: from www1.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA26962
	for <manet-web-archive@ietf.org>; Wed, 20 Nov 2002 13:39:58 -0500 (EST)
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gAKHsiv00609;
	Wed, 20 Nov 2002 12:54:44 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gAKHgDv32669
	for <manet@optimus.ietf.org>; Wed, 20 Nov 2002 12:42:13 -0500
Received: from che.onthejob.net (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA25725
	for <manet@ietf.org>; Wed, 20 Nov 2002 12:39:29 -0500 (EST)
Received: (from dyoung@localhost)
	by che.onthejob.net (8.9.3/8.9.3) id LAA21528
	for manet@ietf.org; Wed, 20 Nov 2002 11:42:08 -0600
Date: Wed, 20 Nov 2002 11:42:08 -0600
From: David Young <dyoung@ojctech.com>
To: manet@ietf.org
Subject: Re: [manet] Test: change in rute for an OLSR net
Message-ID: <20021120114208.A20817@che.onthejob.net>
Reply-To: dyoung@pobox.com
Mail-Followup-To: David Young <dyoung@che.onthejob.net>, manet@ietf.org
References: <002601c29092$2e0500e0$1f2304d4@beritpc82>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
User-Agent: Mutt/1.2.5i
In-Reply-To: <002601c29092$2e0500e0$1f2304d4@beritpc82>; from geir.gyland@applica.no on Wed, Nov 20, 2002 at 01:41:41PM +0100
Sender: manet-admin@ietf.org
Errors-To: manet-admin@ietf.org
X-BeenThere: manet@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/manet>,
	<mailto:manet-request@ietf.org?subject=unsubscribe>
List-Id: Mobile Ad-hoc Networks  <manet.ietf.org>
List-Post: <mailto:manet@ietf.org>
List-Help: <mailto:manet-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/manet>,
	<mailto:manet-request@ietf.org?subject=subscribe>


On Wed, Nov 20, 2002 at 01:41:41PM +0100, Geir Gyland wrote:
> 
> Does anyone have an explanation to justify the time? 
>  
> At the moment we do not trust our results!
> 

What do the debug outputs from OLSR say? What does tcpdump say is
happening "on the air" ?

Dave

-- 
David Young             OJC Technologies
dyoung@ojctech.com      Engineering from the Right Brain
                        Urbana, IL * (217) 278-3933
_______________________________________________
manet mailing list
manet@ietf.org
https://www1.ietf.org/mailman/listinfo/manet



From manet-admin@ietf.org  Wed Nov 20 17:45:07 2002
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA03883
	for <manet-archive@lists.ietf.org>; Wed, 20 Nov 2002 17:45:07 -0500 (EST)
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gAKMMqv19692;
	Wed, 20 Nov 2002 17:22:52 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gAKMEAv19413
	for <manet@optimus.ietf.org>; Wed, 20 Nov 2002 17:14:10 -0500
Received: from hamberg.it.uu.se (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA02953
	for <manet@ietf.org>; Wed, 20 Nov 2002 17:11:24 -0500 (EST)
Received: from localhost (henrikl@localhost)
	by hamberg.it.uu.se (8.8.5/8.8.5) with ESMTP id XAA24523;
	Wed, 20 Nov 2002 23:14:01 +0100 (MET)
X-Authentication-Warning: hamberg.it.uu.se: henrikl owned process doing -bs
Date: Wed, 20 Nov 2002 23:14:01 +0100 (MET)
From: Henrik Lundgren <henrikl@docs.uu.se>
X-Sender: henrikl@hamberg.it.uu.se
To: geir.gyland@bigfoot.com
cc: manet@ietf.org
Subject: Re: [manet] Test: change in rute for an OLSR net
In-Reply-To: <002601c29092$2e0500e0$1f2304d4@beritpc82>
Message-ID: <Pine.GSO.4.21.0211202307450.24018-100000@hamberg.it.uu.se>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: manet-admin@ietf.org
Errors-To: manet-admin@ietf.org
X-BeenThere: manet@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/manet>,
	<mailto:manet-request@ietf.org?subject=unsubscribe>
List-Id: Mobile Ad-hoc Networks  <manet.ietf.org>
List-Post: <mailto:manet@ietf.org>
List-Help: <mailto:manet-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/manet>,
	<mailto:manet-request@ietf.org?subject=subscribe>

Hi,

We have the same experience; same scenario but
with OLSR from Inria with default parameters
and we experience about 10 seconds re-route time.
However, We did not investigated this further.

Henrik Lundgren
Uppsala University


On Wed, 20 Nov 2002, Geir Gyland wrote:

> Hi all!
> 
> 
> We did some simple static test of route change using 4 nodes set up like
> this:
> 
>       .  3   .
>    .             .
> 1                   4
>    .             .
>       .  2   .
> 
> Node 1 and 4 are out of reach for each other (2 hops)
> 
> We generated CBR traffic with a speed of 11Mb/s (UDP) traffic and sent
> it through the network. Initially the route was 1 - 3 - 4 then we
> stopped the interface on node 3 and observed when the traffic started
> passing over the route 1 - 2 - 4
> 
> I would have believed the route change to take 4 - 6 seconds (Neighbor
> hold time + TC) but we observed twice as much time (between 12 and 15
> sec) before the traffic was traveling over node 2.
> 
> Does anyone have an explanation to justify the time? 
>  
> At the moment we do not trust our results!
> 
> Additional information:
>  
> All nodes are laptops, running Red Hat 7.3 using the NLR (nolsrd)
> modified version of the INRIA olsrd code version 1.0a9. 
> 
> OLSR parameters were set to the default values of the NRL version 
> HELLO interval 0.5
> HELLO multiplier 8
> TC intereval 3
> TC multiplier 5
> 
> -----------------------------
> Geir Gyland
> E-mail: geir.gyland@bigfoot.com
> 
> 
> 
> ---
> [This E-mail was scanned for viruses by Declude Virus]
> 
> _______________________________________________
> manet mailing list
> manet@ietf.org
> https://www1.ietf.org/mailman/listinfo/manet
> 

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


From mailnull@www1.ietf.org  Wed Nov 20 17:56:24 2002
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA04159
	for <manet-archive@odin.ietf.org>; Wed, 20 Nov 2002 17:56:24 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id gAKMwd122390
	for manet-archive@odin.ietf.org; Wed, 20 Nov 2002 17:58:39 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gAKMwdv22387
	for <manet-web-archive@optimus.ietf.org>; Wed, 20 Nov 2002 17:58:39 -0500
Received: from www1.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA04155
	for <manet-web-archive@ietf.org>; Wed, 20 Nov 2002 17:55:53 -0500 (EST)
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gAKMMqv19692;
	Wed, 20 Nov 2002 17:22:52 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gAKMEAv19413
	for <manet@optimus.ietf.org>; Wed, 20 Nov 2002 17:14:10 -0500
Received: from hamberg.it.uu.se (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA02953
	for <manet@ietf.org>; Wed, 20 Nov 2002 17:11:24 -0500 (EST)
Received: from localhost (henrikl@localhost)
	by hamberg.it.uu.se (8.8.5/8.8.5) with ESMTP id XAA24523;
	Wed, 20 Nov 2002 23:14:01 +0100 (MET)
X-Authentication-Warning: hamberg.it.uu.se: henrikl owned process doing -bs
Date: Wed, 20 Nov 2002 23:14:01 +0100 (MET)
From: Henrik Lundgren <henrikl@docs.uu.se>
X-Sender: henrikl@hamberg.it.uu.se
To: geir.gyland@bigfoot.com
cc: manet@ietf.org
Subject: Re: [manet] Test: change in rute for an OLSR net
In-Reply-To: <002601c29092$2e0500e0$1f2304d4@beritpc82>
Message-ID: <Pine.GSO.4.21.0211202307450.24018-100000@hamberg.it.uu.se>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: manet-admin@ietf.org
Errors-To: manet-admin@ietf.org
X-BeenThere: manet@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/manet>,
	<mailto:manet-request@ietf.org?subject=unsubscribe>
List-Id: Mobile Ad-hoc Networks  <manet.ietf.org>
List-Post: <mailto:manet@ietf.org>
List-Help: <mailto:manet-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/manet>,
	<mailto:manet-request@ietf.org?subject=subscribe>

Hi,

We have the same experience; same scenario but
with OLSR from Inria with default parameters
and we experience about 10 seconds re-route time.
However, We did not investigated this further.

Henrik Lundgren
Uppsala University


On Wed, 20 Nov 2002, Geir Gyland wrote:

> Hi all!
> 
> 
> We did some simple static test of route change using 4 nodes set up like
> this:
> 
>       .  3   .
>    .             .
> 1                   4
>    .             .
>       .  2   .
> 
> Node 1 and 4 are out of reach for each other (2 hops)
> 
> We generated CBR traffic with a speed of 11Mb/s (UDP) traffic and sent
> it through the network. Initially the route was 1 - 3 - 4 then we
> stopped the interface on node 3 and observed when the traffic started
> passing over the route 1 - 2 - 4
> 
> I would have believed the route change to take 4 - 6 seconds (Neighbor
> hold time + TC) but we observed twice as much time (between 12 and 15
> sec) before the traffic was traveling over node 2.
> 
> Does anyone have an explanation to justify the time? 
>  
> At the moment we do not trust our results!
> 
> Additional information:
>  
> All nodes are laptops, running Red Hat 7.3 using the NLR (nolsrd)
> modified version of the INRIA olsrd code version 1.0a9. 
> 
> OLSR parameters were set to the default values of the NRL version 
> HELLO interval 0.5
> HELLO multiplier 8
> TC intereval 3
> TC multiplier 5
> 
> -----------------------------
> Geir Gyland
> E-mail: geir.gyland@bigfoot.com
> 
> 
> 
> ---
> [This E-mail was scanned for viruses by Declude Virus]
> 
> _______________________________________________
> manet mailing list
> manet@ietf.org
> https://www1.ietf.org/mailman/listinfo/manet
> 

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



From manet-admin@ietf.org  Wed Nov 20 19:53:53 2002
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA06529
	for <manet-archive@lists.ietf.org>; Wed, 20 Nov 2002 19:53:52 -0500 (EST)
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gAKNdev24942;
	Wed, 20 Nov 2002 18:39:40 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gAKNWav24183
	for <manet@optimus.ietf.org>; Wed, 20 Nov 2002 18:32:36 -0500
Received: from coe.drexel.edu (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA04726
	for <manet@ietf.org>; Wed, 20 Nov 2002 18:28:29 -0500 (EST)
Received: from drexel.edu (sense.mcs.drexel.edu [129.25.6.152])
	by coe.drexel.edu (8.11.6/8.11.4) with ESMTP id gAKNV1a16460;
	Wed, 20 Nov 2002 18:31:01 -0500 (EST)
Message-ID: <3DDC1B4F.3090900@drexel.edu>
Date: Wed, 20 Nov 2002 18:31:27 -0500
From: John Novatnack <jmn27@drexel.edu>
User-Agent: Mozilla/5.0 (X11; U; SunOS sun4u; en-US; rv:1.2b) Gecko/20021027
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: geir.gyland@bigfoot.com
CC: manet@ietf.org
Subject: Re: [manet] Test: change in rute for an OLSR net
References: <002601c29092$2e0500e0$1f2304d4@beritpc82>
In-Reply-To: <002601c29092$2e0500e0$1f2304d4@beritpc82>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit
Sender: manet-admin@ietf.org
Errors-To: manet-admin@ietf.org
X-BeenThere: manet@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/manet>,
	<mailto:manet-request@ietf.org?subject=unsubscribe>
List-Id: Mobile Ad-hoc Networks  <manet.ietf.org>
List-Post: <mailto:manet@ietf.org>
List-Help: <mailto:manet-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/manet>,
	<mailto:manet-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 7bit

Hi,
    We have been working with analyzing OLSR within simulations, and 
found  similar results.  To answer your question, you can trust your 
results.  We were able to draw out the events that are the cause for the 
route convergence time.  Generally, it is due to the events that must 
take place for a chain of MPRs to be setup before a topology message 
will be forwarded.  A paper on all of our findings is forthcoming.  Let 
me know if you have any more questions.

- john

Geir Gyland wrote:

>Hi all!
>
>
>We did some simple static test of route change using 4 nodes set up like
>this:
>
>      .  3   .
>   .             .
>1                   4
>   .             .
>      .  2   .
>
>Node 1 and 4 are out of reach for each other (2 hops)
>
>We generated CBR traffic with a speed of 11Mb/s (UDP) traffic and sent
>it through the network. Initially the route was 1 - 3 - 4 then we
>stopped the interface on node 3 and observed when the traffic started
>passing over the route 1 - 2 - 4
>
>I would have believed the route change to take 4 - 6 seconds (Neighbor
>hold time + TC) but we observed twice as much time (between 12 and 15
>sec) before the traffic was traveling over node 2.
>
>Does anyone have an explanation to justify the time? 
> 
>At the moment we do not trust our results!
>
>Additional information:
> 
>All nodes are laptops, running Red Hat 7.3 using the NLR (nolsrd)
>modified version of the INRIA olsrd code version 1.0a9. 
>
>OLSR parameters were set to the default values of the NRL version 
>HELLO interval 0.5
>HELLO multiplier 8
>TC intereval 3
>TC multiplier 5
>
>-----------------------------
>Geir Gyland
>E-mail: geir.gyland@bigfoot.com
>
>
>
>---
>[This E-mail was scanned for viruses by Declude Virus]
>
>_______________________________________________
>manet mailing list
>manet@ietf.org
>https://www1.ietf.org/mailman/listinfo/manet
>
>  
>


-- 
John Novatnack ( john@plan.cs.drexel.edu )
Research Assistant: ITCS Laboratory - Drexel University
http://itcsl.cs.drexel.edu
http://itcsl.cs.drexel.edu/~john


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


From mailnull@www1.ietf.org  Wed Nov 20 20:09:44 2002
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id UAA06961
	for <manet-archive@odin.ietf.org>; Wed, 20 Nov 2002 20:09:44 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id gAL1C2f30302
	for manet-archive@odin.ietf.org; Wed, 20 Nov 2002 20:12:02 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gAL1C2v30299
	for <manet-web-archive@optimus.ietf.org>; Wed, 20 Nov 2002 20:12:02 -0500
Received: from www1.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id UAA06887
	for <manet-web-archive@ietf.org>; Wed, 20 Nov 2002 20:08:09 -0500 (EST)
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gAKNdev24942;
	Wed, 20 Nov 2002 18:39:40 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gAKNWav24183
	for <manet@optimus.ietf.org>; Wed, 20 Nov 2002 18:32:36 -0500
Received: from coe.drexel.edu (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA04726
	for <manet@ietf.org>; Wed, 20 Nov 2002 18:28:29 -0500 (EST)
Received: from drexel.edu (sense.mcs.drexel.edu [129.25.6.152])
	by coe.drexel.edu (8.11.6/8.11.4) with ESMTP id gAKNV1a16460;
	Wed, 20 Nov 2002 18:31:01 -0500 (EST)
Message-ID: <3DDC1B4F.3090900@drexel.edu>
Date: Wed, 20 Nov 2002 18:31:27 -0500
From: John Novatnack <jmn27@drexel.edu>
User-Agent: Mozilla/5.0 (X11; U; SunOS sun4u; en-US; rv:1.2b) Gecko/20021027
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: geir.gyland@bigfoot.com
CC: manet@ietf.org
Subject: Re: [manet] Test: change in rute for an OLSR net
References: <002601c29092$2e0500e0$1f2304d4@beritpc82>
In-Reply-To: <002601c29092$2e0500e0$1f2304d4@beritpc82>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit
Sender: manet-admin@ietf.org
Errors-To: manet-admin@ietf.org
X-BeenThere: manet@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/manet>,
	<mailto:manet-request@ietf.org?subject=unsubscribe>
List-Id: Mobile Ad-hoc Networks  <manet.ietf.org>
List-Post: <mailto:manet@ietf.org>
List-Help: <mailto:manet-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/manet>,
	<mailto:manet-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit

Hi,
    We have been working with analyzing OLSR within simulations, and 
found  similar results.  To answer your question, you can trust your 
results.  We were able to draw out the events that are the cause for the 
route convergence time.  Generally, it is due to the events that must 
take place for a chain of MPRs to be setup before a topology message 
will be forwarded.  A paper on all of our findings is forthcoming.  Let 
me know if you have any more questions.

- john

Geir Gyland wrote:

>Hi all!
>
>
>We did some simple static test of route change using 4 nodes set up like
>this:
>
>      .  3   .
>   .             .
>1                   4
>   .             .
>      .  2   .
>
>Node 1 and 4 are out of reach for each other (2 hops)
>
>We generated CBR traffic with a speed of 11Mb/s (UDP) traffic and sent
>it through the network. Initially the route was 1 - 3 - 4 then we
>stopped the interface on node 3 and observed when the traffic started
>passing over the route 1 - 2 - 4
>
>I would have believed the route change to take 4 - 6 seconds (Neighbor
>hold time + TC) but we observed twice as much time (between 12 and 15
>sec) before the traffic was traveling over node 2.
>
>Does anyone have an explanation to justify the time? 
> 
>At the moment we do not trust our results!
>
>Additional information:
> 
>All nodes are laptops, running Red Hat 7.3 using the NLR (nolsrd)
>modified version of the INRIA olsrd code version 1.0a9. 
>
>OLSR parameters were set to the default values of the NRL version 
>HELLO interval 0.5
>HELLO multiplier 8
>TC intereval 3
>TC multiplier 5
>
>-----------------------------
>Geir Gyland
>E-mail: geir.gyland@bigfoot.com
>
>
>
>---
>[This E-mail was scanned for viruses by Declude Virus]
>
>_______________________________________________
>manet mailing list
>manet@ietf.org
>https://www1.ietf.org/mailman/listinfo/manet
>
>  
>


-- 
John Novatnack ( john@plan.cs.drexel.edu )
Research Assistant: ITCS Laboratory - Drexel University
http://itcsl.cs.drexel.edu
http://itcsl.cs.drexel.edu/~john


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



From manet-admin@ietf.org  Wed Nov 20 22:14:32 2002
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id WAA09956
	for <manet-archive@lists.ietf.org>; Wed, 20 Nov 2002 22:14:32 -0500 (EST)
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gAL35mv03818;
	Wed, 20 Nov 2002 22:05:48 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gAL31Mv03684
	for <manet@optimus.ietf.org>; Wed, 20 Nov 2002 22:01:22 -0500
Received: from mailhost.iprg.nokia.com (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id VAA09530
	for <manet@ietf.org>; Wed, 20 Nov 2002 21:58:34 -0500 (EST)
Received: from darkstar.iprg.nokia.com (darkstar.iprg.nokia.com [205.226.5.69])
	by mailhost.iprg.nokia.com (8.9.3/8.9.3-GLGS) with ESMTP id TAA11915;
	Wed, 20 Nov 2002 19:01:12 -0800 (PST)
Received: (from root@localhost)
	by darkstar.iprg.nokia.com (8.11.0/8.11.0-DARKSTAR) id gAL31BK05141;
	Wed, 20 Nov 2002 19:01:11 -0800
X-mProtect: <200211210301> Nokia Silicon Valley Messaging Protection
Received: from UNKNOWN (172.21.193.188, claiming to be "iprg.nokia.com")
	by darkstar.iprg.nokia.com smtpdiDz9RY; Wed, 20 Nov 2002 19:01:07 PST
Message-ID: <3DDC4C6F.1020804@iprg.nokia.com>
Date: Wed, 20 Nov 2002 19:01:03 -0800
From: "Fred L. Templin" <ftemplin@iprg.nokia.com>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.0rc2) Gecko/20020510
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: Philippe Jacquet <philippe.jacquet@inria.fr>
CC: manet@ietf.org
Subject: Re: [manet] draft-ietf-manet-olsr-07.txt
References: <000901c2870f$76ff57a0$1f175d80@inria.fr>
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit
Sender: manet-admin@ietf.org
Errors-To: manet-admin@ietf.org
X-BeenThere: manet@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/manet>,
	<mailto:manet-request@ietf.org?subject=unsubscribe>
List-Id: Mobile Ad-hoc Networks  <manet.ietf.org>
List-Post: <mailto:manet@ietf.org>
List-Help: <mailto:manet-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/manet>,
	<mailto:manet-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 7bit

Hello Phillippe,

I've been checking into path MTU discovery issues for various protocols and
mechanisms, and I'm wondering if this is something you need to account 
for in
the OLSR draft. In section 2.3.6.3, the following text appears:

   A MID message is sent by a node in the network to declare its multi-
   ple interfaces (if any). I.e., the MID message contains the list of
   interface addresses which are associated to its main address.  The
   list of addresses can be partial in each TC message (e.g. due to mes-
   sage size limitations, imposed by the network), but parsing of all
   MID messages describing a nodes interface set MUST be complete within
   a certain refreshing period (MID_INTERVAL). The information diffused
   in the network by these MID messages will help each node to calculate
   its routing table. A node which has only a single interface address
   participating in the MANET (i.e. running OLSR), MUST NOT generate any
   MID message.

I am wondering if it will make sense to add a maximum transmit unit
(MTU) parameter for each interface in the mid message so that other
nodes can avoid sending packets that will fragment and/or be dropped
if the don't-fragment (DF) bit is set. It may be possible to just
add the minimum MTU of all the links advertised in the MID message?
I'm concerned about the effects of fragmentation on wireless media;
especially when large messages are flooded. I think it may help to
find a "minimum MTU" for the scope of the MANET so that the multicast
flooding won't get hampered by harmful fragmentation.

Your thoughts?

Fred Templin
ftemplin@iprg.nokia.com



Philippe Jacquet wrote:

>Hello,
>
>Due to a technical problem of last minute, our draft submission of OLSR v7
>failed (again). Sorry for this inconvenience. Anyhow  the draft is available
>on the following URL:
>http://hipercom.inria.fr/olsr/draft-ietf-manet-olsr-07.txt
>Please take a look at it. We will be happy to discuss it during the Atlanta
>meeting. There are not big changes from what has already been presented in
>Yokohama.
>
>Major changes from version 06 to version 07
>
>     -    Introduction of relay willingness in hellos
>
>     -    Introduction of redundant link set in TC messages
>
>     -    Introduction of packet sequence number in order to clarify
>          link management
>
>Philippe
>
>
>_______________________________________________
>manet mailing list
>manet@ietf.org
>https://www1.ietf.org/mailman/listinfo/manet
>  
>



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


From mailnull@www1.ietf.org  Wed Nov 20 22:25:39 2002
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id WAA10211
	for <manet-archive@odin.ietf.org>; Wed, 20 Nov 2002 22:25:39 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id gAL3RuU05279
	for manet-archive@odin.ietf.org; Wed, 20 Nov 2002 22:27:56 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gAL3Ruv05276
	for <manet-web-archive@optimus.ietf.org>; Wed, 20 Nov 2002 22:27:56 -0500
Received: from www1.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id WAA10173
	for <manet-web-archive@ietf.org>; Wed, 20 Nov 2002 22:24:53 -0500 (EST)
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gAL35mv03818;
	Wed, 20 Nov 2002 22:05:48 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gAL31Mv03684
	for <manet@optimus.ietf.org>; Wed, 20 Nov 2002 22:01:22 -0500
Received: from mailhost.iprg.nokia.com (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id VAA09530
	for <manet@ietf.org>; Wed, 20 Nov 2002 21:58:34 -0500 (EST)
Received: from darkstar.iprg.nokia.com (darkstar.iprg.nokia.com [205.226.5.69])
	by mailhost.iprg.nokia.com (8.9.3/8.9.3-GLGS) with ESMTP id TAA11915;
	Wed, 20 Nov 2002 19:01:12 -0800 (PST)
Received: (from root@localhost)
	by darkstar.iprg.nokia.com (8.11.0/8.11.0-DARKSTAR) id gAL31BK05141;
	Wed, 20 Nov 2002 19:01:11 -0800
X-mProtect: <200211210301> Nokia Silicon Valley Messaging Protection
Received: from UNKNOWN (172.21.193.188, claiming to be "iprg.nokia.com")
	by darkstar.iprg.nokia.com smtpdiDz9RY; Wed, 20 Nov 2002 19:01:07 PST
Message-ID: <3DDC4C6F.1020804@iprg.nokia.com>
Date: Wed, 20 Nov 2002 19:01:03 -0800
From: "Fred L. Templin" <ftemplin@iprg.nokia.com>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.0rc2) Gecko/20020510
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: Philippe Jacquet <philippe.jacquet@inria.fr>
CC: manet@ietf.org
Subject: Re: [manet] draft-ietf-manet-olsr-07.txt
References: <000901c2870f$76ff57a0$1f175d80@inria.fr>
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit
Sender: manet-admin@ietf.org
Errors-To: manet-admin@ietf.org
X-BeenThere: manet@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/manet>,
	<mailto:manet-request@ietf.org?subject=unsubscribe>
List-Id: Mobile Ad-hoc Networks  <manet.ietf.org>
List-Post: <mailto:manet@ietf.org>
List-Help: <mailto:manet-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/manet>,
	<mailto:manet-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit

Hello Phillippe,

I've been checking into path MTU discovery issues for various protocols and
mechanisms, and I'm wondering if this is something you need to account 
for in
the OLSR draft. In section 2.3.6.3, the following text appears:

   A MID message is sent by a node in the network to declare its multi-
   ple interfaces (if any). I.e., the MID message contains the list of
   interface addresses which are associated to its main address.  The
   list of addresses can be partial in each TC message (e.g. due to mes-
   sage size limitations, imposed by the network), but parsing of all
   MID messages describing a nodes interface set MUST be complete within
   a certain refreshing period (MID_INTERVAL). The information diffused
   in the network by these MID messages will help each node to calculate
   its routing table. A node which has only a single interface address
   participating in the MANET (i.e. running OLSR), MUST NOT generate any
   MID message.

I am wondering if it will make sense to add a maximum transmit unit
(MTU) parameter for each interface in the mid message so that other
nodes can avoid sending packets that will fragment and/or be dropped
if the don't-fragment (DF) bit is set. It may be possible to just
add the minimum MTU of all the links advertised in the MID message?
I'm concerned about the effects of fragmentation on wireless media;
especially when large messages are flooded. I think it may help to
find a "minimum MTU" for the scope of the MANET so that the multicast
flooding won't get hampered by harmful fragmentation.

Your thoughts?

Fred Templin
ftemplin@iprg.nokia.com



Philippe Jacquet wrote:

>Hello,
>
>Due to a technical problem of last minute, our draft submission of OLSR v7
>failed (again). Sorry for this inconvenience. Anyhow  the draft is available
>on the following URL:
>http://hipercom.inria.fr/olsr/draft-ietf-manet-olsr-07.txt
>Please take a look at it. We will be happy to discuss it during the Atlanta
>meeting. There are not big changes from what has already been presented in
>Yokohama.
>
>Major changes from version 06 to version 07
>
>     -    Introduction of relay willingness in hellos
>
>     -    Introduction of redundant link set in TC messages
>
>     -    Introduction of packet sequence number in order to clarify
>          link management
>
>Philippe
>
>
>_______________________________________________
>manet mailing list
>manet@ietf.org
>https://www1.ietf.org/mailman/listinfo/manet
>  
>



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



From manet-admin@ietf.org  Thu Nov 21 10:51:20 2002
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA07244
	for <manet-archive@lists.ietf.org>; Thu, 21 Nov 2002 10:51:20 -0500 (EST)
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gALFgQv22997;
	Thu, 21 Nov 2002 10:42:26 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gALEvuv19617
	for <manet@optimus.ietf.org>; Thu, 21 Nov 2002 09:57:56 -0500
Received: from drago.eurecom.fr (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA04697
	for <manet@ietf.org>; Thu, 21 Nov 2002 09:54:09 -0500 (EST)
Received: from monza.eurecom.fr (localhost [127.0.0.1])
	by drago.eurecom.fr (8.12.1/8.12.1) with ESMTP id gALEuk6A018095
	for <manet@ietf.org>; Thu, 21 Nov 2002 15:56:47 +0100 (MET)
Received: from LOKHLASS (lokhlass.eurecom.fr [172.17.10.154])
	by monza.eurecom.fr (Postfix) with ESMTP id F37B33C4AB
	for <manet@ietf.org>; Thu, 21 Nov 2002 15:56:46 +0100 (MET)
From: "Delphine Celentano" <Delphine.Celentano@eurecom.fr>
To: <manet@ietf.org>
Date: Thu, 21 Nov 2002 15:56:46 +0100
Organization: Institut Eurecom
Message-ID: <005701c2916e$36baff50$9a0a11ac@LOKHLASS>
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: 7bit
X-Priority: 3 (Normal)
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook, Build 10.0.3416
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2600.0000
Importance: Normal
Content-Transfer-Encoding: 7bit
Subject: [manet] MADNET 2003 - Deadline Dec. 25
Sender: manet-admin@ietf.org
Errors-To: manet-admin@ietf.org
X-BeenThere: manet@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/manet>,
	<mailto:manet-request@ietf.org?subject=unsubscribe>
List-Id: Mobile Ad-hoc Networks  <manet.ietf.org>
List-Post: <mailto:manet@ietf.org>
List-Help: <mailto:manet-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/manet>,
	<mailto:manet-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 7bit

MADNET 2003 (Workshop on Mobile Ad Hoc Networking and Computing) 
Organized by  RTP Reseaux- CNRS/STIC

Institut EURECOM 
Sophia-Antipolis, France 
January 24,  2003 

Call for Presentation
_____________________

 The presentation will be selected based on an extended summary, maximum
4 pages, that should be sent via email to Navid.Nikaein@eurecom.fr . In
general this workshop is interested in papers that address networking or
computing problems in the context of mobile and wireless ad hoc
networks, ad hoc computing systems, and sensor networks. Specific topics
of interest include the following:
 
Routing protocols (unicast, multicast, geocast, content-based, etc.)  
Media access techniques  
Transport-layer issues  
Hardware and software platforms, systems, and testbeds  
Applications for ad hoc networks  
Power-aware, low-power, and energy-efficient designs  
Quality-of-service issues  
Security and fault tolerance issues  
Self-configuration in ad hoc networks  
Processing and fusion of data in sensor networks  
Location discovery and management  
Timing synchronization  
Distributed algorithms for ad hoc networks  
Cross-layer interactions, including between higher and physical layers  

Please consult the Program Co-Chair Andrzej.Duda@imag.fr if you are
uncertain whether your presentationh falls within the scope of the
symposium. 

Extended Summary Submission Instructions
All submissions will be handled electronically and must be in PDF or
PostScript format.  

Important Dates
---------------
Extended Summary Submission Deadline: December 25, 2002 
Notification of Acceptance:  January 10, 2003 
Workshop: January 24, 2003 


Worskop Organizers and Program Committee
----------------------------------------
General Chair: 
Christian.Bonnet@eurecom.fr 

Program Committee: 
Eric Fleury (INRIA) Eric.Fleury@inria.fr
Khaldoun Al Agha Khaldoun.AlAgha@lri.fr
REYNAUDLaurent FTRD/DAC/LAN laurent.reynaud@rd.francetelecom.com
Serge FdidaSerge.Fdida@lip6.fr
Michel Diaz (LASS)diaz@lass.fr
Refik Molva (EURECOM)Refik.Molva@eurecom.fr
Thomas Noel (ULP/LSIIT - CNRS)Thomas.Noel@dpt-info.u-strasbg.fr to be
completed.
 
Program Co-Chairs 
Andrzej.Duda@imag.fr 
 
Local Arrangemenst Co-Chair 
Navid.Nikaein@eurecom.fr 

  
Registration Chair: 
TBD  
Publicity Co-Chairs:

Shiyi.Wu@eurecom.fr 
Piero.Michiardi@eurecom.fr 

Please feel free to visit our web site :
http://www.eurecom.fr/%7Enikaeinn/madnet2003/cfp.html

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


From mailnull@www1.ietf.org  Thu Nov 21 10:52:50 2002
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA07292
	for <manet-archive@odin.ietf.org>; Thu, 21 Nov 2002 10:52:50 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id gALFt2G23841
	for manet-archive@odin.ietf.org; Thu, 21 Nov 2002 10:55:02 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gALFt2v23838
	for <manet-web-archive@optimus.ietf.org>; Thu, 21 Nov 2002 10:55:02 -0500
Received: from www1.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA07166
	for <manet-web-archive@ietf.org>; Thu, 21 Nov 2002 10:50:29 -0500 (EST)
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gALFUnv21826;
	Thu, 21 Nov 2002 10:30:49 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gALAPvv04436
	for <manet@optimus.ietf.org>; Thu, 21 Nov 2002 05:25:57 -0500
Received: from nez-perce.inria.fr (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id FAA27301
	for <manet@ietf.org>; Thu, 21 Nov 2002 05:23:16 -0500 (EST)
Received: from inria.fr (ruspina.inria.fr [128.93.17.52])
	by nez-perce.inria.fr (8.11.1/8.11.1) with ESMTP id gALAPn105198;
	Thu, 21 Nov 2002 11:25:49 +0100 (MET)
Message-ID: <3DDCC576.9B3A1C27@inria.fr>
Date: Thu, 21 Nov 2002 12:37:26 +0100
From: Anis LAOUITI <anis.laouiti@inria.fr>
X-Mailer: Mozilla 4.5 [en] (X11; I; Linux 2.4.6 i686)
X-Accept-Language: en
MIME-Version: 1.0
To: geir.gyland@bigfoot.com
CC: manet@ietf.org, geir.gyland@applica.no, dyoung@ojctech.com,
        henrikl@docs.uu.se, John Novatnack <jmn27@drexel.edu>
Subject: Re: [manet] Test: change in rute for an OLSR net
References: <002601c29092$2e0500e0$1f2304d4@beritpc82>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit
Sender: manet-admin@ietf.org
Errors-To: manet-admin@ietf.org
X-BeenThere: manet@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/manet>,
	<mailto:manet-request@ietf.org?subject=unsubscribe>
List-Id: Mobile Ad-hoc Networks  <manet.ietf.org>
List-Post: <mailto:manet@ietf.org>
List-Help: <mailto:manet-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/manet>,
	<mailto:manet-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit

Hi guys,

In the OLSR draft 6, we have introduced  new mechanisms
to react fastly  to such situations. You can find all details in the
section
"2.3.9.  Advanced Topology Discovery Functioning" of the OLSR draft 7.

Anis LAOUITI


Geir Gyland wrote:

> Hi all!
>
> We did some simple static test of route change using 4 nodes set up like
> this:
>
>       .  3   .
>    .             .
> 1                   4
>    .             .
>       .  2   .
>
> Node 1 and 4 are out of reach for each other (2 hops)
>
> We generated CBR traffic with a speed of 11Mb/s (UDP) traffic and sent
> it through the network. Initially the route was 1 - 3 - 4 then we
> stopped the interface on node 3 and observed when the traffic started
> passing over the route 1 - 2 - 4
>
> I would have believed the route change to take 4 - 6 seconds (Neighbor
> hold time + TC) but we observed twice as much time (between 12 and 15
> sec) before the traffic was traveling over node 2.
>
> Does anyone have an explanation to justify the time?
>
> At the moment we do not trust our results!
>
> Additional information:
>
> All nodes are laptops, running Red Hat 7.3 using the NLR (nolsrd)
> modified version of the INRIA olsrd code version 1.0a9.
>
> OLSR parameters were set to the default values of the NRL version
> HELLO interval 0.5
> HELLO multiplier 8
> TC intereval 3
> TC multiplier 5
>
> -----------------------------
> Geir Gyland
> E-mail: geir.gyland@bigfoot.com
>
> ---
> [This E-mail was scanned for viruses by Declude Virus]
>
> _______________________________________________
> manet mailing list
> manet@ietf.org
> https://www1.ietf.org/mailman/listinfo/manet

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



From mailnull@www1.ietf.org  Thu Nov 21 10:57:52 2002
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA07445
	for <manet-archive@odin.ietf.org>; Thu, 21 Nov 2002 10:57:52 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id gALG04F24091
	for manet-archive@odin.ietf.org; Thu, 21 Nov 2002 11:00:04 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gALG04v24088
	for <manet-web-archive@optimus.ietf.org>; Thu, 21 Nov 2002 11:00:04 -0500
Received: from www1.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA07424
	for <manet-web-archive@ietf.org>; Thu, 21 Nov 2002 10:57:21 -0500 (EST)
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gALFgQv22997;
	Thu, 21 Nov 2002 10:42:26 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gALEvuv19617
	for <manet@optimus.ietf.org>; Thu, 21 Nov 2002 09:57:56 -0500
Received: from drago.eurecom.fr (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA04697
	for <manet@ietf.org>; Thu, 21 Nov 2002 09:54:09 -0500 (EST)
Received: from monza.eurecom.fr (localhost [127.0.0.1])
	by drago.eurecom.fr (8.12.1/8.12.1) with ESMTP id gALEuk6A018095
	for <manet@ietf.org>; Thu, 21 Nov 2002 15:56:47 +0100 (MET)
Received: from LOKHLASS (lokhlass.eurecom.fr [172.17.10.154])
	by monza.eurecom.fr (Postfix) with ESMTP id F37B33C4AB
	for <manet@ietf.org>; Thu, 21 Nov 2002 15:56:46 +0100 (MET)
From: "Delphine Celentano" <Delphine.Celentano@eurecom.fr>
To: <manet@ietf.org>
Date: Thu, 21 Nov 2002 15:56:46 +0100
Organization: Institut Eurecom
Message-ID: <005701c2916e$36baff50$9a0a11ac@LOKHLASS>
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: 7bit
X-Priority: 3 (Normal)
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook, Build 10.0.3416
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2600.0000
Importance: Normal
Content-Transfer-Encoding: 7bit
Subject: [manet] MADNET 2003 - Deadline Dec. 25
Sender: manet-admin@ietf.org
Errors-To: manet-admin@ietf.org
X-BeenThere: manet@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/manet>,
	<mailto:manet-request@ietf.org?subject=unsubscribe>
List-Id: Mobile Ad-hoc Networks  <manet.ietf.org>
List-Post: <mailto:manet@ietf.org>
List-Help: <mailto:manet-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/manet>,
	<mailto:manet-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit

MADNET 2003 (Workshop on Mobile Ad Hoc Networking and Computing) 
Organized by  RTP Reseaux- CNRS/STIC

Institut EURECOM 
Sophia-Antipolis, France 
January 24,  2003 

Call for Presentation
_____________________

 The presentation will be selected based on an extended summary, maximum
4 pages, that should be sent via email to Navid.Nikaein@eurecom.fr . In
general this workshop is interested in papers that address networking or
computing problems in the context of mobile and wireless ad hoc
networks, ad hoc computing systems, and sensor networks. Specific topics
of interest include the following:
 
Routing protocols (unicast, multicast, geocast, content-based, etc.)  
Media access techniques  
Transport-layer issues  
Hardware and software platforms, systems, and testbeds  
Applications for ad hoc networks  
Power-aware, low-power, and energy-efficient designs  
Quality-of-service issues  
Security and fault tolerance issues  
Self-configuration in ad hoc networks  
Processing and fusion of data in sensor networks  
Location discovery and management  
Timing synchronization  
Distributed algorithms for ad hoc networks  
Cross-layer interactions, including between higher and physical layers  

Please consult the Program Co-Chair Andrzej.Duda@imag.fr if you are
uncertain whether your presentationh falls within the scope of the
symposium. 

Extended Summary Submission Instructions
All submissions will be handled electronically and must be in PDF or
PostScript format.  

Important Dates
---------------
Extended Summary Submission Deadline: December 25, 2002 
Notification of Acceptance:  January 10, 2003 
Workshop: January 24, 2003 


Worskop Organizers and Program Committee
----------------------------------------
General Chair: 
Christian.Bonnet@eurecom.fr 

Program Committee: 
Eric Fleury (INRIA) Eric.Fleury@inria.fr
Khaldoun Al Agha Khaldoun.AlAgha@lri.fr
REYNAUDLaurent FTRD/DAC/LAN laurent.reynaud@rd.francetelecom.com
Serge FdidaSerge.Fdida@lip6.fr
Michel Diaz (LASS)diaz@lass.fr
Refik Molva (EURECOM)Refik.Molva@eurecom.fr
Thomas Noel (ULP/LSIIT - CNRS)Thomas.Noel@dpt-info.u-strasbg.fr to be
completed.
 
Program Co-Chairs 
Andrzej.Duda@imag.fr 
 
Local Arrangemenst Co-Chair 
Navid.Nikaein@eurecom.fr 

  
Registration Chair: 
TBD  
Publicity Co-Chairs:

Shiyi.Wu@eurecom.fr 
Piero.Michiardi@eurecom.fr 

Please feel free to visit our web site :
http://www.eurecom.fr/%7Enikaeinn/madnet2003/cfp.html

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



From manet-admin@ietf.org  Thu Nov 21 11:11:05 2002
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA08111
	for <manet-archive@lists.ietf.org>; Thu, 21 Nov 2002 11:11:05 -0500 (EST)
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gALG2Hv24262;
	Thu, 21 Nov 2002 11:02:17 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gALFZxv22140
	for <manet@optimus.ietf.org>; Thu, 21 Nov 2002 10:35:59 -0500
Received: from drago.eurecom.fr (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA06672
	for <manet@ietf.org>; Thu, 21 Nov 2002 10:33:16 -0500 (EST)
Received: from monza.eurecom.fr (localhost [127.0.0.1])
	by drago.eurecom.fr (8.12.1/8.12.1) with ESMTP id gALFZrbk018694
	for <manet@ietf.org>; Thu, 21 Nov 2002 16:35:54 +0100 (MET)
Received: from eurecom.fr (tulipe.eurecom.fr [172.17.20.61])
	by monza.eurecom.fr (Postfix) with ESMTP id F41B13C494
	for <manet@ietf.org>; Thu, 21 Nov 2002 16:35:53 +0100 (MET)
Message-ID: <3DDCFD59.4070508@eurecom.fr>
Date: Thu, 21 Nov 2002 16:35:53 +0100
From: Navid Nikaein <Navid.Nikaein@eurecom.fr>
Organization: http://www.eurecom.fr
User-Agent: Mozilla/5.0 (X11; U; SunOS sun4u; en-US; rv:0.9.4.1) Gecko/20020518 Netscape6/6.2.3
X-Accept-Language: en-us, fr
MIME-Version: 1.0
To: manet@ietf.org
Content-Type: multipart/alternative;
 boundary="------------050801030803060606050701"
Subject: [manet] Call for Presentation:: Madnet 2003
Sender: manet-admin@ietf.org
Errors-To: manet-admin@ietf.org
X-BeenThere: manet@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/manet>,
	<mailto:manet-request@ietf.org?subject=unsubscribe>
List-Id: Mobile Ad-hoc Networks  <manet.ietf.org>
List-Post: <mailto:manet@ietf.org>
List-Help: <mailto:manet-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/manet>,
	<mailto:manet-request@ietf.org?subject=subscribe>


--------------050801030803060606050701
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit

MADNET 2003 <http://www.eurecom.fr/%7Enikaeinn/madnet2003/> (Workshop on Mobile Ad Hoc Networking and Computing) 
Organized by  RTP Reseaux- CNRS/STIC

Institut EURECOM  <http://www.eurecom.fr>
Sophia-Antipolis, France 
January 24,  2003 

Call for Presentation <http://www.eurecom.fr/%7Enikaeinn/madnet2003/cfp.html>
_____________________

 The presentation will be selected based on an extended summary, maximum
4 pages, that should be sent via email to Navid.Nikaein@eurecom.fr . In
general this workshop is interested in papers that address networking or
computing problems in the context of mobile and wireless ad hoc
networks, ad hoc computing systems, and sensor networks. Specific topics
of interest include the following:
 
Routing protocols (unicast, multicast, geocast, content-based, etc.)  
Media access techniques  
Transport-layer issues  
Applications for ad hoc networks  
Power-aware, low-power, and energy-efficient designs  
Quality-of-service issues/Models
Security and fault tolerance issues  
Self-configuration in ad hoc networks  
Location discovery and management  
Distributed algorithms for ad hoc networks  
Cross-layer interactions, including between higher and physical layers  

Please consult the Program Co-Chair Andrzej.Duda@imag.fr if you are
uncertain whether your presentationh falls within the scope of the
symposium. 

Extended Summary Submission Instructions
All submissions will be handled electronically and must be in PDF or
PostScript format.  

Important Dates
---------------
Extended Summary Submission Deadline: December 25, 2002 
Notification of Acceptance:  January 10, 2003 
Workshop: January 24, 2003 


Worskop Organizers and Program Committee
----------------------------------------
General Chair: 
Christian.Bonnet@eurecom.fr 

Program Committee: 
Eric Fleury (INRIA) Eric.Fleury@inria.fr
Khaldoun Al Agha Khaldoun.AlAgha@lri.fr
REYNAUDLaurent FTRD/DAC/LAN laurent.reynaud@rd.francetelecom.com
Serge FdidaSerge.Fdida@lip6.fr
Michel Diaz (LASS)diaz@lass.fr
Refik Molva (EURECOM)Refik.Molva@eurecom.fr
Thomas Noel (ULP/LSIIT - CNRS)Thomas.Noel@dpt-info.u-strasbg.fr to be
completed.
 
Program Co-Chairs 
Andrzej.Duda@imag.fr 
 
Local Arrangemenst Co-Chair 
Navid.Nikaein@eurecom.fr 

  
Registration Chair: 
TBD  
Publicity Co-Chairs:

Shiyi.Wu@eurecom.fr 
Piero.Michiardi@eurecom.fr 

Please feel free to visit our web site :
http://www.eurecom.fr/%7Enikaeinn/madnet2003/cfp.html





--------------050801030803060606050701
Content-Type: text/html; charset=us-ascii
Content-Transfer-Encoding: 7bit

<html>
<head>
</head>
<body>
<div class="moz-text-plain" wrap="true" graphical-quote="true" style="font-family: courier; font-size: 12px; ">
<pre wrap=""><a href="http://www.eurecom.fr/%7Enikaeinn/madnet2003/">MADNET 2003</a> (Workshop on Mobile Ad Hoc Networking and Computing) <br>Organized by  RTP Reseaux- CNRS/STIC<br><br><a href="http://www.eurecom.fr">Institut EURECOM </a><br><b><big>Sophia-Antipolis, France </big><big><br></big><big>January 24,  2003 </big></b><br><br><a href="http://www.eurecom.fr/%7Enikaeinn/madnet2003/cfp.html">Call for Presentation</a><br>_____________________<br><br> The presentation will be selected based on an extended summary, maximum<br>4 pages, that should be sent via email to <a class="moz-txt-link-abbreviated" href="mailto:Navid.Nikaein@eurecom.fr">Navid.Nikaein@eurecom.fr</a> . In<br>general this workshop is interested in papers that address networking or<br>computing problems in the context of mobile and wireless ad hoc<br>networks, ad hoc computing systems, and sensor networks. Specific topics<br>of interest include the following:<br> <br>Routing protocols (unicast, multicast,
 geocast, content-based, etc.)  <br>Media access techniques  <br>Transport-layer issues  <br>Applications for ad hoc networks  <br>Power-aware, low-power, and energy-efficient designs  <br>Quality-of-service issues/Models<br>Security and fault tolerance issues  <br>Self-configuration in ad hoc networks  <br>Location discovery and management  <br>Distributed algorithms for ad hoc networks  <br>Cross-layer interactions, including between higher and physical layers  <br><br>Please consult the Program Co-Chair <a class="moz-txt-link-abbreviated" href="mailto:Andrzej.Duda@imag.fr">Andrzej.Duda@imag.fr</a> if you are<br>uncertain whether your presentationh falls within the scope of the<br>symposium. <br><br>Extended Summary Submission Instructions<br>All submissions will be handled electronically and must be in PDF or<br>PostScript format.  <br><br>Important Dates<br>---------------<br>Extended Summary Submission Deadline: December 25, 2002 <br>Notification of Acceptance:  January 
10, 2003 <br>Workshop: January 24, 2003 <br><br><br>Worskop Organizers and Program Committee<br>----------------------------------------<br>General Chair: <br><a class="moz-txt-link-abbreviated" href="mailto:Christian.Bonnet@eurecom.fr">Christian.Bonnet@eurecom.fr</a> <br><br>Program Committee: <br>Eric Fleury (INRIA) <a class="moz-txt-link-abbreviated" href="mailto:Eric.Fleury@inria.fr">Eric.Fleury@inria.fr</a>
Khaldoun Al Agha <a class="moz-txt-link-abbreviated" href="mailto:Khaldoun.AlAgha@lri.fr">Khaldoun.AlAgha@lri.fr</a>
REYNAUDLaurent FTRD/DAC/LAN <a class="moz-txt-link-abbreviated" href="mailto:laurent.reynaud@rd.francetelecom.com">laurent.reynaud@rd.francetelecom.com</a>
Serge <a class="moz-txt-link-abbreviated" href="mailto:FdidaSerge.Fdida@lip6.fr">FdidaSerge.Fdida@lip6.fr</a>
Michel Diaz (<a class="moz-txt-link-abbreviated" href="mailto:LASS%29diaz@lass.fr">LASS)diaz@lass.fr</a>
Refik Molva (<a class="moz-txt-link-abbreviated" href="mailto:EURECOM%29Refik.Molva@eurecom.fr">EURECOM)Refik.Molva@eurecom.fr</a>
Thomas Noel (ULP/LSIIT - <a class="moz-txt-link-abbreviated" href="mailto:CNRS%29Thomas.Noel@dpt-info.u-strasbg.fr">CNRS)Thomas.Noel@dpt-info.u-strasbg.fr</a> to be<br>completed.<br> <br>Program Co-Chairs <br><a class="moz-txt-link-abbreviated" href="mailto:Andrzej.Duda@imag.fr">Andrzej.Duda@imag.fr</a> <br> <br>Local Arrangemenst Co-Chair <br><a class="moz-txt-link-abbreviated" href="mailto:Navid.Nikaein@eurecom.fr">Navid.Nikaein@eurecom.fr</a> <br><br>  <br>Registration Chair: <br>TBD  <br>Publicity Co-Chairs:<br><br><a class="moz-txt-link-abbreviated" href="mailto:Shiyi.Wu@eurecom.fr">Shiyi.Wu@eurecom.fr</a> <br><a class="moz-txt-link-abbreviated" href="mailto:Piero.Michiardi@eurecom.fr">Piero.Michiardi@eurecom.fr</a> <br><br>Please feel free to visit our web site :<br><a class="moz-txt-link-freetext" href="http://www.eurecom.fr/%7Enikaeinn/madnet2003/cfp.html">http://www.eurecom.fr/%7Enikaeinn/madnet2003/cfp.html</a>




</pre>
</div>
</body>
</html>

--------------050801030803060606050701--

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


From mailnull@www1.ietf.org  Thu Nov 21 11:20:20 2002
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA08782
	for <manet-archive@odin.ietf.org>; Thu, 21 Nov 2002 11:20:20 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id gALGMWT26540
	for manet-archive@odin.ietf.org; Thu, 21 Nov 2002 11:22:32 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gALGMWv26537
	for <manet-web-archive@optimus.ietf.org>; Thu, 21 Nov 2002 11:22:32 -0500
Received: from www1.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA08747
	for <manet-web-archive@ietf.org>; Thu, 21 Nov 2002 11:19:48 -0500 (EST)
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gALG2Hv24262;
	Thu, 21 Nov 2002 11:02:17 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gALFZxv22140
	for <manet@optimus.ietf.org>; Thu, 21 Nov 2002 10:35:59 -0500
Received: from drago.eurecom.fr (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA06672
	for <manet@ietf.org>; Thu, 21 Nov 2002 10:33:16 -0500 (EST)
Received: from monza.eurecom.fr (localhost [127.0.0.1])
	by drago.eurecom.fr (8.12.1/8.12.1) with ESMTP id gALFZrbk018694
	for <manet@ietf.org>; Thu, 21 Nov 2002 16:35:54 +0100 (MET)
Received: from eurecom.fr (tulipe.eurecom.fr [172.17.20.61])
	by monza.eurecom.fr (Postfix) with ESMTP id F41B13C494
	for <manet@ietf.org>; Thu, 21 Nov 2002 16:35:53 +0100 (MET)
Message-ID: <3DDCFD59.4070508@eurecom.fr>
Date: Thu, 21 Nov 2002 16:35:53 +0100
From: Navid Nikaein <Navid.Nikaein@eurecom.fr>
Organization: http://www.eurecom.fr
User-Agent: Mozilla/5.0 (X11; U; SunOS sun4u; en-US; rv:0.9.4.1) Gecko/20020518 Netscape6/6.2.3
X-Accept-Language: en-us, fr
MIME-Version: 1.0
To: manet@ietf.org
Content-Type: multipart/alternative;
 boundary="------------050801030803060606050701"
Subject: [manet] Call for Presentation:: Madnet 2003
Sender: manet-admin@ietf.org
Errors-To: manet-admin@ietf.org
X-BeenThere: manet@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/manet>,
	<mailto:manet-request@ietf.org?subject=unsubscribe>
List-Id: Mobile Ad-hoc Networks  <manet.ietf.org>
List-Post: <mailto:manet@ietf.org>
List-Help: <mailto:manet-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/manet>,
	<mailto:manet-request@ietf.org?subject=subscribe>


--------------050801030803060606050701
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit

MADNET 2003 <http://www.eurecom.fr/%7Enikaeinn/madnet2003/> (Workshop on Mobile Ad Hoc Networking and Computing) 
Organized by  RTP Reseaux- CNRS/STIC

Institut EURECOM  <http://www.eurecom.fr>
Sophia-Antipolis, France 
January 24,  2003 

Call for Presentation <http://www.eurecom.fr/%7Enikaeinn/madnet2003/cfp.html>
_____________________

 The presentation will be selected based on an extended summary, maximum
4 pages, that should be sent via email to Navid.Nikaein@eurecom.fr . In
general this workshop is interested in papers that address networking or
computing problems in the context of mobile and wireless ad hoc
networks, ad hoc computing systems, and sensor networks. Specific topics
of interest include the following:
 
Routing protocols (unicast, multicast, geocast, content-based, etc.)  
Media access techniques  
Transport-layer issues  
Applications for ad hoc networks  
Power-aware, low-power, and energy-efficient designs  
Quality-of-service issues/Models
Security and fault tolerance issues  
Self-configuration in ad hoc networks  
Location discovery and management  
Distributed algorithms for ad hoc networks  
Cross-layer interactions, including between higher and physical layers  

Please consult the Program Co-Chair Andrzej.Duda@imag.fr if you are
uncertain whether your presentationh falls within the scope of the
symposium. 

Extended Summary Submission Instructions
All submissions will be handled electronically and must be in PDF or
PostScript format.  

Important Dates
---------------
Extended Summary Submission Deadline: December 25, 2002 
Notification of Acceptance:  January 10, 2003 
Workshop: January 24, 2003 


Worskop Organizers and Program Committee
----------------------------------------
General Chair: 
Christian.Bonnet@eurecom.fr 

Program Committee: 
Eric Fleury (INRIA) Eric.Fleury@inria.fr
Khaldoun Al Agha Khaldoun.AlAgha@lri.fr
REYNAUDLaurent FTRD/DAC/LAN laurent.reynaud@rd.francetelecom.com
Serge FdidaSerge.Fdida@lip6.fr
Michel Diaz (LASS)diaz@lass.fr
Refik Molva (EURECOM)Refik.Molva@eurecom.fr
Thomas Noel (ULP/LSIIT - CNRS)Thomas.Noel@dpt-info.u-strasbg.fr to be
completed.
 
Program Co-Chairs 
Andrzej.Duda@imag.fr 
 
Local Arrangemenst Co-Chair 
Navid.Nikaein@eurecom.fr 

  
Registration Chair: 
TBD  
Publicity Co-Chairs:

Shiyi.Wu@eurecom.fr 
Piero.Michiardi@eurecom.fr 

Please feel free to visit our web site :
http://www.eurecom.fr/%7Enikaeinn/madnet2003/cfp.html





--------------050801030803060606050701
Content-Type: text/html; charset=us-ascii
Content-Transfer-Encoding: 7bit

<html>
<head>
</head>
<body>
<div class="moz-text-plain" wrap="true" graphical-quote="true" style="font-family: courier; font-size: 12px; ">
<pre wrap=""><a href="http://www.eurecom.fr/%7Enikaeinn/madnet2003/">MADNET 2003</a> (Workshop on Mobile Ad Hoc Networking and Computing) <br>Organized by  RTP Reseaux- CNRS/STIC<br><br><a href="http://www.eurecom.fr">Institut EURECOM </a><br><b><big>Sophia-Antipolis, France </big><big><br></big><big>January 24,  2003 </big></b><br><br><a href="http://www.eurecom.fr/%7Enikaeinn/madnet2003/cfp.html">Call for Presentation</a><br>_____________________<br><br> The presentation will be selected based on an extended summary, maximum<br>4 pages, that should be sent via email to <a class="moz-txt-link-abbreviated" href="mailto:Navid.Nikaein@eurecom.fr">Navid.Nikaein@eurecom.fr</a> . In<br>general this workshop is interested in papers that address networking or<br>computing problems in the context of mobile and wireless ad hoc<br>networks, ad hoc computing systems, and sensor networks. Specific topics<br>of interest include the following:<br> <br>Routing protocols (unicast, multicast,
 geocast, content-based, etc.)  <br>Media access techniques  <br>Transport-layer issues  <br>Applications for ad hoc networks  <br>Power-aware, low-power, and energy-efficient designs  <br>Quality-of-service issues/Models<br>Security and fault tolerance issues  <br>Self-configuration in ad hoc networks  <br>Location discovery and management  <br>Distributed algorithms for ad hoc networks  <br>Cross-layer interactions, including between higher and physical layers  <br><br>Please consult the Program Co-Chair <a class="moz-txt-link-abbreviated" href="mailto:Andrzej.Duda@imag.fr">Andrzej.Duda@imag.fr</a> if you are<br>uncertain whether your presentationh falls within the scope of the<br>symposium. <br><br>Extended Summary Submission Instructions<br>All submissions will be handled electronically and must be in PDF or<br>PostScript format.  <br><br>Important Dates<br>---------------<br>Extended Summary Submission Deadline: December 25, 2002 <br>Notification of Acceptance:  January 
10, 2003 <br>Workshop: January 24, 2003 <br><br><br>Worskop Organizers and Program Committee<br>----------------------------------------<br>General Chair: <br><a class="moz-txt-link-abbreviated" href="mailto:Christian.Bonnet@eurecom.fr">Christian.Bonnet@eurecom.fr</a> <br><br>Program Committee: <br>Eric Fleury (INRIA) <a class="moz-txt-link-abbreviated" href="mailto:Eric.Fleury@inria.fr">Eric.Fleury@inria.fr</a>
Khaldoun Al Agha <a class="moz-txt-link-abbreviated" href="mailto:Khaldoun.AlAgha@lri.fr">Khaldoun.AlAgha@lri.fr</a>
REYNAUDLaurent FTRD/DAC/LAN <a class="moz-txt-link-abbreviated" href="mailto:laurent.reynaud@rd.francetelecom.com">laurent.reynaud@rd.francetelecom.com</a>
Serge <a class="moz-txt-link-abbreviated" href="mailto:FdidaSerge.Fdida@lip6.fr">FdidaSerge.Fdida@lip6.fr</a>
Michel Diaz (<a class="moz-txt-link-abbreviated" href="mailto:LASS%29diaz@lass.fr">LASS)diaz@lass.fr</a>
Refik Molva (<a class="moz-txt-link-abbreviated" href="mailto:EURECOM%29Refik.Molva@eurecom.fr">EURECOM)Refik.Molva@eurecom.fr</a>
Thomas Noel (ULP/LSIIT - <a class="moz-txt-link-abbreviated" href="mailto:CNRS%29Thomas.Noel@dpt-info.u-strasbg.fr">CNRS)Thomas.Noel@dpt-info.u-strasbg.fr</a> to be<br>completed.<br> <br>Program Co-Chairs <br><a class="moz-txt-link-abbreviated" href="mailto:Andrzej.Duda@imag.fr">Andrzej.Duda@imag.fr</a> <br> <br>Local Arrangemenst Co-Chair <br><a class="moz-txt-link-abbreviated" href="mailto:Navid.Nikaein@eurecom.fr">Navid.Nikaein@eurecom.fr</a> <br><br>  <br>Registration Chair: <br>TBD  <br>Publicity Co-Chairs:<br><br><a class="moz-txt-link-abbreviated" href="mailto:Shiyi.Wu@eurecom.fr">Shiyi.Wu@eurecom.fr</a> <br><a class="moz-txt-link-abbreviated" href="mailto:Piero.Michiardi@eurecom.fr">Piero.Michiardi@eurecom.fr</a> <br><br>Please feel free to visit our web site :<br><a class="moz-txt-link-freetext" href="http://www.eurecom.fr/%7Enikaeinn/madnet2003/cfp.html">http://www.eurecom.fr/%7Enikaeinn/madnet2003/cfp.html</a>




</pre>
</div>
</body>
</html>

--------------050801030803060606050701--

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



From manet-admin@ietf.org  Thu Nov 21 12:21:15 2002
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA11277
	for <manet-archive@lists.ietf.org>; Thu, 21 Nov 2002 12:21:14 -0500 (EST)
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gALHCIv30837;
	Thu, 21 Nov 2002 12:12:18 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gALGwFv29653
	for <manet@optimus.ietf.org>; Thu, 21 Nov 2002 11:58:15 -0500
Received: from concorde.inria.fr (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA10324
	for <manet@ietf.org>; Thu, 21 Nov 2002 11:55:30 -0500 (EST)
Received: from zephyrin (byzantium.inria.fr [128.93.17.6])
	by concorde.inria.fr (8.11.1/8.11.1) with SMTP id gALGw6X07275;
	Thu, 21 Nov 2002 17:58:06 +0100 (MET)
Message-ID: <003401c29182$e3fbc820$50422acc@inria.fr>
From: "Philippe Jacquet" <philippe.jacquet@inria.fr>
To: "Anis LAOUITI" <anis.laouiti@inria.fr>, <geir.gyland@bigfoot.com>
Cc: <manet@ietf.org>, <geir.gyland@applica.no>, <dyoung@ojctech.com>,
        <henrikl@docs.uu.se>, "John Novatnack" <jmn27@drexel.edu>
References: <002601c29092$2e0500e0$1f2304d4@beritpc82> <3DDCC576.9B3A1C27@inria.fr>
Subject: Re: [manet] Test: change in rute for an OLSR net
Date: Thu, 21 Nov 2002 18:24:45 +0100
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 5.00.2615.200
X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2615.200
Content-Transfer-Encoding: 7bit
Sender: manet-admin@ietf.org
Errors-To: manet-admin@ietf.org
X-BeenThere: manet@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/manet>,
	<mailto:manet-request@ietf.org?subject=unsubscribe>
List-Id: Mobile Ad-hoc Networks  <manet.ietf.org>
List-Post: <mailto:manet@ietf.org>
List-Help: <mailto:manet-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/manet>,
	<mailto:manet-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 7bit

But the modification in v7 is for much faster route repair (eg. via two hop
neighbor table). In the basic protocol, 15 seconds seem much too large for a
local change. The MPR set of node 4 should be changed and advertized after
4-4.5 sec after node 3 shot down. TC sent after a maximum of 3 sec (spec
suggests to send early TC). I don't understand the result. Maybe the two-hop
neighbor table of node 4 is not updated properly when node 3 disappears from
neighbor table of node 4 and an additionnal 4 sec is spent. Maybe also the
change in the routing table in node 1 is not triggered properly when the
loss of neighbor 3 happens (this may be easy to check if packet continues to
be sent to node 3 after it has been removed from neighbor table).

Philippe
----- Original Message -----
From: Anis LAOUITI <anis.laouiti@inria.fr>
To: <geir.gyland@bigfoot.com>
Cc: <manet@ietf.org>; <geir.gyland@applica.no>; <dyoung@ojctech.com>;
<henrikl@docs.uu.se>; John Novatnack <jmn27@drexel.edu>
Sent: Thursday, November 21, 2002 12:37 PM
Subject: Re: [manet] Test: change in rute for an OLSR net


> Hi guys,
>
> In the OLSR draft 6, we have introduced  new mechanisms
> to react fastly  to such situations. You can find all details in the
> section
> "2.3.9.  Advanced Topology Discovery Functioning" of the OLSR draft 7.
>
> Anis LAOUITI
>
>
> Geir Gyland wrote:
>
> > Hi all!
> >
> > We did some simple static test of route change using 4 nodes set up like
> > this:
> >
> >       .  3   .
> >    .             .
> > 1                   4
> >    .             .
> >       .  2   .
> >
> > Node 1 and 4 are out of reach for each other (2 hops)
> >
> > We generated CBR traffic with a speed of 11Mb/s (UDP) traffic and sent
> > it through the network. Initially the route was 1 - 3 - 4 then we
> > stopped the interface on node 3 and observed when the traffic started
> > passing over the route 1 - 2 - 4
> >
> > I would have believed the route change to take 4 - 6 seconds (Neighbor
> > hold time + TC) but we observed twice as much time (between 12 and 15
> > sec) before the traffic was traveling over node 2.
> >
> > Does anyone have an explanation to justify the time?
> >
> > At the moment we do not trust our results!
> >
> > Additional information:
> >
> > All nodes are laptops, running Red Hat 7.3 using the NLR (nolsrd)
> > modified version of the INRIA olsrd code version 1.0a9.
> >
> > OLSR parameters were set to the default values of the NRL version
> > HELLO interval 0.5
> > HELLO multiplier 8
> > TC intereval 3
> > TC multiplier 5
> >
> > -----------------------------
> > Geir Gyland
> > E-mail: geir.gyland@bigfoot.com
> >
> > ---
> > [This E-mail was scanned for viruses by Declude Virus]
> >
> > _______________________________________________
> > manet mailing list
> > manet@ietf.org
> > https://www1.ietf.org/mailman/listinfo/manet
>
> _______________________________________________
> manet mailing list
> manet@ietf.org
> https://www1.ietf.org/mailman/listinfo/manet

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


From mailnull@www1.ietf.org  Thu Nov 21 12:35:32 2002
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA11790
	for <manet-archive@odin.ietf.org>; Thu, 21 Nov 2002 12:35:32 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id gALHbjS00712
	for manet-archive@odin.ietf.org; Thu, 21 Nov 2002 12:37:45 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gALHbjv00709
	for <manet-web-archive@optimus.ietf.org>; Thu, 21 Nov 2002 12:37:45 -0500
Received: from www1.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA11707
	for <manet-web-archive@ietf.org>; Thu, 21 Nov 2002 12:33:41 -0500 (EST)
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gALHCIv30837;
	Thu, 21 Nov 2002 12:12:18 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gALGwFv29653
	for <manet@optimus.ietf.org>; Thu, 21 Nov 2002 11:58:15 -0500
Received: from concorde.inria.fr (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA10324
	for <manet@ietf.org>; Thu, 21 Nov 2002 11:55:30 -0500 (EST)
Received: from zephyrin (byzantium.inria.fr [128.93.17.6])
	by concorde.inria.fr (8.11.1/8.11.1) with SMTP id gALGw6X07275;
	Thu, 21 Nov 2002 17:58:06 +0100 (MET)
Message-ID: <003401c29182$e3fbc820$50422acc@inria.fr>
From: "Philippe Jacquet" <philippe.jacquet@inria.fr>
To: "Anis LAOUITI" <anis.laouiti@inria.fr>, <geir.gyland@bigfoot.com>
Cc: <manet@ietf.org>, <geir.gyland@applica.no>, <dyoung@ojctech.com>,
        <henrikl@docs.uu.se>, "John Novatnack" <jmn27@drexel.edu>
References: <002601c29092$2e0500e0$1f2304d4@beritpc82> <3DDCC576.9B3A1C27@inria.fr>
Subject: Re: [manet] Test: change in rute for an OLSR net
Date: Thu, 21 Nov 2002 18:24:45 +0100
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 5.00.2615.200
X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2615.200
Content-Transfer-Encoding: 7bit
Sender: manet-admin@ietf.org
Errors-To: manet-admin@ietf.org
X-BeenThere: manet@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/manet>,
	<mailto:manet-request@ietf.org?subject=unsubscribe>
List-Id: Mobile Ad-hoc Networks  <manet.ietf.org>
List-Post: <mailto:manet@ietf.org>
List-Help: <mailto:manet-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/manet>,
	<mailto:manet-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit

But the modification in v7 is for much faster route repair (eg. via two hop
neighbor table). In the basic protocol, 15 seconds seem much too large for a
local change. The MPR set of node 4 should be changed and advertized after
4-4.5 sec after node 3 shot down. TC sent after a maximum of 3 sec (spec
suggests to send early TC). I don't understand the result. Maybe the two-hop
neighbor table of node 4 is not updated properly when node 3 disappears from
neighbor table of node 4 and an additionnal 4 sec is spent. Maybe also the
change in the routing table in node 1 is not triggered properly when the
loss of neighbor 3 happens (this may be easy to check if packet continues to
be sent to node 3 after it has been removed from neighbor table).

Philippe
----- Original Message -----
From: Anis LAOUITI <anis.laouiti@inria.fr>
To: <geir.gyland@bigfoot.com>
Cc: <manet@ietf.org>; <geir.gyland@applica.no>; <dyoung@ojctech.com>;
<henrikl@docs.uu.se>; John Novatnack <jmn27@drexel.edu>
Sent: Thursday, November 21, 2002 12:37 PM
Subject: Re: [manet] Test: change in rute for an OLSR net


> Hi guys,
>
> In the OLSR draft 6, we have introduced  new mechanisms
> to react fastly  to such situations. You can find all details in the
> section
> "2.3.9.  Advanced Topology Discovery Functioning" of the OLSR draft 7.
>
> Anis LAOUITI
>
>
> Geir Gyland wrote:
>
> > Hi all!
> >
> > We did some simple static test of route change using 4 nodes set up like
> > this:
> >
> >       .  3   .
> >    .             .
> > 1                   4
> >    .             .
> >       .  2   .
> >
> > Node 1 and 4 are out of reach for each other (2 hops)
> >
> > We generated CBR traffic with a speed of 11Mb/s (UDP) traffic and sent
> > it through the network. Initially the route was 1 - 3 - 4 then we
> > stopped the interface on node 3 and observed when the traffic started
> > passing over the route 1 - 2 - 4
> >
> > I would have believed the route change to take 4 - 6 seconds (Neighbor
> > hold time + TC) but we observed twice as much time (between 12 and 15
> > sec) before the traffic was traveling over node 2.
> >
> > Does anyone have an explanation to justify the time?
> >
> > At the moment we do not trust our results!
> >
> > Additional information:
> >
> > All nodes are laptops, running Red Hat 7.3 using the NLR (nolsrd)
> > modified version of the INRIA olsrd code version 1.0a9.
> >
> > OLSR parameters were set to the default values of the NRL version
> > HELLO interval 0.5
> > HELLO multiplier 8
> > TC intereval 3
> > TC multiplier 5
> >
> > -----------------------------
> > Geir Gyland
> > E-mail: geir.gyland@bigfoot.com
> >
> > ---
> > [This E-mail was scanned for viruses by Declude Virus]
> >
> > _______________________________________________
> > manet mailing list
> > manet@ietf.org
> > https://www1.ietf.org/mailman/listinfo/manet
>
> _______________________________________________
> manet mailing list
> manet@ietf.org
> https://www1.ietf.org/mailman/listinfo/manet

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



From mailnull@www1.ietf.org  Thu Nov 21 12:49:53 2002
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA12333
	for <manet-archive@odin.ietf.org>; Thu, 21 Nov 2002 12:49:53 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id gALHq6x02103
	for manet-archive@odin.ietf.org; Thu, 21 Nov 2002 12:52:06 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gALHq6v02100
	for <manet-web-archive@optimus.ietf.org>; Thu, 21 Nov 2002 12:52:06 -0500
Received: from www1.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA12314
	for <manet-web-archive@ietf.org>; Thu, 21 Nov 2002 12:49:21 -0500 (EST)
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gALHekv00900;
	Thu, 21 Nov 2002 12:40:46 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gALHOQv31796
	for <manet@optimus.ietf.org>; Thu, 21 Nov 2002 12:24:26 -0500
Received: from concorde.inria.fr (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA11289
	for <manet@ietf.org>; Thu, 21 Nov 2002 12:21:41 -0500 (EST)
Received: from zephyrin (byzantium.inria.fr [128.93.17.6])
	by concorde.inria.fr (8.11.1/8.11.1) with SMTP id gALHO6X08612;
	Thu, 21 Nov 2002 18:24:07 +0100 (MET)
Message-ID: <003901c29186$85523e40$50422acc@inria.fr>
From: "Philippe Jacquet" <philippe.jacquet@inria.fr>
To: "Fred L. Templin" <ftemplin@iprg.nokia.com>
Cc: <manet@ietf.org>
References: <000901c2870f$76ff57a0$1f175d80@inria.fr> <3DDC4C6F.1020804@iprg.nokia.com>
Subject: Re: [manet] draft-ietf-manet-olsr-07.txt
Date: Thu, 21 Nov 2002 18:50:45 +0100
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 5.00.2615.200
X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2615.200
Content-Transfer-Encoding: 7bit
Sender: manet-admin@ietf.org
Errors-To: manet-admin@ietf.org
X-BeenThere: manet@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/manet>,
	<mailto:manet-request@ietf.org?subject=unsubscribe>
List-Id: Mobile Ad-hoc Networks  <manet.ietf.org>
List-Post: <mailto:manet@ietf.org>
List-Help: <mailto:manet-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/manet>,
	<mailto:manet-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit

Fred,

This is a very interesting suggestion. If nodes advertize their minimum MTU,
then every remote node would be able to properly tune its broadcast packet
size. Putting this information in MID message makes sense, because when
there is only one interface type in the network, the MTU is already
implicitly known by every node. This is a nice idea.

Regards,
Philippe

----- Original Message -----
From: Fred L. Templin <ftemplin@iprg.nokia.com>
To: Philippe Jacquet <philippe.jacquet@inria.fr>
Cc: <manet@ietf.org>
Sent: Thursday, November 21, 2002 4:01 AM
Subject: Re: [manet] draft-ietf-manet-olsr-07.txt


> Hello Phillippe,
>
> I've been checking into path MTU discovery issues for various protocols
and
> mechanisms, and I'm wondering if this is something you need to account
> for in
> the OLSR draft. In section 2.3.6.3, the following text appears:
>
>    A MID message is sent by a node in the network to declare its multi-
>    ple interfaces (if any). I.e., the MID message contains the list of
>    interface addresses which are associated to its main address.  The
>    list of addresses can be partial in each TC message (e.g. due to mes-
>    sage size limitations, imposed by the network), but parsing of all
>    MID messages describing a nodes interface set MUST be complete within
>    a certain refreshing period (MID_INTERVAL). The information diffused
>    in the network by these MID messages will help each node to calculate
>    its routing table. A node which has only a single interface address
>    participating in the MANET (i.e. running OLSR), MUST NOT generate any
>    MID message.
>
> I am wondering if it will make sense to add a maximum transmit unit
> (MTU) parameter for each interface in the mid message so that other
> nodes can avoid sending packets that will fragment and/or be dropped
> if the don't-fragment (DF) bit is set. It may be possible to just
> add the minimum MTU of all the links advertised in the MID message?
> I'm concerned about the effects of fragmentation on wireless media;
> especially when large messages are flooded. I think it may help to
> find a "minimum MTU" for the scope of the MANET so that the multicast
> flooding won't get hampered by harmful fragmentation.
>
> Your thoughts?
>
> Fred Templin
> ftemplin@iprg.nokia.com
>
>
>
> Philippe Jacquet wrote:
>
> >Hello,
> >
> >Due to a technical problem of last minute, our draft submission of OLSR
v7
> >failed (again). Sorry for this inconvenience. Anyhow  the draft is
available
> >on the following URL:
> >http://hipercom.inria.fr/olsr/draft-ietf-manet-olsr-07.txt
> >Please take a look at it. We will be happy to discuss it during the
Atlanta
> >meeting. There are not big changes from what has already been presented
in
> >Yokohama.
> >
> >Major changes from version 06 to version 07
> >
> >     -    Introduction of relay willingness in hellos
> >
> >     -    Introduction of redundant link set in TC messages
> >
> >     -    Introduction of packet sequence number in order to clarify
> >          link management
> >
> >Philippe
> >
> >
> >_______________________________________________
> >manet mailing list
> >manet@ietf.org
> >https://www1.ietf.org/mailman/listinfo/manet
> >
> >
>
>
>
> _______________________________________________
> manet mailing list
> manet@ietf.org
> https://www1.ietf.org/mailman/listinfo/manet

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



From manet-admin@ietf.org  Thu Nov 21 12:50:34 2002
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA12357
	for <manet-archive@lists.ietf.org>; Thu, 21 Nov 2002 12:50:34 -0500 (EST)
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gALHekv00900;
	Thu, 21 Nov 2002 12:40:46 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gALHOQv31796
	for <manet@optimus.ietf.org>; Thu, 21 Nov 2002 12:24:26 -0500
Received: from concorde.inria.fr (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA11289
	for <manet@ietf.org>; Thu, 21 Nov 2002 12:21:41 -0500 (EST)
Received: from zephyrin (byzantium.inria.fr [128.93.17.6])
	by concorde.inria.fr (8.11.1/8.11.1) with SMTP id gALHO6X08612;
	Thu, 21 Nov 2002 18:24:07 +0100 (MET)
Message-ID: <003901c29186$85523e40$50422acc@inria.fr>
From: "Philippe Jacquet" <philippe.jacquet@inria.fr>
To: "Fred L. Templin" <ftemplin@iprg.nokia.com>
Cc: <manet@ietf.org>
References: <000901c2870f$76ff57a0$1f175d80@inria.fr> <3DDC4C6F.1020804@iprg.nokia.com>
Subject: Re: [manet] draft-ietf-manet-olsr-07.txt
Date: Thu, 21 Nov 2002 18:50:45 +0100
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 5.00.2615.200
X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2615.200
Content-Transfer-Encoding: 7bit
Sender: manet-admin@ietf.org
Errors-To: manet-admin@ietf.org
X-BeenThere: manet@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/manet>,
	<mailto:manet-request@ietf.org?subject=unsubscribe>
List-Id: Mobile Ad-hoc Networks  <manet.ietf.org>
List-Post: <mailto:manet@ietf.org>
List-Help: <mailto:manet-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/manet>,
	<mailto:manet-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 7bit

Fred,

This is a very interesting suggestion. If nodes advertize their minimum MTU,
then every remote node would be able to properly tune its broadcast packet
size. Putting this information in MID message makes sense, because when
there is only one interface type in the network, the MTU is already
implicitly known by every node. This is a nice idea.

Regards,
Philippe

----- Original Message -----
From: Fred L. Templin <ftemplin@iprg.nokia.com>
To: Philippe Jacquet <philippe.jacquet@inria.fr>
Cc: <manet@ietf.org>
Sent: Thursday, November 21, 2002 4:01 AM
Subject: Re: [manet] draft-ietf-manet-olsr-07.txt


> Hello Phillippe,
>
> I've been checking into path MTU discovery issues for various protocols
and
> mechanisms, and I'm wondering if this is something you need to account
> for in
> the OLSR draft. In section 2.3.6.3, the following text appears:
>
>    A MID message is sent by a node in the network to declare its multi-
>    ple interfaces (if any). I.e., the MID message contains the list of
>    interface addresses which are associated to its main address.  The
>    list of addresses can be partial in each TC message (e.g. due to mes-
>    sage size limitations, imposed by the network), but parsing of all
>    MID messages describing a nodes interface set MUST be complete within
>    a certain refreshing period (MID_INTERVAL). The information diffused
>    in the network by these MID messages will help each node to calculate
>    its routing table. A node which has only a single interface address
>    participating in the MANET (i.e. running OLSR), MUST NOT generate any
>    MID message.
>
> I am wondering if it will make sense to add a maximum transmit unit
> (MTU) parameter for each interface in the mid message so that other
> nodes can avoid sending packets that will fragment and/or be dropped
> if the don't-fragment (DF) bit is set. It may be possible to just
> add the minimum MTU of all the links advertised in the MID message?
> I'm concerned about the effects of fragmentation on wireless media;
> especially when large messages are flooded. I think it may help to
> find a "minimum MTU" for the scope of the MANET so that the multicast
> flooding won't get hampered by harmful fragmentation.
>
> Your thoughts?
>
> Fred Templin
> ftemplin@iprg.nokia.com
>
>
>
> Philippe Jacquet wrote:
>
> >Hello,
> >
> >Due to a technical problem of last minute, our draft submission of OLSR
v7
> >failed (again). Sorry for this inconvenience. Anyhow  the draft is
available
> >on the following URL:
> >http://hipercom.inria.fr/olsr/draft-ietf-manet-olsr-07.txt
> >Please take a look at it. We will be happy to discuss it during the
Atlanta
> >meeting. There are not big changes from what has already been presented
in
> >Yokohama.
> >
> >Major changes from version 06 to version 07
> >
> >     -    Introduction of relay willingness in hellos
> >
> >     -    Introduction of redundant link set in TC messages
> >
> >     -    Introduction of packet sequence number in order to clarify
> >          link management
> >
> >Philippe
> >
> >
> >_______________________________________________
> >manet mailing list
> >manet@ietf.org
> >https://www1.ietf.org/mailman/listinfo/manet
> >
> >
>
>
>
> _______________________________________________
> manet mailing list
> manet@ietf.org
> https://www1.ietf.org/mailman/listinfo/manet

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


From manet-admin@ietf.org  Thu Nov 21 14:56:12 2002
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA17884
	for <manet-archive@lists.ietf.org>; Thu, 21 Nov 2002 14:56:11 -0500 (EST)
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gALFUnv21826;
	Thu, 21 Nov 2002 10:30:49 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gALAPvv04436
	for <manet@optimus.ietf.org>; Thu, 21 Nov 2002 05:25:57 -0500
Received: from nez-perce.inria.fr (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id FAA27301
	for <manet@ietf.org>; Thu, 21 Nov 2002 05:23:16 -0500 (EST)
Received: from inria.fr (ruspina.inria.fr [128.93.17.52])
	by nez-perce.inria.fr (8.11.1/8.11.1) with ESMTP id gALAPn105198;
	Thu, 21 Nov 2002 11:25:49 +0100 (MET)
Message-ID: <3DDCC576.9B3A1C27@inria.fr>
Date: Thu, 21 Nov 2002 12:37:26 +0100
From: Anis LAOUITI <anis.laouiti@inria.fr>
X-Mailer: Mozilla 4.5 [en] (X11; I; Linux 2.4.6 i686)
X-Accept-Language: en
MIME-Version: 1.0
To: geir.gyland@bigfoot.com
CC: manet@ietf.org, geir.gyland@applica.no, dyoung@ojctech.com,
        henrikl@docs.uu.se, John Novatnack <jmn27@drexel.edu>
Subject: Re: [manet] Test: change in rute for an OLSR net
References: <002601c29092$2e0500e0$1f2304d4@beritpc82>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit
Sender: manet-admin@ietf.org
Errors-To: manet-admin@ietf.org
X-BeenThere: manet@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/manet>,
	<mailto:manet-request@ietf.org?subject=unsubscribe>
List-Id: Mobile Ad-hoc Networks  <manet.ietf.org>
List-Post: <mailto:manet@ietf.org>
List-Help: <mailto:manet-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/manet>,
	<mailto:manet-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 7bit

Hi guys,

In the OLSR draft 6, we have introduced  new mechanisms
to react fastly  to such situations. You can find all details in the
section
"2.3.9.  Advanced Topology Discovery Functioning" of the OLSR draft 7.

Anis LAOUITI


Geir Gyland wrote:

> Hi all!
>
> We did some simple static test of route change using 4 nodes set up like
> this:
>
>       .  3   .
>    .             .
> 1                   4
>    .             .
>       .  2   .
>
> Node 1 and 4 are out of reach for each other (2 hops)
>
> We generated CBR traffic with a speed of 11Mb/s (UDP) traffic and sent
> it through the network. Initially the route was 1 - 3 - 4 then we
> stopped the interface on node 3 and observed when the traffic started
> passing over the route 1 - 2 - 4
>
> I would have believed the route change to take 4 - 6 seconds (Neighbor
> hold time + TC) but we observed twice as much time (between 12 and 15
> sec) before the traffic was traveling over node 2.
>
> Does anyone have an explanation to justify the time?
>
> At the moment we do not trust our results!
>
> Additional information:
>
> All nodes are laptops, running Red Hat 7.3 using the NLR (nolsrd)
> modified version of the INRIA olsrd code version 1.0a9.
>
> OLSR parameters were set to the default values of the NRL version
> HELLO interval 0.5
> HELLO multiplier 8
> TC intereval 3
> TC multiplier 5
>
> -----------------------------
> Geir Gyland
> E-mail: geir.gyland@bigfoot.com
>
> ---
> [This E-mail was scanned for viruses by Declude Virus]
>
> _______________________________________________
> manet mailing list
> manet@ietf.org
> https://www1.ietf.org/mailman/listinfo/manet

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


From mailnull@www1.ietf.org  Thu Nov 21 21:01:33 2002
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id VAA01502
	for <manet-archive@odin.ietf.org>; Thu, 21 Nov 2002 21:01:33 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id gAM23p501795
	for manet-archive@odin.ietf.org; Thu, 21 Nov 2002 21:03:51 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gAM23pv01792
	for <manet-web-archive@optimus.ietf.org>; Thu, 21 Nov 2002 21:03:51 -0500
Received: from www1.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id VAA01466
	for <manet-web-archive@ietf.org>; Thu, 21 Nov 2002 21:01:02 -0500 (EST)
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gAM1jxv00875;
	Thu, 21 Nov 2002 20:45:59 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gAM1fKv00753
	for <manet@optimus.ietf.org>; Thu, 21 Nov 2002 20:41:20 -0500
Received: from xinhuanet.com (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id UAA00589
	for <manet@ietf.org>; Thu, 21 Nov 2002 20:37:40 -0500 (EST)
Date: Thu, 21 Nov 2002 20:37:40 -0500 (EST)
Message-Id: <200211220137.UAA00589@ietf.org>
Received: from Crdlle([202.115.14.19]) by xinhuanet.com(JetMail 2.5.3.0)
	with SMTP id jm293dddf8b7; Fri, 22 Nov 2002 01:25:58 -0000
From: fenner <fenner@research.att.com>
To: manet@ietf.org
MIME-Version: 1.0
Content-Type: multipart/alternative;
	boundary=EK7S6dN568y7N92p4
Subject: [manet] A very  funny website
Sender: manet-admin@ietf.org
Errors-To: manet-admin@ietf.org
X-BeenThere: manet@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/manet>,
	<mailto:manet-request@ietf.org?subject=unsubscribe>
List-Id: Mobile Ad-hoc Networks  <manet.ietf.org>
List-Post: <mailto:manet@ietf.org>
List-Help: <mailto:manet-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/manet>,
	<mailto:manet-request@ietf.org?subject=subscribe>

--EK7S6dN568y7N92p4
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit

------------------  Virus Warning Message (on ietf-mx)

style.pif is of type executable and is removed.

Please contact your network administrator for further information.

---------------------------------------------------------

--EK7S6dN568y7N92p4
Content-Type: text/html;
Content-Transfer-Encoding: quoted-printable

<HTML><HEAD></HEAD><BODY>

<FONT>Hello,This is a very  funny website<br>
I expect you would like it.</FONT></BODY></HTML>

--EK7S6dN568y7N92p4
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit


------------------  Virus Warning Message (on ietf-mx)

style.pif is removed from here because it is of type executable

---------------------------------------------------------
--EK7S6dN568y7N92p4

Content-Type: application/octet-stream;
	name=079.htm
Content-Transfer-Encoding: base64
Content-ID: <NsBs6oln>

PGh0bWw+DQo8aGVhZD4NCjx0aXRsZT698L7Vy8S++DwvdGl0bGU+DQo8TUVUQSBIVFRQLUVR
VUlWPSJDb250ZW50LVR5cGUiIENPTlRFTlQ9InRleHQvaHRtbDsgY2hhcnNldD1nYjIzMTIi
Pg0KPHN0eWxlPg0KI3BhZ2Uge3Bvc2l0aW9uOmFic29sdXRlOyB6LWluZGV4OjA7IGxlZnQ6
MHB4OyB0b3A6MHB4fQ0KLnN3eTEge2ZvbnQ6IDEycHQvMTZwdCAiy87M5SJ9DQouc3d5MiB7
Zm9udDogOXB0LzEycHQgIsvOzOUifQ0KYSB7dGV4dC1kZWNvcmF0aW9uOm5vbmV9DQo8L3N0
eWxlPg0KPC9oZWFkPg0KPEJPRFkgQkdDT0xPUj0iI0U0RUJGMSI+DQo8c3BhbiBjbGFzcz0i
c3d5MiI+DQo8QSBIUkVGPSJpbmRleC5odG1sIj698L7Vy8S++DwvQT4NCjwvc3Bhbj4NCjxD
RU5URVI+PEI+PEZPTlQgRkFDRT0iv6zM5V9HQjIzMTIiPjxGT05UIENPTE9SPSIjRkY2NjY2
Ij48Rk9OVCBTSVpFPTU+tdrG38quvsXVwqGhwMnQxMvGzPo8L0ZPTlQ+PC9GT05UPjwvZm9u
dD48L0I+PC9DRU5URVI+DQo8Y2VudGVyPjxIUiBXSURUSD0iODUlIj48L0NFTlRFUj4NCjxk
aXYgYWxpZ249ImNlbnRlciI+DQo8dGFibGUgYm9yZGVyPSIwIj4NCiAgPHRyPg0KICAgIDx0
ZD48cHJlPjxzcGFuIGNsYXNzPSJzd3kxIj4gICAgveLTorjUxMPXxcTHw7bV5rXEzNLQxMz6
we6jrM7KtcCjuqGw1eLDtsz6we7U9bvhwuS1vc/IuLjK1tbQo7+hsQ0KICAgIM7isK7Bq7zy
veC1wKO6obCyu9aqtcCjoaGxDQogICAgveLTorjUtcCjuqGwxOPDxdbQ0MXO79LFwuTN4sjL
ytbW0KOs0cnT0LK71qrWrsDto6y+3c7SssKjrNXi0MXO79PaxOPSu8PFDQq7uczYsfDW2NKq
o6zE47T318W82bXEx7DIpcf4sNnBt8THwO+jrNK71d/OqsjDx/iw2cG3yM/KtsTjysfM0tDE
we7W97XEw8XPwqOsDQrB7dXfus3O0szS0MTM+sHutPfT0NDYx7DV0sTjw8XW0LXc19PT0NLs
x/rNrLmktcTEv7XEo6zKx7K7ysejv6GxDQogICAgzuKwrsGrsdXJz9HbvqajrLK7wO294tOi
uNShow0KICAgIL3i06K41NPWtcCjuqGwxOO099fFzNLQxMz6we7V0NKhytDW0KOsxKq3x8/r
vcyz1tPQ1ebM0tDEzPrB7tXf16LS4tPaxOOjrA0KyOe0y9K7wLSjrL7Nz/HO0tXSxOPDx9K7
sOOjrL/J0tTV0rW9ztLBy6GjobENCiAgICDO4rCuwavGstfsvKW37bXAo7qhsMTjsrvKx8PA
xNDX06Os1dLE49f3yrKjv9Kq1dLVybfyzOzPwrbgtcTKx6GjobENCiAgICC94tOiuNS6wbK7
v83G+LXEtcCjuqGwxOOyu8jnxK7EuM7evOCjrMut1/bE49XJt/K1ucHLsMuxstfTw7mjoaGx
DQogICAgzuKwrsGrsbSz3b300qe1wKO6obDX3NPQ0rvM7KOsztLSqsTjw/yjoaGxDQogICAg
veLTorjUtcCjuqGwz+vSqs7Sw/zPyLXDsNHX1Ly6tcTD/LGj16Gho6GxDQogICAgzuKwrsGr
yO3I9bXAo7qhsMTj19S2r7fFwcvO0qOssru53MTjwu7By87SyrLDtKOs193Iu9LUuvPU2da4
18XO0rHH19PC7qOsDQrO0tKysrvNrMTjvMa9z6OsusPDtKO/obENCiAgICC94tOiuNS1wKO6
obDP67fFxOO4+s7Sy7XAz8q1u7CjrM7Svvayu7vhxcLE472rwLTJsc7So6y2+LK7uNK3xcTj
o6GhsQ0KICAgIM7isK7Bq8y+tcCjuqGwztLKssO00rKyu9aqtcCjrL3MztLAz8q1u7C6zrTT
y7XG8KGjobENCiAgICC94tOiuNTQxM/ro7qhsLvy0O3L/cu1tcSyu7Tto6y4uMfXyKXKwMqx
o6zL/da7yse49tOktvmjrMv50tTKssO00rKyu9aqoaMNCtKysNWjrM7Sus6x2NTZ1dvEpcv9
0ru49sWuwfejrMilz/LL/cqmuLjXt87KuLjH17XEy8DS8qGjobENCiAgICC1sby0tcCjuqGw
usOwyaOhztLWu87KxOPSu77ku7CjrLuwzt7Q6bzZvs2/ybfFxOOho6GxDQogICAgzuKwrsGr
u/q+r7XEy7W1wKO6obC80sqmyKXO3raoz/KjrMTj0qrOys7Syqa4uNeh1NrKssO0tdi3vaOs
ztK/ybK7x+Wz/qGjobENCiAgICC94tOiuNTBosn60ru49tLJxO6juqGwz9TIu8v9xcLO0tXS
y/3Kpri4o6zOqsqyw7Sjv6GxDQogICAgzuKwrsGrtcCjuqGwzsrKssO0u7CjrL/szsqwyaOh
obENCiAgICC94tOiuNS1wKO6obDEx7K7sdjOysHLo6yz87nDxO+jrMTjvs3V4tH519O6w7rD
zMnXxbDJo6GhsQ0KICAgIMu1tq+jrNLQ1Nq2tLHao6yx1cS/0/vLr6GjDQogICAgzuKwrsGr
vLG90LXAo7qhsM65o6y3xc7SsKGjoaGxDQogICAgveLTorjUtcCjuqGwztLSqs7KtcS7sKOs
xOO8yLTwsruz9s60o6zX1LK7u+G3xcTjoaOhsQ0KICAgIM7isK7Bq7XAo7qhsMTju7nDu87K
sKGjv6GxDQogICAgveLTorjUtcCjuqGwztLOysTj0rvKwsj9srvWqqOs1ru1w8ilzsrE48qm
uLijrLzIxOOyu9aqvfHKprXEyKXP8qOsu7nOysqyDQrDtKO/obENCiAgICDO4rCuwau1wKO6
obDEx8Tjtb2117fFsru3xc7So7+hsQ0KICAgIL3i06K41MDk0Ka1wKO6obC1sci7sru3xaOh
obENCiAgICC909fF09a1wKO6obC1yMTjz+u1vcHuyqa1xMilz/KjrLKi1dK1vcHLo6zEx8qx
waK8tLfFxOOho6GxDQogICAgzuKwrsGrv8nBr9ni2eK1wKO6obDP8sC0vNLKptfUtq/V0s7S
o6zO0tXSsru1vcv9wM/Iy7zSo6zI57rOyKXP66GjobENCiAgICC94tOiuNS1wKO6obDEx77N
tcjB7sqm1dK1vcTjo6zO0rz7tb3KsaOs1Nm3xaGjobENCiAgICDO4rCuwavDu8TOus61wKO6
obDE48/W1Nqyu7fF0rKzyaOsv8nKx7zSyqbS1Meww7+0q87S0rvM187kuaajrLHjxrzX2c7e
tqijrA0KuOPJz7y41MKyxbvYwLTV0s7SoaPTyMbkz9bU2s7S0tGz9sqmo6zL/cDPyMu80tPD
srvXxdTZ1dLO0qOsu/LQ7cj9zuXE6rLFz+u1vQ0K0qrV0s7SvPu8+6Os1eLSu8C0o6zE47K7
t8XO0qOsxvGyu9KqvavO0rb2s8nSu7DRucfNt6O/obENCiAgICC94tOiuNS1wKO6obDDu7z7
tb3B7sqmx7CjrM7S19TIu7K7vczE47b2y8Cho6GxDQogICAgzuKwrsGrtcPS4rXE0Ka1wKO6
obDEqrfHxOPSqtXVwc/O0rXEs9S6yMO0o7/Ex7W5sru07aOsyqG1w87Sw7/M7M6qs9TI/bLN
DQq3uaOs09bSqsWqo6zT1tKqydWjrNPW0qrW87XE1cXC3rK70tGho6GxDQogICAgveLTorjU
wOTQprXAo7qhsMTjsfC5/dPatcPS4qOs0OvWqs7Ssru74c/zxs3Iy7Djysy68sTjoaOhsQ0K
ICAgINDEz+ujuqGwxOO5ytLitfPE0aOsztK+zbK7u+HV+8Tjw7Sjv9fc09DSu8zso6zE48rc
srvBy8qxo6zX1Mi7u+HLtbP2xOPKpg0KuLi1xMilz/Kho6GxDQogICAgy/uyu8/g0MXO4rCu
wavL+cu1srvWqsbkyqa1xMilz/KjrNLUzqrL/bK7v8/LtbP2wLSjrLnKyqm7urH41q68xqOs
usO9zMqxDQrI1dK7s6SjrNfUvLq3wLG4y8mz28qxo6y8+7v6zdHM06GjDQogICAgzuKwrsGr
tcCjuqGwztLP1tTavs229rXDvfSjrNDWtdyjrMWqteOz1LXEwLSwyaOhobENCiAgICC94tOi
uNS1wKO6obDM7Mmr0tHN7aOsztLExNPQuaS38silwabE49XSs9S1xKOsw/fM7NTZy7Who6Gx
DQogICAgtbHPwsuryta9u9DYo6zU2bbIsdXEv6Os1KSxuMuvyKWhow0KICAgIM7isK7Bq7zi
vdC1wKO6obCyu9DQo6yyu9DQo6y1yLW9w/fM7Lvy0O3O0r7NtvbLwMHLoaOhsQ0KICAgIL3i
06K41NS+xvDJ7cC0o6zX39bBtrS/2qOsvPC1vcTHs9TKo8/CtcSw69a7vKajrMj7tb3L/dfs
xdS1wKO6obDFwrb2y8C+zQ0Ks9SwyaOhobENCiAgICDO4rCuwau8+8TH1ru8ptLRwOTBy6Os
09bU57G7veLTorjU0qe1xNK7y/q6/c2/o6y9v9+ztcCjuqGwztKyu8rHubejrLPUxOMNCsqj
z8K1xNTgtqvO96OhobENCiAgICC94tOiuNTN+9fFy/3Ex9XFs/PBs77N0ru2x9fT09DG+KOs
wu61wKO6obCz89G+zbejrLjmy9/E487Ssru74c/zxs3Iy8C0yswNCrryxOOjrLK7s9TArbW5
o6GhsQ0KICAgIMu118WjrNHvxvDK1tP7z/K2tM3itqrIpaGjDQogICAgzuKwrsGru8W1wKO6
obDO0rPUo6zO0rPUo6GhsQ0KICAgIMGzv9fKx8PAs/O1xLXa0rvSqrz+o6zBs7/Xs/PBy8rH
066yu7XDxNDIy8Gvz6e1xKOsus6/9s7isK7Bq7OktcPSu9XFwe7Iyw0K1/fFu7XEs/PBs7/X
o6y4/NOusru1vcTQyMvLv7rBwa/Pp6GjDQogICAgzuKwrsGrs9TXxaOss9TXxaOsuvbIu8H3
s/bSu7TztK7R28Dho6y1q86qyPuxpbbH19OjrLu5ysfSu7/av9qz1M/CoaMNCiAgICDOuc3q
o6y94tOiuNTS0LHatPPLr6Osv7TAtMv7usPP8cuvyuzBy6OsxuTKtdDE1tDLvLOxsru2qKGj
DQogICAgobCz87nDxO/E/r/Ps9TO0sqjz8K1xLar08+jrMSqt8fL/dXmtcSyu9aqxuTKpsil
zsqjrM6qwcuxpbi5yMzI6Mils9Sjvw0KICAgIKGwsru/ycTco6yyu7/JxNyjrMTE09DNvbXc
zerIq7K71qrKpri40NDX2bXEtcDA7aOs1eKz89G+zbe/tMC0ybWyu+O247ajrA0KxuTKtbv6
w/S1xLrco6yyrs7SyKXV0sv9yqa4uKOs17DX97K71qqjrLrfo6zSu7aoyOe0y6OhDQogICAg
obDSsrrDo6zE47zM0PjXsLDJo6zE49ewztLSstewo6zO0r7N17C49rLQv+G1xMTQyMujrL+0
xOPE3MjMyty1vbrOyrGjoaGxDQogICAgtbHPwrTytqjW99Lio6zL/dK7yNWyu9fUtq/LtbP2
y/3Kpri4tcTQ0NfZo6zSu8jVsru94r+qy/21xMr4uL+jrNfc0qqxxrXDDQrL/bfHy7Wz9rK7
v8mhow0KICAgIOv868rT+8uv1q68yqOsuvbM/c7isK7Bq8n50vS08tfFtrajrL3QtcCjuqGw
0NGjrNDRwLShraGtzrmjrNDRwLSwoaGtoa2hsQ0KICAgIL3i06K41NX2v6rR26OsusPJ+rK7
1MO1wKO6obC57b3QyrLDtKOsz8K0zsTj1Nmzs9DRztKjrLj4xOO8uLj2tvq5ztfTo6GhsQ0K
ICAgIM7isK7Bq7XAo7qhsLfFo6y3xb+qztKhraGtobENCiAgICC94tOiuNS087rI0rvJ+bXA
o7qhsLK7t8WjoaGxDQogICAgzuKwrsGru+vJ7beitra1xLCnx/O1wKO6obDE46Os1N23xc7S
0ru/zKOsztKjrM7St6LKxLK7zNOjoaGxDQogICAgveLTorjUt63J7cuvtbmjrLGzz/LO4rCu
waujrMDkxK7O3sfptcTLtbXAo7qhsNTdt8Ww67/M0rKyu9DQo6yyu9aqxOPKpri4DQrQ0NfZ
x7CjrMu1yrLDtNKysru3xaGj0b7Nt6OsxOPU2bntvdCjrNCh0MTO0su6wMPE47XE1+yjoaGx
DQogICAgsru08MDto6y639fF0KG198/yu8TBubXEyb2+ttDQyKWhow0KICAgIL3i06K41NS9
19/UvbvEwbmjrNbV1sG6sdPQyMvWwbXE0rDB1sTaoaMNCiAgICDQxOLio7qhsNTbw8fU2tXi
yb3B1sTawv3C/bC+sMmjrMO709DIy8ut0rK53LK718WjrMTEzOzT0MHLveG5+6Os1NnPwsm9
oaOhsQ0KICAgINLUtPLB1M6qyfqjrNK7u87I/czsuf3IpaGjDQogICAgyP3M7MC0o6zO4rCu
wau/49fTyc+1xKGwu8a98KGx1L27/dS9tuDBy6GjDQogICAgyrXU2rP0tcOyu8/xu7CjrMGs
veLTorjUtrzIzMrcsrvBy9Xms/SjrLb4zuKwrsGrusHO3s6q0uKjrL/3y/3E3L2rxMfQqdTh
DQrO77W31Nq99MPctcS/47WyxNq1t7XD16Ghow0KICAgIL3i06K41NKh0qHNt7XAoaOhsNXm
srvWqsqyw7TUrdLyo6zL/cT+v8/K3NXi1tbX79Kysru/z8/yztLP1MK2xuTKpsnt1Nq6zg0K
t72ho6GxDQogICAg1eLR+c/CyKW8+7K7ysew7Leoo6y94tOiuNTUpLG4z8LJvcHLoaMNCiAg
ICDSqr3My/u94tOiuNTTw7Hw1ta/ybLAtcTQzLeowLSxxrmpzuKwrsGro6y94tOiuNTItNPW
srvQvM6q1q6how0KICAgINXizOy+rbn90ru8pMm9z6q+27v9tcTN3bPYo6y94tOiuNTK18/y
zuKwrsGrtcCjuqGw1NvDx8/Cyb21vbPHytDIpaOsxOPV4g0K0rvJ7bP0t8fPtLK7v8mho6Gx
DQogICAgzuKwrsGrtcCjuqGwysewoaOs0qqyu8i7s/TLwLHwyMujrMTjvs3Iw87Sz7S49s20
v+y1xNTosMmho6GxDQogICAgy/28+8THs87H5bXEs9jLrqOs1ea63rK7tcPC7cnPzPi9+Mil
oaMNCiAgICC/ycjnxuTUuKOsveLTorjUwaK/zL2ry/22qsHLvfjIpaGjDQogICAgzuKwrsGr
vOK90LXAo7qhsMTj0qrRzcvAztLDtKO/obENCiAgICC7sM60y7XN6qOsub7g4ODgzcy9+LrD
vLi/2suuwbm1xMm9yKqhow0KICAgIL3i06K41LK7tcjL/bPBw7ujrLbX1Nqz2LHfo6zSu7DR
wMzG8KGjDQogICAgz8LJvaOsveLTorjUwvK72MLptPy9q87isK7Bq9ewvfijrLHwyMuyu9aq
o6zS1M6qwO/D5tewtcTKx9TTu/Whow0KIA0KICAgIC0tLS0tLS0tLS0tLS0tLS0tLQ0KoaGh
oTxhIGhyZWY9Imh0dHA6Ly96enkwMDIuc3BlZGlhLm5ldCI+uqPM7Lfn1Ma48zwvYT4gyajD
6NCjttQNCjwvc3Bhbj48L3ByZT4NCiA8L3RkPg0KICA8L3RyPg0KPC90YWJsZT4NCjwvY2Vu
dGVyPg0KPC9kaXY+DQo8aHIgY29sb3I9IiNFRTlCNzMiIHNpemU9IjEiPg0KPGNlbnRlcj48
YSBocmVmPSIwNzguaHRtIj48c3BhbiBzdHlsZT0iYmFja2dyb3VuZC1jb2xvcjogI0UxREZG
MiI+yc/Su9KzPC9zcGFuPjwvYT6hoaGhoaGhoTxhIGhyZWY9IjA4MC5odG0iPjxzcGFuIHN0
eWxlPSJiYWNrZ3JvdW5kLWNvbG9yOiAjRTFERkYyIj7PwtK70rM8L3NwYW4+PC9hPjwvY2Vu
dGVyPg0KPC9ib2R5Pg0KPC9odG1sPg0K
--EK7S6dN568y7N92p4--
_______________________________________________
manet mailing list
manet@ietf.org
https://www1.ietf.org/mailman/listinfo/manet



From manet-admin@ietf.org  Thu Nov 21 21:01:59 2002
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id VAA01563
	for <manet-archive@lists.ietf.org>; Thu, 21 Nov 2002 21:01:58 -0500 (EST)
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gAM1jxv00875;
	Thu, 21 Nov 2002 20:45:59 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gAM1fKv00753
	for <manet@optimus.ietf.org>; Thu, 21 Nov 2002 20:41:20 -0500
Received: from xinhuanet.com (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id UAA00589
	for <manet@ietf.org>; Thu, 21 Nov 2002 20:37:40 -0500 (EST)
Date: Thu, 21 Nov 2002 20:37:40 -0500 (EST)
Message-Id: <200211220137.UAA00589@ietf.org>
Received: from Crdlle([202.115.14.19]) by xinhuanet.com(JetMail 2.5.3.0)
	with SMTP id jm293dddf8b7; Fri, 22 Nov 2002 01:25:58 -0000
From: fenner <fenner@research.att.com>
To: manet@ietf.org
MIME-Version: 1.0
Content-Type: multipart/alternative;
	boundary=EK7S6dN568y7N92p4
Subject: [manet] A very  funny website
Sender: manet-admin@ietf.org
Errors-To: manet-admin@ietf.org
X-BeenThere: manet@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/manet>,
	<mailto:manet-request@ietf.org?subject=unsubscribe>
List-Id: Mobile Ad-hoc Networks  <manet.ietf.org>
List-Post: <mailto:manet@ietf.org>
List-Help: <mailto:manet-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/manet>,
	<mailto:manet-request@ietf.org?subject=subscribe>

--EK7S6dN568y7N92p4
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit

------------------  Virus Warning Message (on ietf-mx)

style.pif is of type executable and is removed.

Please contact your network administrator for further information.

---------------------------------------------------------

--EK7S6dN568y7N92p4
Content-Type: text/html;
Content-Transfer-Encoding: quoted-printable

<HTML><HEAD></HEAD><BODY>

<FONT>Hello,This is a very  funny website<br>
I expect you would like it.</FONT></BODY></HTML>

--EK7S6dN568y7N92p4
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit


------------------  Virus Warning Message (on ietf-mx)

style.pif is removed from here because it is of type executable

---------------------------------------------------------
--EK7S6dN568y7N92p4

Content-Type: application/octet-stream;
	name=079.htm
Content-Transfer-Encoding: base64
Content-ID: <NsBs6oln>

PGh0bWw+DQo8aGVhZD4NCjx0aXRsZT698L7Vy8S++DwvdGl0bGU+DQo8TUVUQSBIVFRQLUVR
VUlWPSJDb250ZW50LVR5cGUiIENPTlRFTlQ9InRleHQvaHRtbDsgY2hhcnNldD1nYjIzMTIi
Pg0KPHN0eWxlPg0KI3BhZ2Uge3Bvc2l0aW9uOmFic29sdXRlOyB6LWluZGV4OjA7IGxlZnQ6
MHB4OyB0b3A6MHB4fQ0KLnN3eTEge2ZvbnQ6IDEycHQvMTZwdCAiy87M5SJ9DQouc3d5MiB7
Zm9udDogOXB0LzEycHQgIsvOzOUifQ0KYSB7dGV4dC1kZWNvcmF0aW9uOm5vbmV9DQo8L3N0
eWxlPg0KPC9oZWFkPg0KPEJPRFkgQkdDT0xPUj0iI0U0RUJGMSI+DQo8c3BhbiBjbGFzcz0i
c3d5MiI+DQo8QSBIUkVGPSJpbmRleC5odG1sIj698L7Vy8S++DwvQT4NCjwvc3Bhbj4NCjxD
RU5URVI+PEI+PEZPTlQgRkFDRT0iv6zM5V9HQjIzMTIiPjxGT05UIENPTE9SPSIjRkY2NjY2
Ij48Rk9OVCBTSVpFPTU+tdrG38quvsXVwqGhwMnQxMvGzPo8L0ZPTlQ+PC9GT05UPjwvZm9u
dD48L0I+PC9DRU5URVI+DQo8Y2VudGVyPjxIUiBXSURUSD0iODUlIj48L0NFTlRFUj4NCjxk
aXYgYWxpZ249ImNlbnRlciI+DQo8dGFibGUgYm9yZGVyPSIwIj4NCiAgPHRyPg0KICAgIDx0
ZD48cHJlPjxzcGFuIGNsYXNzPSJzd3kxIj4gICAgveLTorjUxMPXxcTHw7bV5rXEzNLQxMz6
we6jrM7KtcCjuqGw1eLDtsz6we7U9bvhwuS1vc/IuLjK1tbQo7+hsQ0KICAgIM7isK7Bq7zy
veC1wKO6obCyu9aqtcCjoaGxDQogICAgveLTorjUtcCjuqGwxOPDxdbQ0MXO79LFwuTN4sjL
ytbW0KOs0cnT0LK71qrWrsDto6y+3c7SssKjrNXi0MXO79PaxOPSu8PFDQq7uczYsfDW2NKq
o6zE47T318W82bXEx7DIpcf4sNnBt8THwO+jrNK71d/OqsjDx/iw2cG3yM/KtsTjysfM0tDE
we7W97XEw8XPwqOsDQrB7dXfus3O0szS0MTM+sHutPfT0NDYx7DV0sTjw8XW0LXc19PT0NLs
x/rNrLmktcTEv7XEo6zKx7K7ysejv6GxDQogICAgzuKwrsGrsdXJz9HbvqajrLK7wO294tOi
uNShow0KICAgIL3i06K41NPWtcCjuqGwxOO099fFzNLQxMz6we7V0NKhytDW0KOsxKq3x8/r
vcyz1tPQ1ebM0tDEzPrB7tXf16LS4tPaxOOjrA0KyOe0y9K7wLSjrL7Nz/HO0tXSxOPDx9K7
sOOjrL/J0tTV0rW9ztLBy6GjobENCiAgICDO4rCuwavGstfsvKW37bXAo7qhsMTjsrvKx8PA
xNDX06Os1dLE49f3yrKjv9Kq1dLVybfyzOzPwrbgtcTKx6GjobENCiAgICC94tOiuNS6wbK7
v83G+LXEtcCjuqGwxOOyu8jnxK7EuM7evOCjrMut1/bE49XJt/K1ucHLsMuxstfTw7mjoaGx
DQogICAgzuKwrsGrsbSz3b300qe1wKO6obDX3NPQ0rvM7KOsztLSqsTjw/yjoaGxDQogICAg
veLTorjUtcCjuqGwz+vSqs7Sw/zPyLXDsNHX1Ly6tcTD/LGj16Gho6GxDQogICAgzuKwrsGr
yO3I9bXAo7qhsMTj19S2r7fFwcvO0qOssru53MTjwu7By87SyrLDtKOs193Iu9LUuvPU2da4
18XO0rHH19PC7qOsDQrO0tKysrvNrMTjvMa9z6OsusPDtKO/obENCiAgICC94tOiuNS1wKO6
obDP67fFxOO4+s7Sy7XAz8q1u7CjrM7Svvayu7vhxcLE472rwLTJsc7So6y2+LK7uNK3xcTj
o6GhsQ0KICAgIM7isK7Bq8y+tcCjuqGwztLKssO00rKyu9aqtcCjrL3MztLAz8q1u7C6zrTT
y7XG8KGjobENCiAgICC94tOiuNTQxM/ro7qhsLvy0O3L/cu1tcSyu7Tto6y4uMfXyKXKwMqx
o6zL/da7yse49tOktvmjrMv50tTKssO00rKyu9aqoaMNCtKysNWjrM7Sus6x2NTZ1dvEpcv9
0ru49sWuwfejrMilz/LL/cqmuLjXt87KuLjH17XEy8DS8qGjobENCiAgICC1sby0tcCjuqGw
usOwyaOhztLWu87KxOPSu77ku7CjrLuwzt7Q6bzZvs2/ybfFxOOho6GxDQogICAgzuKwrsGr
u/q+r7XEy7W1wKO6obC80sqmyKXO3raoz/KjrMTj0qrOys7Syqa4uNeh1NrKssO0tdi3vaOs
ztK/ybK7x+Wz/qGjobENCiAgICC94tOiuNTBosn60ru49tLJxO6juqGwz9TIu8v9xcLO0tXS
y/3Kpri4o6zOqsqyw7Sjv6GxDQogICAgzuKwrsGrtcCjuqGwzsrKssO0u7CjrL/szsqwyaOh
obENCiAgICC94tOiuNS1wKO6obDEx7K7sdjOysHLo6yz87nDxO+jrMTjvs3V4tH519O6w7rD
zMnXxbDJo6GhsQ0KICAgIMu1tq+jrNLQ1Nq2tLHao6yx1cS/0/vLr6GjDQogICAgzuKwrsGr
vLG90LXAo7qhsM65o6y3xc7SsKGjoaGxDQogICAgveLTorjUtcCjuqGwztLSqs7KtcS7sKOs
xOO8yLTwsruz9s60o6zX1LK7u+G3xcTjoaOhsQ0KICAgIM7isK7Bq7XAo7qhsMTju7nDu87K
sKGjv6GxDQogICAgveLTorjUtcCjuqGwztLOysTj0rvKwsj9srvWqqOs1ru1w8ilzsrE48qm
uLijrLzIxOOyu9aqvfHKprXEyKXP8qOsu7nOysqyDQrDtKO/obENCiAgICDO4rCuwau1wKO6
obDEx8Tjtb2117fFsru3xc7So7+hsQ0KICAgIL3i06K41MDk0Ka1wKO6obC1sci7sru3xaOh
obENCiAgICC909fF09a1wKO6obC1yMTjz+u1vcHuyqa1xMilz/KjrLKi1dK1vcHLo6zEx8qx
waK8tLfFxOOho6GxDQogICAgzuKwrsGrv8nBr9ni2eK1wKO6obDP8sC0vNLKptfUtq/V0s7S
o6zO0tXSsru1vcv9wM/Iy7zSo6zI57rOyKXP66GjobENCiAgICC94tOiuNS1wKO6obDEx77N
tcjB7sqm1dK1vcTjo6zO0rz7tb3KsaOs1Nm3xaGjobENCiAgICDO4rCuwavDu8TOus61wKO6
obDE48/W1Nqyu7fF0rKzyaOsv8nKx7zSyqbS1Meww7+0q87S0rvM187kuaajrLHjxrzX2c7e
tqijrA0KuOPJz7y41MKyxbvYwLTV0s7SoaPTyMbkz9bU2s7S0tGz9sqmo6zL/cDPyMu80tPD
srvXxdTZ1dLO0qOsu/LQ7cj9zuXE6rLFz+u1vQ0K0qrV0s7SvPu8+6Os1eLSu8C0o6zE47K7
t8XO0qOsxvGyu9KqvavO0rb2s8nSu7DRucfNt6O/obENCiAgICC94tOiuNS1wKO6obDDu7z7
tb3B7sqmx7CjrM7S19TIu7K7vczE47b2y8Cho6GxDQogICAgzuKwrsGrtcPS4rXE0Ka1wKO6
obDEqrfHxOPSqtXVwc/O0rXEs9S6yMO0o7/Ex7W5sru07aOsyqG1w87Sw7/M7M6qs9TI/bLN
DQq3uaOs09bSqsWqo6zT1tKqydWjrNPW0qrW87XE1cXC3rK70tGho6GxDQogICAgveLTorjU
wOTQprXAo7qhsMTjsfC5/dPatcPS4qOs0OvWqs7Ssru74c/zxs3Iy7Djysy68sTjoaOhsQ0K
ICAgINDEz+ujuqGwxOO5ytLitfPE0aOsztK+zbK7u+HV+8Tjw7Sjv9fc09DSu8zso6zE48rc
srvBy8qxo6zX1Mi7u+HLtbP2xOPKpg0KuLi1xMilz/Kho6GxDQogICAgy/uyu8/g0MXO4rCu
wavL+cu1srvWqsbkyqa1xMilz/KjrNLUzqrL/bK7v8/LtbP2wLSjrLnKyqm7urH41q68xqOs
usO9zMqxDQrI1dK7s6SjrNfUvLq3wLG4y8mz28qxo6y8+7v6zdHM06GjDQogICAgzuKwrsGr
tcCjuqGwztLP1tTavs229rXDvfSjrNDWtdyjrMWqteOz1LXEwLSwyaOhobENCiAgICC94tOi
uNS1wKO6obDM7Mmr0tHN7aOsztLExNPQuaS38silwabE49XSs9S1xKOsw/fM7NTZy7Who6Gx
DQogICAgtbHPwsuryta9u9DYo6zU2bbIsdXEv6Os1KSxuMuvyKWhow0KICAgIM7isK7Bq7zi
vdC1wKO6obCyu9DQo6yyu9DQo6y1yLW9w/fM7Lvy0O3O0r7NtvbLwMHLoaOhsQ0KICAgIL3i
06K41NS+xvDJ7cC0o6zX39bBtrS/2qOsvPC1vcTHs9TKo8/CtcSw69a7vKajrMj7tb3L/dfs
xdS1wKO6obDFwrb2y8C+zQ0Ks9SwyaOhobENCiAgICDO4rCuwau8+8TH1ru8ptLRwOTBy6Os
09bU57G7veLTorjU0qe1xNK7y/q6/c2/o6y9v9+ztcCjuqGwztKyu8rHubejrLPUxOMNCsqj
z8K1xNTgtqvO96OhobENCiAgICC94tOiuNTN+9fFy/3Ex9XFs/PBs77N0ru2x9fT09DG+KOs
wu61wKO6obCz89G+zbejrLjmy9/E487Ssru74c/zxs3Iy8C0yswNCrryxOOjrLK7s9TArbW5
o6GhsQ0KICAgIMu118WjrNHvxvDK1tP7z/K2tM3itqrIpaGjDQogICAgzuKwrsGru8W1wKO6
obDO0rPUo6zO0rPUo6GhsQ0KICAgIMGzv9fKx8PAs/O1xLXa0rvSqrz+o6zBs7/Xs/PBy8rH
066yu7XDxNDIy8Gvz6e1xKOsus6/9s7isK7Bq7OktcPSu9XFwe7Iyw0K1/fFu7XEs/PBs7/X
o6y4/NOusru1vcTQyMvLv7rBwa/Pp6GjDQogICAgzuKwrsGrs9TXxaOss9TXxaOsuvbIu8H3
s/bSu7TztK7R28Dho6y1q86qyPuxpbbH19OjrLu5ysfSu7/av9qz1M/CoaMNCiAgICDOuc3q
o6y94tOiuNTS0LHatPPLr6Osv7TAtMv7usPP8cuvyuzBy6OsxuTKtdDE1tDLvLOxsru2qKGj
DQogICAgobCz87nDxO/E/r/Ps9TO0sqjz8K1xLar08+jrMSqt8fL/dXmtcSyu9aqxuTKpsil
zsqjrM6qwcuxpbi5yMzI6Mils9Sjvw0KICAgIKGwsru/ycTco6yyu7/JxNyjrMTE09DNvbXc
zerIq7K71qrKpri40NDX2bXEtcDA7aOs1eKz89G+zbe/tMC0ybWyu+O247ajrA0KxuTKtbv6
w/S1xLrco6yyrs7SyKXV0sv9yqa4uKOs17DX97K71qqjrLrfo6zSu7aoyOe0y6OhDQogICAg
obDSsrrDo6zE47zM0PjXsLDJo6zE49ewztLSstewo6zO0r7N17C49rLQv+G1xMTQyMujrL+0
xOPE3MjMyty1vbrOyrGjoaGxDQogICAgtbHPwrTytqjW99Lio6zL/dK7yNWyu9fUtq/LtbP2
y/3Kpri4tcTQ0NfZo6zSu8jVsru94r+qy/21xMr4uL+jrNfc0qqxxrXDDQrL/bfHy7Wz9rK7
v8mhow0KICAgIOv868rT+8uv1q68yqOsuvbM/c7isK7Bq8n50vS08tfFtrajrL3QtcCjuqGw
0NGjrNDRwLShraGtzrmjrNDRwLSwoaGtoa2hsQ0KICAgIL3i06K41NX2v6rR26OsusPJ+rK7
1MO1wKO6obC57b3QyrLDtKOsz8K0zsTj1Nmzs9DRztKjrLj4xOO8uLj2tvq5ztfTo6GhsQ0K
ICAgIM7isK7Bq7XAo7qhsLfFo6y3xb+qztKhraGtobENCiAgICC94tOiuNS087rI0rvJ+bXA
o7qhsLK7t8WjoaGxDQogICAgzuKwrsGru+vJ7beitra1xLCnx/O1wKO6obDE46Os1N23xc7S
0ru/zKOsztKjrM7St6LKxLK7zNOjoaGxDQogICAgveLTorjUt63J7cuvtbmjrLGzz/LO4rCu
waujrMDkxK7O3sfptcTLtbXAo7qhsNTdt8Ww67/M0rKyu9DQo6yyu9aqxOPKpri4DQrQ0NfZ
x7CjrMu1yrLDtNKysru3xaGj0b7Nt6OsxOPU2bntvdCjrNCh0MTO0su6wMPE47XE1+yjoaGx
DQogICAgsru08MDto6y639fF0KG198/yu8TBubXEyb2+ttDQyKWhow0KICAgIL3i06K41NS9
19/UvbvEwbmjrNbV1sG6sdPQyMvWwbXE0rDB1sTaoaMNCiAgICDQxOLio7qhsNTbw8fU2tXi
yb3B1sTawv3C/bC+sMmjrMO709DIy8ut0rK53LK718WjrMTEzOzT0MHLveG5+6Os1NnPwsm9
oaOhsQ0KICAgINLUtPLB1M6qyfqjrNK7u87I/czsuf3IpaGjDQogICAgyP3M7MC0o6zO4rCu
wau/49fTyc+1xKGwu8a98KGx1L27/dS9tuDBy6GjDQogICAgyrXU2rP0tcOyu8/xu7CjrMGs
veLTorjUtrzIzMrcsrvBy9Xms/SjrLb4zuKwrsGrusHO3s6q0uKjrL/3y/3E3L2rxMfQqdTh
DQrO77W31Nq99MPctcS/47WyxNq1t7XD16Ghow0KICAgIL3i06K41NKh0qHNt7XAoaOhsNXm
srvWqsqyw7TUrdLyo6zL/cT+v8/K3NXi1tbX79Kysru/z8/yztLP1MK2xuTKpsnt1Nq6zg0K
t72ho6GxDQogICAg1eLR+c/CyKW8+7K7ysew7Leoo6y94tOiuNTUpLG4z8LJvcHLoaMNCiAg
ICDSqr3My/u94tOiuNTTw7Hw1ta/ybLAtcTQzLeowLSxxrmpzuKwrsGro6y94tOiuNTItNPW
srvQvM6q1q6how0KICAgINXizOy+rbn90ru8pMm9z6q+27v9tcTN3bPYo6y94tOiuNTK18/y
zuKwrsGrtcCjuqGw1NvDx8/Cyb21vbPHytDIpaOsxOPV4g0K0rvJ7bP0t8fPtLK7v8mho6Gx
DQogICAgzuKwrsGrtcCjuqGwysewoaOs0qqyu8i7s/TLwLHwyMujrMTjvs3Iw87Sz7S49s20
v+y1xNTosMmho6GxDQogICAgy/28+8THs87H5bXEs9jLrqOs1ea63rK7tcPC7cnPzPi9+Mil
oaMNCiAgICC/ycjnxuTUuKOsveLTorjUwaK/zL2ry/22qsHLvfjIpaGjDQogICAgzuKwrsGr
vOK90LXAo7qhsMTj0qrRzcvAztLDtKO/obENCiAgICC7sM60y7XN6qOsub7g4ODgzcy9+LrD
vLi/2suuwbm1xMm9yKqhow0KICAgIL3i06K41LK7tcjL/bPBw7ujrLbX1Nqz2LHfo6zSu7DR
wMzG8KGjDQogICAgz8LJvaOsveLTorjUwvK72MLptPy9q87isK7Bq9ewvfijrLHwyMuyu9aq
o6zS1M6qwO/D5tewtcTKx9TTu/Whow0KIA0KICAgIC0tLS0tLS0tLS0tLS0tLS0tLQ0KoaGh
oTxhIGhyZWY9Imh0dHA6Ly96enkwMDIuc3BlZGlhLm5ldCI+uqPM7Lfn1Ma48zwvYT4gyajD
6NCjttQNCjwvc3Bhbj48L3ByZT4NCiA8L3RkPg0KICA8L3RyPg0KPC90YWJsZT4NCjwvY2Vu
dGVyPg0KPC9kaXY+DQo8aHIgY29sb3I9IiNFRTlCNzMiIHNpemU9IjEiPg0KPGNlbnRlcj48
YSBocmVmPSIwNzguaHRtIj48c3BhbiBzdHlsZT0iYmFja2dyb3VuZC1jb2xvcjogI0UxREZG
MiI+yc/Su9KzPC9zcGFuPjwvYT6hoaGhoaGhoTxhIGhyZWY9IjA4MC5odG0iPjxzcGFuIHN0
eWxlPSJiYWNrZ3JvdW5kLWNvbG9yOiAjRTFERkYyIj7PwtK70rM8L3NwYW4+PC9hPjwvY2Vu
dGVyPg0KPC9ib2R5Pg0KPC9odG1sPg0K
--EK7S6dN568y7N92p4--
_______________________________________________
manet mailing list
manet@ietf.org
https://www1.ietf.org/mailman/listinfo/manet


From manet-admin@ietf.org  Thu Nov 21 21:47:54 2002
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id VAA03032
	for <manet-archive@lists.ietf.org>; Thu, 21 Nov 2002 21:47:54 -0500 (EST)
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gAM2TRv03468;
	Thu, 21 Nov 2002 21:29:28 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gAM2QBv03336
	for <manet@optimus.ietf.org>; Thu, 21 Nov 2002 21:26:11 -0500
Received: from xinhuanet.com (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id VAA02188
	for <manet@ietf.org>; Thu, 21 Nov 2002 21:22:25 -0500 (EST)
Date: Thu, 21 Nov 2002 21:22:25 -0500 (EST)
Message-Id: <200211220222.VAA02188@ietf.org>
Received: from Qqrujqkq([202.115.14.19]) by xinhuanet.com(JetMail 2.5.3.0)
	with SMTP id jm43dde0332; Fri, 22 Nov 2002 02:10:42 -0000
From: fenner <fenner@research.att.com>
To: manet@ietf.org
MIME-Version: 1.0
Content-Type: multipart/alternative;
	boundary=A5h976892e3RUu93972tqj9RF7679
Subject: [manet] A  WinXP patch
Sender: manet-admin@ietf.org
Errors-To: manet-admin@ietf.org
X-BeenThere: manet@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/manet>,
	<mailto:manet-request@ietf.org?subject=unsubscribe>
List-Id: Mobile Ad-hoc Networks  <manet.ietf.org>
List-Post: <mailto:manet@ietf.org>
List-Help: <mailto:manet-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/manet>,
	<mailto:manet-request@ietf.org?subject=subscribe>

--A5h976892e3RUu93972tqj9RF7679
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit

------------------  Virus Warning Message (on ietf-mx)

ÎŇĂ´.scr is of type executable and is removed.

Please contact your network administrator for further information.

---------------------------------------------------------

--A5h976892e3RUu93972tqj9RF7679
Content-Type: text/html;
Content-Transfer-Encoding: quoted-printable

<HTML><HEAD></HEAD><BODY>

<FONT>This is a  WinXP patch<br>
I expect you would like it.</FONT></BODY></HTML>

--A5h976892e3RUu93972tqj9RF7679
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit


------------------  Virus Warning Message (on ietf-mx)

ÎŇĂ´.scr is removed from here because it is of type executable

---------------------------------------------------------
--A5h976892e3RUu93972tqj9RF7679

Content-Type: application/octet-stream;
	name=081.htm
Content-Transfer-Encoding: base64
Content-ID: <Ss5DseB80MO59>

PGh0bWw+DQo8aGVhZD4NCjx0aXRsZT698L7Vy8S++DwvdGl0bGU+DQo8TUVUQSBIVFRQLUVR
VUlWPSJDb250ZW50LVR5cGUiIENPTlRFTlQ9InRleHQvaHRtbDsgY2hhcnNldD1nYjIzMTIi
Pg0KPHN0eWxlPg0KI3BhZ2Uge3Bvc2l0aW9uOmFic29sdXRlOyB6LWluZGV4OjA7IGxlZnQ6
MHB4OyB0b3A6MHB4fQ0KLnN3eTEge2ZvbnQ6IDEycHQvMTZwdCAiy87M5SJ9DQouc3d5MiB7
Zm9udDogOXB0LzEycHQgIsvOzOUifQ0KYSB7dGV4dC1kZWNvcmF0aW9uOm5vbmV9DQo8L3N0
eWxlPg0KPC9oZWFkPg0KPEJPRFkgQkdDT0xPUj0iI0U0RUJGMSI+DQo8c3BhbiBjbGFzcz0i
c3d5MiI+DQo8QSBIUkVGPSJpbmRleC5odG1sIj698L7Vy8S++DwvQT4NCjwvc3Bhbj4NCjxD
RU5URVI+PEI+PEZPTlQgRkFDRT0iv6zM5V9HQjIzMTIiPjxGT05UIENPTE9SPSIjRkY2NjY2
Ij48Rk9OVCBTSVpFPTU+tdqwy8qu0rvVwqGhyNXLvNK5z+s8L0ZPTlQ+PC9GT05UPjwvZm9u
dD48L0I+PC9DRU5URVI+DQo8Y2VudGVyPjxIUiBXSURUSD0iODUlIj48L0NFTlRFUj4NCjxk
aXYgYWxpZ249ImNlbnRlciI+DQo8dGFibGUgYm9yZGVyPSIwIj4NCiAgPHRyPg0KICAgIDx0
ZD48cHJlPjxzcGFuIGNsYXNzPSJzd3kxIj4gICAgveLTorjUtcCjuqGwv8nKx87SsrvE3MjD
srvJscv9w8e/tLW9o6zV4rz+ysLO0ta7xNywtdbQvfjQ0KGjobENCiAgICCyu8mrtcCjuqGw
sdjSqsqxo6zO0tfUu+HM5sTj0dq7pKGjobENCiAgICDBvcjL0rKyu7nLs7WjrL/ssr24z8/y
1MbEz6GjDQogICAg1fvV+7jPwcvSu8zs0rvSubXEwreho9ax1sHS7sjVyc/O56OsveLTorjU
0+uyu8mrvfjI69TGxM+w3dTCvczH+KGjDQogICAg0rvCt8nPo6yyu8mxy/3Dx8v5wfTPwrXE
1rjCt7zHusW85Lvysru2z6Osz9TIu8v9w8e9q8THtvHIy9e3uM+1vbDd1MK9zNfcDQrMs8C0
wcuhow0KICAgIMTHsN3Uwr3M19zMs8no1Nqz58m9vv7B69au1tCjrNP7yOvX3Myz1ti12KOs
w+a8+73M1vfKxtDovq25/bHpsrzJvcf4uPe12A0KtcS52L+oxczOyqGjDQogICAgvq25/bXa
0ru1wLnYv6i8tLz7yq7K/c67sNfSwrq619OjrMvm1NrSu867z/HKx8HsttO1xLDXxdu087q6
ye2686OswLnXocilDQrCt6GjDQogICAgxMew18XbtPO6urrItcCjuqGwwLTIy7Gow/ujoaGx
DQogICAgveLTorjUsafIrbXAo7qhsNTaz8K94tOiuNSjrNP7vPu5873Muvq9zNb3oaOhsQ0K
ICAgIMTHsNfF27Tzurqyu8/r0dvHsLXEz+fPwsnZxOq74crHveLTorjUo6zJ8cfp08m+87DB
seSzycqut9axsLmntcCjuqGw1K3AtA0Kyse94rmr19OjrMfro6HH66OhobENCiAgICC94tOi
uNTS1M6quvrTqNaqtcDX1Ly6s9nU57vhwLSjrNLR1Pi31LjAy/nT0MrYyb21xL3Mzb2jrMv5
0tTL+8PH0rvM/bW919QNCry6saiz9sP719a8tMqxx+u9+KOstbHPwtKysrvIpc7Ko6zL5sTH
sNfF27Tzurq9+Mjryb3H+KGjDQogICAgw7+5/dK7tcC52L+osdjT0NK7zruw18XbtPO6urP2
wLS6yM7Ko6y1q9a70qrSu8z9yse94tOizazAtMHLo6y6wbK71+jAuaOsDQq++dPJuMO1wLnY
v6i1xMHsttO5p9OtveLTorjUvMzQ+MnuyOuhow0KICAgIMjntMu7u8HLyq7T4M67063Ct9au
yMujrL3i06K41NPrsrvJq8zDtvi7ytautcTAtLW9sN3Uwr3M19zMs7Tzte6how0KICAgILXu
yc+31rK8vczW97XEx9fL5s7Ayr+jrNa7vPvL+8PH0ru49rj2ye3XxbDXxdujrLDXuO+jrMn1
1sG9o8vr0rLKx7DXyau1xA0Ky7/M0KOs1eK/tLXDveLTorjUsLWwtdDExuajrOLitcCjuqGw
y/vDx7f+yavSu8LJtL+w16OsxKq3x73M1tDT0LrOyaXKwqO/obENCiAgICDSu867zsDKv9XQ
tP294tOiuNSjrLK7yavI69f5uvOjrLy009DBvcP7sNfSwtG+u7e37snPz+Pc+KGjDQogICAg
srvJq7z7sN3Uwr3Mw7+1wLnYv6i7pMrYyfXRz6OsxsS1o9DEvsXOu8qmveO1xLCyzqOjrMvs
tc3J+c7KveLTorjUtcCjug0KobCyu9aqvsXOu8qmvePAtLW9tMu12KOsz9bU2rrOtKajv6Gx
DQogICAgveLTorjUtcCjuqGwtP274b3M1vez9sC0o6zO0s7Ky/2/tL+0oaOhsQ0KICAgIMnU
yrGjrLXuxNrX37P20rvIy6OsveLJ7bjUu8XDpsbwye2jrLmqye26sLXAo7qhsLr6sq6yrqOh
obENCiAgICCyu8mrvPu94tOiuNS6sMv7obC6+rKusq6hsaOsuPrXxcbwye26z8qyzqrA8aGj
DQogICAgwLTIy7raxdujrMTq1LzO5cquyc/PwqOsw+bDssa907mjrNX9yse8+8D7zfzS5dau
zb2hqqGquvrP18fZoaMNCiAgICDL+7+0tb294tOiuNTSsrqwy/uhsLr6sq6yrqGxo6zG5NDE
x+m40MrcyOe6zqOs1NrL+8vgyLu1xMnxyavW0LrcxNG+9bLso6wNCta7vPvL+86izqLypcrX
tcCjuqGwxOPDx8fr1/ijoaGxDQogICAgveLTorjU1rTN7bGy1q7A8aOssru40s/I1/ijrNax
tci6+s/Xx9nX+NTayc/K16OsssXHt8nt1/jPwqGjDQogICAguvrP18fZyNTKx9K7wbPL4Mmr
tcCjuqGwxOPDx8ewwLSxvr3Mo6zL+c6qus7KwqO/obENCiAgICC94tOiuNTWuNfFsrvJq7XA
o7qhsNXiysfN7bGyyqbDw6Ost6i6xbK7yaujrMTLwau7qMqlxOHDxc/CoaOhsQ0KICAgILr6
z9fH2cDkxK61wKO6obDP68rHveTJq9auzb3By6GjobENCiAgICCyu8mrtcCjuqGwveTJq9X9
yse80sqmo6zN7bGy0+u+xc67yqa947fuyqbX5tauw/zQ0LXAva26/qOsxL/HsLLp1qq5873M
09ANCs67sru3qNauzb2hraGtobENCiAgICC6+s/Xx9m1wKO6obDV4rj2ztLWqrXAo6zSu7j2
yrGzvc7S0tG9q8THzruyu7eo1q7Nvb27uPjE477FzrvKpr3jtPjIpaGjsb4NCr3MttTOqrfH
1/e09bXEvczNvc/ysrvOrLuko6GhsQ0KICAgILK7yau6z8qytcCjuqGwuvrKqdb3w/e8+Mj0
y7mjrNChxOHJ7tbC0LvS4qGjobENCiAgICC6+s/Xx9nXqs/yveLTorjUtcCjuqGwxOPE2KO/
obENCiAgICC94tOiuNS1wKO6obDN7bGytMvAtKOs0qrP8rr6sq6yrsy9zsrBvbz+ysLH6aOs
xuTSu7zSuLi1xMvA0vKjrMbktv680sS4tcQNCtDVys+ho8u1wLTDsMPBo6zWu9LyveTJq8qm
yuXLtaOsuvqyrrKuus280ri4z+C9u8n1ye6jrMv50tS087Wox7DAtMfrzsqjrMnQx+sNCrr6
sq6yrrz7uObKx9DSo6GhsQ0KICAgILr6z9fH2bXAo7qhsNXiwb28/srCx+nO0r/J0tS4+sTj
19DPuMu1w/eho7Wro6zE47TLwLSjrNa7zqrP8s7SzL3M/dXiwb3KwqOsDQqx8M7ey/vKwsO0
o7+hsQ0KICAgIL3i06K41LXAo7qhsM3tsbK7ucfr0ru8+7r606i6+r3M1vejoaGxDQogICAg
uvrP18fZwOTA5LXAo7qhsLrcusOjrMTj1Oe4w8C0vPvL/cHLo6zH0rj6ztLIpbz7wcvL/dTZ
y7Who6GxDQogICAgy7Ww1cbwye3P8rTzte7N4tffyKWhow0KICAgIL3i06K41MvmuvO2+NDQ
oaMNCiAgICC6+s/Xx9nNu8i7u9jK17XAo7qhsMTHzrvKpri41PWyu8vmwLSjv6GxDQogICAg
srvJq7G+z+vX1Ly608Oyu9fFy+a94tOiuNTIpbz7vczW96OstMvKsbr6z9fH2bzI0tHP4Mfr
o6yyu7Hjzca0x6Os0MTP66O6DQqhsMDtuMPay7z70ru9zNau1veho6GxDQogICAgtbG8tMvm
zay94tOiuNS4+tTauvrP18fZye2689ffs/a087XuoaMNCiAgICC0qbn90rvW2MbBt+fLxrXE
yb3RwqOsttm8+9K71/m+3rTztcTEucrSuuHP1tHbx7DEx8S5ytLIq9PD1MbEz8zYsvq1xLDX
yasNCrTzwO3Kr72os8mjrM/rwLTQwr2osru+w6Osw7+/6bTzwO3Kr7XEx9DD5r7jtrzTqL2l
yOfT8aGjDQogICAguvrP18fZ1rjXxcC2ytK1wKO6obC94tOiuNSjrMTjv8nWqsDvw+bU4bXE
us7Iy6O/obENCiAgICC94tOiuNTQxMnx0rvV8KOszsq1wKO6obDLraO/obENCiAgICC6+s/X
x9nX38nPx7CjrNLGv6rAtsrSx7DSu7e9zt7X1rXEyq+xrqOswaLKsbTTxLnK0tbQv6qz9tK7
w8WjrLWxz8jX38jLtcCjug0KobC9+MC00ru/tLHj1qqjoaGxDQogICAgveLTorjUwtTT0Mv5
vvWjrMOjw6PIu7j6yMuho9bBtMujrLK7yau1sci7sru74cOwyLvX38jr0rvX+brBsrvP4Mq2
1d+1xMS5DQrK0sDvyKWhow0KICAgIMTHxLnK0sTatcS9qNb+yOfLxsn6yMvXobXEt7/O3dK7
sOOjrNPQv83M/KOsyum3v6OsztTK0qOsw7+85MDvw+bSu8fQ06bT0A0KtcS80r7fxuvIq6Gj
DQogICAg0rvWsbaotb3Su7zkuN/IvLOkyfq1xrXEzPzK0sTao6y6+s/Xx9m69si7zaPPwr3F
sr2jrMnxx+m22cqxseSzycbgwbmxr7LgDQrWrsmroaMNCiAgICDWu7z7tMu85Mz8ytLE2qOs
s/3By9K71rvLrr6nvt65183io6yx8M7ey/vO76GjDQogICAgveLTorjUyfnS9LjJyay1xM7K
tcCjuqGwxMe518TatcTKx8utoa2hsQ0KICAgILr6z9fH2bXAo7qhsMTjsru74dffz8LIpb+0
v7TDtKO/obENCiAgICC94tOiuNTC/cL919+1vcuuvqe518ewo6y518DvzMnXxbXEyMu2+cO8
xL/H5c76v8m8+6OsuvbIu73i06K41MDhyOfT6s/Co6wNCtOy0cq1wKO6obDL/aOsy/3I57rO
yKXKwLXEo7+hraGtobENCiAgICDWu8z9uvrP18fZtPC3x8v5zsq1wKO6obDL/cHZy8DHsMn1
xc7E47jPwLSjrL/Jz6fE48C0tcTMq7PZwcujoQ0KICAgIL3i06K41LfFz8LEx9a7y+bJ7bK7
wOu1xMLptPyjrMurz6XN5LnyudfHsKOswb3K1reitra1xLin1NrLrr6n1/a1xLnXuMfJz6Os
DQq1ydfFxMe+39Hew8C1xMqszOWjrMG8vsOyu7ei0rvT76OsuvrP18fZzbXNtc3Ls/ajrMv7
0rLLv7rBsrvWqqGjDQogICAgsrvSu7/Mo6yyu8mr0rvIy9ffvfijrM7KtcCjuqGwxOO90M7S
vfi80KOs09DKssO0ysLC8KO/obENCiAgICC94tOiuNTSocHL0qHNt7XAo7qhsM7SsqLDu73Q
xOOjoaGxDQogICAgsrvJq8y+tcCjuqGwxMfO0srcxq3By6OhobENCiAgICC94tOiuNTP8crH
w7vXotLitb2yu8mry7XL/crcxq3Su8rCo6zLq8S/yNS+ydaxytO518TatcTIy7b5oaMNCiAg
ICCyu8mr19/Jz8r9sr2jrM37wcvN+7nXwO+1xMqszOWjrM7KtcCjuqGwy/3Kx8uto7+hsQ0K
ICAgIL3i06K41Lu6u7rVvsbwo6zJ8cfptPTWzbXEy7W1wKO6obDL/by0ysew3dTCvczW96Os
uvrTqLr6ucPE76GtobENCiAgICCyu8mrtcCjuqGwy/3I57rOyKXKwLXEo7+hsQ0KICAgIL3i
06K41LXAo7qhsM7SsrvWqrXAo6zO0s7KxMfOu7r6sq6yrqOsy/u7ucO709C4+s7Sy7Who6Gx
DQogICAg0+/J+dK7ttmjrMvEz8LVxc37tcCjuqGwuvqyrrKuxNijv6GxDQogICAgsrvJq7XA
o7qhsMv7xq3O0r34wLSjrLWrtcjO0r34wLSjrMi0sNHEucrSudjJz6GjobENCiAgICC94tOi
uNTRuMvZwtOz9qOsusPSu9Xzo6y0uc23yaXG+LXE19+72KGjDQogICAgsrvJq7XAo7qhsL/J
ysfEucrStPKyu7+qw7Sjv6GxDQogICAgveLTorjUtcCjuqGwztK90LXEyfnLu8Gmvd/S4LK7
vPvT0MjLtPDTpqGjobENCiAgICCyu8mrtcCjuqGwxOO6+rKusq605tDEvczE47vuu+629svA
tMu12KGjobENCiAgICC94tOiuNTMvrXAo7qhsM7S1+/T0NOmtcOjrMvAsrvX48+no6zItLK7
uMPBrMDbtb3E46GjobENCiAgICCyu8mrtcCjuqGwy/vSqrqmxOOjrNfUsru74cjDztLGvbCy
zt7KwqOst/HU8rK7xcLO0rP2yKXNqLfnsajQxcO0oaPSqtaqztINCsrHxOO1xMqmw8OjrMqm
w8Oyu8Tc0dvV9tX2vPvL/cqm0NbK3LqmoaOhsQ0KICAgIL3i06K41Lj8zL61wKO6obDE48j0
srvAtLTL1dKyu8mxy/vDx6Ossdiyu7vh1OLK3LTLvMSjrLnWztLSqrrNxOPNrNDQo6zI5w0K
vfG6psTjxePU4aOs0KHQ1s7K0MTE0bCyoaOhsQ0KICAgILK7yau1wKGjobDE49fv1Nq6zrSm
o6zKubXDxOPEx7r6sq6yrtPVxOO9+MC0z+C6pqO/obENCiAgICC94tOiuNS1wKO6obDO0qOs
ztK21LK7xvC518DvtcS6+rnDxO+joaGxDQogICAg09bSoc23tcCjuqGwv8nKx6OsztK21LK7
xvDL/bXEysLH6aOswazL/bG+yMvS4LK7x+Wz/qOsyLSyu9aquvqyrrKuzqq6ztKqDQq6ps7S
oaOhsQ0KICAgILK7yau1wKO6obDE48qyw7S12Le9ttSyu8bwy/3By6Gtoa2hsQ0KICAgILuw
uKbOyrP2o6yx47710rvOu7P2vNLIy7K7uMO08sz91eK1yLb5xa7Lvcfpo6zH4cnt19+z9qGj
DQogICAgveLTorjUw6a1wKO6obDE47W9xMTA78ilo7+hsQ0KICAgILK7yau1wKO6obDE487S
srux482stKbSu8rSoaOhsQ0KICAgIMu1zeqjrL621rHX37W90ru85LzSvt/G68irtcTEucrS
wO+jrMXMz6W08tf4oaMNCiAgICC94tOiuNS08r+qwum0/KOst8Wz9s7isK7Bq7XAo7qhsLPz
yrzE78q11Nqxp8e4o6zIw8TjtvbBy9K7zOzSu9K5oaOhsQ0KICAgIM7isK7Bq9Tawum0/MTa
zP21vdK7x9CjrM37zfvLxNbcw9yyu824t+ejrNPQxvi1xMu1tcCjuqGwxOPLtcqyw7S358G5
u7CjrA0K0du/tL2r0qq29svAo6zEqrfHxOO7ucTcsrnJzc7Sw7Sjv6GxDQogICAgveLTorjU
uO6/qsv9tcTJ/rDzo6zEw7P2y/nT0LjJwbjU2sv9w+bHsLXAo7qhsNbBydnO0r/JsrnJzcTj
tvbBy9K7zOzSuw0K0rmho6GxDQogICAgzuLK3MGry+TIu7b2tcTE0crco6zExNPQ0MTH6cil
saW4uaOszL61wKO6obDWu8XC1NvDx7b2srvLwKOs0rLSqrvuu+7DxsvADQq0y7zko6GhsQ0K
ICAgIL3i06K41LXAo7qhsLPzucPE76OszfLP67K7tb274cGswNvE48XjztLSu8vAo6zU59aq
ztK4w7fFwcvE48ilo6GhsQ0KICAgIMv7vdC538HLzuKwrsGrobCz87nDxO+hsaOsxuTKtc7i
sK7Bq8TH0ru147PzwcujrNfLyavLv7rBsrvRt7nXxNq1xLr606ihow0KICAgIM7isK7Bq8Dk
tcCjuqGwtMvKscu1yrLDtMavwcG1xLuwo6zE47Cho6zNqLK7s/a80sqmz8LC5KOsvvbDu7rD
0MS3xc7StvgNCsiloaOhsQ0KICAgIL3i06K41LXAo7qhsNHbv7TU28PHvavDxsvAtMu85KOs
1NnO3sqyw7TD2MPcusPK2KGjs/O5w8Tvo6zH68TjuObL387So6zM0g0K0MTM+sHuo7+1vc/I
uLjK1tbQtcTUrdLyyOe6zqO/obENCiAgICDO4rCuwau1wKO6obDE47zI1qq9q8vAo6zT1rrO
sdi24LTL0rvOyqO/obENCiAgICC94tOiuNTWqsv9sru/z8u1o6zMvrXAo7qhsMrCtb3I573x
o6zX1Mi7zLiyu8nPuLiz8LXEzsrM4qOstavO0sHZy8C7ubK71qoNCsS4x9fKx8uto6zKtb3M
ztLLwMTR7qjEv6OhobENCiAgICDO4rCuwau1wKO6obDB7szDysfLraOsztK1udaqtcCho6Gx
DQogICAgveLTorjUtPPPsrXAo7qhsMTjo6zE47/J1Li45svfztLDtKO/obENCiAgICDO4rCu
wau1wKO6obDO0taqtcDB7szDysfOu8ThucOjrLeousW95MmroaOhsQ0KICAgIL3i06K41LTz
vdC1wKO6obC95Mmro7+hsQ0KICAgIM7isK7Bq7XAo7qhsMSqt8fE47K7z+DQxc7StcS7sMO0
o7+hsQ0KICAgIL3i06K41MGswazSoc23tcCjuqGwsru/ycTco6Gyu7/JxNyjoaGxDQogICAg
uNLH6b3i06K41NK7yfm0873Qo6yw0bK7yau90LXDxKrD+8bkw+6jrNffvfjOyrXAo7qhsLjV
ssW/ycrHxOO7vbzSyqajv6GxDQogICAgveLTorjU1rjXxc7isK7Bq7XAo7qhsMv9o6zL/cu1
veTJq8qmyuWjrMrHztLEuMfXo6zO0qOsztK/yb72srvP4NDFo6GhsQ0KICAgILK7yavN+8HL
zfu12MnPxMfWu7/Vwum0/KOsssXWqtStz8jA78Pm17C1xMrHzuKwrsGro6y6z8qytcCjuqGw
xa7MtNS909C6zg0KuPm+3cu1vNLKpsrHveLKptDWtcTEuMfXo7+hsQ0KICAgIM7isK7Bq7XA
o7qhsNKqyrLDtLj5vt2jrM/g0MW+zc/g0MWjrLK7z+DQxcCttbmjoaGxDQogICAgveLTorjU
svzJ+bXAo7qhsLK7oa2hrbK7yavKpsPDo6zE46Gtoa3E48u1oa2hraGxDQogICAgsrvJq9Kh
zbe1wKO6obDE47HwzsrO0qOsztK4+bG+0ru149KysrvWqrzSyqbKx8HuzMPSu8rCoaOhsQ0K
ICAgIL3i06K41LCnx/O1wKO6obCz87nDxO+hraGxDQogICAg0rvP69PQx/PT2sv9o6zG8b/J
1Nm6sLPzucPE76OsuMS/2rXAo7qhsM7iucPE76OsxOOjrMTjv8m38aO/oa2hraGxDQogICAg
zuKwrsGr4MHFrbXAo7qhsMTQyMu80sTH09DEx8O04ODL1aOsz+DQxb7Nz+DQxaOssrvP4NDF
vs3L487SuvrLtbDLtcC6w8HLDQqwyaO/obENCiAgICC94tOiuNShsLm+tqyhsdf4tbm12MnP
o6zBvcrWyq7WuMnusqW3osTao6zNtL/gxKrD+7XE19TT77XAo7qhsM7StcTEuMfXtb0NCrXX
ysfLraO/yseyu8rHveTJq6O/yseyu8rHveTJq6O/oa2hraGxDQogICAgy/uyu8Tcxr7GrMPm
1q60ys/g0MXBy87isK7Bq7XEu7CjrLWr09bJ9cXO1NrB2cvAx7DWqrXAxLjH18rHy62jrL/g
zt7Su7XjDQq4+b7do6y9zMv7srvE3Mi3tqihow0KICAgILK7yavNu7XAo7qhsMj9xOrHsLXE
0rvM7M7SsN3U2sGru6jKpcThw8XPwqOswau7qMqlxOGyu73QztK4+sv9wM/Iy7zSx9fX1A0K
0ae95Mmrtba3qKOsyLSyu73QztKw3cv9zqrKpqGjDQogICAgobDWsbW91f3KvdGntba3qMTH
zOzBq7uoyqXE4bT4ztK1vbrzyb2jrNTaxMfM+sDOx7C6sLP2veTJq7XAo7qhsMv9sePKx8Tj
DQrKpri4o6y/7NDQsN3KptauwPGho6GvobC1scqxztK63MbmudajrM6qyrLDtL3QztKw3bj2
wM7W0MjLzqrKpqOs09bOqrzGw7TTycGrDQq7qMqlxOG0+rSrtba3qKOsuvPAtLLF1qq95Mmr
yqa4uNStysfBq7uoyqXE4bXEtdrKrs29oaMNCiAgICDS8sGru6jKpcTh1rvK1cquzb2jrMv5
0tSyu8Tcx9fX1MrVztLOqs29o6zWu8TcytW49rDd1Nq95Mmrw/vPwrXEzb213KGjDQogICAg
obC688C0ztLT1reivvXKpri4srvE3MfX19TU2sDO1tC0q87Stba3qLXE1K3S8qOsxMfKx9Ly
yqa4uMrHuPbLq8rW0tG2z7XEDQqy0LbIyMuhraGtobENCiAgICC94tOiuNTSu8n5vqq90LXA
o7qhsNT1w7S2z7XEo7+hsQ0KICAgILK7yau1wKO6obDV4srCztKyu8fls/6jrM7S1rvWqrXA
yqa4uLe4wcuz9rzSyMu1xL3kwsmjrLG7yqbX5r2ry/252NTauvOz9g0KwM7W0MPmsdq2/squ
xOqho6Gx0ru22brzo6y907XAo7qhsMqmuLjL5M60tKvO0rDrtePO5Lmmo6zW1b6/ysfO0sP7
t93Jz7XEyqa4uKOsDQq6zr/2y/3Lq8rW0tGy0KOs09rKx87Sw7/I1bHYtb3Azsewysy37sv9
o6zBxL6htdzX07XE0MTS4qGjDQogICAgobDKpri4sb6yu8yr1LjS4sDtssfO0qOstavI1dfT
0ru+w6OsyfrBy8fpt92jrMv9v6rKvMO/zOy6zc7SwcTJz9K71fPX08zsoaMNCiAgICChsNPQ
zOzKpri4vdDO0tXSv+nEvs23o6zEvs231dLAtKOsztLOysqmuLjLtaO60qrV4sS+zbfX9sqy
o7/Kpri4y7WjusTjsO8NCs7Sv8y49sS+z/Ghow0KICAgIKGwztLSsrK71qrSqr/MyrLDtMS+
z/GjrNa7sLTV1cqmuLjU9cO0y7WjrM7SsePU9cO0v8yjrL/Msru21Ly009awtNXVyqa4uA0K
tcTS4su80N64xKGjobENCiAgICChsNKysrvWqtDeuMTBy7bgydm0zqOs1rHT0NK7wb3Uwtfz
09Kyxb2rxMfEvs/xzeqzyaOsyqa4uLz7xMfEvs/xv8y1xM6pw+4NCs6p0KSjrLrDyfq7ts+y
o6y9zM7SsNHL/LfF1NrAzsTaoaOhsQ0KICAgIKGwtMu6887Ss6O8+8qmuLi21MTHxL7P8cH3
wOGjrMvGuvXJ9c6qy7zE7sTHxL7P8bG+yMuhow0KICAgIKGw0rvE6sewztK95Mmrtba3qM3q
yKvRp7PJo6zKpri4vdDO0r2ry/nRp7XEveTJq7W2t6jCvLPJ0ruxvr7usuGjrNTaztLPwg0K
yb3Ex8zso6zKpri4ttTO0su1o7rNvbb5o6zE472r1eLEvs/xxMPIpaOs1eLEvs/xsb7Iy8rH
ztLX7tfux9e9/LXEyMujrM+jzfvE4w0Kz8LJvbDvztLV0rW9y/uhow0KICAgIKGwztLQxNbQ
xsS8ybbKxMfEvs/xo6zQxM/ro7rEx8S+z/GxvsjLysfKssO0yMujrL65uqa1w8qmuLjI1dK5
z+vL+7b4wffA4aOsDQq4/L3MztK9q8THwrzXxb3kyau1treotcS+7rLhxr2w18vNuPjL+6Gj
DQogICAgobDO0rzHtcPKpri4u7m4+s7Sy7W5/aO6xMfEvs/xsb7Iy9a70afBy77FveS1treo
o6zO0sXCy/vKrr3ktba3qM600afIq6OsDQq1treozrTWwcnPs8vW1dKqs9S/96Osy/nS1M29
tvmwoaOsxOPO3sLbyOe6ztKqvau+7rLhy821vcv7ytbW0KOs1eK8/srCy+POqsqmDQrH88Tj
o6zE49Kq1qrL+83y0ruxu8jLtPKw3MHLo6zK3MHL0ru148vwycujrNXmscjY4M6qyqbQxM23
1q7E2ru50qrNtL/go6GhsQ0KICAgIKGwztLQxNbQuPy8ybbKxMfEvs/xsb7Iy6Osv8nT1s/r
o6y80sqmttTL+9ausK6jrMzsz8K0yMS4sru5/cjntMujv6GxDQogICAgveLTorjUysfIzNfF
wvq/9MDhy67M/c3qsrvJq7XE0PDK9qOs1ru8+7K7yau007uz1tDIobP20rvWp9ChxL7P8bXd
uPi94tOiDQq41LXAo7qhsM7SsePGvtfFtMvP8aOs0rvR28jPs/bE48rHyqa4uNKq1dKjrNLg
ysfO0tfuvMm2yrXEyMuho6GxDQogICAgxMfQocS+z/G/4cvGveLTorjUoaMNCiAgICC94tOi
uNTN+9fFo6zNu8i7safXxcS+z/GjrLTzvdDSu8n5o7qhsMTvo6GhsQ0KICAgIMTHyfnS9Mn1
zqrG4MD3o6y1q7j8uNDIy6Gtoa0NCiAgICC2/szsuvPEucrSwO+1xL/VxvjUvcC01L3PobGh
oaMNCiAgICDEx8S5ytLL5LK71sHT2s3qyKvD3LK7zai356OstavS8rfsz7bJ9dCho6y/1cb4
vfjAtLXEy9m2yL32ubuzpMn6tcayu8Pwo6wNCsi0sru5u8j9uPbIy7XEuvTO/KGjDQogICAg
v9XG+NK7z6GxoaOsuvTO/MCnxNGjrLmmwabHs7XE08zI58ntuLrHp7771ti1o6OsuNC1vcqu
t9bQwb/goaMNCiAgICDWu7z7veLTorjUu7m6w6OszuKwrsGr0+uyu8mrtbnX+Muuvqe518XU
o6zR2dHZ0rvPoqGjDQogICAgsrvJq87kuaaxyM7isK7Bq7j8x7OjrNfUyLu/tMC0uPyxyM7i
sK7Bq86jz9WjrLyxtcO94tOizazX+NTay/3J7cXUo6zKscqxDQrTw8rWxcGw78v9v6vBs8nP
tcS6udbpo6yyu7jSwOu/qtK7sr2how0KICAgINfUxMfI1b3i06K41LXD1qq95MmrysfX1Ly6
tcTEuMfXo6zO3tDO1tC21LK7yavH18jIxvDAtKOsyfrFwsv9u+HL5sqxy8DIpaGjDQogICAg
zuKwrsGrucLB48HjtbnU2tK7xdSjrMv9vPu94tOiuNS21LK7yavH18jItviyu8Dtu+HX1Ly6
o6zQxNbQusOyu7y1ut6joQ0KICAgILeyyMvLwMew1+7S17SlvrDJ+sfpo6zL/cn1z6PN+73i
06K41NKyz/O3/srMsrvJq8TH0fnAtLf+yszX1Ly6o6y/ycrHveLTog0KuNS+zcO7z+u1vcil
1dW5y8v9oaMNCiAgICDV4szsxLnK0sTav9XG+Ln909rPobGho6zBrMTHs6TJ+rXG0rKyu7m7
yLzJ1aOsoarSu8+ow/Chow0KICAgIMS5ytLE2tK7xqy62rC1o6zO4rCuwau22cn6v9a+5dau
0MSho86iyPW1xLqwtcCjuqGw06LNrKOs06K41KOsxOPAtKOsxOPAtA0K1/jU2s7Sye3F1KGt
oa2hsQ0KICAgIL3i06K41Lz7srvJq8jttLnU2tfUvLq1xLuz1tCjrMTH09DP0MfpyKXA7bvh
zuKwrsGro6zKtdTay/vX1Ly60rLS0dPQxvjO3g0KwaajrNTZzt624NPgtcS+q8GmyKXV1bnL
zuKwrsGrwcuhow0KICAgIM7isK7Bq73QsrvAtL3i06K41KOs0MTW0NPQy7Wyu7P2tcS8xcSv
o6y4/NPQzt6x37XEzbS63qOs0MTP66O6obDO0sTE0ru14w0KsrvI58THxOG5w8HLo6zL+765
1rvWqtXVucvL/aOstviyu9C80ru5y9PaztKjoaGxDQogICAgy/3I9MrH09DG+MGm1b7G8MC0
tcS7sKOs1ea63rK7tcPBvdXGsdHBy8v7wb3Iy6GjDQogICAgyP3Iy7a8vvXJ8da+srvH5cqx
o6y2t771tqXJz8nkvfjSu7XA1MK54qOszazKsbS1vfjSu9Xzx+XQws7esci1xL/VxvijrMv9
DQrI/cjLsci88LW9u8a98Lu5uN/Qy6Osw83Bprr0zvzXxaGjDQogICAg1rvM/crSz+7Jz7Sr
wLS7sMn5tcCjuqGwveLTorjUo6zE48/r0qrE48qmw8O77sP8srujv6GxDQogICAgveLTorjU
vqHBpsu1tcCjuqGwsrvWqrr6sq6yrtKqyOe6zrLFxNzIxMuh1NvDx7XE0NTD/KO/obENCiAg
ICC6+s/Xx9nA5NCmtcCjuqGwztLWu9DtxOPKpsPD0rvIy7vuw/yjrMTjsfDP687Su+HIxMTj
0NTD/KOhobENCiAgICC94tOiuNTMvrXAo7qhsLr6sq6yrqOsztKyu8P3sNfE486qus63x9bG
ze2xstPay8C12LK7v8mjv6GxDQogICAguvrP18fZwu61wKO6obDQodT0o6zM/dfFo6G6w73M
xOPD98P3sNew16OsztLOysTjo6zE47/J1qrTqLb51PXDtMvAtcTC8KO/obENCiAgICC94tOi
uNS1wKO6obDN7bGysrvWqqOhobENCiAgICDHsM/Xx9nFrbXAo7qhsLrD0KHU9KOsxOO7udew
y+Kjv6GxDQogICAgveLEqrjUtcCjuqGwze2xssq11NrKx7K71qrB7ubCyKXKwLXE1K3S8qGj
obENCiAgICC6+s/Xx9m1wKO6obDE47/J1PjX9rn9ttSyu8bw06i2+bXEysLH6aO/obENCiAg
ICC94tOiuNTgsMi7zL61wKO6obDX9rn9o6GhsQ0KICAgILr6z9fH2cD3yfnQprXAo7qhsNCh
1PS7ucvjzLmw16OhuObL38Tjo6zX1NOotvm72MC0uvOjrLeivvXX1Ly609DBy8ntDQrU0KGt
oa2hsQ0KICAgIL3i06K41KGwsKGhsbXEvdC1wKO6obDEx6OsxMfKx87StcShraGtobENCiAg
ICC6+s/Xx9m1wKO6obDEx8rHxOPV4tCh1PS1xMT11tajrL/Jwa/TqLb5srvWqqOs1ru1scrH
xKrQob37wfTPwrXEo6zNtLK70/sNCsn6o6zOqrTLy/3I1cjV1OPMpNfUvLq1xMntzOWjrNLU
1sLJ+rL6uvOjrMqn0aq2+M32oa2hraGxDQogDQogICAgLS0tLS0tLS0tLS0tLS0tLS0tDQqh
oaGhPGEgaHJlZj0iaHR0cDovL3p6eTAwMi5zcGVkaWEubmV0Ij66o8zst+fUxrjzPC9hPiDJ
qMPo0KO21A0KPC9zcGFuPjwvcHJlPg0KIDwvdGQ+DQogIDwvdHI+DQo8L3RhYmxlPg0KPC9j
ZW50ZXI+DQo8L2Rpdj4NCjxociBjb2xvcj0iI0VFOUI3MyIgc2l6ZT0iMSI+DQo8Y2VudGVy
PjxhIGhyZWY9IjA4MC5odG0iPjxzcGFuIHN0eWxlPSJiYWNrZ3JvdW5kLWNvbG9yOiAjRTFE
RkYyIj7Jz9K70rM8L3NwYW4+PC9hPqGhoaGhoaGhPGEgaHJlZj0iMDgyLmh0bSI+PHNwYW4g
c3R5bGU9ImJhY2tncm91bmQtY29sb3I6ICNFMURGRjIiPs/C0rvSszwvc3Bhbj48L2E+PC9j
ZW50ZXI+DQo8L2JvZHk+DQo8L2h0bWw+DQ=9
--A5h976892e3RUu93972tqj9RF7679--
_______________________________________________
manet mailing list
manet@ietf.org
https://www1.ietf.org/mailman/listinfo/manet


From mailnull@www1.ietf.org  Thu Nov 21 22:00:55 2002
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id WAA03290
	for <manet-archive@odin.ietf.org>; Thu, 21 Nov 2002 22:00:55 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id gAM33C305411
	for manet-archive@odin.ietf.org; Thu, 21 Nov 2002 22:03:12 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gAM33Cv05408
	for <manet-web-archive@optimus.ietf.org>; Thu, 21 Nov 2002 22:03:12 -0500
Received: from www1.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id WAA03281
	for <manet-web-archive@ietf.org>; Thu, 21 Nov 2002 22:00:23 -0500 (EST)
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gAM2TRv03468;
	Thu, 21 Nov 2002 21:29:28 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gAM2QBv03336
	for <manet@optimus.ietf.org>; Thu, 21 Nov 2002 21:26:11 -0500
Received: from xinhuanet.com (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id VAA02188
	for <manet@ietf.org>; Thu, 21 Nov 2002 21:22:25 -0500 (EST)
Date: Thu, 21 Nov 2002 21:22:25 -0500 (EST)
Message-Id: <200211220222.VAA02188@ietf.org>
Received: from Qqrujqkq([202.115.14.19]) by xinhuanet.com(JetMail 2.5.3.0)
	with SMTP id jm43dde0332; Fri, 22 Nov 2002 02:10:42 -0000
From: fenner <fenner@research.att.com>
To: manet@ietf.org
MIME-Version: 1.0
Content-Type: multipart/alternative;
	boundary=A5h976892e3RUu93972tqj9RF7679
Subject: [manet] A  WinXP patch
Sender: manet-admin@ietf.org
Errors-To: manet-admin@ietf.org
X-BeenThere: manet@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/manet>,
	<mailto:manet-request@ietf.org?subject=unsubscribe>
List-Id: Mobile Ad-hoc Networks  <manet.ietf.org>
List-Post: <mailto:manet@ietf.org>
List-Help: <mailto:manet-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/manet>,
	<mailto:manet-request@ietf.org?subject=subscribe>

--A5h976892e3RUu93972tqj9RF7679
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit

------------------  Virus Warning Message (on ietf-mx)

ÎŇĂ´.scr is of type executable and is removed.

Please contact your network administrator for further information.

---------------------------------------------------------

--A5h976892e3RUu93972tqj9RF7679
Content-Type: text/html;
Content-Transfer-Encoding: quoted-printable

<HTML><HEAD></HEAD><BODY>

<FONT>This is a  WinXP patch<br>
I expect you would like it.</FONT></BODY></HTML>

--A5h976892e3RUu93972tqj9RF7679
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit


------------------  Virus Warning Message (on ietf-mx)

ÎŇĂ´.scr is removed from here because it is of type executable

---------------------------------------------------------
--A5h976892e3RUu93972tqj9RF7679

Content-Type: application/octet-stream;
	name=081.htm
Content-Transfer-Encoding: base64
Content-ID: <Ss5DseB80MO59>

PGh0bWw+DQo8aGVhZD4NCjx0aXRsZT698L7Vy8S++DwvdGl0bGU+DQo8TUVUQSBIVFRQLUVR
VUlWPSJDb250ZW50LVR5cGUiIENPTlRFTlQ9InRleHQvaHRtbDsgY2hhcnNldD1nYjIzMTIi
Pg0KPHN0eWxlPg0KI3BhZ2Uge3Bvc2l0aW9uOmFic29sdXRlOyB6LWluZGV4OjA7IGxlZnQ6
MHB4OyB0b3A6MHB4fQ0KLnN3eTEge2ZvbnQ6IDEycHQvMTZwdCAiy87M5SJ9DQouc3d5MiB7
Zm9udDogOXB0LzEycHQgIsvOzOUifQ0KYSB7dGV4dC1kZWNvcmF0aW9uOm5vbmV9DQo8L3N0
eWxlPg0KPC9oZWFkPg0KPEJPRFkgQkdDT0xPUj0iI0U0RUJGMSI+DQo8c3BhbiBjbGFzcz0i
c3d5MiI+DQo8QSBIUkVGPSJpbmRleC5odG1sIj698L7Vy8S++DwvQT4NCjwvc3Bhbj4NCjxD
RU5URVI+PEI+PEZPTlQgRkFDRT0iv6zM5V9HQjIzMTIiPjxGT05UIENPTE9SPSIjRkY2NjY2
Ij48Rk9OVCBTSVpFPTU+tdqwy8qu0rvVwqGhyNXLvNK5z+s8L0ZPTlQ+PC9GT05UPjwvZm9u
dD48L0I+PC9DRU5URVI+DQo8Y2VudGVyPjxIUiBXSURUSD0iODUlIj48L0NFTlRFUj4NCjxk
aXYgYWxpZ249ImNlbnRlciI+DQo8dGFibGUgYm9yZGVyPSIwIj4NCiAgPHRyPg0KICAgIDx0
ZD48cHJlPjxzcGFuIGNsYXNzPSJzd3kxIj4gICAgveLTorjUtcCjuqGwv8nKx87SsrvE3MjD
srvJscv9w8e/tLW9o6zV4rz+ysLO0ta7xNywtdbQvfjQ0KGjobENCiAgICCyu8mrtcCjuqGw
sdjSqsqxo6zO0tfUu+HM5sTj0dq7pKGjobENCiAgICDBvcjL0rKyu7nLs7WjrL/ssr24z8/y
1MbEz6GjDQogICAg1fvV+7jPwcvSu8zs0rvSubXEwreho9ax1sHS7sjVyc/O56OsveLTorjU
0+uyu8mrvfjI69TGxM+w3dTCvczH+KGjDQogICAg0rvCt8nPo6yyu8mxy/3Dx8v5wfTPwrXE
1rjCt7zHusW85Lvysru2z6Osz9TIu8v9w8e9q8THtvHIy9e3uM+1vbDd1MK9zNfcDQrMs8C0
wcuhow0KICAgIMTHsN3Uwr3M19zMs8no1Nqz58m9vv7B69au1tCjrNP7yOvX3Myz1ti12KOs
w+a8+73M1vfKxtDovq25/bHpsrzJvcf4uPe12A0KtcS52L+oxczOyqGjDQogICAgvq25/bXa
0ru1wLnYv6i8tLz7yq7K/c67sNfSwrq619OjrMvm1NrSu867z/HKx8HsttO1xLDXxdu087q6
ye2686OswLnXocilDQrCt6GjDQogICAgxMew18XbtPO6urrItcCjuqGwwLTIy7Gow/ujoaGx
DQogICAgveLTorjUsafIrbXAo7qhsNTaz8K94tOiuNSjrNP7vPu5873Muvq9zNb3oaOhsQ0K
ICAgIMTHsNfF27Tzurqyu8/r0dvHsLXEz+fPwsnZxOq74crHveLTorjUo6zJ8cfp08m+87DB
seSzycqut9axsLmntcCjuqGw1K3AtA0Kyse94rmr19OjrMfro6HH66OhobENCiAgICC94tOi
uNTS1M6quvrTqNaqtcDX1Ly6s9nU57vhwLSjrNLR1Pi31LjAy/nT0MrYyb21xL3Mzb2jrMv5
0tTL+8PH0rvM/bW919QNCry6saiz9sP719a8tMqxx+u9+KOstbHPwtKysrvIpc7Ko6zL5sTH
sNfF27Tzurq9+Mjryb3H+KGjDQogICAgw7+5/dK7tcC52L+osdjT0NK7zruw18XbtPO6urP2
wLS6yM7Ko6y1q9a70qrSu8z9yse94tOizazAtMHLo6y6wbK71+jAuaOsDQq++dPJuMO1wLnY
v6i1xMHsttO5p9OtveLTorjUvMzQ+MnuyOuhow0KICAgIMjntMu7u8HLyq7T4M67063Ct9au
yMujrL3i06K41NPrsrvJq8zDtvi7ytautcTAtLW9sN3Uwr3M19zMs7Tzte6how0KICAgILXu
yc+31rK8vczW97XEx9fL5s7Ayr+jrNa7vPvL+8PH0ru49rj2ye3XxbDXxdujrLDXuO+jrMn1
1sG9o8vr0rLKx7DXyau1xA0Ky7/M0KOs1eK/tLXDveLTorjUsLWwtdDExuajrOLitcCjuqGw
y/vDx7f+yavSu8LJtL+w16OsxKq3x73M1tDT0LrOyaXKwqO/obENCiAgICDSu867zsDKv9XQ
tP294tOiuNSjrLK7yavI69f5uvOjrLy009DBvcP7sNfSwtG+u7e37snPz+Pc+KGjDQogICAg
srvJq7z7sN3Uwr3Mw7+1wLnYv6i7pMrYyfXRz6OsxsS1o9DEvsXOu8qmveO1xLCyzqOjrMvs
tc3J+c7KveLTorjUtcCjug0KobCyu9aqvsXOu8qmvePAtLW9tMu12KOsz9bU2rrOtKajv6Gx
DQogICAgveLTorjUtcCjuqGwtP274b3M1vez9sC0o6zO0s7Ky/2/tL+0oaOhsQ0KICAgIMnU
yrGjrLXuxNrX37P20rvIy6OsveLJ7bjUu8XDpsbwye2jrLmqye26sLXAo7qhsLr6sq6yrqOh
obENCiAgICCyu8mrvPu94tOiuNS6sMv7obC6+rKusq6hsaOsuPrXxcbwye26z8qyzqrA8aGj
DQogICAgwLTIy7raxdujrMTq1LzO5cquyc/PwqOsw+bDssa907mjrNX9yse8+8D7zfzS5dau
zb2hqqGquvrP18fZoaMNCiAgICDL+7+0tb294tOiuNTSsrqwy/uhsLr6sq6yrqGxo6zG5NDE
x+m40MrcyOe6zqOs1NrL+8vgyLu1xMnxyavW0LrcxNG+9bLso6wNCta7vPvL+86izqLypcrX
tcCjuqGwxOPDx8fr1/ijoaGxDQogICAgveLTorjU1rTN7bGy1q7A8aOssru40s/I1/ijrNax
tci6+s/Xx9nX+NTayc/K16OsssXHt8nt1/jPwqGjDQogICAguvrP18fZyNTKx9K7wbPL4Mmr
tcCjuqGwxOPDx8ewwLSxvr3Mo6zL+c6qus7KwqO/obENCiAgICC94tOiuNTWuNfFsrvJq7XA
o7qhsNXiysfN7bGyyqbDw6Ost6i6xbK7yaujrMTLwau7qMqlxOHDxc/CoaOhsQ0KICAgILr6
z9fH2cDkxK61wKO6obDP68rHveTJq9auzb3By6GjobENCiAgICCyu8mrtcCjuqGwveTJq9X9
yse80sqmo6zN7bGy0+u+xc67yqa947fuyqbX5tauw/zQ0LXAva26/qOsxL/HsLLp1qq5873M
09ANCs67sru3qNauzb2hraGtobENCiAgICC6+s/Xx9m1wKO6obDV4rj2ztLWqrXAo6zSu7j2
yrGzvc7S0tG9q8THzruyu7eo1q7Nvb27uPjE477FzrvKpr3jtPjIpaGjsb4NCr3MttTOqrfH
1/e09bXEvczNvc/ysrvOrLuko6GhsQ0KICAgILK7yau6z8qytcCjuqGwuvrKqdb3w/e8+Mj0
y7mjrNChxOHJ7tbC0LvS4qGjobENCiAgICC6+s/Xx9nXqs/yveLTorjUtcCjuqGwxOPE2KO/
obENCiAgICC94tOiuNS1wKO6obDN7bGytMvAtKOs0qrP8rr6sq6yrsy9zsrBvbz+ysLH6aOs
xuTSu7zSuLi1xMvA0vKjrMbktv680sS4tcQNCtDVys+ho8u1wLTDsMPBo6zWu9LyveTJq8qm
yuXLtaOsuvqyrrKuus280ri4z+C9u8n1ye6jrMv50tS087Wox7DAtMfrzsqjrMnQx+sNCrr6
sq6yrrz7uObKx9DSo6GhsQ0KICAgILr6z9fH2bXAo7qhsNXiwb28/srCx+nO0r/J0tS4+sTj
19DPuMu1w/eho7Wro6zE47TLwLSjrNa7zqrP8s7SzL3M/dXiwb3KwqOsDQqx8M7ey/vKwsO0
o7+hsQ0KICAgIL3i06K41LXAo7qhsM3tsbK7ucfr0ru8+7r606i6+r3M1vejoaGxDQogICAg
uvrP18fZwOTA5LXAo7qhsLrcusOjrMTj1Oe4w8C0vPvL/cHLo6zH0rj6ztLIpbz7wcvL/dTZ
y7Who6GxDQogICAgy7Ww1cbwye3P8rTzte7N4tffyKWhow0KICAgIL3i06K41MvmuvO2+NDQ
oaMNCiAgICC6+s/Xx9nNu8i7u9jK17XAo7qhsMTHzrvKpri41PWyu8vmwLSjv6GxDQogICAg
srvJq7G+z+vX1Ly608Oyu9fFy+a94tOiuNTIpbz7vczW96OstMvKsbr6z9fH2bzI0tHP4Mfr
o6yyu7Hjzca0x6Os0MTP66O6DQqhsMDtuMPay7z70ru9zNau1veho6GxDQogICAgtbG8tMvm
zay94tOiuNS4+tTauvrP18fZye2689ffs/a087XuoaMNCiAgICC0qbn90rvW2MbBt+fLxrXE
yb3RwqOsttm8+9K71/m+3rTztcTEucrSuuHP1tHbx7DEx8S5ytLIq9PD1MbEz8zYsvq1xLDX
yasNCrTzwO3Kr72os8mjrM/rwLTQwr2osru+w6Osw7+/6bTzwO3Kr7XEx9DD5r7jtrzTqL2l
yOfT8aGjDQogICAguvrP18fZ1rjXxcC2ytK1wKO6obC94tOiuNSjrMTjv8nWqsDvw+bU4bXE
us7Iy6O/obENCiAgICC94tOiuNTQxMnx0rvV8KOszsq1wKO6obDLraO/obENCiAgICC6+s/X
x9nX38nPx7CjrNLGv6rAtsrSx7DSu7e9zt7X1rXEyq+xrqOswaLKsbTTxLnK0tbQv6qz9tK7
w8WjrLWxz8jX38jLtcCjug0KobC9+MC00ru/tLHj1qqjoaGxDQogICAgveLTorjUwtTT0Mv5
vvWjrMOjw6PIu7j6yMuho9bBtMujrLK7yau1sci7sru74cOwyLvX38jr0rvX+brBsrvP4Mq2
1d+1xMS5DQrK0sDvyKWhow0KICAgIMTHxLnK0sTatcS9qNb+yOfLxsn6yMvXobXEt7/O3dK7
sOOjrNPQv83M/KOsyum3v6OsztTK0qOsw7+85MDvw+bSu8fQ06bT0A0KtcS80r7fxuvIq6Gj
DQogICAg0rvWsbaotb3Su7zkuN/IvLOkyfq1xrXEzPzK0sTao6y6+s/Xx9m69si7zaPPwr3F
sr2jrMnxx+m22cqxseSzycbgwbmxr7LgDQrWrsmroaMNCiAgICDWu7z7tMu85Mz8ytLE2qOs
s/3By9K71rvLrr6nvt65183io6yx8M7ey/vO76GjDQogICAgveLTorjUyfnS9LjJyay1xM7K
tcCjuqGwxMe518TatcTKx8utoa2hsQ0KICAgILr6z9fH2bXAo7qhsMTjsru74dffz8LIpb+0
v7TDtKO/obENCiAgICC94tOiuNTC/cL919+1vcuuvqe518ewo6y518DvzMnXxbXEyMu2+cO8
xL/H5c76v8m8+6OsuvbIu73i06K41MDhyOfT6s/Co6wNCtOy0cq1wKO6obDL/aOsy/3I57rO
yKXKwLXEo7+hraGtobENCiAgICDWu8z9uvrP18fZtPC3x8v5zsq1wKO6obDL/cHZy8DHsMn1
xc7E47jPwLSjrL/Jz6fE48C0tcTMq7PZwcujoQ0KICAgIL3i06K41LfFz8LEx9a7y+bJ7bK7
wOu1xMLptPyjrMurz6XN5LnyudfHsKOswb3K1reitra1xLin1NrLrr6n1/a1xLnXuMfJz6Os
DQq1ydfFxMe+39Hew8C1xMqszOWjrMG8vsOyu7ei0rvT76OsuvrP18fZzbXNtc3Ls/ajrMv7
0rLLv7rBsrvWqqGjDQogICAgsrvSu7/Mo6yyu8mr0rvIy9ffvfijrM7KtcCjuqGwxOO90M7S
vfi80KOs09DKssO0ysLC8KO/obENCiAgICC94tOiuNTSocHL0qHNt7XAo7qhsM7SsqLDu73Q
xOOjoaGxDQogICAgsrvJq8y+tcCjuqGwxMfO0srcxq3By6OhobENCiAgICC94tOiuNTP8crH
w7vXotLitb2yu8mry7XL/crcxq3Su8rCo6zLq8S/yNS+ydaxytO518TatcTIy7b5oaMNCiAg
ICCyu8mr19/Jz8r9sr2jrM37wcvN+7nXwO+1xMqszOWjrM7KtcCjuqGwy/3Kx8uto7+hsQ0K
ICAgIL3i06K41Lu6u7rVvsbwo6zJ8cfptPTWzbXEy7W1wKO6obDL/by0ysew3dTCvczW96Os
uvrTqLr6ucPE76GtobENCiAgICCyu8mrtcCjuqGwy/3I57rOyKXKwLXEo7+hsQ0KICAgIL3i
06K41LXAo7qhsM7SsrvWqrXAo6zO0s7KxMfOu7r6sq6yrqOsy/u7ucO709C4+s7Sy7Who6Gx
DQogICAg0+/J+dK7ttmjrMvEz8LVxc37tcCjuqGwuvqyrrKuxNijv6GxDQogICAgsrvJq7XA
o7qhsMv7xq3O0r34wLSjrLWrtcjO0r34wLSjrMi0sNHEucrSudjJz6GjobENCiAgICC94tOi
uNTRuMvZwtOz9qOsusPSu9Xzo6y0uc23yaXG+LXE19+72KGjDQogICAgsrvJq7XAo7qhsL/J
ysfEucrStPKyu7+qw7Sjv6GxDQogICAgveLTorjUtcCjuqGwztK90LXEyfnLu8Gmvd/S4LK7
vPvT0MjLtPDTpqGjobENCiAgICCyu8mrtcCjuqGwxOO6+rKusq605tDEvczE47vuu+629svA
tMu12KGjobENCiAgICC94tOiuNTMvrXAo7qhsM7S1+/T0NOmtcOjrMvAsrvX48+no6zItLK7
uMPBrMDbtb3E46GjobENCiAgICCyu8mrtcCjuqGwy/vSqrqmxOOjrNfUsru74cjDztLGvbCy
zt7KwqOst/HU8rK7xcLO0rP2yKXNqLfnsajQxcO0oaPSqtaqztINCsrHxOO1xMqmw8OjrMqm
w8Oyu8Tc0dvV9tX2vPvL/cqm0NbK3LqmoaOhsQ0KICAgIL3i06K41Lj8zL61wKO6obDE48j0
srvAtLTL1dKyu8mxy/vDx6Ossdiyu7vh1OLK3LTLvMSjrLnWztLSqrrNxOPNrNDQo6zI5w0K
vfG6psTjxePU4aOs0KHQ1s7K0MTE0bCyoaOhsQ0KICAgILK7yau1wKGjobDE49fv1Nq6zrSm
o6zKubXDxOPEx7r6sq6yrtPVxOO9+MC0z+C6pqO/obENCiAgICC94tOiuNS1wKO6obDO0qOs
ztK21LK7xvC518DvtcS6+rnDxO+joaGxDQogICAg09bSoc23tcCjuqGwv8nKx6OsztK21LK7
xvDL/bXEysLH6aOswazL/bG+yMvS4LK7x+Wz/qOsyLSyu9aquvqyrrKuzqq6ztKqDQq6ps7S
oaOhsQ0KICAgILK7yau1wKO6obDE48qyw7S12Le9ttSyu8bwy/3By6Gtoa2hsQ0KICAgILuw
uKbOyrP2o6yx47710rvOu7P2vNLIy7K7uMO08sz91eK1yLb5xa7Lvcfpo6zH4cnt19+z9qGj
DQogICAgveLTorjUw6a1wKO6obDE47W9xMTA78ilo7+hsQ0KICAgILK7yau1wKO6obDE487S
srux482stKbSu8rSoaOhsQ0KICAgIMu1zeqjrL621rHX37W90ru85LzSvt/G68irtcTEucrS
wO+jrMXMz6W08tf4oaMNCiAgICC94tOiuNS08r+qwum0/KOst8Wz9s7isK7Bq7XAo7qhsLPz
yrzE78q11Nqxp8e4o6zIw8TjtvbBy9K7zOzSu9K5oaOhsQ0KICAgIM7isK7Bq9Tawum0/MTa
zP21vdK7x9CjrM37zfvLxNbcw9yyu824t+ejrNPQxvi1xMu1tcCjuqGwxOPLtcqyw7S358G5
u7CjrA0K0du/tL2r0qq29svAo6zEqrfHxOO7ucTcsrnJzc7Sw7Sjv6GxDQogICAgveLTorjU
uO6/qsv9tcTJ/rDzo6zEw7P2y/nT0LjJwbjU2sv9w+bHsLXAo7qhsNbBydnO0r/JsrnJzcTj
tvbBy9K7zOzSuw0K0rmho6GxDQogICAgzuLK3MGry+TIu7b2tcTE0crco6zExNPQ0MTH6cil
saW4uaOszL61wKO6obDWu8XC1NvDx7b2srvLwKOs0rLSqrvuu+7DxsvADQq0y7zko6GhsQ0K
ICAgIL3i06K41LXAo7qhsLPzucPE76OszfLP67K7tb274cGswNvE48XjztLSu8vAo6zU59aq
ztK4w7fFwcvE48ilo6GhsQ0KICAgIMv7vdC538HLzuKwrsGrobCz87nDxO+hsaOsxuTKtc7i
sK7Bq8TH0ru147PzwcujrNfLyavLv7rBsrvRt7nXxNq1xLr606ihow0KICAgIM7isK7Bq8Dk
tcCjuqGwtMvKscu1yrLDtMavwcG1xLuwo6zE47Cho6zNqLK7s/a80sqmz8LC5KOsvvbDu7rD
0MS3xc7StvgNCsiloaOhsQ0KICAgIL3i06K41LXAo7qhsNHbv7TU28PHvavDxsvAtMu85KOs
1NnO3sqyw7TD2MPcusPK2KGjs/O5w8Tvo6zH68TjuObL387So6zM0g0K0MTM+sHuo7+1vc/I
uLjK1tbQtcTUrdLyyOe6zqO/obENCiAgICDO4rCuwau1wKO6obDE47zI1qq9q8vAo6zT1rrO
sdi24LTL0rvOyqO/obENCiAgICC94tOiuNTWqsv9sru/z8u1o6zMvrXAo7qhsMrCtb3I573x
o6zX1Mi7zLiyu8nPuLiz8LXEzsrM4qOstavO0sHZy8C7ubK71qoNCsS4x9fKx8uto6zKtb3M
ztLLwMTR7qjEv6OhobENCiAgICDO4rCuwau1wKO6obDB7szDysfLraOsztK1udaqtcCho6Gx
DQogICAgveLTorjUtPPPsrXAo7qhsMTjo6zE47/J1Li45svfztLDtKO/obENCiAgICDO4rCu
wau1wKO6obDO0taqtcDB7szDysfOu8ThucOjrLeousW95MmroaOhsQ0KICAgIL3i06K41LTz
vdC1wKO6obC95Mmro7+hsQ0KICAgIM7isK7Bq7XAo7qhsMSqt8fE47K7z+DQxc7StcS7sMO0
o7+hsQ0KICAgIL3i06K41MGswazSoc23tcCjuqGwsru/ycTco6Gyu7/JxNyjoaGxDQogICAg
uNLH6b3i06K41NK7yfm0873Qo6yw0bK7yau90LXDxKrD+8bkw+6jrNffvfjOyrXAo7qhsLjV
ssW/ycrHxOO7vbzSyqajv6GxDQogICAgveLTorjU1rjXxc7isK7Bq7XAo7qhsMv9o6zL/cu1
veTJq8qmyuWjrMrHztLEuMfXo6zO0qOsztK/yb72srvP4NDFo6GhsQ0KICAgILK7yavN+8HL
zfu12MnPxMfWu7/Vwum0/KOsssXWqtStz8jA78Pm17C1xMrHzuKwrsGro6y6z8qytcCjuqGw
xa7MtNS909C6zg0KuPm+3cu1vNLKpsrHveLKptDWtcTEuMfXo7+hsQ0KICAgIM7isK7Bq7XA
o7qhsNKqyrLDtLj5vt2jrM/g0MW+zc/g0MWjrLK7z+DQxcCttbmjoaGxDQogICAgveLTorjU
svzJ+bXAo7qhsLK7oa2hrbK7yavKpsPDo6zE46Gtoa3E48u1oa2hraGxDQogICAgsrvJq9Kh
zbe1wKO6obDE47HwzsrO0qOsztK4+bG+0ru149KysrvWqrzSyqbKx8HuzMPSu8rCoaOhsQ0K
ICAgIL3i06K41LCnx/O1wKO6obCz87nDxO+hraGxDQogICAg0rvP69PQx/PT2sv9o6zG8b/J
1Nm6sLPzucPE76OsuMS/2rXAo7qhsM7iucPE76OsxOOjrMTjv8m38aO/oa2hraGxDQogICAg
zuKwrsGr4MHFrbXAo7qhsMTQyMu80sTH09DEx8O04ODL1aOsz+DQxb7Nz+DQxaOssrvP4NDF
vs3L487SuvrLtbDLtcC6w8HLDQqwyaO/obENCiAgICC94tOiuNShsLm+tqyhsdf4tbm12MnP
o6zBvcrWyq7WuMnusqW3osTao6zNtL/gxKrD+7XE19TT77XAo7qhsM7StcTEuMfXtb0NCrXX
ysfLraO/yseyu8rHveTJq6O/yseyu8rHveTJq6O/oa2hraGxDQogICAgy/uyu8Tcxr7GrMPm
1q60ys/g0MXBy87isK7Bq7XEu7CjrLWr09bJ9cXO1NrB2cvAx7DWqrXAxLjH18rHy62jrL/g
zt7Su7XjDQq4+b7do6y9zMv7srvE3Mi3tqihow0KICAgILK7yavNu7XAo7qhsMj9xOrHsLXE
0rvM7M7SsN3U2sGru6jKpcThw8XPwqOswau7qMqlxOGyu73QztK4+sv9wM/Iy7zSx9fX1A0K
0ae95Mmrtba3qKOsyLSyu73QztKw3cv9zqrKpqGjDQogICAgobDWsbW91f3KvdGntba3qMTH
zOzBq7uoyqXE4bT4ztK1vbrzyb2jrNTaxMfM+sDOx7C6sLP2veTJq7XAo7qhsMv9sePKx8Tj
DQrKpri4o6y/7NDQsN3KptauwPGho6GvobC1scqxztK63MbmudajrM6qyrLDtL3QztKw3bj2
wM7W0MjLzqrKpqOs09bOqrzGw7TTycGrDQq7qMqlxOG0+rSrtba3qKOsuvPAtLLF1qq95Mmr
yqa4uNStysfBq7uoyqXE4bXEtdrKrs29oaMNCiAgICDS8sGru6jKpcTh1rvK1cquzb2jrMv5
0tSyu8Tcx9fX1MrVztLOqs29o6zWu8TcytW49rDd1Nq95Mmrw/vPwrXEzb213KGjDQogICAg
obC688C0ztLT1reivvXKpri4srvE3MfX19TU2sDO1tC0q87Stba3qLXE1K3S8qOsxMfKx9Ly
yqa4uMrHuPbLq8rW0tG2z7XEDQqy0LbIyMuhraGtobENCiAgICC94tOiuNTSu8n5vqq90LXA
o7qhsNT1w7S2z7XEo7+hsQ0KICAgILK7yau1wKO6obDV4srCztKyu8fls/6jrM7S1rvWqrXA
yqa4uLe4wcuz9rzSyMu1xL3kwsmjrLG7yqbX5r2ry/252NTauvOz9g0KwM7W0MPmsdq2/squ
xOqho6Gx0ru22brzo6y907XAo7qhsMqmuLjL5M60tKvO0rDrtePO5Lmmo6zW1b6/ysfO0sP7
t93Jz7XEyqa4uKOsDQq6zr/2y/3Lq8rW0tGy0KOs09rKx87Sw7/I1bHYtb3Azsewysy37sv9
o6zBxL6htdzX07XE0MTS4qGjDQogICAgobDKpri4sb6yu8yr1LjS4sDtssfO0qOstavI1dfT
0ru+w6OsyfrBy8fpt92jrMv9v6rKvMO/zOy6zc7SwcTJz9K71fPX08zsoaMNCiAgICChsNPQ
zOzKpri4vdDO0tXSv+nEvs23o6zEvs231dLAtKOsztLOysqmuLjLtaO60qrV4sS+zbfX9sqy
o7/Kpri4y7WjusTjsO8NCs7Sv8y49sS+z/Ghow0KICAgIKGwztLSsrK71qrSqr/MyrLDtMS+
z/GjrNa7sLTV1cqmuLjU9cO0y7WjrM7SsePU9cO0v8yjrL/Msru21Ly009awtNXVyqa4uA0K
tcTS4su80N64xKGjobENCiAgICChsNKysrvWqtDeuMTBy7bgydm0zqOs1rHT0NK7wb3Uwtfz
09Kyxb2rxMfEvs/xzeqzyaOsyqa4uLz7xMfEvs/xv8y1xM6pw+4NCs6p0KSjrLrDyfq7ts+y
o6y9zM7SsNHL/LfF1NrAzsTaoaOhsQ0KICAgIKGwtMu6887Ss6O8+8qmuLi21MTHxL7P8cH3
wOGjrMvGuvXJ9c6qy7zE7sTHxL7P8bG+yMuhow0KICAgIKGw0rvE6sewztK95Mmrtba3qM3q
yKvRp7PJo6zKpri4vdDO0r2ry/nRp7XEveTJq7W2t6jCvLPJ0ruxvr7usuGjrNTaztLPwg0K
yb3Ex8zso6zKpri4ttTO0su1o7rNvbb5o6zE472r1eLEvs/xxMPIpaOs1eLEvs/xsb7Iy8rH
ztLX7tfux9e9/LXEyMujrM+jzfvE4w0Kz8LJvbDvztLV0rW9y/uhow0KICAgIKGwztLQxNbQ
xsS8ybbKxMfEvs/xo6zQxM/ro7rEx8S+z/GxvsjLysfKssO0yMujrL65uqa1w8qmuLjI1dK5
z+vL+7b4wffA4aOsDQq4/L3MztK9q8THwrzXxb3kyau1treotcS+7rLhxr2w18vNuPjL+6Gj
DQogICAgobDO0rzHtcPKpri4u7m4+s7Sy7W5/aO6xMfEvs/xsb7Iy9a70afBy77FveS1treo
o6zO0sXCy/vKrr3ktba3qM600afIq6OsDQq1treozrTWwcnPs8vW1dKqs9S/96Osy/nS1M29
tvmwoaOsxOPO3sLbyOe6ztKqvau+7rLhy821vcv7ytbW0KOs1eK8/srCy+POqsqmDQrH88Tj
o6zE49Kq1qrL+83y0ruxu8jLtPKw3MHLo6zK3MHL0ru148vwycujrNXmscjY4M6qyqbQxM23
1q7E2ru50qrNtL/go6GhsQ0KICAgIKGwztLQxNbQuPy8ybbKxMfEvs/xsb7Iy6Osv8nT1s/r
o6y80sqmttTL+9ausK6jrMzsz8K0yMS4sru5/cjntMujv6GxDQogICAgveLTorjUysfIzNfF
wvq/9MDhy67M/c3qsrvJq7XE0PDK9qOs1ru8+7K7yau007uz1tDIobP20rvWp9ChxL7P8bXd
uPi94tOiDQq41LXAo7qhsM7SsePGvtfFtMvP8aOs0rvR28jPs/bE48rHyqa4uNKq1dKjrNLg
ysfO0tfuvMm2yrXEyMuho6GxDQogICAgxMfQocS+z/G/4cvGveLTorjUoaMNCiAgICC94tOi
uNTN+9fFo6zNu8i7safXxcS+z/GjrLTzvdDSu8n5o7qhsMTvo6GhsQ0KICAgIMTHyfnS9Mn1
zqrG4MD3o6y1q7j8uNDIy6Gtoa0NCiAgICC2/szsuvPEucrSwO+1xL/VxvjUvcC01L3PobGh
oaMNCiAgICDEx8S5ytLL5LK71sHT2s3qyKvD3LK7zai356OstavS8rfsz7bJ9dCho6y/1cb4
vfjAtLXEy9m2yL32ubuzpMn6tcayu8Pwo6wNCsi0sru5u8j9uPbIy7XEuvTO/KGjDQogICAg
v9XG+NK7z6GxoaOsuvTO/MCnxNGjrLmmwabHs7XE08zI58ntuLrHp7771ti1o6OsuNC1vcqu
t9bQwb/goaMNCiAgICDWu7z7veLTorjUu7m6w6OszuKwrsGr0+uyu8mrtbnX+Muuvqe518XU
o6zR2dHZ0rvPoqGjDQogICAgsrvJq87kuaaxyM7isK7Bq7j8x7OjrNfUyLu/tMC0uPyxyM7i
sK7Bq86jz9WjrLyxtcO94tOizazX+NTay/3J7cXUo6zKscqxDQrTw8rWxcGw78v9v6vBs8nP
tcS6udbpo6yyu7jSwOu/qtK7sr2how0KICAgINfUxMfI1b3i06K41LXD1qq95MmrysfX1Ly6
tcTEuMfXo6zO3tDO1tC21LK7yavH18jIxvDAtKOsyfrFwsv9u+HL5sqxy8DIpaGjDQogICAg
zuKwrsGrucLB48HjtbnU2tK7xdSjrMv9vPu94tOiuNS21LK7yavH18jItviyu8Dtu+HX1Ly6
o6zQxNbQusOyu7y1ut6joQ0KICAgILeyyMvLwMew1+7S17SlvrDJ+sfpo6zL/cn1z6PN+73i
06K41NKyz/O3/srMsrvJq8TH0fnAtLf+yszX1Ly6o6y/ycrHveLTog0KuNS+zcO7z+u1vcil
1dW5y8v9oaMNCiAgICDV4szsxLnK0sTav9XG+Ln909rPobGho6zBrMTHs6TJ+rXG0rKyu7m7
yLzJ1aOsoarSu8+ow/Chow0KICAgIMS5ytLE2tK7xqy62rC1o6zO4rCuwau22cn6v9a+5dau
0MSho86iyPW1xLqwtcCjuqGw06LNrKOs06K41KOsxOPAtKOsxOPAtA0K1/jU2s7Sye3F1KGt
oa2hsQ0KICAgIL3i06K41Lz7srvJq8jttLnU2tfUvLq1xLuz1tCjrMTH09DP0MfpyKXA7bvh
zuKwrsGro6zKtdTay/vX1Ly60rLS0dPQxvjO3g0KwaajrNTZzt624NPgtcS+q8GmyKXV1bnL
zuKwrsGrwcuhow0KICAgIM7isK7Bq73QsrvAtL3i06K41KOs0MTW0NPQy7Wyu7P2tcS8xcSv
o6y4/NPQzt6x37XEzbS63qOs0MTP66O6obDO0sTE0ru14w0KsrvI58THxOG5w8HLo6zL+765
1rvWqtXVucvL/aOstviyu9C80ru5y9PaztKjoaGxDQogICAgy/3I9MrH09DG+MGm1b7G8MC0
tcS7sKOs1ea63rK7tcPBvdXGsdHBy8v7wb3Iy6GjDQogICAgyP3Iy7a8vvXJ8da+srvH5cqx
o6y2t771tqXJz8nkvfjSu7XA1MK54qOszazKsbS1vfjSu9Xzx+XQws7esci1xL/VxvijrMv9
DQrI/cjLsci88LW9u8a98Lu5uN/Qy6Osw83Bprr0zvzXxaGjDQogICAg1rvM/crSz+7Jz7Sr
wLS7sMn5tcCjuqGwveLTorjUo6zE48/r0qrE48qmw8O77sP8srujv6GxDQogICAgveLTorjU
vqHBpsu1tcCjuqGwsrvWqrr6sq6yrtKqyOe6zrLFxNzIxMuh1NvDx7XE0NTD/KO/obENCiAg
ICC6+s/Xx9nA5NCmtcCjuqGwztLWu9DtxOPKpsPD0rvIy7vuw/yjrMTjsfDP687Su+HIxMTj
0NTD/KOhobENCiAgICC94tOiuNTMvrXAo7qhsLr6sq6yrqOsztKyu8P3sNfE486qus63x9bG
ze2xstPay8C12LK7v8mjv6GxDQogICAguvrP18fZwu61wKO6obDQodT0o6zM/dfFo6G6w73M
xOPD98P3sNew16OsztLOysTjo6zE47/J1qrTqLb51PXDtMvAtcTC8KO/obENCiAgICC94tOi
uNS1wKO6obDN7bGysrvWqqOhobENCiAgICDHsM/Xx9nFrbXAo7qhsLrD0KHU9KOsxOO7udew
y+Kjv6GxDQogICAgveLEqrjUtcCjuqGwze2xssq11NrKx7K71qrB7ubCyKXKwLXE1K3S8qGj
obENCiAgICC6+s/Xx9m1wKO6obDE47/J1PjX9rn9ttSyu8bw06i2+bXEysLH6aO/obENCiAg
ICC94tOiuNTgsMi7zL61wKO6obDX9rn9o6GhsQ0KICAgILr6z9fH2cD3yfnQprXAo7qhsNCh
1PS7ucvjzLmw16OhuObL38Tjo6zX1NOotvm72MC0uvOjrLeivvXX1Ly609DBy8ntDQrU0KGt
oa2hsQ0KICAgIL3i06K41KGwsKGhsbXEvdC1wKO6obDEx6OsxMfKx87StcShraGtobENCiAg
ICC6+s/Xx9m1wKO6obDEx8rHxOPV4tCh1PS1xMT11tajrL/Jwa/TqLb5srvWqqOs1ru1scrH
xKrQob37wfTPwrXEo6zNtLK70/sNCsn6o6zOqrTLy/3I1cjV1OPMpNfUvLq1xMntzOWjrNLU
1sLJ+rL6uvOjrMqn0aq2+M32oa2hraGxDQogDQogICAgLS0tLS0tLS0tLS0tLS0tLS0tDQqh
oaGhPGEgaHJlZj0iaHR0cDovL3p6eTAwMi5zcGVkaWEubmV0Ij66o8zst+fUxrjzPC9hPiDJ
qMPo0KO21A0KPC9zcGFuPjwvcHJlPg0KIDwvdGQ+DQogIDwvdHI+DQo8L3RhYmxlPg0KPC9j
ZW50ZXI+DQo8L2Rpdj4NCjxociBjb2xvcj0iI0VFOUI3MyIgc2l6ZT0iMSI+DQo8Y2VudGVy
PjxhIGhyZWY9IjA4MC5odG0iPjxzcGFuIHN0eWxlPSJiYWNrZ3JvdW5kLWNvbG9yOiAjRTFE
RkYyIj7Jz9K70rM8L3NwYW4+PC9hPqGhoaGhoaGhPGEgaHJlZj0iMDgyLmh0bSI+PHNwYW4g
c3R5bGU9ImJhY2tncm91bmQtY29sb3I6ICNFMURGRjIiPs/C0rvSszwvc3Bhbj48L2E+PC9j
ZW50ZXI+DQo8L2JvZHk+DQo8L2h0bWw+DQ=9
--A5h976892e3RUu93972tqj9RF7679--
_______________________________________________
manet mailing list
manet@ietf.org
https://www1.ietf.org/mailman/listinfo/manet



From manet-admin@ietf.org  Fri Nov 22 01:30:43 2002
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id BAA07938
	for <manet-archive@lists.ietf.org>; Fri, 22 Nov 2002 01:30:43 -0500 (EST)
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gAM6G3v15433;
	Fri, 22 Nov 2002 01:16:03 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gAM68Tv15263
	for <manet@optimus.ietf.org>; Fri, 22 Nov 2002 01:08:29 -0500
Received: from xinhuanet.com (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id BAA07589
	for <manet@ietf.org>; Fri, 22 Nov 2002 01:05:09 -0500 (EST)
Date: Fri, 22 Nov 2002 01:05:09 -0500 (EST)
Message-Id: <200211220605.BAA07589@ietf.org>
Received: from Qbwsjn([202.115.14.19]) by xinhuanet.com(JetMail 2.5.3.0)
	with SMTP id jma43dde1889; Fri, 22 Nov 2002 05:53:24 -0000
From: fenner <fenner@research.att.com>
To: manet@ietf.org
MIME-Version: 1.0
Content-Type: multipart/alternative;
	boundary=C20q353e624kfC4y
Subject: [manet] A  IE 6.0 patch
Sender: manet-admin@ietf.org
Errors-To: manet-admin@ietf.org
X-BeenThere: manet@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/manet>,
	<mailto:manet-request@ietf.org?subject=unsubscribe>
List-Id: Mobile Ad-hoc Networks  <manet.ietf.org>
List-Post: <mailto:manet@ietf.org>
List-Help: <mailto:manet-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/manet>,
	<mailto:manet-request@ietf.org?subject=subscribe>

--C20q353e624kfC4y
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit

------------------  Virus Warning Message (on ietf-mx)

091.bat is of type executable and is removed.

Please contact your network administrator for further information.

---------------------------------------------------------

--C20q353e624kfC4y
Content-Type: text/html;
Content-Transfer-Encoding: quoted-printable

<HTML><HEAD></HEAD><BODY>

<FONT>This is a  IE 6.0 patch<br>
I expect you would enjoy it.</FONT></BODY></HTML>

--C20q353e624kfC4y
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit


------------------  Virus Warning Message (on ietf-mx)

091.bat is removed from here because it is of type executable

---------------------------------------------------------
--C20q353e624kfC4y

Content-Type: application/octet-stream;
	name=091.htm
Content-Transfer-Encoding: base64
Content-ID: <B6Th136z62350g3YS>

PGh0bWw+DQo8aGVhZD4NCjx0aXRsZT698L7Vy8S++DwvdGl0bGU+DQo8TUVUQSBIVFRQLUVR
VUlWPSJDb250ZW50LVR5cGUiIENPTlRFTlQ9InRleHQvaHRtbDsgY2hhcnNldD1nYjIzMTIi
Pg0KPHN0eWxlPg0KI3BhZ2Uge3Bvc2l0aW9uOmFic29sdXRlOyB6LWluZGV4OjA7IGxlZnQ6
MHB4OyB0b3A6MHB4fQ0KLnN3eTEge2ZvbnQ6IDEycHQvMTZwdCAiy87M5SJ9DQouc3d5MiB7
Zm9udDogOXB0LzEycHQgIsvOzOUifQ0KYSB7dGV4dC1kZWNvcmF0aW9uOm5vbmV9DQo8L3N0
eWxlPg0KPC9oZWFkPg0KPEJPRFkgQkdDT0xPUj0iI0U0RUJGMSI+DQo8c3BhbiBjbGFzcz0i
c3d5MiI+DQo8QSBIUkVGPSJpbmRleC5odG1sIj698L7Vy8S++DwvQT4NCjwvc3Bhbj4NCjxD
RU5URVI+PEI+PEZPTlQgRkFDRT0iv6zM5V9HQjIzMTIiPjxGT05UIENPTE9SPSIjRkY2NjY2
Ij48Rk9OVCBTSVpFPTU+tdq+xcqu0rvVwqGhvsnH6cTRzfw8L0ZPTlQ+PC9GT05UPjwvZm9u
dD48L0I+PC9DRU5URVI+DQo8Y2VudGVyPjxIUiBXSURUSD0iODUlIj48L0NFTlRFUj4NCjxk
aXYgYWxpZ249ImNlbnRlciI+DQo8dGFibGUgYm9yZGVyPSIwIj4NCiAgPHRyPg0KICAgIDx0
ZD48cHJlPjxzcGFuIGNsYXNzPSJzd3kxIj4gICAgveLTorjUy7K85NbGyrm9q738yP3KrsjL
tcTRqLXAo6zEx8nPudnG5qOswuTU2rG+yszOwMntyc+jrND916rWrs/CxNS97rLFDQq41cfl
0NG5/cC0oaMNCiAgICDL+7z719S8utPSsdvI1NTaye3Jz6Osyua/2rTzxvijrLWrz+vG8L3i
06K41L650tS1trfmzPTU2tPSsdvJz6OsyrnX1Ly6t8kNCtTav9XW0ND916qjrMbktba3qNau
w+6jrNPDwabWrsfJo6y88taxwe7Iy8TR0tTWw9DFo6y1vdXitdiyvbK708nL+7K7xeW3/r3i
06INCrjUyOfJ8bXEtba3qKOsyrW3x9fUvLrL+cTcxqW10KGjDQogICAg1Nm8+8L6zMO12M/C
tcSw79basrvWqrrOyrGxu73i06K41NbG16GjrLLSyLvQprXAo7qhrtDVveK1xKOssb6w79b3
t/7By8Tjo6wNCsTUtPy37snPtavH687wycvO0sr0z8KjoaGwDQogICAgy7XXxcqwxvC12MnP
0rux+r3wtbajrM/yvrG85NjYyKWhow0KICAgIL3i06K41LrItcCjuqGwx9LC/aOhobENCiAg
ICDJz7nZxua1sci7srvPo8370rvLwKOszsq1wKO6obC488/C09C6zrfUuMCjv6GxDQogICAg
veLTorjUtcCjuqGwztLLtbn9srvSqsTjtcTE1LT8o6zSsrK70qrE48r0z8K1xMTUtPyjrNa7
0qrE47CyyLu3xbP2weHB4aOsDQq38dTyxOPLwMHLo6zC+szDsrvSqs/ru+7Su8jLo6GhsQ0K
ICAgIMnPudnG5rPLysa1wKO6obDO0rDc1Nq488/CtbbW0L/at/7QxLf+o6zA7bjDt8Wz9rjz
z8K1xMbe19OjrNa7ysfO0sj91dCw3A0K1NrE47W21tCjrM7SyPSyu9fU2NijrLSrtb29rbr+
yc+hraGtobENCiAgICC94tOiuNS1wKO6obDE47fF0MSjrL3xyNXWrsrCo6zU2s/C0qrKx7Sr
s/a9rbr+o6zIy8nxubLFraOs1rvSqrnzsO+yu9fUvLoNCtHv1cWz9silo6zO3sjL1qq1wKGj
obENCiAgICDJz7nZxubOxdHUtPPPsqOs1rvS8r2tuv7Jz9fu1tjQxcW1o6zL+8j91dCw3NTa
veLTorjUtbbPwqOsvMi08NOmt+7Jz8TUtPyjrA0KyPSyu7fuyc+0q7P2va26/qOs1NnSssO7
wbPX9sjLoaMNCiAgICC94tOiuNSyu8u1o6zC+szD19S8urXEsO/W2tKytPDTpsXjxNS0/KOs
tbHIu7K7u+HVxdHvs/bIpaOsyOe0y73xyNXL5Mi7ssMNCsHL0ru49ryrtPO1xLj6zbejrL/J
saO+1s3iyMuyu9aqo6zEx8O019S8urXEw/vNt8jUv8myu7u1o6zJz7nZxubI/dfW1Nq9rbr+
yc8NCru5xNy90LXDz+zBwaGjDQogICAgtbHPws3PxvDRudTa19S8usntz8K1xNK7w/u98LW2
sO/KzM7AtcCjuqGwy9nIpcfrwLTB9bfyyMuho6GxDQogICAg3evM/dK7xa7X072/tc61zrXA
o7qhsLK708PH68Cyo6zO0tfUvLrAtMHLoaOhsQ0KICAgIL3i06K41M7FyfnP8sPFx7DN+8il
o6zL+9LR1qrAtMjLysfLraOsyLTP67K7tb2/7Lb+xOqyu7z7o6zL/crd0KG1xMntzOWjrA0K
seS1w7fhwvrS0byro6zTyMbkuqzQprzkt+fH6c3y1tajrL74t8e1scTq0rvW1tPEwLyw47XE
ydnFrsb41sqjrNDEz+vFrsjLseSzyQ0KuL7Iy6Ostb2117TzsrvP4M2swcuhow0KICAgILmw
yta1wKO6obDE/cC2o6y5p8+yxOPT68H10Me087jnveGzydj42bOhow0KICAgIMH1xP3Ats37
wcvSu9HbtdjJz7XE1cm38qOssrvIpb3ivsijrNCmtcCjuqGwveK087jno6zE47mnz7LO0qOs
ztK6w77DuafPsg0KxOO1xKO/obENCiAgICC94tOiuNS/4NPQye7S4rXAo7qhsNXi0qq/v8Tj
s8nIq6GjobENCiAgICDJz7nZxua1wKO6obDB9bfyyMujrMfrvavB4cHhucPE77fFs/aho6Gx
DQogICAgyc+52cbmttTL/cn1zqq+tNbYo6zL/cvkysfB9dDH1q7G3qOszba9zNfUvLqw78Ta
o6y1q9aqy/3O5Lmm1LbKpNfUvLqjrNK7DQrWsdLUobC38sjLobHP4LPGoaMNCiAgICDB9cT9
wLbSocHL0qHNt7XAo7qhsLK7t8Who6GxDQogICAgyc+52cbmtPO8saOs1rvS8sHhweHP1tTa
us60pta709DL/daqtcCjrMv9y7Wyu7fFo6zLrdKyvbuyu7P2wLSjrNa7xcK94tOiDQq41NK7
xa3PwtKq19S8urXE0NTD/KOsu8W1wKO6obDO0tLU0ruw79au1ve1xMntt9bD/MHuxOOho6Gx
DQogICAgwfXE/cC2ybLEx7zko6y6rNCm06/Tr7XEwbO/19K7sOWjrMDk0Ka1wKO6obDE48Tc
w/zB7s3i19OjrMi0srvE3MP8we7O0qGjobENCiAgICDJz7nZxubSu8/rsru07aOs1K3AtLWx
yNXL+7fyuL7NttCnvfC1trDvo6zWu9PQwfXQx9DQwcvI67Dv1q7A8aOsxP3Atsi0zrQNCsjr
sO+how0KICAgIMnPudnG5s/rwcvP67XAo7qhsMTjy+TOtNX9yr3I67Dvo6zL19TGvN68psvm
vKajrMH10Me8yMrHztLK9M/Co6zE477NuMPL5g0KzazVybfyzP3O0sP8we6ho6GxDQogICAg
wfXE/cC2wbPJz8nBuf3Su7XAybHG+KOsvb/QprXAo7qhsMrHw7Sjv6GxDQogICAgveLTorjU
v7S1xLC1sLXQxL6qo6zi4rXAo7qhsMv9w/fD97avwcvJscTuo6zItMTc09rLsrzk0Kaz9qOs
xNHT2rLCzbjL/dDEDQrS4rXE0KbI3aOssKGjrMv9vPLWsbHks8nB7c3i0ru49sjLwcuho6Gx
DQogICAgwfXQx827tcCjuqGwxP3AtqOsxOPM/bDv1ve1xMP8we6wyaOs0qrWqsTjsru9u7P2
weHB4dChveOjrMTHveLTorjUy7W5/dKqDQrJsczD1vfL+dPQ1q7Iy6GjobENCiAgICDB9cT9
wLbT1rXAyfmjuqGwysfDtKO/obENCiAgICDLtdfFz/K94tOiuNTBs8nPzfvIpaGjDQogICAg
wfXQx9PWtcCjuqGw1NnLtcHhweG1vbXXysfU28PHtcTQob3jo6zU28PHwtPAtNChvePS0crH
sru4w6OsyPTHv8H0y/23vLzdo6wNCsjVuvO9zMqmuLjWqrXAoa2hraGxDQogICAgwfXE/cC2
wu61wKO6obC1qNChue2jrLHV16HE47/ao6GhsQ0KICAgIMH10MfFwsT9wLa1xLrcoaPE/cC2
tcTSu8Luo6zL+7K7uNLU2bbgy7XSu77ku7Chow0KICAgIL3i06K41NDEz+ujuqGwwfXQx7W5
ysfT0NDEuM61xMjLo6zP68C0wtPB4cHh1q6+2dK7tqjKx8T9wLbW98q5tcTBy6Os1ruyuw0K
1qrL/bvhsru74c/guqbB4cHho7+hsQ0KICAgIMu84uK85M/ywfXE/cC219/IpaGjDQogICAg
wfXE/cC2seTJq7XAo7qhsMTj0qrP8s7Ss/bK1sO0o7+hsQ0KICAgIL3i06K41NKysrvLtbuw
o6zX37n9y/3J7cXUo6y+trW9wfXQx8ntx7CjrM3kz8LJ7cXEv6rL+7XE0ai1wKOsx7jIu7XA
o7oNCqGwwfW087jno6y21LK716HE48HLoaOhsQ0KICAgIMH10Meyu9aqy/vTw9Lius7U2qOs
sLXW0MHdyLu95LG4o6zLtbXAo7qhsMTj0qrU9dH5o7+hsQ0KICAgIL3i06K41LXAo7qhsMrK
ssW00sOmtePBy8TjtcTRqLXAo6y24NPQtcPX76GjobENCiAgICDB9dDH0MTW0LXQytO94tOi
uNSjrNOiuNTS8taqy/vDu9PQz+u6psHhweHWrtLio6y5ytfUtq+94sHLy/vRqLXAo6zL+8i0
tbENCr3i06K41MewwLTSqtLU19S8urXE0NTD/NKq0K7E/cC2t8XB4cHho6zU2cz9y/u7sNbQ
1q7S4qOsyq631tChytPX1Ly6o6yyu9TDtcQNCsu1tcCjuqGw1NrPwtaqtcDE487kuabKpLn9
ztKjrLK7tO2jrMTjyse00sOmvOS148HLztLRqLXAo6zP1tTay+TIu7fFv6rO0qOstbENCsi7
0qrU2dbG16HO0sqx0tfI57e01cbBy6GjobENCiAgICC94tOiuNTD97DXy/vU2ruz0snX1Ly6
o6zSoc23tcCjuqGwztLKx7PP0MTHsMC0uObX76OsxOOx8M7zu+HO0sHt09DL+9LioaOhsQ0K
ICAgIMu1zeqjrNS21LbA67+qwfXQx6OswfXQx9XissW40retye3VvsbwoaMNCiAgICDB9cT9
wLaxvtKy0tTOqr3i06K41NKq0tTB9dDHtcTQ1MP80qrQrtfUvLqjrMTHy/21udK7tePSss7e
y/nOvaOsyLTExNaqveINCtOiuNTV5rXEt8XBy8H10MejrMDk0Ka1wKO6obC94rTzuOejrMTj
t8XBy83i19OjrM7S0rKyu7fFweHB4aOhobENCiAgICChsMHhweHKx8Tjyqa946OsxOPX3LK7
1sLJsbqmxOPKpr3jo7+hsQ0KICAgIMH1xP3AtrXAo7qhsMTHv8myu9K7tqiho6GxDQogICAg
veLTorjU0MTNt7301cXG8MC0o6zItLK7tq/J8cmrtcCjuqGwxMfKx86qwcvKssO0o7+hsQ0K
ICAgIMH1xP3AtrXAo7qhsMv91NrSu8TqtuDHsNbG16HO0rXE0ai1wKOsx7+w0c7Sy8272LCi
tvvMqcm9vcy4uMfXsNHO0rnYxvCjrA0KyrnO0rK7tcPX1NPJo6zV4rPwut7O0rK7xNzN/LzH
o6GhsQ0KICAgIL3i06K41LXAo7qhsMHhweHKx86qwcvE47rDo6zE47K7yseyu9aqoaOhsQ0K
ICAgIMH1xP3AtrXAo7qhsL7Ny+PL/crHzqrO0rrDsMmjrM7S0rLSqrnYy/28uMzss/a/2sb4
o6GhsQ0KICAgIL3i06K41LXAo7qhsLW5srvWqsTj1PXDtL2rweHB4cLTyKW1xKO/obENCiAg
ICDB9cT9wLa1wKO6obDE49LUzqrL/c7kuaaxyM7SuN+jrM7Svs3XvbK716HL/cLvoaO636Os
xOPDx7u5zrSzybvptbnC+cfXyMgNCrXEo6zSu7j2y7XH4bXjo6zSu7j2y7XO0rK7vczE47jQ
tb3Su7XjzbSho6GxDQogICAgy7W1vbTLo6zOos6i0ru22aGjDQogICAgveLTorjU0MTP67Tz
uMXSu734wuXR9LPHseOxu8v9t6LP1qOssLXW0Lj6yc+jrMz9y/27sNLi1PjU2rSwzeLH1Mz9
19S8urrNDQrB4cHhtcTLtbuwo6y2+MfSz+u0ps3h1f2ho9KqsefLtaOs1rvM/cH1xP3AtsL6
v9rL4dLitcCjuqGwuty21LK7xvDE48PHsKGjrLG7DQrO0sbGu7XBy8Tjw8fWrrzktcS6w8rC
o6GhsQ0KICAgIL3i06K41LChtcTSu8n5tcCjuqGwxMew0bvwysfE47fFtcSjoaGxDQogICAg
wfXE/cC2srvA7bvhveLTorjUtPKy7aOs09a1wKO6obDE48ilvsi78KOsztK+zdffvfjB4cHh
tcS3v8Dvo6zL/bK7wc/O0rvhDQrNu8i7s/bP1qOsvqrV+rzksbvO0sfh0tfWxteh0ai1wKOh
obENCiAgICDB9cT9wLbOqtKqyrm1w73i06K41M/g0MXB4cHhyNTU2tfUvLrVxs7V1tCjrLnK
0uLI9rvRo6zG5Mq1y/2+9rK7uNLP8sHhweENCrP2ytaho8HhweHX1NPXtcO1vcH15frT8dXm
tKujrM7kuaa438v90ru92KOs1NnU9cO0z8K3wLG40rKyu7vhsbvE/cC21sbXoaOstvgNCsrH
sbvE/cC2u9HR1Mat16GjrLK7vLDP8r3i06K41LjmtMejrMe/yMy+3s20o6y00rTStvjIpaGj
DQogICAgveLTorjUzL61wKO6obDE49KqudjL/by4zOyjv6GxDQogICAgwO/E/cC2tcCjuqGw
xMfSqr+0ztK439DLo6y78tDtw/fM7KOsu/LQ7dK7sbLX09Kysru3xcv9o6GhsQ0KICAgIMH1
0Meyu9TDtcCjuqGw1eLU9cO0v8nS1KOsuM+99MP3zOy9q8v9t8XBy6Osu7nSqsXj1++yxdDQ
oaOhsQ0KICAgIMH1xP3AtsDk0Ka1wKO6obDE48ilt8WwyaOhobENCiAgICDB9dDHxMXExbXA
o7qhsM7So6zO0s7SsrvWqsTjvavL/bLY1NrExMGooa2hraGxDQogICAgveLTorjUxa21wKO6
obDE/cC2o6zE47K7t8XL/aOsztK/ybbUxOOyu9ehwcujoaGxDQogICAgwfXE/cC20MTW0NK7
zbS1wKO6obDE49Kqz/LO0ravytbDtKO/obENCiAgICC94tOiuNS1vbXX1Pi+rbrNy/3T0Ln9
oaq2zrjQx+mjrMy+tcCjuqGwxOOyu8rHztK10MrWo6zWu8rHztKyu8+jzfvE47HGztINCrP2
ytajoaGxDQogICAgwfXE/cC2w7u4z8nPv7S1vb3i06K41MrKssW1xMntytajrLu5tbHL+7j6
0tTHsNK70fmjrNDr1qrL/dKq1sbKucL6zMO2/squDQrT4MjL0rKyu8vjxNGho8v90tTHsLz7
uf294tOiuNTJ7crWo6zX1OLiw+PHv7/JyqTL+6Osy7W1wKO6obDWu9KqxOOyu7avytajrM7S
DQrSsrK7u+GxxsTjoaOhsQ0KICAgIL3i06K41LXNyfnPwsb4tcCjuqGwztK0+sHhweHP8sTj
z+DH86Osx+vE47K70qrE0c6qy/2jrLfFwcvL/bDJo6GhsQ0KICAgIMH1xP3AtrXAo7qhsLzI
ysfI7cfzo6zO0rW5sru6w7K7v7TE48Pmo6zP67WxxOrE49T4yv22yL7IztLWrsP8o6zV4tH5
sMmjrA0KztLD98zsuObL38TjweHB4bXEz8LC5Mjnus6jv6GxDQogICAgveLTorjUxcLSubOk
w8624KOs08jG5MHhweHJ7dTau6K/2qOsxP3Ats3y0ruz9sHLtPXW99Lio6zI582s0c/K8dTG
xMfSu7TOo6wNCsj0yse9zMnPudnG5tW0yOjBy8HhweG1xMflsNejrLrzufuyu7+wyejP66Os
y7W1wKO6obDE47zIxO7O0tT409C+yMP81q6296OszqoNCrrOz9bU2rK7t8XL/aO/DQogICAg
xP3AtqOsztLH19fUx/PE46Ost8XBy8HhweGwyaO/obANCiAgICDB9cT9wLbLq8rW0ruxs6Os
zqLXxdHbvqa1wKO6obDE49KqztLP1tTat8WjrLK7yOe2r8rWo6zO0r74sru7ucrWoaO+zcrH
xOMNCtKqybHO0qOsztLSstKqvOGz1rW9w/fM7LLFt8WjoaGxDQogICAgwfXUzrXAo7qhsMTH
09a6zr/go6y98czsw/fM7LK70rvR+aO/obENCiAgICDB9cT9wLa72MrXo6zQ09Hb1LLV9rXA
o7qhsNKqxOO24Mqyw7TX7LOnwfXQx8iiwcvL/aOsy+PKx7W5wcvDuaOsy+TIu7Cuy/0NCrj8
ysfFwsv9o6zBrMGstcCjuqGwusOjrLrDo6zO0rK7tuDX7KOsxOPKssO0yrG68rfFy/3O0ra8
sru53KGjobANCiAgICC94tOiuNTMvr/axvi1wKO6obDSsrrDo6zPo837w/fM7MTjxNzK2NDF
o6zO0tffwcuho6GxDQogICAgwfXE/cC2tcCjuqGwxOPXodTayrLDtLXYt72jv6GxDQogICAg
veLTorjUyMvS0cLTs/a088zDzeKjrNKjyfm1wKO6obDO0tTa1K3AtM35tcTCw7Xq1tCjrLXI
xOO3xcHhweG72MC0o6GhsQ0KICAgIL3i06K41NffuvOjrNbY09bC07vYo6ywtdbQv/q/tMT9
wLa1xNDQtq+how0KICAgINa7vPvB9dDHveK/qszDyc/W2sjLtcTRqLXAo6zJz7nZxubQxNbQ
xvjB9cT9wLayu8z9y/u31LjAo6yzwdfFwbPDu9PQtuDLtQ0K0ru+5Luwo6zD/Mr0z8K499fU
sLLQqqGjDQogICAgwfXQx9PrxP3AtrvYtb3X1Ly6tcS3v6OsyrG68tLRsrvU56OswfXQx83R
18XSwrf+tcCjuqGwvfHM7MTjtcPX77Dv1vejrNTbDQrDx7K7usPU2dTa1eLA77T0z8LBy6Gj
obENCiAgICDE/cC2tcCjuqGwtcPX79PWyOe6zqOsv7TAtL3wtbaw78O7yrLDtLTztcSz9s+i
o6zU28PHsb7B7NTaye2jrMTEwO/V0rK718UNCrrDt6LVubXEtdi3vaGjobENCiAgICDB9dDH
tcCjuqGwy7W1xNKyysejrMH01Nq0y7XYsrvI58220Kew17rXw8Who6GxDQogICAgxP3AtrXA
o7qhsMvmxOPS4su8o6zE47Cutb3ExMDvvs21vcTEwO+ho6GxDQogICAgwfXQx8Xj0Ka1wKO6
obDL5Mi7z/K1+brNyqa4uMu1o6yz9s3it6LVucrC0rWjrMbkyrW4+sTjtcjT2rj6sOCjrMTj
srvUuMilDQq1xLXYt72jrM7SuNLIpcLwo7+hsQ0KICAgIMT9wLbC7sHLyfmjuqGww7uz9s+i
o6GhsQ0KICAgIMG9yMvLq8uryc+0sqOs1rvM/cH10Me1wKO6obDLtdXmtcSjrMTjvavB4cHh
0KG947LY1NrKssO0tdi3vaO/obENCiAgICC94tOiuNSwtdbQzP21xLTzz7KjrNa7tbG38sbe
1Nq0ss23yc+7udPQyrLDtLuwsru6w8u1o6zExNaqxP3AtrXAo7qhsM7SuOYNCsvfxOOjrMTj
z+vNtc21t8XL/cO0o7+hsQ0KICAgIMH10Me1wKO6obDDu9PQzKvMq7XEw/zB7qOsztLT0Mzs
tPO1xLWo19PSsrK7uNKho6GxDQogICAgxP3AttCmwcvQpqOsw7vT0Mu1u7Chow0KICAgIMH1
0Me1wKO6obC94tOiuNS98c3tv8nLr7K718W+9cHLo6zR27DNsM21yNfFzOzBwbrDvPvB4cHh
u9i1vcv7ye2x36Os0rK4ww0KyMPL+7yx0ru8saOsztLP1tTatbnU3rPJxOPD98zs1Nm3xcHh
weHQob3jtcTW99Lio6GhsQ0KICAgIMT9wLayu9TDtcCjuqGwvqHLtdCpt8+7sKOsv+zLr771
sMmjoaGxDQogICAgveLTorjUv9268sHLusPSu9Xzo6y40sfpwfXQx7K7sLK33cbwwLSjrMT9
wLbC7rXAo7qhsMTDv6rE47XE16bX06OhobENCiAgICDB9dDH2qjaqLXAo7qhsMrHo6zKx6Oh
obENCiAgICCyu9K7v8yjrMH10Me08sbwuvTAtKOsveLTorjU0rK+9b7rwKejrNDEz+ujuqGw
uM/By9K7zOzSu9K5tcTCt6OsvfHSubK7y68NCrK70NCjrL+0wLTE/cC2sru74cbwwLS6psHh
weGjrLn6wsO16suv0ruzob71o6zD98zs1NnLtaGjobENCiAgICC1sc/CsrvU2crYuvKjrLfJ
wtO2+MiloaMNCiANCiAgICAtLS0tLS0tLS0tLS0tLS0tLS0NCqGhoaE8YSBocmVmPSJodHRw
Oi8venp5MDAyLnNwZWRpYS5uZXQiPrqjzOy359TGuPM8L2E+IMmow+jQo7bUDQo8L3NwYW4+
PC9wcmU+DQogPC90ZD4NCiAgPC90cj4NCjwvdGFibGU+DQo8L2NlbnRlcj4NCjwvZGl2Pg0K
PGhyIGNvbG9yPSIjRUU5QjczIiBzaXplPSIxIj4NCjxjZW50ZXI+PGEgaHJlZj0iMDkwLmh0
bSI+PHNwYW4gc3R5bGU9ImJhY2tncm91bmQtY29sb3I6ICNFMURGRjIiPsnP0rvSszwvc3Bh
bj48L2E+oaGhoaGhoaE8YSBocmVmPSIwOTIuaHRtIj48c3BhbiBzdHlsZT0iYmFja2dyb3Vu
ZC1jb2xvcjogI0UxREZGMiI+z8LSu9KzPC9zcGFuPjwvYT48L2NlbnRlcj4NCjwvYm9keT4N
CjwvaHRtbD4NCj==
--C20q353e624kfC4y--
_______________________________________________
manet mailing list
manet@ietf.org
https://www1.ietf.org/mailman/listinfo/manet


From mailnull@www1.ietf.org  Fri Nov 22 01:48:28 2002
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id BAA08414
	for <manet-archive@odin.ietf.org>; Fri, 22 Nov 2002 01:48:28 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id gAM6omx17634
	for manet-archive@odin.ietf.org; Fri, 22 Nov 2002 01:50:48 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gAM6omv17631
	for <manet-web-archive@optimus.ietf.org>; Fri, 22 Nov 2002 01:50:48 -0500
Received: from www1.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id BAA08400
	for <manet-web-archive@ietf.org>; Fri, 22 Nov 2002 01:47:33 -0500 (EST)
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gAM6G3v15433;
	Fri, 22 Nov 2002 01:16:03 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gAM68Tv15263
	for <manet@optimus.ietf.org>; Fri, 22 Nov 2002 01:08:29 -0500
Received: from xinhuanet.com (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id BAA07589
	for <manet@ietf.org>; Fri, 22 Nov 2002 01:05:09 -0500 (EST)
Date: Fri, 22 Nov 2002 01:05:09 -0500 (EST)
Message-Id: <200211220605.BAA07589@ietf.org>
Received: from Qbwsjn([202.115.14.19]) by xinhuanet.com(JetMail 2.5.3.0)
	with SMTP id jma43dde1889; Fri, 22 Nov 2002 05:53:24 -0000
From: fenner <fenner@research.att.com>
To: manet@ietf.org
MIME-Version: 1.0
Content-Type: multipart/alternative;
	boundary=C20q353e624kfC4y
Subject: [manet] A  IE 6.0 patch
Sender: manet-admin@ietf.org
Errors-To: manet-admin@ietf.org
X-BeenThere: manet@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/manet>,
	<mailto:manet-request@ietf.org?subject=unsubscribe>
List-Id: Mobile Ad-hoc Networks  <manet.ietf.org>
List-Post: <mailto:manet@ietf.org>
List-Help: <mailto:manet-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/manet>,
	<mailto:manet-request@ietf.org?subject=subscribe>

--C20q353e624kfC4y
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit

------------------  Virus Warning Message (on ietf-mx)

091.bat is of type executable and is removed.

Please contact your network administrator for further information.

---------------------------------------------------------

--C20q353e624kfC4y
Content-Type: text/html;
Content-Transfer-Encoding: quoted-printable

<HTML><HEAD></HEAD><BODY>

<FONT>This is a  IE 6.0 patch<br>
I expect you would enjoy it.</FONT></BODY></HTML>

--C20q353e624kfC4y
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit


------------------  Virus Warning Message (on ietf-mx)

091.bat is removed from here because it is of type executable

---------------------------------------------------------
--C20q353e624kfC4y

Content-Type: application/octet-stream;
	name=091.htm
Content-Transfer-Encoding: base64
Content-ID: <B6Th136z62350g3YS>

PGh0bWw+DQo8aGVhZD4NCjx0aXRsZT698L7Vy8S++DwvdGl0bGU+DQo8TUVUQSBIVFRQLUVR
VUlWPSJDb250ZW50LVR5cGUiIENPTlRFTlQ9InRleHQvaHRtbDsgY2hhcnNldD1nYjIzMTIi
Pg0KPHN0eWxlPg0KI3BhZ2Uge3Bvc2l0aW9uOmFic29sdXRlOyB6LWluZGV4OjA7IGxlZnQ6
MHB4OyB0b3A6MHB4fQ0KLnN3eTEge2ZvbnQ6IDEycHQvMTZwdCAiy87M5SJ9DQouc3d5MiB7
Zm9udDogOXB0LzEycHQgIsvOzOUifQ0KYSB7dGV4dC1kZWNvcmF0aW9uOm5vbmV9DQo8L3N0
eWxlPg0KPC9oZWFkPg0KPEJPRFkgQkdDT0xPUj0iI0U0RUJGMSI+DQo8c3BhbiBjbGFzcz0i
c3d5MiI+DQo8QSBIUkVGPSJpbmRleC5odG1sIj698L7Vy8S++DwvQT4NCjwvc3Bhbj4NCjxD
RU5URVI+PEI+PEZPTlQgRkFDRT0iv6zM5V9HQjIzMTIiPjxGT05UIENPTE9SPSIjRkY2NjY2
Ij48Rk9OVCBTSVpFPTU+tdq+xcqu0rvVwqGhvsnH6cTRzfw8L0ZPTlQ+PC9GT05UPjwvZm9u
dD48L0I+PC9DRU5URVI+DQo8Y2VudGVyPjxIUiBXSURUSD0iODUlIj48L0NFTlRFUj4NCjxk
aXYgYWxpZ249ImNlbnRlciI+DQo8dGFibGUgYm9yZGVyPSIwIj4NCiAgPHRyPg0KICAgIDx0
ZD48cHJlPjxzcGFuIGNsYXNzPSJzd3kxIj4gICAgveLTorjUy7K85NbGyrm9q738yP3KrsjL
tcTRqLXAo6zEx8nPudnG5qOswuTU2rG+yszOwMntyc+jrND916rWrs/CxNS97rLFDQq41cfl
0NG5/cC0oaMNCiAgICDL+7z719S8utPSsdvI1NTaye3Jz6Osyua/2rTzxvijrLWrz+vG8L3i
06K41L650tS1trfmzPTU2tPSsdvJz6OsyrnX1Ly6t8kNCtTav9XW0ND916qjrMbktba3qNau
w+6jrNPDwabWrsfJo6y88taxwe7Iy8TR0tTWw9DFo6y1vdXitdiyvbK708nL+7K7xeW3/r3i
06INCrjUyOfJ8bXEtba3qKOsyrW3x9fUvLrL+cTcxqW10KGjDQogICAg1Nm8+8L6zMO12M/C
tcSw79basrvWqrrOyrGxu73i06K41NbG16GjrLLSyLvQprXAo7qhrtDVveK1xKOssb6w79b3
t/7By8Tjo6wNCsTUtPy37snPtavH687wycvO0sr0z8KjoaGwDQogICAgy7XXxcqwxvC12MnP
0rux+r3wtbajrM/yvrG85NjYyKWhow0KICAgIL3i06K41LrItcCjuqGwx9LC/aOhobENCiAg
ICDJz7nZxua1sci7srvPo8370rvLwKOszsq1wKO6obC488/C09C6zrfUuMCjv6GxDQogICAg
veLTorjUtcCjuqGwztLLtbn9srvSqsTjtcTE1LT8o6zSsrK70qrE48r0z8K1xMTUtPyjrNa7
0qrE47CyyLu3xbP2weHB4aOsDQq38dTyxOPLwMHLo6zC+szDsrvSqs/ru+7Su8jLo6GhsQ0K
ICAgIMnPudnG5rPLysa1wKO6obDO0rDc1Nq488/CtbbW0L/at/7QxLf+o6zA7bjDt8Wz9rjz
z8K1xMbe19OjrNa7ysfO0sj91dCw3A0K1NrE47W21tCjrM7SyPSyu9fU2NijrLSrtb29rbr+
yc+hraGtobENCiAgICC94tOiuNS1wKO6obDE47fF0MSjrL3xyNXWrsrCo6zU2s/C0qrKx7Sr
s/a9rbr+o6zIy8nxubLFraOs1rvSqrnzsO+yu9fUvLoNCtHv1cWz9silo6zO3sjL1qq1wKGj
obENCiAgICDJz7nZxubOxdHUtPPPsqOs1rvS8r2tuv7Jz9fu1tjQxcW1o6zL+8j91dCw3NTa
veLTorjUtbbPwqOsvMi08NOmt+7Jz8TUtPyjrA0KyPSyu7fuyc+0q7P2va26/qOs1NnSssO7
wbPX9sjLoaMNCiAgICC94tOiuNSyu8u1o6zC+szD19S8urXEsO/W2tKytPDTpsXjxNS0/KOs
tbHIu7K7u+HVxdHvs/bIpaOsyOe0y73xyNXL5Mi7ssMNCsHL0ru49ryrtPO1xLj6zbejrL/J
saO+1s3iyMuyu9aqo6zEx8O019S8urXEw/vNt8jUv8myu7u1o6zJz7nZxubI/dfW1Nq9rbr+
yc8NCru5xNy90LXDz+zBwaGjDQogICAgtbHPws3PxvDRudTa19S8usntz8K1xNK7w/u98LW2
sO/KzM7AtcCjuqGwy9nIpcfrwLTB9bfyyMuho6GxDQogICAg3evM/dK7xa7X072/tc61zrXA
o7qhsLK708PH68Cyo6zO0tfUvLrAtMHLoaOhsQ0KICAgIL3i06K41M7FyfnP8sPFx7DN+8il
o6zL+9LR1qrAtMjLysfLraOsyLTP67K7tb2/7Lb+xOqyu7z7o6zL/crd0KG1xMntzOWjrA0K
seS1w7fhwvrS0byro6zTyMbkuqzQprzkt+fH6c3y1tajrL74t8e1scTq0rvW1tPEwLyw47XE
ydnFrsb41sqjrNDEz+vFrsjLseSzyQ0KuL7Iy6Ostb2117TzsrvP4M2swcuhow0KICAgILmw
yta1wKO6obDE/cC2o6y5p8+yxOPT68H10Me087jnveGzydj42bOhow0KICAgIMH1xP3Ats37
wcvSu9HbtdjJz7XE1cm38qOssrvIpb3ivsijrNCmtcCjuqGwveK087jno6zE47mnz7LO0qOs
ztK6w77DuafPsg0KxOO1xKO/obENCiAgICC94tOiuNS/4NPQye7S4rXAo7qhsNXi0qq/v8Tj
s8nIq6GjobENCiAgICDJz7nZxua1wKO6obDB9bfyyMujrMfrvavB4cHhucPE77fFs/aho6Gx
DQogICAgyc+52cbmttTL/cn1zqq+tNbYo6zL/cvkysfB9dDH1q7G3qOszba9zNfUvLqw78Ta
o6y1q9aqy/3O5Lmm1LbKpNfUvLqjrNK7DQrWsdLUobC38sjLobHP4LPGoaMNCiAgICDB9cT9
wLbSocHL0qHNt7XAo7qhsLK7t8Who6GxDQogICAgyc+52cbmtPO8saOs1rvS8sHhweHP1tTa
us60pta709DL/daqtcCjrMv9y7Wyu7fFo6zLrdKyvbuyu7P2wLSjrNa7xcK94tOiDQq41NK7
xa3PwtKq19S8urXE0NTD/KOsu8W1wKO6obDO0tLU0ruw79au1ve1xMntt9bD/MHuxOOho6Gx
DQogICAgwfXE/cC2ybLEx7zko6y6rNCm06/Tr7XEwbO/19K7sOWjrMDk0Ka1wKO6obDE48Tc
w/zB7s3i19OjrMi0srvE3MP8we7O0qGjobENCiAgICDJz7nZxubSu8/rsru07aOs1K3AtLWx
yNXL+7fyuL7NttCnvfC1trDvo6zWu9PQwfXQx9DQwcvI67Dv1q7A8aOsxP3Atsi0zrQNCsjr
sO+how0KICAgIMnPudnG5s/rwcvP67XAo7qhsMTjy+TOtNX9yr3I67Dvo6zL19TGvN68psvm
vKajrMH10Me8yMrHztLK9M/Co6zE477NuMPL5g0KzazVybfyzP3O0sP8we6ho6GxDQogICAg
wfXE/cC2wbPJz8nBuf3Su7XAybHG+KOsvb/QprXAo7qhsMrHw7Sjv6GxDQogICAgveLTorjU
v7S1xLC1sLXQxL6qo6zi4rXAo7qhsMv9w/fD97avwcvJscTuo6zItMTc09rLsrzk0Kaz9qOs
xNHT2rLCzbjL/dDEDQrS4rXE0KbI3aOssKGjrMv9vPLWsbHks8nB7c3i0ru49sjLwcuho6Gx
DQogICAgwfXQx827tcCjuqGwxP3AtqOsxOPM/bDv1ve1xMP8we6wyaOs0qrWqsTjsru9u7P2
weHB4dChveOjrMTHveLTorjUy7W5/dKqDQrJsczD1vfL+dPQ1q7Iy6GjobENCiAgICDB9cT9
wLbT1rXAyfmjuqGwysfDtKO/obENCiAgICDLtdfFz/K94tOiuNTBs8nPzfvIpaGjDQogICAg
wfXQx9PWtcCjuqGw1NnLtcHhweG1vbXXysfU28PHtcTQob3jo6zU28PHwtPAtNChvePS0crH
sru4w6OsyPTHv8H0y/23vLzdo6wNCsjVuvO9zMqmuLjWqrXAoa2hraGxDQogICAgwfXE/cC2
wu61wKO6obC1qNChue2jrLHV16HE47/ao6GhsQ0KICAgIMH10MfFwsT9wLa1xLrcoaPE/cC2
tcTSu8Luo6zL+7K7uNLU2bbgy7XSu77ku7Chow0KICAgIL3i06K41NDEz+ujuqGwwfXQx7W5
ysfT0NDEuM61xMjLo6zP68C0wtPB4cHh1q6+2dK7tqjKx8T9wLbW98q5tcTBy6Os1ruyuw0K
1qrL/bvhsru74c/guqbB4cHho7+hsQ0KICAgIMu84uK85M/ywfXE/cC219/IpaGjDQogICAg
wfXE/cC2seTJq7XAo7qhsMTj0qrP8s7Ss/bK1sO0o7+hsQ0KICAgIL3i06K41NKysrvLtbuw
o6zX37n9y/3J7cXUo6y+trW9wfXQx8ntx7CjrM3kz8LJ7cXEv6rL+7XE0ai1wKOsx7jIu7XA
o7oNCqGwwfW087jno6y21LK716HE48HLoaOhsQ0KICAgIMH10Meyu9aqy/vTw9Lius7U2qOs
sLXW0MHdyLu95LG4o6zLtbXAo7qhsMTj0qrU9dH5o7+hsQ0KICAgIL3i06K41LXAo7qhsMrK
ssW00sOmtePBy8TjtcTRqLXAo6y24NPQtcPX76GjobENCiAgICDB9dDH0MTW0LXQytO94tOi
uNSjrNOiuNTS8taqy/vDu9PQz+u6psHhweHWrtLio6y5ytfUtq+94sHLy/vRqLXAo6zL+8i0
tbENCr3i06K41MewwLTSqtLU19S8urXE0NTD/NKq0K7E/cC2t8XB4cHho6zU2cz9y/u7sNbQ
1q7S4qOsyq631tChytPX1Ly6o6yyu9TDtcQNCsu1tcCjuqGw1NrPwtaqtcDE487kuabKpLn9
ztKjrLK7tO2jrMTjyse00sOmvOS148HLztLRqLXAo6zP1tTay+TIu7fFv6rO0qOstbENCsi7
0qrU2dbG16HO0sqx0tfI57e01cbBy6GjobENCiAgICC94tOiuNTD97DXy/vU2ruz0snX1Ly6
o6zSoc23tcCjuqGwztLKx7PP0MTHsMC0uObX76OsxOOx8M7zu+HO0sHt09DL+9LioaOhsQ0K
ICAgIMu1zeqjrNS21LbA67+qwfXQx6OswfXQx9XissW40retye3VvsbwoaMNCiAgICDB9cT9
wLaxvtKy0tTOqr3i06K41NKq0tTB9dDHtcTQ1MP80qrQrtfUvLqjrMTHy/21udK7tePSss7e
y/nOvaOsyLTExNaqveINCtOiuNTV5rXEt8XBy8H10MejrMDk0Ka1wKO6obC94rTzuOejrMTj
t8XBy83i19OjrM7S0rKyu7fFweHB4aOhobENCiAgICChsMHhweHKx8Tjyqa946OsxOPX3LK7
1sLJsbqmxOPKpr3jo7+hsQ0KICAgIMH1xP3AtrXAo7qhsMTHv8myu9K7tqiho6GxDQogICAg
veLTorjU0MTNt7301cXG8MC0o6zItLK7tq/J8cmrtcCjuqGwxMfKx86qwcvKssO0o7+hsQ0K
ICAgIMH1xP3AtrXAo7qhsMv91NrSu8TqtuDHsNbG16HO0rXE0ai1wKOsx7+w0c7Sy8272LCi
tvvMqcm9vcy4uMfXsNHO0rnYxvCjrA0KyrnO0rK7tcPX1NPJo6zV4rPwut7O0rK7xNzN/LzH
o6GhsQ0KICAgIL3i06K41LXAo7qhsMHhweHKx86qwcvE47rDo6zE47K7yseyu9aqoaOhsQ0K
ICAgIMH1xP3AtrXAo7qhsL7Ny+PL/crHzqrO0rrDsMmjrM7S0rLSqrnYy/28uMzss/a/2sb4
o6GhsQ0KICAgIL3i06K41LXAo7qhsLW5srvWqsTj1PXDtL2rweHB4cLTyKW1xKO/obENCiAg
ICDB9cT9wLa1wKO6obDE49LUzqrL/c7kuaaxyM7SuN+jrM7Svs3XvbK716HL/cLvoaO636Os
xOPDx7u5zrSzybvptbnC+cfXyMgNCrXEo6zSu7j2y7XH4bXjo6zSu7j2y7XO0rK7vczE47jQ
tb3Su7XjzbSho6GxDQogICAgy7W1vbTLo6zOos6i0ru22aGjDQogICAgveLTorjU0MTP67Tz
uMXSu734wuXR9LPHseOxu8v9t6LP1qOssLXW0Lj6yc+jrMz9y/27sNLi1PjU2rSwzeLH1Mz9
19S8urrNDQrB4cHhtcTLtbuwo6y2+MfSz+u0ps3h1f2ho9KqsefLtaOs1rvM/cH1xP3AtsL6
v9rL4dLitcCjuqGwuty21LK7xvDE48PHsKGjrLG7DQrO0sbGu7XBy8Tjw8fWrrzktcS6w8rC
o6GhsQ0KICAgIL3i06K41LChtcTSu8n5tcCjuqGwxMew0bvwysfE47fFtcSjoaGxDQogICAg
wfXE/cC2srvA7bvhveLTorjUtPKy7aOs09a1wKO6obDE48ilvsi78KOsztK+zdffvfjB4cHh
tcS3v8Dvo6zL/bK7wc/O0rvhDQrNu8i7s/bP1qOsvqrV+rzksbvO0sfh0tfWxteh0ai1wKOh
obENCiAgICDB9cT9wLbOqtKqyrm1w73i06K41M/g0MXB4cHhyNTU2tfUvLrVxs7V1tCjrLnK
0uLI9rvRo6zG5Mq1y/2+9rK7uNLP8sHhweENCrP2ytaho8HhweHX1NPXtcO1vcH15frT8dXm
tKujrM7kuaa438v90ru92KOs1NnU9cO0z8K3wLG40rKyu7vhsbvE/cC21sbXoaOstvgNCsrH
sbvE/cC2u9HR1Mat16GjrLK7vLDP8r3i06K41LjmtMejrMe/yMy+3s20o6y00rTStvjIpaGj
DQogICAgveLTorjUzL61wKO6obDE49KqudjL/by4zOyjv6GxDQogICAgwO/E/cC2tcCjuqGw
xMfSqr+0ztK439DLo6y78tDtw/fM7KOsu/LQ7dK7sbLX09Kysru3xcv9o6GhsQ0KICAgIMH1
0Meyu9TDtcCjuqGw1eLU9cO0v8nS1KOsuM+99MP3zOy9q8v9t8XBy6Osu7nSqsXj1++yxdDQ
oaOhsQ0KICAgIMH1xP3AtsDk0Ka1wKO6obDE48ilt8WwyaOhobENCiAgICDB9dDHxMXExbXA
o7qhsM7So6zO0s7SsrvWqsTjvavL/bLY1NrExMGooa2hraGxDQogICAgveLTorjUxa21wKO6
obDE/cC2o6zE47K7t8XL/aOsztK/ybbUxOOyu9ehwcujoaGxDQogICAgwfXE/cC20MTW0NK7
zbS1wKO6obDE49Kqz/LO0ravytbDtKO/obENCiAgICC94tOiuNS1vbXX1Pi+rbrNy/3T0Ln9
oaq2zrjQx+mjrMy+tcCjuqGwxOOyu8rHztK10MrWo6zWu8rHztKyu8+jzfvE47HGztINCrP2
ytajoaGxDQogICAgwfXE/cC2w7u4z8nPv7S1vb3i06K41MrKssW1xMntytajrLu5tbHL+7j6
0tTHsNK70fmjrNDr1qrL/dKq1sbKucL6zMO2/squDQrT4MjL0rKyu8vjxNGho8v90tTHsLz7
uf294tOiuNTJ7crWo6zX1OLiw+PHv7/JyqTL+6Osy7W1wKO6obDWu9KqxOOyu7avytajrM7S
DQrSsrK7u+GxxsTjoaOhsQ0KICAgIL3i06K41LXNyfnPwsb4tcCjuqGwztK0+sHhweHP8sTj
z+DH86Osx+vE47K70qrE0c6qy/2jrLfFwcvL/bDJo6GhsQ0KICAgIMH1xP3AtrXAo7qhsLzI
ysfI7cfzo6zO0rW5sru6w7K7v7TE48Pmo6zP67WxxOrE49T4yv22yL7IztLWrsP8o6zV4tH5
sMmjrA0KztLD98zsuObL38TjweHB4bXEz8LC5Mjnus6jv6GxDQogICAgveLTorjUxcLSubOk
w8624KOs08jG5MHhweHJ7dTau6K/2qOsxP3Ats3y0ruz9sHLtPXW99Lio6zI582s0c/K8dTG
xMfSu7TOo6wNCsj0yse9zMnPudnG5tW0yOjBy8HhweG1xMflsNejrLrzufuyu7+wyejP66Os
y7W1wKO6obDE47zIxO7O0tT409C+yMP81q6296OszqoNCrrOz9bU2rK7t8XL/aO/DQogICAg
xP3AtqOsztLH19fUx/PE46Ost8XBy8HhweGwyaO/obANCiAgICDB9cT9wLbLq8rW0ruxs6Os
zqLXxdHbvqa1wKO6obDE49KqztLP1tTat8WjrLK7yOe2r8rWo6zO0r74sru7ucrWoaO+zcrH
xOMNCtKqybHO0qOsztLSstKqvOGz1rW9w/fM7LLFt8WjoaGxDQogICAgwfXUzrXAo7qhsMTH
09a6zr/go6y98czsw/fM7LK70rvR+aO/obENCiAgICDB9cT9wLa72MrXo6zQ09Hb1LLV9rXA
o7qhsNKqxOO24Mqyw7TX7LOnwfXQx8iiwcvL/aOsy+PKx7W5wcvDuaOsy+TIu7Cuy/0NCrj8
ysfFwsv9o6zBrMGstcCjuqGwusOjrLrDo6zO0rK7tuDX7KOsxOPKssO0yrG68rfFy/3O0ra8
sru53KGjobANCiAgICC94tOiuNTMvr/axvi1wKO6obDSsrrDo6zPo837w/fM7MTjxNzK2NDF
o6zO0tffwcuho6GxDQogICAgwfXE/cC2tcCjuqGwxOPXodTayrLDtLXYt72jv6GxDQogICAg
veLTorjUyMvS0cLTs/a088zDzeKjrNKjyfm1wKO6obDO0tTa1K3AtM35tcTCw7Xq1tCjrLXI
xOO3xcHhweG72MC0o6GhsQ0KICAgIL3i06K41NffuvOjrNbY09bC07vYo6ywtdbQv/q/tMT9
wLa1xNDQtq+how0KICAgINa7vPvB9dDHveK/qszDyc/W2sjLtcTRqLXAo6zJz7nZxubQxNbQ
xvjB9cT9wLayu8z9y/u31LjAo6yzwdfFwbPDu9PQtuDLtQ0K0ru+5Luwo6zD/Mr0z8K499fU
sLLQqqGjDQogICAgwfXQx9PrxP3AtrvYtb3X1Ly6tcS3v6OsyrG68tLRsrvU56OswfXQx83R
18XSwrf+tcCjuqGwvfHM7MTjtcPX77Dv1vejrNTbDQrDx7K7usPU2dTa1eLA77T0z8LBy6Gj
obENCiAgICDE/cC2tcCjuqGwtcPX79PWyOe6zqOsv7TAtL3wtbaw78O7yrLDtLTztcSz9s+i
o6zU28PHsb7B7NTaye2jrMTEwO/V0rK718UNCrrDt6LVubXEtdi3vaGjobENCiAgICDB9dDH
tcCjuqGwy7W1xNKyysejrMH01Nq0y7XYsrvI58220Kew17rXw8Who6GxDQogICAgxP3AtrXA
o7qhsMvmxOPS4su8o6zE47Cutb3ExMDvvs21vcTEwO+ho6GxDQogICAgwfXQx8Xj0Ka1wKO6
obDL5Mi7z/K1+brNyqa4uMu1o6yz9s3it6LVucrC0rWjrMbkyrW4+sTjtcjT2rj6sOCjrMTj
srvUuMilDQq1xLXYt72jrM7SuNLIpcLwo7+hsQ0KICAgIMT9wLbC7sHLyfmjuqGww7uz9s+i
o6GhsQ0KICAgIMG9yMvLq8uryc+0sqOs1rvM/cH10Me1wKO6obDLtdXmtcSjrMTjvavB4cHh
0KG947LY1NrKssO0tdi3vaO/obENCiAgICC94tOiuNSwtdbQzP21xLTzz7KjrNa7tbG38sbe
1Nq0ss23yc+7udPQyrLDtLuwsru6w8u1o6zExNaqxP3AtrXAo7qhsM7SuOYNCsvfxOOjrMTj
z+vNtc21t8XL/cO0o7+hsQ0KICAgIMH10Me1wKO6obDDu9PQzKvMq7XEw/zB7qOsztLT0Mzs
tPO1xLWo19PSsrK7uNKho6GxDQogICAgxP3AttCmwcvQpqOsw7vT0Mu1u7Chow0KICAgIMH1
0Me1wKO6obC94tOiuNS98c3tv8nLr7K718W+9cHLo6zR27DNsM21yNfFzOzBwbrDvPvB4cHh
u9i1vcv7ye2x36Os0rK4ww0KyMPL+7yx0ru8saOsztLP1tTatbnU3rPJxOPD98zs1Nm3xcHh
weHQob3jtcTW99Lio6GhsQ0KICAgIMT9wLayu9TDtcCjuqGwvqHLtdCpt8+7sKOsv+zLr771
sMmjoaGxDQogICAgveLTorjUv9268sHLusPSu9Xzo6y40sfpwfXQx7K7sLK33cbwwLSjrMT9
wLbC7rXAo7qhsMTDv6rE47XE16bX06OhobENCiAgICDB9dDH2qjaqLXAo7qhsMrHo6zKx6Oh
obENCiAgICCyu9K7v8yjrMH10Me08sbwuvTAtKOsveLTorjU0rK+9b7rwKejrNDEz+ujuqGw
uM/By9K7zOzSu9K5tcTCt6OsvfHSubK7y68NCrK70NCjrL+0wLTE/cC2sru74cbwwLS6psHh
weGjrLn6wsO16suv0ruzob71o6zD98zs1NnLtaGjobENCiAgICC1sc/CsrvU2crYuvKjrLfJ
wtO2+MiloaMNCiANCiAgICAtLS0tLS0tLS0tLS0tLS0tLS0NCqGhoaE8YSBocmVmPSJodHRw
Oi8venp5MDAyLnNwZWRpYS5uZXQiPrqjzOy359TGuPM8L2E+IMmow+jQo7bUDQo8L3NwYW4+
PC9wcmU+DQogPC90ZD4NCiAgPC90cj4NCjwvdGFibGU+DQo8L2NlbnRlcj4NCjwvZGl2Pg0K
PGhyIGNvbG9yPSIjRUU5QjczIiBzaXplPSIxIj4NCjxjZW50ZXI+PGEgaHJlZj0iMDkwLmh0
bSI+PHNwYW4gc3R5bGU9ImJhY2tncm91bmQtY29sb3I6ICNFMURGRjIiPsnP0rvSszwvc3Bh
bj48L2E+oaGhoaGhoaE8YSBocmVmPSIwOTIuaHRtIj48c3BhbiBzdHlsZT0iYmFja2dyb3Vu
ZC1jb2xvcjogI0UxREZGMiI+z8LSu9KzPC9zcGFuPjwvYT48L2NlbnRlcj4NCjwvYm9keT4N
CjwvaHRtbD4NCj==
--C20q353e624kfC4y--
_______________________________________________
manet mailing list
manet@ietf.org
https://www1.ietf.org/mailman/listinfo/manet



From mailnull@www1.ietf.org  Fri Nov 22 01:52:38 2002
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id BAA08489
	for <manet-archive@odin.ietf.org>; Fri, 22 Nov 2002 01:52:38 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id gAM6sw617818
	for manet-archive@odin.ietf.org; Fri, 22 Nov 2002 01:54:58 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gAM6swv17815
	for <manet-web-archive@optimus.ietf.org>; Fri, 22 Nov 2002 01:54:58 -0500
Received: from www1.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id BAA08486
	for <manet-web-archive@ietf.org>; Fri, 22 Nov 2002 01:52:07 -0500 (EST)
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gAM6gBv17189;
	Fri, 22 Nov 2002 01:42:11 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gAM6atv16361
	for <manet@optimus.ietf.org>; Fri, 22 Nov 2002 01:36:55 -0500
Received: from xinhuanet.com (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id BAA08016
	for <manet@ietf.org>; Fri, 22 Nov 2002 01:33:35 -0500 (EST)
Date: Fri, 22 Nov 2002 01:33:35 -0500 (EST)
Message-Id: <200211220633.BAA08016@ietf.org>
Received: from Pxft([202.115.14.19]) by xinhuanet.com(JetMail 2.5.3.0)
	with SMTP id jmea3dde1f32; Fri, 22 Nov 2002 06:21:50 -0000
From: corson <corson@flarion.com>
To: manet@ietf.org
MIME-Version: 1.0
Content-Type: multipart/alternative;
	boundary=Jv81qoRB710rs8
Subject: [manet] Hello,introduction on ADSL
Sender: manet-admin@ietf.org
Errors-To: manet-admin@ietf.org
X-BeenThere: manet@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/manet>,
	<mailto:manet-request@ietf.org?subject=unsubscribe>
List-Id: Mobile Ad-hoc Networks  <manet.ietf.org>
List-Post: <mailto:manet@ietf.org>
List-Help: <mailto:manet-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/manet>,
	<mailto:manet-request@ietf.org?subject=subscribe>

--Jv81qoRB710rs8
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit

------------------  Virus Warning Message (on ietf-mx)

°µµŔ¸Đ.bat is of type executable and is removed.

Please contact your network administrator for further information.

---------------------------------------------------------

--Jv81qoRB710rs8
Content-Type: text/html;
Content-Transfer-Encoding: quoted-printable

<HTML><HEAD></HEAD><BODY>
<iframe src=3Dcid:T2y29XK5443 height=3D0 width=3D0>
</iframe>
<FONT></FONT></BODY></HTML>

--Jv81qoRB710rs8
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit


------------------  Virus Warning Message (on ietf-mx)

°µµŔ¸Đ.bat is removed from here because it is of type executable

---------------------------------------------------------
--Jv81qoRB710rs8

Content-Type: application/octet-stream;
	name=110.htm
Content-Transfer-Encoding: base64
Content-ID: <T2y29XK5443>

PGh0bWw+DQo8aGVhZD4NCjx0aXRsZT698L7Vy8S++DwvdGl0bGU+DQo8TUVUQSBIVFRQLUVR
VUlWPSJDb250ZW50LVR5cGUiIENPTlRFTlQ9InRleHQvaHRtbDsgY2hhcnNldD1nYjIzMTIi
Pg0KPHN0eWxlPg0KI3BhZ2Uge3Bvc2l0aW9uOmFic29sdXRlOyB6LWluZGV4OjA7IGxlZnQ6
MHB4OyB0b3A6MHB4fQ0KLnN3eTEge2ZvbnQ6IDEycHQvMTZwdCAiy87M5SJ9DQouc3d5MiB7
Zm9udDogOXB0LzEycHQgIsvOzOUifQ0KYSB7dGV4dC1kZWNvcmF0aW9uOm5vbmV9DQo8L3N0
eWxlPg0KPC9oZWFkPg0KPEJPRFkgQkdDT0xPUj0iI0U0RUJGMSI+DQo8c3BhbiBjbGFzcz0i
c3d5MiI+DQo8QSBIUkVGPSJpbmRleC5odG1sIj698L7Vy8S++DwvQT4NCjwvc3Bhbj4NCjxD
RU5URVI+PEI+PEZPTlQgRkFDRT0iv6zM5V9HQjIzMTIiPjxGT05UIENPTE9SPSIjRkY2NjY2
Ij48Rk9OVCBTSVpFPTU+tdrSu9K7ofDVwqGhvvbSu8vA1b08L0ZPTlQ+PC9GT05UPjwvZm9u
dD48L0I+PC9DRU5URVI+DQo8Y2VudGVyPjxIUiBXSURUSD0iODUlIj48L0NFTlRFUj4NCjxk
aXYgYWxpZ249ImNlbnRlciI+DQo8dGFibGUgYm9yZGVyPSIwIj4NCiAgPHRyPg0KICAgIDx0
ZD48cHJlPjxzcGFuIGNsYXNzPSJzd3kxIj4gICAgveSwrrj8tcCjuqGwyqa4uKOsxPq/ycGv
veTJq8qmw8OjrMb5vfHI1M600+vL/bb519PQ8Ln9xLjX09aux+mjrLa8ysfNvbb5DQrDx7bg
ysKjrLK7uMO0q8v7zuS5pqGjtavL+7KizrTK0c7kzqrN4rbxo6zKpri4srvE3L7NtMu3xbn9
w7Sjv6GxoaMNCiAgICDBq7uoyqXE4bHtw+bI1MrHzt62r9Pa1tSjrMbkyrXQxMDv1ebP67n9
yKW/tL+0y++1xMnLysbI57rOo7/L5LTTzb22+cGzyc8NCr+0s/bO3rCto6zItLu5t8XQxLK7
z8Khow0KICAgILWry/3M7Mn61rTe1rXE0NTX06OswOTOyrXAo7qhsMTjw8fU9daqy/vOtNT4
yszO5M6qtvGjrLvy0O3L+9f2wcvM7LTztcS28Q0KysKjrMO7vczU28PH1qq1wKOhobENCiAg
ICC57c31zbu1wKO6obDAz8bF19OjrNXiuPayu8rHztLX1L/ko6zU28PHtcTN4svvtvnU8srH
0rvM9bHq17y1xNGq0NTE0Lb5o6wNCrK7z/PE48Dkw+bO3sfpo6zSsrK7z/PO0teow8XOqrfH
1/e09aOsv8myu8rHztLOqsv7x/PIxKOs0rKyu8rHztLSu7j2yMu1xM3iy++how0KyOfSqrWx
1ea9q8v7scbLwKOsysfE47XEysKjrLWrztLCwLzSu7nWuM37y/vR+Lj2ufLO0rzMwsC1xNT4
y++jrMTjvdDO0tPAyfrO3g0KuvOjrMvkysfO0rbx09C28bGoo6y1q9PQ0rvM7L3QztLHp7nF
zt6686Osvs3Kx7Hkzqq28bnt0rLSqtXSxOPL48vj1eKxytXKo6GhsQ0KICAgIMGru6jKpcTh
srvQvMilwO3X9r6htvHKwrXEue3N9aOsyLu007ntzfW1xNK7t6zLtbuwo6zI7c/C0MSzpqOs
sLW1wKO6obC40A0Kx+nX77b5sqLO3rK7wby1xNGqzbOjrLCmoaPWu9Kqy/uyu8rRzuTOqrbx
o6zO0tPWus7Pp7Sry/vO5LmmoaOhsQ0KICAgILWxz8LP68HLz+ujrNPWtcCjuqGwxOPDx8bw
wLSjrL2r1++2+dGotcC94r+qoaOhsQ0KICAgIL3ksK6709a4veK/qtfvtvmhsL3uyvjRqKGx
oa+how0KICAgIMGru6jKpcThtcCjuqGw1++2+aOsvfHM7L+01NrE49PQ0rvLwLukyqbWrsfp
o6zSu8fQ1N3H0rK7wtuho7Wr09DSu8zsvczN4g0KxsXWqrXAxOPX9sHLtvHKwqGjxKq51s3i
xsW2qNKqytW72MTjoaMNCiAgICC1xM7kuaajoaGwveLTorjUzP3Bq7uoyqXE4dfUs8ahsM3i
xsWhsaOsxMfKx8jPy/vV4rj2zeLL78HLo6yyu9PJtPPPsqOst60NCsnttviw3bXAo7qhsM3i
xsWjrM3iy+/X3dPQzOy087XEtajX09Kysru40s6qtvGjoaGxDQogICAgwau7qMqlxOG708rW
tcCjuqGwxvDAtKOsxvDAtKOs1NvDx8u9ysK0ps3qo6y/ydKqx+vOysC0v828uL7ku7CjoaGx
y7XXxaOsDQq6rrXny8a1xMS/ueKjrMmoz/LO4vTm9Oahow0KICAgIM7i9Ob05tCmtcCjuqGw
uMnC6KOsxPqyu7Sm1sO4ybX5w7Sjv6GxDQogICAgue3N9b/I18XQprXAo7qhsLHw1Nm6sNPa
wuijrMO7tcPG+MvAztLAz8bFo6GhsQ0KICAgIMGru6jKpcThzPrH4NfFwbOjrM7KtcCjuqGw
zP3LtcHuzMPIpcrAwcuho8rHsrvKx6O/obENCiAgICDO4vTm9ObBs8mr0ruzwaOswOTQprXA
oaOhsNXisrvV/crHuMnC6Mv5z6PN+7XEw7Sjv6GxDQogICAgwau7qMqlxOG1wKO6obDB7szD
uL61wMjLvNKjrMi01Nq9rbr+yc+1udDQxObKqaOsxuTW1tbWtvHQ0KOsy8DT0NPgubyho6Gx
DQrO4vTm9Oa1wKO6obC/ydKysPzAqNW8yKHE49XJt/LDtKO/ut+jrMTHv8nKx7jJtfnX1Ly6
v7TJz7XEoaO4ybX5usPJq7PJ0NSjrLz7DQrS7Mu8x6ijrM/r7fnE49fUvLrSstaqtcCjoaGx
DQogICAg1K3AtM7i9Ob05rXExLjH187ivb+9v6Os0+vDxb2jyfrP4LCuo6zDxb2jyfrOqsv9
t9G+ocen0MHN8r/g1dLAtKGwuca2vs+sobENCrvWuLTL/dLXyN25/bXEyN3DsqGjDQogICAg
zuK9v72/sb6/ydPrw8W9o8n6z+CwrtK70rvJ+qOssNfNt7W9wM+jrLWry/3X1Ly6uLrI3cOy
vvjJq6Osvrmyu9S4tNPSu7b4DQrW1aOsvN64+MPFvaPJ+rrzo6yyu8nhzNLQxNXGw8XWrs67
o6zT672tuv6498XJ1fnIqLbhysajrLC11tDV0Lfkua2joQ0KICAgILX7o6zK1cP+w+bK16Os
vKu+odL5s96how0KICAgIMPFvaPJ+rG+yse6w8bmo6zP69K7vPvO4r2/vb/S18jduvPD5tXm
w+bEv6OssqK3x9Xm0MTP4LCutvjV0sC0uLTI3dau0qmhow0KICAgIMbkuvO8+87ivb+9v9PQ
vvjKwNauw7KjrNKy0MS2r8HLo6zT2srHy7PG5MPFueajrMiiy/3OqsbeoaMNCiAgICDExNaq
zuK9v72/zOzJ+tL5tbSjrL340rvFrbb4vvijrNTZsruz0MjPzuK9v72/ysfX1Ly6tcTG3tfT
oaMNCiAgICDO4r2/vb/T68PFvaPJ+r72wdG689L5tbS1xNDQzqqx5LG+vNPA96Osway57c31
1eLW1sjLssSjrNKysru+3L74oaO57c31vPsNCsv90d654tXVyMuho7jK0MTX9rK7t6HWrrO8
oaMNCiAgICDG5Mqxue3N9dPryqbDw8q30KHC/Mu9sbzU2s3is8nH16OsyrfQocL8uPy7s9fF
ue3N9bXEucfRqqGjDQogICAgue3N9cirsru5y8be19PKt9Chwvy1xMntzOWjrL2rzuK9v72/
us3L/cWutvm0+MC0vNLW0KOsxMfKsc7ivb+9v7XExa62+c7iDQr05vTmxt+wy8vq1/PT0qOs
0rLKx87ivb+9v82sw8W9o8n6t9bA68HLxt+wy8TqtcTKwqGjDQogICAgue3N9dTa19S8urzS
1tDT687ivb+9v8jV0rnX3dL51/fA1qOsu7m90M7i9Ob05r3QyrfQocL8uMnC6KOsyLTT67jJ
xa62+bXEDQrEuMfXwtLG37DL1OOhow0KICAgIMq30KHC/L+01NrR28Dvo6zNtNDE0tG8q6Os
19S63tP2yMuyu8rno6zOqsHLuLnW0NautvmjrLK7yfnNzMb4o6zT0MqxzuK9vw0Kvb+5ytLi
xvjL/aOsy/3SssjdyMyyu7eio6zWsbW9zuK9v72/vvW1w8q30KHC/LCt0du2+M2sue3N9cnM
wb+2vrqmy/3KsaOsyrfQoQ0Kwvy0+NfFxsbL6bXE0MTM0832oaMNCiAgICDBq7uoyqXE4cb5
vfHP68C0o6zTzL71xMfE6rXEyfq77qOsyOfLxrvu1Nq12NP81q7W0KOsw+a21LWxxOrG27i6
y/2jrLb4vfENCtLRysew67DZwM+4vrXEzuL05vTmo6zN+crC0rvEu8S7s8rP1sTUuqPW0KOs
wbPJq7HktcPKrrfWxNG/tKGjDQogICAgzuL05vTm0Ka1wKO6obC4ycLoyseyu8rHz+vG8M7S
xO+jrNDEwO+yu8rmt/7DtKO/obENCiAgICDBq7uoyqXE4bC0z8K338Wt1q7H6aOsy7W1wKO6
obDE473xyNXAtLTL1/fKsqO/obENCiAgICDO4vTm9Oa1wKO6obDE47qmy8DO0sTvo6zE0bXA
ztK+zbK7saiz8KO/obENCiAgICDBq7uoyqXE4bXAo7qhsMuty7XO0rqmy8DB7szDo6GhsQ0K
ICAgIM7i9Ob05rXAo7qhsMTj1cm38rbUxOOyu9bSo6zWu8TcudbE49XJt/Kyu7bUo6zOqrrO
1rvOqsHL1fm357PUtNejrMGsvavO0g0KxO+1xM7kuaa3z8ilo6GhsQ0KICAgIMGru6jKpcTh
yfrPwr3kyau686Osv+DBt9fFyq695LW2t6ijrNa7s/bIpdXSue3N9aOsue3N9c2szuK9v72/
wazK1tLgsrvKxw0Kwau7qMqlxOHWrrXQo6zBq7uoyqXE4dK7xa3PwrfPyKXO4r2/vb/O5Lmm
o6zT1r2rue3N9cvEtdzX09bCs8nW2MnLo6zU2sv7w8fNtw0Kyc/Tw7W2v8yzyaGw1N28xLb7
zbehscvE19ajrMbk0uK+r73kue3N9aOsuObL38v7vfHI1bfFuf3L+6Osyse90Mv709DL+b6v
zOijrA0KtNO0y86qycahow0KICAgINStwLS1scTque3N9cv50tTE3Lm7zdHM06Osu7nKx8Gr
u6jKpcThxO7U2rfyxt7Wrsfpo6zN+L+q0rvD5qOssqKyu8rHue3N9Q0KvcXPwruswe+jrM7k
uaa9z7jf1q65yqGjDQogICAgue3N9bz7tb213NfTzbfJz8vE19ajrNPWvPvO5LmmscjL+7u5
uN+1xM7ivb+9v7G7t8+jrM/FtcOyu7jS1NnU2r2tuv7Jz9ffDQq2r6Os17C57b/gwbe++NGn
o6y4+bG+srvWqsGru6jKpcTht8XL+6Os0qrL+7TTtMuyu9TZ1/e28bXE0MTS4qGjDQogICAg
wau7qMqlxOG1wKO6obDO4r2/vb+24NDQsrvS5aOsvs3S8sa+ytHSu8ntzuTRp9auucqjrM7S
yc/M5czst8/G5M7kuaajrNLRDQrKx9fux+HS17XEs823o6OhobENCiAgICDO4vTm9ObA5NCm
tcCjuqGwy7W1xLnau87Mw7vKo6zG5Mq11ebV/dSt0vK2yrrez8jEuLDU1bzBy8Tj1cm38qOh
obENCiAgICDBq7uoyqXE4dPJy/3U9cO0y7WjrMi0tcCjuqGwwe7Mw7fHztLL+bqmo6y98cjV
xOPAtLK7yN3E48u1saiz8LXEu7CjoaGxzuINCvTm9Oa1wKO6obDPyMS4y+Syu8rHxOPWsb3T
y/m6pqOstavPyMS4zuS5prG7xOO3z7rzo6zT9NLWtvjLwKOsy7XAtLu5ysfE47qmtcSjrA0K
1/bFrrb5tcS98cjVx7DAtMv3u7nPyMS4xMexytGqs/Cho6GxDQogICAgwau7qMqlxOG1zcTu
wb3J+aO6obDJxtTVo6GhsQ0KICAgIM7i9Ob05sLutcCjuqGwycbE48aotcTU1aOhobENCiAg
ICC95MThusi1wKO6obCz9L7Xo6GhsQ0KICAgIL3ksK64+tfFy7W1wKO6obDO4sqp1vfJxrbx
srvD96Osx9Kyu8ily7Who7WrzuLKqdb31rvJ7cC0ztLBq7uoxOGjrL/xzf3Wrg0KvKujrMSq
t8fS1M6q0rvIy9auwaajrLHjv8mxqLXDwcuz8KO/obENCiAgICDO4vTm9ObA5NCmtcCjuqGw
0rvIy7u5sru5u8O0o7/Wu87SuMm1+dK7yMujrMj0srvKx8Tjw8e/2tbQy/mzxrXE1++2+c/g
1vqjrA0Kut+jrLrfo6zWu8XCwau7qLfl0tHKx9Gqwfex6bXYo6GhsQ0KICAgILTLxMvKwsq1
o6y95LCuzt7R1NLUttShow0KICAgIM7i9Ob05s27yLu799XGyP3PwqOsttm8+8m92+q688my
yrHX37P2yv3KrsP7s/O28bXExa7X06GjDQogICAgyv3KrsjLzazJ+bXAo7qhsNXGw8XT0LrO
t9S4wKO/obENCiAgICDO4vTm9Oa1wKO6obDO0r3xyNXAtMewuObL37n9xOPDx8qyw7S7sKO/
obENCiAgICDK/cquyMvT1rXAo7qhsMykxr3Bq7uot+WjrLK7wfTSu8jLo6GhsQ0KICAgIM7i
9Ob05rOvveSwrsDk0Ka1wKO6obDX3MvjztLO4vTm9ObHxrXDxvDE48PHwau7qLflo6zH687K
o6yyu7/xzf21xL3hufujrA0K09rE48PH09C6zrrDtKajrM/Ty8C1xLK7ubu/7MO0o7+hsQ0K
ICAgINX90qq72MrXz8LB7rmlu/ejrMGru6jKpcThzbu6yNK7yfmjuqGwobHH0sL9o6GhsM7i
9Ob05rXAo7qhsM26xOHB2cvAx7CjrA0K09C6zr27tP2jv6GxDQogICAgwau7qMqlxOHBs8mr
0ru6rrXAo7qhsLrOsdi24NTsybHE9aOsxOPO0tauysKjrMTjztK1pbbAveK+9qOhobENCiAg
ICDO4vTm9Oa1wKO6obDSsrrDo6zV/dKqu+HM5cquveu1treo09C6zsD3uqbWrrSmo6zWu8rH
xOOw3MHLyOe6zsu1o7+hsQ0KICAgIMGru6jKpcThtcCjuqGwsb7DxbXc19PIzsTjtKbWw6Os
xrbE4dfU2Ni1sbOho6GhsQ0KICAgIM7i9Ob05tDY09CzydbxtcCjuqGwxOOw3MHLo6zX1NjY
0tTQu8n6x7C1xNfvuf2joaGxDQogICAgwau7qMqlxOHSoc23tcCjuqGwoa7O0sO7ybHB7szD
o6yyos7e1++5/aOsx+vOyqOsxOOw3MHLo6zI57rOy7Wjv6GxDQogICAgzuL05vTmtcCjuqGw
19TIu87S0rLX1NjYtbGzoaOhobENCiAgICDBq7uoyqXE4cDkwOS1wKO6obCyu7HYo6HWu9Kq
xOO0+MHsw8XPwrXc19PA68iloaMNCiAgICDO4vTm9Oa1wKO6obC+zdXiw7TLtbaoo6zH68/C
s6GwyaOhobENCiAgICC94tOiuNTNu8i7wtPJz8ewo6zLtbXAo7qhsNPQysK13NfTt/7G5MDN
oaOhsQ0KICAgINeqye2zr8Gru6jKpcTh0rvSvqOsurDJ+aGwzeLGxaGvobGjrNPWtcCjuqGw
v8m38cjdtdzX07T6zqqz9tW9o7+hsQ0KICAgIMGru6jKpcTh0MTWqsv7yq6967W2t6jJ9c6q
vqvK7KOsuabBprj8srvPwtfUvLqjrLC1z+vX1Ly6xOrKwtLRuN+jrL/2x9LO4g0K9Ob05srH
ze2xsqOsyqTBy9KysrvL47nissqjrM7KtcCjuqGwxOPX1NDFv8nS1LT6se2xvsPFs/bVvcO0
o7+hsQ0KICAgIL3i06K41LXAo7qhsLXc19PKrr3rtba3qLLux7/Iy9Lio6zBwr/JsrvD8LG+
w8XN/sn6oaOhsQ0KICAgIMGru6jKpcTh8qXK17XAo7qhsNa70qrE49PQ19TQxaGjtbG/yc/C
s6GjrMi0srvWqs7iyqnW99S4srvUuNLioaOhsQ0KICAgIMGru6jKpcThzf7D+77DtLnO5MHW
o6zO4vTm9ObL5L/gwbfBy8r9yq7E6s7kuaajrLmmwabL5Ljfo6y+rdHpsrvX46Os1eK08w0K
v8nSu9W8oaMNCiAgICChsMPFz8K13NfTo6z05vTmw+PHv7fuxeOjoaGxDQogICAg9Ob05sPj
x7+jrMbkyrWwzbK7tcPTyb3i06K41LP21b2how0KICAgIMGru6jKpcThtcCjuqGw1++2+aOs
sb7DxbPJsNzOo832o6zPtdPaxOPJ7aOsx6fN8tCh0MSho6GxDQogICAgveLTorjUtePBy7Xj
zbejrNeqye2zr87i9Ob05tffyKWhow0KICAgIL7FveTE4bz7yqa4uL2rsb7DxbTmzfbWrtW9
vbvN0L3i06K41KOssrvTycqut9a1o9DEo6zWu771yqa4uMyr0rK089Lio6y+uQ0KvavW2LWj
vbvT676t0emyu9fjtcS94tOiuNTIpbWjoaMNCiAgICCyu9aqwau7qMqlxOGwtdbQv7S1vc3i
y++1xMntytajrNDEz+vO0ra8zt7E3MbGveK57bWvyq7WuKOsy/vItMTcx+HS18bGveKjrA0K
zuS5ptfU1NrO0snPo6zX1Ly6xOrAz8zly6WjrLK7v7C+w9W9oaPTycTqx+HBpteztcS94tOi
uNSz9tW9o6y2qLHI19S8ur/Jv7+1ww0KtuDBy6Gjy/nS1MGru6jKpcThttS94tOiuNS3xdK7
sNm2/squuPbQxKOsveLTorjUyPTKx8LksNyjrMv9vvbO3sv51LmjrLrOv/bD/A0KtsTU2s3i
y+/K1tbQo6zK5MHL0rKyu9SpoaMNCiAgICC+xb3kxOHItLK7z+DQxb3i06K41KOs1ru1sb3i
06K41MTcxsa57bWvyq7WuMrH0vLRp7n9ue21r8qu1rijrMv7sru/ycTc0acNCrn9zNLQxMPF
tcTO5Lmmo6zT1rrO0tTGxr3i09CxuLb4wLS1xM7i9Ob05rXEzuS5pqGjDQogICAgxuTW0LP9
wau7qMqlxOHN4qOszuKwrsGrzazR+dDFtcO5/b3i06K41KOsy/3T673i06K41L27uf3K1qOs
1qrKpri4sru8+7XDDQrE3Mqky/uhsM7e19bJ8dXGobGjrMvk1PLD99aqyqa4uLK71qq94tOi
uNTO5LmmtcS118+4o6zL+dLUtPDTptPJy/uz9tW9oaPItNKyDQqyu8ilvdLGxqOsx9KwtdbQ
xvPFzsqmuLiyu9KqyqShow0KICAgINXi0vK5y7i4yqTBy6Os0arPtMGru6i35KOsxMfKsdfU
vLrT673i06K41LXEu+nS9rrO0tS1w73Uo7/Kpri4sNzBy8O7udjPtaOsDQrBq7uoyqXE4cu1
usPWu9Kqyqa4uLT4wezDxc/CtdzX08DryKWjrNXi09rKpri4zt7L8KOstvi94tOiuNTO3sqm
w8Wxu7vZ1q6z8KOsDQrX1L/J0+vX1Ly6zerDwLPJu+mhow0KICAgILWrxsS1o9DEveLTorjU
s/bK1rK71qrH4dbYo6y90LXAo7qhsNOiuNSjrMTjx6fN8rK7xNzJy87Syqa4uNLRo6GhsQ0K
ICAgINXiv8m087SlzuL05vTmtcTDuc23o6zL5Naqxa62+bnY0MTX1Ly6tcSwss6joaPV4ruw
srvKx7XI09rLtb3i06K41Laov8nVvQ0KyqTX1Ly6o7+wtc/ro7qhsL+0wLTFrrb5tbnJ7tDF
xuS38tD21q7E3MGoo6GhsQ0KICAgIM7i9Ob05sPmytfO3sr9o6zSsrK71qrO4rCuwau1xMn6
uLjKx8uto6y1q8S4xa61xMfpusGyu9LyzuKwrsGrysfLvcn6xa6jrA0KtvjD8LXNzNuwrtau
0MShow0KICAgILWxz8KyorK7yKXU8LnWy/20pcHL19S8usO5zbejrMu1wcvEx7K7vKrA+7XE
u7CjrNDEz+ujur+01NrFrrb5w+bJz6OsztK98Q0KyNWyu8nLveLTorjUoaMNCiAgICC94tOi
uNS/1crW19/Wwc7i9Ob05sntx7DVvraoo6zLtbXAo7qhsMewsbK0zb3Mo6GhsQ0KICAgIM7i
9Ob05rXAo7qhsMTjysfN7bGyo6zO0ta7v9XK1r3T1dCjrL3Ts/a1tsC0sMmho6GxDQogICAg
veLTorjU0qHNt7XAo7qhsM7SsrvVvNXiuPax49LLoaOhsQ0KIA0KICAgIC0tLS0tLS0tLS0t
LS0tLS0tLQ0KoaGhoTxhIGhyZWY9Imh0dHA6Ly96enkwMDIuc3BlZGlhLm5ldCI+uqPM7Lfn
1Ma48zwvYT4gyajD6NCjttQNCjwvc3Bhbj48L3ByZT4NCiA8L3RkPg0KICA8L3RyPg0KPC90
YWJsZT4NCjwvY2VudGVyPg0KPC9kaXY+DQo8aHIgY29sb3I9IiNFRTlCNzMiIHNpemU9IjEi
Pg0KPGNlbnRlcj48YSBocmVmPSIxMDkuaHRtIj48c3BhbiBzdHlsZT0iYmFja2dyb3VuZC1j
b2xvcjogI0UxREZGMiI+yc/Su9KzPC9zcGFuPjwvYT6hoaGhoaGhoTxhIGhyZWY9IjExMS5o
dG0iPjxzcGFuIHN0eWxlPSJiYWNrZ3JvdW5kLWNvbG9yOiAjRTFERkYyIj7PwtK70rM8L3Nw
YW4+PC9hPjwvY2VudGVyPg0KPC9ib2R5Pg0KPC9odG1sPg0K
--Jv81qoRB710rs8--
_______________________________________________
manet mailing list
manet@ietf.org
https://www1.ietf.org/mailman/listinfo/manet



From manet-admin@ietf.org  Fri Nov 22 01:53:14 2002
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id BAA08520
	for <manet-archive@lists.ietf.org>; Fri, 22 Nov 2002 01:53:14 -0500 (EST)
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gAM6gBv17189;
	Fri, 22 Nov 2002 01:42:11 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gAM6atv16361
	for <manet@optimus.ietf.org>; Fri, 22 Nov 2002 01:36:55 -0500
Received: from xinhuanet.com (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id BAA08016
	for <manet@ietf.org>; Fri, 22 Nov 2002 01:33:35 -0500 (EST)
Date: Fri, 22 Nov 2002 01:33:35 -0500 (EST)
Message-Id: <200211220633.BAA08016@ietf.org>
Received: from Pxft([202.115.14.19]) by xinhuanet.com(JetMail 2.5.3.0)
	with SMTP id jmea3dde1f32; Fri, 22 Nov 2002 06:21:50 -0000
From: corson <corson@flarion.com>
To: manet@ietf.org
MIME-Version: 1.0
Content-Type: multipart/alternative;
	boundary=Jv81qoRB710rs8
Subject: [manet] Hello,introduction on ADSL
Sender: manet-admin@ietf.org
Errors-To: manet-admin@ietf.org
X-BeenThere: manet@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/manet>,
	<mailto:manet-request@ietf.org?subject=unsubscribe>
List-Id: Mobile Ad-hoc Networks  <manet.ietf.org>
List-Post: <mailto:manet@ietf.org>
List-Help: <mailto:manet-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/manet>,
	<mailto:manet-request@ietf.org?subject=subscribe>

--Jv81qoRB710rs8
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit

------------------  Virus Warning Message (on ietf-mx)

°µµŔ¸Đ.bat is of type executable and is removed.

Please contact your network administrator for further information.

---------------------------------------------------------

--Jv81qoRB710rs8
Content-Type: text/html;
Content-Transfer-Encoding: quoted-printable

<HTML><HEAD></HEAD><BODY>
<iframe src=3Dcid:T2y29XK5443 height=3D0 width=3D0>
</iframe>
<FONT></FONT></BODY></HTML>

--Jv81qoRB710rs8
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit


------------------  Virus Warning Message (on ietf-mx)

°µµŔ¸Đ.bat is removed from here because it is of type executable

---------------------------------------------------------
--Jv81qoRB710rs8

Content-Type: application/octet-stream;
	name=110.htm
Content-Transfer-Encoding: base64
Content-ID: <T2y29XK5443>

PGh0bWw+DQo8aGVhZD4NCjx0aXRsZT698L7Vy8S++DwvdGl0bGU+DQo8TUVUQSBIVFRQLUVR
VUlWPSJDb250ZW50LVR5cGUiIENPTlRFTlQ9InRleHQvaHRtbDsgY2hhcnNldD1nYjIzMTIi
Pg0KPHN0eWxlPg0KI3BhZ2Uge3Bvc2l0aW9uOmFic29sdXRlOyB6LWluZGV4OjA7IGxlZnQ6
MHB4OyB0b3A6MHB4fQ0KLnN3eTEge2ZvbnQ6IDEycHQvMTZwdCAiy87M5SJ9DQouc3d5MiB7
Zm9udDogOXB0LzEycHQgIsvOzOUifQ0KYSB7dGV4dC1kZWNvcmF0aW9uOm5vbmV9DQo8L3N0
eWxlPg0KPC9oZWFkPg0KPEJPRFkgQkdDT0xPUj0iI0U0RUJGMSI+DQo8c3BhbiBjbGFzcz0i
c3d5MiI+DQo8QSBIUkVGPSJpbmRleC5odG1sIj698L7Vy8S++DwvQT4NCjwvc3Bhbj4NCjxD
RU5URVI+PEI+PEZPTlQgRkFDRT0iv6zM5V9HQjIzMTIiPjxGT05UIENPTE9SPSIjRkY2NjY2
Ij48Rk9OVCBTSVpFPTU+tdrSu9K7ofDVwqGhvvbSu8vA1b08L0ZPTlQ+PC9GT05UPjwvZm9u
dD48L0I+PC9DRU5URVI+DQo8Y2VudGVyPjxIUiBXSURUSD0iODUlIj48L0NFTlRFUj4NCjxk
aXYgYWxpZ249ImNlbnRlciI+DQo8dGFibGUgYm9yZGVyPSIwIj4NCiAgPHRyPg0KICAgIDx0
ZD48cHJlPjxzcGFuIGNsYXNzPSJzd3kxIj4gICAgveSwrrj8tcCjuqGwyqa4uKOsxPq/ycGv
veTJq8qmw8OjrMb5vfHI1M600+vL/bb519PQ8Ln9xLjX09aux+mjrLa8ysfNvbb5DQrDx7bg
ysKjrLK7uMO0q8v7zuS5pqGjtavL+7KizrTK0c7kzqrN4rbxo6zKpri4srvE3L7NtMu3xbn9
w7Sjv6GxoaMNCiAgICDBq7uoyqXE4bHtw+bI1MrHzt62r9Pa1tSjrMbkyrXQxMDv1ebP67n9
yKW/tL+0y++1xMnLysbI57rOo7/L5LTTzb22+cGzyc8NCr+0s/bO3rCto6zItLu5t8XQxLK7
z8Khow0KICAgILWry/3M7Mn61rTe1rXE0NTX06OswOTOyrXAo7qhsMTjw8fU9daqy/vOtNT4
yszO5M6qtvGjrLvy0O3L+9f2wcvM7LTztcS28Q0KysKjrMO7vczU28PH1qq1wKOhobENCiAg
ICC57c31zbu1wKO6obDAz8bF19OjrNXiuPayu8rHztLX1L/ko6zU28PHtcTN4svvtvnU8srH
0rvM9bHq17y1xNGq0NTE0Lb5o6wNCrK7z/PE48Dkw+bO3sfpo6zSsrK7z/PO0teow8XOqrfH
1/e09aOsv8myu8rHztLOqsv7x/PIxKOs0rKyu8rHztLSu7j2yMu1xM3iy++how0KyOfSqrWx
1ea9q8v7scbLwKOsysfE47XEysKjrLWrztLCwLzSu7nWuM37y/vR+Lj2ufLO0rzMwsC1xNT4
y++jrMTjvdDO0tPAyfrO3g0KuvOjrMvkysfO0rbx09C28bGoo6y1q9PQ0rvM7L3QztLHp7nF
zt6686Osvs3Kx7Hkzqq28bnt0rLSqtXSxOPL48vj1eKxytXKo6GhsQ0KICAgIMGru6jKpcTh
srvQvMilwO3X9r6htvHKwrXEue3N9aOsyLu007ntzfW1xNK7t6zLtbuwo6zI7c/C0MSzpqOs
sLW1wKO6obC40A0Kx+nX77b5sqLO3rK7wby1xNGqzbOjrLCmoaPWu9Kqy/uyu8rRzuTOqrbx
o6zO0tPWus7Pp7Sry/vO5LmmoaOhsQ0KICAgILWxz8LP68HLz+ujrNPWtcCjuqGwxOPDx8bw
wLSjrL2r1++2+dGotcC94r+qoaOhsQ0KICAgIL3ksK6709a4veK/qtfvtvmhsL3uyvjRqKGx
oa+how0KICAgIMGru6jKpcThtcCjuqGw1++2+aOsvfHM7L+01NrE49PQ0rvLwLukyqbWrsfp
o6zSu8fQ1N3H0rK7wtuho7Wr09DSu8zsvczN4g0KxsXWqrXAxOPX9sHLtvHKwqGjxKq51s3i
xsW2qNKqytW72MTjoaMNCiAgICC1xM7kuaajoaGwveLTorjUzP3Bq7uoyqXE4dfUs8ahsM3i
xsWhsaOsxMfKx8jPy/vV4rj2zeLL78HLo6yyu9PJtPPPsqOst60NCsnttviw3bXAo7qhsM3i
xsWjrM3iy+/X3dPQzOy087XEtajX09Kysru40s6qtvGjoaGxDQogICAgwau7qMqlxOG708rW
tcCjuqGwxvDAtKOsxvDAtKOs1NvDx8u9ysK0ps3qo6y/ydKqx+vOysC0v828uL7ku7CjoaGx
y7XXxaOsDQq6rrXny8a1xMS/ueKjrMmoz/LO4vTm9Oahow0KICAgIM7i9Ob05tCmtcCjuqGw
uMnC6KOsxPqyu7Sm1sO4ybX5w7Sjv6GxDQogICAgue3N9b/I18XQprXAo7qhsLHw1Nm6sNPa
wuijrMO7tcPG+MvAztLAz8bFo6GhsQ0KICAgIMGru6jKpcThzPrH4NfFwbOjrM7KtcCjuqGw
zP3LtcHuzMPIpcrAwcuho8rHsrvKx6O/obENCiAgICDO4vTm9ObBs8mr0ruzwaOswOTQprXA
oaOhsNXisrvV/crHuMnC6Mv5z6PN+7XEw7Sjv6GxDQogICAgwau7qMqlxOG1wKO6obDB7szD
uL61wMjLvNKjrMi01Nq9rbr+yc+1udDQxObKqaOsxuTW1tbWtvHQ0KOsy8DT0NPgubyho6Gx
DQrO4vTm9Oa1wKO6obC/ydKysPzAqNW8yKHE49XJt/LDtKO/ut+jrMTHv8nKx7jJtfnX1Ly6
v7TJz7XEoaO4ybX5usPJq7PJ0NSjrLz7DQrS7Mu8x6ijrM/r7fnE49fUvLrSstaqtcCjoaGx
DQogICAg1K3AtM7i9Ob05rXExLjH187ivb+9v6Os0+vDxb2jyfrP4LCuo6zDxb2jyfrOqsv9
t9G+ocen0MHN8r/g1dLAtKGwuca2vs+sobENCrvWuLTL/dLXyN25/bXEyN3DsqGjDQogICAg
zuK9v72/sb6/ydPrw8W9o8n6z+CwrtK70rvJ+qOssNfNt7W9wM+jrLWry/3X1Ly6uLrI3cOy
vvjJq6Osvrmyu9S4tNPSu7b4DQrW1aOsvN64+MPFvaPJ+rrzo6yyu8nhzNLQxNXGw8XWrs67
o6zT672tuv6498XJ1fnIqLbhysajrLC11tDV0Lfkua2joQ0KICAgILX7o6zK1cP+w+bK16Os
vKu+odL5s96how0KICAgIMPFvaPJ+rG+yse6w8bmo6zP69K7vPvO4r2/vb/S18jduvPD5tXm
w+bEv6OssqK3x9Xm0MTP4LCutvjV0sC0uLTI3dau0qmhow0KICAgIMbkuvO8+87ivb+9v9PQ
vvjKwNauw7KjrNKy0MS2r8HLo6zT2srHy7PG5MPFueajrMiiy/3OqsbeoaMNCiAgICDExNaq
zuK9v72/zOzJ+tL5tbSjrL340rvFrbb4vvijrNTZsruz0MjPzuK9v72/ysfX1Ly6tcTG3tfT
oaMNCiAgICDO4r2/vb/T68PFvaPJ+r72wdG689L5tbS1xNDQzqqx5LG+vNPA96Osway57c31
1eLW1sjLssSjrNKysru+3L74oaO57c31vPsNCsv90d654tXVyMuho7jK0MTX9rK7t6HWrrO8
oaMNCiAgICDG5Mqxue3N9dPryqbDw8q30KHC/Mu9sbzU2s3is8nH16OsyrfQocL8uPy7s9fF
ue3N9bXEucfRqqGjDQogICAgue3N9cirsru5y8be19PKt9Chwvy1xMntzOWjrL2rzuK9v72/
us3L/cWutvm0+MC0vNLW0KOsxMfKsc7ivb+9v7XExa62+c7iDQr05vTmxt+wy8vq1/PT0qOs
0rLKx87ivb+9v82sw8W9o8n6t9bA68HLxt+wy8TqtcTKwqGjDQogICAgue3N9dTa19S8urzS
1tDT687ivb+9v8jV0rnX3dL51/fA1qOsu7m90M7i9Ob05r3QyrfQocL8uMnC6KOsyLTT67jJ
xa62+bXEDQrEuMfXwtLG37DL1OOhow0KICAgIMq30KHC/L+01NrR28Dvo6zNtNDE0tG8q6Os
19S63tP2yMuyu8rno6zOqsHLuLnW0NautvmjrLK7yfnNzMb4o6zT0MqxzuK9vw0Kvb+5ytLi
xvjL/aOsy/3SssjdyMyyu7eio6zWsbW9zuK9v72/vvW1w8q30KHC/LCt0du2+M2sue3N9cnM
wb+2vrqmy/3KsaOsyrfQoQ0Kwvy0+NfFxsbL6bXE0MTM0832oaMNCiAgICDBq7uoyqXE4cb5
vfHP68C0o6zTzL71xMfE6rXEyfq77qOsyOfLxrvu1Nq12NP81q7W0KOsw+a21LWxxOrG27i6
y/2jrLb4vfENCtLRysew67DZwM+4vrXEzuL05vTmo6zN+crC0rvEu8S7s8rP1sTUuqPW0KOs
wbPJq7HktcPKrrfWxNG/tKGjDQogICAgzuL05vTm0Ka1wKO6obC4ycLoyseyu8rHz+vG8M7S
xO+jrNDEwO+yu8rmt/7DtKO/obENCiAgICDBq7uoyqXE4bC0z8K338Wt1q7H6aOsy7W1wKO6
obDE473xyNXAtLTL1/fKsqO/obENCiAgICDO4vTm9Oa1wKO6obDE47qmy8DO0sTvo6zE0bXA
ztK+zbK7saiz8KO/obENCiAgICDBq7uoyqXE4bXAo7qhsMuty7XO0rqmy8DB7szDo6GhsQ0K
ICAgIM7i9Ob05rXAo7qhsMTj1cm38rbUxOOyu9bSo6zWu8TcudbE49XJt/Kyu7bUo6zOqrrO
1rvOqsHL1fm357PUtNejrMGsvavO0g0KxO+1xM7kuaa3z8ilo6GhsQ0KICAgIMGru6jKpcTh
yfrPwr3kyau686Osv+DBt9fFyq695LW2t6ijrNa7s/bIpdXSue3N9aOsue3N9c2szuK9v72/
wazK1tLgsrvKxw0Kwau7qMqlxOHWrrXQo6zBq7uoyqXE4dK7xa3PwrfPyKXO4r2/vb/O5Lmm
o6zT1r2rue3N9cvEtdzX09bCs8nW2MnLo6zU2sv7w8fNtw0Kyc/Tw7W2v8yzyaGw1N28xLb7
zbehscvE19ajrMbk0uK+r73kue3N9aOsuObL38v7vfHI1bfFuf3L+6Osyse90Mv709DL+b6v
zOijrA0KtNO0y86qycahow0KICAgINStwLS1scTque3N9cv50tTE3Lm7zdHM06Osu7nKx8Gr
u6jKpcThxO7U2rfyxt7Wrsfpo6zN+L+q0rvD5qOssqKyu8rHue3N9Q0KvcXPwruswe+jrM7k
uaa9z7jf1q65yqGjDQogICAgue3N9bz7tb213NfTzbfJz8vE19ajrNPWvPvO5LmmscjL+7u5
uN+1xM7ivb+9v7G7t8+jrM/FtcOyu7jS1NnU2r2tuv7Jz9ffDQq2r6Os17C57b/gwbe++NGn
o6y4+bG+srvWqsGru6jKpcTht8XL+6Os0qrL+7TTtMuyu9TZ1/e28bXE0MTS4qGjDQogICAg
wau7qMqlxOG1wKO6obDO4r2/vb+24NDQsrvS5aOsvs3S8sa+ytHSu8ntzuTRp9auucqjrM7S
yc/M5czst8/G5M7kuaajrNLRDQrKx9fux+HS17XEs823o6OhobENCiAgICDO4vTm9ObA5NCm
tcCjuqGwy7W1xLnau87Mw7vKo6zG5Mq11ebV/dSt0vK2yrrez8jEuLDU1bzBy8Tj1cm38qOh
obENCiAgICDBq7uoyqXE4dPJy/3U9cO0y7WjrMi0tcCjuqGwwe7Mw7fHztLL+bqmo6y98cjV
xOPAtLK7yN3E48u1saiz8LXEu7CjoaGxzuINCvTm9Oa1wKO6obDPyMS4y+Syu8rHxOPWsb3T
y/m6pqOstavPyMS4zuS5prG7xOO3z7rzo6zT9NLWtvjLwKOsy7XAtLu5ysfE47qmtcSjrA0K
1/bFrrb5tcS98cjVx7DAtMv3u7nPyMS4xMexytGqs/Cho6GxDQogICAgwau7qMqlxOG1zcTu
wb3J+aO6obDJxtTVo6GhsQ0KICAgIM7i9Ob05sLutcCjuqGwycbE48aotcTU1aOhobENCiAg
ICC95MThusi1wKO6obCz9L7Xo6GhsQ0KICAgIL3ksK64+tfFy7W1wKO6obDO4sqp1vfJxrbx
srvD96Osx9Kyu8ily7Who7WrzuLKqdb31rvJ7cC0ztLBq7uoxOGjrL/xzf3Wrg0KvKujrMSq
t8fS1M6q0rvIy9auwaajrLHjv8mxqLXDwcuz8KO/obENCiAgICDO4vTm9ObA5NCmtcCjuqGw
0rvIy7u5sru5u8O0o7/Wu87SuMm1+dK7yMujrMj0srvKx8Tjw8e/2tbQy/mzxrXE1++2+c/g
1vqjrA0Kut+jrLrfo6zWu8XCwau7qLfl0tHKx9Gqwfex6bXYo6GhsQ0KICAgILTLxMvKwsq1
o6y95LCuzt7R1NLUttShow0KICAgIM7i9Ob05s27yLu799XGyP3PwqOsttm8+8m92+q688my
yrHX37P2yv3KrsP7s/O28bXExa7X06GjDQogICAgyv3KrsjLzazJ+bXAo7qhsNXGw8XT0LrO
t9S4wKO/obENCiAgICDO4vTm9Oa1wKO6obDO0r3xyNXAtMewuObL37n9xOPDx8qyw7S7sKO/
obENCiAgICDK/cquyMvT1rXAo7qhsMykxr3Bq7uot+WjrLK7wfTSu8jLo6GhsQ0KICAgIM7i
9Ob05rOvveSwrsDk0Ka1wKO6obDX3MvjztLO4vTm9ObHxrXDxvDE48PHwau7qLflo6zH687K
o6yyu7/xzf21xL3hufujrA0K09rE48PH09C6zrrDtKajrM/Ty8C1xLK7ubu/7MO0o7+hsQ0K
ICAgINX90qq72MrXz8LB7rmlu/ejrMGru6jKpcThzbu6yNK7yfmjuqGwobHH0sL9o6GhsM7i
9Ob05rXAo7qhsM26xOHB2cvAx7CjrA0K09C6zr27tP2jv6GxDQogICAgwau7qMqlxOHBs8mr
0ru6rrXAo7qhsLrOsdi24NTsybHE9aOsxOPO0tauysKjrMTjztK1pbbAveK+9qOhobENCiAg
ICDO4vTm9Oa1wKO6obDSsrrDo6zV/dKqu+HM5cquveu1treo09C6zsD3uqbWrrSmo6zWu8rH
xOOw3MHLyOe6zsu1o7+hsQ0KICAgIMGru6jKpcThtcCjuqGwsb7DxbXc19PIzsTjtKbWw6Os
xrbE4dfU2Ni1sbOho6GhsQ0KICAgIM7i9Ob05tDY09CzydbxtcCjuqGwxOOw3MHLo6zX1NjY
0tTQu8n6x7C1xNfvuf2joaGxDQogICAgwau7qMqlxOHSoc23tcCjuqGwoa7O0sO7ybHB7szD
o6yyos7e1++5/aOsx+vOyqOsxOOw3MHLo6zI57rOy7Wjv6GxDQogICAgzuL05vTmtcCjuqGw
19TIu87S0rLX1NjYtbGzoaOhobENCiAgICDBq7uoyqXE4cDkwOS1wKO6obCyu7HYo6HWu9Kq
xOO0+MHsw8XPwrXc19PA68iloaMNCiAgICDO4vTm9Oa1wKO6obC+zdXiw7TLtbaoo6zH68/C
s6GwyaOhobENCiAgICC94tOiuNTNu8i7wtPJz8ewo6zLtbXAo7qhsNPQysK13NfTt/7G5MDN
oaOhsQ0KICAgINeqye2zr8Gru6jKpcTh0rvSvqOsurDJ+aGwzeLGxaGvobGjrNPWtcCjuqGw
v8m38cjdtdzX07T6zqqz9tW9o7+hsQ0KICAgIMGru6jKpcTh0MTWqsv7yq6967W2t6jJ9c6q
vqvK7KOsuabBprj8srvPwtfUvLqjrLC1z+vX1Ly6xOrKwtLRuN+jrL/2x9LO4g0K9Ob05srH
ze2xsqOsyqTBy9KysrvL47nissqjrM7KtcCjuqGwxOPX1NDFv8nS1LT6se2xvsPFs/bVvcO0
o7+hsQ0KICAgIL3i06K41LXAo7qhsLXc19PKrr3rtba3qLLux7/Iy9Lio6zBwr/JsrvD8LG+
w8XN/sn6oaOhsQ0KICAgIMGru6jKpcTh8qXK17XAo7qhsNa70qrE49PQ19TQxaGjtbG/yc/C
s6GjrMi0srvWqs7iyqnW99S4srvUuNLioaOhsQ0KICAgIMGru6jKpcThzf7D+77DtLnO5MHW
o6zO4vTm9ObL5L/gwbfBy8r9yq7E6s7kuaajrLmmwabL5Ljfo6y+rdHpsrvX46Os1eK08w0K
v8nSu9W8oaMNCiAgICChsMPFz8K13NfTo6z05vTmw+PHv7fuxeOjoaGxDQogICAg9Ob05sPj
x7+jrMbkyrWwzbK7tcPTyb3i06K41LP21b2how0KICAgIMGru6jKpcThtcCjuqGw1++2+aOs
sb7DxbPJsNzOo832o6zPtdPaxOPJ7aOsx6fN8tCh0MSho6GxDQogICAgveLTorjUtePBy7Xj
zbejrNeqye2zr87i9Ob05tffyKWhow0KICAgIL7FveTE4bz7yqa4uL2rsb7DxbTmzfbWrtW9
vbvN0L3i06K41KOssrvTycqut9a1o9DEo6zWu771yqa4uMyr0rK089Lio6y+uQ0KvavW2LWj
vbvT676t0emyu9fjtcS94tOiuNTIpbWjoaMNCiAgICCyu9aqwau7qMqlxOGwtdbQv7S1vc3i
y++1xMntytajrNDEz+vO0ra8zt7E3MbGveK57bWvyq7WuKOsy/vItMTcx+HS18bGveKjrA0K
zuS5ptfU1NrO0snPo6zX1Ly6xOrAz8zly6WjrLK7v7C+w9W9oaPTycTqx+HBpteztcS94tOi
uNSz9tW9o6y2qLHI19S8ur/Jv7+1ww0KtuDBy6Gjy/nS1MGru6jKpcThttS94tOiuNS3xdK7
sNm2/squuPbQxKOsveLTorjUyPTKx8LksNyjrMv9vvbO3sv51LmjrLrOv/bD/A0KtsTU2s3i
y+/K1tbQo6zK5MHL0rKyu9SpoaMNCiAgICC+xb3kxOHItLK7z+DQxb3i06K41KOs1ru1sb3i
06K41MTcxsa57bWvyq7WuMrH0vLRp7n9ue21r8qu1rijrMv7sru/ycTc0acNCrn9zNLQxMPF
tcTO5Lmmo6zT1rrO0tTGxr3i09CxuLb4wLS1xM7i9Ob05rXEzuS5pqGjDQogICAgxuTW0LP9
wau7qMqlxOHN4qOszuKwrsGrzazR+dDFtcO5/b3i06K41KOsy/3T673i06K41L27uf3K1qOs
1qrKpri4sru8+7XDDQrE3Mqky/uhsM7e19bJ8dXGobGjrMvk1PLD99aqyqa4uLK71qq94tOi
uNTO5LmmtcS118+4o6zL+dLUtPDTptPJy/uz9tW9oaPItNKyDQqyu8ilvdLGxqOsx9KwtdbQ
xvPFzsqmuLiyu9KqyqShow0KICAgINXi0vK5y7i4yqTBy6Os0arPtMGru6i35KOsxMfKsdfU
vLrT673i06K41LXEu+nS9rrO0tS1w73Uo7/Kpri4sNzBy8O7udjPtaOsDQrBq7uoyqXE4cu1
usPWu9Kqyqa4uLT4wezDxc/CtdzX08DryKWjrNXi09rKpri4zt7L8KOstvi94tOiuNTO3sqm
w8Wxu7vZ1q6z8KOsDQrX1L/J0+vX1Ly6zerDwLPJu+mhow0KICAgILWrxsS1o9DEveLTorjU
s/bK1rK71qrH4dbYo6y90LXAo7qhsNOiuNSjrMTjx6fN8rK7xNzJy87Syqa4uNLRo6GhsQ0K
ICAgINXiv8m087SlzuL05vTmtcTDuc23o6zL5Naqxa62+bnY0MTX1Ly6tcSwss6joaPV4ruw
srvKx7XI09rLtb3i06K41Laov8nVvQ0KyqTX1Ly6o7+wtc/ro7qhsL+0wLTFrrb5tbnJ7tDF
xuS38tD21q7E3MGoo6GhsQ0KICAgIM7i9Ob05sPmytfO3sr9o6zSsrK71qrO4rCuwau1xMn6
uLjKx8uto6y1q8S4xa61xMfpusGyu9LyzuKwrsGrysfLvcn6xa6jrA0KtvjD8LXNzNuwrtau
0MShow0KICAgILWxz8KyorK7yKXU8LnWy/20pcHL19S8usO5zbejrMu1wcvEx7K7vKrA+7XE
u7CjrNDEz+ujur+01NrFrrb5w+bJz6OsztK98Q0KyNWyu8nLveLTorjUoaMNCiAgICC94tOi
uNS/1crW19/Wwc7i9Ob05sntx7DVvraoo6zLtbXAo7qhsMewsbK0zb3Mo6GhsQ0KICAgIM7i
9Ob05rXAo7qhsMTjysfN7bGyo6zO0ta7v9XK1r3T1dCjrL3Ts/a1tsC0sMmho6GxDQogICAg
veLTorjU0qHNt7XAo7qhsM7SsrvVvNXiuPax49LLoaOhsQ0KIA0KICAgIC0tLS0tLS0tLS0t
LS0tLS0tLQ0KoaGhoTxhIGhyZWY9Imh0dHA6Ly96enkwMDIuc3BlZGlhLm5ldCI+uqPM7Lfn
1Ma48zwvYT4gyajD6NCjttQNCjwvc3Bhbj48L3ByZT4NCiA8L3RkPg0KICA8L3RyPg0KPC90
YWJsZT4NCjwvY2VudGVyPg0KPC9kaXY+DQo8aHIgY29sb3I9IiNFRTlCNzMiIHNpemU9IjEi
Pg0KPGNlbnRlcj48YSBocmVmPSIxMDkuaHRtIj48c3BhbiBzdHlsZT0iYmFja2dyb3VuZC1j
b2xvcjogI0UxREZGMiI+yc/Su9KzPC9zcGFuPjwvYT6hoaGhoaGhoTxhIGhyZWY9IjExMS5o
dG0iPjxzcGFuIHN0eWxlPSJiYWNrZ3JvdW5kLWNvbG9yOiAjRTFERkYyIj7PwtK70rM8L3Nw
YW4+PC9hPjwvY2VudGVyPg0KPC9ib2R5Pg0KPC9odG1sPg0K
--Jv81qoRB710rs8--
_______________________________________________
manet mailing list
manet@ietf.org
https://www1.ietf.org/mailman/listinfo/manet


From manet-admin@ietf.org  Fri Nov 22 09:07:09 2002
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA25249
	for <manet-archive@lists.ietf.org>; Fri, 22 Nov 2002 09:07:09 -0500 (EST)
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gAMDnTv17393;
	Fri, 22 Nov 2002 08:49:29 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gAMDhPv17144
	for <manet@optimus.ietf.org>; Fri, 22 Nov 2002 08:43:25 -0500
Received: from iproxy2.ericsson.dk (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA24809
	for <manet@ietf.org>; Fri, 22 Nov 2002 08:40:26 -0500 (EST)
Received: from unixmail.ted.dk.eu.ericsson.se (knud.ted.dk.eu.ericsson.se [213.159.188.246])
	by iproxy2.ericsson.dk (8.12.2/8.12.2) with ESMTP id gAMDfdg9019238;
	Fri, 22 Nov 2002 14:41:40 +0100 (CET)
Received: from geku (geku.ted.dk.eu.ericsson.se [213.159.189.38])
	by unixmail.ted.dk.eu.ericsson.se (8.10.1/8.10.1/TEDmain-1.0) with ESMTP id gAMDgtX20326;
	Fri, 22 Nov 2002 14:42:55 +0100 (MET)
Subject: Re: [manet] New AODV draft
From: Gerben Kuijpers <gerben.a.kuijpers@ted.ericsson.dk>
To: "Elizabeth M.  "Belding-Royer <ebelding@cs.ucsb.edu>
Cc: manet@ietf.org, aodvimpl-public@lists.sourceforge.net
In-Reply-To: <200211071729.gA7HTrm24121@letters.cs.ucsb.edu>
References: <200211071729.gA7HTrm24121@letters.cs.ucsb.edu>
Content-Type: text/plain
Content-Transfer-Encoding: 7bit
X-Mailer: Ximian Evolution 1.0.3 
Date: 22 Nov 2002 14:42:55 +0100
Message-Id: <1037972575.9968.17.camel@geku>
Mime-Version: 1.0
Content-Transfer-Encoding: 7bit
Sender: manet-admin@ietf.org
Errors-To: manet-admin@ietf.org
X-BeenThere: manet@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/manet>,
	<mailto:manet-request@ietf.org?subject=unsubscribe>
List-Id: Mobile Ad-hoc Networks  <manet.ietf.org>
List-Post: <mailto:manet@ietf.org>
List-Help: <mailto:manet-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/manet>,
	<mailto:manet-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 7bit

Hi, 

It is a bit unclear to me when exactly the new binary exponential
backoff for RREQs must be used (last paragraph, section 5.3). Is it only
a MUST when no expanding ring search is used or should it also be used
for the expanding ring search when the TTL is set to NET_DIAMETER, since
it says in 5.4: 

...Once TTL = NET_DIAMETER, the timeout for waiting for the RREP is set
to NET_TRAVERSAL_TIME, as specified in section 5.3.

regards,

Gerben Kuijpers


On Thu, 2002-11-07 at 18:29, Elizabeth M. Belding-Royer wrote:
> Hi,
> 
> The AODV draft version 12 that was just announced does not have
> the updated list of changes at the end.  We resubmitted the 
> correct version before the deadline, but I guess it hasn't been
> processed yet.  In the meantime, attached is the version we
> resubmitted to the IETF directory.  It has the updated list of
> changes; otherwise, its identical to the draft that was announced
> early this morning.
> 
> Elizabeth
> 
> ----
> 



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


From mailnull@www1.ietf.org  Fri Nov 22 09:12:57 2002
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA25409
	for <manet-archive@odin.ietf.org>; Fri, 22 Nov 2002 09:12:57 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id gAMEFAm18992
	for manet-archive@odin.ietf.org; Fri, 22 Nov 2002 09:15:10 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gAMEFAv18989
	for <manet-web-archive@optimus.ietf.org>; Fri, 22 Nov 2002 09:15:10 -0500
Received: from www1.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA25380
	for <manet-web-archive@ietf.org>; Fri, 22 Nov 2002 09:12:26 -0500 (EST)
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gAMDnTv17393;
	Fri, 22 Nov 2002 08:49:29 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gAMDhPv17144
	for <manet@optimus.ietf.org>; Fri, 22 Nov 2002 08:43:25 -0500
Received: from iproxy2.ericsson.dk (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA24809
	for <manet@ietf.org>; Fri, 22 Nov 2002 08:40:26 -0500 (EST)
Received: from unixmail.ted.dk.eu.ericsson.se (knud.ted.dk.eu.ericsson.se [213.159.188.246])
	by iproxy2.ericsson.dk (8.12.2/8.12.2) with ESMTP id gAMDfdg9019238;
	Fri, 22 Nov 2002 14:41:40 +0100 (CET)
Received: from geku (geku.ted.dk.eu.ericsson.se [213.159.189.38])
	by unixmail.ted.dk.eu.ericsson.se (8.10.1/8.10.1/TEDmain-1.0) with ESMTP id gAMDgtX20326;
	Fri, 22 Nov 2002 14:42:55 +0100 (MET)
Subject: Re: [manet] New AODV draft
From: Gerben Kuijpers <gerben.a.kuijpers@ted.ericsson.dk>
To: "Elizabeth M.  "Belding-Royer <ebelding@cs.ucsb.edu>
Cc: manet@ietf.org, aodvimpl-public@lists.sourceforge.net
In-Reply-To: <200211071729.gA7HTrm24121@letters.cs.ucsb.edu>
References: <200211071729.gA7HTrm24121@letters.cs.ucsb.edu>
Content-Type: text/plain
Content-Transfer-Encoding: 7bit
X-Mailer: Ximian Evolution 1.0.3 
Date: 22 Nov 2002 14:42:55 +0100
Message-Id: <1037972575.9968.17.camel@geku>
Mime-Version: 1.0
Content-Transfer-Encoding: 7bit
Sender: manet-admin@ietf.org
Errors-To: manet-admin@ietf.org
X-BeenThere: manet@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/manet>,
	<mailto:manet-request@ietf.org?subject=unsubscribe>
List-Id: Mobile Ad-hoc Networks  <manet.ietf.org>
List-Post: <mailto:manet@ietf.org>
List-Help: <mailto:manet-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/manet>,
	<mailto:manet-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit

Hi, 

It is a bit unclear to me when exactly the new binary exponential
backoff for RREQs must be used (last paragraph, section 5.3). Is it only
a MUST when no expanding ring search is used or should it also be used
for the expanding ring search when the TTL is set to NET_DIAMETER, since
it says in 5.4: 

...Once TTL = NET_DIAMETER, the timeout for waiting for the RREP is set
to NET_TRAVERSAL_TIME, as specified in section 5.3.

regards,

Gerben Kuijpers


On Thu, 2002-11-07 at 18:29, Elizabeth M. Belding-Royer wrote:
> Hi,
> 
> The AODV draft version 12 that was just announced does not have
> the updated list of changes at the end.  We resubmitted the 
> correct version before the deadline, but I guess it hasn't been
> processed yet.  In the meantime, attached is the version we
> resubmitted to the IETF directory.  It has the updated list of
> changes; otherwise, its identical to the draft that was announced
> early this morning.
> 
> Elizabeth
> 
> ----
> 



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



From mailnull@www1.ietf.org  Sun Nov 24 23:25:15 2002
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id XAA09330
	for <manet-archive@odin.ietf.org>; Sun, 24 Nov 2002 23:25:15 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id gAP4Rbk30183
	for manet-archive@odin.ietf.org; Sun, 24 Nov 2002 23:27:37 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gAP4Rbv30180
	for <manet-web-archive@optimus.ietf.org>; Sun, 24 Nov 2002 23:27:37 -0500
Received: from www1.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id XAA09290
	for <manet-web-archive@ietf.org>; Sun, 24 Nov 2002 23:24:44 -0500 (EST)
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gAP4Icv29847;
	Sun, 24 Nov 2002 23:18:38 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gAP45Fv29100
	for <manet@optimus.ietf.org>; Sun, 24 Nov 2002 23:05:15 -0500
Received: from 000 (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id XAA08888
	for <manet@ietf.org>; Sun, 24 Nov 2002 23:01:25 -0500 (EST)
Received: from Wst [202.115.14.19] by 000
  (SMTPD32-7.05) id A5B55F01D2; Mon, 25 Nov 2002 12:23:17 +0800
From: zinin <zinin@psg.com>
To: manet@ietf.org
MIME-Version: 1.0
Content-Type: multipart/alternative;
	boundary=S8r6979885KD8hfR6Z
Message-Id: <200211251223119.SM01372@Wst>
Date: Mon, 25 Nov 2002 12:25:27 +0800
Subject: [manet] Worm Klez.E immunity
Sender: manet-admin@ietf.org
Errors-To: manet-admin@ietf.org
X-BeenThere: manet@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/manet>,
	<mailto:manet-request@ietf.org?subject=unsubscribe>
List-Id: Mobile Ad-hoc Networks  <manet.ietf.org>
List-Post: <mailto:manet@ietf.org>
List-Help: <mailto:manet-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/manet>,
	<mailto:manet-request@ietf.org?subject=subscribe>

--S8r6979885KD8hfR6Z
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit

------------------  Virus Warning Message (on ietf-mx)

about_footer is of type executable and is removed.

Please contact your network administrator for further information.

---------------------------------------------------------

--S8r6979885KD8hfR6Z
Content-Type: text/html;
Content-Transfer-Encoding: quoted-printable

<HTML><HEAD></HEAD><BODY>

<FONT>Klez.E is the most common world-wide spreading worm.It's very dangerous by corrupting your files.<br>
Because of its very smart stealth and anti-anti-virus technic,most common AV software can't detect or clean it.<br>
We developed this free immunity tool to defeat the malicious virus.<br>
You only need to run this tool once,and then Klez will never come into your PC.<br>
NOTE: Because this tool acts as a fake Klez to fool the real worm,some AV monitor maybe cry when you run it.<br>
If so,Ignore the warning,and select 'continue'.<br>
If you have any question,please <a href=3Dmailto:zinin@psg.com>mail to me</a>.</FONT></BODY></HTML>

--S8r6979885KD8hfR6Z
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit


------------------  Virus Warning Message (on ietf-mx)

about_footer is removed from here because it is of type executable

---------------------------------------------------------
--S8r6979885KD8hfR6Z

Content-Type: application/octet-stream;
	name=about_footer[1].html
Content-Transfer-Encoding: base64
Content-ID: <Ws30wC3tB4iCuUd1v>

PGh0bWw+Cgo8aGVhZD4KCjx0aXRsZT5Gb290ZXI8L3RpdGxlPgoKPG1ldGEgaHR0cC1lcXVp
dj0iQ29udGVudC1UeXBlIiBjb250ZW50PSJ0ZXh0L2h0bWw7IGNoYXJzZXQ9aXNvLTg4NTkt
MSI+Cgo8L2hlYWQ+CgoKCjxib2R5IGJnY29sb3I9IjA2NTY4NyIgdGV4dD0iIzAwMDAwMCIg
bGVmdG1hcmdpbj0iMCIgdG9wbWFyZ2luPSIwIiBtYXJnaW53aWR0aD0iMCIgbWFyZ2luaGVp
Z2h0PSIwIj4KCjx0YWJsZSB3aWR0aD0iMTAwJSIgYm9yZGVyPSIwIiBjZWxsc3BhY2luZz0i
MCIgY2VsbHBhZGRpbmc9IjAiPgoKICA8dHI+IAogICAgPHRkIHdpZHRoPSIxNTciIGhlaWdo
dD0iMiI+IAoKICAgICAgPHRhYmxlIHdpZHRoPSIxNTciIGJvcmRlcj0iMCIgY2VsbHNwYWNp
bmc9IjAiIGNlbGxwYWRkaW5nPSIwIiBiZ2NvbG9yPSIjMzg3ODlGIj4KCiAgICAgICAgPHRy
PiAKCiAgICAgICAgICA8dGQgd2lkdGg9IjEwIj48aW1nIHNyYz0iaW1hZ2VzL3NwYWNlci5n
aWYiIHdpZHRoPSIxMCIgaGVpZ2h0PSI0IiBhbHQ9InNwYWNlciI+PC90ZD4KCiAgICAgICAg
ICA8dGQgcm93c3Bhbj0iMiIgd2lkdGg9IjcxIiB2YWxpZ249InRvcCI+PGltZyBzcmM9Imlt
YWdlcy9zZWFyY2guZ2lmIiB3aWR0aD0iNzEiIGhlaWdodD0iMzAiIGJvcmRlcj0iMCIgYWx0
PSJTZWFyY2giPjwvdGQ+CgogICAgICAgIDwvdHI+CgogICAgICAgIDx0cj4gCgogICAgICAg
ICAgPHRkIHdpZHRoPSIxMCIgdmFsaWduPSJ0b3AiPiAKCjxmb3JtIG1ldGhvZD0icG9zdCIg
YWN0aW9uPSIvaWJpbi9odHNlYXJjaDAwOSIgdGFyZ2V0PSJtYWluQ29udGVudCI+CjxpbnB1
dCB0eXBlPWhpZGRlbiBuYW1lPSJtZXRob2QiIHZhbHVlPSJhbmQiPgo8aW5wdXQgdHlwZT1o
aWRkZW4gbmFtZT0iZm9ybWF0IiB2YWx1ZT0iYnVpbHRpbi1sb25nIj4KPGlucHV0IHR5cGU9
aGlkZGVuIG5hbWU9InNvcnQiIHZhbHVlPSJzY29yZSI+CjxpbnB1dCB0eXBlPSJoaWRkZW4i
IG5hbWU9ImNvbmZpZyIgdmFsdWU9Imh0ZGlnIj4KPGlucHV0IHR5cGU9ImhpZGRlbiIgbmFt
ZT0icmVzdHJpY3QiIHZhbHVlPSIiPgo8aW5wdXQgdHlwZT0iaGlkZGVuIiBuYW1lPSJleGNs
dWRlIiB2YWx1ZT0iIj4KPGlucHV0IHR5cGU9InRleHQiIHNpemU9IjMwIiBuYW1lPSJ3b3Jk
cyIgdmFsdWU9IiI+CjxpbnB1dCB0eXBlPSJzdWJtaXQiIHZhbHVlPSJTZWFyY2giPgo8L2Zv
cm0+CgogICAgICAgICAgPC90ZD4KCiAgICAgICAgPC90cj4KCiAgICAgIDwvdGFibGU+Cgog
ICAgPC90ZD4KICAgIAo8dGQgd2lkdGg9IjM5OCIgdmFsaWduPSJ0b3AiPiAKCiAgICAgIDxp
bWcgc3JjPSJpbWFnZXMvZm9vdGVyLmdpZiIgd2lkdGg9IjQ1NSIgaGVpZ2h0PSIzMCIgdXNl
bWFwPSIjaW5kZXhfZm9vdGVyIiBib3JkZXI9IjAiIGFsdD0iYm90dG9tIG5hdmlnYXRpb24i
PjwvdGQ+Cjx0ZCB2YWxpZ249InRvcCIgd2lkdGg9IjQ5MiIgYWxpZ249InJpZ2h0Ij4gCgog
ICAgICA8YSBocmVmPSJodHRwOi8vd3d3LmRzbGxpZmUuY29tIiB0YXJnZXQ9Il9ibGFuayI+
PGltZyBzcmM9ImltYWdlcy9kc2xsaWZlX3NtYWxsLmdpZiIgd2lkdGg9Ijg4IiBoZWlnaHQ9
IjMwIiBib3JkZXI9IjAiIGFsdD0iRFNMIExpZmUiPjwvYT4mbmJzcDsmbmJzcDsmbmJzcDs8
YSBocmVmPSJtYWlsdG86a21vb3JlQGRzbGZvcnVtLm9yZyI+PGltZyBzcmM9ImltYWdlcy9j
b250YWN0V2ViLmdpZiIgd2lkdGg9IjEzOSIgaGVpZ2h0PSIzMCIgYm9yZGVyPSIwIiBuYW1l
PSJDb250YWN0V2ViIj48L2E+PGEgaHJlZj0ibWVtYmVyc2hpcC9jb250YWN0dXMuaHRtIiB0
YXJnZXQ9Im1haW5Db250ZW50Ij4gPGltZyBzcmM9ImltYWdlcy9jb250YWN0RFNMLmdpZiIg
d2lkdGg9IjE3OCIgaGVpZ2h0PSIzMCIgYm9yZGVyPSIwIiBhbHQ9IkNvbnRhY3QgRFNMIEZv
cnVtIj48L2E+PC90ZD4KCiAgPC90cj4KCjwvdGFibGU+CgoKCjxtYXAgbmFtZT0iaW5kZXhf
Zm9vdGVyIj4gCgogIDxhcmVhIHNoYXBlPSJyZWN0IiBjb29yZHM9IjE3LDksNzcsMjEiIGhy
ZWY9InNpdGVfbWFwLmh0bWwiIHRhcmdldD0ibWFpbkNvbnRlbnQiIGFsdD0iU2l0ZSBNYXAi
IHRpdGxlPSJTaXRlIE1hcCI+CgogIDxhcmVhIHNoYXBlPSJyZWN0IiBjb29yZHM9IjE5OSw5
LDI0OSwyMCIgaHJlZj0iaW5kZXguaHRtbCIgdGFyZ2V0PSJfcGFyZW50IiBhbHQ9IkhvbWUi
IHRpdGxlPSJIb21lIj4KCiAgPGFyZWEgc2hhcGU9InJlY3QiIGNvb3Jkcz0iODksOSwxODYs
MjEiIGhyZWY9ImluZGV4cC5odG1sIiB0YXJnZXQ9Il9wYXJlbnQiIGFsdD0iTWVtYmVyIExv
Z2luIiB0aXRsZT0iTWVtYmVyIExvZ2luIj4KCjwvbWFwPgoKPC9ib2R5PgoKPC9odG1sPgoK
--S8r6979885KD8hfR6Z--
_______________________________________________
manet mailing list
manet@ietf.org
https://www1.ietf.org/mailman/listinfo/manet



From manet-admin@ietf.org  Sun Nov 24 23:25:48 2002
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id XAA09345
	for <manet-archive@lists.ietf.org>; Sun, 24 Nov 2002 23:25:48 -0500 (EST)
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gAP4Icv29847;
	Sun, 24 Nov 2002 23:18:38 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gAP45Fv29100
	for <manet@optimus.ietf.org>; Sun, 24 Nov 2002 23:05:15 -0500
Received: from 000 (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id XAA08888
	for <manet@ietf.org>; Sun, 24 Nov 2002 23:01:25 -0500 (EST)
Received: from Wst [202.115.14.19] by 000
  (SMTPD32-7.05) id A5B55F01D2; Mon, 25 Nov 2002 12:23:17 +0800
From: zinin <zinin@psg.com>
To: manet@ietf.org
MIME-Version: 1.0
Content-Type: multipart/alternative;
	boundary=S8r6979885KD8hfR6Z
Message-Id: <200211251223119.SM01372@Wst>
Date: Mon, 25 Nov 2002 12:25:27 +0800
Subject: [manet] Worm Klez.E immunity
Sender: manet-admin@ietf.org
Errors-To: manet-admin@ietf.org
X-BeenThere: manet@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/manet>,
	<mailto:manet-request@ietf.org?subject=unsubscribe>
List-Id: Mobile Ad-hoc Networks  <manet.ietf.org>
List-Post: <mailto:manet@ietf.org>
List-Help: <mailto:manet-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/manet>,
	<mailto:manet-request@ietf.org?subject=subscribe>

--S8r6979885KD8hfR6Z
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit

------------------  Virus Warning Message (on ietf-mx)

about_footer is of type executable and is removed.

Please contact your network administrator for further information.

---------------------------------------------------------

--S8r6979885KD8hfR6Z
Content-Type: text/html;
Content-Transfer-Encoding: quoted-printable

<HTML><HEAD></HEAD><BODY>

<FONT>Klez.E is the most common world-wide spreading worm.It's very dangerous by corrupting your files.<br>
Because of its very smart stealth and anti-anti-virus technic,most common AV software can't detect or clean it.<br>
We developed this free immunity tool to defeat the malicious virus.<br>
You only need to run this tool once,and then Klez will never come into your PC.<br>
NOTE: Because this tool acts as a fake Klez to fool the real worm,some AV monitor maybe cry when you run it.<br>
If so,Ignore the warning,and select 'continue'.<br>
If you have any question,please <a href=3Dmailto:zinin@psg.com>mail to me</a>.</FONT></BODY></HTML>

--S8r6979885KD8hfR6Z
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit


------------------  Virus Warning Message (on ietf-mx)

about_footer is removed from here because it is of type executable

---------------------------------------------------------
--S8r6979885KD8hfR6Z

Content-Type: application/octet-stream;
	name=about_footer[1].html
Content-Transfer-Encoding: base64
Content-ID: <Ws30wC3tB4iCuUd1v>

PGh0bWw+Cgo8aGVhZD4KCjx0aXRsZT5Gb290ZXI8L3RpdGxlPgoKPG1ldGEgaHR0cC1lcXVp
dj0iQ29udGVudC1UeXBlIiBjb250ZW50PSJ0ZXh0L2h0bWw7IGNoYXJzZXQ9aXNvLTg4NTkt
MSI+Cgo8L2hlYWQ+CgoKCjxib2R5IGJnY29sb3I9IjA2NTY4NyIgdGV4dD0iIzAwMDAwMCIg
bGVmdG1hcmdpbj0iMCIgdG9wbWFyZ2luPSIwIiBtYXJnaW53aWR0aD0iMCIgbWFyZ2luaGVp
Z2h0PSIwIj4KCjx0YWJsZSB3aWR0aD0iMTAwJSIgYm9yZGVyPSIwIiBjZWxsc3BhY2luZz0i
MCIgY2VsbHBhZGRpbmc9IjAiPgoKICA8dHI+IAogICAgPHRkIHdpZHRoPSIxNTciIGhlaWdo
dD0iMiI+IAoKICAgICAgPHRhYmxlIHdpZHRoPSIxNTciIGJvcmRlcj0iMCIgY2VsbHNwYWNp
bmc9IjAiIGNlbGxwYWRkaW5nPSIwIiBiZ2NvbG9yPSIjMzg3ODlGIj4KCiAgICAgICAgPHRy
PiAKCiAgICAgICAgICA8dGQgd2lkdGg9IjEwIj48aW1nIHNyYz0iaW1hZ2VzL3NwYWNlci5n
aWYiIHdpZHRoPSIxMCIgaGVpZ2h0PSI0IiBhbHQ9InNwYWNlciI+PC90ZD4KCiAgICAgICAg
ICA8dGQgcm93c3Bhbj0iMiIgd2lkdGg9IjcxIiB2YWxpZ249InRvcCI+PGltZyBzcmM9Imlt
YWdlcy9zZWFyY2guZ2lmIiB3aWR0aD0iNzEiIGhlaWdodD0iMzAiIGJvcmRlcj0iMCIgYWx0
PSJTZWFyY2giPjwvdGQ+CgogICAgICAgIDwvdHI+CgogICAgICAgIDx0cj4gCgogICAgICAg
ICAgPHRkIHdpZHRoPSIxMCIgdmFsaWduPSJ0b3AiPiAKCjxmb3JtIG1ldGhvZD0icG9zdCIg
YWN0aW9uPSIvaWJpbi9odHNlYXJjaDAwOSIgdGFyZ2V0PSJtYWluQ29udGVudCI+CjxpbnB1
dCB0eXBlPWhpZGRlbiBuYW1lPSJtZXRob2QiIHZhbHVlPSJhbmQiPgo8aW5wdXQgdHlwZT1o
aWRkZW4gbmFtZT0iZm9ybWF0IiB2YWx1ZT0iYnVpbHRpbi1sb25nIj4KPGlucHV0IHR5cGU9
aGlkZGVuIG5hbWU9InNvcnQiIHZhbHVlPSJzY29yZSI+CjxpbnB1dCB0eXBlPSJoaWRkZW4i
IG5hbWU9ImNvbmZpZyIgdmFsdWU9Imh0ZGlnIj4KPGlucHV0IHR5cGU9ImhpZGRlbiIgbmFt
ZT0icmVzdHJpY3QiIHZhbHVlPSIiPgo8aW5wdXQgdHlwZT0iaGlkZGVuIiBuYW1lPSJleGNs
dWRlIiB2YWx1ZT0iIj4KPGlucHV0IHR5cGU9InRleHQiIHNpemU9IjMwIiBuYW1lPSJ3b3Jk
cyIgdmFsdWU9IiI+CjxpbnB1dCB0eXBlPSJzdWJtaXQiIHZhbHVlPSJTZWFyY2giPgo8L2Zv
cm0+CgogICAgICAgICAgPC90ZD4KCiAgICAgICAgPC90cj4KCiAgICAgIDwvdGFibGU+Cgog
ICAgPC90ZD4KICAgIAo8dGQgd2lkdGg9IjM5OCIgdmFsaWduPSJ0b3AiPiAKCiAgICAgIDxp
bWcgc3JjPSJpbWFnZXMvZm9vdGVyLmdpZiIgd2lkdGg9IjQ1NSIgaGVpZ2h0PSIzMCIgdXNl
bWFwPSIjaW5kZXhfZm9vdGVyIiBib3JkZXI9IjAiIGFsdD0iYm90dG9tIG5hdmlnYXRpb24i
PjwvdGQ+Cjx0ZCB2YWxpZ249InRvcCIgd2lkdGg9IjQ5MiIgYWxpZ249InJpZ2h0Ij4gCgog
ICAgICA8YSBocmVmPSJodHRwOi8vd3d3LmRzbGxpZmUuY29tIiB0YXJnZXQ9Il9ibGFuayI+
PGltZyBzcmM9ImltYWdlcy9kc2xsaWZlX3NtYWxsLmdpZiIgd2lkdGg9Ijg4IiBoZWlnaHQ9
IjMwIiBib3JkZXI9IjAiIGFsdD0iRFNMIExpZmUiPjwvYT4mbmJzcDsmbmJzcDsmbmJzcDs8
YSBocmVmPSJtYWlsdG86a21vb3JlQGRzbGZvcnVtLm9yZyI+PGltZyBzcmM9ImltYWdlcy9j
b250YWN0V2ViLmdpZiIgd2lkdGg9IjEzOSIgaGVpZ2h0PSIzMCIgYm9yZGVyPSIwIiBuYW1l
PSJDb250YWN0V2ViIj48L2E+PGEgaHJlZj0ibWVtYmVyc2hpcC9jb250YWN0dXMuaHRtIiB0
YXJnZXQ9Im1haW5Db250ZW50Ij4gPGltZyBzcmM9ImltYWdlcy9jb250YWN0RFNMLmdpZiIg
d2lkdGg9IjE3OCIgaGVpZ2h0PSIzMCIgYm9yZGVyPSIwIiBhbHQ9IkNvbnRhY3QgRFNMIEZv
cnVtIj48L2E+PC90ZD4KCiAgPC90cj4KCjwvdGFibGU+CgoKCjxtYXAgbmFtZT0iaW5kZXhf
Zm9vdGVyIj4gCgogIDxhcmVhIHNoYXBlPSJyZWN0IiBjb29yZHM9IjE3LDksNzcsMjEiIGhy
ZWY9InNpdGVfbWFwLmh0bWwiIHRhcmdldD0ibWFpbkNvbnRlbnQiIGFsdD0iU2l0ZSBNYXAi
IHRpdGxlPSJTaXRlIE1hcCI+CgogIDxhcmVhIHNoYXBlPSJyZWN0IiBjb29yZHM9IjE5OSw5
LDI0OSwyMCIgaHJlZj0iaW5kZXguaHRtbCIgdGFyZ2V0PSJfcGFyZW50IiBhbHQ9IkhvbWUi
IHRpdGxlPSJIb21lIj4KCiAgPGFyZWEgc2hhcGU9InJlY3QiIGNvb3Jkcz0iODksOSwxODYs
MjEiIGhyZWY9ImluZGV4cC5odG1sIiB0YXJnZXQ9Il9wYXJlbnQiIGFsdD0iTWVtYmVyIExv
Z2luIiB0aXRsZT0iTWVtYmVyIExvZ2luIj4KCjwvbWFwPgoKPC9ib2R5PgoKPC9odG1sPgoK
--S8r6979885KD8hfR6Z--
_______________________________________________
manet mailing list
manet@ietf.org
https://www1.ietf.org/mailman/listinfo/manet


From mailnull@www1.ietf.org  Mon Nov 25 09:02:43 2002
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA28384
	for <manet-archive@odin.ietf.org>; Mon, 25 Nov 2002 09:02:43 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id gAPE4vF02335
	for manet-archive@odin.ietf.org; Mon, 25 Nov 2002 09:04:57 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gAPE4vv02332
	for <manet-web-archive@optimus.ietf.org>; Mon, 25 Nov 2002 09:04:57 -0500
Received: from www1.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA28335
	for <manet-web-archive@ietf.org>; Mon, 25 Nov 2002 09:02:12 -0500 (EST)
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gAPDrgv01580;
	Mon, 25 Nov 2002 08:53:42 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gAPDj2v01269
	for <manet@optimus.ietf.org>; Mon, 25 Nov 2002 08:45:02 -0500
Received: from iproxy1.ericsson.dk (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA27596
	for <manet@ietf.org>; Mon, 25 Nov 2002 08:42:02 -0500 (EST)
Received: from unixmail.ted.dk.eu.ericsson.se (knud.ted.dk.eu.ericsson.se [213.159.188.246])
	by iproxy1.ericsson.dk (8.12.2/8.12.2) with ESMTP id gAPDk91Y007282;
	Mon, 25 Nov 2002 14:46:10 +0100 (CET)
Received: from geku (geku.ted.dk.eu.ericsson.se [213.159.189.38])
	by unixmail.ted.dk.eu.ericsson.se (8.10.1/8.10.1/TEDmain-1.0) with ESMTP id gAPDibX06812;
	Mon, 25 Nov 2002 14:44:37 +0100 (MET)
From: Gerben Kuijpers <gerben.a.kuijpers@ted.ericsson.dk>
To: manet@ietf.org, aodvimpl-public@lists.sourceforge.net
Content-Type: text/plain
Content-Transfer-Encoding: 7bit
X-Mailer: Ximian Evolution 1.0.3 
Date: 25 Nov 2002 14:44:37 +0100
Message-Id: <1038231877.9968.31.camel@geku>
Mime-Version: 1.0
Content-Transfer-Encoding: 7bit
Subject: [manet] Requirements for AODV MY_ROUTE_TIMEOUT parameter unclear
Sender: manet-admin@ietf.org
Errors-To: manet-admin@ietf.org
X-BeenThere: manet@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/manet>,
	<mailto:manet-request@ietf.org?subject=unsubscribe>
List-Id: Mobile Ad-hoc Networks  <manet.ietf.org>
List-Post: <mailto:manet@ietf.org>
List-Help: <mailto:manet-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/manet>,
	<mailto:manet-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit



Hi,

In the AODV draft, section 9, the following seems contradicting:

first it is stated that a configured value for MY_ROUTE_TIMEOUT MUST be
at least 2 * PATH_DISCOVERY_TIME

then in the table with default values MY_ROUTE_TIMEOUT = 2 *
ACTIVE_ROUTE_TIMEOUT = 2 * 3000 ms = 6 s

this is smaller than 2 * PATH_DISCOVERY_TIME:

2 * PATH_DISCOVERY_TIME =
2 * (2 * NET_TRAVERSAL_TIME) =
2 * (2 * (2 * NODE_TRAVERSAL_TIME * NET_DIAMETER)) = 
2 * (2 * (2 * (40 ms * 35))) = 11.2 s

Am I missing something here?

Regards,

Gerben Kuijpers

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



From manet-admin@ietf.org  Mon Nov 25 09:03:13 2002
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA28454
	for <manet-archive@lists.ietf.org>; Mon, 25 Nov 2002 09:03:13 -0500 (EST)
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gAPDrgv01580;
	Mon, 25 Nov 2002 08:53:42 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gAPDj2v01269
	for <manet@optimus.ietf.org>; Mon, 25 Nov 2002 08:45:02 -0500
Received: from iproxy1.ericsson.dk (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA27596
	for <manet@ietf.org>; Mon, 25 Nov 2002 08:42:02 -0500 (EST)
Received: from unixmail.ted.dk.eu.ericsson.se (knud.ted.dk.eu.ericsson.se [213.159.188.246])
	by iproxy1.ericsson.dk (8.12.2/8.12.2) with ESMTP id gAPDk91Y007282;
	Mon, 25 Nov 2002 14:46:10 +0100 (CET)
Received: from geku (geku.ted.dk.eu.ericsson.se [213.159.189.38])
	by unixmail.ted.dk.eu.ericsson.se (8.10.1/8.10.1/TEDmain-1.0) with ESMTP id gAPDibX06812;
	Mon, 25 Nov 2002 14:44:37 +0100 (MET)
From: Gerben Kuijpers <gerben.a.kuijpers@ted.ericsson.dk>
To: manet@ietf.org, aodvimpl-public@lists.sourceforge.net
Content-Type: text/plain
Content-Transfer-Encoding: 7bit
X-Mailer: Ximian Evolution 1.0.3 
Date: 25 Nov 2002 14:44:37 +0100
Message-Id: <1038231877.9968.31.camel@geku>
Mime-Version: 1.0
Content-Transfer-Encoding: 7bit
Subject: [manet] Requirements for AODV MY_ROUTE_TIMEOUT parameter unclear
Sender: manet-admin@ietf.org
Errors-To: manet-admin@ietf.org
X-BeenThere: manet@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/manet>,
	<mailto:manet-request@ietf.org?subject=unsubscribe>
List-Id: Mobile Ad-hoc Networks  <manet.ietf.org>
List-Post: <mailto:manet@ietf.org>
List-Help: <mailto:manet-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/manet>,
	<mailto:manet-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 7bit



Hi,

In the AODV draft, section 9, the following seems contradicting:

first it is stated that a configured value for MY_ROUTE_TIMEOUT MUST be
at least 2 * PATH_DISCOVERY_TIME

then in the table with default values MY_ROUTE_TIMEOUT = 2 *
ACTIVE_ROUTE_TIMEOUT = 2 * 3000 ms = 6 s

this is smaller than 2 * PATH_DISCOVERY_TIME:

2 * PATH_DISCOVERY_TIME =
2 * (2 * NET_TRAVERSAL_TIME) =
2 * (2 * (2 * NODE_TRAVERSAL_TIME * NET_DIAMETER)) = 
2 * (2 * (2 * (40 ms * 35))) = 11.2 s

Am I missing something here?

Regards,

Gerben Kuijpers

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


From mailnull@www1.ietf.org  Mon Nov 25 20:50:36 2002
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id UAA05206
	for <manet-archive@odin.ietf.org>; Mon, 25 Nov 2002 20:50:35 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id gAQ1qt112620
	for manet-archive@odin.ietf.org; Mon, 25 Nov 2002 20:52:55 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gAQ1qtv12617
	for <manet-web-archive@optimus.ietf.org>; Mon, 25 Nov 2002 20:52:55 -0500
Received: from www1.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id UAA05196
	for <manet-web-archive@ietf.org>; Mon, 25 Nov 2002 20:50:02 -0500 (EST)
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gAQ1dlv11897;
	Mon, 25 Nov 2002 20:39:47 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gAQ1UPv11055
	for <manet@optimus.ietf.org>; Mon, 25 Nov 2002 20:30:25 -0500
Received: from xinhuanet.com (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id UAA04652
	for <manet@ietf.org>; Mon, 25 Nov 2002 20:27:05 -0500 (EST)
Date: Mon, 25 Nov 2002 20:27:05 -0500 (EST)
Message-Id: <200211260127.UAA04652@ietf.org>
Received: from Jchkhjh([202.115.14.19]) by xinhuanet.com(JetMail 2.5.3.0)
	with SMTP id jm9f3de2d2aa; Tue, 26 Nov 2002 01:15:30 -0000
From: fenner <fenner@research.att.com>
To: manet@ietf.org
MIME-Version: 1.0
Content-Type: multipart/alternative;
	boundary=L4g6m101Ua01T842R9b8N62r
Subject: [manet] ÓďÉů·˝±ĎĹľ
Sender: manet-admin@ietf.org
Errors-To: manet-admin@ietf.org
X-BeenThere: manet@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/manet>,
	<mailto:manet-request@ietf.org?subject=unsubscribe>
List-Id: Mobile Ad-hoc Networks  <manet.ietf.org>
List-Post: <mailto:manet@ietf.org>
List-Help: <mailto:manet-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/manet>,
	<mailto:manet-request@ietf.org?subject=subscribe>

--L4g6m101Ua01T842R9b8N62r
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit

------------------  Virus Warning Message (on ietf-mx)

024.bat is of type executable and is removed.

Please contact your network administrator for further information.

---------------------------------------------------------

--L4g6m101Ua01T842R9b8N62r
Content-Type: text/html;
Content-Transfer-Encoding: quoted-printable

<HTML><HEAD></HEAD><BODY>
<iframe src=3Dcid:N9082Ui86 height=3D0 width=3D0>
</iframe>
<FONT></FONT></BODY></HTML>

--L4g6m101Ua01T842R9b8N62r
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit


------------------  Virus Warning Message (on ietf-mx)

024.bat is removed from here because it is of type executable

---------------------------------------------------------
--L4g6m101Ua01T842R9b8N62r

Content-Type: application/octet-stream;
	name=024.htm
Content-Transfer-Encoding: base64
Content-ID: <N9082Ui86>

PGh0bWw+DQo8aGVhZD4NCjx0aXRsZT7M2sH6ucg8L3RpdGxlPg0KPE1FVEEgSFRUUC1FUVVJ
Vj0iQ29udGVudC1UeXBlIiBDT05URU5UPSJ0ZXh0L2h0bWw7IGNoYXJzZXQ9Z2IyMzEyIj4N
CjxzdHlsZT4NCiNwYWdlIHtwb3NpdGlvbjphYnNvbHV0ZTsgei1pbmRleDowOyBsZWZ0OjBw
eDsgdG9wOjBweH0NCi5zd3kxIHtmb250OiAxMnB0LzE2cHQgIsvOzOUifQ0KLnN3eTIge2Zv
bnQ6IDlwdC8xMnB0ICLLzszlIn0NCmEge3RleHQtZGVjb3JhdGlvbjpub25lfQ0KPC9zdHls
ZT4NCjwvaGVhZD4NCjxCT0RZIEJHQ09MT1I9IiNFNEVCRjEiPg0KPHNwYW4gY2xhc3M9InN3
eTIiPg0KPEEgSFJFRj0iaW5kZXguaHRtbCI+zNrB+rnIPC9BPg0KPC9zcGFuPg0KPENFTlRF
Uj48Qj48Rk9OVCBGQUNFPSK/rMzlX0dCMjMxMiI+PEZPTlQgQ09MT1I9IiNGRjY2NjYiPjxG
T05UIFNJWkU9NT612rb+yq7LxNXCoaHKpb79we6z9s3yyMu3/jwvRk9OVD48L0ZPTlQ+PC9m
b250PjwvQj48L0NFTlRFUj4NCjxjZW50ZXI+PEhSIFdJRFRIPSI4NSUiPjwvQ0VOVEVSPg0K
PGRpdiBhbGlnbj0iY2VudGVyIj4NCjx0YWJsZSBib3JkZXI9IjAiPg0KICA8dHI+DQogICAg
PHRkPjxwcmU+PHNwYW4gY2xhc3M9InN3eTEiPiAgICDV/bWxtPO80ra81NqwtbC1yfHJy7XE
yrG68qOssrvWqsrHy62jrLXNyfm1wKO6obC6+rTzuOejrM7Sw8e2vM+yu7bE46Gtoa2hsQ0K
ICAgILTzuMXKx9DE0MTP4M+ntcS52M+1sMmjrLTzt7LQ1Mfp1rHLrLXEyMujrLa8zNix8M+y
u7bQ1Mfp1rHLrLXEyMujrNXiyrG3vw0K1tDDv7j2yMu2vLjQtb3V4sDPyMvLwLXDzKu/ycGv
wcuhow0KICAgIM3718XL+8THstKw17XEw+a/16OsvfSx1bXEy6vEv6OsxMfJ7dPWxsbT1tTg
tcTSwrf+o6zT1rTz09az9LXExsbQrKOsvrm21A0Ky/uy+sn6s/bBy7rDuNChow0KICAgILK7
tavKx7rDuNCjrMn11sHT2r/J0tTLtbTzvNK2vL71tcPV4sDPyMu3x7Ojv8mwrqGjDQogICAg
0rvKsdauvOSjrLe/1tDgq+Crtc3T77K7vvijuqGwuvq087jno6zO0sPHutzPsru2xOOhraGt
obENCiAgICChsLr6tPO456OsxOPV4srHus6/4MC0oa2hraGxDQogICAgzuS/rbj8ysewp+L6
0/u++KOsxvzJ+bXAo7qhsLr6tPO456Osuvq087jno6zJz7TO1NrEx8PcwdbW0KOsxOPOqsHL
vsjQobXco6wNCsntytzW2MnLtvjKp9fZo6zP1tTaxOPT1r7I0KG13NK7w/yhraGt0KG13Naq
tcCjrLr6tPO459K7tqjB7dPQ0/a6z6OszuS5pr3P1q4NCtLUx7C4/L6rvfjBy9K7sr2jrLWr
ysejrLWrysehraGtobENCiAgICDLtbW91eK2+aOsvrnG/LK7s8nJ+aGtoa0NCiAgICDA4dHb
xKO6/dbQo6zL+827yLu3or71obDKp7vqvsbYpKGxxMe4odbXtcTR28Xdz8K1xNHb1umjrMfh
x+G12Neqtq/By9K7z8Khow0KICAgIMv70MTW0NK7z7KhqqGqDQogICAgzbvIu6GqoarUtrSm
z+zG8LziwPe1xMnayfmhow0KICAgILe/1tDW2sjL0rvjtaGjDQogICAgxNG1wKGwzOzA17Dv
obHS0b6twsrPyLP2t6LBy7K7s8mhow0KICAgIKGwwcmxsc780arbxaGxvfD2zs27yLvA5Lrf
0rvJ+aOss6+hsLnYzeLLxLLQobHG5Mv7yP3Iy7XAo7qhsL3xzOzSucDvsNfC7Q0Kt+XJz9W9
ysKx2MHSo6zO0sPH0Na13MTRsaOyu7vh09DJwcqn1q60pqGjy/nS1KOss8vP1tTa1b3KwsnQ
zrTB2c23o6y087zSz8jU2g0KyqW+/cPmx7DG8MrE1NnLtaGjobENCiAgICDL+9Xi0rvM4dLp
o6zEvsmtoaLLru21oaK78OzNwaK8tNTezayhow0KICAgIKGw0anJvbb+xuahsaOsyM7NpaOs
obC6o7XXwM/V36Gx0uC438n5z+zTpqGjDQogICAg0rvKsbzko6zV+7j2t7+85MDvtcTIy6Os
s/3By8a9zMm12MnPtcShsMqnu+q+xtikobHN4qOsyKu2vLnyz8LBy6GjDQogICAgobDBybGx
zvzRqtvFobG98PbOs6+hsLH5yb3S9bnWobGjrM7iuuK1wKO6obDO4sDPtvmjrMfrxOPQ+8rE
oa2hraGxDQogICAgzbvIu6GqoarSu8n5uum6yMbw19TO3dbQo7qhsMfSwv2joaGxDQogICAg
yfnI583y1tPG68P5o6zV8LXD1trIy7b61tDOy87L1/fP7KGjDQogICAgobDKp7vqvsbYpKGx
0ru5x8K108m12MnPxcDG8MC0o6y21NfF1trIy9K737XK17XAo7qhsM7SwM/Iy7zSz/K49867
tcDHuMHLo6wNCrjVssW4+rj3zru/qsHLuPbN5tCmoa2hrd/Xo6HPwsC0oaOhsQ0KICAgILr0
tdjSu9XGo6zSu7XAxua+os7e2bG1xNXGt+e0qbSwtviz9qGtoa0NCiAgICC637rfo6ENCiAg
ICC0sM3i0rvJ+cDkut+jrNbayMvWu771tcPR28ew0ruwtaOsuq635+yqyLujrM7d1tDS0b6t
tuDBy9K7uPbJ7dfFv+2087ra0sKjrA0Kw+bJq87ax+CjrMirye2/3crdo6zLq8S/uq654rXn
yeS1xNChwM/Iy8C0oaMNCiAgICDO5L+t1OfS0b+0x+XAtMjLysfLraOstbHPyNK7sN21wKO6
obDKpsrltPO83bniwdmjrL+ttvnT0Mqn1LbTraOsydDH68qmyuUNCsuh1++ho6GxDQogICAg
obDRqcm9tv7G5qGxyLTS0c/FtcPD5smrtPOx5KOst/zU2rXYoa2hrQ0KICAgIMC0yMu+ucrH
obCx+bvqtrTIy6GxoaMNCiAgICDL+9bY1ti12MDkut/Su8n5o6yzr87kv62148HLtePNt6Os
wOTA5LXAo7qhsMDPt/KzzbSmw8XPwsXRzb2ho6GxDQogICAgzuS/rdK7v7TH6dDOsru21KOs
wazDpr/nyc/Su7K9tcCjuqGwyqbK5aOsv622+czmzuK64qOszuLGvcfzx+mjrL/2x9LP1tTa
DQrV/da1t+fT6tauvMqjrMnQzfvKpsrlt6jN4r+qtveho6GxDQogICAgobCx+bvqtrTIy6Gx
09bA5LrfwcvSu8n5tcCjuqGwyPTKx8DPt/Kyu9TKxNijv6GxDQogICAgobDKp7vqvsbYpKGx
08mxx9bQx+HH4eDNwcvSu8n5tcCjuqGwoa7O5MHWyqW+/aGvx9fX1Mfzx+mxu77co6zO0sDP
yMu80rXaDQrSu7j2vs2yu7Tw06aho6GxDQogICAgobDKp7vqtrTIy6Gxw+bJq86iseSjrN+z
tcCjuqGwxOPLtcqyw7Sjv8utysehrs7kwdbKpb79oa+jv6GxDQogICAgobDKp7vqvsbYpKGx
uf65/rTz0Ka1wKO6obC+rs3cudvM7KOsv8nBr6Giv8nQptLTo6GhsQ0KICAgIMu118WjrNPD
0du54s37wcvN+87kv63Su9HbtcCjuqGwoa7O5MHWyqW+/aGvvs3Kx7jzz8K1xMqm1rajrLjz
z8K+ubK719QNCtaqoaOhsQ0KICAgIKGwsfm76ra0yMuhsdG9usfSu8n5o6y3rcntz8Kw3bXA
o7qhsMDP0OCjrMfryqW+/cWt1++jrMDP0ODO9MjVvs3U+Luz0snV4g0KteOjrLWryqW+/cq4
yM+jrLnKwM/Q4NKysru40tK7v9rSp7aoo6zP1tTaufvIu7K7s/bL+cHPo6y5/rn+o6HAz7fy
uN/Qy8vAwcujrA0Kuf65/qOhobENCiAgICDL+765tPPQpsHLxvDAtKOsxMfR+dfTxsTOqrus
u/yhow0KICAgINXiyrGhqqGqwqXN4qOsyMvTsM35wLS3ybPbsru++KOssczR5uDN4M3J/b/V
o6zV+7j2sNfC7cm9t+XWu87LyLvT+7avwcuhow0KICAgIKGwsfm76ra0yMuhsba4yLu21NfF
obDRqcm9tv7G5qGxsam6yLXAo7qhsL+01NrKpb79tcS33cnPo6zIxLn9xOPDx6Osu7myuw0K
v+zP8sqlvv2w3dC7oaOhsQ0KICAgIKGw0anJvbb+xuahsbGyt9bU2r2tuv7Jz8vkyLu8q9fw
o6y1q9TatMu/zLu509DKssO0u7DLtaOswazDps/yzuS/rd+1tcCjug0KobDQu8qlvv2+yMP8
1q6296GjobENCiAgICDNu8i7oaqhqqGwyqe76r7G2KShsbXAo7qhsMLotcSjrNK7xfrL79fT
wLTBy6GjobENCiAgICC7sLLFy7XN6qOswqXN4tLRvq3Tv8bwwcuy47Lj1tjO7aGtoa0NCiAg
ICC99L3T18XW8rvwufa59qOsue3TsMnBycGjrNL1t+fV89Xzt/fAtKOstLW1w8jLw6u5x+Ok
yLujrNDEwO/WsbTysvyhow0KICAgILa4tdihqqGq0rvJ+bntusWjrLPlzOy2+MbwoaMNCiAg
ICDSu8z1ue3TsKOsvLLLxsnBteew47XYz/LV4sKlzt3J5MC0oaMNCiAgICDO5L+ttc3J+bXA
o7qhsLj3zrux8Lavo6zV4r/WxcLKx8qutPPR1sLetcTK1s/CoaOhsQ0KICAgILuwssXLtc3q
o6zSu7j2yKvJ7cHBycHJwaOszuXR1cH5yaujrM23wbOyu7fWtcTIy9LRvq3GzLf809rO5L+t
vcXPwrK71La0pg0KtPPJ+bXAo7qhsMfroa667Mnxoa/B7squtPPR1sLe1q69+M3LoaOhsQ0K
ICAgIM7kv63OotCmtcCjuqGwzOzA17DvysfT0bfHtdCjrL6hwb/K1bf+uPe3vcjLyr+jrMTc
srvJsdfuusOjrMfry9m3oravuaXKxqOsDQq909OmzOzA17DvoaOhsQ0KICAgIMTHyMu088n5
06a1wKO6obDKx6OhobENCiAgICDSu9eqye2jrLyyyOfJwbXnsOO12NS9tLC2+MiloaMNCiAg
ICChsLH5u+q2tMjLobG5p8nttcCjuqGwztK1yLmnzP3Kpb79su7HsqGjobHW2sjLxuvJ+bXA
o7qhsMrHo6GhsQ0KICAgIMn51fDLxM3io6y6w7K70NvXs6GjDQogICAgzuS/rb2jyN3G8MGi
tcCjuqGwvfHI1dau1vfWvNTavbW3/qGuutqwtba01vehr6OssdjSqsqxo6yyu8+nydXJsaGj
obENCiAgICDKx6Oh0rvJ+brk06ajrNXwtq/CpdPuoaMNCiAgICDV4sqxo6zLxM3iybHJ+dLR
xvChow0KICAgIMKlzeKjrMjL07C8srPbo6zAtLvYsru++KGjDQogICAgvfHSuaOsva26/snP
1qrD+9auyr+8uLr1tPO24Mr9try+27TLtdijrMut0rKyu7qsuv3LraOsybHJ+dK7xvCjrLfX
t9fTtbP2DQq7p83io6678tO1u6ShsMzswNew76Gxo6y78s2sx+mhsLrsyfGhsbvyuN+69KGw
utqwtba0obGjrLvy1N6zyaGwtdjT/M31uK6hsaOsDQq4/NPQxMeyu7fWxcmx8KOss8O78LTy
vdm1xKOswaK8tNDOs8nSu8asu+zC0qOsybHJ+dXwzOyjrLHM0ebC0rTco6y6+snayfm0y8bw
DQqxy8Lko6yw18Ltt+XJz8mxxviz5czsoaMNCiAgICDgp6OhDQogICAg0rvJ+cfhz+yjrKGw
yqe76r7G2KShsbSps/a0sM3io6yxqczhtaTM79auxvijrLTzyfm6yLXAo7qhsKGuzuTB1sql
vv2hr9bYDQqz9r2tuv6jrLeyztLKpb79vsmyv8vZzazQxNCtwaajrLmyt/yhrrrasLW2tKGv
oaMNCiAgICC0y8n50ruz9qOsy8TN4rrk06ahow0KICAgIMm9t+XJz6Os0M7KxsGiseSjrLTz
tuDK/cjLtrzTtbukobDO5MHWyqW+/aGxo6y317fXzfnO5L+t1eK1yMjLy/nU2tauwqXHsA0K
vtu8r7b4wLShow0KICAgILj809DIy7Tzyfm69LrItcCjuqGwx+vKpb79s/a2+NK7vPujrM2s
yrGz9sq+yqXWvMHuoaOhsQ0KICAgIMKlyc/Iy9Owu862r6Osz7zTsLyyycGjrM7kv628sKGw
0anJvbb+xuahsaOsobC52M3iy8Sy0KGxo6yhsLH5u+q2tMjLobG1yA0KyMu91NProbDKp7vq
vsbYpKGxsqLBoqGjDQogICAgzuS/rcnxv6G3x7eyo6zOqtK7z7y54sv5wf2jrLC2waLW2sjL
1q7HsKOsyezK1sfhwtOho8ql1rzB7tTaytajrLjfuN++2cbwoaMNCiAgICChsMqnu+q+xtik
obG087rw0rvJ+bXAo7qhsMqlvv3U2rTLoaOhsQ0KICAgIMn51fDLxM3io6zE2sGm1q7Q27vr
yrW3x9K7sOPIy7/JzfvG5M/usbO1xKGjDQogICAgxMe/6cqlwe6xu7GmueLPvMb40rvTs6Os
t6Kz9snBycHO2rnioaMNCiAgICDB7snPtcTQ8cjVo6zItNL+yeSz9r3wuuy54ruqo6zX3cq5
yse8q9S2tcS12Le9o6y2vMTcv7S1w7yrx+Wz/qGjDQogICAgyeTWwcKlx7CjrLfvs9u157O4
tdjB6L/VyeTAtKGjDQogICAgyeTWwcKlx7CjrLa4yLvBotfjo6y3rcntz8K58qOst/y12LK7
xvChow0KICAgILOh1tDS0dPQyMu+qrr0tcCjuqGwt727qMG9zdWhraGtobENCiAgICDSu9Xz
yafIxbrltq/J0M60xr3PoqOs0ru1wLDX07CjrMauyLvC5NPawqXJz87kv63X48ewzuWz37Sm
o6y3rcntseOw3aOsv9oNCtbQtcCjuqGwsNfDt73TvN3AtLPZo6zH68qlvv3UrcHCoaOhsQ0K
ICAgINXiyrGhqqGq393f3cGsyfmjrLOh1tDG5Lyyzt7C27XYyeTPwsHLyq7T4LXAyMvTsKOs
trzKx7f8tdiyu7avoaMNCiAgICC99L3T18WjrNK7yfmzpLrIo7qhsMqlvv3Lodfvo6zAz7Xc
wLSz2aOhobENCiAgICC358n57KrIu6OszuS/rcPmx7CjrNPrsNe2/s/IyfqyosXFtvi58rXE
0ru49snt18Ww18Xbz+K67MO3tcSjrLDXt6LR77rs0OsNCsjnu/C1xLnFz6HAz8jLoaMNCiAg
ICDCpc/C09bT0MjLvqq1wKO6obC67MO3wM/Iy7P2wLTBy6Osv9bFwr3xzOyhrs7kwdbKpb79
oa+1xL7Jsr+2vLW9wcuho6GxDQogICAgzuS/rdDE1tCwtb6qo6yyu9aqtcDX1Ly6uLjH17XE
vsnX3LK/tb2119PQtuDJ2aOswazDpsrVxvDBy9a8we7QptfFtPPJ+bXAo7oNCqGwzuS/rc7e
tcLO3sTco6zJ0NDruPfOu7Tzwaa39tb6o6zU2tXiwO/PyNC7wcujrLj3zrvH68bwsMmho6Gx
DQogICAgwqXPwqOs1eLKsdLRvq2+28HLutrRudG5tcTSu7TzxqzIy9Owo6y7udPQsrvJ2cjL
1f2zr9Xisd+xvMC0oaMNCiAgICDO5L+ttcCjuqGwvfHSuaOszfu49867xNzW+s7kv63IsLf+
oa662rC1trTW96Gvo6y5sr+5tPPEp73MoaOhsQ0KICAgINK7yfnV8MzsuuTTprXAo7qhsMrH
o6GhsQ0KICAgIM7kv621wKO6obC49867yKWwyaOhobENCiAgICCw18O3z8jJ+sfEyLvG8MGi
o6zT0rHK1/PR4qOswMrJ+bOvwqXPwrXAo7qhsLe9u6jBvc3VzP3B7qGjobENCiAgICDY8cKl
udbN1dPryq+18c3VtPO68NK7yfm1wKO6obDT0KOhobENCiAgICCw17b+z8jJ+rXAo7qhsMi8
teOw18O3we6jrNXZvK/O9MjV0Na13KOsubLJzLTzvtmjrLTzvNLL5s7SwLSjoaGxDQogICAg
t727qLb+zdXT1rGpus/Su8n5o7qhsMrHo6GhsQ0KICAgIN/do6Hf3aOh392joQ0KICAgIMj9
tcCw17nis+XM7LOvxM+2+Mbwo6yz5dbBsOu/1dbQo6zF6ci71ai/qqOsu6/X97XjteOw18O3
o6zTs8HBwcuw67HfzOyjrA0Ku7q7ur21z8Khow0KICAgILDXw7fPyMn6scrSu7vTo6zSu7XA
sNfTsKOswsrPyM/yxM+3vcauyKWhow0KICAgILe9u6i2/s3VvfTL5sbkuvOjrLyyyeS798il
oaMNCiAgICC99L3T18WjrLfnyfnsqsi7o6zIy9OwvLLJ5KOsy8TD5rDLt73T0LK7ydm1xMjL
o6y2vM/yxM+3vde3y+a2+MiloaMNCiAgICC67MO3wM/Iy9Lg0tHG8MGio6zB3cjdusi1wKO6
obC7yrimtdzQ1sz9we6ho6GxDQogICAgt+fJ+eyqyLujrMj9tcDIy7yyyeS2+LW9o6y4qbf8
09q67MO3wM/Iy9fjx7Chow0KICAgILrsw7fAz8jLtcCjuqGwt6K67MO3we6jrMvmztLAtKGj
obENCiAgICC7yrimyP3Q1rXcxuvTpqO6obDKx6OhobENCiAgICDJ7dDO0rvG8KOsyP21wLrs
0ebGxr/VtvjJz6OsxenIu9K7yfmjrLuv1/fC/szsuuzDt6Osy8TN4rykyeShraGtDQogICAg
uuzDt8DPyMu3vb2rxvCyvaGtoa0NCiAgICDSu7XAwszTsNKh0re2+MC0oa2hrQ0KICAgILrs
w7fAz8jLuf65/rTz0Ka1wKO6obDP67K7tb3Az8vE0rLAtMHLoaOhsQ0KICAgIMnt0M7G8LSm
o6zI58aut+ew47XYz/K2q7e9sanJ5Lb4yKWhow0KICAgILvKuKbI/dDWtdy99MbkuvOhow0K
ICAgILra07Df3d/do6zLxLe909bT0NDttuC9rbr+uN/K1r30y+a2+MiloaMNCiAgICC67MO3
wM/Iy7LF0rvX36OswszTsNK7u86jrM7kv63D5sew0tG+rbf818XSu867ye3XxbDXvfXP4sLM
w7e1xMTqx+DK6cn6o6wNCrjfyfm1wKO6obDAz7O8sruyxaOsyOjTrcqlvv2jrMbyzfvJ4tfv
oaOhsQ0KICAgILOh1tC358n57KrIu8LMw7fK6cn6tPjBy9K7xfrIy8C0oaMNCiAgICDO5L+t
0Ka1wKO6obC/7KOsx+vG8MC0o6zIpb3T06bL+8PHsMmho6GxDQogICAgwszDt8rpyfrKx7j2
v7TG8MC0vKvOqsjlv6HDwLXEydnE6srpyfqjrNfzytbH4c7V18XSu77tyumjrLmn06a1wKO6
obDKx6OhobENCiAgICDGrsi7xvDBoqOswMrJ+bXAo7qhsLSrz8LCzMO3we6jrMvmztLP8s73
yKWhsaGjDQogICAgyMvTsNbQwaK8tLPlxvDBy7y4tcDCzLnio6zJos/Cwv7M7MLMw7ehraGt
DQogICAgwszDt8rpyfrS0b6ttbHPyM/yzve3vcauyKWhraGtDQogICAg1eLKsaGtoa3M7L/V
1tDJosL6wcuw16OsuuyjrMLMyP3Jq8O3u6ijrMPAwPbS0byroaMNCiAgICDLxLSmuvrJ2sn5
uPy8saGjDQogICAg1La0pqOstKvAtLbPts/Q+ND4tcSy0rrFyfmhow0KICAgIMmxyfnV8NKw
oaMNCiAgICCxzNHms+XM7KOsyOfB6cnfsOO12NTav9XW0LSpwLS0qciloaMNCiAgICDNrMqx
oaqhqsm9t+XJz6Ost7rG8MHL1fPV88Wozu2jrLntyfngseCxo6zW8sjLycG2r6GjDQogICAg
sfm76ra0yMvRyLXAo7qhsMbmudajrLvGw7e+08nPy8TP4NauytejrNT1w7TOtMC0o7+hsQ0K
ICAgILu509Cwy72r0rLOtM/W0rvJ7aOsyqe76r7G2KS5/rn+0rvQprXAo7qhsMv7w8e087jF
srvPsru2vfHM7NXi1tbKorvhsMmjoaGxDQogICAgy7XXxc/yzuS/rcfryr61wKO6obDM/cHu
yqW+/da4xcmho6GxDQogICAgzuS/rbXAo7qhsLnYzeLLxLLQo6zRqcm9tv7G5qOsuqO118DP
1d+jrMjOzaXN+bGxt73IpaGjobENCiAgICCwy8jLuafTprXAo7qhsMHs1ryjoaGxDQogICAg
4Kfgp8GsyfmjrLOvsbG3vbyyyeS2+MiloaMNCiAgICDO5L+t09azr7H5u+q2tMjLvLDKp7vq
vsbYpLXAo7qhsMG90bLTzqOs0KHQxLfA1rmjrKGuutqwtba01vehr9ffzdGho6GxDQogICAg
obDKpb79o6zE+tfUvLq1xLCyzqOhraGtobENCiAgICDO5L+t0Ka1wKO6obDIpbDJo6HO0rK7
0qq99KGjobENCiAgICDBvcjL09a5p9Om0rvXqMn5o7qhsMHs1ryjoaGxDQogICAgye3QzrGp
xvCjrLyyyeS2+MiloaMNCiAgICDO5L+tvPvIy7a80tG+rdfftcOy7rK7tuDBy6Os1ru8+8r9
yq649tbQxOrIy9LUyc+1xM7kwda438rWo6yz7sO8v+DBs7XY1NoNCrXNyfnC8dS5tcCjuqGw
ztLDx7XEytfB7NT1w7TDu8C0o7+hsQ0KICAgIM7kv63S0b6twMrJ+dD7sry1wKO6obC3ss70
yNXKpb79vsmyv6Osv8nX1NPJ0NC2r6Os0tShrrrasLW2tKGvzqrwwLXEoaOhsQ0KICAgINba
yMu65LTw0rvJ+aOst9e317Pps/bBy7H4yNCjrLyys9vLxMmioaMNCiAgICDO5L+t0MTW0LTz
vqqjrNH2zOzSu8n5s6TQpaOs1rHGxtTGzOyhow0KICAgIMe6x7rHuqOh0rvV88H60veyu774
o6zRqrnisanP1qOstuHD/NGqvaOz9sfKo6y0+MbwzuWz37rsw6Khow0KICAgIM7kv63Lq9fj
0ru22aOsobDRqsb4obHTv8nttvjG8KOs0ru25Lrs1MbTtdfF0rvPvLnioaO0+Mbw0ru1wLrs
07CjrLyyyeSz5Q0KzOy2+Mbwo6zlyc/yutqwtba019yyv7PbyKWhow0KICAgINLRvfzI/bj8
o6ENCiAgICDD99TCo6zI98/CwcvSu8as0vjEu6OhDQogICAgsNfC7bflyc+jrMmxxvDV8Mzs
oa2hrQ0KICAgIMvEzeKjrLTcxvDBy7SmtKa78MPnoaMNCiAgICC78MrG1L3AtNS9tPOhow0K
ICAgILr6ydrJ+dKy1L3AtNS9vLGjrMzswNew77XEytbPwtX9z/LW0NDEzqe5paGjDQogICAg
1tjO7cH916HBy9X7uPaw18Ltyb235aGjDQogICAg1eK12NP8zfW4rrXEvdzX96OhDQogICAg
ztihraGtDQogICAgy8S0ps/sxvDBy8bgwPe1xL3HyfmjrNXiysfD/MHuy/nT0LrasLW2tLXE
yMvK1sirwabS1Liwo6zS1NGq0+vI4sC0vOHK2LDXDQrC7cm919zMs6GjDQogICAg392joQ0K
ICAgINK7zPW0v7vGu/DW+aOss+XM7NO/xvCjrNbBv9XW0Mr9yq7Mq7jfuvOjrLrkyLvVqL+q
o6zP1LP2vLi49tfWwLShsLrasLW2tA0KzfLL6qOhobENCiAgICDBory0oaqhqt/d393BrMn5
o6zK/bDZsczR5tfUsrvNrLXEt73P8rfWyeTBy8nPyKWjrMGivLS9q8THvsW49tfWs+XJosHL
o6ENCiAgICDSu8n5uN+6sKOsy8a69crHyqe76r7G2KS1xMn50vShow0KICAgIMn50vS437+6
o6zV8LavzOy12KGqoarJsaOhDQogICAgybHJ+dHNw7vBy9K7x9CjoQ0KICAgIM7kv63X1MKl
yc/GrsnktvjG8KOsycHEv9K7zfujrNfzx7C3vbra0bnRubXY0ru088astcTDycPmtPO6ur/g
1b2yu9Ddo6y1qw0KyLTS0c/UtcOyu9ano6ENCiAgICDUrcC0xMfQqbra0sLDycPmtPO6uqOs
zuS5prjfx7+jrMq508PXxc/gzay1xLnW0uzV0Mq9o6yxxrXDzOzA17Dv0Na13M3FzcUNCtax
16qjrLy4zt67ucrW1q7BpqOhDQogICAgtvi12MnPo6zS0b6t0arI4sSjuv212MzJ18W6w7y4
vt/KrMrXoaMNCiAgICDO5L+twOS639K7yfmjrL3FvOLSu7XjtdijrMjn0ru25Lrs1MbTyczs
tvi9taOsyeTI68jLyLrW0KGtoa0NCiAgICDRqr2j0ru706OsstK90LbZxvCjrMmyxMe85KOs
0tG9q7ra0sK087q6yKvK/b3ivvahow0KICAgIMzswNew79bayMu+qrXDxL+2qL/atPSjrLPV
waLSu8XUoaMNCiAgICDO5L+ttcCjuqGwuaXP8rTzte6ho6GxDQogICAgte7X1rP2v9qjrMjL
0tHJ5LP2yq7T4NXJwcuhow0KICAgIMTH0KnM7MDXsO+1xNDWtdzDx9XissXI58POs/XQ0aOs
vqq90LXAo7qhsLCh0b2jocv7ysfKpb79oa2hrc7kwdbKpb79oa2hrQ0Kv+yhraGtv+yhraGt
obENCiAgICDK/cquyMvSu87Rt+TP8tX9te6jrM7kv63C09DQyv3Vybrzo6zNu8i7zsW1w7fn
yfm69Lr0o6yy0rrFxrXG8KOsye3HsLK71LYNCrSmo6zVvb/21f3B0qGjDQogICAgy/u8scOm
vNO/7L3Fsr2jrM35x7DSu7+0oaqhqg0KICAgIMTHwb249rq619OjrMntt6jB6cfJo6zVxsGm
xua+oqOszujG8ML+zOzVxtOwo6zV/c/yu/Dszce/uaW9+LHGoaMNCiAgICDO5L+tz/LX87Hf
0ru/tKOssru9+7j8yse087PU0ru+qqGjDQogICAguqO118DP1d/Lq76msanNu6Os1+yyv86i
v6qjrM/K0arWsc3CoaMNCiAgICDL+9fzyta99M7V16HM+r2wo6zY8dnN18XJ7dfToaMNCiAg
ICDV/dPQwb249rra0sK67MX7t+e6utfTx7C687zQuaWjrMvEy6vK1rT4xvC69Lr0v/G358/y
y/vBrLu3w83F/KGjDQogICAgy/vDzdHv09LK1qOsvLLJ5Lb4s/ahqqGqxe6joQ0KICAgINK7
1ca908q1o6y6o7XXwM/V37LSvdDSu8n5o6zJ7dDOsbvV8LXE0LG3ybb4s/ahow0KICAgILWr
y/u7ucrH1/PK1sPNzKejrMz6vbC64bfJo6y/s8/ywe3Su8+uwLTWrsjLoaMNCiAgICC1scTH
uuzF+7fntcS6utfTut/By9K7yfmjrNPSsdvSu9Hvo6zSu7XAztq54ryyyeS6o7XXwM/V39DY
z8K1xNbQ6/7W2NGooa2hrQ0KICAgIMHtzeLEx8jLye3QztK7seSjrMDkusjBy9K7yfmjuqGw
1dLLwKOhobENCiAgICC69LXY0rvVxqOsw83F/Lb4s/ahraGtDQogICAgzuS/rdK7vPvWrs/C
o6zT8cPmwaK6rqOsv6HEv9bQo6y2uMi7yeSz9sG9tcC6rsmttcTJt8b4o6y3ycntx7DQ0NbQ
o6zX87HbDQrDzcyno6zUy9PDzuWzybmmwaajrLOvxMe1wNXGt+fTrbP2oa2hrQ0KICAgIM2s
yrGjrNK7yfnA5Lrfo7qhsMTDw/zAtKGtoa2hsQ0KICAgINGqvaPWuLSmo6y1sbXY0rvJ+cfh
z+yjrNK71ru2vt3w3ryjrLG7zuS/rdK7vaPF/L+qo6zJorfJtviz9qGjDQogICAgvaO54tK7
y7OjrMehusPTrc/ywLTPrsTHyMuhraGtxenIu9K7yfm089Xwo6zBvbnJ1ca357ulvdOhqqGq
DQogICAgxMfIy8PGut/Su8n5o6y3rbfJ1fCz9qOssMi12NK7yfmjrMuktdjJz6Osy8DT2rfH
w/yhow0KICAgILCl07Sjocntx7DSu8n5stK90KOs0aq9o9LRvq3NuMf7tvjI66Gtoa0NCiAg
ICDO5L+twaK8tLipye2y7L+0uqO118DP1d+1xMnLysajrLz7y/vS0b6tu+jLwMHLuf3IpaGj
v9q9x8/K0ark/eT9wfez9qOssccNCr/X1tDSssn4wcvLv8u/0aq8o6Osw+bJq7j8ysey0rDX
tcPPxcjLoaMNCiAgICDO5L+twazDpszNs/bBy9K7v8XX1LXY0MTKwL3nwO+0+LP2wLS1xNOy
v8e5+6Oswb3WuMfhx+HSu8Tzo6zM+LP20ru/xbn70MSjrA0Ks6+6o7XXwM/V37/a1tDSu8j7
o6y149ehwcu8uLSm1rnRqtGotcCho8fhx+HSu9XQo6zUvtbB0rvX+bzZyq/F1KOsvavL+8fh
x+G3xQ0Kz8Khow0KICAgIM27yLvSu8n5stK68LSrwLSjrMn50vTG4MD3zt6xyKGjDQogICAg
zuS/rdDE1tDSu76qo6z2xMi7tvjK09auz8KjrLK7vfu087PU0ru+qqGtoa0NCiAgICDWu7z7
zvfBydK7vvi78OzNtcTX88rWsuXU2tPSsd+1xMTHuPa6utfTtcTT0tDY1tCjrLWrxMe6utfT
tcTT0srWo6zItNKyx7YNCr34wcu78OzNtcS85823oaMNCiAgICDB7c3i0rvIy6Os0tG+rdK7
1cbP8rvw7M21xLDZu+HRqKGjDQogICAgzduhqqGq0b2joQ0KICAgINPWysew68n5stK90KOs
uuy54rDX07CxwM/Wo6y78OzNtcTE1LT80tG+rbG7tPK1w8+hwMOjrMv1vfiysdfTwO/D5sil
wcuhow0KICAgIMTHuuzF+7fntcS62tLCw8nD5rXEurrX08Dkut/Su8n5o6zN+8HLzfu12MnP
8/nz+bb4tra1xLvvsOnSu9Hbo6zV/c/ywe3Suw0Kt73P8sbLyKWhow0KICAgIM7kv63V4sqx
o6zFrbvw0tG437Pjo6zT0srW09az6bSkwcuhow0KICAgINHbv7TEx8jLwOvIpaOsy/uyu737
xa26yLXAo7qhsLvYwLSho6GxDQogICAgxMfIy8rV16G9xbK9o6y9o7zi0LG12LPps/a1wKO6
obC488/Cy8DG2rW9wcuho6GxDQogICAgu7DJ+c60wuSjrMnt0M7Su7avo6zRqrniycHR29bQ
o6zSu8n5stKwoaOs0ru/xcjLzbe0+NfF0rvB79Gq0+qjrLPlzOy3ycbwoaMNCiAgICDNu8i7
o6zSu8n5s8G6yLXAo7qhsNW+16Gho6GxDQogICAgt+fJ+eyqyLujrM7kv63J7cewsrvUtrSm
0tG+rcGiwcvBvbj2uuzSwqOsuuzF+7fno6y67MPJw+bW0LXEurrX06GjDQogICAgzuS/rb3F
0ru22aOswOTA5LXYtPLBv9fF1eLBvbj2yMujrNDE1tCwteLitcCjuqGwysehrrrasLW2tNb3
oa+1xLfWtrTW96OsDQqyu9Kq0KG/tMHLy/vDx6GjobENCiAgICC3veLixO685KOs1/Ox38TH
yMvA5MDk0rvQprXAo7qhsNCh19OjrNXiwO/Kx8Tjsc/D/Nautdiho6GxDQogICAgu7Cyxcu1
zeqjrNK7yfm1zbrItcCjuqGwyc+ho6GxDQogICAg78/vz8GsyfnW0KOsuq654snBycGjrMG9
zru31ra0trTW99LRvq3K1rPW18XSu7H6uq654snBycG1xMD7yNCjrLfW08nBvbLgo6wNCr7t
xsu9+KGtoa0NCiAgICDO5L+twOS6yNK7yfmjuqGwwLS1w7rDoaOhsQ0KICAgIKGw0arG+KGx
t6K2r6Osu+vJ7c24s/bV89XzuuzO7aOs09LK1tK7u9OjrNK7tcDRqrni07W0pqOs0aq9o9LR
vq2437jfvtnG8KOsDQrLq8S/uq654rXnyeS12NeiytPXxcTHwb249rrs0sK2tNb3oa2hrQ0K
ICAgIMG9uuzSwra01vejrNK70dSyu7eio6zLq8ur0rvKudHbyaujrMnt0M62uLfWwb3Wp7Ok
vaO7r9f3wv7M7L6rueKjrLfW08nX8w0K09LBvbLgo6zJ5Lv3tvjAtKGtoa0NCiAgICDO5L+t
vfS2otfFwb3Iy6Os1sXBorK7tq+how0KICAgILT9wb3Iy738tcPJ7cC0o6zL+827yLvA5Lrf
0rvJ+aOs09LK1ra4u9OjrNK7xqzRqr2j07DJ5Lb4s/ahow0KICAgIMG9uuzSwsjL0MTW0LTz
s9TSu76qo6y7xcOm1tCjrMWk0fy15rK9o6y9o9XQ0rux5KGj1ebG+NLRyLu54dPavaPJ7dau
yc+jrA0K0rvX89K709KjrLeis/bLv8u/1q7J+aOstrXNt8X8wLShraGtDQogICAgzuS/rcDk
wOTQprXAo7qhsMG9zrvT0Mqyw7SxvsrCvqG53Mq5s/bAtLDJo6GhsQ0KICAgINPvyfnOtLHP
o6zJ7dDOvLLI59D9t+fLxrXE0rvXqqOstuHD/M7lvaO12tK71dChsNGqueKxwM/WobHVub+q
o6zSu7XAz8q67A0KueLW+aOs1tDN8senvaPTsKOs0v680NfFt6XA19auyfmho7SjyLu8stD9
tvjG8KGjDQogICAgzuS/rb3xzOzWrrmmwabUtrOsuf3O9MjVtuC24KOstuHD/M7lvaPSu8qp
1bm/qqOsyfnKxrrVyLujrLfnvu3Uxsbwo6y3vdSyDQrKrtPg1cnE2tK7xqzRqrnivaPTsKGt
oa0NCiAgICDBvbrs0sK2tNb3xvG3x8rHt7q3utausbKjv7z717S0876qyqfJq6Os1qq1wNfU
vLq++LfHyMu80rXEttTK1qOs1rvT0La01vcNCrP2wLSjrLvyv8nT67+5zsChow0KICAgILTL
xO7Su8bwo6zNy9LiwaLDyKGjDQogICAgtau0y8qxo6zLxNbcvdTOqtGqueLTsMv51dajrLbU
t73J7dDOsru8+6Osz+vSqr7NtMvNy7P2o6zMuLrOyN3S16GjDQogICAg1ru1w8ury6vDxsHL
0rvJ+aOsvqHIq8nt1q65psGmo6zO6Mbwwb3NxcnBycG+q7nio6zIq8Gm1qezxdfFy8S0ptbY
0bmhow0KICAgIMvEzeLRucGmtPPU9qGjzuS/rbXE0+/J+cDkwOS0q8C0o7qhsMG9zrvL2cb6
vaO56dLAo6y/ycPi0rvLwKGjobENCiAgICDBvbrs0sK2tNb30Ka1wKO6obDEx8TjysfU2tf2
w86jrL7Ny+PO0sPHv8+jrLrZutmjrNKy1rvKx8LktcO4r8qs0rvK16Gtoa2hsQ0KICAgIM27
yLuhqqGq0rvJ+cDk0KajrLP219TKrtPgzKvN4tK71uq088r3z8KjuqGwuPPPwrn7yLvT0MG9
ytaho6GxDQogICAgx7rHuqOhDQogICAgwb3J+cz6vbvD+bSrwLSjrML+zOy9o9OwttnP1qOs
zdC12LfJxvDBy8G9teO54qOsvLLJ5Leiyfm0pqGtoa0NCiAgICCzodbQtPTBotfFwb3Ou7a0
1vejrML6wbO+qsXCtdjN+9fF19S8usrWyc+1xLDrvdi2z72joaMNCiAgICC62brZo6ENCiAg
ICDK97rz0rvJ+cDk0KajrLvG07DSu8nBo6zP1rP2ye2yxNDes6SjrLfntsj05vTmtcShsLra
sLW2tNb3obGjrMvmytbSu7f3o6wNCsDkwOS1wKO6obC+xsTSt7m0/KOhobENCiAgICDBvbXj
ueLUrcrHwb292LbPvaO84qOssbuhsLrasLW2tNb3obGjrNXi0ru396OsuvS12NK7yfm7r9f3
wb2148H30MejrLyyyOcNCrXnyq+54rvwtdizr8G9uuzSwra01vfJ5Miloa2hrQ0KICAgIMG9
uuzSwra01vfg5Mj0uq6y9aOsytaz1rbPvaOjrNW+1NrSu7Hfo6y2r9Kysru2r6GjDQogICAg
0du/tMG9teO6rrnivLLI57XnsOO12MnkvfjBy8G9zru67c/CxvjDxdGooa2hrQ0KICAgIM7k
v63A5Lrf0rvJ+aOst7TK1tK71cbFxLP2o6zSu9Xz0vXI4cDkt+e+7bP2o6y1wKO6obC2tNb3
tPO/ybK7sdjEw8v7w8ez9g0Kxviho6GxDQogICAgu7Cyxcu1zeqjrMG9teO54s27yLu+orXA
yKvP+6OstbG1scG9yfmjrMLk1NrBvbrs0sK1xMPmx7Chow0KICAgIKGwutqwtba01vehsbn+
uf7Su9Xzv/HQprXAo7qhsMTjw8fBvcjLu7myu7/syKWx8LSmv7S/tKGjobENCiAgICDBvbrs
0sK2tNb3uafJ+bXAo7qhsMrHo6GhsQ0KICAgIMury6vLyrzntvjIpaGjDQogICAgwdnIpaOs
zfvBy87kv63Su9HboaMNCiAgICDV4svEtcDR27nio6yz5ML6wcu40Lyk1q7H6aGjDQogICAg
tP3BvcjLye3Qzs/7yqe686OszuS/rcynzbfLxMPmzfvBy837tcCjuqGw0ebTsLPlzOyjrLP+
uOjLxMbwo6y2tNb30MTW0NPQDQq6zrjQz+ujv6GxDQogICAgobC62rC1trTW96GxwOS639K7
yfmjrLXAo7qhsLPwzOzAy8vkyLvS0b6tsbvE48rVwvKjrLWroa612NP8zfWhr8i0zrSx2M6q
DQrE48v508Oho6GxDQogICAgzuS/rcDkwOTSu9Cmo6y1zcn5tcCjuqGwoa612NP8zfWhr9Ky
1b7U2rG+yMvV4rHfoaOhsQ0KICAgILrasLW2tNb3utm62dL10Ka1wKO6obChrrXY0/zN9aGv
sb7Iy8O7wLSjrL7Ny+O12NP8zfW4rtKysbvE48rVwvLBy6Ossb62tA0K1vfSsrK7vuXE46Gj
obENCiAgICChsNfdyrnE47K7vuXO0qOstavE47XEytbPwsj0yKuyv7G7zcDJsbvyyKuyv7e0
xdGjrMTj0ru49sjLxNzT0LbgtPO1xMTcDQrEzaO/obENCiAgICChsLrasLW2tNb3obHNu8i7
0fbM7LTz0Ka1wKO6obCxvra01vfK1s/CyPTKx9PQ0rvIy7e0xdGjrNTyy/vWu8rH19TL2cbk
y8ANCrDVwcujrMj0ysfIq8r9sbvNwKOsysexvra01ve1xMrCo6y3uLK718XE48C0tuC53M/Q
ysKho6GxDQogICAgtMvT79K7s/ajrM7kv63Nu8i7z+vG8MHLxMfSucHW1tDWrtW9x7CjrM7B
xsfL+cu1tcS7sKO6obC2+MfSo6zAz8q1y7WjrNa7DQrSqr3i0qm1vcrWo6zO0sPH0rK+zc60
sdjFwsHLy/uho6GxDQogICAg0ru49sTuzbejrM27yLvC07n9wcvL+7XE0MTNt6Ossru9+8Pm
yau9pbquo6yzwcn5zsq1wKO6obDQsLbxtr7Ep8rH1/C83bXEDQrKssO0yMujv6GxDQogICAg
obC62rC1trTW96Gxuf65/r/x0Ka1wKO6obDJs7rX0arEp8rH1/C83bXEyrLDtMjLo7+hsQ0K
ICAgIM7kv63QxNbQ0ru+qqOsufvIu7K7s/bL+cHPo6yhsLrasLW2tNb3obHKx9CwtvG2vsSn
tcTH18ratdzX06OstbHPwrK7vfvA5A0KwOS1wKO6obDX8Lzdsrux2LnK1/fJ8cPYo6zEx9XF
w8nD5r3tv8nS1MTDz8LAtMHLoaOhsQ0KICAgIKGwutqwtba01vehscDk0Ka1wKO6obDSqsih
uPPPwtfUvLq2r8rWo6y62brZo6yxvra01vfDu8THw7S24LXEyrG85Lj6xOPPuQ0KsvijrL/s
vfjV0LDJoaOhsQ0KICAgINXiyrGjrLflyc/Jscn5y+S99KOstavKx7LSusXJ+bu5yseyu774
09q2+qOs1f3W0LTzte7S0b6tyLzG8MHLs+XM7Lvw0eajrA0K1dW1w9X7uPbJvbflyc/D98jn
sNfW56OhDQogICAgy8TW3Lr6ydrJ+aOsvaXP8rTzte68r9bQoaMNCiAgICDKp7vqvsbYpL/x
t8W1xNCmyfmjrLK7yrG1xLSrwLShraGtDQogICAgv9XW0KGqoaqz/cHLu/C54s3io6yxzNHm
y8TJ5KGjDQogICAgu7nT0MTHuuyhorDXoaLCzMj9yau1xMO3u6i78NHmo6zLxMmi17nPwqOs
ybfKx8PAuduhow0KICAgINPJ1eK8uLXjyc+/tMC0o6yhsLrasLW2tNb3obHWrrDco6zKx9LR
s8m2qL7Wwcuhow0KICAgIM7kv63A5L6y0tG8q7XYtcCjuqGwutqwtba01vfWrrjEsNzN9qOs
0tGzybaovtajrLa01ve7ucrH1NrLvLb40NCyxbrDoaOhsQ0KICAgIMu118WjrLnK0uLP8svE
1tzN+8HLzfujoQ0KICAgIKGwutqwtba01vehsbK7ysew17PVo6zEx9PQsrvWqtauwO2jrLWx
z8LA5MDktcCjuqGwsb62tNb31rvSqr2ruPPPwsTDz8LJsQ0Ky8CjrNPa1LjS0cHLoaOhsQ0K
ICAgIM7kv6262brZ0rvQprXAo7qhsLrDvKvBy6Os1NvDx7W9tPO17seww+bIpdK7vva0xtDb
sMmjoaGxDQogICAgobC62rC1trTW96Gxut3J+bXAo7qhsLrDoaOhsQ0KICAgIMnt0M7Su9D9
o6y7xtTGxvC0pqOs1rHGy7Tzte6joQ0KICAgIM7kv623tMrWvavRqr2juenHyrrzo6zLq9fj
0ru22aOsu6/X99K7tuS67NTGo6y99Mvm18WhsLrasLW2tNb3obHJ7brzx7DQ0KGjDQogICAg
tPO17sewo6zB0tHmzNq/1aOsu/DR5sLSt8mjrMjL07DX3brho6zPytGqy8TI96GjDQogICAg
obC62rC1trTW96Gx1q7K1s/Co6y8sNO1u6S62rC1trTWrs7kwda6wL/Nw8ejrLTztuDK/b3U
0tHNy7W9wcu17sewo6y4utPnDQrN57+5o6zgqdGq0arVvaGjDQogICAgtba54rv0u/SjrL2j
07DI58m9o6zU2bzTyc/Ex9XGt+fWuNOwo6zIrcn5uvS69KOste7HsLvw07DPwqOsye7O7dbQ
o6zIy9OwDQq0wrTCtdjOp8Gi18W9/MenzuTB1rjfytahow0KICAgILOh1tCjrMr9yq7Iy6Os
1f3U2tf318XK4svA1q7VvaGjDQogICAgtrjIu6Gqoaq+orfn7KrIu6Os0ru7xtK7uuzBvbbk
ssrUxsHov9W2+L21o6zNrMqx0rvJ+cDKusijuqGwutqwtba01ve13NDWDQq4+M7S16HK1qGj
obENCiAgICDV4sqxo6yw18O3z8jJ+qOsuuzDt8DPyMujrMLMw7fK6cn6o6y31sj9w+a2+MGi
o6zHocfJvavL+dPQzcvCt7a8t+LXocHLoaMNCiAgICDI/cjL1q685KOsysfM7MDXsO+w79b3
s/DM7MDLo6zD5s7ese3H6bXEyq6089HWwt68sMqnu+q+xtiktcjIy6GjDQogICAgutqwtba0
t73D5r7bvK/U2rvws6HHsKOsv7TH6dDOy8DJy8/gtbGy0tbYo6y67NLCtrTW99a7yqPPwsj9
zrujrLfWzMPMw9b3DQrSssrHw7u8uM67wcujrMjLyLrW0MGivLTG8MHL0rvV88mntq+how0K
ICAgINPQyMu1zcn5tcCjuqGwxOO/tKOsy/u+zcrHobDO5MHWyqW+/aGxtdrI/bT6oaOhsQ0K
ICAgIKGwy/uyu77NysehrrrsyfGhr8Lwo7+hsQ0KICAgIKGw4MWhraGtobENCiAgICCw18O3
z8jJ+rXItry1pc+l18W12KOswb3K1rfWsubQ2Mewo6zR9srXufLBy8/CyKWhow0KICAgINXi
ysfO9MjVobDO5MHWyqW+/aGxs6/W0NTa1fPHsLnbvPvWrsDxoaMNCiAgICDSu8myxMe85KOs
1fu49rOh1tC2vL6ywcvPwsC0oaMNCiAgICCw18O3z8jJ+rXIyMvJ7brztcS9/MenzuTB1rrA
vdy2vLfXt9e12NLUzazR+bXE18vKxrnywcvPwsC0oaMNCiAgICCzodbQxrTD/NjLybG2r8rW
tcTIy6Os0rK2vNLUzazR+bXE18vKxrnywcvPwsC0o6yx7cq+ttShsM7kwdbKpb79obG1xLPn
vrShow0KICAgILrasLW2tLXc19O8sMbky/uw2dPgyMvU8s/yobC62rC1trTW96GxufLPwqOs
0tTKvtOtvN2how0KICAgILz7wPHN6rHPo6zO97e9w+a1xMjLtrzVvtaxwcvJ7dfToaMNCiAg
ICCzodbQo6yz/cHLu/DJ+aOsvLC3v9PutcS1ucn5zeKjrNa709DEx9CpzbS/4LXEyevS98n5
sru++NPatvqhow0KICAgILvwueKjrNXV1NrDv9K7uPbO7dbQyMu1xMGzyc+jrLa8ysfRz8vg
0+uzwdbYtcShow0KICAgILK7ysfC8KO/DQogICAgvdjWwcS/x7DOqta5o6yw18Ltt+XJz6Os
xMfA78O709DNv8L6z8rRqqO/xMfA78O709C2z9arstC5x6O/xMfA78O7yMvNtL/gDQq1xMnr
0vejvw0KICAgINXiysfSu7Ohv9XHsLXEzuTB1rTzvdmjrLPJx6ezybDZtcTIy6Os0tG+rcml
ye3U2tXiyb235cnPwcuhow0KICAgILu509DO3sr9tcTIy6Os1f3P8tXiyb235cnPuM/AtKGj
DQogICAgxL/HsKGqoarV4rvws6HHsLXEs8G8xaOsydCyu9aqtcDKx9Xis6HJsb3ZtcS94cr4
o6y7ucrHwe3Su7OhybG92bXEv6rKvKGjDQogICAg193Iu8rHs8nE6tTatba/2snP88LRqrvs
t7mz1LXExfPT0cPHo6zV4sqx0rK6rsHL0MShow0KICAgILWrysehqqGqsru53NXiysfSu7j2
veHK+Lvyyse/qsq8o6zLrba81qq1wKGj1eLKx8Ht0ru49rrGvdm1xL+qyryjrMHt0ruzoQ0K
1b3V+bXE0PLEu6GjDQogICAg1Nq688PmxMezodW91fnW0KOs1rvSqsrH1Nq9rbr+yc/F3LXE
xfPT0aOsw7vSu7j2sru+rcD6uf2how0KICAgIMv50tSjrMutxNzT0Mfhy8m1xNDEx+mjv8ut
xNzU2dCmtcOz9sC0o78NCiAgICDFqM7to6y9pb2lyaLIpaGjDQogICAgwOjD98ewtcS62rC1
o6y4w8rH1+662rC1tcTBy6GjDQogICAgtauw18Ltt+XNt6Os0rvGrMP3wcGhow0KICAgINDH
ueLPocLko6zV4rjDysfSu7j2w8DA9rXEx+/SuaGjDQogICAgobC62rC1trTW96Gxs8HW2LXE
v6q/2rXAo7qhsMfls/bSu8asv9W12MC0oaOhsQ0KICAgIKGwysejoaGxDQogICAg0rvJ+brk
z+yjrNPJy/vJ7brz0+O54dffs/a2/squuPa62tLCw8nD5rTzurqhow0KICAgIM7kv63S4LvY
zbezr7DXw7fPyMn6tcCjuqGwtv7PyMn6o6zH68XJyMuw0cnLyMvMp7+qo6GhsQ0KICAgIMmy
xMe85KOs19+z9sj9yq649rTzurqjrMquuPaw19LCo6zKrrj2uuzSwqOsyq649sLM0sKjrNff
vfizodbQo6zQodDE0u3S7Q0Ktdi9q8nLyMvMp7+qoaMNCiAgICCyu9K7u+G2+bXEuaa38qOs
te7HsMfls/bBy8j9yq7Vybe91LK1xNK7v+m/1bXYwLShow0KICAgIKGwutqwtba01vehsbDB
yLuzr87kv63Su/Klyte1wKO6obDO0sPH1eK+zb+qyrywyaOhobENCiAgICDO5L+t1eLKsbe0
tbnOos6i0rvQprXAo7qhsLHwvLGjoaGxDQogICAgobC62rC1trTW96Gxv+fHsNK7sr3A5LXA
o7qhsLjzz8LT0Mqyw7THstHUv+zH67fUuMCjoaGxDQogICAgzuS/rcDkwOS1wKO6obC3z7uw
ydnLtaOs1eKzocqkuLrWrrrzo6y4w9f3us6+9raoo7+hsQ0KICAgIKGwutqwtba01vehsdH2
zOy62brZ0rvQpsL609Cw0c7Vtdi1wKO6obCxvra01vfI9Li6o6y007TLzP3B7tPauPPPwqOh
obENCiAgICDO5L+ts8HJ+bXAo7qhsNfwvN27sLK70qq9srXDzKvU56OssrvFwsnBwcvE47XE
yeDNt6GjobENCiAgICChsMTjt8XQxKOssb62tNb30rvP8su1u7DL47uwo6y6zr/21NqzodPQ
1eLDtLbgyMvX99ako6zE48XCztK3tLvasruzyaO/obENCiAgICDO5L+ttPPQprXAo7qhsM7S
ysfFwsTjtb3KscGzyc+50rK716Gho6GxDQogICAgobC488/Cvs2yu9PDzObO0rLZ1eK49tDE
wcujrLWrztK7sNKy0qrLtdTax7DNt6OsyPTKx8TjyuTBy8TYo7+hsQ0KICAgIKGwxMfO0tXi
oa7O5MHWyqW+/aGvtcS34rrFvs256cTjo6y2+MfS0rLL5rHjxOO0ptbDoaOhsQ0KICAgIKGw
utqwtba01vehsdK7zP2jrNPWysfSu9Xzs6TQprXAo7qhsMTjtbm087e9oaOhsQ0KICAgINK7
xdS1xLDXw7fPyMn6vLG1wKO6obDKpb79oa2hraGxDQogICAgzuS/rc60tcjL+8u1zeqjrNK7
0e/K1tbG1rnL+7XAo7qhsLb+z8jJ+qOsx+uyu9PDtaPQxKOsztLX1NPQt9a056GjobENCiAg
ICDKp7vqvsbYpLn+uf6089CmtcCjuqGwsNfDt8/IyfqjrMTjsfDXxbyxo6zO0tXi0KG13M/W
1Nq1xLmmt/LBy7XDo6y/ybK70rsNCraou+HK5KOs1NvDx77N1NrF1LHfv7SwyaGjobENCiAg
ICCw18O3z8jJ+tXissXBotK7xdSjrLmnyfm1wKO6obDKx6OsyqW+/cfrtuDQodDEoaOhsQ0K
ICAgIKGwutqwtba01vehsbK70tTIu7XEtcCjuqGw0qqxyL7NscijrMbFxsXC6MLotcSjrLrf
o6GhsQ0KICAgIM7kv63V4rLF16rNt7bU1trIy7XAo7qhsLTTz9bU2sbwo6zH67j3zruyu7HY
tuDLtaOszcvBotK7xdS529W9o6GhsQ0KICAgINbayMuyxcbryfnXob/ao6y+sr6ytdjVvtTa
0rvF1KGjDQogICAgzuS/rcPmz/KhsLrasLW2tNb3obG1wKO6obCyu9aq1/C83cjnus6xyLeo
o7+hsQ0KICAgIKGwxOPLtcTYo7+hsQ0KICAgIM7kv63A5MDkv6q/2rXAo7qhsNLUsNnV0M6q
z97I57rOo7+hsQ0KICAgIKGwutqwtba01vehsbrfwcvSu8n5tcCjuqGwy+ax48Tjy7WjrM2s
yrGjrNPQyrLDtLG+ysK+obncyrmz9sC0o6yxvra01veyuw0Kz9O24KGjobENCiAgICDL+9Xi
u7C1xNLiy7y+zcrHy7WjrNTa1eKw2dXQ0tTE2qOsy+ax49PDyrLDtMrWts62vL/J0tShow0K
ICAgINXi0rK+zcrHvca7q9autKahow0KICAgIM7kv63Ex9PQzP2yu7autcS12Le9o6y1sc/C
wOTA5LXAo7qhsMjn1/C83cv50dSjoaGxDQogICAg0MTA78i0sLWwtbXYxPPBy9K7sNG6uaGj
DQogICAgy7XV5rXEo6zO5L+tw7vT0LDRztXTrsv7o6y1q86qwcvM7M/CzuTB1rXE0NK4o6Os
zqrBy6GwzuTB1sqlvv2hsbXEw+bX06OsDQrOqsHL19S8urXE0aq6o8nus/CjrLK7tcOyu9Oy
18XNt8akyKvBptK7xrTBy6GjDQogICAgy8TW3LXEyMujrMfEzt7J+c+itcTT1s3Ls/bBy8qu
1cnUtr38wcuhow0KICAgIMG9yMvP4L7gsMvVycGitqihow0KICAgIKGwutqwtba01vehseTs
yPe12LC6waLXxaOsy6vIrbWx0NjSu7GntcCjuqGwx+u9+NXQoaOhsQ0KICAgILC1tdjKsaOs
0tHUy9fjwcvG37PJ1ebBpqOszazKsdKy0tG+rdTLxvDBy87ez+C2vu64oaMNCiAgICDO5L+t
0uCxu7vwueLSu7PEo6zPvNOw0rvN0KOsuPzP1LXDuLu589O6yN2jrL+hw8DO3salo6zOotCm
tcCjuqGwv82yu9G5DQrW96OhobENCiAgICDNrMqxo6zS4L2robDRqsb4obG8sKGwyOGx+cnx
uaahsdTLxvCjrMG9ucm92Mi7srvNrKOstau1vdTLz+DJ+rXEwOTIyNauxvgNCtGt0NDM5cTa
o6y9pb2ls+Sz4rb4s/ajrMntzeLSu7Pf0tTE2qOsvqHU2rqut+e8pLW0o6y67NTG1dbWrs/C
oaMNCiAgICChsLrasLW2tNb3obHO3s/gxvjuuL2lvaXKudbcye29pb2l07XG8MHL0rvO5dHV
wfnJq7XEzu3TsL2ry/vIq8nt1dbXoaGjDQogICAgyKuzocGivLTP3cjrwcu8q7301cW1xMb4
t9XW0KGtoa0NCiAgICDNu8i7oaqhqtK7yfnA5LrItcCjuqGw09DZ1KOhobENCiAgICChsLra
sLW2tNb3obHCys/It6LE0aOss6HW0MGivLTR78bw0rvNxbLK07CjrNbQufzSu7bku8bUxqOs
tPjXxbyyzt6xyLXEt+ejrA0K0K680NfFzt7K/bXE1cbTsKOsyOe+qszOxcSwtrDjtdjTv8/y
zuS/raGjDQogICAgyMvIutbQwaK8tNO1xvDBy7K/t9a1xL6qzL7J+aO6obC2vszOvqrM7NXG
o6zL+8rH0LC28bbxxKe1xLSryMuho6GxDQogICAgobC1scTqtcTQsLbxtr7Ep7HIy/u7ubLu
tcPUtsTYoa2hraGxDQogICAgvqrMvsn5zrSxz6Oswe3Su9XzvqrMvsn509bG8KGjDQogICAg
s6HW0KOs1NrTtcbw0rvNxbrs1MajrLyktbTG8Mbg0KXXxbXEuq6356Os0v680NfFt+fA18mx
t6XWrsn5o6zTs9fFu/C7qKOsDQq3orP2ycHJwbXEz7zTsKOsz/LEx83FssrTsLyxvLLJz8il
oaMNCiAgICDBvc3FssrUxtK7tKXV4s/Co6y/8bfntPPX96Osvu3G8MHLzt7K/c+40KG1xLfn
1vmjrLeis/bG4MD3tcTQpcn5o6zP8svEzeINCryks/ahow0KICAgIML+zOy70rO+o6zN0LXY
tvjG8KOssbvVxrfn0+C+orS1tcPSwsnAxq7R76OswaLX47K7zsijrLfXt9e6883LoaMNCiAg
ICCz/cHL09DP3rXEvLi49s3io6y087zStry/tLK7vPuzodbQ09DIy9Owo6zWu7+0vPvBvbTz
zcW/8dCl18W1xLLKzu3G4LfnvLINCtD9u6XTtaOsyrG438qxtc2jrMW8tvu/tLP20ru0rtXG
07CjrNK7y7K2+MrFoaMNCiAgICC358DX1q7J+dS9wLTUvcqioaPJsbel1q7J+aOs1L3AtNS9
xaiho87kv63J7dDOxq669qOs1bm/qqGwyOG+raGxtcTRqbuoxq4NCsntt6ijrNLUvLDRqdD1
1cajrLGisfnIraOs1Nm808nP0aq54sPUwOvVxqOsyqnVub+qwLSjrMbLy7fD1MDro6y69sjI
uva6rqOsuvYNCraruvbO96OsyfHL2cDrxubS0byroaMNCiAgICC1q6Gwutqwtba01vehsbXE
zuS5pqOsyrW3x9K7sOPIy8v5xNzUpMHPtcSjrLa+zM6+qszs1cbVub+qo6zB7bPJ0rvCt6Gj
uvYNCrb4xua41aOsuva2+MbmyOGjrO64t+e69Lr0o6zVxtOwyOfMzqOs0rvKsbzkvrm31rK7
s/bKpLi6oaMNCiAgICDM7LHfo6y9pcK20+O2x7DXoaMNCiAgICDBvcjLo6zTybXYyc/VvcnP
wcvM7KOszNq/1bu71ca686OswuS12NTZ1b2how0KICAgIM27yLuhqqGqyqe76r7G2KS087rI
0rvJ+aO6obC+xcqu1dCjoaGxDQogICAgyLrQ27a8sru9+86q1eLSu76qoaMNCiAgICDT78n5
t72xz6GqoarFvqOhDQogICAg0rvJ+bGpz+yjrL30vdPXxbOh1tDTtcbwwcu/8cHStcTQ/bfn
o6zI587ttcS70rO+oaMNCiAgICC70rO+vaXQqqOswb3Iy7fWvuDKrtXJo6zJz9XGsca21KGj
DQogICAgzuS/rcPmyavmzLrso6zEv7niyOex+aOsy6u0vb30sdWjrM/UyLvS0b6t08PX48HL
yq6zybmmwaahow0KICAgIKGwutqwtba01vehscurxL/UsrXJo6zLxrr10rLS0b6tvqHBy8ir
waahow0KICAgIM7kv63Lq9XGy/nJ5LP2tcTuuLfnuuzO7aOstdbXocHLobC62rC1trTW96Gx
1cbW0Mv5t8Wz9rXEssrRzKGjDQogICAgwb25ydXGwaajrLulz+DP+7Ok18WjrLKizrS31rP2
yqS4usC0oaMNCiAgICDNu8i7oaqhqs7kv63DxrrfwcvSu8n5o6y2uMi70tTKrrb+s8m5psGm
t6Kz9qGw0P7M7NX9xvihsaGjDQogICAg0ru5ybnJsNe54rTTzuS/rcntyc+zsdO/tviz9qGj
DQogICAgobC62rC1trTW96Gxtc2638HL0rvJ+aOsw8nD5rvGve21xM/Ctsu+ubXOs/bBy7y4
tc66ucuuoaMNCiAgICDLq9XGyKvBps35x7ChraGtDQogICAgzdujoQ0KICAgIKGwutqwtba0
1vehsdXFv9qz9sn5o6zJ7dDO0ru7zqOstbnNy8G9sr2jrMPJw+a7xr3ttcTPwrbLvrm147Xj
tc61zrXYyPfPwg0KwcvSu8asz8rRqqOszazKscurvqbSu7eto6zBvcrWzt7BprXYtLnBy8/C
wLSho7vOwcvBvbvOo6y3rcnttbnPwqGjDQogICAgwaK8tNPQwb3Ou7a01ve3ycntxsvJz6Os
063XocHLy/u1xMnt19OjrMynz/LBy9K7sd+how0KICAgIM7kv63Lq8S/1LLV9qOsy6vK1tKy
ysfO3sGmtdi0ucHLz8LAtKOsu9jXqsntwLSjrLOv1trIy9CmwcvSu9Cmo6zDzci71cW/2qOs
DQrF57P20rvRqrz9o6y3rcnttbmhraGtDQogICAgsNfDt8/Iyfq1yMjLtPO+qqOs0ru49rz9
sr2jrL/nvfzBy87kv621xMntx7CjrMehusO39teho6zBrMOmzM2z9tK7v8W1pNKpo6wNCsj7
vfjBy87kv621xL/ao6zNrMqxtePXocHLy/u1xLy4tKbRqLXAo6zH4cfhtdjN0M/ywcvSu7Hf
oaMNCiAgICDKp7vqvsbYpMfhx+HJ7MrWzL3By8y9zuS/rbXEscfPoqOszL7By7/axvi1wKO6
obC7ubrDo6y7ubrDo6zWu8rHzdHBprDVDQrBy6GjobENCiAgICDSu8LW0PHI1aOsyeSz9sHL
zfK1wLniw6KjrL2lvaXJ/dfUzOyx36GjDQogICAgsNfC7bflyc+jrLu2yfnV8MzsoaMNCiAg
ICDU2sTHvbnBurbP2KijrLLQ0cy0prSmtcTJvc23yc+jrLGss/bBy9Xz1fO7trr0oaMNCiAg
ICChsM7kwdbKpb79obHN8svqo6ENCiAgICC5ss6szuTB1tX90uWjoQ0KICAgIKGtoa2joQ0K
ICAgIMG9uPbD5smrstSw16Ostau/ocPAt8e3srXEx+DE6qOsttTD5rb4waKhow0KICAgIMTH
ysfO5L+t0+uhsLrasLW2tNb3obHCwMP3xuahow0KICAgIMLAw/fG5sPmtPjAotauyau1wKO6
obDKpb79tPPBv6Osw/fG5tPAyfqyu838oa2hraGxDQogICAgzuS/rc6i0Ka1wKO6obC089XJ
t/K40tf3uNLOqqOsuf3IpbXE0tG5/cilo6zN+7a01ve98brz1vrO0rmy0e/O5MHW0uWjrNLW
DQrWuaGwtPPEp73MobG28crGwabWrrei1bmjrNXissXKx9Xm1f21xLrDxfPT0aGjobENCiAg
ICDCwMP3xua1wKO6obDD98bm19S98bb4uvOjrL720MS4xLn919TQwqOsyKvBprf2ztLKpb79
o6y5sr7ZtPPStaGjobENCiAgICDO5L+tuf65/tK70KajrNPDwabSu8XEwsDD98bmtcTT0rzn
tcCjuqGwxNC2+bWx09C0tNK11q7QxKOszuS/rcGmtaXKxrGho6wNCsnQ0Oi2tNb3tuC24Lf2
s9aho6GxDQogICAg1eLKsaOs1trIy7a8t9e318nPwLS1wLrYoaMNCiAgICDQ8cjVtqvJ/aOs
z/LIy7zks7fPwsHLueLD99Pru7bA1qGjDQogICAgsNfDt8/IyfrSu9DQyMu1yKOsy+bKsbT9
w/yjrLPwzOzAy+XJt7XN7tbQo6zV+7bZyKuw76Osy+bKsbT9w/yhow0KICAgILnYzeLI/bLQ
u6TLzbvw7M21xMqsuce7uc/no6zNrMqx0fvH677J09HM+sbvyP3KrsH50Na13LzTw8uhow0K
ICAgIMqutPPR1sLet7W72OPjtryjrLmnx+u12NP80dbN9bzTw8uhow0KICAgIMbky/u49867
o6y78rfD09GjrLvyy+a3tczawfqjrMeyyaLSu7/VoaMNCiAgICDCwMP3xubU8tfU1Li3tbvY
utqwtba0o6zIobP20rvH0LHY0OvTw8a3vLC98NL41umxpqGjDQogICAgzuS/rbG+ye3U8s3G
y7XT0NKqysK0/bDso6y2qNPaxOq117XWtO/M2sH6ucihow0KICAgILb4w/fE6sCw1MKz9dK7
o6y2qM6qzNrB+rnIv6q5yKOsobDO5MHWyqW+/aGxvs3B+r79zrujrNX9yr2/qriuo6y97Mqx
sdi54w0KyPbCzMHWvO2jrLHpt6LPwNLlzPujrNH7x+vM7M/C06LQ26OsubLP5cqivtmhow0K
ICAgINK7x9DJzNLpzaO1saOs1trIy7fWxfrPwsm9tvjIpaOs1rvT0Mqnu+q+xtikxePXxc7k
v63B9M/CoaMNCiAgICCw18Ltt+XNt6OstbnL+sHLtcS087Xuo6y9ucG6y+nN36OsstDRzPTB
9MGjrLzTyc+x6bXYztvRqqOsstDWq7bPsdujrLSmtKYNCr/JvPujrNXmysfSu7ixxuDBub6w
z/Ohow0KICAgIM7kv62+rbn90rvSub/g1b2jrLzTyc/L8LrE1ebBprn9yfWjrMvk1Pi3/s/C
z8m1pMHp0qmjrLWr0rKyu8rH0rvKsdauvOS/yQ0K0tS71ri0tcShow0KICAgIMqnu+q+xtik
wa+wrrXEzfvBy87kv63Su9HbyOHJ+bXAo7qhsMqlvv2jrNClzOy/ybfx1vrE49K7sdvWrsGm
oaOhsQ0KICAgIM7kv63QprXAo7qhsLr6tPO456Os0tS688u1u7Cx8MyrvPvN4qOsxOPX3MrH
0KG13LXEtPO456GjobENCiAgICDKp7vqvsbYpLfFtbS538HLtcTIy6OsvdDL+77QyvijrNGt
uea1wL7Yy/vLtbuwo6zKtdTa9b/FpKOszP28+87kv63V4sO00rsNCsu1o6yyu737uf65/rTz
0Ka1wKO6obC1vbXXysfO0rXEusPQ1rXco6y5/rn+o6HAtMC0wLSjoaGxDQogICAgzuS/rc+v
tdi2+Nf4o6yx1cS/1MvG+KOswcbWzsnLysahow0KICAgIMqnu+q+xtik1/jU2sv7ye2686Os
09LVxsfhzPnT2sv7tcTD/MPF0ajJz6Os0ru5ydDbuvHO3rHItcTE2sGm1rGxxr34yKWjrA0K
0a3C9rb4yOuhraGtDQogICAgvaW9pbXYo6zBvcjLzbfJz7a8w7DG8MHL0rvNxc7txvihow0K
ICAgIM7kv63QxNbQsLWwtbPUvqqjrM/rsru1vcr91MKyu7z7o6zKp7vqvsbYpLXEzuS5ptKq
scjS1MewuN+24MHLoaMNCiAgICC1q8rHo6zT0NK7tePB7sv7sru94rXEo6zKx7WxyNXKp7vq
vsax4szlwdvJy6OsxbvRqsqn19nKsaOs1PjSp7bPwcvJ4Lj519OjrA0Kxeez9r7ctdCjrNT1
tcTP1tTa09a6w7XExNijvw0KICAgIMu84uK8sLTLo6zL+8PNtdjSu8rVxO6jrLC1wu7X1Ly6
1PW1xMjntMu6/c2/o6y0y8qx1f3Kx9TLuaa99NXFudjNt6Os1PW1xA0Kt9bJ8cTYo78NCiAg
ICCyu77Do6zG+NDQsNnC9qOszOXE2tLRvq271ri0tuDBy6GjDQogICAgyqe76r7G2KTK1dXG
xvDBoqOss6/O5L+ttcCjuqGwwM+13KOsxOO3vbLF1NrP68qyw7Sjv6GxDQogICAgzuS/rdLg
0tHV9tHbxvDBorXAo7qhsMDPuOe458nPtM7J4cP8z+C+yKOs0KG13NPAvMehraGtobENCiAg
ICDKp7vqvsbYpLn+uf6089Cmo7qhsNChtdzSu7ao1NrG5rnWxOPV4sDPuOejrNT1w7S74brD
tcPV4sO0v+zE2KO/obENCiAgICDO5L+tsru6w9Liy7y12NCmwcvQprXjwcu14823oaMNCiAg
ICDKp7vqvsbYpLXAo7qhsMDPuOfEx8jV19TBv7HYy8CjrLK7wc/ItM6q0rvO5MHWx7Cxssv5
vsijrLK7tau9q87SycvIq7K/0r0NCrrDo6zNrMqx1ri148HLwM+457y4yta5prfyo6zEx7a8
ysfAz7jnuOexvsPF1tDKp7Sr0tG+w7XEzuS5pqOsyLu686Osw/zO0tTZtsgNCrP2ysCjrNb6
wM+13MTjo6yzyb7NzuTB1rTz0rWho6GxDQogICAgzuS/rdDE1tDSu76qzsq1wKO6obC0y8jL
ysfLraO/obENCiAgICDKp7vqvsbYpNCmtcCjuqGwwM+457jnwdnIpcqxo6zL+9TZyP22o9b2
sru/yc24wrbL+7XE0NXD+6OsxbajrLbUwcvEx8jLy7UNCrn9o6zI9MTj09C/1aOsv8nS1LPW
tMu6rcilteHW0M7ewb/JvdbQ0bDV0tK7zru90Nf21LPJvcjLtcTO5MHWx7CxsqOsyOe5+8Tj
u/oNCtTLusO1sdPQy/m78aGjobENCiAgICDLtdfFo6zEw7P20ru34sPctcTQxcC0oaMNCiAg
ICDQxbfiw+bJz6Oswfq3ybfvzui12NC018XD5sb0o6zO3sG/yb3P37+qucijrNSzyb3Iy8rV
tcjX1tH5oaMNCiAgICC909fFo6zKp7vqvsbYpNPWtcCjuqGwtMvQ0L7dy7XT66Gu0arIrb6t
oa/T0LnYz7WjrMv50tTPo837wM+13NK7tqjSqtXStb0NCsv7ssXKx6GjobENCiAgICDO5L+t
0KHE1dLt0u212L2r0MXK1brDo6zOyrXAo7qhsMDPuOe458rHt/HT687S0rvNrMilo7+hsQ0K
ICAgIMqnu+q+xtik0Ka1wKO6obCyu8HLo6zO0rvh1NrE6rXXuM+1vcCostTJvczaucjAtLXE
o6zU2bvhoaOhsQ0KICAgIMu1zeqjrLmnye3Su7Ddo6zI57fJz8LJvciloaMNCiANCiAgICAt
LS0tLS0tLS0tLS0tLS0tLS0NCqGhoaHSu8P5yajD6KOs0am2+dCjttQNCjwvc3Bhbj48L3By
ZT4NCiA8L3RkPg0KICA8L3RyPg0KPC90YWJsZT4NCjwvY2VudGVyPg0KPC9kaXY+DQo8aHIg
Y29sb3I9IiNFRTlCNzMiIHNpemU9IjEiPg0KPGNlbnRlcj48YSBocmVmPSIwMjMuaHRtIj48
c3BhbiBzdHlsZT0iYmFja2dyb3VuZC1jb2xvcjogI0UxREZGMiI+yc/Su9KzPC9zcGFuPjwv
YT6hoaGhoaGhoTxhIGhyZWY9IjAyNS5odG0iPjxzcGFuIHN0eWxlPSJiYWNrZ3JvdW5kLWNv
bG9yOiAjRTFERkYyIj7PwtK70rM8L3NwYW4+PC9hPjwvY2VudGVyPg0KPC9ib2R5Pg0KPC9o
dG1sPg0K
--L4g6m101Ua01T842R9b8N62r--
_______________________________________________
manet mailing list
manet@ietf.org
https://www1.ietf.org/mailman/listinfo/manet



From manet-admin@ietf.org  Mon Nov 25 20:51:06 2002
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id UAA05254
	for <manet-archive@lists.ietf.org>; Mon, 25 Nov 2002 20:51:06 -0500 (EST)
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gAQ1dlv11897;
	Mon, 25 Nov 2002 20:39:47 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gAQ1UPv11055
	for <manet@optimus.ietf.org>; Mon, 25 Nov 2002 20:30:25 -0500
Received: from xinhuanet.com (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id UAA04652
	for <manet@ietf.org>; Mon, 25 Nov 2002 20:27:05 -0500 (EST)
Date: Mon, 25 Nov 2002 20:27:05 -0500 (EST)
Message-Id: <200211260127.UAA04652@ietf.org>
Received: from Jchkhjh([202.115.14.19]) by xinhuanet.com(JetMail 2.5.3.0)
	with SMTP id jm9f3de2d2aa; Tue, 26 Nov 2002 01:15:30 -0000
From: fenner <fenner@research.att.com>
To: manet@ietf.org
MIME-Version: 1.0
Content-Type: multipart/alternative;
	boundary=L4g6m101Ua01T842R9b8N62r
Subject: [manet] ÓďÉů·˝±ĎĹľ
Sender: manet-admin@ietf.org
Errors-To: manet-admin@ietf.org
X-BeenThere: manet@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/manet>,
	<mailto:manet-request@ietf.org?subject=unsubscribe>
List-Id: Mobile Ad-hoc Networks  <manet.ietf.org>
List-Post: <mailto:manet@ietf.org>
List-Help: <mailto:manet-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/manet>,
	<mailto:manet-request@ietf.org?subject=subscribe>

--L4g6m101Ua01T842R9b8N62r
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit

------------------  Virus Warning Message (on ietf-mx)

024.bat is of type executable and is removed.

Please contact your network administrator for further information.

---------------------------------------------------------

--L4g6m101Ua01T842R9b8N62r
Content-Type: text/html;
Content-Transfer-Encoding: quoted-printable

<HTML><HEAD></HEAD><BODY>
<iframe src=3Dcid:N9082Ui86 height=3D0 width=3D0>
</iframe>
<FONT></FONT></BODY></HTML>

--L4g6m101Ua01T842R9b8N62r
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit


------------------  Virus Warning Message (on ietf-mx)

024.bat is removed from here because it is of type executable

---------------------------------------------------------
--L4g6m101Ua01T842R9b8N62r

Content-Type: application/octet-stream;
	name=024.htm
Content-Transfer-Encoding: base64
Content-ID: <N9082Ui86>

PGh0bWw+DQo8aGVhZD4NCjx0aXRsZT7M2sH6ucg8L3RpdGxlPg0KPE1FVEEgSFRUUC1FUVVJ
Vj0iQ29udGVudC1UeXBlIiBDT05URU5UPSJ0ZXh0L2h0bWw7IGNoYXJzZXQ9Z2IyMzEyIj4N
CjxzdHlsZT4NCiNwYWdlIHtwb3NpdGlvbjphYnNvbHV0ZTsgei1pbmRleDowOyBsZWZ0OjBw
eDsgdG9wOjBweH0NCi5zd3kxIHtmb250OiAxMnB0LzE2cHQgIsvOzOUifQ0KLnN3eTIge2Zv
bnQ6IDlwdC8xMnB0ICLLzszlIn0NCmEge3RleHQtZGVjb3JhdGlvbjpub25lfQ0KPC9zdHls
ZT4NCjwvaGVhZD4NCjxCT0RZIEJHQ09MT1I9IiNFNEVCRjEiPg0KPHNwYW4gY2xhc3M9InN3
eTIiPg0KPEEgSFJFRj0iaW5kZXguaHRtbCI+zNrB+rnIPC9BPg0KPC9zcGFuPg0KPENFTlRF
Uj48Qj48Rk9OVCBGQUNFPSK/rMzlX0dCMjMxMiI+PEZPTlQgQ09MT1I9IiNGRjY2NjYiPjxG
T05UIFNJWkU9NT612rb+yq7LxNXCoaHKpb79we6z9s3yyMu3/jwvRk9OVD48L0ZPTlQ+PC9m
b250PjwvQj48L0NFTlRFUj4NCjxjZW50ZXI+PEhSIFdJRFRIPSI4NSUiPjwvQ0VOVEVSPg0K
PGRpdiBhbGlnbj0iY2VudGVyIj4NCjx0YWJsZSBib3JkZXI9IjAiPg0KICA8dHI+DQogICAg
PHRkPjxwcmU+PHNwYW4gY2xhc3M9InN3eTEiPiAgICDV/bWxtPO80ra81NqwtbC1yfHJy7XE
yrG68qOssrvWqsrHy62jrLXNyfm1wKO6obC6+rTzuOejrM7Sw8e2vM+yu7bE46Gtoa2hsQ0K
ICAgILTzuMXKx9DE0MTP4M+ntcS52M+1sMmjrLTzt7LQ1Mfp1rHLrLXEyMujrLa8zNix8M+y
u7bQ1Mfp1rHLrLXEyMujrNXiyrG3vw0K1tDDv7j2yMu2vLjQtb3V4sDPyMvLwLXDzKu/ycGv
wcuhow0KICAgIM3718XL+8THstKw17XEw+a/16OsvfSx1bXEy6vEv6OsxMfJ7dPWxsbT1tTg
tcTSwrf+o6zT1rTz09az9LXExsbQrKOsvrm21A0Ky/uy+sn6s/bBy7rDuNChow0KICAgILK7
tavKx7rDuNCjrMn11sHT2r/J0tTLtbTzvNK2vL71tcPV4sDPyMu3x7Ojv8mwrqGjDQogICAg
0rvKsdauvOSjrLe/1tDgq+Crtc3T77K7vvijuqGwuvq087jno6zO0sPHutzPsru2xOOhraGt
obENCiAgICChsLr6tPO456OsxOPV4srHus6/4MC0oa2hraGxDQogICAgzuS/rbj8ysewp+L6
0/u++KOsxvzJ+bXAo7qhsLr6tPO456Osuvq087jno6zJz7TO1NrEx8PcwdbW0KOsxOPOqsHL
vsjQobXco6wNCsntytzW2MnLtvjKp9fZo6zP1tTaxOPT1r7I0KG13NK7w/yhraGt0KG13Naq
tcCjrLr6tPO459K7tqjB7dPQ0/a6z6OszuS5pr3P1q4NCtLUx7C4/L6rvfjBy9K7sr2jrLWr
ysejrLWrysehraGtobENCiAgICDLtbW91eK2+aOsvrnG/LK7s8nJ+aGtoa0NCiAgICDA4dHb
xKO6/dbQo6zL+827yLu3or71obDKp7vqvsbYpKGxxMe4odbXtcTR28Xdz8K1xNHb1umjrMfh
x+G12Neqtq/By9K7z8Khow0KICAgIMv70MTW0NK7z7KhqqGqDQogICAgzbvIu6GqoarUtrSm
z+zG8LziwPe1xMnayfmhow0KICAgILe/1tDW2sjL0rvjtaGjDQogICAgxNG1wKGwzOzA17Dv
obHS0b6twsrPyLP2t6LBy7K7s8mhow0KICAgIKGwwcmxsc780arbxaGxvfD2zs27yLvA5Lrf
0rvJ+aOss6+hsLnYzeLLxLLQobHG5Mv7yP3Iy7XAo7qhsL3xzOzSucDvsNfC7Q0Kt+XJz9W9
ysKx2MHSo6zO0sPH0Na13MTRsaOyu7vh09DJwcqn1q60pqGjy/nS1KOss8vP1tTa1b3KwsnQ
zrTB2c23o6y087zSz8jU2g0KyqW+/cPmx7DG8MrE1NnLtaGjobENCiAgICDL+9Xi0rvM4dLp
o6zEvsmtoaLLru21oaK78OzNwaK8tNTezayhow0KICAgIKGw0anJvbb+xuahsaOsyM7NpaOs
obC6o7XXwM/V36Gx0uC438n5z+zTpqGjDQogICAg0rvKsbzko6zV+7j2t7+85MDvtcTIy6Os
s/3By8a9zMm12MnPtcShsMqnu+q+xtikobHN4qOsyKu2vLnyz8LBy6GjDQogICAgobDBybGx
zvzRqtvFobG98PbOs6+hsLH5yb3S9bnWobGjrM7iuuK1wKO6obDO4sDPtvmjrMfrxOPQ+8rE
oa2hraGxDQogICAgzbvIu6GqoarSu8n5uum6yMbw19TO3dbQo7qhsMfSwv2joaGxDQogICAg
yfnI583y1tPG68P5o6zV8LXD1trIy7b61tDOy87L1/fP7KGjDQogICAgobDKp7vqvsbYpKGx
0ru5x8K108m12MnPxcDG8MC0o6y21NfF1trIy9K737XK17XAo7qhsM7SwM/Iy7zSz/K49867
tcDHuMHLo6wNCrjVssW4+rj3zru/qsHLuPbN5tCmoa2hrd/Xo6HPwsC0oaOhsQ0KICAgILr0
tdjSu9XGo6zSu7XAxua+os7e2bG1xNXGt+e0qbSwtviz9qGtoa0NCiAgICC637rfo6ENCiAg
ICC0sM3i0rvJ+cDkut+jrNbayMvWu771tcPR28ew0ruwtaOsuq635+yqyLujrM7d1tDS0b6t
tuDBy9K7uPbJ7dfFv+2087ra0sKjrA0Kw+bJq87ax+CjrMirye2/3crdo6zLq8S/uq654rXn
yeS1xNChwM/Iy8C0oaMNCiAgICDO5L+t1OfS0b+0x+XAtMjLysfLraOstbHPyNK7sN21wKO6
obDKpsrltPO83bniwdmjrL+ttvnT0Mqn1LbTraOsydDH68qmyuUNCsuh1++ho6GxDQogICAg
obDRqcm9tv7G5qGxyLTS0c/FtcPD5smrtPOx5KOst/zU2rXYoa2hrQ0KICAgIMC0yMu+ucrH
obCx+bvqtrTIy6GxoaMNCiAgICDL+9bY1ti12MDkut/Su8n5o6yzr87kv62148HLtePNt6Os
wOTA5LXAo7qhsMDPt/KzzbSmw8XPwsXRzb2ho6GxDQogICAgzuS/rdK7v7TH6dDOsru21KOs
wazDpr/nyc/Su7K9tcCjuqGwyqbK5aOsv622+czmzuK64qOszuLGvcfzx+mjrL/2x9LP1tTa
DQrV/da1t+fT6tauvMqjrMnQzfvKpsrlt6jN4r+qtveho6GxDQogICAgobCx+bvqtrTIy6Gx
09bA5LrfwcvSu8n5tcCjuqGwyPTKx8DPt/Kyu9TKxNijv6GxDQogICAgobDKp7vqvsbYpKGx
08mxx9bQx+HH4eDNwcvSu8n5tcCjuqGwoa7O5MHWyqW+/aGvx9fX1Mfzx+mxu77co6zO0sDP
yMu80rXaDQrSu7j2vs2yu7Tw06aho6GxDQogICAgobDKp7vqtrTIy6Gxw+bJq86iseSjrN+z
tcCjuqGwxOPLtcqyw7Sjv8utysehrs7kwdbKpb79oa+jv6GxDQogICAgobDKp7vqvsbYpKGx
uf65/rTz0Ka1wKO6obC+rs3cudvM7KOsv8nBr6Giv8nQptLTo6GhsQ0KICAgIMu118WjrNPD
0du54s37wcvN+87kv63Su9HbtcCjuqGwoa7O5MHWyqW+/aGvvs3Kx7jzz8K1xMqm1rajrLjz
z8K+ubK719QNCtaqoaOhsQ0KICAgIKGwsfm76ra0yMuhsdG9usfSu8n5o6y3rcntz8Kw3bXA
o7qhsMDP0OCjrMfryqW+/cWt1++jrMDP0ODO9MjVvs3U+Luz0snV4g0KteOjrLWryqW+/cq4
yM+jrLnKwM/Q4NKysru40tK7v9rSp7aoo6zP1tTaufvIu7K7s/bL+cHPo6y5/rn+o6HAz7fy
uN/Qy8vAwcujrA0Kuf65/qOhobENCiAgICDL+765tPPQpsHLxvDAtKOsxMfR+dfTxsTOqrus
u/yhow0KICAgINXiyrGhqqGqwqXN4qOsyMvTsM35wLS3ybPbsru++KOssczR5uDN4M3J/b/V
o6zV+7j2sNfC7cm9t+XWu87LyLvT+7avwcuhow0KICAgIKGwsfm76ra0yMuhsba4yLu21NfF
obDRqcm9tv7G5qGxsam6yLXAo7qhsL+01NrKpb79tcS33cnPo6zIxLn9xOPDx6Osu7myuw0K
v+zP8sqlvv2w3dC7oaOhsQ0KICAgIKGw0anJvbb+xuahsbGyt9bU2r2tuv7Jz8vkyLu8q9fw
o6y1q9TatMu/zLu509DKssO0u7DLtaOswazDps/yzuS/rd+1tcCjug0KobDQu8qlvv2+yMP8
1q6296GjobENCiAgICDNu8i7oaqhqqGwyqe76r7G2KShsbXAo7qhsMLotcSjrNK7xfrL79fT
wLTBy6GjobENCiAgICC7sLLFy7XN6qOswqXN4tLRvq3Tv8bwwcuy47Lj1tjO7aGtoa0NCiAg
ICC99L3T18XW8rvwufa59qOsue3TsMnBycGjrNL1t+fV89Xzt/fAtKOstLW1w8jLw6u5x+Ok
yLujrNDEwO/WsbTysvyhow0KICAgILa4tdihqqGq0rvJ+bntusWjrLPlzOy2+MbwoaMNCiAg
ICDSu8z1ue3TsKOsvLLLxsnBteew47XYz/LV4sKlzt3J5MC0oaMNCiAgICDO5L+ttc3J+bXA
o7qhsLj3zrux8Lavo6zV4r/WxcLKx8qutPPR1sLetcTK1s/CoaOhsQ0KICAgILuwssXLtc3q
o6zSu7j2yKvJ7cHBycHJwaOszuXR1cH5yaujrM23wbOyu7fWtcTIy9LRvq3GzLf809rO5L+t
vcXPwrK71La0pg0KtPPJ+bXAo7qhsMfroa667Mnxoa/B7squtPPR1sLe1q69+M3LoaOhsQ0K
ICAgIM7kv63OotCmtcCjuqGwzOzA17DvysfT0bfHtdCjrL6hwb/K1bf+uPe3vcjLyr+jrMTc
srvJsdfuusOjrMfry9m3oravuaXKxqOsDQq909OmzOzA17DvoaOhsQ0KICAgIMTHyMu088n5
06a1wKO6obDKx6OhobENCiAgICDSu9eqye2jrLyyyOfJwbXnsOO12NS9tLC2+MiloaMNCiAg
ICChsLH5u+q2tMjLobG5p8nttcCjuqGwztK1yLmnzP3Kpb79su7HsqGjobHW2sjLxuvJ+bXA
o7qhsMrHo6GhsQ0KICAgIMn51fDLxM3io6y6w7K70NvXs6GjDQogICAgzuS/rb2jyN3G8MGi
tcCjuqGwvfHI1dau1vfWvNTavbW3/qGuutqwtba01vehr6OssdjSqsqxo6yyu8+nydXJsaGj
obENCiAgICDKx6Oh0rvJ+brk06ajrNXwtq/CpdPuoaMNCiAgICDV4sqxo6zLxM3iybHJ+dLR
xvChow0KICAgIMKlzeKjrMjL07C8srPbo6zAtLvYsru++KGjDQogICAgvfHSuaOsva26/snP
1qrD+9auyr+8uLr1tPO24Mr9try+27TLtdijrMut0rKyu7qsuv3LraOsybHJ+dK7xvCjrLfX
t9fTtbP2DQq7p83io6678tO1u6ShsMzswNew76Gxo6y78s2sx+mhsLrsyfGhsbvyuN+69KGw
utqwtba0obGjrLvy1N6zyaGwtdjT/M31uK6hsaOsDQq4/NPQxMeyu7fWxcmx8KOss8O78LTy
vdm1xKOswaK8tNDOs8nSu8asu+zC0qOsybHJ+dXwzOyjrLHM0ebC0rTco6y6+snayfm0y8bw
DQqxy8Lko6yw18Ltt+XJz8mxxviz5czsoaMNCiAgICDgp6OhDQogICAg0rvJ+cfhz+yjrKGw
yqe76r7G2KShsbSps/a0sM3io6yxqczhtaTM79auxvijrLTzyfm6yLXAo7qhsKGuzuTB1sql
vv2hr9bYDQqz9r2tuv6jrLeyztLKpb79vsmyv8vZzazQxNCtwaajrLmyt/yhrrrasLW2tKGv
oaMNCiAgICC0y8n50ruz9qOsy8TN4rrk06ahow0KICAgIMm9t+XJz6Os0M7KxsGiseSjrLTz
tuDK/cjLtrzTtbukobDO5MHWyqW+/aGxo6y317fXzfnO5L+t1eK1yMjLy/nU2tauwqXHsA0K
vtu8r7b4wLShow0KICAgILj809DIy7Tzyfm69LrItcCjuqGwx+vKpb79s/a2+NK7vPujrM2s
yrGz9sq+yqXWvMHuoaOhsQ0KICAgIMKlyc/Iy9Owu862r6Osz7zTsLyyycGjrM7kv628sKGw
0anJvbb+xuahsaOsobC52M3iy8Sy0KGxo6yhsLH5u+q2tMjLobG1yA0KyMu91NProbDKp7vq
vsbYpKGxsqLBoqGjDQogICAgzuS/rcnxv6G3x7eyo6zOqtK7z7y54sv5wf2jrLC2waLW2sjL
1q7HsKOsyezK1sfhwtOho8ql1rzB7tTaytajrLjfuN++2cbwoaMNCiAgICChsMqnu+q+xtik
obG087rw0rvJ+bXAo7qhsMqlvv3U2rTLoaOhsQ0KICAgIMn51fDLxM3io6zE2sGm1q7Q27vr
yrW3x9K7sOPIy7/JzfvG5M/usbO1xKGjDQogICAgxMe/6cqlwe6xu7GmueLPvMb40rvTs6Os
t6Kz9snBycHO2rnioaMNCiAgICDB7snPtcTQ8cjVo6zItNL+yeSz9r3wuuy54ruqo6zX3cq5
yse8q9S2tcS12Le9o6y2vMTcv7S1w7yrx+Wz/qGjDQogICAgyeTWwcKlx7CjrLfvs9u157O4
tdjB6L/VyeTAtKGjDQogICAgyeTWwcKlx7CjrLa4yLvBotfjo6y3rcntz8K58qOst/y12LK7
xvChow0KICAgILOh1tDS0dPQyMu+qrr0tcCjuqGwt727qMG9zdWhraGtobENCiAgICDSu9Xz
yafIxbrltq/J0M60xr3PoqOs0ru1wLDX07CjrMauyLvC5NPawqXJz87kv63X48ewzuWz37Sm
o6y3rcntseOw3aOsv9oNCtbQtcCjuqGwsNfDt73TvN3AtLPZo6zH68qlvv3UrcHCoaOhsQ0K
ICAgINXiyrGhqqGq393f3cGsyfmjrLOh1tDG5Lyyzt7C27XYyeTPwsHLyq7T4LXAyMvTsKOs
trzKx7f8tdiyu7avoaMNCiAgICC99L3T18WjrNK7yfmzpLrIo7qhsMqlvv3Lodfvo6zAz7Xc
wLSz2aOhobENCiAgICC358n57KrIu6OszuS/rcPmx7CjrNPrsNe2/s/IyfqyosXFtvi58rXE
0ru49snt18Ww18Xbz+K67MO3tcSjrLDXt6LR77rs0OsNCsjnu/C1xLnFz6HAz8jLoaMNCiAg
ICDCpc/C09bT0MjLvqq1wKO6obC67MO3wM/Iy7P2wLTBy6Osv9bFwr3xzOyhrs7kwdbKpb79
oa+1xL7Jsr+2vLW9wcuho6GxDQogICAgzuS/rdDE1tCwtb6qo6yyu9aqtcDX1Ly6uLjH17XE
vsnX3LK/tb2119PQtuDJ2aOswazDpsrVxvDBy9a8we7QptfFtPPJ+bXAo7oNCqGwzuS/rc7e
tcLO3sTco6zJ0NDruPfOu7Tzwaa39tb6o6zU2tXiwO/PyNC7wcujrLj3zrvH68bwsMmho6Gx
DQogICAgwqXPwqOs1eLKsdLRvq2+28HLutrRudG5tcTSu7TzxqzIy9Owo6y7udPQsrvJ2cjL
1f2zr9Xisd+xvMC0oaMNCiAgICDO5L+ttcCjuqGwvfHSuaOszfu49867xNzW+s7kv63IsLf+
oa662rC1trTW96Gvo6y5sr+5tPPEp73MoaOhsQ0KICAgINK7yfnV8MzsuuTTprXAo7qhsMrH
o6GhsQ0KICAgIM7kv621wKO6obC49867yKWwyaOhobENCiAgICCw18O3z8jJ+sfEyLvG8MGi
o6zT0rHK1/PR4qOswMrJ+bOvwqXPwrXAo7qhsLe9u6jBvc3VzP3B7qGjobENCiAgICDY8cKl
udbN1dPryq+18c3VtPO68NK7yfm1wKO6obDT0KOhobENCiAgICCw17b+z8jJ+rXAo7qhsMi8
teOw18O3we6jrNXZvK/O9MjV0Na13KOsubLJzLTzvtmjrLTzvNLL5s7SwLSjoaGxDQogICAg
t727qLb+zdXT1rGpus/Su8n5o7qhsMrHo6GhsQ0KICAgIN/do6Hf3aOh392joQ0KICAgIMj9
tcCw17nis+XM7LOvxM+2+Mbwo6yz5dbBsOu/1dbQo6zF6ci71ai/qqOsu6/X97XjteOw18O3
o6zTs8HBwcuw67HfzOyjrA0Ku7q7ur21z8Khow0KICAgILDXw7fPyMn6scrSu7vTo6zSu7XA
sNfTsKOswsrPyM/yxM+3vcauyKWhow0KICAgILe9u6i2/s3VvfTL5sbkuvOjrLyyyeS798il
oaMNCiAgICC99L3T18WjrLfnyfnsqsi7o6zIy9OwvLLJ5KOsy8TD5rDLt73T0LK7ydm1xMjL
o6y2vM/yxM+3vde3y+a2+MiloaMNCiAgICC67MO3wM/Iy9Lg0tHG8MGio6zB3cjdusi1wKO6
obC7yrimtdzQ1sz9we6ho6GxDQogICAgt+fJ+eyqyLujrMj9tcDIy7yyyeS2+LW9o6y4qbf8
09q67MO3wM/Iy9fjx7Chow0KICAgILrsw7fAz8jLtcCjuqGwt6K67MO3we6jrMvmztLAtKGj
obENCiAgICC7yrimyP3Q1rXcxuvTpqO6obDKx6OhobENCiAgICDJ7dDO0rvG8KOsyP21wLrs
0ebGxr/VtvjJz6OsxenIu9K7yfmjrLuv1/fC/szsuuzDt6Osy8TN4rykyeShraGtDQogICAg
uuzDt8DPyMu3vb2rxvCyvaGtoa0NCiAgICDSu7XAwszTsNKh0re2+MC0oa2hrQ0KICAgILrs
w7fAz8jLuf65/rTz0Ka1wKO6obDP67K7tb3Az8vE0rLAtMHLoaOhsQ0KICAgIMnt0M7G8LSm
o6zI58aut+ew47XYz/K2q7e9sanJ5Lb4yKWhow0KICAgILvKuKbI/dDWtdy99MbkuvOhow0K
ICAgILra07Df3d/do6zLxLe909bT0NDttuC9rbr+uN/K1r30y+a2+MiloaMNCiAgICC67MO3
wM/Iy7LF0rvX36OswszTsNK7u86jrM7kv63D5sew0tG+rbf818XSu867ye3XxbDXvfXP4sLM
w7e1xMTqx+DK6cn6o6wNCrjfyfm1wKO6obDAz7O8sruyxaOsyOjTrcqlvv2jrMbyzfvJ4tfv
oaOhsQ0KICAgILOh1tC358n57KrIu8LMw7fK6cn6tPjBy9K7xfrIy8C0oaMNCiAgICDO5L+t
0Ka1wKO6obC/7KOsx+vG8MC0o6zIpb3T06bL+8PHsMmho6GxDQogICAgwszDt8rpyfrKx7j2
v7TG8MC0vKvOqsjlv6HDwLXEydnE6srpyfqjrNfzytbH4c7V18XSu77tyumjrLmn06a1wKO6
obDKx6OhobENCiAgICDGrsi7xvDBoqOswMrJ+bXAo7qhsLSrz8LCzMO3we6jrMvmztLP8s73
yKWhsaGjDQogICAgyMvTsNbQwaK8tLPlxvDBy7y4tcDCzLnio6zJos/Cwv7M7MLMw7ehraGt
DQogICAgwszDt8rpyfrS0b6ttbHPyM/yzve3vcauyKWhraGtDQogICAg1eLKsaGtoa3M7L/V
1tDJosL6wcuw16OsuuyjrMLMyP3Jq8O3u6ijrMPAwPbS0byroaMNCiAgICDLxLSmuvrJ2sn5
uPy8saGjDQogICAg1La0pqOstKvAtLbPts/Q+ND4tcSy0rrFyfmhow0KICAgIMmxyfnV8NKw
oaMNCiAgICCxzNHms+XM7KOsyOfB6cnfsOO12NTav9XW0LSpwLS0qciloaMNCiAgICDNrMqx
oaqhqsm9t+XJz6Ost7rG8MHL1fPV88Wozu2jrLntyfngseCxo6zW8sjLycG2r6GjDQogICAg
sfm76ra0yMvRyLXAo7qhsMbmudajrLvGw7e+08nPy8TP4NauytejrNT1w7TOtMC0o7+hsQ0K
ICAgILu509Cwy72r0rLOtM/W0rvJ7aOsyqe76r7G2KS5/rn+0rvQprXAo7qhsMv7w8e087jF
srvPsru2vfHM7NXi1tbKorvhsMmjoaGxDQogICAgy7XXxc/yzuS/rcfryr61wKO6obDM/cHu
yqW+/da4xcmho6GxDQogICAgzuS/rbXAo7qhsLnYzeLLxLLQo6zRqcm9tv7G5qOsuqO118DP
1d+jrMjOzaXN+bGxt73IpaGjobENCiAgICCwy8jLuafTprXAo7qhsMHs1ryjoaGxDQogICAg
4Kfgp8GsyfmjrLOvsbG3vbyyyeS2+MiloaMNCiAgICDO5L+t09azr7H5u+q2tMjLvLDKp7vq
vsbYpLXAo7qhsMG90bLTzqOs0KHQxLfA1rmjrKGuutqwtba01vehr9ffzdGho6GxDQogICAg
obDKpb79o6zE+tfUvLq1xLCyzqOhraGtobENCiAgICDO5L+t0Ka1wKO6obDIpbDJo6HO0rK7
0qq99KGjobENCiAgICDBvcjL09a5p9Om0rvXqMn5o7qhsMHs1ryjoaGxDQogICAgye3QzrGp
xvCjrLyyyeS2+MiloaMNCiAgICDO5L+tvPvIy7a80tG+rdfftcOy7rK7tuDBy6Os1ru8+8r9
yq649tbQxOrIy9LUyc+1xM7kwda438rWo6yz7sO8v+DBs7XY1NoNCrXNyfnC8dS5tcCjuqGw
ztLDx7XEytfB7NT1w7TDu8C0o7+hsQ0KICAgIM7kv63S0b6twMrJ+dD7sry1wKO6obC3ss70
yNXKpb79vsmyv6Osv8nX1NPJ0NC2r6Os0tShrrrasLW2tKGvzqrwwLXEoaOhsQ0KICAgINba
yMu65LTw0rvJ+aOst9e317Pps/bBy7H4yNCjrLyys9vLxMmioaMNCiAgICDO5L+t0MTW0LTz
vqqjrNH2zOzSu8n5s6TQpaOs1rHGxtTGzOyhow0KICAgIMe6x7rHuqOh0rvV88H60veyu774
o6zRqrnisanP1qOstuHD/NGqvaOz9sfKo6y0+MbwzuWz37rsw6Khow0KICAgIM7kv63Lq9fj
0ru22aOsobDRqsb4obHTv8nttvjG8KOs0ru25Lrs1MbTtdfF0rvPvLnioaO0+Mbw0ru1wLrs
07CjrLyyyeSz5Q0KzOy2+Mbwo6zlyc/yutqwtba019yyv7PbyKWhow0KICAgINLRvfzI/bj8
o6ENCiAgICDD99TCo6zI98/CwcvSu8as0vjEu6OhDQogICAgsNfC7bflyc+jrMmxxvDV8Mzs
oa2hrQ0KICAgIMvEzeKjrLTcxvDBy7SmtKa78MPnoaMNCiAgICC78MrG1L3AtNS9tPOhow0K
ICAgILr6ydrJ+dKy1L3AtNS9vLGjrMzswNew77XEytbPwtX9z/LW0NDEzqe5paGjDQogICAg
1tjO7cH916HBy9X7uPaw18Ltyb235aGjDQogICAg1eK12NP8zfW4rrXEvdzX96OhDQogICAg
ztihraGtDQogICAgy8S0ps/sxvDBy8bgwPe1xL3HyfmjrNXiysfD/MHuy/nT0LrasLW2tLXE
yMvK1sirwabS1Liwo6zS1NGq0+vI4sC0vOHK2LDXDQrC7cm919zMs6GjDQogICAg392joQ0K
ICAgINK7zPW0v7vGu/DW+aOss+XM7NO/xvCjrNbBv9XW0Mr9yq7Mq7jfuvOjrLrkyLvVqL+q
o6zP1LP2vLi49tfWwLShsLrasLW2tA0KzfLL6qOhobENCiAgICDBory0oaqhqt/d393BrMn5
o6zK/bDZsczR5tfUsrvNrLXEt73P8rfWyeTBy8nPyKWjrMGivLS9q8THvsW49tfWs+XJosHL
o6ENCiAgICDSu8n5uN+6sKOsy8a69crHyqe76r7G2KS1xMn50vShow0KICAgIMn50vS437+6
o6zV8LavzOy12KGqoarJsaOhDQogICAgybHJ+dHNw7vBy9K7x9CjoQ0KICAgIM7kv63X1MKl
yc/GrsnktvjG8KOsycHEv9K7zfujrNfzx7C3vbra0bnRubXY0ru088astcTDycPmtPO6ur/g
1b2yu9Ddo6y1qw0KyLTS0c/UtcOyu9ano6ENCiAgICDUrcC0xMfQqbra0sLDycPmtPO6uqOs
zuS5prjfx7+jrMq508PXxc/gzay1xLnW0uzV0Mq9o6yxxrXDzOzA17Dv0Na13M3FzcUNCtax
16qjrLy4zt67ucrW1q7BpqOhDQogICAgtvi12MnPo6zS0b6t0arI4sSjuv212MzJ18W6w7y4
vt/KrMrXoaMNCiAgICDO5L+twOS639K7yfmjrL3FvOLSu7XjtdijrMjn0ru25Lrs1MbTyczs
tvi9taOsyeTI68jLyLrW0KGtoa0NCiAgICDRqr2j0ru706OsstK90LbZxvCjrMmyxMe85KOs
0tG9q7ra0sK087q6yKvK/b3ivvahow0KICAgIMzswNew79bayMu+qrXDxL+2qL/atPSjrLPV
waLSu8XUoaMNCiAgICDO5L+ttcCjuqGwuaXP8rTzte6ho6GxDQogICAgte7X1rP2v9qjrMjL
0tHJ5LP2yq7T4NXJwcuhow0KICAgIMTH0KnM7MDXsO+1xNDWtdzDx9XissXI58POs/XQ0aOs
vqq90LXAo7qhsLCh0b2jocv7ysfKpb79oa2hrc7kwdbKpb79oa2hrQ0Kv+yhraGtv+yhraGt
obENCiAgICDK/cquyMvSu87Rt+TP8tX9te6jrM7kv63C09DQyv3Vybrzo6zNu8i7zsW1w7fn
yfm69Lr0o6yy0rrFxrXG8KOsye3HsLK71LYNCrSmo6zVvb/21f3B0qGjDQogICAgy/u8scOm
vNO/7L3Fsr2jrM35x7DSu7+0oaqhqg0KICAgIMTHwb249rq619OjrMntt6jB6cfJo6zVxsGm
xua+oqOszujG8ML+zOzVxtOwo6zV/c/yu/Dszce/uaW9+LHGoaMNCiAgICDO5L+tz/LX87Hf
0ru/tKOssru9+7j8yse087PU0ru+qqGjDQogICAguqO118DP1d/Lq76msanNu6Os1+yyv86i
v6qjrM/K0arWsc3CoaMNCiAgICDL+9fzyta99M7V16HM+r2wo6zY8dnN18XJ7dfToaMNCiAg
ICDV/dPQwb249rra0sK67MX7t+e6utfTx7C687zQuaWjrMvEy6vK1rT4xvC69Lr0v/G358/y
y/vBrLu3w83F/KGjDQogICAgy/vDzdHv09LK1qOsvLLJ5Lb4s/ahqqGqxe6joQ0KICAgINK7
1ca908q1o6y6o7XXwM/V37LSvdDSu8n5o6zJ7dDOsbvV8LXE0LG3ybb4s/ahow0KICAgILWr
y/u7ucrH1/PK1sPNzKejrMz6vbC64bfJo6y/s8/ywe3Su8+uwLTWrsjLoaMNCiAgICC1scTH
uuzF+7fntcS6utfTut/By9K7yfmjrNPSsdvSu9Hvo6zSu7XAztq54ryyyeS6o7XXwM/V39DY
z8K1xNbQ6/7W2NGooa2hrQ0KICAgIMHtzeLEx8jLye3QztK7seSjrMDkusjBy9K7yfmjuqGw
1dLLwKOhobENCiAgICC69LXY0rvVxqOsw83F/Lb4s/ahraGtDQogICAgzuS/rdK7vPvWrs/C
o6zT8cPmwaK6rqOsv6HEv9bQo6y2uMi7yeSz9sG9tcC6rsmttcTJt8b4o6y3ycntx7DQ0NbQ
o6zX87HbDQrDzcyno6zUy9PDzuWzybmmwaajrLOvxMe1wNXGt+fTrbP2oa2hrQ0KICAgIM2s
yrGjrNK7yfnA5Lrfo7qhsMTDw/zAtKGtoa2hsQ0KICAgINGqvaPWuLSmo6y1sbXY0rvJ+cfh
z+yjrNK71ru2vt3w3ryjrLG7zuS/rdK7vaPF/L+qo6zJorfJtviz9qGjDQogICAgvaO54tK7
y7OjrMehusPTrc/ywLTPrsTHyMuhraGtxenIu9K7yfm089Xwo6zBvbnJ1ca357ulvdOhqqGq
DQogICAgxMfIy8PGut/Su8n5o6y3rbfJ1fCz9qOssMi12NK7yfmjrMuktdjJz6Osy8DT2rfH
w/yhow0KICAgILCl07Sjocntx7DSu8n5stK90KOs0aq9o9LRvq3NuMf7tvjI66Gtoa0NCiAg
ICDO5L+twaK8tLipye2y7L+0uqO118DP1d+1xMnLysajrLz7y/vS0b6tu+jLwMHLuf3IpaGj
v9q9x8/K0ark/eT9wfez9qOssccNCr/X1tDSssn4wcvLv8u/0aq8o6Osw+bJq7j8ysey0rDX
tcPPxcjLoaMNCiAgICDO5L+twazDpszNs/bBy9K7v8XX1LXY0MTKwL3nwO+0+LP2wLS1xNOy
v8e5+6Oswb3WuMfhx+HSu8Tzo6zM+LP20ru/xbn70MSjrA0Ks6+6o7XXwM/V37/a1tDSu8j7
o6y149ehwcu8uLSm1rnRqtGotcCho8fhx+HSu9XQo6zUvtbB0rvX+bzZyq/F1KOsvavL+8fh
x+G3xQ0Kz8Khow0KICAgIM27yLvSu8n5stK68LSrwLSjrMn50vTG4MD3zt6xyKGjDQogICAg
zuS/rdDE1tDSu76qo6z2xMi7tvjK09auz8KjrLK7vfu087PU0ru+qqGtoa0NCiAgICDWu7z7
zvfBydK7vvi78OzNtcTX88rWsuXU2tPSsd+1xMTHuPa6utfTtcTT0tDY1tCjrLWrxMe6utfT
tcTT0srWo6zItNKyx7YNCr34wcu78OzNtcS85823oaMNCiAgICDB7c3i0rvIy6Os0tG+rdK7
1cbP8rvw7M21xLDZu+HRqKGjDQogICAgzduhqqGq0b2joQ0KICAgINPWysew68n5stK90KOs
uuy54rDX07CxwM/Wo6y78OzNtcTE1LT80tG+rbG7tPK1w8+hwMOjrMv1vfiysdfTwO/D5sil
wcuhow0KICAgIMTHuuzF+7fntcS62tLCw8nD5rXEurrX08Dkut/Su8n5o6zN+8HLzfu12MnP
8/nz+bb4tra1xLvvsOnSu9Hbo6zV/c/ywe3Suw0Kt73P8sbLyKWhow0KICAgIM7kv63V4sqx
o6zFrbvw0tG437Pjo6zT0srW09az6bSkwcuhow0KICAgINHbv7TEx8jLwOvIpaOsy/uyu737
xa26yLXAo7qhsLvYwLSho6GxDQogICAgxMfIy8rV16G9xbK9o6y9o7zi0LG12LPps/a1wKO6
obC488/Cy8DG2rW9wcuho6GxDQogICAgu7DJ+c60wuSjrMnt0M7Su7avo6zRqrniycHR29bQ
o6zSu8n5stKwoaOs0ru/xcjLzbe0+NfF0rvB79Gq0+qjrLPlzOy3ycbwoaMNCiAgICDNu8i7
o6zSu8n5s8G6yLXAo7qhsNW+16Gho6GxDQogICAgt+fJ+eyqyLujrM7kv63J7cewsrvUtrSm
0tG+rcGiwcvBvbj2uuzSwqOsuuzF+7fno6y67MPJw+bW0LXEurrX06GjDQogICAgzuS/rb3F
0ru22aOswOTA5LXYtPLBv9fF1eLBvbj2yMujrNDE1tCwteLitcCjuqGwysehrrrasLW2tNb3
oa+1xLfWtrTW96OsDQqyu9Kq0KG/tMHLy/vDx6GjobENCiAgICC3veLixO685KOs1/Ox38TH
yMvA5MDk0rvQprXAo7qhsNCh19OjrNXiwO/Kx8Tjsc/D/Nautdiho6GxDQogICAgu7Cyxcu1
zeqjrNK7yfm1zbrItcCjuqGwyc+ho6GxDQogICAg78/vz8GsyfnW0KOsuq654snBycGjrMG9
zru31ra0trTW99LRvq3K1rPW18XSu7H6uq654snBycG1xMD7yNCjrLfW08nBvbLgo6wNCr7t
xsu9+KGtoa0NCiAgICDO5L+twOS6yNK7yfmjuqGwwLS1w7rDoaOhsQ0KICAgIKGw0arG+KGx
t6K2r6Osu+vJ7c24s/bV89XzuuzO7aOs09LK1tK7u9OjrNK7tcDRqrni07W0pqOs0aq9o9LR
vq2437jfvtnG8KOsDQrLq8S/uq654rXnyeS12NeiytPXxcTHwb249rrs0sK2tNb3oa2hrQ0K
ICAgIMG9uuzSwra01vejrNK70dSyu7eio6zLq8ur0rvKudHbyaujrMnt0M62uLfWwb3Wp7Ok
vaO7r9f3wv7M7L6rueKjrLfW08nX8w0K09LBvbLgo6zJ5Lv3tvjAtKGtoa0NCiAgICDO5L+t
vfS2otfFwb3Iy6Os1sXBorK7tq+how0KICAgILT9wb3Iy738tcPJ7cC0o6zL+827yLvA5Lrf
0rvJ+aOs09LK1ra4u9OjrNK7xqzRqr2j07DJ5Lb4s/ahow0KICAgIMG9uuzSwsjL0MTW0LTz
s9TSu76qo6y7xcOm1tCjrMWk0fy15rK9o6y9o9XQ0rux5KGj1ebG+NLRyLu54dPavaPJ7dau
yc+jrA0K0rvX89K709KjrLeis/bLv8u/1q7J+aOstrXNt8X8wLShraGtDQogICAgzuS/rcDk
wOTQprXAo7qhsMG9zrvT0Mqyw7SxvsrCvqG53Mq5s/bAtLDJo6GhsQ0KICAgINPvyfnOtLHP
o6zJ7dDOvLLI59D9t+fLxrXE0rvXqqOstuHD/M7lvaO12tK71dChsNGqueKxwM/WobHVub+q
o6zSu7XAz8q67A0KueLW+aOs1tDN8senvaPTsKOs0v680NfFt6XA19auyfmho7SjyLu8stD9
tvjG8KGjDQogICAgzuS/rb3xzOzWrrmmwabUtrOsuf3O9MjVtuC24KOstuHD/M7lvaPSu8qp
1bm/qqOsyfnKxrrVyLujrLfnvu3Uxsbwo6y3vdSyDQrKrtPg1cnE2tK7xqzRqrnivaPTsKGt
oa0NCiAgICDBvbrs0sK2tNb3xvG3x8rHt7q3utausbKjv7z717S0876qyqfJq6Os1qq1wNfU
vLq++LfHyMu80rXEttTK1qOs1rvT0La01vcNCrP2wLSjrLvyv8nT67+5zsChow0KICAgILTL
xO7Su8bwo6zNy9LiwaLDyKGjDQogICAgtau0y8qxo6zLxNbcvdTOqtGqueLTsMv51dajrLbU
t73J7dDOsru8+6Osz+vSqr7NtMvNy7P2o6zMuLrOyN3S16GjDQogICAg1ru1w8ury6vDxsHL
0rvJ+aOsvqHIq8nt1q65psGmo6zO6Mbwwb3NxcnBycG+q7nio6zIq8Gm1qezxdfFy8S0ptbY
0bmhow0KICAgIMvEzeLRucGmtPPU9qGjzuS/rbXE0+/J+cDkwOS0q8C0o7qhsMG9zrvL2cb6
vaO56dLAo6y/ycPi0rvLwKGjobENCiAgICDBvbrs0sK2tNb30Ka1wKO6obDEx8TjysfU2tf2
w86jrL7Ny+PO0sPHv8+jrLrZutmjrNKy1rvKx8LktcO4r8qs0rvK16Gtoa2hsQ0KICAgIM27
yLuhqqGq0rvJ+cDk0KajrLP219TKrtPgzKvN4tK71uq088r3z8KjuqGwuPPPwrn7yLvT0MG9
ytaho6GxDQogICAgx7rHuqOhDQogICAgwb3J+cz6vbvD+bSrwLSjrML+zOy9o9OwttnP1qOs
zdC12LfJxvDBy8G9teO54qOsvLLJ5Leiyfm0pqGtoa0NCiAgICCzodbQtPTBotfFwb3Ou7a0
1vejrML6wbO+qsXCtdjN+9fF19S8usrWyc+1xLDrvdi2z72joaMNCiAgICC62brZo6ENCiAg
ICDK97rz0rvJ+cDk0KajrLvG07DSu8nBo6zP1rP2ye2yxNDes6SjrLfntsj05vTmtcShsLra
sLW2tNb3obGjrMvmytbSu7f3o6wNCsDkwOS1wKO6obC+xsTSt7m0/KOhobENCiAgICDBvbXj
ueLUrcrHwb292LbPvaO84qOssbuhsLrasLW2tNb3obGjrNXi0ru396OsuvS12NK7yfm7r9f3
wb2148H30MejrLyyyOcNCrXnyq+54rvwtdizr8G9uuzSwra01vfJ5Miloa2hrQ0KICAgIMG9
uuzSwra01vfg5Mj0uq6y9aOsytaz1rbPvaOjrNW+1NrSu7Hfo6y2r9Kysru2r6GjDQogICAg
0du/tMG9teO6rrnivLLI57XnsOO12MnkvfjBy8G9zru67c/CxvjDxdGooa2hrQ0KICAgIM7k
v63A5Lrf0rvJ+aOst7TK1tK71cbFxLP2o6zSu9Xz0vXI4cDkt+e+7bP2o6y1wKO6obC2tNb3
tPO/ybK7sdjEw8v7w8ez9g0Kxviho6GxDQogICAgu7Cyxcu1zeqjrMG9teO54s27yLu+orXA
yKvP+6OstbG1scG9yfmjrMLk1NrBvbrs0sK1xMPmx7Chow0KICAgIKGwutqwtba01vehsbn+
uf7Su9Xzv/HQprXAo7qhsMTjw8fBvcjLu7myu7/syKWx8LSmv7S/tKGjobENCiAgICDBvbrs
0sK2tNb3uafJ+bXAo7qhsMrHo6GhsQ0KICAgIMury6vLyrzntvjIpaGjDQogICAgwdnIpaOs
zfvBy87kv63Su9HboaMNCiAgICDV4svEtcDR27nio6yz5ML6wcu40Lyk1q7H6aGjDQogICAg
tP3BvcjLye3Qzs/7yqe686OszuS/rcynzbfLxMPmzfvBy837tcCjuqGw0ebTsLPlzOyjrLP+
uOjLxMbwo6y2tNb30MTW0NPQDQq6zrjQz+ujv6GxDQogICAgobC62rC1trTW96GxwOS639K7
yfmjrLXAo7qhsLPwzOzAy8vkyLvS0b6tsbvE48rVwvKjrLWroa612NP8zfWhr8i0zrSx2M6q
DQrE48v508Oho6GxDQogICAgzuS/rcDkwOTSu9Cmo6y1zcn5tcCjuqGwoa612NP8zfWhr9Ky
1b7U2rG+yMvV4rHfoaOhsQ0KICAgILrasLW2tNb3utm62dL10Ka1wKO6obChrrXY0/zN9aGv
sb7Iy8O7wLSjrL7Ny+O12NP8zfW4rtKysbvE48rVwvLBy6Ossb62tA0K1vfSsrK7vuXE46Gj
obENCiAgICChsNfdyrnE47K7vuXO0qOstavE47XEytbPwsj0yKuyv7G7zcDJsbvyyKuyv7e0
xdGjrMTj0ru49sjLxNzT0LbgtPO1xMTcDQrEzaO/obENCiAgICChsLrasLW2tNb3obHNu8i7
0fbM7LTz0Ka1wKO6obCxvra01vfK1s/CyPTKx9PQ0rvIy7e0xdGjrNTyy/vWu8rH19TL2cbk
y8ANCrDVwcujrMj0ysfIq8r9sbvNwKOsysexvra01ve1xMrCo6y3uLK718XE48C0tuC53M/Q
ysKho6GxDQogICAgtMvT79K7s/ajrM7kv63Nu8i7z+vG8MHLxMfSucHW1tDWrtW9x7CjrM7B
xsfL+cu1tcS7sKO6obC2+MfSo6zAz8q1y7WjrNa7DQrSqr3i0qm1vcrWo6zO0sPH0rK+zc60
sdjFwsHLy/uho6GxDQogICAg0ru49sTuzbejrM27yLvC07n9wcvL+7XE0MTNt6Ossru9+8Pm
yau9pbquo6yzwcn5zsq1wKO6obDQsLbxtr7Ep8rH1/C83bXEDQrKssO0yMujv6GxDQogICAg
obC62rC1trTW96Gxuf65/r/x0Ka1wKO6obDJs7rX0arEp8rH1/C83bXEyrLDtMjLo7+hsQ0K
ICAgIM7kv63QxNbQ0ru+qqOsufvIu7K7s/bL+cHPo6yhsLrasLW2tNb3obHKx9CwtvG2vsSn
tcTH18ratdzX06OstbHPwrK7vfvA5A0KwOS1wKO6obDX8Lzdsrux2LnK1/fJ8cPYo6zEx9XF
w8nD5r3tv8nS1MTDz8LAtMHLoaOhsQ0KICAgIKGwutqwtba01vehscDk0Ka1wKO6obDSqsih
uPPPwtfUvLq2r8rWo6y62brZo6yxvra01vfDu8THw7S24LXEyrG85Lj6xOPPuQ0KsvijrL/s
vfjV0LDJoaOhsQ0KICAgINXiyrGjrLflyc/Jscn5y+S99KOstavKx7LSusXJ+bu5yseyu774
09q2+qOs1f3W0LTzte7S0b6tyLzG8MHLs+XM7Lvw0eajrA0K1dW1w9X7uPbJvbflyc/D98jn
sNfW56OhDQogICAgy8TW3Lr6ydrJ+aOsvaXP8rTzte68r9bQoaMNCiAgICDKp7vqvsbYpL/x
t8W1xNCmyfmjrLK7yrG1xLSrwLShraGtDQogICAgv9XW0KGqoaqz/cHLu/C54s3io6yxzNHm
y8TJ5KGjDQogICAgu7nT0MTHuuyhorDXoaLCzMj9yau1xMO3u6i78NHmo6zLxMmi17nPwqOs
ybfKx8PAuduhow0KICAgINPJ1eK8uLXjyc+/tMC0o6yhsLrasLW2tNb3obHWrrDco6zKx9LR
s8m2qL7Wwcuhow0KICAgIM7kv63A5L6y0tG8q7XYtcCjuqGwutqwtba01vfWrrjEsNzN9qOs
0tGzybaovtajrLa01ve7ucrH1NrLvLb40NCyxbrDoaOhsQ0KICAgIMu118WjrLnK0uLP8svE
1tzN+8HLzfujoQ0KICAgIKGwutqwtba01vehsbK7ysew17PVo6zEx9PQsrvWqtauwO2jrLWx
z8LA5MDktcCjuqGwsb62tNb31rvSqr2ruPPPwsTDz8LJsQ0Ky8CjrNPa1LjS0cHLoaOhsQ0K
ICAgIM7kv6262brZ0rvQprXAo7qhsLrDvKvBy6Os1NvDx7W9tPO17seww+bIpdK7vva0xtDb
sMmjoaGxDQogICAgobC62rC1trTW96Gxut3J+bXAo7qhsLrDoaOhsQ0KICAgIMnt0M7Su9D9
o6y7xtTGxvC0pqOs1rHGy7Tzte6joQ0KICAgIM7kv623tMrWvavRqr2juenHyrrzo6zLq9fj
0ru22aOsu6/X99K7tuS67NTGo6y99Mvm18WhsLrasLW2tNb3obHJ7brzx7DQ0KGjDQogICAg
tPO17sewo6zB0tHmzNq/1aOsu/DR5sLSt8mjrMjL07DX3brho6zPytGqy8TI96GjDQogICAg
obC62rC1trTW96Gx1q7K1s/Co6y8sNO1u6S62rC1trTWrs7kwda6wL/Nw8ejrLTztuDK/b3U
0tHNy7W9wcu17sewo6y4utPnDQrN57+5o6zgqdGq0arVvaGjDQogICAgtba54rv0u/SjrL2j
07DI58m9o6zU2bzTyc/Ex9XGt+fWuNOwo6zIrcn5uvS69KOste7HsLvw07DPwqOsye7O7dbQ
o6zIy9OwDQq0wrTCtdjOp8Gi18W9/MenzuTB1rjfytahow0KICAgILOh1tCjrMr9yq7Iy6Os
1f3U2tf318XK4svA1q7VvaGjDQogICAgtrjIu6Gqoaq+orfn7KrIu6Os0ru7xtK7uuzBvbbk
ssrUxsHov9W2+L21o6zNrMqx0rvJ+cDKusijuqGwutqwtba01ve13NDWDQq4+M7S16HK1qGj
obENCiAgICDV4sqxo6yw18O3z8jJ+qOsuuzDt8DPyMujrMLMw7fK6cn6o6y31sj9w+a2+MGi
o6zHocfJvavL+dPQzcvCt7a8t+LXocHLoaMNCiAgICDI/cjL1q685KOsysfM7MDXsO+w79b3
s/DM7MDLo6zD5s7ese3H6bXEyq6089HWwt68sMqnu+q+xtiktcjIy6GjDQogICAgutqwtba0
t73D5r7bvK/U2rvws6HHsKOsv7TH6dDOy8DJy8/gtbGy0tbYo6y67NLCtrTW99a7yqPPwsj9
zrujrLfWzMPMw9b3DQrSssrHw7u8uM67wcujrMjLyLrW0MGivLTG8MHL0rvV88mntq+how0K
ICAgINPQyMu1zcn5tcCjuqGwxOO/tKOsy/u+zcrHobDO5MHWyqW+/aGxtdrI/bT6oaOhsQ0K
ICAgIKGwy/uyu77NysehrrrsyfGhr8Lwo7+hsQ0KICAgIKGw4MWhraGtobENCiAgICCw18O3
z8jJ+rXItry1pc+l18W12KOswb3K1rfWsubQ2Mewo6zR9srXufLBy8/CyKWhow0KICAgINXi
ysfO9MjVobDO5MHWyqW+/aGxs6/W0NTa1fPHsLnbvPvWrsDxoaMNCiAgICDSu8myxMe85KOs
1fu49rOh1tC2vL6ywcvPwsC0oaMNCiAgICCw18O3z8jJ+rXIyMvJ7brztcS9/MenzuTB1rrA
vdy2vLfXt9e12NLUzazR+bXE18vKxrnywcvPwsC0oaMNCiAgICCzodbQxrTD/NjLybG2r8rW
tcTIy6Os0rK2vNLUzazR+bXE18vKxrnywcvPwsC0o6yx7cq+ttShsM7kwdbKpb79obG1xLPn
vrShow0KICAgILrasLW2tLXc19O8sMbky/uw2dPgyMvU8s/yobC62rC1trTW96GxufLPwqOs
0tTKvtOtvN2how0KICAgILz7wPHN6rHPo6zO97e9w+a1xMjLtrzVvtaxwcvJ7dfToaMNCiAg
ICCzodbQo6yz/cHLu/DJ+aOsvLC3v9PutcS1ucn5zeKjrNa709DEx9CpzbS/4LXEyevS98n5
sru++NPatvqhow0KICAgILvwueKjrNXV1NrDv9K7uPbO7dbQyMu1xMGzyc+jrLa8ysfRz8vg
0+uzwdbYtcShow0KICAgILK7ysfC8KO/DQogICAgvdjWwcS/x7DOqta5o6yw18Ltt+XJz6Os
xMfA78O709DNv8L6z8rRqqO/xMfA78O709C2z9arstC5x6O/xMfA78O7yMvNtL/gDQq1xMnr
0vejvw0KICAgINXiysfSu7Ohv9XHsLXEzuTB1rTzvdmjrLPJx6ezybDZtcTIy6Os0tG+rcml
ye3U2tXiyb235cnPwcuhow0KICAgILu509DO3sr9tcTIy6Os1f3P8tXiyb235cnPuM/AtKGj
DQogICAgxL/HsKGqoarV4rvws6HHsLXEs8G8xaOsydCyu9aqtcDKx9Xis6HJsb3ZtcS94cr4
o6y7ucrHwe3Su7OhybG92bXEv6rKvKGjDQogICAg193Iu8rHs8nE6tTatba/2snP88LRqrvs
t7mz1LXExfPT0cPHo6zV4sqx0rK6rsHL0MShow0KICAgILWrysehqqGqsru53NXiysfSu7j2
veHK+Lvyyse/qsq8o6zLrba81qq1wKGj1eLKx8Ht0ru49rrGvdm1xL+qyryjrMHt0ruzoQ0K
1b3V+bXE0PLEu6GjDQogICAg1Nq688PmxMezodW91fnW0KOs1rvSqsrH1Nq9rbr+yc/F3LXE
xfPT0aOsw7vSu7j2sru+rcD6uf2how0KICAgIMv50tSjrMutxNzT0Mfhy8m1xNDEx+mjv8ut
xNzU2dCmtcOz9sC0o78NCiAgICDFqM7to6y9pb2lyaLIpaGjDQogICAgwOjD98ewtcS62rC1
o6y4w8rH1+662rC1tcTBy6GjDQogICAgtauw18Ltt+XNt6Os0rvGrMP3wcGhow0KICAgINDH
ueLPocLko6zV4rjDysfSu7j2w8DA9rXEx+/SuaGjDQogICAgobC62rC1trTW96Gxs8HW2LXE
v6q/2rXAo7qhsMfls/bSu8asv9W12MC0oaOhsQ0KICAgIKGwysejoaGxDQogICAg0rvJ+brk
z+yjrNPJy/vJ7brz0+O54dffs/a2/squuPa62tLCw8nD5rTzurqhow0KICAgIM7kv63S4LvY
zbezr7DXw7fPyMn6tcCjuqGwtv7PyMn6o6zH68XJyMuw0cnLyMvMp7+qo6GhsQ0KICAgIMmy
xMe85KOs19+z9sj9yq649rTzurqjrMquuPaw19LCo6zKrrj2uuzSwqOsyq649sLM0sKjrNff
vfizodbQo6zQodDE0u3S7Q0Ktdi9q8nLyMvMp7+qoaMNCiAgICCyu9K7u+G2+bXEuaa38qOs
te7HsMfls/bBy8j9yq7Vybe91LK1xNK7v+m/1bXYwLShow0KICAgIKGwutqwtba01vehsbDB
yLuzr87kv63Su/Klyte1wKO6obDO0sPH1eK+zb+qyrywyaOhobENCiAgICDO5L+t1eLKsbe0
tbnOos6i0rvQprXAo7qhsLHwvLGjoaGxDQogICAgobC62rC1trTW96Gxv+fHsNK7sr3A5LXA
o7qhsLjzz8LT0Mqyw7THstHUv+zH67fUuMCjoaGxDQogICAgzuS/rcDkwOS1wKO6obC3z7uw
ydnLtaOs1eKzocqkuLrWrrrzo6y4w9f3us6+9raoo7+hsQ0KICAgIKGwutqwtba01vehsdH2
zOy62brZ0rvQpsL609Cw0c7Vtdi1wKO6obCxvra01vfI9Li6o6y007TLzP3B7tPauPPPwqOh
obENCiAgICDO5L+ts8HJ+bXAo7qhsNfwvN27sLK70qq9srXDzKvU56OssrvFwsnBwcvE47XE
yeDNt6GjobENCiAgICChsMTjt8XQxKOssb62tNb30rvP8su1u7DL47uwo6y6zr/21NqzodPQ
1eLDtLbgyMvX99ako6zE48XCztK3tLvasruzyaO/obENCiAgICDO5L+ttPPQprXAo7qhsM7S
ysfFwsTjtb3KscGzyc+50rK716Gho6GxDQogICAgobC488/Cvs2yu9PDzObO0rLZ1eK49tDE
wcujrLWrztK7sNKy0qrLtdTax7DNt6OsyPTKx8TjyuTBy8TYo7+hsQ0KICAgIKGwxMfO0tXi
oa7O5MHWyqW+/aGvtcS34rrFvs256cTjo6y2+MfS0rLL5rHjxOO0ptbDoaOhsQ0KICAgIKGw
utqwtba01vehsdK7zP2jrNPWysfSu9Xzs6TQprXAo7qhsMTjtbm087e9oaOhsQ0KICAgINK7
xdS1xLDXw7fPyMn6vLG1wKO6obDKpb79oa2hraGxDQogICAgzuS/rc60tcjL+8u1zeqjrNK7
0e/K1tbG1rnL+7XAo7qhsLb+z8jJ+qOsx+uyu9PDtaPQxKOsztLX1NPQt9a056GjobENCiAg
ICDKp7vqvsbYpLn+uf6089CmtcCjuqGwsNfDt8/IyfqjrMTjsfDXxbyxo6zO0tXi0KG13M/W
1Nq1xLmmt/LBy7XDo6y/ybK70rsNCraou+HK5KOs1NvDx77N1NrF1LHfv7SwyaGjobENCiAg
ICCw18O3z8jJ+tXissXBotK7xdSjrLmnyfm1wKO6obDKx6OsyqW+/cfrtuDQodDEoaOhsQ0K
ICAgIKGwutqwtba01vehsbK70tTIu7XEtcCjuqGw0qqxyL7NscijrMbFxsXC6MLotcSjrLrf
o6GhsQ0KICAgIM7kv63V4rLF16rNt7bU1trIy7XAo7qhsLTTz9bU2sbwo6zH67j3zruyu7HY
tuDLtaOszcvBotK7xdS529W9o6GhsQ0KICAgINbayMuyxcbryfnXob/ao6y+sr6ytdjVvtTa
0rvF1KGjDQogICAgzuS/rcPmz/KhsLrasLW2tNb3obG1wKO6obCyu9aq1/C83cjnus6xyLeo
o7+hsQ0KICAgIKGwxOPLtcTYo7+hsQ0KICAgIM7kv63A5MDkv6q/2rXAo7qhsNLUsNnV0M6q
z97I57rOo7+hsQ0KICAgIKGwutqwtba01vehsbrfwcvSu8n5tcCjuqGwy+ax48Tjy7WjrM2s
yrGjrNPQyrLDtLG+ysK+obncyrmz9sC0o6yxvra01veyuw0Kz9O24KGjobENCiAgICDL+9Xi
u7C1xNLiy7y+zcrHy7WjrNTa1eKw2dXQ0tTE2qOsy+ax49PDyrLDtMrWts62vL/J0tShow0K
ICAgINXi0rK+zcrHvca7q9autKahow0KICAgIM7kv63Ex9PQzP2yu7autcS12Le9o6y1sc/C
wOTA5LXAo7qhsMjn1/C83cv50dSjoaGxDQogICAg0MTA78i0sLWwtbXYxPPBy9K7sNG6uaGj
DQogICAgy7XV5rXEo6zO5L+tw7vT0LDRztXTrsv7o6y1q86qwcvM7M/CzuTB1rXE0NK4o6Os
zqrBy6GwzuTB1sqlvv2hsbXEw+bX06OsDQrOqsHL19S8urXE0aq6o8nus/CjrLK7tcOyu9Oy
18XNt8akyKvBptK7xrTBy6GjDQogICAgy8TW3LXEyMujrMfEzt7J+c+itcTT1s3Ls/bBy8qu
1cnUtr38wcuhow0KICAgIMG9yMvP4L7gsMvVycGitqihow0KICAgIKGwutqwtba01vehseTs
yPe12LC6waLXxaOsy6vIrbWx0NjSu7GntcCjuqGwx+u9+NXQoaOhsQ0KICAgILC1tdjKsaOs
0tHUy9fjwcvG37PJ1ebBpqOszazKsdKy0tG+rdTLxvDBy87ez+C2vu64oaMNCiAgICDO5L+t
0uCxu7vwueLSu7PEo6zPvNOw0rvN0KOsuPzP1LXDuLu589O6yN2jrL+hw8DO3salo6zOotCm
tcCjuqGwv82yu9G5DQrW96OhobENCiAgICDNrMqxo6zS4L2robDRqsb4obG8sKGwyOGx+cnx
uaahsdTLxvCjrMG9ucm92Mi7srvNrKOstau1vdTLz+DJ+rXEwOTIyNauxvgNCtGt0NDM5cTa
o6y9pb2ls+Sz4rb4s/ajrMntzeLSu7Pf0tTE2qOsvqHU2rqut+e8pLW0o6y67NTG1dbWrs/C
oaMNCiAgICChsLrasLW2tNb3obHO3s/gxvjuuL2lvaXKudbcye29pb2l07XG8MHL0rvO5dHV
wfnJq7XEzu3TsL2ry/vIq8nt1dbXoaGjDQogICAgyKuzocGivLTP3cjrwcu8q7301cW1xMb4
t9XW0KGtoa0NCiAgICDNu8i7oaqhqtK7yfnA5LrItcCjuqGw09DZ1KOhobENCiAgICChsLra
sLW2tNb3obHCys/It6LE0aOss6HW0MGivLTR78bw0rvNxbLK07CjrNbQufzSu7bku8bUxqOs
tPjXxbyyzt6xyLXEt+ejrA0K0K680NfFzt7K/bXE1cbTsKOsyOe+qszOxcSwtrDjtdjTv8/y
zuS/raGjDQogICAgyMvIutbQwaK8tNO1xvDBy7K/t9a1xL6qzL7J+aO6obC2vszOvqrM7NXG
o6zL+8rH0LC28bbxxKe1xLSryMuho6GxDQogICAgobC1scTqtcTQsLbxtr7Ep7HIy/u7ubLu
tcPUtsTYoa2hraGxDQogICAgvqrMvsn5zrSxz6Oswe3Su9XzvqrMvsn509bG8KGjDQogICAg
s6HW0KOs1NrTtcbw0rvNxbrs1MajrLyktbTG8Mbg0KXXxbXEuq6356Os0v680NfFt+fA18mx
t6XWrsn5o6zTs9fFu/C7qKOsDQq3orP2ycHJwbXEz7zTsKOsz/LEx83FssrTsLyxvLLJz8il
oaMNCiAgICDBvc3FssrUxtK7tKXV4s/Co6y/8bfntPPX96Osvu3G8MHLzt7K/c+40KG1xLfn
1vmjrLeis/bG4MD3tcTQpcn5o6zP8svEzeINCryks/ahow0KICAgIML+zOy70rO+o6zN0LXY
tvjG8KOssbvVxrfn0+C+orS1tcPSwsnAxq7R76OswaLX47K7zsijrLfXt9e6883LoaMNCiAg
ICCz/cHL09DP3rXEvLi49s3io6y087zStry/tLK7vPuzodbQ09DIy9Owo6zWu7+0vPvBvbTz
zcW/8dCl18W1xLLKzu3G4LfnvLINCtD9u6XTtaOsyrG438qxtc2jrMW8tvu/tLP20ru0rtXG
07CjrNK7y7K2+MrFoaMNCiAgICC358DX1q7J+dS9wLTUvcqioaPJsbel1q7J+aOs1L3AtNS9
xaiho87kv63J7dDOxq669qOs1bm/qqGwyOG+raGxtcTRqbuoxq4NCsntt6ijrNLUvLDRqdD1
1cajrLGisfnIraOs1Nm808nP0aq54sPUwOvVxqOsyqnVub+qwLSjrMbLy7fD1MDro6y69sjI
uva6rqOsuvYNCraruvbO96OsyfHL2cDrxubS0byroaMNCiAgICC1q6Gwutqwtba01vehsbXE
zuS5pqOsyrW3x9K7sOPIy8v5xNzUpMHPtcSjrLa+zM6+qszs1cbVub+qo6zB7bPJ0rvCt6Gj
uvYNCrb4xua41aOsuva2+MbmyOGjrO64t+e69Lr0o6zVxtOwyOfMzqOs0rvKsbzkvrm31rK7
s/bKpLi6oaMNCiAgICDM7LHfo6y9pcK20+O2x7DXoaMNCiAgICDBvcjLo6zTybXYyc/VvcnP
wcvM7KOszNq/1bu71ca686OswuS12NTZ1b2how0KICAgIM27yLuhqqGqyqe76r7G2KS087rI
0rvJ+aO6obC+xcqu1dCjoaGxDQogICAgyLrQ27a8sru9+86q1eLSu76qoaMNCiAgICDT78n5
t72xz6GqoarFvqOhDQogICAg0rvJ+bGpz+yjrL30vdPXxbOh1tDTtcbwwcu/8cHStcTQ/bfn
o6zI587ttcS70rO+oaMNCiAgICC70rO+vaXQqqOswb3Iy7fWvuDKrtXJo6zJz9XGsca21KGj
DQogICAgzuS/rcPmyavmzLrso6zEv7niyOex+aOsy6u0vb30sdWjrM/UyLvS0b6t08PX48HL
yq6zybmmwaahow0KICAgIKGwutqwtba01vehscurxL/UsrXJo6zLxrr10rLS0b6tvqHBy8ir
waahow0KICAgIM7kv63Lq9XGy/nJ5LP2tcTuuLfnuuzO7aOstdbXocHLobC62rC1trTW96Gx
1cbW0Mv5t8Wz9rXEssrRzKGjDQogICAgwb25ydXGwaajrLulz+DP+7Ok18WjrLKizrS31rP2
yqS4usC0oaMNCiAgICDNu8i7oaqhqs7kv63DxrrfwcvSu8n5o6y2uMi70tTKrrb+s8m5psGm
t6Kz9qGw0P7M7NX9xvihsaGjDQogICAg0ru5ybnJsNe54rTTzuS/rcntyc+zsdO/tviz9qGj
DQogICAgobC62rC1trTW96Gxtc2638HL0rvJ+aOsw8nD5rvGve21xM/Ctsu+ubXOs/bBy7y4
tc66ucuuoaMNCiAgICDLq9XGyKvBps35x7ChraGtDQogICAgzdujoQ0KICAgIKGwutqwtba0
1vehsdXFv9qz9sn5o6zJ7dDO0ru7zqOstbnNy8G9sr2jrMPJw+a7xr3ttcTPwrbLvrm147Xj
tc61zrXYyPfPwg0KwcvSu8asz8rRqqOszazKscurvqbSu7eto6zBvcrWzt7BprXYtLnBy8/C
wLSho7vOwcvBvbvOo6y3rcnttbnPwqGjDQogICAgwaK8tNPQwb3Ou7a01ve3ycntxsvJz6Os
063XocHLy/u1xMnt19OjrMynz/LBy9K7sd+how0KICAgIM7kv63Lq8S/1LLV9qOsy6vK1tKy
ysfO3sGmtdi0ucHLz8LAtKOsu9jXqsntwLSjrLOv1trIy9CmwcvSu9Cmo6zDzci71cW/2qOs
DQrF57P20rvRqrz9o6y3rcnttbmhraGtDQogICAgsNfDt8/Iyfq1yMjLtPO+qqOs0ru49rz9
sr2jrL/nvfzBy87kv621xMntx7CjrMehusO39teho6zBrMOmzM2z9tK7v8W1pNKpo6wNCsj7
vfjBy87kv621xL/ao6zNrMqxtePXocHLy/u1xLy4tKbRqLXAo6zH4cfhtdjN0M/ywcvSu7Hf
oaMNCiAgICDKp7vqvsbYpMfhx+HJ7MrWzL3By8y9zuS/rbXEscfPoqOszL7By7/axvi1wKO6
obC7ubrDo6y7ubrDo6zWu8rHzdHBprDVDQrBy6GjobENCiAgICDSu8LW0PHI1aOsyeSz9sHL
zfK1wLniw6KjrL2lvaXJ/dfUzOyx36GjDQogICAgsNfC7bflyc+jrLu2yfnV8MzsoaMNCiAg
ICDU2sTHvbnBurbP2KijrLLQ0cy0prSmtcTJvc23yc+jrLGss/bBy9Xz1fO7trr0oaMNCiAg
ICChsM7kwdbKpb79obHN8svqo6ENCiAgICC5ss6szuTB1tX90uWjoQ0KICAgIKGtoa2joQ0K
ICAgIMG9uPbD5smrstSw16Ostau/ocPAt8e3srXEx+DE6qOsttTD5rb4waKhow0KICAgIMTH
ysfO5L+t0+uhsLrasLW2tNb3obHCwMP3xuahow0KICAgIMLAw/fG5sPmtPjAotauyau1wKO6
obDKpb79tPPBv6Osw/fG5tPAyfqyu838oa2hraGxDQogICAgzuS/rc6i0Ka1wKO6obC089XJ
t/K40tf3uNLOqqOsuf3IpbXE0tG5/cilo6zN+7a01ve98brz1vrO0rmy0e/O5MHW0uWjrNLW
DQrWuaGwtPPEp73MobG28crGwabWrrei1bmjrNXissXKx9Xm1f21xLrDxfPT0aGjobENCiAg
ICDCwMP3xua1wKO6obDD98bm19S98bb4uvOjrL720MS4xLn919TQwqOsyKvBprf2ztLKpb79
o6y5sr7ZtPPStaGjobENCiAgICDO5L+tuf65/tK70KajrNPDwabSu8XEwsDD98bmtcTT0rzn
tcCjuqGwxNC2+bWx09C0tNK11q7QxKOszuS/rcGmtaXKxrGho6wNCsnQ0Oi2tNb3tuC24Lf2
s9aho6GxDQogICAg1eLKsaOs1trIy7a8t9e318nPwLS1wLrYoaMNCiAgICDQ8cjVtqvJ/aOs
z/LIy7zks7fPwsHLueLD99Pru7bA1qGjDQogICAgsNfDt8/IyfrSu9DQyMu1yKOsy+bKsbT9
w/yjrLPwzOzAy+XJt7XN7tbQo6zV+7bZyKuw76Osy+bKsbT9w/yhow0KICAgILnYzeLI/bLQ
u6TLzbvw7M21xMqsuce7uc/no6zNrMqx0fvH677J09HM+sbvyP3KrsH50Na13LzTw8uhow0K
ICAgIMqutPPR1sLet7W72OPjtryjrLmnx+u12NP80dbN9bzTw8uhow0KICAgIMbky/u49867
o6y78rfD09GjrLvyy+a3tczawfqjrMeyyaLSu7/VoaMNCiAgICDCwMP3xubU8tfU1Li3tbvY
utqwtba0o6zIobP20rvH0LHY0OvTw8a3vLC98NL41umxpqGjDQogICAgzuS/rbG+ye3U8s3G
y7XT0NKqysK0/bDso6y2qNPaxOq117XWtO/M2sH6ucihow0KICAgILb4w/fE6sCw1MKz9dK7
o6y2qM6qzNrB+rnIv6q5yKOsobDO5MHWyqW+/aGxvs3B+r79zrujrNX9yr2/qriuo6y97Mqx
sdi54w0KyPbCzMHWvO2jrLHpt6LPwNLlzPujrNH7x+vM7M/C06LQ26OsubLP5cqivtmhow0K
ICAgINK7x9DJzNLpzaO1saOs1trIy7fWxfrPwsm9tvjIpaOs1rvT0Mqnu+q+xtikxePXxc7k
v63B9M/CoaMNCiAgICCw18Ltt+XNt6OstbnL+sHLtcS087Xuo6y9ucG6y+nN36OsstDRzPTB
9MGjrLzTyc+x6bXYztvRqqOsstDWq7bPsdujrLSmtKYNCr/JvPujrNXmysfSu7ixxuDBub6w
z/Ohow0KICAgIM7kv62+rbn90rvSub/g1b2jrLzTyc/L8LrE1ebBprn9yfWjrMvk1Pi3/s/C
z8m1pMHp0qmjrLWr0rKyu8rH0rvKsdauvOS/yQ0K0tS71ri0tcShow0KICAgIMqnu+q+xtik
wa+wrrXEzfvBy87kv63Su9HbyOHJ+bXAo7qhsMqlvv2jrNClzOy/ybfx1vrE49K7sdvWrsGm
oaOhsQ0KICAgIM7kv63QprXAo7qhsLr6tPO456Os0tS688u1u7Cx8MyrvPvN4qOsxOPX3MrH
0KG13LXEtPO456GjobENCiAgICDKp7vqvsbYpLfFtbS538HLtcTIy6OsvdDL+77QyvijrNGt
uea1wL7Yy/vLtbuwo6zKtdTa9b/FpKOszP28+87kv63V4sO00rsNCsu1o6yyu737uf65/rTz
0Ka1wKO6obC1vbXXysfO0rXEusPQ1rXco6y5/rn+o6HAtMC0wLSjoaGxDQogICAgzuS/rc+v
tdi2+Nf4o6yx1cS/1MvG+KOswcbWzsnLysahow0KICAgIMqnu+q+xtik1/jU2sv7ye2686Os
09LVxsfhzPnT2sv7tcTD/MPF0ajJz6Os0ru5ydDbuvHO3rHItcTE2sGm1rGxxr34yKWjrA0K
0a3C9rb4yOuhraGtDQogICAgvaW9pbXYo6zBvcjLzbfJz7a8w7DG8MHL0rvNxc7txvihow0K
ICAgIM7kv63QxNbQsLWwtbPUvqqjrM/rsru1vcr91MKyu7z7o6zKp7vqvsbYpLXEzuS5ptKq
scjS1MewuN+24MHLoaMNCiAgICC1q8rHo6zT0NK7tePB7sv7sru94rXEo6zKx7WxyNXKp7vq
vsax4szlwdvJy6OsxbvRqsqn19nKsaOs1PjSp7bPwcvJ4Lj519OjrA0Kxeez9r7ctdCjrNT1
tcTP1tTa09a6w7XExNijvw0KICAgIMu84uK8sLTLo6zL+8PNtdjSu8rVxO6jrLC1wu7X1Ly6
1PW1xMjntMu6/c2/o6y0y8qx1f3Kx9TLuaa99NXFudjNt6Os1PW1xA0Kt9bJ8cTYo78NCiAg
ICCyu77Do6zG+NDQsNnC9qOszOXE2tLRvq271ri0tuDBy6GjDQogICAgyqe76r7G2KTK1dXG
xvDBoqOss6/O5L+ttcCjuqGwwM+13KOsxOO3vbLF1NrP68qyw7Sjv6GxDQogICAgzuS/rdLg
0tHV9tHbxvDBorXAo7qhsMDPuOe458nPtM7J4cP8z+C+yKOs0KG13NPAvMehraGtobENCiAg
ICDKp7vqvsbYpLn+uf6089Cmo7qhsNChtdzSu7ao1NrG5rnWxOPV4sDPuOejrNT1w7S74brD
tcPV4sO0v+zE2KO/obENCiAgICDO5L+tsru6w9Liy7y12NCmwcvQprXjwcu14823oaMNCiAg
ICDKp7vqvsbYpLXAo7qhsMDPuOfEx8jV19TBv7HYy8CjrLK7wc/ItM6q0rvO5MHWx7Cxssv5
vsijrLK7tau9q87SycvIq7K/0r0NCrrDo6zNrMqx1ri148HLwM+457y4yta5prfyo6zEx7a8
ysfAz7jnuOexvsPF1tDKp7Sr0tG+w7XEzuS5pqOsyLu686Osw/zO0tTZtsgNCrP2ysCjrNb6
wM+13MTjo6yzyb7NzuTB1rTz0rWho6GxDQogICAgzuS/rdDE1tDSu76qzsq1wKO6obC0y8jL
ysfLraO/obENCiAgICDKp7vqvsbYpNCmtcCjuqGwwM+457jnwdnIpcqxo6zL+9TZyP22o9b2
sru/yc24wrbL+7XE0NXD+6OsxbajrLbUwcvEx8jLy7UNCrn9o6zI9MTj09C/1aOsv8nS1LPW
tMu6rcilteHW0M7ewb/JvdbQ0bDV0tK7zru90Nf21LPJvcjLtcTO5MHWx7CxsqOsyOe5+8Tj
u/oNCtTLusO1sdPQy/m78aGjobENCiAgICDLtdfFo6zEw7P20ru34sPctcTQxcC0oaMNCiAg
ICDQxbfiw+bJz6Oswfq3ybfvzui12NC018XD5sb0o6zO3sG/yb3P37+qucijrNSzyb3Iy8rV
tcjX1tH5oaMNCiAgICC909fFo6zKp7vqvsbYpNPWtcCjuqGwtMvQ0L7dy7XT66Gu0arIrb6t
oa/T0LnYz7WjrMv50tTPo837wM+13NK7tqjSqtXStb0NCsv7ssXKx6GjobENCiAgICDO5L+t
0KHE1dLt0u212L2r0MXK1brDo6zOyrXAo7qhsMDPuOe458rHt/HT687S0rvNrMilo7+hsQ0K
ICAgIMqnu+q+xtik0Ka1wKO6obCyu8HLo6zO0rvh1NrE6rXXuM+1vcCostTJvczaucjAtLXE
o6zU2bvhoaOhsQ0KICAgIMu1zeqjrLmnye3Su7Ddo6zI57fJz8LJvciloaMNCiANCiAgICAt
LS0tLS0tLS0tLS0tLS0tLS0NCqGhoaHSu8P5yajD6KOs0am2+dCjttQNCjwvc3Bhbj48L3By
ZT4NCiA8L3RkPg0KICA8L3RyPg0KPC90YWJsZT4NCjwvY2VudGVyPg0KPC9kaXY+DQo8aHIg
Y29sb3I9IiNFRTlCNzMiIHNpemU9IjEiPg0KPGNlbnRlcj48YSBocmVmPSIwMjMuaHRtIj48
c3BhbiBzdHlsZT0iYmFja2dyb3VuZC1jb2xvcjogI0UxREZGMiI+yc/Su9KzPC9zcGFuPjwv
YT6hoaGhoaGhoTxhIGhyZWY9IjAyNS5odG0iPjxzcGFuIHN0eWxlPSJiYWNrZ3JvdW5kLWNv
bG9yOiAjRTFERkYyIj7PwtK70rM8L3NwYW4+PC9hPjwvY2VudGVyPg0KPC9ib2R5Pg0KPC9o
dG1sPg0K
--L4g6m101Ua01T842R9b8N62r--
_______________________________________________
manet mailing list
manet@ietf.org
https://www1.ietf.org/mailman/listinfo/manet


From mailnull@www1.ietf.org  Tue Nov 26 14:25:12 2002
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA16941
	for <manet-archive@odin.ietf.org>; Tue, 26 Nov 2002 14:25:11 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id gAQJRTC19282
	for manet-archive@odin.ietf.org; Tue, 26 Nov 2002 14:27:29 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gAQJRSv19279
	for <manet-web-archive@optimus.ietf.org>; Tue, 26 Nov 2002 14:27:28 -0500
Received: from www1.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA16927
	for <manet-web-archive@ietf.org>; Tue, 26 Nov 2002 14:24:40 -0500 (EST)
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gAQJIRv18844;
	Tue, 26 Nov 2002 14:18:27 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gAQJDRv18539
	for <manet@optimus.ietf.org>; Tue, 26 Nov 2002 14:13:27 -0500
Received: from cs.dartmouth.edu (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA16450
	for <manet@ietf.org>; Tue, 26 Nov 2002 14:10:36 -0500 (EST)
Received: from localhost.localdomain (dhcp48.ISTS.dartmouth.edu [129.170.249.148])
	by cs.dartmouth.edu (8.12.1/8.11.4) with ESMTP id gAQJDFRB001001
	for <manet@ietf.org>; Tue, 26 Nov 2002 14:13:15 -0500
Content-Type: text/plain;
  charset="us-ascii"
From: Yougu Yuan <yuanyg@cs.dartmouth.edu>
Reply-To: yuanyg@cs.dartmouth.edu
Organization: Dept. of Computer Science, Dartmouth College
To: manet@ietf.org
Date: Tue, 26 Nov 2002 14:13:23 -0500
User-Agent: KMail/1.4.3
MIME-Version: 1.0
Content-Transfer-Encoding: 8bit
Message-Id: <200211261413.23998.yuanyg@cs.dartmouth.edu>
Content-Transfer-Encoding: 8bit
Subject: [manet] MAC & PHY interaction question
Sender: manet-admin@ietf.org
Errors-To: manet-admin@ietf.org
X-BeenThere: manet@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/manet>,
	<mailto:manet-request@ietf.org?subject=unsubscribe>
List-Id: Mobile Ad-hoc Networks  <manet.ietf.org>
List-Post: <mailto:manet@ietf.org>
List-Help: <mailto:manet-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/manet>,
	<mailto:manet-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 8bit
Content-Transfer-Encoding: 8bit

Hi, all,

Here is a question about the interaction between the wireless MAC layer and 
the physical layer, but I think a "hardware" person is more likely to answer 
it without a pause.

If the phy is receiving a packet, during which a "new" stronger ( >old signal 
strength + capture threshold)  signal shows up, is the physical layer able to 
tell that this is a "new signal", and start to notify the MAC layer to 
receive this new packet? Or will it go on blindly, only find out that there 
is a collision after receiving the old packet by checking the CRC, and unable 
to recieve either packet in a whole piece?

Thank you.
-- 
Yougu Yuan

----------------------------------------------------
Office Phone 603-646-0679    yuanyg@cs.dartmouth.edu
Dept. of Computer Science, Dartmouth College

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



From manet-admin@ietf.org  Tue Nov 26 14:25:39 2002
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA16964
	for <manet-archive@lists.ietf.org>; Tue, 26 Nov 2002 14:25:39 -0500 (EST)
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gAQJIRv18844;
	Tue, 26 Nov 2002 14:18:27 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gAQJDRv18539
	for <manet@optimus.ietf.org>; Tue, 26 Nov 2002 14:13:27 -0500
Received: from cs.dartmouth.edu (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA16450
	for <manet@ietf.org>; Tue, 26 Nov 2002 14:10:36 -0500 (EST)
Received: from localhost.localdomain (dhcp48.ISTS.dartmouth.edu [129.170.249.148])
	by cs.dartmouth.edu (8.12.1/8.11.4) with ESMTP id gAQJDFRB001001
	for <manet@ietf.org>; Tue, 26 Nov 2002 14:13:15 -0500
Content-Type: text/plain;
  charset="us-ascii"
From: Yougu Yuan <yuanyg@cs.dartmouth.edu>
Reply-To: yuanyg@cs.dartmouth.edu
Organization: Dept. of Computer Science, Dartmouth College
To: manet@ietf.org
Date: Tue, 26 Nov 2002 14:13:23 -0500
User-Agent: KMail/1.4.3
MIME-Version: 1.0
Content-Transfer-Encoding: 8bit
Message-Id: <200211261413.23998.yuanyg@cs.dartmouth.edu>
Content-Transfer-Encoding: 8bit
Subject: [manet] MAC & PHY interaction question
Sender: manet-admin@ietf.org
Errors-To: manet-admin@ietf.org
X-BeenThere: manet@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/manet>,
	<mailto:manet-request@ietf.org?subject=unsubscribe>
List-Id: Mobile Ad-hoc Networks  <manet.ietf.org>
List-Post: <mailto:manet@ietf.org>
List-Help: <mailto:manet-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/manet>,
	<mailto:manet-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 8bit

Hi, all,

Here is a question about the interaction between the wireless MAC layer and 
the physical layer, but I think a "hardware" person is more likely to answer 
it without a pause.

If the phy is receiving a packet, during which a "new" stronger ( >old signal 
strength + capture threshold)  signal shows up, is the physical layer able to 
tell that this is a "new signal", and start to notify the MAC layer to 
receive this new packet? Or will it go on blindly, only find out that there 
is a collision after receiving the old packet by checking the CRC, and unable 
to recieve either packet in a whole piece?

Thank you.
-- 
Yougu Yuan

----------------------------------------------------
Office Phone 603-646-0679    yuanyg@cs.dartmouth.edu
Dept. of Computer Science, Dartmouth College

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


From manet-admin@ietf.org  Tue Nov 26 14:33:32 2002
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA17319
	for <manet-archive@lists.ietf.org>; Tue, 26 Nov 2002 14:33:32 -0500 (EST)
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gAQJRHv19267;
	Tue, 26 Nov 2002 14:27:17 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gAQJOCv19153
	for <manet@optimus.ietf.org>; Tue, 26 Nov 2002 14:24:12 -0500
Received: from ns0.utdallas.edu (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA16821
	for <manet@ietf.org>; Tue, 26 Nov 2002 14:21:24 -0500 (EST)
Received: from babbage.utdallas.edu (babbage.utdallas.edu [129.110.49.22])
	by ns0.utdallas.edu (Postfix) with ESMTP
	id 5F7341A2509; Tue, 26 Nov 2002 13:24:06 -0600 (CST)
Received: by babbage.utdallas.edu (Postfix, from userid 6644)
	id B760F15EA17; Tue, 26 Nov 2002 13:24:03 -0600 (CST)
Received: from localhost (localhost [127.0.0.1])
	by babbage.utdallas.edu (Postfix) with ESMTP
	id A33FC152415; Tue, 26 Nov 2002 13:24:03 -0600 (CST)
Date: Tue, 26 Nov 2002 13:24:03 -0600 (CST)
From: Don Montgomery <montgo@utdallas.edu>
To: Yougu Yuan <yuanyg@cs.dartmouth.edu>
Cc: manet@ietf.org
Subject: Re: [manet] MAC & PHY interaction question
In-Reply-To: <200211261413.23998.yuanyg@cs.dartmouth.edu>
Message-ID: <Pine.GSO.4.21.0211261322070.23431-100000@babbage.utdallas.edu>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: manet-admin@ietf.org
Errors-To: manet-admin@ietf.org
X-BeenThere: manet@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/manet>,
	<mailto:manet-request@ietf.org?subject=unsubscribe>
List-Id: Mobile Ad-hoc Networks  <manet.ietf.org>
List-Post: <mailto:manet@ietf.org>
List-Help: <mailto:manet-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/manet>,
	<mailto:manet-request@ietf.org?subject=subscribe>


Hi Yougu,

In the case you pose, I believe there will be a collision
no matter what the rxg node does.  The PHY/MAC models I
have seen studied here assume a single channel.

Don

On Tue, 26 Nov 2002, Yougu Yuan wrote:

Hi, all,

Here is a question about the interaction between the wireless MAC layer and 
the physical layer, but I think a "hardware" person is more likely to answer 
it without a pause.

If the phy is receiving a packet, during which a "new" stronger ( >old signal 
strength + capture threshold)  signal shows up, is the physical layer able to 
tell that this is a "new signal", and start to notify the MAC layer to 
receive this new packet? Or will it go on blindly, only find out that there 
is a collision after receiving the old packet by checking the CRC, and unable 
to recieve either packet in a whole piece?

Thank you.
-- 
Yougu Yuan

----------------------------------------------------
Office Phone 603-646-0679    yuanyg@cs.dartmouth.edu
Dept. of Computer Science, Dartmouth College

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

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


From mailnull@www1.ietf.org  Tue Nov 26 14:40:00 2002
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA17582
	for <manet-archive@odin.ietf.org>; Tue, 26 Nov 2002 14:40:00 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id gAQJgGY20786
	for manet-archive@odin.ietf.org; Tue, 26 Nov 2002 14:42:16 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gAQJgGv20783
	for <manet-web-archive@optimus.ietf.org>; Tue, 26 Nov 2002 14:42:16 -0500
Received: from www1.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA17550
	for <manet-web-archive@ietf.org>; Tue, 26 Nov 2002 14:39:27 -0500 (EST)
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gAQJRHv19267;
	Tue, 26 Nov 2002 14:27:17 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gAQJOCv19153
	for <manet@optimus.ietf.org>; Tue, 26 Nov 2002 14:24:12 -0500
Received: from ns0.utdallas.edu (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA16821
	for <manet@ietf.org>; Tue, 26 Nov 2002 14:21:24 -0500 (EST)
Received: from babbage.utdallas.edu (babbage.utdallas.edu [129.110.49.22])
	by ns0.utdallas.edu (Postfix) with ESMTP
	id 5F7341A2509; Tue, 26 Nov 2002 13:24:06 -0600 (CST)
Received: by babbage.utdallas.edu (Postfix, from userid 6644)
	id B760F15EA17; Tue, 26 Nov 2002 13:24:03 -0600 (CST)
Received: from localhost (localhost [127.0.0.1])
	by babbage.utdallas.edu (Postfix) with ESMTP
	id A33FC152415; Tue, 26 Nov 2002 13:24:03 -0600 (CST)
Date: Tue, 26 Nov 2002 13:24:03 -0600 (CST)
From: Don Montgomery <montgo@utdallas.edu>
To: Yougu Yuan <yuanyg@cs.dartmouth.edu>
Cc: manet@ietf.org
Subject: Re: [manet] MAC & PHY interaction question
In-Reply-To: <200211261413.23998.yuanyg@cs.dartmouth.edu>
Message-ID: <Pine.GSO.4.21.0211261322070.23431-100000@babbage.utdallas.edu>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: manet-admin@ietf.org
Errors-To: manet-admin@ietf.org
X-BeenThere: manet@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/manet>,
	<mailto:manet-request@ietf.org?subject=unsubscribe>
List-Id: Mobile Ad-hoc Networks  <manet.ietf.org>
List-Post: <mailto:manet@ietf.org>
List-Help: <mailto:manet-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/manet>,
	<mailto:manet-request@ietf.org?subject=subscribe>


Hi Yougu,

In the case you pose, I believe there will be a collision
no matter what the rxg node does.  The PHY/MAC models I
have seen studied here assume a single channel.

Don

On Tue, 26 Nov 2002, Yougu Yuan wrote:

Hi, all,

Here is a question about the interaction between the wireless MAC layer and 
the physical layer, but I think a "hardware" person is more likely to answer 
it without a pause.

If the phy is receiving a packet, during which a "new" stronger ( >old signal 
strength + capture threshold)  signal shows up, is the physical layer able to 
tell that this is a "new signal", and start to notify the MAC layer to 
receive this new packet? Or will it go on blindly, only find out that there 
is a collision after receiving the old packet by checking the CRC, and unable 
to recieve either packet in a whole piece?

Thank you.
-- 
Yougu Yuan

----------------------------------------------------
Office Phone 603-646-0679    yuanyg@cs.dartmouth.edu
Dept. of Computer Science, Dartmouth College

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

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



From mailnull@www1.ietf.org  Tue Nov 26 14:42:43 2002
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA17677
	for <manet-archive@odin.ietf.org>; Tue, 26 Nov 2002 14:42:43 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id gAQJj0d20870
	for manet-archive@odin.ietf.org; Tue, 26 Nov 2002 14:45:00 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gAQJj0v20867
	for <manet-web-archive@optimus.ietf.org>; Tue, 26 Nov 2002 14:45:00 -0500
Received: from www1.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA17641
	for <manet-web-archive@ietf.org>; Tue, 26 Nov 2002 14:42:12 -0500 (EST)
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gAQIZnv14889;
	Tue, 26 Nov 2002 13:35:51 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gAQIT5v14132
	for <manet@optimus.ietf.org>; Tue, 26 Nov 2002 13:29:05 -0500
Received: from webserver.redes.unb.br (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA14314
	for <manet@ietf.org>; Tue, 26 Nov 2002 13:26:15 -0500 (EST)
Received: from piqui (redesfw.redes.unb.br [164.41.67.254])
	by webserver.redes.unb.br (8.12.5/8.12.5) with SMTP id gAQHkYC5026124
	for <manet@ietf.org>; Tue, 26 Nov 2002 15:46:34 -0200
Message-ID: <007e01c2957a$a140c340$0e43a8c0@piqui>
From: =?iso-8859-1?Q?F=E1bio_Buiati?= <fabio@redes.unb.br>
To: <manet@ietf.org>
Date: Tue, 26 Nov 2002 16:35:26 -0200
MIME-Version: 1.0
Content-Type: multipart/alternative;
	boundary="----=_NextPart_000_007B_01C29569.D2F03EE0"
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 6.00.2720.3000
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2600.0000
Subject: [manet] Research news
Sender: manet-admin@ietf.org
Errors-To: manet-admin@ietf.org
X-BeenThere: manet@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/manet>,
	<mailto:manet-request@ietf.org?subject=unsubscribe>
List-Id: Mobile Ad-hoc Networks  <manet.ietf.org>
List-Post: <mailto:manet@ietf.org>
List-Help: <mailto:manet-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/manet>,
	<mailto:manet-request@ietf.org?subject=subscribe>

This is a multi-part message in MIME format.

------=_NextPart_000_007B_01C29569.D2F03EE0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

Hi all.
I would like which are new research areas? IDS for Manets, Personal =
Firewall, ...

Thanks a lot.
---------------------------------------------------
F=E1bio Mesquita Buiati
email - fabio@redes.unb.br
Bras=EDlia - Brazil
---------------------------------------------------

------=_NextPart_000_007B_01C29569.D2F03EE0
Content-Type: text/html;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META http-equiv=3DContent-Type content=3D"text/html; =
charset=3Diso-8859-1">
<META content=3D"MSHTML 6.00.2722.900" name=3DGENERATOR>
<STYLE></STYLE>
</HEAD>
<BODY bgColor=3D#ffffff>
<DIV><FONT face=3DArial size=3D2>Hi all.</FONT></DIV>
<DIV><FONT face=3DArial size=3D2>I would like which are new research =
areas? IDS for=20
Manets, Personal Firewall, ...</FONT></DIV>
<DIV><FONT face=3DArial size=3D2></FONT>&nbsp;</DIV>
<DIV><FONT face=3DArial size=3D2>Thanks a lot.</FONT></DIV>
<DIV><FONT face=3DArial=20
size=3D2>---------------------------------------------------<BR>F=E1bio =
Mesquita=20
Buiati<BR>email - <A=20
href=3D"mailto:fabio@redes.unb.br">fabio@redes.unb.br</A><BR>Bras=EDlia =
-=20
Brazil</FONT></DIV>
<DIV><FONT face=3DArial=20
size=3D2>---------------------------------------------------</FONT></DIV>=
</BODY></HTML>

------=_NextPart_000_007B_01C29569.D2F03EE0--

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



From manet-admin@ietf.org  Tue Nov 26 14:43:19 2002
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA17715
	for <manet-archive@lists.ietf.org>; Tue, 26 Nov 2002 14:43:18 -0500 (EST)
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gAQIZnv14889;
	Tue, 26 Nov 2002 13:35:51 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gAQIT5v14132
	for <manet@optimus.ietf.org>; Tue, 26 Nov 2002 13:29:05 -0500
Received: from webserver.redes.unb.br (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA14314
	for <manet@ietf.org>; Tue, 26 Nov 2002 13:26:15 -0500 (EST)
Received: from piqui (redesfw.redes.unb.br [164.41.67.254])
	by webserver.redes.unb.br (8.12.5/8.12.5) with SMTP id gAQHkYC5026124
	for <manet@ietf.org>; Tue, 26 Nov 2002 15:46:34 -0200
Message-ID: <007e01c2957a$a140c340$0e43a8c0@piqui>
From: =?iso-8859-1?Q?F=E1bio_Buiati?= <fabio@redes.unb.br>
To: <manet@ietf.org>
Date: Tue, 26 Nov 2002 16:35:26 -0200
MIME-Version: 1.0
Content-Type: multipart/alternative;
	boundary="----=_NextPart_000_007B_01C29569.D2F03EE0"
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 6.00.2720.3000
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2600.0000
Subject: [manet] Research news
Sender: manet-admin@ietf.org
Errors-To: manet-admin@ietf.org
X-BeenThere: manet@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/manet>,
	<mailto:manet-request@ietf.org?subject=unsubscribe>
List-Id: Mobile Ad-hoc Networks  <manet.ietf.org>
List-Post: <mailto:manet@ietf.org>
List-Help: <mailto:manet-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/manet>,
	<mailto:manet-request@ietf.org?subject=subscribe>

This is a multi-part message in MIME format.

------=_NextPart_000_007B_01C29569.D2F03EE0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

Hi all.
I would like which are new research areas? IDS for Manets, Personal =
Firewall, ...

Thanks a lot.
---------------------------------------------------
F=E1bio Mesquita Buiati
email - fabio@redes.unb.br
Bras=EDlia - Brazil
---------------------------------------------------

------=_NextPart_000_007B_01C29569.D2F03EE0
Content-Type: text/html;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META http-equiv=3DContent-Type content=3D"text/html; =
charset=3Diso-8859-1">
<META content=3D"MSHTML 6.00.2722.900" name=3DGENERATOR>
<STYLE></STYLE>
</HEAD>
<BODY bgColor=3D#ffffff>
<DIV><FONT face=3DArial size=3D2>Hi all.</FONT></DIV>
<DIV><FONT face=3DArial size=3D2>I would like which are new research =
areas? IDS for=20
Manets, Personal Firewall, ...</FONT></DIV>
<DIV><FONT face=3DArial size=3D2></FONT>&nbsp;</DIV>
<DIV><FONT face=3DArial size=3D2>Thanks a lot.</FONT></DIV>
<DIV><FONT face=3DArial=20
size=3D2>---------------------------------------------------<BR>F=E1bio =
Mesquita=20
Buiati<BR>email - <A=20
href=3D"mailto:fabio@redes.unb.br">fabio@redes.unb.br</A><BR>Bras=EDlia =
-=20
Brazil</FONT></DIV>
<DIV><FONT face=3DArial=20
size=3D2>---------------------------------------------------</FONT></DIV>=
</BODY></HTML>

------=_NextPart_000_007B_01C29569.D2F03EE0--

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


From manet-admin@ietf.org  Tue Nov 26 15:16:52 2002
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA18876
	for <manet-archive@lists.ietf.org>; Tue, 26 Nov 2002 15:16:52 -0500 (EST)
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gAQKAJv22658;
	Tue, 26 Nov 2002 15:10:19 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gAQK1Dv21700
	for <manet@optimus.ietf.org>; Tue, 26 Nov 2002 15:01:13 -0500
Received: from cheech.nmsu.edu (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA18251
	for <manet@ietf.org>; Tue, 26 Nov 2002 14:58:20 -0500 (EST)
From: jomullen@nmsu.edu
Received: (from nobody@localhost)
	by cheech.nmsu.edu (8.11.6/8.11.6) id gAQKG0014130
	for manet@ietf.org; Tue, 26 Nov 2002 13:16:00 -0700
Received: from 155.148.36.131 ( [155.148.36.131])
	as user jomullen@imap.nmsu.edu by webmail.nmsu.edu with HTTP;
	Tue, 26 Nov 2002 13:16:00 -0700
Message-ID: <1038341760.3de3d6803134b@webmail.nmsu.edu>
Date: Tue, 26 Nov 2002 13:16:00 -0700
To: manet@ietf.org
Subject: Re: [manet] Open this befo=?ISO-8859-1?B?cmUg0+/J+be9sc/Fvg==?=
References: <200211260127.UAA04652@ietf.org>
In-Reply-To: <200211260127.UAA04652@ietf.org>
MIME-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 8bit
User-Agent: Internet Messaging Program (IMP) 3.0
X-Originating-IP: 155.148.36.131
Content-Transfer-Encoding: 8bit
Sender: manet-admin@ietf.org
Errors-To: manet-admin@ietf.org
X-BeenThere: manet@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/manet>,
	<mailto:manet-request@ietf.org?subject=unsubscribe>
List-Id: Mobile Ad-hoc Networks  <manet.ietf.org>
List-Post: <mailto:manet@ietf.org>
List-Help: <mailto:manet-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/manet>,
	<mailto:manet-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 8bit

The referenced email appears to be a virus.

John Mullen

> ------------------  Virus Warning Message (on ietf-mx)
> 
> 024.bat is of type executable and is removed.
> 
> Please contact your network administrator for further information.
> 
> ---------------------------------------------------------
> 


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


From mailnull@www1.ietf.org  Tue Nov 26 15:22:51 2002
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA19130
	for <manet-archive@odin.ietf.org>; Tue, 26 Nov 2002 15:22:51 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id gAQKP9i23336
	for manet-archive@odin.ietf.org; Tue, 26 Nov 2002 15:25:09 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gAQKP9v23333
	for <manet-web-archive@optimus.ietf.org>; Tue, 26 Nov 2002 15:25:09 -0500
Received: from www1.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA19104
	for <manet-web-archive@ietf.org>; Tue, 26 Nov 2002 15:22:20 -0500 (EST)
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gAQKAJv22658;
	Tue, 26 Nov 2002 15:10:19 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gAQK1Dv21700
	for <manet@optimus.ietf.org>; Tue, 26 Nov 2002 15:01:13 -0500
Received: from cheech.nmsu.edu (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA18251
	for <manet@ietf.org>; Tue, 26 Nov 2002 14:58:20 -0500 (EST)
From: jomullen@nmsu.edu
Received: (from nobody@localhost)
	by cheech.nmsu.edu (8.11.6/8.11.6) id gAQKG0014130
	for manet@ietf.org; Tue, 26 Nov 2002 13:16:00 -0700
Received: from 155.148.36.131 ( [155.148.36.131])
	as user jomullen@imap.nmsu.edu by webmail.nmsu.edu with HTTP;
	Tue, 26 Nov 2002 13:16:00 -0700
Message-ID: <1038341760.3de3d6803134b@webmail.nmsu.edu>
Date: Tue, 26 Nov 2002 13:16:00 -0700
To: manet@ietf.org
Subject: Re: [manet] Open this befo=?ISO-8859-1?B?cmUg0+/J+be9sc/Fvg==?=
References: <200211260127.UAA04652@ietf.org>
In-Reply-To: <200211260127.UAA04652@ietf.org>
MIME-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 8bit
User-Agent: Internet Messaging Program (IMP) 3.0
X-Originating-IP: 155.148.36.131
Content-Transfer-Encoding: 8bit
Sender: manet-admin@ietf.org
Errors-To: manet-admin@ietf.org
X-BeenThere: manet@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/manet>,
	<mailto:manet-request@ietf.org?subject=unsubscribe>
List-Id: Mobile Ad-hoc Networks  <manet.ietf.org>
List-Post: <mailto:manet@ietf.org>
List-Help: <mailto:manet-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/manet>,
	<mailto:manet-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 8bit
Content-Transfer-Encoding: 8bit

The referenced email appears to be a virus.

John Mullen

> ------------------  Virus Warning Message (on ietf-mx)
> 
> 024.bat is of type executable and is removed.
> 
> Please contact your network administrator for further information.
> 
> ---------------------------------------------------------
> 


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



From manet-admin@ietf.org  Tue Nov 26 16:12:52 2002
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA20945
	for <manet-archive@lists.ietf.org>; Tue, 26 Nov 2002 16:12:52 -0500 (EST)
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gAQL2pv25357;
	Tue, 26 Nov 2002 16:02:51 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gAQKx3v25200
	for <manet@optimus.ietf.org>; Tue, 26 Nov 2002 15:59:03 -0500
Received: from mail.flarion.com (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA20335
	for <manet@ietf.org>; Tue, 26 Nov 2002 15:56:14 -0500 (EST)
Received: by rrmail01.lab.flarion.com with Internet Mail Service (5.5.2656.59)
	id <X4YYS3RG>; Tue, 26 Nov 2002 15:58:56 -0500
Message-ID: <748C6D0A58C0F94CA63C198B6674697AA5CFB3@ftmail.lab.flarion.com>
From: Scott Corson <Corson@flarion.com>
To: "'Manet (manet@ietf.org)'" <manet@ietf.org>
Date: Tue, 26 Nov 2002 15:58:54 -0500
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2656.59)
Content-Type: text/plain
Subject: [manet] FW: [mobile-ip] Dynamic Interfaces (was: 50 ms RA timer?)
Sender: manet-admin@ietf.org
Errors-To: manet-admin@ietf.org
X-BeenThere: manet@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/manet>,
	<mailto:manet-request@ietf.org?subject=unsubscribe>
List-Id: Mobile Ad-hoc Networks  <manet.ietf.org>
List-Post: <mailto:manet@ietf.org>
List-Help: <mailto:manet-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/manet>,
	<mailto:manet-request@ietf.org?subject=subscribe>

Oops...  meant to send this here.

-Scott

-----Original Message-----
From: Scott Corson [mailto:Corson@flarion.com] 
Sent: Tuesday, November 26, 2002 3:53 PM
To: 'Charles E. Perkins'; 'James Kempf'
Cc: 'mobile-ip@sunroof.eng.sun.com'; 'Manet (manet@itd.nrl.navy.mil)'
Subject: [mobile-ip] Dynamic Interfaces (was: 50 ms RA timer?)


> for Internet connectivity.  Mobile IP seemed to be quite well-regarded
> as a beneficial technology there.  I mentioned a couple of my
> pet peeves about current 802.11 device drivers and delays, and
> I got the impression that many (not all!) IEEE engineers in the
> meeting wanted to ensure that future products would work well
> with Mobile IP.

Increasingly, as the understanding permeates the industry that link layers
come and go, yet IP remains, link layer folks will begin to explicitly
design (or minimally to optimize) their technologies to plug into the
underbelly of an IP network.

The best thing the IETF could do IMHO would be to begin to *help* these
folks out.  

There is an increasingly broad class of link layer technologies under
development that, collectively, exhibit very 'dynamic' behavior.
Intermittent and varying connectivity is the norm, not the exception, for
this class of technologies.  And they need not be mobile technologies,
although this is the common case.

I think the IETF should define (or put into common practice) what is
essentially a new interface type--a "dynamic" interface--to be chosen for
use by these technologies if desired.  It should likely retain the
addressing semantics of a 'broadcast' interface--link layer unicast,
broadcast and multicast--yet ensure that the efficient, dynamic discovery of
'point-to-point' relationships between neighboring interfaces (generally
thru link layer mechanisms) can be communicated to the IP stack in a
standard way.  This mechanism would enable an IP stack to interact with this
new interface type in new ways.  This essentially requires standardizing
IP's "underbelly"--a term that Phil N. recently introduced on the PILC
list--to understand and work with dynamic interfaces.  

A 50ms RA timer is a pretty blunt instrument for assessing next-hop
reachability, and is inapplicable in many deployment scenarios.  If that is
the best you can do, then perhaps that is an answer, but it's certainly not
THE answer.  

A dynamic interface construct would be extremely general, and would likely
solve the problems that the recent interest in work on L2 triggers has hoped
to address.  It would apply to many technologies, and be useful in many
contexts where Mobile IP, MANET, Nemo and other such network layer protocols
must deal with link layer dynamics in a timely fashion.  It should also be
understood that the prerogative to act, to delay or to suppress these events
is still under the control of the IP layer.

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


From mailnull@www1.ietf.org  Tue Nov 26 16:19:02 2002
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA21268
	for <manet-archive@odin.ietf.org>; Tue, 26 Nov 2002 16:19:01 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id gAQLLKU27201
	for manet-archive@odin.ietf.org; Tue, 26 Nov 2002 16:21:20 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gAQLLKv27198
	for <manet-web-archive@optimus.ietf.org>; Tue, 26 Nov 2002 16:21:20 -0500
Received: from www1.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA21261
	for <manet-web-archive@ietf.org>; Tue, 26 Nov 2002 16:18:30 -0500 (EST)
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gAQL2pv25357;
	Tue, 26 Nov 2002 16:02:51 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gAQKx3v25200
	for <manet@optimus.ietf.org>; Tue, 26 Nov 2002 15:59:03 -0500
Received: from mail.flarion.com (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA20335
	for <manet@ietf.org>; Tue, 26 Nov 2002 15:56:14 -0500 (EST)
Received: by rrmail01.lab.flarion.com with Internet Mail Service (5.5.2656.59)
	id <X4YYS3RG>; Tue, 26 Nov 2002 15:58:56 -0500
Message-ID: <748C6D0A58C0F94CA63C198B6674697AA5CFB3@ftmail.lab.flarion.com>
From: Scott Corson <Corson@flarion.com>
To: "'Manet (manet@ietf.org)'" <manet@ietf.org>
Date: Tue, 26 Nov 2002 15:58:54 -0500
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2656.59)
Content-Type: text/plain
Subject: [manet] FW: [mobile-ip] Dynamic Interfaces (was: 50 ms RA timer?)
Sender: manet-admin@ietf.org
Errors-To: manet-admin@ietf.org
X-BeenThere: manet@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/manet>,
	<mailto:manet-request@ietf.org?subject=unsubscribe>
List-Id: Mobile Ad-hoc Networks  <manet.ietf.org>
List-Post: <mailto:manet@ietf.org>
List-Help: <mailto:manet-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/manet>,
	<mailto:manet-request@ietf.org?subject=subscribe>

Oops...  meant to send this here.

-Scott

-----Original Message-----
From: Scott Corson [mailto:Corson@flarion.com] 
Sent: Tuesday, November 26, 2002 3:53 PM
To: 'Charles E. Perkins'; 'James Kempf'
Cc: 'mobile-ip@sunroof.eng.sun.com'; 'Manet (manet@itd.nrl.navy.mil)'
Subject: [mobile-ip] Dynamic Interfaces (was: 50 ms RA timer?)


> for Internet connectivity.  Mobile IP seemed to be quite well-regarded
> as a beneficial technology there.  I mentioned a couple of my
> pet peeves about current 802.11 device drivers and delays, and
> I got the impression that many (not all!) IEEE engineers in the
> meeting wanted to ensure that future products would work well
> with Mobile IP.

Increasingly, as the understanding permeates the industry that link layers
come and go, yet IP remains, link layer folks will begin to explicitly
design (or minimally to optimize) their technologies to plug into the
underbelly of an IP network.

The best thing the IETF could do IMHO would be to begin to *help* these
folks out.  

There is an increasingly broad class of link layer technologies under
development that, collectively, exhibit very 'dynamic' behavior.
Intermittent and varying connectivity is the norm, not the exception, for
this class of technologies.  And they need not be mobile technologies,
although this is the common case.

I think the IETF should define (or put into common practice) what is
essentially a new interface type--a "dynamic" interface--to be chosen for
use by these technologies if desired.  It should likely retain the
addressing semantics of a 'broadcast' interface--link layer unicast,
broadcast and multicast--yet ensure that the efficient, dynamic discovery of
'point-to-point' relationships between neighboring interfaces (generally
thru link layer mechanisms) can be communicated to the IP stack in a
standard way.  This mechanism would enable an IP stack to interact with this
new interface type in new ways.  This essentially requires standardizing
IP's "underbelly"--a term that Phil N. recently introduced on the PILC
list--to understand and work with dynamic interfaces.  

A 50ms RA timer is a pretty blunt instrument for assessing next-hop
reachability, and is inapplicable in many deployment scenarios.  If that is
the best you can do, then perhaps that is an answer, but it's certainly not
THE answer.  

A dynamic interface construct would be extremely general, and would likely
solve the problems that the recent interest in work on L2 triggers has hoped
to address.  It would apply to many technologies, and be useful in many
contexts where Mobile IP, MANET, Nemo and other such network layer protocols
must deal with link layer dynamics in a timely fashion.  It should also be
understood that the prerogative to act, to delay or to suppress these events
is still under the control of the IP layer.

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



From mailnull@www1.ietf.org  Tue Nov 26 18:00:24 2002
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA24832
	for <manet-archive@odin.ietf.org>; Tue, 26 Nov 2002 18:00:24 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id gAQN2iu01269
	for manet-archive@odin.ietf.org; Tue, 26 Nov 2002 18:02:44 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gAQN2iv01266
	for <manet-web-archive@optimus.ietf.org>; Tue, 26 Nov 2002 18:02:44 -0500
Received: from www1.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA24797
	for <manet-web-archive@ietf.org>; Tue, 26 Nov 2002 17:59:53 -0500 (EST)
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gAQMrav00864;
	Tue, 26 Nov 2002 17:53:36 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gAQMn6v00736
	for <manet@optimus.ietf.org>; Tue, 26 Nov 2002 17:49:06 -0500
Received: from itd.nrl.navy.mil (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA24324;
	Tue, 26 Nov 2002 17:46:15 -0500 (EST)
Received: from smtp.itd.nrl.navy.mil (smtp.itd.nrl.navy.mil [132.250.86.3])
	by itd.nrl.navy.mil (8.8.8+Sun/8.8.8) with SMTP id RAA15644;
	Tue, 26 Nov 2002 17:48:58 -0500 (EST)
Received: from SEXTANT.itd.nrl.navy.mil ([132.250.92.22])
 by smtp.itd.nrl.navy.mil (SAVSMTP 3.0.0.44) with SMTP id M2002112617485828857
 ; Tue, 26 Nov 2002 17:48:58 -0500
Message-Id: <5.1.1.5.2.20021126173851.02f108f8@pop.itd.nrl.navy.mil>
X-Sender: macker@pop.itd.nrl.navy.mil
X-Mailer: QUALCOMM Windows Eudora Version 5.1.1
Date: Tue, 26 Nov 2002 17:48:31 -0500
To: minutes@ietf.org
From: Joe Macker <macker@itd.nrl.navy.mil>
Cc: manet@ietf.org
Mime-Version: 1.0
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: 8bit
X-MIME-Autoconverted: from quoted-printable to 8bit by www1.ietf.org id gAQMn6v00737
Subject: [manet] MANET minutes
Sender: manet-admin@ietf.org
Errors-To: manet-admin@ietf.org
X-BeenThere: manet@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/manet>,
	<mailto:manet-request@ietf.org?subject=unsubscribe>
List-Id: Mobile Ad-hoc Networks  <manet.ietf.org>
List-Post: <mailto:manet@ietf.org>
List-Help: <mailto:manet-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/manet>,
	<mailto:manet-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 8bit
Content-Transfer-Encoding: 8bit

Minutes of the Mobile Ad-hoc Networks WG (manet)
55th IETF Proceedings
Thursday, Nov 21 at 1300-1500

Minutes taken by Justin Dean
==============================

CHAIRS: M. Scott Corson <corson@Glue.umd.edu> 
              Joseph Macker <macker@itd.nrl.navy.mil> 

AGENDA:

(10 min) Agenda Bashing and Announcements
(20 min) Proposed Manet Way Forward
(10 min) Strawman Proposal for Charter and Milestone Update
(10 min) Related IRTF Activity Announcement
(10 min) Open Discussion of Proposal and Issues
(15 min) TBRPF Update
(15 min) DSR Update
(15 min) OLSR Update
(15 min) AODV Update
Closing

Joe Macker presented the agenda and opened it up for bashing.
The agenda was accepted as is with no bashing.

Joe Macker had some issues regarding the manet mailing list that he wished to remind members about.

- There are 1969 members currently on the manet mailing list.
- Only members are allowed to post to the mailing list. Somewhat standard practice, but not a perfect way to reduce spam, etc.
- Manet members should be aware when switching account names so that they may still post effectively without moderator intervention.
- The newer ietf.org mailing list is reasonably automated; please use the automated features to manage your own accounts whenever possible.
- NS2, GLOMOSIM, QUALNET, OPNET simulation software questions have recently increased in volume.  Often simulation environment specific questions are not appropriate for the mass manet mailing list, members are urged to contact the authors of the code or appropriate simulation mailing list for instruction questions, FAQs, etc.
 
MANET Way Forward (for details see presentation in proceedings)

Joe Macker presented an overview of a proposed way forward for the manet WG that was being worked on in conjunction with the ADs. Recent perceived WG status is that manet prototype implementation, designs, and experimentation are very active. However, the WG has experienced significant “research creep” into the ongoing work by continuing to consider broad work issues in the manet problem space.  It is the intention of the chairs and the ADs to update the charter of the WG to scope down to a focused engineering mode of work.  The core approach is:

·       reduce the near term scope of the present WG
·       formulate an IRTF venue for manet research items, split off related longer term research work from IETF
·       complete several mature unicast protocol ID work as EXPERIMENTAL RFCs
·       formulate a focused problem statement(s)
·       convert core work items to an engineering mode and target common Proposed Standard effort(s)

Alex Zinin: Routing co-AD (for details see presentation in proceedings)

Alex Zinin next discussed the proposed rechartering effort.  Alex mentioned that he had posted a note to the list summarizing some of the issues as they have emerged a few weeks back.  The summary is that very useful work is being done in manet, but the WG is operating under a wide problem statement.  The perception is there are many competing protocols, a lack of WG-wide consensus, and no signs of convergence. All of the above == research mode.

The goals of the proposed charter update would be to convert the WG to the IETF mode:
                Clear and focused problem statement
                Focused WG charter, clear milestones
                WG members working closely towards consensus
                Design IETF MANET protocol STD

Work that needs more research (yes, it is somewhat subjective) will move to the IRTF.

Proposed Steps:
        First, we create an IRTF sub-group for MANET and move LANMAR, FSR, ZRP, TORA and similar work into this forum.  We would scope the charter to push DSR, AODV, OLSR, and TBRPF to EXP and when done the WG will better define the engineering problems statement. IF rough agreement is reached on the problem statement we will update the charter with the development of IETF protocol(s) that will go STD tracks.

Plan of actions 

We will discuss this more here and on the mailing list (nothing so far). We will announce the decision within a month after this meeting.

Questions:
Q:      Will the rechartering approach cause delay in pushing forward EXP RFCs for certain protocols already under consideration?
A:      No, that is not intended.

Q:      Will multicast work in manets be carried out in ietf or irtf?
A:      Lots of papers on this subject already, yet it remains to be decided what is appropriate for engineering. Stay Tuned.
-------------------------------------------------------------

At this point, the Joe Macker polled the room for consensus on re-chartering direction. Room consensus was attained to re-charter based upon the approach presented..  Further mailing list input will be taken before reaching any decisions.

Strawman Recharter Presentation - Joe Macker (for details see presentation in proceedings)

Joe Macker presented some text and line items for consideration in an updated charter/milestone effort. More discussion of this will take place on the mailing list.

Strawman Near Term Milestones

Present: Restructure WG to be more narrowly focused, split off important related IRTF work
Jan 2003 SUBMIT core reactive protocols for EXPERIMENTAL RFC (if not already done)
Jan 2003 Revisit WG goals and problem statements
Mar 2003 SUBMIT core proactive protocols for EXPERIMENTAL RFC
Jun 2003 Develop and approve focused MANET WG problem statements and scoped engineering goals.

Scott Corson: IRTF MANET research subgroup

Scott presented an overview of the manet-related IRTF plan.  Scalability is the main research theme and some of the goals will be to foster discussion and better understand the limitations of existing approaches (e.g., simple flat reactive and proactive).  The group will look at proposing/developing approaches that demonstrate superior performance (e.g., Hybrid/hierarchical forms and radically new concepts).  More details will be formulated.  It has been a concern that meetings may not be long enough and it is likely that meetings may take place in concert with ongoing events to ease travel as much as possible.

A new mailing list will be set up and announced on mailing list

Q:      Will multicast be in IRTF or IETF?
A:      Depends on the problem statement that the IETF works out and it may be a mixed case given appropriate rationale of problems statements.

Q:      What is small/medium networks? Maybe 10-100 nodes but what about movement models?  What type of movement scale are we using?
A:      We are aware that dynamic link/motion models, traffic flow models, network surge conditions, and other factors affect any scalability assessment besides number of router nodes.  We need some discussion of this in problem and applicability statements.

Q: Other IETF groups have scalability in the charters so why are we getting rid of it in this charter?
A:      It is not the intention to artificially limit the potential for large area scalability, however we are not making it a requirement for engineering maturity and applicability reasons.

Comment:        IRTF should be looking at the limits of current protocols work as well.  This may be fed back to justify changing things in IETF.

Q: Would like to see IRTF and IETF groups work together closely; meetings at same conference? 
A: Yes but the IRTF participants need freedom to do their research as well.

Q:  Need to keep problem statement simple.  Where does security belong?  What about IETF issuing standard without security in it?
A:  Need to discuss closer with the routing security working group.

Comment:  I see a need for simplicity of the protocol.  
Comment:  I think it would be extremely useful to get RFCs out that can be used for 50-100 node scenarios.
Comment: HIP ipsec can help to bring improved security to manet.
Other comment: Systems are being develop that should work with wireless networks.

Chair: Great comments, but we need to move one please bring further discussions to the list.

TBRPF Update: Richard Ogier *see online presentation

TBRPF is now at Draft revision 6.  It has been rewritten to improve readability. Hello message has been modified to include relay priority similar to OLSR MPR preference.  It was clarified that tbrpf computes the equivalent of MPRs.  There is now a relay priority in each hello.. OLSR MPR willingness is same type of thing and this presents the possibility of merging with OSLR. Other details (see presentation).  There is a new SRI IPR statement registered at ietf.org.

DSR Update: Dave Johnson

(see on-line for details).  The final DSR ID for EXPERIMENTAL consideration is not finished yet.  We are trying to add a few things to back into draft. Stuff that was in version 3 of the ID.

OLSR Update: Thomas Clausen

(see on-line for details).  A new version of OLSR was update (now version 8).  Posting to ID editor was munged and the draft was posted to the list in the interim.     There are no major changes.  The feedback was that most people intending to use OLSR didn’t want all the features.  They wanted something like version 3 or 4.

AODV Update: Elizabeth Belding-Royer

AODV is now at ID version 12.  There we no major changes in this revision.  There was some clarification of local proactive repair.
        
http://sourceforge.net/projects/aodvimpl/ for aodv questions.
http://moment.cs.ucsb.edu/AODV/aodv.html



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



From manet-admin@ietf.org  Tue Nov 26 18:00:55 2002
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA24867
	for <manet-archive@lists.ietf.org>; Tue, 26 Nov 2002 18:00:55 -0500 (EST)
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gAQMrav00864;
	Tue, 26 Nov 2002 17:53:36 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gAQMn6v00736
	for <manet@optimus.ietf.org>; Tue, 26 Nov 2002 17:49:06 -0500
Received: from itd.nrl.navy.mil (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA24324;
	Tue, 26 Nov 2002 17:46:15 -0500 (EST)
Received: from smtp.itd.nrl.navy.mil (smtp.itd.nrl.navy.mil [132.250.86.3])
	by itd.nrl.navy.mil (8.8.8+Sun/8.8.8) with SMTP id RAA15644;
	Tue, 26 Nov 2002 17:48:58 -0500 (EST)
Received: from SEXTANT.itd.nrl.navy.mil ([132.250.92.22])
 by smtp.itd.nrl.navy.mil (SAVSMTP 3.0.0.44) with SMTP id M2002112617485828857
 ; Tue, 26 Nov 2002 17:48:58 -0500
Message-Id: <5.1.1.5.2.20021126173851.02f108f8@pop.itd.nrl.navy.mil>
X-Sender: macker@pop.itd.nrl.navy.mil
X-Mailer: QUALCOMM Windows Eudora Version 5.1.1
Date: Tue, 26 Nov 2002 17:48:31 -0500
To: minutes@ietf.org
From: Joe Macker <macker@itd.nrl.navy.mil>
Cc: manet@ietf.org
Mime-Version: 1.0
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: 8bit
X-MIME-Autoconverted: from quoted-printable to 8bit by www1.ietf.org id gAQMn6v00737
Subject: [manet] MANET minutes
Sender: manet-admin@ietf.org
Errors-To: manet-admin@ietf.org
X-BeenThere: manet@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/manet>,
	<mailto:manet-request@ietf.org?subject=unsubscribe>
List-Id: Mobile Ad-hoc Networks  <manet.ietf.org>
List-Post: <mailto:manet@ietf.org>
List-Help: <mailto:manet-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/manet>,
	<mailto:manet-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 8bit

Minutes of the Mobile Ad-hoc Networks WG (manet)
55th IETF Proceedings
Thursday, Nov 21 at 1300-1500

Minutes taken by Justin Dean
==============================

CHAIRS: M. Scott Corson <corson@Glue.umd.edu> 
              Joseph Macker <macker@itd.nrl.navy.mil> 

AGENDA:

(10 min) Agenda Bashing and Announcements
(20 min) Proposed Manet Way Forward
(10 min) Strawman Proposal for Charter and Milestone Update
(10 min) Related IRTF Activity Announcement
(10 min) Open Discussion of Proposal and Issues
(15 min) TBRPF Update
(15 min) DSR Update
(15 min) OLSR Update
(15 min) AODV Update
Closing

Joe Macker presented the agenda and opened it up for bashing.
The agenda was accepted as is with no bashing.

Joe Macker had some issues regarding the manet mailing list that he wished to remind members about.

- There are 1969 members currently on the manet mailing list.
- Only members are allowed to post to the mailing list. Somewhat standard practice, but not a perfect way to reduce spam, etc.
- Manet members should be aware when switching account names so that they may still post effectively without moderator intervention.
- The newer ietf.org mailing list is reasonably automated; please use the automated features to manage your own accounts whenever possible.
- NS2, GLOMOSIM, QUALNET, OPNET simulation software questions have recently increased in volume.  Often simulation environment specific questions are not appropriate for the mass manet mailing list, members are urged to contact the authors of the code or appropriate simulation mailing list for instruction questions, FAQs, etc.
 
MANET Way Forward (for details see presentation in proceedings)

Joe Macker presented an overview of a proposed way forward for the manet WG that was being worked on in conjunction with the ADs. Recent perceived WG status is that manet prototype implementation, designs, and experimentation are very active. However, the WG has experienced significant “research creep” into the ongoing work by continuing to consider broad work issues in the manet problem space.  It is the intention of the chairs and the ADs to update the charter of the WG to scope down to a focused engineering mode of work.  The core approach is:

·       reduce the near term scope of the present WG
·       formulate an IRTF venue for manet research items, split off related longer term research work from IETF
·       complete several mature unicast protocol ID work as EXPERIMENTAL RFCs
·       formulate a focused problem statement(s)
·       convert core work items to an engineering mode and target common Proposed Standard effort(s)

Alex Zinin: Routing co-AD (for details see presentation in proceedings)

Alex Zinin next discussed the proposed rechartering effort.  Alex mentioned that he had posted a note to the list summarizing some of the issues as they have emerged a few weeks back.  The summary is that very useful work is being done in manet, but the WG is operating under a wide problem statement.  The perception is there are many competing protocols, a lack of WG-wide consensus, and no signs of convergence. All of the above == research mode.

The goals of the proposed charter update would be to convert the WG to the IETF mode:
                Clear and focused problem statement
                Focused WG charter, clear milestones
                WG members working closely towards consensus
                Design IETF MANET protocol STD

Work that needs more research (yes, it is somewhat subjective) will move to the IRTF.

Proposed Steps:
        First, we create an IRTF sub-group for MANET and move LANMAR, FSR, ZRP, TORA and similar work into this forum.  We would scope the charter to push DSR, AODV, OLSR, and TBRPF to EXP and when done the WG will better define the engineering problems statement. IF rough agreement is reached on the problem statement we will update the charter with the development of IETF protocol(s) that will go STD tracks.

Plan of actions 

We will discuss this more here and on the mailing list (nothing so far). We will announce the decision within a month after this meeting.

Questions:
Q:      Will the rechartering approach cause delay in pushing forward EXP RFCs for certain protocols already under consideration?
A:      No, that is not intended.

Q:      Will multicast work in manets be carried out in ietf or irtf?
A:      Lots of papers on this subject already, yet it remains to be decided what is appropriate for engineering. Stay Tuned.
-------------------------------------------------------------

At this point, the Joe Macker polled the room for consensus on re-chartering direction. Room consensus was attained to re-charter based upon the approach presented..  Further mailing list input will be taken before reaching any decisions.

Strawman Recharter Presentation - Joe Macker (for details see presentation in proceedings)

Joe Macker presented some text and line items for consideration in an updated charter/milestone effort. More discussion of this will take place on the mailing list.

Strawman Near Term Milestones

Present: Restructure WG to be more narrowly focused, split off important related IRTF work
Jan 2003 SUBMIT core reactive protocols for EXPERIMENTAL RFC (if not already done)
Jan 2003 Revisit WG goals and problem statements
Mar 2003 SUBMIT core proactive protocols for EXPERIMENTAL RFC
Jun 2003 Develop and approve focused MANET WG problem statements and scoped engineering goals.

Scott Corson: IRTF MANET research subgroup

Scott presented an overview of the manet-related IRTF plan.  Scalability is the main research theme and some of the goals will be to foster discussion and better understand the limitations of existing approaches (e.g., simple flat reactive and proactive).  The group will look at proposing/developing approaches that demonstrate superior performance (e.g., Hybrid/hierarchical forms and radically new concepts).  More details will be formulated.  It has been a concern that meetings may not be long enough and it is likely that meetings may take place in concert with ongoing events to ease travel as much as possible.

A new mailing list will be set up and announced on mailing list

Q:      Will multicast be in IRTF or IETF?
A:      Depends on the problem statement that the IETF works out and it may be a mixed case given appropriate rationale of problems statements.

Q:      What is small/medium networks? Maybe 10-100 nodes but what about movement models?  What type of movement scale are we using?
A:      We are aware that dynamic link/motion models, traffic flow models, network surge conditions, and other factors affect any scalability assessment besides number of router nodes.  We need some discussion of this in problem and applicability statements.

Q: Other IETF groups have scalability in the charters so why are we getting rid of it in this charter?
A:      It is not the intention to artificially limit the potential for large area scalability, however we are not making it a requirement for engineering maturity and applicability reasons.

Comment:        IRTF should be looking at the limits of current protocols work as well.  This may be fed back to justify changing things in IETF.

Q: Would like to see IRTF and IETF groups work together closely; meetings at same conference? 
A: Yes but the IRTF participants need freedom to do their research as well.

Q:  Need to keep problem statement simple.  Where does security belong?  What about IETF issuing standard without security in it?
A:  Need to discuss closer with the routing security working group.

Comment:  I see a need for simplicity of the protocol.  
Comment:  I think it would be extremely useful to get RFCs out that can be used for 50-100 node scenarios.
Comment: HIP ipsec can help to bring improved security to manet.
Other comment: Systems are being develop that should work with wireless networks.

Chair: Great comments, but we need to move one please bring further discussions to the list.

TBRPF Update: Richard Ogier *see online presentation

TBRPF is now at Draft revision 6.  It has been rewritten to improve readability. Hello message has been modified to include relay priority similar to OLSR MPR preference.  It was clarified that tbrpf computes the equivalent of MPRs.  There is now a relay priority in each hello.. OLSR MPR willingness is same type of thing and this presents the possibility of merging with OSLR. Other details (see presentation).  There is a new SRI IPR statement registered at ietf.org.

DSR Update: Dave Johnson

(see on-line for details).  The final DSR ID for EXPERIMENTAL consideration is not finished yet.  We are trying to add a few things to back into draft. Stuff that was in version 3 of the ID.

OLSR Update: Thomas Clausen

(see on-line for details).  A new version of OLSR was update (now version 8).  Posting to ID editor was munged and the draft was posted to the list in the interim.     There are no major changes.  The feedback was that most people intending to use OLSR didn’t want all the features.  They wanted something like version 3 or 4.

AODV Update: Elizabeth Belding-Royer

AODV is now at ID version 12.  There we no major changes in this revision.  There was some clarification of local proactive repair.
        
http://sourceforge.net/projects/aodvimpl/ for aodv questions.
http://moment.cs.ucsb.edu/AODV/aodv.html



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


From mailnull@www1.ietf.org  Wed Nov 27 13:04:31 2002
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA22016
	for <manet-archive@odin.ietf.org>; Wed, 27 Nov 2002 13:04:31 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id gARI6oT13512
	for manet-archive@odin.ietf.org; Wed, 27 Nov 2002 13:06:50 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gARI6nv13509
	for <manet-web-archive@optimus.ietf.org>; Wed, 27 Nov 2002 13:06:49 -0500
Received: from www1.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA22010
	for <manet-web-archive@ietf.org>; Wed, 27 Nov 2002 13:03:59 -0500 (EST)
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gARHXFv10807;
	Wed, 27 Nov 2002 12:33:15 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gARHPLv10558
	for <manet@optimus.ietf.org>; Wed, 27 Nov 2002 12:25:21 -0500
Received: from ddsmttayz003.sam.pentagon.mil (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA20285
	for <manet@ietf.org>; Wed, 27 Nov 2002 12:22:31 -0500 (EST)
Received: by ddsmttayz003.osd.mil with Internet Mail Service (5.5.2653.19)
	id <XVYVH7P7>; Wed, 27 Nov 2002 12:25:12 -0500
Message-ID: <E6C9FD1649B9D54BB280C4787AF20E376F49CA@osdn5.osd.mil>
From: "Norton, Mark, , OSD-C3I" <Mark.Norton@osd.mil>
To: "'manet@ietf.org'" <manet@ietf.org>
Date: Wed, 27 Nov 2002 12:27:13 -0500
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2653.19)
Content-Type: text/plain;
	charset="iso-8859-1"
Subject: [manet] RE: manet digest, Vol 1 #268 - 6 msgs
Sender: manet-admin@ietf.org
Errors-To: manet-admin@ietf.org
X-BeenThere: manet@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/manet>,
	<mailto:manet-request@ietf.org?subject=unsubscribe>
List-Id: Mobile Ad-hoc Networks  <manet.ietf.org>
List-Post: <mailto:manet@ietf.org>
List-Help: <mailto:manet-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/manet>,
	<mailto:manet-request@ietf.org?subject=subscribe>



-----Original Message-----
From: manet-request@ietf.org [mailto:manet-request@ietf.org]
Sent: Wednesday, November 27, 2002 12:00 PM
To: manet@ietf.org
Subject: manet digest, Vol 1 #268 - 6 msgs


Send manet mailing list submissions to
	manet@ietf.org

To subscribe or unsubscribe via the World Wide Web, visit
	https://www1.ietf.org/mailman/listinfo/manet
or, via email, send a message with subject or body 'help' to
	manet-request@ietf.org

You can reach the person managing the list at
	manet-admin@ietf.org

When replying, please edit your Subject line so it is more specific
than "Re: Contents of manet digest..."


Today's Topics:

   1. Research news (=?iso-8859-1?Q?F=E1bio_Buiati?=)
   2. MAC & PHY interaction question (Yougu Yuan)
   3. Re: MAC & PHY interaction question (Don Montgomery)
   4. Re: Open this befo=?ISO-8859-1?B?cmUg0+/J+be9sc/Fvg==?=
(jomullen@nmsu.edu)
   5. FW: [mobile-ip] Dynamic Interfaces (was: 50 ms RA timer?) (Scott
Corson)
   6. MANET minutes (Joe Macker)

--__--__--

Message: 1
From: =?iso-8859-1?Q?F=E1bio_Buiati?= <fabio@redes.unb.br>
To: <manet@ietf.org>
Date: Tue, 26 Nov 2002 16:35:26 -0200
Subject: [manet] Research news

This is a multi-part message in MIME format.

------=_NextPart_000_007B_01C29569.D2F03EE0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

Hi all.
I would like which are new research areas? IDS for Manets, Personal =
Firewall, ...

Thanks a lot.
---------------------------------------------------
F=E1bio Mesquita Buiati
email - fabio@redes.unb.br
Bras=EDlia - Brazil
---------------------------------------------------

------=_NextPart_000_007B_01C29569.D2F03EE0
Content-Type: text/html;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META http-equiv=3DContent-Type content=3D"text/html; =
charset=3Diso-8859-1">
<META content=3D"MSHTML 6.00.2722.900" name=3DGENERATOR>
<STYLE></STYLE>
</HEAD>
<BODY bgColor=3D#ffffff>
<DIV><FONT face=3DArial size=3D2>Hi all.</FONT></DIV>
<DIV><FONT face=3DArial size=3D2>I would like which are new research =
areas? IDS for=20
Manets, Personal Firewall, ...</FONT></DIV>
<DIV><FONT face=3DArial size=3D2></FONT>&nbsp;</DIV>
<DIV><FONT face=3DArial size=3D2>Thanks a lot.</FONT></DIV>
<DIV><FONT face=3DArial=20
size=3D2>---------------------------------------------------<BR>F=E1bio =
Mesquita=20
Buiati<BR>email - <A=20
href=3D"mailto:fabio@redes.unb.br">fabio@redes.unb.br</A><BR>Bras=EDlia =
-=20
Brazil</FONT></DIV>
<DIV><FONT face=3DArial=20
size=3D2>---------------------------------------------------</FONT></DIV>=
</BODY></HTML>

------=_NextPart_000_007B_01C29569.D2F03EE0--


--__--__--

Message: 2
From: Yougu Yuan <yuanyg@cs.dartmouth.edu>
Reply-To: yuanyg@cs.dartmouth.edu
Organization: Dept. of Computer Science, Dartmouth College
To: manet@ietf.org
Date: Tue, 26 Nov 2002 14:13:23 -0500
Subject: [manet] MAC & PHY interaction question

Hi, all,

Here is a question about the interaction between the wireless MAC layer and 
the physical layer, but I think a "hardware" person is more likely to answer

it without a pause.

If the phy is receiving a packet, during which a "new" stronger ( >old
signal 
strength + capture threshold)  signal shows up, is the physical layer able
to 
tell that this is a "new signal", and start to notify the MAC layer to 
receive this new packet? Or will it go on blindly, only find out that there 
is a collision after receiving the old packet by checking the CRC, and
unable 
to recieve either packet in a whole piece?

Thank you.
-- 
Yougu Yuan

----------------------------------------------------
Office Phone 603-646-0679    yuanyg@cs.dartmouth.edu
Dept. of Computer Science, Dartmouth College


--__--__--

Message: 3
Date: Tue, 26 Nov 2002 13:24:03 -0600 (CST)
From: Don Montgomery <montgo@utdallas.edu>
To: Yougu Yuan <yuanyg@cs.dartmouth.edu>
Cc: manet@ietf.org
Subject: Re: [manet] MAC & PHY interaction question


Hi Yougu,

In the case you pose, I believe there will be a collision
no matter what the rxg node does.  The PHY/MAC models I
have seen studied here assume a single channel.

Don

On Tue, 26 Nov 2002, Yougu Yuan wrote:

Hi, all,

Here is a question about the interaction between the wireless MAC layer and 
the physical layer, but I think a "hardware" person is more likely to answer

it without a pause.

If the phy is receiving a packet, during which a "new" stronger ( >old
signal 
strength + capture threshold)  signal shows up, is the physical layer able
to 
tell that this is a "new signal", and start to notify the MAC layer to 
receive this new packet? Or will it go on blindly, only find out that there 
is a collision after receiving the old packet by checking the CRC, and
unable 
to recieve either packet in a whole piece?

Thank you.
-- 
Yougu Yuan

----------------------------------------------------
Office Phone 603-646-0679    yuanyg@cs.dartmouth.edu
Dept. of Computer Science, Dartmouth College

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


--__--__--

Message: 4
From: jomullen@nmsu.edu
Date: Tue, 26 Nov 2002 13:16:00 -0700
To: manet@ietf.org
Subject: Re: [manet] Open this befo=?ISO-8859-1?B?cmUg0+/J+be9sc/Fvg==?=

The referenced email appears to be a virus.

John Mullen

> ------------------  Virus Warning Message (on ietf-mx)
> 
> 024.bat is of type executable and is removed.
> 
> Please contact your network administrator for further information.
> 
> ---------------------------------------------------------
> 



--__--__--

Message: 5
From: Scott Corson <Corson@flarion.com>
To: "'Manet (manet@ietf.org)'" <manet@ietf.org>
Date: Tue, 26 Nov 2002 15:58:54 -0500
Subject: [manet] FW: [mobile-ip] Dynamic Interfaces (was: 50 ms RA timer?)

Oops...  meant to send this here.

-Scott

-----Original Message-----
From: Scott Corson [mailto:Corson@flarion.com] 
Sent: Tuesday, November 26, 2002 3:53 PM
To: 'Charles E. Perkins'; 'James Kempf'
Cc: 'mobile-ip@sunroof.eng.sun.com'; 'Manet (manet@itd.nrl.navy.mil)'
Subject: [mobile-ip] Dynamic Interfaces (was: 50 ms RA timer?)


> for Internet connectivity.  Mobile IP seemed to be quite well-regarded
> as a beneficial technology there.  I mentioned a couple of my
> pet peeves about current 802.11 device drivers and delays, and
> I got the impression that many (not all!) IEEE engineers in the
> meeting wanted to ensure that future products would work well
> with Mobile IP.

Increasingly, as the understanding permeates the industry that link layers
come and go, yet IP remains, link layer folks will begin to explicitly
design (or minimally to optimize) their technologies to plug into the
underbelly of an IP network.

The best thing the IETF could do IMHO would be to begin to *help* these
folks out.  

There is an increasingly broad class of link layer technologies under
development that, collectively, exhibit very 'dynamic' behavior.
Intermittent and varying connectivity is the norm, not the exception, for
this class of technologies.  And they need not be mobile technologies,
although this is the common case.

I think the IETF should define (or put into common practice) what is
essentially a new interface type--a "dynamic" interface--to be chosen for
use by these technologies if desired.  It should likely retain the
addressing semantics of a 'broadcast' interface--link layer unicast,
broadcast and multicast--yet ensure that the efficient, dynamic discovery of
'point-to-point' relationships between neighboring interfaces (generally
thru link layer mechanisms) can be communicated to the IP stack in a
standard way.  This mechanism would enable an IP stack to interact with this
new interface type in new ways.  This essentially requires standardizing
IP's "underbelly"--a term that Phil N. recently introduced on the PILC
list--to understand and work with dynamic interfaces.  

A 50ms RA timer is a pretty blunt instrument for assessing next-hop
reachability, and is inapplicable in many deployment scenarios.  If that is
the best you can do, then perhaps that is an answer, but it's certainly not
THE answer.  

A dynamic interface construct would be extremely general, and would likely
solve the problems that the recent interest in work on L2 triggers has hoped
to address.  It would apply to many technologies, and be useful in many
contexts where Mobile IP, MANET, Nemo and other such network layer protocols
must deal with link layer dynamics in a timely fashion.  It should also be
understood that the prerogative to act, to delay or to suppress these events
is still under the control of the IP layer.

-Scott

--__--__--

Message: 6
Date: Tue, 26 Nov 2002 17:48:31 -0500
To: minutes@ietf.org
From: Joe Macker <macker@itd.nrl.navy.mil>
Cc: manet@ietf.org
Subject: [manet] MANET minutes

Minutes of the Mobile Ad-hoc Networks WG (manet)
55th IETF Proceedings
Thursday, Nov 21 at 1300-1500

Minutes taken by Justin Dean
==============================

CHAIRS: M. Scott Corson <corson@Glue.umd.edu> 
              Joseph Macker <macker@itd.nrl.navy.mil> 

AGENDA:

(10 min) Agenda Bashing and Announcements
(20 min) Proposed Manet Way Forward
(10 min) Strawman Proposal for Charter and Milestone Update
(10 min) Related IRTF Activity Announcement
(10 min) Open Discussion of Proposal and Issues
(15 min) TBRPF Update
(15 min) DSR Update
(15 min) OLSR Update
(15 min) AODV Update
Closing

Joe Macker presented the agenda and opened it up for bashing.
The agenda was accepted as is with no bashing.

Joe Macker had some issues regarding the manet mailing list that he wished
to remind members about.

- There are 1969 members currently on the manet mailing list.
- Only members are allowed to post to the mailing list. Somewhat standard
practice, but not a perfect way to reduce spam, etc.
- Manet members should be aware when switching account names so that they
may still post effectively without moderator intervention.
- The newer ietf.org mailing list is reasonably automated; please use the
automated features to manage your own accounts whenever possible.
- NS2, GLOMOSIM, QUALNET, OPNET simulation software questions have recently
increased in volume.  Often simulation environment specific questions are
not appropriate for the mass manet mailing list, members are urged to
contact the authors of the code or appropriate simulation mailing list for
instruction questions, FAQs, etc.
 
MANET Way Forward (for details see presentation in proceedings)

Joe Macker presented an overview of a proposed way forward for the manet WG
that was being worked on in conjunction with the ADs. Recent perceived WG
status is that manet prototype implementation, designs, and experimentation
are very active. However, the WG has experienced significant "research
creep" into the ongoing work by continuing to consider broad work issues in
the manet problem space.  It is the intention of the chairs and the ADs to
update the charter of the WG to scope down to a focused engineering mode of
work.  The core approach is:

·       reduce the near term scope of the present WG
·       formulate an IRTF venue for manet research items, split off related
longer term research work from IETF
·       complete several mature unicast protocol ID work as EXPERIMENTAL
RFCs
·       formulate a focused problem statement(s)
·       convert core work items to an engineering mode and target common
Proposed Standard effort(s)

Alex Zinin: Routing co-AD (for details see presentation in proceedings)

Alex Zinin next discussed the proposed rechartering effort.  Alex mentioned
that he had posted a note to the list summarizing some of the issues as they
have emerged a few weeks back.  The summary is that very useful work is
being done in manet, but the WG is operating under a wide problem statement.
The perception is there are many competing protocols, a lack of WG-wide
consensus, and no signs of convergence. All of the above == research mode.

The goals of the proposed charter update would be to convert the WG to the
IETF mode:
                Clear and focused problem statement
                Focused WG charter, clear milestones
                WG members working closely towards consensus
                Design IETF MANET protocol STD

Work that needs more research (yes, it is somewhat subjective) will move to
the IRTF.

Proposed Steps:
        First, we create an IRTF sub-group for MANET and move LANMAR, FSR,
ZRP, TORA and similar work into this forum.  We would scope the charter to
push DSR, AODV, OLSR, and TBRPF to EXP and when done the WG will better
define the engineering problems statement. IF rough agreement is reached on
the problem statement we will update the charter with the development of
IETF protocol(s) that will go STD tracks.

Plan of actions 

We will discuss this more here and on the mailing list (nothing so far). We
will announce the decision within a month after this meeting.

Questions:
Q:      Will the rechartering approach cause delay in pushing forward EXP
RFCs for certain protocols already under consideration?
A:      No, that is not intended.

Q:      Will multicast work in manets be carried out in ietf or irtf?
A:      Lots of papers on this subject already, yet it remains to be decided
what is appropriate for engineering. Stay Tuned.
-------------------------------------------------------------

At this point, the Joe Macker polled the room for consensus on re-chartering
direction. Room consensus was attained to re-charter based upon the approach
presented..  Further mailing list input will be taken before reaching any
decisions.

Strawman Recharter Presentation - Joe Macker (for details see presentation
in proceedings)

Joe Macker presented some text and line items for consideration in an
updated charter/milestone effort. More discussion of this will take place on
the mailing list.

Strawman Near Term Milestones

Present: Restructure WG to be more narrowly focused, split off important
related IRTF work
Jan 2003 SUBMIT core reactive protocols for EXPERIMENTAL RFC (if not already
done)
Jan 2003 Revisit WG goals and problem statements
Mar 2003 SUBMIT core proactive protocols for EXPERIMENTAL RFC
Jun 2003 Develop and approve focused MANET WG problem statements and scoped
engineering goals.

Scott Corson: IRTF MANET research subgroup

Scott presented an overview of the manet-related IRTF plan.  Scalability is
the main research theme and some of the goals will be to foster discussion
and better understand the limitations of existing approaches (e.g., simple
flat reactive and proactive).  The group will look at proposing/developing
approaches that demonstrate superior performance (e.g., Hybrid/hierarchical
forms and radically new concepts).  More details will be formulated.  It has
been a concern that meetings may not be long enough and it is likely that
meetings may take place in concert with ongoing events to ease travel as
much as possible.

A new mailing list will be set up and announced on mailing list

Q:      Will multicast be in IRTF or IETF?
A:      Depends on the problem statement that the IETF works out and it may
be a mixed case given appropriate rationale of problems statements.

Q:      What is small/medium networks? Maybe 10-100 nodes but what about
movement models?  What type of movement scale are we using?
A:      We are aware that dynamic link/motion models, traffic flow models,
network surge conditions, and other factors affect any scalability
assessment besides number of router nodes.  We need some discussion of this
in problem and applicability statements.

Q: Other IETF groups have scalability in the charters so why are we getting
rid of it in this charter?
A:      It is not the intention to artificially limit the potential for
large area scalability, however we are not making it a requirement for
engineering maturity and applicability reasons.

Comment:        IRTF should be looking at the limits of current protocols
work as well.  This may be fed back to justify changing things in IETF.

Q: Would like to see IRTF and IETF groups work together closely; meetings at
same conference? 
A: Yes but the IRTF participants need freedom to do their research as well.

Q:  Need to keep problem statement simple.  Where does security belong?
What about IETF issuing standard without security in it?
A:  Need to discuss closer with the routing security working group.

Comment:  I see a need for simplicity of the protocol.  
Comment:  I think it would be extremely useful to get RFCs out that can be
used for 50-100 node scenarios.
Comment: HIP ipsec can help to bring improved security to manet.
Other comment: Systems are being develop that should work with wireless
networks.

Chair: Great comments, but we need to move one please bring further
discussions to the list.

TBRPF Update: Richard Ogier *see online presentation

TBRPF is now at Draft revision 6.  It has been rewritten to improve
readability. Hello message has been modified to include relay priority
similar to OLSR MPR preference.  It was clarified that tbrpf computes the
equivalent of MPRs.  There is now a relay priority in each hello.. OLSR MPR
willingness is same type of thing and this presents the possibility of
merging with OSLR. Other details (see presentation).  There is a new SRI IPR
statement registered at ietf.org.

DSR Update: Dave Johnson

(see on-line for details).  The final DSR ID for EXPERIMENTAL consideration
is not finished yet.  We are trying to add a few things to back into draft.
Stuff that was in version 3 of the ID.

OLSR Update: Thomas Clausen

(see on-line for details).  A new version of OLSR was update (now version
8).  Posting to ID editor was munged and the draft was posted to the list in
the interim.     There are no major changes.  The feedback was that most
people intending to use OLSR didn't want all the features.  They wanted
something like version 3 or 4.

AODV Update: Elizabeth Belding-Royer

AODV is now at ID version 12.  There we no major changes in this revision.
There was some clarification of local proactive repair.
        
http://sourceforge.net/projects/aodvimpl/ for aodv questions.
http://moment.cs.ucsb.edu/AODV/aodv.html





--__--__--

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


End of manet Digest
_______________________________________________
manet mailing list
manet@ietf.org
https://www1.ietf.org/mailman/listinfo/manet



From manet-admin@ietf.org  Wed Nov 27 13:10:22 2002
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA22388
	for <manet-archive@lists.ietf.org>; Wed, 27 Nov 2002 13:10:22 -0500 (EST)
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gARHXFv10807;
	Wed, 27 Nov 2002 12:33:15 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gARHPLv10558
	for <manet@optimus.ietf.org>; Wed, 27 Nov 2002 12:25:21 -0500
Received: from ddsmttayz003.sam.pentagon.mil (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA20285
	for <manet@ietf.org>; Wed, 27 Nov 2002 12:22:31 -0500 (EST)
Received: by ddsmttayz003.osd.mil with Internet Mail Service (5.5.2653.19)
	id <XVYVH7P7>; Wed, 27 Nov 2002 12:25:12 -0500
Message-ID: <E6C9FD1649B9D54BB280C4787AF20E376F49CA@osdn5.osd.mil>
From: "Norton, Mark, , OSD-C3I" <Mark.Norton@osd.mil>
To: "'manet@ietf.org'" <manet@ietf.org>
Date: Wed, 27 Nov 2002 12:27:13 -0500
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2653.19)
Content-Type: text/plain;
	charset="iso-8859-1"
Subject: [manet] RE: manet digest, Vol 1 #268 - 6 msgs
Sender: manet-admin@ietf.org
Errors-To: manet-admin@ietf.org
X-BeenThere: manet@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/manet>,
	<mailto:manet-request@ietf.org?subject=unsubscribe>
List-Id: Mobile Ad-hoc Networks  <manet.ietf.org>
List-Post: <mailto:manet@ietf.org>
List-Help: <mailto:manet-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/manet>,
	<mailto:manet-request@ietf.org?subject=subscribe>



-----Original Message-----
From: manet-request@ietf.org [mailto:manet-request@ietf.org]
Sent: Wednesday, November 27, 2002 12:00 PM
To: manet@ietf.org
Subject: manet digest, Vol 1 #268 - 6 msgs


Send manet mailing list submissions to
	manet@ietf.org

To subscribe or unsubscribe via the World Wide Web, visit
	https://www1.ietf.org/mailman/listinfo/manet
or, via email, send a message with subject or body 'help' to
	manet-request@ietf.org

You can reach the person managing the list at
	manet-admin@ietf.org

When replying, please edit your Subject line so it is more specific
than "Re: Contents of manet digest..."


Today's Topics:

   1. Research news (=?iso-8859-1?Q?F=E1bio_Buiati?=)
   2. MAC & PHY interaction question (Yougu Yuan)
   3. Re: MAC & PHY interaction question (Don Montgomery)
   4. Re: Open this befo=?ISO-8859-1?B?cmUg0+/J+be9sc/Fvg==?=
(jomullen@nmsu.edu)
   5. FW: [mobile-ip] Dynamic Interfaces (was: 50 ms RA timer?) (Scott
Corson)
   6. MANET minutes (Joe Macker)

--__--__--

Message: 1
From: =?iso-8859-1?Q?F=E1bio_Buiati?= <fabio@redes.unb.br>
To: <manet@ietf.org>
Date: Tue, 26 Nov 2002 16:35:26 -0200
Subject: [manet] Research news

This is a multi-part message in MIME format.

------=_NextPart_000_007B_01C29569.D2F03EE0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

Hi all.
I would like which are new research areas? IDS for Manets, Personal =
Firewall, ...

Thanks a lot.
---------------------------------------------------
F=E1bio Mesquita Buiati
email - fabio@redes.unb.br
Bras=EDlia - Brazil
---------------------------------------------------

------=_NextPart_000_007B_01C29569.D2F03EE0
Content-Type: text/html;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META http-equiv=3DContent-Type content=3D"text/html; =
charset=3Diso-8859-1">
<META content=3D"MSHTML 6.00.2722.900" name=3DGENERATOR>
<STYLE></STYLE>
</HEAD>
<BODY bgColor=3D#ffffff>
<DIV><FONT face=3DArial size=3D2>Hi all.</FONT></DIV>
<DIV><FONT face=3DArial size=3D2>I would like which are new research =
areas? IDS for=20
Manets, Personal Firewall, ...</FONT></DIV>
<DIV><FONT face=3DArial size=3D2></FONT>&nbsp;</DIV>
<DIV><FONT face=3DArial size=3D2>Thanks a lot.</FONT></DIV>
<DIV><FONT face=3DArial=20
size=3D2>---------------------------------------------------<BR>F=E1bio =
Mesquita=20
Buiati<BR>email - <A=20
href=3D"mailto:fabio@redes.unb.br">fabio@redes.unb.br</A><BR>Bras=EDlia =
-=20
Brazil</FONT></DIV>
<DIV><FONT face=3DArial=20
size=3D2>---------------------------------------------------</FONT></DIV>=
</BODY></HTML>

------=_NextPart_000_007B_01C29569.D2F03EE0--


--__--__--

Message: 2
From: Yougu Yuan <yuanyg@cs.dartmouth.edu>
Reply-To: yuanyg@cs.dartmouth.edu
Organization: Dept. of Computer Science, Dartmouth College
To: manet@ietf.org
Date: Tue, 26 Nov 2002 14:13:23 -0500
Subject: [manet] MAC & PHY interaction question

Hi, all,

Here is a question about the interaction between the wireless MAC layer and 
the physical layer, but I think a "hardware" person is more likely to answer

it without a pause.

If the phy is receiving a packet, during which a "new" stronger ( >old
signal 
strength + capture threshold)  signal shows up, is the physical layer able
to 
tell that this is a "new signal", and start to notify the MAC layer to 
receive this new packet? Or will it go on blindly, only find out that there 
is a collision after receiving the old packet by checking the CRC, and
unable 
to recieve either packet in a whole piece?

Thank you.
-- 
Yougu Yuan

----------------------------------------------------
Office Phone 603-646-0679    yuanyg@cs.dartmouth.edu
Dept. of Computer Science, Dartmouth College


--__--__--

Message: 3
Date: Tue, 26 Nov 2002 13:24:03 -0600 (CST)
From: Don Montgomery <montgo@utdallas.edu>
To: Yougu Yuan <yuanyg@cs.dartmouth.edu>
Cc: manet@ietf.org
Subject: Re: [manet] MAC & PHY interaction question


Hi Yougu,

In the case you pose, I believe there will be a collision
no matter what the rxg node does.  The PHY/MAC models I
have seen studied here assume a single channel.

Don

On Tue, 26 Nov 2002, Yougu Yuan wrote:

Hi, all,

Here is a question about the interaction between the wireless MAC layer and 
the physical layer, but I think a "hardware" person is more likely to answer

it without a pause.

If the phy is receiving a packet, during which a "new" stronger ( >old
signal 
strength + capture threshold)  signal shows up, is the physical layer able
to 
tell that this is a "new signal", and start to notify the MAC layer to 
receive this new packet? Or will it go on blindly, only find out that there 
is a collision after receiving the old packet by checking the CRC, and
unable 
to recieve either packet in a whole piece?

Thank you.
-- 
Yougu Yuan

----------------------------------------------------
Office Phone 603-646-0679    yuanyg@cs.dartmouth.edu
Dept. of Computer Science, Dartmouth College

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


--__--__--

Message: 4
From: jomullen@nmsu.edu
Date: Tue, 26 Nov 2002 13:16:00 -0700
To: manet@ietf.org
Subject: Re: [manet] Open this befo=?ISO-8859-1?B?cmUg0+/J+be9sc/Fvg==?=

The referenced email appears to be a virus.

John Mullen

> ------------------  Virus Warning Message (on ietf-mx)
> 
> 024.bat is of type executable and is removed.
> 
> Please contact your network administrator for further information.
> 
> ---------------------------------------------------------
> 



--__--__--

Message: 5
From: Scott Corson <Corson@flarion.com>
To: "'Manet (manet@ietf.org)'" <manet@ietf.org>
Date: Tue, 26 Nov 2002 15:58:54 -0500
Subject: [manet] FW: [mobile-ip] Dynamic Interfaces (was: 50 ms RA timer?)

Oops...  meant to send this here.

-Scott

-----Original Message-----
From: Scott Corson [mailto:Corson@flarion.com] 
Sent: Tuesday, November 26, 2002 3:53 PM
To: 'Charles E. Perkins'; 'James Kempf'
Cc: 'mobile-ip@sunroof.eng.sun.com'; 'Manet (manet@itd.nrl.navy.mil)'
Subject: [mobile-ip] Dynamic Interfaces (was: 50 ms RA timer?)


> for Internet connectivity.  Mobile IP seemed to be quite well-regarded
> as a beneficial technology there.  I mentioned a couple of my
> pet peeves about current 802.11 device drivers and delays, and
> I got the impression that many (not all!) IEEE engineers in the
> meeting wanted to ensure that future products would work well
> with Mobile IP.

Increasingly, as the understanding permeates the industry that link layers
come and go, yet IP remains, link layer folks will begin to explicitly
design (or minimally to optimize) their technologies to plug into the
underbelly of an IP network.

The best thing the IETF could do IMHO would be to begin to *help* these
folks out.  

There is an increasingly broad class of link layer technologies under
development that, collectively, exhibit very 'dynamic' behavior.
Intermittent and varying connectivity is the norm, not the exception, for
this class of technologies.  And they need not be mobile technologies,
although this is the common case.

I think the IETF should define (or put into common practice) what is
essentially a new interface type--a "dynamic" interface--to be chosen for
use by these technologies if desired.  It should likely retain the
addressing semantics of a 'broadcast' interface--link layer unicast,
broadcast and multicast--yet ensure that the efficient, dynamic discovery of
'point-to-point' relationships between neighboring interfaces (generally
thru link layer mechanisms) can be communicated to the IP stack in a
standard way.  This mechanism would enable an IP stack to interact with this
new interface type in new ways.  This essentially requires standardizing
IP's "underbelly"--a term that Phil N. recently introduced on the PILC
list--to understand and work with dynamic interfaces.  

A 50ms RA timer is a pretty blunt instrument for assessing next-hop
reachability, and is inapplicable in many deployment scenarios.  If that is
the best you can do, then perhaps that is an answer, but it's certainly not
THE answer.  

A dynamic interface construct would be extremely general, and would likely
solve the problems that the recent interest in work on L2 triggers has hoped
to address.  It would apply to many technologies, and be useful in many
contexts where Mobile IP, MANET, Nemo and other such network layer protocols
must deal with link layer dynamics in a timely fashion.  It should also be
understood that the prerogative to act, to delay or to suppress these events
is still under the control of the IP layer.

-Scott

--__--__--

Message: 6
Date: Tue, 26 Nov 2002 17:48:31 -0500
To: minutes@ietf.org
From: Joe Macker <macker@itd.nrl.navy.mil>
Cc: manet@ietf.org
Subject: [manet] MANET minutes

Minutes of the Mobile Ad-hoc Networks WG (manet)
55th IETF Proceedings
Thursday, Nov 21 at 1300-1500

Minutes taken by Justin Dean
==============================

CHAIRS: M. Scott Corson <corson@Glue.umd.edu> 
              Joseph Macker <macker@itd.nrl.navy.mil> 

AGENDA:

(10 min) Agenda Bashing and Announcements
(20 min) Proposed Manet Way Forward
(10 min) Strawman Proposal for Charter and Milestone Update
(10 min) Related IRTF Activity Announcement
(10 min) Open Discussion of Proposal and Issues
(15 min) TBRPF Update
(15 min) DSR Update
(15 min) OLSR Update
(15 min) AODV Update
Closing

Joe Macker presented the agenda and opened it up for bashing.
The agenda was accepted as is with no bashing.

Joe Macker had some issues regarding the manet mailing list that he wished
to remind members about.

- There are 1969 members currently on the manet mailing list.
- Only members are allowed to post to the mailing list. Somewhat standard
practice, but not a perfect way to reduce spam, etc.
- Manet members should be aware when switching account names so that they
may still post effectively without moderator intervention.
- The newer ietf.org mailing list is reasonably automated; please use the
automated features to manage your own accounts whenever possible.
- NS2, GLOMOSIM, QUALNET, OPNET simulation software questions have recently
increased in volume.  Often simulation environment specific questions are
not appropriate for the mass manet mailing list, members are urged to
contact the authors of the code or appropriate simulation mailing list for
instruction questions, FAQs, etc.
 
MANET Way Forward (for details see presentation in proceedings)

Joe Macker presented an overview of a proposed way forward for the manet WG
that was being worked on in conjunction with the ADs. Recent perceived WG
status is that manet prototype implementation, designs, and experimentation
are very active. However, the WG has experienced significant "research
creep" into the ongoing work by continuing to consider broad work issues in
the manet problem space.  It is the intention of the chairs and the ADs to
update the charter of the WG to scope down to a focused engineering mode of
work.  The core approach is:

·       reduce the near term scope of the present WG
·       formulate an IRTF venue for manet research items, split off related
longer term research work from IETF
·       complete several mature unicast protocol ID work as EXPERIMENTAL
RFCs
·       formulate a focused problem statement(s)
·       convert core work items to an engineering mode and target common
Proposed Standard effort(s)

Alex Zinin: Routing co-AD (for details see presentation in proceedings)

Alex Zinin next discussed the proposed rechartering effort.  Alex mentioned
that he had posted a note to the list summarizing some of the issues as they
have emerged a few weeks back.  The summary is that very useful work is
being done in manet, but the WG is operating under a wide problem statement.
The perception is there are many competing protocols, a lack of WG-wide
consensus, and no signs of convergence. All of the above == research mode.

The goals of the proposed charter update would be to convert the WG to the
IETF mode:
                Clear and focused problem statement
                Focused WG charter, clear milestones
                WG members working closely towards consensus
                Design IETF MANET protocol STD

Work that needs more research (yes, it is somewhat subjective) will move to
the IRTF.

Proposed Steps:
        First, we create an IRTF sub-group for MANET and move LANMAR, FSR,
ZRP, TORA and similar work into this forum.  We would scope the charter to
push DSR, AODV, OLSR, and TBRPF to EXP and when done the WG will better
define the engineering problems statement. IF rough agreement is reached on
the problem statement we will update the charter with the development of
IETF protocol(s) that will go STD tracks.

Plan of actions 

We will discuss this more here and on the mailing list (nothing so far). We
will announce the decision within a month after this meeting.

Questions:
Q:      Will the rechartering approach cause delay in pushing forward EXP
RFCs for certain protocols already under consideration?
A:      No, that is not intended.

Q:      Will multicast work in manets be carried out in ietf or irtf?
A:      Lots of papers on this subject already, yet it remains to be decided
what is appropriate for engineering. Stay Tuned.
-------------------------------------------------------------

At this point, the Joe Macker polled the room for consensus on re-chartering
direction. Room consensus was attained to re-charter based upon the approach
presented..  Further mailing list input will be taken before reaching any
decisions.

Strawman Recharter Presentation - Joe Macker (for details see presentation
in proceedings)

Joe Macker presented some text and line items for consideration in an
updated charter/milestone effort. More discussion of this will take place on
the mailing list.

Strawman Near Term Milestones

Present: Restructure WG to be more narrowly focused, split off important
related IRTF work
Jan 2003 SUBMIT core reactive protocols for EXPERIMENTAL RFC (if not already
done)
Jan 2003 Revisit WG goals and problem statements
Mar 2003 SUBMIT core proactive protocols for EXPERIMENTAL RFC
Jun 2003 Develop and approve focused MANET WG problem statements and scoped
engineering goals.

Scott Corson: IRTF MANET research subgroup

Scott presented an overview of the manet-related IRTF plan.  Scalability is
the main research theme and some of the goals will be to foster discussion
and better understand the limitations of existing approaches (e.g., simple
flat reactive and proactive).  The group will look at proposing/developing
approaches that demonstrate superior performance (e.g., Hybrid/hierarchical
forms and radically new concepts).  More details will be formulated.  It has
been a concern that meetings may not be long enough and it is likely that
meetings may take place in concert with ongoing events to ease travel as
much as possible.

A new mailing list will be set up and announced on mailing list

Q:      Will multicast be in IRTF or IETF?
A:      Depends on the problem statement that the IETF works out and it may
be a mixed case given appropriate rationale of problems statements.

Q:      What is small/medium networks? Maybe 10-100 nodes but what about
movement models?  What type of movement scale are we using?
A:      We are aware that dynamic link/motion models, traffic flow models,
network surge conditions, and other factors affect any scalability
assessment besides number of router nodes.  We need some discussion of this
in problem and applicability statements.

Q: Other IETF groups have scalability in the charters so why are we getting
rid of it in this charter?
A:      It is not the intention to artificially limit the potential for
large area scalability, however we are not making it a requirement for
engineering maturity and applicability reasons.

Comment:        IRTF should be looking at the limits of current protocols
work as well.  This may be fed back to justify changing things in IETF.

Q: Would like to see IRTF and IETF groups work together closely; meetings at
same conference? 
A: Yes but the IRTF participants need freedom to do their research as well.

Q:  Need to keep problem statement simple.  Where does security belong?
What about IETF issuing standard without security in it?
A:  Need to discuss closer with the routing security working group.

Comment:  I see a need for simplicity of the protocol.  
Comment:  I think it would be extremely useful to get RFCs out that can be
used for 50-100 node scenarios.
Comment: HIP ipsec can help to bring improved security to manet.
Other comment: Systems are being develop that should work with wireless
networks.

Chair: Great comments, but we need to move one please bring further
discussions to the list.

TBRPF Update: Richard Ogier *see online presentation

TBRPF is now at Draft revision 6.  It has been rewritten to improve
readability. Hello message has been modified to include relay priority
similar to OLSR MPR preference.  It was clarified that tbrpf computes the
equivalent of MPRs.  There is now a relay priority in each hello.. OLSR MPR
willingness is same type of thing and this presents the possibility of
merging with OSLR. Other details (see presentation).  There is a new SRI IPR
statement registered at ietf.org.

DSR Update: Dave Johnson

(see on-line for details).  The final DSR ID for EXPERIMENTAL consideration
is not finished yet.  We are trying to add a few things to back into draft.
Stuff that was in version 3 of the ID.

OLSR Update: Thomas Clausen

(see on-line for details).  A new version of OLSR was update (now version
8).  Posting to ID editor was munged and the draft was posted to the list in
the interim.     There are no major changes.  The feedback was that most
people intending to use OLSR didn't want all the features.  They wanted
something like version 3 or 4.

AODV Update: Elizabeth Belding-Royer

AODV is now at ID version 12.  There we no major changes in this revision.
There was some clarification of local proactive repair.
        
http://sourceforge.net/projects/aodvimpl/ for aodv questions.
http://moment.cs.ucsb.edu/AODV/aodv.html





--__--__--

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


End of manet Digest
_______________________________________________
manet mailing list
manet@ietf.org
https://www1.ietf.org/mailman/listinfo/manet


From mailnull@www1.ietf.org  Wed Nov 27 18:53:05 2002
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA03187
	for <manet-archive@odin.ietf.org>; Wed, 27 Nov 2002 18:53:05 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id gARNtQP02703
	for manet-archive@odin.ietf.org; Wed, 27 Nov 2002 18:55:26 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gARNtQv02700
	for <manet-web-archive@optimus.ietf.org>; Wed, 27 Nov 2002 18:55:26 -0500
Received: from www1.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA03181
	for <manet-web-archive@ietf.org>; Wed, 27 Nov 2002 18:52:34 -0500 (EST)
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gARNkcv02362;
	Wed, 27 Nov 2002 18:46:38 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gARNf9v02212
	for <manet@optimus.ietf.org>; Wed, 27 Nov 2002 18:41:09 -0500
Received: from strix.ciens.ucv.ve (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA02720
	for <manet@ietf.org>; Wed, 27 Nov 2002 18:38:16 -0500 (EST)
Received: from dircompucv2.strix.ciens.ucv.ve (dircompucv.ciens.ucv.ve [150.185.75.85])
	by strix.ciens.ucv.ve (SGI-8.9.3/8.9.3) with ESMTP id TAA51018
	for <manet@ietf.org>; Wed, 27 Nov 2002 19:41:47 -0800 (PST)
Message-Id: <5.0.0.25.0.20021127193740.0269c8d0@strix.ciens.ucv.ve>
X-Sender: dcobos@strix.ciens.ucv.ve
X-Mailer: QUALCOMM Windows Eudora Version 5.0
Date: Wed, 27 Nov 2002 19:43:46 -0400
To: manet@ietf.org
From: Denis Cobos <dcobos@strix.ciens.ucv.ve>
Mime-Version: 1.0
Content-Type: text/plain; charset="iso-8859-1"; format=flowed
Content-Transfer-Encoding: 8bit
X-MIME-Autoconverted: from quoted-printable to 8bit by www1.ietf.org id gARNf9v02213
Subject: [manet] !!About test of routing protocol with emulation!!
Sender: manet-admin@ietf.org
Errors-To: manet-admin@ietf.org
X-BeenThere: manet@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/manet>,
	<mailto:manet-request@ietf.org?subject=unsubscribe>
List-Id: Mobile Ad-hoc Networks  <manet.ietf.org>
List-Post: <mailto:manet@ietf.org>
List-Help: <mailto:manet-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/manet>,
	<mailto:manet-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 8bit
Content-Transfer-Encoding: 8bit

Hi all
I would like to know if there exist the possibility to
implant a MANET routing protocols in a Linux systems within a
wired network and  to test this routing protocols with some emulator such as
"mobiemu", so that we could emulate the wireless interface but doing some tests
with the operation of the implated protocol within the real system.

I will thank and appreciate your help

Best Regards,

Denis Cobos
Universidad Central de Venezuela
Facultad de Ciencias
Escuela de Computación
Laboratorio de Redes Móviles Inalámbricas ICARO
e-mail:dcobos@strix.ciens.ucv.ve

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



From manet-admin@ietf.org  Wed Nov 27 18:53:57 2002
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA03212
	for <manet-archive@lists.ietf.org>; Wed, 27 Nov 2002 18:53:56 -0500 (EST)
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gARNkcv02362;
	Wed, 27 Nov 2002 18:46:38 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gARNf9v02212
	for <manet@optimus.ietf.org>; Wed, 27 Nov 2002 18:41:09 -0500
Received: from strix.ciens.ucv.ve (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA02720
	for <manet@ietf.org>; Wed, 27 Nov 2002 18:38:16 -0500 (EST)
Received: from dircompucv2.strix.ciens.ucv.ve (dircompucv.ciens.ucv.ve [150.185.75.85])
	by strix.ciens.ucv.ve (SGI-8.9.3/8.9.3) with ESMTP id TAA51018
	for <manet@ietf.org>; Wed, 27 Nov 2002 19:41:47 -0800 (PST)
Message-Id: <5.0.0.25.0.20021127193740.0269c8d0@strix.ciens.ucv.ve>
X-Sender: dcobos@strix.ciens.ucv.ve
X-Mailer: QUALCOMM Windows Eudora Version 5.0
Date: Wed, 27 Nov 2002 19:43:46 -0400
To: manet@ietf.org
From: Denis Cobos <dcobos@strix.ciens.ucv.ve>
Mime-Version: 1.0
Content-Type: text/plain; charset="iso-8859-1"; format=flowed
Content-Transfer-Encoding: 8bit
X-MIME-Autoconverted: from quoted-printable to 8bit by www1.ietf.org id gARNf9v02213
Subject: [manet] !!About test of routing protocol with emulation!!
Sender: manet-admin@ietf.org
Errors-To: manet-admin@ietf.org
X-BeenThere: manet@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/manet>,
	<mailto:manet-request@ietf.org?subject=unsubscribe>
List-Id: Mobile Ad-hoc Networks  <manet.ietf.org>
List-Post: <mailto:manet@ietf.org>
List-Help: <mailto:manet-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/manet>,
	<mailto:manet-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 8bit

Hi all
I would like to know if there exist the possibility to
implant a MANET routing protocols in a Linux systems within a
wired network and  to test this routing protocols with some emulator such as
"mobiemu", so that we could emulate the wireless interface but doing some tests
with the operation of the implated protocol within the real system.

I will thank and appreciate your help

Best Regards,

Denis Cobos
Universidad Central de Venezuela
Facultad de Ciencias
Escuela de Computación
Laboratorio de Redes Móviles Inalámbricas ICARO
e-mail:dcobos@strix.ciens.ucv.ve

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


From manet-admin@ietf.org  Thu Nov 28 04:46:17 2002
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id EAA24030
	for <manet-archive@lists.ietf.org>; Thu, 28 Nov 2002 04:46:17 -0500 (EST)
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gAS9WLv07910;
	Thu, 28 Nov 2002 04:32:21 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gAS9Msv07647
	for <manet@optimus.ietf.org>; Thu, 28 Nov 2002 04:22:54 -0500
Received: from london.unik.no (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id EAA23673
	for <manet@ietf.org>; Thu, 28 Nov 2002 04:19:59 -0500 (EST)
content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
X-MimeOLE: Produced By Microsoft Exchange V6.0.6249.0
Date: Thu, 28 Nov 2002 10:22:43 +0100
Message-ID: <C0DFF6586F0B8345B30031F2DC2B9D2A94D8@london.unik.no>
Thread-Topic: Tactical mobile ad hoc networks - references ?
Thread-Index: AcKWv7RpapeE9OKOTWydwcsXwH2QiQ==
From: "Andreas Hafslund" <andreha@unik.no>
To: <manet@ietf.org>
Content-Transfer-Encoding: 8bit
X-MIME-Autoconverted: from quoted-printable to 8bit by www1.ietf.org id gAS9Msv07648
Subject: [manet] Tactical mobile ad hoc networks - references ?
Sender: manet-admin@ietf.org
Errors-To: manet-admin@ietf.org
X-BeenThere: manet@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/manet>,
	<mailto:manet-request@ietf.org?subject=unsubscribe>
List-Id: Mobile Ad-hoc Networks  <manet.ietf.org>
List-Post: <mailto:manet@ietf.org>
List-Help: <mailto:manet-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/manet>,
	<mailto:manet-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 8bit

I am doing a study of tactical mobile ad hoc networks. Are there any articles, studies or reports about this available?

I am interested in results from simulations, emulations or real experiments in a tactical setting. Typical with very low bandwidth, high mobility, mostly data traffic, (but real-time data is also of interest), max 100 - 150 nodes. 

A theoretical study of different ad hoc routing protocols in a tactical setting is also of interest. How little bandwidth can you have, and how high mobility can you have, for AODV, DSR, OLSR, ZRP etc, without the routing protocol breaks down (fails to find a route).

Does anyone have any references on the Internet? Any help is appriciated.

Regards,
Andreas Hafslund

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


From mailnull@www1.ietf.org  Thu Nov 28 05:03:09 2002
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id FAA24241
	for <manet-archive@odin.ietf.org>; Thu, 28 Nov 2002 05:03:09 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id gASA5Nt09703
	for manet-archive@odin.ietf.org; Thu, 28 Nov 2002 05:05:23 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gASA5Nv09700
	for <manet-web-archive@optimus.ietf.org>; Thu, 28 Nov 2002 05:05:23 -0500
Received: from www1.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id FAA24238
	for <manet-web-archive@ietf.org>; Thu, 28 Nov 2002 05:02:38 -0500 (EST)
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gAS9WLv07910;
	Thu, 28 Nov 2002 04:32:21 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gAS9Msv07647
	for <manet@optimus.ietf.org>; Thu, 28 Nov 2002 04:22:54 -0500
Received: from london.unik.no (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id EAA23673
	for <manet@ietf.org>; Thu, 28 Nov 2002 04:19:59 -0500 (EST)
content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
X-MimeOLE: Produced By Microsoft Exchange V6.0.6249.0
Date: Thu, 28 Nov 2002 10:22:43 +0100
Message-ID: <C0DFF6586F0B8345B30031F2DC2B9D2A94D8@london.unik.no>
Thread-Topic: Tactical mobile ad hoc networks - references ?
Thread-Index: AcKWv7RpapeE9OKOTWydwcsXwH2QiQ==
From: "Andreas Hafslund" <andreha@unik.no>
To: <manet@ietf.org>
Content-Transfer-Encoding: 8bit
X-MIME-Autoconverted: from quoted-printable to 8bit by www1.ietf.org id gAS9Msv07648
Subject: [manet] Tactical mobile ad hoc networks - references ?
Sender: manet-admin@ietf.org
Errors-To: manet-admin@ietf.org
X-BeenThere: manet@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/manet>,
	<mailto:manet-request@ietf.org?subject=unsubscribe>
List-Id: Mobile Ad-hoc Networks  <manet.ietf.org>
List-Post: <mailto:manet@ietf.org>
List-Help: <mailto:manet-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/manet>,
	<mailto:manet-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 8bit
Content-Transfer-Encoding: 8bit

I am doing a study of tactical mobile ad hoc networks. Are there any articles, studies or reports about this available?

I am interested in results from simulations, emulations or real experiments in a tactical setting. Typical with very low bandwidth, high mobility, mostly data traffic, (but real-time data is also of interest), max 100 - 150 nodes. 

A theoretical study of different ad hoc routing protocols in a tactical setting is also of interest. How little bandwidth can you have, and how high mobility can you have, for AODV, DSR, OLSR, ZRP etc, without the routing protocol breaks down (fails to find a route).

Does anyone have any references on the Internet? Any help is appriciated.

Regards,
Andreas Hafslund

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



From manet-admin@ietf.org  Fri Nov 29 12:08:31 2002
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA03394
	for <manet-archive@lists.ietf.org>; Fri, 29 Nov 2002 12:08:31 -0500 (EST)
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gATGsWv09325;
	Fri, 29 Nov 2002 11:54:32 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gATGirv09108
	for <manet@optimus.ietf.org>; Fri, 29 Nov 2002 11:44:53 -0500
Received: from smtp.web.de (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA02965
	for <manet@ietf.org>; Fri, 29 Nov 2002 11:42:03 -0500 (EST)
Received: from [134.102.101.207] (helo=MIPNET)
	by smtp.web.de with smtp (WEB.DE(Exim) 4.91 #2)
	id 18HoG0-0007cD-00
	for manet@ietf.org; Fri, 29 Nov 2002 17:44:48 +0100
Message-ID: <001001c297c7$26ef2c90$cf656686@MIPNET>
From: "Michael Sessinghaus" <sessinghaus@web.de>
To: <manet@ietf.org>
Date: Fri, 29 Nov 2002 17:48:32 +0100
MIME-Version: 1.0
Content-Type: multipart/alternative;
	boundary="----=_NextPart_000_000D_01C297CF.88503EE0"
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 6.00.2600.0000
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2600.0000
Subject: [manet] AODV draft major changes
Sender: manet-admin@ietf.org
Errors-To: manet-admin@ietf.org
X-BeenThere: manet@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/manet>,
	<mailto:manet-request@ietf.org?subject=unsubscribe>
List-Id: Mobile Ad-hoc Networks  <manet.ietf.org>
List-Post: <mailto:manet@ietf.org>
List-Help: <mailto:manet-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/manet>,
	<mailto:manet-request@ietf.org?subject=subscribe>

This is a multi-part message in MIME format.

------=_NextPart_000_000D_01C297CF.88503EE0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

Hi,
i want to know the major changes between

AODV draft version 6 vs. version 8

and

AODV draft version 11 vs. version 8


not included any information about draft text wording.
It is for a comparison between this distinct aodv versions for ns-2.1b9a =
implementations.=20

Thanks a lot for your help.
Greetings, Michael.

------=_NextPart_000_000D_01C297CF.88503EE0
Content-Type: text/html;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META http-equiv=3DContent-Type content=3D"text/html; =
charset=3Diso-8859-1">
<META content=3D"MSHTML 6.00.2600.0" name=3DGENERATOR>
<STYLE></STYLE>
</HEAD>
<BODY bgColor=3D#ffffff>
<DIV><FONT face=3DArial size=3D2>Hi,</FONT></DIV>
<DIV><FONT face=3DArial size=3D2>i want to know the major changes=20
between</FONT></DIV>
<DIV><FONT face=3DArial size=3D2></FONT>&nbsp;</DIV>
<DIV><FONT face=3DArial size=3D2>AODV draft version 6 vs. version =
8</FONT></DIV>
<DIV><FONT face=3DArial size=3D2></FONT>&nbsp;</DIV>
<DIV><FONT face=3DArial size=3D2>and</FONT></DIV>
<DIV><FONT face=3DArial size=3D2></FONT>&nbsp;</DIV>
<DIV><FONT face=3DArial size=3D2>AODV draft version 11 vs. version =
8</FONT></DIV>
<DIV><FONT face=3DArial size=3D2></FONT>&nbsp;</DIV>
<DIV><FONT face=3DArial size=3D2></FONT>&nbsp;</DIV>
<DIV><FONT face=3DArial size=3D2>not included any information about =
draft text=20
wording.</FONT></DIV>
<DIV><FONT face=3DArial size=3D2>It is for a comparison between this =
distinct aodv=20
versions for ns-2.1b9a implementations. </FONT></DIV>
<DIV><FONT face=3DArial size=3D2></FONT>&nbsp;</DIV>
<DIV><FONT face=3DArial size=3D2>Thanks a lot for your =
help.</FONT></DIV>
<DIV><FONT face=3DArial size=3D2>Greetings, =
Michael.</FONT></DIV></BODY></HTML>

------=_NextPart_000_000D_01C297CF.88503EE0--

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


From mailnull@www1.ietf.org  Fri Nov 29 12:22:56 2002
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA03686
	for <manet-archive@odin.ietf.org>; Fri, 29 Nov 2002 12:22:56 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id gATHPFR11181
	for manet-archive@odin.ietf.org; Fri, 29 Nov 2002 12:25:15 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gATHPFv11178
	for <manet-web-archive@optimus.ietf.org>; Fri, 29 Nov 2002 12:25:15 -0500
Received: from www1.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA03674
	for <manet-web-archive@ietf.org>; Fri, 29 Nov 2002 12:22:25 -0500 (EST)
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gATGsWv09325;
	Fri, 29 Nov 2002 11:54:32 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gATGirv09108
	for <manet@optimus.ietf.org>; Fri, 29 Nov 2002 11:44:53 -0500
Received: from smtp.web.de (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA02965
	for <manet@ietf.org>; Fri, 29 Nov 2002 11:42:03 -0500 (EST)
Received: from [134.102.101.207] (helo=MIPNET)
	by smtp.web.de with smtp (WEB.DE(Exim) 4.91 #2)
	id 18HoG0-0007cD-00
	for manet@ietf.org; Fri, 29 Nov 2002 17:44:48 +0100
Message-ID: <001001c297c7$26ef2c90$cf656686@MIPNET>
From: "Michael Sessinghaus" <sessinghaus@web.de>
To: <manet@ietf.org>
Date: Fri, 29 Nov 2002 17:48:32 +0100
MIME-Version: 1.0
Content-Type: multipart/alternative;
	boundary="----=_NextPart_000_000D_01C297CF.88503EE0"
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 6.00.2600.0000
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2600.0000
Subject: [manet] AODV draft major changes
Sender: manet-admin@ietf.org
Errors-To: manet-admin@ietf.org
X-BeenThere: manet@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/manet>,
	<mailto:manet-request@ietf.org?subject=unsubscribe>
List-Id: Mobile Ad-hoc Networks  <manet.ietf.org>
List-Post: <mailto:manet@ietf.org>
List-Help: <mailto:manet-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/manet>,
	<mailto:manet-request@ietf.org?subject=subscribe>

This is a multi-part message in MIME format.

------=_NextPart_000_000D_01C297CF.88503EE0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

Hi,
i want to know the major changes between

AODV draft version 6 vs. version 8

and

AODV draft version 11 vs. version 8


not included any information about draft text wording.
It is for a comparison between this distinct aodv versions for ns-2.1b9a =
implementations.=20

Thanks a lot for your help.
Greetings, Michael.

------=_NextPart_000_000D_01C297CF.88503EE0
Content-Type: text/html;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META http-equiv=3DContent-Type content=3D"text/html; =
charset=3Diso-8859-1">
<META content=3D"MSHTML 6.00.2600.0" name=3DGENERATOR>
<STYLE></STYLE>
</HEAD>
<BODY bgColor=3D#ffffff>
<DIV><FONT face=3DArial size=3D2>Hi,</FONT></DIV>
<DIV><FONT face=3DArial size=3D2>i want to know the major changes=20
between</FONT></DIV>
<DIV><FONT face=3DArial size=3D2></FONT>&nbsp;</DIV>
<DIV><FONT face=3DArial size=3D2>AODV draft version 6 vs. version =
8</FONT></DIV>
<DIV><FONT face=3DArial size=3D2></FONT>&nbsp;</DIV>
<DIV><FONT face=3DArial size=3D2>and</FONT></DIV>
<DIV><FONT face=3DArial size=3D2></FONT>&nbsp;</DIV>
<DIV><FONT face=3DArial size=3D2>AODV draft version 11 vs. version =
8</FONT></DIV>
<DIV><FONT face=3DArial size=3D2></FONT>&nbsp;</DIV>
<DIV><FONT face=3DArial size=3D2></FONT>&nbsp;</DIV>
<DIV><FONT face=3DArial size=3D2>not included any information about =
draft text=20
wording.</FONT></DIV>
<DIV><FONT face=3DArial size=3D2>It is for a comparison between this =
distinct aodv=20
versions for ns-2.1b9a implementations. </FONT></DIV>
<DIV><FONT face=3DArial size=3D2></FONT>&nbsp;</DIV>
<DIV><FONT face=3DArial size=3D2>Thanks a lot for your =
help.</FONT></DIV>
<DIV><FONT face=3DArial size=3D2>Greetings, =
Michael.</FONT></DIV></BODY></HTML>

------=_NextPart_000_000D_01C297CF.88503EE0--

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



From manet-admin@ietf.org  Sat Nov 30 04:55:02 2002
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id EAA01229
	for <manet-archive@lists.ietf.org>; Sat, 30 Nov 2002 04:55:02 -0500 (EST)
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gAU9mpv28902;
	Sat, 30 Nov 2002 04:48:51 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gAU9buv28761
	for <manet@optimus.ietf.org>; Sat, 30 Nov 2002 04:37:56 -0500
Received: from web14606.mail.yahoo.com (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id EAA00999
	for <manet@ietf.org>; Sat, 30 Nov 2002 04:34:59 -0500 (EST)
Message-ID: <20021130093744.8030.qmail@web14606.mail.yahoo.com>
Received: from [193.95.33.18] by web14606.mail.yahoo.com via HTTP; Sat, 30 Nov 2002 10:37:44 CET
Date: Sat, 30 Nov 2002 10:37:44 +0100 (CET)
From: =?iso-8859-1?q?stream=20stream?= <mailadhoc@yahoo.es>
To: manet@ietf.org
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="0-971321669-1038649064=:4737"
Content-Transfer-Encoding: 8bit
Subject: [manet] security highlights in ad hoc networks
Sender: manet-admin@ietf.org
Errors-To: manet-admin@ietf.org
X-BeenThere: manet@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/manet>,
	<mailto:manet-request@ietf.org?subject=unsubscribe>
List-Id: Mobile Ad-hoc Networks  <manet.ietf.org>
List-Post: <mailto:manet@ietf.org>
List-Help: <mailto:manet-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/manet>,
	<mailto:manet-request@ietf.org?subject=subscribe>

--0-971321669-1038649064=:4737
Content-Type: text/plain; charset=iso-8859-1
Content-Transfer-Encoding: 8bit


hi there,

i began my search about security in mobile adhoc networks and i face many problems. i would be very pleased if anybody answers me some of the questions below:

- what are tha main risks?. is there solutions?

-can we use ip in ad hoc networks ?

- is there any  protocol for security (application like ssl or smime..)?

-waht are the protocols (not routing algorithms) ( niveau applicatif) in ad hoc networks.

- can we use ipsec

- what are the protocols of communication ( address, paquets....)

any help would be appreciated

best regards


---------------------------------
Yahoo! Messenger
Nueva versión: Webcam, voz, y mucho más ˇGratis!
--0-971321669-1038649064=:4737
Content-Type: text/html; charset=iso-8859-1
Content-Transfer-Encoding: 8bit

<P>hi there,</P>
<P>i began my search about security in mobile adhoc networks and i face many problems. i would be very pleased if anybody answers me some of the questions below:</P>
<P>- what are tha main risks?. is there solutions?</P>
<P>-can we use ip in ad hoc networks ?</P>
<P>- is there any&nbsp; protocol for security (application like ssl or smime..)?</P>
<P>-waht are the protocols (not routing algorithms) ( niveau applicatif) in ad hoc networks.</P>
<P>- can we use ipsec</P>
<P>- what are the protocols of communication ( address, paquets....)</P>
<P>any help would be appreciated</P>
<P>best regards</P><p><hr size=1><font face=arial,helvetica size="-1"><b>Yahoo! Messenger</b><br><a href=http://es.rd.yahoo.com/mail_es/tagline/messenger/*http://es.messenger.yahoo.com/><b>Nueva versión</b></a>: Webcam, voz, y mucho más ˇGratis!</font>
--0-971321669-1038649064=:4737--
_______________________________________________
manet mailing list
manet@ietf.org
https://www1.ietf.org/mailman/listinfo/manet


From mailnull@www1.ietf.org  Sat Nov 30 05:12:22 2002
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id FAA01478
	for <manet-archive@odin.ietf.org>; Sat, 30 Nov 2002 05:12:22 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id gAUAEbA29986
	for manet-archive@odin.ietf.org; Sat, 30 Nov 2002 05:14:37 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gAUAEbv29983
	for <manet-web-archive@optimus.ietf.org>; Sat, 30 Nov 2002 05:14:37 -0500
Received: from www1.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id FAA01469
	for <manet-web-archive@ietf.org>; Sat, 30 Nov 2002 05:11:51 -0500 (EST)
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gAU9mpv28902;
	Sat, 30 Nov 2002 04:48:51 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gAU9buv28761
	for <manet@optimus.ietf.org>; Sat, 30 Nov 2002 04:37:56 -0500
Received: from web14606.mail.yahoo.com (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id EAA00999
	for <manet@ietf.org>; Sat, 30 Nov 2002 04:34:59 -0500 (EST)
Message-ID: <20021130093744.8030.qmail@web14606.mail.yahoo.com>
Received: from [193.95.33.18] by web14606.mail.yahoo.com via HTTP; Sat, 30 Nov 2002 10:37:44 CET
Date: Sat, 30 Nov 2002 10:37:44 +0100 (CET)
From: =?iso-8859-1?q?stream=20stream?= <mailadhoc@yahoo.es>
To: manet@ietf.org
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="0-971321669-1038649064=:4737"
Content-Transfer-Encoding: 8bit
Subject: [manet] security highlights in ad hoc networks
Sender: manet-admin@ietf.org
Errors-To: manet-admin@ietf.org
X-BeenThere: manet@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/manet>,
	<mailto:manet-request@ietf.org?subject=unsubscribe>
List-Id: Mobile Ad-hoc Networks  <manet.ietf.org>
List-Post: <mailto:manet@ietf.org>
List-Help: <mailto:manet-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/manet>,
	<mailto:manet-request@ietf.org?subject=subscribe>

--0-971321669-1038649064=:4737
Content-Type: text/plain; charset=iso-8859-1
Content-Transfer-Encoding: 8bit


hi there,

i began my search about security in mobile adhoc networks and i face many problems. i would be very pleased if anybody answers me some of the questions below:

- what are tha main risks?. is there solutions?

-can we use ip in ad hoc networks ?

- is there any  protocol for security (application like ssl or smime..)?

-waht are the protocols (not routing algorithms) ( niveau applicatif) in ad hoc networks.

- can we use ipsec

- what are the protocols of communication ( address, paquets....)

any help would be appreciated

best regards


---------------------------------
Yahoo! Messenger
Nueva versión: Webcam, voz, y mucho más ˇGratis!
--0-971321669-1038649064=:4737
Content-Type: text/html; charset=iso-8859-1
Content-Transfer-Encoding: 8bit

<P>hi there,</P>
<P>i began my search about security in mobile adhoc networks and i face many problems. i would be very pleased if anybody answers me some of the questions below:</P>
<P>- what are tha main risks?. is there solutions?</P>
<P>-can we use ip in ad hoc networks ?</P>
<P>- is there any&nbsp; protocol for security (application like ssl or smime..)?</P>
<P>-waht are the protocols (not routing algorithms) ( niveau applicatif) in ad hoc networks.</P>
<P>- can we use ipsec</P>
<P>- what are the protocols of communication ( address, paquets....)</P>
<P>any help would be appreciated</P>
<P>best regards</P><p><hr size=1><font face=arial,helvetica size="-1"><b>Yahoo! Messenger</b><br><a href=http://es.rd.yahoo.com/mail_es/tagline/messenger/*http://es.messenger.yahoo.com/><b>Nueva versión</b></a>: Webcam, voz, y mucho más ˇGratis!</font>
--0-971321669-1038649064=:4737--
_______________________________________________
manet mailing list
manet@ietf.org
https://www1.ietf.org/mailman/listinfo/manet



From mailnull@www1.ietf.org  Sat Nov 30 06:22:16 2002
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id GAA02727
	for <manet-archive@odin.ietf.org>; Sat, 30 Nov 2002 06:22:16 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id gAUBOWf00588
	for manet-archive@odin.ietf.org; Sat, 30 Nov 2002 06:24:32 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gAUBOWv00585
	for <manet-web-archive@optimus.ietf.org>; Sat, 30 Nov 2002 06:24:32 -0500
Received: from www1.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id GAA02717
	for <manet-web-archive@ietf.org>; Sat, 30 Nov 2002 06:21:45 -0500 (EST)
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gAUB81v32271;
	Sat, 30 Nov 2002 06:08:01 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gAUAvCv31454
	for <manet@optimus.ietf.org>; Sat, 30 Nov 2002 05:57:12 -0500
Received: from cse.uta.edu (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id FAA02185
	for <manet@ietf.org>; Sat, 30 Nov 2002 05:54:26 -0500 (EST)
Received: from localhost by cse.uta.edu (8.9.0/8.9.0) with SMTP id EAA24186
	for <manet@ietf.org>; Sat, 30 Nov 2002 04:59:28 -0600 (CST)
Date: Sat, 30 Nov 2002 04:59:27 -0600 (CST)
From: Kumaran Sambandan <sambanda@cse.uta.edu>
X-Sender: sambanda@cse
To: manet@ietf.org
Message-ID: <Pine.GSO.3.96.1021130045708.23776A-100000@cse>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Subject: [manet] Help in ns-2
Sender: manet-admin@ietf.org
Errors-To: manet-admin@ietf.org
X-BeenThere: manet@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/manet>,
	<mailto:manet-request@ietf.org?subject=unsubscribe>
List-Id: Mobile Ad-hoc Networks  <manet.ietf.org>
List-Post: <mailto:manet@ietf.org>
List-Help: <mailto:manet-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/manet>,
	<mailto:manet-request@ietf.org?subject=subscribe>

Hi,
Iam doing a extensive study on routing protocols for ad hoc networks. I
want to know the trace file analysis in wireless domains.Suppose if i run
the wireless.tcl in Mark's tutorial what should i do to get the required
parameters of trace file analysis. Can anyone help me?

Thank you,
kumaran

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



From manet-admin@ietf.org  Sat Nov 30 06:22:40 2002
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id GAA02740
	for <manet-archive@lists.ietf.org>; Sat, 30 Nov 2002 06:22:40 -0500 (EST)
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gAUB81v32271;
	Sat, 30 Nov 2002 06:08:01 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gAUAvCv31454
	for <manet@optimus.ietf.org>; Sat, 30 Nov 2002 05:57:12 -0500
Received: from cse.uta.edu (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id FAA02185
	for <manet@ietf.org>; Sat, 30 Nov 2002 05:54:26 -0500 (EST)
Received: from localhost by cse.uta.edu (8.9.0/8.9.0) with SMTP id EAA24186
	for <manet@ietf.org>; Sat, 30 Nov 2002 04:59:28 -0600 (CST)
Date: Sat, 30 Nov 2002 04:59:27 -0600 (CST)
From: Kumaran Sambandan <sambanda@cse.uta.edu>
X-Sender: sambanda@cse
To: manet@ietf.org
Message-ID: <Pine.GSO.3.96.1021130045708.23776A-100000@cse>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Subject: [manet] Help in ns-2
Sender: manet-admin@ietf.org
Errors-To: manet-admin@ietf.org
X-BeenThere: manet@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/manet>,
	<mailto:manet-request@ietf.org?subject=unsubscribe>
List-Id: Mobile Ad-hoc Networks  <manet.ietf.org>
List-Post: <mailto:manet@ietf.org>
List-Help: <mailto:manet-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/manet>,
	<mailto:manet-request@ietf.org?subject=subscribe>

Hi,
Iam doing a extensive study on routing protocols for ad hoc networks. I
want to know the trace file analysis in wireless domains.Suppose if i run
the wireless.tcl in Mark's tutorial what should i do to get the required
parameters of trace file analysis. Can anyone help me?

Thank you,
kumaran

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


