1. What specifically is the proposal that we are reviewing? Integration of Session Initiation Protocol (SIP) library. - What is the technical content of the project? Refer to the design document. - Is this a new product, or a change to a pre-existing one? If it is a change, would you consider it a "major", "minor", or "micro" change? See the Release Taxonomy in: It is a change to an existing product - Solaris. Release Taxonomy - "minor" - If your project is an evolution of a previous project, what changed from one version to another? N/A. Note that the project was reviewed earlier as PSARC/2005/451, details are in Question 3 below. - What is the motivation for it, in general as well as specific terms? (Note that not everyone on the ARC will be an expert in the area.) Solaris doesn't provide a native SIP (Session Initiation Protocol) stack. This means that a SIP application developer needs to either use an OpenSource SIP stack that runs on Solaris or purchase a 3rd party SIP stack that runs on Solaris and use the provided API to develop applications. Alternatively, the developer would need to write a SIP stack and embed it in the product itself. Customers are reluctant to use OpenSource stacks for their products. Providing a native SIP stack on Solaris will make Solaris a very attractive platform for VoIP and related application developers. - What are the expected benefits for Sun? SIP is used for setting up/terminating sessions for multimedia applications such as VoIP and IM (Instant Messaging). The market for these applications is huge. Sun hardware is already preferred by Telcos, providing a native SIP stack on Solaris will also make Solaris the preferred platform for SIP application developers. We have been talking to customers and telco groups within Sun (like Global Telco Industry Sales), and support for SIP on Solaris is important. - By what criteria will you judge its success? Delivery of SIP stack that supports RFC 3261, RFC 3262, RFC 3323 and RFC 3325 and accompanying API. 2. Describe how your project changes the user experience, upon installation and during normal operation. N/A 3. What is its plan? - What is its current status? Has a design review been done? Are there multiple delivery phases? Currently development is complete. Design review has also been done. We have made the SIP library available via OpenSolaris since Dec 2005. The binary and source for the library are available via OpenSolaris. We have customers using this library and others planning to use this in their product. We have a Sun Customer in India, Reliance Infocomm, who is already developing a product (Application Server) using Solaris SIP. This particular case is an update to PSARC/2005/451. PSARC/2005/451 was reviewed (inception and commitment) on the 12/21/2005 for the download software on OpenSolaris. This case PSARC/2006/402 updates the interface stability level from unstable to evolving. Other than the change in stability levels, another difference between these two cases is the separation of the URI parser into a separate library (this will be done as a separate case). The main reason for PSARC/2005/451 was to provide the API to SIP developers and get feedback on the same, now we have the required input from customers. Going forwards, there will be future projects to enhance the library to include SIP extensions etc. SDP parser and adding call tracing and logging are some onf the future work items. 4. Are there related projects in Sun? - If so, what is the proposal's relationship to their work? Which not-yet- delivered Sun (or non-Sun) projects (libraries, hardware, etc.) does this project depend upon? What other projects, if any, depend on this one? This project depends on liburi - a URI parser. liburi will be integrated by the same project team. LSARC/2006/182 plans to integrate Ekiga, an open source VoIP and video conferencing application into Solaris. Ekiga uses OPAL library which has H.323 and SIP support. We are in discussion with the Ekiga team (and through them with the community). The community is willing to use Solaris SIP in Ekiga if it runs on Solaris, Linux and Windows. Solaris SIP works on Fedora Core 5 (and should not need much work to run on other flavors of Linux), we are investigating porting efforts on Windows. - Are you updating, copying or changing functional areas maintained by other groups? How are you coordinating and communicating with them? Do they "approve" of what you propose? If not, please explain the areas of disagreement. No. 5. How is the project delivered into the system? - Identify packages, directories, libraries, databases, etc. The library - libsip.so.1 and libsips.so - will be delivered by SUNWcsl in /usr/lib (64-bit in /usr/lib/sparcv9 for SPARC and /usr/lib/amd64 for AMD). The header file - sip.h - will be delivered into /usr/include/protocols byt SUNWhea. Man pages will be delivered by SUNWman in /usr/share/man/ma3lib. 6. Describe the project's hardware platform dependencies. N/A 7. System administration N/A 8. Reliability, Availability, Serviceability (RAS) N/A 9. Observability N/A 10. What are the security implications of this project? None. The library does use MD5 internally to generate hash values for indexing transactions and dialogs and also to generate transaction and dialog ids. The application is responsible for providing the connection manager that includes transport functionalities. Thus, the application handles connection establishment, maintenance etc. In case of a TLS connection, the application creates a SIP message using SIPS URL instead of a SIP URI, so the library is not involved. 11. What is its UNIX operational environment: - Which Solaris release(s) does it run on? The library should run on any Solaris release. - Environment variables? Exit status? Signals issued? Signals caught? (See signal(3HEAD).) None. - Device drivers directly used (e.g. /dev/audio)? .rc/defaults or other resource/configuration files or databases? None. - Does it use any "hidden" (filename begins with ".") or temp files? No. - Does it use any locking files? No. - Command line or calling syntax: What options are supported? (please include man pages if available) Does it conform to getopt() parsing requirements? N/A - Is there support for standard forms, e.g. "-display" for X programs? Are these propagated to sub-environments? N/A - What shared libraries does it use? (Hint: if you have code use "ldd" and "dump -Lv")? # ldd libsip.so.1 libmd5.so.1 => /lib/libmd5.so.1 libc.so.1 => /lib/libc.so.1 libpthread.so.1 => /lib/libpthread.so.1 liburi.so.1 => /usr/lib/liburi.so.1 libnsl.so.1 => /lib/libnsl.so.1 libsocket.so.1 => /lib/libsocket.so.1 libmp.so.2 => /lib/libmp.so.2 libmd.so.1 => /lib/libmd.so.1 libscf.so.1 => /lib/libscf.so.1 libuutil.so.1 => /lib/libuutil.so.1 libm.so.2 => /lib/libm.so.2 /platform/SUNW,Ultra-60/lib/libc_psr.so.1 /platform/SUNW,Ultra-60/lib/libmd_psr.so.1 # /usr/ccs/bin/dump -Lv libsip.so.1 libsip.so.1: **** DYNAMIC SECTION INFORMATION **** .dynamic: [INDEX] Tag Value [1] NEEDED libmd5.so.1 [2] NEEDED libc.so.1 [3] NEEDED libpthread.so.1 [4] NEEDED liburi.so.1 [...] - Identify and justify the requirement for any static libraries. N/A - Does it depend on kernel features not provided in your packages and not in the default kernel (e.g. Berkeley compatibility package, /usr/ccs, /usr/ucblib, optional kernel loadable modules)? No. - Is your project 64-bit clean/ready? If not, are there any architectural reasons why it would not work in a 64-bit environment? Does it interoperate with 64-bit versions? Yes. - Does the project depend on particular versions of supporting software (especially Java virtual machines)? If so, do you deliver a private copy? What happens if a conflicting or incompatible version is already or subsequently installed on the system? N/A - Is the project internationalized and localized? N/A. - Is the project compatible with IPV6 interfaces and addresses? Yes. 12. What is its window/desktop operational environment? N/A - Is it ICCCM compliant (ICCCM is the standard protocol for interacting with window managers)? N/A - X properties: Which ones does it depend on? Which ones does it export, and what are their types? N/A - Describe your project's support for User Interface facilities including Help, Undo, Cut/Paste, Drag and Drop, Props, Find, Stop? N/A. - How do you respond to property change notification and ICCCM client messages (e.g. Do you respond to "save workspace")? N/A - Which window-system toolkit/desktop does your project depend on? N/A - Can it execute remotely? Is the user aware that the tool is executing remotely? Does it matter? No. - Which X extensions does it use (e.g. SHM, DGA, Multi-Buffering? (Hint: use "xdpyinfo") N/A - How does it use colormap entries? Can you share them? N/A - Does it handle 24-bit operation? N/A. 13. What interfaces does your project import and export? - Please provide a table of imported and exported interfaces, including stability levels. Pay close attention to the classification of these interfaces in the Interface Taxonomy -- e.g., "Standard," "Stable," and "Evolving;" see: http://sac.sfbay/cgi-bin/bp.cgi?NAME=interface_taxonomy.bp Use the following format: Interfaces Imported Interface Classification Comments uri_t Evolving uri_str_t Evolving uri_parse() Evolving uri_get_errflags() Evolving uri_get_scheme() Evolving Interfaces Exported Interface Classification Comments SIP_SEND_STATEFUL Evolving SIP_DIALOG_ON_FORK Evolving SIP_CRLF Evolving SIP_SKIP_CRLF Evolving SIP_VERSION Evolving SIP Evolving TO Evolving FROM Evolving FROM_COM Evolving TAG Evolving CONTENT_LENGTH Evolving CONTENT_TYPE Evolving CALL_ID Evolving CSEQ Evolving MAX_FORWARDS Evolving CONTACT Evolving VIA Evolving RECORD_ROUTE Evolving ROUTE Evolving ACCEPT Evolving ACCEPT_ENCODE Evolving ACCEPT_LANG Evolving ALERT_INFO Evolving ALLOW Evolving CALL_INFO Evolving CONTENT_DIS Evolving CONTENT_ENCODE Evolving CONTENT_LANG Evolving DATE Evolving ERROR_INFO Evolving EXPIRE Evolving IN_REPLY_TO Evolving MIN_EXPIRE Evolving MIME_VERSION Evolving ORGANIZATION Evolving PRIORITY Evolving REQUIRE Evolving REPLYTO Evolving RETRY_AFTER Evolving SERVER Evolving SUBJECT Evolving SUPPORT Evolving TIMESTAMP Evolving UNSUPPORT Evolving USER_AGENT Evolving WARNING Evolving ALLOW_EVENTS Evolving EVENT Evolving SUBSCRIPTION_STATE Evolving WWW_AUTHEN Evolving AUTHOR Evolving AUTHEN_INFO Evolving PROXY_AUTHOR Evolving PROXY_AUTHEN Evolving PROXY_REQ Evolving PASSERTEDID Evolving PPREFERREDID Evolving PRIVACY Evolving RACK Evolving RSEQ Evolving SIP_TRYING Evolving SIP_RINGING Evolving SIP_CALL_IS_BEING_FORWARDED Evolving SIP_QUEUED Evolving SIP_SESSION_PROGRESS Evolving SIP_OK Evolving SIP_ACCEPTED Evolving SIP_MULTIPLE_CHOICES Evolving SIP_MOVED_PERMANENTLY Evolving SIP_MOVED_TEMPORARILY Evolving SIP_USE_PROXY Evolving SIP_ALTERNATIVE_SERVICE Evolving SIP_BAD_REQUEST Evolving SIP_UNAUTHORIZED Evolving SIP_PAYMENT_REQUIRED Evolving SIP_FORBIDDEN Evolving SIP_NOT_FOUND Evolving SIP_METHOD_NOT_ALLOWED Evolving SIP_NOT_ACCEPTABLE Evolving SIP_PROXY_AUTH_REQUIRED Evolving SIP_REQUEST_TIMEOUT Evolving SIP_GONE Evolving SIP_REQUEST_ENTITY_2_LARGE Evolving SIP_REQUEST_URI_2_LONG Evolving SIP_UNSUPPORTED_MEDIA_TYPE Evolving SIP_UNSUPPORTED_URI_SCHEME Evolving SIP_BAD_EXTENSION Evolving SIP_EXTENSION_REQUIRED Evolving SIP_INTERVAL_2_BRIEF Evolving SIP_TEMPORARILY_UNAVAIL Evolving SIP_CALL_NON_EXISTANT Evolving SIP_LOOP_DETECTED Evolving SIP_TOO_MANY_HOOPS Evolving SIP_ADDRESS_INCOMPLETE Evolving SIP_AMBIGUOUS Evolving SIP_BUSY_HERE Evolving SIP_REQUEST_TERMINATED Evolving SIP_NOT_ACCEPTABLE_HERE Evolving SIP_BAD_EVENT Evolving SIP_REQUEST_PENDING Evolving SIP_UNDECIPHERABLE Evolving SIP_SERVER_INTERNAL_ERROR Evolving SIP_NOT_IMPLEMENTED Evolving SIP_BAD_GATEWAY Evolving SIP_SERVICE_UNAVAILABLE Evolving SIP_SERVER_TIMEOUT Evolving SIP_VERSION_NOT_SUPPORTED Evolving SIP_MESSAGE_2_LARGE Evolving SIP_BUSY_EVERYWHERE Evolving SIP_DECLINE Evolving SIP_DOES_NOT_EXIST_ANYWHERE Evolving SIP_NOT_ACCEPTABLE_ANYWHERE Evolving SIP_PROVISIONAL_RESP Evolving SIP_FINAL_RESP Evolving SIP_OK_RESP Evolving SIP_NONOK_FINAL_RESP Evolving SIP_REDIRECT_RESP Evolving SIP_REQFAIL_RESP Evolving SIP_SRVFAIL_RESP Evolving SIP_GLOBFAIL_RESP Evolving SIP_CLIENT_TRANSACTION Evolving SIP_SERVER_TRANSACTION Evolving SIPS_NEW_TRANSACTION Evolving SIPS_CLNT_CALLING Evolving SIPS_CLNT_INV_PROCEEDING Evolving SIPS_CLNT_INV_TERMINATED Evolving SIPS_CLNT_INV_COMPLETED Evolving SIPS_CLNT_TRYING Evolving SIPS_CLNT_NONINV_PROCEEDING Evolving SIPS_CLNT_NONINV_TERMINATED Evolving SIPS_CLNT_NONINV_COMPLETED Evolving SIPS_SRV_INV_PROCEEDING Evolving SIPS_SRV_INV_COMPLETED Evolving SIPS_SRV_CONFIRMED Evolving SIPS_SRV_INV_TERMINATED Evolving SIPS_SRV_TRYING Evolving SIPS_SRV_NONINV_PROCEEDING Evolving SIPS_SRV_NONINV_COMPLETED Evolving SIPS_SRV_NONINV_TERMINATED Evolving SIP_UAC_DIALOG Evolving SIP_UAS_DIALOG Evolving SIP_DLG_NEW Evolving SIP_DLG_EARLY Evolving SIP_DLG_CONFIRMED Evolving SIP_DLG_DESTROYED Evolving SIP_PARSED_HEADER_VERSION_1 Evolving SIP_VALUE_VERSION_1 Evolving SIP_VALUE_ACTIVE Evolving SIP_VALUE_BAD Evolving SIP_VALUE_DELETED Evolving MAX_SIP_METHODS Evolving UNKNOWN Evolving INVITE Evolving ACK Evolving OPTIONS Evolving BYE Evolving CANCEL Evolving REGISTER Evolving REFER Evolving INFO Evolving SUBSCRIBE Evolving NOTIFY Evolving PRACK Evolving SIP_STACK_VERSION Evolving SIP_STACK_DIALOGS Evolving sip_msg_t Evolving sip_header_t Evolving sip_header_value_t Evolving sip_dialog_t Evolving sip_conn_object_t Evolving sip_transaction_t Evolving sip_str_t Evolving sip_param_t Evolving sip_parsed_header_t Evolving sip_value_state_t Evolving sip_value_t Evolving sip_hdr_general_t Evolving sip_method_t Evolving sip_methods_t Evolving sip_methods Evolving sip_header_function_t Evolving sip_io_pointers_t Evolving sip_ulp_pointers_t Evolving sip_stack_init_t Evolving sip_init_conn_object Evolving sip_clear_stale_data Evolving sip_conn_destroyed Evolving sip_new_msg Evolving sip_free_msg Evolving sip_hold_msg Evolving sip_stack_init Evolving sip_sendmsg Evolving sip_process_new_packet Evolving sip_guid Evolving sip_branchid Evolving sip_get_cseq Evolving sip_get_rseq Evolving sip_get_num_via Evolving sip_add_from Evolving sip_add_to Evolving sip_add_response_line Evolving sip_add_request_line Evolving sip_add_via Evolving sip_add_maxforward Evolving sip_add_callid Evolving sip_add_cseq Evolving sip_add_content_type Evolving sip_add_content Evolving sip_add_contact Evolving sip_add_route Evolving sip_add_record_route Evolving sip_add_branchid_to_via Evolving sip_add_accept Evolving sip_add_author Evolving sip_add_authen_info Evolving sip_add_proxy_authen Evolving sip_add_proxy_author Evolving sip_add_proxy_require Evolving sip_add_www_authen Evolving sip_add_accept_enc Evolving sip_add_accept_lang Evolving sip_add_alert_info Evolving sip_add_allow Evolving sip_add_call_info Evolving sip_add_content_disp Evolving sip_add_content_enc Evolving sip_add_content_lang Evolving sip_add_date Evolving sip_add_error_info Evolving sip_add_expires Evolving sip_add_in_reply_to Evolving sip_add_mime_version Evolving sip_add_min_expires Evolving sip_add_org Evolving sip_add_priority Evolving sip_add_reply_to Evolving sip_add_require Evolving sip_add_retry_after Evolving sip_add_server Evolving sip_add_subject Evolving sip_add_supported Evolving sip_add_tstamp Evolving sip_add_unsupported Evolving sip_add_user_agent Evolving sip_add_warning Evolving sip_add_allow_events Evolving sip_add_event Evolving sip_add_substate Evolving sip_add_privacy Evolving sip_add_passertedid Evolving sip_add_ppreferredid Evolving sip_add_rack Evolving sip_add_rseq Evolving sip_get_author_scheme Evolving sip_get_author_param Evolving sip_get_authen_info Evolving sip_get_proxy_authen_scheme Evolving sip_get_proxy_authen_param Evolving sip_get_proxy_author_scheme Evolving sip_get_proxy_author_param Evolving sip_get_proxy_require Evolving sip_get_www_authen_scheme Evolving sip_get_www_authen_param Evolving sip_get_allow_events Evolving sip_get_event Evolving sip_get_substate Evolving sip_get_accept_type Evolving sip_get_accept_sub_type Evolving sip_get_accept_enc Evolving sip_get_accept_lang Evolving sip_get_alert_info_uri Evolving sip_get_allow_method Evolving sip_get_min_expires Evolving sip_get_mime_version Evolving sip_get_org Evolving sip_get_priority Evolving sip_get_replyto_display_name Evolving sip_get_replyto_uri_str Evolving sip_get_date_time Evolving sip_get_date_day Evolving sip_get_date_month Evolving sip_get_date_wkday Evolving sip_get_date_year Evolving sip_get_date_timezone Evolving sip_get_content_disp Evolving sip_get_content_lang Evolving sip_get_content_enc Evolving sip_get_error_info_uri Evolving sip_get_expires Evolving sip_get_require Evolving sip_get_subject Evolving sip_get_supported Evolving sip_get_tstamp_delay Evolving sip_get_tstamp_value Evolving sip_get_unsupported Evolving sip_get_server Evolving sip_get_user_agent Evolving sip_get_warning_code Evolving sip_get_warning_agent Evolving sip_get_warning_text Evolving sip_get_call_info_uri Evolving sip_get_in_reply_to Evolving sip_get_retry_after_time Evolving sip_get_retry_after_cmts Evolving sip_get_passertedid_display_name Evolving sip_get_passertedid_uri_str Evolving sip_get_ppreferredid_display_name Evolving sip_get_ppreferredid_uri_str Evolving sip_get_priv_value Evolving sip_get_rack_resp_num Evolving sip_get_rack_cseq_num Evolving sip_get_rack_method Evolvin g sip_get_rseq_resp_num Evolving sip_copy_start_line Evolving sip_delete_start_line Evolving sip_copy_header Evolving sip_copy_header_by_name Evolving sip_copy_all_headers Evolving sip_delete_header_by_name Evolving sip_add_header Evolving sip_add_param Evolving sip_delete_header Evolving sip_delete_value Evolving sip_clone_msg Evolving sip_create_response Evolving sip_create_OKack Evolving sip_get_resp_desc Evolving sip_get_branchid Evolving sip_get_header Evolving sip_get_header_value Evolving sip_get_next_value Evolving sip_get_param_value Evolving sip_get_params Evolving sip_is_param_present Evolving sip_msg_to_str Evolving sip_hdr_to_str Evolving sip_reqline_to_str Evolving sip_respline_to_str Evolving sip_msg_is_request Evolving sip_msg_is_response Evolving sip_get_request_method Evolving sip_get_request_uri_str Evolving sip_get_response_code Evolving sip_get_response_phrase Evolving sip_get_sip_version Evolving sip_get_msg_len Evolving sip_get_route_uri_str Evolving sip_get_route_display_name Evolving sip_get_contact_uri_str Evolving sip_get_contact_display_name Evolving sip_get_from_uri_str Evolving sip_get_from_display_name Evolving sip_get_from_tag Evolving sip_get_to_uri_str Evolving sip_get_to_display_name Evolving sip_get_to_tag Evolving sip_get_callid Evolving sip_get_callseq_num Evolving sip_get_callseq_method Evolving sip_get_via_sent_by_host Evolving sip_get_via_sent_by_port Evolving sip_get_via_sent_protocol_version Evolving sip_get_via_sent_protocol_name Evolving sip_get_via_sent_transport Evolving sip_get_maxforward Evolving sip_get_content_length Evolving sip_get_content_type Evolving sip_get_content_sub_type Evolving sip_get_content Evolving sip_create_dialog_req Evolving sip_get_dialog_state Evolving sip_get_dialog_method Evolving sip_get_dialog_callid Evolving sip_get_dialog_local_tag Evolving sip_get_dialog_remote_tag Evolving sip_get_dialog_local_uri Evolving sip_get_dialog_remote_uri Evolving sip_get_dialog_remote_target_uri Evolving sip_get_dialog_route_set Evolving sip_is_dialog_secure Evolving sip_get_dialog_local_cseq Evolving sip_get_dialog_remote_cseq Evolving sip_get_dialog_type Evolving sip_hold_dialog Evolving sip_release_dialog Evolving sip_delete_dialog Evolving sip_get_request_uri Evolving sip_get_uri_parsed Evolving sip_sent_by_to_str Evolving sip_register_sent_by Evolving sip_unregister_sent_by Evolving sip_unregister_all_sent_by Evolving sip_get_trans Evolving sip_get_trans_branchid Evolving sip_get_trans_method Evolving sip_get_trans_state Evolving sip_get_trans_resp_msg Evolving sip_get_trans_orig_msg Evolving sip_hold_trans Evolving sip_release_trans Evolving sip_get_trans_conn_obj Evolving - Exported public library APIs and ABIs see above. Protocols (public or private) Drag and Drop ToolTalk Cut/Paste - Other interfaces - What other applications should it interoperate with? How will it do so? N/A - Is it "pipeable"? How does it use stdin, stdout, stderr? No. - Explain the significant file formats, names, syntax, and semantics. - Is there a public namespace? (Can third parties create names in your namespace?) How is this administered? N/A - Are the externally visible interfaces documented clearly enough for a non-Sun client to use them successfully? Yes these interfaces will be documented in man pages. 14. What are its other significant internal interfaces inter-subsystem and inter-invocation)? N/A 15. Is the interface extensible? How will the interface evolve? - How is versioning handled? Through the standard ON library practise through spec. - What was the commitment level of the previous version? N/A - Can this version co-exist with existing standards and with earlier and later versions or with alternative implementations (perhaps by other vendors)? Yes. - What are the clients over which a change should be managed? N/A - How is transition to a new version to be accomplished? What are the consequences to ISV's and their customers? If any of the interfaces change, then the application would need to changes. 16. How do the interfaces adapt to a changing world? N/A - What is its relationship with (or difficulties with) multimedia? 3D desktops? Nomadic computers? Storage-less clients? A networked file system model (i.e., a network-wide file manager)? N/A 17. Interoperability - If applicable, explain your project's interoperability with the other major implementations in the industry. In particular, does it interoperate with Microsoft's implementation, if one exists? The SIP stack conforms to specifications in the RFCs that are suppported (3261, 3262, 3265, 3323 and 3325), so it will interoperate with any implementation that is based on the RFCs. - What would be different about installing your project in a heterogeneous site instead of a homogeneous one (such as Sun)? N/A - Does your project assume that a Solaris-based system must be in control of the primary administrative node? N/A 18. Performance - How will the project contribute (positively or negatively) to "system load" and "perceived performance"? N/A - What are the performance goals of the project? How were they evaluated? What is the test or reference platform? We have provided some tools to measure the stack performance, especially the transaction and dialog management layer. These tools are available on the OpenSolaris site and are being used by customers. - Does the application pause for significant amounts of time? Can the user interact with the application while it is performing long-duration tasks? N/A - What is your project's MT model? How does it use threads internally? How does it expect its client to use threads? If it uses callbacks, can the called entity create a thread and recursively call back? The library is MT-safe. The library does not impose applications to be single or multithreaded. The library does use a thread internally to manage timers used by the stack. As for recursively calling a callback function, there may be a possibility that an application registers a callback function for transaction state changes and the callback function creates a thread and sends a message that changes the transaction state resulting in calling the callback function again. But, this seems unlikely. - What is the impact on overall system performance? What is the average working set of this component? How much of this is shared/sharable by other apps? An application linked with the new library, libsip.so, increases in size (i.e. the executable) by about 32 bytes. - Does this application "wake up" periodically? How often and under what conditions? What is the working set associated with this behavior? N/A - Will it require large files/databases (for example, new fonts)? N/A - Do files, databases or heap space tend to grow with time/load? What mechanisms does the user have to use to control this? What happens to performance/system load? The memory used depends on the number of SIP messages, transaction and dialog state maintained in the system. Transactions are short lived (either terminate or time out), dialog may be long-lived and are explicitly terminated. Messages, transactions and dialogs can be prevented from being terminated by holding references to it. Applications can control memory usage by holding references only when needed and releasing them when done. 19. Please identify any issues that you would like the ARC to address. - 20. Appendices to include - One-Pager. - Prototype specification. - References to other documents. (Place copies in case directory.)