CBOR WG Meeting - Interim 09
Wednesday, June 19, 2019, 15:00 - 16:00 UTC
Chairs: Francesca Palombini, Jim Schaad

Webex recording: https://ietf.webex.com/recordingservice/sites/ietf/recording/playback/d2409777efd0452da013f3491844d162


Presents:
    * Francesca Palombini
    * Jim Schaad
    * Carsten Bormann
    * Jeffrey Yasskin
    * Michael Richardson
    * Laurence Lundblade
    
* WG status update
    
    - CDDL -> Congratulations!
    
    - charter (https://github.com/cbor-wg/charter/blob/master/charter-01.md )
    
NEW:    
There are a number of additional CBOR tagged types and media type specifications that are either currently
adopted by the working group, by other working groups, or as individual
submissions. Additionally, there are expected to be other such documents
that will come to the attention of the working group. In some cases, the
working group expects to adopt and publish these proposals.

The working group will evaluate and place such proposals in one of the following
categories using a dispatch like process:
    
 *   General purpose specifications that are expected to have broad usage: The
 working group will normally adopt and publish such proposals. Examples of
 proposals in this category are the CBOR Sequence media type (draft-bormann-cbor-sequence)
 and the Error Indications tag (draft-richter-cbor-error-tag).

* Internet wide specific purpose specifications: The working group may decide to adopt these proposals, but typically it would just provide input and recommend that they be published either as an Independent Submission or by a different working group.

* Narrow purpose specifications: The working group may provide evaluation of such proposals, but typically would not support Working Group adoption, and could recommend publication in a different forum. An example of this might be portions of draft-bormann-cbor-tags-oid dealing with some of the more esoteric types such as regular expressions.

* CBOR specification: https://tools.ietf.org/html/draft-ietf-cbor-7049bisCBORBis
    - Status update - https://github.com/cbor-wg/CBORbis/
    - Issue discussion
Leftover: 
    - #18 (non-core tagged types)
    - #69 (security considerations)
    LL: continue the discussion that is on https://github.com/cbor-wg/CBORbis/pull/69    
    - minor editorial PR
    - issues left:
      * 79 -> editorial
      * 77 -> would be good with webauthn people feedback. Editorial clarification that this is one way of doing it and we are not necessarily recommending this particular way. Write a proposal and bring to the list.
      * 71 -> need some text clarifying the role of validation for generic decoders. Take to the list
    
* Array-tag
- issue #7
JY: proposal to split to different document
CB: But we have the registration
JS: Then we should not
CB: proposal to give an example use case