Re: RTGWG feedback on APN next steps
Stefano Previdi IETF <sprevidi4ietf@gmail.com> Thu, 07 April 2022 09:58 UTC
Return-Path: <sprevidi4ietf@gmail.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 880BA3A170D;
Thu, 7 Apr 2022 02:58:33 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.108
X-Spam-Level:
X-Spam-Status: No, score=-2.108 tagged_above=-999 required=5
tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1,
DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, FREEMAIL_FROM=0.001,
SPF_HELO_NONE=0.001, SPF_PASS=-0.001, T_SCC_BODY_TEXT_LINE=-0.01,
URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key)
header.d=gmail.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 eDCneUymk0Gu; Thu, 7 Apr 2022 02:58:27 -0700 (PDT)
Received: from mail-ej1-x62d.google.com (mail-ej1-x62d.google.com
[IPv6:2a00:1450:4864:20::62d])
(using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits))
(No client certificate requested)
by ietfa.amsl.com (Postfix) with ESMTPS id A7CAC3A1707;
Thu, 7 Apr 2022 02:58:26 -0700 (PDT)
Received: by mail-ej1-x62d.google.com with SMTP id n6so9638335ejc.13;
Thu, 07 Apr 2022 02:58:26 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20210112;
h=mime-version:subject:from:in-reply-to:date:cc
:content-transfer-encoding:message-id:references:to;
bh=4UuSQ2VaqjcID+ffcDNY7odNNMmCUxN1+rXgMPHr6kA=;
b=RBTrCV1UitvOSjB6RiHzytUYTy7JB4R1YXZc8TFqgsdVCzap+0ey0SvwK9wMGwA0+C
22wa7ewWJZ9jYnkFKdKASBmNTVo8zufK948aKKCX7aga6N+GLWmPIuEg5mUZjOCb9A13
XJi+X4uTqTipJDBqjOF9auTZR5DbjlD69dH2jiYbCPyUaMk6eG/eymaRGYAdz5rXZAXa
eRh9KyvyGtENSRi79po6/3JrD8DsvLZHx41YbpzLtX965xqRZWu1w+3H3+xhRLBI2xJG
3AM+jnSGPP6Pz4uRsTnomGFrsFA53LxOxL9r1ZFNDN11H/DMfr39mSD766+W+K7UT/vP
z4Kw==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
d=1e100.net; s=20210112;
h=x-gm-message-state:mime-version:subject:from:in-reply-to:date:cc
:content-transfer-encoding:message-id:references:to;
bh=4UuSQ2VaqjcID+ffcDNY7odNNMmCUxN1+rXgMPHr6kA=;
b=Psdz7fboYnc2N2SKP6NEa+cl39gkXXGSbG/Y3WN39rWLMUfGFoelRRpTliQhPm6gIa
Ml4jjnMnCvdfLqeXxjgo3E+OWUWaSXna3AmMVKRdrR2vYuRhneXqtzgNYn1nWjpxL2So
cfo7SzdL5uD048o05ZGk4T+8alWsI/sxXRCfGOcHzPUap1Y7cPuqvpeS0B68ad6XxSwW
iZODAONftrh5wb39QL57xIimOlP525ml8RUeEkkhRgVIGS2hTI/1OkobwbgIoPGjCZPP
MxRCNCurGoxrZYblFCE06V7yGaFrUHZvQNrkhoYRXcMbW0bxsAPyPzwcQYKgb5Iv6/H8
9vog==
X-Gm-Message-State: AOAM531MSynorugyH46YXA35/F1fELviRJJdlL86CqDrJKv7/c15ovKr
a3uSCYFX+yNnBWKY6eZ/Dm8=
X-Google-Smtp-Source: ABdhPJyEdd6qPqNJI5SFOJjT+ZpkUR/VVPJEvD4tkuhxGjM2QL+3Gxo9atTA28wvJ8JHymHH82ZtFg==
X-Received: by 2002:a17:906:2bd7:b0:6ce:698b:7531 with SMTP id
n23-20020a1709062bd700b006ce698b7531mr12192868ejg.146.1649325504509;
Thu, 07 Apr 2022 02:58:24 -0700 (PDT)
Received: from pc.home (host-79-53-20-130.retail.telecomitalia.it.
[79.53.20.130]) by smtp.gmail.com with ESMTPSA id
m3-20020a17090679c300b006cf9ce53354sm7452173ejo.190.2022.04.07.02.58.23
(version=TLS1_2 cipher=ECDHE-ECDSA-AES128-GCM-SHA256 bits=128/128);
Thu, 07 Apr 2022 02:58:23 -0700 (PDT)
Content-Type: text/plain;
charset=utf-8
Mime-Version: 1.0 (Mac OS X Mail 13.4 \(3608.120.23.2.6\))
Subject: Re: RTGWG feedback on APN next steps
From: Stefano Previdi IETF <sprevidi4ietf@gmail.com>
In-Reply-To: <204D8DE6-F51C-4551-B1D7-1D69DBCA3626@hxcore.ol>
Date: Thu, 7 Apr 2022 11:58:22 +0200
Cc: RTGWG <rtgwg@ietf.org>, rtgwg-chairs <rtgwg-chairs@ietf.org>,
"rtg-ads@ietf.org" <rtg-ads@ietf.org>
Content-Transfer-Encoding: quoted-printable
Message-Id: <C178017F-D075-4C2A-8F9F-7C00AE20D15B@gmail.com>
References: <204D8DE6-F51C-4551-B1D7-1D69DBCA3626@hxcore.ol>
To: Jeff Tantsura <jefftant.ietf@gmail.com>
X-Mailer: Apple Mail (2.3608.120.23.2.6)
Archived-At: <https://mailarchive.ietf.org/arch/msg/rtgwg/_emwu4MHyeJEn92amwyHjHCtajA>
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: Thu, 07 Apr 2022 09:58:34 -0000
Hi, I support the creation of an APN focused working group. The problem statement, requirements and framework have been properly documented and there’s a good consensus in the industry that this topic needs to be worked out. A dedicated WG seems, to me, as the best approach. Thanks. s. > On Apr 5, 2022, at 7:14 PM, Jeff Tantsura <jefftant.ietf@gmail.com> 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. 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
- RTGWG feedback on APN next steps Jeff Tantsura
- Re: RTGWG feedback on APN next steps Joel M. Halpern
- Re: RTGWG feedback on APN next steps hsyu
- 答复: RTGWG feedback on APN next steps Feng Yang
- Re: RTGWG feedback on APN next steps Gyan Mishra
- Re: RTGWG feedback on APN next steps liupengyjy@chinamobile.com
- Re: RTGWG feedback on APN next steps Donald Eastlake
- Re: RTGWG feedback on APN next steps zhangs366@chinaunicom.cn
- Re: RTGWG feedback on APN next steps Lin He
- Re: RTGWG feedback on APN next steps strong
- RE: RTGWG feedback on APN next steps 鱼亚锋
- Re: RTGWG feedback on APN next steps Stefano Previdi IETF
- Re: RTGWG feedback on APN next steps Robert Raszuk
- RE: RTGWG feedback on APN next steps Linda Dunbar
- RE: RTGWG feedback on APN next steps Linda Dunbar
- Re: RTGWG feedback on APN next steps Robert Raszuk
- RE: RTGWG feedback on APN next steps Giuseppe Fioccola
- RE: RTGWG feedback on APN next steps UTTARO, JAMES
- RE: RTGWG feedback on APN next steps UTTARO, JAMES
- Re: RTGWG feedback on APN next steps duzongpeng@foxmail.com
- Re: RE: RTGWG feedback on APN next steps duzongpeng@foxmail.com
- Re: RTGWG feedback on APN next steps Dhruv Dhody
- RE: RTGWG feedback on APN next steps Luc-Fabrice Ndifor Ngwa [ MTN Cameroon ]
- Re: RTGWG feedback on APN next steps 庞冉(联通集团中国联通研究院-本 部)
- RE: RTGWG feedback on APN next steps Adrian Farrel
- Re: RTGWG feedback on APN next steps Luis M. Contreras
- RE: RTGWG feedback on APN next steps Alexander Clemm
- Re: RTGWG feedback on APN next steps Yichi Xu
- RE: RTGWG feedback on APN next steps Dirk Trossen
- Re: RTGWG feedback on APN next steps chongfeng.xie@foxmail.com
- Re: RTGWG feedback on APN next steps zhuyq8@chinatelecom.cn
- Re: RTGWG feedback on APN next steps 贺鲲鹏
- RE: RTGWG feedback on APN next steps Jeff Tantsura
- Re: RTGWG feedback on APN next steps Liang Felix