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

"Prof. Diego Dujovne" <diego.dujovne@mail.udp.cl> Thu, 10 March 2016 23:25 UTC

Return-Path: <diego.dujovne@mail.udp.cl>
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 08BFA12DE76 for <6tisch@ietfa.amsl.com>; Thu, 10 Mar 2016 15:25:53 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.598
X-Spam-Level:
X-Spam-Status: No, score=-2.598 tagged_above=-999 required=5 tests=[AC_DIV_BONANZA=0.001, BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-0.7] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=mail-udp-cl.20150623.gappssmtp.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 i7XhCbRX1Le1 for <6tisch@ietfa.amsl.com>; Thu, 10 Mar 2016 15:25:51 -0800 (PST)
Received: from mail-wm0-x234.google.com (mail-wm0-x234.google.com [IPv6:2a00:1450:400c:c09::234]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id B52F512DE72 for <6tisch@ietf.org>; Thu, 10 Mar 2016 15:25:50 -0800 (PST)
Received: by mail-wm0-x234.google.com with SMTP id p65so7230335wmp.0 for <6tisch@ietf.org>; Thu, 10 Mar 2016 15:25:50 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=mail-udp-cl.20150623.gappssmtp.com; s=20150623; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc; bh=I7iAYAZPWuk/7DGIx+0/9zvrxIJb+LgCgNaE35D7Lg0=; b=h6+HtM2pYP+sKDPL6pcX1hVrC/Dh3FS5O0R0faUByUO6lR5PS3rWSxpNijsuqSimPh qGUhF0jshTxC3YtBmMLATP2taz+DdaryL70DcCKe6qEj1l3Ihi99M+W9UqMAIUUBm/T2 +WtbQ9SD3q7UiazXL9LrFGo5akKmb5+sAK5dEiRUyo/vtgOOSk5hUdr9nutoM0y1W/16 aLos7EAxQ1La5mDoW7GnuMs9s1JT9RQtYVHjM7owBTuUDdp/tEAw2FHL2HUCCoH2/tHL 7Q1zQ5PyEtoQI3/Ti1Wk0+G2RStvzEFMpI7C5FcRHI8sd3CRBtAd3m2IpqaMj8B9dVPA D5pA==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:in-reply-to:references:date :message-id:subject:from:to:cc; bh=I7iAYAZPWuk/7DGIx+0/9zvrxIJb+LgCgNaE35D7Lg0=; b=KdfgvjkT7UaXDgMl3U8QMWs80xkUcLhX+N3fD26W33Ene6FToRmrpYFUgzH8jWMUi6 WkjdupRdydNQ2rql+5ym+Bq8DuAdb/E05CTy8hX5JCljqFJaUPXA67xUNTwc8A94fD/V +9OL+mCW4jlFM85wmS5INxhPxFMHlsewpNUjJR21kH/RMYH3pk2yRc9D3e7VwOmrF62h ZI7/iZPNBmaO+Jk1z02MOCK5+b024tHvYAudQ3PqiU5z54XnHpqtB6iqOzAA/Oc8xnkJ HF6163OrmhMwWPpIRhFQNgvsvMB4qsm/1gA5oRhjkC/EPhfZQGkVehwX727XntRNCL2L RjrQ==
X-Gm-Message-State: AD7BkJJueIapKCyX3RveHY81q3/myZ9qI2aUBBrNp6YHvBG1hM53PTZCudq1ipkQtju1uLG+tirL2a0qS6moiQ==
MIME-Version: 1.0
X-Received: by 10.28.195.9 with SMTP id t9mr929054wmf.0.1457652349015; Thu, 10 Mar 2016 15:25:49 -0800 (PST)
Received: by 10.28.11.195 with HTTP; Thu, 10 Mar 2016 15:25:48 -0800 (PST)
In-Reply-To: <db9afb0eddea42239c7203e29af6fdc1@XCH-RCD-001.cisco.com>
References: <CAH7SZV-wE=mhNm9DM6_xigGeGQD352XjNzNc=c7JewHvUvBxbw@mail.gmail.com> <db9afb0eddea42239c7203e29af6fdc1@XCH-RCD-001.cisco.com>
Date: Thu, 10 Mar 2016 20:25:48 -0300
Message-ID: <CAH7SZV-7mH0PXg3bBB_cmEJhC7jyLbgFdR32=QpASCxg6Fz3+A@mail.gmail.com>
From: "Prof. Diego Dujovne" <diego.dujovne@mail.udp.cl>
To: "Pascal Thubert (pthubert)" <pthubert@cisco.com>
Content-Type: multipart/alternative; boundary=001a1148d9fe782d3b052dba223b
Archived-At: <http://mailarchive.ietf.org/arch/msg/6tisch/wFUPG-jSCw7qLRCVlqeFQIIdlyY>
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:25:53 -0000

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>om>:

> 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] *On Behalf Of *Prof.
> Diego Dujovne
> *Sent:* jeudi 3 mars 2016 17:12
> *To:* 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
> (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
(56 2) 676 8125