Re: [irtf-discuss] Update on "Challenges for the Internet Routing Infrastructure Introduced by Changes"
Toerless Eckert <tte@cs.fau.de> Wed, 24 February 2021 18:44 UTC
Return-Path: <eckert@i4.informatik.uni-erlangen.de>
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 C60E63A1962
for <irtf-discuss@ietfa.amsl.com>; Wed, 24 Feb 2021 10:44:03 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.649
X-Spam-Level:
X-Spam-Status: No, score=-1.649 tagged_above=-999 required=5
tests=[BAYES_00=-1.9, HEADER_FROM_DIFFERENT_DOMAINS=0.25,
SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001]
autolearn=no 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 GhBASXJCWByp for <irtf-discuss@ietfa.amsl.com>;
Wed, 24 Feb 2021 10:44:01 -0800 (PST)
Received: from faui40.informatik.uni-erlangen.de
(faui40.informatik.uni-erlangen.de [131.188.34.40])
(using TLSv1.2 with cipher ADH-AES256-GCM-SHA384 (256/256 bits))
(No client certificate requested)
by ietfa.amsl.com (Postfix) with ESMTPS id 824C63A17DE
for <irtf-discuss@irtf.org>; Wed, 24 Feb 2021 10:44:00 -0800 (PST)
Received: from faui48f.informatik.uni-erlangen.de
(faui48f.informatik.uni-erlangen.de [IPv6:2001:638:a000:4134::ffff:52])
by faui40.informatik.uni-erlangen.de (Postfix) with ESMTP id 1534E54804B;
Wed, 24 Feb 2021 19:43:55 +0100 (CET)
Received: by faui48f.informatik.uni-erlangen.de (Postfix, from userid 10463)
id 12C0F440163; Wed, 24 Feb 2021 19:43:55 +0100 (CET)
Date: Wed, 24 Feb 2021 19:43:55 +0100
From: Toerless Eckert <tte@cs.fau.de>
To: Marie-Jose Montpetit <marie@mjmontpetit.com>
Cc: adrian@olddog.co.uk, irtf-discuss@irtf.org,
draft-king-irtf-challenges-in-routing@ietf.org
Message-ID: <20210224184355.GQ35983@faui48f.informatik.uni-erlangen.de>
References: <045901d70a93$ec0ffce0$c42ff6a0$@olddog.co.uk>
<B3F2CF00-C94C-4C3A-8426-4FD55880888B@mjmontpetit.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=iso-8859-1
Content-Disposition: inline
Content-Transfer-Encoding: 8bit
In-Reply-To: <B3F2CF00-C94C-4C3A-8426-4FD55880888B@mjmontpetit.com>
User-Agent: Mutt/1.10.1 (2018-07-13)
Archived-At: <https://mailarchive.ietf.org/arch/msg/irtf-discuss/gl8Tlpc4dPwPjgsIOli3mbNqYAw>
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 18:44:04 -0000
Hi Marie,
Would you like to contribute such content ?
Cheers
Toerless
On Wed, Feb 24, 2021 at 07:23:40AM -0500, Marie-Jose Montpetit wrote:
>
> 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)
--
---
tte@cs.fau.de
- [irtf-discuss] Update on "Challenges for the Inte… Adrian Farrel
- Re: [irtf-discuss] Update on "Challenges for the … Marie-Jose Montpetit
- Re: [irtf-discuss] Update on "Challenges for the … Adrian Farrel
- Re: [irtf-discuss] Update on "Challenges for the … Marie-Jose Montpetit
- Re: [irtf-discuss] Update on "Challenges for the … Adrian Farrel
- Re: [irtf-discuss] Update on "Challenges for the … Toerless Eckert