IETF Logo Mail Archive

[AVTCORE] Fw: New Version Notification for draft-ietf-avtcore-feedback-supression-rtp-01

Qin Wu <sunseawq@huawei.com> Fri, 15 April 2011 10:04 UTC

Return-Path: <sunseawq@huawei.com>
X-Original-To: avt@ietfc.amsl.com
Delivered-To: avt@ietfc.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfc.amsl.com (Postfix) with ESMTP id 1FFB2E07A9 for <avt@ietfc.amsl.com>; Fri, 15 Apr 2011 03:04:36 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.642
X-Spam-Level:
X-Spam-Status: No, score=-2.642 tagged_above=-999 required=5 tests=[AWL=3.072, BAYES_00=-2.599, HTML_FONT_FACE_BAD=0.884, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([208.66.40.236]) by localhost (ietfc.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id oR-wJCKcQyOR for <avt@ietfc.amsl.com>; Fri, 15 Apr 2011 03:04:35 -0700 (PDT)
Received: from szxga04-in.huawei.com (szxga04-in.huawei.com [119.145.14.67]) by ietfc.amsl.com (Postfix) with ESMTP id 9F2F5E065A for <avt@ietf.org>; Fri, 15 Apr 2011 03:04:34 -0700 (PDT)
Received: from huawei.com (szxga04-in [172.24.2.12]) by szxga04-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 2.14 (built Aug 8 2006)) with ESMTP id <0LJO00GNMUL3PE@szxga04-in.huawei.com> for avt@ietf.org; Fri, 15 Apr 2011 18:03:04 +0800 (CST)
Received: from huawei.com ([172.24.2.119]) by szxga04-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 2.14 (built Aug 8 2006)) with ESMTP id <0LJO00F9MUL39H@szxga04-in.huawei.com> for avt@ietf.org; Fri, 15 Apr 2011 18:03:03 +0800 (CST)
Received: from w53375 ([10.138.41.70]) by szxml04-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 2.14 (built Aug 8 2006)) with ESMTPA id <0LJO00HEXUL3C2@szxml04-in.huawei.com> for avt@ietf.org; Fri, 15 Apr 2011 18:03:03 +0800 (CST)
Date: Fri, 15 Apr 2011 18:05:53 +0800
From: Qin Wu <sunseawq@huawei.com>
To: avt@ietf.org
Message-id: <03fa01cbfb54$b52f1f20$46298a0a@china.huawei.com>
MIME-version: 1.0
X-MIMEOLE: Produced By Microsoft MimeOLE V6.00.2900.3664
X-Mailer: Microsoft Outlook Express 6.00.2900.3664
Content-type: multipart/alternative; boundary="Boundary_(ID_JqI8j4EHb8QGMRK3Ds99bw)"
X-Priority: 3
X-MSMail-priority: Normal
Cc: magnus.westerlund@ericsson.com
Subject: [AVTCORE] Fw: New Version Notification for draft-ietf-avtcore-feedback-supression-rtp-01
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: Fri, 15 Apr 2011 10:04:36 -0000

Hi,folks:
We have updated draft-ietf-avtcore-feedback-suppression-rtp to version 01 to address the comments from Prague meeting and on the list. 
The new version is available at:
http://datatracker.ietf.org/doc/draft-ietf-avtcore-feedback-supression-rtp/
the diff from 00 is 
http://tools.ietf.org/rfcdiff?url2=draft-ietf-avtcore-feedback-supression-rtp-01

Also I recall in the meeting there was a comment about use case and we have four use cases 
in the current draft and I would ask WG do people think these use cases are clear and 
what use cases are missing and do people think that use cases are needed.

Regards!
-Qin 
----- Original Message ----- 
From: "IETF I-D Submission Tool" <idsubmission@ietf.org>
To: <sunseawq@huawei.com>
Cc: <xiayangsong@huawei.com>; <Even.roni@huawei.com>
Sent: Friday, April 15, 2011 5:52 PM
Subject: New Version Notification for draft-ietf-avtcore-feedback-supression-rtp-01


> 
> A new version of I-D, draft-ietf-avtcore-feedback-supression-rtp-01.txt has been successfully submitted by Wenson Wu and posted to the IETF repository.
> 
> Filename: draft-ietf-avtcore-feedback-supression-rtp
> Revision: 01
> Title: RTCP Extension for Feedback Suppression Indication
> Creation_date: 2011-04-15
> WG ID: avtcore
> Number_of_pages: 17
> 
> Abstract:
> In a large RTP session using the RTCP feedback mechanism defined in
> RFC 4585, a media source or middlebox may experience transient
> overload if some event causes a large number of receivers to send
> feedback at once.  This feedback implosion can be mitigated if the
> device suffering from overload can send a third party loss report
> message to the receivers to inhibit further feedback.  This memo
> defines RTCP extensions for third party loss report, to suppress NACK
> and FIR feedback requests.  It also defines associated SDP signaling.
>                                                                                  
> 
> 
> The IETF Secretariat.
> 
>

v2.23.0 | Report a Bug | By Email