MEC URN namespace: Difference between revisions

From MECwiki
Jump to: navigation, search
No edit summary
No edit summary
(2 intermediate revisions by the same user not shown)
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:&lt;MEC sub-tree&gt;</pre>
<pre>urn:etsi:mec:&lt;MEC sub-tree&gt;</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 specifications defined by ETSI ISG MEC. The following ETSI MEC specifications define LCM coordination actions:  
<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>
<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  
[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>
Line 38: 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).

Revision as of 13:34, 28 April 2021

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 can be found on the ETSI webpage 1. The MEC URN namespace has the following structure:

urn:etsi:mec:<MEC sub-tree>

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

MEC sub-tree

MEC sub-tree Full Namespace Type Description
coord urn:etsi:mec:coord string 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:
  • ETSI GS MEC 010-2 v2.2.1 (to be published at 2).

Type definitions

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}

Adding an entry (for ETSI ISG MEC group only)

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.

Pre-condition: 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).