[Gen-art] Genart last call review of draft-ietf-rmcat-coupled-cc-06

Matthew Miller <linuxwolf+ietf@outer-planes.net> Mon, 11 September 2017 15:43 UTC

Return-Path: <linuxwolf+ietf@outer-planes.net>
X-Original-To: gen-art@ietf.org
Delivered-To: gen-art@ietfa.amsl.com
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id 9B6901326FE; Mon, 11 Sep 2017 08:43:24 -0700 (PDT)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: Matthew Miller <linuxwolf+ietf@outer-planes.net>
To: gen-art@ietf.org
Cc: rmcat@ietf.org, ietf@ietf.org, draft-ietf-rmcat-coupled-cc.all@ietf.org
X-Test-IDTracker: no
X-IETF-IDTracker: 6.60.0
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <150514460458.9791.14186175950174051912@ietfa.amsl.com>
Date: Mon, 11 Sep 2017 08:43:24 -0700
Archived-At: <https://mailarchive.ietf.org/arch/msg/gen-art/ST_t9CPxPvFbsefpgdsmemXD1k8>
Subject: [Gen-art] Genart last call review of draft-ietf-rmcat-coupled-cc-06
X-BeenThere: gen-art@ietf.org
X-Mailman-Version: 2.1.22
List-Id: "GEN-ART: General Area Review Team" <gen-art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/gen-art>, <mailto:gen-art-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/gen-art/>
List-Post: <mailto:gen-art@ietf.org>
List-Help: <mailto:gen-art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/gen-art>, <mailto:gen-art-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 11 Sep 2017 15:43:25 -0000

Reviewer: Matthew Miller
Review result: Ready with Nits

I am the assigned Gen-ART reviewer for this draft. The General Area
Review Team (Gen-ART) reviews all IETF documents being processed
by the IESG for the IETF Chair.  Please treat these comments just
like any other last call comments.

For more information, please see the FAQ at

<https://trac.ietf.org/trac/gen/wiki/GenArtfaq>.

Document: draft-ietf-rmcat-coupled-cc-06
Reviewer: Matthew A. Miller
Review Date:  2017-09-11
IETF LC End Date: 2017-08-28
IESG Telechat date: 2017-09-14

Summary:

This document is ready to be published as Experimental; I have some nits
below that addressing them would help with the readability.

Major issues:  NONE

Minor issues:  NONE

Nits/editorial comments:

* In Section 2. "Definitions", the second sentence detailing the term
"Flow" is awkward.  I think "or" can be added between "connection," and
"an RTP stream" to correct it?

  """
  It could, for example, be a transport layer connection, or an RTP
  stream [RFC7656], whether or not this RTP stream is multiplexed
  onto an RTP session with other RTP streams.
  """

* In Section 4. "Architectural overview", the last paragraph has an
awkwardly-phrased sentence.  I suggest the following sentence be changed from:
  """
  It does, for instance, not define how many bits must be used to represent
  FSIs, or in which way the entities communicate.
  """

  to the following:
  """
  It does not, for instance, define how many bits must be used to represent
  FSIs, or in which way the entities communicate.
  """