Subject: [Cbor] Fwd: [cbor-wg/CBORbis] Try for two levels of decoding error? (#45)

From: Carsten Bormann <[email-masked]>
Date: Wed, 13 Mar 2019 14:50:14 +0100

With much of Jeffrey’s #17 accepted (in slightly edited form as #61), I think we can revisit #45.

Here is my most recent comment on the issue.

Are the three levels the right ones?
Have we nailed strict mode?

Fresh editor’s copy at https://cbor-wg.github.io/CBORbis/draft-ietf-cbor-7049bis.html <https://cbor-wg.github.io/CBORbis/draft-ietf-cbor-7049bis.html>
(all variants via https://cbor-wg.github.io/CBORbis/ <https://cbor-wg.github.io/CBORbis/> ).

Grüße, Carsten

> Begin forwarded message:
> 
> From: cabo <[email-masked] <mailto:[email-masked]>>
> Subject: Re: [cbor-wg/CBORbis] Try for two levels of decoding error? (#45)
> Date: March 13, 2019 at 14:44:39 GMT+1
> To: cbor-wg/CBORbis <[email-masked] <mailto:[email-masked]>>
> Cc: Subscribed <[email-masked] <mailto:[email-masked]>>
> Reply-To: cbor-wg/CBORbis <reply+00f4be62a8c49a99fc36[email-masked] <mailto:reply+00f4be62a8c49a99fc36[email-masked]>>
> 
> Essentially, we now have three levels:
> 
> well-formed (vs. syntactic error). Not well-formed is now MUST NOT generate/accept.
> valid (vs. semantic error). Protocol encoders now MUST generate valid CBOR.
> expected (vs. unexpected by application). This is application-specific and often expressed in CDDL.
> I'm not sure we have all in order for strict mode, so I'll leave this open for now, but I think we have nailed the levels.
> 
> —
> You are receiving this because you are subscribed to this thread.
> Reply to this email directly, view it on GitHub <https://github.com/cbor-wg/CBORbis/issues/45#issuecomment-472427263>, or mute the thread <https://github.com/notifications/unsubscribe-auth/APS-YipaO0K5_D9d09aBmqS9K5TAdYR_ks5vWQDHgaJpZM4ZnGKu>.
>