Important Disclosures and Information
This page will host the collaborative efforts of the ONAP API CVS proposal working team. The working team's purpose is to devise a consistent API versioning strategy for ONAP.
The intent of this page is to capture as much information as possible that occurred during working team discussion(s). It does not mean guidance or a solution has been finalized.
The artifacts/meeting notes contained on this page should not be considered to be the "official" API versioning standard for ONAP, but rather it is the detail of the collaboration taking place amongst the working team.
ONAP CVS Proposal Deck was presented to the Architecture Committee on 4/3/2018, prompting the formation of this working team.
Clarification on terminology used for discussion(s):
- SHALL (mandatory) is used to indicate a requirement that is contractually binding, meaning it must be implemented, and its implementation verified.
- SHOULD (non-mandatory) is used to indicate a goal which must be addressed by the design team, but is not formally verified.
Working Team Members
| Name | Company | Phone Number | TIme Zone | |
|---|---|---|---|---|
| AT&T | dw2049@att.com | (561) 371-7619 | EST | |
| AMDOCS | sharon.chisholm@amdocs.com | |||
| Huawei | Christopher.Donley@huawei.com | |||
| AT&T | gg2147@att.com | (847) 420-8459 | ||
| Mark Ho | AT&T | mh574f@att.com | (781) 791-4345 | EST |
| VMware | ramkik@vmware.com | |||
| OAM Technologies | adolfo.perez-duran@oamtechnologies.com | |||
| Intel | alex.vul@intel.com | |||
| Huawei | Parviz.Yegani@huawei.com |
* Responsible team lead
Discussion Items
Kick-off meeting scheduled for 4/5/2018 at 1000 EST
Clarification on terminology:
- SHALL (mandatory) is used to indicate a requirement that is contractually binding, meaning it must be implemented, and its implementation verified.
- SHOULD (non-mandatory) is used to indicate a goal which must be addressed by the design team, but is not formally verified.
Item | What | Notes |
|---|---|---|
| 1 |