Hi Lingli, Sure, we will review it during the call and utilize in the future for tracking a different use case related issues.
Best regards, Alla Goldner Open Network Division Amdocs Technology [cid:image001.png@01D2FEE9.3022AE60] From: Lingli Deng [mailto:denglin...@chinamobile.com] Sent: Monday, July 17, 2017 10:39 AM To: Alla Goldner <alla.gold...@amdocs.com>; onap-usecase...@lists.onap.org Cc: 'onap-tsc' <email@example.com> Subject: RE: [onap-tsc] Use case subcommittee - agenda for tomorrow's (17/07/2017) meeting Hi Alla and team, As you might already note, there is a wiki page that integration team maintains for usecase related Q&A. It would be great to have it review and utilized as a track list for remaining issues. Thanks, Lingli From: onap-tsc-boun...@lists.onap.org<mailto:onap-tsc-boun...@lists.onap.org> [mailto:onap-tsc-boun...@lists.onap.org] On Behalf Of Alla Goldner Sent: 2017年7月16日 22:22 To: onap-usecase...@lists.onap.org<mailto:onap-usecase...@lists.onap.org> Cc: onap-tsc <firstname.lastname@example.org<mailto:email@example.com>> Subject: [onap-tsc] Use case subcommittee - agenda for tomorrow's (17/07/2017) meeting Hi all, Here is agenda for tomorrow’s Use case subcommittee meeting. R1 use cases are of highest priority. We must see if/what is needed to complete use cases interactions with a different projects this week. We will start going over R2 use case only if time permits. PTLs of a different projects, please indicate before tomorrow’s meeting if additional clarifications on R1 use cases are needed. Please upload your suggested R2 use cases https://wiki.onap.org/display/DW/Release+2+Use+Cases, so we can start some offline discussions as well. 1. R1 use cases (vCPE and vVoLTE): Status, Open issues, required actions (use cases leaders: vCPE: Kang Xi/Yoav Kluger/Jon Fannar, vVoLTE: Yang Xe/Chengli Wang/Lingli Deng) 2. R2 use cases: the initial proposals (list of those mentioned by a different related email exchanges is here): * Network Function Change Management * Enterprise vCPE * SD-WAN * SD-LAN * 5G i. RAN deployment ii. E2E Network Slicing 1. AOB For your information: 1. No comments were received for Use case subcommittee flow of operation as documented here https://wiki.onap.org/display/DW/Usecase+subcommittee<https://urldefense.proofpoint.com/v2/url?u=https-3A__wiki.onap.org_display_DW_Usecase-2Bsubcommittee&d=DwMFAw&c=LFYZ-o9_HUMeMTSQicvjIg&r=YQZaNPLN15xk3BWcVl7k8w&m=fJeFF2gsoUxIvMSd7LwlFJm195aQf6PCsGoLcOOJcVs&s=_gs9OYnZ5I93MA1QgqXnFJ9luEVCYalLple1Iynub1w&e=> 2. Meetings were held discussing use cases implementation with a different projects. We will go over status of those meetings. List of points from the last week is as following: * vCPE: i. Still under discussion?: 1. DCAE/Intel discussion to close packets’ format (please involve Alok Gupta per his request) 2. Interactions with SDC will be further clarified AG> Status. 3. SDN-C functional extension will be discussed with SDN-C team ii. Meeting with SDN-C/SDC/SO covering vCPE service model by Gil Bullard is scheduled for this Tuesday (relates to points 2 and 3 from the list above) iii. Brian Freeman started experimenting with onboarding a vCPE VNF with generic unix machine heat templates * vVoLTE i. There is request to include model which drives the use case in the vVolTE use case description ii. A question on whether vIMS+vEPC is enforced as a single request coming from SO (i.e. as a single network service or not). It was clarified that it is up to implementation, as VF-C can support it both ways. The corresponding clarification should be included in the use case description iii. Still under discussion?: 1. SDC for design time functionality 2. SDN-C interaction with 3rd party controller 3. For overlay - whether Openstack or hardware will be used - discussions with Brian Freeman are initiated 1. Following doodle poll results, I sent dedicated mail yesterday. We are moving to weekly meetings. Best regards, Alla Goldner Open Network Division Amdocs Technology [cid:image001.png@01D2FEE9.3022AE60] This message and the information contained herein is proprietary and confidential and subject to the Amdocs policy statement, you may review at https://www.amdocs.com/about/email-disclaimer This message and the information contained herein is proprietary and confidential and subject to the Amdocs policy statement, you may review at https://www.amdocs.com/about/email-disclaimer <https://www.amdocs.com/about/email-disclaimer>
_______________________________________________ ONAP-TSC mailing list ONAP-TSC@lists.onap.org https://lists.onap.org/mailman/listinfo/onap-tsc