[openpgp] Mike Bishop's No Objection on draft-ietf-openpgp-pqc-15: (with COMMENT)

[Mike Bishop via Datatracker <[e-mail]>]

Mike Bishop has entered the following ballot position for
draft-ietf-openpgp-pqc-15: 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-openpgp-pqc/



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

# IESG review of draft-ietf-openpgp-pqc-14

CC @MikeBishop

## Comments

### Section 3.1, paragraph 2
```
     encrypting to different keys if at least one key does not support
     PQ(/T) encryption schemes.
```
"if any key does not support" or "unless all keys support" might be easier to
parse.

### Section 8.1, paragraph 1
```
     multiple PKESKs if at least one does not use PQ(/T) encryption
     schemes.
```
Similarly, "if any of them do not use" or "unless all of them use" might be easier to parse.

## 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://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.

### Typos

#### Section 1, paragraph 1
```
-    extend OpenPGP by algorithms that remain secure in the presence of a
-                   ^^
+    extend OpenPGP with algorithms that remain secure in the presence of a
+                   ^^^^
```

#### Section 1, paragraph 2
```
-    Technology (NIST) in mid 2022 [NISTIR-8413] as the result of the NIST
-                            ^
+    Technology (NIST) in mid-2022 [NISTIR-8413] as the result of the NIST
+                            ^
```

#### Section 1, paragraph 3
```
-    two components appears as single data structure or algorithm from the
+    two components appears as a single data structure or algorithm from the
+                             ++
```

#### Section 1.2.3, paragraph 2
```
-    taken into account.  We refer to Section 10.1 for a discussion of the
-                         ^^^^
+    taken into account.  Refer to Section 10.1 for a discussion of the
+                         ^
```

#### Section 1.3, paragraph 1
```
-    The ECDH encryption is defined here as a KEM via X25519 and X448
-   ----
```

#### Section 1.4.1, paragraph 3
```
-    the consuming party has to successfully perform the cryptographic
-                       -------
```

#### Section 1.4.1, paragraph 3
```
-    message, in order for the message to be deciphered and considered as
-           ----------
```

#### Section 8.2, paragraph 1
```
-    The OpenPGP specification [RFC9580] allows to sign a message with
-                                               ---
+    The OpenPGP specification [RFC9580] allows signing a message with
+                                                   +++
```

#### Section 8.3, paragraph 1
```
-    When verifying, an implementation MAY be willing to accept signatures
+    When verifying, an implementation MAY be willing to accept signatures both from
+                                                                         ++++++++++
```

### Grammar/style

#### Section 6.1.1, paragraph 1
```
not be supported by all clients. Therefore various migration considerations
                                 ^^^^^^^^^
```
A comma may be missing after the conjunctive/linking adverb "Therefore".

#### Section 7.1, paragraph 2
```
any OpenPGP signature, the hashed meta data includes the signature algorithm
                                  ^^^^^^^^^
```
Did you mean "metadata"?

#### Section 8.1, paragraph 0
```
 attacks, this specification recommends to avoid key-reuse across protocols i
                             ^^^^^^^^^^^^^^^^^^^
```
The verb "recommends" is used with the gerund form. Consider "recommends avoiding".

#### Section 8.3, paragraph 1
```
t no word is the suffix of another. Thus this property ensures unambiguous pa
                                    ^^^^
```
A comma may be missing after the conjunctive/linking adverb "Thus".

#### Section 12.11, paragraph 2
```
pendix A. Test Vectors To help implementing this specification a set of non-n
                               ^^^^^^^^^^^^
```
Consider "help with implementing".