Re: [irs-discuss] IRS comments

Alia Atlas <akatlas@gmail.com> Thu, 30 August 2012 19:10 UTC

Return-Path: <akatlas@gmail.com>
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 80C4821F8598 for <irs-discuss@ietfa.amsl.com>; Thu, 30 Aug 2012 12:10:32 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.961
X-Spam-Level:
X-Spam-Status: No, score=-2.961 tagged_above=-999 required=5 tests=[AWL=-0.362, BAYES_00=-2.599]
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 XXLyvTmD3gSi for <irs-discuss@ietfa.amsl.com>; Thu, 30 Aug 2012 12:10:31 -0700 (PDT)
Received: from mail-ie0-f172.google.com (mail-ie0-f172.google.com [209.85.223.172]) by ietfa.amsl.com (Postfix) with ESMTP id 88B5521F84B5 for <irs-discuss@ietf.org>; Thu, 30 Aug 2012 12:10:31 -0700 (PDT)
Received: by ieak13 with SMTP id k13so1205792iea.31 for <irs-discuss@ietf.org>; Thu, 30 Aug 2012 12:10:31 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=iAEyGPzBqeFedgIIGzoTIRbmTULWyjkq9c416p5BqNY=; b=Mpid8F26IDH4vWUQnBNZu1d+SMuHxBimle9KY3e1g88qhcvcCio1looDGtzJkSKa8U Eg0FKpTgirA3OBXMDJWFyCTh4olQ1cBA+rkKAl/KZSVCbGYCKKv8ICVrNvW/CFCOCmoY 74NVfdAgzC5frU7Sban8Sg0I1+8FTLO2cDLdRe58nAmy3cTylatUPAdFhl2xak8sIULa kWuJmxvT8dMJOY/hPUFwmcSkiOxkMT05hIJlwfG9+YP22ITV0UzG7f3QOgXZIgEzCwwd JrnZkt3dlByNraCj+PVI9TiuJDXJzN9O0dSt5FV8uI6HNkWIo7AO+9GdWR4fN+FqEeQc 0Pyg==
MIME-Version: 1.0
Received: by 10.50.213.106 with SMTP id nr10mr1863778igc.58.1346353831143; Thu, 30 Aug 2012 12:10:31 -0700 (PDT)
Received: by 10.50.91.135 with HTTP; Thu, 30 Aug 2012 12:10:31 -0700 (PDT)
In-Reply-To: <CACKN6JFNHSM=Tu=tPCUe7zWm1g9LRfa6Bv9kvr+uoriVhmLhBQ@mail.gmail.com>
References: <812700A304640D4292205D5E83FC59E1061C211D@p-embx01-eq.jnpr.net> <CAG=JvvjYk_E6+Qdidyyjc5oDss9HeA2aq2pt5ciQeX06fuiWsQ@mail.gmail.com> <CAG4d1reLL2_4KRb6yseJK9WTB47YzumMBGdu+UwcOWXxmE0M8Q@mail.gmail.com> <CAG=JvvjVhGsVcSzEFxDKKfNckQxgQiWeezWvwpcoAOSgOP--Nw@mail.gmail.com> <CAG4d1rd_p6x_+PsHWtsYU=oOCT-GnmnZNL+MHcJf4NEG5boP7A@mail.gmail.com> <B37E6A2CE5957F4E83C1D9845A0FFE38014A33BC4A@MDWEXGMB02.ciena.com> <CAG4d1reWGjUU-z=9Gx_MvetAWF6wM8oUMpQRc9hxOg1MU37X_w@mail.gmail.com> <A3C4E51A53661B4EBEE7C5F5E6FCDEB5025AB94FE6D2@USEXCHANGE.corp.extremenetworks.com> <CAG4d1rfD8_0WgzRqH-OVAxfn1RYNfY_ynwkcmqN3MBYyrn5TnQ@mail.gmail.com> <3512BB31280C39448A9880F61DD54CEB09C07E@xmb-aln-x09.cisco.com> <CAG4d1rcvk1RmRmrpCwiAGx9s0v3X9aPECdeF1Wz7WSuYwzdFKA@mail.gmail.com> <CACKN6JH8eiYty3QOZ+E5Nt0wO3nYn87yB3pKixJK-3dnaOXfLQ@mail.gmail.com> <CACKN6JFMZqOnHU=vEkx8WxwSLjg5MYY=-VoJ7uOt8SAzvbAT6Q@mail.gmail.com> <A3C4E51A53661B4EBEE7C5F5E6FCDEB5025AB94FE847@USEXCHANGE.corp.extremenetworks.com> <B37E6A2CE5957F4E83C1D9845A0FFE38014A33C0A0@MDWEXGMB02.ciena.com> <CAG4d1rehfWk-HX27eysze8zdDzjNk4h4wwj2zV6_WJWxoNxY8Q@mail.gmail.com> <B37E6A2CE5957F4E83C1D9845A0FFE38014A33C26F@MDWEXGMB02.ciena.com> <B17A6910EEDD1F45980687268941550FB7B7B6@MISOUT7MSGUSR9I.ITServices.sbc.com> <B37E6A2CE5957F4E83C1D9845A0FFE38014A33C2BD@MDWEXGMB02.ciena.com> <C584046466ED224CA92C1BC3313B963E09F22C5413@INBANSXCHMBSA3.in.alcatel-lucent.com> <B37E6A2CE5957F4E83C1D9845A0FFE38014A33C554@MDWEXGMB02.ciena.com> <C584046466ED224CA92C1BC3313B963E09F22C55F2@INBANSXCHMBSA3.in.alcatel-lucent.com> <CAG4d1rfEkxAu_XbeVN_76mw+=-Rm45-eveuKMWbeXBTuktrj_w@mail.gmail.com> <CACKN6JFNHSM=Tu=tPCUe7zWm1g9LRfa6Bv9kvr+uoriVhmLhBQ@mail.gmail.com>
Date: Thu, 30 Aug 2012 15:10:31 -0400
Message-ID: <CAG4d1rfTsCo5G92a_hFzUyEaWHH33JeXVTZnmAnd4gi3GavsYw@mail.gmail.com>
From: Alia Atlas <akatlas@gmail.com>
To: Edward Crabbe <edc@google.com>
Content-Type: text/plain; charset="ISO-8859-1"
Cc: "UTTARO, JAMES" <ju1738@att.com>, "Dutta, Pranjal K (Pranjal)" <pranjal.dutta@alcatel-lucent.com>, "Shah, Himanshu" <hshah@ciena.com>, "irs-discuss@ietf.org" <irs-discuss@ietf.org>
Subject: Re: [irs-discuss] IRS comments
X-BeenThere: irs-discuss@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "Interface to The Internet Routing System \(IRS\)" <irs-discuss.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/irs-discuss>, <mailto:irs-discuss-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/irs-discuss>
List-Post: <mailto:irs-discuss@ietf.org>
List-Help: <mailto:irs-discuss-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/irs-discuss>, <mailto:irs-discuss-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 30 Aug 2012 19:10:32 -0000

Ed,

Sure - it provides the ability for centralized route computation -
whether SPF or other.
But that isn't all an IGP does - and the topological information may
still rely on link-state information from an IGP.   It also doesn't
address convergence concerns.

I think there is more to be considered than just whether a central box
can run an SPF and install the associated routes.

Alia


On Thu, Aug 30, 2012 at 2:58 PM, Edward Crabbe <edc@google.com> wrote:
> Alia;
>
> If there is
>
> a) a mechanism for installing routes, pbr or otherwise, which recurse to
> directly connected nexthops
> b) a mechanism for gathering topological information
>
> then you've inherently enabled centralized spf.
>
> On Thu, Aug 16, 2012 at 9:34 AM, Alia Atlas <akatlas@gmail.com> wrote:
>>
>> I haven't seen a good description of what is intended or desired by
>> moving the SPF functionality to a centralized location.  Clearly such
>> centralization can have a very bad impact on convergence - which is a
>> strong motivator for simultaneously computing fast-reroute
>> alternatives (with guaranteed coverage ala MRT) and installing both.
>>
>> I don't see IRS as having a way of "turning off" the SPF computation
>> in the IGP; a different lobotomized IGP protocol/process would be
>> needed.
>>
>> Alia
>>
>> On Thu, Aug 16, 2012 at 12:14 PM, Dutta, Pranjal K (Pranjal)
>> <pranjal.dutta@alcatel-lucent.com> wrote:
>> > "LSDB (I saw an email which talks about reducing IGP to link
>> >> distribution protocol and running SPF in centralized network
>> >> controller)"
>> >
>> > I have seen discussions in the past on this and in fact I didn't get
>> > precisely what is meant. If anybody in the list could brief very
>> > precisely that would help a lot.
>> >
>> > Here is my understanding - the routers would do LSA/LSP flooding for
>> > OSPF/ISIS as it is done today. So routers would build neighboring
>> > relationship/adjacencies to participate in flooding and each router builds
>> > its LSDB.
>> >
>> > Then the IRS "application" would track LSDB changes and pull up the
>> > "diffs" from each router (thru "controller") whenever there is a change. The
>> > application would compute SPF on behalf of each router (LSDB). The result of
>> > the compute would be pushed by application to each Router (thru controller)
>> > and inject entries into RIB.
>> >
>> > Is that correct? How different this going to be from PCE?
>> >
>> > If this is correct then perhaps we would like to ask what are the
>> > scalability numbers in LSDB we are talking about?
>> >
>> > The "application" would be running in a high performance server and so
>> > SPF compute there is not an issue and perhaps it is good way to synchronize
>> > FIB update (to a certain extent) to avoid u-loops etc.
>> >
>> > But when we are managing all routers in the purview of the application,
>> > the computing power in each router is not uniform. To be realistic, I have
>> > some concerns on how much "real-timeness" we could achieve between
>> > application and controllers on such proposals, esp. when scaling numbers are
>> > high. This leads to higher time lag on inconsistency between application SPF
>> > compute and FIB update. It's almost like the classic "slow peering" issues
>> > with TCP like protocols - the high performance peer is slowed down by low
>> > performance peer.
>> >
>> > Static route interface is good thing because it is a state that persists
>> > longer.
>> >
>> > IGPs may be deployed in very dynamic environments where tight coupling
>> > is desirable between SPF compute and FIB update. In scaled environments the
>> > issue is less about SPF compute time and is more about synchronizing the
>> > FIB.
>> >
>> > Running on-demand CSPF by IRS application may be fine because of
>> > persistency of RSVP-TE tunnels in dynamic environments.
>> >
>> > I apologize if I misunderstood the intent.
>> >
>> > Thanks,
>> > Pranjal
>>
>> ---snip---
>> _______________________________________________
>> irs-discuss mailing list
>> irs-discuss@ietf.org
>> https://www.ietf.org/mailman/listinfo/irs-discuss
>
>