Re: [ssm] IGMPv3/SSM API for Java ?

Stig Venaas <Stig.Venaas@uninett.no> Sat, 30 April 2005 15:02 UTC

Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1DRtUH-0002Th-56; Sat, 30 Apr 2005 11:02:33 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1DRtUF-0002Tc-5r for ssm@megatron.ietf.org; Sat, 30 Apr 2005 11:02:31 -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 LAA12064 for <ssm@ietf.org>; Sat, 30 Apr 2005 11:02:28 -0400 (EDT)
Received: from tyholt.uninett.no ([158.38.60.10]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1DRthX-0004kL-5d for ssm@ietf.org; Sat, 30 Apr 2005 11:16:15 -0400
Received: from storhaugen.uninett.no (storhaugen.uninett.no [IPv6:2001:700:1:7:290:27ff:fe22:7186]) by tyholt.uninett.no (8.12.10/8.12.10) with ESMTP id j3UF2HLL026959; Sat, 30 Apr 2005 17:02:17 +0200
Received: from storhaugen.uninett.no (localhost.localdomain [127.0.0.1]) by storhaugen.uninett.no (8.12.11/8.12.9) with ESMTP id j3UF2HlE025635; Sat, 30 Apr 2005 17:02:17 +0200
Received: (from venaas@localhost) by storhaugen.uninett.no (8.12.11/8.12.11/Submit) id j3UF2GiY025634; Sat, 30 Apr 2005 17:02:16 +0200
X-Authentication-Warning: storhaugen.uninett.no: venaas set sender to Stig.Venaas@uninett.no using -f
Date: Sat, 30 Apr 2005 17:02:16 +0200
From: Stig Venaas <Stig.Venaas@uninett.no>
To: Marshall Eubanks <marshall.eubanks@gmail.com>
Subject: Re: [ssm] IGMPv3/SSM API for Java ?
Message-ID: <20050430150216.GA25617@storhaugen.uninett.no>
References: <2E60260A5637C2448841A5F60A6F9B033F5062@enfimail1.datcon.co.uk> <dcad22d805043007432b27c241@mail.gmail.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <dcad22d805043007432b27c241@mail.gmail.com>
User-Agent: Mutt/1.4.1i
X-Spam-Score: 0.0 (/)
X-Scan-Signature: cd26b070c2577ac175cd3a6d878c6248
Cc: James Lingard <James.Lingard@dataconnection.com>, Toerless Eckert <eckert@cisco.com>, ssm@ietf.org
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

On Sat, Apr 30, 2005 at 10:43:27AM -0400, Marshall Eubanks wrote:
> Well, I registered and voted for it; took about 3 minutes.

Glad to see this coming up. I was just wondering the same myself a
few days ago.

I've written a tool called ssmping to check SSM reception from a
host (http://www.venaas.no/multicast/ssmping/) and I was thinking
that a Java version might be good. But then I also need a Java API,
so I should vote as well.

Stig

> 
> Regards
> Marshall
> 
> On 4/30/05, James Lingard <James.Lingard@dataconnection.com> wrote:
> > 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=4403551
> > 
> > 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.
> > 
> > --
> > 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
> >
> 
> _______________________________________________
> ssm mailing list
> ssm@ietf.org
> https://www1.ietf.org/mailman/listinfo/ssm

_______________________________________________
ssm mailing list
ssm@ietf.org
https://www1.ietf.org/mailman/listinfo/ssm