[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
IPv6 Confusion
- Subject: IPv6 Confusion
- From: drc at virtualized.org (David Conrad)
- Date: Tue, 17 Feb 2009 12:20:19 -0800
- In-reply-to: <050701c99135$df0f0ed0$9d2d2c70$@net>
- References: <6CDE22DE80A63A4DACF4FE2C916519A53F022F784D@BLV11EXVS01.corp.dm.local>	<[email protected]>	<6CDE22DE80A63A4DACF4FE2C916519A53F022F788E@BLV11EXVS01.corp.dm.local>	<050701c99135$df0f0ed0$9d2d2c70$@net>
On Feb 17, 2009, at 11:28 AM, Tony Hain wrote:
> Approach IPv6 as a new and different protocol.
Unfortunately, I gather this isn't what end users or network operators  
want or expect.  I suspect if we want to make real inroads towards  
IPv6 deployment, we'll need to spend a bit more time making IPv6 look,  
taste, and feel like IPv4 and less time berating folks for "IPv4- 
think" (not that you do this, but others here do).  For example,  
getting over the stateless autoconfig religion (which was never fully  
thought out -- how does a autoconfig'd device get a DNS name  
associated with their address in a DNSSEC-signed world again?) and  
letting network operators use DHCP with IPv6 the way they do with IPv4.
Or, we simply continue down the path of more NATv4.
Regards,
-drc