COSE Virtual Interim

Connection details


Action Items


0. Administrivia (Chairs)

1. Document Status (Chairs)

In RFC Editor queue

In RFC Editor queue

In RFC Editor queue

2. Certificates CBOR encoding

MCR: "C509" seems okay.
Carsten: It might be useful while there are systems that read only one of the types of the certificate and other systems in the same communication that read only the other.
MCR: I understood this as being able to send post quantum algorithm (in LAMPS meeting).
John: Isn't this just a new algorithm and we can use it as such?
MCR: People want to be able to issue PQ algorithm, while there might be devices that are still not capable of reading those PQ signatures.

Something broken on audio, but:
The use case I see is using EDHOC for unilaterally authenticated operations ("Get page from weather service and be sure it's from the weather service, which is open to everyone")
That's similar but not identical to the TOFU (trust on first use?) case of SSH-style deployments.

3. AOB

MCR: This should not be responsiblility of the WG, but we probably should mark the code in our repository as archived and provide a link to a fork should work well.
Mike: I agree, this is not a WG project, but it would make sense to send a note on the ML if you fork it and continue to develop it.

Jonathan: How are PR accepted, who verifies them, etc.
Carsten: This is probably slightly different than the Java implementation
MCR: Probably the WG should
Mike: I agree that the WG should be responsible for that one.
MCR: Probably it would be useful to send github summary