Dear Authors/Chairs/ADs, Please see below for comments from one of the experts.
Best regards, David Dong IANA Services Sr. Specialist On Thu Oct 26 18:21:25 2023, [email protected] wrote: > Hello, > > I have reviewed the registration request for draft-ietf-cose-cwt- > claims-in-headers-07 as a Designated Expert for the "COSE Header > Parameters" registry > https://www.iana.org/assignments/cose/cose.xhtml#header-parameters. I > have not consulted with the other expert, so Carsten, if you have any > opinion please go ahead. > > I have a major issue with this registration: this is basically a > duplicate of an existing registration, called "kccs". "kccs" is > described as follows: > > > A CWT Claims Set (CCS) containing a COSE_Key in a 'cnf' claim and > > possibly other claims. CCS is defined in [RFC8392]. > > If my understanding is correct, this is almost exactly what draft- > ietf-cose-cwt-claims-in-headers wants, with the exception that draft- > ietf-cose-cwt-claims-in-headers doesn't give any specification about > which claims are included. I believe registering another parameter, as > requested by draft-ietf-cose-cwt-claims-in-headers, goes against the > guidance given by the Expert Review Instructions of RFC 9052, Section > 11.6: > > > Reviewers are encouraged to get sufficient information for > > registration requests to ensure that the usage is not going to > > duplicate an existing registration > > I note that "kccs" is registered by the EDHOC document in lake: > https://datatracker.ietf.org/doc/draft-ietf-lake-edhoc/ which is not > yet published (it is however in EDIT state in the RFC Editor queue). I > suggest that that document's COSE Header Parameter is changed so that > the description is more general and cover this case as well. > > This could be done by a small change of the name "kccs" to "ccs" and > the following change in the description: > > OLD > A CWT Claims Set (CCS) containing a COSE_Key in a 'cnf' claim and > possibly other claims. CCS is defined in [RFC8392]. > NEW > A CWT Claims Set (CCS) as defined in [RFC8392]. > > (And if that is done, I suggest the same modification is done for > "kcwt"). > > Then draft-ietf-cose-cwt-claims-in-headers would not need to be > published at all. > > Francesca > > From: David Dong via RT <[email protected]> > Date: Tuesday, 17 October 2023 at 20:45 > To: > Cc: Francesca Palombini <[email protected]>, > [email protected] <[email protected]>, [email protected] <[email protected]> > Subject: [IANA #1284212] expert review for draft-ietf-cose-cwt-claims- > in-headers (cose) > Dear Francesca Palombini and Carsten Bormann (cc: cose WG), > > As the designated experts for the COSE Header Parameters registry, can > you review the proposed registration in draft-ietf-cose-cwt-claims-in- > headers-06 for us? Please see: > > https://datatracker.ietf.org/doc/draft-ietf-cose-cwt-claims-in- > headers/ > > The due date is October 31st. > > If this is OK, when the IESG approves the document for publication, > we'll make the registration at: > > https://www.iana.org/assignments/cose/ > > Unless you ask us to wait for the other reviewers, we’ll act on the > first response we receive. > > With thanks, > > David Dong > IANA Services Sr. Specialist _______________________________________________ COSE mailing list [email protected] https://www.ietf.org/mailman/listinfo/cose
