Re: [6tisch] 6P and Sf0 issue: 6top protocol behaviour at boot

"Pascal Thubert (pthubert)" <pthubert@cisco.com> Thu, 10 March 2016 23:47 UTC

Return-Path: <pthubert@cisco.com>
X-Original-To: 6tisch@ietfa.amsl.com
Delivered-To: 6tisch@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 0C5D812DDF2 for <6tisch@ietfa.amsl.com>; Thu, 10 Mar 2016 15:47:02 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -14.519
X-Spam-Level:
X-Spam-Status: No, score=-14.519 tagged_above=-999 required=5 tests=[AC_DIV_BONANZA=0.001, BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_HI=-5, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, RP_MATCHES_RCVD=-0.001, USER_IN_DEF_DKIM_WL=-7.5] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=cisco.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Wge-C-0L0TtH for <6tisch@ietfa.amsl.com>; Thu, 10 Mar 2016 15:47:00 -0800 (PST)
Received: from rcdn-iport-2.cisco.com (rcdn-iport-2.cisco.com [173.37.86.73]) (using TLSv1.2 with cipher DHE-RSA-SEED-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id CF47C12DCA9 for <6tisch@ietf.org>; Thu, 10 Mar 2016 15:46:59 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=9874; q=dns/txt; s=iport; t=1457653619; x=1458863219; h=from:to:cc:subject:date:message-id:references: in-reply-to:mime-version; bh=6qbkIAu07VSwRTjoWvO6chzbZFe5VQzAzhyjeoud+iE=; b=LGk6gjH1Fe1tVxX9kLr+N5b/zFJZzBx6duPo1+7QjAWcuGbS2yhTZPX7 XTG5Rq+fAo1Bf96J0aLQnoQL2QiDO9LEBBdPuP9s78Gyc6m2rmKrYYwDu O2U79m32xvS0SDZVX43A07GGLjQc1s9Yz5bg60ww96VYn6lHZengTVszB U=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: =?us-ascii?q?A0AFAgCFBuJW/4oNJK1egnJMUm26JAENg?= =?us-ascii?q?W0dhXICgUA4FAEBAQEBAQFkJ4RBAQEBBEkwEAIBCBEEAQEoBzIUCQgCBA4FiCS?= =?us-ascii?q?9ZQEBAQEBAQEBAQEBAQEBAQEBAQEBARWGGIFzCIJHhBQHAQFTCIJtgQ8Fkn2EP?= =?us-ascii?q?wGGVochgWSNG45pAR4BAUKDZGqJFgkXgRsBAQE?=
X-IronPort-AV: E=Sophos; i="5.24,317,1454976000"; d="scan'208,217"; a="84521203"
Received: from alln-core-5.cisco.com ([173.36.13.138]) by rcdn-iport-2.cisco.com with ESMTP/TLS/DHE-RSA-AES256-SHA; 10 Mar 2016 23:46:58 +0000
Received: from XCH-ALN-003.cisco.com (xch-aln-003.cisco.com [173.36.7.13]) by alln-core-5.cisco.com (8.14.5/8.14.5) with ESMTP id u2ANkwwa007977 (version=TLSv1/SSLv3 cipher=AES256-SHA bits=256 verify=FAIL); Thu, 10 Mar 2016 23:46:58 GMT
Received: from xch-rcd-001.cisco.com (173.37.102.11) by XCH-ALN-003.cisco.com (173.36.7.13) with Microsoft SMTP Server (TLS) id 15.0.1104.5; Thu, 10 Mar 2016 17:46:57 -0600
Received: from xch-rcd-001.cisco.com ([173.37.102.11]) by XCH-RCD-001.cisco.com ([173.37.102.11]) with mapi id 15.00.1104.009; Thu, 10 Mar 2016 17:46:58 -0600
From: "Pascal Thubert (pthubert)" <pthubert@cisco.com>
To: "Prof. Diego Dujovne" <diego.dujovne@mail.udp.cl>
Thread-Topic: [6tisch] 6P and Sf0 issue: 6top protocol behaviour at boot
Thread-Index: AQHReyQvwbBbqE4NSEOe/B8D7SbA2Z9TV/zx
Date: Thu, 10 Mar 2016 23:46:58 +0000
Message-ID: <48716627-C2D1-417B-BB8C-BE7026A205D5@cisco.com>
References: <CAH7SZV-wE=mhNm9DM6_xigGeGQD352XjNzNc=c7JewHvUvBxbw@mail.gmail.com> <db9afb0eddea42239c7203e29af6fdc1@XCH-RCD-001.cisco.com>, <CAH7SZV-7mH0PXg3bBB_cmEJhC7jyLbgFdR32=QpASCxg6Fz3+A@mail.gmail.com>
In-Reply-To: <CAH7SZV-7mH0PXg3bBB_cmEJhC7jyLbgFdR32=QpASCxg6Fz3+A@mail.gmail.com>
Accept-Language: fr-FR, en-US
Content-Language: fr-FR
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-ms-exchange-transport-fromentityheader: Hosted
Content-Type: multipart/alternative; boundary="_000_48716627C2D1417BBB8CBE7026A205D5ciscocom_"
MIME-Version: 1.0
Archived-At: <http://mailarchive.ietf.org/arch/msg/6tisch/TkNwMeP2ZzXk3ctEJ7mbSbS7Qb8>
Cc: "6tisch@ietf.org" <6tisch@ietf.org>
Subject: Re: [6tisch] 6P and Sf0 issue: 6top protocol behaviour at boot
X-BeenThere: 6tisch@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: "Discuss link layer model for Deterministic IPv6 over the TSCH mode of IEEE 802.15.4e, and impacts on RPL and 6LoWPAN such as resource allocation" <6tisch.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/6tisch>, <mailto:6tisch-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/6tisch/>
List-Post: <mailto:6tisch@ietf.org>
List-Help: <mailto:6tisch-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/6tisch>, <mailto:6tisch-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 10 Mar 2016 23:47:02 -0000

Correct Diego

And that's a desired effect so that a node gets a lot of bandwidth to complete its join. You better complete a few at a time then have hundreds half way through and none fully done.

We may actually reject a join if the queue is too long, exhausting=sleep well and come back in 10

Take care,

Pascal

Le 11 mars 2016 ? 00:25, Prof. Diego Dujovne <diego.dujovne@mail.udp.cl<mailto:diego.dujovne@mail.udp.cl>> a ?crit :

Pascal,
          I was thinking of a worst-case condition: all neighbours are
willing to join. A limited pool would satisfy only a part of them, thus
putting the rest of the nodes in a join queue. Am I correct?
Regards,

                      Diego


2016-03-04 7:55 GMT-03:00 Pascal Thubert (pthubert) <pthubert@cisco.com<mailto:pthubert@cisco.com>>:
Hello Diego:

One suggestion would be that when a node attempts to join, the parent immediately grants a set of cells for the join process from a limited pool (to avoid DDOS). These cells are to be released at the end of the join and are there to boost the bandwidth for that critical phase.

Cheers,

Pascal

From: 6tisch [mailto:6tisch-bounces@ietf.org<mailto:6tisch-bounces@ietf.org>] On Behalf Of Prof. Diego Dujovne
Sent: jeudi 3 mars 2016 17:12
To: 6tisch@ietf.org<mailto:6tisch@ietf.org>
Subject: [6tisch] 6P and Sf0 issue: 6top protocol behaviour at boot

Dear all,
            Although it was discussed, there is no specification
on the 6top behaviour at boot. The discussion point here is if the
6top messages shall be transmitted on minimal cells until
the slotframe 1 (SFR1) has been populated enough to support
the transactions.
          - The use of minimal is optional. In case minimal is used,
the decision on when to switch is out of scope?
          - In case minimal is not used, shall we specify another
mechanism to enable 6top to transmit messages?
Thanks!
Regards,
                                             Diego Dujovne

--
DIEGO DUJOVNE
Acad?mico Escuela de Ingenier?a en Inform?tica y Telecomunicaciones
Facultad de Ingenier?a UDP
www.ingenieria.udp.cl<http://www.ingenieria.udp.cl>
(56 2) 676 8125



--
DIEGO DUJOVNE
Acad?mico Escuela de Ingenier?a en Inform?tica y Telecomunicaciones
Facultad de Ingenier?a UDP
www.ingenieria.udp.cl<http://www.ingenieria.udp.cl>
(56 2) 676 8125