[AVTCORE] Spencer Dawkins' Yes on draft-ietf-avtcore-rtp-multi-stream-10: (with COMMENT)

"Spencer Dawkins" <spencerdawkins.ietf@gmail.com> Thu, 03 December 2015 03:41 UTC

Return-Path: <spencerdawkins.ietf@gmail.com>
X-Original-To: avt@ietf.org
Delivered-To: avt@ietfa.amsl.com
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id 849761ACEB8; Wed, 2 Dec 2015 19:41:00 -0800 (PST)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: Spencer Dawkins <spencerdawkins.ietf@gmail.com>
To: The IESG <iesg@ietf.org>
X-Test-IDTracker: no
X-IETF-IDTracker: 6.11.0
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <20151203034100.19390.99194.idtracker@ietfa.amsl.com>
Date: Wed, 02 Dec 2015 19:41:00 -0800
Archived-At: <http://mailarchive.ietf.org/arch/msg/avt/vk4Fv_iry-1wCPI0gSWgrLnk4pk>
Cc: avtcore-chairs@ietf.org, draft-ietf-avtcore-rtp-multi-stream@ietf.org, avt@ietf.org
Subject: [AVTCORE] Spencer Dawkins' Yes on draft-ietf-avtcore-rtp-multi-stream-10: (with COMMENT)
X-BeenThere: avt@ietf.org
X-Mailman-Version: 2.1.15
List-Id: Audio/Video Transport Core Maintenance <avt.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/avt>, <mailto:avt-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/avt/>
List-Post: <mailto:avt@ietf.org>
List-Help: <mailto:avt-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/avt>, <mailto:avt-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 03 Dec 2015 03:41:00 -0000

Spencer Dawkins has entered the following ballot position for
draft-ietf-avtcore-rtp-multi-stream-10: Yes

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-avtcore-rtp-multi-stream/



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

Thank you for doing this work.

I have a small number of comments you might consider.

In this text:

      Note: The above is chosen to match the TCP initial window of 4
      packets, not the larger TCP initial windows for which there is an
      ongoing experiment.  The reason for this is a desire to be
      conservative, since an RTP endpoint will also in many cases start
      sending RTP data packets at the same time as these initial RTCP
      packets are sent.
      
Not to be pedantic, but it would be more correct to say "TCP maximum
initial window of 4 packets". RFC 3390 describes this in TCP-speak as 

   Equivalently, the upper bound for the initial window size is based on
   the MSS, as follows:

       If (MSS <= 1095 bytes)
           then win <= 4 * MSS;
       If (1095 bytes < MSS < 2190 bytes)
           then win <= 4380;
       If (2190 bytes <= MSS)
           then win <= 2 * MSS;

If you end up making changes to this text, providing RFC 3390 as the
reference for 4 and RFC 6928 for the experiment would make the reader's
job easier.

In this text:

   The above algorithm has been shown in simulations to maintain the
   inter-RTCP packet transmission time distribution for each SSRC, and
   to consume the same amount of bandwidth as non-aggregated RTCP
   packets.  
   
is there a reference you could provide for the simulations?

In this text:

   The finality of sending RTCP BYE, means that endpoints needs to
   consider if the ceasing of transmission of an RTP stream is temporary
   or more permanent. 

I don't understand the subtlety of "more permanent" - is this
"permanent"?