Re: [tsvwg] residential broadband BCP PHB and CP treatment Re: CC/bleaching thoughts for draft-ietf-tsvwg-le-phb-04

Brian E Carpenter <brian.e.carpenter@gmail.com> Sat, 21 April 2018 03:46 UTC

Return-Path: <brian.e.carpenter@gmail.com>
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 60B0512DA03 for <tsvwg@ietfa.amsl.com>; Fri, 20 Apr 2018 20:46:09 -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, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com
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 lcPRH-jSMriD for <tsvwg@ietfa.amsl.com>; Fri, 20 Apr 2018 20:46:07 -0700 (PDT)
Received: from mail-pf0-x22b.google.com (mail-pf0-x22b.google.com [IPv6:2607:f8b0:400e:c00::22b]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 5A073124BFA for <tsvwg@ietf.org>; Fri, 20 Apr 2018 20:46:07 -0700 (PDT)
Received: by mail-pf0-x22b.google.com with SMTP id j5so5091385pfh.2 for <tsvwg@ietf.org>; Fri, 20 Apr 2018 20:46:07 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=sender:subject:to:cc:references:from:message-id:date:user-agent :mime-version:in-reply-to:content-language:content-transfer-encoding; bh=+RH4fXd3mQ+qCG9IAwW0Vn78At9TT8duiBstOdxEvog=; b=i8S9Z0cifd8PeuDr7GG4jnseYVBNhrpNNVp6rftuaOfzAObxBCVv4mEUCTyDCUQkH7 j5jVFPIfWa7V1JAWvr681+M9YfJV0aJTfPZIbPIldMMmaezM8aazBjyaXMGI8lK3CMLq JWqMedFal02pSOJUNqYi09NnIwrC4SnQa5ssnIkNPwWusk8zuUWrYNmXLzK78Rn9pAAV HE5VZpP2i2fUsoPD1uYASOAF01vI1WYeVSzsEsnW7+TH3y8HzUW0Il/XYqFXonCVmBWI 85CvHi8ndo9Kg+OEP2dLJ9YI2jGov5nzG6nPTAxuvRignjbjszi7JBY6Ra9B/v3P2X5N AzOA==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:sender:subject:to:cc:references:from:message-id :date:user-agent:mime-version:in-reply-to:content-language :content-transfer-encoding; bh=+RH4fXd3mQ+qCG9IAwW0Vn78At9TT8duiBstOdxEvog=; b=r9laoYZ5p2ZfTXraAyyacFc3zlXyeqKBSm/mq3edf6Oz7+vQXVL1TQ5MEp5OWcpZnP Uu5j3OIrq7dwb2NWM0qAzqmoiRFNMC/jDieku/NUcgMh6/PJ4gWwRqQ4f9TyOY1Gk/Ai UUuld078Pzuq3aMTMjBC6sKkd6nkV+qbzl5uwTWUCcJGs8PEqvaiSRoViI6OPnoVxgT4 MSL2FxG+AjE48xoaaE+PHu9i5hRYdn6WRFT9inKnINSjOfOldBDRvQMOOQyuRMsLu0xR 2Aj8WCMvSph+ds9Qex5ECB0PGcpdVverVhLBt74Ah8duBhDTsApphZmUfTPSgyw7qZL4 iwlA==
X-Gm-Message-State: ALQs6tAeDqXPmL2PPEFcgIUFAA+2BYlcyQYTZZvndbzWSOTWMqCWGRGx GEFopUlWl4xihjVov0k38Z4TVQ==
X-Google-Smtp-Source: AIpwx4+zbTv5LAFgA6SLpAJSbu0f38YNUDacWOTwH2YYR53J84sLu1+uEUYFFWSMeH0mx4oQ5sMw3w==
X-Received: by 10.98.254.17 with SMTP id z17mr11816966pfh.105.1524282366592; Fri, 20 Apr 2018 20:46:06 -0700 (PDT)
Received: from [192.168.178.26] ([118.149.104.73]) by smtp.gmail.com with ESMTPSA id x3sm16755676pff.87.2018.04.20.20.46.04 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Fri, 20 Apr 2018 20:46:05 -0700 (PDT)
Sender: Brian Carpenter <becarpenter46@gmail.com>
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> <adf6493b-45fd-9d0c-70f5-5d343cad22dd@gmail.com> <alpine.DEB.2.20.1804200635060.18650@uplift.swm.pp.se> <fbc0e011-6e37-c0ee-c90e-191349f75cac@gmail.com> <alpine.DEB.2.20.1804200823330.18650@uplift.swm.pp.se>
From: Brian E Carpenter <brian.e.carpenter@gmail.com>
Message-ID: <943a0db3-5aa6-0f09-c13b-e69a3f62ef5f@gmail.com>
Date: Sat, 21 Apr 2018 15:46:13 +1200
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:52.0) Gecko/20100101 Thunderbird/52.7.0
MIME-Version: 1.0
In-Reply-To: <alpine.DEB.2.20.1804200823330.18650@uplift.swm.pp.se>
Content-Type: text/plain; charset="utf-8"
Content-Language: en-US
Content-Transfer-Encoding: 7bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/tsvwg/LTsc8-xaQUPxBpbD5OXv8m0_CZs>
Subject: Re: [tsvwg] residential broadband BCP PHB and CP treatment Re: 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: Sat, 21 Apr 2018 03:46:09 -0000

Hi Mikael,

On 20/04/2018 18:28, Mikael Abrahamsson wrote:
> On Fri, 20 Apr 2018, Brian E Carpenter wrote:
> 
>> Mikael,
>>
>>> If CP == 1 goto queueLE;
>>
>> Sure, if IANA assigns the code point that the draft requests.
> 
> Of course.
> 
>>> I would
>>> like whatever we come up with to be RFC8325 compatible and at least not
>>> conflicting with it.
>>
>> If you mean 8325 *as updated by draft-ietf-tsvwg-le-phb* we are fine.
>> But it will be very important to get that update into everybody's head.
> 
> Can you please enlighten me why you think it's ok to put CS1 into the same 
> queue as LE (background, as per 8325), but it's not ok to remap CP 
> CS1->LE?

Because RFC2474 clearly states that CS1 gets precedence over DF (=CS0).
(Which in fact goes back to RFC791 and RFC1349.)

"PHBs selected by a Class Selector Codepoint
 SHOULD give packets a probability of timely forwarding that is not
 lower than that given to packets marked with a Class Selector
 codepoint of lower relative order..." (RFC2474 section 4.2.2.2)

None of the other RFCs that use the CS1 codepoint for LE have formally
updated RFC2474; in other words they all violate the SHOULD above.
Specifically, RFC4594 did not formally update RFC2474.

A user who sets CS1 because they want better treatment than default
is doing exactly what an IETF standard says. So if you see CS1 on
incoming traffic, you have no idea whether the user wanted Precedence 1
or LE, unless you have a specific understanding with that user.

To me that means that the correct default behaviour is to map CS1 to
DF, as a compromise. Of course, if you *know* whether the user is
relying on RFC2474 or on RFC4594, you can configure the correct
mapping. But that's always true of diffserv.

   Brian

> 
> Because my proposal for the second scenario in my earlier email would 
> otherwise have been (adding remap of CS1 -> LE):
> 
> If CP == 1 then pass; # allow LE
> If CP == 8 then set CP = 1; # remap CS1 to LE
> If CP => 2 then set CP = 0; # set 2-63 to 0
> 
> I think this is an important distinction and we need to decide how to 
> handle this case. Is CS1 more likely to be equivalent to BE or LE? Because 
> in this scenario, it's going into one of these two. What's the least harm?
>