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

Marie-Jose Montpetit <marie@mjmontpetit.com> Wed, 24 February 2021 12:23 UTC

Return-Path: <marie@mjmontpetit.com>
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 1113A3A14E0 for <irtf-discuss@ietfa.amsl.com>; Wed, 24 Feb 2021 04:23:45 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.897
X-Spam-Level:
X-Spam-Status: No, score=-1.897 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, SPF_HELO_NONE=0.001, SPF_NONE=0.001, URIBL_BLOCKED=0.001] autolearn=unavailable autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=mjmontpetit-com.20150623.gappssmtp.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 zUhWdZukBx4v for <irtf-discuss@ietfa.amsl.com>; Wed, 24 Feb 2021 04:23:43 -0800 (PST)
Received: from mail-qt1-x82b.google.com (mail-qt1-x82b.google.com [IPv6:2607:f8b0:4864:20::82b]) (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 368243A14E1 for <irtf-discuss@irtf.org>; Wed, 24 Feb 2021 04:23:43 -0800 (PST)
Received: by mail-qt1-x82b.google.com with SMTP id b3so1202973qtj.10 for <irtf-discuss@irtf.org>; Wed, 24 Feb 2021 04:23:43 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=mjmontpetit-com.20150623.gappssmtp.com; s=20150623; h=content-transfer-encoding:mime-version:subject:from:in-reply-to:cc :date:message-id:references:to; bh=BhRFclKHKTSoGRUdZMV9uh9GQvQy7Gv0Jwym63LR8Hc=; b=cfvV7zOt34bG4+G/kzRaoHiY6wMyKQO0uQIfwRA+qD7+F5r377ZQiMRZSn2JbJGoUX QNwIbQ00fPrAmIVe3+4fGMmgsjQWy5GdiJe/NDDvTrv30LL+d95oiEMHmarVCFZSDmVR cQCxbRR5RWgoQLh4LkGw1OBaZ//lmph1wDlWB6JHm59TenSWYiyE9ct6CrHp3eJHMXWG /YSwguGXCac31RoCnYA44unV7i4RzCS8HLwwFY+fv+dTRJ0l3SsBU+6LCpUVOy1g7q8Q DTs1csoP4MraIAxFR8YhBmXxKgTOknenjNorIRfE7bTQUpjr4Ioxtm+E8sa7cFtw6Iv5 IaTg==
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=BhRFclKHKTSoGRUdZMV9uh9GQvQy7Gv0Jwym63LR8Hc=; b=g2mBQecPYgqDEBKKW+I9+jFO2xlII+lFiItpmISHd8v932TmwsnY3WvEgreWVf6TKL t0PqnRDUhinkOUlMmRyoh3DqkT2fMUknRxv++lSorOxcxV3YVnyEIu4V1rm7P8wsNA1Y A8Rq3G8HrAq7hbHzAkSupvOk4FrrZyTIuLhsd5ncoAlz3PtiCm/adc9QswwcjdQcSmTF O2hUsnbKr4e8WXrWvG0MXGPl/zihDzTZ2O8rImUOmznBrtrBcDRZoyaSKfNTFpodf4uX pEet2vyg2iRsrDgx3o3J5sLDd6Y6oZa8s/Vwa2qfQy5s9DROt3/yrnDFx3jV0J28nc+8 itPA==
X-Gm-Message-State: AOAM532awn26/8Qt4SkbisjZKVjRuBxLYyzjSsqC2rZo528Pt26IXtoD oPiKYDpFMVBOpb0zRzaAV51cwoU6WABa1A==
X-Google-Smtp-Source: ABdhPJwmao2yeHaMi28anmBYrAkgh9LQpFyEvikEmeb5i4g8hSYw+LR8+kXCaw/NvEi3AyMs9xkxZg==
X-Received: by 2002:ac8:5197:: with SMTP id c23mr9260485qtn.126.1614169421727; Wed, 24 Feb 2021 04:23:41 -0800 (PST)
Received: from [192.168.1.130] (modemcable193.226-80-70.mc.videotron.ca. [70.80.226.193]) by smtp.gmail.com with ESMTPSA id b190sm1334806qkg.103.2021.02.24.04.23.41 (version=TLS1_3 cipher=TLS_AES_128_GCM_SHA256 bits=128/128); Wed, 24 Feb 2021 04:23:41 -0800 (PST)
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: quoted-printable
Mime-Version: 1.0 (1.0)
From: Marie-Jose Montpetit <marie@mjmontpetit.com>
In-Reply-To: <045901d70a93$ec0ffce0$c42ff6a0$@olddog.co.uk>
Cc: irtf-discuss@irtf.org, draft-king-irtf-challenges-in-routing@ietf.org
Date: Wed, 24 Feb 2021 07:23:40 -0500
Message-Id: <B3F2CF00-C94C-4C3A-8426-4FD55880888B@mjmontpetit.com>
References: <045901d70a93$ec0ffce0$c42ff6a0$@olddog.co.uk>
To: adrian@olddog.co.uk
X-Mailer: iPad Mail (18B92)
Archived-At: <https://mailarchive.ietf.org/arch/msg/irtf-discuss/z0It1WyRB0rwSTs4Qhopcup_8Zc>
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:23:45 -0000

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)