Re: [Geopriv] Please note: Re: I-D Action: draft-ietf-geopriv-deref-protocol-06.txt

On 7/12/2012 11:15 AM, Robert Sparks wrote:
> This revision addressed all the points from IESG review.
>
> Notably, it contained a clarification to when TLS is required:
>
> OLD:
>   TLS SHOULD be used.
>
> NEW:
>    TLS MUST be used unless confidentiality and integrity are provided by
>    some other mechanism, such as IPsec or a fully trusted network.
>    Without a reliable assertion that a mechanism is in place, such as
>    through configuration or user override, then TLS MUST be used.
My concerns for this is that the use of the HELD over the TLS transport 
creates the infringement of the US6370629 patent(s) which is/are in 
court over the assignment fraud claim. The next court date is the middle 
of August and the case number is CV165643 in Santa Cruz CA Superior Court.

See the existing IPR filings with the IETF on this issue. Its the same 
one the Timestamp folks face, the DNSSec folks face and you folks face 
as well for all location based services.

Todd Glassey
> If you have a concern with this change, please let me know ASAP.
> If I haven't heard anything I'll approve the document towards the end 
> of next week.
>
> RjS
> On 7/11/12 6:13 PM, 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)       : James Winterbottom
>>                            Hannes Tschofenig
>>                            Henning Schulzrinne
>>                            Martin Thomson
>> 	Filename        : draft-ietf-geopriv-deref-protocol-06.txt
>> 	Pages           : 23
>> 	Date            : 2012-07-11
>>
>> Abstract:
>>     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 URI that can be used in conjunction with the
>>     HTTP-Enabled Location Delivery (HELD) protocol to request the
>>     location of the Target.
>>
>>
>> The IETF datatracker status page for this draft is:
>> https://datatracker.ietf.org/doc/draft-ietf-geopriv-deref-protocol
>>
>> There's also a htmlized version available at:
>> http://tools.ietf.org/html/draft-ietf-geopriv-deref-protocol-06
>>
>> A diff from previous version is available at:
>> http://tools.ietf.org/rfcdiff?url2=draft-ietf-geopriv-deref-protocol-06
>>
>>
>> Internet-Drafts are also available by anonymous FTP at:
>> ftp://ftp.ietf.org/internet-drafts/
>>
>> _______________________________________________
>> 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
>
>
> No virus found in this message.
> Checked by AVG - www.avg.com <http://www.avg.com>
> Version: 2012.0.2195 / Virus Database: 2437/5127 - Release Date: 07/12/12
>

-- 
//Confidential Mailing - Please destroy this if you are not the intended recipient.