Re: [Cbor] Private Use Tags
Richter, Jörg <Joerg.Richter@pdv-FS.de> Tue, 19 February 2019 12:44 UTC
Return-Path: <Joerg.Richter@pdv-FS.de>
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 B6C90130E91 for <cbor@ietfa.amsl.com>; Tue, 19 Feb 2019 04:44:47 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.92
X-Spam-Level:
X-Spam-Status: No, score=-0.92 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, FROM_EXCESS_BASE64=0.979, URIBL_BLOCKED=0.001] autolearn=no 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 B8qubFnoAsy9 for <cbor@ietfa.amsl.com>; Tue, 19 Feb 2019 04:44:46 -0800 (PST)
Received: from mail.pdv-fs.de (mail.pdv-fs.de [213.208.220.5]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 8D7B212867A for <cbor@ietf.org>; Tue, 19 Feb 2019 04:44:45 -0800 (PST)
Received: from EXCHDB1.pdv-fs.de (192.168.180.94) by EXCHDB2.pdv-fs.de (192.168.180.95) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA256_P256) id 15.1.1466.3; Tue, 19 Feb 2019 13:44:42 +0100
Received: from EXCHDB1.pdv-fs.de ([fe80::6c4a:8b1b:60f4:4437]) by EXCHDB1.pdv-fs.de ([fe80::6c4a:8b1b:60f4:4437%15]) with mapi id 15.01.1466.012; Tue, 19 Feb 2019 13:44:42 +0100
From: "Richter, Jörg" <Joerg.Richter@pdv-FS.de>
To: Carsten Bormann <cabo@tzi.org>
CC: "cbor@ietf.org" <cbor@ietf.org>
Thread-Topic: [Cbor] Private Use Tags
Thread-Index: AdTIOqbH7vBaupuMSHSPiypDCyPcOQAC2yoAAAJ3lNA=
Date: Tue, 19 Feb 2019 12:44:42 +0000
Message-ID: <9b9d1eb961f74114b466c8ea0c5bce39@pdv-FS.de>
References: <c262a6100b0d4aaea6fefeff36ad7403@pdv-FS.de> <D495FA59-3701-433F-A32A-00C1316D9365@tzi.org>
In-Reply-To: <D495FA59-3701-433F-A32A-00C1316D9365@tzi.org>
Accept-Language: de-DE, en-US
Content-Language: de-DE
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [192.168.180.93]
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64
MIME-Version: 1.0
Archived-At: <https://mailarchive.ietf.org/arch/msg/cbor/ohy9WuyDh1QSpb5dpcsXAPg0V18>
Subject: Re: [Cbor] Private Use 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: Tue, 19 Feb 2019 12:44:48 -0000
Good point. At the moment I use tag 27 for it. (Serialised language-independent object with type name and constructor arguments) The disadvantage is that the CBOR encoding is quite long. But I think I'll keep that for now and allocate tags when the need grows. > -----Original Message----- > From: Carsten Bormann [mailto:cabo@tzi.org] > Sent: Tuesday, February 19, 2019 1:27 PM > To: Richter, Jörg > Cc: cbor@ietf.org > Subject: Re: [Cbor] Private Use Tags > > Hi Jörg, > > The IETF has a long and checkered history with private-use allocations. > > Generally, the observation is that private-use allocations start to get > used for something that does get wide deployment, and suddenly, those > allocations take on specific semantics and no longer truly are available > for private use. > This is somewhat related to the “X-Dash problem”, which is discussed in > RFC 6648. > > Instead, you can just go ahead and register the tags “Jörg Richter Private > 1” to “Jörg Richter Private 10”. (Preferably in the 1+2 or, if the > allocation is huge, 1+4 byte space.) The Tag number space is huge, so it > is unlikely we will run out because of such private use allocations. And > if one of these suddenly takes off, you can keep the number and change the > name (and supply a specification, I hope). (You might want to use a > middle person for the allocation if you don’t even want to disclose that > you are using CBOR Tags.) > > Grüße, Carsten > > > On Feb 19, 2019, at 11:11, Richter, Jörg <Joerg.Richter@pdv-FS.de> > wrote: > > > > I had the idea to tag some internal types. These types are > > never transferred to other communication partners. > > Would it be possible to provide a tag range that is explicitly > > marked as "Private Use Area"? This would exclude the > > possibility that these tags will be assigned in the future and > > that there will be a collision. > > > > > > _______________________________________________ > > CBOR mailing list > > CBOR@ietf.org > > https://www.ietf.org/mailman/listinfo/cbor
- [Cbor] Private Use Tags Richter
- Re: [Cbor] Private Use Tags Carsten Bormann
- Re: [Cbor] Private Use Tags Richter
- Re: [Cbor] Private Use Tags Brian E Carpenter