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

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

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, 02 Apr 2020 03:23:55 +0000
Message-ID: <1520992FC97B944A9979C2FC1D7DB0F404DF08CC@dggeml524-mbx.china.huawei.com>
Accept-Language: en-US
Content-Language: zh-CN
Content-Type: multipart/alternative; boundary="_000_1520992FC97B944A9979C2FC1D7DB0F404DF08CCdggeml524mbxchi_"
MIME-Version: 1.0
Archived-At: <https://mailarchive.ietf.org/arch/msg/idr/FlXPwQ24M1MVvH5B6MznZz0xO-c>
Subject: [Idr] [IDR] draft-liu-idr-flowspec-ifit-04
Precedence: list

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

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