From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from smtp65.iad3a.emailsrvr.com (smtp65.iad3a.emailsrvr.com [173.203.187.65]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client did not present a certificate) by huchra.bufferbloat.net (Postfix) with ESMTPS id 0047621F2E2 for ; Mon, 26 Jan 2015 16:14:05 -0800 (PST) Received: from smtp1.relay.iad3a.emailsrvr.com (localhost.localdomain [127.0.0.1]) by smtp1.relay.iad3a.emailsrvr.com (SMTP Server) with ESMTP id 90DFA180180; Mon, 26 Jan 2015 19:14:04 -0500 (EST) Received: from app36.wa-webapps.iad3a (relay-webapps.rsapps.net [172.27.255.140]) by smtp1.relay.iad3a.emailsrvr.com (SMTP Server) with ESMTP id 7632B180253; Mon, 26 Jan 2015 19:14:04 -0500 (EST) X-Sender-Id: dpreed@reed.com Received: from app36.wa-webapps.iad3a (relay-webapps.rsapps.net [172.27.255.140]) by 0.0.0.0:25 (trex/5.4.2); Tue, 27 Jan 2015 00:14:04 GMT Received: from reed.com (localhost.localdomain [127.0.0.1]) by app36.wa-webapps.iad3a (Postfix) with ESMTP id 6075E38008A; Mon, 26 Jan 2015 19:14:04 -0500 (EST) Received: by apps.rackspace.com (Authenticated sender: dpreed@reed.com, from: dpreed@reed.com) with HTTP; Mon, 26 Jan 2015 19:14:04 -0500 (EST) Date: Mon, 26 Jan 2015 19:14:04 -0500 (EST) From: dpreed@reed.com To: "David Lang" MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----=_20150126191404000000_63161" Importance: Normal X-Priority: 3 (Normal) X-Type: html In-Reply-To: References: <54B5D28A.3010906@gmail.com> <7B1EA8F0-FCB6-4A37-950F-2558FC751DE8@gmail.com> <54C038D0.1000305@gmail.com> <54C0BD22.3000608@gmail.com> <54C13F47.1010203@gmail.com> <1422111577.328132080@apps.rackspace.com> <1422217048.025611275@apps.rackspace.com> <1422237076.005718796@apps.rackspace.com> <11462.1422246794@turing-police.cc.vt.edu> X-Auth-ID: dpreed@reed.com Message-ID: <1422317644.389812775@apps.rackspace.com> X-Mailer: webmail/11.3.10-RC Cc: "cerowrt-devel@lists.bufferbloat.net" Subject: Re: [Cerowrt-devel] =?utf-8?q?Recording_RF_management_info_=5Fand=5F_?= =?utf-8?q?associated_traffic=3F?= X-BeenThere: cerowrt-devel@lists.bufferbloat.net X-Mailman-Version: 2.1.13 Precedence: list List-Id: Development issues regarding the cerowrt test router project List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 27 Jan 2015 00:14:34 -0000 ------=_20150126191404000000_63161 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable =0AAnd having every /48 MAC address in your entterprise tracked is cheaper?= =0A=0A=0AOn Sunday, January 25, 2015 11:44pm, "David Lang" = said:=0A=0A=0A=0A> On Sun, 25 Jan 2015, Valdis.Kletnieks@vt.edu wrote:=0A> = =0A> > On Sun, 25 Jan 2015 18:09:59 -0800, David Lang said:=0A> >> The diff= erence is that the switches and their protocols have been=0A> designed from= =0A> >> the beginning for this scale of operation, IP routing protocols are= =0A> designed for=0A> >> much fewer endpoints to track.=0A> >=0A> > Anybody= who's carrying a full routing table was swallowing on the order=0A> > of 5= 28,833 routes (as of Friday's "weekly routing table report" posted=0A> > to= NANOG). Pretty much everybody and their pet llama accepts full tables=0A> = > thesedays.=0A> >=0A> > You know anybody who's doing that many entries in = an L2 Ethernet broadcast=0A> > domain?=0A> =0A> The full IP routing tables = are something that you normally only have to deal=0A> with in a few devices= at the perimeter of your network.=0A> =0A> What is being talked about here= is routing each /32 IP address individually=0A> throughout your network so= that any IP address can be connected anywhere and=0A> have it 'just work' = as far as the client on that IP is concerned.=0A> =0A> David Lang=0A> ------=_20150126191404000000_63161 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable

And having every /48 MAC= address in your entterprise tracked is cheaper?

=0A=0A



On Sunday, January 25, 2015 11:44pm, "David Lang" <david@lang.hm> s= aid:

=0A
=0A

= > > to NANOG). Pretty much everybody and their pet llama accepts full= tables
> > thesedays.
> >
> > You know an= ybody who's doing that many entries in an L2 Ethernet broadcast
> &= gt; domain?
>
> The full IP routing tables are something t= hat you normally only have to deal
> with in a few devices at the p= erimeter of your network.
>
> What is being talked about h= ere is routing each /32 IP address individually
> throughout your n= etwork so that any IP address can be connected anywhere and
> have = it 'just work' as far as the client on that IP is concerned.
>
> David Lang
>

=0A
 ------=_20150126191404000000_63161--