> -----Original Message----- > From: Paul Kyzivat [mailto:[EMAIL PROTECTED] > Sent: Thursday, November 20, 2008 9:55 AM > > > Or, if you mean it is a hash of info that will then get munged, the > header needs to be inserted by some box before the munging happens.
Sure, and the question was if that inserting box could be a proxy. The answer is yes, I think. The generator of the Session-ID value should be the UAC, but can be any proxy or b2bua if the UAC did not do it. The later the hop is in the path that does the generation, the less useful it becomes, but that's ok. > And > it still has the property that it is then only usable by those who are > downstream. But that's ok. It's better than what we have now - it works in more cases than what we have now, for cases where one or more b2bua's change the call-id. If nothing in the path changes the call-id, session-id doesn't break anything. That's why I was saying it would be used as an alternative not replacement for things - i.e., if you subscribe for a dialog-event package, you could include both call-id+tag and session-id, such that if call-id+tags didn't match on the UAS, then session-id could be checked as a last resort. If the UAS or UAC doesn't support session-id, that last resort won't succeed or be used either; but that's no worse, and gives a chance for it to succeed which is better. -hadriel _______________________________________________ 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
