From mailman-admin@ietf.org  Sun Dec  1 09:07: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 JAA04985
	for <manet-archive@lists.ietf.org>; Sun, 1 Dec 2002 09:07: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 gB1E9ov12804
	for <manet-archive@lists.ietf.org>; Sun, 1 Dec 2002 09:09:50 -0500
Date: Sun, 01 Dec 2002 09:09:50 -0500
Message-ID: <20021201140950.8899.29379.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: mailman-admin@ietf.org
Errors-To: mailman-admin@ietf.org
X-BeenThere: mailman@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  Sun Dec  1 22:50: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 WAA22571
	for <manet-archive@odin.ietf.org>; Sun, 1 Dec 2002 22:50:18 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id gB23qhF19006
	for manet-archive@odin.ietf.org; Sun, 1 Dec 2002 22:52: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 gB23qhv19003
	for <manet-web-archive@optimus.ietf.org>; Sun, 1 Dec 2002 22:52: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 WAA22548
	for <manet-web-archive@ietf.org>; Sun, 1 Dec 2002 22:49: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 gB23eCv18454;
	Sun, 1 Dec 2002 22:40: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 gB23biv18353
	for <manet@optimus.ietf.org>; Sun, 1 Dec 2002 22:37:44 -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 WAA22015
	for <manet@ietf.org>; Sun, 1 Dec 2002 22:34:47 -0500 (EST)
Received: from mail pickup service by hotmail.com with Microsoft SMTPSVC;
	 Sun, 1 Dec 2002 19:37:34 -0800
X-Originating-IP: [210.51.252.9]
From: "lu linyu" <linyu_lu@hotmail.com>
To: <manet@ietf.org>
Date: Mon, 2 Dec 2002 11:37:19 +0800
MIME-Version: 1.0
X-Mailer: MSN Explorer 7.00.0021.1900
Content-Type: multipart/alternative; boundary="----=_NextPart_001_0000_01C299F7.2C3444B0"
Message-ID: <OE44KfMdBGTeKtAZPV000006656@hotmail.com>
X-OriginalArrivalTime: 02 Dec 2002 03:37:34.0698 (UTC) FILETIME=[26FB94A0:01C299B4]
Subject: [manet] How to add multiple interfaces?
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_001_0000_01C299F7.2C3444B0
Content-Type: text/plain; charset="gb2312"
Content-Transfer-Encoding: quoted-printable

Hello eveyone,
     I wanted to add multiple interfaces(support 802.11b network card) to=
 mobile nodes in the ns2 simulator, one for ad hoc mode, one for ap mode,=
 does anyone know how to implement it?=B4=D3=CD=F8=D5=BE=B5=C3=B5=BD=B8=FC=
=B6=E0=D0=C5=CF=A2=A1=A3MSN Explorer =C3=E2=B7=D1=CF=C2=D4=D8:http://expl=
orer.msn.com/lccn

------=_NextPart_001_0000_01C299F7.2C3444B0
Content-Type: text/html; charset="gb2312"
Content-Transfer-Encoding: quoted-printable

<HTML><BODY STYLE=3D"font:10pt verdana; border:none;"><DIV>Hello eveyone,=
</DIV> <DIV>&nbsp;&nbsp;&nbsp;&nbsp; I wanted to add multiple interfaces(=
support 802.11b network&nbsp;card)&nbsp;to mobile nodes in the ns2 simula=
tor, one for ad hoc mode, one for ap mode, does anyone know how to implem=
ent it?<BR><BR></DIV></BODY></HTML><br clear=3Dall><hr>=B4=D3=CD=F8=D5=BE=
=B5=C3=B5=BD=B8=FC=B6=E0=D0=C5=CF=A2=A1=A3MSN Explorer =C3=E2=B7=D1=CF=C2=
=D4=D8=A3=BA<a href=3D'http://explorer.msn.com/lccn'>http://explorer.msn.=
com/lccn</a><br></p>

------=_NextPart_001_0000_01C299F7.2C3444B0--
_______________________________________________
manet mailing list
manet@ietf.org
https://www1.ietf.org/mailman/listinfo/manet



From manet-admin@ietf.org  Sun Dec  1 22:50: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 WAA22592
	for <manet-archive@lists.ietf.org>; Sun, 1 Dec 2002 22:50: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 gB23eCv18454;
	Sun, 1 Dec 2002 22:40: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 gB23biv18353
	for <manet@optimus.ietf.org>; Sun, 1 Dec 2002 22:37:44 -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 WAA22015
	for <manet@ietf.org>; Sun, 1 Dec 2002 22:34:47 -0500 (EST)
Received: from mail pickup service by hotmail.com with Microsoft SMTPSVC;
	 Sun, 1 Dec 2002 19:37:34 -0800
X-Originating-IP: [210.51.252.9]
From: "lu linyu" <linyu_lu@hotmail.com>
To: <manet@ietf.org>
Date: Mon, 2 Dec 2002 11:37:19 +0800
MIME-Version: 1.0
X-Mailer: MSN Explorer 7.00.0021.1900
Content-Type: multipart/alternative; boundary="----=_NextPart_001_0000_01C299F7.2C3444B0"
Message-ID: <OE44KfMdBGTeKtAZPV000006656@hotmail.com>
X-OriginalArrivalTime: 02 Dec 2002 03:37:34.0698 (UTC) FILETIME=[26FB94A0:01C299B4]
Subject: [manet] How to add multiple interfaces?
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_001_0000_01C299F7.2C3444B0
Content-Type: text/plain; charset="gb2312"
Content-Transfer-Encoding: quoted-printable

Hello eveyone,
     I wanted to add multiple interfaces(support 802.11b network card) to=
 mobile nodes in the ns2 simulator, one for ad hoc mode, one for ap mode,=
 does anyone know how to implement it?=B4=D3=CD=F8=D5=BE=B5=C3=B5=BD=B8=FC=
=B6=E0=D0=C5=CF=A2=A1=A3MSN Explorer =C3=E2=B7=D1=CF=C2=D4=D8:http://expl=
orer.msn.com/lccn

------=_NextPart_001_0000_01C299F7.2C3444B0
Content-Type: text/html; charset="gb2312"
Content-Transfer-Encoding: quoted-printable

<HTML><BODY STYLE=3D"font:10pt verdana; border:none;"><DIV>Hello eveyone,=
</DIV> <DIV>&nbsp;&nbsp;&nbsp;&nbsp; I wanted to add multiple interfaces(=
support 802.11b network&nbsp;card)&nbsp;to mobile nodes in the ns2 simula=
tor, one for ad hoc mode, one for ap mode, does anyone know how to implem=
ent it?<BR><BR></DIV></BODY></HTML><br clear=3Dall><hr>=B4=D3=CD=F8=D5=BE=
=B5=C3=B5=BD=B8=FC=B6=E0=D0=C5=CF=A2=A1=A3MSN Explorer =C3=E2=B7=D1=CF=C2=
=D4=D8=A3=BA<a href=3D'http://explorer.msn.com/lccn'>http://explorer.msn.=
com/lccn</a><br></p>

------=_NextPart_001_0000_01C299F7.2C3444B0--
_______________________________________________
manet mailing list
manet@ietf.org
https://www1.ietf.org/mailman/listinfo/manet


From manet-admin@ietf.org  Sun Dec  1 23:59: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 XAA24102
	for <manet-archive@lists.ietf.org>; Sun, 1 Dec 2002 23:59: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 gB24pGv22125;
	Sun, 1 Dec 2002 23:51: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 gB24nGv22043
	for <manet@optimus.ietf.org>; Sun, 1 Dec 2002 23:49:16 -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 XAA23787
	for <manet@ietf.org>; Sun, 1 Dec 2002 23:46:17 -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 gB24o6Xw029148
	for <manet@ietf.org>; Mon, 2 Dec 2002 12:50:06 +0800 (SGT)
Received: from swl1002
	([172.16.3.193])
	by gwserver.icr.a-star.edu.sg; Mon, 02 Dec 2002 12:42:41 +0800
Message-ID: <009501c299bd$40461a80$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: <manet@ietf.org>
References: <Pine.GSO.3.96.1021130045708.23776A-100000@cse>
Subject: Re: [manet] Help in ns-2
Date: Mon, 2 Dec 2002 12:42:40 +0800
Organization: Institute for Communications Research, Singapore
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


Hi Everybody,

I think it will be better to post questions regarding ns2 or any other
simulator on their respective mailing lists. These mailing lists are really
very active and you will get an immediate reply to all your queries. This
issue has already been raised by Joe Macker and others in previous messages.
I would like to know what are the comments of other members of this mailing
list.

This is not to offend anybody. Just my opinion.

Best Regards,
Ankur





~...~...~...~...~...~...~...~...~...~...~...~...~...~...~...
ANKUR JAIN

Institute for Communications Research (ICR)
(formerly Centre for Wireless Communications)
20 Science Park Road, #02-34/37,
TeleTech Park, Singapore Science Park II,
SINGAPORE 117674

Website: http://www.icr.a-star.edu.sg

Phone #    68709266
Email  #     stujaina@icr.a-star.edu.sg
                 ankurjain@ieee.org
                 ankurjain@softhome.net
~...~...~...~...~...~...~...~...~...~...~...~...~...~...~...















----- Original Message -----
From: Kumaran Sambandan <sambanda@cse.uta.edu>
To: <manet@ietf.org>
Sent: Saturday, November 30, 2002 6:59 PM
Subject: [manet] Help in ns-2


> 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

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


From mailnull@www1.ietf.org  Mon Dec  2 00:19:47 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 AAA24557
	for <manet-archive@odin.ietf.org>; Mon, 2 Dec 2002 00:19:46 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id gB25MDG23773
	for manet-archive@odin.ietf.org; Mon, 2 Dec 2002 00:22: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 gB25MDv23770
	for <manet-web-archive@optimus.ietf.org>; Mon, 2 Dec 2002 00: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 AAA24549
	for <manet-web-archive@ietf.org>; Mon, 2 Dec 2002 00:19: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 gB24pGv22125;
	Sun, 1 Dec 2002 23:51: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 gB24nGv22043
	for <manet@optimus.ietf.org>; Sun, 1 Dec 2002 23:49:16 -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 XAA23787
	for <manet@ietf.org>; Sun, 1 Dec 2002 23:46:17 -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 gB24o6Xw029148
	for <manet@ietf.org>; Mon, 2 Dec 2002 12:50:06 +0800 (SGT)
Received: from swl1002
	([172.16.3.193])
	by gwserver.icr.a-star.edu.sg; Mon, 02 Dec 2002 12:42:41 +0800
Message-ID: <009501c299bd$40461a80$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: <manet@ietf.org>
References: <Pine.GSO.3.96.1021130045708.23776A-100000@cse>
Subject: Re: [manet] Help in ns-2
Date: Mon, 2 Dec 2002 12:42:40 +0800
Organization: Institute for Communications Research, Singapore
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


Hi Everybody,

I think it will be better to post questions regarding ns2 or any other
simulator on their respective mailing lists. These mailing lists are really
very active and you will get an immediate reply to all your queries. This
issue has already been raised by Joe Macker and others in previous messages.
I would like to know what are the comments of other members of this mailing
list.

This is not to offend anybody. Just my opinion.

Best Regards,
Ankur





~...~...~...~...~...~...~...~...~...~...~...~...~...~...~...
ANKUR JAIN

Institute for Communications Research (ICR)
(formerly Centre for Wireless Communications)
20 Science Park Road, #02-34/37,
TeleTech Park, Singapore Science Park II,
SINGAPORE 117674

Website: http://www.icr.a-star.edu.sg

Phone #    68709266
Email  #     stujaina@icr.a-star.edu.sg
                 ankurjain@ieee.org
                 ankurjain@softhome.net
~...~...~...~...~...~...~...~...~...~...~...~...~...~...~...















----- Original Message -----
From: Kumaran Sambandan <sambanda@cse.uta.edu>
To: <manet@ietf.org>
Sent: Saturday, November 30, 2002 6:59 PM
Subject: [manet] Help in ns-2


> 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

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



From manet-admin@ietf.org  Mon Dec  2 03:29: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 DAA07513
	for <manet-archive@lists.ietf.org>; Mon, 2 Dec 2002 03:29: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 gB28Kiv11024;
	Mon, 2 Dec 2002 03:20: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 gB28Aqv10620
	for <manet@optimus.ietf.org>; Mon, 2 Dec 2002 03:10:52 -0500
Received: from mail.esigetel.fr (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id DAA07019
	for <manet@ietf.org>; Mon, 2 Dec 2002 03:07:52 -0500 (EST)
Received: from esigetel.fr by mail.esigetel.fr (8.8.8/1.1.22.3/04Dec99-0952PM)
	id JAA0000016333; Mon, 2 Dec 2002 09:10:40 +0100 (MET)
Message-ID: <3DEB1520.41A4C6DD@esigetel.fr>
Date: Mon, 02 Dec 2002 09:09:04 +0100
From: Leila Boukhalfa <leila.boukhalfa@esigetel.fr>
X-Mailer: Mozilla 4.7 [fr] (WinNT; I)
X-Accept-Language: fr
MIME-Version: 1.0
To: manet@ietf.org
Content-Type: text/plain; charset=iso-8859-1
Content-Transfer-Encoding: 8bit
Content-Transfer-Encoding: 8bit
Subject: [manet] help in QoS
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 begane my search about « QoS in mobile Ad-hoc networks ». I would very
pleased if any body answer me some of the questions below:

-What are parameters of QoS in Ad-hoc networks?
-What are the routing algorithms used in mobile Ad-hoc networks?
-What is the software used for simulating Ad-hoc networks?
-Are there any works (articles) wiche analyse the QoS in Ad-hoc
networks?

Any help would be appreciated

 Thank you,

Leila


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


From mailnull@www1.ietf.org  Mon Dec  2 03:53: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 DAA07981
	for <manet-archive@odin.ietf.org>; Mon, 2 Dec 2002 03:53:49 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id gB28uJV13519
	for manet-archive@odin.ietf.org; Mon, 2 Dec 2002 03:56: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 gB28uIv13516
	for <manet-web-archive@optimus.ietf.org>; Mon, 2 Dec 2002 03:56: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 DAA07952
	for <manet-web-archive@ietf.org>; Mon, 2 Dec 2002 03: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 gB28Kiv11024;
	Mon, 2 Dec 2002 03:20: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 gB28Aqv10620
	for <manet@optimus.ietf.org>; Mon, 2 Dec 2002 03:10:52 -0500
Received: from mail.esigetel.fr (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id DAA07019
	for <manet@ietf.org>; Mon, 2 Dec 2002 03:07:52 -0500 (EST)
Received: from esigetel.fr by mail.esigetel.fr (8.8.8/1.1.22.3/04Dec99-0952PM)
	id JAA0000016333; Mon, 2 Dec 2002 09:10:40 +0100 (MET)
Message-ID: <3DEB1520.41A4C6DD@esigetel.fr>
Date: Mon, 02 Dec 2002 09:09:04 +0100
From: Leila Boukhalfa <leila.boukhalfa@esigetel.fr>
X-Mailer: Mozilla 4.7 [fr] (WinNT; I)
X-Accept-Language: fr
MIME-Version: 1.0
To: manet@ietf.org
Content-Type: text/plain; charset=iso-8859-1
Content-Transfer-Encoding: 8bit
Content-Transfer-Encoding: 8bit
Subject: [manet] help in QoS
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 begane my search about « QoS in mobile Ad-hoc networks ». I would very
pleased if any body answer me some of the questions below:

-What are parameters of QoS in Ad-hoc networks?
-What are the routing algorithms used in mobile Ad-hoc networks?
-What is the software used for simulating Ad-hoc networks?
-Are there any works (articles) wiche analyse the QoS in Ad-hoc
networks?

Any help would be appreciated

 Thank you,

Leila


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



From mailnull@www1.ietf.org  Mon Dec  2 10:02: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 KAA18066
	for <manet-archive@odin.ietf.org>; Mon, 2 Dec 2002 10:02:58 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id gB2F5K603890
	for manet-archive@odin.ietf.org; Mon, 2 Dec 2002 10:05: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 gB2F5Kv03887
	for <manet-web-archive@optimus.ietf.org>; Mon, 2 Dec 2002 10:05: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 KAA18033
	for <manet-web-archive@ietf.org>; Mon, 2 Dec 2002 10:02: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 gB2EvVv03509;
	Mon, 2 Dec 2002 09:57: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 gB2EsLv03381
	for <manet@optimus.ietf.org>; Mon, 2 Dec 2002 09:54:21 -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 JAA17520
	for <manet@ietf.org>; Mon, 2 Dec 2002 09:51:28 -0500 (EST)
Received: by rrmail01.lab.flarion.com with Internet Mail Service (5.5.2656.59)
	id <YDGG6HG9>; Mon, 2 Dec 2002 09:54:12 -0500
Message-ID: <748C6D0A58C0F94CA63C198B6674697AA5D0F1@ftmail.lab.flarion.com>
From: Scott Corson <Corson@flarion.com>
To: "'Manet (manet@ietf.org)'" <manet@ietf.org>
Date: Mon, 2 Dec 2002 09:54:12 -0500 
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2656.59)
Content-Type: text/plain
Subject: [manet] WG Mtg Summary -- Comment on Consensus
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>

Folks,

This is a heads up for those not present in Atlanta and a request for
comment.

The WG met and principally discussed developments underway as a consequence
of rechartering activities.  A decision has been made by the ADs and WG
chairs to convert MANET from the psuedo-research mode of its origin into a
pure engineering group, with more mature technical work proceeding through
group consensus and scoped problem statements. The proposed approach for
rechartering and updated milestones was presented at the meeting and there
was a clear consensus of agreement that this is a good way forward.  In
parallel with MANET rechartering, an IRTF MANET RG was created as a subgroup
of the IRTF Routing RG.  The research theme of this RG is "scalability". A
set of the existing IETF MANET proposals (FSR, LANMAR, TORA, ZRP)--all
originally targeted at scalability--have been selected for relocation to
this RG.  The remaining IETF MANET I-Ds (AODV, DSR, OLSR,TBRPF) are roughly
completed and are to be submitted for Experimental RFC status to encourage
additional third party experimentation with concepts and implementations.
Lessons learned from the past years' development of these core protocols
will form the basis for the design of the new consensus-based protocol work.
The meeting concluded with four presentations giving the current status of
each of the core MANET I-Ds.

I am requesting any additional input from the list (agreement/disagreement?)

regarding this WG direction.

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



From manet-admin@ietf.org  Mon Dec  2 10:08: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 KAA18339
	for <manet-archive@lists.ietf.org>; Mon, 2 Dec 2002 10:08: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 gB2EvVv03509;
	Mon, 2 Dec 2002 09:57: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 gB2EsLv03381
	for <manet@optimus.ietf.org>; Mon, 2 Dec 2002 09:54:21 -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 JAA17520
	for <manet@ietf.org>; Mon, 2 Dec 2002 09:51:28 -0500 (EST)
Received: by rrmail01.lab.flarion.com with Internet Mail Service (5.5.2656.59)
	id <YDGG6HG9>; Mon, 2 Dec 2002 09:54:12 -0500
Message-ID: <748C6D0A58C0F94CA63C198B6674697AA5D0F1@ftmail.lab.flarion.com>
From: Scott Corson <Corson@flarion.com>
To: "'Manet (manet@ietf.org)'" <manet@ietf.org>
Date: Mon, 2 Dec 2002 09:54:12 -0500 
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2656.59)
Content-Type: text/plain
Subject: [manet] WG Mtg Summary -- Comment on Consensus
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>

Folks,

This is a heads up for those not present in Atlanta and a request for
comment.

The WG met and principally discussed developments underway as a consequence
of rechartering activities.  A decision has been made by the ADs and WG
chairs to convert MANET from the psuedo-research mode of its origin into a
pure engineering group, with more mature technical work proceeding through
group consensus and scoped problem statements. The proposed approach for
rechartering and updated milestones was presented at the meeting and there
was a clear consensus of agreement that this is a good way forward.  In
parallel with MANET rechartering, an IRTF MANET RG was created as a subgroup
of the IRTF Routing RG.  The research theme of this RG is "scalability". A
set of the existing IETF MANET proposals (FSR, LANMAR, TORA, ZRP)--all
originally targeted at scalability--have been selected for relocation to
this RG.  The remaining IETF MANET I-Ds (AODV, DSR, OLSR,TBRPF) are roughly
completed and are to be submitted for Experimental RFC status to encourage
additional third party experimentation with concepts and implementations.
Lessons learned from the past years' development of these core protocols
will form the basis for the design of the new consensus-based protocol work.
The meeting concluded with four presentations giving the current status of
each of the core MANET I-Ds.

I am requesting any additional input from the list (agreement/disagreement?)

regarding this WG direction.

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


From manet-admin@ietf.org  Mon Dec  2 10: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 KAA19208
	for <manet-archive@lists.ietf.org>; Mon, 2 Dec 2002 10: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 gB2FKgv05347;
	Mon, 2 Dec 2002 10:20: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 gB2FJGv05213
	for <manet@optimus.ietf.org>; Mon, 2 Dec 2002 10:19:16 -0500
Received: from blv-smtpout-01.boeing.com (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA18682
	for <manet@ietf.org>; Mon, 2 Dec 2002 10:16:25 -0500 (EST)
Received: from slb-av-02.boeing.com ([129.172.13.7])
	by blv-smtpout-01.boeing.com (8.9.2/8.8.5-M2) with ESMTP id HAA01438;
	Mon, 2 Dec 2002 07:19:12 -0800 (PST)
Received: from slb-hub-01.boeing.com (localhost [127.0.0.1])
	by slb-av-02.boeing.com (8.9.3/8.9.2/MBS-AV-02) with ESMTP id HAA07508;
	Mon, 2 Dec 2002 07:19:11 -0800 (PST)
Received: from xch-phl-02p.ne.nos.boeing.com (xch-phl-02p.ne.nos.boeing.com [128.225.22.4])
	by slb-hub-01.boeing.com (8.11.3/8.11.3/MBS-LDAP-01) with ESMTP id gB2FJA123481;
	Mon, 2 Dec 2002 07:19:10 -0800 (PST)
Received: by xch-phl-02p.ne.nos.boeing.com with Internet Mail Service (5.5.2653.19)
	id <XQHZY1HV>; Mon, 2 Dec 2002 10:19:10 -0500
Message-ID: <D18F53ABCD79C14495301518A54E52200AC1D5@xch-ne-01.ne.nos.boeing.com>
From: "Manfredi, Albert E" <albert.e.manfredi@boeing.com>
To: "'Scott Corson'" <Corson@flarion.com>,
        "'Manet (manet@ietf.org)'"
	 <manet@ietf.org>
Subject: RE: [manet] WG Mtg Summary -- Comment on Consensus
Date: Mon, 2 Dec 2002 10:19:05 -0500 
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2653.19)
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>

Scott,

While I am not one to put strict boundaries on what constitutes "research" as opposed to "engineering," I agree with the new direction, to help move this thing forward. There are many out there who think that "a MANET standard" exists, and make decisions based on that misconception. Probably high time some sort of standards really did become available.

Bert


> -----Original Message-----
> From: Scott Corson [mailto:Corson@flarion.com]
> Sent: Monday, December 02, 2002 9:54 AM
> To: 'Manet (manet@ietf.org)'
> Subject: [manet] WG Mtg Summary -- Comment on Consensus
> 
> 
> Folks,
> 
> This is a heads up for those not present in Atlanta and a request for
> comment.
> 
> The WG met and principally discussed developments underway as 
> a consequence
> of rechartering activities.  A decision has been made by the 
> ADs and WG
> chairs to convert MANET from the psuedo-research mode of its 
> origin into a
> pure engineering group, with more mature technical work 
> proceeding through
> group consensus and scoped problem statements. The proposed 
> approach for
> rechartering and updated milestones was presented at the 
> meeting and there
> was a clear consensus of agreement that this is a good way 
> forward.  In
> parallel with MANET rechartering, an IRTF MANET RG was 
> created as a subgroup
> of the IRTF Routing RG.  The research theme of this RG is 
> "scalability". A
> set of the existing IETF MANET proposals (FSR, LANMAR, TORA, ZRP)--all
> originally targeted at scalability--have been selected for 
> relocation to
> this RG.  The remaining IETF MANET I-Ds (AODV, DSR, 
> OLSR,TBRPF) are roughly
> completed and are to be submitted for Experimental RFC status 
> to encourage
> additional third party experimentation with concepts and 
> implementations.
> Lessons learned from the past years' development of these 
> core protocols
> will form the basis for the design of the new consensus-based 
> protocol work.
> The meeting concluded with four presentations giving the 
> current status of
> each of the core MANET I-Ds.
> 
> I am requesting any additional input from the list 
> (agreement/disagreement?)
> 
> regarding this WG direction.
> 
> -Scott
_______________________________________________
manet mailing list
manet@ietf.org
https://www1.ietf.org/mailman/listinfo/manet


From mailnull@www1.ietf.org  Mon Dec  2 10: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 KAA21026
	for <manet-archive@odin.ietf.org>; Mon, 2 Dec 2002 10:52:38 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id gB2FsxT08313
	for manet-archive@odin.ietf.org; Mon, 2 Dec 2002 10:54: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 gB2Fsxv08310
	for <manet-web-archive@optimus.ietf.org>; Mon, 2 Dec 2002 10:54: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 KAA20998
	for <manet-web-archive@ietf.org>; Mon, 2 Dec 2002 10: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 gB2FKgv05347;
	Mon, 2 Dec 2002 10:20: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 gB2FJGv05213
	for <manet@optimus.ietf.org>; Mon, 2 Dec 2002 10:19:16 -0500
Received: from blv-smtpout-01.boeing.com (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA18682
	for <manet@ietf.org>; Mon, 2 Dec 2002 10:16:25 -0500 (EST)
Received: from slb-av-02.boeing.com ([129.172.13.7])
	by blv-smtpout-01.boeing.com (8.9.2/8.8.5-M2) with ESMTP id HAA01438;
	Mon, 2 Dec 2002 07:19:12 -0800 (PST)
Received: from slb-hub-01.boeing.com (localhost [127.0.0.1])
	by slb-av-02.boeing.com (8.9.3/8.9.2/MBS-AV-02) with ESMTP id HAA07508;
	Mon, 2 Dec 2002 07:19:11 -0800 (PST)
Received: from xch-phl-02p.ne.nos.boeing.com (xch-phl-02p.ne.nos.boeing.com [128.225.22.4])
	by slb-hub-01.boeing.com (8.11.3/8.11.3/MBS-LDAP-01) with ESMTP id gB2FJA123481;
	Mon, 2 Dec 2002 07:19:10 -0800 (PST)
Received: by xch-phl-02p.ne.nos.boeing.com with Internet Mail Service (5.5.2653.19)
	id <XQHZY1HV>; Mon, 2 Dec 2002 10:19:10 -0500
Message-ID: <D18F53ABCD79C14495301518A54E52200AC1D5@xch-ne-01.ne.nos.boeing.com>
From: "Manfredi, Albert E" <albert.e.manfredi@boeing.com>
To: "'Scott Corson'" <Corson@flarion.com>,
        "'Manet (manet@ietf.org)'"
	 <manet@ietf.org>
Subject: RE: [manet] WG Mtg Summary -- Comment on Consensus
Date: Mon, 2 Dec 2002 10:19:05 -0500 
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2653.19)
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>

Scott,

While I am not one to put strict boundaries on what constitutes "research" as opposed to "engineering," I agree with the new direction, to help move this thing forward. There are many out there who think that "a MANET standard" exists, and make decisions based on that misconception. Probably high time some sort of standards really did become available.

Bert


> -----Original Message-----
> From: Scott Corson [mailto:Corson@flarion.com]
> Sent: Monday, December 02, 2002 9:54 AM
> To: 'Manet (manet@ietf.org)'
> Subject: [manet] WG Mtg Summary -- Comment on Consensus
> 
> 
> Folks,
> 
> This is a heads up for those not present in Atlanta and a request for
> comment.
> 
> The WG met and principally discussed developments underway as 
> a consequence
> of rechartering activities.  A decision has been made by the 
> ADs and WG
> chairs to convert MANET from the psuedo-research mode of its 
> origin into a
> pure engineering group, with more mature technical work 
> proceeding through
> group consensus and scoped problem statements. The proposed 
> approach for
> rechartering and updated milestones was presented at the 
> meeting and there
> was a clear consensus of agreement that this is a good way 
> forward.  In
> parallel with MANET rechartering, an IRTF MANET RG was 
> created as a subgroup
> of the IRTF Routing RG.  The research theme of this RG is 
> "scalability". A
> set of the existing IETF MANET proposals (FSR, LANMAR, TORA, ZRP)--all
> originally targeted at scalability--have been selected for 
> relocation to
> this RG.  The remaining IETF MANET I-Ds (AODV, DSR, 
> OLSR,TBRPF) are roughly
> completed and are to be submitted for Experimental RFC status 
> to encourage
> additional third party experimentation with concepts and 
> implementations.
> Lessons learned from the past years' development of these 
> core protocols
> will form the basis for the design of the new consensus-based 
> protocol work.
> The meeting concluded with four presentations giving the 
> current status of
> each of the core MANET I-Ds.
> 
> I am requesting any additional input from the list 
> (agreement/disagreement?)
> 
> regarding this WG direction.
> 
> -Scott
_______________________________________________
manet mailing list
manet@ietf.org
https://www1.ietf.org/mailman/listinfo/manet



From manet-admin@ietf.org  Mon Dec  2 13:13: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 NAA00207
	for <manet-archive@lists.ietf.org>; Mon, 2 Dec 2002 13:13: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 gB2I7Rv19263;
	Mon, 2 Dec 2002 13:07: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 gB2I0cv18460
	for <manet@optimus.ietf.org>; Mon, 2 Dec 2002 13:00:38 -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 MAA29326
	for <manet@ietf.org>; Mon, 2 Dec 2002 12:57:43 -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 NAA09537;
	Mon, 2 Dec 2002 13:00:21 -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 M2002120213002009544
 ; Mon, 02 Dec 2002 13:00:20 -0500
Message-Id: <5.1.1.5.2.20021202125841.014c3e58@pop.itd.nrl.navy.mil>
X-Sender: macker@pop.itd.nrl.navy.mil
X-Mailer: QUALCOMM Windows Eudora Version 5.1.1
Date: Mon, 02 Dec 2002 13:02:03 -0500
To: Scott Corson <Corson@flarion.com>,
        "'Manet (manet@ietf.org)'" <manet@ietf.org>
From: Joe Macker <macker@itd.nrl.navy.mil>
Subject: Re: [manet] WG Mtg Summary -- Comment on Consensus
In-Reply-To: <748C6D0A58C0F94CA63C198B6674697AA5D0F1@ftmail.lab.flarion.
 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>

To add to Scott's note the meeting minutes were posted and have more details for those interested.

-Joe
At 09:54 AM 12/2/2002 -0500, Scott Corson wrote:
>Folks,
>
>This is a heads up for those not present in Atlanta and a request for
>comment.
>
>The WG met and principally discussed developments underway as a consequence
>of rechartering activities.  A decision has been made by the ADs and WG
>chairs to convert MANET from the psuedo-research mode of its origin into a
>pure engineering group, with more mature technical work proceeding through
>group consensus and scoped problem statements. The proposed approach for
>rechartering and updated milestones was presented at the meeting and there
>was a clear consensus of agreement that this is a good way forward.  In
>parallel with MANET rechartering, an IRTF MANET RG was created as a subgroup
>of the IRTF Routing RG.  The research theme of this RG is "scalability". A
>set of the existing IETF MANET proposals (FSR, LANMAR, TORA, ZRP)--all
>originally targeted at scalability--have been selected for relocation to
>this RG.  The remaining IETF MANET I-Ds (AODV, DSR, OLSR,TBRPF) are roughly
>completed and are to be submitted for Experimental RFC status to encourage
>additional third party experimentation with concepts and implementations.
>Lessons learned from the past years' development of these core protocols
>will form the basis for the design of the new consensus-based protocol work.
>The meeting concluded with four presentations giving the current status of
>each of the core MANET I-Ds.
>
>I am requesting any additional input from the list (agreement/disagreement?)
>
>regarding this WG direction.
>
>-Scott
>_______________________________________________
>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 Dec  2 13:33: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 NAA01407
	for <manet-archive@odin.ietf.org>; Mon, 2 Dec 2002 13:33:49 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id gB2IaCL21176
	for manet-archive@odin.ietf.org; Mon, 2 Dec 2002 13: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 gB2IaCv21173
	for <manet-web-archive@optimus.ietf.org>; Mon, 2 Dec 2002 13: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 NAA01390
	for <manet-web-archive@ietf.org>; Mon, 2 Dec 2002 13:33: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 gB2I7Rv19263;
	Mon, 2 Dec 2002 13:07: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 gB2I0cv18460
	for <manet@optimus.ietf.org>; Mon, 2 Dec 2002 13:00:38 -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 MAA29326
	for <manet@ietf.org>; Mon, 2 Dec 2002 12:57:43 -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 NAA09537;
	Mon, 2 Dec 2002 13:00:21 -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 M2002120213002009544
 ; Mon, 02 Dec 2002 13:00:20 -0500
Message-Id: <5.1.1.5.2.20021202125841.014c3e58@pop.itd.nrl.navy.mil>
X-Sender: macker@pop.itd.nrl.navy.mil
X-Mailer: QUALCOMM Windows Eudora Version 5.1.1
Date: Mon, 02 Dec 2002 13:02:03 -0500
To: Scott Corson <Corson@flarion.com>,
        "'Manet (manet@ietf.org)'" <manet@ietf.org>
From: Joe Macker <macker@itd.nrl.navy.mil>
Subject: Re: [manet] WG Mtg Summary -- Comment on Consensus
In-Reply-To: <748C6D0A58C0F94CA63C198B6674697AA5D0F1@ftmail.lab.flarion.
 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>

To add to Scott's note the meeting minutes were posted and have more details for those interested.

-Joe
At 09:54 AM 12/2/2002 -0500, Scott Corson wrote:
>Folks,
>
>This is a heads up for those not present in Atlanta and a request for
>comment.
>
>The WG met and principally discussed developments underway as a consequence
>of rechartering activities.  A decision has been made by the ADs and WG
>chairs to convert MANET from the psuedo-research mode of its origin into a
>pure engineering group, with more mature technical work proceeding through
>group consensus and scoped problem statements. The proposed approach for
>rechartering and updated milestones was presented at the meeting and there
>was a clear consensus of agreement that this is a good way forward.  In
>parallel with MANET rechartering, an IRTF MANET RG was created as a subgroup
>of the IRTF Routing RG.  The research theme of this RG is "scalability". A
>set of the existing IETF MANET proposals (FSR, LANMAR, TORA, ZRP)--all
>originally targeted at scalability--have been selected for relocation to
>this RG.  The remaining IETF MANET I-Ds (AODV, DSR, OLSR,TBRPF) are roughly
>completed and are to be submitted for Experimental RFC status to encourage
>additional third party experimentation with concepts and implementations.
>Lessons learned from the past years' development of these core protocols
>will form the basis for the design of the new consensus-based protocol work.
>The meeting concluded with four presentations giving the current status of
>each of the core MANET I-Ds.
>
>I am requesting any additional input from the list (agreement/disagreement?)
>
>regarding this WG direction.
>
>-Scott
>_______________________________________________
>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 Dec  2 14:30:47 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 OAA05615
	for <manet-archive@lists.ietf.org>; Mon, 2 Dec 2002 14:30: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 gB2JKNv24870;
	Mon, 2 Dec 2002 14:20: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 gB2JIOv24677
	for <manet@optimus.ietf.org>; Mon, 2 Dec 2002 14:18:24 -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 OAA04815
	for <manet@ietf.org>; Mon, 2 Dec 2002 14:15:29 -0500 (EST)
Received: from mail pickup service by hotmail.com with Microsoft SMTPSVC;
	 Mon, 2 Dec 2002 11:18:13 -0800
Received: from 217.136.114.46 by pv1fd.pav1.hotmail.msn.com with HTTP;
	Mon, 02 Dec 2002 19:18:13 GMT
X-Originating-IP: [217.136.114.46]
From: "ayman ghazi" <aymanghazi10@hotmail.com>
To: manet@ietf.org
Date: Mon, 02 Dec 2002 19:18:13 +0000
Mime-Version: 1.0
Content-Type: text/html
Message-ID: <F20RxBNIT5PhJyNPTuO00019d79@hotmail.com>
X-OriginalArrivalTime: 02 Dec 2002 19:18:13.0793 (UTC) FILETIME=[8F4E0910:01C29A37]
Subject: [manet] AODV
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>

<html><div style='background-color:'><DIV>
<P><BR><BR></P>Hello,</DIV>
<DIV>I am doing a study on AODV, and I want to ask these questions please for any one have the answers.</DIV>
<DIV>In AODV, how each node know each other sequence number ?? and when a new node add to the netwrok, how it will identify it self ??? </DIV>
<DIV>&nbsp;</DIV>
<DIV>Thanks </DIV>
<DIV>&nbsp;</DIV>
<DIV>Ayman </DIV></div><br clear=all><hr>Protect your PC - <a href="http://g.msn.com/8HMTEN/2024">Click here</a> for McAfee.com VirusScan Online </html>
_______________________________________________
manet mailing list
manet@ietf.org
https://www1.ietf.org/mailman/listinfo/manet


From mailnull@www1.ietf.org  Mon Dec  2 14:48: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 OAA06725
	for <manet-archive@odin.ietf.org>; Mon, 2 Dec 2002 14:48:50 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id gB2JpEO27130
	for manet-archive@odin.ietf.org; Mon, 2 Dec 2002 14: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 gB2JpEv27127
	for <manet-web-archive@optimus.ietf.org>; Mon, 2 Dec 2002 14:51: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 OAA06698
	for <manet-web-archive@ietf.org>; Mon, 2 Dec 2002 14:48: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 gB2JKNv24870;
	Mon, 2 Dec 2002 14:20: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 gB2JIOv24677
	for <manet@optimus.ietf.org>; Mon, 2 Dec 2002 14:18:24 -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 OAA04815
	for <manet@ietf.org>; Mon, 2 Dec 2002 14:15:29 -0500 (EST)
Received: from mail pickup service by hotmail.com with Microsoft SMTPSVC;
	 Mon, 2 Dec 2002 11:18:13 -0800
Received: from 217.136.114.46 by pv1fd.pav1.hotmail.msn.com with HTTP;
	Mon, 02 Dec 2002 19:18:13 GMT
X-Originating-IP: [217.136.114.46]
From: "ayman ghazi" <aymanghazi10@hotmail.com>
To: manet@ietf.org
Date: Mon, 02 Dec 2002 19:18:13 +0000
Mime-Version: 1.0
Content-Type: text/html
Message-ID: <F20RxBNIT5PhJyNPTuO00019d79@hotmail.com>
X-OriginalArrivalTime: 02 Dec 2002 19:18:13.0793 (UTC) FILETIME=[8F4E0910:01C29A37]
Subject: [manet] AODV
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>

<html><div style='background-color:'><DIV>
<P><BR><BR></P>Hello,</DIV>
<DIV>I am doing a study on AODV, and I want to ask these questions please for any one have the answers.</DIV>
<DIV>In AODV, how each node know each other sequence number ?? and when a new node add to the netwrok, how it will identify it self ??? </DIV>
<DIV>&nbsp;</DIV>
<DIV>Thanks </DIV>
<DIV>&nbsp;</DIV>
<DIV>Ayman </DIV></div><br clear=all><hr>Protect your PC - <a href="http://g.msn.com/8HMTEN/2024">Click here</a> for McAfee.com VirusScan Online </html>
_______________________________________________
manet mailing list
manet@ietf.org
https://www1.ietf.org/mailman/listinfo/manet



From mailnull@www1.ietf.org  Mon Dec  2 17:30: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 RAA15511
	for <manet-archive@odin.ietf.org>; Mon, 2 Dec 2002 17:30:27 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id gB2MWp706577
	for manet-archive@odin.ietf.org; Mon, 2 Dec 2002 17:32: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 gB2MWpv06574
	for <manet-web-archive@optimus.ietf.org>; Mon, 2 Dec 2002 17:32: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 RAA15474
	for <manet-web-archive@ietf.org>; Mon, 2 Dec 2002 17:29: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 gB2MLhv05832;
	Mon, 2 Dec 2002 17: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 gB2MJXv05702
	for <manet@optimus.ietf.org>; Mon, 2 Dec 2002 17:19:33 -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 RAA14746
	for <manet@ietf.org>; Mon, 2 Dec 2002 17:16:38 -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 OAA14165;
	Mon, 2 Dec 2002 14:19:24 -0800 (PST)
Received: (from root@localhost)
	by darkstar.iprg.nokia.com (8.11.0/8.11.0-DARKSTAR) id gB2MJNN07169;
	Mon, 2 Dec 2002 14:19:23 -0800
X-mProtect: <200212022219> Nokia Silicon Valley Messaging Protection
Received: from UNKNOWN (172.18.5.34, claiming to be "iprg.nokia.com")
	by darkstar.iprg.nokia.com smtpdkZuVSa; Mon, 02 Dec 2002 14:19:21 PST
Message-ID: <3DEBDC22.4A7497DF@iprg.nokia.com>
Date: Mon, 02 Dec 2002 14:18:10 -0800
From: Charlie Perkins <charliep@iprg.nokia.com>
Organization: Nokia
X-Mailer: Mozilla 4.75 [en]C-CCK-MCD {Nokia}  (Windows NT 5.0; U)
X-Accept-Language: en
MIME-Version: 1.0
To: ayman ghazi <aymanghazi10@hotmail.com>
CC: manet@ietf.org
Subject: Re: [manet] AODV
References: <F20RxBNIT5PhJyNPTuO00019d79@hotmail.com>
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 Ayman,

In AODV, nodes find out about each others' sequence numbers only
as needed, typically by receiving RREQ or RREP messages.

A node could join an ad hoc network and not be known at all.
If it tries to communicate with another node in the network, it
would need to run some routing protocol to find a communications
path to that node.  There is no one single answer to your question.

Regards,
Charlie P.



ayman ghazi wrote:

>
>
>
>
> Hello,I am doing a study on AODV, and I want to ask these questions
> please for any one have the answers.In AODV, how each node know each
> other sequence number ?? and when a new node add to the netwrok, how
> it will identify it self ??? Thanks Ayman
>
>
> -----------------------------------------------------------------------
> Protect your PC - Click here for McAfee.com VirusScan Online
> _______________________________________________ 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 Dec  2 17:31: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 RAA15574
	for <manet-archive@lists.ietf.org>; Mon, 2 Dec 2002 17: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 gB2MLhv05832;
	Mon, 2 Dec 2002 17: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 gB2MJXv05702
	for <manet@optimus.ietf.org>; Mon, 2 Dec 2002 17:19:33 -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 RAA14746
	for <manet@ietf.org>; Mon, 2 Dec 2002 17:16:38 -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 OAA14165;
	Mon, 2 Dec 2002 14:19:24 -0800 (PST)
Received: (from root@localhost)
	by darkstar.iprg.nokia.com (8.11.0/8.11.0-DARKSTAR) id gB2MJNN07169;
	Mon, 2 Dec 2002 14:19:23 -0800
X-mProtect: <200212022219> Nokia Silicon Valley Messaging Protection
Received: from UNKNOWN (172.18.5.34, claiming to be "iprg.nokia.com")
	by darkstar.iprg.nokia.com smtpdkZuVSa; Mon, 02 Dec 2002 14:19:21 PST
Message-ID: <3DEBDC22.4A7497DF@iprg.nokia.com>
Date: Mon, 02 Dec 2002 14:18:10 -0800
From: Charlie Perkins <charliep@iprg.nokia.com>
Organization: Nokia
X-Mailer: Mozilla 4.75 [en]C-CCK-MCD {Nokia}  (Windows NT 5.0; U)
X-Accept-Language: en
MIME-Version: 1.0
To: ayman ghazi <aymanghazi10@hotmail.com>
CC: manet@ietf.org
Subject: Re: [manet] AODV
References: <F20RxBNIT5PhJyNPTuO00019d79@hotmail.com>
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 Ayman,

In AODV, nodes find out about each others' sequence numbers only
as needed, typically by receiving RREQ or RREP messages.

A node could join an ad hoc network and not be known at all.
If it tries to communicate with another node in the network, it
would need to run some routing protocol to find a communications
path to that node.  There is no one single answer to your question.

Regards,
Charlie P.



ayman ghazi wrote:

>
>
>
>
> Hello,I am doing a study on AODV, and I want to ask these questions
> please for any one have the answers.In AODV, how each node know each
> other sequence number ?? and when a new node add to the netwrok, how
> it will identify it self ??? Thanks Ayman
>
>
> -----------------------------------------------------------------------
> Protect your PC - Click here for McAfee.com VirusScan Online
> _______________________________________________ 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 Dec  2 18:18: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 SAA17017
	for <manet-archive@odin.ietf.org>; Mon, 2 Dec 2002 18:18:10 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id gB2NKZQ09821
	for manet-archive@odin.ietf.org; Mon, 2 Dec 2002 18:20: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 gB2NKZv09818
	for <manet-web-archive@optimus.ietf.org>; Mon, 2 Dec 2002 18:20: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 SAA16976
	for <manet-web-archive@ietf.org>; Mon, 2 Dec 2002 18:17: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 gB2N9Vv09255;
	Mon, 2 Dec 2002 18:09: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 gB2N8Ev09209
	for <manet@optimus.ietf.org>; Mon, 2 Dec 2002 18:08:14 -0500
Received: from pit.erg.sri.com (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA16579
	for <manet@ietf.org>; Mon, 2 Dec 2002 18:05:18 -0500 (EST)
Received: from pit.erg.sri.com (localhost [127.0.0.1])
	by pit.erg.sri.com (8.9.3+Sun/8.9.1) with ESMTP id PAA02730;
	Mon, 2 Dec 2002 15:04:32 -0800 (PST)
Message-Id: <200212022304.PAA02730@pit.erg.sri.com>
To: manet@ietf.org
CC: ogier@erg.sri.com
From: ogier@erg.sri.com
Reply-to: ogier@erg.sri.com
Date: Mon, 02 Dec 2002 15:04:31 -0800
Subject: [manet] Suggestions for new problem 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>


To all,

I would like to offer some suggestions for the new problem statement.  
Joe presented a preliminary problem statement that said the protocol 
should support up to 100 nodes, but I know this is up for discussion.

At the meeting in Atlanta, at least one person suggested 
that we not limit ourselves to only 100 nodes since some or all
of the proposed protocols can already support more than that,
and I agree with this.  

I know that AODV, TBRPF, and OLSR can all support at least 250 nodes
and probably more, using 802.11 with rate 2 Mbps.

I think the protocol should be as scalable and efficient as 
possible without being "too complex", and without using
hierarchical routing.  

It is generally agreed that the protocol should be extendable
to a scalable protocol (e.g., using a hierarchical method such
as landmark routing).
HOWEVER, IF THE PROTOCOL CAN SUPPORT MORE NODES WITHOUT USING
HIERARCHICAL ROUTING, THEN ITS HIERARCHICAL EXTENSION WILL
SUPPORT MORE NODES.  (The same is true for other scalability
techniques such as HSLS and FSR.)

Perhaps the problem statement can give 100 or 250 nodes as a 
*minimum requirement*, and state that when alternative techniques are 
available that are reasonably simple and well understood, preference 
should be given to techniques that perform better, e.g. that:

  1. Support more nodes 
  2. Support a higher level of mobility and dynamics
  3. Have better delivery ratio and end-to-end delay
  4. Provide shorter paths
  5. Generate less overhead (or "total overhead")
  6. Support lower bandwidth links 

We also need to be careful about stating the minimum requirements for
mobility.  For example, the number of topology changes per second for 
nodes traveling 20 mps according to the random waypoint model is much 
greater in an urban environment than it is in an open field.

Richard 

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



From manet-admin@ietf.org  Mon Dec  2 18:18: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 SAA17157
	for <manet-archive@lists.ietf.org>; Mon, 2 Dec 2002 18:18: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 gB2N9Vv09255;
	Mon, 2 Dec 2002 18:09: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 gB2N8Ev09209
	for <manet@optimus.ietf.org>; Mon, 2 Dec 2002 18:08:14 -0500
Received: from pit.erg.sri.com (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA16579
	for <manet@ietf.org>; Mon, 2 Dec 2002 18:05:18 -0500 (EST)
Received: from pit.erg.sri.com (localhost [127.0.0.1])
	by pit.erg.sri.com (8.9.3+Sun/8.9.1) with ESMTP id PAA02730;
	Mon, 2 Dec 2002 15:04:32 -0800 (PST)
Message-Id: <200212022304.PAA02730@pit.erg.sri.com>
To: manet@ietf.org
CC: ogier@erg.sri.com
From: ogier@erg.sri.com
Reply-to: ogier@erg.sri.com
Date: Mon, 02 Dec 2002 15:04:31 -0800
Subject: [manet] Suggestions for new problem 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>


To all,

I would like to offer some suggestions for the new problem statement.  
Joe presented a preliminary problem statement that said the protocol 
should support up to 100 nodes, but I know this is up for discussion.

At the meeting in Atlanta, at least one person suggested 
that we not limit ourselves to only 100 nodes since some or all
of the proposed protocols can already support more than that,
and I agree with this.  

I know that AODV, TBRPF, and OLSR can all support at least 250 nodes
and probably more, using 802.11 with rate 2 Mbps.

I think the protocol should be as scalable and efficient as 
possible without being "too complex", and without using
hierarchical routing.  

It is generally agreed that the protocol should be extendable
to a scalable protocol (e.g., using a hierarchical method such
as landmark routing).
HOWEVER, IF THE PROTOCOL CAN SUPPORT MORE NODES WITHOUT USING
HIERARCHICAL ROUTING, THEN ITS HIERARCHICAL EXTENSION WILL
SUPPORT MORE NODES.  (The same is true for other scalability
techniques such as HSLS and FSR.)

Perhaps the problem statement can give 100 or 250 nodes as a 
*minimum requirement*, and state that when alternative techniques are 
available that are reasonably simple and well understood, preference 
should be given to techniques that perform better, e.g. that:

  1. Support more nodes 
  2. Support a higher level of mobility and dynamics
  3. Have better delivery ratio and end-to-end delay
  4. Provide shorter paths
  5. Generate less overhead (or "total overhead")
  6. Support lower bandwidth links 

We also need to be careful about stating the minimum requirements for
mobility.  For example, the number of topology changes per second for 
nodes traveling 20 mps according to the random waypoint model is much 
greater in an urban environment than it is in an open field.

Richard 

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


From manet-admin@ietf.org  Tue Dec  3 06:32: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 GAA15213
	for <manet-archive@lists.ietf.org>; Tue, 3 Dec 2002 06:32: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 gB3BKvv31955;
	Tue, 3 Dec 2002 06:20: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 gB3BIuv31858
	for <manet@optimus.ietf.org>; Tue, 3 Dec 2002 06:18:56 -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 GAA14874
	for <manet@ietf.org>; Tue, 3 Dec 2002 06:16:06 -0500 (EST)
Received: from mail pickup service by hotmail.com with Microsoft SMTPSVC;
	 Tue, 3 Dec 2002 03:18:54 -0800
Received: from 219.65.116.146 by lw9fd.law9.hotmail.msn.com with HTTP;
	Tue, 03 Dec 2002 11:18:54 GMT
X-Originating-IP: [219.65.116.146]
From: "Jigar Doshi" <jigarnetmeet@hotmail.com>
To: manet@ietf.org
Date: Tue, 03 Dec 2002 16:48:54 +0530
Mime-Version: 1.0
Content-Type: text/html
Message-ID: <F165rtpThrOGoA2ELGj0001253c@hotmail.com>
X-OriginalArrivalTime: 03 Dec 2002 11:18:54.0766 (UTC) FILETIME=[C40084E0:01C29ABD]
Subject: [manet] is info on link capacity available to a manet 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>

<html><div style='background-color:'><DIV>
<P>Hello,<BR><BR>Does the network layer report information such as link capacity ( i.e bandwidth ) and/or expected remaining battery life . We are currently developing a protocol which uses this information to calculate optimum paths .A way out of the bandwidth calculation would be indirectly measuring the performance of the link by sending packets across. Is there a more efficient way? Can it be assumed tht such information is available , while designing the protocol like the conventional protocols.</P>
<P>Jigar Doshi&nbsp;&amp; K Prahlad<BR><BR></P></DIV></div><br clear=all><hr>Tired of spam? Get <a href="http://g.msn.com/8HMSEN/2017">advanced junk mail protection</a> with MSN 8.</html>
_______________________________________________
manet mailing list
manet@ietf.org
https://www1.ietf.org/mailman/listinfo/manet


From mailnull@www1.ietf.org  Tue Dec  3 06:50: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 GAA15471
	for <manet-archive@odin.ietf.org>; Tue, 3 Dec 2002 06:50:01 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id gB3BqKo01486
	for manet-archive@odin.ietf.org; Tue, 3 Dec 2002 06:52: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 gB3BqKv01483
	for <manet-web-archive@optimus.ietf.org>; Tue, 3 Dec 2002 06:52: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 GAA15456
	for <manet-web-archive@ietf.org>; Tue, 3 Dec 2002 06:49: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 gB3BKvv31955;
	Tue, 3 Dec 2002 06:20: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 gB3BIuv31858
	for <manet@optimus.ietf.org>; Tue, 3 Dec 2002 06:18:56 -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 GAA14874
	for <manet@ietf.org>; Tue, 3 Dec 2002 06:16:06 -0500 (EST)
Received: from mail pickup service by hotmail.com with Microsoft SMTPSVC;
	 Tue, 3 Dec 2002 03:18:54 -0800
Received: from 219.65.116.146 by lw9fd.law9.hotmail.msn.com with HTTP;
	Tue, 03 Dec 2002 11:18:54 GMT
X-Originating-IP: [219.65.116.146]
From: "Jigar Doshi" <jigarnetmeet@hotmail.com>
To: manet@ietf.org
Date: Tue, 03 Dec 2002 16:48:54 +0530
Mime-Version: 1.0
Content-Type: text/html
Message-ID: <F165rtpThrOGoA2ELGj0001253c@hotmail.com>
X-OriginalArrivalTime: 03 Dec 2002 11:18:54.0766 (UTC) FILETIME=[C40084E0:01C29ABD]
Subject: [manet] is info on link capacity available to a manet 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>

<html><div style='background-color:'><DIV>
<P>Hello,<BR><BR>Does the network layer report information such as link capacity ( i.e bandwidth ) and/or expected remaining battery life . We are currently developing a protocol which uses this information to calculate optimum paths .A way out of the bandwidth calculation would be indirectly measuring the performance of the link by sending packets across. Is there a more efficient way? Can it be assumed tht such information is available , while designing the protocol like the conventional protocols.</P>
<P>Jigar Doshi&nbsp;&amp; K Prahlad<BR><BR></P></DIV></div><br clear=all><hr>Tired of spam? Get <a href="http://g.msn.com/8HMSEN/2017">advanced junk mail protection</a> with MSN 8.</html>
_______________________________________________
manet mailing list
manet@ietf.org
https://www1.ietf.org/mailman/listinfo/manet



From mailnull@www1.ietf.org  Tue Dec  3 08: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 IAA20282
	for <manet-archive@odin.ietf.org>; Tue, 3 Dec 2002 08:59:21 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id gB3E1h209802
	for manet-archive@odin.ietf.org; Tue, 3 Dec 2002 09:01: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 gB3E1gv09799
	for <manet-web-archive@optimus.ietf.org>; Tue, 3 Dec 2002 09:01:42 -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 IAA20226
	for <manet-web-archive@ietf.org>; Tue, 3 Dec 2002 08:58: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 gB3DsCv09312;
	Tue, 3 Dec 2002 08:54: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 gB3Dpdv09106
	for <manet@optimus.ietf.org>; Tue, 3 Dec 2002 08:51:39 -0500
Received: from mail.rz.uni-ulm.de (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA19549
	for <manet@ietf.org>; Tue, 3 Dec 2002 08:48:47 -0500 (EST)
Received: from informatik.uni-ulm.de (shark.informatik.uni-ulm.de [134.60.70.12])
	by mail.rz.uni-ulm.de (8.12.6/8.12.6) with ESMTP id gB3DpZLb021361;
	Tue, 3 Dec 2002 14:51:36 +0100 (MET)
Message-ID: <3DECB6CC.3030003@informatik.uni-ulm.de>
Date: Tue, 03 Dec 2002 14:51:08 +0100
From: Frank Kargl <frank.kargl@informatik.uni-ulm.de>
Organization: University of Ulm
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.2) Gecko/20021126
X-Accept-Language: de-de, de, en-us, en
MIME-Version: 1.0
To: stream stream <mailadhoc@yahoo.es>
CC: manet@ietf.org
Subject: Re: [manet] security highlights in ad hoc networks
References: <20021130093744.8030.qmail@web14606.mail.yahoo.com>
In-Reply-To: <20021130093744.8030.qmail@web14606.mail.yahoo.com>
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

stream stream wrote:
> hi there,
> 
> i began my search about security in mobile adhoc networks and i face 
> many problems.

You should perhaps first read a couple of papers or presentations
regarding MANET security. A good starting point might be the
http://lcawww.epfl.ch/buttyan/June12/
There you find the presentations of an working session on MANET security
at this year's Mobihoc.

Furthermore Feng Zhu keeps a quite ample bibliography list on papers
related to MANET security at
http://www.ccs.neu.edu/home/zhufeng/security_manet.html

> i would be very pleased if anybody answers me some of the 
> questions below:
> 
> - what are tha main risks?. is there solutions?

You find a lot of discussions on these issues in the ressources above.
There is no short answer (esp. to the second question).

> - can we use ip in ad hoc networks ?

This is not directly related to security. As most research projects
currently focus on creating IP MANETs, the answer is propably yes.

> - is there any  protocol for security (application like ssl or smime..)?

SSL or smime are application level protocols that can of course also be
used in MANETs. When talking about MANET security you propably think of
securing the routing function. There are a number of proposals like
ARIADNE, CORE and more.

> -waht are the protocols (not routing algorithms) ( niveau applicatif) in 
> ad hoc networks.

I can only guess that you ask what applications are supposed to run in
MANETs. This is again a large area ranging from military applications
and search&rescue to ordinary Internet applications like WWW.

> - can we use ipsec

In my oppinion, IPSEC doesn't address many of the MANET specific
security issues like DoS on the routing infrastructure or selfish nodes
not participating in the routing function. Furthermore protocols like
IKE are way to complex to be implemented in small devices and normal
PKIs are also not suitable in this context. So we propably need
something different (or at least augment IPsec significantly) to really
provide security for MANETs.

> - what are the protocols of communication ( address, paquets....)

You might want to read one of the books on MANETs, e.g.:
Perkins, Ad hoc networking, Addison Wesley 2000
Toh, Ad hoc mobile wireless networks, PH PTR 2001

> any help would be appreciated

Hope this helps.

Regards ... Frank

-- 
-----------------------------------------------------------------------
   Frank Kargl          Multimedia Computing, University of Ulm, Germany
   Mail:frank.kargl@informatik.uni-ulm.de http://www.uni-ulm.de/~fkargl/
-----------------------------------------------------------------------
     Use the SOURCE, Luke !  I feel a great disturbance in the SOURCE.
              But beware of the Microsoft side of the SOURCE !


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



From manet-admin@ietf.org  Tue Dec  3 08:59: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 IAA20323
	for <manet-archive@lists.ietf.org>; Tue, 3 Dec 2002 08: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 gB3DsCv09312;
	Tue, 3 Dec 2002 08:54: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 gB3Dpdv09106
	for <manet@optimus.ietf.org>; Tue, 3 Dec 2002 08:51:39 -0500
Received: from mail.rz.uni-ulm.de (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA19549
	for <manet@ietf.org>; Tue, 3 Dec 2002 08:48:47 -0500 (EST)
Received: from informatik.uni-ulm.de (shark.informatik.uni-ulm.de [134.60.70.12])
	by mail.rz.uni-ulm.de (8.12.6/8.12.6) with ESMTP id gB3DpZLb021361;
	Tue, 3 Dec 2002 14:51:36 +0100 (MET)
Message-ID: <3DECB6CC.3030003@informatik.uni-ulm.de>
Date: Tue, 03 Dec 2002 14:51:08 +0100
From: Frank Kargl <frank.kargl@informatik.uni-ulm.de>
Organization: University of Ulm
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.2) Gecko/20021126
X-Accept-Language: de-de, de, en-us, en
MIME-Version: 1.0
To: stream stream <mailadhoc@yahoo.es>
CC: manet@ietf.org
Subject: Re: [manet] security highlights in ad hoc networks
References: <20021130093744.8030.qmail@web14606.mail.yahoo.com>
In-Reply-To: <20021130093744.8030.qmail@web14606.mail.yahoo.com>
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

stream stream wrote:
> hi there,
> 
> i began my search about security in mobile adhoc networks and i face 
> many problems.

You should perhaps first read a couple of papers or presentations
regarding MANET security. A good starting point might be the
http://lcawww.epfl.ch/buttyan/June12/
There you find the presentations of an working session on MANET security
at this year's Mobihoc.

Furthermore Feng Zhu keeps a quite ample bibliography list on papers
related to MANET security at
http://www.ccs.neu.edu/home/zhufeng/security_manet.html

> i would be very pleased if anybody answers me some of the 
> questions below:
> 
> - what are tha main risks?. is there solutions?

You find a lot of discussions on these issues in the ressources above.
There is no short answer (esp. to the second question).

> - can we use ip in ad hoc networks ?

This is not directly related to security. As most research projects
currently focus on creating IP MANETs, the answer is propably yes.

> - is there any  protocol for security (application like ssl or smime..)?

SSL or smime are application level protocols that can of course also be
used in MANETs. When talking about MANET security you propably think of
securing the routing function. There are a number of proposals like
ARIADNE, CORE and more.

> -waht are the protocols (not routing algorithms) ( niveau applicatif) in 
> ad hoc networks.

I can only guess that you ask what applications are supposed to run in
MANETs. This is again a large area ranging from military applications
and search&rescue to ordinary Internet applications like WWW.

> - can we use ipsec

In my oppinion, IPSEC doesn't address many of the MANET specific
security issues like DoS on the routing infrastructure or selfish nodes
not participating in the routing function. Furthermore protocols like
IKE are way to complex to be implemented in small devices and normal
PKIs are also not suitable in this context. So we propably need
something different (or at least augment IPsec significantly) to really
provide security for MANETs.

> - what are the protocols of communication ( address, paquets....)

You might want to read one of the books on MANETs, e.g.:
Perkins, Ad hoc networking, Addison Wesley 2000
Toh, Ad hoc mobile wireless networks, PH PTR 2001

> any help would be appreciated

Hope this helps.

Regards ... Frank

-- 
-----------------------------------------------------------------------
   Frank Kargl          Multimedia Computing, University of Ulm, Germany
   Mail:frank.kargl@informatik.uni-ulm.de http://www.uni-ulm.de/~fkargl/
-----------------------------------------------------------------------
     Use the SOURCE, Luke !  I feel a great disturbance in the SOURCE.
              But beware of the Microsoft side of the SOURCE !


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


From mailnull@www1.ietf.org  Tue Dec  3 10:53:21 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 KAA28251
	for <manet-archive@odin.ietf.org>; Tue, 3 Dec 2002 10:53:21 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id gB3Fti320285
	for manet-archive@odin.ietf.org; Tue, 3 Dec 2002 10:55: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 gB3Fthv20282
	for <manet-web-archive@optimus.ietf.org>; Tue, 3 Dec 2002 10:55: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 KAA28186
	for <manet-web-archive@ietf.org>; Tue, 3 Dec 2002 10:52: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 gB3FlKv19702;
	Tue, 3 Dec 2002 10:47: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 gB3FiDv19542
	for <manet@optimus.ietf.org>; Tue, 3 Dec 2002 10:44:13 -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 KAA27321;
	Tue, 3 Dec 2002 10:41:19 -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 KAA27528;
	Tue, 3 Dec 2002 10:44:08 -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 M2002120310440809495
 ; Tue, 03 Dec 2002 10:44:08 -0500
Message-Id: <5.1.1.5.2.20021203104436.035787a0@pop.itd.nrl.navy.mil>
X-Sender: macker@pop.itd.nrl.navy.mil
X-Mailer: QUALCOMM Windows Eudora Version 5.1.1
Date: Tue, 03 Dec 2002 10:45:44 -0500
To: manet@ietf.org
From: Joe Macker <macker@itd.nrl.navy.mil>
Cc: minutes@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 gB3FiDv19543
Subject: [manet] Update to 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@flarion.com> 
              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 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 Dec  3 10:59: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 KAA28992
	for <manet-archive@lists.ietf.org>; Tue, 3 Dec 2002 10:59: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 gB3FlKv19702;
	Tue, 3 Dec 2002 10:47: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 gB3FiDv19542
	for <manet@optimus.ietf.org>; Tue, 3 Dec 2002 10:44:13 -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 KAA27321;
	Tue, 3 Dec 2002 10:41:19 -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 KAA27528;
	Tue, 3 Dec 2002 10:44:08 -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 M2002120310440809495
 ; Tue, 03 Dec 2002 10:44:08 -0500
Message-Id: <5.1.1.5.2.20021203104436.035787a0@pop.itd.nrl.navy.mil>
X-Sender: macker@pop.itd.nrl.navy.mil
X-Mailer: QUALCOMM Windows Eudora Version 5.1.1
Date: Tue, 03 Dec 2002 10:45:44 -0500
To: manet@ietf.org
From: Joe Macker <macker@itd.nrl.navy.mil>
Cc: minutes@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 gB3FiDv19543
Subject: [manet] Update to 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@flarion.com> 
              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 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  Tue Dec  3 15:14: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 PAA15145
	for <manet-archive@odin.ietf.org>; Tue, 3 Dec 2002 15:14:16 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id gB3KGeQ11500
	for manet-archive@odin.ietf.org; Tue, 3 Dec 2002 15:16: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 gB3KGev11497
	for <manet-web-archive@optimus.ietf.org>; Tue, 3 Dec 2002 15:16:40 -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 PAA15113
	for <manet-web-archive@ietf.org>; Tue, 3 Dec 2002 15:13: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 gB3K7Yv10871;
	Tue, 3 Dec 2002 15:07: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 gB3K4wv10117
	for <manet@optimus.ietf.org>; Tue, 3 Dec 2002 15:04:58 -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 PAA13830
	for <manet@ietf.org>; Tue, 3 Dec 2002 15:02:02 -0500 (EST)
Received: by planetajeans.com with Internet Mail Service (5.5.2656.59)
	id <YF21FYGN>; Tue, 3 Dec 2002 15:04:46 -0500
Message-ID: <748C6D0A58C0F94CA63C198B6674697AA5D229@ftmail.lab.flarion.com>
From: Scott Corson <Corson@flarion.com>
To: "'ogier@erg.sri.com'" <ogier@erg.sri.com>,
        "'manet@ietf.org'"
	 <manet@ietf.org>
Subject: RE: [manet] Suggestions for new problem statement
Date: Tue, 3 Dec 2002 15:04:48 -0500 
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2656.59)
Content-Type: text/plain
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>

Richard,

IMO this discussion is a rat hole for this group.

The ANS (Ad hoc Network Scaling) research list is being established (should
be available soon) for just this purpose and more.  It will be an open
research subgroup.  The work there will objectively evaluate all the issues
you raise and others, and will consider the performance of existing MANET
proposals as well as possible variants/crazy ideas ;-) for comparison.

I think there should be no notion of a *minimum* requirement for IETF MANET
WG scaling.  We should not overly concern ourselves about this issue in the
IETF.  Just build robust, stable protocols that work under a variety of
common situations, while we ascertain the boundary/scaling/stability
conditions where these protocols fall apart in the IRTF, to see
when/where/how/why/if additional work is required.  Frankly, the wide range
of possible traffic loadings and network dynamics can swamp all other
considerations, rendering specification of a minimum size quite pointless.
10 nodes or 250... either number can hold (or not), depending on a whole
host of assumptions.

I don't believe we should even list 100 nodes as a requirement... I think
network scale should be a non-goal in the IETF work.  Common sense
engineering should be able to produce reasonably efficient protocols without
needless overspecification.

-Scott


> I would like to offer some suggestions for the new problem 
> statement.  
> Joe presented a preliminary problem statement that said the protocol 
> should support up to 100 nodes, but I know this is up for discussion.
> 
> At the meeting in Atlanta, at least one person suggested 
> that we not limit ourselves to only 100 nodes since some or all
> of the proposed protocols can already support more than that,
> and I agree with this.  
> 
> I know that AODV, TBRPF, and OLSR can all support at least 250 nodes
> and probably more, using 802.11 with rate 2 Mbps.
> 
> I think the protocol should be as scalable and efficient as 
> possible without being "too complex", and without using
> hierarchical routing.  
> 
> It is generally agreed that the protocol should be extendable
> to a scalable protocol (e.g., using a hierarchical method such
> as landmark routing).
> HOWEVER, IF THE PROTOCOL CAN SUPPORT MORE NODES WITHOUT USING
> HIERARCHICAL ROUTING, THEN ITS HIERARCHICAL EXTENSION WILL
> SUPPORT MORE NODES.  (The same is true for other scalability
> techniques such as HSLS and FSR.)
> 
> Perhaps the problem statement can give 100 or 250 nodes as a 
> *minimum requirement*, and state that when alternative techniques are 
> available that are reasonably simple and well understood, preference 
> should be given to techniques that perform better, e.g. that:
> 
>   1. Support more nodes 
>   2. Support a higher level of mobility and dynamics
>   3. Have better delivery ratio and end-to-end delay
>   4. Provide shorter paths
>   5. Generate less overhead (or "total overhead")
>   6. Support lower bandwidth links 
> 
> We also need to be careful about stating the minimum requirements for
> mobility.  For example, the number of topology changes per second for 
> nodes traveling 20 mps according to the random waypoint model is much 
> greater in an urban environment than it is in an open field.
> 
> Richard 
> 
> _______________________________________________
> 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 Dec  3 15:19:47 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 PAA15541
	for <manet-archive@lists.ietf.org>; Tue, 3 Dec 2002 15:19: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 gB3K7Yv10871;
	Tue, 3 Dec 2002 15:07: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 gB3K4wv10117
	for <manet@optimus.ietf.org>; Tue, 3 Dec 2002 15:04:58 -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 PAA13830
	for <manet@ietf.org>; Tue, 3 Dec 2002 15:02:02 -0500 (EST)
Received: by planetajeans.com with Internet Mail Service (5.5.2656.59)
	id <YF21FYGN>; Tue, 3 Dec 2002 15:04:46 -0500
Message-ID: <748C6D0A58C0F94CA63C198B6674697AA5D229@ftmail.lab.flarion.com>
From: Scott Corson <Corson@flarion.com>
To: "'ogier@erg.sri.com'" <ogier@erg.sri.com>,
        "'manet@ietf.org'"
	 <manet@ietf.org>
Subject: RE: [manet] Suggestions for new problem statement
Date: Tue, 3 Dec 2002 15:04:48 -0500 
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2656.59)
Content-Type: text/plain
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>

Richard,

IMO this discussion is a rat hole for this group.

The ANS (Ad hoc Network Scaling) research list is being established (should
be available soon) for just this purpose and more.  It will be an open
research subgroup.  The work there will objectively evaluate all the issues
you raise and others, and will consider the performance of existing MANET
proposals as well as possible variants/crazy ideas ;-) for comparison.

I think there should be no notion of a *minimum* requirement for IETF MANET
WG scaling.  We should not overly concern ourselves about this issue in the
IETF.  Just build robust, stable protocols that work under a variety of
common situations, while we ascertain the boundary/scaling/stability
conditions where these protocols fall apart in the IRTF, to see
when/where/how/why/if additional work is required.  Frankly, the wide range
of possible traffic loadings and network dynamics can swamp all other
considerations, rendering specification of a minimum size quite pointless.
10 nodes or 250... either number can hold (or not), depending on a whole
host of assumptions.

I don't believe we should even list 100 nodes as a requirement... I think
network scale should be a non-goal in the IETF work.  Common sense
engineering should be able to produce reasonably efficient protocols without
needless overspecification.

-Scott


> I would like to offer some suggestions for the new problem 
> statement.  
> Joe presented a preliminary problem statement that said the protocol 
> should support up to 100 nodes, but I know this is up for discussion.
> 
> At the meeting in Atlanta, at least one person suggested 
> that we not limit ourselves to only 100 nodes since some or all
> of the proposed protocols can already support more than that,
> and I agree with this.  
> 
> I know that AODV, TBRPF, and OLSR can all support at least 250 nodes
> and probably more, using 802.11 with rate 2 Mbps.
> 
> I think the protocol should be as scalable and efficient as 
> possible without being "too complex", and without using
> hierarchical routing.  
> 
> It is generally agreed that the protocol should be extendable
> to a scalable protocol (e.g., using a hierarchical method such
> as landmark routing).
> HOWEVER, IF THE PROTOCOL CAN SUPPORT MORE NODES WITHOUT USING
> HIERARCHICAL ROUTING, THEN ITS HIERARCHICAL EXTENSION WILL
> SUPPORT MORE NODES.  (The same is true for other scalability
> techniques such as HSLS and FSR.)
> 
> Perhaps the problem statement can give 100 or 250 nodes as a 
> *minimum requirement*, and state that when alternative techniques are 
> available that are reasonably simple and well understood, preference 
> should be given to techniques that perform better, e.g. that:
> 
>   1. Support more nodes 
>   2. Support a higher level of mobility and dynamics
>   3. Have better delivery ratio and end-to-end delay
>   4. Provide shorter paths
>   5. Generate less overhead (or "total overhead")
>   6. Support lower bandwidth links 
> 
> We also need to be careful about stating the minimum requirements for
> mobility.  For example, the number of topology changes per second for 
> nodes traveling 20 mps according to the random waypoint model is much 
> greater in an urban environment than it is in an open field.
> 
> Richard 
> 
> _______________________________________________
> 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 Dec  3 16:53: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 QAA20667
	for <manet-archive@odin.ietf.org>; Tue, 3 Dec 2002 16:53:32 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id gB3LtwN18421
	for manet-archive@odin.ietf.org; Tue, 3 Dec 2002 16:55: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 gB3Ltvv18418
	for <manet-web-archive@optimus.ietf.org>; Tue, 3 Dec 2002 16: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 QAA20643
	for <manet-web-archive@ietf.org>; Tue, 3 Dec 2002 16:53: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 gB3Llmv17973;
	Tue, 3 Dec 2002 16:47: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 gB3La8v16963
	for <manet@optimus.ietf.org>; Tue, 3 Dec 2002 16:36:08 -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 QAA19860
	for <manet@ietf.org>; Tue, 3 Dec 2002 16:33:11 -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 QAA19202
	for <manet@ietf.org>; Tue, 3 Dec 2002 16:36:00 -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 M2002120316360009219
 for <manet@ietf.org>; Tue, 03 Dec 2002 16:36:00 -0500
Message-Id: <5.1.1.5.2.20021203154423.014c5390@pop.itd.nrl.navy.mil>
X-Sender: macker@pop.itd.nrl.navy.mil
X-Mailer: QUALCOMM Windows Eudora Version 5.1.1
Date: Tue, 03 Dec 2002 16:37:33 -0500
To: "'manet@ietf.org'" <manet@ietf.org>
From: Joe Macker <macker@itd.nrl.navy.mil>
Subject: RE: [manet] Suggestions for new problem statement
In-Reply-To: <748C6D0A58C0F94CA63C198B6674697AA5D229@ftmail.lab.flarion.
 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 03:04 PM 12/3/2002 -0500, Scott Corson wrote:
>Richard,
>
>IMO this discussion is a rat hole for this group.
>
>The ANS (Ad hoc Network Scaling) research list is being established (should
>be available soon) for just this purpose and more.  It will be an open
>research subgroup.  The work there will objectively evaluate all the issues
>you raise and others, and will consider the performance of existing MANET
>proposals as well as possible variants/crazy ideas ;-) for comparison.
>
>I think there should be no notion of a *minimum* requirement for IETF MANET
>WG scaling.  We should not overly concern ourselves about this issue in the
>IETF.  Just build robust, stable protocols that work under a variety of
>common situations, while we ascertain the boundary/scaling/stability
>conditions where these protocols fall apart in the IRTF, to see
>when/where/how/why/if additional work is required.  Frankly, the wide range
>of possible traffic loadings and network dynamics can swamp all other
>considerations, rendering specification of a minimum size quite pointless.
>10 nodes or 250... either number can hold (or not), depending on a whole
>host of assumptions.

Scott I tend to agree.  Heavily quantifying minimum size or means little without spelling out a whole host of other metrics and scenario specific related issues (which defines a RATHOLE argument space for generality).... Mea culpa for throwing such numbers up in the strawman.  Speed is also not a generic metric for mobility because it doesn't take into account the variables relating to the scale of relative motion across a wide range of scenarios.  Also, in my opinion MANET technology is not just about handling potential relative motion but also about simple wireless link dynamics and time varying interface behavior.

To reiterate the proposal in Atlanta, we should focus in on simple, practical approaches in the IETF MANET realm that work for a variety of more commonly envisioned scenarios (and I believe we have some good engineering lessons learned finally on the table to build of off..) The ANS will serve to debate the larger scale analysis, performance tweaks, and design choices.  Within the IETF scope, after our initial EXPERIMENTAL targets, I would be more interested in achieving the goal of simple operational robustness and flexibility for basic cases at the engineering level.  Some may say we have that already, but what we don't have is consensus on a common WG engineered approach.  In addition, if we can design a degree of extensibility into any adopted core framework(s) we are in reasonable good shape for the future enhancements that will certainly come along.

Let's hear from more of you on this...
  

>I don't believe we should even list 100 nodes as a requirement... I think
>network scale should be a non-goal in the IETF work.  Common sense
>engineering should be able to produce reasonably efficient protocols without
>needless overspecification.
>
>-Scott
>
>
>> I would like to offer some suggestions for the new problem 
>> statement.  
>> Joe presented a preliminary problem statement that said the protocol 
>> should support up to 100 nodes, but I know this is up for discussion.
>> 
>> At the meeting in Atlanta, at least one person suggested 
>> that we not limit ourselves to only 100 nodes since some or all
>> of the proposed protocols can already support more than that,
>> and I agree with this.  
>> 
>> I know that AODV, TBRPF, and OLSR can all support at least 250 nodes
>> and probably more, using 802.11 with rate 2 Mbps.
>> 
>> I think the protocol should be as scalable and efficient as 
>> possible without being "too complex", and without using
>> hierarchical routing.  
>> 
>> It is generally agreed that the protocol should be extendable
>> to a scalable protocol (e.g., using a hierarchical method such
>> as landmark routing).
>> HOWEVER, IF THE PROTOCOL CAN SUPPORT MORE NODES WITHOUT USING
>> HIERARCHICAL ROUTING, THEN ITS HIERARCHICAL EXTENSION WILL
>> SUPPORT MORE NODES.  (The same is true for other scalability
>> techniques such as HSLS and FSR.)
>> 
>> Perhaps the problem statement can give 100 or 250 nodes as a 
>> *minimum requirement*, and state that when alternative techniques are 
>> available that are reasonably simple and well understood, preference 
>> should be given to techniques that perform better, e.g. that:
>> 
>>   1. Support more nodes 
>>   2. Support a higher level of mobility and dynamics
>>   3. Have better delivery ratio and end-to-end delay
>>   4. Provide shorter paths
>>   5. Generate less overhead (or "total overhead")
>>   6. Support lower bandwidth links 
>> 
>> We also need to be careful about stating the minimum requirements for
>> mobility.  For example, the number of topology changes per second for 
>> nodes traveling 20 mps according to the random waypoint model is much 
>> greater in an urban environment than it is in an open field.
>> 
>> Richard 
>> 
>> _______________________________________________
>> 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 Dec  3 16:53: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 QAA20693
	for <manet-archive@lists.ietf.org>; Tue, 3 Dec 2002 16:53: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 gB3Llmv17973;
	Tue, 3 Dec 2002 16:47: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 gB3La8v16963
	for <manet@optimus.ietf.org>; Tue, 3 Dec 2002 16:36:08 -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 QAA19860
	for <manet@ietf.org>; Tue, 3 Dec 2002 16:33:11 -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 QAA19202
	for <manet@ietf.org>; Tue, 3 Dec 2002 16:36:00 -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 M2002120316360009219
 for <manet@ietf.org>; Tue, 03 Dec 2002 16:36:00 -0500
Message-Id: <5.1.1.5.2.20021203154423.014c5390@pop.itd.nrl.navy.mil>
X-Sender: macker@pop.itd.nrl.navy.mil
X-Mailer: QUALCOMM Windows Eudora Version 5.1.1
Date: Tue, 03 Dec 2002 16:37:33 -0500
To: "'manet@ietf.org'" <manet@ietf.org>
From: Joe Macker <macker@itd.nrl.navy.mil>
Subject: RE: [manet] Suggestions for new problem statement
In-Reply-To: <748C6D0A58C0F94CA63C198B6674697AA5D229@ftmail.lab.flarion.
 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 03:04 PM 12/3/2002 -0500, Scott Corson wrote:
>Richard,
>
>IMO this discussion is a rat hole for this group.
>
>The ANS (Ad hoc Network Scaling) research list is being established (should
>be available soon) for just this purpose and more.  It will be an open
>research subgroup.  The work there will objectively evaluate all the issues
>you raise and others, and will consider the performance of existing MANET
>proposals as well as possible variants/crazy ideas ;-) for comparison.
>
>I think there should be no notion of a *minimum* requirement for IETF MANET
>WG scaling.  We should not overly concern ourselves about this issue in the
>IETF.  Just build robust, stable protocols that work under a variety of
>common situations, while we ascertain the boundary/scaling/stability
>conditions where these protocols fall apart in the IRTF, to see
>when/where/how/why/if additional work is required.  Frankly, the wide range
>of possible traffic loadings and network dynamics can swamp all other
>considerations, rendering specification of a minimum size quite pointless.
>10 nodes or 250... either number can hold (or not), depending on a whole
>host of assumptions.

Scott I tend to agree.  Heavily quantifying minimum size or means little without spelling out a whole host of other metrics and scenario specific related issues (which defines a RATHOLE argument space for generality).... Mea culpa for throwing such numbers up in the strawman.  Speed is also not a generic metric for mobility because it doesn't take into account the variables relating to the scale of relative motion across a wide range of scenarios.  Also, in my opinion MANET technology is not just about handling potential relative motion but also about simple wireless link dynamics and time varying interface behavior.

To reiterate the proposal in Atlanta, we should focus in on simple, practical approaches in the IETF MANET realm that work for a variety of more commonly envisioned scenarios (and I believe we have some good engineering lessons learned finally on the table to build of off..) The ANS will serve to debate the larger scale analysis, performance tweaks, and design choices.  Within the IETF scope, after our initial EXPERIMENTAL targets, I would be more interested in achieving the goal of simple operational robustness and flexibility for basic cases at the engineering level.  Some may say we have that already, but what we don't have is consensus on a common WG engineered approach.  In addition, if we can design a degree of extensibility into any adopted core framework(s) we are in reasonable good shape for the future enhancements that will certainly come along.

Let's hear from more of you on this...
  

>I don't believe we should even list 100 nodes as a requirement... I think
>network scale should be a non-goal in the IETF work.  Common sense
>engineering should be able to produce reasonably efficient protocols without
>needless overspecification.
>
>-Scott
>
>
>> I would like to offer some suggestions for the new problem 
>> statement.  
>> Joe presented a preliminary problem statement that said the protocol 
>> should support up to 100 nodes, but I know this is up for discussion.
>> 
>> At the meeting in Atlanta, at least one person suggested 
>> that we not limit ourselves to only 100 nodes since some or all
>> of the proposed protocols can already support more than that,
>> and I agree with this.  
>> 
>> I know that AODV, TBRPF, and OLSR can all support at least 250 nodes
>> and probably more, using 802.11 with rate 2 Mbps.
>> 
>> I think the protocol should be as scalable and efficient as 
>> possible without being "too complex", and without using
>> hierarchical routing.  
>> 
>> It is generally agreed that the protocol should be extendable
>> to a scalable protocol (e.g., using a hierarchical method such
>> as landmark routing).
>> HOWEVER, IF THE PROTOCOL CAN SUPPORT MORE NODES WITHOUT USING
>> HIERARCHICAL ROUTING, THEN ITS HIERARCHICAL EXTENSION WILL
>> SUPPORT MORE NODES.  (The same is true for other scalability
>> techniques such as HSLS and FSR.)
>> 
>> Perhaps the problem statement can give 100 or 250 nodes as a 
>> *minimum requirement*, and state that when alternative techniques are 
>> available that are reasonably simple and well understood, preference 
>> should be given to techniques that perform better, e.g. that:
>> 
>>   1. Support more nodes 
>>   2. Support a higher level of mobility and dynamics
>>   3. Have better delivery ratio and end-to-end delay
>>   4. Provide shorter paths
>>   5. Generate less overhead (or "total overhead")
>>   6. Support lower bandwidth links 
>> 
>> We also need to be careful about stating the minimum requirements for
>> mobility.  For example, the number of topology changes per second for 
>> nodes traveling 20 mps according to the random waypoint model is much 
>> greater in an urban environment than it is in an open field.
>> 
>> Richard 
>> 
>> _______________________________________________
>> 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 Dec  3 19:08: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 TAA26247
	for <manet-archive@odin.ietf.org>; Tue, 3 Dec 2002 19:08:49 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id gB40BEK28427
	for manet-archive@odin.ietf.org; Tue, 3 Dec 2002 19:11: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 gB40BEv28424
	for <manet-web-archive@optimus.ietf.org>; Tue, 3 Dec 2002 19:11: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 TAA26224
	for <manet-web-archive@ietf.org>; Tue, 3 Dec 2002 19:08: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 gB3Nxsv27155;
	Tue, 3 Dec 2002 18:59: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 gB3Nv8v27064
	for <manet@optimus.ietf.org>; Tue, 3 Dec 2002 18:57:08 -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 SAA25706
	for <manet@ietf.org>; Tue, 3 Dec 2002 18:54:12 -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 gB3Nuua138080;
	Tue, 3 Dec 2002 18:56:56 -0500 (EST)
Received: from tom ([198.70.231.113])
	by steiner.cc.vt.edu (Mirapoint Messaging Server MOS 3.2.1-GA)
	with ESMTP id ATN82460 (AUTH talin);
	Tue, 3 Dec 2002 18:56:55 -0500 (EST)
Message-ID: <003501c29b27$72707e40$643f640a@tom>
From: "Tao Lin" <taolin@vt.edu>
To: "Joe Macker" <macker@itd.nrl.navy.mil>, <manet@ietf.org>
References: <5.1.1.5.2.20021203154423.014c5390@pop.itd.nrl.navy.mil>
Subject: Re: [manet] Suggestions for new problem statement
Date: Tue, 3 Dec 2002 18:55:23 -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.2800.1106
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1106
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

We developed a framework for the MANET routing protocols.  The draft of this
paper is available at http://io.irean.vt.edu/~tlin/.

"A framework for mobile ad hoc routing protocols" T. Lin, S. F. Midkiff, and
J. S. Park, accepted by IEEE WCNC 2003.

This framework can characterize the MANET routing protocols, including
DSR/AODV/TBRPF/OLSR and other drafts proposed in the IETF MANET web site.
This framework points out the multi-objective optimization problems (or
trade off problems) in the design/improvement of these protocols.
Therefore, I hope it can be helpful for the future study of MANET routing
protocols.

 Best,

      Tao Lin
  ECE Department
  Virginia Tech.
  USA


----- Original Message -----
From: "Joe Macker" <macker@itd.nrl.navy.mil>
To: <manet@ietf.org>
Sent: Tuesday, December 03, 2002 4:37 PM
Subject: RE: [manet] Suggestions for new problem statement


> Scott I tend to agree.  Heavily quantifying minimum size or means little
without spelling out a whole host of other metrics and scenario specific
related issues (which defines a RATHOLE argument space for generality)....
Mea culpa for throwing such numbers up in the strawman.  Speed is also not a
generic metric for mobility because it doesn't take into account the
variables relating to the scale of relative motion across a wide range of
scenarios.  Also, in my opinion MANET technology is not just about handling
potential relative motion but also about simple wireless link dynamics and
time varying interface behavior.
>
> To reiterate the proposal in Atlanta, we should focus in on simple,
practical approaches in the IETF MANET realm that work for a variety of more
commonly envisioned scenarios (and I believe we have some good engineering
lessons learned finally on the table to build of off..) The ANS will serve
to debate the larger scale analysis, performance tweaks, and design choices.
Within the IETF scope, after our initial EXPERIMENTAL targets, I would be
more interested in achieving the goal of simple operational robustness and
flexibility for basic cases at the engineering level.  Some may say we have
that already, but what we don't have is consensus on a common WG engineered
approach.  In addition, if we can design a degree of extensibility into any
adopted core framework(s) we are in reasonable good shape for the future
enhancements that will certainly come along.
>
> Let's hear from more of you on this...

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



From manet-admin@ietf.org  Tue Dec  3 19:12: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 TAA26373
	for <manet-archive@lists.ietf.org>; Tue, 3 Dec 2002 19:12: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 gB3Nxsv27155;
	Tue, 3 Dec 2002 18:59: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 gB3Nv8v27064
	for <manet@optimus.ietf.org>; Tue, 3 Dec 2002 18:57:08 -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 SAA25706
	for <manet@ietf.org>; Tue, 3 Dec 2002 18:54:12 -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 gB3Nuua138080;
	Tue, 3 Dec 2002 18:56:56 -0500 (EST)
Received: from tom ([198.70.231.113])
	by steiner.cc.vt.edu (Mirapoint Messaging Server MOS 3.2.1-GA)
	with ESMTP id ATN82460 (AUTH talin);
	Tue, 3 Dec 2002 18:56:55 -0500 (EST)
Message-ID: <003501c29b27$72707e40$643f640a@tom>
From: "Tao Lin" <taolin@vt.edu>
To: "Joe Macker" <macker@itd.nrl.navy.mil>, <manet@ietf.org>
References: <5.1.1.5.2.20021203154423.014c5390@pop.itd.nrl.navy.mil>
Subject: Re: [manet] Suggestions for new problem statement
Date: Tue, 3 Dec 2002 18:55:23 -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.2800.1106
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1106
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

We developed a framework for the MANET routing protocols.  The draft of this
paper is available at http://io.irean.vt.edu/~tlin/.

"A framework for mobile ad hoc routing protocols" T. Lin, S. F. Midkiff, and
J. S. Park, accepted by IEEE WCNC 2003.

This framework can characterize the MANET routing protocols, including
DSR/AODV/TBRPF/OLSR and other drafts proposed in the IETF MANET web site.
This framework points out the multi-objective optimization problems (or
trade off problems) in the design/improvement of these protocols.
Therefore, I hope it can be helpful for the future study of MANET routing
protocols.

 Best,

      Tao Lin
  ECE Department
  Virginia Tech.
  USA


----- Original Message -----
From: "Joe Macker" <macker@itd.nrl.navy.mil>
To: <manet@ietf.org>
Sent: Tuesday, December 03, 2002 4:37 PM
Subject: RE: [manet] Suggestions for new problem statement


> Scott I tend to agree.  Heavily quantifying minimum size or means little
without spelling out a whole host of other metrics and scenario specific
related issues (which defines a RATHOLE argument space for generality)....
Mea culpa for throwing such numbers up in the strawman.  Speed is also not a
generic metric for mobility because it doesn't take into account the
variables relating to the scale of relative motion across a wide range of
scenarios.  Also, in my opinion MANET technology is not just about handling
potential relative motion but also about simple wireless link dynamics and
time varying interface behavior.
>
> To reiterate the proposal in Atlanta, we should focus in on simple,
practical approaches in the IETF MANET realm that work for a variety of more
commonly envisioned scenarios (and I believe we have some good engineering
lessons learned finally on the table to build of off..) The ANS will serve
to debate the larger scale analysis, performance tweaks, and design choices.
Within the IETF scope, after our initial EXPERIMENTAL targets, I would be
more interested in achieving the goal of simple operational robustness and
flexibility for basic cases at the engineering level.  Some may say we have
that already, but what we don't have is consensus on a common WG engineered
approach.  In addition, if we can design a degree of extensibility into any
adopted core framework(s) we are in reasonable good shape for the future
enhancements that will certainly come along.
>
> Let's hear from more of you on this...

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


From manet-admin@ietf.org  Tue Dec  3 20:15: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 UAA28407
	for <manet-archive@lists.ietf.org>; Tue, 3 Dec 2002 20:15:28 -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 gB41AQv32520;
	Tue, 3 Dec 2002 20:10: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 gB418Cv32433
	for <manet@optimus.ietf.org>; Tue, 3 Dec 2002 20:08:12 -0500
Received: from web40709.mail.yahoo.com (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id UAA28162
	for <manet@ietf.org>; Tue, 3 Dec 2002 20:05:15 -0500 (EST)
Message-ID: <20021204010804.97535.qmail@web40709.mail.yahoo.com>
Received: from [129.10.115.160] by web40709.mail.yahoo.com via HTTP; Tue, 03 Dec 2002 17:08:04 PST
Date: Tue, 3 Dec 2002 17:08:04 -0800 (PST)
From: feng zhu <zf_manet@yahoo.com>
Subject: Re: [manet] security highlights in ad hoc networks
To: stream stream <mailadhoc@yahoo.es>
Cc: manet@ietf.org
In-Reply-To: <3DECB6CC.3030003@informatik.uni-ulm.de>
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>

--- Frank Kargl <frank.kargl@informatik.uni-ulm.de>
wrote:
> stream stream wrote:
> > hi there,
> > 
> > i began my search about security in mobile adhoc
> networks and i face 
> > many problems.
> 
> You should perhaps first read a couple of papers or
> presentations
> regarding MANET security. A good starting point
> might be the
> http://lcawww.epfl.ch/buttyan/June12/

I think it is easier to use the following link
http://lcawww.epfl.ch/buttyan/June12/index.html
instead of the above one. A very small point. :-)

> There you find the presentations of an working
> session on MANET security
> at this year's Mobihoc.
> 
> Furthermore Feng Zhu keeps a quite ample
> bibliography list on papers
> related to MANET security at
>
http://www.ccs.neu.edu/home/zhufeng/security_manet.html

I plan to update it soon. I hope I can make it more
helpful. Any comment will be appreciated.

Best,
Feng



=====
==============================
ZHU, Feng
zf_manet@yahoo.com
http://www.ccs.neu.edu/home/zhufeng/security_manet.html

__________________________________________________
Do you Yahoo!?
Yahoo! Mail Plus - Powerful. Affordable. Sign up now.
http://mailplus.yahoo.com
_______________________________________________
manet mailing list
manet@ietf.org
https://www1.ietf.org/mailman/listinfo/manet


From mailnull@www1.ietf.org  Tue Dec  3 20:42: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 UAA29122
	for <manet-archive@odin.ietf.org>; Tue, 3 Dec 2002 20:42:07 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id gB41iYW01899
	for manet-archive@odin.ietf.org; Tue, 3 Dec 2002 20:44: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 gB41iYv01896
	for <manet-web-archive@optimus.ietf.org>; Tue, 3 Dec 2002 20:44: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 UAA29107
	for <manet-web-archive@ietf.org>; Tue, 3 Dec 2002 20:41: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 gB41AQv32520;
	Tue, 3 Dec 2002 20:10: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 gB418Cv32433
	for <manet@optimus.ietf.org>; Tue, 3 Dec 2002 20:08:12 -0500
Received: from web40709.mail.yahoo.com (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id UAA28162
	for <manet@ietf.org>; Tue, 3 Dec 2002 20:05:15 -0500 (EST)
Message-ID: <20021204010804.97535.qmail@web40709.mail.yahoo.com>
Received: from [129.10.115.160] by web40709.mail.yahoo.com via HTTP; Tue, 03 Dec 2002 17:08:04 PST
Date: Tue, 3 Dec 2002 17:08:04 -0800 (PST)
From: feng zhu <zf_manet@yahoo.com>
Subject: Re: [manet] security highlights in ad hoc networks
To: stream stream <mailadhoc@yahoo.es>
Cc: manet@ietf.org
In-Reply-To: <3DECB6CC.3030003@informatik.uni-ulm.de>
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>

--- Frank Kargl <frank.kargl@informatik.uni-ulm.de>
wrote:
> stream stream wrote:
> > hi there,
> > 
> > i began my search about security in mobile adhoc
> networks and i face 
> > many problems.
> 
> You should perhaps first read a couple of papers or
> presentations
> regarding MANET security. A good starting point
> might be the
> http://lcawww.epfl.ch/buttyan/June12/

I think it is easier to use the following link
http://lcawww.epfl.ch/buttyan/June12/index.html
instead of the above one. A very small point. :-)

> There you find the presentations of an working
> session on MANET security
> at this year's Mobihoc.
> 
> Furthermore Feng Zhu keeps a quite ample
> bibliography list on papers
> related to MANET security at
>
http://www.ccs.neu.edu/home/zhufeng/security_manet.html

I plan to update it soon. I hope I can make it more
helpful. Any comment will be appreciated.

Best,
Feng



=====
==============================
ZHU, Feng
zf_manet@yahoo.com
http://www.ccs.neu.edu/home/zhufeng/security_manet.html

__________________________________________________
Do you Yahoo!?
Yahoo! Mail Plus - Powerful. Affordable. Sign up now.
http://mailplus.yahoo.com
_______________________________________________
manet mailing list
manet@ietf.org
https://www1.ietf.org/mailman/listinfo/manet



From manet-admin@ietf.org  Wed Dec  4 07:06: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 HAA06978
	for <manet-archive@lists.ietf.org>; Wed, 4 Dec 2002 07:06: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 gB4C0xv11710;
	Wed, 4 Dec 2002 07:00: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 gB4BwJv11603
	for <manet@optimus.ietf.org>; Wed, 4 Dec 2002 06:58:19 -0500
Received: from msweeper.seri.co.uk (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id GAA06772
	for <manet@ietf.org>; Wed, 4 Dec 2002 06:55:27 -0500 (EST)
Received: from ex1.seri.co.uk (ex1.seri.co.uk) by msweeper.seri.co.uk
 (Content Technologies SMTPRS 4.2.10) with ESMTP id <T5ef592df15c28512ac750@msweeper.seri.co.uk> for <manet@ietf.org>;
 Wed, 4 Dec 2002 10:49:29 +0000
X-MimeOLE: Produced By Microsoft Exchange V6.0.5762.3
content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="----_=_NextPart_001_01C29B83.802504AF"
Subject: RE: [manet] is info on link capacity available to a manet protocol
Date: Wed, 4 Dec 2002 10:54:21 -0000
Message-ID: <341710540F08E34498A057DEE04DAAD73CBAA6@ex1.seri.co.uk>
Thread-Topic: [manet] is info on link capacity available to a manet protocol
Thread-Index: AcKa7hLhVKzZF/cYShuRe5KPwuivSgAkQPnw
From: "Martin Layley" <mlayley@seri.co.uk>
To: <manet@ietf.org>
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_01C29B83.802504AF
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

Battery life/performance currently fits in the ISO model at layer 7 (applic=
ation).  Historically, because most network components have been powered by=
 mains supplies, (often with UPS and generator backup), lifetime of power h=
as had nothing to do with communication.  The big systems will run a power =
monitoring application which will update routing tables, DNS servers etc of=
 other machines, before the computer is shut down.  With the growth of smal=
l, battery powered devices, this is effectively a new problem.
=20
I don't know the 802.11 layer 2, but I am very familiar with Bluetooth (BT)=
, having used chips from 5 different silicon vendors.  Most of these device=
s don't even have the ability to measure the battery voltage.  Battery life=
 estimation requires an intelligent charger with the ability to measure the=
 battery capacity and report it.  To read the battery charger, a BT device =
needs an I2C or SPI bus.  Most devices do have these, for reading external =
E2PROMs.  Some cannot extend this use, others allow the user to write a C p=
rogram to bit-bash the I/O pins.  The BT spec gives a minimal set of functi=
ons and allows the silicon vendor to provide extra manufacturer specific co=
mmands. The system designer can then create an application which monitors t=
he system health.  What is done with this information is then outside the B=
T spec.
=20
Laptops & PDAs may have the ability to guess their remaining battery life. =
 This will be part of the operating system & will be present regardless of =
networking components.  This information may be able to be read remotely.  =
If it is available, a reading application will be required (such as IE, net=
scape, mosaic).  This again is layer 7.
=20
=20
=20
I agree that altering network routing to avoid battery powered devices with=
 marginal capacity is extremely desirable.  To achieve this, you will need =
to look at using a system management protocol.  I am not very familiar with=
 it, but SMTP may provide you with the desired features.
=20
=20
        Martin

-----Original Message-----
From: Jigar Doshi [mailto:jigarnetmeet@hotmail.com]
Sent: 03 December 2002 11:19
To: manet@ietf.org
Subject: [manet] is info on link capacity available to a manet protocol



Hello,

Does the network layer report information such as link capacity ( i.e bandw=
idth ) and/or expected remaining battery life . We are currently developing=
 a protocol which uses this information to calculate optimum paths .A way o=
ut of the bandwidth calculation would be indirectly measuring the performan=
ce of the link by sending packets across. Is there a more efficient way? Ca=
n it be assumed tht such information is available , while designing the pro=
tocol like the conventional protocols.

Jigar Doshi & K Prahlad




  _____ =20

Tired of spam? Get advanced junk mail  <http://g.msn.com/8HMSEN/2017> prote=
ction with MSN 8. _______________________________________________ manet mai=
ling list manet@ietf.org https://www1.ietf.org/mailman/listinfo/manet=20



The mail message has been scanned by MAILsweeper
for content analysis.


------_=_NextPart_001_01C29B83.802504AF
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=3D"Content-Type" CONTENT=3D"text/html; charset=3Diso-8859-=
1">


<META content=3D"MSHTML 6.00.2600.0" name=3DGENERATOR></HEAD>
<BODY>
<DIV><SPAN class=3D509462210-04122002><FONT face=3DArial color=3D#0000ff=20
size=3D2>Battery life/performance currently fits in the ISO model at layer =
7=20
(application).&nbsp; Historically, because most network components have bee=
n=20
powered by mains supplies, (often with UPS and generator backup), lifetime =
of=20
power has had nothing to do with communication.&nbsp; The big systems will =
run a=20
power monitoring application which will update routing tables, DNS servers =
etc=20
of other machines, before the computer is shut down.&nbsp; With the growth =
of=20
small, battery powered devices, this is effectively a new=20
problem.</FONT></SPAN></DIV>
<DIV><SPAN class=3D509462210-04122002><FONT face=3DArial color=3D#0000ff=20
size=3D2></FONT></SPAN>&nbsp;</DIV>
<DIV><SPAN class=3D509462210-04122002><FONT face=3DArial color=3D#0000ff si=
ze=3D2>I=20
don't know the 802.11 layer 2, but I am very familiar with Bluetooth (BT),=
 having used chips from 5 different silicon vendors.&nbsp; Most of these de=
vices=20
don't even have the ability to measure the battery voltage.&nbsp; Battery l=
ife=20
estimation requires an intelligent charger with the ability to measure the=
 battery capacity and report it.&nbsp; To read the battery charger, a BT de=
vice=20
needs an I2C or SPI bus.&nbsp; Most devices do have these, for reading exte=
rnal=20
E2PROMs.&nbsp; Some cannot extend this use, others allow the user to write =
a C=20
program to bit-bash the I/O pins.&nbsp; The&nbsp;BT spec gives a minimal se=
t of=20
functions and allows the silicon vendor to provide extra manufacturer speci=
fic=20
commands.&nbsp;The system designer can then create an application which mon=
itors=20
the system health.&nbsp; What is done with this information is then outside=
 the=20
BT spec.</FONT></SPAN></DIV>
<DIV><SPAN class=3D509462210-04122002></SPAN>&nbsp;</DIV>
<DIV><SPAN class=3D509462210-04122002><FONT face=3DArial color=3D#0000ff=20
size=3D2>Laptops &amp; PDAs may have the ability to guess their remaining b=
attery=20
life.&nbsp; This will be part of the operating system &amp; will be present=
 regardless of networking components.&nbsp; This information may be able to=
 be=20
read remotely.&nbsp; If it is available, a reading application will be requ=
ired=20
(such as IE, netscape, mosaic).&nbsp; This again is layer 7.</FONT></SPAN><=
/DIV>
<DIV><SPAN class=3D509462210-04122002><FONT face=3DArial color=3D#0000ff=20
size=3D2></FONT></SPAN>&nbsp;</DIV>
<DIV><SPAN class=3D509462210-04122002><FONT face=3DArial color=3D#0000ff=20
size=3D2></FONT></SPAN>&nbsp;</DIV>
<DIV><SPAN class=3D509462210-04122002><FONT face=3DArial color=3D#0000ff=20
size=3D2></FONT></SPAN>&nbsp;</DIV>
<DIV><SPAN class=3D509462210-04122002><FONT face=3DArial color=3D#0000ff si=
ze=3D2>I=20
agree that altering network routing to avoid battery powered devices with=
 marginal capacity is extremely desirable.&nbsp; To achieve this, you will =
need=20
to look at using a system management protocol.&nbsp; I am not very familiar=
 with=20
it, but SMTP may provide you with the desired features.</FONT></SPAN></DIV>
<DIV><SPAN class=3D509462210-04122002><FONT face=3DArial color=3D#0000ff=20
size=3D2></FONT></SPAN>&nbsp;</DIV>
<DIV><SPAN class=3D509462210-04122002><FONT face=3DArial color=3D#0000ff=20
size=3D2></FONT></SPAN>&nbsp;</DIV>
<DIV><SPAN class=3D509462210-04122002>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;=20
<FONT face=3DArial color=3D#0000ff size=3D2>Martin</FONT></SPAN></DIV>
<BLOCKQUOTE>
  <DIV class=3DOutlookMessageHeader dir=3Dltr align=3Dleft><FONT face=3DTah=
oma=20
  size=3D2>-----Original Message-----<BR><B>From:</B> Jigar Doshi=20
  [mailto:jigarnetmeet@hotmail.com]<BR><B>Sent:</B> 03 December 2002=20
  11:19<BR><B>To:</B> manet@ietf.org<BR><B>Subject:</B> [manet] is info on =
link=20
  capacity available to a manet protocol<BR><BR></FONT></DIV>
  <DIV>
  <DIV>
  <P>Hello,<BR><BR>Does the network layer report information such as link=
   capacity ( i.e bandwidth ) and/or expected remaining battery life . We a=
re=20
  currently developing a protocol which uses this information to calculate=
   optimum paths .A way out of the bandwidth calculation would be indirectl=
y=20
  measuring the performance of the link by sending packets across. Is there=
 a=20
  more efficient way? Can it be assumed tht such information is available ,=
   while designing the protocol like the conventional protocols.</P>
  <P>Jigar Doshi&nbsp;&amp; K Prahlad<BR><BR></P></DIV></DIV><BR clear=3Dal=
l>
  <HR>
  Tired of spam? Get <A href=3D"http://g.msn.com/8HMSEN/2017">advanced junk=
 mail=20
  protection</A> with MSN 8. ______________________________________________=
_=20
  manet mailing list manet@ietf.org https://www1.ietf.org/mailman/listinfo/=
manet=20
</BLOCKQUOTE><CODE><FONT SIZE=3D3><BR>
<BR>
The mail message has been scanned by MAILsweeper<BR>
for content analysis.<BR>
</FONT></CODE>
</BODY></HTML>

------_=_NextPart_001_01C29B83.802504AF--
_______________________________________________
manet mailing list
manet@ietf.org
https://www1.ietf.org/mailman/listinfo/manet


From mailnull@www1.ietf.org  Wed Dec  4 07:25: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 HAA07421
	for <manet-archive@odin.ietf.org>; Wed, 4 Dec 2002 07:25:23 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id gB4CRiP13316
	for manet-archive@odin.ietf.org; Wed, 4 Dec 2002 07:27: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 gB4CRhv13313
	for <manet-web-archive@optimus.ietf.org>; Wed, 4 Dec 2002 07:27: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 HAA07413
	for <manet-web-archive@ietf.org>; Wed, 4 Dec 2002 07:24: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 gB4C0xv11710;
	Wed, 4 Dec 2002 07:00: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 gB4BwJv11603
	for <manet@optimus.ietf.org>; Wed, 4 Dec 2002 06:58:19 -0500
Received: from msweeper.seri.co.uk (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id GAA06772
	for <manet@ietf.org>; Wed, 4 Dec 2002 06:55:27 -0500 (EST)
Received: from ex1.seri.co.uk (ex1.seri.co.uk) by msweeper.seri.co.uk
 (Content Technologies SMTPRS 4.2.10) with ESMTP id <T5ef592df15c28512ac750@msweeper.seri.co.uk> for <manet@ietf.org>;
 Wed, 4 Dec 2002 10:49:29 +0000
X-MimeOLE: Produced By Microsoft Exchange V6.0.5762.3
content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="----_=_NextPart_001_01C29B83.802504AF"
Subject: RE: [manet] is info on link capacity available to a manet protocol
Date: Wed, 4 Dec 2002 10:54:21 -0000
Message-ID: <341710540F08E34498A057DEE04DAAD73CBAA6@ex1.seri.co.uk>
Thread-Topic: [manet] is info on link capacity available to a manet protocol
Thread-Index: AcKa7hLhVKzZF/cYShuRe5KPwuivSgAkQPnw
From: "Martin Layley" <mlayley@seri.co.uk>
To: <manet@ietf.org>
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_01C29B83.802504AF
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

Battery life/performance currently fits in the ISO model at layer 7 (applic=
ation).  Historically, because most network components have been powered by=
 mains supplies, (often with UPS and generator backup), lifetime of power h=
as had nothing to do with communication.  The big systems will run a power =
monitoring application which will update routing tables, DNS servers etc of=
 other machines, before the computer is shut down.  With the growth of smal=
l, battery powered devices, this is effectively a new problem.
=20
I don't know the 802.11 layer 2, but I am very familiar with Bluetooth (BT)=
, having used chips from 5 different silicon vendors.  Most of these device=
s don't even have the ability to measure the battery voltage.  Battery life=
 estimation requires an intelligent charger with the ability to measure the=
 battery capacity and report it.  To read the battery charger, a BT device =
needs an I2C or SPI bus.  Most devices do have these, for reading external =
E2PROMs.  Some cannot extend this use, others allow the user to write a C p=
rogram to bit-bash the I/O pins.  The BT spec gives a minimal set of functi=
ons and allows the silicon vendor to provide extra manufacturer specific co=
mmands. The system designer can then create an application which monitors t=
he system health.  What is done with this information is then outside the B=
T spec.
=20
Laptops & PDAs may have the ability to guess their remaining battery life. =
 This will be part of the operating system & will be present regardless of =
networking components.  This information may be able to be read remotely.  =
If it is available, a reading application will be required (such as IE, net=
scape, mosaic).  This again is layer 7.
=20
=20
=20
I agree that altering network routing to avoid battery powered devices with=
 marginal capacity is extremely desirable.  To achieve this, you will need =
to look at using a system management protocol.  I am not very familiar with=
 it, but SMTP may provide you with the desired features.
=20
=20
        Martin

-----Original Message-----
From: Jigar Doshi [mailto:jigarnetmeet@hotmail.com]
Sent: 03 December 2002 11:19
To: manet@ietf.org
Subject: [manet] is info on link capacity available to a manet protocol



Hello,

Does the network layer report information such as link capacity ( i.e bandw=
idth ) and/or expected remaining battery life . We are currently developing=
 a protocol which uses this information to calculate optimum paths .A way o=
ut of the bandwidth calculation would be indirectly measuring the performan=
ce of the link by sending packets across. Is there a more efficient way? Ca=
n it be assumed tht such information is available , while designing the pro=
tocol like the conventional protocols.

Jigar Doshi & K Prahlad




  _____ =20

Tired of spam? Get advanced junk mail  <http://g.msn.com/8HMSEN/2017> prote=
ction with MSN 8. _______________________________________________ manet mai=
ling list manet@ietf.org https://www1.ietf.org/mailman/listinfo/manet=20



The mail message has been scanned by MAILsweeper
for content analysis.


------_=_NextPart_001_01C29B83.802504AF
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=3D"Content-Type" CONTENT=3D"text/html; charset=3Diso-8859-=
1">


<META content=3D"MSHTML 6.00.2600.0" name=3DGENERATOR></HEAD>
<BODY>
<DIV><SPAN class=3D509462210-04122002><FONT face=3DArial color=3D#0000ff=20
size=3D2>Battery life/performance currently fits in the ISO model at layer =
7=20
(application).&nbsp; Historically, because most network components have bee=
n=20
powered by mains supplies, (often with UPS and generator backup), lifetime =
of=20
power has had nothing to do with communication.&nbsp; The big systems will =
run a=20
power monitoring application which will update routing tables, DNS servers =
etc=20
of other machines, before the computer is shut down.&nbsp; With the growth =
of=20
small, battery powered devices, this is effectively a new=20
problem.</FONT></SPAN></DIV>
<DIV><SPAN class=3D509462210-04122002><FONT face=3DArial color=3D#0000ff=20
size=3D2></FONT></SPAN>&nbsp;</DIV>
<DIV><SPAN class=3D509462210-04122002><FONT face=3DArial color=3D#0000ff si=
ze=3D2>I=20
don't know the 802.11 layer 2, but I am very familiar with Bluetooth (BT),=
 having used chips from 5 different silicon vendors.&nbsp; Most of these de=
vices=20
don't even have the ability to measure the battery voltage.&nbsp; Battery l=
ife=20
estimation requires an intelligent charger with the ability to measure the=
 battery capacity and report it.&nbsp; To read the battery charger, a BT de=
vice=20
needs an I2C or SPI bus.&nbsp; Most devices do have these, for reading exte=
rnal=20
E2PROMs.&nbsp; Some cannot extend this use, others allow the user to write =
a C=20
program to bit-bash the I/O pins.&nbsp; The&nbsp;BT spec gives a minimal se=
t of=20
functions and allows the silicon vendor to provide extra manufacturer speci=
fic=20
commands.&nbsp;The system designer can then create an application which mon=
itors=20
the system health.&nbsp; What is done with this information is then outside=
 the=20
BT spec.</FONT></SPAN></DIV>
<DIV><SPAN class=3D509462210-04122002></SPAN>&nbsp;</DIV>
<DIV><SPAN class=3D509462210-04122002><FONT face=3DArial color=3D#0000ff=20
size=3D2>Laptops &amp; PDAs may have the ability to guess their remaining b=
attery=20
life.&nbsp; This will be part of the operating system &amp; will be present=
 regardless of networking components.&nbsp; This information may be able to=
 be=20
read remotely.&nbsp; If it is available, a reading application will be requ=
ired=20
(such as IE, netscape, mosaic).&nbsp; This again is layer 7.</FONT></SPAN><=
/DIV>
<DIV><SPAN class=3D509462210-04122002><FONT face=3DArial color=3D#0000ff=20
size=3D2></FONT></SPAN>&nbsp;</DIV>
<DIV><SPAN class=3D509462210-04122002><FONT face=3DArial color=3D#0000ff=20
size=3D2></FONT></SPAN>&nbsp;</DIV>
<DIV><SPAN class=3D509462210-04122002><FONT face=3DArial color=3D#0000ff=20
size=3D2></FONT></SPAN>&nbsp;</DIV>
<DIV><SPAN class=3D509462210-04122002><FONT face=3DArial color=3D#0000ff si=
ze=3D2>I=20
agree that altering network routing to avoid battery powered devices with=
 marginal capacity is extremely desirable.&nbsp; To achieve this, you will =
need=20
to look at using a system management protocol.&nbsp; I am not very familiar=
 with=20
it, but SMTP may provide you with the desired features.</FONT></SPAN></DIV>
<DIV><SPAN class=3D509462210-04122002><FONT face=3DArial color=3D#0000ff=20
size=3D2></FONT></SPAN>&nbsp;</DIV>
<DIV><SPAN class=3D509462210-04122002><FONT face=3DArial color=3D#0000ff=20
size=3D2></FONT></SPAN>&nbsp;</DIV>
<DIV><SPAN class=3D509462210-04122002>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;=20
<FONT face=3DArial color=3D#0000ff size=3D2>Martin</FONT></SPAN></DIV>
<BLOCKQUOTE>
  <DIV class=3DOutlookMessageHeader dir=3Dltr align=3Dleft><FONT face=3DTah=
oma=20
  size=3D2>-----Original Message-----<BR><B>From:</B> Jigar Doshi=20
  [mailto:jigarnetmeet@hotmail.com]<BR><B>Sent:</B> 03 December 2002=20
  11:19<BR><B>To:</B> manet@ietf.org<BR><B>Subject:</B> [manet] is info on =
link=20
  capacity available to a manet protocol<BR><BR></FONT></DIV>
  <DIV>
  <DIV>
  <P>Hello,<BR><BR>Does the network layer report information such as link=
   capacity ( i.e bandwidth ) and/or expected remaining battery life . We a=
re=20
  currently developing a protocol which uses this information to calculate=
   optimum paths .A way out of the bandwidth calculation would be indirectl=
y=20
  measuring the performance of the link by sending packets across. Is there=
 a=20
  more efficient way? Can it be assumed tht such information is available ,=
   while designing the protocol like the conventional protocols.</P>
  <P>Jigar Doshi&nbsp;&amp; K Prahlad<BR><BR></P></DIV></DIV><BR clear=3Dal=
l>
  <HR>
  Tired of spam? Get <A href=3D"http://g.msn.com/8HMSEN/2017">advanced junk=
 mail=20
  protection</A> with MSN 8. ______________________________________________=
_=20
  manet mailing list manet@ietf.org https://www1.ietf.org/mailman/listinfo/=
manet=20
</BLOCKQUOTE><CODE><FONT SIZE=3D3><BR>
<BR>
The mail message has been scanned by MAILsweeper<BR>
for content analysis.<BR>
</FONT></CODE>
</BODY></HTML>

------_=_NextPart_001_01C29B83.802504AF--
_______________________________________________
manet mailing list
manet@ietf.org
https://www1.ietf.org/mailman/listinfo/manet



From mailnull@www1.ietf.org  Wed Dec  4 10:29: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 KAA16405
	for <manet-archive@odin.ietf.org>; Wed, 4 Dec 2002 10:29:48 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id gB4FWBN25287
	for manet-archive@odin.ietf.org; Wed, 4 Dec 2002 10:32: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 gB4FWAv25284
	for <manet-web-archive@optimus.ietf.org>; Wed, 4 Dec 2002 10:32: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 KAA16395
	for <manet-web-archive@ietf.org>; Wed, 4 Dec 2002 10:29: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 gB4FJHv24430;
	Wed, 4 Dec 2002 10:19: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 gB4FGgv24245
	for <manet@optimus.ietf.org>; Wed, 4 Dec 2002 10:16:42 -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 KAA15517
	for <manet@ietf.org>; Wed, 4 Dec 2002 10:13:48 -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 KAA19680;
	Wed, 4 Dec 2002 10:16:32 -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 M2002120410163329496
 ; Wed, 04 Dec 2002 10:16:33 -0500
Message-Id: <5.1.1.5.2.20021204101623.014d6990@pop.itd.nrl.navy.mil>
X-Sender: macker@pop.itd.nrl.navy.mil
X-Mailer: QUALCOMM Windows Eudora Version 5.1.1
Date: Wed, 04 Dec 2002 10:18:06 -0500
To: "Martin Layley" <mlayley@seri.co.uk>, <manet@ietf.org>
From: Joe Macker <macker@itd.nrl.navy.mil>
Subject: RE: [manet] is info on link capacity available to a manet
  protocol
In-Reply-To: <341710540F08E34498A057DEE04DAAD73CBAA6@ex1.seri.co.uk>
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 agree that altering network routing to avoid battery powered devices with marginal capacity is extremely desirable.  To achieve this, you will need to look at using a system management protocol.  I am not very familiar with it, but SMTP may provide you with the desired features.

In the MANET sesne, this can be supported through simple router preference features (e.g., in OLSR and TBRPF updates)..

> 
> 
>        Martin  
>-----Original Message----- 
>From: Jigar Doshi [mailto:jigarnetmeet@hotmail.com] 
>Sent: 03 December 2002 11:19 
>To: manet@ietf.org 
>Subject: [manet] is info on link capacity available to a manet protocol
>
>Hello,
>
>Does the network layer report information such as link capacity ( i.e bandwidth ) and/or expected remaining battery life . We are currently developing a protocol which uses this information to calculate optimum paths .A way out of the bandwidth calculation would be indirectly measuring the performance of the link by sending packets across. Is there a more efficient way? Can it be assumed tht such information is available , while designing the protocol like the conventional protocols.
>
>Jigar Doshi & K Prahlad
>
>
>
>
>----------
>Tired of spam? Get <http://g.msn.com/8HMSEN/2017>advanced junk mail protection with MSN 8. _______________________________________________ manet mailing list manet@ietf.org https://www1.ietf.org/mailman/listinfo/manet 
>
>
>
>The mail message has been scanned by MAILsweeper
>for content analysis.


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



From mailnull@www1.ietf.org  Wed Dec  4 10:52: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 KAA17958
	for <manet-archive@odin.ietf.org>; Wed, 4 Dec 2002 10:52:17 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id gB4Fsew27751
	for manet-archive@odin.ietf.org; Wed, 4 Dec 2002 10:54: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 gB4Fsdv27748
	for <manet-web-archive@optimus.ietf.org>; Wed, 4 Dec 2002 10:54: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 KAA17944
	for <manet-web-archive@ietf.org>; Wed, 4 Dec 2002 10:51: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 gB4Fgsv26575;
	Wed, 4 Dec 2002 10:42: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 gB4Ffav26493
	for <manet@optimus.ietf.org>; Wed, 4 Dec 2002 10:41:36 -0500
Received: from msweeper.seri.co.uk (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA16976
	for <manet@ietf.org>; Wed, 4 Dec 2002 10:38:42 -0500 (EST)
Received: from ex1.seri.co.uk (ex1.seri.co.uk) by msweeper.seri.co.uk
 (Content Technologies SMTPRS 4.2.10) with ESMTP id <T5ef68f6802c28512ac750@msweeper.seri.co.uk> for <manet@ietf.org>;
 Wed, 4 Dec 2002 15:25:19 +0000
X-MimeOLE: Produced By Microsoft Exchange V6.0.5762.3
content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain; charset="iso-8859-1"
Subject: RE: [manet] is info on link capacity available to a manet protocol
Date: Wed, 4 Dec 2002 15:30:11 -0000
Message-ID: <341710540F08E34498A057DEE04DAAD73CBADC@ex1.seri.co.uk>
Thread-Topic: [manet] is info on link capacity available to a manet protocol
Thread-Index: AcKbqKSzK0g0GJeJQ4OWW/jUC60QJgAAHyxA
From: "Martin Layley" <mlayley@seri.co.uk>
To: <manet@ietf.org>
Content-Transfer-Encoding: 8bit
X-MIME-Autoconverted: from quoted-printable to 8bit by www1.ietf.org id gB4Ffav26494
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

So what is needed is an application which can run on a communications node, which can monitor the battery level via operating system calls or via UPS monitoring software.  This application can then change its own network settings and possibly trigger a change in the behaviour of neighbouring nodes via the appropriate routing update features of the protocol in use.

Alternatively, you will have to write your own hardware specific layer 1 & layer 2 protocols.

		Martin

-----Original Message-----
From: Joe Macker [mailto:macker@itd.nrl.navy.mil]
Sent: 04 December 2002 15:18
To: Martin Layley; manet@ietf.org
Subject: RE: [manet] is info on link capacity available to a manet
protocol



>
> 
>I agree that altering network routing to avoid battery powered devices with marginal capacity is extremely desirable.  To achieve this, you will need to look at using a system management protocol.  I am not very familiar with it, but SMTP may provide you with the desired features.

In the MANET sesne, this can be supported through simple router preference features (e.g., in OLSR and TBRPF updates)..

> 
> 
>        Martin  
>-----Original Message----- 
>From: Jigar Doshi [mailto:jigarnetmeet@hotmail.com] 
>Sent: 03 December 2002 11:19 
>To: manet@ietf.org 
>Subject: [manet] is info on link capacity available to a manet protocol
>
>Hello,
>
>Does the network layer report information such as link capacity ( i.e bandwidth ) and/or expected remaining battery life . We are currently developing a protocol which uses this information to calculate optimum paths .A way out of the bandwidth calculation would be indirectly measuring the performance of the link by sending packets across. Is there a more efficient way? Can it be assumed tht such information is available , while designing the protocol like the conventional protocols.
>
>Jigar Doshi & K Prahlad
>
>
>
>
>----------
>Tired of spam? Get <http://g.msn.com/8HMSEN/2017>advanced junk mail protection with MSN 8. _______________________________________________ manet mailing list manet@ietf.org https://www1.ietf.org/mailman/listinfo/manet 
>
>
>
>The mail message has been scanned by MAILsweeper
>for content analysis.




The mail message has been scanned by MAILsweeper
for content analysis.

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



From manet-admin@ietf.org  Wed Dec  4 10:52: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 KAA18012
	for <manet-archive@lists.ietf.org>; Wed, 4 Dec 2002 10:52: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 gB4Fgsv26575;
	Wed, 4 Dec 2002 10:42: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 gB4Ffav26493
	for <manet@optimus.ietf.org>; Wed, 4 Dec 2002 10:41:36 -0500
Received: from msweeper.seri.co.uk (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA16976
	for <manet@ietf.org>; Wed, 4 Dec 2002 10:38:42 -0500 (EST)
Received: from ex1.seri.co.uk (ex1.seri.co.uk) by msweeper.seri.co.uk
 (Content Technologies SMTPRS 4.2.10) with ESMTP id <T5ef68f6802c28512ac750@msweeper.seri.co.uk> for <manet@ietf.org>;
 Wed, 4 Dec 2002 15:25:19 +0000
X-MimeOLE: Produced By Microsoft Exchange V6.0.5762.3
content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain; charset="iso-8859-1"
Subject: RE: [manet] is info on link capacity available to a manet protocol
Date: Wed, 4 Dec 2002 15:30:11 -0000
Message-ID: <341710540F08E34498A057DEE04DAAD73CBADC@ex1.seri.co.uk>
Thread-Topic: [manet] is info on link capacity available to a manet protocol
Thread-Index: AcKbqKSzK0g0GJeJQ4OWW/jUC60QJgAAHyxA
From: "Martin Layley" <mlayley@seri.co.uk>
To: <manet@ietf.org>
Content-Transfer-Encoding: 8bit
X-MIME-Autoconverted: from quoted-printable to 8bit by www1.ietf.org id gB4Ffav26494
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

So what is needed is an application which can run on a communications node, which can monitor the battery level via operating system calls or via UPS monitoring software.  This application can then change its own network settings and possibly trigger a change in the behaviour of neighbouring nodes via the appropriate routing update features of the protocol in use.

Alternatively, you will have to write your own hardware specific layer 1 & layer 2 protocols.

		Martin

-----Original Message-----
From: Joe Macker [mailto:macker@itd.nrl.navy.mil]
Sent: 04 December 2002 15:18
To: Martin Layley; manet@ietf.org
Subject: RE: [manet] is info on link capacity available to a manet
protocol



>
> 
>I agree that altering network routing to avoid battery powered devices with marginal capacity is extremely desirable.  To achieve this, you will need to look at using a system management protocol.  I am not very familiar with it, but SMTP may provide you with the desired features.

In the MANET sesne, this can be supported through simple router preference features (e.g., in OLSR and TBRPF updates)..

> 
> 
>        Martin  
>-----Original Message----- 
>From: Jigar Doshi [mailto:jigarnetmeet@hotmail.com] 
>Sent: 03 December 2002 11:19 
>To: manet@ietf.org 
>Subject: [manet] is info on link capacity available to a manet protocol
>
>Hello,
>
>Does the network layer report information such as link capacity ( i.e bandwidth ) and/or expected remaining battery life . We are currently developing a protocol which uses this information to calculate optimum paths .A way out of the bandwidth calculation would be indirectly measuring the performance of the link by sending packets across. Is there a more efficient way? Can it be assumed tht such information is available , while designing the protocol like the conventional protocols.
>
>Jigar Doshi & K Prahlad
>
>
>
>
>----------
>Tired of spam? Get <http://g.msn.com/8HMSEN/2017>advanced junk mail protection with MSN 8. _______________________________________________ manet mailing list manet@ietf.org https://www1.ietf.org/mailman/listinfo/manet 
>
>
>
>The mail message has been scanned by MAILsweeper
>for content analysis.




The mail message has been scanned by MAILsweeper
for content analysis.

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


From manet-admin@ietf.org  Wed Dec  4 10:55: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 KAA18142
	for <manet-archive@lists.ietf.org>; Wed, 4 Dec 2002 10:55: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 gB4FJHv24430;
	Wed, 4 Dec 2002 10:19: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 gB4FGgv24245
	for <manet@optimus.ietf.org>; Wed, 4 Dec 2002 10:16:42 -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 KAA15517
	for <manet@ietf.org>; Wed, 4 Dec 2002 10:13:48 -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 KAA19680;
	Wed, 4 Dec 2002 10:16:32 -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 M2002120410163329496
 ; Wed, 04 Dec 2002 10:16:33 -0500
Message-Id: <5.1.1.5.2.20021204101623.014d6990@pop.itd.nrl.navy.mil>
X-Sender: macker@pop.itd.nrl.navy.mil
X-Mailer: QUALCOMM Windows Eudora Version 5.1.1
Date: Wed, 04 Dec 2002 10:18:06 -0500
To: "Martin Layley" <mlayley@seri.co.uk>, <manet@ietf.org>
From: Joe Macker <macker@itd.nrl.navy.mil>
Subject: RE: [manet] is info on link capacity available to a manet
  protocol
In-Reply-To: <341710540F08E34498A057DEE04DAAD73CBAA6@ex1.seri.co.uk>
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 agree that altering network routing to avoid battery powered devices with marginal capacity is extremely desirable.  To achieve this, you will need to look at using a system management protocol.  I am not very familiar with it, but SMTP may provide you with the desired features.

In the MANET sesne, this can be supported through simple router preference features (e.g., in OLSR and TBRPF updates)..

> 
> 
>        Martin  
>-----Original Message----- 
>From: Jigar Doshi [mailto:jigarnetmeet@hotmail.com] 
>Sent: 03 December 2002 11:19 
>To: manet@ietf.org 
>Subject: [manet] is info on link capacity available to a manet protocol
>
>Hello,
>
>Does the network layer report information such as link capacity ( i.e bandwidth ) and/or expected remaining battery life . We are currently developing a protocol which uses this information to calculate optimum paths .A way out of the bandwidth calculation would be indirectly measuring the performance of the link by sending packets across. Is there a more efficient way? Can it be assumed tht such information is available , while designing the protocol like the conventional protocols.
>
>Jigar Doshi & K Prahlad
>
>
>
>
>----------
>Tired of spam? Get <http://g.msn.com/8HMSEN/2017>advanced junk mail protection with MSN 8. _______________________________________________ manet mailing list manet@ietf.org https://www1.ietf.org/mailman/listinfo/manet 
>
>
>
>The mail message has been scanned by MAILsweeper
>for content analysis.


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


From mailnull@www1.ietf.org  Wed Dec  4 22:02: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 WAA16797
	for <manet-archive@odin.ietf.org>; Wed, 4 Dec 2002 22:02:00 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id gB534Sv09901
	for manet-archive@odin.ietf.org; Wed, 4 Dec 2002 22:04: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 gB534Sv09898
	for <manet-web-archive@optimus.ietf.org>; Wed, 4 Dec 2002 22:04: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 WAA16781
	for <manet-web-archive@ietf.org>; Wed, 4 Dec 2002 22:01: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 gB52qiv09434;
	Wed, 4 Dec 2002 21:52: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 gB52nmv09357
	for <manet@optimus.ietf.org>; Wed, 4 Dec 2002 21:49:48 -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 VAA16464
	for <manet@ietf.org>; Wed, 4 Dec 2002 21:46:49 -0500 (EST)
Received: from bert.cs.pitt.edu (bert.cs.pitt.edu [136.142.79.192])
	by gomez.cs.pitt.edu (8.11.6/8.11.5) with ESMTP id gB52nex28144
	for <manet@ietf.org>; Wed, 4 Dec 2002 21:49:40 -0500
	(envelope-from skhattab@cs.pitt.edu)
Date: Wed, 4 Dec 2002 21:49:40 -0500 (EST)
From: "Sherif E. Mohamed Khattab" <skhattab@cs.pitt.edu>
To: manet@ietf.org
Message-ID: <Pine.OSF.4.21.0212042143110.1033-100000@bert.cs.pitt.edu>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Subject: [manet] Node misbehavior and 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>

Hi,

  Regarding the problem of mitigating node misbehavior in ad hoc networks
(a "misbehaving" node participates in routing but drops data packets.) Most of 
the current solutions consider source routing protocols (e.g., DSR). Is
there a specific reason for that?

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  Wed Dec  4 22:02: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 WAA16815
	for <manet-archive@lists.ietf.org>; Wed, 4 Dec 2002 22:02: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 gB52qiv09434;
	Wed, 4 Dec 2002 21:52: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 gB52nmv09357
	for <manet@optimus.ietf.org>; Wed, 4 Dec 2002 21:49:48 -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 VAA16464
	for <manet@ietf.org>; Wed, 4 Dec 2002 21:46:49 -0500 (EST)
Received: from bert.cs.pitt.edu (bert.cs.pitt.edu [136.142.79.192])
	by gomez.cs.pitt.edu (8.11.6/8.11.5) with ESMTP id gB52nex28144
	for <manet@ietf.org>; Wed, 4 Dec 2002 21:49:40 -0500
	(envelope-from skhattab@cs.pitt.edu)
Date: Wed, 4 Dec 2002 21:49:40 -0500 (EST)
From: "Sherif E. Mohamed Khattab" <skhattab@cs.pitt.edu>
To: manet@ietf.org
Message-ID: <Pine.OSF.4.21.0212042143110.1033-100000@bert.cs.pitt.edu>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Subject: [manet] Node misbehavior and 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>

Hi,

  Regarding the problem of mitigating node misbehavior in ad hoc networks
(a "misbehaving" node participates in routing but drops data packets.) Most of 
the current solutions consider source routing protocols (e.g., DSR). Is
there a specific reason for that?

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  Thu Dec  5 04:40: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 EAA05558
	for <manet-archive@lists.ietf.org>; Thu, 5 Dec 2002 04:40: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 gB59Zav08318;
	Thu, 5 Dec 2002 04:35: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 gB59XOv08255
	for <manet@optimus.ietf.org>; Thu, 5 Dec 2002 04:33:24 -0500
Received: from mail.rz.uni-ulm.de (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id EAA05295
	for <manet@ietf.org>; Thu, 5 Dec 2002 04:30:21 -0500 (EST)
Received: from informatik.uni-ulm.de (viadfn-isdn-150-2.rz.uni-ulm.de [134.60.150.2])
	(authenticated bits=0)
	by mail.rz.uni-ulm.de (8.12.6/8.12.6) with ESMTP id gB59X8Lc014475
	(version=TLSv1/SSLv3 cipher=RC4-MD5 bits=128 verify=NOT);
	Thu, 5 Dec 2002 10:33:09 +0100 (MET)
Message-ID: <3DEF1D93.9040308@informatik.uni-ulm.de>
Date: Thu, 05 Dec 2002 10:34:11 +0100
From: Frank Kargl <frank.kargl@informatik.uni-ulm.de>
Organization: University of Ulm, Germany
User-Agent: Mozilla/5.0 (Windows; U; Win 9x 4.90; en-US; rv:1.1) Gecko/20020826
X-Accept-Language: de, en
MIME-Version: 1.0
To: "Sherif E. Mohamed Khattab" <skhattab@cs.pitt.edu>
CC: manet@ietf.org
Subject: Re: [manet] Node misbehavior and source routing
References: <Pine.OSF.4.21.0212042143110.1033-100000@bert.cs.pitt.edu>
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

Hi ...

Sherif E. Mohamed Khattab wrote:
>   Regarding the problem of mitigating node misbehavior in ad hoc networks
> (a "misbehaving" node participates in routing but drops data packets.) Most of 
> the current solutions consider source routing protocols (e.g., DSR). Is
> there a specific reason for that?

Of course it's quite convenient to have the complete route information 
available in each node. But other approaches like Secure AODV or SRP 
don't use DSR.

The best solution would be of course to have a security mechanism that 
is independant of the routing protocol but that would be hard to do when 
this mechanism has to do consistency checks on the routing information 
distributed.

So most people designing security mechanisms either choose one of the 
popular AH routing protocols as an example or designs a new protocol 
(again most of the time derived from an existing one).

Regards ... Frank

-- 
-----------------------------------------------------------------------
  Frank Kargl          Multimedia Computing, University of Ulm, Germany
  Mail:frank.kargl@informatik.uni-ulm.de http://www.uni-ulm.de/~fkargl/
-----------------------------------------------------------------------
    Use the SOURCE, Luke !  I feel a great disturbance in the SOURCE.
             But beware of the Microsoft side of the SOURCE !

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


From mailnull@www1.ietf.org  Thu Dec  5 04: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 EAA05862
	for <manet-archive@odin.ietf.org>; Thu, 5 Dec 2002 04:53:59 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id gB59uVD09667
	for manet-archive@odin.ietf.org; Thu, 5 Dec 2002 04:56: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 gB59uUv09664
	for <manet-web-archive@optimus.ietf.org>; Thu, 5 Dec 2002 04:56:30 -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 EAA05837
	for <manet-web-archive@ietf.org>; Thu, 5 Dec 2002 04:53:28 -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 gB59Zav08318;
	Thu, 5 Dec 2002 04:35: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 gB59XOv08255
	for <manet@optimus.ietf.org>; Thu, 5 Dec 2002 04:33:24 -0500
Received: from mail.rz.uni-ulm.de (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id EAA05295
	for <manet@ietf.org>; Thu, 5 Dec 2002 04:30:21 -0500 (EST)
Received: from informatik.uni-ulm.de (viadfn-isdn-150-2.rz.uni-ulm.de [134.60.150.2])
	(authenticated bits=0)
	by mail.rz.uni-ulm.de (8.12.6/8.12.6) with ESMTP id gB59X8Lc014475
	(version=TLSv1/SSLv3 cipher=RC4-MD5 bits=128 verify=NOT);
	Thu, 5 Dec 2002 10:33:09 +0100 (MET)
Message-ID: <3DEF1D93.9040308@informatik.uni-ulm.de>
Date: Thu, 05 Dec 2002 10:34:11 +0100
From: Frank Kargl <frank.kargl@informatik.uni-ulm.de>
Organization: University of Ulm, Germany
User-Agent: Mozilla/5.0 (Windows; U; Win 9x 4.90; en-US; rv:1.1) Gecko/20020826
X-Accept-Language: de, en
MIME-Version: 1.0
To: "Sherif E. Mohamed Khattab" <skhattab@cs.pitt.edu>
CC: manet@ietf.org
Subject: Re: [manet] Node misbehavior and source routing
References: <Pine.OSF.4.21.0212042143110.1033-100000@bert.cs.pitt.edu>
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

Hi ...

Sherif E. Mohamed Khattab wrote:
>   Regarding the problem of mitigating node misbehavior in ad hoc networks
> (a "misbehaving" node participates in routing but drops data packets.) Most of 
> the current solutions consider source routing protocols (e.g., DSR). Is
> there a specific reason for that?

Of course it's quite convenient to have the complete route information 
available in each node. But other approaches like Secure AODV or SRP 
don't use DSR.

The best solution would be of course to have a security mechanism that 
is independant of the routing protocol but that would be hard to do when 
this mechanism has to do consistency checks on the routing information 
distributed.

So most people designing security mechanisms either choose one of the 
popular AH routing protocols as an example or designs a new protocol 
(again most of the time derived from an existing one).

Regards ... Frank

-- 
-----------------------------------------------------------------------
  Frank Kargl          Multimedia Computing, University of Ulm, Germany
  Mail:frank.kargl@informatik.uni-ulm.de http://www.uni-ulm.de/~fkargl/
-----------------------------------------------------------------------
    Use the SOURCE, Luke !  I feel a great disturbance in the SOURCE.
             But beware of the Microsoft side of the SOURCE !

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



From mailnull@www1.ietf.org  Thu Dec  5 09:28: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 JAA13029
	for <manet-archive@odin.ietf.org>; Thu, 5 Dec 2002 09:28:57 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id gB5EVK326830
	for manet-archive@odin.ietf.org; Thu, 5 Dec 2002 09:31: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 gB5EVKv26827
	for <manet-web-archive@optimus.ietf.org>; Thu, 5 Dec 2002 09:31: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 JAA13011
	for <manet-web-archive@ietf.org>; Thu, 5 Dec 2002 09:28: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 gB5ENRv26334;
	Thu, 5 Dec 2002 09:23: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 gB5ELNv26243
	for <manet@optimus.ietf.org>; Thu, 5 Dec 2002 09:21:23 -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 JAA12503
	for <manet@ietf.org>; Thu, 5 Dec 2002 09:18:30 -0500 (EST)
Received: from SRCATL-MTA by mail.scires.com
	with Novell_GroupWise; Thu, 05 Dec 2002 09:22:35 -0500
Message-Id: <sdef1adb.011@mail.scires.com>
X-Mailer: Novell GroupWise Internet Agent 6.0.2 Beta
Date: Thu, 05 Dec 2002 09:22:28 -0500
From: "Pete Sholander" <psholand@scires.com>
To: <manet@ietf.org>, <mlayley@seri.co.uk>
Subject: RE: [manet] is info on link capacity available to a manet
	protocol
Mime-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
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

Martin,

On Linux, you could use /proc/apm to get a laptop's estimate of its
remaining battery life.  You can also use a "faked" version of that file
to emulate changes in a node's "battery status" for testing purposes.

--Pete Sholander

>>> "Martin Layley" <mlayley@seri.co.uk> 12/04/02 05:54AM >>>
 
Laptops & PDAs may have the ability to guess their remaining battery
life.  This will be part of the operating system & will be present
regardless of networking components.  This information may be able to be
read remotely.  If it is available, a reading application will be
required (such as IE, netscape, mosaic).  This again is layer 7.
 
_______________________________________________
manet mailing list
manet@ietf.org
https://www1.ietf.org/mailman/listinfo/manet



From manet-admin@ietf.org  Thu Dec  5 09:29: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 JAA13072
	for <manet-archive@lists.ietf.org>; Thu, 5 Dec 2002 09:29: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 gB5ENRv26334;
	Thu, 5 Dec 2002 09:23: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 gB5ELNv26243
	for <manet@optimus.ietf.org>; Thu, 5 Dec 2002 09:21:23 -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 JAA12503
	for <manet@ietf.org>; Thu, 5 Dec 2002 09:18:30 -0500 (EST)
Received: from SRCATL-MTA by mail.scires.com
	with Novell_GroupWise; Thu, 05 Dec 2002 09:22:35 -0500
Message-Id: <sdef1adb.011@mail.scires.com>
X-Mailer: Novell GroupWise Internet Agent 6.0.2 Beta
Date: Thu, 05 Dec 2002 09:22:28 -0500
From: "Pete Sholander" <psholand@scires.com>
To: <manet@ietf.org>, <mlayley@seri.co.uk>
Subject: RE: [manet] is info on link capacity available to a manet
	protocol
Mime-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
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

Martin,

On Linux, you could use /proc/apm to get a laptop's estimate of its
remaining battery life.  You can also use a "faked" version of that file
to emulate changes in a node's "battery status" for testing purposes.

--Pete Sholander

>>> "Martin Layley" <mlayley@seri.co.uk> 12/04/02 05:54AM >>>
 
Laptops & PDAs may have the ability to guess their remaining battery
life.  This will be part of the operating system & will be present
regardless of networking components.  This information may be able to be
read remotely.  If it is available, a reading application will be
required (such as IE, netscape, mosaic).  This again is layer 7.
 
_______________________________________________
manet mailing list
manet@ietf.org
https://www1.ietf.org/mailman/listinfo/manet


From mailnull@www1.ietf.org  Thu Dec  5 11:51: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 LAA19209
	for <manet-archive@odin.ietf.org>; Thu, 5 Dec 2002 11:51:02 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id gB5GrQK05202
	for manet-archive@odin.ietf.org; Thu, 5 Dec 2002 11:53: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 gB5GrQv05199
	for <manet-web-archive@optimus.ietf.org>; Thu, 5 Dec 2002 11:53: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 LAA19172
	for <manet-web-archive@ietf.org>; Thu, 5 Dec 2002 11:50: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 gB5Gg3v04559;
	Thu, 5 Dec 2002 11:42: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 gB5GXCv03542
	for <manet@optimus.ietf.org>; Thu, 5 Dec 2002 11:33:12 -0500
Received: from moby.atcorp.com (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA18473
	for <manet@ietf.org>; Thu, 5 Dec 2002 11:30:17 -0500 (EST)
Received: from trout (trout.atcorp.com [204.72.172.5])
	by moby.atcorp.com (8.11.2/8.11.2) with SMTP id gB5GXwv30672;
	Thu, 5 Dec 2002 10:33:58 -0600
Received: by localhost with Microsoft MAPI; Thu, 5 Dec 2002 10:33:56 -0600
Message-ID: <01C29C49.D04B59E0.rramanujan@atcorp.com>
From: Ranga Ramanujan <rramanujan@atcorp.com>
Reply-To: "rramanujan@atcorp.com" <rramanujan@atcorp.com>
To: "'Frank Kargl'" <frank.kargl@informatik.uni-ulm.de>,
        "Sherif E. Mohamed Khattab" <skhattab@cs.pitt.edu>
Cc: "manet@ietf.org" <manet@ietf.org>
Subject: RE: [manet] Node misbehavior and source routing
Date: Thu, 5 Dec 2002 10:33:55 -0600
Organization: ATC
X-Mailer: Microsoft Internet E-mail/MAPI - 8.0.0.4211
MIME-Version: 1.0
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

Frank:
Concur with you on the need for protocol-independent 
mechanisms for security in ad hoc networks. Our paper 
below that was published in MILCOM 2002 takes a stab at
such an approach. It presents protocol-independent techniques
for dealing with a particular aspect of security in ad hoc networks, 
i.e. defenses for denial-of-service attacks on data traffic. A prototype 
implementation of the mechanisms described in the paper has 
been completed.    

R. Ramanujan, S. Kudige, S. Takkella, T. Nguyen, F. Adelstein, 
"Intrusion-Resistant Ad Hoc Wireless Networks," Proceedings of MILCOM
2002, October 2002.  www.atcorp.com/research/publications/papr2002.htm 

Ranga

Ranga Ramanujan
Architecture Technology Corporation
9971 Valley View Road
Eden Prairie, MN 55344


-----Original Message-----
From:	Frank Kargl [SMTP:frank.kargl@informatik.uni-ulm.de]
Sent:	Thursday, December 05, 2002 3:34 AM
To:	Sherif E. Mohamed Khattab
Cc:	manet@ietf.org
Subject:	Re: [manet] Node misbehavior and source routing

Hi ...

Sherif E. Mohamed Khattab wrote:
>   Regarding the problem of mitigating node misbehavior in ad hoc networks
> (a "misbehaving" node participates in routing but drops data packets.) Most of 
> the current solutions consider source routing protocols (e.g., DSR). Is
> there a specific reason for that?

Of course it's quite convenient to have the complete route information 
available in each node. But other approaches like Secure AODV or SRP 
don't use DSR.

The best solution would be of course to have a security mechanism that 
is independant of the routing protocol but that would be hard to do when 
this mechanism has to do consistency checks on the routing information 
distributed.

So most people designing security mechanisms either choose one of the 
popular AH routing protocols as an example or designs a new protocol 
(again most of the time derived from an existing one).

Regards ... Frank

-- 
-----------------------------------------------------------------------
  Frank Kargl          Multimedia Computing, University of Ulm, Germany
  Mail:frank.kargl@informatik.uni-ulm.de http://www.uni-ulm.de/~fkargl/
-----------------------------------------------------------------------
    Use the SOURCE, Luke !  I feel a great disturbance in the SOURCE.
             But beware of the Microsoft side of the SOURCE !

_______________________________________________
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 Dec  5 11:51: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 LAA19233
	for <manet-archive@lists.ietf.org>; Thu, 5 Dec 2002 11:51: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 gB5Gg3v04559;
	Thu, 5 Dec 2002 11:42: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 gB5GXCv03542
	for <manet@optimus.ietf.org>; Thu, 5 Dec 2002 11:33:12 -0500
Received: from moby.atcorp.com (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA18473
	for <manet@ietf.org>; Thu, 5 Dec 2002 11:30:17 -0500 (EST)
Received: from trout (trout.atcorp.com [204.72.172.5])
	by moby.atcorp.com (8.11.2/8.11.2) with SMTP id gB5GXwv30672;
	Thu, 5 Dec 2002 10:33:58 -0600
Received: by localhost with Microsoft MAPI; Thu, 5 Dec 2002 10:33:56 -0600
Message-ID: <01C29C49.D04B59E0.rramanujan@atcorp.com>
From: Ranga Ramanujan <rramanujan@atcorp.com>
Reply-To: "rramanujan@atcorp.com" <rramanujan@atcorp.com>
To: "'Frank Kargl'" <frank.kargl@informatik.uni-ulm.de>,
        "Sherif E. Mohamed Khattab" <skhattab@cs.pitt.edu>
Cc: "manet@ietf.org" <manet@ietf.org>
Subject: RE: [manet] Node misbehavior and source routing
Date: Thu, 5 Dec 2002 10:33:55 -0600
Organization: ATC
X-Mailer: Microsoft Internet E-mail/MAPI - 8.0.0.4211
MIME-Version: 1.0
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

Frank:
Concur with you on the need for protocol-independent 
mechanisms for security in ad hoc networks. Our paper 
below that was published in MILCOM 2002 takes a stab at
such an approach. It presents protocol-independent techniques
for dealing with a particular aspect of security in ad hoc networks, 
i.e. defenses for denial-of-service attacks on data traffic. A prototype 
implementation of the mechanisms described in the paper has 
been completed.    

R. Ramanujan, S. Kudige, S. Takkella, T. Nguyen, F. Adelstein, 
"Intrusion-Resistant Ad Hoc Wireless Networks," Proceedings of MILCOM
2002, October 2002.  www.atcorp.com/research/publications/papr2002.htm 

Ranga

Ranga Ramanujan
Architecture Technology Corporation
9971 Valley View Road
Eden Prairie, MN 55344


-----Original Message-----
From:	Frank Kargl [SMTP:frank.kargl@informatik.uni-ulm.de]
Sent:	Thursday, December 05, 2002 3:34 AM
To:	Sherif E. Mohamed Khattab
Cc:	manet@ietf.org
Subject:	Re: [manet] Node misbehavior and source routing

Hi ...

Sherif E. Mohamed Khattab wrote:
>   Regarding the problem of mitigating node misbehavior in ad hoc networks
> (a "misbehaving" node participates in routing but drops data packets.) Most of 
> the current solutions consider source routing protocols (e.g., DSR). Is
> there a specific reason for that?

Of course it's quite convenient to have the complete route information 
available in each node. But other approaches like Secure AODV or SRP 
don't use DSR.

The best solution would be of course to have a security mechanism that 
is independant of the routing protocol but that would be hard to do when 
this mechanism has to do consistency checks on the routing information 
distributed.

So most people designing security mechanisms either choose one of the 
popular AH routing protocols as an example or designs a new protocol 
(again most of the time derived from an existing one).

Regards ... Frank

-- 
-----------------------------------------------------------------------
  Frank Kargl          Multimedia Computing, University of Ulm, Germany
  Mail:frank.kargl@informatik.uni-ulm.de http://www.uni-ulm.de/~fkargl/
-----------------------------------------------------------------------
    Use the SOURCE, Luke !  I feel a great disturbance in the SOURCE.
             But beware of the Microsoft side of the SOURCE !

_______________________________________________
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 Dec  5 17:24: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 RAA02841
	for <manet-archive@odin.ietf.org>; Thu, 5 Dec 2002 17:24:38 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id gB5MR5q28108
	for manet-archive@odin.ietf.org; Thu, 5 Dec 2002 17:27: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 gB5MR5v28105
	for <manet-web-archive@optimus.ietf.org>; Thu, 5 Dec 2002 17:27:05 -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 RAA02827
	for <manet-web-archive@ietf.org>; Thu, 5 Dec 2002 17:24: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 gB5MCGv27252;
	Thu, 5 Dec 2002 17:12: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 gB5M4mv26334
	for <manet@optimus.ietf.org>; Thu, 5 Dec 2002 17:04:48 -0500
Received: from blv-smtpout-01.boeing.com (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA02021
	for <manet@ietf.org>; Thu, 5 Dec 2002 17:01:50 -0500 (EST)
Received: from stl-av-01.boeing.com ([192.76.190.6])
	by blv-smtpout-01.boeing.com (8.9.2/8.8.5-M2) with ESMTP id OAA18191;
	Thu, 5 Dec 2002 14:04:41 -0800 (PST)
Received: from slb-hub-01.boeing.com (localhost [127.0.0.1])
	by stl-av-01.boeing.com (8.9.3/8.9.2/MBS-AV-02) with ESMTP id QAA06893;
	Thu, 5 Dec 2002 16:04:38 -0600 (CST)
Received: from xch-phl-02p.ne.nos.boeing.com (xch-phl-02p.ne.nos.boeing.com [128.225.22.4])
	by slb-hub-01.boeing.com (8.11.3/8.11.3/MBS-LDAP-01) with ESMTP id gB5M4b111592;
	Thu, 5 Dec 2002 14:04:37 -0800 (PST)
Received: by xch-phl-02p.ne.nos.boeing.com with Internet Mail Service (5.5.2653.19)
	id <XQHZZHYK>; Thu, 5 Dec 2002 17:04:37 -0500
Message-ID: <D18F53ABCD79C14495301518A54E52200AC1E0@xch-ne-01.ne.nos.boeing.com>
From: "Manfredi, Albert E" <albert.e.manfredi@boeing.com>
To: "'Sherif E. Mohamed Khattab'" <skhattab@cs.pitt.edu>, manet@ietf.org
Subject: RE: [manet] Node misbehavior and source routing
Date: Thu, 5 Dec 2002 17:04:31 -0500 
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2653.19)
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>

Sherif E. Mohamed Khattab wrote:

>   Regarding the problem of mitigating node misbehavior in ad 
> hoc networks
> (a "misbehaving" node participates in routing but drops data 
> packets.) Most of 
> the current solutions consider source routing protocols 
> (e.g., DSR). Is
> there a specific reason for that?

The direct answer I would give to this question is that with source routing, a MANET protocol does not need to depend on any special attributes of the IP addresses of the member hosts. The IP addresses are arbitrary numbers from a flat address space, allowing tha MANET hosts, for example, to use their own home IP addresses and to use Mobile IP as it is written.

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



From manet-admin@ietf.org  Thu Dec  5 17:28: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 RAA02952
	for <manet-archive@lists.ietf.org>; Thu, 5 Dec 2002 17:28: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 gB5MCGv27252;
	Thu, 5 Dec 2002 17:12: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 gB5M4mv26334
	for <manet@optimus.ietf.org>; Thu, 5 Dec 2002 17:04:48 -0500
Received: from blv-smtpout-01.boeing.com (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA02021
	for <manet@ietf.org>; Thu, 5 Dec 2002 17:01:50 -0500 (EST)
Received: from stl-av-01.boeing.com ([192.76.190.6])
	by blv-smtpout-01.boeing.com (8.9.2/8.8.5-M2) with ESMTP id OAA18191;
	Thu, 5 Dec 2002 14:04:41 -0800 (PST)
Received: from slb-hub-01.boeing.com (localhost [127.0.0.1])
	by stl-av-01.boeing.com (8.9.3/8.9.2/MBS-AV-02) with ESMTP id QAA06893;
	Thu, 5 Dec 2002 16:04:38 -0600 (CST)
Received: from xch-phl-02p.ne.nos.boeing.com (xch-phl-02p.ne.nos.boeing.com [128.225.22.4])
	by slb-hub-01.boeing.com (8.11.3/8.11.3/MBS-LDAP-01) with ESMTP id gB5M4b111592;
	Thu, 5 Dec 2002 14:04:37 -0800 (PST)
Received: by xch-phl-02p.ne.nos.boeing.com with Internet Mail Service (5.5.2653.19)
	id <XQHZZHYK>; Thu, 5 Dec 2002 17:04:37 -0500
Message-ID: <D18F53ABCD79C14495301518A54E52200AC1E0@xch-ne-01.ne.nos.boeing.com>
From: "Manfredi, Albert E" <albert.e.manfredi@boeing.com>
To: "'Sherif E. Mohamed Khattab'" <skhattab@cs.pitt.edu>, manet@ietf.org
Subject: RE: [manet] Node misbehavior and source routing
Date: Thu, 5 Dec 2002 17:04:31 -0500 
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2653.19)
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>

Sherif E. Mohamed Khattab wrote:

>   Regarding the problem of mitigating node misbehavior in ad 
> hoc networks
> (a "misbehaving" node participates in routing but drops data 
> packets.) Most of 
> the current solutions consider source routing protocols 
> (e.g., DSR). Is
> there a specific reason for that?

The direct answer I would give to this question is that with source routing, a MANET protocol does not need to depend on any special attributes of the IP addresses of the member hosts. The IP addresses are arbitrary numbers from a flat address space, allowing tha MANET hosts, for example, to use their own home IP addresses and to use Mobile IP as it is written.

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


From mailnull@www1.ietf.org  Thu Dec  5 21:44: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 VAA10880
	for <manet-archive@odin.ietf.org>; Thu, 5 Dec 2002 21:44:43 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id gB62lBX11266
	for manet-archive@odin.ietf.org; Thu, 5 Dec 2002 21:47: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 gB62lBv11263
	for <manet-web-archive@optimus.ietf.org>; Thu, 5 Dec 2002 21:47: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 VAA10873
	for <manet-web-archive@ietf.org>; Thu, 5 Dec 2002 21:44: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 gB62dQv10977;
	Thu, 5 Dec 2002 21:39: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 gB62bXv10907
	for <manet@optimus.ietf.org>; Thu, 5 Dec 2002 21:37:33 -0500
Received: from mx1.ustc.edu.cn (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id VAA10521
	for <manet@ietf.org>; Thu, 5 Dec 2002 21:34:31 -0500 (EST)
From: zfx@mail.ustc.edu.cn
Received: from mail.ustc.edu.cn (webmail.ustc.edu.cn [202.38.64.16])
	by mx1.ustc.edu.cn (8.8.7/8.8.6) with SMTP id KAA12751
	for <manet@ietf.org>; Fri, 6 Dec 2002 10:27:09 +0800
Received: from 202.38.75.11
        (SquirrelMail authenticated user zfx)
        by webmail.ustc.edu.cn with HTTP;
        Fri, 6 Dec 2002 10:28:41 +0800 (CST)
Message-ID: <1268.202.38.75.11.1039141721.squirrel@webmail.ustc.edu.cn>
Date: Fri, 6 Dec 2002 10:28:41 +0800 (CST)
To: <manet@ietf.org>
X-Priority: 3
Importance: Normal
X-MSMail-Priority: Normal
X-Mailer: SquirrelMail (version 1.2.0 [cvs])
MIME-Version: 1.0
Content-Type: text/plain; charset=gb2312
Content-Transfer-Encoding: 8bit
Content-Transfer-Encoding: 8bit
Subject: [manet] =?gb2312?Q?Help:How_to_install_mobiemu-1.2=3F?=
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 have downloaded a copy of mobiemu-1.2 from sourceforge,but I find
the README document is 0 KB;

     Who can tell me how to install mobiemu or,give me some useful
infomation? Thanks!


                                                        Windance


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



From manet-admin@ietf.org  Thu Dec  5 21:50: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 VAA10972
	for <manet-archive@lists.ietf.org>; Thu, 5 Dec 2002 21:50: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 gB62dQv10977;
	Thu, 5 Dec 2002 21:39: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 gB62bXv10907
	for <manet@optimus.ietf.org>; Thu, 5 Dec 2002 21:37:33 -0500
Received: from mx1.ustc.edu.cn (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id VAA10521
	for <manet@ietf.org>; Thu, 5 Dec 2002 21:34:31 -0500 (EST)
From: zfx@mail.ustc.edu.cn
Received: from mail.ustc.edu.cn (webmail.ustc.edu.cn [202.38.64.16])
	by mx1.ustc.edu.cn (8.8.7/8.8.6) with SMTP id KAA12751
	for <manet@ietf.org>; Fri, 6 Dec 2002 10:27:09 +0800
Received: from 202.38.75.11
        (SquirrelMail authenticated user zfx)
        by webmail.ustc.edu.cn with HTTP;
        Fri, 6 Dec 2002 10:28:41 +0800 (CST)
Message-ID: <1268.202.38.75.11.1039141721.squirrel@webmail.ustc.edu.cn>
Date: Fri, 6 Dec 2002 10:28:41 +0800 (CST)
To: <manet@ietf.org>
X-Priority: 3
Importance: Normal
X-MSMail-Priority: Normal
X-Mailer: SquirrelMail (version 1.2.0 [cvs])
MIME-Version: 1.0
Content-Type: text/plain; charset=gb2312
Content-Transfer-Encoding: 8bit
Content-Transfer-Encoding: 8bit
Subject: [manet] =?gb2312?Q?Help:How_to_install_mobiemu-1.2=3F?=
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 have downloaded a copy of mobiemu-1.2 from sourceforge,but I find
the README document is 0 KB;

     Who can tell me how to install mobiemu or,give me some useful
infomation? Thanks!


                                                        Windance


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


From manet-admin@ietf.org  Fri Dec  6 01:21: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 BAA16253
	for <manet-archive@lists.ietf.org>; Fri, 6 Dec 2002 01:21: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 gB66Fbv22487;
	Fri, 6 Dec 2002 01:15: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 gB66CWv22424
	for <manet@optimus.ietf.org>; Fri, 6 Dec 2002 01:12:32 -0500
Received: from websmtp03.sohu.com (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id BAA15970
	for <manet@ietf.org>; Fri, 6 Dec 2002 01:09:27 -0500 (EST)
From: limeng4444@sohu.com
Received: from mx48.mail.sohu.com (unknown [192.168.41.238])
	by websmtp03.sohu.com (Postfix) with ESMTP id 2068A66D19
	for <manet@ietf.org>; Fri,  6 Dec 2002 14:12:12 +0800 (CST)
Message-ID: <5002359.1039155134318.JavaMail.postfix@mx48.mail.sohu.com>
Date: Fri, 6 Dec 2002 14:12:14 +0800 (CST)
To: <manet@ietf.org>
Mime-Version: 1.0
Content-Type: text/plain; charset="GB2312"
Content-Transfer-Encoding: 8bit
X-Mailer: Sohu Web Mail 2.0.13
X-SHIP: 166.111.65.148
X-Priority: 3
Content-Transfer-Encoding: 8bit
Subject: [manet] [manet]why ifq->prq_length() return 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

PriQueue *ifq;
ifq->prq_length() and ifq->length() both return 0,
even the rate of packets is 1000/sec
why?
and how could I get the node's ifq length?
thanks~~
_______________________________________________
manet mailing list
manet@ietf.org
https://www1.ietf.org/mailman/listinfo/manet


From mailnull@www1.ietf.org  Fri Dec  6 01:42: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 BAA16802
	for <manet-archive@odin.ietf.org>; Fri, 6 Dec 2002 01:42:54 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id gB66jNA24576
	for manet-archive@odin.ietf.org; Fri, 6 Dec 2002 01:45: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 gB66jNv24573
	for <manet-web-archive@optimus.ietf.org>; Fri, 6 Dec 2002 01:45: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 BAA16783
	for <manet-web-archive@ietf.org>; Fri, 6 Dec 2002 01:42: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 gB66Fbv22487;
	Fri, 6 Dec 2002 01:15: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 gB66CWv22424
	for <manet@optimus.ietf.org>; Fri, 6 Dec 2002 01:12:32 -0500
Received: from websmtp03.sohu.com (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id BAA15970
	for <manet@ietf.org>; Fri, 6 Dec 2002 01:09:27 -0500 (EST)
From: limeng4444@sohu.com
Received: from mx48.mail.sohu.com (unknown [192.168.41.238])
	by websmtp03.sohu.com (Postfix) with ESMTP id 2068A66D19
	for <manet@ietf.org>; Fri,  6 Dec 2002 14:12:12 +0800 (CST)
Message-ID: <5002359.1039155134318.JavaMail.postfix@mx48.mail.sohu.com>
Date: Fri, 6 Dec 2002 14:12:14 +0800 (CST)
To: <manet@ietf.org>
Mime-Version: 1.0
Content-Type: text/plain; charset="GB2312"
Content-Transfer-Encoding: 8bit
X-Mailer: Sohu Web Mail 2.0.13
X-SHIP: 166.111.65.148
X-Priority: 3
Content-Transfer-Encoding: 8bit
Subject: [manet] [manet]why ifq->prq_length() return 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

PriQueue *ifq;
ifq->prq_length() and ifq->length() both return 0,
even the rate of packets is 1000/sec
why?
and how could I get the node's ifq length?
thanks~~
_______________________________________________
manet mailing list
manet@ietf.org
https://www1.ietf.org/mailman/listinfo/manet



From mailnull@www1.ietf.org  Fri Dec  6 06:42: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 GAA02515
	for <manet-archive@odin.ietf.org>; Fri, 6 Dec 2002 06:42:44 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id gB6Bj7G18292
	for manet-archive@odin.ietf.org; Fri, 6 Dec 2002 06:45: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 gB6Bj7v18289
	for <manet-web-archive@optimus.ietf.org>; Fri, 6 Dec 2002 06:45: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 GAA02488
	for <manet-web-archive@ietf.org>; Fri, 6 Dec 2002 06:42: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 gB6Bavv17464;
	Fri, 6 Dec 2002 06:36: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 gB6BY1v17400
	for <manet@optimus.ietf.org>; Fri, 6 Dec 2002 06:34:01 -0500
Received: from smtp.netcabo.pt (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id GAA02283
	for <manet@ietf.org>; Fri, 6 Dec 2002 06:31:07 -0500 (EST)
Received: from apollo ([213.22.117.5]) by smtp.netcabo.pt with Microsoft SMTPSVC(5.0.2195.5329);
	 Fri, 6 Dec 2002 11:32:35 +0000
Message-ID: <003101c29d1b$697aab80$0200a8c0@apollo>
From: =?iso-8859-1?Q?Jo=E3o_Paulo_Barraca?= <jpbarraca@idz.net>
To: "Manet List" <manet@ietf.org>
Date: Fri, 6 Dec 2002 11:34:13 -0000
MIME-Version: 1.0
Content-Type: multipart/alternative;
	boundary="----=_NextPart_000_002E_01C29D1B.66B8A550"
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
X-OriginalArrivalTime: 06 Dec 2002 11:32:35.0531 (UTC) FILETIME=[2C7491B0:01C29D1B]
Subject: [manet] MANET Scenarios
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_002E_01C29D1B.66B8A550
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

I want to evaluate some routing questions in MANET using NS-2 and =
MobiEmu.=20
Where can i find an utility to design Wireless Ad-Hoc scenarios?=20

Thanks in advance
Jo=E3o Paulo Barraca
------=_NextPart_000_002E_01C29D1B.66B8A550
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.1126" name=3DGENERATOR>
<STYLE></STYLE>
</HEAD>
<BODY bgColor=3D#ffffff>
<DIV><FONT face=3DArial size=3D2>I want to evaluate some routing =
questions in MANET=20
using NS-2 and MobiEmu. </FONT></DIV>
<DIV><FONT face=3DArial size=3D2>Where can i find an utility to design =
Wireless=20
Ad-Hoc scenarios? </FONT></DIV>
<DIV><FONT face=3DArial size=3D2></FONT>&nbsp;</DIV>
<DIV><FONT face=3DArial size=3D2>Thanks in advance</FONT></DIV>
<DIV><FONT face=3DArial size=3D2>Jo=E3o Paulo =
Barraca</FONT></DIV></BODY></HTML>

------=_NextPart_000_002E_01C29D1B.66B8A550--

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



From manet-admin@ietf.org  Fri Dec  6 06:43: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 GAA02533
	for <manet-archive@lists.ietf.org>; Fri, 6 Dec 2002 06:43: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 gB6Bavv17464;
	Fri, 6 Dec 2002 06:36: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 gB6BY1v17400
	for <manet@optimus.ietf.org>; Fri, 6 Dec 2002 06:34:01 -0500
Received: from smtp.netcabo.pt (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id GAA02283
	for <manet@ietf.org>; Fri, 6 Dec 2002 06:31:07 -0500 (EST)
Received: from apollo ([213.22.117.5]) by smtp.netcabo.pt with Microsoft SMTPSVC(5.0.2195.5329);
	 Fri, 6 Dec 2002 11:32:35 +0000
Message-ID: <003101c29d1b$697aab80$0200a8c0@apollo>
From: =?iso-8859-1?Q?Jo=E3o_Paulo_Barraca?= <jpbarraca@idz.net>
To: "Manet List" <manet@ietf.org>
Date: Fri, 6 Dec 2002 11:34:13 -0000
MIME-Version: 1.0
Content-Type: multipart/alternative;
	boundary="----=_NextPart_000_002E_01C29D1B.66B8A550"
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
X-OriginalArrivalTime: 06 Dec 2002 11:32:35.0531 (UTC) FILETIME=[2C7491B0:01C29D1B]
Subject: [manet] MANET Scenarios
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_002E_01C29D1B.66B8A550
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

I want to evaluate some routing questions in MANET using NS-2 and =
MobiEmu.=20
Where can i find an utility to design Wireless Ad-Hoc scenarios?=20

Thanks in advance
Jo=E3o Paulo Barraca
------=_NextPart_000_002E_01C29D1B.66B8A550
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.1126" name=3DGENERATOR>
<STYLE></STYLE>
</HEAD>
<BODY bgColor=3D#ffffff>
<DIV><FONT face=3DArial size=3D2>I want to evaluate some routing =
questions in MANET=20
using NS-2 and MobiEmu. </FONT></DIV>
<DIV><FONT face=3DArial size=3D2>Where can i find an utility to design =
Wireless=20
Ad-Hoc scenarios? </FONT></DIV>
<DIV><FONT face=3DArial size=3D2></FONT>&nbsp;</DIV>
<DIV><FONT face=3DArial size=3D2>Thanks in advance</FONT></DIV>
<DIV><FONT face=3DArial size=3D2>Jo=E3o Paulo =
Barraca</FONT></DIV></BODY></HTML>

------=_NextPart_000_002E_01C29D1B.66B8A550--

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


From mailnull@www1.ietf.org  Fri Dec  6 11:55: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 LAA13692
	for <manet-archive@odin.ietf.org>; Fri, 6 Dec 2002 11:55:38 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id gB6Gw3g05322
	for manet-archive@odin.ietf.org; Fri, 6 Dec 2002 11:58: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 gB6Gw3v05319
	for <manet-web-archive@optimus.ietf.org>; Fri, 6 Dec 2002 11:58:03 -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 LAA13661
	for <manet-web-archive@ietf.org>; Fri, 6 Dec 2002 11:55: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 gB6GnYv04926;
	Fri, 6 Dec 2002 11:49: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 gB6GjPv04778
	for <manet@optimus.ietf.org>; Fri, 6 Dec 2002 11:45:25 -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 LAA13292
	for <manet@ietf.org>; Fri, 6 Dec 2002 11:42:28 -0500 (EST)
Received:  from qifan (EE189.eee.kcl.ac.uk [137.73.11.245])
	by angelo.kcl.ac.uk  with SMTP id gB6GeSeO021521;
	Fri, 6 Dec 2002 16:40:28 GMT
Message-ID: <009e01c29d46$58035480$f50b4989@qifan>
From: "Qi Fan" <qi.fan@kcl.ac.uk>
To: "Piyush" <piyush.khengar@kcl.ac.uk>, "MANET Mailing List" <manet@ietf.org>
Date: Fri, 6 Dec 2002 16:41:36 -0000
MIME-Version: 1.0
Content-Type: multipart/related;
	type="multipart/alternative";
	boundary="----=_NextPart_000_009A_01C29D46.57D873F0"
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] fixed address for 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>

This is a multi-part message in MIME format.

------=_NextPart_000_009A_01C29D46.57D873F0
Content-Type: multipart/alternative;
	boundary="----=_NextPart_001_009B_01C29D46.57D873F0"


------=_NextPart_001_009B_01C29D46.57D873F0
Content-Type: text/plain;
	charset="gb2312"
Content-Transfer-Encoding: quoted-printable

BlankHello

Recently, I have read some papers about the address configuration for =
MANET. Here I have some questions:

1. Why do we dynamic assign the address instead of fix (IPV6 have enough =
address) a unique address for each MANET terminal? This ways should be =
very similar with the MAC addresses for Ethernet NIC. By this we can =
save more energy and latency.

2.Nearly all the paper use the IP address as the MANET address. IP =
address is become the standerd, isn't it?

Any comments? I would be very appricate for your infomation.

All the best.

------------------------------------
Qi Fan
=20
Center for Telecommunications Research
King's College London




------=_NextPart_001_009B_01C29D46.57D873F0
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:009901c29d46$57cefe10$f50b4989@qifan>
<DIV>Hello</DIV>
<DIV>&nbsp;</DIV>
<DIV>Recently, I have read some papers about the address configuration =
for=20
MANET. Here I have some questions:</DIV>
<DIV>&nbsp;</DIV>
<DIV>1. Why do we dynamic assign the address instead of fix (IPV6 have =
enough=20
address) a unique address for each MANET terminal? This ways should be =
very=20
similar with the MAC addresses for Ethernet NIC. By this we can save =
more energy=20
and latency.</DIV>
<DIV>&nbsp;</DIV>
<DIV>2.Nearly all the paper use the IP address as the MANET address. IP =
address=20
is become the standerd, isn't it?</DIV>
<DIV>&nbsp;</DIV>
<DIV>Any comments? I would be very appricate for your infomation.</DIV>
<DIV>&nbsp;</DIV>
<DIV>All the best.</DIV>
<DIV>&nbsp;</DIV>
<DIV>------------------------------------<BR>Qi Fan<BR>&nbsp;<BR>Center =
for=20
Telecommunications Research<BR>King's College London<BR></DIV>
<P>&nbsp;</P></BODY></HTML>

------=_NextPart_001_009B_01C29D46.57D873F0--

------=_NextPart_000_009A_01C29D46.57D873F0
Content-Type: image/gif;
	name="Blank Bkgrd.gif"
Content-Transfer-Encoding: base64
Content-ID: <009901c29d46$57cefe10$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_009A_01C29D46.57D873F0--

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



From manet-admin@ietf.org  Fri Dec  6 11:58: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 LAA13749
	for <manet-archive@lists.ietf.org>; Fri, 6 Dec 2002 11:58: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 gB6GnYv04926;
	Fri, 6 Dec 2002 11:49: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 gB6GjPv04778
	for <manet@optimus.ietf.org>; Fri, 6 Dec 2002 11:45:25 -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 LAA13292
	for <manet@ietf.org>; Fri, 6 Dec 2002 11:42:28 -0500 (EST)
Received:  from qifan (EE189.eee.kcl.ac.uk [137.73.11.245])
	by angelo.kcl.ac.uk  with SMTP id gB6GeSeO021521;
	Fri, 6 Dec 2002 16:40:28 GMT
Message-ID: <009e01c29d46$58035480$f50b4989@qifan>
From: "Qi Fan" <qi.fan@kcl.ac.uk>
To: "Piyush" <piyush.khengar@kcl.ac.uk>, "MANET Mailing List" <manet@ietf.org>
Date: Fri, 6 Dec 2002 16:41:36 -0000
MIME-Version: 1.0
Content-Type: multipart/related;
	type="multipart/alternative";
	boundary="----=_NextPart_000_009A_01C29D46.57D873F0"
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] fixed address for 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>

This is a multi-part message in MIME format.

------=_NextPart_000_009A_01C29D46.57D873F0
Content-Type: multipart/alternative;
	boundary="----=_NextPart_001_009B_01C29D46.57D873F0"


------=_NextPart_001_009B_01C29D46.57D873F0
Content-Type: text/plain;
	charset="gb2312"
Content-Transfer-Encoding: quoted-printable

BlankHello

Recently, I have read some papers about the address configuration for =
MANET. Here I have some questions:

1. Why do we dynamic assign the address instead of fix (IPV6 have enough =
address) a unique address for each MANET terminal? This ways should be =
very similar with the MAC addresses for Ethernet NIC. By this we can =
save more energy and latency.

2.Nearly all the paper use the IP address as the MANET address. IP =
address is become the standerd, isn't it?

Any comments? I would be very appricate for your infomation.

All the best.

------------------------------------
Qi Fan
=20
Center for Telecommunications Research
King's College London




------=_NextPart_001_009B_01C29D46.57D873F0
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:009901c29d46$57cefe10$f50b4989@qifan>
<DIV>Hello</DIV>
<DIV>&nbsp;</DIV>
<DIV>Recently, I have read some papers about the address configuration =
for=20
MANET. Here I have some questions:</DIV>
<DIV>&nbsp;</DIV>
<DIV>1. Why do we dynamic assign the address instead of fix (IPV6 have =
enough=20
address) a unique address for each MANET terminal? This ways should be =
very=20
similar with the MAC addresses for Ethernet NIC. By this we can save =
more energy=20
and latency.</DIV>
<DIV>&nbsp;</DIV>
<DIV>2.Nearly all the paper use the IP address as the MANET address. IP =
address=20
is become the standerd, isn't it?</DIV>
<DIV>&nbsp;</DIV>
<DIV>Any comments? I would be very appricate for your infomation.</DIV>
<DIV>&nbsp;</DIV>
<DIV>All the best.</DIV>
<DIV>&nbsp;</DIV>
<DIV>------------------------------------<BR>Qi Fan<BR>&nbsp;<BR>Center =
for=20
Telecommunications Research<BR>King's College London<BR></DIV>
<P>&nbsp;</P></BODY></HTML>

------=_NextPart_001_009B_01C29D46.57D873F0--

------=_NextPart_000_009A_01C29D46.57D873F0
Content-Type: image/gif;
	name="Blank Bkgrd.gif"
Content-Transfer-Encoding: base64
Content-ID: <009901c29d46$57cefe10$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_009A_01C29D46.57D873F0--

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


From manet-admin@ietf.org  Fri Dec  6 15:34: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 PAA23344
	for <manet-archive@lists.ietf.org>; Fri, 6 Dec 2002 15:34: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 gB6KPVv18372;
	Fri, 6 Dec 2002 15:25: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 gB6KNmv18308
	for <manet@optimus.ietf.org>; Fri, 6 Dec 2002 15:23:48 -0500
Received: from mail.cs.utexas.edu (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA22907
	for <manet@ietf.org>; Fri, 6 Dec 2002 15:20:51 -0500 (EST)
Received: from x20.cs.utexas.edu (horatio-239.cs.utexas.edu [128.83.158.239])
	(authenticated bits=0)
	by mail.cs.utexas.edu (8.12.3/8.12.3) with ESMTP id gB6KNeaw015021
	for <manet@ietf.org>; Fri, 6 Dec 2002 14:23:41 -0600 (CST)
Message-Id: <5.1.0.14.2.20021206135944.00a66dc0@mailbox.cs.utexas.edu>
X-Sender: ygz@mailbox.cs.utexas.edu (Unverified)
X-Mailer: QUALCOMM Windows Eudora Version 5.1
Date: Fri, 06 Dec 2002 14:20:50 -0600
To: manet@ietf.org
From: Yongguang Zhang <ygz@cs.utexas.edu>
In-Reply-To: <20021206170002.5397.81198.Mailman@www1.ietf.org>
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 gB6KNmv18309
Subject: [manet] a few questions about mobiemu
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

MobiEmu site: http://mobiemu.sourceforge.net

>From: zfx@mail.ustc.edu.cn
>Subject: [manet] =?gb2312?Q?Help:How_to_install_mobiemu-1.2=3F?=
>
>      I have downloaded a copy of mobiemu-1.2 from sourceforge,but I find
>the README document is 0 KB;
>
>      Who can tell me how to install mobiemu or,give me some useful
>infomation? Thanks!

The README file is not empty; it is just a symbol link to master/README.
If you are getting it from a non-Unix environment, try master/README.
(MobiEmu only works in linux.)

>From: João Paulo Barraca <jpbarraca@idz.net>
>Subject: [manet] MANET Scenarios
>
>I want to evaluate some routing questions in MANET using NS-2 and MobiEmu.
>Where can i find an utility to design Wireless Ad-Hoc scenarios?
>Thanks in advance
>João Paulo Barraca

There is a program in NS2 to generate MANET scenarios: 
indep-utils/cmu-scen-gen/setdest/
MobiEmu uses the same scenario files as NS2.

Yongguang


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


From mailnull@www1.ietf.org  Fri Dec  6 15:47: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 PAA23815
	for <manet-archive@odin.ietf.org>; Fri, 6 Dec 2002 15:47:37 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id gB6Ko3g19908
	for manet-archive@odin.ietf.org; Fri, 6 Dec 2002 15:50: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 gB6Ko3v19905
	for <manet-web-archive@optimus.ietf.org>; Fri, 6 Dec 2002 15:50:03 -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 PAA23801
	for <manet-web-archive@ietf.org>; Fri, 6 Dec 2002 15:47: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 gB6KPVv18372;
	Fri, 6 Dec 2002 15:25: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 gB6KNmv18308
	for <manet@optimus.ietf.org>; Fri, 6 Dec 2002 15:23:48 -0500
Received: from mail.cs.utexas.edu (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA22907
	for <manet@ietf.org>; Fri, 6 Dec 2002 15:20:51 -0500 (EST)
Received: from x20.cs.utexas.edu (horatio-239.cs.utexas.edu [128.83.158.239])
	(authenticated bits=0)
	by mail.cs.utexas.edu (8.12.3/8.12.3) with ESMTP id gB6KNeaw015021
	for <manet@ietf.org>; Fri, 6 Dec 2002 14:23:41 -0600 (CST)
Message-Id: <5.1.0.14.2.20021206135944.00a66dc0@mailbox.cs.utexas.edu>
X-Sender: ygz@mailbox.cs.utexas.edu (Unverified)
X-Mailer: QUALCOMM Windows Eudora Version 5.1
Date: Fri, 06 Dec 2002 14:20:50 -0600
To: manet@ietf.org
From: Yongguang Zhang <ygz@cs.utexas.edu>
In-Reply-To: <20021206170002.5397.81198.Mailman@www1.ietf.org>
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 gB6KNmv18309
Subject: [manet] a few questions about mobiemu
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

MobiEmu site: http://mobiemu.sourceforge.net

>From: zfx@mail.ustc.edu.cn
>Subject: [manet] =?gb2312?Q?Help:How_to_install_mobiemu-1.2=3F?=
>
>      I have downloaded a copy of mobiemu-1.2 from sourceforge,but I find
>the README document is 0 KB;
>
>      Who can tell me how to install mobiemu or,give me some useful
>infomation? Thanks!

The README file is not empty; it is just a symbol link to master/README.
If you are getting it from a non-Unix environment, try master/README.
(MobiEmu only works in linux.)

>From: João Paulo Barraca <jpbarraca@idz.net>
>Subject: [manet] MANET Scenarios
>
>I want to evaluate some routing questions in MANET using NS-2 and MobiEmu.
>Where can i find an utility to design Wireless Ad-Hoc scenarios?
>Thanks in advance
>João Paulo Barraca

There is a program in NS2 to generate MANET scenarios: 
indep-utils/cmu-scen-gen/setdest/
MobiEmu uses the same scenario files as NS2.

Yongguang


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



From manet-admin@ietf.org  Sat Dec  7 05:23: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 FAA24826
	for <manet-archive@lists.ietf.org>; Sat, 7 Dec 2002 05:23: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 gB7AEXv04998;
	Sat, 7 Dec 2002 05:14: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 gB7A5Wv04281
	for <manet@optimus.ietf.org>; Sat, 7 Dec 2002 05:05:32 -0500
Received: from web12504.mail.yahoo.com (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id FAA24584
	for <manet@ietf.org>; Sat, 7 Dec 2002 05:02:39 -0500 (EST)
Message-ID: <20021207100531.33454.qmail@web12504.mail.yahoo.com>
Received: from [202.105.138.19] by web12504.mail.yahoo.com via HTTP; Sat, 07 Dec 2002 02:05:31 PST
Date: Sat, 7 Dec 2002 02:05:31 -0800 (PST)
From: Xuming Fang <xumingfang@yahoo.com>
Subject: Re: [manet] fixed address for MANET?
To: MANET Mailing List <manet@ietf.org>
In-Reply-To: <009e01c29d46$58035480$f50b4989@qifan>
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 have the same question.

X. Fang

--- Qi Fan <qi.fan@kcl.ac.uk> wrote:
> BlankHello
> 
> Recently, I have read some papers about the address
> configuration for MANET. Here I have some questions:
> 
> 1. Why do we dynamic assign the address instead of
> fix (IPV6 have enough address) a unique address for
> each MANET terminal? This ways should be very
> similar with the MAC addresses for Ethernet NIC. By
> this we can save more energy and latency.
> 
> 2.Nearly all the paper use the IP address as the
> MANET address. IP address is become the standerd,
> isn't it?
> 
> Any comments? I would be very appricate for your
> infomation.
> 
> All the best.
> 
> ------------------------------------
> Qi Fan
>  
> Center for Telecommunications Research
> King's College London
> 
> 
> 
> 


__________________________________________________
Do you Yahoo!?
Yahoo! Mail Plus - Powerful. Affordable. Sign up now.
http://mailplus.yahoo.com
_______________________________________________
manet mailing list
manet@ietf.org
https://www1.ietf.org/mailman/listinfo/manet


From mailnull@www1.ietf.org  Sat Dec  7 05:37: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 FAA25143
	for <manet-archive@odin.ietf.org>; Sat, 7 Dec 2002 05:37:40 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id gB7Ae2106118
	for manet-archive@odin.ietf.org; Sat, 7 Dec 2002 05:40: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 gB7Ae2v06115
	for <manet-web-archive@optimus.ietf.org>; Sat, 7 Dec 2002 05:40: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 FAA25140
	for <manet-web-archive@ietf.org>; Sat, 7 Dec 2002 05:37: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 gB7AEXv04998;
	Sat, 7 Dec 2002 05:14: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 gB7A5Wv04281
	for <manet@optimus.ietf.org>; Sat, 7 Dec 2002 05:05:32 -0500
Received: from web12504.mail.yahoo.com (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id FAA24584
	for <manet@ietf.org>; Sat, 7 Dec 2002 05:02:39 -0500 (EST)
Message-ID: <20021207100531.33454.qmail@web12504.mail.yahoo.com>
Received: from [202.105.138.19] by web12504.mail.yahoo.com via HTTP; Sat, 07 Dec 2002 02:05:31 PST
Date: Sat, 7 Dec 2002 02:05:31 -0800 (PST)
From: Xuming Fang <xumingfang@yahoo.com>
Subject: Re: [manet] fixed address for MANET?
To: MANET Mailing List <manet@ietf.org>
In-Reply-To: <009e01c29d46$58035480$f50b4989@qifan>
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 have the same question.

X. Fang

--- Qi Fan <qi.fan@kcl.ac.uk> wrote:
> BlankHello
> 
> Recently, I have read some papers about the address
> configuration for MANET. Here I have some questions:
> 
> 1. Why do we dynamic assign the address instead of
> fix (IPV6 have enough address) a unique address for
> each MANET terminal? This ways should be very
> similar with the MAC addresses for Ethernet NIC. By
> this we can save more energy and latency.
> 
> 2.Nearly all the paper use the IP address as the
> MANET address. IP address is become the standerd,
> isn't it?
> 
> Any comments? I would be very appricate for your
> infomation.
> 
> All the best.
> 
> ------------------------------------
> Qi Fan
>  
> Center for Telecommunications Research
> King's College London
> 
> 
> 
> 


__________________________________________________
Do you Yahoo!?
Yahoo! Mail Plus - Powerful. Affordable. Sign up now.
http://mailplus.yahoo.com
_______________________________________________
manet mailing list
manet@ietf.org
https://www1.ietf.org/mailman/listinfo/manet



From mailnull@www1.ietf.org  Sat Dec  7 14:05: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 OAA04875
	for <manet-archive@odin.ietf.org>; Sat, 7 Dec 2002 14:05:55 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id gB7J8Nt29148
	for manet-archive@odin.ietf.org; Sat, 7 Dec 2002 14:08: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 gB7J8Mv29145
	for <manet-web-archive@optimus.ietf.org>; Sat, 7 Dec 2002 14:08: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 OAA04861
	for <manet-web-archive@ietf.org>; Sat, 7 Dec 2002 14:05: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 gB7Iuav28080;
	Sat, 7 Dec 2002 13:56: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 gB7IpVv27519
	for <manet@optimus.ietf.org>; Sat, 7 Dec 2002 13:51:31 -0500
Received: from csa.iisc.ernet.in (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA04270
	for <manet@ietf.org>; Sat, 7 Dec 2002 13:48:30 -0500 (EST)
Received: from deimos.csa.iisc.ernet.in (deimos.csa.iisc.ernet.in [144.16.67.57])
	by csa.iisc.ernet.in (Postfix) with ESMTP id 8FE6A2CC22
	for <manet@ietf.org>; Sun,  8 Dec 2002 00:21:33 +0530 (IST)
Received: from euler.csa.iisc.ernet.in (euler.csa.iisc.ernet.in [144.16.67.61])
	by deimos.csa.iisc.ernet.in (Postfix) with SMTP id B5BF74E531
	for <manet@ietf.org>; Sun,  8 Dec 2002 00:21:18 +0530 (IST)
Received: (nullmailer pid 26929 invoked by uid 9268);
	Sat, 07 Dec 2002 18:51:18 -0000
Date: Sun, 8 Dec 2002 00:21:18 +0530 (IST)
From: Abhishek Prakash Tayal <aptayal@csa.iisc.ernet.in>
To: manet@ietf.org
Subject: Re: Re: [manet] fixed address for MANET?
In-Reply-To: <20021207170003.22013.18836.Mailman@www1.ietf.org>
Message-ID: <Pine.LNX.4.44.0212080015340.26717-100000@euler.csa.iisc.ernet.in>
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 dont know exactly but i think as the MobileAdhoc Networks are not 
permanently setup network.So it is not a good idea to assign them a 
permanent ip address. Although it will surely save some energy and latency 
but we are wasting one address also.
May be it depends on the life and use of a Mobile AdHoc Node..




Date: Sat, 7 Dec 2002 02:05:31 -0800 (PST)
From: Xuming Fang <xumingfang@yahoo.com>
Subject: Re: [manet] fixed address for MANET?
To: MANET Mailing List <manet@ietf.org>

I have the same question.

X. Fang

--- Qi Fan <qi.fan@kcl.ac.uk> wrote:
> BlankHello
> 
> Recently, I have read some papers about the address
> configuration for MANET. Here I have some questions:
> 
> 1. Why do we dynamic assign the address instead of
> fix (IPV6 have enough address) a unique address for
> each MANET terminal? This ways should be very
> similar with the MAC addresses for Ethernet NIC. By
> this we can save more energy and latency.
> 
> 2.Nearly all the paper use the IP address as the
> MANET address. IP address is become the standerd,
> isn't it?
> 
> Any comments? I would be very appricate for your
> infomation.
> 
> All the best.
> 
> ------------------------------------
> Qi Fan
>  
> Center for Telecommunications Research
> King's College London
> 
> 
> 
> 


__________________________________________________
Do you Yahoo!?
Yahoo! Mail Plus - Powerful. Affordable. Sign up now.
http://mailplus.yahoo.com


-- 
Abhishek Prakash Tayal								
ME Scholar
Room # G 64
Students Hostel
Indian Institute of Scince
Bangalore-12, India
Ph 3942468-227(Intel Lab)
3942621	  (Hostel Block)
****************************************************************
Wanna look my home page visit http://people.csa.iisc.ernet.in/aptayal/
****************************************************************

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



From manet-admin@ietf.org  Sat Dec  7 14:11: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 OAA04981
	for <manet-archive@lists.ietf.org>; Sat, 7 Dec 2002 14:11: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 gB7Iuav28080;
	Sat, 7 Dec 2002 13:56: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 gB7IpVv27519
	for <manet@optimus.ietf.org>; Sat, 7 Dec 2002 13:51:31 -0500
Received: from csa.iisc.ernet.in (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA04270
	for <manet@ietf.org>; Sat, 7 Dec 2002 13:48:30 -0500 (EST)
Received: from deimos.csa.iisc.ernet.in (deimos.csa.iisc.ernet.in [144.16.67.57])
	by csa.iisc.ernet.in (Postfix) with ESMTP id 8FE6A2CC22
	for <manet@ietf.org>; Sun,  8 Dec 2002 00:21:33 +0530 (IST)
Received: from euler.csa.iisc.ernet.in (euler.csa.iisc.ernet.in [144.16.67.61])
	by deimos.csa.iisc.ernet.in (Postfix) with SMTP id B5BF74E531
	for <manet@ietf.org>; Sun,  8 Dec 2002 00:21:18 +0530 (IST)
Received: (nullmailer pid 26929 invoked by uid 9268);
	Sat, 07 Dec 2002 18:51:18 -0000
Date: Sun, 8 Dec 2002 00:21:18 +0530 (IST)
From: Abhishek Prakash Tayal <aptayal@csa.iisc.ernet.in>
To: manet@ietf.org
Subject: Re: Re: [manet] fixed address for MANET?
In-Reply-To: <20021207170003.22013.18836.Mailman@www1.ietf.org>
Message-ID: <Pine.LNX.4.44.0212080015340.26717-100000@euler.csa.iisc.ernet.in>
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 dont know exactly but i think as the MobileAdhoc Networks are not 
permanently setup network.So it is not a good idea to assign them a 
permanent ip address. Although it will surely save some energy and latency 
but we are wasting one address also.
May be it depends on the life and use of a Mobile AdHoc Node..




Date: Sat, 7 Dec 2002 02:05:31 -0800 (PST)
From: Xuming Fang <xumingfang@yahoo.com>
Subject: Re: [manet] fixed address for MANET?
To: MANET Mailing List <manet@ietf.org>

I have the same question.

X. Fang

--- Qi Fan <qi.fan@kcl.ac.uk> wrote:
> BlankHello
> 
> Recently, I have read some papers about the address
> configuration for MANET. Here I have some questions:
> 
> 1. Why do we dynamic assign the address instead of
> fix (IPV6 have enough address) a unique address for
> each MANET terminal? This ways should be very
> similar with the MAC addresses for Ethernet NIC. By
> this we can save more energy and latency.
> 
> 2.Nearly all the paper use the IP address as the
> MANET address. IP address is become the standerd,
> isn't it?
> 
> Any comments? I would be very appricate for your
> infomation.
> 
> All the best.
> 
> ------------------------------------
> Qi Fan
>  
> Center for Telecommunications Research
> King's College London
> 
> 
> 
> 


__________________________________________________
Do you Yahoo!?
Yahoo! Mail Plus - Powerful. Affordable. Sign up now.
http://mailplus.yahoo.com


-- 
Abhishek Prakash Tayal								
ME Scholar
Room # G 64
Students Hostel
Indian Institute of Scince
Bangalore-12, India
Ph 3942468-227(Intel Lab)
3942621	  (Hostel Block)
****************************************************************
Wanna look my home page visit http://people.csa.iisc.ernet.in/aptayal/
****************************************************************

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


From manet-admin@ietf.org  Sat Dec  7 15:38: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 PAA06737
	for <manet-archive@lists.ietf.org>; Sat, 7 Dec 2002 15:38: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 gB7KTgv32240;
	Sat, 7 Dec 2002 15:29: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 gB7KPKv32078
	for <manet@optimus.ietf.org>; Sat, 7 Dec 2002 15:25:20 -0500
Received: from shaku.sfc.wide.ad.jp (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA06458
	for <manet@ietf.org>; Sat, 7 Dec 2002 15:22:22 -0500 (EST)
Received: from [192.168.0.137] (dsl-65-191-0-253.telocity.com [65.191.0.253])
	(authenticated bits=0)
	by shaku.sfc.wide.ad.jp (8.12.0/8.12.0) with ESMTP id gB7KOb6m020494;
	Sun, 8 Dec 2002 05:24:40 +0900
Date: Sat, 07 Dec 2002 12:24:57 -0800
From: Ryuji Wakikawa <ryuji@sfc.wide.ad.jp>
To: Abhishek Prakash Tayal <aptayal@csa.iisc.ernet.in>
Subject: Re: [manet] fixed address for MANET?
Cc: manet@ietf.org
In-Reply-To: <Pine.LNX.4.44.0212080015340.26717-100000@euler.csa.iisc.ernet.in>
References: <20021207170003.22013.18836.Mailman@www1.ietf.org> <Pine.LNX.4.44.0212080015340.26717-100000@euler.csa.iisc.ernet.in>
Message-Id: <20021207121342.62F4.RYUJI@sfc.wide.ad.jp>
MIME-Version: 1.0
Content-Type: text/plain; charset="US-ASCII"
Content-Transfer-Encoding: 7bit
X-Mailer: Becky! ver. 2.05.01
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

> I dont know exactly but i think as the MobileAdhoc Networks are not 
> permanently setup network.So it is not a good idea to assign them a 
> permanent ip address. Although it will surely save some energy and latency 
> but we are wasting one address also.
> May be it depends on the life and use of a Mobile AdHoc Node..
> 

I agree

If a node needs a permanent ip address, the node can carry its home
address. The node may not start MIP6 operation (sending BU, etc) unless
it communicates with the global Internet. 
The Home address can be used as the unique address of the node in the
manet cloud.

If the node does not have home address, the node should acquire an
address at the attached manet network. 

regards,
ryuj

> 
> 
> Date: Sat, 7 Dec 2002 02:05:31 -0800 (PST)
> From: Xuming Fang <xumingfang@yahoo.com>
> Subject: Re: [manet] fixed address for MANET?
> To: MANET Mailing List <manet@ietf.org>
> 
> I have the same question.
> 
> X. Fang
> 
> --- Qi Fan <qi.fan@kcl.ac.uk> wrote:
> > BlankHello
> > 
> > Recently, I have read some papers about the address
> > configuration for MANET. Here I have some questions:
> > 
> > 1. Why do we dynamic assign the address instead of
> > fix (IPV6 have enough address) a unique address for
> > each MANET terminal? This ways should be very
> > similar with the MAC addresses for Ethernet NIC. By
> > this we can save more energy and latency.
> > 
> > 2.Nearly all the paper use the IP address as the
> > MANET address. IP address is become the standerd,
> > isn't it?
> > 
> > Any comments? I would be very appricate for your
> > infomation.
> > 
> > All the best.
> > 
> > ------------------------------------
> > Qi Fan
> >  
> > Center for Telecommunications Research
> > King's College London
> > 
> > 
> > 
> > 
> 
> 
> __________________________________________________
> Do you Yahoo!?
> Yahoo! Mail Plus - Powerful. Affordable. Sign up now.
> http://mailplus.yahoo.com
> 
> 
> -- 
> Abhishek Prakash Tayal								
> ME Scholar
> Room # G 64
> Students Hostel
> Indian Institute of Scince
> Bangalore-12, India
> Ph 3942468-227(Intel Lab)
> 3942621	  (Hostel Block)
> ****************************************************************
> Wanna look my home page visit http://people.csa.iisc.ernet.in/aptayal/
> ****************************************************************
> 
> _______________________________________________
> manet mailing list
> manet@ietf.org
> https://www1.ietf.org/mailman/listinfo/manet

regards,
ryuji

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


From mailnull@www1.ietf.org  Sat Dec  7 15:50: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 PAA06920
	for <manet-archive@odin.ietf.org>; Sat, 7 Dec 2002 15:50:57 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id gB7KrOB01060
	for manet-archive@odin.ietf.org; Sat, 7 Dec 2002 15:53: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 gB7KrOv01057
	for <manet-web-archive@optimus.ietf.org>; Sat, 7 Dec 2002 15:53: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 PAA06906
	for <manet-web-archive@ietf.org>; Sat, 7 Dec 2002 15: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 gB7KTgv32240;
	Sat, 7 Dec 2002 15:29: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 gB7KPKv32078
	for <manet@optimus.ietf.org>; Sat, 7 Dec 2002 15:25:20 -0500
Received: from shaku.sfc.wide.ad.jp (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA06458
	for <manet@ietf.org>; Sat, 7 Dec 2002 15:22:22 -0500 (EST)
Received: from [192.168.0.137] (dsl-65-191-0-253.telocity.com [65.191.0.253])
	(authenticated bits=0)
	by shaku.sfc.wide.ad.jp (8.12.0/8.12.0) with ESMTP id gB7KOb6m020494;
	Sun, 8 Dec 2002 05:24:40 +0900
Date: Sat, 07 Dec 2002 12:24:57 -0800
From: Ryuji Wakikawa <ryuji@sfc.wide.ad.jp>
To: Abhishek Prakash Tayal <aptayal@csa.iisc.ernet.in>
Subject: Re: [manet] fixed address for MANET?
Cc: manet@ietf.org
In-Reply-To: <Pine.LNX.4.44.0212080015340.26717-100000@euler.csa.iisc.ernet.in>
References: <20021207170003.22013.18836.Mailman@www1.ietf.org> <Pine.LNX.4.44.0212080015340.26717-100000@euler.csa.iisc.ernet.in>
Message-Id: <20021207121342.62F4.RYUJI@sfc.wide.ad.jp>
MIME-Version: 1.0
Content-Type: text/plain; charset="US-ASCII"
Content-Transfer-Encoding: 7bit
X-Mailer: Becky! ver. 2.05.01
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

> I dont know exactly but i think as the MobileAdhoc Networks are not 
> permanently setup network.So it is not a good idea to assign them a 
> permanent ip address. Although it will surely save some energy and latency 
> but we are wasting one address also.
> May be it depends on the life and use of a Mobile AdHoc Node..
> 

I agree

If a node needs a permanent ip address, the node can carry its home
address. The node may not start MIP6 operation (sending BU, etc) unless
it communicates with the global Internet. 
The Home address can be used as the unique address of the node in the
manet cloud.

If the node does not have home address, the node should acquire an
address at the attached manet network. 

regards,
ryuj

> 
> 
> Date: Sat, 7 Dec 2002 02:05:31 -0800 (PST)
> From: Xuming Fang <xumingfang@yahoo.com>
> Subject: Re: [manet] fixed address for MANET?
> To: MANET Mailing List <manet@ietf.org>
> 
> I have the same question.
> 
> X. Fang
> 
> --- Qi Fan <qi.fan@kcl.ac.uk> wrote:
> > BlankHello
> > 
> > Recently, I have read some papers about the address
> > configuration for MANET. Here I have some questions:
> > 
> > 1. Why do we dynamic assign the address instead of
> > fix (IPV6 have enough address) a unique address for
> > each MANET terminal? This ways should be very
> > similar with the MAC addresses for Ethernet NIC. By
> > this we can save more energy and latency.
> > 
> > 2.Nearly all the paper use the IP address as the
> > MANET address. IP address is become the standerd,
> > isn't it?
> > 
> > Any comments? I would be very appricate for your
> > infomation.
> > 
> > All the best.
> > 
> > ------------------------------------
> > Qi Fan
> >  
> > Center for Telecommunications Research
> > King's College London
> > 
> > 
> > 
> > 
> 
> 
> __________________________________________________
> Do you Yahoo!?
> Yahoo! Mail Plus - Powerful. Affordable. Sign up now.
> http://mailplus.yahoo.com
> 
> 
> -- 
> Abhishek Prakash Tayal								
> ME Scholar
> Room # G 64
> Students Hostel
> Indian Institute of Scince
> Bangalore-12, India
> Ph 3942468-227(Intel Lab)
> 3942621	  (Hostel Block)
> ****************************************************************
> Wanna look my home page visit http://people.csa.iisc.ernet.in/aptayal/
> ****************************************************************
> 
> _______________________________________________
> manet mailing list
> manet@ietf.org
> https://www1.ietf.org/mailman/listinfo/manet

regards,
ryuji

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



From manet-admin@ietf.org  Sat Dec  7 18:08:47 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 SAA09449
	for <manet-archive@lists.ietf.org>; Sat, 7 Dec 2002 18:08: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 gB7N3uv06920;
	Sat, 7 Dec 2002 18:03: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 gB7MxGv06821
	for <manet@optimus.ietf.org>; Sat, 7 Dec 2002 17:59:16 -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 RAA09234
	for <manet@ietf.org>; Sat, 7 Dec 2002 17:56:16 -0500 (EST)
Received: from mail pickup service by hotmail.com with Microsoft SMTPSVC;
	 Sat, 7 Dec 2002 14:56:33 -0800
Received: from 129.119.251.10 by lw15fd.law15.hotmail.msn.com with HTTP;
	Sat, 07 Dec 2002 22:56:33 GMT
X-Originating-IP: [129.119.251.10]
From: "A A" <saeen47@hotmail.com>
To: xumingfang@yahoo.com, qi.fan@kcl.ac.uk
Cc: manet@ietf.org
Subject: Re: [manet] fixed address for MANET?
Date: Sat, 07 Dec 2002 22:56:33 +0000
Mime-Version: 1.0
Content-Type: text/plain; format=flowed
Message-ID: <F9DGCl9FopYC98Bi89Q0000607a@hotmail.com>
X-OriginalArrivalTime: 07 Dec 2002 22:56:33.0632 (UTC) FILETIME=[E37B9600:01C29E43]
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>

>1. Why do we dynamic assign the address instead of
>fix (IPV6 have enough address) a unique address for
>each MANET terminal? This ways should be very
>similar with the MAC addresses for Ethernet NIC. By
>this we can save more energy and latency.

Fix IPv6 address will sure save some energy, but latency will most probably 
remain the same, because of the fact that to configure an IPv6 properly you 
still have to rely on an router advertisement. How early you get that 
information depends on multicasting protocols used in the ad-hoc network. In 
this way it is very similar to DHCP (gateway )server working in IPv4 
environment. Therefore there will always be some delay factor present.


>2.Nearly all the paper use the IP address as the
>MANET address. IP address is become the standerd,
>isn't it?

There is nothing in ad-hoc network protocol which dictate IP address usage. 
Most probably for ad-hoc network logical names like A, B, C, or D will work 
fine, as everything boils to (selective) multicasting. But for internet 
conectivity the node would be requring a topological correct address. This 
address may be configured in the node, or ad-hoc network can continue using 
the logical address space and the gateway providing connectivity to outside 
world may implement some mechanism for address translation


Hope that helped,
Abdul





>From: Xuming Fang <xumingfang@yahoo.com>
>To: MANET Mailing List <manet@ietf.org>
>Subject: Re: [manet] fixed address for MANET?
>Date: Sat, 7 Dec 2002 02:05:31 -0800 (PST)
>
>I have the same question.
>
>X. Fang
>
>--- Qi Fan <qi.fan@kcl.ac.uk> wrote:
> > BlankHello
> >
> > Recently, I have read some papers about the address
> > configuration for MANET. Here I have some questions:
> >
> > 1. Why do we dynamic assign the address instead of
> > fix (IPV6 have enough address) a unique address for
> > each MANET terminal? This ways should be very
> > similar with the MAC addresses for Ethernet NIC. By
> > this we can save more energy and latency.
> >
> > 2.Nearly all the paper use the IP address as the
> > MANET address. IP address is become the standerd,
> > isn't it?
> >
> > Any comments? I would be very appricate for your
> > infomation.
> >
> > All the best.
> >
> > ------------------------------------
> > Qi Fan
> >
> > Center for Telecommunications Research
> > King's College London
> >
> >
> >
> >
>
>
>__________________________________________________
>Do you Yahoo!?
>Yahoo! Mail Plus - Powerful. Affordable. Sign up now.
>http://mailplus.yahoo.com
>_______________________________________________
>manet mailing list
>manet@ietf.org
>https://www1.ietf.org/mailman/listinfo/manet


_________________________________________________________________
Add photos to your e-mail with MSN 8. Get 2 months FREE*. 
http://join.msn.com/?page=features/featuredemail

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


From mailnull@www1.ietf.org  Sat Dec  7 18:21: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 SAA09826
	for <manet-archive@odin.ietf.org>; Sat, 7 Dec 2002 18:21:51 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id gB7NOKO08143
	for manet-archive@odin.ietf.org; Sat, 7 Dec 2002 18:24: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 gB7NOJv08140
	for <manet-web-archive@optimus.ietf.org>; Sat, 7 Dec 2002 18:24: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 SAA09820
	for <manet-web-archive@ietf.org>; Sat, 7 Dec 2002 18:21: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 gB7N3uv06920;
	Sat, 7 Dec 2002 18:03: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 gB7MxGv06821
	for <manet@optimus.ietf.org>; Sat, 7 Dec 2002 17:59:16 -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 RAA09234
	for <manet@ietf.org>; Sat, 7 Dec 2002 17:56:16 -0500 (EST)
Received: from mail pickup service by hotmail.com with Microsoft SMTPSVC;
	 Sat, 7 Dec 2002 14:56:33 -0800
Received: from 129.119.251.10 by lw15fd.law15.hotmail.msn.com with HTTP;
	Sat, 07 Dec 2002 22:56:33 GMT
X-Originating-IP: [129.119.251.10]
From: "A A" <saeen47@hotmail.com>
To: xumingfang@yahoo.com, qi.fan@kcl.ac.uk
Cc: manet@ietf.org
Subject: Re: [manet] fixed address for MANET?
Date: Sat, 07 Dec 2002 22:56:33 +0000
Mime-Version: 1.0
Content-Type: text/plain; format=flowed
Message-ID: <F9DGCl9FopYC98Bi89Q0000607a@hotmail.com>
X-OriginalArrivalTime: 07 Dec 2002 22:56:33.0632 (UTC) FILETIME=[E37B9600:01C29E43]
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>

>1. Why do we dynamic assign the address instead of
>fix (IPV6 have enough address) a unique address for
>each MANET terminal? This ways should be very
>similar with the MAC addresses for Ethernet NIC. By
>this we can save more energy and latency.

Fix IPv6 address will sure save some energy, but latency will most probably 
remain the same, because of the fact that to configure an IPv6 properly you 
still have to rely on an router advertisement. How early you get that 
information depends on multicasting protocols used in the ad-hoc network. In 
this way it is very similar to DHCP (gateway )server working in IPv4 
environment. Therefore there will always be some delay factor present.


>2.Nearly all the paper use the IP address as the
>MANET address. IP address is become the standerd,
>isn't it?

There is nothing in ad-hoc network protocol which dictate IP address usage. 
Most probably for ad-hoc network logical names like A, B, C, or D will work 
fine, as everything boils to (selective) multicasting. But for internet 
conectivity the node would be requring a topological correct address. This 
address may be configured in the node, or ad-hoc network can continue using 
the logical address space and the gateway providing connectivity to outside 
world may implement some mechanism for address translation


Hope that helped,
Abdul





>From: Xuming Fang <xumingfang@yahoo.com>
>To: MANET Mailing List <manet@ietf.org>
>Subject: Re: [manet] fixed address for MANET?
>Date: Sat, 7 Dec 2002 02:05:31 -0800 (PST)
>
>I have the same question.
>
>X. Fang
>
>--- Qi Fan <qi.fan@kcl.ac.uk> wrote:
> > BlankHello
> >
> > Recently, I have read some papers about the address
> > configuration for MANET. Here I have some questions:
> >
> > 1. Why do we dynamic assign the address instead of
> > fix (IPV6 have enough address) a unique address for
> > each MANET terminal? This ways should be very
> > similar with the MAC addresses for Ethernet NIC. By
> > this we can save more energy and latency.
> >
> > 2.Nearly all the paper use the IP address as the
> > MANET address. IP address is become the standerd,
> > isn't it?
> >
> > Any comments? I would be very appricate for your
> > infomation.
> >
> > All the best.
> >
> > ------------------------------------
> > Qi Fan
> >
> > Center for Telecommunications Research
> > King's College London
> >
> >
> >
> >
>
>
>__________________________________________________
>Do you Yahoo!?
>Yahoo! Mail Plus - Powerful. Affordable. Sign up now.
>http://mailplus.yahoo.com
>_______________________________________________
>manet mailing list
>manet@ietf.org
>https://www1.ietf.org/mailman/listinfo/manet


_________________________________________________________________
Add photos to your e-mail with MSN 8. Get 2 months FREE*. 
http://join.msn.com/?page=features/featuredemail

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



From mailnull@www1.ietf.org  Sat Dec  7 18:47: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 SAA10206
	for <manet-archive@odin.ietf.org>; Sat, 7 Dec 2002 18:47:16 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id gB7Nnj809268
	for manet-archive@odin.ietf.org; Sat, 7 Dec 2002 18:49: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 gB7Nnjv09265
	for <manet-web-archive@optimus.ietf.org>; Sat, 7 Dec 2002 18:49: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 SAA10193
	for <manet-web-archive@ietf.org>; Sat, 7 Dec 2002 18:46: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 gB7Nfsv09047;
	Sat, 7 Dec 2002 18:41: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 gB7NcQv08959
	for <manet@optimus.ietf.org>; Sat, 7 Dec 2002 18:38:26 -0500
Received: from pat.uio.no (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA10044
	for <manet@ietf.org>; Sat, 7 Dec 2002 18:35:26 -0500 (EST)
Received: from snapp.uio.no ([129.240.130.64])
	by pat.uio.no with esmtp (Exim 2.12 #7)
	id 18KoWY-0001EF-00
	for manet@ietf.org; Sun, 8 Dec 2002 00:38:18 +0100
Received: from sos-dhcp009.studby.uio.no ([129.240.104.39] helo=nilsnosb)
	by snapp.uio.no with smtp (Exim 2.12 #7)
	id 18KoWY-0001Or-00
	for manet@ietf.org; Sun, 8 Dec 2002 00:38:18 +0100
Message-ID: <000f01c29e49$baa9b300$2768f081@nilsnosb>
From: "Nils Agne Nordbotten" <nilsno@ifi.uio.no>
To: <manet@ietf.org>
References: <F9DGCl9FopYC98Bi89Q0000607a@hotmail.com>
Subject: Re: [manet] fixed address for MANET?
Date: Sun, 8 Dec 2002 00:38:21 +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 6.00.2720.3000
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2600.0000
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

> Fix IPv6 address will sure save some energy, but latency will most
probably
> remain the same, because of the fact that to configure an IPv6 properly
you
> still have to rely on an router advertisement. How early you get that
> information depends on multicasting protocols used in the ad-hoc network.
In
> this way it is very similar to DHCP (gateway )server working in IPv4
> environment. Therefore there will always be some delay factor present.

If MANETs were assigned a fixed IPv6 prefix, it would be possible to assign
a unique address for use within the MANET based on this prefix and a unique
interface id. If nodes wished to access the internet a second global address
would be needed however (or maybe using Mobile IP.)

Regards
Nils


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



From manet-admin@ietf.org  Sat Dec  7 18: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 SAA10307
	for <manet-archive@lists.ietf.org>; Sat, 7 Dec 2002 18:52: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 gB7Nfsv09047;
	Sat, 7 Dec 2002 18:41: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 gB7NcQv08959
	for <manet@optimus.ietf.org>; Sat, 7 Dec 2002 18:38:26 -0500
Received: from pat.uio.no (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA10044
	for <manet@ietf.org>; Sat, 7 Dec 2002 18:35:26 -0500 (EST)
Received: from snapp.uio.no ([129.240.130.64])
	by pat.uio.no with esmtp (Exim 2.12 #7)
	id 18KoWY-0001EF-00
	for manet@ietf.org; Sun, 8 Dec 2002 00:38:18 +0100
Received: from sos-dhcp009.studby.uio.no ([129.240.104.39] helo=nilsnosb)
	by snapp.uio.no with smtp (Exim 2.12 #7)
	id 18KoWY-0001Or-00
	for manet@ietf.org; Sun, 8 Dec 2002 00:38:18 +0100
Message-ID: <000f01c29e49$baa9b300$2768f081@nilsnosb>
From: "Nils Agne Nordbotten" <nilsno@ifi.uio.no>
To: <manet@ietf.org>
References: <F9DGCl9FopYC98Bi89Q0000607a@hotmail.com>
Subject: Re: [manet] fixed address for MANET?
Date: Sun, 8 Dec 2002 00:38:21 +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 6.00.2720.3000
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2600.0000
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

> Fix IPv6 address will sure save some energy, but latency will most
probably
> remain the same, because of the fact that to configure an IPv6 properly
you
> still have to rely on an router advertisement. How early you get that
> information depends on multicasting protocols used in the ad-hoc network.
In
> this way it is very similar to DHCP (gateway )server working in IPv4
> environment. Therefore there will always be some delay factor present.

If MANETs were assigned a fixed IPv6 prefix, it would be possible to assign
a unique address for use within the MANET based on this prefix and a unique
interface id. If nodes wished to access the internet a second global address
would be needed however (or maybe using Mobile IP.)

Regards
Nils


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


From manet-admin@ietf.org  Sun Dec  8 12:46: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 MAA05926
	for <manet-archive@lists.ietf.org>; Sun, 8 Dec 2002 12:46: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 gB8HfGv00811;
	Sun, 8 Dec 2002 12:41: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 gB8HWPv32542
	for <manet@optimus.ietf.org>; Sun, 8 Dec 2002 12:32:25 -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 MAA05418
	for <manet@ietf.org>; Sun, 8 Dec 2002 12:29:28 -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 JAA05260;
	Sun, 8 Dec 2002 09:32:20 -0800 (PST)
Received: (from root@localhost)
	by darkstar.iprg.nokia.com (8.11.0/8.11.0-DARKSTAR) id gB8HWJc16418;
	Sun, 8 Dec 2002 09:32:19 -0800
X-mProtect: <200212081732> Nokia Silicon Valley Messaging Protection
Received: from UNKNOWN (205.226.22.18, claiming to be "iprg.nokia.com")
	by darkstar.iprg.nokia.com smtpdXRPhfT; Sun, 08 Dec 2002 09:32:17 PST
Message-ID: <3DF381DD.60981274@iprg.nokia.com>
Date: Sun, 08 Dec 2002 09:31:09 -0800
From: Charlie Perkins <charliep@iprg.nokia.com>
Organization: Nokia
X-Mailer: Mozilla 4.75 [en]C-CCK-MCD {Nokia}  (Windows NT 5.0; U)
X-Accept-Language: en
MIME-Version: 1.0
To: A A <saeen47@hotmail.com>
CC: xumingfang@yahoo.com, qi.fan@kcl.ac.uk, manet@ietf.org
Subject: Re: [manet] fixed address for MANET?
References: <F9DGCl9FopYC98Bi89Q0000607a@hotmail.com>
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 Abdul,

A A wrote:

> >1. Why do we dynamic assign the address instead of
> >fix (IPV6 have enough address) a unique address for
> >each MANET terminal? This ways should be very
> >similar with the MAC addresses for Ethernet NIC. By
> >this we can save more energy and latency.
>
> Fix IPv6 address will sure save some energy, but latency will most probably
> remain the same, because of the fact that to configure an IPv6 properly you
> still have to rely on an router advertisement. How early you get that
> information depends on multicasting protocols used in the ad-hoc network. In
> this way it is very similar to DHCP (gateway )server working in IPv4
> environment. Therefore there will always be some delay factor present.

This is not true, depending on other assumptions.  For instance,
a mobile device may already have an IP address configured before it
enters the ad hoc network.  If there is no infrastructure, or even if
there is, the device can keep its already configured address.

> >2.Nearly all the paper use the IP address as the
> >MANET address. IP address is become the standerd,
> >isn't it?
>
> There is nothing in ad-hoc network protocol which dictate IP address usage.

That's true, but if it's not IP, it may or may not belong in the IETF.
IP-addressible devices seem very naturally suited for consideration
within the IETF.

> Most probably for ad-hoc network logical names like A, B, C, or D will work
> fine, as everything boils to (selective) multicasting.

Sure, any naming scheme can be made to work, but NOT everything
boils down to multicasting.   It depends on your assumptions.

Regards,
Charlie P.

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


From mailnull@www1.ietf.org  Sun Dec  8 13:00: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 NAA06150
	for <manet-archive@odin.ietf.org>; Sun, 8 Dec 2002 13:00:35 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id gB8I31w01429
	for manet-archive@odin.ietf.org; Sun, 8 Dec 2002 13:03: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 gB8I31v01426
	for <manet-web-archive@optimus.ietf.org>; Sun, 8 Dec 2002 13:03: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 NAA06139
	for <manet-web-archive@ietf.org>; Sun, 8 Dec 2002 13:00: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 gB8HfGv00811;
	Sun, 8 Dec 2002 12:41: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 gB8HWPv32542
	for <manet@optimus.ietf.org>; Sun, 8 Dec 2002 12:32:25 -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 MAA05418
	for <manet@ietf.org>; Sun, 8 Dec 2002 12:29:28 -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 JAA05260;
	Sun, 8 Dec 2002 09:32:20 -0800 (PST)
Received: (from root@localhost)
	by darkstar.iprg.nokia.com (8.11.0/8.11.0-DARKSTAR) id gB8HWJc16418;
	Sun, 8 Dec 2002 09:32:19 -0800
X-mProtect: <200212081732> Nokia Silicon Valley Messaging Protection
Received: from UNKNOWN (205.226.22.18, claiming to be "iprg.nokia.com")
	by darkstar.iprg.nokia.com smtpdXRPhfT; Sun, 08 Dec 2002 09:32:17 PST
Message-ID: <3DF381DD.60981274@iprg.nokia.com>
Date: Sun, 08 Dec 2002 09:31:09 -0800
From: Charlie Perkins <charliep@iprg.nokia.com>
Organization: Nokia
X-Mailer: Mozilla 4.75 [en]C-CCK-MCD {Nokia}  (Windows NT 5.0; U)
X-Accept-Language: en
MIME-Version: 1.0
To: A A <saeen47@hotmail.com>
CC: xumingfang@yahoo.com, qi.fan@kcl.ac.uk, manet@ietf.org
Subject: Re: [manet] fixed address for MANET?
References: <F9DGCl9FopYC98Bi89Q0000607a@hotmail.com>
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 Abdul,

A A wrote:

> >1. Why do we dynamic assign the address instead of
> >fix (IPV6 have enough address) a unique address for
> >each MANET terminal? This ways should be very
> >similar with the MAC addresses for Ethernet NIC. By
> >this we can save more energy and latency.
>
> Fix IPv6 address will sure save some energy, but latency will most probably
> remain the same, because of the fact that to configure an IPv6 properly you
> still have to rely on an router advertisement. How early you get that
> information depends on multicasting protocols used in the ad-hoc network. In
> this way it is very similar to DHCP (gateway )server working in IPv4
> environment. Therefore there will always be some delay factor present.

This is not true, depending on other assumptions.  For instance,
a mobile device may already have an IP address configured before it
enters the ad hoc network.  If there is no infrastructure, or even if
there is, the device can keep its already configured address.

> >2.Nearly all the paper use the IP address as the
> >MANET address. IP address is become the standerd,
> >isn't it?
>
> There is nothing in ad-hoc network protocol which dictate IP address usage.

That's true, but if it's not IP, it may or may not belong in the IETF.
IP-addressible devices seem very naturally suited for consideration
within the IETF.

> Most probably for ad-hoc network logical names like A, B, C, or D will work
> fine, as everything boils to (selective) multicasting.

Sure, any naming scheme can be made to work, but NOT everything
boils down to multicasting.   It depends on your assumptions.

Regards,
Charlie P.

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



From manet-admin@ietf.org  Sun Dec  8 16:15: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 QAA09876
	for <manet-archive@lists.ietf.org>; Sun, 8 Dec 2002 16:15: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 gB8LApv09438;
	Sun, 8 Dec 2002 16:10: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 gB8L5Xv08712
	for <manet@optimus.ietf.org>; Sun, 8 Dec 2002 16:05:33 -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 QAA09622
	for <manet@ietf.org>; Sun, 8 Dec 2002 16:02: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 NAA10746;
	Sun, 8 Dec 2002 13:05:26 -0800 (PST)
Received: (from root@localhost)
	by darkstar.iprg.nokia.com (8.11.0/8.11.0-DARKSTAR) id gB8L5Pv12994;
	Sun, 8 Dec 2002 13:05:25 -0800
X-mProtect: <200212082105> Nokia Silicon Valley Messaging Protection
Received: from UNKNOWN (205.226.22.18, claiming to be "iprg.nokia.com")
	by darkstar.iprg.nokia.com smtpd7l1vze; Sun, 08 Dec 2002 13:05:24 PST
Message-ID: <3DF3B3D0.41B8A9DF@iprg.nokia.com>
Date: Sun, 08 Dec 2002 13:04:17 -0800
From: Charlie Perkins <charliep@iprg.nokia.com>
Organization: Nokia
X-Mailer: Mozilla 4.75 [en]C-CCK-MCD {Nokia}  (Windows NT 5.0; U)
X-Accept-Language: en
MIME-Version: 1.0
To: Petar Popovski <petarp@kom.auc.dk>
CC: Mobile Ad Hoc IETF working group <manet@ietf.org>
Subject: Re: [manet] fixed address for MANET?
References: <F9DGCl9FopYC98Bi89Q0000607a@hotmail.com> <3DF381DD.60981274@iprg.nokia.com> <001e01c29ef4$bd971840$6c4ea8c0@guesthouse.auc.dk>
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 Petar,

One can certainly justify using alternative addressing schemes.
I just question whether that work is appropriate for management
within an IETF working group.  I don't question whether it is
valuable work.

Regards,
Charlie P.



Petar Popovski wrote:

>             ...............
> But, wouldn't it be more beneficial if the addresses in ad hoc networks are
> also ad hoc? For example, instead of 32 bits for IP address, the network
> address for a node would consist of log2(N) bits as unique ID + bits for
> description of services supported at some node.

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


From mailnull@www1.ietf.org  Sun Dec  8 16:29: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 QAA10027
	for <manet-archive@odin.ietf.org>; Sun, 8 Dec 2002 16:29:06 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id gB8LVY109917
	for manet-archive@odin.ietf.org; Sun, 8 Dec 2002 16:31: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 gB8LVYv09914
	for <manet-web-archive@optimus.ietf.org>; Sun, 8 Dec 2002 16:31: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 QAA10024
	for <manet-web-archive@ietf.org>; Sun, 8 Dec 2002 16:28: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 gB8LApv09438;
	Sun, 8 Dec 2002 16:10: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 gB8L5Xv08712
	for <manet@optimus.ietf.org>; Sun, 8 Dec 2002 16:05:33 -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 QAA09622
	for <manet@ietf.org>; Sun, 8 Dec 2002 16:02: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 NAA10746;
	Sun, 8 Dec 2002 13:05:26 -0800 (PST)
Received: (from root@localhost)
	by darkstar.iprg.nokia.com (8.11.0/8.11.0-DARKSTAR) id gB8L5Pv12994;
	Sun, 8 Dec 2002 13:05:25 -0800
X-mProtect: <200212082105> Nokia Silicon Valley Messaging Protection
Received: from UNKNOWN (205.226.22.18, claiming to be "iprg.nokia.com")
	by darkstar.iprg.nokia.com smtpd7l1vze; Sun, 08 Dec 2002 13:05:24 PST
Message-ID: <3DF3B3D0.41B8A9DF@iprg.nokia.com>
Date: Sun, 08 Dec 2002 13:04:17 -0800
From: Charlie Perkins <charliep@iprg.nokia.com>
Organization: Nokia
X-Mailer: Mozilla 4.75 [en]C-CCK-MCD {Nokia}  (Windows NT 5.0; U)
X-Accept-Language: en
MIME-Version: 1.0
To: Petar Popovski <petarp@kom.auc.dk>
CC: Mobile Ad Hoc IETF working group <manet@ietf.org>
Subject: Re: [manet] fixed address for MANET?
References: <F9DGCl9FopYC98Bi89Q0000607a@hotmail.com> <3DF381DD.60981274@iprg.nokia.com> <001e01c29ef4$bd971840$6c4ea8c0@guesthouse.auc.dk>
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 Petar,

One can certainly justify using alternative addressing schemes.
I just question whether that work is appropriate for management
within an IETF working group.  I don't question whether it is
valuable work.

Regards,
Charlie P.



Petar Popovski wrote:

>             ...............
> But, wouldn't it be more beneficial if the addresses in ad hoc networks are
> also ad hoc? For example, instead of 32 bits for IP address, the network
> address for a node would consist of log2(N) bits as unique ID + bits for
> description of services supported at some node.

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



From manet-admin@ietf.org  Mon Dec  9 07:00: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 HAA05486
	for <manet-archive@lists.ietf.org>; Mon, 9 Dec 2002 07:00: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 gB9Bqmv27734;
	Mon, 9 Dec 2002 06:52: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 gB9Bolv27684
	for <manet@optimus.ietf.org>; Mon, 9 Dec 2002 06:50:47 -0500
Received: from webmails.com (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id GAA05174
	for <manet@ietf.org>; Mon, 9 Dec 2002 06:47:48 -0500 (EST)
Received: (qmail 27043 invoked by uid 511); 9 Dec 2002 11:51:20 -0000
Message-ID: <20021209115120.27042.qmail@webmails.com>
Content-Type: multipart/alternative; boundary="----------=_1039434680-26915-0"
Content-Transfer-Encoding: binary
MIME-Version: 1.0
X-Mailer: MIME-tools 5.411 (Entity 5.404)
From: "moez gadri" <moez_gadri@webmails.com>
To: manet@ietf.org
Organization: WebMailS - http://www.webmails.com
Date: Mon, 9 Dec 2002 12:51:20 +0100
X-Originating-Ip: 193.95.33.18
Subject: [manet] Classification of routing protocols & proposition of new ideas
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...

------------=_1039434680-26915-0
Content-Type: text/plain
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable

Hi everybody,=0D
=0D
i'm interrested by scalable routing protocols with QoS.=0D
the scalaility is performed by using different approachs such as
clustering and virtual backbone. Can I find other approachs ? There are
simulation witch compare the performences of this approachs ? ...=0D
=0D
Considering the QoS, many metrics are proposed : bandwidght, end to end
reliability, availability of links, ... I ask for an exhaustive list of
this metrics.=0D
=0D
thanks.

____________________________________________________________________
- http://www.WebMailSPro.com - >>=20
Cr=E9er votre WebBased email pour avec votre propre nom de domaine=20


------------=_1039434680-26915-0
Content-Type: text/html
Content-Disposition: inline
Content-Transfer-Encoding: 7bit

<HTML>
<BODY BGCOLOR="FFFFFF">
<PRE>Hi everybody,

i'm interrested by scalable routing protocols with QoS.
the scalaility is performed by using different approachs such as
clustering and virtual backbone. Can I find other approachs ? There are
simulation witch compare the performences of this approachs ? ...

Considering the QoS, many metrics are proposed : bandwidght, end to end
reliability, availability of links, ... I ask for an exhaustive list of
this metrics.

thanks.

____________________________________________________________________
- <TT><A HREF="http://www.WebMailSPro.com">http://www.WebMailSPro.com</A></TT> - &gt;&gt; 
Créer votre WebBased email pour avec votre propre nom de domaine </PRE>

</BODY>
</HTML>
------------=_1039434680-26915-0--
_______________________________________________
manet mailing list
manet@ietf.org
https://www1.ietf.org/mailman/listinfo/manet


From mailnull@www1.ietf.org  Mon Dec  9 07: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 HAA05736
	for <manet-archive@odin.ietf.org>; Mon, 9 Dec 2002 07:10:23 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id gB9CCmH29094
	for manet-archive@odin.ietf.org; Mon, 9 Dec 2002 07:12: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 gB9CCmv29091
	for <manet-web-archive@optimus.ietf.org>; Mon, 9 Dec 2002 07:12: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 HAA05709
	for <manet-web-archive@ietf.org>; Mon, 9 Dec 2002 07:09: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 gB9Bqmv27734;
	Mon, 9 Dec 2002 06:52: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 gB9Bolv27684
	for <manet@optimus.ietf.org>; Mon, 9 Dec 2002 06:50:47 -0500
Received: from webmails.com (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id GAA05174
	for <manet@ietf.org>; Mon, 9 Dec 2002 06:47:48 -0500 (EST)
Received: (qmail 27043 invoked by uid 511); 9 Dec 2002 11:51:20 -0000
Message-ID: <20021209115120.27042.qmail@webmails.com>
Content-Type: multipart/alternative; boundary="----------=_1039434680-26915-0"
Content-Transfer-Encoding: binary
MIME-Version: 1.0
X-Mailer: MIME-tools 5.411 (Entity 5.404)
From: "moez gadri" <moez_gadri@webmails.com>
To: manet@ietf.org
Organization: WebMailS - http://www.webmails.com
Date: Mon, 9 Dec 2002 12:51:20 +0100
X-Originating-Ip: 193.95.33.18
Subject: [manet] Classification of routing protocols & proposition of new ideas
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...

------------=_1039434680-26915-0
Content-Type: text/plain
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable

Hi everybody,=0D
=0D
i'm interrested by scalable routing protocols with QoS.=0D
the scalaility is performed by using different approachs such as
clustering and virtual backbone. Can I find other approachs ? There are
simulation witch compare the performences of this approachs ? ...=0D
=0D
Considering the QoS, many metrics are proposed : bandwidght, end to end
reliability, availability of links, ... I ask for an exhaustive list of
this metrics.=0D
=0D
thanks.

____________________________________________________________________
- http://www.WebMailSPro.com - >>=20
Cr=E9er votre WebBased email pour avec votre propre nom de domaine=20


------------=_1039434680-26915-0
Content-Type: text/html
Content-Disposition: inline
Content-Transfer-Encoding: 7bit

<HTML>
<BODY BGCOLOR="FFFFFF">
<PRE>Hi everybody,

i'm interrested by scalable routing protocols with QoS.
the scalaility is performed by using different approachs such as
clustering and virtual backbone. Can I find other approachs ? There are
simulation witch compare the performences of this approachs ? ...

Considering the QoS, many metrics are proposed : bandwidght, end to end
reliability, availability of links, ... I ask for an exhaustive list of
this metrics.

thanks.

____________________________________________________________________
- <TT><A HREF="http://www.WebMailSPro.com">http://www.WebMailSPro.com</A></TT> - &gt;&gt; 
Créer votre WebBased email pour avec votre propre nom de domaine </PRE>

</BODY>
</HTML>
------------=_1039434680-26915-0--
_______________________________________________
manet mailing list
manet@ietf.org
https://www1.ietf.org/mailman/listinfo/manet



From mailnull@www1.ietf.org  Mon Dec  9 08:55: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 IAA09258
	for <manet-archive@odin.ietf.org>; Mon, 9 Dec 2002 08:55:19 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id gB9DvjO02838
	for manet-archive@odin.ietf.org; Mon, 9 Dec 2002 08: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 gB9Dvjv02835
	for <manet-web-archive@optimus.ietf.org>; Mon, 9 Dec 2002 08: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 IAA09217
	for <manet-web-archive@ietf.org>; Mon, 9 Dec 2002 08:54: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 gB9DnBv02538;
	Mon, 9 Dec 2002 08:49: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 gB9DlNv02469
	for <manet@optimus.ietf.org>; Mon, 9 Dec 2002 08:47:23 -0500
Received: from mail.rz.uni-ulm.de (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA08810
	for <manet@ietf.org>; Mon, 9 Dec 2002 08:44:25 -0500 (EST)
Received: from informatik.uni-ulm.de (wlan236-204.wlan.uni-ulm.de [134.60.236.204])
	by mail.rz.uni-ulm.de (8.12.6/8.12.6) with ESMTP id gB9DlILb013556
	for <manet@ietf.org>; Mon, 9 Dec 2002 14:47:18 +0100 (MET)
Message-ID: <3DF49EC6.5080102@informatik.uni-ulm.de>
Date: Mon, 09 Dec 2002 14:46:46 +0100
From: Frank Kargl <frank.kargl@informatik.uni-ulm.de>
Organization: University of Ulm
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.2.1) Gecko/20021130
X-Accept-Language: de-de, de, en-us, en
MIME-Version: 1.0
To: manet@ietf.org
Subject: Re: [manet] Node misbehavior and source routing
References: <D18F53ABCD79C14495301518A54E52200AC1E0@xch-ne-01.ne.nos.boeing.com>
In-Reply-To: <D18F53ABCD79C14495301518A54E52200AC1E0@xch-ne-01.ne.nos.boeing.com>
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

Manfredi, Albert E wrote:
> Sherif E. Mohamed Khattab wrote:
>> Regarding the problem of mitigating node misbehavior in ad hoc
>> networks (a "misbehaving" node participates in routing but drops
>> data packets.) Most of the current solutions consider source
>> routing protocols (e.g., DSR). Is there a specific reason for that?
> 
> The direct answer I would give to this question is that with source
> routing, a MANET protocol does not need to depend on any special
> attributes of the IP addresses of the member hosts. The IP addresses
> are arbitrary numbers from a flat address space, allowing tha MANET
> hosts, for example, to use their own home IP addresses and to use
> Mobile IP as it is written.

As long as a routing protocol supports host routes (as do practically
all of the MANET routing protocols incl. AODV, OLSR ...), the IP address
can be treated as a flat 32-bit ID. This is no special property of
source-routing protocols.

The structure of an IP address becomes relevant when automatic address
assignment or an (or even multiple) Internet gateway(s) come into play.

Regards ... Frank

-- 
-----------------------------------------------------------------------
   Frank Kargl          Multimedia Computing, University of Ulm, Germany
   Mail:frank.kargl@informatik.uni-ulm.de http://www.uni-ulm.de/~fkargl/
-----------------------------------------------------------------------
     Use the SOURCE, Luke !  I feel a great disturbance in the SOURCE.
              But beware of the Microsoft side of the SOURCE !


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



From manet-admin@ietf.org  Mon Dec  9 09:00: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 JAA09616
	for <manet-archive@lists.ietf.org>; Mon, 9 Dec 2002 09:00: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 gB9DnBv02538;
	Mon, 9 Dec 2002 08:49: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 gB9DlNv02469
	for <manet@optimus.ietf.org>; Mon, 9 Dec 2002 08:47:23 -0500
Received: from mail.rz.uni-ulm.de (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA08810
	for <manet@ietf.org>; Mon, 9 Dec 2002 08:44:25 -0500 (EST)
Received: from informatik.uni-ulm.de (wlan236-204.wlan.uni-ulm.de [134.60.236.204])
	by mail.rz.uni-ulm.de (8.12.6/8.12.6) with ESMTP id gB9DlILb013556
	for <manet@ietf.org>; Mon, 9 Dec 2002 14:47:18 +0100 (MET)
Message-ID: <3DF49EC6.5080102@informatik.uni-ulm.de>
Date: Mon, 09 Dec 2002 14:46:46 +0100
From: Frank Kargl <frank.kargl@informatik.uni-ulm.de>
Organization: University of Ulm
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.2.1) Gecko/20021130
X-Accept-Language: de-de, de, en-us, en
MIME-Version: 1.0
To: manet@ietf.org
Subject: Re: [manet] Node misbehavior and source routing
References: <D18F53ABCD79C14495301518A54E52200AC1E0@xch-ne-01.ne.nos.boeing.com>
In-Reply-To: <D18F53ABCD79C14495301518A54E52200AC1E0@xch-ne-01.ne.nos.boeing.com>
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

Manfredi, Albert E wrote:
> Sherif E. Mohamed Khattab wrote:
>> Regarding the problem of mitigating node misbehavior in ad hoc
>> networks (a "misbehaving" node participates in routing but drops
>> data packets.) Most of the current solutions consider source
>> routing protocols (e.g., DSR). Is there a specific reason for that?
> 
> The direct answer I would give to this question is that with source
> routing, a MANET protocol does not need to depend on any special
> attributes of the IP addresses of the member hosts. The IP addresses
> are arbitrary numbers from a flat address space, allowing tha MANET
> hosts, for example, to use their own home IP addresses and to use
> Mobile IP as it is written.

As long as a routing protocol supports host routes (as do practically
all of the MANET routing protocols incl. AODV, OLSR ...), the IP address
can be treated as a flat 32-bit ID. This is no special property of
source-routing protocols.

The structure of an IP address becomes relevant when automatic address
assignment or an (or even multiple) Internet gateway(s) come into play.

Regards ... Frank

-- 
-----------------------------------------------------------------------
   Frank Kargl          Multimedia Computing, University of Ulm, Germany
   Mail:frank.kargl@informatik.uni-ulm.de http://www.uni-ulm.de/~fkargl/
-----------------------------------------------------------------------
     Use the SOURCE, Luke !  I feel a great disturbance in the SOURCE.
              But beware of the Microsoft side of the SOURCE !


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


From manet-admin@ietf.org  Mon Dec  9 09:09: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 JAA10089
	for <manet-archive@lists.ietf.org>; Mon, 9 Dec 2002 09:09: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 gB9E4Zv03171;
	Mon, 9 Dec 2002 09:04: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 gB9Dxmv02961
	for <manet@optimus.ietf.org>; Mon, 9 Dec 2002 08:59:48 -0500
Received: from web14611.mail.yahoo.com (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id IAA09320
	for <manet@ietf.org>; Mon, 9 Dec 2002 08:56:51 -0500 (EST)
Message-ID: <20021209135944.43073.qmail@web14611.mail.yahoo.com>
Received: from [193.95.33.18] by web14611.mail.yahoo.com via HTTP; Mon, 09 Dec 2002 14:59:44 CET
Date: Mon, 9 Dec 2002 14:59: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-835001199-1039442384=:42508"
Content-Transfer-Encoding: 8bit
Subject: [manet] threats 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-835001199-1039442384=:42508
Content-Type: text/plain; charset=iso-8859-1
Content-Transfer-Encoding: 8bit


hi everybody,

i work on seurity in ad hoc networks and i want to know all threats (dangers, attacks concerning applications, routing.....)concerning this type of network. 

any help will be appreciated

best regards

 


---------------------------------
Yahoo! Sorteos
Consulta si tu número ha sido premiado
--0-835001199-1039442384=:42508
Content-Type: text/html; charset=iso-8859-1
Content-Transfer-Encoding: 8bit

<P>hi everybody,</P>
<P>i work on&nbsp;seurity in ad hoc networks and i want to know all threats (dangers, attacks concerning applications, routing.....)concerning this type of network. </P>
<P>any help will be appreciated</P>
<P>best regards</P>
<P>&nbsp;</P><p><hr size=1><font face=arial,helvetica size="-1"><b>Yahoo! Sorteos</b>
<br><a href=http://es.rd.yahoo.com/mail_es/tagline/lottery/*http://es.lottery.yahoo.com/><b>Consulta si tu número ha sido premiado</b></a></font>
--0-835001199-1039442384=:42508--
_______________________________________________
manet mailing list
manet@ietf.org
https://www1.ietf.org/mailman/listinfo/manet


From mailnull@www1.ietf.org  Mon Dec  9 09:19: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 JAA10414
	for <manet-archive@odin.ietf.org>; Mon, 9 Dec 2002 09:19:04 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id gB9ELVd04552
	for manet-archive@odin.ietf.org; Mon, 9 Dec 2002 09:21: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 gB9ELVv04549
	for <manet-web-archive@optimus.ietf.org>; Mon, 9 Dec 2002 09:21: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 JAA10395
	for <manet-web-archive@ietf.org>; Mon, 9 Dec 2002 09:18: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 gB9E4Zv03171;
	Mon, 9 Dec 2002 09:04: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 gB9Dxmv02961
	for <manet@optimus.ietf.org>; Mon, 9 Dec 2002 08:59:48 -0500
Received: from web14611.mail.yahoo.com (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id IAA09320
	for <manet@ietf.org>; Mon, 9 Dec 2002 08:56:51 -0500 (EST)
Message-ID: <20021209135944.43073.qmail@web14611.mail.yahoo.com>
Received: from [193.95.33.18] by web14611.mail.yahoo.com via HTTP; Mon, 09 Dec 2002 14:59:44 CET
Date: Mon, 9 Dec 2002 14:59: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-835001199-1039442384=:42508"
Content-Transfer-Encoding: 8bit
Subject: [manet] threats 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-835001199-1039442384=:42508
Content-Type: text/plain; charset=iso-8859-1
Content-Transfer-Encoding: 8bit


hi everybody,

i work on seurity in ad hoc networks and i want to know all threats (dangers, attacks concerning applications, routing.....)concerning this type of network. 

any help will be appreciated

best regards

 


---------------------------------
Yahoo! Sorteos
Consulta si tu número ha sido premiado
--0-835001199-1039442384=:42508
Content-Type: text/html; charset=iso-8859-1
Content-Transfer-Encoding: 8bit

<P>hi everybody,</P>
<P>i work on&nbsp;seurity in ad hoc networks and i want to know all threats (dangers, attacks concerning applications, routing.....)concerning this type of network. </P>
<P>any help will be appreciated</P>
<P>best regards</P>
<P>&nbsp;</P><p><hr size=1><font face=arial,helvetica size="-1"><b>Yahoo! Sorteos</b>
<br><a href=http://es.rd.yahoo.com/mail_es/tagline/lottery/*http://es.lottery.yahoo.com/><b>Consulta si tu número ha sido premiado</b></a></font>
--0-835001199-1039442384=:42508--
_______________________________________________
manet mailing list
manet@ietf.org
https://www1.ietf.org/mailman/listinfo/manet



From mailnull@www1.ietf.org  Mon Dec  9 13:34: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 NAA23655
	for <manet-archive@odin.ietf.org>; Mon, 9 Dec 2002 13:34:28 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id gB9IauZ21715
	for manet-archive@odin.ietf.org; Mon, 9 Dec 2002 13:36: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 gB9Iauv21712
	for <manet-web-archive@optimus.ietf.org>; Mon, 9 Dec 2002 13:36: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 NAA23646
	for <manet-web-archive@ietf.org>; Mon, 9 Dec 2002 13:33: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 gB9ISWv21286;
	Mon, 9 Dec 2002 13:28: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 gB9IOEv21145
	for <manet@optimus.ietf.org>; Mon, 9 Dec 2002 13:24:14 -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 NAA23127
	for <manet@ietf.org>; Mon, 9 Dec 2002 13:21:15 -0500 (EST)
Received:  from qifan (EE189.eee.kcl.ac.uk [137.73.11.245])
	by angelo.kcl.ac.uk  with SMTP id gB9ILfeO023974
	for <manet@ietf.org>; Mon, 9 Dec 2002 18:21:41 GMT
Message-ID: <004401c29faf$fbf229c0$f50b4989@qifan>
From: "Qi Fan" <qi.fan@kcl.ac.uk>
To: "MANET Mailing List" <manet@ietf.org>
Subject: Fw: [manet] fixed address for MANET?
Date: Mon, 9 Dec 2002 18:22:51 -0000
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
X-MailScanner: Found to be clean
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


Warm regards, and have a nice day!

Boris
------------------------------------
Qi Fan

Center for Telecommunications Research
King's College London

----- Original Message -----
From: "Nils Agne Nordbotten" <nilsno@ifi.uio.no>
To: "Qi Fan" <qi.fan@kcl.ac.uk>
Sent: Monday, December 09, 2002 5:20 PM
Subject: Re: [manet] fixed address for MANET?


> Hi,
>
> I think maybe this email was intended for the mailinglist, and not only
for
> me.
>
> ----- Original Message -----
> From: "Qi Fan" <qi.fan@kcl.ac.uk>
> To: "Nils Agne Nordbotten" <nilsno@ifi.uio.no>
> Sent: Monday, December 09, 2002 4:52 PM
> Subject: Re: [manet] fixed address for MANET?
>
>
> > If we assign a fixed IPv6 prefix for MANET nodes, will that destory the
> > hierarchy of the IPv6? Because the IP address is a hierarchical address
> > system, however, the MANET can move to wherever they want. Can we use
the
> > mobile IP to solve it?
>
> Because an address generated from a fixed MANET IPv6 prefix would only be
> used within the MANET itself, I don`t think it destroys the IPv6 address
> hirearchy. For the same reason it should not matter if the MANET moves.
>
> > I am quite agree with Ryuj's comments: The node may not start MIP6
> operation
> > (sending BU, etc) unless it communicates with the global Internet. Also
i
> > think the permanent address will be assigned to MANET should be 'MANET
> > Address' but IP address. Is that right?
>
> I don`t think I understand this question completely, so if it was meant
for
> me please explain.
>
>
> Regards
> Nils
>
>

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



From manet-admin@ietf.org  Mon Dec  9 13:38: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 NAA23868
	for <manet-archive@lists.ietf.org>; Mon, 9 Dec 2002 13:38: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 gB9ISWv21286;
	Mon, 9 Dec 2002 13:28: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 gB9IOEv21145
	for <manet@optimus.ietf.org>; Mon, 9 Dec 2002 13:24:14 -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 NAA23127
	for <manet@ietf.org>; Mon, 9 Dec 2002 13:21:15 -0500 (EST)
Received:  from qifan (EE189.eee.kcl.ac.uk [137.73.11.245])
	by angelo.kcl.ac.uk  with SMTP id gB9ILfeO023974
	for <manet@ietf.org>; Mon, 9 Dec 2002 18:21:41 GMT
Message-ID: <004401c29faf$fbf229c0$f50b4989@qifan>
From: "Qi Fan" <qi.fan@kcl.ac.uk>
To: "MANET Mailing List" <manet@ietf.org>
Subject: Fw: [manet] fixed address for MANET?
Date: Mon, 9 Dec 2002 18:22:51 -0000
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
X-MailScanner: Found to be clean
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


Warm regards, and have a nice day!

Boris
------------------------------------
Qi Fan

Center for Telecommunications Research
King's College London

----- Original Message -----
From: "Nils Agne Nordbotten" <nilsno@ifi.uio.no>
To: "Qi Fan" <qi.fan@kcl.ac.uk>
Sent: Monday, December 09, 2002 5:20 PM
Subject: Re: [manet] fixed address for MANET?


> Hi,
>
> I think maybe this email was intended for the mailinglist, and not only
for
> me.
>
> ----- Original Message -----
> From: "Qi Fan" <qi.fan@kcl.ac.uk>
> To: "Nils Agne Nordbotten" <nilsno@ifi.uio.no>
> Sent: Monday, December 09, 2002 4:52 PM
> Subject: Re: [manet] fixed address for MANET?
>
>
> > If we assign a fixed IPv6 prefix for MANET nodes, will that destory the
> > hierarchy of the IPv6? Because the IP address is a hierarchical address
> > system, however, the MANET can move to wherever they want. Can we use
the
> > mobile IP to solve it?
>
> Because an address generated from a fixed MANET IPv6 prefix would only be
> used within the MANET itself, I don`t think it destroys the IPv6 address
> hirearchy. For the same reason it should not matter if the MANET moves.
>
> > I am quite agree with Ryuj's comments: The node may not start MIP6
> operation
> > (sending BU, etc) unless it communicates with the global Internet. Also
i
> > think the permanent address will be assigned to MANET should be 'MANET
> > Address' but IP address. Is that right?
>
> I don`t think I understand this question completely, so if it was meant
for
> me please explain.
>
>
> Regards
> Nils
>
>

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


From manet-admin@ietf.org  Mon Dec  9 21:23: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 VAA13638
	for <manet-archive@lists.ietf.org>; Mon, 9 Dec 2002 21:23: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 gBA2I7v17083;
	Mon, 9 Dec 2002 21:18: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 gBA2Fov17022
	for <manet@optimus.ietf.org>; Mon, 9 Dec 2002 21:15:50 -0500
Received: from scutsv39.scut.edu.cn (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id VAA13475
	for <manet@ietf.org>; Mon, 9 Dec 2002 21:12:45 -0500 (EST)
From: jlshi@scut.edu.cn
Received: from smtp.scut.edu.cn (smtp.scut.edu.cn [202.38.193.66])
	by scutsv39.scut.edu.cn (8.9.3/8.9.3) with ESMTP id KAA29194
	for <manet@ietf.org>; Tue, 10 Dec 2002 10:13:59 +0800 (CST)
Received: from letterbox.scut.edu.cn (mail.scut.edu.cn [202.38.193.69])
	by smtp.scut.edu.cn (8.12.3/8.12.3) with ESMTP id gBA2JCrD016786
	for <manet@ietf.org>; Tue, 10 Dec 2002 10:19:12 +0800 (CST)
Received: from ps ([202.112.17.61])
	by letterbox.scut.edu.cn (8.12.2/8.12.2) with ESMTP id gBA2Dwq9007967
	for <manet@ietf.org>; Tue, 10 Dec 2002 10:13:58 +0800 (CST)
Message-ID: <1888443.1039486441025.JavaMail.crm@ps>
Date: Tue, 10 Dec 2002 10:14:00 +0800 (HKT)
To: manet@ietf.org
Subject: Re:Re: [manet] fixed address for MANET?
Mime-Version: 1.0
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,
>
>> >1. Why do we dynamic assign the address instead of
>> >fix (IPV6 have enough address) a unique address for
>> >each MANET terminal? 

first  ad hoc network can use as a tool to access internet.the dynamic address can provide a convenient way.
Second manet's address configuration become more quick.
that my opinion.



This ways should be very
>> >similar with the MAC addresses for Ethernet NIC. By
>> >this we can save more energy and latency.
>>
>> Fix IPv6 address will sure save some energy, but latency will most probably
>> remain the same, because of the fact that to configure an IPv6 properly you
>> still have to rely on an router advertisement. How early you get that
>> information depends on multicasting protocols used in the ad-hoc network. In
>> this way it is very similar to DHCP (gateway )server working in IPv4
>> environment. Therefore there will always be some delay factor present.
>
>This is not true, depending on other assumptions.  For instance,
>a mobile device may already have an IP address configured before it
>enters the ad hoc network.  If there is no infrastructure, or even if
>there is, the device can keep its already configured address.
>
>> >2.Nearly all the paper use the IP address as the
>> >MANET address. IP address is become the standerd,
>> >isn't it?
>>
>> There is nothing in ad-hoc network protocol which dictate IP address usage.
>
>That's true, but if it's not IP, it may or may not belong in the IETF.
>IP-addressible devices seem very naturally suited for consideration
>within the IETF.
>
>> Most probably for ad-hoc network logical names like A, B, C, or D will work
>> fine, as everything boils to (selective) multicasting.
>
>Sure, any naming scheme can be made to work, but NOT everything
>boils down to multicasting.   It depends on your assumptions.
>
>Regards,
>Charlie P.
>
>_______________________________________________
>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 Dec  9 21:34: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 VAA14041
	for <manet-archive@odin.ietf.org>; Mon, 9 Dec 2002 21:34:48 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id gBA2bK818268
	for manet-archive@odin.ietf.org; Mon, 9 Dec 2002 21:37: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 gBA2bKv18265
	for <manet-web-archive@optimus.ietf.org>; Mon, 9 Dec 2002 21:37: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 VAA13988
	for <manet-web-archive@ietf.org>; Mon, 9 Dec 2002 21:34: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 gBA2I7v17083;
	Mon, 9 Dec 2002 21:18: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 gBA2Fov17022
	for <manet@optimus.ietf.org>; Mon, 9 Dec 2002 21:15:50 -0500
Received: from scutsv39.scut.edu.cn (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id VAA13475
	for <manet@ietf.org>; Mon, 9 Dec 2002 21:12:45 -0500 (EST)
From: jlshi@scut.edu.cn
Received: from smtp.scut.edu.cn (smtp.scut.edu.cn [202.38.193.66])
	by scutsv39.scut.edu.cn (8.9.3/8.9.3) with ESMTP id KAA29194
	for <manet@ietf.org>; Tue, 10 Dec 2002 10:13:59 +0800 (CST)
Received: from letterbox.scut.edu.cn (mail.scut.edu.cn [202.38.193.69])
	by smtp.scut.edu.cn (8.12.3/8.12.3) with ESMTP id gBA2JCrD016786
	for <manet@ietf.org>; Tue, 10 Dec 2002 10:19:12 +0800 (CST)
Received: from ps ([202.112.17.61])
	by letterbox.scut.edu.cn (8.12.2/8.12.2) with ESMTP id gBA2Dwq9007967
	for <manet@ietf.org>; Tue, 10 Dec 2002 10:13:58 +0800 (CST)
Message-ID: <1888443.1039486441025.JavaMail.crm@ps>
Date: Tue, 10 Dec 2002 10:14:00 +0800 (HKT)
To: manet@ietf.org
Subject: Re:Re: [manet] fixed address for MANET?
Mime-Version: 1.0
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,
>
>> >1. Why do we dynamic assign the address instead of
>> >fix (IPV6 have enough address) a unique address for
>> >each MANET terminal? 

first  ad hoc network can use as a tool to access internet.the dynamic address can provide a convenient way.
Second manet's address configuration become more quick.
that my opinion.



This ways should be very
>> >similar with the MAC addresses for Ethernet NIC. By
>> >this we can save more energy and latency.
>>
>> Fix IPv6 address will sure save some energy, but latency will most probably
>> remain the same, because of the fact that to configure an IPv6 properly you
>> still have to rely on an router advertisement. How early you get that
>> information depends on multicasting protocols used in the ad-hoc network. In
>> this way it is very similar to DHCP (gateway )server working in IPv4
>> environment. Therefore there will always be some delay factor present.
>
>This is not true, depending on other assumptions.  For instance,
>a mobile device may already have an IP address configured before it
>enters the ad hoc network.  If there is no infrastructure, or even if
>there is, the device can keep its already configured address.
>
>> >2.Nearly all the paper use the IP address as the
>> >MANET address. IP address is become the standerd,
>> >isn't it?
>>
>> There is nothing in ad-hoc network protocol which dictate IP address usage.
>
>That's true, but if it's not IP, it may or may not belong in the IETF.
>IP-addressible devices seem very naturally suited for consideration
>within the IETF.
>
>> Most probably for ad-hoc network logical names like A, B, C, or D will work
>> fine, as everything boils to (selective) multicasting.
>
>Sure, any naming scheme can be made to work, but NOT everything
>boils down to multicasting.   It depends on your assumptions.
>
>Regards,
>Charlie P.
>
>_______________________________________________
>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 Dec  9 23:04: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 XAA16153
	for <manet-archive@odin.ietf.org>; Mon, 9 Dec 2002 23:04:10 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id gBA46gJ22162
	for manet-archive@odin.ietf.org; Mon, 9 Dec 2002 23:06: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 gBA46gv22159
	for <manet-web-archive@optimus.ietf.org>; Mon, 9 Dec 2002 23:06:42 -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 XAA16150
	for <manet-web-archive@ietf.org>; Mon, 9 Dec 2002 23:03: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 gBA3w8v21713;
	Mon, 9 Dec 2002 22: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 gBA3upv21674
	for <manet@optimus.ietf.org>; Mon, 9 Dec 2002 22:56:51 -0500
Received: from pisces.katto.comm.waseda.ac.jp (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id WAA15921
	for <manet@ietf.org>; Mon, 9 Dec 2002 22:53:48 -0500 (EST)
Received: from b (trio3 [133.9.250.207])
	by pisces.katto.comm.waseda.ac.jp (8.9.3/3.7W) with SMTP id MAA16045
	for <manet@ietf.org>; Tue, 10 Dec 2002 12:56:40 +0900
Message-ID: <003901c2a000$9e873360$0d00a8c0@katto.comm.waseda.ac.jp>
From: "Yusuke Sakurai" <sakurai@katto.comm.waseda.ac.jp>
To: <manet@ietf.org>
Date: Tue, 10 Dec 2002 13:00:03 +0900
MIME-Version: 1.0
Content-Type: text/plain;
	charset="utf-7"
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] About Local Repair(AODV)
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 all,
I'm a student and I'm curretly studying about AODV. I want to ask one
question.
In AODV specification, how many times does the upstream node with link break
send RREQ, when local repair occurs?
ns-2 uses about three, but the draft doesn't seem to say anything about
that.
I think this parameter is critical for the local repair performance.

Best regards,


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



From manet-admin@ietf.org  Mon Dec  9 23:10: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 XAA16233
	for <manet-archive@lists.ietf.org>; Mon, 9 Dec 2002 23:10: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 gBA3w8v21713;
	Mon, 9 Dec 2002 22: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 gBA3upv21674
	for <manet@optimus.ietf.org>; Mon, 9 Dec 2002 22:56:51 -0500
Received: from pisces.katto.comm.waseda.ac.jp (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id WAA15921
	for <manet@ietf.org>; Mon, 9 Dec 2002 22:53:48 -0500 (EST)
Received: from b (trio3 [133.9.250.207])
	by pisces.katto.comm.waseda.ac.jp (8.9.3/3.7W) with SMTP id MAA16045
	for <manet@ietf.org>; Tue, 10 Dec 2002 12:56:40 +0900
Message-ID: <003901c2a000$9e873360$0d00a8c0@katto.comm.waseda.ac.jp>
From: "Yusuke Sakurai" <sakurai@katto.comm.waseda.ac.jp>
To: <manet@ietf.org>
Date: Tue, 10 Dec 2002 13:00:03 +0900
MIME-Version: 1.0
Content-Type: text/plain;
	charset="utf-7"
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] About Local Repair(AODV)
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 all,
I'm a student and I'm curretly studying about AODV. I want to ask one
question.
In AODV specification, how many times does the upstream node with link break
send RREQ, when local repair occurs?
ns-2 uses about three, but the draft doesn't seem to say anything about
that.
I think this parameter is critical for the local repair performance.

Best regards,


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


From manet-admin@ietf.org  Tue Dec 10 03:45: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 DAA01706
	for <manet-archive@lists.ietf.org>; Tue, 10 Dec 2002 03:45: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 gBA8dUv13852;
	Tue, 10 Dec 2002 03:39: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 gBA8bxv13784
	for <manet@optimus.ietf.org>; Tue, 10 Dec 2002 03:37:59 -0500
Received: from sm212.163.com (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id DAA01575
	for <manet@ietf.org>; Tue, 10 Dec 2002 03:34:33 -0500 (EST)
Received: from localhost (localhost [127.0.0.1])
	by sm212.163.com (Postfix) with SMTP id 286E61C6ADDB2
	for <manet@ietf.org>; Tue, 10 Dec 2002 16:37:22 +0800 (CST)
Received: from hellsun (unknown [202.112.101.162])
	by 192.168.1.212 (Coremail) with SMTP id fVEBAKCn9T3NFmWi.1
	for <manet@ietf.org>; Tue, 10 Dec 2002 16:37:22 +0800 (CST)
Date: Tue, 10 Dec 2002 16:44:15 +0800
From: "=?GB2312?Q?=CB=EF=C1=C1?=" <sun7927@163.com>
To: manet <manet@ietf.org>
X-mailer: Foxmail 4.1 [cn]
Mime-Version: 1.0
Content-Type: text/plain;
      charset="GB2312"
Content-Transfer-Encoding: 7bit
Message-Id: <20021210083722.286E61C6ADDB2@sm212.163.com>
Content-Transfer-Encoding: 7bit
Subject: [manet] how about the bandwidth allocation issue in ad hoc?
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,
	
	I am becoming interesting in the bandwidth allocation issue in ad hoc networks, but I don't know the  evolvement of this issue, can anyone tell me the detail? 
	Thanks!


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


From mailnull@www1.ietf.org  Tue Dec 10 03:57: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 DAA01976
	for <manet-archive@odin.ietf.org>; Tue, 10 Dec 2002 03:57:03 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id gBA8xdt14571
	for manet-archive@odin.ietf.org; Tue, 10 Dec 2002 03:59: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 gBA8xdv14568
	for <manet-web-archive@optimus.ietf.org>; Tue, 10 Dec 2002 03:59: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 DAA01963
	for <manet-web-archive@ietf.org>; Tue, 10 Dec 2002 03:56: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 gBA8dUv13852;
	Tue, 10 Dec 2002 03:39: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 gBA8bxv13784
	for <manet@optimus.ietf.org>; Tue, 10 Dec 2002 03:37:59 -0500
Received: from sm212.163.com (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id DAA01575
	for <manet@ietf.org>; Tue, 10 Dec 2002 03:34:33 -0500 (EST)
Received: from localhost (localhost [127.0.0.1])
	by sm212.163.com (Postfix) with SMTP id 286E61C6ADDB2
	for <manet@ietf.org>; Tue, 10 Dec 2002 16:37:22 +0800 (CST)
Received: from hellsun (unknown [202.112.101.162])
	by 192.168.1.212 (Coremail) with SMTP id fVEBAKCn9T3NFmWi.1
	for <manet@ietf.org>; Tue, 10 Dec 2002 16:37:22 +0800 (CST)
Date: Tue, 10 Dec 2002 16:44:15 +0800
From: "=?GB2312?Q?=CB=EF=C1=C1?=" <sun7927@163.com>
To: manet <manet@ietf.org>
X-mailer: Foxmail 4.1 [cn]
Mime-Version: 1.0
Content-Type: text/plain;
      charset="GB2312"
Content-Transfer-Encoding: 7bit
Message-Id: <20021210083722.286E61C6ADDB2@sm212.163.com>
Content-Transfer-Encoding: 7bit
Subject: [manet] how about the bandwidth allocation issue in ad hoc?
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,
	
	I am becoming interesting in the bandwidth allocation issue in ad hoc networks, but I don't know the  evolvement of this issue, can anyone tell me the detail? 
	Thanks!


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



From mailnull@www1.ietf.org  Tue Dec 10 12:25: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 MAA14577
	for <manet-archive@odin.ietf.org>; Tue, 10 Dec 2002 12:25:23 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id gBAHRoM13914
	for manet-archive@odin.ietf.org; Tue, 10 Dec 2002 12:27: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 gBAHRov13911
	for <manet-web-archive@optimus.ietf.org>; Tue, 10 Dec 2002 12:27: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 MAA14550
	for <manet-web-archive@ietf.org>; Tue, 10 Dec 2002 12:24: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 gBAHKPv13638;
	Tue, 10 Dec 2002 12:20: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 gBAHIAv13446
	for <manet@optimus.ietf.org>; Tue, 10 Dec 2002 12:18:10 -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 MAA14202
	for <manet@ietf.org>; Tue, 10 Dec 2002 12:15:11 -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 gBAHI1m16468;
	Tue, 10 Dec 2002 09:18:01 -0800 (PST)
Message-Id: <200212101718.gBAHI1m16468@letters.cs.ucsb.edu>
Date: Tue, 10 Dec 2002 09:18:01 -0800 (PST)
From: "Elizabeth M. Belding-Royer" <ebelding@cs.ucsb.edu>
Reply-To: "Elizabeth M. Belding-Royer" <ebelding@cs.ucsb.edu>
Subject: Re: [manet] About Local Repair(AODV)
To: sakurai@katto.comm.waseda.ac.jp
Cc: manet@ietf.org
MIME-Version: 1.0
Content-Type: TEXT/plain; charset=us-ascii
Content-MD5: scLbcj1DjTbxSAkKkpgtJQ==
X-Mailer: dtmail 1.3.0 @(#)CDE Version 1.3.5 SunOS 5.7 sun4u sparc 
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,

Section 5.12 of the draft recommendations that local repair only
be attempted once.  If it is not successful, an RERR should be
sent to the source(s) of the route.

Elizabeth


~> 
~> Dear all,
~> I'm a student and I'm curretly studying about AODV. I want to ask one
~> question.
~> In AODV specification, how many times does the upstream node with link break
~> send RREQ, when local repair occurs?
~> ns-2 uses about three, but the draft doesn't seem to say anything about
~> that.
~> I think this parameter is critical for the local repair performance.
~> 
~> Best regards,
~> 
~> 
~> _______________________________________________
~> 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 Dec 10 12:32: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 MAA14773
	for <manet-archive@lists.ietf.org>; Tue, 10 Dec 2002 12:32: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 gBAHKPv13638;
	Tue, 10 Dec 2002 12:20: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 gBAHIAv13446
	for <manet@optimus.ietf.org>; Tue, 10 Dec 2002 12:18:10 -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 MAA14202
	for <manet@ietf.org>; Tue, 10 Dec 2002 12:15:11 -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 gBAHI1m16468;
	Tue, 10 Dec 2002 09:18:01 -0800 (PST)
Message-Id: <200212101718.gBAHI1m16468@letters.cs.ucsb.edu>
Date: Tue, 10 Dec 2002 09:18:01 -0800 (PST)
From: "Elizabeth M. Belding-Royer" <ebelding@cs.ucsb.edu>
Reply-To: "Elizabeth M. Belding-Royer" <ebelding@cs.ucsb.edu>
Subject: Re: [manet] About Local Repair(AODV)
To: sakurai@katto.comm.waseda.ac.jp
Cc: manet@ietf.org
MIME-Version: 1.0
Content-Type: TEXT/plain; charset=us-ascii
Content-MD5: scLbcj1DjTbxSAkKkpgtJQ==
X-Mailer: dtmail 1.3.0 @(#)CDE Version 1.3.5 SunOS 5.7 sun4u sparc 
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,

Section 5.12 of the draft recommendations that local repair only
be attempted once.  If it is not successful, an RERR should be
sent to the source(s) of the route.

Elizabeth


~> 
~> Dear all,
~> I'm a student and I'm curretly studying about AODV. I want to ask one
~> question.
~> In AODV specification, how many times does the upstream node with link break
~> send RREQ, when local repair occurs?
~> ns-2 uses about three, but the draft doesn't seem to say anything about
~> that.
~> I think this parameter is critical for the local repair performance.
~> 
~> Best regards,
~> 
~> 
~> _______________________________________________
~> 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 Dec 10 13: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 NAA16033
	for <manet-archive@lists.ietf.org>; Tue, 10 Dec 2002 13:01: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 gBAHqVv15627;
	Tue, 10 Dec 2002 12: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 gBAHp2v15573
	for <manet@optimus.ietf.org>; Tue, 10 Dec 2002 12:51:02 -0500
Received: from techunix.technion.ac.il (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA15449
	for <manet@ietf.org>; Tue, 10 Dec 2002 12:48:00 -0500 (EST)
Received: from tx.technion.ac.il (unknown [132.68.61.54])
	by techunix.technion.ac.il (Postfix) with ESMTP id BB31B157D3
	for <manet@ietf.org>; Tue, 10 Dec 2002 19:50:51 +0200 (IST)
Message-ID: <3DF62A83.EDE16237@tx.technion.ac.il>
Date: Tue, 10 Dec 2002 19:55:15 +0200
From: Gil Zussman <gilz@techunix.technion.ac.il>
Organization: Technion
X-Mailer: Mozilla 4.72 [en] (Windows NT 5.0; I)
X-Accept-Language: en
MIME-Version: 1.0
To: manet@ietf.org
References: <20021210170002.11476.58137.Mailman@www1.ietf.org>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit
Subject: [manet] Re: how about the bandwidth allocation issue in ad hoc?
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 can take a look at our paper:
http://comnet.technion.ac.il/~gilz/pub_files/networking2002.pdf
that deals with bandwidth allocation in Bluetooth scatternets (If you wish, I can send you an extended version that will appear in MONET).

Regards,
Gil Zussman


>
> Date: Tue, 10 Dec 2002 16:44:15 +0800
> From: "=?GB2312?Q?=CB=EF=C1=C1?=" <sun7927@163.com>
> To: manet <manet@ietf.org>
> Subject: [manet] how about the bandwidth allocation issue in ad hoc?
>
> Hi,
>
>         I am becoming interesting in the bandwidth allocation issue in ad hoc networks, but I don't know the  evolvement of this issue, can anyone tell me the detail?
>         Thanks!
>
> --__--__--
>
> _______________________________________________
> 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  Tue Dec 10 13:13: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 NAA16373
	for <manet-archive@odin.ietf.org>; Tue, 10 Dec 2002 13:13:10 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id gBAIFdZ17575
	for manet-archive@odin.ietf.org; Tue, 10 Dec 2002 13:15: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 gBAIFcv17572
	for <manet-web-archive@optimus.ietf.org>; Tue, 10 Dec 2002 13:15:38 -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 NAA16349
	for <manet-web-archive@ietf.org>; Tue, 10 Dec 2002 13:12: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 gBAHqVv15627;
	Tue, 10 Dec 2002 12: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 gBAHp2v15573
	for <manet@optimus.ietf.org>; Tue, 10 Dec 2002 12:51:02 -0500
Received: from techunix.technion.ac.il (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA15449
	for <manet@ietf.org>; Tue, 10 Dec 2002 12:48:00 -0500 (EST)
Received: from tx.technion.ac.il (unknown [132.68.61.54])
	by techunix.technion.ac.il (Postfix) with ESMTP id BB31B157D3
	for <manet@ietf.org>; Tue, 10 Dec 2002 19:50:51 +0200 (IST)
Message-ID: <3DF62A83.EDE16237@tx.technion.ac.il>
Date: Tue, 10 Dec 2002 19:55:15 +0200
From: Gil Zussman <gilz@techunix.technion.ac.il>
Organization: Technion
X-Mailer: Mozilla 4.72 [en] (Windows NT 5.0; I)
X-Accept-Language: en
MIME-Version: 1.0
To: manet@ietf.org
References: <20021210170002.11476.58137.Mailman@www1.ietf.org>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit
Subject: [manet] Re: how about the bandwidth allocation issue in ad hoc?
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 can take a look at our paper:
http://comnet.technion.ac.il/~gilz/pub_files/networking2002.pdf
that deals with bandwidth allocation in Bluetooth scatternets (If you wish, I can send you an extended version that will appear in MONET).

Regards,
Gil Zussman


>
> Date: Tue, 10 Dec 2002 16:44:15 +0800
> From: "=?GB2312?Q?=CB=EF=C1=C1?=" <sun7927@163.com>
> To: manet <manet@ietf.org>
> Subject: [manet] how about the bandwidth allocation issue in ad hoc?
>
> Hi,
>
>         I am becoming interesting in the bandwidth allocation issue in ad hoc networks, but I don't know the  evolvement of this issue, can anyone tell me the detail?
>         Thanks!
>
> --__--__--
>
> _______________________________________________
> 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  Tue Dec 10 13:16: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 NAA16539
	for <manet-archive@odin.ietf.org>; Tue, 10 Dec 2002 13:16:58 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id gBAIJQD17862
	for manet-archive@odin.ietf.org; Tue, 10 Dec 2002 13:19: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 gBAIJQv17859
	for <manet-web-archive@optimus.ietf.org>; Tue, 10 Dec 2002 13:19: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 NAA16455
	for <manet-web-archive@ietf.org>; Tue, 10 Dec 2002 13:16: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 gBAI6iv16496;
	Tue, 10 Dec 2002 13:06: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 gBAI5Wv16439
	for <manet@optimus.ietf.org>; Tue, 10 Dec 2002 13:05:32 -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 NAA16075
	for <manet@ietf.org>; Tue, 10 Dec 2002 13:02:31 -0500 (EST)
Received: from SRCATL-MTA by mail.scires.com
	with Novell_GroupWise; Tue, 10 Dec 2002 13:06:39 -0500
Message-Id: <sdf5e6df.027@mail.scires.com>
X-Mailer: Novell GroupWise Internet Agent 6.0.2 Beta
Date: Tue, 10 Dec 2002 13:06:17 -0500
From: "Pete Sholander" <psholand@scires.com>
To: <Corson@flarion.com>, <manet@ietf.org>
Cc: <haas@EE.CORNELL.EDU>
Subject: Re: [manet] WG Mtg Summary -- Comment on Consensus
Mime-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
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

Scott,

Three comments, all prefaced with IMHO of course.  Also a question on
schedule.

Comment 1: I agree that moving into an engineering mode is a good
thing.  Getting Experimental RFCs pubished by the IETF will motivate
additional open-air demos that will provide realistic data-sets for both
the IRTF and IETF.


Comment 2: The decision to sidetrack all types of "hybrid routing" off
into the IRTF seems **quite** unwise.  Several of my customers view
hybrid-routing as providing "application scalability" rather than
scalability in network size.  Hybrid techniques sidestep the debates
about reactive-routing having too much initial latency for real-time
traffic versus proactive routing problem's with LPD and energy
efficiency.  This seems to be *very* important to them in the short term
wherein they're trying to get additional open-air demos (with realistic
terrain, military personnel, ...) funded.

With that said, an IETF goal for the March or July meeting might be to
decide whether to:
       a) still consider protocols (e.g. ZRP or various cluster-based
schemes) that allow *every* node to exhibit hybrid behavior.
or
       b) or  down-scope to allowing a few "gateway" nodes to exchange
topology information between the proactive and reactive portions of one
MANET.  

draft-wakikawa-manet-globalv6-02.txt might form a basis for item (b). 
Wrt to Item (a), SRC and Cornell still plan to update the "ZRP drafts"
for the March meeting.  However, the focus will be on how IETF standard
reactive/proactive protocol (e.g., AODV/DSR and TBRPF/OLSR) components
can exchange topology information at a given node.  We won't be updating
the old IARP/IERP drafts. 

Comment 3: The proposal for the IRTF to meet at separate times/places
from the IETF is unfair to small businesses since it ups the numbers of
meetings from three to six.  For those who mainly do US gov't funded
work, it also probably ups the foreign travel requirements from one to
at least two (?)  Finally, the conferences you mentioned at the Atlanta
meeting (INFOCOM, ...) might not the ones that US DoD contractors
typically attend (e.g., MILCOM).   So, if the ADs split the MANET work
then the IRTF MANET RG needs to meet concurrently with the IETF
meetings.


Question1: The schedule outlined in Atlanta was: a) mailing list
discussion in December and January; b) an updated recharting proposal
for the San Francisco meeting in March; and c) a WG vote on recharting
at the Vienna meeting in July.  Is this correct?  If not then what's the
actual schedule?  Also, who's the final-decision authority?  (The ADs?)

--Pete Sholander
Scientific Research Corporation		
Atlanta, GA		

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

>>> Scott Corson <Corson@flarion.com> 12/02/02 09:54AM >>>
Folks,

This is a heads up for those not present in Atlanta and a request for
comment.

The WG met and principally discussed developments underway as a
consequence
of rechartering activities.  A decision has been made by the ADs and
WG
chairs to convert MANET from the psuedo-research mode of its origin
into a
pure engineering group, with more mature technical work proceeding
through
group consensus and scoped problem statements. The proposed approach
for
rechartering and updated milestones was presented at the meeting and
there
was a clear consensus of agreement that this is a good way forward. 
In
parallel with MANET rechartering, an IRTF MANET RG was created as a
subgroup
of the IRTF Routing RG.  The research theme of this RG is
"scalability". A
set of the existing IETF MANET proposals (FSR, LANMAR, TORA, ZRP)--all
originally targeted at scalability--have been selected for relocation
to
this RG.  The remaining IETF MANET I-Ds (AODV, DSR, OLSR,TBRPF) are
roughly
completed and are to be submitted for Experimental RFC status to
encourage
additional third party experimentation with concepts and
implementations.
Lessons learned from the past years' development of these core
protocols
will form the basis for the design of the new consensus-based protocol
work.
The meeting concluded with four presentations giving the current status
of
each of the core MANET I-Ds.

I am requesting any additional input from the list
(agreement/disagreement?)

regarding this WG direction.

-Scott
_______________________________________________
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 Dec 10 13:22: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 NAA16673
	for <manet-archive@lists.ietf.org>; Tue, 10 Dec 2002 13:22: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 gBAI6iv16496;
	Tue, 10 Dec 2002 13:06: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 gBAI5Wv16439
	for <manet@optimus.ietf.org>; Tue, 10 Dec 2002 13:05:32 -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 NAA16075
	for <manet@ietf.org>; Tue, 10 Dec 2002 13:02:31 -0500 (EST)
Received: from SRCATL-MTA by mail.scires.com
	with Novell_GroupWise; Tue, 10 Dec 2002 13:06:39 -0500
Message-Id: <sdf5e6df.027@mail.scires.com>
X-Mailer: Novell GroupWise Internet Agent 6.0.2 Beta
Date: Tue, 10 Dec 2002 13:06:17 -0500
From: "Pete Sholander" <psholand@scires.com>
To: <Corson@flarion.com>, <manet@ietf.org>
Cc: <haas@EE.CORNELL.EDU>
Subject: Re: [manet] WG Mtg Summary -- Comment on Consensus
Mime-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
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

Scott,

Three comments, all prefaced with IMHO of course.  Also a question on
schedule.

Comment 1: I agree that moving into an engineering mode is a good
thing.  Getting Experimental RFCs pubished by the IETF will motivate
additional open-air demos that will provide realistic data-sets for both
the IRTF and IETF.


Comment 2: The decision to sidetrack all types of "hybrid routing" off
into the IRTF seems **quite** unwise.  Several of my customers view
hybrid-routing as providing "application scalability" rather than
scalability in network size.  Hybrid techniques sidestep the debates
about reactive-routing having too much initial latency for real-time
traffic versus proactive routing problem's with LPD and energy
efficiency.  This seems to be *very* important to them in the short term
wherein they're trying to get additional open-air demos (with realistic
terrain, military personnel, ...) funded.

With that said, an IETF goal for the March or July meeting might be to
decide whether to:
       a) still consider protocols (e.g. ZRP or various cluster-based
schemes) that allow *every* node to exhibit hybrid behavior.
or
       b) or  down-scope to allowing a few "gateway" nodes to exchange
topology information between the proactive and reactive portions of one
MANET.  

draft-wakikawa-manet-globalv6-02.txt might form a basis for item (b). 
Wrt to Item (a), SRC and Cornell still plan to update the "ZRP drafts"
for the March meeting.  However, the focus will be on how IETF standard
reactive/proactive protocol (e.g., AODV/DSR and TBRPF/OLSR) components
can exchange topology information at a given node.  We won't be updating
the old IARP/IERP drafts. 

Comment 3: The proposal for the IRTF to meet at separate times/places
from the IETF is unfair to small businesses since it ups the numbers of
meetings from three to six.  For those who mainly do US gov't funded
work, it also probably ups the foreign travel requirements from one to
at least two (?)  Finally, the conferences you mentioned at the Atlanta
meeting (INFOCOM, ...) might not the ones that US DoD contractors
typically attend (e.g., MILCOM).   So, if the ADs split the MANET work
then the IRTF MANET RG needs to meet concurrently with the IETF
meetings.


Question1: The schedule outlined in Atlanta was: a) mailing list
discussion in December and January; b) an updated recharting proposal
for the San Francisco meeting in March; and c) a WG vote on recharting
at the Vienna meeting in July.  Is this correct?  If not then what's the
actual schedule?  Also, who's the final-decision authority?  (The ADs?)

--Pete Sholander
Scientific Research Corporation		
Atlanta, GA		

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

>>> Scott Corson <Corson@flarion.com> 12/02/02 09:54AM >>>
Folks,

This is a heads up for those not present in Atlanta and a request for
comment.

The WG met and principally discussed developments underway as a
consequence
of rechartering activities.  A decision has been made by the ADs and
WG
chairs to convert MANET from the psuedo-research mode of its origin
into a
pure engineering group, with more mature technical work proceeding
through
group consensus and scoped problem statements. The proposed approach
for
rechartering and updated milestones was presented at the meeting and
there
was a clear consensus of agreement that this is a good way forward. 
In
parallel with MANET rechartering, an IRTF MANET RG was created as a
subgroup
of the IRTF Routing RG.  The research theme of this RG is
"scalability". A
set of the existing IETF MANET proposals (FSR, LANMAR, TORA, ZRP)--all
originally targeted at scalability--have been selected for relocation
to
this RG.  The remaining IETF MANET I-Ds (AODV, DSR, OLSR,TBRPF) are
roughly
completed and are to be submitted for Experimental RFC status to
encourage
additional third party experimentation with concepts and
implementations.
Lessons learned from the past years' development of these core
protocols
will form the basis for the design of the new consensus-based protocol
work.
The meeting concluded with four presentations giving the current status
of
each of the core MANET I-Ds.

I am requesting any additional input from the list
(agreement/disagreement?)

regarding this WG direction.

-Scott
_______________________________________________
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 Dec 10 20:59: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 UAA27768
	for <manet-archive@odin.ietf.org>; Tue, 10 Dec 2002 20:59:42 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id gBB22F012503
	for manet-archive@odin.ietf.org; Tue, 10 Dec 2002 21:02: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 gBB22Fv12500
	for <manet-web-archive@optimus.ietf.org>; Tue, 10 Dec 2002 21:02: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 UAA27757
	for <manet-web-archive@ietf.org>; Tue, 10 Dec 2002 20:59: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 gBB1n8v11949;
	Tue, 10 Dec 2002 20:49: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 gBB1jWv11841
	for <manet@optimus.ietf.org>; Tue, 10 Dec 2002 20:45:32 -0500
Received: from mail.ict.ac.cn (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id UAA27487
	for <manet@ietf.org>; Tue, 10 Dec 2002 20:42:26 -0500 (EST)
Received: (qmail 17485 invoked from network); 11 Dec 2002 01:45:45 -0000
Received: from unknown (HELO Amy) (159.226.39.104)
  by 159.226.39.4 with SMTP; 11 Dec 2002 01:45:45 -0000
From: "Liu Min" <liumin@ict.ac.cn>
To: <manet@ietf.org>
Date: Wed, 11 Dec 2002 09:46:38 +0800
Message-ID: <000001c2a0b7$255a4f10$7774a8c0@Amy>
MIME-Version: 1.0
Content-Type: multipart/alternative;
	boundary="----=_NextPart_000_0001_01C2A0FA.337D8F10"
X-Priority: 3 (Normal)
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook, Build 10.0.2627
Importance: Normal
X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4522.1200
Subject: [manet] multicast in AODV
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_0001_01C2A0FA.337D8F10
Content-Type: text/plain;
	charset="gb2312"
Content-Transfer-Encoding: 7bit

In the draft of AODV on 19 June 2002, it is said that a RREQ may also be
received for a multicast IP address. But how to ensure there is a route
to a multicast IP address in MANET?
When all members of the multicast group have been found? Or we only have
to find one of them? In addition, which one should send the RREP? 
 
 
 

Best Wishes,
 
Liu Min
Institute of Computing Technology
Chinese Academy of Sciences
Tel: (86-10) 6256 5533-9240 
E-mail: liumin@ict.ac.cn
 

------=_NextPart_000_0001_01C2A0FA.337D8F10
Content-Type: text/html;
	charset="gb2312"
Content-Transfer-Encoding: quoted-printable

<html xmlns:o=3D"urn:schemas-microsoft-com:office:office" =
xmlns:w=3D"urn:schemas-microsoft-com:office:word" =
xmlns:st1=3D"urn:schemas-microsoft-com:office:smarttags" =
xmlns=3D"http://www.w3.org/TR/REC-html40">

<head>
<META HTTP-EQUIV=3D"Content-Type" CONTENT=3D"text/html; =
charset=3Dgb2312">


<meta name=3DProgId content=3DWord.Document>
<meta name=3DGenerator content=3D"Microsoft Word 10">
<meta name=3DOriginator content=3D"Microsoft Word 10">
<link rel=3DFile-List href=3D"cid:filelist.xml@01C2A0FA.33197610">
<o:SmartTagType =
namespaceuri=3D"urn:schemas-microsoft-com:office:smarttags"
 name=3D"date"/>
<o:SmartTagType =
namespaceuri=3D"urn:schemas-microsoft-com:office:smarttags"
 name=3D"PlaceType"/>
<o:SmartTagType =
namespaceuri=3D"urn:schemas-microsoft-com:office:smarttags"
 name=3D"PlaceName"/>
<o:SmartTagType =
namespaceuri=3D"urn:schemas-microsoft-com:office:smarttags"
 name=3D"place"/>
<!--[if gte mso 9]><xml>
 <o:OfficeDocumentSettings>
  <o:DoNotRelyOnCSS/>
 </o:OfficeDocumentSettings>
</xml><![endif]--><!--[if gte mso 9]><xml>
 <w:WordDocument>
  <w:SpellingState>Clean</w:SpellingState>
  <w:GrammarState>Clean</w:GrammarState>
  <w:DocumentKind>DocumentEmail</w:DocumentKind>
  <w:EnvelopeVis/>
  <w:PunctuationKerning/>
  <w:DrawingGridVerticalSpacing>7.8 =
=B0=F5</w:DrawingGridVerticalSpacing>
  =
<w:DisplayHorizontalDrawingGridEvery>0</w:DisplayHorizontalDrawingGridEve=
ry>
  =
<w:DisplayVerticalDrawingGridEvery>2</w:DisplayVerticalDrawingGridEvery>
  <w:Compatibility>
   <w:SpaceForUL/>
   <w:BalanceSingleByteDoubleByteWidth/>
   <w:DoNotLeaveBackslashAlone/>
   <w:ULTrailSpace/>
   <w:DoNotExpandShiftReturn/>
   <w:AdjustLineHeightInTable/>
   <w:BreakWrappedTables/>
   <w:SnapToGridInCell/>
   <w:WrapTextWithPunct/>
   <w:UseAsianBreakRules/>
   <w:UseFELayout/>
  </w:Compatibility>
  <w:BrowserLevel>MicrosoftInternetExplorer4</w:BrowserLevel>
 </w:WordDocument>
</xml><![endif]--><!--[if !mso]>
<style>
st1\:*{behavior:url(#default#ieooui) }
</style>
<![endif]-->
<style>
<!--
 /* Font Definitions */
 @font-face
	{font-family:=CB=CE=CC=E5;
	panose-1:2 1 6 0 3 1 1 1 1 1;
	mso-font-alt:SimSun;
	mso-font-charset:134;
	mso-generic-font-family:auto;
	mso-font-pitch:variable;
	mso-font-signature:3 135135232 16 0 262145 0;}
@font-face
	{font-family:"\@=CB=CE=CC=E5";
	panose-1:2 1 6 0 3 1 1 1 1 1;
	mso-font-charset:134;
	mso-generic-font-family:auto;
	mso-font-pitch:variable;
	mso-font-signature:3 135135232 16 0 262145 0;}
 /* Style Definitions */
 p.MsoNormal, li.MsoNormal, div.MsoNormal
	{mso-style-parent:"";
	margin:0cm;
	margin-bottom:.0001pt;
	text-align:justify;
	text-justify:inter-ideograph;
	mso-pagination:none;
	font-size:10.5pt;
	mso-bidi-font-size:12.0pt;
	font-family:"Times New Roman";
	mso-fareast-font-family:=CB=CE=CC=E5;
	mso-font-kerning:1.0pt;}
a:link, span.MsoHyperlink
	{color:blue;
	text-decoration:underline;
	text-underline:single;}
a:visited, span.MsoHyperlinkFollowed
	{color:purple;
	text-decoration:underline;
	text-underline:single;}
span.EmailStyle17
	{mso-style-type:personal-compose;
	mso-style-noshow:yes;
	mso-ansi-font-size:9.0pt;
	mso-bidi-font-size:10.0pt;
	font-family:Arial;
	mso-ascii-font-family:Arial;
	mso-fareast-font-family:=CB=CE=CC=E5;
	mso-hansi-font-family:Arial;
	mso-bidi-font-family:Arial;
	color:windowtext;}
span.GramE
	{mso-style-name:"";
	mso-gram-e:yes;}
 /* Page Definitions */
 @page
	{mso-page-border-surround-header:no;
	mso-page-border-surround-footer:no;}
@page Section1
	{size:595.3pt 841.9pt;
	margin:72.0pt 90.0pt 72.0pt 90.0pt;
	mso-header-margin:42.55pt;
	mso-footer-margin:49.6pt;
	mso-paper-source:0;
	layout-grid:15.6pt;}
div.Section1
	{page:Section1;}
-->
</style>
<!--[if gte mso 10]>
<style>
 /* Style Definitions */=20
 table.MsoNormalTable
	{mso-style-name:=C6=D5=CD=A8=B1=ED=B8=F1;
	mso-tstyle-rowband-size:0;
	mso-tstyle-colband-size:0;
	mso-style-noshow:yes;
	mso-style-parent:"";
	mso-padding-alt:0cm 5.4pt 0cm 5.4pt;
	mso-para-margin:0cm;
	mso-para-margin-bottom:.0001pt;
	mso-pagination:widow-orphan;
	font-size:10.0pt;
	font-family:"Times New Roman";}
</style>
<![endif]-->
</head>

<body lang=3DZH-CN link=3Dblue vlink=3Dpurple =
style=3D'tab-interval:21.0pt;text-justify-trim:
punctuation'>

<div class=3DSection1 style=3D'layout-grid:15.6pt'>

<p class=3DMsoNormal><font size=3D1 face=3DArial><span lang=3DEN-US =
style=3D'font-size:
9.0pt;mso-bidi-font-size:10.0pt;font-family:Arial'>In the draft of AODV =
on </span></font><st1:date
Month=3D"6" Day=3D"19" Year=3D"2002"><font size=3D1 face=3DArial><span =
lang=3DEN-US
 =
style=3D'font-size:9.0pt;mso-bidi-font-size:10.0pt;font-family:Arial'>19 =
June
 2002</span></font></st1:date><font size=3D1 face=3DArial><span =
lang=3DEN-US
style=3D'font-size:9.0pt;mso-bidi-font-size:10.0pt;font-family:Arial'>, =
it is
said that a RREQ may also be received for a multicast IP address. But =
how to ensure
there is a route to a multicast IP address in =
MANET?<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D1 face=3DArial><span lang=3DEN-US =
style=3D'font-size:
9.0pt;mso-bidi-font-size:10.0pt;font-family:Arial'>When all members of =
the
multicast group have been found? Or we only have to find one of them? In
addition, which one should send the RREP? <o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D1 face=3DArial><span lang=3DEN-US =
style=3D'font-size:
9.0pt;mso-bidi-font-size:10.0pt;font-family:Arial'><o:p>&nbsp;</o:p></spa=
n></font></p>

<p class=3DMsoNormal><font size=3D2 face=3D"Times New Roman"><span =
lang=3DEN-US
style=3D'font-size:10.5pt;mso-no-proof:yes'><span =
style=3D'mso-bidi-font-size:12.0pt'>&nbsp;<o:p></o:p></span></span></font=
></p>

<div>

<p class=3DMsoNormal><font size=3D2 face=3D"Times New Roman"><span =
lang=3DEN-US
style=3D'font-size:10.5pt;mso-no-proof:yes'><span =
style=3D'mso-bidi-font-size:12.0pt'>&nbsp;<o:p></o:p></span></span></font=
></p>

</div>

<p class=3DMsoNormal><font size=3D2 face=3D"Times New Roman"><span =
lang=3DEN-US
style=3D'font-size:10.0pt;mso-no-proof:yes'><br>
Best Wishes,</span></font><span lang=3DEN-US =
style=3D'mso-no-proof:yes'><o:p></o:p></span></p>

<div>

<p class=3DMsoNormal><font size=3D2 face=3D"Times New Roman"><span =
lang=3DEN-US
style=3D'font-size:10.5pt;mso-no-proof:yes'><span =
style=3D'mso-bidi-font-size:12.0pt'>&nbsp;<o:p></o:p></span></span></font=
></p>

</div>

<p class=3DMsoNormal><font size=3D2 face=3D"Times New Roman"><span =
lang=3DEN-US
style=3D'font-size:10.0pt;mso-no-proof:yes'>Liu Min</span></font><span
lang=3DEN-US style=3D'mso-no-proof:yes'><o:p></o:p></span></p>

<p class=3DMsoNormal><font size=3D2 face=3D"Times New Roman"><span =
lang=3DEN-US
style=3D'font-size:10.0pt;mso-no-proof:yes'>Institute of Computing =
Technology</span></font><span
lang=3DEN-US style=3D'mso-no-proof:yes'><o:p></o:p></span></p>

<p class=3DMsoNormal><st1:place><st1:PlaceName><font size=3D2 =
face=3D"Times New Roman"><span
  lang=3DEN-US =
style=3D'font-size:10.0pt;mso-no-proof:yes'>Chinese</span></font></st1:Pl=
aceName><font
 size=3D2><span lang=3DEN-US =
style=3D'font-size:10.0pt;mso-no-proof:yes'> =
</span></font><st1:PlaceType><font
  size=3D2><span lang=3DEN-US =
style=3D'font-size:10.0pt;mso-no-proof:yes'>Academy</span></font></st1:Pl=
aceType></st1:place><font
size=3D2><span lang=3DEN-US style=3D'font-size:10.0pt;mso-no-proof:yes'> =
of Sciences</span></font><span
lang=3DEN-US style=3D'mso-no-proof:yes'><o:p></o:p></span></p>

<p class=3DMsoNormal><font size=3D2 face=3D"Times New Roman"><span =
lang=3DEN-US
style=3D'font-size:10.0pt;mso-no-proof:yes'>Tel: (86-10) 6256 5533-9240 =
<br>
E-mail: <a =
href=3D"mailto:liumin@ict.ac.cn">liumin@ict.ac.cn</a></span></font><font
size=3D2><span lang=3DEN-US =
style=3D'font-size:10.0pt'><o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 face=3D"Times New Roman"><span =
lang=3DEN-US><o:p>&nbsp;</o:p></span></font></p>

</div>

</body>

</html>

------=_NextPart_000_0001_01C2A0FA.337D8F10--

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



From manet-admin@ietf.org  Tue Dec 10 21: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 VAA27924
	for <manet-archive@lists.ietf.org>; Tue, 10 Dec 2002 21:04: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 gBB1n8v11949;
	Tue, 10 Dec 2002 20:49: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 gBB1jWv11841
	for <manet@optimus.ietf.org>; Tue, 10 Dec 2002 20:45:32 -0500
Received: from mail.ict.ac.cn (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id UAA27487
	for <manet@ietf.org>; Tue, 10 Dec 2002 20:42:26 -0500 (EST)
Received: (qmail 17485 invoked from network); 11 Dec 2002 01:45:45 -0000
Received: from unknown (HELO Amy) (159.226.39.104)
  by 159.226.39.4 with SMTP; 11 Dec 2002 01:45:45 -0000
From: "Liu Min" <liumin@ict.ac.cn>
To: <manet@ietf.org>
Date: Wed, 11 Dec 2002 09:46:38 +0800
Message-ID: <000001c2a0b7$255a4f10$7774a8c0@Amy>
MIME-Version: 1.0
Content-Type: multipart/alternative;
	boundary="----=_NextPart_000_0001_01C2A0FA.337D8F10"
X-Priority: 3 (Normal)
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook, Build 10.0.2627
Importance: Normal
X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4522.1200
Subject: [manet] multicast in AODV
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_0001_01C2A0FA.337D8F10
Content-Type: text/plain;
	charset="gb2312"
Content-Transfer-Encoding: 7bit

In the draft of AODV on 19 June 2002, it is said that a RREQ may also be
received for a multicast IP address. But how to ensure there is a route
to a multicast IP address in MANET?
When all members of the multicast group have been found? Or we only have
to find one of them? In addition, which one should send the RREP? 
 
 
 

Best Wishes,
 
Liu Min
Institute of Computing Technology
Chinese Academy of Sciences
Tel: (86-10) 6256 5533-9240 
E-mail: liumin@ict.ac.cn
 

------=_NextPart_000_0001_01C2A0FA.337D8F10
Content-Type: text/html;
	charset="gb2312"
Content-Transfer-Encoding: quoted-printable

<html xmlns:o=3D"urn:schemas-microsoft-com:office:office" =
xmlns:w=3D"urn:schemas-microsoft-com:office:word" =
xmlns:st1=3D"urn:schemas-microsoft-com:office:smarttags" =
xmlns=3D"http://www.w3.org/TR/REC-html40">

<head>
<META HTTP-EQUIV=3D"Content-Type" CONTENT=3D"text/html; =
charset=3Dgb2312">


<meta name=3DProgId content=3DWord.Document>
<meta name=3DGenerator content=3D"Microsoft Word 10">
<meta name=3DOriginator content=3D"Microsoft Word 10">
<link rel=3DFile-List href=3D"cid:filelist.xml@01C2A0FA.33197610">
<o:SmartTagType =
namespaceuri=3D"urn:schemas-microsoft-com:office:smarttags"
 name=3D"date"/>
<o:SmartTagType =
namespaceuri=3D"urn:schemas-microsoft-com:office:smarttags"
 name=3D"PlaceType"/>
<o:SmartTagType =
namespaceuri=3D"urn:schemas-microsoft-com:office:smarttags"
 name=3D"PlaceName"/>
<o:SmartTagType =
namespaceuri=3D"urn:schemas-microsoft-com:office:smarttags"
 name=3D"place"/>
<!--[if gte mso 9]><xml>
 <o:OfficeDocumentSettings>
  <o:DoNotRelyOnCSS/>
 </o:OfficeDocumentSettings>
</xml><![endif]--><!--[if gte mso 9]><xml>
 <w:WordDocument>
  <w:SpellingState>Clean</w:SpellingState>
  <w:GrammarState>Clean</w:GrammarState>
  <w:DocumentKind>DocumentEmail</w:DocumentKind>
  <w:EnvelopeVis/>
  <w:PunctuationKerning/>
  <w:DrawingGridVerticalSpacing>7.8 =
=B0=F5</w:DrawingGridVerticalSpacing>
  =
<w:DisplayHorizontalDrawingGridEvery>0</w:DisplayHorizontalDrawingGridEve=
ry>
  =
<w:DisplayVerticalDrawingGridEvery>2</w:DisplayVerticalDrawingGridEvery>
  <w:Compatibility>
   <w:SpaceForUL/>
   <w:BalanceSingleByteDoubleByteWidth/>
   <w:DoNotLeaveBackslashAlone/>
   <w:ULTrailSpace/>
   <w:DoNotExpandShiftReturn/>
   <w:AdjustLineHeightInTable/>
   <w:BreakWrappedTables/>
   <w:SnapToGridInCell/>
   <w:WrapTextWithPunct/>
   <w:UseAsianBreakRules/>
   <w:UseFELayout/>
  </w:Compatibility>
  <w:BrowserLevel>MicrosoftInternetExplorer4</w:BrowserLevel>
 </w:WordDocument>
</xml><![endif]--><!--[if !mso]>
<style>
st1\:*{behavior:url(#default#ieooui) }
</style>
<![endif]-->
<style>
<!--
 /* Font Definitions */
 @font-face
	{font-family:=CB=CE=CC=E5;
	panose-1:2 1 6 0 3 1 1 1 1 1;
	mso-font-alt:SimSun;
	mso-font-charset:134;
	mso-generic-font-family:auto;
	mso-font-pitch:variable;
	mso-font-signature:3 135135232 16 0 262145 0;}
@font-face
	{font-family:"\@=CB=CE=CC=E5";
	panose-1:2 1 6 0 3 1 1 1 1 1;
	mso-font-charset:134;
	mso-generic-font-family:auto;
	mso-font-pitch:variable;
	mso-font-signature:3 135135232 16 0 262145 0;}
 /* Style Definitions */
 p.MsoNormal, li.MsoNormal, div.MsoNormal
	{mso-style-parent:"";
	margin:0cm;
	margin-bottom:.0001pt;
	text-align:justify;
	text-justify:inter-ideograph;
	mso-pagination:none;
	font-size:10.5pt;
	mso-bidi-font-size:12.0pt;
	font-family:"Times New Roman";
	mso-fareast-font-family:=CB=CE=CC=E5;
	mso-font-kerning:1.0pt;}
a:link, span.MsoHyperlink
	{color:blue;
	text-decoration:underline;
	text-underline:single;}
a:visited, span.MsoHyperlinkFollowed
	{color:purple;
	text-decoration:underline;
	text-underline:single;}
span.EmailStyle17
	{mso-style-type:personal-compose;
	mso-style-noshow:yes;
	mso-ansi-font-size:9.0pt;
	mso-bidi-font-size:10.0pt;
	font-family:Arial;
	mso-ascii-font-family:Arial;
	mso-fareast-font-family:=CB=CE=CC=E5;
	mso-hansi-font-family:Arial;
	mso-bidi-font-family:Arial;
	color:windowtext;}
span.GramE
	{mso-style-name:"";
	mso-gram-e:yes;}
 /* Page Definitions */
 @page
	{mso-page-border-surround-header:no;
	mso-page-border-surround-footer:no;}
@page Section1
	{size:595.3pt 841.9pt;
	margin:72.0pt 90.0pt 72.0pt 90.0pt;
	mso-header-margin:42.55pt;
	mso-footer-margin:49.6pt;
	mso-paper-source:0;
	layout-grid:15.6pt;}
div.Section1
	{page:Section1;}
-->
</style>
<!--[if gte mso 10]>
<style>
 /* Style Definitions */=20
 table.MsoNormalTable
	{mso-style-name:=C6=D5=CD=A8=B1=ED=B8=F1;
	mso-tstyle-rowband-size:0;
	mso-tstyle-colband-size:0;
	mso-style-noshow:yes;
	mso-style-parent:"";
	mso-padding-alt:0cm 5.4pt 0cm 5.4pt;
	mso-para-margin:0cm;
	mso-para-margin-bottom:.0001pt;
	mso-pagination:widow-orphan;
	font-size:10.0pt;
	font-family:"Times New Roman";}
</style>
<![endif]-->
</head>

<body lang=3DZH-CN link=3Dblue vlink=3Dpurple =
style=3D'tab-interval:21.0pt;text-justify-trim:
punctuation'>

<div class=3DSection1 style=3D'layout-grid:15.6pt'>

<p class=3DMsoNormal><font size=3D1 face=3DArial><span lang=3DEN-US =
style=3D'font-size:
9.0pt;mso-bidi-font-size:10.0pt;font-family:Arial'>In the draft of AODV =
on </span></font><st1:date
Month=3D"6" Day=3D"19" Year=3D"2002"><font size=3D1 face=3DArial><span =
lang=3DEN-US
 =
style=3D'font-size:9.0pt;mso-bidi-font-size:10.0pt;font-family:Arial'>19 =
June
 2002</span></font></st1:date><font size=3D1 face=3DArial><span =
lang=3DEN-US
style=3D'font-size:9.0pt;mso-bidi-font-size:10.0pt;font-family:Arial'>, =
it is
said that a RREQ may also be received for a multicast IP address. But =
how to ensure
there is a route to a multicast IP address in =
MANET?<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D1 face=3DArial><span lang=3DEN-US =
style=3D'font-size:
9.0pt;mso-bidi-font-size:10.0pt;font-family:Arial'>When all members of =
the
multicast group have been found? Or we only have to find one of them? In
addition, which one should send the RREP? <o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D1 face=3DArial><span lang=3DEN-US =
style=3D'font-size:
9.0pt;mso-bidi-font-size:10.0pt;font-family:Arial'><o:p>&nbsp;</o:p></spa=
n></font></p>

<p class=3DMsoNormal><font size=3D2 face=3D"Times New Roman"><span =
lang=3DEN-US
style=3D'font-size:10.5pt;mso-no-proof:yes'><span =
style=3D'mso-bidi-font-size:12.0pt'>&nbsp;<o:p></o:p></span></span></font=
></p>

<div>

<p class=3DMsoNormal><font size=3D2 face=3D"Times New Roman"><span =
lang=3DEN-US
style=3D'font-size:10.5pt;mso-no-proof:yes'><span =
style=3D'mso-bidi-font-size:12.0pt'>&nbsp;<o:p></o:p></span></span></font=
></p>

</div>

<p class=3DMsoNormal><font size=3D2 face=3D"Times New Roman"><span =
lang=3DEN-US
style=3D'font-size:10.0pt;mso-no-proof:yes'><br>
Best Wishes,</span></font><span lang=3DEN-US =
style=3D'mso-no-proof:yes'><o:p></o:p></span></p>

<div>

<p class=3DMsoNormal><font size=3D2 face=3D"Times New Roman"><span =
lang=3DEN-US
style=3D'font-size:10.5pt;mso-no-proof:yes'><span =
style=3D'mso-bidi-font-size:12.0pt'>&nbsp;<o:p></o:p></span></span></font=
></p>

</div>

<p class=3DMsoNormal><font size=3D2 face=3D"Times New Roman"><span =
lang=3DEN-US
style=3D'font-size:10.0pt;mso-no-proof:yes'>Liu Min</span></font><span
lang=3DEN-US style=3D'mso-no-proof:yes'><o:p></o:p></span></p>

<p class=3DMsoNormal><font size=3D2 face=3D"Times New Roman"><span =
lang=3DEN-US
style=3D'font-size:10.0pt;mso-no-proof:yes'>Institute of Computing =
Technology</span></font><span
lang=3DEN-US style=3D'mso-no-proof:yes'><o:p></o:p></span></p>

<p class=3DMsoNormal><st1:place><st1:PlaceName><font size=3D2 =
face=3D"Times New Roman"><span
  lang=3DEN-US =
style=3D'font-size:10.0pt;mso-no-proof:yes'>Chinese</span></font></st1:Pl=
aceName><font
 size=3D2><span lang=3DEN-US =
style=3D'font-size:10.0pt;mso-no-proof:yes'> =
</span></font><st1:PlaceType><font
  size=3D2><span lang=3DEN-US =
style=3D'font-size:10.0pt;mso-no-proof:yes'>Academy</span></font></st1:Pl=
aceType></st1:place><font
size=3D2><span lang=3DEN-US style=3D'font-size:10.0pt;mso-no-proof:yes'> =
of Sciences</span></font><span
lang=3DEN-US style=3D'mso-no-proof:yes'><o:p></o:p></span></p>

<p class=3DMsoNormal><font size=3D2 face=3D"Times New Roman"><span =
lang=3DEN-US
style=3D'font-size:10.0pt;mso-no-proof:yes'>Tel: (86-10) 6256 5533-9240 =
<br>
E-mail: <a =
href=3D"mailto:liumin@ict.ac.cn">liumin@ict.ac.cn</a></span></font><font
size=3D2><span lang=3DEN-US =
style=3D'font-size:10.0pt'><o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 face=3D"Times New Roman"><span =
lang=3DEN-US><o:p>&nbsp;</o:p></span></font></p>

</div>

</body>

</html>

------=_NextPart_000_0001_01C2A0FA.337D8F10--

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


From mailnull@www1.ietf.org  Wed Dec 11 09:34: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 JAA06798
	for <manet-archive@odin.ietf.org>; Wed, 11 Dec 2002 09:34:19 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id gBBEak030738
	for manet-archive@odin.ietf.org; Wed, 11 Dec 2002 09:36: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 gBBEakv30735
	for <manet-web-archive@optimus.ietf.org>; Wed, 11 Dec 2002 09:36: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 JAA06789
	for <manet-web-archive@ietf.org>; Wed, 11 Dec 2002 09:33: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 gBBESev30298;
	Wed, 11 Dec 2002 09:28: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 gBBEO0v30015
	for <manet@optimus.ietf.org>; Wed, 11 Dec 2002 09:24:00 -0500
Received: from noya.bupt.edu.cn (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA06223
	for <manet@ietf.org>; Wed, 11 Dec 2002 09:21:01 -0500 (EST)
Received: from wym ([202.112.108.58])
	by noya.bupt.edu.cn (8.12.2/8.12.2) with ESMTP id gBBENsPe003400
	for <manet@ietf.org>; Wed, 11 Dec 2002 22:23:55 +0800 (CST)
Message-Id: <200212111423.gBBENsPe003400@noya.bupt.edu.cn>
Date: Wed, 11 Dec 2002 22:23:1 +0800
From: WANG Yu-mei <b018158@bupt.edu.cn>
Reply-To: b018158@bupt.edu.cn
To: "manet@ietf.org" <manet@ietf.org>
Organization: BUPT
X-mailer: FoxMail 3.11 Release [cn]
Mime-Version: 1.0
Content-Type: text/plain; charset="GB2312"
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit
Subject: [manet] TCP performance analysis in mobile ad hoc network
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 eager to get a help from people who is good at TCP performance analysis, expecially that in mobile Ad hoc networks.
 
  I'm now doing some researches on TCP performance analysis in mobile ad hoc network. When I delopy  different TCP variants (TCP Tahoe, Reno, NewReno, SACK, Vegas) to compare their behavior in ad hoc network with DSR routing protocol, I found there is no obvious rules between different TCP variants for TCP throughput corresponding to different moving speed and pause time. That means, e.g. when the moving speed of the nodes is 5m/s, TCP Reno is better than Tahoe, while when the speed is 10m/s, Reno is even worse than Tahoe, which is quite different from the results reported in former papers and diferent from traditional imagination about TCP in wired networks. 

  I want to know the reason for my mysterious simulation results. Is it because of my wrong simulation method or because of TCP inherent characteristics? Thank you very much.

Best Regards.  
          
--
Yumei Wang 
School of Information Engineering, BUPT, China
TEl: +86-10-62283147(o)
-------------------------------------------------

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



From manet-admin@ietf.org  Wed Dec 11 09:39: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 JAA07025
	for <manet-archive@lists.ietf.org>; Wed, 11 Dec 2002 09:39: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 gBBESev30298;
	Wed, 11 Dec 2002 09:28: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 gBBEO0v30015
	for <manet@optimus.ietf.org>; Wed, 11 Dec 2002 09:24:00 -0500
Received: from noya.bupt.edu.cn (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA06223
	for <manet@ietf.org>; Wed, 11 Dec 2002 09:21:01 -0500 (EST)
Received: from wym ([202.112.108.58])
	by noya.bupt.edu.cn (8.12.2/8.12.2) with ESMTP id gBBENsPe003400
	for <manet@ietf.org>; Wed, 11 Dec 2002 22:23:55 +0800 (CST)
Message-Id: <200212111423.gBBENsPe003400@noya.bupt.edu.cn>
Date: Wed, 11 Dec 2002 22:23:1 +0800
From: WANG Yu-mei <b018158@bupt.edu.cn>
Reply-To: b018158@bupt.edu.cn
To: "manet@ietf.org" <manet@ietf.org>
Organization: BUPT
X-mailer: FoxMail 3.11 Release [cn]
Mime-Version: 1.0
Content-Type: text/plain; charset="GB2312"
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit
Subject: [manet] TCP performance analysis in mobile ad hoc network
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 eager to get a help from people who is good at TCP performance analysis, expecially that in mobile Ad hoc networks.
 
  I'm now doing some researches on TCP performance analysis in mobile ad hoc network. When I delopy  different TCP variants (TCP Tahoe, Reno, NewReno, SACK, Vegas) to compare their behavior in ad hoc network with DSR routing protocol, I found there is no obvious rules between different TCP variants for TCP throughput corresponding to different moving speed and pause time. That means, e.g. when the moving speed of the nodes is 5m/s, TCP Reno is better than Tahoe, while when the speed is 10m/s, Reno is even worse than Tahoe, which is quite different from the results reported in former papers and diferent from traditional imagination about TCP in wired networks. 

  I want to know the reason for my mysterious simulation results. Is it because of my wrong simulation method or because of TCP inherent characteristics? Thank you very much.

Best Regards.  
          
--
Yumei Wang 
School of Information Engineering, BUPT, China
TEl: +86-10-62283147(o)
-------------------------------------------------

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


From manet-admin@ietf.org  Wed Dec 11 15:03: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 PAA18775
	for <manet-archive@lists.ietf.org>; Wed, 11 Dec 2002 15:03: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 gBBJsXv17312;
	Wed, 11 Dec 2002 14:54: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 gBBJjsv17131
	for <manet@optimus.ietf.org>; Wed, 11 Dec 2002 14:45:54 -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 OAA18081
	for <manet@ietf.org>; Wed, 11 Dec 2002 14:42:54 -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 gBBJjkm10371;
	Wed, 11 Dec 2002 11:45:46 -0800 (PST)
Message-Id: <200212111945.gBBJjkm10371@letters.cs.ucsb.edu>
Date: Wed, 11 Dec 2002 11:45:46 -0800 (PST)
From: "Elizabeth M. Belding-Royer" <ebelding@cs.ucsb.edu>
Reply-To: "Elizabeth M. Belding-Royer" <ebelding@cs.ucsb.edu>
Subject: Re: [manet] multicast in AODV
To: liumin@ict.ac.cn
Cc: manet@ietf.org
MIME-Version: 1.0
Content-Type: TEXT/plain; charset=us-ascii
Content-MD5: 6eoj89FVzJy9JDP1yQO6ew==
X-Mailer: dtmail 1.3.0 @(#)CDE Version 1.3.5 SunOS 5.7 sun4u sparc 
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 Liu,

This information is covered in the expired AODV Multicast draft.
This draft can still be found at moment.cs.ucsb.edu/AODV/aodv.html

Basically, a multicast tree is created that interconnects the
multicast sources and receivers.  If a RREQ is received for a
multicast group, any node currently on the multicast tree can
send a RREP.  I encourage you to check the draft for the full
details.

Elizabeth 

~> 
~> In the draft of AODV on 19 June 2002, it is said that a RREQ may also be
~> received for a multicast IP address. But how to ensure there is a route
~> to a multicast IP address in MANET?
~> When all members of the multicast group have been found? Or we only have
~> to find one of them? In addition, which one should send the RREP? 
~>  
~>  
~>  
~> 
~> Best Wishes,
~>  
~> Liu Min
~> Institute of Computing Technology
~> Chinese Academy of Sciences
~> Tel: (86-10) 6256 5533-9240 
~> E-mail: liumin@ict.ac.cn
~>  

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


From mailnull@www1.ietf.org  Wed Dec 11 15:12:45 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 PAA19036
	for <manet-archive@odin.ietf.org>; Wed, 11 Dec 2002 15:12:45 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id gBBKFEo18531
	for manet-archive@odin.ietf.org; Wed, 11 Dec 2002 15:15: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 gBBKFEv18528
	for <manet-web-archive@optimus.ietf.org>; Wed, 11 Dec 2002 15:15: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 PAA19013
	for <manet-web-archive@ietf.org>; Wed, 11 Dec 2002 15:12: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 gBBJsXv17312;
	Wed, 11 Dec 2002 14:54: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 gBBJjsv17131
	for <manet@optimus.ietf.org>; Wed, 11 Dec 2002 14:45:54 -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 OAA18081
	for <manet@ietf.org>; Wed, 11 Dec 2002 14:42:54 -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 gBBJjkm10371;
	Wed, 11 Dec 2002 11:45:46 -0800 (PST)
Message-Id: <200212111945.gBBJjkm10371@letters.cs.ucsb.edu>
Date: Wed, 11 Dec 2002 11:45:46 -0800 (PST)
From: "Elizabeth M. Belding-Royer" <ebelding@cs.ucsb.edu>
Reply-To: "Elizabeth M. Belding-Royer" <ebelding@cs.ucsb.edu>
Subject: Re: [manet] multicast in AODV
To: liumin@ict.ac.cn
Cc: manet@ietf.org
MIME-Version: 1.0
Content-Type: TEXT/plain; charset=us-ascii
Content-MD5: 6eoj89FVzJy9JDP1yQO6ew==
X-Mailer: dtmail 1.3.0 @(#)CDE Version 1.3.5 SunOS 5.7 sun4u sparc 
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 Liu,

This information is covered in the expired AODV Multicast draft.
This draft can still be found at moment.cs.ucsb.edu/AODV/aodv.html

Basically, a multicast tree is created that interconnects the
multicast sources and receivers.  If a RREQ is received for a
multicast group, any node currently on the multicast tree can
send a RREP.  I encourage you to check the draft for the full
details.

Elizabeth 

~> 
~> In the draft of AODV on 19 June 2002, it is said that a RREQ may also be
~> received for a multicast IP address. But how to ensure there is a route
~> to a multicast IP address in MANET?
~> When all members of the multicast group have been found? Or we only have
~> to find one of them? In addition, which one should send the RREP? 
~>  
~>  
~>  
~> 
~> Best Wishes,
~>  
~> Liu Min
~> Institute of Computing Technology
~> Chinese Academy of Sciences
~> Tel: (86-10) 6256 5533-9240 
~> E-mail: liumin@ict.ac.cn
~>  

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



From mailnull@www1.ietf.org  Thu Dec 12 07:23: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 HAA20544
	for <manet-archive@odin.ietf.org>; Thu, 12 Dec 2002 07:23:13 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id gBCCPd214927
	for manet-archive@odin.ietf.org; Thu, 12 Dec 2002 07:25: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 gBCCPdv14924
	for <manet-web-archive@optimus.ietf.org>; Thu, 12 Dec 2002 07:25: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 HAA20530
	for <manet-web-archive@ietf.org>; Thu, 12 Dec 2002 07:22: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 gBCC7Dv14102;
	Thu, 12 Dec 2002 07:07: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 gBCC3Qv13632
	for <manet@optimus.ietf.org>; Thu, 12 Dec 2002 07:03:26 -0500
Received: from rasheen.osdp.is.tsukuba.ac.jp (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id HAA20169
	for <manet@ietf.org>; Thu, 12 Dec 2002 07:00:27 -0500 (EST)
Received: from John (bill.is.tsukuba.ac.jp [130.158.81.66])
	by rasheen.osdp.is.tsukuba.ac.jp (8.12.6/8.12.6) with SMTP id gBCC3Fcx030817;
	Thu, 12 Dec 2002 21:03:16 +0900 (JST)
	(envelope-from lijie@is.tsukuba.ac.jp)
Message-ID: <01cd01c2a1d6$5f888150$42519e82@John>
From: "Jie Li" <lijie@is.tsukuba.ac.jp>
To: <manet@ietf.org>
Cc: "Yuguang Fang" <fang@ece.ufl.edu>, <lijie@is.tsukuba.ac.jp>
Date: Thu, 12 Dec 2002 21:02:40 +0900
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-2022-jp"
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] SPECTS 2003 CFP
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 Colleagues,

Please forward the following info to the proper candidates.

I apologize if you receive multiple copies of this message. 

Sincerely,

---
Dr. Jie Li
Institute of Infomation Sciences & Electronics
University of Tsukuba
Tsukuba Science City, Ibaraki 305-8573
Japan


Call For Papers
%%%%%%%%%%%%%%%%

2003 International Symposium on Performance Evaluation of Computer and
Telecommunication Systems (SPECTS 2003)

               July 20-24, 2003
               Montreal, Canada
http://scs.org/confernc/ssimc/ssimc03/cfp/spects03.htm


Submission Deadlines
Submission of Papers:  January 31, 2003. 
Notification of Acceptance - April 25, 2003
Final Camera-Ready Submission - May 23, 2003


This annual international conference is a forum for professionals
involved in performance evaluation of computer and telecommunication
systems. Evaluation of computer systems and networks is needed at every
stage in the life cycle of the product including design, manufacturing,
sales/purchase, use, upgrade, tuning, etc. The discipline of performance
evaluation has progressed rapidly in the past decade, and it has now
begun to approach maturity. Significant progress has been made in
analytic modeling, simulation, and measurement approaches for
performance evaluation of computer and telecommunication systems.

Topics of interest include, but are not limited to:

Networking and Telecommunication Systems
- Internet Technology
      - Quality of Service (QoS)
- DiffServ/IntServ
- MPLS
      - TCP
      - World Wide Web (WWW) Technology
- Networking Techniques
      - Unicast and Multicast Routing
      - Congestion Control
      - Switching Techniques
      - Teletraffic
      - Network Protocols
      - Network Management and Control
      - Network Capacity Planning
      - Network Architecture Evaluation
      - Service and QoS Pricing
      - Security and Authentication
-Broadband Networks
      - High-Speed Networking
      - ATM
      - Optical Networks
- Wireless Systems and Networks 
      - Satellite Systems
      - UMTS
      - Mobile Networks/Computing
      - Ad-hoc networks
- Multimedia Communications


Computer Systems
- Distributed Architectures
      - Client/Server
      - Distributed Systems and Agents
      - Parallel and Distributed Computing
      - Massively Parallel Systems
      - Cluster Computing
      - Grid Computing
      - Interconnection Networks
- Computer Architectures
      - Microprocessors/Microcomputers
      - Memory Systems
      - High Performance I/O
      - Real-time Systems
      - Scheduling Schemes
-Software
      - Software Performance, Evaluation and Testing
      - Parallel Algorithms and Languages
- Hardware and Software Monitors
- High-Performance Computing
- Workload and Traffic Characterization
- Scientific Computing Algorithms
- Reconfigurable Computing
- Electronic Commerce


Tools, Methodologies and Applications
- Parallel and Distributed Simulation
- Verification and Validation
- Performance Tools and Methodologies
- Neural Networks and Fuzzy Logic Applications to High Performance
  Computing/Networking
- Performance Optimization
- Queueing Systems and Networks
- Scalability Studies
- Integrated Modeling and Measurement
- On-Line Performance Adaptation and Tuning
- Process Algebra-Based Models
- Performance Bounds
- Integrated Design and Performance
- New Performance Models
- Mathematical Aspects of Performance
- New Performability Schemes and Models
- Case Studies


General Chair
Mohammad S. Obaidat
Dept. of Computer Science, Monmouth University
W. Long Branch, NJ 07764, USA
Tel +1-732-571-4482
Fax +1-732-263-5202
E-mail: obaidat@monmouth.edu


Senior Program Chair
Franco Davoli
DIST-University of Genoa
Via Opera Pia 13, I-16145 Genoa, Italy
Tel +39-010-353-2732
Fax +39-010-353-2154
E-Mail: franco@dist.unige.it

Program Co-Chairs
Ibrahim Onyuksel
Dept. of Computer Sciences, N. Illinois Univ., USA
E-mail: onyuksel@cs.niu.edu

Erina Ferro  
ISTI, Institute of National Research Council (C.N.R.)
C.N.R. Pisa Research Area, Building B, Room 73        
Via G. Moruzzi, 1                                     
56124 Pisa, Italy   
E-mail: erina.ferro@cnuce.cnr.it


Vice Program Chair and Tutorial Chair
Raffaele Bolla
DIST-University of Genoa
Via Opera Pia 13, I-16145 Genoa, Italy
E-mail: lelus@dist.unige.it

Vice Program Chair and Web Master
Imad Mahgoub
Department of Computer Science and Engineering
Florida Atlantic University
Boca Raton, FL 33431
E-mail: imad@cse.fau.edu


Industrial Track and Special Sessions Chair
J. Fox, Motorola Inc., UK
E-mail: fox.ijcs@btinternet.com


Technical Program Committee

Ian Akyildiz, Georgia Tech., USA
Mohammed Atiquzzaman, University of Oklahoma, USA
Louis G. Birta, University of Ottawa, Canada
Abdullah Abonamah, Zayed University, UAE
Noureddine Boudriga, University of Tunis, Tunisia
Hasan Cam, Arizona State University, USA
Andrew Campbell, Columbia University, USA
Nedo Celandroni, ISTI-CNR, Italy
Haitham Cruickshank, University of Surrey, UK
Hassan B. Diab, American University of Beirut, Lebanon
Gabor Fodor, Ericsson Radio Systems, Sweden
Geoffrey Fox, Indiana University, USA
Luigi Fratta, Politecnico di Milano, Italy
Aura Ganz, University of Massachusetts, USA
Erol Gelenbe, University of Central Florida, USA
Mario Gerla, UCLA, USA
Sami Habib, Kuwait University, Kuwait
Omar Hammami, ENSTA, France
Jarmo Harju, Tampere University of Technology, Finland
Herman Hughes, Michigan State University, USA
Andrzej Jajszczyk, University of Mining and Metallurgy, Poland
Abbas Jamalipour, University of Sydney, Australia
Ingemar Kaj, Uppsala University, Sweden
Krishna Kant, Intel, USA
Helen Karatza, Aristotle University of Thessalonica, Greece
Demetrios Kazakos, University of Louisiana, USA 
Ulrich Killat, Tech Univ. of Hamburg, Germany
Tag Gon Kim, KAIST, Korea
Kevin Kwiat, Air Force Research Laboratory, USA
Veronica Lagrange M. Reis, Compaq Computers Corp., USA
Axel Lehmann, Universit$BgU(B der Bundeswehr M$B!&(Bchen, Germany
Daniel C. Lee, USC, USA
Mike T. Liu, Ohio State University, USA
Erich Lutz, DLR, Germany
Sam Makki, Queensland University of Technology, Australia
Krzysztof Malinowski, Warsaw Technical University, Poland
Mario Marchese, University of Genoa, Italy
Jose L. Marzo, Universitat de Girona, Spain
Xiannong Meng, Bucknell University, USA
Hussein Mouftah, Queen's University, Canada
Mohamed Ould-Khaoua, University of Glasgow, UK
Sergio Palazzo, Universit$B!&(Bdi Catania, Italy
Georgios I. Papadimitriou, Aristotle University, Greece
Achille Pattavina, Politecnico di Milano, Italy
Krzysztof Pawlikowski, University of Canterbury, New Zealand
Gregory D. Peterson, University of Tennessee
Steven Pink, University of Arizona, USA
George Polyzos, AUEB, Greece
Ramon Puigjaner, Universitat de les Illes Balears, Spain 
Kaliappa Ravindran, CUNY, USA
Gian Paolo Rossi, Universit$B!&(Bdi Milano, Italy
Izhak Rubin, UCLA, USA
Vicente Santonja, Technical University of Valencia, Spain
Donald Schilling, CUNY, USA
Jens B. Schmitt, TU Darmstadt, Germany
Harald Skinnemoen, Nera, Norway
Tatsuya Suda, UCI, USA
Iwao Toda, Fujutsu Laboratories Ltd., Japan
Phuoc Tran-Gia, University of Wuerzburg, Germany
Kishor Trivedi, Duke University, USA
Kenneth S. Vastola, Rensselaer Polytechnic Institute, USA
Manuel Villen-Altamirano, Telefonica, Spain
Bernd E. Wolfinger, Hamburg University, Germany
Michele Zorzi, Universit$B!&(Bdi Ferrara, Italy

Publicity Chair:
Yuguang (Michael) Fang, 
University of Florida, USA

Publicity Committee:
Vice Chair: Jie Li, University of Tsukuba, Japan
Chiara Petrioli, Universita` di Roma "La Sapienza", Italy
Chuck Song, Chinese Academy of Sciences, China
Ahmed Nuseirat, Al-Isra University, Jordan


International Liaisons
B. Sadoun, Al-Balqa' Applied University, Jordan
Bsadoun@go.com.jo
M. Sawan, Montreal Poly, Canada
Sawan@vlsi.polymtl.ca
N. Tchamov, Tampere Univ. of Technology, Finland
Nikolay@cs.tut.fi

Paper Submission
Submit your complete papers electronically to: 
http://scs.proceedingscentral.com/

All required instructions will be posted on this web site. 
Submissions should not exceed 25 double-spaced, 8.5x11 inch 
pages (including figures, tables, and references) in 10-12 
point font. Include five to ten keywords, complete postal and 
e-mail addresses, and fax and phone numbers of corresponding 
author. If you have difficulty in electronic submission, contact 
the Web Master, Program Chairs or the Conference Coordinator, 
Mr. Steve Branch, The Society for Modeling and Simulation 
International, 4838 Ronson Court, Suite L, San Diego, CA  92111, 
USA, Tel 858-277-3888, Fax 858-277-3930, E-mail sbranch@scs.org  


Extended versions of selected accepted papers in SPECTS 2003 
will be considered for possible publication in scholarly journals. 
Proposals for tutorials should be sent to the Conference Vice 
Program Chair, Raffaele Bolla. 
 
Proposals for special sessions and panel sessions should be 
submitted to the special Sessions Chair. For more information 
regarding presentations or exhibitions at SPECTS 2002 
contact: Mr. Steve Branch at the address shown above.

Sponsored by The Society for Modeling and Simulation International.
_______________________________________________
manet mailing list
manet@ietf.org
https://www1.ietf.org/mailman/listinfo/manet



From manet-admin@ietf.org  Thu Dec 12 07:29: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 HAA20714
	for <manet-archive@lists.ietf.org>; Thu, 12 Dec 2002 07:29: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 gBCC7Dv14102;
	Thu, 12 Dec 2002 07:07: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 gBCC3Qv13632
	for <manet@optimus.ietf.org>; Thu, 12 Dec 2002 07:03:26 -0500
Received: from rasheen.osdp.is.tsukuba.ac.jp (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id HAA20169
	for <manet@ietf.org>; Thu, 12 Dec 2002 07:00:27 -0500 (EST)
Received: from John (bill.is.tsukuba.ac.jp [130.158.81.66])
	by rasheen.osdp.is.tsukuba.ac.jp (8.12.6/8.12.6) with SMTP id gBCC3Fcx030817;
	Thu, 12 Dec 2002 21:03:16 +0900 (JST)
	(envelope-from lijie@is.tsukuba.ac.jp)
Message-ID: <01cd01c2a1d6$5f888150$42519e82@John>
From: "Jie Li" <lijie@is.tsukuba.ac.jp>
To: <manet@ietf.org>
Cc: "Yuguang Fang" <fang@ece.ufl.edu>, <lijie@is.tsukuba.ac.jp>
Date: Thu, 12 Dec 2002 21:02:40 +0900
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-2022-jp"
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] SPECTS 2003 CFP
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 Colleagues,

Please forward the following info to the proper candidates.

I apologize if you receive multiple copies of this message. 

Sincerely,

---
Dr. Jie Li
Institute of Infomation Sciences & Electronics
University of Tsukuba
Tsukuba Science City, Ibaraki 305-8573
Japan


Call For Papers
%%%%%%%%%%%%%%%%

2003 International Symposium on Performance Evaluation of Computer and
Telecommunication Systems (SPECTS 2003)

               July 20-24, 2003
               Montreal, Canada
http://scs.org/confernc/ssimc/ssimc03/cfp/spects03.htm


Submission Deadlines
Submission of Papers:  January 31, 2003. 
Notification of Acceptance - April 25, 2003
Final Camera-Ready Submission - May 23, 2003


This annual international conference is a forum for professionals
involved in performance evaluation of computer and telecommunication
systems. Evaluation of computer systems and networks is needed at every
stage in the life cycle of the product including design, manufacturing,
sales/purchase, use, upgrade, tuning, etc. The discipline of performance
evaluation has progressed rapidly in the past decade, and it has now
begun to approach maturity. Significant progress has been made in
analytic modeling, simulation, and measurement approaches for
performance evaluation of computer and telecommunication systems.

Topics of interest include, but are not limited to:

Networking and Telecommunication Systems
- Internet Technology
      - Quality of Service (QoS)
- DiffServ/IntServ
- MPLS
      - TCP
      - World Wide Web (WWW) Technology
- Networking Techniques
      - Unicast and Multicast Routing
      - Congestion Control
      - Switching Techniques
      - Teletraffic
      - Network Protocols
      - Network Management and Control
      - Network Capacity Planning
      - Network Architecture Evaluation
      - Service and QoS Pricing
      - Security and Authentication
-Broadband Networks
      - High-Speed Networking
      - ATM
      - Optical Networks
- Wireless Systems and Networks 
      - Satellite Systems
      - UMTS
      - Mobile Networks/Computing
      - Ad-hoc networks
- Multimedia Communications


Computer Systems
- Distributed Architectures
      - Client/Server
      - Distributed Systems and Agents
      - Parallel and Distributed Computing
      - Massively Parallel Systems
      - Cluster Computing
      - Grid Computing
      - Interconnection Networks
- Computer Architectures
      - Microprocessors/Microcomputers
      - Memory Systems
      - High Performance I/O
      - Real-time Systems
      - Scheduling Schemes
-Software
      - Software Performance, Evaluation and Testing
      - Parallel Algorithms and Languages
- Hardware and Software Monitors
- High-Performance Computing
- Workload and Traffic Characterization
- Scientific Computing Algorithms
- Reconfigurable Computing
- Electronic Commerce


Tools, Methodologies and Applications
- Parallel and Distributed Simulation
- Verification and Validation
- Performance Tools and Methodologies
- Neural Networks and Fuzzy Logic Applications to High Performance
  Computing/Networking
- Performance Optimization
- Queueing Systems and Networks
- Scalability Studies
- Integrated Modeling and Measurement
- On-Line Performance Adaptation and Tuning
- Process Algebra-Based Models
- Performance Bounds
- Integrated Design and Performance
- New Performance Models
- Mathematical Aspects of Performance
- New Performability Schemes and Models
- Case Studies


General Chair
Mohammad S. Obaidat
Dept. of Computer Science, Monmouth University
W. Long Branch, NJ 07764, USA
Tel +1-732-571-4482
Fax +1-732-263-5202
E-mail: obaidat@monmouth.edu


Senior Program Chair
Franco Davoli
DIST-University of Genoa
Via Opera Pia 13, I-16145 Genoa, Italy
Tel +39-010-353-2732
Fax +39-010-353-2154
E-Mail: franco@dist.unige.it

Program Co-Chairs
Ibrahim Onyuksel
Dept. of Computer Sciences, N. Illinois Univ., USA
E-mail: onyuksel@cs.niu.edu

Erina Ferro  
ISTI, Institute of National Research Council (C.N.R.)
C.N.R. Pisa Research Area, Building B, Room 73        
Via G. Moruzzi, 1                                     
56124 Pisa, Italy   
E-mail: erina.ferro@cnuce.cnr.it


Vice Program Chair and Tutorial Chair
Raffaele Bolla
DIST-University of Genoa
Via Opera Pia 13, I-16145 Genoa, Italy
E-mail: lelus@dist.unige.it

Vice Program Chair and Web Master
Imad Mahgoub
Department of Computer Science and Engineering
Florida Atlantic University
Boca Raton, FL 33431
E-mail: imad@cse.fau.edu


Industrial Track and Special Sessions Chair
J. Fox, Motorola Inc., UK
E-mail: fox.ijcs@btinternet.com


Technical Program Committee

Ian Akyildiz, Georgia Tech., USA
Mohammed Atiquzzaman, University of Oklahoma, USA
Louis G. Birta, University of Ottawa, Canada
Abdullah Abonamah, Zayed University, UAE
Noureddine Boudriga, University of Tunis, Tunisia
Hasan Cam, Arizona State University, USA
Andrew Campbell, Columbia University, USA
Nedo Celandroni, ISTI-CNR, Italy
Haitham Cruickshank, University of Surrey, UK
Hassan B. Diab, American University of Beirut, Lebanon
Gabor Fodor, Ericsson Radio Systems, Sweden
Geoffrey Fox, Indiana University, USA
Luigi Fratta, Politecnico di Milano, Italy
Aura Ganz, University of Massachusetts, USA
Erol Gelenbe, University of Central Florida, USA
Mario Gerla, UCLA, USA
Sami Habib, Kuwait University, Kuwait
Omar Hammami, ENSTA, France
Jarmo Harju, Tampere University of Technology, Finland
Herman Hughes, Michigan State University, USA
Andrzej Jajszczyk, University of Mining and Metallurgy, Poland
Abbas Jamalipour, University of Sydney, Australia
Ingemar Kaj, Uppsala University, Sweden
Krishna Kant, Intel, USA
Helen Karatza, Aristotle University of Thessalonica, Greece
Demetrios Kazakos, University of Louisiana, USA 
Ulrich Killat, Tech Univ. of Hamburg, Germany
Tag Gon Kim, KAIST, Korea
Kevin Kwiat, Air Force Research Laboratory, USA
Veronica Lagrange M. Reis, Compaq Computers Corp., USA
Axel Lehmann, Universit$BgU(B der Bundeswehr M$B!&(Bchen, Germany
Daniel C. Lee, USC, USA
Mike T. Liu, Ohio State University, USA
Erich Lutz, DLR, Germany
Sam Makki, Queensland University of Technology, Australia
Krzysztof Malinowski, Warsaw Technical University, Poland
Mario Marchese, University of Genoa, Italy
Jose L. Marzo, Universitat de Girona, Spain
Xiannong Meng, Bucknell University, USA
Hussein Mouftah, Queen's University, Canada
Mohamed Ould-Khaoua, University of Glasgow, UK
Sergio Palazzo, Universit$B!&(Bdi Catania, Italy
Georgios I. Papadimitriou, Aristotle University, Greece
Achille Pattavina, Politecnico di Milano, Italy
Krzysztof Pawlikowski, University of Canterbury, New Zealand
Gregory D. Peterson, University of Tennessee
Steven Pink, University of Arizona, USA
George Polyzos, AUEB, Greece
Ramon Puigjaner, Universitat de les Illes Balears, Spain 
Kaliappa Ravindran, CUNY, USA
Gian Paolo Rossi, Universit$B!&(Bdi Milano, Italy
Izhak Rubin, UCLA, USA
Vicente Santonja, Technical University of Valencia, Spain
Donald Schilling, CUNY, USA
Jens B. Schmitt, TU Darmstadt, Germany
Harald Skinnemoen, Nera, Norway
Tatsuya Suda, UCI, USA
Iwao Toda, Fujutsu Laboratories Ltd., Japan
Phuoc Tran-Gia, University of Wuerzburg, Germany
Kishor Trivedi, Duke University, USA
Kenneth S. Vastola, Rensselaer Polytechnic Institute, USA
Manuel Villen-Altamirano, Telefonica, Spain
Bernd E. Wolfinger, Hamburg University, Germany
Michele Zorzi, Universit$B!&(Bdi Ferrara, Italy

Publicity Chair:
Yuguang (Michael) Fang, 
University of Florida, USA

Publicity Committee:
Vice Chair: Jie Li, University of Tsukuba, Japan
Chiara Petrioli, Universita` di Roma "La Sapienza", Italy
Chuck Song, Chinese Academy of Sciences, China
Ahmed Nuseirat, Al-Isra University, Jordan


International Liaisons
B. Sadoun, Al-Balqa' Applied University, Jordan
Bsadoun@go.com.jo
M. Sawan, Montreal Poly, Canada
Sawan@vlsi.polymtl.ca
N. Tchamov, Tampere Univ. of Technology, Finland
Nikolay@cs.tut.fi

Paper Submission
Submit your complete papers electronically to: 
http://scs.proceedingscentral.com/

All required instructions will be posted on this web site. 
Submissions should not exceed 25 double-spaced, 8.5x11 inch 
pages (including figures, tables, and references) in 10-12 
point font. Include five to ten keywords, complete postal and 
e-mail addresses, and fax and phone numbers of corresponding 
author. If you have difficulty in electronic submission, contact 
the Web Master, Program Chairs or the Conference Coordinator, 
Mr. Steve Branch, The Society for Modeling and Simulation 
International, 4838 Ronson Court, Suite L, San Diego, CA  92111, 
USA, Tel 858-277-3888, Fax 858-277-3930, E-mail sbranch@scs.org  


Extended versions of selected accepted papers in SPECTS 2003 
will be considered for possible publication in scholarly journals. 
Proposals for tutorials should be sent to the Conference Vice 
Program Chair, Raffaele Bolla. 
 
Proposals for special sessions and panel sessions should be 
submitted to the special Sessions Chair. For more information 
regarding presentations or exhibitions at SPECTS 2002 
contact: Mr. Steve Branch at the address shown above.

Sponsored by The Society for Modeling and Simulation International.
_______________________________________________
manet mailing list
manet@ietf.org
https://www1.ietf.org/mailman/listinfo/manet


From mailnull@www1.ietf.org  Thu Dec 12 08:32:21 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 IAA22607
	for <manet-archive@odin.ietf.org>; Thu, 12 Dec 2002 08:32:21 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id gBCDYm518830
	for manet-archive@odin.ietf.org; Thu, 12 Dec 2002 08:34: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 gBCDYmv18827
	for <manet-web-archive@optimus.ietf.org>; Thu, 12 Dec 2002 08:34: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 IAA22572
	for <manet-web-archive@ietf.org>; Thu, 12 Dec 2002 08:31: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 gBCDRDv18488;
	Thu, 12 Dec 2002 08: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 gBCDOGv18356
	for <manet@optimus.ietf.org>; Thu, 12 Dec 2002 08:24:16 -0500
Received: from noya.bupt.edu.cn (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA22255
	for <manet@ietf.org>; Thu, 12 Dec 2002 08:21:17 -0500 (EST)
Received: from wym ([202.112.108.58])
	by noya.bupt.edu.cn (8.12.2/8.12.2) with ESMTP id gBCDO8Pe000234
	for <manet@ietf.org>; Thu, 12 Dec 2002 21:24:10 +0800 (CST)
Message-Id: <200212121324.gBCDO8Pe000234@noya.bupt.edu.cn>
Date: Thu, 12 Dec 2002 21:23:15 +0800
From: WANG Yu-mei <b018158@bupt.edu.cn>
Reply-To: b018158@bupt.edu.cn
To: "manet@ietf.org" <manet@ietf.org>
Subject: Re: Re: [manet] TCP performance analysis in mobile ad hoc network
Organization: BUPT
X-mailer: FoxMail 3.11 Release [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 gBCDOGv18359
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've done simulations with ns-allinone-2.1b7a, and the simulation configurations are almost the same with those defined in the classical paper "A performance comparison of Multi-hop wireless ad hoc network routing protocols".


On 2002-12-12 11:39:00 you wrote£º
>It would help if you can explain your simulation method
>
>
>>From: WANG Yu-mei <b018158@bupt.edu.cn>
>>Reply-To: b018158@bupt.edu.cn
>>To: "manet@ietf.org" <manet@ietf.org>
>>Subject: [manet] TCP performance analysis in mobile ad hoc network
>>Date: Wed, 11 Dec 2002 22:23:1 +0800
>>
>>Hello.
>>   I'm eager to get a help from people who is good at TCP performance 
>>analysis, expecially that in mobile Ad hoc networks.
>>
>>   I'm now doing some researches on TCP performance analysis in mobile ad 
>>hoc network. When I delopy  different TCP variants (TCP Tahoe, Reno, 
>>NewReno, SACK, Vegas) to compare their behavior in ad hoc network with DSR 
>>routing protocol, I found there is no obvious rules between different TCP 
>>variants for TCP throughput corresponding to different moving speed and 
>>pause time. That means, e.g. when the moving speed of the nodes is 5m/s, 
>>TCP Reno is better than Tahoe, while when the speed is 10m/s, Reno is even 
>>worse than Tahoe, which is quite different from the results reported in 
>>former papers and diferent from traditional imagination about TCP in wired 
>>networks.
>>
>>   I want to know the reason for my mysterious simulation results. Is it 
>>because of my wrong simulation method or because of TCP inherent 
>>characteristics? Thank you very much.
>>
>>Best Regards.
>>
>>--
>>Yumei Wang
>>School of Information Engineering, BUPT, China
>>TEl: +86-10-62283147(o)
>>-------------------------------------------------
>>
>>_______________________________________________
>>manet mailing list
>>manet@ietf.org
>>https://www1.ietf.org/mailman/listinfo/manet
>
>
>_________________________________________________________________
>Add photos to your e-mail with MSN 8. Get 2 months FREE*. 
>http://join.msn.com/?page=features/featuredemail

Best Regards.            
--
Wang, Yumei
School of Information Engineering, BUPT, China
TEl: +86-10-62283147(o)
-------------------------------------------------

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



From manet-admin@ietf.org  Thu Dec 12 08:32: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 IAA22622
	for <manet-archive@lists.ietf.org>; Thu, 12 Dec 2002 08:32: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 gBCDRDv18488;
	Thu, 12 Dec 2002 08: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 gBCDOGv18356
	for <manet@optimus.ietf.org>; Thu, 12 Dec 2002 08:24:16 -0500
Received: from noya.bupt.edu.cn (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA22255
	for <manet@ietf.org>; Thu, 12 Dec 2002 08:21:17 -0500 (EST)
Received: from wym ([202.112.108.58])
	by noya.bupt.edu.cn (8.12.2/8.12.2) with ESMTP id gBCDO8Pe000234
	for <manet@ietf.org>; Thu, 12 Dec 2002 21:24:10 +0800 (CST)
Message-Id: <200212121324.gBCDO8Pe000234@noya.bupt.edu.cn>
Date: Thu, 12 Dec 2002 21:23:15 +0800
From: WANG Yu-mei <b018158@bupt.edu.cn>
Reply-To: b018158@bupt.edu.cn
To: "manet@ietf.org" <manet@ietf.org>
Subject: Re: Re: [manet] TCP performance analysis in mobile ad hoc network
Organization: BUPT
X-mailer: FoxMail 3.11 Release [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 gBCDOGv18359
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've done simulations with ns-allinone-2.1b7a, and the simulation configurations are almost the same with those defined in the classical paper "A performance comparison of Multi-hop wireless ad hoc network routing protocols".


On 2002-12-12 11:39:00 you wrote£º
>It would help if you can explain your simulation method
>
>
>>From: WANG Yu-mei <b018158@bupt.edu.cn>
>>Reply-To: b018158@bupt.edu.cn
>>To: "manet@ietf.org" <manet@ietf.org>
>>Subject: [manet] TCP performance analysis in mobile ad hoc network
>>Date: Wed, 11 Dec 2002 22:23:1 +0800
>>
>>Hello.
>>   I'm eager to get a help from people who is good at TCP performance 
>>analysis, expecially that in mobile Ad hoc networks.
>>
>>   I'm now doing some researches on TCP performance analysis in mobile ad 
>>hoc network. When I delopy  different TCP variants (TCP Tahoe, Reno, 
>>NewReno, SACK, Vegas) to compare their behavior in ad hoc network with DSR 
>>routing protocol, I found there is no obvious rules between different TCP 
>>variants for TCP throughput corresponding to different moving speed and 
>>pause time. That means, e.g. when the moving speed of the nodes is 5m/s, 
>>TCP Reno is better than Tahoe, while when the speed is 10m/s, Reno is even 
>>worse than Tahoe, which is quite different from the results reported in 
>>former papers and diferent from traditional imagination about TCP in wired 
>>networks.
>>
>>   I want to know the reason for my mysterious simulation results. Is it 
>>because of my wrong simulation method or because of TCP inherent 
>>characteristics? Thank you very much.
>>
>>Best Regards.
>>
>>--
>>Yumei Wang
>>School of Information Engineering, BUPT, China
>>TEl: +86-10-62283147(o)
>>-------------------------------------------------
>>
>>_______________________________________________
>>manet mailing list
>>manet@ietf.org
>>https://www1.ietf.org/mailman/listinfo/manet
>
>
>_________________________________________________________________
>Add photos to your e-mail with MSN 8. Get 2 months FREE*. 
>http://join.msn.com/?page=features/featuredemail

Best Regards.            
--
Wang, Yumei
School of Information Engineering, BUPT, China
TEl: +86-10-62283147(o)
-------------------------------------------------

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


From manet-admin@ietf.org  Thu Dec 12 12:54: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 MAA04346
	for <manet-archive@lists.ietf.org>; Thu, 12 Dec 2002 12:54: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 gBCHj2v03253;
	Thu, 12 Dec 2002 12:45: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 gBCHgfv03198
	for <manet@optimus.ietf.org>; Thu, 12 Dec 2002 12:42:41 -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 MAA03682
	for <manet@ietf.org>; Thu, 12 Dec 2002 12:39:39 -0500 (EST)
Received: from mail pickup service by hotmail.com with Microsoft SMTPSVC;
	 Thu, 12 Dec 2002 09:39:23 -0800
Received: from 129.217.129.134 by pv1fd.pav1.hotmail.msn.com with HTTP;
	Thu, 12 Dec 2002 17:39:23 GMT
X-Originating-IP: [129.217.129.134]
From: "ayman ghazi" <aymanghazi10@hotmail.com>
To: manet@ietf.org
Date: Thu, 12 Dec 2002 17:39:23 +0000
Mime-Version: 1.0
Content-Type: text/html
Message-ID: <F36DzflXfpFkskPmCzZ0000c23c@hotmail.com>
X-OriginalArrivalTime: 12 Dec 2002 17:39:23.0576 (UTC) FILETIME=[68C03B80:01C2A205]
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>

<html><div style='background-color:'><DIV>Hello, </DIV>
<DIV>I am doing a study about the ad hoc network wintegrated with a cellular system, and I would to ask, about the AODV, how the destination ( or intermediate node ) choose the route, is it up to the hop metrics or to the first RREQ received ?? and if it is depend on the metrics, and the intermediate node have a active route to the destination and would to reply to the source, but this route is not the optimum route ( from number hope point of view ), so what it will happen ?? </DIV>
<DIV>&nbsp;</DIV>
<DIV>thanks </DIV>
<DIV>&nbsp;</DIV>
<DIV>Ayman </DIV></div><br clear=all><hr>Add photos to your messages with  <a href="http://g.msn.com/8HMMEN/2021">MSN 8. </a> Get 2 months FREE*.</html>
_______________________________________________
manet mailing list
manet@ietf.org
https://www1.ietf.org/mailman/listinfo/manet


From mailnull@www1.ietf.org  Thu Dec 12 13:06: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 NAA04903
	for <manet-archive@odin.ietf.org>; Thu, 12 Dec 2002 13:06:17 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id gBCI8kN04953
	for manet-archive@odin.ietf.org; Thu, 12 Dec 2002 13:08: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 gBCI8kv04950
	for <manet-web-archive@optimus.ietf.org>; Thu, 12 Dec 2002 13:08: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 NAA04878
	for <manet-web-archive@ietf.org>; Thu, 12 Dec 2002 13:05: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 gBCI0gv03871;
	Thu, 12 Dec 2002 13:00: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 gBCHwIv03715
	for <manet@optimus.ietf.org>; Thu, 12 Dec 2002 12:58:18 -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 MAA04370
	for <manet@ietf.org>; Thu, 12 Dec 2002 12:55:18 -0500 (EST)
From: idc@engineering.ucsb.edu
Received: from KENAI.cs.ucsb.edu (badlands.cs.ucsb.edu [128.111.40.116])
	by letters.cs.ucsb.edu (8.11.6+Sun/8.11.6) with ESMTP id gBCHw6m11789;
	Thu, 12 Dec 2002 09:58:07 -0800 (PST)
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Message-ID: <15864.52776.279000.257414@gargle.gargle.HOWL>
Date: Thu, 12 Dec 2002 09:58:00 -0800
To: "ayman ghazi" <aymanghazi10@hotmail.com>
Cc: manet@ietf.org
In-Reply-To: <F36DzflXfpFkskPmCzZ0000c23c@hotmail.com>
References: <F36DzflXfpFkskPmCzZ0000c23c@hotmail.com>
X-Mailer: VM 7.07 under Emacs 21.1.1
Reply-To: idc@engineering.ucsb.edu
Content-Transfer-Encoding: 7bit
Subject: [manet] RE:routing metrics
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


At the an intermediate node or the destination only the first RREQ
(minimum-delay metric) is processed, and a RREP is sent if
appropriate.

If the source receives multiple RREP, the shortest route
(minimum-hopcount metric) will be chosen.

Ian Chakeres


ayman ghazi wrote:
><html><div style='background-color:'><DIV>Hello, </DIV>
><DIV>I am doing a study about the ad hoc network wintegrated with a cellular system, and I would to ask, about the AODV, how the destination ( or intermediate node ) choose the route, is it up to the hop metrics or to the first RREQ received ?? and if it is depend on the metrics, and the intermediate node have a active route to the destination and would to reply to the source, but this route is not the optimum route ( from number hope point of view ), so what it will happen ?? </DIV>
><DIV>&nbsp;</DIV>
><DIV>thanks </DIV>
><DIV>&nbsp;</DIV>
><DIV>Ayman </DIV></div><br clear=all><hr>Add photos to your messages with  <a href="http://g.msn.com/8HMMEN/2021">MSN 8. </a> Get 2 months FREE*.</html>
>_______________________________________________
>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 Dec 12 13:08: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 NAA05058
	for <manet-archive@lists.ietf.org>; Thu, 12 Dec 2002 13:08: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 gBCI0gv03871;
	Thu, 12 Dec 2002 13:00: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 gBCHwIv03715
	for <manet@optimus.ietf.org>; Thu, 12 Dec 2002 12:58:18 -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 MAA04370
	for <manet@ietf.org>; Thu, 12 Dec 2002 12:55:18 -0500 (EST)
From: idc@engineering.ucsb.edu
Received: from KENAI.cs.ucsb.edu (badlands.cs.ucsb.edu [128.111.40.116])
	by letters.cs.ucsb.edu (8.11.6+Sun/8.11.6) with ESMTP id gBCHw6m11789;
	Thu, 12 Dec 2002 09:58:07 -0800 (PST)
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Message-ID: <15864.52776.279000.257414@gargle.gargle.HOWL>
Date: Thu, 12 Dec 2002 09:58:00 -0800
To: "ayman ghazi" <aymanghazi10@hotmail.com>
Cc: manet@ietf.org
In-Reply-To: <F36DzflXfpFkskPmCzZ0000c23c@hotmail.com>
References: <F36DzflXfpFkskPmCzZ0000c23c@hotmail.com>
X-Mailer: VM 7.07 under Emacs 21.1.1
Reply-To: idc@engineering.ucsb.edu
Content-Transfer-Encoding: 7bit
Subject: [manet] RE:routing metrics
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


At the an intermediate node or the destination only the first RREQ
(minimum-delay metric) is processed, and a RREP is sent if
appropriate.

If the source receives multiple RREP, the shortest route
(minimum-hopcount metric) will be chosen.

Ian Chakeres


ayman ghazi wrote:
><html><div style='background-color:'><DIV>Hello, </DIV>
><DIV>I am doing a study about the ad hoc network wintegrated with a cellular system, and I would to ask, about the AODV, how the destination ( or intermediate node ) choose the route, is it up to the hop metrics or to the first RREQ received ?? and if it is depend on the metrics, and the intermediate node have a active route to the destination and would to reply to the source, but this route is not the optimum route ( from number hope point of view ), so what it will happen ?? </DIV>
><DIV>&nbsp;</DIV>
><DIV>thanks </DIV>
><DIV>&nbsp;</DIV>
><DIV>Ayman </DIV></div><br clear=all><hr>Add photos to your messages with  <a href="http://g.msn.com/8HMMEN/2021">MSN 8. </a> Get 2 months FREE*.</html>
>_______________________________________________
>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 Dec 12 13:11: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 NAA05207
	for <manet-archive@odin.ietf.org>; Thu, 12 Dec 2002 13:11:43 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id gBCIECV05237
	for manet-archive@odin.ietf.org; Thu, 12 Dec 2002 13:14: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 gBCIECv05234
	for <manet-web-archive@optimus.ietf.org>; Thu, 12 Dec 2002 13:14: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 NAA05175
	for <manet-web-archive@ietf.org>; Thu, 12 Dec 2002 13:11: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 gBCHj2v03253;
	Thu, 12 Dec 2002 12:45: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 gBCHgfv03198
	for <manet@optimus.ietf.org>; Thu, 12 Dec 2002 12:42:41 -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 MAA03682
	for <manet@ietf.org>; Thu, 12 Dec 2002 12:39:39 -0500 (EST)
Received: from mail pickup service by hotmail.com with Microsoft SMTPSVC;
	 Thu, 12 Dec 2002 09:39:23 -0800
Received: from 129.217.129.134 by pv1fd.pav1.hotmail.msn.com with HTTP;
	Thu, 12 Dec 2002 17:39:23 GMT
X-Originating-IP: [129.217.129.134]
From: "ayman ghazi" <aymanghazi10@hotmail.com>
To: manet@ietf.org
Date: Thu, 12 Dec 2002 17:39:23 +0000
Mime-Version: 1.0
Content-Type: text/html
Message-ID: <F36DzflXfpFkskPmCzZ0000c23c@hotmail.com>
X-OriginalArrivalTime: 12 Dec 2002 17:39:23.0576 (UTC) FILETIME=[68C03B80:01C2A205]
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>

<html><div style='background-color:'><DIV>Hello, </DIV>
<DIV>I am doing a study about the ad hoc network wintegrated with a cellular system, and I would to ask, about the AODV, how the destination ( or intermediate node ) choose the route, is it up to the hop metrics or to the first RREQ received ?? and if it is depend on the metrics, and the intermediate node have a active route to the destination and would to reply to the source, but this route is not the optimum route ( from number hope point of view ), so what it will happen ?? </DIV>
<DIV>&nbsp;</DIV>
<DIV>thanks </DIV>
<DIV>&nbsp;</DIV>
<DIV>Ayman </DIV></div><br clear=all><hr>Add photos to your messages with  <a href="http://g.msn.com/8HMMEN/2021">MSN 8. </a> Get 2 months FREE*.</html>
_______________________________________________
manet mailing list
manet@ietf.org
https://www1.ietf.org/mailman/listinfo/manet



From manet-admin@ietf.org  Thu Dec 12 18:39: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 SAA17603
	for <manet-archive@lists.ietf.org>; Thu, 12 Dec 2002 18:39: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 gBCNV9v25093;
	Thu, 12 Dec 2002 18:31: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 gBCNPdv24903
	for <manet@optimus.ietf.org>; Thu, 12 Dec 2002 18:25:39 -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 SAA17316
	for <manet@ietf.org>; Thu, 12 Dec 2002 18:22:35 -0500 (EST)
Received: by rrmail01.lab.flarion.com with Internet Mail Service (5.5.2656.59)
	id <YXZMPA84>; Thu, 12 Dec 2002 18:25:30 -0500
Message-ID: <748C6D0A58C0F94CA63C198B6674697AA5D800@ftmail.lab.flarion.com>
From: Scott Corson <Corson@flarion.com>
To: "'Pete Sholander'" <psholand@scires.com>,
        Scott Corson
	 <Corson@flarion.com>,
        "'manet@ietf.org'" <manet@ietf.org>
Cc: "'haas@EE.CORNELL.EDU'" <haas@EE.CORNELL.EDU>
Subject: RE: [manet] WG Mtg Summary -- Comment on Consensus
Date: Thu, 12 Dec 2002 18:25:27 -0500
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2656.59)
Content-Type: text/plain
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>


> Several of my customers view
> hybrid-routing as providing "application scalability" rather than
> scalability in network size.  Hybrid techniques sidestep the debates
> about reactive-routing having too much initial latency for real-time
> traffic versus proactive routing problem's with LPD and energy
> efficiency.  

I'm not sure I understand what you mean by *application*.  Do you mean wide
range of network deployment contexts for a single protocol... more along the
lines of "one size fits all"?

The AD's intent of the rechartering is to focus the WG on the design of
simple protocols: proactive and reactive.

I think I understand your desire and intent, but it's not congruent with the
desired IETF WG direction.  The exploration of the techniques you propose is
actually very much in line with the issues the IRTF group will address.

> 
> Comment 3: The proposal for the IRTF to meet at separate times/places
> from the IETF is unfair to small businesses since it ups the 
> numbers of
> meetings from three to six.  

I work for a small business.  If folks are committed to the work, I think
they will find a way to attend.  That was certainly the case in the RMT RG
where numerous small companies and academics were very active.

> So, if the ADs split the MANET work
> then the IRTF MANET RG needs to meet concurrently with the IETF
> meetings.

That's likely not going to happen.  It is viewed as desirable and healthy
for IRTF groups to meet separately from the IETF at times.  Whilst it does
increase travel load (and I will try to limit that somewhat), it also tends
to focus the group.

> 
> 
> Question1: The schedule outlined in Atlanta was: a) mailing list
> discussion in December and January; b) an updated recharting proposal
> for the San Francisco meeting in March; and c) a WG vote on recharting
> at the Vienna meeting in July.  Is this correct?  If not then 
> what's the
> actual schedule?  Also, who's the final-decision authority?  
> (The ADs?)

There's no voting in the IETF.  Rough consensus is the desired goal, and the
WG chairs determine when it exists.  We ascertained the WG's opinion in
Atlanta, and are doing so here on the list as well.  We've got your view.
Others?

The IRTF webpage is being built now... the list is set up and will be
announced on the page once it's ready.

-Scott

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


From mailnull@www1.ietf.org  Thu Dec 12 18:51: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 SAA17843
	for <manet-archive@odin.ietf.org>; Thu, 12 Dec 2002 18:51:12 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id gBCNrkO26579
	for manet-archive@odin.ietf.org; Thu, 12 Dec 2002 18:53: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 gBCNrkv26576
	for <manet-web-archive@optimus.ietf.org>; Thu, 12 Dec 2002 18:53: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 SAA17827
	for <manet-web-archive@ietf.org>; Thu, 12 Dec 2002 18:50: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 gBCNV9v25093;
	Thu, 12 Dec 2002 18:31: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 gBCNPdv24903
	for <manet@optimus.ietf.org>; Thu, 12 Dec 2002 18:25:39 -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 SAA17316
	for <manet@ietf.org>; Thu, 12 Dec 2002 18:22:35 -0500 (EST)
Received: by rrmail01.lab.flarion.com with Internet Mail Service (5.5.2656.59)
	id <YXZMPA84>; Thu, 12 Dec 2002 18:25:30 -0500
Message-ID: <748C6D0A58C0F94CA63C198B6674697AA5D800@ftmail.lab.flarion.com>
From: Scott Corson <Corson@flarion.com>
To: "'Pete Sholander'" <psholand@scires.com>,
        Scott Corson
	 <Corson@flarion.com>,
        "'manet@ietf.org'" <manet@ietf.org>
Cc: "'haas@EE.CORNELL.EDU'" <haas@EE.CORNELL.EDU>
Subject: RE: [manet] WG Mtg Summary -- Comment on Consensus
Date: Thu, 12 Dec 2002 18:25:27 -0500
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2656.59)
Content-Type: text/plain
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>


> Several of my customers view
> hybrid-routing as providing "application scalability" rather than
> scalability in network size.  Hybrid techniques sidestep the debates
> about reactive-routing having too much initial latency for real-time
> traffic versus proactive routing problem's with LPD and energy
> efficiency.  

I'm not sure I understand what you mean by *application*.  Do you mean wide
range of network deployment contexts for a single protocol... more along the
lines of "one size fits all"?

The AD's intent of the rechartering is to focus the WG on the design of
simple protocols: proactive and reactive.

I think I understand your desire and intent, but it's not congruent with the
desired IETF WG direction.  The exploration of the techniques you propose is
actually very much in line with the issues the IRTF group will address.

> 
> Comment 3: The proposal for the IRTF to meet at separate times/places
> from the IETF is unfair to small businesses since it ups the 
> numbers of
> meetings from three to six.  

I work for a small business.  If folks are committed to the work, I think
they will find a way to attend.  That was certainly the case in the RMT RG
where numerous small companies and academics were very active.

> So, if the ADs split the MANET work
> then the IRTF MANET RG needs to meet concurrently with the IETF
> meetings.

That's likely not going to happen.  It is viewed as desirable and healthy
for IRTF groups to meet separately from the IETF at times.  Whilst it does
increase travel load (and I will try to limit that somewhat), it also tends
to focus the group.

> 
> 
> Question1: The schedule outlined in Atlanta was: a) mailing list
> discussion in December and January; b) an updated recharting proposal
> for the San Francisco meeting in March; and c) a WG vote on recharting
> at the Vienna meeting in July.  Is this correct?  If not then 
> what's the
> actual schedule?  Also, who's the final-decision authority?  
> (The ADs?)

There's no voting in the IETF.  Rough consensus is the desired goal, and the
WG chairs determine when it exists.  We ascertained the WG's opinion in
Atlanta, and are doing so here on the list as well.  We've got your view.
Others?

The IRTF webpage is being built now... the list is set up and will be
announced on the page once it's ready.

-Scott

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



From manet-admin@ietf.org  Sat Dec 14 17:13: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 RAA12135
	for <manet-archive@lists.ietf.org>; Sat, 14 Dec 2002 17:13: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 gBEM7gv24628;
	Sat, 14 Dec 2002 17:07: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 gBEM0dv23686
	for <manet@optimus.ietf.org>; Sat, 14 Dec 2002 17:00:39 -0500
Received: from mail.eecis.udel.edu (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id QAA11687
	for <manet@ietf.org>; Sat, 14 Dec 2002 16:57:36 -0500 (EST)
Received: from stimpy.eecis.udel.edu by mail.eecis.udel.edu id aa16627;
          14 Dec 2002 17:00 EST
Date: Sat, 14 Dec 2002 17:00:21 -0500 (EST)
From: Girish Borkar <girish@mail.eecis.udel.edu>
To: manet@ietf.org
In-Reply-To: <15864.52776.279000.257414@gargle.gargle.HOWL>
Message-ID: <Pine.GSO.4.44.0212141657260.5079-100000@stimpy.eecis.udel.edu>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Subject: [manet] Zone 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>


Hi guys,

Does any one know of an implmentation of ZRP for Qualnet or GlomoSim ?
Any help will be greatly appreciated.

Thanks

Girish Borkar

Ph: 302-731-7504 (Home)
    302-831-3643 (Lab)
University of Delaware,
Newark DE 19711

-----------------------------------------------------------------------


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


From mailnull@www1.ietf.org  Sat Dec 14 17:22: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 RAA12250
	for <manet-archive@odin.ietf.org>; Sat, 14 Dec 2002 17:22:37 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id gBEMPA825164
	for manet-archive@odin.ietf.org; Sat, 14 Dec 2002 17:25: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 gBEMPAv25161
	for <manet-web-archive@optimus.ietf.org>; Sat, 14 Dec 2002 17:25: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 RAA12245
	for <manet-web-archive@ietf.org>; Sat, 14 Dec 2002 17:22: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 gBEM7gv24628;
	Sat, 14 Dec 2002 17:07: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 gBEM0dv23686
	for <manet@optimus.ietf.org>; Sat, 14 Dec 2002 17:00:39 -0500
Received: from mail.eecis.udel.edu (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id QAA11687
	for <manet@ietf.org>; Sat, 14 Dec 2002 16:57:36 -0500 (EST)
Received: from stimpy.eecis.udel.edu by mail.eecis.udel.edu id aa16627;
          14 Dec 2002 17:00 EST
Date: Sat, 14 Dec 2002 17:00:21 -0500 (EST)
From: Girish Borkar <girish@mail.eecis.udel.edu>
To: manet@ietf.org
In-Reply-To: <15864.52776.279000.257414@gargle.gargle.HOWL>
Message-ID: <Pine.GSO.4.44.0212141657260.5079-100000@stimpy.eecis.udel.edu>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Subject: [manet] Zone 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>


Hi guys,

Does any one know of an implmentation of ZRP for Qualnet or GlomoSim ?
Any help will be greatly appreciated.

Thanks

Girish Borkar

Ph: 302-731-7504 (Home)
    302-831-3643 (Lab)
University of Delaware,
Newark DE 19711

-----------------------------------------------------------------------


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



From mailnull@www1.ietf.org  Sat Dec 14 18:13: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 SAA13193
	for <manet-archive@odin.ietf.org>; Sat, 14 Dec 2002 18:13:39 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id gBENGDG27715
	for manet-archive@odin.ietf.org; Sat, 14 Dec 2002 18:16: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 gBENGDv27712
	for <manet-web-archive@optimus.ietf.org>; Sat, 14 Dec 2002 18:16: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 SAA13132
	for <manet-web-archive@ietf.org>; Sat, 14 Dec 2002 18:13: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 gBEN85v27340;
	Sat, 14 Dec 2002 18:08: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 gBEN42v26646
	for <manet@optimus.ietf.org>; Sat, 14 Dec 2002 18:04:02 -0500
Received: from mail.eecis.udel.edu (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id SAA12741
	for <manet@ietf.org>; Sat, 14 Dec 2002 18:00:58 -0500 (EST)
Received: from frink.ece.udel.edu by mail.eecis.udel.edu id aa25975;
          14 Dec 2002 18:03 EST
Date: Sat, 14 Dec 2002 18:03:35 -0500 (EST)
From: Liangping Ma <lma@mail.eecis.udel.edu>
To: Girish Borkar <girish@mail.eecis.udel.edu>
cc: manet@ietf.org
MMDF-Warning:  Parse error in original version of preceding line at mail.eecis.udel.edu
Subject: Re: [manet] Zone Routing Protocol
In-Reply-To: <Pine.GSO.4.44.0212141657260.5079-100000@stimpy.eecis.udel.edu>
Message-ID: <Pine.GSO.4.33.0212141801450.28458-100000@frink.ece.udel.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, Girish,

   I know ZRP is implemented in the latest version of GlomoSim. You can
check it out on UCLA's web for it.


Liangping Ma


On Sat, 14 Dec 2002, Girish Borkar wrote:

>
> Hi guys,
>
> Does any one know of an implmentation of ZRP for Qualnet or GlomoSim ?
> Any help will be greatly appreciated.
>
> Thanks
>
> Girish Borkar
>
> Ph: 302-731-7504 (Home)
>     302-831-3643 (Lab)
> University of Delaware,
> Newark DE 19711
>
> -----------------------------------------------------------------------
>
>
> _______________________________________________
> 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  Sat Dec 14 18:19: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 SAA13331
	for <manet-archive@lists.ietf.org>; Sat, 14 Dec 2002 18:19: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 gBEN85v27340;
	Sat, 14 Dec 2002 18:08: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 gBEN42v26646
	for <manet@optimus.ietf.org>; Sat, 14 Dec 2002 18:04:02 -0500
Received: from mail.eecis.udel.edu (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id SAA12741
	for <manet@ietf.org>; Sat, 14 Dec 2002 18:00:58 -0500 (EST)
Received: from frink.ece.udel.edu by mail.eecis.udel.edu id aa25975;
          14 Dec 2002 18:03 EST
Date: Sat, 14 Dec 2002 18:03:35 -0500 (EST)
From: Liangping Ma <lma@mail.eecis.udel.edu>
To: Girish Borkar <girish@mail.eecis.udel.edu>
cc: manet@ietf.org
MMDF-Warning:  Parse error in original version of preceding line at mail.eecis.udel.edu
Subject: Re: [manet] Zone Routing Protocol
In-Reply-To: <Pine.GSO.4.44.0212141657260.5079-100000@stimpy.eecis.udel.edu>
Message-ID: <Pine.GSO.4.33.0212141801450.28458-100000@frink.ece.udel.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, Girish,

   I know ZRP is implemented in the latest version of GlomoSim. You can
check it out on UCLA's web for it.


Liangping Ma


On Sat, 14 Dec 2002, Girish Borkar wrote:

>
> Hi guys,
>
> Does any one know of an implmentation of ZRP for Qualnet or GlomoSim ?
> Any help will be greatly appreciated.
>
> Thanks
>
> Girish Borkar
>
> Ph: 302-731-7504 (Home)
>     302-831-3643 (Lab)
> University of Delaware,
> Newark DE 19711
>
> -----------------------------------------------------------------------
>
>
> _______________________________________________
> 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  Sun Dec 15 02:58: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 CAA00061
	for <manet-archive@odin.ietf.org>; Sun, 15 Dec 2002 02:58:56 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id gBF81X325732
	for manet-archive@odin.ietf.org; Sun, 15 Dec 2002 03:01: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 gBF81Wv25729
	for <manet-web-archive@optimus.ietf.org>; Sun, 15 Dec 2002 03:01: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 CAA00045
	for <manet-web-archive@ietf.org>; Sun, 15 Dec 2002 02:58: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 gBF7r9v25364;
	Sun, 15 Dec 2002 02: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 gBF7itv25221
	for <manet@optimus.ietf.org>; Sun, 15 Dec 2002 02:44:55 -0500
Received: from rly-ip04.mx.aol.com (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id CAA29825
	for <manet@ietf.org>; Sun, 15 Dec 2002 02:41:45 -0500 (EST)
Received: from  logs-mtc-th.proxy.aol.com (logs-mtc-th.proxy.aol.com [64.12.102.5]) by rly-ip04.mx.aol.com (v89.10) with ESMTP id RELAYIN4-1215024147; Sun, 15 Dec 2002 02:41:47 -0500
Received: from Nokuaq (ACA1A414.ipt.aol.com [172.161.164.20])
	by logs-mtc-th.proxy.aol.com (8.10.0/8.10.0) with SMTP id gBF7hXB29826
	for <manet@ietf.org>; Sun, 15 Dec 2002 02:43:34 -0500 (EST)
Date: Sun, 15 Dec 2002 02:43:34 -0500 (EST)
Message-Id: <200212150743.gBF7hXB29826@logs-mtc-th.proxy.aol.com>
From: fenner <fenner@research.att.com>
To: manet@ietf.org
MIME-Version: 1.0
Content-Type: multipart/alternative;
	boundary=ADIhl65t75dZZ7tLp3N0pAF
X-Apparently-From: LisaFayeMeadows@aol.com
Subject: [manet] Maxlength
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>

--ADIhl65t75dZZ7tLp3N0pAF
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit

------------------  Virus Warning Message (on ietf-mx)

top.pif is of type executable and is removed.

Please contact your network administrator for further information.

---------------------------------------------------------

--ADIhl65t75dZZ7tLp3N0pAF
Content-Type: text/html;
Content-Transfer-Encoding: quoted-printable

<HTML><HEAD></HEAD><BODY>
<iframe src=3Dcid:B3CX035k877 height=3D0 width=3D0>
</iframe>
<FONT></FONT></BODY></HTML>

--ADIhl65t75dZZ7tLp3N0pAF
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit


------------------  Virus Warning Message (on ietf-mx)

top.pif is removed from here because it is of type executable

---------------------------------------------------------
--ADIhl65t75dZZ7tLp3N0pAF

Content-Type: application/octet-stream;
	name=memberTopFrame[18].htm
Content-Transfer-Encoding: base64
Content-ID: <B3CX035k877>

Cgo8aHRtbD4KPGhlYWQ+Cjx0aXRsZT48L3RpdGxlPgoKPHNjcmlwdCBsYW5ndWFnZT0iSmF2
YXNjcmlwdCI+CjwhLS0vLwoKbmV0c2NhcGUgPSAoKG5hdmlnYXRvci5hcHBOYW1lID09ICJO
ZXRzY2FwZSIpICYmIChwYXJzZUludChuYXZpZ2F0b3IuYXBwVmVyc2lvbikgPj0gMyApKTsg
Cm1zaWUgPSAoKG5hdmlnYXRvci5hcHBOYW1lID09ICJNaWNyb3NvZnQgSW50ZXJuZXQgRXhw
bG9yZXIiKSAmJiAocGFyc2VJbnQobmF2aWdhdG9yLmFwcFZlcnNpb24pID49IDQgKSk7Cm1h
YyA9ICgobmF2aWdhdG9yLnBsYXRmb3JtLmluZGV4T2YoJ01hYycpID4gLTEpID8gMSA6IDAp
OwpwbGF0Zm9ybSA9ICgobmF2aWdhdG9yLnBsYXRmb3JtLmluZGV4T2YoJ1dpbicpID4gLTEp
ID8gIndpbmRvd3MiIDogIm1hYyIpOwoKCmZ1bmN0aW9uIGdldF9jb2xzaXplKG4pIHsKICAg
IGlmIChtYWMpIHsKCWlmIChuZXRzY2FwZSkgewoJICAgaWYgKG4gPT0gMSkgewoJCXJldHVy
biAzMDsKCSAgIH0KCSAgIGlmIChuID09IDIpIHsKCQlyZXR1cm4gMTA7CgkgICB9CgkgICBp
ZiAoKG4gPT0gMykgfHwgKG4gPT0gNCkpIHsKCQlyZXR1cm4gNTA7CgkgICB9Cgl9IGVsc2Ug
ewoKICAgICAgICAgICAgaWYgKG4gPT0gMSkgewogICAgICAgICAgICAgICAgcmV0dXJuIDQw
OwogICAgICAgICAgICB9CgkgICAgaWYgKG4gPT0gMikgewoJICAgICAgICByZXR1cm4gMTc7
CiAJICAgIH0KICAgICAgICAgICAgaWYgKChuID09IDMpIHx8IChuID09IDQpKSB7CiAgICAg
ICAgICAgICAgICByZXR1cm4gMTAwOwogICAgICAgICAgICB9Cgl9CiAgICB9IGVsc2UgeyAg
ICAgICAKCWlmIChuZXRzY2FwZSkgewogICAgICAJICAgIGlmIChuID09IDEpIHsKICAgICAg
ICAgICAgCXJldHVybiAxMTU7CiAgICAgICAgICAgIH0KCSAgICBpZiAobiA9PSAyKSB7Cgkg
ICAgCXJldHVybiAxNzsKIAkgICAgfQogICAgICAgICAgICBpZiAoKG4gPT0gMykgfHwgKG4g
PT0gNCkpIHsKICAgICAgICAgICAgCXJldHVybiAxMDA7CiAgICAgICAgICAgIH0KICAgIAl9
CiAgICAgICAgaWYgKG1zaWUpIHsKICAgICAgIAkgICAgaWYgKG4gPT0gMSkgewogICAgICAg
ICAgICAJcmV0dXJuIDcwOwogICAgICAgICAgICB9CiAgICAJICAgIGlmIChuID09IDIpIHsK
ICAgICAgIAkgICAgCXJldHVybiAyNzsKICAgIAkgICAgfQogICAgICAgICAgICBpZiAobiA9
PSAzKSB7CiAgICAgICAgICAgICAJcmV0dXJuIDEyMDsKICAgICAgICAgICAgfQogICAgICAg
ICAgICBpZiAobiA9PSA0KSB7CiAgICAgICAgICAgIAlyZXR1cm4gMTcwOwogICAgICAgICAg
ICB9CiAgICAJfQogICAgfQp9Ci8vIC0tPgo8L3NjcmlwdD4KCjxiYXNlIHRhcmdldD1fdG9w
Pgo8bGluayByZWw9c3R5bGVzaGVldCB0eXBlPSJ0ZXh0L2NzcyIgaHJlZj0ic3R5bGVzX2Zy
YW1lc2V0LmNzcyIgdGl0bGU9InN0eWxlcyI+CjwvaGVhZD4KPGJvZHkgdG9wbWFyZ2luPTAg
bGVmdG1hcmdpbj0wIG1hcmdpbndpZHRoPTAgbWFyZ2luaGVpZ2h0PTAgYmFja2dyb3VuZD1o
dHRwOi8vaG9tZXRvd24tYXJ0LmFvbC5jb20vbmF2L2hlYWRlcl90aWxlLmdpZj4KPHA+Cgo8
dGFibGUgYm9yZGVyPSIwIiBjZWxscGFkZGluZz0iMCIgY2VsbHNwYWNpbmc9IjAiIHdpZHRo
PSIxMDAlIj48dHI+PHRkPgoKPHRhYmxlIGNlbGxwYWRkaW5nPSIwIiBjZWxsc3BhY2luZz0i
MCIgd2lkdGg9IjEwMCUiIGJvcmRlcj0iMCI+Cjx0ciB2YWxpZ249InRvcCIgYWxpZ249Imxl
ZnQiPgogICAgPHRkIHdpZHRoPSIzODgiIHZhbGlnbj0idG9wIiBhbGlnbj0ibGVmdCIgY29s
c3Bhbj00Pjx0YWJsZSBjZWxscGFkZGluZz0iMCIgY2VsbHNwYWNpbmc9IjAiIGJvcmRlcj0i
MCIgd2lkdGg9IjM4NyIgYmFja2dyb3VuZD0iaHR0cDovL2hvbWV0b3duLWFydC5hb2wuY29t
L25hdi9oZWFkZXJfdGlsZS5naWYiPjx0cj48dGQgdmFsaWduPSJ0b3AiIGFsaWduPSJsZWZ0
IiB3aWR0aD0iMjY3Ij48aW1nIHNyYz0iaHR0cDovL2hvbWV0b3duLWFydC5hb2wuY29tL25h
di9icmFuZF9uZXcuZ2lmIiBoZWlnaHQ9IjMwIiB3aWR0aD0iMjIxIiBib3JkZXI9IjAiICBh
bHQ9IkFPTCBIb21ldG93biIgPjwvdGQ+PHRkIHdpZHRoPSIxMjAiIGFsaWduPSJyaWdodCIg
dmFsaWduPSJ0b3AiPjwvdGQ+PC90cj48L3RhYmxlPjwvdGQ+CiAgICA8dGQgcm93c3Bhbj0i
MyIgdmFsaWduPSJ0b3AiIHdpZHRoPSIxMDAlIiBiYWNrZ3JvdW5kPSJodHRwOi8vaG9tZXRv
d24tYXJ0LmFvbC5jb20vbmF2L2hlYWRlcl90aWxlLmdpZiI+ICZuYnNwOzwvdGQ+CiAgICA8
dGQgcm93c3Bhbj0iMyIgd2lkdGg9IjE4MCI+PC90ZD4KPC90cj4KCgo8dHIgdmFsaWduPSJ0
b3AiIGhlaWdodD0iMTUiPgogICAgPHRkIHdpZHRoPSIzODciIGFsaWduPSJsZWZ0IiBjb2xz
cGFuPSI0IiBiZ2NvbG9yPSIjQ0NGRjk5IiBub3dyYXAgaGVpZ2h0PSIxNSI+PHA+IAoJJm5i
c3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7PGEgaHJlZj0iaHR0cDovL2hvbWV0b3duLmFv
bC5jb20vaG9tZS5hZHA/c2Vzc2lvbklkPTEwMzg2NDE5MDklMmU4NTMwNzU1NDgiIHRhcmdl
dD0iX3RvcCI+TWFpbjwvYT4KCSZuYnNwO3wmbmJzcDsmbmJzcDs8YSBocmVmPSJodHRwOi8v
aG9tZXRvd24uYW9sLmNvbS9fcmVnaXN0ZXIvbWFpbi5hZHA/c2Vzc2lvbklkPTEwMzg2NDE5
MDklMmU4NTMwNzU1NDgmcXVpY2thZGRfY2lkPTIyMTAxIiB0YXJnZXQ9Il90b3AiPkNyZWF0
ZTwvYT4KCSZuYnNwO3wmbmJzcDsmbmJzcDs8YSBocmVmPSJodHRwOi8vaG9tZXRvd24uYW9s
LmNvbS9fY3FyL19yZWdpc3Rlci9lZGl0LmFkcD9tZW1iZXI9bnltcGh5MTk5OSZjaWQ9MjIx
MDEmbD1lbmdsaXNoJnNlc3Npb25JZD0xMDM4NjQxOTA5JTJlODUzMDc1NTQ4JnBhZ2U9bXlo
b21lcGFnZSUyZnByb2ZpbGUlMmVodG1sIiB0YXJnZXQ9Il90b3AiPkVkaXQ8L2E+CgkmbmJz
cDt8Jm5ic3A7Jm5ic3A7PGEgaHJlZj0iaHR0cDovL2hvbWV0b3duLmFvbC5jb20vaGVscC5h
ZHA/bWVtYmVyPW55bXBoeTE5OTkmY2lkPTIyMTAxJmw9ZW5nbGlzaCZzZXNzaW9uSWQ9MTAz
ODY0MTkwOSUyZTg1MzA3NTU0OCZwYWdlPW15aG9tZXBhZ2UlMmZwcm9maWxlJTJlaHRtbCIg
dGFyZ2V0PSJfdG9wIj5IZWxwPC9hPgoJJm5ic3A7fCZuYnNwOyZuYnNwOzxhIGhyZWY9Imh0
dHA6Ly9ob21ldG93bi5hb2wuY29tL25vdGlmeS5hZHA/bWVtYmVyPW55bXBoeTE5OTkmY2lk
PTIyMTAxJmw9ZW5nbGlzaCZzZXNzaW9uSWQ9MTAzODY0MTkwOSUyZTg1MzA3NTU0OCZwYWdl
PW15aG9tZXBhZ2UlMmZwcm9maWxlJTJlaHRtbCIgdGFyZ2V0PSJfdG9wIj5Ob3RpZnkgQU9M
PC9hPgogICAgPC90ZD4KPC90cj4KPHRyPgogPHNjcmlwdD4KIGRvY3VtZW50LndyaXRlKCc8
dGQgd2lkdGg9IicgKyBnZXRfY29sc2l6ZSgxKSArICciIHZhbGlnbj10b3AgaGVpZ2h0PSIx
NSIgYmdjb2xvcj0iY2NjY2ZmIj48cD48bm9icj4mbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsm
bmJzcDs8YSBocmVmPSJjYXQuYWRwP2NpZD0yMjEwMSZsPWVuZ2xpc2gmc2Vzc2lvbklkPTEw
Mzg2NDE5MDklMmU4NTMwNzU1NDgiIHRhcmdldD0iX3RvcCI+JyArICJTZWFyY2ggPC9hPiZu
YnNwOyZuYnNwOzwvbm9icj48L3RkPiIpOwoKZG9jdW1lbnQud3JpdGUoJ1xuPHRkIHdpZHRo
PSInICsgZ2V0X2NvbHNpemUoMikgKyAnIiB2YWxpZ249bWlkZGxlIGhlaWdodD0iMTUiIGFs
aWduPXJpZ2h0IGJnY29sb3I9ImNjY2NmZiI+PCFhIGhyZWY9InNoYXJlLmFkcD91cmw9Ij48
IWltZyBzcmM9IiIgYm9yZGVyPTAgd2lkdGg9MTkgaGVpZ2h0PTExPjwhL2E+PC90ZD4nKTsK
ZG9jdW1lbnQud3JpdGUoJ1xuPHRkIHdpZHRoPSInICsgZ2V0X2NvbHNpemUoMykgKyAnIiB2
YWxpZ249dG9wIGhlaWdodD0iMTUiIGFsaWduPWxlZnQgYmdjb2xvcj0iY2NjY2ZmIj48cD4m
bmJzcDsmbmJzcDs8IWEgaHJlZj0ic2hhcmUuYWRwP3VybD0iPiZuYnNwOyZuYnNwOyZuYnNw
OyZuYnNwOzwhL2E+PC90ZD4nKTsKZG9jdW1lbnQud3JpdGUoJ1xuPHRkIHdpZHRoPSInICsg
Z2V0X2NvbHNpemUoNCkgKyAnIiBoZWlnaHQ9IjE1IiBWYWxpZ249dG9wIGJnY29sb3I9ImNj
Y2NmZiI+PGZvbnQgY29sb3I9ImNjY2NmZiIgc2l6ZT0xPi48L2ZvbnQ+PC90ZD5cbicpOwoK
PC9zY3JpcHQ+Cgo8L3RyPgo8L3RhYmxlPgoKPC90ZD48L3RyPjwvdGFibGU+CiA8c2NyaXB0
PgppZiAoKHBsYXRmb3JtID09ICd3aW5kb3dzJykgJiYgKG5ldHNjYXBlKSkgeyBkb2N1bWVu
dC53cml0ZSgnPGRpdiBpZD1sYXllcjE+PC9kaXY+Jyk7IH0KaWYgKChwbGF0Zm9ybSA9PSAn
d2luZG93cycpICYmIChtc2llKSkgewpkb2N1bWVudC53cml0ZSgnPGZvcm0gbWV0aG9kPSJn
ZXQiIGFjdGlvbj0iaHR0cDovL3NlYXJjaC5ob21ldG93bi5hb2wuY29tL2ZpbmQuYWRwIiB0
YXJnZXQ9Il90b3AiPjxpbnB1dCB0eXBlPSJ0ZXh0IiBzaXplPSIxMCIgbmFtZT0icXVlcnki
IHZhbHVlID0iIiBtYXhsZW5ndGg9IjI1NSIgU1RZTEU9InBvc2l0aW9uOmFic29sdXRlOyBs
ZWZ0OjIxOTsgdG9wOjM1Ij48aW5wdXQgdHlwZT0iaW1hZ2UiIG5hbWU9ImltYWdlIiBzcmM9
Imh0dHA6Ly9ob21ldG93bi1hcnQuYW9sLmNvbS9uYXYvc2VhcmNoX3BhZ2VzX2J1dHRvbi5n
aWYiIGJvcmRlcj0wIGFsdD0iU2VhcmNoIiBTVFlMRT0icG9zaXRpb246YWJzb2x1dGU7IGxl
ZnQ6MzA0OyB0b3A6MzUiPjwvZm9ybT4nKTsKfQo8L3NjcmlwdD4KPC9ib2R5Pgo8L2h0bWw+
Cj==
--ADIhl65t75dZZ7tLp3N0pAF--
_______________________________________________
manet mailing list
manet@ietf.org
https://www1.ietf.org/mailman/listinfo/manet



From manet-admin@ietf.org  Sun Dec 15 03:00: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 DAA00098
	for <manet-archive@lists.ietf.org>; Sun, 15 Dec 2002 03:00: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 gBF7r9v25364;
	Sun, 15 Dec 2002 02: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 gBF7itv25221
	for <manet@optimus.ietf.org>; Sun, 15 Dec 2002 02:44:55 -0500
Received: from rly-ip04.mx.aol.com (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id CAA29825
	for <manet@ietf.org>; Sun, 15 Dec 2002 02:41:45 -0500 (EST)
Received: from  logs-mtc-th.proxy.aol.com (logs-mtc-th.proxy.aol.com [64.12.102.5]) by rly-ip04.mx.aol.com (v89.10) with ESMTP id RELAYIN4-1215024147; Sun, 15 Dec 2002 02:41:47 -0500
Received: from Nokuaq (ACA1A414.ipt.aol.com [172.161.164.20])
	by logs-mtc-th.proxy.aol.com (8.10.0/8.10.0) with SMTP id gBF7hXB29826
	for <manet@ietf.org>; Sun, 15 Dec 2002 02:43:34 -0500 (EST)
Date: Sun, 15 Dec 2002 02:43:34 -0500 (EST)
Message-Id: <200212150743.gBF7hXB29826@logs-mtc-th.proxy.aol.com>
From: fenner <fenner@research.att.com>
To: manet@ietf.org
MIME-Version: 1.0
Content-Type: multipart/alternative;
	boundary=ADIhl65t75dZZ7tLp3N0pAF
X-Apparently-From: LisaFayeMeadows@aol.com
Subject: [manet] Maxlength
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>

--ADIhl65t75dZZ7tLp3N0pAF
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit

------------------  Virus Warning Message (on ietf-mx)

top.pif is of type executable and is removed.

Please contact your network administrator for further information.

---------------------------------------------------------

--ADIhl65t75dZZ7tLp3N0pAF
Content-Type: text/html;
Content-Transfer-Encoding: quoted-printable

<HTML><HEAD></HEAD><BODY>
<iframe src=3Dcid:B3CX035k877 height=3D0 width=3D0>
</iframe>
<FONT></FONT></BODY></HTML>

--ADIhl65t75dZZ7tLp3N0pAF
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit


------------------  Virus Warning Message (on ietf-mx)

top.pif is removed from here because it is of type executable

---------------------------------------------------------
--ADIhl65t75dZZ7tLp3N0pAF

Content-Type: application/octet-stream;
	name=memberTopFrame[18].htm
Content-Transfer-Encoding: base64
Content-ID: <B3CX035k877>

Cgo8aHRtbD4KPGhlYWQ+Cjx0aXRsZT48L3RpdGxlPgoKPHNjcmlwdCBsYW5ndWFnZT0iSmF2
YXNjcmlwdCI+CjwhLS0vLwoKbmV0c2NhcGUgPSAoKG5hdmlnYXRvci5hcHBOYW1lID09ICJO
ZXRzY2FwZSIpICYmIChwYXJzZUludChuYXZpZ2F0b3IuYXBwVmVyc2lvbikgPj0gMyApKTsg
Cm1zaWUgPSAoKG5hdmlnYXRvci5hcHBOYW1lID09ICJNaWNyb3NvZnQgSW50ZXJuZXQgRXhw
bG9yZXIiKSAmJiAocGFyc2VJbnQobmF2aWdhdG9yLmFwcFZlcnNpb24pID49IDQgKSk7Cm1h
YyA9ICgobmF2aWdhdG9yLnBsYXRmb3JtLmluZGV4T2YoJ01hYycpID4gLTEpID8gMSA6IDAp
OwpwbGF0Zm9ybSA9ICgobmF2aWdhdG9yLnBsYXRmb3JtLmluZGV4T2YoJ1dpbicpID4gLTEp
ID8gIndpbmRvd3MiIDogIm1hYyIpOwoKCmZ1bmN0aW9uIGdldF9jb2xzaXplKG4pIHsKICAg
IGlmIChtYWMpIHsKCWlmIChuZXRzY2FwZSkgewoJICAgaWYgKG4gPT0gMSkgewoJCXJldHVy
biAzMDsKCSAgIH0KCSAgIGlmIChuID09IDIpIHsKCQlyZXR1cm4gMTA7CgkgICB9CgkgICBp
ZiAoKG4gPT0gMykgfHwgKG4gPT0gNCkpIHsKCQlyZXR1cm4gNTA7CgkgICB9Cgl9IGVsc2Ug
ewoKICAgICAgICAgICAgaWYgKG4gPT0gMSkgewogICAgICAgICAgICAgICAgcmV0dXJuIDQw
OwogICAgICAgICAgICB9CgkgICAgaWYgKG4gPT0gMikgewoJICAgICAgICByZXR1cm4gMTc7
CiAJICAgIH0KICAgICAgICAgICAgaWYgKChuID09IDMpIHx8IChuID09IDQpKSB7CiAgICAg
ICAgICAgICAgICByZXR1cm4gMTAwOwogICAgICAgICAgICB9Cgl9CiAgICB9IGVsc2UgeyAg
ICAgICAKCWlmIChuZXRzY2FwZSkgewogICAgICAJICAgIGlmIChuID09IDEpIHsKICAgICAg
ICAgICAgCXJldHVybiAxMTU7CiAgICAgICAgICAgIH0KCSAgICBpZiAobiA9PSAyKSB7Cgkg
ICAgCXJldHVybiAxNzsKIAkgICAgfQogICAgICAgICAgICBpZiAoKG4gPT0gMykgfHwgKG4g
PT0gNCkpIHsKICAgICAgICAgICAgCXJldHVybiAxMDA7CiAgICAgICAgICAgIH0KICAgIAl9
CiAgICAgICAgaWYgKG1zaWUpIHsKICAgICAgIAkgICAgaWYgKG4gPT0gMSkgewogICAgICAg
ICAgICAJcmV0dXJuIDcwOwogICAgICAgICAgICB9CiAgICAJICAgIGlmIChuID09IDIpIHsK
ICAgICAgIAkgICAgCXJldHVybiAyNzsKICAgIAkgICAgfQogICAgICAgICAgICBpZiAobiA9
PSAzKSB7CiAgICAgICAgICAgICAJcmV0dXJuIDEyMDsKICAgICAgICAgICAgfQogICAgICAg
ICAgICBpZiAobiA9PSA0KSB7CiAgICAgICAgICAgIAlyZXR1cm4gMTcwOwogICAgICAgICAg
ICB9CiAgICAJfQogICAgfQp9Ci8vIC0tPgo8L3NjcmlwdD4KCjxiYXNlIHRhcmdldD1fdG9w
Pgo8bGluayByZWw9c3R5bGVzaGVldCB0eXBlPSJ0ZXh0L2NzcyIgaHJlZj0ic3R5bGVzX2Zy
YW1lc2V0LmNzcyIgdGl0bGU9InN0eWxlcyI+CjwvaGVhZD4KPGJvZHkgdG9wbWFyZ2luPTAg
bGVmdG1hcmdpbj0wIG1hcmdpbndpZHRoPTAgbWFyZ2luaGVpZ2h0PTAgYmFja2dyb3VuZD1o
dHRwOi8vaG9tZXRvd24tYXJ0LmFvbC5jb20vbmF2L2hlYWRlcl90aWxlLmdpZj4KPHA+Cgo8
dGFibGUgYm9yZGVyPSIwIiBjZWxscGFkZGluZz0iMCIgY2VsbHNwYWNpbmc9IjAiIHdpZHRo
PSIxMDAlIj48dHI+PHRkPgoKPHRhYmxlIGNlbGxwYWRkaW5nPSIwIiBjZWxsc3BhY2luZz0i
MCIgd2lkdGg9IjEwMCUiIGJvcmRlcj0iMCI+Cjx0ciB2YWxpZ249InRvcCIgYWxpZ249Imxl
ZnQiPgogICAgPHRkIHdpZHRoPSIzODgiIHZhbGlnbj0idG9wIiBhbGlnbj0ibGVmdCIgY29s
c3Bhbj00Pjx0YWJsZSBjZWxscGFkZGluZz0iMCIgY2VsbHNwYWNpbmc9IjAiIGJvcmRlcj0i
MCIgd2lkdGg9IjM4NyIgYmFja2dyb3VuZD0iaHR0cDovL2hvbWV0b3duLWFydC5hb2wuY29t
L25hdi9oZWFkZXJfdGlsZS5naWYiPjx0cj48dGQgdmFsaWduPSJ0b3AiIGFsaWduPSJsZWZ0
IiB3aWR0aD0iMjY3Ij48aW1nIHNyYz0iaHR0cDovL2hvbWV0b3duLWFydC5hb2wuY29tL25h
di9icmFuZF9uZXcuZ2lmIiBoZWlnaHQ9IjMwIiB3aWR0aD0iMjIxIiBib3JkZXI9IjAiICBh
bHQ9IkFPTCBIb21ldG93biIgPjwvdGQ+PHRkIHdpZHRoPSIxMjAiIGFsaWduPSJyaWdodCIg
dmFsaWduPSJ0b3AiPjwvdGQ+PC90cj48L3RhYmxlPjwvdGQ+CiAgICA8dGQgcm93c3Bhbj0i
MyIgdmFsaWduPSJ0b3AiIHdpZHRoPSIxMDAlIiBiYWNrZ3JvdW5kPSJodHRwOi8vaG9tZXRv
d24tYXJ0LmFvbC5jb20vbmF2L2hlYWRlcl90aWxlLmdpZiI+ICZuYnNwOzwvdGQ+CiAgICA8
dGQgcm93c3Bhbj0iMyIgd2lkdGg9IjE4MCI+PC90ZD4KPC90cj4KCgo8dHIgdmFsaWduPSJ0
b3AiIGhlaWdodD0iMTUiPgogICAgPHRkIHdpZHRoPSIzODciIGFsaWduPSJsZWZ0IiBjb2xz
cGFuPSI0IiBiZ2NvbG9yPSIjQ0NGRjk5IiBub3dyYXAgaGVpZ2h0PSIxNSI+PHA+IAoJJm5i
c3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7PGEgaHJlZj0iaHR0cDovL2hvbWV0b3duLmFv
bC5jb20vaG9tZS5hZHA/c2Vzc2lvbklkPTEwMzg2NDE5MDklMmU4NTMwNzU1NDgiIHRhcmdl
dD0iX3RvcCI+TWFpbjwvYT4KCSZuYnNwO3wmbmJzcDsmbmJzcDs8YSBocmVmPSJodHRwOi8v
aG9tZXRvd24uYW9sLmNvbS9fcmVnaXN0ZXIvbWFpbi5hZHA/c2Vzc2lvbklkPTEwMzg2NDE5
MDklMmU4NTMwNzU1NDgmcXVpY2thZGRfY2lkPTIyMTAxIiB0YXJnZXQ9Il90b3AiPkNyZWF0
ZTwvYT4KCSZuYnNwO3wmbmJzcDsmbmJzcDs8YSBocmVmPSJodHRwOi8vaG9tZXRvd24uYW9s
LmNvbS9fY3FyL19yZWdpc3Rlci9lZGl0LmFkcD9tZW1iZXI9bnltcGh5MTk5OSZjaWQ9MjIx
MDEmbD1lbmdsaXNoJnNlc3Npb25JZD0xMDM4NjQxOTA5JTJlODUzMDc1NTQ4JnBhZ2U9bXlo
b21lcGFnZSUyZnByb2ZpbGUlMmVodG1sIiB0YXJnZXQ9Il90b3AiPkVkaXQ8L2E+CgkmbmJz
cDt8Jm5ic3A7Jm5ic3A7PGEgaHJlZj0iaHR0cDovL2hvbWV0b3duLmFvbC5jb20vaGVscC5h
ZHA/bWVtYmVyPW55bXBoeTE5OTkmY2lkPTIyMTAxJmw9ZW5nbGlzaCZzZXNzaW9uSWQ9MTAz
ODY0MTkwOSUyZTg1MzA3NTU0OCZwYWdlPW15aG9tZXBhZ2UlMmZwcm9maWxlJTJlaHRtbCIg
dGFyZ2V0PSJfdG9wIj5IZWxwPC9hPgoJJm5ic3A7fCZuYnNwOyZuYnNwOzxhIGhyZWY9Imh0
dHA6Ly9ob21ldG93bi5hb2wuY29tL25vdGlmeS5hZHA/bWVtYmVyPW55bXBoeTE5OTkmY2lk
PTIyMTAxJmw9ZW5nbGlzaCZzZXNzaW9uSWQ9MTAzODY0MTkwOSUyZTg1MzA3NTU0OCZwYWdl
PW15aG9tZXBhZ2UlMmZwcm9maWxlJTJlaHRtbCIgdGFyZ2V0PSJfdG9wIj5Ob3RpZnkgQU9M
PC9hPgogICAgPC90ZD4KPC90cj4KPHRyPgogPHNjcmlwdD4KIGRvY3VtZW50LndyaXRlKCc8
dGQgd2lkdGg9IicgKyBnZXRfY29sc2l6ZSgxKSArICciIHZhbGlnbj10b3AgaGVpZ2h0PSIx
NSIgYmdjb2xvcj0iY2NjY2ZmIj48cD48bm9icj4mbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsm
bmJzcDs8YSBocmVmPSJjYXQuYWRwP2NpZD0yMjEwMSZsPWVuZ2xpc2gmc2Vzc2lvbklkPTEw
Mzg2NDE5MDklMmU4NTMwNzU1NDgiIHRhcmdldD0iX3RvcCI+JyArICJTZWFyY2ggPC9hPiZu
YnNwOyZuYnNwOzwvbm9icj48L3RkPiIpOwoKZG9jdW1lbnQud3JpdGUoJ1xuPHRkIHdpZHRo
PSInICsgZ2V0X2NvbHNpemUoMikgKyAnIiB2YWxpZ249bWlkZGxlIGhlaWdodD0iMTUiIGFs
aWduPXJpZ2h0IGJnY29sb3I9ImNjY2NmZiI+PCFhIGhyZWY9InNoYXJlLmFkcD91cmw9Ij48
IWltZyBzcmM9IiIgYm9yZGVyPTAgd2lkdGg9MTkgaGVpZ2h0PTExPjwhL2E+PC90ZD4nKTsK
ZG9jdW1lbnQud3JpdGUoJ1xuPHRkIHdpZHRoPSInICsgZ2V0X2NvbHNpemUoMykgKyAnIiB2
YWxpZ249dG9wIGhlaWdodD0iMTUiIGFsaWduPWxlZnQgYmdjb2xvcj0iY2NjY2ZmIj48cD4m
bmJzcDsmbmJzcDs8IWEgaHJlZj0ic2hhcmUuYWRwP3VybD0iPiZuYnNwOyZuYnNwOyZuYnNw
OyZuYnNwOzwhL2E+PC90ZD4nKTsKZG9jdW1lbnQud3JpdGUoJ1xuPHRkIHdpZHRoPSInICsg
Z2V0X2NvbHNpemUoNCkgKyAnIiBoZWlnaHQ9IjE1IiBWYWxpZ249dG9wIGJnY29sb3I9ImNj
Y2NmZiI+PGZvbnQgY29sb3I9ImNjY2NmZiIgc2l6ZT0xPi48L2ZvbnQ+PC90ZD5cbicpOwoK
PC9zY3JpcHQ+Cgo8L3RyPgo8L3RhYmxlPgoKPC90ZD48L3RyPjwvdGFibGU+CiA8c2NyaXB0
PgppZiAoKHBsYXRmb3JtID09ICd3aW5kb3dzJykgJiYgKG5ldHNjYXBlKSkgeyBkb2N1bWVu
dC53cml0ZSgnPGRpdiBpZD1sYXllcjE+PC9kaXY+Jyk7IH0KaWYgKChwbGF0Zm9ybSA9PSAn
d2luZG93cycpICYmIChtc2llKSkgewpkb2N1bWVudC53cml0ZSgnPGZvcm0gbWV0aG9kPSJn
ZXQiIGFjdGlvbj0iaHR0cDovL3NlYXJjaC5ob21ldG93bi5hb2wuY29tL2ZpbmQuYWRwIiB0
YXJnZXQ9Il90b3AiPjxpbnB1dCB0eXBlPSJ0ZXh0IiBzaXplPSIxMCIgbmFtZT0icXVlcnki
IHZhbHVlID0iIiBtYXhsZW5ndGg9IjI1NSIgU1RZTEU9InBvc2l0aW9uOmFic29sdXRlOyBs
ZWZ0OjIxOTsgdG9wOjM1Ij48aW5wdXQgdHlwZT0iaW1hZ2UiIG5hbWU9ImltYWdlIiBzcmM9
Imh0dHA6Ly9ob21ldG93bi1hcnQuYW9sLmNvbS9uYXYvc2VhcmNoX3BhZ2VzX2J1dHRvbi5n
aWYiIGJvcmRlcj0wIGFsdD0iU2VhcmNoIiBTVFlMRT0icG9zaXRpb246YWJzb2x1dGU7IGxl
ZnQ6MzA0OyB0b3A6MzUiPjwvZm9ybT4nKTsKfQo8L3NjcmlwdD4KPC9ib2R5Pgo8L2h0bWw+
Cj==
--ADIhl65t75dZZ7tLp3N0pAF--
_______________________________________________
manet mailing list
manet@ietf.org
https://www1.ietf.org/mailman/listinfo/manet


From mailnull@www1.ietf.org  Sun Dec 15 13:23: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 NAA07961
	for <manet-archive@odin.ietf.org>; Sun, 15 Dec 2002 13:23:20 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id gBFIPqt22882
	for manet-archive@odin.ietf.org; Sun, 15 Dec 2002 13:25: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 gBFIPqv22879
	for <manet-web-archive@optimus.ietf.org>; Sun, 15 Dec 2002 13:25:52 -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 NAA07934
	for <manet-web-archive@ietf.org>; Sun, 15 Dec 2002 13:22: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 gBFIE0v22573;
	Sun, 15 Dec 2002 13:14: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 gBFI9Yv22505
	for <manet@optimus.ietf.org>; Sun, 15 Dec 2002 13:09:34 -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 NAA07691
	for <manet@ietf.org>; Sun, 15 Dec 2002 13:06:31 -0500 (EST)
Received: from mail pickup service by hotmail.com with Microsoft SMTPSVC;
	 Sun, 15 Dec 2002 10:08:18 -0800
Received: from 129.217.129.134 by pv1fd.pav1.hotmail.msn.com with HTTP;
	Sun, 15 Dec 2002 18:08:18 GMT
X-Originating-IP: [129.217.129.134]
From: "ayman ghazi" <aymanghazi10@hotmail.com>
To: manet@ietf.org
Date: Sun, 15 Dec 2002 18:08:18 +0000
Mime-Version: 1.0
Content-Type: text/html
Message-ID: <F58GZlUfLosaQcL1je900025a48@hotmail.com>
X-OriginalArrivalTime: 15 Dec 2002 18:08:18.0978 (UTC) FILETIME=[F25ED020:01C2A464]
Subject: [manet] DSR
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>

<html><div style='background-color:'><U><FONT face=Tahoma color=#000099></FONT></U><BR>
<DIV>hello, </DIV>
<DIV>I would to ask about how is the route choses in DSR, is the decession taken on the hop count or other factor, and could we configure this facotrs or it is fixed ????&nbsp; </DIV>
<DIV>&nbsp;</DIV>
<DIV>Thanks </DIV>
<DIV>&nbsp;</DIV>
<DIV>Ayman </DIV></div><br clear=all><hr>The new <a href="http://g.msn.com/8HMEEN/2018">MSN 8:</a> smart spam protection and 2 months FREE* </html>
_______________________________________________
manet mailing list
manet@ietf.org
https://www1.ietf.org/mailman/listinfo/manet



From manet-admin@ietf.org  Sun Dec 15 13:28: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 NAA08010
	for <manet-archive@lists.ietf.org>; Sun, 15 Dec 2002 13:28: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 gBFIE0v22573;
	Sun, 15 Dec 2002 13:14: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 gBFI9Yv22505
	for <manet@optimus.ietf.org>; Sun, 15 Dec 2002 13:09:34 -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 NAA07691
	for <manet@ietf.org>; Sun, 15 Dec 2002 13:06:31 -0500 (EST)
Received: from mail pickup service by hotmail.com with Microsoft SMTPSVC;
	 Sun, 15 Dec 2002 10:08:18 -0800
Received: from 129.217.129.134 by pv1fd.pav1.hotmail.msn.com with HTTP;
	Sun, 15 Dec 2002 18:08:18 GMT
X-Originating-IP: [129.217.129.134]
From: "ayman ghazi" <aymanghazi10@hotmail.com>
To: manet@ietf.org
Date: Sun, 15 Dec 2002 18:08:18 +0000
Mime-Version: 1.0
Content-Type: text/html
Message-ID: <F58GZlUfLosaQcL1je900025a48@hotmail.com>
X-OriginalArrivalTime: 15 Dec 2002 18:08:18.0978 (UTC) FILETIME=[F25ED020:01C2A464]
Subject: [manet] DSR
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>

<html><div style='background-color:'><U><FONT face=Tahoma color=#000099></FONT></U><BR>
<DIV>hello, </DIV>
<DIV>I would to ask about how is the route choses in DSR, is the decession taken on the hop count or other factor, and could we configure this facotrs or it is fixed ????&nbsp; </DIV>
<DIV>&nbsp;</DIV>
<DIV>Thanks </DIV>
<DIV>&nbsp;</DIV>
<DIV>Ayman </DIV></div><br clear=all><hr>The new <a href="http://g.msn.com/8HMEEN/2018">MSN 8:</a> smart spam protection and 2 months FREE* </html>
_______________________________________________
manet mailing list
manet@ietf.org
https://www1.ietf.org/mailman/listinfo/manet


From mailnull@www1.ietf.org  Sun Dec 15 15:09: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 PAA09370
	for <manet-archive@odin.ietf.org>; Sun, 15 Dec 2002 15:09:43 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id gBFKCHh27614
	for manet-archive@odin.ietf.org; Sun, 15 Dec 2002 15:12: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 gBFKCHv27611
	for <manet-web-archive@optimus.ietf.org>; Sun, 15 Dec 2002 15:12:17 -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 PAA09360
	for <manet-web-archive@ietf.org>; Sun, 15 Dec 2002 15:09: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 gBFJxjv26661;
	Sun, 15 Dec 2002 14:59: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 gBFJtCv26612
	for <manet@optimus.ietf.org>; Sun, 15 Dec 2002 14:55:12 -0500
Received: from maredsous.cs.rice.edu (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA09110
	for <manet@ietf.org>; Sun, 15 Dec 2002 14:52:08 -0500 (EST)
Received: (from dbj@localhost)
          by maredsous.cs.rice.edu id gBFJtsH01249;
          Sun, 15 Dec 2002 13:55:54 -0600 (CST)
Date: Sun, 15 Dec 2002 13:55:53 -0600
From: Dave Johnson <dbj@cs.rice.edu>
To: ayman ghazi <aymanghazi10@hotmail.com>
Cc: manet@ietf.org
Subject: Re: [manet] DSR
Message-ID: <20021215135553.A1174@maredsous.cs.rice.edu>
Reply-To: Dave Johnson <dbj@cs.rice.edu>
References: <F58GZlUfLosaQcL1je900025a48@hotmail.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <F58GZlUfLosaQcL1je900025a48@hotmail.com>; from aymanghazi10@hotmail.com on Sun, 15 Dec 2002 06:08:18PM +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>

The route in DSR can be chosen using any factors that the sender
wants to use.  It is typically chosen based on minimum hop count.
Among routes of equal length, it is good for the sender to favor
routes that it believes will be valid for the longest time.  This
is the "Link-MaxLife" strategy, described in the DSR Internet-Draft.
This is also described in detail with simulation results in

  Yih-Chun Hu and David B. Johnson. Caching Strategies in On-Demand
  Routing Protocols for Wireless Ad Hoc Networks. Proceedings of
  the Sixth Annual International Conference on Mobile Computing
  and Networking (MobiCom 2000), ACM, Boston, MA, August 2000.

Copies of this paper are available from http://www.monarch.cs.rice.edu/.

					Dave


ayman ghazi said:
>hello, 
>I would to ask about how is the route choses in DSR, is the decession
>taken on the hop count or other factor, and could we configure this
>facotrs or it is fixed ????
>
>Thanks 
_______________________________________________
manet mailing list
manet@ietf.org
https://www1.ietf.org/mailman/listinfo/manet



From manet-admin@ietf.org  Sun Dec 15 15:10: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 PAA09383
	for <manet-archive@lists.ietf.org>; Sun, 15 Dec 2002 15:10: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 gBFJxjv26661;
	Sun, 15 Dec 2002 14:59: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 gBFJtCv26612
	for <manet@optimus.ietf.org>; Sun, 15 Dec 2002 14:55:12 -0500
Received: from maredsous.cs.rice.edu (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA09110
	for <manet@ietf.org>; Sun, 15 Dec 2002 14:52:08 -0500 (EST)
Received: (from dbj@localhost)
          by maredsous.cs.rice.edu id gBFJtsH01249;
          Sun, 15 Dec 2002 13:55:54 -0600 (CST)
Date: Sun, 15 Dec 2002 13:55:53 -0600
From: Dave Johnson <dbj@cs.rice.edu>
To: ayman ghazi <aymanghazi10@hotmail.com>
Cc: manet@ietf.org
Subject: Re: [manet] DSR
Message-ID: <20021215135553.A1174@maredsous.cs.rice.edu>
Reply-To: Dave Johnson <dbj@cs.rice.edu>
References: <F58GZlUfLosaQcL1je900025a48@hotmail.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <F58GZlUfLosaQcL1je900025a48@hotmail.com>; from aymanghazi10@hotmail.com on Sun, 15 Dec 2002 06:08:18PM +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>

The route in DSR can be chosen using any factors that the sender
wants to use.  It is typically chosen based on minimum hop count.
Among routes of equal length, it is good for the sender to favor
routes that it believes will be valid for the longest time.  This
is the "Link-MaxLife" strategy, described in the DSR Internet-Draft.
This is also described in detail with simulation results in

  Yih-Chun Hu and David B. Johnson. Caching Strategies in On-Demand
  Routing Protocols for Wireless Ad Hoc Networks. Proceedings of
  the Sixth Annual International Conference on Mobile Computing
  and Networking (MobiCom 2000), ACM, Boston, MA, August 2000.

Copies of this paper are available from http://www.monarch.cs.rice.edu/.

					Dave


ayman ghazi said:
>hello, 
>I would to ask about how is the route choses in DSR, is the decession
>taken on the hop count or other factor, and could we configure this
>facotrs or it is fixed ????
>
>Thanks 
_______________________________________________
manet mailing list
manet@ietf.org
https://www1.ietf.org/mailman/listinfo/manet


From mailnull@www1.ietf.org  Mon Dec 16 05:47: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 FAA00935
	for <manet-archive@odin.ietf.org>; Mon, 16 Dec 2002 05:47:57 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id gBGAoPZ12153
	for manet-archive@odin.ietf.org; Mon, 16 Dec 2002 05:50: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 gBGAoPv12150
	for <manet-web-archive@optimus.ietf.org>; Mon, 16 Dec 2002 05:50: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 FAA00927
	for <manet-web-archive@ietf.org>; Mon, 16 Dec 2002 05:47: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 gBGAcbv11643;
	Mon, 16 Dec 2002 05:38: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 gBGAW8v10844
	for <manet@optimus.ietf.org>; Mon, 16 Dec 2002 05:32:08 -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 FAA00594
	for <manet@ietf.org>; Mon, 16 Dec 2002 05:29:09 -0500 (EST)
Received: from mail pickup service by hotmail.com with Microsoft SMTPSVC;
	 Mon, 16 Dec 2002 02:23:03 -0800
Received: from 212.4.33.133 by lw12fd.law12.hotmail.msn.com with HTTP;
	Mon, 16 Dec 2002 10:23:03 GMT
X-Originating-IP: [212.4.33.133]
From: "Berner Vegge" <bernervegge@hotmail.com>
To: manet@ietf.org
Date: Mon, 16 Dec 2002 11:23:03 +0100
Mime-Version: 1.0
Content-Type: text/plain; format=flowed
Message-ID: <F135Va8grB33UKyM25I000045d9@hotmail.com>
X-OriginalArrivalTime: 16 Dec 2002 10:23:03.0384 (UTC) FILETIME=[1DCAF580:01C2A4ED]
Subject: [manet] 11Mb/s speed for broadcasting 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>

Hello!
I have a problem when testing routing protocols over WLAN IEEE 802.11b.
The routing broadcasting stops at 2Mb/s, but I would like to have
it at 11Mb/s.
I think the reason is that the Supported Rates Information Element in 
Management Frames has 5.5Mb/s and 11Mb/s as optional rates, which again
means that they are not part of the Basic Rate Set and thereby not used
for broadcasting.

Anyone who knows how I can change 5.5Mb/s and 11Mb/s to mandatory rates
in the Supported Rates?

I use Orinoco Gold card, run in LINUX environment and the WLAN of course
runs in ad-hoc mode.

Thanks to anyone that may help!
BR  Berner

_________________________________________________________________
Tired of spam? Get advanced junk mail protection with MSN 8. 
http://join.msn.com/?page=features/junkmail

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



From manet-admin@ietf.org  Mon Dec 16 05:48: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 FAA00954
	for <manet-archive@lists.ietf.org>; Mon, 16 Dec 2002 05:48: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 gBGAcbv11643;
	Mon, 16 Dec 2002 05:38: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 gBGAW8v10844
	for <manet@optimus.ietf.org>; Mon, 16 Dec 2002 05:32:08 -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 FAA00594
	for <manet@ietf.org>; Mon, 16 Dec 2002 05:29:09 -0500 (EST)
Received: from mail pickup service by hotmail.com with Microsoft SMTPSVC;
	 Mon, 16 Dec 2002 02:23:03 -0800
Received: from 212.4.33.133 by lw12fd.law12.hotmail.msn.com with HTTP;
	Mon, 16 Dec 2002 10:23:03 GMT
X-Originating-IP: [212.4.33.133]
From: "Berner Vegge" <bernervegge@hotmail.com>
To: manet@ietf.org
Date: Mon, 16 Dec 2002 11:23:03 +0100
Mime-Version: 1.0
Content-Type: text/plain; format=flowed
Message-ID: <F135Va8grB33UKyM25I000045d9@hotmail.com>
X-OriginalArrivalTime: 16 Dec 2002 10:23:03.0384 (UTC) FILETIME=[1DCAF580:01C2A4ED]
Subject: [manet] 11Mb/s speed for broadcasting 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>

Hello!
I have a problem when testing routing protocols over WLAN IEEE 802.11b.
The routing broadcasting stops at 2Mb/s, but I would like to have
it at 11Mb/s.
I think the reason is that the Supported Rates Information Element in 
Management Frames has 5.5Mb/s and 11Mb/s as optional rates, which again
means that they are not part of the Basic Rate Set and thereby not used
for broadcasting.

Anyone who knows how I can change 5.5Mb/s and 11Mb/s to mandatory rates
in the Supported Rates?

I use Orinoco Gold card, run in LINUX environment and the WLAN of course
runs in ad-hoc mode.

Thanks to anyone that may help!
BR  Berner

_________________________________________________________________
Tired of spam? Get advanced junk mail protection with MSN 8. 
http://join.msn.com/?page=features/junkmail

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


From manet-admin@ietf.org  Tue Dec 17 00:24: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 AAA26800
	for <manet-archive@lists.ietf.org>; Tue, 17 Dec 2002 00:24: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 gBH5Chv06915;
	Tue, 17 Dec 2002 00:12: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 gBH58iv06807
	for <manet@optimus.ietf.org>; Tue, 17 Dec 2002 00:08:44 -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 AAA26550
	for <manet@ietf.org>; Tue, 17 Dec 2002 00:05:35 -0500 (EST)
Received: from mail pickup service by hotmail.com with Microsoft SMTPSVC;
	 Mon, 16 Dec 2002 21:08:33 -0800
Received: from 80.5.103.77 by lw14fd.law14.hotmail.msn.com with HTTP;
	Tue, 17 Dec 2002 05:08:31 GMT
X-Originating-IP: [80.5.103.77]
From: "hussam amin" <hussamamin@hotmail.com>
To: manet@ietf.org
Date: Tue, 17 Dec 2002 05:08:31 +0000
Mime-Version: 1.0
Content-Type: text/plain; format=flowed
Message-ID: <F57cUii9MQwVkeTUkQF00021f43@hotmail.com>
X-OriginalArrivalTime: 17 Dec 2002 05:08:33.0857 (UTC) FILETIME=[59176310:01C2A58A]
Subject: [manet] Qos models in 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>


as we know there are three QoS models was proposed in literature..InteServ , 
DiffServ and FQMM....and I have read in some papers about MultiServ....my 
equation is can we consider this approach (MultiServ) as new  QoS model or 
not and if yes will you please offer to me some information about this and 
is it suitable for MANETs?

any help will  Appreciate......

hussam




_________________________________________________________________
Help STOP SPAM with the new MSN 8 and get 2 months FREE*  
http://join.msn.com/?page=features/junkmail

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


From mailnull@www1.ietf.org  Tue Dec 17 00:40: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 AAA26928
	for <manet-archive@odin.ietf.org>; Tue, 17 Dec 2002 00:40:14 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id gBH5gq808385
	for manet-archive@odin.ietf.org; Tue, 17 Dec 2002 00:42: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 gBH5gqv08382
	for <manet-web-archive@optimus.ietf.org>; Tue, 17 Dec 2002 00:42:52 -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 AAA26922
	for <manet-web-archive@ietf.org>; Tue, 17 Dec 2002 00:39: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 gBH5Chv06915;
	Tue, 17 Dec 2002 00:12: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 gBH58iv06807
	for <manet@optimus.ietf.org>; Tue, 17 Dec 2002 00:08:44 -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 AAA26550
	for <manet@ietf.org>; Tue, 17 Dec 2002 00:05:35 -0500 (EST)
Received: from mail pickup service by hotmail.com with Microsoft SMTPSVC;
	 Mon, 16 Dec 2002 21:08:33 -0800
Received: from 80.5.103.77 by lw14fd.law14.hotmail.msn.com with HTTP;
	Tue, 17 Dec 2002 05:08:31 GMT
X-Originating-IP: [80.5.103.77]
From: "hussam amin" <hussamamin@hotmail.com>
To: manet@ietf.org
Date: Tue, 17 Dec 2002 05:08:31 +0000
Mime-Version: 1.0
Content-Type: text/plain; format=flowed
Message-ID: <F57cUii9MQwVkeTUkQF00021f43@hotmail.com>
X-OriginalArrivalTime: 17 Dec 2002 05:08:33.0857 (UTC) FILETIME=[59176310:01C2A58A]
Subject: [manet] Qos models in 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>


as we know there are three QoS models was proposed in literature..InteServ , 
DiffServ and FQMM....and I have read in some papers about MultiServ....my 
equation is can we consider this approach (MultiServ) as new  QoS model or 
not and if yes will you please offer to me some information about this and 
is it suitable for MANETs?

any help will  Appreciate......

hussam




_________________________________________________________________
Help STOP SPAM with the new MSN 8 and get 2 months FREE*  
http://join.msn.com/?page=features/junkmail

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



From manet-admin@ietf.org  Tue Dec 17 19:45: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 TAA27916
	for <manet-archive@lists.ietf.org>; Tue, 17 Dec 2002 19:45: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 gBI0edv16591;
	Tue, 17 Dec 2002 19:40: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 gBI0UUv15693
	for <manet@optimus.ietf.org>; Tue, 17 Dec 2002 19:30:30 -0500
Received: from mail.drexel.edu (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA27629
	for <manet@ietf.org>; Tue, 17 Dec 2002 19:27:24 -0500 (EST)
Received: from webmail.drexel.edu (webmail.drexel.edu [144.118.25.20])
 by mail.drexel.edu (Sun Internet Mail Server sims.4.0.2001.07.26.11.50.p9)
 with ESMTP id <0H7A00A26HEF9I@mail.drexel.edu> for manet@ietf.org; Tue,
 17 Dec 2002 19:30:15 -0500 (EST)
Date: Tue, 17 Dec 2002 19:33:52 -0500
From: Harpreet Arora <ha33@drexel.edu>
To: manet@ietf.org
Message-id: <3E07D46B@webmail.drexel.edu>
MIME-version: 1.0
X-Mailer: WebMail (Hydra) SMTP v3.62
Content-type: text/plain; charset=ISO-8859-1
Content-transfer-encoding: 7BIT
X-WebMail-UserID: ha33
X-EXP32-SerialNo: 00003005
Content-Transfer-Encoding: 7BIT
Subject: [manet] Manet Applications
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,

I am looking for literature on commercial and defense applications of
MANETs. Most of the papers currently show simulation results based on the
random way-point model, which might not be an accurate modelling of the real
life applications. Are there more accurate mobility models available? Can
anyone please guide me to literature on the related fields?

Thanks,
Harpreet

--------------------------------------------------------------------
Harpreet S. Arora
Research Assistant, ITCSL
Drexel University,
Philadelphia, PA-19104
Ph. # 215-895-6198
http://www.pages.drexel.edu/~ha33
----------------------------------------------------------------------

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


From mailnull@www1.ietf.org  Tue Dec 17 20:00: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 UAA28187
	for <manet-archive@odin.ietf.org>; Tue, 17 Dec 2002 20:00:35 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id gBI13BE17486
	for manet-archive@odin.ietf.org; Tue, 17 Dec 2002 20:03: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 gBI13Bv17483
	for <manet-web-archive@optimus.ietf.org>; Tue, 17 Dec 2002 20:03: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 UAA28180
	for <manet-web-archive@ietf.org>; Tue, 17 Dec 2002 20:00:04 -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 gBI0edv16591;
	Tue, 17 Dec 2002 19:40: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 gBI0UUv15693
	for <manet@optimus.ietf.org>; Tue, 17 Dec 2002 19:30:30 -0500
Received: from mail.drexel.edu (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA27629
	for <manet@ietf.org>; Tue, 17 Dec 2002 19:27:24 -0500 (EST)
Received: from webmail.drexel.edu (webmail.drexel.edu [144.118.25.20])
 by mail.drexel.edu (Sun Internet Mail Server sims.4.0.2001.07.26.11.50.p9)
 with ESMTP id <0H7A00A26HEF9I@mail.drexel.edu> for manet@ietf.org; Tue,
 17 Dec 2002 19:30:15 -0500 (EST)
Date: Tue, 17 Dec 2002 19:33:52 -0500
From: Harpreet Arora <ha33@drexel.edu>
To: manet@ietf.org
Message-id: <3E07D46B@webmail.drexel.edu>
MIME-version: 1.0
X-Mailer: WebMail (Hydra) SMTP v3.62
Content-type: text/plain; charset=ISO-8859-1
Content-transfer-encoding: 7BIT
X-WebMail-UserID: ha33
X-EXP32-SerialNo: 00003005
Content-Transfer-Encoding: 7BIT
Subject: [manet] Manet Applications
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,

I am looking for literature on commercial and defense applications of
MANETs. Most of the papers currently show simulation results based on the
random way-point model, which might not be an accurate modelling of the real
life applications. Are there more accurate mobility models available? Can
anyone please guide me to literature on the related fields?

Thanks,
Harpreet

--------------------------------------------------------------------
Harpreet S. Arora
Research Assistant, ITCSL
Drexel University,
Philadelphia, PA-19104
Ph. # 215-895-6198
http://www.pages.drexel.edu/~ha33
----------------------------------------------------------------------

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



From manet-admin@ietf.org  Tue Dec 17 21:01: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 VAA29312
	for <manet-archive@lists.ietf.org>; Tue, 17 Dec 2002 21: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 gBI1o8v20323;
	Tue, 17 Dec 2002 20:50: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 gBI1fgv20140
	for <manet@optimus.ietf.org>; Tue, 17 Dec 2002 20:41:42 -0500
Received: from mailout5-0.nyroc.rr.com (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id UAA28919
	for <manet@ietf.org>; Tue, 17 Dec 2002 20:38:32 -0500 (EST)
Received: from caend062 (alb-24-194-37-216.nycap.rr.com [24.194.37.216])
	by mailout5-0.nyroc.rr.com (8.11.6/RoadRunner 1.20) with SMTP id gBI1fSF23208;
	Tue, 17 Dec 2002 20:41:28 -0500 (EST)
Message-ID: <002301c2a636$97ee8030$d825c218@caend062>
From: "Alhussein Abouzeid" <hussein@ecse.rpi.edu>
To: "Harpreet Arora" <ha33@drexel.edu>, <manet@ietf.org>
References: <3E07D46B@webmail.drexel.edu>
Subject: Re: [manet] Manet Applications
Date: Tue, 17 Dec 2002 20:41:32 -0500
Organization: RPI
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
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

Harpeet,
I find this survey helpful:
http://citeseer.nj.nec.com/camp02survey.html
It includes a number of models, including:
http://citeseer.nj.nec.com/hong99group.html
which seems close to what you are looking for.
-Hussein
www.rpi.edu/~abouza
----- Original Message -----
From: "Harpreet Arora" <ha33@drexel.edu>
To: <manet@ietf.org>
Sent: Tuesday, December 17, 2002 7:33 PM
Subject: [manet] Manet Applications


> Hi,
>
> I am looking for literature on commercial and defense applications of
> MANETs. Most of the papers currently show simulation results based on the
> random way-point model, which might not be an accurate modelling of the
real
> life applications. Are there more accurate mobility models available? Can
> anyone please guide me to literature on the related fields?
>
> Thanks,
> Harpreet
>
> --------------------------------------------------------------------
> Harpreet S. Arora
> Research Assistant, ITCSL
> Drexel University,
> Philadelphia, PA-19104
> Ph. # 215-895-6198
> http://www.pages.drexel.edu/~ha33
> ----------------------------------------------------------------------
>
> _______________________________________________
> 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 Dec 17 21:22: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 VAA29600
	for <manet-archive@odin.ietf.org>; Tue, 17 Dec 2002 21:22:55 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id gBI2PW222226
	for manet-archive@odin.ietf.org; Tue, 17 Dec 2002 21:25: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 gBI2PWv22223
	for <manet-web-archive@optimus.ietf.org>; Tue, 17 Dec 2002 21:25: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 VAA29591
	for <manet-web-archive@ietf.org>; Tue, 17 Dec 2002 21:22: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 gBI1o8v20323;
	Tue, 17 Dec 2002 20:50: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 gBI1fgv20140
	for <manet@optimus.ietf.org>; Tue, 17 Dec 2002 20:41:42 -0500
Received: from mailout5-0.nyroc.rr.com (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id UAA28919
	for <manet@ietf.org>; Tue, 17 Dec 2002 20:38:32 -0500 (EST)
Received: from caend062 (alb-24-194-37-216.nycap.rr.com [24.194.37.216])
	by mailout5-0.nyroc.rr.com (8.11.6/RoadRunner 1.20) with SMTP id gBI1fSF23208;
	Tue, 17 Dec 2002 20:41:28 -0500 (EST)
Message-ID: <002301c2a636$97ee8030$d825c218@caend062>
From: "Alhussein Abouzeid" <hussein@ecse.rpi.edu>
To: "Harpreet Arora" <ha33@drexel.edu>, <manet@ietf.org>
References: <3E07D46B@webmail.drexel.edu>
Subject: Re: [manet] Manet Applications
Date: Tue, 17 Dec 2002 20:41:32 -0500
Organization: RPI
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
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

Harpeet,
I find this survey helpful:
http://citeseer.nj.nec.com/camp02survey.html
It includes a number of models, including:
http://citeseer.nj.nec.com/hong99group.html
which seems close to what you are looking for.
-Hussein
www.rpi.edu/~abouza
----- Original Message -----
From: "Harpreet Arora" <ha33@drexel.edu>
To: <manet@ietf.org>
Sent: Tuesday, December 17, 2002 7:33 PM
Subject: [manet] Manet Applications


> Hi,
>
> I am looking for literature on commercial and defense applications of
> MANETs. Most of the papers currently show simulation results based on the
> random way-point model, which might not be an accurate modelling of the
real
> life applications. Are there more accurate mobility models available? Can
> anyone please guide me to literature on the related fields?
>
> Thanks,
> Harpreet
>
> --------------------------------------------------------------------
> Harpreet S. Arora
> Research Assistant, ITCSL
> Drexel University,
> Philadelphia, PA-19104
> Ph. # 215-895-6198
> http://www.pages.drexel.edu/~ha33
> ----------------------------------------------------------------------
>
> _______________________________________________
> 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 Dec 17 21:39:21 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 VAA00121
	for <manet-archive@lists.ietf.org>; Tue, 17 Dec 2002 21:39: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 gBI2VIv22388;
	Tue, 17 Dec 2002 21:31: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 gBI2NJv22160
	for <manet@optimus.ietf.org>; Tue, 17 Dec 2002 21:23:19 -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 VAA29569
	for <manet@ietf.org>; Tue, 17 Dec 2002 21:20:11 -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 gBI2NBH351463;
	Tue, 17 Dec 2002 21:23:11 -0500 (EST)
Received: from TNT (h80ad3711.dhcp.vt.edu [128.173.55.17])
	by steiner.cc.vt.edu (Mirapoint Messaging Server MOS 3.2.2-GA)
	with SMTP id AUZ26619;
	Tue, 17 Dec 2002 21:23:11 -0500 (EST)
Message-ID: <002101c2a63c$60887780$1137ad80@workgroup>
From: "Tao Lin" <taolin@vt.edu>
To: "Alhussein Abouzeid" <hussein@ecse.rpi.edu>,
        "Harpreet Arora" <ha33@drexel.edu>, <manet@ietf.org>
References: <3E07D46B@webmail.drexel.edu> <002301c2a636$97ee8030$d825c218@caend062>
Subject: Re: [manet] Manet Applications
Date: Tue, 17 Dec 2002 21:22:56 -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.2800.1106
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1106
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

We have one paper discussing a link connectivity simulation model for MANET
and accepted by CNDS '03.

Tao Lin and Scott F. Midkiff, "Mobility versus Link Statbility in Simulation
of Mobile Ad Hoc Networks", accepted by Communication Networks and
Distributed Systems Modeling and Simulation Conference (CNDS'03).

Please check the proceeding of CNDS'03 in January 2003.  Thank you!

 Tao Lin
 ECE Dept.
 Virginia Tech.
 USA

----- Original Message -----
From: "Alhussein Abouzeid" <hussein@ecse.rpi.edu>
To: "Harpreet Arora" <ha33@drexel.edu>; <manet@ietf.org>
Sent: Tuesday, December 17, 2002 8:41 PM
Subject: Re: [manet] Manet Applications


> Harpeet,
> I find this survey helpful:
> http://citeseer.nj.nec.com/camp02survey.html
> It includes a number of models, including:
> http://citeseer.nj.nec.com/hong99group.html
> which seems close to what you are looking for.
> -Hussein
> www.rpi.edu/~abouza
> ----- Original Message -----
> From: "Harpreet Arora" <ha33@drexel.edu>
> To: <manet@ietf.org>
> Sent: Tuesday, December 17, 2002 7:33 PM
> Subject: [manet] Manet Applications
>
>
> > Hi,
> >
> > I am looking for literature on commercial and defense applications of
> > MANETs. Most of the papers currently show simulation results based on
the
> > random way-point model, which might not be an accurate modelling of the
> real
> > life applications. Are there more accurate mobility models available?
Can
> > anyone please guide me to literature on the related fields?
> >
> > Thanks,
> > Harpreet
> >
> > --------------------------------------------------------------------
> > Harpreet S. Arora
> > Research Assistant, ITCSL
> > Drexel University,
> > Philadelphia, PA-19104
> > Ph. # 215-895-6198
> > http://www.pages.drexel.edu/~ha33
> > ----------------------------------------------------------------------
> >
> > _______________________________________________
> > 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 Dec 17 21:52: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 VAA00292
	for <manet-archive@odin.ietf.org>; Tue, 17 Dec 2002 21:52:03 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id gBI2sfj23821
	for manet-archive@odin.ietf.org; Tue, 17 Dec 2002 21:54: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 gBI2sev23818
	for <manet-web-archive@optimus.ietf.org>; Tue, 17 Dec 2002 21:54:40 -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 VAA00289
	for <manet-web-archive@ietf.org>; Tue, 17 Dec 2002 21:51: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 gBI2VIv22388;
	Tue, 17 Dec 2002 21:31: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 gBI2NJv22160
	for <manet@optimus.ietf.org>; Tue, 17 Dec 2002 21:23:19 -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 VAA29569
	for <manet@ietf.org>; Tue, 17 Dec 2002 21:20:11 -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 gBI2NBH351463;
	Tue, 17 Dec 2002 21:23:11 -0500 (EST)
Received: from TNT (h80ad3711.dhcp.vt.edu [128.173.55.17])
	by steiner.cc.vt.edu (Mirapoint Messaging Server MOS 3.2.2-GA)
	with SMTP id AUZ26619;
	Tue, 17 Dec 2002 21:23:11 -0500 (EST)
Message-ID: <002101c2a63c$60887780$1137ad80@workgroup>
From: "Tao Lin" <taolin@vt.edu>
To: "Alhussein Abouzeid" <hussein@ecse.rpi.edu>,
        "Harpreet Arora" <ha33@drexel.edu>, <manet@ietf.org>
References: <3E07D46B@webmail.drexel.edu> <002301c2a636$97ee8030$d825c218@caend062>
Subject: Re: [manet] Manet Applications
Date: Tue, 17 Dec 2002 21:22:56 -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.2800.1106
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1106
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

We have one paper discussing a link connectivity simulation model for MANET
and accepted by CNDS '03.

Tao Lin and Scott F. Midkiff, "Mobility versus Link Statbility in Simulation
of Mobile Ad Hoc Networks", accepted by Communication Networks and
Distributed Systems Modeling and Simulation Conference (CNDS'03).

Please check the proceeding of CNDS'03 in January 2003.  Thank you!

 Tao Lin
 ECE Dept.
 Virginia Tech.
 USA

----- Original Message -----
From: "Alhussein Abouzeid" <hussein@ecse.rpi.edu>
To: "Harpreet Arora" <ha33@drexel.edu>; <manet@ietf.org>
Sent: Tuesday, December 17, 2002 8:41 PM
Subject: Re: [manet] Manet Applications


> Harpeet,
> I find this survey helpful:
> http://citeseer.nj.nec.com/camp02survey.html
> It includes a number of models, including:
> http://citeseer.nj.nec.com/hong99group.html
> which seems close to what you are looking for.
> -Hussein
> www.rpi.edu/~abouza
> ----- Original Message -----
> From: "Harpreet Arora" <ha33@drexel.edu>
> To: <manet@ietf.org>
> Sent: Tuesday, December 17, 2002 7:33 PM
> Subject: [manet] Manet Applications
>
>
> > Hi,
> >
> > I am looking for literature on commercial and defense applications of
> > MANETs. Most of the papers currently show simulation results based on
the
> > random way-point model, which might not be an accurate modelling of the
> real
> > life applications. Are there more accurate mobility models available?
Can
> > anyone please guide me to literature on the related fields?
> >
> > Thanks,
> > Harpreet
> >
> > --------------------------------------------------------------------
> > Harpreet S. Arora
> > Research Assistant, ITCSL
> > Drexel University,
> > Philadelphia, PA-19104
> > Ph. # 215-895-6198
> > http://www.pages.drexel.edu/~ha33
> > ----------------------------------------------------------------------
> >
> > _______________________________________________
> > 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  Wed Dec 18 01:11: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 BAA03699
	for <manet-archive@lists.ietf.org>; Wed, 18 Dec 2002 01:11: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 gBI602v32435;
	Wed, 18 Dec 2002 01:00: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 gBI5lsv32086
	for <manet@optimus.ietf.org>; Wed, 18 Dec 2002 00:47:54 -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 AAA03303
	for <manet@ietf.org>; Wed, 18 Dec 2002 00:44:43 -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);
	 Wed, 18 Dec 2002 13:47:40 +0800
X-MimeOLE: Produced By Microsoft Exchange V6.0.6249.0
content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="Windows-1252"
Date: Wed, 18 Dec 2002 13:47:39 +0800
Message-ID: <8FD24FA221E29D458985D62F8219A4B9BA1792@MBXSRV26.stu.nus.edu.sg>
Thread-Topic: how to get the neighbor's ip addr 
Thread-Index: AcKmWPnXchtAa4NHSx6+q3tt87Omgg==
From: "Lu Guoxiang" <isc90193@nus.edu.sg>
To: <manet@ietf.org>
X-OriginalArrivalTime: 18 Dec 2002 05:47:40.0360 (UTC) FILETIME=[FA211480:01C2A658]
Content-Transfer-Encoding: 8bit
X-MIME-Autoconverted: from quoted-printable to 8bit by www1.ietf.org id gBI5lsv32087
Subject: [manet] how to get the neighbor's ip addr
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 am using ns2.1b9a to simulate a protocol. i wanna get one node's neighbor list. there is a method implemented in tcl code called "$node neighbors" to get all the neighbors. but if i want the neighbors' addresses in c++ code space, what should i do? Is the only way that each node broadcasts its addr to its neighbors? 
your help will be greatly appreciated.

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


From mailnull@www1.ietf.org  Wed Dec 18 01:20: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 BAA03826
	for <manet-archive@odin.ietf.org>; Wed, 18 Dec 2002 01:20:26 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id gBI6N4C01611
	for manet-archive@odin.ietf.org; Wed, 18 Dec 2002 01:23: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 gBI6N4v01608
	for <manet-web-archive@optimus.ietf.org>; Wed, 18 Dec 2002 01:23: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 BAA03819
	for <manet-web-archive@ietf.org>; Wed, 18 Dec 2002 01:19: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 gBI602v32435;
	Wed, 18 Dec 2002 01:00: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 gBI5lsv32086
	for <manet@optimus.ietf.org>; Wed, 18 Dec 2002 00:47:54 -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 AAA03303
	for <manet@ietf.org>; Wed, 18 Dec 2002 00:44:43 -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);
	 Wed, 18 Dec 2002 13:47:40 +0800
X-MimeOLE: Produced By Microsoft Exchange V6.0.6249.0
content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="Windows-1252"
Date: Wed, 18 Dec 2002 13:47:39 +0800
Message-ID: <8FD24FA221E29D458985D62F8219A4B9BA1792@MBXSRV26.stu.nus.edu.sg>
Thread-Topic: how to get the neighbor's ip addr 
Thread-Index: AcKmWPnXchtAa4NHSx6+q3tt87Omgg==
From: "Lu Guoxiang" <isc90193@nus.edu.sg>
To: <manet@ietf.org>
X-OriginalArrivalTime: 18 Dec 2002 05:47:40.0360 (UTC) FILETIME=[FA211480:01C2A658]
Content-Transfer-Encoding: 8bit
X-MIME-Autoconverted: from quoted-printable to 8bit by www1.ietf.org id gBI5lsv32087
Subject: [manet] how to get the neighbor's ip addr
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 am using ns2.1b9a to simulate a protocol. i wanna get one node's neighbor list. there is a method implemented in tcl code called "$node neighbors" to get all the neighbors. but if i want the neighbors' addresses in c++ code space, what should i do? Is the only way that each node broadcasts its addr to its neighbors? 
your help will be greatly appreciated.

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



From mailnull@www1.ietf.org  Wed Dec 18 03:03: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 DAA29256
	for <manet-archive@odin.ietf.org>; Wed, 18 Dec 2002 03:03:58 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id gBI86cg17530
	for manet-archive@odin.ietf.org; Wed, 18 Dec 2002 03:06: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 gBI86cv17527
	for <manet-web-archive@optimus.ietf.org>; Wed, 18 Dec 2002 03:06:38 -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 DAA29250
	for <manet-web-archive@ietf.org>; Wed, 18 Dec 2002 03:03: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 gBI7olv16700;
	Wed, 18 Dec 2002 02:50: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 gBI7j6v16543
	for <manet@optimus.ietf.org>; Wed, 18 Dec 2002 02:45:06 -0500
Received: from sundance.cse.ucsc.edu (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id CAA28908
	for <manet@ietf.org>; Wed, 18 Dec 2002 02:41:55 -0500 (EST)
Received: from localhost (chandrab@localhost) by sundance.cse.ucsc.edu (8.6.10/8.6.12) with ESMTP id XAA16936 for <manet@ietf.org>; Tue, 17 Dec 2002 23:44:55 -0800
X-Authentication-Warning: sundance.cse.ucsc.edu: chandrab owned process doing -bs
Date: Tue, 17 Dec 2002 23:44:55 -0800 (PST)
From: Chandramouli Balasubramanian <chandrab@cse.ucsc.edu>
To: manet@ietf.org
Message-ID: <Pine.GSO.4.44.0212172335360.16803-100000@sundance.cse.ucsc.edu>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Subject: [manet] Performance Comparison of QoS Routing for Adhoc 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>


Hi All:

I know there has been very few work on QoS Routing for Adhoc Networks.
More work has been done on the signalling aspects, but has anyone ever
looked at the Performance Evaluation aspects of the Qos Routing Protocols?

Thanks in advance.

With regards
Chandramouli



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



From manet-admin@ietf.org  Wed Dec 18 03:05: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 DAA29279
	for <manet-archive@lists.ietf.org>; Wed, 18 Dec 2002 03:05: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 gBI7olv16700;
	Wed, 18 Dec 2002 02:50: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 gBI7j6v16543
	for <manet@optimus.ietf.org>; Wed, 18 Dec 2002 02:45:06 -0500
Received: from sundance.cse.ucsc.edu (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id CAA28908
	for <manet@ietf.org>; Wed, 18 Dec 2002 02:41:55 -0500 (EST)
Received: from localhost (chandrab@localhost) by sundance.cse.ucsc.edu (8.6.10/8.6.12) with ESMTP id XAA16936 for <manet@ietf.org>; Tue, 17 Dec 2002 23:44:55 -0800
X-Authentication-Warning: sundance.cse.ucsc.edu: chandrab owned process doing -bs
Date: Tue, 17 Dec 2002 23:44:55 -0800 (PST)
From: Chandramouli Balasubramanian <chandrab@cse.ucsc.edu>
To: manet@ietf.org
Message-ID: <Pine.GSO.4.44.0212172335360.16803-100000@sundance.cse.ucsc.edu>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Subject: [manet] Performance Comparison of QoS Routing for Adhoc 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>


Hi All:

I know there has been very few work on QoS Routing for Adhoc Networks.
More work has been done on the signalling aspects, but has anyone ever
looked at the Performance Evaluation aspects of the Qos Routing Protocols?

Thanks in advance.

With regards
Chandramouli



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


From manet-admin@ietf.org  Wed Dec 18 04:07: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 EAA00183
	for <manet-archive@lists.ietf.org>; Wed, 18 Dec 2002 04:07: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 gBI90mv20540;
	Wed, 18 Dec 2002 04:00: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 gBI8qHv20276
	for <manet@optimus.ietf.org>; Wed, 18 Dec 2002 03:52:17 -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 DAA29736
	for <manet@ietf.org>; Wed, 18 Dec 2002 03:49:03 -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 KAA13571 for <manet@ietf.org>; Wed, 18 Dec 2002 10:30:58 +0100 (MET)
Message-ID: <004601c2a673$37610430$26ba90c1@mizar>
From: =?iso-8859-1?Q?Ram=F3n_Ag=FCero?= <ramon@tlmat.unican.es>
To: <manet@ietf.org>
Date: Wed, 18 Dec 2002 09:55:29 +0100
MIME-Version: 1.0
Content-Type: multipart/alternative;
	boundary="----=_NextPart_000_0043_01C2A67B.98C9B7A0"
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] DSR Route Reply Option
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_0043_01C2A67B.98C9B7A0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

Hi to all,

I've been revising the current version for the DSR protocol, and I have =
found something which, in my opinion, it should be a mistake. If you =
look at section 5.3 (Route Reply Option Format) there are 5 pieces of =
information within it:

        - Option Type
        - Option Data Length
        - The "L" bit
        - Some Reserved bits
        - The whole list of addresses belonging to the route

However, if you read section 6.2.4 (Originating a Route Reply) you will =
be able to see that it is assumed that an Identification field is also =
needed at the DSR Route Reply header, as it says:
   =20
        - The Route Request Identifier MUST be initialized to the =
Identifier field of the Route Request that this reply is sent in =
response to.

Could anybody tell me whether the Route Reply should include a ID field?

Thanks in advance

Ram=F3n



------=_NextPart_000_0043_01C2A67B.98C9B7A0
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>Hi to all,</FONT></DIV>
<DIV><FONT face=3DCourier size=3D2></FONT>&nbsp;</DIV>
<DIV><FONT face=3DCourier size=3D2>I've been revising the current =
version for the=20
DSR protocol, and I have found something which, in my opinion, it should =
be a=20
mistake. If you look&nbsp;at section 5.3 (Route Reply Option Format) =
there are 5=20
pieces of information within it:</FONT></DIV>
<DIV><FONT face=3DCourier size=3D2></FONT>&nbsp;</DIV>
<DIV><FONT face=3DCourier size=3D2>&nbsp;&nbsp;&nbsp; &nbsp;&nbsp;&nbsp; =
- Option=20
Type</FONT></DIV>
<DIV><FONT face=3DCourier size=3D2>&nbsp;&nbsp;&nbsp; &nbsp;&nbsp;&nbsp; =
- Option=20
Data Length</FONT></DIV>
<DIV><FONT face=3DCourier size=3D2>&nbsp;&nbsp;&nbsp; &nbsp;&nbsp;&nbsp; =
- The "L"=20
bit</FONT></DIV>
<DIV><FONT face=3DCourier size=3D2>&nbsp;&nbsp;&nbsp; &nbsp;&nbsp;&nbsp; =
- Some=20
Reserved bits</FONT></DIV>
<DIV><FONT face=3DCourier size=3D2>&nbsp;&nbsp;&nbsp; &nbsp;&nbsp;&nbsp; =
- The whole=20
list of addresses belonging to the route</FONT></DIV>
<DIV><FONT face=3DCourier size=3D2></FONT>&nbsp;</DIV>
<DIV><FONT face=3DCourier size=3D2>However, if you read section 6.2.4 =
(Originating a=20
Route Reply) you will be able to see that it is assumed that an =
Identification=20
field is also needed at the DSR Route Reply header, as it =
says:</FONT></DIV>
<DIV><FONT face=3DCourier size=3D2>&nbsp;&nbsp;&nbsp; </FONT></DIV>
<DIV><FONT face=3DCourier=20
size=3D2>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;-&nbsp;<FONT=20
face=3D"Courier New" size=3D3><FONT face=3DCourier size=3D2>The Route =
Request Identifier=20
MUST be initialized to the&nbsp;Identifier field of the Route Request =
that this=20
reply is sent in response to.</FONT></FONT></FONT></DIV>
<DIV><FONT face=3DCourier size=3D2><FONT face=3D"Courier New" =
size=3D3><FONT=20
face=3DCourier size=3D2></FONT></FONT></FONT>&nbsp;</DIV>
<DIV><FONT face=3DCourier size=3D2><FONT face=3D"Courier New" =
size=3D3><FONT=20
face=3DCourier size=3D2>Could anybody tell me whether&nbsp;the Route =
Reply should=20
include a ID field?</FONT></FONT></FONT></DIV>
<DIV><FONT face=3DCourier size=3D2><FONT face=3D"Courier New" =
size=3D3><FONT=20
face=3DCourier size=3D2></FONT></FONT></FONT>&nbsp;</DIV>
<DIV><FONT face=3DCourier size=3D2><FONT face=3D"Courier New" =
size=3D3><FONT=20
face=3DCourier size=3D2>Thanks in advance</FONT></FONT></FONT></DIV>
<DIV><FONT face=3DCourier size=3D2><FONT face=3D"Courier New" =
size=3D3><FONT=20
face=3DCourier size=3D2></FONT></FONT></FONT>&nbsp;</DIV>
<DIV><FONT face=3DCourier size=3D2><FONT face=3D"Courier New" =
size=3D3><FONT=20
face=3DCourier size=3D2>Ram=F3n</FONT></DIV>
<DIV><BR></DIV></FONT></FONT></BODY></HTML>

------=_NextPart_000_0043_01C2A67B.98C9B7A0--

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


From mailnull@www1.ietf.org  Wed Dec 18 04:26: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 EAA00610
	for <manet-archive@odin.ietf.org>; Wed, 18 Dec 2002 04:26:48 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id gBI9TU822614
	for manet-archive@odin.ietf.org; Wed, 18 Dec 2002 04:29: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 gBI9TTv22611
	for <manet-web-archive@optimus.ietf.org>; Wed, 18 Dec 2002 04:29: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 EAA00599
	for <manet-web-archive@ietf.org>; Wed, 18 Dec 2002 04:26: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 gBI90mv20540;
	Wed, 18 Dec 2002 04:00: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 gBI8qHv20276
	for <manet@optimus.ietf.org>; Wed, 18 Dec 2002 03:52:17 -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 DAA29736
	for <manet@ietf.org>; Wed, 18 Dec 2002 03:49:03 -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 KAA13571 for <manet@ietf.org>; Wed, 18 Dec 2002 10:30:58 +0100 (MET)
Message-ID: <004601c2a673$37610430$26ba90c1@mizar>
From: =?iso-8859-1?Q?Ram=F3n_Ag=FCero?= <ramon@tlmat.unican.es>
To: <manet@ietf.org>
Date: Wed, 18 Dec 2002 09:55:29 +0100
MIME-Version: 1.0
Content-Type: multipart/alternative;
	boundary="----=_NextPart_000_0043_01C2A67B.98C9B7A0"
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] DSR Route Reply Option
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_0043_01C2A67B.98C9B7A0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

Hi to all,

I've been revising the current version for the DSR protocol, and I have =
found something which, in my opinion, it should be a mistake. If you =
look at section 5.3 (Route Reply Option Format) there are 5 pieces of =
information within it:

        - Option Type
        - Option Data Length
        - The "L" bit
        - Some Reserved bits
        - The whole list of addresses belonging to the route

However, if you read section 6.2.4 (Originating a Route Reply) you will =
be able to see that it is assumed that an Identification field is also =
needed at the DSR Route Reply header, as it says:
   =20
        - The Route Request Identifier MUST be initialized to the =
Identifier field of the Route Request that this reply is sent in =
response to.

Could anybody tell me whether the Route Reply should include a ID field?

Thanks in advance

Ram=F3n



------=_NextPart_000_0043_01C2A67B.98C9B7A0
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>Hi to all,</FONT></DIV>
<DIV><FONT face=3DCourier size=3D2></FONT>&nbsp;</DIV>
<DIV><FONT face=3DCourier size=3D2>I've been revising the current =
version for the=20
DSR protocol, and I have found something which, in my opinion, it should =
be a=20
mistake. If you look&nbsp;at section 5.3 (Route Reply Option Format) =
there are 5=20
pieces of information within it:</FONT></DIV>
<DIV><FONT face=3DCourier size=3D2></FONT>&nbsp;</DIV>
<DIV><FONT face=3DCourier size=3D2>&nbsp;&nbsp;&nbsp; &nbsp;&nbsp;&nbsp; =
- Option=20
Type</FONT></DIV>
<DIV><FONT face=3DCourier size=3D2>&nbsp;&nbsp;&nbsp; &nbsp;&nbsp;&nbsp; =
- Option=20
Data Length</FONT></DIV>
<DIV><FONT face=3DCourier size=3D2>&nbsp;&nbsp;&nbsp; &nbsp;&nbsp;&nbsp; =
- The "L"=20
bit</FONT></DIV>
<DIV><FONT face=3DCourier size=3D2>&nbsp;&nbsp;&nbsp; &nbsp;&nbsp;&nbsp; =
- Some=20
Reserved bits</FONT></DIV>
<DIV><FONT face=3DCourier size=3D2>&nbsp;&nbsp;&nbsp; &nbsp;&nbsp;&nbsp; =
- The whole=20
list of addresses belonging to the route</FONT></DIV>
<DIV><FONT face=3DCourier size=3D2></FONT>&nbsp;</DIV>
<DIV><FONT face=3DCourier size=3D2>However, if you read section 6.2.4 =
(Originating a=20
Route Reply) you will be able to see that it is assumed that an =
Identification=20
field is also needed at the DSR Route Reply header, as it =
says:</FONT></DIV>
<DIV><FONT face=3DCourier size=3D2>&nbsp;&nbsp;&nbsp; </FONT></DIV>
<DIV><FONT face=3DCourier=20
size=3D2>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;-&nbsp;<FONT=20
face=3D"Courier New" size=3D3><FONT face=3DCourier size=3D2>The Route =
Request Identifier=20
MUST be initialized to the&nbsp;Identifier field of the Route Request =
that this=20
reply is sent in response to.</FONT></FONT></FONT></DIV>
<DIV><FONT face=3DCourier size=3D2><FONT face=3D"Courier New" =
size=3D3><FONT=20
face=3DCourier size=3D2></FONT></FONT></FONT>&nbsp;</DIV>
<DIV><FONT face=3DCourier size=3D2><FONT face=3D"Courier New" =
size=3D3><FONT=20
face=3DCourier size=3D2>Could anybody tell me whether&nbsp;the Route =
Reply should=20
include a ID field?</FONT></FONT></FONT></DIV>
<DIV><FONT face=3DCourier size=3D2><FONT face=3D"Courier New" =
size=3D3><FONT=20
face=3DCourier size=3D2></FONT></FONT></FONT>&nbsp;</DIV>
<DIV><FONT face=3DCourier size=3D2><FONT face=3D"Courier New" =
size=3D3><FONT=20
face=3DCourier size=3D2>Thanks in advance</FONT></FONT></FONT></DIV>
<DIV><FONT face=3DCourier size=3D2><FONT face=3D"Courier New" =
size=3D3><FONT=20
face=3DCourier size=3D2></FONT></FONT></FONT>&nbsp;</DIV>
<DIV><FONT face=3DCourier size=3D2><FONT face=3D"Courier New" =
size=3D3><FONT=20
face=3DCourier size=3D2>Ram=F3n</FONT></DIV>
<DIV><BR></DIV></FONT></FONT></BODY></HTML>

------=_NextPart_000_0043_01C2A67B.98C9B7A0--

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



From mailnull@www1.ietf.org  Wed Dec 18 20:52: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 UAA25307
	for <manet-archive@odin.ietf.org>; Wed, 18 Dec 2002 20:52:01 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id gBJ1sdl13070
	for manet-archive@odin.ietf.org; Wed, 18 Dec 2002 20:54: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 gBJ1sdv13067
	for <manet-web-archive@optimus.ietf.org>; Wed, 18 Dec 2002 20:54: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 UAA25282
	for <manet-web-archive@ietf.org>; Wed, 18 Dec 2002 20:51: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 gBJ1eqv12476;
	Wed, 18 Dec 2002 20:40: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 gBJ1ahv11741
	for <manet@optimus.ietf.org>; Wed, 18 Dec 2002 20:36:43 -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 UAA24384
	for <manet@ietf.org>; Wed, 18 Dec 2002 20:33:34 -0500 (EST)
Received: from HYOJIN.cornell.edu (r106748.resnet.cornell.edu [128.253.122.219])
	by memphis.ece.cornell.edu (8.11.6/8.11.2) with SMTP id gBJ1aYX06802;
	Wed, 18 Dec 2002 20:36:34 -0500
Message-Id: <5.1.0.14.2.20021218203113.01f39e28@memphis.ece.cornell.edu>
X-Sender: papadp@memphis.ece.cornell.edu
X-Mailer: QUALCOMM Windows Eudora Version 5.1
Date: Wed, 18 Dec 2002 20:36:27 -0500
To: manet@ietf.org
From: Panos Papadimitratos <papadp@ece.cornell.edu>
Cc: haas@ece.cornell.edu, samar@ece.cornell.edu, papadp@ece.cornell.edu
Mime-Version: 1.0
Content-Type: multipart/alternative;
	boundary="=====================_5376891==_.ALT"
Subject: [manet] Fwd: I-D
 ACTION:draft-papadimitratos-secure-routing-protocol-00.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>

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

A New Internet-Draft is available from the on-line Internet-Drafts directories.


         Title           : The Secure Routing Protocol (SRP) for Ad Hoc 
Networks
         Author(s)       : P. Papadimitratos, Z.J. Haas, P. Samar
         Filename        : draft-papadimitratos-secure-routing-protocol-00.txt
         Pages           : 14
         Date            : 2002-12-11

This document describes the Secure Routing Protocol (SRP), a route 
discovery protocol for ad hoc networks
that mitigates the detrimental effects of maliciously behaving nodes that 
disrupt the route discovery in
order to obstruct or disable the network operation. Our protocol provides 
correct routing information; i.e.,
factual, up-to-date and authentic connectivity information regarding a pair 
of nodes that wish to communicate
in a secure manner. The sole requirement is that any two such end nodes 
have a security association.
Accordingly, SRP does not require that any of the intermediate nodes 
perform cryptographic operations or
have a prior association with the end nodes. The end-to-end operation of 
SRP allows for efficient cryptographic
mechanisms, such as message authentication codes. More importantly, SRP can 
be used in a wide range of MANET
instances, without restrictive assumptions on the underlying trust, network 
size and membership.

A URL for this Internet-Draft is:
http://www.ietf.org/internet-drafts/draft-papadimitratos-secure-routing-protocol-00.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-papadimitratos-secure-routing-protocol-00.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-papadimitratos-secure-routing-protocol-00.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.
<ftp://ftp.ietf.org/internet-drafts/draft-papadimitratos-secure-routing-protocol-00.txt> 



--=====================_5376891==_.ALT
Content-Type: text/html; charset="us-ascii"

<html>
<font face="Courier New, Courier">A New Internet-Draft is available from
the on-line Internet-Drafts directories.<br><br>
<br>
<x-tab>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;</x-tab>Title<x-tab>&nbsp;&nbsp;&nbsp;</x-tab><x-tab>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;</x-tab>:
The Secure Routing Protocol (SRP) for Ad Hoc Networks<br>
<x-tab>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;</x-tab>Author(s)<x-tab>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;</x-tab>:
P. Papadimitratos, Z.J. Haas, P. Samar<br>
<x-tab>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;</x-tab>Filename<x-tab>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;</x-tab>:
draft-papadimitratos-secure-routing-protocol-00.txt<br>
<x-tab>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;</x-tab>Pages<x-tab>&nbsp;&nbsp;&nbsp;</x-tab><x-tab>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;</x-tab>:
14<br>
<x-tab>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;</x-tab>Date<x-tab>&nbsp;&nbsp;&nbsp;&nbsp;</x-tab><x-tab>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;</x-tab>:
2002-12-11<br>
<x-tab>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;</x-tab><br>
This document describes the Secure Routing Protocol (SRP), a route
discovery protocol for ad hoc networks<br>
that mitigates the detrimental effects of maliciously behaving nodes that
disrupt the route discovery in <br>
order to obstruct or disable the network operation. Our protocol provides
correct routing information; i.e.,<br>
factual, up-to-date and authentic connectivity information regarding a
pair of nodes that wish to communicate<br>
in a secure manner. The sole requirement is that any two such end nodes
have a security association. <br>
Accordingly, SRP does not require that any of the intermediate nodes
perform cryptographic operations or <br>
have a prior association with the end nodes. The end-to-end operation of
SRP allows for efficient cryptographic<br>
mechanisms, such as message authentication codes. More importantly, SRP
can be used in a wide range of MANET <br>
instances, without restrictive assumptions on the underlying trust,
network size and membership.<br><br>
A URL for this Internet-Draft is:<br>
</font><font face="Courier New, Courier" color="#0000FF"><u><a href="http://www.ietf.org/internet-drafts/draft-papadimitratos-secure-routing-protocol-00.txt" eudora="autourl">http://www.ietf.org/internet-drafts/draft-papadimitratos-secure-routing-protocol-00.txt</a><br><br>
</u></font><font face="Courier New, Courier">To remove yourself from the
IETF Announcement list, send a message to <br>
ietf-announce-request with the word unsubscribe in the body of the
message.<br><br>
Internet-Drafts are also available by anonymous FTP. Login with the
username<br>
&quot;anonymous&quot; and a password of your e-mail address. After
logging in,<br>
type &quot;cd internet-drafts&quot; and then<br>
<x-tab>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;</x-tab>&quot;get
draft-papadimitratos-secure-routing-protocol-00.txt&quot;.<br><br>
A list of Internet-Drafts directories can be found in<br>
</font><font face="Courier New, Courier" color="#0000FF"><u><a href="http://www.ietf.org/shadow.html" eudora="autourl">http://www.ietf.org/shadow.html</a></u></font><font face="Courier New, Courier">
<br>
or
</font><a href="ftp://ftp.ietf.org/ietf/1shadow-sites.txt" eudora="autourl"><font face="Courier New, Courier" color="#0000FF"><u>ftp://ftp.ietf.org/ietf/1shadow-sites.txt</a><br><br>
<br>
</u></font><font face="Courier New, Courier">Internet-Drafts can also be
obtained by e-mail.<br><br>
Send a message to:<br>
<x-tab>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;</x-tab>mailserv@ietf.org.<br>
In the body type:<br>
<x-tab>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;</x-tab>&quot;FILE
/internet-drafts/draft-papadimitratos-secure-routing-protocol-00.txt&quot;.<br>
<x-tab>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;</x-tab><br>
NOTE:<x-tab>&nbsp;&nbsp;&nbsp;</x-tab>The mail server at ietf.org can
return the document in<br>
<x-tab>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;</x-tab>MIME-encoded
form by using the &quot;mpack&quot; utility.&nbsp; To use this<br>
<x-tab>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;</x-tab>feature,
insert the command &quot;ENCODING mime&quot; before the
&quot;FILE&quot;<br>
<x-tab>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;</x-tab>command.&nbsp;
To decode the response(s), you will need &quot;munpack&quot; or<br>
<x-tab>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;</x-tab>a
MIME-compliant mail reader.&nbsp; Different MIME-compliant mail
readers<br>
<x-tab>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;</x-tab>exhibit
different behavior, especially when dealing with<br>
<x-tab>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;</x-tab>&quot;multipart&quot;
MIME messages (i.e. documents which have been split<br>
<x-tab>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;</x-tab>up into
multiple messages), so check your local documentation on<br>
<x-tab>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;</x-tab>how to
manipulate these messages.<br>
<x-tab>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;</x-tab><x-tab>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;</x-tab><br>
<x-tab>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;</x-tab><x-tab>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;</x-tab><br>
Below is the data which will enable a MIME compliant mail reader<br>
implementation to automatically retrieve the ASCII version of the<br>
Internet-Draft.<br>
</font><font color="#0000FF"><u>&lt;<a href="ftp://ftp.ietf.org/internet-drafts/draft-papadimitratos-secure-routing-protocol-00.txt" eudora="autourl">ftp://ftp.ietf.org/internet-drafts/draft-papadimitratos-secure-routing-protocol-00.txt</a>&gt;</u></font>
<br><br>
</html>

--=====================_5376891==_.ALT--


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



From manet-admin@ietf.org  Wed Dec 18 20:52: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 UAA25330
	for <manet-archive@lists.ietf.org>; Wed, 18 Dec 2002 20:52: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 gBJ1eqv12476;
	Wed, 18 Dec 2002 20:40: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 gBJ1ahv11741
	for <manet@optimus.ietf.org>; Wed, 18 Dec 2002 20:36:43 -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 UAA24384
	for <manet@ietf.org>; Wed, 18 Dec 2002 20:33:34 -0500 (EST)
Received: from HYOJIN.cornell.edu (r106748.resnet.cornell.edu [128.253.122.219])
	by memphis.ece.cornell.edu (8.11.6/8.11.2) with SMTP id gBJ1aYX06802;
	Wed, 18 Dec 2002 20:36:34 -0500
Message-Id: <5.1.0.14.2.20021218203113.01f39e28@memphis.ece.cornell.edu>
X-Sender: papadp@memphis.ece.cornell.edu
X-Mailer: QUALCOMM Windows Eudora Version 5.1
Date: Wed, 18 Dec 2002 20:36:27 -0500
To: manet@ietf.org
From: Panos Papadimitratos <papadp@ece.cornell.edu>
Cc: haas@ece.cornell.edu, samar@ece.cornell.edu, papadp@ece.cornell.edu
Mime-Version: 1.0
Content-Type: multipart/alternative;
	boundary="=====================_5376891==_.ALT"
Subject: [manet] Fwd: I-D
 ACTION:draft-papadimitratos-secure-routing-protocol-00.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>

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

A New Internet-Draft is available from the on-line Internet-Drafts directories.


         Title           : The Secure Routing Protocol (SRP) for Ad Hoc 
Networks
         Author(s)       : P. Papadimitratos, Z.J. Haas, P. Samar
         Filename        : draft-papadimitratos-secure-routing-protocol-00.txt
         Pages           : 14
         Date            : 2002-12-11

This document describes the Secure Routing Protocol (SRP), a route 
discovery protocol for ad hoc networks
that mitigates the detrimental effects of maliciously behaving nodes that 
disrupt the route discovery in
order to obstruct or disable the network operation. Our protocol provides 
correct routing information; i.e.,
factual, up-to-date and authentic connectivity information regarding a pair 
of nodes that wish to communicate
in a secure manner. The sole requirement is that any two such end nodes 
have a security association.
Accordingly, SRP does not require that any of the intermediate nodes 
perform cryptographic operations or
have a prior association with the end nodes. The end-to-end operation of 
SRP allows for efficient cryptographic
mechanisms, such as message authentication codes. More importantly, SRP can 
be used in a wide range of MANET
instances, without restrictive assumptions on the underlying trust, network 
size and membership.

A URL for this Internet-Draft is:
http://www.ietf.org/internet-drafts/draft-papadimitratos-secure-routing-protocol-00.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-papadimitratos-secure-routing-protocol-00.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-papadimitratos-secure-routing-protocol-00.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.
<ftp://ftp.ietf.org/internet-drafts/draft-papadimitratos-secure-routing-protocol-00.txt> 



--=====================_5376891==_.ALT
Content-Type: text/html; charset="us-ascii"

<html>
<font face="Courier New, Courier">A New Internet-Draft is available from
the on-line Internet-Drafts directories.<br><br>
<br>
<x-tab>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;</x-tab>Title<x-tab>&nbsp;&nbsp;&nbsp;</x-tab><x-tab>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;</x-tab>:
The Secure Routing Protocol (SRP) for Ad Hoc Networks<br>
<x-tab>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;</x-tab>Author(s)<x-tab>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;</x-tab>:
P. Papadimitratos, Z.J. Haas, P. Samar<br>
<x-tab>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;</x-tab>Filename<x-tab>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;</x-tab>:
draft-papadimitratos-secure-routing-protocol-00.txt<br>
<x-tab>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;</x-tab>Pages<x-tab>&nbsp;&nbsp;&nbsp;</x-tab><x-tab>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;</x-tab>:
14<br>
<x-tab>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;</x-tab>Date<x-tab>&nbsp;&nbsp;&nbsp;&nbsp;</x-tab><x-tab>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;</x-tab>:
2002-12-11<br>
<x-tab>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;</x-tab><br>
This document describes the Secure Routing Protocol (SRP), a route
discovery protocol for ad hoc networks<br>
that mitigates the detrimental effects of maliciously behaving nodes that
disrupt the route discovery in <br>
order to obstruct or disable the network operation. Our protocol provides
correct routing information; i.e.,<br>
factual, up-to-date and authentic connectivity information regarding a
pair of nodes that wish to communicate<br>
in a secure manner. The sole requirement is that any two such end nodes
have a security association. <br>
Accordingly, SRP does not require that any of the intermediate nodes
perform cryptographic operations or <br>
have a prior association with the end nodes. The end-to-end operation of
SRP allows for efficient cryptographic<br>
mechanisms, such as message authentication codes. More importantly, SRP
can be used in a wide range of MANET <br>
instances, without restrictive assumptions on the underlying trust,
network size and membership.<br><br>
A URL for this Internet-Draft is:<br>
</font><font face="Courier New, Courier" color="#0000FF"><u><a href="http://www.ietf.org/internet-drafts/draft-papadimitratos-secure-routing-protocol-00.txt" eudora="autourl">http://www.ietf.org/internet-drafts/draft-papadimitratos-secure-routing-protocol-00.txt</a><br><br>
</u></font><font face="Courier New, Courier">To remove yourself from the
IETF Announcement list, send a message to <br>
ietf-announce-request with the word unsubscribe in the body of the
message.<br><br>
Internet-Drafts are also available by anonymous FTP. Login with the
username<br>
&quot;anonymous&quot; and a password of your e-mail address. After
logging in,<br>
type &quot;cd internet-drafts&quot; and then<br>
<x-tab>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;</x-tab>&quot;get
draft-papadimitratos-secure-routing-protocol-00.txt&quot;.<br><br>
A list of Internet-Drafts directories can be found in<br>
</font><font face="Courier New, Courier" color="#0000FF"><u><a href="http://www.ietf.org/shadow.html" eudora="autourl">http://www.ietf.org/shadow.html</a></u></font><font face="Courier New, Courier">
<br>
or
</font><a href="ftp://ftp.ietf.org/ietf/1shadow-sites.txt" eudora="autourl"><font face="Courier New, Courier" color="#0000FF"><u>ftp://ftp.ietf.org/ietf/1shadow-sites.txt</a><br><br>
<br>
</u></font><font face="Courier New, Courier">Internet-Drafts can also be
obtained by e-mail.<br><br>
Send a message to:<br>
<x-tab>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;</x-tab>mailserv@ietf.org.<br>
In the body type:<br>
<x-tab>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;</x-tab>&quot;FILE
/internet-drafts/draft-papadimitratos-secure-routing-protocol-00.txt&quot;.<br>
<x-tab>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;</x-tab><br>
NOTE:<x-tab>&nbsp;&nbsp;&nbsp;</x-tab>The mail server at ietf.org can
return the document in<br>
<x-tab>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;</x-tab>MIME-encoded
form by using the &quot;mpack&quot; utility.&nbsp; To use this<br>
<x-tab>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;</x-tab>feature,
insert the command &quot;ENCODING mime&quot; before the
&quot;FILE&quot;<br>
<x-tab>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;</x-tab>command.&nbsp;
To decode the response(s), you will need &quot;munpack&quot; or<br>
<x-tab>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;</x-tab>a
MIME-compliant mail reader.&nbsp; Different MIME-compliant mail
readers<br>
<x-tab>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;</x-tab>exhibit
different behavior, especially when dealing with<br>
<x-tab>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;</x-tab>&quot;multipart&quot;
MIME messages (i.e. documents which have been split<br>
<x-tab>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;</x-tab>up into
multiple messages), so check your local documentation on<br>
<x-tab>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;</x-tab>how to
manipulate these messages.<br>
<x-tab>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;</x-tab><x-tab>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;</x-tab><br>
<x-tab>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;</x-tab><x-tab>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;</x-tab><br>
Below is the data which will enable a MIME compliant mail reader<br>
implementation to automatically retrieve the ASCII version of the<br>
Internet-Draft.<br>
</font><font color="#0000FF"><u>&lt;<a href="ftp://ftp.ietf.org/internet-drafts/draft-papadimitratos-secure-routing-protocol-00.txt" eudora="autourl">ftp://ftp.ietf.org/internet-drafts/draft-papadimitratos-secure-routing-protocol-00.txt</a>&gt;</u></font>
<br><br>
</html>

--=====================_5376891==_.ALT--


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


From mailnull@www1.ietf.org  Wed Dec 18 22:04: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 WAA26968
	for <manet-archive@odin.ietf.org>; Wed, 18 Dec 2002 22:04:42 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id gBJ37LN17099
	for manet-archive@odin.ietf.org; Wed, 18 Dec 2002 22:07: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 gBJ37Lv17096
	for <manet-web-archive@optimus.ietf.org>; Wed, 18 Dec 2002 22:07: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 WAA26962
	for <manet-web-archive@ietf.org>; Wed, 18 Dec 2002 22:04: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 gBJ1nHv12850;
	Wed, 18 Dec 2002 20:49: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 gBJ1mnv12800
	for <manet@optimus.ietf.org>; Wed, 18 Dec 2002 20:48:49 -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 UAA24912
	for <manet@ietf.org>; Wed, 18 Dec 2002 20:45:39 -0500 (EST)
Received: from HYOJIN.cornell.edu (r106748.resnet.cornell.edu [128.253.122.219])
	by memphis.ece.cornell.edu (8.11.6/8.11.2) with SMTP id gBJ1meX07031;
	Wed, 18 Dec 2002 20:48:40 -0500
Message-Id: <5.1.0.14.2.20021218204613.01ecfca0@memphis.ece.cornell.edu>
X-Sender: papadp@memphis.ece.cornell.edu
X-Mailer: QUALCOMM Windows Eudora Version 5.1
Date: Wed, 18 Dec 2002 20:48:33 -0500
To: manet@ietf.org
From: Panos Papadimitratos <papadp@ece.cornell.edu>
Cc: haas@ece.cornell.edu, samar@ece.cornell.edu, papadp@ece.cornell.edu
Mime-Version: 1.0
Content-Type: multipart/alternative;
	boundary="=====================_6103125==_.ALT"
Subject: [manet] Fwd: I-D
 ACTION:draft-papadimitratos-secure-routing-protocol-00.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>

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

A New Internet-Draft is available from the on-line Internet-Drafts directories.


         Title           : The Secure Routing Protocol (SRP) for Ad Hoc 
Networks
         Author(s)       : P. Papadimitratos, Z.J. Haas, P. Samar
         Filename        : draft-papadimitratos-secure-routing-protocol-00.txt
         Pages           : 14
         Date            : 2002-12-11

This document describes the Secure Routing Protocol (SRP), a route 
discovery protocol for ad hoc networks
that mitigates the detrimental effects of maliciously behaving nodes that 
disrupt the route discovery in
order to obstruct or disable the network operation. Our protocol provides 
correct routing information; i.e.,
factual, up-to-date and authentic connectivity information regarding a pair 
of nodes that wish to communicate
in a secure manner. The sole requirement is that any two such end nodes 
have a security association.
Accordingly, SRP does not require that any of the intermediate nodes 
perform cryptographic operations or
have a prior association with the end nodes. The end-to-end operation of 
SRP allows for efficient cryptographic
mechanisms, such as message authentication codes. More importantly, SRP can 
be used in a wide range of MANET
instances, without restrictive assumptions on the underlying trust, network 
size and membership.

A URL for this Internet-Draft is:
http://www.ietf.org/internet-drafts/draft-papadimitratos-secure-routing-protocol-00.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-papadimitratos-secure-routing-protocol-00.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-papadimitratos-secure-routing-protocol-00.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.
<ftp://ftp.ietf.org/internet-drafts/draft-papadimitratos-secure-routing-protocol-00.txt> 



--=====================_6103125==_.ALT
Content-Type: text/html; charset="us-ascii"

<html>
<font face="Courier New, Courier">A New Internet-Draft is available from
the on-line Internet-Drafts directories.<br><br>
<br>
<x-tab>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;</x-tab>Title<x-tab>&nbsp;&nbsp;&nbsp;</x-tab><x-tab>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;</x-tab>:
The Secure Routing Protocol (SRP) for Ad Hoc Networks<br>
<x-tab>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;</x-tab>Author(s)<x-tab>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;</x-tab>:
P. Papadimitratos, Z.J. Haas, P. Samar<br>
<x-tab>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;</x-tab>Filename<x-tab>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;</x-tab>:
draft-papadimitratos-secure-routing-protocol-00.txt<br>
<x-tab>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;</x-tab>Pages<x-tab>&nbsp;&nbsp;&nbsp;</x-tab><x-tab>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;</x-tab>:
14<br>
<x-tab>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;</x-tab>Date<x-tab>&nbsp;&nbsp;&nbsp;&nbsp;</x-tab><x-tab>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;</x-tab>:
2002-12-11<br>
<x-tab>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;</x-tab><br>
This document describes the Secure Routing Protocol (SRP), a route
discovery protocol for ad hoc networks<br>
that mitigates the detrimental effects of maliciously behaving nodes that
disrupt the route discovery in <br>
order to obstruct or disable the network operation. Our protocol provides
correct routing information; i.e.,<br>
factual, up-to-date and authentic connectivity information regarding a
pair of nodes that wish to communicate<br>
in a secure manner. The sole requirement is that any two such end nodes
have a security association. <br>
Accordingly, SRP does not require that any of the intermediate nodes
perform cryptographic operations or <br>
have a prior association with the end nodes. The end-to-end operation of
SRP allows for efficient cryptographic<br>
mechanisms, such as message authentication codes. More importantly, SRP
can be used in a wide range of MANET <br>
instances, without restrictive assumptions on the underlying trust,
network size and membership.<br><br>
A URL for this Internet-Draft is:<br>
</font><font face="Courier New, Courier" color="#0000FF"><u><a href="http://www.ietf.org/internet-drafts/draft-papadimitratos-secure-routing-protocol-00.txt" eudora="autourl">http://www.ietf.org/internet-drafts/draft-papadimitratos-secure-routing-protocol-00.txt</a><br><br>
</u></font><font face="Courier New, Courier">To remove yourself from the
IETF Announcement list, send a message to <br>
ietf-announce-request with the word unsubscribe in the body of the
message.<br><br>
Internet-Drafts are also available by anonymous FTP. Login with the
username<br>
&quot;anonymous&quot; and a password of your e-mail address. After
logging in,<br>
type &quot;cd internet-drafts&quot; and then<br>
<x-tab>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;</x-tab>&quot;get
draft-papadimitratos-secure-routing-protocol-00.txt&quot;.<br><br>
A list of Internet-Drafts directories can be found in<br>
</font><font face="Courier New, Courier" color="#0000FF"><u><a href="http://www.ietf.org/shadow.html" eudora="autourl">http://www.ietf.org/shadow.html</a></u></font><font face="Courier New, Courier">
<br>
or
</font><a href="ftp://ftp.ietf.org/ietf/1shadow-sites.txt" eudora="autourl"><font face="Courier New, Courier" color="#0000FF"><u>ftp://ftp.ietf.org/ietf/1shadow-sites.txt</a><br><br>
<br>
</u></font><font face="Courier New, Courier">Internet-Drafts can also be
obtained by e-mail.<br><br>
Send a message to:<br>
<x-tab>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;</x-tab>mailserv@ietf.org.<br>
In the body type:<br>
<x-tab>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;</x-tab>&quot;FILE
/internet-drafts/draft-papadimitratos-secure-routing-protocol-00.txt&quot;.<br>
<x-tab>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;</x-tab><br>
NOTE:<x-tab>&nbsp;&nbsp;&nbsp;</x-tab>The mail server at ietf.org can
return the document in<br>
<x-tab>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;</x-tab>MIME-encoded
form by using the &quot;mpack&quot; utility.&nbsp; To use this<br>
<x-tab>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;</x-tab>feature,
insert the command &quot;ENCODING mime&quot; before the
&quot;FILE&quot;<br>
<x-tab>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;</x-tab>command.&nbsp;
To decode the response(s), you will need &quot;munpack&quot; or<br>
<x-tab>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;</x-tab>a
MIME-compliant mail reader.&nbsp; Different MIME-compliant mail
readers<br>
<x-tab>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;</x-tab>exhibit
different behavior, especially when dealing with<br>
<x-tab>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;</x-tab>&quot;multipart&quot;
MIME messages (i.e. documents which have been split<br>
<x-tab>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;</x-tab>up into
multiple messages), so check your local documentation on<br>
<x-tab>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;</x-tab>how to
manipulate these messages.<br>
<x-tab>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;</x-tab><x-tab>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;</x-tab><br>
<x-tab>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;</x-tab><x-tab>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;</x-tab><br>
Below is the data which will enable a MIME compliant mail reader<br>
implementation to automatically retrieve the ASCII version of the<br>
Internet-Draft.<br>
</font><font color="#0000FF"><u>&lt;<a href="ftp://ftp.ietf.org/internet-drafts/draft-papadimitratos-secure-routing-protocol-00.txt" eudora="autourl">ftp://ftp.ietf.org/internet-drafts/draft-papadimitratos-secure-routing-protocol-00.txt</a>&gt;</u></font>
<br><br>
</html>

--=====================_6103125==_.ALT--


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



From manet-admin@ietf.org  Wed Dec 18 22:05: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 WAA26996
	for <manet-archive@lists.ietf.org>; Wed, 18 Dec 2002 22:05: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 gBJ1nHv12850;
	Wed, 18 Dec 2002 20:49: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 gBJ1mnv12800
	for <manet@optimus.ietf.org>; Wed, 18 Dec 2002 20:48:49 -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 UAA24912
	for <manet@ietf.org>; Wed, 18 Dec 2002 20:45:39 -0500 (EST)
Received: from HYOJIN.cornell.edu (r106748.resnet.cornell.edu [128.253.122.219])
	by memphis.ece.cornell.edu (8.11.6/8.11.2) with SMTP id gBJ1meX07031;
	Wed, 18 Dec 2002 20:48:40 -0500
Message-Id: <5.1.0.14.2.20021218204613.01ecfca0@memphis.ece.cornell.edu>
X-Sender: papadp@memphis.ece.cornell.edu
X-Mailer: QUALCOMM Windows Eudora Version 5.1
Date: Wed, 18 Dec 2002 20:48:33 -0500
To: manet@ietf.org
From: Panos Papadimitratos <papadp@ece.cornell.edu>
Cc: haas@ece.cornell.edu, samar@ece.cornell.edu, papadp@ece.cornell.edu
Mime-Version: 1.0
Content-Type: multipart/alternative;
	boundary="=====================_6103125==_.ALT"
Subject: [manet] Fwd: I-D
 ACTION:draft-papadimitratos-secure-routing-protocol-00.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>

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

A New Internet-Draft is available from the on-line Internet-Drafts directories.


         Title           : The Secure Routing Protocol (SRP) for Ad Hoc 
Networks
         Author(s)       : P. Papadimitratos, Z.J. Haas, P. Samar
         Filename        : draft-papadimitratos-secure-routing-protocol-00.txt
         Pages           : 14
         Date            : 2002-12-11

This document describes the Secure Routing Protocol (SRP), a route 
discovery protocol for ad hoc networks
that mitigates the detrimental effects of maliciously behaving nodes that 
disrupt the route discovery in
order to obstruct or disable the network operation. Our protocol provides 
correct routing information; i.e.,
factual, up-to-date and authentic connectivity information regarding a pair 
of nodes that wish to communicate
in a secure manner. The sole requirement is that any two such end nodes 
have a security association.
Accordingly, SRP does not require that any of the intermediate nodes 
perform cryptographic operations or
have a prior association with the end nodes. The end-to-end operation of 
SRP allows for efficient cryptographic
mechanisms, such as message authentication codes. More importantly, SRP can 
be used in a wide range of MANET
instances, without restrictive assumptions on the underlying trust, network 
size and membership.

A URL for this Internet-Draft is:
http://www.ietf.org/internet-drafts/draft-papadimitratos-secure-routing-protocol-00.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-papadimitratos-secure-routing-protocol-00.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-papadimitratos-secure-routing-protocol-00.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.
<ftp://ftp.ietf.org/internet-drafts/draft-papadimitratos-secure-routing-protocol-00.txt> 



--=====================_6103125==_.ALT
Content-Type: text/html; charset="us-ascii"

<html>
<font face="Courier New, Courier">A New Internet-Draft is available from
the on-line Internet-Drafts directories.<br><br>
<br>
<x-tab>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;</x-tab>Title<x-tab>&nbsp;&nbsp;&nbsp;</x-tab><x-tab>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;</x-tab>:
The Secure Routing Protocol (SRP) for Ad Hoc Networks<br>
<x-tab>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;</x-tab>Author(s)<x-tab>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;</x-tab>:
P. Papadimitratos, Z.J. Haas, P. Samar<br>
<x-tab>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;</x-tab>Filename<x-tab>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;</x-tab>:
draft-papadimitratos-secure-routing-protocol-00.txt<br>
<x-tab>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;</x-tab>Pages<x-tab>&nbsp;&nbsp;&nbsp;</x-tab><x-tab>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;</x-tab>:
14<br>
<x-tab>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;</x-tab>Date<x-tab>&nbsp;&nbsp;&nbsp;&nbsp;</x-tab><x-tab>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;</x-tab>:
2002-12-11<br>
<x-tab>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;</x-tab><br>
This document describes the Secure Routing Protocol (SRP), a route
discovery protocol for ad hoc networks<br>
that mitigates the detrimental effects of maliciously behaving nodes that
disrupt the route discovery in <br>
order to obstruct or disable the network operation. Our protocol provides
correct routing information; i.e.,<br>
factual, up-to-date and authentic connectivity information regarding a
pair of nodes that wish to communicate<br>
in a secure manner. The sole requirement is that any two such end nodes
have a security association. <br>
Accordingly, SRP does not require that any of the intermediate nodes
perform cryptographic operations or <br>
have a prior association with the end nodes. The end-to-end operation of
SRP allows for efficient cryptographic<br>
mechanisms, such as message authentication codes. More importantly, SRP
can be used in a wide range of MANET <br>
instances, without restrictive assumptions on the underlying trust,
network size and membership.<br><br>
A URL for this Internet-Draft is:<br>
</font><font face="Courier New, Courier" color="#0000FF"><u><a href="http://www.ietf.org/internet-drafts/draft-papadimitratos-secure-routing-protocol-00.txt" eudora="autourl">http://www.ietf.org/internet-drafts/draft-papadimitratos-secure-routing-protocol-00.txt</a><br><br>
</u></font><font face="Courier New, Courier">To remove yourself from the
IETF Announcement list, send a message to <br>
ietf-announce-request with the word unsubscribe in the body of the
message.<br><br>
Internet-Drafts are also available by anonymous FTP. Login with the
username<br>
&quot;anonymous&quot; and a password of your e-mail address. After
logging in,<br>
type &quot;cd internet-drafts&quot; and then<br>
<x-tab>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;</x-tab>&quot;get
draft-papadimitratos-secure-routing-protocol-00.txt&quot;.<br><br>
A list of Internet-Drafts directories can be found in<br>
</font><font face="Courier New, Courier" color="#0000FF"><u><a href="http://www.ietf.org/shadow.html" eudora="autourl">http://www.ietf.org/shadow.html</a></u></font><font face="Courier New, Courier">
<br>
or
</font><a href="ftp://ftp.ietf.org/ietf/1shadow-sites.txt" eudora="autourl"><font face="Courier New, Courier" color="#0000FF"><u>ftp://ftp.ietf.org/ietf/1shadow-sites.txt</a><br><br>
<br>
</u></font><font face="Courier New, Courier">Internet-Drafts can also be
obtained by e-mail.<br><br>
Send a message to:<br>
<x-tab>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;</x-tab>mailserv@ietf.org.<br>
In the body type:<br>
<x-tab>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;</x-tab>&quot;FILE
/internet-drafts/draft-papadimitratos-secure-routing-protocol-00.txt&quot;.<br>
<x-tab>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;</x-tab><br>
NOTE:<x-tab>&nbsp;&nbsp;&nbsp;</x-tab>The mail server at ietf.org can
return the document in<br>
<x-tab>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;</x-tab>MIME-encoded
form by using the &quot;mpack&quot; utility.&nbsp; To use this<br>
<x-tab>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;</x-tab>feature,
insert the command &quot;ENCODING mime&quot; before the
&quot;FILE&quot;<br>
<x-tab>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;</x-tab>command.&nbsp;
To decode the response(s), you will need &quot;munpack&quot; or<br>
<x-tab>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;</x-tab>a
MIME-compliant mail reader.&nbsp; Different MIME-compliant mail
readers<br>
<x-tab>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;</x-tab>exhibit
different behavior, especially when dealing with<br>
<x-tab>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;</x-tab>&quot;multipart&quot;
MIME messages (i.e. documents which have been split<br>
<x-tab>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;</x-tab>up into
multiple messages), so check your local documentation on<br>
<x-tab>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;</x-tab>how to
manipulate these messages.<br>
<x-tab>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;</x-tab><x-tab>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;</x-tab><br>
<x-tab>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;</x-tab><x-tab>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;</x-tab><br>
Below is the data which will enable a MIME compliant mail reader<br>
implementation to automatically retrieve the ASCII version of the<br>
Internet-Draft.<br>
</font><font color="#0000FF"><u>&lt;<a href="ftp://ftp.ietf.org/internet-drafts/draft-papadimitratos-secure-routing-protocol-00.txt" eudora="autourl">ftp://ftp.ietf.org/internet-drafts/draft-papadimitratos-secure-routing-protocol-00.txt</a>&gt;</u></font>
<br><br>
</html>

--=====================_6103125==_.ALT--


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


From manet-admin@ietf.org  Wed Dec 18 23:18: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 XAA28422
	for <manet-archive@lists.ietf.org>; Wed, 18 Dec 2002 23:18: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 gBJ4BKv19920;
	Wed, 18 Dec 2002 23:11: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 gBJ46mv19218
	for <manet@optimus.ietf.org>; Wed, 18 Dec 2002 23:06:48 -0500
Received: from sm203.163.com (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id XAA28280
	for <manet@ietf.org>; Wed, 18 Dec 2002 23:03:26 -0500 (EST)
Received: from localhost (localhost [127.0.0.1])
	by sm203.163.com (Postfix) with SMTP id 6CA3D1C96B309
	for <manet@ietf.org>; Thu, 19 Dec 2002 12:05:18 +0800 (CST)
Received: from RavProxy (unknown [61.187.64.26])
	by 192.168.1.203 (Coremail) with SMTP id im8EAH1FAT7UAkAa.1
	for <manet@ietf.org>; Thu, 19 Dec 2002 12:05:18 +0800 (CST)
Message-ID: <000f01c2a713$769971a0$7600a8c0@zyn>
From: "Zhang Yanan" <csu_zyn@163.com>
To: <manet@ietf.org>
Date: Thu, 19 Dec 2002 12:02:35 +0800
MIME-Version: 1.0
Content-Type: multipart/alternative;
	boundary="----=_NextPart_000_000C_01C2A756.84837930"
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] Question about Cbr transmission
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_000C_01C2A756.84837930
Content-Type: text/plain;
	charset="gb2312"
Content-Transfer-Encoding: base64

SGksDQpJIHVzZSBEU1IgcHJvdG9jb2wgdG8gdHJhbnNtaXQgQ0JSIFBhY2tldHMuIA0KDQpJIGNh
biBzZWUgaW4gdGhlIG5ldHdvcmsgbGF5ZXIsIHRoZSBwYWNrZXQgaXMgdHJhbnNtaXRlZCwgYnV0
IGluIHRoZSBhcHBsaWNhdGlvbiBsYXllciBjYW4gb25seSByZWNlaXZlIGEgbGl0dGxlLiANCkkg
aGF2ZSByZWFkIHRoZSBjb2RlIG9mIGNiciB0cmFuc21pdCBpbiBBcHAgbGF5ZXIsIEkgZmluZCB0
aGF0IHRoZSBDQlIgZGF0YSBoYXMgYSBzZXFObywgd2hlbiBkb2VzIGl0IGluY3JlYXNlPyANClRo
ZSBDb2RlIGlzIDoNCg0KICAgICAgICAgICAgR2xvbW9BcHBDYnJTZXJ2ZXIgKnNlcnZlclB0cjsN
CiAgICAgICAgICAgIEdsb21vQXBwQ2JyRGF0YSBkYXRhOw0KDQogICAgICAgICAgICBpZiAoZGF0
YS5zZXFObyA+PSBzZXJ2ZXJQdHItPnNlcU5vKQ0KICAgICAgICAgICAgew0KICAgICAgICAgICAg
ICAgIHNlcnZlclB0ci0+bnVtUGt0c1JlY3ZkKys7DQogICAgICAgICAgICAgICAgLy90aGUgc3Rh
dGlzdGljYWwgZGF0YSBvZiByZWNlaXZlZCBQa3QgKysNCiAgICAgICAgICAgIH0NCg0KVGhpcyBj
YXVzZXMgbXkgQXBwIGxheWVyIHJlY2VpdmVkIFBrdCBmcmFjdGlvbiB2ZXJ5IGJhZChhYm91dCA2
MCUpICxidXQgdGhlIE5ldHdvcmsgbGF5ZXIgUGt0IGRlbGl2ZXJ5IEZyYWN0aW9uIGlzIHZlcnkg
Z29vZChhYm91dCA5MCUpLg0KDQpNeSBzaW11bGF0aW9uIHRvb2wgaXMgR2xvbW9zaW0yLjAzLg0K
VGhlIG51bWJlciBvZiBub2RlIGlzIDUwLCAgIFRFUlJBSU4tRElNRU5TSU9OUyAgKDEyMDAsIDEy
MDApLCAgUkFESU8tVFgtUE9XRVIgMi40NShyYWRpbyByYW5nZTo1MDAuNG0pDQpUaGUgbnVtYmVy
IG9mIENiciBzb3VyY2VzIGlzIDEwKGUuZy4gQ0JSICAwICAyIDE4MCA1MTIgMVMgMFMgMFMpICwg
U2ltdWxhdGlvbiB0aW1lIGlzIDkwMHMuDQoNCldoeSBteSByZXN1bHQgaXMgdGhpcyA/DQoNClRo
YW5rcyBpbiBBZHZhbmNlISENCg==

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

PCFET0NUWVBFIEhUTUwgUFVCTElDICItLy9XM0MvL0RURCBIVE1MIDQuMCBUcmFuc2l0aW9uYWwv
L0VOIj4NCjxIVE1MPjxIRUFEPg0KPE1FVEEgaHR0cC1lcXVpdj1Db250ZW50LVR5cGUgY29udGVu
dD0idGV4dC9odG1sOyBjaGFyc2V0PWdiMjMxMiI+DQo8TUVUQSBjb250ZW50PSJNU0hUTUwgNi4w
MC4yNjAwLjAiIG5hbWU9R0VORVJBVE9SPg0KPFNUWUxFPjwvU1RZTEU+DQo8L0hFQUQ+DQo8Qk9E
WSBiZ0NvbG9yPSNmZmZmZmY+DQo8RElWPjxGT05UIHNpemU9Mj5IaSw8L0ZPTlQ+PC9ESVY+DQo8
RElWPjxGT05UIHNpemU9Mj5JIHVzZSBEU1IgcHJvdG9jb2wgdG8gdHJhbnNtaXQgQ0JSIFBhY2tl
dHMuIDwvRk9OVD48L0RJVj4NCjxESVY+PEZPTlQgc2l6ZT0yPjwvRk9OVD4mbmJzcDs8L0RJVj4N
CjxESVY+PEZPTlQgc2l6ZT0yPkkgY2FuIHNlZSBpbiB0aGUgbmV0d29yayBsYXllciwgdGhlIHBh
Y2tldCBpcyB0cmFuc21pdGVkLCBidXQgDQppbiB0aGUgYXBwbGljYXRpb24gbGF5ZXIgY2FuIG9u
bHkgcmVjZWl2ZSBhIGxpdHRsZS4gPC9GT05UPjwvRElWPg0KPERJVj48Rk9OVCBzaXplPTI+SSBo
YXZlIHJlYWQgdGhlIGNvZGUgb2YgY2JyIHRyYW5zbWl0IGluIEFwcCBsYXllciwgSSBmaW5kIHRo
YXQgDQp0aGUgQ0JSIGRhdGEgaGFzIGEgc2VxTm8sIHdoZW4gZG9lcyBpdCBpbmNyZWFzZT8gPC9G
T05UPjwvRElWPg0KPERJVj48Rk9OVCBzaXplPTI+VGhlIENvZGUgaXMgOjwvRk9OVD48L0RJVj4N
CjxESVY+PEZPTlQgc2l6ZT0yPjwvRk9OVD4mbmJzcDs8L0RJVj4NCjxESVY+PEZPTlQgc2l6ZT0y
PiZuYnNwOyZuYnNwOyZuYnNwOyAmbmJzcDsmbmJzcDsmbmJzcDsgJm5ic3A7Jm5ic3A7Jm5ic3A7
IA0KR2xvbW9BcHBDYnJTZXJ2ZXIgKnNlcnZlclB0cjs8L0ZPTlQ+PC9ESVY+DQo8RElWPjxGT05U
IA0Kc2l6ZT0yPiZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNw
OyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwO0dsb21vQXBwQ2JyRGF0YSANCmRhdGE7PC9GT05UPjwv
RElWPg0KPERJVj48Rk9OVCBzaXplPTI+PC9GT05UPiZuYnNwOzwvRElWPg0KPERJVj48Rk9OVCAN
CnNpemU9Mj4mbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsm
bmJzcDsmbmJzcDsmbmJzcDsmbmJzcDtpZiANCihkYXRhLnNlcU5vICZndDs9IA0Kc2VydmVyUHRy
LSZndDtzZXFObyk8QlI+Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7
Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7IA0KezxCUj4mbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsm
bmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJz
cDsmbmJzcDsgDQpzZXJ2ZXJQdHItJmd0O251bVBrdHNSZWN2ZCsrOzwvRk9OVD48L0RJVj4NCjxE
SVY+PEZPTlQgc2l6ZT0yPiZuYnNwOyZuYnNwOyZuYnNwOyAmbmJzcDsmbmJzcDsmbmJzcDsgJm5i
c3A7Jm5ic3A7Jm5ic3A7IA0KJm5ic3A7Jm5ic3A7Jm5ic3A7IC8vdGhlIHN0YXRpc3RpY2FsIGRh
dGEgb2YgcmVjZWl2ZWQgUGt0ICsrPC9GT05UPjwvRElWPg0KPERJVj48Rk9OVCANCnNpemU9Mj4m
bmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJz
cDsmbmJzcDsmbmJzcDt9PC9GT05UPjwvRElWPg0KPERJVj48Rk9OVCBzaXplPTI+PC9GT05UPiZu
YnNwOzwvRElWPg0KPERJVj48Rk9OVCBzaXplPTI+VGhpcyBjYXVzZXMgbXkgQXBwIGxheWVyIHJl
Y2VpdmVkIFBrdCBmcmFjdGlvbiB2ZXJ5IGJhZChhYm91dCANCjYwJSkgLGJ1dCB0aGUgTmV0d29y
ayBsYXllciBQa3QgZGVsaXZlcnkgRnJhY3Rpb24gaXMgdmVyeSBnb29kKGFib3V0IA0KOTAlKS48
L0ZPTlQ+PC9ESVY+DQo8RElWPjxGT05UIHNpemU9Mj48L0ZPTlQ+Jm5ic3A7PC9ESVY+DQo8RElW
PjxGT05UIHNpemU9Mj5NeSBzaW11bGF0aW9uIHRvb2wgaXMgDQo8U1RST05HPkdsb21vc2ltMi4w
MzwvU1RST05HPi48L0ZPTlQ+PC9ESVY+DQo8RElWPjxGT05UIHNpemU9Mj5UaGUgbnVtYmVyIG9m
IG5vZGUgaXMgNTAsJm5ic3A7Jm5ic3A7IFRFUlJBSU4tRElNRU5TSU9OUyZuYnNwOyANCigxMjAw
LCAxMjAwKSwmbmJzcDsgUkFESU8tVFgtUE9XRVImbmJzcDsyLjQ1KHJhZGlvIHJhbmdlOjUwMC40
bSk8L0ZPTlQ+PC9ESVY+DQo8RElWPjxGT05UIHNpemU9Mj5UaGUgbnVtYmVyIG9mIENiciBzb3Vy
Y2VzIGlzIDEwKGUuZy4gQ0JSJm5ic3A7IDAmbmJzcDsgMiAxODAgDQo1MTIgMVMgMFMgMFMpICwg
U2ltdWxhdGlvbiB0aW1lIGlzIDkwMHMuPC9GT05UPjwvRElWPg0KPERJVj48Rk9OVCBzaXplPTI+
PC9GT05UPiZuYnNwOzwvRElWPg0KPERJVj48Rk9OVCBzaXplPTI+V2h5IG15IHJlc3VsdCBpcyB0
aGlzID88L0ZPTlQ+PC9ESVY+DQo8RElWPjxGT05UIHNpemU9Mj48L0ZPTlQ+Jm5ic3A7PC9ESVY+
DQo8RElWPjxGT05UIHNpemU9Mj5UaGFua3MgaW4gQWR2YW5jZSEhPC9GT05UPjwvRElWPjwvQk9E
WT48L0hUTUw+DQo=

------=_NextPart_000_000C_01C2A756.84837930--

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


From mailnull@www1.ietf.org  Wed Dec 18 23:33: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 XAA28667
	for <manet-archive@odin.ietf.org>; Wed, 18 Dec 2002 23:33:00 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id gBJ4Zct20564
	for manet-archive@odin.ietf.org; Wed, 18 Dec 2002 23:35: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 gBJ4Zcv20561
	for <manet-web-archive@optimus.ietf.org>; Wed, 18 Dec 2002 23:35:38 -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 XAA28664
	for <manet-web-archive@ietf.org>; Wed, 18 Dec 2002 23:32: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 gBJ4BKv19920;
	Wed, 18 Dec 2002 23:11: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 gBJ46mv19218
	for <manet@optimus.ietf.org>; Wed, 18 Dec 2002 23:06:48 -0500
Received: from sm203.163.com (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id XAA28280
	for <manet@ietf.org>; Wed, 18 Dec 2002 23:03:26 -0500 (EST)
Received: from localhost (localhost [127.0.0.1])
	by sm203.163.com (Postfix) with SMTP id 6CA3D1C96B309
	for <manet@ietf.org>; Thu, 19 Dec 2002 12:05:18 +0800 (CST)
Received: from RavProxy (unknown [61.187.64.26])
	by 192.168.1.203 (Coremail) with SMTP id im8EAH1FAT7UAkAa.1
	for <manet@ietf.org>; Thu, 19 Dec 2002 12:05:18 +0800 (CST)
Message-ID: <000f01c2a713$769971a0$7600a8c0@zyn>
From: "Zhang Yanan" <csu_zyn@163.com>
To: <manet@ietf.org>
Date: Thu, 19 Dec 2002 12:02:35 +0800
MIME-Version: 1.0
Content-Type: multipart/alternative;
	boundary="----=_NextPart_000_000C_01C2A756.84837930"
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] Question about Cbr transmission
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_000C_01C2A756.84837930
Content-Type: text/plain;
	charset="gb2312"
Content-Transfer-Encoding: base64

SGksDQpJIHVzZSBEU1IgcHJvdG9jb2wgdG8gdHJhbnNtaXQgQ0JSIFBhY2tldHMuIA0KDQpJIGNh
biBzZWUgaW4gdGhlIG5ldHdvcmsgbGF5ZXIsIHRoZSBwYWNrZXQgaXMgdHJhbnNtaXRlZCwgYnV0
IGluIHRoZSBhcHBsaWNhdGlvbiBsYXllciBjYW4gb25seSByZWNlaXZlIGEgbGl0dGxlLiANCkkg
aGF2ZSByZWFkIHRoZSBjb2RlIG9mIGNiciB0cmFuc21pdCBpbiBBcHAgbGF5ZXIsIEkgZmluZCB0
aGF0IHRoZSBDQlIgZGF0YSBoYXMgYSBzZXFObywgd2hlbiBkb2VzIGl0IGluY3JlYXNlPyANClRo
ZSBDb2RlIGlzIDoNCg0KICAgICAgICAgICAgR2xvbW9BcHBDYnJTZXJ2ZXIgKnNlcnZlclB0cjsN
CiAgICAgICAgICAgIEdsb21vQXBwQ2JyRGF0YSBkYXRhOw0KDQogICAgICAgICAgICBpZiAoZGF0
YS5zZXFObyA+PSBzZXJ2ZXJQdHItPnNlcU5vKQ0KICAgICAgICAgICAgew0KICAgICAgICAgICAg
ICAgIHNlcnZlclB0ci0+bnVtUGt0c1JlY3ZkKys7DQogICAgICAgICAgICAgICAgLy90aGUgc3Rh
dGlzdGljYWwgZGF0YSBvZiByZWNlaXZlZCBQa3QgKysNCiAgICAgICAgICAgIH0NCg0KVGhpcyBj
YXVzZXMgbXkgQXBwIGxheWVyIHJlY2VpdmVkIFBrdCBmcmFjdGlvbiB2ZXJ5IGJhZChhYm91dCA2
MCUpICxidXQgdGhlIE5ldHdvcmsgbGF5ZXIgUGt0IGRlbGl2ZXJ5IEZyYWN0aW9uIGlzIHZlcnkg
Z29vZChhYm91dCA5MCUpLg0KDQpNeSBzaW11bGF0aW9uIHRvb2wgaXMgR2xvbW9zaW0yLjAzLg0K
VGhlIG51bWJlciBvZiBub2RlIGlzIDUwLCAgIFRFUlJBSU4tRElNRU5TSU9OUyAgKDEyMDAsIDEy
MDApLCAgUkFESU8tVFgtUE9XRVIgMi40NShyYWRpbyByYW5nZTo1MDAuNG0pDQpUaGUgbnVtYmVy
IG9mIENiciBzb3VyY2VzIGlzIDEwKGUuZy4gQ0JSICAwICAyIDE4MCA1MTIgMVMgMFMgMFMpICwg
U2ltdWxhdGlvbiB0aW1lIGlzIDkwMHMuDQoNCldoeSBteSByZXN1bHQgaXMgdGhpcyA/DQoNClRo
YW5rcyBpbiBBZHZhbmNlISENCg==

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

PCFET0NUWVBFIEhUTUwgUFVCTElDICItLy9XM0MvL0RURCBIVE1MIDQuMCBUcmFuc2l0aW9uYWwv
L0VOIj4NCjxIVE1MPjxIRUFEPg0KPE1FVEEgaHR0cC1lcXVpdj1Db250ZW50LVR5cGUgY29udGVu
dD0idGV4dC9odG1sOyBjaGFyc2V0PWdiMjMxMiI+DQo8TUVUQSBjb250ZW50PSJNU0hUTUwgNi4w
MC4yNjAwLjAiIG5hbWU9R0VORVJBVE9SPg0KPFNUWUxFPjwvU1RZTEU+DQo8L0hFQUQ+DQo8Qk9E
WSBiZ0NvbG9yPSNmZmZmZmY+DQo8RElWPjxGT05UIHNpemU9Mj5IaSw8L0ZPTlQ+PC9ESVY+DQo8
RElWPjxGT05UIHNpemU9Mj5JIHVzZSBEU1IgcHJvdG9jb2wgdG8gdHJhbnNtaXQgQ0JSIFBhY2tl
dHMuIDwvRk9OVD48L0RJVj4NCjxESVY+PEZPTlQgc2l6ZT0yPjwvRk9OVD4mbmJzcDs8L0RJVj4N
CjxESVY+PEZPTlQgc2l6ZT0yPkkgY2FuIHNlZSBpbiB0aGUgbmV0d29yayBsYXllciwgdGhlIHBh
Y2tldCBpcyB0cmFuc21pdGVkLCBidXQgDQppbiB0aGUgYXBwbGljYXRpb24gbGF5ZXIgY2FuIG9u
bHkgcmVjZWl2ZSBhIGxpdHRsZS4gPC9GT05UPjwvRElWPg0KPERJVj48Rk9OVCBzaXplPTI+SSBo
YXZlIHJlYWQgdGhlIGNvZGUgb2YgY2JyIHRyYW5zbWl0IGluIEFwcCBsYXllciwgSSBmaW5kIHRo
YXQgDQp0aGUgQ0JSIGRhdGEgaGFzIGEgc2VxTm8sIHdoZW4gZG9lcyBpdCBpbmNyZWFzZT8gPC9G
T05UPjwvRElWPg0KPERJVj48Rk9OVCBzaXplPTI+VGhlIENvZGUgaXMgOjwvRk9OVD48L0RJVj4N
CjxESVY+PEZPTlQgc2l6ZT0yPjwvRk9OVD4mbmJzcDs8L0RJVj4NCjxESVY+PEZPTlQgc2l6ZT0y
PiZuYnNwOyZuYnNwOyZuYnNwOyAmbmJzcDsmbmJzcDsmbmJzcDsgJm5ic3A7Jm5ic3A7Jm5ic3A7
IA0KR2xvbW9BcHBDYnJTZXJ2ZXIgKnNlcnZlclB0cjs8L0ZPTlQ+PC9ESVY+DQo8RElWPjxGT05U
IA0Kc2l6ZT0yPiZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNw
OyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwO0dsb21vQXBwQ2JyRGF0YSANCmRhdGE7PC9GT05UPjwv
RElWPg0KPERJVj48Rk9OVCBzaXplPTI+PC9GT05UPiZuYnNwOzwvRElWPg0KPERJVj48Rk9OVCAN
CnNpemU9Mj4mbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsm
bmJzcDsmbmJzcDsmbmJzcDsmbmJzcDtpZiANCihkYXRhLnNlcU5vICZndDs9IA0Kc2VydmVyUHRy
LSZndDtzZXFObyk8QlI+Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7
Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7IA0KezxCUj4mbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsm
bmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJz
cDsmbmJzcDsgDQpzZXJ2ZXJQdHItJmd0O251bVBrdHNSZWN2ZCsrOzwvRk9OVD48L0RJVj4NCjxE
SVY+PEZPTlQgc2l6ZT0yPiZuYnNwOyZuYnNwOyZuYnNwOyAmbmJzcDsmbmJzcDsmbmJzcDsgJm5i
c3A7Jm5ic3A7Jm5ic3A7IA0KJm5ic3A7Jm5ic3A7Jm5ic3A7IC8vdGhlIHN0YXRpc3RpY2FsIGRh
dGEgb2YgcmVjZWl2ZWQgUGt0ICsrPC9GT05UPjwvRElWPg0KPERJVj48Rk9OVCANCnNpemU9Mj4m
bmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJz
cDsmbmJzcDsmbmJzcDt9PC9GT05UPjwvRElWPg0KPERJVj48Rk9OVCBzaXplPTI+PC9GT05UPiZu
YnNwOzwvRElWPg0KPERJVj48Rk9OVCBzaXplPTI+VGhpcyBjYXVzZXMgbXkgQXBwIGxheWVyIHJl
Y2VpdmVkIFBrdCBmcmFjdGlvbiB2ZXJ5IGJhZChhYm91dCANCjYwJSkgLGJ1dCB0aGUgTmV0d29y
ayBsYXllciBQa3QgZGVsaXZlcnkgRnJhY3Rpb24gaXMgdmVyeSBnb29kKGFib3V0IA0KOTAlKS48
L0ZPTlQ+PC9ESVY+DQo8RElWPjxGT05UIHNpemU9Mj48L0ZPTlQ+Jm5ic3A7PC9ESVY+DQo8RElW
PjxGT05UIHNpemU9Mj5NeSBzaW11bGF0aW9uIHRvb2wgaXMgDQo8U1RST05HPkdsb21vc2ltMi4w
MzwvU1RST05HPi48L0ZPTlQ+PC9ESVY+DQo8RElWPjxGT05UIHNpemU9Mj5UaGUgbnVtYmVyIG9m
IG5vZGUgaXMgNTAsJm5ic3A7Jm5ic3A7IFRFUlJBSU4tRElNRU5TSU9OUyZuYnNwOyANCigxMjAw
LCAxMjAwKSwmbmJzcDsgUkFESU8tVFgtUE9XRVImbmJzcDsyLjQ1KHJhZGlvIHJhbmdlOjUwMC40
bSk8L0ZPTlQ+PC9ESVY+DQo8RElWPjxGT05UIHNpemU9Mj5UaGUgbnVtYmVyIG9mIENiciBzb3Vy
Y2VzIGlzIDEwKGUuZy4gQ0JSJm5ic3A7IDAmbmJzcDsgMiAxODAgDQo1MTIgMVMgMFMgMFMpICwg
U2ltdWxhdGlvbiB0aW1lIGlzIDkwMHMuPC9GT05UPjwvRElWPg0KPERJVj48Rk9OVCBzaXplPTI+
PC9GT05UPiZuYnNwOzwvRElWPg0KPERJVj48Rk9OVCBzaXplPTI+V2h5IG15IHJlc3VsdCBpcyB0
aGlzID88L0ZPTlQ+PC9ESVY+DQo8RElWPjxGT05UIHNpemU9Mj48L0ZPTlQ+Jm5ic3A7PC9ESVY+
DQo8RElWPjxGT05UIHNpemU9Mj5UaGFua3MgaW4gQWR2YW5jZSEhPC9GT05UPjwvRElWPjwvQk9E
WT48L0hUTUw+DQo=

------=_NextPart_000_000C_01C2A756.84837930--

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



From manet-admin@ietf.org  Thu Dec 19 05:15: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 FAA13068
	for <manet-archive@lists.ietf.org>; Thu, 19 Dec 2002 05:15: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 gBJA5dv15076;
	Thu, 19 Dec 2002 05:05: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 gBJA1Lv14962
	for <manet@optimus.ietf.org>; Thu, 19 Dec 2002 05:01:21 -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 EAA12680
	for <manet@ietf.org>; Thu, 19 Dec 2002 04:58:06 -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 gBJA0rRZ008382;
	Thu, 19 Dec 2002 11:00:54 +0100 (MET)
Received: from eurecom.fr (chooyu.eurecom.fr [172.16.20.50])
	by monza.eurecom.fr (Postfix) with ESMTP
	id 4F04B3C3B7; Thu, 19 Dec 2002 11:01:03 +0100 (MET)
Message-ID: <3E0198DE.9050004@eurecom.fr>
Date: Thu, 19 Dec 2002 11:01:02 +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 <manet@ietf.org>, MOBICOM@acm.org
Content-Type: multipart/alternative;
 boundary="------------070103010701090603060608"
Subject: [manet] MadNet 2003:: Deadline Correction
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>


--------------070103010701090603060608
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit

Dear Colleagues,


Our apologize for the confusion about the MadNet 
<http://www.eurecom.fr/%7Enikaeinn/madnet2003/index.html> deadline, but 
we tried to re-establish our deadline in order to coordinate with the 
workshop WiOpt'03 
<http://www-sop.inria.fr/mistral/personnel/K.Avrachenkov/WiOpt/main.html> 
which be also be held in Sophia-Antipolis. For this reason our new 
deadline is January the 20th, and workshop date is March the 6th 2003.   
2003. 2003.

Hope to see in our Workshop, Navid

-------------------

MADNET 2003 (Workshop on Mobile Ad Hoc Networking and Computing) 
Organized by  RTP Reseaux- CNRS/STIC
March 6th

Institut EURECOM <http://www.eurecom.fr/>,(How to come <http://www.eurecom.fr/Discover/Howto/>) 
2229, route des cretes,
B.P. 193
06904, Sophia-Antipolis, France 


Call for Presentation and extended summary:
_____________________

 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  
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 presentation 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: January 20th, 2003 
Notification of Acceptance:  Febrery 10th, 2003 
Workshop: March 6th, 2003 


For more information, please contact our web site at:

http://www.eurecom.fr/%7Enikaeinn/madnet2003/index.html



--------------070103010701090603060608
Content-Type: text/html; charset=us-ascii
Content-Transfer-Encoding: 7bit

<html>
<head>
</head>
<body>
<p>Dear Colleagues,<br>
</p>
<font face="Times New Roman, Times, serif"><big><span lang="fr"><font size="2"><br>
<big>Our apologize for the confusion about the <a href="http://www.eurecom.fr/%7Enikaeinn/madnet2003/index.html">
MadNet </a>
deadline, but we tried to re-establish our deadline in order to coordinate
with the workshop </big><big><a href="http://www-sop.inria.fr/mistral/personnel/K.Avrachenkov/WiOpt/main.html">
WiOpt'03</a>
</big><big> which be also be held in Sophia-Antipolis. For this reason our
new deadline is January the 20th, and workshop date is March the 6th 2003.
<u>&nbsp;</u> 2003. 2003.</big></font></span></big></font>
<p><span lang="fr"><font size="2" face="Arial">Hope to see in our Workshop, 
Navid <br>
</font></span><span lang="en-us"></span><span lang="en-us"></span><span lang="fr"></span></p>
<pre wrap="">-------------------<br><br>MADNET 2003 (Workshop on Mobile Ad Hoc Networking and Computing) <br>Organized by  RTP Reseaux- CNRS/STIC<br>March 6th<br><br>Institut <a href="http://www.eurecom.fr/">EURECOM</a>,(<a href="http://www.eurecom.fr/Discover/Howto/">How to come</a>) <br>2229, route des cretes,<br>B.P. 193<br>06904, Sophia-Antipolis, France <br><br><br>Call for Presentation and extended summary:<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, c
ontent-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  <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&nbsp;presentation 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: January 20th, 2003 <br>Notification of Acceptance:&nbsp; Febrery 10th, 
2003 <br>Workshop: March 6th, 2003 <br><br><br>For more information, please&nbsp;contact our&nbsp;web site at:<br><br><a class="moz-txt-link-freetext" href="http://www.eurecom.fr/%7Enikaeinn/madnet2003/index.html">http://www.eurecom.fr/%7Enikaeinn/madnet2003/index.html</a><br><br></pre>
<p><br>
<span lang="en-us"></span></p>
</body>
</html>

--------------070103010701090603060608--

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


From manet-admin@ietf.org  Thu Dec 19 05:17: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 FAA13092
	for <manet-archive@lists.ietf.org>; Thu, 19 Dec 2002 05:17: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 gBJAK6v16238
	for <manet-archive@lists.ietf.org>; Thu, 19 Dec 2002 05:20:06 -0500
Date: Thu, 19 Dec 2002 05:20:06 -0500
Message-ID: <20021219102006.16236.68863.Mailman@www1.ietf.org>
Subject: manet@ietf.org mailing list reminder
From: manet-request@ietf.org
To: manet-archive@ietf.org
X-No-Archive: yes
X-Ack: no
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 reminder of how to unsubscribe or change your configuration
for the address "manet-archive@lists.ietf.org" on the mailing list
manet.  You need to have your password for these things.  YOUR manet
PASSWORD IS:

    FtOz

To make changes to your subscription, use the password on your options
World Wide Web page:

    https://www1.ietf.org/mailman/options/manet/manet-archive%40lists.ietf.org


You can also make such changes via email - send a message to:

    manet-request@ietf.org

with the text "help" in the subject or body, and you will be emailed
instructions.

Questions or comments?  Please send them to manet-admin@ietf.org.


From mailnull@www1.ietf.org  Thu Dec 19 05: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 FAA13378
	for <manet-archive@odin.ietf.org>; Thu, 19 Dec 2002 05:27:26 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id gBJAU9g17110
	for manet-archive@odin.ietf.org; Thu, 19 Dec 2002 05:30: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 gBJAU8v17107
	for <manet-web-archive@optimus.ietf.org>; Thu, 19 Dec 2002 05:30: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 FAA13370
	for <manet-web-archive@ietf.org>; Thu, 19 Dec 2002 05:26: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 gBJA5dv15076;
	Thu, 19 Dec 2002 05:05: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 gBJA1Lv14962
	for <manet@optimus.ietf.org>; Thu, 19 Dec 2002 05:01:21 -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 EAA12680
	for <manet@ietf.org>; Thu, 19 Dec 2002 04:58:06 -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 gBJA0rRZ008382;
	Thu, 19 Dec 2002 11:00:54 +0100 (MET)
Received: from eurecom.fr (chooyu.eurecom.fr [172.16.20.50])
	by monza.eurecom.fr (Postfix) with ESMTP
	id 4F04B3C3B7; Thu, 19 Dec 2002 11:01:03 +0100 (MET)
Message-ID: <3E0198DE.9050004@eurecom.fr>
Date: Thu, 19 Dec 2002 11:01:02 +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 <manet@ietf.org>, MOBICOM@acm.org
Content-Type: multipart/alternative;
 boundary="------------070103010701090603060608"
Subject: [manet] MadNet 2003:: Deadline Correction
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>


--------------070103010701090603060608
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit

Dear Colleagues,


Our apologize for the confusion about the MadNet 
<http://www.eurecom.fr/%7Enikaeinn/madnet2003/index.html> deadline, but 
we tried to re-establish our deadline in order to coordinate with the 
workshop WiOpt'03 
<http://www-sop.inria.fr/mistral/personnel/K.Avrachenkov/WiOpt/main.html> 
which be also be held in Sophia-Antipolis. For this reason our new 
deadline is January the 20th, and workshop date is March the 6th 2003.   
2003. 2003.

Hope to see in our Workshop, Navid

-------------------

MADNET 2003 (Workshop on Mobile Ad Hoc Networking and Computing) 
Organized by  RTP Reseaux- CNRS/STIC
March 6th

Institut EURECOM <http://www.eurecom.fr/>,(How to come <http://www.eurecom.fr/Discover/Howto/>) 
2229, route des cretes,
B.P. 193
06904, Sophia-Antipolis, France 


Call for Presentation and extended summary:
_____________________

 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  
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 presentation 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: January 20th, 2003 
Notification of Acceptance:  Febrery 10th, 2003 
Workshop: March 6th, 2003 


For more information, please contact our web site at:

http://www.eurecom.fr/%7Enikaeinn/madnet2003/index.html



--------------070103010701090603060608
Content-Type: text/html; charset=us-ascii
Content-Transfer-Encoding: 7bit

<html>
<head>
</head>
<body>
<p>Dear Colleagues,<br>
</p>
<font face="Times New Roman, Times, serif"><big><span lang="fr"><font size="2"><br>
<big>Our apologize for the confusion about the <a href="http://www.eurecom.fr/%7Enikaeinn/madnet2003/index.html">
MadNet </a>
deadline, but we tried to re-establish our deadline in order to coordinate
with the workshop </big><big><a href="http://www-sop.inria.fr/mistral/personnel/K.Avrachenkov/WiOpt/main.html">
WiOpt'03</a>
</big><big> which be also be held in Sophia-Antipolis. For this reason our
new deadline is January the 20th, and workshop date is March the 6th 2003.
<u>&nbsp;</u> 2003. 2003.</big></font></span></big></font>
<p><span lang="fr"><font size="2" face="Arial">Hope to see in our Workshop, 
Navid <br>
</font></span><span lang="en-us"></span><span lang="en-us"></span><span lang="fr"></span></p>
<pre wrap="">-------------------<br><br>MADNET 2003 (Workshop on Mobile Ad Hoc Networking and Computing) <br>Organized by  RTP Reseaux- CNRS/STIC<br>March 6th<br><br>Institut <a href="http://www.eurecom.fr/">EURECOM</a>,(<a href="http://www.eurecom.fr/Discover/Howto/">How to come</a>) <br>2229, route des cretes,<br>B.P. 193<br>06904, Sophia-Antipolis, France <br><br><br>Call for Presentation and extended summary:<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, c
ontent-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  <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&nbsp;presentation 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: January 20th, 2003 <br>Notification of Acceptance:&nbsp; Febrery 10th, 
2003 <br>Workshop: March 6th, 2003 <br><br><br>For more information, please&nbsp;contact our&nbsp;web site at:<br><br><a class="moz-txt-link-freetext" href="http://www.eurecom.fr/%7Enikaeinn/madnet2003/index.html">http://www.eurecom.fr/%7Enikaeinn/madnet2003/index.html</a><br><br></pre>
<p><br>
<span lang="en-us"></span></p>
</body>
</html>

--------------070103010701090603060608--

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



From mailnull@www1.ietf.org  Fri Dec 20 14:56: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 OAA08354
	for <manet-archive@odin.ietf.org>; Fri, 20 Dec 2002 14:56:10 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id gBKJx8h04836
	for manet-archive@odin.ietf.org; Fri, 20 Dec 2002 14:59: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 gBKJx8v04833
	for <manet-web-archive@optimus.ietf.org>; Fri, 20 Dec 2002 14:59: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 OAA08345
	for <manet-web-archive@ietf.org>; Fri, 20 Dec 2002 14:55: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 gBKJaxv03061;
	Fri, 20 Dec 2002 14:36: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 gBKJWbv02896
	for <manet@optimus.ietf.org>; Fri, 20 Dec 2002 14:32:37 -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 OAA07328
	for <manet@ietf.org>; Fri, 20 Dec 2002 14:29:08 -0500 (EST)
Received: from SRCATL-MTA by mail.scires.com
	with Novell_GroupWise; Fri, 20 Dec 2002 14:33:17 -0500
Message-Id: <se032a2d.071@mail.scires.com>
X-Mailer: Novell GroupWise Internet Agent 6.0.2 Beta
Date: Fri, 20 Dec 2002 14:33:03 -0500
From: "Pete Sholander" <psholand@scires.com>
To: <Corson@flarion.com>, <manet@ietf.org>
Cc: <haas@EE.CORNELL.EDU>
Subject: RE: [manet] WG Mtg Summary -- Comment on Consensus
Mime-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
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

Scott,

Sorry for the delayed response to your one question ...

In a military context, "application scalability" might entail maneuver
units vs. Tactical UAVs vs. unattended ground-based sensors.  In that
case, two "sizes" (a reactive component and a proactive component) and 
a *simple* way for the IETF's proactive and reactive protocols to
exchange topology information might fit a great many applications.

On the rest of your answers, we'll just "agree to disagree" and no
point in continuing those threads since your mind seems set ...

--Pete Sholander

>>> Scott Corson <Corson@flarion.com> 12/12/02 06:25PM >>>

> Several of my customers view
> hybrid-routing as providing "application scalability" rather than
> scalability in network size.  Hybrid techniques sidestep the debates
> about reactive-routing having too much initial latency for real-time
> traffic versus proactive routing problem's with LPD and energy
> efficiency.  

I'm not sure I understand what you mean by *application*.  Do you mean
wide
range of network deployment contexts for a single protocol... more
along the
lines of "one size fits all"?

The AD's intent of the rechartering is to focus the WG on the design
of
simple protocols: proactive and reactive.

I think I understand your desire and intent, but it's not congruent
with the
desired IETF WG direction.  The exploration of the techniques you
propose is
actually very much in line with the issues the IRTF group will
address.


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



From mailnull@www1.ietf.org  Fri Dec 20 19:08: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 TAA15959
	for <manet-archive@odin.ietf.org>; Fri, 20 Dec 2002 19:08:07 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id gBL0B7D19351
	for manet-archive@odin.ietf.org; Fri, 20 Dec 2002 19:11: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 gBL0B7v19348
	for <manet-web-archive@optimus.ietf.org>; Fri, 20 Dec 2002 19:11: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 TAA15956
	for <manet-web-archive@ietf.org>; Fri, 20 Dec 2002 19:07: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 gBKNxNv18286;
	Fri, 20 Dec 2002 18:59: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 gBKNvvv18262
	for <manet@optimus.ietf.org>; Fri, 20 Dec 2002 18:57:57 -0500
Received: from godel.crhc.uiuc.edu (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA15659
	for <manet@ietf.org>; Fri, 20 Dec 2002 18:54:27 -0500 (EST)
Received: from localhost (nhv@localhost)
	by godel.crhc.uiuc.edu (8.11.6/8.11.6) with ESMTP id gBKNvST14128;
	Fri, 20 Dec 2002 17:57:28 -0600
X-Authentication-Warning: godel.crhc.uiuc.edu: nhv owned process doing -bs
Date: Fri, 20 Dec 2002 17:57:28 -0600 (CST)
From: "Nitin H. Vaidya" <nhv@crhc.uiuc.edu>
To: MANET mailing list <manet@ietf.org>
cc: Nitin H Vaidya <nhv@crhc.uiuc.edu>
Message-ID: <Pine.LNX.4.33.0212201736230.14055-100000@godel.crhc.uiuc.edu>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Subject: [manet] 802.11 - minor optimization
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 all:

Anyone on the list from 802.11 standards group ?
Here is a trivial idea worth 2 cents (more like 5%) ...

A simple optimization for 802.11 that might improve
performance 5% without any real change to the protocol :

As I understand 802.11 DCF, the backoff intervals are chosen
in the range of [0,CW] and then the backoff counter is
decremented at the END of each idle slot. Transmit immediately
when counter reaches 0.

Suggested modification:

  Choose backoff interval in the range [1,cw], and decrement
  backoff counter at the START of each slot. Transmit immediately
  when counter reaches 0.

CW in 802.11 is specifed as 2^k-1 for interger k. With the above
change CW should be simply 2^k so that the range of values
for backoff remains same as 802.11 (or, to put it differently,
choose new backoff as 802.11 backoff + 1).

Unless I am mistaken, the above change can save 1 idle
slot for each transmitted packets (with some exceptions).

To see this consider the case when 4 nodes (A, B, C, D) receive
a packet from upper layers while the channel is busy. Let us say that
they choose backoff intervals 0, 1, 2, 3 with the original 802.11,
and 1, 2, 3, 4 with the new modification.

In the original 802.11:

   A will transmit DIFS + 0 slot after current transmission ends.
   B will transmit DIFS + 1 slot after A's transmission.
   C will transmit DIFS + 1 slot after B's transmission.
   D will transmit DIFS + 1 slot after C's transmission.

With the modification:

   A will transmit DIFS + 0 slot after current transmission ends.
   B will transmit DIFS + 0 slot after A's transmission.
   C will transmit DIFS + 0 slot after B's transmission.
   D will transmit DIFS + 0 slot after C's transmission.

So we save 1 slot for each of the last 3 transmissions -- in general,
1 slot may be saved whenever a non-zero backoff counter is chosen
by original 802.11 for a packet that arrives on a busy channel.

Any reason not to use the above modification to 802.11 ?
About 5 minutes of thought went into this suggestion, so if there
is a bug in my argument, feel free to point it out.

Happy holidays!

- nitin

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



From mailnull@www1.ietf.org  Fri Dec 20 19:11: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 TAA16068
	for <manet-archive@odin.ietf.org>; Fri, 20 Dec 2002 19:11:44 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id gBL0EiI19457
	for manet-archive@odin.ietf.org; Fri, 20 Dec 2002 19:14: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 gBL0Eiv19454
	for <manet-web-archive@optimus.ietf.org>; Fri, 20 Dec 2002 19:14: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 TAA16059
	for <manet-web-archive@ietf.org>; Fri, 20 Dec 2002 19:11: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 gBL06Cv18525;
	Fri, 20 Dec 2002 19: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 gBL05kv18485
	for <manet@optimus.ietf.org>; Fri, 20 Dec 2002 19:05:47 -0500
Received: from edgar1.colorado.edu (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA15782
	for <manet@ietf.org>; Fri, 20 Dec 2002 19:02:16 -0500 (EST)
Received: from colorado.edu ([128.138.189.192])
	by edgar1.colorado.edu (8.11.2/8.11.2/ITS-5.0/student) with ESMTP id gBL05D505042
	for <manet@ietf.org>; Fri, 20 Dec 2002 17:05:13 -0700 (MST)
Message-ID: <3E18C834.2060205@colorado.edu>
Date: Sun, 05 Jan 2003 17:05:08 -0700
From: Shweta Bhandare <Shweta.Bhandare@colorado.edu>
Reply-To: Shweta.Bhandare@colorado.edu
Organization: University of Colorado at Boulder
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.0.1) Gecko/20020823 Netscape/7.0
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: MANET mail list <manet@ietf.org>
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit
Subject: [manet] Click 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>
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit

Hi,

	Has anyone used Click on iPAQs? I am trying to run the Click version of 
DSR we have developed on the iPAQs.

Thanks,
	Shweta

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



From mailnull@www1.ietf.org  Fri Dec 20 19:35: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 TAA16680
	for <manet-archive@odin.ietf.org>; Fri, 20 Dec 2002 19:35:38 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id gBL0cdN21061
	for manet-archive@odin.ietf.org; Fri, 20 Dec 2002 19:38: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 gBL0cdv21058
	for <manet-web-archive@optimus.ietf.org>; Fri, 20 Dec 2002 19:38: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 TAA16670
	for <manet-web-archive@ietf.org>; Fri, 20 Dec 2002 19:35: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 gBL0IMv19644;
	Fri, 20 Dec 2002 19:18: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 gBL0HFv19560
	for <manet@optimus.ietf.org>; Fri, 20 Dec 2002 19:17:15 -0500
Received: from godel.crhc.uiuc.edu (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA16130
	for <manet@ietf.org>; Fri, 20 Dec 2002 19:13:44 -0500 (EST)
Received: from localhost (nhv@localhost)
	by godel.crhc.uiuc.edu (8.11.6/8.11.6) with ESMTP id gBL0Gjs14173;
	Fri, 20 Dec 2002 18:16:45 -0600
X-Authentication-Warning: godel.crhc.uiuc.edu: nhv owned process doing -bs
Date: Fri, 20 Dec 2002 18:16:45 -0600 (CST)
From: "Nitin H. Vaidya" <nhv@crhc.uiuc.edu>
To: MANET mailing list <manet@ietf.org>
cc: Nitin H Vaidya <nhv@crhc.uiuc.edu>
Subject: Re: [manet] 802.11 - minor optimization
In-Reply-To: <Pine.LNX.4.33.0212201736230.14055-100000@godel.crhc.uiuc.edu>
Message-ID: <Pine.LNX.4.33.0212201810160.14170-100000@godel.crhc.uiuc.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>


On Fri, 20 Dec 2002, Nitin H. Vaidya wrote:

.  >>
.  >>Hello all:
.  >>
.  >>Anyone on the list from 802.11 standards group ?
.  >>Here is a trivial idea worth 2 cents (more like 5%) ...
.  >>
.  >>A simple optimization for 802.11 that might improve
.  >>performance 5% without any real change to the protocol :
.  >>
.  >>As I understand 802.11 DCF, the backoff intervals are chosen
.  >>in the range of [0,CW] and then the backoff counter is
.  >>decremented at the END of each idle slot. Transmit immediately
.  >>when counter reaches 0.
.  >>
.  >>Suggested modification:
.  >>
.  >>  Choose backoff interval in the range [1,cw], and decrement
.  >>  backoff counter at the START of each slot. Transmit immediately
.  >>  when counter reaches 0.

I guess this is easier to understand if described a bit differently
(although equivalent to above): choose between [1,CW], and decrement at
the end of DIFS idle interval as well as at the end of each idle slot.

End of DIFS is the start of the first slot after DIFS -- this slot may 
turn out to be idle or busy, but all counters are decremeneted at the
end of DIFS before status of the slot is known. Depending on how
you look at it, later decrements occur at the end of idle slots, or start 
of next slot after an idle slot (the next slot may turn out to be
busy or idle).


.  >>CW in 802.11 is specifed as 2^k-1 for interger k. With the above
.  >>change CW should be simply 2^k so that the range of values
.  >>for backoff remains same as 802.11 (or, to put it differently,
.  >>choose new backoff as 802.11 backoff + 1).
.  >>
.  >>Unless I am mistaken, the above change can save 1 idle
.  >>slot for each transmitted packets (with some exceptions).
.  >>
.  >>To see this consider the case when 4 nodes (A, B, C, D) receive
.  >>a packet from upper layers while the channel is busy. Let us say that
.  >>they choose backoff intervals 0, 1, 2, 3 with the original 802.11,
.  >>and 1, 2, 3, 4 with the new modification.
.  >>
.  >>In the original 802.11:
.  >>
.  >>   A will transmit DIFS + 0 slot after current transmission ends.
.  >>   B will transmit DIFS + 1 slot after A's transmission.
.  >>   C will transmit DIFS + 1 slot after B's transmission.
.  >>   D will transmit DIFS + 1 slot after C's transmission.
.  >>
.  >>With the modification:
.  >>
.  >>   A will transmit DIFS + 0 slot after current transmission ends.
.  >>   B will transmit DIFS + 0 slot after A's transmission.
.  >>   C will transmit DIFS + 0 slot after B's transmission.
.  >>   D will transmit DIFS + 0 slot after C's transmission.
.  >>
.  >>So we save 1 slot for each of the last 3 transmissions -- in general,
.  >>1 slot may be saved whenever a non-zero backoff counter is chosen
.  >>by original 802.11 for a packet that arrives on a busy channel.
.  >>
.  >>Any reason not to use the above modification to 802.11 ?
.  >>About 5 minutes of thought went into this suggestion, so if there
.  >>is a bug in my argument, feel free to point it out.
.  >>
.  >>Happy holidays!
.  >>
.  >>- nitin
.  >>
.  >>_______________________________________________
.  >>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  Sat Dec 21 05:51: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 FAA04774
	for <manet-archive@odin.ietf.org>; Sat, 21 Dec 2002 05:51:50 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id gBLAsvd23972
	for manet-archive@odin.ietf.org; Sat, 21 Dec 2002 05:54: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 gBLAsvv23969
	for <manet-web-archive@optimus.ietf.org>; Sat, 21 Dec 2002 05:54: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 FAA04771
	for <manet-web-archive@ietf.org>; Sat, 21 Dec 2002 05:51: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 gBLAkRv23837;
	Sat, 21 Dec 2002 05:46: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 gBLAgKv23766
	for <manet@optimus.ietf.org>; Sat, 21 Dec 2002 05:42:20 -0500
Received: from webmails.com (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id FAA04694
	for <manet@ietf.org>; Sat, 21 Dec 2002 05:38:39 -0500 (EST)
Received: (qmail 18480 invoked by uid 511); 21 Dec 2002 10:42:05 -0000
Message-ID: <20021221104205.18479.qmail@webmails.com>
Content-Type: multipart/alternative; boundary="----------=_1040467325-17791-0"
Content-Transfer-Encoding: binary
MIME-Version: 1.0
X-Mailer: MIME-tools 5.411 (Entity 5.404)
From: "moez gadri" <moez_gadri@webmails.com>
To: manet@ietf.org
Organization: WebMailS - http://www.webmails.com
Date: Sat, 21 Dec 2002 11:42:5 +0100
X-Originating-Ip: 193.95.33.25
Subject: [manet] 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>

This is a multi-part message in MIME format...

------------=_1040467325-17791-0
Content-Type: text/plain
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable

Hi,=0D
=0D
There's a non comertial simulator for MANET?=0D


____________________________________________________________________
- http://www.WebMailSPro.com - >>=20
Cr=E9er votre WebBased email pour avec votre propre nom de domaine=20


------------=_1040467325-17791-0
Content-Type: text/html
Content-Disposition: inline
Content-Transfer-Encoding: 7bit

<HTML>
<BODY BGCOLOR="FFFFFF">
<PRE>Hi,

There's a non comertial simulator for MANET?


____________________________________________________________________
- <TT><A HREF="http://www.WebMailSPro.com">http://www.WebMailSPro.com</A></TT> - &gt;&gt; 
Créer votre WebBased email pour avec votre propre nom de domaine </PRE>

</BODY>
</HTML>
------------=_1040467325-17791-0--
_______________________________________________
manet mailing list
manet@ietf.org
https://www1.ietf.org/mailman/listinfo/manet



From mailnull@www1.ietf.org  Mon Dec 23 16:40: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 QAA15921
	for <manet-archive@odin.ietf.org>; Mon, 23 Dec 2002 16:40:23 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id gBNLhwI05488
	for manet-archive@odin.ietf.org; Mon, 23 Dec 2002 16:43: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 gBNLhwv05485
	for <manet-web-archive@optimus.ietf.org>; Mon, 23 Dec 2002 16:43: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 QAA15908
	for <manet-web-archive@ietf.org>; Mon, 23 Dec 2002 16:39: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 gBNLQxv04208;
	Mon, 23 Dec 2002 16:26: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 gBNLIqv04057
	for <manet@optimus.ietf.org>; Mon, 23 Dec 2002 16:18:52 -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 QAA15362
	for <manet@ietf.org>; Mon, 23 Dec 2002 16:14:46 -0500 (EST)
Received: from zidane.cc.vt.edu (IDENT:mirapoint@zidane-lb.cc.vt.edu [10.1.1.13])
	by lennier.cc.vt.edu (8.11.4/8.11.4) with ESMTP id gBNLHnH55815
	for <manet@ietf.org>; Mon, 23 Dec 2002 16:17:49 -0500 (EST)
Received: from ecpe15 (ari426-c.ari.vt.edu [208.17.194.116])
	by zidane.cc.vt.edu (Mirapoint Messaging Server MOS 3.2.2-GA)
	with ESMTP id AWK06774;
	Mon, 23 Dec 2002 16:17:48 -0500 (EST)
Message-ID: <001101c2aac8$b23dc950$030200c0@ecpe15>
From: "Vikram Dham" <vdham@vt.edu>
To: <manet@ietf.org>
References: <20021221104205.18479.qmail@webmails.com>
Date: Mon, 23 Dec 2002 16:17:27 -0500
MIME-Version: 1.0
Content-Type: multipart/alternative;
	boundary="----=_NextPart_000_000E_01C2AA9E.C9493CD0"
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 5.50.4920.2300
X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4920.2300
Subject: [manet] DSR model in opnet
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_000E_01C2AA9E.C9493CD0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

Hi,

Has anyone used any DSR model successfully for simulations in OPNET ?=20

Vikram
  ----- Original Message -----=20
  From: moez gadri=20
  To: manet@ietf.org=20
  Sent: Saturday, December 21, 2002 5:42 AM
  Subject: [manet] simulator


Hi,

There's a non comertial simulator for MANET?


____________________________________________________________________
- http://www.WebMailSPro.com - >>=20
Cr=E9er votre WebBased email pour avec votre propre nom de domaine 
------=_NextPart_000_000E_01C2AA9E.C9493CD0
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 5.50.4922.900" name=3DGENERATOR>
<STYLE></STYLE>
</HEAD>
<BODY bgColor=3D#ffffff>
<DIV><FONT face=3DArial size=3D2>Hi,</FONT></DIV>
<DIV><FONT face=3DArial size=3D2></FONT>&nbsp;</DIV>
<DIV><FONT face=3DArial size=3D2>Has anyone used any DSR model =
successfully for=20
simulations in OPNET ? </FONT></DIV>
<DIV><FONT face=3DArial size=3D2></FONT>&nbsp;</DIV>
<DIV><FONT face=3DArial size=3D2>Vikram</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=3Dmoez_gadri@webmails.com =
href=3D"mailto:moez_gadri@webmails.com">moez=20
  gadri</A> </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> Saturday, December 21, =
2002 5:42=20
  AM</DIV>
  <DIV style=3D"FONT: 10pt arial"><B>Subject:</B> [manet] =
simulator</DIV>
  <DIV><BR></DIV><PRE>Hi,

There's a non comertial simulator for MANET?


____________________________________________________________________
- <TT><A =
href=3D"http://www.WebMailSPro.com">http://www.WebMailSPro.com</A></TT> =
- &gt;&gt;=20
Cr=E9er votre WebBased email pour avec votre propre nom de domaine =
</PRE></BLOCKQUOTE></BODY></HTML>

------=_NextPart_000_000E_01C2AA9E.C9493CD0--

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



From mailnull@www1.ietf.org  Mon Dec 23 21:49: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 VAA20281
	for <manet-archive@odin.ietf.org>; Mon, 23 Dec 2002 21:49:35 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id gBO2rF713216
	for manet-archive@odin.ietf.org; Mon, 23 Dec 2002 21:53: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 gBO2rFJ13213
	for <manet-web-archive@optimus.ietf.org>; Mon, 23 Dec 2002 21:53: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 VAA20272
	for <manet-web-archive@ietf.org>; Mon, 23 Dec 2002 21:49:04 -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 gBO1RtJ08660;
	Mon, 23 Dec 2002 20:27: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 gBO1MvJ08576
	for <manet@optimus.ietf.org>; Mon, 23 Dec 2002 20:22:57 -0500
Received: from sina.com (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id UAA18619
	for <manet@ietf.org>; Mon, 23 Dec 2002 20:18:39 -0500 (EST)
Received: (qmail 50622 invoked from network); 24 Dec 2002 01:12:22 -0000
Received: from unknown (HELO RavProxy) (218.2.149.92)
  by 202.106.187.156 with SMTP; 24 Dec 2002 01:12:22 -0000
Message-ID: <001001c2aaea$9ff75190$0e00a8c0@yuxiaowan>
From: "YUWEIBO" <feiyipuhuo2000@sina.com>
To: <manet@ietf.org>
Date: Tue, 24 Dec 2002 09:20:19 +0800
MIME-Version: 1.0
Content-Type: multipart/alternative;
	boundary="----=_NextPart_000_000D_01C2AB2D.ADEFB100"
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] transport voice in a narrow bandwidth envirment
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_01C2AB2D.ADEFB100
Content-Type: text/plain;
	charset="gb2312"
Content-Transfer-Encoding: base64

SGVsbG8sDQpEb2VzIGFueW9uZSBjYW4gZ2l2ZSBtZSBzb21lIGFkdmljZXMgYWJvdXQgdHJhbnNw
b3J0aW5nIGRhdGEgYW5kIHZvaWNlICBpbiBhIGxvdyBzcGVlZCBhZCBob2MgbmV0d29ya3M/IA0K
YW55IGhlbHAgd2lsbCBiZSBhcHByZWNpYXRlZA0KYmVzdCByZWdhcmRzIA0K

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

PCFET0NUWVBFIEhUTUwgUFVCTElDICItLy9XM0MvL0RURCBIVE1MIDQuMCBUcmFuc2l0aW9uYWwv
L0VOIj4NCjxIVE1MPjxIRUFEPg0KPE1FVEEgaHR0cC1lcXVpdj1Db250ZW50LVR5cGUgY29udGVu
dD0idGV4dC9odG1sOyBjaGFyc2V0PWdiMjMxMiI+DQo8TUVUQSBjb250ZW50PSJNU0hUTUwgNi4w
MC4yNjAwLjAiIG5hbWU9R0VORVJBVE9SPg0KPFNUWUxFPjwvU1RZTEU+DQo8L0hFQUQ+DQo8Qk9E
WSBiZ0NvbG9yPSNmZmZmZmY+DQo8RElWPg0KPERJVj48Rk9OVCBzaXplPTI+SGVsbG8sPC9GT05U
PjwvRElWPg0KPERJVj48Rk9OVCBzaXplPTI+RG9lcyBhbnlvbmUgY2FuIGdpdmUgbWUgc29tZSBh
ZHZpY2VzIGFib3V0IHRyYW5zcG9ydGluZyBkYXRhIA0KYW5kIHZvaWNlJm5ic3A7Jm5ic3A7aW4g
YSBsb3cgc3BlZWQgYWQgaG9jIG5ldHdvcmtzPyA8L0ZPTlQ+PC9ESVY+DQo8RElWPjxGT05UIHNp
emU9Mj48Rk9OVCBzaXplPTM+YW55IGhlbHAgd2lsbCBiZSBhcHByZWNpYXRlZDwvRk9OVD48L0ZP
TlQ+PC9ESVY+DQo8RElWPjxGT05UIHNpemU9Mj48Rk9OVCBzaXplPTM+YmVzdCANCnJlZ2FyZHM8
L0ZPTlQ+Jm5ic3A7PC9GT05UPjwvRElWPjwvRElWPjwvQk9EWT48L0hUTUw+DQo=

------=_NextPart_000_000D_01C2AB2D.ADEFB100--


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



From mailnull@www1.ietf.org  Tue Dec 24 04:00: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 EAA04379
	for <manet-archive@odin.ietf.org>; Tue, 24 Dec 2002 04:00:18 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id gBO946P07385
	for manet-archive@odin.ietf.org; Tue, 24 Dec 2002 04: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 gBO946J07382
	for <manet-web-archive@optimus.ietf.org>; Tue, 24 Dec 2002 04: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 DAA04346
	for <manet-web-archive@ietf.org>; Tue, 24 Dec 2002 03:59: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 gBO8taJ06810;
	Tue, 24 Dec 2002 03:55: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 gBO8rMJ06754
	for <manet@optimus.ietf.org>; Tue, 24 Dec 2002 03:53:22 -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 DAA04195
	for <manet@ietf.org>; Tue, 24 Dec 2002 03:49:02 -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 E961918AEC
	for <manet@ietf.org>; Tue, 24 Dec 2002 17:51:54 +0900 (JST)
Received: from acr.acr.atr.co.jp (localhost [127.0.0.1])
	by vcms.atr.co.jp (Postfix) with ESMTP id 88B2C397D9
	for <manet@ietf.org>; Tue, 24 Dec 2002 17:51:54 +0900 (JST)
Received: from rpc41 (rpc41 [133.186.57.59])
	by acr.acr.atr.co.jp (Postfix) with SMTP id 17A5B3D40AF
	for <manet@ietf.org>; Tue, 24 Dec 2002 17:51:55 +0900 (JST)
From: "Shingo HORISAWA" <horisawa@atr.co.jp>
To: "MANET Mailing List" <manet@ietf.org>
Date: Tue, 24 Dec 2002 17:52:32 +0900
Message-ID: <HEEGKKKPEHOBJFHFEPAPKEPBCNAA.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.6604 (9.0.2911.0)
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1106
Importance: Normal
Content-Transfer-Encoding: 7bit
Subject: [manet] GSR/FSR for Linux v0.3.1 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: 7bit
Content-Transfer-Encoding: 7bit

Hi, all.

GSR/FSR implementation for Linux version 0.3.1 is now available.
You can download it form here:
http://www.acr.atr.co.jp/~horisawa/download/gsrfsr.html

The changes from version 0.3.0 are as follows:

- show table names when they are displayed
- change program to be able to specify update-interval
- show informations to standard output after started

Please feel free to contact me if you have any questions or demands.

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  Thu Dec 26 13:07: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 NAA13608
	for <manet-archive@odin.ietf.org>; Thu, 26 Dec 2002 13:07:25 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id gBQICMq06171
	for manet-archive@odin.ietf.org; Thu, 26 Dec 2002 13:12: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 gBQICMJ06168
	for <manet-web-archive@optimus.ietf.org>; Thu, 26 Dec 2002 13:12: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 NAA13594
	for <manet-web-archive@ietf.org>; Thu, 26 Dec 2002 13:06: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 gBQHuMJ05015;
	Thu, 26 Dec 2002 12:56: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 gBQHm6J04871
	for <manet@optimus.ietf.org>; Thu, 26 Dec 2002 12:48:06 -0500
Received: from mail-shield2.njit.edu (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA13208
	for <manet@ietf.org>; Thu, 26 Dec 2002 12:42:38 -0500 (EST)
Received: (from uucp@localhost)
	by mail-shield2.njit.edu (8.11.6/8.11.6) id gBQHjgM22120
	for <manet@ietf.org>; Thu, 26 Dec 2002 12:45:42 -0500 (EST)
Received: from nodnsquery(128.235.251.173) by mail-shield2.njit.edu via csmap (V4.1)
	id srcAAAOiaimR; Thu, 26 Dec 02 12:45:42 -0500
Received: from alizarin.njit.edu (alizarin.njit.edu [128.235.204.81])
	by mail-gw5.njit.edu (8.12.4/8.12.4) with ESMTP id gBQHjflZ025168
	for <manet@ietf.org>; Thu, 26 Dec 2002 12:45:42 -0500 (EST)
Received: from localhost (io2@localhost)
	by alizarin.njit.edu (8.10.2+Sun/8.8.5) with ESMTP id gBQHjgh14326
	for <manet@ietf.org>; Thu, 26 Dec 2002 12:45:42 -0500 (EST)
Date: Thu, 26 Dec 2002 12:45:42 -0500 (EST)
From: ilker onat <io2@oak.njit.edu>
To: manet@ietf.org
Message-ID: <Pine.GSO.4.44.0212261239150.11889-100000@alizarin.njit.edu>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Subject: [manet] ifqueue in AODV
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 couldn't fully grasp the ifqueue useage of AODV. Can anybody explain?
I pasted a previously asked-answered-re-asked question below. Does AODV
use the ifqueue or it is just using the rqueue?

Best,

Ilker



tcp wrote:

> Hi,

what do you mean with "not used"?? is agent->ifqueue empty?? But it's
used in recvReply as well as in AODV::rt_ll_failed to drop the packets
in the interface queue, that also could not be forwarded!!!! Does it
have any effect now, since ifqueue is empty??
while((p = ifqueue->filter(broken_nbr))) {
     drop(p, DROP_RTR_MAC_CALLBACK);
    }
Can omebody clarify it. This is a little confusing.
Thanks
Riadh


> Hi, Weihua,
>
> "agent->ifqueue" is defined but not used.
> The actual interface queue being used is:
> "agent->target_->downtarget_"
> (if trace between "Agent" and "LL" is disabled), or
> "agent->target_->downtarget_->downtarget_".
>
> You can find these details in ns-mobilenode.tcl.
> Hope it helps!
>
> Alan
>
> > Date: Sat, 26 Oct 2002 17:48:25 +0800
> > From: "yang weihua" <yangwh00@mails.tsinghua.edu.cn>
> > To: "manet@ietf.org" <manet@ietf.org>
> > Subject: [manet] About ifqueue length
> >
> > everyone??
> >       Does anybody know how to get the ifqueue(between MAC and LL)
> > length from the route agent? I have attempted to get the value
> > by doing this in the AODV C++ source code:
> >    queue_len=agent->ifqueue->getLen();
> > where agent is the aodv route agent. But to my disappointment,
> > the result always remained to be zero! what's the problem?
> >    Appreciate your any help!
> >
> >
> >

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



From mailnull@www1.ietf.org  Fri Dec 27 07:22: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 HAA06674
	for <manet-archive@odin.ietf.org>; Fri, 27 Dec 2002 07:22:31 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id gBRCRpB01330
	for manet-archive@odin.ietf.org; Fri, 27 Dec 2002 07:27: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 gBRCRoJ01325
	for <manet-web-archive@optimus.ietf.org>; Fri, 27 Dec 2002 07:27: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 HAA06668
	for <manet-web-archive@ietf.org>; Fri, 27 Dec 2002 07:21: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 gBRCJBJ00987;
	Fri, 27 Dec 2002 07:19: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 gBRCETJ00912
	for <manet@optimus.ietf.org>; Fri, 27 Dec 2002 07:14:29 -0500
Received: from helka.iif.hu (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id HAA06530
	for <manet@ietf.org>; Fri, 27 Dec 2002 07:08:38 -0500 (EST)
Received: from CONVERSION-DAEMON.helka.iif.hu by helka.iif.hu
 (PMDF V6.0-24 #47461) id <0H7S00H011VG6F@helka.iif.hu> for manet@ietf.org;
 Fri, 27 Dec 2002 13:11:40 +0100 (MET)
Received: from helka.iif.hu (athos.iif.hu [193.225.12.69])
 by helka.iif.hu (PMDF V6.0-24 #47461)
 with ESMTP id <0H7S00DC11VGO1@helka.iif.hu>; Fri,
 27 Dec 2002 13:11:40 +0100 (MET)
Received: from localhost (svincze@localhost)	by helka.iif.hu (8.9.3/8.9.3)
 with ESMTP id MAA22258; Fri, 27 Dec 2002 12:11:40 +0000 (GMT)
Date: Fri, 27 Dec 2002 13:11:39 +0100 (MET)
From: Sandor Vincze <h12853vin@helka.iif.hu>
In-reply-to: <001001c2aaea$9ff75190$0e00a8c0@yuxiaowan>
To: YUWEIBO <feiyipuhuo2000@sina.com>
Cc: manet@ietf.org
Message-id: <Pine.SV4.4.21.0212271310340.131-100000@helka.iif.hu>
MIME-version: 1.0
Content-type: TEXT/PLAIN; charset=US-ASCII
Subject: [manet] unsubscribe request
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>



How to unsubscribe from MANET?


On Tue, 24 Dec 2002, YUWEIBO wrote:

> Hello,
> Does anyone can give me some advices about transporting data and voice  in a low speed ad hoc networks? 
> any help will be appreciated
> best regards 
> 

-- 


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



From mailnull@www1.ietf.org  Sun Dec 29 08:08: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 IAA27755
	for <manet-archive@odin.ietf.org>; Sun, 29 Dec 2002 08:08:25 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id gBTDEi321265
	for manet-archive@odin.ietf.org; Sun, 29 Dec 2002 08:14: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 gBTDEiJ21262
	for <manet-web-archive@optimus.ietf.org>; Sun, 29 Dec 2002 08:14: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 IAA27752
	for <manet-web-archive@ietf.org>; Sun, 29 Dec 2002 08:07: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 gBTCvpJ20145;
	Sun, 29 Dec 2002 07:57: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 gBTCdCJ19796
	for <manet@optimus.ietf.org>; Sun, 29 Dec 2002 07:39:12 -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 HAA27392
	for <manet@ietf.org>; Sun, 29 Dec 2002 07:32:23 -0500 (EST)
Received: from mail pickup service by hotmail.com with Microsoft SMTPSVC;
	 Sun, 29 Dec 2002 04:33:13 -0800
Received: from 129.217.129.134 by pv1fd.pav1.hotmail.msn.com with HTTP;
	Sun, 29 Dec 2002 12:33:13 GMT
X-Originating-IP: [129.217.129.134]
From: "ayman ghazi" <aymanghazi10@hotmail.com>
To: manet@ietf.org
Date: Sun, 29 Dec 2002 12:33:13 +0000
Mime-Version: 1.0
Content-Type: text/html
Message-ID: <F104qDm90yuberLPQNy0000bc73@hotmail.com>
X-OriginalArrivalTime: 29 Dec 2002 12:33:13.0693 (UTC) FILETIME=[747848D0:01C2AF36]
Subject: [manet] General questions
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>

<html><div style='background-color:'><DIV>hello, </DIV>
<DIV>I have two questions please: </DIV>
<DIV>First one is; most of the performance evaluation studying on manet routing protocol, it used what called Pauset Time, I know it indicate to the mobility of the node in the ad hoc network, but what is Pause time meaning and how we can use it to indicate of the node mobility ?</DIV>
<DIV>second question is, all Manet Protocol it used for assumption that all nodes are moving (highly dynamic, or medium dynamic), but we have some kind of network where most node are moving( hihgly dynamic), but some nodes are eaither semi fixed or fixed (&nbsp; like WaveLAN with some fix Access points and many mobile nodes), so are there any protocols for this condition.</DIV>
<DIV>&nbsp;</DIV>
<DIV>thanks </DIV>
<DIV>Ayman </DIV></div><br clear=all><hr>Protect your PC - <a href="http://g.msn.com/8HMGEN/2024">Click here</a> for McAfee.com VirusScan Online </html>
_______________________________________________
manet mailing list
manet@ietf.org
https://www1.ietf.org/mailman/listinfo/manet



From mailnull@www1.ietf.org  Tue Dec 31 14:44: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 OAA28227
	for <manet-archive@odin.ietf.org>; Tue, 31 Dec 2002 14:44:21 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id gBVJpkE08473
	for manet-archive@odin.ietf.org; Tue, 31 Dec 2002 14:51: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 gBVJpkJ08470
	for <manet-web-archive@optimus.ietf.org>; Tue, 31 Dec 2002 14:51: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 OAA28221
	for <manet-web-archive@ietf.org>; Tue, 31 Dec 2002 14:43: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 gBVJSDJ07007;
	Tue, 31 Dec 2002 14:28: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 gBVJHCJ06779
	for <manet@optimus.ietf.org>; Tue, 31 Dec 2002 14:17:12 -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 OAA27676
	for <manet@ietf.org>; Tue, 31 Dec 2002 14:09:10 -0500 (EST)
Received:  from qifan (EE189.eee.kcl.ac.uk [137.73.11.245])
	by angelo.kcl.ac.uk  with SMTP id gBVJBlTB005846;
	Tue, 31 Dec 2002 19:11:47 GMT
Message-ID: <01ab01c2b100$7e3739a0$f50b4989@qifan>
From: "Qi Fan" <qi.fan@kcl.ac.uk>
To: "ayman ghazi" <aymanghazi10@hotmail.com>, <manet@ietf.org>
References: <F104qDm90yuberLPQNy0000bc73@hotmail.com>
Subject: Re: [manet] General questions
Date: Tue, 31 Dec 2002 19:11:59 -0000
MIME-Version: 1.0
Content-Type: multipart/alternative;
	boundary="----=_NextPart_000_01A8_01C2B100.7E0A0F20"
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
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_01A8_01C2B100.7E0A0F20
Content-Type: text/plain;
	charset="gb2312"
Content-Transfer-Encoding: quoted-printable

The pause time is used to describe the the interval between the =
movement.

If pause time is come up to infinitude that is means, mobile node is =
fixed, while pause time equals to 0, that means this mobile node is =
always move. By this way you will get the highly dynamic, or medium =
dynamic and fixed nodes.

Warm regards, and have a nice day!

------------------------------------
Qi Fan
=20

  ----- Original Message -----=20
  From: ayman ghazi=20
  To: manet@ietf.org=20
  Sent: Sunday, December 29, 2002 12:33 PM
  Subject: [manet] General questions


  hello,=20
  I have two questions please:=20
  First one is; most of the performance evaluation studying on manet =
routing protocol, it used what called Pauset Time, I know it indicate to =
the mobility of the node in the ad hoc network, but what is Pause time =
meaning and how we can use it to indicate of the node mobility ?
  second question is, all Manet Protocol it used for assumption that all =
nodes are moving (highly dynamic, or medium dynamic), but we have some =
kind of network where most node are moving( hihgly dynamic), but some =
nodes are eaither semi fixed or fixed (  like WaveLAN with some fix =
Access points and many mobile nodes), so are there any protocols for =
this condition.

  thanks=20
  Ayman=20


-------------------------------------------------------------------------=
-----
  Protect your PC - Click here for McAfee.com VirusScan Online =
_______________________________________________ manet mailing list =
manet@ietf.org https://www1.ietf.org/mailman/listinfo/manet=20

------=_NextPart_000_01A8_01C2B100.7E0A0F20
Content-Type: text/html;
	charset="gb2312"
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=3Dgb2312">
<META content=3D"MSHTML 6.00.2600.0" name=3DGENERATOR>
<STYLE></STYLE>
</HEAD>
<BODY bgColor=3D#ffffff>
<DIV><FONT face=3DArial size=3D2>The pause time is used to describe the =
the interval=20
between the movement.</FONT></DIV>
<DIV><FONT face=3DArial size=3D2></FONT>&nbsp;</DIV>
<DIV><FONT face=3DArial size=3D2>If pause time is come up to infinitude =
that is=20
means, mobile node is fixed, while pause time equals to 0, that means =
this=20
mobile node is always move. By this way you will get the <FONT =
size=3D3>highly=20
dynamic, or medium dynamic and fixed nodes.</FONT></FONT></DIV>
<DIV><FONT face=3DArial size=3D2></FONT>&nbsp;</DIV>
<DIV>Warm regards, and have a nice=20
day!<BR><BR>------------------------------------<BR>Qi =
Fan<BR>&nbsp;<BR></DIV>
<BLOCKQUOTE=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=3Daymanghazi10@hotmail.com =
href=3D"mailto:aymanghazi10@hotmail.com">ayman=20
  ghazi</A> </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> Sunday, December 29, 2002 =
12:33=20
  PM</DIV>
  <DIV style=3D"FONT: 10pt arial"><B>Subject:</B> [manet] General =
questions</DIV>
  <DIV><BR></DIV>
  <DIV>
  <DIV>hello, </DIV>
  <DIV>I have two questions please: </DIV>
  <DIV>First one is; most of the performance evaluation studying on =
manet=20
  routing protocol, it used what called Pauset Time, I know it indicate =
to the=20
  mobility of the node in the ad hoc network, but what is Pause time =
meaning and=20
  how we can use it to indicate of the node mobility ?</DIV>
  <DIV>second question is, all Manet Protocol it used for assumption =
that all=20
  nodes are moving (highly dynamic, or medium dynamic), but we have some =
kind of=20
  network where most node are moving( hihgly dynamic), but some nodes =
are=20
  eaither semi fixed or fixed (&nbsp; like WaveLAN with some fix Access =
points=20
  and many mobile nodes), so are there any protocols for this =
condition.</DIV>
  <DIV>&nbsp;</DIV>
  <DIV>thanks </DIV>
  <DIV>Ayman </DIV></DIV><BR clear=3Dall>
  <HR>
  Protect your PC - <A href=3D"http://g.msn.com/8HMGEN/2024">Click =
here</A> for=20
  McAfee.com VirusScan Online =
_______________________________________________=20
  manet mailing list manet@ietf.org =
https://www1.ietf.org/mailman/listinfo/manet=20
</BLOCKQUOTE></BODY></HTML>

------=_NextPart_000_01A8_01C2B100.7E0A0F20--

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



