>> >More seriously: I'm not entirely sure how to interpret responseTime
>> >in the context of a SIP PA. This might work as you have described,
>> >but I would suggest that it complicates things
>considerably. There's
>> >discussion on this point in my draft here:
>> >
>> ><http://tools.ietf.org/html/draft-thomson-simple-cont-presence->val
>> -req-02#section-4.6.1.1>
>> >
>> >I don't know how to solve this problem yet.
>> >
>>
>>I am not sure I see the problems.
>>
>>Imagine a SIP proxy receives a SIP message with an LbyR and wants to
>>retrieve location information for routing. Depending on the
>URI scheme
>>(HTTP vs. SIP) he would either use
>>http://tools.ietf.org/id/draft-winterbottom-geopriv-deref-prot
>ocol-03.t
>>xt
>>Or
>>http://www.ietf.org/internet-drafts/draft-ietf-geopriv-loc-fil
>ters-04.t
>>xt
>
>I'm confused.
>
>For SIP, why would the filters doc be used when Conveyance
>already has how a server dereferences a location URI for routing?
>
>This isn't a soliciting action requiring filters.
How does SIP Location Conveyance dereference location URIs?
My reading of draft-ietf-sip-location-conveyance was that it conveys
location by value and/or by reference.
What "indication" is used in a SIP SUBSCRIBE to indicate "Please give me
location information suitable for routing."?
Ciao
Hannes
_______________________________________________
Geopriv mailing list
Geopriv@ietf.org
https://www.ietf.org/mailman/listinfo/geopriv
