Re: RTGWG feedback on APN next steps
Dhruv Dhody <dhruv.ietf@gmail.com> Fri, 08 April 2022 03:08 UTC
Return-Path: <dhruv.ietf@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 24CC53A19B3;
Thu, 7 Apr 2022 20:08:11 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.107
X-Spam-Level:
X-Spam-Status: No, score=-2.107 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,
HTML_MESSAGE=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 PF28yolK2ayz; Thu, 7 Apr 2022 20:08:06 -0700 (PDT)
Received: from mail-io1-xd36.google.com (mail-io1-xd36.google.com
[IPv6:2607:f8b0:4864:20::d36])
(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 6C27A3A0864;
Thu, 7 Apr 2022 20:08:06 -0700 (PDT)
Received: by mail-io1-xd36.google.com with SMTP id k25so9151612iok.8;
Thu, 07 Apr 2022 20:08:06 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20210112;
h=mime-version:references:in-reply-to:from:date:message-id:subject:to
:cc; bh=U6hS9HsheiX79SOsav93c2vW6P0JRytyozoC9mMPPlA=;
b=ePRD5peOfJNtxKQ+QzFSxe/OVyLj9MXZOv9xy9i5vpmKQlKhyIWq3xlKMooe9z9t+a
WU2RBzAu1tWX5gU4shzY4BHDTGggf8EYnweW74aCNvnKrIdL9/Y8lC5L4948iXAtSJI8
EZZHfOGHo/cH1iPp9wqnzS/L5mOm/fPJWgeYF+ca8k43wR0+vjalZEOyC+1wqXfipDYC
tcQAfECXPkky3F0lU+wsAGRalzrq9oN3DY2w9ChHCalQADRQLs5TbMCLUUlxKaI87y0M
aNNldjKI2GWuiwyOx+R9/V5m4eYJ96KYRPEQYCMVls0txl4KQh+FJ2AXq88/lLEp9lTF
MZOw==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
d=1e100.net; s=20210112;
h=x-gm-message-state:mime-version:references:in-reply-to:from:date
:message-id:subject:to:cc;
bh=U6hS9HsheiX79SOsav93c2vW6P0JRytyozoC9mMPPlA=;
b=bI+zhttzWURyceofMIgT099lhkVku4Y/3s3uQwulBBp3q2hqvnu3Xx17KAGlIPuOJN
04WHoeCJHBd0X1TSrQHPHSNo2d4sV6JI4pGkFQYzdGy2p6gns4Pw1fegndWM23xHe45c
vOfLa0BbgvDdNz8acyqgTbrhHdOEon8Z7MMG/UjSkZA7MXyXJVuDh1nYi6PlRCSrsDCL
knrYGf4RVwn13NxpKeCnq0pnMCOfnFVpLyZyDT8c7DD1p7XNchkeJzo/Cxg3JjF07Qiu
WZi1VNvNUPjUGfUBDT+huSncz1i7xnNM1gh0A+wDuwquwZi+U1zdSz/KBFMYe4JhZ/kr
TbCA==
X-Gm-Message-State: AOAM531D/dSSxMHoKGrY2JqsNEmLyOGdq5cNzlvPcVtyciNfACWcZBMr
yNUG3GNYpNbG5XpZXLSH7/HBV4ONRCkjYLKzQ/U=
X-Google-Smtp-Source: ABdhPJzm1a6PinvqXuE4ID38rHwitbxIhDfdZuoSLygbDIEBh58t9zUAaJPw9sSPH8ObiWWgLK2SC9pc/2ShyWtITVY=
X-Received: by 2002:a05:6638:248c:b0:323:9560:5a7c with SMTP id
x12-20020a056638248c00b0032395605a7cmr8611774jat.161.1649387285267; Thu, 07
Apr 2022 20:08:05 -0700 (PDT)
MIME-Version: 1.0
References: <204D8DE6-F51C-4551-B1D7-1D69DBCA3626@hxcore.ol>
In-Reply-To: <204D8DE6-F51C-4551-B1D7-1D69DBCA3626@hxcore.ol>
From: Dhruv Dhody <dhruv.ietf@gmail.com>
Date: Fri, 8 Apr 2022 08:37:29 +0530
Message-ID: <CAB75xn5wEWNPuL-AVH7by9_XX5D4sMWAN+AjxuEShO4ODMP9uQ@mail.gmail.com>
Subject: Re: RTGWG feedback on APN next steps
To: Jeff Tantsura <jefftant.ietf@gmail.com>
Cc: RTGWG <rtgwg@ietf.org>, rtgwg-chairs <rtgwg-chairs@ietf.org>,
"rtg-ads@ietf.org" <rtg-ads@ietf.org>
Content-Type: multipart/alternative; boundary="0000000000003c49c905dc1be75d"
Archived-At: <https://mailarchive.ietf.org/arch/msg/rtgwg/u1OV48m6rnF_qHJing9TpiyEpJU>
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 03:08:12 -0000
Hi Chairs, Thanks for initiating this call for the feedback! I support the creation of a new WG and will participate and contribute to it. A dedicated home to reach a rough consensus on the scope of the problem and framework is necessary to make progress. I see that there are still some concerns that have been expressed on the list, but IMHO the chances of resolving them in a dedicated WG are higher as we drive towards consensus. I agree that the scope of the WG and the charter would need to be well crafted. Thanks! Dhruv On Tue, Apr 5, 2022 at 10:45 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