IETF Logo Mail Archive

[v4v6interim] Potential interoperability issue

Fred Baker <fred@cisco.com> Thu, 02 October 2008 17:31 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 AFC8328C172; Thu, 2 Oct 2008 10:31: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 0EF0C28C0ED for <v4v6interim@core3.amsl.com>; Thu, 2 Oct 2008 10:31:16 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -106.528
X-Spam-Level:
X-Spam-Status: No, score=-106.528 tagged_above=-999 required=5 tests=[AWL=0.071, 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 M6IJa+uJVwkY for <v4v6interim@core3.amsl.com>; Thu, 2 Oct 2008 10:31:15 -0700 (PDT)
Received: from sj-iport-4.cisco.com (sj-iport-4.cisco.com [171.68.10.86]) by core3.amsl.com (Postfix) with ESMTP id 3430E28C172 for <v4v6interim@ietf.org>; Thu, 2 Oct 2008 10:31:15 -0700 (PDT)
X-IronPort-AV: E=Sophos;i="4.33,352,1220227200"; d="scan'208";a="22496750"
Received: from sj-dkim-4.cisco.com ([171.71.179.196]) by sj-iport-4.cisco.com with ESMTP; 02 Oct 2008 17:31:23 +0000
Received: from sj-core-1.cisco.com (sj-core-1.cisco.com [171.71.177.237]) by sj-dkim-4.cisco.com (8.12.11/8.12.11) with ESMTP id m92HVNKj011250 for <v4v6interim@ietf.org>; Thu, 2 Oct 2008 10:31:23 -0700
Received: from xbh-sjc-231.amer.cisco.com (xbh-sjc-231.cisco.com [128.107.191.100]) by sj-core-1.cisco.com (8.13.8/8.13.8) with ESMTP id m92HVMQl024370 for <v4v6interim@ietf.org>; Thu, 2 Oct 2008 17:31:23 GMT
Received: from xfe-sjc-212.amer.cisco.com ([171.70.151.187]) by xbh-sjc-231.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.1830); Thu, 2 Oct 2008 10:31:21 -0700
Received: from [192.168.3.109] ([10.21.75.252]) by xfe-sjc-212.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.1830); Thu, 2 Oct 2008 10:31:20 -0700
Message-Id: <E0F13238-A5C2-4BEE-BE28-7FFCFEFB3FDC@cisco.com>
From: Fred Baker <fred@cisco.com>
To: Cullen Jennings <fluffy@cisco.com>
Mime-Version: 1.0 (Apple Message framework v929.2)
Date: Thu, 02 Oct 2008 13:31:19 -0400
X-Mailer: Apple Mail (2.929.2)
X-OriginalArrivalTime: 02 Oct 2008 17:31:20.0902 (UTC) FILETIME=[AF35C660:01C924B4]
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; l=854; t=1222968683; x=1223832683; c=relaxed/simple; s=sjdkim4002; h=Content-Type:From:Subject:Content-Transfer-Encoding:MIME-Version; d=cisco.com; i=fred@cisco.com; z=From:=20Fred=20Baker=20<fred@cisco.com> |Subject:=20Potential=20interoperability=20issue |Sender:=20; bh=773c8CSJj5XltZfbMv15StOexeUbZg9ew/K3yPEo5yQ=; b=B9Qvc70pjws7UD9EydbIrSt5lFejMATZl6R4B+WttoCA6rk/0p38KpeQMM 9g6J2pImHUQ9nlvfeOHxyx3x/FT5CmZ6Y19HPlJJb8bp1axhPjT+jxY9G0YT H9aY0BXdBI;
Authentication-Results: sj-dkim-4; header.From=fred@cisco.com; dkim=pass ( sig from cisco.com/sjdkim4002 verified; );
Cc: v4v6interim@ietf.org
Subject: [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

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.

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. 
_______________________________________________
v4v6interim mailing list
v4v6interim@ietf.org
https://www.ietf.org/mailman/listinfo/v4v6interim

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