IETF Logo Mail Archive

Re: [ftpext] Last Call: <draft-ietf-ftpext2-hosts-02.txt> (File Transfer Protocol HOST Command for Virtual Hosts) to Proposed Standard

Robert McMurray <robmcm@microsoft.com> Fri, 24 June 2011 19:08 UTC

Return-Path: <robmcm@microsoft.com>
X-Original-To: ftpext@ietfa.amsl.com
Delivered-To: ftpext@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 2845011E80FB; Fri, 24 Jun 2011 12:08:24 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.984
X-Spam-Level:
X-Spam-Status: No, score=-6.984 tagged_above=-999 required=5 tests=[AWL=0.483, BAYES_00=-2.599, RCVD_IN_DNSWL_HI=-8, UNRESOLVED_TEMPLATE=3.132]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 8NHpbMcXK8ze; Fri, 24 Jun 2011 12:08:23 -0700 (PDT)
Received: from smtp.microsoft.com (smtp.microsoft.com [131.107.115.214]) by ietfa.amsl.com (Postfix) with ESMTP id 5DB4711E80F1; Fri, 24 Jun 2011 12:08:23 -0700 (PDT)
Received: from TK5EX14HUBC105.redmond.corp.microsoft.com (157.54.80.48) by TK5-EXGWY-E803.partners.extranet.microsoft.com (10.251.56.169) with Microsoft SMTP Server (TLS) id 8.2.176.0; Fri, 24 Jun 2011 12:08:23 -0700
Received: from AM1EHSOBE006.bigfish.com (157.54.51.112) by mail.microsoft.com (157.54.80.48) with Microsoft SMTP Server (TLS) id 14.1.289.8; Fri, 24 Jun 2011 12:08:22 -0700
Received: from mail93-am1-R.bigfish.com (10.3.201.246) by AM1EHSOBE006.bigfish.com (10.3.204.26) with Microsoft SMTP Server id 14.1.225.22; Fri, 24 Jun 2011 19:08:20 +0000
Received: from mail93-am1 (localhost.localdomain [127.0.0.1]) by mail93-am1-R.bigfish.com (Postfix) with ESMTP id 4CE7B17980DB; Fri, 24 Jun 2011 19:08:20 +0000 (UTC)
X-SpamScore: -35
X-BigFish: PS-35(zz9371M111aL4015L542Mzz1202h1082kzz1033IL8275bh8275dhz31h2a8h668h839h61h)
X-Spam-TCS-SCL: 0:0
X-Forefront-Antispam-Report: CIP:157.55.61.146; KIP:(null); UIP:(null); IPV:SKI; H:CH1PRD0302HT006.namprd03.prod.outlook.com; R:internal; EFV:INT
Received-SPF: softfail (mail93-am1: transitioning domain of microsoft.com does not designate 157.55.61.146 as permitted sender) client-ip=157.55.61.146; envelope-from=robmcm@microsoft.com; helo=CH1PRD0302HT006.namprd03.prod.outlook.com ; .outlook.com ;
Received: from mail93-am1 (localhost.localdomain [127.0.0.1]) by mail93-am1 (MessageSwitch) id 130894250069656_30765; Fri, 24 Jun 2011 19:08:20 +0000 (UTC)
Received: from AM1EHSMHS018.bigfish.com (unknown [10.3.201.253]) by mail93-am1.bigfish.com (Postfix) with ESMTP id 02A40F8804B; Fri, 24 Jun 2011 19:08:20 +0000 (UTC)
Received: from CH1PRD0302HT006.namprd03.prod.outlook.com (157.55.61.146) by AM1EHSMHS018.bigfish.com (10.3.206.21) with Microsoft SMTP Server (TLS) id 14.1.225.22; Fri, 24 Jun 2011 19:08:20 +0000
Received: from CH1PRD0302MB131.namprd03.prod.outlook.com ([169.254.11.234]) by CH1PRD0302HT006.namprd03.prod.outlook.com ([10.28.29.125]) with mapi id 14.01.0225.056; Fri, 24 Jun 2011 19:08:18 +0000
From: Robert McMurray <robmcm@microsoft.com>
To: Mykyta Yevstifeyev <evnikita2@gmail.com>, "ietf@ietf.org" <ietf@ietf.org>, "ftpext@ietf.org" <ftpext@ietf.org>
Thread-Topic: [ftpext] Last Call: <draft-ietf-ftpext2-hosts-02.txt> (File Transfer Protocol HOST Command for Virtual Hosts) to Proposed Standard
Thread-Index: AQHMMqEmcdEZfuFND0GouWGSZJApmpTM3a+w
Date: Fri, 24 Jun 2011 19:08:18 +0000
Message-ID: <01AA9EC92749BF4894AC2B3039EA4A2C1949D19E@CH1PRD0302MB131.namprd03.prod.outlook.com>
References: <20110616130503.4854.51928.idtracker@ietfa.amsl.com> <4E04C0CE.1030807@gmail.com>
In-Reply-To: <4E04C0CE.1030807@gmail.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [10.28.29.74]
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-OrganizationHeadersPreserved: CH1PRD0302HT006.namprd03.prod.outlook.com
X-FOPE-CONNECTOR: Id%0$Dn%*$RO%0$TLS%0$FQDN%$TlsDn%
X-FOPE-CONNECTOR: Id%59$Dn%GMAIL.COM$RO%2$TLS%6$FQDN%131.107.125.5$TlsDn%
X-FOPE-CONNECTOR: Id%59$Dn%IETF.ORG$RO%2$TLS%6$FQDN%131.107.125.5$TlsDn%
X-OriginatorOrg: microsoft.com
X-CrossPremisesHeadersPromoted: TK5EX14HUBC105.redmond.corp.microsoft.com
X-CrossPremisesHeadersFiltered: TK5EX14HUBC105.redmond.corp.microsoft.com
Subject: Re: [ftpext] Last Call: <draft-ietf-ftpext2-hosts-02.txt> (File Transfer Protocol HOST Command for Virtual Hosts) to Proposed Standard
X-BeenThere: ftpext@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: <ftpext.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/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: Fri, 24 Jun 2011 19:08:24 -0000

Thanks, Mykyta.

Section 3.3 already addresses that scenario in the second paragraph - and the server behaviors are exactly what you were suggesting:

   As discussed in section 3 of this document, if a HOST command is sent
   after a user has been authenticated the server SHOULD do one of the
   following:

   a.  Send a 503 reply for an invalid sequence of commands.

   b.  Treat the HOST command as though a REIN command was sent and
       reset the user-PI to the state that existed after the previous
       HOST command was sent and before the user had been authenticated,
       and then return the appropriate reply for the HOST command.

Thanks again!

Robert McMurray

-----Original Message-----
From: Mykyta Yevstifeyev [mailto:evnikita2@gmail.com] 
Sent: Friday, June 24, 2011 9:53 AM
To: ietf@ietf.org; ftpext@ietf.org
Subject: Re: [ftpext] Last Call: <draft-ietf-ftpext2-hosts-02.txt> (File Transfer Protocol HOST Command for Virtual Hosts) to Proposed Standard

Hello,

This document is well written; I'm strongly for its publication on Standards Track.  I have an only remark.  This document doesn't seem to mention what is the behavior of the server if HOST command is sent after one HOST has already been sent.  Eg.

C> HOST example.com
S> 220 Host OK
C> USER foo
S> 331 Specify password
C> PASS bar
S> 230 Logged in
C> HOST example.org
S> ????

I suppose the server may treat this as REIN and then switching to specified host, if the user is authenticated, and just switch to such host if the user isn't already logged in.  Another option is sending 503 reply, as invalid sequence of commands.

Thanks,
Mykyta Yevstifeyev

v2.23.0 | Report a Bug | By Email