Hi Steve, Thanks.
For CCVPN, it’s just some extension work of L2 service plus the L1 service from multi-domain optical team. No new functions after the merge. There might be some overlapping work need to be distinguished but I believe that these won’t cause new issues to Arc. The combination report is on the make. For 5G case, we will keep our plan for Frankfurt as what has been presented so no new functions at least for Frankfurt. For the combined material of these two 5G use cases, we also need some more time working on it. Can we report to the Arc team about the updates on next week’s Arc subcommittee call? Best, Lin ------------------------------- 发件人: <[email protected]> 代表 "Stephen Terrill via Lists.Onap.Org" <[email protected]> 答复: <[email protected]> 日期: 2019年10月8日 星期二 01:25 收件人: LinMeng <[email protected]>, "[email protected]" <[email protected]>, "[email protected]" <[email protected]> 抄送: <[email protected]> 主题: Re: [Onap-arc] Arch Tracking for Frankfurt Hi Lin, Thank-you for the update. I believe that the original request was to have the requirements clear and ready by the end of September for prioritization, so I guess as soon as is feasible. To be fair, the multi-domain optical service has been presented and there weren’t noted issues, just requesting due diligence by checking synergies with CCVPN, but we should still close that off properly. The slicing – I assume its OK – I just don’t know as any updates and implications havent’t been seen. BR, Steve From: LinMeng <[email protected]> Sent: Saturday, 5 October 2019 16:03 To: Stephen Terrill <[email protected]>; [email protected]; [email protected] Cc: [email protected]; [email protected]; [email protected]; Henry Yu <[email protected]>; Gaurav agrawal <[email protected]> Subject: Re: [Onap-arc] Arch Tracking for Frankfurt Hi Steve, REQ-146 is also relavant to slicing evolution. But According to F2F discussion, REQ-158 and REQ-146 will be merged into one use case. We are working on the combination work for Arc review. Also, Mutidomain optical service is also asked to be merged into CCVPN, so we also need to merge REQ-37 and REQ-141. We also will prensent our combination work for Arc review. May I ask when is the deadline for us to present our combination work and when is the due for finalizing Arc requirement for Frankfurt? Best, Lin 发件人: <[email protected]> 代表 "Stephen Terrill via Lists.Onap.Org" <[email protected]> 答复: <[email protected]> 日期: 2019年10月3日 星期四 23:17 收件人: "[email protected]" <[email protected]>, "[email protected]" <[email protected]> 抄送: <[email protected]> 主题: [Onap-arc] Arch Tracking for Frankfurt Hi, I have been trying to track what I think is relivant to consider from an architecture prespective for the frankfurt release and note it here: https://wiki.onap.org/display/DW/ONAP+Frankfurt+Release+Architecture+Requirements Later I can fold these results into the pink/purple recommendation in the frankfurt requirements. If you feel this is incorrect, please let me know. BR, Steve Stephen Terrill Senior Expert, Automation and Management TECHNOLOGY SPECIALIST BDGS RDP Architecture & Technology Phone: +34913393005 Mobile: +34609168515 [email protected] Ericsson C/ Via de los Poblados 13. B 28033,Madrid, Madrid Spain ericsson.com Our commitment to Technology for Good and Diversity and Inclusion contributes to positive change. Follow us on: Facebook LinkedIn Twitter Legal entity:ERICSSON AB registration number 556056-6258, registered office in Stockholm. This communication is confidential. Our email terms: www.ericsson.com/en/legal/privacy/email-disclaimer -=-=-=-=-=-=-=-=-=-=-=- Links: You receive all messages sent to this group. View/Reply Online (#5462): https://lists.onap.org/g/onap-tsc/message/5462 Mute This Topic: https://lists.onap.org/mt/34405274/21656 Group Owner: [email protected] Unsubscribe: https://lists.onap.org/g/onap-tsc/leave/2743226/1412191262/xyzzy [[email protected]] -=-=-=-=-=-=-=-=-=-=-=-
