One minor comment: Given that one reason for supporting GET is
generic, non-HELD/PIDF-aware clients, doesn't it seem a little odd
that the GET example includes:
Accept: application/pidf+xml,application/held+xml;q=0.5
It might be a little more realistic to use something like a typical
XHR Accept line:
Accept: application/xml,text/xml;q=0.5,*;q=0.1
On Sep 29, 2010, at 12:28 AM, Thomson, Martin wrote:
> I've made this update to include the changes discussed at IETF-78.
>
> The document now describes what an HTTP GET request means.
>
> Diff here:
> <http://tools.ietf.org/rfcdiff?url2=draft-ietf-geopriv-deref-protocol-01.txt
> >
>
> On 2010-09-29 at 12:15:01, Internet-Drafts@ietf.org wrote:
>> A New Internet-Draft is available from the on-line Internet-Drafts
>> directories.
>> This draft is a work item of the Geographic Location/Privacy Working
>> Group of the IETF.
>>
>>
>> Title : A Location Dereferencing Protocol Using HELD
>> Author(s) : J. Winterbottom, et al.
>> Filename : draft-ietf-geopriv-deref-protocol-01.txt
>> Pages : 23
>> Date : 2010-09-28
>>
>> This document describes how to use the Hypertext Transfer Protocol
>> (HTTP) over Transport Layer Security (TLS) as a dereferencing
>> protocol to resolve a reference to a Presence Information Data Format
>> Location Object (PIDF-LO). The document assumes that a Location
>> Recipient possesses a secure HELD URI that can be used in conjunction
>> with the HELD protocol to request the location of the Target.
>>
>> A URL for this Internet-Draft is:
>> http://www.ietf.org/internet-drafts/draft-ietf-geopriv-deref-
>> protocol-
>> 01.txt
> _______________________________________________
> Geopriv mailing list
> Geopriv@ietf.org
> https://www.ietf.org/mailman/listinfo/geopriv
_______________________________________________
Geopriv mailing list
Geopriv@ietf.org
https://www.ietf.org/mailman/listinfo/geopriv
