The use of RIPng

[Benedikt Stockebrand]

Hi Ted and list,

Ted Mittelstaedt <tedm at ipinc.net> writes:

> Complexity like running a routing protocol on each WS? ;-)

That's what we did fifteen years ago with IPv4.

Then came VRRP and HSRP, plus whatever non-standardized mechanisms you
would use with a stateful packet filter.  Saved quite some trouble.

And with IPv6, Autoconf+NUD becomes yet another option.

> This does NOT mean that all cheap solutions are reliable.

That's he problem: Too often you only find out after you've deployed
them.

As far as "buy Cisco/IBM/Microsoft/<whatever big name> and you're are
out of trouble" goes, I think we agree that that only works if you
need an excuse towards management rather than an actual solution.

> Hmm, well we treat all our customers, including the residential ones,
> this way.

In that case you don't have those "buy cheap" people as customers.
I've been working for a large ISP (then called T-Online), and with
customer support showing up rather impressively on the balance sheet,
no matter what you do it's eventually down to "you get what you pay
for".

In other words, consider yourself lucky.  Small end users do have
their own peculiarities, but the low-cost end user business can really
drive you crazy.  And no, I didn't do user support (whatever level)
there.

> In any case, as far as Internet connectivity goes, the Telco's
> control the reliability of THAT. 
> [...]
> Perhaps the Telco's operate differently in Germany?

The people I talk about frequently have a dial-up backup solution,
often with UMTS/3G as a last resort.

And while the telcos are likely pretty much the same all over the
world, there are smaller ISPs here who primarily target these
customers.  As I understand, they frequently offer fallback
connectivity to business customers.


Cheers,

    Benedikt

-- 
			 Business Grade IPv6
		    Consulting, Training, Projects

Benedikt Stockebrand, Dipl.-Inform.   http://www.benedikt-stockebrand.de/