IETF Logo Mail Archive

[manet] Re: [IPv6]Re: IPv6 Address for Ad Hoc Networks

Kyle Rose <krose@krose.org> Fri, 02 August 2024 18:45 UTC

Return-Path: <krose@krose.org>
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 64527C14F686 for <manet@ietfa.amsl.com>; Fri, 2 Aug 2024 11:45:25 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.106
X-Spam-Level:
X-Spam-Status: No, score=-2.106 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_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 (1024-bit key) header.d=krose.org
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 M3pQluDj-TrH for <manet@ietfa.amsl.com>; Fri, 2 Aug 2024 11:45:21 -0700 (PDT)
Received: from mail-ej1-x62d.google.com (mail-ej1-x62d.google.com [IPv6:2a00:1450:4864:20::62d]) (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 bits) key-exchange X25519 server-signature ECDSA (P-256) server-digest SHA256) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 6A711C137370 for <manet@ietf.org>; Fri, 2 Aug 2024 11:45:21 -0700 (PDT)
Received: by mail-ej1-x62d.google.com with SMTP id a640c23a62f3a-a7a9cf7d3f3so1048646866b.1 for <manet@ietf.org>; Fri, 02 Aug 2024 11:45:21 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=krose.org; s=google; t=1722624319; x=1723229119; darn=ietf.org; h=content-transfer-encoding:cc:to:subject:message-id:date:from :in-reply-to:references:mime-version:from:to:cc:subject:date :message-id:reply-to; bh=56UGxL4EJUdKUZfGkBK2J1tKjJf+/yzwAkNqeHS3bcs=; b=ZpNB9w09nJf5fE92iYTdAS2xCiRKMQBhbCTBYAXzudnDtpY6w4IA3Keud5STt2mJIf A0W6mv2n1EDi93cJ5K2+Wrok562/7Xp0scmJIjf/gNugjJyprwXUEg2FLDEb5T5+iiE0 bQnh0wIAzokCXDwCLL5rZxWFnS4GmRl+mz3qw=
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1722624319; x=1723229119; h=content-transfer-encoding:cc:to:subject:message-id:date:from :in-reply-to:references:mime-version:x-gm-message-state:from:to:cc :subject:date:message-id:reply-to; bh=56UGxL4EJUdKUZfGkBK2J1tKjJf+/yzwAkNqeHS3bcs=; b=jp2G3EAVgBsZjBVPZCsi8LVy5UX53I8Q9xUBTGMH72BukYykYyl0XS36R5E4EBnofm /5/MXZTEV4BUGuhwK1qebgASNCd1qjjAPLQyDvz5XHJt20nk1SGq0czaQ0tMbaJBrjVN F+mdkPJqxGg+LM3vzVn4e/JIYRvLIVtv34HgRoCu/xl+bmewvl1S3mKEvUvIK7rLKQIX UY0I2utXWuulM+3uQ3g/6NwFJX90JKAEyhFaDgsj/TDxLZhpOAbp0iIUHQFSMiuImJSk V9A0P1hemid6N2/m0Qk0aBBo94cFR+RVI4JjhBLDiDsii7MqUzo71wXG3magHlb0qO+K jaOQ==
X-Forwarded-Encrypted: i=1; AJvYcCUlwIAoi63K+21R6s7bBM6y+faQHM8/t3i2xhAJIdXdJj2mtpfZ8BsUBPwgR9z+yrmOvW8ec8Jvp/z1N+0x0Q==
X-Gm-Message-State: AOJu0YwMg7JeWhNpPFSPiFrr0KhB01VoXU//TP4ryB/Z3BmKO0kTYzTl CvOE2xsnsLpVAopo7iXksJCc5eyZt0FAihHlI3tARloBaBygW5hkuFwYhHXZV8yYIvOSEkY/qgA Jn9Whrvmj1651T6bWz735GZdIgQvPKdZZZO4n0g==
X-Google-Smtp-Source: AGHT+IH1E9yskBfLOF67Hnk8OJOdeKJZmln4xmvAG0fzOlx31P5UeVlRcRGkr6cJ9gvywE8Ca7pA8MwjheOwkPNh17Y=
X-Received: by 2002:a17:906:f5a4:b0:a7a:a4be:2f9d with SMTP id a640c23a62f3a-a7dc4db3c44mr310747866b.12.1722624318913; Fri, 02 Aug 2024 11:45:18 -0700 (PDT)
MIME-Version: 1.0
References: <172254176215.2393908.5844096604515362364@dt-datatracker-659f84ff76-9wqgv> <BN0P110MB1420B37307E968D513A12EF9A3B2A@BN0P110MB1420.NAMP110.PROD.OUTLOOK.COM> <792AF5A2-EF5D-42B5-8BC6-D8B5D2845C38@gmail.com>
In-Reply-To: <792AF5A2-EF5D-42B5-8BC6-D8B5D2845C38@gmail.com>
From: Kyle Rose <krose@krose.org>
Date: Fri, 02 Aug 2024 14:45:07 -0400
Message-ID: <CAJU8_nWmUsu2M6FREZaRFGqDC4bOBKeSAXC_hzUoB1AgGMoHBA@mail.gmail.com>
To: Bob Hinden <bob.hinden@gmail.com>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
Message-ID-Hash: FGNCU6YEPVS54S2PBD3UZ3GZIJKNKX2B
X-Message-ID-Hash: FGNCU6YEPVS54S2PBD3UZ3GZIJKNKX2B
X-MailFrom: krose@krose.org
X-Mailman-Rule-Misses: dmarc-mitigation; no-senders; approved; emergency; loop; banned-address; member-moderation; header-match-manet.ietf.org-0; header-match-manet.ietf.org-1; header-match-manet.ietf.org-2; header-match-manet.ietf.org-3; header-match-manet.ietf.org-4; header-match-manet.ietf.org-5; header-match-manet.ietf.org-6; header-match-manet.ietf.org-7; header-match-manet.ietf.org-8; header-match-manet.ietf.org-9; header-match-manet.ietf.org-10; header-match-manet.ietf.org-11; header-match-manet.ietf.org-12; header-match-manet.ietf.org-13; header-match-manet.ietf.org-14; header-match-manet.ietf.org-15; header-match-manet.ietf.org-16; header-match-manet.ietf.org-17; nonmember-moderation; administrivia; implicit-dest; max-recipients; max-size; news-moderation; no-subject; digests; suspicious-header
CC: "Templin (US), Fred L" <Fred.L.Templin=40boeing.com@dmarc.ietf.org>, IPv6 List <ipv6@ietf.org>, "manet@ietf.org" <manet@ietf.org>
X-Mailman-Version: 3.3.9rc4
Precedence: list
Subject: [manet] Re: [IPv6]Re: IPv6 Address for Ad Hoc Networks
List-Id: Mobile Ad-hoc Networks <manet.ietf.org>
Archived-At: <https://mailarchive.ietf.org/arch/msg/manet/VkBgM6pVDKKAXRXYQxqYuczRvqM>
List-Archive: <https://mailarchive.ietf.org/arch/browse/manet>
List-Help: <mailto:manet-request@ietf.org?subject=help>
List-Owner: <mailto:manet-owner@ietf.org>
List-Post: <mailto:manet@ietf.org>
List-Subscribe: <mailto:manet-join@ietf.org>
List-Unsubscribe: <mailto:manet-leave@ietf.org>

On Fri, Aug 2, 2024 at 2:35 PM Bob Hinden <bob.hinden@gmail.com> wrote:
> IMHO, this draft should not specify any specific prefixes.   It should all be “To be assigned”.   Including it now is a distraction to the more important question.
>
> I think the question that needs to be answered is:  Is there a real need for Ad Hoc IPv6 addresses?   Focusing now on the details or which or how many prefixes it might use doesn’t address that.

It sounds like the main example use case is a mobile ad-hoc network,
e.g., of vehicles traveling on a highway at different speeds and with
no ability to pre-define a mesh or to pre-determine routes within that
network to connected resources.

Has anyone proposed concretely building such a thing with a particular
application in mind?

I'm trying to figure out whether this is WG or RG territory.

Kyle

v2.29.0 | Report a Bug | By Email | System Status