Re: [External] Request for information - Challenges in routing related to semantic addressing

Robert Raszuk <robert@raszuk.net> Fri, 02 April 2021 20:48 UTC

Return-Path: <robert@raszuk.net>
X-Original-To: routing-discussion@ietfa.amsl.com
Delivered-To: routing-discussion@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id F04F23A231D for <routing-discussion@ietfa.amsl.com>; Fri, 2 Apr 2021 13:48:09 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.098
X-Spam-Level:
X-Spam-Status: No, score=-2.098 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, HTML_MESSAGE=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=raszuk.net
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 Oul-atohEBfx for <routing-discussion@ietfa.amsl.com>; Fri, 2 Apr 2021 13:48:05 -0700 (PDT)
Received: from mail-lf1-x12c.google.com (mail-lf1-x12c.google.com [IPv6:2a00:1450:4864:20::12c]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 3BDA43A226E for <routing-discussion@ietf.org>; Fri, 2 Apr 2021 13:48:05 -0700 (PDT)
Received: by mail-lf1-x12c.google.com with SMTP id i26so9050289lfl.1 for <routing-discussion@ietf.org>; Fri, 02 Apr 2021 13:48:05 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=raszuk.net; s=google; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=qtFYyeY0XEi7kxvwWb2UnUKgmI6Wy7Z7jD3OlKse9X4=; b=CFNV0izU9IXYXdIpnmsnohz3JIPxFq9/JyU1DNUFL4aU/K1R8uC7eCdrZ8XsgMBhjC Jcef3QrGRZfHA6SgeKeu49irx3Igf2OE4jPSw+6oLLkhkzHdBVwIaskrkM+tjjmf9MgB KeqYplM910NOuRmvt/X/g/157LDOMXmMC+W/NfwZlxj/DfHzX5FTHtznskYnS1F4AGj7 lAw4O+mj6i5918nYyL9zaa28e1pS4bT9gQc4lMB7RoWdllcO5TME+ICB/psf/3Jbawvj 6KbgYoWcTkYg05O+rtCm8088mFDpKU+12bvgYovdKTfIMTRGO1OBbLQByv3aPdDneOdO em4w==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=qtFYyeY0XEi7kxvwWb2UnUKgmI6Wy7Z7jD3OlKse9X4=; b=ow0vKxnl+czDxsURgET6plLhuWkkWu2G9f4MEEeLm14kPNEF3G5OYlTHqazOY0c/ZP OOOepI6Xz+m4FrSCJt2ei+Qnwe/ydoAXa2ztLbspIhIl6f+i3s0utENhLmXhsdOgOHEL G1RZskKFkNyMmZFpOO8H6uUPzLswQW8dCsdYB31cEBnp2/JZOY2rNtFAuRKog4kv3dkC Q7jRguaOpIZyoHjEpmR8pAxLlZ63zSUhNblAdLOxAjA0ly8FSJY76qotHaNIRqf93Dr1 c2RrXoo+2v5py6CgsCSHQg6X7YSL2xs260Hrzmhd8S/BM5MNZgXF9tgUA1tGowHSY93U iGAg==
X-Gm-Message-State: AOAM533mCblskLH0CIgfhWHPo+PFp3GeE0zdt4QJ3d3L4ZWGqH26cFNM GEOO1og94Af7vqPFGxfjM7hmd76zAyA2rd4cmHE8Ng==
X-Google-Smtp-Source: ABdhPJwXsoHpRFs3zm5WGndtt60a+hK1ZZAE/ydEXG76iSadvWvMj33FGfepmFRBvMNnK3FB3v4mszj0N7r8SkzHmaU=
X-Received: by 2002:ac2:46db:: with SMTP id p27mr9880879lfo.396.1617396482794; Fri, 02 Apr 2021 13:48:02 -0700 (PDT)
MIME-Version: 1.0
References: <02d401d701fd$25905a90$70b10fb0$@olddog.co.uk> <CADnDZ88mA7B_a1MUYnXSviD5wjNL3sbqaqrbK0u3NXi6OqeNAA@mail.gmail.com> <CWXP265MB2087CD3D4A4B7EB370EBD534D6889@CWXP265MB2087.GBRP265.PROD.OUTLOOK.COM> <006800FC-8628-4F09-92DB-745E75B6DB4F@apnic.net> <79C06A8C-3998-4426-98A4-934C76F92A44@gigix.net> <7C4F0D54-7DBF-4BB8-9338-0690342E5638@apnic.net>
In-Reply-To: <7C4F0D54-7DBF-4BB8-9338-0690342E5638@apnic.net>
From: Robert Raszuk <robert@raszuk.net>
Date: Fri, 02 Apr 2021 22:47:51 +0200
Message-ID: <CAOj+MME0tRoUQs=WxTDXrGKuVjQU+A6Wt8uoPVyFgk1jND0jyQ@mail.gmail.com>
Subject: Re: [External] Request for information - Challenges in routing related to semantic addressing
To: Geoff Huston <gih@apnic.net>
Cc: Luigi Iannone <ggx@gigix.net>, "King, Daniel" <d.king@lancaster.ac.uk>, adrian <adrian@olddog.co.uk>, "draft-king-irtf-challenges-in-routing@ietf.org" <draft-king-irtf-challenges-in-routing@ietf.org>, "routing-discussion@ietf.org" <routing-discussion@ietf.org>
Content-Type: multipart/alternative; boundary="000000000000d176aa05bf037626"
Archived-At: <https://mailarchive.ietf.org/arch/msg/routing-discussion/RlqgVzmTQClBf1r-15Xqwm0jtUE>
X-BeenThere: routing-discussion@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Routing Area General mailing list <routing-discussion.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/routing-discussion>, <mailto:routing-discussion-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/routing-discussion/>
List-Post: <mailto:routing-discussion@ietf.org>
List-Help: <mailto:routing-discussion-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/routing-discussion>, <mailto:routing-discussion-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 02 Apr 2021 20:48:10 -0000

>
> Similarly, I'm aware of some (many?) ways to use the 64 bit interface
> identifier, some of which embed one-off tokens in the field in an extreme
> case of privacy addressing.


Indeed and I am also aware of such use cases.

See I am actually not sure what this discussion is all about :)  Orthodox
v6-ers claim that you only can assign IPv6 addresses to the interfaces. And
frankly this is ok. Except since early moments router's interfaces were
both physical and logical. And in the latter case logical interface is
nothing else then instantiation of some semantics. It can be simple
loopback, it can be virtual tunnel termination, it can be dial-up, it also
can be service chain anchor. In modern slide decks it is called SR
endpoint.

So last 64 bits give you great place to express to the destination which
attracts traffic to such address on how you want this packet to be handled.

Such indication can be implicit or explicit - I think some people do not
like to see it explicit. But honestly it should be in best interest of the
IETF to make it as explicit as folks want to disclose it for better
interoperability across vendors, wider adoption, solicitation of more
comments etc ... .

Happy Easter Holidays to all,
Robert