Re: [Sip-implementors] SRTP key transmission

2009-06-04 Thread Vadim Lebedev
You're right it is inconvenience, However in e-mail applications for example it is not considered to be inconvenient, The public keys can be retrieved and stored in the address book in the same way as secure email software does... Thanks Vadim Paul Kyzivat wrote: > A significant limitation in wh

Re: [Sip-implementors] SDP in Session Refresh Request

2009-06-04 Thread shamik.saha
Hi Paul, When the re-invite reaches the other end will it searches for the best bandwith codec again from the offered codecs even if the VERSION number is the same in the re-invite as the original invite. Thanks and regards, Shamik Saha Project Engineer Voice Protocols Cell : +91-9886704155 -

Re: [Sip-implementors] SDP in Session Refresh Request

2009-06-04 Thread Paul Kyzivat
Attila Sipos wrote: > One more thing. > > I have seen UAs refresh the session using an UPDATE without any SDP. > Doing it this way doesn't change any of the codecs. > > RFC 4028 says: > It is RECOMMENDED that the UPDATE request not contain an >offer [4], but a re-INVITE SHOULD contain one,

Re: [Sip-implementors] SDP in Session Refresh Request

2009-06-04 Thread Attila Sipos
One more thing. I have seen UAs refresh the session using an UPDATE without any SDP. Doing it this way doesn't change any of the codecs. RFC 4028 says: It is RECOMMENDED that the UPDATE request not contain an offer [4], but a re-INVITE SHOULD contain one, even if the details of the sessio

Re: [Sip-implementors] 200OK without SDP.

2009-06-04 Thread Paul Kyzivat
Good answers. Also look at http://www.ietf.org/internet-drafts/draft-ietf-sipping-sip-offeranswer-10.txt Paul Attila Sipos wrote: > yes, the call flow is fine. > > But I can understand why you are confused. > The important part is this: > For this specification, that is >

Re: [Sip-implementors] SRTP key transmission

2009-06-04 Thread Paul Kyzivat
A significant limitation in what you propose is that it requires Bob to have a public key that Alice knows. In general we don't find that to be the case in most telephony applications. Thanks, Paul Vadim Lebedev wrote: > I see, > Well this particular attack could be prevented by

[Sip-implementors] sip-implementors

2009-06-04 Thread anjan naik
Hi, This is Anjan. Joined this mailing list today. /Anjan. ___ Sip-implementors mailing list Sip-implementors@lists.cs.columbia.edu https://lists.cs.columbia.edu/cucslists/listinfo/sip-implementors

Re: [Sip-implementors] Doubt in Instant Message

2009-06-04 Thread Avasarala Ranjit-A20990
In standard SMS, its 162 characters. But in case of standard IM clients like Gtalk, Yahoo messenger, it depends more on the IM client. Regards Ranjit -Original Message- From: sip-implementors-boun...@lists.cs.columbia.edu [mailto:sip-implementors-boun...@lists.cs.columbia.edu] On Beh

Re: [Sip-implementors] Doubt in Instant Message

2009-06-04 Thread Shanbhag, Somesh (NSN - IN/Bangalore)
I think if its RFC 3428, ist upto 1300 bytes, but depends on the MTU and other parameters. Somesh -Original Message- From: sip-implementors-boun...@lists.cs.columbia.edu [mailto:sip-implementors-boun...@lists.cs.columbia.edu] On Behalf Of ext friend friend Sent: Thursday, June 04, 20

[Sip-implementors] Doubt in Instant Message

2009-06-04 Thread friend friend
Dear Experts,     How many characters should be supported in Standard Instant messaging?      Is any standard size available or its depends on requirement?   Please advice me.   Thanks & Regards, vijay Bollywood news, movie reviews, film trailers and more! Go to http://in.movies.y