Re: [aqm] [tsvwg] Using intelligent dropping to improve video quality under congestion (draft-lai-tsvwg-normalizer-00.txt)

"Cheng-Jia Lai (chelai)" <chelai@cisco.com> Wed, 10 July 2013 23:43 UTC

Return-Path: <chelai@cisco.com>
X-Original-To: aqm@ietfa.amsl.com
Delivered-To: aqm@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 6D04D11E814E; Wed, 10 Jul 2013 16:43:00 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -10.599
X-Spam-Level:
X-Spam-Status: No, score=-10.599 tagged_above=-999 required=5 tests=[AWL=0.000, BAYES_00=-2.599, RCVD_IN_DNSWL_HI=-8]
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 kYnkvpgVEuWp; Wed, 10 Jul 2013 16:42:56 -0700 (PDT)
Received: from rcdn-iport-6.cisco.com (rcdn-iport-6.cisco.com [173.37.86.77]) by ietfa.amsl.com (Postfix) with ESMTP id 7FEB121F9B38; Wed, 10 Jul 2013 16:42:55 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=8199; q=dns/txt; s=iport; t=1373499775; x=1374709375; h=from:to:cc:subject:date:message-id:references: in-reply-to:content-transfer-encoding:mime-version; bh=JD1mJnu2lnchGEMAxov2z+JrzktK+Y27xua2GBg46/Y=; b=g4C/OCFf3raKEiTQ04BzB1ks6Jnar3d59EIWMZsGaO6NbD4+fSzC/qZF jSQduEJqhNe1IW6ovcndB0AjabDx6N3HzRK8bXU+d2InvDf9N6R3p/YOm UfL7I6V8K7dx5aF5bA6ajFrU2ZPGwlDc1u8u4nXjd8noXG2gEB4tbUDE8 c=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AisFAOXw3VGtJV2b/2dsb2JhbABagwkyTcEngQ4WdIIjAQEBAQIBZRQFBwQCAQgRAQMBAQEKAhcEBzIUAwYIAgQBDQEECAGIAAYMt16PMgYrAgUGgwNsA4hvkBSQIYFYgTmCKA
X-IronPort-AV: E=Sophos;i="4.87,1039,1363132800"; d="scan'208";a="233346935"
Received: from rcdn-core-4.cisco.com ([173.37.93.155]) by rcdn-iport-6.cisco.com with ESMTP; 10 Jul 2013 23:42:54 +0000
Received: from xhc-aln-x09.cisco.com (xhc-aln-x09.cisco.com [173.36.12.83]) by rcdn-core-4.cisco.com (8.14.5/8.14.5) with ESMTP id r6ANgr0q016324 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL); Wed, 10 Jul 2013 23:42:53 GMT
Received: from xmb-aln-x11.cisco.com ([169.254.6.51]) by xhc-aln-x09.cisco.com ([173.36.12.83]) with mapi id 14.02.0318.004; Wed, 10 Jul 2013 18:42:53 -0500
From: "Cheng-Jia Lai (chelai)" <chelai@cisco.com>
To: Dave Taht <dave.taht@gmail.com>, "Toerless Eckert (eckert)" <eckert@cisco.com>
Thread-Topic: [tsvwg] Using intelligent dropping to improve video quality under congestion (draft-lai-tsvwg-normalizer-00.txt)
Thread-Index: AQHOfaBDTO2Q2/ChiUO6fKWGKHceJZleig/Q
Date: Wed, 10 Jul 2013 23:42:52 +0000
Message-ID: <A860EC86B79FA646BF3F89165A886264153324B5@xmb-aln-x11.cisco.com>
References: <20130710180147.GA614@cisco.com> <CAA93jw68E5DgtzvE5N=2-QnGzZQzYQkevFwqWmiSGxiBZk0h4Q@mail.gmail.com>
In-Reply-To: <CAA93jw68E5DgtzvE5N=2-QnGzZQzYQkevFwqWmiSGxiBZk0h4Q@mail.gmail.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [10.154.161.170]
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Cc: "rmcat@ietf.org" <rmcat@ietf.org>, "rtcweb@ietf.org" <rtcweb@ietf.org>, "tsvwg@ietf.org" <tsvwg@ietf.org>, "aqm@ietf.org" <aqm@ietf.org>
Subject: Re: [aqm] [tsvwg] Using intelligent dropping to improve video quality under congestion (draft-lai-tsvwg-normalizer-00.txt)
X-BeenThere: aqm@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "Discussion list for active queue management and flow isolation." <aqm.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/aqm>, <mailto:aqm-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/aqm>
List-Post: <mailto:aqm@ietf.org>
List-Help: <mailto:aqm-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/aqm>, <mailto:aqm-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 10 Jul 2013 23:43:00 -0000

Yes, NM could also work with ECN (and it should be made so). In fact, we did implementation using WRED on routers that support ECN markings. If RTP endpoints support ECN markings, WRED will mark ECN instead of dropping the packets as avg Q size is between min & max threshold. But it still suffers from unfairness at congestion, where the avg Q size starts to exceed the max threshold for the lowest priority packet class...

We did experience a hard time trying to properly configure WRED parameters for preferential dropping of video packets with our NM implementation... It is a good insight you said here: maybe it is worth exploring how our work can perhaps use other AQM algorithms like CoDel, PIE, etc.

In fact, NM doesn't need specific AQM to drop by probabilities... it will be interesting to see how it can work with delay-based dropping. However, NM does require some "weighted" version of those AQMs. Hopefully a weighted version (if any) won't introduce new parameters (or too many) to configure the AQM.

Regards,
CJ


-----Original Message-----
From: tsvwg-bounces@ietf.org [mailto:tsvwg-bounces@ietf.org] On Behalf Of Dave Taht
Sent: Wednesday, July 10, 2013 12:02 PM
To: Toerless Eckert (eckert)
Cc: rmcat@ietf.org; rtcweb@ietf.org; tsvwg@ietf.org
Subject: Re: [tsvwg] Using intelligent dropping to improve video quality under congestion (draft-lai-tsvwg-normalizer-00.txt)

On Wed, Jul 10, 2013 at 11:01 AM, Toerless Eckert (eckert)
<eckert@cisco.com> wrote:
> When dealing with congestion for real-time datagram (UDP/RTP) based video flows, one idea
> that we think has shown to provide good value is to intelligently drop in the network
> preferentially the least important packets within a video flow, for example non-referenced
> P-frames, because their loss creates the lowest impact to video quality.

I've begun to look at webrtc of late in the context of fq_codel.

One thing that might work would be ECN marking important frames and
not ECN marking
others. Problem overall is that ecn can be gamed and is largely not
enabled, and so on...

> One of the main concerns raised against such schemes was one of fairness. If flows
> would start to indicate different priorities for packets in them, how would we
> be able to avoid that flows would indicate all their packets to be of high priority
> to shift packet drops to other flows. Or even more importantly: how could we motivate
> flows to indicate that some of their packets are low priority without them having to
> fear that they would experience more loss than than flows that don't do this.

same gaming problem...

> So, there is one draft that we would like to present (presumably in TSVWG)  explaining
> how we think this problem can be solved: draft-lai-tsvwg-normalizer-00.txt
>
> (Actually, this is how we did solve the problem in our implementatin of intelligent dropping,
>  so this is not theoretical).

In the case of the fq_codel algorithm I can see a "delayed drop"
mechanism happening,
where upon deciding to drop, it could defer a drop up to a few packets
based on the classification
of the packet, say 3 packets at most. Since flows are already
identified, this is kind of easy
by adding another state variable...

At the moment what I have deployed and tested most is a simple 3 tier
fq_codel based shaper,
which has a priority, best effort, and background queue. The priority
queue is generally only DNS traffic,
the background is only CS1, and fq_codel does such a good job with
sparse streams in
the general case that for VOIP, etc on the networks I fiddle with,
there is no point in having
much more than the BE queue. And presently all other markings are ignored.

video is another story. (or could be, I don't know enough about
webrtc's behaviors to
"see" what will happen)

So I can see trying to utilize the AF markings as you describe in your
draft in codel's
drop decision. While this is also subject to being gamed, the
disincentives are slight.

This is a little different from using "drop probability" as the
decider, however, but I
would hope that this mapping of the old AF style random drop ideas
into the new style delay
ideas could work...

And what codel depends on is a definition of "TCP friendly". That if a
stream is not
going to behave in a tcp friendly manner, then an entirely different
strategy for such
flows seems necessary, and glomming on some additional state isn't going to
be the right thing.

> Now granted, the problem of fairness is but one element of building a complete ssytem
> around the idea of intelligent dropping, so if folks here on the lists would like to
> see for example
>
>   a) how well can it work in routers to shift packet drops to low-prio packets

I guess where I fall apart here is how to shift the encoders to send thinner
streams at  any level of packet drop.

>   b) whats the evidence that it's good for video quality
>   c) How should we do the marking best going forward

> Then please let us know. We'd be very interested to provide insight into the parts of
> those pieces that we have also worked out or discuss the ones we have not (primarily c ;-)

I'd be interested in specific codecs, example video streams, and test
scripts to try
and fiddle with this, as well as viable metrics.

>
> Thanks!
>     Toerless
>
> In-Reply-To: <A860EC86B79FA646BF3F89165A886264151D0AB9@xmb-aln-x11.cisco.com>
>
> On Sat, Feb 09, 2013 at 03:00:48AM +0000, Cheng-Jia Lai (chelai) wrote:
>> Hi all,
>>
>> We have submitted a new Internet draft to describe a Normalization Marker (NM) for DiffServ AF PHB groups, based on our work at Cisco. The goal of NM deployment is to create a new incentive for video encoders to generate more discardable packets when using AF PHB in DIffServ. We are looking forward to your review comments.
>>
>> Best regards,
>> CJ
>>
>> -----Original Message-----
>> From: internet-drafts@ietf.org [mailto:internet-drafts@ietf.org]
>> Sent: Friday, February 08, 2013 6:25 PM
>> To: Cheng-Jia Lai (chelai)
>> Cc: Wenyi Wang (wenywang); Stan Yang (stanyang); Toerless Eckert (eckert); Fred Yip (fyip)
>> Subject: New Version Notification for draft-lai-tsvwg-normalizer-00.txt
>>
>>
>> A new version of I-D, draft-lai-tsvwg-normalizer-00.txt
>> has been successfully submitted by Cheng-Jia Lai and posted to the
>> IETF repository.
>>
>> Filename:      draft-lai-tsvwg-normalizer
>> Revision:      00
>> Title:                 Normalization Marker for AF PHB Group in DiffServ
>> Creation date:         2013-02-08
>> WG ID:                 Individual Submission
>> Number of pages: 15
>> URL:             http://www.ietf.org/internet-drafts/draft-lai-tsvwg-normalizer-00.txt
>> Status:          http://datatracker.ietf.org/doc/draft-lai-tsvwg-normalizer
>> Htmlized:        http://tools.ietf.org/html/draft-lai-tsvwg-normalizer-00
>>
>>
>> Abstract:
>>    This memo describes a Normalization Marker (NM) at DiffServ (DS)
>>    nodes to normalize the distribution of DS codepoint (DSCP) markings
>>    for an Assured Forwarding (AF) Per-Hop Behavior (PHB) group.  NM is
>>    useful for traffic conditioning with Active Queue Management (AQM)
>>    when the AF PHB group is deployed for multimedia service classes that
>>    carry video packets with advanced codec technologies.  Using NM can
>>    offer an incentive that is however missing in today's ecosystem of
>>    practical deployment, i.e., when congestion occurs in the AF PHB
>>    group, the network should allow a video codec to benefit from its
>>    effort of generating finer layers of intra-flow precedence (IFP) with
>>    discardable packets in a more balanced distribution.
>>
>>
>>
>>
>> The IETF Secretariat
>>
>
> --
> ---
> Toerless Eckert, eckert@cisco.com
> Cisco NSSTG Systems & Technology Architecture
> SDN: Let me play with the network, mommy!
>



-- 
Dave Täht

Fixing bufferbloat with cerowrt: http://www.teklibre.com/cerowrt/subscribe.html