Re: [Geopriv] Review of draft-ietf-geopriv-http-location-delivery-07

Eric Rescorla <ekr@networkresonance.com> Mon, 26 May 2008 13:34 UTC

Return-Path: <ietf-bounces@ietf.org>
X-Original-To: ietf-archive@megatron.ietf.org
Delivered-To: ietfarch-ietf-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id C209628C15D; Mon, 26 May 2008 06:34:16 -0700 (PDT)
X-Original-To: ietf@core3.amsl.com
Delivered-To: ietf@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 242F33A68BC; Mon, 26 May 2008 06:34:15 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.604
X-Spam-Level:
X-Spam-Status: No, score=-0.604 tagged_above=-999 required=5 tests=[AWL=-0.109, BAYES_00=-2.599, FH_RELAY_NODNS=1.451, HELO_MISMATCH_COM=0.553, RDNS_NONE=0.1]
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 XluObHJFlGtM; Mon, 26 May 2008 06:34:14 -0700 (PDT)
Received: from kilo.rtfm.com (unknown [74.95.2.169]) by core3.amsl.com (Postfix) with ESMTP id BBA8C28C161; Mon, 26 May 2008 06:33:35 -0700 (PDT)
Received: from kilo.local (localhost [127.0.0.1]) by kilo.rtfm.com (Postfix) with ESMTP id 1F69F2A8B51; Mon, 26 May 2008 06:33:40 -0700 (PDT)
Date: Mon, 26 May 2008 06:33:39 -0700
From: Eric Rescorla <ekr@networkresonance.com>
To: "Tschofenig, Hannes (NSN - FI/Espoo)" <hannes.tschofenig@nsn.com>
Subject: Re: [Geopriv] Review of draft-ietf-geopriv-http-location-delivery-07
In-Reply-To: <C41BFCED3C088E40A8510B57B165C162062CAF@FIESEXC007.nsn-intra.net>
References: <20080525020040.4DE5A5081A@romeo.rtfm.com> <483991AE.9060906@gmx.net> <20080525182946.DF50C2A74DA@kilo.rtfm.com> <4839C06C.5010506@gmx.net> <20080525225416.E5B492A78AF@kilo.rtfm.com> <C41BFCED3C088E40A8510B57B165C162062CAF@FIESEXC007.nsn-intra.net>
User-Agent: Wanderlust/2.15.5 (Almost Unreal) Emacs/22.1 Mule/5.0 (SAKAKI)
MIME-Version: 1.0 (generated by SEMI 1.14.6 - "Maruoka")
Message-Id: <20080526133340.1F69F2A8B51@kilo.rtfm.com>
Cc: GEOPRIV <geopriv@ietf.org>, secdir@mit.edu, draft-ietf-geopriv-http-location-delivery@tools.ietf.org, iesg@ietf.org, ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: IETF Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/pipermail/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: ietf-bounces@ietf.org
Errors-To: ietf-bounces@ietf.org

At Mon, 26 May 2008 10:17:19 +0300,
Tschofenig, Hannes (NSN - FI/Espoo) wrote:
> 
> Hi Ekr, 
> 
> ~snip~
> 
> >> >   
> >> When you operate a network and you want this stuff to work then you 
> >> have to consider this aspect.
> >> In the past a few folks have suggested to write a BCP about how 
> >> different deployments may deal with this aspect but I believe it is 
> >> far too early todo so for a BCP.
> >
> >The problem is that I'm not sure that this is an issue that 
> >can be solved by the network operator. In the example I 
> >described, it sounds to me like new protocol work may be required.
> 
> So far, there was nobody who believed that new protocol work would be
> required. 

Then I think this document needs some editorial work to 
explain this, since as it is, it certainly gave me
that impression.


> >http://tools.ietf.org/id/draft-winterbottom-geopriv-deref-proto
> >col-00.txt
> >
> >What's the status of that document?
> >
> 
> At the last meeting the group agreed that this document should become a
> WG item. 
> I believe my co-author has submitted the document but it got stuck
> somewhere. 
> 
> Thanks for reminding me to ping my co-authors again. 

As noted above, based on my understanding of what you have said,
this needs to be a normative ref.

-Ekr
_______________________________________________
IETF mailing list
IETF@ietf.org
https://www.ietf.org/mailman/listinfo/ietf