Re: [tsvwg] New Version Notification for draft-white-tsvwg-lld-00.txt

Greg White <g.white@CableLabs.com> Tue, 12 March 2019 02:18 UTC

Return-Path: <g.white@CableLabs.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 5B96112AF7F for <tsvwg@ietfa.amsl.com>; Mon, 11 Mar 2019 19:18:07 -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, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=cablelabs.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 1MzASk5BUZFg for <tsvwg@ietfa.amsl.com>; Mon, 11 Mar 2019 19:18:04 -0700 (PDT)
Received: from NAM04-SN1-obe.outbound.protection.outlook.com (mail-eopbgr700122.outbound.protection.outlook.com [40.107.70.122]) (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 3C9BC129A86 for <tsvwg@ietf.org>; Mon, 11 Mar 2019 19:18:04 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=cablelabs.com; s=selector1; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-SenderADCheck; bh=FPYfYbfiq+Pjg7kd9NSrRcOlIoP2FgxF0oN9sJSM44U=; b=Q12I8jl2fY8P/yqNpdkLbx7tHQNC0Kdx8JCPjlkG9EJ0OITKROVJbXdN47PueoEm7WJSREZNB93aY50BSUllaoaLG8iowscWrKRJ0Gyu/Nn3/cYkpPHCRGbEjuZawICSrNqByyaHrm0zHpQXzIBPUbzM8W0niK/TsIGHCsNQJeI=
Received: from SN6PR06MB4655.namprd06.prod.outlook.com (52.135.117.85) by SN6PR06MB4045.namprd06.prod.outlook.com (52.132.123.139) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.1686.18; Tue, 12 Mar 2019 02:18:01 +0000
Received: from SN6PR06MB4655.namprd06.prod.outlook.com ([fe80::712c:21cc:3dcf:637b]) by SN6PR06MB4655.namprd06.prod.outlook.com ([fe80::712c:21cc:3dcf:637b%4]) with mapi id 15.20.1686.021; Tue, 12 Mar 2019 02:18:01 +0000
From: Greg White <g.white@CableLabs.com>
To: Luca Muscariello <luca.muscariello@gmail.com>
CC: "tsvwg@ietf.org" <tsvwg@ietf.org>
Thread-Topic: [tsvwg] New Version Notification for draft-white-tsvwg-lld-00.txt
Thread-Index: AQHU2HnRyW07oTC9ek+bGSwvy18MNA==
Date: Tue, 12 Mar 2019 02:18:01 +0000
Message-ID: <0289E1B3-9AFF-4633-A9B1-6BAEE96B7692@cablelabs.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
user-agent: Microsoft-MacOutlook/10.14.0.181208
x-originating-ip: [73.14.190.183]
x-ms-publictraffictype: Email
x-ms-office365-filtering-correlation-id: e7f3b032-468c-485b-c276-08d6a690f3c4
x-microsoft-antispam: BCL:0; PCL:0; RULEID:(2390118)(7020095)(4652040)(8989299)(4534185)(4627221)(201703031133081)(201702281549075)(8990200)(5600127)(711020)(4605104)(2017052603328)(7153060)(7193020); SRVR:SN6PR06MB4045;
x-ms-traffictypediagnostic: SN6PR06MB4045:
x-ms-exchange-purlcount: 7
x-microsoft-exchange-diagnostics: 1; SN6PR06MB4045; 20:TQOokQ1qiNwK6Sb87H9MbV4ZLPocMitLS7hLzcqY0eq1nE82SsCx4vd3d4yeZyjqnpWgsvgD4AVXfrJFQGpyKw4WoEndMqDkOuvymj0U5pTj04Cactu9oNAuCkFfa2ACAD3VU1Kj6V6cR0xfLsQGZNkCif9fXcTHQxp0fJ6lJH8=
x-microsoft-antispam-prvs: <SN6PR06MB4045177ED0B122399CD925B1EE490@SN6PR06MB4045.namprd06.prod.outlook.com>
x-forefront-prvs: 09749A275C
x-forefront-antispam-report: SFV:NSPM; SFS:(10019020)(979002)(346002)(366004)(136003)(39840400004)(376002)(396003)(189003)(199004)(106356001)(8936002)(6246003)(316002)(6916009)(81166006)(81156014)(83716004)(25786009)(8676002)(99286004)(966005)(186003)(256004)(14444005)(86362001)(97736004)(6486002)(36756003)(5660300002)(26005)(66574012)(68736007)(6436002)(6116002)(58126008)(229853002)(82746002)(3846002)(66066001)(478600001)(53936002)(14454004)(4326008)(2616005)(476003)(6346003)(6512007)(486006)(105586002)(33656002)(6506007)(102836004)(6306002)(53546011)(2906002)(305945005)(71190400001)(71200400001)(15650500001)(7736002)(85282002)(969003)(989001)(999001)(1009001)(1019001); DIR:OUT; SFP:1102; SCL:1; SRVR:SN6PR06MB4045; H:SN6PR06MB4655.namprd06.prod.outlook.com; FPR:; SPF:None; LANG:en; PTR:InfoNoRecords; MX:1; A:1;
received-spf: None (protection.outlook.com: CableLabs.com does not designate permitted sender hosts)
authentication-results: spf=none (sender IP is ) smtp.mailfrom=g.white@CableLabs.com;
x-ms-exchange-senderadcheck: 1
x-microsoft-antispam-message-info: lQGNUCSPmDrWKb945mNjdgyVVx/GO1tBv3Ple5ZcKOi2UjIWeT03ik2IUFLxEfZgJRUF3bz3f2QIa0LyroNIUYct7hhBAXtp1vh5pU70tB+KTpjM/+ppnP7VPHeAAWwjKM7MwObJba4eSZ//ZefA72EAx3uDMuA0wO604IGzeSALFRYsJCCtMQS0mUtRa6ng0KbInL7JsjodrDHkh+Ub96AbiWp6tp22QCib/2/LxrOYiNysTe9eyn/Htg+9fhble94CM79uPPFbFXSfTXobfCaDxphxTvVoBD2LA8IV2jFcQqDYPPHJ2EeiqSsopFLFLUsZI9GEJCkkjeUKCPJQPM/N+XeqrrTcAC/42uP6m/wcZRDDpSLcn4Mr0c0yoe+CUPZEKD8x9uiu98ecVe3fqekjfU0jNBx97A7k0zQUvw8=
Content-Type: text/plain; charset="utf-8"
Content-ID: <2A8C0CFD1569104A9F0665FC865E53A9@namprd06.prod.outlook.com>
Content-Transfer-Encoding: base64
MIME-Version: 1.0
X-OriginatorOrg: cablelabs.com
X-MS-Exchange-CrossTenant-Network-Message-Id: e7f3b032-468c-485b-c276-08d6a690f3c4
X-MS-Exchange-CrossTenant-originalarrivaltime: 12 Mar 2019 02:18:01.2812 (UTC)
X-MS-Exchange-CrossTenant-fromentityheader: Hosted
X-MS-Exchange-CrossTenant-id: ce4fbcd1-1d81-4af0-ad0b-2998c441e160
X-MS-Exchange-CrossTenant-mailboxtype: HOSTED
X-MS-Exchange-Transport-CrossTenantHeadersStamped: SN6PR06MB4045
Archived-At: <https://mailarchive.ietf.org/arch/msg/tsvwg/Cr3cxA3YnyVajHYpsETUONMGdBs>
Subject: Re: [tsvwg] New Version Notification for draft-white-tsvwg-lld-00.txt
X-BeenThere: tsvwg@ietf.org
X-Mailman-Version: 2.1.29
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, 12 Mar 2019 02:18:07 -0000

Hi Luca, 

You can find the details in Annex P of the DOCSIS MULPIv3.1 spec.
https://specification-search.cablelabs.com/CM-SP-MULPIv3.1

-Greg


From: Luca Muscariello <luca.muscariello@gmail.com>
Date: Monday, March 11, 2019 at 6:26 PM
To: Greg White <g.white@CableLabs.com>
Cc: Dave Taht <dave@taht.net>, Jonathan Morton <chromatix99@gmail.com>, "tsvwg@ietf.org" <tsvwg@ietf.org>
Subject: Re: [tsvwg] New Version Notification for draft-morton-taht-tsvwg-sce-00.txt

Hi Greg,

I'm curious about the queue protection function in the LLD document.
It seems to assume that a flow table is maintained to determine if a flow 
has the right to enter the low latency queue.

Can you give more details about that component? Or point me to a reference?

Thanks
Luca


On 3/11/19, 5:29 PM, "tsvwg on behalf of Greg White" <tsvwg-bounces@ietf.org on behalf of g.white@CableLabs.com> wrote:

    TSVWG,
    
    I've posted a new informative draft that gives an overview of the new Low Latency DOCSIS specification (see links below).  This overview may be interesting to TSVWG participants because it includes support for L4S (https://datatracker.ietf.org/doc/html/draft-ietf-tsvwg-aqm-dualq-coupled) and for the NQB PHB (https://datatracker.ietf.org/doc/html/draft-white-tsvwg-nqb).
    
    Best Regards,
    Greg
    
    
    
    On 3/11/19, 5:05 PM, "internet-drafts@ietf.org" <internet-drafts@ietf.org> wrote:
    
        
        A new version of I-D, draft-white-tsvwg-lld-00.txt
        has been successfully submitted by Greg White and posted to the
        IETF repository.
        
        Name:		draft-white-tsvwg-lld
        Revision:	00
        Title:		Low Latency DOCSIS - Technology Overview
        Document date:	2019-03-11
        Group:		Individual Submission
        Pages:		25
        URL:            https://www.ietf.org/internet-drafts/draft-white-tsvwg-lld-00.txt 
        Status:         https://datatracker.ietf.org/doc/draft-white-tsvwg-lld/ 
        Htmlized:       https://tools.ietf.org/html/draft-white-tsvwg-lld-00 
        Htmlized:       https://datatracker.ietf.org/doc/html/draft-white-tsvwg-lld 
        
        
        Abstract:
           NOTE: This document is a reformatted version of [LLD-white-paper].
        
           The evolution of the bandwidth capabilities - from kilobits per
           second to gigabits - across generations of DOCSIS cable broadband
           technology has paved the way for the applications that today form our
           digital lives.  Along with increased bandwidth, or "speed", the
           latency performance of DOCSIS technology has also improved in recent
           years.  Although it often gets less attention, latency performance
           contributes as much or more to the broadband experience and the
           feasibility of future applications as does speed.
        
           Low Latency DOCSIS technology (LLD) is a specification developed by
           CableLabs in collaboration with DOCSIS vendors and cable operators
           that tackles the two main causes of latency in the network: queuing
           delay and media acquisition delay.  LLD introduces an approach
           wherein data traffic from applications that aren't causing latency
           can take a different logical path through the DOCSIS network without
           getting hung up behind data from applications that are causing
           latency, as is the case in today's Internet architectures.  This
           mechanism doesn't interfere with the way applications share the total
           bandwidth of the connection, and it doesn't reduce one application's
           latency at the expense of others.  In addition, LLD improves the
           DOCSIS upstream media acquisition delay with a faster request-grant
           loop and a new proactive scheduling mechanism.  LLD makes the
           internet experience better for latency sensitive applications without
           any negative impact on other applications.
        
           The latest generation of DOCSIS equipment that has been deployed in
           the field - DOCSIS 3.1 - experiences typical latency performance of
           around 10 milliseconds (ms) on the Access Network link.  However,
           under heavy load, the link can experience delay spikes of 100 ms or
           more.  LLD systems can deliver a consistent 1 ms delay on the DOCSIS
           network for traffic that isn't causing latency, imperceptible for
           nearly all applications.  The experience will be more consistent with
           much smaller delay variation.
        
           LLD can be deployed by field-upgrading DOCSIS 3.1 cable modem and
           cable modem termination system devices with new software.  The
           technology includes tools that enable automatic provisioning of these
           new services, and it also introduces new tools to report statistics
           of latency performance to the operator.
        
           Cable operators, DOCSIS equipment manufacturers, and application
           providers will all have to act in order to take advantage of LLD.
           This white paper explains the technology and describes the role that
           each of these parties plays in making LLD a reality.
        
                                                                                          
        
        
        Please note that it may take a couple of minutes from the time of submission
        until the htmlized version and diff are available at tools.ietf.org.
        
        The IETF Secretariat