From ftp-wg-owner@hethmon.com Thu Jul 5 14:07:39 2001 Received: from mail.hethmon.com (mail.hethmon.com [208.171.56.195]) by ietf.org (8.9.1a/8.9.1a) with SMTP id OAA21971 for ; Thu, 5 Jul 2001 14:07:38 -0400 (EDT) Received: from mail.hethmon.com ([208.171.56.195] [208.171.56.195]) by mail.hethmon.com (Hethmon Brothers Smtpd) id 20010705131147-54520-9 ; Thu, 05 Jul 2001 13:11:48 -0500 Received: from mail3.microsoft.com ([131.107.3.123] [131.107.3.123]) by mail.hethmon.com (Hethmon Brothers Smtpd) id 20010705131143-30420-8 ; Thu, 05 Jul 2001 13:11:43 -0500 Received: from 157.54.9.101 by mail3.microsoft.com (InterScan E-Mail VirusWall NT); Thu, 05 Jul 2001 08:08:33 -0700 (Pacific Daylight Time) Received: from red-msg-04.redmond.corp.microsoft.com ([157.54.12.74]) by inet-imc-01.redmond.corp.microsoft.com with Microsoft SMTPSVC(5.0.2195.2966); Thu, 5 Jul 2001 08:10:52 -0700 X-MimeOLE: Produced By Microsoft Exchange V6.0.4712.0 content-class: urn:content-classes:message MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Message-ID: Thread-Topic: Ftp-WG: Re: draft-ietf-ftpext-mlst-10 comments Thread-Index: Ab+JzI3VTTu2CMcYQm6jeQtb/3kZIF7lmg0w , X-OriginalArrivalTime: 05 Jul 2001 15:10:52.0373 (UTC) FILETIME=[AE63D050:01C10564] Date: Thu, 5 Jul 2001 13:11:45 -0500 X-OldDate: Thu, 5 Jul 2001 08:10:37 -0700 Sender: ftp-wg-owner X-Listname: ftp-wg@hethmon.com Reply-To: FTPEXT Working Group From: "Bryan Starbuck" To: "FTPEXT Working Group" Subject: Ftp-WG: Re: draft-ietf-ftpext-mlst-10 comments Content-Transfer-Encoding: 8bit X-MIME-Autoconverted: from quoted-printable to 8bit by ietf.org id OAA21971 I'm the owner for the graphical FTP support in Internet Explorer and I found the same problem. I found from extensive backward compatibility tests that the server and client can't start using UTF8 by default. Therefore, I need the client and server to handshake before they can safely start using UTF8. I do this by having the server advertise that it can handle UTF8 by returning "UTF8" for the FEAT command. The client will then send "OPTS UTF8 ON". If the server returns a successful reply value, both sides know that everything from then on is in UTF8. I know that doesn't fully comply with RFC 2640 but it solves the backward compat issue. It also works well with FEAT/OPTS. I would love to hear how other people solved this problem. -Bryan (Sorry the reply is so late...) ====================================== Bryan Starbuck - BryanSt@microsoft.com Software Design Engineer Windows XP Shell -----Original Message----- From: Brad Clements [mailto:bkc@murkworks.com] Sent: Thursday, March 09, 2000 5:40 AM To: FTPEXT Working Group Subject: Ftp-WG: Re: draft-ietf-ftpext-mlst-10 comments With respect to Sergey's recent post. I can't comment on the internationalization issues. I do think that the pathname format being sent by the server, or the client, should be un-ambigious. The client should be able to tell the server "I'll accept UTF-8, I can send UTF-8" and the server should be able to say "I can send UTF-8, I can receive UTF-8". I know the LANG option was mentioned as a way to do some of this, but I think it would be good to eleminate "guess" and path-type determination based on inspection. Brad Clements, bkc@murkworks.com (315)268-1000 http://www.murkworks.com (315)268-9812 Fax netmeeting: ils://ils.murkworks.com AOL-IM: BKClements From ftp-wg-owner@hethmon.com Tue Jul 10 11:13:16 2001 Received: from mail.hethmon.com (mail.hethmon.com [208.171.56.195]) by ietf.org (8.9.1a/8.9.1a) with SMTP id LAA03074 for ; Tue, 10 Jul 2001 11:13:15 -0400 (EDT) Received: from mail.hethmon.com ([208.171.56.195] [208.171.56.195]) by mail.hethmon.com (Hethmon Brothers Smtpd) id 20010710101757-16038-9 ; Tue, 10 Jul 2001 10:17:57 -0500 Received: from e22.nc.us.ibm.com ([32.97.136.228] [32.97.136.228]) by mail.hethmon.com (Hethmon Brothers Smtpd) id 20010710101751-7598-8 ; Tue, 10 Jul 2001 10:17:53 -0500 Received: from southrelay02.raleigh.ibm.com (southrelay02.raleigh.ibm.com [9.37.3.209]) by e22.nc.us.ibm.com (8.9.3/8.9.3) with ESMTP id LAA18580; Tue, 10 Jul 2001 11:00:41 -0500 Received: from d04nm200.raleigh.ibm.com (d04nm200.raleigh.ibm.com [9.67.226.57]) by southrelay02.raleigh.ibm.com (8.11.1m3/NCO v4.96) with ESMTP id f6AFBP567572; Tue, 10 Jul 2001 11:11:25 -0400 Importance: Normal X-Mailer: Lotus Notes Release 5.0.6a January 17, 2001 Message-ID: X-MIMETrack: Serialize by Router on D04NM200/04/M/IBM(Build M9_05202001 Beta 2|May 20, 2001) at 07/10/2001 11:11:25 AM MIME-Version: 1.0 Content-type: text/plain; charset=us-ascii Date: Tue, 10 Jul 2001 10:17:55 -0500 X-OldDate: Tue, 10 Jul 2001 11:11:22 -0400 Sender: ftp-wg-owner X-Listname: ftp-wg@hethmon.com Reply-To: FTPEXT Working Group From: "Janet Wolf" To: "Bryan Starbuck" Subject: Ftp-WG: Re: draft-ietf-ftpext-mlst-10 comments Bryan, My FTP client issues FEAT during login. My client looks for both LANG and UTF8 in the FEAT reply. As you know, the LANG portion includes its current language with an asterisk (e.g., LANG en*,fr,de). My client extracts the language marked with the asterisk and sends that LANG command to the server (i.e. LANG en). At that point, per RFC 2640, the server and my client have just negotiated UTF-8 encoding of pathnames. As for my server, it always includes UTF8 and LANG en* in the FEAT reply (subject to configuration options). My server supports LANG, but the only language on offer is English. RFC 2640 says a server must support the LANG command, but it doesn't require the server to support more than one language. The point of supporting LANG in this way is to allow a client to negotiate UTF-8 encoding with my server. I am very curious where you got the idea of using OPTS UTF8 ON? Cheers, Janet C. Wolf "Bryan Starbuck" on 07/05/2001 11:10:37 AM To: "FTPEXT Working Group" , Janet Wolf/Raleigh/IBM@IBMUS, cc: Subject: RE: Ftp-WG: Re: draft-ietf-ftpext-mlst-10 comments I'm the owner for the graphical FTP support in Internet Explorer and I found the same problem. I found from extensive backward compatibility tests that the server and client can't start using UTF8 by default. Therefore, I need the client and server to handshake before they can safely start using UTF8. I do this by having the server advertise that it can handle UTF8 by returning "UTF8" for the FEAT command. The client will then send "OPTS UTF8 ON". If the server returns a successful reply value, both sides know that everything from then on is in UTF8. I know that doesn't fully comply with RFC 2640 but it solves the backward compat issue. It also works well with FEAT/OPTS. I would love to hear how other people solved this problem. -Bryan (Sorry the reply is so late...) ====================================== Bryan Starbuck - BryanSt@microsoft.com Software Design Engineer Windows XP Shell -----Original Message----- From: Brad Clements [mailto:bkc@murkworks.com] Sent: Thursday, March 09, 2000 5:40 AM To: FTPEXT Working Group Subject: Ftp-WG: Re: draft-ietf-ftpext-mlst-10 comments With respect to Sergey's recent post. I can't comment on the internationalization issues. I do think that the pathname format being sent by the server, or the client, should be un-ambigious. The client should be able to tell the server "I'll accept UTF-8, I can send UTF-8" and the server should be able to say "I can send UTF-8, I can receive UTF-8". I know the LANG option was mentioned as a way to do some of this, but I think it would be good to eleminate "guess" and path-type determination based on inspection. Brad Clements, bkc@murkworks.com (315)268-1000 http://www.murkworks.com (315)268-9812 Fax netmeeting: ils://ils.murkworks.com AOL-IM: BKClements