[sip-comm-dev] IcedJava: STUN/TURN and ICE


#1

Just to net the list know, I've been working on an implementation of STUN/ICE these past couple of weeks that implement RFC 5389 and MMUSIC-ICE. Support for STUN/Datagram demultiplexing is built in, and an RTPConnector for JMF/FMJ is in the works, though it's a separate module to avoid unnecessary dependancies.

  I don't yet have a public version of this project ready, and it will go through several more cycles before it's completed, but this is a full time development project on my end, for a project at $DAYJOB, and this particular module will be open-sourced when all is said and done.

  It doesn't have roots in the STUN4J or JSTUN code bases, though will likely be licensed similarly as LGPL.

  I know that ICE is on the roadmap for SIP Communicator, and work has started on other library adaptations, but, frankly, I didn't want to wade through the largely obsoleted code bases of existing projects to get this one to work. In that, I apologize for creating 'yet another' STUN library, however, given that this is full time work for me, it might be quicker to work with me on this project rather than working part time on adapting one of the other STUN libraries into a full ICE implementation.

  Anyone have an interest in this one?


#2

Hey Charles,

Thanks for the note.

Charles Chappell wrote:

  Just to net the list know, I've been working on an implementation of
STUN/ICE these past couple of weeks that implement RFC 5389 and MMUSIC-
ICE. Support for STUN/Datagram demultiplexing is built in, and an
RTPConnector for JMF/FMJ is in the works, though it's a separate
module to avoid unnecessary dependancies.

  I don't yet have a public version of this project ready, and it will
go through several more cycles before it's completed, but this is a
full time development project on my end, for a project at $DAYJOB, and
this particular module will be open-sourced when all is said and done.

Any idea of an approximate deadline?

  It doesn't have roots in the STUN4J or JSTUN code bases

Ah that's a shame. It would certainly have been easier to collaborate if
it did.

though will
likely be licensed similarly as LGPL.

  I know that ICE is on the roadmap for SIP Communicator, and work has
started on other library adaptations, but, frankly, I didn't want to
wade through the largely obsoleted code bases of existing projects to
get this one to work. In that, I apologize for creating 'yet another'
STUN library, however, given that this is full time work for me, it
might be quicker to work with me on this project rather than working
part time on adapting one of the other STUN libraries into a full ICE
implementation.

I understand. A couple of more questions:

Where are you planning on hosting it?

Would you be willing to accept developers from this project as
committers of the ICE stack?

This would invariably imply losing some of the copyright/IP so would it
also be acceptable to you employer?

Cheers,
Emil

···

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@sip-communicator.dev.java.net
For additional commands, e-mail: dev-help@sip-communicator.dev.java.net