[payload] Questions on draft-ietf-payload-vp8-16
"Ben Campbell" <ben@nostrum.com> Mon, 29 June 2015 21:51 UTC
Return-Path: <ben@nostrum.com>
X-Original-To: payload@ietfa.amsl.com
Delivered-To: payload@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 08FEF1B355B; Mon, 29 Jun 2015 14:51:05 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.91
X-Spam-Level:
X-Spam-Status: No, score=-1.91 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, T_RP_MATCHES_RCVD=-0.01] autolearn=ham
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 IpNsv0vAF_4B; Mon, 29 Jun 2015 14:51:03 -0700 (PDT)
Received: from nostrum.com (raven-v6.nostrum.com [IPv6:2001:470:d:1130::1]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 72C341A905C; Mon, 29 Jun 2015 14:51:00 -0700 (PDT)
Received: from [10.0.1.23] (cpe-70-119-203-4.tx.res.rr.com [70.119.203.4]) (authenticated bits=0) by nostrum.com (8.15.1/8.14.9) with ESMTPSA id t5TLojQo092202 (version=TLSv1 cipher=DHE-RSA-AES128-SHA bits=128 verify=NO); Mon, 29 Jun 2015 16:50:56 -0500 (CDT) (envelope-from ben@nostrum.com)
X-Authentication-Warning: raven.nostrum.com: Host cpe-70-119-203-4.tx.res.rr.com [70.119.203.4] claimed to be [10.0.1.23]
From: Ben Campbell <ben@nostrum.com>
To: draft-ietf-payload-vp8.all@ietf.org, payload-chairs@ietf.org, payload@ietf.org
Date: Mon, 29 Jun 2015 16:50:45 -0500
Message-ID: <8163A1DE-531A-4CDA-AA6F-61ADCDAE784B@nostrum.com>
MIME-Version: 1.0
Content-Type: text/plain; format="flowed"
X-Mailer: MailMate (1.9.1r5084)
Archived-At: <http://mailarchive.ietf.org/arch/msg/payload/ar5CTlIZs2Tyecld0cm2YeQG318>
Subject: [payload] Questions on draft-ietf-payload-vp8-16
X-BeenThere: payload@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: Audio/Video Transport Payloads working group discussion list <payload.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/payload>, <mailto:payload-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/payload/>
List-Post: <mailto:payload@ietf.org>
List-Help: <mailto:payload-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/payload>, <mailto:payload-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 29 Jun 2015 21:51:05 -0000
Hi, I'm doing a quick re-look at draft-ietf-payload-vp8-16 before starting a repeat IETF Last Call. I have a few comments. I don't think any of these need delay the last call, so please address them along with any last call comments. Please bear in mind that I am reconstructing a lot of history here, so I apologize in advance if I bring up things that have already been discussed. Thanks! Ben. ------------ General: Ted Lemon and Pete Resnick made some AD comments when they were still ADs. Even though they are no longer on the IESG, their comments look reasonable. I don't see evidence that they have been addressed--please consider addressing them. It looks like you have addressed some, but not all, of Stephen Farrell's comments. Has there been discussion on why the ones not addressed were not addressed? (Note that in both of the paragraphs above, I don't mean by "addressed" that the draft necessarily needs to change--just that the authors respond to the input--even if only to say why they don't agree with a comment.) -- 4.5 and 4.5.1: It would be helpful to explain why these are listed as examples. I assume it's one of those cases where this algorithm gives the right results, but others could also do so. If so, some words to that effect would be helpful. It might also be helpful to include a few words indicating why 4.5.1 is a child of 4.5 rather than a peer. (I assume because partition reconstruction is a subset of frame reconstruction?) -- 7: I don't see a response to the secdir review ( Secdir review of draft-ietf-payload-vp8-08 ). For the SRTP question, please consider using the boilerplate in the appendix of draft-ietf-payload-rtp-howto-14 (section A.13).
- [payload] Questions on draft-ietf-payload-vp8-16 Ben Campbell
- Re: [payload] Questions on draft-ietf-payload-vp8… Harald Alvestrand