
From thomas.r.henderson@boeing.com  Mon Mar  1 08:43:41 2010
Return-Path: <thomas.r.henderson@boeing.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 9620328C2EC for <hipsec@core3.amsl.com>; Mon,  1 Mar 2010 08:43:41 -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 FQeR8iQlO7a1 for <hipsec@core3.amsl.com>; Mon,  1 Mar 2010 08:43:41 -0800 (PST)
Received: from stl-smtpout-01.boeing.com (stl-smtpout-01.boeing.com [130.76.96.56]) by core3.amsl.com (Postfix) with ESMTP id DB1383A8B95 for <hipsec@ietf.org>; Mon,  1 Mar 2010 08:43:40 -0800 (PST)
Received: from slb-av-01.boeing.com (slb-av-01.boeing.com [129.172.13.4]) by stl-smtpout-01.ns.cs.boeing.com (8.14.4/8.14.4/8.14.4/SMTPOUT) with ESMTP id o21GhZh1010747 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=FAIL); Mon, 1 Mar 2010 10:43:36 -0600 (CST)
Received: from slb-av-01.boeing.com (localhost [127.0.0.1]) by slb-av-01.boeing.com (8.14.4/8.14.4/DOWNSTREAM_RELAY) with ESMTP id o21GhZHc028491; Mon, 1 Mar 2010 08:43:35 -0800 (PST)
Received: from XCH-NWHT-01.nw.nos.boeing.com (xch-nwht-01.nw.nos.boeing.com [130.247.70.222]) by slb-av-01.boeing.com (8.14.4/8.14.4/UPSTREAM_RELAY) with ESMTP id o21GhZQv028470 (version=TLSv1/SSLv3 cipher=RC4-MD5 bits=128 verify=OK); Mon, 1 Mar 2010 08:43:35 -0800 (PST)
Received: from XCH-NW-10V.nw.nos.boeing.com ([130.247.25.83]) by XCH-NWHT-01.nw.nos.boeing.com ([130.247.70.222]) with mapi; Mon, 1 Mar 2010 08:43:35 -0800
From: "Henderson, Thomas R" <thomas.r.henderson@boeing.com>
To: "hip-chairs@tools.ietf.org" <hip-chairs@tools.ietf.org>
Date: Mon, 1 Mar 2010 08:43:34 -0800
Thread-Topic: tracker for issues on the bis documents
Thread-Index: Acq5XlVJXYkEkaFrS1ORirH7zTRFYw==
Message-ID: <7CC566635CFE364D87DC5803D4712A6C4C1F48A82C@XCH-NW-10V.nw.nos.boeing.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: en-US
x-tm-as-product-ver: SMEX-8.0.0.1181-6.000.1038-17218.004
x-tm-as-result: No--38.908000-8.000000-31
x-tm-as-user-approved-sender: No
x-tm-as-user-blocked-sender: No
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Cc: "hipsec@ietf.org" <hipsec@ietf.org>
Subject: [Hipsec] tracker for issues on the bis documents
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, 01 Mar 2010 16:43:41 -0000

Gonzalo, I lost track of where the WG decided to place tracker issues for t=
he "bis" documents.  I didn't see any linked from the hip tools page at :ht=
tp://tools.ietf.org/wg/hip/
or from the Issues tab:  http://trac.tools.ietf.org/wg/hip/trac/report/1

Can you suggest where we can start to log issues?

Thanks,
Tom

From ari.keranen@nomadiclab.com  Mon Mar  1 09:08:33 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 84EAC28C472 for <hipsec@core3.amsl.com>; Mon,  1 Mar 2010 09:08:33 -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 IC-yHNqSnI0V for <hipsec@core3.amsl.com>; Mon,  1 Mar 2010 09:08:32 -0800 (PST)
Received: from gw.nomadiclab.com (unknown [IPv6:2001:14b8:400:101::2]) by core3.amsl.com (Postfix) with ESMTP id 313ED3A77D0 for <hipsec@ietf.org>; Mon,  1 Mar 2010 09:08:31 -0800 (PST)
Received: from localhost (localhost [127.0.0.1]) by gw.nomadiclab.com (Postfix) with ESMTP id B0D5E4E6C5; Mon,  1 Mar 2010 19:08:31 +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 khPUULmKkCZT; Mon,  1 Mar 2010 19:08:31 +0200 (EET)
Received: from [IPv6:2001:14b8:400:101:21c:23ff:fe45:a6c1] (unknown [IPv6:2001:14b8:400:101:21c:23ff:fe45:a6c1]) by gw.nomadiclab.com (Postfix) with ESMTP id 240124E67D; Mon,  1 Mar 2010 19:08:31 +0200 (EET)
Message-ID: <4B8BF48E.2060301@nomadiclab.com>
Date: Mon, 01 Mar 2010 19:08:30 +0200
From: Ari Keranen <ari.keranen@nomadiclab.com>
User-Agent: Thunderbird 2.0.0.23 (X11/20090817)
MIME-Version: 1.0
To: "Henderson, Thomas R" <thomas.r.henderson@boeing.com>
References: <4B5F07F6.7080800@ericsson.com> <7CC566635CFE364D87DC5803D4712A6C4C1F48A7C0@XCH-NW-10V.nw.nos.boeing.com>	 <4B83F243.6070208@nomadiclab.com> <7CC566635CFE364D87DC5803D4712A6C4C1F48A7D1@XCH-NW-10V.nw.nos.boeing.com> <4B8689B0.50704@nomadiclab.com> <7CC566635CFE364D87DC5803D4712A6C4C1F48A7FF@XCH-NW-10V.nw.nos.boeing.com> <4B877153.10908@nomadiclab.com> <7CC566635CFE364D87DC5803D4712A6C4C1F48A81E@XCH-NW-10V.nw.nos.boeing.com>
In-Reply-To: <7CC566635CFE364D87DC5803D4712A6C4C1F48A81E@XCH-NW-10V.nw.nos.boeing.com>
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
Cc: HIP <hipsec@ietf.org>
Subject: Re: [Hipsec] WGLC: draft-ietf-hip-reload-instance-00
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, 01 Mar 2010 17:08:33 -0000

Henderson, Thomas R wrote:
>> -----Original Message-----
>> From: Ari Keranen [mailto:ari.keranen@nomadiclab.com]
>> Sent: Thursday, February 25, 2010 11:00 PM
>> To: Henderson, Thomas R
>> Cc: 'Gonzalo Camarillo'; HIP
>> Subject: Re: [Hipsec] WGLC: draft-ietf-hip-reload-instance-00
>>
>> Henderson, Thomas R wrote:
>>>>> When you say "In the other Peer ID mode, namely "RELOAD",..."
>>>>> which case do you mean?  Just the self-generated case?  If it is
>>>>> the centralized case, the Node IDs can't be used as HITs, and
>>>>> then the Node IDs and the HITs are not related to one another and
>>>>> need to be bound by some kind of certificate framework.  This is
>>>>> what I think section 5.6.1.1 of the base draft refers to.  Or am
>>>>> I misunderstanding something?
>>>> We mean both cases.  I'm sorry but I don't follow why couldn't the
>>>> non-ORCHID Node IDs be used as "HITs" (i.e., in the HIP header, VIA
>>>>  lists and certificates) in the centralized case?
>>>>
>>> Let's say that the enrollment server allocates the first node the
>>> Node ID of "0", the second node a Node ID of "1" etc.  Are you
>>> suggesting that these values are used as HITs?
>> Yes. Although the enrollment server would not really give IDs
>> like that
>> but rather make them cryptographically random, but the point
>> remains the
>> same: the IDs in the RELOAD mode are not (necessarily) hashes
>> of public
>> keys.
>>
>>> I raised this issue in another thread yesterday, but it seems to me
>>> that a central idea in the HIP architecture is that the HIT is the
>>> hash of the public key of a public/private key pair and
>> that the host
>>> holds the private key.  I don't believe we've talked before
>> about the
>>> possibility that the HI and HIT are not related cryptographically.
>> Yeah, we had a thread on the HIP list about this some half a year ago
>> but it died away. I admit that the HIT being a hash of a
>> public key is
>> somewhat central idea in HIP, but is it really necessary if
>> you have a
>> certificate that can provide the same binding between the
>> non-HIT-ID and
>> Host ID?
>>
>> AFAIK, you only lose the property that for someone else it's
>> really hard
>> to generate the same identity, but with an enrollment server
>> that would
>> not be a problem thanks to the certificates. Without an enrollment
>> server one could fake the ID in the RELOAD mode, but then you
>> can still
>> use the ORCHID mode and real HITs or generate IDs as digests
>> (SHA-1 or
>> SHA-256) of the public key as the RELOAD draft proposes.
>>
> 
> I think we should really explore this idea more but let's do so in the more RFC4423bis context as discussed in the other thread.  I wasn't objecting to the idea per se, but just that we should not slip it into this draft if it is not really recognized as a part of HIP today.

Actually, we used to have a milestone about this in the charter, but it 
was removed last July when the WG's conclusion was that transformations 
would be context specific. So, this already is recognized as part of the 
HIP today.

> I see pros and cons to non-ORCHID HITs:
> - pro:  can be designed to be hierarchical or formatted as needed.  Can they even be IPv6 addresses?
> - con:  HITs are no longer unique.  It is really the certificate which is the unique identifier.
> It does seem more flexible and may have deployment advantages.  Does it solve the ACL problem with current HITs (that they are non-aggregatable)?  It could lead to aggregatable HITs but then the ACL will need to know the authorizing enrollment server for those HITs, and check CERTs.

These questions are good to be explored on RFC4423bis, but we don't need 
the answers to proceed with the RELOAD instance spec, so I would not 
delay the instance spec by making it depend on RFC4423bis.

Anyhow, we are not changing anything fundamental in HIP, and having this 
property we can make HIP meet the different requirements that people 
building overlays have.


Cheers,
Ari

From thomas.r.henderson@boeing.com  Mon Mar  1 09:50:19 2010
Return-Path: <thomas.r.henderson@boeing.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 B241528C411 for <hipsec@core3.amsl.com>; Mon,  1 Mar 2010 09:50:19 -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 ZUcck50P67KO for <hipsec@core3.amsl.com>; Mon,  1 Mar 2010 09:50:18 -0800 (PST)
Received: from blv-smtpout-01.boeing.com (blv-smtpout-01.boeing.com [130.76.32.69]) by core3.amsl.com (Postfix) with ESMTP id 0685628C165 for <hipsec@ietf.org>; Mon,  1 Mar 2010 09:50:07 -0800 (PST)
Received: from blv-av-01.boeing.com (blv-av-01.boeing.com [130.247.48.231]) by blv-smtpout-01.ns.cs.boeing.com (8.14.4/8.14.4/8.14.4/SMTPOUT) with ESMTP id o21HnvM9014111 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=FAIL); Mon, 1 Mar 2010 09:49:58 -0800 (PST)
Received: from blv-av-01.boeing.com (localhost [127.0.0.1]) by blv-av-01.boeing.com (8.14.4/8.14.4/DOWNSTREAM_RELAY) with ESMTP id o21Hnv1c006758; Mon, 1 Mar 2010 09:49:57 -0800 (PST)
Received: from XCH-NWHT-10.nw.nos.boeing.com (xch-nwht-10.nw.nos.boeing.com [130.247.25.113]) by blv-av-01.boeing.com (8.14.4/8.14.4/UPSTREAM_RELAY) with ESMTP id o21Hnv2e006752 (version=TLSv1/SSLv3 cipher=RC4-MD5 bits=128 verify=OK); Mon, 1 Mar 2010 09:49:57 -0800 (PST)
Received: from XCH-NW-10V.nw.nos.boeing.com ([130.247.25.83]) by XCH-NWHT-10.nw.nos.boeing.com ([130.247.25.113]) with mapi; Mon, 1 Mar 2010 09:49:57 -0800
From: "Henderson, Thomas R" <thomas.r.henderson@boeing.com>
To: "'Ari Keranen'" <ari.keranen@nomadiclab.com>
Date: Mon, 1 Mar 2010 09:49:56 -0800
Thread-Topic: [Hipsec] WGLC: draft-ietf-hip-reload-instance-00
Thread-Index: Acq5Yg8qOyIOp18/TgeK86cAM/9wGwAAefZg
Message-ID: <7CC566635CFE364D87DC5803D4712A6C4C1F48A831@XCH-NW-10V.nw.nos.boeing.com>
References: <4B5F07F6.7080800@ericsson.com> <7CC566635CFE364D87DC5803D4712A6C4C1F48A7C0@XCH-NW-10V.nw.nos.boeing.com >	 	<4B83F243.6070208@nomadiclab.com> <7CC566635CFE364D87DC5803D4712A6C4C1F48A7D1@XCH-NW-10V.nw.nos.boeing.com> <4B8689B0.50704@nomadiclab.com> <7CC566635CFE364D87DC5803D4712A6C4C1F48A7FF@XCH-NW-10V.nw.nos.boeing.com> <4B877153.10908@nomadiclab.com> <7CC566635CFE364D87DC5803D4712A6C4C1F48A81E@XCH-NW-10V.nw.nos.boeing.com> <4B8BF48E.2060301@nomadiclab.com>
In-Reply-To: <4B8BF48E.2060301@nomadiclab.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: en-US
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Cc: HIP <hipsec@ietf.org>
Subject: Re: [Hipsec] WGLC: draft-ietf-hip-reload-instance-00
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, 01 Mar 2010 17:50:20 -0000

> >
> > I think we should really explore this idea more but let's
> do so in the more RFC4423bis context as discussed in the
> other thread.  I wasn't objecting to the idea per se, but
> just that we should not slip it into this draft if it is not
> really recognized as a part of HIP today.
>
> Actually, we used to have a milestone about this in the
> charter, but it
> was removed last July when the WG's conclusion was that
> transformations
> would be context specific. So, this already is recognized as
> part of the
> HIP today.

Can you point me to a document that shows where this is recognized as part =
of HIP today?

>
> > I see pros and cons to non-ORCHID HITs:
> > - pro:  can be designed to be hierarchical or formatted as
> needed.  Can they even be IPv6 addresses?
> > - con:  HITs are no longer unique.  It is really the
> certificate which is the unique identifier.
> > It does seem more flexible and may have deployment
> advantages.  Does it solve the ACL problem with current HITs
> (that they are non-aggregatable)?  It could lead to
> aggregatable HITs but then the ACL will need to know the
> authorizing enrollment server for those HITs, and check CERTs.
>
> These questions are good to be explored on RFC4423bis, but we
> don't need
> the answers to proceed with the RELOAD instance spec, so I would not
> delay the instance spec by making it depend on RFC4423bis.
>
> Anyhow, we are not changing anything fundamental in HIP, and
> having this
> property we can make HIP meet the different requirements that people
> building overlays have.
>

I disagree that this changes anything fundamental:  RFC5201, section 3.1:
3.1.  Host Identity Tag (HIT)

   The Host Identity Tag is a 128-bit value -- a hashed encoding of the
   Host Identifier.

I am not opposed to relaxing this in principle but I do not recall that we =
have agreed on how to do this.

- Tom

From gonzalo.camarillo@ericsson.com  Tue Mar  2 00:28:02 2010
Return-Path: <gonzalo.camarillo@ericsson.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 9079328C0E9 for <hipsec@core3.amsl.com>; Tue,  2 Mar 2010 00:28:02 -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 6rPRsOSnM5kq for <hipsec@core3.amsl.com>; Tue,  2 Mar 2010 00:28:01 -0800 (PST)
Received: from mailgw10.se.ericsson.net (mailgw10.se.ericsson.net [193.180.251.61]) by core3.amsl.com (Postfix) with ESMTP id 99E7A3A89A6 for <hipsec@ietf.org>; Tue,  2 Mar 2010 00:28:01 -0800 (PST)
X-AuditID: c1b4fb3d-b7c72ae00000040e-e4-4b8ccc111b30
Received: from esealmw129.eemea.ericsson.se (Unknown_Domain [153.88.253.125]) by mailgw10.se.ericsson.net (Symantec Brightmail Gateway) with SMTP id AF.70.01038.11CCC8B4; Tue,  2 Mar 2010 09:28:01 +0100 (CET)
Received: from esealmw129.eemea.ericsson.se ([153.88.254.177]) by esealmw129.eemea.ericsson.se with Microsoft SMTPSVC(6.0.3790.3959);  Tue, 2 Mar 2010 09:28:00 +0100
Received: from [131.160.126.169] ([131.160.126.169]) by esealmw129.eemea.ericsson.se with Microsoft SMTPSVC(6.0.3790.3959);  Tue, 2 Mar 2010 09:28:00 +0100
Message-ID: <4B8CCC10.2010502@ericsson.com>
Date: Tue, 02 Mar 2010 10:28:00 +0200
From: Gonzalo Camarillo <Gonzalo.Camarillo@ericsson.com>
User-Agent: Thunderbird 2.0.0.23 (Windows/20090812)
MIME-Version: 1.0
To: "Henderson, Thomas R" <thomas.r.henderson@boeing.com>
References: <7CC566635CFE364D87DC5803D4712A6C4C1F48A82C@XCH-NW-10V.nw.nos.boeing.com>
In-Reply-To: <7CC566635CFE364D87DC5803D4712A6C4C1F48A82C@XCH-NW-10V.nw.nos.boeing.com>
X-Enigmail-Version: 0.96.0
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
X-OriginalArrivalTime: 02 Mar 2010 08:28:00.0345 (UTC) FILETIME=[44EA8C90:01CAB9E2]
X-Brightmail-Tracker: AAAAAA==
Cc: "hipsec@ietf.org" <hipsec@ietf.org>, "hip-chairs@tools.ietf.org" <hip-chairs@tools.ietf.org>
Subject: Re: [Hipsec] tracker for issues on the bis documents
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, 02 Mar 2010 08:28:02 -0000

Hi Tom,

yes, we decided to use that tracker but nobody has logged anything yet.
If you need to create an account or need the chairs to grant you access
rights, let us know off line and we will fix it.

Cheers,

Gonzalo


Henderson, Thomas R wrote:
> Gonzalo, I lost track of where the WG decided to place tracker issues for the "bis" documents.  I didn't see any linked from the hip tools page at :http://tools.ietf.org/wg/hip/
> or from the Issues tab:  http://trac.tools.ietf.org/wg/hip/trac/report/1
> 
> Can you suggest where we can start to log issues?
> 
> Thanks,
> Tom
> _______________________________________________
> Hipsec mailing list
> Hipsec@ietf.org
> https://www.ietf.org/mailman/listinfo/hipsec


From ari.keranen@nomadiclab.com  Tue Mar  2 00:36:56 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 B62C23A863F for <hipsec@core3.amsl.com>; Tue,  2 Mar 2010 00:36:56 -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 UCAWHshT7OuS for <hipsec@core3.amsl.com>; Tue,  2 Mar 2010 00:36:55 -0800 (PST)
Received: from gw.nomadiclab.com (n2.nomadiclab.com [IPv6:2001:14b8:400:101::2]) by core3.amsl.com (Postfix) with ESMTP id 707A23A70E2 for <hipsec@ietf.org>; Tue,  2 Mar 2010 00:36:55 -0800 (PST)
Received: from localhost (localhost [127.0.0.1]) by gw.nomadiclab.com (Postfix) with ESMTP id 225C54E6D7; Tue,  2 Mar 2010 10:36:55 +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 h9249RYjyEol; Tue,  2 Mar 2010 10:36:54 +0200 (EET)
Received: from [IPv6:2001:14b8:400:101:21c:23ff:fe45:a6c1] (unknown [IPv6:2001:14b8:400:101:21c:23ff:fe45:a6c1]) by gw.nomadiclab.com (Postfix) with ESMTP id 79AFE4E6C3; Tue,  2 Mar 2010 10:36:54 +0200 (EET)
Message-ID: <4B8CCE26.7010104@nomadiclab.com>
Date: Tue, 02 Mar 2010 10:36:54 +0200
From: Ari Keranen <ari.keranen@nomadiclab.com>
User-Agent: Thunderbird 2.0.0.23 (X11/20090817)
MIME-Version: 1.0
To: "Henderson, Thomas R" <thomas.r.henderson@boeing.com>
References: <4B5F07F6.7080800@ericsson.com> <7CC566635CFE364D87DC5803D4712A6C4C1F48A7C0@XCH-NW-10V.nw.nos.boeing.com	>	 <4B83F243.6070208@nomadiclab.com> <7CC566635CFE364D87DC5803D4712A6C4C1F48A7D1@XCH-NW-10V.nw.nos.boeing.com>	 <4B8689B0.50704@nomadiclab.com> <7CC566635CFE364D87DC5803D4712A6C4C1F48A7FF@XCH-NW-10V.nw.nos.boeing.com> <4B877153.10908@nomadiclab.com> <7CC566635CFE364D87DC5803D4712A6C4C1F48A81E@XCH-NW-10V.nw.nos.boeing.com> <4B8BF48E.2060301@nomadiclab.com> <7CC566635CFE364D87DC5803D4712A6C4C1F48A831@XCH-NW-10V.nw.nos.boeing.com>
In-Reply-To: <7CC566635CFE364D87DC5803D4712A6C4C1F48A831@XCH-NW-10V.nw.nos.boeing.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Cc: HIP <hipsec@ietf.org>
Subject: Re: [Hipsec] WGLC: draft-ietf-hip-reload-instance-00
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, 02 Mar 2010 08:36:56 -0000

Henderson, Thomas R wrote:
>>> I think we should really explore this idea more but let's4
>> do so in the more RFC4423bis context as discussed in the other
>> thread.  I wasn't objecting to the idea per se, but just that we
>> should not slip it into this draft if it is not really recognized
>> as a part of HIP today.
>> 
>> Actually, we used to have a milestone about this in the charter,
>> but it was removed last July when the WG's conclusion was that 
>> transformations would be context specific. So, this already is
>> recognized as part of the HIP today.
> 
> Can you point me to a document that shows where this is recognized as
> part of HIP today?

The WG overlay documents, HIP BONE and RELOAD instance, have reflected 
this. Yes, they are not RFCs, but my point was that this is nothing we 
have introduced here out of the blue.

>>> I see pros and cons to non-ORCHID HITs: - pro:  can be designed
>>> to be hierarchical or formatted as
>> needed.  Can they even be IPv6 addresses?
>>> - con:  HITs are no longer unique.  It is really the
>> certificate which is the unique identifier.
>>> It does seem more flexible and may have deployment
>> advantages.  Does it solve the ACL problem with current HITs (that
>> they are non-aggregatable)?  It could lead to aggregatable HITs but
>> then the ACL will need to know the authorizing enrollment server
>> for those HITs, and check CERTs.
>> 
>> These questions are good to be explored on RFC4423bis, but we don't
>> need the answers to proceed with the RELOAD instance spec, so I
>> would not delay the instance spec by making it depend on
>> RFC4423bis.
>> 
>> Anyhow, we are not changing anything fundamental in HIP, and having
>> this property we can make HIP meet the different requirements that
>> people building overlays have.
>> 
> 
> I disagree that this changes anything fundamental:  RFC5201, section
> 3.1: 3.1.  Host Identity Tag (HIT)
> 
> The Host Identity Tag is a 128-bit value -- a hashed encoding of the 
> Host Identifier.

OK, that's true, only the "ORCHID mode" identifiers are strictly HITs in 
that sense so we could call the generic RELOAD mode IDs something else. 
Perhaps RITs?

> I am not opposed to relaxing this in principle but I do not recall
> that we have agreed on how to do this.

When we removed the generic transformation milestone from the charter, 
the conclusion was that the transformation (or Node ID generation) would 
be done in different ways depending on the peer protocol and thus better 
defined in the instance specs. And that's what the RELOAD instance spec 
now does. Also, if the ID is generated as the RELOAD draft proposes (SHA 
of the public key; which you could use also as the the Host ID), it 
actually even fits nicely to the definition of HIT.


Cheers,
Ari

From heer@informatik.rwth-aachen.de  Tue Mar  2 07:28:23 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 C5FC93A8B4E for <hipsec@core3.amsl.com>; Tue,  2 Mar 2010 07:28:23 -0800 (PST)
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 B9QDTcWUaYKZ for <hipsec@core3.amsl.com>; Tue,  2 Mar 2010 07:28:22 -0800 (PST)
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 782733A8B36 for <hipsec@ietf.org>; Tue,  2 Mar 2010 07:28:22 -0800 (PST)
MIME-version: 1.0
Content-transfer-encoding: 7BIT
Content-type: text/plain; charset=us-ascii
Received: from ironport-out-2.rz.rwth-aachen.de ([134.130.5.41]) 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 <0KYN00938UZAVHC0@mta-2.ms.rz.RWTH-Aachen.de> for hipsec@ietf.org; Tue, 02 Mar 2010 16:28:22 +0100 (CET)
X-IronPort-AV: E=Sophos;i="4.49,567,1262559600";   d="scan'208";a="25327748"
Received: from relay-auth-1.ms.rz.rwth-aachen.de (HELO relay-auth-1) ([134.130.7.78]) by ironport-in-2.rz.rwth-aachen.de with ESMTP; Tue, 02 Mar 2010 16:28:22 +0100
Received: from umic-137-226-154-185.nn.rwth-aachen.de ([unknown] [137.226.154.185]) by relay-auth-1.ms.rz.rwth-aachen.de (Sun Java(tm) System Messaging Server 7.0-3.01 64bit (built Dec 9 2008)) with ESMTPA id <0KYN00KKAUZA7Q70@relay-auth-1.ms.rz.rwth-aachen.de> for hipsec@ietf.org; Tue, 02 Mar 2010 16:28:22 +0100 (CET)
From: Tobias Heer <heer@cs.rwth-aachen.de>
Date: Tue, 02 Mar 2010 16:28:26 +0100
Message-id: <A06A3401-7765-45C4-A53B-208993B7071C@cs.rwth-aachen.de>
To: Julien Laganier <julienl@qualcomm.com>, Thomas R Henderson <thomas.r.henderson@boeing.com>
X-Mailer: Apple Mail (2.1077)
Cc: "hipsec@ietf.org WG" <hipsec@ietf.org>
Subject: [Hipsec] Orchid generation algorithm - where should it be specified?
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, 02 Mar 2010 15:28:23 -0000

Hello Julien and Tom, 

the algorithm for generating the hash part of the HITs in the new ORCHID format and its index should be specified somewhere. The question is where.

Since not all protocols that use ORCHIDS are required to use the same bits/algorithms, it might make sense to specify the actual ID and algorithm in the context of the protocol that uses the ORCHID.
In our case, we could start with a simple allocation for:

ID 0 - SHA2-256 truncated to 96 bits

This could be defined in any HIP document. I think RFC5201-bis would make sense, wouldn't it?
We can later extend it to use some hash chain extension mechanism (e.g., as ID 1) but I think a simple mechanism is a good start.

Any opinions on this?

Tobias
 





--  

Dipl.-Inform. Tobias Heer, Ph.D. Student
Distributed Systems Group 
RWTH Aachen University, Germany
tel: +49 241 80 207 76
web: http://ds.cs.rwth-aachen.de/members/heer








From julienl@qualcomm.com  Tue Mar  2 08:19:35 2010
Return-Path: <julienl@qualcomm.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 CF42A28C163 for <hipsec@core3.amsl.com>; Tue,  2 Mar 2010 08:19:35 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -106.599
X-Spam-Level: 
X-Spam-Status: No, score=-106.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id oAP4pwSnkQ+4 for <hipsec@core3.amsl.com>; Tue,  2 Mar 2010 08:19:34 -0800 (PST)
Received: from wolverine02.qualcomm.com (wolverine02.qualcomm.com [199.106.114.251]) by core3.amsl.com (Postfix) with ESMTP id 8A4DD28C111 for <hipsec@ietf.org>; Tue,  2 Mar 2010 08:19:34 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=qualcomm.com; i=julienl@qualcomm.com; q=dns/txt; s=qcdkim; t=1267546776; x=1299082776; h=from:to:cc:date:subject:thread-topic:thread-index: message-id:references:in-reply-to:accept-language: content-language:x-ms-has-attach:x-ms-tnef-correlator: acceptlanguage:content-type:content-transfer-encoding: mime-version; z=From:=20"Laganier,=20Julien"=20<julienl@qualcomm.com> |To:=20Tobias=20Heer=20<heer@cs.rwth-aachen.de>,=20Thomas =20R=20Henderson=0D=0A=09<thomas.r.henderson@boeing.com> |CC:=20"hipsec@ietf.org=20WG"=20<hipsec@ietf.org>|Date: =20Tue,=202=20Mar=202010=2008:19:30=20-0800|Subject:=20RE :=20Orchid=20generation=20algorithm=20-=20where=20should =20it=20be=20specified?|Thread-Topic:=20Orchid=20generati on=20algorithm=20-=20where=20should=20it=20be=20specified ?|Thread-Index:=20Acq6HQFRfWovKopxThqPJUotU+OLVQABvcMQ |Message-ID:=20<BF345F63074F8040B58C00A186FCA57F1C6A8C3F1 E@NALASEXMB04.na.qualcomm.com>|References:=20<A06A3401-77 65-45C4-A53B-208993B7071C@cs.rwth-aachen.de>|In-Reply-To: =20<A06A3401-7765-45C4-A53B-208993B7071C@cs.rwth-aachen.d e>|Accept-Language:=20en-US|Content-Language:=20en-US |X-MS-Has-Attach:|X-MS-TNEF-Correlator:|acceptlanguage: =20en-US|Content-Type:=20text/plain=3B=20charset=3D"us-as cii"|Content-Transfer-Encoding:=20quoted-printable |MIME-Version:=201.0; bh=VfXl7MeUss/DF6kNXUBOF33mv0krkBvLDKWrIV9Mqeg=; b=y1VPBTE9lWLindvNkRd5X1oIJi7g9SzmvDC7ykh/C/pK2qOR6yIm83ha f+68S+ig57nFKhJg0uyRmx5+OLw3cFvTLKZsALXcdGT63OQefIle396KP XKbXUb1SAZSzkFeBVEMg4v+mf0/wYa8hrHfurfj/o8/bW58fSwmg5657F 0=;
X-IronPort-AV: E=McAfee;i="5400,1158,5908"; a="35389543"
Received: from ironrogue.qualcomm.com ([129.46.61.164]) by wolverine02.qualcomm.com with ESMTP; 02 Mar 2010 08:19:35 -0800
X-IronPort-AV: E=Sophos;i="4.49,567,1262592000"; d="scan'208";a="47612519"
Received: from nasanexhub02.na.qualcomm.com ([10.46.143.120]) by ironrogue.qualcomm.com with ESMTP/TLS/RC4-MD5; 02 Mar 2010 08:19:35 -0800
Received: from nalasexhub02.na.qualcomm.com (10.47.130.89) by nasanexhub02.na.qualcomm.com (10.46.143.120) with Microsoft SMTP Server (TLS) id 8.2.234.1; Tue, 2 Mar 2010 08:19:35 -0800
Received: from NALASEXMB04.na.qualcomm.com ([10.47.7.114]) by nalasexhub02.na.qualcomm.com ([10.47.130.89]) with mapi; Tue, 2 Mar 2010 08:19:36 -0800
From: "Laganier, Julien" <julienl@qualcomm.com>
To: Tobias Heer <heer@cs.rwth-aachen.de>, Thomas R Henderson <thomas.r.henderson@boeing.com>
Date: Tue, 2 Mar 2010 08:19:30 -0800
Thread-Topic: Orchid generation algorithm - where should it be specified?
Thread-Index: Acq6HQFRfWovKopxThqPJUotU+OLVQABvcMQ
Message-ID: <BF345F63074F8040B58C00A186FCA57F1C6A8C3F1E@NALASEXMB04.na.qualcomm.com>
References: <A06A3401-7765-45C4-A53B-208993B7071C@cs.rwth-aachen.de>
In-Reply-To: <A06A3401-7765-45C4-A53B-208993B7071C@cs.rwth-aachen.de>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: en-US
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Cc: "hipsec@ietf.org WG" <hipsec@ietf.org>
Subject: Re: [Hipsec] Orchid generation algorithm - where should it be specified?
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, 02 Mar 2010 16:19:36 -0000

Hello Tobias,

Tobias Heer wrote:
>=20
> Hello Julien and Tom,
>=20
> the algorithm for generating the hash part of the HITs in the new
> ORCHID format and its index should be specified somewhere. The question
> is where.
>=20
> Since not all protocols that use ORCHIDS are required to use the same
> bits/algorithms, it might make sense to specify the actual ID and
> algorithm in the context of the protocol that uses the ORCHID.

I agree.

> In our case, we could start with a simple allocation for:
>=20
> ID 0 - SHA2-256 truncated to 96 bits
>=20
> This could be defined in any HIP document. I think RFC5201-bis would
> make sense, wouldn't it?
> We can later extend it to use some hash chain extension mechanism (e.g.,
> as ID 1) but I think a simple mechanism is a good start.
>=20
> Any opinions on this?

I agree that 5201bis is the logical place to do that.

--julien

From thomas.r.henderson@boeing.com  Tue Mar  2 08:44:36 2010
Return-Path: <thomas.r.henderson@boeing.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 5723928C14E for <hipsec@core3.amsl.com>; Tue,  2 Mar 2010 08:44:36 -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=[AWL=0.000,  BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id jqQzPbVTczV9 for <hipsec@core3.amsl.com>; Tue,  2 Mar 2010 08:44:35 -0800 (PST)
Received: from blv-smtpout-01.boeing.com (blv-smtpout-01.boeing.com [130.76.32.69]) by core3.amsl.com (Postfix) with ESMTP id 7E3D93A8B99 for <hipsec@ietf.org>; Tue,  2 Mar 2010 08:44:35 -0800 (PST)
Received: from stl-av-01.boeing.com (stl-av-01.boeing.com [192.76.190.6]) by blv-smtpout-01.ns.cs.boeing.com (8.14.4/8.14.4/8.14.4/SMTPOUT) with ESMTP id o22GiRbp006685 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=FAIL); Tue, 2 Mar 2010 08:44:30 -0800 (PST)
Received: from stl-av-01.boeing.com (localhost [127.0.0.1]) by stl-av-01.boeing.com (8.14.4/8.14.4/DOWNSTREAM_RELAY) with ESMTP id o22GiRXo011924; Tue, 2 Mar 2010 10:44:27 -0600 (CST)
Received: from XCH-NWHT-08.nw.nos.boeing.com (xch-nwht-08.nw.nos.boeing.com [130.247.25.112]) by stl-av-01.boeing.com (8.14.4/8.14.4/UPSTREAM_RELAY) with ESMTP id o22GiAnm011252 (version=TLSv1/SSLv3 cipher=RC4-MD5 bits=128 verify=OK); Tue, 2 Mar 2010 10:44:27 -0600 (CST)
Received: from XCH-NW-10V.nw.nos.boeing.com ([130.247.25.83]) by XCH-NWHT-08.nw.nos.boeing.com ([130.247.25.112]) with mapi; Tue, 2 Mar 2010 08:44:14 -0800
From: "Henderson, Thomas R" <thomas.r.henderson@boeing.com>
To: "'Laganier, Julien'" <julienl@qualcomm.com>, Tobias Heer <heer@cs.rwth-aachen.de>
Date: Tue, 2 Mar 2010 08:44:13 -0800
Thread-Topic: Orchid generation algorithm - where should it be specified?
Thread-Index: Acq6HQFRfWovKopxThqPJUotU+OLVQABvcMQAADlmBA=
Message-ID: <7CC566635CFE364D87DC5803D4712A6C4C1F48A839@XCH-NW-10V.nw.nos.boeing.com>
References: <A06A3401-7765-45C4-A53B-208993B7071C@cs.rwth-aachen.de> <BF345F63074F8040B58C00A186FCA57F1C6A8C3F1E@NALASEXMB04.na.qualcomm.com>
In-Reply-To: <BF345F63074F8040B58C00A186FCA57F1C6A8C3F1E@NALASEXMB04.na.qualcomm.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: en-US
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Cc: "hipsec@ietf.org WG" <hipsec@ietf.org>
Subject: Re: [Hipsec] Orchid generation algorithm - where should it be specified?
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, 02 Mar 2010 16:44:36 -0000

> -----Original Message-----
> From: Laganier, Julien [mailto:julienl@qualcomm.com]
> Sent: Tuesday, March 02, 2010 8:20 AM
> To: Tobias Heer; Henderson, Thomas R
> Cc: hipsec@ietf.org WG
> Subject: RE: Orchid generation algorithm - where should it be
> specified?
>
> Hello Tobias,
>
> Tobias Heer wrote:
> >
> > Hello Julien and Tom,
> >
> > the algorithm for generating the hash part of the HITs in the new
> > ORCHID format and its index should be specified somewhere.
> The question
> > is where.
> >
> > Since not all protocols that use ORCHIDS are required to
> use the same
> > bits/algorithms, it might make sense to specify the actual ID and
> > algorithm in the context of the protocol that uses the ORCHID.
>
> I agree.
>
> > In our case, we could start with a simple allocation for:
> >
> > ID 0 - SHA2-256 truncated to 96 bits
> >
> > This could be defined in any HIP document. I think RFC5201-bis would
> > make sense, wouldn't it?
> > We can later extend it to use some hash chain extension
> mechanism (e.g.,
> > as ID 1) but I think a simple mechanism is a good start.
> >
> > Any opinions on this?
>
> I agree that 5201bis is the logical place to do that.
>

+1

Tom

From jan.melen@nomadiclab.com  Wed Mar  3 12:30:23 2010
Return-Path: <jan.melen@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 B777E28C26F for <hipsec@core3.amsl.com>; Wed,  3 Mar 2010 12:30:23 -0800 (PST)
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 FWH-tUbnoDLR for <hipsec@core3.amsl.com>; Wed,  3 Mar 2010 12:30:21 -0800 (PST)
Received: from smtp.melen.org (foxgw.melen.org [84.20.145.65]) by core3.amsl.com (Postfix) with ESMTP id D1C8428C171 for <hipsec@ietf.org>; Wed,  3 Mar 2010 12:30:15 -0800 (PST)
Received: from esealmw967.eemea.ericsson.se ([IPv6:2001:14b8:400:f00::25]) by smtp.melen.org (8.14.3/8.14.3) with ESMTP id o23J8aes068544; Wed, 3 Mar 2010 19:08:36 GMT (envelope-from jan.melen@nomadiclab.com)
Mime-Version: 1.0 (Apple Message framework v1077)
Content-Type: multipart/alternative; boundary=Apple-Mail-200--574177288
From: Jan Melen <jan.melen@nomadiclab.com>
In-Reply-To: <7CC566635CFE364D87DC5803D4712A6C4C1F48A7BF@XCH-NW-10V.nw.nos.boeing.com>
Date: Wed, 3 Mar 2010 21:08:35 +0200
Message-Id: <79B9C9FA-E49A-4103-B1DA-741FC0389635@nomadiclab.com>
References: <4B5F07F6.7080800@ericsson.com> <7CC566635CFE364D87DC5803D4712A6C4C1F48A7BF@XCH-NW-10V.nw.nos.boeing.com>
To: "Henderson, Thomas R" <thomas.r.henderson@boeing.com>
X-Mailer: Apple Mail (2.1077)
X-Virus-Scanned: clamav-milter 0.95.3 at smtp.melen.org
X-Virus-Status: Clean
Cc: HIP <hipsec@ietf.org>
Subject: Re: [Hipsec] WGLC: draft-ietf-hip-hiccups-01
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 Mar 2010 20:30:23 -0000

--Apple-Mail-200--574177288
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=us-ascii

Hi,

Here is link to updated version:
http://users.piuha.net/jmelen/HICCUPS/draft-ietf-hip-hiccups-02.txt

On Feb 22, 2010, at 8:46 PM, Henderson, Thomas R wrote:

>=20
>=20
>> -----Original Message-----
>> From: hipsec-bounces@ietf.org
>> [mailto:hipsec-bounces@ietf.org] On Behalf Of Gonzalo Camarillo
>> Sent: Tuesday, January 26, 2010 7:19 AM
>> To: HIP
>> Subject: [Hipsec] WGLC: HIP-based overlays
>>=20
>> Folks,
>>=20
>> we would like to WGLC the set of specifications that describe how to
>> build HIP-based overlays. The documents under WGLC are the following:
>>=20
>> http://tools.ietf.org/html/draft-ietf-hip-bone-04
>> http://tools.ietf.org/html/draft-ietf-hip-reload-instance-00
>> http://tools.ietf.org/html/draft-ietf-hip-hiccups-01
>> http://tools.ietf.org/html/draft-ietf-hip-via-00
>>=20
>> This WGLC will end on February 23rd. Please, send your
>> comments to this
>> list.
>>=20
>=20
> comments on draft-ietf-hip-hiccups-01:
>=20
> Overall, I think that this document mainly makes sense in the context =
of HIP BONE and should be folded into that specification.  However, if =
kept stand-alone, it would help to clarify in the introduction that this =
specifies a data service with the following semantics:  unordered, =
duplicate free (subject to receiver ACK cache size and lifetime), =
reliable (up to a retransmission count), authenticated, and encrypted =
message-based delivery service.  I would also recommend stating that =
APIs to higher-level protocols that might use this service are outside =
the scope of this specification.
>=20


Added the semantics and that APIs are outside the scope.


>> 2. Terminology
>>=20
>>=20
>>   The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
>>   "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in =
this
>>   document are to be interpreted as described in RFC 2119 [RFC2119].
>=20
> This section is empty; probably at the very least it should point to =
the normative references that define the terminology in use later in the =
document.
>=20

Yes, added reference to RFC 5201 for terminology.


>> 3. Background on HIP
>>=20
>>=20
>>   The HIP protocol specification [RFC5201] defines a number of =
messages
>>   and parameters.  The parameters are encoded as TLVs, as shown in
>>   Section 3.1.2.  Furthermore, the HIP header carries a Next Header
>>   field, allowing other arbitrary packets to be carried within HIP
>>   packets.
>=20
> Perhaps this section could go away or be refactored if this draft is =
merged to hip-bone.
>=20
>> 4.1. Definition of the PAYLOAD_MAC Parameter
>>=20
>>     Length            length in octets, excluding Type, Length, and
>>                       Padding
>=20
> are there any minimum or maximum size limitations for this parameter?  =
Should the maximum length be tied to the maximum size that the HMAC can =
handle?


Do you mean that we should be more specific than what we are saying =
about the HMAC itself:
  Payload HMAC      HMAC computed over the data to which the Next
                     Header and Payload Data points to. The size of
                     the HMAC is the natural size of the computation
                     output depending on the used function.

>=20
>> 5.1. Handling of SEQ_DATA and ACK_DATA
>>=20
>>=20
>>   A HIP DATA packet contains zero or one SEQ_DATA parameter.  The
>>   presence of a SEQ_DATA parameter indicates that the receiver MUST =
ACK
>>   the HIP DATA packet.  A HIP DATA packet that does not contain a
>>   SEQ_DATA parameter is simply an ACK of a previous HIP DATA packet =
and
>>   MUST NOT be ACKed.
>=20
> is it legal to have a HIP DATA with zero SEQ_DATA and zero ACK_DATA?  =
If not, suggest to say that if SEQ_DATA is missing, ACK_DATA must be =
present.
>=20
> Can SEQ_DATA be present with no PAYLOAD_MAC parameter?


Fixed either SEQ_DATA or ACK_DATA must be present and in case of =
SEQ_DATA also PAYLOAD_MAC is required.


>=20
>>   packet.  A host MAY choose to hold the HIP DATA packet carrying ACK
>>   for a short period of time to allow for the possibility of
>>   piggybacking the ACK parameter, in a manner similar to TCP delayed
>>   acknowledgments.
>=20
> Should the ACK_DATA format allow for multiple sequence numbers, if so, =
to avoid carrying a Type and Length field for each one?


Yes and now it is defined.


>=20
>>   1.  The host creates a HIP DATA packet that contains a SEQ_DATA
>>       parameter.  The host is free to choose any value for the =
SEQ_DATA
>>       parameter in the first HIP DATA packet it sends to a =
destination.
>=20
> This section would be clearer if you replaced "SEQ_DATA parameter" and =
"SEQ_DATA value" with "SEQ_DATA sequence number".

Fixed.


   Thanks for reviewing the draft
       Jan



--Apple-Mail-200--574177288
Content-Transfer-Encoding: quoted-printable
Content-Type: text/html;
	charset=us-ascii

<html><head></head><body style=3D"word-wrap: break-word; =
-webkit-nbsp-mode: space; -webkit-line-break: after-white-space; =
">Hi,<div><br></div><div>Here is link to updated version:</div><div><a =
href=3D"http://users.piuha.net/jmelen/HICCUPS/draft-ietf-hip-hiccups-02.tx=
t">http://users.piuha.net/jmelen/HICCUPS/draft-ietf-hip-hiccups-02.txt</a>=
</div><div><br></div><div><div><div>On Feb 22, 2010, at 8:46 PM, =
Henderson, Thomas R wrote:</div><br =
class=3D"Apple-interchange-newline"><blockquote =
type=3D"cite"><div><br><br><blockquote type=3D"cite">-----Original =
Message-----<br></blockquote><blockquote type=3D"cite">From: <a =
href=3D"mailto:hipsec-bounces@ietf.org">hipsec-bounces@ietf.org</a><br></b=
lockquote><blockquote type=3D"cite">[mailto:hipsec-bounces@ietf.org] On =
Behalf Of Gonzalo Camarillo<br></blockquote><blockquote =
type=3D"cite">Sent: Tuesday, January 26, 2010 7:19 =
AM<br></blockquote><blockquote type=3D"cite">To: =
HIP<br></blockquote><blockquote type=3D"cite">Subject: [Hipsec] WGLC: =
HIP-based overlays<br></blockquote><blockquote =
type=3D"cite"><br></blockquote><blockquote =
type=3D"cite">Folks,<br></blockquote><blockquote =
type=3D"cite"><br></blockquote><blockquote type=3D"cite">we would like =
to WGLC the set of specifications that describe how =
to<br></blockquote><blockquote type=3D"cite">build HIP-based overlays. =
The documents under WGLC are the following:<br></blockquote><blockquote =
type=3D"cite"><br></blockquote><blockquote type=3D"cite"><a =
href=3D"http://tools.ietf.org/html/draft-ietf-hip-bone-04">http://tools.ie=
tf.org/html/draft-ietf-hip-bone-04</a><br></blockquote><blockquote =
type=3D"cite"><a =
href=3D"http://tools.ietf.org/html/draft-ietf-hip-reload-instance-00">http=
://tools.ietf.org/html/draft-ietf-hip-reload-instance-00</a><br></blockquo=
te><blockquote type=3D"cite"><a =
href=3D"http://tools.ietf.org/html/draft-ietf-hip-hiccups-01">http://tools=
.ietf.org/html/draft-ietf-hip-hiccups-01</a><br></blockquote><blockquote =
type=3D"cite"><a =
href=3D"http://tools.ietf.org/html/draft-ietf-hip-via-00">http://tools.iet=
f.org/html/draft-ietf-hip-via-00</a><br></blockquote><blockquote =
type=3D"cite"><br></blockquote><blockquote type=3D"cite">This WGLC will =
end on February 23rd. Please, send your<br></blockquote><blockquote =
type=3D"cite">comments to this<br></blockquote><blockquote =
type=3D"cite">list.<br></blockquote><blockquote =
type=3D"cite"><br></blockquote><br>comments on =
draft-ietf-hip-hiccups-01:<br><br>Overall, I think that this document =
mainly makes sense in the context of HIP BONE and should be folded into =
that specification. &nbsp;However, if kept stand-alone, it would help to =
clarify in the introduction that this specifies a data service with the =
following semantics: &nbsp;unordered, duplicate free (subject to =
receiver ACK cache size and lifetime), reliable (up to a retransmission =
count), authenticated, and encrypted message-based delivery service. =
&nbsp;I would also recommend stating that APIs to higher-level protocols =
that might use this service are outside the scope of this =
specification.<br><br></div></blockquote><div><br></div><div><br></div><di=
v>Added the semantics and that APIs are outside the =
scope.</div><div><br></div><br><blockquote type=3D"cite"><div><blockquote =
type=3D"cite">2. Terminology<br></blockquote><blockquote =
type=3D"cite"><br></blockquote><blockquote =
type=3D"cite"><br></blockquote><blockquote type=3D"cite"> =
&nbsp;&nbsp;The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", =
"SHALL NOT",<br></blockquote><blockquote type=3D"cite"> =
&nbsp;&nbsp;"SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" =
in this<br></blockquote><blockquote type=3D"cite"> &nbsp;&nbsp;document =
are to be interpreted as described in RFC 2119 =
[RFC2119].<br></blockquote><br>This section is empty; probably at the =
very least it should point to the normative references that define the =
terminology in use later in the =
document.<br><br></div></blockquote><div><br></div><div>Yes, added =
reference to RFC 5201 for =
terminology.</div><div><br></div><br><blockquote =
type=3D"cite"><div><blockquote type=3D"cite">3. Background on =
HIP<br></blockquote><blockquote type=3D"cite"><br></blockquote><blockquote=
 type=3D"cite"><br></blockquote><blockquote type=3D"cite"> =
&nbsp;&nbsp;The HIP protocol specification [RFC5201] defines a number of =
messages<br></blockquote><blockquote type=3D"cite"> &nbsp;&nbsp;and =
parameters. &nbsp;The parameters are encoded as TLVs, as shown =
in<br></blockquote><blockquote type=3D"cite"> &nbsp;&nbsp;Section 3.1.2. =
&nbsp;Furthermore, the HIP header carries a Next =
Header<br></blockquote><blockquote type=3D"cite"> &nbsp;&nbsp;field, =
allowing other arbitrary packets to be carried within =
HIP<br></blockquote><blockquote type=3D"cite"> =
&nbsp;&nbsp;packets.<br></blockquote><br>Perhaps this section could go =
away or be refactored if this draft is merged to =
hip-bone.<br><br><blockquote type=3D"cite">4.1. Definition of the =
PAYLOAD_MAC Parameter<br></blockquote><blockquote =
type=3D"cite"><br></blockquote><blockquote type=3D"cite"> =
&nbsp;&nbsp;&nbsp;&nbsp;Length =
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;length =
in octets, excluding Type, Length, and<br></blockquote><blockquote =
type=3D"cite"> =
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;Padding<br></blo=
ckquote><br>are there any minimum or maximum size limitations for this =
parameter? &nbsp;Should the maximum length be tied to the maximum size =
that the HMAC can =
handle?<br></div></blockquote><div><br></div><div><br></div><div>Do you =
mean that we should be more specific than what we are saying about the =
HMAC itself:</div><div><span class=3D"Apple-style-span" =
style=3D"font-family: Times; "><pre style=3D"word-wrap: break-word; =
white-space: pre-wrap; ">  Payload HMAC      HMAC computed over the data =
to which the Next
                     Header and Payload Data points to. The size of
                     the HMAC is the natural size of the computation
                     output depending on the used =
function.</pre></span></div><br><blockquote =
type=3D"cite"><div><br><blockquote type=3D"cite">5.1. Handling of =
SEQ_DATA and ACK_DATA<br></blockquote><blockquote =
type=3D"cite"><br></blockquote><blockquote =
type=3D"cite"><br></blockquote><blockquote type=3D"cite"> &nbsp;&nbsp;A =
HIP DATA packet contains zero or one SEQ_DATA parameter. =
&nbsp;The<br></blockquote><blockquote type=3D"cite"> =
&nbsp;&nbsp;presence of a SEQ_DATA parameter indicates that the receiver =
MUST ACK<br></blockquote><blockquote type=3D"cite"> &nbsp;&nbsp;the HIP =
DATA packet. &nbsp;A HIP DATA packet that does not contain =
a<br></blockquote><blockquote type=3D"cite"> &nbsp;&nbsp;SEQ_DATA =
parameter is simply an ACK of a previous HIP DATA packet =
and<br></blockquote><blockquote type=3D"cite"> &nbsp;&nbsp;MUST NOT be =
ACKed.<br></blockquote><br>is it legal to have a HIP DATA with zero =
SEQ_DATA and zero ACK_DATA? &nbsp;If not, suggest to say that if =
SEQ_DATA is missing, ACK_DATA must be present.<br><br>Can SEQ_DATA be =
present with no PAYLOAD_MAC =
parameter?<br></div></blockquote><div><br></div><div><br></div><div>Fixed =
either SEQ_DATA or ACK_DATA must be present and in case of SEQ_DATA also =
PAYLOAD_MAC is required.</div><div><br></div><br><blockquote =
type=3D"cite"><div><br><blockquote type=3D"cite"> &nbsp;&nbsp;packet. =
&nbsp;A host MAY choose to hold the HIP DATA packet carrying =
ACK<br></blockquote><blockquote type=3D"cite"> &nbsp;&nbsp;for a short =
period of time to allow for the possibility =
of<br></blockquote><blockquote type=3D"cite"> &nbsp;&nbsp;piggybacking =
the ACK parameter, in a manner similar to TCP =
delayed<br></blockquote><blockquote type=3D"cite"> =
&nbsp;&nbsp;acknowledgments.<br></blockquote><br>Should the ACK_DATA =
format allow for multiple sequence numbers, if so, to avoid carrying a =
Type and Length field for each =
one?<br></div></blockquote><div><br></div><div><br></div><div>Yes and =
now it is defined.</div><div><br></div><br><blockquote =
type=3D"cite"><div><br><blockquote type=3D"cite"> &nbsp;&nbsp;1. =
&nbsp;The host creates a HIP DATA packet that contains a =
SEQ_DATA<br></blockquote><blockquote type=3D"cite"> =
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;parameter. &nbsp;The host is free to =
choose any value for the SEQ_DATA<br></blockquote><blockquote =
type=3D"cite"> &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;parameter in the =
first HIP DATA packet it sends to a =
destination.<br></blockquote><br>This section would be clearer if you =
replaced "SEQ_DATA parameter" and "SEQ_DATA value" with "SEQ_DATA =
sequence =
number".<br></div></blockquote></div><br></div><div>Fixed.</div><div><br><=
/div><div><br></div><div>&nbsp;&nbsp; Thanks for reviewing the =
draft</div><div>&nbsp;&nbsp; &nbsp; &nbsp; =
Jan</div><div><br></div><div><br></div></body></html>=

--Apple-Mail-200--574177288--

From ari.keranen@nomadiclab.com  Thu Mar  4 02:27:52 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 8A3863A879D for <hipsec@core3.amsl.com>; Thu,  4 Mar 2010 02:27:52 -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 MGlHLKHO1maS for <hipsec@core3.amsl.com>; Thu,  4 Mar 2010 02:27:51 -0800 (PST)
Received: from gw.nomadiclab.com (unknown [IPv6:2001:14b8:400:101::2]) by core3.amsl.com (Postfix) with ESMTP id 08FD23A879A for <hipsec@ietf.org>; Thu,  4 Mar 2010 02:27:50 -0800 (PST)
Received: from localhost (localhost [127.0.0.1]) by gw.nomadiclab.com (Postfix) with ESMTP id 6E2F04E6D4 for <hipsec@ietf.org>; Thu,  4 Mar 2010 12:27:51 +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 zJrQrXOJMaJM for <hipsec@ietf.org>; Thu,  4 Mar 2010 12:27:50 +0200 (EET)
Received: from [IPv6:2001:14b8:400:101:21c:23ff:fe45:a6c1] (unknown [IPv6:2001:14b8:400:101:21c:23ff:fe45:a6c1]) by gw.nomadiclab.com (Postfix) with ESMTP id 6A17D4E6C5 for <hipsec@ietf.org>; Thu,  4 Mar 2010 12:27:50 +0200 (EET)
Message-ID: <4B8F8B26.4050300@nomadiclab.com>
Date: Thu, 04 Mar 2010 12:27:50 +0200
From: Ari Keranen <ari.keranen@nomadiclab.com>
User-Agent: Thunderbird 2.0.0.23 (X11/20090817)
MIME-Version: 1.0
To: HIP <hipsec@ietf.org>
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Transfer-Encoding: 7bit
Subject: [Hipsec] draft-keranen-hip-native-nat-traversal-00
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 Mar 2010 10:27:52 -0000

Hi all,

We wrote an extension to the HIP NAT traversal draft that uses the ICE 
methodology with HIP messages and an ESP relay for the NAT traversal 
procedures:

http://www.ietf.org/id/draft-keranen-hip-native-nat-traversal-00.txt

This draft addresses the issue that one may not be willing to integrate 
a full ICE implementation with HIP but rather re-use the HIP messages 
and state machines for the same purpose.

Comments are welcome!


Cheers,
Ari


-------- Original Message --------
Subject: New Version Notification for 
draft-keranen-hip-native-nat-traversal-00


A new version of I-D, draft-keranen-hip-native-nat-traversal-00.txt has 
been successfuly submitted by Ari Keranen and posted to the IETF repository.

Filename:	 draft-keranen-hip-native-nat-traversal
Revision:	 00
Title:		 Native NAT Traversal Mode for the Host Identity Protocol
Creation_date:	 2010-03-01
WG ID:		 Independent Submission
Number_of_pages: 15

Abstract:
This document specifies a new Network Address Translator (NAT)
traversal mode for the Host Identity Protocol (HIP).  The new mode is
based on the Interactive Connectivity Establishment (ICE) methodology
and UDP encapsulation of data and signaling traffic.  The main
difference from the previously specified modes is the use of HIP
messages for all NAT traversal procedures.
 



The IETF Secretariat.

From mkomu@cs.hut.fi  Thu Mar  4 02:35:18 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 3BEB928C0DC for <hipsec@core3.amsl.com>; Thu,  4 Mar 2010 02:35:18 -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 ghc2koRMAgCc for <hipsec@core3.amsl.com>; Thu,  4 Mar 2010 02:35:15 -0800 (PST)
Received: from hutcs.cs.hut.fi (hutcs.cs.hut.fi [130.233.192.7]) by core3.amsl.com (Postfix) with ESMTP id 928DA28C0D8 for <hipsec@ietf.org>; Thu,  4 Mar 2010 02:35:15 -0800 (PST)
Received: from hutcs.cs.hut.fi ([130.233.192.7] helo=[127.0.0.1]) by hutcs.cs.hut.fi with esmtpsa (TLSv1:AES256-SHA:256) (Exim 4.54) id 1Nn8Oh-0005gv-Pc for hipsec@ietf.org; Thu, 04 Mar 2010 12:35:15 +0200
Message-ID: <4B8F8CE3.6060203@cs.hut.fi>
Date: Thu, 04 Mar 2010 12:35:15 +0200
From: Miika Komu <mkomu@cs.hut.fi>
User-Agent: Mozilla/5.0 (X11; U; Linux x86_64; en-US; rv:1.9.1.9pre) Gecko/20100301 Shredder/3.0.4pre
MIME-Version: 1.0
To: hipsec@ietf.org
References: <4B8F8B26.4050300@nomadiclab.com>
In-Reply-To: <4B8F8B26.4050300@nomadiclab.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Subject: Re: [Hipsec] draft-keranen-hip-native-nat-traversal-00
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 Mar 2010 10:35:18 -0000

On 03/04/2010 12:27 PM, Ari Keranen wrote:

Hi,

based on our implementation experimentation, I would say that this is a 
better for the experimental NAT traversal work to proceed towards 
standards track.

> Hi all,
>
> We wrote an extension to the HIP NAT traversal draft that uses the ICE
> methodology with HIP messages and an ESP relay for the NAT traversal
> procedures:
>
> http://www.ietf.org/id/draft-keranen-hip-native-nat-traversal-00.txt
>
> This draft addresses the issue that one may not be willing to integrate
> a full ICE implementation with HIP but rather re-use the HIP messages
> and state machines for the same purpose.
>
> Comments are welcome!
>
>
> Cheers,
> Ari
>
>
> -------- Original Message --------
> Subject: New Version Notification for
> draft-keranen-hip-native-nat-traversal-00
>
>
> A new version of I-D, draft-keranen-hip-native-nat-traversal-00.txt has
> been successfuly submitted by Ari Keranen and posted to the IETF
> repository.
>
> Filename: draft-keranen-hip-native-nat-traversal
> Revision: 00
> Title: Native NAT Traversal Mode for the Host Identity Protocol
> Creation_date: 2010-03-01
> WG ID: Independent Submission
> Number_of_pages: 15
>
> Abstract:
> This document specifies a new Network Address Translator (NAT)
> traversal mode for the Host Identity Protocol (HIP). The new mode is
> based on the Interactive Connectivity Establishment (ICE) methodology
> and UDP encapsulation of data and signaling traffic. The main
> difference from the previously specified modes is the use of HIP
> messages for all NAT traversal procedures.
>
>
>
>
> The IETF Secretariat.
> _______________________________________________
> Hipsec mailing list
> Hipsec@ietf.org
> https://www.ietf.org/mailman/listinfo/hipsec


From ari.keranen@nomadiclab.com  Thu Mar  4 09:11:51 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 4BD513A8D81 for <hipsec@core3.amsl.com>; Thu,  4 Mar 2010 09:11:51 -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=[AWL=0.000,  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 yCOanAKT-kuU for <hipsec@core3.amsl.com>; Thu,  4 Mar 2010 09:11:47 -0800 (PST)
Received: from gw.nomadiclab.com (unknown [IPv6:2001:14b8:400:101::2]) by core3.amsl.com (Postfix) with ESMTP id 0F55F3A8DA4 for <hipsec@ietf.org>; Thu,  4 Mar 2010 09:11:45 -0800 (PST)
Received: from localhost (localhost [127.0.0.1]) by gw.nomadiclab.com (Postfix) with ESMTP id 125EF4E6DF; Thu,  4 Mar 2010 19:11:44 +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 v2ni1qRWsIwc; Thu,  4 Mar 2010 19:11:43 +0200 (EET)
Received: from [IPv6:2001:14b8:400:101:21c:23ff:fe45:a6c1] (unknown [IPv6:2001:14b8:400:101:21c:23ff:fe45:a6c1]) by gw.nomadiclab.com (Postfix) with ESMTP id 2F7B54E6DD; Thu,  4 Mar 2010 19:11:43 +0200 (EET)
Message-ID: <4B8FE9CE.3020600@nomadiclab.com>
Date: Thu, 04 Mar 2010 19:11:42 +0200
From: Ari Keranen <ari.keranen@nomadiclab.com>
User-Agent: Thunderbird 2.0.0.23 (X11/20090817)
MIME-Version: 1.0
To: "Henderson, Thomas R" <thomas.r.henderson@boeing.com>
References: <4B5F07F6.7080800@ericsson.com> <7CC566635CFE364D87DC5803D4712A6C4C1F48A7C1@XCH-NW-10V.nw.nos.boeing.com>
In-Reply-To: <7CC566635CFE364D87DC5803D4712A6C4C1F48A7C1@XCH-NW-10V.nw.nos.boeing.com>
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
Cc: HIP <hipsec@ietf.org>
Subject: Re: [Hipsec] WGLC: draft-ietf-hip-bone-04
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 Mar 2010 17:11:51 -0000

Hi Tom,

Thanks for the comments! Responses inline.

Henderson, Thomas R wrote:
> comments on draft-ietf-hip-bone-04:
> 
> (please see my other post suggesting that this draft include the via
> and hiccups drafts and that it add a better protocol overview
> section).

OK, we'll add some overview text to the next version.

>> 2. Terminology
>> 
>> 
>> The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
>>  "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in
>> this document are to be interpreted as described in RFC 2119
>> [RFC2119].
> 
> This section is empty; I think that since this is intended as a
> framework document, a good terminology section is needed.

OK. I added the following:

    Overlay network:  A network built on top of another network.  In case
       of HIP BONEs, the underlaying network is an IP network and the
       overlay can be, e.g., a peer-to-peer (P2P) network.

    Peer protocol:  A protocol used by nodes in an overlay network for
       performing, e.g., data storage and retrieval or overlay
       maintenance.  HIP is used for conveying the peer protocol messages
       between the nodes in the overlay network.

    Node ID:  A value that uniquely identifies a node in an overlay
       network.  The value is not usually human-friendly, but for example
       a hash of a public key.

    Valid locator:  A Locator (as defined in [RFC5206]; usually an IP
       address or an address and a port number) that a host is known to
       be reachable at, for example, because there is an active HIP
       association with the host.

Did you have something else specific in mind that should be added here?

>> 3. Background on HIP
>> 
> 
> I previously commented (earlier version of this draft) that it might
> be easier to refer readers to the HIP arch or base RFCs, but if you
> want to keep it here, suggest to move it to an appendix since it is
> not normative material.

I think it's good to have this early in the document since it provides 
the needed background for P2P (and other non-HIP) people about HIP. If 
it were in the appendix, or just references, likely it would be never 
actually read and there would be plenty of misconceptions about the rest 
of the document.

>> 4. The HIP BONE Framework
>> 
>> 
>> An overlay typically requires three types of operations:
>> 
>> o  overlay maintenance. o  data storage and retrieval. o
>> connection management.
> 
> Not all overlays (e.g. pure routing overlays) require data storage
> and retrieval.  Suggest to say that "Many overlays typically
> require..."

Makes sense; fixed this.

>> 4.1. Peer ID Assignment and Bootstrap
>> 
>> Nodes in an overlay are primarily identified by their Peer IDs.
> 
> This terminology "Peer ID" seems very RELOAD-centric.  How about the
> more general "Node ID", or talk about the distinction between peers
> and clients, such as in RELOAD?

Good point. Changed all the occurrences of Peer ID into Node ID.

>> If the overlay network or peer protocol has more specific 
>> requirements for the Peer ID value that prevent using HITs derived 
>> from public keys, each host will need a certificate (e.g., in their
>>  HIP base exchanges) provided by the enrollment server to prove
>> that they are authorized to use a particular identifier in the
>> overlay.
> 
> Note:  this is what I thought was missing in the instance
> specification.

This will be clarified in the RELOAD instance spec.

>> Bootstrap issues such as how to locate an enrollment or a bootstrap
>>  server belong to the peer protocol.
> 
> This seems to be a placeholder sentence for future text.  At the very
> least, this framework draft should deal with the bootstrap issue of
> how to forward I1s along the HIP BONE when a node first joins the
> overlay.

I think this is really an instance specific issue and there's not much 
one can say in the architecture document.

>> Note that the border between HIP BONE instance specification and a 
>> peer protocol specifications is blurry.
> 
> I agree with this observation; the current drafts are basically
> written from the standpoint of RELOAD and details about e.g.
> interaction between HIP and topology plugin are fuzzy.  However, it
> seems to me that to be useful as a general purpose framework for
> arbitrary peer protocols, crisper APIs would need to be specified.

I think that how, e.g., the topology plugin and HIP daemon actually 
interact are implementation details, and as discussed in the instance 
spec thread, I think these documents are not the right place for 
defining APIs or implementation details.

>> 5. Advantages of Using HIP BONE
>> 
>> Using HIP BONE, as opposed to a peer protocol, to perform
>> connection management in an overlay has a set of advantages.  HIP
>> BONE can be used by any peer protocol.  This keeps each peer
>> protocol from defining primitives needed for connection management
>> (e.g., primitives to establish connections and to tunnel messages
>> through the overlay) and NAT traversal.  Having this functionality
>> at a lower layer allows multiple upper-layer protocols to take
>> advantage of it.
> 
> This section probably could be moved to an introduction, explaining
> why we are going through all of the trouble to support these
> overlays.

Makes sense. I moved this to be part of the intro section.

>> 7.  Architectural Considerations
> 
> Note, Section 7 is probably more important as a first section, not
> the last in the draft.

I'll see what we can do with this.

>> Architecturally, routing tables are located between the peer
>> protocol and HIP, as shown in Figure 7.
> 
> This is important architectural discussion.  I had a few questions
> here:
> 
> 1) can a HIP packet from one overlay consult the routing table built
> in another overlay?

I'd say that, by default, no. HIP BONE packets are overlay network 
specific (identified with the OVERLAY_ID), so they should not cross 
overlay borders. However, I think we shouldn't forbid that either if 
someone want to specify something for this.

> 2) if HIP receives a locally originated packet with no OVERLAY_ID,
> and it has one or more peer protocols running, how does it decide
> where to route the packet?  I assume that all locally originated
> packets will somehow have their overlay identifier specified, but it
> would be helpful to state this somewhere.  For example, if it were
> RELOAD, RELOAD may have special APIs allowing it to identify the
> overlay ID that all locally originated packets from the RELOAD
> instance should use.  In addition, if HIP on that node was providing
> traditional HIP services to legacy applications, such (legacy
> applications) outbound packets would use rendezvous/relay servers as
> usual.

This is mostly an API issue, but one could configure his HIP 
implementation so that if there is no locator for a HIT, it is 
automatically sent to a certain overlay. Actually, we could define a 
"rendezvous usage" using RELOAD for this in the RELOAD instance spec.


Cheers,
Ari

From root@core3.amsl.com  Fri Mar  5 09:15:01 2010
Return-Path: <root@core3.amsl.com>
X-Original-To: hipsec@ietf.org
Delivered-To: hipsec@core3.amsl.com
Received: by core3.amsl.com (Postfix, from userid 0) id 6447C28C2C1; Fri,  5 Mar 2010 09:15:01 -0800 (PST)
From: Internet-Drafts@ietf.org
To: i-d-announce@ietf.org
Content-Type: Multipart/Mixed; Boundary="NextPart"
Mime-Version: 1.0
Message-Id: <20100305171501.6447C28C2C1@core3.amsl.com>
Date: Fri,  5 Mar 2010 09:15:01 -0800 (PST)
Cc: hipsec@ietf.org
Subject: [Hipsec] I-D Action:draft-ietf-hip-hiccups-02.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, 05 Mar 2010 17:15:01 -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           : HIP (Host Identity Protocol) Immediate Carriage and Conveyance of Upper- layer Protocol Signaling (HICCUPS)
	Author(s)       : G. Camarillo, J. Melen
	Filename        : draft-ietf-hip-hiccups-02.txt
	Pages           : 15
	Date            : 2010-03-05

This document defines a new HIP (Host Identity Protocol) packet type
called DATA.  HIP DATA packets are used to securely and reliably
convey arbitrary protocol messages over the Internet and various
overlay networks.

A URL for this Internet-Draft is:
http://www.ietf.org/internet-drafts/draft-ietf-hip-hiccups-02.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-hiccups-02.txt";
	site="ftp.ietf.org";
	access-type="anon-ftp";
	directory="internet-drafts"

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


--NextPart--

From mkomu@cs.hut.fi  Mon Mar  8 03:36:31 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 A435C3A6959 for <hipsec@core3.amsl.com>; Mon,  8 Mar 2010 03:36:31 -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 opXITOW+HZsx for <hipsec@core3.amsl.com>; Mon,  8 Mar 2010 03:36:30 -0800 (PST)
Received: from hutcs.cs.hut.fi (hutcs.cs.hut.fi [130.233.192.7]) by core3.amsl.com (Postfix) with ESMTP id B59D43A68A7 for <hipsec@ietf.org>; Mon,  8 Mar 2010 03:36:30 -0800 (PST)
Received: from hutcs.cs.hut.fi ([130.233.192.7] helo=[127.0.0.1]) by hutcs.cs.hut.fi with esmtpsa (TLSv1:AES256-SHA:256) (Exim 4.54) id 1NobGC-0006uI-Fj; Mon, 08 Mar 2010 13:36:32 +0200
Message-ID: <4B94E140.2020301@cs.hut.fi>
Date: Mon, 08 Mar 2010 13:36:32 +0200
From: Miika Komu <mkomu@cs.hut.fi>
User-Agent: Mozilla/5.0 (X11; U; Linux x86_64; en-US; rv:1.9.1.9pre) Gecko/20100304 Shredder/3.0.4pre
MIME-Version: 1.0
To: hip WG <hipsec@ietf.org>
Content-Type: text/plain; charset=iso-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Cc: Dmitrij Lagutin <Dmitrij.Lagutin@hiit.fi>
Subject: [Hipsec] About the HICCUPS draft
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 Mar 2010 11:36:31 -0000

----- Forwarded message from Dmitrij Lagutin <Dmitrij.Lagutin@hiit.fi> -----
     Date: Thu, 04 Mar 2010 14:29:31 +0200
     From: Dmitrij Lagutin <Dmitrij.Lagutin@hiit.fi>
Reply-To: Dmitrij Lagutin <Dmitrij.Lagutin@hiit.fi>
  Subject: About the HICCUPS draft
       To: hipsec@ietf.org

Dear all,


I have been working at Helsinki Institute for Information Technology (HIIT)
with the technology called Packet Level Authentication (PLA). PLA aims to
provide availability and hop-by-hop authentication on the network layer 
through
cryptographic signatures. The main idea is to give intermediate nodes 
means to
detect modified, duplicated and delayed packets, these packets can be then
dropped immediately before they even reach the destination.

Miika Komu and others suggested me combining principles of PLA with HIP 
since
they mostly complement each other. The HICCUPS draft seems to be a good 
place
for that. Some of my ideas are listed below.

- Could the possibility of more extensive hop-by-hop verification be 
included in
the security considerations chapter (7.) of the draft?

- A timestamp added to HICCUPS parameters would allow detection of 
significantly
delayed packets. A global time synchronization mechanism would not be 
absolutely
necessary.

- A separate sequence number added to every HICCUPS packet would allow 
detection
of duplicated packets (which can be used in replay attacks). In contrast to
SEQ_DATA packet, this sequence number would not be ACKed.


Best regards,
Dmitrij Lagutin
Researcher, Helsinki Institute for Information Technology

----- End forwarded message -----





From root@core3.amsl.com  Mon Mar  8 08:45:03 2010
Return-Path: <root@core3.amsl.com>
X-Original-To: hipsec@ietf.org
Delivered-To: hipsec@core3.amsl.com
Received: by core3.amsl.com (Postfix, from userid 0) id 95E063A6A65; Mon,  8 Mar 2010 08:45:02 -0800 (PST)
From: Internet-Drafts@ietf.org
To: i-d-announce@ietf.org
Content-Type: Multipart/Mixed; Boundary="NextPart"
Mime-Version: 1.0
Message-Id: <20100308164502.95E063A6A65@core3.amsl.com>
Date: Mon,  8 Mar 2010 08:45:02 -0800 (PST)
Cc: hipsec@ietf.org
Subject: [Hipsec] I-D Action:draft-ietf-hip-via-01.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 Mar 2010 16:45:04 -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 (HIP) Multi-hop Routing Extension
	Author(s)       : G. Camarillo, A. Keranen
	Filename        : draft-ietf-hip-via-01.txt
	Pages           : 9
	Date            : 2010-03-08

This document specifies two extensions to HIP to implement multi-hop
routing.  The first extension allows implementing source routing in
HIP.  That is, a host sending a HIP packet can define a set of hosts
that the HIP packet should traverse.  The second extension allows a
HIP packet to carry and record the list of hosts that forwarded it.

A URL for this Internet-Draft is:
http://www.ietf.org/internet-drafts/draft-ietf-hip-via-01.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-via-01.txt";
	site="ftp.ietf.org";
	access-type="anon-ftp";
	directory="internet-drafts"

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


--NextPart--

From root@core3.amsl.com  Mon Mar  8 10:15:02 2010
Return-Path: <root@core3.amsl.com>
X-Original-To: hipsec@ietf.org
Delivered-To: hipsec@core3.amsl.com
Received: by core3.amsl.com (Postfix, from userid 0) id A1DBF3A6AE3; Mon,  8 Mar 2010 10:15:02 -0800 (PST)
From: Internet-Drafts@ietf.org
To: i-d-announce@ietf.org
Content-Type: Multipart/Mixed; Boundary="NextPart"
Mime-Version: 1.0
Message-Id: <20100308181502.A1DBF3A6AE3@core3.amsl.com>
Date: Mon,  8 Mar 2010 10:15:02 -0800 (PST)
Cc: hipsec@ietf.org
Subject: [Hipsec] I-D Action:draft-ietf-hip-bone-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 Mar 2010 18:15:02 -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           : HIP BONE: Host Identity Protocol (HIP) Based Overlay Networking Environment
	Author(s)       : G. Camarillo, et al.
	Filename        : draft-ietf-hip-bone-05.txt
	Pages           : 21
	Date            : 2010-03-08

This document specifies a framework to build HIP (Host Identity
Protocol)-based overlay networks.  This framework uses HIP to perform
connection management.  Other functions, such as data storage and
retrieval or overlay maintenance, are implemented using protocols
other than HIP.  These protocols are loosely referred to as peer
protocols.

A URL for this Internet-Draft is:
http://www.ietf.org/internet-drafts/draft-ietf-hip-bone-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-bone-05.txt";
	site="ftp.ietf.org";
	access-type="anon-ftp";
	directory="internet-drafts"

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


--NextPart--

From root@core3.amsl.com  Mon Mar  8 10:15:02 2010
Return-Path: <root@core3.amsl.com>
X-Original-To: hipsec@ietf.org
Delivered-To: hipsec@core3.amsl.com
Received: by core3.amsl.com (Postfix, from userid 0) id 9B9923A6A72; Mon,  8 Mar 2010 10:15:02 -0800 (PST)
From: Internet-Drafts@ietf.org
To: i-d-announce@ietf.org
Content-Type: Multipart/Mixed; Boundary="NextPart"
Mime-Version: 1.0
Message-Id: <20100308181502.9B9923A6A72@core3.amsl.com>
Date: Mon,  8 Mar 2010 10:15:02 -0800 (PST)
Cc: hipsec@ietf.org
Subject: [Hipsec] I-D Action:draft-ietf-hip-reload-instance-01.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 Mar 2010 18:15:02 -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-Based Overlay Networking Environment (HIP BONE) Instance Specification for REsource LOcation And Discovery (RELOAD)
	Author(s)       : A. Keranen, et al.
	Filename        : draft-ietf-hip-reload-instance-01.txt
	Pages           : 10
	Date            : 2010-03-08

This document is the Host Identity Protocol-Based Overlay Networking
Environment (HIP BONE) instance specification for the REsource
LOcation And Discovery (RELOAD) protocol.  The document provides the
details needed to build a RELOAD-based overlay that uses HIP.

A URL for this Internet-Draft is:
http://www.ietf.org/internet-drafts/draft-ietf-hip-reload-instance-01.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-reload-instance-01.txt";
	site="ftp.ietf.org";
	access-type="anon-ftp";
	directory="internet-drafts"

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


--NextPart--

From Dmitrij.Lagutin@hiit.fi  Thu Mar  4 04:29:31 2010
Return-Path: <Dmitrij.Lagutin@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 B93283A89EC for <hipsec@core3.amsl.com>; Thu,  4 Mar 2010 04:29:31 -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 QwJdJbRJ1DH3 for <hipsec@core3.amsl.com>; Thu,  4 Mar 2010 04:29:30 -0800 (PST)
Received: from argo.otaverkko.fi (argo.otaverkko.fi [212.68.0.2]) by core3.amsl.com (Postfix) with ESMTP id 87B0E3A89E0 for <hipsec@ietf.org>; Thu,  4 Mar 2010 04:29:30 -0800 (PST)
Received: from localhost (hydra.otaverkko.fi [212.68.0.4]) by argo.otaverkko.fi (Postfix) with ESMTP id 07C1625ED20 for <hipsec@ietf.org>; Thu,  4 Mar 2010 14:29:31 +0200 (EET)
Received: from victory.hiit.fi (victory.hiit.fi [128.214.113.205])  by webmail.hiit.fi (IMP) with HTTP  for <dlagutin.hiit@nestor.otaverkko.fi>; Thu, 04 Mar 2010 14:29:31 +0200
Message-ID: <1267705771.4b8fa7ab0486b@webmail.hiit.fi>
Date: Thu, 04 Mar 2010 14:29:31 +0200
From: Dmitrij Lagutin <Dmitrij.Lagutin@hiit.fi>
To: hipsec@ietf.org
MIME-Version: 1.0
Content-Type: text/plain; charset=iso-8859-1
Content-Transfer-Encoding: 8bit
User-Agent: Internet Messaging Program (IMP) 3.2.6
X-Originating-IP: 128.214.113.205
X-Mailman-Approved-At: Mon, 08 Mar 2010 23:38:29 -0800
Subject: [Hipsec] About the HICCUPS draft
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 Mar 2010 12:30:34 -0000

Dear all,


I have been working at Helsinki Institute for Information Technology (HIIT)
with the technology called Packet Level Authentication (PLA). PLA aims to
provide availability and hop-by-hop authentication on the network layer through
cryptographic signatures. The main idea is to give intermediate nodes means to
detect modified, duplicated and delayed packets, these packets can be then
dropped immediately before they even reach the destination.

Miika Komu and others suggested me combining principles of PLA with HIP since
they mostly complement each other. The HICCUPS draft seems to be a good place
for that. Some of my ideas are listed below.

- Could the possibility of more extensive hop-by-hop verification be included in
the security considerations chapter (7.) of the draft?

- A timestamp added to HICCUPS parameters would allow detection of significantly
delayed packets. A global time synchronization mechanism would not be absolutely
necessary.

- A separate sequence number added to every HICCUPS packet would allow detection
of duplicated packets (which can be used in replay attacks). In contrast to
SEQ_DATA packet, this sequence number would not be ACKed.


Best regards,
Dmitrij Lagutin
Researcher, Helsinki Institute for Information Technology


From ari.keranen@nomadiclab.com  Tue Mar  9 04:53:39 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 9137E3A67F8 for <hipsec@core3.amsl.com>; Tue,  9 Mar 2010 04:53:39 -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 x8vTTY4ih1Ga for <hipsec@core3.amsl.com>; Tue,  9 Mar 2010 04:53:38 -0800 (PST)
Received: from gw.nomadiclab.com (unknown [IPv6:2001:14b8:400:101::2]) by core3.amsl.com (Postfix) with ESMTP id B142F3A67FA for <hipsec@ietf.org>; Tue,  9 Mar 2010 04:53:38 -0800 (PST)
Received: from localhost (localhost [127.0.0.1]) by gw.nomadiclab.com (Postfix) with ESMTP id 3BED44F9F1 for <hipsec@ietf.org>; Tue,  9 Mar 2010 14:53:39 +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 WVcRQ-GfH45X for <hipsec@ietf.org>; Tue,  9 Mar 2010 14:53:38 +0200 (EET)
Received: from [IPv6:2001:14b8:400:101:21c:23ff:fe45:a6c1] (unknown [IPv6:2001:14b8:400:101:21c:23ff:fe45:a6c1]) by gw.nomadiclab.com (Postfix) with ESMTP id 5CB5B4F9EF for <hipsec@ietf.org>; Tue,  9 Mar 2010 14:53:38 +0200 (EET)
Message-ID: <4B9644D2.9080008@nomadiclab.com>
Date: Tue, 09 Mar 2010 14:53:38 +0200
From: Ari Keranen <ari.keranen@nomadiclab.com>
User-Agent: Thunderbird 2.0.0.23 (X11/20090817)
MIME-Version: 1.0
To: HIP <hipsec@ietf.org>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Subject: [Hipsec] Updated HIP overlay drafts
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 Mar 2010 12:53:39 -0000

Hi all,

We submitted updated versions of the HIP BONE and VIA drafts:
http://www.ietf.org/internet-drafts/draft-ietf-hip-bone-05.txt
http://www.ietf.org/internet-drafts/draft-ietf-hip-via-01.txt

They address the comments that were given during the WGLC:
- HIP BONE was restructured and a framework overview section was added
- HIP BONE now includes terminology part with the common terms used in 
that context
- OVERLAY_TTL parameter type was changed to critical so that it can be 
used as a generic forwarding loop breaker
- Instead of "Peer ID", HIP BONE uses the more generic term "Node ID"
- HIP VIA supports now loose source routing mode where a hop in the 
destination list may be skipped
- Some clarifications were added to HIP VIA regarding the definitions 
and use of the parameters

Also the RELOAD instance spec was updated:
http://www.ietf.org/internet-drafts/draft-ietf-hip-reload-instance-01.txt

That version contains fixes for the comments, other clarifications, and 
also changes due to new version of the RELOAD draft (AttachLite was 
removed).


Cheers,
Ari

From ari.keranen@nomadiclab.com  Tue Mar  9 05:09:26 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 A780F3A6806 for <hipsec@core3.amsl.com>; Tue,  9 Mar 2010 05:09:26 -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=[AWL=0.000,  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 3Ef+VdkHJqws for <hipsec@core3.amsl.com>; Tue,  9 Mar 2010 05:09:25 -0800 (PST)
Received: from gw.nomadiclab.com (unknown [IPv6:2001:14b8:400:101::2]) by core3.amsl.com (Postfix) with ESMTP id 7915B3A6805 for <hipsec@ietf.org>; Tue,  9 Mar 2010 05:09:25 -0800 (PST)
Received: from localhost (localhost [127.0.0.1]) by gw.nomadiclab.com (Postfix) with ESMTP id 8AA9F4F9F5 for <hipsec@ietf.org>; Tue,  9 Mar 2010 15:09:29 +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 ZBDOzsIyaVsb for <hipsec@ietf.org>; Tue,  9 Mar 2010 15:09:29 +0200 (EET)
Received: from [IPv6:2001:14b8:400:101:21c:23ff:fe45:a6c1] (unknown [IPv6:2001:14b8:400:101:21c:23ff:fe45:a6c1]) by gw.nomadiclab.com (Postfix) with ESMTP id EFA394F9F4 for <hipsec@ietf.org>; Tue,  9 Mar 2010 15:09:28 +0200 (EET)
Message-ID: <4B964888.2050500@nomadiclab.com>
Date: Tue, 09 Mar 2010 15:09:28 +0200
From: Ari Keranen <ari.keranen@nomadiclab.com>
User-Agent: Thunderbird 2.0.0.23 (X11/20090817)
MIME-Version: 1.0
To: HIP <hipsec@ietf.org>
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Transfer-Encoding: 7bit
Subject: [Hipsec] [Fwd: New Version Notification for draft-keranen-hip-over-hip-01]
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 Mar 2010 13:09:26 -0000

Hi all,

The HIP-over-HIP draft was also updated:
http://tools.ietf.org/html/draft-keranen-hip-over-hip-01

The new version contains small fixes and the following changes regarding 
the comments given on the previous version:
- One can now revert back to the original mode used in the base exchange 
("DEFAULT" mode)
- Mode negotiation after BeX using UPDATEs was added
- Added a MUST for using ESP transport format if ESP modes are used
- The host with the lower HIT initiates the TCP connection in the 
ESP-TCP mode
- Added text on when to use different modes
- Added text about error and mobility cases and a new error Notify type
- Added IANA registry for the transport modes


Cheers,
Ari

-------- Original Message --------
Subject: New Version Notification for draft-keranen-hip-over-hip-01
Date: Mon, 8 Mar 2010 17:31:36 +0100
From: IETF I-D Submission Tool <idsubmission@ietf.org>


A new version of I-D, draft-keranen-hip-over-hip-01.txt has been 
successfuly submitted by Ari Keranen and posted to the IETF repository.

Filename:	 draft-keranen-hip-over-hip
Revision:	 01
Title:		 Host Identity Protocol Signaling Message Transport Modes
Creation_date:	 2010-03-08
WG ID:		 Independent Submission
Number_of_pages: 8

Abstract:
This document specifies two transport modes for Host Identity
Protocol signaling messages that allow conveying them over encrypted
connections initiated with the Host Identity Protocol.
 



The IETF Secretariat.



From ari.keranen@nomadiclab.com  Tue Mar  9 07:14:34 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 BB7273A6831 for <hipsec@core3.amsl.com>; Tue,  9 Mar 2010 07:14:34 -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 nzrrz18d-7Ip for <hipsec@core3.amsl.com>; Tue,  9 Mar 2010 07:14:33 -0800 (PST)
Received: from gw.nomadiclab.com (unknown [IPv6:2001:14b8:400:101::2]) by core3.amsl.com (Postfix) with ESMTP id A40B93A6920 for <hipsec@ietf.org>; Tue,  9 Mar 2010 07:14:33 -0800 (PST)
Received: from localhost (localhost [127.0.0.1]) by gw.nomadiclab.com (Postfix) with ESMTP id 5C64E4FA07; Tue,  9 Mar 2010 17:14:37 +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 aX5EIhvEKhoX; Tue,  9 Mar 2010 17:14:35 +0200 (EET)
Received: from [IPv6:2001:14b8:400:101:21c:23ff:fe45:a6c1] (unknown [IPv6:2001:14b8:400:101:21c:23ff:fe45:a6c1]) by gw.nomadiclab.com (Postfix) with ESMTP id 92F1B4FA05; Tue,  9 Mar 2010 17:14:35 +0200 (EET)
Message-ID: <4B9665DB.9090208@nomadiclab.com>
Date: Tue, 09 Mar 2010 17:14:35 +0200
From: Ari Keranen <ari.keranen@nomadiclab.com>
User-Agent: Thunderbird 2.0.0.23 (X11/20090817)
MIME-Version: 1.0
To: Miika Komu <mkomu@cs.hut.fi>
References: <4B8F8B26.4050300@nomadiclab.com> <4B8F8CE3.6060203@cs.hut.fi>
In-Reply-To: <4B8F8CE3.6060203@cs.hut.fi>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Cc: hipsec@ietf.org
Subject: Re: [Hipsec] draft-keranen-hip-native-nat-traversal-00
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 Mar 2010 15:14:34 -0000

Hi Miika,

Yes, this mode has its benefits over the STUN based methods and could be 
a good candidate for the standards track too.


Cheers,
Ari

Miika Komu wrote:
> On 03/04/2010 12:27 PM, Ari Keranen wrote:
> 
> Hi,
> 
> based on our implementation experimentation, I would say that this is a 
> better for the experimental NAT traversal work to proceed towards 
> standards track.
> 
>> Hi all,
>>
>> We wrote an extension to the HIP NAT traversal draft that uses the ICE
>> methodology with HIP messages and an ESP relay for the NAT traversal
>> procedures:
>>
>> http://www.ietf.org/id/draft-keranen-hip-native-nat-traversal-00.txt
>>
>> This draft addresses the issue that one may not be willing to integrate
>> a full ICE implementation with HIP but rather re-use the HIP messages
>> and state machines for the same purpose.
>>
>> Comments are welcome!
>>
>>
>> Cheers,
>> Ari
>>
>>
>> -------- Original Message --------
>> Subject: New Version Notification for
>> draft-keranen-hip-native-nat-traversal-00
>>
>>
>> A new version of I-D, draft-keranen-hip-native-nat-traversal-00.txt has
>> been successfuly submitted by Ari Keranen and posted to the IETF
>> repository.
>>
>> Filename: draft-keranen-hip-native-nat-traversal
>> Revision: 00
>> Title: Native NAT Traversal Mode for the Host Identity Protocol
>> Creation_date: 2010-03-01
>> WG ID: Independent Submission
>> Number_of_pages: 15
>>
>> Abstract:
>> This document specifies a new Network Address Translator (NAT)
>> traversal mode for the Host Identity Protocol (HIP). The new mode is
>> based on the Interactive Connectivity Establishment (ICE) methodology
>> and UDP encapsulation of data and signaling traffic. The main
>> difference from the previously specified modes is the use of HIP
>> messages for all NAT traversal procedures.
>>

From rgm@htt-consult.com  Tue Mar  9 08:34:52 2010
Return-Path: <rgm@htt-consult.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 A7C763A6831 for <hipsec@core3.amsl.com>; Tue,  9 Mar 2010 08:34:52 -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 JL5-CCCY8rmF for <hipsec@core3.amsl.com>; Tue,  9 Mar 2010 08:34:51 -0800 (PST)
Received: from klovia.htt-consult.com (klovia.htt-consult.com [208.83.67.149]) by core3.amsl.com (Postfix) with ESMTP id CC40E3A6830 for <hipsec@ietf.org>; Tue,  9 Mar 2010 08:34:51 -0800 (PST)
Received: from localhost (unknown [127.0.0.1]) by klovia.htt-consult.com (Postfix) with ESMTP id 7259868B28 for <hipsec@ietf.org>; Tue,  9 Mar 2010 17:30:46 +0000 (UTC)
X-Virus-Scanned: amavisd-new at localhost
Received: from klovia.htt-consult.com ([127.0.0.1]) by localhost (klovia.htt-consult.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id foy8TBS6D3CE for <hipsec@ietf.org>; Tue,  9 Mar 2010 12:30:37 -0500 (EST)
Received: from nc2400.htt-consult.com (h155.home.htt [208.83.67.155]) (Authenticated sender: rgm@htt-consult.com) by klovia.htt-consult.com (Postfix) with ESMTPSA id 1973268B27 for <hipsec@ietf.org>; Tue,  9 Mar 2010 12:30:37 -0500 (EST)
Message-ID: <4B9678A3.1000406@htt-consult.com>
Date: Tue, 09 Mar 2010 11:34:43 -0500
From: Robert Moskowitz <rgm@htt-consult.com>
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.9.1.8) Gecko/20100301 Fedora/3.0.3-1.fc12 Thunderbird/3.0.3
MIME-Version: 1.0
To: hipsec@ietf.org
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Subject: [Hipsec] Fwd: I-D Action: draft-moskowitz-hip-rfc5201-bis-01
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 Mar 2010 16:34:52 -0000

I don't know why this has not appeared here, but thanks Tobias for what 
you have done the past few weeks.

-----Original Message-----
From: IETF I-D Submission Tool [mailto:idsubmission@ietf.org]
Sent: Monday, March 08, 2010 7:47 PM
To: heer@cs.rwth-aachen.de
Cc: robert.moskowitz@icsalabs.com; pekka.nikander@nomadiclab.com;
petri.jokela@nomadiclab.com; thomas.r.henderson@boeing.com
Subject: New Version Notification for draft-moskowitz-hip-rfc5201-bis-01


A new version of I-D, draft-moskowitz-hip-rfc5201-bis-01.txt has been
successfuly submitted by Tobias Heer and posted to the IETF repository.

Filename:	 draft-moskowitz-hip-rfc5201-bis
Revision:	 01
Title:		 Host Identity Protocol
Creation_date:	 2010-03-09
WG ID:		 Independent Submission
Number_of_pages: 105

Abstract:
This document specifies the details of the Host Identity Protocol
(HIP).  HIP allows consenting hosts to securely establish and
maintain shared IP-layer state, allowing separation of the identifier
and locator roles of IP addresses, thereby enabling continuity of
communications across IP address changes.  HIP is based on a Sigma-
compliant Diffie-Hellman key exchange, using public key identifiers
from a new Host Identity namespace for mutual peer authentication.
The protocol is designed to be resistant to denial-of-service (DoS)
and man-in-the-middle (MitM) attacks.  When used together with
another suitable security protocol, such as the Encapsulated Security
Payload (ESP), it provides integrity protection and optional
encryption for upper-layer protocols, such as TCP and UDP.

This document obsoletes RFC 5201 and addresses the concerns raised by
the IESG, particularly that of crypto agility.  It also incorporates
lessons learned from the implementations of RFC 5201.




The IETF Secretariat.





From heer@informatik.rwth-aachen.de  Tue Mar  9 08:48:30 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 44FA43A6950 for <hipsec@core3.amsl.com>; Tue,  9 Mar 2010 08:48:30 -0800 (PST)
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 MLBDnMwAp6Sr for <hipsec@core3.amsl.com>; Tue,  9 Mar 2010 08:48:19 -0800 (PST)
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 528B53A68E9 for <hipsec@ietf.org>; Tue,  9 Mar 2010 08:48:18 -0800 (PST)
MIME-version: 1.0
Content-transfer-encoding: 7BIT
Content-type: text/plain; charset=us-ascii
Received: from ironport-out-2.rz.rwth-aachen.de ([134.130.5.41]) 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 <0KZ000DROXCLB410@mta-2.ms.rz.RWTH-Aachen.de> for hipsec@ietf.org; Tue, 09 Mar 2010 17:48:21 +0100 (CET)
X-IronPort-AV: E=Sophos;i="4.49,608,1262559600";   d="scan'208";a="25864402"
Received: from relay-auth-1.ms.rz.rwth-aachen.de (HELO relay-auth-1) ([134.130.7.78]) by ironport-in-2.rz.rwth-aachen.de with ESMTP; Tue, 09 Mar 2010 17:48:21 +0100
Received: from umic-137-226-154-185.nn.rwth-aachen.de ([unknown] [137.226.154.185]) by relay-auth-1.ms.rz.rwth-aachen.de (Sun Java(tm) System Messaging Server 7.0-3.01 64bit (built Dec 9 2008)) with ESMTPA id <0KZ000BZIXCLED20@relay-auth-1.ms.rz.rwth-aachen.de> for hipsec@ietf.org; Tue, 09 Mar 2010 17:48:21 +0100 (CET)
From: Tobias Heer <heer@cs.rwth-aachen.de>
In-reply-to: <4B9678A3.1000406@htt-consult.com>
Date: Tue, 09 Mar 2010 17:48:27 +0100
Message-id: <41E071E3-C310-4910-96C4-B03C8CC9415D@cs.rwth-aachen.de>
References: <4B9678A3.1000406@htt-consult.com>
To: "hipsec@ietf.org WG" <hipsec@ietf.org>
X-Mailer: Apple Mail (2.1077)
Subject: Re: [Hipsec] Fwd: I-D Action: draft-moskowitz-hip-rfc5201-bis-01
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 Mar 2010 16:48:30 -0000

Hi, 

I would like to add the change-log for the draft:

Change-log draft-moskowitz-RFC5201-bis-01
----------------------------------------
* Extended protocol overview to include restart option
* Extended state machine to include restart option because of
  unsupported Algorithms
* Replaced SHA-1 with SHA-256 for required implementation
* Added OGA list parameter (715) for detecting the Responder's set of OGAs
* Added Appendix on ORCHID use in HITs
* Added truncated SHA-256 option for HITs
* Added truncated SHA-1 option for HITs
* Added text about new ORCHID structure to HIT overview
* Moved Editor role to Robert Moskowitz
* Added SHA-256 to puzzle parameter
* Generalized LTRUNC to be hash-function agnostic
* Added text about RHASH depending on OGA

With these changes we are currently at step 1 of the following crypto agility roadmap:
1) Crypto agility for the HIT
2) Improved crypto agility for the signature algorithm and the HI
3) Improved crypto agility for DH
4) Definition of new algorithms for use in 1, 2, and 3
 
Hence, the submitted draft (version 01) is far from complete and should be understood as an initial step towards crypto agility.


Am 09.03.2010 um 17:34 schrieb Robert Moskowitz:

> I don't know why this has not appeared here,

I think this is because it is an individual submission. These are not sent to the WG mailing lists automatically.

BR, 

Tobias


--  

Dipl.-Inform. Tobias Heer, Ph.D. Student
Distributed Systems Group 
RWTH Aachen University, Germany
tel: +49 241 80 207 76
web: http://ds.cs.rwth-aachen.de/members/heer








From Dmitriy.Kuptsov@hiit.fi  Thu Mar 11 11:02:21 2010
Return-Path: <Dmitriy.Kuptsov@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 ECE993A6CDD for <hipsec@core3.amsl.com>; Thu, 11 Mar 2010 11:02:21 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.001
X-Spam-Level: 
X-Spam-Status: No, score=0.001 tagged_above=-999 required=5 tests=[BAYES_50=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 uJGEg+x+IgDv for <hipsec@core3.amsl.com>; Thu, 11 Mar 2010 11:02:21 -0800 (PST)
Received: from argo.otaverkko.fi (argo.otaverkko.fi [212.68.0.2]) by core3.amsl.com (Postfix) with ESMTP id 223313A6E12 for <hipsec@ietf.org>; Thu, 11 Mar 2010 10:37:19 -0800 (PST)
Received: from localhost (hydra.otaverkko.fi [212.68.0.4]) by argo.otaverkko.fi (Postfix) with ESMTP id 2477725ED06 for <hipsec@ietf.org>; Thu, 11 Mar 2010 20:37:24 +0200 (EET)
Received: from hoasnet-ff00dd00-165.dhcp.inet.fi (hoasnet-ff00dd00-165.dhcp.inet.fi [80.221.0.165])  by webmail.otaverkko.fi (IMP) with HTTP  for <kuptsov.hiit@nestor.otaverkko.fi>; Thu, 11 Mar 2010 20:37:24 +0200
Message-ID: <1268332644.4b993864212f8@webmail.otaverkko.fi>
Date: Thu, 11 Mar 2010 20:37:24 +0200
From: Dmitriy Kuptsov <Dmitriy.Kuptsov@hiit.fi>
To: hipsec@ietf.org
MIME-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 8bit
User-Agent: Internet Messaging Program (IMP) 3.2.6
X-Originating-IP: 80.221.0.165
Subject: [Hipsec] replacing DH in HIP
X-BeenThere: hipsec@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: "This is the official IETF Mailing List for the HIP Working Group." <hipsec.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/hipsec>, <mailto:hipsec-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/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 Mar 2010 19:02:22 -0000

Hi all,

Recently, at Helsinki Institute for Information Technology, we were trying to
run HIP on sensor nodes, even though computing DH public values and secret is
not a problem in terms of time, such operation consumes a lot of energy. So I
was wondering if DH can be replace with something more lightweight, e.g,
bivariate polynomials. Consider a modified HIP base exchange:

I                                                            R
|                 HITi, HITr, HostIDi                        |
|----------------------------------------------------------->|
|   HITi, HITr, HostIDr, Puzzle, Enc_pubI(Poly_r), Sig       |
|<-----------------------------------------------------------|
|    HITi, HITr, Solution, Enc_pubR(Poly_i), Sig, HMAC       |
|----------------------------------------------------------->|
|                HITi, HITr, HMAC, Sig                       |
|<-----------------------------------------------------------|

Where the modifications are:
(i) I1 carries the host identity, aka public key, of the initiator as parameter
(ii) R1 carries additional encrypted using Initiators public key (found in I1)
parameter which contains a randomly generated (by responder) bivariate
polynomial of form for instance f(rand_r XOR HITr, y). Probably here it is
impossible to have pre-generate R1's.
(iii) I2 carries the encrypted using Responder's public key bivariate polynomial
of form for instance f(rand_r XOR HITr, rand_i XOR HIT i) such that R gets now
the secret key.
(iv) R2 remains the unmodified.

Here Enc function can be RSA or ECC using public key of receiver of a message
such that eavesdropper cannot obtain the polynomial send in R1 or I2 messages.

The bivariate polynomials f(x, y) = a0+a1xy+a2x^2y^2+...+anx^ny^n can be
implemented really efficiently in sensor nodes over field G(2^16) and later
using several such polynomials to construct a key of needed size. For instance,
to construct a shared key of 80 bits Responder randomly selects 5 bivariate
polynomials (all with different coefficients):
f_1(rand_r_1 XOR HITr, y)
f_2(rand_r_2 XOR HITr, y)
f_3(rand_r_3 XOR HITr, y)
f_4(rand_r_4 XOR HITr, y)
f_5(rand_r_5 XOR HITr, y)
Or may be even consecutive polynomials can be derived using some key derivation
function...

Then the initiator computes all 5 polynomials and gets the key as
Key = (f_1(rand_r_1 XOR HITr, rand_r_1 XOR HITi) || ... ||f_5(rand_r_5 XOR HITr,
rand_r_5 XOR HITi))

The same key is obtained by responder once it receives an I2 message.

Of course such approach does not comply with HIP specs in many ways. However, is
it feasible/secure to do something like this?

Kind regards,
Dmitriy Kuptsov



From gonzalo.camarillo@ericsson.com  Sat Mar 13 07:57:53 2010
Return-Path: <gonzalo.camarillo@ericsson.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 547723A6909 for <hipsec@core3.amsl.com>; Sat, 13 Mar 2010 07:57:53 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -103.199
X-Spam-Level: 
X-Spam-Status: No, score=-103.199 tagged_above=-999 required=5 tests=[AWL=0.400, BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1, 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 fPGpIWtXSe2n for <hipsec@core3.amsl.com>; Sat, 13 Mar 2010 07:57:52 -0800 (PST)
Received: from mailgw10.se.ericsson.net (mailgw10.se.ericsson.net [193.180.251.61]) by core3.amsl.com (Postfix) with ESMTP id 4FF9C3A68B8 for <hipsec@ietf.org>; Sat, 13 Mar 2010 07:57:51 -0800 (PST)
X-AuditID: c1b4fb3d-b7bf6ae000005bec-2e-4b9bb6038c0c
Received: from esealmw129.eemea.ericsson.se (Unknown_Domain [153.88.253.125]) by mailgw10.se.ericsson.net (Symantec Brightmail Gateway) with SMTP id 64.57.23532.406BB9B4; Sat, 13 Mar 2010 16:57:56 +0100 (CET)
Received: from esealmw127.eemea.ericsson.se ([153.88.254.171]) by esealmw129.eemea.ericsson.se with Microsoft SMTPSVC(6.0.3790.3959);  Sat, 13 Mar 2010 16:57:55 +0100
Received: from [131.160.126.224] ([131.160.126.224]) by esealmw127.eemea.ericsson.se with Microsoft SMTPSVC(6.0.3790.3959);  Sat, 13 Mar 2010 16:57:53 +0100
Message-ID: <4B9BB5FD.7010401@ericsson.com>
Date: Sat, 13 Mar 2010 17:57:49 +0200
From: Gonzalo Camarillo <Gonzalo.Camarillo@ericsson.com>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.0; en-US; rv:1.9.1.8) Gecko/20100227 Thunderbird/3.0.3
MIME-Version: 1.0
To: HIP <hipsec@ietf.org>
References: <4B9644D2.9080008@nomadiclab.com>
In-Reply-To: <4B9644D2.9080008@nomadiclab.com>
X-Enigmail-Version: 1.0.1
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
X-OriginalArrivalTime: 13 Mar 2010 15:57:55.0369 (UTC) FILETIME=[F1BF9190:01CAC2C5]
X-Brightmail-Tracker: AAAAAA==
Subject: Re: [Hipsec] Updated HIP overlay drafts
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: Sat, 13 Mar 2010 15:57:53 -0000

Folks,

the authors of the overlay drafts have revised them in order to address
the comments received during their WGLC. Please, have a look at the new
revisions so that we can request their publication. We will wait for
comments until the HIP WG meeting in Anaheim.

Cheers,

Gonzalo
HIP co-chair

On 09/03/2010 2:53 PM, Ari Keranen wrote:
> Hi all,
> 
> We submitted updated versions of the HIP BONE and VIA drafts:
> http://www.ietf.org/internet-drafts/draft-ietf-hip-bone-05.txt
> http://www.ietf.org/internet-drafts/draft-ietf-hip-via-01.txt
> 
> They address the comments that were given during the WGLC:
> - HIP BONE was restructured and a framework overview section was added
> - HIP BONE now includes terminology part with the common terms used in 
> that context
> - OVERLAY_TTL parameter type was changed to critical so that it can be 
> used as a generic forwarding loop breaker
> - Instead of "Peer ID", HIP BONE uses the more generic term "Node ID"
> - HIP VIA supports now loose source routing mode where a hop in the 
> destination list may be skipped
> - Some clarifications were added to HIP VIA regarding the definitions 
> and use of the parameters
> 
> Also the RELOAD instance spec was updated:
> http://www.ietf.org/internet-drafts/draft-ietf-hip-reload-instance-01.txt
> 
> That version contains fixes for the comments, other clarifications, and 
> also changes due to new version of the RELOAD draft (AttachLite was 
> removed).
> 
> 
> Cheers,
> Ari
> _______________________________________________
> Hipsec mailing list
> Hipsec@ietf.org
> https://www.ietf.org/mailman/listinfo/hipsec
> 


From rgm@htt-consult.com  Mon Mar 15 07:57:41 2010
Return-Path: <rgm@htt-consult.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 4DC253A6B64 for <hipsec@core3.amsl.com>; Mon, 15 Mar 2010 07:57:41 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.001
X-Spam-Level: 
X-Spam-Status: No, score=0.001 tagged_above=-999 required=5 tests=[BAYES_50=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 td87ShBEDfZV for <hipsec@core3.amsl.com>; Mon, 15 Mar 2010 07:57:40 -0700 (PDT)
Received: from klovia.htt-consult.com (klovia.htt-consult.com [208.83.67.149]) by core3.amsl.com (Postfix) with ESMTP id 7ADAD3A67B3 for <hipsec@ietf.org>; Mon, 15 Mar 2010 07:57:38 -0700 (PDT)
Received: from localhost (unknown [127.0.0.1]) by klovia.htt-consult.com (Postfix) with ESMTP id D566768B69; Mon, 15 Mar 2010 15:53:11 +0000 (UTC)
X-Virus-Scanned: amavisd-new at localhost
Received: from klovia.htt-consult.com ([127.0.0.1]) by localhost (klovia.htt-consult.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 5bleeAIhdDtj; Mon, 15 Mar 2010 11:53:02 -0400 (EDT)
Received: from nc2400.htt-consult.com (unknown [199.72.57.111]) (Authenticated sender: rgm@htt-consult.com) by klovia.htt-consult.com (Postfix) with ESMTPSA id E5F4768B4E; Mon, 15 Mar 2010 11:53:01 -0400 (EDT)
Message-ID: <4B9E4AD3.6020601@htt-consult.com>
Date: Mon, 15 Mar 2010 10:57:23 -0400
From: Robert Moskowitz <rgm@htt-consult.com>
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.9.1.8) Gecko/20100301 Fedora/3.0.3-1.fc12 Thunderbird/3.0.3
MIME-Version: 1.0
To: Dmitriy Kuptsov <Dmitriy.Kuptsov@hiit.fi>
References: <1268332644.4b993864212f8@webmail.otaverkko.fi>
In-Reply-To: <1268332644.4b993864212f8@webmail.otaverkko.fi>
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
Cc: hipsec@ietf.org
Subject: Re: [Hipsec] replacing DH in HIP
X-BeenThere: hipsec@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: "This is the official IETF Mailing List for the HIP Working Group." <hipsec.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/hipsec>, <mailto:hipsec-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/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, 15 Mar 2010 14:57:41 -0000

On 03/11/2010 01:37 PM, Dmitriy Kuptsov wrote:
> Hi all,
>
> Recently, at Helsinki Institute for Information Technology, we were trying to
> run HIP on sensor nodes, even though computing DH public values and secret is
> not a problem in terms of time, such operation consumes a lot of energy. So I
> was wondering if DH can be replace with something more lightweight, e.g,
> bivariate polynomials.

Can you provide some literature references for this algorithm? And where 
else it is used?

>   Consider a modified HIP base exchange:
>
> I                                                            R
> |                 HITi, HITr, HostIDi                        |
> |----------------------------------------------------------->|
> |   HITi, HITr, HostIDr, Puzzle, Enc_pubI(Poly_r), Sig       |
> |<-----------------------------------------------------------|
> |    HITi, HITr, Solution, Enc_pubR(Poly_i), Sig, HMAC       |
> |----------------------------------------------------------->|
> |                HITi, HITr, HMAC, Sig                       |
> |<-----------------------------------------------------------|
>
> Where the modifications are:
> (i) I1 carries the host identity, aka public key, of the initiator as parameter
> (ii) R1 carries additional encrypted using Initiators public key (found in I1)
> parameter which contains a randomly generated (by responder) bivariate
> polynomial of form for instance f(rand_r XOR HITr, y). Probably here it is
> impossible to have pre-generate R1's.
> (iii) I2 carries the encrypted using Responder's public key bivariate polynomial
> of form for instance f(rand_r XOR HITr, rand_i XOR HIT i) such that R gets now
> the secret key.
> (iv) R2 remains the unmodified.
>
> Here Enc function can be RSA or ECC using public key of receiver of a message
> such that eavesdropper cannot obtain the polynomial send in R1 or I2 messages.
>
> The bivariate polynomials f(x, y) = a0+a1xy+a2x^2y^2+...+anx^ny^n can be
> implemented really efficiently in sensor nodes over field G(2^16) and later
> using several such polynomials to construct a key of needed size. For instance,
> to construct a shared key of 80 bits Responder randomly selects 5 bivariate
> polynomials (all with different coefficients):
> f_1(rand_r_1 XOR HITr, y)
> f_2(rand_r_2 XOR HITr, y)
> f_3(rand_r_3 XOR HITr, y)
> f_4(rand_r_4 XOR HITr, y)
> f_5(rand_r_5 XOR HITr, y)
> Or may be even consecutive polynomials can be derived using some key derivation
> function...
>
> Then the initiator computes all 5 polynomials and gets the key as
> Key = (f_1(rand_r_1 XOR HITr, rand_r_1 XOR HITi) || ... ||f_5(rand_r_5 XOR HITr,
> rand_r_5 XOR HITi))
>
> The same key is obtained by responder once it receives an I2 message.
>
> Of course such approach does not comply with HIP specs in many ways. However, is
> it feasible/secure to do something like this?
>
> Kind regards,
> Dmitriy Kuptsov
>
>
> _______________________________________________
> Hipsec mailing list
> Hipsec@ietf.org
> https://www.ietf.org/mailman/listinfo/hipsec
>
>    

From rgm@htt-consult.com  Mon Mar 15 12:19:02 2010
Return-Path: <rgm@htt-consult.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 580FF3A6BBE for <hipsec@core3.amsl.com>; Mon, 15 Mar 2010 12:19:02 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.999
X-Spam-Level: 
X-Spam-Status: No, score=-0.999 tagged_above=-999 required=5 tests=[AWL=1.000,  BAYES_00=-2.599, J_CHICKENPOX_13=0.6]
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 Ig530tMTTEj8 for <hipsec@core3.amsl.com>; Mon, 15 Mar 2010 12:19:00 -0700 (PDT)
Received: from klovia.htt-consult.com (klovia.htt-consult.com [208.83.67.149]) by core3.amsl.com (Postfix) with ESMTP id CCA9F3A69ED for <hipsec@ietf.org>; Mon, 15 Mar 2010 12:18:52 -0700 (PDT)
Received: from localhost (unknown [127.0.0.1]) by klovia.htt-consult.com (Postfix) with ESMTP id 1116768B4B for <hipsec@ietf.org>; Mon, 15 Mar 2010 20:14:27 +0000 (UTC)
X-Virus-Scanned: amavisd-new at localhost
Received: from klovia.htt-consult.com ([127.0.0.1]) by localhost (klovia.htt-consult.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id r8N7yRzbtYst for <hipsec@ietf.org>; Mon, 15 Mar 2010 16:14:17 -0400 (EDT)
Received: from nc2400.htt-consult.com (unknown [199.72.57.111]) (Authenticated sender: rgm@htt-consult.com) by klovia.htt-consult.com (Postfix) with ESMTPSA id BE36E68B43 for <hipsec@ietf.org>; Mon, 15 Mar 2010 16:14:16 -0400 (EDT)
Message-ID: <4B9E880D.7090705@htt-consult.com>
Date: Mon, 15 Mar 2010 15:18:37 -0400
From: Robert Moskowitz <rgm@htt-consult.com>
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.9.1.8) Gecko/20100301 Fedora/3.0.3-1.fc12 Thunderbird/3.0.3
MIME-Version: 1.0
To: hipsec@ietf.org
References: <1268332644.4b993864212f8@webmail.otaverkko.fi>
In-Reply-To: <1268332644.4b993864212f8@webmail.otaverkko.fi>
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 8bit
Subject: Re: [Hipsec] replacing DH in HIP
X-BeenThere: hipsec@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: "This is the official IETF Mailing List for the HIP Working Group." <hipsec.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/hipsec>, <mailto:hipsec-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/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, 15 Mar 2010 19:19:02 -0000

posting back to the list.

On 03/15/2010 12:03 PM, Dmitriy Kuptsov wrote:
> Hi,
>
> Thank you for the replay. You can find this kind of "key exchange" for
> instance in [2] which was used for wireless sensor networks. There is
> also some background material in [1] and an application in technical
> report [3].
>    

Thank you for this information.

Are there any more recent references?

For sensors vendors that I have been talking to, code size is just as 
much a concern as cpu requirements. How does this approach compare to a 
DH EC implementation?

> Note that in [2] the polynomials are generated before the actual
> deployment, that is for instance node with IDa after deployment stores a
> set of polynomials, e.g., f(IDa, IDb), ..., f(IDa, IDx), such that it
> can only establish a pair wise secure channels with nodes identified by
> IDb, ..., IDx correspondingly. However, this kind of presharing has its
> limitations (frankly speaking it is not scalable). So that is why I
> though whether it can be useful/meaningful to use HIP to agree on a
> common polynomial(s) between 2 sensors nodes during base exchange and
> use the result to derive a common key.
>
> Of course the modification of HIP base exchange below does not necessary
> require the polynomials to be used (they can be interpreted as key
> derivation functions). Instead it can be that initiator and responder
> exchange 2 random strings (which are carried in R1 and I2 and encrypted
> using corresponding public keys), and later use those to derive a common
> key (if it is secure of course).
>
> References:
> [1] Carlo Blundo, Alfredo De Santis, Amir Herzberg, Shay Kutten, Ugo
> Vaccaro, and Moti Yung. "Perfectly-secure key distribution for dynamic
> conferences" In CRYPTO, pages 471鈥�486, 1992.
> [2] DONGGANG LIU, PENG NING and RONGFANG LI, "Establishing Pairwise Keys
> in Distributed Sensor Networks" in Proceedings of ACM Conference on
> Computer and Communications Security 2003 (CCS'03) ***
> [3] Abedelaziz Mohaisen "Password Authentication and Key Exchange
> Protocol" technical report
>
> *** also full paper exist
>
> On Mon, 2010-03-15 at 10:57 -0400, Robert Moskowitz wrote:
>    
>> On 03/11/2010 01:37 PM, Dmitriy Kuptsov wrote:
>>      
>>> Hi all,
>>>
>>> Recently, at Helsinki Institute for Information Technology, we were trying to
>>> run HIP on sensor nodes, even though computing DH public values and secret is
>>> not a problem in terms of time, such operation consumes a lot of energy. So I
>>> was wondering if DH can be replace with something more lightweight, e.g,
>>> bivariate polynomials.
>>>        
>> Can you provide some literature references for this algorithm? And where
>> else it is used?
>>
>>      
>>>    Consider a modified HIP base exchange:
>>>
>>> I                                                            R
>>> |                 HITi, HITr, HostIDi                        |
>>> |----------------------------------------------------------->|
>>> |   HITi, HITr, HostIDr, Puzzle, Enc_pubI(Poly_r), Sig       |
>>> |<-----------------------------------------------------------|
>>> |    HITi, HITr, Solution, Enc_pubR(Poly_i), Sig, HMAC       |
>>> |----------------------------------------------------------->|
>>> |                HITi, HITr, HMAC, Sig                       |
>>> |<-----------------------------------------------------------|
>>>
>>> Where the modifications are:
>>> (i) I1 carries the host identity, aka public key, of the initiator as parameter
>>> (ii) R1 carries additional encrypted using Initiators public key (found in I1)
>>> parameter which contains a randomly generated (by responder) bivariate
>>> polynomial of form for instance f(rand_r XOR HITr, y). Probably here it is
>>> impossible to have pre-generate R1's.
>>> (iii) I2 carries the encrypted using Responder's public key bivariate polynomial
>>> of form for instance f(rand_r XOR HITr, rand_i XOR HIT i) such that R gets now
>>> the secret key.
>>> (iv) R2 remains the unmodified.
>>>
>>> Here Enc function can be RSA or ECC using public key of receiver of a message
>>> such that eavesdropper cannot obtain the polynomial send in R1 or I2 messages.
>>>
>>> The bivariate polynomials f(x, y) = a0+a1xy+a2x^2y^2+...+anx^ny^n can be
>>> implemented really efficiently in sensor nodes over field G(2^16+1) and later
>>> using several such polynomials to construct a key of needed size. For instance,
>>> to construct a shared key of 80 bits Responder randomly selects 5 bivariate
>>> polynomials (all with different coefficients):
>>> f_1(rand_r_1 XOR HITr, y)
>>> f_2(rand_r_2 XOR HITr, y)
>>> f_3(rand_r_3 XOR HITr, y)
>>> f_4(rand_r_4 XOR HITr, y)
>>> f_5(rand_r_5 XOR HITr, y)
>>> Or may be even consecutive polynomials can be derived using some key derivation
>>> function...
>>>
>>> Then the initiator computes all 5 polynomials and gets the key as
>>> Key = (f_1(rand_r_1 XOR HITr, rand_r_1 XOR HITi) || ... ||f_5(rand_r_5 XOR HITr,
>>> rand_r_5 XOR HITi))
>>>
>>> The same key is obtained by responder once it receives an I2 message.
>>>
>>> Of course such approach does not comply with HIP specs in many ways. However, is
>>> it feasible/secure to do something like this?
>>>
>>> Kind regards,
>>> Dmitriy Kuptsov
>>>
>>>
>>> _______________________________________________
>>> Hipsec mailing list
>>> Hipsec@ietf.org
>>> https://www.ietf.org/mailman/listinfo/hipsec
>>>
>>>
>>>        
>
>
>    

From dmitriy.kuptsov@hiit.fi  Tue Mar 16 03:15:19 2010
Return-Path: <dmitriy.kuptsov@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 83FB03A692D for <hipsec@core3.amsl.com>; Tue, 16 Mar 2010 03:15:19 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.601
X-Spam-Level: 
X-Spam-Status: No, score=0.601 tagged_above=-999 required=5 tests=[BAYES_50=0.001, J_CHICKENPOX_13=0.6]
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 VSX9fjJRg2VE for <hipsec@core3.amsl.com>; Tue, 16 Mar 2010 03:15:18 -0700 (PDT)
Received: from argo.otaverkko.fi (argo.otaverkko.fi [212.68.0.2]) by core3.amsl.com (Postfix) with ESMTP id 3AE0E3A67F9 for <hipsec@ietf.org>; Tue, 16 Mar 2010 03:15:17 -0700 (PDT)
Received: from [128.214.114.91] (wyoming.pc.hiit.fi [128.214.114.91]) by argo.otaverkko.fi (Postfix) with ESMTP id 3EEE525ED15; Tue, 16 Mar 2010 12:15:25 +0200 (EET)
From: Dmitriy Kuptsov <dmitriy.kuptsov@hiit.fi>
To: Robert Moskowitz <rgm@htt-consult.com>
In-Reply-To: <4B9E880D.7090705@htt-consult.com>
References: <1268332644.4b993864212f8@webmail.otaverkko.fi> <4B9E880D.7090705@htt-consult.com>
Content-Type: text/plain; charset="UTF-8"
Organization: HIIT, TKK
Date: Tue, 16 Mar 2010 12:15:24 +0200
Message-ID: <1268734524.3020.299.camel@dmitriy-desktop.hiit.fi>
Mime-Version: 1.0
X-Mailer: Evolution 2.28.1 
Content-Transfer-Encoding: 8bit
Cc: hipsec@ietf.org
Subject: Re: [Hipsec] replacing DH in HIP
X-BeenThere: hipsec@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
Reply-To: dmitriy.kuptsov@hiit.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: Tue, 16 Mar 2010 10:15:19 -0000

Hi,

On Mon, 2010-03-15 at 15:18 -0400, Robert Moskowitz wrote:
> posting back to the list.
> 
> On 03/15/2010 12:03 PM, Dmitriy Kuptsov wrote:
> > Hi,
> >
> > Thank you for the replay. You can find this kind of "key exchange" for
> > instance in [2] which was used for wireless sensor networks. There is
> > also some background material in [1] and an application in technical
> > report [3].
> >    
> 
> Thank you for this information.
> 
> Are there any more recent references?

Well, at least I am not aware of any other right now.

> For sensors vendors that I have been talking to, code size is just as 
> much a concern as cpu requirements. How does this approach compare to a 
> DH EC implementation?

Talking in terms of energy consumption?

We did not evaluate ECDH on sensors yet (only DH), but we did measure
the polynomial computation which is really efficient (probably we can
provide some figures by the end of this week). According to [4] ECDH key
exchange (not authenticated; 192-bits prime field was used) consumes
57.33 mJ per node on MICAz mote (ATmega128 platform). Also in [4] it was
estimated using model from [5] (where 2 AA batteries with capacity of
2500  mAh are used for power supply) that 117,750 key exchanges are
possible before the battery voltage drops below critical level.

[4] Christian Lederer, Roland Mader, Manuel Koschuch, Johann Gro脽sch盲dl,
Alexander Szekely, and Stefan Tillich : "Energy-Efficient Implementation
of ECDH Key Exchange for Wireless Sensor Networks" 
[5] Krzysztof Piotrowski, Peter Langendoerfer and Steffen Peter : "How
Public Key Cryptography Influences Wireless Sensor Node Lifetime"

> > Note that in [2] the polynomials are generated before the actual
> > deployment, that is for instance node with IDa after deployment stores a
> > set of polynomials, e.g., f(IDa, IDb), ..., f(IDa, IDx), such that it
> > can only establish a pair wise secure channels with nodes identified by
> > IDb, ..., IDx correspondingly. However, this kind of presharing has its
> > limitations (frankly speaking it is not scalable). So that is why I
> > though whether it can be useful/meaningful to use HIP to agree on a
> > common polynomial(s) between 2 sensors nodes during base exchange and
> > use the result to derive a common key.
> >
> > Of course the modification of HIP base exchange below does not necessary
> > require the polynomials to be used (they can be interpreted as key
> > derivation functions). Instead it can be that initiator and responder
> > exchange 2 random strings (which are carried in R1 and I2 and encrypted
> > using corresponding public keys), and later use those to derive a common
> > key (if it is secure of course).
> >
> > References:
> > [1] Carlo Blundo, Alfredo De Santis, Amir Herzberg, Shay Kutten, Ugo
> > Vaccaro, and Moti Yung. "Perfectly-secure key distribution for dynamic
> > conferences" In CRYPTO, pages 471鈥�486, 1992.
> > [2] DONGGANG LIU, PENG NING and RONGFANG LI, "Establishing Pairwise Keys
> > in Distributed Sensor Networks" in Proceedings of ACM Conference on
> > Computer and Communications Security 2003 (CCS'03) ***
> > [3] Abedelaziz Mohaisen "Password Authentication and Key Exchange
> > Protocol" technical report
> >
> > *** also full paper exist
> >
> > On Mon, 2010-03-15 at 10:57 -0400, Robert Moskowitz wrote:
> >    
> >> On 03/11/2010 01:37 PM, Dmitriy Kuptsov wrote:
> >>      
> >>> Hi all,
> >>>
> >>> Recently, at Helsinki Institute for Information Technology, we were trying to
> >>> run HIP on sensor nodes, even though computing DH public values and secret is
> >>> not a problem in terms of time, such operation consumes a lot of energy. So I
> >>> was wondering if DH can be replace with something more lightweight, e.g,
> >>> bivariate polynomials.
> >>>        
> >> Can you provide some literature references for this algorithm? And where
> >> else it is used?
> >>
> >>      
> >>>    Consider a modified HIP base exchange:
> >>>
> >>> I                                                            R
> >>> |                 HITi, HITr, HostIDi                        |
> >>> |----------------------------------------------------------->|
> >>> |   HITi, HITr, HostIDr, Puzzle, Enc_pubI(Poly_r), Sig       |
> >>> |<-----------------------------------------------------------|
> >>> |    HITi, HITr, Solution, Enc_pubR(Poly_i), Sig, HMAC       |
> >>> |----------------------------------------------------------->|
> >>> |                HITi, HITr, HMAC, Sig                       |
> >>> |<-----------------------------------------------------------|
> >>>
> >>> Where the modifications are:
> >>> (i) I1 carries the host identity, aka public key, of the initiator as parameter
> >>> (ii) R1 carries additional encrypted using Initiators public key (found in I1)
> >>> parameter which contains a randomly generated (by responder) bivariate
> >>> polynomial of form for instance f(rand_r XOR HITr, y). Probably here it is
> >>> impossible to have pre-generate R1's.
> >>> (iii) I2 carries the encrypted using Responder's public key bivariate polynomial
> >>> of form for instance f(rand_r XOR HITr, rand_i XOR HIT i) such that R gets now
> >>> the secret key.
> >>> (iv) R2 remains the unmodified.
> >>>
> >>> Here Enc function can be RSA or ECC using public key of receiver of a message
> >>> such that eavesdropper cannot obtain the polynomial send in R1 or I2 messages.
> >>>
> >>> The bivariate polynomials f(x, y) = a0+a1xy+a2x^2y^2+...+anx^ny^n can be
> >>> implemented really efficiently in sensor nodes over field G(2^16+1) and later
> >>> using several such polynomials to construct a key of needed size. For instance,
> >>> to construct a shared key of 80 bits Responder randomly selects 5 bivariate
> >>> polynomials (all with different coefficients):
> >>> f_1(rand_r_1 XOR HITr, y)
> >>> f_2(rand_r_2 XOR HITr, y)
> >>> f_3(rand_r_3 XOR HITr, y)
> >>> f_4(rand_r_4 XOR HITr, y)
> >>> f_5(rand_r_5 XOR HITr, y)
> >>> Or may be even consecutive polynomials can be derived using some key derivation
> >>> function...
> >>>
> >>> Then the initiator computes all 5 polynomials and gets the key as
> >>> Key = (f_1(rand_r_1 XOR HITr, rand_r_1 XOR HITi) || ... ||f_5(rand_r_5 XOR HITr,
> >>> rand_r_5 XOR HITi))
> >>>
> >>> The same key is obtained by responder once it receives an I2 message.
> >>>
> >>> Of course such approach does not comply with HIP specs in many ways. However, is
> >>> it feasible/secure to do something like this?
> >>>
> >>> Kind regards,
> >>> Dmitriy Kuptsov
> >>>
> >>>
> >>> _______________________________________________
> >>> Hipsec mailing list
> >>> Hipsec@ietf.org
> >>> https://www.ietf.org/mailman/listinfo/hipsec
> >>>
> >>>
> >>>        
> >
> >
> >    
> _______________________________________________
> Hipsec mailing list
> Hipsec@ietf.org
> https://www.ietf.org/mailman/listinfo/hipsec



From ari.keranen@nomadiclab.com  Tue Mar 16 03:20:43 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 7FC343A695B for <hipsec@core3.amsl.com>; Tue, 16 Mar 2010 03:20:43 -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 oMzUOU7vf8dC for <hipsec@core3.amsl.com>; Tue, 16 Mar 2010 03:20:42 -0700 (PDT)
Received: from gw.nomadiclab.com (unknown [IPv6:2001:14b8:400:101::2]) by core3.amsl.com (Postfix) with ESMTP id D16CB3A68DC for <hipsec@ietf.org>; Tue, 16 Mar 2010 03:20:35 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by gw.nomadiclab.com (Postfix) with ESMTP id 491C54E6D3 for <hipsec@ietf.org>; Tue, 16 Mar 2010 12:20:42 +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 a2d3BzBH95UE for <hipsec@ietf.org>; Tue, 16 Mar 2010 12:20:41 +0200 (EET)
Received: from [IPv6:2001:14b8:400:101:21c:23ff:fe45:a6c1] (unknown [IPv6:2001:14b8:400:101:21c:23ff:fe45:a6c1]) by gw.nomadiclab.com (Postfix) with ESMTP id C070D4E6CD for <hipsec@ietf.org>; Tue, 16 Mar 2010 12:20:41 +0200 (EET)
Message-ID: <4B9F5B79.1080103@nomadiclab.com>
Date: Tue, 16 Mar 2010 12:20:41 +0200
From: Ari Keranen <ari.keranen@nomadiclab.com>
User-Agent: Thunderbird 2.0.0.23 (X11/20090817)
MIME-Version: 1.0
To: HIP <hipsec@ietf.org>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Subject: [Hipsec] Making hip-over-hip draft a WG item
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, 16 Mar 2010 10:20:43 -0000

Hi all,

The HIP-over-HIP draft specifies how HIP signaling messages can be sent 
over encrypted (ESP) connections. This feature is useful, e.g., in some 
scenarios involving overlays and therefore it would make sense to 
standardize it.

http://tools.ietf.org/html/draft-keranen-hip-over-hip-01

Would people support this draft to become a WG item?


Cheers,
Ari

From dmitriy.kuptsov@hiit.fi  Tue Mar 16 03:46:07 2010
Return-Path: <dmitriy.kuptsov@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 B80273A6931 for <hipsec@core3.amsl.com>; Tue, 16 Mar 2010 03:46:07 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.601
X-Spam-Level: 
X-Spam-Status: No, score=0.601 tagged_above=-999 required=5 tests=[BAYES_50=0.001, J_CHICKENPOX_13=0.6]
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 IXb8FgmlJnjc for <hipsec@core3.amsl.com>; Tue, 16 Mar 2010 03:46:06 -0700 (PDT)
Received: from argo.otaverkko.fi (argo.otaverkko.fi [212.68.0.2]) by core3.amsl.com (Postfix) with ESMTP id 526983A67E1 for <hipsec@ietf.org>; Tue, 16 Mar 2010 03:46:06 -0700 (PDT)
Received: from [128.214.114.91] (wyoming.pc.hiit.fi [128.214.114.91]) by argo.otaverkko.fi (Postfix) with ESMTP id 6E28E25ED13; Tue, 16 Mar 2010 12:46:14 +0200 (EET)
From: Dmitriy Kuptsov <dmitriy.kuptsov@hiit.fi>
To: Robert Moskowitz <rgm@htt-consult.com>
In-Reply-To: <1268734524.3020.299.camel@dmitriy-desktop.hiit.fi>
References: <1268332644.4b993864212f8@webmail.otaverkko.fi> <4B9E880D.7090705@htt-consult.com> <1268734524.3020.299.camel@dmitriy-desktop.hiit.fi>
Content-Type: text/plain; charset="UTF-8"
Organization: HIIT, TKK
Date: Tue, 16 Mar 2010 12:46:13 +0200
Message-ID: <1268736373.3020.302.camel@dmitriy-desktop.hiit.fi>
Mime-Version: 1.0
X-Mailer: Evolution 2.28.1 
Content-Transfer-Encoding: 8bit
Cc: hipsec@ietf.org
Subject: Re: [Hipsec] replacing DH in HIP
X-BeenThere: hipsec@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
Reply-To: dmitriy.kuptsov@hiit.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: Tue, 16 Mar 2010 10:46:07 -0000

Hi,

On Tue, 2010-03-16 at 12:15 +0200, Dmitriy Kuptsov wrote:
> Hi,
> 
> On Mon, 2010-03-15 at 15:18 -0400, Robert Moskowitz wrote:
> > posting back to the list.
> > 
> > On 03/15/2010 12:03 PM, Dmitriy Kuptsov wrote:
> > > Hi,
> > >
> > > Thank you for the replay. You can find this kind of "key exchange" for
> > > instance in [2] which was used for wireless sensor networks. There is
> > > also some background material in [1] and an application in technical
> > > report [3].
> > >    
> > 
> > Thank you for this information.
> > 
> > Are there any more recent references?
> 
> Well, at least I am not aware of any other right now.
> 
> > For sensors vendors that I have been talking to, code size is just as 
> > much a concern as cpu requirements. How does this approach compare to a 
> > DH EC implementation?

If talking about code size in RAM and comparing just ECDH and
polynomials then i would bet that later requires less. 

> 
> Talking in terms of energy consumption?
> 
> We did not evaluate ECDH on sensors yet (only DH), but we did measure
> the polynomial computation which is really efficient (probably we can
> provide some figures by the end of this week). According to [4] ECDH key
> exchange (not authenticated; 192-bits prime field was used) consumes
> 57.33 mJ per node on MICAz mote (ATmega128 platform). Also in [4] it was
> estimated using model from [5] (where 2 AA batteries with capacity of
> 2500  mAh are used for power supply) that 117,750 key exchanges are
> possible before the battery voltage drops below critical level.
> 
> [4] Christian Lederer, Roland Mader, Manuel Koschuch, Johann Gro脽sch盲dl,
> Alexander Szekely, and Stefan Tillich : "Energy-Efficient Implementation
> of ECDH Key Exchange for Wireless Sensor Networks" 
> [5] Krzysztof Piotrowski, Peter Langendoerfer and Steffen Peter : "How
> Public Key Cryptography Influences Wireless Sensor Node Lifetime"
> 
> > > Note that in [2] the polynomials are generated before the actual
> > > deployment, that is for instance node with IDa after deployment stores a
> > > set of polynomials, e.g., f(IDa, IDb), ..., f(IDa, IDx), such that it
> > > can only establish a pair wise secure channels with nodes identified by
> > > IDb, ..., IDx correspondingly. However, this kind of presharing has its
> > > limitations (frankly speaking it is not scalable). So that is why I
> > > though whether it can be useful/meaningful to use HIP to agree on a
> > > common polynomial(s) between 2 sensors nodes during base exchange and
> > > use the result to derive a common key.
> > >
> > > Of course the modification of HIP base exchange below does not necessary
> > > require the polynomials to be used (they can be interpreted as key
> > > derivation functions). Instead it can be that initiator and responder
> > > exchange 2 random strings (which are carried in R1 and I2 and encrypted
> > > using corresponding public keys), and later use those to derive a common
> > > key (if it is secure of course).
> > >
> > > References:
> > > [1] Carlo Blundo, Alfredo De Santis, Amir Herzberg, Shay Kutten, Ugo
> > > Vaccaro, and Moti Yung. "Perfectly-secure key distribution for dynamic
> > > conferences" In CRYPTO, pages 471鈥�486, 1992.
> > > [2] DONGGANG LIU, PENG NING and RONGFANG LI, "Establishing Pairwise Keys
> > > in Distributed Sensor Networks" in Proceedings of ACM Conference on
> > > Computer and Communications Security 2003 (CCS'03) ***
> > > [3] Abedelaziz Mohaisen "Password Authentication and Key Exchange
> > > Protocol" technical report
> > >
> > > *** also full paper exist
> > >
> > > On Mon, 2010-03-15 at 10:57 -0400, Robert Moskowitz wrote:
> > >    
> > >> On 03/11/2010 01:37 PM, Dmitriy Kuptsov wrote:
> > >>      
> > >>> Hi all,
> > >>>
> > >>> Recently, at Helsinki Institute for Information Technology, we were trying to
> > >>> run HIP on sensor nodes, even though computing DH public values and secret is
> > >>> not a problem in terms of time, such operation consumes a lot of energy. So I
> > >>> was wondering if DH can be replace with something more lightweight, e.g,
> > >>> bivariate polynomials.
> > >>>        
> > >> Can you provide some literature references for this algorithm? And where
> > >> else it is used?
> > >>
> > >>      
> > >>>    Consider a modified HIP base exchange:
> > >>>
> > >>> I                                                            R
> > >>> |                 HITi, HITr, HostIDi                        |
> > >>> |----------------------------------------------------------->|
> > >>> |   HITi, HITr, HostIDr, Puzzle, Enc_pubI(Poly_r), Sig       |
> > >>> |<-----------------------------------------------------------|
> > >>> |    HITi, HITr, Solution, Enc_pubR(Poly_i), Sig, HMAC       |
> > >>> |----------------------------------------------------------->|
> > >>> |                HITi, HITr, HMAC, Sig                       |
> > >>> |<-----------------------------------------------------------|
> > >>>
> > >>> Where the modifications are:
> > >>> (i) I1 carries the host identity, aka public key, of the initiator as parameter
> > >>> (ii) R1 carries additional encrypted using Initiators public key (found in I1)
> > >>> parameter which contains a randomly generated (by responder) bivariate
> > >>> polynomial of form for instance f(rand_r XOR HITr, y). Probably here it is
> > >>> impossible to have pre-generate R1's.
> > >>> (iii) I2 carries the encrypted using Responder's public key bivariate polynomial
> > >>> of form for instance f(rand_r XOR HITr, rand_i XOR HIT i) such that R gets now
> > >>> the secret key.
> > >>> (iv) R2 remains the unmodified.
> > >>>
> > >>> Here Enc function can be RSA or ECC using public key of receiver of a message
> > >>> such that eavesdropper cannot obtain the polynomial send in R1 or I2 messages.
> > >>>
> > >>> The bivariate polynomials f(x, y) = a0+a1xy+a2x^2y^2+...+anx^ny^n can be
> > >>> implemented really efficiently in sensor nodes over field G(2^16+1) and later
> > >>> using several such polynomials to construct a key of needed size. For instance,
> > >>> to construct a shared key of 80 bits Responder randomly selects 5 bivariate
> > >>> polynomials (all with different coefficients):
> > >>> f_1(rand_r_1 XOR HITr, y)
> > >>> f_2(rand_r_2 XOR HITr, y)
> > >>> f_3(rand_r_3 XOR HITr, y)
> > >>> f_4(rand_r_4 XOR HITr, y)
> > >>> f_5(rand_r_5 XOR HITr, y)
> > >>> Or may be even consecutive polynomials can be derived using some key derivation
> > >>> function...
> > >>>
> > >>> Then the initiator computes all 5 polynomials and gets the key as
> > >>> Key = (f_1(rand_r_1 XOR HITr, rand_r_1 XOR HITi) || ... ||f_5(rand_r_5 XOR HITr,
> > >>> rand_r_5 XOR HITi))
> > >>>
> > >>> The same key is obtained by responder once it receives an I2 message.
> > >>>
> > >>> Of course such approach does not comply with HIP specs in many ways. However, is
> > >>> it feasible/secure to do something like this?
> > >>>
> > >>> Kind regards,
> > >>> Dmitriy Kuptsov
> > >>>
> > >>>
> > >>> _______________________________________________
> > >>> Hipsec mailing list
> > >>> Hipsec@ietf.org
> > >>> https://www.ietf.org/mailman/listinfo/hipsec
> > >>>
> > >>>
> > >>>        
> > >
> > >
> > >    
> > _______________________________________________
> > Hipsec mailing list
> > Hipsec@ietf.org
> > https://www.ietf.org/mailman/listinfo/hipsec
> 
> 
> _______________________________________________
> Hipsec mailing list
> Hipsec@ietf.org
> https://www.ietf.org/mailman/listinfo/hipsec



From heer@informatik.rwth-aachen.de  Tue Mar 16 04:32:21 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 ADD5E3A6A6A for <hipsec@core3.amsl.com>; Tue, 16 Mar 2010 04:32:21 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.438
X-Spam-Level: 
X-Spam-Status: No, score=-3.438 tagged_above=-999 required=5 tests=[AWL=-0.496, BAYES_20=-0.74, 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 gsaTUaayRZs0 for <hipsec@core3.amsl.com>; Tue, 16 Mar 2010 04:32:20 -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 5393E3A6A4F for <hipsec@ietf.org>; Tue, 16 Mar 2010 04:31:01 -0700 (PDT)
MIME-version: 1.0
Content-transfer-encoding: 7BIT
Content-type: text/plain; charset=us-ascii
Received: from ironport-out-2.rz.rwth-aachen.de ([134.130.5.41]) 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 <0KZD005Q3HBVRZG0@mta-2.ms.rz.RWTH-Aachen.de> for hipsec@ietf.org; Tue, 16 Mar 2010 12:31:07 +0100 (CET)
X-IronPort-AV: E=Sophos;i="4.49,649,1262559600";   d="scan'208";a="26336706"
Received: from relay-auth-1.ms.rz.rwth-aachen.de (HELO relay-auth-1) ([134.130.7.78]) by ironport-in-2.rz.rwth-aachen.de with ESMTP; Tue, 16 Mar 2010 12:31:08 +0100
Received: from umic-137-226-154-185.nn.rwth-aachen.de ([unknown] [137.226.154.185]) by relay-auth-1.ms.rz.rwth-aachen.de (Sun Java(tm) System Messaging Server 7.0-3.01 64bit (built Dec 9 2008)) with ESMTPA id <0KZD00E67HBV0090@relay-auth-1.ms.rz.rwth-aachen.de> for hipsec@ietf.org; Tue, 16 Mar 2010 12:31:07 +0100 (CET)
From: Tobias Heer <heer@cs.rwth-aachen.de>
In-reply-to: <1268332644.4b993864212f8@webmail.otaverkko.fi>
Date: Tue, 16 Mar 2010 12:31:16 +0100
Message-id: <C203E2BC-250E-49C3-8983-EE68E75F5D31@cs.rwth-aachen.de>
References: <1268332644.4b993864212f8@webmail.otaverkko.fi>
To: Dmitriy Kuptsov <Dmitriy.Kuptsov@hiit.fi>
X-Mailer: Apple Mail (2.1077)
Cc: hipsec@ietf.org
Subject: Re: [Hipsec] replacing DH in HIP
X-BeenThere: hipsec@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: "This is the official IETF Mailing List for the HIP Working Group." <hipsec.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/hipsec>, <mailto:hipsec-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/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, 16 Mar 2010 11:32:21 -0000

Hello Dimitriy, 

Am 11.03.2010 um 19:37 schrieb Dmitriy Kuptsov:


> Hi all,
> 
> Recently, at Helsinki Institute for Information Technology, we were trying to
> run HIP on sensor nodes, even though computing DH public values and secret is
> not a problem in terms of time, such operation consumes a lot of energy. So I
> was wondering if DH can be replace with something more lightweight, e.g,
> bivariate polynomials. Consider a modified HIP base exchange:
> 

[...]

> Of course such approach does not comply with HIP specs in many ways. However, is
> it feasible/secure to do something like this?
> 

HIP is currently very IP-network focused (updates, NAT traversal, address verification in the base exchange, etc.). It can be used in other scenarios, of course. However, I wonder how much of HIP becomes obsolete when you push it into your scenario. What features of HIP do you require?

There are some problems when using polynomial shares that require to use them in a tightly controlled closed system (please correct me if I am wrong). This would considerably change the way HIP works. Maybe you can comment on these issues in the context of HIP: 

a) they require a trust center that holds the basic keying material. Hence, hosts cannot generate their keys by themselves anymore. Moreover, AFAIK there must be one basic keying material, so distributing the role of trust centers is difficult. In HIP hosts can generate their cryptographic keys by themselves without any help from outside. Do we have to give up this property?
b) the protocol is only alpha-secure. This means that the trust center must be careful when handing out keying material. Otherwise there is a chance that all keying material is compromised. Therefore, the approach requires some measures like user registration, etc. to make sure that one user cannot gather more shares than necessary to break the security. Are there established approaches to circumvent this limitation?
c) there is no perfect forward secrecy (as opposed to DH). If the polynomial shares are compromised (for the whole system or just for one node) all previous (recorded) communications are available to attackers. Are there any countermeasures to avoid this?
d) the size of the keying material is related to the maximum numbers of hosts in the system (because of the alpha-secure property). Where are the scalability limits of the approach. Is it sensible to assume 100, 1000, or billions of hosts that can be supported?

Some more questions: 
Is interoperability with ordinary HIP nodes a goal or will the communication just be between sensors?
Is the puzzle mechanism of importance because of DoS (AFAIK DH computation cost is one of the main reasons to have it)?
How is ID-locator resolution handled in your scenario or is it of any relevance (maybe you only have direct communication anyway)?

Don't get me wrong: the reason I am asking is not to oppose your approach. I just want to understand it better. In general I appreciate all efforts of speeding up HIP and of extending its scope.

BR, 

Tobias

 

--  

Dipl.-Inform. Tobias Heer, Ph.D. Student
Distributed Systems Group 
RWTH Aachen University, Germany
tel: +49 241 80 207 76
web: http://ds.cs.rwth-aachen.de/members/heer








From Dmitriy.Kuptsov@hiit.fi  Tue Mar 16 10:07:01 2010
Return-Path: <Dmitriy.Kuptsov@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 BA9B53A69A2 for <hipsec@core3.amsl.com>; Tue, 16 Mar 2010 10:07:01 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.001
X-Spam-Level: 
X-Spam-Status: No, score=0.001 tagged_above=-999 required=5 tests=[BAYES_50=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 FdTUJrfE4o9s for <hipsec@core3.amsl.com>; Tue, 16 Mar 2010 10:07:00 -0700 (PDT)
Received: from argo.otaverkko.fi (argo.otaverkko.fi [212.68.0.2]) by core3.amsl.com (Postfix) with ESMTP id D64573A6A69 for <hipsec@ietf.org>; Tue, 16 Mar 2010 10:06:55 -0700 (PDT)
Received: from localhost (hydra.otaverkko.fi [212.68.0.4]) by argo.otaverkko.fi (Postfix) with ESMTP id D827225ED16; Tue, 16 Mar 2010 19:07:02 +0200 (EET)
Received: from hoasnet-ff00dd00-165.dhcp.inet.fi (hoasnet-ff00dd00-165.dhcp.inet.fi [80.221.0.165])  by webmail.otaverkko.fi (IMP) with HTTP  for <kuptsov.hiit@nestor.otaverkko.fi>; Tue, 16 Mar 2010 19:07:02 +0200
Message-ID: <1268759222.4b9fbab6d27aa@webmail.otaverkko.fi>
Date: Tue, 16 Mar 2010 19:07:02 +0200
From: Dmitriy Kuptsov <Dmitriy.Kuptsov@hiit.fi>
To: Tobias Heer <heer@cs.rwth-aachen.de>
References: <1268332644.4b993864212f8@webmail.otaverkko.fi> <C203E2BC-250E-49C3-8983-EE68E75F5D31@cs.rwth-aachen.de>
In-Reply-To: <C203E2BC-250E-49C3-8983-EE68E75F5D31@cs.rwth-aachen.de>
MIME-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 8bit
User-Agent: Internet Messaging Program (IMP) 3.2.6
X-Originating-IP: 80.221.0.165
Cc: hipsec@ietf.org, Dmitriy Kuptsov <Dmitriy.Kuptsov@hiit.fi>
Subject: Re: [Hipsec] replacing DH in HIP
X-BeenThere: hipsec@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: "This is the official IETF Mailing List for the HIP Working Group." <hipsec.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/hipsec>, <mailto:hipsec-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/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, 16 Mar 2010 17:07:01 -0000

Hi Tobias,

Quoting Tobias Heer <heer@cs.rwth-aachen.de>:

> Hello Dimitriy,
> [...]
> HIP is currently very IP-network focused (updates, NAT traversal, address
> verification in the base exchange, etc.). It can be used in other scenarios,
> of course. However, I wonder how much of HIP becomes obsolete when you push
> it into your scenario. What features of HIP do you require?

In my opinion for wireless sensor networks the following should be possible:
(i) node identification (using HITs) and authentication (using host identities)
(ii) shared secret negotiation
(iii) transform suit negotiation

> There are some problems when using polynomial shares that require to use them
> in a tightly controlled closed system (please correct me if I am wrong). This

We might have some misunderstanding, but I am not sure.

Well the scenario I have described in previous email there is no need for
trusted 3rd party (TTP) to generating shared secret between initiator and
responder. The only usage of TTP, which is similar to current HIP I assume, is
to allow nodes to authenticate HITs they see in the base exchange using the
certificates for instance.

The only major modification to HIP base exchange is to carry initiator's host
identity already in I1 message such that responder can use it to pass some
secret in R1 message in a secure way. Here secret is a bivariate polynomial (or
polynomials depending on which size of the secret should be generated) to which
I referred previously. The selection of a bivariate polynomial is just to allow
both initiator and responder introduce randomness in key generation process

In my opinion questions a) through d) are not relevant in this context (please
correct me if I am also misunderstood something here)

> would considerably change the way HIP works. Maybe you can comment on these
> issues in the context of HIP:
>
> a) they require a trust center that holds the basic keying material. Hence,
> hosts cannot generate their keys by themselves anymore. Moreover, AFAIK there
> must be one basic keying material, so distributing the role of trust centers
> is difficult. In HIP hosts can generate their cryptographic keys by
> themselves without any help from outside. Do we have to give up this
> property?
N/A
> b) the protocol is only alpha-secure. This means that the trust center must
> be careful when handing out keying material. Otherwise there is a chance that
> all keying material is compromised. Therefore, the approach requires some
> measures like user registration, etc. to make sure that one user cannot
> gather more shares than necessary to break the security. Are there
> established approaches to circumvent this limitation?
N/A

Trust centre does not generate any polynomials to any nodes in the network (I
think I have mentioned it before). The only usage of trust centre can be to
provide a mean for authenticating HITs (for instance (i) using certificates or
(ii) paths of Merkle trees constructed out of HITs acceptable in the network
(iii) something else if exist).

> c) there is no perfect forward secrecy (as opposed to DH). If the polynomial
> shares are compromised (for the whole system or just for one node) all
> previous (recorded) communications are available to attackers. Are there any
> countermeasures to avoid this? N/A

Since polynomial(s) is (are) generated randomly by responder every time it
receives and R1 message (just as it DH public value is currently generated) and
is used only to derive a key for a session with a particular node there should
be no way to correlate it to other polynomials generated in other base
exchanges, etc.

> d) the size of the keying material is related to the maximum numbers of hosts
> in the system (because of the alpha-secure property). Where are the
> scalability limits of the approach. Is it sensible to assume 100, 1000, or
> billions of hosts that can be supported?
N/A

> Some more questions:
> Is interoperability with ordinary HIP nodes a goal or will the communication
> just be between sensors?

Well it is probably favourable to have interoperability with ordinary HIP nodes
for a number of reasons; such as integration of sensor network with Internet,
etc.

> Is the puzzle mechanism of importance because of DoS (AFAIK DH computation
> cost is one of the main reasons to have it)?

Puzzle mechanism probably not so important for sensor networks.

> How is ID-locator resolution handled in your scenario or is it of any
> relevance (maybe you only have direct communication anyway)?

Well it depends on the application it can also be so that nodes are several hops
away.

> Don't get me wrong: the reason I am asking is not to oppose your approach. I
> just want to understand it better. In general I appreciate all efforts of
> speeding up HIP and of extending its scope.

Actually I love to see response to my questions, so no problem. Thank you!

Kind regards,
Dmitriy

> BR,
>
> Tobias
>
>
>
> --
>
> Dipl.-Inform. Tobias Heer, Ph.D. Student
> Distributed Systems Group
> RWTH Aachen University, Germany
> tel: +49 241 80 207 76
> web: http://ds.cs.rwth-aachen.de/members/heer
>
>
>
>
>
>
>
> _______________________________________________
> Hipsec mailing list
> Hipsec@ietf.org
> https://www.ietf.org/mailman/listinfo/hipsec
>





From rgm@htt-consult.com  Tue Mar 16 10:34:20 2010
Return-Path: <rgm@htt-consult.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 432703A69D0 for <hipsec@core3.amsl.com>; Tue, 16 Mar 2010 10:34:20 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.799
X-Spam-Level: 
X-Spam-Status: No, score=-1.799 tagged_above=-999 required=5 tests=[AWL=0.800,  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 fIP0dWGTcb1J for <hipsec@core3.amsl.com>; Tue, 16 Mar 2010 10:34:18 -0700 (PDT)
Received: from klovia.htt-consult.com (klovia.htt-consult.com [208.83.67.149]) by core3.amsl.com (Postfix) with ESMTP id 22FAF3A684A for <hipsec@ietf.org>; Tue, 16 Mar 2010 10:34:17 -0700 (PDT)
Received: from localhost (unknown [127.0.0.1]) by klovia.htt-consult.com (Postfix) with ESMTP id 8704668B43; Tue, 16 Mar 2010 18:29:51 +0000 (UTC)
X-Virus-Scanned: amavisd-new at localhost
Received: from klovia.htt-consult.com ([127.0.0.1]) by localhost (klovia.htt-consult.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 0Kc5MIaeKy5r; Tue, 16 Mar 2010 14:29:41 -0400 (EDT)
Received: from nc2400.htt-consult.com (unknown [199.72.57.111]) (Authenticated sender: rgm@htt-consult.com) by klovia.htt-consult.com (Postfix) with ESMTPSA id C9A9068B40; Tue, 16 Mar 2010 14:29:40 -0400 (EDT)
Message-ID: <4B9FC0E5.6090404@htt-consult.com>
Date: Tue, 16 Mar 2010 13:33:25 -0400
From: Robert Moskowitz <rgm@htt-consult.com>
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.9.1.8) Gecko/20100301 Fedora/3.0.3-1.fc12 Thunderbird/3.0.3
MIME-Version: 1.0
To: Dmitriy Kuptsov <Dmitriy.Kuptsov@hiit.fi>
References: <1268332644.4b993864212f8@webmail.otaverkko.fi>	<C203E2BC-250E-49C3-8983-EE68E75F5D31@cs.rwth-aachen.de> <1268759222.4b9fbab6d27aa@webmail.otaverkko.fi>
In-Reply-To: <1268759222.4b9fbab6d27aa@webmail.otaverkko.fi>
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
Cc: hipsec@ietf.org
Subject: Re: [Hipsec] replacing DH in HIP
X-BeenThere: hipsec@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: "This is the official IETF Mailing List for the HIP Working Group." <hipsec.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/hipsec>, <mailto:hipsec-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/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, 16 Mar 2010 17:34:20 -0000

On 03/16/2010 01:07 PM, Dmitriy Kuptsov wrote:
> Hi Tobias,
>
> Quoting Tobias Heer<heer@cs.rwth-aachen.de>:
>
>    
>> Hello Dimitriy,
>> [...]
>> HIP is currently very IP-network focused (updates, NAT traversal, address
>> verification in the base exchange, etc.). It can be used in other scenarios,
>> of course. However, I wonder how much of HIP becomes obsolete when you push
>> it into your scenario. What features of HIP do you require?
>>      
> In my opinion for wireless sensor networks the following should be possible:
> (i) node identification (using HITs) and authentication (using host identities)
> (ii) shared secret negotiation
> (iii) transform suit negotiation
>    

There will still be the HIT so if the system supports IP, there should 
be no need to run HIP again for IP security.
>    
>> There are some problems when using polynomial shares that require to use them
>> in a tightly controlled closed system (please correct me if I am wrong). This
>>      
> We might have some misunderstanding, but I am not sure.
>
> Well the scenario I have described in previous email there is no need for
> trusted 3rd party (TTP) to generating shared secret between initiator and
> responder.

In my investigations, I am finding out that 'traditionally' bivariate 
polynomials are used to distribute keys from a TTP. Perhaps others are 
assuming this senario. I see that is not your intent, but I am not sure 
of your whole process.

>   The only usage of TTP, which is similar to current HIP I assume, is
> to allow nodes to authenticate HITs they see in the base exchange using the
> certificates for instance.
>
> The only major modification to HIP base exchange is to carry initiator's host
> identity already in I1 message such that responder can use it to pass some
> secret in R1 message in a secure way. Here secret is a bivariate polynomial (or
> polynomials depending on which size of the secret should be generated) to which
> I referred previously. The selection of a bivariate polynomial is just to allow
> both initiator and responder introduce randomness in key generation process
>
> In my opinion questions a) through d) are not relevant in this context (please
> correct me if I am also misunderstood something here)
>
>    
>> would considerably change the way HIP works. Maybe you can comment on these
>> issues in the context of HIP:
>>
>> a) they require a trust center that holds the basic keying material. Hence,
>> hosts cannot generate their keys by themselves anymore. Moreover, AFAIK there
>> must be one basic keying material, so distributing the role of trust centers
>> is difficult. In HIP hosts can generate their cryptographic keys by
>> themselves without any help from outside. Do we have to give up this
>> property?
>>      
> N/A
>    
>> b) the protocol is only alpha-secure. This means that the trust center must
>> be careful when handing out keying material. Otherwise there is a chance that
>> all keying material is compromised. Therefore, the approach requires some
>> measures like user registration, etc. to make sure that one user cannot
>> gather more shares than necessary to break the security. Are there
>> established approaches to circumvent this limitation?
>>      
> N/A
>
> Trust centre does not generate any polynomials to any nodes in the network (I
> think I have mentioned it before). The only usage of trust centre can be to
> provide a mean for authenticating HITs (for instance (i) using certificates or
> (ii) paths of Merkle trees constructed out of HITs acceptable in the network
> (iii) something else if exist).
>
>    
>> c) there is no perfect forward secrecy (as opposed to DH). If the polynomial
>> shares are compromised (for the whole system or just for one node) all
>> previous (recorded) communications are available to attackers. Are there any
>> countermeasures to avoid this? N/A
>>      
> Since polynomial(s) is (are) generated randomly by responder every time it
> receives and R1 message (just as it DH public value is currently generated) and
> is used only to derive a key for a session with a particular node there should
> be no way to correlate it to other polynomials generated in other base
> exchanges, etc.
>
>    
>> d) the size of the keying material is related to the maximum numbers of hosts
>> in the system (because of the alpha-secure property). Where are the
>> scalability limits of the approach. Is it sensible to assume 100, 1000, or
>> billions of hosts that can be supported?
>>      
> N/A
>
>    
>> Some more questions:
>> Is interoperability with ordinary HIP nodes a goal or will the communication
>> just be between sensors?
>>      
> Well it is probably favourable to have interoperability with ordinary HIP nodes
> for a number of reasons; such as integration of sensor network with Internet,
> etc.
>
>    
>> Is the puzzle mechanism of importance because of DoS (AFAIK DH computation
>> cost is one of the main reasons to have it)?
>>      
> Puzzle mechanism probably not so important for sensor networks.
>
>    
>> How is ID-locator resolution handled in your scenario or is it of any
>> relevance (maybe you only have direct communication anyway)?
>>      
> Well it depends on the application it can also be so that nodes are several hops
> away.
>
>    
>> Don't get me wrong: the reason I am asking is not to oppose your approach. I
>> just want to understand it better. In general I appreciate all efforts of
>> speeding up HIP and of extending its scope.
>>      
> Actually I love to see response to my questions, so no problem. Thank you!
>
> Kind regards,
> Dmitriy
>
>    
>> BR,
>>
>> Tobias
>>
>>
>>
>> --
>>
>> Dipl.-Inform. Tobias Heer, Ph.D. Student
>> Distributed Systems Group
>> RWTH Aachen University, Germany
>> tel: +49 241 80 207 76
>> web: http://ds.cs.rwth-aachen.de/members/heer
>>
>>
>>
>>
>>
>>
>>
>> _______________________________________________
>> Hipsec mailing list
>> Hipsec@ietf.org
>> https://www.ietf.org/mailman/listinfo/hipsec
>>
>>      
>
>
>
> _______________________________________________
> Hipsec mailing list
> Hipsec@ietf.org
> https://www.ietf.org/mailman/listinfo/hipsec
>
>    

From jan.melen@nomadiclab.com  Wed Mar 17 01:43:26 2010
Return-Path: <jan.melen@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 D4E873A6928 for <hipsec@core3.amsl.com>; Wed, 17 Mar 2010 01:43:26 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.469
X-Spam-Level: 
X-Spam-Status: No, score=-1.469 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, DNS_FROM_OPENWHOIS=1.13]
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 97e1FkNsGuHx for <hipsec@core3.amsl.com>; Wed, 17 Mar 2010 01:43:26 -0700 (PDT)
Received: from gw.nomadiclab.com (unknown [IPv6:2001:14b8:400:101::2]) by core3.amsl.com (Postfix) with ESMTP id 600133A6909 for <hipsec@ietf.org>; Wed, 17 Mar 2010 01:43:22 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by gw.nomadiclab.com (Postfix) with ESMTP id 400A84E6CD for <hipsec@ietf.org>; Wed, 17 Mar 2010 10:43:31 +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 E1xI8RwEw4Fh for <hipsec@ietf.org>; Wed, 17 Mar 2010 10:43:30 +0200 (EET)
Received: from smtp.nomadiclab.com (d146.nomadiclab.com [IPv6:2001:14b8:400:100::146]) by gw.nomadiclab.com (Postfix) with ESMTP id 9D4274E6D3 for <hipsec@ietf.org>; Wed, 17 Mar 2010 10:43:30 +0200 (EET)
Received: from smtp.nomadiclab.com (localhost [127.0.0.1]) by smtp.nomadiclab.com (Postfix) with ESMTP id 616F9107194; Wed, 17 Mar 2010 10:43:30 +0200 (EET)
Received: from [IPv6:::1] (n2.nomadiclab.com [IPv6:2001:14b8:400:101::2]) by smtp.nomadiclab.com (Postfix) with ESMTP id 28793106F11; Wed, 17 Mar 2010 10:43:30 +0200 (EET)
Mime-Version: 1.0 (Apple Message framework v1077)
Content-Type: text/plain; charset=us-ascii
From: Jan Melen <jan.melen@nomadiclab.com>
In-Reply-To: <4B9F5B79.1080103@nomadiclab.com>
Date: Wed, 17 Mar 2010 10:43:29 +0200
Content-Transfer-Encoding: quoted-printable
Message-Id: <2F808992-7A4C-4467-BDB1-47D3E9EA0070@nomadiclab.com>
References: <4B9F5B79.1080103@nomadiclab.com>
To: Ari Keranen <ari.keranen@nomadiclab.com>
X-Mailer: Apple Mail (2.1077)
X-Virus-Scanned: ClamAV using ClamSMTP
Cc: HIP <hipsec@ietf.org>
Subject: Re: [Hipsec] Making hip-over-hip draft a WG item
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, 17 Mar 2010 08:43:26 -0000

Hi,

+1, but I would explicitly indicate that re-keying and BEX needs to be =
done outside ESP connections due to unnecessary complexity for selecting =
whether to use old or new SA and on how long one should maintain the =
state from the old SA because of retransmissions.

      Jan


On Mar 16, 2010, at 12:20 PM, Ari Keranen wrote:

> Hi all,
>=20
> The HIP-over-HIP draft specifies how HIP signaling messages can be =
sent over encrypted (ESP) connections. This feature is useful, e.g., in =
some scenarios involving overlays and therefore it would make sense to =
standardize it.
>=20
> http://tools.ietf.org/html/draft-keranen-hip-over-hip-01
>=20
> Would people support this draft to become a WG item?
>=20
>=20
> Cheers,
> Ari
> _______________________________________________
> Hipsec mailing list
> Hipsec@ietf.org
> https://www.ietf.org/mailman/listinfo/hipsec


From jan.melen@nomadiclab.com  Wed Mar 17 01:54:16 2010
Return-Path: <jan.melen@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 2ED483A6849 for <hipsec@core3.amsl.com>; Wed, 17 Mar 2010 01:54:16 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.469
X-Spam-Level: 
X-Spam-Status: No, score=-1.469 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, DNS_FROM_OPENWHOIS=1.13]
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 42gn8OhNGhsA for <hipsec@core3.amsl.com>; Wed, 17 Mar 2010 01:54:15 -0700 (PDT)
Received: from gw.nomadiclab.com (unknown [IPv6:2001:14b8:400:101::2]) by core3.amsl.com (Postfix) with ESMTP id 32B8C3A6928 for <hipsec@ietf.org>; Wed, 17 Mar 2010 01:54:15 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by gw.nomadiclab.com (Postfix) with ESMTP id 62FA24E6D3; Wed, 17 Mar 2010 10:54:24 +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 lEscATJxsnSi; Wed, 17 Mar 2010 10:54:23 +0200 (EET)
Received: from smtp.nomadiclab.com (d146.nomadiclab.com [IPv6:2001:14b8:400:100::146]) by gw.nomadiclab.com (Postfix) with ESMTP id 5C20D4E6CD; Wed, 17 Mar 2010 10:54:23 +0200 (EET)
Received: from smtp.nomadiclab.com (localhost [127.0.0.1]) by smtp.nomadiclab.com (Postfix) with ESMTP id 1F7C2107194; Wed, 17 Mar 2010 10:54:23 +0200 (EET)
Received: from [IPv6:::1] (n2.nomadiclab.com [IPv6:2001:14b8:400:101::2]) by smtp.nomadiclab.com (Postfix) with ESMTP id DC319106F11; Wed, 17 Mar 2010 10:54:22 +0200 (EET)
Mime-Version: 1.0 (Apple Message framework v1077)
Content-Type: text/plain; charset=us-ascii
From: Jan Melen <jan.melen@nomadiclab.com>
In-Reply-To: <1267705771.4b8fa7ab0486b@webmail.hiit.fi>
Date: Wed, 17 Mar 2010 10:54:22 +0200
Content-Transfer-Encoding: quoted-printable
Message-Id: <C5C31D4E-8815-4C00-9D8E-171A5E432766@nomadiclab.com>
References: <1267705771.4b8fa7ab0486b@webmail.hiit.fi>
To: Dmitrij Lagutin <Dmitrij.Lagutin@hiit.fi>
X-Mailer: Apple Mail (2.1077)
X-Virus-Scanned: ClamAV using ClamSMTP
Cc: hipsec@ietf.org
Subject: Re: [Hipsec] About the HICCUPS draft
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, 17 Mar 2010 08:54:16 -0000

Hi,

As I already indicated in a private email discussion I would propose =
that you write a separate draft on PLA and HIP maybe a bis to HICCUPS. =
Current HICCUPS is aiming for support that is required by hip-bone.

Also the proposal of non-ACK delivery could be one thing that is added =
when we have PLA type authentication in the packets.

     Jan=20

On Mar 4, 2010, at 2:29 PM, Dmitrij Lagutin wrote:

> Dear all,
>=20
>=20
> I have been working at Helsinki Institute for Information Technology =
(HIIT)
> with the technology called Packet Level Authentication (PLA). PLA aims =
to
> provide availability and hop-by-hop authentication on the network =
layer through
> cryptographic signatures. The main idea is to give intermediate nodes =
means to
> detect modified, duplicated and delayed packets, these packets can be =
then
> dropped immediately before they even reach the destination.
>=20
> Miika Komu and others suggested me combining principles of PLA with =
HIP since
> they mostly complement each other. The HICCUPS draft seems to be a =
good place
> for that. Some of my ideas are listed below.
>=20
> - Could the possibility of more extensive hop-by-hop verification be =
included in
> the security considerations chapter (7.) of the draft?
>=20
> - A timestamp added to HICCUPS parameters would allow detection of =
significantly
> delayed packets. A global time synchronization mechanism would not be =
absolutely
> necessary.
>=20
> - A separate sequence number added to every HICCUPS packet would allow =
detection
> of duplicated packets (which can be used in replay attacks). In =
contrast to
> SEQ_DATA packet, this sequence number would not be ACKed.
>=20
>=20
> Best regards,
> Dmitrij Lagutin
> Researcher, Helsinki Institute for Information Technology
>=20
> _______________________________________________
> Hipsec mailing list
> Hipsec@ietf.org
> https://www.ietf.org/mailman/listinfo/hipsec


From ari.keranen@nomadiclab.com  Wed Mar 17 02:32:05 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 C9DF03A69E0 for <hipsec@core3.amsl.com>; Wed, 17 Mar 2010 02:32:05 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.034
X-Spam-Level: 
X-Spam-Status: No, score=-2.034 tagged_above=-999 required=5 tests=[AWL=-0.565, BAYES_00=-2.599, DNS_FROM_OPENWHOIS=1.13]
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 GqR+XO3abupM for <hipsec@core3.amsl.com>; Wed, 17 Mar 2010 02:32:05 -0700 (PDT)
Received: from gw.nomadiclab.com (unknown [IPv6:2001:14b8:400:101::2]) by core3.amsl.com (Postfix) with ESMTP id 8E0CF3A690A for <hipsec@ietf.org>; Wed, 17 Mar 2010 02:32:04 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by gw.nomadiclab.com (Postfix) with ESMTP id E25C94E6D3 for <hipsec@ietf.org>; Wed, 17 Mar 2010 11:32:09 +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 VICf+sxkMBDO; Wed, 17 Mar 2010 11:32:09 +0200 (EET)
Received: from [IPv6:2001:14b8:400:101:21c:23ff:fe45:a6c1] (unknown [IPv6:2001:14b8:400:101:21c:23ff:fe45:a6c1]) by gw.nomadiclab.com (Postfix) with ESMTP id 146AE4E6CD; Wed, 17 Mar 2010 11:32:08 +0200 (EET)
Message-ID: <4BA0A198.2080007@nomadiclab.com>
Date: Wed, 17 Mar 2010 11:32:08 +0200
From: Ari Keranen <ari.keranen@nomadiclab.com>
User-Agent: Thunderbird 2.0.0.23 (X11/20090817)
MIME-Version: 1.0
To: Jan Melen <jan.melen@nomadiclab.com>
References: <4B9F5B79.1080103@nomadiclab.com> <2F808992-7A4C-4467-BDB1-47D3E9EA0070@nomadiclab.com>
In-Reply-To: <2F808992-7A4C-4467-BDB1-47D3E9EA0070@nomadiclab.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Cc: HIP <hipsec@ietf.org>
Subject: Re: [Hipsec] Making hip-over-hip draft a WG item
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, 17 Mar 2010 09:32:05 -0000

Hi Jan,

That makes sense; I'll change that in the next version of the draft.


Thanks,
Ari

Jan Melen wrote:
> Hi,
> 
> +1, but I would explicitly indicate that re-keying and BEX needs to
> be done outside ESP connections due to unnecessary complexity for
> selecting whether to use old or new SA and on how long one should
> maintain the state from the old SA because of retransmissions.
> 
> Jan
> 
> 
> On Mar 16, 2010, at 12:20 PM, Ari Keranen wrote:
> 
>> Hi all,
>> 
>> The HIP-over-HIP draft specifies how HIP signaling messages can be
>> sent over encrypted (ESP) connections. This feature is useful,
>> e.g., in some scenarios involving overlays and therefore it would
>> make sense to standardize it.
>> 
>> http://tools.ietf.org/html/draft-keranen-hip-over-hip-01
>> 
>> Would people support this draft to become a WG item?
>> 
>> 
>> Cheers, Ari _______________________________________________ Hipsec
>> mailing list Hipsec@ietf.org 
>> https://www.ietf.org/mailman/listinfo/hipsec
> 


From ari.keranen@nomadiclab.com  Wed Mar 17 04:56:55 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 AA9A93A68B4 for <hipsec@core3.amsl.com>; Wed, 17 Mar 2010 04:56:55 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.978
X-Spam-Level: 
X-Spam-Status: No, score=-1.978 tagged_above=-999 required=5 tests=[AWL=-0.508, BAYES_00=-2.599, DNS_FROM_OPENWHOIS=1.13]
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 b1L2iFvB-9wK for <hipsec@core3.amsl.com>; Wed, 17 Mar 2010 04:56:54 -0700 (PDT)
Received: from gw.nomadiclab.com (unknown [IPv6:2001:14b8:400:101::2]) by core3.amsl.com (Postfix) with ESMTP id 661E73A67FD for <hipsec@ietf.org>; Wed, 17 Mar 2010 04:56:53 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by gw.nomadiclab.com (Postfix) with ESMTP id 209954E6D3; Wed, 17 Mar 2010 13:57:00 +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 4+n25eiTPq11; Wed, 17 Mar 2010 13:56:59 +0200 (EET)
Received: from [IPv6:2001:14b8:400:101:21c:23ff:fe45:a6c1] (unknown [IPv6:2001:14b8:400:101:21c:23ff:fe45:a6c1]) by gw.nomadiclab.com (Postfix) with ESMTP id 90B344E6CD; Wed, 17 Mar 2010 13:56:59 +0200 (EET)
Message-ID: <4BA0C38B.2060107@nomadiclab.com>
Date: Wed, 17 Mar 2010 13:56:59 +0200
From: Ari Keranen <ari.keranen@nomadiclab.com>
User-Agent: Thunderbird 2.0.0.23 (X11/20090817)
MIME-Version: 1.0
To: Dmitrij Lagutin <Dmitrij.Lagutin@hiit.fi>, hipsec@ietf.org
References: <1267705771.4b8fa7ab0486b@webmail.hiit.fi> <C5C31D4E-8815-4C00-9D8E-171A5E432766@nomadiclab.com>
In-Reply-To: <C5C31D4E-8815-4C00-9D8E-171A5E432766@nomadiclab.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Cc: Jan Melen <jan.melen@nomadiclab.com>
Subject: Re: [Hipsec] About the HICCUPS draft
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, 17 Mar 2010 11:56:55 -0000

Hi,

I agree with Jan on this. It would make more sense to have this as an 
independent document rather than having it as an integral part of HICCUPS.

After all, PLA adds a fair amount of complexity (if I understood the 
proposal correctly; looking forward to the RG presentation) but it's not 
really required in many cases. As long as there's nothing in HICCUPS 
that prevents adding PLA features later on, I would not change the 
HICCUPS draft. That said, perhaps the "more extensive hop-by-hop 
verification" comment could be added to the security section.


Cheers,
Ari

Jan Melen wrote:
> Hi,
> 
> As I already indicated in a private email discussion I would propose
> that you write a separate draft on PLA and HIP maybe a bis to
> HICCUPS. Current HICCUPS is aiming for support that is required by
> hip-bone.
> 
> Also the proposal of non-ACK delivery could be one thing that is
> added when we have PLA type authentication in the packets.
> 
> Jan
> 
> On Mar 4, 2010, at 2:29 PM, Dmitrij Lagutin wrote:
> 
>> Dear all,
>> 
>> 
>> I have been working at Helsinki Institute for Information
>> Technology (HIIT) with the technology called Packet Level
>> Authentication (PLA). PLA aims to provide availability and
>> hop-by-hop authentication on the network layer through 
>> cryptographic signatures. The main idea is to give intermediate
>> nodes means to detect modified, duplicated and delayed packets,
>> these packets can be then dropped immediately before they even
>> reach the destination.
>> 
>> Miika Komu and others suggested me combining principles of PLA with
>> HIP since they mostly complement each other. The HICCUPS draft
>> seems to be a good place for that. Some of my ideas are listed
>> below.
>> 
>> - Could the possibility of more extensive hop-by-hop verification
>> be included in the security considerations chapter (7.) of the
>> draft?
>> 
>> - A timestamp added to HICCUPS parameters would allow detection of
>> significantly delayed packets. A global time synchronization
>> mechanism would not be absolutely necessary.
>> 
>> - A separate sequence number added to every HICCUPS packet would
>> allow detection of duplicated packets (which can be used in replay
>> attacks). In contrast to SEQ_DATA packet, this sequence number
>> would not be ACKed.
>> 
>> 
>> Best regards, Dmitrij Lagutin Researcher, Helsinki Institute for
>> Information Technology
>> 
>> _______________________________________________ Hipsec mailing list
>>  Hipsec@ietf.org https://www.ietf.org/mailman/listinfo/hipsec
> 
> _______________________________________________ Hipsec mailing list 
> Hipsec@ietf.org https://www.ietf.org/mailman/listinfo/hipsec


From gao.yang2@zte.com.cn  Wed Mar 17 06:35:01 2010
Return-Path: <gao.yang2@zte.com.cn>
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 AD75B3A692D for <hipsec@core3.amsl.com>; Wed, 17 Mar 2010 06:35:01 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -95.34
X-Spam-Level: 
X-Spam-Status: No, score=-95.34 tagged_above=-999 required=5 tests=[AWL=-3.679, BAYES_00=-2.599, CHARSET_FARAWAY_HEADER=3.2, DNS_FROM_OPENWHOIS=1.13, HTML_MESSAGE=0.001, MIME_8BIT_HEADER=0.3, MIME_BASE64_TEXT=1.753, MIME_CHARSET_FARAWAY=2.45, RCVD_DOUBLE_IP_LOOSE=0.76, SARE_SUB_ENC_GB2312=1.345, 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 wwgh3h2eoA1p for <hipsec@core3.amsl.com>; Wed, 17 Mar 2010 06:35:00 -0700 (PDT)
Received: from mx6.zte.com.cn (mx6.zte.com.cn [63.218.89.70]) by core3.amsl.com (Postfix) with ESMTP id C37D23A6A51 for <hipsec@ietf.org>; Wed, 17 Mar 2010 06:34:48 -0700 (PDT)
Received: from [10.30.17.100] by mx6.zte.com.cn with surfront esmtp id 128642133923422; Wed, 17 Mar 2010 21:33:52 +0800 (CST)
Received: from [192.168.168.1] by [192.168.168.16] with StormMail ESMTP id 84131.3193149038; Wed, 17 Mar 2010 21:32:47 +0800 (CST)
Received: from notes_smtp.zte.com.cn ([10.30.1.239]) by mse2.zte.com.cn with ESMTP id o2HDZ16t073146; Wed, 17 Mar 2010 21:35:02 +0800 (CST) (envelope-from gao.yang2@zte.com.cn)
In-Reply-To: <2F808992-7A4C-4467-BDB1-47D3E9EA0070@nomadiclab.com>
To: Jan Melen <jan.melen@nomadiclab.com>
MIME-Version: 1.0
X-Mailer: Lotus Notes Release 7.0.1 January 17, 2006
Message-ID: <OFA840E57D.AB617BF9-ON482576E9.004A28B7-482576E9.004A8218@zte.com.cn>
From: gao.yang2@zte.com.cn
Date: Wed, 17 Mar 2010 21:33:09 +0800
X-MIMETrack: Serialize by Router on notes_smtp/zte_ltd(Release 6.5.4|March 27, 2005) at 2010-03-17 21:34:46, Serialize complete at 2010-03-17 21:34:46
Content-Type: multipart/alternative; boundary="=_alternative 004A820E482576E9_="
X-MAIL: mse2.zte.com.cn o2HDZ16t073146
Cc: HIP <hipsec@ietf.org>
Subject: [Hipsec] =?gb2312?b?tPC4tDogUmU6ICBNYWtpbmcgaGlwLW92ZXItaGlwIGRy?= =?gb2312?b?YWZ0IGEgV0cgaXRlbQ==?=
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, 17 Mar 2010 13:35:01 -0000

This is a multipart message in MIME format.
--=_alternative 004A820E482576E9_=
Content-Type: text/plain; charset="GB2312"
Content-Transfer-Encoding: base64

KzENCg0KIEFuZCBJIGFsc28gYW50aWNpcGFudGUgc2VlaW5nIEhJUCBkcmFmdHMgYWJvdXQgVGVs
Y29tIHVzYWdlLiANCg0KPT09PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09PT0NCiBaaXAg
ICAgOiAyMTAwMTINCiBUZWwgICAgOiA4NzIxMQ0KIFRlbDIgICA6KCs4NiktMDI1LTUyODc3MjEx
DQogZV9tYWlsIDogZ2FvLnlhbmcyQHp0ZS5jb20uY24NCj09PT09PT09PT09PT09PT09PT09PT09
PT09PT09PT09PT09DQoNCg0KDQpKYW4gTWVsZW4gPGphbi5tZWxlbkBub21hZGljbGFiLmNvbT4g
DQq3orz+yMs6ICBoaXBzZWMtYm91bmNlc0BpZXRmLm9yZw0KMjAxMC0wMy0xNyAxNjo0Mw0KDQrK
1bz+yMsNCkFyaSBLZXJhbmVuIDxhcmkua2VyYW5lbkBub21hZGljbGFiLmNvbT4NCrOty80NCkhJ
UCA8aGlwc2VjQGlldGYub3JnPg0K1vfM4g0KUmU6IFtIaXBzZWNdIE1ha2luZyBoaXAtb3Zlci1o
aXAgZHJhZnQgYSBXRyBpdGVtDQoNCg0KDQoNCg0KDQpIaSwNCg0KKzEsIGJ1dCBJIHdvdWxkIGV4
cGxpY2l0bHkgaW5kaWNhdGUgdGhhdCByZS1rZXlpbmcgYW5kIEJFWCBuZWVkcyB0byBiZSANCmRv
bmUgb3V0c2lkZSBFU1AgY29ubmVjdGlvbnMgZHVlIHRvIHVubmVjZXNzYXJ5IGNvbXBsZXhpdHkg
Zm9yIHNlbGVjdGluZyANCndoZXRoZXIgdG8gdXNlIG9sZCBvciBuZXcgU0EgYW5kIG9uIGhvdyBs
b25nIG9uZSBzaG91bGQgbWFpbnRhaW4gdGhlIHN0YXRlIA0KZnJvbSB0aGUgb2xkIFNBIGJlY2F1
c2Ugb2YgcmV0cmFuc21pc3Npb25zLg0KDQogICAgICBKYW4NCg0KDQpPbiBNYXIgMTYsIDIwMTAs
IGF0IDEyOjIwIFBNLCBBcmkgS2VyYW5lbiB3cm90ZToNCg0KPiBIaSBhbGwsDQo+IA0KPiBUaGUg
SElQLW92ZXItSElQIGRyYWZ0IHNwZWNpZmllcyBob3cgSElQIHNpZ25hbGluZyBtZXNzYWdlcyBj
YW4gYmUgc2VudCANCm92ZXIgZW5jcnlwdGVkIChFU1ApIGNvbm5lY3Rpb25zLiBUaGlzIGZlYXR1
cmUgaXMgdXNlZnVsLCBlLmcuLCBpbiBzb21lIA0Kc2NlbmFyaW9zIGludm9sdmluZyBvdmVybGF5
cyBhbmQgdGhlcmVmb3JlIGl0IHdvdWxkIG1ha2Ugc2Vuc2UgdG8gDQpzdGFuZGFyZGl6ZSBpdC4N
Cj4gDQo+IGh0dHA6Ly90b29scy5pZXRmLm9yZy9odG1sL2RyYWZ0LWtlcmFuZW4taGlwLW92ZXIt
aGlwLTAxDQo+IA0KPiBXb3VsZCBwZW9wbGUgc3VwcG9ydCB0aGlzIGRyYWZ0IHRvIGJlY29tZSBh
IFdHIGl0ZW0/DQo+IA0KPiANCj4gQ2hlZXJzLA0KPiBBcmkNCj4gX19fX19fX19fX19fX19fX19f
X19fX19fX19fX19fX19fX19fX19fX19fX19fX18NCj4gSGlwc2VjIG1haWxpbmcgbGlzdA0KPiBI
aXBzZWNAaWV0Zi5vcmcNCj4gaHR0cHM6Ly93d3cuaWV0Zi5vcmcvbWFpbG1hbi9saXN0aW5mby9o
aXBzZWMNCg0KX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX18N
CkhpcHNlYyBtYWlsaW5nIGxpc3QNCkhpcHNlY0BpZXRmLm9yZw0KaHR0cHM6Ly93d3cuaWV0Zi5v
cmcvbWFpbG1hbi9saXN0aW5mby9oaXBzZWMNCg0KDQoNCg0KDQotLS0tLS0tLS0tLS0tLS0tLS0t
LS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLQ0KWlRFIEluZm9ybWF0aW9uIFNl
Y3VyaXR5IE5vdGljZTogVGhlIGluZm9ybWF0aW9uIGNvbnRhaW5lZCBpbiB0aGlzIG1haWwgaXMg
c29sZWx5IHByb3BlcnR5IG9mIHRoZSBzZW5kZXIncyBvcmdhbml6YXRpb24uIFRoaXMgbWFpbCBj
b21tdW5pY2F0aW9uIGlzIGNvbmZpZGVudGlhbC4gUmVjaXBpZW50cyBuYW1lZCBhYm92ZSBhcmUg
b2JsaWdhdGVkIHRvIG1haW50YWluIHNlY3JlY3kgYW5kIGFyZSBub3QgcGVybWl0dGVkIHRvIGRp
c2Nsb3NlIHRoZSBjb250ZW50cyBvZiB0aGlzIGNvbW11bmljYXRpb24gdG8gb3RoZXJzLg0KVGhp
cyBlbWFpbCBhbmQgYW55IGZpbGVzIHRyYW5zbWl0dGVkIHdpdGggaXQgYXJlIGNvbmZpZGVudGlh
bCBhbmQgaW50ZW5kZWQgc29sZWx5IGZvciB0aGUgdXNlIG9mIHRoZSBpbmRpdmlkdWFsIG9yIGVu
dGl0eSB0byB3aG9tIHRoZXkgYXJlIGFkZHJlc3NlZC4gSWYgeW91IGhhdmUgcmVjZWl2ZWQgdGhp
cyBlbWFpbCBpbiBlcnJvciBwbGVhc2Ugbm90aWZ5IHRoZSBvcmlnaW5hdG9yIG9mIHRoZSBtZXNz
YWdlLiBBbnkgdmlld3MgZXhwcmVzc2VkIGluIHRoaXMgbWVzc2FnZSBhcmUgdGhvc2Ugb2YgdGhl
IGluZGl2aWR1YWwgc2VuZGVyLg0KVGhpcyBtZXNzYWdlIGhhcyBiZWVuIHNjYW5uZWQgZm9yIHZp
cnVzZXMgYW5kIFNwYW0gYnkgWlRFIEFudGktU3BhbSBzeXN0ZW0uDQo=
--=_alternative 004A820E482576E9_=
Content-Type: text/html; charset="GB2312"
Content-Transfer-Encoding: base64

DQo8YnI+PGZvbnQgc2l6ZT0yIGZhY2U9InNhbnMtc2VyaWYiPisxPC9mb250Pg0KPGJyPg0KPGJy
Pjxmb250IHNpemU9MiBmYWNlPSJzYW5zLXNlcmlmIj4mbmJzcDtBbmQgSSBhbHNvIGFudGljaXBh
bnRlIHNlZWluZw0KSElQIGRyYWZ0cyBhYm91dCBUZWxjb20gdXNhZ2UuIDwvZm9udD4NCjxicj4N
Cjxicj48Zm9udCBzaXplPTIgZmFjZT0ic2Fucy1zZXJpZiI+PT09PT09PT09PT09PT09PT09PT09
PT09PT09PT09PT09PT08YnI+DQogWmlwICZuYnNwOyAmbmJzcDs6IDIxMDAxMjxicj4NCiBUZWwg
Jm5ic3A7ICZuYnNwOzogODcyMTE8YnI+DQogVGVsMiAmbmJzcDsgOigrODYpLTAyNS01Mjg3NzIx
MTxicj4NCiBlX21haWwgOiBnYW8ueWFuZzJAenRlLmNvbS5jbjxicj4NCj09PT09PT09PT09PT09
PT09PT09PT09PT09PT09PT09PT09PC9mb250Pg0KPGJyPg0KPGJyPg0KPGJyPg0KPHRhYmxlIHdp
ZHRoPTEwMCU+DQo8dHIgdmFsaWduPXRvcD4NCjx0ZCB3aWR0aD0yNiU+PGZvbnQgc2l6ZT0xIGZh
Y2U9InNhbnMtc2VyaWYiPjxiPkphbiBNZWxlbiAmbHQ7amFuLm1lbGVuQG5vbWFkaWNsYWIuY29t
Jmd0OzwvYj4NCjwvZm9udD4NCjxicj48Zm9udCBzaXplPTEgZmFjZT0ic2Fucy1zZXJpZiI+t6K8
/sjLOiAmbmJzcDtoaXBzZWMtYm91bmNlc0BpZXRmLm9yZzwvZm9udD4NCjxwPjxmb250IHNpemU9
MSBmYWNlPSJzYW5zLXNlcmlmIj4yMDEwLTAzLTE3IDE2OjQzPC9mb250Pg0KPHRkIHdpZHRoPTcz
JT4NCjx0YWJsZSB3aWR0aD0xMDAlPg0KPHRyIHZhbGlnbj10b3A+DQo8dGQ+DQo8ZGl2IGFsaWdu
PXJpZ2h0Pjxmb250IHNpemU9MSBmYWNlPSJzYW5zLXNlcmlmIj7K1bz+yMs8L2ZvbnQ+PC9kaXY+
DQo8dGQ+PGZvbnQgc2l6ZT0xIGZhY2U9InNhbnMtc2VyaWYiPkFyaSBLZXJhbmVuICZsdDthcmku
a2VyYW5lbkBub21hZGljbGFiLmNvbSZndDs8L2ZvbnQ+DQo8dHIgdmFsaWduPXRvcD4NCjx0ZD4N
CjxkaXYgYWxpZ249cmlnaHQ+PGZvbnQgc2l6ZT0xIGZhY2U9InNhbnMtc2VyaWYiPrOty808L2Zv
bnQ+PC9kaXY+DQo8dGQ+PGZvbnQgc2l6ZT0xIGZhY2U9InNhbnMtc2VyaWYiPkhJUCAmbHQ7aGlw
c2VjQGlldGYub3JnJmd0OzwvZm9udD4NCjx0ciB2YWxpZ249dG9wPg0KPHRkPg0KPGRpdiBhbGln
bj1yaWdodD48Zm9udCBzaXplPTEgZmFjZT0ic2Fucy1zZXJpZiI+1vfM4jwvZm9udD48L2Rpdj4N
Cjx0ZD48Zm9udCBzaXplPTEgZmFjZT0ic2Fucy1zZXJpZiI+UmU6IFtIaXBzZWNdIE1ha2luZyBo
aXAtb3Zlci1oaXAgZHJhZnQNCmEgV0cgaXRlbTwvZm9udD48L3RhYmxlPg0KPGJyPg0KPHRhYmxl
Pg0KPHRyIHZhbGlnbj10b3A+DQo8dGQ+DQo8dGQ+PC90YWJsZT4NCjxicj48L3RhYmxlPg0KPGJy
Pg0KPGJyPg0KPGJyPjx0dD48Zm9udCBzaXplPTI+SGksPGJyPg0KPGJyPg0KKzEsIGJ1dCBJIHdv
dWxkIGV4cGxpY2l0bHkgaW5kaWNhdGUgdGhhdCByZS1rZXlpbmcgYW5kIEJFWCBuZWVkcyB0byBi
ZQ0KZG9uZSBvdXRzaWRlIEVTUCBjb25uZWN0aW9ucyBkdWUgdG8gdW5uZWNlc3NhcnkgY29tcGxl
eGl0eSBmb3Igc2VsZWN0aW5nDQp3aGV0aGVyIHRvIHVzZSBvbGQgb3IgbmV3IFNBIGFuZCBvbiBo
b3cgbG9uZyBvbmUgc2hvdWxkIG1haW50YWluIHRoZSBzdGF0ZQ0KZnJvbSB0aGUgb2xkIFNBIGJl
Y2F1c2Ugb2YgcmV0cmFuc21pc3Npb25zLjxicj4NCjxicj4NCiAmbmJzcDsgJm5ic3A7ICZuYnNw
O0phbjxicj4NCjxicj4NCjxicj4NCk9uIE1hciAxNiwgMjAxMCwgYXQgMTI6MjAgUE0sIEFyaSBL
ZXJhbmVuIHdyb3RlOjxicj4NCjxicj4NCiZndDsgSGkgYWxsLDxicj4NCiZndDsgPGJyPg0KJmd0
OyBUaGUgSElQLW92ZXItSElQIGRyYWZ0IHNwZWNpZmllcyBob3cgSElQIHNpZ25hbGluZyBtZXNz
YWdlcyBjYW4gYmUNCnNlbnQgb3ZlciBlbmNyeXB0ZWQgKEVTUCkgY29ubmVjdGlvbnMuIFRoaXMg
ZmVhdHVyZSBpcyB1c2VmdWwsIGUuZy4sIGluDQpzb21lIHNjZW5hcmlvcyBpbnZvbHZpbmcgb3Zl
cmxheXMgYW5kIHRoZXJlZm9yZSBpdCB3b3VsZCBtYWtlIHNlbnNlIHRvDQpzdGFuZGFyZGl6ZSBp
dC48YnI+DQomZ3Q7IDxicj4NCiZndDsgaHR0cDovL3Rvb2xzLmlldGYub3JnL2h0bWwvZHJhZnQt
a2VyYW5lbi1oaXAtb3Zlci1oaXAtMDE8YnI+DQomZ3Q7IDxicj4NCiZndDsgV291bGQgcGVvcGxl
IHN1cHBvcnQgdGhpcyBkcmFmdCB0byBiZWNvbWUgYSBXRyBpdGVtPzxicj4NCiZndDsgPGJyPg0K
Jmd0OyA8YnI+DQomZ3Q7IENoZWVycyw8YnI+DQomZ3Q7IEFyaTxicj4NCiZndDsgX19fX19fX19f
X19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX188YnI+DQomZ3Q7IEhpcHNlYyBt
YWlsaW5nIGxpc3Q8YnI+DQomZ3Q7IEhpcHNlY0BpZXRmLm9yZzxicj4NCiZndDsgaHR0cHM6Ly93
d3cuaWV0Zi5vcmcvbWFpbG1hbi9saXN0aW5mby9oaXBzZWM8YnI+DQo8YnI+DQpfX19fX19fX19f
X19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fXzxicj4NCkhpcHNlYyBtYWlsaW5n
IGxpc3Q8YnI+DQpIaXBzZWNAaWV0Zi5vcmc8YnI+DQpodHRwczovL3d3dy5pZXRmLm9yZy9tYWls
bWFuL2xpc3RpbmZvL2hpcHNlYzxicj4NCjxicj4NCjwvZm9udD48L3R0Pg0KPGJyPg0KPGJyPjxw
cmU+DQotLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0t
LS0tLQ0KWlRFJm5ic3A7SW5mb3JtYXRpb24mbmJzcDtTZWN1cml0eSZuYnNwO05vdGljZTombmJz
cDtUaGUmbmJzcDtpbmZvcm1hdGlvbiZuYnNwO2NvbnRhaW5lZCZuYnNwO2luJm5ic3A7dGhpcyZu
YnNwO21haWwmbmJzcDtpcyZuYnNwO3NvbGVseSZuYnNwO3Byb3BlcnR5Jm5ic3A7b2YmbmJzcDt0
aGUmbmJzcDtzZW5kZXIncyZuYnNwO29yZ2FuaXphdGlvbi4mbmJzcDtUaGlzJm5ic3A7bWFpbCZu
YnNwO2NvbW11bmljYXRpb24mbmJzcDtpcyZuYnNwO2NvbmZpZGVudGlhbC4mbmJzcDtSZWNpcGll
bnRzJm5ic3A7bmFtZWQmbmJzcDthYm92ZSZuYnNwO2FyZSZuYnNwO29ibGlnYXRlZCZuYnNwO3Rv
Jm5ic3A7bWFpbnRhaW4mbmJzcDtzZWNyZWN5Jm5ic3A7YW5kJm5ic3A7YXJlJm5ic3A7bm90Jm5i
c3A7cGVybWl0dGVkJm5ic3A7dG8mbmJzcDtkaXNjbG9zZSZuYnNwO3RoZSZuYnNwO2NvbnRlbnRz
Jm5ic3A7b2YmbmJzcDt0aGlzJm5ic3A7Y29tbXVuaWNhdGlvbiZuYnNwO3RvJm5ic3A7b3RoZXJz
Lg0KVGhpcyZuYnNwO2VtYWlsJm5ic3A7YW5kJm5ic3A7YW55Jm5ic3A7ZmlsZXMmbmJzcDt0cmFu
c21pdHRlZCZuYnNwO3dpdGgmbmJzcDtpdCZuYnNwO2FyZSZuYnNwO2NvbmZpZGVudGlhbCZuYnNw
O2FuZCZuYnNwO2ludGVuZGVkJm5ic3A7c29sZWx5Jm5ic3A7Zm9yJm5ic3A7dGhlJm5ic3A7dXNl
Jm5ic3A7b2YmbmJzcDt0aGUmbmJzcDtpbmRpdmlkdWFsJm5ic3A7b3ImbmJzcDtlbnRpdHkmbmJz
cDt0byZuYnNwO3dob20mbmJzcDt0aGV5Jm5ic3A7YXJlJm5ic3A7YWRkcmVzc2VkLiZuYnNwO0lm
Jm5ic3A7eW91Jm5ic3A7aGF2ZSZuYnNwO3JlY2VpdmVkJm5ic3A7dGhpcyZuYnNwO2VtYWlsJm5i
c3A7aW4mbmJzcDtlcnJvciZuYnNwO3BsZWFzZSZuYnNwO25vdGlmeSZuYnNwO3RoZSZuYnNwO29y
aWdpbmF0b3ImbmJzcDtvZiZuYnNwO3RoZSZuYnNwO21lc3NhZ2UuJm5ic3A7QW55Jm5ic3A7dmll
d3MmbmJzcDtleHByZXNzZWQmbmJzcDtpbiZuYnNwO3RoaXMmbmJzcDttZXNzYWdlJm5ic3A7YXJl
Jm5ic3A7dGhvc2UmbmJzcDtvZiZuYnNwO3RoZSZuYnNwO2luZGl2aWR1YWwmbmJzcDtzZW5kZXIu
DQpUaGlzJm5ic3A7bWVzc2FnZSZuYnNwO2hhcyZuYnNwO2JlZW4mbmJzcDtzY2FubmVkJm5ic3A7
Zm9yJm5ic3A7dmlydXNlcyZuYnNwO2FuZCZuYnNwO1NwYW0mbmJzcDtieSZuYnNwO1pURSZuYnNw
O0FudGktU3BhbSZuYnNwO3N5c3RlbS4NCjwvcHJlPg==
--=_alternative 004A820E482576E9_=--


From dmitriy.kuptsov@hiit.fi  Thu Mar 18 03:06:19 2010
Return-Path: <dmitriy.kuptsov@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 417CD3A6B5D for <hipsec@core3.amsl.com>; Thu, 18 Mar 2010 03:06:19 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 3.285
X-Spam-Level: ***
X-Spam-Status: No, score=3.285 tagged_above=-999 required=5 tests=[BAYES_50=0.001, DNS_FROM_OPENWHOIS=1.13, FRT_BELOW2=2.154]
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 s8JLxMSlOqKm for <hipsec@core3.amsl.com>; Thu, 18 Mar 2010 03:06:18 -0700 (PDT)
Received: from argo.otaverkko.fi (argo.otaverkko.fi [212.68.0.2]) by core3.amsl.com (Postfix) with ESMTP id 0F9153A6849 for <hipsec@ietf.org>; Thu, 18 Mar 2010 03:06:18 -0700 (PDT)
Received: from [193.167.187.116] (ip116.infrahip.net [193.167.187.116]) by argo.otaverkko.fi (Postfix) with ESMTP id B949225ED10; Thu, 18 Mar 2010 12:06:28 +0200 (EET)
From: Dmitriy Kuptsov <dmitriy.kuptsov@hiit.fi>
To: Tobias Heer <heer@cs.rwth-aachen.de>
In-Reply-To: <C203E2BC-250E-49C3-8983-EE68E75F5D31@cs.rwth-aachen.de>
References: <1268332644.4b993864212f8@webmail.otaverkko.fi> <C203E2BC-250E-49C3-8983-EE68E75F5D31@cs.rwth-aachen.de>
Content-Type: text/plain; charset="UTF-8"
Organization: HIIT, TKK
Date: Thu, 18 Mar 2010 12:06:19 +0200
Message-ID: <1268906779.4208.87.camel@dmitriy-desktop.hiit.fi>
Mime-Version: 1.0
X-Mailer: Evolution 2.28.1 
Content-Transfer-Encoding: 7bit
Cc: hipsec@ietf.org
Subject: Re: [Hipsec] replacing DH in HIP
X-BeenThere: hipsec@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
Reply-To: dmitriy.kuptsov@hiit.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: Thu, 18 Mar 2010 10:06:19 -0000

Hi Tobias,

On Tue, 2010-03-16 at 12:31 +0100, Tobias Heer wrote:
> 
> Don't get me wrong: the reason I am asking is not to oppose your approach. I just want to understand it better. In general I appreciate all efforts of speeding up HIP and of extending its scope.
> 

I apologies for being somewhat awkward. 

So the whole process of "optimized" secret key negotiation for
lightweight sensors can look as follows:

1. Each node (similar as what it is in current HIP) have they
public-private key pair (this can be a self-generated or generated and
signed by TTP -  a network operator, depending whether the network
should be an open or closed group). I am not sure whether HITs should
play some other role other than identifiers (in a context of sensor
network), but lets not concentrate on this right now.

2. The goal is for any given 2 nodes (no matter whether they are just 1
hop or several hops away) in the network to establish (or update) a
secret session key in more "lightweight" manner as compared to DH which
is used currently in HIP.

3. To do so, the initiator sends an I1 packet containing common HIP
header, as well as it also sends its public key (corresponding to its
HIT) in a form of HostID parameter. 

4. The responder constructs R1 packet containing the following
parameters (of course common HIP header is still present):
	(i) New parameter that carries some secret, call it ENC(S), where S can
be anything some function, random string, etc., that later will allow
both initiator and responder to agree on some common secret (of way is
to use bivariate polynomials, see bellow the explanation how those can
be used to derive a common secret). The ENC parameter is encrypted using
initiators public key (I assume that encryption is more efficient than
DH or ECDH computation)
	(ii) Responder's HostID
	(iii) Signature that covers the entire HIP packet.


5. Once the initiator receives R1 packet proceeds with normal steps,
such as signature verification, etc. It then decrypts the ENC parameter
with is private key and obtains S. Using S initiator computes a secret
key. Once this is done the initiator constructs I2 packet with the
following parameters:
	(i) The ENC parameter which carries let say S', which will allow the
responder to derive the same secret key. This parameter is encrypted
using responder public key.
	(ii) HMAC parameter as usual 
	(iii) Signature parameter as usual (I am not sure whether HMAC is
sufficient and we can omit using signatures in I2 and R2 packets for
wireless sensor networks)


6. Responder upon receiving I2 decrypts ENC parameter (i) computes the
session key and (ii) verifies HMAC. It then construct an R2 packet with
follwing parameters:
	(i) HMAC 
	(ii) Signature (may HMAC is sufficient and signature parameter can be
omitted in sensor networks?)


Session key deviation function (using bivariate polynomials) can look as
following:

1. Responder randomly selects coefficients {a0, a1, ..., at} and point x
for a bivariate polynomial of form:

F(x, y) = a0*b0 + a1*b1*x*y + ... + at*bt*x^t*y^t 

(Note that this happens when I1 is received)

2. Initiator uses the F(x, y) (found in R1 message) and randomly selects
coefficients {b0, b1, ..., bt} and point y. The initiator now can 
evaluate F(x, y) and get common secret. It then sends back to responder
the evaluated at point y and using coefficients {b0, b1, ..., bt}
polynomial F(x, y).

3. Responder now can also evaluate F(x, y) (knowing both coefficients
{a0, a1, ..., at}, {b0, b1, ..., bt}, x and y points) and get the same
session key as initiator.



Kind regards,
Dmitriy Kuptsov

  
	   


From ari.keranen@nomadiclab.com  Wed Mar 24 15:48:27 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 CECCD3A6DD1 for <hipsec@core3.amsl.com>; Wed, 24 Mar 2010 15:48:27 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.02
X-Spam-Level: 
X-Spam-Status: No, score=0.02 tagged_above=-999 required=5 tests=[BAYES_05=-1.11, DNS_FROM_OPENWHOIS=1.13]
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 epy5LePOLF7N for <hipsec@core3.amsl.com>; Wed, 24 Mar 2010 15:48:27 -0700 (PDT)
Received: from gw.nomadiclab.com (unknown [IPv6:2001:14b8:400:101::2]) by core3.amsl.com (Postfix) with ESMTP id C114E3A6DD0 for <hipsec@ietf.org>; Wed, 24 Mar 2010 15:48:26 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by gw.nomadiclab.com (Postfix) with ESMTP id 792404E6DD; Thu, 25 Mar 2010 00:48:46 +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 M6f7MLh8CH0f; Thu, 25 Mar 2010 00:48:45 +0200 (EET)
Received: from [127.0.0.1] (localhost [IPv6:::1]) by gw.nomadiclab.com (Postfix) with ESMTPSA id 5689E4E6C5; Thu, 25 Mar 2010 00:48:44 +0200 (EET)
Message-ID: <4BAA96C5.5080404@nomadiclab.com>
Date: Wed, 24 Mar 2010 15:48:37 -0700
From: Ari Keranen <ari.keranen@nomadiclab.com>
User-Agent: Thunderbird 2.0.0.24 (Windows/20100228)
MIME-Version: 1.0
To: HIP <hipsec@ietf.org>
References: <4B9644D2.9080008@nomadiclab.com> <4B9BB5FD.7010401@ericsson.com>
In-Reply-To: <4B9BB5FD.7010401@ericsson.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Subject: Re: [Hipsec] Updated HIP overlay drafts
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, 24 Mar 2010 22:48:27 -0000

Hi all,

After talking with Tom off-line we agreed that it would be good to add 
some text in the HIP BONE draft on what to do if one does not explicitly 
specify to which overlay a HIP message should be sent to (i.e., one 
should be able to configure a "default overlay"). I'll fix this in the 
next version along with other WGLC comments.


Cheers,
Ari

Gonzalo Camarillo wrote:
> Folks,
> 
> the authors of the overlay drafts have revised them in order to address
> the comments received during their WGLC. Please, have a look at the new
> revisions so that we can request their publication. We will wait for
> comments until the HIP WG meeting in Anaheim.
> 
> Cheers,
> 
> Gonzalo
> HIP co-chair
> 
> On 09/03/2010 2:53 PM, Ari Keranen wrote:
>> Hi all,
>>
>> We submitted updated versions of the HIP BONE and VIA drafts:
>> http://www.ietf.org/internet-drafts/draft-ietf-hip-bone-05.txt
>> http://www.ietf.org/internet-drafts/draft-ietf-hip-via-01.txt
>>
>> They address the comments that were given during the WGLC:
>> - HIP BONE was restructured and a framework overview section was added
>> - HIP BONE now includes terminology part with the common terms used in 
>> that context
>> - OVERLAY_TTL parameter type was changed to critical so that it can be 
>> used as a generic forwarding loop breaker
>> - Instead of "Peer ID", HIP BONE uses the more generic term "Node ID"
>> - HIP VIA supports now loose source routing mode where a hop in the 
>> destination list may be skipped
>> - Some clarifications were added to HIP VIA regarding the definitions 
>> and use of the parameters
>>
>> Also the RELOAD instance spec was updated:
>> http://www.ietf.org/internet-drafts/draft-ietf-hip-reload-instance-01.txt
>>
>> That version contains fixes for the comments, other clarifications, and 
>> also changes due to new version of the RELOAD draft (AttachLite was 
>> removed).
>>
>>
>> Cheers,
>> Ari
>> _______________________________________________
>> Hipsec mailing list
>> Hipsec@ietf.org
>> https://www.ietf.org/mailman/listinfo/hipsec
>>
> 


From julienl@qualcomm.com  Tue Mar 30 14:28:20 2010
Return-Path: <julienl@qualcomm.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 454C93A6B31 for <hipsec@core3.amsl.com>; Tue, 30 Mar 2010 14:28:20 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -103.61
X-Spam-Level: 
X-Spam-Status: No, score=-103.61 tagged_above=-999 required=5 tests=[BAYES_20=-0.74, DNS_FROM_OPENWHOIS=1.13, RCVD_IN_DNSWL_MED=-4, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id SyyBFcv4BRxD for <hipsec@core3.amsl.com>; Tue, 30 Mar 2010 14:28:18 -0700 (PDT)
Received: from wolverine01.qualcomm.com (wolverine01.qualcomm.com [199.106.114.254]) by core3.amsl.com (Postfix) with ESMTP id 573F83A6B33 for <hipsec@ietf.org>; Tue, 30 Mar 2010 14:28:18 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=qualcomm.com; i=julienl@qualcomm.com; q=dns/txt; s=qcdkim; t=1269984528; x=1301520528; h=from:to:cc:date:subject:thread-topic:thread-index: message-id:accept-language:content-language: x-ms-has-attach:x-ms-tnef-correlator:acceptlanguage: content-type:content-transfer-encoding:mime-version: x-ironport-av; z=From:=20"Laganier,=20Julien"=20<julienl@qualcomm.com> |To:=20"hipsec@ietf.org"=20<hipsec@ietf.org>|CC:=20"pekka .nikander@ericsson.com"=20<pekka.nikander@ericsson.com> |Date:=20Tue,=2030=20Mar=202010=2014:28:45=20-0700 |Subject:=20Follow-up=20on=204843bis=20/=20ORCHIDv2 |Thread-Topic:=20Follow-up=20on=204843bis=20/=20ORCHIDv2 |Thread-Index:=20AcrQT/qO3jjqs/ioTmKbD87b6FgxKQ=3D=3D |Message-ID:=20<BF345F63074F8040B58C00A186FCA57F1C6AA56C5 7@NALASEXMB04.na.qualcomm.com>|Accept-Language:=20en-US |Content-Language:=20en-US|X-MS-Has-Attach: |X-MS-TNEF-Correlator:|acceptlanguage:=20en-US |Content-Type:=20text/plain=3B=20charset=3D"us-ascii" |Content-Transfer-Encoding:=20quoted-printable |MIME-Version:=201.0|X-IronPort-AV:=20E=3DMcAfee=3Bi=3D"5 400,1158,5936"=3B=20a=3D"37631640"; bh=qx1MkNg/wJuHBkaWDfscc5jqBr9ScXNL4/ynUcHexcs=; b=LXQdsNdx3s9go0gunPIFDKxMQF/7JDJnxDtkkgXsizzjEmSWu5adTh1e z1hDOvTHAijGWA+4N9hXDTOAS+yqurWYrBpR7R98D5tcLpLiQxTH1zjWi czH1FUnYYwv89ZhUIpJc2BpJZuPCRe5ddLkLQL+ijs4kiO3HC9IKcJ7wN 4=;
X-IronPort-AV: E=McAfee;i="5400,1158,5936"; a="37631640"
Received: from ironmsg01-r.qualcomm.com ([172.30.46.15]) by wolverine01.qualcomm.com with ESMTP; 30 Mar 2010 14:28:48 -0700
Received: from nasanexhub02.na.qualcomm.com ([10.46.143.120]) by ironmsg01-r.qualcomm.com with ESMTP/TLS/RC4-MD5; 30 Mar 2010 14:28:48 -0700
Received: from nalasexhc03.na.qualcomm.com (10.47.129.194) by nasanexhub02.na.qualcomm.com (10.46.143.120) with Microsoft SMTP Server (TLS) id 8.2.234.1; Tue, 30 Mar 2010 14:28:47 -0700
Received: from NALASEXMB04.na.qualcomm.com ([10.47.7.114]) by nalasexhc03.na.qualcomm.com ([10.47.129.194]) with mapi; Tue, 30 Mar 2010 14:28:47 -0700
From: "Laganier, Julien" <julienl@qualcomm.com>
To: "hipsec@ietf.org" <hipsec@ietf.org>
Date: Tue, 30 Mar 2010 14:28:45 -0700
Thread-Topic: Follow-up on 4843bis / ORCHIDv2
Thread-Index: AcrQT/qO3jjqs/ioTmKbD87b6FgxKQ==
Message-ID: <BF345F63074F8040B58C00A186FCA57F1C6AA56C57@NALASEXMB04.na.qualcomm.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: en-US
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Cc: "pekka.nikander@ericsson.com" <pekka.nikander@ericsson.com>
Subject: [Hipsec] Follow-up on 4843bis / ORCHIDv2
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, 30 Mar 2010 21:28:20 -0000

Folks,

As proposed at last IETF meeting, it seems we have a way forward with 4843b=
is:

1. HIP WG to have a 4843bis deliverable that introduces crypto-agility
   - Request permanent allocation of a new /28 prefix for ORCHIDv2
   - Introduces ORCHIDv2 Generation Algorithm (OGA), defined in a given Con=
text=20
	 - (e.g. HIP in RFC5201 bis)
   - Define new ORCHIv2 Generation Procedure:
        Input :=3D any bitstring=20
        ORCHID Input :=3D Context ID | Input=20
        ORCHID Ouput :=3D OGA( ORCHID Input )=20
        ORCHID :=3D Prefix | OGA Type | Encode_96( ORCHID Ouput)

=3D> question mark: Do we let the current 2001:10::/28 allocation expire? I=
 recommend we do as it will make it easier to obtain a permanent allocation=
.

2. HIP WG to allocate OGA Type 1 as SHA1 in 5201bis and keep other values a=
s unallocated, allocation requiring IETF specification.

=3D> question mark: Do we start with SHA-256 instead?

--julien

From thomas.r.henderson@boeing.com  Tue Mar 30 14:36:06 2010
Return-Path: <thomas.r.henderson@boeing.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 24AA63A690C for <hipsec@core3.amsl.com>; Tue, 30 Mar 2010 14:36:06 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -5.469
X-Spam-Level: 
X-Spam-Status: No, score=-5.469 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, DNS_FROM_OPENWHOIS=1.13, 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 ZBq0q7GPiRRc for <hipsec@core3.amsl.com>; Tue, 30 Mar 2010 14:36:05 -0700 (PDT)
Received: from blv-smtpout-01.boeing.com (blv-smtpout-01.boeing.com [130.76.32.69]) by core3.amsl.com (Postfix) with ESMTP id 8358F3A6B62 for <hipsec@ietf.org>; Tue, 30 Mar 2010 14:36:01 -0700 (PDT)
Received: from stl-av-01.boeing.com (stl-av-01.boeing.com [192.76.190.6]) by blv-smtpout-01.ns.cs.boeing.com (8.14.4/8.14.4/8.14.4/SMTPOUT) with ESMTP id o2ULaJgj013444 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=FAIL); Tue, 30 Mar 2010 14:36:20 -0700 (PDT)
Received: from stl-av-01.boeing.com (localhost [127.0.0.1]) by stl-av-01.boeing.com (8.14.4/8.14.4/DOWNSTREAM_RELAY) with ESMTP id o2ULaJmn010571; Tue, 30 Mar 2010 16:36:19 -0500 (CDT)
Received: from XCH-NWHT-10.nw.nos.boeing.com (xch-nwht-10.nw.nos.boeing.com [130.247.25.113]) by stl-av-01.boeing.com (8.14.4/8.14.4/UPSTREAM_RELAY) with ESMTP id o2ULaJsN010556 (version=TLSv1/SSLv3 cipher=RC4-MD5 bits=128 verify=OK); Tue, 30 Mar 2010 16:36:19 -0500 (CDT)
Received: from XCH-NW-10V.nw.nos.boeing.com ([130.247.25.85]) by XCH-NWHT-10.nw.nos.boeing.com ([130.247.25.113]) with mapi; Tue, 30 Mar 2010 14:36:19 -0700
From: "Henderson, Thomas R" <thomas.r.henderson@boeing.com>
To: "'Laganier, Julien'" <julienl@qualcomm.com>, "hipsec@ietf.org" <hipsec@ietf.org>
Date: Tue, 30 Mar 2010 14:36:17 -0700
Thread-Topic: Follow-up on 4843bis / ORCHIDv2
Thread-Index: AcrQT/qO3jjqs/ioTmKbD87b6FgxKQAAHgkQ
Message-ID: <7CC566635CFE364D87DC5803D4712A6C4CE8C2719F@XCH-NW-10V.nw.nos.boeing.com>
References: <BF345F63074F8040B58C00A186FCA57F1C6AA56C57@NALASEXMB04.na.qualcomm.com>
In-Reply-To: <BF345F63074F8040B58C00A186FCA57F1C6AA56C57@NALASEXMB04.na.qualcomm.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: en-US
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Cc: "pekka.nikander@ericsson.com" <pekka.nikander@ericsson.com>
Subject: Re: [Hipsec] Follow-up on 4843bis / ORCHIDv2
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, 30 Mar 2010 21:36:06 -0000

> -----Original Message-----
> From: hipsec-bounces@ietf.org
> [mailto:hipsec-bounces@ietf.org] On Behalf Of Laganier, Julien
> Sent: Tuesday, March 30, 2010 2:29 PM
> To: hipsec@ietf.org
> Cc: pekka.nikander@ericsson.com
> Subject: [Hipsec] Follow-up on 4843bis / ORCHIDv2
>
> Folks,
>
> As proposed at last IETF meeting, it seems we have a way
> forward with 4843bis:
>
> 1. HIP WG to have a 4843bis deliverable that introduces crypto-agility
>    - Request permanent allocation of a new /28 prefix for ORCHIDv2
>    - Introduces ORCHIDv2 Generation Algorithm (OGA), defined
> in a given Context
>        - (e.g. HIP in RFC5201 bis)
>    - Define new ORCHIv2 Generation Procedure:
>         Input :=3D any bitstring
>         ORCHID Input :=3D Context ID | Input
>         ORCHID Ouput :=3D OGA( ORCHID Input )
>         ORCHID :=3D Prefix | OGA Type | Encode_96( ORCHID Ouput)
>
> =3D> question mark: Do we let the current 2001:10::/28
> allocation expire? I recommend we do as it will make it
> easier to obtain a permanent allocation.

+1

>
> 2. HIP WG to allocate OGA Type 1 as SHA1 in 5201bis and keep
> other values as unallocated, allocation requiring IETF specification.
>
> =3D> question mark: Do we start with SHA-256 instead?

I would be happy to delegate the question to the crypto forum or other expe=
rts, but my impression is that SHA-1 is already being phased out elsewhere =
and that existing libraries typically have SHA-256 support.

Tom

From miika.komu@hiit.fi  Tue Mar 30 21:09:45 2010
Return-Path: <miika.komu@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 AB4BB3A6782 for <hipsec@core3.amsl.com>; Tue, 30 Mar 2010 21:09:45 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -5.469
X-Spam-Level: 
X-Spam-Status: No, score=-5.469 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, DNS_FROM_OPENWHOIS=1.13, 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 hL8Y-awOjhZp for <hipsec@core3.amsl.com>; Tue, 30 Mar 2010 21:09:44 -0700 (PDT)
Received: from hutcs.cs.hut.fi (hutcs.cs.hut.fi [130.233.192.7]) by core3.amsl.com (Postfix) with ESMTP id 262B53A68F9 for <hipsec@ietf.org>; Tue, 30 Mar 2010 21:09:42 -0700 (PDT)
Received: from hutcs.cs.hut.fi ([130.233.192.7] helo=[127.0.0.1]) by hutcs.cs.hut.fi with esmtpsa (TLSv1:AES256-SHA:256) (Exim 4.54) id 1NwpFq-000383-7L for hipsec@ietf.org; Wed, 31 Mar 2010 07:10:10 +0300
Message-ID: <4BB2CB81.5070008@hiit.fi>
Date: Wed, 31 Mar 2010 07:11:45 +0300
From: Miika Komu <miika.komu@hiit.fi>
User-Agent: Mozilla/5.0 (X11; U; Linux x86_64; en-US; rv:1.9.1.10pre) Gecko/20100328 Shredder/3.0.5pre
MIME-Version: 1.0
To: hipsec@ietf.org
References: <BF345F63074F8040B58C00A186FCA57F1C6AA56C57@NALASEXMB04.na.qualcomm.com> <7CC566635CFE364D87DC5803D4712A6C4CE8C2719F@XCH-NW-10V.nw.nos.boeing.com>
In-Reply-To: <7CC566635CFE364D87DC5803D4712A6C4CE8C2719F@XCH-NW-10V.nw.nos.boeing.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Subject: Re: [Hipsec] Follow-up on 4843bis / ORCHIDv2
X-BeenThere: hipsec@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
Reply-To: miika.komu@hiit.fi
List-Id: "This is the official IETF Mailing List for the HIP Working Group." <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, 31 Mar 2010 04:09:45 -0000

On 31/03/10 00:36, Henderson, Thomas R wrote:

Hi,

>> -----Original Message----- From: hipsec-bounces@ietf.org
>> [mailto:hipsec-bounces@ietf.org] On Behalf Of Laganier, Julien
>> Sent: Tuesday, March 30, 2010 2:29 PM To: hipsec@ietf.org Cc:
>> pekka.nikander@ericsson.com Subject: [Hipsec] Follow-up on 4843bis
>> / ORCHIDv2
>>
>> Folks,
>>
>> As proposed at last IETF meeting, it seems we have a way forward
>> with 4843bis:
>>
>> 1. HIP WG to have a 4843bis deliverable that introduces
>> crypto-agility - Request permanent allocation of a new /28 prefix
>> for ORCHIDv2 - Introduces ORCHIDv2 Generation Algorithm (OGA),
>> defined in a given Context - (e.g. HIP in RFC5201 bis) - Define new
>> ORCHIv2 Generation Procedure: Input := any bitstring ORCHID Input
>> := Context ID | Input ORCHID Ouput := OGA( ORCHID Input ) ORCHID :=
>> Prefix | OGA Type | Encode_96( ORCHID Ouput)
>>
>> =>  question mark: Do we let the current 2001:10::/28 allocation
>> expire? I recommend we do as it will make it easier to obtain a
>> permanent allocation.
>
> +1

+1

>> 2. HIP WG to allocate OGA Type 1 as SHA1 in 5201bis and keep other
>> values as unallocated, allocation requiring IETF specification.
>>
>> =>  question mark: Do we start with SHA-256 instead?
>
> I would be happy to delegate the question to the crypto forum or
> other experts, but my impression is that SHA-1 is already being
> phased out elsewhere and that existing libraries typically have
> SHA-256 support.

I was following discussion of other people in the IETF and their opinion 
seemed to be that...

* SHA-256 may be an overkill for sensors
* Attacks on SHA1 are collision attacks where as we need just the 
preimage property

For further information, please refer to:

http://tools.ietf.org/search/rfc4270

From samu.varjonen@hiit.fi  Tue Mar 30 23:52:15 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 C87473A699F for <hipsec@core3.amsl.com>; Tue, 30 Mar 2010 23:52:15 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.469
X-Spam-Level: 
X-Spam-Status: No, score=-1.469 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, DNS_FROM_OPENWHOIS=1.13]
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 Bw2Cf0Gnlu2V for <hipsec@core3.amsl.com>; Tue, 30 Mar 2010 23:52:14 -0700 (PDT)
Received: from argo.otaverkko.fi (argo.otaverkko.fi [212.68.0.2]) by core3.amsl.com (Postfix) with ESMTP id 63FB33A6A48 for <hipsec@ietf.org>; Tue, 30 Mar 2010 23:52:11 -0700 (PDT)
Received: from [10.0.0.145] (kone170188.ippnet.fi [62.197.170.188]) by argo.otaverkko.fi (Postfix) with ESMTP id 02A7D25ED1E; Wed, 31 Mar 2010 09:52:40 +0300 (EEST)
Message-ID: <4BB2F138.7010305@hiit.fi>
Date: Wed, 31 Mar 2010 09:52:40 +0300
From: Varjonen Samu <samu.varjonen@hiit.fi>
User-Agent: Thunderbird 2.0.0.24 (X11/20100317)
MIME-Version: 1.0
To: miika.komu@hiit.fi
References: <BF345F63074F8040B58C00A186FCA57F1C6AA56C57@NALASEXMB04.na.qualcomm.com>	<7CC566635CFE364D87DC5803D4712A6C4CE8C2719F@XCH-NW-10V.nw.nos.boeing.com> <4BB2CB81.5070008@hiit.fi>
In-Reply-To: <4BB2CB81.5070008@hiit.fi>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Cc: hipsec@ietf.org
Subject: Re: [Hipsec] Follow-up on 4843bis / ORCHIDv2
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, 31 Mar 2010 06:52:15 -0000

Miika Komu wrote:
> On 31/03/10 00:36, Henderson, Thomas R wrote:
> 
> Hi,
> 
>>> -----Original Message----- From: hipsec-bounces@ietf.org
>>> [mailto:hipsec-bounces@ietf.org] On Behalf Of Laganier, Julien
>>> Sent: Tuesday, March 30, 2010 2:29 PM To: hipsec@ietf.org Cc:
>>> pekka.nikander@ericsson.com Subject: [Hipsec] Follow-up on 4843bis
>>> / ORCHIDv2
>>>
>>> Folks,
>>>
>>> As proposed at last IETF meeting, it seems we have a way forward
>>> with 4843bis:
>>>
>>> 1. HIP WG to have a 4843bis deliverable that introduces
>>> crypto-agility - Request permanent allocation of a new /28 prefix
>>> for ORCHIDv2 - Introduces ORCHIDv2 Generation Algorithm (OGA),
>>> defined in a given Context - (e.g. HIP in RFC5201 bis) - Define new
>>> ORCHIv2 Generation Procedure: Input := any bitstring ORCHID Input
>>> := Context ID | Input ORCHID Ouput := OGA( ORCHID Input ) ORCHID :=
>>> Prefix | OGA Type | Encode_96( ORCHID Ouput)
>>>
>>> =>  question mark: Do we let the current 2001:10::/28 allocation
>>> expire? I recommend we do as it will make it easier to obtain a
>>> permanent allocation.
>>
>> +1
> 
> +1
+1
> 
>>> 2. HIP WG to allocate OGA Type 1 as SHA1 in 5201bis and keep other
>>> values as unallocated, allocation requiring IETF specification.
>>>
>>> =>  question mark: Do we start with SHA-256 instead?
>>
>> I would be happy to delegate the question to the crypto forum or
>> other experts, but my impression is that SHA-1 is already being
>> phased out elsewhere and that existing libraries typically have
>> SHA-256 support.
> 
> I was following discussion of other people in the IETF and their opinion 
> seemed to be that...
> 
> * SHA-256 may be an overkill for sensors
> * Attacks on SHA1 are collision attacks where as we need just the 
> preimage property
> 
> For further information, please refer to:
> 
> http://tools.ietf.org/search/rfc4270
> _______________________________________________
> Hipsec mailing list
> Hipsec@ietf.org
> https://www.ietf.org/mailman/listinfo/hipsec


From wang.jun17@zte.com.cn  Wed Mar 31 01:36:03 2010
Return-Path: <wang.jun17@zte.com.cn>
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 5EC6B3A67F9; Wed, 31 Mar 2010 01:36:03 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -94.091
X-Spam-Level: 
X-Spam-Status: No, score=-94.091 tagged_above=-999 required=5 tests=[BAYES_40=-0.185, DNS_FROM_OPENWHOIS=1.13, HTML_MESSAGE=0.001, MIME_BASE64_TEXT=1.753, MIME_CHARSET_FARAWAY=2.45, RCVD_DOUBLE_IP_LOOSE=0.76, 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 FDvuVdtvagkI; Wed, 31 Mar 2010 01:36:02 -0700 (PDT)
Received: from mx6.zte.com.cn (mx6.zte.com.cn [63.218.89.70]) by core3.amsl.com (Postfix) with ESMTP id AC0D33A67AD; Wed, 31 Mar 2010 01:35:59 -0700 (PDT)
Received: from [10.30.17.100] by mx6.zte.com.cn with surfront esmtp id 128642312144290; Wed, 31 Mar 2010 16:34:52 +0800 (CST)
Received: from [192.168.168.1] by [192.168.168.16] with StormMail ESMTP id 96829.3615427014; Wed, 31 Mar 2010 16:33:38 +0800 (CST)
Received: from notes_smtp.zte.com.cn ([10.30.1.239]) by mse2.zte.com.cn with ESMTP id o2V8aCCN089958; Wed, 31 Mar 2010 16:36:18 +0800 (CST) (envelope-from wang.jun17@zte.com.cn)
In-Reply-To: <4BB2F138.7010305@hiit.fi>
To: Varjonen Samu <samu.varjonen@hiit.fi>
MIME-Version: 1.0
X-Mailer: Lotus Notes Release 6.5.4 March 27, 2005
Message-ID: <OF3A669355.4E545420-ON482576F7.002E81F9-482576F7.002F4059@zte.com.cn>
From: wang.jun17@zte.com.cn
Date: Wed, 31 Mar 2010 16:36:07 +0800
X-MIMETrack: Serialize by Router on notes_smtp/zte_ltd(Release 6.5.4|March 27, 2005) at 2010-03-31 16:36:09, Serialize complete at 2010-03-31 16:36:09
Content-Type: multipart/alternative; boundary="=_alternative 002F4051482576F7_="
X-MAIL: mse2.zte.com.cn o2V8aCCN089958
Cc: hipsec@ietf.org, hipsec-bounces@ietf.org
Subject: Re: [Hipsec] Follow-up on 4843bis / ORCHIDv2
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, 31 Mar 2010 08:36:03 -0000

This is a multipart message in MIME format.
--=_alternative 002F4051482576F7_=
Content-Type: text/plain; charset="GB2312"
Content-Transfer-Encoding: base64

RG9lcyBPUkNISUQgY29uc2lkZXIgYW55IGNvbW1lcmNpYWwgZGVwbG95bWVudCByZXF1aXJlbWVu
dHM/DQpJZiBISVAgY291bGQgYmUgY29tbWVyY2lhbCBkZXBsb3llZCwgSElQIElEIHNob3VsZCBi
ZSBkaXZpZGVkIGludG8gbWFueSANCnN1Yi1waWVjZXMgYW5kIGFsbG9jYXRlZCB0byBzZXJ2aWNl
IHByb3ZpZGVycyBvciBvdGhlciBvcmdhbml6YXRpb25zIC4NCg0KDQpSdXNzZWxsIFdhbmcNCg0K
DQoNCg0KVmFyam9uZW4gU2FtdSA8c2FtdS52YXJqb25lbkBoaWl0LmZpPiANCreivP7IyzogIGhp
cHNlYy1ib3VuY2VzQGlldGYub3JnDQoyMDEwLTAzLTMxIDE0OjUyDQoNCsrVvP7Iyw0KbWlpa2Eu
a29tdUBoaWl0LmZpDQqzrcvNDQpoaXBzZWNAaWV0Zi5vcmcNCtb3zOINClJlOiBbSGlwc2VjXSBG
b2xsb3ctdXAgb24gNDg0M2JpcyAvIE9SQ0hJRHYyDQoNCg0KDQoNCg0KDQpNaWlrYSBLb211IHdy
b3RlOg0KPiBPbiAzMS8wMy8xMCAwMDozNiwgSGVuZGVyc29uLCBUaG9tYXMgUiB3cm90ZToNCj4g
DQo+IEhpLA0KPiANCj4+PiAtLS0tLU9yaWdpbmFsIE1lc3NhZ2UtLS0tLSBGcm9tOiBoaXBzZWMt
Ym91bmNlc0BpZXRmLm9yZw0KPj4+IFttYWlsdG86aGlwc2VjLWJvdW5jZXNAaWV0Zi5vcmddIE9u
IEJlaGFsZiBPZiBMYWdhbmllciwgSnVsaWVuDQo+Pj4gU2VudDogVHVlc2RheSwgTWFyY2ggMzAs
IDIwMTAgMjoyOSBQTSBUbzogaGlwc2VjQGlldGYub3JnIENjOg0KPj4+IHBla2thLm5pa2FuZGVy
QGVyaWNzc29uLmNvbSBTdWJqZWN0OiBbSGlwc2VjXSBGb2xsb3ctdXAgb24gNDg0M2Jpcw0KPj4+
IC8gT1JDSElEdjINCj4+Pg0KPj4+IEZvbGtzLA0KPj4+DQo+Pj4gQXMgcHJvcG9zZWQgYXQgbGFz
dCBJRVRGIG1lZXRpbmcsIGl0IHNlZW1zIHdlIGhhdmUgYSB3YXkgZm9yd2FyZA0KPj4+IHdpdGgg
NDg0M2JpczoNCj4+Pg0KPj4+IDEuIEhJUCBXRyB0byBoYXZlIGEgNDg0M2JpcyBkZWxpdmVyYWJs
ZSB0aGF0IGludHJvZHVjZXMNCj4+PiBjcnlwdG8tYWdpbGl0eSAtIFJlcXVlc3QgcGVybWFuZW50
IGFsbG9jYXRpb24gb2YgYSBuZXcgLzI4IHByZWZpeA0KPj4+IGZvciBPUkNISUR2MiAtIEludHJv
ZHVjZXMgT1JDSElEdjIgR2VuZXJhdGlvbiBBbGdvcml0aG0gKE9HQSksDQo+Pj4gZGVmaW5lZCBp
biBhIGdpdmVuIENvbnRleHQgLSAoZS5nLiBISVAgaW4gUkZDNTIwMSBiaXMpIC0gRGVmaW5lIG5l
dw0KPj4+IE9SQ0hJdjIgR2VuZXJhdGlvbiBQcm9jZWR1cmU6IElucHV0IDo9IGFueSBiaXRzdHJp
bmcgT1JDSElEIElucHV0DQo+Pj4gOj0gQ29udGV4dCBJRCB8IElucHV0IE9SQ0hJRCBPdXB1dCA6
PSBPR0EoIE9SQ0hJRCBJbnB1dCApIE9SQ0hJRCA6PQ0KPj4+IFByZWZpeCB8IE9HQSBUeXBlIHwg
RW5jb2RlXzk2KCBPUkNISUQgT3VwdXQpDQo+Pj4NCj4+PiA9PiAgcXVlc3Rpb24gbWFyazogRG8g
d2UgbGV0IHRoZSBjdXJyZW50IDIwMDE6MTA6Oi8yOCBhbGxvY2F0aW9uDQo+Pj4gZXhwaXJlPyBJ
IHJlY29tbWVuZCB3ZSBkbyBhcyBpdCB3aWxsIG1ha2UgaXQgZWFzaWVyIHRvIG9idGFpbiBhDQo+
Pj4gcGVybWFuZW50IGFsbG9jYXRpb24uDQo+Pg0KPj4gKzENCj4gDQo+ICsxDQorMQ0KPiANCj4+
PiAyLiBISVAgV0cgdG8gYWxsb2NhdGUgT0dBIFR5cGUgMSBhcyBTSEExIGluIDUyMDFiaXMgYW5k
IGtlZXAgb3RoZXINCj4+PiB2YWx1ZXMgYXMgdW5hbGxvY2F0ZWQsIGFsbG9jYXRpb24gcmVxdWly
aW5nIElFVEYgc3BlY2lmaWNhdGlvbi4NCj4+Pg0KPj4+ID0+ICBxdWVzdGlvbiBtYXJrOiBEbyB3
ZSBzdGFydCB3aXRoIFNIQS0yNTYgaW5zdGVhZD8NCj4+DQo+PiBJIHdvdWxkIGJlIGhhcHB5IHRv
IGRlbGVnYXRlIHRoZSBxdWVzdGlvbiB0byB0aGUgY3J5cHRvIGZvcnVtIG9yDQo+PiBvdGhlciBl
eHBlcnRzLCBidXQgbXkgaW1wcmVzc2lvbiBpcyB0aGF0IFNIQS0xIGlzIGFscmVhZHkgYmVpbmcN
Cj4+IHBoYXNlZCBvdXQgZWxzZXdoZXJlIGFuZCB0aGF0IGV4aXN0aW5nIGxpYnJhcmllcyB0eXBp
Y2FsbHkgaGF2ZQ0KPj4gU0hBLTI1NiBzdXBwb3J0Lg0KPiANCj4gSSB3YXMgZm9sbG93aW5nIGRp
c2N1c3Npb24gb2Ygb3RoZXIgcGVvcGxlIGluIHRoZSBJRVRGIGFuZCB0aGVpciBvcGluaW9uIA0K
DQo+IHNlZW1lZCB0byBiZSB0aGF0Li4uDQo+IA0KPiAqIFNIQS0yNTYgbWF5IGJlIGFuIG92ZXJr
aWxsIGZvciBzZW5zb3JzDQo+ICogQXR0YWNrcyBvbiBTSEExIGFyZSBjb2xsaXNpb24gYXR0YWNr
cyB3aGVyZSBhcyB3ZSBuZWVkIGp1c3QgdGhlIA0KPiBwcmVpbWFnZSBwcm9wZXJ0eQ0KPiANCj4g
Rm9yIGZ1cnRoZXIgaW5mb3JtYXRpb24sIHBsZWFzZSByZWZlciB0bzoNCj4gDQo+IGh0dHA6Ly90
b29scy5pZXRmLm9yZy9zZWFyY2gvcmZjNDI3MA0KPiBfX19fX19fX19fX19fX19fX19fX19fX19f
X19fX19fX19fX19fX19fX19fX19fXw0KPiBIaXBzZWMgbWFpbGluZyBsaXN0DQo+IEhpcHNlY0Bp
ZXRmLm9yZw0KPiBodHRwczovL3d3dy5pZXRmLm9yZy9tYWlsbWFuL2xpc3RpbmZvL2hpcHNlYw0K
DQpfX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fXw0KSGlwc2Vj
IG1haWxpbmcgbGlzdA0KSGlwc2VjQGlldGYub3JnDQpodHRwczovL3d3dy5pZXRmLm9yZy9tYWls
bWFuL2xpc3RpbmZvL2hpcHNlYw0KDQoNCg0KDQoNCi0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0t
LS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tDQpaVEUgSW5mb3JtYXRpb24gU2VjdXJpdHkg
Tm90aWNlOiBUaGUgaW5mb3JtYXRpb24gY29udGFpbmVkIGluIHRoaXMgbWFpbCBpcyBzb2xlbHkg
cHJvcGVydHkgb2YgdGhlIHNlbmRlcidzIG9yZ2FuaXphdGlvbi4gVGhpcyBtYWlsIGNvbW11bmlj
YXRpb24gaXMgY29uZmlkZW50aWFsLiBSZWNpcGllbnRzIG5hbWVkIGFib3ZlIGFyZSBvYmxpZ2F0
ZWQgdG8gbWFpbnRhaW4gc2VjcmVjeSBhbmQgYXJlIG5vdCBwZXJtaXR0ZWQgdG8gZGlzY2xvc2Ug
dGhlIGNvbnRlbnRzIG9mIHRoaXMgY29tbXVuaWNhdGlvbiB0byBvdGhlcnMuDQpUaGlzIGVtYWls
IGFuZCBhbnkgZmlsZXMgdHJhbnNtaXR0ZWQgd2l0aCBpdCBhcmUgY29uZmlkZW50aWFsIGFuZCBp
bnRlbmRlZCBzb2xlbHkgZm9yIHRoZSB1c2Ugb2YgdGhlIGluZGl2aWR1YWwgb3IgZW50aXR5IHRv
IHdob20gdGhleSBhcmUgYWRkcmVzc2VkLiBJZiB5b3UgaGF2ZSByZWNlaXZlZCB0aGlzIGVtYWls
IGluIGVycm9yIHBsZWFzZSBub3RpZnkgdGhlIG9yaWdpbmF0b3Igb2YgdGhlIG1lc3NhZ2UuIEFu
eSB2aWV3cyBleHByZXNzZWQgaW4gdGhpcyBtZXNzYWdlIGFyZSB0aG9zZSBvZiB0aGUgaW5kaXZp
ZHVhbCBzZW5kZXIuDQpUaGlzIG1lc3NhZ2UgaGFzIGJlZW4gc2Nhbm5lZCBmb3IgdmlydXNlcyBh
bmQgU3BhbSBieSBaVEUgQW50aS1TcGFtIHN5c3RlbS4NCg==
--=_alternative 002F4051482576F7_=
Content-Type: text/html; charset="GB2312"
Content-Transfer-Encoding: base64

DQo8YnI+PGZvbnQgc2l6ZT0yIGZhY2U9InNhbnMtc2VyaWYiPkRvZXMgT1JDSElEIGNvbnNpZGVy
IGFueSBjb21tZXJjaWFsDQpkZXBsb3ltZW50IHJlcXVpcmVtZW50cz88L2ZvbnQ+DQo8YnI+PGZv
bnQgc2l6ZT0yIGZhY2U9InNhbnMtc2VyaWYiPklmIEhJUCBjb3VsZCBiZSBjb21tZXJjaWFsIGRl
cGxveWVkLA0KSElQIElEIHNob3VsZCBiZSBkaXZpZGVkIGludG8gbWFueSBzdWItcGllY2VzIGFu
ZCBhbGxvY2F0ZWQgdG8gc2VydmljZQ0KcHJvdmlkZXJzIG9yIG90aGVyIG9yZ2FuaXphdGlvbnMg
LjwvZm9udD4NCjxicj4NCjxicj4NCjxicj48Zm9udCBzaXplPTIgZmFjZT0ic2Fucy1zZXJpZiI+
UnVzc2VsbCBXYW5nPGJyPg0KPC9mb250Pg0KPGJyPg0KPGJyPg0KPGJyPg0KPHRhYmxlIHdpZHRo
PTEwMCU+DQo8dHIgdmFsaWduPXRvcD4NCjx0ZCB3aWR0aD0zNCU+PGZvbnQgc2l6ZT0xIGZhY2U9
InNhbnMtc2VyaWYiPjxiPlZhcmpvbmVuIFNhbXUgJmx0O3NhbXUudmFyam9uZW5AaGlpdC5maSZn
dDs8L2I+DQo8L2ZvbnQ+DQo8YnI+PGZvbnQgc2l6ZT0xIGZhY2U9InNhbnMtc2VyaWYiPreivP7I
yzogJm5ic3A7aGlwc2VjLWJvdW5jZXNAaWV0Zi5vcmc8L2ZvbnQ+DQo8cD48Zm9udCBzaXplPTEg
ZmFjZT0ic2Fucy1zZXJpZiI+MjAxMC0wMy0zMSAxNDo1MjwvZm9udD4NCjx0ZCB3aWR0aD02NSU+
DQo8dGFibGUgd2lkdGg9MTAwJT4NCjx0ciB2YWxpZ249dG9wPg0KPHRkPg0KPGRpdiBhbGlnbj1y
aWdodD48Zm9udCBzaXplPTEgZmFjZT0ic2Fucy1zZXJpZiI+ytW8/sjLPC9mb250PjwvZGl2Pg0K
PHRkPjxmb250IHNpemU9MSBmYWNlPSJzYW5zLXNlcmlmIj5taWlrYS5rb211QGhpaXQuZmk8L2Zv
bnQ+DQo8dHIgdmFsaWduPXRvcD4NCjx0ZD4NCjxkaXYgYWxpZ249cmlnaHQ+PGZvbnQgc2l6ZT0x
IGZhY2U9InNhbnMtc2VyaWYiPrOty808L2ZvbnQ+PC9kaXY+DQo8dGQ+PGZvbnQgc2l6ZT0xIGZh
Y2U9InNhbnMtc2VyaWYiPmhpcHNlY0BpZXRmLm9yZzwvZm9udD4NCjx0ciB2YWxpZ249dG9wPg0K
PHRkPg0KPGRpdiBhbGlnbj1yaWdodD48Zm9udCBzaXplPTEgZmFjZT0ic2Fucy1zZXJpZiI+1vfM
4jwvZm9udD48L2Rpdj4NCjx0ZD48Zm9udCBzaXplPTEgZmFjZT0ic2Fucy1zZXJpZiI+UmU6IFtI
aXBzZWNdIEZvbGxvdy11cCBvbiA0ODQzYmlzIC8NCk9SQ0hJRHYyPC9mb250PjwvdGFibGU+DQo8
YnI+DQo8dGFibGU+DQo8dHIgdmFsaWduPXRvcD4NCjx0ZD4NCjx0ZD48L3RhYmxlPg0KPGJyPjwv
dGFibGU+DQo8YnI+DQo8YnI+DQo8YnI+PGZvbnQgc2l6ZT0yPjx0dD5NaWlrYSBLb211IHdyb3Rl
Ojxicj4NCiZndDsgT24gMzEvMDMvMTAgMDA6MzYsIEhlbmRlcnNvbiwgVGhvbWFzIFIgd3JvdGU6
PGJyPg0KJmd0OyA8YnI+DQomZ3Q7IEhpLDxicj4NCiZndDsgPGJyPg0KJmd0OyZndDsmZ3Q7IC0t
LS0tT3JpZ2luYWwgTWVzc2FnZS0tLS0tIEZyb206IGhpcHNlYy1ib3VuY2VzQGlldGYub3JnPGJy
Pg0KJmd0OyZndDsmZ3Q7IFttYWlsdG86aGlwc2VjLWJvdW5jZXNAaWV0Zi5vcmddIE9uIEJlaGFs
ZiBPZiBMYWdhbmllciwgSnVsaWVuPGJyPg0KJmd0OyZndDsmZ3Q7IFNlbnQ6IFR1ZXNkYXksIE1h
cmNoIDMwLCAyMDEwIDI6MjkgUE0gVG86IGhpcHNlY0BpZXRmLm9yZw0KQ2M6PGJyPg0KJmd0OyZn
dDsmZ3Q7IHBla2thLm5pa2FuZGVyQGVyaWNzc29uLmNvbSBTdWJqZWN0OiBbSGlwc2VjXSBGb2xs
b3ctdXAgb24NCjQ4NDNiaXM8YnI+DQomZ3Q7Jmd0OyZndDsgLyBPUkNISUR2Mjxicj4NCiZndDsm
Z3Q7Jmd0Ozxicj4NCiZndDsmZ3Q7Jmd0OyBGb2xrcyw8YnI+DQomZ3Q7Jmd0OyZndDs8YnI+DQom
Z3Q7Jmd0OyZndDsgQXMgcHJvcG9zZWQgYXQgbGFzdCBJRVRGIG1lZXRpbmcsIGl0IHNlZW1zIHdl
IGhhdmUgYSB3YXkgZm9yd2FyZDxicj4NCiZndDsmZ3Q7Jmd0OyB3aXRoIDQ4NDNiaXM6PGJyPg0K
Jmd0OyZndDsmZ3Q7PGJyPg0KJmd0OyZndDsmZ3Q7IDEuIEhJUCBXRyB0byBoYXZlIGEgNDg0M2Jp
cyBkZWxpdmVyYWJsZSB0aGF0IGludHJvZHVjZXM8YnI+DQomZ3Q7Jmd0OyZndDsgY3J5cHRvLWFn
aWxpdHkgLSBSZXF1ZXN0IHBlcm1hbmVudCBhbGxvY2F0aW9uIG9mIGEgbmV3IC8yOA0KcHJlZml4
PGJyPg0KJmd0OyZndDsmZ3Q7IGZvciBPUkNISUR2MiAtIEludHJvZHVjZXMgT1JDSElEdjIgR2Vu
ZXJhdGlvbiBBbGdvcml0aG0gKE9HQSksPGJyPg0KJmd0OyZndDsmZ3Q7IGRlZmluZWQgaW4gYSBn
aXZlbiBDb250ZXh0IC0gKGUuZy4gSElQIGluIFJGQzUyMDEgYmlzKSAtIERlZmluZQ0KbmV3PGJy
Pg0KJmd0OyZndDsmZ3Q7IE9SQ0hJdjIgR2VuZXJhdGlvbiBQcm9jZWR1cmU6IElucHV0IDo9IGFu
eSBiaXRzdHJpbmcgT1JDSElEDQpJbnB1dDxicj4NCiZndDsmZ3Q7Jmd0OyA6PSBDb250ZXh0IElE
IHwgSW5wdXQgT1JDSElEIE91cHV0IDo9IE9HQSggT1JDSElEIElucHV0ICkNCk9SQ0hJRCA6PTxi
cj4NCiZndDsmZ3Q7Jmd0OyBQcmVmaXggfCBPR0EgVHlwZSB8IEVuY29kZV85NiggT1JDSElEIE91
cHV0KTxicj4NCiZndDsmZ3Q7Jmd0Ozxicj4NCiZndDsmZ3Q7Jmd0OyA9Jmd0OyAmbmJzcDtxdWVz
dGlvbiBtYXJrOiBEbyB3ZSBsZXQgdGhlIGN1cnJlbnQgMjAwMToxMDo6LzI4DQphbGxvY2F0aW9u
PGJyPg0KJmd0OyZndDsmZ3Q7IGV4cGlyZT8gSSByZWNvbW1lbmQgd2UgZG8gYXMgaXQgd2lsbCBt
YWtlIGl0IGVhc2llciB0byBvYnRhaW4NCmE8YnI+DQomZ3Q7Jmd0OyZndDsgcGVybWFuZW50IGFs
bG9jYXRpb24uPGJyPg0KJmd0OyZndDs8YnI+DQomZ3Q7Jmd0OyArMTxicj4NCiZndDsgPGJyPg0K
Jmd0OyArMTxicj4NCisxPGJyPg0KJmd0OyA8YnI+DQomZ3Q7Jmd0OyZndDsgMi4gSElQIFdHIHRv
IGFsbG9jYXRlIE9HQSBUeXBlIDEgYXMgU0hBMSBpbiA1MjAxYmlzIGFuZCBrZWVwDQpvdGhlcjxi
cj4NCiZndDsmZ3Q7Jmd0OyB2YWx1ZXMgYXMgdW5hbGxvY2F0ZWQsIGFsbG9jYXRpb24gcmVxdWly
aW5nIElFVEYgc3BlY2lmaWNhdGlvbi48YnI+DQomZ3Q7Jmd0OyZndDs8YnI+DQomZ3Q7Jmd0OyZn
dDsgPSZndDsgJm5ic3A7cXVlc3Rpb24gbWFyazogRG8gd2Ugc3RhcnQgd2l0aCBTSEEtMjU2IGlu
c3RlYWQ/PGJyPg0KJmd0OyZndDs8YnI+DQomZ3Q7Jmd0OyBJIHdvdWxkIGJlIGhhcHB5IHRvIGRl
bGVnYXRlIHRoZSBxdWVzdGlvbiB0byB0aGUgY3J5cHRvIGZvcnVtDQpvcjxicj4NCiZndDsmZ3Q7
IG90aGVyIGV4cGVydHMsIGJ1dCBteSBpbXByZXNzaW9uIGlzIHRoYXQgU0hBLTEgaXMgYWxyZWFk
eSBiZWluZzxicj4NCiZndDsmZ3Q7IHBoYXNlZCBvdXQgZWxzZXdoZXJlIGFuZCB0aGF0IGV4aXN0
aW5nIGxpYnJhcmllcyB0eXBpY2FsbHkgaGF2ZTxicj4NCiZndDsmZ3Q7IFNIQS0yNTYgc3VwcG9y
dC48YnI+DQomZ3Q7IDxicj4NCiZndDsgSSB3YXMgZm9sbG93aW5nIGRpc2N1c3Npb24gb2Ygb3Ro
ZXIgcGVvcGxlIGluIHRoZSBJRVRGIGFuZCB0aGVpciBvcGluaW9uDQo8YnI+DQomZ3Q7IHNlZW1l
ZCB0byBiZSB0aGF0Li4uPGJyPg0KJmd0OyA8YnI+DQomZ3Q7ICogU0hBLTI1NiBtYXkgYmUgYW4g
b3ZlcmtpbGwgZm9yIHNlbnNvcnM8YnI+DQomZ3Q7ICogQXR0YWNrcyBvbiBTSEExIGFyZSBjb2xs
aXNpb24gYXR0YWNrcyB3aGVyZSBhcyB3ZSBuZWVkIGp1c3QgdGhlDQo8YnI+DQomZ3Q7IHByZWlt
YWdlIHByb3BlcnR5PGJyPg0KJmd0OyA8YnI+DQomZ3Q7IEZvciBmdXJ0aGVyIGluZm9ybWF0aW9u
LCBwbGVhc2UgcmVmZXIgdG86PGJyPg0KJmd0OyA8YnI+DQomZ3Q7IGh0dHA6Ly90b29scy5pZXRm
Lm9yZy9zZWFyY2gvcmZjNDI3MDxicj4NCiZndDsgX19fX19fX19fX19fX19fX19fX19fX19fX19f
X19fX19fX19fX19fX19fX19fX188YnI+DQomZ3Q7IEhpcHNlYyBtYWlsaW5nIGxpc3Q8YnI+DQom
Z3Q7IEhpcHNlY0BpZXRmLm9yZzxicj4NCiZndDsgaHR0cHM6Ly93d3cuaWV0Zi5vcmcvbWFpbG1h
bi9saXN0aW5mby9oaXBzZWM8YnI+DQo8YnI+DQpfX19fX19fX19fX19fX19fX19fX19fX19fX19f
X19fX19fX19fX19fX19fX19fXzxicj4NCkhpcHNlYyBtYWlsaW5nIGxpc3Q8YnI+DQpIaXBzZWNA
aWV0Zi5vcmc8YnI+DQpodHRwczovL3d3dy5pZXRmLm9yZy9tYWlsbWFuL2xpc3RpbmZvL2hpcHNl
Yzxicj4NCjxicj4NCjwvdHQ+PC9mb250Pg0KPGJyPg0KPGJyPjxwcmU+DQotLS0tLS0tLS0tLS0t
LS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLQ0KWlRFJm5ic3A7SW5m
b3JtYXRpb24mbmJzcDtTZWN1cml0eSZuYnNwO05vdGljZTombmJzcDtUaGUmbmJzcDtpbmZvcm1h
dGlvbiZuYnNwO2NvbnRhaW5lZCZuYnNwO2luJm5ic3A7dGhpcyZuYnNwO21haWwmbmJzcDtpcyZu
YnNwO3NvbGVseSZuYnNwO3Byb3BlcnR5Jm5ic3A7b2YmbmJzcDt0aGUmbmJzcDtzZW5kZXIncyZu
YnNwO29yZ2FuaXphdGlvbi4mbmJzcDtUaGlzJm5ic3A7bWFpbCZuYnNwO2NvbW11bmljYXRpb24m
bmJzcDtpcyZuYnNwO2NvbmZpZGVudGlhbC4mbmJzcDtSZWNpcGllbnRzJm5ic3A7bmFtZWQmbmJz
cDthYm92ZSZuYnNwO2FyZSZuYnNwO29ibGlnYXRlZCZuYnNwO3RvJm5ic3A7bWFpbnRhaW4mbmJz
cDtzZWNyZWN5Jm5ic3A7YW5kJm5ic3A7YXJlJm5ic3A7bm90Jm5ic3A7cGVybWl0dGVkJm5ic3A7
dG8mbmJzcDtkaXNjbG9zZSZuYnNwO3RoZSZuYnNwO2NvbnRlbnRzJm5ic3A7b2YmbmJzcDt0aGlz
Jm5ic3A7Y29tbXVuaWNhdGlvbiZuYnNwO3RvJm5ic3A7b3RoZXJzLg0KVGhpcyZuYnNwO2VtYWls
Jm5ic3A7YW5kJm5ic3A7YW55Jm5ic3A7ZmlsZXMmbmJzcDt0cmFuc21pdHRlZCZuYnNwO3dpdGgm
bmJzcDtpdCZuYnNwO2FyZSZuYnNwO2NvbmZpZGVudGlhbCZuYnNwO2FuZCZuYnNwO2ludGVuZGVk
Jm5ic3A7c29sZWx5Jm5ic3A7Zm9yJm5ic3A7dGhlJm5ic3A7dXNlJm5ic3A7b2YmbmJzcDt0aGUm
bmJzcDtpbmRpdmlkdWFsJm5ic3A7b3ImbmJzcDtlbnRpdHkmbmJzcDt0byZuYnNwO3dob20mbmJz
cDt0aGV5Jm5ic3A7YXJlJm5ic3A7YWRkcmVzc2VkLiZuYnNwO0lmJm5ic3A7eW91Jm5ic3A7aGF2
ZSZuYnNwO3JlY2VpdmVkJm5ic3A7dGhpcyZuYnNwO2VtYWlsJm5ic3A7aW4mbmJzcDtlcnJvciZu
YnNwO3BsZWFzZSZuYnNwO25vdGlmeSZuYnNwO3RoZSZuYnNwO29yaWdpbmF0b3ImbmJzcDtvZiZu
YnNwO3RoZSZuYnNwO21lc3NhZ2UuJm5ic3A7QW55Jm5ic3A7dmlld3MmbmJzcDtleHByZXNzZWQm
bmJzcDtpbiZuYnNwO3RoaXMmbmJzcDttZXNzYWdlJm5ic3A7YXJlJm5ic3A7dGhvc2UmbmJzcDtv
ZiZuYnNwO3RoZSZuYnNwO2luZGl2aWR1YWwmbmJzcDtzZW5kZXIuDQpUaGlzJm5ic3A7bWVzc2Fn
ZSZuYnNwO2hhcyZuYnNwO2JlZW4mbmJzcDtzY2FubmVkJm5ic3A7Zm9yJm5ic3A7dmlydXNlcyZu
YnNwO2FuZCZuYnNwO1NwYW0mbmJzcDtieSZuYnNwO1pURSZuYnNwO0FudGktU3BhbSZuYnNwO3N5
c3RlbS4NCjwvcHJlPg==
--=_alternative 002F4051482576F7_=--


From heer@informatik.rwth-aachen.de  Wed Mar 31 04:25:35 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 6B7363A698A for <hipsec@core3.amsl.com>; Wed, 31 Mar 2010 04:25:35 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.221
X-Spam-Level: 
X-Spam-Status: No, score=-1.221 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, DNS_FROM_OPENWHOIS=1.13, HELO_EQ_DE=0.35, HELO_MISMATCH_DE=1.448, MIME_CHARSET_FARAWAY=2.45, 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 dF98lDo0rmZE for <hipsec@core3.amsl.com>; Wed, 31 Mar 2010 04:25:33 -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 B1BD43A6846 for <hipsec@ietf.org>; Wed, 31 Mar 2010 04:25:33 -0700 (PDT)
MIME-version: 1.0
Content-type: text/plain; charset=GB2312
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 <0L0500G3R93EE7G0@mta-2.ms.rz.RWTH-Aachen.de> for hipsec@ietf.org; Wed, 31 Mar 2010 13:26:02 +0200 (CEST)
X-IronPort-AV: E=Sophos;i="4.51,341,1267398000";   d="scan'208";a="51091034"
Received: from relay-auth-1.ms.rz.rwth-aachen.de (HELO relay-auth-1) ([134.130.7.78]) by ironport-in-1.rz.rwth-aachen.de with ESMTP; Wed, 31 Mar 2010 13:25:52 +0200
Received: from [137.226.12.163] ([unknown] [137.226.12.163]) by relay-auth-1.ms.rz.rwth-aachen.de (Sun Java(tm) System Messaging Server 7.0-3.01 64bit (built Dec 9 2008)) with ESMTPA id <0L0500JOG933RD70@relay-auth-1.ms.rz.rwth-aachen.de> for hipsec@ietf.org; Wed, 31 Mar 2010 13:25:52 +0200 (CEST)
From: Tobias Heer <heer@cs.rwth-aachen.de>
In-reply-to: <OF3A669355.4E545420-ON482576F7.002E81F9-482576F7.002F4059@zte.com.cn>
Date: Wed, 31 Mar 2010 13:26:13 +0200
Content-transfer-encoding: quoted-printable
Message-id: <D5ADDB6D-50E8-4998-A037-70E37444E786@cs.rwth-aachen.de>
References: <OF3A669355.4E545420-ON482576F7.002E81F9-482576F7.002F4059@zte.com.cn>
To: wang.jun17@zte.com.cn
X-Mailer: Apple Mail (2.1077)
Cc: "hipsec@ietf.org WG" <hipsec@ietf.org>
Subject: Re: [Hipsec] Follow-up on 4843bis / ORCHIDv2
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, 31 Mar 2010 11:25:35 -0000

Hello Russel,=20

Am 31.03.2010 um 10:36 schrieb wang.jun17@zte.com.cn:

> Does ORCHID consider any commercial deployment requirements?
> If HIP could be commercial deployed, HIP ID should be divided into =
many=20
> sub-pieces and allocated to service providers or other organizations .
>=20
This might be important for future consideration, however, at the moment =
the namespace of the HIT is flat and does not allow that. However, the =
new design of the ORCHID can allow for such hierarchy by implementing a =
new OGA type that specifies that some of the bits in the orchid should =
be interpreted as organization ID. However, this has to be thought =
through thoroughly since it occupies at least one of the few OGA type =
IDs we have to our avail.

BR,=20

Tobias

>=20
> Russell Wang
>=20
>=20
>=20
>=20
> Varjonen Samu <samu.varjonen@hiit.fi>=20
> =B7=A2=BC=FE=C8=CB:  hipsec-bounces@ietf.org
> 2010-03-31 14:52
>=20
> =CA=D5=BC=FE=C8=CB
> miika.komu@hiit.fi
> =B3=AD=CB=CD
> hipsec@ietf.org
> =D6=F7=CC=E2
> Re: [Hipsec] Follow-up on 4843bis / ORCHIDv2
>=20
>=20
>=20
>=20
>=20
>=20
> Miika Komu wrote:
>> On 31/03/10 00:36, Henderson, Thomas R wrote:
>>=20
>> Hi,
>>=20
>>>> -----Original Message----- From: hipsec-bounces@ietf.org
>>>> [mailto:hipsec-bounces@ietf.org] On Behalf Of Laganier, Julien
>>>> Sent: Tuesday, March 30, 2010 2:29 PM To: hipsec@ietf.org Cc:
>>>> pekka.nikander@ericsson.com Subject: [Hipsec] Follow-up on 4843bis
>>>> / ORCHIDv2
>>>>=20
>>>> Folks,
>>>>=20
>>>> As proposed at last IETF meeting, it seems we have a way forward
>>>> with 4843bis:
>>>>=20
>>>> 1. HIP WG to have a 4843bis deliverable that introduces
>>>> crypto-agility - Request permanent allocation of a new /28 prefix
>>>> for ORCHIDv2 - Introduces ORCHIDv2 Generation Algorithm (OGA),
>>>> defined in a given Context - (e.g. HIP in RFC5201 bis) - Define new
>>>> ORCHIv2 Generation Procedure: Input :=3D any bitstring ORCHID Input
>>>> :=3D Context ID | Input ORCHID Ouput :=3D OGA( ORCHID Input ) =
ORCHID :=3D
>>>> Prefix | OGA Type | Encode_96( ORCHID Ouput)
>>>>=20
>>>> =3D>  question mark: Do we let the current 2001:10::/28 allocation
>>>> expire? I recommend we do as it will make it easier to obtain a
>>>> permanent allocation.
>>>=20
>>> +1
>>=20
>> +1
> +1
>>=20
>>>> 2. HIP WG to allocate OGA Type 1 as SHA1 in 5201bis and keep other
>>>> values as unallocated, allocation requiring IETF specification.
>>>>=20
>>>> =3D>  question mark: Do we start with SHA-256 instead?
>>>=20
>>> I would be happy to delegate the question to the crypto forum or
>>> other experts, but my impression is that SHA-1 is already being
>>> phased out elsewhere and that existing libraries typically have
>>> SHA-256 support.
>>=20
>> I was following discussion of other people in the IETF and their =
opinion=20
>=20
>> seemed to be that...
>>=20
>> * SHA-256 may be an overkill for sensors
>> * Attacks on SHA1 are collision attacks where as we need just the=20
>> preimage property
>>=20
>> For further information, please refer to:
>>=20
>> http://tools.ietf.org/search/rfc4270
>> _______________________________________________
>> Hipsec mailing list
>> Hipsec@ietf.org
>> https://www.ietf.org/mailman/listinfo/hipsec
>=20
> _______________________________________________
> Hipsec mailing list
> Hipsec@ietf.org
> https://www.ietf.org/mailman/listinfo/hipsec
>=20
>=20
>=20
>=20
>=20
> --------------------------------------------------------
> ZTE Information Security Notice: The information contained in this =
mail is solely property of the sender's organization. This mail =
communication is confidential. Recipients named above are obligated to =
maintain secrecy and are not permitted to disclose the contents of this =
communication to others.
> This email and any files transmitted with it are confidential and =
intended solely for the use of the individual or entity to whom they are =
addressed. If you have received this email in error please notify the =
originator of the message. Any views expressed in this message are those =
of the individual sender.
> This message has been scanned for viruses and Spam by ZTE Anti-Spam =
system.
> _______________________________________________
> Hipsec mailing list
> Hipsec@ietf.org
> https://www.ietf.org/mailman/listinfo/hipsec




-- =20

Dipl.-Inform. Tobias Heer, Ph.D. Student
Distributed Systems Group=20
RWTH Aachen University, Germany
tel: +49 241 80 207 76
web: http://ds.cs.rwth-aachen.de/members/heer








From julienl@qualcomm.com  Wed Mar 31 08:35:07 2010
Return-Path: <julienl@qualcomm.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 850863A68BD; Wed, 31 Mar 2010 08:35:07 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -105.469
X-Spam-Level: 
X-Spam-Status: No, score=-105.469 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, DNS_FROM_OPENWHOIS=1.13, RCVD_IN_DNSWL_MED=-4,  USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id edW2SYxgf01L; Wed, 31 Mar 2010 08:35:04 -0700 (PDT)
Received: from wolverine01.qualcomm.com (wolverine01.qualcomm.com [199.106.114.254]) by core3.amsl.com (Postfix) with ESMTP id E350D3A696A; Wed, 31 Mar 2010 08:35:03 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=qualcomm.com; i=julienl@qualcomm.com; q=dns/txt; s=qcdkim; t=1270049735; x=1301585735; h=from:to:cc:date:subject:thread-topic:thread-index: message-id:references:in-reply-to:accept-language: content-language:x-ms-has-attach:x-ms-tnef-correlator: acceptlanguage:content-type:content-transfer-encoding: mime-version:x-ironport-av; z=From:=20"Laganier,=20Julien"=20<julienl@qualcomm.com> |To:=20"wang.jun17@zte.com.cn"=20<wang.jun17@zte.com.cn>, =20Varjonen=20Samu=0D=0A=09<samu.varjonen@hiit.fi>|CC:=20 "hipsec@ietf.org"=20<hipsec@ietf.org>,=20"hipsec-bounces@ ietf.org"=0D=0A=09<hipsec-bounces@ietf.org>|Date:=20Wed, =2031=20Mar=202010=2008:35:31=20-0700|Subject:=20RE:=20[H ipsec]=20Follow-up=20on=204843bis=20/=20ORCHIDv2 |Thread-Topic:=20[Hipsec]=20Follow-up=20on=204843bis=20/ =20ORCHIDv2|Thread-Index:=20AcrQrUfnTbTNRX01SDuueWVDzzj3B wAOZODA|Message-ID:=20<BF345F63074F8040B58C00A186FCA57F1C 6AA56CD2@NALASEXMB04.na.qualcomm.com>|References:=20<4BB2 F138.7010305@hiit.fi>=0D=0A=20<OF3A669355.4E545420-ON4825 76F7.002E81F9-482576F7.002F4059@zte.com.cn>|In-Reply-To: =20<OF3A669355.4E545420-ON482576F7.002E81F9-482576F7.002F 4059@zte.com.cn>|Accept-Language:=20en-US |Content-Language:=20en-US|X-MS-Has-Attach: |X-MS-TNEF-Correlator:|acceptlanguage:=20en-US |Content-Type:=20text/plain=3B=20charset=3D"us-ascii" |Content-Transfer-Encoding:=20quoted-printable |MIME-Version:=201.0|X-IronPort-AV:=20E=3DMcAfee=3Bi=3D"5 400,1158,5937"=3B=20a=3D"37691534"; bh=itA7y2Mf9bCY+C7dolrmO7PPZgyt8ZTuc9nkBfgLma4=; b=BdOtDxb7o/Cew3v8fk/2UWzbmDShJxybFYOV9U9V/xEUqEO0AWWIxGmw 0Sd6C/n0mhXTM5zrV6tO0GbZWsJhF7PpJfhptdtLrxTGUA5GNVxTxNFIt 5lsKVWrKCWqot/DmQYksb/zet630UbQy48urJ8TEEGanz2ENE66nkMVZH M=;
X-IronPort-AV: E=McAfee;i="5400,1158,5937"; a="37691534"
Received: from ironmsg01-r.qualcomm.com ([172.30.46.15]) by wolverine01.qualcomm.com with ESMTP; 31 Mar 2010 08:35:35 -0700
Received: from nasanexhub05.na.qualcomm.com ([129.46.134.219]) by ironmsg01-r.qualcomm.com with ESMTP/TLS/RC4-MD5; 31 Mar 2010 08:35:34 -0700
Received: from nalasexhc01.na.qualcomm.com (10.47.129.185) by nasanexhub05.na.qualcomm.com (129.46.134.219) with Microsoft SMTP Server (TLS) id 8.2.234.1; Wed, 31 Mar 2010 08:35:33 -0700
Received: from NALASEXMB04.na.qualcomm.com ([10.47.7.114]) by nalasexhc01.na.qualcomm.com ([10.47.129.185]) with mapi; Wed, 31 Mar 2010 08:35:33 -0700
From: "Laganier, Julien" <julienl@qualcomm.com>
To: "wang.jun17@zte.com.cn" <wang.jun17@zte.com.cn>, Varjonen Samu <samu.varjonen@hiit.fi>
Date: Wed, 31 Mar 2010 08:35:31 -0700
Thread-Topic: [Hipsec] Follow-up on 4843bis / ORCHIDv2
Thread-Index: AcrQrUfnTbTNRX01SDuueWVDzzj3BwAOZODA
Message-ID: <BF345F63074F8040B58C00A186FCA57F1C6AA56CD2@NALASEXMB04.na.qualcomm.com>
References: <4BB2F138.7010305@hiit.fi> <OF3A669355.4E545420-ON482576F7.002E81F9-482576F7.002F4059@zte.com.cn>
In-Reply-To: <OF3A669355.4E545420-ON482576F7.002E81F9-482576F7.002F4059@zte.com.cn>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: en-US
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Cc: "hipsec@ietf.org" <hipsec@ietf.org>, "hipsec-bounces@ietf.org" <hipsec-bounces@ietf.org>
Subject: Re: [Hipsec] Follow-up on 4843bis / ORCHIDv2
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, 31 Mar 2010 15:35:07 -0000

Maybe I'm blunt, but IMHO HIP identifiers are flat. If hierarchical allocat=
ion and management of identifier is a required feature, DNS names look like=
 a better fit than Host Identities / Tags. There's already been some work o=
n name-based sockets, e.g., see this paper from Christian Vogt.

<http://christianvogt.mailup.net/pub/2009/vogt-2009-name-oriented-sockets.p=
df>

wang.jun17@zte.com.cn wrote:
>
>
> Does ORCHID consider any commercial deployment requirements?=20
> If HIP could be commercial deployed, HIP ID should be divided into many s=
ub-pieces
> and allocated to service providers or other organizations .=20
>
>
> Russell Wang

From julienl@qualcomm.com  Wed Mar 31 08:37:28 2010
Return-Path: <julienl@qualcomm.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 8D6813A6A05 for <hipsec@core3.amsl.com>; Wed, 31 Mar 2010 08:37:28 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -105.004
X-Spam-Level: 
X-Spam-Status: No, score=-105.004 tagged_above=-999 required=5 tests=[AWL=0.465, BAYES_00=-2.599, DNS_FROM_OPENWHOIS=1.13, RCVD_IN_DNSWL_MED=-4, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 9Rzvmig3Gi2t for <hipsec@core3.amsl.com>; Wed, 31 Mar 2010 08:37:27 -0700 (PDT)
Received: from wolverine02.qualcomm.com (wolverine02.qualcomm.com [199.106.114.251]) by core3.amsl.com (Postfix) with ESMTP id 6E5433A69DA for <hipsec@ietf.org>; Wed, 31 Mar 2010 08:37:27 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=qualcomm.com; i=julienl@qualcomm.com; q=dns/txt; s=qcdkim; t=1270049879; x=1301585879; h=from:to:date:subject:thread-topic:thread-index: message-id:references:in-reply-to:accept-language: content-language:x-ms-has-attach:x-ms-tnef-correlator: acceptlanguage:content-type:content-transfer-encoding: mime-version:x-ironport-av; z=From:=20"Laganier,=20Julien"=20<julienl@qualcomm.com> |To:=20"miika.komu@hiit.fi"=20<miika.komu@hiit.fi>,=20"hi psec@ietf.org"=0D=0A=09<hipsec@ietf.org>|Date:=20Wed,=203 1=20Mar=202010=2008:37:37=20-0700|Subject:=20RE:=20[Hipse c]=20Follow-up=20on=204843bis=20/=20ORCHIDv2 |Thread-Topic:=20[Hipsec]=20Follow-up=20on=204843bis=20/ =20ORCHIDv2|Thread-Index:=20AcrQiBN+1O4dUXCJTii4kndvGR5Tm wAX71Ng|Message-ID:=20<BF345F63074F8040B58C00A186FCA57F1C 6AA56CD3@NALASEXMB04.na.qualcomm.com>|References:=20<BF34 5F63074F8040B58C00A186FCA57F1C6AA56C57@NALASEXMB04.na.qua lcomm.com>=0D=0A=09<7CC566635CFE364D87DC5803D4712A6C4CE8C 2719F@XCH-NW-10V.nw.nos.boeing.com>=0D=0A=20<4BB2CB81.507 0008@hiit.fi>|In-Reply-To:=20<4BB2CB81.5070008@hiit.fi> |Accept-Language:=20en-US|Content-Language:=20en-US |X-MS-Has-Attach:|X-MS-TNEF-Correlator:|acceptlanguage: =20en-US|Content-Type:=20text/plain=3B=20charset=3D"us-as cii"|Content-Transfer-Encoding:=20quoted-printable |MIME-Version:=201.0|X-IronPort-AV:=20E=3DMcAfee=3Bi=3D"5 400,1158,5937"=3B=20a=3D"37606723"; bh=v4vO7G5n8gPojWQejnfBfmSTQSfHC2stAqoVIMf9/do=; b=MvV8ADZXMKow/O0MDg+Hbs9HDGno8UdqXiRBq4MbHIF3tngkjkDCciMM ZsC629Sfmc10NuawLnALW/EQI8msX0tghFWSQQSTYuafmnCQuo5e3hkwR tFYsug161KMy0iYlmBhUI/JH4VDdKyy5VLXmEqMJpajP3aMLxD6oQ2qqw 0=;
X-IronPort-AV: E=McAfee;i="5400,1158,5937"; a="37606723"
Received: from ironmsg01-r.qualcomm.com ([172.30.46.15]) by wolverine02.qualcomm.com with ESMTP; 31 Mar 2010 08:37:58 -0700
Received: from nasanexhub02.na.qualcomm.com ([10.46.143.120]) by ironmsg01-r.qualcomm.com with ESMTP/TLS/RC4-MD5; 31 Mar 2010 08:37:40 -0700
Received: from nalasexhc02.na.qualcomm.com (10.47.129.186) by nasanexhub02.na.qualcomm.com (10.46.143.120) with Microsoft SMTP Server (TLS) id 8.2.234.1; Wed, 31 Mar 2010 08:37:39 -0700
Received: from NALASEXMB04.na.qualcomm.com ([10.47.7.114]) by nalasexhc02.na.qualcomm.com ([10.47.129.186]) with mapi; Wed, 31 Mar 2010 08:37:39 -0700
From: "Laganier, Julien" <julienl@qualcomm.com>
To: "miika.komu@hiit.fi" <miika.komu@hiit.fi>, "hipsec@ietf.org" <hipsec@ietf.org>
Date: Wed, 31 Mar 2010 08:37:37 -0700
Thread-Topic: [Hipsec] Follow-up on 4843bis / ORCHIDv2
Thread-Index: AcrQiBN+1O4dUXCJTii4kndvGR5TmwAX71Ng
Message-ID: <BF345F63074F8040B58C00A186FCA57F1C6AA56CD3@NALASEXMB04.na.qualcomm.com>
References: <BF345F63074F8040B58C00A186FCA57F1C6AA56C57@NALASEXMB04.na.qualcomm.com> <7CC566635CFE364D87DC5803D4712A6C4CE8C2719F@XCH-NW-10V.nw.nos.boeing.com> <4BB2CB81.5070008@hiit.fi>
In-Reply-To: <4BB2CB81.5070008@hiit.fi>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: en-US
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Subject: Re: [Hipsec] Follow-up on 4843bis / ORCHIDv2
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, 31 Mar 2010 15:37:28 -0000

Miika Komu wrote:
>
> [...]
>=20
> >> 2. HIP WG to allocate OGA Type 1 as SHA1 in 5201bis and keep other
> >> values as unallocated, allocation requiring IETF specification.
> >>
> >> =3D>  question mark: Do we start with SHA-256 instead?
> >
> > I would be happy to delegate the question to the crypto forum or
> > other experts, but my impression is that SHA-1 is already being
> > phased out elsewhere and that existing libraries typically have
> > SHA-256 support.
>=20
> I was following discussion of other people in the IETF and their
> opinion
> seemed to be that...
>=20
> * SHA-256 may be an overkill for sensors
> * Attacks on SHA1 are collision attacks where as we need just the
> preimage property

I agree that we do not care about collision attacks. (And the day where the=
re are practical attacks on SHA1's preimage resistance, the world will have=
 quite a bigger problem than upgrading ORCHIDv2's OGA for HIP ;-)
=20
> For further information, please refer to:
>=20
> http://tools.ietf.org/search/rfc4270

Right, good read.

--julien

From wang.jun17@zte.com.cn  Wed Mar 31 18:10:56 2010
Return-Path: <wang.jun17@zte.com.cn>
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 DA0BC3A67B3; Wed, 31 Mar 2010 18:10:56 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -94.368
X-Spam-Level: 
X-Spam-Status: No, score=-94.368 tagged_above=-999 required=5 tests=[AWL=0.277, BAYES_20=-0.74, DNS_FROM_OPENWHOIS=1.13, HTML_MESSAGE=0.001, MIME_BASE64_TEXT=1.753, MIME_CHARSET_FARAWAY=2.45,  RCVD_DOUBLE_IP_LOOSE=0.76, 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 SpEeMyPLIpkL; Wed, 31 Mar 2010 18:10:55 -0700 (PDT)
Received: from mx6.zte.com.cn (mx6.zte.com.cn [63.218.89.70]) by core3.amsl.com (Postfix) with ESMTP id AC4C43A67A5; Wed, 31 Mar 2010 18:10:54 -0700 (PDT)
Received: from [10.30.17.100] by mx6.zte.com.cn with surfront esmtp id 128642312144290; Thu, 1 Apr 2010 09:09:49 +0800 (CST)
Received: from [192.168.168.1] by [192.168.168.16] with StormMail ESMTP id 29502.4106493463; Thu, 1 Apr 2010 09:08:37 +0800 (CST)
Received: from notes_smtp.zte.com.cn ([10.30.1.239]) by mse2.zte.com.cn with ESMTP id o311BJ1A003685; Thu, 1 Apr 2010 09:11:19 +0800 (CST) (envelope-from wang.jun17@zte.com.cn)
In-Reply-To: <BF345F63074F8040B58C00A186FCA57F1C6AA56CD2@NALASEXMB04.na.qualcomm.com>
To: "Laganier, Julien" <julienl@qualcomm.com>
MIME-Version: 1.0
X-Mailer: Lotus Notes Release 6.5.4 March 27, 2005
Message-ID: <OFAF998C42.F6DDA65F-ON482576F8.00049E68-482576F8.00068525@zte.com.cn>
From: wang.jun17@zte.com.cn
Date: Thu, 1 Apr 2010 09:11:11 +0800
X-MIMETrack: Serialize by Router on notes_smtp/zte_ltd(Release 6.5.4|March 27, 2005) at 2010-04-01 09:11:18, Serialize complete at 2010-04-01 09:11:18
Content-Type: multipart/alternative; boundary="=_alternative 00068522482576F8_="
X-MAIL: mse2.zte.com.cn o311BJ1A003685
Cc: "hipsec@ietf.org" <hipsec@ietf.org>, "hipsec-bounces@ietf.org" <hipsec-bounces@ietf.org>
Subject: Re: [Hipsec] Follow-up on 4843bis / ORCHIDv2
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, 01 Apr 2010 01:10:57 -0000

This is a multipart message in MIME format.
--=_alternative 00068522482576F8_=
Content-Type: text/plain; charset="GB2312"
Content-Transfer-Encoding: base64

VGhlIGZsYXQgYXNzdW1wdGlvbiBtYXliZSBlbm91Z2ggZm9yIGV4cGVyaW1lbnQsIGJ1dCB3ZSBh
cmUgcHVzaGluZyBISVAgDQppbnRvIGEgUFMgc3RhdHVzLCBzbyBJIHRoaW5rIHdlIHNob3VsZCBt
YWtlIGl0IGlzIHJlYWR5IGZvciBjb21tZXJjaWFsLg0KQXNzdW1pbmcgdGhhdCBhbiBJU1Agd2Fu
dCB0byBkZXBsb3kgYSBISVAgbmV0d29yaywgaGUgbXVzdCBjb25zaWRlciBvZiANCmludGVyd29y
a2luZyB3aXRoIElQVjYgbmV0d29yaywgc28gdGhlIGhpcCBwcmVmaXggbXVzdCBiZSBhbm5vdWNl
ZCBhcyANCm5vcm1hbCBpcHY2IHByZWZpeCBhbW9uZ3N0IHRoZSByb3V0ZXJzLiBJZiB0aGVyZSBh
cmUgbW9yZSB0aGFuIG9uZSBJU1AgDQpoYXZlIGRlcGxveWVkIGluZGVwZW5kZW50IHB1YmxpYyBo
aXAgbmV0d29yaywgdGhlIGZsYXQgaGlwIGFkZHJlc3Mgc3BhY2UgDQp3aWxsIGludHJvZHVjZSBy
b3V0aW5nIGNvbmZsaWN0cy4NClNvIG1heWJlIGEgaGlwIGFkcmVzcyBhc3NpZ25tZW50IGF1dGhv
cml0eSBpcyByZXF1aXJlZCwgYW5kIHdoaWNoIGJpdHMgDQpyZXByZXNlbnQgdGhlIG9yZ2FuaXph
dGlvbiBzaG91bGQgYmUgZXhwbGljaXRseSBkZWZpbmVkLg0KT3IgbWF5YmUgSSdtIHdyb25nPw0K
DQpSdXNzZWxsIFdhbmcNCg0KDQoNCg0KDQoiTGFnYW5pZXIsIEp1bGllbiIgPGp1bGllbmxAcXVh
bGNvbW0uY29tPiANCjIwMTAtMDMtMzEgMjM6MzUNCg0KytW8/sjLDQoid2FuZy5qdW4xN0B6dGUu
Y29tLmNuIiA8d2FuZy5qdW4xN0B6dGUuY29tLmNuPiwgVmFyam9uZW4gU2FtdSANCjxzYW11LnZh
cmpvbmVuQGhpaXQuZmk+DQqzrcvNDQoiaGlwc2VjQGlldGYub3JnIiA8aGlwc2VjQGlldGYub3Jn
PiwgImhpcHNlYy1ib3VuY2VzQGlldGYub3JnIiANCjxoaXBzZWMtYm91bmNlc0BpZXRmLm9yZz4N
Ctb3zOINClJFOiBbSGlwc2VjXSBGb2xsb3ctdXAgb24gNDg0M2JpcyAvIE9SQ0hJRHYyDQoNCg0K
DQoNCg0KDQpNYXliZSBJJ20gYmx1bnQsIGJ1dCBJTUhPIEhJUCBpZGVudGlmaWVycyBhcmUgZmxh
dC4gSWYgaGllcmFyY2hpY2FsIA0KYWxsb2NhdGlvbiBhbmQgbWFuYWdlbWVudCBvZiBpZGVudGlm
aWVyIGlzIGEgcmVxdWlyZWQgZmVhdHVyZSwgRE5TIG5hbWVzIA0KbG9vayBsaWtlIGEgYmV0dGVy
IGZpdCB0aGFuIEhvc3QgSWRlbnRpdGllcyAvIFRhZ3MuIFRoZXJlJ3MgYWxyZWFkeSBiZWVuIA0K
c29tZSB3b3JrIG9uIG5hbWUtYmFzZWQgc29ja2V0cywgZS5nLiwgc2VlIHRoaXMgcGFwZXIgZnJv
bSBDaHJpc3RpYW4gVm9ndC4NCg0KPA0KaHR0cDovL2NocmlzdGlhbnZvZ3QubWFpbHVwLm5ldC9w
dWIvMjAwOS92b2d0LTIwMDktbmFtZS1vcmllbnRlZC1zb2NrZXRzLnBkZg0KPg0KDQp3YW5nLmp1
bjE3QHp0ZS5jb20uY24gd3JvdGU6DQo+DQo+DQo+IERvZXMgT1JDSElEIGNvbnNpZGVyIGFueSBj
b21tZXJjaWFsIGRlcGxveW1lbnQgcmVxdWlyZW1lbnRzPyANCj4gSWYgSElQIGNvdWxkIGJlIGNv
bW1lcmNpYWwgZGVwbG95ZWQsIEhJUCBJRCBzaG91bGQgYmUgZGl2aWRlZCBpbnRvIG1hbnkgDQpz
dWItcGllY2VzDQo+IGFuZCBhbGxvY2F0ZWQgdG8gc2VydmljZSBwcm92aWRlcnMgb3Igb3RoZXIg
b3JnYW5pemF0aW9ucyAuIA0KPg0KPg0KPiBSdXNzZWxsIFdhbmcNCg0KDQoNCg0KDQotLS0tLS0t
LS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLQ0KWlRFIElu
Zm9ybWF0aW9uIFNlY3VyaXR5IE5vdGljZTogVGhlIGluZm9ybWF0aW9uIGNvbnRhaW5lZCBpbiB0
aGlzIG1haWwgaXMgc29sZWx5IHByb3BlcnR5IG9mIHRoZSBzZW5kZXIncyBvcmdhbml6YXRpb24u
IFRoaXMgbWFpbCBjb21tdW5pY2F0aW9uIGlzIGNvbmZpZGVudGlhbC4gUmVjaXBpZW50cyBuYW1l
ZCBhYm92ZSBhcmUgb2JsaWdhdGVkIHRvIG1haW50YWluIHNlY3JlY3kgYW5kIGFyZSBub3QgcGVy
bWl0dGVkIHRvIGRpc2Nsb3NlIHRoZSBjb250ZW50cyBvZiB0aGlzIGNvbW11bmljYXRpb24gdG8g
b3RoZXJzLg0KVGhpcyBlbWFpbCBhbmQgYW55IGZpbGVzIHRyYW5zbWl0dGVkIHdpdGggaXQgYXJl
IGNvbmZpZGVudGlhbCBhbmQgaW50ZW5kZWQgc29sZWx5IGZvciB0aGUgdXNlIG9mIHRoZSBpbmRp
dmlkdWFsIG9yIGVudGl0eSB0byB3aG9tIHRoZXkgYXJlIGFkZHJlc3NlZC4gSWYgeW91IGhhdmUg
cmVjZWl2ZWQgdGhpcyBlbWFpbCBpbiBlcnJvciBwbGVhc2Ugbm90aWZ5IHRoZSBvcmlnaW5hdG9y
IG9mIHRoZSBtZXNzYWdlLiBBbnkgdmlld3MgZXhwcmVzc2VkIGluIHRoaXMgbWVzc2FnZSBhcmUg
dGhvc2Ugb2YgdGhlIGluZGl2aWR1YWwgc2VuZGVyLg0KVGhpcyBtZXNzYWdlIGhhcyBiZWVuIHNj
YW5uZWQgZm9yIHZpcnVzZXMgYW5kIFNwYW0gYnkgWlRFIEFudGktU3BhbSBzeXN0ZW0uDQo=
--=_alternative 00068522482576F8_=
Content-Type: text/html; charset="GB2312"
Content-Transfer-Encoding: base64

DQo8YnI+PGZvbnQgc2l6ZT0yIGZhY2U9InNhbnMtc2VyaWYiPlRoZSBmbGF0IGFzc3VtcHRpb24g
bWF5YmUgZW5vdWdoIGZvcg0KZXhwZXJpbWVudCwgYnV0IHdlIGFyZSBwdXNoaW5nIEhJUCBpbnRv
IGEgUFMgc3RhdHVzLCBzbyBJIHRoaW5rIHdlIHNob3VsZA0KbWFrZSBpdCBpcyByZWFkeSBmb3Ig
Y29tbWVyY2lhbC48L2ZvbnQ+DQo8cD48Zm9udCBzaXplPTIgZmFjZT0ic2Fucy1zZXJpZiI+QXNz
dW1pbmcgdGhhdCBhbiBJU1Agd2FudCB0byBkZXBsb3kgYQ0KSElQIG5ldHdvcmssIGhlIG11c3Qg
Y29uc2lkZXIgb2YgaW50ZXJ3b3JraW5nIHdpdGggSVBWNiBuZXR3b3JrLCBzbyB0aGUNCmhpcCBw
cmVmaXggbXVzdCBiZSBhbm5vdWNlZCBhcyBub3JtYWwgaXB2NiBwcmVmaXggYW1vbmdzdCB0aGUg
cm91dGVycy4NCklmIHRoZXJlIGFyZSBtb3JlIHRoYW4gb25lIElTUCBoYXZlIGRlcGxveWVkIGlu
ZGVwZW5kZW50IHB1YmxpYyBoaXAgbmV0d29yaywNCnRoZSBmbGF0IGhpcCBhZGRyZXNzIHNwYWNl
IHdpbGwgaW50cm9kdWNlIHJvdXRpbmcgY29uZmxpY3RzLjwvZm9udD4NCjxwPjxmb250IHNpemU9
MiBmYWNlPSJzYW5zLXNlcmlmIj5TbyBtYXliZSBhIGhpcCBhZHJlc3MgYXNzaWdubWVudCBhdXRo
b3JpdHkNCmlzIHJlcXVpcmVkLCBhbmQgd2hpY2ggYml0cyByZXByZXNlbnQgdGhlIG9yZ2FuaXph
dGlvbiBzaG91bGQgYmUgZXhwbGljaXRseQ0KZGVmaW5lZC48L2ZvbnQ+DQo8cD48Zm9udCBzaXpl
PTIgZmFjZT0ic2Fucy1zZXJpZiI+T3IgbWF5YmUgSSdtIHdyb25nPzwvZm9udD4NCjxwPg0KPHA+
PGZvbnQgc2l6ZT0yIGZhY2U9InNhbnMtc2VyaWYiPlJ1c3NlbGwgV2FuZzwvZm9udD4NCjxicj48
Zm9udCBzaXplPTIgZmFjZT0ic2Fucy1zZXJpZiI+PGJyPg0KPC9mb250Pg0KPGJyPg0KPGJyPg0K
PGJyPg0KPHRhYmxlIHdpZHRoPTEwMCU+DQo8dHIgdmFsaWduPXRvcD4NCjx0ZCB3aWR0aD0zNCU+
PGZvbnQgc2l6ZT0xIGZhY2U9InNhbnMtc2VyaWYiPjxiPiZxdW90O0xhZ2FuaWVyLCBKdWxpZW4m
cXVvdDsNCiZsdDtqdWxpZW5sQHF1YWxjb21tLmNvbSZndDs8L2I+IDwvZm9udD4NCjxwPjxmb250
IHNpemU9MSBmYWNlPSJzYW5zLXNlcmlmIj4yMDEwLTAzLTMxIDIzOjM1PC9mb250Pg0KPHRkIHdp
ZHRoPTY1JT4NCjx0YWJsZSB3aWR0aD0xMDAlPg0KPHRyIHZhbGlnbj10b3A+DQo8dGQ+DQo8ZGl2
IGFsaWduPXJpZ2h0Pjxmb250IHNpemU9MSBmYWNlPSJzYW5zLXNlcmlmIj7K1bz+yMs8L2ZvbnQ+
PC9kaXY+DQo8dGQ+PGZvbnQgc2l6ZT0xIGZhY2U9InNhbnMtc2VyaWYiPiZxdW90O3dhbmcuanVu
MTdAenRlLmNvbS5jbiZxdW90OyAmbHQ7d2FuZy5qdW4xN0B6dGUuY29tLmNuJmd0OywNClZhcmpv
bmVuIFNhbXUgJmx0O3NhbXUudmFyam9uZW5AaGlpdC5maSZndDs8L2ZvbnQ+DQo8dHIgdmFsaWdu
PXRvcD4NCjx0ZD4NCjxkaXYgYWxpZ249cmlnaHQ+PGZvbnQgc2l6ZT0xIGZhY2U9InNhbnMtc2Vy
aWYiPrOty808L2ZvbnQ+PC9kaXY+DQo8dGQ+PGZvbnQgc2l6ZT0xIGZhY2U9InNhbnMtc2VyaWYi
PiZxdW90O2hpcHNlY0BpZXRmLm9yZyZxdW90OyAmbHQ7aGlwc2VjQGlldGYub3JnJmd0OywNCiZx
dW90O2hpcHNlYy1ib3VuY2VzQGlldGYub3JnJnF1b3Q7ICZsdDtoaXBzZWMtYm91bmNlc0BpZXRm
Lm9yZyZndDs8L2ZvbnQ+DQo8dHIgdmFsaWduPXRvcD4NCjx0ZD4NCjxkaXYgYWxpZ249cmlnaHQ+
PGZvbnQgc2l6ZT0xIGZhY2U9InNhbnMtc2VyaWYiPtb3zOI8L2ZvbnQ+PC9kaXY+DQo8dGQ+PGZv
bnQgc2l6ZT0xIGZhY2U9InNhbnMtc2VyaWYiPlJFOiBbSGlwc2VjXSBGb2xsb3ctdXAgb24gNDg0
M2JpcyAvDQpPUkNISUR2MjwvZm9udD48L3RhYmxlPg0KPGJyPg0KPHRhYmxlPg0KPHRyIHZhbGln
bj10b3A+DQo8dGQ+DQo8dGQ+PC90YWJsZT4NCjxicj48L3RhYmxlPg0KPGJyPg0KPGJyPg0KPGJy
Pjxmb250IHNpemU9Mj48dHQ+TWF5YmUgSSdtIGJsdW50LCBidXQgSU1ITyBISVAgaWRlbnRpZmll
cnMgYXJlIGZsYXQuDQpJZiBoaWVyYXJjaGljYWwgYWxsb2NhdGlvbiBhbmQgbWFuYWdlbWVudCBv
ZiBpZGVudGlmaWVyIGlzIGEgcmVxdWlyZWQgZmVhdHVyZSwNCkROUyBuYW1lcyBsb29rIGxpa2Ug
YSBiZXR0ZXIgZml0IHRoYW4gSG9zdCBJZGVudGl0aWVzIC8gVGFncy4gVGhlcmUncyBhbHJlYWR5
DQpiZWVuIHNvbWUgd29yayBvbiBuYW1lLWJhc2VkIHNvY2tldHMsIGUuZy4sIHNlZSB0aGlzIHBh
cGVyIGZyb20gQ2hyaXN0aWFuDQpWb2d0Ljxicj4NCjxicj4NCiZsdDtodHRwOi8vY2hyaXN0aWFu
dm9ndC5tYWlsdXAubmV0L3B1Yi8yMDA5L3ZvZ3QtMjAwOS1uYW1lLW9yaWVudGVkLXNvY2tldHMu
cGRmJmd0Ozxicj4NCjxicj4NCndhbmcuanVuMTdAenRlLmNvbS5jbiB3cm90ZTo8YnI+DQomZ3Q7
PGJyPg0KJmd0Ozxicj4NCiZndDsgRG9lcyBPUkNISUQgY29uc2lkZXIgYW55IGNvbW1lcmNpYWwg
ZGVwbG95bWVudCByZXF1aXJlbWVudHM/IDxicj4NCiZndDsgSWYgSElQIGNvdWxkIGJlIGNvbW1l
cmNpYWwgZGVwbG95ZWQsIEhJUCBJRCBzaG91bGQgYmUgZGl2aWRlZCBpbnRvDQptYW55IHN1Yi1w
aWVjZXM8YnI+DQomZ3Q7IGFuZCBhbGxvY2F0ZWQgdG8gc2VydmljZSBwcm92aWRlcnMgb3Igb3Ro
ZXIgb3JnYW5pemF0aW9ucyAuIDxicj4NCiZndDs8YnI+DQomZ3Q7PGJyPg0KJmd0OyBSdXNzZWxs
IFdhbmc8YnI+DQo8YnI+DQo8L3R0PjwvZm9udD4NCjxicj4NCjxicj48cHJlPg0KLS0tLS0tLS0t
LS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0NClpURSZuYnNw
O0luZm9ybWF0aW9uJm5ic3A7U2VjdXJpdHkmbmJzcDtOb3RpY2U6Jm5ic3A7VGhlJm5ic3A7aW5m
b3JtYXRpb24mbmJzcDtjb250YWluZWQmbmJzcDtpbiZuYnNwO3RoaXMmbmJzcDttYWlsJm5ic3A7
aXMmbmJzcDtzb2xlbHkmbmJzcDtwcm9wZXJ0eSZuYnNwO29mJm5ic3A7dGhlJm5ic3A7c2VuZGVy
J3MmbmJzcDtvcmdhbml6YXRpb24uJm5ic3A7VGhpcyZuYnNwO21haWwmbmJzcDtjb21tdW5pY2F0
aW9uJm5ic3A7aXMmbmJzcDtjb25maWRlbnRpYWwuJm5ic3A7UmVjaXBpZW50cyZuYnNwO25hbWVk
Jm5ic3A7YWJvdmUmbmJzcDthcmUmbmJzcDtvYmxpZ2F0ZWQmbmJzcDt0byZuYnNwO21haW50YWlu
Jm5ic3A7c2VjcmVjeSZuYnNwO2FuZCZuYnNwO2FyZSZuYnNwO25vdCZuYnNwO3Blcm1pdHRlZCZu
YnNwO3RvJm5ic3A7ZGlzY2xvc2UmbmJzcDt0aGUmbmJzcDtjb250ZW50cyZuYnNwO29mJm5ic3A7
dGhpcyZuYnNwO2NvbW11bmljYXRpb24mbmJzcDt0byZuYnNwO290aGVycy4NClRoaXMmbmJzcDtl
bWFpbCZuYnNwO2FuZCZuYnNwO2FueSZuYnNwO2ZpbGVzJm5ic3A7dHJhbnNtaXR0ZWQmbmJzcDt3
aXRoJm5ic3A7aXQmbmJzcDthcmUmbmJzcDtjb25maWRlbnRpYWwmbmJzcDthbmQmbmJzcDtpbnRl
bmRlZCZuYnNwO3NvbGVseSZuYnNwO2ZvciZuYnNwO3RoZSZuYnNwO3VzZSZuYnNwO29mJm5ic3A7
dGhlJm5ic3A7aW5kaXZpZHVhbCZuYnNwO29yJm5ic3A7ZW50aXR5Jm5ic3A7dG8mbmJzcDt3aG9t
Jm5ic3A7dGhleSZuYnNwO2FyZSZuYnNwO2FkZHJlc3NlZC4mbmJzcDtJZiZuYnNwO3lvdSZuYnNw
O2hhdmUmbmJzcDtyZWNlaXZlZCZuYnNwO3RoaXMmbmJzcDtlbWFpbCZuYnNwO2luJm5ic3A7ZXJy
b3ImbmJzcDtwbGVhc2UmbmJzcDtub3RpZnkmbmJzcDt0aGUmbmJzcDtvcmlnaW5hdG9yJm5ic3A7
b2YmbmJzcDt0aGUmbmJzcDttZXNzYWdlLiZuYnNwO0FueSZuYnNwO3ZpZXdzJm5ic3A7ZXhwcmVz
c2VkJm5ic3A7aW4mbmJzcDt0aGlzJm5ic3A7bWVzc2FnZSZuYnNwO2FyZSZuYnNwO3Rob3NlJm5i
c3A7b2YmbmJzcDt0aGUmbmJzcDtpbmRpdmlkdWFsJm5ic3A7c2VuZGVyLg0KVGhpcyZuYnNwO21l
c3NhZ2UmbmJzcDtoYXMmbmJzcDtiZWVuJm5ic3A7c2Nhbm5lZCZuYnNwO2ZvciZuYnNwO3ZpcnVz
ZXMmbmJzcDthbmQmbmJzcDtTcGFtJm5ic3A7YnkmbmJzcDtaVEUmbmJzcDtBbnRpLVNwYW0mbmJz
cDtzeXN0ZW0uDQo8L3ByZT4=
--=_alternative 00068522482576F8_=--


From julienl@qualcomm.com  Wed Mar 31 19:09:23 2010
Return-Path: <julienl@qualcomm.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 2C13A3A6916; Wed, 31 Mar 2010 19:09:23 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -105.159
X-Spam-Level: 
X-Spam-Status: No, score=-105.159 tagged_above=-999 required=5 tests=[AWL=0.309, BAYES_00=-2.599, DNS_FROM_OPENWHOIS=1.13, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_MED=-4, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id PY1m0WI97ZH8; Wed, 31 Mar 2010 19:09:21 -0700 (PDT)
Received: from wolverine02.qualcomm.com (wolverine02.qualcomm.com [199.106.114.251]) by core3.amsl.com (Postfix) with ESMTP id D29E43A6890; Wed, 31 Mar 2010 19:09:20 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=qualcomm.com; i=julienl@qualcomm.com; q=dns/txt; s=qcdkim; t=1270087793; x=1301623793; h=from:to:cc:date:subject:thread-topic:thread-index: message-id:reply-to:accept-language:content-language: x-ms-has-attach:x-ms-tnef-correlator:acceptlanguage: content-type:mime-version; z=From:=20"Laganier,=20Julien"=20<julienl@qualcomm.com> |To:=20"wang.jun17@zte.com.cn"=20<wang.jun17@zte.com.cn> |CC:=20"hipsec@ietf.org"=20<hipsec@ietf.org>,=20"hipsec-b ounces@ietf.org"=0D=0A=09<hipsec-bounces@ietf.org>,=20Var jonen=20Samu=20<samu.varjonen@hiit.fi>|Date:=20Wed,=2031 =20Mar=202010=2019:09:44=20-0700|Subject:=20RE:=20[Hipsec ]=20Follow-up=20on=204843bis=20/=20ORCHIDv2|Thread-Topic: =20[Hipsec]=20Follow-up=20on=204843bis=20/=20ORCHIDv2 |Thread-Index:=20AcrRQGlCu98+2pfASoC7ZOf5WxOtyQ=3D=3D |Message-ID:=20<BF345F63074F8040B58C00A186FCA57F1C6A93942 2@NALASEXMB04.na.qualcomm.com>|Reply-To:=20"Laganier,=20J ulien"=20<julienl@qualcomm.com>|Accept-Language:=20en-US |Content-Language:=20en-US|X-MS-Has-Attach: |X-MS-TNEF-Correlator:|acceptlanguage:=20en-US |Content-Type:=20multipart/alternative=3B=0D=0A=09boundar y=3D"_000_BF345F63074F8040B58C00A186FCA57F1C6A939422NALAS EXMB04na_"|MIME-Version:=201.0; bh=HQxTiJtsAFgOcmkwE1vxOAr/I9DsUFeX6PQl0+LpCiM=; b=ynjw2Cy8En0mSI5BKTaV4gl0o+rBWT3Io8JemOXNg/7kZQ0o4IFC5aqo C6QeGaEF4kd/omjM457yUpLTDI/GLUY6CMHh9q6xufoKyy914pDaalZ4K nYjaXWvv9A5ZZtTTGS9Z/qQ046m3Xers8eGkIfN5Ezpa68jeGVYLqTsW4 Q=;
X-IronPort-AV: E=McAfee;i="5400,1158,5937"; a="37654382"
Received: from ironmsg01-r.qualcomm.com ([172.30.46.15]) by wolverine02.qualcomm.com with ESMTP; 31 Mar 2010 19:09:52 -0700
X-IronPort-AV: E=Sophos;i="4.51,343,1267430400"; d="scan'208,217";a="3712869"
Received: from nasanexhub02.na.qualcomm.com ([10.46.143.120]) by ironmsg01-r.qualcomm.com with ESMTP/TLS/RC4-MD5; 31 Mar 2010 19:09:52 -0700
Received: from nalasexhc03.na.qualcomm.com (10.47.129.194) by nasanexhub02.na.qualcomm.com (10.46.143.120) with Microsoft SMTP Server (TLS) id 8.2.234.1; Wed, 31 Mar 2010 19:09:51 -0700
Received: from NALASEXMB04.na.qualcomm.com ([10.47.7.114]) by nalasexhc03.na.qualcomm.com ([10.47.129.194]) with mapi; Wed, 31 Mar 2010 19:09:51 -0700
From: "Laganier, Julien" <julienl@qualcomm.com>
To: "wang.jun17@zte.com.cn" <wang.jun17@zte.com.cn>
Date: Wed, 31 Mar 2010 19:09:44 -0700
Thread-Topic: [Hipsec] Follow-up on 4843bis / ORCHIDv2
Thread-Index: AcrRQGlCu98+2pfASoC7ZOf5WxOtyQ==
Message-ID: <BF345F63074F8040B58C00A186FCA57F1C6A939422@NALASEXMB04.na.qualcomm.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: en-US
Content-Type: multipart/alternative; boundary="_000_BF345F63074F8040B58C00A186FCA57F1C6A939422NALASEXMB04na_"
MIME-Version: 1.0
Cc: "hipsec@ietf.org" <hipsec@ietf.org>, "hipsec-bounces@ietf.org" <hipsec-bounces@ietf.org>
Subject: Re: [Hipsec] Follow-up on 4843bis / ORCHIDv2
X-BeenThere: hipsec@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
Reply-To: "Laganier, Julien" <julienl@qualcomm.com>
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, 01 Apr 2010 02:09:23 -0000

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

V2hhdCB5b3UncmUgZGVzY3JpYmluZyBpcyBiZWluZyB3b3JrZWQgb24gaW4gdGhlIExJU1AgV0cu
DQoNCi0tanVsaWVuDQoNCg0KDQpfX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fXw0KT24g
TWFyIDMxLCAyMDEwIDY6MTEgUE0sIHdhbmcuanVuMTdAenRlLmNvbS5jbiA8d2FuZy5qdW4xN0B6
dGUuY29tLmNuPiB3cm90ZToNCg0KDQpUaGUgZmxhdCBhc3N1bXB0aW9uIG1heWJlIGVub3VnaCBm
b3IgZXhwZXJpbWVudCwgYnV0IHdlIGFyZSBwdXNoaW5nIEhJUCBpbnRvIGEgUFMgc3RhdHVzLCBz
byBJIHRoaW5rIHdlIHNob3VsZCBtYWtlIGl0IGlzIHJlYWR5IGZvciBjb21tZXJjaWFsLg0KDQpB
c3N1bWluZyB0aGF0IGFuIElTUCB3YW50IHRvIGRlcGxveSBhIEhJUCBuZXR3b3JrLCBoZSBtdXN0
IGNvbnNpZGVyIG9mIGludGVyd29ya2luZyB3aXRoIElQVjYgbmV0d29yaywgc28gdGhlIGhpcCBw
cmVmaXggbXVzdCBiZSBhbm5vdWNlZCBhcyBub3JtYWwgaXB2NiBwcmVmaXggYW1vbmdzdCB0aGUg
cm91dGVycy4gSWYgdGhlcmUgYXJlIG1vcmUgdGhhbiBvbmUgSVNQIGhhdmUgZGVwbG95ZWQgaW5k
ZXBlbmRlbnQgcHVibGljIGhpcCBuZXR3b3JrLCB0aGUgZmxhdCBoaXAgYWRkcmVzcyBzcGFjZSB3
aWxsIGludHJvZHVjZSByb3V0aW5nIGNvbmZsaWN0cy4NCg0KU28gbWF5YmUgYSBoaXAgYWRyZXNz
IGFzc2lnbm1lbnQgYXV0aG9yaXR5IGlzIHJlcXVpcmVkLCBhbmQgd2hpY2ggYml0cyByZXByZXNl
bnQgdGhlIG9yZ2FuaXphdGlvbiBzaG91bGQgYmUgZXhwbGljaXRseSBkZWZpbmVkLg0KDQpPciBt
YXliZSBJJ20gd3Jvbmc/DQoNClJ1c3NlbGwgV2FuZw0KDQoNCg0KDQoNCiJMYWdhbmllciwgSnVs
aWVuIiA8anVsaWVubEBxdWFsY29tbS5jb20+DQoNCjIwMTAtMDMtMzEgMjM6MzUNCg0KDQrmlLbk
u7bkuroNCiAgICAgICAgIndhbmcuanVuMTdAenRlLmNvbS5jbiIgPHdhbmcuanVuMTdAenRlLmNv
bS5jbj4sIFZhcmpvbmVuIFNhbXUgPHNhbXUudmFyam9uZW5AaGlpdC5maT4NCuaKhOmAgQ0KICAg
ICAgICAiaGlwc2VjQGlldGYub3JnIiA8aGlwc2VjQGlldGYub3JnPiwgImhpcHNlYy1ib3VuY2Vz
QGlldGYub3JnIiA8aGlwc2VjLWJvdW5jZXNAaWV0Zi5vcmc+DQrkuLvpopgNCiAgICAgICAgUkU6
IFtIaXBzZWNdIEZvbGxvdy11cCBvbiA0ODQzYmlzIC8gT1JDSElEdjINCg0KDQoNCg0KDQoNCg0K
TWF5YmUgSSdtIGJsdW50LCBidXQgSU1ITyBISVAgaWRlbnRpZmllcnMgYXJlIGZsYXQuIElmIGhp
ZXJhcmNoaWNhbCBhbGxvY2F0aW9uIGFuZCBtYW5hZ2VtZW50IG9mIGlkZW50aWZpZXIgaXMgYSBy
ZXF1aXJlZCBmZWF0dXJlLCBETlMgbmFtZXMgbG9vayBsaWtlIGEgYmV0dGVyIGZpdCB0aGFuIEhv
c3QgSWRlbnRpdGllcyAvIFRhZ3MuIFRoZXJlJ3MgYWxyZWFkeSBiZWVuIHNvbWUgd29yayBvbiBu
YW1lLWJhc2VkIHNvY2tldHMsIGUuZy4sIHNlZSB0aGlzIHBhcGVyIGZyb20gQ2hyaXN0aWFuIFZv
Z3QuDQoNCjxodHRwOi8vY2hyaXN0aWFudm9ndC5tYWlsdXAubmV0L3B1Yi8yMDA5L3ZvZ3QtMjAw
OS1uYW1lLW9yaWVudGVkLXNvY2tldHMucGRmPg0KDQp3YW5nLmp1bjE3QHp0ZS5jb20uY24gd3Jv
dGU6DQo+DQo+DQo+IERvZXMgT1JDSElEIGNvbnNpZGVyIGFueSBjb21tZXJjaWFsIGRlcGxveW1l
bnQgcmVxdWlyZW1lbnRzPw0KPiBJZiBISVAgY291bGQgYmUgY29tbWVyY2lhbCBkZXBsb3llZCwg
SElQIElEIHNob3VsZCBiZSBkaXZpZGVkIGludG8gbWFueSBzdWItcGllY2VzDQo+IGFuZCBhbGxv
Y2F0ZWQgdG8gc2VydmljZSBwcm92aWRlcnMgb3Igb3RoZXIgb3JnYW5pemF0aW9ucyAuDQo+DQo+
DQo+IFJ1c3NlbGwgV2FuZw0KDQoNCg0KDQotLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0t
LS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLQ0KWlRFIEluZm9ybWF0aW9uIFNlY3VyaXR5IE5vdGlj
ZTogVGhlIGluZm9ybWF0aW9uIGNvbnRhaW5lZCBpbiB0aGlzIG1haWwgaXMgc29sZWx5IHByb3Bl
cnR5IG9mIHRoZSBzZW5kZXIncyBvcmdhbml6YXRpb24uIFRoaXMgbWFpbCBjb21tdW5pY2F0aW9u
IGlzIGNvbmZpZGVudGlhbC4gUmVjaXBpZW50cyBuYW1lZCBhYm92ZSBhcmUgb2JsaWdhdGVkIHRv
IG1haW50YWluIHNlY3JlY3kgYW5kIGFyZSBub3QgcGVybWl0dGVkIHRvIGRpc2Nsb3NlIHRoZSBj
b250ZW50cyBvZiB0aGlzIGNvbW11bmljYXRpb24gdG8gb3RoZXJzLg0KVGhpcyBlbWFpbCBhbmQg
YW55IGZpbGVzIHRyYW5zbWl0dGVkIHdpdGggaXQgYXJlIGNvbmZpZGVudGlhbCBhbmQgaW50ZW5k
ZWQgc29sZWx5IGZvciB0aGUgdXNlIG9mIHRoZSBpbmRpdmlkdWFsIG9yIGVudGl0eSB0byB3aG9t
IHRoZXkgYXJlIGFkZHJlc3NlZC4gSWYgeW91IGhhdmUgcmVjZWl2ZWQgdGhpcyBlbWFpbCBpbiBl
cnJvciBwbGVhc2Ugbm90aWZ5IHRoZSBvcmlnaW5hdG9yIG9mIHRoZSBtZXNzYWdlLiBBbnkgdmll
d3MgZXhwcmVzc2VkIGluIHRoaXMgbWVzc2FnZSBhcmUgdGhvc2Ugb2YgdGhlIGluZGl2aWR1YWwg
c2VuZGVyLg0KVGhpcyBtZXNzYWdlIGhhcyBiZWVuIHNjYW5uZWQgZm9yIHZpcnVzZXMgYW5kIFNw
YW0gYnkgWlRFIEFudGktU3BhbSBzeXMNCg0K

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

V2hhdCB5b3UncmUgZGVzY3JpYmluZyBpcyBiZWluZyB3b3JrZWQgb24gaW4gdGhlIExJU1AgV0cu
PGJyPjxicj4tLWp1bGllbjxicj48YnI+PHNwYW4gc3R5bGU9ImZvbnQtZmFtaWx5OlByZWx1ZGUs
IFZlcmRhbmEsIHNhbi1zZXJpZjsiPjxicj48YnI+PC9zcGFuPjxzcGFuIHN0eWxlPSJjb2xvcjpu
YXZ5OyBmb250LWZhbWlseTpQcmVsdWRlLCBWZXJkYW5hLCBzYW4tc2VyaWY7ICI+PGhyIGFsaWdu
PSJsZWZ0IiBzdHlsZT0id2lkdGg6NzUlIj5PbiBNYXIgMzEsIDIwMTAgNjoxMSBQTSwgd2FuZy5q
dW4xN0B6dGUuY29tLmNuICZsdDt3YW5nLmp1bjE3QHp0ZS5jb20uY24mZ3Q7IHdyb3RlOiA8YnI+
PGJyPg0KPGJyPg0KPGZvbnQgc2l6ZT0iMiIgZmFjZT0ic2Fucy1zZXJpZiI+VGhlIGZsYXQgYXNz
dW1wdGlvbiBtYXliZSBlbm91Z2ggZm9yIGV4cGVyaW1lbnQsIGJ1dCB3ZSBhcmUgcHVzaGluZyBI
SVAgaW50byBhIFBTIHN0YXR1cywgc28gSSB0aGluayB3ZSBzaG91bGQgbWFrZSBpdCBpcyByZWFk
eSBmb3IgY29tbWVyY2lhbC48L2ZvbnQ+DQo8cD48Zm9udCBzaXplPSIyIiBmYWNlPSJzYW5zLXNl
cmlmIj5Bc3N1bWluZyB0aGF0IGFuIElTUCB3YW50IHRvIGRlcGxveSBhIEhJUCBuZXR3b3JrLCBo
ZSBtdXN0IGNvbnNpZGVyIG9mIGludGVyd29ya2luZyB3aXRoIElQVjYgbmV0d29yaywgc28gdGhl
IGhpcCBwcmVmaXggbXVzdCBiZSBhbm5vdWNlZCBhcyBub3JtYWwgaXB2NiBwcmVmaXggYW1vbmdz
dCB0aGUgcm91dGVycy4gSWYgdGhlcmUgYXJlIG1vcmUgdGhhbiBvbmUgSVNQIGhhdmUgZGVwbG95
ZWQNCiBpbmRlcGVuZGVudCBwdWJsaWMgaGlwIG5ldHdvcmssIHRoZSBmbGF0IGhpcCBhZGRyZXNz
IHNwYWNlIHdpbGwgaW50cm9kdWNlIHJvdXRpbmcgY29uZmxpY3RzLjwvZm9udD4NCjwvcD4NCjxw
Pjxmb250IHNpemU9IjIiIGZhY2U9InNhbnMtc2VyaWYiPlNvIG1heWJlIGEgaGlwIGFkcmVzcyBh
c3NpZ25tZW50IGF1dGhvcml0eSBpcyByZXF1aXJlZCwgYW5kIHdoaWNoIGJpdHMgcmVwcmVzZW50
IHRoZSBvcmdhbml6YXRpb24gc2hvdWxkIGJlIGV4cGxpY2l0bHkgZGVmaW5lZC48L2ZvbnQ+DQo8
L3A+DQo8cD48Zm9udCBzaXplPSIyIiBmYWNlPSJzYW5zLXNlcmlmIj5PciBtYXliZSBJJ20gd3Jv
bmc/PC9mb250PiA8L3A+DQo8cD48L3A+DQo8cD48Zm9udCBzaXplPSIyIiBmYWNlPSJzYW5zLXNl
cmlmIj5SdXNzZWxsIFdhbmc8L2ZvbnQ+IDxicj4NCjxmb250IHNpemU9IjIiIGZhY2U9InNhbnMt
c2VyaWYiPjxicj4NCjwvZm9udD48YnI+DQo8YnI+DQo8YnI+DQo8L3A+PHRhYmxlIHdpZHRoPSIx
MDAlIj4NCjx0Ym9keT4NCjx0ciB2YWxpZ249InRvcCI+DQo8dGQgd2lkdGg9IjM0JSI+PGZvbnQg
c2l6ZT0iMSIgZmFjZT0ic2Fucy1zZXJpZiI+PGI+IkxhZ2FuaWVyLCBKdWxpZW4iICZsdDtqdWxp
ZW5sQHF1YWxjb21tLmNvbSZndDs8L2I+DQo8L2ZvbnQ+DQo8cD48Zm9udCBzaXplPSIxIiBmYWNl
PSJzYW5zLXNlcmlmIj4yMDEwLTAzLTMxIDIzOjM1PC9mb250PiA8L3A+DQo8L3RkPg0KPHRkIHdp
ZHRoPSI2NSUiPg0KPHRhYmxlIHdpZHRoPSIxMDAlIj4NCjx0Ym9keT4NCjx0ciB2YWxpZ249InRv
cCI+DQo8dGQ+DQo8ZGl2IGFsaWduPSJyaWdodCI+PGZvbnQgc2l6ZT0iMSIgZmFjZT0ic2Fucy1z
ZXJpZiI+5pS25Lu25Lq6PC9mb250PjwvZGl2Pg0KPC90ZD4NCjx0ZD48Zm9udCBzaXplPSIxIiBm
YWNlPSJzYW5zLXNlcmlmIj4id2FuZy5qdW4xN0B6dGUuY29tLmNuIiAmbHQ7d2FuZy5qdW4xN0B6
dGUuY29tLmNuJmd0OywgVmFyam9uZW4gU2FtdSAmbHQ7c2FtdS52YXJqb25lbkBoaWl0LmZpJmd0
OzwvZm9udD4NCjwvdGQ+DQo8L3RyPg0KPHRyIHZhbGlnbj0idG9wIj4NCjx0ZD4NCjxkaXYgYWxp
Z249InJpZ2h0Ij48Zm9udCBzaXplPSIxIiBmYWNlPSJzYW5zLXNlcmlmIj7mioTpgIE8L2ZvbnQ+
PC9kaXY+DQo8L3RkPg0KPHRkPjxmb250IHNpemU9IjEiIGZhY2U9InNhbnMtc2VyaWYiPiJoaXBz
ZWNAaWV0Zi5vcmciICZsdDtoaXBzZWNAaWV0Zi5vcmcmZ3Q7LCAiaGlwc2VjLWJvdW5jZXNAaWV0
Zi5vcmciICZsdDtoaXBzZWMtYm91bmNlc0BpZXRmLm9yZyZndDs8L2ZvbnQ+DQo8L3RkPg0KPC90
cj4NCjx0ciB2YWxpZ249InRvcCI+DQo8dGQ+DQo8ZGl2IGFsaWduPSJyaWdodCI+PGZvbnQgc2l6
ZT0iMSIgZmFjZT0ic2Fucy1zZXJpZiI+5Li76aKYPC9mb250PjwvZGl2Pg0KPC90ZD4NCjx0ZD48
Zm9udCBzaXplPSIxIiBmYWNlPSJzYW5zLXNlcmlmIj5SRTogW0hpcHNlY10gRm9sbG93LXVwIG9u
IDQ4NDNiaXMgLyBPUkNISUR2MjwvZm9udD48L3RkPg0KPC90cj4NCjwvdGJvZHk+DQo8L3RhYmxl
Pg0KPGJyPg0KPHRhYmxlPg0KPHRib2R5Pg0KPHRyIHZhbGlnbj0idG9wIj4NCjx0ZD48L3RkPg0K
PHRkPjwvdGQ+DQo8L3RyPg0KPC90Ym9keT4NCjwvdGFibGU+DQo8YnI+DQo8L3RkPg0KPC90cj4N
CjwvdGJvZHk+DQo8L3RhYmxlPg0KPGJyPg0KPGJyPg0KPGJyPg0KPGZvbnQgc2l6ZT0iMiI+PHR0
Pk1heWJlIEknbSBibHVudCwgYnV0IElNSE8gSElQIGlkZW50aWZpZXJzIGFyZSBmbGF0LiBJZiBo
aWVyYXJjaGljYWwgYWxsb2NhdGlvbiBhbmQgbWFuYWdlbWVudCBvZiBpZGVudGlmaWVyIGlzIGEg
cmVxdWlyZWQgZmVhdHVyZSwgRE5TIG5hbWVzIGxvb2sgbGlrZSBhIGJldHRlciBmaXQgdGhhbiBI
b3N0IElkZW50aXRpZXMgLyBUYWdzLiBUaGVyZSdzIGFscmVhZHkgYmVlbiBzb21lIHdvcmsgb24g
bmFtZS1iYXNlZA0KIHNvY2tldHMsIGUuZy4sIHNlZSB0aGlzIHBhcGVyIGZyb20gQ2hyaXN0aWFu
IFZvZ3QuPGJyPg0KPGJyPg0KJmx0O2h0dHA6Ly9jaHJpc3RpYW52b2d0Lm1haWx1cC5uZXQvcHVi
LzIwMDkvdm9ndC0yMDA5LW5hbWUtb3JpZW50ZWQtc29ja2V0cy5wZGYmZ3Q7PGJyPg0KPGJyPg0K
d2FuZy5qdW4xN0B6dGUuY29tLmNuIHdyb3RlOjxicj4NCiZndDs8YnI+DQomZ3Q7PGJyPg0KJmd0
OyBEb2VzIE9SQ0hJRCBjb25zaWRlciBhbnkgY29tbWVyY2lhbCBkZXBsb3ltZW50IHJlcXVpcmVt
ZW50cz8gPGJyPg0KJmd0OyBJZiBISVAgY291bGQgYmUgY29tbWVyY2lhbCBkZXBsb3llZCwgSElQ
IElEIHNob3VsZCBiZSBkaXZpZGVkIGludG8gbWFueSBzdWItcGllY2VzPGJyPg0KJmd0OyBhbmQg
YWxsb2NhdGVkIHRvIHNlcnZpY2UgcHJvdmlkZXJzIG9yIG90aGVyIG9yZ2FuaXphdGlvbnMgLiA8
YnI+DQomZ3Q7PGJyPg0KJmd0Ozxicj4NCiZndDsgUnVzc2VsbCBXYW5nPGJyPg0KPGJyPg0KPC90
dD48L2ZvbnQ+PGJyPg0KPGJyPg0KPHA+PC9wPg0KPHByZT4tLS0tLS0tLS0tLS0tLS0tLS0tLS0t
LS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLQ0KWlRFJm5ic3A7SW5mb3JtYXRpb24m
bmJzcDtTZWN1cml0eSZuYnNwO05vdGljZTombmJzcDtUaGUmbmJzcDtpbmZvcm1hdGlvbiZuYnNw
O2NvbnRhaW5lZCZuYnNwO2luJm5ic3A7dGhpcyZuYnNwO21haWwmbmJzcDtpcyZuYnNwO3NvbGVs
eSZuYnNwO3Byb3BlcnR5Jm5ic3A7b2YmbmJzcDt0aGUmbmJzcDtzZW5kZXIncyZuYnNwO29yZ2Fu
aXphdGlvbi4mbmJzcDtUaGlzJm5ic3A7bWFpbCZuYnNwO2NvbW11bmljYXRpb24mbmJzcDtpcyZu
YnNwO2NvbmZpZGVudGlhbC4mbmJzcDtSZWNpcGllbnRzJm5ic3A7bmFtZWQmbmJzcDthYm92ZSZu
YnNwO2FyZSZuYnNwO29ibGlnYXRlZCZuYnNwO3RvJm5ic3A7bWFpbnRhaW4mbmJzcDtzZWNyZWN5
Jm5ic3A7YW5kJm5ic3A7YXJlJm5ic3A7bm90Jm5ic3A7cGVybWl0dGVkJm5ic3A7dG8mbmJzcDtk
aXNjbG9zZSZuYnNwO3RoZSZuYnNwO2NvbnRlbnRzJm5ic3A7b2YmbmJzcDt0aGlzJm5ic3A7Y29t
bXVuaWNhdGlvbiZuYnNwO3RvJm5ic3A7b3RoZXJzLg0KVGhpcyZuYnNwO2VtYWlsJm5ic3A7YW5k
Jm5ic3A7YW55Jm5ic3A7ZmlsZXMmbmJzcDt0cmFuc21pdHRlZCZuYnNwO3dpdGgmbmJzcDtpdCZu
YnNwO2FyZSZuYnNwO2NvbmZpZGVudGlhbCZuYnNwO2FuZCZuYnNwO2ludGVuZGVkJm5ic3A7c29s
ZWx5Jm5ic3A7Zm9yJm5ic3A7dGhlJm5ic3A7dXNlJm5ic3A7b2YmbmJzcDt0aGUmbmJzcDtpbmRp
dmlkdWFsJm5ic3A7b3ImbmJzcDtlbnRpdHkmbmJzcDt0byZuYnNwO3dob20mbmJzcDt0aGV5Jm5i
c3A7YXJlJm5ic3A7YWRkcmVzc2VkLiZuYnNwO0lmJm5ic3A7eW91Jm5ic3A7aGF2ZSZuYnNwO3Jl
Y2VpdmVkJm5ic3A7dGhpcyZuYnNwO2VtYWlsJm5ic3A7aW4mbmJzcDtlcnJvciZuYnNwO3BsZWFz
ZSZuYnNwO25vdGlmeSZuYnNwO3RoZSZuYnNwO29yaWdpbmF0b3ImbmJzcDtvZiZuYnNwO3RoZSZu
YnNwO21lc3NhZ2UuJm5ic3A7QW55Jm5ic3A7dmlld3MmbmJzcDtleHByZXNzZWQmbmJzcDtpbiZu
YnNwO3RoaXMmbmJzcDttZXNzYWdlJm5ic3A7YXJlJm5ic3A7dGhvc2UmbmJzcDtvZiZuYnNwO3Ro
ZSZuYnNwO2luZGl2aWR1YWwmbmJzcDtzZW5kZXIuDQpUaGlzJm5ic3A7bWVzc2FnZSZuYnNwO2hh
cyZuYnNwO2JlZW4mbmJzcDtzY2FubmVkJm5ic3A7Zm9yJm5ic3A7dmlydXNlcyZuYnNwO2FuZCZu
YnNwO1NwYW0mbmJzcDtieSZuYnNwO1pURSZuYnNwO0FudGktU3BhbSZuYnNwO3N5cw0KPC9wcmU+
DQoNCg0KPC9zcGFuPg0K

--_000_BF345F63074F8040B58C00A186FCA57F1C6A939422NALASEXMB04na_--

From miika.komu@hiit.fi  Wed Mar 31 21:40:20 2010
Return-Path: <miika.komu@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 0A9EE3A67F0 for <hipsec@core3.amsl.com>; Wed, 31 Mar 2010 21:40:20 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.981
X-Spam-Level: 
X-Spam-Status: No, score=0.981 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, DNS_FROM_OPENWHOIS=1.13, MIME_CHARSET_FARAWAY=2.45]
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 CeiFLI04I94z for <hipsec@core3.amsl.com>; Wed, 31 Mar 2010 21:40:19 -0700 (PDT)
Received: from argo.otaverkko.fi (argo.otaverkko.fi [212.68.0.2]) by core3.amsl.com (Postfix) with ESMTP id A936C3A6782 for <hipsec@ietf.org>; Wed, 31 Mar 2010 21:40:18 -0700 (PDT)
Received: from [192.168.0.165] (cs27089185.pp.htv.fi [89.27.89.185]) by argo.otaverkko.fi (Postfix) with ESMTP id D5ABA25ED1D for <hipsec@ietf.org>; Thu,  1 Apr 2010 07:40:49 +0300 (EEST)
Message-ID: <4BB423D0.3000001@hiit.fi>
Date: Thu, 01 Apr 2010 07:40:48 +0300
From: Miika Komu <miika.komu@hiit.fi>
User-Agent: Mozilla/5.0 (X11; U; Linux x86_64; en-US; rv:1.9.1.10pre) Gecko/20100330 Shredder/3.0.5pre
MIME-Version: 1.0
To: hipsec@ietf.org
References: <OFAF998C42.F6DDA65F-ON482576F8.00049E68-482576F8.00068525@zte.com.cn>
In-Reply-To: <OFAF998C42.F6DDA65F-ON482576F8.00049E68-482576F8.00068525@zte.com.cn>
Content-Type: text/plain; charset=GB2312
Content-Transfer-Encoding: 8bit
Subject: Re: [Hipsec] Follow-up on 4843bis / ORCHIDv2
X-BeenThere: hipsec@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
Reply-To: miika.komu@hiit.fi
List-Id: "This is the official IETF Mailing List for the HIP Working Group." <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, 01 Apr 2010 04:40:20 -0000

On 04/01/2010 04:11 AM, wang.jun17@zte.com.cn wrote:

Hi,

the orchid prefix is not routable in the same way that other IPv6
addresses are. Addresses with the orchid prefix are virtual addresses
similar to the ones used e.g. in VPNs and other tunnel mechanisms. So
they should not be advertised e.g. with BGP. However, they can be
advertised in DNS in new HI records.

> The flat assumption maybe enough for experiment, but we are pushing HIP 
> into a PS status, so I think we should make it is ready for commercial.
> 
> Assuming that an ISP want to deploy a HIP network, he must consider of 
> interworking with IPV6 network, so the hip prefix must be annouced as 
> normal ipv6 prefix amongst the routers. If there are more than one ISP 
> have deployed independent public hip network, the flat hip address space 
> will introduce routing conflicts.
> 
> So maybe a hip adress assignment authority is required, and which bits 
> represent the organization should be explicitly defined.
> 
> Or maybe I'm wrong?
> 
> Russell Wang
> 
> 
> 
> 
> *"Laganier, Julien" <julienl@qualcomm.com>*
> 
> 2010-03-31 23:35
> 
> 	
> 收件人
> 	"wang.jun17@zte.com.cn" <wang.jun17@zte.com.cn>, Varjonen Samu 
> <samu.varjonen@hiit.fi>
> 抄送
> 	"hipsec@ietf.org" <hipsec@ietf.org>, "hipsec-bounces@ietf.org" 
> <hipsec-bounces@ietf.org>
> 主题
> 	RE: [Hipsec] Follow-up on 4843bis / ORCHIDv2
> 
> 
> 	
> 
> 
> 
> 
> 
> Maybe I'm blunt, but IMHO HIP identifiers are flat. If hierarchical 
> allocation and management of identifier is a required feature, DNS names 
> look like a better fit than Host Identities / Tags. There's already been 
> some work on name-based sockets, e.g., see this paper from Christian Vogt.
> 
> <http://christianvogt.mailup.net/pub/2009/vogt-2009-name-oriented-sockets.pdf>
> 
> wang.jun17@zte.com.cn wrote:
>  >
>  >
>  > Does ORCHID consider any commercial deployment requirements?
>  > If HIP could be commercial deployed, HIP ID should be divided into 
> many sub-pieces
>  > and allocated to service providers or other organizations .
>  >
>  >
>  > Russell Wang
> 
> 
> 
> --------------------------------------------------------
> ZTE  Information  Security  Notice:  The  information  contained  in  this  mail  is  solely  property  of  the  sender's  organization.  This  mail  communication  is  confidential.  Recipients  named  above  are  obligated  to  maintain  secrecy  and  are  not  permitted  to  disclose  the  contents  of  this  communication  to  others.
> This  email  and  any  files  transmitted  with  it  are  confidential  and  intended  solely  for  the  use  of  the  individual  or  entity  to  whom  they  are  addressed.  If  you  have  received  this  email  in  error  please  notify  the  originator  of  the  message.  Any  views  expressed  in  this  message  are  those  of  the  individual  sender.
> This  message  has  been  scanned  for  viruses  and  Spam  by  ZTE  Anti-Spam  system.
> 
> 
> 
> _______________________________________________
> Hipsec mailing list
> Hipsec@ietf.org
> https://www.ietf.org/mailman/listinfo/hipsec

