Re: [manet] SMF in Manet and MPR

"Adamson, Robert B CIV USN NRL (5522) Washington DC (USA)" <brian.adamson@nrl.navy.mil> Mon, 21 March 2022 13:28 UTC

Return-Path: <brian.adamson@nrl.navy.mil>
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 65C6B3A12B7 for <manet@ietfa.amsl.com>; Mon, 21 Mar 2022 06:28:50 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.108
X-Spam-Level:
X-Spam-Status: No, score=-2.108 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_DNSWL_BLOCKED=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 (2048-bit key) header.d=nrl.navy.mil header.b=mVpB0Ufp; dkim=pass (1024-bit key) header.d=nrl.navy.mil header.b=0St9rRBN
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 DmFuRBXR7hBg for <manet@ietfa.amsl.com>; Mon, 21 Mar 2022 06:28:44 -0700 (PDT)
Received: from mfe.dren.mil (mfe.dren.mil [IPv6:2001:480:a0:f003::234]) (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 42BCD3A1AAB for <manet@ietf.org>; Mon, 21 Mar 2022 06:28:35 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=nrl.navy.mil; h=from : to : subject : date : message-id : references : in-reply-to : content-type : content-id : content-transfer-encoding : mime-version; s=s2.dkim; bh=/RMAoQ55ENaJ8vbpTzpzgXgXR1q7Sr7aFONdcTmDxRg=; b=mVpB0Ufp5jeNrAVs/axxyzjb188BblDrZn7h/GGK/Uhxyu4gg5Fm6Gcb5VDgFxCr+8L6 pCyt6s17JEFfgUR5CcKlKomy/bZ88z4uYEYeGltt+GcZo1hwsXrzFgLOcXIoqDOF6GV5 xGAaNa6ID6bVzqA6xMCInBUpUDoc4QfvjtDkyjR7W9BpavbVWBPS+7DgHu5OV8znJXOB dfA7JwhMyebwQzlTpUkD3o99mQeKu9oRzNssSrdlrw6DnAzFkIlKlHmgjvnHPFsMCWzt 7VqRIYs49U2pVt9Xe7BGag42dVtXrXy5bxHLLyRigaAsVIZq6HSIxaAyOynIh6nZ8juf Gw==
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=nrl.navy.mil; h=from : to : subject : date : message-id : references : in-reply-to : content-type : content-id : content-transfer-encoding : mime-version; s=s1.dkim; bh=/RMAoQ55ENaJ8vbpTzpzgXgXR1q7Sr7aFONdcTmDxRg=; b=0St9rRBNxwjEjgzaSrLuPuFO+/QTo6W15NxSTfhudBVGQSOkEcCh+VeqU2QpynbNC2ev 0E213bWucAK6GHCLbFSePGSzCOvHp9Wl2F93cLcyq3oBYbr+STyFkOsVKWfAr+xiPeUJ T/Kwb+nADK98mwyUIc9ZiMrA3c2brJLmE4I=
Received: from pps.reinject (ppae.dren.mil [127.0.0.1]) by ppae.dren.mil (8.16.1.2/8.16.1.2) with ESMTPS id 22LDSXAd013157 (version=TLSv1.2 cipher=ECDHE-RSA-AES256-GCM-SHA384 bits=256 verify=NOT) for <manet@ietf.org>; Mon, 21 Mar 2022 13:28:33 GMT
Received: from ppae.dren.mil (ppae.dren.mil [127.0.0.1]) by pps.reinject (8.16.0.36/8.16.0.36) with SMTP id 22LDSX5J013150 for <manet@ietf.org>; Mon, 21 Mar 2022 13:28:33 GMT
Received: from mail5.nrl.navy.mil (mail5.nrl.navy.mil [IPv6:2001:480:20:404:0:0:25:114]) by ppae.dren.mil with ESMTP id 22LDSXBD013145 (version=TLSv1.2 cipher=ECDHE-RSA-AES256-GCM-SHA384 bits=256 verify=NOT); Mon, 21 Mar 2022 13:28:33 +0000
Received: from G1950SRVB2003.WDC.GEN.NRL.NAVY.MIL (g1950srvb2003.wdc.gen.nrl.navy.mil [128.60.31.203]) by mail5.nrl.navy.mil (8.15.2/8.15.2) with ESMTPS id 22LDSW1n026063 (version=TLSv1.2 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=OK); Mon, 21 Mar 2022 09:28:32 -0400
Received: from G1950SRVB2001.WDC.GEN.NRL.NAVY.MIL (2001:480:20:2031:31::201) by G1950SRVB2003.WDC.GEN.NRL.NAVY.MIL (2001:480:20:2031:31::203) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.1.2375.24; Mon, 21 Mar 2022 09:28:32 -0400
Received: from G1950SRVB2001.WDC.GEN.NRL.NAVY.MIL ([fe80::d1d8:a0fa:8863:95de]) by G1950SRVB2001.WDC.GEN.NRL.NAVY.MIL ([fe80::d1d8:a0fa:8863:95de%13]) with mapi id 15.01.2375.024; Mon, 21 Mar 2022 09:28:31 -0400
From: "Adamson, Robert B CIV USN NRL (5522) Washington DC (USA)" <brian.adamson@nrl.navy.mil>
To: Henning Rogge <hrogge@gmail.com>, MANET IETF <manet@ietf.org>
Thread-Topic: [manet] SMF in Manet and MPR
Thread-Index: AQHYPSTQCD60RkpF20SdK2Cx/swfeKzJ1NIA
Date: Mon, 21 Mar 2022 13:28:31 +0000
Message-ID: <34F68A6F-F4A3-4B9C-A4DD-549246154F67@nrl.navy.mil>
References: <CAGnRvuoAdGeuzESf4VgYVB2xkEBX=t+3Vm4BMn0q37OKx9_jAQ@mail.gmail.com>
In-Reply-To: <CAGnRvuoAdGeuzESf4VgYVB2xkEBX=t+3Vm4BMn0q37OKx9_jAQ@mail.gmail.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [128.60.31.173]
Content-Type: text/plain; charset="utf-8"
Content-ID: <332A6E01572E8948BE3A3840CCC76F8E@mail.nrl.navy.mil>
Content-Transfer-Encoding: base64
MIME-Version: 1.0
X-Scanned-By: MIMEDefang 2.84 on 132.250.4.114
Archived-At: <https://mailarchive.ietf.org/arch/msg/manet/ObDwtGsph8-gr3FtpXYFtmHUMYw>
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 13:28:51 -0000

Hi Henning,

I didn't participate in the discussion you mention but agree that heterogenous MANET is particularly challenging for multicast.  SMF by itself with distributed CDS relay set formation can't optimize (or even approximate it well) without multi-hop signaling.  I have been continuing to experiment (part time as I have opportunity) with the Elastic Multicast concept we presented several years ago.  The current "nrlsmf" implementation includes a variety of Elastic Multicast operating modes.  One of those use the an Elastic Multicast flow advertisement (EM_ADV) message that propagates from multicast sources and builds up an ETX path metric that can be used by "downstream" nodes (and/or receivers) to select (and acknowledge via EM_ACK messages) upstream relays according to that metric.  I also plan to extend the code to support advertising the maximum supportable path bandwidth (and possibly even RTT) for flows in that signaling including report back to the source of available path bandwidth.   That would allow for other metrics to be used in the forwarding tree/mesh selection.  This quickly gets into the application-specific domain if imagine how that information could be used.  It does seem there could be benefit for multiple applications being able leverage a common, underlying signaling approach like this.  Even though my code does not yet use PACKET BB (I was lazy on that while I'm still figuring out what meaningful information signaling messages should include), that could be done and integrated as an add-on to existing MANET signaling.  I.e., as opposed to each application implementing its own independent signaling.

Best regards,

Brian

On 3/21/22, 9:08 AM, "manet on behalf of Henning Rogge" <manet-bounces@ietf.org on behalf of hrogge@gmail.com> wrote:

    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