Re: [xrblock] proposed change to discard draft for the issue:duplication packet discards

Colin Perkins <csp@csperkins.org> Tue, 21 August 2012 22:02 UTC

Return-Path: <csp@csperkins.org>
X-Original-To: xrblock@ietfa.amsl.com
Delivered-To: xrblock@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id E983E21F85AF for <xrblock@ietfa.amsl.com>; Tue, 21 Aug 2012 15:02:21 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -103.553
X-Spam-Level:
X-Spam-Status: No, score=-103.553 tagged_above=-999 required=5 tests=[AWL=0.045, BAYES_00=-2.599, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-1, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 8kNKsjyBhQpw for <xrblock@ietfa.amsl.com>; Tue, 21 Aug 2012 15:02:21 -0700 (PDT)
Received: from anchor-msapost-1.mail.demon.net (anchor-msapost-1.mail.demon.net [195.173.77.164]) by ietfa.amsl.com (Postfix) with ESMTP id EA37021F85A8 for <xrblock@ietf.org>; Tue, 21 Aug 2012 15:02:20 -0700 (PDT)
Received: from starkperkins.demon.co.uk ([80.176.158.71] helo=[192.168.0.11]) by anchor-post-1.mail.demon.net with esmtpsa (AUTH csperkins-dwh) (TLSv1:AES128-SHA:128) (Exim 4.69) id 1T3wWh-0005uI-hw; Tue, 21 Aug 2012 22:02:19 +0000
Mime-Version: 1.0 (Apple Message framework v1278)
Content-Type: multipart/alternative; boundary="Apple-Mail=_5E76D8F5-8038-4FEA-A790-08A194BAF209"
From: Colin Perkins <csp@csperkins.org>
X-Priority: 3
In-Reply-To: <E107A66D6D774BCB93CA1E1D2045D6BD@china.huawei.com>
Date: Tue, 21 Aug 2012 23:02:17 +0100
Message-Id: <A43F1D04-F8D8-4651-A12A-0EFFB5DE5F86@csperkins.org>
References: <CC53B1A9.4935B%alan.d.clark@telchemy.com><D04380D1-7EC7-4F4C-A22B-EEE374A452A8@csperkins.org><CALw1_Q0EHyf98AFt4O=53BKAKtQAq4cyUZKqA1DeoPs1dovxNw@mail.gmail.com> <05210899-B3BD-4E02-99A4-71469B6B12E6@csperkins.org> <E107A66D6D774BCB93CA1E1D2045D6BD@china.huawei.com>
To: Qin Wu <bill.wu@huawei.com>
X-Mailer: Apple Mail (2.1278)
Cc: xrblock@ietf.org
Subject: Re: [xrblock] proposed change to discard draft for the issue:duplication packet discards
X-BeenThere: xrblock@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Metric Blocks for use with RTCP's Extended Report Framework working group discussion list <xrblock.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/xrblock>, <mailto:xrblock-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/xrblock>
List-Post: <mailto:xrblock@ietf.org>
List-Help: <mailto:xrblock-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/xrblock>, <mailto:xrblock-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 21 Aug 2012 22:02:22 -0000

Qin,

On 20 Aug 2012, at 05:44, Qin Wu wrote:
> Hi,
> ----- Original Message -----
> From: Colin Perkins
> To: Kevin Gross
> Cc: xrblock@ietf.org
> Sent: Saturday, August 18, 2012 12:12 AM
> Subject: Re: [xrblock] proposed change to discard draft for the issue:duplication packet discards
> 
> Kevin,
> 
> On 17 Aug 2012, at 18:11, Kevin Gross wrote:
>> I don't think it is necessary or appropriate to include this sort of value judgement. What is expensive? What is necessary? At best, this is getting tangential. I support the original wording of Qin's note though I think it should be a separate paragraph and perhaps marked as a note.
> 
> Qin's original wording seems to me to be encouraging duplication. I do not support that, since it does break RTCP statistics if done in the naïve way implied. I'm happy if someone wants to propose a more neutral wording, part-way between my suggestion and Qin's text.
>  
> [Qin]: How about rephrasing it as follows:
> "
> Note that duplicating RTP packets is for robustness or error resilience but may disrupts RTCP statitics.
> In order to tackle this, the mechanism described in [draft-ietf-avext-rtp-duplication-00] can be used which
> will not cause breakage of RTP streams or RTCP rules.
> "
> This statement will put as an indepent paragraph as Kevin suggested.

The "may disrupt RTCP statistics" is misleading: duplicating RTP packets in the naïve manner _will_ break RTCP. 

-- 
Colin Perkins
http://csperkins.org/