Re: [Fwd: (ngtrans) I-D ACTION:draft-many-ngtrans-connect-ipv6-igp-01.txt]

Pekka Savola <pekkas@netcore.fi> Mon, 04 March 2002 14:44 UTC

Received: from mercury.Sun.COM (mercury.Sun.COM [192.9.25.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA26482 for <ngtrans-archive@odin.ietf.org>; Mon, 4 Mar 2002 09:44:29 -0500 (EST)
Received: from engmail2.Eng.Sun.COM ([129.146.1.25]) by mercury.Sun.COM (8.9.3+Sun/8.9.3) with ESMTP id GAA16657; Mon, 4 Mar 2002 06:41:30 -0800 (PST)
Received: from sunroof.eng.sun.com (sunroof.Eng.Sun.COM [129.146.168.88]) by engmail2.Eng.Sun.COM (8.9.3+Sun/8.9.3/ENSMAIL,v2.1p1) with ESMTP id GAA08913; Mon, 4 Mar 2002 06:41:08 -0800 (PST)
Received: from sunroof.eng.sun.com (localhost [127.0.0.1]) by sunroof.eng.sun.com (8.12.2+Sun/8.12.2) with ESMTP id g24EeZKL023235 for <ngtrans-dist@sunroof.eng.sun.com>; Mon, 4 Mar 2002 06:40:35 -0800 (PST)
Received: (from majordomo@localhost) by sunroof.eng.sun.com (8.12.2+Sun/8.12.2/Submit) id g24EeZCP023234 for ngtrans-dist; Mon, 4 Mar 2002 06:40:35 -0800 (PST)
X-Authentication-Warning: sunroof.eng.sun.com: majordomo set sender to owner-ngtrans@sunroof.eng.sun.com using -f
Received: from engmail3.Eng.Sun.COM (engmail3 [129.144.170.5]) by sunroof.eng.sun.com (8.12.2+Sun/8.12.2) with ESMTP id g24EeWKL023227 for <ngtrans@sunroof.eng.sun.com>; Mon, 4 Mar 2002 06:40:32 -0800 (PST)
Received: from venus.sun.com (venus.EBay.Sun.COM [129.150.69.5]) by engmail3.Eng.Sun.COM (8.9.3+Sun/8.9.3/ENSMAIL, v2.1p1) with ESMTP id GAA03989 for <ngtrans@sunroof.eng.sun.com>; Mon, 4 Mar 2002 06:40:32 -0800 (PST)
Received: from netcore.fi (netcore.fi [193.94.160.1]) by venus.sun.com (8.9.3+Sun/8.9.3) with ESMTP id GAA28500 for <ngtrans@sunroof.eng.sun.com>; Mon, 4 Mar 2002 06:40:30 -0800 (PST)
Received: from localhost (pekkas@localhost) by netcore.fi (8.11.6/8.11.6) with ESMTP id g24EeOx21962; Mon, 4 Mar 2002 16:40:24 +0200
Date: Mon, 04 Mar 2002 16:40:24 +0200
From: Pekka Savola <pekkas@netcore.fi>
To: Damien Galand <damien.galand@alcatel.fr>
cc: ngtrans@sunroof.eng.sun.com
Subject: Re: [Fwd: (ngtrans) I-D ACTION:draft-many-ngtrans-connect-ipv6-igp-01.txt]
In-Reply-To: <3C837D6C.D957D5EB@alcatel.fr>
Message-ID: <Pine.LNX.4.44.0203041634470.21908-100000@netcore.fi>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset="US-ASCII"
Sender: owner-ngtrans@sunroof.eng.sun.com
Precedence: bulk
Reply-To: Pekka Savola <pekkas@netcore.fi>

On Mon, 4 Mar 2002, Damien Galand wrote:
> --------------------------------------
> Abstract
> 
> This draft proposes a mechanism that allows an  incremental deployment
> of IPv6 inside an IPv4 AS. It aims at automatically set up tunnels,
> using IGP standard capabilities, in order to gradually introduce IPv6
> connectivity within an initially IPv4 AS. As specified in
> draft-ietf-ngtrans-introduction-to-ipv6-transition-07.txt, this
> technique must be considered as a solution with a scope of domain.

Why not ISATAP [or BGP-tunneling, sigh]?

Personally I really don't see why we need a lot of really specific
solutions when ones we already have provide almost everything anyone would
need.  Soon ngtrans will be a dump of everything fancy like some say MPLS
is. 

I think this kind of "micro-specifying" is just drawing the attention from
the really important issues, like getting on with the transition and
fixing (possible) issues in current transition toolbox.

Detailed comments to the draft later.

-- 
Pekka Savola                 "Tell me of difficulties surmounted,
Netcore Oy                   not those you stumble over and fall"
Systems. Networks. Security.  -- Robert Jordan: A Crown of Swords