IETF Logo Mail Archive

Re: [v4v6interim] Potential interoperability issue

Iljitsch van Beijnum <iljitsch@muada.com> Sat, 04 October 2008 07:48 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 0D37C3A69D0; Sat, 4 Oct 2008 00:48:50 -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 0E6123A69D0 for <v4v6interim@core3.amsl.com>; Sat, 4 Oct 2008 00:48:49 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.53
X-Spam-Level:
X-Spam-Status: No, score=-1.53 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, DATE_IN_PAST_06_12=1.069]
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 u7tQ+zuFyzLU for <v4v6interim@core3.amsl.com>; Sat, 4 Oct 2008 00:48:48 -0700 (PDT)
Received: from sequoia.muada.com (unknown [IPv6:2001:1af8:2:5::2]) by core3.amsl.com (Postfix) with ESMTP id 24B5A3A6849 for <v4v6interim@ietf.org>; Sat, 4 Oct 2008 00:48:47 -0700 (PDT)
Received: from [10.0.1.3] (82-192-90-29.leasedsl.net [82.192.90.29] (may be forged)) (authenticated bits=0) by sequoia.muada.com (8.13.3/8.13.3) with ESMTP id m947meKK028377 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NO); Sat, 4 Oct 2008 09:48:42 +0200 (CEST) (envelope-from iljitsch@muada.com)
Message-Id: <4E6509A8-CE7E-4807-ABC3-C5A705676B7C@muada.com>
From: Iljitsch van Beijnum <iljitsch@muada.com>
To: Fred Baker <fred@cisco.com>
In-Reply-To: <E0F13238-A5C2-4BEE-BE28-7FFCFEFB3FDC@cisco.com>
Mime-Version: 1.0 (Apple Message framework v929.2)
Date: Sat, 04 Oct 2008 00:17:38 +0200
References: <E0F13238-A5C2-4BEE-BE28-7FFCFEFB3FDC@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 2 okt 2008, at 19:31, Fred Baker wrote:

>> Dumb question from personal ignorance. SMTP opens with a HELO or  
>> EHLO that has the IP address of the MTA in it.

[...]

> That either calls for an ALG or appropriate code in the servers that  
> can deal with an <> address even when the server doesn't have such  
> an address. The simplest resolution might be to have the MTA have a  
> leg in the IPv6 world and one in the IPv4 world.

Right. I don't think we should create trouble where none exists in  
practice. Running an SMTP server behind a translator is not a good  
idea; using a dual stack SMTP server as a forwarder makes much more  
sense.

_______________________________________________
v4v6interim mailing list
v4v6interim@ietf.org
https://www.ietf.org/mailman/listinfo/v4v6interim

v2.29.0 | Report a Bug | By Email | System Status