Re: [tsvwg] Another tunnel/VPN scenario (was RE: Reasons for WGLC/RFC asap)

Steven Blake <slblake@petri-meat.com> Fri, 04 December 2020 01:54 UTC

Return-Path: <slblake@petri-meat.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 04C3B3A11F8 for <tsvwg@ietfa.amsl.com>; Thu, 3 Dec 2020 17:54:18 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.901
X-Spam-Level:
X-Spam-Status: No, score=-1.901 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_MSPIKE_H2=-0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
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 oBUWBXknzGAa for <tsvwg@ietfa.amsl.com>; Thu, 3 Dec 2020 17:54:16 -0800 (PST)
Received: from olivedrab.birch.relay.mailchannels.net (olivedrab.birch.relay.mailchannels.net [23.83.209.135]) (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 821033A0DAB for <tsvwg@ietf.org>; Thu, 3 Dec 2020 17:54:16 -0800 (PST)
X-Sender-Id: totalchoicehosting|x-authuser|slblake+petri-meat.com@pawpaw.tchmachines.com
Received: from relay.mailchannels.net (localhost [127.0.0.1]) by relay.mailchannels.net (Postfix) with ESMTP id 689921E1D29; Fri, 4 Dec 2020 01:54:15 +0000 (UTC)
Received: from pawpaw.tchmachines.com (100-105-161-17.trex.outbound.svc.cluster.local [100.105.161.17]) (Authenticated sender: totalchoicehosting) by relay.mailchannels.net (Postfix) with ESMTPA id 5FD8B1E1D61; Fri, 4 Dec 2020 01:54:14 +0000 (UTC)
X-Sender-Id: totalchoicehosting|x-authuser|slblake+petri-meat.com@pawpaw.tchmachines.com
Received: from pawpaw.tchmachines.com (pawpaw.tchmachines.com [208.76.80.100]) (using TLSv1.2 with cipher DHE-RSA-AES256-GCM-SHA384) by 0.0.0.0:2500 (trex/5.18.11); Fri, 04 Dec 2020 01:54:15 +0000
X-MC-Relay: Neutral
X-MailChannels-SenderId: totalchoicehosting|x-authuser|slblake+petri-meat.com@pawpaw.tchmachines.com
X-MailChannels-Auth-Id: totalchoicehosting
X-Coil-Snatch: 36886783268eec15_1607046855169_3758601688
X-MC-Loop-Signature: 1607046855168:4140964026
X-MC-Ingress-Time: 1607046855168
Received: from [136.56.88.61] (port=35030 helo=axion.home.arpa) by pawpaw.tchmachines.com with esmtpsa (TLS1.2) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.93) (envelope-from <slblake@petri-meat.com>) id 1kl0IR-0006za-Sg; Thu, 03 Dec 2020 20:54:09 -0500
Message-ID: <44e2d6be0ecb93cc0163a8f73d368f65048b7dc4.camel@petri-meat.com>
From: Steven Blake <slblake@petri-meat.com>
To: Gorry Fairhurst <gorry@erg.abdn.ac.uk>
Cc: tsvwg IETF list <tsvwg@ietf.org>
Date: Thu, 03 Dec 2020 20:54:09 -0500
In-Reply-To: <494cd867-58ad-2cb5-4682-0b4c4f003326@erg.abdn.ac.uk>
References: <MN2PR19MB4045A76BC832A078250E436483E00@MN2PR19MB4045.namprd19.prod.outlook.com> <HE1PR0701MB2876A45ED62F1174A2462FF3C2FF0@HE1PR0701MB2876.eurprd07.prod.outlook.com> <56178FE4-E6EA-4736-B77F-8E71915A171B@gmx.de> <0763351c-3ba0-2205-59eb-89a1aa74d303@bobbriscoe.net> <25D05011-8193-482F-8186-A433AE3FE5C3@gmail.com> <494cd867-58ad-2cb5-4682-0b4c4f003326@erg.abdn.ac.uk>
Content-Type: text/plain; charset="UTF-8"
User-Agent: Evolution 3.34.4 (3.34.4-1.fc31)
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
X-AuthUser: slblake+petri-meat.com@pawpaw.tchmachines.com
Archived-At: <https://mailarchive.ietf.org/arch/msg/tsvwg/bIIbCn22Ho7VRQKICUHhZRPyXAQ>
Subject: Re: [tsvwg] Another tunnel/VPN scenario (was RE: Reasons for WGLC/RFC asap)
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: Fri, 04 Dec 2020 01:54:18 -0000

On Thu, 2020-12-03 at 16:40 +0000, Gorry Fairhurst wrote:
> Just on that last point, perhaps we should be clearer by what 
> "experiment" means.
> 
> On 03/12/2020 15:52, Jonathan Morton wrote:
> > Frankly, the sooner the WG understands and accepts that basic fact,
> > the sooner we can move to a viable solution - one which does not
> > redefine CE from the semantics established by RFC-3168 and RFC-
> > 8511, and hence does not place burdens on networks which have no
> > interest in the L4S experiment.
> 
> I think we need to be clear that I understand the proposal is to an 
> Internet-wide experimental deployment.

Have single network experiments been attempted? Have cooperating
peering network experiments been attempted? Why is an *Internet-wide*
experiment the appropriate next step, especially when potential
detrimental impacts to traffic flows of non-participating networks &
hosts have been identified?

> If succesful, I'd expect we'll discover things in the deployment
> that 
> will make us consider new things, before this is approved as a PS.
> The 
> WG might later decide to obsolete RFC-3168, or L4S, or neither, or
> both. 
> That will be to decide in future. In persepective, about 15 years
> passed 
> before the previous EXP use of ECT(1) was made made historic,
> enabling this.
> 
> Gorry

Is there a planned deadline to evaluate the results of the experiment,
and either advance to PS or revert the allocation of ECT(1)?


Regards,

// Steve