Re: [Hipsec] comments on draft-ietf-hip-rfc4423-bis-01

Miika Komu <mkomu@cs.hut.fi> Mon, 21 February 2011 16:54 UTC

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 275FB3A6FE0 for <hipsec@core3.amsl.com>; Mon, 21 Feb 2011 08:54:37 -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 KrulX8glIyuq for <hipsec@core3.amsl.com>; Mon, 21 Feb 2011 08:54:35 -0800 (PST)
Received: from mail.cs.hut.fi (mail.cs.hut.fi [130.233.192.7]) by core3.amsl.com (Postfix) with ESMTP id C11923A6DC6 for <hipsec@ietf.org>; Mon, 21 Feb 2011 08:54:35 -0800 (PST)
Received: from hutcs.cs.hut.fi ([130.233.192.10] helo=[127.0.0.1]) by mail.cs.hut.fi with esmtp (Exim 4.54) id 1PrZ2a-0006PN-La for hipsec@ietf.org; Mon, 21 Feb 2011 18:55:16 +0200
Message-ID: <4D6298C6.50705@cs.hut.fi>
Date: Mon, 21 Feb 2011 18:54:30 +0200
From: Miika Komu <mkomu@cs.hut.fi>
User-Agent: Mozilla/5.0 (X11; U; Linux x86_64; en-US; rv:1.9.2.13) Gecko/20101208 Thunderbird/3.1.7
MIME-Version: 1.0
To: hipsec@ietf.org
References: <FD98F9C3CBABA74E89B5D4B5DE0263B9379A8486D1@XCH-NW-12V.nw.nos.boeing.com> <4D626A88.6060806@htt-consult.com> <FD98F9C3CBABA74E89B5D4B5DE0263B9379AA07740@XCH-NW-12V.nw.nos.boeing.com>
In-Reply-To: <FD98F9C3CBABA74E89B5D4B5DE0263B9379AA07740@XCH-NW-12V.nw.nos.boeing.com>
Content-Type: text/plain; charset="ISO-8859-1"; format="flowed"
Content-Transfer-Encoding: 7bit
Subject: Re: [Hipsec] comments on draft-ietf-hip-rfc4423-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: Mon, 21 Feb 2011 16:54:37 -0000

Hi,

On 21/02/11 17:49, Ahrenholz, Jeffrey M wrote:

>>> Section 6.2 last paragraph discusses skipping the address check;
>>> CBA can also be used to reduce handover latency here?
>>
>> CBA?
>
> credit-based authentication
>
> Maybe this lost its steam? Was it ever implemented?
> http://tools.ietf.org/html/draft-vogt-hip-credit-based-authorization-00
>
> I wouldn't reference CBA if there is no WG interest...

it's part of RFC5206.

>>> "There was little if any concrete thoughts about how HIP might affect
>>>    IP-layer or application-layer multicast."
>>> This sentence made sense in conjunction with the RFC 4423 abstract:
>>> "The memo describes the thinking of the authors as of Fall 2003."
>>> ...but without such text that sentence on multicast doesn't really
>>> stand on its own.
>>
>> What would you suggest?
>
> maybe:
> "There has not been much work in describing how HIP might affect
> IP-layer or application-layer multicast."
> or:
> "Few concrete thoughts exist about how HIP might affect
> IP-layer or application-layer multicast."
> ?
>
> Just trying to reduce the dependency on: "[As of Fall 2003] there was little if any..."

these guys have been researching on HIP-based multicast:

http://www.computer.org/portal/web/csdl/doi/10.1109/ICNS.2007.66