From xmw@cernet.edu.cn Fri Jul 1 02:24:18 2011 Return-Path: X-Original-To: hiprg@ietfa.amsl.com Delivered-To: hiprg@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 5013D11E80B8 for ; Fri, 1 Jul 2011 02:24:18 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -98.15 X-Spam-Level: X-Spam-Status: No, score=-98.15 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, FH_HAS_XAIMC=2.696, MIME_BASE64_TEXT=1.753, USER_IN_WHITELIST=-100] Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id OK62F+4VYGDA for ; Fri, 1 Jul 2011 02:24:13 -0700 (PDT) Received: from cernet.edu.cn (cernet.edu.cn [202.112.39.2]) by ietfa.amsl.com (Postfix) with SMTP id D802A11E80CF for ; Fri, 1 Jul 2011 02:24:11 -0700 (PDT) Received: from user-THINK([219.243.215.210]) by cernet.edu.cn(AIMC 3.2.0.0) with SMTP id jm14c4e0dc520; Fri, 01 Jul 2011 17:24:08 +0800 Date: Fri, 1 Jul 2011 17:24:12 +0800 From: "Mingwei Xu" To: "hiprg" Message-ID: <201107011724124176529@cernet.edu.cn> X-mailer: Foxmail 6, 15, 201, 22 [cn] Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: base64 X-AIMC-AUTH: xmw X-AIMC-MAILFROM: xmw@cernet.edu.cn X-AIMC-Msg-ID: MaSx9c0B Subject: Re: [hiprg] HIPRG charter discussion X-BeenThere: hiprg@irtf.org X-Mailman-Version: 2.1.12 Precedence: list List-Id: "Host Identity Protocol \(HIP\) Research Group" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 01 Jul 2011 09:24:18 -0000 SGksIEFuZHJlaSwNCg0KVHNpbmdodWEgVW5pdmVyc2l0eSBoYXMgZ3JlYXQgaW50ZXJlc3Qgb24g dGhlIGhpZXJhcmNoaWNhbCBISVQgcmVzZWFyY2ggd29yay4gDQpXZSBoYXZlIGhhZCBzb21lIHN0 dWR5IG9uIEhJUCBhbmQgTmFtZSBCYXNlZCBTb2NrZXQgKE5CUykuIEkgdGhpbmsgSElQDQpoYXMg aXRzIGFkdmFudGFnZXMgaW4gSUQvTE9DIHNjaGVtcy4gV2Ugd2FudCB0byBkbyBtb3JlIHdvcmsg b24gbW9iaWxpdHkNCmFuZCBzZWN1cml0eSBiYXNlZCBvbiBILUhJUC4gV2Ugd2lsbCBhdHRlbmQg dGhlIEhJUFJHIG1lZXRpbmdzIGNvbnRpbnVhbGx5DQphbmQgY29udHJpYnV0ZSB0byBILUhJUCBk cmFmdHMgZGV2ZWxvcG1lbnQuDQoNCk1pbmd3ZWkgWHUNCg0KDQoNCkZyb206IEFuZHJlaSBHdXJ0 b3YgPGd1cnRvdiBhdCBoaWl0LmZpPiANClRvOiBXZW5kb25nIFdBTkcgPHdkd2FuZyBhdCBidXB0 LmVkdS5jbj4gDQpDYzogaGlwcmcgPGhpcHJnIGF0IGlydGYub3JnPiANCkRhdGU6IFRodSwgMzAg SnVuIDIwMTEgMDk6MzI6MjQgKzAzMDAgDQpJbi1yZXBseS10bzogPDIwMTEwNjMwMTEzMDUwODI0 MzE1MyBhdCBidXB0LmVkdS5jbj4gDQpSZWZlcmVuY2VzOiA8MjAxMTA2MjgxNjU5NDE1NTE0NDY5 IGF0IGJ1cHQuZWR1LmNuPiA8MjAxMTA2MzAxMTMwNTA4MjQzMTUzIGF0IGJ1cHQuZWR1LmNuPiAN Cg0KLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0t LS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0NCkNhbiB5b3UgY29tbWl0IHRvIGF0dGVuZCB0aGUg SElQUkcgbWVldGluZ3MgYXQgSUVURiBmb3Igb25lLXR3byB5ZWFycyB0bw0KIGNvbnRyaWJ1dGUg dG8gaC1oaXAgZHJhZnQgZGV2ZWxvcG1lbnQgb3IgYXQgbGVhc3QgcHJvdmlkZSBhY3RpdmUNCmZl ZWRiYWNrIG9uIHRoZSBtYWlsaW5nIGxpc3QgKGUuZy4gYXQgbGVhc3Qgb25lIGVtYWlsL3dlZWsp Pw0KDQpTYW1lIHF1ZXN0aW9uIGFsc28gYXBwbGllcyB0byBDaGluYSBtb2JpbGUuDQoNCkFuZHJl aQ0KDQoNCldlbmRvbmcgV0FORyB3cm90ZToNCj4gDQo+ICANCj4gT3VyIHRlYW0gaGFzDQo+IGlu dGVyZXN0aW5nIG9uIHRoZSBoaWVyYXJjaGljYWwgSElUIHJlc2VhcmNoIHdvcmsuIHdlIGhhdmUg YWxyZWFkeSBpbXBsZW1lbnRlZCBhIGRlbW8gb2YgSUQtTG9jYXRvciBtYXBwaW5nIHNlcnZpY2Vz IGJhc2VkIG9uIEhJUC4gDQo+IFdlIGFsc28gaG9wZSB0byBkbyBtb3JlIHdvcmtzIG9uIGl0IGZv ciB0aGUgZnV0dXJlIEludGVybmV0IG1vYmlsaXR5IGFuZCBzZWN1cml0eSBmdW5jdGlvbnMuDQo+ IFdlbmRvbmcgV0FORw0KPiBCZWlqaW5nIFVuaXZlcnN0eSBvZiBQb3N0cyBhbmQgVGVsZWNvbW11 bmljYXRpb25zIChCVVBUKSANCj4gMjAxMS0wNi0zMA0KPiAgDQo+ICANCj4gIA0KPj4gLS0tLS3p 5OXkLS0tLS0NCj4+IOXk5DogQW5kcmVpIEd1cnRvdiBbbWFpbHRvOmd1cnRvdiBhdCBoaWl0LmZp XQ0KPj4g5enm6TogMjAxMeU25jE05iAxNzo0NA0KPj4g5uTkOiBYdSBYaWFvaHUNCj4+IObpOiAn SGVuZGVyc29uLCBUaG9tYXMgUic7IGhpcHJnIGF0IGlydGYub3JnOyBpcnRmLWNoYWlyIGF0IGly c2cub3JnDQo+PiDk6TogUmU6IFtoaXByZ10gSElQUkcgY2hhcnRlciBkaXNjdXNzaW9uDQo+PiAN Cj4+IA0KPj4gSGVpIFhpYW9odSwNCj4+IA0KPj4gVGhhdCdzIGFuIGludGVyZXN0aW5nIHRvcGlj LCBidXQgdGhlcmUgc2hvdWxkIGJlIGludGVyZXN0IG9mIHNldmVyYWwNCj4+IG9yZ2FuaXphdGlv bnMgdG8gZGlzY3VzcyBhbmQgZGV2ZWxvcCBpdCBqb2ludGx5IGF0IEhJUFJHLiBDYW4geW91IHRo aW5rDQo+PiBvZiBvdGhlcnMgd2hvIHdvdWxkIGJlIHdpbGxpbmcgdG8gY29tbWl0IHRvIHRoaXMg dG9waWMgZm9yIGEgY291cGxlDQo+PiB5ZWFycz8gTWF5YmUgQ2hpbmEgbW9iaWxlLCBUc2luZ2h1 YSBVbml2ZXJzaXR5Pw0KPj4gDQo+PiBBbmRyZWkNCj4+IA0KPj4gWHUgWGlhb2h1IHdyb3RlOg0K Pj4gPiBIaSBUb20gYW5kIGFsbCwNCj4+ID4NCj4+ID4gSSBwcm9wb3NlIHRvIGNvbnNpZGVyIHRh a2luZyB0aGUgaGllcmFyY2hpY2FsIEhJVCByZXNlYXJjaCBhcyBhIG5ldyBjaGFydGVyDQo+PiA+ IGl0ZW0uIElNSE8sIHRoZXJlIGFyZSBhdCBsZWFzdCB0d28gbWFqb3IgYmVuZWZpdHMgb2YgdXNp bmcgaGllcmFyY2hpY2FsIEhJVHMNCj4+ID4gZnJvbSB0aGUgY29tbWVyY2lhbCBkZXBsb3ltZW50 IHBlcnNwZWN0aXZlczoNCj4+ID4NCj4+ID4gRmlyc3QsIHRoZSBJRC9ISVQgcmVnaXN0cmF0aW9u IG1hbmFnZW1lbnQgc2VydmljZSBhbmQgdGhlIElELXRvLUxvY2F0b3INCj4+ID4gbWFwcGluZyBz ZXJ2aWNlIGNvcnJlc3BvbmRpbmcgdG8gdGhlIGhpZXJhcmNoaWNhbCBISVRzIGNvdWxkIGJlIHJ1 biBpbiBhDQo+PiA+IGhpZXJhcmNoaWNhbCBtYW5uZXIuIEluIG90aGVyIHdvcmRzLCBzdWNoIGds b2JhbCBtb2JpbGl0eSBtYW5hZ2VtZW50DQo+PiBzZXJ2aWNlDQo+PiA+IHN5c3RlbXMgY291bGQg YmUgb3BlcmF0ZWQgYnkgZGlmZmVyZW50IGNvdW50cmllcyBhbmQgZGlmZmVyZW50IG9wZXJhdG9y cw0KPj4gPiB3aXRoIGNsZWFyIGFkbWluaXN0cmF0aXZlIGRvbWFpbiBib3VuZGFyaWVzIGFuZCBy ZWFzb25hYmxlIGJ1c2luZXNzDQo+PiBtb2RlbHMsDQo+PiA+IGp1c3QgbGlrZSB0aGUgdGVsZXBo b25lIG51bWJlciBzcGFjZSBpbiB0aGUgdGVsZXBob25lIG5ldHdvcmsgYW5kIHRoZSBob21lDQo+ PiA+IGFkZHJlc3Mgc3BhY2UgaW4gdGhlIG1vYmlsZSBJUCBuZXR3b3JrLiBJbiBhZGRpdGlvbiwg dGhlIGV4aXN0aW5nIEROUw0KPj4gPiBpbmZyYXN0cnVjdHVyZSBkb2Vzbid0IG5lZWQgdG8gYmUg Y2hhbmdlZCBsYXJnZWx5LiBUaGF0J3MgdG8gc2F5LCBISVRzIG9mDQo+PiA+IHRoZSBISVAgaG9z dHMgY291bGQgYmUgc3RvcmVkIGRpcmVjdGx5IGFzIHRoZWlyIGNvcnJlc3BvbmRpbmcgQUFBQSBS UnMgaW4NCj4+ID4gdGhlIGV4aXN0aW5nIEROUyBpbmZyYXN0cnVjdHVyZS4NCj4+ID4NCj4+ID4g U2Vjb25kLCB0aGUgdXNhZ2Ugb2YgaGllcmFyY2hpY2FsIEhJVHMgd2lsbCBlYXNlIHRoZSB0cmFu c2l0aW9uIGZvciBISVAuIEZvcg0KPj4gPiBpbnN0YW5jZSwgbGVnYWN5IElQdjYgaG9zdHMgY291 bGQgYWNjZXNzIG1vYmlsZSBISVAgaG9zdHMgdmlhIHByb3ZpZGVyLW93bmVkDQo+PiA+IEhJUCBw cm94eSBkZXZpY2VzIChqdXN0IGFzIGhvbWUgYWdlbnRzIGluIHRoZSBtb2JpbGUgSVAgbmV0d29y aykgc2luY2UgdGhlDQo+PiA+IGhpZXJhcmNoaWNhbCBISVRzIGNvdWxkIGJlIHJvdXRhYmxlIGlu IHRoZSBJbnRlcm5ldC4gT24gdGhlIGNvbnRyYXJ5LA0KPj4gPiBPUkNISURzIGFyZSBub3Qgcm91 dGFibGUgaW4gdGhlIEludGVybmV0IHNpbmNlIHRoZXJlIGlzIG5vIHJlYXNvbmFibGUNCj4+ID4g YnVzaW5lc3MgbW90aXZhdGlvbiBmb3Igb3BlcmF0b3JzIHRvIGRlcGxveSBISVAgcHJveHkgZGV2 aWNlcyBmb3Igc3VjaCBmbGF0DQo+PiA+IGlkZW50aWZpZXJzLg0KPj4gPg0KPj4gPiBUaGVyZSBo YXMgYmVlbiBzb21lIHByb3Bvc2FscyBhbmQgcHJlc2VudGF0aW9ucyBkaXNjdXNzaW5nIGFib3V0 DQo+PiA+IGhpZXJhcmNoaWNhbCBISVRzIGluIEhJUFJHIGJlZm9yZSBhcyBmb2xsb3dzOg0KPj4g PiBodHRwOi8vdG9vbHMuaWV0Zi5vcmcvaHRtbC9kcmFmdC14dS1oaXAtaGllcmFyY2hpY2FsLTAy DQo+PiA+IGh0dHA6Ly90b29scy5pZXRmLm9yZy9odG1sL2RyYWZ0LWt1cHRzb3YtaGhpdC0wMg0K Pj4gPiBodHRwOi8vdG9vbHMuaWV0Zi5vcmcvaHRtbC9kcmFmdC14dS1yYW5naS0wNA0KPj4gPg0K Pj4gPiBCeSB0aGUgd2F5LCB3ZSBoYXZlIGltcGxlbWVudGVkIHRoZSBSQU5HSQ0KPj4gPiAoaHR0 cDovL3Rvb2xzLmlldGYub3JnL2h0bWwvZHJhZnQteHUtcmFuZ2ktMDQpIHByb3RvdHlwZSB3aGlj aCB1c2VzIGENCj4+ID4gaGllcmFyY2hpY2FsIGFuZCBjcnlwdG9ncmFwaGljIGhvc3QgSURzIHdp dGggZGVsZWdhdGlvbi1vcmllbnRlZCBzdHJ1Y3R1cmUuDQo+PiA+IEhvcGUgd2UgY291bGQgaGF2 ZSBhIGNoYW5jZSB0byBzaG93IHRoZSBpbXBsZW1lbnRhdGlvbiBkZXRhaWxzIGFuZA0KPj4gPiB2 ZXJpZmljYXRpb24gcmVzdWx0cyBhdCB0aGUgZm9ydGhjb21pbmcgSUVURiBtZWV0aW5nIGluIFF1 ZWJlYyBDaXR5Lg0KPj4gPg0KPj4gPiBCZXN0IHJlZ2FyZHMsDQo+PiA+IFhpYW9odQ0KPj4gPg0K Pj4gPg0KPj4gPj4gLS0tLS3p5OXkLS0tLS0NCj4+ID4+IOXk5DogaGlwcmctYm91bmNlcyBhdCBp cnRmLm9yZyBbbWFpbHRvOmhpcHJnLWJvdW5jZXMgYXQgaXJ0Zi5vcmddIOToDQo+PiA+PiBIZW5k ZXJzb24sIFRob21hcyBSDQo+PiA+PiDl6ebpOiAyMDEx5TbmNuYgMjI6NDkNCj4+ID4+IObk5Dog aGlwcmcgYXQgaXJ0Zi5vcmcNCj4+ID4+IObpOiAnaXJ0Zi1jaGFpciBhdCBpcnNnLm9yZycNCj4+ ID4+IOTpOiBbaGlwcmddIEhJUFJHIGNoYXJ0ZXIgZGlzY3Vzc2lvbg0KPj4gPj4NCj4+ID4+IFdp dGggdGhlIGNvbXBsZXRpb24gb2YgdGhlIGV4cGVyaW1lbnQgcmVwb3J0IChvdXIgbWFpbiBSRyBj aGFydGVyIGl0ZW0NCj4+ID4gc2luY2UNCj4+ID4+IHRoZSBSRydzIGluY2VwdGlvbiksIEkgd291 bGQgbGlrZSB0byBhc2sgYWJvdXQgZnV0dXJlIGRpcmVjdGlvbnMgb2YgdGhlDQo+PiA+IFJHLg0K Pj4gPj4gT3V0c2lkZSBvZiBjb21wbGV0aW5nIG91ciBjdXJyZW50IFJHIGRyYWZ0cywgd2UgbmVl ZCB0byB0cnkgdG8gZGVmaW5lIHNvbWUNCj4+ID4+IG5ldyBjb2xsYWJvcmF0aXZlIHdvcmsgaXRl bXMgYW5kIGRlZmluZSB3aGF0IHJvbGUgdGhlIFJHIHdpbGwgcGxheQ0KPj4gPiByZWxhdGl2ZSB0 bw0KPj4gPj4gdGhlIFdHLg0KPj4gPj4NCj4+ID4+IFRoZXNlIHdvcmsgaXRlbXMgc2hvdWxkIGlk ZWFsbHkgc2F0aXNmeSB0aGUgZm9sbG93aW5nIGNyaXRlcmlhOg0KPj4gPj4gLSBpcyB0aGUgcmVz ZWFyY2ggYXJlYSBjbGVhciBhbmQgcmVsZXZhbnQgZm9yIHRoZSBJbnRlcm5ldCBjb21tdW5pdHkg YW5kDQo+PiA+IGZvcg0KPj4gPj4gSElQIGluIHBhcnRpY3VsYXI/ICBXaGF0IGFyZSB0aGUgZXhw ZWN0ZWQgb3V0Y29tZXMgYW5kIGltcGFjdD8NCj4+ID4+IC0gd2lsbCB0aGUgUkcgZm9zdGVyIHdv cmsgdGhhdCB3b3VsZCBub3QgYmUgZG9uZSBvdGhlcndpc2U/ICBGb3IgaW5zdGFuY2UsDQo+PiA+ PiBwYXJ0aWNpcGF0aW9uIGRyYXduIGZyb20gbW9yZSB0aGFuIGEgc2luZ2xlIGluc3RpdHV0aW9u IG9yIGNvdW50cnkuICBDYW4NCj4+ID4gd2UNCj4+ID4+IHRyeSB0byBpZGVudGlmeSBpbmRpdmlk dWFscyBmb3IgdGhpcyBhbnRpY2lwYXRlZCBwYXJ0aWNpcGF0aW9uPw0KPj4gPj4NCj4+ID4+IFdl IGNhbiBoYXZlIHNvbWUgZGlzY3Vzc2lvbiBvZiB0aGlzIGF0IHRoZSBuZXh0IG1lZXRpbmcgYnV0 IEkgd291bGQgbGlrZQ0KPj4gPiB0byBzZWUNCj4+ID4+IHdoZXRoZXIgd2UgY2FuIHN0YXJ0IGlk ZW50aWZ5aW5nIHNvbWUgdG9waWNzIG9uIHRoZSBsaXN0IGJlZm9yZSB0aGUNCj4+ID4gbWVldGlu Zy4NCj4+ID4+IC0gVG9tDQoNCg0K From thomas.r.henderson@boeing.com Sat Jul 2 15:46:43 2011 Return-Path: X-Original-To: hiprg@ietfa.amsl.com Delivered-To: hiprg@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 62B2D11E8082 for ; Sat, 2 Jul 2011 15:46:43 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -105.8 X-Spam-Level: X-Spam-Status: No, score=-105.8 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4, SARE_SUB_RAND_LETTRS4=0.799, USER_IN_WHITELIST=-100] Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id j3efQgx5QHbF for ; Sat, 2 Jul 2011 15:46:42 -0700 (PDT) Received: from stl-smtpout-01.boeing.com (stl-smtpout-01.boeing.com [130.76.96.56]) by ietfa.amsl.com (Postfix) with ESMTP id 5D4F821F85AA for ; Sat, 2 Jul 2011 15:46:31 -0700 (PDT) Received: from stl-av-01.boeing.com (stl-av-01.boeing.com [192.76.190.6]) by stl-smtpout-01.ns.cs.boeing.com (8.14.4/8.14.4/8.14.4/SMTPOUT) with ESMTP id p62MkOe1016572 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=FAIL); Sat, 2 Jul 2011 17:46:25 -0500 (CDT) Received: from stl-av-01.boeing.com (localhost [127.0.0.1]) by stl-av-01.boeing.com (8.14.4/8.14.4/DOWNSTREAM_RELAY) with ESMTP id p62MkOcS022950; Sat, 2 Jul 2011 17:46:24 -0500 (CDT) Received: from XCH-NWHT-07.nw.nos.boeing.com (xch-nwht-07.nw.nos.boeing.com [130.247.25.111]) by stl-av-01.boeing.com (8.14.4/8.14.4/UPSTREAM_RELAY) with ESMTP id p62MkOf2022947 (version=TLSv1/SSLv3 cipher=RC4-MD5 bits=128 verify=OK); Sat, 2 Jul 2011 17:46:24 -0500 (CDT) Received: from XCH-NW-10V.nw.nos.boeing.com ([130.247.25.83]) by XCH-NWHT-07.nw.nos.boeing.com ([130.247.25.111]) with mapi; Sat, 2 Jul 2011 15:46:10 -0700 From: "Henderson, Thomas R" To: "'Martin Stiemerling'" Date: Sat, 2 Jul 2011 15:46:10 -0700 Thread-Topic: IRSG review of draft-irtf-hip-experiment Thread-Index: AcwwIlZ4ER2xrt4hTyG57Kt6k2x0uwI46LXA Message-ID: <7CC566635CFE364D87DC5803D4712A6C4CEFAF030F@XCH-NW-10V.nw.nos.boeing.com> References: In-Reply-To: Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: acceptlanguage: en-US Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable MIME-Version: 1.0 Cc: "hiprg@irtf.org" Subject: Re: [hiprg] IRSG review of draft-irtf-hip-experiment X-BeenThere: hiprg@irtf.org X-Mailman-Version: 2.1.12 Precedence: list List-Id: "Host Identity Protocol \(HIP\) Research Group" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 02 Jul 2011 22:46:43 -0000 Martin, Thanks for providing the IRSG review of this draft. Responses inline below= : > -----Original Message----- > From: irsg-bounces@irtf.org [mailto:irsg-bounces@irtf.org] On Behalf Of > Martin Stiemerling > Sent: Tuesday, June 21, 2011 7:49 AM > To: irsg@irtf.org > Subject: [irsg] IRSG review of draft-irtf-hip-experiment >=20 > Dear all, >=20 > Here is my review of draft-irtf-hip-experiment-12. >=20 > The draft is basically fine and it provides an excellent overview about > the HIP experiments, their outcomes, and lessons learnt. >=20 > There are a few nits: > - Section 1, Introduction: > The draft -12 dates May 2011, but the intro says it compiles data from > 2004 to 2009. Wasn't there any further work until May 2011? We haven't been updating it with recent work since it would always be a mov= ing target and we would like to publish it with the material gathered throu= gh 2009. So I propose no change here. > - Section 2.1, Figure 1: > It is not clear from the figure what is user space and what is kernel > space. This doesn't match the text on page 7, bottom. This might be > confusing to an average reader. Suggested rephrase: Old text: A common way to partition the HIP implementation is to implement a keying daemon in user-space that interacts with kernel-level support for ESP, as shown in Figure 1. However, the HIPL project has demonstrated that it is also possible to support HIP with a purely kernel-level implementation. New text: A HIP implementation typically consists of a key management process that coordinates with an IPsec-extended stack, as shown in Figure 1. In practice, HIP has been implemented entirely in user-space, entirely in the kernel, or as a hybrid with a user-space key management process and a kernel-level ESP. > - Section 2.3.1, page 10, 1st paragraph: > s/4) a ad-hoc/4) an ad-hoc OK > - Section 2.3.1, page 11, paragraph starting with "Over time...": > I suggest to split this paragraph after "...1) and 3). I.e., starting > "Implementing the first approach..." as a new paragraph. OK > - Section 2.4, page 16, 3rd paragraph: > The conclusion of the first sentence isn't that obvious for an average > reader. It would be good to give a reference/hint why running IPv6 apps > over IPv4 (and vice versa) is made possible by HIP. Old text: HIP makes it possible to use IPv6 applications over the IPv4 network and vice versa. The interfamily portion of the BEET patch in the Linux kernel was found more difficult to complete compared with the single-family processing. All three open source HIP implementations have demonstrated some form of interfamily handoff support.=20 New text: HIP makes it possible to use IPv6 applications over the IPv4 network and vice versa. This has been called interfamily operation (flexibility between different address families) and is enabled by the fact that the transport pseudoheader is based on HITs regardless of whether the=20 application or the underlying network path is based on IPv4. =20 All three open source HIP implementations have demonstrated some form of= =20 interfamily handoff support. The interfamily portion of the BEET patch in the Linux kernel was found more difficult to complete compared with t= he single-family processing. (new paragraph break here) > - Section 3.5, page 20, 3rd paragraph: > s/200 rps/200 requests per second/ OK > - Section 5.4, page 24, paragraph starting with "A HIP-aware...": > The last sentence is not completely correct, as a change of the IP > address may remove a firewall (or any other network entity) from the > data packet path between source and destination. In this case, the > firewall would not be able to learn any of the changes anymore. I > suggest adding at the end of the sentence ", if still on the path." OK If no other comments, I will publish the -13 version before the cutoff next= Monday. - Tom From zehn.cao@gmail.com Sun Jul 3 01:04:10 2011 Return-Path: X-Original-To: hiprg@ietfa.amsl.com Delivered-To: hiprg@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id D404F21F87C6 for ; Sun, 3 Jul 2011 01:04:10 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -1.74 X-Spam-Level: X-Spam-Status: No, score=-1.74 tagged_above=-999 required=5 tests=[AWL=-0.930, BAYES_00=-2.599, CN_BODY_35=0.339, MIME_CHARSET_FARAWAY=2.45, RCVD_IN_DNSWL_LOW=-1] Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id MF4M5qHq9ajX for ; Sun, 3 Jul 2011 01:04:10 -0700 (PDT) Received: from mail-iw0-f182.google.com (mail-iw0-f182.google.com [209.85.214.182]) by ietfa.amsl.com (Postfix) with ESMTP id B4EE721F87C4 for ; Sun, 3 Jul 2011 01:04:09 -0700 (PDT) Received: by iwr19 with SMTP id 19so5108021iwr.13 for ; Sun, 03 Jul 2011 01:04:09 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type:content-transfer-encoding; bh=Nh+Ygx/EV/sWBS03D9A4EgNBWZ7S2W/742RqlapWoYE=; b=emtMWe0Gb2cu6Xc49jw1+G6Pdko4hjYLuRhY67+3ywClfx6QFvot1QERBX8UMobxbe RJ40hz70XyWzRz+xdxa6pFavP2cHqY3eePYOQOGNXpdilqyzwyupgAyhqqFedHjmIhn5 kvg71r2SVMWEgmIqyeo1mvEGrxMp0Tu6DCjFQ= MIME-Version: 1.0 Received: by 10.42.11.207 with SMTP id v15mr5622445icv.22.1309680249082; Sun, 03 Jul 2011 01:04:09 -0700 (PDT) Received: by 10.42.169.193 with HTTP; Sun, 3 Jul 2011 01:04:08 -0700 (PDT) In-Reply-To: <4E0C1878.1030609@hiit.fi> References: <201106281659415514469@bupt.edu.cn> <201106301130508243153@bupt.edu.cn> <4E0C1878.1030609@hiit.fi> Date: Sun, 3 Jul 2011 16:04:08 +0800 Message-ID: From: Zhen Cao To: Andrei Gurtov Content-Type: text/plain; charset=GB2312 Content-Transfer-Encoding: quoted-printable Cc: Wendong WANG , hiprg Subject: Re: [hiprg] HIPRG charter discussion X-BeenThere: hiprg@irtf.org X-Mailman-Version: 2.1.12 Precedence: list List-Id: "Host Identity Protocol \(HIP\) Research Group" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 03 Jul 2011 08:04:10 -0000 Hi Andrei, Attendance is not a problem. China Mobile has been actively attending IETF for more than 6 years, 10 people each time. And we are also always alive on the mailing list. Thank you, Zhen -China Mobile On Thu, Jun 30, 2011 at 2:32 PM, Andrei Gurtov wrote: > > Can you commit to attend the HIPRG meetings at IETF for one-two years to > contribute to h-hip draft development or at least provide active > feedback on the mailing list (e.g. at least one email/week)? > > Same question also applies to China mobile. > > Andrei > > > Wendong WANG wrote: >> >> >> Our team has >> interesting on the hierarchical HIT research work. we have already imple= mented a demo of ID-Locator mapping services based on HIP. >> We also hope to do more works on it for the future Internet mobility and= security functions. >> Wendong WANG >> Beijing Universty of Posts and Telecommunications (BUPT) >> 2011-06-30 >> >> >> >>> -----=D3=CA=BC=FE=D4=AD=BC=FE----- >>> =B7=A2=BC=FE=C8=CB: Andrei Gurtov [mailto:gurtov@hiit.fi] >>> =B7=A2=CB=CD=CA=B1=BC=E4: 2011=C4=EA6=D4=C214=C8=D5 17:44 >>> =CA=D5=BC=FE=C8=CB: Xu Xiaohu >>> =B3=AD=CB=CD: 'Henderson, Thomas R'; hiprg@irtf.org; irtf-chair@irsg.or= g >>> =D6=F7=CC=E2: Re: [hiprg] HIPRG charter discussion >>> >>> >>> Hei Xiaohu, >>> >>> That's an interesting topic, but there should be interest of several >>> organizations to discuss and develop it jointly at HIPRG. Can you think >>> of others who would be willing to commit to this topic for a couple >>> years? Maybe China mobile, Tsinghua University? >>> >>> Andrei >>> >>> Xu Xiaohu wrote: >>> > Hi Tom and all, >>> > >>> > I propose to consider taking the hierarchical HIT research as a new c= harter >>> > item. IMHO, there are at least two major benefits of using hierarchic= al HITs >>> > from the commercial deployment perspectives: >>> > >>> > First, the ID/HIT registration management service and the ID-to-Locat= or >>> > mapping service corresponding to the hierarchical HITs could be run i= n a >>> > hierarchical manner. In other words, such global mobility management >>> service >>> > systems could be operated by different countries and different operat= ors >>> > with clear administrative domain boundaries and reasonable business >>> models, >>> > just like the telephone number space in the telephone network and the= home >>> > address space in the mobile IP network. In addition, the existing DNS >>> > infrastructure doesn't need to be changed largely. That's to say, HIT= s of >>> > the HIP hosts could be stored directly as their corresponding AAAA RR= s in >>> > the existing DNS infrastructure. >>> > >>> > Second, the usage of hierarchical HITs will ease the transition for H= IP. For >>> > instance, legacy IPv6 hosts could access mobile HIP hosts via provide= r-owned >>> > HIP proxy devices (just as home agents in the mobile IP network) sinc= e the >>> > hierarchical HITs could be routable in the Internet. On the contrary, >>> > ORCHIDs are not routable in the Internet since there is no reasonable >>> > business motivation for operators to deploy HIP proxy devices for suc= h flat >>> > identifiers. >>> > >>> > There has been some proposals and presentations discussing about >>> > hierarchical HITs in HIPRG before as follows: >>> > http://tools.ietf.org/html/draft-xu-hip-hierarchical-02 >>> > http://tools.ietf.org/html/draft-kuptsov-hhit-02 >>> > http://tools.ietf.org/html/draft-xu-rangi-04 >>> > >>> > By the way, we have implemented the RANGI >>> > (http://tools.ietf.org/html/draft-xu-rangi-04) prototype which uses a >>> > hierarchical and cryptographic host IDs with delegation-oriented stru= cture. >>> > Hope we could have a chance to show the implementation details and >>> > verification results at the forthcoming IETF meeting in Quebec City. >>> > >>> > Best regards, >>> > Xiaohu >>> > >>> > >>> >> -----=D3=CA=BC=FE=D4=AD=BC=FE----- >>> >> =B7=A2=BC=FE=C8=CB: hiprg-bounces@irtf.org [mailto:hiprg-bounces@irt= f.org] =B4=FA=B1=ED >>> >> Henderson, Thomas R >>> >> =B7=A2=CB=CD=CA=B1=BC=E4: 2011=C4=EA6=D4=C26=C8=D5 22:49 >>> >> =CA=D5=BC=FE=C8=CB: hiprg@irtf.org >>> >> =B3=AD=CB=CD: 'irtf-chair@irsg.org' >>> >> =D6=F7=CC=E2: [hiprg] HIPRG charter discussion >>> >> >>> >> With the completion of the experiment report (our main RG charter it= em >>> > since >>> >> the RG's inception), I would like to ask about future directions of = the >>> > RG. >>> >> Outside of completing our current RG drafts, we need to try to defin= e some >>> >> new collaborative work items and define what role the RG will play >>> > relative to >>> >> the WG. >>> >> >>> >> These work items should ideally satisfy the following criteria: >>> >> - is the research area clear and relevant for the Internet community= and >>> > for >>> >> HIP in particular? What are the expected outcomes and impact? >>> >> - will the RG foster work that would not be done otherwise? For ins= tance, >>> >> participation drawn from more than a single institution or country. = Can >>> > we >>> >> try to identify individuals for this anticipated participation? >>> >> >>> >> We can have some discussion of this at the next meeting but I would = like >>> > to see >>> >> whether we can start identifying some topics on the list before the >>> > meeting. >>> >> - Tom >>> >> _______________________________________________ >>> >> hiprg mailing list >>> >> hiprg@irtf.org >>> >> https://www.irtf.org/mailman/listinfo/hiprg >>> > >>> > _______________________________________________ >>> > hiprg mailing list >>> > hiprg@irtf.org >>> > https://www.irtf.org/mailman/listinfo/hiprg >> >> >> ------------------------------------------------------------------------ >> >> _______________________________________________ >> hiprg mailing list >> hiprg@irtf.org >> https://www.irtf.org/mailman/listinfo/hiprg > > _______________________________________________ > hiprg mailing list > hiprg@irtf.org > https://www.irtf.org/mailman/listinfo/hiprg > --=20 Best regards, Zhen From jeffrey.m.ahrenholz@boeing.com Fri Jul 8 13:03:25 2011 Return-Path: X-Original-To: hiprg@ietfa.amsl.com Delivered-To: hiprg@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 2140321F8CA2 for ; Fri, 8 Jul 2011 13:03:25 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -5.8 X-Spam-Level: X-Spam-Status: No, score=-5.8 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4, SARE_SUB_RAND_LETTRS4=0.799] Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id jRfg+uJcG1lL for ; Fri, 8 Jul 2011 13:03:24 -0700 (PDT) Received: from blv-smtpout-01.boeing.com (blv-smtpout-01.boeing.com [130.76.32.69]) by ietfa.amsl.com (Postfix) with ESMTP id 87D3621F8C93 for ; Fri, 8 Jul 2011 13:03:24 -0700 (PDT) Received: from stl-av-01.boeing.com (stl-av-01.boeing.com [192.76.190.6]) by blv-smtpout-01.ns.cs.boeing.com (8.14.4/8.14.4/8.14.4/SMTPOUT) with ESMTP id p68K3Mjf025216 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=FAIL); Fri, 8 Jul 2011 13:03:23 -0700 (PDT) Received: from stl-av-01.boeing.com (localhost [127.0.0.1]) by stl-av-01.boeing.com (8.14.4/8.14.4/DOWNSTREAM_RELAY) with ESMTP id p68K3Le7007600; Fri, 8 Jul 2011 15:03:21 -0500 (CDT) Received: from XCH-NWHT-02.nw.nos.boeing.com (xch-nwht-02.nw.nos.boeing.com [130.247.70.248]) by stl-av-01.boeing.com (8.14.4/8.14.4/UPSTREAM_RELAY) with ESMTP id p68K3L4f007576 (version=TLSv1/SSLv3 cipher=RC4-MD5 bits=128 verify=OK); Fri, 8 Jul 2011 15:03:21 -0500 (CDT) Received: from XCH-NW-12V.nw.nos.boeing.com ([130.247.25.246]) by XCH-NWHT-02.nw.nos.boeing.com ([130.247.70.248]) with mapi; Fri, 8 Jul 2011 13:03:20 -0700 From: "Ahrenholz, Jeffrey M" To: Martin Stiemerling , "hiprg@irtf.org" Date: Fri, 8 Jul 2011 13:03:21 -0700 Thread-Topic: Review of draft-irtf-hiprg-dht-03 Thread-Index: AcwyWxDcoW/lGzJLR4m2SC8gbjhAjQLOERuw Message-ID: References: In-Reply-To: Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: acceptlanguage: en-US Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable MIME-Version: 1.0 Subject: Re: [hiprg] Review of draft-irtf-hiprg-dht-03 X-BeenThere: hiprg@irtf.org X-Mailman-Version: 2.1.12 Precedence: list List-Id: "Host Identity Protocol \(HIP\) Research Group" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 08 Jul 2011 20:03:25 -0000 Martin, Thanks for your review. I've posted a -04 revision with changes mentioned h= ere. Comments inline below. > I would swap the Section 3 and Section 4. Section 3 is > relying on the knowledge about what the HDRRs are, but > all of this is introduced in Section 4.=20 Done: sections 3 and 4 are swapped, with a little introductory text (moved = from the lookup section) at the beginning of the HDRR section. > - Section 3, page 8, first paragraph on that page: > How often should a HIP peer check whether the name to HIT > binding is still valid? The text only says that a check=20 > if needed, but there is no hint to the frequency, e.g., > years, days, hours, minutes, seconds (?) OK, I've added this sentence: " For example, local policy may specify checking the name-to-HIT binding on a daily basis, while the address record is updated hourly for active peers." Usually I keep HITs tied to a specific name for a long time (years), are th= ere other thoughts on reasonable frequencies? =20 > - Section 4, page 15, last paragraph: > This proposed server side checking could be source of a=20 > denial of service attack, as the DHT server would need=20 > to do some processing on its own. I would either remove=20 > this or document it well in the security section.=20 I added a paragraph to the security considerations section. Is it enough? A= ny other thoughts on techniques the server should use to mitigate DoS? > - Section 6, page 18, 4th paragraph: > This latency considerations neglect the processing impact > of the DHT itself. DHTs are not the fastest lookup mechanism > in the world. This should also be documented as an impacting factor.=20 =20 I re-worded this paragraph to include DHT slowness as impacting the latency= . > - Section 1, first paragraph: > "DHTs are also designed to support frequently updating" > What is frequently in this case? I would understand frequently in=20 > the range of seconds, but this may not be true for DHTs. DHTs can > be updated more frequently than a DNS based approach and that is=20 > what you are probably trying to say here. Yes, more frequently than DNS, fixed. > - Section 2, 3rd paragraph, 1st sentence: > " OpenDHT stores values using (hash) keys."=20 > This is incomplete. I would suggest to write > "OpenDHT stores values and indexes those by using (hash) keys." Fixed. > - Appendix A: > Please add a note that this appendix should be removed by=20 > the RFC editor (assuming that this is the intention). OK, added the note to the appendix title. -Jeff From thomas.r.henderson@boeing.com Sat Jul 9 10:22:02 2011 Return-Path: X-Original-To: hiprg@ietfa.amsl.com Delivered-To: hiprg@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id C6C4921F8653 for ; Sat, 9 Jul 2011 10:22:02 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -106.2 X-Spam-Level: X-Spam-Status: No, score=-106.2 tagged_above=-999 required=5 tests=[AWL=0.400, BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4, USER_IN_WHITELIST=-100] Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 1buRxHN3T1vI for ; Sat, 9 Jul 2011 10:22:02 -0700 (PDT) Received: from stl-smtpout-01.boeing.com (stl-smtpout-01.boeing.com [130.76.96.56]) by ietfa.amsl.com (Postfix) with ESMTP id 5514D21F864E for ; Sat, 9 Jul 2011 10:22:01 -0700 (PDT) Received: from stl-av-01.boeing.com (stl-av-01.boeing.com [192.76.190.6]) by stl-smtpout-01.ns.cs.boeing.com (8.14.4/8.14.4/8.14.4/SMTPOUT) with ESMTP id p69HM0Z3010118 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=FAIL) for ; Sat, 9 Jul 2011 12:22:01 -0500 (CDT) Received: from stl-av-01.boeing.com (localhost [127.0.0.1]) by stl-av-01.boeing.com (8.14.4/8.14.4/DOWNSTREAM_RELAY) with ESMTP id p69HM0L6007519 for ; Sat, 9 Jul 2011 12:22:00 -0500 (CDT) Received: from XCH-NWHT-06.nw.nos.boeing.com (xch-nwht-06.nw.nos.boeing.com [130.247.25.110]) by stl-av-01.boeing.com (8.14.4/8.14.4/UPSTREAM_RELAY) with ESMTP id p69HM0WC007499 (version=TLSv1/SSLv3 cipher=RC4-MD5 bits=128 verify=OK) for ; Sat, 9 Jul 2011 12:22:00 -0500 (CDT) Received: from XCH-NW-10V.nw.nos.boeing.com ([130.247.25.83]) by XCH-NWHT-06.nw.nos.boeing.com ([130.247.25.110]) with mapi; Sat, 9 Jul 2011 10:21:59 -0700 From: "Henderson, Thomas R" To: "hiprg@irtf.org" Date: Sat, 9 Jul 2011 10:21:59 -0700 Thread-Topic: hybrid dns/dht performance cited in experiment report Thread-Index: Acw+XLWXpdB5m+3aSSG2vRlw0PpC4w== Message-ID: <7CC566635CFE364D87DC5803D4712A6C4CEFAF037B@XCH-NW-10V.nw.nos.boeing.com> Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: acceptlanguage: en-US Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable MIME-Version: 1.0 Subject: [hiprg] hybrid dns/dht performance cited in experiment report X-BeenThere: hiprg@irtf.org X-Mailman-Version: 2.1.12 Precedence: list List-Id: "Host Identity Protocol \(HIP\) Research Group" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 09 Jul 2011 17:22:02 -0000 One of Martin's comments pertained to a section in the draft regarding some= hybrid DNS/DHT performance numbers: http://tools.ietf.org/html/draft-irtf-hip-experiment-12#section-3.5 However, I could not find the citation that should go with this data. Can = someone provide a citation? If someone is familiar with this data, is the = data cited in the experiment report correct? I would like to fix this along with the changes Martin suggested before the= IETF 81 deadline. - Tom From pascal.urien@gmail.com Sun Jul 10 09:46:04 2011 Return-Path: X-Original-To: hiprg@ietfa.amsl.com Delivered-To: hiprg@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 8A7FD21F8747 for ; Sun, 10 Jul 2011 09:46:04 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -2.799 X-Spam-Level: X-Spam-Status: No, score=-2.799 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-1, SARE_SUB_RAND_LETTRS4=0.799] Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id xoCoxoeqrcHs for ; Sun, 10 Jul 2011 09:46:03 -0700 (PDT) Received: from mail-qy0-f182.google.com (mail-qy0-f182.google.com [209.85.216.182]) by ietfa.amsl.com (Postfix) with ESMTP id B190021F8744 for ; Sun, 10 Jul 2011 09:46:03 -0700 (PDT) Received: by qyk38 with SMTP id 38so2121136qyk.13 for ; Sun, 10 Jul 2011 09:46:03 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=mime-version:date:message-id:subject:from:to:content-type; bh=1qRDl7nQfGFJm9vwIXFRrIZkoN9TBXIgFlu6mCDHKBU=; b=BG0qORCrIuTs8LO9jLH6rpyIe8odi/CAXoKngmFDWeUMr2OVjkF1BxxgXnRUZdLWpr ieEl5QfyWV/vvf09lzgJWwvUB6SHRLM0QrxXVz3XjbmJE8iB1BoiyBNtWnjlboXPEQNM AUY2idovMu0KDMftrZRNafm/VTq10if1suMUQ= MIME-Version: 1.0 Received: by 10.229.10.21 with SMTP id n21mr1818599qcn.221.1310316361333; Sun, 10 Jul 2011 09:46:01 -0700 (PDT) Received: by 10.229.136.131 with HTTP; Sun, 10 Jul 2011 09:46:01 -0700 (PDT) Date: Sun, 10 Jul 2011 18:46:01 +0200 Message-ID: From: Pascal Urien To: hiprg@irtf.org Content-Type: multipart/alternative; boundary=0016e6496b4642ba6a04a7b9cdd0 Subject: [hiprg] draft-irtf-hiprg-rfid X-BeenThere: hiprg@irtf.org X-Mailman-Version: 2.1.12 Precedence: list List-Id: "Host Identity Protocol \(HIP\) Research Group" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 10 Jul 2011 16:46:04 -0000 --0016e6496b4642ba6a04a7b9cdd0 Content-Type: text/plain; charset=ISO-8859-1 Hi All, A new version of the draft-irtf-hiprg-rfid has been posted The first experimental platform working with Android 2.3 is now available see http://perso.telecom-paristech.fr/~urien/hiprfid/index.html for details Best Regards Pascal --0016e6496b4642ba6a04a7b9cdd0 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable
Hi All,
=A0
=A0A new version of the draft-irtf-hiprg-rfid has been posted
=A0
=A0The first experimental platform working with Android 2.3 is now ava= ilable
=A0
=A0
Best Regards
=A0
Pascal
--0016e6496b4642ba6a04a7b9cdd0-- From goodzi@gmail.com Thu Jul 14 03:58:34 2011 Return-Path: X-Original-To: hiprg@ietfa.amsl.com Delivered-To: hiprg@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id DC28421F86D9 for ; Thu, 14 Jul 2011 03:58:34 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -3.598 X-Spam-Level: X-Spam-Status: No, score=-3.598 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-1] Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id FDEkOlt9fQ2Q for ; Thu, 14 Jul 2011 03:58:34 -0700 (PDT) Received: from mail-ew0-f54.google.com (mail-ew0-f54.google.com [209.85.215.54]) by ietfa.amsl.com (Postfix) with ESMTP id 6BBF421F85B5 for ; Thu, 14 Jul 2011 03:58:31 -0700 (PDT) Received: by ewy1 with SMTP id 1so90396ewy.13 for ; Thu, 14 Jul 2011 03:58:30 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=mime-version:date:message-id:subject:from:to:cc:content-type; bh=uWalCPUf2WpQ7kzk3PLnY/uXbO+WgQls4nHWniP6BrQ=; b=jrc31pweUXgGvZ65ZXLTHtfb85UHRRrPG/c6E6Jg1MeNLXagscSavSxFSK3PlxImtr 7+UEa9kUR1Bud39rtb0BR4bz3coJzf0Ss8UlrVI20GF+3JJbqmRT7vlk0IVaCfN47LjV LFeftUNobvwXqeyRb840RU6SoeqDyta9dKx68= MIME-Version: 1.0 Received: by 10.14.98.79 with SMTP id u55mr711106eef.27.1310641110287; Thu, 14 Jul 2011 03:58:30 -0700 (PDT) Received: by 10.14.53.2 with HTTP; Thu, 14 Jul 2011 03:58:30 -0700 (PDT) Date: Thu, 14 Jul 2011 12:58:30 +0200 Message-ID: From: Bokor Laszlo To: hiprg@irtf.org Content-Type: multipart/alternative; boundary=bcaec517a75ece85fa04a805690c Cc: hipsec@ietf.org, hipl-users@freelists.org Subject: [hiprg] research paper about a flat and distributed HIP scheme for future mobile networks X-BeenThere: hiprg@irtf.org X-Mailman-Version: 2.1.12 Precedence: list List-Id: "Host Identity Protocol \(HIP\) Research Group" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 14 Jul 2011 10:58:35 -0000 --bcaec517a75ece85fa04a805690c Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Dear Folks, please let me advertise you a research paper about a flat and distributed HIP scheme for future mobile networks: Title: Evaluation of two integrated signalling schemes for the Ultra Flat Architecture using SIP, IEEE 802.21, and HIP/PMIP protocols ACM link: http://portal.acm.org/citation.cfm?id=3D1975468 DOI: http://dx.doi.org/10.1016/j.comnet.2011.02.005 I hope you will find the above article interesting, and also that you will provide us with feedbacks on our work. Best regards, goodzi -- L=E1szl=F3 BOKOR Budapest University of Technology and Economics (BME) Department of Telecommunications (HIT) - Mobile Innovation Centre (MIK) Tel: +36-1-463-3420, Fax: +36-1-463-3307 web: http://www.hit.bme.hu/~bokorl --bcaec517a75ece85fa04a805690c Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Dear Folks,

please let me advertise you a research paper about a fla= t and distributed HIP scheme for future mobile networks:

Title: Eval= uation of two integrated signalling schemes for the Ultra Flat Architecture= using SIP, IEEE 802.21, and HIP/PMIP protocols
ACM link: http:= //portal.acm.org/citation.cfm?id=3D1975468
DOI: http://dx.doi.org/10.1016/j.comnet.2= 011.02.005

I hope you will find the above article interesting, and also that you w= ill provide us with feedbacks on our work.

Best regards,
goodzi
--
L=E1szl=F3 BOKOR
Budapest University of Technology and Econo= mics (BME)
Department of Telecommunications (HIT) - Mobile Innovation Centre (MIK)
= Tel: +36-1-463-3420, Fax: +36-1-463-3307
web: http://www.hit.bme.hu/~bokorl
--bcaec517a75ece85fa04a805690c-- From thomas.r.henderson@boeing.com Tue Jul 19 21:58:01 2011 Return-Path: X-Original-To: hiprg@ietfa.amsl.com Delivered-To: hiprg@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 3DBB521F87C2 for ; Tue, 19 Jul 2011 21:58:01 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -106.499 X-Spam-Level: X-Spam-Status: No, score=-106.499 tagged_above=-999 required=5 tests=[AWL=0.100, BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4, USER_IN_WHITELIST=-100] Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Ltv8hGtIyQGw for ; Tue, 19 Jul 2011 21:58:00 -0700 (PDT) Received: from stl-smtpout-01.boeing.com (stl-smtpout-01.boeing.com [130.76.96.56]) by ietfa.amsl.com (Postfix) with ESMTP id B3C8021F87BD for ; Tue, 19 Jul 2011 21:57:57 -0700 (PDT) Received: from slb-av-01.boeing.com (slb-av-01.boeing.com [129.172.13.4]) by stl-smtpout-01.ns.cs.boeing.com (8.14.4/8.14.4/8.14.4/SMTPOUT) with ESMTP id p6K4vmGQ009268 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=FAIL) for ; Tue, 19 Jul 2011 23:57:48 -0500 (CDT) Received: from slb-av-01.boeing.com (localhost [127.0.0.1]) by slb-av-01.boeing.com (8.14.4/8.14.4/DOWNSTREAM_RELAY) with ESMTP id p6K4vlgl018178 for ; Tue, 19 Jul 2011 21:57:47 -0700 (PDT) Received: from XCH-NWHT-04.nw.nos.boeing.com (xch-nwht-04.nw.nos.boeing.com [130.247.64.250]) by slb-av-01.boeing.com (8.14.4/8.14.4/UPSTREAM_RELAY) with ESMTP id p6K4vl7F018175 (version=TLSv1/SSLv3 cipher=RC4-MD5 bits=128 verify=OK) for ; Tue, 19 Jul 2011 21:57:47 -0700 (PDT) Received: from XCH-NW-10V.nw.nos.boeing.com ([130.247.25.83]) by XCH-NWHT-04.nw.nos.boeing.com ([130.247.64.250]) with mapi; Tue, 19 Jul 2011 21:57:47 -0700 From: "Henderson, Thomas R" To: "hiprg@irtf.org" Date: Tue, 19 Jul 2011 21:57:47 -0700 Thread-Topic: proposed HIPRG meeting slot change Thread-Index: AcxGmZDo2Me3u8+5SBaMsaCXgphpEw== Message-ID: <7CC566635CFE364D87DC5803D4712A6C4CEFAF0403@XCH-NW-10V.nw.nos.boeing.com> Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: acceptlanguage: en-US Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable MIME-Version: 1.0 Subject: [hiprg] proposed HIPRG meeting slot change X-BeenThere: hiprg@irtf.org X-Mailman-Version: 2.1.12 Precedence: list List-Id: "Host Identity Protocol \(HIP\) Research Group" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 20 Jul 2011 04:58:01 -0000 Hi all, We've been asked whether HIPRG would be willing to move the meeting slot to= Thursday morning at 0900-1130 from Wednesday morning at 0900-1130. Lars w= ants to move the IRTF open meeting to Wednesday to deconflict it with the T= hursday mobopts RG meeting. >From my reading of the agenda, moving HIPRG to Thursday may be preferable f= or some of our participants who also attend core and mptcp working groups (= which also are scheduled for Wednesday morning). =20 Please let me know if moving HIPRG to Thursday morning, in place of the IRT= F open meeting, will cause problems for your planned attendance; otherwise,= I will let Lars know that the switch would be OK. =20 - Tom From thomas.r.henderson@boeing.com Fri Jul 22 11:14:11 2011 Return-Path: X-Original-To: hiprg@ietfa.amsl.com Delivered-To: hiprg@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 723A821F8B58 for ; Fri, 22 Jul 2011 11:14:11 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -106.519 X-Spam-Level: X-Spam-Status: No, score=-106.519 tagged_above=-999 required=5 tests=[AWL=0.080, BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4, USER_IN_WHITELIST=-100] Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 1wIpOYvvr1Ez for ; Fri, 22 Jul 2011 11:14:11 -0700 (PDT) Received: from slb-smtpout-01.boeing.com (slb-smtpout-01.boeing.com [130.76.64.48]) by ietfa.amsl.com (Postfix) with ESMTP id 0966021F8B57 for ; Fri, 22 Jul 2011 11:14:10 -0700 (PDT) Received: from stl-av-01.boeing.com (stl-av-01.boeing.com [192.76.190.6]) by slb-smtpout-01.ns.cs.boeing.com (8.14.4/8.14.4/8.14.4/SMTPOUT) with ESMTP id p6MIE9Cp002919 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=FAIL) for ; Fri, 22 Jul 2011 11:14:10 -0700 (PDT) Received: from stl-av-01.boeing.com (localhost [127.0.0.1]) by stl-av-01.boeing.com (8.14.4/8.14.4/DOWNSTREAM_RELAY) with ESMTP id p6MIE9EM022688 for ; Fri, 22 Jul 2011 13:14:09 -0500 (CDT) Received: from XCH-NWHT-02.nw.nos.boeing.com (xch-nwht-02.nw.nos.boeing.com [130.247.70.248]) by stl-av-01.boeing.com (8.14.4/8.14.4/UPSTREAM_RELAY) with ESMTP id p6MIE8Nq022670 (version=TLSv1/SSLv3 cipher=RC4-MD5 bits=128 verify=OK) for ; Fri, 22 Jul 2011 13:14:08 -0500 (CDT) Received: from XCH-NW-10V.nw.nos.boeing.com ([130.247.25.83]) by XCH-NWHT-02.nw.nos.boeing.com ([130.247.70.248]) with mapi; Fri, 22 Jul 2011 11:14:08 -0700 From: "Henderson, Thomas R" To: "hiprg@irtf.org" Date: Fri, 22 Jul 2011 11:14:07 -0700 Thread-Topic: HIPRG meeting moved to Thursday morning Thread-Index: AcxImyWzmWvaGR5lRMasG5TEP1eNnw== Message-ID: <7CC566635CFE364D87DC5803D4712A6C4CEFAF0449@XCH-NW-10V.nw.nos.boeing.com> Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: acceptlanguage: en-US Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable MIME-Version: 1.0 Subject: [hiprg] HIPRG meeting moved to Thursday morning X-BeenThere: hiprg@irtf.org X-Mailman-Version: 2.1.12 Precedence: list List-Id: "Host Identity Protocol \(HIP\) Research Group" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 22 Jul 2011 18:14:11 -0000 Please note the agenda change, which has been posted on the IETF website no= w. Please have a look at the current agenda and send additional requests to me= ASAP. http://www.ietf.org/proceedings/81/agenda/HIPRG.txt Thanks, Tom From thomas.r.henderson@boeing.com Sun Jul 24 22:53:42 2011 Return-Path: X-Original-To: hiprg@ietfa.amsl.com Delivered-To: hiprg@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 4A25321F8ADC for ; Sun, 24 Jul 2011 22:53:42 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -106.532 X-Spam-Level: X-Spam-Status: No, score=-106.532 tagged_above=-999 required=5 tests=[AWL=0.067, BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4, USER_IN_WHITELIST=-100] Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id ENiHBXI5FpLx for ; Sun, 24 Jul 2011 22:53:41 -0700 (PDT) Received: from slb-smtpout-01.boeing.com (slb-smtpout-01.boeing.com [130.76.64.48]) by ietfa.amsl.com (Postfix) with ESMTP id C562F21F8AD9 for ; Sun, 24 Jul 2011 22:53:41 -0700 (PDT) Received: from slb-av-01.boeing.com (slb-av-01.boeing.com [129.172.13.4]) by slb-smtpout-01.ns.cs.boeing.com (8.14.4/8.14.4/8.14.4/SMTPOUT) with ESMTP id p6P5raDt015187 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=FAIL) for ; Sun, 24 Jul 2011 22:53:36 -0700 (PDT) Received: from slb-av-01.boeing.com (localhost [127.0.0.1]) by slb-av-01.boeing.com (8.14.4/8.14.4/DOWNSTREAM_RELAY) with ESMTP id p6P5rZel021615 for ; Sun, 24 Jul 2011 22:53:35 -0700 (PDT) Received: from XCH-NWHT-10.nw.nos.boeing.com (xch-nwht-10.nw.nos.boeing.com [130.247.25.113]) by slb-av-01.boeing.com (8.14.4/8.14.4/UPSTREAM_RELAY) with ESMTP id p6P5rZ7m021603 (version=TLSv1/SSLv3 cipher=RC4-MD5 bits=128 verify=OK) for ; Sun, 24 Jul 2011 22:53:35 -0700 (PDT) Received: from XCH-NW-10V.nw.nos.boeing.com ([130.247.25.83]) by XCH-NWHT-10.nw.nos.boeing.com ([130.247.25.113]) with mapi; Sun, 24 Jul 2011 22:53:35 -0700 From: "Henderson, Thomas R" To: "hiprg@irtf.org" Date: Sun, 24 Jul 2011 22:53:34 -0700 Thread-Topic: meeting update Thread-Index: AcxKjzBrg92AvUABSICd1LXBD1Xi2w== Message-ID: <7CC566635CFE364D87DC5803D4712A6C4CEFAF0461@XCH-NW-10V.nw.nos.boeing.com> Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: acceptlanguage: en-US Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable MIME-Version: 1.0 Subject: [hiprg] meeting update X-BeenThere: hiprg@irtf.org X-Mailman-Version: 2.1.12 Precedence: list List-Id: "Host Identity Protocol \(HIP\) Research Group" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 25 Jul 2011 05:53:42 -0000 I've updated the agenda on the IETF site this evening. There may be one or= two more presentations added, and I will work with the presenters to defin= e presentation times over the next couple of days. Please note, if you haven't already, that we have traded slots with the IRT= F Open Meeting and will be meeting on Thursday morning instead of Wednesday= morning. The IRTF Open Meeting [*] is a new meeting for this IETF and wil= l probably be of interest to many of you. I also plan to hold some discussion about rechartering and next steps, as p= reviously discussed on the list [**], so please come with your thoughts on = this topic. - Tom [*] http://www.ietf.org/proceedings/81/agenda/IRTF.txt [**] http://www.ietf.org/mail-archive/web/hiprg/current/msg00831.html From heer@informatik.rwth-aachen.de Thu Jul 28 15:08:02 2011 Return-Path: X-Original-To: hiprg@ietfa.amsl.com Delivered-To: hiprg@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id B862811E812A for ; Thu, 28 Jul 2011 15:08:02 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -4.801 X-Spam-Level: X-Spam-Status: No, score=-4.801 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HELO_EQ_DE=0.35, HELO_MISMATCH_DE=1.448, RCVD_IN_DNSWL_MED=-4] Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 61OJh1+I5V+1 for ; Thu, 28 Jul 2011 15:08:01 -0700 (PDT) Received: from mta-1.ms.rz.rwth-aachen.de (mta-1.ms.rz.RWTH-Aachen.DE [134.130.7.72]) by ietfa.amsl.com (Postfix) with ESMTP id 6144211E807E for ; Thu, 28 Jul 2011 15:08:01 -0700 (PDT) MIME-version: 1.0 Content-transfer-encoding: 7BIT Content-type: text/plain; charset=us-ascii Received: from ironport-out-1.rz.rwth-aachen.de ([134.130.5.40]) by mta-1.ms.rz.RWTH-Aachen.de (Sun Java(tm) System Messaging Server 6.3-7.04 (built Sep 26 2008)) with ESMTP id <0LP200D18DHBW470@mta-1.ms.rz.RWTH-Aachen.de> for hiprg@irtf.org; Fri, 29 Jul 2011 00:07:59 +0200 (CEST) X-IronPort-AV: E=Sophos;i="4.67,284,1309730400"; d="scan'208";a="127598921" Received: from relay-auth-2.ms.rz.rwth-aachen.de (HELO relay-auth-2) ([134.130.7.79]) by ironport-in-1.rz.rwth-aachen.de with ESMTP; Fri, 29 Jul 2011 00:07:59 +0200 Received: from [192.168.3.4] ([unknown] [91.179.190.134]) by relay-auth-2.ms.rz.rwth-aachen.de (Sun Java(tm) System Messaging Server 7.0-3.01 64bit (built Dec 9 2008)) with ESMTPA id <0LP200AP2DHAPN00@relay-auth-2.ms.rz.rwth-aachen.de> for hiprg@irtf.org; Fri, 29 Jul 2011 00:07:59 +0200 (CEST) From: Tobias Heer Date: Fri, 29 Jul 2011 00:07:58 +0200 Message-id: <48A70FBD-6BF5-458D-9932-0E431938473F@cs.rwth-aachen.de> To: hiprg@irtf.org X-Mailer: Apple Mail (2.1084) Subject: [hiprg] Starting a list of RG topics of importance/interest X-BeenThere: hiprg@irtf.org X-Mailman-Version: 2.1.12 Precedence: list List-Id: "Host Identity Protocol \(HIP\) Research Group" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 28 Jul 2011 22:08:02 -0000 Hi. Lars raised the question whether there are still enough research questions left to justify a rechartering of the HIPRG. I took this as a reason to classify some of the _ongoing_ efforts into four different research areas. These research areas have been explored partially but by individual problem solutions. There were drafts within each area but none was adopted as RG item because at the time being there were already other issues (RG items) to be addressed. Maybe this description can be the basis for formulating a future research agenda. If not it may at least show current research efforts in the context of HIP. This collection is just an initial proposal. Add your own topics of interest to it or change and extend this list in a reply to the list. * HIP interaction with middleboxes HIP can be a burden or a big advantage for middleboxes. In the last 2 years we've seen quite some proposals to enable secure signaling to middleboxes and inclusion of middleboxes in the HIP communication flow to enable different goals ranging from security to mobility and ease of deployment. With stronger focus on these things, the RG could help to channel the individual efforts into a coherent and complete analysis and could foster the creation of comprehensive solutions. Drafts on my mind are: - draft-lagutin-hip-pla - draft-heer-hip-middle-auth But there is other research in this are as well - (Rene Hummen is working on related topics). - The femtocell presentation today also used HIP middleboxes as specified in draft-heer-hip-middle-auth * HIP as part of the infrastructure There are a number of drafts and papers that use HIP within the network to connect different networks and to create VPN-like network overlays. People have presented quite some ideas within the RG and the RG could be a place to moderate and align these efforts. Ongoing work in this area: - draft-henderson-hip-vpls - HIP and femtocell technology - We have a similar solutions under development at RWTH in the context of the Mobile ACcess project (there were presentations in Beijing and Anaheim) - I guess Mobile Router would also fit in here * HIP derivates for application specific use cases The RFID and the DEX documents are two siblings or offsprings of HIP that target specific scenarios. Nevertheless, these protocols share a common set of features and ideas. Right now these protocols are completely separate but I had discussions with Bob and Pascal and we agreed that some sort of interoperability would be good or even required. However, creating interoperability of these protocols is more than just defining conversion rules because some essential differences remain. An interesting question for me is how we can create that _family_ of interoperable HIP protocols that Bob envisioned. What are the requirements for new family members? Which mechanisms (in standardization and protocol design) are required to achieve a maintainable and evolvable set of protocols. Documents: - draft-moskowitz-hip-rg-dex - draft-irtf-hiprg-rfid - current efforts with the IEEE and IoT-related groups * HIT and ORCHID design. How can we enable hierarchies within the flat HIP namespace to make things like revocation and HIP/IP resolution simpler. This may sound easy at a first glance but there are some tough decisions to make: How many bits can we sacrifice to encode a hierarchy in a HIT. Are there smart ways of avoiding security penalties? Can we use techniques to strengthen the security of the HIT (e.g., similar to CGAs). Are we even moving towards CGAs? How do hierarchies affect other mechanisms in HIP (e.g., cipher negotiation in RFC5201-bis)? How can we manage and use these hierarchies? Related documents: -draft-xu-hip-hierarchical * Use cases for HIP certificates The definition of HIP certificates deliberately excludes the specification of specific use cases. However the certificates were mentioned in quite many presentations in the past. Hence, scenario dependent and scenario independent methods to generate and handle certificates are still largely undefined and unaligned. It would be great if the RG could collect different use cases and condense these in a "best-practices" or "use-cases" document. In addition, mechanisms to signal that certificates are required need to be defined. As these are not part of the minimal set of features required for HIP, I assume that the RG is a good place to bootstrap such work. - draft-heer-hip-service - draft-henderson-hip-vpls - draft-pellikka-hiprg-certreq - HIP and femtocell technology - I have seen certificates pop up in some other places here and there ------------ There may be more research and problem areas that I missed. There may also be additional documents, papers and drafts that I did not mention here. If so, it would be great if people could extend this list. Cheers, Tobi -- Dipl.-Inform. Tobias Heer, Ph.D. Student Chair of Communication and Distributed Systems - comsys RWTH Aachen University, Germany tel: +49 241 80 207 76 web: http://www.comsys.rwth-aachen.de/team/tobias-heer/ blog: http://dtobi.wordpress.com/ card: http://card.ly/dtobi pgp id: AEECA5BF From mkomu@cs.hut.fi Sun Jul 31 23:04:18 2011 Return-Path: X-Original-To: hiprg@ietfa.amsl.com Delivered-To: hiprg@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id C2F0921F8557 for ; Sun, 31 Jul 2011 23:04:18 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -5.205 X-Spam-Level: X-Spam-Status: No, score=-5.205 tagged_above=-999 required=5 tests=[AWL=1.395, BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4] Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id uBFwP5D5Ui5O for ; Sun, 31 Jul 2011 23:04:18 -0700 (PDT) Received: from mail.cs.hut.fi (mail.cs.hut.fi [130.233.192.7]) by ietfa.amsl.com (Postfix) with ESMTP id BBFBC21F8556 for ; Sun, 31 Jul 2011 23:04:17 -0700 (PDT) Received: from hutcs.cs.hut.fi ([130.233.192.10] helo=[127.0.0.1]) by mail.cs.hut.fi with esmtp (Exim 4.54) id 1Qnlbx-0001Ot-7p for hiprg@irtf.org; Mon, 01 Aug 2011 09:04:21 +0300 Message-ID: <4E3641F0.10405@cs.hut.fi> Date: Mon, 01 Aug 2011 09:04:32 +0300 From: Miika Komu User-Agent: Mozilla/5.0 (X11; U; Linux x86_64; en-US; rv:1.9.2.18) Gecko/20110617 Thunderbird/3.1.11 MIME-Version: 1.0 To: hiprg@irtf.org References: <48A70FBD-6BF5-458D-9932-0E431938473F@cs.rwth-aachen.de> In-Reply-To: <48A70FBD-6BF5-458D-9932-0E431938473F@cs.rwth-aachen.de> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Subject: Re: [hiprg] Starting a list of RG topics of importance/interest X-BeenThere: hiprg@irtf.org X-Mailman-Version: 2.1.12 Precedence: list List-Id: "Host Identity Protocol \(HIP\) Research Group" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 01 Aug 2011 06:04:18 -0000 Hi, On 07/29/2011 01:07 AM, Tobias Heer wrote: > Hi. > > Lars raised the question whether there are still enough research questions left > to justify a rechartering of the HIPRG. I took this as a reason to classify > some of the _ongoing_ efforts into four different research areas. These > research areas have been explored partially but by individual problem solutions. > There were drafts within each area but none was adopted as RG item because at > the time being there were already other issues (RG items) to be addressed. Maybe > this description can be the basis for formulating a future research agenda. If > not it may at least show current research efforts in the context of HIP. This > collection is just an initial proposal. Add your own topics of interest to it or > change and extend this list in a reply to the list. > > * HIP interaction with middleboxes > > HIP can be a burden or a big advantage for middleboxes. In the last 2 years > we've seen quite some proposals to enable secure signaling to middleboxes and > inclusion of middleboxes in the HIP communication flow to enable different goals > ranging from security to mobility and ease of deployment. With stronger focus > on these things, the RG could help to channel the individual efforts into a > coherent and complete analysis and could foster the creation of comprehensive > solutions. > > Drafts on my mind are: > - draft-lagutin-hip-pla I have to ask Lagutin of his interest in continuing this work. Samu has had earlier some interest in finishing an implementation of this. > - draft-heer-hip-middle-auth But there is other research in this are as well > - (Rene Hummen is working on related topics). > - The femtocell presentation today also used HIP middleboxes as specified in > draft-heer-hip-middle-auth I believe this is important. +1 > * HIP as part of the infrastructure > > There are a number of drafts and papers that use HIP within the network to > connect different networks and to create VPN-like network overlays. People have > presented quite some ideas within the RG and the RG could be a place to moderate > and align these efforts. > > Ongoing work in this area: > > - draft-henderson-hip-vpls > - HIP and femtocell technology > - We have a similar solutions under development at RWTH in the context of the > Mobile ACcess project (there were presentations in Beijing and Anaheim) > - I guess Mobile Router would also fit in here I believe the VPLS is a nice use scenario of HIP. +1 I have to check the femtocell presentation, sounds interesting too. > * HIP derivates for application specific use cases > > The RFID and the DEX documents are two siblings or offsprings of HIP that target > specific scenarios. Nevertheless, these protocols share a common set of > features and ideas. Right now these protocols are completely separate but I had > discussions with Bob and Pascal and we agreed that some sort of interoperability > would be good or even required. However, creating interoperability of these > protocols is more than just defining conversion rules because some essential > differences remain. An interesting question for me is how we can create that > _family_ of interoperable HIP protocols that Bob envisioned. What are the > requirements for new family members? Which mechanisms (in standardization and > protocol design) are required to achieve a maintainable and evolvable set of > protocols. > > Documents: > - draft-moskowitz-hip-rg-dex > - draft-irtf-hiprg-rfid > - current efforts with the IEEE and IoT-related groups +1 for the interoperability concerns. I think some small things could be adopted to RFC5201bis as well if it makes the protocol more flexible. > * HIT and ORCHID design. > > How can we enable hierarchies within the flat HIP namespace to make things like > revocation and HIP/IP resolution simpler. This may sound easy at a first glance > but there are some tough decisions to make: How many bits can we sacrifice to > encode a hierarchy in a HIT. Are there smart ways of avoiding security > penalties? Can we use techniques to strengthen the security of the HIT (e.g., > similar to CGAs). Are we even moving towards CGAs? How do hierarchies affect > other mechanisms in HIP (e.g., cipher negotiation in RFC5201-bis)? How can we > manage and use these hierarchies? > > Related documents: > > -draft-xu-hip-hierarchical While I believe its feasible for HIP to co-exist without hierarchies, I think this is important as well. Interoperability (and cryptoagility?) needs to be considered again because now there's hierarchical and non-hierarchical HITs. > * Use cases for HIP certificates > > The definition of HIP certificates deliberately excludes the specification of > specific use cases. However the certificates were mentioned in quite many > presentations in the past. Hence, scenario dependent and scenario independent > methods to generate and handle certificates are still largely undefined and > unaligned. It would be great if the RG could collect different use cases and > condense these in a "best-practices" or "use-cases" document. In addition, > mechanisms to signal that certificates are required need to be defined. As > these are not part of the minimal set of features required for HIP, I assume > that the RG is a good place to bootstrap such work. > > - draft-heer-hip-service > - draft-henderson-hip-vpls > - draft-pellikka-hiprg-certreq > - HIP and femtocell technology > - I have seen certificates pop up in some other places here and there +1 > There may be more research and problem areas that I missed. There may also be > additional documents, papers and drafts that I did not mention here. If so, it > would be great if people could extend this list.