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

Mikael Abrahamsson <swmike@swm.pp.se> Fri, 20 April 2018 06:58 UTC

Return-Path: <swmike@swm.pp.se>
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 3BB6012AF84 for <tsvwg@ietfa.amsl.com>; Thu, 19 Apr 2018 23:58:37 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.301
X-Spam-Level:
X-Spam-Status: No, score=-4.301 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_MED=-2.3, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=swm.pp.se
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 ubyDaHES2kKR for <tsvwg@ietfa.amsl.com>; Thu, 19 Apr 2018 23:58:35 -0700 (PDT)
Received: from uplift.swm.pp.se (swm.pp.se [212.247.200.143]) (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 94072129C6B for <tsvwg@ietf.org>; Thu, 19 Apr 2018 23:58:35 -0700 (PDT)
Received: by uplift.swm.pp.se (Postfix, from userid 501) id 5FA2DB0; Fri, 20 Apr 2018 08:58:32 +0200 (CEST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=swm.pp.se; s=mail; t=1524207512; bh=8YGxRJBkU0hbPQbmfkT5z+DWRsGH6KPxXMCUbLCj+ZE=; h=Date:From:To:cc:Subject:In-Reply-To:References:From; b=AXYwrQwbBYRcDRwkPlxTOu7eSHZquarJJSDRGgblPYiLco/z+/FrUEQkMgVbX9qW2 hDF8LxdbJ8RjQLJ6kbHaA6FEUp5Nh/MJ4J4U4nbI/uO1YNAnf1vZuHbzjsYZXQJ7zW GnbNOhngh7mO5iKGrD5dhjvfcBO+cz4CRhSh0tVw=
Received: from localhost (localhost [127.0.0.1]) by uplift.swm.pp.se (Postfix) with ESMTP id 5D7EBAF; Fri, 20 Apr 2018 08:58:32 +0200 (CEST)
Date: Fri, 20 Apr 2018 08:58:32 +0200
From: Mikael Abrahamsson <swmike@swm.pp.se>
To: Ruediger.Geib@telekom.de
cc: tsvwg@ietf.org
In-Reply-To: <LEJPR01MB103305081F93A808ED0AF7159CB40@LEJPR01MB1033.DEUPRD01.PROD.OUTLOOK.DE>
Message-ID: <alpine.DEB.2.20.1804200849320.18650@uplift.swm.pp.se>
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> <LEJPR01MB103305081F93A808ED0AF7159CB40@LEJPR01MB1033.DEUPRD01.PROD.OUTLOOK.DE>
User-Agent: Alpine 2.20 (DEB 67 2015-01-07)
Organization: People's Front Against WWW
MIME-Version: 1.0
Content-Type: text/plain; charset="US-ASCII"; format="flowed"
Archived-At: <https://mailarchive.ietf.org/arch/msg/tsvwg/Ijk_izr7xBP26nEFtqnq50g_pr4>
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: Fri, 20 Apr 2018 06:58:37 -0000

On Fri, 20 Apr 2018, Ruediger.Geib@telekom.de wrote:

> Mikael, by "residential broadband" you mean the consumer edge device or the home gateway - a piece of equipment which today isn't located within provider premises?
>
> The direction of traffic at the residential broadband gateway is "to the Internet" and congestion is caused by sources within the home network. All of that is BYOD equipment (in some countries including the residential broadband gateway).
>
> Should that be correct, I support your idea of giving LE queuing guidance to the residential broadband gateway vendors.
>
> If your proposal is meant to cover other pieces of equipment, like Broadband Network Gateways, please clarify.

This guidance is for CP handling/mapping ingress on BNG and on peering 
routers (ISP edge), and CP based PHB ingress/egress customer-facing for 
both BNG, HGW and all other equipment handling last-hop-to-customer 
traffic and intra-customer network for BYOD non-managed networks (such as 
a residential network).

So some examples:

What should the PHB be egress on BNG -> customer

What should the CP treatment be ingress on BNG (because HGW is customer 
controlled potentially).

If BNG is doing ingress shaping for instance, what should this PHB be 
(again, customer-controlled HGW).

What is the CP treatment between ISPs when nothing is discussed regarding 
CP treatment (Internet peering default). What should ISP ingress settings 
be towards an IX LAN for instance.

What is the CP based egress PHB towards an IX.

All of this is for Internet traffic, think cat pictures, online gaming, 
OTT streaming services etc. Generic Internet traffic.

In my solution my "BNG" does ingress and egress shaping, and that's what I 
have used so far in my examples. I don't consider the HGW a trusted 
device (it often is, but not all the time).

-- 
Mikael Abrahamsson    email: swmike@swm.pp.se