Re: [manet] SMF in Manet and MPR

Philippe Jacquet <philippe.jacquet@inria.fr> Mon, 21 March 2022 16:02 UTC

Return-Path: <philippe.jacquet@inria.fr>
X-Original-To: manet@ietfa.amsl.com
Delivered-To: manet@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id A9E9B3A0D50 for <manet@ietfa.amsl.com>; Mon, 21 Mar 2022 09:02:18 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.107
X-Spam-Level:
X-Spam-Status: No, score=-2.107 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, RCVD_IN_MSPIKE_H4=0.001, RCVD_IN_MSPIKE_WL=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, T_SCC_BODY_TEXT_LINE=-0.01, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=inria.fr
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 VlkAjbMoYVvH for <manet@ietfa.amsl.com>; Mon, 21 Mar 2022 09:02:13 -0700 (PDT)
Received: from mail2-relais-roc.national.inria.fr (mail2-relais-roc.national.inria.fr [192.134.164.83]) (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 CE5973A196E for <manet@ietf.org>; Mon, 21 Mar 2022 09:02:12 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=inria.fr; s=dc; h=date:from:to:cc:message-id:in-reply-to:references: subject:mime-version:content-transfer-encoding; bh=s9OC3oFLYlqzKOAZ5PDgNQhta2peXM/YiIXqmD8bR78=; b=q215bPOhuWtdjLhzIonj6dqcT06DhBrHo925PVatXsvEQFUjLc2WfRA3 0dWGkxv79eV7fR3+AvEhRTgA3y1ezxPoHySxCU3xWcePtlHjzBytMv2+a V9a5pLA6uXAPt5TAACbAzf9IV7G8s2kw6IcX3j4gzKcGysAIDyu1Om9Z0 E=;
Authentication-Results: mail2-relais-roc.national.inria.fr; dkim=none (message not signed) header.i=none; spf=SoftFail smtp.mailfrom=philippe.jacquet@inria.fr; spf=None smtp.helo=postmaster@zcs-store4.inria.fr
Received-SPF: SoftFail (mail2-relais-roc.national.inria.fr: domain of philippe.jacquet@inria.fr is inclined to not designate 128.93.142.31 as permitted sender) identity=mailfrom; client-ip=128.93.142.31; receiver=mail2-relais-roc.national.inria.fr; envelope-from="philippe.jacquet@inria.fr"; x-sender="philippe.jacquet@inria.fr"; x-conformance=spf_only; x-record-type="v=spf1"; x-record-text="v=spf1 ip4:192.134.164.0/24 mx ~all"
Received-SPF: None (mail2-relais-roc.national.inria.fr: no sender authenticity information available from domain of postmaster@zcs-store4.inria.fr) identity=helo; client-ip=128.93.142.31; receiver=mail2-relais-roc.national.inria.fr; envelope-from="philippe.jacquet@inria.fr"; x-sender="postmaster@zcs-store4.inria.fr"; x-conformance=spf_only
X-IronPort-AV: E=Sophos;i="5.90,199,1643670000"; d="scan'208";a="27280020"
X-MGA-submission: MDH8RKhHePcvRQ/8/NS29Kz8nDKSB7/GIp/dff4ClTwjNpgMVQsROqfG3pPYN5g8lHi6ZesWHNrqRBaZD9b+1NVcsGNEbKLI+zB5iVzPZejadtHvi25cz5uhjRbTPa4ib00CEI65VrTjJb8xFEmIBouBR3gzZkd4+5T6nLw5atRVjQ==
Received: from zcs-store4.inria.fr ([128.93.142.31]) by mail2-relais-roc.national.inria.fr with ESMTP; 21 Mar 2022 17:02:09 +0100
Date: Mon, 21 Mar 2022 17:02:08 +0100
From: Philippe Jacquet <philippe.jacquet@inria.fr>
To: Henning Rogge <hrogge@gmail.com>
Cc: "manet@ietf.org IETF" <manet@ietf.org>
Message-ID: <944632927.6192671.1647878528946.JavaMail.zimbra@inria.fr>
In-Reply-To: <CAGnRvuoAdGeuzESf4VgYVB2xkEBX=t+3Vm4BMn0q37OKx9_jAQ@mail.gmail.com>
References: <CAGnRvuoAdGeuzESf4VgYVB2xkEBX=t+3Vm4BMn0q37OKx9_jAQ@mail.gmail.com>
MIME-Version: 1.0
Content-Type: text/plain; charset="ISO-8859-1"
Content-Transfer-Encoding: quoted-printable
X-Originating-IP: [92.94.249.180]
X-Mailer: Zimbra 8.8.15_GA_4203 (ZimbraWebClient - GC95 (Mac)/8.8.15_GA_4232)
Thread-Topic: SMF in Manet and MPR
Thread-Index: r7m9Gr9GHErd1LAxpIGM3c+A/Fu/fQ==
Archived-At: <https://mailarchive.ietf.org/arch/msg/manet/-PnaGWvA8iHJCDfMgnI8R5yZtdA>
Subject: Re: [manet] SMF in Manet and MPR
X-BeenThere: manet@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Mobile Ad-hoc Networks <manet.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/manet>, <mailto:manet-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/manet/>
List-Post: <mailto:manet@ietf.org>
List-Help: <mailto:manet-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/manet>, <mailto:manet-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 21 Mar 2022 16:02:19 -0000

I apologise that I didn't follow too much Manet these last years. As far as I remember the multiple interface MPR stuff with OLSRv2 were assuming that the interfaces were capable to support the topology control traffic, which was supposed to be the sole source of multicast traffic. But if the multicast traffic is demanding significant capacity, there were in the literature some efficient ways to select the MPR according to the demanded QoS. But this supposes that the traffic comes with QoS requirement TLS. 

I hope it helps,

Philippe

----- Mail original -----
De: "Henning Rogge" <hrogge@gmail.com>
À: "manet@ietf.org IETF" <manet@ietf.org>
Envoyé: Lundi 21 Mars 2022 14:06:39
Objet: [manet] SMF in Manet and MPR

Hi,

I am reacting to the talk during the IETF meeting (chat didn't worked
for me for some reason).

My trouble with the MPR optimization for SMF (and a bit with SMF in
general) is that we currently have no good MPR algorithm for
heterogeneous Manet (Manet with multiple different types of radios).

The only described MPR algorithm (OLSRv2 appendix) works separately
for each interface... which means it always selects MPRs on long-range
(and slow) interfaces, which is really not what we want.

Of course there is also the problem that SMF completely ignores
routing metrics... and the problem that we lack a good dataplane for
SMF, which often results in horrible "raw socket trickery"...

So in general I would not suggest to people using SMF because I have
yet to find an use-case where SMF is doing well. Often an
application-specific forwarding strategy is much better than a generic
IP one in terms of multicast in Manet.

Henning Rogge

_______________________________________________
manet mailing list
manet@ietf.org
https://www.ietf.org/mailman/listinfo/manet