Re: [tsvwg] CC/bleaching thoughts for draft-ietf-tsvwg-le-phb-04

"Bless, Roland (TM)" <roland.bless@kit.edu> Mon, 23 April 2018 09:49 UTC

Return-Path: <roland.bless@kit.edu>
X-Original-To: tsvwg@ietfa.amsl.com
Delivered-To: tsvwg@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 53EE01201FA for <tsvwg@ietfa.amsl.com>; Mon, 23 Apr 2018 02:49:52 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.201
X-Spam-Level:
X-Spam-Status: No, score=-4.201 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
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 M4ktXMo8og4J for <tsvwg@ietfa.amsl.com>; Mon, 23 Apr 2018 02:49:50 -0700 (PDT)
Received: from iramx2.ira.uni-karlsruhe.de (iramx2.ira.uni-karlsruhe.de [141.3.10.81]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id CC4771200A0 for <tsvwg@ietf.org>; Mon, 23 Apr 2018 02:49:49 -0700 (PDT)
Received: from i72vorta.tm.uni-karlsruhe.de ([141.3.71.26] helo=i72vorta.tm.kit.edu) by iramx2.ira.uni-karlsruhe.de with esmtp port 25 iface 141.3.10.81 id 1fAY6U-0001fm-Sc; Mon, 23 Apr 2018 11:49:46 +0200
Received: from [IPv6:::1] (ip6-localhost [IPv6:::1]) by i72vorta.tm.kit.edu (Postfix) with ESMTPS id D1563420111; Mon, 23 Apr 2018 11:49:46 +0200 (CEST)
To: Mikael Abrahamsson <swmike@swm.pp.se>
Cc: tsvwg@ietf.org
References: <20180406160344.xwfqgzhzfto56jhq@faui48f.informatik.uni-erlangen.de> <LEJPR01MB1033F43509F08701B2B5EA1D9CBF0@LEJPR01MB1033.DEUPRD01.PROD.OUTLOOK.DE> <82d646b7-d475-64d6-9f0b-f75e3daeeaca@gmail.com> <20180410090033.xkwsyfbfardg4pwx@faui48f.informatik.uni-erlangen.de> <ddac784e-3a88-c82d-0ed5-3816bffa2d72@gmail.com> <20180412023305.6nwyoway2m2exy2c@faui48f.informatik.uni-erlangen.de> <LEJPR01MB10334C794BDA7E125917576E9CBC0@LEJPR01MB1033.DEUPRD01.PROD.OUTLOOK.DE> <alpine.DEB.2.20.1804190826550.18650@uplift.swm.pp.se> <d8c2ca1b-aa78-9f96-2fd8-e089cf4fb5b3@kit.edu> <alpine.DEB.2.20.1804191243340.18650@uplift.swm.pp.se>
From: "Bless, Roland (TM)" <roland.bless@kit.edu>
Organization: Institute of Telematics, Karlsruhe Institute of Technology
Message-ID: <db3c3900-f4f1-3e5a-01dc-ed5d13118187@kit.edu>
Date: Mon, 23 Apr 2018 11:49:46 +0200
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:52.0) Gecko/20100101 Thunderbird/52.7.0
MIME-Version: 1.0
In-Reply-To: <alpine.DEB.2.20.1804191243340.18650@uplift.swm.pp.se>
Content-Type: text/plain; charset="utf-8"
Content-Language: en-GB
Content-Transfer-Encoding: 8bit
X-ATIS-AV: ClamAV (iramx2.ira.uni-karlsruhe.de)
X-ATIS-Timestamp: iramx2.ira.uni-karlsruhe.de 1524476987.003483958
Archived-At: <https://mailarchive.ietf.org/arch/msg/tsvwg/RUniixsztOhbFdfG2pV9qKpu43U>
Subject: Re: [tsvwg] CC/bleaching thoughts for draft-ietf-tsvwg-le-phb-04
X-BeenThere: tsvwg@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: Transport Area Working Group <tsvwg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/tsvwg>, <mailto:tsvwg-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/tsvwg/>
List-Post: <mailto:tsvwg@ietf.org>
List-Help: <mailto:tsvwg-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/tsvwg>, <mailto:tsvwg-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 23 Apr 2018 09:49:52 -0000

Hi Mikael,

Am 19.04.2018 um 12:52 schrieb Mikael Abrahamsson:
> On Thu, 19 Apr 2018, Bless, Roland (TM) wrote:
> 
>> Ok, so _bleaching_ for me would be to set the DSCP to 0. The subsequent
> 
> Ok, what should I call the following (all values decimal for the 6 DSCP
> CP bits)
> 
> Look at diffserv CP values 0-63.
> If CP in range 2-63, SET CP=0
> If CP == 1 pass unchanged
> If CP == 0 pass unchanged
> 
> This bleaches 2-63 to 0 and leaves 1 unchanged. What do we call this?

This is correctly stated, so I would always qualify bleaching with
the respective DSCPs that are bleached.

>> This is a bit confusing. What do you mean by "bleach" here, treat
>> LE as BE? Remarking of DSCPs is a somewhat orthogonal problem since
> 
> For me there are two things an ISP does depending on DSCP values. It has
> a policy that (might) inspect CP values and change them. It also has a
> PHB depending on the CP values.
> 
> The simplest policy is "SET CP = 0 on all packets". This seems to be
> what you call bleaching.

Yep.

>> Diffserv requires a flexible mapping from DSCP -> PHB. So my
>> recommendation is to remark CS1 to LE for domains that formerly used
>> CS1 as LE codepoint. Otherwise, you cannot be sure whether CS1 actually
>> is CS1 in its original meaning or whether it should be treated as LE.
>> Removing that ambiguity is the main motivation for my LE PHB draft.
> 
> If the domain previously just bleached everything and now wants to
> deploy support for LE (both allowing the CP to enter the ISP network and
> also creating different PHB for LE vs BE), what should it do regarding CS1?

> Saying "it depends" is not helpful. This is the Internet with billions
> of devices and users. What should be the default behaviour for
> non-managed devices run by normal people that they bought from the
> electronics store. I am not talking about managed enterprise networks
> etc. I am talking about the most common network out there, the "oh, I
> need Internet access to watch cat pictures on my own device and it's
> default out of box configured from DSCP point of view".

I think that Ruediger also stated that it depends on what was previously
the semantics of CS1 at that particular link. The problem is indeed at
app level, since there may be some apps using CS1 in LE semantics and
some probably in genuine CS semantics. So the choice is to map CS1->LE
or to bleach it unless you want to support genuine CS1. As a provider
it is your own risk and I think one could monitor the traffic volume.
If it is negligible, then using BE or elevated services for CS1 is no
problem, but otherwise this traffic may adversely affect other BE traffic.

>>> 3. Bleach rest to BE.
>>
>> What is the rest?
> 
> CP between 2 and 63. Not 0 and 1.

Ok, that is much more precise.

Regards
 Roland