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

"Hui Deng" <denghui02@gmail.com> Tue, 18 November 2008 01:24 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 5551D28C0E6; Mon, 17 Nov 2008 17:24:35 -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 9867C28C0E6 for <hipsec@core3.amsl.com>; Mon, 17 Nov 2008 17:24:33 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.598
X-Spam-Level:
X-Spam-Status: No, score=-2.598 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HTML_MESSAGE=0.001]
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 sCODrS9I+Bbr for <hipsec@core3.amsl.com>; Mon, 17 Nov 2008 17:24:32 -0800 (PST)
Received: from ey-out-2122.google.com (ey-out-2122.google.com [74.125.78.24]) by core3.amsl.com (Postfix) with ESMTP id 4B4D83A6922 for <hipsec@ietf.org>; Mon, 17 Nov 2008 17:24:32 -0800 (PST)
Received: by ey-out-2122.google.com with SMTP id 9so1072439eyd.31 for <hipsec@ietf.org>; Mon, 17 Nov 2008 17:24:30 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:message-id:date:from:to :subject:cc:in-reply-to:mime-version:content-type:references; bh=0cPsgvUolIWGwCwG2UCXpQ4S6ohpmSRPyE+9zMAMYqk=; b=iKyw8JLUziPOmmEjAUOXH5xfU52kqTfwxU6cz3Bfnm2FE+htFLfEicb5G5feME0ita KJg5F1eEwRiSC/AmUqTSDK8nTOgEwEmNRVTbzdtFP8SDz6OmeO466F2d9LFi2WAa17aE FvlXUdL2mRH35E9BzHcmz7G+8NDQM8oeBZeaM=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:from:to:subject:cc:in-reply-to:mime-version :content-type:references; b=LbNXzSimJEH5zEQNv+oD6S4VgxwXnoN+9hkXKiDWdJPSR0jG7DfZ72aWKEhh8uEO5P cqi6EfzRm5dVEVpyQgvY/SRx3VsImcHwBL0GFM+HpDkSG60HrW/z+hR/Kj7t6U/TMHif r0eoS4GjlXwI4RzTFXsLkEXynqPx5V4ALi5Fw=
Received: by 10.210.57.12 with SMTP id f12mr4448174eba.199.1226971470197; Mon, 17 Nov 2008 17:24:30 -0800 (PST)
Received: by 10.210.109.14 with HTTP; Mon, 17 Nov 2008 17:24:30 -0800 (PST)
Message-ID: <1d38a3350811171724m6a7f2f84la1b47dcf2ac5b5c5@mail.gmail.com>
Date: Tue, 18 Nov 2008 09:24:30 +0800
From: Hui Deng <denghui02@gmail.com>
To: Cullen Jennings <fluffy@cisco.com>, Hui Deng <denghui@chinamobile.com>
In-Reply-To: <AB6DC025-4872-412B-98E7-A3AE0E84404F@cisco.com>
MIME-Version: 1.0
References: <AB6DC025-4872-412B-98E7-A3AE0E84404F@cisco.com>
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: multipart/mixed; boundary="===============1877681511=="
Sender: hipsec-bounces@ietf.org
Errors-To: hipsec-bounces@ietf.org

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