PoC Topics - Revision history

Carignani at 13:53, 18 September 2018

2018-09-18T13:53:02Z

← Older revision		Revision as of 14:53, 18 September 2018
Line 1:		Line 1:
	= Rationale =		= Rationale =
	PoC Topics are specific areas, often linked to a Work Item, where input or feedback from the AFI Proofs of Concept is needed. AFI PoC Topics help to focus PoC Projects on the most relevant topics for TC ~~NTECH~~/AFI, and to increase the relevance of their contributions.		PoC Topics are specific areas, often linked to a Work Item, where input or feedback from the AFI Proofs of Concept is needed. AFI PoC Topics help to focus PoC Projects on the most relevant topics for TC INT/AFI, and to increase the relevance of their contributions.

	~~NTECH~~/AFI PoC Topics are identified and documented by ~~NTECH~~ AFI WG. ~~NTECH~~/AFI PoC Topics may include templates for the PoC Contributions and deadlines to ensure that the PoC Contributions arrive on-time to be taken into account by the targeted WIs.		INT/AFI PoC Topics are identified and documented by INT AFI WG. INT/AFI PoC Topics may include templates for the PoC Contributions and deadlines to ensure that the PoC Contributions arrive on-time to be taken into account by the targeted WIs.

	= AFI PoC Topics =		= AFI PoC Topics =
Line 192:		Line 192:

	= Feeding back the results =		= Feeding back the results =
	As soon as experimental results relevant for a given ~~NTECH~~/AFI PoC Topic are available (no need to wait for the PoC Project to be completed), the PoC Team creates a contribution and informs the ~~NTECH~~ AFI WG by email (if the PoC Topic had a specific template for feedback contributions, it should be used). PoC Teams are also encouraged to contribute additional results and lessons learned during the PoC Project to the ~~NTECH~~ AFI WG.		As soon as experimental results relevant for a given INT/AFI PoC Topic are available (no need to wait for the PoC Project to be completed), the PoC Team creates a contribution and informs the INT AFI WG by email (if the PoC Topic had a specific template for feedback contributions, it should be used). PoC Teams are also encouraged to contribute additional results and lessons learned during the PoC Project to the INT AFI WG.

	A generic PoC Feedback Template is available in [[PoC Framework]]		A generic PoC Feedback Template is available in [[PoC Framework]]

	= ~~NTECH~~ / AFI Deliverables =		= INT / AFI Deliverables =
	{\| class="wikitable"		{\| class="wikitable"
	! style="font-weight: bold;" \| Deliverable number / WI Code		! style="font-weight: bold;" \| Deliverable number / WI Code

Almagia: /* Addressing a PoC Topic in a PoC Project */

2016-01-14T14:52:13Z

Addressing a PoC Topic in a PoC Project

← Older revision		Revision as of 15:52, 14 January 2016
Line 189:		Line 189:
	PoC Teams specify the targeted PoC Topic(s) in their PoC Proposal, and commit to provide the expected contribution (input or feedback) in the requested format (template, if applicable) in a timely manner.		PoC Teams specify the targeted PoC Topic(s) in their PoC Proposal, and commit to provide the expected contribution (input or feedback) in the requested format (template, if applicable) in a timely manner.

	For each PoC Topic ~~adressed~~, one or several Test Descriptions should be provided.		For each PoC Topic addressed, one or several Test Descriptions should be provided.

	= Feeding back the results =		= Feeding back the results =

Almagia: /* Addressing a PoC Topic in a PoC Project */

2016-01-14T14:29:00Z

Addressing a PoC Topic in a PoC Project

← Older revision		Revision as of 15:29, 14 January 2016
Line 188:		Line 188:
	= Addressing a PoC Topic in a PoC Project =		= Addressing a PoC Topic in a PoC Project =
	PoC Teams specify the targeted PoC Topic(s) in their PoC Proposal, and commit to provide the expected contribution (input or feedback) in the requested format (template, if applicable) in a timely manner.		PoC Teams specify the targeted PoC Topic(s) in their PoC Proposal, and commit to provide the expected contribution (input or feedback) in the requested format (template, if applicable) in a timely manner.

			For each PoC Topic adressed, one or several Test Descriptions should be provided.

	= Feeding back the results =		= Feeding back the results =

Almagia at 14:27, 14 January 2016

2016-01-14T14:27:52Z

← Older revision		Revision as of 15:27, 14 January 2016
Line 183:		Line 183:

	(*) TBC - New Work Item To Be Created.		(*) TBC - New Work Item To Be Created.

	(**) Note: One recognized combination is based on the “Unified Architectural Framework” that combines AMC, SDN, NFV, and E2E Orchestration Reference Models, emerging from the Joint SDOs/Fora Initiative on Industry Harmonization for Unified Standards on Autonomic Management & Control of Networks and Services, SDN, NFV, E2E Orchestration (see http://www.tmforumlive.org/workshops/#tab-ieee-workshop-on-autonomics)		(**) Note: One recognized combination is based on the “Unified Architectural Framework” that combines AMC, SDN, NFV, and E2E Orchestration Reference Models, emerging from the Joint SDOs/Fora Initiative on Industry Harmonization for Unified Standards on Autonomic Management & Control of Networks and Services, SDN, NFV, E2E Orchestration (see http://www.tmforumlive.org/workshops/#tab-ieee-workshop-on-autonomics)

Almagia at 14:27, 14 January 2016

2016-01-14T14:27:29Z

← Older revision		Revision as of 15:27, 14 January 2016
Line 70:		Line 70:
	\| ACTIVE		\| ACTIVE
	\| ETSI GS AFI 002		\| ETSI GS AFI 002
	\| TBC*		\| TBC (*)
	\| Technical Report		\| Technical Report
	\| Q4 2017		\| Q4 2017
Line 79:		Line 79:
	\| ACTIVE		\| ACTIVE
	\| ETSI GS AFI 002		\| ETSI GS AFI 002
	\| TBC*		\| TBC (*)
	\| Technical Report		\| Technical Report
	\| Q4 2017		\| Q4 2017
Line 88:		Line 88:
	\| ACTIVE		\| ACTIVE
	\| ETSI GS AFI 002		\| ETSI GS AFI 002
	\| TBC*		\| TBC(*)
	\| Technical Report		\| Technical Report
	\| Q4 2017		\| Q4 2017
Line 97:		Line 97:
	\| ACTIVE		\| ACTIVE
	\| ETSI GS AFI 002		\| ETSI GS AFI 002
	\| TBC*		\| TBC(*)
	\| Technical Report		\| Technical Report
	\| Q4 2017		\| Q4 2017
Line 106:		Line 106:
	\| ACTIVE		\| ACTIVE
	\| ETSI GS AFI 002		\| ETSI GS AFI 002
	\| TBC*		\| TBC(*)
	\| Technical Report		\| Technical Report
	\| Q4 2017		\| Q4 2017
Line 125:		Line 125:
	technologies, Software Defined Network (SDN),		technologies, Software Defined Network (SDN),
	Network Function Virtualization (NFV) and		Network Function Virtualization (NFV) and
	End to End orchestration.		End to End orchestration.(**)
	\| ACTIVE		\| ACTIVE
	\| DTR/NTECH-AFI-0020-GANA-impact		\| DTR/NTECH-AFI-0020-GANA-impact
Line 139:		Line 139:
	\| ACTIVE		\| ACTIVE
	\| ETSI GS AFI 002		\| ETSI GS AFI 002
	\| TBC*		\| TBC(*)
	\| Technical Report		\| Technical Report
	\| Q4 2017		\| Q4 2017
Line 177:		Line 177:
	\| ACTIVE		\| ACTIVE
	\| ETSI GS AFI 002		\| ETSI GS AFI 002
	\| TBC*		\| TBC(*)
	\| Technical Report		\| Technical Report
	\| Q4 2017		\| Q4 2017
	\|}		\|}

	TBC *: New Work Item ~~to be created~~.		(*) TBC - New Work Item To Be Created.
			(**) Note: One recognized combination is based on the “Unified Architectural Framework” that combines AMC, SDN, NFV, and E2E Orchestration Reference Models, emerging from the Joint SDOs/Fora Initiative on Industry Harmonization for Unified Standards on Autonomic Management & Control of Networks and Services, SDN, NFV, E2E Orchestration (see http://www.tmforumlive.org/workshops/#tab-ieee-workshop-on-autonomics)

	= Addressing a PoC Topic in a PoC Project =		= Addressing a PoC Topic in a PoC Project =

Almagia: Undo revision 2653 by Almagia (talk)

2016-01-14T14:25:41Z

Undo revision 2653 by Almagia (talk)

← Older revision		Revision as of 15:25, 14 January 2016
Line 70:		Line 70:
	\| ACTIVE		\| ACTIVE
	\| ETSI GS AFI 002		\| ETSI GS AFI 002
	\| TBC (**)		\| TBC*
	\| Technical Report		\| Technical Report
	\| Q4 2017		\| Q4 2017
Line 79:		Line 79:
	\| ACTIVE		\| ACTIVE
	\| ETSI GS AFI 002		\| ETSI GS AFI 002
	\| TBC (**)		\| TBC*
	\| Technical Report		\| Technical Report
	\| Q4 2017		\| Q4 2017
Line 88:		Line 88:
	\| ACTIVE		\| ACTIVE
	\| ETSI GS AFI 002		\| ETSI GS AFI 002
	\| TBC (**)		\| TBC*
	\| Technical Report		\| Technical Report
	\| Q4 2017		\| Q4 2017
Line 97:		Line 97:
	\| ACTIVE		\| ACTIVE
	\| ETSI GS AFI 002		\| ETSI GS AFI 002
	\| TBC (**)		\| TBC*
	\| Technical Report		\| Technical Report
	\| Q4 2017		\| Q4 2017
Line 106:		Line 106:
	\| ACTIVE		\| ACTIVE
	\| ETSI GS AFI 002		\| ETSI GS AFI 002
	\| TBC (**)		\| TBC*
	\| Technical Report		\| Technical Report
	\| Q4 2017		\| Q4 2017
Line 125:		Line 125:
	technologies, Software Defined Network (SDN),		technologies, Software Defined Network (SDN),
	Network Function Virtualization (NFV) and		Network Function Virtualization (NFV) and
	End to End orchestration.~~(*)~~		End to End orchestration.
	\| ACTIVE		\| ACTIVE
	\| DTR/NTECH-AFI-0020-GANA-impact		\| DTR/NTECH-AFI-0020-GANA-impact
Line 139:		Line 139:
	\| ACTIVE		\| ACTIVE
	\| ETSI GS AFI 002		\| ETSI GS AFI 002
	\| TBC (**)		\| TBC*
	\| Technical Report		\| Technical Report
	\| Q4 2017		\| Q4 2017

Almagia at 14:25, 14 January 2016

2016-01-14T14:25:06Z

← Older revision		Revision as of 15:25, 14 January 2016
Line 70:		Line 70:
	\| ACTIVE		\| ACTIVE
	\| ETSI GS AFI 002		\| ETSI GS AFI 002
	\| TBC*		\| TBC (**)
	\| Technical Report		\| Technical Report
	\| Q4 2017		\| Q4 2017
Line 79:		Line 79:
	\| ACTIVE		\| ACTIVE
	\| ETSI GS AFI 002		\| ETSI GS AFI 002
	\| TBC*		\| TBC (**)
	\| Technical Report		\| Technical Report
	\| Q4 2017		\| Q4 2017
Line 88:		Line 88:
	\| ACTIVE		\| ACTIVE
	\| ETSI GS AFI 002		\| ETSI GS AFI 002
	\| TBC*		\| TBC (**)
	\| Technical Report		\| Technical Report
	\| Q4 2017		\| Q4 2017
Line 97:		Line 97:
	\| ACTIVE		\| ACTIVE
	\| ETSI GS AFI 002		\| ETSI GS AFI 002
	\| TBC*		\| TBC (**)
	\| Technical Report		\| Technical Report
	\| Q4 2017		\| Q4 2017
Line 106:		Line 106:
	\| ACTIVE		\| ACTIVE
	\| ETSI GS AFI 002		\| ETSI GS AFI 002
	\| TBC*		\| TBC (**)
	\| Technical Report		\| Technical Report
	\| Q4 2017		\| Q4 2017
Line 125:		Line 125:
	technologies, Software Defined Network (SDN),		technologies, Software Defined Network (SDN),
	Network Function Virtualization (NFV) and		Network Function Virtualization (NFV) and
	End to End orchestration.		End to End orchestration.(*)
	\| ACTIVE		\| ACTIVE
	\| DTR/NTECH-AFI-0020-GANA-impact		\| DTR/NTECH-AFI-0020-GANA-impact
Line 139:		Line 139:
	\| ACTIVE		\| ACTIVE
	\| ETSI GS AFI 002		\| ETSI GS AFI 002
	\| TBC*		\| TBC (**)
	\| Technical Report		\| Technical Report
	\| Q4 2017		\| Q4 2017

Almagia: /* Feeding back the results */

2015-10-08T13:36:06Z

Feeding back the results

← Older revision		Revision as of 14:36, 8 October 2015
Line 189:		Line 189:
	= Feeding back the results =		= Feeding back the results =
	As soon as experimental results relevant for a given NTECH/AFI PoC Topic are available (no need to wait for the PoC Project to be completed), the PoC Team creates a contribution and informs the NTECH AFI WG by email (if the PoC Topic had a specific template for feedback contributions, it should be used). PoC Teams are also encouraged to contribute additional results and lessons learned during the PoC Project to the NTECH AFI WG.		As soon as experimental results relevant for a given NTECH/AFI PoC Topic are available (no need to wait for the PoC Project to be completed), the PoC Team creates a contribution and informs the NTECH AFI WG by email (if the PoC Topic had a specific template for feedback contributions, it should be used). PoC Teams are also encouraged to contribute additional results and lessons learned during the PoC Project to the NTECH AFI WG.

			A generic PoC Feedback Template is available in [[PoC Framework]]

	= NTECH / AFI Deliverables =		= NTECH / AFI Deliverables =

Almagia: /* Addressing a PoC Topic in a PoC Project */

2015-10-08T13:35:53Z

Addressing a PoC Topic in a PoC Project

← Older revision		Revision as of 14:35, 8 October 2015
Line 186:		Line 186:
	= Addressing a PoC Topic in a PoC Project =		= Addressing a PoC Topic in a PoC Project =
	PoC Teams specify the targeted PoC Topic(s) in their PoC Proposal, and commit to provide the expected contribution (input or feedback) in the requested format (template, if applicable) in a timely manner.		PoC Teams specify the targeted PoC Topic(s) in their PoC Proposal, and commit to provide the expected contribution (input or feedback) in the requested format (template, if applicable) in a timely manner.

	~~A generic PoC Feedback Template is available in [[PoC Framework]]~~

	= Feeding back the results =		= Feeding back the results =

Almagia: /* Addressing a PoC Topic in a PoC Project */

2015-10-08T13:35:39Z

Addressing a PoC Topic in a PoC Project

← Older revision		Revision as of 14:35, 8 October 2015
Line 186:		Line 186:
	= Addressing a PoC Topic in a PoC Project =		= Addressing a PoC Topic in a PoC Project =
	PoC Teams specify the targeted PoC Topic(s) in their PoC Proposal, and commit to provide the expected contribution (input or feedback) in the requested format (template, if applicable) in a timely manner.		PoC Teams specify the targeted PoC Topic(s) in their PoC Proposal, and commit to provide the expected contribution (input or feedback) in the requested format (template, if applicable) in a timely manner.

			A generic PoC Feedback Template is available in [[PoC Framework]]

	= Feeding back the results =		= Feeding back the results =