Re: [Secdispatch] [Cbor] Ciphertext format draft

[Carsten Bormann <[e-mail]>]

Hi Yaron,

Here is a quick update proposal to the CDDL:


var_header = {
        K_KEY_PROVIDER => uint,
        K_KEY_ID => bstr,
        ? K_KEY_VERSION => uint,
        ? K_AUX_DATA => bstr,
        ? K_NONCE => bstr,
        ? K_AUTH_TAG => bstr,
        ? K_AAD => bstr,
        * (k_ext .feature "header-extension") => any
}

k_ext = uint .ge K__EXTENSIONS

; K_RESERVED = 0
K_KEY_PROVIDER = 1
K_KEY_ID = 2
K_KEY_VERSION = 3
K_AUX_DATA = 4
K_NONCE = 5
K_AUTH_TAG = 6
K_AAD = 7
        ; extend from here
K__EXTENSIONS = 8



The idea is to use “.feature” to clearly identify extensions from the base set.

This would give you validator output like

** Features potentially used: header-extension: [1577, 4416, 3178, 2698]
/var_header/ {1: 2286, 2: /bstr/ h'686F74626564', 3: 4661,
 5: /bstr/ h'756E70726F70656E7365',
 6: /bstr/ h'6F7879616E746872617175696E6F6E65',
 7: /bstr/ h'636572656272616C6C79', 1577: /any/ "feeze",
 4416: /any/ "bronchiolitis", 3178: /any/ "mesole", 2698: /any/ "parvoline”}

so you know which extensions are in use.

Grüße, Carsten