From b29ede342e992b40cd7984e47dd59ce1a620de86 Mon Sep 17 00:00:00 2001 From: Carsten Bormann Date: Wed, 16 Oct 2024 12:54:38 +0200 Subject: [PATCH] =?UTF-8?q?Add=20language=20alerting=20to=20"CBOR=20decode?= =?UTF-8?q?r"=20=E2=89=A0=20"CDE=20decoder"?= MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit This supplements the changes in PR #19 to Close #18 --- draft-ietf-cbor-cde.md | 4 +++- 1 file changed, 3 insertions(+), 1 deletion(-) diff --git a/draft-ietf-cbor-cde.md b/draft-ietf-cbor-cde.md index 60f3347..59d300b 100644 --- a/draft-ietf-cbor-cde.md +++ b/draft-ietf-cbor-cde.md @@ -391,7 +391,9 @@ Notes: Application profiles such as dCBOR are different as they can affect the data model by restricting some values and ranges. -* CBOR decoders in general are not required to check for preferred +* CBOR decoders in general (as opposed to "CDE decoders" specifically + advertised as supporting CDE) + are not required to check for preferred serialization or CDE and reject inputs that do not fulfill their requirements. However, in an environment that employs deterministic encoding,