Re: [irs-discuss] IRS Problem Statement Posted

James Kempf <james.kempf@ericsson.com> Tue, 31 July 2012 16:11 UTC

Return-Path: <james.kempf@ericsson.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 BDD8721F867F for <irs-discuss@ietfa.amsl.com>; Tue, 31 Jul 2012 09:11:57 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.182
X-Spam-Level:
X-Spam-Status: No, score=-6.182 tagged_above=-999 required=5 tests=[AWL=0.417, BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id cykyghuKSRiu for <irs-discuss@ietfa.amsl.com>; Tue, 31 Jul 2012 09:11:51 -0700 (PDT)
Received: from imr3.ericy.com (imr3.ericy.com [198.24.6.13]) by ietfa.amsl.com (Postfix) with ESMTP id ED47121F869A for <irs-discuss@ietf.org>; Tue, 31 Jul 2012 09:11:50 -0700 (PDT)
Received: from eusaamw0706.eamcs.ericsson.se ([147.117.20.31]) by imr3.ericy.com (8.13.8/8.13.8) with ESMTP id q6VGBJhE022980 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL); Tue, 31 Jul 2012 11:11:47 -0500
Received: from EUSAACMS0703.eamcs.ericsson.se ([169.254.1.135]) by eusaamw0706.eamcs.ericsson.se ([147.117.20.31]) with mapi; Tue, 31 Jul 2012 12:11:38 -0400
From: James Kempf <james.kempf@ericsson.com>
To: Nitin Bahadur <nitinb@juniper.net>, Robert Raszuk <robert@raszuk.net>
Date: Tue, 31 Jul 2012 12:11:37 -0400
Thread-Topic: [irs-discuss] IRS Problem Statement Posted
Thread-Index: Ac1uwSAnSG+rmSQ3S12saISb+HgJ8QAdG2zQ
Message-ID: <CE39F5249064D946AA3535E63A014619656FB98A50@EUSAACMS0703.eamcs.ericsson.se>
References: <CE39F5249064D946AA3535E63A014619656FB98703@EUSAACMS0703.eamcs.ericsson.se> <CC3C59B2.2275E%nitinb@juniper.net> <728F9B956B2C48439CA9294B1723B14623754A18@dfweml509-mbs.china.huawei.com> <EE2E7697-92F1-4E98-A3FE-47CDF28C81C7@juniper.net> <F0ABFF98-0B62-4203-B3BA-EF704AE0FBA7@raszuk.net> <879186E3-D9D7-49B5-8E38-8CC4E4D34282@juniper.net>
In-Reply-To: <879186E3-D9D7-49B5-8E38-8CC4E4D34282@juniper.net>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
acceptlanguage: en-US
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Cc: Thomas Nadeau <tnadeau@juniper.net>, Susan Hares <susan.hares@huawei.com>, "irs-discuss@ietf.org" <irs-discuss@ietf.org>
Subject: Re: [irs-discuss] IRS Problem Statement Posted
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: Tue, 31 Jul 2012 16:11:58 -0000

 
> [ off-topic ]
> 
> Today in IDR, Microsoft folks presented on running data 
> centers using BGP. So I guess we should put OSPF & ISIS to 
> rest. We can use BGP for everything.
> 

Yeah, right. Then when it breaks due to being used for something it wasn't designed, we can spend the next 10 years in IETF working groups coming up with fixes. And have to hire high priced BFG gurus to configure and keep it running in the meantime. :-) 

> [ / off-topic ]
> 
> Openflow abstractions are at the forwarding level. IRS does 
> not compete with that.
> 
> [ rant ]
> Did I just hear that you've convinced your company to replace 
> all of its networking gear with OF gear and a uber powerful 
> controller.
> [ / rant ]

Wollen Sie dann weiter die Unterhaltung auf Deutsch haben?
> 

Anyway, I've been working with OpenFlow on and off since 2006. You can do stuff like:

- make an access/aggregation network with a couple hundred switches look like a gigantic router to the outside world by aggregating the interfaces (and thereby make it easier to manage)

- do application specific flow steering for chained processing in middleboxes (complaints about DPI please to /dev/null)

- run a 3GPP/LTE mobile core with the control plane including routing completely in a cloud instead of only the mobility mangement part

- and finally, as Google has demonstrated, run your network at 90% capacity as opposed to 30% (and, yes, I know that the network was rather special and perhaps not characteristic of a provider network but it still shows what you can do)


But it is not magic, there are lots of problems that need work, and it could still go badly wrong. Right now, it is at the peak of the Gardner hype curve, give it another year, and everybody will be trashing it, unless of course the hype curve moves up another notch.

			jak

> Thanks
> Nitin
> 
> On Jul 30, 2012, at 6:48 PM, "Robert Raszuk" 
> <robert@raszuk.net>; wrote:
> 
> > hi Nitin,
> > 
> > 
> >> So IRS needs to define interfaces for both the lower layer 
> and the upper layer.
> > 
> > That's precisely what openflow protocol does. Thx for 
> confirming clearly the intentions ;).
> > 
> > Best regards,
> > R.
>