Re: [irs-discuss] An idea ... MTR + IRS

Thomas Nadeau <> Tue, 07 August 2012 22:22 UTC

Return-Path: <>
Received: from localhost (localhost []) by (Postfix) with ESMTP id 935A621F8598 for <>; Tue, 7 Aug 2012 15:22:52 -0700 (PDT)
X-Virus-Scanned: amavisd-new at
X-Spam-Flag: NO
X-Spam-Score: -6.359
X-Spam-Status: No, score=-6.359 tagged_above=-999 required=5 tests=[AWL=0.240, BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
Received: from ([]) by localhost ( []) (amavisd-new, port 10024) with ESMTP id zbc8M6G6dnGi for <>; Tue, 7 Aug 2012 15:22:52 -0700 (PDT)
Received: from ( []) by (Postfix) with ESMTP id DE72821F858E for <>; Tue, 7 Aug 2012 15:22:51 -0700 (PDT)
Received: from ([]) (using TLSv1) by ([]) with SMTP ID; Tue, 07 Aug 2012 15:22:51 PDT
Received: from ( by ( with Microsoft SMTP Server (TLS) id; Tue, 7 Aug 2012 15:22:30 -0700
Received: from ( by ( with Microsoft SMTP Server (TLS) id 14.1.355.2; Tue, 7 Aug 2012 15:22:29 -0700
Received: from ([fe80::1914:3299:33d9:e43b]) by ([fe80::c126:c633:d2dc:8090%11]) with mapi; Tue, 7 Aug 2012 18:22:28 -0400
From: Thomas Nadeau <>
To: Edward Crabbe <>, "" <>
Date: Tue, 7 Aug 2012 18:22:28 -0400
Thread-Topic: [irs-discuss] An idea ... MTR + IRS
Thread-Index: Ac106yDW0rpjVyedTvSyEf6htA24Hg==
Message-ID: <>
In-Reply-To: <>
Accept-Language: en-US
Content-Language: en-US
user-agent: Microsoft-MacOutlook/
acceptlanguage: en-US
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Cc: "" <>
Subject: Re: [irs-discuss] An idea ... MTR + IRS
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: Tue, 07 Aug 2012 22:22:52 -0000

I agree. The only related thing is that you can run both on the same box, effectively creating another "hybrid" scenario, or as we like to call it, tri-brid. *)


From: Edward Crabbe <<>>
Date: Tuesday, August 7, 2012 6:19 PM
To: "<>" <<>>
Cc: "<>" <<>>
Subject: Re: [irs-discuss] An idea ... MTR + IRS


If topo information export is in scope (which I believe it is) and PBR route injection with nh recursion to rib (and thus connected routes) is in scope (which I'm quite sure it is) then yes, this is in scope.

Although I'm not sure what it has to do with OF /OF controllers? ;P

On Thu, Aug 2, 2012 at 5:02 PM, Robert Raszuk <<>> wrote:

This morning Scott mentioned that he would like to use IRS to shut down all protocols and just be able to write to RIB. Now James said that he would like to get a network topology as "every OpenFlow controller requires this"

Both connected together resulted in an idea of using multi-topology-routing where your base topology discovers physical link connectivity graph while other topologies could be programmed by external entities example: OF controllers or any other external to routers network intelligence oracles to deliver actual services ?

Would that be in scope of IRS effort ? If so what would be the proposed "write to RIB" set of protocols ? Would you support OF 1.3 even if one would be happy to lock such topologies only to software/programmable switching paths ?

Best rgs,
irs-discuss mailing list<>