MEC URN namespace - Revision history

Featherston1: Changed https to http to avoid a "lock icon" being presented

2024-03-25T15:00:27Z

Changed https to http to avoid a "lock icon" being presented

← Older revision		Revision as of 16:00, 25 March 2024
Line 1:		Line 1:
	<h3> Introduction</h3>		<h3> Introduction</h3>
	ETSI ISG MEC is maintaining a namespace registry as a sub tree of the ETSI root <nowiki>urn:etsi</nowiki> namespace. A description of the top level ETSI URN namespace can be found on the ETSI webpage [~~https~~://portal.etsi.org/PNNS/GenericAllocation/ETSIURNNamespace.aspx [1]]. The MEC URN namespace has the following structure:		ETSI ISG MEC is maintaining a namespace registry as a sub tree of the ETSI root <nowiki>urn:etsi</nowiki> namespace. A description of the top level ETSI URN namespace can be found on the ETSI webpage [http://portal.etsi.org/PNNS/GenericAllocation/ETSIURNNamespace.aspx [1]]. The MEC URN namespace has the following structure:
	<pre>urn:etsi:mec:<MEC sub-tree></pre>		<pre>urn:etsi:mec:<MEC sub-tree></pre>

Line 18:		Line 18:
	\|The namespace for Lifecycle management (LCM) coordination actions specified in group specifications defined by ETSI ISG MEC. The following ETSI MEC specifications define LCM coordination actions:		\|The namespace for Lifecycle management (LCM) coordination actions specified in group specifications defined by ETSI ISG MEC. The following ETSI MEC specifications define LCM coordination actions:
	<ul>		<ul>
	<li>ETSI GS MEC 010-2 v2.2.1 onwards (published at [[~~https~~://www.etsi.org/deliver/etsi_gs/MEC/001_099/01002/ 2]]).</li>		<li>ETSI GS MEC 010-2 v2.2.1 onwards (published at [[http://www.etsi.org/deliver/etsi_gs/MEC/001_099/01002/ 2]]).</li>
	</ul>		</ul>
	\|-		\|-
Line 26:		Line 26:
	\|The namespace for CAPIF extensions specified in group specifications defined by ETSI ISG MEC. The following ETSI MEC specifications define CAPIF extensions:		\|The namespace for CAPIF extensions specified in group specifications defined by ETSI ISG MEC. The following ETSI MEC specifications define CAPIF extensions:

	* ETSI GS MEC 011 v3.2.1 (published at [[~~https~~://www.etsi.org/deliver/etsi_gs/mec/001_099/011/ 3]])		* ETSI GS MEC 011 v3.2.1 (published at [[http://www.etsi.org/deliver/etsi_gs/mec/001_099/011/ 3]])
	\|}		\|}

Featherston1: Added "onwards" to indicate that versions later than 010-2 V2.2.1 are valid too

2024-03-25T11:31:08Z

Added "onwards" to indicate that versions later than 010-2 V2.2.1 are valid too

← Older revision		Revision as of 12:31, 25 March 2024
Line 1:		Line 1:
	<h3> Introduction</h3>		<h3> Introduction</h3>
	ETSI ISG MEC is maintaining a namespace registry as a sub tree of the ETSI root <nowiki>urn:etsi</nowiki> namespace. A description of the top level ETSI URN namespace can be found on the ETSI webpage [https://portal.etsi.org/PNNS/GenericAllocation/ETSIURNNamespace.aspx 1]. The MEC URN namespace has the following structure:		ETSI ISG MEC is maintaining a namespace registry as a sub tree of the ETSI root <nowiki>urn:etsi</nowiki> namespace. A description of the top level ETSI URN namespace can be found on the ETSI webpage [https://portal.etsi.org/PNNS/GenericAllocation/ETSIURNNamespace.aspx [1]]. The MEC URN namespace has the following structure:
	<pre>urn:etsi:mec:<MEC sub-tree></pre>		<pre>urn:etsi:mec:<MEC sub-tree></pre>

Line 18:		Line 18:
	\|The namespace for Lifecycle management (LCM) coordination actions specified in group specifications defined by ETSI ISG MEC. The following ETSI MEC specifications define LCM coordination actions:		\|The namespace for Lifecycle management (LCM) coordination actions specified in group specifications defined by ETSI ISG MEC. The following ETSI MEC specifications define LCM coordination actions:
	<ul>		<ul>
	<li>ETSI GS MEC 010-2 v2.2.1 (published at [[https://www.etsi.org/deliver/etsi_gs/MEC/001_099/01002/ 2]]).</li>		<li>ETSI GS MEC 010-2 v2.2.1 onwards (published at [[https://www.etsi.org/deliver/etsi_gs/MEC/001_099/01002/ 2]]).</li>
	</ul>		</ul>
	\|-		\|-

Featherston1: Implementation of MECDECODE(24)000007

2024-03-23T03:13:58Z

Implementation of MECDECODE(24)000007

← Older revision		Revision as of 04:13, 23 March 2024
Line 18:		Line 18:
	\|The namespace for Lifecycle management (LCM) coordination actions specified in group specifications defined by ETSI ISG MEC. The following ETSI MEC specifications define LCM coordination actions:		\|The namespace for Lifecycle management (LCM) coordination actions specified in group specifications defined by ETSI ISG MEC. The following ETSI MEC specifications define LCM coordination actions:
	<ul>		<ul>
	<li>ETSI GS MEC 010-2 v2.2.1 (~~to be~~ published at		<li>ETSI GS MEC 010-2 v2.2.1 (published at [[https://www.etsi.org/deliver/etsi_gs/MEC/001_099/01002/ 2]]).</li>
	[https://www.etsi.org/deliver/etsi_gs/MEC/001_099/01002/ 2]).</li>
	</ul>		</ul>
			\|-
			\|capifext
			\|<nowiki>urn:etsi:mec:capifext</nowiki>
			\|string
			\|The namespace for CAPIF extensions specified in group specifications defined by ETSI ISG MEC. The following ETSI MEC specifications define CAPIF extensions:

			* ETSI GS MEC 011 v3.2.1 (published at [[https://www.etsi.org/deliver/etsi_gs/mec/001_099/011/ 3]])
	\|}		\|}

Rauschenbac at 13:34, 28 April 2021

2021-04-28T13:34:54Z

← Older revision		Revision as of 14:34, 28 April 2021
Line 33:		Line 33:

	<h3>Adding an entry (for ETSI ISG MEC group only)</h3>		<h3>Adding an entry (for ETSI ISG MEC group only)</h3>
	A new MEC sub-tree can only be requested by an the ETSI MEC ISG and ~~their~~ its working groups, by making a contribution to ETSI ISG MEC (DECODE).		A new MEC sub-tree can only be requested by the ETSI MEC ISG and its working groups, by making a contribution to ETSI ISG MEC DECODE.

	<b>Pre-condition:</b> a MEC work item running has identified the need to enable a URN namespace. A contact person to formalize the request has been identified (e.g., a technical group official such as a WG Chair, the work item rapporteur or the author of the CR that introduces the new namespace subtree in the specification).		<b>Pre-condition:</b> a MEC work item running has identified the need to enable a URN namespace. A contact person to formalize the request has been identified (e.g., a technical group official such as a WG Chair, the work item rapporteur or the author of the CR that introduces the new namespace subtree in the specification).

Rauschenbac at 13:32, 28 April 2021

2021-04-28T13:32:04Z

← Older revision		Revision as of 14:32, 28 April 2021
Line 16:		Line 16:
	\|<nowiki>urn:etsi:mec:coord</nowiki>		\|<nowiki>urn:etsi:mec:coord</nowiki>
	\|string		\|string
	\|The namespace for Lifecycle management (LCM) coordination actions specified in group		\|The namespace for Lifecycle management (LCM) coordination actions specified in group specifications defined by ETSI ISG MEC. The following ETSI MEC specifications define LCM coordination actions:
	specifications defined by ETSI ISG MEC. The following ETSI MEC specifications define LCM coordination actions:
	<ul>		<ul>
	<li>ETSI GS MEC 010-2 v2.2.1 (to be published at		<li>ETSI GS MEC 010-2 v2.2.1 (to be published at

Rauschenbac at 13:31, 28 April 2021

2021-04-28T13:31:36Z

← Older revision		Revision as of 14:31, 28 April 2021
Line 1:		Line 1:
	<h3> Introduction</h3>		<h3> Introduction</h3>
	ETSI ISG MEC is maintaining a namespace registry as a sub tree of the ETSI root ~~URN~~ namespace. A description of the top level ETSI URN namespace can be found on the ETSI webpage [https://portal.etsi.org/PNNS/GenericAllocation/ETSIURNNamespace.aspx 1]. The ~~NFV~~ URN namespace has the following structure:		ETSI ISG MEC is maintaining a namespace registry as a sub tree of the ETSI root <nowiki>urn:etsi</nowiki> namespace. A description of the top level ETSI URN namespace can be found on the ETSI webpage [https://portal.etsi.org/PNNS/GenericAllocation/ETSIURNNamespace.aspx 1]. The MEC URN namespace has the following structure:
	<pre>urn:etsi:mec:<MEC sub-tree></pre>		<pre>urn:etsi:mec:<MEC sub-tree></pre>

Line 6:		Line 6:

	<h3>MEC sub-tree</h3>		<h3>MEC sub-tree</h3>
	~~<table>~~		{\| class="wikitable"
	~~<th>~~		\|+
	~~<td>~~MEC sub-tree~~</td>~~		!MEC sub-tree
	~~<td>~~Full Namespace~~</td>~~		!Full Namespace
	~~<td>~~Type~~</td>~~		!Type
	~~<td>~~Description~~</td>~~		!Description
	~~</th>~~		\|-
			\|coord
	~~<tr>~~		\|<nowiki>urn:etsi:mec:coord</nowiki>
	~~<td>~~coord~~</td>~~		\|string
	<td>urn:etsi:~~nfv~~:coord</td>		\|The namespace for Lifecycle management (LCM) coordination actions specified in group
	~~<td>~~string~~</td>~~
	~~<td>~~The namespace for ~~Llifecycle~~ management (LCM) coordination actions specified in group
	specifications defined by ETSI ISG MEC. The following ETSI MEC specifications define LCM coordination actions:		specifications defined by ETSI ISG MEC. The following ETSI MEC specifications define LCM coordination actions:
	<ul>		<ul>
Line 24:		Line 22:
	[https://www.etsi.org/deliver/etsi_gs/MEC/001_099/01002/ 2]).</li>		[https://www.etsi.org/deliver/etsi_gs/MEC/001_099/01002/ 2]).</li>
	</ul>		</ul>
	~~</td>~~		\|}
	~~</tr>~~
	~~</table>~~

	<h3>Type definitions</h3>		<h3>Type definitions</h3>

Rauschenbac at 13:26, 28 April 2021

2021-04-28T13:26:03Z

← Older revision		Revision as of 14:26, 28 April 2021
Line 1:		Line 1:
	<h3> Introduction</h3>		<h3> Introduction</h3>
	ETSI ISG MEC is maintaining a namespace registry as a sub tree of the ETSI root ~~urn:etsi~~ namespace. A description of the top level ETSI URN namespace can be found on the ETSI webpage [https://portal.etsi.org/PNNS/GenericAllocation/ETSIURNNamespace.aspx 1]. The NFV URN namespace has the following structure:		ETSI ISG MEC is maintaining a namespace registry as a sub tree of the ETSI root URN namespace. A description of the top level ETSI URN namespace can be found on the ETSI webpage [https://portal.etsi.org/PNNS/GenericAllocation/ETSIURNNamespace.aspx 1]. The NFV URN namespace has the following structure:
	<pre>urn:etsi:mec:<MEC sub-tree></pre>		<pre>urn:etsi:mec:<MEC sub-tree></pre>

Line 7:		Line 7:
	<h3>MEC sub-tree</h3>		<h3>MEC sub-tree</h3>
	<table>		<table>
	<tr>		<th>
	<td>MEC sub-tree</td>		<td>MEC sub-tree</td>
	<td>Full Namespace</td>		<td>Full Namespace</td>
	<td>Type</td>		<td>Type</td>
	<td>Description</td>		<td>Description</td>
	</tr>		</th>

	<tr>		<tr>
Line 19:		Line 19:
	<td>string</td>		<td>string</td>
	<td>The namespace for Llifecycle management (LCM) coordination actions specified in group		<td>The namespace for Llifecycle management (LCM) coordination actions specified in group
	specifications defined by ETSI ISG MEC.		specifications defined by ETSI ISG MEC. The following ETSI MEC specifications define LCM coordination actions:

	The following ETSI MEC specifications define LCM coordination actions:
	<ul>		<ul>
	<li>ETSI GS MEC 010-2 v2.2.1 (to be published at		<li>ETSI GS MEC 010-2 v2.2.1 (to be published at

Rauschenbac at 13:24, 28 April 2021

2021-04-28T13:24:33Z

← Older revision		Revision as of 14:24, 28 April 2021
Line 26:		Line 26:
	[https://www.etsi.org/deliver/etsi_gs/MEC/001_099/01002/ 2]).</li>		[https://www.etsi.org/deliver/etsi_gs/MEC/001_099/01002/ 2]).</li>
	</ul>		</ul>
			</td>
			</tr>
			</table>

	<h3>Type definitions</h3>		<h3>Type definitions</h3>

Rauschenbac: Created page with "

Introduction

ETSI ISG MEC is maintaining a namespace registry as a sub tree of the ETSI root urn:etsi namespace. A description of the top level ETSI URN namespace ca..."

2021-04-28T13:23:46Z

Created page with "<h3> Introduction</h3> ETSI ISG MEC is maintaining a namespace registry as a sub tree of the ETSI root urn:etsi namespace. A description of the top level ETSI URN namespace ca..."

New page

<h3> Introduction</h3>
ETSI ISG MEC is maintaining a namespace registry as a sub tree of the ETSI root urn:etsi namespace. A description of the top level ETSI URN namespace can be found on the ETSI webpage [https://portal.etsi.org/PNNS/GenericAllocation/ETSIURNNamespace.aspx 1]. The NFV URN namespace has the following structure:
<pre>urn:etsi:mec:<MEC sub-tree></pre>

The following sections describe the basic structure of the sub-tree and how an entry in the registry can be requested.

<h3>MEC sub-tree</h3>
<table>
<tr>
<td>MEC sub-tree</td>
<td>Full Namespace</td>
<td>Type</td>
<td>Description</td>
</tr>

<tr>
<td>coord</td>
<td>urn:etsi:nfv:coord</td>
<td>string</td>
<td>The namespace for Llifecycle management (LCM) coordination actions specified in group
specifications defined by ETSI ISG MEC.

The following ETSI MEC specifications define LCM coordination actions:
<ul>
<li>ETSI GS MEC 010-2 v2.2.1 (to be published at
[https://www.etsi.org/deliver/etsi_gs/MEC/001_099/01002/ 2]).</li>
</ul>

<h3>Type definitions</h3>
<pre>
string = 1*(ALPHANUMERIC/-/_)
# a string should contain one or more upper- or lower-case letters, integer numbers, hyphens or underscores

ALPHA = {a-zA-Z}
ALPHANUMERIC = {a-zA-Z0-9}
</pre>

<h3>Adding an entry (for ETSI ISG MEC group only)</h3>
A new MEC sub-tree can only be requested by an the ETSI MEC ISG and their its working groups, by making a contribution to ETSI ISG MEC (DECODE).

<b>Pre-condition:</b> a MEC work item running has identified the need to enable a URN namespace. A contact person to formalize the request has been identified (e.g., a technical group official such as a WG Chair, the work item rapporteur or the author of the CR that introduces the new namespace subtree in the specification).