IETF Logo Mail Archive

RE: Question on IPV4/IPV6 Multicast interoperability

Tina TSOU <Tina.Tsou.Zouting@huawei.com> Tue, 20 December 2011 00:39 UTC

Return-Path: <Tina.Tsou.Zouting@huawei.com>
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 5E9A621F8477; Mon, 19 Dec 2011 16:39:21 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.598
X-Spam-Level:
X-Spam-Status: No, score=-6.598 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 5TJN6S-0X4WY; Mon, 19 Dec 2011 16:39:20 -0800 (PST)
Received: from szxga04-in.huawei.com (szxga04-in.huawei.com [119.145.14.67]) by ietfa.amsl.com (Postfix) with ESMTP id 1E73821F8462; Mon, 19 Dec 2011 16:39:20 -0800 (PST)
Received: from huawei.com (szxga04-in [172.24.2.12]) by szxga04-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 2.14 (built Aug 8 2006)) with ESMTP id <0LWH001ZY8HBIM@szxga04-in.huawei.com>; Tue, 20 Dec 2011 08:39:11 +0800 (CST)
Received: from szxrg02-dlp.huawei.com ([172.24.2.119]) by szxga04-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 2.14 (built Aug 8 2006)) with ESMTP id <0LWH002WD8HA1Q@szxga04-in.huawei.com>; Tue, 20 Dec 2011 08:39:11 +0800 (CST)
Received: from szxeml206-edg.china.huawei.com ([172.24.2.119]) by szxrg02-dlp.huawei.com (MOS 4.1.9-GA) with ESMTP id AFU52928; Tue, 20 Dec 2011 08:39:10 +0800
Received: from SZXEML416-HUB.china.huawei.com (10.82.67.155) by szxeml206-edg.china.huawei.com (172.24.2.58) with Microsoft SMTP Server (TLS) id 14.1.323.3; Tue, 20 Dec 2011 08:39:08 +0800
Received: from SZXEML526-MBX.china.huawei.com ([169.254.2.37]) by szxeml416-hub.china.huawei.com ([10.82.67.155]) with mapi id 14.01.0323.003; Tue, 20 Dec 2011 08:39:03 +0800
Date: Tue, 20 Dec 2011 00:39:02 +0000
From: Tina TSOU <Tina.Tsou.Zouting@huawei.com>
Subject: RE: Question on IPV4/IPV6 Multicast interoperability
In-reply-to: <1324206855.51664.YahooMailNeo@web121801.mail.ne1.yahoo.com>
X-Originating-IP: [10.193.34.145]
To: Ghanashyam Satpathy <ghanashyam_satpathy@yahoo.com>, "ipv6@ietf.org" <ipv6@ietf.org>
Message-id: <C0E0A32284495243BDE0AC8A066631A80C22F04F@szxeml526-mbx.china.huawei.com>
MIME-version: 1.0
Content-type: multipart/alternative; boundary="Boundary_(ID_f/BsSJ6RYBqOdKm0ahN7+w)"
Content-language: en-US
Accept-Language: en-US, zh-CN
Thread-topic: Question on IPV4/IPV6 Multicast interoperability
Thread-index: AQHMvpzl8eODnaBst02N8+9ZmITwy5Xj4SAA
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
X-CFilter-Loop: Reflected
References: <1324206855.51664.YahooMailNeo@web121801.mail.ne1.yahoo.com>
Cc: MBONED WG <mboned@ietf.org>, "multrans@ietf.org" <multrans@ietf.org>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ipv6>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ipv6>, <mailto:ipv6-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 20 Dec 2011 00:39:21 -0000

Ghanashyam,
http://datatracker.ietf.org/doc/draft-tsou-multrans-addr-acquisition/
http://datatracker.ietf.org/doc/draft-zhou-multrans-af1-specification/
Running code exists.
Hope it helps.

Best Regards,
Tina TSOU
http://tinatsou.weebly.com/contact.html

From: ipv6-bounces@ietf.org [mailto:ipv6-bounces@ietf.org] On Behalf Of Ghanashyam Satpathy
Sent: Sunday, December 18, 2011 3:14 AM
To: ipv6@ietf.org
Subject: Question on IPV4/IPV6 Multicast interoperability

Hello,

I have a question on IPV4/IPV6 Multicast interoperability. We have succesfully upgraded our application(Windows Based) to support IPV6 and faced issue on multicast interoperability. Multicast messages sent by a IPV6 server is successfully receved by a client running on IPV6. But any client running on IPV4 is not able to receive the message.

Quite a no. of things I tried like using IPV4 mapped IPV6 address and V4 embeded V6 adress.But nothing seems to be working.Would like to know an unified way so that one multicast message sent by an IPV6 server should be received by both V6 and V4 client.

Would be great if somebody can send some code snippet(C/C++) on it.

Thanks.

Ghanashyam

v2.23.0 | Report a Bug | By Email