Return-Path: X-Original-To: irs-discuss@ietfa.amsl.com Delivered-To: irs-discuss@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 04FFB21F8722 for ; Wed, 10 Oct 2012 08:22:18 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -10.598 X-Spam-Level: X-Spam-Status: No, score=-10.598 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_HI=-8] Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id r7W2h4FI-vwa for ; Wed, 10 Oct 2012 08:22:16 -0700 (PDT) Received: from rcdn-iport-1.cisco.com (rcdn-iport-1.cisco.com [173.37.86.72]) by ietfa.amsl.com (Postfix) with ESMTP id 79A1621F87D2 for ; Wed, 10 Oct 2012 08:22:06 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=6844; q=dns/txt; s=iport; t=1349882526; x=1351092126; h=from:to:subject:date:message-id:mime-version; bh=6LfOVTH4KtmsaOG03hOxjJamHh37PJ7WF9lzzjhyH9E=; b=Ztji+OasGBV4VHCw1vo4A7Xo9+7T7o1HWy8Pdx8IZ0+cQH6LBkgEYRX3 /HJO6Gv04pF/nRYZ8e30Bay15j1g4GGdv9JPzuPEDTp4oNFsn9gjkUS5v 7sQllGCJZvxT+UuOSEn74XpluT8Xvpn7RRfgaiFJzlgH+QdhLqf84hDdz 8=; X-IronPort-Anti-Spam-Filtered: true X-IronPort-Anti-Spam-Result: Av4EABKSdVCtJXG+/2dsb2JhbABEgku8Y4EIgiIBBBIBGl4BKlYmAQQbARmHYguWPYEooCeRB2ADpDGBa4Jtghc X-IronPort-AV: E=Sophos; i="4.80,564,1344211200"; d="scan'208,217"; a="129971367" Received: from rcdn-core2-3.cisco.com ([173.37.113.190]) by rcdn-iport-1.cisco.com with ESMTP; 10 Oct 2012 15:22:05 +0000 Received: from xhc-aln-x13.cisco.com (xhc-aln-x13.cisco.com [173.36.12.87]) by rcdn-core2-3.cisco.com (8.14.5/8.14.5) with ESMTP id q9AFM5PE014086 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL) for ; Wed, 10 Oct 2012 15:22:05 GMT Received: from xmb-rcd-x12.cisco.com ([169.254.2.162]) by xhc-aln-x13.cisco.com ([173.36.12.87]) with mapi id 14.02.0318.001; Wed, 10 Oct 2012 10:22:05 -0500 From: "Kausik Majumdar (kmajumda)" To: "irs-discuss@ietf.org" Thread-Topic: [irs-discuss] central membership computation for mpls VPNs Thread-Index: Ac2m+wCD0x2GxGt7S+q7EuhRKdEMLw== Date: Wed, 10 Oct 2012 15:22:04 +0000 Message-ID: Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: x-originating-ip: [161.44.186.147] x-tm-as-product-ver: SMEX-10.2.0.1135-7.000.1014-19258.000 x-tm-as-result: No--35.566400-8.000000-31 x-tm-as-user-approved-sender: No x-tm-as-user-blocked-sender: No Content-Type: multipart/alternative; boundary="_000_B81B498DA819A64E907482A44E472CE40F517247xmbrcdx12ciscoc_" MIME-Version: 1.0 Subject: [irs-discuss] central membership computation for mpls VPNs X-BeenThere: irs-discuss@ietf.org X-Mailman-Version: 2.1.12 Precedence: list List-Id: "Interface to The Internet Routing System \(IRS\)" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 10 Oct 2012 15:22:18 -0000 --_000_B81B498DA819A64E907482A44E472CE40F517247xmbrcdx12ciscoc_ Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable Hi, I am new in irs alias. I was looking through the draft http://www.ietf.org/= id/draft-white-irs-use-case-00.txt to find out some more details on the cen= tral membership computation for MPLS VPNs as mentioned in the doc - MPLS based VPNs use route target extended communities to express membership information. Every PE router holds incoming BGP NLRI and processes them to determine membership and then import the NLRI into the appropriate MPLS/VPN routing tables. This consumes resources, both memory and compute on each of the PE devices. An alternative approach is to monitor routing updates on every PE from the attached CEs and then compute membership in a central manner. Once computed the routes are pushed to the VPN RIBs of the participating PEs. Are we talking about exporting the route updates from each PEs to a central= server out of hw devices and compute BGP membership centrally and then dow= nloading the selective/optimized routes to the respective PEs ? Can someone= point me some details on how to compute membership in a central manner. Thanks in advance, Kausik --_000_B81B498DA819A64E907482A44E472CE40F517247xmbrcdx12ciscoc_ Content-Type: text/html; charset="us-ascii" Content-Transfer-Encoding: quoted-printable

 

Hi,

 

I am new in irs alias. I was looking through the dra= ft http://www.ietf.org/id/draft-white-irs-use-case-00.txt to find out some= more details on the central membership computation for MPLS VPNs as mentio= ned in the doc –

 

   MPLS based VPNs use route target extended com= munities to express

   membership information.  Every PE router= holds incoming BGP NLRI and

   processes them to determine membership and th= en import the NLRI into

   the appropriate MPLS/VPN routing tables. = ; This consumes resources,

   both memory and compute on each of the PE dev= ices.

 

   An alternative approach is to monitor routing updates on every PE

   from t= he attached CEs and then compute membership in a central<= /p>

   manner= .  Once computed the routes are pushed to the VPN RIBs of the

   partic= ipating PEs.

 

Are we talking about exporting the route updates fro= m each PEs to a central server out of hw devices and compute BGP membership= centrally and then downloading the selective/optimized routes to the respe= ctive PEs ? Can someone point me some details on how to compute membership in a central manner.

 

Thanks in advance,

Kausik  

 

--_000_B81B498DA819A64E907482A44E472CE40F517247xmbrcdx12ciscoc_--