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

Marshall Eubanks <marshall.eubanks@gmail.com> Sat, 30 April 2005 14:43 UTC

Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1DRtBy-0006wK-5D; Sat, 30 Apr 2005 10:43:38 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1DRtBw-0006uc-Qt for ssm@megatron.ietf.org; Sat, 30 Apr 2005 10:43:36 -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 KAA10706 for <ssm@ietf.org>; Sat, 30 Apr 2005 10:43:34 -0400 (EDT)
Received: from zproxy.gmail.com ([64.233.162.202]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1DRtPE-00041b-PX for ssm@ietf.org; Sat, 30 Apr 2005 10:57:21 -0400
Received: by zproxy.gmail.com with SMTP id 18so1326922nzp for <ssm@ietf.org>; Sat, 30 Apr 2005 07:43:27 -0700 (PDT)
DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:reply-to:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; b=scYJ6Uy9n0W6p6Z1zLeKTY+yEjkHdkCXhU78BBezUtoHjiT45TfMINuNEnCqh2MuaI9j8RO4MwoS81TKNlQP4fiOgrslLdWrVz7sgwh0PHFq4pWzTte0tLBo2H7NpSL6hKMQK9R2Z5xvA5GpX6p9B4EB7mXBMxPMd/TtLuGCWvg=
Received: by 10.36.41.14 with SMTP id o14mr335271nzo; Sat, 30 Apr 2005 07:43:27 -0700 (PDT)
Received: by 10.36.42.11 with HTTP; Sat, 30 Apr 2005 07:43:27 -0700 (PDT)
Message-ID: <dcad22d805043007432b27c241@mail.gmail.com>
Date: Sat, 30 Apr 2005 10:43:27 -0400
From: Marshall Eubanks <marshall.eubanks@gmail.com>
To: James Lingard <James.Lingard@dataconnection.com>
Subject: Re: [ssm] IGMPv3/SSM API for Java ?
In-Reply-To: <2E60260A5637C2448841A5F60A6F9B033F5062@enfimail1.datcon.co.uk>
Mime-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable
Content-Disposition: inline
References: <2E60260A5637C2448841A5F60A6F9B033F5062@enfimail1.datcon.co.uk>
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 25620135586de10c627e3628c432b04a
Content-Transfer-Encoding: quoted-printable
Cc: Toerless Eckert <eckert@cisco.com>, ssm@ietf.org
X-BeenThere: ssm@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
Reply-To: Marshall Eubanks <marshall.eubanks@gmail.com>
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

Well, I registered and voted for it; took about 3 minutes.

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