Re: [Roll] signaling RPI option value and support of RFC 8138 in RPLv2
Michael Richardson <mcr@sandelman.ca> Tue, 17 December 2019 18:00 UTC
Return-Path: <mcr@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 D5618120888 for <roll@ietfa.amsl.com>; Tue, 17 Dec 2019 10:00:44 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.199
X-Spam-Level:
X-Spam-Status: No, score=-4.199 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, 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 VaeyML_dZRmc for <roll@ietfa.amsl.com>; Tue, 17 Dec 2019 10:00:42 -0800 (PST)
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 6DA6A120CB2 for <roll@ietf.org>; Tue, 17 Dec 2019 10:00:37 -0800 (PST)
Received: from sandelman.ca (obiwan.sandelman.ca [IPv6:2607:f0b0:f:2::247]) by tuna.sandelman.ca (Postfix) with ESMTP id B26F838981 for <roll@ietf.org>; Tue, 17 Dec 2019 13:00:33 -0500 (EST)
Received: from localhost (localhost [IPv6:::1]) by sandelman.ca (Postfix) with ESMTP id 9F07651E for <roll@ietf.org>; Tue, 17 Dec 2019 13:00:36 -0500 (EST)
From: Michael Richardson <mcr@sandelman.ca>
To: Routing Over Low power and Lossy networks <roll@ietf.org>
In-Reply-To: <MN2PR11MB356594C2F7955220956FF6B0D8550@MN2PR11MB3565.namprd11.prod.outlook.com>
References: <MN2PR11MB356594C2F7955220956FF6B0D8550@MN2PR11MB3565.namprd11.prod.outlook.com>
X-Mailer: MH-E 8.6; nmh 1.7+dev; GNU Emacs 24.5.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: text/plain; charset="utf-8"
Content-Transfer-Encoding: quoted-printable
Date: Tue, 17 Dec 2019 13:00:36 -0500
Message-ID: <28470.1576605636@localhost>
Archived-At: <https://mailarchive.ietf.org/arch/msg/roll/nG-riIhpeJBS5w3D5oNe0EZfr6I>
Subject: Re: [Roll] signaling RPI option value and support of RFC 8138 in RPLv2
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, 17 Dec 2019 18:00:45 -0000
Pascal Thubert (pthubert) <pthubert@cisco.com> wrote: Rahul> I would like to confirm a point here... Reclaiming the turnon-8138 Rahul> flag in MOP>=7 would mean that 8138 is _mandatorily_ supported in Rahul> the nodes above MOP>=7 such that they no more depend on this Rahul> flag. This in itself is a bigger decision! Is my understanding Rahul> correct? While the advantages of 8138 are obvious in non-storing Rahul> MOP case, they are less impacting/obvious in storing MOP case. > The configuration bits can be reclaimed if the value is always-on or > always off for a new MOP. When defining a MOP, it is possible to > indicate either way and then to reclaim the bits. I see that MOPext > could say, individually for each bit: > a) For any MOP >= 7, the bit is implicitly always on (or off) unless > the MOP specification says otherwise ... > My preference goes to a), defaulting both settings to on. My rationale is this: I agree. -- ] Never tell me the odds! | ipv6 mesh networks [ ] Michael Richardson, Sandelman Software Works | IoT architect [ ] mcr@sandelman.ca http://www.sandelman.ca/ | ruby on rails [
- [Roll] signaling RPI option value and support of … Pascal Thubert (pthubert)
- Re: [Roll] signaling RPI option value and support… Michael Richardson
- Re: [Roll] signaling RPI option value and support… Abdussalam Baryun