>>If 3GPP decides to use something other than DTLS-SRTP, we will have >>two standards for SRTP keying -- the IETF standard and the non-IETF >>standard. I do not consider that desirable. >> > >Why should crypto be different than the underlying protocol? >The bifurcation between "IETF SIP" and "3GPP SIP" already >exists in the market. > ><http://www.nostrum.com/~adam/images/too-late.png>
I don't understand this "IETF SIP" versus "3GPP SIP" thing. "3GPP SIP" is a SIP profile, including a number of SIP extensions, all done in IETF. There is nothing which a non-3GPP entity can't use. What is "IETF SIP"? What do I have to implement in order to be "IETF SIP" compliant? RFC3261? RFC3261 plus each and every extension out there? Also, DTLS-SRTP is not the only mechanism defined in IETF for key management. The 3GPP might come to a conclusion based on their requirements that one of the other IETF mechanisms is better suited. This would then also only be a profiling of IETF, and not diverge from IETF. Regards, Christer _______________________________________________ Sip mailing list https://www1.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
