IETF Logo Mail Archive

Re: [Roll] unaware leaves - graceful shutdown of attached-6LR

Michael Richardson <mcr+ietf@sandelman.ca> Wed, 15 April 2020 20:39 UTC

Return-Path: <mcr+ietf@sandelman.ca>
X-Original-To: roll@ietfa.amsl.com
Delivered-To: roll@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id C03BC3A0A0B for <roll@ietfa.amsl.com>; Wed, 15 Apr 2020 13:39:31 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.888
X-Spam-Level:
X-Spam-Status: No, score=-1.888 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, SPF_HELO_NONE=0.001, T_SPF_PERMERROR=0.01, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
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 XNYNMcL_lkOl for <roll@ietfa.amsl.com>; Wed, 15 Apr 2020 13:39:29 -0700 (PDT)
Received: from tuna.sandelman.ca (tuna.sandelman.ca [IPv6:2607:f0b0:f:3:216:3eff:fe7c:d1f3]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 9E2283A0A0A for <roll@ietf.org>; Wed, 15 Apr 2020 13:39:29 -0700 (PDT)
Received: from sandelman.ca (obiwan.sandelman.ca [IPv6:2607:f0b0:f:2::247]) by tuna.sandelman.ca (Postfix) with ESMTP id ADE4A3897C for <roll@ietf.org>; Wed, 15 Apr 2020 16:37:43 -0400 (EDT)
Received: from localhost (localhost [IPv6:::1]) by sandelman.ca (Postfix) with ESMTP id 9E1B2602 for <roll@ietf.org>; Wed, 15 Apr 2020 16:39:25 -0400 (EDT)
From: Michael Richardson <mcr+ietf@sandelman.ca>
To: Routing Over Low power and Lossy networks <roll@ietf.org>
In-Reply-To: <43981634-330F-496C-AE8F-CB4423448F3D@cisco.com>
References: <BM1PR01MB402069255ECA6D35B53B8BC1A9DD0@BM1PR01MB4020.INDPRD01.PROD.OUTLOOK.COM> <43981634-330F-496C-AE8F-CB4423448F3D@cisco.com>
X-Mailer: MH-E 8.6; nmh 1.7+dev; GNU Emacs 25.1.1
X-Face: $\n1pF)h^`}$H>Hk{L"x@)JS7<%Az}5RyS@k9X%29-lHB$Ti.V>2bi.~ehC0; <'$9xN5Ub# z!G,p`nR&p7Fz@^UXIn156S8.~^@MJ*mMsD7=QFeq%AL4m<nPbLgmtKK-5dC@#:k
MIME-Version: 1.0
Content-Type: multipart/signed; boundary="=-=-="; micalg="pgp-sha256"; protocol="application/pgp-signature"
Date: Wed, 15 Apr 2020 16:39:25 -0400
Message-ID: <28985.1586983165@localhost>
Archived-At: <https://mailarchive.ietf.org/arch/msg/roll/fzAf4yOGC_3-fCDkoISsZGWy9tQ>
Subject: Re: [Roll] unaware leaves - graceful shutdown of attached-6LR
X-BeenThere: roll@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Routing Over Low power and Lossy networks <roll.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/roll>, <mailto:roll-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/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, 15 Apr 2020 20:39:32 -0000

Rahul Jadhav <nyrahul@outlook.com> wrote:
    > In the event that the attached 6LR needs to gracefully shutdown, it
    > needs to inform the RUL(s) to detach and possibly move to another 6LR.
    > I believe this could be done using NA(EARO, Status="Removed"); from the
    > attached-6LR. Can this NA be multicasted if the attached-6LR has more
    > than one RULs attached to it?

Pascal Thubert \(pthubert\) <pthubert=40cisco.com@dmarc.ietf.org> wrote:
    > Normally this is done using a final RA. But the RA is broadcast so
    > unicasting a NA with ‘R’ flag off is a great idea. This is the exact
    > signal that this router does not serve this node. Lifetime 0 would
    > indicate that the router removes the NCE.

The other reason that I think that we need to unicast the NA is because it
needs to occur when the sleepy device is awake.
That could take some time to reach all devices!

I agree that it would be better to do this before the 6LR goes away, as the
next time a device like a window-smash sensor wakes up could be because it
needs to send an ALERT :-)

I think that in a 6tisch scenario, it might take a few cycles of the schedule
to get all the unicast NAs sent.

--
Michael Richardson <mcr+IETF@sandelman.ca>, Sandelman Software Works
 -= IPv6 IoT consulting =-

v2.20.0 | Report a Bug | By Email