IETF Logo Mail Archive

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

"Dan Wing" <dwing@cisco.com> Thu, 23 December 2010 18:25 UTC

Return-Path: <dwing@cisco.com>
X-Original-To: ftpext@core3.amsl.com
Delivered-To: ftpext@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 43FF53A6858; Thu, 23 Dec 2010 10:25:01 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -110.514
X-Spam-Level:
X-Spam-Status: No, score=-110.514 tagged_above=-999 required=5 tests=[AWL=0.085, BAYES_00=-2.599, RCVD_IN_DNSWL_HI=-8, 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 gy4a6TGCz06L; Thu, 23 Dec 2010 10:25:00 -0800 (PST)
Received: from sj-iport-4.cisco.com (sj-iport-4.cisco.com [171.68.10.86]) by core3.amsl.com (Postfix) with ESMTP id 726F03A6843; Thu, 23 Dec 2010 10:25:00 -0800 (PST)
Authentication-Results: sj-iport-4.cisco.com; dkim=neutral (message not signed) header.i=none
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AgMFABciE02rR7Hu/2dsb2JhbACXN4x0c6VcmyuFSgSEZQ
X-IronPort-AV: E=Sophos;i="4.60,219,1291593600"; d="scan'208";a="237095583"
Received: from sj-core-5.cisco.com ([171.71.177.238]) by sj-iport-4.cisco.com with ESMTP; 23 Dec 2010 18:27:01 +0000
Received: from dwingWS (sjc-vpn2-687.cisco.com [10.21.114.175]) by sj-core-5.cisco.com (8.13.8/8.14.3) with ESMTP id oBNIR1ee012334; Thu, 23 Dec 2010 18:27:01 GMT
From: Dan Wing <dwing@cisco.com>
To: 'Iljitsch van Beijnum' <iljitsch@muada.com>
References: <0cac01cb58ea$32d19a60$9874cf20$@com> <9B57C850BB53634CACEC56EF4853FF65343005F2@TK5EX14MBXW601.wingroup.windeploy.ntdev.microsoft.com> <B166ACF7-FA96-4954-8411-A86BC7923A76@muada.com> <9B57C850BB53634CACEC56EF4853FF653447D195@TK5EX14MBXW604.wingroup.windeploy.ntdev.microsoft.com> <9B57C850BB53634CACEC56EF4853FF653447ECAF@TK5EX14MBXW604.wingroup.windeploy.ntdev.microsoft.com> <8B73074C-5B7E-425F-B8B2-C28757FB7CD6@muada.com> <9B57C850BB53634CACEC56EF4853FF653447F40D@TK5EX14MBXW604.wingroup.windeploy.ntdev.microsoft.com> <9B57C850BB53634CACEC56EF4853FF653447F599@TK5EX14MBXW604.wingroup.windeploy.ntdev.microsoft.com> <049901cba2cc$238f67e0$6aae37a0$@com> <101F87C4-F714-48C2-852A-67332B712DD1@muada.com>
In-Reply-To: <101F87C4-F714-48C2-852A-67332B712DD1@muada.com>
Date: Thu, 23 Dec 2010 10:27:01 -0800
Message-ID: <04a401cba2ce$fdba5180$f92ef480$@com>
MIME-Version: 1.0
Content-Type: text/plain; charset="US-ASCII"
Content-Transfer-Encoding: 7bit
X-Mailer: Microsoft Office Outlook 12.0
Thread-Index: AcuizQsxEH0fsv7gT0CgDu564FTndQAABOLw
Content-Language: en-us
Cc: draft-ietf-behave-ftp64@tools.ietf.org, ftpext@ietf.org, 'Behave WG' <behave@ietf.org>, 'Dave Thaler' <dthaler@microsoft.com>
Subject: Re: [ftpext] [BEHAVE] one week WGLC, draft-ietf-behave-ftp64-05
X-BeenThere: ftpext@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: <ftpext.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/ftpext>, <mailto:ftpext-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ftpext>
List-Post: <mailto:ftpext@ietf.org>
List-Help: <mailto:ftpext-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ftpext>, <mailto:ftpext-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 23 Dec 2010 18:25:01 -0000

> -----Original Message-----
> From: Iljitsch van Beijnum [mailto:iljitsch@muada.com]
> Sent: Thursday, December 23, 2010 10:13 AM
> To: Dan Wing
> Cc: 'Dave Thaler'; draft-ietf-behave-ftp64@tools.ietf.org;
> ftpext@ietf.org; 'Behave WG'
> Subject: Re: [BEHAVE] one week WGLC, draft-ietf-behave-ftp64-05
> 
> On 23 dec 2010, at 19:06, Dan Wing wrote:
> 
> > The best solution I see is the FTP64 ALG has to (MUST)
> > remove LANG from the server's FEAT response, and translate
> > the LANG command to NOOP and return a 5xy response to the
> > client.
> 
> 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.

-d

v2.23.0 | Report a Bug | By Email