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).
| Draft Reference | view scope & schedule | Direct link to Issue Tracker |
|---|---|---|
| NFV-EVE001 "Hypervisor Rqmts spec" | EVE001 issue tracker | |
| NFV-EVE002 "MEF Use Cases report" | EVE002 issue tracker | |
| NFV-EVE003 "NFVI Node Arch report" | EVE003 issue tracker | |
| NFV-EVE004 "Virtualisation technologies Report" | EVE004 issue tracker | |
| NFV-EVE005 "SDN usage in NFV Report" | EVE005 issue tracker | |
| NFV-IFA001 "Acceleration 1 - UCs report" | IFA001 issue tracker | |
| NFV-IFA002 "Acceleration 2 - VNF Intface Spec" | IFA002 issue tracker | |
| NFV-IFA003 "Acceleration 3 - vSwitch Spec" | IFA003 issue tracker | |
| NFV-IFA004 "Acceleration 4 - Mgmt aspects Spec" | IFA004 issue tracker | |
| NFV-IFA005 "Or-Vi ref point Spec" | IFA005 issue tracker | |
| NFV-IFA006 "Vi-Vnfm ref point Spec" | IFA006 issue tracker | |
| NFV-IFA007 "Or-Vnfm ref point Spec" | IFA007 issue tracker | |
| NFV-IFA008 "Ve-Vnfm ref point Spec" | IFA008 issue tracker | |
| NFV-IFA009 "MANO architectural options report" | IFA009 issue tracker | |
| NFV-IFA010 "MANO Functional Rqmts Spec" | IFA010 issue tracker | |
| NFV-IFA011 "VNF Packaging Spec" | IFA011 issue tracker | |
| NFV-IFA012 "Os-Ma-Nfvo ref point Spec - svc mgmt & info model" | IFA012 issue tracker | |
| NFV-IFA013 "Os-Ma-Nfvo ref point Spec - info model" | IFA013 issue tracker | |
| NFV-IFA014 "Network Service Templates Specification" | IFA014 issue tracker | |
| NFV-REL002 "Scalable Arch for Reliability Report" | REL002 issue tracker | |
| NFV-REL003 "E2E reliability models report" | REL003 issue tracker | |
| NFV-REL004 "Active monitoring & failure detection report" | REL004 issue tracker | |
| NFV-SEC002 "Security features in mgmt sofware report" | SEC002 issue tracker | |
| NFV-SEC004 "LI report" | SEC004 issue tracker | |
| NFV-SEC005 "Certificate mgmt report" | SEC005 issue tracker | |
| NFV-SEC006 "Sec & Regulation report" | SEC006 issue tracker | |
| NFV-SEC007 "NFV Attestation report" | SEC007 issue tracker | |
| NFV-SEC008 "Security Monitoring report" | SEC008 issue tracker | |
| NFV-SEC009 "UCs for multi-layer host admin" | SEC009 issue tracker | |
| NFV-TST001 "Pre-deployment Validation report" | TST001 issue tracker | |
| NFV-TST002 "Iop Testing Methodology report" | TST002 issue tracker |
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
- the issue still exists in the latest version of the respective GS document, and
- 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:
- On the main screen choose project "NFV Specifications" and the sub-project for the corresponding GS document and then click "Report Issue".
- In the form, choose the most appropriate category for the new issue (see table below):
- Select the latest version of the GS document that contains the issue.
- Provide a descriptive one-line summary of the issue.
- Provide a detailed description of the issue: What specific issue did you encounter and where? What would you have expected to find instead?
- Optionally, provide additional information. This is the field to put references to external documents, if any.
- Keep the "View Status" as "public"
- 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. |