Re: [manet] Experiment with 2000 nodes with LOAD

"JP Vasseur (jvasseur)" <jvasseur@cisco.com> Wed, 17 October 2012 16:39 UTC

Return-Path: <jvasseur@cisco.com>
X-Original-To: manet@ietfa.amsl.com
Delivered-To: manet@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 49B2421F86A3 for <manet@ietfa.amsl.com>; Wed, 17 Oct 2012 09:39:11 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -10.598
X-Spam-Level:
X-Spam-Status: No, score=-10.598 tagged_above=-999 required=5 tests=[AWL=-0.000, BAYES_00=-2.599, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_HI=-8]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id ufsffBBpQbOA for <manet@ietfa.amsl.com>; Wed, 17 Oct 2012 09:39:10 -0700 (PDT)
Received: from rcdn-iport-4.cisco.com (rcdn-iport-4.cisco.com [173.37.86.75]) by ietfa.amsl.com (Postfix) with ESMTP id 2B23721F8619 for <manet@ietf.org>; Wed, 17 Oct 2012 09:39:10 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=10726; q=dns/txt; s=iport; t=1350491950; x=1351701550; h=from:to:cc:subject:date:message-id:references: in-reply-to:mime-version; bh=mIb6t3b7Wo2ZKqDMHOirhsjlrQjVyD+MoZGrOHXlV3M=; b=PRopHFA8ZSbpofX9BBcnCjLDbKEqbIYMd0K8ubIQq4aCBIVZbzh42c7y x/DOjn1cRrdUBjwIz7PMeH9loz2htb9dJsr7ceaLuPfSd+1/DDKVNyQG/ E5FAPBj7mZOCUDn65TTqHv7c7d7vwfgIlsql1I4oTD6CbjHRqMCR2X9Zx Y=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AgIFAOrdflCtJV2Y/2dsb2JhbABFgkq0ewGIWoEIgiABAQEDAQEBAQ8BWAMLBQsCAQgiHQcnCxQRAgQOBQgah1wGC5stoC2LWAoQhUhgA5cAjTSBa4JvgVwHHBg
X-IronPort-AV: E=Sophos; i="4.80,602,1344211200"; d="scan'208,217"; a="132685802"
Received: from rcdn-core-1.cisco.com ([173.37.93.152]) by rcdn-iport-4.cisco.com with ESMTP; 17 Oct 2012 16:39:07 +0000
Received: from xhc-aln-x01.cisco.com (xhc-aln-x01.cisco.com [173.36.12.75]) by rcdn-core-1.cisco.com (8.14.5/8.14.5) with ESMTP id q9HGd6Wu031610 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL); Wed, 17 Oct 2012 16:39:06 GMT
Received: from xmb-rcd-x02.cisco.com ([169.254.4.118]) by xhc-aln-x01.cisco.com ([173.36.12.75]) with mapi id 14.02.0318.001; Wed, 17 Oct 2012 11:39:06 -0500
From: "JP Vasseur (jvasseur)" <jvasseur@cisco.com>
To: Thierry LYS <thierry.lys@erdfdistribution.fr>
Thread-Topic: [manet] Experiment with 2000 nodes with LOAD
Thread-Index: AQHNrIXsX9Q4I6nx+EWXPWrFiWjGfA==
Date: Wed, 17 Oct 2012 16:39:06 +0000
Message-ID: <03B78081B371D44390ED6E7BADBB4A7721FF091C@xmb-rcd-x02.cisco.com>
References: <OF38F683BD.8734DB37-ONC1257A9A.0055F173-C1257A9A.0057F743@notes.edfgdf.fr>
In-Reply-To: <OF38F683BD.8734DB37-ONC1257A9A.0055F173-C1257A9A.0057F743@notes.edfgdf.fr>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [10.21.82.231]
x-tm-as-product-ver: SMEX-10.2.0.1135-7.000.1014-19280.000
x-tm-as-result: No--46.726700-8.000000-31
x-tm-as-user-approved-sender: No
x-tm-as-user-blocked-sender: No
Content-Type: multipart/alternative; boundary="_000_03B78081B371D44390ED6E7BADBB4A7721FF091Cxmbrcdx02ciscoc_"
MIME-Version: 1.0
Cc: "<manet@ietf.org>" <manet@ietf.org>
Subject: Re: [manet] Experiment with 2000 nodes with LOAD
X-BeenThere: manet@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Mobile Ad-hoc Networks <manet.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/manet>, <mailto:manet-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/manet>
List-Post: <mailto:manet@ietf.org>
List-Help: <mailto:manet-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/manet>, <mailto:manet-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 17 Oct 2012 16:39:11 -0000

Thanks Thierry for your comments, this is useful.

That being said, let's bear in mind that one deployment is not sufficient to draw performance conclusion. This is especially true with reactive protocol
where the control traffic is driven by the user traffic, by contrast with reactive routing where the topology is built regardless of the user traffic profile.
But let's discuss about it once we have the new revisions of the drafts, see what the options are, …

ROLL co-chair hat on, if Load-ng deals with LLNs, all I am asking is to make sure that ROLL gets involved considering the expertise of the WG on these
environments (as you rightfully pointed out, AMI PLC are clearly a very constrained LLNs).

Best Regards.

JP.

On Oct 17, 2012, at 6:00 PM, Thierry LYS wrote:


Hi Cédric Chauvenet,

As mentionned in Lavenu's previous mail we have rolled-out a 2000 G3 PLC  (an internationally standardized PLC technology) node trial and obtained excellent performances :

  *   daily collection success rate of 98 %
  *   dicovery rate of 99,7 % (the remaining meters is facing in majority HW problems)

It is more than a year and a half that this experiment runs !

...and believe me, PLC is a very harsh media and routing is playing a critical role here. We see along the day a very stable communication rate even in duty hours (around 8 AM and 6-9 PM)
This experiment proves that LOAD is a good protocol for large PLC networks characterized by low bandwidth, unstable links and link asymmetry.
We use our experience to improve it and that's how LOADng has come up !
Finally, PLC media is probably not so far from mobile networks since attenuation and noise is changing with time !

Best regards,

Thierry Lys
ERDF
<Mail Attachment.gif>    Thierry Lys
Direction Comptage / Metering Division
Building Crysalis - 345 Avenue Georges Clémenceau - 92000 Nanterre - France
Tel : +33 (0)1 81 97 67 77


Hi Cédric, (Hope people will follow which cedric is talking !)

Le 16 oct. 2012 à 18:58, Cedric-2 LAVENU a écrit :

Dear Cédric,

I'm not sure all this discussions really make sense :

> An LLN network is definitely a type of MANET

As JP pointed out, if LLNs challenges can be addressed  in MANET, why would have ROLL being created ?
I think that a protocol intend to LLNs, or if LLNs are included in the scope should be reviewed by the ROLL working group , as it is the place dedicated by the IETF.

Does that makes sense ?

according to what Adrian said (he has been quoted several times in the past mails). One of the fileds LOADng is intended to be used are AMI PLC networks with low bandwidth (few kbps in the harshest environments), but can be extensible to other types of MANETs.

And regarding your comment about experience with LOADng :

> LOADng is a protocol for which several running implementations exist and interoperate as shown in draft : http://tools.ietf.org/html/draft-lavenu-lln-loadng-interoperability-report-02

yes it has been discussed, and explained that the goal of these test were focused on validating the protocol behavior, not the performance.

> In addition, LOAD (the previous version) was successfully run in a 2000 PLC node trial.

Very nice !
Would you mind to share some details on this ?

Cédric.


I think that all the facts are on the table to say that LOAD would be suitable for MANETs (LLNs being a subset of MANETs). In addition field and lab experience does exist and demonstrated that LOADng can be very efficient.

Regards,
Cédric _______________________________________________
manet mailing list
manet@ietf.org<mailto:manet@ietf.org>
https://www.ietf.org/mailman/listinfo/manet