RE: [External] Re: Request for information - Challenges in routing related to semantic addressing

"King, Daniel" <d.king@lancaster.ac.uk> Mon, 15 February 2021 10:40 UTC

Return-Path: <d.king@lancaster.ac.uk>
X-Original-To: routing-discussion@ietfa.amsl.com
Delivered-To: routing-discussion@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 4ED373A1108; Mon, 15 Feb 2021 02:40:22 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.1
X-Spam-Level:
X-Spam-Status: No, score=0.1 tagged_above=-999 required=5 tests=[DKIM_SIGNED=0.1, DKIM_VALID=-0.1, HTML_MESSAGE=0.001, HTTPS_HTTP_MISMATCH=0.1, RCVD_IN_MSPIKE_H2=-0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=no autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=livelancsac.onmicrosoft.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 BiE_4Fa2Xpx2; Mon, 15 Feb 2021 02:40:20 -0800 (PST)
Received: from GBR01-CWL-obe.outbound.protection.outlook.com (mail-eopbgr110092.outbound.protection.outlook.com [40.107.11.92]) (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 8FA253A1106; Mon, 15 Feb 2021 02:40:19 -0800 (PST)
ARC-Seal: i=1; a=rsa-sha256; s=arcselector9901; d=microsoft.com; cv=none; b=TouOEnkE41T8FoZQvND2ljDmNTFTIttIToKyodUA7VLQFVaEZdxwLTsJVGmfHD6F9vKeIclLLV9tWVryDETknXBzmO6RP9moiaIENCKKTV3rJFYv++PmWGT1nonVqaXsbu8Jp1ruPdvDk878wbomCVFOeeLJmnrl6fYOycjNtNOBz81GM0u+nkBC0BsoZBi9cXFuUCwVprQXCrCgawtBS1w5oZIl9oi0W+nQ7oeaB31uGesOpb9npPuoBZv8KbsMwEs2QjQ3DwTxQsbNwSG/RyePyFIrjQ7WuhY+H1S4N7iNZDA8TINvqc3h78iNwbm65GNWcn/oK7KmPeYk0gUiaA==
ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=microsoft.com; s=arcselector9901; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-SenderADCheck; bh=lPIdcmGQt2BMA9zXivrxZvjBFwCrNmRHPtw+1VWsK5Y=; b=f0H3AMvGnqSqDRDpNKKKO9s8fT7TxDW4ZW8OOlHSG/zA9H81JW1aWYhY8+xVNQ76aOG8Kxszht5FOckr5li9XUcNumZ4OClQ3MznmbG2qJFQH4QK1kuWVk4qoGnRzjnI4PdCLn8ZTBORZaxx5ERH37UKx8KBhb9HdK7qwMpwzpKiRLwFjtaJUuZLL0OBC7p5CkjF9IObP/4heAykoMUQlmwvCo83u410f5y0CcYusOsqxZO1nzjLCAI7ub2KU4ZUnZRbdw1MtrPL6cpiFoVdnB7dLCHHkUVs3ilcYMrKWlz9eQLmCQCkM48JcmclZ1jZ+uNF3+wMR+1Uswz/goQL5w==
ARC-Authentication-Results: i=1; mx.microsoft.com 1; spf=pass smtp.mailfrom=lancaster.ac.uk; dmarc=pass action=none header.from=lancaster.ac.uk; dkim=pass header.d=lancaster.ac.uk; arc=none
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=livelancsac.onmicrosoft.com; s=selector2-livelancsac-onmicrosoft-com; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-SenderADCheck; bh=lPIdcmGQt2BMA9zXivrxZvjBFwCrNmRHPtw+1VWsK5Y=; b=vIcqgZI/rlHbE6iYhF8cAuXY+liyZmUgfikl+D3khBpUetX7KDvXo2OXN+REKiM0J0ARXA8b2UQJXBX4yK76fny3rQmPOsTR3q+Q6MYAxHoU98lSYIoSEZh+mwBRuIHSABagYYaSKQ0Bjt/gYrN17u1sCPUeW2Gyu3rhvDmN3Ao=
Received: from CWXP265MB2087.GBRP265.PROD.OUTLOOK.COM (2603:10a6:400:84::14) by CWXP265MB1608.GBRP265.PROD.OUTLOOK.COM (2603:10a6:401:48::9) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.3846.39; Mon, 15 Feb 2021 10:40:12 +0000
Received: from CWXP265MB2087.GBRP265.PROD.OUTLOOK.COM ([fe80::b195:1b03:cda0:3897]) by CWXP265MB2087.GBRP265.PROD.OUTLOOK.COM ([fe80::b195:1b03:cda0:3897%5]) with mapi id 15.20.3846.042; Mon, 15 Feb 2021 10:40:12 +0000
From: "King, Daniel" <d.king@lancaster.ac.uk>
To: Abdussalam Baryun <abdussalambaryun@gmail.com>, adrian <adrian@olddog.co.uk>
CC: "routing-discussion@ietf.org" <routing-discussion@ietf.org>, "draft-king-irtf-challenges-in-routing@ietf.org" <draft-king-irtf-challenges-in-routing@ietf.org>
Subject: RE: [External] Re: Request for information - Challenges in routing related to semantic addressing
Thread-Topic: [External] Re: Request for information - Challenges in routing related to semantic addressing
Thread-Index: AQHXA2UCU4KzltbAsU6WF91JFW3c7apZAl7A
Date: Mon, 15 Feb 2021 10:40:12 +0000
Message-ID: <CWXP265MB2087CD3D4A4B7EB370EBD534D6889@CWXP265MB2087.GBRP265.PROD.OUTLOOK.COM>
References: <02d401d701fd$25905a90$70b10fb0$@olddog.co.uk> <CADnDZ88mA7B_a1MUYnXSviD5wjNL3sbqaqrbK0u3NXi6OqeNAA@mail.gmail.com>
In-Reply-To: <CADnDZ88mA7B_a1MUYnXSviD5wjNL3sbqaqrbK0u3NXi6OqeNAA@mail.gmail.com>
Accept-Language: en-GB, en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
authentication-results: gmail.com; dkim=none (message not signed) header.d=none;gmail.com; dmarc=none action=none header.from=lancaster.ac.uk;
x-originating-ip: [2a00:23c7:108:9201:ac72:8d90:742b:eb20]
x-ms-publictraffictype: Email
x-ms-office365-filtering-correlation-id: 80dca5f4-91fc-4081-29eb-08d8d19e1304
x-ms-traffictypediagnostic: CWXP265MB1608:
x-microsoft-antispam-prvs: <CWXP265MB1608C494E7288799E70264FBD6889@CWXP265MB1608.GBRP265.PROD.OUTLOOK.COM>
x-ms-oob-tlc-oobclassifiers: OLM:10000;
x-ms-exchange-senderadcheck: 1
x-microsoft-antispam: BCL:0;
x-microsoft-antispam-message-info: CygxXoeN7RDp3UKRrBk8SrIeOsED1zM9CrUMzhYaPZI9Nx3AsJXn6BzDXbldR9++RM+avTzopNNx1KrrrnjA3UAzxypIF3X9YeG3JldBRbnaWdYF95TzOYtT3Baj4Ux0ghzr6jaZ8E6hAaBsXXkqwPKilL1uYanU9RvaiT91+VqFIupBOjxJYwcFN2ZZrTnvuE74ze1igDTv+hzT7uiFd9+h6Ou74D7S4Pm4pM+7Ymx4GDEbHe/zHYKlXRzBtJyJFhEGj0erGewuG5hUbo+9lyQ9lyHLLc+2V3HM4tnTEtUNpyu1zdZgv1JxFHWrpYSc2cENF95/NgL2CO51odmHuLYlwHYwWrvk2xDh7yh5p8stEoBF+/D7KGdE+z5UOX7j0mORBsIoR1Hk290AEpNvwYl4MalFglyQ+d5JdHSTy3a0FN0yp0h7El1a6MF9Xk+DuMWQ5pj6nJdjwge4q27LuLWPktODyLvk3GjdjB7bhQGw4PgOfLBwvjjId+/Wi9puWQOnOQPF7tcsoABWTV94SBjH5qir1FUZqRFEBGDy3B48uJetR/srBi1k1g+6v4KVjQeFgtkS4/Aic4dei4j+3M33FEDkx/z62AwQBSfQCFw=
x-forefront-antispam-report: CIP:255.255.255.255; CTRY:; LANG:en; SCL:1; SRV:; IPV:NLI; SFV:NSPM; H:CWXP265MB2087.GBRP265.PROD.OUTLOOK.COM; PTR:; CAT:NONE; SFS:(4636009)(39860400002)(346002)(376002)(136003)(366004)(396003)(7696005)(8676002)(55016002)(2906002)(66446008)(4326008)(786003)(71200400001)(316002)(53546011)(66574015)(110136005)(64756008)(66556008)(6506007)(54906003)(9686003)(86362001)(8936002)(83380400001)(66476007)(186003)(166002)(52536014)(33656002)(478600001)(76116006)(66946007)(5660300002)(966005); DIR:OUT; SFP:1102;
x-ms-exchange-antispam-messagedata: yUrf/kdf8z22iboeWeBCT+CzSUlVReX4fYzurxsbTvDtLgMxE+r9UMKTjs4DPQSJSEmCb+zo03Bqz3GwuX9wIqYAWzLaH1+v7yfwJNzChqMbefeNFEiKVEAifY8qbwR+vuxHAu1yQWCO5d5HDg6wyA5HlnBELBbOK8xzJoq76zF/SGPAQe9m8G21PU89bStCULjyYjcOJwU88JII1Cn7iSw536HJWMzXy3PD4stOBBz+MPtsknN67u2wbsjj6/ZWMQCpLZm+nwahsyNyYxlGC6FbohqGnNYnUQ7EsaeWFFHAyZH5hwmWVB4KX7E34drNGiePCL9z5FRoip5ugxsOMXaFcL23084VYHCvm3qfak2WbMcjBiQPX8sZ2yH/jRicRQfg3k9AtmCG4QTDqRiLbXNGLvIcarfZzigMTgNbo/HNq0avvKUAWN40jSFBt4Ax8QJhDt3JtsSuazp0YgnADyQwvnBZGWiVHM/QDbpLYnFiYuNI6HBdUWVA5s8T5wH2eFh4h8ecVyzEbu7PV9WyC00AlxDOx9QvTtrJrVgfl1ksvgBn4gXnSgzPBb823T9/FazW31Zl5PXHunz+RB0PJ7f4sQ0g/J4QQWmXxC0pcUbjRT+f9Yy6b3R8tWIfPIwvMVC8U5MwCUxXBX98F2mLLnTfSNQEDHD64gH3+g/8FrsIEFQQt7TnIqpRBENU9JUM0EB2sKJKjso2xNMGhUYYM0Opi57lBfS3KEpkoonX7CrqhH0XzKRqZVSnILoBajRuQKVGznF/edBKqa2ExXBG3DlG2Iz684dxH1zYf64ownU3yf71XZyCXamPw87/cOjjzOtTOP9pU2LlwgLE/VtGkcHqjFa4917YOOR8IGcxU2zK8doGqM2uj0QfkkbJFeKxhviibsxA3rDeKrhM4mwdgcGT8eIdcEdtk2rplcBcE1zhVyqzbUa8stSfe8n6q5LYQ3HdWDMA4fCaNWFgpJ0YIuSSngDXMTJurbK5E2hAoHbUmcW275PSyf7MYmvQH6N4XvFds8cD2ZxhJxzZ+KIkUkAqU8/Es26VFKu2Ewhs24sqni5OAaIweDZEHeC8BqFqWdDSMvV4ucrlfhV9LcDphUaOYaNeNC+nTDx/CVJZD5w9sxoehaeF2GD8LI9nxl2tcQntpj4V21kJ4n0v0camIlA7IJPlrBS4ZUOEJfbLWyj12ObeyZbK1Don1jBNC0iwD5+jM79S+woa29ZfaiahhjU7ihsmghcwqDPaVY6hiXHPCGTvuz2i5+u5duYIN1b9J9iehWDxVZQ4IGGhpXQ3XOclY7DccI1ZW21VFoeUGfzxSy5Q64omA9IcZo4OCgSXTWupp+bh2NasyMfNCulKZuBSvXA5GSDlRPSj+A6fEjj0G8XwEybJD3TjfOZu9f6r
x-ms-exchange-transport-forked: True
Content-Type: multipart/alternative; boundary="_000_CWXP265MB2087CD3D4A4B7EB370EBD534D6889CWXP265MB2087GBRP_"
MIME-Version: 1.0
X-OriginatorOrg: lancaster.ac.uk
X-MS-Exchange-CrossTenant-AuthAs: Internal
X-MS-Exchange-CrossTenant-AuthSource: CWXP265MB2087.GBRP265.PROD.OUTLOOK.COM
X-MS-Exchange-CrossTenant-Network-Message-Id: 80dca5f4-91fc-4081-29eb-08d8d19e1304
X-MS-Exchange-CrossTenant-originalarrivaltime: 15 Feb 2021 10:40:12.6405 (UTC)
X-MS-Exchange-CrossTenant-fromentityheader: Hosted
X-MS-Exchange-CrossTenant-id: 9c9bcd11-977a-4e9c-a9a0-bc734090164a
X-MS-Exchange-CrossTenant-mailboxtype: HOSTED
X-MS-Exchange-CrossTenant-userprincipalname: +P3lgGcfpvYeIko2YwLaEeaiCUG9hu8rZDsDoOPhNtqksMYpWAFeKQHx7Vwk1C7v6dMfglZl4odP4UkGGvXdAg==
X-MS-Exchange-Transport-CrossTenantHeadersStamped: CWXP265MB1608
Archived-At: <https://mailarchive.ietf.org/arch/msg/routing-discussion/2mSytXWe58filnKImnkmpgsVYiM>
X-BeenThere: routing-discussion@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Routing Area General mailing list <routing-discussion.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/routing-discussion>, <mailto:routing-discussion-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/routing-discussion/>
List-Post: <mailto:routing-discussion@ietf.org>
List-Help: <mailto:routing-discussion-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/routing-discussion>, <mailto:routing-discussion-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 15 Feb 2021 10:40:22 -0000

Hi AB,

Thanks for scanning and commenting.

The I-D has bubbled for a while after seeing various discussions on contextual and semantic routing I-Ds, mostly clean-slate approaches. Although the initial literature review highlighted some common objectives across proposals and implementations, I struggled to find anything that defined "semantic routing" and goals that we could use/reference. I likely missed prior research that provides a useful definition. If not, then I agree that having the IRTF research community document a description for "semantic routing" and common goals, would be beneficial.

BR, Dan.

From: Abdussalam Baryun <abdussalambaryun@gmail.com>
Sent: 15 February 2021 06:37
To: adrian <adrian@olddog.co.uk>
Cc: routing-discussion@ietf.org; draft-king-irtf-challenges-in-routing@ietf.org
Subject: [External] Re: Request for information - Challenges in routing related to semantic addressing


This email originated outside the University. Check before clicking links or attachments.
Hi Adrian,

Thanks for this informational draft, I also think it is important for this list, however, I think I need to have some primary definitions by the authors in this draft, to define meanings of the main objective items (addressing, semantic routing, etc), so then it will be easier to survey and overview.

Best Regards,
AB

On Sat, Feb 13, 2021 at 1:41 PM Adrian Farrel <adrian@olddog.co.uk<mailto:adrian@olddog.co.uk>> wrote:
Hi,

We have just posted "Challenges for the Internet Routing Infrastructure Introduced by Changes in Address Semantics" (https://datatracker.ietf.org/doc/draft-king-irtf-challenges-in-routing/<https://eur02.safelinks.protection.outlook.com/?url=https%3A%2F%2Fdatatracker.ietf.org%2Fdoc%2Fdraft-king-irtf-challenges-in-routing%2F&data=04%7C01%7Cd.king%40lancaster.ac.uk%7C0789ec4da3bd49e47c8408d8d17c22c9%7C9c9bcd11977a4e9ca9a0bc734090164a%7C0%7C0%7C637489678393825383%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C2000&sdata=zmZnEd9jRMv%2BdH%2FcFlyz7yBK09JYQFDuHTBmoQnV4w8%3D&reserved=0>).

This IRTF draft is an attempt to survey the issues and existing research related to the impact on the routing system of the many and varied proposals to add semantics to IP (chiefly IPv6) addresses. Where we are unable to find existing research, we are trying to collect the research questions that we think need to be addressed [sic].

Obviously, this is just a -00 version of the draft and it has a long way to go both in terms of clarity and literature search.

We asked the IRTF to help us with comments and thoughts. In particular, if anyone is aware of any ongoing or published research in the area of semantic addressing or the consequences in routing, we would like to hear about it.

This document is deliberately NOT discussing:
-       Are these address semantic schemes wise or crazy?
-       Is it legal to place semantics in addresses?
-       Is it even possible to achieve overloading of addresses?
What we are doing is zooming in on any existing research of the impact on the routing system and, absent that, to list out the questions that should be answered by research.

Alvaro suggested that routing-discussion would be a good place to copy this request for help.

Response direct to the authors or on this list (until we're told it is not appropriate for this list šŸ˜‰)

Best,
Adrian (for the authors)

_______________________________________________
routing-discussion mailing list
routing-discussion@ietf.org<mailto:routing-discussion@ietf.org>
https://www.ietf.org/mailman/listinfo/routing-discussion<https://eur02.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.ietf.org%2Fmailman%2Flistinfo%2Frouting-discussion&data=04%7C01%7Cd.king%40lancaster.ac.uk%7C0789ec4da3bd49e47c8408d8d17c22c9%7C9c9bcd11977a4e9ca9a0bc734090164a%7C0%7C0%7C637489678393835329%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C2000&sdata=3Hw%2B88OLxy6v9NQ5D4rAWyzS%2FAd9NC9gFKao3jGVce4%3D&reserved=0>