RE: RTGWG feedback on APN next steps

Adrian Farrel <adrian@olddog.co.uk> Fri, 08 April 2022 17:12 UTC

Return-Path: <adrian@olddog.co.uk>
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 B41B13A1845; Fri, 8 Apr 2022 10:12:41 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.903
X-Spam-Level:
X-Spam-Status: No, score=-0.903 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, MAY_BE_FORGED=1, RCVD_IN_DNSWL_BLOCKED=0.001, RCVD_IN_MSPIKE_H5=0.001, RCVD_IN_MSPIKE_WL=0.001, SPF_HELO_NONE=0.001, SPF_NONE=0.001, T_SCC_BODY_TEXT_LINE=-0.01, 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 9b357PKT1zL7; Fri, 8 Apr 2022 10:12:39 -0700 (PDT)
Received: from mta5.iomartmail.com (mta5.iomartmail.com [62.128.193.155]) (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 95ED13A1842; Fri, 8 Apr 2022 10:12:34 -0700 (PDT)
Received: from vs4.iomartmail.com (vs4.iomartmail.com [10.12.10.122]) by mta5.iomartmail.com (8.14.7/8.14.7) with ESMTP id 238HCVim018887; Fri, 8 Apr 2022 18:12:31 +0100
Received: from vs4.iomartmail.com (unknown [127.0.0.1]) by IMSVA (Postfix) with ESMTP id 135FF4604C; Fri, 8 Apr 2022 18:12:31 +0100 (BST)
Received: from vs4.iomartmail.com (unknown [127.0.0.1]) by IMSVA (Postfix) with ESMTP id 06A534604A; Fri, 8 Apr 2022 18:12:31 +0100 (BST)
Received: from asmtp3.iomartmail.com (unknown [10.12.10.224]) by vs4.iomartmail.com (Postfix) with ESMTPS; Fri, 8 Apr 2022 18:12:30 +0100 (BST)
Received: from LAPTOPK7AS653V (198.197.bbplus.pte-ag1.dyn.plus.net [81.174.197.198] (may be forged)) (authenticated bits=0) by asmtp3.iomartmail.com (8.14.7/8.14.7) with ESMTP id 238HCUBK016807 (version=TLSv1/SSLv3 cipher=ECDHE-RSA-AES256-GCM-SHA384 bits=256 verify=NO); Fri, 8 Apr 2022 18:12:30 +0100
Reply-To: <adrian@olddog.co.uk>
From: "Adrian Farrel" <adrian@olddog.co.uk>
To: "'Jeff Tantsura'" <jefftant.ietf@gmail.com>, "'RTGWG'" <rtgwg@ietf.org>, "'rtgwg-chairs'" <rtgwg-chairs@ietf.org>, <rtg-ads@ietf.org>
References: <204D8DE6-F51C-4551-B1D7-1D69DBCA3626@hxcore.ol>
In-Reply-To: <204D8DE6-F51C-4551-B1D7-1D69DBCA3626@hxcore.ol>
Subject: RE: RTGWG feedback on APN next steps
Date: Fri, 8 Apr 2022 18:12:28 +0100
Organization: Old Dog Consulting
Message-ID: <05f401d84b6b$d3ef9f70$7bcede50$@olddog.co.uk>
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="----=_NextPart_000_05F5_01D84B74.35B4A3B0"
X-Mailer: Microsoft Outlook 16.0
Thread-Index: AQKon3Ys/am+UrHLVeo/KDa/0N3UlatFlI8A
Content-Language: en-gb
X-Originating-IP: 81.174.197.198
X-Thinkmail-Auth: adrian@olddog.co.uk
X-TM-AS-GCONF: 00
X-TM-AS-Product-Ver: IMSVA-9.1.0.2090-9.0.0.1000-26822.001
X-TM-AS-Result: No--28.490-10.0-31-10
X-imss-scan-details: No--28.490-10.0-31-10
X-TMASE-Version: IMSVA-9.1.0.2090-9.0.1000-26822.001
X-TMASE-Result: 10--28.489900-10.000000
X-TMASE-MatchedRID: qsaWi0FWcYvxIbpQ8BhdbKJYDeXFTTUTmxiTnSRu8z6GD9O3ui1h2Bv3 n9aCElqQjAOodPX1XTxFen0j2422Kli4F1ScQrWQ3nHtGkYl/VpNLPQl0QAltD2UWodwCj5HM/8 xlD//I5tb6JYpoGrnWsN2weE7GAmZp9N3nIP4XvXHYNKoSYWoHvtiJd16CCrJ4Y6kI/Ug2+ekmV fMaQ84Wc1j70qfy418Cj9154oQbrBVWK0SX6WmVBKWs8nk7uc870GLyvzOg0wwaoe6trQC0b4zf TpGjdbaQxTNQIR96f6lXzozWLmhVHjxgHkp9duCX9knSHW8uXU2ugGkJu34Zp3jW+hMr638VXFz 93jC3xe2wOS+5LgRCxeXF48LMwEsR1vveBQPCRcrCLswi3Npja6IBbSnfz+3srDwfHQQaK1na42 ZCQpcXqd2f8t80y/fg9vDTbe8QsiFtNDXkV/ga99JA2lmQRNU0E7bU7GWyi8Hg31vZvY63nJjJg HKarrTsOAILXWuRMcMvr5eMIb5nUDhU8Vgq6FvAjqAxuWkdTGjT0w/TJJw6C2818Jova4CbVsEF Jqff8nvp8GuZhjBuTsOdvA5nu/wA7dimDbca7hmNCKOCsW/OtVYleRFiu07myiLZetSf8mVHVxP 1hp9BUpZ1N/CwmPL0KkIUsNMdlSQZS2ujCtcuA==
X-TMASE-SNAP-Result: 1.821001.0001-0-1-22:0,33:0,34:0-0
Archived-At: <https://mailarchive.ietf.org/arch/msg/rtgwg/Sql-2OjPk3eP-wECN7dtPOYc4PM>
X-BeenThere: rtgwg@ietf.org
X-Mailman-Version: 2.1.29
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: Fri, 08 Apr 2022 17:12:42 -0000

Hi Jeff and Yingzhen,

 

I would certainly appreciate a place that is working on a framework and the requirements that underlie the drive for APN.

 

I think that APN fits within the broad scope of “semantic routing” that I described at the meeting during IETF 113 and I would like us to be certain that the range of problems being addressed by APN has been fully discussed so that we avoid producing a niche solution for a subset of the use cases that might be addressed if we considered more carefully.

 

Robert is right that there are some risks associated with the potential complexity added to the routing and forwarding system (I hope I captured the essence of that in my presentation and in draft-king-irtf-challenges-in-routing), and I feel that working through these in a focused venue as part of the discussion of the framework would help target the solutions work better.

 

A small “however” here…

However, before fully supporting the creation of a working group, I do like to see the charter and scope. Obviously, that is beyond the current question that you asked (and that’s fine), but I just want the ADs to know the qualification to my answer.

 

Cheers,

Adrian

 

From: rtgwg <rtgwg-bounces@ietf.org> On Behalf Of Jeff Tantsura
Sent: 05 April 2022 18:15
To: RTGWG <rtgwg@ietf.org>rg>; rtgwg-chairs <rtgwg-chairs@ietf.org>rg>; rtg-ads@ietf.org
Subject: RTGWG feedback on APN next steps

 

Dear RTGWG,

 

 

APN has been presented at RTGWG multiple times, and we see the evolution of the

documents, including the scope of the problem and framework.  This topic needs

collaboration across WGs; we can foresee that not all issues to be addressed are

within the charter of RTGWG and would span beyond the Routing area.

 

RTGWG is chartered to provide a venue for new work, there are a couple of different options and one option for handling

such new work would be to recommend the development of a new WG.  

The Chairs would then want to recommend that the ADs consider forming a focus WG, with a set of well defined deliverables and milestones (after delivery the group would be shut down) to work on a framework for APN.

 

We would like to solicit the WG for opinions.  Please note that comments about

existing APN documents should be sent to apn@ietf.org <mailto:apn@ietf.org> .  This thread focuses on

support or objection to recommending that the ADs consider the formation of a

new WG.

 

Please send your comments, support, or objectiond.

Thanks!

 

 

Cheers,

Yingzhen  Jeff