IETF Logo Mail Archive

Re: [bess] 答复: 答复: Flowspec for L2VPN and E-VPN

"Henderickx, Wim (Wim)" <wim.henderickx@alcatel-lucent.com> Fri, 14 November 2014 00:28 UTC

Return-Path: <wim.henderickx@alcatel-lucent.com>
X-Original-To: bess@ietfa.amsl.com
Delivered-To: bess@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 738261A014F for <bess@ietfa.amsl.com>; Thu, 13 Nov 2014 16:28:00 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -7.194
X-Spam-Level:
X-Spam-Status: No, score=-7.194 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, MIME_8BIT_HEADER=0.3, RCVD_IN_DNSWL_HI=-5, RP_MATCHES_RCVD=-0.594] 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 b9GxA9Vsb5kZ for <bess@ietfa.amsl.com>; Thu, 13 Nov 2014 16:27:58 -0800 (PST)
Received: from smtp-fr.alcatel-lucent.com (fr-hpgre-esg-01.alcatel-lucent.com [135.245.210.22]) (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 8F5721A007E for <bess@ietf.org>; Thu, 13 Nov 2014 16:27:58 -0800 (PST)
Received: from fr711usmtp1.zeu.alcatel-lucent.com (unknown [135.239.2.122]) by Websense Email Security Gateway with ESMTPS id 34A88512403D1; Fri, 14 Nov 2014 00:27:53 +0000 (GMT)
Received: from FR711WXCHHUB01.zeu.alcatel-lucent.com (fr711wxchhub01.zeu.alcatel-lucent.com [135.239.2.111]) by fr711usmtp1.zeu.alcatel-lucent.com (GMO) with ESMTP id sAE0Ru47032250 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL); Fri, 14 Nov 2014 01:27:56 +0100
Received: from FR711WXCHMBA07.zeu.alcatel-lucent.com ([169.254.3.219]) by FR711WXCHHUB01.zeu.alcatel-lucent.com ([135.239.2.111]) with mapi id 14.03.0195.001; Fri, 14 Nov 2014 01:27:56 +0100
From: "Henderickx, Wim (Wim)" <wim.henderickx@alcatel-lucent.com>
To: Haoweiguo <haoweiguo@huawei.com>, Thomas Morin <thomas.morin@orange.com>, BESS <bess@ietf.org>
Thread-Topic: 答复: 答复: [bess] Flowspec for L2VPN and E-VPN
Thread-Index: AQHP/6HVZEVjWN2WUEGu6SH1HvGpzg==
Date: Fri, 14 Nov 2014 00:27:55 +0000
Message-ID: <D08A6F8F.1096E8%wim.henderickx@alcatel-lucent.com>
Accept-Language: nl-BE, en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
user-agent: Microsoft-MacOutlook/14.4.5.141003
x-originating-ip: [135.239.27.40]
Content-Type: text/plain; charset="utf-8"
Content-ID: <0D1E392DE50BDF4BB1B083F1BCE38861@exchange.lucent.com>
Content-Transfer-Encoding: base64
MIME-Version: 1.0
Archived-At: http://mailarchive.ietf.org/arch/msg/bess/hJuKOrpLWhaDo3_oQLZ2vWp7xKM
Cc: IDR Chairs <idr-chairs@tools.ietf.org>
Subject: Re: [bess] 答复: 答复: Flowspec for L2VPN and E-VPN
X-BeenThere: bess@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: BGP-Enabled ServiceS working group discussion list <bess.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/bess>, <mailto:bess-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/bess/>
List-Post: <mailto:bess@ietf.org>
List-Help: <mailto:bess-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/bess>, <mailto:bess-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 14 Nov 2014 00:28:00 -0000

We define a new AFI/SAFI that accommodates all we have + include L2
extensions.
Operators that don’t need L2 extensions keep what they have.
Operators that need L2 extensions go to the new method or mix the new
method with the old methods per service type.

Make sense?

On 13/11/14 14:16, "Haoweiguo" <haoweiguo@huawei.com> wrote:

>How to achieve compatability with current existed flowspec[RFC5575]
>applications? 
>Thanks
>weiguo
>
>________________________________________
>发件人: Henderickx, Wim (Wim) [wim.henderickx@alcatel-lucent.com]
>发送时间: 2014年11月14日 8:14
>收件人: Haoweiguo; Thomas Morin; BESS
>抄送: IDR Chairs
>主题: Re: 答复: [bess] Flowspec for L2VPN and E-VPN
>
>If we define a new things I prefer to address the wider issue and include
>L2 in that.
>
>On 13/11/14 14:13, "Haoweiguo" <haoweiguo@huawei.com> wrote:
>
>>Hi Wim,
>>Allocating different AFI/SAFI(s) for each flow spec application is a
>>applicable solution. Theoretically, unified mechanism for all flowspec
>>can be designed, but it maybe a more harder work in IDR.
>>Thanks
>>weiguo
>>
>>________________________________________
>>发件人: BESS [bess-bounces@ietf.org] 代表 Henderickx, Wim (Wim)
>>[wim.henderickx@alcatel-lucent.com]
>>发送时间: 2014年11月14日 7:55
>>收件人: Thomas Morin; BESS
>>抄送: IDR Chairs
>>主题: Re: [bess] Flowspec for L2VPN and E-VPN
>>
>>As I stated in the IDR meeting my observation is that we require to many
>>AFI/SAFI(s) for all flow spec functions. Flow spec in general is
>>providing
>>match criteria¹s with related actions. Given the proposal on Flowspec for
>>L2 is new we should look at the bigger picture.
>>In My view we need a mechanism in BGP to advertise Flowspec match
>>criteria¹s with related actions and they should cover L2/L3-IPv4/IPv6.
>>
>>On 13/11/14 13:44, "Thomas Morin" <thomas.morin@orange.com> wrote:
>>
>>>Hi WG,
>>>
>>>A heads up...
>>>
>>>These two drafts relate to BESS and thus may be of interest to us:
>>>- draft-hao-idr-flowspec-l2vpn
>>><http://tools.ietf.org/html?draft=draft-hao-idr-flowspec-l2vpn-01> (on
>>>idr agenda, being presented right now)
>>>- draft-hao-idr-flowspec-evpn
>>><https://tools.ietf.org/html/draft-hao-idr-flowspec-evpn-00>
>>>
>>>Best,
>>>
>>>-Thomas
>>>
>>>
>>>_______________________________________________
>>>BESS mailing list
>>>BESS@ietf.org
>>>https://www.ietf.org/mailman/listinfo/bess
>>
>>_______________________________________________
>>BESS mailing list
>>BESS@ietf.org
>>https://www.ietf.org/mailman/listinfo/bess

v2.46.0 | Report a Bug | By Email | System Status