On Apr 23, 2008, at 12:29 PM, [EMAIL PROTECTED] wrote: > Hi, > I have been an user of SIP for a while, but never got into the > need to extend it. I have tried to do an extensive research to see > if there are any draft or RFC that handles the requirements that I > am requested to do. Here is the scenario that I am trying to fulfill. > > A UA (custom hardware/software) wants to place or change the call > into a secure call. It notifies the other participant by an INVITE > or NOTIFY and both UA agree on the change and the details of the > security. There are several different method of securing the call, > and that would be included in the parameter passed between the UA. > If this is not possible is there a way to embed the parameters into > the header of the INVITE or NOTIFY so at least both UA know of the > request? >
What do you mean, "secured call"? This term means many different things to even more different people. You might look at: http://www.ietf.org/internet-drafts/draft-ietf-sip-sips-08.txt which has completed working group last call and I'm about to send to the IESG, and at: http://www.ietf.org/internet-drafts/draft-ietf-sip-media-security-requirements-04.txt and http://www.ietf.org/internet-drafts/draft-ietf-sip-dtls-srtp-framework-01.txt which, if I recall aright, are currently in working group last call. -- Dean _______________________________________________ Sip mailing list https://www.ietf.org/mailman/listinfo/sip This list is for NEW development of the core SIP Protocol Use [EMAIL PROTECTED] for questions on current sip Use [EMAIL PROTECTED] for new developments on the application of sip
