1. Discussion of Publishing CSD03 version of NFV Profile
John Crandall

2. Publish CSD03 version of NFV Profile as CS
Reflects the work that has been done for the last two years.
Rename the document
Rename as Profile for Network Functions Virtualization (NFV) based on phase 1 implementation
Change wording in csd03 to emphasize it will not be revised except for editorial cleanup.
Add pointer to replacement document.
Promote only as a Committee Specification
Not an OASIS standard
Recognition that there is a clear difference in both data and deployment models between ETSI MAN001 and ETSI IFA versions.
Allows for faster adoption/consumption for the latest IFA specification.

3. Update convention statement
Express the ETSI IFA specification using existing TOSCA normative types in the TOSCA Simple Profile 1.2 and TOSCA NFV Profile Committee Specification Draft 03 as much as when possible. New types will be created expressing ETSI IFA concepts and information not already available in TOSCA.
Express the subset of ETSI IFA information required for correct orchestration.
It is not required that the TOSCA NFV profile match ETSI IFA information model entities with the same names or representation.
The TOSCA NFV Profile will clearly identify the information from ESTI IFA that it will express and the mapping between the TOSCA and ESTI IF information models.
TOSCA types created to support ETSI IFA for each version of the TOSCA NFV profile must evolve in a manner that support combining older and newer types in the same service template (i.e. you don’t have to change old templates or parts of a template to support the new types).
Editor note: It was expressed on the AdHoc call that inheritance and artifacts should be used to incorporate the IFA additions. Should this be explicitly stated?