Re: [AVTCORE] Comments on draft-ietf-avtcore-feedback-supression-rtp-06.txt

Magnus Westerlund <magnus.westerlund@ericsson.com> Wed, 21 September 2011 15:25 UTC

Return-Path: <magnus.westerlund@ericsson.com>
X-Original-To: avt@ietfa.amsl.com
Delivered-To: avt@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 7657F1F0C84 for <avt@ietfa.amsl.com>; Wed, 21 Sep 2011 08:25:47 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -106.521
X-Spam-Level:
X-Spam-Status: No, score=-106.521 tagged_above=-999 required=5 tests=[AWL=0.078, BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id nmQbGIte96Ei for <avt@ietfa.amsl.com>; Wed, 21 Sep 2011 08:25:46 -0700 (PDT)
Received: from mailgw10.se.ericsson.net (mailgw10.se.ericsson.net [193.180.251.61]) by ietfa.amsl.com (Postfix) with ESMTP id 253321F0C82 for <avt@ietf.org>; Wed, 21 Sep 2011 08:25:45 -0700 (PDT)
X-AuditID: c1b4fb3d-b7c47ae000000b17-30-4e7a028efda3
Received: from esessmw0184.eemea.ericsson.se (Unknown_Domain [153.88.253.125]) by mailgw10.se.ericsson.net (Symantec Mail Security) with SMTP id B3.F6.02839.E820A7E4; Wed, 21 Sep 2011 17:28:14 +0200 (CEST)
Received: from [127.0.0.1] (153.88.115.8) by esessmw0184.eemea.ericsson.se (153.88.115.82) with Microsoft SMTP Server id 8.3.137.0; Wed, 21 Sep 2011 17:28:03 +0200
Message-ID: <4E7A027D.6090603@ericsson.com>
Date: Wed, 21 Sep 2011 17:27:57 +0200
From: Magnus Westerlund <magnus.westerlund@ericsson.com>
User-Agent: Mozilla/5.0 (Windows NT 6.1; rv:6.0.2) Gecko/20110902 Thunderbird/6.0.2
MIME-Version: 1.0
To: Qin Wu <bill.wu@huawei.com>
References: <20110831070359.24630.22446.idtracker@ietfa.amsl.com> <4E5F9C23.8050702@ericsson.com> <19810C85B8E8469899492927E1AAA6B9@china.huawei.com> <4E65D2BD.2050008@ericsson.com> <C6D2DB253DBC45E98EE3DB9F6D3A4D99@china.huawei.com> <4E6E15BD.7060404@ericsson.com> <3FC5A993DFCB4758A8F734C50E7AC21D@china.huawei.com> <4E73657E.2000006@ericsson.com> <BA847A1465E141CB92B4181F8C57D402@china.huawei.com>
In-Reply-To: <BA847A1465E141CB92B4181F8C57D402@china.huawei.com>
X-Enigmail-Version: 1.3.1
Content-Type: text/plain; charset="ISO-8859-1"
Content-Transfer-Encoding: 8bit
X-Brightmail-Tracker: AAAAAA==
Cc: "avt@ietf.org" <avt@ietf.org>, "draft-ietf-avtcore-feedback-supression-rtp@tools.ietf.org" <draft-ietf-avtcore-feedback-supression-rtp@tools.ietf.org>
Subject: Re: [AVTCORE] Comments on draft-ietf-avtcore-feedback-supression-rtp-06.txt
X-BeenThere: avt@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Audio/Video Transport Core Maintenance <avt.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/avt>, <mailto:avt-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/avt>
List-Post: <mailto:avt@ietf.org>
List-Help: <mailto:avt-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/avt>, <mailto:avt-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 21 Sep 2011 15:25:47 -0000

Hi,

I think the discussion has become so convoluted that it is difficult to
understand what applies to which deployment.

On 2011-09-19 07:36, Qin Wu wrote:
> Hi, Magnus:
> Please see my reply below.
> ----- Original Message ----- 
> From: "Magnus Westerlund" <magnus.westerlund@ericsson.com>
> To: "Qin Wu" <bill.wu@huawei.com>
> Cc: <avt@ietf.org>; <draft-ietf-avtcore-feedback-supression-rtp@tools.ietf.org>
> Sent: Friday, September 16, 2011 11:04 PM
> Subject: Re: Comments on draft-ietf-avtcore-feedback-supression-rtp-06.txt
> 
> 
>> On 2011-09-16 12:18, Qin Wu wrote:
>>>>>>
>>>>>>> 5. Section 3, fourth paragraph:
>>>>
>>>> I think using observed RTTs is a good thing. However, one needs to 
>>>> answer the question of who's RTT are one using. A SSM receiver has
>>>> no RTT measurements performed, as they are sending no SRs. So
>>>> unless the summary Report is provided the receiver have no
>>>> knowledge of any RTTs in the system.
>>>>
>>>> This is likely true also for intermediaries unless they send data
>>>> using their own SSRC, like unicast RTX.
>>>>
>>>> Thus, it becomes difficult to know how the entities will behave
>>>> with these retransmission timers.
>>>
>>>
>>> [Qin]: This is not true. Look at the section 7.1.6 of RFC5760, in SSM
>>> summary feedback case, the distribution source can use Round-Trip
>>> time sub-report block defined in section 7.1.6 to tell the receiver
>>> about the round-trip time from the distribution source to the
>>> receivers. This round-trip time can be calculated based on the SR
>>> from media source, RR from receiver and the current time according to
>>> the section 7.1.6. So this round-trip time calculation also applies
>>> to the other use cases.
>>
>> I think we are in full agreement when the summary feedback mode is used.
>> But what if it isn't. What if one uses the simple feedback. 
> 
> [Qin]: As described in draft-ietf-avtcore-feedback-suppression-rtp, 
> 
> in simple feedback case, DS will not send TPLR instead it send NACK.
> 
> I am not sure the timing rule for sending NACK is the scope of this document.
> 

I guess we are back to what "it" says in the following sentence.
One example is the middle box gets
   the retransmitted packet by sending a NACK upstream and sent it
   downstream.

If it is "the NACK". But I have to say that I am confused by this test
if it is one SSM group that continues all the way to the ultimate
receiver and the Intermediary is just a on route monitoring and help
device.


> 
>> Sure, the
>> receiver can measure the time until its RTCP packet comes back to it.
>> But that doesn't measure the Media source to receiver RTT which I
>> believe is the relevant here.
> 
> [Qin]Unlike Summary Feedback model case, in simple feedback model,
> 
>  as described in section 6.1 of RFC5760, the DS create its own Sender
> 
>  report which includes round trip time calculation between DS and 
> 
> receiver.


>  
> 
> If the DS want to know the RTT between media source and itself, the DS
> 
>  can estimate it based on the SR sent from media source to the DS and
> 
>  current time as measured from its own system clock.
> 

I think I missed something important in this case. In simple feedback
model, also the receivers RTCP are feed back into the group. Thus the
combination of the SR and the receivers RRs should enable each
participant to have a view of the delay between the DS and each receiver.


>  
> 
> I don't understand why in this case the receiver still needs to know the RTT 
> between media source and receiver since the SR sent from DS rather than media source 
> carries the round trip time calcualtion.

Well, if the goal is to determine the amount of time a TPLR or for that
matter a NACK suppresses new NACKs I think one have to take into account
the RTTs to be expected before receiving a repair packet or know that it
has been lost.

But with this each session participant clearly has the information it
needs.

> 
>> And I think the question is still what RTT one uses in these
>> measurements. 
> 
> [Qin]: See above.
> 
> 
>> The one related to the media server, or one related to the
>> SSRC injecting the TPLR. They don't need to be the same.
> 
> [Qin]: In all these case, I think SSRC of source is still from media server or media source.
> 
> The SSRC of sender is generated by the middlebox.
> In TPLR format described in section 4.2 of draft-ietf-avtcore-feedback-suppression-rtp, SSRC in FCI format
> is SSRC of media source. Since media source may change, so does SSRC of media source.
> am I wrong?


The above question was really about whose delays in the system one
should consider. If an Intermediary sends the NACK to the DS. Then there
is one RTT between the intermediary and the DS. The downstream receiver
will have another RTT with the DS. In that context I think one do need
to consider which time intervalls that makes sense. What legs of the
system does the messages need to traverse before getting the reaction,
or having to retransmit.

When it comes to the SSRCs, don't forgett that you do have two SSRC isn
the common packet format for feedback messges. One of the source of the
feedback message and one that is the media source that the message
relate to.


>>>
>>> Assume the intermediary sits between media source and receiver, we
>>> can ask intermediary to measure the round trip time between media
>>> source and intermediary, the round trip time between intermediary and
>>> receiver to make sure the media source is more near to the
>>> intermediary than the receiver.
>>
>> Yes, that makes sense. But what method(s) of measuring are you proposing
>> for the intermediary?
> 
> [Qin]: The intermediary may Use the same measurement method described in 
> 
> the section 7.1.6 ,first paragraph of RFC5760 in SSM summary feedback model case.
> 
> Is that clear?

Well, does that work? Is the intermediary receving the RTCP RRs from the
receivers. And what way have they taken to reach the intermediary.

But I have to say that I have become confused in which model we are
discussing here.



-- 

Magnus Westerlund

----------------------------------------------------------------------
Multimedia Technologies, Ericsson Research EAB/TVM
----------------------------------------------------------------------
Ericsson AB                | Phone  +46 10 7148287
Färögatan 6                | Mobile +46 73 0949079
SE-164 80 Stockholm, Sweden| mailto: magnus.westerlund@ericsson.com
----------------------------------------------------------------------