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://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://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?

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.

3) Issues with references?
- RFC2247 and GSMA-SGP.22 are listed as informative reference, but are not
referenced anywhere. - RFC6962 and RFC8398 referenced normatively has been
obsoleted by RFC9162 and RFC9598 respectively. - RFC1274 referenced
informatively has been obsoleted by RFC4524. -
draft-ietf-lamps-rfc7030-csrattrs has been published as RFC9908; also please
cross-check that it is not normative along the lines of RFC7030

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.



_______________________________________________
COSE mailing list -- [email protected]
To unsubscribe send an email to [email protected]

Reply via email to