Re: [Geopriv] draft-ietf-geopriv-dhcp-lbyr-uri-option-04

"Hannes Tschofenig" <Hannes.Tschofenig@gmx.net> Thu, 26 March 2009 17:28 UTC

Return-Path: <Hannes.Tschofenig@gmx.net>
X-Original-To: geopriv@core3.amsl.com
Delivered-To: geopriv@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 4888F3A684B for <geopriv@core3.amsl.com>; Thu, 26 Mar 2009 10:28:14 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.345
X-Spam-Level:
X-Spam-Status: No, score=-2.345 tagged_above=-999 required=5 tests=[AWL=0.254, BAYES_00=-2.599]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 7L841xJE-qxg for <geopriv@core3.amsl.com>; Thu, 26 Mar 2009 10:28:13 -0700 (PDT)
Received: from mail.gmx.net (mail.gmx.net [213.165.64.20]) by core3.amsl.com (Postfix) with SMTP id 53AB13A6920 for <geopriv@ietf.org>; Thu, 26 Mar 2009 10:27:53 -0700 (PDT)
Received: (qmail invoked by alias); 26 Mar 2009 17:28:45 -0000
Received: from dhcp-14f7.meeting.ietf.org (EHLO 4FIL42860) [130.129.20.247] by mail.gmx.net (mp044) with SMTP; 26 Mar 2009 18:28:45 +0100
X-Authenticated: #29516787
X-Provags-ID: V01U2FsdGVkX181Su8VUCE1ZvaI9JDmFjq2D93xD2uieM8jFFOQzm yVNaCSOw+bNEmf
From: Hannes Tschofenig <Hannes.Tschofenig@gmx.net>
To: 'Marc Linsner' <mlinsner@cisco.com>, 'GEOPRIV' <geopriv@ietf.org>
References: <032901c9ae33$b0043280$f7148182@nsnintra.net> <C5F101E0.13809%mlinsner@cisco.com>
Date: Thu, 26 Mar 2009 10:29:58 -0700
Message-ID: <032a01c9ae38$7e81fee0$f7148182@nsnintra.net>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
X-Mailer: Microsoft Office Outlook 11
Thread-Index: AcmuM64Umw7/HXD5QDGCd6aqhudFPQAACvjHAADHqKA=
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.3350
In-Reply-To: <C5F101E0.13809%mlinsner@cisco.com>
X-Y-GMX-Trusted: 0
X-FuHaFi: 0.5600000000000001
Subject: Re: [Geopriv] draft-ietf-geopriv-dhcp-lbyr-uri-option-04
X-BeenThere: geopriv@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Geographic Location/Privacy <geopriv.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/geopriv>, <mailto:geopriv-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/geopriv>
List-Post: <mailto:geopriv@ietf.org>
List-Help: <mailto:geopriv-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/geopriv>, <mailto:geopriv-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 26 Mar 2009 17:28:14 -0000

Hi Marc, 


don't know whether this is the model that James has in mind. 

Please also note the paragraph at the end of Section 4.3: 

   It should also be noted that while the lybr requirements document
   specifies a requirement that a client SHOULD be able to cancel
   location references, the protocol specified in this document does not
   provide that functionality.  The mechanism to provide this support in
   the protocol requires explicit management of Target state on the LIS.
   It is anticipated that extensions to HELD may support that
   requirement.

This paragraph refers to functionality similar to
http://tools.ietf.org/id/draft-winterbottom-geopriv-held-context-03.txt.
That document might not be too applicable to your solution as a concrete
mechanism but the idea is similar. 

Btw, I noticed a mismatch with the    
http://tools.ietf.org/html/draft-ietf-geopriv-lbyr-requirements-07
Document: 
"
C3. Location URI cancellation:  The location configuration protocol
      MUST support the ability to request a cancellation of a specific
      location URI.
"

You could also say that the following requirements stated in
http://tools.ietf.org/html/draft-ietf-geopriv-lbyr-requirements-07 by this
document in it's current form: 

   C6. Reuse indicator:  There SHOULD be a way to allow a client to
      control whether a location URI can be resolved once only, or
      multiple times.


   C7. Selective disclosure:  The location configuration protocol MUST
      provide a mechanism to control what information is being disclosed
      about the Target.

Ciao
Hannes

>-----Original Message-----
>From: Marc Linsner [mailto:mlinsner@cisco.com] 
>Sent: 26 March, 2009 09:57
>To: Hannes Tschofenig; 'GEOPRIV'
>Subject: Re: [Geopriv] draft-ietf-geopriv-dhcp-lbyr-uri-option-04
>
>Hannes,
>
>Would the words from section 4.3 of the HELD draft satisfy this?
>
>-Marc-
>
>
>On 3/26/09 9:55 AM, "Hannes Tschofenig" 
><Hannes.Tschofenig@gmx.net> wrote:
>
>> Regarding the discussion we had at the meeting today I believe I am 
>> only asking for a description on the expected semantic of 
>the LbyR for 
>> usage with this document to make sure that we have a common 
>> understanding of the security / privacy properties.
>> 
>> I don't think that my request goes too far.
>> 
>> Thanks. 
>> 
>> Ciao
>> Hannes
>> 
>> 
>> _______________________________________________
>> Geopriv mailing list
>> Geopriv@ietf.org
>> https://www.ietf.org/mailman/listinfo/geopriv
>
>