From ari.keranen@nomadiclab.com  Wed Mar  2 04:41:33 2011
Return-Path: <ari.keranen@nomadiclab.com>
X-Original-To: hiprg@core3.amsl.com
Delivered-To: hiprg@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id A445E3A67F3 for <hiprg@core3.amsl.com>; Wed,  2 Mar 2011 04:41:33 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2
X-Spam-Level: 
X-Spam-Status: No, score=-2 tagged_above=-999 required=5 tests=[AWL=-0.200, BAYES_00=-2.599, SARE_SUB_RAND_LETTRS4=0.799]
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 ai68HucM93Cj for <hiprg@core3.amsl.com>; Wed,  2 Mar 2011 04:41:32 -0800 (PST)
Received: from gw.nomadiclab.com (unknown [IPv6:2001:14b8:400:101::2]) by core3.amsl.com (Postfix) with ESMTP id 67EF73A67EC for <hiprg@irtf.org>; Wed,  2 Mar 2011 04:41:31 -0800 (PST)
Received: from localhost (localhost [127.0.0.1]) by gw.nomadiclab.com (Postfix) with ESMTP id CBD9E4E6D7; Wed,  2 Mar 2011 14:42:32 +0200 (EET)
X-Virus-Scanned: amavisd-new at nomadiclab.com
Received: from gw.nomadiclab.com ([127.0.0.1]) by localhost (inside.nomadiclab.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id awMJgxd5wWbt; Wed,  2 Mar 2011 14:42:32 +0200 (EET)
Received: from [IPv6:::1] (localhost [IPv6:::1]) by gw.nomadiclab.com (Postfix) with ESMTP id 094E84E6BC; Wed,  2 Mar 2011 14:42:32 +0200 (EET)
Mime-Version: 1.0 (Apple Message framework v1082)
Content-Type: text/plain; charset=us-ascii
From: Ari Keranen <ari.keranen@nomadiclab.com>
In-Reply-To: <7CC566635CFE364D87DC5803D4712A6C4CED25AF20@XCH-NW-10V.nw.nos.boeing.com>
Date: Wed, 2 Mar 2011 14:42:31 +0200
Content-Transfer-Encoding: quoted-printable
Message-Id: <4AED97FB-E08F-4476-9BF2-0F6AE6BB63E5@nomadiclab.com>
References: <A7C7A8B4-FE51-4471-9674-0A5AC54CCC6B@nomadiclab.com> <7CC566635CFE364D87DC5803D4712A6C4CED25AF20@XCH-NW-10V.nw.nos.boeing.com>
To: "Henderson, Thomas R" <thomas.r.henderson@boeing.com>
X-Mailer: Apple Mail (2.1082)
Cc: "hiprg@irtf.org" <hiprg@irtf.org>
Subject: Re: [hiprg] draft-irtf-hip-experiment-10 review
X-BeenThere: hiprg@irtf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: "Host Identity Protocol \(HIP\) Research Group" <hiprg.irtf.org>
List-Unsubscribe: <https://www.irtf.org/mailman/listinfo/hiprg>, <mailto:hiprg-request@irtf.org?subject=unsubscribe>
List-Archive: <http://www.irtf.org/mail-archive/web/hiprg>
List-Post: <mailto:hiprg@irtf.org>
List-Help: <mailto:hiprg-request@irtf.org?subject=help>
List-Subscribe: <https://www.irtf.org/mailman/listinfo/hiprg>, <mailto:hiprg-request@irtf.org?subject=subscribe>
X-List-Received-Date: Wed, 02 Mar 2011 12:41:33 -0000

Hi Tom,

On Mar 1, 2011, at 7:32 AM, Henderson, Thomas R wrote:
>> -----Original Message-----
>> From: Ari Keranen [mailto:ari.keranen@nomadiclab.com]
>> Sent: Monday, February 28, 2011 8:56 AM
>> To: hiprg@irtf.org
>> Cc: Henderson, Thomas R
>> Subject: draft-irtf-hip-experiment-10 review
>>=20
>> Hi,
>>=20
>> I finally managed to have look at the experiment report doc. Here's
>> some comments and nits:
>>=20
>>=20
>> 1.1.  What is HIP?
>>=20
>> Could mention that Standards Track work has been started (in the end =
of
>> the section).
>>=20
>>=20
>> 1.2.  Scope
>>=20
>> During the timeframe of this report (2004-09),
>>=20
>> s/09/2011/
>>=20
>>=20
>> 2.3.8.  Interactions with host firewalls
>>=20
>>   When using HIP over UDP, the host needs to open
>>   just port 10500 in practice.
>>=20
>> This seems to imply that inbound unsolicited packets to 10500 would =
be
>> needed, which is not the case as long as ICE is used (except for the
>> HIP relay server). I'd rather say something like "the firewall needs =
to
>> allow outbound UDP packets and responses to them".
>>=20
>>=20
>=20
> Ari, thanks for the review.  The reason that the document still says =
2009 is that it mainly stopped receiving substantial inputs since that =
time, so to avoid confusion, I propose to rephrase:  "During the period =
of time in which the bulk of this report was drafted (2004-2009), ..."

OK, that makes sense.

> I'll make the other two changes suggested above in the next revision =
(-11), and I have a few more changes to add that Miika suggested.
>=20
> I am waiting to receive inputs on the question I posed recently about =
privacy and identity theft vulnerability of the DH exchange, before =
revising that section and publishing the -11 version.  Yesterday I posed =
a question on the crypto-forum research group list =
(http://www.ietf.org/mail-archive/web/cfrg/current/msg02919.html) and =
I've received some feedback there.  Pekka also pointed me to the 2004 =
paper on BLIND, which I'll review again.

Based on the discussion there, it seems that at least the "vulnerable to =
identity theft" part should be rephrased. Perhaps something like "can't =
hide the identity" would be more appropriate.


Cheers,
Ari=

From jeffrey.m.ahrenholz@boeing.com  Thu Mar  3 08:37:00 2011
Return-Path: <jeffrey.m.ahrenholz@boeing.com>
X-Original-To: hiprg@core3.amsl.com
Delivered-To: hiprg@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 9F0833A68B9 for <hiprg@core3.amsl.com>; Thu,  3 Mar 2011 08:37:00 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.2
X-Spam-Level: 
X-Spam-Status: No, score=-6.2 tagged_above=-999 required=5 tests=[AWL=-0.399,  BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4, SARE_SUB_RAND_LETTRS4=0.799]
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 2fwypTke+oCl for <hiprg@core3.amsl.com>; Thu,  3 Mar 2011 08:36:58 -0800 (PST)
Received: from stl-smtpout-01.boeing.com (stl-smtpout-01.boeing.com [130.76.96.56]) by core3.amsl.com (Postfix) with ESMTP id 6BB353A67F1 for <hiprg@irtf.org>; Thu,  3 Mar 2011 08:36:58 -0800 (PST)
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 p23Gc5I9013005 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=FAIL) for <hiprg@irtf.org>; Thu, 3 Mar 2011 10:38:06 -0600 (CST)
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 p23Gc5OB027970 for <hiprg@irtf.org>; Thu, 3 Mar 2011 10:38:05 -0600 (CST)
Received: from XCH-NWHT-01.nw.nos.boeing.com (xch-nwht-01.nw.nos.boeing.com [130.247.70.222]) by stl-av-01.boeing.com (8.14.4/8.14.4/UPSTREAM_RELAY) with ESMTP id p23Gc4qb027931 (version=TLSv1/SSLv3 cipher=RC4-MD5 bits=128 verify=OK) for <hiprg@irtf.org>; Thu, 3 Mar 2011 10:38:05 -0600 (CST)
Received: from XCH-NW-12V.nw.nos.boeing.com ([130.247.25.246]) by XCH-NWHT-01.nw.nos.boeing.com ([130.247.70.222]) with mapi; Thu, 3 Mar 2011 08:38:04 -0800
From: "Ahrenholz, Jeffrey M" <jeffrey.m.ahrenholz@boeing.com>
To: "hiprg@irtf.org" <hiprg@irtf.org>
Date: Thu, 3 Mar 2011 08:38:15 -0800
Thread-Topic: comments on draft-irtf-hip-experiment-10
Thread-Index: AcvZwWTBuubYa4lFTqOxV5AfccjZJw==
Message-ID: <FD98F9C3CBABA74E89B5D4B5DE0263B9379AA9ED4A@XCH-NW-12V.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] comments on draft-irtf-hip-experiment-10
X-BeenThere: hiprg@irtf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: "Host Identity Protocol \(HIP\) Research Group" <hiprg.irtf.org>
List-Unsubscribe: <https://www.irtf.org/mailman/listinfo/hiprg>, <mailto:hiprg-request@irtf.org?subject=unsubscribe>
List-Archive: <http://www.irtf.org/mail-archive/web/hiprg>
List-Post: <mailto:hiprg@irtf.org>
List-Help: <mailto:hiprg-request@irtf.org?subject=help>
List-Subscribe: <https://www.irtf.org/mailman/listinfo/hiprg>, <mailto:hiprg-request@irtf.org?subject=subscribe>
X-List-Received-Date: Thu, 03 Mar 2011 16:37:00 -0000

I reviewed the experiment report, below are some suggestions.

-Jeff

Section 2
replace "Windows XP and Vista" with "Windows XP/Vista/7"

Section 2.1.1
s/could potentially allow all implementations/all Linux implementations/

Section 2.3.1
For option 5) "DNS proxy supporting RFC5205", this should be changed to mor=
e generally cover RFC5205. The DNS proxy technique is distinct from storing=
 HIP RR in a modified DNS server.

Section 2.3.2
s/leap of feath/leap of faith/
s/there is not/there is no/ ?

Section 2.3.2
May want to add a statement about OpenHIP and opportunistic mode:

The OpenHIP project experimented with opporunistic mode through the use of =
an
opportunistic (-o) option. For the responder, this option determines whethe=
r or not HIP accepts I1s received with a zeroed receiver's HIT. On the init=
iator's side, this option allows one to configure a name and LSI in the kno=
wn Host Identities file. When the HIT field is missing, an I1 is sent with =
a zeroed receiver's HIT. The LSI is needed by an IPv4 application to trigge=
r the association. Note that normally the LSI used is based on the bottom 2=
4 bits of the HIT, but in the case of opportunistic mode, the HIT is unknow=
n; thus the LSI may differ from the HIT.

Section 2.3.7
regarding the Boeing pilot project:
s/certificates are planned to be generated/certificates were generated/

also add reference to cert spec:

 Use of certificates in HIP requires extensions to
    the HIP specifications [ID.ietf-hip-cert].

(and freshen the reference to -09 revision)

Section 3.4
Seems there is an extra [RFC5204] reference in the first sentence.

Section 4.1
s/Another unexperimented way to transparently use HIP is/
 Another method for transparently using HIP, which has no implementation ex=
perience, is/

may want a reference here to draft-irtf-hiprg-proxies-01 here

Section 5.1
s/insert it to/insert it into/

Section 5.2
2nd paragraph regarding low-power devices cites a mobiarch paper but nowher=
e references DEX (Diet-Exchange) draft-moskowitz-hip-rg-dex-04

Section 5.3
may revise text with:
  Furthermore, legacy firewalls often disallow IPsec traffic and drop
  HIP control packets, if UDP encapsulation is not used.

s/reputation purposes/non-repudiation purposes/

Section 5.4
s/implemented HIP firewall/implemented a HIP-aware firewall/

may want reference to draft-heer-hip-middle-auth-02

Section 6
Nowhere mentions the use of anonymous HITs with regards to privacy issues.


From zehn.cao@gmail.com  Thu Mar 10 22:51:36 2011
Return-Path: <zehn.cao@gmail.com>
X-Original-To: hiprg@core3.amsl.com
Delivered-To: hiprg@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 9BEC73A68E4 for <hiprg@core3.amsl.com>; Thu, 10 Mar 2011 22:51:36 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.898
X-Spam-Level: 
X-Spam-Status: No, score=-3.898 tagged_above=-999 required=5 tests=[AWL=-0.299, BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-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 DYeIyxQpY9Yv for <hiprg@core3.amsl.com>; Thu, 10 Mar 2011 22:51:34 -0800 (PST)
Received: from mail-iy0-f182.google.com (mail-iy0-f182.google.com [209.85.210.182]) by core3.amsl.com (Postfix) with ESMTP id 36BEE3A687C for <hiprg@irtf.org>; Thu, 10 Mar 2011 22:51:34 -0800 (PST)
Received: by iyj12 with SMTP id 12so2813693iyj.13 for <hiprg@irtf.org>; Thu, 10 Mar 2011 22:52:53 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:in-reply-to:references:date :message-id:subject:from:to:content-type:content-transfer-encoding; bh=7PK6ES5d/VL7lplXItu8sbL0JGsf/6KArN89dSMmjvs=; b=tLQLOLG3SYHyB9Vg9J4dUvdxXiY4su5CpsuTWq0HmPQCOgRhjyMFvIT+4MXmipm1b1 FkhSdmN0oz29SzXIjMsAxBf2y+5ohoy5xeEfOcjWBlASFBPDwHWTKh8vuQJTJ2R3FSqc LFXUjrFC6qIrCZl+ThcAh4/fVHpsNmZ3S3VLg=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :content-type:content-transfer-encoding; b=tkwbBQUBUUe2j3StRWlOqtXoZci5OIxjipOeizEtVaDmY7TGKjmuuleUrxng695YFi IQM/5E8ilCZVWdS3jgCiyKcv9fSVopr8Zwa2ivhbTfYxaM5JESNQIQHOSoAWMe0vckcp 23qHOSNz41BeddPkInzu9xE5wK4kPCf2rp7U0=
MIME-Version: 1.0
Received: by 10.42.97.7 with SMTP id l7mr11105813icn.471.1299826373075; Thu, 10 Mar 2011 22:52:53 -0800 (PST)
Received: by 10.42.136.130 with HTTP; Thu, 10 Mar 2011 22:52:53 -0800 (PST)
In-Reply-To: <AANLkTin9MCT4saWS2Qo+zo1T4V39Fi_HsPbr=0MwJLgB@mail.gmail.com>
References: <20110307141502.11968.66765.idtracker@localhost> <AANLkTin9MCT4saWS2Qo+zo1T4V39Fi_HsPbr=0MwJLgB@mail.gmail.com>
Date: Fri, 11 Mar 2011 14:52:53 +0800
Message-ID: <AANLkTikA-hsjCSPiwXyAvo9UAdSEt10BQZ5si3emjVuv@mail.gmail.com>
From: Zhen Cao <zehn.cao@gmail.com>
To: hiprg@irtf.org
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable
Subject: Re: [hiprg] I-D Action:draft-cao-hiprg-flow-mobility-00.txt
X-BeenThere: hiprg@irtf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: "Host Identity Protocol \(HIP\) Research Group" <hiprg.irtf.org>
List-Unsubscribe: <https://www.irtf.org/mailman/listinfo/hiprg>, <mailto:hiprg-request@irtf.org?subject=unsubscribe>
List-Archive: <http://www.irtf.org/mail-archive/web/hiprg>
List-Post: <mailto:hiprg@irtf.org>
List-Help: <mailto:hiprg-request@irtf.org?subject=help>
List-Subscribe: <https://www.irtf.org/mailman/listinfo/hiprg>, <mailto:hiprg-request@irtf.org?subject=subscribe>
X-List-Received-Date: Fri, 11 Mar 2011 06:51:36 -0000

Hi All,

Please find the hip flow mobility draft, comments welcome.

If possible, I'd like to request a short slot to discuss the
requirement and scenario at the Prague meeting. Thank you.

Regards,
Zhen
> ---------- Forwarded message ----------
> From: =A0<Internet-Drafts@ietf.org>
> Date: Mon, Mar 7, 2011 at 10:15 PM
> Subject: I-D Action:draft-cao-hiprg-flow-mobility-00.txt
> To: i-d-announce@ietf.org
>
>
> A New Internet-Draft is available from the on-line Internet-Drafts direct=
ories.
>
> =A0 =A0 =A0 =A0Title =A0 =A0 =A0 =A0 =A0 : HIP Extension for Flow Mobilit=
y Management
> =A0 =A0 =A0 =A0Author(s) =A0 =A0 =A0 : Z. Cao, et al.
> =A0 =A0 =A0 =A0Filename =A0 =A0 =A0 =A0: draft-cao-hiprg-flow-mobility-00=
.txt
> =A0 =A0 =A0 =A0Pages =A0 =A0 =A0 =A0 =A0 : 11
> =A0 =A0 =A0 =A0Date =A0 =A0 =A0 =A0 =A0 =A0: 2011-03-07
>
> This document defines flow mobility extension to the Host Identity
> Protocol (HIP). =A0A multi-homed HIP host makes the binding of a flow
> and one or more locators, through the new parameter "E-LOCATOR",
> which is the extension of "LOCATOR" defined in RFC5206, the host can
> acknowledgement his peers with addresses available that fit for some
> traffic flow. =A0Peer hosts then selects the most appropriate address
> to transfer the traffic flow.
>
> A URL for this Internet-Draft is:
> http://www.ietf.org/internet-drafts/draft-cao-hiprg-flow-mobility-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.
>
>
> _______________________________________________
> I-D-Announce mailing list
> I-D-Announce@ietf.org
> https://www.ietf.org/mailman/listinfo/i-d-announce
> Internet-Draft directories: http://www.ietf.org/shadow.html
> or ftp://ftp.ietf.org/ietf/1shadow-sites.txt
>
>
>
>
> --
> Best regards,
> Zhen
>



--=20
Best regards,
Zhen

From fu@cs.uni-goettingen.de  Fri Mar 11 02:48:44 2011
Return-Path: <fu@cs.uni-goettingen.de>
X-Original-To: hiprg@core3.amsl.com
Delivered-To: hiprg@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 3256D3A689A for <hiprg@core3.amsl.com>; Fri, 11 Mar 2011 02:48:44 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.172
X-Spam-Level: 
X-Spam-Status: No, score=-0.172 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HELO_EQ_DE=0.35, SUBJ_ALL_CAPS=2.077]
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 GTOObFWxLELa for <hiprg@core3.amsl.com>; Fri, 11 Mar 2011 02:48:42 -0800 (PST)
Received: from amailer.gwdg.de (amailer.gwdg.de [134.76.10.18]) by core3.amsl.com (Postfix) with ESMTP id 765F63A6893 for <hiprg@irtf.org>; Fri, 11 Mar 2011 02:48:41 -0800 (PST)
Received: from s5.ifi.informatik.uni-goettingen.de ([134.76.81.25] helo=[172.23.0.20]) by mailer.gwdg.de with esmtpsa (TLSv1:AES256-SHA:256) (Exim 4.72) (envelope-from <fu@cs.uni-goettingen.de>) id 1Pxzux-0006Iv-Nz for hiprg@irtf.org; Fri, 11 Mar 2011 11:49:59 +0100
Message-ID: <4D79FEA3.4030104@cs.uni-goettingen.de>
Date: Fri, 11 Mar 2011 11:51:15 +0100
From: Xiaoming Fu <fu@cs.uni-goettingen.de>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.1; en-US; rv:1.9.2.15) Gecko/20110303 Thunderbird/3.1.9
MIME-Version: 1.0
To: hiprg@irtf.org
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-Authenticated: Id:xfu
X-Virus-Scanned: (clean) by exiscan+sophie
Subject: [hiprg] CFP: IEEE ICNP 2011
X-BeenThere: hiprg@irtf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: "Host Identity Protocol \(HIP\) Research Group" <hiprg.irtf.org>
List-Unsubscribe: <https://www.irtf.org/mailman/listinfo/hiprg>, <mailto:hiprg-request@irtf.org?subject=unsubscribe>
List-Archive: <http://www.irtf.org/mail-archive/web/hiprg>
List-Post: <mailto:hiprg@irtf.org>
List-Help: <mailto:hiprg-request@irtf.org?subject=help>
List-Subscribe: <https://www.irtf.org/mailman/listinfo/hiprg>, <mailto:hiprg-request@irtf.org?subject=subscribe>
X-List-Received-Date: Fri, 11 Mar 2011 10:48:44 -0000

We apologize if you receive multiple copies of this message.

===================================================================
19th IEEE International Conference on Network Protocols (ICNP 2011)
Vancouver, BC Canada, October 17-20, 2011
http://www.cs.utah.edu/~mprobst/ICNP2011/
===================================================================


IMPORTANT DATES:
Title/Abstract submission:	April 15, 2011 11:59 PM PDT
Full paper submission:	        April 22, 2011 11:59 PM PDT
Notification of acceptance:	July 28, 2011
Camera ready version:	        August 26, 2011 11:59 PM PDT
The advance (discounted) registration deadline:	TBD
Conference:	                October 17-20, 2011

CALL FOR PAPERS:
http://www.cs.utah.edu/~mprobst/ICNP2011/ICNP-2011-CFP.pdf

ICNP, the IEEE International Conference on Network Protocols, is the 
premier conference covering all aspects of network protocols, including 
design, analysis, specification, verification, implementation, and 
performance. ICNP 2011, the 19th ICNP, sponsored by IEEE and IEEE 
Computer Society Technical Committee on Distributed Processing, will be 
held in Vancouver, Canada, October 17-20, 2011. Papers with significant 
research contributions to the held of network protocols are solicited 
for submission. Papers cannot be previously published nor under review 
by another conference or journal. Papers containing plagiarized material 
will be subject to the IEEE plagiarism policy and will be rejected 
without review.

Topics of interest include, but are not limited to:

* Protocol design, implementation, testing, and analysis
* Measurement of protocol performance
* Protocols for specific functions, such as routing, congestion control, 
security, survivability, and network management
* Protocols for wireless, mobile, sensor, mesh networks, cognitive 
communication, and white spaces.
* Protocols for cloud computing, peer-to-peer systems, emerging 
distributed systems, and disruption tolerant networks.

Papers must deal specifically with protocols. Papers on general 
networking where protocols are only a secondary focus will be considered 
only if they are of exceptional quality. ICNP will select an accepted 
full paper for the best paper award.

ICNP 2011 will use a double-blind review process. The identity of 
authors and referees will not be revealed to each other. To ensure blind 
reviewing, author names and affiliations should not appear in the paper; 
bibliographic references should be made in such a way as to preserve 
author anonymity. Papers should adhere to the IEEE Computer conference 
paper format (IEEEtran.cls) and should not exceed 10 pages. The font 
size should be no smaller than 10 pt. At lease one author of an accepted 
paper is expected to register for the conference and to present the 
paper at the conference, in order for the paper to appear in the 
conference proceedings and the IEEE digital library.


ORGANIZING COMMITTEE

General Chairs:
Funda Ergun, Simon Fraser University, Canada
Thomas La Porta, Penn State University, USA

Program Chairs:
Sneha Kasera, University of Utah, USA
Baochun Li, University of Toronto, Canada

Advisory Board:
Simon Lam, University of Texas at Austin, USA
Mike T. Liu, Ohio State University, USA
Raymond Miller, University of Maryland, USA

Steering Committee:
Ken Calvert, University of Kentucky, USA (Chair)
Kevin Almeroth, UC Santa Barbara, USA
Sonia Fahmy, Purdue University, USA
Mohamed Gouda, University of Texas, USA
Teruo Higashino, Osaka University, Japan
David Lee, Ohio State University, USA
K. K. Ramakrishnan, AT&T Labs Research, USA
Krishan Sabnani, Bell Labs, USA



Besides the main conference, ICNP 2011 will include workshops, posters 
and a PhD forum as well. Further details will be given in a later date.

Best regards,
Xiaoming Fu

From thomas.r.henderson@boeing.com  Fri Mar 11 14:20:52 2011
Return-Path: <thomas.r.henderson@boeing.com>
X-Original-To: hiprg@core3.amsl.com
Delivered-To: hiprg@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 251043A69F3 for <hiprg@core3.amsl.com>; Fri, 11 Mar 2011 14:20:52 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -106.555
X-Spam-Level: 
X-Spam-Status: No, score=-106.555 tagged_above=-999 required=5 tests=[AWL=0.044, BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4, USER_IN_WHITELIST=-100]
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 eqrQ0GBajteZ for <hiprg@core3.amsl.com>; Fri, 11 Mar 2011 14:20:51 -0800 (PST)
Received: from stl-smtpout-01.boeing.com (stl-smtpout-01.boeing.com [130.76.96.56]) by core3.amsl.com (Postfix) with ESMTP id 1F6103A6814 for <hiprg@irtf.org>; Fri, 11 Mar 2011 14:20:51 -0800 (PST)
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 p2BMM8TH007424 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=FAIL); Fri, 11 Mar 2011 16:22:08 -0600 (CST)
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 p2BMM78I013253; Fri, 11 Mar 2011 16:22:08 -0600 (CST)
Received: from XCH-NWHT-04.nw.nos.boeing.com (xch-nwht-04.nw.nos.boeing.com [130.247.64.250]) by stl-av-01.boeing.com (8.14.4/8.14.4/UPSTREAM_RELAY) with ESMTP id p2BMM772013216 (version=TLSv1/SSLv3 cipher=RC4-MD5 bits=128 verify=OK); Fri, 11 Mar 2011 16:22:07 -0600 (CST)
Received: from XCH-NW-10V.nw.nos.boeing.com ([130.247.25.85]) by XCH-NWHT-04.nw.nos.boeing.com ([130.247.64.250]) with mapi; Fri, 11 Mar 2011 14:22:06 -0800
From: "Henderson, Thomas R" <thomas.r.henderson@boeing.com>
To: "'Zhen Cao'" <zehn.cao@gmail.com>, "hiprg@irtf.org" <hiprg@irtf.org>
Date: Fri, 11 Mar 2011 14:22:05 -0800
Thread-Topic: [hiprg] I-D Action:draft-cao-hiprg-flow-mobility-00.txt
Thread-Index: AcvfuPXB4xGRgPcVTT20nS5UQvyJjQAgbocA
Message-ID: <7CC566635CFE364D87DC5803D4712A6C4CED25AFBC@XCH-NW-10V.nw.nos.boeing.com>
References: <20110307141502.11968.66765.idtracker@localhost><AANLkTin9MCT4saWS2Qo+zo1T4V39Fi_HsPbr=0MwJLgB@mail.gmail.com> <AANLkTikA-hsjCSPiwXyAvo9UAdSEt10BQZ5si3emjVuv@mail.gmail.com>
In-Reply-To: <AANLkTikA-hsjCSPiwXyAvo9UAdSEt10BQZ5si3emjVuv@mail.gmail.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: Re: [hiprg] I-D Action:draft-cao-hiprg-flow-mobility-00.txt
X-BeenThere: hiprg@irtf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: "Host Identity Protocol \(HIP\) Research Group" <hiprg.irtf.org>
List-Unsubscribe: <https://www.irtf.org/mailman/listinfo/hiprg>, <mailto:hiprg-request@irtf.org?subject=unsubscribe>
List-Archive: <http://www.irtf.org/mail-archive/web/hiprg>
List-Post: <mailto:hiprg@irtf.org>
List-Help: <mailto:hiprg-request@irtf.org?subject=help>
List-Subscribe: <https://www.irtf.org/mailman/listinfo/hiprg>, <mailto:hiprg-request@irtf.org?subject=subscribe>
X-List-Received-Date: Fri, 11 Mar 2011 22:20:52 -0000

> -----Original Message-----
> From: hiprg-bounces@irtf.org [mailto:hiprg-bounces@irtf.org] On Behalf
> Of Zhen Cao
> Sent: Thursday, March 10, 2011 10:53 PM
> To: hiprg@irtf.org
> Subject: Re: [hiprg] I-D Action:draft-cao-hiprg-flow-mobility-00.txt
>=20
> Hi All,
>=20
> Please find the hip flow mobility draft, comments welcome.
>=20
> If possible, I'd like to request a short slot to discuss the
> requirement and scenario at the Prague meeting. Thank you.
>=20
> Regards,
> Zhen

I will add you to the agenda.

Thanks,
Tom

From zhangdacheng@huawei.com  Sun Mar 13 18:47:41 2011
Return-Path: <zhangdacheng@huawei.com>
X-Original-To: hiprg@core3.amsl.com
Delivered-To: hiprg@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 3FFB93A6AB9 for <hiprg@core3.amsl.com>; Sun, 13 Mar 2011 18:47:41 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.438
X-Spam-Level: 
X-Spam-Status: No, score=-1.438 tagged_above=-999 required=5 tests=[AWL=-0.943, 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 XrxR6CaoYgxW for <hiprg@core3.amsl.com>; Sun, 13 Mar 2011 18:47:40 -0700 (PDT)
Received: from szxga01-in.huawei.com (unknown [119.145.14.64]) by core3.amsl.com (Postfix) with ESMTP id 7CC103A6AAC for <hiprg@irtf.org>; Sun, 13 Mar 2011 18:47:40 -0700 (PDT)
Received: from huawei.com (szxga05-in [172.24.2.49]) by szxga05-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 2.14 (built Aug 8 2006)) with ESMTP id <0LI000BBIYB4JT@szxga05-in.huawei.com> for hiprg@irtf.org; Mon, 14 Mar 2011 09:47:28 +0800 (CST)
Received: from huawei.com ([172.24.2.119]) by szxga05-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 2.14 (built Aug 8 2006)) with ESMTP id <0LI000I0QYB35Y@szxga05-in.huawei.com> for hiprg@irtf.org; Mon, 14 Mar 2011 09:47:28 +0800 (CST)
Received: from z00133208z ([10.110.98.43]) by szxml04-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 2.14 (built Aug 8 2006)) with ESMTPA id <0LI000482YATON@szxml04-in.huawei.com> for hiprg@irtf.org; Mon, 14 Mar 2011 09:47:27 +0800 (CST)
Date: Mon, 14 Mar 2011 09:47:17 +0800
From: Dacheng Zhang <zhangdacheng@huawei.com>
In-reply-to: <4D79FEA3.4030104@cs.uni-goettingen.de>
To: hiprg@irtf.org
Message-id: <001001cbe1e9$c0123780$4036a680$@com>
MIME-version: 1.0
X-Mailer: Microsoft Office Outlook 12.0
Content-type: text/plain; charset=us-ascii
Content-language: zh-cn
Content-transfer-encoding: 7BIT
Thread-index: Acvf2iu/zeg0VZF5QW2/QJDrDWZ8kgCDrDAA
References: <4D79FEA3.4030104@cs.uni-goettingen.de>
Subject: [hiprg] update of the HIP proxy and HI revocation drafts
X-BeenThere: hiprg@irtf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: "Host Identity Protocol \(HIP\) Research Group" <hiprg.irtf.org>
List-Unsubscribe: <https://www.irtf.org/mailman/listinfo/hiprg>, <mailto:hiprg-request@irtf.org?subject=unsubscribe>
List-Archive: <http://www.irtf.org/mail-archive/web/hiprg>
List-Post: <mailto:hiprg@irtf.org>
List-Help: <mailto:hiprg-request@irtf.org?subject=help>
List-Subscribe: <https://www.irtf.org/mailman/listinfo/hiprg>, <mailto:hiprg-request@irtf.org?subject=subscribe>
X-List-Received-Date: Mon, 14 Mar 2011 01:47:41 -0000

Hi, 

Follows are the links of the latest updates of the draft-irtf-hiprg-proxies
and draft-irtf-hiprg-revocation.
http://tools.ietf.org/html/draft-irtf-hiprg-proxies-02
https://tools.ietf.org/html/draft-irtf-hiprg-revocation-02

Any advice will be very appreciated.

Cheers

Dacheng



From Pascal.Urien@gmail.com  Mon Mar 14 00:27:07 2011
Return-Path: <Pascal.Urien@gmail.com>
X-Original-To: hiprg@core3.amsl.com
Delivered-To: hiprg@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 807503A6B0E for <hiprg@core3.amsl.com>; Mon, 14 Mar 2011 00:27:07 -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.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id pQaJbO2-briK for <hiprg@core3.amsl.com>; Mon, 14 Mar 2011 00:27:06 -0700 (PDT)
Received: from mail-ww0-f72.google.com (mail-ww0-f72.google.com [74.125.82.72]) by core3.amsl.com (Postfix) with ESMTP id 1FC0D3A6B07 for <hiprg@irtf.org>; Mon, 14 Mar 2011 00:27:05 -0700 (PDT)
Received: by wwi14 with SMTP id 14so276172wwi.7 for <hiprg@irtf.org>; Mon, 14 Mar 2011 00:28:28 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.227.7.80 with SMTP id c16mr655711wbc.19.1300087708587; Mon, 14 Mar 2011 00:28:28 -0700 (PDT)
In-Reply-To: <7CC566635CFE364D87DC5803D4712A6C4CED25AFBC@XCH-NW-10V.nw.nos.boeing.com>
Message-ID: <002215975dfe0c1931049e6c4203@google.com>
Date: Mon, 14 Mar 2011 07:28:28 +0000
From: Pascal.Urien@gmail.com
To: "Henderson, Thomas R" <thomas.r.henderson@boeing.com>, "hiprg@irtf.org" <hiprg@irtf.org>
Content-Type: multipart/alternative; boundary=002215975dfe0c1910049e6c4200
Cc: updated@core3.amsl.com, HIP-RFID@core3.amsl.com, draft@core3.amsl.com
Subject: [hiprg] draft-irtf-hiprg-rfid-02
X-BeenThere: hiprg@irtf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: "Host Identity Protocol \(HIP\) Research Group" <hiprg.irtf.org>
List-Unsubscribe: <https://www.irtf.org/mailman/listinfo/hiprg>, <mailto:hiprg-request@irtf.org?subject=unsubscribe>
List-Archive: <http://www.irtf.org/mail-archive/web/hiprg>
List-Post: <mailto:hiprg@irtf.org>
List-Help: <mailto:hiprg-request@irtf.org?subject=help>
List-Subscribe: <https://www.irtf.org/mailman/listinfo/hiprg>, <mailto:hiprg-request@irtf.org?subject=subscribe>
X-List-Received-Date: Mon, 14 Mar 2011 07:27:07 -0000

--002215975dfe0c1910049e6c4200
Content-Type: text/plain; charset=ISO-8859-1; format=flowed; delsp=yes

Hi Thomas,

An updated version the HIP-RFID draft is available (  
http://tools.ietf.org/html/draft-irtf-hiprg-rfid-02 )

What is new is an annex with javacard code for NFC RFIDs, some typos have  
been corrected

I have updated a web page that contains all the java stuff needed fo  
experiments ( http://perso.telecom-paristech.fr/~urien/hiprfid/index.html )

Due to a lack of funding i could not attend to the next IETF meeting...

Best Regards

Pascal

--002215975dfe0c1910049e6c4200
Content-Type: text/html; charset=ISO-8859-1

Hi Thomas,
<br />
<br /> An updated version the HIP-RFID draft is available ( http://tools.ietf.org/html/draft-irtf-hiprg-rfid-02 )
<br />
<br /> What is new is an annex with javacard code for NFC RFIDs, some typos have been corrected
<br />
<br /> I have updated a web page that contains all the java stuff needed fo experiments ( http://perso.telecom-paristech.fr/~urien/hiprfid/index.html )
<br />
<br /> Due to a lack of funding i could not attend to the next IETF meeting...
<br />
<br />Best Regards
<br />
<br />Pascal
--002215975dfe0c1910049e6c4200--

From rgm@htt-consult.com  Mon Mar 14 13:45:14 2011
Return-Path: <rgm@htt-consult.com>
X-Original-To: hiprg@core3.amsl.com
Delivered-To: hiprg@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 67B4A3A6F39 for <hiprg@core3.amsl.com>; Mon, 14 Mar 2011 13:45:14 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.537
X-Spam-Level: 
X-Spam-Status: No, score=-2.537 tagged_above=-999 required=5 tests=[AWL=0.062,  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 hHYLEYM9YVxh for <hiprg@core3.amsl.com>; Mon, 14 Mar 2011 13:45:13 -0700 (PDT)
Received: from klovia.htt-consult.com (klovia.htt-consult.com [208.83.67.149]) by core3.amsl.com (Postfix) with ESMTP id 45B083A6F23 for <hiprg@irtf.org>; Mon, 14 Mar 2011 13:45:13 -0700 (PDT)
Received: from localhost (unknown [127.0.0.1]) by klovia.htt-consult.com (Postfix) with ESMTP id 1414962A9F for <hiprg@irtf.org>; Mon, 14 Mar 2011 20:46:16 +0000 (UTC)
X-Virus-Scanned: amavisd-new at localhost
Received: from klovia.htt-consult.com ([127.0.0.1]) by localhost (klovia.htt-consult.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id uJdX+yy3cqWG for <hiprg@irtf.org>; Mon, 14 Mar 2011 16:45:56 -0400 (EDT)
Received: from nc2400.htt-consult.com (nc2400.htt-consult.com [208.83.67.155]) (Authenticated sender: rgm@htt-consult.com) by klovia.htt-consult.com (Postfix) with ESMTPSA id 4ABED62A96 for <hiprg@irtf.org>; Mon, 14 Mar 2011 16:45:56 -0400 (EDT)
Message-ID: <4D7E7E83.8090703@htt-consult.com>
Date: Mon, 14 Mar 2011 16:45:55 -0400
From: Robert Moskowitz <rgm@htt-consult.com>
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.9.2.13) Gecko/20101209 Fedora/3.1.7-0.35.b3pre.fc14 Thunderbird/3.1.7
MIME-Version: 1.0
To: hiprg@irtf.org
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Subject: [hiprg] Fwd: New Version Notification for draft-moskowitz-hip-rg-dex-05
X-BeenThere: hiprg@irtf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: "Host Identity Protocol \(HIP\) Research Group" <hiprg.irtf.org>
List-Unsubscribe: <https://www.irtf.org/mailman/listinfo/hiprg>, <mailto:hiprg-request@irtf.org?subject=unsubscribe>
List-Archive: <http://www.irtf.org/mail-archive/web/hiprg>
List-Post: <mailto:hiprg@irtf.org>
List-Help: <mailto:hiprg-request@irtf.org?subject=help>
List-Subscribe: <https://www.irtf.org/mailman/listinfo/hiprg>, <mailto:hiprg-request@irtf.org?subject=subscribe>
X-List-Received-Date: Mon, 14 Mar 2011 20:45:14 -0000

This is what I put together to make today's cutoff.

I still have not completely reconciled HIP DEX with HIP BEX, that is 
edits have been made to text in BEX that is duplicatted in DEX and I 
have not completed the cutting and pasting.  So I will have one last 
update that will be on my personal server before the meeting.  However 
there will probably NOT be any meaty changes before the meeting unless 
someone comes to me with some good comments (and yes, Miika, I am still 
working through your notes).


-----Original Message-----
From: IETF I-D Submission Tool [mailto:idsubmission@ietf.org]
Sent: Monday, March 14, 2011 4:35 PM
To: robert.moskowitz@icsalabs.com
Subject: New Version Notification for draft-moskowitz-hip-rg-dex-05


A new version of I-D, draft-moskowitz-hip-rg-dex-05.txt has been
successfully submitted by Robert Moskowitz and posted to the IETF
repository.

Filename:	 draft-moskowitz-hip-rg-dex
Revision:	 05
Title:		 HIP Diet EXchange (DEX)
Creation_date:	 2011-03-14
WG ID:		 Independent Submission
Number_of_pages: 35

Abstract:
This document specifies the details of the Host Identity Protocol
Diet EXchange (HIP DEX).  HIP DEX is a variant of the HIP Base
EXchange (HIP BEX) [RFC5201-bis] specifically designed to use as few
crypto primitives as possible yet still deliver the same class of
security features as HIP BEX.

The design goal of HIP DEX is to be usable by sensor devices that are
memory and processor constrained.  Like HIP BEX it is expected to be
used together with another suitable security protocol, such as the
Encapsulated Security Payload (ESP).  HIP DEX can also be used
directly as a keying mechanism for a MAC layer security protocol as
is supported by IEEE 802.15.4 [IEEE.802-15-4.2006].




The IETF Secretariat.





From thomas.r.henderson@boeing.com  Wed Mar 16 15:59:34 2011
Return-Path: <thomas.r.henderson@boeing.com>
X-Original-To: hiprg@core3.amsl.com
Delivered-To: hiprg@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 7CA2B3A69DC for <hiprg@core3.amsl.com>; Wed, 16 Mar 2011 15:59:34 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -106.563
X-Spam-Level: 
X-Spam-Status: No, score=-106.563 tagged_above=-999 required=5 tests=[AWL=0.036, BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4, USER_IN_WHITELIST=-100]
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 8ozCgBVQx04l for <hiprg@core3.amsl.com>; Wed, 16 Mar 2011 15:59:33 -0700 (PDT)
Received: from slb-smtpout-01.boeing.com (slb-smtpout-01.boeing.com [130.76.64.48]) by core3.amsl.com (Postfix) with ESMTP id C96113A6974 for <hiprg@irtf.org>; Wed, 16 Mar 2011 15:59:33 -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 p2GN0oAF019264 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=FAIL) for <hiprg@irtf.org>; Wed, 16 Mar 2011 16:00:51 -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 p2GN0noK002061 for <hiprg@irtf.org>; Wed, 16 Mar 2011 18:00:49 -0500 (CDT)
Received: from XCH-NWHT-09.nw.nos.boeing.com (xch-nwht-09.nw.nos.boeing.com [130.247.25.115]) by stl-av-01.boeing.com (8.14.4/8.14.4/UPSTREAM_RELAY) with ESMTP id p2GMxtrC029314 (version=TLSv1/SSLv3 cipher=RC4-MD5 bits=128 verify=OK) for <hiprg@irtf.org>; Wed, 16 Mar 2011 18:00:47 -0500 (CDT)
Received: from XCH-NW-10V.nw.nos.boeing.com ([130.247.25.85]) by XCH-NWHT-09.nw.nos.boeing.com ([130.247.25.115]) with mapi; Wed, 16 Mar 2011 16:00:36 -0700
From: "Henderson, Thomas R" <thomas.r.henderson@boeing.com>
To: "hiprg@irtf.org" <hiprg@irtf.org>
Date: Wed, 16 Mar 2011 16:00:36 -0700
Thread-Topic: IETF 80 HIPRG preliminary agenda
Thread-Index: AcvkLfaUz3GwCXQWTlivVsjV/QBcGA==
Message-ID: <7CC566635CFE364D87DC5803D4712A6C4CED25B004@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] IETF 80 HIPRG preliminary agenda
X-BeenThere: hiprg@irtf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: "Host Identity Protocol \(HIP\) Research Group" <hiprg.irtf.org>
List-Unsubscribe: <https://www.irtf.org/mailman/listinfo/hiprg>, <mailto:hiprg-request@irtf.org?subject=unsubscribe>
List-Archive: <http://www.irtf.org/mail-archive/web/hiprg>
List-Post: <mailto:hiprg@irtf.org>
List-Help: <mailto:hiprg-request@irtf.org?subject=help>
List-Subscribe: <https://www.irtf.org/mailman/listinfo/hiprg>, <mailto:hiprg-request@irtf.org?subject=subscribe>
X-List-Received-Date: Wed, 16 Mar 2011 22:59:34 -0000

Hi all, I've posted a preliminary agenda for the HIPRG meeting here:
http://www.ietf.org/proceedings/80/agenda/HIPRG.txt

I would like to spend the first part of the meeting to discuss our research=
 group drafts and to try to close out issues, and I'd like to encourage som=
e review and discussion on the list between now and then if people can read=
 the drafts and comment (all were recently updated).

Please let me know of any additional slot requests for presentations.

- Tom

From thomas.r.henderson@boeing.com  Mon Mar 28 04:33:22 2011
Return-Path: <thomas.r.henderson@boeing.com>
X-Original-To: hiprg@core3.amsl.com
Delivered-To: hiprg@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id BA2253A67DF for <hiprg@core3.amsl.com>; Mon, 28 Mar 2011 04:33:22 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -106.568
X-Spam-Level: 
X-Spam-Status: No, score=-106.568 tagged_above=-999 required=5 tests=[AWL=0.031, BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4, USER_IN_WHITELIST=-100]
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 imo9nSA8NuDd for <hiprg@core3.amsl.com>; Mon, 28 Mar 2011 04:33:21 -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 B5AE43A6805 for <hiprg@irtf.org>; Mon, 28 Mar 2011 04:33:21 -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.4/8.14.4/8.14.4/SMTPOUT) with ESMTP id p2SBYwuk005151 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=FAIL) for <hiprg@irtf.org>; Mon, 28 Mar 2011 06:34:58 -0500 (CDT)
Received: from blv-av-01.boeing.com (localhost [127.0.0.1]) by blv-av-01.boeing.com (8.14.4/8.14.4/DOWNSTREAM_RELAY) with ESMTP id p2SBYvqw027217 for <hiprg@irtf.org>; Mon, 28 Mar 2011 04:34:57 -0700 (PDT)
Received: from XCH-NWHT-08.nw.nos.boeing.com (xch-nwht-08.nw.nos.boeing.com [130.247.25.112]) by blv-av-01.boeing.com (8.14.4/8.14.4/UPSTREAM_RELAY) with ESMTP id p2SBYvf4027214 (version=TLSv1/SSLv3 cipher=RC4-MD5 bits=128 verify=OK) for <hiprg@irtf.org>; Mon, 28 Mar 2011 04:34:57 -0700 (PDT)
Received: from XCH-NW-10V.nw.nos.boeing.com ([130.247.25.85]) by XCH-NWHT-08.nw.nos.boeing.com ([130.247.25.112]) with mapi; Mon, 28 Mar 2011 04:34:57 -0700
From: "Henderson, Thomas R" <thomas.r.henderson@boeing.com>
To: "hiprg@irtf.org" <hiprg@irtf.org>
Date: Mon, 28 Mar 2011 04:34:56 -0700
Thread-Topic: RG meeting reminder
Thread-Index: AcvtPCkZVosC0b2IT7CDj0iDPEv1tg==
Message-ID: <7CC566635CFE364D87DC5803D4712A6C4CED25B06F@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] RG meeting reminder
X-BeenThere: hiprg@irtf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: "Host Identity Protocol \(HIP\) Research Group" <hiprg.irtf.org>
List-Unsubscribe: <https://www.irtf.org/mailman/listinfo/hiprg>, <mailto:hiprg-request@irtf.org?subject=unsubscribe>
List-Archive: <http://www.irtf.org/mail-archive/web/hiprg>
List-Post: <mailto:hiprg@irtf.org>
List-Help: <mailto:hiprg-request@irtf.org?subject=help>
List-Subscribe: <https://www.irtf.org/mailman/listinfo/hiprg>, <mailto:hiprg-request@irtf.org?subject=subscribe>
X-List-Received-Date: Mon, 28 Mar 2011 11:33:22 -0000

This is a reminder that we will be meeting Tuesday at 13h00 in Karlin 1 roo=
m.  The agenda is posted here:
http://www.ietf.org/proceedings/80/agenda/HIPRG.txt

Presenters, if you could please provide me with your slides in advance of t=
he meeting, I will upload them to the meeting materials site.

I would also like to request that presenters identify what actions they wou=
ld like to see taken by the RG, or what are the remaining open issues from =
their perspective, so we can focus the discussion there.

I will send out some separate mail regarding our active RG drafts suggestin=
g some items that we could hope to discuss and resolve at the meeting.

- Tom

From thomas.r.henderson@boeing.com  Mon Mar 28 05:41:40 2011
Return-Path: <thomas.r.henderson@boeing.com>
X-Original-To: hiprg@core3.amsl.com
Delivered-To: hiprg@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 64DBF3A68F0 for <hiprg@core3.amsl.com>; Mon, 28 Mar 2011 05:41:40 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -105.871
X-Spam-Level: 
X-Spam-Status: No, score=-105.871 tagged_above=-999 required=5 tests=[AWL=-0.671, BAYES_00=-2.599, J_CHICKENPOX_13=0.6, RCVD_IN_DNSWL_MED=-4, SARE_SUB_RAND_LETTRS4=0.799, USER_IN_WHITELIST=-100]
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 eG76wZR0p8kn for <hiprg@core3.amsl.com>; Mon, 28 Mar 2011 05:41:39 -0700 (PDT)
Received: from blv-smtpout-01.boeing.com (blv-smtpout-01.boeing.com [130.76.32.69]) by core3.amsl.com (Postfix) with ESMTP id 038D03A6817 for <hiprg@irtf.org>; Mon, 28 Mar 2011 05:41:38 -0700 (PDT)
Received: from blv-av-01.boeing.com (blv-av-01.boeing.com [130.247.48.231]) by blv-smtpout-01.ns.cs.boeing.com (8.14.4/8.14.4/8.14.4/SMTPOUT) with ESMTP id p2SCgu0A011845 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=FAIL); Mon, 28 Mar 2011 05:43:01 -0700 (PDT)
Received: from blv-av-01.boeing.com (localhost [127.0.0.1]) by blv-av-01.boeing.com (8.14.4/8.14.4/DOWNSTREAM_RELAY) with ESMTP id p2SCgukX024146; Mon, 28 Mar 2011 05:42:56 -0700 (PDT)
Received: from XCH-NWHT-04.nw.nos.boeing.com (xch-nwht-04.nw.nos.boeing.com [130.247.64.250]) by blv-av-01.boeing.com (8.14.4/8.14.4/UPSTREAM_RELAY) with ESMTP id p2SCguUX024142 (version=TLSv1/SSLv3 cipher=RC4-MD5 bits=128 verify=OK); Mon, 28 Mar 2011 05:42:56 -0700 (PDT)
Received: from XCH-NW-10V.nw.nos.boeing.com ([130.247.25.85]) by XCH-NWHT-04.nw.nos.boeing.com ([130.247.64.250]) with mapi; Mon, 28 Mar 2011 05:42:56 -0700
From: "Henderson, Thomas R" <thomas.r.henderson@boeing.com>
To: "'Pascal.Urien@telecom-paristech.fr'" <Pascal.Urien@telecom-paristech.fr>,  "'Gyu Myoung Lee'" <gmlee@kaist.ac.kr>, "'Guy.Pujolle@lip6.fr'" <Guy.Pujolle@lip6.fr>
Date: Mon, 28 Mar 2011 05:42:55 -0700
Thread-Topic: some questions for draft-irtf-hiprg-rfid-02
Thread-Index: AcvtRafIhQRlE9/CT2KeNBqylceWUw==
Message-ID: <7CC566635CFE364D87DC5803D4712A6C4CED25B070@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
Cc: "hiprg@irtf.org" <hiprg@irtf.org>
Subject: [hiprg] some questions for draft-irtf-hiprg-rfid-02
X-BeenThere: hiprg@irtf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: "Host Identity Protocol \(HIP\) Research Group" <hiprg.irtf.org>
List-Unsubscribe: <https://www.irtf.org/mailman/listinfo/hiprg>, <mailto:hiprg-request@irtf.org?subject=unsubscribe>
List-Archive: <http://www.irtf.org/mail-archive/web/hiprg>
List-Post: <mailto:hiprg@irtf.org>
List-Help: <mailto:hiprg-request@irtf.org?subject=help>
List-Subscribe: <https://www.irtf.org/mailman/listinfo/hiprg>, <mailto:hiprg-request@irtf.org?subject=subscribe>
X-List-Received-Date: Mon, 28 Mar 2011 12:41:40 -0000

Pascal, Guy, and Guy,
I had a few questions and comments regarding the most recent draft on HIP s=
upport for RFID that we could perhaps try to discuss at the meeting tomorro=
w (or on the list in the meantime).

As background, it seems that the main goal of this protocol is to avoid dis=
closing the EPC to unauthorized readers; the RFID can disclose it to those =
portals that hold a shared secret with the RFID. =20

In the current draft, there seems to me that there is no need to include ho=
st identifier fields in this protocol.  The draft states that the HIT-I is =
a random number and the HIT-R could be a null value.  All of the identifica=
tion seems to be done on the basis of the f value passed in the exchange, w=
hich contains enough information to find the EPC.  Could you explain how HI=
Ts are used, if at all? =20

On a related note, the last sentence in Section 1 mentions that it is simil=
ar to the BLIND in the case that only one HIT is blinded.  I am wondering w=
hether that case applies here-- the initiator host identifier needs to be b=
linded, but the responder HIT doesn't really matter.  This left me wonderin=
g whether the protocol could be refactored as a variant of BLIND, in which =
case the EPC could be somehow embedded in the HIT-I and recoverable based o=
n the shared secret and nonce exchange.  For example, make the HIT-I some r=
eversible function f(key,EPC).  That would restore the use of HITs in the p=
rotocol.

It wasn't clear to me how ESP would work, how are the keys derived for it? =
 The existing keys in the draft seem to be directly drawn from functions su=
ch as g(r1,r2, EPC) but there seems to be no analogy to the DH keymat deriv=
ation process in HIP.  Could you clarify what are the requirements in your =
framework for a general key derivation function?

Another major section missing in this document is the Security Consideratio=
ns section, which will need to be carefully written to state the security c=
laims and known vulnerabilities of this protocol.

- Tom=20



From pascal.urien@gmail.com  Mon Mar 28 06:08:29 2011
Return-Path: <pascal.urien@gmail.com>
X-Original-To: hiprg@core3.amsl.com
Delivered-To: hiprg@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id ACB0E3A6803 for <hiprg@core3.amsl.com>; Mon, 28 Mar 2011 06:08:29 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.199
X-Spam-Level: 
X-Spam-Status: No, score=-2.199 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HTML_MESSAGE=0.001, J_CHICKENPOX_13=0.6, RCVD_IN_DNSWL_LOW=-1, SARE_SUB_RAND_LETTRS4=0.799]
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 dTJaADoLHag3 for <hiprg@core3.amsl.com>; Mon, 28 Mar 2011 06:08:28 -0700 (PDT)
Received: from mail-qy0-f175.google.com (mail-qy0-f175.google.com [209.85.216.175]) by core3.amsl.com (Postfix) with ESMTP id 661D33A67DA for <hiprg@irtf.org>; Mon, 28 Mar 2011 06:08:28 -0700 (PDT)
Received: by qyk35 with SMTP id 35so1156549qyk.13 for <hiprg@irtf.org>; Mon, 28 Mar 2011 06:10:05 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:in-reply-to:references:date :message-id:subject:from:to:cc:content-type; bh=SA77twk4Jq8DJnsiVQpI3IxQkyVNkLrEkG7oweb+R60=; b=XIf+QBqrFzK49NUUINY2C/hvWJcMif6jBmVVJXy+Q3oms6KyQtmoXZpTIebYP6Lstw tmH51MMYjiXMjhYfISiCMZd8gYq4FHR2aNsCDXfL1nAWpndOGRqX3hniCgEXQthBxiRX M/MnUVZFZ0DNS2zNvyrobunzQfVzqdWaR4wqc=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; b=W3vp7R2jhIPKhEdcyQJ7iVIeHzD0dfBh4EcCa6nUyX5R4/6UPHqMWHfDG8ueiL8aiS 1Gl79G91lLVGveQQkhMsj/v2cReou1n/zTesVch2orspeq6dzHmwm+U12NkNU356GGM2 MwuasWb5uHCkv6lNiy9N8zLYGq03TFPcdasac=
MIME-Version: 1.0
Received: by 10.229.19.12 with SMTP id y12mr3246379qca.267.1301317805300; Mon, 28 Mar 2011 06:10:05 -0700 (PDT)
Received: by 10.229.97.212 with HTTP; Mon, 28 Mar 2011 06:10:05 -0700 (PDT)
In-Reply-To: <7CC566635CFE364D87DC5803D4712A6C4CED25B070@XCH-NW-10V.nw.nos.boeing.com>
References: <7CC566635CFE364D87DC5803D4712A6C4CED25B070@XCH-NW-10V.nw.nos.boeing.com>
Date: Mon, 28 Mar 2011 15:10:05 +0200
Message-ID: <AANLkTi=NtCnz9UcLfWD7n8Zt65pf-9=KvzN7bU3Jm0GZ@mail.gmail.com>
From: Pascal Urien <pascal.urien@gmail.com>
To: "Henderson, Thomas R" <thomas.r.henderson@boeing.com>
Content-Type: multipart/alternative; boundary=0016e64f693e865da3049f8aa974
Cc: Gyu Myoung Lee <gmlee@kaist.ac.kr>, "Guy.Pujolle@lip6.fr" <Guy.Pujolle@lip6.fr>, "hiprg@irtf.org" <hiprg@irtf.org>, "Pascal.Urien@telecom-paristech.fr" <Pascal.Urien@telecom-paristech.fr>
Subject: Re: [hiprg] some questions for draft-irtf-hiprg-rfid-02
X-BeenThere: hiprg@irtf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: "Host Identity Protocol \(HIP\) Research Group" <hiprg.irtf.org>
List-Unsubscribe: <https://www.irtf.org/mailman/listinfo/hiprg>, <mailto:hiprg-request@irtf.org?subject=unsubscribe>
List-Archive: <http://www.irtf.org/mail-archive/web/hiprg>
List-Post: <mailto:hiprg@irtf.org>
List-Help: <mailto:hiprg-request@irtf.org?subject=help>
List-Subscribe: <https://www.irtf.org/mailman/listinfo/hiprg>, <mailto:hiprg-request@irtf.org?subject=subscribe>
X-List-Received-Date: Mon, 28 Mar 2011 13:08:29 -0000

--0016e64f693e865da3049f8aa974
Content-Type: text/plain; charset=ISO-8859-1

Hi Thoams

2011/3/28 Henderson, Thomas R <thomas.r.henderson@boeing.com>

> Pascal, Guy, and Guy,
> I had a few questions and comments regarding the most recent draft on HIP
> support for RFID that we could perhaps try to discuss at the meeting
> tomorrow (or on the list in the meantime).
>
> As background, it seems that the main goal of this protocol is to avoid
> disclosing the EPC to unauthorized readers; the RFID can disclose it to
> those portals that hold a shared secret with the RFID.
>

The draft targets the protection of the ID (of the RFID). It MAY be an EPC
Code, but also an other class of ID (why not an HIT ?)


>
> In the current draft, there seems to me that there is no need to include
> host identifier fields in this protocol.  The draft states that the HIT-I is
> a random number and the HIT-R could be a null value.  All of the
> identification seems to be done on the basis of the f value passed in the
> exchange, which contains enough information to find the EPC.  Could you
> explain how HITs are used, if at all?
>

The issue with the HTI-I is that it MUST not be a fix value, in order to
avoid a direct link between an object and its HIT

The portal is identfied by its HIT value, zero meaning implicitely known
(i.e the portal of a domain)


>
> On a related note, the last sentence in Section 1 mentions that it is
> similar to the BLIND in the case that only one HIT is blinded.  I am
> wondering whether that case applies here-- the initiator host identifier
> needs to be blinded, but the responder HIT doesn't really matter.  This left
> me wondering whether the protocol could be refactored as a variant of BLIND,
> in which case the EPC could be somehow embedded in the HIT-I and recoverable
> based on the shared secret and nonce exchange.  For example, make the HIT-I
> some reversible function f(key,EPC).  That would restore the use of HITs in
> the protocol.
>

BLIND has no cryto agility, it works with a fix algorithm. From a
cryptpgraphics point of view the f function may be a bijective application
(reversible) or a surjective apllication (hash)

 A profile of HIP_RFID COULD be compatible with blind  with f a bijection
and f(r1,r2, HIP_I), i.e. f is a protected value of HIP_I


>
> It wasn't clear to me how ESP would work, how are the keys derived for it?
>  The existing keys in the draft seem to be directly drawn from functions
> such as g(r1,r2, EPC) but there seems to be no analogy to the DH keymat
> derivation process in HIP.  Could you clarify what are the requirements in
> your framework for a general key derivation function?
>


What we need for ESP is
- A negociation of the Security Association SA, i.e. selected algorithms for
encryption and data integrity
- A formula, like Key(s) = PRF (r1,r2, ID, others parameters) in order to
compute the SA keys

-

>
> Another major section missing in this document is the Security
> Considerations section, which will need to be carefully written to state the
> security claims and known vulnerabilities of this protocol.
>

Agree. I suggest to focus on the case where no ESP channel is opened.

A next draft could focus on the ESP negociation.


>
> - Tom
>
>
Pascal

>
> _______________________________________________
> hiprg mailing list
> hiprg@irtf.org
> https://www.irtf.org/mailman/listinfo/hiprg
>

--0016e64f693e865da3049f8aa974
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

Hi Thoams<br><br>
<div class=3D"gmail_quote">2011/3/28 Henderson, Thomas R <span dir=3D"ltr">=
&lt;<a href=3D"mailto:thomas.r.henderson@boeing.com">thomas.r.henderson@boe=
ing.com</a>&gt;</span><br>
<blockquote style=3D"BORDER-LEFT: #ccc 1px solid; MARGIN: 0px 0px 0px 0.8ex=
; PADDING-LEFT: 1ex" class=3D"gmail_quote">Pascal, Guy, and Guy,<br>I had a=
 few questions and comments regarding the most recent draft on HIP support =
for RFID that we could perhaps try to discuss at the meeting tomorrow (or o=
n the list in the meantime).<br>
<br>As background, it seems that the main goal of this protocol is to avoid=
 disclosing the EPC to unauthorized readers; the RFID can disclose it to th=
ose portals that hold a shared secret with the RFID.<br></blockquote>
<div>=A0</div>
<div>The draft targets the protection of the ID (of the RFID). It MAY be an=
 EPC Code, but also an other class of ID (why not an HIT ?)</div>
<div>=A0</div>
<blockquote style=3D"BORDER-LEFT: #ccc 1px solid; MARGIN: 0px 0px 0px 0.8ex=
; PADDING-LEFT: 1ex" class=3D"gmail_quote"><br>In the current draft, there =
seems to me that there is no need to include host identifier fields in this=
 protocol. =A0The draft states that the HIT-I is a random number and the HI=
T-R could be a null value. =A0All of the identification seems to be done on=
 the basis of the f value passed in the exchange, which contains enough inf=
ormation to find the EPC. =A0Could you explain how HITs are used, if at all=
?<br>
</blockquote>
<div>=A0</div>
<div>The issue with the HTI-I is that it MUST not be a fix value, in order =
to avoid a direct link between an object and its HIT</div>
<div>=A0</div>
<div>The portal is identfied by its HIT value, zero meaning implicitely kno=
wn (i.e the portal of a domain)</div>
<div>=A0</div>
<blockquote style=3D"BORDER-LEFT: #ccc 1px solid; MARGIN: 0px 0px 0px 0.8ex=
; PADDING-LEFT: 1ex" class=3D"gmail_quote"><br>On a related note, the last =
sentence in Section 1 mentions that it is similar to the BLIND in the case =
that only one HIT is blinded. =A0I am wondering whether that case applies h=
ere-- the initiator host identifier needs to be blinded, but the responder =
HIT doesn&#39;t really matter. =A0This left me wondering whether the protoc=
ol could be refactored as a variant of BLIND, in which case the EPC could b=
e somehow embedded in the HIT-I and recoverable based on the shared secret =
and nonce exchange. =A0For example, make the HIT-I some reversible function=
 f(key,EPC). =A0That would restore the use of HITs in the protocol.<br>
</blockquote>
<div>=A0</div>
<div>BLIND has no cryto agility, it works with a fix algorithm. From a cryp=
tpgraphics point of view the f function may be a bijective application (rev=
ersible) or a surjective apllication (hash)</div>
<div>=A0</div>
<div>=A0A profile of HIP_RFID COULD be compatible with blind=A0=A0with f a =
bijection and f(r1,r2, HIP_I), i.e. f is a protected value of HIP_I</div>
<div>=A0</div>
<blockquote style=3D"BORDER-LEFT: #ccc 1px solid; MARGIN: 0px 0px 0px 0.8ex=
; PADDING-LEFT: 1ex" class=3D"gmail_quote"><br>It wasn&#39;t clear to me ho=
w ESP would work, how are the keys derived for it? =A0The existing keys in =
the draft seem to be directly drawn from functions such as g(r1,r2, EPC) bu=
t there seems to be no analogy to the DH keymat derivation process in HIP. =
=A0Could you clarify what are the requirements in your framework for a gene=
ral key derivation function?<br>
</blockquote>
<div>=A0</div>
<div>=A0</div>
<div>What we need for ESP is</div>
<div>- A negociation of the Security Association SA, i.e. selected algorith=
ms for encryption and data integrity</div>
<div>- A formula, like Key(s) =3D PRF (r1,r2, ID, others parameters) in ord=
er to compute the SA keys</div>
<div>=A0</div>
<div>- </div>
<blockquote style=3D"BORDER-LEFT: #ccc 1px solid; MARGIN: 0px 0px 0px 0.8ex=
; PADDING-LEFT: 1ex" class=3D"gmail_quote"><br>Another major section missin=
g in this document is the Security Considerations section, which will need =
to be carefully written to state the security claims and known vulnerabilit=
ies of this protocol.<br>
</blockquote>
<div>=A0</div>
<div>Agree. I suggest to focus on the case where no ESP channel is opened. =
</div>
<div>=A0</div>
<div>A next draft could focus on the ESP negociation.</div>
<div>=A0</div>
<blockquote style=3D"BORDER-LEFT: #ccc 1px solid; MARGIN: 0px 0px 0px 0.8ex=
; PADDING-LEFT: 1ex" class=3D"gmail_quote"><br>- Tom<br><br></blockquote>
<div>=A0</div>
<div>Pascal</div>
<blockquote style=3D"BORDER-LEFT: #ccc 1px solid; MARGIN: 0px 0px 0px 0.8ex=
; PADDING-LEFT: 1ex" class=3D"gmail_quote"><br>____________________________=
___________________<br>hiprg mailing list<br><a href=3D"mailto:hiprg@irtf.o=
rg">hiprg@irtf.org</a><br>
<a href=3D"https://www.irtf.org/mailman/listinfo/hiprg" target=3D"_blank">h=
ttps://www.irtf.org/mailman/listinfo/hiprg</a><br></blockquote></div><br>

--0016e64f693e865da3049f8aa974--

From thomas.r.henderson@boeing.com  Mon Mar 28 07:11:43 2011
Return-Path: <thomas.r.henderson@boeing.com>
X-Original-To: hiprg@core3.amsl.com
Delivered-To: hiprg@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 688F83A684A for <hiprg@core3.amsl.com>; Mon, 28 Mar 2011 07:11:40 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -106.126
X-Spam-Level: 
X-Spam-Status: No, score=-106.126 tagged_above=-999 required=5 tests=[AWL=-0.326, 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.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id yyZqPQW0GYtN for <hiprg@core3.amsl.com>; Mon, 28 Mar 2011 07:11:37 -0700 (PDT)
Received: from blv-smtpout-01.boeing.com (blv-smtpout-01.boeing.com [130.76.32.69]) by core3.amsl.com (Postfix) with ESMTP id 77BCB3A6849 for <hiprg@irtf.org>; Mon, 28 Mar 2011 07:11:36 -0700 (PDT)
Received: from slb-av-01.boeing.com (slb-av-01.boeing.com [129.172.13.4]) by blv-smtpout-01.ns.cs.boeing.com (8.14.4/8.14.4/8.14.4/SMTPOUT) with ESMTP id p2SEBcFp023945 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=FAIL); Mon, 28 Mar 2011 07:11:41 -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 p2SEBc3o012355; Mon, 28 Mar 2011 07:11:38 -0700 (PDT)
Received: from XCH-NWHT-07.nw.nos.boeing.com (xch-nwht-07.nw.nos.boeing.com [130.247.25.111]) by slb-av-01.boeing.com (8.14.4/8.14.4/UPSTREAM_RELAY) with ESMTP id p2SEBbha012333 (version=TLSv1/SSLv3 cipher=RC4-MD5 bits=128 verify=OK); Mon, 28 Mar 2011 07:11:37 -0700 (PDT)
Received: from XCH-NW-10V.nw.nos.boeing.com ([130.247.25.85]) by XCH-NWHT-07.nw.nos.boeing.com ([130.247.25.111]) with mapi; Mon, 28 Mar 2011 07:11:37 -0700
From: "Henderson, Thomas R" <thomas.r.henderson@boeing.com>
To: "'Dacheng Zhang'" <zhangdacheng@huawei.com>, "'dmitriy.kuptsov@hiit.fi'" <dmitriy.kuptsov@hiit.fi>, "shenshuo@cnnic.cn" <shenshuo@cnnic.cn>
Date: Mon, 28 Mar 2011 07:11:36 -0700
Thread-Topic: comments on draft-irtf-hiprg-revocation-02.txt
Thread-Index: AcvtUgr0JPTQnn+KSBOKCovcRAefjg==
Message-ID: <7CC566635CFE364D87DC5803D4712A6C4CED25B071@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
Cc: "hiprg@irtf.org" <hiprg@irtf.org>
Subject: [hiprg] comments on draft-irtf-hiprg-revocation-02.txt
X-BeenThere: hiprg@irtf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: "Host Identity Protocol \(HIP\) Research Group" <hiprg.irtf.org>
List-Unsubscribe: <https://www.irtf.org/mailman/listinfo/hiprg>, <mailto:hiprg-request@irtf.org?subject=unsubscribe>
List-Archive: <http://www.irtf.org/mail-archive/web/hiprg>
List-Post: <mailto:hiprg@irtf.org>
List-Help: <mailto:hiprg-request@irtf.org?subject=help>
List-Subscribe: <https://www.irtf.org/mailman/listinfo/hiprg>, <mailto:hiprg-request@irtf.org?subject=subscribe>
X-List-Received-Date: Mon, 28 Mar 2011 14:11:44 -0000

Dacheng and all,

Here are some comments on the latest version of your document.  I think tha=
t the draft could be improved by more careful definition of and distinction=
 between the host identity and host identifier (see RFC4423), and to summar=
ize  more clearly (in the introduction) the main issues that this draft is =
concerned with:

1) what does it mean for two or more different hosts to have the same host =
identifier?  Here there are two cases:  1a) there is a trusted third party =
who can resolve this, and 1b) there is no such arbitrator

2) what does it mean for one host to have multiple host identifiers associa=
ted with the same host identity; can these be associated together and can t=
hey be expired or deprecated similar to how locators are deprecated?

I think that the draft has some clear solutions for some of the above quest=
ions but less clear for others, so it would be useful to also summarize in =
section 1 which of the questions are well answered and which will require f=
urther study.

It is time to start filling in the terminology section more fully (Section =
2).

Where you say in Section 5:  "Until now, the ID to Locator mapping solution=
 in HIP has not been standardized yet.  We argue that it is desired to inte=
grate the implicit key revocation functionality into such systems."  I woul=
d suggest to clarify that you are not talking about DNS here but instead ab=
out something like the DHT lookup.

In section 6 paragraph 2, I did not understand how this case could handle t=
he situation when the reason to remove the HI was due to key compromise-- p=
erhaps clarify this point here.

In section 8, the end of this section ends prematurely.  The paragraph that=
 starts "Because the HI of a HIP host acts as both the identity and the pub=
lic key of the HIP host at the same time." does not contain complete senten=
ces and has some of the terminology problems that I mentioned above.

In section 10 (Security considerations), I think you need to start filling =
it out, rather than the blanket statement that you have there.  Perhaps a w=
ay to start is to review this RFC:  http://www.ietf.org/rfc/rfc3552.txt

- Tom





From thomas.r.henderson@boeing.com  Mon Mar 28 08:31:54 2011
Return-Path: <thomas.r.henderson@boeing.com>
X-Original-To: hiprg@core3.amsl.com
Delivered-To: hiprg@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 50E913A6A53 for <hiprg@core3.amsl.com>; Mon, 28 Mar 2011 08:31:54 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -105.806
X-Spam-Level: 
X-Spam-Status: No, score=-105.806 tagged_above=-999 required=5 tests=[AWL=-0.606, BAYES_00=-2.599, J_CHICKENPOX_13=0.6, RCVD_IN_DNSWL_MED=-4, SARE_SUB_RAND_LETTRS4=0.799, USER_IN_WHITELIST=-100]
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 3vn6OqXHuALP for <hiprg@core3.amsl.com>; Mon, 28 Mar 2011 08:31:53 -0700 (PDT)
Received: from slb-smtpout-01.boeing.com (slb-smtpout-01.boeing.com [130.76.64.48]) by core3.amsl.com (Postfix) with ESMTP id 3C4573A6943 for <hiprg@irtf.org>; Mon, 28 Mar 2011 08:31:53 -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 p2SFXEB2022736 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=FAIL); Mon, 28 Mar 2011 08:33:15 -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 p2SFXEA1002460; Mon, 28 Mar 2011 10:33:14 -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 p2SFXD2k002435 (version=TLSv1/SSLv3 cipher=RC4-MD5 bits=128 verify=OK); Mon, 28 Mar 2011 10:33:14 -0500 (CDT)
Received: from XCH-NW-10V.nw.nos.boeing.com ([130.247.25.85]) by XCH-NWHT-06.nw.nos.boeing.com ([130.247.25.110]) with mapi; Mon, 28 Mar 2011 08:33:13 -0700
From: "Henderson, Thomas R" <thomas.r.henderson@boeing.com>
To: "'Pascal Urien'" <pascal.urien@gmail.com>
Date: Mon, 28 Mar 2011 08:33:12 -0700
Thread-Topic: [hiprg] some questions for draft-irtf-hiprg-rfid-02
Thread-Index: AcvtSXdeKespkGgESOCI7p8glHgP3gAEea3wAAAP2tA=
Message-ID: <7CC566635CFE364D87DC5803D4712A6C4CED25B074@XCH-NW-10V.nw.nos.boeing.com>
References: <7CC566635CFE364D87DC5803D4712A6C4CED25B073@XCH-NW-10V.nw.nos.boeing.com>
In-Reply-To: <7CC566635CFE364D87DC5803D4712A6C4CED25B073@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="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Cc: Gyu Myoung Lee <gmlee@kaist.ac.kr>, "Guy.Pujolle@lip6.fr" <Guy.Pujolle@lip6.fr>, "hiprg@irtf.org" <hiprg@irtf.org>, "Pascal.Urien@telecom-paristech.fr" <Pascal.Urien@telecom-paristech.fr>
Subject: Re: [hiprg] some questions for draft-irtf-hiprg-rfid-02
X-BeenThere: hiprg@irtf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: "Host Identity Protocol \(HIP\) Research Group" <hiprg.irtf.org>
List-Unsubscribe: <https://www.irtf.org/mailman/listinfo/hiprg>, <mailto:hiprg-request@irtf.org?subject=unsubscribe>
List-Archive: <http://www.irtf.org/mail-archive/web/hiprg>
List-Post: <mailto:hiprg@irtf.org>
List-Help: <mailto:hiprg-request@irtf.org?subject=help>
List-Subscribe: <https://www.irtf.org/mailman/listinfo/hiprg>, <mailto:hiprg-request@irtf.org?subject=subscribe>
X-List-Received-Date: Mon, 28 Mar 2011 15:31:54 -0000

>=20
> From: Pascal Urien [mailto:pascal.urien@gmail.com]
> Sent: Monday, March 28, 2011 6:10 AM
> To: Henderson, Thomas R
> Cc: Pascal.Urien@telecom-paristech.fr; Gyu Myoung Lee;
> Guy.Pujolle@lip6.fr; hiprg@irtf.org
> Subject: Re: [hiprg] some questions for draft-irtf-hiprg-rfid-02
>=20
> Hi Thoams
> 2011/3/28 Henderson, Thomas R <thomas.r.henderson@boeing.com>
> Pascal, Guy, and Guy,
> I had a few questions and comments regarding the most recent draft on
> HIP support for RFID that we could perhaps try to discuss at the
> meeting tomorrow (or on the list in the meantime).
>=20
> As background, it seems that the main goal of this protocol is to avoid
> disclosing the EPC to unauthorized readers; the RFID can disclose it to
> those portals that hold a shared secret with the RFID.
>=20
> The draft targets the protection of the ID (of the RFID). It MAY be an
> EPC Code, but also an other class of ID (why not an HIT ?)
>=20
> In the current draft, there seems to me that there is no need to
> include host identifier fields in this protocol. =A0The draft states that
> the HIT-I is a random number and the HIT-R could be a null value. =A0All
> of the identification seems to be done on the basis of the f value
> passed in the exchange, which contains enough information to find the
> EPC. =A0Could you explain how HITs are used, if at all?
>=20
> The issue with the HTI-I is that it MUST not be a fix value, in order
> to avoid a direct link between an object and its HIT
>=20
> The portal is identfied by its HIT value, zero meaning implicitely
> known (i.e the portal of a domain)
>=20
>=20
>> On a related note, the last sentence in Section 1 mentions that it is
>> similar to the BLIND in the case that only one HIT is blinded. =A0I am
>> wondering whether that case applies here-- the initiator host
>> identifier needs to be blinded, but the responder HIT doesn't really
>> matter. =A0This left me wondering whether the protocol could be
>> refactored as a variant of BLIND, in which case the EPC could be
>> somehow embedded in the HIT-I and recoverable based on the shared
>> secret and nonce exchange. =A0For example, make the HIT-I some reversibl=
e
>> function f(key,EPC). =A0That would restore the use of HITs in the
>> protocol.
>=20
> BLIND has no cryto agility, it works with a fix algorithm. From a
> cryptpgraphics point of view the f function may be a bijective
> application (reversible) or a surjective apllication (hash)
>=20
>  A profile of HIP_RFID COULD be compatible with blind  with f a
> bijection and f(r1,r2, HIP_I), i.e. f is a protected value of HIP_I
>=20
>

Your points are important clarifications that we should try to include in t=
he draft.  Especially what role the HITs play in different variations of th=
e protocol, and how this is different from traditional HIP.

>> It wasn't clear to me how ESP would work, how are the keys derived for
>> it? =A0The existing keys in the draft seem to be directly drawn from
>> functions such as g(r1,r2, EPC) but there seems to be no analogy to the
>> DH keymat derivation process in HIP. =A0Could you clarify what are the
>> requirements in your framework for a general key derivation function?
>=20
>=20
> What we need for ESP is
> - A negociation of the Security Association SA, i.e. selected
> algorithms for encryption and data integrity
> - A formula, like Key(s) =3D PRF (r1,r2, ID, others parameters) in order
> to compute the SA keys
>=20

again, please include the above in an update

> -
>=20
>> Another major section missing in this document is the Security
>> Considerations section, which will need to be carefully written to
>> state the security claims and known vulnerabilities of this protocol.
>=20
> Agree. I suggest to focus on the case where no ESP channel is opened.
>=20
> A next draft could focus on the ESP negociation.

Thanks for the quick response.

Tom

From zhangdacheng@huawei.com  Mon Mar 28 09:19:41 2011
Return-Path: <zhangdacheng@huawei.com>
X-Original-To: hiprg@core3.amsl.com
Delivered-To: hiprg@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 51C5B3A6A63 for <hiprg@core3.amsl.com>; Mon, 28 Mar 2011 09:19:41 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.923
X-Spam-Level: 
X-Spam-Status: No, score=0.923 tagged_above=-999 required=5 tests=[AWL=-2.676,  BAYES_00=-2.599, CHARSET_FARAWAY_HEADER=3.2, FH_RELAY_NODNS=1.451,  HELO_MISMATCH_COM=0.553, MIME_8BIT_HEADER=0.3, MIME_CHARSET_FARAWAY=2.45, RCVD_IN_DNSWL_MED=-4, RDNS_NONE=0.1, SARE_SUB_ENC_GB2312=1.345, SARE_SUB_RAND_LETTRS4=0.799]
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 jrOiHulYAtND for <hiprg@core3.amsl.com>; Mon, 28 Mar 2011 09:19:36 -0700 (PDT)
Received: from szxga04-in.huawei.com (unknown [119.145.14.67]) by core3.amsl.com (Postfix) with ESMTP id 9F3A33A6892 for <hiprg@irtf.org>; Mon, 28 Mar 2011 09:19:34 -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 <0LIS00NH502Z2W@szxga04-in.huawei.com> for hiprg@irtf.org; Tue, 29 Mar 2011 00:20:59 +0800 (CST)
Received: from szxeml204-edg.china.huawei.com ([172.24.2.119]) by szxga04-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 2.14 (built Aug  8 2006)) with ESMTP id <0LIS00GPR02Z1P@szxga04-in.huawei.com> for hiprg@irtf.org; Tue, 29 Mar 2011 00:20:59 +0800 (CST)
Received: from SZXEML403-HUB.china.huawei.com (10.82.67.35) by szxeml204-edg.china.huawei.com (172.24.2.56) with Microsoft SMTP Server (TLS) id 14.1.270.1; Tue, 29 Mar 2011 00:20:56 +0800
Received: from SZXEML501-MBX.china.huawei.com ([169.254.5.242]) by szxeml403-hub.china.huawei.com ([169.254.173.75]) with mapi id 14.01.0270.001; Tue, 29 Mar 2011 00:20:58 +0800
Date: Mon, 28 Mar 2011 16:20:58 +0000
From: "Dacheng Zhang(Dacheng)" <zhangdacheng@huawei.com>
In-reply-to: <7CC566635CFE364D87DC5803D4712A6C4CED25B071@XCH-NW-10V.nw.nos.boeing.com>
X-Originating-IP: [172.24.2.41]
To: "Henderson, Thomas R" <thomas.r.henderson@boeing.com>, "'dmitriy.kuptsov@hiit.fi'" <dmitriy.kuptsov@hiit.fi>, "shenshuo@cnnic.cn" <shenshuo@cnnic.cn>
Message-id: <C72CBD9FE3CA604887B1B3F1D145D05E7DC5C4@szxeml501-mbx.china.huawei.com>
MIME-version: 1.0
Content-type: text/plain; charset=gb2312
Content-language: zh-CN
Content-transfer-encoding: 7BIT
Accept-Language: zh-CN, en-US
Thread-topic: comments on draft-irtf-hiprg-revocation-02.txt
Thread-index: AcvtUgr0JPTQnn+KSBOKCovcRAefjgAEHR4o
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
References: <7CC566635CFE364D87DC5803D4712A6C4CED25B071@XCH-NW-10V.nw.nos.boeing.com>
Cc: "hiprg@irtf.org" <hiprg@irtf.org>
Subject: [hiprg] =?gb2312?b?ILTwuLQ6IGNvbW1lbnRzIG9uIGRyYWZ0LWlydGYtaGlw?= =?gb2312?b?cmctcmV2b2NhdGlvbi0wMi50eHQ=?=
X-BeenThere: hiprg@irtf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: "Host Identity Protocol \(HIP\) Research Group" <hiprg.irtf.org>
List-Unsubscribe: <https://www.irtf.org/mailman/listinfo/hiprg>, <mailto:hiprg-request@irtf.org?subject=unsubscribe>
List-Archive: <http://www.irtf.org/mail-archive/web/hiprg>
List-Post: <mailto:hiprg@irtf.org>
List-Help: <mailto:hiprg-request@irtf.org?subject=help>
List-Subscribe: <https://www.irtf.org/mailman/listinfo/hiprg>, <mailto:hiprg-request@irtf.org?subject=subscribe>
X-List-Received-Date: Mon, 28 Mar 2011 16:19:41 -0000

Thanks a lot, Tom. Please see the inline please.

>>Here are some comments on the latest version of your document.  I think that the draft could be improved by more careful definition of and distinction between the host identity and host identifier (see RFC4423), and to summarize  more >>clearly (in the introduction) the main issues that this draft is concerned with:

>>1) what does it mean for two or more different hosts to have the same host identifier?  Here there are two cases:  1a) there is a trusted third party who can resolve this, and 1b) there is no such arbitrator

>>2) what does it mean for one host to have multiple host identifiers associated with the same host identity; can these be associated together and can they be expired or deprecated similar to how locators are deprecated?

Will update it!

>>I think that the draft has some clear solutions for some of the above questions but less clear for others, so it would be useful to also summarize in section 1 which of the questions are well answered and which will require further study.

>>It is time to start filling in the terminology section more fully (Section 2).
Agree and will do it.

>>Where you say in Section 5:  "Until now, the ID to Locator mapping solution in HIP has not been standardized yet.  We argue that it is desired to integrate the implicit key revocation functionality into such systems."  I would suggest to >>clarify that you are not talking about DNS here but instead about something like the DHT lookup.

DNS is a "Locator to ID " mapping solution. Yes, when I mention "ID to Locator" mapping solution, I indicate the DHT solution.

>>In section 6 paragraph 2, I did not understand how this case could handle the situation when the reason to remove the HI was due to key compromise-- perhaps clarify this point here.

This paragraph introduce the CRL solution in PKI. I just try to indicate that when a HI is removed, the revocation information can be put a trusted third party for other interested hosts to query. Will update it!

>>In section 8, the end of this section ends prematurely.  The paragraph that starts "Because the HI of a HIP host acts as both the identity and the public key of the HIP host at the same time." does not contain complete sentences and has >>some of the terminology problems that I mentioned above.

Will update it!

>>In section 10 (Security considerations), I think you need to start filling it out, rather than the blanket statement that you have there.  Perhaps a way to start is to review this RFC:  http://www.ietf.org/rfc/rfc3552.txt

Will update it!

- Tom





From thomas.r.henderson@boeing.com  Mon Mar 28 11:39:06 2011
Return-Path: <thomas.r.henderson@boeing.com>
X-Original-To: hiprg@core3.amsl.com
Delivered-To: hiprg@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 1031A3A68E0 for <hiprg@core3.amsl.com>; Mon, 28 Mar 2011 11:39:06 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -106.07
X-Spam-Level: 
X-Spam-Status: No, score=-106.07 tagged_above=-999 required=5 tests=[AWL=-0.270, 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.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id yUrDSJ26cl3h for <hiprg@core3.amsl.com>; Mon, 28 Mar 2011 11:39:05 -0700 (PDT)
Received: from blv-smtpout-01.boeing.com (blv-smtpout-01.boeing.com [130.76.32.69]) by core3.amsl.com (Postfix) with ESMTP id 4F7873A67D6 for <hiprg@irtf.org>; Mon, 28 Mar 2011 11:39:05 -0700 (PDT)
Received: from blv-av-01.boeing.com (blv-av-01.boeing.com [130.247.48.231]) by blv-smtpout-01.ns.cs.boeing.com (8.14.4/8.14.4/8.14.4/SMTPOUT) with ESMTP id p2SIeYPm011703 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=FAIL); Mon, 28 Mar 2011 11:40:34 -0700 (PDT)
Received: from blv-av-01.boeing.com (localhost [127.0.0.1]) by blv-av-01.boeing.com (8.14.4/8.14.4/DOWNSTREAM_RELAY) with ESMTP id p2SIeYn3004014; Mon, 28 Mar 2011 11:40:34 -0700 (PDT)
Received: from XCH-NWHT-03.nw.nos.boeing.com (xch-nwht-03.nw.nos.boeing.com [130.247.71.23]) by blv-av-01.boeing.com (8.14.4/8.14.4/UPSTREAM_RELAY) with ESMTP id p2SIeYkt004007 (version=TLSv1/SSLv3 cipher=RC4-MD5 bits=128 verify=OK); Mon, 28 Mar 2011 11:40:34 -0700 (PDT)
Received: from XCH-NW-10V.nw.nos.boeing.com ([130.247.25.85]) by XCH-NWHT-03.nw.nos.boeing.com ([130.247.71.23]) with mapi; Mon, 28 Mar 2011 11:40:33 -0700
From: "Henderson, Thomas R" <thomas.r.henderson@boeing.com>
To: "'Dacheng Zhang'" <zhangdacheng@huawei.com>, "'???'" <xuxh@huawei.com>, "shenshuo@cnnic.cn" <shenshuo@cnnic.cn>
Date: Mon, 28 Mar 2011 11:40:33 -0700
Thread-Topic: comments on draft-irtf-hiprg-proxies-02
Thread-Index: Acvtd50Td7prmPSyR3KTVBFI/v+ZBg==
Message-ID: <7CC566635CFE364D87DC5803D4712A6C4CED25B07C@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
Cc: "hiprg@irtf.org" <hiprg@irtf.org>
Subject: [hiprg] comments on draft-irtf-hiprg-proxies-02
X-BeenThere: hiprg@irtf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: "Host Identity Protocol \(HIP\) Research Group" <hiprg.irtf.org>
List-Unsubscribe: <https://www.irtf.org/mailman/listinfo/hiprg>, <mailto:hiprg-request@irtf.org?subject=unsubscribe>
List-Archive: <http://www.irtf.org/mail-archive/web/hiprg>
List-Post: <mailto:hiprg@irtf.org>
List-Help: <mailto:hiprg-request@irtf.org?subject=help>
List-Subscribe: <https://www.irtf.org/mailman/listinfo/hiprg>, <mailto:hiprg-request@irtf.org?subject=subscribe>
X-List-Received-Date: Mon, 28 Mar 2011 18:39:06 -0000

Dacheng and all,
I reviewed this draft and I believe the presentation and terminology is muc=
h improved from the previous version.  I can provide editorial comments sep=
arately.  The terminology section in Section 2 needs to be completed more f=
ully.  Another term that is used frequently in the draft but is not complet=
ely clear to me is "DNS lookup inspector" (is this a resolver?). =20

I do not have a specific text suggestion for this but I would suggest also =
in the security considerations section to talk about considerations for DI-=
proxy types in the DNS intercepting aspects of the configuration.  Earlier =
in the draft, you brought up the problems with DNSSEC, but are there also s=
ecurity concerns introduced by having a DNS intercepting proxy involved in =
general (is a host more exposed to DNS-related attacks)?

- Tom

From thomas.r.henderson@boeing.com  Mon Mar 28 13:56:54 2011
Return-Path: <thomas.r.henderson@boeing.com>
X-Original-To: hiprg@core3.amsl.com
Delivered-To: hiprg@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id E460328C107 for <hiprg@core3.amsl.com>; Mon, 28 Mar 2011 13:56:54 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -106.462
X-Spam-Level: 
X-Spam-Status: No, score=-106.462 tagged_above=-999 required=5 tests=[AWL=0.137, BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4, USER_IN_WHITELIST=-100]
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 JMIuECEj2e7F for <hiprg@core3.amsl.com>; Mon, 28 Mar 2011 13:56:54 -0700 (PDT)
Received: from slb-smtpout-01.boeing.com (slb-smtpout-01.boeing.com [130.76.64.48]) by core3.amsl.com (Postfix) with ESMTP id 2233D28C0F7 for <hiprg@irtf.org>; Mon, 28 Mar 2011 13:56:54 -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 p2SKwNVD011403 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=FAIL) for <hiprg@irtf.org>; Mon, 28 Mar 2011 13:58:24 -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 p2SKwNKE017504 for <hiprg@irtf.org>; Mon, 28 Mar 2011 15:58:23 -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 p2SKwLT0017465 (version=TLSv1/SSLv3 cipher=RC4-MD5 bits=128 verify=OK) for <hiprg@irtf.org>; Mon, 28 Mar 2011 15:58:23 -0500 (CDT)
Received: from XCH-NW-10V.nw.nos.boeing.com ([130.247.25.85]) by XCH-NWHT-07.nw.nos.boeing.com ([130.247.25.111]) with mapi; Mon, 28 Mar 2011 13:58:21 -0700
From: "Henderson, Thomas R" <thomas.r.henderson@boeing.com>
To: "hiprg@irtf.org" <hiprg@irtf.org>
Date: Mon, 28 Mar 2011 13:58:19 -0700
Thread-Topic: draft statement for level of support of the HIP experiment report
Thread-Index: Acvtitz5ZNNv/9q5RiekieSE8eiVJA==
Message-ID: <7CC566635CFE364D87DC5803D4712A6C4CED25B084@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] draft statement for level of support of the HIP experiment report
X-BeenThere: hiprg@irtf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: "Host Identity Protocol \(HIP\) Research Group" <hiprg.irtf.org>
List-Unsubscribe: <https://www.irtf.org/mailman/listinfo/hiprg>, <mailto:hiprg-request@irtf.org?subject=unsubscribe>
List-Archive: <http://www.irtf.org/mail-archive/web/hiprg>
List-Post: <mailto:hiprg@irtf.org>
List-Help: <mailto:hiprg-request@irtf.org?subject=help>
List-Subscribe: <https://www.irtf.org/mailman/listinfo/hiprg>, <mailto:hiprg-request@irtf.org?subject=subscribe>
X-List-Received-Date: Mon, 28 Mar 2011 20:56:55 -0000

Following the procedures here:
http://trac.tools.ietf.org/group/irtf/trac/wiki/IRTF-RFCs#ResearchGroupPrep=
aration

we need to add a paragraph near the beginning of the experiment report stat=
ing the breadth and depth of review of the draft by the RG.  For the experi=
ment report, I plan to state the following unless someone objects.

"This document was developed over several years as the main charter item fo=
r the HIP research group, and has received inputs and reviews from most of =
the active research group participants.  There is research group consensus =
to publish it."

- Tom
