Re: FW: Next steps discussing Routing Challenges of Semantic Addressing

Alexandre Petrescu <alexandre.petrescu@gmail.com> Thu, 06 May 2021 20:22 UTC

Return-Path: <alexandre.petrescu@gmail.com>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 3DEDA3A3076 for <ipv6@ietfa.amsl.com>; Thu, 6 May 2021 13:22:06 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.649
X-Spam-Level:
X-Spam-Status: No, score=0.649 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_ADSP_CUSTOM_MED=0.001, FORGED_GMAIL_RCVD=1, FREEMAIL_FROM=0.001, NICE_REPLY_A=-0.001, NML_ADSP_CUSTOM_MED=0.9, RCVD_IN_DNSWL_BLOCKED=0.001, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, SPF_HELO_NONE=0.001, SPF_SOFTFAIL=0.665, 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 5gTm4UrC9Iut for <ipv6@ietfa.amsl.com>; Thu, 6 May 2021 13:22:01 -0700 (PDT)
Received: from smtp2-g21.free.fr (smtp2-g21.free.fr [212.27.42.2]) (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 7017E3A3078 for <ipv6@ietf.org>; Thu, 6 May 2021 13:22:01 -0700 (PDT)
Received: from [IPv6:2a01:e0a:937:bc30::c8b2:2e1d] (unknown [IPv6:2a01:e0a:937:bc30::c8b2:2e1d]) by smtp2-g21.free.fr (Postfix) with ESMTP id 2533D200445 for <ipv6@ietf.org>; Thu, 6 May 2021 22:21:54 +0200 (CEST)
Subject: Re: FW: Next steps discussing Routing Challenges of Semantic Addressing
To: ipv6@ietf.org
References: <4f22f9591c0a48d1a351f52318cd3319@boeing.com> <CAOj+MMHxh5UmUsPOmun+XGPcBK0=AGLzSpx7Nemni1WzPnta9w@mail.gmail.com>
From: Alexandre Petrescu <alexandre.petrescu@gmail.com>
Message-ID: <539de301-3378-e6d6-d868-081a647f52c0@gmail.com>
Date: Thu, 06 May 2021 22:21:53 +0200
User-Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:78.0) Gecko/20100101 Thunderbird/78.10.1
MIME-Version: 1.0
In-Reply-To: <CAOj+MMHxh5UmUsPOmun+XGPcBK0=AGLzSpx7Nemni1WzPnta9w@mail.gmail.com>
Content-Type: text/plain; charset="utf-8"; format="flowed"
Content-Language: fr
Content-Transfer-Encoding: 8bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/ipv6/6uIYgo8RYsMc34m8zA0u6pFIrgM>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ipv6/>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ipv6>, <mailto:ipv6-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 06 May 2021 20:22:06 -0000

Le 06/05/2021 à 22:04, Robert Raszuk a écrit :
> All,
> 
> May I ask why this topic is being taken outside of IETF ?

Maybe because https://www.jiscmail.ac.uk/cgi-bin/webadmin?A0=SARAH is
not on IPv6?

> Is it so difficult to create a new list ?

I think it is very easy for IETF Secretariat to create email lists, but
it is very difficult for me to create a new local filter for each new
mailing list, and since some time now.  To address that problem, there
is a need of a new communications protocol feature to be used by the
IETF Secretariat in a trustful manner, such that it automatically
creates an email filter in my email reader and a new folder, upon the
creation of a new email list.

Creating a list first outside the IETF, and then potentially moving it
to IETF or IRTF, poses a significant challenge in automatically updating
these filters.  Because there would be no single entity (like the IETF
Secretariat) that could trigger this.  The Secretariat would have to
have a close relationship with that organisation outside of IETF.

> Or is this so off topic to say ipv6 or 6man lists that it can not be
>  discussed there ?

I think it does make sense to discuss it at IETF.

I doubt though that routing on more bits than a dst address can be
qualified as semantics.  Semantics would be if the packets could smell
something and routing would happen on that smell.  Or be coloured
something, or have a spin, or similar.

Addressing something with something else than an address also poses a
challenge.  On another hand, the semantics of an address could be
augmented with port numbers, and then routing could be done based on
address+portnumbers, maybe traffic engineering.

Just some simple thoughts...  I have to read the description first.

Alex

> 
> Thx, Robert
> 
> 
> On Thu, May 6, 2021 at 9:09 PM Manfredi (US), Albert E 
> <albert.e.manfredi@boeing.com <mailto:albert.e.manfredi@boeing.com>>
>  wrote:
> 
> This is something that ought to be of interest to organizations which
> want to use their own semantics, in the IPv6 prefixes. There was some
> discussion on 6man some time ago, in which the assumption appeared to
> be, such a thing is already viable.
> 
> Bert
> 
> -----Original Message----- From: routing-discussion 
> <routing-discussion-bounces@ietf.org 
> <mailto:routing-discussion-bounces@ietf.org>> On Behalf Of Adrian 
> Farrel Sent: Thursday, May 06, 2021 05:49 To: irtf-discuss@irtf.org 
> <mailto:irtf-discuss@irtf.org>; routing-discussion@ietf.org 
> <mailto:routing-discussion@ietf.org> Subject: [EXTERNAL] Next steps 
> discussing Routing Challenges of Semantic Addressing
> 
> EXT email: be mindful of links/attachments.
> 
> Dear all,
> 
> Back in March we posted an initial draft to open the discussion of 
> research related to routing based on additional meaning assigned to 
> IP addresses, and to routing based on fields other than the 
> destination address field of an IP packet. That draft attracted some
>  comments, and one thing was clear: we needed to split the draft into
>  a survey of work that has happened / is happening, and a discussion
>  of the challenges to routing together with the research question.
> 
> So we have done this now (sorry it took so long) and have posted: 
> https://datatracker.ietf.org/doc/draft-king-irtf-semantic-routing-survey/
>
>
>
>
>
> 
<https://datatracker.ietf.org/doc/draft-king-irtf-semantic-routing-survey/>
> 
> https://datatracker.ietf.org/doc/draft-king-irtf-challenges-in-routing/
>
>
>
>
>
> 
<https://datatracker.ietf.org/doc/draft-king-irtf-challenges-in-routing/>
> 
> 
> These new drafts do not pick up all of the comments received (we 
> focused on the split), but we hope to address the comments in new 
> revisions soon.
> 
> At the same time, we have set up a dedicated mailing list for 
> discussion of "Semantic Addressing Routing and Hardware" (SARAH) at 
> sarah@jiscmail.ac.uk <mailto:sarah@jiscmail.ac.uk>. This is an 
> academic, research-based community where we can discuss all aspects 
> of the drafts, introduce our research to each other, and advertise 
> related conference activity. You can subscribe at 
> https://www.jiscmail.ac.uk/cgi-bin/webadmin?A0=SARAH 
> <https://www.jiscmail.ac.uk/cgi-bin/webadmin?A0=SARAH>.
> 
> We hope the new list will help to focus discussion and avoid
> spamming existing mailing lists.
> 
> Looking forward to hearing your opinions.
> 
> Adrian and Dan
> 
> _______________________________________________ routing-discussion 
> mailing list routing-discussion@ietf.org 
> <mailto:routing-discussion@ietf.org> 
> https://www.ietf.org/mailman/listinfo/routing-discussion 
> <https://www.ietf.org/mailman/listinfo/routing-discussion>
> 
> -------------------------------------------------------------------- 
> IETF IPv6 working group mailing list ipv6@ietf.org 
> <mailto:ipv6@ietf.org> Administrative Requests: 
> https://www.ietf.org/mailman/listinfo/ipv6 
> <https://www.ietf.org/mailman/listinfo/ipv6> 
> --------------------------------------------------------------------
> 
> 
> -------------------------------------------------------------------- 
> IETF IPv6 working group mailing list ipv6@ietf.org Administrative 
> Requests: https://www.ietf.org/mailman/listinfo/ipv6 
> --------------------------------------------------------------------
>