[MMUSIC] RID open issue #5: max-fps

Adam Roach <adam@nostrum.com> Fri, 11 March 2016 18:25 UTC

Return-Path: <adam@nostrum.com>
X-Original-To: mmusic@ietfa.amsl.com
Delivered-To: mmusic@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 1F7F412DA0A for <mmusic@ietfa.amsl.com>; Fri, 11 Mar 2016 10:25:34 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.901
X-Spam-Level:
X-Spam-Status: No, score=-1.901 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RP_MATCHES_RCVD=-0.001] 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 7zX-RgL2TVzf for <mmusic@ietfa.amsl.com>; Fri, 11 Mar 2016 10:25:31 -0800 (PST)
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 B704012D9D9 for <mmusic@ietf.org>; Fri, 11 Mar 2016 10:25:14 -0800 (PST)
Received: from Orochi.local (99-152-145-110.lightspeed.dllstx.sbcglobal.net [99.152.145.110]) (authenticated bits=0) by nostrum.com (8.15.2/8.14.9) with ESMTPSA id u2BI6Iia098731 (version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128 verify=NO) for <mmusic@ietf.org>; Fri, 11 Mar 2016 12:06:18 -0600 (CST) (envelope-from adam@nostrum.com)
X-Authentication-Warning: raven.nostrum.com: Host 99-152-145-110.lightspeed.dllstx.sbcglobal.net [99.152.145.110] claimed to be Orochi.local
To: "mmusic@ietf.org" <mmusic@ietf.org>
From: Adam Roach <adam@nostrum.com>
Message-ID: <56E3091A.1030005@nostrum.com>
Date: Fri, 11 Mar 2016 12:06:18 -0600
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.10; rv:38.0) Gecko/20100101 Thunderbird/38.6.0
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"; format="flowed"
Content-Transfer-Encoding: 7bit
Archived-At: <http://mailarchive.ietf.org/arch/msg/mmusic/awFcZVRKFEnb0XZbKja5HV2Subc>
Subject: [MMUSIC] RID open issue #5: max-fps
X-BeenThere: mmusic@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: Multiparty Multimedia Session Control Working Group <mmusic.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/mmusic>, <mailto:mmusic-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/mmusic/>
List-Post: <mailto:mmusic@ietf.org>
List-Help: <mailto:mmusic-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mmusic>, <mailto:mmusic-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 11 Mar 2016 18:25:34 -0000

I'm putting up the open issues in the RID draft that haven't had dedicated threads yet for a final round of discussion.

For this one, see https://tools.ietf.org/html/draft-ietf-mmusic-rid-04#section-5

    Comment from Stephan Wenger: Would it be better to define max-fps as
    constraining the average over a second rather than the inverse of the
    smallest allowed interval between frames?

    PROPOSAL: Keep as currently defined.  The difference is subtle.  The
    only kinds of cases allowed by an average that aren't allowed by a
    minimum interframe interval are those such as sending no packets for
    most of a second, followed by a burst of 30 frames 1 ms apart, as
    part of a stream constrained to 30 fps.  Such cases seem undesirable.


If you disagree with the proposal, please send email in the next few days with an alternate proposal.

Thanks!

/a