User Tools

Site Tools


wiki:tsc:tscpolicydraftjan2016

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revision Previous revision
Next revision
Previous revision
wiki:tsc:tscpolicydraftjan2016 [2016/01/29 13:33]
Christopher Price
wiki:tsc:tscpolicydraftjan2016 [2016/02/09 17:22] (current)
Ray Paik [OPNFV TSC Policy]
Line 22: Line 22:
   * **Openness**:​ The TSC should ensure that all technical decisions are made in an open and transparent fashion.   * **Openness**:​ The TSC should ensure that all technical decisions are made in an open and transparent fashion.
  
-The TSC will review projects based on their scope in accordance with the overall purpose of OPNFV as defined in the bylaws (see section 1.4 of the bylaws). Projects may focus on any of the ETSI NFV architecture functional blocks, reference points, additional architectural functional blocks, supporting tools and infrastructure.  ​+The TSC will review projects based on their scope in accordance with the overall purpose of OPNFV as defined in the bylaws (see section 1.4 of the bylaws). Projects may focus on any of the ETSI NFV architecture functional blocks, reference points, supporting tools and infrastructure.  ​
    
 The ETSI Framework is provided here for reference: The ETSI Framework is provided here for reference:
 +
 [insert block diagram] [insert block diagram]
    
Line 40: Line 41:
   *   ​Vn-Nf:​ The reference point between NFVI and a Virtualised Network Function (VNF)   *   ​Vn-Nf:​ The reference point between NFVI and a Virtualised Network Function (VNF)
   *   ​Or-Vnfm:​ The reference point between the Orchestrator and a VNFM   *   ​Or-Vnfm:​ The reference point between the Orchestrator and a VNFM
-  *   ​Vi-Vnfm:​ The reference point between a VNF Manager (VNFMand the VIM+  *   ​Vi-Vnfm:​ The reference point between a VNFM and the VIM
   *   ​Or-Vi:​ The reference point between the Orchestrator and the VIM   *   ​Or-Vi:​ The reference point between the Orchestrator and the VIM
   *   ​Nf-Vi:​ The reference point between the VIM and the NFVI   *   ​Nf-Vi:​ The reference point between the VIM and the NFVI
   *   ​Os-Ma:​ The reference point between a consumer-side OSS/BSS and the Management and Orchestration   *   ​Os-Ma:​ The reference point between a consumer-side OSS/BSS and the Management and Orchestration
   *   ​Ve-Vnfm:​ The reference point between the VNF/EMS and a VNFM   *   ​Ve-Vnfm:​ The reference point between the VNF/EMS and a VNFM
-  *   ​Se-MaA:​ The reference point between the Service, VNF, and Infrastructure Description and the NFV Management and Orchestration 
    
 Additional details about architecture,​ functional blocks and reference points can be found in the ETSI NFV Architectural Framework [1].  Note that some of the functional blocks may be further decomposed if required, while still staying within the overall ETSI NFV architectural framework. ​ Additional details about architecture,​ functional blocks and reference points can be found in the ETSI NFV Architectural Framework [1].  Note that some of the functional blocks may be further decomposed if required, while still staying within the overall ETSI NFV architectural framework. ​
    
-[1]  ETSI GS NFV 002 v1.1.1, Network Functions Virtualisation;​ Architectural Framework, ​http://​www.etsi.org/​deliver/​etsi_gs/​NFV/​001_099/​002/​01.01.01_60/gs_NFV002v010101p.pdf+[1]  ETSI GS NFV 002 v1.2.1, Network Functions Virtualisation;​ Architectural Framework, ​https://​www.etsi.org/​deliver/​etsi_gs/​NFV/​001_099/​002/​01.02.01_60/gs_NFV002v010201p.pdf 
  
 Related Documents: Related Documents:
Line 56: Line 56:
  
 OPNFV Project Lifecycle OPNFV Project Lifecycle
- 
wiki/tsc/tscpolicydraftjan2016.1454074384.txt.gz ยท Last modified: 2016/01/29 13:33 by Christopher Price