Re: [v4v6interim] "IPv4->IPv6 is hard"
Mark Townsley <townsley@cisco.com> Mon, 20 October 2008 07:38 UTC
Return-Path: <v4v6interim-bounces@ietf.org>
X-Original-To: v4v6interim-archive@ietf.org
Delivered-To: ietfarch-v4v6interim-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 7081C3A68F3; Mon, 20 Oct 2008 00:38:21 -0700 (PDT)
X-Original-To: v4v6interim@core3.amsl.com
Delivered-To: v4v6interim@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 137D73A68DB for <v4v6interim@core3.amsl.com>; Mon, 20 Oct 2008 00:38:21 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.531
X-Spam-Level:
X-Spam-Status: No, score=-6.531 tagged_above=-999 required=5 tests=[AWL=0.068, BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id BOP8Z0GtIxqV for <v4v6interim@core3.amsl.com>; Mon, 20 Oct 2008 00:38:20 -0700 (PDT)
Received: from ams-iport-1.cisco.com (ams-iport-1.cisco.com [144.254.224.140]) by core3.amsl.com (Postfix) with ESMTP id A88B03A6900 for <v4v6interim@ietf.org>; Mon, 20 Oct 2008 00:38:19 -0700 (PDT)
X-IronPort-AV: E=Sophos;i="4.33,450,1220227200"; d="scan'208";a="23085303"
Received: from ams-dkim-1.cisco.com ([144.254.224.138]) by ams-iport-1.cisco.com with ESMTP; 20 Oct 2008 07:39:29 +0000
Received: from ams-core-1.cisco.com (ams-core-1.cisco.com [144.254.224.150]) by ams-dkim-1.cisco.com (8.12.11/8.12.11) with ESMTP id m9K7dTg5027587; Mon, 20 Oct 2008 09:39:29 +0200
Received: from xbh-ams-332.emea.cisco.com (xbh-ams-332.cisco.com [144.254.231.87]) by ams-core-1.cisco.com (8.13.8/8.13.8) with ESMTP id m9K7dTh6013857; Mon, 20 Oct 2008 07:39:29 GMT
Received: from xfe-ams-332.cisco.com ([144.254.231.73]) by xbh-ams-332.emea.cisco.com with Microsoft SMTPSVC(6.0.3790.1830); Mon, 20 Oct 2008 09:39:29 +0200
Received: from ams-townsley-8713.cisco.com ([10.55.233.228]) by xfe-ams-332.cisco.com with Microsoft SMTPSVC(6.0.3790.1830); Mon, 20 Oct 2008 09:39:28 +0200
Message-ID: <48FC3561.3040005@cisco.com>
Date: Mon, 20 Oct 2008 09:38:09 +0200
From: Mark Townsley <townsley@cisco.com>
User-Agent: Thunderbird 2.0.0.17 (Macintosh/20080914)
MIME-Version: 1.0
To: Fred Baker <fred@cisco.com>
References: <B4A9FAB9-F39D-42AA-BE3B-AF6A3C48CC93@cisco.com> <4391DDA1-6432-4DCD-8A38-F351C68058B5@muada.com> <48F8A9F9.6000505@sri.com> <48F8BC64.10608@psg.com> <48F8D984.90901@sri.com> <0F936B42-2FB9-413B-ADDF-BE881730F95E@cisco.com>
In-Reply-To: <0F936B42-2FB9-413B-ADDF-BE881730F95E@cisco.com>
X-OriginalArrivalTime: 20 Oct 2008 07:39:29.0028 (UTC) FILETIME=[FBEB5440:01C93286]
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; l=2188; t=1224488369; x=1225352369; c=relaxed/simple; s=amsdkim1002; h=Content-Type:From:Subject:Content-Transfer-Encoding:MIME-Version; d=cisco.com; i=townsley@cisco.com; z=From:=20Mark=20Townsley=20<townsley@cisco.com> |Subject:=20Re=3A=20[v4v6interim]=20=22IPv4->IPv6=20is=20ha rd=22 |Sender:=20; bh=POV0F23msJFqMNmBFJn+BJGuwsr3oKnE8ADgL4y8QQ8=; b=QecRWRZ6o18yB3keDmsrnZG5gwulb3FRf9yIK1fRKOJasuNOfnK3irNDG8 C83OAdhSSJT53Y1lylJzviQ28ydt8Zk1v+0/POG9txUirOm4/Q2V4dwh9Nob jZiSIR9Wph;
Authentication-Results: ams-dkim-1; header.From=townsley@cisco.com; dkim=pass ( sig from cisco.com/amsdkim1002 verified; );
Cc: v4v6interim@ietf.org
Subject: Re: [v4v6interim] "IPv4->IPv6 is hard"
X-BeenThere: v4v6interim@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Discussion of coexistence topics for the 01-Oct-2008 v4-v6 coexistence interim meeting <v4v6interim.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/v4v6interim>, <mailto:v4v6interim-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/pipermail/v4v6interim>
List-Post: <mailto:v4v6interim@ietf.org>
List-Help: <mailto:v4v6interim-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/v4v6interim>, <mailto:v4v6interim-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 7bit
Content-Type: text/plain; charset="us-ascii"; Format="flowed"
Sender: v4v6interim-bounces@ietf.org
Errors-To: v4v6interim-bounces@ietf.org
Fred Baker wrote: > > On Oct 17, 2008, at 11:29 AM, Ed Jankiewicz wrote: > >> yup. I really meant to say "right now" and even for the near future, >> don't we still expect most servers/applications to be dual-stack >> rather than IPv6-only? My point was there are more pressing problems >> to solve, while it would be nice for all variations to work, some can >> be deferred. > > One has to define "dual stack". > > Everything that runs on my Mac is potentially dual stack, in the sense > that the code is there to run both IPv4 and IPv6. Present it with an > IPv4 network, it does so. Present it with an IPv6 network, it does so. > > It the thing it needs to talk with is IPvX and it only has IPvY > routing, however, it can't get there. From my home I can't access > ipv6.google.com because no ISP in Santa Barbara County runs IPv6. > > The DS-Lite model says that I should set up a tunnel across the IPv4 > infrastructure, whether from my host or from my router; 6to4 is > similar, as are others. Actually, the DS-Lite model targets setting up a tunnel to cross IPv6-only infrastructure - so, not very useful for you situation with an ISP not delivering IPv6. - Mark > > The translation model says that the host should use the network > available to it and something in the network should change the > protocol when and where it must. > > My personal preference is for dual stack deployment, and where > necessary to change as little as possible, as the changes will outlive > the need for them by decades. Asking the host to build tunnels is an > example of such a change. Under the ISP's control or at least in > collusion with it, I can see building tunnels. But even there, as the > ISPs deploy IPv6 that becomes a change that will outlive the need for > it. That's why I'm working on translation - enable the network > administration to install what it needs to when it needs it, and > enable it to remove it when the need goes away. > > my two yen > > _______________________________________________ > v4v6interim mailing list > v4v6interim@ietf.org > https://www.ietf.org/mailman/listinfo/v4v6interim > _______________________________________________ v4v6interim mailing list v4v6interim@ietf.org https://www.ietf.org/mailman/listinfo/v4v6interim
- [v4v6interim] "IPv4->IPv6 is hard" Fred Baker
- Re: [v4v6interim] "IPv4->IPv6 is hard" Mark Townsley
- Re: [v4v6interim] "IPv4->IPv6 is hard" Fred Baker
- Re: [v4v6interim] "IPv4->IPv6 is hard" Iljitsch van Beijnum
- Re: [v4v6interim] "IPv4->IPv6 is hard" Ed Jankiewicz
- Re: [v4v6interim] "IPv4->IPv6 is hard" Fred Baker
- Re: [v4v6interim] "IPv4->IPv6 is hard" Randy Bush
- Re: [v4v6interim] "IPv4->IPv6 is hard" Ed Jankiewicz
- Re: [v4v6interim] "IPv4->IPv6 is hard" Randy Bush
- Re: [v4v6interim] "IPv4->IPv6 is hard" Ed Jankiewicz
- Re: [v4v6interim] "IPv4->IPv6 is hard" Eric Vyncke (evyncke)
- Re: [v4v6interim] "IPv4->IPv6 is hard" Fred Baker
- Re: [v4v6interim] "IPv4->IPv6 is hard" Fred Baker
- Re: [v4v6interim] "IPv4->IPv6 is hard" Xing Li
- Re: [v4v6interim] "IPv4->IPv6 is hard" marcelo bagnulo braun
- Re: [v4v6interim] "IPv4->IPv6 is hard" Fred Baker
- Re: [v4v6interim] "IPv4->IPv6 is hard" Xing Li
- Re: [v4v6interim] "IPv4->IPv6 is hard" Xing Li
- Re: [v4v6interim] "IPv4->IPv6 is hard" marcelo bagnulo braun
- Re: [v4v6interim] "IPv4->IPv6 is hard" Mark Townsley
- Re: [v4v6interim] "IPv4->IPv6 is hard" Rémi Després
- Re: [v4v6interim] "IPv4->IPv6 is hard" Xing Li