On Fri, 2008-12-05 at 13:43 -0500, Hadriel Kaplan wrote: > > From: Dale Worley [mailto:[EMAIL PROTECTED] > > > > I think you're getting into a lot of trouble with this. For one thing, > > if a request forks, it creates multiple dialogs. If the UAC inserted a > > session-id, all those dialogs share the same session-id. Previously, > > that situation is disambiguated by identifying a dialog by giving > > call-id/from-tag/to-tag. But session-id alone is ambiguous, so it can't > > be used to replace the current dialog identifiers. And since we assume > > that the tags will be changed by B2BUAs, session-id/from-tag/to-tag > > won't work at all. > > No - read the (latest) draft. The to-tag is in fact also used, to > dis-ambiguate these things. And I note that this would mean it can't > be changed. I'm on the fence whether to create a surrogate for that > as well. (ugh)
But B2BUAs now change to-tags, so we don't have the "works in most current deployments" condition. Also, to-tags may have the same problem as call-ids, namely that they reveal the manufacturer of the originating UA. I think the mechanism needs to be revised to deal with this. Dale _______________________________________________ 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
