Hi Mike,

Thanks for your review. Please find responses to your comments inline below, 
with reference to 
PR#389<https://github.com/cose-wg/CBOR-certificates/pull/389>. Some of your 
comments (apart from the nits, which we handle separately) were already 
addressed, see Editor’s copy:
https://cose-wg.github.io/CBOR-certificates/draft-ietf-cose-cbor-encoded-cert.html

Thanks,
Göran


From: Mike Bishop via Datatracker <[email protected]>
Date: Tuesday, 28 April 2026 at 17:47
To: The IESG <[email protected]>
Cc: [email protected] <[email protected]>; [email protected] <[email protected]>; 
[email protected] 
<[email protected]>; [email protected] 
<[email protected]>
Subject: Mike Bishop's No Objection on draft-ietf-cose-cbor-encoded-cert-18: 
(with COMMENT)

Mike Bishop 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%7C13eb79d7f394400c221d08dea53d7c79%7C92e84cebfbfd47abbe52080c6b87953f%7C0%7C0%7C639129880672584600%7CUnknown%7CTWFpbGZsb3d8eyJFbXB0eU1hcGkiOnRydWUsIlYiOiIwLjAuMDAwMCIsIlAiOiJXaW4zMiIsIkFOIjoiTWFpbCIsIldUIjoyfQ%3D%3D%7C0%7C%7C%7C&sdata=rBQ%2BSV4UUsvHW1TDRUO5qN68PvoHL%2BMv%2B5ptIjcWw8I%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%7C13eb79d7f394400c221d08dea53d7c79%7C92e84cebfbfd47abbe52080c6b87953f%7C0%7C0%7C639129880672612101%7CUnknown%7CTWFpbGZsb3d8eyJFbXB0eU1hcGkiOnRydWUsIlYiOiIwLjAuMDAwMCIsIlAiOiJXaW4zMiIsIkFOIjoiTWFpbCIsIldUIjoyfQ%3D%3D%7C0%7C%7C%7C&sdata=8cgU6T1ODmZtYeM0SRzZGBEe%2FPYK1KJBM%2FL2Xrrg58s%3D&reserved=0<https://datatracker.ietf.org/doc/draft-ietf-cose-cbor-encoded-cert/>



----------------------------------------------------------------------
COMMENT:
----------------------------------------------------------------------

# IESG review of draft-ietf-cose-cbor-encoded-cert-18

CC @MikeBishop

## Comments

### IANA

This document seems to have unresolved IANA issues. Have next steps
been determined?

### Section 8.1, paragraph 1
```
     The expert reviewers for the registries defined in this document are
     expected to ensure that the usage solves a valid use case that could
     not be solved better in a different way, that it is not going to
     duplicate an entry that is already registered, and that the
     registered point is likely to be used in deployments.  They are
```
These things are vague enough to give me concern; not quite DISCUSS-level, but I
worry that we're inviting appeals from registrants who disagree with the
reviewer on the "best" preferred solution.

[GS: Changed in PR#389<https://github.com/cose-wg/CBOR-certificates/pull/389>, 
using text from:
https://www.ietf.org/rfc/rfc9668.html#name-expert-review-instructions. 
Hopefully this addresses your concern.]


### Section 8.6, paragraph 1

How does "If OID is present" reconcile with "OID [is] mandatory”?

[GS: Fixed in Editor's copy.]

### Section 8.6, paragraph 1

Is the goal that all elements of some existing registry are assigned
mapped values here? If so, synchronization becomes a concern, and adding a
column to that registry might be preferable. If it's independent and just linked
to that other registry by OID, this is probably the best we can do.

[GS: The purpose of this registry is to register the integers using the (int, 
SpecialText) encoding of RDNAttributes described in 3.1.4. There is no existing 
registry for this purpose, the intent is that this registry should enable the 
synchronization of such encodings.]


### Too many authors

The document has six authors, which exceeds the recommended author limit. Has
the sponsoring AD agreed that this is appropriate?
[GS: AD is informed.]

### Missing references

No reference entries found for these items, which were mentioned in the text:
`[bytes]`.

[GS: Fixed in Editor's copy.]

### DOWNREFs

DOWNREF `[RFC7299]` from this Proposed Standard to Informational `RFC7299`.
(For IESG discussion. It seems this DOWNREF was not mentioned in the Last Call
and also seems to not appear in the DOWNREF registry. Reference only appears to
be for a registry reference.)

[GS: Please advise if further action is needed.]

### IP addresses

Found IP blocks or addresses not inside RFC5737/RFC3849 example ranges:
`23.106.104.0`, `2.5.29.15`, `2.5.29.37`, `2.5.4.41`, `2.5.4.11`, `2.5.4.8`,
`23.109.0.0/16`, `2001:7f9:ffff:ffff:ffff:ffff:ffff:ffff`, `2.5.4.12`,
`2.5.29.30`, `2.5.4.20`, `23.111.63.255`, `2.5.29.14`, `2.5.4.43`, `2.5.29.32`,
`2.5.4.4`, `2.5.4.6`, `2.5.29.54`, `2.5.29.31`, `23.106.119.255`,
`22.82.0.0/16`, `2.5.4.15`, `2.5.29.35`, `2.5.29.46`, `1.3.101.113`,
`2.5.4.97`, `2002:8:0:ffff:ffff:ffff:ffff:ffff`, `2.5.4.17`,
`2001:bff:ffff:ffff:ffff:ffff:ffff:ffff`, `23.111.16.0`, `2.5.4.42`,
`2.5.4.65`, `1.3.101.111`, `1.3.101.110`, `2.5.29.18`, `2.5.4.3`, `2.5.4.7`,
`2.5.4.44`, `2.5.4.5`, `2.5.29.19`, `2.5.4.46`, `2.5.4.9`, `2.5.29.9`,
`2.5.29.36`, `2.5.4.54`, `23.83.112.0/20`, `1.3.101.112`, `2.5.29.17`,
`2.5.29.33`, and `2.5.4.10`.

[GS: Fixed in Editor's copy.]

## Nits

All comments below are about very minor potential issues that you may choose to
address in some way - or ignore - as you see fit. Some were flagged by
automated tools (via 
https://eur02.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Flarseggert%2Fietf-reviewtool&data=05%7C02%7Cgoran.selander%40ericsson.com%7C13eb79d7f394400c221d08dea53d7c79%7C92e84cebfbfd47abbe52080c6b87953f%7C0%7C0%7C639129880672632177%7CUnknown%7CTWFpbGZsb3d8eyJFbXB0eU1hcGkiOnRydWUsIlYiOiIwLjAuMDAwMCIsIlAiOiJXaW4zMiIsIkFOIjoiTWFpbCIsIldUIjoyfQ%3D%3D%7C0%7C%7C%7C&sdata=XynUGMEN0V3dfnVrc7O%2FRxbRnq1EoJlQusF1vs%2Fd1F0%3D&reserved=0)<https://github.com/larseggert/ietf-reviewtool>,
 so there
will likely be some false positives. There is no need to let me know what you
did with these suggestions.

—

[GS: The rest of the mail is omitted.]
_______________________________________________
COSE mailing list -- [email protected]
To unsubscribe send an email to [email protected]

Reply via email to