IETF Logo Mail Archive

Re: [Int-area] Continuing the addressing discussion: what is an address anyway?

Eliot Lear <lear@lear.ch> Tue, 25 January 2022 07:46 UTC

Return-Path: <lear@lear.ch>
X-Original-To: int-area@ietfa.amsl.com
Delivered-To: int-area@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 3067D3A0D98; Mon, 24 Jan 2022 23:46:25 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.056
X-Spam-Level:
X-Spam-Status: No, score=0.056 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_ADSP_ALL=0.8, DKIM_INVALID=0.1, DKIM_SIGNED=0.1, HTML_MESSAGE=0.001, NICE_REPLY_A=-0.714, SPF_PASS=-0.001, T_SPF_HELO_PERMERROR=0.01, URIBL_BLOCKED=0.001, URI_DOTEDU=1.659] autolearn=no autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=fail (1024-bit key) reason="fail (message has been altered)" header.d=lear.ch
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 XjP0cBl76EPd; Mon, 24 Jan 2022 23:46:20 -0800 (PST)
Received: from upstairs.ofcourseimright.com (upstairs.ofcourseimright.com [185.32.222.29]) (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 D1E7B3A0DF1; Mon, 24 Jan 2022 23:46:18 -0800 (PST)
Received: from [IPV6:2001:420:c0c0:1011::1] ([IPv6:2001:420:c0c0:1011:0:0:0:1]) (authenticated bits=0) by upstairs.ofcourseimright.com (8.15.2/8.15.2/Debian-18) with ESMTPSA id 20P7kFJ6148076 (version=TLSv1.3 cipher=TLS_AES_128_GCM_SHA256 bits=128 verify=NO); Tue, 25 Jan 2022 08:46:16 +0100
Authentication-Results: upstairs.ofcourseimright.com; dmarc=none (p=none dis=none) header.from=lear.ch
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=lear.ch; s=upstairs; t=1643096776; bh=9ukah82Pwx69v1EqZfehYBT5eePBPnE/pPZHOx9i0yA=; h=Date:To:References:From:Subject:In-Reply-To:From; b=D1794HEwPsUw0cBxTuf/03mvWbe0q3GWbEeDheguYwIb8WDRu+uK6SXqby0tDpgwR FKlKMzME3QgO+E9RKsq9Y4CpueNyQthHCi8DYZx6C6zedqmBqZoKvQheWs0FoYPhlG e5149g2Lz/7lwyWGWD610vWZILJR7zbWfHsx7m4Y=
Message-ID: <7de0956f-3fde-1543-405b-b635f6e69362@lear.ch>
Date: Tue, 25 Jan 2022 08:46:13 +0100
MIME-Version: 1.0
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.15; rv:91.0) Gecko/20100101 Thunderbird/91.5.0
Content-Language: en-US
To: Dirk Trossen <dirk.trossen=40huawei.com@dmarc.ietf.org>, "Int-area@ietf.org" <Int-area@ietf.org>
References: <57c643c667d94a77b9917bb17dc142a5@huawei.com>
From: Eliot Lear <lear@lear.ch>
In-Reply-To: <57c643c667d94a77b9917bb17dc142a5@huawei.com>
Content-Type: multipart/signed; micalg="pgp-sha256"; protocol="application/pgp-signature"; boundary="------------t2IXUZqLoD8Je1ltvWcG4OeF"
Archived-At: <https://mailarchive.ietf.org/arch/msg/int-area/-eCqhu0ZIEnFrbbCJ0qcRYDniO0>
Subject: Re: [Int-area] Continuing the addressing discussion: what is an address anyway?
X-BeenThere: int-area@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: IETF Internet Area WG Mailing List <int-area.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/int-area>, <mailto:int-area-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/int-area/>
List-Post: <mailto:int-area@ietf.org>
List-Help: <mailto:int-area-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/int-area>, <mailto:int-area-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 25 Jan 2022 07:46:26 -0000

Hi Dirk,

On 25.01.22 08:19, Dirk Trossen wrote:
>
> Hence, I would suggest that any answers to the question above ought to 
> be guided by what we (as users) want from the network, e.g., in terms 
> of reachability, privacy, security, exposure of desired capabilities 
> and possibly more.
>
The orthodoxy here is the seminal work of Shoch[1]. And of course 
there's Saltzer et al.[2]  The assumptions being made today by different 
players are indeed all over the map.  Routing is a function of the 
network.  Or is it?  Privacy is something the endpoint must manage.  Or 
is it?  So I like your approach for discussion.

Eliot

[1] http://www.postel.org/ien/txt/ien19.txt
[2] http://web.mit.edu/Saltzer/www/publications/endtoend/endtoendA4.pdf

v2.23.0 | Report a Bug | By Email