From nobody Sun Jul 24 02:10:40 2022 Return-Path: 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 41BF0C14F739; Sun, 24 Jul 2022 02:10:39 -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, FREEMAIL_FROM=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] autolearn=ham autolearn_force=no Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com 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 EAdHN_3hRJrR; Sun, 24 Jul 2022 02:10:38 -0700 (PDT) Received: from mail-oi1-x234.google.com (mail-oi1-x234.google.com [IPv6:2607:f8b0:4864:20::234]) (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits) server-digest SHA256) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id C56E6C14F72A; Sun, 24 Jul 2022 02:10:38 -0700 (PDT) Received: by mail-oi1-x234.google.com with SMTP id u9so10144979oiv.12; Sun, 24 Jul 2022 02:10:38 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20210112; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc:content-transfer-encoding; bh=FKC/AIRE7T3QNypDsdrCrTPJGcRDuradhRoKJ5TGz1A=; b=loKxcS9fXDaIBhGCZHvK1hxgegyVb1QgDhqRqhQPIQ97eQeW6JjFq3a8cdZhQ/m2UJ 4AIEviKPZQd0fsmoaQonX5rURudPEXaflvqqEnCu1pJ9iFPJzjhQ+dDoJUiW4UWXBSWp 781u92+fVamPwjOQlwLMP1KFX0whkY9Lz9b3ss2xJeAE9KGx5NjTC+LtPaLLowJX58l3 RLKQ1jE3sbGf6HjCbVSHYUTfsL92fe1HBu4asJx1IbaVmp6CA+gxnfs6oaN1hYyZLQW+ vZM/hHKd+ilFIkOskIClv6kLNx+48ggFWPIEg9V0sMf8kPIVkRf8mRBffNsEAXjcPjXb b6Tw== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc:content-transfer-encoding; bh=FKC/AIRE7T3QNypDsdrCrTPJGcRDuradhRoKJ5TGz1A=; b=5F/BjroUogmDzyFWrCWGYAu7bo30fS7jxGgA/WQcwSdTdz7is0zvqd0ui+CH3uIxL4 Vaz4NY62Z3e3WBC2ZoPmHzrCun2II99QF/3i+5E24DaxrHrktODX2DfmbnAQbK6HVjym zsmvfYy0gEkAT3DSnXWchtcYRe1d3VTW7sx8nC16NGjk/SdZyDgpQXGWHJBgJYZZiaLV ZWr2yNBENEvQPSZkmiHjEiUEnwzgAn59agyPn5JDT5X43rCAvztQ1F/cbnofSXwdlPuK 35s75HZMZjwrFMt9wr6573LhP7nOGoIEWYfbLeccsrI7K+abcz9tbtgJWwrbfY7qLYpr L8TQ== X-Gm-Message-State: AJIora823ALBLZ69rhw3Vri51nQnUhhDRcScCZGtGAJGRv+h3UgVcHdP p1EhEszb5QQ1NM1/Ibp9RBl1ABdJEfgDo0F6nh4HWZxJ X-Google-Smtp-Source: AGRyM1sWNIb+pUlMWIjnvjqSTTaUjqvPNz0jjfHsgYLAxHdPBv3a9BTQO/NRYjJ4M63Y46yPtjXnBfot2XvHtzFpkwI= X-Received: by 2002:a05:6808:152c:b0:33a:bf39:a8bd with SMTP id u44-20020a056808152c00b0033abf39a8bdmr3140628oiw.164.1658653837971; Sun, 24 Jul 2022 02:10:37 -0700 (PDT) MIME-Version: 1.0 References: <04615795-09D5-4908-92FD-F247EC64DD3E@nrl.navy.mil> In-Reply-To: <04615795-09D5-4908-92FD-F247EC64DD3E@nrl.navy.mil> From: Henning Rogge Date: Sun, 24 Jul 2022 11:10:13 +0200 Message-ID: To: "Adamson, Robert B CIV USN NRL (5592) Washington DC (USA)" Cc: "Velt, R. (Ronald) in 't" , "Rogge, Henning" , "manet@ietf.org" , "manet-chairs@ietf.org" Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable Archived-At: 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 List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 24 Jul 2022 09:10:39 -0000 On Fri, Jul 22, 2022 at 3:44 PM Adamson, Robert B CIV USN NRL (5592) Washington DC (USA) wrote: > > Ron, Henning, > > I am not sure if I can participate in the live meeting next week, but I c= ould provide some information and even slides to Henning (if he=E2=80=99s i= nterested) on the nrlsmf data plane. The current code has evolved a bit s= ince we last presented an overview at an IETF meeting. Or if you want to = identify this as a possible future presentation if there=E2=80=99s interest= let me know. I think some information about how SMF its doing the data plane would be interesting, I am just not sure if I could present your way how to implement it. > My current =E2=80=9Cgo to=E2=80=9D approach for the data/forwarding plane= as a user-space process has been to use a combination of PF_PACKET socket = (on Linux =E2=80=A6 other mechanisms on the other operating systems support= ed that includes MacOSX, Windows, Android, and other Unix platforms). and a= Tun/Tap virtual interface with the protocols configured on the Tun/Tap int= erface. Tun/Tap can be a great alternative to PF_PACKET sockets... especially because they play much nicer with complicated network setups, e.g. policy routing. > This is a topic of particular interest for me. One thing I have been do= ing is more clearly separating the data/forwarding plane aspects of SMF/Ela= stic Multicast implementation from the control plane. There are some event= s triggered by things that happen in the data plane (e.g., detection of mul= ticast flow activity/inactivity) and part of the approach is achieve suffic= ient functionality while minimizing what happens in the forwarding plane an= d limiting the amount of interaction between the control plane and data pla= ne. Some of our work has included working with Open vSwitch (OvS) and I ha= ve been looking at this in the interest of what data/forwarding plane funct= ionality could be embedded within OvS to support MANET multicast. The ide= a would be then to have an option besides the user-space forwarding engine = approach currently used. Has anyone ever tried to use EBPF to implement a hash-based duplicate detec= tor? > From: manet on behalf of "Velt, R. (Ronald) in '= t" > Date: Friday, July 22, 2022 at 5:19 AM > To: "Rogge, Henning" , "manet@ietf.org"= > Cc: "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 opini= on. I checked with the chairs of the other groups: there was positive feedb= ack from Donald Eastlake and silence from the ROLL chairs (which we will in= terpret as approval =F0=9F=98=8A How much time do you think you need? I=E2= =80=99ll adapt the agenda accordingly once I get to Philly. (Am travelling = today). I would like to keep the talk short, but I have yet to finalize the talk. Henning Rogge