[rmcat] AD review and IETF last call of draft-ietf-rmcat-video-traffic-model

Mirja Kühlewind <mirja.kuehlewind@tik.ee.ethz.ch> Mon, 14 January 2019 17:20 UTC

Return-Path: <mirja.kuehlewind@tik.ee.ethz.ch>
X-Original-To: rmcat@ietfa.amsl.com
Delivered-To: rmcat@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id E6D101311BB; Mon, 14 Jan 2019 09:20:12 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.2
X-Spam-Level:
X-Spam-Status: No, score=-4.2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id vGOxxOdl71Kb; Mon, 14 Jan 2019 09:20:11 -0800 (PST)
Received: from virgo01.ee.ethz.ch (virgo01.ee.ethz.ch [129.132.2.226]) (using TLSv1.2 with cipher ADH-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id F1C301311CA; Mon, 14 Jan 2019 09:20:07 -0800 (PST)
Received: from localhost (localhost [127.0.0.1]) by virgo01.ee.ethz.ch (Postfix) with ESMTP id 43dgFy1qrbzMlxt; Mon, 14 Jan 2019 18:20:06 +0100 (CET)
X-Virus-Scanned: Debian amavisd-new at virgo01.ee.ethz.ch
Received: from virgo01.ee.ethz.ch ([127.0.0.1]) by localhost (virgo01.ee.ethz.ch [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id PcmwA7w_jEmJ; Mon, 14 Jan 2019 18:20:04 +0100 (CET)
X-MtScore: NO score=0
Received: from [192.168.178.24] (i577BCE3A.versanet.de [87.123.206.58]) by virgo01.ee.ethz.ch (Postfix) with ESMTPSA; Mon, 14 Jan 2019 18:20:04 +0100 (CET)
From: Mirja Kühlewind <mirja.kuehlewind@tik.ee.ethz.ch>
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: quoted-printable
Mime-Version: 1.0 (Mac OS X Mail 11.5 \(3445.9.1\))
Message-Id: <EC0E786D-3F44-485D-8603-ED70CF0D9CFF@tik.ee.ethz.ch>
Date: Mon, 14 Jan 2019 18:20:03 +0100
Cc: rmcat@ietf.org
To: draft-ietf-rmcat-video-traffic-model.all@ietf.org
X-Mailer: Apple Mail (2.3445.9.1)
Archived-At: <https://mailarchive.ietf.org/arch/msg/rmcat/-1S4xwk_APP_q049jJl96wgRnwc>
Subject: [rmcat] AD review and IETF last call of draft-ietf-rmcat-video-traffic-model
X-BeenThere: rmcat@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: "RTP Media Congestion Avoidance Techniques \(RMCAT\) Working Group discussion list." <rmcat.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/rmcat>, <mailto:rmcat-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/rmcat/>
List-Post: <mailto:rmcat@ietf.org>
List-Help: <mailto:rmcat-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/rmcat>, <mailto:rmcat-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 14 Jan 2019 17:20:13 -0000

Hi authors,

thanks for the well-written document! I’ve reviewed the draft with no substantial comments and as such went ahead and already requested IETF last call.

There is one minor editorial thing to keep in mind for the next update: the header line on each page currently contains the whole title of the document which is quite long and therefore cropped. As such the header looks like this:

Internet-DraftVideo Traffic Models for RTP Congestion ContrNovember 2018

In the xml there is an option to specify a short title. I would recommend you to add that for the next revision with a short title such as "Video Traffic Models for RTP“ that then is respectively used on build in the header line.

And one minor question on the technical content: Is there a possibility to give a useful reference to Laplacian distributions. The answer might be no as I would also myself rather point people to wikipedia, however, I was wondering about that.

And one last comment on a process-related point: the implementation status sections as proposed in rfc7942 are usually meant to be removed on publication (as they will usually outdate quickly). I guess in this case it, however, could make sense to keep it. What’s your intention here? Maybe it would be good to also note something in the shepherd write-up and I can add an RFC editor note on publication if needed.

Thanks!
Mirja