[Idr] FW: New Version Notification for draft-peng-idr-apn-bgp-flowspec-00.txt
"Pengshuping (Peng Shuping)" <pengshuping@huawei.com> Tue, 05 March 2024 07:06 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 5AE73C14F6B5 for <idr@ietfa.amsl.com>; Mon, 4 Mar 2024 23:06:51 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.194
X-Spam-Level:
X-Spam-Status: No, score=-4.194 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_MED=-2.3, 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 YHQ45-svA8di for <idr@ietfa.amsl.com>; Mon, 4 Mar 2024 23:06:50 -0800 (PST)
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 D6D72C14F61C for <idr@ietf.org>; Mon, 4 Mar 2024 23:06:49 -0800 (PST)
Received: from mail.maildlp.com (unknown [172.18.186.231]) by frasgout.his.huawei.com (SkyGuard) with ESMTP id 4TpmhX4PHwz6J6bM for <idr@ietf.org>; Tue, 5 Mar 2024 15:02:04 +0800 (CST)
Received: from lhrpeml500006.china.huawei.com (unknown [7.191.161.198]) by mail.maildlp.com (Postfix) with ESMTPS id 467DF140D26 for <idr@ietf.org>; Tue, 5 Mar 2024 15:06:47 +0800 (CST)
Received: from canpemm500008.china.huawei.com (7.192.105.151) by lhrpeml500006.china.huawei.com (7.191.161.198) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.1.2507.35; Tue, 5 Mar 2024 07:06:46 +0000
Received: from canpemm500008.china.huawei.com (7.192.105.151) by canpemm500008.china.huawei.com (7.192.105.151) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.1.2507.35; Tue, 5 Mar 2024 15:06:44 +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; Tue, 5 Mar 2024 15:06:44 +0800
From: "Pengshuping (Peng Shuping)" <pengshuping@huawei.com>
To: "idr@ietf.org" <idr@ietf.org>
Thread-Topic: New Version Notification for draft-peng-idr-apn-bgp-flowspec-00.txt
Thread-Index: AQHabiVwLKwyLY1kAkS8+sC2v2vfqrEor1tQ
Date: Tue, 05 Mar 2024 07:06:44 +0000
Message-ID: <4ce76a775dba4cdebb6ca0fd7dcdcd2d@huawei.com>
References: <170955098589.63313.5702540179844656474@ietfa.amsl.com>
In-Reply-To: <170955098589.63313.5702540179844656474@ietfa.amsl.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_4ce76a775dba4cdebb6ca0fd7dcdcd2dhuaweicom_"
MIME-Version: 1.0
Archived-At: <https://mailarchive.ietf.org/arch/msg/idr/ifMy8GrATRCq-gVXwBFVPjl3_JY>
Subject: [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: Tue, 05 Mar 2024 07:06:51 -0000
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 <internet-drafts@ietf.org> Sent: Monday, March 4, 2024 7:16 PM To: Huiyue Zhang <zhanghy30@chinatelecom.cn>; Ran Pang <pangran@chinaunicom.cn>; Pengshuping (Peng Shuping) <pengshuping@huawei.com>; Yong Cui <cuiyong@tsinghua.edu.cn>; Lizhenbin <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
- [Idr] FW: New Version Notification for draft-peng… Pengshuping (Peng Shuping)
- Re: [Idr] FW: New Version Notification for draft-… Chongfeng Xie
- Re: [Idr] FW: New Version Notification for draft-… Pengshuping (Peng Shuping)
- Re: [Idr] New Version Notification for draft-peng… Zhuangshunwan
- Re: [Idr] New Version Notification for draft-peng… Pengshuping (Peng Shuping)