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

<Ruediger.Geib@telekom.de> Fri, 20 April 2018 06:40 UTC

Return-Path: <Ruediger.Geib@telekom.de>
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 4C38212D874 for <tsvwg@ietfa.amsl.com>; Thu, 19 Apr 2018 23:40:29 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.3
X-Spam-Level:
X-Spam-Status: No, score=-4.3 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] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=telekom.de header.b=rezu/Ql1; dkim=pass (1024-bit key) header.d=telekom.onmicrosoft.de header.b=h1v/1KkU
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 JBIIYItlRey6 for <tsvwg@ietfa.amsl.com>; Thu, 19 Apr 2018 23:40:26 -0700 (PDT)
Received: from mailout33.telekom.de (MAILOUT33.telekom.de [194.25.225.145]) (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 38178129C6B for <tsvwg@ietf.org>; Thu, 19 Apr 2018 23:40:26 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=telekom.de; i=@telekom.de; q=dns/txt; s=dtag1; t=1524206426; x=1555742426; h=from:to:cc:subject:date:message-id:references: in-reply-to:content-transfer-encoding:mime-version; bh=y2aANpn57dbfyafbYVVtYe/zQKvFrc1xOsL+HCi2sa0=; b=rezu/Ql1Di3S7GZ0bxnlFUOusPoswNT7q190rOHxrftEZM1PNhLp+dG8 vaX4GfI388g5r89KkwrAn0j0/gHg5EfpbMmm4aUWc+By7qv3gYoyjDkPC C3a7om4RovBHOjqpFbu96RDaS8HyXYHpu/LzWdFNq3ZKLM5/FuWxVQiZj daz6J5gYeoJTs4XXTVlaSv7Xz/oIQvk50Jcg5BFvs2P1ma3bhDiWSzlKT iyW2ohSTHw26Us7uWwPk7/QD5tF7yhr13PrTKAR4VDWsxAtOYfiMMt0bv gOrKk8jDuSW+J/wGTYpXMtw0YlzITk596vo0oN+kJmdzhXGNpL7WmAOOO g==;
Received: from qdezc2.de.t-internal.com ([10.171.255.37]) by MAILOUT31.dmznet.de.t-internal.com with ESMTP/TLS/DHE-RSA-AES256-GCM-SHA384; 20 Apr 2018 08:40:24 +0200
X-IronPort-AV: E=Sophos;i="5.48,405,1517871600"; d="scan'208";a="790669393"
Received: from he105762.emea1.cds.t-internal.com ([10.169.118.58]) by qde0ps.de.t-internal.com with ESMTP/TLS/AES256-SHA; 20 Apr 2018 08:40:23 +0200
Received: from HE105654.EMEA1.cds.t-internal.com (10.169.118.86) by HE105762.emea1.cds.t-internal.com (10.169.118.58) with Microsoft SMTP Server (TLS) id 15.0.1365.1; Fri, 20 Apr 2018 08:40:23 +0200
Received: from HE106564.emea1.cds.t-internal.com (10.171.40.16) by HE105654.EMEA1.cds.t-internal.com (10.169.118.86) with Microsoft SMTP Server (TLS) id 15.0.1365.1 via Frontend Transport; Fri, 20 Apr 2018 08:40:23 +0200
Received: from GER01-FRA-obe.outbound.protection.outlook.de (51.4.80.22) by O365mail01.telekom.de (172.30.0.234) with Microsoft SMTP Server (TLS) id 15.0.1365.1; Fri, 20 Apr 2018 08:40:03 +0200
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=telekom.onmicrosoft.de; s=selector1-telekom-onmicrosoft-de; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version; bh=y2aANpn57dbfyafbYVVtYe/zQKvFrc1xOsL+HCi2sa0=; b=h1v/1KkU8K8WEuhiFVclHlo2NvQ69z6GRxr3yAGOfVxAEvjPbG2YM3lKhBLM5cZu7BSSsqUYiPz/F1R8P0syADpLBuejuAU+0k3fjhLDWfVXqB1Pw9JwWgsqbVdQ+RHodKAgYg8QQA6iHQtqOsTlnSujLZnhExU144TCPXNO9JQ=
Received: from LEJPR01MB1033.DEUPRD01.PROD.OUTLOOK.DE (10.158.147.8) by LEJPR01MB1036.DEUPRD01.PROD.OUTLOOK.DE (10.158.147.11) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA384_P256) id 15.20.696.12; Fri, 20 Apr 2018 06:40:22 +0000
Received: from LEJPR01MB1033.DEUPRD01.PROD.OUTLOOK.DE ([fe80::608d:dfcb:f6c3:8f9]) by LEJPR01MB1033.DEUPRD01.PROD.OUTLOOK.DE ([fe80::608d:dfcb:f6c3:8f9%14]) with mapi id 15.20.0696.013; Fri, 20 Apr 2018 06:40:22 +0000
From: Ruediger.Geib@telekom.de
To: swmike@swm.pp.se
CC: tsvwg@ietf.org
Thread-Topic: [tsvwg] residential broadband BCP PHB and CP treatment Re: CC/bleaching thoughts for draft-ietf-tsvwg-le-phb-04
Thread-Index: AQHT2GLHWOW2tNrXIkacJcBg/Z0qH6QJKz2w
Date: Fri, 20 Apr 2018 06:40:22 +0000
Message-ID: <LEJPR01MB103305081F93A808ED0AF7159CB40@LEJPR01MB1033.DEUPRD01.PROD.OUTLOOK.DE>
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>
In-Reply-To: <alpine.DEB.2.20.1804200635060.18650@uplift.swm.pp.se>
Accept-Language: en-US
Content-Language: de-DE
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
authentication-results: swm.pp.se; dkim=none (message not signed) header.d=none;swm.pp.se; dmarc=none action=none header.from=telekom.de;
x-originating-ip: [164.19.3.197]
x-ms-publictraffictype: Email
x-microsoft-exchange-diagnostics: 1; LEJPR01MB1036; 7:s5SZPm82zDtAHPt8ylEH6C3f14N1qXbhmQ2eWNj0PbQiA1ndy/JjlxjX2rupXYuYottK1NXE/N5yrBB5UEMgdyHNs8RCcOYKTcjWEfu+8T4STWRPAPlNq0Nvzz19evLxawBi6egIdPGchNAFQhIc99HI0f1cyiD2O50ZiPWNiLmwYNrh2yQcK3ENJN5sFsKlHQlMcF+Uc5HoMPZ94hR6ObO+kxRtgq7EAYYpwXv/030HAEfxFE88vY/HmXBAZRkU
x-ms-exchange-antispam-srfa-diagnostics: SOS;
x-microsoft-antispam: UriScan:; BCL:0; PCL:0; RULEID:(7020095)(4652020)(5600026)(4534165)(4627221)(201703031133081)(201702281549075)(2017052603328)(7153060)(7193020); SRVR:LEJPR01MB1036;
x-ms-traffictypediagnostic: LEJPR01MB1036:
x-microsoft-antispam-prvs: <LEJPR01MB103643DE33E6AA0263E632729CB40@LEJPR01MB1036.DEUPRD01.PROD.OUTLOOK.DE>
x-exchange-antispam-report-test: UriScan:;
x-exchange-antispam-report-cfa-test: BCL:0; PCL:0; RULEID:(6040522)(2401047)(8121501046)(5005006)(3231232)(944501391)(52105095)(93006095)(93001095)(10201501046)(3002001)(6041310)(201703131423095)(201702281528075)(20161123555045)(201703061421075)(201703061406153)(20161123564045)(20161123560045)(20161123562045)(20161123558120)(6072148)(201708071742011); SRVR:LEJPR01MB1036; BCL:0; PCL:0; RULEID:; SRVR:LEJPR01MB1036;
x-forefront-prvs: 0648FCFFA8
x-forefront-antispam-report: SFV:NSPM; SFS:(10009020)(376002)(396003)(39380400002)(39860400002)(366004)(346002)(252514010)(7736002)(305945005)(316002)(66066001)(2906002)(476003)(446003)(86362001)(11346002)(5250100002)(6916009)(478600001)(3660700001)(72206003)(76176011)(52396003)(33656002)(26005)(3846002)(3280700002)(75402003)(81166006)(8676002)(5660300001)(59450400001)(55016002)(74482002)(9686003)(186003)(2900100001)(102836004)(561944003)(7696005)(53936002)(6116002)(93886005)(4326008)(8936002)(217873001); DIR:OUT; SFP:1101; SCL:1; SRVR:LEJPR01MB1036; H:LEJPR01MB1033.DEUPRD01.PROD.OUTLOOK.DE; FPR:; SPF:None; LANG:en; MLV:sfv;
x-microsoft-antispam-message-info: BGkEsTnydZIDy4Jb1nks/pirA9XKhy7/+ZWMlPI8bgxFil4URGuZerzeVvYluCJKJadEyep80UqOj5jvDavxUu+w+Rj6WwFIJ51zF9EV2N0mJTk16yRDWQlBM6QVW3NIvxSFMbkQEMVm3S/SUm4AbW+lK6od7wmiH4UgYhL1hHt7r7rTWommHWqubx65Bq4E
spamdiagnosticoutput: 1:99
spamdiagnosticmetadata: NSPM
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-MS-Office365-Filtering-Correlation-Id: 4ba03a4c-e7d4-496a-81d6-08d5a6899771
X-MS-Exchange-CrossTenant-Network-Message-Id: 4ba03a4c-e7d4-496a-81d6-08d5a6899771
X-MS-Exchange-CrossTenant-originalarrivaltime: 20 Apr 2018 06:40:22.3540 (UTC)
X-MS-Exchange-CrossTenant-fromentityheader: Hosted
X-MS-Exchange-CrossTenant-id: bde4dffc-4b60-4cf6-8b04-a5eeb25f5c4f
X-MS-Exchange-Transport-CrossTenantHeadersStamped: LEJPR01MB1036
X-OriginatorOrg: telekom.de
Archived-At: <https://mailarchive.ietf.org/arch/msg/tsvwg/318xlONZnmYGkRdnq8kYiKBhPKw>
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:40:29 -0000

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. 

Regards,

Ruediger

-----Ursprüngliche Nachricht-----
Von: tsvwg [mailto:tsvwg-bounces@ietf.org] Im Auftrag von Mikael Abrahamsson

Ok, so just to make things perfectly clear. I am trying to create a BCP for residential broadband for PHB and CP treatment. This means BYOD, no contracts, no knowledge. This includes mobile, wifi, wireline etc. I would like whatever we come up with to be RFC8325 compatible and at least not conflicting with it. My goal is to go to the operator community and try to get as wide adoption of this as possible. If I succeed, this will be the new default behaviour for residential broadband access.

So, from this discussion it seems to me that what we would like to happen that would do least harm is this pseudocode.

CP is decimal representation of diffserv CP 0 to 63.

If CP => 0 then pass; # do not bleach anything

The PHB is set up like this:

If CP == 0 goto queueBE;
If CP == 1 goto queueLE;
If CP => 2 goto queueRest;

The queues are set up to drain with current ratios:

queueBE 	10
queueRest 	10
queueLE 	1

... or something along those lines, meaning queueLE gets ~5% of the capacity when the other queues are full.

If operator wants to bleach, then pseudocode changes to:

If CP == 1 then pass; # allow LE
If CP => 2 then set CP = 0; # set 2-63 to 0

The PHB is set up like this:

If CP == 1 goto queueLE;
goto queueBE;

The queues are set up to drain with current ratios:

queueBE 	20
queueLE 	1

This sums up into roughly same thing but just 2 queues and LE gets ~5%.

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