[Idr] [IDR] draft-liu-idr-flowspec-ifit-04

wangyali <wangyali11@huawei.com> Thu, 02 April 2020 03:24 UTC

Return-Path: <wangyali11@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 12D083A0870 for <idr@ietfa.amsl.com>; Wed, 1 Apr 2020 20:24:03 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.9
X-Spam-Level:
X-Spam-Status: No, score=-1.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
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 Z2ZkdXR8UmF8 for <idr@ietfa.amsl.com>; Wed, 1 Apr 2020 20:24:01 -0700 (PDT)
Received: from huawei.com (lhrrgout.huawei.com [185.176.76.210]) (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 6437F3A086B for <idr@ietf.org>; Wed, 1 Apr 2020 20:24:01 -0700 (PDT)
Received: from lhreml714-chm.china.huawei.com (unknown [172.18.7.107]) by Forcepoint Email with ESMTP id 27625B830A1EEC98423E for <idr@ietf.org>; Thu, 2 Apr 2020 04:24:00 +0100 (IST)
Received: from lhreml714-chm.china.huawei.com (10.201.108.65) by lhreml714-chm.china.huawei.com (10.201.108.65) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256) id 15.1.1713.5; Thu, 2 Apr 2020 04:23:59 +0100
Received: from DGGEML424-HUB.china.huawei.com (10.1.199.41) by lhreml714-chm.china.huawei.com (10.201.108.65) with Microsoft SMTP Server (version=TLS1_0, cipher=TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA) id 15.1.1713.5 via Frontend Transport; Thu, 2 Apr 2020 04:23:59 +0100
Received: from DGGEML524-MBX.china.huawei.com ([169.254.1.149]) by dggeml424-hub.china.huawei.com ([10.1.199.41]) with mapi id 14.03.0487.000; Thu, 2 Apr 2020 11:23:55 +0800
From: wangyali <wangyali11@huawei.com>
To: "Acee Lindem (acee)" <acee@cisco.com>, "idr@ietf.org" <idr@ietf.org>
Thread-Topic: [IDR] draft-liu-idr-flowspec-ifit-04
Thread-Index: AdYInbV/0wjgMW/CRm2a6SsEu58ISw==
Date: Thu, 2 Apr 2020 03:23:55 +0000
Message-ID: <1520992FC97B944A9979C2FC1D7DB0F404DF08CC@dggeml524-mbx.china.huawei.com>
Accept-Language: en-US
Content-Language: zh-CN
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [10.108.203.62]
Content-Type: multipart/alternative; boundary="_000_1520992FC97B944A9979C2FC1D7DB0F404DF08CCdggeml524mbxchi_"
MIME-Version: 1.0
X-CFilter-Loop: Reflected
Archived-At: <https://mailarchive.ietf.org/arch/msg/idr/FlXPwQ24M1MVvH5B6MznZz0xO-c>
Subject: [Idr] [IDR] draft-liu-idr-flowspec-ifit-04
X-BeenThere: idr@ietf.org
X-Mailman-Version: 2.1.29
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: Thu, 02 Apr 2020 03:24:03 -0000

Hi Acee,

This is Yali. Thanks for your question on IDR Interim Meeting. Please find my reply as follows.

>>Acee: I sorta see the community (to turn on/off).
 Why do you want this in the flow specification. I think you just need a tag in the packet for IOAM.
 Are you trying to prevent attacks that are coming in via OAM?
YW: One use case is SLA assurance of game or video service for VIP users. So that we can enable specific IFIT option types to these packets of target flow that match the game or video flow specifications (e.g. source and destination address, port number, DSCP). Thus desired telemetry data (e.g. packet loss and delay) can be exported to determine if there is QoS degradation.

So taking advantages of the automatic distribution of traffic policies supported by BGP Flowspec mechanism, and the encoding formats in extended community used to propagate actions , this draft defines the IFIT Action specific extended community to instruct adding a specific IFIT-Option-Types into packets of flows that match the Flow Specifications as well as updating relevant IFIT-Data-Field in packets automatically.

Best regards,
Yali