[lamps] Lars Eggert's No Objection on draft-ietf-lamps-documentsigning-eku-05: (with COMMENT)

Lars Eggert via Datatracker <noreply@ietf.org> Tue, 23 August 2022 15:24 UTC

Return-Path: <noreply@ietf.org>
X-Original-To: spasm@ietf.org
Delivered-To: spasm@ietfa.amsl.com
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id 9F8CDC159487; Tue, 23 Aug 2022 08:24:44 -0700 (PDT)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: Lars Eggert via Datatracker <noreply@ietf.org>
To: The IESG <iesg@ietf.org>
Cc: draft-ietf-lamps-documentsigning-eku@ietf.org, lamps-chairs@ietf.org, spasm@ietf.org, housley@vigilsec.com, housley@vigilsec.com
X-Test-IDTracker: no
X-IETF-IDTracker: 8.14.0
Auto-Submitted: auto-generated
Precedence: bulk
Reply-To: Lars Eggert <lars@eggert.org>
Message-ID: <166126828449.22257.9885284596092018113@ietfa.amsl.com>
Date: Tue, 23 Aug 2022 08:24:44 -0700
Archived-At: <https://mailarchive.ietf.org/arch/msg/spasm/hA2gqQIZPDuhhSc8FhWgXe1aLO4>
Subject: [lamps] Lars Eggert's No Objection on draft-ietf-lamps-documentsigning-eku-05: (with COMMENT)
X-BeenThere: spasm@ietf.org
X-Mailman-Version: 2.1.39
List-Id: "This is a venue for discussion of doing Some Pkix And SMime \(spasm\) work." <spasm.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/spasm>, <mailto:spasm-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/spasm/>
List-Post: <mailto:spasm@ietf.org>
List-Help: <mailto:spasm-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/spasm>, <mailto:spasm-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 23 Aug 2022 15:24:44 -0000

Lars Eggert has entered the following ballot position for
draft-ietf-lamps-documentsigning-eku-05: 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-lamps-documentsigning-eku/



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

# GEN AD review of draft-ietf-lamps-documentsigning-eku-05

CC @larseggert

Thanks to Dale Worley for the General Area Review Team (Gen-ART) review
(https://mailarchive.ietf.org/arch/msg/gen-art/1T23l8-kN8pEMqnQvh1ir3MsGVw)

## Comments

### Section 4, paragraph 1
```
     The signed contents of Internet-Drafts are primarily intended to be
```
Did you mean "documents" here instead of "Internet-Drafts"?

## 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 3
```
-    owner but by another vendor, the vender who own the KeyPurposeIds may
-                                         ^
-    not able to control use, or even do not know about the use. - If the
-                                                                -
+    owner but by another vendor, the vendor who own the KeyPurposeIds may
+                                         ^
```

#### Section 4, paragraph 5
```
-       party software proresses each restriction on "Excluded
-                         ^
+       party software processes each restriction on "Excluded
+                         ^
```

### Grammar/style

#### Section 4, paragraph 8
```
the format it is handling (e.g. text, pdf, etc). 5. Implications for a Certif
                                      ^^^
```
File types are normally capitalized.

#### Section 4, paragraph 8
```
ormat it is handling (e.g. text, pdf, etc). 5. Implications for a Certificati
                                      ^^^
```
A period is needed after the abbreviation "etc.".

## Notes

This review is in the ["IETF Comments" Markdown format][ICMF], You can use the
[`ietf-comments` tool][ICT] to automatically convert this review into
individual GitHub issues. Review generated by the [`ietf-reviewtool`][IRT].

[ICMF]: https://github.com/mnot/ietf-comments/blob/main/format.md
[ICT]: https://github.com/mnot/ietf-comments
[IRT]: https://github.com/larseggert/ietf-reviewtool