Re: [v4v6interim] Potential interoperability issue
"Eric Vyncke (evyncke)" <evyncke@cisco.com> Fri, 03 October 2008 14:49 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 B574B3A693B; Fri, 3 Oct 2008 07:49:16 -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 CF7083A693B for <v4v6interim@core3.amsl.com>; Fri, 3 Oct 2008 07:49:15 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -5.547
X-Spam-Level:
X-Spam-Status: No, score=-5.547 tagged_above=-999 required=5 tests=[AWL=1.052, 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 PlYqI5x9niCY for <v4v6interim@core3.amsl.com>; Fri, 3 Oct 2008 07:49:15 -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 7986E3A6820 for <v4v6interim@ietf.org>; Fri, 3 Oct 2008 07:49:14 -0700 (PDT)
X-IronPort-AV: E=Sophos;i="4.33,356,1220227200"; d="scan'208";a="21573820"
Received: from ams-dkim-1.cisco.com ([144.254.224.138]) by ams-iport-1.cisco.com with ESMTP; 03 Oct 2008 14:49:09 +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 m93En9jp017112; Fri, 3 Oct 2008 16:49:09 +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 m93En90C002115; Fri, 3 Oct 2008 14:49:09 GMT
Received: from xmb-ams-33a.cisco.com ([144.254.231.85]) by xbh-ams-332.emea.cisco.com with Microsoft SMTPSVC(6.0.3790.1830); Fri, 3 Oct 2008 16:49:08 +0200
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Date: Fri, 03 Oct 2008 16:46:00 +0200
Message-ID: <CE2BF2A7B1008C459FD7978065C6ECE0079493AC@xmb-ams-33a.emea.cisco.com>
In-Reply-To: <3127D92C-CADA-4A3C-8C10-5A7194F4B3CD@apple.com>
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
Thread-Topic: [v4v6interim] Potential interoperability issue
Thread-Index: Ackkt5OsAbhCRIJoTOGjwHwnT2WrhQArrr1A
References: <E0F13238-A5C2-4BEE-BE28-7FFCFEFB3FDC@cisco.com> <3127D92C-CADA-4A3C-8C10-5A7194F4B3CD@apple.com>
From: "Eric Vyncke (evyncke)" <evyncke@cisco.com>
To: james woodyatt <jhw@apple.com>, v4v6interim@ietf.org
X-OriginalArrivalTime: 03 Oct 2008 14:49:08.0921 (UTC) FILETIME=[30E91290:01C92567]
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; l=828; t=1223045349; x=1223909349; c=relaxed/simple; s=amsdkim1002; h=Content-Type:From:Subject:Content-Transfer-Encoding:MIME-Version; d=cisco.com; i=evyncke@cisco.com; z=From:=20=22Eric=20Vyncke=20(evyncke)=22=20<evyncke@cisco.c om> |Subject:=20RE=3A=20[v4v6interim]=20Potential=20interoperab ility=20issue |Sender:=20; bh=FMUdcxnJXLM8j972m2eHe9iyn4bOxAGKc+fjwECzom4=; b=psZTK4a6dLRsg4nixwCI0nDwuFURWfIIabHLLuO6UznxjziwJKUoGLap5u U7Ux4/OH9Gttii9w6zH9IolOAnaRIo51yEQTIIBIbNdkS0u9y1Xet1GbZCEo btj3NY554Z;
Authentication-Results: ams-dkim-1; header.From=evyncke@cisco.com; dkim=pass ( sig from cisco.com/amsdkim1002 verified; );
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-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
Sender: v4v6interim-bounces@ietf.org
Errors-To: v4v6interim-bounces@ietf.org
> > > 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. > > I would agree that this is the simplest way to handle SMTP servers. Agreed as well. A proxy approach is always better (predictable, traceable) but then you need to proxy/intercept the DNS request for the MX record and change it on the fly. Moreover, AFAIK, the optional IP address in the HELO message is just 'for information' only. It is mainly used in the Received: headers which are used for debugging (and can easily be forged as they are not part of the DKIM signatire). -éric _______________________________________________ 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