Rosen, Brian wrote:
An issue raised by reviewers for location-conveyance was how it works if
the UAS tries to send its location to the UAC. There are several things
that are problematic with this, including errors: the UAC can't tell the
UAS about an error it finds in the location.
We propose to resolve this by specifying that location-conveyance sends
the location of the UAC. The header can appear in a message from the
UAS to the UAC, but it means that the UAS is looping back the location
of the UAC.
The other end can send its location with an UPDATE or ReINVITE, turning
around the connection (i.e. becoming the UAC).
The loopback procedure is useful when proxies insert location. The UAC
may not even be aware that it happened, and yet it gets an error or a
result it doesn't understand. If the UAS echo's what it gets, the UAC
can see it.
If this proposal finds favor with the working group, we will modify the
text in the next revision of -conveyance to incorporate it.
This sounds wise to me.
Something that bears further discussion: is an intermediate node
permitted to drop the location from a response? I think there are
competing interests here - some intermediate nodes may want to drop it,
while the UAC would prefer to have it retained.
Paul
_______________________________________________
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
