Commitment: SIP Library Integration (2006/402)
Submitter: Venugopal Iyer
Owner: Jim Carlson


SUMMARY
=======
* TCR - make sip fail
* Some language problems in the man pages - nit, clean up the English

* Spec update - warning

ISSUES
======
kb-01	SIP stack initialization - sip_stack_init() is not idempotent. 
	any words of caution from calling sip_stack_init() by other
 	libraries? the example in mind is a prohram that explicitly
	calls sip_stack_init(), and is linked to library that in turn calls
	that function.

* An app links to a library which creates the stack.
* sib doesn't re-initialize the stack - project team doesn't feel like it would be agood idea to have two libs sync up together and use sip.
* TCR - update document about how sip cannot be used with libraries


kb-02	Writing parsers for custom headers -
	Who's responsible for freeing the sip_padrsed_header_t allocated
	by the parser, (uncluding the chains of sip_value_t dangling off it) ?
	Should applications providing custom headers parsing also provide
	a destrutor for the objects those parsers create?

kb-03	Life of transaction hash table across forks. Any risk of parent and
	child competing on transaction?

* Transaction is in progress when request is processing. A transaction is essentially sends a request and creates a transaction. If information is read from the socket, it comes from the child or the parent and then it is send to processing.

Other issues
------------
* Some language problems in the man pages - nit, clean up the English


VOTE
====
yes - gary, kais, glenn, ed, jim, bill
no - 
abstain - 
NP - 



NEXT STEP
=========
* case was approved during commitment
* waiting need opinion