New topic -- Do we want at all to try and tackle mapping of which
location goes with which error, to make sure each receiver of the
response pays attention or ignores what they are supposed to (wrt
locationValues)?
If this is a good idea, would a header parameter sequence number
(mapped between Geolocation header and Geolocation-Error header) do
the trick? I think we'll just need to make sure the numbers don't
replicate another sequence number within the same Call-ID, and not
be universally unique through space and time.
Agreed.
This might be a little too much to take on this late (to the
deadline) or it just might be too silly of an idea *or* do you
think the host ID within the Geolocation-Error header might be
enough to cover this idea.
I'm not sure what format the hostID has. If IP address, you could end
up with two 192.168.0.1, from different hosts, which would be rather
confusing.
_______________________________________________
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
