Development issues regarding the cerowrt test router project
 help / color / mirror / Atom feed
From: Mike O'Dell <mo@ccr.org>
To: Dave Taht <dave.taht@gmail.com>
Cc: "cerowrt-devel@lists.bufferbloat.net"
	<cerowrt-devel@lists.bufferbloat.net>
Subject: Re: [Cerowrt-devel] Cerowrt-devel Digest, Vol 31, Issue 4
Date: Sat, 07 Jun 2014 14:54:07 -0400	[thread overview]
Message-ID: <20140607185407.165BB119C54@ccr.org> (raw)
In-Reply-To: Your message of "Sat, 07 Jun 2014 11:21:17 PDT." <CAA93jw6hhUiBfA+x68S52dcGs_vj8GJ_fyuBgev9=0NnTM-3bA@mail.gmail.com>


Having links from multiple providers "just work" is indeed a grand idea.

Unfortunately, IPv6 doesn't deal with multihoming any better than IPv4 doesn't;
in fact, it's pretty clearly worse.

you can get the bath water to run out a different hole by tipping
the bathtub, but you can't make in run *into* the bathtub the same way.

I agree that nested NATs are suboptimal and usually unnecessary.

As for falling off the cliff of bridging, it depends entirely
on how far you fall and what you land upon. 

The fundamental problem is that the L2 fabric needs dynamic routing
more sophisticated than a Spanning Tree. It's not hard to do and
is quite effective at solving the problems of transiting local
dynamic topology without annoying the L3 machinery. It even provides
for traffic engineering of different traffic types without having
to suffer through the myriad NO-OPs created by the IETF trying to solve
the problem in a network flat as road-kill on an Interstate.

	-mo

  reply	other threads:[~2014-06-07 18:54 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <mailman.51111.1402070994.1815.cerowrt-devel@lists.bufferbloat.net>
2014-06-07 18:02 ` Mike O'Dell
2014-06-07 18:21   ` Dave Taht
2014-06-07 18:54     ` Mike O'Dell [this message]
2014-06-07 19:07       ` Dave Taht
2014-06-07 19:20         ` Mike O'Dell
2014-06-07 19:41           ` Dave Taht
2014-06-07 19:54             ` Dave Taht

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=20140607185407.165BB119C54@ccr.org \
    --to=mo@ccr.org \
    --cc=cerowrt-devel@lists.bufferbloat.net \
    --cc=dave.taht@gmail.com \
    /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