Hi, Of course, IoTivity, the CTT and vendor implementations here at the cert event have to be updated too so changing the core spec is only part of the equation.
I agree that it would be ideal to get this implemented this week to avoid legacy issues with devices that we'll be certifying this week. I have commitment from Jacek that if IoTivity (and the devices) makes the change, they can make the change in the CTT as well. So it comes down to whether or not this can be done in IoTivity in a short timeframe. With Stephane on vacation, it may require someone else to provide a patch for this. Mitch From: [email protected] [mailto:architecture_tg at openconnectivity.org] On Behalf Of Wouter van der Beek (wovander) Sent: Monday, July 11, 2016 5:40 AM To: jinchoe at samsung.com; Stephane Lejeune (stlejeun); architecture_tg at openconnectivity.org; jinchoe at gmail.com Cc: iotivity-dev at lists.iotivity.org Subject: RE: [architecture_tg] IPv6 Multicast Address assignment for "All OCF Nodes" Congratulations Stephane, I did not expect it so quickly. It would be good to do this already in the upcoming plugfest. Richard, will you take an action item to change the architecture document to use/reference this multicast IP address? Kind Regards, Wouter From: [email protected] [mailto:architecture_tg at openconnectivity.org] On Behalf Of ??? Sent: 11 July 2016 13:33 To: Stephane Lejeune (stlejeun) <stlejeun at cisco.com>; architecture_tg at openconnectivity.org; jinchoe at gmail.com Cc: iotivity-dev at lists.iotivity.org Subject: RE: [architecture_tg] IPv6 Multicast Address assignment for "All OCF Nodes" great! You just did it. :-) JinHyeock --------- Original Message --------- Sender : Stephane Lejeune (stlejeun) <stlejeun at cisco.com> Date : 2016-07-11 19:54 (GMT+9) Title : [architecture_tg] IPv6 Multicast Address assignment for "All OCF Nodes" Hi all, IANA has listed " All OCF Nodes" for the following variable scope address: FF0X:0:0:0:0:0:0:158 Please see http://www.iana.org/assignments/ipv6-multicast-addresses In the assigned variable-scope address -- which can also be listed as "FF0X::158" for short -- the "X" denotes any possible scope. Assignment in the variable scope range means that you can use your address with any scope you like, while avoiding conflicts with other assignments/uses. Best regards, Stephane. <http://v70ext.samsung.net/mail/ext/v1/external/status/update?userid=jinchoe &do=bWFpbElEPTIwMTYwNzExMTIzMjQ0ZXBjbXMxcDg4YzZmM2Q1OTFkYjA0N2IxNzkxYmFjYWIy OTFjNjE4ZiZyZWNpcGllbnRBZGRyZXNzPWFyY2hpdGVjdHVyZV90Z0BvcGVuY29ubmVjdGl2aXR5 Lm9yZw__> _____ No virus found in this message. Checked by AVG - www.avg.com Version: 2016.0.7640 / Virus Database: 4613/12581 - Release Date: 07/08/16 -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.iotivity.org/pipermail/iotivity-dev/attachments/20160711/04009e75/attachment.html> -------------- next part -------------- A non-text attachment was scrubbed... Name: image001.png Type: image/png Size: 33527 bytes Desc: not available URL: <http://lists.iotivity.org/pipermail/iotivity-dev/attachments/20160711/04009e75/attachment.png>
