
From heer@informatik.rwth-aachen.de  Wed Nov  3 09:03:12 2010
Return-Path: <heer@informatik.rwth-aachen.de>
X-Original-To: hipsec@core3.amsl.com
Delivered-To: hipsec@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 8B1F728C0FD for <hipsec@core3.amsl.com>; Wed,  3 Nov 2010 09:03:12 -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.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id XkscE6llLqBg for <hipsec@core3.amsl.com>; Wed,  3 Nov 2010 09:03:11 -0700 (PDT)
Received: from mta-2.ms.rz.rwth-aachen.de (mta-2.ms.rz.RWTH-Aachen.DE [134.130.7.73]) by core3.amsl.com (Postfix) with ESMTP id 3E7BF28C0E7 for <hipsec@ietf.org>; Wed,  3 Nov 2010 09:03:11 -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-2.ms.rz.RWTH-Aachen.de (Sun Java(tm) System Messaging Server 6.3-7.04 (built Sep 26 2008)) with ESMTP id <0LBB00AFEGLITZ10@mta-2.ms.rz.RWTH-Aachen.de> for hipsec@ietf.org; Wed, 03 Nov 2010 17:03:18 +0100 (CET)
X-IronPort-AV: E=Sophos;i="4.58,289,1286143200";   d="scan'208";a="79629692"
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; Wed, 03 Nov 2010 17:03:18 +0100
Received: from umic-i4-137-226-45-90.nn.rwth-aachen.de ([unknown] [137.226.45.90]) 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 <0LBB00476GLIEI10@relay-auth-2.ms.rz.rwth-aachen.de> for hipsec@ietf.org; Wed, 03 Nov 2010 17:03:18 +0100 (CET)
From: Tobias Heer <heer@cs.rwth-aachen.de>
Date: Wed, 03 Nov 2010 17:03:18 +0100
Message-id: <0752B0E2-59FC-4CEE-B0BE-20074885E92C@cs.rwth-aachen.de>
To: HIP WG <hipsec@ietf.org>, hiprg@irtf.org
X-Pgp-Agent: GPGMail 1.3.0
X-Mailer: Apple Mail (2.1081)
Subject: [Hipsec] Activities regarding CoRE and HIP for Internet of Things
X-BeenThere: hipsec@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: "This is the official IETF Mailing List for the HIP Working Group." <hipsec.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/hipsec>, <mailto:hipsec-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/hipsec>
List-Post: <mailto:hipsec@ietf.org>
List-Help: <mailto:hipsec-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/hipsec>, <mailto:hipsec-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 03 Nov 2010 16:03:12 -0000

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Hi,

I'd like to bring to your attention that there was some discussion about using HIP for resource constrained devices in the context of the CoRE WG. The discussion is still ongoing.
Some of you folks might be interested in following the discussions on the core mailing list [1] or reading previous posts in the archives[2].

Best regards, and possibly see you in Beijing,

Tobias

[1] http://www.ietf.org/mailman/listinfo/core
[2] http://www.ietf.org/mail-archive/web/core/

- -- 
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://ds.cs.rwth-aachen.de/members/heer
blog: http://dtobi.wordpress.com/
card: http://card.ly/dtobi







-----BEGIN PGP SIGNATURE-----
Version: GnuPG/MacGPG2 v2.0.14 (Darwin)

iEYEARECAAYFAkzRh8YACgkQf4eSaa7spb/weQCeJx2yhkhPdfRzC8XUEKeOuhiy
ZA0An0lC+W42bgDrGpNSUdFIHCM1vtb7
=MkJq
-----END PGP SIGNATURE-----

From zfhu2001@163.com  Thu Nov  4 02:48:29 2010
Return-Path: <zfhu2001@163.com>
X-Original-To: hipsec@core3.amsl.com
Delivered-To: hipsec@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 6039F3A69D5 for <hipsec@core3.amsl.com>; Thu,  4 Nov 2010 02:48:29 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.002
X-Spam-Level: 
X-Spam-Status: No, score=0.002 tagged_above=-999 required=5 tests=[BAYES_50=0.001, HTML_MESSAGE=0.001]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id nmntEkaUJUD6 for <hipsec@core3.amsl.com>; Thu,  4 Nov 2010 02:48:26 -0700 (PDT)
Received: from m50-132.163.com (m50-132.163.com [123.125.50.132]) by core3.amsl.com (Postfix) with ESMTP id C0EC43A692F for <hipsec@ietf.org>; Thu,  4 Nov 2010 02:48:25 -0700 (PDT)
Received: from ZFHU-BUTP (unknown [123.122.4.195]) by smtp2 (Coremail) with SMTP id DNGowKBr1IRwgdJMquXaAA--.191S2; Thu, 04 Nov 2010 17:48:34 +0800 (CST)
Date: Thu, 4 Nov 2010 17:48:25 +0800
From: "zfhu2001" <zfhu2001@163.com>
To: "hipsec" <hipsec@ietf.org>
Message-ID: <201011041748233287181@163.com>
X-mailer: Foxmail 6, 15, 201, 23 [cn]
Mime-Version: 1.0
Content-Type: multipart/alternative; boundary="=====003_Dragon215848251840_====="
X-CM-TRANSID: DNGowKBr1IRwgdJMquXaAA--.191S2
X-Coremail-Antispam: 1Uf129KBjvdXoWrXFyxXrWftFW7ZF1fKrWUtwb_yoWxXFc_u3 yvkryDta1kWr47Kr4xGF45WrWS9ayUKr1avw4Fqas3Cwn8Jr45Jry0qr9Ykw1Iy3WjgrZI yr1SvrZa9w13WjkaLaAFLSUrUUUUUb8apTn2vfkv8UJUUUU8Yxn0WfASr-VFAUDa7-sFnT 9fnUUvcSsGvfC2KfnxnUUI43ZEXa7IU8j0PDUUUUU==
X-CM-SenderInfo: p2ik3jqqqrqiywtou0bp/1tbiOQJ-iUjh4v67rQAAsu
Cc: =?gb2312?B?uvqyqcDPyqY=?= <bj.hubo@gmail.com>, =?gb2312?B?tsXOxL6y?= <lxadj@126.com>
Subject: [Hipsec]  HIP Registration problem
X-BeenThere: hipsec@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: "This is the official IETF Mailing List for the HIP Working Group." <hipsec.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/hipsec>, <mailto:hipsec-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/hipsec>
List-Post: <mailto:hipsec@ietf.org>
List-Help: <mailto:hipsec-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/hipsec>, <mailto:hipsec-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 04 Nov 2010 09:48:29 -0000

This is a multi-part message in MIME format.

--=====003_Dragon215848251840_=====
Content-Type: text/plain;
	charset="gb2312"
Content-Transfer-Encoding: 7bit

Hi all,

    As we know, a mobile node registers its HIP and IP address binding to a correponding RVS server, but now I'm wondering whether the MN will register to a new RVS if a mobile node moves to another network and simultaneously its previous RVS server does not work any more. Or does HIP provide a mechanisim as DAAP of MIP to detect the serving RVS server of its home area?
Thanks.

2010-11-04 



  
Zhangfeng HU, PhD candidate of
Broadband Network Research Center,
State Key Laboratory of Networking and Switching Technology, 
Beijing University of Posts and Telecommunications, Beijing, China

Email:zfhu2001@gmail.com
Tel:86+13811892137

--=====003_Dragon215848251840_=====
Content-Type: text/html;
	charset="gb2312"
Content-Transfer-Encoding: 7bit

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META content="text/html; charset=gb2312" http-equiv=Content-Type>
<META name=GENERATOR content="MSHTML 8.00.6001.18975"><LINK rel=stylesheet 
href="BLOCKQUOTE{margin-Top: 0px; margin-Bottom: 0px; margin-Left: 2em}"></HEAD>
<BODY style="MARGIN: 10px; FONT-FAMILY: verdana; FONT-SIZE: 10pt">
<DIV><FONT size=2>
<DIV>Hi&nbsp;all,</DIV>
<DIV>&nbsp;</DIV>
<DIV>&nbsp;&nbsp;&nbsp; As we know, a mobile node registers its HIP and IP 
address binding to a correponding RVS server, but now I'm wondering whether the 
MN will register to a new RVS if a mobile node moves to another network and 
simultaneously its previous RVS server does not work any more.&nbsp;Or does HIP 
provide a mechanisim as DAAP of MIP to detect the serving RVS server of its home 
area?</DIV>
<DIV>Thanks.</DIV></FONT></DIV>
<DIV><FONT size=2></FONT>&nbsp;</DIV>
<DIV align=left><FONT color=#c0c0c0 size=2>2010-11-04 </FONT></DIV><FONT size=2>
<HR style="WIDTH: 122px; HEIGHT: 2px" align=left SIZE=2>

<DIV><FONT color=#c0c0c0 size=2><SPAN>
<DIV>
<DIV><FONT size=2></FONT>&nbsp; 
<DIV><FONT size=1>Zhangfeng HU, PhD&nbsp;candidate of</FONT></DIV>
<DIV><FONT size=1>Broadband Network Research Center,</FONT></DIV>
<DIV><FONT size=1>State Key Laboratory of Networking and Switching Technology, 
</FONT></DIV>
<DIV><FONT size=1>Beijing University of Posts and Telecommunications, Beijing, 
China</FONT></DIV>
<DIV><FONT size=1></FONT>&nbsp;</DIV>
<DIV><FONT size=1>Email:zfhu2001@gmail.com</FONT></DIV>
<DIV>
<DIV><FONT 
size=1>Tel:86+13811892137</FONT></DIV></DIV></DIV></DIV></SPAN></FONT></DIV></FONT></BODY></HTML>

--=====003_Dragon215848251840_=====--



From mkomu@cs.hut.fi  Thu Nov  4 03:47:32 2010
Return-Path: <mkomu@cs.hut.fi>
X-Original-To: hipsec@core3.amsl.com
Delivered-To: hipsec@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id CCA673A69D1 for <hipsec@core3.amsl.com>; Thu,  4 Nov 2010 03:47:32 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.599
X-Spam-Level: 
X-Spam-Status: No, score=-6.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id WQGuZHvd6tPJ for <hipsec@core3.amsl.com>; Thu,  4 Nov 2010 03:47:32 -0700 (PDT)
Received: from mail.cs.hut.fi (mail.cs.hut.fi [130.233.192.7]) by core3.amsl.com (Postfix) with ESMTP id EEBE43A69B7 for <hipsec@ietf.org>; Thu,  4 Nov 2010 03:47:31 -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 1PDxM3-0002IS-Uu for hipsec@ietf.org; Thu, 04 Nov 2010 12:47:40 +0200
Message-ID: <4CD28F4A.5070106@cs.hut.fi>
Date: Thu, 04 Nov 2010 12:47:38 +0200
From: Miika Komu <mkomu@cs.hut.fi>
User-Agent: Mozilla/5.0 (X11; U; Linux x86_64; en-US; rv:1.9.1.15) Gecko/20101027 Thunderbird/3.0.10
MIME-Version: 1.0
To: hipsec@ietf.org
References: <201011041748233287181@163.com>
In-Reply-To: <201011041748233287181@163.com>
Content-Type: text/plain; charset=GB2312
Content-Transfer-Encoding: 7bit
Subject: Re: [Hipsec] HIP Registration problem
X-BeenThere: hipsec@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: "This is the official IETF Mailing List for the HIP Working Group." <hipsec.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/hipsec>, <mailto:hipsec-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/hipsec>
List-Post: <mailto:hipsec@ietf.org>
List-Help: <mailto:hipsec-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/hipsec>, <mailto:hipsec-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 04 Nov 2010 10:47:32 -0000

On 11/04/2010 11:48 AM, zfhu2001 wrote:
> Hi all,
> As we know, a mobile node registers its HIP and IP address binding to a 
> correponding RVS server, but now I'm wondering whether the MN will 
> register to a new RVS if a mobile node moves to another network and 
> simultaneously its previous RVS server does not work any more. Or does 
> HIP provide a mechanisim as DAAP of MIP to detect the serving RVS server 
> of its home area?
> Thanks.
> 2010-11-04

Hi,

there's no such thing as "home agent" or "home area" in HIP. This is one
of the differences to MIP. The same rendezvous server can be reused
independently of the current network using the UPDATE procedure.
Remember also that the rendezvous server forwards only the first I1 or
the first UPDATE packet, so it's still a light-weight operation even
though the latency be longer. The rendezvous server does not forward any
application payload.

Fault-tolerance for RVS may fall into the category of local policies
(?). Changing the "current" RVS requires also an update to the DNS
records. Another strategy could be just to publish multiple RVS servers
in the DNS and send packets to all of them (which ever happens to be alive).

From samu.varjonen@hiit.fi  Thu Nov  4 09:25:28 2010
Return-Path: <samu.varjonen@hiit.fi>
X-Original-To: hipsec@core3.amsl.com
Delivered-To: hipsec@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 44CE128C0F8 for <hipsec@core3.amsl.com>; Thu,  4 Nov 2010 09:25:28 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level: 
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id uIJswh0xKb0A for <hipsec@core3.amsl.com>; Thu,  4 Nov 2010 09:25:25 -0700 (PDT)
Received: from argo.otaverkko.fi (argo.otaverkko.fi [212.68.0.2]) by core3.amsl.com (Postfix) with ESMTP id BF60628C0ED for <hipsec@ietf.org>; Thu,  4 Nov 2010 09:25:18 -0700 (PDT)
Received: from [80.186.63.205] (80-186-63-205.elisa-mobile.fi [80.186.63.205]) by argo.otaverkko.fi (Postfix) with ESMTP id 99CD525ED2A; Thu,  4 Nov 2010 18:25:14 +0200 (EET)
Message-ID: <4CD2DE58.8060202@hiit.fi>
Date: Thu, 04 Nov 2010 18:24:56 +0200
From: Samu Varjonen <samu.varjonen@hiit.fi>
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.9.1.12) Gecko/20100915 Thunderbird/3.0.8
MIME-Version: 1.0
To: Ari Keranen <ari.keranen@nomadiclab.com>, HIP <hipsec@ietf.org>
References: <20100923104502.A5CA73A6951@core3.amsl.com>	<4C9B337D.4000904@hiit.fi> <4C9B580A.4080808@nomadiclab.com>	<4CA06B6E.3060308@hiit.fi> <4CA34445.6040007@nomadiclab.com>	<4CA97A29.2080204@hiit.fi> <4CA97A85.4070709@hiit.fi>
In-Reply-To: <4CA97A85.4070709@hiit.fi>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Subject: Re: [Hipsec] draft-ietf-hip-cert-04 review
X-BeenThere: hipsec@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: "This is the official IETF Mailing List for the HIP Working Group." <hipsec.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/hipsec>, <mailto:hipsec-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/hipsec>
List-Post: <mailto:hipsec@ietf.org>
List-Help: <mailto:hipsec-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/hipsec>, <mailto:hipsec-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 04 Nov 2010 16:25:28 -0000

Hi,

Comments in-line...

On 10/04/2010 09:56 AM, Samu Varjonen wrote:
> Hi,
>
> Forgot to CC the list :)
>
> On 04/10/10 09:54, Samu Varjonen wrote:
>> On 29/09/10 16:51, Ari Keranen wrote:
>>> On 09/27/2010 01:01 PM, Samu Varjonen wrote:
>>>> On 23/09/10 16:37, Ari Keranen wrote:
>>>>> Format:
>>>>> Issuer: CN=hit-of-host
>>>>> Subject: CN=hit-of-host
>>>>>
>>>>> X509v3 extensions:
>>>>> X509v3 Issuer Alternative Name:
>>>>> IP Address:HIT-OF-HOST
>>>>> X509v3 Subject Alternative Name:
>>>>> IP Address:HIT-OF-HOST
>>>>>
>>>>> From here (and especially from the example) one gets the idea that the
>>>>> exact same information would be there 4 times. The issuer and subject
>>>>> can be (and often are?) different, right?
>>>>>
>>>>
>>>> The answer is above the example.
>>>>
>>>> "
>>>> If only HIP information is presented as either
>>>> the issuer or the subject the HIT is also placed into the respective
>>>> entity's DNs Common Name (CN) section in a colon delimited
>>>> presentation format. *Inclusion of CN is not necessary if DN contains
>>>> any other information.* It is RECOMMENDED to use the FQDN/NAI from
>>>> the hosts HOST_ID parameter in the DN if one exists.
>>>> "
>>>>
>>>> Do you think that this needs clarification?
>>>
>>> Yes, that would help.
>>>
>>> For example, what is meant by "only HIP information" is not really
>>> clear. Also I guess it should say "DN's" instead of "DNs" in the text.
>>> And there isn't any text on whether the issuer and subject HITs can be
>>> different (the text and example implies that they're always identical).
>>>
>>
>> OK, I can change the example to contain different HITs as issuer and
>> subject and clarify the paragraph.
>>

Here is the new version:

http://www.cs.helsinki.fi/u/sklvarjo/draft-ietf-hip-cert-04-pre04.txt

Can you check out especially Section 3. to see if the clarifications (for the 
above) work for you or if you have other suggestion for improving the document.

Thanks, Samu

>>>>>
>>>>> 6. Error signaling
>>>>>
>>>>> INVALID_CERTIFICATE 50
>>>>>
>>>>> Sent in response to a failed verification of a certificate.
>>>>> Notification Data contains 4 octets, in order Cert group,
>>>>> Cert count, Cert ID, and Cert type of the certificate
>>>>> parameter that caused the failure.
>>>>>
>>>>> How does the verifier determine which certificate (if there are more
>>>>> than one) caused the failure? Isn't it rather always so that none of
>>>>> the
>>>>> given certificates were valid (for this particular use)?
>>>>>
>>>>
>>>> In most cases I would say that one failed verification fails the
>>>> verification of the whole chain. But in a case where you send two
>>>> certificates/chains for different services and the other one fails you
>>>> might want to know which failed. Registration extensions the REG_FAILED
>>>> would reveal the failed chain. I would like to leave the possibility to
>>>> tell the specific failed certificate for HIP-aware applications. So,
>>>> maybe it should say that the Notification Data MAY contain 4 octets...
>>>
>>> OK. But what if you send three (or more) certificates?
>>
>> If I followed you correctly the Notification Data would need more than 4
>> octets to inform about more than one failed certificate in one or more
>> groups. How about "the Notification Data MAY contain n groups of 4
>> octets (n calculated from the length of the parameter) . The group
>> contains octets in the following order: Cert group, Cert count, Cert ID,
>> and Cert type."
>>
>> Any other suggestions/ideas?
>>
>>>
>>>
>>> Cheers,
>>> Ari
>>
>
> _______________________________________________
> Hipsec mailing list
> Hipsec@ietf.org
> https://www.ietf.org/mailman/listinfo/hipsec


From ari.keranen@nomadiclab.com  Sat Nov  6 17:53:18 2010
Return-Path: <ari.keranen@nomadiclab.com>
X-Original-To: hipsec@core3.amsl.com
Delivered-To: hipsec@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id E3CE528C0CF for <hipsec@core3.amsl.com>; Sat,  6 Nov 2010 17:53:17 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level: 
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id FjzVCqray3HH for <hipsec@core3.amsl.com>; Sat,  6 Nov 2010 17:53:16 -0700 (PDT)
Received: from gw.nomadiclab.com (unknown [IPv6:2001:14b8:400:101::2]) by core3.amsl.com (Postfix) with ESMTP id 7EDB03A6946 for <hipsec@ietf.org>; Sat,  6 Nov 2010 17:53:15 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by gw.nomadiclab.com (Postfix) with ESMTP id AC47A4E6D7; Sun,  7 Nov 2010 01:48:34 +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 h4jqwI3xf7aV; Sun,  7 Nov 2010 01:48:33 +0200 (EET)
Received: from [127.0.0.1] (localhost [IPv6:::1]) by gw.nomadiclab.com (Postfix) with ESMTP id 3B63F4E6BD; Sun,  7 Nov 2010 01:48:28 +0200 (EET)
Message-ID: <4CD5F888.6010806@nomadiclab.com>
Date: Sun, 07 Nov 2010 08:53:28 +0800
From: Ari Keranen <ari.keranen@nomadiclab.com>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.1; fi; rv:1.9.2.8) Gecko/20100802 Lightning/1.0b2 Thunderbird/3.1.2
MIME-Version: 1.0
To: Samu Varjonen <samu.varjonen@hiit.fi>
References: <20100923104502.A5CA73A6951@core3.amsl.com>	<4C9B337D.4000904@hiit.fi> <4C9B580A.4080808@nomadiclab.com>	<4CA06B6E.3060308@hiit.fi> <4CA34445.6040007@nomadiclab.com>	<4CA97A29.2080204@hiit.fi> <4CA97A85.4070709@hiit.fi> <4CD2DE58.8060202@hiit.fi>
In-Reply-To: <4CD2DE58.8060202@hiit.fi>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Cc: HIP <hipsec@ietf.org>
Subject: Re: [Hipsec] draft-ietf-hip-cert-04 review
X-BeenThere: hipsec@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: "This is the official IETF Mailing List for the HIP Working Group." <hipsec.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/hipsec>, <mailto:hipsec-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/hipsec>
List-Post: <mailto:hipsec@ietf.org>
List-Help: <mailto:hipsec-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/hipsec>, <mailto:hipsec-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sun, 07 Nov 2010 00:53:18 -0000

Hi Samu,

5.11.2010 0:24, Samu Varjonen kirjoitti:
> On 10/04/2010 09:56 AM, Samu Varjonen wrote:
>> On 04/10/10 09:54, Samu Varjonen wrote:
>>> On 29/09/10 16:51, Ari Keranen wrote:
>>>> On 09/27/2010 01:01 PM, Samu Varjonen wrote:
>>>>> On 23/09/10 16:37, Ari Keranen wrote:
>>>>>> Format:
>>>>>> Issuer: CN=hit-of-host
>>>>>> Subject: CN=hit-of-host
>>>>>>
>>>>>> X509v3 extensions:
>>>>>> X509v3 Issuer Alternative Name:
>>>>>> IP Address:HIT-OF-HOST
>>>>>> X509v3 Subject Alternative Name:
>>>>>> IP Address:HIT-OF-HOST
>>>>>>
>>>>>> From here (and especially from the example) one gets the idea that
>>>>>> the
>>>>>> exact same information would be there 4 times. The issuer and subject
>>>>>> can be (and often are?) different, right?
>>>>>>
>>>>>
>>>>> The answer is above the example.
>>>>>
>>>>> "
>>>>> If only HIP information is presented as either
>>>>> the issuer or the subject the HIT is also placed into the respective
>>>>> entity's DNs Common Name (CN) section in a colon delimited
>>>>> presentation format. *Inclusion of CN is not necessary if DN contains
>>>>> any other information.* It is RECOMMENDED to use the FQDN/NAI from
>>>>> the hosts HOST_ID parameter in the DN if one exists.
>>>>> "
>>>>>
>>>>> Do you think that this needs clarification?
>>>>
>>>> Yes, that would help.
>>>>
>>>> For example, what is meant by "only HIP information" is not really
>>>> clear. Also I guess it should say "DN's" instead of "DNs" in the text.
>>>> And there isn't any text on whether the issuer and subject HITs can be
>>>> different (the text and example implies that they're always identical).
>>>>
>>>
>>> OK, I can change the example to contain different HITs as issuer and
>>> subject and clarify the paragraph.
>>>
>
> Here is the new version:
>
> http://www.cs.helsinki.fi/u/sklvarjo/draft-ietf-hip-cert-04-pre04.txt
>
> Can you check out especially Section 3. to see if the clarifications
> (for the above) work for you or if you have other suggestion for
> improving the document.

Looks better now, thanks! Few comments still:

In the example, it would be better to use "Format of [...]" instead of 
just "Format".

I mentioned about this already earlier in this thread (recommended 
RFC5952), but should you be more specific of the presentation format or 
is anything OK? Or is there some reason not to recommend anything for this?


Cheers,
Ari

From zfhu2001@163.com  Sun Nov  7 19:04:33 2010
Return-Path: <zfhu2001@163.com>
X-Original-To: hipsec@core3.amsl.com
Delivered-To: hipsec@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 852CC3A6951 for <hipsec@core3.amsl.com>; Sun,  7 Nov 2010 19:04:25 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 1.61
X-Spam-Level: *
X-Spam-Status: No, score=1.61 tagged_above=-999 required=5 tests=[BAYES_50=0.001, FROM_EXCESS_BASE64=1.456, HTML_MESSAGE=0.001, SARE_SUB_ENC_UTF8=0.152]
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 SrptgZMbNGjR for <hipsec@core3.amsl.com>; Sun,  7 Nov 2010 19:04:21 -0800 (PST)
Received: from m50-133.163.com (m50-133.163.com [123.125.50.133]) by core3.amsl.com (Postfix) with ESMTP id 92F5D3A672F for <hipsec@ietf.org>; Sun,  7 Nov 2010 19:04:14 -0800 (PST)
Received: from ZFHU-BUTP (unknown [123.116.137.174]) by smtp3 (Coremail) with SMTP id DdGowKBbDIWjaNdMFBv_AA--.288S2; Mon, 08 Nov 2010 11:04:05 +0800 (CST)
Date: Mon, 8 Nov 2010 11:03:58 +0800
From: "=?utf-8?B?WmhhbmdmZW5nIEhV?=" <zfhu2001@163.com>
To: "=?utf-8?B?TWlpa2EgS29tdQ==?=" <mkomu@cs.hut.fi>, "=?utf-8?B?aGlwc2Vj?=" <hipsec@ietf.org>
References: <201011041748233287181@163.com>
Message-ID: <201011081103570007893@163.com>
X-mailer: Foxmail 6, 15, 201, 23 [cn]
Mime-Version: 1.0
Content-Type: multipart/alternative; boundary="=====003_Dragon350103238280_====="
X-CM-TRANSID: DdGowKBbDIWjaNdMFBv_AA--.288S2
X-Coremail-Antispam: 1Uf129KBjvJXoW7Cr15Zr48tw1UWF48CF47CFg_yoW8KFWkpF W5Kay5KrWkGryrXw18ArWIqr4jvFWxXr4UWas5Grn7CFZ0qw1jvr1kGr1Y9a4UurWfGF1F vF1jg3yrZ3WDJw7anT9S1TB71UUUUUUqnTZGkaVYY2UrUUUUjbIjqfuFe4nvWSU5nxnvy2 9KBjDUYxBIdaVFxhVjvjDU0xZFpf9x07jcgAwUUUUU=
X-CM-SenderInfo: p2ik3jqqqrqiywtou0bp/1tbiOQKDiUjh4yUE+AAAsi
Cc: =?utf-8?B?5p2c5paH6Z2Z?= <lxadj@126.com>
Subject: Re: [Hipsec] =?utf-8?q?HIP_Registration_problem?=
X-BeenThere: hipsec@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: "This is the official IETF Mailing List for the HIP Working Group." <hipsec.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/hipsec>, <mailto:hipsec-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/hipsec>
List-Post: <mailto:hipsec@ietf.org>
List-Help: <mailto:hipsec-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/hipsec>, <mailto:hipsec-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 08 Nov 2010 03:04:33 -0000

This is a multi-part message in MIME format.

--=====003_Dragon350103238280_=====
Content-Type: text/plain;
	charset="utf-8"
Content-Transfer-Encoding: base64

SGksDQp5ZXMsIHRoYXQncyB0aGUgdHJ1dGguIFNpbmNlIEhJUCBkb2VzIHByb3ZpZGUgYSBtZWNo
YW5pc20gYXMgREFBUCBvZiBNSVAsIHdlIGFyZSBqdXN0IGNvbnNpZGVyaW5nIGEgbWV0aG9kIG9m
IHByb3ZpZGluZyBmYXVsdCB0b3JsZXJhbmNlIGZvciBSVlMgaW4gSElQLiBGb3Igc29tZSBtb2Jp
bGUgbm9kZXMsIHRoZSBoaWdoIGF2YWlsYWJpbGl0eSBpcyB2ZXJ5IGltcG9ydGFudCwgaG93ZXZl
ciB0aGUgYXZhaWxhYmlsaXR5IG9mIHRoZXNlIG1vYmlsZSBub2RlcyBpcyBtb3N0bHkgZGVjaWRl
ZCBieSB0aGUgYXZhaWxhYmlsaXR5IG9mIHRoZSBjb3JyZXNwb25kaW5nIFJWUyB3aG8gc2VydmVz
IHRoZW0uIFRoaXMgUlZTIGZhdWx0IHRvcmxlcmFuY2UgY2FuIG5vdCBiZSBlYXNpbHkgaW1wbGVt
ZW50ZWQgdGhyb3VnaCB1cGRhdGluZyB0aGUgZW50cmllcyBpbiBETlMsIGJlY2F1c2Ugb2YgdGhl
IGhpZ2ggbGF0ZW5jeSBhbmQgdGhlIGNhY2hlIG1lY2hhbmlzbSB1c2VkIGluIEROUy4NCg0KDQoN
CjIwMTAtMTEtMDggDQoNCg0KDQogIA0KWmhhbmdmZW5nIEhVLCBQaEQgY2FuZGlkYXRlIG9mDQpC
cm9hZGJhbmQgTmV0d29yayBSZXNlYXJjaCBDZW50ZXIsDQpTdGF0ZSBLZXkgTGFib3JhdG9yeSBv
ZiBOZXR3b3JraW5nIGFuZCBTd2l0Y2hpbmcgVGVjaG5vbG9neSwgDQpCZWlqaW5nIFVuaXZlcnNp
dHkgb2YgUG9zdHMgYW5kIFRlbGVjb21tdW5pY2F0aW9ucywgQmVpamluZywgQ2hpbmENCg0KRW1h
aWw6emZodTIwMDFAZ21haWwuY29tDQpUZWw6ODYrMTM4MTE4OTIxMzcNCg0KDQoNCuWPkeS7tuS6
uu+8miBNaWlrYSBLb211IA0K5Y+R6YCB5pe26Ze077yaIDIwMTAtMTEtMDQgIDE4OjQ3OjQ1IA0K
5pS25Lu25Lq677yaIGhpcHNlYyANCuaKhOmAge+8miANCuS4u+mimO+8miBSZTogW0hpcHNlY10g
SElQIFJlZ2lzdHJhdGlvbiBwcm9ibGVtIA0KIA0KT24gMTEvMDQvMjAxMCAxMTo0OCBBTSwgemZo
dTIwMDEgd3JvdGU6DQo+IEhpIGFsbCwNCj4gQXMgd2Uga25vdywgYSBtb2JpbGUgbm9kZSByZWdp
c3RlcnMgaXRzIEhJUCBhbmQgSVAgYWRkcmVzcyBiaW5kaW5nIHRvIGEgDQo+IGNvcnJlcG9uZGlu
ZyBSVlMgc2VydmVyLCBidXQgbm93IEknbSB3b25kZXJpbmcgd2hldGhlciB0aGUgTU4gd2lsbCAN
Cj4gcmVnaXN0ZXIgdG8gYSBuZXcgUlZTIGlmIGEgbW9iaWxlIG5vZGUgbW92ZXMgdG8gYW5vdGhl
ciBuZXR3b3JrIGFuZCANCj4gc2ltdWx0YW5lb3VzbHkgaXRzIHByZXZpb3VzIFJWUyBzZXJ2ZXIg
ZG9lcyBub3Qgd29yayBhbnkgbW9yZS4gT3IgZG9lcyANCj4gSElQIHByb3ZpZGUgYSBtZWNoYW5p
c2ltIGFzIERBQVAgb2YgTUlQIHRvIGRldGVjdCB0aGUgc2VydmluZyBSVlMgc2VydmVyIA0KPiBv
ZiBpdHMgaG9tZSBhcmVhPw0KPiBUaGFua3MuDQo+IDIwMTAtMTEtMDQNCkhpLA0KdGhlcmUncyBu
byBzdWNoIHRoaW5nIGFzICJob21lIGFnZW50IiBvciAiaG9tZSBhcmVhIiBpbiBISVAuIFRoaXMg
aXMgb25lDQpvZiB0aGUgZGlmZmVyZW5jZXMgdG8gTUlQLiBUaGUgc2FtZSByZW5kZXp2b3VzIHNl
cnZlciBjYW4gYmUgcmV1c2VkDQppbmRlcGVuZGVudGx5IG9mIHRoZSBjdXJyZW50IG5ldHdvcmsg
dXNpbmcgdGhlIFVQREFURSBwcm9jZWR1cmUuDQpSZW1lbWJlciBhbHNvIHRoYXQgdGhlIHJlbmRl
enZvdXMgc2VydmVyIGZvcndhcmRzIG9ubHkgdGhlIGZpcnN0IEkxIG9yDQp0aGUgZmlyc3QgVVBE
QVRFIHBhY2tldCwgc28gaXQncyBzdGlsbCBhIGxpZ2h0LXdlaWdodCBvcGVyYXRpb24gZXZlbg0K
dGhvdWdoIHRoZSBsYXRlbmN5IGJlIGxvbmdlci4gVGhlIHJlbmRlenZvdXMgc2VydmVyIGRvZXMg
bm90IGZvcndhcmQgYW55DQphcHBsaWNhdGlvbiBwYXlsb2FkLg0KRmF1bHQtdG9sZXJhbmNlIGZv
ciBSVlMgbWF5IGZhbGwgaW50byB0aGUgY2F0ZWdvcnkgb2YgbG9jYWwgcG9saWNpZXMNCig/KS4g
Q2hhbmdpbmcgdGhlICJjdXJyZW50IiBSVlMgcmVxdWlyZXMgYWxzbyBhbiB1cGRhdGUgdG8gdGhl
IEROUw0KcmVjb3Jkcy4gQW5vdGhlciBzdHJhdGVneSBjb3VsZCBiZSBqdXN0IHRvIHB1Ymxpc2gg
bXVsdGlwbGUgUlZTIHNlcnZlcnMNCmluIHRoZSBETlMgYW5kIHNlbmQgcGFja2V0cyB0byBhbGwg
b2YgdGhlbSAod2hpY2ggZXZlciBoYXBwZW5zIHRvIGJlIGFsaXZlKS4NCl9fX19fX19fX19fX19f
X19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fDQpIaXBzZWMgbWFpbGluZyBsaXN0DQpI
aXBzZWNAaWV0Zi5vcmcNCmh0dHBzOi8vd3d3LmlldGYub3JnL21haWxtYW4vbGlzdGluZm8vaGlw
c2VjDQrDlMOawrTCq8OIw6vCtcOEw5PDisK8w77DlsOQw47CtMK3wqLDj8OWwrLCocK2wr7CocKj
DQrCvMOswrLDqcK5wqTCvsOfwqPCukFWRyAtIHd3dy5hdmcuY29tIA0KwrDDpsKxwr7Co8K6OS4w
Ljg2NSAvIMKywqHCtsK+w4rDvcK+w53Cv8OiwqPCujI3MS4xLjEvMzIzNSAtIMK3wqLCssK8w4jD
lcOGw5rCo8K6MTEvMDMvMTAgMTY6MzY6MDANCg==

--=====003_Dragon350103238280_=====
Content-Type: text/html;
	charset="utf-8"
Content-Transfer-Encoding: base64

77u/PCFET0NUWVBFIEhUTUwgUFVCTElDICItLy9XM0MvL0RURCBIVE1MIDQuMCBUcmFuc2l0aW9u
YWwvL0VOIj4NCjxIVE1MPjxIRUFEPg0KPE1FVEEgY29udGVudD0idGV4dC9odG1sOyBjaGFyc2V0
PXV0Zi04IiBodHRwLWVxdWl2PUNvbnRlbnQtVHlwZT4NCjxNRVRBIG5hbWU9R0VORVJBVE9SIGNv
bnRlbnQ9Ik1TSFRNTCA4LjAwLjYwMDEuMTg5NzUiPg0KPFNUWUxFPkBmb250LWZhY2Ugew0KCWZv
bnQtZmFtaWx5OiDlrovkvZM7DQp9DQpAZm9udC1mYWNlIHsNCglmb250LWZhbWlseTogVmVyZGFu
YTsNCn0NCkBmb250LWZhY2Ugew0KCWZvbnQtZmFtaWx5OiBA5a6L5L2TOw0KfQ0KQHBhZ2UgU2Vj
dGlvbjEge3NpemU6IDU5NS4zcHQgODQxLjlwdDsgbWFyZ2luOiA3Mi4wcHQgOTAuMHB0IDcyLjBw
dCA5MC4wcHQ7IGxheW91dC1ncmlkOiAxNS42cHQ7IH0NClAuTXNvTm9ybWFsIHsNCglURVhULUpV
U1RJRlk6IGludGVyLWlkZW9ncmFwaDsgVEVYVC1BTElHTjoganVzdGlmeTsgTUFSR0lOOiAwY20g
MGNtIDBwdDsgRk9OVC1GQU1JTFk6ICJUaW1lcyBOZXcgUm9tYW4iOyBGT05ULVNJWkU6IDEwLjVw
dA0KfQ0KTEkuTXNvTm9ybWFsIHsNCglURVhULUpVU1RJRlk6IGludGVyLWlkZW9ncmFwaDsgVEVY
VC1BTElHTjoganVzdGlmeTsgTUFSR0lOOiAwY20gMGNtIDBwdDsgRk9OVC1GQU1JTFk6ICJUaW1l
cyBOZXcgUm9tYW4iOyBGT05ULVNJWkU6IDEwLjVwdA0KfQ0KRElWLk1zb05vcm1hbCB7DQoJVEVY
VC1KVVNUSUZZOiBpbnRlci1pZGVvZ3JhcGg7IFRFWFQtQUxJR046IGp1c3RpZnk7IE1BUkdJTjog
MGNtIDBjbSAwcHQ7IEZPTlQtRkFNSUxZOiAiVGltZXMgTmV3IFJvbWFuIjsgRk9OVC1TSVpFOiAx
MC41cHQNCn0NCkE6bGluayB7DQoJQ09MT1I6IGJsdWU7IFRFWFQtREVDT1JBVElPTjogdW5kZXJs
aW5lDQp9DQpTUEFOLk1zb0h5cGVybGluayB7DQoJQ09MT1I6IGJsdWU7IFRFWFQtREVDT1JBVElP
TjogdW5kZXJsaW5lDQp9DQpBOnZpc2l0ZWQgew0KCUNPTE9SOiBwdXJwbGU7IFRFWFQtREVDT1JB
VElPTjogdW5kZXJsaW5lDQp9DQpTUEFOLk1zb0h5cGVybGlua0ZvbGxvd2VkIHsNCglDT0xPUjog
cHVycGxlOyBURVhULURFQ09SQVRJT046IHVuZGVybGluZQ0KfQ0KU1BBTi5FbWFpbFN0eWxlMTcg
ew0KCUZPTlQtU1RZTEU6IG5vcm1hbDsgRk9OVC1GQU1JTFk6IFZlcmRhbmE7IENPTE9SOiB3aW5k
b3d0ZXh0OyBGT05ULVdFSUdIVDogbm9ybWFsOyBURVhULURFQ09SQVRJT046IG5vbmU7IG1zby1z
dHlsZS10eXBlOiBwZXJzb25hbC1jb21wb3NlDQp9DQpESVYuU2VjdGlvbjEgew0KCXBhZ2U6IFNl
Y3Rpb24xDQp9DQpVTktOT1dOIHsNCglGT05ULVNJWkU6IDEwcHQNCn0NCkJMT0NLUVVPVEUgew0K
CU1BUkdJTi1UT1A6IDBweDsgTUFSR0lOLUJPVFRPTTogMHB4OyBNQVJHSU4tTEVGVDogMmVtDQp9
DQpPTCB7DQoJTUFSR0lOLVRPUDogMHB4OyBNQVJHSU4tQk9UVE9NOiAwcHgNCn0NClVMIHsNCglN
QVJHSU4tVE9QOiAwcHg7IE1BUkdJTi1CT1RUT006IDBweA0KfQ0KPC9TVFlMRT4NCjwvSEVBRD4N
CjxCT0RZIHN0eWxlPSJNQVJHSU46IDEwcHg7IEZPTlQtRkFNSUxZOiB2ZXJkYW5hOyBGT05ULVNJ
WkU6IDEwcHQiPg0KPERJVj48Rk9OVCBjb2xvcj0jMDAwMDgwIHNpemU9Mj5IaSw8L0ZPTlQ+PC9E
SVY+DQo8RElWPjxGT05UIGNvbG9yPSMwMDAwODA+eWVzLCB0aGF0J3MgdGhlIHRydXRoLiBTaW5j
ZSBISVAgZG9lcyBwcm92aWRlIGEgDQptZWNoYW5pc20gYXMgREFBUCBvZiBNSVAsIHdlIGFyZSBq
dXN0IGNvbnNpZGVyaW5nIGEgbWV0aG9kIG9mIHByb3ZpZGluZyBmYXVsdCANCnRvcmxlcmFuY2Ug
Zm9yIFJWUyBpbiBISVAuIEZvciBzb21lIG1vYmlsZSBub2RlcywgdGhlIGhpZ2ggYXZhaWxhYmls
aXR5IGlzIHZlcnkgDQppbXBvcnRhbnQsIGhvd2V2ZXIgdGhlIGF2YWlsYWJpbGl0eSBvZiB0aGVz
ZSBtb2JpbGUgbm9kZXMgaXMgbW9zdGx5IGRlY2lkZWQgYnkgDQp0aGUgYXZhaWxhYmlsaXR5IG9m
IHRoZSBjb3JyZXNwb25kaW5nIFJWUyB3aG8gc2VydmVzIHRoZW0uIFRoaXMgUlZTIGZhdWx0IA0K
dG9ybGVyYW5jZSBjYW4gbm90IGJlIGVhc2lseSBpbXBsZW1lbnRlZCB0aHJvdWdoIHVwZGF0aW5n
IHRoZSBlbnRyaWVzIGluIEROUywgDQpiZWNhdXNlIG9mIHRoZSBoaWdoIGxhdGVuY3kgYW5kIHRo
ZSBjYWNoZSBtZWNoYW5pc20gdXNlZCBpbiBETlMuPC9GT05UPjwvRElWPg0KPERJVj48Rk9OVCBj
b2xvcj0jMDAwMDgwPjwvRk9OVD4mbmJzcDs8L0RJVj4NCjxESVY+PEZPTlQgY29sb3I9IzAwMDA4
MCBzaXplPTI+PC9GT05UPiZuYnNwOzwvRElWPg0KPERJVj48Rk9OVCBjb2xvcj0jMDAwMDgwIHNp
emU9Mj48L0ZPTlQ+Jm5ic3A7PC9ESVY+DQo8RElWPjxGT05UIGNvbG9yPSNjMGMwYzAgc2l6ZT0y
PjIwMTAtMTEtMDggPC9GT05UPjwvRElWPjxGT05UIGNvbG9yPSMwMDAwODAgDQpzaXplPTI+DQo8
SFIgc3R5bGU9IldJRFRIOiAxMDBweCIgYWxpZ249bGVmdCBjb2xvcj0jYjVjNGRmIFNJWkU9MT4N
CjwvRk9OVD4NCjxESVY+PEZPTlQgY29sb3I9I2MwYzBjMCBzaXplPTI+PFNQQU4+DQo8RElWPg0K
PERJVj48Rk9OVCBzaXplPTI+PC9GT05UPiZuYnNwOyANCjxESVY+PEZPTlQgc2l6ZT0xPlpoYW5n
ZmVuZyBIVSwgUGhEJm5ic3A7Y2FuZGlkYXRlIG9mPC9GT05UPjwvRElWPg0KPERJVj48Rk9OVCBz
aXplPTE+QnJvYWRiYW5kIE5ldHdvcmsgUmVzZWFyY2ggQ2VudGVyLDwvRk9OVD48L0RJVj4NCjxE
SVY+PEZPTlQgc2l6ZT0xPlN0YXRlIEtleSBMYWJvcmF0b3J5IG9mIE5ldHdvcmtpbmcgYW5kIFN3
aXRjaGluZyBUZWNobm9sb2d5LCANCjwvRk9OVD48L0RJVj4NCjxESVY+PEZPTlQgc2l6ZT0xPkJl
aWppbmcgVW5pdmVyc2l0eSBvZiBQb3N0cyBhbmQgVGVsZWNvbW11bmljYXRpb25zLCBCZWlqaW5n
LCANCkNoaW5hPC9GT05UPjwvRElWPg0KPERJVj48Rk9OVCBzaXplPTE+PC9GT05UPiZuYnNwOzwv
RElWPg0KPERJVj48Rk9OVCBzaXplPTE+RW1haWw6emZodTIwMDFAZ21haWwuY29tPC9GT05UPjwv
RElWPg0KPERJVj4NCjxESVY+PEZPTlQgDQpzaXplPTE+VGVsOjg2KzEzODExODkyMTM3PC9GT05U
PjwvRElWPjwvRElWPjwvRElWPjwvRElWPjwvU1BBTj48L0ZPTlQ+PC9ESVY+DQo8SFIgY29sb3I9
I2I1YzRkZiBTSVpFPTE+DQoNCjxESVY+PEZPTlQgc2l6ZT0yPjxTVFJPTkc+5Y+R5Lu25Lq677ya
PC9TVFJPTkc+IE1paWthIEtvbXUgPC9GT05UPjwvRElWPg0KPERJVj48Rk9OVCBzaXplPTI+PFNU
Uk9ORz7lj5HpgIHml7bpl7TvvJo8L1NUUk9ORz4gMjAxMC0xMS0wNCZuYnNwOyAxODo0Nzo0NSA8
L0ZPTlQ+PC9ESVY+DQo8RElWPjxGT05UIHNpemU9Mj48U1RST05HPuaUtuS7tuS6uu+8mjwvU1RS
T05HPiBoaXBzZWMgPC9GT05UPjwvRElWPg0KPERJVj48Rk9OVCBzaXplPTI+PFNUUk9ORz7mioTp
gIHvvJo8L1NUUk9ORz4gPC9GT05UPjwvRElWPg0KPERJVj48Rk9OVCBzaXplPTI+PFNUUk9ORz7k
uLvpopjvvJo8L1NUUk9ORz4gUmU6IFtIaXBzZWNdIEhJUCBSZWdpc3RyYXRpb24gcHJvYmxlbSAN
CjwvRk9OVD48L0RJVj4NCjxESVY+PEZPTlQgc2l6ZT0yPjwvRk9OVD4gPC9ESVY+DQo8RElWPjxG
T05UIHNpemU9Mj4NCjxESVY+T24mbmJzcDsxMS8wNC8yMDEwJm5ic3A7MTE6NDgmbmJzcDtBTSwm
bmJzcDt6Zmh1MjAwMSZuYnNwO3dyb3RlOjwvRElWPg0KPERJVj4mZ3Q7Jm5ic3A7SGkmbmJzcDth
bGwsPC9ESVY+DQo8RElWPiZndDsmbmJzcDtBcyZuYnNwO3dlJm5ic3A7a25vdywmbmJzcDthJm5i
c3A7bW9iaWxlJm5ic3A7bm9kZSZuYnNwO3JlZ2lzdGVycyZuYnNwO2l0cyZuYnNwO0hJUCZuYnNw
O2FuZCZuYnNwO0lQJm5ic3A7YWRkcmVzcyZuYnNwO2JpbmRpbmcmbmJzcDt0byZuYnNwO2EmbmJz
cDs8L0RJVj4NCjxESVY+Jmd0OyZuYnNwO2NvcnJlcG9uZGluZyZuYnNwO1JWUyZuYnNwO3NlcnZl
ciwmbmJzcDtidXQmbmJzcDtub3cmbmJzcDtJJ20mbmJzcDt3b25kZXJpbmcmbmJzcDt3aGV0aGVy
Jm5ic3A7dGhlJm5ic3A7TU4mbmJzcDt3aWxsJm5ic3A7PC9ESVY+DQo8RElWPiZndDsmbmJzcDty
ZWdpc3RlciZuYnNwO3RvJm5ic3A7YSZuYnNwO25ldyZuYnNwO1JWUyZuYnNwO2lmJm5ic3A7YSZu
YnNwO21vYmlsZSZuYnNwO25vZGUmbmJzcDttb3ZlcyZuYnNwO3RvJm5ic3A7YW5vdGhlciZuYnNw
O25ldHdvcmsmbmJzcDthbmQmbmJzcDs8L0RJVj4NCjxESVY+Jmd0OyZuYnNwO3NpbXVsdGFuZW91
c2x5Jm5ic3A7aXRzJm5ic3A7cHJldmlvdXMmbmJzcDtSVlMmbmJzcDtzZXJ2ZXImbmJzcDtkb2Vz
Jm5ic3A7bm90Jm5ic3A7d29yayZuYnNwO2FueSZuYnNwO21vcmUuJm5ic3A7T3ImbmJzcDtkb2Vz
Jm5ic3A7PC9ESVY+DQo8RElWPiZndDsmbmJzcDtISVAmbmJzcDtwcm92aWRlJm5ic3A7YSZuYnNw
O21lY2hhbmlzaW0mbmJzcDthcyZuYnNwO0RBQVAmbmJzcDtvZiZuYnNwO01JUCZuYnNwO3RvJm5i
c3A7ZGV0ZWN0Jm5ic3A7dGhlJm5ic3A7c2VydmluZyZuYnNwO1JWUyZuYnNwO3NlcnZlciZuYnNw
OzwvRElWPg0KPERJVj4mZ3Q7Jm5ic3A7b2YmbmJzcDtpdHMmbmJzcDtob21lJm5ic3A7YXJlYT88
L0RJVj4NCjxESVY+Jmd0OyZuYnNwO1RoYW5rcy48L0RJVj4NCjxESVY+Jmd0OyZuYnNwOzIwMTAt
MTEtMDQ8L0RJVj4NCjxESVY+PC9ESVY+DQo8RElWPkhpLDwvRElWPg0KPERJVj48L0RJVj4NCjxE
SVY+dGhlcmUncyZuYnNwO25vJm5ic3A7c3VjaCZuYnNwO3RoaW5nJm5ic3A7YXMmbmJzcDsiaG9t
ZSZuYnNwO2FnZW50IiZuYnNwO29yJm5ic3A7ImhvbWUmbmJzcDthcmVhIiZuYnNwO2luJm5ic3A7
SElQLiZuYnNwO1RoaXMmbmJzcDtpcyZuYnNwO29uZTwvRElWPg0KPERJVj5vZiZuYnNwO3RoZSZu
YnNwO2RpZmZlcmVuY2VzJm5ic3A7dG8mbmJzcDtNSVAuJm5ic3A7VGhlJm5ic3A7c2FtZSZuYnNw
O3JlbmRlenZvdXMmbmJzcDtzZXJ2ZXImbmJzcDtjYW4mbmJzcDtiZSZuYnNwO3JldXNlZDwvRElW
Pg0KPERJVj5pbmRlcGVuZGVudGx5Jm5ic3A7b2YmbmJzcDt0aGUmbmJzcDtjdXJyZW50Jm5ic3A7
bmV0d29yayZuYnNwO3VzaW5nJm5ic3A7dGhlJm5ic3A7VVBEQVRFJm5ic3A7cHJvY2VkdXJlLjwv
RElWPg0KPERJVj5SZW1lbWJlciZuYnNwO2Fsc28mbmJzcDt0aGF0Jm5ic3A7dGhlJm5ic3A7cmVu
ZGV6dm91cyZuYnNwO3NlcnZlciZuYnNwO2ZvcndhcmRzJm5ic3A7b25seSZuYnNwO3RoZSZuYnNw
O2ZpcnN0Jm5ic3A7STEmbmJzcDtvcjwvRElWPg0KPERJVj50aGUmbmJzcDtmaXJzdCZuYnNwO1VQ
REFURSZuYnNwO3BhY2tldCwmbmJzcDtzbyZuYnNwO2l0J3MmbmJzcDtzdGlsbCZuYnNwO2EmbmJz
cDtsaWdodC13ZWlnaHQmbmJzcDtvcGVyYXRpb24mbmJzcDtldmVuPC9ESVY+DQo8RElWPnRob3Vn
aCZuYnNwO3RoZSZuYnNwO2xhdGVuY3kmbmJzcDtiZSZuYnNwO2xvbmdlci4mbmJzcDtUaGUmbmJz
cDtyZW5kZXp2b3VzJm5ic3A7c2VydmVyJm5ic3A7ZG9lcyZuYnNwO25vdCZuYnNwO2ZvcndhcmQm
bmJzcDthbnk8L0RJVj4NCjxESVY+YXBwbGljYXRpb24mbmJzcDtwYXlsb2FkLjwvRElWPg0KPERJ
Vj48L0RJVj4NCjxESVY+RmF1bHQtdG9sZXJhbmNlJm5ic3A7Zm9yJm5ic3A7UlZTJm5ic3A7bWF5
Jm5ic3A7ZmFsbCZuYnNwO2ludG8mbmJzcDt0aGUmbmJzcDtjYXRlZ29yeSZuYnNwO29mJm5ic3A7
bG9jYWwmbmJzcDtwb2xpY2llczwvRElWPg0KPERJVj4oPykuJm5ic3A7Q2hhbmdpbmcmbmJzcDt0
aGUmbmJzcDsiY3VycmVudCImbmJzcDtSVlMmbmJzcDtyZXF1aXJlcyZuYnNwO2Fsc28mbmJzcDth
biZuYnNwO3VwZGF0ZSZuYnNwO3RvJm5ic3A7dGhlJm5ic3A7RE5TPC9ESVY+DQo8RElWPnJlY29y
ZHMuJm5ic3A7QW5vdGhlciZuYnNwO3N0cmF0ZWd5Jm5ic3A7Y291bGQmbmJzcDtiZSZuYnNwO2p1
c3QmbmJzcDt0byZuYnNwO3B1Ymxpc2gmbmJzcDttdWx0aXBsZSZuYnNwO1JWUyZuYnNwO3NlcnZl
cnM8L0RJVj4NCjxESVY+aW4mbmJzcDt0aGUmbmJzcDtETlMmbmJzcDthbmQmbmJzcDtzZW5kJm5i
c3A7cGFja2V0cyZuYnNwO3RvJm5ic3A7YWxsJm5ic3A7b2YmbmJzcDt0aGVtJm5ic3A7KHdoaWNo
Jm5ic3A7ZXZlciZuYnNwO2hhcHBlbnMmbmJzcDt0byZuYnNwO2JlJm5ic3A7YWxpdmUpLjwvRElW
Pg0KPERJVj5fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fXzwv
RElWPg0KPERJVj5IaXBzZWMmbmJzcDttYWlsaW5nJm5ic3A7bGlzdDwvRElWPg0KPERJVj5IaXBz
ZWNAaWV0Zi5vcmc8L0RJVj4NCjxESVY+aHR0cHM6Ly93d3cuaWV0Zi5vcmcvbWFpbG1hbi9saXN0
aW5mby9oaXBzZWM8L0RJVj4NCjxESVY+PC9ESVY+DQo8RElWPsOUw5rCtMKrw4jDq8K1w4TDk8OK
wrzDvsOWw5DDjsK0wrfCosOPw5bCssKhwrbCvsKhwqM8L0RJVj4NCjxESVY+wrzDrMKyw6nCucKk
wr7Dn8KjwrpBVkcmbmJzcDstJm5ic3A7d3d3LmF2Zy5jb20mbmJzcDs8L0RJVj4NCjxESVY+wrDD
psKxwr7Co8K6OS4wLjg2NSZuYnNwOy8mbmJzcDvCssKhwrbCvsOKw73CvsOdwr/DosKjwroyNzEu
MS4xLzMyMzUmbmJzcDstJm5ic3A7wrfCosKywrzDiMOVw4bDmsKjwroxMS8wMy8xMCZuYnNwOzE2
OjM2OjAwPC9ESVY+DQo8RElWPjwvRElWPjwvRk9OVD48L0RJVj48L0JPRFk+PC9IVE1MPg0K

--=====003_Dragon350103238280_=====--



From andrewmcgr@gmail.com  Sun Nov  7 19:28:47 2010
Return-Path: <andrewmcgr@gmail.com>
X-Original-To: hipsec@core3.amsl.com
Delivered-To: hipsec@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 8284328C0E4 for <hipsec@core3.amsl.com>; Sun,  7 Nov 2010 19:28:47 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.901
X-Spam-Level: 
X-Spam-Status: No, score=-1.901 tagged_above=-999 required=5 tests=[AWL=-0.699, BAYES_00=-2.599, HTML_MESSAGE=0.001, MIME_QP_LONG_LINE=1.396]
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 LInejcJTP1uZ for <hipsec@core3.amsl.com>; Sun,  7 Nov 2010 19:28:46 -0800 (PST)
Received: from mail-pz0-f44.google.com (mail-pz0-f44.google.com [209.85.210.44]) by core3.amsl.com (Postfix) with ESMTP id 64D8728C0D9 for <hipsec@ietf.org>; Sun,  7 Nov 2010 19:28:46 -0800 (PST)
Received: by pzk4 with SMTP id 4so1003190pzk.31 for <hipsec@ietf.org>; Sun, 07 Nov 2010 19:29:06 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:subject:mime-version :content-type:from:in-reply-to:date:cc:message-id:references:to :x-mailer; bh=yjKO2oPl79OQtHyEa/uWwSdZtwQdbBC1pEfmkYf9lGI=; b=phyAAF3GujRTz52wzj1EH+3TWdSN4zTlyRFSh/EVcm3BkT+rq0Zlt+XO9AIiG+n06l Ieg9WACZ/U+FwDXRFyTod1jAkG3Cc9IDYsfsgPf0jsN5PbPVANIqhcHDAUU3nADNOP4p 6voZm4fjSSC9ytvbwEK/eavhNLB3OONFGKD+k=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=subject:mime-version:content-type:from:in-reply-to:date:cc :message-id:references:to:x-mailer; b=tcGbHZiqTubdB+WPsBqdlighG1Pi2sTmNj8wyiMV+Dc0lvHSDsIdWyixSrHno0wQo7 Cg1llbe+wAjjKXlQyfOe71Hb6tFyETTbY6Hdp15ZNCx1aFAwnFVvLC3yvffZqwbnj1F4 ktPBMUL67Pq2M0sfrcbTGF1fElI34sTzkj/n4=
Received: by 10.142.14.20 with SMTP id 20mr4156560wfn.305.1289186945036; Sun, 07 Nov 2010 19:29:05 -0800 (PST)
Received: from ?IPv6:::1? (121-74-11-172.telstraclear.net [121.74.11.172]) by mx.google.com with ESMTPS id w14sm7378037wfd.18.2010.11.07.19.28.58 (version=TLSv1/SSLv3 cipher=RC4-MD5); Sun, 07 Nov 2010 19:29:03 -0800 (PST)
Mime-Version: 1.0 (Apple Message framework v1081)
Content-Type: multipart/alternative; boundary=Apple-Mail-5510--505396230
From: Andrew McGregor <andrewmcgr@gmail.com>
In-Reply-To: <201011081103570007893@163.com>
Date: Mon, 8 Nov 2010 11:28:52 +0800
Message-Id: <9E4345D0-100A-4E9B-BA20-8490C9E3A8C9@gmail.com>
References: <201011041748233287181@163.com> <201011081103570007893@163.com>
To: "Zhangfeng HU" <zfhu2001@163.com>
X-Mailer: Apple Mail (2.1081)
Cc: hipsec <hipsec@ietf.org>, =?utf-8?B?5p2c5paH6Z2Z?= <lxadj@126.com>
Subject: Re: [Hipsec] HIP Registration problem
X-BeenThere: hipsec@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: "This is the official IETF Mailing List for the HIP Working Group." <hipsec.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/hipsec>, <mailto:hipsec-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/hipsec>
List-Post: <mailto:hipsec@ietf.org>
List-Help: <mailto:hipsec-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/hipsec>, <mailto:hipsec-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 08 Nov 2010 03:28:47 -0000

--Apple-Mail-5510--505396230
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=utf-8

Register with several and use DNS round-robin, or just talk to all of =
them at once.  That's probably good enough, I think.

Andrew

On 8/11/2010, at 11:03 AM, Zhangfeng HU wrote:

> Hi,
> yes, that's the truth. Since HIP does provide a mechanism as DAAP of =
MIP, we are just considering a method of providing fault torlerance for =
RVS in HIP. For some mobile nodes, the high availability is very =
important, however the availability of these mobile nodes is mostly =
decided by the availability of the corresponding RVS who serves them. =
This RVS fault torlerance can not be easily implemented through updating =
the entries in DNS, because of the high latency and the cache mechanism =
used in DNS.
> =20
> =20
> =20
> 2010-11-08
> =20
> Zhangfeng HU, PhD candidate of
> Broadband Network Research Center,
> State Key Laboratory of Networking and Switching Technology,
> Beijing University of Posts and Telecommunications, Beijing, China
> =20
> Email:zfhu2001@gmail.com
> Tel:86+13811892137
> =E5=8F=91=E4=BB=B6=E4=BA=BA=EF=BC=9A Miika Komu
> =E5=8F=91=E9=80=81=E6=97=B6=E9=97=B4=EF=BC=9A 2010-11-04  18:47:45
> =E6=94=B6=E4=BB=B6=E4=BA=BA=EF=BC=9A hipsec
> =E6=8A=84=E9=80=81=EF=BC=9A
> =E4=B8=BB=E9=A2=98=EF=BC=9A Re: [Hipsec] HIP Registration problem
> On 11/04/2010 11:48 AM, zfhu2001 wrote:
> > Hi all,
> > As we know, a mobile node registers its HIP and IP address binding =
to a=20
> > correponding RVS server, but now I'm wondering whether the MN will=20=

> > register to a new RVS if a mobile node moves to another network and=20=

> > simultaneously its previous RVS server does not work any more. Or =
does=20
> > HIP provide a mechanisim as DAAP of MIP to detect the serving RVS =
server=20
> > of its home area?
> > Thanks.
> > 2010-11-04
> Hi,
> there's no such thing as "home agent" or "home area" in HIP. This is =
one
> of the differences to MIP. The same rendezvous server can be reused
> independently of the current network using the UPDATE procedure.
> Remember also that the rendezvous server forwards only the first I1 or
> the first UPDATE packet, so it's still a light-weight operation even
> though the latency be longer. The rendezvous server does not forward =
any
> application payload.
> Fault-tolerance for RVS may fall into the category of local policies
> (?). Changing the "current" RVS requires also an update to the DNS
> records. Another strategy could be just to publish multiple RVS =
servers
> in the DNS and send packets to all of them (which ever happens to be =
alive).
> _______________________________________________
> Hipsec mailing list
> Hipsec@ietf.org
> https://www.ietf.org/mailman/listinfo/hipsec
> =C3=94=C3=9A=C2=B4=C2=AB=C3=88=C3=AB=C2=B5=C3=84=C3=93=C3=8A=C2=BC=C3=BE=
=C3=96=C3=90=C3=8E=C2=B4=C2=B7=C2=A2=C3=8F=C3=96=C2=B2=C2=A1=C2=B6=C2=BE=C2=
=A1=C2=A3
> =C2=BC=C3=AC=C2=B2=C3=A9=C2=B9=C2=A4=C2=BE=C3=9F=C2=A3=C2=BAAVG - =
www.avg.com=20
> =C2=B0=C3=A6=C2=B1=C2=BE=C2=A3=C2=BA9.0.865 / =
=C2=B2=C2=A1=C2=B6=C2=BE=C3=8A=C3=BD=C2=BE=C3=9D=C2=BF=C3=A2=C2=A3=C2=BA27=
1.1.1/3235 - =C2=B7=C2=A2=C2=B2=C2=BC=C3=88=C3=95=C3=86=C3=9A=C2=A3=C2=BA1=
1/03/10 16:36:00
> _______________________________________________
> Hipsec mailing list
> Hipsec@ietf.org
> https://www.ietf.org/mailman/listinfo/hipsec


--Apple-Mail-5510--505396230
Content-Transfer-Encoding: quoted-printable
Content-Type: text/html;
	charset=utf-8

<html><head><base href=3D"x-msg://3851/"></head><body style=3D"word-wrap: =
break-word; -webkit-nbsp-mode: space; -webkit-line-break: =
after-white-space; ">Register with several and use DNS round-robin, or =
just talk to all of them at once. &nbsp;That's probably good enough, I =
think.<div><br></div><div>Andrew</div><div><br><div><div>On 8/11/2010, =
at 11:03 AM, Zhangfeng HU wrote:</div><br =
class=3D"Apple-interchange-newline"><blockquote type=3D"cite"><span =
class=3D"Apple-style-span" style=3D"border-collapse: separate; =
font-family: 'Lucida Sans'; font-style: normal; font-variant: normal; =
font-weight: normal; letter-spacing: normal; line-height: normal; =
orphans: 2; text-indent: 0px; text-transform: none; white-space: normal; =
widows: 2; word-spacing: 0px; -webkit-border-horizontal-spacing: 0px; =
-webkit-border-vertical-spacing: 0px; =
-webkit-text-decorations-in-effect: none; -webkit-text-size-adjust: =
auto; -webkit-text-stroke-width: 0px; font-size: medium; "><div =
style=3D"margin-top: 10px; margin-right: 10px; margin-bottom: 10px; =
margin-left: 10px; font-family: verdana; font-size: 10pt; "><div><font =
color=3D"#000080" size=3D"2">Hi,</font></div><div><font =
color=3D"#000080">yes, that's the truth. Since HIP does provide a =
mechanism as DAAP of MIP, we are just considering a method of providing =
fault torlerance for RVS in HIP. For some mobile nodes, the high =
availability is very important, however the availability of these mobile =
nodes is mostly decided by the availability of the corresponding RVS who =
serves them. This RVS fault torlerance can not be easily implemented =
through updating the entries in DNS, because of the high latency and the =
cache mechanism used in DNS.</font></div><div><font =
color=3D"#000080"></font>&nbsp;</div><div><font color=3D"#000080" =
size=3D"2"></font>&nbsp;</div><div><font color=3D"#000080" =
size=3D"2"></font>&nbsp;</div><div><font color=3D"#c0c0c0" =
size=3D"2">2010-11-08</font></div><font color=3D"#000080" size=3D"2"><hr =
align=3D"left" color=3D"#b5c4df" size=3D"1" style=3D"width: 100px; =
"></font><div><font color=3D"#c0c0c0" size=3D"2"><span><div><div><font =
size=3D"2"></font>&nbsp;<div><font size=3D"1">Zhangfeng HU, =
PhD&nbsp;candidate of</font></div><div><font size=3D"1">Broadband =
Network Research Center,</font></div><div><font size=3D"1">State Key =
Laboratory of Networking and Switching =
Technology,</font></div><div><font size=3D"1">Beijing University of =
Posts and Telecommunications, Beijing, China</font></div><div><font =
size=3D"1"></font>&nbsp;</div><div><font size=3D"1">Email:<a =
href=3D"mailto:zfhu2001@gmail.com" style=3D"color: blue; =
text-decoration: underline; =
">zfhu2001@gmail.com</a></font></div><div><div><font =
size=3D"1">Tel:86+13811892137</font></div></div></div></div></span></font>=
</div><hr color=3D"#b5c4df" size=3D"1"><div><font =
size=3D"2"><strong>=E5=8F=91=E4=BB=B6=E4=BA=BA=EF=BC=9A</strong><span =
class=3D"Apple-converted-space">&nbsp;</span>Miika =
Komu</font></div><div><font =
size=3D"2"><strong>=E5=8F=91=E9=80=81=E6=97=B6=E9=97=B4=EF=BC=9A</strong><=
span class=3D"Apple-converted-space">&nbsp;</span>2010-11-04&nbsp; =
18:47:45</font></div><div><font =
size=3D"2"><strong>=E6=94=B6=E4=BB=B6=E4=BA=BA=EF=BC=9A</strong><span =
class=3D"Apple-converted-space">&nbsp;</span>hipsec</font></div><div><font=
 size=3D"2"><strong>=E6=8A=84=E9=80=81=EF=BC=9A</strong></font></div><div>=
<font size=3D"2"><strong>=E4=B8=BB=E9=A2=98=EF=BC=9A</strong><span =
class=3D"Apple-converted-space">&nbsp;</span>Re: [Hipsec] HIP =
Registration problem</font></div><div><font =
size=3D"2"></font></div><div><font =
size=3D"2"><div>On&nbsp;11/04/2010&nbsp;11:48&nbsp;AM,&nbsp;zfhu2001&nbsp;=
wrote:</div><div>&gt;&nbsp;Hi&nbsp;all,</div><div>&gt;&nbsp;As&nbsp;we&nbs=
p;know,&nbsp;a&nbsp;mobile&nbsp;node&nbsp;registers&nbsp;its&nbsp;HIP&nbsp=
;and&nbsp;IP&nbsp;address&nbsp;binding&nbsp;to&nbsp;a&nbsp;</div><div>&gt;=
&nbsp;correponding&nbsp;RVS&nbsp;server,&nbsp;but&nbsp;now&nbsp;I'm&nbsp;w=
ondering&nbsp;whether&nbsp;the&nbsp;MN&nbsp;will&nbsp;</div><div>&gt;&nbsp=
;register&nbsp;to&nbsp;a&nbsp;new&nbsp;RVS&nbsp;if&nbsp;a&nbsp;mobile&nbsp=
;node&nbsp;moves&nbsp;to&nbsp;another&nbsp;network&nbsp;and&nbsp;</div><di=
v>&gt;&nbsp;simultaneously&nbsp;its&nbsp;previous&nbsp;RVS&nbsp;server&nbs=
p;does&nbsp;not&nbsp;work&nbsp;any&nbsp;more.&nbsp;Or&nbsp;does&nbsp;</div=
><div>&gt;&nbsp;HIP&nbsp;provide&nbsp;a&nbsp;mechanisim&nbsp;as&nbsp;DAAP&=
nbsp;of&nbsp;MIP&nbsp;to&nbsp;detect&nbsp;the&nbsp;serving&nbsp;RVS&nbsp;s=
erver&nbsp;</div><div>&gt;&nbsp;of&nbsp;its&nbsp;home&nbsp;area?</div><div=
>&gt;&nbsp;Thanks.</div><div>&gt;&nbsp;2010-11-04</div><div></div><div>Hi,=
</div><div></div><div>there's&nbsp;no&nbsp;such&nbsp;thing&nbsp;as&nbsp;"h=
ome&nbsp;agent"&nbsp;or&nbsp;"home&nbsp;area"&nbsp;in&nbsp;HIP.&nbsp;This&=
nbsp;is&nbsp;one</div><div>of&nbsp;the&nbsp;differences&nbsp;to&nbsp;MIP.&=
nbsp;The&nbsp;same&nbsp;rendezvous&nbsp;server&nbsp;can&nbsp;be&nbsp;reuse=
d</div><div>independently&nbsp;of&nbsp;the&nbsp;current&nbsp;network&nbsp;=
using&nbsp;the&nbsp;UPDATE&nbsp;procedure.</div><div>Remember&nbsp;also&nb=
sp;that&nbsp;the&nbsp;rendezvous&nbsp;server&nbsp;forwards&nbsp;only&nbsp;=
the&nbsp;first&nbsp;I1&nbsp;or</div><div>the&nbsp;first&nbsp;UPDATE&nbsp;p=
acket,&nbsp;so&nbsp;it's&nbsp;still&nbsp;a&nbsp;light-weight&nbsp;operatio=
n&nbsp;even</div><div>though&nbsp;the&nbsp;latency&nbsp;be&nbsp;longer.&nb=
sp;The&nbsp;rendezvous&nbsp;server&nbsp;does&nbsp;not&nbsp;forward&nbsp;an=
y</div><div>application&nbsp;payload.</div><div></div><div>Fault-tolerance=
&nbsp;for&nbsp;RVS&nbsp;may&nbsp;fall&nbsp;into&nbsp;the&nbsp;category&nbs=
p;of&nbsp;local&nbsp;policies</div><div>(?).&nbsp;Changing&nbsp;the&nbsp;"=
current"&nbsp;RVS&nbsp;requires&nbsp;also&nbsp;an&nbsp;update&nbsp;to&nbsp=
;the&nbsp;DNS</div><div>records.&nbsp;Another&nbsp;strategy&nbsp;could&nbs=
p;be&nbsp;just&nbsp;to&nbsp;publish&nbsp;multiple&nbsp;RVS&nbsp;servers</d=
iv><div>in&nbsp;the&nbsp;DNS&nbsp;and&nbsp;send&nbsp;packets&nbsp;to&nbsp;=
all&nbsp;of&nbsp;them&nbsp;(which&nbsp;ever&nbsp;happens&nbsp;to&nbsp;be&n=
bsp;alive).</div><div>_______________________________________________</div=
><div>Hipsec&nbsp;mailing&nbsp;list</div><div><a =
href=3D"mailto:Hipsec@ietf.org" style=3D"color: blue; text-decoration: =
underline; ">Hipsec@ietf.org</a></div><div><a =
href=3D"https://www.ietf.org/mailman/listinfo/hipsec" style=3D"color: =
blue; text-decoration: underline; =
">https://www.ietf.org/mailman/listinfo/hipsec</a></div><div></div><div>=C3=
=94=C3=9A=C2=B4=C2=AB=C3=88=C3=AB=C2=B5=C3=84=C3=93=C3=8A=C2=BC=C3=BE=C3=96=
=C3=90=C3=8E=C2=B4=C2=B7=C2=A2=C3=8F=C3=96=C2=B2=C2=A1=C2=B6=C2=BE=C2=A1=C2=
=A3</div><div>=C2=BC=C3=AC=C2=B2=C3=A9=C2=B9=C2=A4=C2=BE=C3=9F=C2=A3=C2=BA=
AVG&nbsp;-&nbsp;<a href=3D"http://www.avg.com" style=3D"color: blue; =
text-decoration: underline; =
">www.avg.com</a>&nbsp;</div><div>=C2=B0=C3=A6=C2=B1=C2=BE=C2=A3=C2=BA9.0.=
865&nbsp;/&nbsp;=C2=B2=C2=A1=C2=B6=C2=BE=C3=8A=C3=BD=C2=BE=C3=9D=C2=BF=C3=A2=
=C2=A3=C2=BA271.1.1/3235&nbsp;-&nbsp;=C2=B7=C2=A2=C2=B2=C2=BC=C3=88=C3=95=C3=
=86=C3=9A=C2=A3=C2=BA11/03/10&nbsp;16:36:00</div><div></div></font></div>_=
______________________________________________<br>Hipsec mailing =
list<br><a href=3D"mailto:Hipsec@ietf.org" style=3D"color: blue; =
text-decoration: underline; ">Hipsec@ietf.org</a><br><a =
href=3D"https://www.ietf.org/mailman/listinfo/hipsec" style=3D"color: =
blue; text-decoration: underline; =
">https://www.ietf.org/mailman/listinfo/hipsec</a><br></div></span></block=
quote></div><br></div></body></html>=

--Apple-Mail-5510--505396230--

From mkomu@cs.hut.fi  Sun Nov  7 20:53:05 2010
Return-Path: <mkomu@cs.hut.fi>
X-Original-To: hipsec@core3.amsl.com
Delivered-To: hipsec@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 2F4AE28C0E4 for <hipsec@core3.amsl.com>; Sun,  7 Nov 2010 20:53:05 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.599
X-Spam-Level: 
X-Spam-Status: No, score=-6.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Y5o8ulgO5r3u for <hipsec@core3.amsl.com>; Sun,  7 Nov 2010 20:52:58 -0800 (PST)
Received: from mail.cs.hut.fi (mail.cs.hut.fi [130.233.192.7]) by core3.amsl.com (Postfix) with ESMTP id C957128C0F2 for <hipsec@ietf.org>; Sun,  7 Nov 2010 20:52:57 -0800 (PST)
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 1PFJjI-0000Mx-Aq for hipsec@ietf.org; Mon, 08 Nov 2010 06:53:16 +0200
Message-ID: <4CD7823A.8090003@cs.hut.fi>
Date: Mon, 08 Nov 2010 06:53:14 +0200
From: Miika Komu <mkomu@cs.hut.fi>
User-Agent: Mozilla/5.0 (X11; U; Linux x86_64; en-US; rv:1.9.1.15) Gecko/20101027 Thunderbird/3.0.10
MIME-Version: 1.0
To: hipsec@ietf.org
References: <201011041748233287181@163.com> <201011081103570007893@163.com> <9E4345D0-100A-4E9B-BA20-8490C9E3A8C9@gmail.com>
In-Reply-To: <9E4345D0-100A-4E9B-BA20-8490C9E3A8C9@gmail.com>
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 8bit
Subject: Re: [Hipsec] HIP Registration problem
X-BeenThere: hipsec@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: "This is the official IETF Mailing List for the HIP Working Group." <hipsec.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/hipsec>, <mailto:hipsec-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/hipsec>
List-Post: <mailto:hipsec@ietf.org>
List-Help: <mailto:hipsec-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/hipsec>, <mailto:hipsec-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 08 Nov 2010 04:53:05 -0000

Hi,

agree with Andrew. We've had already a related discussion on parallel 
connectivity checks which applies to rendezvous as well:

http://www.ietf.org/mail-archive/web/hipsec/current/msg02837.html

On 11/08/2010 05:28 AM, Andrew McGregor wrote:
> Register with several and use DNS round-robin, or just talk to all of
> them at once. That's probably good enough, I think.
>
> Andrew
>
> On 8/11/2010, at 11:03 AM, Zhangfeng HU wrote:
>
>> Hi,
>> yes, that's the truth. Since HIP does provide a mechanism as DAAP of
>> MIP, we are just considering a method of providing fault torlerance
>> for RVS in HIP. For some mobile nodes, the high availability is very
>> important, however the availability of these mobile nodes is mostly
>> decided by the availability of the corresponding RVS who serves them.
>> This RVS fault torlerance can not be easily implemented through
>> updating the entries in DNS, because of the high latency and the cache
>> mechanism used in DNS.
>> 2010-11-08
>> ------------------------------------------------------------------------
>> Zhangfeng HU, PhD candidate of
>> Broadband Network Research Center,
>> State Key Laboratory of Networking and Switching Technology,
>> Beijing University of Posts and Telecommunications, Beijing, China
>> Email:zfhu2001@gmail.com <mailto:zfhu2001@gmail.com>
>> Tel:86+13811892137
>> ------------------------------------------------------------------------
>> *发件人：* Miika Komu
>> *发送时间：* 2010-11-04 18:47:45
>> *收件人：* hipsec
>> *抄送：*
>> *主题：* Re: [Hipsec] HIP Registration problem
>> On 11/04/2010 11:48 AM, zfhu2001 wrote:
>> > Hi all,
>> > As we know, a mobile node registers its HIP and IP address binding to a
>> > correponding RVS server, but now I'm wondering whether the MN will
>> > register to a new RVS if a mobile node moves to another network and
>> > simultaneously its previous RVS server does not work any more. Or does
>> > HIP provide a mechanisim as DAAP of MIP to detect the serving RVS server
>> > of its home area?
>> > Thanks.
>> > 2010-11-04
>> Hi,
>> there's no such thing as "home agent" or "home area" in HIP. This is one
>> of the differences to MIP. The same rendezvous server can be reused
>> independently of the current network using the UPDATE procedure.
>> Remember also that the rendezvous server forwards only the first I1 or
>> the first UPDATE packet, so it's still a light-weight operation even
>> though the latency be longer. The rendezvous server does not forward any
>> application payload.
>> Fault-tolerance for RVS may fall into the category of local policies
>> (?). Changing the "current" RVS requires also an update to the DNS
>> records. Another strategy could be just to publish multiple RVS servers
>> in the DNS and send packets to all of them (which ever happens to be
>> alive).
>> _______________________________________________
>> Hipsec mailing list
>> Hipsec@ietf.org <mailto:Hipsec@ietf.org>
>> https://www.ietf.org/mailman/listinfo/hipsec
>> ÔÚ´«ÈëµÄÓÊ¼þÖÐÎ´·¢ÏÖ²¡¶¾¡£
>> ¼ì²é¹¤¾ß£ºAVG - www.avg.com <http://www.avg.com>
>> °æ±¾£º9.0.865 / ²¡¶¾Êý¾Ý¿â£º271.1.1/3235 - ·¢²¼ÈÕÆÚ£º11/03/10 16:36:00
>> _______________________________________________
>> Hipsec mailing list
>> Hipsec@ietf.org <mailto:Hipsec@ietf.org>
>> https://www.ietf.org/mailman/listinfo/hipsec
>
>
>
> _______________________________________________
> Hipsec mailing list
> Hipsec@ietf.org
> https://www.ietf.org/mailman/listinfo/hipsec


From Internet-Drafts@ietf.org  Mon Nov  8 03:30:13 2010
Return-Path: <Internet-Drafts@ietf.org>
X-Original-To: hipsec@core3.amsl.com
Delivered-To: hipsec@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 22CF63A69A2; Mon,  8 Nov 2010 03:30:13 -0800 (PST)
X-Quarantine-ID: <2GQE+lFffYUM>
X-Virus-Scanned: amavisd-new at amsl.com
X-Amavis-Alert: BAD HEADER, MIME error: error: unexpected end of preamble
X-Spam-Flag: NO
X-Spam-Score: -99.242
X-Spam-Level: 
X-Spam-Status: No, score=-99.242 tagged_above=-999 required=5 tests=[AWL=-0.428, BAYES_00=-2.599, MISSING_MIME_HB_SEP=2.119, SARE_BOUNDARY_LC=1.666, 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 2GQE+lFffYUM; Mon,  8 Nov 2010 03:30:11 -0800 (PST)
Received: from [127.0.0.1] (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id DF3BB28C157; Mon,  8 Nov 2010 03:30:06 -0800 (PST)
MIME-Version: 1.0
Content-Type: multipart/mixed; boundary="nextpart"
From: Internet-Drafts@ietf.org
To: i-d-announce@ietf.org
X-Test-IDTracker: no
Message-ID: <20101108113006.25315.53911.idtracker@localhost>
Date: Mon, 08 Nov 2010 03:30:06 -0800
Cc: hipsec@ietf.org
Subject: [Hipsec] I-D Action:draft-ietf-hip-cert-05.txt
X-BeenThere: hipsec@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: "This is the official IETF Mailing List for the HIP Working Group." <hipsec.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/hipsec>, <mailto:hipsec-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/hipsec>
List-Post: <mailto:hipsec@ietf.org>
List-Help: <mailto:hipsec-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/hipsec>, <mailto:hipsec-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 08 Nov 2010 11:30:13 -0000

--NextPart

A New Internet-Draft is available from the on-line Internet-Drafts directories.
This draft is a work item of the Host Identity Protocol Working Group of the IETF.


	Title           : Host Identity Protocol Certificates
	Author(s)       : T. Heer, S. Varjonen
	Filename        : draft-ietf-hip-cert-05.txt
	Pages           : 13
	Date            : 2010-11-08

The CERT parameter is a container for X.509.v3 certificates and
Simple Public Key Infrastructure (SPKI) certificates.  It is used for
carrying these certificates in Host Identity Protocol (HIP) control
packets.  This document only specifies the certificate parameter and
the error signaling in case of a failed verification.  The use of
certificates including how certificates are obtained, requested, and
which actions are taken upon successful or failed verification are to
be defined in the documents that use the certificate parameter.
Additionally, this document specifies the representations of Host
Identity Tags in X.509.v3 and SPKI certificates.

A URL for this Internet-Draft is:
http://www.ietf.org/internet-drafts/draft-ietf-hip-cert-05.txt

Internet-Drafts are also available by anonymous FTP at:
ftp://ftp.ietf.org/internet-drafts/

Below is the data which will enable a MIME compliant mail reader
implementation to automatically retrieve the ASCII version of the
Internet-Draft.

--NextPart
Content-Type: Message/External-body;
	name="draft-ietf-hip-cert-05.txt";
	site="ftp.ietf.org";
	access-type="anon-ftp";
	directory="internet-drafts"

Content-Type: text/plain
Content-ID:     <2010-11-08032810.I-D@ietf.org>

--NextPart--

From Internet-Drafts@ietf.org  Mon Nov  8 18:16:22 2010
Return-Path: <Internet-Drafts@ietf.org>
X-Original-To: hipsec@core3.amsl.com
Delivered-To: hipsec@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 6DBE628C292; Mon,  8 Nov 2010 18:16:22 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -101.835
X-Spam-Level: 
X-Spam-Status: No, score=-101.835 tagged_above=-999 required=5 tests=[AWL=0.764, BAYES_00=-2.599, 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 T0sVdKOGufPW; Mon,  8 Nov 2010 18:16:21 -0800 (PST)
Received: from [127.0.0.1] (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 9C2BE3A6A1E; Mon,  8 Nov 2010 18:15:30 -0800 (PST)
MIME-Version: 1.0
Content-Type: Multipart/Mixed; Boundary="NextPart"
From: Internet-Drafts@ietf.org
To: i-d-announce@ietf.org
X-Test-IDTracker: no
Message-ID: <20101109021530.26008.87765.idtracker@localhost>
Date: Mon, 08 Nov 2010 18:15:30 -0800
Cc: hipsec@ietf.org
Subject: [Hipsec] I-D Action:draft-ietf-hip-cert-05.txt
X-BeenThere: hipsec@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: "This is the official IETF Mailing List for the HIP Working Group." <hipsec.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/hipsec>, <mailto:hipsec-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/hipsec>
List-Post: <mailto:hipsec@ietf.org>
List-Help: <mailto:hipsec-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/hipsec>, <mailto:hipsec-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 09 Nov 2010 02:16:22 -0000

--NextPart

A New Internet-Draft is available from the on-line Internet-Drafts directories.
This draft is a work item of the Host Identity Protocol Working Group of the IETF.


	Title           : Host Identity Protocol Certificates
	Author(s)       : T. Heer, S. Varjonen
	Filename        : draft-ietf-hip-cert-05.txt
	Pages           : 13
	Date            : 2010-11-08

The CERT parameter is a container for X.509.v3 certificates and
Simple Public Key Infrastructure (SPKI) certificates.  It is used for
carrying these certificates in Host Identity Protocol (HIP) control
packets.  This document only specifies the certificate parameter and
the error signaling in case of a failed verification.  The use of
certificates including how certificates are obtained, requested, and
which actions are taken upon successful or failed verification are to
be defined in the documents that use the certificate parameter.
Additionally, this document specifies the representations of Host
Identity Tags in X.509.v3 and SPKI certificates.

A URL for this Internet-Draft is:
http://www.ietf.org/internet-drafts/draft-ietf-hip-cert-05.txt

Internet-Drafts are also available by anonymous FTP at:
ftp://ftp.ietf.org/internet-drafts/

Below is the data which will enable a MIME compliant mail reader
implementation to automatically retrieve the ASCII version of the
Internet-Draft.

--NextPart
Content-Type: Message/External-body; name="draft-ietf-hip-cert-05.txt";
	site="ftp.ietf.org"; access-type="anon-ftp";
	directory="internet-drafts"

Content-Type: text/plain
Content-ID: <2010-11-08032810.I-D@ietf.org>


--NextPart--

From wenjingduxx@gmail.com  Wed Nov  3 18:14:38 2010
Return-Path: <wenjingduxx@gmail.com>
X-Original-To: hipsec@core3.amsl.com
Delivered-To: hipsec@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id AD89928C0EB for <hipsec@core3.amsl.com>; Wed,  3 Nov 2010 18:14:38 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.598
X-Spam-Level: 
X-Spam-Status: No, score=-2.598 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HTML_MESSAGE=0.001]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id wqvbZV4PXqFX for <hipsec@core3.amsl.com>; Wed,  3 Nov 2010 18:14:37 -0700 (PDT)
Received: from mail-px0-f172.google.com (mail-px0-f172.google.com [209.85.212.172]) by core3.amsl.com (Postfix) with ESMTP id E2D193A6910 for <hipsec@ietf.org>; Wed,  3 Nov 2010 18:14:37 -0700 (PDT)
Received: by pxi6 with SMTP id 6so86204pxi.31 for <hipsec@ietf.org>; Wed, 03 Nov 2010 18:14:46 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:received:date:message-id :subject:from:to:content-type; bh=q8rlUVAIBppgVvLTg2KDDpAuXDtujneuA86bLyQlJm0=; b=YqpXro3HboJAgRntxor4r4CW5iwdZUvS7ZouRgCxmxoZrmJMEyFnGtgLgocLtLhW4o Us2L/ho2T9MlEPj/VOOODKJ2qeAz0gT4qHyewXyGJwkBS7D9knGE2atTAyUcgk909Uv7 z/maO1RsWYrXNgUHea55gpPEehMUOmjHCcCY0=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:date:message-id:subject:from:to:content-type; b=LyluknmNS09mWIWGCh21ZAw4oZvR3swgKG6JkjMAnyX4BaomMtzk9rkSRExccsOu2L FVck/Pb+Bn1vyLxDjQSjR8LDgzUyMQFESPltAdDwQ4irxgejK/L0NvJESrIqFcb9Le77 4RMoAR4qlHlfH1MHrPlqoItLLcMnECu3IhB3Y=
MIME-Version: 1.0
Received: by 10.142.223.15 with SMTP id v15mr10604wfg.330.1288833286400; Wed, 03 Nov 2010 18:14:46 -0700 (PDT)
Received: by 10.142.114.3 with HTTP; Wed, 3 Nov 2010 18:14:46 -0700 (PDT)
Date: Thu, 4 Nov 2010 09:14:46 +0800
Message-ID: <AANLkTins_Z4uD9FuH50k8EwzQg7=SZBYUSEna1fFvxLY@mail.gmail.com>
From: wenjing du <wenjingduxx@gmail.com>
To: hipsec@ietf.org
Content-Type: multipart/alternative; boundary=000e0cd255ae35ec3a04942fe27d
X-Mailman-Approved-At: Tue, 09 Nov 2010 02:18:52 -0800
Subject: [Hipsec]  Register Question
X-BeenThere: hipsec@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: "This is the official IETF Mailing List for the HIP Working Group." <hipsec.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/hipsec>, <mailto:hipsec-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/hipsec>
List-Post: <mailto:hipsec@ietf.org>
List-Help: <mailto:hipsec-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/hipsec>, <mailto:hipsec-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 04 Nov 2010 08:12:24 -0000

--000e0cd255ae35ec3a04942fe27d
Content-Type: text/plain; charset=ISO-8859-1

Hi all,



   A mobile node registers its HIT and IP address to a RVS, I am
wandering whether the MN will register to a new RVS if one MN moves to
another network and its previous RVS does not work?

   or Does hip provide a mechanism such as DAAP of MIP to detect a RVS of
its home area?



Evela

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

<br>
<div id=3D"msg_body" style=3D"PADDING-RIGHT: 10px; PADDING-LEFT: 10px; FONT=
-SIZE: 14px; PADDING-BOTTOM: 0px; COLOR: #000000; PADDING-TOP: 0px"><base t=
arget=3D"_blank">
<div id=3D"msg_body" style=3D"PADDING-RIGHT: 10px; PADDING-LEFT: 10px; FONT=
-SIZE: 14px; PADDING-BOTTOM: 0px; COLOR: #000000; PADDING-TOP: 0px"><base t=
arget=3D"_blank">
<p>Hi all,</p>
<p>=A0=A0=A0</p>
<p>=A0=A0=A0A mobile node registers its HIT and IP address to a RVS, I am w=
andering=A0whether=A0the MN will register to a new RVS if one MN moves to a=
nother network and its previous RVS does not=A0work?</p>
<p>=A0=A0 or=A0Does hip=A0provide=A0a mechanism such as DAAP of MIP to dete=
ct a RVS of its home area?</p>
<p>=A0</p>
<p>Evela</p></div><br></div>

--000e0cd255ae35ec3a04942fe27d--

From gurtov@hiit.fi  Mon Nov  8 07:40:46 2010
Return-Path: <gurtov@hiit.fi>
X-Original-To: hipsec@core3.amsl.com
Delivered-To: hipsec@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 110703A68DE for <hipsec@core3.amsl.com>; Mon,  8 Nov 2010 07:40:46 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level: 
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id xy8bmNIg8gQ7 for <hipsec@core3.amsl.com>; Mon,  8 Nov 2010 07:40:42 -0800 (PST)
Received: from argo.otaverkko.fi (argo.otaverkko.fi [212.68.0.2]) by core3.amsl.com (Postfix) with ESMTP id 265383A68BE for <hipsec@ietf.org>; Mon,  8 Nov 2010 07:40:17 -0800 (PST)
Received: from [130.129.65.55] (dhcp-4137.meeting.ietf.org [130.129.65.55]) by argo.otaverkko.fi (Postfix) with ESMTP id A81F025ED1D for <hipsec@ietf.org>; Mon,  8 Nov 2010 17:40:24 +0200 (EET)
Message-ID: <4CD819D9.3000504@hiit.fi>
Date: Mon, 08 Nov 2010 17:40:09 +0200
From: Andrei Gurtov <gurtov@hiit.fi>
User-Agent: Thunderbird 2.0.0.24 (Windows/20100228)
MIME-Version: 1.0
To: hipsec <hipsec@ietf.org>
X-Enigmail-Version: 0.96.0
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit
X-Mailman-Approved-At: Tue, 09 Nov 2010 02:18:52 -0800
Subject: [Hipsec] multipath transmission
X-BeenThere: hipsec@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: "This is the official IETF Mailing List for the HIP Working Group." <hipsec.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/hipsec>, <mailto:hipsec-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/hipsec>
List-Post: <mailto:hipsec@ietf.org>
List-Help: <mailto:hipsec-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/hipsec>, <mailto:hipsec-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 08 Nov 2010 15:40:46 -0000

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Hi,

We've been discussing with Tom on integrating text on multipath
scheduler in HIP to the new multihoming draft. Do you think that's a
good idea? The section would be more like advanced/optional feature in
the document which is not mandatory to implement. The actual idea is
described in following papers

A. Gurtov, T. Polishchuk, Secure Multipath Transport for Legacy Internet
Applications, in Proc. of BROADNETS'09, September 2009.
T. Polishchuk, A. Gurtov, Improving TCP-friendliness for mHIP , to
appear in Proc. of 5th International Conference on Access Networks
(ACCESSNETS'10), November 2010.
http://www.cs.helsinki.fi/u/gurtov/papers/

BR
Andrei
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.10 (MingW32)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/

iEYEARECAAYFAkzYGdkACgkQP7jp0uceFkR+EQCaAjpyN5Fwx8CtCyQt87sQYh3c
K6QAoIiExYIEEzXY/O6Zz15FyYS3aGeR
=RcFd
-----END PGP SIGNATURE-----

From mkomu@cs.hut.fi  Tue Nov  9 20:41:52 2010
Return-Path: <mkomu@cs.hut.fi>
X-Original-To: hipsec@core3.amsl.com
Delivered-To: hipsec@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 64AE63A6818 for <hipsec@core3.amsl.com>; Tue,  9 Nov 2010 20:41:52 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.599
X-Spam-Level: 
X-Spam-Status: No, score=-6.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id U2r3tGA-mLNm for <hipsec@core3.amsl.com>; Tue,  9 Nov 2010 20:41:48 -0800 (PST)
Received: from mail.cs.hut.fi (mail.cs.hut.fi [130.233.192.7]) by core3.amsl.com (Postfix) with ESMTP id 547063A680A for <hipsec@ietf.org>; Tue,  9 Nov 2010 20:41:47 -0800 (PST)
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 1PG2Vf-0001yf-OP for hipsec@ietf.org; Wed, 10 Nov 2010 06:42:12 +0200
Message-ID: <4CDA22A1.2080405@cs.hut.fi>
Date: Wed, 10 Nov 2010 06:42:09 +0200
From: Miika Komu <mkomu@cs.hut.fi>
User-Agent: Mozilla/5.0 (X11; U; Linux x86_64; en-US; rv:1.9.1.15) Gecko/20101027 Thunderbird/3.0.10
MIME-Version: 1.0
To: hipsec@ietf.org
References: <4CD819D9.3000504@hiit.fi>
In-Reply-To: <4CD819D9.3000504@hiit.fi>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Subject: Re: [Hipsec] multipath transmission
X-BeenThere: hipsec@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: "This is the official IETF Mailing List for the HIP Working Group." <hipsec.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/hipsec>, <mailto:hipsec-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/hipsec>
List-Post: <mailto:hipsec@ietf.org>
List-Help: <mailto:hipsec-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/hipsec>, <mailto:hipsec-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 10 Nov 2010 04:41:52 -0000

Hi,

nice work! I believe it justifies a document of its own. My suggestion 
would be a new research group document because the work is still based 
on simulations, lacks interoperability results and experimentation in 
the wild. I'd also like to see the existing mobility and multihoming 
draft to make rapid progress rather than being blocked by new extensions.

On 11/08/2010 05:40 PM, Andrei Gurtov wrote:
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
>
> Hi,
>
> We've been discussing with Tom on integrating text on multipath
> scheduler in HIP to the new multihoming draft. Do you think that's a
> good idea? The section would be more like advanced/optional feature in
> the document which is not mandatory to implement. The actual idea is
> described in following papers
>
> A. Gurtov, T. Polishchuk, Secure Multipath Transport for Legacy Internet
> Applications, in Proc. of BROADNETS'09, September 2009.
> T. Polishchuk, A. Gurtov, Improving TCP-friendliness for mHIP , to
> appear in Proc. of 5th International Conference on Access Networks
> (ACCESSNETS'10), November 2010.
> http://www.cs.helsinki.fi/u/gurtov/papers/
>
> BR
> Andrei
> -----BEGIN PGP SIGNATURE-----
> Version: GnuPG v1.4.10 (MingW32)
> Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/
>
> iEYEARECAAYFAkzYGdkACgkQP7jp0uceFkR+EQCaAjpyN5Fwx8CtCyQt87sQYh3c
> K6QAoIiExYIEEzXY/O6Zz15FyYS3aGeR
> =RcFd
> -----END PGP SIGNATURE-----
> _______________________________________________
> Hipsec mailing list
> Hipsec@ietf.org
> https://www.ietf.org/mailman/listinfo/hipsec


From gurtov@cs.helsinki.fi  Thu Nov 11 00:16:51 2010
Return-Path: <gurtov@cs.helsinki.fi>
X-Original-To: hipsec@core3.amsl.com
Delivered-To: hipsec@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id B27BF3A68BC for <hipsec@core3.amsl.com>; Thu, 11 Nov 2010 00:16:51 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.599
X-Spam-Level: 
X-Spam-Status: No, score=-102.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, 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 yOAPtnvxjDQz for <hipsec@core3.amsl.com>; Thu, 11 Nov 2010 00:16:50 -0800 (PST)
Received: from argo.otaverkko.fi (argo.otaverkko.fi [212.68.0.2]) by core3.amsl.com (Postfix) with ESMTP id 84BDD3A68FD for <hipsec@ietf.org>; Thu, 11 Nov 2010 00:16:49 -0800 (PST)
Received: from [130.129.118.189] (dhcp-76bd.meeting.ietf.org [130.129.118.189]) by argo.otaverkko.fi (Postfix) with ESMTP id 95F3425ED11; Thu, 11 Nov 2010 10:17:16 +0200 (EET)
Message-ID: <4CDBA603.1030601@cs.helsinki.fi>
Date: Thu, 11 Nov 2010 10:14:59 +0200
From: Andrei Gurtov <gurtov@cs.helsinki.fi>
User-Agent: Thunderbird 2.0.0.24 (Windows/20100228)
MIME-Version: 1.0
To: Miika Komu <mkomu@cs.hut.fi>
References: <4CD819D9.3000504@hiit.fi> <4CDA22A1.2080405@cs.hut.fi>
In-Reply-To: <4CDA22A1.2080405@cs.hut.fi>
X-Enigmail-Version: 0.96.0
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit
Cc: hipsec@ietf.org
Subject: Re: [Hipsec] multipath transmission
X-BeenThere: hipsec@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: "This is the official IETF Mailing List for the HIP Working Group." <hipsec.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/hipsec>, <mailto:hipsec-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/hipsec>
List-Post: <mailto:hipsec@ietf.org>
List-Help: <mailto:hipsec-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/hipsec>, <mailto:hipsec-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 11 Nov 2010 08:16:51 -0000

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1


Actually there is a Linux implementation and experiments. The paper is
under review currently and I'll post a link after it has been accepted.

Regarding interoperability, I don't think multihoming in general was
ever tested for HIP implementations.

As I mentioned, this part can go to a separate optional section and
could provide additional motivation for the WG document rather than
being simple fault-over multihoming.

Andrei

Miika Komu wrote:
> Hi,
> 
> nice work! I believe it justifies a document of its own. My suggestion
> would be a new research group document because the work is still based
> on simulations, lacks interoperability results and experimentation in
> the wild. I'd also like to see the existing mobility and multihoming
> draft to make rapid progress rather than being blocked by new extensions.
> 
> On 11/08/2010 05:40 PM, Andrei Gurtov wrote:
> Hi,
> 
> We've been discussing with Tom on integrating text on multipath
> scheduler in HIP to the new multihoming draft. Do you think that's a
> good idea? The section would be more like advanced/optional feature in
> the document which is not mandatory to implement. The actual idea is
> described in following papers
> 
> A. Gurtov, T. Polishchuk, Secure Multipath Transport for Legacy Internet
> Applications, in Proc. of BROADNETS'09, September 2009.
> T. Polishchuk, A. Gurtov, Improving TCP-friendliness for mHIP , to
> appear in Proc. of 5th International Conference on Access Networks
> (ACCESSNETS'10), November 2010.
> http://www.cs.helsinki.fi/u/gurtov/papers/
> 
> BR
> Andrei
_______________________________________________
Hipsec mailing list
Hipsec@ietf.org
https://www.ietf.org/mailman/listinfo/hipsec

> _______________________________________________
> Hipsec mailing list
> Hipsec@ietf.org
> https://www.ietf.org/mailman/listinfo/hipsec
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.10 (MingW32)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/

iEYEARECAAYFAkzbpgMACgkQP7jp0uceFkRxbwCcD0uSzF+6vJ5ItmFiVQ+hqSEm
Hc4AoL/iLjePh4py8JrlRUlMPUsvG0vO
=Q6+Y
-----END PGP SIGNATURE-----

From goodzi@gmail.com  Fri Nov 12 01:25:09 2010
Return-Path: <goodzi@gmail.com>
X-Original-To: hipsec@core3.amsl.com
Delivered-To: hipsec@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 112A228C12A for <hipsec@core3.amsl.com>; Fri, 12 Nov 2010 01:25:09 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level: 
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id wnqCPWLdprTf for <hipsec@core3.amsl.com>; Fri, 12 Nov 2010 01:24:59 -0800 (PST)
Received: from mail-iw0-f172.google.com (mail-iw0-f172.google.com [209.85.214.172]) by core3.amsl.com (Postfix) with ESMTP id 8A2E628C105 for <hipsec@ietf.org>; Fri, 12 Nov 2010 01:24:59 -0800 (PST)
Received: by iwn40 with SMTP id 40so3437110iwn.31 for <hipsec@ietf.org>; Fri, 12 Nov 2010 01:25:31 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:received:in-reply-to :references:date:message-id:subject:from:to:cc:content-type :content-transfer-encoding; bh=tezm1IK1snKi/SPmYrqsNvwc5YQXjEBkRJQ7+Qp/0II=; b=eDH5k9txXIUDCP2fcDTw8HaldVyaH5arFg0AVl2wuJFlp8OJ+4CyJ2r91HoyD/5vgz Laz0OvvPf2fGKXsFVzryFxJRYBF281t4JV5SV+9LsZBjbdMq2B3gaS1hHR8vifDamw95 e1Kc+sPquqKtyF/aHInucH13YWvfcqcMVJvyU=
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:content-transfer-encoding; b=GphK2Zlu3rT5Y07W/Nq4sGfN71SD0he+7V0gDPrmR1boRHCFViteelkIJiYbCLSQvs 2YTwJ2p+3NUXvgHQTWmsWgFK//RNQoKJy4oC7fmFVl/nJfmqN1/H6TIJjw1Ceu9xA8g/ dg9r7BNrPTxHZKzdyWawScl2CIyGA7ATC9y84=
MIME-Version: 1.0
Received: by 10.231.169.70 with SMTP id x6mr1706788iby.2.1289553931475; Fri, 12 Nov 2010 01:25:31 -0800 (PST)
Received: by 10.231.33.203 with HTTP; Fri, 12 Nov 2010 01:25:31 -0800 (PST)
In-Reply-To: <4CDBA603.1030601@cs.helsinki.fi>
References: <4CD819D9.3000504@hiit.fi> <4CDA22A1.2080405@cs.hut.fi> <4CDBA603.1030601@cs.helsinki.fi>
Date: Fri, 12 Nov 2010 10:25:31 +0100
Message-ID: <AANLkTi=OX=spy7i1S_f+0=zunkY+nB3Eez8A+abZPwHo@mail.gmail.com>
From: Bokor Laszlo <goodzi@gmail.com>
To: Andrei Gurtov <gurtov@cs.helsinki.fi>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable
Cc: hipsec@ietf.org
Subject: Re: [Hipsec] multipath transmission
X-BeenThere: hipsec@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: "This is the official IETF Mailing List for the HIP Working Group." <hipsec.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/hipsec>, <mailto:hipsec-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/hipsec>
List-Post: <mailto:hipsec@ietf.org>
List-Help: <mailto:hipsec-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/hipsec>, <mailto:hipsec-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 12 Nov 2010 09:25:09 -0000

Dear Andrei,

I have one small comment to this nice work and your mail:

> Regarding interoperability, I don't think multihoming in general was
> ever tested for HIP implementations.

Knowing that this is not a real-life implementation, but here you can
find our research paper presenting HIP-based multihoming and flow
mobility ("per-application mobility") implemented and tested as an
INET/OMNeT++ simulation:

http://www.ict-optimix.eu/images/0/0a/Protocol_Design_and_Analysis_of_a_HIP=
-based_Per-Application_Mobility_Management_Platform_PDF.pdf

Best regards,
Laszlo

--
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


2010/11/11 Andrei Gurtov <gurtov@cs.helsinki.fi>:
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
>
>
> Actually there is a Linux implementation and experiments. The paper is
> under review currently and I'll post a link after it has been accepted.
>
> Regarding interoperability, I don't think multihoming in general was
> ever tested for HIP implementations.
>
> As I mentioned, this part can go to a separate optional section and
> could provide additional motivation for the WG document rather than
> being simple fault-over multihoming.
>
> Andrei
>
> Miika Komu wrote:
>> Hi,
>>
>> nice work! I believe it justifies a document of its own. My suggestion
>> would be a new research group document because the work is still based
>> on simulations, lacks interoperability results and experimentation in
>> the wild. I'd also like to see the existing mobility and multihoming
>> draft to make rapid progress rather than being blocked by new extensions=
.
>>
>> On 11/08/2010 05:40 PM, Andrei Gurtov wrote:
>> Hi,
>>
>> We've been discussing with Tom on integrating text on multipath
>> scheduler in HIP to the new multihoming draft. Do you think that's a
>> good idea? The section would be more like advanced/optional feature in
>> the document which is not mandatory to implement. The actual idea is
>> described in following papers
>>
>> A. Gurtov, T. Polishchuk, Secure Multipath Transport for Legacy Internet
>> Applications, in Proc. of BROADNETS'09, September 2009.
>> T. Polishchuk, A. Gurtov, Improving TCP-friendliness for mHIP , to
>> appear in Proc. of 5th International Conference on Access Networks
>> (ACCESSNETS'10), November 2010.
>> http://www.cs.helsinki.fi/u/gurtov/papers/
>>
>> BR
>> Andrei
> _______________________________________________
> Hipsec mailing list
> Hipsec@ietf.org
> https://www.ietf.org/mailman/listinfo/hipsec
>
>> _______________________________________________
>> Hipsec mailing list
>> Hipsec@ietf.org
>> https://www.ietf.org/mailman/listinfo/hipsec
> -----BEGIN PGP SIGNATURE-----
> Version: GnuPG v1.4.10 (MingW32)
> Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/
>
> iEYEARECAAYFAkzbpgMACgkQP7jp0uceFkRxbwCcD0uSzF+6vJ5ItmFiVQ+hqSEm
> Hc4AoL/iLjePh4py8JrlRUlMPUsvG0vO
> =3DQ6+Y
> -----END PGP SIGNATURE-----
> _______________________________________________
> Hipsec mailing list
> Hipsec@ietf.org
> https://www.ietf.org/mailman/listinfo/hipsec
>

From jpellikk@ee.oulu.fi  Fri Nov 12 05:32:17 2010
Return-Path: <jpellikk@ee.oulu.fi>
X-Original-To: hipsec@core3.amsl.com
Delivered-To: hipsec@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id A43543A6B40 for <hipsec@core3.amsl.com>; Fri, 12 Nov 2010 05:32:17 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level: 
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id hzdIvofHb5Gl for <hipsec@core3.amsl.com>; Fri, 12 Nov 2010 05:32:10 -0800 (PST)
Received: from ees2.oulu.fi (ee.oulu.fi [130.231.61.23]) by core3.amsl.com (Postfix) with ESMTP id 60E763A6B48 for <hipsec@ietf.org>; Fri, 12 Nov 2010 05:32:09 -0800 (PST)
Received: from [10.100.11.140] (ee-gw5 [130.231.61.15]) (authenticated bits=0) by ees2.oulu.fi (8.13.8/8.13.8) with ESMTP id oACDWfAq020874 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO) for <hipsec@ietf.org>; Fri, 12 Nov 2010 15:32:41 +0200
Message-ID: <4CDD41FD.7090400@ee.oulu.fi>
Date: Fri, 12 Nov 2010 15:32:45 +0200
From: Jani Pellikka <jpellikk@ee.oulu.fi>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.1; en-US; rv:1.9.2.8) Gecko/20100802 Lightning/1.0b2 Thunderbird/3.1.2
MIME-Version: 1.0
To: hipsec@ietf.org
X-Enigmail-Version: 1.1.1
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Subject: [Hipsec] First HIP certificate requests draft
X-BeenThere: hipsec@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
Reply-To: jpellikk@ee.oulu.fi
List-Id: "This is the official IETF Mailing List for the HIP Working Group." <hipsec.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/hipsec>, <mailto:hipsec-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/hipsec>
List-Post: <mailto:hipsec@ietf.org>
List-Help: <mailto:hipsec-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/hipsec>, <mailto:hipsec-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 12 Nov 2010 13:32:17 -0000

Hi,

I have uploaded the first draft of "HIP Certificate Requests", which was
I believe briefly presented in the Beijing meeting by Andrei a few days ago.

I hope I could get some feedback on it.

http://www.ietf.org/id/draft-pellikka-hiprg-certreq-00.txt

Filename:	 draft-pellikka-hiprg-certreq
Revision:	 00
Title:		 HIP Certificate Requests
Creation_date:	 2010-11-12
WG ID:		 Independent Submission
Number_of_pages: 6

Best Regards,
Jani Pellikka

-- 
Jani Pellikka
Centre for Wireless Communications (CWC)
University of Oulu, P.O. Box 4500
FI-90014, University of Oulu, Finland
Tel: +358 8 553 2965, Fax: +358 8 553 2845
jpellikk@ee.oulu.fi, http://www.cwc.oulu.fi

From Internet-Drafts@ietf.org  Fri Nov 19 04:15:06 2010
Return-Path: <Internet-Drafts@ietf.org>
X-Original-To: hipsec@core3.amsl.com
Delivered-To: hipsec@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 4121828B56A; Fri, 19 Nov 2010 04:15:06 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.375
X-Spam-Level: 
X-Spam-Status: No, score=-102.375 tagged_above=-999 required=5 tests=[AWL=0.224, BAYES_00=-2.599, 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 9DZ+rtoAfwEl; Fri, 19 Nov 2010 04:15:03 -0800 (PST)
Received: from [127.0.0.1] (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 292213A68D5; Fri, 19 Nov 2010 04:15:02 -0800 (PST)
MIME-Version: 1.0
Content-Type: Multipart/Mixed; Boundary="NextPart"
From: Internet-Drafts@ietf.org
To: i-d-announce@ietf.org
X-Test-IDTracker: no
X-IETF-IDTracker: 3.09
Message-ID: <20101119121502.19627.23641.idtracker@localhost>
Date: Fri, 19 Nov 2010 04:15:02 -0800
Cc: hipsec@ietf.org
Subject: [Hipsec] I-D Action:draft-ietf-hip-cert-06.txt
X-BeenThere: hipsec@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: "This is the official IETF Mailing List for the HIP Working Group." <hipsec.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/hipsec>, <mailto:hipsec-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/hipsec>
List-Post: <mailto:hipsec@ietf.org>
List-Help: <mailto:hipsec-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/hipsec>, <mailto:hipsec-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 19 Nov 2010 12:15:06 -0000

--NextPart

A New Internet-Draft is available from the on-line Internet-Drafts directories.
This draft is a work item of the Host Identity Protocol Working Group of the IETF.


	Title           : Host Identity Protocol Certificates
	Author(s)       : T. Heer, S. Varjonen
	Filename        : draft-ietf-hip-cert-06.txt
	Pages           : 13
	Date            : 2010-11-19

The CERT parameter is a container for X.509.v3 certificates and
Simple Public Key Infrastructure (SPKI) certificates.  It is used for
carrying these certificates in Host Identity Protocol (HIP) control
packets.  This document specifies the certificate parameter and the
error signaling in case of a failed verification.  Additionally, this
document specifies the representations of Host Identity Tags in
X.509.v3 and SPKI certificates.

The concrete use of certificates including how certificates are
obtained, requested, and which actions are taken upon successful or
failed verification are specific to the scenario in which the
certificates are used.  Hence, the definition of these scenario-
specific aspects are left to the documents that use the CERT
parameter.

A URL for this Internet-Draft is:
http://www.ietf.org/internet-drafts/draft-ietf-hip-cert-06.txt

Internet-Drafts are also available by anonymous FTP at:
ftp://ftp.ietf.org/internet-drafts/

Below is the data which will enable a MIME compliant mail reader
implementation to automatically retrieve the ASCII version of the
Internet-Draft.

--NextPart
Content-Type: Message/External-body; name="draft-ietf-hip-cert-06.txt";
	site="ftp.ietf.org"; access-type="anon-ftp";
	directory="internet-drafts"

Content-Type: text/plain
Content-ID: <2010-11-19040455.I-D@ietf.org>


--NextPart--
