Re: [Mobopts] New Draft on Proxy SEND

Brett Pentland <brett.pentland@eng.monash.edu.au> Wed, 25 May 2005 07:35 UTC

Received: from darkstar.iprg.nokia.com (darkstar.iprg.nokia.com [205.226.5.69]) by mailhost.iprg.nokia.com (8.9.3/8.9.3-GLGS) with ESMTP id AAA04064; Wed, 25 May 2005 00:35:32 -0700 (PDT)
Received: (from root@localhost) by darkstar.iprg.nokia.com (8.11.0/8.11.0-DARKSTAR) id j4P746N14637; Wed, 25 May 2005 00:04:06 -0700
X-mProtect: <200505250704> Nokia Silicon Valley Messaging Protection
Received: from mailrelay.iprg.nokia.com (205.226.0.201) by darkstar.iprg.nokia.com smtpdvXmctC; Wed, 25 May 2005 00:04:04 PDT
X-Scanned: Wed, 25 May 2005 00:35:15 -0700 Nokia Message Protector V1.3.35 2005042208 - RELEASE
Received: (from root@localhost) by mailrelay.iprg.nokia.com (8.12.9/8.12.9) id j4P7ZFPS030159; Wed, 25 May 2005 00:35:15 -0700
X-pstn-settings: 5 (1.50000:1.50000) p:5 r:4 m:4 c:5
X-pstn-version: pase:2.23
X-pstn-levels: s:99.90000/99.90000 p:95.91080 r:95.91080 m:97.02319 c:98.76780
X-pstn-address: from <mobopts-bounces@irtf.org>
X-pstn-spam: N
Received: from megatron.ietf.org (132.151.6.71) by mailrelay.iprg.nokia.com 00hFq4u2; Wed, 25 May 2005 00:35:14 PDT
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1DaqO9-00069N-W4; Wed, 25 May 2005 03:33:14 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1DaqO3-00066J-Fz for mobopts@megatron.ietf.org; Wed, 25 May 2005 03:33:11 -0400
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id DAA14984 for <mobopts@irtf.org>; Wed, 25 May 2005 03:33:05 -0400 (EDT)
Received: from alpha9.its.monash.edu.au ([130.194.1.9]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1DaqgN-0004RW-8G for mobopts@irtf.org; Wed, 25 May 2005 03:52:04 -0400
Received: from localhost ([130.194.13.88]) by vaxh.its.monash.edu.au (PMDF V6.2-1 #31112) with ESMTP id <01LOOM2AZ46S9ANU7V@vaxh.its.monash.edu.au> for mobopts@irtf.org; Wed, 25 May 2005 17:33:00 +1000
Received: from curly.its.monash.edu.au (localhost.localdomain [127.0.0.1]) by localhost (Postfix) with ESMTP id 7A57BAB543; Wed, 25 May 2005 17:32:59 +1000 (EST)
Received: from [130.194.252.100] (brettpc.eng.monash.edu.au [130.194.252.100]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by curly.its.monash.edu.au (Postfix) with ESMTP id 531A04FB0C; Wed, 25 May 2005 17:32:59 +1000 (EST)
Date: Wed, 25 May 2005 17:32:58 +1000
From: Brett Pentland <brett.pentland@eng.monash.edu.au>
Subject: Re: [Mobopts] New Draft on Proxy SEND
In-reply-to: <014401c55a3f$7fec4fc0$016115ac@dcml.docomolabsusa.com>
To: James Kempf <kempf@docomolabs-usa.com>
Message-id: <42942A2A.5010600@eng.monash.edu.au>
MIME-version: 1.0
Content-type: text/plain; charset="ISO-8859-1"; format="flowed"
Content-transfer-encoding: 7bit
X-Accept-Language: en-us, en
User-Agent: Mozilla Thunderbird 1.0.2-1.3.3 (X11/20050513)
References: <014401c55a3f$7fec4fc0$016115ac@dcml.docomolabsusa.com>
X-Spam-Score: 2.4 (++)
X-Scan-Signature: 8abaac9e10c826e8252866cbe6766464
Content-Transfer-Encoding: 7bit
Cc: mobopts@irtf.org
X-BeenThere: mobopts@irtf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: IP Mobility Optimizations <mobopts.irtf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/mobopts>, <mailto:mobopts-request@irtf.org?subject=unsubscribe>
List-Post: <mailto:mobopts@irtf.org>
List-Help: <mailto:mobopts-request@irtf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/mobopts>, <mailto:mobopts-request@irtf.org?subject=subscribe>
Sender: mobopts-bounces@irtf.org
Errors-To: mobopts-bounces@irtf.org
Status: O

Hi Jim,

I don't think I understand the signature stuff well enough for
much meaningful commentary, but the general concept sounds good.

I have one question about the backward compatibility section (3.5).
If a multi-CGA capable node needs to be able to issue ND messages
with standard SEND RSA signatures, what procedure is used to decide
when to do this?  Does the node try a Ring Signature Option, and if
it gets no response, try again with a standard SEND signature?  If
so, would it keep an notation in its neighbour cache of the Ring
Signature capability of each node, for future reference?

Cheers,
Brett.

James Kempf wrote:
> I've just posted a new draft on how to do secure address proxying. Until the
> draft appears in the Interent Drafts directory, you can find the draft here:
> 
> http://www.geocities.com/kempf42/draft-kempf-mobopts-ringsig-ndproxy-00.txt
> 
> The draft defines how to use Rivest-Shamir-Tauman ring signatures (Asiacrypt
> 2001) and CGAs generated with multiple keys to allow a router, such as a
> Mobile IPv6 home agent, to securely proxy a CGA. Multi-key CGAs allow secure
> proxying without revealing from the cryptographic material whether the
> mobile node is on or off the link, unlike other secure proxying techniques.
> 
> Note that DoCoMo has filed for IPR on this draft, we're working on the
> release currently. DoCoMo's policy is to release IPR royality-free if the
> draft is approved as an Internet Standard if the IPR involves
> interoperability, and I'm recommending that for this case.

_______________________________________________
Mobopts mailing list
Mobopts@irtf.org
https://www1.ietf.org/mailman/listinfo/mobopts