The Prior Art Database and Publishing service will be updated on Sunday, February 25th, from 1-3pm ET. You may experience brief service interruptions during that time.
Browse Prior Art Database

FTP Operation Over Big Address Records (FOOBAR) (RFC1639)

IP.com Disclosure Number: IPCOM000002475D
Original Publication Date: 1994-Jun-01
Included in the Prior Art Database: 2000-Sep-12
Document File: 4 page(s) / 9K

Publishing Venue

Internet Society Requests For Comment (RFCs)

Related People

D. Piscitello: AUTHOR


This paper describes a convention for specifying address families other than the default Internet address family in FTP commands and replies.

This text was extracted from a ASCII document.
This is the abbreviated version, containing approximately 29% of the total text.

Network Working Group D. Piscitello

Request for Comments: 1639 Core Competence, Inc.

Obsoletes: 1545 June 1994

Category: Experimental

FTP Operation Over Big Address Records (FOOBAR)

Status of this Memo

This memo defines an Experimental Protocol for the Internet

community. This memo does not specify an Internet standard of any

kind. Discussion and suggestions for improvement are requested.

Distribution of this memo is unlimited.


This paper describes a convention for specifying address families

other than the default Internet address family in FTP commands and



In the File Transfer Protocol (STD 9, RFC 959), the PORT command

argument specifies the data port to be used to establish

a data connection for FTP (STD 9, RFC 959). This argument is also

used in the PASV reply to request the server-DTP to listen on a data

port other than its default data port. This RFC specifies a method

for assigning addresses other than 32-bit IPv4 addresses to data

ports through the specification of a "long Port (LPRT)" command and

"Long Passive (LPSV)" reply, each having as its argument a

host-port>, which allows for additional address families, variable

length network addresses and variable length port numbers.

This is a general solution, applicable for all "next generation" IP

alternatives, as well as for other network protocols than IP. This

revision also extends FTP to allow for its operation over transport

interfaces other than TCP.


Many thanks to all the folks in the IETF who casually mentioned how

to do this, but who left it to me to write this RFC. Special thanks

to Rich Colella, Bob Ullmann, Steve Lunt, Jay Israel, Jon Postel,

Shawn Ostermann, and Tae Kyong Song, who contributed to this work.

1. Background

The PORT command of File Transfer Protocol allows users to specify an

address other than the default data port for the transport connection

over which data are transferred. The PORT command syntax is:


The argument is the concatenation of a 32-bit internet

and a 16-bit TCP . This address

information is broken into 8-bit fields and the value of each field

is transmitted as a decimal number (in character string

representation). The fields are separated by commas. A PORT command

is thus of the general form "PORT h1,h2,h3,h4,p1,p2", where h1 is the

high order 8 bits of the internet host addre...