Re: [tsvwg] FQ & VPNs

Jonathan Morton <chromatix99@gmail.com> Sun, 21 February 2021 19:31 UTC

Return-Path: <chromatix99@gmail.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 494063A105D for <tsvwg@ietfa.amsl.com>; Sun, 21 Feb 2021 11:31:43 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.848
X-Spam-Level:
X-Spam-Status: No, score=-1.848 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_ENVFROM_END_DIGIT=0.25, FREEMAIL_FROM=0.001, 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 x-KFjaN1QBX7 for <tsvwg@ietfa.amsl.com>; Sun, 21 Feb 2021 11:31:41 -0800 (PST)
Received: from mail-lj1-x22c.google.com (mail-lj1-x22c.google.com [IPv6:2a00:1450:4864:20::22c]) (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 9519F3A104A for <tsvwg@ietf.org>; Sun, 21 Feb 2021 11:31:38 -0800 (PST)
Received: by mail-lj1-x22c.google.com with SMTP id r11so7385502ljk.9 for <tsvwg@ietf.org>; Sun, 21 Feb 2021 11:31:38 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:subject:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to; bh=yg4kjNFz6qgo8//kXeQCxcSC44kXS+j/YvRKtGkP9dM=; b=uaN/S7IzK8qzQMBk/wVOxcTH77Rlm4D1p+uT8icXPaRYqDLOJA7qxO6lCKqV0QFMEn YscvB+JEigkSK3P2mKsbTIy6TRx8howwrR5AzEZV/CJoxsrClHtD6PZWqdEIWQs69tkD qk9ATOO3qHgt6bjCOO08PsZMbiZshtase3IX1k7AhuB4VH0m5omKv++SGWcqNtV/u3+u LcPabH759UtmTRsFctDJRGxYL5m+PmlvspmYb4tUZXBmrJ3hjAoqPLJGeJdzjuA0gWwZ tDuN46a1c9dPovrMkC5mBMmPsVe00hpbI4p721RJgWhSRpUNWbg42nbwy8MQyiRzKveJ HMBQ==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:subject:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to; bh=yg4kjNFz6qgo8//kXeQCxcSC44kXS+j/YvRKtGkP9dM=; b=HmBrXVDHB7Ur2v3Lv7XWVkRjdKUoJp5Nj/IC5kIBlWItz8Nt0zVI3rW7txb8GFA/DB DU9BWyQpqg2Np6JZAhzs7PRJomNcKGMgQg35tGa7BxKAGqYlkYSotXz+fQpvRS0d/3fp E0JV9Lvj1jsuw7IMD/udRyV8y9b6OzFrE1/XVx0pc6g2TeELHuUDPB6hh5G3EPZMaR6E a4UZqBW6Iqy+sEMaEXwSXM2JCfB8eSc+xROwUedARcBS/aShLC177tw6LT7KLjjRWdU/ R323mt8ODTLe+UVxqlJeEdMXI6m+6suisARbbDaYBPMbvbptRqlK0+1VhHBD5hWVOPHC GgJA==
X-Gm-Message-State: AOAM532lVDP07CYX4CWx9exxhGZe9vQNgmPuXxv2P9ptYYQACwWZMu24 OIvXHqSG8XmTf5HJF/ZIbPw=
X-Google-Smtp-Source: ABdhPJzKyopwXQyQuTnqvzm+ceT3R7vLsLkVH2pauEqWop0nRllSLgav/byOzwzwKFCn2F7oLNA5tQ==
X-Received: by 2002:a2e:a16b:: with SMTP id u11mr12081325ljl.164.1613935896943; Sun, 21 Feb 2021 11:31:36 -0800 (PST)
Received: from jonathartonsmbp.lan (176-93-29-60.bb.dnainternet.fi. [176.93.29.60]) by smtp.gmail.com with ESMTPSA id 186sm964496lfh.193.2021.02.21.11.31.36 (version=TLS1_2 cipher=ECDHE-ECDSA-AES128-GCM-SHA256 bits=128/128); Sun, 21 Feb 2021 11:31:36 -0800 (PST)
Content-Type: text/plain; charset=us-ascii
Mime-Version: 1.0 (Mac OS X Mail 11.5 \(3445.9.7\))
From: Jonathan Morton <chromatix99@gmail.com>
In-Reply-To: <HE1PR0701MB2299C166CC9988746F3F16C5C2829@HE1PR0701MB2299.eurprd07.prod.outlook.com>
Date: Sun, 21 Feb 2021 21:31:35 +0200
Cc: Tom Henderson <tomh@tomh.org>, Dave Taht <dave.taht@gmail.com>, TSVWG <tsvwg@ietf.org>
Content-Transfer-Encoding: quoted-printable
Message-Id: <CD42B120-D4E2-42CC-B5EB-782033F1EC8F@gmail.com>
References: <161366419040.16138.17111583810851995947@ietfa.amsl.com> <BF0810D9-E742-4FCB-90B1-6957551B585D@heistp.net> <b222bbdf-70ae-3e5b-b122-1160299fb4e2@bobbriscoe.net> <E7CC88FA-F064-4B72-BAA9-8BE40F7AF040@gmail.com> <52cb434a-bd91-6260-7be9-85bdbd07b625@bobbriscoe.net> <BCAB7068-A10A-4FC4-9719-E300F644262C@gmail.com> <43f43fa2-69c4-bc10-3ffb-e95e41809335@bobbriscoe.net> <4835a3cd-4d88-68ac-d172-1e21bc42a150@bobbriscoe.net> <CAA93jw7_yvkqU-uxHkbHkO2g_RFmzCmJcxQhMJcBQjo=+QMh=w@mail.gmail.com> <HE1PR0701MB2299CF42CA83576C86070BB0C2839@HE1PR0701MB2299.eurprd07.prod.outlook.com> <13EBAF97-A9AF-47A1-AB71-546C31F762C2@gmail.com> <HE1PR0701MB22999A319816198B515234BEC2829@HE1PR0701MB2299.eurprd07.prod.outlook.com> <CAA93jw6GNbgOSDfWo2mQPWSS5GQdTNqtq=fBgspP=MNkyPNtfA@mail.gmail.com> <eef468c8-1152-f6e8-cfbf-c80cb2d465a0@tomh.org> <94BF48C8-733B-42AC-ABC1-246692E2E0A1@gmail.com> <HE1PR0701MB2299C166CC9988746F3F16C5C2829@HE1PR0701MB2299.eurprd07.prod.outlook.com>
To: Ingemar Johansson S <ingemar.s.johansson@ericsson.com>
X-Mailer: Apple Mail (2.3445.9.7)
Archived-At: <https://mailarchive.ietf.org/arch/msg/tsvwg/71PAXrWPNqYeN1bnyW_ZgfzOw5k>
Subject: Re: [tsvwg] FQ & VPNs
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: Sun, 21 Feb 2021 19:31:50 -0000

> On 21 Feb, 2021, at 9:24 pm, Ingemar Johansson S <ingemar.s.johansson@ericsson.com> wrote:
> 
> Please read
> https://tools.ietf.org/html/rfc8311

Yes, I did.  And what it actually says is:

> This memo updates RFC 3168 to allow routers to treat the ECT(0) and ECT(1) codepoints differently, provided that the changes from RFC 3168 are documented in an Experimental RFC in the IETF document stream.  The specific change to 
> RFC 3168 is to insert the words "unless otherwise specified by an Experimental RFC in the IETF document stream" at the end of the above sentence.

Which is pretty much equivalent to what I just said to Tom.  RFC-8311 does not *in itself* allow routers to treat the two ECT codepoints differently; it merely allows the IETF to approve an experiment which does so.  It has not yet done so.

 - Jonathan Morton