Re: [Gen-art] review of draft-ietf-avtcore-feedback-supression-rtp-16.txt

Qin Wu <bill.wu@huawei.com> Fri, 13 April 2012 08:59 UTC

Return-Path: <bill.wu@huawei.com>
X-Original-To: gen-art@ietfa.amsl.com
Delivered-To: gen-art@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id E7DE421F848F for <gen-art@ietfa.amsl.com>; Fri, 13 Apr 2012 01:59:19 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.652
X-Spam-Level:
X-Spam-Status: No, score=-1.652 tagged_above=-999 required=5 tests=[AWL=0.947, BAYES_00=-2.599]
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 EFELeLoyn7wq for <gen-art@ietfa.amsl.com>; Fri, 13 Apr 2012 01:59:19 -0700 (PDT)
Received: from dfwrgout.huawei.com (dfwrgout.huawei.com [206.16.17.72]) by ietfa.amsl.com (Postfix) with ESMTP id D56A021F8606 for <gen-art@ietf.org>; Fri, 13 Apr 2012 01:59:17 -0700 (PDT)
Received: from 172.18.9.243 (EHLO dfweml201-edg.china.huawei.com) ([172.18.9.243]) by dfwrg01-dlp.huawei.com (MOS 4.2.3-GA FastPath) with ESMTP id AFE58507; Fri, 13 Apr 2012 04:59:17 -0400 (EDT)
Received: from DFWEML406-HUB.china.huawei.com (10.193.5.131) by dfweml201-edg.china.huawei.com (172.18.9.107) with Microsoft SMTP Server (TLS) id 14.1.323.3; Fri, 13 Apr 2012 01:56:02 -0700
Received: from SZXEML422-HUB.china.huawei.com (10.82.67.161) by dfweml406-hub.china.huawei.com (10.193.5.131) with Microsoft SMTP Server (TLS) id 14.1.323.3; Fri, 13 Apr 2012 01:56:08 -0700
Received: from w53375 (10.138.41.149) by szxeml422-hub.china.huawei.com (10.82.67.161) with Microsoft SMTP Server (TLS) id 14.1.323.3; Fri, 13 Apr 2012 16:56:02 +0800
Message-ID: <C92761F5031B46058D647B52CEF649A5@china.huawei.com>
From: Qin Wu <bill.wu@huawei.com>
To: Magnus Westerlund <magnus.westerlund@ericsson.com>
References: <201204121143.q3CBhKgh034929@givry.fdupont.fr> <3E7F70F6BF7A49EC834DD001A636D13E@china.huawei.com> <4F87E5BE.3080100@ericsson.com>
Date: Fri, 13 Apr 2012 16:56:01 +0800
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 6.00.2900.5931
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.6109
X-Originating-IP: [10.138.41.149]
X-CFilter-Loop: Reflected
Cc: gen-art@ietf.org, draft-ietf-avtcore-feedback-supression-rtp.all@tools.ietf.org
Subject: Re: [Gen-art] review of draft-ietf-avtcore-feedback-supression-rtp-16.txt
X-BeenThere: gen-art@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "GEN-ART: General Area Review Team" <gen-art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/gen-art>, <mailto:gen-art-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/gen-art>
List-Post: <mailto:gen-art@ietf.org>
List-Help: <mailto:gen-art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/gen-art>, <mailto:gen-art-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 13 Apr 2012 08:59:20 -0000

Hi,
----- Original Message ----- 
From: "Magnus Westerlund" <magnus.westerlund@ericsson.com>
To: "Qin Wu" <bill.wu@huawei.com>
Cc: "Francis Dupont" <Francis.Dupont@fdupont.fr>fr>; <gen-art@ietf.org>rg>; <draft-ietf-avtcore-feedback-supression-rtp.all@tools.ietf.org>
Sent: Friday, April 13, 2012 4:37 PM
Subject: Re: review of draft-ietf-avtcore-feedback-supression-rtp-16.txt


> On 2012-04-13 10:19, Qin Wu wrote:
>> Hi,Francis:
>> Sorry for late reply. please see my repy inline.
>> ----- Original Message ----- 
>> From: "Francis Dupont" <Francis.Dupont@fdupont.fr>
>> To: "Qin Wu" <bill.wu@huawei.com>
>> Cc: <gen-art@ietf.org>rg>; <draft-ietf-avtcore-feedback-supression-rtp.all@tools.ietf.org>
>> Sent: Thursday, April 12, 2012 7:43 PM
>> Subject: Re: review of draft-ietf-avtcore-feedback-supression-rtp-16.txt 
>> 
>> 
>>> In your previous mail you wrote:
>>>
>>>>  > - Abstract page 1: implosion -> explosion (things which can implode are rare :-)
>>>>  
>>>>  [Qin]: RFC4588 referenced by this document is using "implosion". So
>>>>  I think it should be fine to use the same term in this document.:-)
>>>
>>> => RFC 2887 too. IMHO it is time to stop this "implosion" madness and
>>> to return to a correct language (BTW we have the same problem in French, for
>>> an unknown reason the word implosion is often used in place of explosion
>>> when it has the exact opposite meaning...).
>> 
>> [Qin]:I can understand it is more sensitive to use "explosion" than "implosion"in France.:-)
>> However my understanding is implosion seems to mean feedback messages overwhelm the network capacity.
>> If we change "implosion" into "explosion", we seems to change the meaning of "feedback implosion", 
>> that is to say, "feedback explision " means feedback message has already paralyzed the network. The Network dies :-).
>> I am aware that RFC4585 also use "feedback implosion". Since this draft references RFC4585,
>> Isn't draft-ietf-avtcore-feedback-supression-rtp in accordance with RFC4585?
> 
> I would like to point out that feedback implosion actually can be seen
> as an implosion event. All the feedback traffic generated are
> concentrated at the target for the feedback. Thus causing an implosion
> of the feedback target under the "weight" of all the feedback.

[Qin]: Exactly.

> But, seriously "Feedback Implosion" is an established expression within
> computer science. Thus although it may not be all correct we shouldn't
> change it. 

[Qin]: Agree. 

>I would recommend that you google "Feedback Implosion" all
> the hits on the first page are related to computer science, at least for me.
> 
> Cheers
> 
> 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
> ----------------------------------------------------------------------
>