Re: [avtext] framemarking: add frame size info

Jonathan Lennox <jonathan@vidyo.com> Fri, 26 August 2016 17:07 UTC

Return-Path: <prvs=2046469317=jonathan@vidyo.com>
X-Original-To: avtext@ietfa.amsl.com
Delivered-To: avtext@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 4AF6912D195 for <avtext@ietfa.amsl.com>; Fri, 26 Aug 2016 10:07:57 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.83
X-Spam-Level:
X-Spam-Status: No, score=-1.83 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-0.7, RCVD_IN_SORBS_WEB=0.77, SPF_PASS=-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 2HvLu4Ixdkjo for <avtext@ietfa.amsl.com>; Fri, 26 Aug 2016 10:07:55 -0700 (PDT)
Received: from mx0b-00198e01.pphosted.com (mx0b-00198e01.pphosted.com [67.231.157.197]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 8DA4F12D0C2 for <avtext@ietf.org>; Fri, 26 Aug 2016 10:07:55 -0700 (PDT)
Received: from pps.filterd (m0073110.ppops.net [127.0.0.1]) by mx0b-00198e01.pphosted.com (8.16.0.17/8.16.0.17) with SMTP id u7QH4BcG025404; Fri, 26 Aug 2016 13:07:54 -0400
Received: from mail.vidyo.com ([162.209.16.214]) by mx0b-00198e01.pphosted.com with ESMTP id 24xhy2w4dn-1 (version=TLSv1 cipher=AES128-SHA bits=128 verify=NOT); Fri, 26 Aug 2016 13:07:54 -0400
Received: from 492132-EXCH1.vidyo.com ([fe80::50:56ff:fe85:4f77]) by 492133-EXCH2.vidyo.com ([fe80::50:56ff:fe85:6b62%13]) with mapi id 14.03.0195.001; Fri, 26 Aug 2016 12:07:53 -0500
From: Jonathan Lennox <jonathan@vidyo.com>
To: "Paul E. Jones" <paulej@packetizer.com>
Thread-Topic: [avtext] framemarking: add frame size info
Thread-Index: AQHR/7tWhDk2VlpZFkqFowW+3dwBpKBbzR0A
Date: Fri, 26 Aug 2016 17:07:53 +0000
Message-ID: <B4BD5FDA-FB39-4714-92A3-EE647A8D06D9@vidyo.com>
References: <CAEn+E3h-b=8VEkhZ56Z9Ww+mTCA2H1B93UAkgbfmySyi2CnvnA@mail.gmail.com> <em8de2860d-9b70-44ce-87e5-3c6ecb1fb1ee@sydney>
In-Reply-To: <em8de2860d-9b70-44ce-87e5-3c6ecb1fb1ee@sydney>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [160.79.219.114]
Content-Type: multipart/alternative; boundary="_000_B4BD5FDAFB39471492A3EE647A8D06D9vidyocom_"
MIME-Version: 1.0
X-Proofpoint-Virus-Version: vendor=fsecure engine=2.50.10432:, , definitions=2016-08-26_12:, , signatures=0
X-Proofpoint-Spam-Details: rule=outbound_notspam policy=outbound score=0 spamscore=0 suspectscore=0 malwarescore=0 phishscore=0 adultscore=0 bulkscore=0 classifier=spam adjust=0 reason=mlx scancount=1 engine=8.0.1-1604210000 definitions=main-1608260224
Archived-At: <https://mailarchive.ietf.org/arch/msg/avtext/XIXJZ6JmWohZ4D8ewaq2Eyua__U>
Cc: "avtext@ietf.org" <avtext@ietf.org>
Subject: Re: [avtext] framemarking: add frame size info
X-BeenThere: avtext@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: Audio/Video Transport Extensions working group discussion list <avtext.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/avtext>, <mailto:avtext-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/avtext/>
List-Post: <mailto:avtext@ietf.org>
List-Help: <mailto:avtext-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/avtext>, <mailto:avtext-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 26 Aug 2016 17:07:57 -0000

(As an individual.)

In the latest version of simulcast the media distributor would need the RID values, not the PT values, but the idea is the same — it needs the SDP.

Note that if the media distributor doesn’t have information from the SDP it can’t reliably identify the frame marking header extension at all, since header extension IDs are negotiated. So I’m not sure how much benefit there is to putting the size in the header extension.

That said, if we envision a scenario where encoders might be frequently changing their video size (in response to available network bandwidth, or the like), it might be useful for encoders to be able to indicate the current size they’re encoding without needing to send updated SDP all the time.

On Aug 26, 2016, at 12:52 PM, Paul E. Jones <paulej@packetizer.com<mailto:paulej@packetizer.com>> wrote:

Miguel,

You make the assumption that the media distributor will not see the SDP, I suppose.  While certainly a valid model, I'll admit that I had personally assumed any media forwarding function would see the SDP (or at least be told the PT values and any relevant flow information similar to what RFC 6236 provides) and would thus know which PT values correspond to what video resolutions if simulcast is employed.

Paul

------ Original Message ------
From: "Miguel París Díaz" <mparisdiaz@gmail.com<mailto:mparisdiaz@gmail.com>>
To: avtext@ietf.org<mailto:avtext@ietf.org>
Sent: 8/25/2016 10:12:48 AM
Subject: [avtext] framemarking: add frame size info

Hello,
it would be great having frame size (width and height) info in the Frame Marking RTP header extension [1].

Why?
For example, in the case of using simulcast in an SFU, selecting the stream by the size would ease the application development and improve the experience of the users.
Application developers don't usually have deep knowledge about media like bitrate, etc., but they know which video size has to be rendered in the GUI, which may depend on the client where the app is running: a mobile, a PC with a 13"· screen, a PC with 27" screen, etc.

In this way and taking a videoconference app as example, if a participant select another participant to be rendered as main video, the app could ask the SFU to select the video quality that better matches to 800x600 size.

What do you think about this idea?

Thanks and best regards!!

Refs
[1] https://tools.ietf.org/html/draft-ietf-avtext-framemarking-02

--
Miguel París Díaz
------------------------------------------------------------------------
Computer/Software engineer.
Researcher and architect in http://www.kurento.org<http://www.kurento.org/>
http://twitter.com/mparisdiaz
------------------------------------------------------------------------
_______________________________________________
avtext mailing list
avtext@ietf.org<mailto:avtext@ietf.org>
https://www.ietf.org/mailman/listinfo/avtext