Re: NIST SIP API license and SDP license

"M. Rangnathan" <[email protected]>
Newsgroups gmane.comp.voip.nist-sip
Message-ID <[email protected]>
HI Sanjay,

The SIP API  *only the itnerfaces and not the implementation of the 
interfaces that is*  is indeed SUN / BEA IP and is licensed under the 
terms and conditions therein. You may note that this is true of 
virtually all the API in the J2EE / J2SE bundle including the J2EE API, 
JSLEE API etc. However the implementation of the JSIP API Is public 
domain in the same fashion that there are several HTTP Servlet 
impelemtations with different licensing schemes. I am not familiar with 
the legal implications of all this.

I dont know about the SDP license status. You may well be right about 
its expiry. It is provided for examination purposes.  The API is an old 
one and pending final release of the SDP API (from CISCO/DYNAMICSOFT) 
However, the implementation of the SDP API is in the public domain in 
perpetuity. Confusing indeed. The implementation of the SDP API is yours 
to do what you want with. If you are concerned about the expired license 
you may consider stripping off the implements ... keyword from each of 
the implementation classes.

I hope I have sorted things out for you :-)

Ranga


 Sanjay wrote:

>Is the SDP license now expired? The license agreement states it expires in
>2years of the license text (in 2003)?
>
>Is SIP API is Sun Intellectual property. Is that also licensed under jsip?
>
>Thanks,
>Sanjay
>
>_______________________________________________
>nist-sip mailing list
>[email protected]
>http://www-x.antd.nist.gov/mailman/listinfo/nist-sip
>
>  
>


-- 
M. Ranganathan 

Advanced Networking Technologies Division,
National Institute of Standards and Technology (NIST),
100 Bureau Drive, Stop 8920, Gaithersburg, MD 20899. 
tel:301 975 3664 , fax:301 590 0932 http://w3.antd.nist.gov/
Advanced Networking Technologies For the People!
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.