+1
I've read the I-D previously and after skimming it again and all I can
find is one minor nit:
The terms "COSE object", "object" are used synonymously. Without being
familiar with JOSE (or maybe COSE in general) it is not crystal clear,
if you mean COSE envelope including payload ("COSE object") or just
playload ("object"). This is a very minor nit. I assume it would
probably never be confused with just payload and very rarely be confused
with different application specific types of payloads that share the
same content format (not including the COSE envelope).
In general, this work is quite complementary to profiling COSE headers
in general and pulling it in from JOSE is a very convenient step towards
that goal.
Viele Grüße,
Henk
On 15.11.23 22:40, Ivaylo Petrov wrote:
Dear all,
As discussed during IETF 118, this message starts the formal Working
Group Last Call of the draft-ietf-cose-typ-header-parameters-in-headers [1].
The working group last call will run for **three weeks** (due to
thanksgiving), ending on Dec 6, 2023.
Please review and send any comments or feedback to the working
group. Even if your feedback is "this is ready", please let us know.
Thank you,
- Mike and Ivaylo
COSE Chairs
[1]:
https://www.ietf.org/archive/id/draft-ietf-cose-typ-header-parameter-01.html <https://www.ietf.org/archive/id/draft-ietf-cose-typ-header-parameter-01.html>
_______________________________________________
COSE mailing list
[email protected]
https://www.ietf.org/mailman/listinfo/cose
_______________________________________________
COSE mailing list
[email protected]
https://www.ietf.org/mailman/listinfo/cose
