Re: [tsvwg] I-D Action: draft-ietf-tsvwg-nqb-19.txt - 7. Example Use Cases

Ruediger.Geib@telekom.de Tue, 10 October 2023 12:03 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 331A2C14F721 for <tsvwg@ietfa.amsl.com>; Tue, 10 Oct 2023 05:03:36 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -7.104
X-Spam-Level:
X-Spam-Status: No, score=-7.104 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIMWL_WL_HIGH=-0.001, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, RCVD_IN_DNSWL_HI=-5, RCVD_IN_MSPIKE_H5=0.001, RCVD_IN_MSPIKE_WL=0.001, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, SPF_HELO_NONE=0.001, SPF_NONE=0.001, T_SCC_BODY_TEXT_LINE=-0.01, URIBL_DBL_BLOCKED_OPENDNS=0.001, URIBL_ZEN_BLOCKED_OPENDNS=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=telekom.de
Received: from mail.ietf.org ([50.223.129.194]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id eAlrpCCugGZt for <tsvwg@ietfa.amsl.com>; Tue, 10 Oct 2023 05:03:31 -0700 (PDT)
Received: from mailout41.telekom.de (mailout41.telekom.de [194.25.225.151]) (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 D6086C1516E1 for <tsvwg@ietf.org>; Tue, 10 Oct 2023 05:03:28 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=telekom.de; i=@telekom.de; q=dns/txt; s=dtag1; t=1696939411; x=1728475411; h=from:to:cc:subject:date:message-id:references: in-reply-to:content-transfer-encoding:mime-version; bh=7dURPfxx1bw4usYPR1qLsDZlxjbnIJu/dGlWhbOFssk=; b=JYtbG0Adf237ubXrcJm1RipgeAAxr5r3rj9D3jQw30cBxEwnOLgpR5SX Ebl1NCXHFjRrlhNwfajhEoyw8Vf0y0ZZOf5j78AT9G0KPOeL8IBIJAQuG i7n4uFMe6U+1w93busCqzGisdHimW3ZJLkC4iDq5WThnCY/NxJnaYW86z pt7uTDSMNK+r5Pc2Mdb4pp8dF6Ge+XyGyuM1KwtMkvH2OoFWk8+c0ysJn EZgWbkNjKApA0Upom2ore1St39tuBwkaOns2lZPDTiE88nKJeALyr4jEZ WJfuAvbMDtNHRuJFZb9L+cwPc5oomb+u8OSZFwQIUMqSikLWVLiBd4dpp A==;
Received: from qdec94.de.t-internal.com ([10.171.255.41]) by mailout41.dmznet.de.t-internal.com with ESMTP/TLS/ECDHE-RSA-AES128-GCM-SHA256; 10 Oct 2023 14:03:26 +0200
IronPort-SDR: 65253d8e_hhvKcQ5a8E7iNiJZK6QO4WHSxpmGyZtTQSdo8o0nJXUASiZ dtWveSQbGzlKuaniBEujOSetUvY23RNH++HymUA==
X-IronPort-AV: E=Sophos;i="6.03,212,1694728800"; d="scan'208";a="813790686"
X-MGA-submission: MDHcVZ/ZzRX4KFby5oP6uukg1ffARAYbzicz404M/jE5yhCK4+xZWO2Dv6tYEnFdcIe8g/F7UeowjD7Sgt1IDHqITFj0cItF3hNA4RDKoINZcfY2PPYLSko6gEyW5+KznmhAmBAN8Vav8jxuXLKuEstSLuFeRsoRPfATdyZLXEIRkg==
Received: from he101393.emea1.cds.t-internal.com ([10.169.119.197]) by QDEC97.de.t-internal.com with ESMTP/TLS/ECDHE-RSA-AES128-GCM-SHA256; 10 Oct 2023 14:03:25 +0200
Received: from HE126308.emea1.cds.t-internal.com (10.169.119.205) by HE101393.emea1.cds.t-internal.com (10.169.119.197) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.2.1118.37; Tue, 10 Oct 2023 14:03:25 +0200
Received: from HE104281.emea1.cds.t-internal.com (10.169.119.195) by HE126308.emea1.cds.t-internal.com (10.169.119.205) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.2.1118.37; Tue, 10 Oct 2023 14:03:25 +0200
Received: from HE102772.emea1.cds.t-internal.com (10.171.40.44) by HE104281.emea1.cds.t-internal.com (10.169.119.195) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.2.1118.37 via Frontend Transport; Tue, 10 Oct 2023 14:03:25 +0200
Received: from DEU01-FR2-obe.outbound.protection.outlook.com (104.47.11.169) by O365mail09.telekom.de (172.30.0.241) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.2.1118.37; Tue, 10 Oct 2023 14:03:24 +0200
ARC-Seal: i=1; a=rsa-sha256; s=arcselector9901; d=microsoft.com; cv=none; b=MwsPiROm9c1Q/nu9mvCVXxQhD13xiYH5J1qGN7n8eKkKAdQSq+KwioyJcEY3Xtg3LQ+s/oVjlTf+IbQCw/eAs4otdNHcoU0vmJjz1a1IQnKCkz4x4wbJCWQU7O/xu9xz5EYmWbpyFyxaHY91yRjGWkdxhAOIektpb/GV9F93lbhp2qML/3c+vfOdRbf+aqFoujmNghRImtbExGqOD6W+LutIO4Pt1FjOg6XaHieQmPenVXpRSzyiTBn9LBaN20sLHzh6yAS+dkCi+5SY1qTwhv7bo8p4uhZZIO3vjmEUIIiboR/ddHSvs2Tjk0G6TvRCpBI7K+uj1NrckOmY2U2hEQ==
ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=microsoft.com; s=arcselector9901; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-AntiSpam-MessageData-ChunkCount:X-MS-Exchange-AntiSpam-MessageData-0:X-MS-Exchange-AntiSpam-MessageData-1; bh=7dURPfxx1bw4usYPR1qLsDZlxjbnIJu/dGlWhbOFssk=; b=mgjdoKyHx4NT9YRgMvIAAVdgjNQLA5t9rjKMdRFBgumwDq2v3tla7fgpreYTLVJ8sKb2cylAz1wZxJwD8xkONP+DpwTGtro8+1KkTUtGY/RLKtCEVkxl87uxJvfJd2yfv2dRD/+x2IaniWEfuaYHtxblUxw9RrniBgWekuo3xZ4IYPj7Z6QwmvHqoMKj4Zsb6KY1K03mgwniwuzFsh6/N4nao2M36V6yfi62UwcQQxNa4Ch/oquVTIj46Ni/qzFI0nSxTv67H5cE4RhTheUzUQUjHuXYWRhs56zxswx/oa2/W9+CWxzpQA4nSmS5owAn8HZHueWSGGfMVlnzuNviBw==
ARC-Authentication-Results: i=1; mx.microsoft.com 1; spf=pass smtp.mailfrom=telekom.de; dmarc=pass action=none header.from=telekom.de; dkim=pass header.d=telekom.de; arc=none
Received: from FR2P281MB1527.DEUP281.PROD.OUTLOOK.COM (2603:10a6:d10:8b::11) by BEZP281MB2327.DEUP281.PROD.OUTLOOK.COM (2603:10a6:b10:45::8) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.6863.38; Tue, 10 Oct 2023 12:03:23 +0000
Received: from FR2P281MB1527.DEUP281.PROD.OUTLOOK.COM ([fe80::417:87fc:d537:1ece]) by FR2P281MB1527.DEUP281.PROD.OUTLOOK.COM ([fe80::417:87fc:d537:1ece%4]) with mapi id 15.20.6863.032; Tue, 10 Oct 2023 12:03:23 +0000
From: Ruediger.Geib@telekom.de
To: g.white@cablelabs.com
CC: tsvwg@ietf.org
Thread-Topic: [tsvwg] I-D Action: draft-ietf-tsvwg-nqb-19.txt - 7. Example Use Cases
Thread-Index: AQHZxGXJpsxuy5d+vEi3SzYla5TsNrAE5xaAgD5wIFA=
Date: Tue, 10 Oct 2023 12:03:23 +0000
Message-ID: <FR2P281MB152733EF549DC43BE4CB52C09CCDA@FR2P281MB1527.DEUP281.PROD.OUTLOOK.COM>
References: <169039129927.3244.8784605239288349316@ietfa.amsl.com> <FR2P281MB1527222BE1ECC3E66F22F8569C0AA@FR2P281MB1527.DEUP281.PROD.OUTLOOK.COM> <8206ADBB-5163-43DC-8BC4-F7A166E85B45@cablelabs.com>
In-Reply-To: <8206ADBB-5163-43DC-8BC4-F7A166E85B45@cablelabs.com>
Accept-Language: de-DE, en-US
Content-Language: de-DE
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
authentication-results: dkim=none (message not signed) header.d=none;dmarc=none action=none header.from=telekom.de;
x-ms-publictraffictype: Email
x-ms-traffictypediagnostic: FR2P281MB1527:EE_|BEZP281MB2327:EE_
x-ms-office365-filtering-correlation-id: 26ccf1ee-e8e1-49eb-1979-08dbc988e719
x-ms-exchange-senderadcheck: 1
x-ms-exchange-antispam-relay: 0
x-microsoft-antispam: BCL:0;
x-microsoft-antispam-message-info: 6zfpYdqW7mdm9huwF5+ZA2qjUWoXzJIRfXKO7gHdgxB+6dzGERKUiCT0A0gisZSGLEfLgFtvOx7DcCr5t3xGCucqhuvfsyGOThMET5dE9PT0/IaGb2KkM/MqE1gWGj6TmO72Gt+Q8C63WqayyhxuR9m5YtjhZEAKvy6CmRLPulx6lm7ceQtMmiDWDnwLvSdycO220UUFPfrouOdL15nV/nx05a7NIX/iD71jwB9Iu3XH+3IYmHk+Qex0r6qdUc7zuFPzvYU9D+qZrF8kVfkUF7Cekrz8JOfajMwrh4fqpDa1xgke6yPew8ZRhjb6AVvgpo5BW9gUIYZoh7z99CUUfpuWZKdIDtNzI3w8lzxS2tinnbjDmo1ESWMaeCEXlvpvfkz5U88e9i+7yc8ren8Xcw5+zSDXr8AWFFqbeQYCLYqQbCjQWvidSmGcPielxxZtQhGBM+80a7X4YzhdNPvyO+jmTKR746NU58kiFbkVFS4RQ0q1SO2TG+5tHP+1/KpcMKJ81Eh1R1l1xXeyAMbtXYqYOMjoHZXWw/rv0ykpCGrHYXS/6hvSwR7T/jrf5amqjPjubQ8Yabuxjj5mQ/yIbu3unzRVn4lxgs2GwouffcW7eUMpe/XYbofIBrIIDZyPHwGF5bciyDE/HhtpXL5EZgLqsGBYq1yhlfEqGWxd7gMN7ZCxD0x67nYMUrG4UL5P
x-forefront-antispam-report: CIP:255.255.255.255; CTRY:; LANG:en; SCL:1; SRV:; IPV:NLI; SFV:NSPM; H:FR2P281MB1527.DEUP281.PROD.OUTLOOK.COM; PTR:; CAT:NONE; SFS:(13230031)(396003)(39860400002)(346002)(366004)(136003)(376002)(230922051799003)(1590799021)(64100799003)(451199024)(186009)(1800799009)(66899024)(1580799018)(2906002)(85202003)(33656002)(86362001)(85182001)(122000001)(82960400001)(55016003)(38100700002)(38070700005)(26005)(4326008)(8936002)(8676002)(66574015)(966005)(71200400001)(9686003)(6506007)(7696005)(41300700001)(66446008)(66476007)(6916009)(64756008)(66556008)(66946007)(76116006)(83380400001)(316002)(5660300002)(478600001)(52536014); DIR:OUT; SFP:1101;
x-ms-exchange-antispam-messagedata-chunkcount: 1
x-ms-exchange-antispam-messagedata-0: 6soEkUu6Y8x8HAixEvqD0yoU+LqHkadMVGKunzUsiiqJvDX0TFdyoaJZzey6xGnjOiKN6nEpAgGWf9XJdL4w13e5AJuq/I0vMmsOv2/DIDu/lmx2zrAKgEsfoQJaRyhuB+bO5kFwO06z78TwdJtaXq6kN0B1UuCRMwE+b2pTIeZCP5G0WW9C6TKdCQFu4F66yUmGhuHh1Zb8NQ0b2vaMn/URAokUGE63sjUp8xadCo8zanzEzFB1GEh/EboCwtb8lmID5RXgVUvgiaDCoqqilgez74VVSOTchy0dvU5DMzrobvO09ahmbIJkUkZ/i7hpyEO+g7C1KG659U/LlpwCTkReb9w64n5xr8Y0fyo92UqycHo5lzb2d4S7aBDFy7HLyRT14Nl7vSmpVfMofBTJU6V6cLOqCBAUIKIJQ6Mon8pNhGuMBUqL2niPuX9WGdz4cclLaMWh+IpDVXfVTNha2l/aDL3Ika1RBj/QD/DMKUrkja3C7HTyR04xSipQUbbRxqgahqqctdeNFIilFNuX2vezDSYKXzNynkhLsA1tNpgCQoYw6S5uFsOb8S2uD8ibUN89ldBv+/u12MkrB4PRZ+RhEc5ZW5cndfMWxGZSiZpj/gZ7CmE878p0kIGZYhvYNu40O87s+le9IIwiHkTXZNvhZb/4+z5vmzLlgU92sxI76P6LaAgz6ThbN9mDXE3YrUSkfibB01O/C8CUy4Ib00nRNeYSD74JaVWCYvfwWHVlnVojP0Lx188nXpFsT3sAwVASCMzSJKwWmnfzIapaXMIp9Rh8hNKNXEoICwbTWCq59vd6B57ZEUyzmcWvu5GUR+cdqbkX71wk+pKvnSwvfnEBLXg7FzAGdFKS+Yv8IBsRNB6KcMUcZkDPh4l5aMFUzDMvFnvLBhRkrtArcnwGBf1qxHRntt6h8Za+gi3OV4i01MfpF7BSoG1+af/K8AkCHzJpMawDyuF58s8iZe9yzmAc1pjU/XmhyzlIRyAMWQlIOyfdQcDYS3cC3oKiTEmHnnKd/h+KHCKAg8tKUEqIdWeT6kEFostKR4DesQl82pDyo1wtXw1XoHzbI7Ffa/XdhhnMFAbAIu8uHjD9le7DHbrBNpCr1oEFwVeeXOIjMRZP2yETn4D9rsbRugfFXLqHQWQ/utqqovzy9z8dpBjKS9X6F5ohhcQP9RX8wEv+3GUKCwJYtreRfBeUPNWXugg9Q02FkmFtodzGFlw3TWlf5W3Zoo53f/Yo1P0gqY+h+LtkVZHiTZZeDT6R43LEQ1SbhY7XP+cFNseB2oqpCsVtfr5eJLKSsjBrB8oqdKRNa9GHOo9eRgYchh3VEvY1R5JKT7YBPwKGJz+xG1p0lRY/1fBBsyWDONsMN63grCVSUWXoHuZw5sqqUQzSQEZ4hhRxrrrakGdcLU06IdmLG8Z/JQYrF09DKJREpolKrhxQSynBiSrkEz9vML4hdaTHCe9mcW69LT2szAXZol3DRjrmU9BKMgANkTWsKhJsYHpBHTF7l8N6e7BYQ7zT9Hcrtt8XNUb7TuOhuVuCQlb7mK2SOYtePjEex2OfPOE/tNIoLSRzWEX+he9x2U/7qsZjKDym
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64
MIME-Version: 1.0
X-MS-Exchange-CrossTenant-AuthAs: Internal
X-MS-Exchange-CrossTenant-AuthSource: FR2P281MB1527.DEUP281.PROD.OUTLOOK.COM
X-MS-Exchange-CrossTenant-Network-Message-Id: 26ccf1ee-e8e1-49eb-1979-08dbc988e719
X-MS-Exchange-CrossTenant-originalarrivaltime: 10 Oct 2023 12:03:23.2535 (UTC)
X-MS-Exchange-CrossTenant-fromentityheader: Hosted
X-MS-Exchange-CrossTenant-id: bde4dffc-4b60-4cf6-8b04-a5eeb25f5c4f
X-MS-Exchange-CrossTenant-mailboxtype: HOSTED
X-MS-Exchange-CrossTenant-userprincipalname: nWlUPMaDXHrCP/mM6XERtWg94/viZUKs+HkXCZOkohBiGMKuTcYMWOk1FbIBHnBNjK9wk32rAqFgGoOYtMfl2VQGK2+2K5BwVO78kimLQs8=
X-MS-Exchange-Transport-CrossTenantHeadersStamped: BEZP281MB2327
X-OriginatorOrg: telekom.de
Archived-At: <https://mailarchive.ietf.org/arch/msg/tsvwg/utDVrzcqoXSoFgS4qWi727h3gkY>
Subject: Re: [tsvwg] I-D Action: draft-ietf-tsvwg-nqb-19.txt - 7. Example Use Cases
X-BeenThere: tsvwg@ietf.org
X-Mailman-Version: 2.1.39
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: Tue, 10 Oct 2023 12:03:36 -0000

Hi Greg,

thanks for closing the "use case" headline issue.

Regarding security  related to 3GPP, I'm not an expert either. Maybe adding a sentence that the security section doesn't discuss 3GPP related issues and favours a discussion there, if the suggested scheduling is adapted? Such a comment may apply as well for standards of all other SDOs, if preferred. Such a statement would cleanly delineate IETF responsibility from that of other SDOs. 

I note that draft NQB recommends implementation for several other SDOs by requirements language, but so far wasn't liaised with these SDOs. I'd prefer clarity on the topic "security of NQB operation if supported by standards of other SDOs", as the document extensively discusses support by other SDOs and does so by using requirements language. In particular, the security section should be explicit
- whether the IETF NQB security discussion covers the deployment of NQB within another SDO
- if not, please add an explicit statement that the security of deployment and operation of NQB is expected by an SDO set to specify support of NQB.

Regards,

Ruediger

-----Ursprüngliche Nachricht-----
Von: Greg White <g.white@cablelabs.com> 
Gesendet: Donnerstag, 31. August 2023 20:21
An: Geib, Rüdiger <Ruediger.Geib@telekom.de>; tsvwg-chairs@ietf.org
Cc: tsvwg@ietf.org
Betreff: Re: [tsvwg] I-D Action: draft-ietf-tsvwg-nqb-19.txt - 7. Example Use Cases

Hi Ruediger,

Per your suggestion, I will relabel section 7 as "Mapping NQB to standards of other SDOs".

Regarding cases where NQB is not supported, we already have the overall requirement (section 4.2) that NQB be aggregated with Default traffic, and in the Wi-Fi sub-section there is specific text around legacy W-Fi gear.  In DOCSIS there is no inspection of the DSCP unless it is explicitly configured, so the default behavior aligns with section 4.2 already.  I believe the same is true in 3GPP networks (but would welcome validation of that from someone more expert than I am).

Regarding the security discussion, that can be found in section 11, where it covers general concerns and also some specific ones that relate to Wi-Fi.  I believe that the security considerations for DOCSIS are covered sufficiently by the general statements.  Are you aware of specific security considerations for 3GPP? If so, please provide text to address the concerns that you have in mind.

-Greg

  


On 8/1/23, 4:49 AM, "Ruediger.Geib@telekom.de <mailto:Ruediger.Geib@telekom.de>" <Ruediger.Geib@telekom.de <mailto:Ruediger.Geib@telekom.de>> wrote:


Hi Greg, hi chairs,


Section 7. Example Use Cases


This section doesn't contain example use cases. The section contains NQB mappings to standards of other SDOs and does so by requirement language. I'd like to offer two proposals to make progress:
- either keep the section title "Example Use Cases" and change content to example use cases.
- or keep the content and change the section title to reflect the content offered. Example: "Mapping NQB to standards of other SDO's" (inspired by "Mapping Diffserv to IEEE 802.11")


- I note that Section 7 only standardizes how to support NQB by standards of other SDOs. The draft so far does not specify how these SDO's should forward NQB marked traffic, if the NQB PHB is not supported.
- There's no or little security discussion of possible threats imposed if NQB mappings to standards of other SDO's are applied as specified by this draft. Please add these.


I address the chairs too, as I failed to find other RFCs applying extensive requirements language in a section named "Example Use Cases" when making a small sample of other RFCs. This may be usual practice, but I'm unfortunately not aware of it. I welcome guidance.


Regards,


Ruediger


-----Ursprüngliche Nachricht-----
Von: tsvwg <tsvwg-bounces@ietf.org <mailto:tsvwg-bounces@ietf.org>> Im Auftrag von internet-drafts@ietf.org <mailto:internet-drafts@ietf.org>
Gesendet: Mittwoch, 26. Juli 2023 19:08
An: i-d-announce@ietf.org <mailto:i-d-announce@ietf.org>
Cc: tsvwg@ietf.org <mailto:tsvwg@ietf.org>
Betreff: [tsvwg] I-D Action: draft-ietf-tsvwg-nqb-19.txt




A New Internet-Draft is available from the on-line Internet-Drafts directories. This Internet-Draft is a work item of the Transport Area Working Group (TSVWG) WG of the IETF.


Title : A Non-Queue-Building Per-Hop Behavior (NQB PHB) for Differentiated Services Authors : Greg White Thomas Fossati Filename : draft-ietf-tsvwg-nqb-19.txt Pages : 29 Date : 2023-07-26


Abstract:
This document specifies properties and characteristics of a Non- Queue-Building Per-Hop Behavior (NQB PHB). The NQB PHB provides a shallow-buffered, best-effort service as a complement to a Default deep-buffered best-effort service for Internet services. The purpose of this NQB PHB is to provide a separate queue that enables smooth (i.e. non-bursty), low-data-rate, application-limited traffic microflows, which would ordinarily share a queue with bursty and capacity-seeking traffic, to avoid the latency, latency variation and loss caused by such traffic. This PHB is implemented without prioritization and can be implemented without rate policing, making it suitable for environments where the use of these features is restricted. The NQB PHB has been developed primarily for use by access network segments, where queuing delays and queuing loss caused by Queue-Building protocols are manifested, but its use is not limited to such segments. In particular, applications to cable broadband links, Wi-Fi links, and mobile network radio and core segments are discussed. This document recommends a specific Differentiated Services Code Point (DSCP) to identify Non-Queue- Building microflows.


[NOTE (to be removed by RFC-Editor): This document references an ISE submission draft (I-D.briscoe-docsis-q-protection) that is approved for publication as an RFC. This draft should be held for publication until the queue protection RFC can be referenced.]


The IETF datatracker status page for this Internet-Draft is:
https://datatracker.ietf.org/doc/draft-ietf-tsvwg-nqb/ <https://datatracker.ietf.org/doc/draft-ietf-tsvwg-nqb/>


There is also an HTML version available at:
https://www.ietf.org/archive/id/draft-ietf-tsvwg-nqb-19.html <https://www.ietf.org/archive/id/draft-ietf-tsvwg-nqb-19.html>


A diff from the previous version is available at:
https://author-tools.ietf.org/iddiff?url2=draft-ietf-tsvwg-nqb-19 <https://author-tools.ietf.org/iddiff?url2=draft-ietf-tsvwg-nqb-19>


Internet-Drafts are also available by rsync at rsync.ietf.org::internet-drafts