Re: [MMUSIC] [avtext] framemarking: add frame size info

Miguel París Díaz <mparisdiaz@gmail.com> Sun, 30 April 2017 14:51 UTC

Return-Path: <mparisdiaz@gmail.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 D2293129401; Sun, 30 Apr 2017 07:51:53 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.999
X-Spam-Level:
X-Spam-Status: No, score=-1.999 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com
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 JXzVdrutivmu; Sun, 30 Apr 2017 07:51:51 -0700 (PDT)
Received: from mail-yb0-x229.google.com (mail-yb0-x229.google.com [IPv6:2607:f8b0:4002:c09::229]) (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 115FE1293E4; Sun, 30 Apr 2017 07:49:49 -0700 (PDT)
Received: by mail-yb0-x229.google.com with SMTP id s22so24152077ybe.3; Sun, 30 Apr 2017 07:49:49 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=iFYIM0QPWAZd2pL0QGL0GcOxmVRB5MaQhVtewod4xvo=; b=C/eNOHtel/MnnK45gjIecsi0G12jB0eSxJDFxtH4xom0bNkrxsvjtdsmNcWyJSfwge mwItTrqJcM6N9WtkUOZD8fLluWidxionnvgs1bBxE0MegKNCxOL8jLgTPZlpC9avZprZ NdEDnM+haCqSRJ2PgAWdAEIj5FPHXp57QQwTGyowO8VGcjD1lYUxwb+7DTs2oGd1ktkz 1ahRvfFIr5+AsNR7xe33ZMFHBrl1Xc/abwW7ws1gV8beao9hhEg1gmOR7soIjYz5rJs9 wEC6F2wUbYPBQADhkMtXu39kUTvaU99l1dFmNw2DLbgciTRNVSIS495Y8q6pplWBKb2Y Io0A==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc; bh=iFYIM0QPWAZd2pL0QGL0GcOxmVRB5MaQhVtewod4xvo=; b=ndBSEw/oWgQfpobC4vOteIpZV7vWBJNCYCLE1ZswgYr2GBeJwWFkyrgsYhviMKII89 qFIxT9R1GRAAsMJzvU5Pq6AQ+BkuVhqshVjVGtINwP0CyPQbZyEDLP65shVkFw3XbsQg VtIZNIZcF/LfhV5bUygAdgKxxagVxBBDH4Pmf2FdJl//Z/1PhjbtPou400A4bm6x5uOY j37QMc8cyxu4EXO3+JOsQNBg3JEiKnlqHk/o+bygik3yMENTuBAHQOYy7PwoeVslujBD y03rIual5i15mafAgDpPxQBIr22jxZ6MN+l2D/iqT8yAbDSiF3MKeOHIeWeVt/gNpTFw 2glA==
X-Gm-Message-State: AN3rC/5zPoWyrbQOzvMgWSb+NBjHjKOfbxfytDO83NqVLuqvR9Uye3ow 97fSIOWMz/iiQ2Xuap2Gx5P5+d5ZDA==
X-Received: by 10.37.171.194 with SMTP id v60mr16719079ybi.100.1493563788198; Sun, 30 Apr 2017 07:49:48 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.129.46.18 with HTTP; Sun, 30 Apr 2017 07:49:47 -0700 (PDT)
In-Reply-To: <D4FEA22D.6B914%mzanaty@cisco.com>
References: <CAEn+E3h-b=8VEkhZ56Z9Ww+mTCA2H1B93UAkgbfmySyi2CnvnA@mail.gmail.com> <em8de2860d-9b70-44ce-87e5-3c6ecb1fb1ee@sydney> <B4BD5FDA-FB39-4714-92A3-EE647A8D06D9@vidyo.com> <CAEn+E3jt9gzKU748uJrxAsu6eY-c5G23_=u6SHLRAv=oD4Z-ow@mail.gmail.com> <CAEn+E3iqskKLDidPnw2Y3DGMP_x-rWD_tnuC7K3vT=EU5gb7cw@mail.gmail.com> <CAEn+E3gK4CQ3WEXJvitUePb4N4au2uEEQZDagVBfPSKjinkxXg@mail.gmail.com> <D4FEA22D.6B914%mzanaty@cisco.com>
From: =?UTF-8?Q?Miguel_Par=C3=ADs_D=C3=ADaz?= <mparisdiaz@gmail.com>
Date: Sun, 30 Apr 2017 16:49:47 +0200
Message-ID: <CAEn+E3iT1vUFyQ7Wx5tb6fR+6OMZWRGV50VFt-vwke+8m8ZfNg@mail.gmail.com>
To: "Mo Zanaty (mzanaty)" <mzanaty@cisco.com>
Cc: Jonathan Lennox <jonathan@vidyo.com>, "avtext@ietf.org" <avtext@ietf.org>, mmusic <mmusic@ietf.org>
Content-Type: multipart/alternative; boundary=001a11487c560b8cfc054e636b4a
Archived-At: <https://mailarchive.ietf.org/arch/msg/mmusic/I_uB9-rI57Sz3jw9RI3rtU7vvGg>
Subject: Re: [MMUSIC] [avtext] framemarking: add frame size info
X-BeenThere: mmusic@ietf.org
X-Mailman-Version: 2.1.22
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: Sun, 30 Apr 2017 14:51:54 -0000

Thanks for the pointer Mo,
I couldn't assist to the IETF in Chicago,so I appreciate so much your
response ;).

Best!!

2017-03-27 17:10 GMT+02:00 Mo Zanaty (mzanaty) <mzanaty@cisco.com>om>:

> Hi Miguel,
>
> This was discussed in IETF 97 during the AVTEXT session on Frame Marking.
> See the slides and minutes.
> https://datatracker.ietf.org/meeting/97/session/avtext
>
> The recommended and agreed solution was to use RID rather than add frame
> size
> in the Frame Marking header extension.
>
> Thanks,
> Mo
>
>
> From: mmusic <mmusic-bounces@ietf.org> on behalf of Miguel París Díaz <
> mparisdiaz@gmail.com>
> Date: Monday, March 27, 2017 at 3:43 AM
> To: Jonathan Lennox <jonathan@vidyo.com>
> Cc: "avtext@ietf.org" <avtext@ietf.org>rg>, "mmusic@ietf.org" <
> mmusic@ietf.org>
> Subject: Re: [MMUSIC] [avtext] framemarking: add frame size info
>
> Hello again,
> is there anybody considering this proposal, or nobody see the benefits?
>
> Kind regards!!
>
> 2016-11-10 15:18 GMT+01:00 Miguel París Díaz <mparisdiaz@gmail.com>om>:
>
>> Hello,
>> in the new draft of sdp-simulcast an "RTP Aspect" section [1] has been
>> added, which explains how the media is handled on RTP level.
>>
>> Specifically, In the Media-Switching Mixer section [2] the same thoughts
>> I exposed are said:
>>
>>    This section discusses the behavior in cases where the RTP middlebox
>>    behaves like the Media-Switching Mixer (Section 3.6.2 <https://tools.ietf.org/html/draft-ietf-mmusic-sdp-simulcast-06#section-3.6.2>) in RTP
>>    Topologies [RFC7667 <https://tools.ietf.org/html/rfc7667>].  The fundamental aspect here is that the media
>>    sources delivered from the middlebox will be the mixer's conceptual
>>    or functional ones.  For example, one media source may be the main
>>    speaker in high resolution video, while a number of other media
>>    sources are thumbnails of each participant.
>>
>>    The above results in that the RTP stream produced by the mixer is one
>>    that switches between a number of received incoming RTP streams for
>>    different media sources and in different simulcast versions.  The
>>    mixer selects the media source to be sent as one of the RTP streams,
>>    and then selects among the available simulcast streams for the most
>>    appropriate one.  The selection criteria include available bandwidth
>>    on the mixer to receiver path and restrictions based on the
>>    functional usage of the RTP stream delivered to the receiver.  An
>>    example of the latter, is that it is unnecessary to forward a full HD
>>    video to a receiver if the display area is just a thumbnail.  Thus,
>>    restrictions may exist to not allow some simulcast streams to be
>>    forwarded for some of the mixer's media sources.
>>
>>
>> In our case to provide this feature, currently we have to depay the RTP
>> packets, and apply different types of parses (depending on the codec) to
>> read the frame size, which reduces the scalability of the system and hinder
>> the implementation a lot.
>> Because of that, I think that having frame size (width and height) info
>> in the Frame Marking RTP header extension is quite interesting to implement
>> this kind of use cases in a easy and efficient way (the same that an
>> audio-level extension header is provided to avoid analysing it in the
>> middlebox side).
>>
>> I am adding MMUSIC group in the thread, because I think that this also
>> should be discussed in the context of the simulcast case.
>>
>> Best!!
>>
>> Refs
>> [1] https://tools.ietf.org/html/draft-ietf-mmusic-sdp-simulcast-
>> 06#section-7.2
>> [2] https://tools.ietf.org/html/draft-ietf-mmusic-sdp-simulcast-
>> 06#section-7.2.1
>>
>>
>> 2016-08-30 12:37 GMT+02:00 Miguel París Díaz <mparisdiaz@gmail.com>om>:
>>
>>> I assume that the media distributor has the information from the SDP (it
>>> performs the SDP negotiation which each "client"), but the point is that
>>> encoders may change the video size depending on the available bandwidth,
>>> the complexivity of the video source, etc., unless the sender forces the
>>> encoders' configuration with a fix frame size...
>>>
>>>
>>> 2016-08-26 19:07 GMT+02:00 Jonathan Lennox <jonathan@vidyo.com>om>:
>>>
>>>> (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>
>>>> 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>
>>>> To: 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://twitter.com/mparisdiaz
>>>> ------------------------------------------------------------
>>>> ------------
>>>>
>>>> _______________________________________________
>>>> avtext mailing list
>>>> avtext@ietf.org
>>>> https://www.ietf.org/mailman/listinfo/avtext
>>>>
>>>>
>>>>
>>>
>>>
>>> --
>>> Miguel París Díaz
>>> ------------------------------------------------------------------------
>>> Computer/Software engineer.
>>> Researcher and architect in http://www.kurento.org
>>> http://twitter.com/mparisdiaz
>>> ------------------------------------------------------------------------
>>>
>>
>>
>>
>> --
>> Miguel París Díaz
>> ------------------------------------------------------------------------
>> Computer/Software engineer.
>> Researcher and architect in http://www.kurento.org
>> http://twitter.com/mparisdiaz
>> ------------------------------------------------------------------------
>>
>
>
>
> --
> Miguel París Díaz
> ------------------------------------------------------------------------
> Computer/Software engineer.
> Researcher and architect in http://www.kurento.org
> http://twitter.com/mparisdiaz
> ------------------------------------------------------------------------
>



-- 
Miguel París Díaz
------------------------------------------------------------------------
Computer/Software engineer.
Researcher and architect in http://www.kurento.org
http://twitter.com/mparisdiaz
------------------------------------------------------------------------