NFV Issue Tracker

The ETSI Issue Tracker allows to report feedback on an ETSI NFV public DRAFTs.

ETSI NFV public DRAFTs are available in the NFV Open Area. (this area only contains the ISG NFV drafts which have been made public, i.e. most of them).

Login to the Issue Tracker

Login with EOL: NFV members and participants can login to the ETSI NFV Issue Tracker with their ETSI OnLine (EOL) account (used to log into the ETSI Portal).

Create local account: The ETSI NFV Issue Tracker is also open to the general public: creating a local account only requires a username and a valid e-mail address, which is verified in the process.

New accounts have a "Reporter" role by default, which allows to submit new issues and view public issues.

Submit a new Issue

Connect to the ETSI Issue Tracker and login. On the main screen choose project "NFV Specifications" and the sub-project for the corresponding GS document

Before submitting a new issue, please check that

1. the issue still exists in the latest version of the respective GS document, and
2. the issue has not yet been reported by someone else. If the latter is the case, please add a comment to the existing issue rather than reporting a new one.

To submit a new issue:

1. On the main screen choose project "NFV Specifications" and the sub-project for the corresponding GS document and then click "Report Issue".
   
   
   
2. In the form, choose the most appropriate category for the new issue (see table below):
   
   
   
3. Select the latest version of the GS document that contains the issue.
4. Provide a descriptive one-line summary of the issue.
5. Provide a detailed description of the issue: What specific issue did you encounter and where? What would you have expected to find instead?
6. Optionally, provide additional information. This is the field to put references to external documents, if any.
7. Optionally, set the "View Status":
   • If this is an ETSI NFV internal issue (e.g. gap tracking by the rapporteur) and this issue is still confidential because it refers to a non-public document, set to "private".
   • Else, keep as "public".
     Note: We should keep our own issues public whenever possible, as this helps reducing duplicate reports.
8. Click "Submit Report".

Issue categories:

Category	Semantic
Bug	Some aspect of the spec cannot be implemented as described.
Clarification	Some aspect of the spec is ambiguous or unclear.
Feature Gap	The specs are missing a feature (e.g. an operation, parameter) without which the described features cannot be implemented.