Re: [arch-d] How old is too old and what this means for product lifecycles? Re: [Last-Call] [TLS] Last Call: <draft-ietf-tls-oldversions-deprecate-09.txt> (Deprecating TLSv1.0 and TLSv1.1) to Best Current Practice
Randy Bush <randy@psg.com> Sat, 05 December 2020 18:10 UTC
Return-Path: <randy@psg.com>
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 732FC3A0AA0; Sat, 5 Dec 2020 10:10:08 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.9
X-Spam-Level:
X-Spam-Status: No, score=-1.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, 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 cxWi-IXpNK4i; Sat, 5 Dec 2020 10:10:07 -0800 (PST)
Received: from ran.psg.com (ran.psg.com [IPv6:2001:418:8006::18]) (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 AF8E73A0A9C; Sat, 5 Dec 2020 10:10:06 -0800 (PST)
Received: from localhost ([127.0.0.1] helo=ryuu.rg.net) by ran.psg.com with esmtp (Exim 4.90_1) (envelope-from <randy@psg.com>) id 1klc0P-0005sV-QS; Sat, 05 Dec 2020 18:10:01 +0000
Date: Sat, 05 Dec 2020 10:10:01 -0800
Message-ID: <m2zh2sktty.wl-randy@psg.com>
From: Randy Bush <randy@psg.com>
To: Eliot Lear <lear@cisco.com>
Cc: Ted Lemon <mellon@fugue.com>, "Ackermann, Michael" <MAckermann@bcbsm.com>, iotops@ietf.org, architecture-discuss@iab.org
In-Reply-To: <80F697E4-B225-49E0-8271-CDAB66E42A95@cisco.com>
References: <160496076356.8063.5138064792555453422@ietfa.amsl.com> <SN6PR02MB4512B95842251AE4C04B199CC3F30@SN6PR02MB4512.namprd02.prod.outlook.com> <BYAPR14MB31765FD24F4DFD90F81AEE2BD7F30@BYAPR14MB3176.namprd14.prod.outlook.com> <SN6PR02MB4512CBA9E4BF6AAC778BC674C3F30@SN6PR02MB4512.namprd02.prod.outlook.com> <DM6PR14MB31789349B737961728B7691ED7F30@DM6PR14MB3178.namprd14.prod.outlook.com> <CACsn0ckvoqZ5-JPRkOXp2Mw2zeTOdyCYLvX1NV1waJ-yidTwMQ@mail.gmail.com> <SN6PR02MB45129E647485BA5794D5CF4EC3F20@SN6PR02MB4512.namprd02.prod.outlook.com> <MWHPR02MB2464CD5D5B7568E9EAC58B26D6F20@MWHPR02MB2464.namprd02.prod.outlook.com> <DM6PR14MB3178EC0521427BF7C3523CACD7F10@DM6PR14MB3178.namprd14.prod.outlook.com> <CAChr6SzvQK+exfgYEwfVNknMjr-Y-UJ4A7k0DkOkL9wmLQ84aQ@mail.gmail.com> <MWHPR02MB246499F35613820D45EB55AAD6F10@MWHPR02MB2464.namprd02.prod.outlook.com> <DM6PR14MB3178A0C152A746E41C6A01C6D7F10@DM6PR14MB3178.namprd14.prod.outlook.com> <f8486514-9726-68d0-2bc8-dccd4293017e@cs.tcd.ie> <DM6PR14MB317843CA2B3D67F6660F4F0DD7F10@DM6PR14MB3178.namprd14.prod.outlook.com> <127BB8C9-679E-48C1-8617-C6092AEE9914@fugue.com> <DM6PR14MB3178C1F8B6E4FD6E9FD9C8C4D7F10@DM6PR14MB3178.namprd14.prod.outlook.com> <8E6EB6FF-E83B-44B5-A0A2-7499678DC6B6@fugue.com> <DM6PR14MB317817FD62369A8E0FF93CA8D7F10@DM6PR14MB3178.namprd14.prod.outlook.com> <77363965-99A5-4790-B40B-011827C8D113@fugue.com> <80F697E4-B225-49E0-8271-CDAB66E42A95@cisco.com>
User-Agent: Wanderlust/2.15.9 (Almost Unreal) Emacs/26.3 Mule/6.0 (HANACHIRUSATO)
MIME-Version: 1.0 (generated by SEMI-EPG 1.14.7 - "Harue")
Content-Type: text/plain; charset="US-ASCII"
Archived-At: <https://mailarchive.ietf.org/arch/msg/architecture-discuss/sOvqqYExokeprRyC7G2eHlWvkv8>
Subject: Re: [arch-d] How old is too old and what this means for product lifecycles? Re: [Last-Call] [TLS] Last Call: <draft-ietf-tls-oldversions-deprecate-09.txt> (Deprecating TLSv1.0 and TLSv1.1) to Best Current Practice
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: Sat, 05 Dec 2020 18:10:09 -0000
[ where are we going and why am i in this handbasket? ] < rant > when you have a plant which can turn out a jillion new thingies with a day of set-up, the costs of the infrastructure to securely maintain and upgrade them in the field for three, let alone 20, years is astronomical in comparison. now multiply that by a new and different thingie being manufactured next month. now multiply that by a few hundred manufacturers. perhaps the only way to understand in one's gut the scale of this problem is to spend a few weeks in shenzhen. to improve the math one would have to amortize the cost of maintenance over many many flavors and makers of thingies. so the acme thingie mfr, and the hackme thingie mfr, and the ... need to have a common code base and upgrade infrastructure. this is seen as stifling innovation in a highly innovative and competitive space. the time from first pitch to vc term sheet and funding has gone down to two weeks. and the resulting landfill rivals the problem of plastics in the oceans. android is the only example i can think of with a multi-manufacturer upgrade and maintenance infrastructure; and it is notoriously horrid. researchers publish papers on how bad it is. but credit to android for trying. long way to go. alternatively, one could be in a regulated environment, e.g. military, medical, etc., where multiplying the cost of the thingie by orders of magnitude is seen as worth the social benefit. but, even in these environments, do not underestimate the attack surface due to sloppy ops. we, for some value of we, are used building a reliable network from unreliable components. distributed protocols are the key. that is a different universe from a reliable and long-term maintainable thingie. and maybe we don't want to use our favorite vendors' boat anchors as examples. randy, who still has a curta and a k&e log log duplex decitrig
- [arch-d] How old is too old and what this means f… Eliot Lear
- Re: [arch-d] How old is too old and what this mea… Ted Lemon
- Re: [arch-d] How old is too old and what this mea… Randy Bush
- Re: [arch-d] How old is too old and what this mea… Ted Lemon
- Re: [arch-d] How old is too old and what this mea… Randy Bush
- Re: [arch-d] How old is too old and what this mea… Ted Lemon
- Re: [arch-d] How old is too old and what this mea… Randy Bush
- Re: [arch-d] How old is too old and what this mea… Randy Bush
- Re: [arch-d] How old is too old and what this mea… Eric Rescorla
- Re: [arch-d] How old is too old and what this mea… Randy Bush
- Re: [arch-d] How old is too old and what this mea… Christian Huitema
- Re: [arch-d] [Iotops] How old is too old and what… Amyas Phillips
- Re: [arch-d] [Iotops] How old is too old and what… Eliot Lear
- Re: [arch-d] [Iotops] How old is too old and what… Toerless Eckert
- Re: [arch-d] [Iotops] How old is too old and what… Henning Schulzrinne
- Re: [arch-d] [Iotops] How old is too old and what… Sávyo Vinícius
- Re: [arch-d] [Iotops] How old is too old and what… Randy Bush
- Re: [arch-d] [Iotops] How old is too old and what… Toerless Eckert
- Re: [arch-d] [Iotops] How old is too old and what… John Levine
- Re: [arch-d] [Iotops] How old is too old and what… Henning Schulzrinne
- Re: [arch-d] [Iotops] How old is too old and what… Michael Richardson
- Re: [arch-d] [Iotops] How old is too old and what… Michael Richardson
- Re: [arch-d] [Iotops] How old is too old and what… Toerless Eckert
- Re: [arch-d] [Iotops] How old is too old and what… Sávyo Vinícius
- Re: [arch-d] [Iotops] How old is too old and what… Randy Bush
- Re: [arch-d] [Iotops] How old is too old and what… Eliot Lear