Re: [Hipsec] Comments on draft-cao-hip-geolocation

"Hannes Tschofenig" <Hannes.Tschofenig@gmx.net> Tue, 18 November 2008 01:30 UTC

Return-Path: <hipsec-bounces@ietf.org>
X-Original-To: hip-archive@lists.ietf.org
Delivered-To: ietfarch-hip-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id B9FCB28C1DA; Mon, 17 Nov 2008 17:30:18 -0800 (PST)
X-Original-To: hipsec@core3.amsl.com
Delivered-To: hipsec@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 604EE28C1D7 for <hipsec@core3.amsl.com>; Mon, 17 Nov 2008 17:30:17 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.167
X-Spam-Level:
X-Spam-Status: No, score=-1.167 tagged_above=-999 required=5 tests=[AWL=0.363, BAYES_00=-2.599, DATE_IN_PAST_06_12=1.069]
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 y2ZQO9SwZmeP for <hipsec@core3.amsl.com>; Mon, 17 Nov 2008 17:30:16 -0800 (PST)
Received: from mail.gmx.net (mail.gmx.net [213.165.64.20]) by core3.amsl.com (Postfix) with SMTP id 35FDA28C1A0 for <hipsec@ietf.org>; Mon, 17 Nov 2008 17:30:16 -0800 (PST)
Received: (qmail invoked by alias); 18 Nov 2008 01:30:14 -0000
Received: from unknown (EHLO 4FIL42860) [130.129.31.217] by mail.gmx.net (mp049) with SMTP; 18 Nov 2008 02:30:14 +0100
X-Authenticated: #29516787
X-Provags-ID: V01U2FsdGVkX1/Aso8gPefAapiHBdVYi+/scQH/NF6VTReGLq7GdX UzgCR2OG0VVjuA
From: "Hannes Tschofenig" <Hannes.Tschofenig@gmx.net>
To: "'Hui Deng'" <denghui02@gmail.com>, "'Cullen Jennings'" <fluffy@cisco.com>, "'Hui Deng'" <denghui@chinamobile.com>
References: <AB6DC025-4872-412B-98E7-A3AE0E84404F@cisco.com> <1d38a3350811171724m6a7f2f84la1b47dcf2ac5b5c5@mail.gmail.com>
Date: Mon, 17 Nov 2008 19:30:12 +0200
Message-ID: <016c01c948da$279c60c0$6612a20a@nsnintra.net>
MIME-Version: 1.0
X-Mailer: Microsoft Office Outlook 11
In-Reply-To: <1d38a3350811171724m6a7f2f84la1b47dcf2ac5b5c5@mail.gmail.com>
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.3350
Thread-Index: AclJHGsCm8X0lq+BROyes8RGMWTIPgAQmSWg
X-Y-GMX-Trusted: 0
X-FuHaFi: 0.85
Cc: 'HIP' <hipsec@ietf.org>
Subject: Re: [Hipsec] Comments on draft-cao-hip-geolocation
X-BeenThere: hipsec@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: "This is the official IETF Mailing List for the HIP Working Group." <hipsec.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/hipsec>, <mailto:hipsec-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/pipermail/hipsec>
List-Post: <mailto:hipsec@ietf.org>
List-Help: <mailto:hipsec-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/hipsec>, <mailto:hipsec-request@ietf.org?subject=subscribe>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: hipsec-bounces@ietf.org
Errors-To: hipsec-bounces@ietf.org

I believe that conveying location in HIP is a misguided approach. 
Wrong layer! 
 


________________________________

	From: hipsec-bounces@ietf.org [mailto:hipsec-bounces@ietf.org] On
Behalf Of Hui Deng
	Sent: 18 November, 2008 03:25
	To: Cullen Jennings; Hui Deng
	Cc: HIP
	Subject: Re: [Hipsec] Comments on draft-cao-hip-geolocation
	
	
	Hi, Cullen,
	 
	Thanks for your comments, 
	 
	It could be understand from another direction, if the mobile users
use HIP. Here are some reasons listed below. 

	-- HIP has the  security mechanisms (i.e. ENCRYPTED) 
	-- GEOPRIV security framework can be integrated into HIP call flow
	-- the geo-location changes of mobile user may not be cared or
covered by many applications.
	-- delivering geo-location in HIP can provide the generic mechanism
and interface for the up-layer applications; 
	-- delivering geo-location in HIP can greatly reduce the redundant
work for up-layer applications.
	
	Basically, operator sometime prefer use infrastructure layer to
transmit this information.
	 
	thanks for your understanding.
	Best regards,
	 
	-Hui Deng
	
	2008/11/15 Cullen Jennings <fluffy@cisco.com>
	


		Due to the requirements of managing the privacy of geo and
civil location information, I think this type of information is much better
transfered at an application layer than at the transport layer.
		
		Cullen in my individual contributor role
		
		_______________________________________________
		Hipsec mailing list
		Hipsec@ietf.org
		https://www.ietf.org/mailman/listinfo/hipsec
		



_______________________________________________
Hipsec mailing list
Hipsec@ietf.org
https://www.ietf.org/mailman/listinfo/hipsec