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

Chongfeng Xie <chongfeng.xie@foxmail.com> Wed, 13 March 2024 06:42 UTC

Return-Path: <chongfeng.xie@foxmail.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 B73F1C14F6E9 for <idr@ietfa.amsl.com>; Tue, 12 Mar 2024 23:42:36 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.84
X-Spam-Level:
X-Spam-Status: No, score=0.84 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, HELO_DYNAMIC_IPADDR=1.951, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, RCVD_IN_MSPIKE_H4=0.001, RCVD_IN_MSPIKE_WL=0.001, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, RDNS_DYNAMIC=0.982, 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=no autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=foxmail.com
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 zEKsV_pmW6SJ for <idr@ietfa.amsl.com>; Tue, 12 Mar 2024 23:42:32 -0700 (PDT)
Received: from out203-205-221-236.mail.qq.com (out203-205-221-236.mail.qq.com [203.205.221.236]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 8420DC14F5F8 for <idr@ietf.org>; Tue, 12 Mar 2024 23:42:31 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=foxmail.com; s=s201512; t=1710312148; bh=TT3m0htSkU7I+igtYk2eyFVEsjN6JG1XwdIGq1zTPNQ=; h=Date:From:To:Subject:References; b=bvgETuaVkw+wk9l2UWtylo9P+sgiJmqLUSgesxg3T761UemwhEBzqVTfZYC94VVv2 O+OrE8QRcYUqnnYvrDfqXMC8DM6voLuYw7Tc1rmJwDat/FVSC68AJgsf55fnW8k5P9 hjE8hWVs9/XQX+WkcDCQqe4J933yC1i1xbcIvnLU=
Received: from DESKTOP-48H476U ([219.142.69.75]) by newxmesmtplogicsvrszb6-0.qq.com (NewEsmtp) with SMTP id A9AA8885; Wed, 13 Mar 2024 14:42:26 +0800
X-QQ-mid: xmsmtpt1710312146tb4jy6idf
Message-ID: <tencent_A9CDF062F52BB50B57F21DAE93019D398C09@qq.com>
X-QQ-XMAILINFO: OQhZ3T0tjf0aL3SvKp8arEf+PfVe+141iZkb/TR3FW7mYuNrBdLICGOlIdx8SZ 7lluzdBdlaiUKQBKoASX9xY3UuIY0/7oxJFy3mE29lUF70S1KKd/8U0nlZs15+PsMQ0ahvrdaqyZ mDdwmIZNXG0xDZnwMlrlEZc/Ry/uspz4ybf6UA1qWYTX6EbjD+RCM5bLMKo6KXtEjcEjlWr8q30J DsnMBs6e9KBRxC1Wy26p3biwy/PdiL6i8TFRCHBCKnuQNuuF7zrb9BLv6ZbZUB9pPnmJhxwIBvvm BdtuBGu1SmGpSXQ0E/xSnxW3n+V7b8tXUgB7eDmPYG3o/+7Dd5hG6LVa7/wDfKwjuGe8zfpfYgOb A0txI6JtL9ncO1T0ga6SuNXJVO3p3SvNck2NCUm0SRVYvtbKfselBGJU4ToIz8sdsm+2PiOkEkdS fvDketqaYz8A8wxGvrHlFd/yh9W/9Ey+r+KmVYoujKqh0M6/abiVMuM0oNpEZ3Zq3N72VBJMriQZ L0a1Ix2WuI+GZwEKNxEGxlsSnMEJUzO0RqrrXPW9Ek3rO7ueLiJaYLt50q54/o1PcLDCDOVTd0JJ 5xSeb6wl6pu99LThCCQ4MX66Mjy/AfHZZBvwliitLDBgunG/0Q5Dto8UtKBZu7XPu8DsDFWQsa8A GzggWdnQZsZhC6tAWpcF3R+uo3NktIOxNIjCMUuNKCgdjIzJSsbeBnpi5obieJcOCHWqkJ4B4N1q gd00NZO3YDrKP244M/nobuaXG7r2aLje8RXt2ThM8/Ns0y4T8WHRwd/Gq/2P+kZcb3jrZFu12lBv iUnfGCjlvyF2iJOv6Y2V5OAW1FPhyxoip+7ZVMiBDCcu2xNgPsLyAkawQ9WzJbnsbJ/HWMdNAEET i1gmoLtaKEprY1xTow0Ne9uhL1APlqhkzZJpmy3QIWXbCNN9JqyoqAGNPUgjMibL+YCKR5BwtGQa ap1odtkVTB4ib7PKGwqsO6KrUKMfKUPgJ37Eiou9aGAZ+Y/g0BSw6Jq90IZNNW
X-QQ-XMRINFO: NyFYKkN4Ny6FSmKK/uo/jdU=
Date: Wed, 13 Mar 2024 14:42:27 +0800
From: Chongfeng Xie <chongfeng.xie@foxmail.com>
To: idr <idr@ietf.org>, pengshuping <pengshuping@huawei.com>
References: <170955098589.63313.5702540179844656474@ietfa.amsl.com>, <4ce76a775dba4cdebb6ca0fd7dcdcd2d@huawei.com>
X-Priority: 3
X-GUID: F4F939BF-A6B6-4F7B-8D39-9193C36A2798
X-Has-Attach: no
X-Mailer: Foxmail 7.2.25.243[cn]
Mime-Version: 1.0
X-OQ-MSGID: <202403131442270425558@foxmail.com>
Content-Type: multipart/alternative; boundary="----=_001_NextPart060476407053_=----"
Archived-At: <https://mailarchive.ietf.org/arch/msg/idr/DXpqlYeGeYQNDfKetnw5r_c0v0I>
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 06:42:36 -0000

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\)
Date: 2024-03-05 15:06
To: 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 <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