Re: [bess] 答复: 答复: Flowspec for L2VPN and E-VPN
Robert Raszuk <robert@raszuk.net> Fri, 14 November 2014 08:09 UTC
Return-Path: <rraszuk@gmail.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 212D01A01A5 for <bess@ietfa.amsl.com>; Fri, 14 Nov 2014 00:09:25 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.977
X-Spam-Level:
X-Spam-Status: No, score=-0.977 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, FM_FORGED_GMAIL=0.622, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, MIME_8BIT_HEADER=0.3, SPF_PASS=-0.001] autolearn=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 QEm7y-E2MJ_7 for <bess@ietfa.amsl.com>; Fri, 14 Nov 2014 00:09:23 -0800 (PST)
Received: from mail-ie0-x234.google.com (mail-ie0-x234.google.com [IPv6:2607:f8b0:4001:c03::234]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 165871A0083 for <bess@ietf.org>; Fri, 14 Nov 2014 00:09:23 -0800 (PST)
Received: by mail-ie0-f180.google.com with SMTP id rl12so2048115iec.39 for <bess@ietf.org>; Fri, 14 Nov 2014 00:09:22 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:sender:in-reply-to:references:date:message-id:subject :from:to:cc:content-type; bh=H2zemzstqxyxfcrSL06r316tRy/rAHTXl7Pn7J6mT0I=; b=n1kE8ABfq5OL903aoBhbqrjJZnKIvhpLYebORedUFYcMgMuN9ebyKlt1fUPdqEiPl/ 596nBAIuKruQQFlhPpUtel6kyHP5IY9aFw59yzeWMWXhIvjube/J2lAFMqyJ8tKRocLp cfDWs+E3DF8XRtm9o2RxFNXPHX0DHm27aQHaFQWkPncnnlxaCqAMIsBTW+kphhRYeLYB mKb6JvAU5BMxutE1YaPYAbbEcGsBGXQuqGmYaO78y2uO97/8xrEY3/E2aR4NsaQLE/b2 /YWGxVqcEh+S0kxG+AORECcsNVb8Mo2oZdHUxTUFNVQQ41cNIyCQzpGycByroWUeSNxg /f5w==
MIME-Version: 1.0
X-Received: by 10.50.138.197 with SMTP id qs5mr4285433igb.17.1415952562261; Fri, 14 Nov 2014 00:09:22 -0800 (PST)
Sender: rraszuk@gmail.com
Received: by 10.107.171.149 with HTTP; Fri, 14 Nov 2014 00:09:22 -0800 (PST)
In-Reply-To: <DD5FC8DE455C3348B94340C0AB5517334F810200@nkgeml501-mbs.china.huawei.com>
References: <D08A6D3E.1096C5%wim.henderickx@alcatel-lucent.com> <C07F5057-3D69-423A-98AF-D166E94143D1@cisco.com> <DD5FC8DE455C3348B94340C0AB5517334F810200@nkgeml501-mbs.china.huawei.com>
Date: Fri, 14 Nov 2014 09:09:22 +0100
X-Google-Sender-Auth: GsOTvs9nSnNwYxw5x03PKJL9DMc
Message-ID: <CA+b+ERmGYEf5m7dkCV7z9A=0PWsYo4OQPHaHrKEEL4tb_souNQ@mail.gmail.com>
From: Robert Raszuk <robert@raszuk.net>
To: Haoweiguo <haoweiguo@huawei.com>
Content-Type: multipart/alternative; boundary="089e010d9e327e16c40507cd252e"
Archived-At: http://mailarchive.ietf.org/arch/msg/bess/J9Wj8uLCPH6FRNImYK322G6ApPM
Cc: "Henderickx, Wim (Wim)" <wim.henderickx@alcatel-lucent.com>, Thomas Morin <thomas.morin@orange.com>, IDR Chairs <idr-chairs@tools.ietf.org>, "Bertrand Duvivier (bduvivie)" <bduvivie@cisco.com>, BESS <bess@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 08:09:25 -0000
RT overlap is a configuration issue not a protocol design issue. It is easy to avoid it by proper RT assignment for non congruent services. Cheers, R. On Fri, Nov 14, 2014 at 9:06 AM, Haoweiguo <haoweiguo@huawei.com> wrote: > Hi Bertrand, > What's your solution for RT overlap issue or other possible > issue?Sometimes it is unfortunate that designing beauty needs to be > compromised in reality. > Thanks > weiguo > > ________________________________________ > 发件人: Bertrand Duvivier (bduvivie) [bduvivie@cisco.com] > 发送时间: 2014年11月14日 16:00 > 收件人: Henderickx, Wim (Wim) > 抄送: Haoweiguo; Thomas Morin; BESS; IDR Chairs > 主题: Re: [bess] 答复: Flowspec for L2VPN and E-VPN > > +1... Would to avoid to see multiplication of fs safi. > > Sent from iPAD > > > > On Nov 14, 2014, at 01:15, Henderickx, Wim (Wim) < > wim.henderickx@alcatel-lucent.com> wrote: > > > > 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 > > > > _______________________________________________ > > 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 >
- Re: [bess] 答复: Flowspec for L2VPN and E-VPN Henderickx, Wim (Wim)
- [bess] 答复: 答复: Flowspec for L2VPN and E-VPN Haoweiguo
- Re: [bess] 答复: Flowspec for L2VPN and E-VPN Bertrand Duvivier (bduvivie)
- [bess] 答复: 答复: Flowspec for L2VPN and E-VPN Haoweiguo
- Re: [bess] 答复: 答复: Flowspec for L2VPN and E-VPN Robert Raszuk
- Re: [bess] 答复: Flowspec for L2VPN and E-VPN Haoweiguo
- Re: [bess] 答复: Flowspec for L2VPN and E-VPN Henderickx, Wim (Wim)
- Re: [bess] 答复: Flowspec for L2VPN and E-VPN Dongjie (Jimmy)