Re: [6tsch] Work item on security

[Rene Struik <[e-mail]>]

Hi Pascal:

I suggest to leave the current language in the draft charter as is right now. Broadening the scope to essentially a complete trust life-cycle management solution, as you suggest, seems
to be somewhat premature, esp. given that there has hardly been any discussion on the mailing list or on calls on the topic of security yet (10 minutes during July
5th call; no real discussion). It would be prudent to clearly define what problem one is trying to solve first before jumping on solutions.

The broadened scope would be important for internet-of-things applications of course, but seems to be a larger undertaking than providing the "glue" between 802.15.4e and IPv6.

Best regards, Rene
  
[current draft charter text related to security (version July 24, 2013)]

A document on the security architecture and requirements for 6TSCH will be
developed, and depending on the security requirements identified in the
document, the group may work on a security solution and ask for security area
review.


On 7/24/2013 6:09 AM, Pascal Thubert (pthubert) wrote:
>
> Dear all :
>
> So far we have been pretty unclear on whether the security work would 
> be in charter, and what the scope of that work would be.
>
> Raghu unearthed the issue as he was working on the work item slides 
> for the BoF.
>
> I see the need for a security framework that describes commissioning, 
> provisioning, key exchange and link security for large 6TSCH networks.
>
> And that is exactly what Yoshi and the others have started with 
> draft-ohba-6tsch-security.
>
> Questions to the group:
>
> Could/should we make this a full work item?
>
> And if so, what scope exactly?
>
> Cheers,
>
> Pascal
>
>
>
> _______________________________________________
> 6tsch mailing list
> [e-mail]
> https://www.ietf.org/mailman/listinfo/6tsch


-- 
email: [e-mail] | Skype: rstruik
cell: [phone] | US: [phone]