Brian Rosen wrote:
Yeah, I wanted to limit options. I wanted two representations of the same
location as a single header. I'm not really stuck on that, but cutting down
on options is good.
The general approach of allowing multiple valued headers to appear by
repeating the header or using comma separated values is quite deeply
embedded. Making an exception for one header would IMO be far worse than
being consistent with all the other multivalued headers.
The stacks I know of handle this internally. An exception will require
more code, not less.
Paul
Brian
-----Original Message-----
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]
Sent: Tuesday, May 01, 2007 1:33 PM
To: [email protected]
Subject: Re: [Sip] Location-conveyance: ISSUE #3 - multiple locations
From: Henning Schulzrinne <[EMAIL PROTECTED]>
> 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
What it must mean is:
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 two locationValues, both containing inserted-by
geloloc-params with the same value.
For example:
Geolocation: <cid:[email protected]>;inserted-by=endpoint
Geolocation: <sips:[EMAIL PROTECTED]>;inserted-
by=endpoint
or
Geolocation: <cid:[email protected]>;inserted-by=endpoint,
<sips:[EMAIL PROTECTED]>;inserted-by=endpoint
Dale
_______________________________________________
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
_______________________________________________
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
_______________________________________________
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
