[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
IPv6 Confusion
- Subject: IPv6 Confusion
- From: randy at psg.com (Randy Bush)
- Date: Thu, 19 Feb 2009 16:55:15 +0900
- In-reply-to: <[email protected]>
- References: <6CDE22DE80A63A4DACF4FE2C916519A53F022F784D@BLV11EXVS01.corp.dm.local>	<[email protected]>	<6CDE22DE80A63A4DACF4FE2C916519A53F022F788E@BLV11EXVS01.corp.dm.local>	<050701c99135$df0f0ed0$9d2d2c70$@net>	<[email protected]>	<056801c9914d$7c2a0e10$747e2a30$@net>	<[email protected]>	<072401c9920d$cb823cb0$6286b610$@net>	<[email protected]>
>  This may be where Randy Bush derives his "IVTF"  label.
not exactly.  see <http://archive.psg.com/051000.ccr-ivtf.pdf>.
> Yes, there have been attempts to bridge the two camps, but I suspect  
> the only way to really address this is a fundamental shift in the way  
> the IETF does business, taking into account the fact that network  
> operators and end users, by and large, are not the implementors of  
> protocols and don't actually care how they are implemented, but rather  
> the folks who define what the protocols need to do.  I'll admit some  
> skepticism that such a change is actually feasible.
standards bodies used to be composed of users meeting to drive vendors
to common specs so the users had freedom of choice and inter-operation.
the ietf has become vendors inventing new and ever more complex features
to drive users to minimal margins.
randy