At 06:41 PM 7/7/2007, Henning Schulzrinne wrote:
I'm not sure either if PSAPs reeeeally care if location was
inserted by a UAC or proxy along the way - they just want
something. It sounded good when I first came up with the idea, but
it is also merely informative in nature, and has zero integrity.
I agree that the PSAP doesn't care who inserted the information and
there's really not much difference between one inserted by a proxy
and the end system, as far as the PSAP is concerned. The only one
that cares is probably the caller (UAC), mostly if things go wrong.
It can be really frustrating if some crucial information is inserted
by some proxy you can't see, and you have no idea who did it and thus
don't know if you should talk to your local provider or some other
party closer to the destination. I don't know whether this is a
realistic issue, given that most location information will be
inserted either by the UAC or the outbound proxy.
Thus, maybe it would be sufficient to make the suitable extensibility
hooks in both the Geolocation header and the error indication so that
these can be added later, if we can't agree quickly on a suitable
format.
as much as anything, I'm thinking of going with your proposal to
change "inserted-by=endpoint or server" to "inserted-by=host-id/name"
so that transaction statefulness of location insertion is easier to
recognize in a response.
This would blow up the idea of indicating if a locationValue was
inserted by a endpoint or server... that was my point.
It also gets us away from tracking a sequence number (of what
length?) and having to nail down all the parameters of that new value
- consensus might be in 2009 on this one with a number
_______________________________________________
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
