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

"Joel M. Halpern" <jmh@joelhalpern.com> Mon, 15 February 2021 16:11 UTC

Return-Path: <jmh@joelhalpern.com>
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 175DE3A0CE9; Mon, 15 Feb 2021 08:11:04 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.199
X-Spam-Level:
X-Spam-Status: No, score=-0.199 tagged_above=-999 required=5 tests=[DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, NICE_REPLY_A=-0.001, RCVD_IN_MSPIKE_H4=0.001, RCVD_IN_MSPIKE_WL=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=joelhalpern.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 oEcYE8LpHE81; Mon, 15 Feb 2021 08:11:02 -0800 (PST)
Received: from maila2.tigertech.net (maila2.tigertech.net [208.80.4.152]) (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 5F04A3A0C03; Mon, 15 Feb 2021 08:11:02 -0800 (PST)
Received: from localhost (localhost [127.0.0.1]) by maila2.tigertech.net (Postfix) with ESMTP id 4DfTc61GXVz6GD54; Mon, 15 Feb 2021 08:11:02 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=joelhalpern.com; s=2.tigertech; t=1613405462; bh=XLNyObWezMMDrzFzcr2kUiIFWg/U+8BidaaksoiAtCY=; h=Subject:To:Cc:References:From:Date:In-Reply-To:From; b=hxGQ9NFvbedBaKZ68uYl3F9o5J3g0KSqrcl3qXWyiaphJAS7RnVk7sBenyMpaZpAt Bqqhw15AJEwFMJmDLczjJRVBGiTgotYlpdmG4qSBrRK0u9dghXaieiU7Ns3ZJIAQdf c8H1XYWnLgXJ1CExANKEb4hNh3Lg9qXZ4L2sDpow=
X-Quarantine-ID: <IiDoYiVBoDMx>
X-Virus-Scanned: Debian amavisd-new at a2.tigertech.net
Received: from [192.168.128.43] (unknown [50.225.209.66]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by maila2.tigertech.net (Postfix) with ESMTPSA id 4DfTc441FZz6GD5G; Mon, 15 Feb 2021 08:11:00 -0800 (PST)
Subject: Re: [External] Re: Request for information - Challenges in routing related to semantic addressing
To: "King, Daniel" <d.king@lancaster.ac.uk>, adrian <adrian@olddog.co.uk>
Cc: "draft-king-irtf-challenges-in-routing@ietf.org" <draft-king-irtf-challenges-in-routing@ietf.org>, "routing-discussion@ietf.org" <routing-discussion@ietf.org>
References: <02d401d701fd$25905a90$70b10fb0$@olddog.co.uk> <CADnDZ88mA7B_a1MUYnXSviD5wjNL3sbqaqrbK0u3NXi6OqeNAA@mail.gmail.com> <CWXP265MB2087CD3D4A4B7EB370EBD534D6889@CWXP265MB2087.GBRP265.PROD.OUTLOOK.COM>
From: "Joel M. Halpern" <jmh@joelhalpern.com>
Message-ID: <f040717b-f099-92fb-be48-bce59a587b5b@joelhalpern.com>
Date: Mon, 15 Feb 2021 11:10:59 -0500
User-Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:78.0) Gecko/20100101 Thunderbird/78.7.0
MIME-Version: 1.0
In-Reply-To: <CWXP265MB2087CD3D4A4B7EB370EBD534D6889@CWXP265MB2087.GBRP265.PROD.OUTLOOK.COM>
Content-Type: text/plain; charset="utf-8"; format="flowed"
Content-Language: en-US
Content-Transfer-Encoding: 8bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/routing-discussion/2AIG8LdibkwT8nHS4Dpo9Mrpr1E>
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 16:11:04 -0000

I can't argue with an effort to define the term "semantic routing".
However, I would be very concerned by an effort to define goals for it 
before we have such a definition.  Depending upon the definition, the 
answer may be that it is a bad idea.

Yours,
Joel

On 2/15/2021 5:40 AM, King, Daniel wrote:
> 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>
> 
> 
> _______________________________________________
> routing-discussion mailing list
> routing-discussion@ietf.org
> https://www.ietf.org/mailman/listinfo/routing-discussion
>