[rmcat] Adam Roach's No Objection on draft-ietf-rmcat-sbd-11: (with COMMENT)

Adam Roach <adam@nostrum.com> Thu, 05 April 2018 06:28 UTC

MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 8bit
From: Adam Roach <adam@nostrum.com>
To: The IESG <iesg@ietf.org>
Cc: draft-ietf-rmcat-sbd@ietf.org, Anna Brunstrom <anna.brunstrom@kau.se>, rmcat-chairs@ietf.org, anna.brunstrom@kau.se, rmcat@ietf.org
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <152290968414.26031.16395339801847446844.idtracker@ietfa.amsl.com>
Date: Wed, 04 Apr 2018 23:28:04 -0700
Archived-At: <https://mailarchive.ietf.org/arch/msg/rmcat/8XivvvIfGsuIqmQy3OBFj_BnHoM>
Subject: [rmcat] Adam Roach's No Objection on draft-ietf-rmcat-sbd-11: (with COMMENT)

Adam Roach has entered the following ballot position for
draft-ietf-rmcat-sbd-11: 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/iesg/statement/discuss-criteria.html
for more information about IESG DISCUSS and COMMENT positions.


The document, along with other ballot positions, can be found here:
https://datatracker.ietf.org/doc/draft-ietf-rmcat-sbd/



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

Thanks for everyone's work on this document, and especially to those who ran the
preliminary experiments. This sounds like an interesting technique. I have two
minor comments.

---------------------------------------------------------------------------

§2:

>  The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
>  "SHOULD", "SHOULD NOT", "RECOMMENDED", "NOT RECOMMENDED", "MAY", and
>  "OPTIONAL" in this document are to be interpreted as described in BCP
>  14 [RFC2119] RFC2119 [RFC2119] RFC8174 [RFC8174] when, and only when,
>  they appear in all capitals, as shown here.

This is almost, but not quite, the boilerplate defined in RFC 8174. Please
consider fixing it.

---------------------------------------------------------------------------

§2.1 says "Usually M=N", while §2.2 recommends N=50 and M=30. These statements
seem in conflict.

[rmcat] Adam Roach's No Objection on draft-ietf-r… Adam Roach