Re: [Idr] FW: New Version Notification for draft-peng-idr-apn-bgp-flowspec-00.txt

"Pengshuping (Peng Shuping)" <pengshuping@huawei.com> Wed, 13 March 2024 07:56 UTC

Return-Path: <pengshuping@huawei.com>
X-Original-To: idr@ietfa.amsl.com
Delivered-To: idr@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id F2DCAC15792A for <idr@ietfa.amsl.com>; Wed, 13 Mar 2024 00:56:09 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.894
X-Spam-Level:
X-Spam-Status: No, score=-6.894 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_HI=-5, RCVD_IN_MSPIKE_H4=0.001, RCVD_IN_MSPIKE_WL=0.001, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, T_KAM_HTML_FONT_INVALID=0.01, T_SCC_BODY_TEXT_LINE=-0.01, URIBL_DBL_BLOCKED_OPENDNS=0.001, URIBL_ZEN_BLOCKED_OPENDNS=0.001] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([50.223.129.194]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 7SH61xrwYvdQ for <idr@ietfa.amsl.com>; Wed, 13 Mar 2024 00:56:06 -0700 (PDT)
Received: from frasgout.his.huawei.com (frasgout.his.huawei.com [185.176.79.56]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id A5F94C157915 for <idr@ietf.org>; Wed, 13 Mar 2024 00:56:05 -0700 (PDT)
Received: from mail.maildlp.com (unknown [172.18.186.31]) by frasgout.his.huawei.com (SkyGuard) with ESMTP id 4TvjVk11RNz6JB51 for <idr@ietf.org>; Wed, 13 Mar 2024 15:55:42 +0800 (CST)
Received: from lhrpeml100005.china.huawei.com (unknown [7.191.160.25]) by mail.maildlp.com (Postfix) with ESMTPS id 34009140D27 for <idr@ietf.org>; Wed, 13 Mar 2024 15:55:42 +0800 (CST)
Received: from canpemm100006.china.huawei.com (7.192.104.17) by lhrpeml100005.china.huawei.com (7.191.160.25) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.1.2507.35; Wed, 13 Mar 2024 07:55:35 +0000
Received: from canpemm500008.china.huawei.com (7.192.105.151) by canpemm100006.china.huawei.com (7.192.104.17) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.1.2507.35; Wed, 13 Mar 2024 15:55:33 +0800
Received: from canpemm500008.china.huawei.com ([7.192.105.151]) by canpemm500008.china.huawei.com ([7.192.105.151]) with mapi id 15.01.2507.035; Wed, 13 Mar 2024 15:55:33 +0800
From: "Pengshuping (Peng Shuping)" <pengshuping@huawei.com>
To: Chongfeng Xie <chongfeng.xie@foxmail.com>, idr <idr@ietf.org>
Thread-Topic: [Idr] FW: New Version Notification for draft-peng-idr-apn-bgp-flowspec-00.txt
Thread-Index: AQHabiVwLKwyLY1kAkS8+sC2v2vfqrEor1tQgAyXraeAAACfYA==
Date: Wed, 13 Mar 2024 07:55:33 +0000
Message-ID: <07eac8c019914ccd93f79c4cfe9f0375@huawei.com>
References: <170955098589.63313.5702540179844656474@ietfa.amsl.com>, <4ce76a775dba4cdebb6ca0fd7dcdcd2d@huawei.com> <tencent_A9CDF062F52BB50B57F21DAE93019D398C09@qq.com>
In-Reply-To: <tencent_A9CDF062F52BB50B57F21DAE93019D398C09@qq.com>
Accept-Language: zh-CN, en-US
Content-Language: zh-CN
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [10.153.179.165]
Content-Type: multipart/alternative; boundary="_000_07eac8c019914ccd93f79c4cfe9f0375huaweicom_"
MIME-Version: 1.0
Archived-At: <https://mailarchive.ietf.org/arch/msg/idr/hXIogUBW9fiELz3my_SmrxoSOMU>
Subject: Re: [Idr] FW: New Version Notification for draft-peng-idr-apn-bgp-flowspec-00.txt
X-BeenThere: idr@ietf.org
X-Mailman-Version: 2.1.39
Precedence: list
List-Id: Inter-Domain Routing <idr.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/idr>, <mailto:idr-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/idr/>
List-Post: <mailto:idr@ietf.org>
List-Help: <mailto:idr-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/idr>, <mailto:idr-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 13 Mar 2024 07:56:10 -0000

Hi Chongfeng,

Thank you for this suggestion.

There are a few use cases we targeted in this draft. Their requirements are also mentioned below.

1)     To perform policy enforcement at nodes based on APN ID.

At a policy enforcement node, the APN ID carried in the incoming data packets is used to match against the APN ID carried in the BGP FS Component, if it is a successful match, the corresponding policy at this node will be enforced, e.g. traffic steering into a specific tunnel. – This use case explains why we need to define this new component type for APN.

2)     To create an APN ID based on the APN FS rules at the APN domain edge when there are also co-existing FS rules. The different parts of the APN ID might be created by different FS rules. -- This explains why we needs to define the ordering of the multiple coexisting FS rules to organize them in an effective order. We categorize the rules into Groups, and then within each Group, we further categorize the rules into Sub-Groups. We have also defined the usage principles for the rules within a Sub-Group, between Sub-Groups, and between Groups.

3)     To obtain the APN ID from the incoming data packets or from the FS and encapsulate it in the outer tunnel header such as IPv6 extension header – This explains why we need to define the Traffic Filtering Actions. There are four ways to obtain the APN ID.

Best Regards,
Shuping


From: Chongfeng Xie <chongfeng.xie@foxmail.com>
Sent: Wednesday, March 13, 2024 2:42 PM
To: idr <idr@ietf.org>; Pengshuping (Peng Shuping) <pengshuping@huawei.com>
Subject: Re: [Idr] FW: New Version Notification for draft-peng-idr-apn-bgp-flowspec-00.txt

Hi Shuping,

Would you show a general use case of dissemination of BGP Flow Specification Rules for APN?  Personally I think this will conducive to understanding the new approach and promoting it in the future.

Best regards

Chongfeng


From: Pengshuping \(Peng Shuping\)<mailto:pengshuping=40huawei.com@dmarc.ietf.org>
Date: 2024-03-05 15:06
To: idr@ietf.org<mailto:idr@ietf.org>
Subject: [Idr] FW: New Version Notification for draft-peng-idr-apn-bgp-flowspec-00.txt

Hi all,



We have published this draft on the dissemination of BGP Flow Specification Rules for APN (https://datatracker.ietf.org/doc/html/draft-peng-idr-apn-bgp-flowspec), to enable the traffic filtering in an APN domain as well as the traffic control and actions at the policy enforcement points in this domain.



The technical points of this draft include:

1. A new BGP Flow Spec Component Type is specified with the match field APN ID to support the traffic filtering using APN.
2. A Grouping Identifier Opaque Extend Community [RFC4360] (Sub-Type = TBD2) carrying both Group ID (2 octets) and Sub-group ID (2 octets) is defined, aiming to provide an efficient grouping mechanism for the multiple co-existing Flow Specification rules to be matched in a desired order as well as the actions being applied to a particular traffic flow. The encoding format, usage principles and usage example (APN) are provided.
3. Traffic filtering actions (incl. Traffic Marking, Inherit, Stitch) are specified to enable the creation of the APN ID in the outer tunnel encapsulation when matched to the corresponding Flow Spec rules.

Your review and comments are appreciated. Thank you!



Best Regards,

Shuping







-----Original Message-----
From: internet-drafts@ietf.org<mailto:internet-drafts@ietf.org> <internet-drafts@ietf.org<mailto:internet-drafts@ietf.org>>
Sent: Monday, March 4, 2024 7:16 PM
To: Huiyue Zhang <zhanghy30@chinatelecom.cn<mailto:zhanghy30@chinatelecom.cn>>; Ran Pang <pangran@chinaunicom.cn<mailto:pangran@chinaunicom.cn>>; Pengshuping (Peng Shuping) <pengshuping@huawei.com<mailto:pengshuping@huawei.com>>; Yong Cui <cuiyong@tsinghua.edu.cn<mailto:cuiyong@tsinghua.edu.cn>>; Lizhenbin <lizhenbin@huawei.com<mailto:lizhenbin@huawei.com>>
Subject: New Version Notification for draft-peng-idr-apn-bgp-flowspec-00.txt



A new version of Internet-Draft draft-peng-idr-apn-bgp-flowspec-00.txt has been successfully submitted by Shuping Peng and posted to the IETF repository.



Name:     draft-peng-idr-apn-bgp-flowspec

Revision: 00

Title:    Dissemination of BGP Flow Specification Rules for APN

Date:     2024-03-04

Group:    Individual Submission

Pages:    19

URL:      https://www.ietf.org/archive/id/draft-peng-idr-apn-bgp-flowspec-00.txt

Status:   https://datatracker.ietf.org/doc/draft-peng-idr-apn-bgp-flowspec/

HTMLized: https://datatracker.ietf.org/doc/html/draft-peng-idr-apn-bgp-flowspec





Abstract:



   A BGP Flow Specification is an n-tuple consisting of several matching

   criteria that can be applied to IP traffic.  Application-aware

   Networking (APN) is a framework, where APN data packets convey APN

   attribute including APN ID and/or APN Parameters.  The dynamic Flow

   Spec mechanism for APN is designed for the new applications of

   traffic filtering in an APN domain as well as the traffic control and

   actions at the policy enforcement points in this domain.  These

   applications require coordination among the ASes within a service

   provider.



   This document specifies a new BGP Flow Spec Component Type in order

   to support APN traffic filtering.  The match field is the APN ID.  It

   also specifies traffic filtering actions to enable the creation of

   the APN ID in the outer tunnel encapsulation when matched to the

   corresponding Flow Spec rules.







The IETF Secretariat