Re: [Hipsec] submission of a new I-D:"Delivering Geographic Location in Host Identity Protocol (HIP)"

Suping ZHAI <zhaisuping@huawei.com> Thu, 23 October 2008 02:06 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 57C663A6BCD; Wed, 22 Oct 2008 19:06:20 -0700 (PDT)
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 CA4353A6B87 for <hipsec@core3.amsl.com>; Wed, 22 Oct 2008 19:06:19 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.495
X-Spam-Level:
X-Spam-Status: No, score=-0.495 tagged_above=-999 required=5 tests=[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 5-ggUd7RYZSB for <hipsec@core3.amsl.com>; Wed, 22 Oct 2008 19:06:19 -0700 (PDT)
Received: from szxga04-in.huawei.com (unknown [119.145.14.67]) by core3.amsl.com (Postfix) with ESMTP id F13C53A6B73 for <hipsec@ietf.org>; Wed, 22 Oct 2008 19:06:18 -0700 (PDT)
Received: from huawei.com (szxga04-in [172.24.2.12]) by szxga04-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 2.14 (built Aug 8 2006)) with ESMTP id <0K96003V75WE03@szxga04-in.huawei.com> for hipsec@ietf.org; Thu, 23 Oct 2008 10:07:26 +0800 (CST)
Received: from huawei.com ([172.24.1.18]) by szxga04-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 2.14 (built Aug 8 2006)) with ESMTP id <0K9600DG35WEPP@szxga04-in.huawei.com> for hipsec@ietf.org; Thu, 23 Oct 2008 10:07:26 +0800 (CST)
Received: from zhaisp ([10.111.12.102]) by szxml03-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 2.14 (built Aug 8 2006)) with ESMTPA id <0K9600IP65WE6S@szxml03-in.huawei.com> for hipsec@ietf.org; Thu, 23 Oct 2008 10:07:26 +0800 (CST)
Date: Thu, 23 Oct 2008 10:07:32 +0800
From: Suping ZHAI <zhaisuping@huawei.com>
To: Feng Cao <fcao@cisco.com> (fcao), "hipsec@ietf.org" <hipsec@ietf.org>
Message-id: <0K9600IP85WE6S@szxml03-in.huawei.com>
MIME-version: 1.0
X-Mailer: Foxmail 4.2 [cn]
Subject: Re: [Hipsec] submission of a new I-D:"Delivering Geographic Location in Host Identity Protocol (HIP)"
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

Hi Feng,
One comment with respect of the parameter geolocation. In the location-based services, the location can be identified by the LOCATOR which is defined in RFC5206, it can also provide the privacy and authentication. So what's the preference of the GEOLOCATION comparing with the LOCATOR?

Best Regards,
Suping
---original message---
From: fcao@cisco.com
Sent: 2008-10-22 10:21:00
Subject:[Hipsec] submission of a new I-D:"Delivering Geographic Location	in Host Identity Protocol (HIP)"

>Hi all,
> 
>A new I-D, draft-cao-hip-geolocation-00, was just submitted to IETF HIP
>WG. Your comments are always welcome.
> 
>Here is the staging URL for now: 
>http://www3.ietf.org/proceedings/staging/draft-cao-hip-geolocation-00.tx
>t
><http://www3.ietf.org/proceedings/staging/draft-cao-hip-geolocation-00.t
>xt> 
>
>Abstract: This document defines a new parameter for delivering
>geographic location in Host Identity Protocol (HIP). For mobile users
>using HIP, one generic mechanism is proposed to share or update their
>geo- location information with either rendezvous servers or their peers.
>In addition, geo-location privacy is also protected with the help of the
>ENCRYPTED parameter.
>
>Thanks,
>
>--Feng
>_______________________________________________
>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