<pre>Internet Engineering Task Force (IETF)                        P. Hethmon
Request for Comments: 7151                              Hethmon Brothers
Updates: <a href="./rfc959">959</a>                                                 R. McMurray
Category: Standards Track                          Microsoft Corporation
ISSN: 2070-1721                                               March 2014


         <span class="h1">File Transfer Protocol HOST Command for Virtual Hosts</span>

Abstract

   The File Transfer Protocol, as defined in <a href="./rfc959">RFC 959</a>, does not provide a
   way for FTP clients and servers to differentiate between multiple DNS
   names that are registered for a single IP address.  This document
   defines a new FTP command that provides a mechanism for FTP clients
   and servers to identify individual virtual hosts on an FTP server.

Status of This Memo

   This is an Internet Standards Track document.

   This document is a product of the Internet Engineering Task Force
   (IETF).  It represents the consensus of the IETF community.  It has
   received public review and has been approved for publication by the
   Internet Engineering Steering Group (IESG).  Further information on
   Internet Standards is available in <a href="./rfc5741#section-2">Section&nbsp;2 of RFC 5741</a>.

   Information about the current status of this document, any errata,
   and how to provide feedback on it may be obtained at
   <a href="http://www.rfc-editor.org/info/rfc7151">http://www.rfc-editor.org/info/rfc7151</a>.

Copyright Notice

   Copyright (c) 2014 IETF Trust and the persons identified as the
   document authors.  All rights reserved.

   This document is subject to <a href="https://www.rfc-editor.org/bcp/bcp78">BCP 78</a> and the IETF Trust's Legal
   Provisions Relating to IETF Documents
   (<a href="http://trustee.ietf.org/license-info">http://trustee.ietf.org/license-info</a>) in effect on the date of
   publication of this document.  Please review these documents
   carefully, as they describe your rights and restrictions with respect
   to this document.  Code Components extracted from this document must
   include Simplified BSD License text as described in Section 4.e of
   the Trust Legal Provisions and are provided without warranty as
   described in the Simplified BSD License.






<span class="grey">Hethmon &amp; McMurray           Standards Track                    [Page 1]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-2" ></span>
<span class="grey"><a href="./rfc7151">RFC 7151</a>           FTP HOST Command for Virtual Hosts         March 2014</span>


Table of Contents

   <a href="#section-1">1</a>. Introduction ....................................................<a href="#page-2">2</a>
   <a href="#section-2">2</a>. Document Conventions ............................................<a href="#page-3">3</a>
      <a href="#section-2.1">2.1</a>. Basic Tokens ...............................................<a href="#page-3">3</a>
      <a href="#section-2.2">2.2</a>. Server Replies .............................................<a href="#page-4">4</a>
   <a href="#section-3">3</a>. The HOST Command ................................................<a href="#page-4">4</a>
      <a href="#section-3.1">3.1</a>. Syntax of the HOST Command .................................<a href="#page-5">5</a>
      <a href="#section-3.2">3.2</a>. HOST Command Semantics .....................................<a href="#page-7">7</a>
           <a href="#section-3.2.1">3.2.1</a>. REIN Command Semantics ..............................<a href="#page-8">8</a>
           <a href="#section-3.2.2">3.2.2</a>. User-PI Usage of HOST ...............................<a href="#page-9">9</a>
           <a href="#section-3.2.3">3.2.3</a>. State Diagrams .....................................<a href="#page-11">11</a>
      <a href="#section-3.3">3.3</a>. HOST Command Errors .......................................<a href="#page-16">16</a>
      <a href="#section-3.4">3.4</a>. FEAT Response for HOST Command ............................<a href="#page-17">17</a>
   <a href="#section-4">4</a>. Security Considerations ........................................<a href="#page-17">17</a>
   <a href="#section-5">5</a>. IANA Considerations ............................................<a href="#page-19">19</a>
   <a href="#section-6">6</a>. References .....................................................<a href="#page-19">19</a>
      <a href="#section-6.1">6.1</a>. Normative References ......................................<a href="#page-19">19</a>
      <a href="#section-6.2">6.2</a>. Informative References ....................................<a href="#page-20">20</a>
   <a href="#appendix-A">Appendix A</a>. Unworkable Alternatives ...............................<a href="#page-21">21</a>
     <a href="#appendix-A.1">A.1</a>. Overloading the CWD Command ................................<a href="#page-21">21</a>
     <a href="#appendix-A.2">A.2</a>. Overloading the ACCT Command ...............................<a href="#page-21">21</a>
     <a href="#appendix-A.3">A.3</a>. Overloading the USER Command ...............................<a href="#page-22">22</a>
     <a href="#appendix-A.4">A.4</a>. Conclusion .................................................<a href="#page-23">23</a>
   <a href="#appendix-B">Appendix B</a>. Acknowledgements ......................................<a href="#page-23">23</a>

<span class="h2"><a class="selflink" id="section-1" href="#section-1">1</a>.  Introduction</span>

   It is common on the Internet for many DNS names to resolve to a
   single IP address.  This practice has introduced the concept of a
   "virtual host", where a host appears to exist as an independent
   entity but, in reality, shares its physical resources with one or
   more similar hosts.

   Such an arrangement presents some problems for FTP servers, because
   an FTP server distinguishes incoming FTP connections by IP addresses
   rather than DNS names.  Therefore, all DNS names that share a common
   IP address are handled by the same FTP server and share the same
   Network Virtual File System (NVFS).

   This means that different virtual hosts cannot offer different
   virtual file systems to clients, nor can they offer different
   authentication systems.  Any scheme to overcome this issue needs to
   indicate not only the destination IP address but also the virtual
   hostname that is associated with the desired virtual FTP server.
   Typical user-FTP processes currently use hostnames to perform
   hostname-to-IP-address resolution and then ignore hostnames for the




<span class="grey">Hethmon &amp; McMurray           Standards Track                    [Page 2]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-3" ></span>
<span class="grey"><a href="./rfc7151">RFC 7151</a>           FTP HOST Command for Virtual Hosts         March 2014</span>


   rest of the FTP session; therefore, any mechanism to overcome this
   issue would require modifications to the user protocol interpreter
   (user-PI) and server protocol interpreter (server-PI).

   It should be noted that this same problem existed for HTTP/1.0 as
   defined in [<a href="./rfc1945" title="&quot;Hypertext Transfer Protocol -- HTTP/1.0&quot;">RFC1945</a>] and was resolved in HTTP/1.1 as defined in
   [<a href="./rfc2616" title="&quot;Hypertext Transfer Protocol -- HTTP/1.1&quot;">RFC2616</a>] through the addition of the Host request header field.  The
   goal of this document is to bring a similar level of feature parity
   to FTP by introducing a new HOST command that allows user-FTP
   processes to specify which virtual host to connect to for a
   server-FTP process that is handling requests for multiple virtual
   hosts on a single IP address.

<span class="h2"><a class="selflink" id="section-2" href="#section-2">2</a>.  Document Conventions</span>

   The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
   "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this
   document are to be interpreted as described in [<a href="./rfc2119" title="&quot;Key words for use in RFCs to Indicate Requirement Levels&quot;">RFC2119</a>].

   In examples, "C&gt;" and "S&gt;" indicate lines sent by the client and
   server, respectively.

   This document also uses notation defined in [<a href="./rfc959" title="&quot;File Transfer Protocol (FTP)&quot;">RFC959</a>] and [<a href="./rfc1123" title="&quot;Requirements for Internet Hosts - Application and Support&quot;">RFC1123</a>].
   In particular, the terms "reply", "user", "NVFS", "NVT", "file",
   "pathname", "FTP commands", "DTP", "user-FTP process", "user-PI",
   "user-DTP", "server-FTP process", "server-PI", "server-DTP", "mode",
   "type", "control connection", "data connection", and "ASCII", are all
   used here as defined there.

   The required syntax is defined using the Augmented BNF defined in
   [<a href="./rfc5234" title="&quot;Augmented BNF for Syntax Specifications: ABNF&quot;">RFC5234</a>].  Some general ABNF definitions are required throughout the
   document; they will be defined in subsequent sections.

   With the increased use of virtualization technologies, there may be
   several possible definitions for the term "virtual host".  This
   document follows the definition from <a href="./rfc3875#section-4.1.14">Section&nbsp;4.1.14 of [RFC3875]</a>,
   where several virtual hosts share the same IP address, and hostnames
   are used by the server-FTP process to route user-PI sessions to the
   appropriate virtual host.

<span class="h3"><a class="selflink" id="section-2.1" href="#section-2.1">2.1</a>.  Basic Tokens</span>

   This document imports the core definitions given in <a href="./rfc5234#appendix-B">Appendix&nbsp;B of
   [RFC5234]</a>.  There, definitions will be found for basic ABNF elements
   like ALPHA, DIGIT, SP, etc.  To that, the following term is added for
   use in this document.

      TCHAR = VCHAR / SP / HTAB    ; visible plus white space



<span class="grey">Hethmon &amp; McMurray           Standards Track                    [Page 3]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-4" ></span>
<span class="grey"><a href="./rfc7151">RFC 7151</a>           FTP HOST Command for Virtual Hosts         March 2014</span>


   The VCHAR (from [<a href="./rfc5234" title="&quot;Augmented BNF for Syntax Specifications: ABNF&quot;">RFC5234</a>]) and TCHAR rules give basic character types
   from varying subsets of the ASCII character set for use in various
   commands and responses.

   Note that in ABNF, string literals are case insensitive.  That
   convention is preserved in this document and implies that FTP
   commands and parameters that are added by this specification have
   values that can be represented in any case.  That is, "HOST" is the
   same as "host", "Host", "HoSt", etc.  Similarly, because domain names
   are defined to be case insensitive, "ftp.example.com" is the same as
   "Ftp.Example.Com", "fTp.eXample.cOm", etc.

<span class="h3"><a class="selflink" id="section-2.2" href="#section-2.2">2.2</a>.  Server Replies</span>

   <a href="./rfc959#section-4.2">Section&nbsp;4.2 of [RFC959]</a> defines the format and meaning of replies by
   the server-PI to FTP commands from the user-PI.  Those reply
   conventions are used here without change.

      error-response = error-code SP *TCHAR CRLF
      error-code     = ("4" / "5") 2DIGIT

   Implementers should note that the ABNF syntax used in this document
   and other FTP-related documents (but that was not used in [<a href="./rfc959" title="&quot;File Transfer Protocol (FTP)&quot;">RFC959</a>])
   sometimes shows replies using the one-line format.  Unless otherwise
   explicitly stated, multi-line responses are also permitted.
   Implementers should assume that, unless stated to the contrary, any
   reply to any FTP command (including QUIT) can be of the multi-line
   format described in [<a href="./rfc959" title="&quot;File Transfer Protocol (FTP)&quot;">RFC959</a>].

   Throughout this document, replies will be identified by the three-
   digit code that is their first element.  Thus, the term "500 reply"
   means a reply from the server-PI using the three-digit code "500".

<span class="h2"><a class="selflink" id="section-3" href="#section-3">3</a>.  The HOST Command</span>

   A new command, "HOST", is added to the FTP command set in order to
   allow a server-FTP process to determine to which of possibly many
   virtual hosts the client wishes to connect.  If a HOST command is
   sent, it MUST be issued before the user is authenticated, as this
   will allow the authentication scheme and set of authorized users to
   be dependent upon the virtual host that is chosen.

   Server-FTP processes MUST treat a situation in which the HOST command
   is issued more than once before the user has been authenticated as
   though only the last HOST command had been sent, and return the
   appropriate reply for the last HOST command.  Server-FTP processes





<span class="grey">Hethmon &amp; McMurray           Standards Track                    [Page 4]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-5" ></span>
<span class="grey"><a href="./rfc7151">RFC 7151</a>           FTP HOST Command for Virtual Hosts         March 2014</span>


   MUST treat a situation in which the HOST command is issued after the
   user has been authenticated as an erroneous sequence of commands and
   return a 503 reply.

   Servers should note that the response to the HOST command is a
   sensible time to send their "welcome" message.  This allows the
   message to be personalized for any virtual hosts that are supported.
   It also allows the client to determine, via the FEAT response, the
   languages or representations supported by the server and select an
   appropriate one via the LANG command.  See [<a href="./rfc2640" title="&quot;Internationalization of the File Transfer Protocol&quot;">RFC2640</a>] for more
   information.

   It should be noted that user-PI implementations that were created
   before the introduction of the HOST command will not support this new
   command.  A similar problem existed with the introduction of the Host
   header for HTTP in [<a href="./rfc2616" title="&quot;Hypertext Transfer Protocol -- HTTP/1.1&quot;">RFC2616</a>], and HTTP server implementations had to
   determine how best to accommodate HTTP requests from down-level
   clients that did not support the Host header.  With this in mind,
   server-FTP processes will need to determine how best to accommodate
   FTP requests from down-level FTP clients that do not support the HOST
   command, but those considerations are outside the scope of this
   document.

<span class="h3"><a class="selflink" id="section-3.1" href="#section-3.1">3.1</a>.  Syntax of the HOST Command</span>

   The HOST command is defined as follows.  Note that [<a href="./rfc3986" title="&quot;Uniform Resource Identifier (URI): Generic Syntax&quot;">RFC3986</a>] remains
   the normative specification for the syntactic form of IPv4 and IPv6
   address literals, in order to ensure identical presentation in 'ftp'
   URI hostname parts and in the protocol element specified here.

      host-command  = "HOST" SP hostname CRLF
      hostname      = domain / IP-literal

      domain        = sub-domain *("." sub-domain)
      sub-domain    = let-dig [ldh-str]
      let-dig       = ALPHA / DIGIT
      ldh-str       = *( ALPHA / DIGIT / "-" ) let-dig

      IP-literal    = ( "[" IPv6address "]" ) / IPv4address

      IPv6address   = &lt;see <a href="./rfc3986#section-3.2.2">[RFC3986] Section&nbsp;3.2.2</a>&gt;
      IPv4address   = &lt;see <a href="./rfc3986#section-3.2.2">[RFC3986] Section&nbsp;3.2.2</a>&gt;

      host-response = host-ok / error-response
      host-ok       = "220" [ SP *TCHAR ] CRLF






<span class="grey">Hethmon &amp; McMurray           Standards Track                    [Page 5]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-6" ></span>
<span class="grey"><a href="./rfc7151">RFC 7151</a>           FTP HOST Command for Virtual Hosts         March 2014</span>


   The "hostname" rule is a restricted form of the "host" rule specified
   in [<a href="./rfc3986" title="&quot;Uniform Resource Identifier (URI): Generic Syntax&quot;">RFC3986</a>].  Details of the additional restrictions imposed by this
   document are given in the discussion of the syntax that occurs later
   in this section; they aim at simplifying implementations by only
   allowing what currently is specified precisely and in use on the
   Internet.

   As with all FTP commands, the "HOST" command word is case independent
   and can be specified in any character case desired.

   The "hostname" (given as a parameter) specifies the virtual host to
   which access is desired.  This SHOULD be the same hostname that was
   used to obtain the IP address to which the FTP control connection was
   made, after any client conversions have been completed that convert
   an abbreviated or local alias to a complete (fully qualified) domain
   name, but before resolving a DNS alias (owner of a CNAME resource
   record) to its canonical name.

   Internationalization of domain names is only supported through the
   use of Internationalized Domain Names for Applications (IDNA)
   "A-labels" for &lt;sub-domain&gt; as described in [<a href="./rfc5890" title="&quot;Internationalized Domain Names for Applications (IDNA): Definitions and Document Framework&quot;">RFC5890</a>].  For example,
   the following HOST command specifies an internationalized
   domain name:

      HOST xn--e1afmkfd.com

   If the user was given an IPv4 or IPv6 literal address, and
   consequently was not required to derive the literal address from a
   hostname, the client MAY send the HOST command with the IPv4 or IPv6
   literal address as specified to it.  While it may seem
   counterintuitive to specify a literal address by using the HOST
   command after the client has already connected to the server using a
   literal address, this should be expected behavior because a user-FTP
   process should not be required to differentiate between a fully
   qualified domain name and an IPv4 or IPv6 network literal address.
   That being said, if the IPv4 or IPv6 literal address specified by the
   client does not match the literal address for the server, the server
   MUST respond with a 504 reply to indicate that the IPv4 or IPv6
   literal address is not valid.

   When the hostname parameter contains a literal address, square
   brackets are expected to disambiguate IPv6 address syntax from port
   numbers syntax.  Therefore, if the literal address is an IPv6
   address, the IPv6 address is required to be enclosed in square
   brackets (after eliminating any syntax that might also -- but is not
   required to -- be enclosed in brackets, and from which the server
   deduced that a literal address had been specified).  For example, the




<span class="grey">Hethmon &amp; McMurray           Standards Track                    [Page 6]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-7" ></span>
<span class="grey"><a href="./rfc7151">RFC 7151</a>           FTP HOST Command for Virtual Hosts         March 2014</span>


   following examples MAY be sent if the client had been instructed to
   connect to "192.0.2.1", "2001:db8::c000:201", or "::192.0.2.1",
   respectively, and IPv6 syntax is preferred:

      HOST 192.0.2.1
      HOST [2001:db8::c000:201]
      HOST [::192.0.2.1]

   The client MUST NOT send the port number as part of the HOST command,
   even when the client has been instructed to connect to a non-standard
   port.  The reason for this requirement is that the user-PI will have
   established a connection to the server-PI before the HOST command is
   sent; therefore, specifying a different port with the HOST command
   has no meaning.  For example, the server-PI MUST respond with a 501
   reply if the client sends a HOST command with syntax like either of
   the following examples:

      HOST 192.0.2.1:2112
      HOST [2001:db8::c000:201]:2112

   The hostname parameter is otherwise to be treated as a fully
   qualified domain name or relative name as those terms are defined in
   <a href="./rfc1034#section-3.1">Section&nbsp;3.1 of [RFC1034]</a>.  This implies that the name is to be
   treated as a case-independent string, meaning that uppercase ASCII
   characters are to be treated as equivalent to their corresponding
   lowercase ASCII characters but otherwise preserved as given.  It also
   implies some limits on the length of the parameter and of the
   components that create its internal structure.  Those limits are not
   altered in any way here.

   Neither [<a href="./rfc1034" title="&quot;Domain Names - Concepts and Facilities&quot;">RFC1034</a>] nor [<a href="./rfc1035" title="&quot;Domain Names - Implementation and Specification&quot;">RFC1035</a>] imposes any other restrictions upon
   what kinds of names can be stored in the DNS.  This specification,
   however, only allows the use of names that can be inferred from the
   ABNF grammar given for the "hostname".  Similarly, this specification
   restricts address literals to the IPv4 and IPv6 address families well
   established on the Internet.

<span class="h3"><a class="selflink" id="section-3.2" href="#section-3.2">3.2</a>.  HOST Command Semantics</span>

   Upon receiving the HOST command, before authenticating the user-PI, a
   server-FTP process SHOULD validate that the hostname given represents
   a valid virtual host for that server and, if it is valid, establish
   the appropriate environment for that virtual host.  The resultant
   actions needed to create that environment are not specified here and
   may range from doing nothing at all to performing a simple change of
   working directory, changing authentication schemes and/or username
   and password lists, or making much more elaborate state changes --
   such as creating isolated environments for each FTP session.



<span class="grey">Hethmon &amp; McMurray           Standards Track                    [Page 7]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-8" ></span>
<span class="grey"><a href="./rfc7151">RFC 7151</a>           FTP HOST Command for Virtual Hosts         March 2014</span>


   The 220 reply code for the HOST command is the same as the code that
   is used in the initial "welcome" message that is sent after the
   connection is established.

   If the hostname specified would normally be acceptable, but is
   temporarily unavailable, the server-FTP process SHOULD respond to the
   HOST command with a 421 reply and close the connection.

      Example:

      The server-FTP process is shutting down, so the server-FTP process
      responds to the HOST command with a 421 reply and closes the
      connection.  In this scenario, the 421 reply informs the client it
      can retry at another time.

   If the hostname specified is unknown at the server, or if the server
   is otherwise unwilling to treat the particular connection as a
   connection to the hostname specified, the server SHOULD respond with
   a 504 reply.

      Examples:

      The particular virtual host that was specified by the HOST command
      is disabled at the server.  The server responds with a 504 reply
      and keeps the connection open in order to allow the user-PI an
      opportunity to specify another virtual host with a subsequent HOST
      command.

      Alternatively, the server-FTP process might choose to route all
      connections with unknown hostnames to a different virtual host so
      that no connection attempts will result in failed connections.
      This design would be implementation specific and outside the scope
      of this specification.

<span class="h4"><a class="selflink" id="section-3.2.1" href="#section-3.2.1">3.2.1</a>.  REIN Command Semantics</span>

   As specified in [<a href="./rfc959" title="&quot;File Transfer Protocol (FTP)&quot;">RFC959</a>], the REIN command returns the state of the
   connection to what it was immediately after the transport connection
   was opened.  This specification makes no changes to that behavior.
   The effect of a HOST command MUST be reset if a REIN command is
   performed, and a new HOST command MUST be issued afterwards in order
   to connect to a virtual host.









<span class="grey">Hethmon &amp; McMurray           Standards Track                    [Page 8]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-9" ></span>
<span class="grey"><a href="./rfc7151">RFC 7151</a>           FTP HOST Command for Virtual Hosts         March 2014</span>


<span class="h4"><a class="selflink" id="section-3.2.2" href="#section-3.2.2">3.2.2</a>.  User-PI Usage of HOST</span>

   A user-PI MUST send the HOST command after opening the transport
   connection, or after any REIN command, before attempting to
   authenticate the user with the USER command.  The following example
   illustrates what a typical login sequence might look like when the
   HOST command is used:

      C&gt; HOST ftp.example.com
      S&gt; 220 Host accepted
      C&gt; USER foo
      S&gt; 331 Password required
      C&gt; PASS bar
      S&gt; 230 User logged in

   If a user-PI sends an additional HOST command before attempting to
   authenticate the user, a server-FTP process MUST treat the additional
   HOST command as though a previous HOST command was not sent and
   return the appropriate reply for the new HOST command.  For example,
   if a user specifies the wrong virtual hostname by mistake, sending a
   subsequent HOST command will rectify the error.  The following
   example illustrates what the login sequence might look like when the
   HOST command is sent twice before a user has been authenticated:

      C&gt; HOST foo.example.com
      S&gt; 220 Host accepted
      C&gt; HOST bar.example.com
      S&gt; 220 Host accepted
      C&gt; USER foo
      S&gt; 331 Password required
      C&gt; PASS bar
      S&gt; 230 User logged in

   The HOST command can be used in combination with the ACCT command to
   differentiate between a user's various accounts on a specific virtual
   host.  In this scenario, the user-PI sends a HOST command, which the
   server-PI uses to route activity to the correct virtual host; the
   user-PI sends credentials using the USER and PASS commands, which the
   server-PI validates; then, the user-PI sends an ACCT command to
   specify any additional account information for the server-PI
   implementation.  The following example illustrates a sequential
   series of client commands that specify both a HOST and ACCT, with the
   server responses omitted for brevity:

      C&gt; HOST ftp.example.com
      C&gt; USER foo
      C&gt; PASS bar
      C&gt; ACCT project1



<span class="grey">Hethmon &amp; McMurray           Standards Track                    [Page 9]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-10" ></span>
<span class="grey"><a href="./rfc7151">RFC 7151</a>           FTP HOST Command for Virtual Hosts         March 2014</span>


   This is also true when the HOST command is used with the AUTH and
   ADAT commands that are discussed in [<a href="./rfc2228" title="&quot;FTP Security Extensions&quot;">RFC2228</a>] and [<a href="./rfc4217" title="&quot;Securing FTP with TLS&quot;">RFC4217</a>].  In this
   scenario, the user-PI sends a HOST command, which the server-PI uses
   to route activity to the correct virtual host; then, the user-PI uses
   the AUTH and ADAT commands to negotiate the security mechanism and
   relevant authentication token(s) with the server-PI; then, the
   user-PI sends user credentials using the USER and PASS commands,
   which the server-PI validates, after which the user-PI MAY send an
   ACCT command to specify any additional account information for the
   server-PI implementation.  The following example illustrates a
   sequential series of client commands that specify both HOST and ACCT
   commands when used in conjunction with the security commands that are
   discussed in [<a href="./rfc2228" title="&quot;FTP Security Extensions&quot;">RFC2228</a>] and [<a href="./rfc4217" title="&quot;Securing FTP with TLS&quot;">RFC4217</a>], with the server responses
   omitted for brevity:

      C&gt; HOST ftp.example.com
      C&gt; AUTH &lt;mechanism-name&gt;
      C&gt; ADAT &lt;base64data&gt;
      C&gt; USER foo
      C&gt; PASS bar
      C&gt; ACCT project1

   An exception to the above scenario would be when a user-PI is
   providing the hostname in the "server_name" extension of a Transport
   Layer Security (TLS) extended client hello as discussed in [<a href="./rfc6066" title="&quot;Transport Layer Security (TLS) Extensions: Extension Definitions&quot;">RFC6066</a>].
   When the user-PI specifies the hostname in the "server_name"
   extension of a TLS extended client hello, the server-PI MUST verify
   that the hostname in the HOST command matches the value of the
   "server_name" extension.  The following example illustrates a
   sequential series of client commands that specify the HOST command
   when used in conjunction with the TLS extensions that are discussed
   in [<a href="./rfc6066" title="&quot;Transport Layer Security (TLS) Extensions: Extension Definitions&quot;">RFC6066</a>], with the server responses omitted for brevity:

      C&gt; AUTH TLS
      C&gt; HOST ftp.example.com
      C&gt; USER foo
      C&gt; PASS bar

   Additional security information about using the HOST command with the
   security extensions that are discussed in [<a href="./rfc2228" title="&quot;FTP Security Extensions&quot;">RFC2228</a>], [<a href="./rfc4217" title="&quot;Securing FTP with TLS&quot;">RFC4217</a>], and
   [<a href="./rfc6066" title="&quot;Transport Layer Security (TLS) Extensions: Extension Definitions&quot;">RFC6066</a>] is provided in <a href="#section-4">Section 4</a> of this document.










<span class="grey">Hethmon &amp; McMurray           Standards Track                   [Page 10]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-11" ></span>
<span class="grey"><a href="./rfc7151">RFC 7151</a>           FTP HOST Command for Virtual Hosts         March 2014</span>


<span class="h4"><a class="selflink" id="section-3.2.3" href="#section-3.2.3">3.2.3</a>.  State Diagrams</span>

   The state diagrams in this section illustrate typical sequences for
   command and reply interchange between the user-PI and server-PI.
   These diagrams are modeled on the similar diagrams in <a href="./rfc959#section-6">Section&nbsp;6 of
   [RFC959]</a>.

   In each diagram, the (B) "begin" state is assumed to occur after the
   transport connection has opened or after a REIN command has
   succeeded.  Other commands (such as FEAT [<a href="./rfc2389" title="&quot;Feature negotiation mechanism for the File Transfer Protocol&quot;">RFC2389</a>]) that require no
   authentication may have intervened.

   Additionally, a three-digit reply indicates a precise server reply
   code.  A single digit on a reply path indicates any server reply that
   begins with that digit, except where a precise server reply code is
   defined on another path.  For example, a single digit "5" will apply
   to "500", "501", "502", etc., when those reply codes are not
   expressly defined in the diagram.  For each command, there are three
   possible outcomes: success (S), failure (F), or error (E).  In the
   state diagrams below, we use the symbol "B" for "begin" and the
   symbol "W" for "wait for reply".

   For each of these diagrams, without any state transitions being
   shown, a REIN command will return the diagram from any wait state to
   the (B) "begin" state.


























<span class="grey">Hethmon &amp; McMurray           Standards Track                   [Page 11]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-12" ></span>
<span class="grey"><a href="./rfc7151">RFC 7151</a>           FTP HOST Command for Virtual Hosts         March 2014</span>


   The state diagram in Figure 1 shows a typical sequence of flow of
   control when HOST is used with USER and PASS to log in to a
   particular FTP virtual host.

              +---+   HOST    +---+ 1,3,5
              | B |----------&gt;| W |-----------------
              +---+           +---+                 |
                               | |                  |
                     2,500,502 | | 4,501,503,504    |
                 --------------   -----------       |
                |                            |      V
                V                   1        |    +---+
              +---+   USER    +---+--------------&gt;| E |
              |   |----------&gt;| W | 2        |    +---+
              +---+           +---+-------   |      ^
                               | |        |  |      |
                             3 | | 4,5    |  |      |
                 --------------   -----   |  |      |
                |                      |  |  |      |
                |                -------------------
                |              1|      |  |  |
                V               |      |   ------&gt;+---+
              +---+   PASS    +---+ 2  |     |    | S |
              |   |----------&gt;| W |--------------&gt;+---+
              +---+           +---+    |     |
                                |      |     |
                                |4,5   |     |
                                |      |      ---&gt;+---+
                                |       ---------&gt;| F |
                                 ----------------&gt;+---+

            Figure 1: Typical Login Sequence with HOST Command



















<span class="grey">Hethmon &amp; McMurray           Standards Track                   [Page 12]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-13" ></span>
<span class="grey"><a href="./rfc7151">RFC 7151</a>           FTP HOST Command for Virtual Hosts         March 2014</span>


   After a user has logged in, an additional account may be required by
   the server and specified by the client by using the ACCT command.
   With this in mind, the state diagram in Figure 2 shows a typical
   sequence of flow of control when HOST is used with USER and PASS to
   log in to an FTP virtual host and ACCT is used to specify an account.

              +---+   HOST    +---+ 1,3,5
              | B |----------&gt;| W |-----------------
              +---+           +---+                 |
                               | |                  |
                     2,500,502 | | 4,501,503,504    |
                 --------------   -------------     |
                |                              |    |
                V                   1          |    V
              +---+   USER    +---+--------------&gt;+---+
              |   |----------&gt;| W | 2       -----&gt;| E |
              +---+           +---+------  |  ---&gt;+---+
                               | |       | | | |
                             3 | | 4,5   | | | |
                 --------------   -----  | | | |
                |                      | | | | |
                |                      | | | | |
                |                ----------  | |
                |              1|      | |   | |
                V               |      | |   | |
              +---+   PASS    +---+ 2  |  -------&gt;+---+
              |   |----------&gt;| W |--------------&gt;| S |
              +---+           +---+   -----------&gt;+---+
                               | |   | |     | |
                             3 | |4,5| |     | |
                 --------------   --------   |  ----
                |                    | |  |  |      |
                |                    | |  |  |      |
                |                ------------       |
                |            1,3|    | |  |         |
                V               |   2| |  |         V
              +---+   ACCT    +---+--  |   ------&gt;+---+
              |   |----------&gt;| W | 4,5 ---------&gt;| F |
              +---+           +---+--------------&gt;+---+

           Figure 2: Login Sequence with HOST and ACCT Commands

   The state diagram in Figure 3 shows a typical sequence of flow of
   control when HOST is used with the AUTH and ADAT commands that are
   discussed in [<a href="./rfc2228" title="&quot;FTP Security Extensions&quot;">RFC2228</a>].  (NOTE: <a href="#section-4">Section 4</a> provides additional
   information about using the HOST command with TLS.)





<span class="grey">Hethmon &amp; McMurray           Standards Track                   [Page 13]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-14" ></span>
<span class="grey"><a href="./rfc7151">RFC 7151</a>           FTP HOST Command for Virtual Hosts         March 2014</span>


              +---+   HOST    +---+ 1,3,5
              | B |----------&gt;| W |------------------
              +---+           +---+                  |
                               | |                   |
                     2,500,502 | | 4,501,503,504     |
                 --------------   -------------      |
                |                              |     |
                V                              |     |
              +---+   AUTH    +---+ 4,5        |     |
              |   |----------&gt;| W |-----------&gt;|     |
              +---+           +---+            |     |
                           334 | |             |     |
                 --------------  |             |     |
                |            234 |             |     |
                |    ------------              |     |
                V   |               4,5        |     |
              +---+ | ADAT    +---+-----------&gt;|     |
              |   |----------&gt;| W | 335        |     |
              +---+ |         +---+-----       |     |
                ^   |           |       |      |     |
                |   |           |       |      |     |
                 -----------------------       |     |
                    |           |              |     |
                ----        235 |              |     |
               |  --------------               |     |
               | |                             |     V
               V V                  1          |   +---+
              +---+   USER    +---+---------------&gt;| E |
              |   |----------&gt;| W | 2          |   +---+
              +---+           +---+-------     |     ^
                               | |        |    |     |
                             3 | | 4,5    |    |     |
                 --------------   ------  |    |     |
                |                       | |    |     |
                |                --------------------
                |              1|       | |    |
                V               |       |  -------&gt;+---+
              +---+   PASS    +---+ 2   |      |   | S |
              |   |----------&gt;| W |---------------&gt;+---+
              +---+           +---+     |      |
                                |       |      |
                                |4,5    |      |
                                |       |       --&gt;+---+
                                |        ---------&gt;| F |
                                 -----------------&gt;+---+

         Figure 3: Login Sequence with HOST and AUTH/ADAT Commands




<span class="grey">Hethmon &amp; McMurray           Standards Track                   [Page 14]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-15" ></span>
<span class="grey"><a href="./rfc7151">RFC 7151</a>           FTP HOST Command for Virtual Hosts         March 2014</span>


   After a user has logged in with the security commands that are
   discussed in [<a href="./rfc2228" title="&quot;FTP Security Extensions&quot;">RFC2228</a>], an additional account may be required by the
   server and specified by the client by using the ACCT command.  The
   state diagram in Figure 4 shows a typical sequence of flow of control
   when HOST is used with the AUTH and ADAT commands to log in to an FTP
   virtual host and ACCT is used to specify an account.

              +---+   HOST    +---+ 1,3,5
              | B |----------&gt;| W |------------------
              +---+           +---+                  |
                               | |                   |
                     2,500,502 | | 4,501,503,504     |
                +--------------   --------------     |
                |                               |    |
                V                               |    |
              +---+   AUTH    +---+ 4,5         |    |
              |   |----------&gt;| W |------------&gt;|    |
              +---+           +---+             |    |
                           334 | |              |    |
                 --------------  |              |    |
                |            234 |              |    |
                |    ------------               |    |
                V   |               4,5         |    |
              +---+ | ADAT    +---+------------&gt;|    |
              |   |----------&gt;| W | 335         |    |
              +---+ |         +---+-----        |    |
                ^   |           |       |       |    |
                |   |           |       |       |    |
                 -----------------------        |    |
                    |           |               |    |
                ----         235|               |    |
               |  --------------                |    |
               | |                              |    |
               V V                  1           |    V
              +---+   USER    +---+---------------&gt;+---+
              |   |----------&gt;| W | 2        -----&gt;| E |
              +---+           +---+-------  |  ---&gt;+---+
                               | |        | | | |
                             3 | | 4,5    | | | |
                 --------------   ------  | | | |
                |                       | | | | |
                |                -----------  | |
                |              1|       | |   | |
                V               |       | |   | |
              +---+   PASS    +---+ 2   |  -------&gt;+---+
              |   |----------&gt;| W |---------------&gt;| S |
              +---+           +---+   ------------&gt;+---+
                               | |   |  |     | |



<span class="grey">Hethmon &amp; McMurray           Standards Track                   [Page 15]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-16" ></span>
<span class="grey"><a href="./rfc7151">RFC 7151</a>           FTP HOST Command for Virtual Hosts         March 2014</span>


                             3 | |4,5|  |     | |
                 --------------   ---------   |  ----
                |                    |  |  |  |      |
                |                -------------       |
                |            1,3|    |  |  |         |
                V               |   2|  |  |         V
              +---+   ACCT    +---+--   |   ------&gt;+---+
              |   |----------&gt;| W | 4,5  ---------&gt;| F |
              +---+           +---+---------------&gt;+---+

      Figure 4: Login Sequence with HOST and AUTH/ADAT/ACCT Commands

<span class="h3"><a class="selflink" id="section-3.3" href="#section-3.3">3.3</a>.  HOST Command Errors</span>

   The server-PI SHOULD return a 500 or 502 reply if the HOST command is
   unrecognized or unimplemented, as specified in [<a href="./rfc959" title="&quot;File Transfer Protocol (FTP)&quot;">RFC959</a>].  For
   example, a server-PI that predates or otherwise does not conform to
   this specification would be expected to return a 500 or 502 reply.

   As discussed in <a href="#section-3">Section 3</a> of this document, if a HOST command is sent
   after a user has been authenticated, the server MUST treat the
   situation as an invalid sequence of commands and return a 503 reply.

   A 501 reply SHOULD be sent if the hostname given is syntactically
   invalid, and a 504 reply SHOULD be sent if a syntactically valid
   hostname is not a valid virtual hostname for the server.  In all such
   cases, the server-FTP process MUST do one of the following:

   a.  Ignore the HOST command and act as if a HOST command had not been
       sent.  A user-FTP process MAY then send a subsequent HOST command
       with a different hostname.

   b.  Close the connection.

   A user-PI receiving a 500 or 502 reply to a HOST command SHOULD
   assume that the server-PI does not implement virtual servers by using
   the HOST command.  The user-PI MAY then proceed to log in as if the
   HOST command had not been sent.

   A user-PI receiving an error reply that is different from the errors
   that have been described here SHOULD assume that the virtual HOST is
   unavailable and terminate communications.

   A server-PI that receives a USER command to begin the authentication
   sequence without having received a HOST command SHOULD NOT reject the
   USER command.  Clients that conform to earlier FTP specifications do
   not send HOST commands.  In this case, the server MAY act as if some
   default virtual host had been explicitly selected, or the server MAY



<span class="grey">Hethmon &amp; McMurray           Standards Track                   [Page 16]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-17" ></span>
<span class="grey"><a href="./rfc7151">RFC 7151</a>           FTP HOST Command for Virtual Hosts         March 2014</span>


   enter an environment that is different from that of any supported
   virtual hosts, perhaps one in which a union of all available accounts
   exists and that presents an NVFS that appears to contain
   subdirectories that contain the NVFS for all supported virtual hosts.

<span class="h3"><a class="selflink" id="section-3.4" href="#section-3.4">3.4</a>.  FEAT Response for HOST Command</span>

   When replying to the FEAT command [<a href="./rfc2389" title="&quot;Feature negotiation mechanism for the File Transfer Protocol&quot;">RFC2389</a>], a server-FTP process
   that supports the HOST command MUST include a line containing the
   single word "HOST".  This word is case insensitive, but it SHOULD be
   sent in upper case so as to maximize interoperability with disparate
   implementations.  That is, the response SHOULD be:

      C&gt; FEAT
      S&gt; 211- &lt;any descriptive text&gt;
      S&gt;  ...
      S&gt;  HOST
      S&gt;  ...
      S&gt; 211 End

   The ellipses indicate placeholders where other features may be
   included but are not required.  The one-space indentation of the
   feature lines is mandatory [<a href="./rfc2389" title="&quot;Feature negotiation mechanism for the File Transfer Protocol&quot;">RFC2389</a>].

<span class="h2"><a class="selflink" id="section-4" href="#section-4">4</a>.  Security Considerations</span>

   As discussed in <a href="#section-3">Section 3</a> of this document, a server implementation
   MUST treat an additional HOST command that was sent before a user has
   been authenticated as though a previous HOST command was not sent.
   In this situation, the server implementation MUST reset the
   authentication environment, as that would allow for segregation
   between the security environments for each virtual host on an FTP
   server.  The implementation details for security environments may
   vary greatly based on the requirements of each server implementation
   and operating system, and those details are outside the scope of the
   protocol itself.  For example, a virtual host "foo.example.com" on an
   FTP server might use a specific username and password list, while the
   virtual host "bar.example.com" on the same FTP server might use a
   different username and password list.  In such a scenario, resetting
   the security environment is necessary for the virtual servers to
   appear to behave independently from a client perspective, while the
   actual server implementation details are irrelevant at the protocol
   level.

   <a href="./rfc4217#section-15.1.1">Section&nbsp;15.1.1 of [RFC4217]</a> discusses the use of X.509 certificates
   for server authentication.  Taking the information from that document
   into account, when securing FTP sessions with the security mechanisms
   that are defined in [<a href="./rfc4217" title="&quot;Securing FTP with TLS&quot;">RFC4217</a>], client implementations SHOULD verify



<span class="grey">Hethmon &amp; McMurray           Standards Track                   [Page 17]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-18" ></span>
<span class="grey"><a href="./rfc7151">RFC 7151</a>           FTP HOST Command for Virtual Hosts         March 2014</span>


   that the hostname that they specify in the parameter for the HOST
   command matches the identity that is specified in the server's X.509
   certificate in order to prevent man-in-the-middle attacks.

   When the HOST command is used in combination with the FTP security
   extensions that were introduced in [<a href="./rfc2228" title="&quot;FTP Security Extensions&quot;">RFC2228</a>] and [<a href="./rfc4217" title="&quot;Securing FTP with TLS&quot;">RFC4217</a>], the HOST
   command SHOULD precede the security handshake when the user-PI is not
   providing the "server_name" in the extended client hello as defined
   in [<a href="./rfc6066" title="&quot;Transport Layer Security (TLS) Extensions: Extension Definitions&quot;">RFC6066</a>].  This allows both user-FTP and server-FTP processes to
   map an FTP HOST with the correct server name in the server's
   certificate.  If the HOST command is sent after the security
   handshake, then mapping an FTP HOST to the correct security
   certificate will not take place before the secure session is
   established.

   For example, if a server-FTP process has multiple virtual hosts
   defined and no hostname has been sent from a user-FTP process, the
   server-FTP process will be unable to route the connection to the
   correct virtual host when the connection is established.  In this
   situation, the server-FTP process will be forced to choose a virtual
   host that will respond.  When the user-PI attempts to negotiate a
   secure connection, the virtual host to which the connection was
   routed will respond with its server certificate during the security
   handshake.  If the virtual host that was chosen by the server-FTP
   process does not match the virtual host to which the user-FTP process
   had intended to connect, the user-PI will be unable to verify the
   server's identity as presented in the server certificate message.

   However, if the user-PI is providing the "server_name" in the
   extended client hello as defined in <a href="./rfc6066#section-3">Section&nbsp;3 of [RFC6066]</a>, the
   user-PI MAY provide the HOST command after the security handshake
   because the server will be able to route the connection to the
   correct virtual host based on the contents of the "server_name"
   extension and the client will be able to verify the server's identity
   as presented in the corresponding server certificate message.
   However, the server-PI MUST verify that the name in the HOST command
   matches the "server_name" that is provided in the extended client
   hello.

   In general, client implementations SHOULD protect user credentials by
   using the FTP security extensions that were introduced in [<a href="./rfc2228" title="&quot;FTP Security Extensions&quot;">RFC2228</a>]
   and [<a href="./rfc4217" title="&quot;Securing FTP with TLS&quot;">RFC4217</a>]; a detailed discussion for securing FTP sessions can be
   found in those documents, and a general discussion of security issues
   related to FTP can be found in [<a href="./rfc2577" title="&quot;FTP Security Considerations&quot;">RFC2577</a>].







<span class="grey">Hethmon &amp; McMurray           Standards Track                   [Page 18]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-19" ></span>
<span class="grey"><a href="./rfc7151">RFC 7151</a>           FTP HOST Command for Virtual Hosts         March 2014</span>


<span class="h2"><a class="selflink" id="section-5" href="#section-5">5</a>.  IANA Considerations</span>

   IANA has registered the following FTP extension according to the
   procedure established by [<a href="./rfc5797" title="&quot;FTP Command and Extension Registry&quot;">RFC5797</a>]:

   +------+---------+-------------+------+------+----------------------+
   | cmd  | FEAT    | description | type | conf | RFC#s/References and |
   |      | Code    |             |      |      | Notes                |
   +------+---------+-------------+------+------+----------------------+
   | HOST | HOST    | Hostname    | a    | o    | <a href="./rfc7151">RFC 7151</a>             |
   +------+---------+-------------+------+------+----------------------+

<span class="h2"><a class="selflink" id="section-6" href="#section-6">6</a>.  References</span>

<span class="h3"><a class="selflink" id="section-6.1" href="#section-6.1">6.1</a>.  Normative References</span>

   [<a id="ref-RFC959">RFC959</a>]   Postel, J. and J. Reynolds, "File Transfer Protocol
              (FTP)", STD 9, <a href="./rfc959">RFC 959</a>, October 1985.

   [<a id="ref-RFC1034">RFC1034</a>]  Mockapetris, P., "Domain Names - Concepts and Facilities",
              STD 13, <a href="./rfc1034">RFC 1034</a>, November 1987.

   [<a id="ref-RFC1035">RFC1035</a>]  Mockapetris, P., "Domain Names - Implementation and
              Specification", STD 13, <a href="./rfc1035">RFC 1035</a>, November 1987.

   [<a id="ref-RFC1123">RFC1123</a>]  Braden, R., "Requirements for Internet Hosts - Application
              and Support", STD 3, <a href="./rfc1123">RFC 1123</a>, October 1989.

   [<a id="ref-RFC2119">RFC2119</a>]  Bradner, S., "Key words for use in RFCs to Indicate
              Requirement Levels", <a href="https://www.rfc-editor.org/bcp/bcp14">BCP 14</a>, <a href="./rfc2119">RFC 2119</a>, March 1997.

   [<a id="ref-RFC2228">RFC2228</a>]  Horowitz, M. and S. Lunt, "FTP Security Extensions", <a href="./rfc2228">RFC</a>
              <a href="./rfc2228">2228</a>, October 1997.

   [<a id="ref-RFC2389">RFC2389</a>]  Hethmon, P. and R. Elz, "Feature negotiation mechanism for
              the File Transfer Protocol", <a href="./rfc2389">RFC 2389</a>, August 1998.

   [<a id="ref-RFC2640">RFC2640</a>]  Curtin, B., "Internationalization of the File Transfer
              Protocol", <a href="./rfc2640">RFC 2640</a>, July 1999.

   [<a id="ref-RFC3986">RFC3986</a>]  Berners-Lee, T., Fielding, R., and L. Masinter, "Uniform
              Resource Identifier (URI): Generic Syntax", STD 66, <a href="./rfc3986">RFC</a>
              <a href="./rfc3986">3986</a>, January 2005.

   [<a id="ref-RFC4217">RFC4217</a>]  Ford-Hutchinson, P., "Securing FTP with TLS", <a href="./rfc4217">RFC 4217</a>,
              October 2005.





<span class="grey">Hethmon &amp; McMurray           Standards Track                   [Page 19]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-20" ></span>
<span class="grey"><a href="./rfc7151">RFC 7151</a>           FTP HOST Command for Virtual Hosts         March 2014</span>


   [<a id="ref-RFC5234">RFC5234</a>]  Crocker, D. and P. Overell, "Augmented BNF for Syntax
              Specifications: ABNF", STD 68, <a href="./rfc5234">RFC 5234</a>, January 2008.

   [<a id="ref-RFC5890">RFC5890</a>]  Klensin, J., "Internationalized Domain Names for
              Applications (IDNA): Definitions and Document Framework",
              <a href="./rfc5890">RFC 5890</a>, August 2010.

   [<a id="ref-RFC6066">RFC6066</a>]  Eastlake, D., "Transport Layer Security (TLS) Extensions:
              Extension Definitions", <a href="./rfc6066">RFC 6066</a>, January 2011.

<span class="h3"><a class="selflink" id="section-6.2" href="#section-6.2">6.2</a>.  Informative References</span>

   [<a id="ref-RFC1945">RFC1945</a>]  Berners-Lee, T., Fielding, R., and H. Nielsen, "Hypertext
              Transfer Protocol -- HTTP/1.0", <a href="./rfc1945">RFC 1945</a>, May 1996.

   [<a id="ref-RFC2577">RFC2577</a>]  Allman, M. and S. Ostermann, "FTP Security
              Considerations", <a href="./rfc2577">RFC 2577</a>, May 1999.

   [<a id="ref-RFC2616">RFC2616</a>]  Fielding, R., Gettys, J., Mogul, J., Frystyk, H.,
              Masinter, L., Leach, P., and T. Berners-Lee, "Hypertext
              Transfer Protocol -- HTTP/1.1", <a href="./rfc2616">RFC 2616</a>, June 1999.

   [<a id="ref-RFC3875">RFC3875</a>]  Robinson, D. and K. Coar, "The Common Gateway Interface
              (CGI) Version 1.1", <a href="./rfc3875">RFC 3875</a>, October 2004.

   [<a id="ref-RFC5797">RFC5797</a>]  Klensin, J. and A. Hoenes, "FTP Command and Extension
              Registry", <a href="./rfc5797">RFC 5797</a>, March 2010.
























<span class="grey">Hethmon &amp; McMurray           Standards Track                   [Page 20]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-21" ></span>
<span class="grey"><a href="./rfc7151">RFC 7151</a>           FTP HOST Command for Virtual Hosts         March 2014</span>


<span class="h2"><a class="selflink" id="appendix-A" href="#appendix-A">Appendix A</a>.  Unworkable Alternatives</span>

   Due to the level of scope for adding a new command to FTP, a brief
   discussion of suggested alternatives to a HOST command and their
   respective limitations is warranted.  The suggested alternatives that
   are discussed in this appendix have been proposed in the past, but
   each of these ideas was deemed insufficient for the reasons listed
   within each section of this appendix.

<span class="h3"><a class="selflink" id="appendix-A.1" href="#appendix-A.1">A.1</a>.  Overloading the CWD Command</span>

   One suggested method to emulate a form of virtual hosts would be for
   the client to simply send a CWD command after connecting, using the
   virtual hostname as the argument to the CWD command.  This would
   allow the server-FTP process to implement the file stores of the
   virtual hosts as subdirectories in its NVFS.  This suggestion is
   simple in concept, and most server-FTP implementations support this
   without requiring any code changes.  While this method is simple to
   describe and implement, it suffers from several drawbacks:

   a.  The CWD command is available only after the user-PI has
       authenticated itself to the server-FTP process.  Thus, all
       virtual hosts would be required to share a common authentication
       scheme if they used this method.

   b.  To make the virtual host truly transparent, either the server-FTP
       process needs to be modified to include information that shows
       the special nature of this first CWD command (negating most of
       the advantage of this scheme), or all users must see the same
       identical NVFS view upon connecting (they must connect in the
       same initial directory), or the NVFS must implement the full set
       of virtual host directories at each possible initial directory
       for any possible user.

   c.  Unless the server is specially modified, a user connecting this
       way to a virtual host would be able to easily move to any other
       virtual host supported at the same server-FTP process, exposing
       the nature of the virtual host.

<span class="h3"><a class="selflink" id="appendix-A.2" href="#appendix-A.2">A.2</a>.  Overloading the ACCT Command</span>

   Another suggested method would be to simply overload the ACCT command
   for FTP virtual hosts, but this proposal is unacceptable for several
   reasons with regard to when the ACCT command is sent during the
   request flow.  Sections <a href="#section-5.4">5.4</a> and <a href="#section-6">6</a> of [<a href="./rfc959" title="&quot;File Transfer Protocol (FTP)&quot;">RFC959</a>] document the request
   flow for a login sequence as USER -&gt; PASS -&gt; ACCT.  This flow of
   commands may be acceptable when you are considering a single user




<span class="grey">Hethmon &amp; McMurray           Standards Track                   [Page 21]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-22" ></span>
<span class="grey"><a href="./rfc7151">RFC 7151</a>           FTP HOST Command for Virtual Hosts         March 2014</span>


   having multiple accounts on an FTP server, but it fails to
   differentiate between virtual hosts when you consider the following
   two issues:

   a.  The first problem with overloading the ACCT command is
       certificate negotiation when using the FTP security extensions
       that are documented in [<a href="./rfc2228" title="&quot;FTP Security Extensions&quot;">RFC2228</a>] and [<a href="./rfc4217" title="&quot;Securing FTP with TLS&quot;">RFC4217</a>].  In order to
       safeguard user credentials, negotiation of the security mechanism
       and certificate must occur before login credentials are sent by
       the client.  The problem with using the ACCT command in this
       scenario is that there is no way of ensuring that the certificate
       matches the correct virtual host before the user credentials are
       sent.

   b.  The second problem with overloading the ACCT command is how user
       credentials are implemented for FTP virtual hosts.  FTP server
       implementations may allow the use of custom user credentials on a
       per-virtual-host basis.  For example, in one particular
       implementation the virtual host negotiation occurs, and then the
       user credentials are looked up using the account mechanism that
       is specific to that virtual host.  So once again the virtual host
       negotiation must take place before the user credentials are sent.

<span class="h3"><a class="selflink" id="appendix-A.3" href="#appendix-A.3">A.3</a>.  Overloading the USER Command</span>

   An additional suggestion would be to overload well-known syntax
   through the existing USER command, as illustrated in the following
   example:

      C&gt; USER foo@example.com
      S&gt; 331 Password required
      C&gt; PASS bar
      S&gt; 230 User logged in

   In this example, the user "foo" might be attempting to log on to the
   virtual host "example.com" on an FTP server.  This suggestion may
   seem plausible at first, but it introduces several implementation
   problems.  For example:

   a.  Some network environments already use the "username@hostname"
       syntax for network credentials, where the "hostname" portion
       refers to the location of the user's credentials within the
       network hierarchy.  Using the "foo@example.com" syntax, it
       becomes difficult to differentiate between the user "foo" logging
       into a virtual host that is named "example.com" on an FTP server
       versus the user "foo@example.com" logging into an FTP server with
       no specified virtual host.




<span class="grey">Hethmon &amp; McMurray           Standards Track                   [Page 22]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-23" ></span>
<span class="grey"><a href="./rfc7151">RFC 7151</a>           FTP HOST Command for Virtual Hosts         March 2014</span>


   b.  When using the FTP security extensions that are documented in
       [<a href="./rfc2228" title="&quot;FTP Security Extensions&quot;">RFC2228</a>] and [<a href="./rfc4217" title="&quot;Securing FTP with TLS&quot;">RFC4217</a>], negotiation of the security mechanism
       and certificate must occur before login credentials are sent by
       the client.  More specifically, the AUTH/ADAT commands must be
       sent before the USER command in order to safeguard user
       credentials.  If you overload the USER command, there is no way
       of ensuring that the certificate matches the correct virtual host
       before the user credentials are sent by the client.

<span class="h3"><a class="selflink" id="appendix-A.4" href="#appendix-A.4">A.4</a>.  Conclusion</span>

   After examining the above alternatives, and in order to obtain an
   adequate emulation of "real" FTP servers, it was concluded that
   supporting virtual hosts will require both client and server
   modifications.  Therefore, a new FTP command seems the most likely
   solution to provide the required level of support.

<span class="h2"><a class="selflink" id="appendix-B" href="#appendix-B">Appendix B</a>.  Acknowledgements</span>

   Robert Elz and Paul Hethmon provided a detailed discussion of the
   HOST command in their Internet-Draft titled "Extensions to FTP" as
   part of their work with the FTPEXT Working Group of the IETF.  Their
   work formed the basis for much of this document, and their help has
   been greatly appreciated.  They would also like to credit Bernhard
   Rosenkraenzer for having first suggested and described the HOST
   command.

   Several people have provided a wealth of constructive feedback about
   earlier versions of this document that has helped to shape its
   development; many of their suggestions have been incorporated, and
   their contributions are gratefully acknowledged.  There are far too
   many to mention here, but the authors of this document would like to
   specifically thank Alexey Melnikov, Alfred Hoenes, John Klensin, Joe
   Touch, Paul Ford-Hutchinson, Daniel Stenberg, Mykyta Yevstifeyev,
   Alec Rowell, Jaroslav Dunajsky, Wade Hilmo, Anthony Bryan, and Barry
   Leiba for their assistance.















<span class="grey">Hethmon &amp; McMurray           Standards Track                   [Page 23]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-24" ></span>
<span class="grey"><a href="./rfc7151">RFC 7151</a>           FTP HOST Command for Virtual Hosts         March 2014</span>


Authors' Addresses

   Paul Hethmon
   Hethmon Brothers
   2305 Chukar Road
   Knoxville, TN  37923
   USA

   EMail: phethmon@hethmon.com


   Robert McMurray
   Microsoft Corporation
   One Microsoft Way
   Redmond, WA  98052
   USA

   EMail: robmcm@microsoft.com

































Hethmon &amp; McMurray           Standards Track                   [Page 24]
</pre>