NFV Issue Tracker
The NFV Issue Tracker allows anyone to report feedback on the NFV Public DRAFTs available in the NFV Open Area.
Each Public Draft has an associated Issue Tracker project. To access the appropriate one just click on the direct links listed in the table below:
[You will first have to login with your EOL account, or create yourself an account (see instructions further down)]
| Draft Reference | Scope & schedule | Direct link to Issue Tracker |
|---|---|---|
| NFV001 edition311 "NFV Use Cases" | NFV001 edition311 details | NFV001 edition311 issue tracker |
| EVE001 "Hypervisor Rqmts spec" | EVE001 details | EVE001 issue tracker |
| EVE002 "MEF Use Cases report" | EVE002 details | EVE002 issue tracker |
| EVE003 "NFVI Node Arch report" | EVE003 details | EVE003 issue tracker |
| EVE004 "Virtualisation technologies Report" | EVE004 details | EVE004 issue tracker |
| EVE005 "SDN usage in NFV Report" | EVE005 details | EVE005 issue tracker |
| EVE007 "NFVI Hw rqmts spec" | EVE007 details | |
| EVE008 "Charging and Billing report" | EVE008 details | |
| EVE009 "E2E Process Descriptions report" | EVE009 details | |
| IFA001 "Acceleration 1 - UCs report" | IFA001 details | IFA001 issue tracker |
| IFA002 "Acceleration 2 - VNF Intface Spec" | IFA002 details | IFA002 issue tracker |
| IFA002 edition221 "Acceleration - VNF Intface Spec" | IFA002 ed221 details | use IFA002 issue tracker (above) |
| IFA003 "Acceleration 3 - vSwitch Spec" | IFA003 details | IFA003 issue tracker |
| IFA004 "Acceleration 4 - Mgmt aspects Spec" | IFA004 details | IFA004 issue tracker |
| IFA005 "Or-Vi ref point Spec" | IFA005 details | IFA005 issue tracker |
| IFA006 "Vi-Vnfm ref point Spec" | IFA006 details | IFA006 issue tracker |
| IFA007 "Or-Vnfm ref point Spec" | IFA007 details | IFA007 issue tracker |
| IFA008 "Ve-Vnfm ref point Spec" | IFA008 details | IFA008 issue tracker |
| IFA009 "MANO architectural options report" | IFA009 details | IFA009 issue tracker |
| IFA010 "MANO Functional Rqmts Spec" | IFA010 details | IFA010 issue tracker |
| IFA010 edition221 "MANO Functional Rqmts Spec" | IFA010 ed221 details | use IFA010 issue tracker (above) |
| IFA011 "VNF Packaging Spec" | IFA011 details | IFA011 issue tracker |
| IFA012 "Os-Ma-Nfvo ref point Spec - svc mgmt & info model" | IFA012 details | IFA012 issue tracker |
| IFA013 "Os-Ma-Nfvo ref point Spec - info model" | IFA013 details | IFA013 issue tracker |
| IFA014 "Network Service Templates Specification" | IFA014 details | IFA014 issue tracker |
| IFA015 "NFV Information Model Report" | IFA015 details | IFA015 issue tracker |
| IFA016 "Papyrus Guidelines" | IFA016 details | IFA016 issue tracker |
| IFA017 "UML Modeling Guidelines" | IFA017 details | IFA017 issue tracker |
| IFA018 "Acceleration Intface Spec" | IFA018 details | IFA018 issue tracker |
| IFA019 "Resource Mgmt Acceleration @ Nf-Vi - Spec" | IFA019 details | IFA019 issue tracker |
| IFA020 "NFVO decomposition options report" | IFA020 details | IFA020 issue tracker |
| IFA021 "MANO and automated deployment report" | IFA021 details | IFA021 issue tracker |
| IFA022 "Multi-Site Services report" | IFA022 details | IFA022 issue tracker |
| IFA023 "Policy Mgmt in MANO report" | IFA023 details | IFA023 issue tracker |
| REL002 "Scalable Arch for Reliability Report" | REL002 details | REL002 issue tracker |
| REL003 "E2E reliability models report" | REL003 details | REL003 issue tracker |
| REL004 "Active monitoring & failure detection report" | REL004 details | REL004 issue tracker |
| REL005 "Quality Accountability Framework" | REL005 details | REL005 issue tracker |
| REL006 "SW Upgrade spec" | REL006 details | REL006 issue tracker |
| REL007 "MANO resilience report" | REL007 details | REL007 issue tracker |
| REL008 "Error Handling report" | REL08 details | REL08 issue tracker |
| SEC002 "Security features in mgmt sofware report" | SEC002 details | SEC002 issue tracker |
| SEC003 Security and Trust Guidance | SEC003 details | SEC003 issue tracker |
| SEC004 "LI report" | SEC004 details | SEC004 issue tracker |
| SEC005 "Certificate mgmt report" | SEC005 details | SEC005 issue tracker |
| SEC006 "Sec & Regulation report" | SEC006 details | SEC006 issue tracker |
| SEC007 "NFV Attestation report" | SEC007 details | SEC007 issue tracker |
| SEC008 "Security Monitoring report" | SEC008 details | SEC008 issue tracker |
| SEC009 "UCs for multi-layer host admin" | SEC009 details | SEC009 issue tracker |
| SEC010 "Retained Data Report" | SEC010 details | SEC010 issue tracker |
| SEC011 "LI Architecture Report" | SEC011 details | SEC011 issue tracker |
| SEC012 Arch for sensitive components - Spec | SEC012 details | SEC012 issue tracker |
| SEC013 Sec mgmt & Monitoring Spec | SEC013 details | SEC013 issue tracker |
| SEC014 "MANO Security Spec" | SEC014 details | SEC014 issue tracker |
| SOL001 "TOSCA-based NFV descriptors spec" | SOL001 details | SOL001 issue tracker |
| SOL002 "Ve-Vnfm RESTful protocols spec" | SOL002 details | SOL002 issue tracker |
| SOL003 "Or-Vnfm protocols spec" | SOL003 details | SOL003 issue tracker |
| SOL004 "VNF Package Stage 3" | SOL004 details | SOL004 issue tracker |
| SOL005 "Os-Ma-nfvo APIs" | SOL005 details | SOL005 issue tracker |
| SOL006 "YANG based NFV Descriptors spec" | SOL006 details | SOL006 issue tracker |
| SOL007 "NSD file structure spec" | SOL007 details | SOL007 issue tracker |
| SOL009 "MANO mgmt stage 3" | SOL009 details | SOL009 issue tracker |
| SOL010 "VNF snapshot pkg stage 3" | SOL010 details | SOL010 issue tracker |
| SOL011 "Or-Or Stage 3" | SOL011 details | SOL011 issue tracker |
| SOL012 "Protocol Spec for Policy Mgmt Intface" | SOL012 details | SOL012 issue tracker |
| SOL014 "VR_descriptor_stage_3" | SOL014 details | SOL014 issue tracker |
| SOL016 "MANO Stage 3 procedures spec" | SOL016 details | SOL016 issue tracker |
| SOL018 "CCM stage 3" | SOL018 details | SOL018 issue tracker |
| TST001 "Pre-deployment Validation report" | TST001 details | TST001 issue tracker |
| TST002 "Iop Testing Methodology report" | TST002 details | TST002 issue tracker |
| TST004 "NFVI_PATH_TEST report" | TST004 details | TST004 issue tracker |
| TST005 "VNF_snapshot_report" | TST005 details | TST005 issue tracker |
| TST006 "CICD & Devops report" | TST006 details | TST006 issue tracker |
| TST007 "VIM/VNFM Iop Testing Guidelines" | TST007 details | TST007 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).
Go to the ETSI NFV Issue Tracker and login.
User with EOL account can view and create issues, but users without EOL account can only view issues.
Issue tracker allows normal users to submit new issues and view public issues, but does not allow to process issues.
Chairs, Vice-Chairs, and Rapporteurs have a "Developer" or "Maintainer" role, which additionally allows viewing private issues and processing issues.
View Issues
1. Go to the ETSI NFV Issue Tracker and login.
2. To view the list of all issues, click "Issues" under "Pinned" drop down button.
3. To view issues by assignee, author, or label, click the search bar and choose the relevant option.
4. To find issues related to a specific specification, version, or other details, use the search bar to enter your keywords.
5. To view the details of a specific issue, click title of the issue.
1. Go to the ETSI Forge NFV Group.
2. Click on the "Issues" repository.
3. View issues as mentioned in the Step 2 of the previous section.
Submitting an Issue to the Issue Tracker
For Non-EOL Users
Non-EOL users cannot report issues directly via the ETSI NFV Issue Tracker. However, it is recommended that they submit their issues by sending an email to "NFVsupport@etsi.org".
For EOL Users
Go to the ETSI NFV Issue Tracker and login.
Before creating a new issue, please check that:
a) The issue still exists in the latest version of the respective GS document, and
b) 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 create a new issue:
- Go to ETSI NFV Issue Tracker, click "Issues" under "Pinned" drop down button, and click "New issue".
- The Type is default set to "Issue" don't change it.
- Issue Title: In the issue Title input field, provide a clear and concise one-line summary of the issue.
- Following the format: [Version] <NFV-Specification> <Issue_title>
- For example: [v5.1.1] NFV-SOL003 Missing attribute in Query Compute Resources
- Issue description: In the description input box, clearly explain the issue. Describe what the issue is, what the expected outcome should be, and include any additional details or links to relevant documents if available.
- Setting additional fields:
- Assignee: If you are going to resolve the issue yourself, choose "assign yourself" in the "Assignee" field. Otherwise, its Chair, Co-chair, or rapporteur, responsibility to assign the issue to the relevant individual.
- Labels: Use labels to help organize and filter issues. When creating an issue, make sure to:
- Add the appropriate ISG NFV Working Group (WG) label (e.g., "NFV-SOL" for a SOL specification issue).
- Choose a label that describes the issue category: Bug, Clarification, or Feature Gap.
- Dates and Milestone: If you are unsure with the dates and milestone, leave these fields as they are. These fields are supposed to be managed by Chairs, Vice-Chairs, or Rapporteurs, if needed.
- Once all necessary details are added, click "Create issue" to submit.
In case of confidential issues:
- 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, send it via email to "NFVsupport@etsi.org".
- Note: We should keep our own issues public whenever possible, as this helps reducing duplicate reports.
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. |
Monitoring Relevant Issue(s)
By default, the issue reporter (or creator) receives email notifications when someone comments on the issue, updates its status (e.g., closed or reopened), or performs other related actions. However, if you want to manage notifications for the issue(s) you are involved in:
1. Log in to the ETSI NFV Issue Tracker.
2. In the Issue repository, click the bell icon in the issue repository and select "Participate" to receive updates on issues you are part of.
3. Select "On mention" option, to get notified only when you are specifically mentioned in a comment.
4. To stop receiving email notifications, select the "Disabled" option.
Monitor All Issues
Users can also subscribe to receive email notifications for all activities within the repository.
1. Log in to the ETSI NFV Issue Tracker.
2. In the Issue repository, click the bell icon in the issue repository and select "Watch" to get notified for all activity in the Issue repository.
3. To stop receiving email notifications, select the "Disabled" option.
