REPOST: Re: A new forum is up! Q: what means nntp

Fri Dec 28 20:28:38 EST 2001

ssthapa at classes.cs.uchicago.edu (Suchandra Thapa) writes:
>     Actually I believe rfc765 and rfc959 (FTP protocol) is superceded by 
> rfc1123 which outlines and corrects the specifications for the ftp, telnet, 
> smtp, and dns protocols. In particular interest to me, rfc1123 indicates that 
> pasv responses in the ftp protocol don't have to have the format of 
> 227 (h1,h2,h3,h4,p1,p2). This was something that the python ftplib assumed until
> the 2.2 release and which caused problems with anonftpd.

reference:
http://www.garlic.com/~lynn/rfcietff.htm

& click on RFCs that are also

"Standards (STD)"

and scroll down to STD-9

Note that most fields are "clickable" for instance FTP brings up:

FTP - (Stan) - File Transfer Protocol [port:21] 
959 (STD-9) - File Transfer Protocol
1415 - FTP-FTAM Gateway Specification

clicking on the ".txt" field will retrieve the actual RFC.

Clicking on various RFC nos &/or STD references will bring up the
appropriate information.

Various processes also do cross-checking of released rfc status as well as
information released in new STD1s for consistency. The "Obsoleted" section
use to appear as "Section 6.10" in earlier STD1s.

=============================

STD-9
959 (Stan) - File Transfer Protocol (FTP)

  959 is the "standard"

959 S
File Transfer Protocol, Postel J., Reynolds J., 1985/10/01 (69pp)
(.txt=147316) (STD-9) (Updated by 2228, 2640, 2773) (Obsoletes 765)
(Ref'ed By 2389) (FTP)

  959 has current updates 2228, 2640, & 2773 ... and is also ref'ed by 2389

2259 PS
File Transfer Protocol, Postel J., Reynolds J., 1985/10/01 (69pp)
(.txt=147316) (STD-9) (Updated by 2228, 2640, 2773) (Obsoletes 765)
(Ref'ed By 2389) (FTP)

  2259 is currently in proposed standard state

2640 PS
Internationalization of the File Transfer Protocol, Curtin B.,
1999/07/28 (27pp) (.txt=57204) (Updates 959)

  2640 is currently in proposed standard state

2773 E
Encryption using KEA and SKIPJACK, Housley R., Nace W., Yee P.,
2000/02/14 (9pp) (.txt=20008) (Updates 959)

  2773 is experimental 

2389 PS
Feature negotiation mechanism for the File Transfer Protocol, Elz R.,
Hethmon P., 1998/08/21 (9pp) (.txt=18536) (See Also 959)

  and 2389 is proposed standard state ... but doesn't update 959 but refers to it.

=========================

 ... also STD-3

STD-3
1122 (Stan) - Requirements for Internet hosts - communication layers
1123 (Stan) - Requirements for Internet hosts - application and support

1123 S

Requirements for Internet hosts - application and support, Braden R.,
1989/10/01 (98pp) (.txt=239721) (STD-3) (Updated by 2181, 2821)

  ... 1123 is standard but doesn't directly update FTP or 959 ... but does list
  requirements for Internet hosts - application and support, which is also updated
  by

2181 PS
Clarifications to the DNS Specification, Bush R., Elz R., 1997/07/31
(15pp) (.txt=36989) (Updated by 2535) (Updates 1034, 1035, 1123)
(DNS-CLAR)

   2181 is proposed standard status

2821 PS
Simple Mail Transfer Protocol, Klensin J., 2001/04/24 (79pp)
(.txt=192504) (Obsoletes 821, 974, 1869) (Updates 1123) (SMTP)

====================

from 1123:

4.  FILE TRANSFER

   4.1  FILE TRANSFER PROTOCOL -- FTP

      4.1.1  INTRODUCTION

         The File Transfer Protocol FTP is the primary Internet standard
         for file transfer.  The current specification is contained in
         RFC-959 [FTP:1].

         FTP uses separate simultaneous TCP connections for control and
         for data transfer.  The FTP protocol includes many features,
         some of which are not commonly implemented.  However, for every
         feature in FTP, there exists at least one implementation.  The
         minimum implementation defined in RFC-959 was too small, so a
         somewhat larger minimum implementation is defined here.

         Internet users have been unnecessarily burdened for years by
         deficient FTP implementations.  Protocol implementors have
         suffered from the erroneous opinion that implementing FTP ought
         to be a small and trivial task.  This is wrong, because FTP has
         a user interface, because it has to deal (correctly) with the
         whole variety of communication and operating system errors that
         may occur, and because it has to handle the great diversity of
         real file systems in the world.

-- 
Anne & Lynn Wheeler   | lynn at garlic.com -  http://www.garlic.com/~lynn/ 

========= WAS CANCELLED BY =======:
Path: news.sol.net!spool0-nwblwi.newsops.execpc.com!newsfeeds.sol.net!newspump.sol.net!newsfeed.direct.ca!look.ca!newsfeed.dacom.co.kr!feeder.kornet.net!news1.kornet.net!ua4canc3ll3r
From: Anne & Lynn Wheeler <lynn at garlic.com>
Newsgroups: comp.lang.python
Subject: cmsg cancel <uvgeqerxi.fsf at earthlink.net>
Control: cancel <uvgeqerxi.fsf at earthlink.net>
Date: Mon, 31 Dec 2001 03:29:30 GMT
Organization: A poorly-installed InterNetNews site
Lines: 2
Message-ID: <cancel.uvgeqerxi.fsf at earthlink.net>
NNTP-Posting-Host: 211.57.49.2
X-Trace: news2.kornet.net 1009774921 27193 211.57.49.2 (31 Dec 2001 05:02:01 GMT)
X-Complaints-To: usenet at news2.kornet.net
NNTP-Posting-Date: Mon, 31 Dec 2001 05:02:01 +0000 (UTC)
X-No-Archive: yes
X-Unac4ncel: yes
X-Commentary: I love NewsAgent 1.10 and the Sandblaster Cancel Engine Build 74 (19 March 1999)

This message was cancelled from within Mozilla.