FW: New Version Notification for draft-trossen-rtgwg-rosa-00.txt

Dirk Trossen <dirk.trossen@huawei.com> Mon, 24 October 2022 09:02 UTC

Return-Path: <dirk.trossen@huawei.com>
X-Original-To: rtgwg@ietfa.amsl.com
Delivered-To: rtgwg@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id BFC87C1522BA for <rtgwg@ietfa.amsl.com>; Mon, 24 Oct 2022 02:02:33 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.907
X-Spam-Level:
X-Spam-Status: No, score=-6.907 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_HI=-5, RCVD_IN_MSPIKE_H2=-0.001, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, T_SCC_BODY_TEXT_LINE=-0.01, URIBL_BLOCKED=0.001, URIBL_DBL_BLOCKED_OPENDNS=0.001, URIBL_ZEN_BLOCKED_OPENDNS=0.001] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([50.223.129.194]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 2Zed6uSylAUu for <rtgwg@ietfa.amsl.com>; Mon, 24 Oct 2022 02:02:32 -0700 (PDT)
Received: from frasgout.his.huawei.com (frasgout.his.huawei.com [185.176.79.56]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 4AEA5C1522B7 for <rtgwg@ietf.org>; Mon, 24 Oct 2022 02:02:32 -0700 (PDT)
Received: from fraeml704-chm.china.huawei.com (unknown [172.18.147.201]) by frasgout.his.huawei.com (SkyGuard) with ESMTP id 4MwpsL2wynz67Cxn for <rtgwg@ietf.org>; Mon, 24 Oct 2022 16:59:02 +0800 (CST)
Received: from lhrpeml100001.china.huawei.com (7.191.160.183) by fraeml704-chm.china.huawei.com (10.206.15.53) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA256_P256) id 15.1.2375.31; Mon, 24 Oct 2022 11:02:29 +0200
Received: from lhrpeml500003.china.huawei.com (7.191.162.67) by lhrpeml100001.china.huawei.com (7.191.160.183) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256) id 15.1.2375.31; Mon, 24 Oct 2022 10:02:29 +0100
Received: from lhrpeml500003.china.huawei.com ([7.191.162.67]) by lhrpeml500003.china.huawei.com ([7.191.162.67]) with mapi id 15.01.2375.031; Mon, 24 Oct 2022 10:02:29 +0100
From: Dirk Trossen <dirk.trossen@huawei.com>
To: "rtgwg@ietf.org" <rtgwg@ietf.org>
Subject: FW: New Version Notification for draft-trossen-rtgwg-rosa-00.txt
Thread-Topic: New Version Notification for draft-trossen-rtgwg-rosa-00.txt
Thread-Index: AQHY54Z7eFFYESyF5E2weaNSS++6vq4dPhZQ
Date: Mon, 24 Oct 2022 09:02:28 +0000
Message-ID: <494e4a4fb7b34e73b8ff040add040065@huawei.com>
References: <166660176609.13535.11308283489631444575@ietfa.amsl.com>
In-Reply-To: <166660176609.13535.11308283489631444575@ietfa.amsl.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [10.81.214.209]
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64
MIME-Version: 1.0
X-CFilter-Loop: Reflected
Archived-At: <https://mailarchive.ietf.org/arch/msg/rtgwg/xRFpOTP6OYcBznaSLsPR1UKKWkE>
X-BeenThere: rtgwg@ietf.org
X-Mailman-Version: 2.1.39
Precedence: list
List-Id: Routing Area Working Group <rtgwg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/rtgwg>, <mailto:rtgwg-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/rtgwg/>
List-Post: <mailto:rtgwg@ietf.org>
List-Help: <mailto:rtgwg-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/rtgwg>, <mailto:rtgwg-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 24 Oct 2022 09:02:33 -0000

Dear all,

We (Luis from Telefonica and myself) have posted an I-D on 'routing on service addresses' (see below), outlining an approach to direct IP packets based on service address information rather than network locator addresses in an end-to-end manner. For this, we suggest the use of IPv6 extension headers, utilized by a shim overlay atop IPv6 and realized by what we call a ROSA provider. 

We have requested a presentation slot for the upcoming IETF meeting in London but I would love to hear feedback and comments already on the list, if possible. 

I am also looking forward to any discussions at the IETF, including as side discussions, with those interested in this topic.

Many thanks!

Best,

Dirk 

-----Original Message-----
From: internet-drafts@ietf.org <internet-drafts@ietf.org> 
Sent: 24 October 2022 10:56
To: Luis M. Contreras <luismiguel.contrerasmurillo@telefonica.com>; Dirk Trossen <dirk.trossen@huawei.com>; Luis Contreras <luismiguel.contrerasmurillo@telefonica.com>
Subject: New Version Notification for draft-trossen-rtgwg-rosa-00.txt


A new version of I-D, draft-trossen-rtgwg-rosa-00.txt has been successfully submitted by Dirk Trossen and posted to the IETF repository.

Name:		draft-trossen-rtgwg-rosa
Revision:	00
Title:		Routing on Service Addresses
Document date:	2022-10-24
Group:		Individual Submission
Pages:		31
URL:            https://www.ietf.org/archive/id/draft-trossen-rtgwg-rosa-00.txt
Status:         https://datatracker.ietf.org/doc/draft-trossen-rtgwg-rosa/
Htmlized:       https://datatracker.ietf.org/doc/html/draft-trossen-rtgwg-rosa


Abstract:
   This document proposes a novel communication approach which reasons
   about WHAT is being communicated (and invoked) instead of WHO is
   communicating.  Such approach is meant to transition away from
   locator-based addressing (and thus routing and forwarding) to an
   addressing scheme where the address semantics relate to services
   being invoked (e.g., for computational processes, and their generated
   information requests and responses).

   The document introduces Routing on Service Addresses (ROSA), as a
   realization of what is referred to as 'service-based routing' (SBR).
   Such routing is designed to be constrained by service-specific
   parameters that go beyond load and latency, as in today's best effort
   or traffic engineering based routing, leading to an approach to steer
   traffic in a service-specific constraint-based manner.

   Particularly, this document outlines sample ROSA use case scenarios,
   requirements for its design, and the ROSA system design itself.

                                                                                  


The IETF Secretariat