> -----Original Message----- > From: Ian Elz [mailto:[EMAIL PROTECTED] > Sent: Friday, December 05, 2008 5:30 AM > > >-----Original Message----- > >From: Hadriel Kaplan [mailto:[EMAIL PROTECTED] > >Sent: 03 December 2008 20:23 > > > >Actually, there *is* a way of making a Proxy in the path, depending on > >where the Proxy is. If it's the edge proxy between the UAC and its > >registrar, have it insert itself in the Path header for the Register, > and > >any/all requests trying to get to that UA using GRUU/AoR should in > theory > >go through that Proxy. > > [Ian Elz ] Thus it is only a proxy which is includes itself in the Path > header during registration which is allowed to insert a session-id.
Nope, that's just one example. You said there was no way to make a Proxy be in the path for out-of-dialog requests, and I said sure there is. You could also have a one-and-only Proxy for accepting requests from outside your domain, which could do the matching. Or the Proxy could be the Registrar for your domain, which is always traversed to reach registered UAs. Again, though - this is not about who can generate a Session-ID. It's about who can do the matching. Every hop can try to do matching for all I care. It won't affect interoperability or add failure cases where previously there were success cases. It's only at a MAY level - you don't have to do it if you don't want to. > [Ian Elz ] But having a proxy insert a session-id is not fixing > anything. I am not arguing against the session-id at this point just > allowing proxies to invent one and add then in the middle of a request. > Allowing the proxy to add a session-id requires that the proxy must be > included in the message sequence for the new request using the > session-id as a reference and it must also remember that it inserted the > session-id and map the session-id <--> call-id & tags from one side to > the other when they are used as a reference. Nope, it doesn't require that at all. See the draft - it's at a MAY to do matching. I think you may be reading something into the draft that it doesn't say: that only a Session-ID *generator* can do matching? The draft doesn't say that, nor did I intend it if it does. :) Should I put words in the draft making that clearer? -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
