Re: [arch-d] possible new IAB programme on Internet resilience

"John Levine" <johnl@taugh.com> Sun, 29 December 2019 17:34 UTC

Return-Path: <johnl@iecc.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 676DC12007C for <architecture-discuss@ietfa.amsl.com>; Sun, 29 Dec 2019 09:34:24 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.75
X-Spam-Level:
X-Spam-Status: No, score=-1.75 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HEADER_FROM_DIFFERENT_DOMAINS=0.25, SPF_HELO_NONE=0.001, SPF_PASS=-0.001] autolearn=no autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1536-bit key) header.d=iecc.com header.b=h9h5ZutU; dkim=pass (1536-bit key) header.d=taugh.com header.b=rYaJhzYg
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 BIFMYAzCRfgJ for <architecture-discuss@ietfa.amsl.com>; Sun, 29 Dec 2019 09:34:23 -0800 (PST)
Received: from gal.iecc.com (gal.iecc.com [IPv6:2001:470:1f07:1126:0:43:6f73:7461]) (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 D351712006E for <architecture-discuss@ietf.org>; Sun, 29 Dec 2019 09:34:22 -0800 (PST)
Received: (qmail 18737 invoked from network); 29 Dec 2019 17:34:21 -0000
DKIM-Signature: v=1; a=rsa-sha256; c=simple; d=iecc.com; h=date:message-id:from:to:cc:subject:in-reply-to:mime-version:content-type:content-transfer-encoding; s=492f.5e08e39d.k1912; i=printer-iecc.com@submit.iecc.com; bh=lP3IXsau8fxPm6Y5/SxBfUiRjozrlON637DavDAZ8oA=; b=h9h5ZutUOlHuDo96fFWNxOR+9VGzF9PF9nNyut/MIqpPEzY3NkhgdYmaw60P4LdJPlSl6XCMbSygtMU6bQSCcriEPjCRRpwOeg9VOkRVk8SDIQu1SYWFU13znzLNviaROEP7P9+wwgK8E545Zii4fgcgQAhPsK0L+kchWbQMy6bz5nSyqA5BK2w6t1no5+DyPkMsHNz37pOCwRBefslJzHMTPLFw3fFOqMMQ0JSxIXGyf9Qq643Va2p5y8cgh87w
DKIM-Signature: v=1; a=rsa-sha256; c=simple; d=taugh.com; h=date:message-id:from:to:cc:subject:in-reply-to:mime-version:content-type:content-transfer-encoding; s=492f.5e08e39d.k1912; olt=printer-iecc.com@submit.iecc.com; bh=lP3IXsau8fxPm6Y5/SxBfUiRjozrlON637DavDAZ8oA=; b=rYaJhzYgfIYac4zHkTPvREKVUU6uw+ndW4U5j0INnjcZkv/axtnA8Z5JQWnOM4EGap/8f59eYP3p5qVLwFyHc8fgLMmPNPxHBwKJznhAOYrOQCcW97szg+P3nQwD1l/3KPpWY9Lein4dAiyyK8gDUv2h+9d0eDvQIp+QU930YPT9iahdvgPcCUFIjb0/+2smRV6BJVzGcBwVBvsTB/SJyarx2nk2riDlnE2tNfHlzJqo2m/NnjV/yVIUjzEwrpE+
Received: from ary.qy ([IPv6:2001:470:1f07:1126::78:696d:6170]) by imap.iecc.com ([IPv6:2001:470:1f07:1126::78:696d:6170]) with ESMTPSA (TLS1.2 ECDHE-RSA AES-256-GCM AEAD, printer@iecc.com) via TCP6; 29 Dec 2019 17:34:21 -0000
Received: by ary.qy (Postfix, from userid 501) id BEC0311CFC60; Sun, 29 Dec 2019 12:34:20 -0500 (EST)
Date: 29 Dec 2019 12:34:20 -0500
Message-Id: <20191229173420.BEC0311CFC60@ary.qy>
From: "John Levine" <johnl@taugh.com>
To: architecture-discuss@ietf.org
Cc: tte@cs.fau.de
In-Reply-To: <20191229170740.GI8801@faui48f.informatik.uni-erlangen.de>
Organization: Taughannock Networks
X-Headerized: yes
Mime-Version: 1.0
Content-type: text/plain; charset=utf-8
Content-transfer-encoding: 8bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/architecture-discuss/RAimcwb_YLMNUaJarCj1cUKegKE>
Subject: Re: [arch-d] possible new IAB programme on Internet resilience
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, 29 Dec 2019 17:34:25 -0000

In article <20191229170740.GI8801@faui48f.informatik.uni-erlangen.de> you write:
>When reading all the threads about policy i was wondering what this could
>mean technically to IETF/IAB work, and the best i could come up with
>was the part of our standards that allow to express policies.

A lot of our designs have implicit policy models.  The most obvious is
the DNS.  Since it's one tree with a single root, it was inevitable
that we would end up with something like ICANN to manage that root.

The fixed size of the IPv4 address space and our failure to produce a
migration path to a successor made it equally inevitable that IP
addresses would be worth money and people will buy and sell and steal
them.  The RIRs' effectiveness in managing all this is, ah, mixed.

>I do wonder though what specifically the technologies for IAB/IETF
>could be to express policies regarding resilience, and i think it
>would be interesting to outline/document those. Especially when its
>more than any of aforementioned policies to select a single path
>or control what traffic policies should be applied to it.

Right.  I hope we can learn from our experience.

R's,
John