IETF Logo Mail Archive

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

Antoine FRESSANCOURT <antoine.fressancourt@huawei.com> Mon, 07 March 2022 13:47 UTC

Return-Path: <antoine.fressancourt@huawei.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 4DCE83A1061 for <int-area@ietfa.amsl.com>; Mon, 7 Mar 2022 05:47:05 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.908
X-Spam-Level:
X-Spam-Status: No, score=-1.908 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_MSPIKE_H4=0.001, RCVD_IN_MSPIKE_WL=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, T_SCC_BODY_TEXT_LINE=-0.01] autolearn=ham autolearn_force=no
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 7fwZJVDUhJa1 for <int-area@ietfa.amsl.com>; Mon, 7 Mar 2022 05:47:02 -0800 (PST)
Received: from frasgout.his.huawei.com (frasgout.his.huawei.com [185.176.79.56]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 393383A1077 for <Int-area@ietf.org>; Mon, 7 Mar 2022 05:47:02 -0800 (PST)
Received: from fraeml707-chm.china.huawei.com (unknown [172.18.147.201]) by frasgout.his.huawei.com (SkyGuard) with ESMTP id 4KC08d6Sf6z6H74Y; Mon, 7 Mar 2022 21:45:37 +0800 (CST)
Received: from lhreml722-chm.china.huawei.com (10.201.108.73) by fraeml707-chm.china.huawei.com (10.206.15.35) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256) id 15.1.2308.21; Mon, 7 Mar 2022 14:46:58 +0100
Received: from lhreml726-chm.china.huawei.com (10.201.108.77) by lhreml722-chm.china.huawei.com (10.201.108.73) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256) id 15.1.2308.21; Mon, 7 Mar 2022 13:46:57 +0000
Received: from lhreml726-chm.china.huawei.com ([10.201.108.77]) by lhreml726-chm.china.huawei.com ([10.201.108.77]) with mapi id 15.01.2308.021; Mon, 7 Mar 2022 13:46:57 +0000
From: Antoine FRESSANCOURT <antoine.fressancourt@huawei.com>
To: Toerless Eckert <tte@cs.fau.de>
CC: Jens Finkhaeuser <jens@interpeer.io>, Brian E Carpenter <brian.e.carpenter@gmail.com>, "Int-area@ietf.org" <Int-area@ietf.org>, Dirk Trossen <dirk.trossen=40huawei.com@dmarc.ietf.org>
Thread-Topic: [Int-area] Continuing the addressing discussion: what is an address anyway?
Thread-Index: AdgRu64YB5eA1MJiQEiPQSsbU7BQswAA/ICABvLpPoAABrn7gABImqoAABbfaYAAJh6fAAARYhYAAIBWYAAAA+TlsAADciUAAACp4jAAAReJAAAALicQ
Date: Mon, 07 Mar 2022 13:46:57 +0000
Message-ID: <112b8d13bf6b405096bc1223cf649c05@huawei.com>
References: <Yh5M18z2/YVfpW7i@faui48e.informatik.uni-erlangen.de> <A771FFF8-43A8-4D84-8B6E-A3E7AF96644E@gmail.com> <YiBhOKIK9bMqwx0a@faui48e.informatik.uni-erlangen.de> <385CF477-C876-482F-ADFE-DAAD6CA7BAEC@gmail.com> <YiH6iHwv+U9QFA06@faui48e.informatik.uni-erlangen.de> <499a3364-7ea5-4268-cce3-43f010f36a72@gmail.com> <Gpm-qFUmOVey9DYUJV6S_UNYb02p7ANbT8rEjy8JA54B__1YeX6Uny2E16uEg_o-R7v9CWPdDbyOgNW7nJyACAbx7Ok99Q-zad1EsgYBerc=@interpeer.io> <d128f1fc15824cae9012ab5f30358221@huawei.com> <YiX9tJpx31UKp823@faui48e.informatik.uni-erlangen.de> <5600131c158945848385d92c7132a96a@huawei.com> <YiYJfIAxI5rxXdE/@faui48e.informatik.uni-erlangen.de>
In-Reply-To: <YiYJfIAxI5rxXdE/@faui48e.informatik.uni-erlangen.de>
Accept-Language: fr-FR, en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [10.201.117.184]
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-CFilter-Loop: Reflected
Archived-At: <https://mailarchive.ietf.org/arch/msg/int-area/cqNghkI7DdOzkQ_AEFvGKM5q2F4>
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: Mon, 07 Mar 2022 13:47:06 -0000

See inline,

Best regards,

Antoine

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

So, when i am roaming from another country, would that carrier not try to connect to my home carrier by the combination of MCC and MNC ?

That feature to me would make MCC+MNC similar to a routing prefix, right ?

[AFT] The main difference in my view is that in mobile roaming ecosystems, you can't really route a packet to a specific network operator by going through a kind of transit provider that would take all the roaming requests for a single country (or at least this is how I remember things). I miss the possibility to aggregate part of the routing prefixes in IPvX to consider this an addressing scheme. From a topological standpoint, it means that you can't really use a transit intermediate that goes somewhat in the direction of the destination to route roaming traffic (at least in my view).

v2.23.0 | Report a Bug | By Email