Re: [v4v6interim] Potential interoperability issue
james woodyatt <jhw@apple.com> Thu, 02 October 2008 17:51 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 6B3E53A6A0C; Thu, 2 Oct 2008 10:51:26 -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 AB8503A6A77 for <v4v6interim@core3.amsl.com>; Thu, 2 Oct 2008 10:51:25 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -106.599
X-Spam-Level:
X-Spam-Status: No, score=-106.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4, USER_IN_WHITELIST=-100]
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 b+JSr+7JLaC6 for <v4v6interim@core3.amsl.com>; Thu, 2 Oct 2008 10:51:21 -0700 (PDT)
Received: from mail-out4.apple.com (mail-out4.apple.com [17.254.13.23]) by core3.amsl.com (Postfix) with ESMTP id D5A3E3A6A0C for <v4v6interim@ietf.org>; Thu, 2 Oct 2008 10:51:21 -0700 (PDT)
Received: from relay12.apple.com (relay12.apple.com [17.128.113.53]) by mail-out4.apple.com (Postfix) with ESMTP id 2F1753FD1451 for <v4v6interim@ietf.org>; Thu, 2 Oct 2008 10:51:44 -0700 (PDT)
Received: from relay12.apple.com (unknown [127.0.0.1]) by relay12.apple.com (Symantec Mail Security) with ESMTP id 1B244464003 for <v4v6interim@ietf.org>; Thu, 2 Oct 2008 10:51:44 -0700 (PDT)
X-AuditID: 11807135-ab983bb000000d0e-1e-48e50a2fec6b
Received: from il0602f-dhcp175.apple.com (il0602f-dhcp175.apple.com [17.206.50.175]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (No client certificate requested) by relay12.apple.com (Apple SCV relay) with ESMTP id EA15B420003 for <v4v6interim@ietf.org>; Thu, 2 Oct 2008 10:51:43 -0700 (PDT)
Message-Id: <3127D92C-CADA-4A3C-8C10-5A7194F4B3CD@apple.com>
From: james woodyatt <jhw@apple.com>
To: v4v6interim@ietf.org
In-Reply-To: <E0F13238-A5C2-4BEE-BE28-7FFCFEFB3FDC@cisco.com>
Mime-Version: 1.0 (Apple Message framework v929.2)
Date: Thu, 02 Oct 2008 10:51:43 -0700
References: <E0F13238-A5C2-4BEE-BE28-7FFCFEFB3FDC@cisco.com>
X-Mailer: Apple Mail (2.929.2)
X-Brightmail-Tracker: AAAAAA==
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 Oct 2, 2008, at 10:31, Fred Baker wrote: > > Sitting in your discussion of applications that may have issues > through a translator. In the chat room, I asked: > >> Dumb question from personal ignorance. SMTP opens with a HELO or >> EHLO that has the IP address of the MTA in it. Does SMTP treat that >> as a character string, or does it interpret the address? If it >> interprets the address, it may have the same issue as FTP in a 6to4 >> environment > > and James Woodyatt replied > >> Some things interpret it as an address, e.g. rule processing >> engines for deciding whether to require TLS. Or authentication. The EHLO message has a domain name. In SMTP, the Domain grammar production includes a special case allowing for an IP address literal instead of a FQDN. This domain name in the EHLO message is sometimes used to make decisions about TLS and AUTH requirements. So, too, can the IP address of the connecting client be used for such decisions. Whether an ALG is required to cope with this is a question I'm not prepared to answer. > 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. -- james woodyatt <jhw@apple.com> member of technical staff, communications engineering _______________________________________________ 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