Re: [Roll] NSA PS-set metric/constraint

Remous-Aris Koutsiamanis <> Fri, 06 March 2020 15:59 UTC

Return-Path: <>
Received: from localhost (localhost []) by (Postfix) with ESMTP id C411C3A0A05 for <>; Fri, 6 Mar 2020 07:59:06 -0800 (PST)
X-Virus-Scanned: amavisd-new at
X-Spam-Flag: NO
X-Spam-Score: -2.098
X-Spam-Status: No, score=-2.098 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, HTML_MESSAGE=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: (amavisd-new); dkim=pass (2048-bit key) header.b=FzjgEYEr; dkim=pass (2048-bit key) header.b=DsJZM/nG
Received: from ([]) by localhost ( []) (amavisd-new, port 10024) with ESMTP id EHlMb5vcAbuF for <>; Fri, 6 Mar 2020 07:59:04 -0800 (PST)
Received: from ( []) (using TLSv1.2 with cipher ADH-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by (Postfix) with ESMTPS id C30953A0A46 for <>; Fri, 6 Mar 2020 07:59:03 -0800 (PST)
Received: from ( []) by (Postfix) with ESMTP id C571C2D09 for <>; Fri, 6 Mar 2020 16:59:00 +0100 (CET)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;; s=20160819-nLV10XS2; t=1583510340; bh=BpVGvjDbkYtpZAqKeS4TdhA0/gqu2TYfNGyaPbHSzgE=; h=References:In-Reply-To:From:Date:Subject:To:Cc:From; b=FzjgEYErGqIfHb1oAs9AdKwot6lcbhe0MjLNgAG7xsN/w0ZgIC8p8dj+F1RtXLwqL 68LfapsZUkRMi4GZaETDs83Am/1zj2Bs/jRFHMLHE7pP2/zQ0YnayidS318R/HRBFP 6uZRnXO4jhpKKGDNB7Qv3jg26WnzHCygKlagLAuircAs1LUosrw0/5yxJaYvW3TLKf PxIH0n7tiCm+atLLfalLEpJp8jBaC3ecAPvoPi13UHHlecEjfMjrapunkysN1x5W3U iazTmkgpcEY81BFwiKFUp13sUtEsV7K3yly5DoxDCnee9A0TjLuSmEN5LfzYq6gl4F uE6arB0VgQnuQ==
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; t=1583510340; s=20191001-wvim;;; h=MIME-Version:References:In-Reply-To:From:Date:Message-ID:Subject:To:Cc:Content-Type; l=5093; bh=BpVGvjDbkYtpZAqKeS4TdhA0/gqu2TYfNGyaPbHSzgE=; b=DsJZM/nGNzwaMnzhMEJZL9N8oj9BWA4tbPLvtQjK6qiWsmsZPUxMNXOKTeomL/mM Pfw9jyv9/UNumZAF/JyzHxZFB64yejQQJ7XidTjvACKFps+8X63a0NI2iOnA/LAZvYl H+vPIq9LmufJJPqH6uByudJhKVBQZNgPVZ2VmxH+3O7+Ts/kLBdIelVzrD8iFf8o3ae UyNBf9UyJyufUfwj7kFAitSJXEddw5O4T94RGt7rsg0YJQjriXH7PPydUs0PAnDp8Pp G+ESXq4amB8OEUX7QXx3IomulS+IOTMy7tDmJHTFvbeP3iOg/rQYnZ/wa+VASdpxrNZ jnNdH1rwUA==
Received: by with ESMTPA for <> ; Fri, 6 Mar 2020 16:58:55 +0100 (CET)
Received: by with SMTP id d8so2546531ion.7 for <>; Fri, 06 Mar 2020 07:58:55 -0800 (PST)
X-Gm-Message-State: ANhLgQ1WwOuYGNTrLTAUxycxDeX6A741iq42c8TXY7I+D4Sn1xL9hfwY vqI5So6yALNvRPQXcXnbMxqccrEkK5UwYJKacq8=
X-Google-Smtp-Source: ADFU+vtIncQoyBI0NrUsx9b8SZlgVITaTSzRK/sg0HlLX4XsvK45Z/Y/6Lv/Lbd/ENEH4IgS2MduFXsdg8og+KMKu6I=
X-Received: by 2002:a02:a412:: with SMTP id c18mr3809224jal.69.1583510331233; Fri, 06 Mar 2020 07:58:51 -0800 (PST)
MIME-Version: 1.0
References: <> <> <> <>
In-Reply-To: <>
From: Remous-Aris Koutsiamanis <>
Date: Fri, 06 Mar 2020 16:58:57 +0100
X-Gmail-Original-Message-ID: <>
Message-ID: <>
To: dominique barthel <>
Cc: "Georgios Z. Papadopoulos" <>, roll <>
Content-Type: multipart/alternative; boundary="000000000000ca9ba305a031ba4d"
X-ContactOffice-Account: com:113819248
Archived-At: <>
Subject: Re: [Roll] NSA PS-set metric/constraint
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Routing Over Low power and Lossy networks <>
List-Unsubscribe: <>, <>
List-Archive: <>
List-Post: <>
List-Help: <>
List-Subscribe: <>, <>
X-List-Received-Date: Fri, 06 Mar 2020 15:59:14 -0000

Hello Dominique,

sorry to bother you in a probably very busy period.
To finalise our draft before the cutoff, we're waiting for a brief answer
from you on this previous question:

On Sat, Feb 29, 2020 at 12:51 AM Remous-Aris Koutsiamanis <>

> [DP] Alternate proposal:
>> Could the PS be part of an NSA Metric? After all, it is used to help
>> select which parent(s) are best suited for upward routing, not to prune
>> downlink propagation of the DIO along a path that exceed some metric
>> value. C=0, R=1, P=1 comes to mind for this metric.
> [ARIS]
So I read a bit more about this. So C=0 means "use as a routing metric", OK.
> R=1 means "use as a recorded metric", i.e. not aggregated, because
> aggregated makes no sense, OK.
> Now, P=1 means that one or more of the nodes on the path did not record
> the metric. So, it's less a "command" and more a report of previous
> behaviour.
> My question is: it seems impossible that *all* the parent sets can be
> recorded along the path due to size, so each node *replaces* the received
> parent set with it's own.
> We can specify this with text of course, but I have not seen another
> existing metric that behaves like this.
> On the other hand, the NSA metric object is not used a lot, and if it
> makes sense for any metric to be replaced rather then appended to a list of
> metrics, that metric would be NSA.
> I am not sure about that P=1 part though and how it relates to replacing
> the existing metrics.
> If I understand this correctly, a node reporting it's own parent set in
> the NSA will set P=1 basically to let the receiving nodes know that they
> should not expect to find inside all the metric along the whole path, but
> only a part of it, and in our case from just the sending node.
> Am I getting this right?