Re: [Cbor] Chunks with tags inside indefinite-length string (major type 2 and 3)
worley@ariadne.com (Dale R. Worley) Wed, 18 December 2019 03:34 UTC
Return-Path: <worley@alum.mit.edu>
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 6A4A212013A for <cbor@ietfa.amsl.com>; Tue, 17 Dec 2019 19:34:02 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.684
X-Spam-Level:
X-Spam-Status: No, score=-1.684 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, HEADER_FROM_DIFFERENT_DOMAINS=0.25, RCVD_IN_DNSWL_LOW=-0.7, SPF_HELO_NONE=0.001, SPF_SOFTFAIL=0.665] autolearn=no autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=comcastmailservice.net
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 K-utk8RW15E5 for <cbor@ietfa.amsl.com>; Tue, 17 Dec 2019 19:34:00 -0800 (PST)
Received: from resqmta-ch2-11v.sys.comcast.net (resqmta-ch2-11v.sys.comcast.net [IPv6:2001:558:fe21:29:69:252:207:43]) (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 4040C120073 for <cbor@ietf.org>; Tue, 17 Dec 2019 19:33:59 -0800 (PST)
Received: from resomta-ch2-12v.sys.comcast.net ([69.252.207.108]) by resqmta-ch2-11v.sys.comcast.net with ESMTP id hPYjip8tpZB3ohQ63i1qzi; Wed, 18 Dec 2019 03:33:59 +0000
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=comcastmailservice.net; s=20180828_2048; t=1576640039; bh=pu+6CuFBh2f3nG3xuXXzbVgfkTR0RaL7HEL7zVk6apo=; h=Received:Received:Received:Received:From:To:Subject:Date: Message-ID; b=QyJuz+86v9Y7v3CvunOFIOqMVvPGbq+7O21IptSCNIR7TB0FE90/d1gVKdmd/AUHE YN1biWnO16jNb4iQVNiqGpQ0/4e8LYFnAkzrtlRWkwEK3qQUzC8WTgOveD7Y6q82JI z0BTx5L2voqz4jWQtSNKcmNOILn+Ml7YNEhjNB4auQ+z2zHr/wtFNV+8sPCFdWJcT2 daBDeLyiQo79JSrq0TBFZN+TdpqaI2xkiHm5VXobmzmDPxgbb3MYTMrf/gIGCgLGCP XqMwad7jFge11OxwVhumJYDobi8OkIJZiLH5Ktw1ZJyO7KSlZBNqpi3kOkw5Mhyy// 0x1bii1ZJhmqQ==
Received: from hobgoblin.ariadne.com ([IPv6:2601:192:4600:1e00:222:fbff:fe91:d396]) by resomta-ch2-12v.sys.comcast.net with ESMTPA id hQ60inQusEu3BhQ61iyR7n; Wed, 18 Dec 2019 03:33:58 +0000
X-Xfinity-VMeta: sc=-100.00;st=legit
Received: from hobgoblin.ariadne.com (hobgoblin.ariadne.com [127.0.0.1]) by hobgoblin.ariadne.com (8.14.7/8.14.7) with ESMTP id xBI3XuBB021299; Tue, 17 Dec 2019 22:33:56 -0500
Received: (from worley@localhost) by hobgoblin.ariadne.com (8.14.7/8.14.7/Submit) id xBI3XsOZ021288; Tue, 17 Dec 2019 22:33:54 -0500
X-Authentication-Warning: hobgoblin.ariadne.com: worley set sender to worley@alum.mit.edu using -f
From: worley@ariadne.com
To: Carsten Bormann <cabo@tzi.org>
Cc: faye.github@gmail.com, cbor@ietf.org
In-Reply-To: <E7A98F5A-256D-4C2D-B001-4054B87F1AF1@tzi.org> (cabo@tzi.org)
Sender: worley@ariadne.com
Date: Tue, 17 Dec 2019 22:33:53 -0500
Message-ID: <8736di2tpa.fsf@hobgoblin.ariadne.com>
Archived-At: <https://mailarchive.ietf.org/arch/msg/cbor/dDmzkMKBmt_PMt4NitNkp3W8iPw>
Subject: Re: [Cbor] Chunks with tags inside indefinite-length string (major type 2 and 3)
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, 18 Dec 2019 03:34:03 -0000
Carsten Bormann <cabo@tzi.org> writes: > Why would we allow tags here? Indefinite strings are a very limited > syntactical structure; there is no need to allow flexibility here (in > particular if there is no semantic gain from that). The reason I argue is that having worked with SIP, I've become very respectful of extensibility. SIP has taken over the internals of every major telecom company, it seems. And that doesn't seem to be because SIP is wonderfully designed; it's sort of a running joke to list the things one would change in the next version of SIP if it didn't have to be upward-compatible. But SIP has a number of very general extensibility mechanisms that make it possible to implement almost any telecomm feature in an upward-compatible way. And there are dozens if not hundreds of SIP extensions. And while I cannot guess what use might be made of tagging chunks of indefinite-length strings, it seems to me that as long as the fundamental structure of CBOR allows such a thing to be constructed unambiguously, the wisest course of action is to make it clear that such constructs can sensibly be made, but the current standard assigns no meaning to them. Dale
- [Cbor] Chunks with tags inside indefinite-length … Faye Amacker
- Re: [Cbor] Chunks with tags inside indefinite-len… Jeffrey Yasskin
- Re: [Cbor] Chunks with tags inside indefinite-len… Jeffrey Yasskin
- Re: [Cbor] Chunks with tags inside indefinite-len… Laurence Lundblade
- Re: [Cbor] Chunks with tags inside indefinite-len… Dale R. Worley
- Re: [Cbor] Chunks with tags inside indefinite-len… Carsten Bormann
- Re: [Cbor] Chunks with tags inside indefinite-len… Dale R. Worley
- Re: [Cbor] Chunks with tags inside indefinite-len… Carsten Bormann