From: James (james@towardex.com)
Date: Mon Sep 20 2004 - 00:32:56 GMT-3
On Sun, Sep 19, 2004 at 11:22:28PM -0400, Scott Morris wrote:
> Saying it's no different is a huge understatement. :)
>
> Many rules change when it comes to how you program the routing protocols...
> However, in the grand scheme of things, just realize that it is not a "core"
> topic....
Yes I agree.. but..
Most people in general, when they first see IPv6, their first response is
that is a completely different world of thing with its own concepts and
with its own way of dealings as if it is first time they see Voice. That
ofcourse is from my experience, which can be different from others.
My point is that IPv6 _concept_ is in line with IPv4. One needs to review
the IETF documentations and relevant RFC's, possibly research up in industry
developments to learn really about how IPv6 is different than IPv4.
Places like Internet2/Abilene, Tiscali, Sprint & number of networks who run
tun/native/dual-stack IPv4/IPv6 *production* networks today have certainly
shared some of their backbone design experiences and configuration snippets
to the industry, including Cisco and Juniper mostly in config formats.
It is ofcourse different, and rules do change, starting with the way ip
address looks and how one should subnet it, but the concept of internetwork
routing remains relatively the same. My point is if you have problems
configuring ISIS with IPv4, you will continue to have problems in IPv6 of
it. Once the conceptual basis of internetwork routing is in place, and
learning what has been changed in IPv6 specifically, then the time it
takes to pick up the knowledge in realm of what to type becomes a lot
easier...
>
> Learn the general concepts and know how to look things up on the DocCD...
> The CD has very good information about dealing with IPv6.
>
> 788 pages is nice if you want to implement it. Skimming it, playing with it
> once or twice and knowing where to look it up is nice if you want to not
> freak out when it shows up on your CCIE lab exam in January!
I agree. :)
-J
-- James Jun TowardEX Technologies, Inc. Technical Lead Network Design, Consulting, IT Outsourcing james@towardex.com Boston-based Colocation & Bandwidth Services cell: 1(978)-394-2867 web: http://www.towardex.com , noc: www.twdx.net
This archive was generated by hypermail 2.1.4 : Fri Oct 01 2004 - 15:00:46 GMT-3