Difference between revisions of "NFV URN Namespace"

From NFVwiki
Jump to: navigation, search
(Moving "NFVURN Page" from private wiki to public wiki.)
 
m (Requesting an entry (for ETSI technical bodies only))
Line 35: Line 35:
  
 
* '''Pre-condition:''' a work item running in the WG has identified the need to enable a URN namespace. A contact person to formalize the request has been identified (e.g., a WG official such as the WG Chair, the work item rapporteur).
 
* '''Pre-condition:''' a work item running in the WG has identified the need to enable a URN namespace. A contact person to formalize the request has been identified (e.g., a WG official such as the WG Chair, the work item rapporteur).
* ''Step #1:'' Download the "URN namespace application template" in contribution [https://portal.etsi.org/ngppapp/ContributionCreation.aspx?primarykeys=168857&source=QIGSBIKSHQAZ NFVTSC(19)000003]
+
* ''Step #1:'' Download the "URN namespace application template" in contribution [https://docbox.etsi.org/ISG/NFV/TSC/05-CONTRIBUTIONS/2019//NFVTSC(19)000003r2_Template_for_URN_namespace_applications.docx NFVTSC(19)000003]
 
* ''Step #2:'' Fill in the template and submit it as a contribution under the "NFV TSC" workspace of the ETSI Portal.
 
* ''Step #2:'' Fill in the template and submit it as a contribution under the "NFV TSC" workspace of the ETSI Portal.
 
* ''Step #3:'' The TSC will review the application.
 
* ''Step #3:'' The TSC will review the application.
 
** If the application is accepted, a new entry in the "NFV URN Namespace" will be enabled.
 
** If the application is accepted, a new entry in the "NFV URN Namespace" will be enabled.
 
** If the application cannot be accepted, it will be communicated to the contact person together with any additional information to be considered for resolving the "non-acceptance".
 
** If the application cannot be accepted, it will be communicated to the contact person together with any additional information to be considered for resolving the "non-acceptance".

Revision as of 08:46, 23 April 2019

Introduction

ETSI ISG NFV 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 NFV URN namespace has the following structure:

urn:etsi:nfv:<NFV sub-tree>

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

NFV sub-tree

NFV sub-tree Full Namespace Type Description
yang:etsi-nfv-descriptors
urn:etsi:nfv:yang:etsi-nfv-descriptors
string Namespace for YANG modules specified in ETSI GS NFV-SOL 006.

Latest draft of SOL006

Type definitions

string = (ALPHA)0*(ALPHANUMERIC/-/_)
# a string starts with an upper- or lower-case letter followed by zero or more upper- or lower-case letters, integer numbers, hyphens or underscores

ALPHA = {a-zA-Z}
ALPHANUMERIC = {a-zA-Z0-9}

Requesting an entry (for ETSI technical bodies only)

A new NFV sub-tree can only be requested by a ETSI technical body.

To request a sub-tree please follow the guide below.

  • Pre-condition: a work item running in the WG has identified the need to enable a URN namespace. A contact person to formalize the request has been identified (e.g., a WG official such as the WG Chair, the work item rapporteur).
  • Step #1: Download the "URN namespace application template" in contribution NFVTSC(19)000003
  • Step #2: Fill in the template and submit it as a contribution under the "NFV TSC" workspace of the ETSI Portal.
  • Step #3: The TSC will review the application.
    • If the application is accepted, a new entry in the "NFV URN Namespace" will be enabled.
    • If the application cannot be accepted, it will be communicated to the contact person together with any additional information to be considered for resolving the "non-acceptance".