IETF Logo Mail Archive

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

Rahul Jadhav <nyrahul@outlook.com> Tue, 14 April 2020 02:04 UTC

Return-Path: <nyrahul@outlook.com>
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 80CA83A02BC for <roll@ietfa.amsl.com>; Mon, 13 Apr 2020 19:04:54 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.099
X-Spam-Level:
X-Spam-Status: No, score=-2.099 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, RCVD_IN_MSPIKE_H2=-0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=outlook.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 JEkKMGChodpa for <roll@ietfa.amsl.com>; Mon, 13 Apr 2020 19:04:51 -0700 (PDT)
Received: from APC01-PU1-obe.outbound.protection.outlook.com (mail-oln040092254063.outbound.protection.outlook.com [40.92.254.63]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 4EBFB3A0147 for <roll@ietf.org>; Mon, 13 Apr 2020 19:04:51 -0700 (PDT)
ARC-Seal: i=1; a=rsa-sha256; s=arcselector9901; d=microsoft.com; cv=none; b=dM20VorZIF6ebkE2TA/m5ckQetS5j4OeteeYxh5d/y9xDkrlvEiCxtld1UNs+Yif1RdzyX76St49F3CT2BPIOtwfbG8CagYT3VKC5Dtat9xC1infGMkzhQfMuokO8W89SV9Cr5Tb0fUQt2F40Ygs1DhYdXbXKgAvyWteOWRdpY3+obWXJC+LJYkKQ3xnnparBDyBBJnLtrff6lTzt6LCR0/22t0+5pFH39PRDn85iemjzaH3uExt7ZWKgTUrDLOi01KS+Q6Qrgb/e3w2ze0TjUmsoq94hn5BNFI8Y3FR222UoZLweCIuxs0q6YyPE5rHhmTEFNwkE3x+R3YcRdWyFA==
ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=microsoft.com; s=arcselector9901; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-SenderADCheck; bh=rHm+kpzf+gl9liKSkiCph29tmnZO7BfgAGefOwq1Uf0=; b=HxKZIg65ZiJ7WRemwifT3a4BhO6Pko9xs1VuffGJxlgO/RMnsXnK6AKIszOaKKAgjxqxG1F/wpiUYo7CvWGkeSRTrD0ByE8crjv6dATiL/kdZzBVelwUYixMzZH1t3zukqMkOyZGvT0CvFaUWV16Ekc5Mm4VrXdmWbYlIqEjK2Ipc4CfeHc19JMlB6gfu1PBSNVnYs7fMREId0/M+PjMeh5o18Z9ZU9MD9+V1uLZN9rzmOgQeGzvz0c8OdZHBR2ERKJmJgDwaiVeIL97bj2rz3x0zEP2EV792wae3GXK4AeRDwySD0M+P+DCyf3eTyAPzn7Bu5VS/qwWRDcgqbUQAA==
ARC-Authentication-Results: i=1; mx.microsoft.com 1; spf=none; dmarc=none; dkim=none; arc=none
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=outlook.com; s=selector1; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-SenderADCheck; bh=rHm+kpzf+gl9liKSkiCph29tmnZO7BfgAGefOwq1Uf0=; b=ZghSu/w1KmDP/+2xmIv1+utaiWbwukSfoeXtifY1mHL7Cul1KIoPuA7P9vhZUSVIZH51Ljys9vOmKxIXh0vg59BQSyEKqXR3bumOUZga7RQNdnd/TD99U1F3lY2To3vCzBn7bbmLmAJzwHa6/not1O7FuYIF+nVNoY4GxO4Y0YuBnHmr+ejpXrmoa2y6n+LKFK1b9hNNTNvXYPZvg5jTO8QwNi3L0OHcgIrNd8DtzoiriNJxDIvDYzHLq+xkKWymhT4yJCWKs9dqxj13fCJ5Qywh9MBAVqL6oKlqy9ridVH1w46jq5vWBq8FPMbtWCSbFUEv5R9EPylEKh92Fl3Ouw==
Received: from SG2APC01FT112.eop-APC01.prod.protection.outlook.com (2a01:111:e400:7ebd::50) by SG2APC01HT097.eop-APC01.prod.protection.outlook.com (2a01:111:e400:7ebd::456) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.2900.18; Tue, 14 Apr 2020 02:04:48 +0000
Received: from BM1PR01MB4020.INDPRD01.PROD.OUTLOOK.COM (10.152.250.59) by SG2APC01FT112.mail.protection.outlook.com (10.152.250.201) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.2900.15 via Frontend Transport; Tue, 14 Apr 2020 02:04:48 +0000
Received: from BM1PR01MB4020.INDPRD01.PROD.OUTLOOK.COM ([fe80::a1ff:5c53:dc37:c050]) by BM1PR01MB4020.INDPRD01.PROD.OUTLOOK.COM ([fe80::a1ff:5c53:dc37:c050%6]) with mapi id 15.20.2900.028; Tue, 14 Apr 2020 02:04:48 +0000
From: Rahul Jadhav <nyrahul@outlook.com>
To: Routing Over Low power and Lossy networks <roll@ietf.org>
Thread-Topic: [Roll] unaware leaves - graceful shutdown of attached-6LR
Thread-Index: AQHWEZQvbgNuDRZQpEGmjIYHLkz6MKh3KT0IgAC0VwQ=
Date: Tue, 14 Apr 2020 02:04:48 +0000
Message-ID: <BM1PR01MB4020A5C1C43CDC700477C39EA9DA0@BM1PR01MB4020.INDPRD01.PROD.OUTLOOK.COM>
References: <BM1PR01MB402069255ECA6D35B53B8BC1A9DD0@BM1PR01MB4020.INDPRD01.PROD.OUTLOOK.COM>, <43981634-330F-496C-AE8F-CB4423448F3D@cisco.com>
In-Reply-To: <43981634-330F-496C-AE8F-CB4423448F3D@cisco.com>
Accept-Language: en-IN, en-US
Content-Language: en-IN
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-incomingtopheadermarker: OriginalChecksum:D87808778C4E6BD97B18D109AB163D327531C09D377EEE5B098B611F60D5ABD6; UpperCasedChecksum:E844B6B827443BFEA003B9828E48778A30D556BA64E72CAE0C1926F973B4AB1C; SizeAsReceived:6937; Count:44
x-tmn: [KhELeIiiHNFSf6sQDqicEfVc4RbWeMO/]
x-ms-publictraffictype: Email
x-incomingheadercount: 44
x-eopattributedmessage: 0
x-ms-office365-filtering-correlation-id: f0038dde-e14b-491a-4341-08d7e0183604
x-ms-traffictypediagnostic: SG2APC01HT097:
x-microsoft-antispam: BCL:0;
x-microsoft-antispam-message-info: XMXmR53g+7GIfyyBuRMQiCnIKj7O5HS8bKPAKocDHbkZ12VGfutym7QBgINvpaKfbonslpIMmiNgrnV7NsmK5XSx8dP5+vXHHthJXObDYIEYQmEO6mRKEAmSjp1BnhhYZUTuDqB/JRfZyfq5YS/foz0s34KwUYhU9ovezNlM6ttrOPbxcUjFYCa7dTEVXUQ1KCUiNVjhjQf26poVMpdauOY1ltbkHjvIoH0mYAj/Iik=
x-forefront-antispam-report: CIP:255.255.255.255; CTRY:; LANG:en; SCL:0; SRV:; IPV:NLI; SFV:NSPM; H:BM1PR01MB4020.INDPRD01.PROD.OUTLOOK.COM; PTR:; CAT:NONE; SFTY:; SFS:; DIR:OUT; SFP:1901;
x-ms-exchange-antispam-messagedata: 8Fv/3h2CGm8+uEsW6EKUKqc/Uyo49LStlM2d2xv0pJtbU/7N1Fy3xt3zVT56C2u3sAC6vJReDIic04c28x3cljU9hr0HxY4YWVXvtshlMJfByt8SBSWfUCQnXK7bzM89fKizsY96EqAVosN6IhgXjg==
x-ms-exchange-transport-forked: True
Content-Type: multipart/alternative; boundary="_000_BM1PR01MB4020A5C1C43CDC700477C39EA9DA0BM1PR01MB4020INDP_"
MIME-Version: 1.0
X-OriginatorOrg: outlook.com
X-MS-Exchange-CrossTenant-RMS-PersistedConsumerOrg: 00000000-0000-0000-0000-000000000000
X-MS-Exchange-CrossTenant-Network-Message-Id: f0038dde-e14b-491a-4341-08d7e0183604
X-MS-Exchange-CrossTenant-rms-persistedconsumerorg: 00000000-0000-0000-0000-000000000000
X-MS-Exchange-CrossTenant-originalarrivaltime: 14 Apr 2020 02:04:48.5221 (UTC)
X-MS-Exchange-CrossTenant-fromentityheader: Internet
X-MS-Exchange-CrossTenant-id: 84df9e7f-e9f6-40af-b435-aaaaaaaaaaaa
X-MS-Exchange-Transport-CrossTenantHeadersStamped: SG2APC01HT097
Archived-At: <https://mailarchive.ietf.org/arch/msg/roll/b4wkp_DhPcN-u43SHo1JjH57__w>
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: Tue, 14 Apr 2020 02:04:55 -0000

Please find my response inline.

________________________________
From: Roll <roll-bounces@ietf.org> on behalf of Pascal Thubert (pthubert) <pthubert=40cisco.com@dmarc.ietf.org>
Sent: 13 April 2020 11:14 PM
To: Routing Over Low power and Lossy networks <roll@ietf.org>
Subject: Re: [Roll] unaware leaves - graceful shutdown of attached-6LR

Great point Rahul.

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.

Status removed indicates an error. I’d rather use status 0, lifetime 0, ‘R’ off. Don’t you think?

[RJ] Imo, Lifetime is something that is controlled by the target/owner. There has never been (?) a case where someone else changes lifetime on behalf of the target node.
RFC 8505 states: "Removed: The binding state was removed.  This Status MAY be placed in an NA(EARO) message that is sent as the rejection of a proxy registration to an IPv6 ND Registrar, or in an asynchronous NA(EARO), at any time."
I still feel using Status="Removed", 'R' off may be applicable more.

Keep safe.

Pascal

Le 13 avr. 2020 à 15:07, Rahul Jadhav <nyrahul@outlook.com> a écrit :


Hello Pascal/Authors,

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?
Is this correct/allowed? For RPL we have route-poisoning using which a 6LR does a graceful shutdown, but the route-poisoning is not applicable to RULs.. I believe this should be clarified in the text.

Regards,
Rahul
_______________________________________________
Roll mailing list
Roll@ietf.org
https://www.ietf.org/mailman/listinfo/roll

v2.23.0 | Report a Bug | By Email