Re: [Dart] [tsvwg] Comments on draft-ietf-tsvwg-rtcweb-qos-00

Brian E Carpenter <brian.e.carpenter@gmail.com> Wed, 25 June 2014 23:27 UTC

Return-Path: <brian.e.carpenter@gmail.com>
X-Original-To: dart@ietfa.amsl.com
Delivered-To: dart@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id C75D61A02EB; Wed, 25 Jun 2014 16:27:24 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2
X-Spam-Level:
X-Spam-Status: No, score=-2 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, 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 8Scw2sh1wJFN; Wed, 25 Jun 2014 16:27:23 -0700 (PDT)
Received: from mail-pd0-x231.google.com (mail-pd0-x231.google.com [IPv6:2607:f8b0:400e:c02::231]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 9B5AB1A0291; Wed, 25 Jun 2014 16:27:23 -0700 (PDT)
Received: by mail-pd0-f177.google.com with SMTP id y10so2215051pdj.8 for <multiple recipients>; Wed, 25 Jun 2014 16:27:23 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=message-id:date:from:organization:user-agent:mime-version:to:cc :subject:references:in-reply-to:content-type :content-transfer-encoding; bh=dIP8mwMt8T+GJhCTvdsJyY4Y/+N2w6IbYv5dJlC/f+M=; b=IulVlSLgfZZRVeU/rL+28yf47gbyqIHkKVD04ZtdUV22wZe9ruhXqU/aWQbJOsFTN7 PKgrOmVdNlT1JSYov48BNsZA7aCgx54ajXVwhu7ot93G6VoO6lSf2ZVhDtojnvAkXyrT cvPHm2TPct0I2Zrb4FQcuIsQCn7t6eI94pP/XxeuV7Gc9IMfP3S89TWfGNFdwDVG604B Tz6nMkUwMYgkLFwHlsRIoVz8/yinACwofdCuR/U8rFW41D+iQZdik8SuDhZeCAzuI8cG jrJAijTRjoda/h+T9i+2+iPO3AA6pYaXnyPqYw23BMiemp6PpUdERpPNSZVowIcr9axo j0fA==
X-Received: by 10.69.17.66 with SMTP id gc2mr16120057pbd.90.1403738843269; Wed, 25 Jun 2014 16:27:23 -0700 (PDT)
Received: from [192.168.178.23] (153.199.69.111.dynamic.snap.net.nz. [111.69.199.153]) by mx.google.com with ESMTPSA id qk9sm24937114pac.16.2014.06.25.16.27.21 for <multiple recipients> (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Wed, 25 Jun 2014 16:27:22 -0700 (PDT)
Message-ID: <53AB5AE1.9040306@gmail.com>
Date: Thu, 26 Jun 2014 11:27:29 +1200
From: Brian E Carpenter <brian.e.carpenter@gmail.com>
Organization: University of Auckland
User-Agent: Thunderbird 2.0.0.6 (Windows/20070728)
MIME-Version: 1.0
To: gorry@erg.abdn.ac.uk
References: <mailman.106.1403636431.23016.dart@ietf.org> <53AACD6C.3010309@erg.abdn.ac.uk>
In-Reply-To: <53AACD6C.3010309@erg.abdn.ac.uk>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: 7bit
Archived-At: http://mailarchive.ietf.org/arch/msg/dart/xEdx_YV4eXZJ_ei3rqjNw89Qq_I
Cc: dart@ietf.org, tsvwg WG <tsvwg@ietf.org>
Subject: Re: [Dart] [tsvwg] Comments on draft-ietf-tsvwg-rtcweb-qos-00
X-BeenThere: dart@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: "\"DiffServ Applied to RTP Transports discussion list\"" <dart.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dart>, <mailto:dart-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/dart/>
List-Post: <mailto:dart@ietf.org>
List-Help: <mailto:dart-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dart>, <mailto:dart-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 25 Jun 2014 23:27:24 -0000

On 26/06/2014 01:23, Gorry Fairhurst wrote:
...
>> Sure, however, my point was that simply injecting traffic marked with
>> a DSCP for a PHB that normally requires prior admission control is
>> somewhat problematic: either guarantees for already admitted flows
>> are violated or such traffic has to be dropped.
> 
> I see a potential problem here, if this becomes a default: If widely
> deployed using EF, the traffic will likely result in this DSCP being
> ignored/dropped (not given you EF properties0)or in breaking EF
> properties for other flows (which needs to be policed).

If you look at RFC3246 (the EF specification) you will find
these words:

 the rate at which EF
 traffic is served at a given output interface should be at least the
 configured rate R, over a suitably defined interval, independent of
 the offered load of non-EF traffic to that interface.

In other words, if you do not apply admission control to
EF traffic, excess traffic *will* be discarded, because EF
has a strict maximum rate.

    Brian