
From madullay81@yahoo.com  Wed May 13 18:18:14 2009
Return-Path: <madullay81@yahoo.com>
X-Original-To: routing-discussion@core3.amsl.com
Delivered-To: routing-discussion@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 259D53A69B5 for <routing-discussion@core3.amsl.com>; Wed, 13 May 2009 18:18:14 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.184
X-Spam-Level: 
X-Spam-Status: No, score=-0.184 tagged_above=-999 required=5 tests=[BAYES_40=-0.185, HTML_MESSAGE=0.001]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id yPKQUdvd5J9B for <routing-discussion@core3.amsl.com>; Wed, 13 May 2009 18:18:13 -0700 (PDT)
Received: from web46003.mail.sp1.yahoo.com (web46003.mail.sp1.yahoo.com [68.180.199.96]) by core3.amsl.com (Postfix) with SMTP id 6A3C13A6949 for <routing-discussion@ietf.org>; Wed, 13 May 2009 18:18:13 -0700 (PDT)
Received: (qmail 29196 invoked by uid 60001); 14 May 2009 01:19:43 -0000
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=yahoo.com; s=s1024; t=1242263983; bh=wTUVchMnsq9jMGMDgTvVE4R2Fs1WP1/KmK0LgKRTbkc=; h=Message-ID:X-YMail-OSG:Received:X-Mailer:Date:From:Subject:To:MIME-Version:Content-Type; b=mUaf7EOFgDdoKjuYYLzrihQga0nxNkHuOD8GJbJaWMeBohjjajtRUGx+bESTwBpclzvL0kEG9O1MZPnNnL8NRTkLzPqJkD6A+3PxaCKf7M9GoVmNNEwpKb8bTj76+nB08eHLAJGbZPozvNEbOEDUtxf1cDLteDXDdroiioTUAvM=
DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=s1024; d=yahoo.com; h=Message-ID:X-YMail-OSG:Received:X-Mailer:Date:From:Subject:To:MIME-Version:Content-Type; b=QrbqI0S2HUrMjT99rMX3o0zn5Z0H1q+r0jPJf36ljslquwI4CALny/Mr65JbjBoWG4b/1df5aQTwuhG+xNJAs1pI1DqknGOaGSgvZwiKBhGb1wUcYXdLe/aXd7Xkq0XJEW7ntY4P0kHE7BAH6hQwvkDWXVHDq5HsHxBIp2IJIdQ=;
Message-ID: <463268.29140.qm@web46003.mail.sp1.yahoo.com>
X-YMail-OSG: tXh6Ay0VM1mmrj24oIIHaUjhn_65m67IlsUGM4e6ZZQNraGd0LfmjK2bkQoT1UmV3pSuzFDApWsXUzbgh3Ba0E_xiLAF3knFV.m.DKbFr14eMQ7AQh58i1UOh54pejglCMGVkFsj9lEnA12GEcD1Ci1ZzhFb_Zf1BXdhzXGInW7IxWww_2.0dyht8RiL2XStNG0j5jQCuhXKgfeiMwrZMAS9RCl7wYMCLiePgvR2dkeJcjxS5SJwje0pRzm0NEF5XOIkSfpGqPRmx1d1Ow--
Received: from [193.11.186.31] by web46003.mail.sp1.yahoo.com via HTTP; Wed, 13 May 2009 18:19:43 PDT
X-Mailer: YahooMailClassic/5.3.9 YahooMailWebService/0.7.289.10
Date: Wed, 13 May 2009 18:19:43 -0700 (PDT)
From: Muhammad <madullay81@yahoo.com>
Subject: Help
To: routing-discussion@ietf.org
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="0-33709969-1242263983=:29140"
X-BeenThere: routing-discussion@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Routing Area General mailing list <routing-discussion.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/routing-discussion>,  <mailto:routing-discussion-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/routing-discussion>
List-Post: <mailto:routing-discussion@ietf.org>
List-Help: <mailto:routing-discussion-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/routing-discussion>, <mailto:routing-discussion-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 14 May 2009 01:22:01 -0000

--0-33709969-1242263983=:29140
Content-Type: text/plain; charset=iso-8859-1
Content-Transfer-Encoding: quoted-printable

Hi All there,

I am a master student and doing my thesis. I want to evaluate routing proto=
cols performance in WSN using OpNET. I found 5 MANET routing protocols in O=
pNET which are also used in WSN but the problem is, I came to know that to =
implement these protocols, I have to use normal WLAN or MANET technology in=
 my project so that these protocols can be implemented. But I want to use s=
ensor nodes not MANET nodes. then I tried to use ZigBee, WPAN nodes but sam=
e problem there, I cant see any protocol's implementation option for these =
nodes (technologies), which is not supported by OpNET (maybe).

Now, I want to know, can I use MANET nodes as Sensor nodes (on suppositon b=
asis, if allowed/ acceptable) although they have alot of differences. Secon=
dly, is there any way if I could use the same routing (MANET) or any routin=
g protocol using WPAN nodes=A0 or ZigBee nodes using OpNET. Please guide me=
 and suggest me a proper solution. Your earliest response will be highly ap=
preciated.

Kind Regards

AMM@@@R

=0A=0A=0A      
--0-33709969-1242263983=:29140
Content-Type: text/html; charset=iso-8859-1
Content-Transfer-Encoding: quoted-printable

<table cellspacing=3D"0" cellpadding=3D"0" border=3D"0" ><tr><td valign=3D"=
top" style=3D"font: inherit;"><font size=3D"3"><span style=3D"color: rgb(67=
, 67, 67); font-family: bookman old style,new york,times,serif;">Hi All the=
re,</span><br style=3D"color: rgb(67, 67, 67); font-family: bookman old sty=
le,new york,times,serif;"><br style=3D"color: rgb(67, 67, 67); font-family:=
 bookman old style,new york,times,serif;"><span style=3D"color: rgb(67, 67,=
 67); font-family: bookman old style,new york,times,serif;">I am a master s=
tudent and doing my thesis. I want to evaluate routing protocols performanc=
e in WSN using OpNET. I found 5 MANET routing protocols in OpNET which are =
also used in WSN but the problem is, I came to know that to implement these=
 protocols, I have to use normal WLAN or MANET technology in my project so =
that these protocols can be implemented. But I want to use sensor nodes not=
 MANET nodes. then I tried to use ZigBee, WPAN nodes but same problem there=
, I cant see
 any protocol's implementation option for these nodes (technologies), which=
 is not supported by OpNET (maybe).</span><br style=3D"color: rgb(67, 67, 6=
7); font-family: bookman old style,new york,times,serif;"><br style=3D"colo=
r: rgb(67, 67, 67); font-family: bookman old style,new york,times,serif;"><=
span style=3D"color: rgb(67, 67, 67); font-family: bookman old style,new yo=
rk,times,serif;">Now, I want to know, can I use MANET nodes as Sensor nodes=
 (on suppositon basis, if allowed/ acceptable) although they have alot of d=
ifferences. Secondly, is there any way if I could use the same routing (MAN=
ET) or any routing protocol using WPAN nodes&nbsp; or ZigBee nodes using Op=
NET. Please guide me and suggest me a proper solution. Your earliest respon=
se will be highly appreciated.</span></font><br><br>Kind Regards<br><br>AMM=
@@@R<br><br></td></tr></table><br>=0A=0A      
--0-33709969-1242263983=:29140--

From adrian@olddog.co.uk  Tue May 19 06:52:22 2009
Return-Path: <adrian@olddog.co.uk>
X-Original-To: routing-discussion@core3.amsl.com
Delivered-To: routing-discussion@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 3726E3A6E9F for <routing-discussion@core3.amsl.com>; Tue, 19 May 2009 06:52:22 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.125
X-Spam-Level: 
X-Spam-Status: No, score=-2.125 tagged_above=-999 required=5 tests=[AWL=0.473,  BAYES_00=-2.599, STOX_REPLY_TYPE=0.001]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id llGXs8SDDito for <routing-discussion@core3.amsl.com>; Tue, 19 May 2009 06:52:21 -0700 (PDT)
Received: from asmtp1.iomartmail.com (asmtp1.iomartmail.com [62.128.201.248]) by core3.amsl.com (Postfix) with ESMTP id 2713E3A6E66 for <routing-discussion@ietf.org>; Tue, 19 May 2009 06:52:20 -0700 (PDT)
Received: from asmtp1.iomartmail.com (localhost.localdomain [127.0.0.1]) by asmtp1.iomartmail.com (8.12.11.20060308/8.12.8) with ESMTP id n4JDrtdt003944 for <routing-discussion@ietf.org>; Tue, 19 May 2009 14:53:55 +0100
Received: from your029b8cecfe (dsl-sp-81-140-15-32.in-addr.broadbandscope.com [81.140.15.32]) (authenticated bits=0) by asmtp1.iomartmail.com (8.12.11.20060308/8.12.11) with ESMTP id n4JDrsr3003935 for <routing-discussion@ietf.org>; Tue, 19 May 2009 14:53:55 +0100
Message-ID: <604C72C023784318A97135CFF626C863@your029b8cecfe>
From: "Adrian Farrel" <adrian@olddog.co.uk>
To: <routing-discussion@ietf.org>
Subject: IETF Last Call: draft-ietf-opsawg-operations-and-management
Date: Tue, 19 May 2009 14:50:38 +0100
MIME-Version: 1.0
Content-Type: text/plain; format=flowed; charset="iso-8859-1"; reply-type=original
Content-Transfer-Encoding: 7bit
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 6.00.2900.5512
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.5579
X-BeenThere: routing-discussion@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
Reply-To: Adrian Farrel <adrian@olddog.co.uk>
List-Id: Routing Area General mailing list <routing-discussion.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/routing-discussion>,  <mailto:routing-discussion-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/routing-discussion>
List-Post: <mailto:routing-discussion@ietf.org>
List-Help: <mailto:routing-discussion-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/routing-discussion>, <mailto:routing-discussion-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 19 May 2009 13:52:22 -0000

All,

This I-D would not be binding on authors of new I-Ds, but gives "guidance". 
My interpretation is that the IESG might require consideration of this 
guidance when reviewing protocol specs so it would be sensible if you 
reviewed this work and commented during IETF last call.

Thanks,
Adrian
----- Original Message ----- 
From: "The IESG" <iesg-secretary@ietf.org>
To: "IETF-Announce" <ietf-announce@ietf.org>
Cc: <opsawg@ietf.org>
Sent: Tuesday, May 19, 2009 2:39 PM
Subject: Last Call: draft-ietf-opsawg-operations-and-management (Guidelines 
for Considering Operations and Management of New Protocols and Protocol 
Extensions) to BCP


> The IESG has received a request from the Operations and Management Area
> Working Group WG (opsawg) to consider the following document:
>
> - 'Guidelines for Considering Operations and Management of New Protocols
>   and Protocol Extensions '
>   <draft-ietf-opsawg-operations-and-management-07.txt> as a BCP
>
> The IESG plans to make a decision in the next few weeks, and solicits
> final comments on this action.  Please send substantive comments to the
> ietf@ietf.org mailing lists by 2009-06-02. Exceptionally,
> comments may be sent to iesg@ietf.org instead. In either case, please
> retain the beginning of the Subject line to allow automated sorting.
>
> The file can be obtained via
> http://www.ietf.org/internet-drafts/draft-ietf-opsawg-operations-and-management-07.txt
>
>
> IESG discussion can be tracked via
> https://datatracker.ietf.org/public/pidtracker.cgi?command=view_id&dTag=16452&rfc_flag=0
>
> _______________________________________________
> IETF-Announce mailing list
> IETF-Announce@ietf.org
> https://www.ietf.org/mailman/listinfo/ietf-announce
> 


