wiki:tsc:tscpolicydraftjan2016
Differences
This shows you the differences between two versions of the page.
| Both sides previous revision Previous revision | |||
|
wiki:tsc:tscpolicydraftjan2016 [2016/02/09 13:41] Gerald Kunzmann [OPNFV TSC Policy] fixed typo MaA -> Ma |
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: | ||
| Line 46: | Line 46: | ||
| * 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-Ma: 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 57: | Line 56: | ||
| OPNFV Project Lifecycle | OPNFV Project Lifecycle | ||
| - | |||
wiki/tsc/tscpolicydraftjan2016.1455025313.txt.gz · Last modified: 2016/02/09 13:41 by Gerald Kunzmann
Page Tools
Except where otherwise noted, content on this wiki is licensed under the following license: Creative Commons Attribution 4.0 International License
