Re: [babel] BABEL / MANET / ROLL and multicast

David Schinazi <dschinazi.ietf@gmail.com> Mon, 02 May 2022 19:22 UTC

Return-Path: <dschinazi.ietf@gmail.com>
X-Original-To: babel@ietfa.amsl.com
Delivered-To: babel@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id B34D4C14F740; Mon, 2 May 2022 12:22:41 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.097
X-Spam-Level:
X-Spam-Status: No, score=-1.097 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, FREEMAIL_REPLY=1, HTML_MESSAGE=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=no 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 qV0DkUYFIvtz; Mon, 2 May 2022 12:22:38 -0700 (PDT)
Received: from mail-pl1-x630.google.com (mail-pl1-x630.google.com [IPv6:2607:f8b0:4864:20::630]) (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 EFBC1C14EB1F; Mon, 2 May 2022 12:22:37 -0700 (PDT)
Received: by mail-pl1-x630.google.com with SMTP id x18so2053601plg.6; Mon, 02 May 2022 12:22:37 -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; bh=rLotNjT+nm9aQspHjCjsy1MjdNGK+8aAtjfGwg6HEeA=; b=JTqytPDkxpytDZv3dutqM+bn/O/fLF04kZxTegDWBymcuY0rX/9ONb7HWo6Bl8KIm2 7UzIOttn07LOGVRf/WMfTx8Jret27tLoCx0kQOQ/2En3khHmFvnCmzIwFprzJfE10z/c hV117mU/spZBCgi3qmLKjfaSmVz4iNGFX8p0UVPlQUqZDunJgsvXBCI7rAidRUqE9adq 7KGp5f00kUX/Ua/0Zfu7T7WLS4jO3ohlvP7YmMR/PBQrNVAeGBQbb925YP6zgYPdObmI 5+b6wstM2uAzLGnrLoy7BWMZ9D2Celb2xJkw2/n37AEGQ/4Cw/oLkfathMUCe0uPwZ3I j6VQ==
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; bh=rLotNjT+nm9aQspHjCjsy1MjdNGK+8aAtjfGwg6HEeA=; b=iHRZtpIEtnAxbZ5CmxCYZAFlXMyeKS3FcODmnVfMdwaD9KDrJ5AshD1F1EDPDj/jwc xNLK35+NchaDTMGPk+H79TpfLOXrGQYIDKjsL8vrfzawZJ2BlBHImFDcHZs+EISv8EEj g8F3ibHk2xIFIlWCMZgrb4I4WoNJonsRc1rwKJdiWLMfAGplQ2/d9poMdULvx05p4Ds/ TqyVrCFUYnnNc4V48tgv7SJOyF+KZGT/jQURifaAFfDRfGl/e/LltN81Ma0LO+cRIwbr vNK1mn5p+4WA9dF1EkgQt3yOT92UMnn95p1+gDsen4jO/s0S2ZgX52pTd1cKHhiMMi6c a/GQ==
X-Gm-Message-State: AOAM531dTYeVEdIWBg/lbOZw0XdNaNsx4YrvxhLT+0BtzX7EyNyDgODj 4h73D78+clmUUdCJmQdaGYtATos1LrDlFPiHVdkyF5aP
X-Google-Smtp-Source: ABdhPJx/PQoNtnvWviLY/XKdQP3h6HjPFBoQZmPCIhjjOVAUK6kbMVJduPgGJIGyeV+0YvMWV9R7Tq3qhPL0czKNf00=
X-Received: by 2002:a17:90a:a58d:b0:1db:ed34:e46d with SMTP id b13-20020a17090aa58d00b001dbed34e46dmr751007pjq.124.1651519357167; Mon, 02 May 2022 12:22:37 -0700 (PDT)
MIME-Version: 1.0
References: <CAF4+nEFo4-XRhMLGHe-BaFferQ6pPNVHK7Ve7qA8se+fC4DECw@mail.gmail.com>
In-Reply-To: <CAF4+nEFo4-XRhMLGHe-BaFferQ6pPNVHK7Ve7qA8se+fC4DECw@mail.gmail.com>
From: David Schinazi <dschinazi.ietf@gmail.com>
Date: Mon, 02 May 2022 12:22:26 -0700
Message-ID: <CAPDSy+5voFRf8j=kHhetxsiRRHAF00YjsRnCOh7kRB5cmF6gbg@mail.gmail.com>
To: Donald Eastlake <d3e3e3@gmail.com>
Cc: Babel at IETF <babel@ietf.org>, babel-chairs <babel-chairs@ietf.org>
Content-Type: multipart/alternative; boundary="0000000000009fac9205de0c50ba"
Archived-At: <https://mailarchive.ietf.org/arch/msg/babel/6NsqrtzZ9fJolD_m84dLodbPYAg>
Subject: Re: [babel] BABEL / MANET / ROLL and multicast
X-BeenThere: babel@ietf.org
X-Mailman-Version: 2.1.34
Precedence: list
List-Id: "A list for discussion of the Babel Routing Protocol." <babel.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/babel>, <mailto:babel-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/babel/>
List-Post: <mailto:babel@ietf.org>
List-Help: <mailto:babel-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/babel>, <mailto:babel-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 02 May 2022 19:22:41 -0000

Out of curiosity, what's the use-case for using multicast over a mesh
network?
When it comes to device/service discovery, we've found that a unicast-based
register/query model is much more reliable and wire-efficient.
David

On Thu, Apr 28, 2022 at 8:15 PM Donald Eastlake <d3e3e3@gmail.com> wrote:

> Hi,
>
> During the last IETF meeting I spoke with the Routing Area ADs and there
> was a suggestion that we might look into having a joint BABEL / MANET /
> ROLL WG meeting on the topic of multicast. All three Working Groups, BABEL,
> MANET, and ROLL, have considered multicast but not made much progress in
> that direction.
>
> If there is interest in this, I can contact the chairs of MANET and ROLL
> to see about scheduling a joint session for the next IETF meeting which
> will be July 25-29. (That meeting will be in Philadelphia but as usual,
> remote participation will be reasonably convenient.) Of course, if the WGs
> can't come up with a reasonable number of presentations, no joint meeting
> would be held.
>
> Thanks,
> Donald
> ===============================
>  Donald E. Eastlake 3rd   +1-508-333-2270 (cell)
>  2386 Panoramic Circle, Apopka, FL 32703 USA
>  d3e3e3@gmail.com
> _______________________________________________
> babel mailing list
> babel@ietf.org
> https://www.ietf.org/mailman/listinfo/babel
>