Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
 by megatron.ietf.org with esmtp (Exim 4.32)
 id 1DRqEz-0001JV-87; Sat, 30 Apr 2005 07:34:33 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
 by megatron.ietf.org with esmtp (Exim 4.32) id 1DRqEy-0001JQ-66
 for ssm@megatron.ietf.org; Sat, 30 Apr 2005 07:34:32 -0400
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
 by ietf.org (8.9.1a/8.9.1a) with ESMTP id HAA28613
 for <ssm@ietf.org>; Sat, 30 Apr 2005 07:34:31 -0400 (EDT)
Received: from smtp2.dataconnection.com ([192.91.191.8])
 by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1DRqSE-0005uH-Dm
 for ssm@ietf.org; Sat, 30 Apr 2005 07:48:14 -0400
Received: from enfimail1.datcon.co.uk ([172.19.14.253]) by
 smtp2.dataconnection.com with Microsoft SMTPSVC(6.0.3790.211); 
 Sat, 30 Apr 2005 12:34:19 +0100
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
X-MimeOLE: Produced By Microsoft Exchange V6.5.7226.0
Subject: RE: [ssm] IGMPv3/SSM API for Java ?
Date: Sat, 30 Apr 2005 12:34:19 +0100
Message-ID: <2E60260A5637C2448841A5F60A6F9B033F5062@enfimail1.datcon.co.uk>
Thread-Topic: [ssm] IGMPv3/SSM API for Java ?
Thread-Index: AcVNJ3SfREc7lQzET2isvwhPebqt8AATwJhw
From: "James Lingard" <James.Lingard@dataconnection.com>
To: "Toerless Eckert" <eckert@cisco.com>, <ssm@ietf.org>
X-OriginalArrivalTime: 30 Apr 2005 11:34:19.0496 (UTC)
 FILETIME=[8C495E80:01C54D78]
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 52f7a77164458f8c7b36b66787c853da
Content-Transfer-Encoding: quoted-printable
Cc: 
X-BeenThere: ssm@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Source-Specific Multicast <ssm.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ssm>,
 <mailto:ssm-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ssm@ietf.org>
List-Help: <mailto:ssm-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ssm>,
 <mailto:ssm-request@ietf.org?subject=subscribe>
Sender: ssm-bounces@ietf.org
Errors-To: ssm-bounces@ietf.org

Toerless,

I'm pretty sure you're right that there's no SSM API, though I can't =
confirm that there's no implicit way of triggering (S,G) membership =
reports.  The following RFE has been raised in Sun's Java bug database =
for this issue (though you may need to register in order to view this =
page):

http://bugs.sun.com/bugdatabase/view_bug.do?bug_id=3D4403551

The standard way of encouraging Sun to get bugs fixed is for lots of =
people to vote for them.  See:

http://bugs.sun.com/bugdatabase/top25_bugs.do
http://bugs.sun.com/bugdatabase/top25_rfes.do

I think they do actually pay attention to these.  Currently this RFE has =
only 2 votes (of which one is mine), but if we could encourage lots =
(i.e. >100) of IETF multicast folks to vote for this bug, something =
might happen :)

Other than that, there is something called the Java Community Process =
(see http://jcp.org/en/home/index) by which new APIs and language =
features are often developed, although I'm no expert on how this works.

It also seems that for the next release (J2SE 6.0), Sun are soliciting =
externally contributed code (see =
http://java.sun.com/developer/technicalArticles/J2SE/peabody/).  So if =
there's someone out there with the time to work on this, this route may =
well be the fastest.

Hope that helps,
James.

--=20
James Lingard
Data Connection Ltd (DCL)
http://www.dataconnection.com/


-----Original Message-----
From: ssm-bounces@ietf.org [mailto:ssm-bounces@ietf.org]On Behalf Of
Toerless Eckert
Sent: 30 April 2005 02:49
To: ssm@ietf.org
Subject: [ssm] IGMPv3/SSM API for Java ?


Looking at

  http://java.sun.com/j2se/1.5.0/docs/api/java/net/MulticastSocket.html

it looks as if Java does NOT have any SSM API, eg: nothing like
JoinSourceGroup(). Can anyone more aware of Java confirm this ? Or
would any Java implementation implicitly trigger at least an IGMPv3
INCLUDE({S},G) membership report whenever a connected datagram socket
was bound to a group (get the source address from connect(), get the
group from JoinGroup() ?) ... I wouldn't think so.. ?

So, assuming the Java world has ignored SSM so far, what can be done
to change this ? I wouldn't even know who defines the API (within ?
outside of Sun ??)

Thanks
    Toerless

_______________________________________________
ssm mailing list
ssm@ietf.org
https://www1.ietf.org/mailman/listinfo/ssm


