Re: [Int-area] draft-eckert-intarea-functional-addr-internets-00.txt

Stewart Bryant <stewart.bryant@gmail.com> Tue, 13 July 2021 05:57 UTC

Return-Path: <stewart.bryant@gmail.com>
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 A27F13A1865 for <int-area@ietfa.amsl.com>; Mon, 12 Jul 2021 22:57:40 -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, FREEMAIL_FROM=0.001, RCVD_IN_DNSWL_NONE=-0.0001, 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=gmail.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 XXKxJyr7erv4 for <int-area@ietfa.amsl.com>; Mon, 12 Jul 2021 22:57:35 -0700 (PDT)
Received: from mail-wm1-x32b.google.com (mail-wm1-x32b.google.com [IPv6:2a00:1450:4864:20::32b]) (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 0EBDA3A1862 for <int-area@ietf.org>; Mon, 12 Jul 2021 22:57:34 -0700 (PDT)
Received: by mail-wm1-x32b.google.com with SMTP id u5-20020a7bc0450000b02901480e40338bso1001427wmc.1 for <int-area@ietf.org>; Mon, 12 Jul 2021 22:57:34 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=content-transfer-encoding:mime-version:subject:from:in-reply-to:cc :date:message-id:references:to; bh=W0oWcdxtMeNwQN0UHYMqHhgKF2b1x3XXnnL+UdG7Kmc=; b=me4Eu/tgF/QaXdJpmHr+t1ZYcnq/gHzDQljaxK72zJyx7sQR86vHpe7XvVv5c0XJFS ol356HOgS07sHUk1MA+GRMYi9YHcqE/Rwkl53ye7TkdOuwxLbP/NpmpAdkOiPNGQtpGj 4yoz5e8lQpTPiF0qHnTooXOmxSzFJ2JwsC57LjyBe/aD9TZW2JcOuPtPA5aFhScVcjMz hPL61N4827rnw9zFXsatqkUo9LN4yFs6Cfi6VnFtF+rQqq2BHQrEBaKrq7iaJIVxOcY0 g4G1ovPPMWuNOso3xNBcmSulNNaL43Ol1ZuLAPTsmhS7lOiSLT+tbuaWzRCRs6SzA50I XJFg==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:content-transfer-encoding:mime-version:subject :from:in-reply-to:cc:date:message-id:references:to; bh=W0oWcdxtMeNwQN0UHYMqHhgKF2b1x3XXnnL+UdG7Kmc=; b=SDPtjlX+yC+x20uI1yz3mmLov7ASP8pmd+I6/MgQOVH/kSjZLcZM5bH07Kx24hbF/K ISibN+QThwsB5NvgiP4rAzKyT4pOZ+yoV/V0uZuNaFd7wBfoqv/640oCs8hXyR6678LW sho/SiqU5lAjxbmAIv1mQcItxeVWlWc5KI2f6BmeCGhxCj2YwLryNBPWr4Fa7riMzibd skdQL05/ts+Te4BQuVMZ4VXprQ/g4x0FwO6V/8weSx2tsCReFdsjgFH27S47EKptaS4K fdRcuGwfdYU1zLlKMXGnhhGMJZEOU4cbLPNIQkUBFn0IlIRX1CQ6WUY4UJbr1rsqS+qj a+zQ==
X-Gm-Message-State: AOAM531sfbY+Wm3yh2KLatzSyi6tUVSZNJMrkpp+se+bSdj7TSs90aUZ wi0cItKZ9DrJDUMUwvykjQXaICjhslE=
X-Google-Smtp-Source: ABdhPJxc0tjWTA8v4QKuON83jCsfjO3tgB51uZXkkLWbmwBywxACgjhgCS0JN7tLrcvB9QdD44fbBQ==
X-Received: by 2002:a1c:80cd:: with SMTP id b196mr656154wmd.179.1626155852565; Mon, 12 Jul 2021 22:57:32 -0700 (PDT)
Received: from smtpclient.apple ([2a00:23c5:3395:c901:54f8:3062:a8aa:f2ff]) by smtp.gmail.com with ESMTPSA id a10sm16599380wrm.12.2021.07.12.22.57.32 (version=TLS1_3 cipher=TLS_AES_128_GCM_SHA256 bits=128/128); Mon, 12 Jul 2021 22:57:32 -0700 (PDT)
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: quoted-printable
Mime-Version: 1.0 (1.0)
From: Stewart Bryant <stewart.bryant@gmail.com>
In-Reply-To: <20210712230411.GB24216@faui48e.informatik.uni-erlangen.de>
Cc: int-area@ietf.org
Date: Tue, 13 Jul 2021 06:57:31 +0100
Message-Id: <BC56402F-D785-405F-A770-206DFE208D40@gmail.com>
References: <20210712230411.GB24216@faui48e.informatik.uni-erlangen.de>
To: Toerless Eckert <tte@cs.fau.de>
X-Mailer: iPad Mail (18F72)
Archived-At: <https://mailarchive.ietf.org/arch/msg/int-area/V4bIL6Q8i-FZ1kbxpvS_y9zie9A>
Subject: Re: [Int-area] draft-eckert-intarea-functional-addr-internets-00.txt
X-BeenThere: int-area@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: IETF Internet Area 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, 13 Jul 2021 05:57:41 -0000

An interesting draft Toerless.

From a background POV it is worth noting ISO 8473 which is in deployment with multi-type variable length address.

It is also worth noting that SA is different from DA to the extent that it may not belong in the network layer header of the outgoing packet. The SA is arguably a function of the payload and the application. Indeed some MPLS OAM solutions do just that by making the return address implicit in the arrival LSP, or a parameter in a payload TLV. SA as in IP is arguably just a convenience for a simplified method of operating an application.

Stewart

Sent from my iPad

> On 13 Jul 2021, at 00:05, Toerless Eckert <tte@cs.fau.de> wrote:
> Dear Int-area
> 
> As attached below, i have written up an idea about why and how variable-length
> addresses in the network layer would be useful for many limited domain internetworks,
> but also how they could provide a simple and easily extensible framework to
> add additional semantics (the likes of multicast, BIER, ICN), and also make it easier 
> to express the programmability that SRv6 introduced.
> 
> Would very much welcome discussion/feedback, and will be asking for a slot
> to present/discuss this int-area 111.
> 
> Note that the -00 writeup is mostly inspirational for what i think the cool
> things one could do with it are and to explain the concepts.
> 
> Obviously, if/when there is interest in this
> direction, the harder work of figuring out how to best introduce this
> incrementally, and ideally backward compatible into existing networks wold
> be the next big set of items to work out.
> 
> Cheers
>    Toerless
> 
> On Mon, Jul 12, 2021 at 01:00:25PM -0700, internet-drafts@ietf.org wrote:
>> A new version of I-D, draft-eckert-intarea-functional-addr-internets-00.txt
>> has been successfully submitted by Toerless Eckert and posted to the
>> IETF repository.
>> 
>> Name:        draft-eckert-intarea-functional-addr-internets
>> Revision:    00
>> Title:        Functional Addressing (FA) for internets with Independent Network Address Spaces (IINAS)
>> Document date:    2021-07-12
>> Group:        Individual Submission
>> Pages:        30
>> URL:            https://www.ietf.org/archive/id/draft-eckert-intarea-functional-addr-internets-00.txt
>> Status:         https://datatracker.ietf.org/doc/draft-eckert-intarea-functional-addr-internets/
>> Htmlized:       https://datatracker.ietf.org/doc/html/draft-eckert-intarea-functional-addr-internets
>> 
>> 
>> Abstract:
>>   Recent work has raised interest in exploring network layer addressing
>>   that is more flexible than fixed-length addressing as used in IPv4
>>   (32 bit) and IPv6 (128 bit).
>> 
>>   The reasons for the interest include both support for multiple and
>>   potentially novel address semantics, but also optimizations of
>>   addressing for existing semantics such as unicast tailored not for
>>   the global Internet but to better support private networks / limited
>>   domains.
>> 
>>   This memo explores in the view of the author yet little explored
>>   reasons for more flexible addresses namely the problems and
>>   opportunities for Internetworking with Independent Network Address
>>   Spaces (IINAS).
>> 
>>   To better enable such internetworks, this memo proposes a framework
>>   for a Functional Addressing model.  This model also intends to
>>   support several other addressing goals including programmability and
>>   multiple semantics.
>> 
>> 
>> 
>> 
>> The IETF Secretariat
> 
> -- 
> ---
> tte@cs.fau.de
> 
> _______________________________________________
> Int-area mailing list
> Int-area@ietf.org
> https://www.ietf.org/mailman/listinfo/int-area