Dwarka question has assumed that we may not apply this update into this PF device. But If we can do this by today or tomorrow, we don't need to concern both compatible. I think we can finalize all related tasks soon.
BR, Uze Choi -----Original Message----- From: [email protected] [mailto:architecture_tg at openconnectivity.org] On Behalf Of Thiago Macieira Sent: Tuesday, July 12, 2016 11:46 AM To: architecture_tg at openconnectivity.org Cc: Stephane Lejeune (stlejeun); Dwarkaprasad Dayama; iotivity- dev at lists.iotivity.org Subject: Re: [architecture_tg] IPv6 Multicast Address assignment for "All OCF Nodes" On segunda-feira, 11 de julho de 2016 23:45:10 PDT Stephane Lejeune (stlejeun) wrote: > > 2. How do we plan to handle backward compatibility for devices being > > certified in in this week @ Poland? > I have a couple ideas but prefer having this discussion after we > actually know we do have certified devices. Suggestion: add a patch that keeps the All CoAP Nodes compatibility by default, but has a compile-time option to turn it off (just All OCF Nodes). That way, we can choose whether we certify requiring both or just the new address. If we decide to certify only requiring the new address, it becomes the user's decision whether to keep compatibility or not. They wouldn't have to, for certification. But they may want to if they have pre-certified devices that they want to keep compatibility with. -- Thiago Macieira - thiago.macieira (AT) intel.com Software Architect - Intel Open Source Technology Center
