Re: [Coin] FW: New Version Notification for draft-trossen-rtgwg-routing-beyond-reachability-00.txt

Jon Crowcroft <Jon.Crowcroft@cl.cam.ac.uk> Fri, 11 February 2022 09:23 UTC

Return-Path: <Jon.Crowcroft@cl.cam.ac.uk>
X-Original-To: coin@ietfa.amsl.com
Delivered-To: coin@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 649013A09A5 for <coin@ietfa.amsl.com>; Fri, 11 Feb 2022 01:23:43 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.339
X-Spam-Level:
X-Spam-Status: No, score=-0.339 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_BLOCKED=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001, URI_DOTEDU=1.659] autolearn=no autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=cl.cam.ac.uk
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 U6UfScf-354J for <coin@ietfa.amsl.com>; Fri, 11 Feb 2022 01:23:38 -0800 (PST)
Received: from mta1.cl.cam.ac.uk (mta1.cl.cam.ac.uk [IPv6:2a05:b400:110::25:1]) (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 78E503A053F for <coin@irtf.org>; Fri, 11 Feb 2022 01:23:37 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=cl.cam.ac.uk; s=mta3; h=Message-Id:Date:Content-Transfer-Encoding: Content-ID:Content-Type:MIME-Version:References:In-reply-to:Subject:cc:To: From:Sender:Reply-To:Content-Description:Resent-Date:Resent-From: Resent-Sender:Resent-To:Resent-Cc:Resent-Message-ID:List-Id:List-Help: List-Unsubscribe:List-Subscribe:List-Post:List-Owner:List-Archive; bh=G66rOt2osDmgFpKs8Tw00H0GLi7dSIf/byhPvBW62pc=; t=1644571418; x=1645435418; b=C/GzsfCxfvBbCxAvAW2EkZpoRjbs0KhW2kJlNsj/SSO3i5x84Uw9171RWBt7zW/TmCkLqG0j1Wh 4UsHYluHy8ZivIwoNWqUJ4XDGxaYoqvP8cA3s/urBeZ+dOrxYUHU95iiMV/AgSPdwUMNFf5PRl15w DTy6E34rvXdsF3pssEQSSUAPEPEvg0Xbj6J8tB2Loa8TC+I1SM4Ehie/vvS+Mvw80GDl85aqrcwGR KfXfig+XfO6zC9bUUsJjJK8GOHy+/PFJpPYXCmYzhnikvOo/OUPED1HA8GLHsrWCVAJ+ZsZf3UsiU qP9C7eTqC8qizYdo+KRQLHaOY48KfCidZ5BQ==;
Received: from slogin-new.cl.cam.ac.uk ([2a05:b400:110::22:98] helo=svr-ssh-0.cl.cam.ac.uk) (dnseec=no) by mta1.cl.cam.ac.uk:587 [2a05:b400:110::25:1] with esmtp (Exim 4.94) id 1nIS9L-0002AT-2Q (envelope-from <Jon.Crowcroft@cl.cam.ac.uk>); Fri, 11 Feb 2022 09:23:31 +0000
From: Jon Crowcroft <Jon.Crowcroft@cl.cam.ac.uk>
To: Luigi Iannone <ggx@gigix.net>
cc: coin@irtf.org, Jon Crowcroft <Jon.Crowcroft@cl.cam.ac.uk>
In-reply-to: <0400CCC4-DD33-4280-8298-9C3BF8B02CBE@gigix.net>
References: <0400CCC4-DD33-4280-8298-9C3BF8B02CBE@gigix.net>
Comments: In-reply-to Luigi Iannone <ggx@gigix.net> message dated "Wed, 09 Feb 2022 11:56:55 +0100."
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-ID: <1954093.1644571410.1@svr-ssh-0.cl.cam.ac.uk>
Content-Transfer-Encoding: quoted-printable
Date: Fri, 11 Feb 2022 09:23:31 +0000
Message-Id: <E1nIS9L-0002AT-2Q@mta1.cl.cam.ac.uk>
Archived-At: <https://mailarchive.ietf.org/arch/msg/coin/eVOQd8lD_W4Hxs5Y12soz7l62lg>
Subject: Re: [Coin] FW: New Version Notification for draft-trossen-rtgwg-routing-beyond-reachability-00.txt
X-BeenThere: coin@irtf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: "COIN: Computing in the Network" <coin.irtf.org>
List-Unsubscribe: <https://www.irtf.org/mailman/options/coin>, <mailto:coin-request@irtf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/coin/>
List-Post: <mailto:coin@irtf.org>
List-Help: <mailto:coin-request@irtf.org?subject=help>
List-Subscribe: <https://www.irtf.org/mailman/listinfo/coin>, <mailto:coin-request@irtf.org?subject=subscribe>
X-List-Received-Date: Fri, 11 Feb 2022 09:23:44 -0000

so the checklist for any new routing approach is the three M's

-Mobility
-Multihoming
-Multicast

extra marks  are avaialble for:

security:
+typically integrity of routes
+mitigate or don't make worse DoS
+retain as much (optinal) anonimity as people want

policy:
by which i mean anything that isn't just optimisation against some performance metric.

so my fave work out of all the future internet work 20 years back was I3
http://i3.cs.berkeley.edu/publications/papers/i3-sigcomm.pdf
as it asically spoke to the three Ms directly, by putting
rendezvous points in the net as a first class piece of the architecture
(obviously RPs had shown up in multicast as cores or in PIM already
but this generalised that) - then it falls to the designer to addres the extra mark
challenges, once you put a 3rd party in the net, you create a lovely pivot for all sorts of
attacks - hence it behoves us in groups like coin, to think about how you secure this
and it is now a three body problem, which we all know to be very much harder than two.

and that really is in-net compute in a nutshell...


> 
> In light of recent discussion on this mailing list the document below 
> announced on the RTGWG mailing list may be of some interest here as well 
> (IMO).
> 
> Ciao
> 
> L.
> 
> Dirk Trossen <dirk.trossen@huawei.com> Tue, 08 February 2022 13:20 
> UTCShow header
> Dear all,
> 
> We have posted the draft below to seed a wider RTG WG discussion on 
> routing evolution, based on various ongoing interactions and discussions 
> within the IETF and IRTF on this topic.
> 
> This draft recognizes the ongoing evolution of Internet routing based on 
> the many extensions to the original reachability-focused purpose of IP 
> routing, identifies issues with the approach of developing those 
> extensions, and proposes a way forward in direct relation to the RTG WG 
> charter.
> 
> We are seeking feedback and comments from the WG on the topic of routing 
> evolution, particularly on the suggested actions as well as issues 
> identified in the draft.
> 
> Best,
> 
> 
> Dirk (on behalf of the authors)
> 
> -----Original Message-----
> From: internet-drafts@ietf.org [mailto:internet-drafts@ietf.org]
> Sent: 08 February 2022 14:10
> To: Zhe Lou <zhe.lou@huawei.com>om>gt;om>; Dirk Trossen 
> <dirk.trossen@huawei.com>om>gt;om>; Sheng Jiang <jiangsheng@huawei.com>om>gt;om>; Zhe 
> Lou <zhe.lou@huawei.com>
> Subject: New Version Notification for 
> draft-trossen-rtgwg-routing-beyond-reachability-00.txt
> 
> 
> A new version of I-D, 
> draft-trossen-rtgwg-routing-beyond-reachability-00.txt
> has been successfully submitted by Dirk Trossen and posted to the IETF 
> repository.
> 
> Name:           draft-trossen-rtgwg-routing-beyond-reachability
> Revision:       00
> Title:          Continuing to Evolve Internet Routing Beyond 'Mere' 
> Reachability
> Document date:  2022-02-08
> Group:          Individual Submission
> Pages:          25
> URL:            
> https://www.ietf.org/archive/id/draft-trossen-rtgwg-routing-beyond-reachability-00.txt
> Status:         
> https://datatracker.ietf.org/doc/draft-trossen-rtgwg-routing-beyond-reachability/
> Htmlized:       
> https://datatracker.ietf.org/doc/html/draft-trossen-rtgwg-routing-beyond-reachability
> 
> 
> Abstract:
>    This document discusses the evolution of the Internet routing system
>    beyond mere reachability.  We observe, through examples of past
>    development, that such evolution has been taking place to improve on
>    capabilities of the Internet, deal with more complicated network
>    deployments and cater to changing requirements by end users as well
>    as novel and emerging applications.
> 
>    For achieving a routing system that serves more than a singular
>    reachability purpose, more information is taken into account when
>    performing the purpose-specific functions.  Such extra information
>    can be obtained by extending current routing protocols to exchange
>    more information or by carrying that information within packets.
> 
>    This document is intended to seed discussions of how the observed
>    evolution of the Internet's routing system can continue, what issues
>    may occur when simply continuing the current approach for achieving
>    routing beyond 'mere' reachability and what may be needed to address
>    those issues.  Ultimately, however, this document recognizes the
>    positive impact that moving beyond reachability has brought to the
>    Internet and will continue to do so.
> 
> 
> 
> 
> The IETF Secretariat
> 
> 
> --
> Coin mailing list
> Coin@irtf.org
> https://www.irtf.org/mailman/listinfo/coin
>