IETF Logo Mail Archive

Re: [video-codec] draft-filippov-netvc-requirements-01

Thomas Daede <tdaede@mozilla.com> Tue, 21 July 2015 16:12 UTC

Return-Path: <tdaede@mozilla.com>
X-Original-To: video-codec@ietfa.amsl.com
Delivered-To: video-codec@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id B8F0C1A8BBE for <video-codec@ietfa.amsl.com>; Tue, 21 Jul 2015 09:12:17 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.601
X-Spam-Level:
X-Spam-Status: No, score=-2.601 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001] 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 orHQkIvIoBag for <video-codec@ietfa.amsl.com>; Tue, 21 Jul 2015 09:12:15 -0700 (PDT)
Received: from mail-wi0-f169.google.com (mail-wi0-f169.google.com [209.85.212.169]) (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 2F7951A8BBF for <video-codec@ietf.org>; Tue, 21 Jul 2015 09:12:15 -0700 (PDT)
Received: by wibud3 with SMTP id ud3so132588697wib.0 for <video-codec@ietf.org>; Tue, 21 Jul 2015 09:12:13 -0700 (PDT)
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:subject:to:references:from:message-id:date :user-agent:mime-version:in-reply-to:content-type :content-transfer-encoding; bh=DEWZcRpFuWgTpnVzNTmcDr0q5M/C3D/6xks/fLWr9K0=; b=SUmiEdi93mC8Vib5cQGmWGTa6TcSI1L4CoSDGoz7gh0GF09y15lKqyiDcsgG6l4UfY 5geT1p93fWTcGMhU96e3ikgzrYOaeQY5Dj+YVpw8BQFbrmzx8WZciruplOnhpvVPIbev UTolrRtWDgpgelCP99itvxsuzI4F50Es/8c3RYwP+/k873okkJybKjSiQApXxx6uAV/8 /Ehubs3Bgid8GvnGQI6ieTohqiCHqPKs0XGx8MPO/B904ALPOTDAHKqyabG1zjg+ajOM R+Kn6wAVFCg+TPYiVwT9o9BNlXVvzznUbUfzVwnpEo1GEqitAh8/B1TUzxrKPiU2yp+i yFhw==
X-Gm-Message-State: ALoCoQmvtSE6298rITy+JOfY/rAxD1mrMi3jIMPBmNXHVUEAwDCk989EP2+BiufyhFCRzBJACWy8
X-Received: by 10.194.93.198 with SMTP id cw6mr71129476wjb.113.1437495133805; Tue, 21 Jul 2015 09:12:13 -0700 (PDT)
Received: from ?IPv6:2001:67c:370:168:7e7a:91ff:fe9e:8126? ([2001:67c:370:168:7e7a:91ff:fe9e:8126]) by smtp.gmail.com with ESMTPSA id qq1sm37762538wjc.0.2015.07.21.09.12.12 (version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Tue, 21 Jul 2015 09:12:12 -0700 (PDT)
To: "Ali C. Begen (abegen)" <abegen@cisco.com>, "video-codec@ietf.org" <video-codec@ietf.org>
References: <32AA73C5-0D17-4ECE-A02D-041C5147D9E5@cisco.com> <55AE60D0.3040201@mozilla.com> <29BD22C6-8790-451B-B754-ED55D2F41C90@cisco.com>
From: Thomas Daede <tdaede@mozilla.com>
Message-ID: <55AE6F5C.8000805@mozilla.com>
Date: Tue, 21 Jul 2015 18:12:12 +0200
User-Agent: http://a.pomf.se/cszdno.opus
MIME-Version: 1.0
In-Reply-To: <29BD22C6-8790-451B-B754-ED55D2F41C90@cisco.com>
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
Archived-At: <http://mailarchive.ietf.org/arch/msg/video-codec/DdVOSqbEbJx0UcxvyvmmxAAJ6Vk>
Subject: Re: [video-codec] draft-filippov-netvc-requirements-01
X-BeenThere: video-codec@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: Video codec BoF discussion list <video-codec.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/video-codec>, <mailto:video-codec-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/video-codec/>
List-Post: <mailto:video-codec@ietf.org>
List-Help: <mailto:video-codec-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/video-codec>, <mailto:video-codec-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 21 Jul 2015 16:12:17 -0000

>> - All of the use cases should specify either a high latency or low
>> latency requirement.
> 
> And where is the borderline?

What is a borderline use case? I would much rather keep the number of
configurations as low as possible.

> I still argue iptv should be removed entirely.

I would be fine with this. If it stays, it needs a much clearer use case
definition.

Thomas

v2.23.0 | Report a Bug | By Email