Re: RTGWG feedback on APN next steps

hsyu <hsyu@cfiec.net> Wed, 06 April 2022 10:08 UTC

Return-Path: <hsyu@cfiec.net>
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 2693F3A185D for <rtgwg@ietfa.amsl.com>; Wed, 6 Apr 2022 03:08:04 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.864
X-Spam-Level:
X-Spam-Status: No, score=-0.864 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, INVALID_MSGID=0.568, MIME_HTML_ONLY=0.1, RCVD_IN_XBL=0.375, 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 dR5y115ZbIln for <rtgwg@ietfa.amsl.com>; Wed, 6 Apr 2022 03:08:00 -0700 (PDT)
Received: from smtpbg154.qq.com (smtpbg154.qq.com [15.184.224.54]) (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 0253B3A1732 for <rtgwg@ietf.org>; Wed, 6 Apr 2022 03:07:58 -0700 (PDT)
X-QQ-mid: bizesmtp70t1649239671t9i71pp6
Received: from DESKTOP-3U2VLEE ( [124.14.224.58]) by bizesmtp.qq.com (ESMTP) with id ; Wed, 06 Apr 2022 18:07:50 +0800 (CST)
X-QQ-SSF: 00400000001000B0C000B00A0000000
X-QQ-FEAT: 0VgNaGdhy9jbbCijvYeNmIQf7TnozyW9mfzDAOwvxoQpb5m3KuNASmTSYc8/8 XNuDgfqkRG+ZvEELmb8n2vF1b3bn1b+4EZJ0LrfubyehaeaXQtV5PsMhQJGAtzleCHx6wHf kBT3NZ+YBOmnxz2ei27OQZIcj5dRQaa3YHLQBMByG5SfI8qcKvT/EqRB+OeEASNfBtk+3kJ X+oeYYxz+zkC9s/lSwpQ6Sc3qRIgRiIVjzpz5sJ05w8qb5MzmrkYScYcQru2yPTe0R31G4v 6DcC/7F1F4pDoknDB3O62Xo8mDc6rgFlyDVxWm+P09nHf0H6K7hoY+36uf3walN5BtVMxfw YDXSKLfHVgfjkR5MbW6F6N7M2bT3A==
X-QQ-GoodBg: 2
Date: Wed, 6 Apr 2022 18:07:49 +0800
From: hsyu <hsyu@cfiec.net>
To: =?utf-8?Q?jefftant.ietf=40gmail.com?= <jefftant.ietf@gmail.com>
Cc: =?utf-8?Q?rtgwg=40ietf.org?= <rtgwg@ietf.org>
Message-ID: <23AF3159-72AD-494F-AC7D-5C79F7FD0759@cfiec.net>+9B2491148A968617
In-Reply-To: <mailman.0.1649228789.15457.rtgwg@ietf.org>
References: <mailman.0.1649228789.15457.rtgwg@ietf.org>
Subject: Re: RTGWG feedback on APN next steps
X-Mailer: MailMasterPC/4.16.1.1026 (Win10 19H2)
X-CUSTOM-MAIL-MASTER-SENT-ID: BD043595-10D3-4602-97EF-76D3471BCEE4
MIME-Version: 1.0
Content-Type: text/html; charset="utf-8"
Content-Transfer-Encoding: base64
X-QQ-SENDSIZE: 520
Feedback-ID: bizesmtp:cfiec.net:qybgforeign:qybgforeign9
X-QQ-Bgrelay: 1
Archived-At: <https://mailarchive.ietf.org/arch/msg/rtgwg/nb5XAzZS6pOymmM-QpZfB_Syx5I>
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: Wed, 06 Apr 2022 10:08:05 -0000

Hi,  Jeff and all,

There are currently a lot of work around APN and the APN framework is the most important one. I think that it is a good idea to suggest a dedicated working group for our discussions. Thank you!

Best regards.

https://maas.mail.163.com/dashi-web-extend/html/proSignature.html?ftlId=1&name=Haisheng+Yu%28Johnson%29&uid=hsyu%40cfiec.net&iconUrl=https%3A%2F%2Fmail-online.nosdn.127.net%2Fsm50a1433bca9fb284d4265d35e9ed54d3.jpg&items=%5B%22%22%2C%22hsyu%40cfiec.net%22%2C%22%22%2C%22%22%2C%22%22%5D" rel="nofollow">
Haisheng Yu(Johnson)

Chief Expert of Guangzhou GenChain
International Network Research
Institute Co., Ltd.

Director of Prospective Technology
Laboratory, China Future Internet 
Engineering Center

Researcher at Macau University of 
Science and Technology

IEEE Guangzhou/Macau Blockchain 
Group Chair

On 4/5/2022 17:15,<jefftant.ietf@gmail.com> wrote:

RTGWG feedback on APN next steps

Jeff Tantsura <jefftant.ietf@gmail.com> Tue, 05 April 2022 17:15 UTC

It is not clear to me that there is a well-defined problem or a 
willingness to embrace community process around the APN work.  (Feedback 
suggesting that there are existing approaches to be considered has 
consistently been met with repetitions of the same "new" proposals.)

That said, whether "a focus WG, with a set of well defined deliverables 
and milestones" would be a good idea or not depends in large part on 
what the terms are for the WG.  I can imagine cases which, while I might 
think them less than useful, would not be harmful and might be helpful. 
  I can equally imagine terms from the same premise that would be 
unacceptable.

Yours,
Joel

On 4/5/2022 1:14 PM, Jeff Tantsura wrote:
> 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
> 
> 
> _______________________________________________
> rtgwg mailing list
> rtgwg@ietf.org
> https://www.ietf.org/mailman/listinfo/rtgwg" rel="nofollow">https://www.ietf.org/mailman/listinfo/rtgwg