Re: [tsvwg] Adoption call for draft-white-tsvwg-l4sops - to conclude 24th March 2021

Pete Heist <> Fri, 12 March 2021 12:31 UTC

Return-Path: <>
Received: from localhost (localhost []) by (Postfix) with ESMTP id 698953A0888 for <>; Fri, 12 Mar 2021 04:31:24 -0800 (PST)
X-Virus-Scanned: amavisd-new at
X-Spam-Flag: NO
X-Spam-Score: -2.098
X-Spam-Status: No, score=-2.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, RCVD_IN_DNSWL_BLOCKED=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: (amavisd-new); dkim=pass (2048-bit key)
Received: from ([]) by localhost ( []) (amavisd-new, port 10024) with ESMTP id WkCq-Nl2Zj2w for <>; Fri, 12 Mar 2021 04:31:22 -0800 (PST)
Received: from ( [IPv6:2a00:1450:4864:20::436]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by (Postfix) with ESMTPS id 94DFE3A0890 for <>; Fri, 12 Mar 2021 04:31:22 -0800 (PST)
Received: by with SMTP id j2so4700109wrx.9 for <>; Fri, 12 Mar 2021 04:31:22 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;; s=google; h=message-id:subject:from:to:cc:date:in-reply-to:references :user-agent:mime-version:content-transfer-encoding; bh=r4U6yxLw7d8aFqiFV1SNCqvFwqG59BB2qaXnUDtFvtc=; b=Dk2hI4pQtGsb+Iaa7+uFnJStPDpIb55pHtpbfvthC7oiRduzP45fRnCwUm7yOgTZ7v d7TPTJeR/ShqDGeCr6qTG+zb8mm2I/Q0TYE2WRTGzs+oX35y86YF6pxZ6RG/BhT0DgJ8 9l2Yq1+/Y5NHHRtF7e4JmFdgvalF0rBGT91eXvxVyiOF+a7xH6rzlPSrx98NeGulSZvx JJah8jJ4UL+RJhCGpLy/v5fCXPUF2hTY/tYpLH+t6Zf5S07jNNKnCVTtpUDWTTAJGG0a bCQ5pMeICWI/Hzn+poA3jyZOCChg8GCgvdStvLatDlcgRgxPL/tEdD+BLiFQ2BdJ1xJg RgSg==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;; s=20161025; h=x-gm-message-state:message-id:subject:from:to:cc:date:in-reply-to :references:user-agent:mime-version:content-transfer-encoding; bh=r4U6yxLw7d8aFqiFV1SNCqvFwqG59BB2qaXnUDtFvtc=; b=N0rK3rD4gsUmal0dhLUUn7rMYY9Ug1cpiBJxuuPzDzgZQPo58gzs6166GPtcVcKfDo syNh0i0T8BMt2UAhNGiqUz9woS7x8AWgZ9Um4l+tdFUdPq/bJEgL2O5w1zHDEuxRZXuY utc2UheZjMFm7nyLUjPaOkp4G6PmOnD9wwJs/vltdHlLEQhOkayJ4Q0Ab0bRGPP/P8ri yS+PqvGLkxDNXqFflj5MvTKZO+/qBL0DCsV5qudyCMeuEe6VwwGhMZy8YeDk/FDWE2Ow Rl4Au4XGwhoZyyZDUoipN5xcEbHu3VPzNrHH1Tij2S943yqTpQGTKgvLlpj90wALW9rr VM5g==
X-Gm-Message-State: AOAM531SMZ3IJCF2qv3UjDsQtXrzPW9u+iGHMrXBCaI4uVAjood7gCcf a1fniSZztOfevG0TbAj/KiY8og==
X-Google-Smtp-Source: ABdhPJxNOUe1TNN1A14VmNtp4VDj0cRY+Y7PWMykJ6SiZP7h4rSmBXjtAD4MMSi5QMgUzfy02b5EBg==
X-Received: by 2002:a5d:518c:: with SMTP id k12mr13904154wrv.15.1615552276002; Fri, 12 Mar 2021 04:31:16 -0800 (PST)
Received: from [] ( []) by with ESMTPSA id y205sm2429066wmc.18.2021. (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256); Fri, 12 Mar 2021 04:31:15 -0800 (PST)
Message-ID: <>
From: Pete Heist <>
To: Gorry Fairhurst <>
Cc: "" <>
Date: Fri, 12 Mar 2021 13:31:14 +0100
In-Reply-To: <>
References: <>
Content-Type: text/plain; charset="UTF-8"
User-Agent: Evolution 3.38.4
MIME-Version: 1.0
Content-Transfer-Encoding: 8bit
Archived-At: <>
Subject: Re: [tsvwg] Adoption call for draft-white-tsvwg-l4sops - to conclude 24th March 2021
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Transport Area Working Group <>
List-Unsubscribe: <>, <>
List-Archive: <>
List-Post: <>
List-Help: <>
List-Subscribe: <>, <>
X-List-Received-Date: Fri, 12 Mar 2021 12:31:24 -0000

I'll explain my position of not taking a stance on this document.

The available data suggest that L4S and conventional traffic cannot
coexist safely in the same RFC3168 signaling queue, and that those
queues have been deployed to some extent. I don't think this is
something that operational guidance by itself can fix, and would prefer
to see that addressed first.

However, I'm also not sure that impeding progress on this document is
helpful. In case the WG decides that there is rough consensus to
proceed with known safety issues, then I'd likely be among those
insisting on WGLC for this draft together with the L4S drafts. This
will provide published information on what to expect, and document what
issues were known by the IETF prior to approval for experiment.

If the document is adopted, then I should be able to provide at least
one review down the line.


On Tue, 2021-03-09 at 16:05 +0000, Gorry Fairhurst wrote:
> The WG is running an adoption call for:
>      Operational Guidance for Deployment of L4S in the Internet
> will end at midnight UTC on 24th March 2021.
> Please do read the draft, and send any comments/concerns to either
> the 
> tsvwg or to the chairs <>. Notes of support to 
> progress this work, and volunteers to review the drafts will also be 
> very welcome at this stage.
> Best wishes,
> Gorry, Wes and David
> (tsvwg co-chairs)