On May 1, 2007, at 11:53 AM, Brian Rosen wrote:
Proposed text for this subject:
Sending multiple locations (multiple Geolocation headers, or multiple
locationValues in a single Geolocation header is confusing to the
UAS. It
has no way to decide what these mean, and how to use them. There
are a few
exceptions to this general statement. The UAC may have both a
reference and
a value, and may wish to send them together. The value is the current
location of the UAC when sent, and the reference may be used to
obtain a
more current (and possibly more accurate) location later. Also, a
proxy
server may assert location even if the UAC provided location. In
this case,
the inserted-by value would be different. Finally, applications of
location
different from what?
Do you mean that they differ from each other?
may specify specific behavior for multiple locations and thus blanket
prohibition of such is ill advised.
Therefore:
A UAC or proxy wishing to supply both a reference and a value,
representing
the location of the UAC from the same source, MUST provide a single
Geolocation header, with two locationValues, and an inserted-by value.
That doesn't work, unless I'm misunderstanding what you mean.
Geolocation: x
Geolocation: y
is exactly the same (syntactic transformation) as
Geolocation: x, y
Otherwise, and in the absence of application specific guidance,
multiple
Geolocation headers and multiple locationValues with the same
inserted-by
value SHOULD NOT be used.
_______________________________________________
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
