From hipsec-bounces@ietf.org Sun Oct 12 10:27:53 2008 Return-Path: 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 ADA973A6A14; Sun, 12 Oct 2008 10:27:53 -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 B90213A6A0D for ; Sun, 12 Oct 2008 10:27:52 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -2.599 X-Spam-Level: X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[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 1dffaHGd-qfM for ; Sun, 12 Oct 2008 10:27:52 -0700 (PDT) Received: from creon.otaverkko.fi (creon.otaverkko.fi [212.68.0.5]) by core3.amsl.com (Postfix) with ESMTP id E3DF03A6A08 for ; Sun, 12 Oct 2008 10:27:51 -0700 (PDT) Received: from localhost (localhost [127.0.0.1]) by creon.otaverkko.fi (Postfix) with ESMTP id B23D821AF3F; Sun, 12 Oct 2008 20:28:16 +0300 (EEST) Received: from creon.otaverkko.fi ([127.0.0.1]) by localhost (creon.otaverkko.fi [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 02247-10; Sun, 12 Oct 2008 20:28:12 +0300 (EEST) Received: from argo.otaverkko.fi (argo.otaverkko.fi [212.68.0.2]) by creon.otaverkko.fi (Postfix) with ESMTP id 3CA6D21AF39; Sun, 12 Oct 2008 20:28:12 +0300 (EEST) Received: from [192.168.1.2] (hil4.kyla.fi [82.130.20.68]) by argo.otaverkko.fi (Postfix) with ESMTP id 340CF25ED06; Sun, 12 Oct 2008 20:28:12 +0300 (EEST) Message-ID: <48F233AB.6060601@hiit.fi> Date: Sun, 12 Oct 2008 20:28:11 +0300 From: Miika Komu User-Agent: Thunderbird 2.0.0.17 (X11/20080925) MIME-Version: 1.0 To: hipsec@ietf.org X-Virus-Scanned: amavisd-new at otaverkko.fi Cc: hipsec-rg@listserv.cybertrust.com Subject: [Hipsec] beet patches for linux 2.6 kernel series X-BeenThere: hipsec@ietf.org X-Mailman-Version: 2.1.9 Precedence: list Reply-To: miika.komu@hiit.fi List-Id: "This is the official IETF Mailing List for the HIP Working Group." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Content-Transfer-Encoding: 7bit Content-Type: text/plain; charset="us-ascii"; Format="flowed" Sender: hipsec-bounces@ietf.org Errors-To: hipsec-bounces@ietf.org FYI, fully working BEET patches for Linux kernel are available in the just released 2.6.27 version. Special thanks for Joakim Koskela for finishing this work. _______________________________________________ Hipsec mailing list Hipsec@ietf.org https://www.ietf.org/mailman/listinfo/hipsec From hipsec-bounces@ietf.org Tue Oct 21 10:15:05 2008 Return-Path: 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 52BB028C161; Tue, 21 Oct 2008 10:15:05 -0700 (PDT) X-Original-To: hipsec@ietf.org Delivered-To: hipsec@core3.amsl.com Received: by core3.amsl.com (Postfix, from userid 0) id 106123A6B7A; Tue, 21 Oct 2008 10:15:01 -0700 (PDT) From: Internet-Drafts@ietf.org To: i-d-announce@ietf.org Content-Type: Multipart/Mixed; Boundary="NextPart" Mime-Version: 1.0 Message-Id: <20081021171502.106123A6B7A@core3.amsl.com> Date: Tue, 21 Oct 2008 10:15:02 -0700 (PDT) Cc: hipsec@ietf.org Subject: [Hipsec] I-D ACTION:draft-ietf-hip-cert-00.txt 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." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: hipsec-bounces@ietf.org Errors-To: hipsec-bounces@ietf.org --NextPart A New Internet-Draft is available from the on-line Internet-Drafts directories. This draft is a work item of the Host Identity Protocol Working Group of the IETF. Title : HIP Certificates Author(s) : T. Heer, S. Varjonen Filename : draft-ietf-hip-cert-00.txt Pages : 10 Date : 2008-10-21 This document specifies a certificate parameter called CERT for the Host Identity Protocol (HIP). The CERT parameter is a container for Simple Public Key Infrastructure (SPKI) and X.509.v3 certificates. It is used for carrying these certificates in HIP control messages. Additionally, this document specifies the representations of Host Identity Tags in SPKI and X.509.v3 certificates. A URL for this Internet-Draft is: http://www.ietf.org/internet-drafts/draft-ietf-hip-cert-00.txt Internet-Drafts are also available by anonymous FTP at: ftp://ftp.ietf.org/internet-drafts/ Below is the data which will enable a MIME compliant mail reader implementation to automatically retrieve the ASCII version of the Internet-Draft. --NextPart Content-Type: Message/External-body; name="draft-ietf-hip-cert-00.txt"; site="ftp.ietf.org"; access-type="anon-ftp"; directory="internet-drafts" Content-Type: text/plain Content-ID: <2008-10-21101137.I-D@ietf.org> --NextPart Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ Hipsec mailing list Hipsec@ietf.org https://www.ietf.org/mailman/listinfo/hipsec --NextPart-- From hipsec-bounces@ietf.org Wed Oct 22 10:20:07 2008 Return-Path: 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 CD79C28C1AE; Wed, 22 Oct 2008 10:20:07 -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 DEE0028C198 for ; Wed, 22 Oct 2008 10:20:05 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -6.598 X-Spam-Level: X-Spam-Status: No, score=-6.598 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_MED=-4] 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 24Zt27AJhsue for ; Wed, 22 Oct 2008 10:20:05 -0700 (PDT) Received: from sj-iport-6.cisco.com (sj-iport-6.cisco.com [171.71.176.117]) by core3.amsl.com (Postfix) with ESMTP id 0CE3A28C1AC for ; Wed, 22 Oct 2008 10:20:05 -0700 (PDT) X-IronPort-AV: E=Sophos;i="4.33,465,1220227200"; d="scan'208,217";a="180498921" Received: from sj-dkim-4.cisco.com ([171.71.179.196]) by sj-iport-6.cisco.com with ESMTP; 22 Oct 2008 17:21:18 +0000 Received: from sj-core-3.cisco.com (sj-core-3.cisco.com [171.68.223.137]) by sj-dkim-4.cisco.com (8.12.11/8.12.11) with ESMTP id m9MHLIo6003408; Wed, 22 Oct 2008 10:21:18 -0700 Received: from xbh-sjc-211.amer.cisco.com (xbh-sjc-211.cisco.com [171.70.151.144]) by sj-core-3.cisco.com (8.13.8/8.13.8) with ESMTP id m9MHLIA6029856; Wed, 22 Oct 2008 17:21:18 GMT Received: from xmb-sjc-224.amer.cisco.com ([128.107.191.98]) by xbh-sjc-211.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.1830); Wed, 22 Oct 2008 10:21:13 -0700 X-Mimeole: Produced By Microsoft Exchange V6.5 Content-class: urn:content-classes:message MIME-Version: 1.0 Date: Wed, 22 Oct 2008 10:21:14 -0700 Message-ID: <5F16CF3DBBC7EE45BF6E136F13F5CFEA071313C8@xmb-sjc-224.amer.cisco.com> X-MS-Has-Attach: X-MS-TNEF-Correlator: Thread-Topic: submission of a new I-D: "Delivering Geographic Location in Host Identity Protocol (HIP)" Thread-Index: Ack0apYtuWRPe4laQSGT64eHB1GETw== From: "Feng Cao (fcao)" To: X-OriginalArrivalTime: 22 Oct 2008 17:21:13.0715 (UTC) FILETIME=[958F6430:01C9346A] DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; l=2943; t=1224696078; x=1225560078; c=relaxed/simple; s=sjdkim4002; h=Content-Type:From:Subject:Content-Transfer-Encoding:MIME-Version; d=cisco.com; i=fcao@cisco.com; z=From:=20=22Feng=20Cao=20(fcao)=22=20 |Subject:=20submission=20of=20a=20new=20I-D=3A=20=22Deliver ing=20Geographic=20Location=20in=20Host=20Identity=20Protoco l=20(HIP)=22 |Sender:=20; bh=+aA6140ECAlNcbke+bOSBTJJ6cus02M3fT6Kau6ty3U=; b=IEKsIrp4CC2no+nleNlJQrG6z7wZjwc/QPJ2VdhUZgB3Ii+NRtPYJF7Uo0 Cl9tWaF0f3JLA+B/hrEhjQH9imsZsDkaqrsPMXRXikPK+CpK+tT3hhZk3w/5 FWQJhML3hR; Authentication-Results: sj-dkim-4; header.From=fcao@cisco.com; dkim=pass ( sig from cisco.com/sjdkim4002 verified; ); Cc: "David Ward \(wardd\)" , Hui Deng Subject: [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." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Content-Type: multipart/mixed; boundary="===============1787917276==" Sender: hipsec-bounces@ietf.org Errors-To: hipsec-bounces@ietf.org This is a multi-part message in MIME format. --===============1787917276== Content-class: urn:content-classes:message Content-Type: multipart/alternative; boundary="----_=_NextPart_001_01C9346A.95583411" This is a multi-part message in MIME format. ------_=_NextPart_001_01C9346A.95583411 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable Hi all, =20 A new I-D, draft-cao-hip-geolocation-00, was just submitted to IETF HIP WG. Your comments are always welcome. =20 Here is the staging URL for now:=20 http://www3.ietf.org/proceedings/staging/draft-cao-hip-geolocation-00.tx t =20 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 ------_=_NextPart_001_01C9346A.95583411 Content-Type: text/html; charset="us-ascii" Content-Transfer-Encoding: quoted-printable
Hi=20 all,
 
A new I-D,=20 draft-cao-hip-geolocation-00, was just submitted to IETF HIP WG. Your = comments=20 are always welcome.
 
Here = is the staging=20 URL for now:
http://www3.ietf.org/proceedings/staging/draft-cao-hip-geolocati= on-00.txt

Abstract: This=20 document defines a new parameter for delivering geographic location in = Host=20 Identity Protocol (HIP). For mobile users using HIP, one generic = mechanism is=20 proposed to share or update their geo- location information with either=20 rendezvous servers or their peers. = In=20 addition, geo-location privacy is also protected with the help of the = ENCRYPTED=20 parameter.

Thanks,

--Feng

------_=_NextPart_001_01C9346A.95583411-- --===============1787917276== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ Hipsec mailing list Hipsec@ietf.org https://www.ietf.org/mailman/listinfo/hipsec --===============1787917276==-- From hipsec-bounces@ietf.org Wed Oct 22 19:06:20 2008 Return-Path: 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 ; 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 ; 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 ; 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 To: Feng Cao (fcao), "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." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-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 >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 From hipsec-bounces@ietf.org Thu Oct 23 01:25:27 2008 Return-Path: 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 253713A6AA5; Thu, 23 Oct 2008 01:25:27 -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 E2BF23A69AF for ; Thu, 23 Oct 2008 01:25:25 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: 0.805 X-Spam-Level: X-Spam-Status: No, score=0.805 tagged_above=-999 required=5 tests=[AWL=-1.300, BAYES_50=0.001, 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 cdOYe1HB7JIL for ; Thu, 23 Oct 2008 01:25:25 -0700 (PDT) Received: from szxga02-in.huawei.com (unknown [119.145.14.65]) by core3.amsl.com (Postfix) with ESMTP id F1C0B3A68DA for ; Thu, 23 Oct 2008 01:25:24 -0700 (PDT) Received: from huawei.com (szxga02-in [172.24.2.6]) by szxga02-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 2.14 (built Aug 8 2006)) with ESMTP id <0K960005YNECCK@szxga02-in.huawei.com> for hipsec@ietf.org; Thu, 23 Oct 2008 16:25:24 +0800 (CST) Received: from huawei.com ([172.24.1.12]) by szxga02-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 2.14 (built Aug 8 2006)) with ESMTP id <0K9600K80NECQU@szxga02-in.huawei.com> for hipsec@ietf.org; Thu, 23 Oct 2008 16:25:24 +0800 (CST) Received: from zhaisp ([10.111.12.102]) by szxml05-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 2.14 (built Aug 8 2006)) with ESMTPA id <0K9600JA4NEBTA@szxml05-in.huawei.com> for hipsec@ietf.org; Thu, 23 Oct 2008 16:25:24 +0800 (CST) Date: Thu, 23 Oct 2008 16:25:24 +0800 From: Suping ZHAI To: "hipsec@ietf.org" Message-id: <0K9600JA5NEBTA@szxml05-in.huawei.com> MIME-version: 1.0 X-Mailer: Foxmail 4.2 [cn] Subject: [Hipsec] A question about 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." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: hipsec-bounces@ietf.org Errors-To: hipsec-bounces@ietf.org Hi all, After studying HIP for a while, I find that HIP can perfectly solve the mobility/multihoming/security problems which the now existing internet faces. But as to the multicast, which is an important feature which make so many applications such as IPTV, VOD, etc, how to accormmodate it in HIP? In another word, how to support the multicast services with HIP? Can somebody give me a guidance? TIA. Best Regards, Suping ZHAI zhaisuping@huawei.com Tel:0086-10-82836044 Fax:0086-10-82836284 _______________________________________________ Hipsec mailing list Hipsec@ietf.org https://www.ietf.org/mailman/listinfo/hipsec From hipsec-bounces@ietf.org Thu Oct 23 02:43:30 2008 Return-Path: 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 D2C783A6C4D; Thu, 23 Oct 2008 02:43:30 -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 79B273A6C3F for ; Thu, 23 Oct 2008 02:43:29 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -2.599 X-Spam-Level: X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[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 ppDNDRoxlELs for ; Thu, 23 Oct 2008 02:43:25 -0700 (PDT) Received: from creon.otaverkko.fi (creon.otaverkko.fi [212.68.0.5]) by core3.amsl.com (Postfix) with ESMTP id C7A603A6885 for ; Thu, 23 Oct 2008 02:43:24 -0700 (PDT) Received: from localhost (localhost [127.0.0.1]) by creon.otaverkko.fi (Postfix) with ESMTP id 7126621AF50; Thu, 23 Oct 2008 12:44:42 +0300 (EEST) Received: from creon.otaverkko.fi ([127.0.0.1]) by localhost (creon.otaverkko.fi [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 29427-05; Thu, 23 Oct 2008 12:44:32 +0300 (EEST) Received: from argo.otaverkko.fi (argo.otaverkko.fi [212.68.0.2]) by creon.otaverkko.fi (Postfix) with ESMTP id 530B021AF54; Thu, 23 Oct 2008 12:44:32 +0300 (EEST) Received: from [193.167.187.93] (ip93.infrahip.net [193.167.187.93]) by argo.otaverkko.fi (Postfix) with ESMTP id 4CD9625ED06; Thu, 23 Oct 2008 12:44:32 +0300 (EEST) Message-ID: <49004780.90204@hiit.fi> Date: Thu, 23 Oct 2008 12:44:32 +0300 From: Varjonen Samu User-Agent: Thunderbird 2.0.0.17 (X11/20080925) MIME-Version: 1.0 To: Suping ZHAI References: <0K9600JA5NEBTA@szxml05-in.huawei.com> In-Reply-To: <0K9600JA5NEBTA@szxml05-in.huawei.com> X-Virus-Scanned: amavisd-new at otaverkko.fi Cc: "hipsec@ietf.org" Subject: Re: [Hipsec] A question about 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." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Content-Transfer-Encoding: 7bit Content-Type: text/plain; charset="us-ascii"; Format="flowed" Sender: hipsec-bounces@ietf.org Errors-To: hipsec-bounces@ietf.org Hi, To my knowledge there is two published papers on the topic. Host Identity Specific Multicast http://ieeexplore.ieee.org/Xplore/login.jsp?url=/iel5/4438242/4438243/04438250.pdf?arnumber=4438250 and On Supporting Multicast and Delegation in Hi3 http://www.cs.helsinki.fi/u/gurtov/papers/hi3_multicast.pdf If anyone on the list knows more I would also be interested! I am also looking into possibilities/ideas to support multicast in HIP and doing some work to get them on paper and published some day in the future. BR, Samu Varjonen Suping ZHAI wrote: > Hi all, > After studying HIP for a while, I find that HIP can perfectly solve the mobility/multihoming/security problems which the now existing internet faces. But as to the multicast, which is an important feature which make so many applications such as IPTV, VOD, etc, how to accormmodate it in HIP? In another word, how to support the multicast services with HIP? Can somebody give me a guidance? TIA. > > > Best Regards, > Suping ZHAI > zhaisuping@huawei.com > Tel:0086-10-82836044 > Fax:0086-10-82836284 > > > _______________________________________________ > 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 From hipsec-bounces@ietf.org Thu Oct 23 02:47:53 2008 Return-Path: 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 5F9953A6C45; Thu, 23 Oct 2008 02:47:53 -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 518973A6C45 for ; Thu, 23 Oct 2008 02:47:52 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -6.599 X-Spam-Level: X-Spam-Status: No, score=-6.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4] 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 SjgM4ANvR3p1 for ; Thu, 23 Oct 2008 02:47:51 -0700 (PDT) Received: from mail.cs.helsinki.fi (courier.cs.helsinki.fi [128.214.9.1]) by core3.amsl.com (Postfix) with ESMTP id 33E663A6C37 for ; Thu, 23 Oct 2008 02:47:51 -0700 (PDT) Received: from [88.192.47.114] (dsl-hkibrasgw3-ff2fc000-114.dhcp.inet.fi [88.192.47.114]) (AUTH: PLAIN gurtov, SSL: TLSv1/SSLv3,256bits,AES256-SHA) by mail.cs.helsinki.fi with esmtp; Thu, 23 Oct 2008 12:48:54 +0300 id 0005BF70.49004886.0000590A Message-ID: <4900486D.4020501@cs.helsinki.fi> Date: Thu, 23 Oct 2008 12:48:29 +0300 From: Andrei Gurtov User-Agent: Thunderbird 2.0.0.17 (Windows/20080914) MIME-Version: 1.0 To: hipsec@ietf.org References: <0K9600JA5NEBTA@szxml05-in.huawei.com> In-Reply-To: <0K9600JA5NEBTA@szxml05-in.huawei.com> Subject: Re: [Hipsec] A question about 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." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Content-Transfer-Encoding: 7bit Content-Type: text/plain; charset="us-ascii"; Format="flowed" Sender: hipsec-bounces@ietf.org Errors-To: hipsec-bounces@ietf.org Check Chapter 6.6 from the HIP book :) http://eu.wiley.com/WileyCDA/WileyTitle/productCd-0470997907.html Andrei Suping ZHAI wrote: > Hi all, > After studying HIP for a while, I find that HIP can perfectly solve the mobility/multihoming/security problems which the now existing internet faces. But as to the multicast, which is an important feature which make so many applications such as IPTV, VOD, etc, how to accormmodate it in HIP? In another word, how to support the multicast services with HIP? Can somebody give me a guidance? TIA. > > > Best Regards, > Suping ZHAI > zhaisuping@huawei.com > Tel:0086-10-82836044 > Fax:0086-10-82836284 > > > _______________________________________________ > 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 From hipsec-bounces@ietf.org Thu Oct 23 04:34:42 2008 Return-Path: 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 A88DB28C198; Thu, 23 Oct 2008 04:34:42 -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 F367D3A67A6 for ; Thu, 23 Oct 2008 04:34:41 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -2.599 X-Spam-Level: X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[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 fl5La6qtSBvb for ; Thu, 23 Oct 2008 04:34:33 -0700 (PDT) Received: from creon.otaverkko.fi (creon.otaverkko.fi [212.68.0.5]) by core3.amsl.com (Postfix) with ESMTP id 91F3E3A69A8 for ; Thu, 23 Oct 2008 04:34:32 -0700 (PDT) Received: from localhost (localhost [127.0.0.1]) by creon.otaverkko.fi (Postfix) with ESMTP id C4FF421AF54; Thu, 23 Oct 2008 14:09:56 +0300 (EEST) Received: from creon.otaverkko.fi ([127.0.0.1]) by localhost (creon.otaverkko.fi [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 04236-09; Thu, 23 Oct 2008 14:09:46 +0300 (EEST) Received: from argo.otaverkko.fi (argo.otaverkko.fi [212.68.0.2]) by creon.otaverkko.fi (Postfix) with ESMTP id C023921AF3C; Thu, 23 Oct 2008 14:09:46 +0300 (EEST) Received: from [193.167.187.93] (ip93.infrahip.net [193.167.187.93]) by argo.otaverkko.fi (Postfix) with ESMTP id B861B25ED06; Thu, 23 Oct 2008 14:09:46 +0300 (EEST) Message-ID: <49005B7A.2020900@hiit.fi> Date: Thu, 23 Oct 2008 14:09:46 +0300 From: Varjonen Samu User-Agent: Thunderbird 2.0.0.17 (X11/20080925) MIME-Version: 1.0 To: Suping ZHAI References: <0K9600IP85WE6S@szxml03-in.huawei.com> In-Reply-To: <0K9600IP85WE6S@szxml03-in.huawei.com> X-Virus-Scanned: amavisd-new at otaverkko.fi Cc: "hipsec@ietf.org" , "Feng Cao \(fcao\)" 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." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Content-Transfer-Encoding: 7bit Content-Type: text/plain; charset="us-ascii"; Format="flowed" Sender: hipsec-bounces@ietf.org Errors-To: hipsec-bounces@ietf.org Hi, Suping ZHAI wrote: > 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? > Also to me the LOCATOR seems like a better place for this stuff as geo-loc information is a "locator". If IPs are used as the means to offer location LOCATOR would be straight forward. What if the location is based on GPS coordinates, well, lets add a new type to LOCATOR to inform about geographical location and define that these are NOT to be used for sending traffic. I would have liked to see a use case about why would I want to send geoloc information in HIP control packets. To me it seems that the application using HIP is more interested in the geoloc information. Or is this something that could be used with HIP Bone to offer locality based optimation for the overlay? Anyway some motivational stuff in the beginning would be nice. In introduction, in the end, ENCRYPTED not ENCRPTED. In the terminology I found that defining HIT is useless because if you need this draft you probably already know about HITs. But it does no harm in the list. In the terminology I noticed a term Peer connection. It sounded a lot like Host Association. Should it be HA? Also about the terminology usage in the draft, RFC 5204 defines Rendezvous extension not Rendevous extension. At least in sections 4.2, 4.3, 4.4, 4.5 and 5, the "z" char is missing. I would remove all the new words from the paper. They did not give any extra information on the parameter. To my opinion it can be just like "this paper describes parameter called GEOLOC". The newness of the parameter does not offer anything. In the figs correct the explanations, for example in fig 1 (which does not have a label) the Length is explained as 16, yes it is 16 bits long but it would be nicer to see it like "Length in octets, excluding Type, and Padding". Same goes for the LocationFormat. The length can be read from the fig. Could also be mentioned in the fig but after the content explanation. About the LocationFormat, should the bit defining LbyV/LbyR be separated from it because it does not change the location format. It changes how you use the LocationPayload and the LocationFormat would just say how you read it. Now ... +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | LocationFormat | | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | ... After ... +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ |L| LocationFormat | | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | ... L LbyV if 0 and LbyR if 1 ... Or ... +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ |L| Reserved | LocationFormat | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ ... L LbyV if 0 and LbyR if 1 I would lose the quotation marks from around the field names. The fig for ENCRYPTED can be seen in RFC 5201 in section 5.2.15 and reference to that should do the trick. It was quite clear the the Encrypted payload was the GEOLOC parameter even without the fig. Section 3.4. "The (new) GEOLOC_REQ parameter are defined" There is only one GEOLOC_REQ so "is" not "are" and the fig does not have a label. About the usage of the GEOLOC_REQ. Is it always used with the RVS or can I ask CNs location. Whose location can I ask from RVS? There is HIT present but can it be any HIT RVS knows. What if the HIT queried does not support GEOLOC, how RVS answers then? Section 4.3. "RVS can server as Location" should be "can serve as" "It is similar that GEOLOC can be embedded..." is repeated three times in the text in sections 4.3., 4.4. and 4.5. It is already stated in section 3.3. and it is NOT necessary to repeat it. Security considerations: You can always rate limit the control packets (quick and dirty solution). How about if one is lying about the location? BR, Samu Varjonen > 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 >> > 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 _______________________________________________ Hipsec mailing list Hipsec@ietf.org https://www.ietf.org/mailman/listinfo/hipsec From hipsec-bounces@ietf.org Thu Oct 23 10:56:14 2008 Return-Path: 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 BC0A83A684D; Thu, 23 Oct 2008 10:56:14 -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 BB9743A6838 for ; Thu, 23 Oct 2008 10:56:13 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -6.598 X-Spam-Level: X-Spam-Status: No, score=-6.598 tagged_above=-999 required=5 tests=[AWL=0.001, BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4] 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 ZA2mcbUOqY62 for ; Thu, 23 Oct 2008 10:56:12 -0700 (PDT) Received: from sj-iport-6.cisco.com (sj-iport-6.cisco.com [171.71.176.117]) by core3.amsl.com (Postfix) with ESMTP id B58BD3A688D for ; Thu, 23 Oct 2008 10:56:12 -0700 (PDT) X-IronPort-AV: E=Sophos;i="4.33,471,1220227200"; d="scan'208";a="181302689" Received: from sj-dkim-3.cisco.com ([171.71.179.195]) by sj-iport-6.cisco.com with ESMTP; 23 Oct 2008 17:57:32 +0000 Received: from sj-core-1.cisco.com (sj-core-1.cisco.com [171.71.177.237]) by sj-dkim-3.cisco.com (8.12.11/8.12.11) with ESMTP id m9NHvWtk010937; Thu, 23 Oct 2008 10:57:32 -0700 Received: from xbh-sjc-221.amer.cisco.com (xbh-sjc-221.cisco.com [128.107.191.63]) by sj-core-1.cisco.com (8.13.8/8.13.8) with ESMTP id m9NHvW5s026973; Thu, 23 Oct 2008 17:57:32 GMT Received: from xmb-sjc-224.amer.cisco.com ([128.107.191.98]) by xbh-sjc-221.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.1830); Thu, 23 Oct 2008 10:57:32 -0700 X-Mimeole: Produced By Microsoft Exchange V6.5 Content-class: urn:content-classes:message MIME-Version: 1.0 Date: Thu, 23 Oct 2008 10:57:30 -0700 Message-ID: <5F16CF3DBBC7EE45BF6E136F13F5CFEA071319AD@xmb-sjc-224.amer.cisco.com> In-Reply-To: <0K9600IP85WE6S@szxml03-in.huawei.com> X-MS-Has-Attach: X-MS-TNEF-Correlator: Thread-Topic: [Hipsec] submission of a new I-D:"Delivering Geographic Location in Host Identity Protocol (HIP)" Thread-Index: Ack0tBmS9YpqTwfuRRiKbg8/YSn53AAgiu2Q From: "Feng Cao (fcao)" To: "Suping ZHAI" , X-OriginalArrivalTime: 23 Oct 2008 17:57:32.0632 (UTC) FILETIME=[D2B57D80:01C93538] DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; l=2363; t=1224784652; x=1225648652; c=relaxed/simple; s=sjdkim3002; h=Content-Type:From:Subject:Content-Transfer-Encoding:MIME-Version; d=cisco.com; i=fcao@cisco.com; z=From:=20=22Feng=20Cao=20(fcao)=22=20 |Subject:=20RE=3A=20[Hipsec]=20submission=20of=20a=20new=20 I-D=3A=22Delivering=20Geographic=20Location=09in=20Host=20Id entity=20Protocol=20(HIP)=22 |Sender:=20; bh=o6cNg2V5MSh7qFe8NBlyzNbTKxhXUf0wxF2hZqdYAGc=; b=p72kyaLPzsgeA6NiDav9ftTK48aLCBdL9LFntbTzQblJTavUTHEAxTgN0N hR4fOPQQFbVrN6U5RhOMBool0K4rP+9iuYOlGCYKzthH/Su21aHTkxzMvOZx o0upVakHL+; Authentication-Results: sj-dkim-3; header.From=fcao@cisco.com; dkim=pass ( sig from cisco.com/sjdkim3002 verified; ); 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." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: hipsec-bounces@ietf.org Errors-To: hipsec-bounces@ietf.org Hi Suping, LOCATOR is another option to carrying geo-location. But there are some drawbacks for using LOCATOR. For example, there is a need to provide geo-location request, where GEOLOC_REQ is more clear and specific (instead of creating new LOCATOR_REQ only for geo-location). There are also some incompatible fields in LOCATOR, such as the limit of locator length and P-bit. Additionally, LOCATOR or location may generate confusion for its scope among various users, so geo-location sounds to be direct and clear. We stick to GEOLOC and GEOLOC_REQ for now (and are open to other options), unless that HIP WG reaches the consensus. Thanks, --Feng -----Original Message----- From: Suping ZHAI [mailto:zhaisuping@huawei.com] Sent: Wednesday, October 22, 2008 7:08 PM To: Feng Cao (fcao); hipsec@ietf.org Subject: Re: [Hipsec] submission of a new I-D:"Delivering Geographic Location in Host Identity Protocol (HIP)" 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.t >x >t >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 From hipsec-bounces@ietf.org Thu Oct 23 11:44:08 2008 Return-Path: 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 0D19E3A6838; Thu, 23 Oct 2008 11:44:08 -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 7D9A73A6838 for ; Thu, 23 Oct 2008 11:44:06 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -6.599 X-Spam-Level: X-Spam-Status: No, score=-6.599 tagged_above=-999 required=5 tests=[AWL=0.000, BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4] 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 yFxk4LPrW3A8 for ; Thu, 23 Oct 2008 11:44:05 -0700 (PDT) Received: from sj-iport-2.cisco.com (sj-iport-2.cisco.com [171.71.176.71]) by core3.amsl.com (Postfix) with ESMTP id 2D7B73A67E4 for ; Thu, 23 Oct 2008 11:44:05 -0700 (PDT) X-IronPort-AV: E=Sophos;i="4.33,471,1220227200"; d="scan'208";a="98226692" Received: from sj-dkim-3.cisco.com ([171.71.179.195]) by sj-iport-2.cisco.com with ESMTP; 23 Oct 2008 18:44:55 +0000 Received: from sj-core-1.cisco.com (sj-core-1.cisco.com [171.71.177.237]) by sj-dkim-3.cisco.com (8.12.11/8.12.11) with ESMTP id m9NIitxe024790; Thu, 23 Oct 2008 11:44:55 -0700 Received: from xbh-sjc-231.amer.cisco.com (xbh-sjc-231.cisco.com [128.107.191.100]) by sj-core-1.cisco.com (8.13.8/8.13.8) with ESMTP id m9NIitmG021189; Thu, 23 Oct 2008 18:44:55 GMT Received: from xmb-sjc-224.amer.cisco.com ([128.107.191.98]) by xbh-sjc-231.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.1830); Thu, 23 Oct 2008 11:44:55 -0700 X-Mimeole: Produced By Microsoft Exchange V6.5 Content-class: urn:content-classes:message MIME-Version: 1.0 Date: Thu, 23 Oct 2008 11:44:54 -0700 Message-ID: <5F16CF3DBBC7EE45BF6E136F13F5CFEA07131A1F@xmb-sjc-224.amer.cisco.com> In-Reply-To: <49005B7A.2020900@hiit.fi> X-MS-Has-Attach: X-MS-TNEF-Correlator: Thread-Topic: [Hipsec] submission of a new I-D:"Delivering Geographic Location in Host Identity Protocol (HIP)" Thread-Index: Ack0//btq9yLJ5NTR7uKXKlcWc/qtAAOOCsw From: "Feng Cao (fcao)" To: "Varjonen Samu" X-OriginalArrivalTime: 23 Oct 2008 18:44:55.0345 (UTC) FILETIME=[71191210:01C9353F] DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; l=6049; t=1224787495; x=1225651495; c=relaxed/simple; s=sjdkim3002; h=Content-Type:From:Subject:Content-Transfer-Encoding:MIME-Version; d=cisco.com; i=fcao@cisco.com; z=From:=20=22Feng=20Cao=20(fcao)=22=20 |Subject:=20RE=3A=20[Hipsec]=20submission=20of=20a=20new=20 I-D=3A=22Delivering=20Geographic=20Location=20in=20Host=20Id entity=20Protocol=20(HIP)=22 |Sender:=20; bh=F7fn6XmUTsnj8yoGzDzXDvrqlf55A6euLEAWop1LP9A=; b=JvXYUQ6IGOnLNVx95Klvmsoen10xx/NokdP2GeDS32LatNK1NOgaXknf4Y 3/NPKzt8ACV2k8bVefuYACkLdVY9KdNn6ChkxpacMs1fCn/FJC0R66DwM7Jm uiadjmb4Ql; Authentication-Results: sj-dkim-3; header.From=fcao@cisco.com; dkim=pass ( sig from cisco.com/sjdkim3002 verified; ); Cc: hipsec@ietf.org 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." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: hipsec-bounces@ietf.org Errors-To: hipsec-bounces@ietf.org Hi Varjonen, Thanks for your review and good catches on the errors. Will incorporate most of your comments and submit the updated draft. --Feng -----Original Message----- From: Varjonen Samu [mailto:samu.varjonen@hiit.fi] Sent: Thursday, October 23, 2008 4:10 AM To: Suping ZHAI Cc: Feng Cao (fcao); hipsec@ietf.org Subject: Re: [Hipsec] submission of a new I-D:"Delivering Geographic Location in Host Identity Protocol (HIP)" Hi, Suping ZHAI wrote: > 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? > Also to me the LOCATOR seems like a better place for this stuff as geo-loc information is a "locator". If IPs are used as the means to offer location LOCATOR would be straight forward. What if the location is based on GPS coordinates, well, lets add a new type to LOCATOR to inform about geographical location and define that these are NOT to be used for sending traffic. I would have liked to see a use case about why would I want to send geoloc information in HIP control packets. To me it seems that the application using HIP is more interested in the geoloc information. Or is this something that could be used with HIP Bone to offer locality based optimation for the overlay? Anyway some motivational stuff in the beginning would be nice. In introduction, in the end, ENCRYPTED not ENCRPTED. In the terminology I found that defining HIT is useless because if you need this draft you probably already know about HITs. But it does no harm in the list. In the terminology I noticed a term Peer connection. It sounded a lot like Host Association. Should it be HA? Also about the terminology usage in the draft, RFC 5204 defines Rendezvous extension not Rendevous extension. At least in sections 4.2, 4.3, 4.4, 4.5 and 5, the "z" char is missing. I would remove all the new words from the paper. They did not give any extra information on the parameter. To my opinion it can be just like "this paper describes parameter called GEOLOC". The newness of the parameter does not offer anything. In the figs correct the explanations, for example in fig 1 (which does not have a label) the Length is explained as 16, yes it is 16 bits long but it would be nicer to see it like "Length in octets, excluding Type, and Padding". Same goes for the LocationFormat. The length can be read from the fig. Could also be mentioned in the fig but after the content explanation. About the LocationFormat, should the bit defining LbyV/LbyR be separated from it because it does not change the location format. It changes how you use the LocationPayload and the LocationFormat would just say how you read it. Now ... +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | LocationFormat | | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | ... After ... +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ |L| LocationFormat | | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | ... L LbyV if 0 and LbyR if 1 ... Or ... +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ |L| Reserved | LocationFormat | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ ... L LbyV if 0 and LbyR if 1 I would lose the quotation marks from around the field names. The fig for ENCRYPTED can be seen in RFC 5201 in section 5.2.15 and reference to that should do the trick. It was quite clear the the Encrypted payload was the GEOLOC parameter even without the fig. Section 3.4. "The (new) GEOLOC_REQ parameter are defined" There is only one GEOLOC_REQ so "is" not "are" and the fig does not have a label. About the usage of the GEOLOC_REQ. Is it always used with the RVS or can I ask CNs location. Whose location can I ask from RVS? There is HIT present but can it be any HIT RVS knows. What if the HIT queried does not support GEOLOC, how RVS answers then? Section 4.3. "RVS can server as Location" should be "can serve as" "It is similar that GEOLOC can be embedded..." is repeated three times in the text in sections 4.3., 4.4. and 4.5. It is already stated in section 3.3. and it is NOT necessary to repeat it. Security considerations: You can always rate limit the control packets (quick and dirty solution). How about if one is lying about the location? BR, Samu Varjonen > 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 >> > 0.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 _______________________________________________ Hipsec mailing list Hipsec@ietf.org https://www.ietf.org/mailman/listinfo/hipsec From hipsec-bounces@ietf.org Fri Oct 24 10:18:38 2008 Return-Path: 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 130D53A6BED; Fri, 24 Oct 2008 10:18:38 -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 92FFC3A6BED for ; Fri, 24 Oct 2008 10:18:36 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -6.599 X-Spam-Level: X-Spam-Status: No, score=-6.599 tagged_above=-999 required=5 tests=[AWL=0.000, BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4] 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 pg1MbHqO+Zji for ; Fri, 24 Oct 2008 10:18:35 -0700 (PDT) Received: from sj-iport-1.cisco.com (sj-iport-1.cisco.com [171.71.176.70]) by core3.amsl.com (Postfix) with ESMTP id 950923A6BE4 for ; Fri, 24 Oct 2008 10:18:35 -0700 (PDT) X-IronPort-AV: E=Sophos;i="4.33,479,1220227200"; d="scan'208";a="95802291" Received: from sj-dkim-2.cisco.com ([171.71.179.186]) by sj-iport-1.cisco.com with ESMTP; 24 Oct 2008 17:19:58 +0000 Received: from sj-core-2.cisco.com (sj-core-2.cisco.com [171.71.177.254]) by sj-dkim-2.cisco.com (8.12.11/8.12.11) with ESMTP id m9OHJvc9002069 for ; Fri, 24 Oct 2008 10:19:57 -0700 Received: from xbh-sjc-231.amer.cisco.com (xbh-sjc-231.cisco.com [128.107.191.100]) by sj-core-2.cisco.com (8.13.8/8.13.8) with ESMTP id m9OHJvI4024580 for ; Fri, 24 Oct 2008 17:19:57 GMT Received: from xmb-sjc-224.amer.cisco.com ([128.107.191.98]) by xbh-sjc-231.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.1830); Fri, 24 Oct 2008 10:19:57 -0700 X-MIMEOLE: Produced By Microsoft Exchange V6.5 Content-class: urn:content-classes:message MIME-Version: 1.0 Date: Fri, 24 Oct 2008 10:19:56 -0700 Message-ID: <5F16CF3DBBC7EE45BF6E136F13F5CFEA07131EA3@xmb-sjc-224.amer.cisco.com> X-MS-Has-Attach: X-MS-TNEF-Correlator: Thread-Topic: revised I-D:"Delivering Geographic Location in Host Identity Protocol (HIP)" Thread-Index: Ack0//btq9yLJ5NTR7uKXKlcWc/qtAAOOCswADBhmyA= From: "Feng Cao (fcao)" To: X-OriginalArrivalTime: 24 Oct 2008 17:19:57.0863 (UTC) FILETIME=[BD2CCB70:01C935FC] DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; l=740; t=1224868798; x=1225732798; c=relaxed/simple; s=sjdkim2002; h=Content-Type:From:Subject:Content-Transfer-Encoding:MIME-Version; d=cisco.com; i=fcao@cisco.com; z=From:=20=22Feng=20Cao=20(fcao)=22=20 |Subject:=20revised=20I-D=3A=22Delivering=20Geographic=20Lo cation=20in=20Host=20Identity=20Protocol=20(HIP)=22 |Sender:=20; bh=jyv11fVeosO0NV0h++pFFTNh0elIn317VB3dzOq7D1Q=; b=duM7NsDYeMm2beM9oMYhtBcbSOaXvUAXzuPuR3jrzluDdvDurW/ZmyP7Mf xxp99AXoUDnt5T0oNJjGtDIZDdZMEHZMqSzBS0RTRjbBGYGmdiNzR/lD6mM9 1P8fHEnPZp; Authentication-Results: sj-dkim-2; header.From=fcao@cisco.com; dkim=pass ( sig from cisco.com/sjdkim2002 verified; ); Subject: [Hipsec] revised 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." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: hipsec-bounces@ietf.org Errors-To: hipsec-bounces@ietf.org Hi all, This I-D had been revised and submitted again yesterday. We'd like to thank the reviewers from this list. Most of the comments are incorporated into the updated version, especially the open issues raised. Further comments are always welcome. Here is the staging URL sent from the automatic IETF I-D submission tool: http://www3.ietf.org/proceedings/staging/draft-cao-hip-geolocation-01.tx t Thanks, --Feng Feng Cao, Ph.D., CISSP Infrastructure Security Research and Development Cisco Systems, Inc. Phone: (408)525-9988 Email: fcao@cisco.com P.S. I'll be out of country on vacation in the next two weeks. Will respond to any comments as soon as I return. Sorry for any inconvenience. _______________________________________________ Hipsec mailing list Hipsec@ietf.org https://www.ietf.org/mailman/listinfo/hipsec From hipsec-bounces@ietf.org Sat Oct 25 00:28:26 2008 Return-Path: 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 0E7723A689D; Sat, 25 Oct 2008 00:28:26 -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 215393A6841 for ; Sat, 25 Oct 2008 00:28:24 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: 0.155 X-Spam-Level: X-Spam-Status: No, score=0.155 tagged_above=-999 required=5 tests=[AWL=0.650, 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 vo3XxvNRgQ9M for ; Sat, 25 Oct 2008 00:28:23 -0700 (PDT) Received: from szxga01-in.huawei.com (unknown [119.145.14.64]) by core3.amsl.com (Postfix) with ESMTP id 257EF3A688C for ; Sat, 25 Oct 2008 00:28:23 -0700 (PDT) Received: from huawei.com (szxga01-in [172.24.2.3]) by szxga01-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 2.14 (built Aug 8 2006)) with ESMTP id <0K9A001BCA5CYY@szxga01-in.huawei.com> for hipsec@ietf.org; Sat, 25 Oct 2008 15:29:36 +0800 (CST) Received: from huawei.com ([172.24.1.24]) by szxga01-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 2.14 (built Aug 8 2006)) with ESMTP id <0K9A0067MA5BRQ@szxga01-in.huawei.com> for hipsec@ietf.org; Sat, 25 Oct 2008 15:29:35 +0800 (CST) Received: from zhaisp ([10.111.12.102]) by szxml04-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 2.14 (built Aug 8 2006)) with ESMTPA id <0K9A00HHTA5B86@szxml04-in.huawei.com> for hipsec@ietf.org; Sat, 25 Oct 2008 15:29:35 +0800 (CST) Date: Sat, 25 Oct 2008 15:29:35 +0800 From: Suping ZHAI To: Feng Cao (fcao), "hipsec@ietf.org" Message-id: <0K9A00HHVA5B86@szxml04-in.huawei.com> MIME-version: 1.0 X-Mailer: Foxmail 4.2 [cn] Subject: Re: [Hipsec] submission of a newI-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." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-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, See comment inline. ---original message--- From: fcao@cisco.com Sent: 2008-10-23 10:57:00 Subject:RE: [Hipsec] submission of a newI-D:"Delivering Geographic Location in Host Identity Protocol (HIP)" >Hi Suping, > >LOCATOR is another option to carrying geo-location. But there are some >drawbacks for using LOCATOR. For example, there is a need to provide >geo-location request, where GEOLOC_REQ is more clear and specific >(instead of creating new LOCATOR_REQ only for geo-location). >There are also some incompatible fields in LOCATOR, such as the limit of locator >length and P-bit. I don't think there are incompatibility issues here. It's so natural to define a new Locator Type to solve the above mentioned problem. E.g if Locator Type = GEOLOC, the following 16bits may be identified as Locator Length field. Suping >Additionally, LOCATOR or location may generate >confusion for its scope among various users, so geo-location sounds to >be direct and clear. > >We stick to GEOLOC and GEOLOC_REQ for now (and are open to other >options), unless that HIP WG reaches the consensus. > >Thanks, > >--Feng > >-----Original Message----- >From: Suping ZHAI [mailto:zhaisuping@huawei.com] >Sent: Wednesday, October 22, 2008 7:08 PM >To: Feng Cao (fcao); hipsec@ietf.org >Subject: Re: [Hipsec] submission of a new I-D:"Delivering Geographic >Location in Host Identity Protocol (HIP)" > >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.t >>x >>t >>>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 From hipsec-bounces@ietf.org Mon Oct 27 03:15:03 2008 Return-Path: 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 DFE643A6919; Mon, 27 Oct 2008 03:15:03 -0700 (PDT) X-Original-To: hipsec@ietf.org Delivered-To: hipsec@core3.amsl.com Received: by core3.amsl.com (Postfix, from userid 0) id E4FAA3A6844; Mon, 27 Oct 2008 03:15:01 -0700 (PDT) From: Internet-Drafts@ietf.org To: i-d-announce@ietf.org Content-Type: Multipart/Mixed; Boundary="NextPart" Mime-Version: 1.0 Message-Id: <20081027101501.E4FAA3A6844@core3.amsl.com> Date: Mon, 27 Oct 2008 03:15:01 -0700 (PDT) Cc: hipsec@ietf.org Subject: [Hipsec] I-D Action:draft-ietf-hip-bone-00.txt 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." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: hipsec-bounces@ietf.org Errors-To: hipsec-bounces@ietf.org --NextPart A New Internet-Draft is available from the on-line Internet-Drafts directories. This draft is a work item of the Host Identity Protocol Working Group of the IETF. Title : HIP BONE: Host Identity Protocol (HIP) Based Overlay Networking Environment Author(s) : G. Camarillo, et al. Filename : draft-ietf-hip-bone-00.txt Pages : 18 Date : 2008-10-27 This document specifies a framework to build HIP (Host Identity Protocol)-based overlay networks. This framework uses HIP to perform connection management. Other functions, such as data storage and retrieval or overlay maintenance, are implemented using protocols other than HIP. These protocols are loosely referred to as peer protocols. A URL for this Internet-Draft is: http://www.ietf.org/internet-drafts/draft-ietf-hip-bone-00.txt Internet-Drafts are also available by anonymous FTP at: ftp://ftp.ietf.org/internet-drafts/ Below is the data which will enable a MIME compliant mail reader implementation to automatically retrieve the ASCII version of the Internet-Draft. --NextPart Content-Type: Message/External-body; name="draft-ietf-hip-bone-00.txt"; site="ftp.ietf.org"; access-type="anon-ftp"; directory="internet-drafts" Content-Type: text/plain Content-ID: <2008-10-27030338.I-D@ietf.org> --NextPart Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ Hipsec mailing list Hipsec@ietf.org https://www.ietf.org/mailman/listinfo/hipsec --NextPart-- From hipsec-bounces@ietf.org Mon Oct 27 17:58:33 2008 Return-Path: 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 EC3253A6859; Mon, 27 Oct 2008 17:58:33 -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 135033A6809 for ; Mon, 27 Oct 2008 17:58:33 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -4.74 X-Spam-Level: X-Spam-Status: No, score=-4.74 tagged_above=-999 required=5 tests=[BAYES_20=-0.74, RCVD_IN_DNSWL_MED=-4] 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 zRKzr4yjukbx for ; Mon, 27 Oct 2008 17:58:32 -0700 (PDT) Received: from stl-smtpout-01.boeing.com (stl-smtpout-01.boeing.com [130.76.96.56]) by core3.amsl.com (Postfix) with ESMTP id 256EB3A6A8B for ; Mon, 27 Oct 2008 17:58:32 -0700 (PDT) Received: from blv-av-01.boeing.com (blv-av-01.boeing.com [130.247.48.231]) by stl-smtpout-01.ns.cs.boeing.com (8.14.0/8.14.0/8.14.0/SMTPOUT) with ESMTP id m9S0wGXT003067 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=FAIL) for ; Mon, 27 Oct 2008 19:58:26 -0500 (CDT) Received: from blv-av-01.boeing.com (localhost [127.0.0.1]) by blv-av-01.boeing.com (8.14.0/8.14.0/DOWNSTREAM_RELAY) with ESMTP id m9S0wF9o026240 for ; Mon, 27 Oct 2008 17:58:15 -0700 (PDT) Received: from hogwarts.rt.cs.boeing.com (hogwarts.rt.cs.boeing.com [130.42.32.238]) by blv-av-01.boeing.com (8.14.0/8.14.0/UPSTREAM_RELAY) with ESMTP id m9S0wFKe026237 for ; Mon, 27 Oct 2008 17:58:15 -0700 (PDT) Received: from crescent.rt.cs.boeing.com (crescent [130.42.32.236]) (using TLSv1 with cipher RC4-MD5 (128/128 bits)) (No client certificate requested) by hogwarts.rt.cs.boeing.com (Postfix) with ESMTP id AE18E15B46 for ; Mon, 27 Oct 2008 17:58:15 -0700 (PDT) From: Orlie Brewer To: "hipsec@ietf.org" Date: Mon, 27 Oct 2008 18:04:23 -0700 Message-Id: <1225155863.13213.3.camel@crescent.rt.cs.boeing.com> Mime-Version: 1.0 X-Mailer: Evolution 2.6.0 Subject: [Hipsec] HIP Mobile Router draft X-BeenThere: hipsec@ietf.org X-Mailman-Version: 2.1.9 Precedence: list Reply-To: orlie.t.brewer@boeing.com List-Id: "This is the official IETF Mailing List for the HIP Working Group." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: hipsec-bounces@ietf.org Errors-To: hipsec-bounces@ietf.org Hello, We have been implementing portions of the HIP mobile router draft to OpenHIP: <> Below are a few questions and comments about our effort. In section 5.1 of the draft, the "mobile router adds its self-signed locator set information to the I1 message" and "its signed LOCATOR TLV and ESP_INFO TLV to the I2 message." This only seems useful if the peer node has the host identity public key of the mobile router to verify the signature, but there is no mention of the mobile router passing that information to the peer node or establishing a HIP connection with the peer node. Also, these would have to be added after the portion of the message signed by the mobile node. We have defined a ESP_INFO_UNSIGNED parameter to place the SPINAT info after the portion of the message signed by the mobile node in the I2 message. Also, in that section, "the mobile router adds an encrypted 'echo request' parameter to the I1 message." We are assuming that it is an ECHO_REQUEST_UNSIGNED parameter that would be placed after the portion of the message signed by the mobile node. Another question with signatures is with the UPDATE packet. The HIP RFC5201, section 5.3.5, say that an HMAC parameter and a HIP_SIGNATURE parameter are mandatory. Again, is this suppose to be the mobile router's signature? The draft does not mention signatures in relation to the UPDATE packet. A general comment is that the draft seems to consider two cases, a mobile node with existing SAs moving behind a mobile router and a mobile node already behind a mobile router establishing an SA through a mobile router. However, it is a little confusing which case is being discussed at times as the draft seems to jump between the two cases. It would be clearer if it were explicitly stated when the different cases were begin discussed. Orlie Brewer The Boeing Company VOICE: (425) 373 - 2881, P.O. Box 3707, MS 7L-48 FAX: (425) 373 - 2960 Seattle, WA 98124-2207 EMAIL: orlie.t.brewer@boeing.com _______________________________________________ Hipsec mailing list Hipsec@ietf.org https://www.ietf.org/mailman/listinfo/hipsec From hipsec-bounces@ietf.org Fri Oct 31 09:15:05 2008 Return-Path: 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 065183A6C72; Fri, 31 Oct 2008 09:15:05 -0700 (PDT) X-Original-To: hipsec@ietf.org Delivered-To: hipsec@core3.amsl.com Received: by core3.amsl.com (Postfix, from userid 0) id 75CDB3A6C30; Fri, 31 Oct 2008 09:15:01 -0700 (PDT) From: Internet-Drafts@ietf.org To: i-d-announce@ietf.org Content-Type: Multipart/Mixed; Boundary="NextPart" Mime-Version: 1.0 Message-Id: <20081031161501.75CDB3A6C30@core3.amsl.com> Date: Fri, 31 Oct 2008 09:15:01 -0700 (PDT) Cc: hipsec@ietf.org Subject: [Hipsec] I-D Action:draft-ietf-hip-nat-traversal-05.txt 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." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: hipsec-bounces@ietf.org Errors-To: hipsec-bounces@ietf.org --NextPart A New Internet-Draft is available from the on-line Internet-Drafts directories. This draft is a work item of the Host Identity Protocol Working Group of the IETF. Title : Basic HIP Extensions for Traversal of Network Address Translators Author(s) : M. Komu, et al. Filename : draft-ietf-hip-nat-traversal-05.txt Pages : 32 Date : 2008-10-31 This document specifies extensions to the Host Identity Protocol (HIP) to facilitate Network Address Translator (NAT) traversal. The extensions are based on the use of the Interactive Connectivity Establishment (ICE) methodology to discover a working path between two end-hosts, and on standard techniques for encapsulating Encapsulating Security Payload (ESP) packets within the User Datagram Protocol (UDP). This document also defines elements of procedure for NAT traversal, including the optional use of a HIP relay server. With these extensions HIP is able to work in environments that have NATs and provides a generic NAT traversal solution to higher-layer networking applications. A URL for this Internet-Draft is: http://www.ietf.org/internet-drafts/draft-ietf-hip-nat-traversal-05.txt Internet-Drafts are also available by anonymous FTP at: ftp://ftp.ietf.org/internet-drafts/ Below is the data which will enable a MIME compliant mail reader implementation to automatically retrieve the ASCII version of the Internet-Draft. --NextPart Content-Type: Message/External-body; name="draft-ietf-hip-nat-traversal-05.txt"; site="ftp.ietf.org"; access-type="anon-ftp"; directory="internet-drafts" Content-Type: text/plain Content-ID: <2008-10-31090047.I-D@ietf.org> --NextPart Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ Hipsec mailing list Hipsec@ietf.org https://www.ietf.org/mailman/listinfo/hipsec --NextPart-- From hipsec-bounces@ietf.org Fri Oct 31 09:56:03 2008 Return-Path: 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 4451128C233; Fri, 31 Oct 2008 09:56:03 -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 4C6FC28C280 for ; Fri, 31 Oct 2008 09:56:02 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -6.249 X-Spam-Level: X-Spam-Status: No, score=-6.249 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HELO_EQ_SE=0.35, RCVD_IN_DNSWL_MED=-4] 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 YhexyBtVpd9i for ; Fri, 31 Oct 2008 09:56:01 -0700 (PDT) Received: from mailgw3.ericsson.se (mailgw3.ericsson.se [193.180.251.60]) by core3.amsl.com (Postfix) with ESMTP id 512E528C1F8 for ; Fri, 31 Oct 2008 09:55:57 -0700 (PDT) Received: from mailgw3.ericsson.se (unknown [127.0.0.1]) by mailgw3.ericsson.se (Symantec Mail Security) with ESMTP id 0C34A20412 for ; Fri, 31 Oct 2008 17:55:55 +0100 (CET) X-AuditID: c1b4fb3c-ad8cdbb0000015b5-54-490b389a326b Received: from esealmw128.eemea.ericsson.se (unknown [153.88.254.121]) by mailgw3.ericsson.se (Symantec Mail Security) with ESMTP id E60BF2023D for ; Fri, 31 Oct 2008 17:55:54 +0100 (CET) Received: from esealmw128.eemea.ericsson.se ([153.88.254.176]) by esealmw128.eemea.ericsson.se with Microsoft SMTPSVC(6.0.3790.1830); Fri, 31 Oct 2008 17:55:54 +0100 Received: from mail.lmf.ericsson.se ([131.160.11.50]) by esealmw128.eemea.ericsson.se with Microsoft SMTPSVC(6.0.3790.1830); Fri, 31 Oct 2008 17:55:54 +0100 Received: from [127.0.0.1] (nomadiclab.lmf.ericsson.se [131.160.33.3]) by mail.lmf.ericsson.se (Postfix) with ESMTP id 75C732330 for ; Fri, 31 Oct 2008 18:55:54 +0200 (EET) Message-ID: <490B38D7.2060405@nomadiclab.com> Date: Fri, 31 Oct 2008 18:56:55 +0200 From: Ari Keranen User-Agent: Thunderbird 2.0.0.17 (X11/20080925) MIME-Version: 1.0 To: hipsec@ietf.org References: <20081031161501.75CDB3A6C30@core3.amsl.com> In-Reply-To: <20081031161501.75CDB3A6C30@core3.amsl.com> X-OriginalArrivalTime: 31 Oct 2008 16:55:54.0752 (UTC) FILETIME=[89E7C800:01C93B79] X-Brightmail-Tracker: AAAAAA== Subject: Re: [Hipsec] I-D Action:draft-ietf-hip-nat-traversal-05.txt 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." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Content-Transfer-Encoding: 7bit Content-Type: text/plain; charset="us-ascii"; Format="flowed" Sender: hipsec-bounces@ietf.org Errors-To: hipsec-bounces@ietf.org Hi all, Internet-Drafts@ietf.org wrote: > A New Internet-Draft is available from the on-line Internet-Drafts directories. > This draft is a work item of the Host Identity Protocol Working Group of the IETF. > > > Title : Basic HIP Extensions for Traversal of Network Address Translators > Author(s) : M. Komu, et al. > Filename : draft-ietf-hip-nat-traversal-05.txt > Pages : 32 > Date : 2008-10-31 > Here's what has changed since the last (04) version: - lots of editorial and other small fixes - added non-normative intro - "NAT transform" parameter is now known as "NAT traversal mode" - new connectivity check transaction pacing negotiation - more details on ICE connectivity checks - added ICE candidate gathering information - more details on STUN connectivity check messages - added explicit negotiation of simple UDP encapsulation NAT traversal mode - updated format of REG_FROM, RELAY_FROM and RELAY_TO parameters The current version should have all the features that are needed, but it still needs some more implementation experience. Comments are welcome! Cheers, Ari _______________________________________________ Hipsec mailing list Hipsec@ietf.org https://www.ietf.org/mailman/listinfo/hipsec