Types that doesn't comply with the Tosca or ESTI NFV SOL001 or Tosca-nfv syntax

Specification reference:

TOSCA Simple Profile YAML 1.2 Referecne:  http://docs.oasis-open.org/tosca/TOSCA-Simple-Profile-YAML/v1.2/TOSCA-Simple-Profile-YAML-v1.2.html  [TOSCA-YAML-1.2]

ESTI NFV-SOL 001 V2.5.1 Reference: https://www.etsi.org/deliver/etsi_gs/NFV-SOL/001_099/001/02.05.01_60/gs_NFV-SOL001v020501p.pdf  [SOL001]

                                                           https://www.etsi.org/deliver/etsi_gs/NFV-SOL/001_099/001/02.05.01_60/gs_NFV-SOL001v020501p0.zip (YAML definitions)

TOSCA Simple Profile YAML NFV 1.0 Referecne:  http://docs.oasis-open.org/tosca/tosca-nfv/v1.0/tosca-nfv-v1.0.html [TOSCA-NFV]  (According to Former user (Deleted)TOSCA-NFV's conent has already been incorporated by the early version of  [SOL001], and no longer being updated).

Analysis by different types

According to the analysis results, the model problems found can be summarized into four categories：

• A :  Not comply with tosca grammar 
  This classification is used to record types that don't comply with the basic tosca  syntax specification
  
  
• B1:  Not comply with existing TOSCA-simple-YAML-1.2
• B2: Not comply with existing SOL001-v2.5.1
  Type definitions quite like the types which defined in specification, but still have some difference， such as base type difference, property difference, etc
  
  
  
• C:  SDC private extension 
  This classification is used to record SDC private extension 
  
  
• D:  Use Case private extension
  This classification is used to record  the extension types which used to support specific use case 
  
  

R3 CSAR 

vCPE：

CCVPN: