Hi Göran, Thanks for your response and for considering the comments.
Thanks, Ketan On Mon, May 4, 2026 at 6:42 PM Göran Selander <[email protected]> wrote: > Hi Ketan, > > Thanks for your review. Please find responses to your comments inline > below, with reference to PR > <https://github.com/cose-wg/CBOR-certificates/pull/384>#384 > <https://github.com/cose-wg/CBOR-certificates/pull/384>: > > For overview of the current state of the draft, see Editor’s copy: > > https://cose-wg.github.io/CBOR-certificates/draft-ietf-cose-cbor-encoded-cert.html > > Thanks, > Göran > > *From: *Ketan Talaulikar via Datatracker <[email protected]> > *Date: *Monday, 27 April 2026 at 11:29 > *To: *The IESG <[email protected]> > *Cc: *[email protected] <[email protected]>; [email protected] < > [email protected]>; [email protected] < > [email protected]>; [email protected] < > [email protected]> > *Subject: *Ketan Talaulikar's No Objection on > draft-ietf-cose-cbor-encoded-cert-18: (with COMMENT) > > Ketan Talaulikar has entered the following ballot position for > draft-ietf-cose-cbor-encoded-cert-18: No Objection > > When responding, please keep the subject line intact and reply to all > email addresses included in the To and CC lines. (Feel free to cut this > introductory paragraph, however.) > > > Please refer to > https://eur02.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.ietf.org%2Fabout%2Fgroups%2Fiesg%2Fstatements%2Fhandling-ballot-positions%2F&data=05%7C02%7Cgoran.selander%40ericsson.com%7Ca72dc4fef81c4183b82808dea43f8a2e%7C92e84cebfbfd47abbe52080c6b87953f%7C0%7C0%7C639128789973188692%7CUnknown%7CTWFpbGZsb3d8eyJFbXB0eU1hcGkiOnRydWUsIlYiOiIwLjAuMDAwMCIsIlAiOiJXaW4zMiIsIkFOIjoiTWFpbCIsIldUIjoyfQ%3D%3D%7C0%7C%7C%7C&sdata=pDaQ%2FN6WCNU6dTUXRc8LjjaPwgsTeQPa8nRZu7WsoVY%3D&reserved=0 > <https://www.ietf.org/about/groups/iesg/statements/handling-ballot-positions/> > for more information about how to handle DISCUSS and COMMENT positions. > > > The document, along with other ballot positions, can be found here: > > https://eur02.safelinks.protection.outlook.com/?url=https%3A%2F%2Fdatatracker.ietf.org%2Fdoc%2Fdraft-ietf-cose-cbor-encoded-cert%2F&data=05%7C02%7Cgoran.selander%40ericsson.com%7Ca72dc4fef81c4183b82808dea43f8a2e%7C92e84cebfbfd47abbe52080c6b87953f%7C0%7C0%7C639128789973223624%7CUnknown%7CTWFpbGZsb3d8eyJFbXB0eU1hcGkiOnRydWUsIlYiOiIwLjAuMDAwMCIsIlAiOiJXaW4zMiIsIkFOIjoiTWFpbCIsIldUIjoyfQ%3D%3D%7C0%7C%7C%7C&sdata=XdfLe14%2BKmIudSDn%2F0k3dEV3D1ASkr79AK4WQaqF9NU%3D&reserved=0 > <https://datatracker.ietf.org/doc/draft-ietf-cose-cbor-encoded-cert/> > > > > ---------------------------------------------------------------------- > COMMENT: > ---------------------------------------------------------------------- > > Thanks to the authors and the WG for their work on this document. Please > find > below some comments and some clarifications sought to help improve the > document. > > 1) In some of the IANA sections, e.g., section 8.6, there is > a "Comments" field > and those actually reference normative specifications. Not being someone > familiar with this area, I am unable to determine if "Comments" mean > "Specifications" or something else. In any case, does "comments" seem the > right > title for the column if it has mainly normative specifications? > > [GS: The "Comments" field is common for this type of IANA registrations. > We use it for additional information, in most cases but not always as > reference to a specification or a section in this document. Note that this > is in many cases redundant since OIDs are known by their identifiers, so > essentially it provides just convenience for the reader. Given that the > "Comments" field is expected to be present we think this is good use of the > field, but happy to change to some other convention.] > > 2) There is some text under IANA considerations in section 8.15.1 that > seem not > related to or suitable for that section and instead should be perhaps > elsewhere > in the document. Please cross-check. > > [GS: We got the same comment from Roman, and removed the subsection since > the content is outdated. See PR > <https://github.com/cose-wg/CBOR-certificates/pull/384>#384 > <https://github.com/cose-wg/CBOR-certificates/pull/384> ] > > 3) Issues with references? > - RFC2247 and GSMA-SGP.22 are listed as informative reference, but are not > referenced anywhere. > > [GS: RFC2247 is removed in PR > <https://github.com/cose-wg/CBOR-certificates/pull/384>#384 > <https://github.com/cose-wg/CBOR-certificates/pull/384>, but GSMA-SGP.22 > is referenced from the table in section 8.9.] > > - RFC6962 and RFC8398 referenced normatively has been > obsoleted by RFC9162 and RFC9598 respectively. > > [GS: These references are not used anymore and thus removed, see Editor's > copy.] > > - RFC1274 referenced informatively has been obsoleted by RFC4524. > > [GS: Done in PR <https://github.com/cose-wg/CBOR-certificates/pull/384> > #384 <https://github.com/cose-wg/CBOR-certificates/pull/384>] > > - draft-ietf-lamps-rfc7030-csrattrs has been published as RFC9908; > [GS: Done in PR <https://github.com/cose-wg/CBOR-certificates/pull/384> > #384 <https://github.com/cose-wg/CBOR-certificates/pull/384>] > > also please cross-check that it is not normative along the lines of > RFC7030 > [GS: It is still informative, but included to provide better motivation, > which is missing in RFC 8295. ] > > I note that the shepherd write-up indicates 5 authors while the document > actually has 6. This is just to bring to the attention of the responsible > AD as > it exceeds the normally expected number. > > [GS: The AD is informed.] > > Thanks, > Göran > > >
_______________________________________________ COSE mailing list -- [email protected] To unsubscribe send an email to [email protected]
