IETF Logo Mail Archive

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

Carsten Bormann <cabo@tzi.org> Wed, 13 March 2019 13:50 UTC

Return-Path: <cabo@tzi.org>
X-Original-To: cbor@ietfa.amsl.com
Delivered-To: cbor@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id B2266129284 for <cbor@ietfa.amsl.com>; Wed, 13 Mar 2019 06:50:26 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.298
X-Spam-Level:
X-Spam-Status: No, score=-2.298 tagged_above=-999 required=5 tests=[HTML_MESSAGE=0.001, RCVD_IN_DNSWL_MED=-2.3, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id eZ48tH9XwVaU for <cbor@ietfa.amsl.com>; Wed, 13 Mar 2019 06:50:24 -0700 (PDT)
Received: from mailhost.informatik.uni-bremen.de (mailhost.informatik.uni-bremen.de [IPv6:2001:638:708:30c9::12]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 349C21240D3 for <cbor@ietf.org>; Wed, 13 Mar 2019 06:50:24 -0700 (PDT)
X-Virus-Scanned: amavisd-new at informatik.uni-bremen.de
Received: from submithost.informatik.uni-bremen.de (submithost2.informatik.uni-bremen.de [134.102.200.7]) by mailhost.informatik.uni-bremen.de (8.14.5/8.14.5) with ESMTP id x2DDoFeG018172 for <cbor@ietf.org>; Wed, 13 Mar 2019 14:50:20 +0100 (CET)
Received: from client-0134.vpn.uni-bremen.de (client-0134.vpn.uni-bremen.de [134.102.107.134]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by submithost.informatik.uni-bremen.de (Postfix) with ESMTPSA id 44KCs332b2z1Bp8; Wed, 13 Mar 2019 14:50:15 +0100 (CET)
From: Carsten Bormann <cabo@tzi.org>
Content-Type: multipart/alternative; boundary="Apple-Mail=_7B5CC273-2273-4917-96BF-9F44B7A12BCD"
X-Mao-Original-Outgoing-Id: 574177811.714317-b2c7b631d380081746514daaf0bc584b
Mime-Version: 1.0 (Mac OS X Mail 11.5 \(3445.9.1\))
Date: Wed, 13 Mar 2019 14:50:14 +0100
Message-Id: <599B84C7-3581-4339-BB5F-C02D5FDD1BDB@tzi.org>
References: <cbor-wg/CBORbis/issues/45/472427263@github.com>
To: cbor@ietf.org
X-Mailer: Apple Mail (2.3445.9.1)
Archived-At: <https://mailarchive.ietf.org/arch/msg/cbor/lHyfJ20ICgqhOaYbDZk2L-gPIdo>
Subject: [Cbor] Fwd: [cbor-wg/CBORbis] Try for two levels of decoding error? (#45)
X-BeenThere: cbor@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: "Concise Binary Object Representation \(CBOR\)" <cbor.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/cbor>, <mailto:cbor-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/cbor/>
List-Post: <mailto:cbor@ietf.org>
List-Help: <mailto:cbor-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/cbor>, <mailto:cbor-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 13 Mar 2019 13:50:27 -0000

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 <notifications@github.com <mailto:notifications@github.com>>
> 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 <CBORbis@noreply.github.com <mailto:CBORbis@noreply.github.com>>
> Cc: Subscribed <subscribed@noreply.github.com <mailto:subscribed@noreply.github.com>>
> Reply-To: cbor-wg/CBORbis <reply+00f4be62a8c49a99fc36ffb59deedd89656aa5d99e3b2c0e92cf0000000118a0cb4792a169ce17908f7d@reply.github.com <mailto:reply+00f4be62a8c49a99fc36ffb59deedd89656aa5d99e3b2c0e92cf0000000118a0cb4792a169ce17908f7d@reply.github.com>>
> 
> 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>.
>

v2.23.0 | Report a Bug | By Email