From: Grant Taylor <gtaylor@riverviewtech.net>
To: Mail List - Netfilter <netfilter@vger.kernel.org>
Subject: Re: Bridges
Date: Thu, 19 Aug 2010 11:41:15 -0500 [thread overview]
Message-ID: <4C6D5EAB.6090509@riverviewtech.net> (raw)
In-Reply-To: <alpine.LSU.2.01.1008191817130.28980@obet.zrqbmnf.qr>
On 08/19/10 11:21, Jan Engelhardt wrote:
> Routing as a concept remains hardware-agnostic.
Agreed.
> Otherwise you would have to tell me whether a bulk of
> RFC1149-conforming pigeons do "routing" or "L3-switching". Absurd
> comparison?
I believe layer 3 switching is a subset of the generic concept of routing.
I forgot how funny RFC 1149 was. Thank you for the chuckle. :-)
Seeing as how the RFC 1149 specifies Avian Carriers and the printing /
scanning of data, I think it defines both layers 1 and 2. Further, the
RFC states that A.C. are a point to point technology. (Where said
points are is subject to change and storms.)
As such, I don't believe that A.C. do routing in any form at all. I
believe the routing is better left to the layer 2.5 / 3 human that is
printing, duct taping, tossing, removing, and scanning of datagrams.
Directly, it is my belief that RFC1149-conforming pigeons don't do
"routing", much less "L3-switching".
Nope, your comparison is not absurd. Though I do think it does open an
can of worms. ;-)
> Optimized ICs surely existed before people started calling routing
> l3-switching.
Quite possibly.
I can't recall when I first heard about layer 3 switching. Though if we
look at the technology of some older (mid to late 90's) higher end
routers, they had switching planes in them. So I'd say that l3
switching (in a switch) is an evolution of technology and More's Law
allowing said technology to come to the l3 wiring closet switch.
> Right... directly from the propaganda ministry. I can see the flaw in
> that.
Hehe. ;-)
Cisco may be the propaganda ministry, but most of their technical
documentation is accurate. Or at least what it's describing is often
imitated by other vendors. Common law standard any one?
Grant. . . .
next prev parent reply other threads:[~2010-08-19 16:41 UTC|newest]
Thread overview: 68+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-08-17 22:44 Bridges Jonathan Tripathy
2010-08-17 22:56 ` Bridges Jan Engelhardt
2010-08-17 23:34 ` Bridges Stephen Hemminger
2010-08-18 11:27 ` Bridges Thomas Jacob
2010-08-18 19:51 ` Bridges Jonathan Tripathy
2010-08-18 21:51 ` Bridges Grant Taylor
2010-08-18 21:57 ` Bridges Jonathan Tripathy
2010-08-18 22:08 ` Bridges Grant Taylor
2010-08-18 22:15 ` Bridges Jonathan Tripathy
2010-08-18 22:26 ` Bridges Jan Engelhardt
2010-08-18 22:51 ` Bridges Jonathan Tripathy
2010-08-18 23:05 ` Bridges Pascal Hambourg
2010-08-18 23:07 ` Bridges Jonathan Tripathy
2010-08-18 23:21 ` Bridges Pascal Hambourg
2010-08-18 23:23 ` Bridges Jonathan Tripathy
2010-08-18 23:45 ` Bridges Jonathan Tripathy
2010-08-19 7:26 ` Bridges Pascal Hambourg
2010-08-19 18:47 ` Bridges Jonathan Tripathy
2010-08-19 19:26 ` Bridges Pascal Hambourg
2010-08-19 19:37 ` Bridges Jonathan Tripathy
2010-08-19 20:00 ` Bridges Jan Engelhardt
2010-08-19 20:11 ` Bridges Jonathan Tripathy
2010-08-19 21:14 ` Bridges Pascal Hambourg
2010-08-19 21:24 ` Bridges Jonathan Tripathy
2010-08-19 22:04 ` Bridges Pascal Hambourg
2010-08-19 22:53 ` Bridges Jonathan Tripathy
2010-08-20 8:53 ` Bridges Pascal Hambourg
2010-08-21 21:46 ` Bridges Jonathan Tripathy
2010-08-21 23:25 ` Bridges Jan Engelhardt
[not found] ` <4C70E853.6050107@abpni.co .uk>
2010-08-22 9:05 ` Bridges Jonathan Tripathy
2010-08-22 9:09 ` Bridges Jan Engelhardt
[not found] ` <4C70E 9A2.3040907@abpni.co.uk>
2010-08-22 9:10 ` Bridges Jonathan Tripathy
2010-08-22 21:02 ` Bridges Pascal Hambourg
[not found] ` <4C7194 D3.7070803@abpni.co.uk>
2010-08-22 21:21 ` Bridges Jonathan Tripathy
2010-08-23 8:22 ` Bridges Pascal Hambourg
2010-08-23 20:18 ` Bridges Jonathan Tripathy
2010-08-24 8:57 ` Bridges Karel Rericha
2010-08-24 14:44 ` Bridges Pascal Hambourg
2010-08-24 17:37 ` Bridges Jonathan Tripathy
2010-08-24 18:07 ` Bridges Pascal Hambourg
2010-08-24 18:34 ` Bridges Jonathan Tripathy
2010-08-24 22:20 ` Bridges Pascal Hambourg
2010-08-20 8:38 ` Bridges Jan Engelhardt
2010-08-20 9:05 ` Bridges Pascal Hambourg
2010-08-20 9:09 ` Bridges Jan Engelhardt
2010-08-20 10:26 ` Bridges Pascal Hambourg
2010-08-20 16:02 ` Bridges Grant Taylor
2010-08-20 16:18 ` Bridges Jan Engelhardt
2010-08-20 16:25 ` Bridges Grant Taylor
2010-08-20 16:32 ` Bridges Jan Engelhardt
2010-08-21 12:48 ` Bridges Pascal Hambourg
2010-08-21 21:44 ` Bridges Grant Taylor
2010-08-19 19:28 ` Bridges Jan Engelhardt
2010-08-18 22:59 ` Bridges Pascal Hambourg
2010-08-18 23:00 ` Bridges Jonathan Tripathy
2010-08-18 23:11 ` Bridges Pascal Hambourg
2010-08-19 8:29 ` Bridges Jan Engelhardt
2010-08-19 9:16 ` Bridges Pascal Hambourg
2010-08-19 3:52 ` Bridges Grant Taylor
2010-08-19 7:33 ` Bridges Pascal Hambourg
2010-08-19 14:51 ` Bridges Grant Taylor
2010-08-19 14:56 ` Bridges Jan Engelhardt
2010-08-19 15:49 ` Bridges Grant Taylor
2010-08-19 16:21 ` Bridges Jan Engelhardt
2010-08-19 16:41 ` Grant Taylor [this message]
2010-08-19 17:10 ` Bridges Jan Engelhardt
2010-08-19 18:36 ` Bridges Grant Taylor
2010-08-19 17:10 ` Bridges Rick Jones
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=4C6D5EAB.6090509@riverviewtech.net \
--to=gtaylor@riverviewtech.net \
--cc=netfilter@vger.kernel.org \
/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