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

Gyan Mishra <hayabusagsm@gmail.com> Wed, 10 February 2021 03:48 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 6B5F43A12DA; Tue, 9 Feb 2021 19:48:26 -0800 (PST)
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, 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 XXE7u5DG3Fwu; Tue, 9 Feb 2021 19:48:24 -0800 (PST)
Received: from mail-pf1-x42b.google.com (mail-pf1-x42b.google.com [IPv6:2607:f8b0:4864:20::42b]) (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 1747B3A12BB; Tue, 9 Feb 2021 19:48:24 -0800 (PST)
Received: by mail-pf1-x42b.google.com with SMTP id k13so380227pfh.13; Tue, 09 Feb 2021 19:48:24 -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=lYe2w2+q+en4IQOG67CKi8ADXvVgPaLlGru+cU8iYeM=; b=LhW8h41Bmu6H7J8G7g0VqFmXAoy6Kv5A/EenH+gxokUTEmgfU83KqYInTajj3lcc4/ gqD6FnVXlD75wFdcRIbOjDs5gN6EWOJl9+f7Ayh6z4khKfPRiwiULBkmwxt20HiiO2FJ 9c3KYrqExy1R+gef+YUg0hwJju0g5yu8nQfU6+KbA4mzU2QvVjj3T0EuVjuxIKDiFHWI gRw4gFTIKJ0/j/B0EOAYMwMre+eAdVRUJvIOlT9da0WZHTXUXlsON5YS/rudI5YkSmRA 3djvUjvdF9AWkjrOSggpAmMiuqp7VDhqzl8Z2VjZmOnFy9E6Ngp7+6pfmKae/YNMbDME p85A==
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=lYe2w2+q+en4IQOG67CKi8ADXvVgPaLlGru+cU8iYeM=; b=eUInwRPbEc1UiCr1N+ly/FWA9mCw5iJecLIsE9VU0dVl+h0JxoCe0HeclPe5MD0QNi 9MhxjDSmJuqfHdXBF5W+ECK6YjjpC/fibLRApfxqUnC8jF5CsmJvjoUGbrni0dFIty4d huvGCOlQN3tpAiOeZpVk+NFnDnnPfcOMZY8lQApUB9aITWXlEKWTuLn6YiGD1S7xSZgv 20HTZcEQqDn35d+18CjNKBYst72vFvYhKMhZlGTXcnKZJK6X5W6JpaNJYw8gGS0pYs6o zErpqbrfexJuCPN2Jdp+zfzE/rneG//I5vN83fsugn8GbsF6Kldm+ZiGq6E652YXcR94 gRNw==
X-Gm-Message-State: AOAM533dWHRSQH5GAnFoSwvcrBR0I8DP4/Mf6UMdy9ahIA4gn5cM1Kck Uy/AYW1IXqbjMjMGJIeOn/0H+Lm5EGUIVuvzU9Q=
X-Google-Smtp-Source: ABdhPJxxlOdkxC8b2qgCfpIPXE/4sLEh7sO4kKaPMol0QIOqyQ04+TCjVuG53r02KAz/Spcs9GuLksSspRRGgArrm28=
X-Received: by 2002:a65:6547:: with SMTP id a7mr1206591pgw.50.1612928903380; Tue, 09 Feb 2021 19:48:23 -0800 (PST)
MIME-Version: 1.0
References: <OS0P286MB0338E6143AB38DA4BD74CD43DAB39@OS0P286MB0338.JPNP286.PROD.OUTLOOK.COM> <CABNhwV0hbhnkWrbUbSCEbvO=Xd29_QiPGraoZE-Rnc6CRPFjsw@mail.gmail.com> <4278D47A901B3041A737953BAA078ADE1988FFD3@dggeml512-mbs.china.huawei.com>
In-Reply-To: <4278D47A901B3041A737953BAA078ADE1988FFD3@dggeml512-mbs.china.huawei.com>
From: Gyan Mishra <hayabusagsm@gmail.com>
Date: Tue, 09 Feb 2021 22:48:12 -0500
Message-ID: <CABNhwV0CtxwnpDs9_msJdhpK1t5Gc-2mtXUPeswSkOm75SCLDw@mail.gmail.com>
To: "Pengshuping (Peng Shuping)" <pengshuping@huawei.com>
Cc: "apn@ietf.org" <apn@ietf.org>, "int-area@ietf.org" <int-area@ietf.org>, "liupengyjy@outlook.com" <liupengyjy@outlook.com>, "rtgwg@ietf.org" <rtgwg@ietf.org>
Content-Type: multipart/related; boundary="000000000000569dd605baf34675"
Archived-At: <https://mailarchive.ietf.org/arch/msg/apn/FOhlpmKKJDObvvuB0KhESs0IfRA>
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: Wed, 10 Feb 2021 03:48:26 -0000

Hi Shuping

Welcome and much obliged to be part of the APN team!!

My throughs are that we would cater each
presentation based on the WG audience so let’s say for 6MAN we delve deep
into APN use of extension headers.

For Spring it would be about SR-TE steering path instantiation and related
caveats and maybe how to manage or extent trust for inter provider SR-TE
for network slice.

For TEAS we would discuss details of 5G and network slicing framework using
APN ID and steering.

Just a few examples


Kind Regards

Gyan

On Fri, Feb 5, 2021 at 5:15 AM Pengshuping (Peng Shuping) <
pengshuping@huawei.com> wrote:

> Dear Gyan,
>
>
>
> Truly appreciate your support on APN! It has been great to have you on
> board. Thank you very much!
>
>
>
> We would need to discuss more on how to have productive discussions in
> these groups and collect feedback so to keep this work progressing.
>
>
>
> What would be desired to be heard in these presentations and discussed in
> the meetings? Suggestions are very welcomed.
>
>
>
> Best regards,
>
> Shuping
>
>
>
>
>
> *From:* Gyan Mishra [mailto:hayabusagsm@gmail.com]
> *Sent:* Thursday, February 4, 2021 12:16 PM
> *To:* liupengyjy@outlook.com
> *Cc:* Pengshuping (Peng Shuping) <pengshuping@huawei.com>; apn@ietf.org;
> int-area@ietf.org; rtgwg@ietf.org
> *Subject:* Re: [Apn] The official instructions on the next step of APN
>
>
>
>
>
> 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
>
> --
>
> [image: 图像已被发件人删除。] <http://www.verizon.com/>
>
> *Gyan Mishra*
>
> *Network Solutions Architect *
>
>
>
> *M 301 502-1347 13101 Columbia Pike
> <https://www.google.com/maps/search/13101+Columbia+Pike?entry=gmail&source=g>
> *Silver Spring, MD
>
>
>
-- 

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

*Gyan Mishra*

*Network Solutions A**rchitect *



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