[Jmap] Lars Eggert's No Objection on draft-ietf-jmap-blob-17: (with COMMENT)

Lars Eggert via Datatracker <noreply@ietf.org> Mon, 12 December 2022 12:47 UTC

Return-Path: <noreply@ietf.org>
X-Original-To: jmap@ietf.org
Delivered-To: jmap@ietfa.amsl.com
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id 06DE6C14F740; Mon, 12 Dec 2022 04:47:49 -0800 (PST)
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-jmap-blob@ietf.org, jmap-chairs@ietf.org, jmap@ietf.org, fenton@bluepopcorn.net, fenton@bluepopcorn.net
X-Test-IDTracker: no
X-IETF-IDTracker: 9.2.1
Auto-Submitted: auto-generated
Precedence: bulk
Reply-To: Lars Eggert <lars@eggert.org>
Message-ID: <167084926901.46253.17280886640924528315@ietfa.amsl.com>
Date: Mon, 12 Dec 2022 04:47:49 -0800
Archived-At: <https://mailarchive.ietf.org/arch/msg/jmap/fkJUvN1vKGb9NruTc_Jd9cF7W5k>
Subject: [Jmap] Lars Eggert's No Objection on draft-ietf-jmap-blob-17: (with COMMENT)
X-BeenThere: jmap@ietf.org
X-Mailman-Version: 2.1.39
List-Id: JSON Message Access Protocol <jmap.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/jmap>, <mailto:jmap-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/jmap/>
List-Post: <mailto:jmap@ietf.org>
List-Help: <mailto:jmap-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/jmap>, <mailto:jmap-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 12 Dec 2022 12:47:49 -0000

Lars Eggert has entered the following ballot position for
draft-ietf-jmap-blob-17: 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-jmap-blob/



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

# GEN AD review of draft-ietf-jmap-blob-17

CC @larseggert

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

## 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.1, paragraph 14
```
-       list MUST be present in the HTTP Digest Alogirthms registry
-                                                  ^ -
+       list MUST be present in the HTTP Digest Algorithms registry
+                                                 + ^
```

#### Section 4, paragraph 2
```
-    unchanged by this specfication, and is selected by the
+    unchanged by this specification, and is selected by the
+                          +
```

#### Section 4.1, paragraph 17
```
-    For each sucessful upload, servers MUST add an entry to the
+    For each successful upload, servers MUST add an entry to the
+               +
```

### Grammar/style

#### Section 4.2.2, paragraph 12
```
data given to a Blob/upload is a well formed instance of the specified media
                                 ^^^^^^^^^^^
```
This word is normally spelled with a hyphen.

#### Section 4.2.2, paragraph 12
```
e far side of security scanners (anti-virus or exfiltration scanners for exa
                                 ^^^^^^^^^^
```
This word is normally spelled as one.

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