[v6tc] Re: Tunneling and Transition Drafts (fwd)
Pekka Savola <pekkas@netcore.fi> Wed, 06 April 2005 08:03 UTC
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id EAA12344; Wed, 6 Apr 2005 04:03:21 -0400 (EDT)
Received: from megatron.ietf.org ([132.151.6.71]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1DJ5dn-0003VL-2V; Wed, 06 Apr 2005 04:11:59 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1DJ5Un-0001JV-TD; Wed, 06 Apr 2005 04:02:41 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1DJ5Uk-0001Hp-KY for v6tc@megatron.ietf.org; Wed, 06 Apr 2005 04:02:38 -0400
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id EAA12255 for <v6tc@ietf.org>; Wed, 6 Apr 2005 04:02:36 -0400 (EDT)
Received: from netcore.fi ([193.94.160.1]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1DJ5d3-0003U0-Ic for v6tc@ietf.org; Wed, 06 Apr 2005 04:11:14 -0400
Received: from localhost (pekkas@localhost) by netcore.fi (8.11.6/8.11.6) with ESMTP id j3682Sk12010 for <v6tc@ietf.org>; Wed, 6 Apr 2005 11:02:28 +0300
Date: Wed, 06 Apr 2005 11:02:28 +0300
From: Pekka Savola <pekkas@netcore.fi>
To: v6tc@ietf.org
Message-ID: <Pine.LNX.4.61.0504061101480.11494@netcore.fi>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset="US-ASCII"; format="flowed"
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 6e922792024732fb1bb6f346e63517e4
Subject: [v6tc] Re: Tunneling and Transition Drafts (fwd)
X-BeenThere: v6tc@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: v6tc.ietf.org
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/v6tc>, <mailto:v6tc-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www1.ietf.org/pipermail/v6tc>
List-Post: <mailto:v6tc@ietf.org>
List-Help: <mailto:v6tc-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/v6tc>, <mailto:v6tc-request@ietf.org?subject=subscribe>
Sender: v6tc-bounces@ietf.org
Errors-To: v6tc-bounces@ietf.org
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 9a2be21919e71dc6faef12b370c4ecf5
FYI -- I didn't think this was relevant to v6tc (except about the clarification of the focus of v6tc) so I didn't add Cc:. ---------- Forwarded message ---------- Date: Wed, 6 Apr 2005 09:13:24 +0300 (EEST) From: Pekka Savola <pekkas@netcore.fi> To: Fred Baker <fred@cisco.com> Cc: v6ops@ops.ietf.org, Lindqvist Erik Kurt <kurtis@kurtis.pp.se>, David Kessens <david.kessens@nokia.com> Subject: Re: Tunneling and Transition Drafts On Tue, 5 Apr 2005, Fred Baker wrote: > As I understand it, v6tc (which was intended to take over all the tunneling > stuff, which is to say a large proposition of the transition stuff) is dead > in the water. The expectation was that all the tunneling/transition stuff > would move there, but the BOF was a non-event. There isn't likely to be a > v6tc WG. (Dear AD: if you disagree, this would be a good time to say so). No, "[v6tc] intended to take over all the tunneling stuff" was *never* the goal of v6tc. Many months ago (maybe it's at about a year now), when we first discussed how to move around with all the work that keeps coming to v6ops, one of the first proposals was to create "v6tuns" working group, working on the tunneling mechanisms. The idea was rejected in the relatively short order, and has not been seen since. We don't need another ngtrans, specifying all the transition mechanisms people come up with. (However, one, slightly better idea was to create a maintenance WG to move 6to4 to Draft Standard, figure out what to do with so-called 6over4, move rfc2893(bis) to DS, etc. -- but there would undoubtedly be a big slippery slope there, and it may be a bit too early for this activity.) > - how to tunnel IPv6 through an IPv4-only/dominant network between > IPv6-only/dominant hosts or networks > > key attribute: static or dynamic IPv6/IPv4 tunnels between tunnel > endpoints, and appropriate routing through the IPv4 domain to > determine what the appropriate tunnel endpoint router would be. > Could be done with a DNS name not unlike a reverse lookup for > the IPv6 address but delivering an IPv4 "A" record. Could also > be done through simple routing if the tunnels sty up or use a > concept like RFC 1793. The DNS lookup (after you know what you're looking for -- including "discovery" part is trickier) is not a hard problem. The real problem, which v6tc set out primarily to solve was how to set up the tunnel at both endpoints without requiring manual configuration (especially the endpoint addresses) at both ends -- and running a routing protocol between the two is a non-starter. > - how to translate IPv6->IPv4 and IPv6-IPv4 between an IPv6-only/dominant > and an IPv4-only/dominant domain > > key attribute: translation system captures DNS lookups and > re-advertises its own address in some way, so that IPv4 hosts > seeking IPv6 peers connect to it and it translates, and IPv6 > hosts connect to it and it translates. This must be badly worded because that you're saying is basically NAT-PT with DNS-ALG, which is exactly what we just decided was a bit.. um.. problematic, and requested reclassification as Experimental. > Which brings me to my question. I am being asked by various proponents of > various things what the working group wants to do with their approach. I need > to know what the game plan for this working group is: let a thousand flowers > bloom (they can all ask for informational status from the RFC Editor and the > probability that the transition will happen in an orderly fashion rapidly > approaches zero), or I need a consensus statement from the working group that > every single approach on the table will be set aside and the working group > will actively work on providing a single solution that meets all those needs > that the IETF can look at and say "yes, that will accomplish an orderly > transition in a timely fashion and If I read this correctly, you see two options: 1) let the authors publish their stuff as RFC-ed informational, if they want to, or 2) produce a Grand Unified Mechanism somewhere (here or some other WG) which solves all the needs (and hopefully world hunger besides). [This is a bit challenging as those needs include tunneling in every possible way, translation, etc.] These are a bit polarized. What I think we should do is: - obviously, allow 1) if that's what people want - not use the v6ops meeting time etc. on these proposals; short pointers on the list may be OK, but lengthy discussions should be elsewhere (discretion of the chairs to rule out stuff as out of scope, as always) - if a mechanism comes along that a lot of people actually want to work on, ask that they create a BOF, and then see if it gains sufficient momentum or not. - or the authors can obviously try to reach ADs and ask sponsoring the work; or use appropriate other WGs if the work is in scope there (e.g., 6PE (bgp tunneling) work has moved over to IDR wg) -- Pekka Savola "You each name yourselves king, yet the Netcore Oy kingdom bleeds." Systems. Networks. Security. -- George R.R. Martin: A Clash of Kings _______________________________________________ v6tc mailing list v6tc@ietf.org https://www1.ietf.org/mailman/listinfo/v6tc
- [v6tc] Re: Tunneling and Transition Drafts (fwd) Pekka Savola
- Re: l2tp support on OS's Re: [v6tc] Re: Tunneling… JORDI PALET MARTINEZ
- [v6tc] Re: Tunneling and Transition Drafts JORDI PALET MARTINEZ
- [v6tc] Re: Tunneling and Transition Drafts Fred Baker
- Re: [v6tc] Re: Tunneling and Transition Drafts Jerome Durand
- Re: [v6tc] Re: Tunneling and Transition Drafts Pekka Savola
- Re: [v6tc] Re: Tunneling and Transition Drafts Soininen Jonne (Nokia-NET/Helsinki)
- Re: [v6tc] Re: Tunneling and Transition Drafts Jerome Durand
- RE: [v6tc] Re: Tunneling and Transition Drafts Bound, Jim
- RE: [v6tc] Re: Tunneling and Transition Drafts Bound, Jim
- Re: [v6tc] Re: Tunneling and Transition Drafts Thomas Narten
- Re: Fwd: [v6tc] Re: Tunneling and Transition Draf… Thomas Narten
- Re: [v6tc] Re: Tunneling and Transition Drafts JORDI PALET MARTINEZ
- Fwd: [v6tc] Re: Tunneling and Transition Drafts Fred Baker
- Re: [v6tc] Re: Tunneling and Transition Drafts Fred Baker
- RE: [v6tc] Re: Tunneling and Transition Drafts Soohong Daniel Park
- Re: [v6tc] Re: Tunneling and Transition Drafts Radhakrishnan Suryanarayanan
- Re: [v6tc] Re: Tunneling and Transition Drafts Jerome Durand
- Re: [v6tc] Re: Tunneling and Transition Drafts Jeroen Massar
- Re: [v6tc] Re: Tunneling and Transition Drafts Pekka Savola
- Re: [v6tc] Re: Tunneling and Transition Drafts JORDI PALET MARTINEZ
- Re: [v6tc] Re: Tunneling and Transition Drafts Thomas Narten
- Re: [v6tc] Re: Tunneling and Transition Drafts Jeroen Massar
- Re: [v6tc] Re: Tunneling and Transition Drafts JORDI PALET MARTINEZ
- Re: [v6tc] Re: Tunneling and Transition Drafts Pekka Savola
- Re: [v6tc] Re: Tunneling and Transition Drafts JORDI PALET MARTINEZ
- Re: [v6tc] Re: Tunneling and Transition Drafts Jeroen Massar
- Re: [v6tc] Re: Tunneling and Transition Drafts Vladimir Kotal
- Re: [v6tc] Re: Tunneling and Transition Drafts Jerome Durand
- Re: [v6tc] Re: Tunneling and Transition Drafts Jeroen Massar
- Re: [v6tc] Re: Tunneling and Transition Drafts JORDI PALET MARTINEZ
- Re: [v6tc] Re: Tunneling and Transition Drafts Jeroen Massar
- Re: [v6tc] Re: Tunneling and Transition Drafts JORDI PALET MARTINEZ
- Re: [v6tc] Re: Tunneling and Transition Drafts W. Mark Townsley
- Re: [v6tc] Re: Tunneling and Transition Drafts Jeroen Massar
- Re: [v6tc] Re: Tunneling and Transition Drafts W. Mark Townsley
- Re: [v6tc] Re: Tunneling and Transition Drafts Francis Dupont
- Re: [v6tc] Re: Tunneling and Transition Drafts Francis Dupont
- Re: [v6tc] Re: Tunneling and Transition Drafts Francis Dupont
- Re: [v6tc] Re: Tunneling and Transition Drafts Jeroen Massar
- [v6tc] Let the market decide or not: L2TP and/or … Alain Durand
- Re: [v6tc] Re: Tunneling and Transition Drafts W. Mark Townsley
- Re: [v6tc] Let the market decide or not: L2TP and… JORDI PALET MARTINEZ
- Re: [v6tc] Re: Tunneling and Transition Drafts JORDI PALET MARTINEZ
- Re: [v6tc] Let the market decide or not: L2TP and… W. Mark Townsley
- l2tp support on OS's Re: [v6tc] Re: Tunneling and… Jeroen Massar
- Re: [v6tc] Let the market decide or not: L2TP and… Alain Durand
- Re: [v6tc] Let the market decide or not: L2TP and… Pekka Savola
- Re: [v6tc] Let the market decide or not: L2TP and… Francis Dupont
- Re: l2tp support on OS's Re: [v6tc] Re: Tunneling… JORDI PALET MARTINEZ
- Re: l2tp support on OS's Re: [v6tc] Re: Tunneling… Jeroen Massar
- Re: l2tp support on OS's Re: [v6tc] Re: Tunneling… W. Mark Townsley
- Re: l2tp support on OS's Re: [v6tc] Re: Tunneling… Francis Dupont
- Re: [v6tc] Let the market decide or not: L2TP and… Jerome Durand
- Re: [v6tc] Let the market decide or not: L2TP and… Jerome Durand
- Re: [v6tc] Re: Tunneling and Transition Drafts Tim Chown
- Re: [v6tc] Let the market decide or not: L2TP and… Pekka Savola
- Re: [v6tc] Re: Tunneling and Transition Drafts Fred Baker
- Re: [v6tc] Re: Tunneling and Transition Drafts Jeroen Massar
- Re: [v6tc] Re: Tunneling and Transition Drafts Fred Baker
- Re: [v6tc] Re: Tunneling and Transition Drafts Jeroen Massar
- Re: [v6tc] Re: Tunneling and Transition Drafts Jeroen Massar
- Re: [v6tc] Re: Tunneling and Transition Drafts Tim Chown
- Re: [v6tc] Re: Tunneling and Transition Drafts Fred Baker
- Re: [v6tc] Re: Tunneling and Transition Drafts Ronald.vanderPol
- Re: [v6tc] Re: Tunneling and Transition Drafts Ronald.vanderPol