FW: New Version Notification for draft-li-apn-problem-statement-usecases-04.txt

Lizhenbin <lizhenbin@huawei.com> Thu, 17 June 2021 03:56 UTC

Return-Path: <lizhenbin@huawei.com>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (localhost []) by ietfa.amsl.com (Postfix) with ESMTP id 677623A194C; Wed, 16 Jun 2021 20:56:44 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.2
X-Spam-Status: No, score=-4.2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, 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] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([]) by localhost (ietfa.amsl.com []) (amavisd-new, port 10024) with ESMTP id l2ZzziBb22HM; Wed, 16 Jun 2021 20:56:39 -0700 (PDT)
Received: from frasgout.his.huawei.com (frasgout.his.huawei.com []) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 04FFC3A1948; Wed, 16 Jun 2021 20:56:39 -0700 (PDT)
Received: from fraeml743-chm.china.huawei.com (unknown []) by frasgout.his.huawei.com (SkyGuard) with ESMTP id 4G57FB1HSnz6K6C9; Thu, 17 Jun 2021 11:43:26 +0800 (CST)
Received: from dggpemm500006.china.huawei.com ( by fraeml743-chm.china.huawei.com ( with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256) id 15.1.2176.2; Thu, 17 Jun 2021 05:56:35 +0200
Received: from dggpemm500008.china.huawei.com ( by dggpemm500006.china.huawei.com ( with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256) id 15.1.2176.2; Thu, 17 Jun 2021 11:56:33 +0800
Received: from dggpemm500008.china.huawei.com ([]) by dggpemm500008.china.huawei.com ([]) with mapi id 15.01.2176.012; Thu, 17 Jun 2021 11:56:33 +0800
From: Lizhenbin <lizhenbin@huawei.com>
To: RTGWG <rtgwg@ietf.org>, "apn@ietf.org" <apn@ietf.org>
CC: 6MAN <6man@ietf.org>
Subject: FW: New Version Notification for draft-li-apn-problem-statement-usecases-04.txt
Thread-Topic: New Version Notification for draft-li-apn-problem-statement-usecases-04.txt
Thread-Index: AQHXYyrNJaq3O2Syf0K+rgXX84LpXasXj1tQ
Date: Thu, 17 Jun 2021 03:56:33 +0000
Message-ID: <4e404724ac714e5996f1a76552ee9640@huawei.com>
References: <162390134763.745.8764059568921585909@ietfa.amsl.com>
In-Reply-To: <162390134763.745.8764059568921585909@ietfa.amsl.com>
Accept-Language: zh-CN, en-US
Content-Language: zh-CN
x-originating-ip: []
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64
MIME-Version: 1.0
X-CFilter-Loop: Reflected
Archived-At: <https://mailarchive.ietf.org/arch/msg/ipv6/zMRXCPW6IRf3eAyVpqIOAxlRGXs>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ipv6/>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ipv6>, <mailto:ipv6-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 17 Jun 2021 03:56:45 -0000

Hi Folks,
According to the feedback, we updates the draft. The updates are as follows:
1. For home broadband scenario, the figure is changed. The RG is connected to AN (access network), then the metro network. 
2. For mobile broadband scenario, since the scope the APN attribute is encapsulated with the GTP-u tunnel is not in IETF, we remove the part. And the figure is also changed. The APN domain is confined to the mobile transport network.

Accordingly the following draft is also updated.

We updated the drafts according to the apparent issues. We will go on to refine the draft. Your comments are always welcome.

Best Regards,

-----Original Message-----
From: internet-drafts@ietf.org [mailto:internet-drafts@ietf.org] 
Sent: Thursday, June 17, 2021 11:42 AM
To: Chongfeng Xie <xiechf@chinatelecom.cn>; Dan Voyer <daniel.voyer@bell.ca>; Daniel Voyer <daniel.voyer@bell.ca>; Gyan Mishra <gyan.s.mishra@verizon.com>; j00406941 <jguichar@futurewei.com>; j00406941 <jguichar@futurewei.com>; Kentaro Ebisawa <ebisawa@toyota-tokyo.tech>; Peng Liu <liupengyjy@chinamobile.com>; Pengshuping (Peng Shuping) <pengshuping@huawei.com>; Stefano Previdi <stefano@previdi.net>; Lizhenbin <lizhenbin@huawei.com>; Zhuangzhuang Qin <qinzhuangzhuang@chinaunicom.cn>
Subject: New Version Notification for draft-li-apn-problem-statement-usecases-04.txt

A new version of I-D, draft-li-apn-problem-statement-usecases-04.txt
has been successfully submitted by Zhenbin Li and posted to the IETF repository.

Name:		draft-li-apn-problem-statement-usecases
Revision:	04
Title:		Problem Statement and Use Cases of Application-aware Networking (APN)
Document date:	2021-06-17
Group:		Individual Submission
Pages:		16
URL:            https://www.ietf.org/archive/id/draft-li-apn-problem-statement-usecases-04.txt
Status:         https://datatracker.ietf.org/doc/draft-li-apn-problem-statement-usecases/
Htmlized:       https://datatracker.ietf.org/doc/html/draft-li-apn-problem-statement-usecases
Diff:           https://www.ietf.org/rfcdiff?url2=draft-li-apn-problem-statement-usecases-04

   Network operators are facing the challenge of providing better
   network services for users.  As the ever-developing 5G and industrial
   verticals evolve, more and more services that have diverse network
   requirements such as ultra-low latency and high reliability are
   emerging, and therefore differentiated service treatment is desired
   by users.  On the other hand, as network technologies such as
   Hierarchical QoS (H-QoS), SR Policy, and Network Slicing keep
   evolving, the network has the capability to provide more fine-
   granularity differentiated services.  However, network operators are
   typically unware of the applications that are traversing their
   network infrastructure, which means that not very effective
   differentiated service treatment can be provided to the traffic
   flows.  As network technologies evolve including deployments of IPv6,
   SRv6, Segment Routing over MPLS dataplane, the programmability
   provided by IPv6 and Segment Routing can be augmented by conveying
   application related information into the network satifying the fine-
   granularity requirements.

   This document analyzes the existing problems caused by lack of
   service awareness, and outlines various use cases that could benefit
   from an Application-aware Networking (APN) framework.


The IETF Secretariat