...
- White paper Neal’s comments discussion
- Jeff presented Akraino API URL prelim PowerPoint
- Dual landing page option: api.akraino.org, apiportal.akraino.org
- Single landing page option: all links under one subdomain name
- Collaboration with ETSI MEC in two fields, API content (analysis and comparison) and API adaptation (sandbox ,workshop, validation)
Notes
- WP#2 final review
Neal - will be editing next few days - API Portal landing page / URL proposal
Jane - change 2nd and 3rd link eamples to API wiki and API testing
Neal - walk through 3GPP APIs CAF, NEF (traffic influencing). What other Akraino BP groups are using ?
Tina - should be hosted on LF Edge owned server
Jane - showed API portal mind map prototype. Idea is to make it easy for developers to zero in on API related info they need
Neal / Jane - back and forth on OpenNESS NEF vs. 3GPP version
Neal - suggest to present single URL landing page to TSC, but keep working within existing dual URL framework - ESTI MEC DECODE activity
Jane - collect thoughts on ETSI MEC collaboration
Neal - Intel is taking part, focus on actual implementations
Jane - possibly work with them on API validation, but we have limited resources
Jeff - how does ETSI MEC fit in with other new work item proposals ?
Neal -does outside collaboration help move ETSI MEC along faster ?