...
- Vikram expressed concerns in the following areas:
- The phase 1 whitepaper content may be diluted or bloated if material related to edge infrastructure is included. The original purpose of the white paper has always been, for over a year, app developer facing APIs for commercial purposes. Including infrastructure API related content is not aligned with that
- The infrastructure work item proposals include SDO architecture which is not open source originated
- The whitepaper should be published on-time and not delayed
- Jane responded with the following:
- Edge infrastructure work item is at the proposal stage to collect feedback. The delivery of this work item will be a separate whitepaper with infrastructure focus only
- SDOs’ approach cited in proposals is for solution comparison purposes only. Our work focus is on the open source community’s view of edge infrastructure and convergence of APIs across vendors
- It should be emphasized the new work item is not about standards integration or edge architecture recommendation. The subject is about APIs
- Tina clarified the following:
- API sub-committee has 2 work streams set up since June 2019: Application interface APIs and Infrastructure APIs
- 2 work streams can have their own focuses and deliver separately focused whitepapers
- Weekly meetings can be shared with time split
- Jeff Brower commented:
- Application developers are concerned about latency and other crucial issues controlled by Telcos and need assurance that developer APIs will continue to be compatible with what Telcos and their suppliers are doing in standards development
- The developer API whitepaper could have a sidebar to that effect if it would help to keep the group and work streams unified
...