RE: Clarification on the BNG deployment//RE: Application-Aware Networking (APN) focused interim

Lizhenbin <> Wed, 16 June 2021 10:23 UTC

Return-Path: <>
Received: from localhost (localhost []) by (Postfix) with ESMTP id 34D473A0F35; Wed, 16 Jun 2021 03:23:36 -0700 (PDT)
X-Virus-Scanned: amavisd-new at
X-Spam-Flag: NO
X-Spam-Score: -3.598
X-Spam-Status: No, score=-3.598 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_FONT_LOW_CONTRAST=0.001, HTML_MESSAGE=0.001, HTTPS_HTTP_MISMATCH=0.1, RCVD_IN_DNSWL_MED=-2.3, RCVD_IN_MSPIKE_H2=-0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001, URI_NOVOWEL=0.5] autolearn=ham autolearn_force=no
Received: from ([]) by localhost ( []) (amavisd-new, port 10024) with ESMTP id SVx7c27lAKjn; Wed, 16 Jun 2021 03:23:29 -0700 (PDT)
Received: from ( []) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by (Postfix) with ESMTPS id 588C63A0F39; Wed, 16 Jun 2021 03:23:19 -0700 (PDT)
Received: from (unknown []) by (SkyGuard) with ESMTP id 4G4gxj6mhhz6K6Dw; Wed, 16 Jun 2021 18:13:29 +0800 (CST)
Received: from ( by ( with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256) id 15.1.2176.2; Wed, 16 Jun 2021 12:23:09 +0200
Received: from ( by ( with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256) id 15.1.2176.2; Wed, 16 Jun 2021 18:23:08 +0800
Received: from ([]) by ([]) with mapi id 15.01.2176.012; Wed, 16 Jun 2021 18:23:08 +0800
From: Lizhenbin <>
To: "STARK, BARBARA H" <>, "''" <>, 'RTGWG' <>
CC: '6MAN' <>
Subject: RE: Clarification on the BNG deployment//RE: Application-Aware Networking (APN) focused interim
Thread-Topic: Clarification on the BNG deployment//RE: Application-Aware Networking (APN) focused interim
Thread-Index: Addh+M6lhAmHMgeRQguGYq8NM4jGnwAKjtIQABzEasA=
Date: Wed, 16 Jun 2021 10:23:07 +0000
Message-ID: <>
References: <> <>
In-Reply-To: <>
Accept-Language: zh-CN, en-US
Content-Language: zh-CN
x-originating-ip: []
Content-Type: multipart/alternative; boundary="_000_d2e5ff4539074805ae1077b0d9112b4ehuaweicom_"
MIME-Version: 1.0
X-CFilter-Loop: Reflected
Archived-At: <>
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <>
List-Unsubscribe: <>, <>
List-Archive: <>
List-Post: <>
List-Help: <>
List-Subscribe: <>, <>
X-List-Received-Date: Wed, 16 Jun 2021 10:23:37 -0000

Hi Barbara,
Please refer to my reply inline.

Best Regards,

Sent: Wednesday, June 16, 2021 4:53 AM
To: Lizhenbin <>; '' <>; 'RTGWG' <>
Cc: '6MAN' <>
Subject: RE: Clarification on the BNG deployment//RE: Application-Aware Networking (APN) focused interim

It seems odd not to consider a broadband deployment architecture like
in the context of wanting to enable improved usage of network slicing and such.

The BNG architecture does what it was intended to do: Ethernet aggregation.
If you want to do something else, you should probably consider a different architecture (or
consider working with BBF to evolve its BNG architecture into something different --
if you don't want the AGF architecture with a 5G-RG described in the above link).

Note the BNG is a BBF-defined network element. AFAIK, it was originally defined in:

To Michael's comments: While there are still some (many?) operators who use PPPoE, I'm aware of
major operators who use BNGs without PPP or PPPoE. PPP is not a core function when
operating a BNG in an access network. Ethernet-based aggregation is the central feature that
defines a BNG.

[Robin] Thanks for your information on the network architecture of the BNG. As what I reply Michael,
in the home broadband scenario, we focus on the metro network and the case that the existing L2
information in the packet can also be used to map to the APN ID. There may be more existing
information from the PPPOE or IPOE packet header. We can take them into account. Your information
is a good input to prioritize the possible existing information.

So, again, if someone wants to do network slicing instead of Ethernet aggregation
(based on VLAN tags), they are right that the BNG is not the right access architecture
component. The AGF with a 5G-RG is much better suited to supporting network slicing.
Fortunately, a specification already exists for that architecture (complete with detailed
requirements for the 5G-RG [in TR-124] and how to manage the 5G-RG using TR-181).
[Robin] The network slice described in the drafts of the APN work is the IETF network slice scenario in the metro
network or the mobile transport network. The edge can steer the packet to the corresponding IETF network slice
according to the policy matching the APN ID.


From: ipv6 <<>> On Behalf Of Lizhenbin
Sent: Tuesday, June 15, 2021 10:27 AM
To:<>; RTGWG <<>>
Cc: 6MAN <<>>
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.<;!!BhdT!3x44cVFathXW5PntzRYHyVvBmnpz1XlgAyiKPu5OZGeTMI8ZIF8YEX9EiAnJ_w$>

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,

From: Apn [] On Behalf Of Pengshuping (Peng Shuping)
Sent: Friday, June 4, 2021 10:53 PM
Cc: 6MAN <<>>; RTGWG <<>>
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.<;!!BhdT!3x44cVFathXW5PntzRYHyVvBmnpz1XlgAyiKPu5OZGeTMI8ZIF8YEX8NEVCG-Q$>

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 [] On Behalf Of Pengshuping (Peng Shuping)
Sent: Wednesday, June 2, 2021 9:14 AM
Cc: 6MAN <<>>; RTGWG <<>>
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.<;!!BhdT!3x44cVFathXW5PntzRYHyVvBmnpz1XlgAyiKPu5OZGeTMI8ZIF8YEX8NEVCG-Q$>

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,

From: Apn [] On Behalf Of Pengshuping (Peng Shuping)
Sent: Friday, May 14, 2021 8:55 AM
To: 6MAN <<>>
Cc:<>; Routing Area Working Group <<>>;<>
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,

From: rtgwg [] On Behalf Of Jeff Tantsura
Sent: Friday, May 7, 2021 6:38 AM
To: Routing WG <<>>; RTGWG <<>>
Subject: Application-Aware Networking (APN) focused interim


We have scheduled Application-Aware Networking (APN) focused interim (agenda to be published), June 3rd, 2021, 7:00AM PST

Looking forward to seeing you,

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<;!!BhdT!3x44cVFathXW5PntzRYHyVvBmnpz1XlgAyiKPu5OZGeTMI8ZIF8YEX_uCjrJSg$>

More ways to join:

Join from the meeting link<;!!BhdT!3x44cVFathXW5PntzRYHyVvBmnpz1XlgAyiKPu5OZGeTMI8ZIF8YEX_uCjrJSg$>

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<;!!BhdT!3x44cVFathXW5PntzRYHyVvBmnpz1XlgAyiKPu5OZGeTMI8ZIF8YEX9uh2QDPQ$>

Join from a video system or application


You can also dial and enter your meeting number.

Join using Microsoft Lync or Microsoft Skype for Business


If you are a host, click here<;!!BhdT!3x44cVFathXW5PntzRYHyVvBmnpz1XlgAyiKPu5OZGeTMI8ZIF8YEX8obFl-0w$> to view host information.

Need help? Go to<;!!BhdT!3x44cVFathXW5PntzRYHyVvBmnpz1XlgAyiKPu5OZGeTMI8ZIF8YEX8uzIUdug$>