[168021] in North American Network Operators' Group
Re: turning on comcast v6
daemon@ATHENA.MIT.EDU (Aled Morris)
Mon Jan 6 05:33:40 2014
In-Reply-To: <op.w85e9uy3tfhldh@rbeam.xactional.com>
Date: Mon, 6 Jan 2014 10:33:20 +0000
From: Aled Morris <aledm@qix.co.uk>
To: Ricky Beam <jfbeam@gmail.com>
Cc: NANOG <nanog@nanog.org>
Errors-To: nanog-bounces+nanog.discuss=bloom-picayune.mit.edu@nanog.org
On 4 January 2014 06:06, Ricky Beam <jfbeam@gmail.com> wrote:
> It'll **NEVER** be a default because it breaks too many clueless people's
> networks. Just like, surprise, DHCP "guard" isn't on by default in any
> gear I'm aware of.
>
>
Spanning-tree portfast isn't on by default, and that breaks plenty of
clueless people's networks with client DHCP timeouts. Just sayin'.
I appreciate the view that IPv6 was designed in a certain way, partly to
fix the problems and remove the kludges in IPv4; the reality is that IPv4
was wildly successful because it wasn't the proscriptive OSI.
Whilst I would prefer not to see the mistakes of IPv4 repeated (especially
NAT and RFC1918 addressing) trying to "help" people not shoot themselves in
the foot will simply retard deployment and maybe result in even worse
workarounds.
Come on people - Postel's Law applies, let's be liberal in what we accept
into the protocol design too. If users want DHCP served default gateway,
fine. Nobody's forcing you to enable it on your network if you don't want
to.
Aled
