I know that TCP/TLS implementation is required for CNC(CoAP Native Cloud) project scope in OCF Bangkok version. You mean there will be mainly 3 patches to complete it. Am I right?
If these patches do not prevent operation in the existing scenario, direct patch into master looks reasonable. BR, Uze Choi From: iotivity-dev-boun...@lists.iotivity.org [mailto:iotivity-dev-boun...@lists.iotivity.org] On Behalf Of 조제현 Sent: Tuesday, March 13, 2018 3:45 PM To: kishen.mal...@intel.com Cc: iotivity-dev@lists.iotivity.org Subject: [dev] Regarding iotivity-constrained TCP contribution. Hello, I have a plan to contribute tcp feature in iotivity-constrained repository. below is contribute plan. ------------------------------------------------------------------------------------------------------ STEP 1. separate ipadapter with UDP & make space for TCP adapter. (like below) ipadapter | ┏-------┐ UDP TCP STEP 2. implement TCP adapter. STEP 3. implement CoAP over TCP. ------------------------------------------------------------------------------------------------------ The question is that do I need to make separate branch for this? or just push to master and review for it. Thanks. jaehyun <http://gais.sec.samsung.net/gaps/images/card_samsungKor2.gif> 조제현 Jaehyun Cho Assistant Engineer IoT Lab Convergence Team Software R&D Center SAMSUNG ELECTRONICS CO., LTD. Mobile : 82-10-9621-2800 E-mail : jaehyun3....@samsung.com <http://ext.samsung.net/mail/ext/v1/external/status/update?userid=jaehyun3.cho&do=bWFpbElEPTIwMTgwMzEzMDY0NTI1ZXBjbXMxcDJhOTBhNjlmOTIzZTkyMTkyZTkzZTMwYzhiYmNkNTZiMCZyZWNpcGllbnRBZGRyZXNzPWlvdGl2aXR5LWRldkBsaXN0cy5pb3Rpdml0eS5vcmc_>
_______________________________________________ iotivity-dev mailing list iotivity-dev@lists.iotivity.org https://lists.iotivity.org/mailman/listinfo/iotivity-dev
