Re: [ftpext] [BEHAVE] one week WGLC, draft-ietf-behave-ftp64-05

Iljitsch van Beijnum <> Thu, 23 December 2010 21:41 UTC

Return-Path: <>
Received: from localhost (localhost []) by (Postfix) with ESMTP id B46DA3A68B7; Thu, 23 Dec 2010 13:41:34 -0800 (PST)
X-Virus-Scanned: amavisd-new at
X-Spam-Flag: NO
X-Spam-Score: -102.6
X-Spam-Status: No, score=-102.6 tagged_above=-999 required=5 tests=[AWL=-0.000, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from ([]) by localhost ( []) (amavisd-new, port 10024) with ESMTP id 8OyXFcjZ5mXP; Thu, 23 Dec 2010 13:40:59 -0800 (PST)
Received: from (unknown [IPv6:2001:1af8:2:5::2]) by (Postfix) with ESMTP id B17343A6895; Thu, 23 Dec 2010 13:40:58 -0800 (PST)
Received: from [] ( [] (may be forged)) (authenticated bits=0) by (8.13.3/8.13.3) with ESMTP id oBNLgpE5073861 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NO); Thu, 23 Dec 2010 22:42:52 +0100 (CET) (envelope-from
Mime-Version: 1.0 (Apple Message framework v1082)
Content-Type: text/plain; charset=us-ascii
From: Iljitsch van Beijnum <>
In-Reply-To: <04a401cba2ce$fdba5180$f92ef480$@com>
Date: Thu, 23 Dec 2010 22:42:48 +0100
Content-Transfer-Encoding: quoted-printable
Message-Id: <>
References: <0cac01cb58ea$32d19a60$9874cf20$@com> <> <> <> <> <> <> <> <049901cba2cc$238f67e0$6aae37a0$@com> <> <04a401cba2ce$fdba5180$f92ef480$@com>
To: Dan Wing <>
X-Mailer: Apple Mail (2.1082)
Cc:,, 'Behave WG' <>, 'Dave Thaler' <>
Subject: Re: [ftpext] [BEHAVE] one week WGLC, draft-ietf-behave-ftp64-05
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: <>
List-Unsubscribe: <>, <>
List-Archive: <>
List-Post: <>
List-Help: <>
List-Subscribe: <>, <>
X-List-Received-Date: Thu, 23 Dec 2010 21:41:35 -0000

On 23 dec 2010, at 19:27, Dan Wing wrote:

>> But how does making the server use the default language make the user's
>> experience any better?

> The user might have to read something in the FTP server's default
> language, but it will be ASCII.  That's better than the FTP client
> potentially throwing an error.

Dave mentioned the client potentially crashing. I don't buy that. An FTP client can obviously handle ASCII if the desired LANG is not supported, so then it's going to crash when it sees the same characters when another language is negotiated but it otherwise sees the same text. It's not like 7-bit ASCII characters never occur in languages that use other scripts.

Maybe at this point in the discussion it would be good to hear from implementers. There are already tons of NAT44 FTP ALGs out there, I wonder how those solve this.