Versions Compared

Old Version 1

changes.mady.by.user Jeff Brower

Saved on

compared with

New Version 2

changes.mady.by.user Jeff Brower

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

20 March 2020 / 9:00 AM PDT / Zoom meeting

Attendees 

Tina Tsou, Vikram Siwach , Jane Shen, Jiafeng Zhu, Neal Oliver, Swarup Nayak, Jeff Brower

Meeting Notes - Brower

Agenda

Last Meeting Follow-up

Tina clarified that subcommittee chair/co-chair should attend Thursday TSC meeting to provide subcommittee update. 

New Business

Jane provided future work item proposal details. The presentation was stopped on slide page 2 when SDO was mentioned. 

Notes

  • Vikram expressed concerns in the following areas:
    1. 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
    2. The infrastructure work item proposals include SDO architecture which is not open source originated
    3. The whitepaper should be published  on-time and not delayed
  • Jane responded with the following:
    1. 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
    2. 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
    3. 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:
    1. API sub-committee has 2 work streams set up since June 2019: Application interface APIs and Infrastructure APIs
    2. 2 work streams can have their own focuses and deliver separately focused whitepapers
    3. Weekly meetings can be shared with time split
  • Jeff Brower commented:
    1. 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
    2. The developer API whitepaper could have a sidebar to that effect if it would help to keep the group and work streams unified

Action Items

Offline discussions should be facilitated to resolve misunderstandings and maintain group momentum