Re: [Roll] Fwd: New Version Notification for draft-tripathi-roll-rpl-simulation-01

Omprakash Gnawali <gnawali@cs.stanford.edu> Wed, 30 December 2009 00:17 UTC

Return-Path: <gnawali@cs.stanford.edu>
X-Original-To: roll@core3.amsl.com
Delivered-To: roll@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 7EDBE3A691A for <roll@core3.amsl.com>; Tue, 29 Dec 2009 16:17:56 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.277
X-Spam-Level:
X-Spam-Status: No, score=-4.277 tagged_above=-999 required=5 tests=[AWL=-1.500, BAYES_50=0.001, FM_FORGED_GMAIL=0.622, J_CHICKENPOX_82=0.6, RCVD_IN_DNSWL_MED=-4]
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 46QfY999QbJy for <roll@core3.amsl.com>; Tue, 29 Dec 2009 16:17:55 -0800 (PST)
Received: from cs-smtp-2.Stanford.EDU (cs-smtp-2.Stanford.EDU [171.64.64.26]) by core3.amsl.com (Postfix) with ESMTP id AF6AE3A68E7 for <roll@ietf.org>; Tue, 29 Dec 2009 16:17:55 -0800 (PST)
Received: from qw-out-2122.google.com ([74.125.92.25]) by cs-smtp-2.Stanford.EDU with esmtpsa (TLSv1:RC4-MD5:128) (Exim 4.60) (envelope-from <gnawali@cs.stanford.edu>) id 1NPmFr-0007pb-JE for roll@ietf.org; Tue, 29 Dec 2009 16:17:36 -0800
Received: by qw-out-2122.google.com with SMTP id 9so2539375qwb.31 for <roll@ietf.org>; Tue, 29 Dec 2009 16:17:34 -0800 (PST)
MIME-Version: 1.0
Received: by 10.224.84.197 with SMTP id k5mr2206688qal.204.1262132254661; Tue, 29 Dec 2009 16:17:34 -0800 (PST)
In-Reply-To: <e9ba5eb80912291558l1dcc4bdcqbadb7b69ce68cb9e@mail.gmail.com>
References: <20091222035821.C522A3A6966@core3.amsl.com> <E694FFD2-5EBC-43DF-8278-F6FBE6ADF94C@ece.drexel.edu> <d4dcddd20912222309k38034cdv675fc17709e1eca4@mail.gmail.com> <d4dcddd20912222352u3add47b4j753fafa6558c1935@mail.gmail.com> <e9ba5eb80912231633y211a931cna59443e11efe3deb@mail.gmail.com> <e9ba5eb80912232224p62566e36sc497af4c00fc581@mail.gmail.com> <32377771-299D-41B6-98A4-02AF14167D99@cs.stanford.edu> <e9ba5eb80912291558l1dcc4bdcqbadb7b69ce68cb9e@mail.gmail.com>
Date: Tue, 29 Dec 2009 19:17:34 -0500
Message-ID: <d4dcddd20912291617oaf569aewadec43c93fd92e81@mail.gmail.com>
From: Omprakash Gnawali <gnawali@cs.stanford.edu>
To: Joydeep Tripathi <joydeep.tripathi@gmail.com>
Content-Type: text/plain; charset="ISO-8859-1"
Content-Transfer-Encoding: quoted-printable
X-Scan-Signature: 1c1d34d4ae2aac1d1f929c6f17b0cb0c
Cc: ROLL WG <roll@ietf.org>
Subject: Re: [Roll] Fwd: New Version Notification for draft-tripathi-roll-rpl-simulation-01
X-BeenThere: roll@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Routing Over Low power and Lossy networks <roll.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/roll>, <mailto:roll-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/roll>
List-Post: <mailto:roll@ietf.org>
List-Help: <mailto:roll-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/roll>, <mailto:roll-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 30 Dec 2009 00:17:56 -0000

On Tue, Dec 29, 2009 at 6:58 PM, Joydeep Tripathi
<joydeep.tripathi@gmail.com> wrote:
> Hi,
>
> On Thu, Dec 24, 2009 at 2:25 AM, Philip Levis <pal@cs.stanford.edu> wrote:
>>
>> On Dec 23, 2009, at 10:24 PM, Joydeep Tripathi wrote:
>>
>>> On Wed, Dec 23, 2009 at 2:52 AM, Omprakash Gnawali
>>> <gnawali@cs.stanford.edu>
>>>  wrote:
>>>>
>>>> I managed to find the pdf with the graphs. Here are some comments.
>>>>
>>>> It will help greatly if more information about the link model were
>>>> included. -01 mentions:
>>>>
>>>> "* Link failure model: Time varying real network traces containing
>>>> packet delivery probability for each
>>>> link and over all channels for both indoor network deployment and
>>>> outdoor network deployment were used.
>>>> Thus, di erent types of link characteristics are used in the study.
>>>> * Topology: The topologies are gathered from real-life deployment
>>>> (traces mentioned above) as opposed
>>>> to random topology simulations. are repeated here:"
>>>>
>>> Actually,we collected real-life traces with hundreds of links varying
>>> with time for the network,  and simulated the same variation in PDR
>>> for each link as in the real deployment.
>>
>> I don't understand -- how do you do this? There has to be some interval over
>> which you average, unless you are replaying success/failure traces. Link can
>> very much faster than every ten seconds.
>
> Actually you are right, the PDR value of a link is averaged over 100
> packets over an interval. When the trace was gathered, during each 15
> minutes interval, 100 packets are transmitted over a link in the
> network. Out of 100 packets, number of successfully received packets
> was count for each link between two communicating nodes that are
> physically one hop away. The number of successfully received packets
> out of 100 packets originally transmitted was recorded as the PDR of
> the link after each 15 minutes interval. In our simulation, we
> consider the PDR between those two nodes to be constant during a 10
> minutes interval. When an interval gets over, we consider the next PDR
> value between same two nodes in the database of traces, that was
> collected during the next interval and use that value for next
> interval.
>
> I hope this clarifies how the link quality traces are gathered and
> used. Please let me know if you have further questions.

Each node sends a packet every 9 seconds to estimate the link quality
and the estimate is updated every 100 packets?

Do you consider datarate in your simulation?

I did not understand why data collection uses a window of 15 mins and
data use uses a window of 10 mins.

- om_p