Commit bd6d036f authored by Valerie Aurora (Bow Shock)'s avatar Valerie Aurora (Bow Shock)
Browse files

Update normative and informative reference sections

parent cce97b33
Loading
Loading
Loading
Loading
+4 −23
Original line number Diff line number Diff line
@@ -183,34 +183,15 @@ The present document does not cover other product categories defined in EU Regul

## 2.1 Normative references

> TODO-HAS: Add reference to PT3 for vulnerability handling (see VULH and normative referenecs in the Network Interfaces draft).

**_Editor's Note_: _This Section Needs To Be Updated_**

> **In Harmonised Standards these references shall be specific** (identified by date of publication and/or edition number or version number) **publicly available and in English, except in exceptional circumstances making sure that impacts have been evaluated and explanations have been given on how any negative implications should be avoided** . See clauses 2.10.1 and 8.4 of the [EDRs](EDRs) and the communiqué on "[References in ETSI Deliverables](https://portal.etsi.org/Portals/0/TBpages/edithelp/Docs/News_from_editHelp/References_in_ETSI_deliverables.pdf)".
>
> Guidance for selecting normative references in harmonised standards is given in clause 2.8.3 of the Vademecum on European standardisation. Please **systematically consult with your Technical Officer** for the latest guidance on normative references other than to ENs, ISO/IEC standards, notably to prevent the risk of non-acceptance.
>
> **Legal acts can never be used as normative references.**
>
> It is recommended that the number of references be limited to the minimum needed for the implementation/application of the ETSI Deliverables. References not directly concerned with the implementation/application/understanding of the ETSI Deliverable shall be listed in the Bibliography annex.
>
> References are either specific (identified by date of publication and/or edition number or version number) or non-specific. For specific references, only the cited version applies. For non-specific references, the latest version of the referenced document (including any amendments) applies.
>
> Referenced documents which are not found to be publicly available in the expected location might be found in the [ETSI docbox](https://docbox.etsi.org/Reference/).

> NOTE: While any hyperlinks included in this clause were valid at the time of publication, ETSI cannot guarantee their long-term validity.

The following referenced documents are necessary for the application of the present document.

- <a name="_ref_1">[1]</a> &lt;Standard Organization acronym> &lt;document number> (&lt;version number>): "&lt;Title>".

- <a name="_ref_1">[1]</a> prEN 40000-1-1: “Cybersecurity requirements for products with digital elements – Vocabulary”</a>

## 2.2 Informative references
- <a name="_ref_2">[2] prEN 40000-1-2: “Cybersecurity requirements for products with digital elements - Part 1-2: Principles for cyber resilience”</a>

> TODO-HAS: check if we need to add/remove anything here
- <a name="_ref_3">[3] prEN 40000-1-3: “Cybersecurity requirements for products with digital elements – Vulnerability Handling”</a>

**_Editor's Note_: _This Section Needs To Be Updated_**
## 2.2 Informative references

References are either specific (identified by date of publication and/or edition number or version number) or nonspecific. For specific references, only the cited version applies. For non-specific references, the latest version of the referenced document (including any amendments) applies.