Agenda and notes:
Documents that have left the WG
tags-oid has been in RFC-EDITOR state for a week
WG documents status and issues
cddl-control: stalling for lack of review?
who read? only CA (shepherd), FP (AD)
Ask Henk? CB: Document has three relatively independent parts, reviewers could do only one each and still be helpful.
Ongoing maps discussions
Brendan’s review of packed
Carsten’s knee-jerk: https://mailarchive.ietf.org/arch/msg/cbor/GVecTtrIZIDDwvGKlXtCGxF8nFE
YANG-CBOR/SID has an IANA DE block (yes, media-types again), PR #21 about to resolve that
CB: As WG not only need to get CBOR part right but also help with integration in context. Typical stumbling point: Getting media types defined. Happened here again. Maybe CoRE choice with parameterized media type was not too bright (not accurately reflected in formal part of IANA registration), but maybe at some point create manual “how to get CBOR media types defined” so it gets past designated experts/IESG.
CB: If you do IANA reg in one document planning ahead for another document, does that create a normative reference from the planning-ahead to the using document? Need to discuss with normative-reference afficionados. Has occurred in several places. Need thinking about purpose of registries etc.
CBOR use in other SDOs
“JSON”: JSON OBJECT with short keys (v,tg,mp…)
“CBOR”: CBOR, keys still text
“COSE”: COSE, signing the CBOR (see below), CWT claim -260 == hcert Health Certificate hcert -260 map [European_eHealth_Network] Certificate
“COMPRESSED”: useless zlib COMPRESSION,
“BASE45”: for QR-code, not-so-bright BASE45,
“PREFIX”: Add Prefix HC(x):,
18([<< {4: h'04BDE79BDB2AE660', 1: -7} >>, {}, << {4: 1620237600, 6: 1620064800, 1: "AT", -260: {1: {"v": [{"dn": 1, "ma": "ORG-100030215", "vp": "1119305005", "dt": "2021-02-18", "co": "AT", "ci": "urn:uvci:01:AT:10807843F94AEE0EE5093FBC254BD813P", "mp": "EU/1/20/1528", "is": "BMSGPK Austria", "sd": 2, "tg": "840539006"}], "nam": {"fnt": "MUSTERFRAU<GOESSINGER", "fn": "Musterfrau-G\u00f6\u00dfinger", "gnt": "GABRIELE", "gn": "Gabriele"}, "ver": "1.0.0", "dob": "1998-02-26"}}} >>, h'151971B37480C44FFB882793D4D7A073A9367EEF3F5AC33A328F17054625E4BFC55CF6F7C038FF08E488090FE20D6CFFBB44D7614AA21A79503D7857854E857B'])
Guidance for CBOR users? Draft on base45 is “The Base45 Data Encoding”, Patrik Faltstrom, Fredrik Ljunggren, Dirk-Willem van Gulik, 2021-06-14, draft-faltstrom-base45
This document describes the Base45 encoding scheme which is built upon the Base64, Base32 and Base16 encoding schemes.
AOB
Attendance:
2. Christian Amsüss, chair
3. Francesca Palombini
4. Rikard Höglund
5. Peter Yee, AKAYLA
6. Marco Tiloca, RISE
7. Emile Cormier
8. Carsten Bormann, TZI