https://nfvwiki.etsi.org/api.php?action=feedcontributions&user=Worndle&feedformat=atomNFVwiki - User contributions [en]2024-03-28T20:49:27ZUser contributionsMediaWiki 1.39.3https://nfvwiki.etsi.org/index.php?title=NFV_URN_Namespace&diff=3716NFV URN Namespace2021-05-17T13:24:10Z<p>Worndle: Added link to updated template as per decision in TSC#212</p>
<hr />
<div>=== Introduction ===<br />
ETSI ISG NFV is maintaining a namespace registry as a sub tree of the ETSI root <code><nowiki>urn:etsi</nowiki></code> 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].<br />
<br />
The NFV URN namespace has the following structure:<br />
<nowiki>urn:etsi:nfv</nowiki>:<NFV sub-tree><br />
The following sections describe the basic structure of the sub-tree and how a entry in the registry can be requested.<br />
<br />
=== NFV sub-tree ===<br />
{| class="wikitable"<br />
|+<br />
!NFV sub-tree<br />
!Full Namespace<br />
!Description<br />
|-<br />
|coord<br />
|<br />
<nowiki>urn:etsi:nfv:coord</nowiki><br />
|Namespace for public LCM coordination action names defined in ETSI NFV specifications, including [https://docbox.etsi.org/ISG/NFV/Open/Drafts/SOL002ed351_RESTful_protocols_spec ETSI GS NFV-SOL 002 v3.5.1] and later.<br />
|-<br />
|yang:etsi-nfv-descriptors<br />
|<br />
<nowiki>urn:etsi:nfv:yang:etsi-nfv-descriptors</nowiki><br />
|The namespace for YANG modules specified in ETSI GS NFV-SOL 006, available for download as [https://www.etsi.org/standards#page=1&search=NFV-SOL%20006&title=1&etsiNumber=1&content=0&version=1&onApproval=1&published=1&historical=1&startDate=1988-01-15&endDate=2021-05-03&harmonized=0&keyword=&TB=826,,835,,833,,789,,832,,831,,795,,796,,800,,798,,799,,848,,797,,828&stdType=&frequency=&mandate=&collection=&sort=1 ETSI GS NFV-SOL 006] and as a YANG specification in [https://forge.etsi.org/gitlab/nfv/SOL006/blob/master/src/yang/etsi-nfv-descriptors.yang etsi-nfv-descriptors.yang].<br />
|-<br />
|yang:etsi-nfv-vnfd<br />
|<br />
<nowiki>urn:etsi:nfv:yang:etsi-nfv-vnfd</nowiki><br />
|Namespace for the YANG module that is used to model a single VNFD, according to the YANG specification available in [https://forge.etsi.org/rep/nfv/SOL006/blob/v2.6.1/src/yang/etsi-nfv-vnfd.yang etsi-nfv-vnfd.yang] file and specified in [https://www.etsi.org/standards#page=1&search=NFV-SOL%20006&title=1&etsiNumber=1&content=0&version=1&onApproval=1&published=1&historical=1&startDate=1988-01-15&endDate=2021-05-03&harmonized=0&keyword=&TB=826,,835,,833,,789,,832,,831,,795,,796,,800,,798,,799,,848,,797,,828&stdType=&frequency=&mandate=&collection=&sort=1 ETSI GS NFV-SOL 006].<br />
|-<br />
|yang:etsi-nfv-nsd<br />
|<br />
<nowiki>urn:etsi:nfv:yang:etsi-nfv-nsd</nowiki><br />
|Namespace for the YANG module that is used to model a single NSD, according to the YANG specification available in [https://forge.etsi.org/rep/nfv/SOL006/blob/v2.6.1/src/yang/etsi-nfv-nsd.yang etsi-nfv-nsd.yang] file and specified in [https://www.etsi.org/standards#page=1&search=NFV-SOL%20006&title=1&etsiNumber=1&content=0&version=1&onApproval=1&published=1&historical=1&startDate=1988-01-15&endDate=2021-05-03&harmonized=0&keyword=&TB=826,,835,,833,,789,,832,,831,,795,,796,,800,,798,,799,,848,,797,,828&stdType=&frequency=&mandate=&collection=&sort=1 ETSI GS NFV-SOL 006].<br />
|-<br />
|yang:etsi-nfv-pnfd<br />
|<br />
<nowiki>urn:etsi:nfv:yang:etsi-nfv-pnfd</nowiki><br />
|Namespace for the YANG module that is used to model a single PNFD, according to the YANG specification available in [https://forge.etsi.org/rep/nfv/SOL006/blob/v2.6.1/src/yang/etsi-nfv-pnfd.yang etsi-nfv-pnfd.yang] file and specified in [https://www.etsi.org/standards#page=1&search=NFV-SOL%20006&title=1&etsiNumber=1&content=0&version=1&onApproval=1&published=1&historical=1&startDate=1988-01-15&endDate=2021-05-03&harmonized=0&keyword=&TB=826,,835,,833,,789,,832,,831,,795,,796,,800,,798,,799,,848,,797,,828&stdType=&frequency=&mandate=&collection=&sort=1 ETSI GS NFV-SOL 006].<br />
|-<br />
|webfinger<br />
|<code><nowiki>urn:etsi:nfv:webfinger</nowiki></code><br />
|This node is a namespace for webfinger services.<br />
Related specification [https://www.etsi.org/standards#page=1&search=NFV-SEC%20022&title=1&etsiNumber=1&content=0&version=1&onApproval=1&published=1&historical=1&startDate=1988-01-15&endDate=2021-05-03&harmonized=0&keyword=&TB=826,,835,,833,,789,,832,,831,,795,,796,,800,,798,,799,,848,,797,,828&stdType=&frequency=&mandate=&collection=&sort=1 ETSI GS NFV-SEC 022]<br />
|-<br />
|webfinger:rel<br />
|<code><nowiki>urn:etsi:nfv:webfinger:rel</nowiki></code><br />
|This node is a namespace for "rel" value of the webfinger services used for the dynamic discovery of servers.<br />
Related specification [https://www.etsi.org/standards#page=1&search=NFV-SEC%20022&title=1&etsiNumber=1&content=0&version=1&onApproval=1&published=1&historical=1&startDate=1988-01-15&endDate=2021-05-03&harmonized=0&keyword=&TB=826,,835,,833,,789,,832,,831,,795,,796,,800,,798,,799,,848,,797,,828&stdType=&frequency=&mandate=&collection=&sort=1 ETSI GS NFV-SEC 022]<br />
|-<br />
|webfinger:rel:api-oauth-server<br />
|<code><nowiki>urn:etsi:nfv:webfinger:rel:api-oauth-server</nowiki></code><br />
|Value of Webfinger service for the discovery of authorization server identifier for API access control using OAuth2.0.<br />
Related specification [https://www.etsi.org/standards#page=1&search=NFV-SEC%20022&title=1&etsiNumber=1&content=0&version=1&onApproval=1&published=1&historical=1&startDate=1988-01-15&endDate=2021-05-03&harmonized=0&keyword=&TB=826,,835,,833,,789,,832,,831,,795,,796,,800,,798,,799,,848,,797,,828&stdType=&frequency=&mandate=&collection=&sort=1 ETSI GS NFV-SEC 022]<br />
|}<br />
<br />
=== Requesting an entry (for ETSI technical groups only) ===<br />
A new NFV sub-tree can only be requested by an ETSI technical group (i.e., Technical Bodies, Industry Specification Groups, Open Source Groups and Special Communities), and their working groups (if applicable).<br />
<br />
To request a sub-tree please follow the guidelines below.<br />
<br />
* '''Pre-condition:''' a work item running in the ETSI technical group 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).<br />
* ''Step #1:'' Download the "URN namespace application template" in contribution [https://docbox.etsi.org/ISG/NFV/TSC/05-CONTRIBUTIONS/2019//NFVTSC(19)000003r3_Template_for_URN_namespace_applications.docx NFVTSC(19)000003]<br />
* ''Step #2:'' Fill in the template and submit it as a contribution under the "NFV TSC" workspace of the ETSI Portal.<br />
* ''Step #3:'' The ETSI NFV TSC will review the application.<br />
** If the application is accepted, a new entry in the "NFV URN Namespace" will be enabled.<br />
** 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".</div>Worndlehttps://nfvwiki.etsi.org/index.php?title=NFV_URN_Namespace&diff=3714NFV URN Namespace2021-05-17T13:16:45Z<p>Worndle: Removed "type" column and supplementary text as per decision in TSC#212</p>
<hr />
<div>=== Introduction ===<br />
ETSI ISG NFV is maintaining a namespace registry as a sub tree of the ETSI root <code><nowiki>urn:etsi</nowiki></code> 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].<br />
<br />
The NFV URN namespace has the following structure:<br />
<nowiki>urn:etsi:nfv</nowiki>:<NFV sub-tree><br />
The following sections describe the basic structure of the sub-tree and how a entry in the registry can be requested.<br />
<br />
=== NFV sub-tree ===<br />
{| class="wikitable"<br />
|+<br />
!NFV sub-tree<br />
!Full Namespace<br />
!Description<br />
|-<br />
|coord<br />
|<br />
<nowiki>urn:etsi:nfv:coord</nowiki><br />
|Namespace for public LCM coordination action names defined in ETSI NFV specifications, including [https://docbox.etsi.org/ISG/NFV/Open/Drafts/SOL002ed351_RESTful_protocols_spec ETSI GS NFV-SOL 002 v3.5.1] and later.<br />
|-<br />
|yang:etsi-nfv-descriptors<br />
|<br />
<nowiki>urn:etsi:nfv:yang:etsi-nfv-descriptors</nowiki><br />
|The namespace for YANG modules specified in ETSI GS NFV-SOL 006, available for download as [https://www.etsi.org/standards#page=1&search=NFV-SOL%20006&title=1&etsiNumber=1&content=0&version=1&onApproval=1&published=1&historical=1&startDate=1988-01-15&endDate=2021-05-03&harmonized=0&keyword=&TB=826,,835,,833,,789,,832,,831,,795,,796,,800,,798,,799,,848,,797,,828&stdType=&frequency=&mandate=&collection=&sort=1 ETSI GS NFV-SOL 006] and as a YANG specification in [https://forge.etsi.org/gitlab/nfv/SOL006/blob/master/src/yang/etsi-nfv-descriptors.yang etsi-nfv-descriptors.yang].<br />
|-<br />
|yang:etsi-nfv-vnfd<br />
|<br />
<nowiki>urn:etsi:nfv:yang:etsi-nfv-vnfd</nowiki><br />
|Namespace for the YANG module that is used to model a single VNFD, according to the YANG specification available in [https://forge.etsi.org/rep/nfv/SOL006/blob/v2.6.1/src/yang/etsi-nfv-vnfd.yang etsi-nfv-vnfd.yang] file and specified in [https://www.etsi.org/standards#page=1&search=NFV-SOL%20006&title=1&etsiNumber=1&content=0&version=1&onApproval=1&published=1&historical=1&startDate=1988-01-15&endDate=2021-05-03&harmonized=0&keyword=&TB=826,,835,,833,,789,,832,,831,,795,,796,,800,,798,,799,,848,,797,,828&stdType=&frequency=&mandate=&collection=&sort=1 ETSI GS NFV-SOL 006].<br />
|-<br />
|yang:etsi-nfv-nsd<br />
|<br />
<nowiki>urn:etsi:nfv:yang:etsi-nfv-nsd</nowiki><br />
|Namespace for the YANG module that is used to model a single NSD, according to the YANG specification available in [https://forge.etsi.org/rep/nfv/SOL006/blob/v2.6.1/src/yang/etsi-nfv-nsd.yang etsi-nfv-nsd.yang] file and specified in [https://www.etsi.org/standards#page=1&search=NFV-SOL%20006&title=1&etsiNumber=1&content=0&version=1&onApproval=1&published=1&historical=1&startDate=1988-01-15&endDate=2021-05-03&harmonized=0&keyword=&TB=826,,835,,833,,789,,832,,831,,795,,796,,800,,798,,799,,848,,797,,828&stdType=&frequency=&mandate=&collection=&sort=1 ETSI GS NFV-SOL 006].<br />
|-<br />
|yang:etsi-nfv-pnfd<br />
|<br />
<nowiki>urn:etsi:nfv:yang:etsi-nfv-pnfd</nowiki><br />
|Namespace for the YANG module that is used to model a single PNFD, according to the YANG specification available in [https://forge.etsi.org/rep/nfv/SOL006/blob/v2.6.1/src/yang/etsi-nfv-pnfd.yang etsi-nfv-pnfd.yang] file and specified in [https://www.etsi.org/standards#page=1&search=NFV-SOL%20006&title=1&etsiNumber=1&content=0&version=1&onApproval=1&published=1&historical=1&startDate=1988-01-15&endDate=2021-05-03&harmonized=0&keyword=&TB=826,,835,,833,,789,,832,,831,,795,,796,,800,,798,,799,,848,,797,,828&stdType=&frequency=&mandate=&collection=&sort=1 ETSI GS NFV-SOL 006].<br />
|-<br />
|webfinger<br />
|<code><nowiki>urn:etsi:nfv:webfinger</nowiki></code><br />
|This node is a namespace for webfinger services.<br />
Related specification [https://www.etsi.org/standards#page=1&search=NFV-SEC%20022&title=1&etsiNumber=1&content=0&version=1&onApproval=1&published=1&historical=1&startDate=1988-01-15&endDate=2021-05-03&harmonized=0&keyword=&TB=826,,835,,833,,789,,832,,831,,795,,796,,800,,798,,799,,848,,797,,828&stdType=&frequency=&mandate=&collection=&sort=1 ETSI GS NFV-SEC 022]<br />
|-<br />
|webfinger:rel<br />
|<code><nowiki>urn:etsi:nfv:webfinger:rel</nowiki></code><br />
|This node is a namespace for "rel" value of the webfinger services used for the dynamic discovery of servers.<br />
Related specification [https://www.etsi.org/standards#page=1&search=NFV-SEC%20022&title=1&etsiNumber=1&content=0&version=1&onApproval=1&published=1&historical=1&startDate=1988-01-15&endDate=2021-05-03&harmonized=0&keyword=&TB=826,,835,,833,,789,,832,,831,,795,,796,,800,,798,,799,,848,,797,,828&stdType=&frequency=&mandate=&collection=&sort=1 ETSI GS NFV-SEC 022]<br />
|-<br />
|webfinger:rel:api-oauth-server<br />
|<code><nowiki>urn:etsi:nfv:webfinger:rel:api-oauth-server</nowiki></code><br />
|Value of Webfinger service for the discovery of authorization server identifier for API access control using OAuth2.0.<br />
Related specification [https://www.etsi.org/standards#page=1&search=NFV-SEC%20022&title=1&etsiNumber=1&content=0&version=1&onApproval=1&published=1&historical=1&startDate=1988-01-15&endDate=2021-05-03&harmonized=0&keyword=&TB=826,,835,,833,,789,,832,,831,,795,,796,,800,,798,,799,,848,,797,,828&stdType=&frequency=&mandate=&collection=&sort=1 ETSI GS NFV-SEC 022]<br />
|}<br />
<br />
=== Requesting an entry (for ETSI technical groups only) ===<br />
A new NFV sub-tree can only be requested by an ETSI technical group (i.e., Technical Bodies, Industry Specification Groups, Open Source Groups and Special Communities), and their working groups (if applicable).<br />
<br />
To request a sub-tree please follow the guidelines below.<br />
<br />
* '''Pre-condition:''' a work item running in the ETSI technical group 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).<br />
* ''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]<br />
* ''Step #2:'' Fill in the template and submit it as a contribution under the "NFV TSC" workspace of the ETSI Portal.<br />
* ''Step #3:'' The ETSI NFV TSC will review the application.<br />
** If the application is accepted, a new entry in the "NFV URN Namespace" will be enabled.<br />
** 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".</div>Worndlehttps://nfvwiki.etsi.org/index.php?title=NFV_URN_Namespace&diff=3710NFV URN Namespace2021-05-03T08:57:04Z<p>Worndle: Updated links to latest versions of the specs</p>
<hr />
<div>=== Introduction ===<br />
ETSI ISG NFV is maintaining a namespace registry as a sub tree of the ETSI root <code><nowiki>urn:etsi</nowiki></code> 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].<br />
<br />
The NFV URN namespace has the following structure:<br />
<nowiki>urn:etsi:nfv</nowiki>:<NFV sub-tree><br />
The following sections describe the basic structure of the sub-tree and how a entry in the registry can be requested.<br />
<br />
=== NFV sub-tree ===<br />
{| class="wikitable"<br />
|+<br />
!NFV sub-tree<br />
!Full Namespace<br />
!Type<br />
!Description<br />
|-<br />
|coord<br />
|<br />
<nowiki>urn:etsi:nfv:coord</nowiki><br />
|string<br />
|Namespace for public LCM coordination action names defined in ETSI NFV specifications, including [https://docbox.etsi.org/ISG/NFV/Open/Drafts/SOL002ed351_RESTful_protocols_spec ETSI GS NFV-SOL 002 v3.5.1] and later.<br />
|-<br />
|yang:etsi-nfv-descriptors<br />
|<br />
<nowiki>urn:etsi:nfv:yang:etsi-nfv-descriptors</nowiki><br />
|string<br />
|The namespace for YANG modules specified in ETSI GS NFV-SOL 006, available for download as [https://www.etsi.org/standards#page=1&search=NFV-SOL%20006&title=1&etsiNumber=1&content=0&version=1&onApproval=1&published=1&historical=1&startDate=1988-01-15&endDate=2021-05-03&harmonized=0&keyword=&TB=826,,835,,833,,789,,832,,831,,795,,796,,800,,798,,799,,848,,797,,828&stdType=&frequency=&mandate=&collection=&sort=1 ETSI GS NFV-SOL 006] and as a YANG specification in [https://forge.etsi.org/gitlab/nfv/SOL006/blob/master/src/yang/etsi-nfv-descriptors.yang etsi-nfv-descriptors.yang].<br />
|-<br />
|yang:etsi-nfv-vnfd<br />
|<br />
<nowiki>urn:etsi:nfv:yang:etsi-nfv-vnfd</nowiki><br />
|string<br />
|Namespace for the YANG module that is used to model a single VNFD, according to the YANG specification available in [https://forge.etsi.org/rep/nfv/SOL006/blob/v2.6.1/src/yang/etsi-nfv-vnfd.yang etsi-nfv-vnfd.yang] file and specified in [https://www.etsi.org/standards#page=1&search=NFV-SOL%20006&title=1&etsiNumber=1&content=0&version=1&onApproval=1&published=1&historical=1&startDate=1988-01-15&endDate=2021-05-03&harmonized=0&keyword=&TB=826,,835,,833,,789,,832,,831,,795,,796,,800,,798,,799,,848,,797,,828&stdType=&frequency=&mandate=&collection=&sort=1 ETSI GS NFV-SOL 006].<br />
|-<br />
|yang:etsi-nfv-nsd<br />
|<br />
<nowiki>urn:etsi:nfv:yang:etsi-nfv-nsd</nowiki><br />
|string<br />
|Namespace for the YANG module that is used to model a single NSD, according to the YANG specification available in [https://forge.etsi.org/rep/nfv/SOL006/blob/v2.6.1/src/yang/etsi-nfv-nsd.yang etsi-nfv-nsd.yang] file and specified in [https://www.etsi.org/standards#page=1&search=NFV-SOL%20006&title=1&etsiNumber=1&content=0&version=1&onApproval=1&published=1&historical=1&startDate=1988-01-15&endDate=2021-05-03&harmonized=0&keyword=&TB=826,,835,,833,,789,,832,,831,,795,,796,,800,,798,,799,,848,,797,,828&stdType=&frequency=&mandate=&collection=&sort=1 ETSI GS NFV-SOL 006].<br />
|-<br />
|yang:etsi-nfv-pnfd<br />
|<br />
<nowiki>urn:etsi:nfv:yang:etsi-nfv-pnfd</nowiki><br />
|string<br />
|Namespace for the YANG module that is used to model a single PNFD, according to the YANG specification available in [https://forge.etsi.org/rep/nfv/SOL006/blob/v2.6.1/src/yang/etsi-nfv-pnfd.yang etsi-nfv-pnfd.yang] file and specified in [https://www.etsi.org/standards#page=1&search=NFV-SOL%20006&title=1&etsiNumber=1&content=0&version=1&onApproval=1&published=1&historical=1&startDate=1988-01-15&endDate=2021-05-03&harmonized=0&keyword=&TB=826,,835,,833,,789,,832,,831,,795,,796,,800,,798,,799,,848,,797,,828&stdType=&frequency=&mandate=&collection=&sort=1 ETSI GS NFV-SOL 006].<br />
|-<br />
|webfinger<br />
|<code><nowiki>urn:etsi:nfv:webfinger</nowiki></code><br />
|string<br />
|This node is a namespace for webfinger services.<br />
Related specification [https://www.etsi.org/standards#page=1&search=NFV-SEC%20022&title=1&etsiNumber=1&content=0&version=1&onApproval=1&published=1&historical=1&startDate=1988-01-15&endDate=2021-05-03&harmonized=0&keyword=&TB=826,,835,,833,,789,,832,,831,,795,,796,,800,,798,,799,,848,,797,,828&stdType=&frequency=&mandate=&collection=&sort=1 ETSI GS NFV-SEC 022]<br />
|-<br />
|webfinger:rel<br />
|<code><nowiki>urn:etsi:nfv:webfinger:rel</nowiki></code><br />
|string<br />
|This node is a namespace for "rel" value of the webfinger services used for the dynamic discovery of servers.<br />
Related specification [https://www.etsi.org/standards#page=1&search=NFV-SEC%20022&title=1&etsiNumber=1&content=0&version=1&onApproval=1&published=1&historical=1&startDate=1988-01-15&endDate=2021-05-03&harmonized=0&keyword=&TB=826,,835,,833,,789,,832,,831,,795,,796,,800,,798,,799,,848,,797,,828&stdType=&frequency=&mandate=&collection=&sort=1 ETSI GS NFV-SEC 022]<br />
|-<br />
|webfinger:rel:api-oauth-server<br />
|<code><nowiki>urn:etsi:nfv:webfinger:rel:api-oauth-server</nowiki></code><br />
|string<br />
|Value of Webfinger service for the discovery of authorization server identifier for API access control using OAuth2.0.<br />
Related specification [https://www.etsi.org/standards#page=1&search=NFV-SEC%20022&title=1&etsiNumber=1&content=0&version=1&onApproval=1&published=1&historical=1&startDate=1988-01-15&endDate=2021-05-03&harmonized=0&keyword=&TB=826,,835,,833,,789,,832,,831,,795,,796,,800,,798,,799,,848,,797,,828&stdType=&frequency=&mandate=&collection=&sort=1 ETSI GS NFV-SEC 022]<br />
|}<br />
<br />
==== Type definitions ====<br />
string = (ALPHA)0*(ALPHANUMERIC/-/_)<br />
# 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<br />
<br />
ALPHA = {a-zA-Z}<br />
ALPHANUMERIC = {a-zA-Z0-9}<br />
<br />
=== Requesting an entry (for ETSI technical groups only) ===<br />
A new NFV sub-tree can only be requested by an ETSI technical group (i.e., Technical Bodies, Industry Specification Groups, Open Source Groups and Special Communities), and their working groups (if applicable).<br />
<br />
To request a sub-tree please follow the guidelines below.<br />
<br />
* '''Pre-condition:''' a work item running in the ETSI technical group 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).<br />
* ''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]<br />
* ''Step #2:'' Fill in the template and submit it as a contribution under the "NFV TSC" workspace of the ETSI Portal.<br />
* ''Step #3:'' The ETSI NFV TSC will review the application.<br />
** If the application is accepted, a new entry in the "NFV URN Namespace" will be enabled.<br />
** 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".</div>Worndlehttps://nfvwiki.etsi.org/index.php?title=NFV_URN_Namespace&diff=3709NFV URN Namespace2021-04-22T13:01:41Z<p>Worndle: Added new entry for coord according to approved contribution NFVTSC(21)000029.</p>
<hr />
<div>=== Introduction ===<br />
ETSI ISG NFV is maintaining a namespace registry as a sub tree of the ETSI root <code><nowiki>urn:etsi</nowiki></code> 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].<br />
<br />
The NFV URN namespace has the following structure:<br />
<nowiki>urn:etsi:nfv</nowiki>:<NFV sub-tree><br />
The following sections describe the basic structure of the sub-tree and how a entry in the registry can be requested.<br />
<br />
=== NFV sub-tree ===<br />
{| class="wikitable"<br />
|+<br />
!NFV sub-tree<br />
!Full Namespace<br />
!Type<br />
!Description<br />
|-<br />
|coord<br />
|<br />
<nowiki>urn:etsi:nfv:coord</nowiki><br />
|string<br />
|Namespace for public LCM coordination action names defined in ETSI NFV specifications, including ETSI GS NFV-SOL 002 v3.5.1 and later.<br />
|-<br />
|yang:etsi-nfv-descriptors<br />
|<br />
<nowiki>urn:etsi:nfv:yang:etsi-nfv-descriptors</nowiki><br />
|string<br />
|The namespace for YANG modules specified in ETSI GS NFV-SOL 006, available for download as [https://www.etsi.org/deliver/etsi_gs/NFV-SOL/001_099/006/02.06.01_60/gs_nfv-sol006v020601p.pdf ETSI GS NFV-SOL 006 v2.6.1] and as a YANG specification in [https://forge.etsi.org/gitlab/nfv/SOL006/blob/master/src/yang/etsi-nfv-descriptors.yang etsi-nfv-descriptors.yang].<br />
|-<br />
|yang:etsi-nfv-vnfd<br />
|<br />
<nowiki>urn:etsi:nfv:yang:etsi-nfv-vnfd</nowiki><br />
|string<br />
|Namespace for the YANG module that is used to model a single VNFD, according to the YANG specification available in [https://forge.etsi.org/rep/nfv/SOL006/blob/v2.6.1/src/yang/etsi-nfv-vnfd.yang etsi-nfv-vnfd.yang] file and specified in [https://www.etsi.org/deliver/etsi_gs/NFV-SOL/001_099/006/02.06.01_60/gs_nfv-sol006v020601p.pdf ETSI GS NFV-SOL 006 v2.6.1].<br />
|-<br />
|yang:etsi-nfv-nsd<br />
|<br />
<nowiki>urn:etsi:nfv:yang:etsi-nfv-nsd</nowiki><br />
|string<br />
|Namespace for the YANG module that is used to model a single NSD, according to the YANG specification available in [https://forge.etsi.org/rep/nfv/SOL006/blob/v2.6.1/src/yang/etsi-nfv-nsd.yang etsi-nfv-nsd.yang] file and specified in [https://www.etsi.org/deliver/etsi_gs/NFV-SOL/001_099/006/02.06.01_60/gs_nfv-sol006v020601p.pdf ETSI GS NFV-SOL 006 v2.6.1].<br />
|-<br />
|yang:etsi-nfv-pnfd<br />
|<br />
<nowiki>urn:etsi:nfv:yang:etsi-nfv-pnfd</nowiki><br />
|string<br />
|Namespace for the YANG module that is used to model a single PNFD, according to the YANG specification available in [https://forge.etsi.org/rep/nfv/SOL006/blob/v2.6.1/src/yang/etsi-nfv-pnfd.yang etsi-nfv-pnfd.yang] file and specified in [https://www.etsi.org/deliver/etsi_gs/NFV-SOL/001_099/006/02.06.01_60/gs_nfv-sol006v020601p.pdf ETSI GS NFV-SOL 006 v2.6.1].<br />
|-<br />
|webfinger<br />
|<code><nowiki>urn:etsi:nfv:webfinger</nowiki></code><br />
|string<br />
|This node is a namespace for webfinger services.<br />
Related specification [https://docbox.etsi.org/ISG/NFV/Open/Drafts/SEC022_API_Access_Token_Spec/NFV-SEC022v010.zip ETSI GS NFV-SEC 022 (latest draft)]<br />
|-<br />
|webfinger:rel<br />
|<code><nowiki>urn:etsi:nfv:webfinger:rel</nowiki></code><br />
|string<br />
|This node is a namespace for "rel" value of the webfinger services used for the dynamic discovery of servers.<br />
Related specification [https://docbox.etsi.org/ISG/NFV/Open/Drafts/SEC022_API_Access_Token_Spec/NFV-SEC022v010.zip ETSI GS NFV-SEC 022 (latest draft)]<br />
|-<br />
|webfinger:rel:api-oauth-server<br />
|<code><nowiki>urn:etsi:nfv:webfinger:rel:api-oauth-server</nowiki></code><br />
|string<br />
|Value of Webfinger service for the discovery of authorization server identifier for API access control using OAuth2.0.<br />
Related specification [https://docbox.etsi.org/ISG/NFV/Open/Drafts/SEC022_API_Access_Token_Spec/NFV-SEC022v010.zip ETSI GS NFV-SEC 022 (latest draft)]<br />
|}<br />
<br />
==== Type definitions ====<br />
string = (ALPHA)0*(ALPHANUMERIC/-/_)<br />
# 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<br />
<br />
ALPHA = {a-zA-Z}<br />
ALPHANUMERIC = {a-zA-Z0-9}<br />
<br />
=== Requesting an entry (for ETSI technical groups only) ===<br />
A new NFV sub-tree can only be requested by an ETSI technical group (i.e., Technical Bodies, Industry Specification Groups, Open Source Groups and Special Communities), and their working groups (if applicable).<br />
<br />
To request a sub-tree please follow the guidelines below.<br />
<br />
* '''Pre-condition:''' a work item running in the ETSI technical group 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).<br />
* ''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]<br />
* ''Step #2:'' Fill in the template and submit it as a contribution under the "NFV TSC" workspace of the ETSI Portal.<br />
* ''Step #3:'' The ETSI NFV TSC will review the application.<br />
** If the application is accepted, a new entry in the "NFV URN Namespace" will be enabled.<br />
** 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".</div>Worndlehttps://nfvwiki.etsi.org/index.php?title=NFV_URN_Namespace&diff=3536NFV URN Namespace2019-06-06T15:10:23Z<p>Worndle: Added new URN entries from NFV000039r1</p>
<hr />
<div>=== Introduction ===<br />
ETSI ISG NFV is maintaining a namespace registry as a sub tree of the ETSI root <code><nowiki>urn:etsi</nowiki></code> 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].<br />
<br />
The NFV URN namespace has the following structure:<br />
<nowiki>urn:etsi:nfv</nowiki>:<NFV sub-tree><br />
The following sections describe the basic structure of the sub-tree and how a entry in the registry can be requested.<br />
<br />
=== NFV sub-tree ===<br />
{| class="wikitable"<br />
|+<br />
!NFV sub-tree<br />
!Full Namespace<br />
!Type<br />
!Description<br />
|-<br />
|yang:etsi-nfv-descriptors<br />
|<br />
<nowiki>urn:etsi:nfv:yang:etsi-nfv-descriptors</nowiki><br />
|string<br />
|The namespace for YANG modules specified in ETSI GS NFV-SOL 006, available for download as [https://www.etsi.org/deliver/etsi_gs/NFV-SOL/001_099/006/02.06.01_60/gs_nfv-sol006v020601p.pdf ETSI GS NFV-SOL 006 v2.6.1] and as a YANG specification in [https://forge.etsi.org/gitlab/nfv/SOL006/blob/master/src/yang/etsi-nfv-descriptors.yang etsi-nfv-descriptors.yang].<br />
|-<br />
|yang:etsi-nfv-vnfd<br />
|<br />
<nowiki>urn:etsi:nfv:yang:etsi-nfv-vnfd</nowiki><br />
|string<br />
|Namespace for the YANG module that is used to model a single VNFD, according to the YANG specification available in [https://forge.etsi.org/rep/nfv/SOL006/blob/v2.6.1/src/yang/etsi-nfv-vnfd.yang etsi-nfv-vnfd.yang] file and specified in [https://www.etsi.org/deliver/etsi_gs/NFV-SOL/001_099/006/02.06.01_60/gs_nfv-sol006v020601p.pdf ETSI GS NFV-SOL 006 v2.6.1].<br />
|-<br />
|yang:etsi-nfv-nsd<br />
|<br />
<nowiki>urn:etsi:nfv:yang:etsi-nfv-nsd</nowiki><br />
|string<br />
|Namespace for the YANG module that is used to model a single NSD, according to the YANG specification available in [https://forge.etsi.org/rep/nfv/SOL006/blob/v2.6.1/src/yang/etsi-nfv-nsd.yang etsi-nfv-nsd.yang] file and specified in [https://www.etsi.org/deliver/etsi_gs/NFV-SOL/001_099/006/02.06.01_60/gs_nfv-sol006v020601p.pdf ETSI GS NFV-SOL 006 v2.6.1].<br />
|-<br />
|yang:etsi-nfv-pnfd<br />
|<br />
<nowiki>urn:etsi:nfv:yang:etsi-nfv-pnfd</nowiki><br />
|string<br />
|Namespace for the YANG module that is used to model a single PNFD, according to the YANG specification available in [https://forge.etsi.org/rep/nfv/SOL006/blob/v2.6.1/src/yang/etsi-nfv-pnfd.yang etsi-nfv-pnfd.yang] file and specified in [https://www.etsi.org/deliver/etsi_gs/NFV-SOL/001_099/006/02.06.01_60/gs_nfv-sol006v020601p.pdf ETSI GS NFV-SOL 006 v2.6.1].<br />
|-<br />
|webfinger<br />
|<code><nowiki>urn:etsi:nfv:webfinger</nowiki></code><br />
|string<br />
|This node is a namespace for webfinger services.<br />
Related specification [https://docbox.etsi.org/ISG/NFV/Open/Drafts/SEC022_API_Access_Token_Spec/NFV-SEC022v010.zip ETSI GS NFV-SEC 022 (latest draft)]<br />
|-<br />
|webfinger:rel<br />
|<code><nowiki>urn:etsi:nfv:webfinger:rel</nowiki></code><br />
|string<br />
|This node is a namespace for "rel" value of the webfinger services used for the dynamic discovery of servers.<br />
Related specification [https://docbox.etsi.org/ISG/NFV/Open/Drafts/SEC022_API_Access_Token_Spec/NFV-SEC022v010.zip ETSI GS NFV-SEC 022 (latest draft)]<br />
|-<br />
|webfinger:rel:api-oauth-server<br />
|<code><nowiki>urn:etsi:nfv:webfinger:rel:api-oauth-server</nowiki></code><br />
|string<br />
|Value of Webfinger service for the discovery of authorization server identifier for API access control using OAuth2.0.<br />
Related specification [https://docbox.etsi.org/ISG/NFV/Open/Drafts/SEC022_API_Access_Token_Spec/NFV-SEC022v010.zip ETSI GS NFV-SEC 022 (latest draft)]<br />
|}<br />
<br />
==== Type definitions ====<br />
string = (ALPHA)0*(ALPHANUMERIC/-/_)<br />
# 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<br />
<br />
ALPHA = {a-zA-Z}<br />
ALPHANUMERIC = {a-zA-Z0-9}<br />
<br />
=== Requesting an entry (for ETSI technical groups only) ===<br />
A new NFV sub-tree can only be requested by an ETSI technical group (i.e., Technical Bodies, Industry Specification Groups, Open Source Groups and Special Communities), and their working groups (if applicable).<br />
<br />
To request a sub-tree please follow the guidelines below.<br />
<br />
* '''Pre-condition:''' a work item running in the ETSI technical group 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).<br />
* ''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]<br />
* ''Step #2:'' Fill in the template and submit it as a contribution under the "NFV TSC" workspace of the ETSI Portal.<br />
* ''Step #3:'' The ETSI NFV TSC will review the application.<br />
** If the application is accepted, a new entry in the "NFV URN Namespace" will be enabled.<br />
** 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".</div>Worndlehttps://nfvwiki.etsi.org/index.php?title=NFV_URN_Namespace&diff=3528NFV URN Namespace2019-05-03T11:47:01Z<p>Worndle: Updated terminology to match ETSI directives for all technical groups within ETSI</p>
<hr />
<div>=== Introduction ===<br />
ETSI ISG NFV is maintaining a namespace registry as a sub tree of the ETSI root <code><nowiki>urn:etsi</nowiki></code> 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].<br />
<br />
The NFV URN namespace has the following structure:<br />
<nowiki>urn:etsi:nfv</nowiki>:<NFV sub-tree><br />
The following sections describe the basic structure of the sub-tree and how a entry in the registry can be requested.<br />
<br />
=== NFV sub-tree ===<br />
{| class="wikitable"<br />
|+<br />
!NFV sub-tree<br />
!Full Namespace<br />
!Type<br />
!Description<br />
|-<br />
|yang:etsi-nfv-descriptors<br />
|<br />
<nowiki>urn:etsi:nfv:yang:etsi-nfv-descriptors</nowiki><br />
|string<br />
|Namespace for YANG modules specified in ETSI GS NFV-SOL 006.<br />
[https://docbox.etsi.org/ISG/NFV/Open/Drafts/SOL006_YANG_based_NFV_Descriptors_spec Latest draft of SOL006]<br />
|-<br />
|yang:etsi-nfv-vnfd<br />
|<br />
<nowiki>urn:etsi:nfv:yang:etsi-nfv-vnfd</nowiki><br />
|string<br />
|Namespace for the YANG module that is used to model a single VNFD, according to the YANG specification available in [https://forge.etsi.org/rep/nfv/SOL006/blob/v2.6.1/src/yang/etsi-nfv-vnfd.yang etsi-nfv-vnfd.yang] file.<br />
|-<br />
|yang:etsi-nfv-nsd<br />
|<br />
<nowiki>urn:etsi:nfv:yang:etsi-nfv-nsd</nowiki><br />
|string<br />
|Namespace for the YANG module that is used to model a single NSD, according to the YANG specification available in [https://forge.etsi.org/rep/nfv/SOL006/blob/v2.6.1/src/yang/etsi-nfv-nsd.yang etsi-nfv-nsd.yang] file<br />
|-<br />
|yang:etsi-nfv-pnfd<br />
|<br />
<nowiki>urn:etsi:nfv:yang:etsi-nfv-pnfd</nowiki><br />
|string<br />
|Namespace for the YANG module that is used to model a single PNFD, according to the YANG specification available in [https://forge.etsi.org/rep/nfv/SOL006/blob/v2.6.1/src/yang/etsi-nfv-pnfd.yang etsi-nfv-pnfd.yang] file<br />
|}<br />
<br />
==== Type definitions ====<br />
string = (ALPHA)0*(ALPHANUMERIC/-/_)<br />
# 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<br />
<br />
ALPHA = {a-zA-Z}<br />
ALPHANUMERIC = {a-zA-Z0-9}<br />
<br />
=== Requesting an entry (for ETSI technical groups only) ===<br />
A new NFV sub-tree can only be requested by an ETSI technical group (i.e., Technical Bodies, Industry Specification Groups, Open Source Groups and Special Communities) their working groups (if applicable).<br />
<br />
To request a sub-tree please follow the guide below.<br />
<br />
* '''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).<br />
* ''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]<br />
* ''Step #2:'' Fill in the template and submit it as a contribution under the "NFV TSC" workspace of the ETSI Portal.<br />
* ''Step #3:'' The TSC will review the application.<br />
** If the application is accepted, a new entry in the "NFV URN Namespace" will be enabled.<br />
** 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".</div>Worndlehttps://nfvwiki.etsi.org/index.php?title=NFV_URN_Namespace&diff=3527NFV URN Namespace2019-05-03T11:39:20Z<p>Worndle: Added new namespace sub-trees requested via NFVSOL(19)000237r3</p>
<hr />
<div>=== Introduction ===<br />
ETSI ISG NFV is maintaining a namespace registry as a sub tree of the ETSI root <code><nowiki>urn:etsi</nowiki></code> 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].<br />
<br />
The NFV URN namespace has the following structure:<br />
<nowiki>urn:etsi:nfv</nowiki>:<NFV sub-tree><br />
The following sections describe the basic structure of the sub-tree and how a entry in the registry can be requested.<br />
<br />
=== NFV sub-tree ===<br />
{| class="wikitable"<br />
|+<br />
!NFV sub-tree<br />
!Full Namespace<br />
!Type<br />
!Description<br />
|-<br />
|yang:etsi-nfv-descriptors<br />
|<br />
<nowiki>urn:etsi:nfv:yang:etsi-nfv-descriptors</nowiki><br />
|string<br />
|Namespace for YANG modules specified in ETSI GS NFV-SOL 006.<br />
[https://docbox.etsi.org/ISG/NFV/Open/Drafts/SOL006_YANG_based_NFV_Descriptors_spec Latest draft of SOL006]<br />
|-<br />
|yang:etsi-nfv-vnfd<br />
|<br />
<nowiki>urn:etsi:nfv:yang:etsi-nfv-vnfd</nowiki><br />
|string<br />
|Namespace for the YANG module that is used to model a single VNFD, according to the YANG specification available in [https://forge.etsi.org/rep/nfv/SOL006/blob/v2.6.1/src/yang/etsi-nfv-vnfd.yang etsi-nfv-vnfd.yang] file.<br />
|-<br />
|yang:etsi-nfv-nsd<br />
|<br />
<nowiki>urn:etsi:nfv:yang:etsi-nfv-nsd</nowiki><br />
|string<br />
|Namespace for the YANG module that is used to model a single NSD, according to the YANG specification available in [https://forge.etsi.org/rep/nfv/SOL006/blob/v2.6.1/src/yang/etsi-nfv-nsd.yang etsi-nfv-nsd.yang] file<br />
|-<br />
|yang:etsi-nfv-pnfd<br />
|<br />
<nowiki>urn:etsi:nfv:yang:etsi-nfv-pnfd</nowiki><br />
|string<br />
|Namespace for the YANG module that is used to model a single PNFD, according to the YANG specification available in [https://forge.etsi.org/rep/nfv/SOL006/blob/v2.6.1/src/yang/etsi-nfv-pnfd.yang etsi-nfv-pnfd.yang] file<br />
|}<br />
<br />
==== Type definitions ====<br />
string = (ALPHA)0*(ALPHANUMERIC/-/_)<br />
# 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<br />
<br />
ALPHA = {a-zA-Z}<br />
ALPHANUMERIC = {a-zA-Z0-9}<br />
<br />
=== Requesting an entry (for ETSI technical bodies only) ===<br />
A new NFV sub-tree can only be requested by a ETSI technical body.<br />
<br />
To request a sub-tree please follow the guide below.<br />
<br />
* '''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).<br />
* ''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]<br />
* ''Step #2:'' Fill in the template and submit it as a contribution under the "NFV TSC" workspace of the ETSI Portal.<br />
* ''Step #3:'' The TSC will review the application.<br />
** If the application is accepted, a new entry in the "NFV URN Namespace" will be enabled.<br />
** 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".</div>Worndle