[Cbor] Validity checking and tags

Laurence Lundblade <lgl@island-resort.com> Sun, 03 November 2019 16:57 UTC

Return-Path: <lgl@island-resort.com>
X-Original-To: cbor@ietfa.amsl.com
Delivered-To: cbor@ietfa.amsl.com
Received: from localhost (localhost []) by ietfa.amsl.com (Postfix) with ESMTP id 202F712008F for <cbor@ietfa.amsl.com>; Sun, 3 Nov 2019 08:57:25 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.897
X-Spam-Status: No, score=-1.897 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_HELO_NONE=0.001, SPF_NONE=0.001] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([]) by localhost (ietfa.amsl.com []) (amavisd-new, port 10024) with ESMTP id b8yRade2r4W4 for <cbor@ietfa.amsl.com>; Sun, 3 Nov 2019 08:57:23 -0800 (PST)
Received: from p3plsmtpa06-02.prod.phx3.secureserver.net (p3plsmtpa06-02.prod.phx3.secureserver.net []) (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 3CE0412004A for <cbor@ietf.org>; Sun, 3 Nov 2019 08:57:23 -0800 (PST)
Received: from [] ([]) by :SMTPAUTH: with ESMTPA id RJBpiZe3M4y4cRJBqipfSr; Sun, 03 Nov 2019 09:57:22 -0700
From: Laurence Lundblade <lgl@island-resort.com>
Content-Type: multipart/alternative; boundary="Apple-Mail=_305F2178-37CD-4839-8EB2-C86BCED237DF"
Mime-Version: 1.0 (Mac OS X Mail 12.4 \(3445.104.11\))
Message-Id: <1F1C4AE2-25DB-455F-846C-A262A82A4A33@island-resort.com>
Date: Sun, 3 Nov 2019 08:57:21 -0800
To: cbor@ietf.org
X-Mailer: Apple Mail (2.3445.104.11)
X-CMAE-Envelope: MS4wfIuHZdPxiSpcAYtxyK8lbyDmUHj57ehvAx3D9PcxQAhlqhoHGVmSoiRbQUSovulz1ODOGYFFzEDEPLNJh9lHDGrq6F90Jdd66/8vDZFa4AL9XuBeZgR9 TkgFLvljbsadkHkCElVFfo/w1y/iQIF/1Txadyo6rpz7/282f9U8ju7G
Archived-At: <https://mailarchive.ietf.org/arch/msg/cbor/y1EZ-IylFpJ3_MndQGADSbKhx0s>
Subject: [Cbor] Validity checking and tags
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: Sun, 03 Nov 2019 16:57:25 -0000

Some CBOR protocols will require use of a tag to indicate a particular data type (on a per instance basis) and others will explicitly prohibit use of a tag (on a per instance basis).

That implies that generic validity processing can only be performed on data items that are explicitly tagged. For example generic processing can’t check the internal structure of a decimal fraction for validity unless it is tagged. It just won’t know that it is a decimal fraction.

I think we expect protocols using using these new / custom / registered / bespoke data types to not require instances to be tagged, so validity checking will be limited. 

I think this is mostly OK, but wanted to point it out.

(We refer to these new / custom / registered / bespoke data types primarily as tagged, but then say the tag is not necessary; I think this is confusing).