IETF Logo Mail Archive

(ngtrans) draft-lefaucheur-bgp-tunnel-transition-00.txt

itojun@iijlab.net Wed, 17 July 2002 02:17 UTC

Received: from patan.sun.com (patan.Sun.COM [192.18.98.43]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id WAA08580 for <ngtrans-archive@lists.ietf.org>; Tue, 16 Jul 2002 22:17:25 -0400 (EDT)
Received: from engmail4.Eng.Sun.COM ([129.144.134.6]) by patan.sun.com (8.9.3+Sun/8.9.3) with ESMTP id UAA11009; Tue, 16 Jul 2002 20:17:31 -0600 (MDT)
Received: from sunroof.eng.sun.com (sunroof.Eng.Sun.COM [129.146.168.88]) by engmail4.Eng.Sun.COM (8.9.3+Sun/8.9.3/ENSMAIL,v2.1p1) with ESMTP id TAA20073; Tue, 16 Jul 2002 19:17:19 -0700 (PDT)
Received: from sunroof.eng.sun.com (localhost [127.0.0.1]) by sunroof.eng.sun.com (8.12.4/8.12.4) with ESMTP id g6H2GgoN000128 for <ngtrans-dist@sunroof.eng.sun.com>; Tue, 16 Jul 2002 19:16:42 -0700 (PDT)
Received: (from majordomo@localhost) by sunroof.eng.sun.com (8.12.4/8.12.4/Submit) id g6H2Gf35000127 for ngtrans-dist; Tue, 16 Jul 2002 19:16:41 -0700 (PDT)
X-Authentication-Warning: sunroof.eng.sun.com: majordomo set sender to owner-ngtrans@sunroof.eng.sun.com using -f
Received: from engmail2.Eng.Sun.COM (engmail2 [129.146.1.25]) by sunroof.eng.sun.com (8.12.4/8.12.4) with ESMTP id g6H2GcoN000119 for <ngtrans@sunroof.eng.sun.com>; Tue, 16 Jul 2002 19:16:38 -0700 (PDT)
Received: from pheriche.sun.com (pheriche.Central.Sun.COM [129.147.5.34]) by engmail2.Eng.Sun.COM (8.9.3+Sun/8.9.3/ENSMAIL, v2.1p1) with ESMTP id TAA18977 for <ngtrans@sunroof.eng.sun.com>; Tue, 16 Jul 2002 19:16:41 -0700 (PDT)
Received: from coconut.itojun.org (coconut.itojun.org [210.160.95.97]) by pheriche.sun.com (8.9.3+Sun/8.9.3) with ESMTP id UAA28445 for <ngtrans@sunroof.eng.sun.com>; Tue, 16 Jul 2002 20:16:39 -0600 (MDT)
Received: from itojun.org (localhost [127.0.0.1]) by coconut.itojun.org (Postfix) with ESMTP id 7F8C54B22 for <ngtrans@sunroof.eng.sun.com>; Wed, 17 Jul 2002 11:16:32 +0900 (JST)
To: ngtrans@sunroof.eng.sun.com
X-Template-Reply-To: itojun@itojun.org
X-Template-Return-Receipt-To: itojun@itojun.org
X-PGP-Fingerprint: F8 24 B4 2C 8C 98 57 FD 90 5F B4 60 79 54 16 E2
Subject: (ngtrans) draft-lefaucheur-bgp-tunnel-transition-00.txt
From: itojun@iijlab.net
Date: Wed, 17 Jul 2002 11:16:32 +0900
Message-Id: <20020717021632.7F8C54B22@coconut.itojun.org>
Sender: owner-ngtrans@sunroof.eng.sun.com
Precedence: bulk
Reply-To: itojun@iijlab.net

	i don't understand why this transition technology is needed.

	to make use of this mechanism, we need to upgrade all of the EBGP
	routers in the cloud.  when doing so, we can setup normal RFC2893
	tunnels and do normal BGP4+ over IPv6 (over IPv6-over-IPv4 tunnel).
	we don't need a new automated mechanism.

	another thing bothers me is the special use of IPv4 mapped address
	as indication of tunnel endpoint.  IPv4 mapped address already has
	overloaded with multiple meanings (RFC2553 API, SIIT, ...) and i
	really want to see these multiple semantics get removed, and make it
	be used only for RFC2553 only.  it causes a lot of security issues
	as outlined in my previous drafts.
	(i'm happy to say long good bye to IPv4 mapped address itself, but that
	is another question)

	we don't need more magic.

itojun

v2.23.0 | Report a Bug | By Email