Re: [v4v6interim] Potential interoperability issue
Iljitsch van Beijnum <iljitsch@muada.com> Mon, 06 October 2008 08:35 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 7A59B3A6831; Mon, 6 Oct 2008 01:35:52 -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 B81403A67C1 for <v4v6interim@core3.amsl.com>; Mon, 6 Oct 2008 01:35:50 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.065
X-Spam-Level:
X-Spam-Status: No, score=-2.065 tagged_above=-999 required=5 tests=[AWL=0.535, BAYES_00=-2.599]
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 vyFTs+srLILx for <v4v6interim@core3.amsl.com>; Mon, 6 Oct 2008 01:35:50 -0700 (PDT)
Received: from sequoia.muada.com (unknown [IPv6:2001:1af8:2:5::2]) by core3.amsl.com (Postfix) with ESMTP id BB59F3A692F for <v4v6interim@ietf.org>; Mon, 6 Oct 2008 01:35:49 -0700 (PDT)
Received: from nirrti.muada.com (nirrti.muada.com [82.192.90.28]) (authenticated bits=0) by sequoia.muada.com (8.13.3/8.13.3) with ESMTP id m968ZotJ072217 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NO); Mon, 6 Oct 2008 10:35:50 +0200 (CEST) (envelope-from iljitsch@muada.com)
Message-Id: <AB3F6653-44B6-4C58-858B-04D3DCBD4F12@muada.com>
From: Iljitsch van Beijnum <iljitsch@muada.com>
To: Fred Baker <fred@cisco.com>
In-Reply-To: <74408D36-502A-439F-A097-8569C4B8DE06@cisco.com>
Mime-Version: 1.0 (Apple Message framework v929.2)
Date: Mon, 06 Oct 2008 10:36:00 +0200
References: <E0F13238-A5C2-4BEE-BE28-7FFCFEFB3FDC@cisco.com> <4E6509A8-CE7E-4807-ABC3-C5A705676B7C@muada.com> <74408D36-502A-439F-A097-8569C4B8DE06@cisco.com>
X-Mailer: Apple Mail (2.929.2)
Cc: v4v6interim@ietf.org
Subject: Re: [v4v6interim] Potential interoperability issue
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"; DelSp="yes"
Sender: v4v6interim-bounces@ietf.org
Errors-To: v4v6interim-bounces@ietf.org
On 4 okt 2008, at 22:37, Fred Baker wrote: >> using a dual stack SMTP server as a forwarder makes much more sense. > Gee, you make it sound as if I were arguing against dual stack. I'm > merely noting that dual stack isn't being deployed at the rate one > would hope for and that my customers are looking for a translation > solution. The thing that we have to make explicit is that it's necessary to deploy the right solution to a given problem, one size never fits all. Dual stack is not a good solution for clients for two reasons: it requires running both IP versions throughout a network, which increases cost and complexity, and it uses up just as many addresses as just running IPv4. But for servers, dual stack is the best possible solution, because it's way simpler than the alternatives as receiving incoming sessions through translation is a big hurdle and the address use and network complexity aren't as bad because the number of servers and presumably, the number of places they're present are limited. In the case of SMTP it's also easy to simply put a dual stack server in the path if you have an IPv6 server. _______________________________________________ v4v6interim mailing list v4v6interim@ietf.org https://www.ietf.org/mailman/listinfo/v4v6interim
- [v4v6interim] Potential interoperability issue Fred Baker
- Re: [v4v6interim] Potential interoperability issue james woodyatt
- Re: [v4v6interim] Potential interoperability issue Brian E Carpenter
- Re: [v4v6interim] Potential interoperability issue Eric Vyncke (evyncke)
- Re: [v4v6interim] Potential interoperability issue Iljitsch van Beijnum
- Re: [v4v6interim] Potential interoperability issue Fred Baker
- Re: [v4v6interim] Potential interoperability issue Iljitsch van Beijnum
- Re: [v4v6interim] Potential interoperability issue Ed Koehler Jr