[89237] in North American Network Operators' Group

home help back first fref pref prev next nref lref last post

Time for IPv10? (was Re: Time for IPv8?)

daemon@ATHENA.MIT.EDU (Roland Dobbins)
Sun Mar 5 22:51:30 2006

In-Reply-To: <86B89662-FD68-47E1-BCFE-2C3832E1380D@cisco.com>
From: Roland Dobbins <rdobbins@cisco.com>
Date: Sun, 5 Mar 2006 19:50:56 -0800
To: nanog@nanog.org
Errors-To: owner-nanog@merit.edu



[ It's been pointed out that, due to various historical reasons, IPv8  
might not be the best choice of version-number to use in this  
context.  So, IPv10 can serve for purposes of discussion, in its  
stead. ]

On Mar 5, 2006, at 7:19 PM, Roland Dobbins wrote:

>
>
> On Mar 5, 2006, at 6:59 PM, Owen DeLong wrote:
>
>> Far from it, but, there are lessons to be
>> learned that are applicable to the internet, and, separating the
>> end system identifier from the routing function is one we still seem
>> determined to avoid for reasons passing my understanding.
>
> And this is the real answer, of course.
>
> There were two fundamental design decisions made back in the Olden  
> Days which continue to exert a strong and in many cases quite  
> negative sway over this entire set of inter-related issues:
>
> 1.	Utilizing the endpoint identifier in the routing function, as
> 	Vince Fuller and you (among others) have stated, and
>
> 2.	The ships-in-the-night nature of the TCP/IP protocol stack.
> 	This latter design decision is a big part of the reason TCP/IP
> 	has been so successful to date; however, we find more and
> 	more kludgey, brittle hacks to try and provide some sort
> 	of linkages for purposes of enforcing policy, etc.  The
> 	irony is that these attempts largely stem from the unforeseen
> 	side-effects of #1, and also contribute to a reinforcing
> 	feedback loop which further locks us into #1.
>
> Given the manifold difficulties we're facing today as a result of  
> these two design decisions (#2 is a 'hidden' reason behind untold  
> amounts of capex and opex being spent in frustratingly  
> nonproductive ways), perhaps it is time to consider declaring the  
> 'Limited-Deployment IPv6 Proof-of-Concept Experiment' to be a  
> success, take the lessons learned (there are a lot more unresolved  
> and potentially problematic issues than those mentioned in this  
> thread) into account and get started on IPv8.
>
> ----------------------------------------------------------------------
> Roland Dobbins <rdobbins@cisco.com> // 408.527.6376 voice
>
>      Everything has been said.  But nobody listens.
>
>                    -- Roger Shattuck

----------------------------------------------------------------------
Roland Dobbins <rdobbins@cisco.com> // 408.527.6376 voice

      Everything has been said.  But nobody listens.

                    -- Roger Shattuck


home help back first fref pref prev next nref lref last post