Re: francois' comments and why RFC4474 not used in the field
Paul Kyzivat <[email protected]>
| Newsgroups | gmane.ietf.sip |
|---|---|
| Message-ID | <[email protected]> |
Hans beat me to it with his reply - if there is more than one media stream (e.g. audio/video), and they come from different sources, then what to you display? Dean says these and the signaling identity should match. Modulo the problems we are trying to solve with intermediaries, that will be the situation in the majority of cases. But the general case is: - one, none, or maybe more than one, identity for the signaling - one, none, (or maybe more than one?), identity for each media stream With that jumble of stuff you need to decide what to present to the user. If all are the same then no problem. If you have a UI that permits display of them all, then no problem. (Except user confusion.) But if there is disagreement among the sources and you can only present one, then do you: pick one, or pick none? At the moment that seems to be a common case. We may be able to get some sort of identity for one of these, but can't verify that it applies to all (where "all" usually means signaling + audio) and we can at most display one. Thanks, Paul Dean Willis wrote: > > On Mar 30, 2009, at 8:03 PM, Jiri Kuthan wrote: >> >> There is a timing aspect in favor of placing identity in signaling -- >> I would like to know whose call is ringing before I answer (if I do). > > So, we need identity in signaling, we need identity in media, and we > need the two identity expressions to match. > > That's what we get with RFC 4474 and DTLS/SRTP. > > Why were we trying to change it to protect something else? > > -- > 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 > _______________________________________________ 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