Debian Codegraph @

rfc1639.html

raw
1 <pre>Network Working Group D. Piscitello
2 Request for Comments: 1639 Core Competence, Inc.
3 Obsoletes: <a href="./rfc1545">1545</a> June 1994
4 Category: Experimental
5
6
7 <span class="h1">FTP Operation Over Big Address Records (FOOBAR)</span>
8
9 Status of this Memo
10
11 This memo defines an Experimental Protocol for the Internet
12 community. This memo does not specify an Internet standard of any
13 kind. Discussion and suggestions for improvement are requested.
14 Distribution of this memo is unlimited.
15
16 Abstract
17
18 This paper describes a convention for specifying address families
19 other than the default Internet address family in FTP commands and
20 replies.
21
22 Introduction
23
24 In the File Transfer Protocol (STD 9, <a href="./rfc959">RFC 959</a>), the PORT command
25 argument &lt;host-port&gt; specifies the data port to be used to establish
26 a data connection for FTP (STD 9, <a href="./rfc959">RFC 959</a>). This argument is also
27 used in the PASV reply to request the server-DTP to listen on a data
28 port other than its default data port. This RFC specifies a method
29 for assigning addresses other than 32-bit IPv4 addresses to data
30 ports through the specification of a "long Port (LPRT)" command and
31 "Long Passive (LPSV)" reply, each having as its argument a &lt;long-
32 host-port&gt;, which allows for additional address families, variable
33 length network addresses and variable length port numbers.
34
35 This is a general solution, applicable for all "next generation" IP
36 alternatives, as well as for other network protocols than IP. This
37 revision also extends FTP to allow for its operation over transport
38 interfaces other than TCP.
39
40 Acknowledgments
41
42 Many thanks to all the folks in the IETF who casually mentioned how
43 to do this, but who left it to me to write this RFC. Special thanks
44 to Rich Colella, Bob Ullmann, Steve Lunt, Jay Israel, Jon Postel,
45 Shawn Ostermann, and Tae Kyong Song, who contributed to this work.
46
47
48
49
50
51
52 <span class="grey">Piscitello [Page 1]</span></pre>
53 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-2" ></span>
54 <span class="grey"><a href="./rfc1639">RFC 1639</a> FTP Over Big Address June 1994</span>
55
56
57 <span class="h2"><a class="selflink" id="section-1" href="#section-1">1</a>. Background</span>
58
59 The PORT command of File Transfer Protocol allows users to specify an
60 address other than the default data port for the transport connection
61 over which data are transferred. The PORT command syntax is:
62
63 PORT &lt;SP&gt; &lt;host-port&gt; &lt;CRLF&gt;
64
65 The &lt;host-port&gt; argument is the concatenation of a 32-bit internet
66 &lt;host-address&gt; and a 16-bit TCP &lt;port-address&gt;. This address
67 information is broken into 8-bit fields and the value of each field
68 is transmitted as a decimal number (in character string
69 representation). The fields are separated by commas. A PORT command
70 is thus of the general form "PORT h1,h2,h3,h4,p1,p2", where h1 is the
71 high order 8 bits of the internet host address.
72
73 The &lt;host-port&gt; argument is also used by the PASV reply, and in
74 certain negative completion replies.
75
76 To accommodate larger network addresses anticipated for all IP "next
77 generation" alternatives, and to accommodate FTP operation over
78 network and transport protocols other than IP, new commands and reply
79 codes are needed for FTP.
80
81 <span class="h2"><a class="selflink" id="section-2" href="#section-2">2</a>. The LPRT Command</span>
82
83 The LPRT command allows users to specify a "long" address for the
84 transport connection over which data are transferred. The LPRT
85 command syntax is:
86
87 LPRT &lt;SP&gt; &lt;long-host-port&gt; &lt;CRLF&gt;
88
89 The &lt;long-host-port&gt; argument is the concatenation of the following
90 fields;
91
92 o an 8-bit &lt;address-family&gt; argument (af)
93
94 o an 8-bit &lt;host-address-length&gt; argument (hal)
95
96 o a &lt;host-address&gt; of &lt;host-address-length&gt; (h1, h2, ...)
97
98 o an 8-bit &lt;port-address-length&gt; (pal)
99
100 o a &lt;port-address&gt; of &lt;port-address-length&gt; (p1, p2, ...)
101
102 The initial values assigned to the &lt;address-family&gt; argument take the
103 value of the version number of IP (see Assigned Numbers, STD 2, <a href="./rfc1340">RFC</a>
104 <a href="./rfc1340">1340</a>); values in the range of 0-15 decimal are thus reserved for IP
105
106
107
108 <span class="grey">Piscitello [Page 2]</span></pre>
109 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-3" ></span>
110 <span class="grey"><a href="./rfc1639">RFC 1639</a> FTP Over Big Address June 1994</span>
111
112
113 and assigned by IANA. Values in the range 16-255 are available for
114 the IANA to assign to all other network layer protocols over which
115 FTP may be operated.
116
117 Relevant assigned &lt;address-family&gt; numbers for FOOBAR are:
118
119 Decimal Keyword
120 ------ -------
121 0 reserved
122 1-3 unassigned
123 4 Internet Protocol (IP)
124 5 ST Datagram Mode
125 6 SIP
126 7 TP/IX
127 8 PIP
128 9 TUBA
129 10-14 unassigned
130 15 reserved
131 16 Novell IPX
132
133 The value of each field is broken into 8-bit fields and the value of
134 each field is transmitted as an unsigned decimal number (in character
135 string representation, note that negative numbers are explicitly not
136 permitted). The fields are separated by commas.
137
138 A LPRT command is thus of the general form
139
140 LPRT af,hal,h1,h2,h3,h4...,pal,p1,p2...
141
142 where h1 is the high order 8 bits of the internet host address, and
143 p1 is the high order 8 bits of the port number (transport address).
144
145 <span class="h2"><a class="selflink" id="section-3" href="#section-3">3</a>. The LPSV Command</span>
146
147 The L(ONG) PASSIVE command requests the server-DTP to listen on a
148 data port other than its default data port and to wait for a
149 connection rather than initiate one upon receipt of a transfer
150 command. The response to this command includes the address family,
151 host address length indicator, host address, port address length, and
152 port address of the listener process at the server. The reply code
153 and text for entering the passive mode using a long address is 228
154 (Interpretation according to FTP is: positive completion reply 2yz,
155 connections x2z, passive mode entered using long address xy8).
156
157 The suggested text message to accompany this reply code is:
158
159 228 Entering Long Passive Mode
160 (af, hal, h1, h2, h3,..., pal, p1, p2...)
161
162
163
164 <span class="grey">Piscitello [Page 3]</span></pre>
165 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-4" ></span>
166 <span class="grey"><a href="./rfc1639">RFC 1639</a> FTP Over Big Address June 1994</span>
167
168
169 <span class="h2"><a class="selflink" id="section-4" href="#section-4">4</a>. Permanent Negative Completion Reply Codes</span>
170
171 The negative completion reply codes that are associated with syntax
172 errors in the PORT and PASV commands are appropriate for the LPRT and
173 LPSV commands (500, 501). An additional negative completion reply
174 code is needed to distinguish the case where a host supports the LPRT
175 or LPSV command, but does not support the address family specified.
176
177 Of the FTP function groupings defined for reply codes (syntax,
178 information, connections, authentication and accounting, and file
179 system), "connections" seems the most logical choice; thus, an
180 additional negative command completion reply code, 521 is added, with
181 the following suggested textual message:
182
183 521 Supported address families are (af1, af2, ..., afn)
184
185 Where (af1, af2, ..., afn) are the values of the version numbers of
186 the "next generation" or other protocol families supported. (Note: it
187 has been suggested that the families could also be represented by
188 ASCII strings.)
189
190 <span class="h2"><a class="selflink" id="section-5" href="#section-5">5</a>. Rationale</span>
191
192 An explicit address family argument in the LPRT command and LPSV
193 reply allows the Internet community to experiment with a variety of
194 "next generation IP" and other network layer protocol alternatives
195 within a common FTP implementation framework. (It also allows the use
196 of a different address family on the command and data connections.)
197 An explicit length indicator for the host address is necessary
198 because some of the IPNG alternatives make use of variable length
199 addresses. An explicit host address is necessary because FTP says
200 it's necessary.
201
202 The decision to provide a length indicator for the port number is not
203 as obvious, and certainly goes beyond the necessary condition of
204 having to support TCP port numbers.
205
206 Currently, at least one IPng alternative (TP/IX) supports longer port
207 addresses. And given the increasingly "multi-protocol" nature of the
208 Internet, it seems reasonable that someone, somewhere, might wish to
209 operate FTP operate over Appletalk, IPX, and OSI networks as well as
210 TCP/IP networks. (In theory, FTP should operate over *any* transport
211 protocol that offers the same service as TCP.) Since some of these
212 transport protocols may offer transport selectors or port numbers
213 that exceed 16 bits, a length indicator may be desirable. If FTP must
214 indeed be changed to accommodate larger network addresses, it may be
215 prudent to determine at this time whether the same flexibility is
216 useful or necessary with respect to transport addresses.
217
218
219
220 <span class="grey">Piscitello [Page 4]</span></pre>
221 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-5" ></span>
222 <span class="grey"><a href="./rfc1639">RFC 1639</a> FTP Over Big Address June 1994</span>
223
224
225 <span class="h2"><a class="selflink" id="section-6" href="#section-6">6</a>. Conclusions</span>
226
227 The mechanism defined here is simple, extensible, and meets both IPNG
228 and multi-protocol internet needs.
229
230 <span class="h2"><a class="selflink" id="section-7" href="#section-7">7</a>. References</span>
231
232 STD 9, <a href="./rfc959">RFC 959</a> Postel, J., and J. Reynolds, "File Transfer Protocol",
233 STD 9, <a href="./rfc959">RFC 959</a>, USC/Information Sciences Institute,
234 October 1985.
235
236 STD 2, <a href="./rfc1340">RFC 1340</a> Reynolds, J., and J. Postel, "Assigned Numbers",
237 STD 2, <a href="./rfc1340">RFC 1340</a>, USC/Information Sciences Institute,
238 July 1992. (Does not include recently assigned IPv7
239 numbers).
240
241 STD 3, <a href="./rfc1123">RFC 1123</a> Braden, R., Editor, "Requirements for Internet
242 Hosts - Application and Support", STD 3, <a href="./rfc1123">RFC 1123</a>,
243 USC/Information Sciences Institute, October 1989.
244
245 <span class="h2"><a class="selflink" id="section-8" href="#section-8">8</a>. Security Considerations</span>
246
247 Security issues are not discussed in this memo.
248
249 <span class="h2"><a class="selflink" id="section-9" href="#section-9">9</a>. Author's Address</span>
250
251 David M. Piscitello
252 Core Competence, Inc.
253 1620 Tuckerstown Road
254 Dresher, PA 19025
255
256 EMail: [email protected]
257
258
259
260
261
262
263
264
265
266
267
268
269
270
271
272
273
274
275
276 Piscitello [Page 5]
277 </pre>