RE: A new draft on APN for your review, thank you!

["Pengshuping (Peng Shuping)" <[e-mail]>]

Hi Gyan,

It is truly great to receive your such positive feedback and support on this work! Welcome on board! ☺

Indeed APN provides a new fine granularity marking. “A new paradigm of QoE type marking” as you called sounds very inspiring. Would you like to elaborate a bit more?

Would you also like to elaborate more on the benefits which you as an operator could receive when using SLA parameters such as bandwidth, delay, jitter? We got some concerns before regarding the forwarding efficiency imposed by taking those parameters. What are your opinions on this “potential issue”? How to encapsulate them more efficiently?

These elaborations could be further integrated into the relevant drafts if you like, to serve as the potential work items of APN in IETF.

Thank you!

To all, it would also be good to hear your opinions and suggestions as well. Thanks!

Best regards,
Shuping


From: Gyan Mishra [mailto:[e-mail]]
Sent: Saturday, January 16, 2021 11:22 AM
To: Pengshuping (Peng Shuping) <[e-mail]>
Cc: [e-mail]; [e-mail]
Subject: Re: A new draft on APN for your review, thank you!


Hi Shuping and Authors

I am a new member of APN after reading through the all the APN drafts.  Very interesting and great idea.

Great way to leverage IPv6 data plane extension header concept along with SRv6 path steering coloring for 5G network slicing to create a new paradigm of QOE type marking matching and scheduling APN flow to map to discrete SR-TE paths via SDN controller.

I am very interested in the APN concepts and the SLA gap that exists for operators to convey bandwidth, delay and jitter which is has been a Day 1 missing gap for QOS 5-tuple packet classification marking and scheduling.  Was out of scope of QOS but it would have been nice for operators if that were possible.  With this new APN architecture operators can now signal via IPv6 EH options encoded sub-tlv for bandwidth, delay and jitter in IPv6 EH headers HBH, DOH or SRH.  I like it.

I would be interested in collaborating on the APN efforts.

Some feedback on the problem statement draft:

https://tools.ietf.org/html/draft-li-apn-problem-statement-usecases-01

In the problem statement draft section 3 some feedback.  Also feedback overall for the APN architecture.

For operators QOS DSCP marking and  PHB scheduling has been able to provide IP SLA bandwidth guarantees for services provided today with Gold Bronze Silver QOS guaranteed based on traffic types voice, video data for decades.  However it did not provide any fine IP SLA granularity for bandwidth, delay and jitter which has really been out of scope for QOS.  Their have been other methods that most vendors have IP SLA application probes to monitor bandwidth, delay, jitter to stay within certain pre defined operator constraints.  However there has never been a method to take SLA parameters such as bandwidth, delay, jitter and instantiate a path.

The paradigm has now expand to include 5G network slicing and shared and dedicated resources and isolation capabilities and DETNET framework to improve real time voice and video services.  With the paradigm change for 5G, APN is now a much needed to provide the fine granularity SLA that now discretely includes bandwidth, delay and jitter components in real time as part of the provisioning process of the SR-TE path instantiation mapping.


Kind Regards

Gyan


On Mon, Dec 14, 2020 at 10:12 PM Pengshuping (Peng Shuping) <[e-mail]<mailto:[e-mail]>> wrote:

Dear all,



A new draft on APN has been posted, https://datatracker.ietf.org/doc/html/draft-peng-apn-scope-gap-analysis.



In this draft, we clarified the scope of the APN work in IETF, introduced an example use case and the basic solution. Moreover, we compared with the existing “similar” work/solutions and did corresponding gap analysis.



Your review and comments are very much appreciated. Thank you!



Best regards,

Shuping





A new version of I-D, draft-peng-apn-scope-gap-analysis-00.txt

has been successfully submitted by Shuping Peng and posted to the IETF repository.



Name:              draft-peng-apn-scope-gap-analysis

Revision: 00

Title:                 APN Scope and Gap Analysis

Document date:      2020-12-16

Group:              Individual Submission

Pages:              11

URL:            https://www.ietf.org/archive/id/draft-peng-apn-scope-gap-analysis-00.txt

Status:         https://datatracker.ietf.org/doc/draft-peng-apn-scope-gap-analysis/

Htmlized:       https://datatracker.ietf.org/doc/html/draft-peng-apn-scope-gap-analysis

Htmlized:       https://tools.ietf.org/html/draft-peng-apn-scope-gap-analysis-00





Abstract:

   The APN work in IETF is focused on developing a framework and set of

   mechanisms to derive, convey and use an identifier to allow for

   implementing fine-grain user-, application-, and service-level

   requirements at the network layer.  This document describes the scope

   of the APN work and the solution gap analysis.



_______________________________________________
rtgwg mailing list
[e-mail]<mailto:[e-mail]>
https://www.ietf.org/mailman/listinfo/rtgwg
--

[图像已被发件人删除。]<http://www.verizon.com/>

Gyan Mishra

Network Solutions Architect

M 301 502-1347
13101 Columbia Pike
Silver Spring, MD