From ssm-bounces@ietf.org Fri Apr 29 21:49:30 2005 Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1DRh6o-0001ag-7t; Fri, 29 Apr 2005 21:49:30 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1DRh6m-0001ab-1H for ssm@megatron.ietf.org; Fri, 29 Apr 2005 21:49:28 -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 VAA08736 for ; Fri, 29 Apr 2005 21:49:26 -0400 (EDT) Received: from sj-iport-2-in.cisco.com ([171.71.176.71] helo=sj-iport-2.cisco.com) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1DRhJv-0001Yq-7b for ssm@ietf.org; Fri, 29 Apr 2005 22:03:05 -0400 Received: from sj-core-5.cisco.com (171.71.177.238) by sj-iport-2.cisco.com with ESMTP; 29 Apr 2005 18:49:17 -0700 Received: from cisco.com (cypher.cisco.com [171.69.11.142]) by sj-core-5.cisco.com (8.12.10/8.12.6) with ESMTP id j3U1nEhu023322 for ; Fri, 29 Apr 2005 18:49:15 -0700 (PDT) Received: (from eckert@localhost) by cisco.com (8.8.8-Cisco List Logging/8.8.8) id SAA10904 for ssm@ietf.org; Fri, 29 Apr 2005 18:49:14 -0700 (PDT) Date: Fri, 29 Apr 2005 18:49:14 -0700 From: Toerless Eckert To: ssm@ietf.org Message-ID: <20050430014914.GK2155@cisco.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.4i X-Spam-Score: 0.0 (/) X-Scan-Signature: 856eb5f76e7a34990d1d457d8e8e5b7f Subject: [ssm] IGMPv3/SSM API for Java ? X-BeenThere: ssm@ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Source-Specific Multicast List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: ssm-bounces@ietf.org Errors-To: ssm-bounces@ietf.org 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 From ssm-bounces@ietf.org Sat Apr 30 07:34:33 2005 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 ; 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" To: "Toerless Eckert" , 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 List-Unsubscribe: , List-Post: List-Help: List-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 From ssm-bounces@ietf.org Sat Apr 30 10:43:38 2005 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 ; 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 ; 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: Date: Sat, 30 Apr 2005 10:43:27 -0400 From: Marshall Eubanks To: James Lingard 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 , ssm@ietf.org X-BeenThere: ssm@ietf.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: Marshall Eubanks List-Id: Source-Specific Multicast List-Unsubscribe: , List-Post: List-Help: List-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 wrote: > Toerless, >=20 > I'm pretty sure you're right that there's no SSM API, though I can't conf= irm that there's no implicit way of triggering (S,G) membership reports. T= he 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): >=20 > http://bugs.sun.com/bugdatabase/view_bug.do?bug_id=3D4403551 >=20 > The standard way of encouraging Sun to get bugs fixed is for lots of peop= le to vote for them. See: >=20 > http://bugs.sun.com/bugdatabase/top25_bugs.do > http://bugs.sun.com/bugdatabase/top25_rfes.do >=20 > 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 := ) >=20 > Other than that, there is something called the Java Community Process (se= e 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. >=20 > It also seems that for the next release (J2SE 6.0), Sun are soliciting ex= ternally contributed code (see http://java.sun.com/developer/technicalArtic= les/J2SE/peabody/). So if there's someone out there with the time to work = on this, this route may well be the fastest. >=20 > Hope that helps, > James. >=20 > -- > James Lingard > Data Connection Ltd (DCL) > http://www.dataconnection.com/ >=20 >=20 > -----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 ? >=20 > Looking at >=20 > http://java.sun.com/j2se/1.5.0/docs/api/java/net/MulticastSocket.html >=20 > 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.. ? >=20 > 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 ??) >=20 > Thanks > Toerless >=20 > _______________________________________________ > 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 From ssm-bounces@ietf.org Sat Apr 30 11:02:33 2005 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 ; 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 To: Marshall Eubanks Subject: Re: [ssm] IGMPv3/SSM API for Java ? Message-ID: <20050430150216.GA25617@storhaugen.uninett.no> References: <2E60260A5637C2448841A5F60A6F9B033F5062@enfimail1.datcon.co.uk> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.4.1i X-Spam-Score: 0.0 (/) X-Scan-Signature: cd26b070c2577ac175cd3a6d878c6248 Cc: James Lingard , Toerless Eckert , ssm@ietf.org X-BeenThere: ssm@ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Source-Specific Multicast List-Unsubscribe: , List-Post: List-Help: List-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 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 From ssm-bounces@ietf.org Sat Apr 30 11:10:40 2005 Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1DRtc8-0003wB-MM; Sat, 30 Apr 2005 11:10:40 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1DRtc6-0003w6-Ll for ssm@megatron.ietf.org; Sat, 30 Apr 2005 11:10:39 -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 LAA12617 for ; Sat, 30 Apr 2005 11:10:36 -0400 (EDT) Received: from clarinet.u-strasbg.fr ([130.79.90.157]) by ietf-mx.ietf.org with smtp (Exim 4.33) id 1DRtpN-000536-Jt for ssm@ietf.org; Sat, 30 Apr 2005 11:24:23 -0400 Received: (qmail 27663 invoked for bounce); 30 Apr 2005 15:10:20 -0000 Received: from unknown (HELO ?192.168.0.3?) (hoerdt@unknown) by unknown with RC4-MD5 encrypted SMTP; 30 Apr 2005 15:10:20 -0000 Message-ID: <42739FA8.2010604@clarinet.u-strasbg.fr> Date: Sat, 30 Apr 2005 17:09:28 +0200 From: Hoerdt Mickael User-Agent: Mozilla/5.0 (X11; U; Linux i686; fr-FR; rv:1.7.7) Gecko/20050420 Debian/1.7.7-2 X-Accept-Language: en MIME-Version: 1.0 To: Stig Venaas Subject: Re: [ssm] IGMPv3/SSM API for Java ? References: <2E60260A5637C2448841A5F60A6F9B033F5062@enfimail1.datcon.co.uk> <20050430150216.GA25617@storhaugen.uninett.no> In-Reply-To: <20050430150216.GA25617@storhaugen.uninett.no> Content-Type: text/plain; charset=ISO-8859-1; format=flowed X-Spam-Score: 0.0 (/) X-Scan-Signature: 944ecb6e61f753561f559a497458fb4f Content-Transfer-Encoding: quoted-printable X-MIME-Autoconverted: from 8bit to quoted-printable by ietf.org id LAA12617 Cc: James Lingard , Toerless Eckert , Marshall Eubanks , ssm@ietf.org X-BeenThere: ssm@ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Source-Specific Multicast List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: ssm-bounces@ietf.org Errors-To: ssm-bounces@ietf.org I voted too. One may take in account that this Java API may depends on=20 libc implementation of RFC 3678 to run (which depends on kernel=20 implementation too). I'm not sure how java works, but if its the case,=20 only glibc starting from 2.3.4 supports it. Does anyone know how the=20 java APIs are implemented ? are they overlay of C/C++ ? Hoerdt Micka=EBl Stig Venaas wrote: >On Sat, Apr 30, 2005 at 10:43:27AM -0400, Marshall Eubanks wrote: > =20 > >>Well, I registered and voted for it; took about 3 minutes. >> =20 >> > >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 > > =20 > >>Regards >>Marshall >> >>On 4/30/05, James Lingard wrote: >> =20 >> >>>Toerless, >>> >>>I'm pretty sure you're right that there's no SSM API, though I can't c= onfirm that there's no implicit way of triggering (S,G) membership report= s. 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 p= eople 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 h= as 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 h= appen :) >>> >>>Other than that, there is something called the Java Community Process = (see http://jcp.org/en/home/index) by which new APIs and language feature= s 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/technical= Articles/J2SE/peabody/). So if there's someone out there with the time t= o 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.htm= l >>> >>>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 >>> >>> =20 >>> >>_______________________________________________ >>ssm mailing list >>ssm@ietf.org >>https://www1.ietf.org/mailman/listinfo/ssm >> =20 >> > >_______________________________________________ >ssm mailing list >ssm@ietf.org >https://www1.ietf.org/mailman/listinfo/ssm > =20 > _______________________________________________ ssm mailing list ssm@ietf.org https://www1.ietf.org/mailman/listinfo/ssm From ssm-bounces@ietf.org Sat Apr 30 15:13:17 2005 Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1DRxOv-0001pe-R7; Sat, 30 Apr 2005 15:13:17 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1DRxOu-0001pZ-5J for ssm@megatron.ietf.org; Sat, 30 Apr 2005 15:13:16 -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 PAA25752 for ; Sat, 30 Apr 2005 15:13:14 -0400 (EDT) Received: from sj-iport-5.cisco.com ([171.68.10.87]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1DRxcE-0004Ma-HF for ssm@ietf.org; Sat, 30 Apr 2005 15:27:02 -0400 Received: from sj-core-4.cisco.com (171.68.223.138) by sj-iport-5.cisco.com with ESMTP; 30 Apr 2005 12:13:07 -0700 Received: from cisco.com (cypher.cisco.com [171.69.11.142]) by sj-core-4.cisco.com (8.12.10/8.12.6) with ESMTP id j3UJD3pR025357; Sat, 30 Apr 2005 12:13:03 -0700 (PDT) Received: (from eckert@localhost) by cisco.com (8.8.8-Cisco List Logging/8.8.8) id MAA26476; Sat, 30 Apr 2005 12:13:02 -0700 (PDT) Date: Sat, 30 Apr 2005 12:13:02 -0700 From: Toerless Eckert To: James Lingard Subject: Re: [ssm] IGMPv3/SSM API for Java ? Message-ID: <20050430191302.GP2155@cisco.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.4i X-Spam-Score: 0.0 (/) X-Scan-Signature: 8abaac9e10c826e8252866cbe6766464 Cc: ssm@ietf.org X-BeenThere: ssm@ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Source-Specific Multicast List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: ssm-bounces@ietf.org Errors-To: ssm-bounces@ietf.org Thanks. Registered and voted. Is it actually possible to leave comments in that bug too ? I tried to on the "Comments" place, but it just responded with "We encountered an unexpected error. Please try back again. " The page also says "Welcome, null" ... *sigh* On Sat, Apr 30, 2005 at 12:34:19PM +0100, James Lingard 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/ _______________________________________________ ssm mailing list ssm@ietf.org https://www1.ietf.org/mailman/listinfo/ssm From ssm-bounces@ietf.org Sat Apr 30 15:15:08 2005 Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1DRxQi-00026x-Eo; Sat, 30 Apr 2005 15:15:08 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1DRxQg-00023X-Qy for ssm@megatron.ietf.org; Sat, 30 Apr 2005 15:15:07 -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 PAA26171 for ; Sat, 30 Apr 2005 15:15:05 -0400 (EDT) Received: from sj-iport-5.cisco.com ([171.68.10.87]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1DRxe1-0004Rr-5v for ssm@ietf.org; Sat, 30 Apr 2005 15:28:53 -0400 Received: from sj-core-4.cisco.com (171.68.223.138) by sj-iport-5.cisco.com with ESMTP; 30 Apr 2005 12:14:58 -0700 Received: from cisco.com (cypher.cisco.com [171.69.11.142]) by sj-core-4.cisco.com (8.12.10/8.12.6) with ESMTP id j3UJEtpR025608; Sat, 30 Apr 2005 12:14:55 -0700 (PDT) Received: (from eckert@localhost) by cisco.com (8.8.8-Cisco List Logging/8.8.8) id MAA26729; Sat, 30 Apr 2005 12:14:55 -0700 (PDT) Date: Sat, 30 Apr 2005 12:14:55 -0700 From: Toerless Eckert To: mboned@lists.uoregon.edu Subject: Re: [ssm] IGMPv3/SSM API for Java ? Message-ID: <20050430191455.GQ2155@cisco.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.4i X-Spam-Score: 0.0 (/) X-Scan-Signature: 5a9a1bd6c2d06a21d748b7d0070ddcb8 Cc: ssm@ietf.org X-BeenThere: ssm@ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Source-Specific Multicast List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: ssm-bounces@ietf.org Errors-To: ssm-bounces@ietf.org Copied to mboned. Would be nice if more people would vote on this bug. Thanks Toerless On Sat, Apr 30, 2005 at 12:34:19PM +0100, James Lingard 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