Re: [rmcat] I-D Action: draft-ietf-rmcat-cc-requirements-07.txt
Varun Singh <vsingh.ietf@gmail.com> Tue, 11 November 2014 22:01 UTC
Return-Path: <vsingh.ietf@gmail.com>
X-Original-To: rmcat@ietfa.amsl.com
Delivered-To: rmcat@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id BBC9C1A1AF4 for <rmcat@ietfa.amsl.com>; Tue, 11 Nov 2014 14:01:21 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.999
X-Spam-Level:
X-Spam-Status: No, score=-1.999 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, SPF_PASS=-0.001] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id ScF8Lu_pSHlg for <rmcat@ietfa.amsl.com>; Tue, 11 Nov 2014 14:01:19 -0800 (PST)
Received: from mail-ie0-x22d.google.com (mail-ie0-x22d.google.com [IPv6:2607:f8b0:4001:c03::22d]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id CA8521A1A59 for <rmcat@ietf.org>; Tue, 11 Nov 2014 14:01:18 -0800 (PST)
Received: by mail-ie0-f173.google.com with SMTP id tr6so12359519ieb.32 for <rmcat@ietf.org>; Tue, 11 Nov 2014 14:01:17 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=eogbcXQlyhp1I+qSzhsnTmAg8lHN7DQ+TTNZDmMblPA=; b=bmiFkpw6Yx5fDxYEXDpyEIt+DtYMMaosifh2kwhPBRQgT9rp2G94Fb+/a6hs/sD+Vg 9EA7kuj1jVl4XlhfcfLqXnC+bjzMLMow4Y48ta3Kb2V7cu8hohegadD0wwOJRbVnUVme AD9WxOG5d1SzWehC+zlNrKTsaBIj5B3Zu3WKbuGWUxlAiqj0a1RzIokRsTwCDOrJu3lB mHXYp7kEI44N3gOfkjzKiNQrN8U74ZOj6V5+wjdYI7E3jHQ84zc9NvUBSqSdf8q5QQF4 yYLai9LPTbCQQD8COYWdCAcZYIXRe3k2b2ItGpyngyn7nOPcTd7kYtZyGRUvJHgSqJ19 DMTw==
MIME-Version: 1.0
X-Received: by 10.107.138.26 with SMTP id m26mr12774219iod.64.1415743277800; Tue, 11 Nov 2014 14:01:17 -0800 (PST)
Received: by 10.50.95.199 with HTTP; Tue, 11 Nov 2014 14:01:17 -0800 (PST)
Received: by 10.50.95.199 with HTTP; Tue, 11 Nov 2014 14:01:17 -0800 (PST)
In-Reply-To: <E0F7A68B07B53F4FBD12DABD61CBA90E127E39E6@ESESSMB307.ericsson.se>
References: <20141027182704.18420.64429.idtracker@ietfa.amsl.com> <CAChjaGwWNyyKYtJFVHa731_hPCv=CU9+ZL7MuvP4HN8uxmAysw@mail.gmail.com> <54521BEB.8090807@ericsson.com> <59ef1bef12d457c5f934d87680712c68@mail.gmail.com> <545240E3.6080503@ericsson.com> <a26e6e2e11f1cc7ccec50f35c2466ad7@mail.gmail.com> <54525B77.40109@ericsson.com> <69F46100-6951-499C-948B-F3BA366D1E19@csperkins.org> <54573FD4.5090503@ericsson.com> <E0F7A68B07B53F4FBD12DABD61CBA90E127E39E6@ESESSMB307.ericsson.se>
Date: Tue, 11 Nov 2014 12:01:17 -1000
Message-ID: <CAEbPqrybNSzDjpLr6yxZGDL0-YS3J1CUoZnpsN=zKZX4ch36OQ@mail.gmail.com>
From: Varun Singh <vsingh.ietf@gmail.com>
To: Zaheduzzaman Sarker <zaheduzzaman.sarker@ericsson.com>
Content-Type: multipart/alternative; boundary="001a113ff6aa2aa27605079c6bca"
Archived-At: http://mailarchive.ietf.org/arch/msg/rmcat/tDNHAPFYI4SvzfWx2Hq3UjzvwdM
Cc: "Karen E. Egede Nielsen" <karen.nielsen@tieto.com>, rmcat WG <rmcat@ietf.org>, Varun Singh <varun@comnet.tkk.fi>, Colin Perkins <csp@csperkins.org>, Randell Jesup <randell-ietf@jesup.org>
Subject: Re: [rmcat] I-D Action: draft-ietf-rmcat-cc-requirements-07.txt
X-BeenThere: rmcat@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: "RTP Media Congestion Avoidance Techniques \(RMCAT\) Working Group discussion list." <rmcat.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/rmcat>, <mailto:rmcat-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/rmcat/>
List-Post: <mailto:rmcat@ietf.org>
List-Help: <mailto:rmcat-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/rmcat>, <mailto:rmcat-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 11 Nov 2014 22:01:21 -0000
Hi Zahed, Look's good. A minor nit inline. On 11 Nov 2014 11:30, "Zaheduzzaman Sarker" < zaheduzzaman.sarker@ericsson.com> wrote: > > Hi, > > To address the comments regarding adding text related to rtp circuit breaker, I am going to add following text ("-->" marks the beginning of the additional text) to the already existing text in the introduction of the draft. Let me know if it captures the essences of the discussions. > > "One particular protocol portfolio being developed for this use case > is WebRTC [I-D.ietf-rtcweb-overview], where one envisions sending > multiple flows using the Real-time Transport Protocol (RTP) [RFC3550] > between two peers, in conjunction with data flows, all at the same > time, without having special arrangements with the intervening > service providers. --> As RTP does not provide any congestion control > mechanism; a set of circuit breakers, such as [I-D.ietf-avtcore-rtp- AFAIK there are no other circuit breakers, I'd suggest removing such as. > circuit-breakers], are required to protect the network from excessive Excessive congestion --> congestion collapse? > congestion caused by the non-congestion controlled flows. When the > real-time interactive media is congestion controlled, it is > recommended that the congestion control mechanism operates within the > constraints defined by these circuit breakers when circuit breaker is > present and that it should not cause congestion collapse when circuit > breaker is not implemented.<--" > > BR > > Zahed > > > -----Original Message----- > > From: rmcat [mailto:rmcat-bounces@ietf.org] On Behalf Of Zaheduzzaman > > Sarker > > Sent: den 3 november 2014 09:42 > > To: Colin Perkins > > Cc: Karen E. E. Nielsen; Randell Jesup; rmcat WG > > Subject: Re: [rmcat] I-D Action: draft-ietf-rmcat-cc-requirements-07.txt > > > > > > > > On 2014-11-01 19:43, Colin Perkins wrote: > > > On 30 Oct 2014, at 15:38, Zaheduzzaman Sarker > > <zaheduzzaman.sarker@ericsson.com> wrote: > > >> On 2014-10-30 15:05, Karen Elisabeth Egede Nielsen wrote: > > >>> Interworking with circuit breaker and prevention of collapse when circuit > > breaker is not active to me sounds like requirements. > > >>> > > >>> The same may goes for the statement from the app interaction > > reformulated, e.g., in the following way: > > >>> > > >>> The RMCAT congestion control should constrain the traffic under its control > > so that the circuit breaker only may trip as a consequence of issues exterior to > > the RMCAT congestion control, like link path failures or severe congestion > > caused by traffic flows not under RMCAT congestion control. > > >>> > > >>> My personal preference would be to have this become an explicit new > > requirement (with subclauses). Would you rather like to see this be discussed in > > the introduction only ? > > >>> > > >> > > >> If we define requirements on the relationship between circuit breaker and > > RMCAT congestion control algorithm then I think we will have to state more > > than what is stated above (explaining how the requirement can be realize when > > RTP/AVPF is used). > > >> > > >> The circuit breaker draft states - > > >> "Receiving rapid feedback about congestion events potentially allows > > >> congestion control algorithms to be more responsive, and to better > > >> adapt the media transmission to the limitations of the network. It > > >> is expected that many RTP congestion control algorithms will adopt > > >> the RTP/AVPF profile for this reason, defining new transport layer > > >> feedback reports that suit their requirements. Since these reports > > >> are not yet defined, and likely very specific to the details of the > > >> congestion control algorithm chosen, they cannot be used as part of > > >> the generic RTP circuit breaker.". > > >> > > >> This is a general wisdom that RMCAT congestion control algorithms with use > > RTP/AVPF. Correct me if I am wrong but we are yet to see the impact of circuit > > breaker when used with RTP/AVPF. > > > > > > The RTP circuit breaker draft does have some discussion of how it interacts > > with RTP/AVPF feedback, but I agree that we haven't fully explored how it > > interacts with reduced RTCP reporting intervals. That's the remaining open issue > > with the -07 version of the circuit breaker draft. > > > > > >> I was thinking that we can keep the relationship between the generic circuit > > breaker and congestion control algorithm as "expected" not as "required". Then > > we have eval guideline which can outline how to evaluate to candidate RMCAT > > Algorithms when circuit breaker is available and not available. > > > > > > Perhaps RECOMMENDED rather than REQUIRED? > > > > yes, that sounds good to me. > > > > BR > > > > -- > > > > Zahed > > > > ================================================== > > ANM ZAHEDUZZAMAN SARKER > > > > > > Ericsson AB > > Services, Media and Network Features > > Laboratoriegränd 11 > > 97128 Luleå, Sweden > > Phone +46 10 717 37 43 > > Fax +46 920 996 21 > > SMS/MMS +46 76 115 37 43 > > zaheduzzaman.sarker@ericsson.com > > www.ericsson.com > > > > ================================================== >
- [rmcat] I-D Action: draft-ietf-rmcat-cc-requireme… internet-drafts
- Re: [rmcat] I-D Action: draft-ietf-rmcat-cc-requi… Karen Elisabeth Egede Nielsen
- Re: [rmcat] I-D Action: draft-ietf-rmcat-cc-requi… Zaheduzzaman Sarker
- Re: [rmcat] I-D Action: draft-ietf-rmcat-cc-requi… Karen Elisabeth Egede Nielsen
- Re: [rmcat] I-D Action: draft-ietf-rmcat-cc-requi… Zaheduzzaman Sarker
- Re: [rmcat] I-D Action: draft-ietf-rmcat-cc-requi… Karen Elisabeth Egede Nielsen
- Re: [rmcat] I-D Action: draft-ietf-rmcat-cc-requi… Zaheduzzaman Sarker
- Re: [rmcat] I-D Action: draft-ietf-rmcat-cc-requi… Colin Perkins
- Re: [rmcat] I-D Action: draft-ietf-rmcat-cc-requi… Zaheduzzaman Sarker
- Re: [rmcat] I-D Action: draft-ietf-rmcat-cc-requi… Zaheduzzaman Sarker
- Re: [rmcat] I-D Action: draft-ietf-rmcat-cc-requi… Varun Singh
- Re: [rmcat] I-D Action: draft-ietf-rmcat-cc-requi… Zaheduzzaman Sarker
- Re: [rmcat] I-D Action: draft-ietf-rmcat-cc-requi… Colin Perkins