December 13, 2017 (f2f meeting)

Here is the summary/list of action items:

1. Needed to have contact person details per each requirement – Alla to provide (in the attached)

2. Scaling out requirement is merged with auto/manual scaling requirement, assuming both VFC and APPC support

3. Enhancements for service onboarding requirement merges with PNF support requirement

4. 5G task force ned to discuss VFC support with VFC team, as currently this is missing from the table of affected entities

5. The next level of details for discussions with PTLs must be provided by the requirements authors and this should include, at least:

   1. Sequence diagrams

   2. VNFs

   3. Full list of involved companies (in terms of number of developers each company is willing to put on the specific development)

   4. Model information

   5. Description of how the requirement will be tested

   6. APIs (existing and new) – nice to have, if information is available

   7. It is up to requirements’ authors to have discussions with PTLs during the next week (as the following one is Christmas Holidays). PTLs must get all information related to specific functional requirements (as per described above) and discuss it with the teams by the end of the next week, so, when they come back from Christmas vacation (January 2^nd), they can analyze and discuss it with their teams, and come up with their estimations by January 8^th. By January 18 (during the following 10 days) they will need to build harmonized view on all functional requirements plus S3P, and define what they can implement.

Those requirements which will not be discussed with PTLs next week will be defined as a stretch goal.

Monday’s Usecase subcommittee meeting will be dedicated to review the additional information available by Monday. We can also use some of the meeting time for discussions with the PTLs, if requirements team makes sure PTL attends our call.