Re: RTGWG feedback on APN next steps

Gyan Mishra <hayabusagsm@gmail.com> Wed, 06 April 2022 13:48 UTC

Return-Path: <hayabusagsm@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 8A0D73A1205; Wed, 6 Apr 2022 06:48:45 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.097
X-Spam-Level:
X-Spam-Status: No, score=-2.097 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_REMOTE_IMAGE=0.01, 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 RKdradZG2-Bs; Wed, 6 Apr 2022 06:48:41 -0700 (PDT)
Received: from mail-pj1-x102b.google.com (mail-pj1-x102b.google.com [IPv6:2607:f8b0:4864:20::102b]) (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 E1B5D3A11E2; Wed, 6 Apr 2022 06:48:40 -0700 (PDT)
Received: by mail-pj1-x102b.google.com with SMTP id a16-20020a17090a6d9000b001c7d6c1bb13so2727301pjk.4; Wed, 06 Apr 2022 06:48:40 -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=jBRyZ6xOtTGMDMkth4KhBwrriNHGlXJMnxP9QPmhmAY=; b=KrO/ra2rJzDhqg7dphmY8SiEKiUgxFVhsJ1AitX6y6t/1yqDw1RS+qInr8e2HXEjOy Hzfnhm2MB5S+kpDHSPmlNzcwnEtEiLnO9zHdeM85gvJRUQP7zAbOeqiBi6bNQqI1l2MR OYxVIiFSII4/i7vKK9UUcUDC7doZA2wXKeyQ9WQ9qR/WTQoWO1qbMGDn1jWnQ2HN/Zrt S6ve9KqyjX/zjCtS9LYwPd/5Pt2pmFem6Dvaxe5JWKr4dOfc63Yv9MnPhRVid010aQw/ MjUzrvC8XM/YQNDm9p0Ufukc+NuMPpqahb4GlMGpjIWDcCEp/l6UYT7MP56W+REYE/eH cJbQ==
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=jBRyZ6xOtTGMDMkth4KhBwrriNHGlXJMnxP9QPmhmAY=; b=iLqYr9vvQJ+BjSFnOI/1qMD0ulzMxM69dEFtRaIGcQQP6P5wm8gbgCBWCpDYia4Flp nAcu+Nb/YCMH0KQpxSs8j1l8I8kTScqjAWaFvxvJpza97YwF1CwkecGjiR9Go7bYcNWt 4pME1/BaIWS6gWtq+qh98apf1jEv9YkckE1t2JBpecUmg7qEeM+joGoAQ6EThLQmiQun H09CZ9eq0u2DMHi8nODRdgvHLR4c2FzZO7NJ3BQKIpYXCMb1PwIxcCwMtCUpc9Ovsxc6 hV85pnvkimfvjBAeBldUwnqeGsyNzS0kVJHpXHIWCijh6EsF19ZV7RuDPtMriIG4hvYA y4hA==
X-Gm-Message-State: AOAM530HzV7Oxl2p6/wb2sR5fcUXPS8W07tGmre11N0NH6UgrDU/plxK jXNE6yyPCEc1GO/bSnT/ED9+no3tnGPR7vzpv/4qE2oc
X-Google-Smtp-Source: ABdhPJxKtBED+mngTeMd2onO4OySMq7WptmeiUkImoVvDFozI4TIU4HLNiqpfWcLhBdJK36jt4/RFbEYhcwrsS8nuWA=
X-Received: by 2002:a17:902:b613:b0:156:7d82:c09b with SMTP id b19-20020a170902b61300b001567d82c09bmr8856886pls.80.1649252919564; Wed, 06 Apr 2022 06:48:39 -0700 (PDT)
MIME-Version: 1.0
References: <204D8DE6-F51C-4551-B1D7-1D69DBCA3626@hxcore.ol> <005401d849b4$34803cf0$9d80b6d0$@com>
In-Reply-To: <005401d849b4$34803cf0$9d80b6d0$@com>
From: Gyan Mishra <hayabusagsm@gmail.com>
Date: Wed, 6 Apr 2022 09:48:28 -0400
Message-ID: <CABNhwV3hVq1OHFY9y0tMYmLDYNO=D_OhWefec3-9T_0+R4KOWQ@mail.gmail.com>
Subject: Re: RTGWG feedback on APN next steps
To: Feng Yang <yangfeng@chinamobile.com>
Cc: Jeff Tantsura <jefftant.ietf@gmail.com>, RTGWG <rtgwg@ietf.org>, rtg-ads@ietf.org, rtgwg-chairs <rtgwg-chairs@ietf.org>
Content-Type: multipart/alternative; boundary="0000000000006a5f9105dbfc9e65"
Archived-At: <https://mailarchive.ietf.org/arch/msg/rtgwg/GzY4iwqjUhzlSVISuL8AAmTA1Qg>
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 13:48:46 -0000

Dear RTGWG

After the BOF and many rounds of review of APN, we  have from each round
have clarified the scope of APN as well as resolution of all outstanding
issues from the BOF.  Any outstanding issues not closed out that still
exist, we would like to openly address and make part of the defined
deliverables.

We would like to continue the work as we have received positive feedback
and interest from the IETF community.

Many thanks to the RTGWG to provide a venue for APN for discussions.

As the APN work spans beyond the RTGWG charter to 6MAN, SPRING, BESS, IDR,
PCE  and possibly other WGs, I support the chairs recommendations on
forming a limited lifetime Focus WG for APN work with a set of defined
deliverables and milestones.

We would like to work with the RTGWG WG to solicit feedback on APN  in
building the set of defined deliverables and milestones.

Thank you

Gyan



On Wed, Apr 6, 2022 at 8:45 AM Feng Yang <yangfeng@chinamobile.com> wrote:

> Hi folks,
>
>
>
> After so many rounds of clarifications and a lot of work, now APN has a
> very clear scope as well as problem statement. We also have an use case
> draft of APN.
>
> We support the suggestion to have this APN focused WG and we would like to
> join the work on the APN framework.
>
>
>
> BR,
>
> Feng Yang
>
>
>
> *发件人:* rtgwg [mailto:rtgwg-bounces@ietf.org] *代表 *Jeff Tantsura
> *发送时间:* 2022年4月6日 01:15
> *收件人:* RTGWG; rtgwg-chairs; rtg-ads@ietf.org
> *主题:* 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.  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
>
-- 

<http://www.verizon.com/>

*Gyan Mishra*

*Network Solutions A**rchitect *

*Email gyan.s.mishra@verizon.com <gyan.s.mishra@verizon.com>*



*M 301 502-1347*