Re: [irtf-discuss] Update on "Challenges for the Internet Routing Infrastructure Introduced by Changes"

Adrian Farrel <adrian@olddog.co.uk> Wed, 24 February 2021 12:44 UTC

Return-Path: <adrian@olddog.co.uk>
X-Original-To: irtf-discuss@ietfa.amsl.com
Delivered-To: irtf-discuss@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 1A7723A14E9; Wed, 24 Feb 2021 04:44:15 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.895
X-Spam-Level:
X-Spam-Status: No, score=-1.895 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_MSPIKE_H3=0.001, RCVD_IN_MSPIKE_WL=0.001, SPF_HELO_NONE=0.001, SPF_NONE=0.001, URIBL_BLOCKED=0.001] 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 meLIJukULYPr; Wed, 24 Feb 2021 04:44:13 -0800 (PST)
Received: from mta7.iomartmail.com (mta7.iomartmail.com [62.128.193.157]) (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 D59183A150B; Wed, 24 Feb 2021 04:44:12 -0800 (PST)
Received: from vs1.iomartmail.com (vs1.iomartmail.com [10.12.10.121]) by mta7.iomartmail.com (8.14.4/8.14.4) with ESMTP id 11OCiALS022313; Wed, 24 Feb 2021 12:44:10 GMT
Received: from vs1.iomartmail.com (unknown [127.0.0.1]) by IMSVA (Postfix) with ESMTP id 3790022042; Wed, 24 Feb 2021 12:44:10 +0000 (GMT)
Received: from asmtp3.iomartmail.com (unknown [10.12.10.224]) by vs1.iomartmail.com (Postfix) with ESMTPS id 215D22203C; Wed, 24 Feb 2021 12:44:10 +0000 (GMT)
Received: from LAPTOPK7AS653V ([87.112.199.121]) (authenticated bits=0) by asmtp3.iomartmail.com (8.14.4/8.14.4) with ESMTP id 11OCi9De022162 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=NO); Wed, 24 Feb 2021 12:44:09 GMT
Reply-To: <adrian@olddog.co.uk>
From: "Adrian Farrel" <adrian@olddog.co.uk>
To: "'Marie-Jose Montpetit'" <marie@mjmontpetit.com>
Cc: <irtf-discuss@irtf.org>, <draft-king-irtf-challenges-in-routing@ietf.org>
References: <045901d70a93$ec0ffce0$c42ff6a0$@olddog.co.uk> <B3F2CF00-C94C-4C3A-8426-4FD55880888B@mjmontpetit.com>
In-Reply-To: <B3F2CF00-C94C-4C3A-8426-4FD55880888B@mjmontpetit.com>
Date: Wed, 24 Feb 2021 12:44:08 -0000
Organization: Old Dog Consulting
Message-ID: <049c01d70aaa$bf2107d0$3d631770$@olddog.co.uk>
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: quoted-printable
X-Mailer: Microsoft Outlook 16.0
Thread-Index: AQI8Hz1G+cdq9uaCtk3gZoyE7oR9BwKqI5dJqYfD4cA=
Content-Language: en-gb
X-Originating-IP: 87.112.199.121
X-Thinkmail-Auth: adrian@olddog.co.uk
X-TM-AS-GCONF: 00
X-TM-AS-Product-Ver: IMSVA-9.0.0.1623-8.2.0.1013-25942.003
X-TM-AS-Result: No--14.765-10.0-31-10
X-imss-scan-details: No--14.765-10.0-31-10
X-TMASE-Version: IMSVA-9.0.0.1623-8.2.1013-25942.003
X-TMASE-Result: 10--14.765100-10.000000
X-TMASE-MatchedRID: Ync95tbzDRlRn39sim9+cHFPUrVDm6jtkYC3rjkUXRLGK4L6OtQr98Vj EEE40kDNmecayrqVrlPfqpuToKGfMAS4DkGAkuCFrdLFFKR7dukXhPQmXMtIyzVBg7smZGiBg7p bZl2hQA7gQGH3/X1T4wLwEvuDLcjRTsc3oPKh4gqt395w6mpxFU+crEA4+nhZOUKaYbjwR6QEO2 pVgUq2iTDOSE1tWAtW8x9+tEL3Ui0EyPQwW5BBavwmuD7e97dbojX2kLuehY01Tv8wGe5RLliqA yk7LkbknOr799mASi20ERzR/OrQGEH/R3q75ysciH95tLFH8efg02I3oyGU8AdcjVKj+329EbWh nkYtojp77Vq1NOEIOqi6MVStwLNWFLh3aaMYdQkdDctFr7spHPmXzp/t9r6wpfrLsBaiuHlYadf 7BXyIe+mMX0Ro5a7jbPO1y2ZZZ85QiSZ/HI8mBDBocZwAmaRtC/ExpXrHizxPQiQvzFiGeAFfgV TicugFYxgIpWpoIv8HwP5zLNLkyShU8bkobVgsxLSBAmMhEpIRAd26BrSMwoVquVYFwXAmg7Ewp QTK2LurB8A7wes0q1TT9WlYkydOYFa6Zcuh7o2DrIfvx7TmRUzzNX6FuGYDPSeoGnZSYhyWOXCI oLL/x9HPoS42fTCw8oMDsCeMQed2yPj1XXqlKQchQmx6NZX0GIMg4+U4kbW13P7r6QU9aDS1nqz P7DGCykFTxE/Vm67W2lLeYy+8t2YBzHSlpuK6TvKpZzlxUs99LQinZ4QefNQdB5NUNSsiU2Qzq8 5WfnB0HSe131POnuJGF26G8SWypfzLa08EuFCoDfxQcH/uxSbCIdA/hcvasZk8jxsgK6DG1wYEQ jAH1ZqidEYv/YgQ
X-TMASE-SNAP-Result: 1.821001.0001-0-1-12:0,22:0,33:0,34:0-0
Archived-At: <https://mailarchive.ietf.org/arch/msg/irtf-discuss/Xhzs5s5K1NLeIMuhsqyOZnWJZws>
Subject: Re: [irtf-discuss] Update on "Challenges for the Internet Routing Infrastructure Introduced by Changes"
X-BeenThere: irtf-discuss@irtf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: IRTF general and new-work discussion list <irtf-discuss.irtf.org>
List-Unsubscribe: <https://www.irtf.org/mailman/options/irtf-discuss>, <mailto:irtf-discuss-request@irtf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/irtf-discuss/>
List-Post: <mailto:irtf-discuss@irtf.org>
List-Help: <mailto:irtf-discuss-request@irtf.org?subject=help>
List-Subscribe: <https://www.irtf.org/mailman/listinfo/irtf-discuss>, <mailto:irtf-discuss-request@irtf.org?subject=subscribe>
X-List-Received-Date: Wed, 24 Feb 2021 12:44:15 -0000

Thanks Marie-José,

Yes, this is certainly work that is needed.

We should present a little more about the architectures that people are considering, and the split of address/metadata/data is a helpful distinction. In fact, the metadata/data is largely historic, and we're looking at the various proposals to encode information in the address. Perhaps our draft currently has too much information about previous work, and not enough about current proposals -- work in progress!

I just want to note that it's not our new addressing 😊. What we're trying to do is collect information about all of the proposals and research that are out there.

The pointer to COIN is helpful, and we'll try to factor something into the next revision.

Best,
Adrian

-----Original Message-----
From: Marie-Jose Montpetit <marie@mjmontpetit.com> 
Sent: 24 February 2021 12:24
To: adrian@olddog.co.uk
Cc: irtf-discuss@irtf.org; draft-king-irtf-challenges-in-routing@ietf.org
Subject: Re: [irtf-discuss] Update on "Challenges for the Internet Routing Infrastructure Introduced by Changes"


I think it would be nice if your document was putting more focus on the proposed architecture and the applications that could need your new addressing. Also I think there are three layers here: address (IP or IP like), meta data and data. Of course you could route on any or all of them which I think is what you propose. And the more you go from simple ‘this is where I want to go’ into how and why complexity increases and speed goes down. Maybe you should also highlight performance aspects  more clearly. There is a link to the COIN work where discovery and essentially in-router computations would add new potential for routing algorithms.

mjm

Marie-José Montpetit, Ph.D.

> On Feb 24, 2021, at 5:01 AM, Adrian Farrel <adrian@olddog.co.uk> wrote:
> 
> Hi all,
> 
> We received some feedback (thanks) on draft-king-irtf-challenges-in-routing
> and posted an update at
> https://datatracker.ietf.org/doc/draft-king-irtf-challenges-in-routing/
> 
> To recap, the draft presents a brief survey of technologies related to IP
> address semantic proposals and describes the challenges to the existing
> routing system that they present. It then summarizes the opportunities for
> research into new or modified routing protocols to make use of new address
> semantics. It does not pass comment on the advisability or practicality of
> any of the solutions.
> 
> The intention, therefore, is to try to get a broad view of the work that has
> been done, is in hand, and needs to be done. The document is not attempting
> a detailed technical analysis, and is not proposing technical solutions.
> 
> We would really appreciate comments, feedback, and pointers to related work.
> 
> Thanks,
> Adrian (for the authors)