Re: [6tisch] SF0 - Cell reclamation by RPL parent

Thomas Watteyne <twatteyne@gmail.com> Fri, 11 March 2016 13:53 UTC

Return-Path: <twatteyne@gmail.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 9C86312D6DD for <6tisch@ietfa.amsl.com>; Fri, 11 Mar 2016 05:53:42 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.699
X-Spam-Level:
X-Spam-Status: No, score=-2.699 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.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 Wg6WFSAyXfH5 for <6tisch@ietfa.amsl.com>; Fri, 11 Mar 2016 05:53:40 -0800 (PST)
Received: from mail-lb0-x236.google.com (mail-lb0-x236.google.com [IPv6:2a00:1450:4010:c04::236]) (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 7391A12D674 for <6tisch@ietf.org>; Fri, 11 Mar 2016 05:53:39 -0800 (PST)
Received: by mail-lb0-x236.google.com with SMTP id xr8so151521168lbb.1 for <6tisch@ietf.org>; Fri, 11 Mar 2016 05:53:39 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=BXrjuQXMDVrYzHNiT9MI+nhGUEtcXZ2q+I35rqCv2Tg=; b=zGNAAoyFOfSTL5Rywl5j/6aOuT9u7Jlsg3Yxgc3D/uxE9a5Ct/msbp6F8jZBJuYdVE FI9o9l52nY1ZVFM0xUPV4qXzbeV2LmxlHzBiNt6Ku99mRgmTbcTLTlpB4OUb6Ix3QX0N 8xNr/wxeBRVk/FWHV0h5SgClG36jw2kGMv7KIcxmOprSeHdvffw1e203agokP5YlgMaz KK5e+E0nHA4pLTWJDhbU312m0iwUQJAKPbcEDVQ2M5d7L9kMzRYz2IhxzdHXgVOGM+9a l6vlbYQpR/FkYnrlIeVdTd5NmkHVL3ZSyn9obNzSOX8nNGH82vxplYPpGDJhhSzVI1v5 k3Qw==
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:from:date :message-id:subject:to:cc; bh=BXrjuQXMDVrYzHNiT9MI+nhGUEtcXZ2q+I35rqCv2Tg=; b=izDUdR1Hw0Fd2ek8k4GZK7Lo8o1FqkJAjTjjr9YQe9ZW/gKcXEYQ+1KfnuD90oOjfo MpaOKdJuZSc7gSw09PLAzIYwb8wp3M9O1zHD0qQQ3daHudCf1gRhFs/dcS/0AzkYZzhA q7U/ukvCjs4SJ4y64p2kQfZL9EQHtmqlgZf7tJbAzodKEYYYVbry/LxL2seE4Pyn6iDj pnGvGH7iP1ZnLgVlvkdOQ8wOqc55tLCWxq3jHcF1oweGR+8/ukgEF/8CuE81c8PWqZUG ANk7DOw5ATg6wGjdbbkUljo4NPHH7ufNQSGTF6behldJnJBYsRQQ/ubchPR7AK7G641o 9oWw==
X-Gm-Message-State: AD7BkJJZZLhuL0YHKX7U57CEkoDHMOtKbRIKxdN8mZjTPZLpQCas6M3sGZ3JLi2lTpdce0Os3ikTx/bP8TIYbg==
X-Received: by 10.112.151.207 with SMTP id us15mr2402545lbb.28.1457704417410; Fri, 11 Mar 2016 05:53:37 -0800 (PST)
MIME-Version: 1.0
Received: by 10.25.41.212 with HTTP; Fri, 11 Mar 2016 05:53:17 -0800 (PST)
In-Reply-To: <56DD59C8.20403@ece.iisc.ernet.in>
References: <56DD59C8.20403@ece.iisc.ernet.in>
From: Thomas Watteyne <twatteyne@gmail.com>
Date: Fri, 11 Mar 2016 14:53:17 +0100
Message-ID: <CADJ9OA-kKzVbq+1f_5dYW6hv_TqrpXC2HkrZq1w+FezA7VhzXQ@mail.gmail.com>
To: "S.V.R.Anand" <anand@ece.iisc.ernet.in>
Content-Type: multipart/alternative; boundary="047d7b8744dafcc389052dc64122"
Archived-At: <http://mailarchive.ietf.org/arch/msg/6tisch/nVqLhxkGRjZjgLp7XivPRrJ2P18>
Cc: "6tisch@ietf.org" <6tisch@ietf.org>, "Prof. Diego Dujovne" <diego.dujovne@mail.udp.cl>
Subject: Re: [6tisch] SF0 - Cell reclamation by RPL parent
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: Fri, 11 Mar 2016 13:53:42 -0000

Anand,

You are raising a good point. This would mean that a 6P transaction is
started not by the the sender, but the receiver.

I have added a slide in the set for this afternoon's call, as a
high-bandwidth discussion might be best approach here.

Thomas

On Mon, Mar 7, 2016 at 11:36 AM, S.V.R.Anand <anand@ece.iisc.ernet.in>
wrote:

> Hi Diego and others,
>
> Since we are discussing about the message transactions in SF0, this mail
> is with
> respect to the RPL parent, the cell donor.
>
> There are situations where the RPL parent might want to apply a cell
> reclamation
> and, depending on the context, a reallocation policy dynamically. This
> results in one or more cells that
> have been given to its children are reclaimed by the RPL parent due to
> various
> reasons as below.
>
> - The child node is out of the network, or child and parent cannot reach
> each other,
>   after the 6P add cell transaction is complete, thereby delete cell
> operation is not
>   being transacted. Cell reclamation helps in "cell garbage" collection.
>
> - As add cell requests arrive asynchronously from its children, an RPL
>   parent implementing certain fairness objective might re-appropriate the
> cells
>   that have already alloted its children, especially during a resource
> crunch.
>
> - Referring to the following text in 4.2.5 of the 6tisch architecture
> document,
>
>   "...Note that a PCE is expected to have precedence in the allocation, so
> that  an RPL parent
>     would only be able to obtain portions that are not in-use by the PCE."
>
>   It may be that, an RPL parent might have to relinquish its own cells if
>    needed by PCE any time. In such a scenario, the RPL parent may be
> forced to
>   reclaim the cells given to its children.
>
> While the first case is relatively less complex, the latter two cases are
> problematic as these cases can lead to (i) potential race conditions, say
> between PCE and SF0 operations, and (ii) a cascading effect across several
> RPL
> parents down the DODAG. Currently, there is no mechanism defined to address
> this problem.
>
> I suppose the above text extends beyond SF0.
>
> In light of the above use cases and the associated problems, do you think
> it is a
> good idea to include an appropriate message in SF0 for reclaiming the
> cells by
> the RPL parent ? or are we inviting new set of problems by doing so ?
>
> Will be happy to receive your inputs.
>
> Anand
>
>
> --
> This message has been scanned for viruses and
> dangerous content by MailScanner, and is
> believed to be clean.
>
> _______________________________________________
> 6tisch mailing list
> 6tisch@ietf.org
> https://www.ietf.org/mailman/listinfo/6tisch
>