From 0e06f96398389227ae15382509baef5dba01b331 Mon Sep 17 00:00:00 2001 From: Eric Murray Date: Wed, 23 Oct 2024 13:23:57 +0100 Subject: [PATCH] Update CAMARA-Security-Interoperability.md --- documentation/CAMARA-Security-Interoperability.md | 3 ++- 1 file changed, 2 insertions(+), 1 deletion(-) diff --git a/documentation/CAMARA-Security-Interoperability.md b/documentation/CAMARA-Security-Interoperability.md index 49b3d9c..15af05a 100644 --- a/documentation/CAMARA-Security-Interoperability.md +++ b/documentation/CAMARA-Security-Interoperability.md @@ -51,11 +51,12 @@ By encapsulating these elements within this document, it aims to provide a compr The target audience for this document is the service/technical departments of operators exposing network functions via standard CAMARA APIs and the applications or client systems that consume CAMARA standard APIs to make use of the operator's network capabilities. - ## Conventions The keywords "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 RFC 2119. +Unless otherwise noted, all the protocol parameter names and values are case sensitive. + ## General Considerations ### Transport Security