[wi-sun rlmmwg] Security Features in RLMM Profile 1v01
Ryota Yamada
ryamada at ari.ncl.omron.co.jp
Wed Jun 29 17:09:53 PDT 2016
Dear Verotiana-san,
Thank you very much for your feedback. I will put your feedback in a
slide for the discussion in the RLMM WG TC today.
Best regards,
Ryota
On 2016/06/29 19:33, rverotiana at nict.go.jp wrote:
> Dear Yamada-san and all,
>
>>From our last call I believe we are down to a choice between [2] and [3].
>
> If my understanding is correct, here are the things we should consider in this discussion:
>
> *The key update frequency depends on:
>
> - the R1/R9 traffic (traffic to and from R0 is bound by their duty
> cycle and is less significant in the key update frequency)
> - the number of R1 devices in the network
> - others?
>
> *The following implementation cases are possible:
>
> - Many R1, low traffic (Key update frequency similar to the R0
> wake-up frequency) ==> [2]
> - Many R1, high traffic ==> [3], but broadcast become costly
> (multiple unicasts).
> o If broadcast transmissions are frequent, [2] is better
> o Another option would be to have a common key for R1s and unique respective keys for R0
> - Low number of R1 (most devices are R0) or only R0 ==> [2] or [3].
> o If [3], broadcasts can be handled with multiple unicast transmissions synchronized with the duty cycle of R0.
> - Others?
>
> So far, there is no strict definition or requirement on few/many R1 or high/low traffic.
> Therefore, one of the most feasible/preferable choice might be "to simply hold those two options."
>
> This might help the discussion tomorrow.
>
> Best regards,
>
> Verotiana
>
>
>> Dear RLMM WG members,
>>
>> This is gentle reminder to members for providing feedback for discussion
>> on security features in RLMM Profile 1v01. We will discuss about this in
>> the call to be held tomorrow on Jun. 30th JST.
>>
>> If you could provide your feedback before the call, we can share it in
>> the call.
>>
>> Best regards,
>> Ryota
>>
>>
>> On 2016/06/24 16:14, Ryota Yamada wrote:
>>> Dear RLMM WG members,
>>>
>>> I have uploaded the updated version of the material which summarize
>>> current status of discussion regarding security feature for 1v01:
>>> https://dms.wi-sun.org/htcomnet/Handlers/Download.ashx?action=download&file=M2MIG%2F20160624%20Security%20Features%20in%20RLMM%20Profile%201v01%200v01.pptx
>>>
>>>
>>> Please go through the material and give your feedback before next call
>>> to be held fromm 11:00 on Jun. 30th JST.
>>>
>>> There are two major questions:
>>> (1) Which option on page 3 of the material shall we choose?
>>> (2) Which option on page 7 shall we choose for how to manage key?
>>>
>>> If you have any comment or suggestion, please let me know.
>>>
>>> Best regards,
>>> Ryota
>>>
>>>
>>
>> 様
>>
>> お世話になっております。オムロン株式会社の山田亮太です。
>>
>> さん
>>
>> おつかれさまです。(企画)オープンの山田亮太です。
>>
>>
>>
>> 以上、よろしくお願いいたします。
>>
>>
>> --
>> +--------------------------------
>> | Ryota Yamada <ryamada at ari.ncl.omron.co.jp>
>> |
>> | OMRON Corporation
>> | Technology and Intellectual Property H.Q.
>> | Planning and CTO Support Division
>> | Open Innovation Sec.
>> |
>> | Tel: +81-774-74-2158 (Ext: 7-232-6558)
>>
>> _______________________________________________
>> rlmmwg mailing list
>> rlmmwg at wi-sun.org
>> https://lists.wi-sun.org/listinfo/rlmmwg
>>
>> Copyright (C) 2016 Wi-SUN Alliance. The contents of this email are confidential and may not be disclosed to non-members without prior written consent of an authorised representative of Wi-SUN Alliance.
>>
>
>
>
様
お世話になっております。オムロン株式会社の山田亮太です。
さん
おつかれさまです。(企画)オープンの山田亮太です。
以上、よろしくお願いいたします。
--
+--------------------------------
| Ryota Yamada <ryamada at ari.ncl.omron.co.jp>
|
| OMRON Corporation
| Technology and Intellectual Property H.Q.
| Planning and CTO Support Division
| Open Innovation Sec.
|
| Tel: +81-774-74-2158 (Ext: 7-232-6558)
More information about the rlmmwg
mailing list