From bea5b590a893df3f3aedb0ae7755cc9692d525b8 Mon Sep 17 00:00:00 2001 From: Steven Bellock Date: Fri, 22 Sep 2023 10:43:45 -0700 Subject: [PATCH] Remove requirements terminology (#110) Fix #58. The specification does not follow RFC2119 and there isn't time to go through everything to figure out what is normative and what isn't, so let's just remove the section. Signed-off-by: Steven Bellock --- doc/Caliptra.md | 4 ---- 1 file changed, 4 deletions(-) diff --git a/doc/Caliptra.md b/doc/Caliptra.md index 78100ff..1196b98 100644 --- a/doc/Caliptra.md +++ b/doc/Caliptra.md @@ -85,10 +85,6 @@ The following acronyms and abbreviations are used throughout this document. | **TEE** | Trusted Execution Environment | | **TRNG** | True Random Number Generator | -# Requirements terminology - -The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", "SHOULD", "SHOULD NOT", "RECOMMENDED", "NOT RECOMMENDED", "MAY", and "OPTIONAL" in this document are to be interpreted as described in [[BCP 14](https://tools.ietf.org/html/bcp14)] [[RFC2119](https://tools.ietf.org/html/rfc2119)] [[RFC8174](https://tools.ietf.org/html/rfc8174)] when, and only when, they appear in all capitals. - # References 1. NIST Special Publication 800-193 Platform Firmware Resiliency Guidelines