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

Francis Dupont <Francis.Dupont@fdupont.fr> Fri, 13 April 2012 09:07 UTC

Return-Path: <Francis.Dupont@fdupont.fr>
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 7B74A21F8491 for <gen-art@ietfa.amsl.com>; Fri, 13 Apr 2012 02:07:04 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.539
X-Spam-Level:
X-Spam-Status: No, score=-2.539 tagged_above=-999 required=5 tests=[AWL=0.060, 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 WdF3S6w0pnGb for <gen-art@ietfa.amsl.com>; Fri, 13 Apr 2012 02:07:04 -0700 (PDT)
Received: from givry.fdupont.fr (givry.fdupont.fr [IPv6:2001:41d0:1:6d55:211:5bff:fe98:d51e]) by ietfa.amsl.com (Postfix) with ESMTP id AF6B721F847D for <gen-art@ietf.org>; Fri, 13 Apr 2012 02:07:03 -0700 (PDT)
Received: from givry.fdupont.fr (localhost [127.0.0.1]) by givry.fdupont.fr (8.14.3/8.14.3) with ESMTP id q3D96t6a013105; Fri, 13 Apr 2012 11:06:57 +0200 (CEST) (envelope-from dupont@givry.fdupont.fr)
Message-Id: <201204130906.q3D96t6a013105@givry.fdupont.fr>
From: Francis Dupont <Francis.Dupont@fdupont.fr>
To: Qin Wu <bill.wu@huawei.com>
In-reply-to: Your message of Fri, 13 Apr 2012 16:19:44 +0800. <3E7F70F6BF7A49EC834DD001A636D13E@china.huawei.com>
Date: Fri, 13 Apr 2012 11:06:55 +0200
Sender: Francis.Dupont@fdupont.fr
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 09:07:04 -0000

 In your previous mail you wrote:

> [Qin]:I can understand it is more sensitive to use "explosion" than
> "implosion" in France.:-)

=> both words exist in both language with the same spelling and
meaning.  Perhaps do you mean we are more attached to use the right
term in France (:-)?

> However my understanding is implosion seems to mean feedback
> messages overwhelm the network capacity.

=> this is the definition of explosion.

>  If we change "implosion" into "explosion", we seems to change the
>  meaning of "feedback implosion", that is to say, "feedback
>  explosion " 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?

=> you have the choice between using the correct term or keeping the
wrong term because some did the error in referenced documents.
You know my opinion.

Regards

Francis.Dupont@fdupont.fr

PS: perhaps we should ask the RFC Editor to produce a collective
Errata to fix this misuse of implosion for explosion?