1. Introduction 1.1 Project/Component Working Name: SER removal 1.2 Name of Document Author/Supplier: Author: Lukas Rovensky 1.3 Date of This Document: 19 March, 2010 1.4 The requested release taxonomy: Patch binding for the announcement and marking as Obsolete. Minor binding for the removal. 1.5 Introduction This FastTrack will EOF the Sip Express Router (SER) and its web based interface -- SERWeb -- from Solaris Next and obsolete SER and SERWeb in Solaris 10. On November 4th 2008 a new SIP Router project was announced and joined by SER developers, [1]. This also means that SER itself is no longer developed in favour of the SIP Router, [2]. Since SER is no longer developed product it shall be removed from Solaris Next. Should a similar product be required then the SIP Router (Kamailio) may be a good candidate. Note, that attributes(5) documents an exception, which can apply to this case: 4. An interface specification which isn't controlled by Sun has been changed incompatibly and the vast majority of interface consumers expect the newer interface. 1.6 Previous Relevant ARC cases LSARC/2004/324 - sfw/SIP Proxy Server (actually still in waiting state), [3] 1.7 SIP Status In Solaris, RFC 3261 SER itself provides functionality, which implements SIP protocol, RFC 3261, [8]. There are currently also two libraries in Solaris, which implement the SIP protocol (RFC 3261, [8]) and can be eventually used for implementation of SIP routing: * libsip (also in S10, since U4), PSARC 2006/402, [4], CR 6461142, [5] This library is developed by Oracle and it is available both in Solaris 10 and OpenSolaris / Solaris Next. As per the responsible engineer, there is at least one customer, who had built its application using libsip. * libosip2, LSARC 2009/277, [6], CR 6826484, [7] This is an open source library, [9]. There are no further plans with this library as per the responsible engineer. 1.8 Input From Marketing, Usage of SER Marketing was informed about the intention to remove SER from Solaris Next. They do not seem to have any real data, which would support or deny this action. Their current position is as the following: "Right now, I agree with the general position that SER seems like an unsupported offering and we should drop it, however we do need to assess if we should and who should pick up SIP router." The I-team also tried to approach OS Ambassadors (sig.oe@sun.com) to get more info about SER usage but no one provided any data. The I-team also looked at IPS download statistics maintained by Stephen Hahn and by end of February 2010 SER reached 24813 downloads as part of OpenSolaris. 2. Documentation Obsoleting SER and SERWeb in Solaris 10 will be announced in release notes for Solaris 10. Interface Stability in SER man page (ser(8)) in Solaris 10 will be set to "Obsolete, External". 3. Packaging and Delivery SUNWserr, SUNWseru and SUNWserweb packages will be removed from OpenSolaris. This does mean that the renamed packages will no longer be delivered (service:network:sip:ser and service:network:sip:ser:administration). 4. Interfaces All the interfaces described below will be obsoleted in Solaris 10 and removed from OpenSolars / SNV. The following files and directories (including all their content) will be removed from OpenSolaris / SNV: /usr/sfw/sbin/ser /usr/sfw/sbin/serctl /usr/sfw/lib/ser/ /usr/sfw/share/doc/ser/ /etc/sfw/ser/ /usr/sfw/share/serweb/ 5. References [1] http://sip-router.org/2008/11/04/the-sip-router-project-launched/ [2] http://sip-router.org/ [3] http://sac.sfbay/LSARC/2004/324/ [4] http://sac.sfbay/PSARC/2006/402/ http://arc.opensolaris.org/caselog/PSARC/2006/402/ [5] http://monaco.sfbay/detail.jsf?cr=6461142-2145051 http://bugs.opensolaris.org/bugdatabase/view_bug.do?bug_id=6461142 [6] http://sac.sfbay/LSARC/2009/277/ http://arc.opensolaris.org/caselog/LSARC/2009/277/ [7] http://monaco.sfbay/detail.jsf?cr=6826484 http://bugs.opensolaris.org/bugdatabase/view_bug.do?bug_id=6826484 [8] http://www.ietf.org/rfc/rfc3261.txt [9] http://www.gnu.org/software/osip/ 6. Resources and Schedule 6.4. Steering Committee requested information 6.4.1. Consolidation C-team Name: sfw 6.5. ARC review type: FastTrack 6.6. ARC Exposure: open