Re: [manet] special MANET broadcast addresses?

Christopher Dearlove <christopher.dearlove@gmail.com> Thu, 02 February 2023 02:31 UTC

Return-Path: <christopher.dearlove@gmail.com>
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 46438C1516F2 for <manet@ietfa.amsl.com>; Wed, 1 Feb 2023 18:31:38 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.095
X-Spam-Level:
X-Spam-Status: No, score=-2.095 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, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_DBL_BLOCKED_OPENDNS=0.001, URIBL_ZEN_BLOCKED_OPENDNS=0.001] 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 TE4lBeDnUdpQ for <manet@ietfa.amsl.com>; Wed, 1 Feb 2023 18:31:33 -0800 (PST)
Received: from mail-ed1-x536.google.com (mail-ed1-x536.google.com [IPv6:2a00:1450:4864:20::536]) (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 CCF6CC151551 for <manet@ietf.org>; Wed, 1 Feb 2023 18:31:33 -0800 (PST)
Received: by mail-ed1-x536.google.com with SMTP id fi26so645929edb.7 for <manet@ietf.org>; Wed, 01 Feb 2023 18:31:33 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20210112; h=references:to:cc:in-reply-to:date:subject:mime-version:message-id :from:from:to:cc:subject:date:message-id:reply-to; bh=AEE6GxF19coRIQB8KYKbd8MliCCHhcw7axa0UtL896U=; b=ZUhMfWMSYEvDrlpgfhT0mgBQcgSuNqF3yBcXj55YP5pfRpnjyMBNJ+s6R8Ka8M1z0W XyBk4KBGFRlePhTfS1LSxVTBNOAtdSkvMcEdC0phnqGX/9Ev50d0z4cfrcbETojNAOVP heHZjC+Jd0uNaViJdAzcaw+VjW5IJp64HEPz5NUsNzn2uouuew6kBLem+nxT+exr4kr5 mk6G8aQ/WsbrZJcKOxYWUJIGreswb/Y59lvwoZ3weU0JmkJdnH0B/0+faXzf1fX/1t9l ps/B++J/BjuPz1EC3AqhcJdkl3hMIj4ESfMmuRohMk7WJEfrVQDP8D1oLpsECoYr8DVZ d3yQ==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=references:to:cc:in-reply-to:date:subject:mime-version:message-id :from:x-gm-message-state:from:to:cc:subject:date:message-id:reply-to; bh=AEE6GxF19coRIQB8KYKbd8MliCCHhcw7axa0UtL896U=; b=08KtLIr30/f0b5ZG69kW6HtcOEge5ocuuDyVXfiZ3qMpdvWfz2dhbdNP+sfEO0IfkY aGTW0yYp1143VXjkBAOFbRilxdME4GEfeHI0W4+t6kDNy+1Q35fxczSrUZxcL5jZRm/7 LSbDZocWf2yAOda5QPh83b14qStz+GPPcNpXALKSnmWj1hajtbKbXHjEOHcpNKaFcjka yGZovb/fxH5jPVT5SqtqP3AHyNoWzjlSYv2A4kf2HyaS4isE43PZki3AbNeoWKgpJx5P zENL+LJrE0N6zjmrb3fT3xiiCo/0Xhqhsd+bHCw36SK1QcmFppeYvmKJ+NYPH1rY+cFO akbA==
X-Gm-Message-State: AO0yUKXNj+WDdVgSuRn3KfXxTodxT8aWbO6HRJFJeb84Fc+C3/eCACzN fdd7hcloh2uIcoZPhovq0dvZGnR8f9A=
X-Google-Smtp-Source: AK7set/JF6sU1lUkD4F9dkhOkh9obhasbeFOxFj7OZDmiOU5LzZ4oJbxLk+y4Kn+Tq+moYG3+OMLgQ==
X-Received: by 2002:a05:6402:2997:b0:46c:e558:ce60 with SMTP id eq23-20020a056402299700b0046ce558ce60mr5208771edb.22.1675305091618; Wed, 01 Feb 2023 18:31:31 -0800 (PST)
Received: from smtpclient.apple (82-132-227-87.dab.02.net. [82.132.227.87]) by smtp.gmail.com with ESMTPSA id bm3-20020a170906c04300b0087bd3ed8555sm9385938ejb.27.2023.02.01.18.31.30 (version=TLS1_2 cipher=ECDHE-ECDSA-AES128-GCM-SHA256 bits=128/128); Wed, 01 Feb 2023 18:31:31 -0800 (PST)
From: Christopher Dearlove <christopher.dearlove@gmail.com>
Message-Id: <DB490225-E8B0-4F03-A143-DF68DEFA7344@gmail.com>
Content-Type: multipart/alternative; boundary="Apple-Mail=_7318817E-D169-4437-94C0-D4AE8A13236E"
Mime-Version: 1.0 (Mac OS X Mail 16.0 \(3731.300.101.1.3\))
Date: Thu, 02 Feb 2023 02:31:17 +0000
In-Reply-To: <PH1P110MB1148ECEF5380A5442F43B3F0B0D69@PH1P110MB1148.NAMP110.PROD.OUTLOOK.COM>
Cc: "manet@ietf.org" <manet@ietf.org>
To: "Stevens, Jim A Collins" <James.A.Stevens=40collins.com@dmarc.ietf.org>
References: <PH1P110MB1148ECEF5380A5442F43B3F0B0D69@PH1P110MB1148.NAMP110.PROD.OUTLOOK.COM>
X-Mailer: Apple Mail (2.3731.300.101.1.3)
Archived-At: <https://mailarchive.ietf.org/arch/msg/manet/hxuMdVcYfpWHHY7amBTRiPFEwu0>
Subject: Re: [manet] special MANET broadcast addresses?
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: Thu, 02 Feb 2023 02:31:38 -0000

Have you looked at the address defined in RFC 5498? It’s not exactly what you’re asking for, but it might be part of a solution.

> On 2 Feb 2023, at 01:19, Stevens, Jim A Collins <James.A.Stevens=40collins.com@dmarc.ietf.org> wrote:
> 
> I am working on a multihop MANET network protocol design where the MANET radios can be one or more RF hops from each other.  There can be multiple hosts connected to the MANET radios at each MANET platform (vehicle) – either directly via ethernet or via a router connected to the MANET radio.  
>  
> Two of the desired services of this MANET network are
> for applications in a host at one MANET platform to send packets to hosts at platforms of MANET radios that are one-RF-hop away from the source’s MANET radio (called “One-RF-hop-cast”) and
> for applications in a host at one MANET platform to send packets to hosts at platforms of all the other MANET radios. (called “All-RF-cast”)
>  
> We can’t address these two services using IP link-local broadcast (255.255.255.255) or directed subnet broadcast because the hosts could be in different IP subnets at the different MANET platforms.
>  
> Thus, we are planning to define two IP multicast addresses to indicate these two services.  One multicast to go to hosts connected to radios one-RF hop away via the MANET network and one multicast address to go to all hosts connected to the MANET network.
>  
> We can have two choices for defining those multicast addresses
> define two addresses from the Administratively Scoped Multicast Space defined in RFCs 2365 and 5771 or
> request two global multicast addresses from IANA  (probably from Ad Hoc Block 1 defined in RFC 5771).
>  
> Questions
> are there any other MANET networks/protocols today that do something like this?  If yes, how do they indicate the desire for these two services?
> are these two services general enough that they should become a global service that is available in other MANET networks/protocols than the one I am working on?
>  
> Thanks
> Jim Stevens
>  
> _______________________________________________
> manet mailing list
> manet@ietf.org <mailto:manet@ietf.org>
> https://www.ietf.org/mailman/listinfo/manet