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

Eduard Metz <etmetz@gmail.com> Wed, 16 June 2021 13:55 UTC

Return-Path: <etmetz@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 690743A1960; Wed, 16 Jun 2021 06:55:05 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.096
X-Spam-Level:
X-Spam-Status: No, score=-2.096 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_FONT_LOW_CONTRAST=0.001, HTML_MESSAGE=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=unavailable 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 AFul4qTweZVJ; Wed, 16 Jun 2021 06:54:59 -0700 (PDT)
Received: from mail-lf1-x133.google.com (mail-lf1-x133.google.com [IPv6:2a00:1450:4864:20::133]) (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 CD6AE3A1963; Wed, 16 Jun 2021 06:54:58 -0700 (PDT)
Received: by mail-lf1-x133.google.com with SMTP id q20so4530415lfo.2; Wed, 16 Jun 2021 06:54:58 -0700 (PDT)
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=/KrlYhG5j7wD1oG7CyoPaMnfGTQNPpNdSlQeLlbeg3Q=; b=Su3QuRMt582EPdnYAcYBS/CXUsqkDEjPJ2Woi2h3bjlD1LGNIhYZaHkvmOje3tYN0K sL5GEc57HDBi0tYMAkxtnwoIrfA2vAo6D7WIsD8f2bC2unDcUzXQKLrJLqHTRXegA/IR ycg5qRrlPJLSSKxvRCUgFh1y7iNd/jq9+xy0gfOuJn2t/A2Dilujl8KBkIR+Ir0+Dbgr Dlo2InIqREjRgr4PtfR+Z4RjMVQCp0hbJ8/j4GxJMJouvZ17lsFiTQiWFGiwmbI6+grp W+o8hQP3145SdCnUQudYWph3Nr6mUm7h0Uv3zyIhIuTTRxMnTHvkPjL+sVp1Bouzv/Ha 83KQ==
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=/KrlYhG5j7wD1oG7CyoPaMnfGTQNPpNdSlQeLlbeg3Q=; b=CbUiEZanmaAAjHUHKZzoyL5oLPpSYrSpz4gQ8/uIsUANIeXqtAL3KwlNqJqFcnGUOw I4ROLYGtB1d8LiaT5W5ejiRMsq82gRbGj4bzzD+AQtPJ0wLxJO3RS3F6tACw90RyvJtT EFJ4+fM9Dj2CVgXF91g3myY4Ik7BTn8pfvVKv4qomVy6fxhus3qVFkTkY4q0Szhq81eN G2yt7Hrfi8vm9b4G/QtficMyOYqJcHxR8RcHFQ6hEeeUJjFQePaMYbnGHDwlyaTcqLiK C5iQZOLo5YhL7XbsMcRySvtUMtvg6oBVy4Q574xhGyCr7XiQgX7NclWwVDFAJ/wLvrHG J8wQ==
X-Gm-Message-State: AOAM530yEpuIABmqEyan/3W10gdZrGj+j5l4NGsrB+GwI0ZVoo9LS5MB d7hEkUeKsyvS3VSa51OeommG3oD/bWm6rskKfJo=
X-Google-Smtp-Source: ABdhPJwFDcjYkn0BvYF1OfTyM9/tla911rLiBUWPKTEMllzp6PXp8ZHbiguRFZfKliddzEc00RpdCIn2MFyXHkDSQwk=
X-Received: by 2002:a05:6512:2283:: with SMTP id f3mr3792696lfu.523.1623851695553; Wed, 16 Jun 2021 06:54:55 -0700 (PDT)
MIME-Version: 1.0
References: <839c7b39a645469eb11d91583355d4ec@huawei.com> <MW4PR15MB4474DB33F6206B025B231689D0309@MW4PR15MB4474.namprd15.prod.outlook.com> <8574bbe3a3994177a993d2b4a3def4a7@huawei.com>
In-Reply-To: <8574bbe3a3994177a993d2b4a3def4a7@huawei.com>
From: Eduard Metz <etmetz@gmail.com>
Date: Wed, 16 Jun 2021 15:54:44 +0200
Message-ID: <CAG=3OHckS0XOG+UCrqsqooeGBU8i_pHUr3_77=MLES+QpxNiTA@mail.gmail.com>
To: "Pengshuping (Peng Shuping)" <pengshuping@huawei.com>
Cc: David Allan I <david.i.allan=40ericsson.com@dmarc.ietf.org>, Lizhenbin <lizhenbin@huawei.com>, "apn@ietf.org" <apn@ietf.org>, RTGWG <rtgwg@ietf.org>, 6MAN <6man@ietf.org>
Content-Type: multipart/alternative; boundary="0000000000007b418d05c4e26f57"
Archived-At: <https://mailarchive.ietf.org/arch/msg/apn/gwLnTuUPaGP_xq8LCVCbb2dJL8Y>
Subject: Re: [Apn] Clarification on the BNG deployment//RE: Application-Aware Networking (APN) focused interim
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, 16 Jun 2021 13:55:06 -0000

Is it correct to say that this proposes a mapping / encoding of
"application" information into a common transport / infrastructure layer
based on information from either the encapsulated / carried traffic and/or
the originating domain? Kind of similar to how e.g. the classification and
marking of the MPLS TC field on a PE, but now with a more wider use of the
application information.

I find the term application a bit confusing, in particular in the fixed
broadband case the granularity in the example is rather coarse.
Application suggests something more finegrained, at least to me.
The use of VLAN for classification may not be generally available, if the
access is based on a single VLAN a more complex classification is required
anyway.

All scenarios include some kind of tunneling in which the actual user
carried. Is this the scope of this APN solution?
I would expect application awareness would be relevant end-to-end, or at
least within one domain. For example, in the fixed broadband case, what
happens after the BNG?

SD-WAN on the other hand is an "end-to-end" scenario,it may even span
multiple operator domains.
Also note that SD-WAN may make use of FBB or MBB as an access, possibly
creating multiple layers of APN.

The APN domain now is bounded by PEs (for FBB and MBB), wouldn't it be
better to specify functional elements as the boundaries? Or do you consider
the PE to be a functional element as well?
In case of FBB the edge of an APN domain could be implemented in the same
node as the OLT (or BNG on the other side) or even the CPE.

cheers,
  Eduard



On Wed, Jun 16, 2021 at 5:01 AM Pengshuping (Peng Shuping) <
pengshuping@huawei.com> wrote:

> Hi David,
>
>
>
> I think the network scenarios in Robin’s mind are something like the
> diagrams below.
>
>
>
> MBB:
>
> gNB --  PE1 -----  (SRv6) tunnel ---- PE2 -- UPF
>
>
>
> FBB:
>
> RG --  PE1 ----- (SRv6) tunnel ---- PE2 -- BNG
>
>
>
> In the MBB, “The QFI is carried in an encapsulation header on N3 (and N9)”
> – TS23.501. That is between gNB and UPF is the GTP-u and QFI is used in the
> GTP-u tunnel, while between PE1 and PE2 is the IP metro network and APN
> attribute is used in the IP tunnel (e.g. SRv6 tunnel). At PE1, the QFI and
> other information in the packet header (payload is not touched) could be
> used to construct the APN attribute based on the Operator’s configurations,
> which will be encapsulated in an IP tunnel header such as SRv6 header on
> top of the GTP-u tunnel. This APN attribute will be used within the IP
> metro network to do the policy enforcement and service provisioning. Once
> the packet leaves the IP metro network, the APN attribute will be
> removed/decapsulated together with the IP tunnel header.
>
>
>
> The FBB case is similar to MBB.
>
>
>
> Here RG/BNG (BBF is responsible) and gNB/UPF (3GPP is responsible) are not
> touched.
>
>
>
> Best regards,
>
> Shuping
>
>
>
>
>
>
>
> *From:* ipv6 [mailto:ipv6-bounces@ietf.org] *On Behalf Of *David Allan I
> *Sent:* Wednesday, June 16, 2021 5:14 AM
> *To:* Lizhenbin <lizhenbin@huawei.com>om>; apn@ietf.org; RTGWG <
> rtgwg@ietf.org>
> *Cc:* 6MAN <6man@ietf.org>
> *Subject:* RE: Clarification on the BNG deployment//RE: Application-Aware
> Networking (APN) focused interim
>
>
>
> 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 <ipv6-bounces@ietf.org> *On Behalf Of *Lizhenbin
> *Sent:* Tuesday, June 15, 2021 8:27 AM
> *To:* apn@ietf.org; RTGWG <rtgwg@ietf.org>
> *Cc:* 6MAN <6man@ietf.org>
> *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:apn-bounces@ietf.org <apn-bounces@ietf.org>] *On
> Behalf Of *Pengshuping (Peng Shuping)
> *Sent:* Friday, June 4, 2021 10:53 PM
> *To:* apn@ietf.org
> *Cc:* 6MAN <6man@ietf.org>rg>; RTGWG <rtgwg@ietf.org>
> *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! J
>
>
>
> Best regards,
>
> Shuping j
>
>
>
>
>
>
>
> *From:* ipv6 [mailto:ipv6-bounces@ietf.org <ipv6-bounces@ietf.org>] *On
> Behalf Of *Pengshuping (Peng Shuping)
> *Sent:* Wednesday, June 2, 2021 9:14 AM
> *To:* apn@ietf.org
> *Cc:* 6MAN <6man@ietf.org>rg>; RTGWG <rtgwg@ietf.org>
> *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:apn-bounces@ietf.org <apn-bounces@ietf.org>] *On
> Behalf Of *Pengshuping (Peng Shuping)
> *Sent:* Friday, May 14, 2021 8:55 AM
> *To:* 6MAN <6man@ietf.org>
> *Cc:* apn@ietf.org; Routing Area Working Group <rtgwg-chairs@ietf.org>rg>;
> 6man-chairs@ietf.org
> *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:rtgwg-bounces@ietf.org <rtgwg-bounces@ietf.org>] *On
> Behalf Of *Jeff Tantsura
> *Sent:* Friday, May 7, 2021 6:38 AM
> *To:* Routing WG <rtgwg-chairs@ietf.org>rg>; RTGWG <rtgwg@ietf.org>
> *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##
> <%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 1611493477@ietf.webex.com
>
> You can also dial 173.243.2.68 and enter your meeting number.
>
>
>
>
>
>
>
> *Join using Microsoft Lync or Microsoft Skype for Business*
>
> Dial 1611493477.ietf@lync.webex.com
>
>
>
>
>
>
>
> 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
> rtgwg@ietf.org
> https://www.ietf.org/mailman/listinfo/rtgwg
>