From owner-freebsd-bugs Mon Sep 4 17:29:50 2000 Delivered-To: freebsd-bugs@freebsd.org Received: from coconut.itojun.org (coconut.itojun.org [210.160.95.97]) by hub.freebsd.org (Postfix) with ESMTP id BE27B37B422 for ; Mon, 4 Sep 2000 17:29:48 -0700 (PDT) Received: from kiwi.itojun.org (localhost.itojun.org [127.0.0.1]) by coconut.itojun.org (8.9.3+3.2W/3.7W/smtpfeed 1.06) with ESMTP id JAA08623; Tue, 5 Sep 2000 09:29:42 +0900 (JST) To: Brad Huntting Cc: bugs@freebsd.org, huntting@glarp.com, Hajimu UMEMOTO , core@kame.net In-reply-to: huntting's message of Mon, 04 Sep 2000 14:51:16 CST. <200009042051.OAA72183@hunkular.glarp.com> X-Template-Reply-To: itojun@itojun.org X-Template-Return-Receipt-To: itojun@itojun.org X-PGP-Fingerprint: F8 24 B4 2C 8C 98 57 FD 90 5F B4 60 79 54 16 E2 Subject: Re: kern/21016: IPV6_JOIN_GROUP doesnt work for mapped IPv4 multicast addresses From: itojun@iijlab.net Date: Tue, 05 Sep 2000 09:29:42 +0900 Message-ID: <8621.968113782@coconut.itojun.org> Sender: owner-freebsd-bugs@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org >> this is a feature. IPv4 mapped address on AF_INET6 socket is just >> to help porting basic IPv4 apps at ease. to manipulate IPv4 traffic >> in detail (including TOS/TTL, or multicast), you must use AF_INET >> socket. >Section 3.7 of draft-ietf-ipngwg-rfc2553bis-00.txt does not aggre. >V4 mapped addresses are clearly intended to allow "basic" v6 apps >to interoperate with legacy v4 apps w/o duplicating code. And >"basic" in this case most definitly includes multicast. where did you get the impression for the last sentence? from my understanding, multicast is outside of scope (and I'm very convinced about it) the more you try to use IPv4 mapped address in wider scope, the system gets more messy. >Is KAME planning on fixing this anytime soon? I don't think so. I can't speak for other KAME guys. itojun To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-bugs" in the body of the message