Re: [Mipshop] Gauging interest in official WG adoption of internetdrafts

Rajeev Koodli <rajeev@iprg.nokia.com> Tue, 28 March 2006 01:19 UTC

Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1FO2rW-0008IO-31; Mon, 27 Mar 2006 20:19:10 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1FO2rU-0008Hh-D4 for mipshop@ietf.org; Mon, 27 Mar 2006 20:19:08 -0500
Received: from darkstar.iprg.nokia.com ([205.226.5.69]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1FO2rT-0007R3-K5 for mipshop@ietf.org; Mon, 27 Mar 2006 20:19:08 -0500
Received: (from root@localhost) by darkstar.iprg.nokia.com (8.11.0/8.11.0-DARKSTAR) id k2S0cPb02639; Mon, 27 Mar 2006 16:38:25 -0800
X-mProtect: <200603280038> Nokia Silicon Valley Messaging Protection
Received: from mvdhcp14193.americas.nokia.com (172.18.141.93, claiming to be "[127.0.0.1]") by darkstar.iprg.nokia.com smtpdv19jmH; Mon, 27 Mar 2006 16:38:23 PST
Message-ID: <44288EAA.5000309@iprg.nokia.com>
Date: Mon, 27 Mar 2006 17:17:30 -0800
From: Rajeev Koodli <rajeev@iprg.nokia.com>
User-Agent: Mozilla Thunderbird 1.0.6 (Windows/20050716)
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: James Kempf <kempf@docomolabs-usa.com>
Subject: Re: [Mipshop] Gauging interest in official WG adoption of internetdrafts
References: <20060322074936.65932.qmail@web81910.mail.mud.yahoo.com> <Pine.LNX.4.58.0603272256480.3081@rhea.tcs.hut.fi> <016c01c651e0$e65d82d0$026115ac@dcml.docomolabsusa.com>
In-Reply-To: <016c01c651e0$e65d82d0$026115ac@dcml.docomolabsusa.com>
Content-Type: text/plain; charset="ISO-8859-1"; format="flowed"
Content-Transfer-Encoding: 7bit
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 22bbb45ef41b733eb2d03ee71ece8243
Cc: Wassim Haddad <whaddad@tcs.hut.fi>, mipshop@ietf.org
X-BeenThere: mipshop@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: mipshop.ietf.org
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/mipshop>, <mailto:mipshop-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:mipshop@ietf.org>
List-Help: <mailto:mipshop-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/mipshop>, <mailto:mipshop-request@ietf.org?subject=subscribe>
Errors-To: mipshop-bounces@ietf.org

The purpose of SEND-based key derivation for handover is to obtain a 
handover key for securing FMIP signaling (Primarily FBU). Whereas a 
general-purpose solution may be desirable, our experience with such 
efforts indicate the pitfalls associated with subtlety. So, I prefer to 
keep the scope of the _current_ WG item to securing FMIP signaling. 
Perhaps in the future, enhancements may be considered.

Regards,

-Rajeev


James Kempf wrote:
> Wassim,
> 
> As we've discussed offlist, context transfer of keys between ARs has the 
> potential to violate the Housley Critera:
> 
> http://www.ietf.org/internet-drafts/draft-housley-aaa-key-mgmt-02.txt
> 
> Russ' draft is written specifically with AAA key management in mind, but 
> the criteria apply to other types of key management as well. I skimmed 
> your draft, and it seemed to me that there might be a problem.
> 
> Rajeev and I have been working on this draft for over a year, and it was 
> transferred from MOBOPTS with the recommendation that it become a WG 
> draft. If you manage to come up with some way to reduce the amount of 
> signaling involved in SEND-based key exchange for handover that is 
> consistent with the Housley Critera, I would have no problem 
> incorporating that into the WG draft at that time. Gab and Stefano can 
> correct me if I am wrong, but I do not believe we are in a hurry to get 
> this draft to the IESG, so there should be plenty of time to incorporate 
> enhancements that you or any WG member would like to include.
> 
>            jak
> 
> 
> ----- Original Message ----- From: "Wassim Haddad" <whaddad@tcs.hut.fi>
> To: "gabriel montenegro" <gabriel_montenegro_2000@yahoo.com>
> Cc: <mipshop@ietf.org>
> Sent: Monday, March 27, 2006 12:07 PM
> Subject: Re: [Mipshop] Gauging interest in official WG adoption of 
> internetdrafts
> 
> 
>> Hi,
>>
>> I support making the first two and the last three items WG items.
>> Concerning the third item, I'd like to mention that the OptiSEND
>> proposal (draft-haddad-mipshop-optisend-01), while not complete yet,
>> allows the MN to share a secret with the *first* AR and to use it to
>> authenticate ND signaling messages *and* mobility signaling messages
>> exchanged between an AR and the MN during the MN movements and as
>> long as the shared secret remains valid.
>>
>>
>> Regards,
>>
>> Wassim H.
>>
>>
>>
>> On Tue, 21 Mar 2006, gabriel montenegro wrote:
>>
>>> Folks,
>>>
>>> In today's meeting we talked about 4 potential items up for adoption 
>>> as official working
>>> groups. Talking with folks after the meeting, we've decided to add 
>>> two more to the list
>>> of items we'll ask the WG whether we should adopt. This is the 
>>> follow-up email to today's
>>> discussion, to make sure we ask this on the mailing list.
>>>
>>> So the question to the WG is: Should we adopt the following documents 
>>> as official WG
>>> items (based on the individual drafts as noted below)?:
>>>
>>> 1. draft-ietf-mipshop-fmipv6-rev-XX.txt
>>> based on draft-koodli-mipshop-rfc4068bis-00.txt
>>>
>>> 2. draft-ietf-mipshop-handover-keys-aaa-XX.txt
>>> based on  draft-vidya-mipshop-handover-keys-aaa-01.txt
>>>
>>> 3. draft-ietf-mipshop-handover-key-send-XX.txt
>>> based on draft-kempf-mobopts-handover-key-01.txt (currently expired)
>>>
>>> 4. draft-ietf-mipshop-fh80216e-XX.txt
>>> based on draft-jang-mipshop-fh80216e-02.txt
>>>
>>> 5. draft-ietf-mipshop-3gfh-XX.txt
>>> based on draft-yokota-mipshop-3gfh-02.txt
>>>
>>> 6. draft-ietf-mipshop-cga-cba-XX.txt
>>> based on draft-arkko-mipshop-cga-cba-03.txt
>>>
>>> Please send comments one way or another through April 4, 2006.
>>>
>>> Thanks,
>>>
>>> chairs
>>>
>>>
>>> __________________________________________________
>>> Do You Yahoo!?
>>> Tired of spam?  Yahoo! Mail has the best spam protection around
>>> http://mail.yahoo.com
>>>
>>> _______________________________________________
>>> Mipshop mailing list
>>> Mipshop@ietf.org
>>> https://www1.ietf.org/mailman/listinfo/mipshop
>>>
>>>
>>
>> _______________________________________________
>> Mipshop mailing list
>> Mipshop@ietf.org
>> https://www1.ietf.org/mailman/listinfo/mipshop
>>
> 
> 
> 
> _______________________________________________
> Mipshop mailing list
> Mipshop@ietf.org
> https://www1.ietf.org/mailman/listinfo/mipshop


_______________________________________________
Mipshop mailing list
Mipshop@ietf.org
https://www1.ietf.org/mailman/listinfo/mipshop