IETF Logo Mail Archive

[IPv6]Re: Bridging ipv4/ipv6 multicast and broadcast?

Michael Richardson <mcr+ietf@sandelman.ca> Fri, 21 June 2024 18:28 UTC

Return-Path: <mcr+ietf@sandelman.ca>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id A767EC14F6B5 for <ipv6@ietfa.amsl.com>; Fri, 21 Jun 2024 11:28:41 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.108
X-Spam-Level:
X-Spam-Status: No, score=-2.108 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, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, T_SCC_BODY_TEXT_LINE=-0.01, 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=sandelman.ca
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 HcsMef4eI7S7 for <ipv6@ietfa.amsl.com>; Fri, 21 Jun 2024 11:28:37 -0700 (PDT)
Received: from tuna.sandelman.ca (tuna.sandelman.ca [IPv6:2607:f0b0:f:3:216:3eff:fe7c:d1f3]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 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 68DB1C14F6B2 for <ipv6@ietf.org>; Fri, 21 Jun 2024 11:28:37 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by tuna.sandelman.ca (Postfix) with ESMTP id 298FC3898B; Fri, 21 Jun 2024 14:28:35 -0400 (EDT)
Received: from tuna.sandelman.ca ([127.0.0.1]) by localhost (localhost [127.0.0.1]) (amavisd-new, port 10024) with LMTP id oe1tpOpWddWK; Fri, 21 Jun 2024 14:28:34 -0400 (EDT)
Received: from sandelman.ca (obiwan.sandelman.ca [IPv6:2607:f0b0:f:2::247]) by tuna.sandelman.ca (Postfix) with ESMTP id D2FBF38988; Fri, 21 Jun 2024 14:28:33 -0400 (EDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=sandelman.ca; s=mail; t=1718994513; bh=/fGbQl1G3Ks+arshyPY+5kgwku1dG10bcKZ8htWXbUI=; h=From:To:cc:Subject:In-Reply-To:References:Date:From; b=c66giHoa2mkaMo3z/2BQgKIe+ATJdu55zbqnMynC92cFvRYwwbYPH8tsmqdq9YsoN 2gSfW5oqvQ97t1TjcXNGZGRiJ7gYjCzJBA9ajK2kaa0J1vuUthh0Apm8giAZ/q7QrM BXcNCy4OjXi5mEOY2H/7Lpghwz3geLFApezgf4ZS1utFZeZG8SsKNn9nruniYR2dyC VoNArKjaUaeqsnAvUhWSdDB90yry7lEradcmCXKo88hSg3d+ZwdvfFVOB4HvzPa/mC Va/zkHvNwQVpOde9ztcdUzIgEp7wf2Uo6c6OLPjA3OxX55/iuTeyT5VPKxW8KIRwl8 fLx0OTwlDy4KA==
Received: from obiwan.sandelman.ca (localhost [IPv6:::1]) by sandelman.ca (Postfix) with ESMTP id C8D8D7AE; Fri, 21 Jun 2024 14:28:33 -0400 (EDT)
From: Michael Richardson <mcr+ietf@sandelman.ca>
To: "Soni \"They/Them\" L." <fakedme+ipv6@gmail.com>
In-Reply-To: <84613752-858f-456e-9df5-17367cb2a41a@gmail.com>
References: <dbf7e116-2f5c-4929-9b0b-92c3947cdb3a@gmail.com> <CAPt1N1=LKiFr-TCNJjLqEEyeA86DW_7OhSMyFetABa8_kiFrFw@mail.gmail.com> <2da8ca43-d0d2-42d4-9a45-4fac2a08c5c1@gmail.com> <CAPt1N1maOMMOo0uN9ZJpgu3myVp2mxKfSHSFsxcw=Do9pNOJwQ@mail.gmail.com> <84613752-858f-456e-9df5-17367cb2a41a@gmail.com>
X-Mailer: MH-E 8.6+git; nmh 1.8+dev; GNU Emacs 28.2
X-Face: $\n1pF)h^`}$H>Hk{L"x@)JS7<%Az}5RyS@k9X%29-lHB$Ti.V>2bi.~ehC0;<'$9xN5Ub# z!G,p`nR&p7Fz@^UXIn156S8.~^@MJ*mMsD7=QFeq%AL4m<nPbLgmtKK-5dC@#:k
MIME-Version: 1.0
Content-Type: multipart/signed; boundary="=-=-="; micalg="pgp-sha512"; protocol="application/pgp-signature"
Date: Fri, 21 Jun 2024 14:28:33 -0400
Message-ID: <28606.1718994513@obiwan.sandelman.ca>
Message-ID-Hash: C3H53REJBPBSW6MPXMAGZQBTVGSWWDFX
X-Message-ID-Hash: C3H53REJBPBSW6MPXMAGZQBTVGSWWDFX
X-MailFrom: mcr+ietf@sandelman.ca
X-Mailman-Rule-Misses: dmarc-mitigation; no-senders; approved; emergency; loop; banned-address; member-moderation; header-match-ipv6.ietf.org-0; nonmember-moderation; administrivia; implicit-dest; max-recipients; max-size; news-moderation; no-subject; digests; suspicious-header
CC: ipv6@ietf.org
X-Mailman-Version: 3.3.9rc4
Precedence: list
Subject: [IPv6]Re: Bridging ipv4/ipv6 multicast and broadcast?
List-Id: "IPv6 Maintenance Working Group (6man)" <ipv6.ietf.org>
Archived-At: <https://mailarchive.ietf.org/arch/msg/ipv6/ggbHY9TbOzIjEPJaEoudKs3SRL8>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ipv6>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Owner: <mailto:ipv6-owner@ietf.org>
List-Post: <mailto:ipv6@ietf.org>
List-Subscribe: <mailto:ipv6-join@ietf.org>
List-Unsubscribe: <mailto:ipv6-leave@ietf.org>

I think that the bug is either:

1) the host that wants to do minecraft is not actually IPv6-only, it wants
v4, and shouldn't do option 108.

2) IPv6-only hosts should actually continue to configure IPv4-Link-Local
addresses.

I don't think bridging is the right answer.
Minecraft can trivially add discovery and LAN play over v6-Link-Local.

--
Michael Richardson <mcr+IETF@sandelman.ca>   . o O ( IPv6 IøT consulting )
           Sandelman Software Works Inc, Ottawa and Worldwide

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