From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail-io1-xd34.google.com (mail-io1-xd34.google.com [IPv6:2607:f8b0:4864:20::d34]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by lists.bufferbloat.net (Postfix) with ESMTPS id CB9113CB35 for ; Fri, 22 Mar 2019 14:28:21 -0400 (EDT) Received: by mail-io1-xd34.google.com with SMTP id b9so2463629iot.13 for ; Fri, 22 Mar 2019 11:28:21 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=broadcom.com; s=google; h=from:mime-version:thread-index:date:message-id:subject:to; bh=EPdEL5hejvXB/Cd+hXnyfECQQSun4BTaNjsXviPIB+k=; b=Ag/zTk77RIADDnDP9wfMKklk/II504NSZs9kCEyXQWJtpIf4S55Qvb9kVRBcw6B/hO 9+3gRVpvGPH+75w3GJvB35A4Oadoh7NBy6B/Yn97jJT+QN3NHje54nkjrbIf3q/TiCv2 eo0cS4WFTRtIQ3I3vwH1d5Hk5gbZ4b2hqbK1M= X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:from:mime-version:thread-index:date:message-id :subject:to; bh=EPdEL5hejvXB/Cd+hXnyfECQQSun4BTaNjsXviPIB+k=; b=Tkk1yCTNga/yfIFMuzwDn8j0d8vLYRnMr4oRSbDydNDN3JIOK/rW28x4W0GFQCkQd6 eSCToya4TjLguG03IVJcuegPwspO8KMuqA/TqSTgz1N9wTKsspXwqpR+G07CuBOoTiLJ 2N0EvgO4+0A4JYh2IZzlOJfqSdx2MZefU2Q7/yq57fKTPjBMw96U3S6xSIjK+I8J7qeG 9BxAPRFrTR0Bm1YLPZLyJ7XEegFiTlpibhfXx8kDAxO5j+uU09CjStmJqL0zDdP9ZaAe KES0NrwpHVYzg7/psdsj/oky9hh6Gky72O0ytelDcjLCJplvP4HteHmT2e00fwvV+OhE zt0w== X-Gm-Message-State: APjAAAVGj7MgkZNx5Q7buT4o2XzfqepXRMvZ3IG+qS4Rjoy/CDlsrF6P jvhmr+3YO/ZJCCRvOm5NfRRAc+ykuLiRFXpBdoX+FDyR X-Google-Smtp-Source: APXvYqwXNcXvLRdPH6t3nD9tDRQN5hHs0AV+YhlEV1XmrjqJehutL7LooNqD4IfAaug7jtnErmnrsyyrSVfiduL7BNg= X-Received: by 2002:a6b:760b:: with SMTP id g11mr8084619iom.249.1553279301070; Fri, 22 Mar 2019 11:28:21 -0700 (PDT) From: Victor Hou MIME-Version: 1.0 X-Mailer: Microsoft Outlook 14.0 Thread-Index: AdTg3QYkBAESsz/aQnCkVtcjYthT4A== Date: Fri, 22 Mar 2019 11:28:19 -0700 Message-ID: <2c8ad5fe4be5c52ad1a3c2bf7f91a09a@mail.gmail.com> To: bloat@lists.bufferbloat.net Content-Type: multipart/alternative; boundary="000000000000fa6edf0584b3047d" Subject: [Bloat] [Ecn-sane] [iccrg] Fwd: [tcpPrague] Implementation and experimentation of TCP Prague/L4S hackaton at IETF104 X-BeenThere: bloat@lists.bufferbloat.net X-Mailman-Version: 2.1.20 Precedence: list List-Id: General list for discussing Bufferbloat List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 22 Mar 2019 18:28:21 -0000 --000000000000fa6edf0584b3047d Content-Type: text/plain; charset="UTF-8" On Mon Mar 18 21:06:57 EDT 2019, Bob Briscoe said: >>> * In summer 2017 CableLabs started work on Low Latency DOCSIS, and hired me later in the year to help develop and specify it, along with support for L4S o In Jan 2019 the Low Latency DOCSIS spec was published and is now being implemented. o You can find the primary companies involved at the end of the White Paper. https://cablela.bs/low-latency-docsis-technology-overview-february-2019 o Operators: Liberty Global Charter Rogers Comcast Shaw Cox Communications o Equipment vendors ARRIS Huawei Broadcom Intel Casa Nokia Cisco Videotron >>> Broadcom has been deeply involved in developing the Low Latency DOCSIS cable industry specification that Bob Briscoe mentioned. We concur with the L4S use of ECT(1). L4S can be implemented either in a dual-queue or an fq implementation. SCE cannot be implemented with a dual-queue implementation; the only way to support it is with an fq implementation. An fq implementation is incompatible with the Low Latency DOCSIS specification developed within the cable industry. Victor --000000000000fa6edf0584b3047d Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable

On Mon Mar 18 21:06:57 EDT 20= 19, Bob Briscoe said:

=C2=A0

>>>=C2=A0

* In summer 2017 CableLa= bs started work on Low Latency DOCSIS, and hired

me later in the year to help develop and specify it, along with support

for L4S

=C2=A0=C2=A0 o I= n Jan 2019 the Low Latency DOCSIS spec was published and is now

being implemented.

=C2=A0=C2=A0 o= You can find the primary companies involved at the end of the White

Paper.

https://cab= lela.bs/low-latency-docsis-technology-overview-february-2019

=C2=A0=C2=A0 o Operators:

=C2=A0= =C2=A0=C2=A0=C2=A0 Liberty Global

=C2=A0=C2=A0=C2= =A0=C2=A0 Charter

=C2=A0=C2=A0=C2=A0=C2=A0 Rogers=

=C2=A0=C2=A0=C2=A0=C2=A0 Comcast

=C2=A0=C2=A0=C2=A0=C2=A0 Shaw

=C2=A0= =C2=A0=C2=A0 =C2=A0Cox Communications

o Equipment= vendors

=C2=A0=C2=A0=C2=A0=C2=A0 ARRIS

=C2=A0=C2=A0=C2=A0=C2=A0 Huawei

= =C2=A0=C2=A0=C2=A0=C2=A0 Broadcom

=C2=A0=C2=A0=C2= =A0=C2=A0 Intel

=C2=A0=C2=A0=C2=A0=C2=A0 Casa

=

=C2=A0=C2=A0=C2=A0=C2=A0 Nokia

=C2=A0=C2=A0=C2=A0=C2=A0 Cisco

=C2=A0=C2=A0= =C2=A0=C2=A0 Videotron

>>>=C2=A0

=C2=A0

Broadcom has been deepl= y involved in developing the Low Latency DOCSIS cable industry specificatio= n that Bob Briscoe mentioned.=C2=A0 We concur with the L4S use of ECT(1).= =C2=A0 L4S can be implemented either in a dual-queue or an fq implementatio= n. SCE cannot be implemented with a dual-queue implementation; the only way= to support it is with an fq implementation.=C2=A0 An fq implementation is = incompatible with the Low Latency DOCSIS specification developed within the= cable industry.

=C2=A0

Victor

--000000000000fa6edf0584b3047d--