Re: [Apn] The official instructions on the next step of APN

Gyan Mishra <hayabusagsm@gmail.com> Thu, 04 February 2021 04:16 UTC

Return-Path: <hayabusagsm@gmail.com>
X-Original-To: apn@ietfa.amsl.com
Delivered-To: apn@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 8712A3A0C57; Wed, 3 Feb 2021 20:16:36 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.087
X-Spam-Level:
X-Spam-Status: No, score=-1.087 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, FREEMAIL_REPLY=1, HTML_MESSAGE=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, T_REMOTE_IMAGE=0.01, URIBL_BLOCKED=0.001] autolearn=no 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 HQweGpQ9Ym4P; Wed, 3 Feb 2021 20:16:34 -0800 (PST)
Received: from mail-pf1-x429.google.com (mail-pf1-x429.google.com [IPv6:2607:f8b0:4864:20::429]) (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 9B8B83A0C4C; Wed, 3 Feb 2021 20:16:34 -0800 (PST)
Received: by mail-pf1-x429.google.com with SMTP id m6so1301005pfk.1; Wed, 03 Feb 2021 20:16:34 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=0Ha+0ayrK/QaHnPzLDM8tltJSb/VHhDPQr/hR+aKhfM=; b=DbHdV9unZ3fagoyp5fb8AATQu7OIPH2XjeZwWyqIcR5TgFyaq3eS0WK43ycxxnTyRY AjCI70sB/rJaULtIDif+VtO9L42gqfc+LWZ8kLL4xPDo+Vbn/iZsMT7imc8XrYpCwugY 5HpPw0zui9T4QbOaDKVlnRLhWemoRBForwEA7umMWH16S9MXIdkAdvrZZyhSZnq+FdNr 0VNY7Q3unx70rNRnp5nkAD242BPsh6RCbm0oMPR+INhxBwbTOEA4eZoSlrI07PFvaMcD J4lhV/Bu7QPgzAK2S8EHr+3pbL6CPh5W/4lu2dSBhN/FxGkByBRRLi5A+lZVOgmVNGPH ktow==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=0Ha+0ayrK/QaHnPzLDM8tltJSb/VHhDPQr/hR+aKhfM=; b=SdTd3r1bJn9K5O/BsOD4VCUYHxburmhl0qD77y3ZFXSsdT8+oJlY/aNlQxC0euzTdn PsaLDilb3AC6xZythSQuat5W8uGZOcFUvcMkkluOTikQqJ1u7XdavvGz6uSXqAYFCdnl TClHV3olAAxJYSy20vqyLy7N7jeuKbRBwvjsv4I2KIEGVA3vmHtCgHl2i4A8BuLymqnf lNdfTFkDjSAfJKcYlo2pIWRvGiZTSfkYsVgTjZqhcTdSWTmoWQPQXz/3Tw3AU5ogLSOC MsM6dKClGBlFjkTTKB6w8bL+LNi2MqKg4hiS35Qn+aSOM4dYkGo1Bs6NCervtqPM4zsZ jDbg==
X-Gm-Message-State: AOAM532R1OiuHSm67E7mQktC1ytBIzkU3vcmYmFOrmzUUYO04RzoDhQY 02P2A6ClQAkMuRhHj7AN47CwG9rGfdGYNmJU3kU=
X-Google-Smtp-Source: ABdhPJw8Juap1A69A49Or9I8f1/CCis4NTDRZ2P65bNt51pzZx6gETYTC1FHvH/x3/7Q6e6CmBZwJQLOYjzNIWKvcp4=
X-Received: by 2002:a63:bd4a:: with SMTP id d10mr6962923pgp.18.1612412194085; Wed, 03 Feb 2021 20:16:34 -0800 (PST)
MIME-Version: 1.0
References: <OS0P286MB0338E6143AB38DA4BD74CD43DAB39@OS0P286MB0338.JPNP286.PROD.OUTLOOK.COM>
In-Reply-To: <OS0P286MB0338E6143AB38DA4BD74CD43DAB39@OS0P286MB0338.JPNP286.PROD.OUTLOOK.COM>
From: Gyan Mishra <hayabusagsm@gmail.com>
Date: Wed, 03 Feb 2021 23:16:23 -0500
Message-ID: <CABNhwV0hbhnkWrbUbSCEbvO=Xd29_QiPGraoZE-Rnc6CRPFjsw@mail.gmail.com>
To: "liupengyjy@outlook.com" <liupengyjy@outlook.com>
Cc: "Pengshuping (Peng Shuping)" <pengshuping@huawei.com>, "apn@ietf.org" <apn@ietf.org>, "int-area@ietf.org" <int-area@ietf.org>, "rtgwg@ietf.org" <rtgwg@ietf.org>
Content-Type: multipart/alternative; boundary="0000000000000f606d05ba7af84b"
Archived-At: <https://mailarchive.ietf.org/arch/msg/apn/IK1eoTwcALgnwpXqk0SS9qkOEfk>
Subject: Re: [Apn] The official instructions on the next step of APN
X-BeenThere: apn@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Application-aware Networking <apn.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/apn>, <mailto:apn-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/apn/>
List-Post: <mailto:apn@ietf.org>
List-Help: <mailto:apn-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/apn>, <mailto:apn-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 04 Feb 2021 04:16:37 -0000

Hi Shuping

I agree that APN has critical applicability for operators for 5G, DETNET
and even any public or private multicast MVPN streaming video content so
does have quite extensive applicability for operators.
There also maybe private SR  use cases for special SLA application flows
value added service.

As for productive discussions to move the ball forward with APN BOF, I do
agree with having discussions where network operators can share their
experiences and how APN can benefit so in that light as you stated IntArea
and RTGWG are a good start.
GROW maybe useful for in the global internet routing context and how APN
can play a role.

I think DETNET would be good for applicability statement,  and Spring, 6MAN
and TEAS maybe good from a APN architecture and design framework as APN
leverages IPv6 data plane EH headers and utilizes traffic steering SRv6
forwarding plane and also gets into 5G network slicing so then TEAS comes
into play and NS network slicing architecture.

I would be happy to present APN architecture and applicability at IETF 110.

Kind Regards

Gyan

On Wed, Feb 3, 2021 at 10:34 PM liupengyjy@outlook.com <
liupengyjy@outlook.com> wrote:

> It's good news that APN can be fully discussed in rtg and intarea'
> meetings.
>
> There have been many drafts of APN technology and scenarios. As an
> operator, we think APN is valuable and worthy of discussion and progress.
>
> Regards,
> Peng Liu(CMCC)
>
> ---Original---
> *From:* "Pengshuping (Peng Shuping)"<pengshuping@huawei.com>
> *Date:* Thu, Feb 4, 2021 09:39 AM
> *To:* "apn@ietf.org"<apn@ietf.org>;
> *Cc:* "int-area@ietf.org"<int-area@ietf.org>;"rtgwg@ietf.org"<
> rtgwg@ietf.org>;
> *Subject:* [Apn] The official instructions on the next step of APN
>
> Dear all,
>
>
>
> You may have seen the BoF announcement
> https://www.ietf.org/blog/ietf110-bofs/.
>
>
>
> The instructions on the next step of APN are officially confirmed,
>
> 1.      Presentations and discussions in the RTGWG and INTAREA meetings
> at IETF110.
>
> 2.      A virtual interim meeting of the RTGWG to be scheduled after
> IETF110 to go into more depth on this topic.
>
>
>
> Any suggestions on how to have fruitful discussions and progress the work
> in IETF are very welcomed. Thank you!
>
>
>
> “The Application-Aware Networking (APN) BOF proposal was focused on
> developing a framework and set of mechanisms to derive, convey, and use an
> identifier to allow for the signaling of fine-grained user-, application-,
> and service-level requirements at the network layer. This proposal was made
> for several previous IETF meetings and will benefit from further focused
> discussion at IETF 110 during the Routing Area Working Group (RTGWG
> <https://datatracker.ietf.org/wg/rtgwg/about/>) and Internet Area Working
> Group (INTAREA <https://datatracker.ietf.org/wg/intarea/about/>)
> meetings. A virtual interim meeting of the RTGWG to be scheduled after IETF
> 110 will go into more depth on this topic. Discussion continues on the Application-aware
> Networking <https://www.ietf.org/mailman/listinfo/apn> mailing list. ”
>
>
>
> Best regards,
>
> Shuping
>
>
> --
> Apn mailing list
> Apn@ietf.org
> https://www.ietf.org/mailman/listinfo/apn
>
-- 

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

*Gyan Mishra*

*Network Solutions A**rchitect *



*M 301 502-134713101 Columbia Pike *Silver Spring, MD