Re: [manet] IETF 114 manet meeting presentation

"Adamson, Robert B CIV USN NRL (5592) Washington DC (USA)" <brian.adamson@nrl.navy.mil> Fri, 22 July 2022 13:44 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 40A4BC16ED11; Fri, 22 Jul 2022 06:44:46 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.104
X-Spam-Level:
X-Spam-Status: No, score=-2.104 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, RCVD_IN_DNSWL_BLOCKED=0.001, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, T_SCC_BODY_TEXT_LINE=-0.01, URIBL_BLOCKED=0.001, URIBL_DBL_BLOCKED_OPENDNS=0.001, URIBL_ZEN_BLOCKED_OPENDNS=0.001] autolearn=unavailable autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=nrl.navy.mil
Received: from mail.ietf.org ([50.223.129.194]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id OqlFWV58QTtw; Fri, 22 Jul 2022 06:44:41 -0700 (PDT)
Received: from mf.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 34192C16ED0E; Fri, 22 Jul 2022 06:44:40 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=nrl.navy.mil; h=from : to : cc : subject : date : message-id : content-type : mime-version; s=s2.dkim; bh=GsCXgZkE2EOK/mHoX/OqwqK7NpbXXlzdV29ipdE3REA=; b=KHTsUVqNdD9ztg3RyhDluVdEEiSrelqRzAYM90OgV20kzpHGisILhanbS+T96A+K7Qz4 MylUR76TPGnUxDgno1/DL9m80VOMAFV/O8Y3h8xEUo3Ct5Yc6MJwUiifBD4wAoQCN3OV Zh6ZRoWm7I1L4NV6uILaMFBs6l2Ud6W3ZU5lXJtiIQvKaRPVRPHcaZnRWUdAn2IvTU1D ormg9sMf+vJ9z7rm6Q77oRIX8/arII0R/CmmpgNhi71Cm701Uwc2ZQcatnKAuiyI/S5b 76gJ5A5hZ8CzslF64HV9C3/bGrRyyaWXFxov0SmRH0NIBW+sdycgq4DVlZ0G0R8tx+d2 Ig==
Received: from mail6.nrl.navy.mil (mail6.nrl.navy.mil [IPv6:2001:480:20:421:0:0:25:116]) by ppae.dren.mil (8.16.1.2/8.16.1.2) with ESMTPS id 26MDiTUh043314 (version=TLSv1.2 cipher=ECDHE-RSA-AES256-GCM-SHA384 bits=256 verify=NOT); Fri, 22 Jul 2022 13:44:29 GMT
Received: from G1950SRVB2101.WDC.GEN.NRL.NAVY.MIL (g1950srvb2101.wdc.gen.nrl.navy.mil [128.60.31.207]) by mail6.nrl.navy.mil (8.15.2/8.15.2) with ESMTPS id 26MDiSdU008598 (version=TLSv1.2 cipher=AES256-GCM-SHA384 bits=256 verify=OK); Fri, 22 Jul 2022 09:44:28 -0400
Received: from G1950SRVB2001.WDC.GEN.NRL.NAVY.MIL (2001:480:20:2031:31::201) by G1950SRVB2101.WDC.GEN.NRL.NAVY.MIL (2001:480:20:2031:31::207) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256) id 15.1.2507.9; Fri, 22 Jul 2022 09:44:28 -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%7]) with mapi id 15.01.2507.009; Fri, 22 Jul 2022 09:44:28 -0400
From: "Adamson, Robert B CIV USN NRL (5592) Washington DC (USA)" <brian.adamson@nrl.navy.mil>
To: "Velt, R. (Ronald) in 't" <Ronald.intVelt=40tno.nl@dmarc.ietf.org>, "Rogge, Henning" <henning.rogge@fkie.fraunhofer.de>, "manet@ietf.org" <manet@ietf.org>
CC: "manet-chairs@ietf.org" <manet-chairs@ietf.org>
Thread-Topic: [manet] IETF 114 manet meeting presentation
Thread-Index: AQHYndEpZvxu8duWykirXQvPNGCM3w==
Date: Fri, 22 Jul 2022 13:44:28 +0000
Message-ID: <04615795-09D5-4908-92FD-F247EC64DD3E@nrl.navy.mil>
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: multipart/alternative; boundary="_000_0461579509D5490892FDF247EC64DD3Enrlnavymil_"
MIME-Version: 1.0
X-Scanned-By: MIMEDefang 2.85 on 132.250.21.116
Archived-At: <https://mailarchive.ietf.org/arch/msg/manet/mdzXSCaQZJqTP1NmzAh_QCUNdSo>
Subject: Re: [manet] IETF 114 manet meeting presentation
X-BeenThere: manet@ietf.org
X-Mailman-Version: 2.1.39
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: Fri, 22 Jul 2022 13:44:46 -0000

Ron, Henning,

I am not sure if I can participate in the live meeting next week, but I could provide some information and even slides to Henning (if he’s interested)  on the nrlsmf data plane.  The current code has evolved a bit since we last presented an overview at an IETF meeting.   Or if you want to identify this as a possible future presentation if there’s interest let me know.

My current “go to” approach for the data/forwarding plane as a user-space process has been to use a combination of PF_PACKET socket (on Linux … other mechanisms on the other operating systems supported that includes MacOSX, Windows, Android, and other Unix platforms). and a Tun/Tap virtual interface with the protocols configured on the Tun/Tap interface.

This is a  topic of particular interest for me.  One thing I have been doing is more clearly separating the data/forwarding plane aspects of SMF/Elastic Multicast implementation from the control plane.  There are some events triggered by things that happen in the data plane (e.g., detection of multicast flow activity/inactivity) and part of the approach is achieve sufficient functionality while minimizing what happens in the forwarding plane and limiting the amount of interaction between the control plane and data plane.  Some of our work has included working with Open vSwitch (OvS) and I have been looking at this in the interest of what data/forwarding plane functionality could be embedded within OvS to support MANET multicast.   The idea would be then to have an option besides the user-space forwarding engine approach currently used.

Best regards,

Brian


From: manet <manet-bounces@ietf.org> on behalf of "Velt, R. (Ronald) in 't" <Ronald.intVelt=40tno.nl@dmarc.ietf.org>
Date: Friday, July 22, 2022 at 5:19 AM
To: "Rogge, Henning" <henning.rogge@fkie.fraunhofer.de>, "manet@ietf.org" <manet@ietf.org>
Cc: "manet-chairs@ietf.org" <manet-chairs@ietf.org>
Subject: Re: [manet] IETF 114 manet meeting presentation

Hi Henning,

That would certainly be a useful contribution to our session, in my opinion. I checked with the chairs of the other groups: there was positive feedback from Donald Eastlake and silence from the ROLL chairs (which we will interpret as approval 😊 How much time do you think you need? I’ll adapt the agenda accordingly once I get to Philly. (Am travelling today).

Thanks!
Ronald

From: manet <manet-bounces@ietf.org> On Behalf Of Rogge, Henning
Sent: donderdag 21 juli 2022 15:44
To: manet@ietf.org
Cc: manet-chairs@ietf.org
Subject: [manet] IETF 114 manet meeting presentation

Hello,

I will be attending (online) the IETF 114 MANET meeting and would like to give a short presentation about the practical problems of multicast routing.

A “how the hell should we do the data-plane” talk.

I know, it’s in theory and implementation issue and not a protocol one, but I think it is a VERY relevant problem for MANET, because there is no good solution on Linux (which is often and widely used for MANET implementations) and I worry that other operation systems have similar issues.

In the end, if the data-plane is bad, nobody will use any protocol we talk about.

Henning Rogge

This message may contain information that is not intended for you. If you are not the addressee or if this message was sent to you by mistake, you are requested to inform the sender and delete the message. TNO accepts no liability for the content of this e-mail, for the manner in which you use it and for damage of any kind resulting from the risks inherent to the electronic transmission of messages.