Let me try to explain:
Let's say proxy P1 inserts location information L1, and user agent U1
inserts L2. I want to identity L1 and L2, not necessarily the IP
addresses or host names for proxy P1 or user agent U1 (which may or
may not be unique, if NATs are involved).
The reason is simple - some element may insert location information,
and the poor sender will try to figure out an error for location
information it has never inserted.
I think this should be in all responses, as calls may succeed even if
the location information, or one piece of it, happens to be bad. I
still want to know that the call may have been routed without taking
the location information into consideration, say, and why.
The 3261 generic-param is fine with me.
Henning
On Jul 5, 2007, at 9:45 PM, James M. Polk wrote:
Question - what's the difference between "...he location element
that suffers from the problem identified..." mentioned above and
how you "... don't feel strongly about identifying the originator
of the error". Aren't they the same node?
If not, I need to understand, as I define what ID goes into this
header.
Another point - should this error header only be in the 424 (Bad
Location Information) response, or all 4XX responses, allowing a
transaction to be successful - but without the location piece of
the information exchange being good?
This was discussed, but I don't think the discussion ever concluded.
_______________________________________________
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
