[T2TRG] CoRAL Dictionaries and the side meeting yesterday

Jim Schaad <ietf@augustcellars.com> Wed, 20 November 2019 01:36 UTC

Return-Path: <ietf@augustcellars.com>
X-Original-To: t2trg@ietfa.amsl.com
Delivered-To: t2trg@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 6FC0812092A for <t2trg@ietfa.amsl.com>; Tue, 19 Nov 2019 17:36:10 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.9
X-Spam-Level:
X-Spam-Status: No, score=-1.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_NONE=-0.0001, SPF_HELO_NONE=0.001, SPF_PASS=-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 3z5F20wPWTMS for <t2trg@ietfa.amsl.com>; Tue, 19 Nov 2019 17:36:09 -0800 (PST)
Received: from mail2.augustcellars.com (augustcellars.com [50.45.239.150]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id B72D6120935 for <T2TRG@irtf.org>; Tue, 19 Nov 2019 17:36:08 -0800 (PST)
Received: from Jude (73.180.8.170) by mail2.augustcellars.com (192.168.0.56) with Microsoft SMTP Server (TLS) id 15.0.1395.4; Tue, 19 Nov 2019 17:36:01 -0800
From: Jim Schaad <ietf@augustcellars.com>
To: 'Klaus Hartke' <klaus.hartke@ericsson.com>
CC: T2TRG@irtf.org
Date: Wed, 20 Nov 2019 09:36:00 +0800
Message-ID: <01c301d59f42$deb32d00$9c198700$@augustcellars.com>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
X-Mailer: Microsoft Outlook 16.0
Thread-Index: AdWfPI/v0UnGJicMSuqPzsXT0JLSAA==
Content-Language: en-us
X-Originating-IP: [73.180.8.170]
Archived-At: <https://mailarchive.ietf.org/arch/msg/t2trg/_UTSyb6ScfWnJhffHX_AsTx5Nho>
Subject: [T2TRG] CoRAL Dictionaries and the side meeting yesterday
X-BeenThere: t2trg@irtf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: IRTF Thing-to-Thing Research Group <t2trg.irtf.org>
List-Unsubscribe: <https://www.irtf.org/mailman/options/t2trg>, <mailto:t2trg-request@irtf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/t2trg/>
List-Post: <mailto:t2trg@irtf.org>
List-Help: <mailto:t2trg-request@irtf.org?subject=help>
List-Subscribe: <https://www.irtf.org/mailman/listinfo/t2trg>, <mailto:t2trg-request@irtf.org?subject=subscribe>
X-List-Received-Date: Wed, 20 Nov 2019 01:36:11 -0000

Klaus,

I am still having some problems with the way that you described how
dictionaries would work for CoRE apps with a single dictionary being used.

My understanding of what you said is that:
1.  We would define a CoRE apps dictionary and pre-populate it with some of
the common items
2.  For each new CoRE app created (by the IETF?) the dictionary will be
extended by adding the new items to the dictionary (maybe the end, maybe
later)

The assumption here seems to be that a CoRE app would never be extended with
new things.  As an example of what I mean consider the following:

*  Given the intense pressure from the ACE working group, the CoRE WG gets
it act together and releases a version 1 Pub-Sub server.  
* So a client and a server are released which use the dictionary for
compression and are both happy.
*  A version 2 of the Pub-Sub server gets released.  This adds some
vocabulary around wills.  The vocabulary is then added to the CoRE App
dictionary
*  The Pub-Sub server gets updated because it is a big box, but the client
does not because it is small
*  The client queries the Pub-Sub server and gets back some compression
points which it does not recognize.

What am I missing?

Jim