[Idr] 答复: New Version Notification for draft-liang-idr-bgp-flowspec-time-00.txt

Youjianjie <youjianjie@huawei.com> Fri, 23 October 2015 06:27 UTC

Return-Path: <youjianjie@huawei.com>
X-Original-To: idr@ietfa.amsl.com
Delivered-To: idr@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id B91801AD371 for <idr@ietfa.amsl.com>; Thu, 22 Oct 2015 23:27:00 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.911
X-Spam-Level:
X-Spam-Status: No, score=-3.911 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, MIME_8BIT_HEADER=0.3, RCVD_IN_DNSWL_MED=-2.3, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01] autolearn=ham
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 Oy-Bvz_M4krG for <idr@ietfa.amsl.com>; Thu, 22 Oct 2015 23:26:58 -0700 (PDT)
Received: from lhrrgout.huawei.com (lhrrgout.huawei.com [194.213.3.17]) (using TLSv1 with cipher RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 5C82A1AD2EE for <idr@ietf.org>; Thu, 22 Oct 2015 23:26:57 -0700 (PDT)
Received: from 172.18.7.190 (EHLO lhreml401-hub.china.huawei.com) ([172.18.7.190]) by lhrrg01-dlp.huawei.com (MOS 4.3.7-GA FastPath queued) with ESMTP id CCX72496; Fri, 23 Oct 2015 06:26:55 +0000 (GMT)
Received: from NKGEML408-HUB.china.huawei.com (10.98.56.39) by lhreml401-hub.china.huawei.com (10.201.5.240) with Microsoft SMTP Server (TLS) id 14.3.235.1; Fri, 23 Oct 2015 07:26:54 +0100
Received: from NKGEML509-MBS.china.huawei.com ([169.254.2.4]) by nkgeml408-hub.china.huawei.com ([10.98.56.39]) with mapi id 14.03.0235.001; Fri, 23 Oct 2015 14:26:47 +0800
From: Youjianjie <youjianjie@huawei.com>
To: Thomas Mangin <thomas.mangin@exa-networks.co.uk>, "idr@ietf.org" <idr@ietf.org>
Thread-Topic: [Idr] New Version Notification for draft-liang-idr-bgp-flowspec-time-00.txt
Thread-Index: AQHRChGgxqAXHE5ijUa50tGg9c/2Xp5yETIg//+68QCABtTWIA==
Date: Fri, 23 Oct 2015 06:26:47 +0000
Message-ID: <F6C28B32DA084644BB6C8D0BD65B669D1FAB89@nkgeml509-mbs.china.huawei.com>
References: <F6C28B32DA084644BB6C8D0BD65B669D1F8421@nkgeml509-mbs.china.huawei.com> <F50BEEEC-B62C-4E89-BD26-4575BD868334@exa-networks.co.uk>
In-Reply-To: <F50BEEEC-B62C-4E89-BD26-4575BD868334@exa-networks.co.uk>
Accept-Language: zh-CN, en-US
Content-Language: zh-CN
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [10.136.79.106]
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64
MIME-Version: 1.0
X-CFilter-Loop: Reflected
Archived-At: <http://mailarchive.ietf.org/arch/msg/idr/KagtKxAn0cAd9Mo20ZsoNRBbnAE>
Subject: [Idr] 答复: New Version Notification for draft-liang-idr-bgp-flowspec-time-00.txt
X-BeenThere: idr@ietf.org
X-Mailman-Version: 2.1.15
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: Fri, 23 Oct 2015 06:27:00 -0000

Hi Thomas,

Thanks for your comments. 
The "Flow Validity Period" is proposed for the FlowSpec NLRI instead of FlowSpec components (e.g. filters). The filters defined in RFC5575 are used to match the packets; however, the "Flow Validity Period" is an attribute of the FlowSpec rule itself, not acting as a filter, in this document.

Thanks,
Jianjie

> -----邮件原件-----
> 发件人: Idr [mailto:idr-bounces@ietf.org] 代表 Thomas Mangin
> 发送时间: 2015年10月19日 13:59
> 收件人: idr@ietf.org
> 主题: Re: [Idr] New Version Notification for
> draft-liang-idr-bgp-flowspec-time-00.txt
> 
> Hello Jianjie,
> 
> Could you please explain why you choose a TLV vs individual new flow
> components. Naively, I would have thought that it would be easier to create a
> number of new individual tests (start time, duration, delay, ..).
> 
> While I am sympathetic to the idea, many of ExaBGP’s users have asked me to
> introduce a similar feature in the code, I would rather not see yet another TLV
> requiring yes another custom parser to be handled when RFC 5575 has a
> perfectly good generic mechanism to handle tests on flow routes.
> 
> Yours sincerely,
> 
> Thomas Mangin
> 
> http://exa.net.uk/about/contact-us
> On 19 Oct 2015, at 3:08, Youjianjie wrote:
> 
> > Dear all,
> >
> > This document proposes a new BGP path attribute called "Flow Extended
> > Attribute", which carries expected valid period information for a
> > FlowSpec rule.
> > Could you please review? Your comments are welcome.
> >
> > Thanks,
> > Jianjie
> >
> > -----邮件原件-----
> > 发件人: internet-drafts@ietf.org [mailto:internet-drafts@ietf.org]
> > 发送时间: 2015年10月19日 9:58
> > 收件人: Liangqiandeng; Zhuangshunwan; Youjianjie; Zhuangshunwan;
> > Youjianjie; Liangqiandeng
> > 主题: New Version Notification for
> > draft-liang-idr-bgp-flowspec-time-00.txt
> >
> >
> > A new version of I-D, draft-liang-idr-bgp-flowspec-time-00.txt
> > has been successfully submitted by Jianjie You and posted to the IETF
> > repository.
> >
> > Name:		draft-liang-idr-bgp-flowspec-time
> > Revision:	00
> > Title:		BGP FlowSpec with Time Constraints
> > Document date:	2015-10-18
> > Group:		Individual Submission
> > Pages:		9
> > URL:
> > https://www.ietf.org/internet-drafts/draft-liang-idr-bgp-flowspec-time-00.txt
> > Status:
> > https://datatracker.ietf.org/doc/draft-liang-idr-bgp-flowspec-time/
> > Htmlized:
> > https://tools.ietf.org/html/draft-liang-idr-bgp-flowspec-time-00
> >
> >
> > Abstract:
> > The BGP flow specification (FlowSpec) is an additional tool to
> > mitigate the effects of Distributed Denial of Service (DDoS) attacks.
> > Since DDoS attacks are dynamic, filtering of a flow may only be
> > necessary for some specified time, and be undesirable at other times.
> > This document proposes a new BGP path attribute called "Flow Extended
> > Attribute", which carries expected valid period information for a
> > FlowSpec rule.  So network administrators can control certain types of
> > traffic in a specified period.
> >
> >
> >
> >
> >
> > Please note that it may take a couple of minutes from the time of
> > submission until the htmlized version and diff are available at
> > tools.ietf.org.
> >
> > The IETF Secretariat
> >
> > _______________________________________________
> > Idr mailing list
> > Idr@ietf.org
> > https://www.ietf.org/mailman/listinfo/idr
> 
> _______________________________________________
> Idr mailing list
> Idr@ietf.org
> https://www.ietf.org/mailman/listinfo/idr