NFV URN Namespace: Difference between revisions
(Added new entry for coord according to approved contribution NFVTSC(21)000029.) |
(Updated links to latest versions of the specs) |
||
Line 18: | Line 18: | ||
<nowiki>urn:etsi:nfv:coord</nowiki> | <nowiki>urn:etsi:nfv:coord</nowiki> | ||
|string | |string | ||
|Namespace for public LCM coordination action names defined in ETSI NFV specifications, including ETSI GS NFV-SOL 002 v3.5.1 and later. | |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. | ||
|- | |- | ||
|yang:etsi-nfv-descriptors | |yang:etsi-nfv-descriptors | ||
Line 24: | Line 24: | ||
<nowiki>urn:etsi:nfv:yang:etsi-nfv-descriptors</nowiki> | <nowiki>urn:etsi:nfv:yang:etsi-nfv-descriptors</nowiki> | ||
|string | |string | ||
|The namespace for YANG modules specified in ETSI GS NFV-SOL 006, available for download as [https://www.etsi.org/ | |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]. | ||
|- | |- | ||
|yang:etsi-nfv-vnfd | |yang:etsi-nfv-vnfd | ||
Line 30: | Line 30: | ||
<nowiki>urn:etsi:nfv:yang:etsi-nfv-vnfd</nowiki> | <nowiki>urn:etsi:nfv:yang:etsi-nfv-vnfd</nowiki> | ||
|string | |string | ||
|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/ | |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]. | ||
|- | |- | ||
|yang:etsi-nfv-nsd | |yang:etsi-nfv-nsd | ||
Line 36: | Line 36: | ||
<nowiki>urn:etsi:nfv:yang:etsi-nfv-nsd</nowiki> | <nowiki>urn:etsi:nfv:yang:etsi-nfv-nsd</nowiki> | ||
|string | |string | ||
|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/ | |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]. | ||
|- | |- | ||
|yang:etsi-nfv-pnfd | |yang:etsi-nfv-pnfd | ||
Line 42: | Line 42: | ||
<nowiki>urn:etsi:nfv:yang:etsi-nfv-pnfd</nowiki> | <nowiki>urn:etsi:nfv:yang:etsi-nfv-pnfd</nowiki> | ||
|string | |string | ||
|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/ | |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]. | ||
|- | |- | ||
|webfinger | |webfinger | ||
Line 48: | Line 48: | ||
|string | |string | ||
|This node is a namespace for webfinger services. | |This node is a namespace for webfinger services. | ||
Related specification [https:// | 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] | ||
|- | |- | ||
|webfinger:rel | |webfinger:rel | ||
Line 54: | Line 54: | ||
|string | |string | ||
|This node is a namespace for "rel" value of the webfinger services used for the dynamic discovery of servers. | |This node is a namespace for "rel" value of the webfinger services used for the dynamic discovery of servers. | ||
Related specification [https:// | 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] | ||
|- | |- | ||
|webfinger:rel:api-oauth-server | |webfinger:rel:api-oauth-server | ||
Line 60: | Line 60: | ||
|string | |string | ||
|Value of Webfinger service for the discovery of authorization server identifier for API access control using OAuth2.0. | |Value of Webfinger service for the discovery of authorization server identifier for API access control using OAuth2.0. | ||
Related specification [https:// | 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] | ||
|} | |} | ||
Revision as of 08:57, 3 May 2021
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 |
---|---|---|---|
coord |
urn:etsi:nfv:coord |
string | Namespace for public LCM coordination action names defined in ETSI NFV specifications, including ETSI GS NFV-SOL 002 v3.5.1 and later. |
yang:etsi-nfv-descriptors |
urn:etsi:nfv:yang:etsi-nfv-descriptors |
string | The namespace for YANG modules specified in ETSI GS NFV-SOL 006, available for download as ETSI GS NFV-SOL 006 and as a YANG specification in etsi-nfv-descriptors.yang. |
yang:etsi-nfv-vnfd |
urn:etsi:nfv:yang:etsi-nfv-vnfd |
string | Namespace for the YANG module that is used to model a single VNFD, according to the YANG specification available in etsi-nfv-vnfd.yang file and specified in ETSI GS NFV-SOL 006. |
yang:etsi-nfv-nsd |
urn:etsi:nfv:yang:etsi-nfv-nsd |
string | Namespace for the YANG module that is used to model a single NSD, according to the YANG specification available in etsi-nfv-nsd.yang file and specified in ETSI GS NFV-SOL 006. |
yang:etsi-nfv-pnfd |
urn:etsi:nfv:yang:etsi-nfv-pnfd |
string | Namespace for the YANG module that is used to model a single PNFD, according to the YANG specification available in etsi-nfv-pnfd.yang file and specified in ETSI GS NFV-SOL 006. |
webfinger | urn:etsi:nfv:webfinger
|
string | This node is a namespace for webfinger services.
Related specification ETSI GS NFV-SEC 022 |
webfinger:rel | urn:etsi:nfv:webfinger:rel
|
string | This node is a namespace for "rel" value of the webfinger services used for the dynamic discovery of servers.
Related specification ETSI GS NFV-SEC 022 |
webfinger:rel:api-oauth-server | urn:etsi:nfv:webfinger:rel:api-oauth-server
|
string | Value of Webfinger service for the discovery of authorization server identifier for API access control using OAuth2.0.
Related specification ETSI GS NFV-SEC 022 |
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 groups only)
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).
To request a sub-tree please follow the guidelines below.
- 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).
- 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 ETSI NFV 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".