Re: [arch-d] FYI: closure of the IAB Stack Evolution program

John Leslie <john@jlc.net> Sun, 25 August 2019 19:27 UTC

Return-Path: <john@jlc.net>
X-Original-To: architecture-discuss@ietfa.amsl.com
Delivered-To: architecture-discuss@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 00BDD120058 for <architecture-discuss@ietfa.amsl.com>; Sun, 25 Aug 2019 12:27:06 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.899
X-Spam-Level:
X-Spam-Status: No, score=-1.899 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=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 TZsccHJs1Dnj for <architecture-discuss@ietfa.amsl.com>; Sun, 25 Aug 2019 12:27:04 -0700 (PDT)
Received: from mailhost.jlc.net (mailhost.jlc.net [199.201.159.4]) by ietfa.amsl.com (Postfix) with ESMTP id 4D74412004D for <architecture-discuss@iab.org>; Sun, 25 Aug 2019 12:27:04 -0700 (PDT)
Received: by mailhost.jlc.net (Postfix, from userid 104) id 6123D908893; Sun, 25 Aug 2019 15:26:54 -0400 (EDT)
Date: Sun, 25 Aug 2019 15:26:54 -0400
From: John Leslie <john@jlc.net>
To: Fernando Gont <fgont@si6networks.com>
Cc: John Leslie <john@jlc.net>, Ted Hardie <ted.ietf@gmail.com>, Chris Morrow <morrowc@ops-netman.net>, architecture-discuss@iab.org
Message-ID: <20190825192654.GA78819@verdi>
References: <d5009253-4884-9f1f-66e7-1159e85524b9@si6networks.com> <770822F2-688F-44EA-A6A1-7E7EDBFAA989@trammell.ch> <cece8133-6b69-a677-52fc-a7fb4c7d5136@si6networks.com> <64E3A59C-8709-41E0-B74F-C036E4481AE4@apple.com> <f3645e11-d823-4308-3f51-6f2da5e33180@si6networks.com> <87imqnvhui.wl-morrowc@ops-netman.net> <CA+9kkMDWk3kmYOZ8Zz+BjUZG0+sshQJjR9pYt-NgL8umqpMtWQ@mail.gmail.com> <eb2bc35f-ea95-69b9-5163-baded0c47478@si6networks.com> <20190825164839.GA77144@verdi> <1b872d8d-e932-d212-478d-4cc0da1255ec@si6networks.com>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Disposition: inline
In-Reply-To: <1b872d8d-e932-d212-478d-4cc0da1255ec@si6networks.com>
User-Agent: Mutt/1.6.1 (2016-04-27)
Archived-At: <https://mailarchive.ietf.org/arch/msg/architecture-discuss/IjpcTn6BR1AITdsCjQY1_LI5dNA>
Subject: Re: [arch-d] FYI: closure of the IAB Stack Evolution program
X-BeenThere: architecture-discuss@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: open discussion forum for long/wide-range architectural issues <architecture-discuss.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/architecture-discuss>, <mailto:architecture-discuss-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/architecture-discuss/>
List-Post: <mailto:architecture-discuss@ietf.org>
List-Help: <mailto:architecture-discuss-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/architecture-discuss>, <mailto:architecture-discuss-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sun, 25 Aug 2019 19:27:06 -0000

Fernando Gont <fgont@si6networks.com> wrote:
> On 25/8/19 19:48, John Leslie wrote:
> >    However, architecture-discuss@iab.org _really_shouldn't_ abandon hope
>> of deploying a new transport protocol: it's _hard_; it may not happen in
>> my lifetime; but the Internet, or its replacement, _will_ need a new
>> transport procotol some day...
> 
> I tend to associate hope with religion, rather than engineering. :-)

   Actually, religion is about "belief," not "hope".

   "Hope" is about imagining a future; and implies that it's a future we
_might_ agree to work towards. (A religious person might pray for God's
help; but _anyone_ could keep the idea in mind in case something changes.)

> Certainly, hope will not get us there. Probably nothing will... but if
> there's any chance that something that will, it's certainly not 'hope'
> but some sort of action -- whatever it is.

   I won't argue lingustics here. You're welcome to substitute your own
word. My point is that we shouldn't rule out a future where we _can_
deploy a new transport protocol, even if we believe it "too hard" right
now.

--
John Leslie <john@jlc.net>