From: dpreed@reed.com
To: "David Lang" <david@lang.hm>
Cc: "cerowrt-devel@lists.bufferbloat.net"
<cerowrt-devel@lists.bufferbloat.net>
Subject: Re: [Cerowrt-devel] Recording RF management info _and_ associated traffic?
Date: Mon, 26 Jan 2015 19:14:04 -0500 (EST) [thread overview]
Message-ID: <1422317644.389812775@apps.rackspace.com> (raw)
In-Reply-To: <alpine.DEB.2.02.1501252039590.19609@nftneq.ynat.uz>
[-- Attachment #1: Type: text/plain, Size: 1237 bytes --]
And having every /48 MAC address in your entterprise tracked is cheaper?
On Sunday, January 25, 2015 11:44pm, "David Lang" <david@lang.hm> said:
> On Sun, 25 Jan 2015, Valdis.Kletnieks@vt.edu wrote:
>
> > On Sun, 25 Jan 2015 18:09:59 -0800, David Lang said:
> >> The difference is that the switches and their protocols have been
> designed from
> >> the beginning for this scale of operation, IP routing protocols are
> designed for
> >> much fewer endpoints to track.
> >
> > Anybody who's carrying a full routing table was swallowing on the order
> > of 528,833 routes (as of Friday's "weekly routing table report" posted
> > to NANOG). Pretty much everybody and their pet llama accepts full tables
> > thesedays.
> >
> > You know anybody who's doing that many entries in an L2 Ethernet broadcast
> > domain?
>
> The full IP routing tables are something that you normally only have to deal
> with in a few devices at the perimeter of your network.
>
> What is being talked about here is routing each /32 IP address individually
> throughout your network 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
>
[-- Attachment #2: Type: text/html, Size: 1906 bytes --]
next prev parent reply other threads:[~2015-01-27 0:14 UTC|newest]
Thread overview: 43+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-01-14 2:20 Richard Smith
2015-01-20 16:59 ` Rich Brown
2015-01-21 23:40 ` Richard Smith
2015-01-21 23:58 ` David Lang
2015-01-22 9:04 ` Richard Smith
2015-01-22 9:18 ` David Lang
2015-01-22 18:19 ` Richard Smith
2015-01-22 22:09 ` David Lang
2015-01-22 22:55 ` Roman Toledo Casabona
2015-01-24 14:59 ` dpreed
2015-01-24 15:30 ` Kelvin Edmison
2015-01-25 4:35 ` David Lang
2015-01-25 5:02 ` Dave Taht
2015-01-25 5:04 ` Dave Taht
2015-01-25 6:44 ` David Lang
2015-01-25 7:06 ` David Lang
[not found] ` <CAA93jw64KjW-JjLxB3i_ZK348NCyJYSQACFO34MaUsBBWyZ+pA@mail.gmail.com>
2015-01-25 7:59 ` Dave Taht
2015-01-25 9:39 ` David Lang
2015-01-25 15:03 ` Chuck Anderson
2015-01-25 20:17 ` dpreed
2015-01-25 23:21 ` Aaron Wood
2015-01-25 23:57 ` David Lang
2015-01-26 1:51 ` dpreed
2015-01-26 2:09 ` David Lang
2015-01-26 4:33 ` Valdis.Kletnieks
2015-01-26 4:44 ` David Lang
2015-01-27 0:14 ` dpreed [this message]
2015-01-27 0:23 ` David Lang
2015-01-26 2:19 ` Dave Taht
2015-01-26 2:43 ` David Lang
2015-01-26 2:58 ` Dave Taht
2015-01-26 3:17 ` dpreed
2015-01-26 3:32 ` David Lang
2015-01-26 3:45 ` Dave Taht
2015-01-27 0:12 ` dpreed
2015-01-27 0:31 ` David Lang
2015-01-27 0:36 ` Dave Taht
2015-01-26 3:19 ` David Lang
2015-01-26 4:25 ` Valdis.Kletnieks
2015-01-26 4:39 ` David Lang
2015-01-26 16:42 ` Valdis.Kletnieks
2015-01-25 8:07 ` Outback Dingo
2015-01-30 16:14 ` Richard Smith
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://lists.bufferbloat.net/postorius/lists/cerowrt-devel.lists.bufferbloat.net/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1422317644.389812775@apps.rackspace.com \
--to=dpreed@reed.com \
--cc=cerowrt-devel@lists.bufferbloat.net \
--cc=david@lang.hm \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox