Re: Sufficient Energy to finish KINK--comments by 2005-01-06

Nobuo OKABE<[email protected]>
>From: Sam Hartman <[email protected]>
>Subject: Re: Sufficient Energy to finish KINK--comments by 2005-01-06
>Date: Fri, 17 Dec 2004 18:08:36 -0500
>
>>     Nobuo> FYI
>>     Nobuo> Some people outside IETF are also interested in KINK.
>>     Nobuo>    http://fire.nist.gov/bfrlpubs/build03/art034.html
>>     Nobuo> So I believe KINK is important for industrial area where
>>     Nobuo> there are a lot of low-end devices mentioned by Kamada-san.
>> 
>> Sure, but if we cannot get enough people within the IETF to be
>> interested then we cannot do adequate review and so we will not do the
>> work.
>> If you have contacts in any of these areas and can convince people to
>> join this working group, rewiev specs, etc, then that would be greatly
>> appreciated.
>> People don't need to attend meetings to review drafts.
>
>The followings are what we can do for the WG now:
>
>1) Our group will contribute this WG
>   because we are also working for those area
>   (e.g. building, factory, plants) and implementing KINK.
>   We will show the details later.
>   # FYI: Kamada-san is a member of our group.
>
>2) I don't have a concrete connection with the author of the above URL.
>   However, I will contact him anyhow....I'm not sure the result though....
>
>----- nobuo

We have two groups in WIDE project which have interest in 
standardization of KINK.

One is TACA-WG (which Okabe-san mentioned above), who is developing 
security framework for facility networks. These facility network 
consists of huge number of low-capability (such as 8bit MPU) nodes. 
So, we need to make a scheme which can work not using public key 
cryptography. That's the reason why KINK is the key technical element 
in this work. TACA-WG has already made rough idea of the security 
framework and now in the prototyping stage.

Another group is IPSEC group, which is also known as the developer of 
racoon key management deamon in KAME IPv6 stack. This group is now 
implementing Racoon2, which supports both IKEv2 and KINK as IPSEC key 
management protocols. So, we have aready implemented KINK for this 
Racoon2 work (Kamada-san is the main contributor for KINK part of 
Racoon2).

Because these two groups has experience on implementing and using 
KINK, we can call for reviewer of KINK draft in these groups.
Also, we have aready itemize several issues in implementing KINK, we 
(maybe Kamada-san and some other guys) will write individual I-D on 
this implementation issue soon. I think this I-D will be a good start 
point for discussing how to do on KINK work. How about that ?

-- Atsushi INOUE   

-- 
Atsushi Inoue mailto:[email protected]