Re: [arch-d] [Iotops] How old is too old and what this means for product lifecycles?

Eliot Lear <lear@cisco.com> Wed, 09 December 2020 06:50 UTC

Return-Path: <lear@cisco.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 3E7913A0D06 for <architecture-discuss@ietfa.amsl.com>; Tue, 8 Dec 2020 22:50:17 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -9.6
X-Spam-Level:
X-Spam-Status: No, score=-9.6 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIMWL_WL_MED=-0.001, 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_PASS=-0.001, URIBL_BLOCKED=0.001, USER_IN_DEF_DKIM_WL=-7.5] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=cisco.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 U7TMkhfOCQVG for <architecture-discuss@ietfa.amsl.com>; Tue, 8 Dec 2020 22:50:16 -0800 (PST)
Received: from aer-iport-2.cisco.com (aer-iport-2.cisco.com [173.38.203.52]) (using TLSv1.2 with cipher DHE-RSA-SEED-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 8A72F3A074E for <architecture-discuss@iab.org>; Tue, 8 Dec 2020 22:50:15 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=1240; q=dns/txt; s=iport; t=1607496615; x=1608706215; h=from:message-id:mime-version:subject:date:in-reply-to:cc: to:references; bh=VhPFwg8rM9Ll5av1CzEb4VjfWqZCJjPd+F4Lfc0ndSk=; b=bgZ48bUax5QmY4Wnhu+0kd1EzKvAcHKNW8/ccZtxWS3/eMQ661KlR/OJ B7dmVBwuoc6dvnassbuMXkVXw3xkiyUrIfb0baEnDd2TiohH2CMwwZhvP GFfnMiwnZqdcKyfn/MzRDTOedj00h5VcGRXbfqt54lHp3WsqXGm1K75ta A=;
X-Files: signature.asc : 488
X-IPAS-Result: =?us-ascii?q?A0DcBQDActBflxbLJq1iHAEBAQEBAQcBARIBAQQEAQFAg?= =?us-ascii?q?U+DH1cBIBIujG9TiCecMwQHAQEBCgMBASUKBAEBg0sBAXMBAQgCgX8mOBMCA?= =?us-ascii?q?wEBAQMCAwEBAQEFAQEBAgEGBBQBAQEBAQEBAYY2DIVyAQEBAQIBeQULCxguV?= =?us-ascii?q?wYTgyYBgmYgD6t6dIE0hVeFHgoGgTiBU4wLggCBOByCJy4+iAiCLASDeoFBZ?= =?us-ascii?q?5wJnBiCfoMjgTeWZgMfgxIBj2GPQbExg20CBAYFAhWBbSGBWTMaCBsVZQGCP?= =?us-ascii?q?j4SGQ2OO4NXillAAzA3AgYKAQEDCYpqAQE?=
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-AV: E=Sophos;i="5.78,404,1599523200"; d="asc'?scan'208";a="31758964"
Received: from aer-iport-nat.cisco.com (HELO aer-core-1.cisco.com) ([173.38.203.22]) by aer-iport-2.cisco.com with ESMTP/TLS/DHE-RSA-SEED-SHA; 09 Dec 2020 06:50:11 +0000
Received: from [10.61.196.80] ([10.61.196.80]) by aer-core-1.cisco.com (8.15.2/8.15.2) with ESMTPS id 0B96oAv6027868 (version=TLSv1.2 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=NO); Wed, 9 Dec 2020 06:50:10 GMT
From: Eliot Lear <lear@cisco.com>
Message-Id: <302A37B6-4A3C-4CDE-8C29-410A982296FA@cisco.com>
Content-Type: multipart/signed; boundary="Apple-Mail=_E3D66599-7099-4DF1-8E91-D3272F86F042"; protocol="application/pgp-signature"; micalg=pgp-sha256
Mime-Version: 1.0 (Mac OS X Mail 13.4 \(3608.120.23.2.4\))
Date: Wed, 9 Dec 2020 07:50:09 +0100
In-Reply-To: <m2im9chsne.wl-randy@psg.com>
Cc: architecture-discuss@iab.org, iotops@ietf.org, Ted Lemon <mellon@fugue.com>
To: Randy Bush <randy@psg.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> <m2zh2sktty.wl-randy@psg.com> <277E5229-EFCC-4758-B4F6-6B159212BA14@ambotec.org> <50213DD8-794D-4180-A918-A6B94FDC61C3@cisco.com> <m2im9chsne.wl-randy@psg.com>
X-Mailer: Apple Mail (2.3608.120.23.2.4)
X-Outbound-SMTP-Client: 10.61.196.80, [10.61.196.80]
X-Outbound-Node: aer-core-1.cisco.com
Archived-At: <https://mailarchive.ietf.org/arch/msg/architecture-discuss/8j1oGOtiPVwWM6KH11-BMSQbe-c>
Subject: Re: [arch-d] [Iotops] How old is too old and what this means for product lifecycles?
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: Wed, 09 Dec 2020 06:50:17 -0000

Hi Randy

> On 8 Dec 2020, at 22:52, Randy Bush <randy@psg.com> wrote:
> 
> https://www.wired.com/story/amnesia33-iot-vulnerabilitiesmay-never-get-fixed/


Yes.  That article hits on nearly every security and incentive problem the IOT industry has.

Eliot