Re: [Teas] AQM in draft-ietf-teas-rfc3272bis

Dave Taht <dave.taht@gmail.com> Fri, 25 February 2022 12:10 UTC

Return-Path: <dave.taht@gmail.com>
X-Original-To: teas@ietfa.amsl.com
Delivered-To: teas@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 68A873A0C04 for <teas@ietfa.amsl.com>; Fri, 25 Feb 2022 04:10:28 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -7.098
X-Spam-Level:
X-Spam-Status: No, score=-7.098 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, FREEMAIL_FROM=0.001, RCVD_IN_DNSWL_HI=-5, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.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 WQ-1LVPMVh0n for <teas@ietfa.amsl.com>; Fri, 25 Feb 2022 04:10:22 -0800 (PST)
Received: from mail-ed1-x534.google.com (mail-ed1-x534.google.com [IPv6:2a00:1450:4864:20::534]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id A11CA3A0A92 for <teas@ietf.org>; Fri, 25 Feb 2022 04:10:22 -0800 (PST)
Received: by mail-ed1-x534.google.com with SMTP id m3so7084225eda.10 for <teas@ietf.org>; Fri, 25 Feb 2022 04:10:22 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20210112; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc:content-transfer-encoding; bh=eDlo5xG4hmxj52Uwr/LOQhoGQmIpxjuxG7ao20/Lk0M=; b=J50XZQQSptbaAiMZ6XLkRuaYulErQDTrI5b9LwIAkBFNOoGd30zUlV/XSUPQlPZ153 mLSbz687CD7b7ZxwUjqfY80FYf7vhLDyh8+knqH9UoEaAyZzwxdb8Vo8NEIxzGHy5x/U HMtId5HfFCowXz5KK5SzjulQCkPEwW0jo5hvkGpDXY9RkGpq5jKCPtrMSUl5WVK7y/n+ PBpLo5Mw7PeCdWvewjpsDv9CueXMRGenrxjC20jN2hpygWmQ8ZjGc3jMAO+TwvUlPyJ4 t4m8BdF1BIwQ3Sav/mlK/KZXPi3c1O8zc30aK6VoyfeJeTNelrlyHPxuVcXVUUgqQ5vu GMPw==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc:content-transfer-encoding; bh=eDlo5xG4hmxj52Uwr/LOQhoGQmIpxjuxG7ao20/Lk0M=; b=CCecJ6s4zqoFLAp6vMjjI06+DZvY/BH4dshwjCuQGpMUO0Qv44Y8U4+xqO8+sr0aeZ KzYqjMl9z3qziWUk5ULMDxF9TQclujrXM25pPIzFDXMrcBB+m8KTDcA/zIMXuw/wZb+3 zY3Ma6J76vpj1YYwE7wCpwkxTeO++is/0Vt1EKZviNQKkIlkJkUivUd/155dQULoNl76 hzOPoQHEXimDnSUorSyHeshyX+YbNessRNTX400vqPW7lBhMYzsgc6VR6qM831GwoOLA znVNYw6ShnqjOuMYCpNSTWwYHXg2NIFiUXlfNATbk3qCE48pTNn1b0/PXFp4Vjy1c99z 2zdg==
X-Gm-Message-State: AOAM533fx860T5moNDnOu6qJu1MyMdABLnWXpNFDGenkC79cjsh9C+1k wAO3By0kVzxY8YJ7IXt5Dg3atT+KmeWEsx1bashECbso8/U=
X-Google-Smtp-Source: ABdhPJx0pKB/KzbLwXdwnXMUMVVOBsfqD7mYi0dADyGQc9KxEgxwM9O69j2C/2frPbmzSw3QmOMNjmpSQgw1EwekgnM=
X-Received: by 2002:a50:e08c:0:b0:407:cdc6:809e with SMTP id f12-20020a50e08c000000b00407cdc6809emr6765529edl.162.1645791020175; Fri, 25 Feb 2022 04:10:20 -0800 (PST)
MIME-Version: 1.0
References: <036b01d82a26$e94581c0$bbd08540$@olddog.co.uk>
In-Reply-To: <036b01d82a26$e94581c0$bbd08540$@olddog.co.uk>
From: Dave Taht <dave.taht@gmail.com>
Date: Fri, 25 Feb 2022 07:10:06 -0500
Message-ID: <CAA93jw4YsOnek0GhoP+3+Qor31bLw-basKzngPdn2E0xMoQLXw@mail.gmail.com>
To: adrian@olddog.co.uk
Cc: teas@ietf.org
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
Archived-At: <https://mailarchive.ietf.org/arch/msg/teas/vpwR-9ypd6ghpSDpnOHKuUR-YVg>
Subject: Re: [Teas] AQM in draft-ietf-teas-rfc3272bis
X-BeenThere: teas@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Traffic Engineering Architecture and Signaling working group discussion list <teas.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/teas>, <mailto:teas-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/teas/>
List-Post: <mailto:teas@ietf.org>
List-Help: <mailto:teas-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/teas>, <mailto:teas-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 25 Feb 2022 12:10:37 -0000

I certainly think that some form of aqm,fq,or fq+aqm, awareness of
correct buffer sizing for certain traffic types, notably voip, are
essential components of quality traffic engineering.

very useful e2e techniques such as packet pacing are also now widely deployed.

In lieu of actually contributing text to teas at this particular moment in time:

rfc7567 is worth citing at least.

this is a good read about short vs big buffered switches:
https://blog.cloudflare.com/asics-at-the-edge/

Over here is some recent work with graphs (if you login) on the
mikrotik deployment:

https://forum.mikrotik.com/viewtopic.php?t=179307

https://forum.mikrotik.com/viewtopic.php?t=181289

A fallout of those threads above for me is trying to discover the
actual use and deployment of wred today, particularly with or without
rfc3168 style ecn or l4s/sce style early marking.

docsis 3.1 has pie: deployment report here:
https://blog.apnic.net/2021/12/02/working-latency-the-next-qoe-frontier/
-

cisco's AFD is useful (but not an ietf standard)

fq_codel is the default in linux, ios, osx, used as a core component
in "smart queue management"
(https://www.bufferbloat.net/projects/cerowrt/wiki/Smart_Queue_Management/
) in a ton of linux based routers, and in wifi.

Middleboxes such as preseem, and libreqos are also essentially doing
what I would consider to be TE.

After dumping all that stuff at y'all, the recent bitag report might
be of some interest

https://www.bitag.org/documents/BITAG_latency_explained.pdf

and for laughs:

https://blog.apnic.net/2020/01/22/bufferbloat-may-be-solved-but-its-not-over-yet/


On Fri, Feb 25, 2022 at 4:06 AM Adrian Farrel <adrian@olddog.co.uk> wrote:
>
> Dave Taht (cc here) recently mentioned in a social media comment that
> draft-ietf-teas-rfc3272bis fails to mention the work of the AQM working
> group.
>
> I've invited him to suggest a couple of short paragraphs and also recommend
> where they might fit into the document.
>
> Everyone is welcome to discuss whether AQM constitutes Traffic Engineering,
> and (of course) suggest their own text.
>
> Thanks,
> Adrian
>


-- 
I tried to build a better future, a few times:
https://wayforward.archive.org/?site=https%3A%2F%2Fwww.icei.org

Dave Täht CEO, TekLibre, LLC