Hi Looking over the draft I’m struggling to tell the difference between an APN encoded in tunnel meta data and a 5G System QFI encoded in tunnel meta data. There appears to be a 1:1 conceptual alignment, classification at system ingress, derive the value, encode for use by intermediate systems in encapsulating metadata.
So I would observe that besides being functionally identical, compared to existing wireline deployments, the 5G System also has the rest of the tools to fully operationalize, apply policy to and monetize this stuff. And the BBF along with 3GPP are busy specifying convergence to add this functionality to wireline access…. 5G FMC Architecture (broadband-forum.org)<https://www.broadband-forum.org/technical/download/TR-470.pdf> And the 3GPP counterpart is TS 23.316 (release 16). FYI, the BBF is currently working on issue 2 of the 5G WWC specification set and looking to publish by YE. So what problem are we solving again here? Cheers Dave From: ipv6 <[email protected]> On Behalf Of Lizhenbin Sent: Tuesday, June 15, 2021 8:27 AM To: [email protected]; RTGWG <[email protected]> Cc: 6MAN <[email protected]> Subject: Clarification on the BNG deployment//RE: Application-Aware Networking (APN) focused interim Hi Folks, In the interim meeting, there were much discussion on the BNG deployment in the home broadband scenario. In the section 5 of the following draft, there is more details about the scenarios. https://www.ietf.org/archive/id/draft-li-apn-problem-statement-usecases-03.txt As far as I know, there are types of deployment of BNGs in the scenarios: 1. RG is directly connected with the BNG 2. RG is connected spanning the metro network. Because the BNG is responsible for the user management, if failure happens, it will have much negative effect on the users’ access to the Internet or other network services. If the second deployment method is used, the number of the BNG is small and the BNG can access more users, but the risk is high. If the first deployment is adopted, it may need more BNGs, but the risk can be low. So there is the trade-off in the network design and the deployment of the BNG. The draft takes the second deployment to illustrate that the QinQ information besides the 5-tuple information can also be mapped to APN ID when the packet traverses the metro network. That is the reason why not describe the first type of deployment. Best Regards, Robin From: Apn [mailto:[email protected]] On Behalf Of Pengshuping (Peng Shuping) Sent: Friday, June 4, 2021 10:53 PM To: [email protected]<mailto:[email protected]> Cc: 6MAN <[email protected]<mailto:[email protected]>>; RTGWG <[email protected]<mailto:[email protected]>> Subject: Re: [Apn] Application-Aware Networking (APN) focused interim Dear all, Many thanks for the questions, comments, and suggestions from those who joined the APN focused Interim meeting yesterday, which were very helpful to further refine the work and progress it forwards. Please find the meeting minutes and materials discussed yesterday. https://datatracker.ietf.org/meeting/interim-2021-rtgwg-01/session/rtgwg If you have any views, comments, and questions, please don’t hesitate to post them in the mailing list. Many thanks again to our AD and Chairs for arranging this Interim meeting! Nice weekend! ☺ Best regards, Shuping j From: ipv6 [mailto:[email protected]] On Behalf Of Pengshuping (Peng Shuping) Sent: Wednesday, June 2, 2021 9:14 AM To: [email protected]<mailto:[email protected]> Cc: 6MAN <[email protected]<mailto:[email protected]>>; RTGWG <[email protected]<mailto:[email protected]>> Subject: FW: Application-Aware Networking (APN) focused interim Dear all, Just a reminder that the APN focused Interim meeting @RTG will be held tomorrow, Thursday 2021-06-03 14:00 UTC. The Webex is attached. You could find the slides that are going to guide the discussions in the following link. There might be minor updates in the final slides. https://datatracker.ietf.org/meeting/interim-2021-rtgwg-01/session/rtgwg The tentative agenda is as follows, 1. Agenda bashing (10mins) –AD, Chairs 2. Problem Statement (30mins) – Gyan Mishra 3. Solution discussions (45-60mins) – Shuping/Robin 4. Wrap-up & action plan (10mins) – Chairs If you have any suggestions and comments, please let us know. Many thanks! Best regards, Shuping From: Apn [mailto:[email protected]] On Behalf Of Pengshuping (Peng Shuping) Sent: Friday, May 14, 2021 8:55 AM To: 6MAN <[email protected]<mailto:[email protected]>> Cc: [email protected]<mailto:[email protected]>; Routing Area Working Group <[email protected]<mailto:[email protected]>>; [email protected]<mailto:[email protected]> Subject: [Apn] FW: Application-Aware Networking (APN) focused interim Dear all, The APN Interim meeting has been scheduled on June 3rd. Please find the meeting information shared by the Chairs of the RTG WG below. In this APN Interim meeting, we are going to focus more on the discussions of the solutions (more overview than details), including 1. the design of the APN attribute itself 2. the encapsulation of the APN attribute on the various data planes (the encapsulation on the IPv6 data plane is an example) 3. the control plane protocols extensions for exchanging the APN attribute 4. NETCONF/YANG models for the NBI and SBI You are very welcomed to join the discussions, and your comments and suggestions are very much appreciated. Thank you! Best regards, Shuping From: rtgwg [mailto:[email protected]] On Behalf Of Jeff Tantsura Sent: Friday, May 7, 2021 6:38 AM To: Routing WG <[email protected]<mailto:[email protected]>>; RTGWG <[email protected]<mailto:[email protected]>> Subject: Application-Aware Networking (APN) focused interim Dear RTGWG, We have scheduled Application-Aware Networking (APN) focused interim (agenda to be published), June 3rd, 2021, 7:00AM PST Looking forward to seeing you, Cheers, Jeff and Chris When it's time, start your Webex meeting here. Thursday, June 3, 2021 7:00 AM | (UTC-07:00) Pacific Time (US & Canada) | 2 hrs Start meeting<https://ietf.webex.com/ietf/j.php?MTID=mc8ee2b80cb0fdd92745199a121f452db> More ways to join: Join from the meeting link https://ietf.webex.com/ietf/j.php?MTID=mc8ee2b80cb0fdd92745199a121f452db Join by meeting number Meeting number (access code): 161 149 3477 Meeting password: gpN26drAet4 Tap to join from a mobile device (attendees only) +1-650-479-3208,,1611493477##<tel:%2B1-650-479-3208,,*01*1611493477%23%23*01*> Call-in toll number (US/Canada) Join by phone 1-650-479-3208 Call-in toll number (US/Canada) Global call-in numbers<https://ietf.webex.com/ietf/globalcallin.php?MTID=m8fc024386f16ac264aaa306eeb5dff0c> Join from a video system or application Dial [email protected]<sip:[email protected]> You can also dial 173.243.2.68 and enter your meeting number. Join using Microsoft Lync or Microsoft Skype for Business Dial [email protected]<sip:[email protected]> If you are a host, click here<https://ietf.webex.com/ietf/j.php?MTID=m6b0d9545f1c064a6aa8f7739e2d4c763> to view host information. Need help? Go to https://help.webex.com
_______________________________________________ rtgwg mailing list [email protected] https://www.ietf.org/mailman/listinfo/rtgwg
