Code merging is done in 1.1-rel. Please apply them into PF participating device and CTT.
# IoTivity patch is submitted. (Stephane: done) # Verification (SungKyu.Ko : Virtual QA lead: done) # Code Merging (1.1-rel branch) (Ashok : Maintainer for CA Layer: done) # PF participant apply this update (Participants: 7/12) # CTT is modified with this update (Mitch : 7/12) This is code change done by Stephane. ??: cid:image001.png at 01D1DC23.4139AD00 -----Original Message----- From: ???(Uze Choi) [mailto:[email protected]] Sent: Tuesday, July 12, 2016 10:48 AM To: 'Mats Wichmann'; 'iotivity-dev at lists.iotivity.org' Cc: Mitch Kettrick (cpm at openconnectivity.org) Subject: [Apply Plan] RE: [dev] [architecture_tg] IPv6 Multicast Address assignment for "All OCF Nodes" Hi, All. Regarding IPv6 multicast address change in IoTivity, we need quick move. As a request of IoTivity Lead Architect, let me organize the time line as follows. # IoTivity patch is submitted. (Stephane: done) # Verification (SungKyu.Ko : Virtual QA lead: done) # Code Merging (1.1-rel branch) (Ashok : Maintainer for CA Layer: done) # PF participant apply this update (Participants: 7/12) # CTT is modified with this update (Mitch : 7/12) Let me update the status whenever event happens. In addition to this patch, we may expect the another update for IoTivity 1.1.1 by tomorrow(7/13) BR, Uze Choi -----Original Message----- From: [email protected] [mailto:iotivity-dev- bounces at lists.iotivity.org] On Behalf Of Mats Wichmann Sent: Tuesday, July 12, 2016 9:20 AM To: iotivity-dev at lists.iotivity.org Subject: Re: [dev] [architecture_tg] IPv6 Multicast Address assignment for "All OCF Nodes" On 07/11/2016 06:21 PM, Thiago Macieira wrote: > On segunda-feira, 11 de julho de 2016 20:29:16 PDT Dwarkaprasad Dayama wrote: >> Dear Stephane, >> >> That's really good news. >> Few Q's - >> >> 1. When can you or someone submit Patch to IoTivity? >> 2. How do we plan to handle backward compatibility for devices being >> certified in in this week @ Poland? > > We have two options: > > A) we switch immediately, with no backwards compatibility. > > That means this change should not land in the 1.1.x branch, due to its > incompatibility. The earliest we could have it is in 1.2.0. This doesn't sound viable to me. Immediately, except excluding 1.1 era implementations? > B) we add support for it and slowly deprecate the All CoAP Nodes > address > > That change could be in 1.1.x and we would schedule the deprecation > for something like 1.3.0. That means code rework to deal with trying on two address ranges during the transition period, no? No sure how trivial that is. Whichever, a decision Real Soon due to the status of 1.1.1 would seem to be needed. _______________________________________________ iotivity-dev mailing list <mailto:iotivity-dev at lists.iotivity.org> iotivity-dev at lists.iotivity.org <https://lists.iotivity.org/mailman/listinfo/iotivity-dev> https://lists.iotivity.org/mailman/listinfo/iotivity-dev -------------- next part -------------- HTML ?????? ??????????????... URL: <http://lists.iotivity.org/pipermail/iotivity-dev/attachments/20160712/43d132c4/attachment.html> -------------- next part -------------- A non-text attachment was scrubbed... Name: image001.png Type: image/png Size: 81292 bytes Desc: ?????? ?? ????????. URL: <http://lists.iotivity.org/pipermail/iotivity-dev/attachments/20160712/43d132c4/attachment.png>
