[lamps] Lars Eggert's No Objection on draft-ietf-lamps-rfc3709bis-08: (with COMMENT)

[Lars Eggert via Datatracker <[e-mail]>]

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



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

# GEN AD review of draft-ietf-lamps-rfc3709bis-08

CC @larseggert

Thanks to Paul Kyzivat for the General Area Review Team (Gen-ART) review
(https://mailarchive.ietf.org/arch/msg/gen-art/IiFgJfnLGPzwxj92raQWE4oI108)

## Comments

### Section 4.1, paragraph 8
```
     Note that the HTTPS scheme (https://...) requires the validation of
     other certificates to establish a secure connection.  For this
     reason, the HTTP scheme (http://...) may be easier for a client to
     handle.  Also, the hash of the logotype data provides data integrity.
```
It may be easier, but it's also insecure. I find it odd that we don't
recommend HTTPS over HTTP here?

### Inclusive language

Found terminology that should be reviewed for inclusivity; see
https://www.rfc-editor.org/part2/#inclusive_language for background and more
guidance:

 * Term `his`; alternatives might be `they`, `them`, `their`
 * Term `traditional`; alternatives might be `classic`, `classical`, `common`,
   `conventional`, `customary`, `fixed`, `habitual`, `historic`,
   `long-established`, `popular`, `prescribed`, `regular`, `rooted`,
   `time-honored`, `universal`, `widely used`, `widespread`

## 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 3, paragraph 6
```
-    applications where the audio text is placed as the "alt" atttribute
-                                                                -
```

#### Section 3, paragraph 6
```
-    value of an html image (img) element and the language value obtained
-                ^^^^
+    value of an HTML image (img) element and the language value obtained
+                ^^^^
```

#### Section 7, paragraph 16
```
-    When a bitmapped image is used, the PNG [ISO15948] format SHOULD be
-                 ---
```

### URLs

These URLs in the document can probably be converted to HTTPS:

 * http://www.w3.org/TR/2008/PR-SVGTiny12-20081117

### Grammar/style

#### Section 1, paragraph 3
```
tificate may be examined from several different perspectives. Systematic pro
                              ^^^^^^^^^^^^^^^^^
```
Consider using "several".

#### Section 1, paragraph 9
```
a user identifies the owner of the web site. * Peer e-mail exchange in busin
                                   ^^^^^^^^
```
Nowadays, it's more common to write this as one word.

#### Section 1.1, paragraph 4
```
ate is too technical and is not user friendly. It contains no graphic symbol
                                ^^^^^^^^^^^^^
```
This word is normally spelled with a hyphen.

#### Section 1.3, paragraph 3
```
the end, the human will decide whether or not to accept an executable email a
                               ^^^^^^^^^^^^^^
```
Consider shortening this phrase to just "whether". It is correct though if you
mean "regardless of whether".

#### Section 6, paragraph 7
```
references to information stored outside of the SVG image of type B, C, or D
                                 ^^^^^^^^^^
```
This phrase is redundant. Consider using "outside".

#### Section 7, paragraph 2
```
FC1952] as specified in [SVGR]. When a uncompressed SVG image is fetched wit
                                     ^
```
Use "an" instead of "a" if the following word starts with a vowel sound, e.g.
"an article", "an hour".

#### Section 7, paragraph 3
```
 characters as specified above. When a SVG image is embedded in the certific
                                     ^
```
Use "an" instead of "a" if the following word starts with a vowel sound, e.g.
"an article", "an hour".

## 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