About site: Internet/Protocols/FTP/Related RFCs - RFC0463
Return to Computers also Computers
  About site: http://www.rfc-editor.org/rfc/rfc463.txt

Title: Internet/Protocols/FTP/Related RFCs - RFC0463 FTP Comments and response to RFC430
Hotscripts_com Directory which lists free and commercial message board providers.

Mackstar Web design, Flash, and database interaction in English and Japanese.

Hexadecimal_Character_Codes_in_Java_Unicode All spaces, punctuation, accented characters, and any other non-ASCII characters are replaced with \unn; in Java Unicode format encoding, where nn is equivalent to the hexadecimal number representing

RFC_1365 An IP Address Extension Proposal. K. Siyan. September 1992.

pgasync A PostgreSQL client library for Python with special support for Twisted. [Open Source, BSD]

Webtrax_Help A log file analysis program for NCSA web server logs, which produces up to twenty different graphical and tabular reports.

  Alexa statistic for http://www.rfc-editor.org/rfc/rfc463.txt





Get your Google PageRank






Please visit: http://www.rfc-editor.org/rfc/rfc463.txt
  Related sites for http://www.rfc-editor.org/rfc/rfc463.txt
    Extranet_Policy Defines the requirement that third party organizations requiring access to the organization's networks must sign a third-party connection agreement. [PDF]
    SourceForge_net__ReactOS ReactOS project page.
    Random_Structures_and_Algorithms Poznan, Poland; 2--6 August 1999.
    Stan\'s_Visual_Basic_For_Beginners Info about getting started with Visual Basic programming as well as free programs.
    Talking_Panda_-_iLingo Language translator for iPod.
    RFC_0270 Correction to BBN Report No. 1822 (NIC NO 7958). A.M. McKenzie. January 1972.
    How\'s_it_going? Multi-project management and documentation software, that saves time, and improves communication among project managers, team members, project office staff, stakeholders, and executives. For Microsoft
    TomSoft Offers three screen savers for Windows 95/98/NT.
    SPAA_2001 13th ACM Symposium on Parallel Algorithms and Architectures. Crete Island, Greece. July 4-6, 2001.
    Developer_Fusion_-_C# Free source code, articles and tutorials for C# and .NET developers, plus a discussion forum.
    15_Dollar_Domains Offers registration along with affiliate and volume discount programs.
    Electronic_Studio Projects for pic microcontrollers, aimed at both professionals and students. Site available in English and Spanish.
    Fl_Table A generic row/column widget to encapsulate rows and columns of any kind of widgets, or even custom widgets that are entirely based on the low level.
    JICSLP\'96_Workshop_on_Parallelism_and_Implementation_Technology Post-JICSLP'96 Workshop and 1996 Compulog Net Area Meeting on Parallelism and Implementation Technology for (Constraint) Logic Programming Languages.
    Saarland,_University Department of Computer Science. Areas of research include combinatorics, computational geometry, compilers for real-time embedded systems, formal modelling of circuits, computer architecture, descrip
    Proverb_Design Brisbane, Australia based company, providing complete website design services.
    Christanto,_Bionito_-_Visigraphic Specialise in web design and development, graphic design, and photo editing. Based in Surabaya, East Java, Indonesia.
    McGinnis,_Brian Specializing in web design, search engine marketing and promotion. Also offers graphic design, java programming, and multimedia integration. Includes resume. Located in Remsenburg, New York, United St
    Eyron_Software_Group Localizes software into Hebrew.
    Gnews_Publisher A webbased news/article management script. Authors publish their news in categories and content schedule.
This is websites2007.org cache of m/ as retrieved on 2008.09.06 websites2007.org's cache is the snapshot that we took of the page as we crawled the web. The page may have changed since that time.
Network Working Group Abhay K. BhushanRFC # 463 MIT-DMCGNIC # 14573 February 21, 1973 FTP Comments and Response to RFC 430 Most of the comments in RFC 430 by Bob Braden are useful suggestionswhich should be included in the forthcoming official FTP specification.This RFC represents my response to Braden's comments and other views.These comments should be useful for the FTP meeting on March 16 at BBN(announcement warning AAM NIC #14417). The results of the FTP subgroupmeeting held at BBN on January 25 will be published in RFC 4541 (arepublished?).SPECIFIC RESPONSES TO RFC 430. Item A1 - I will let Bob Braden handle the "print file" issues (the "still" should be removed). Item A2 - I agree that concessions are undesirable and should be removed unless people cannot "live" without them. Item A3 - I strongly support "bit flag coding" for descriptors. Other definition improvement suggestions are ok too. Item A4 - The diagram was useful. An alternate one is given on page 17 of RFC 454. I prefer the latter. Item A5 - The FTP may not be privileged enough to alter passwords in many Host systems (e.g. Multics). I know that CCN allows changing passwords on-line. We can define a format for changing passwords in the pass command, but I don't think we can require that all servers allow password changing. This is a minor problem that can be easily solved. Item A6 - Yes, the comment that TYPE should be before BYTE was for bad implementations. The server should reject data transfer parameters only when the data transfer command is received. The order of the parameter-change commands is not important. Item A7 - I do agree that NCP's should be fixed. A 255 (socket number) reply should be required at a specific time, and NCP's should be able to provide it (this also permits the proposed GSOC command). Let us find out at next meeting if there is anyone who cannot live with this new requirement.Bhushan [Page 1] RFC 463 FTP Comments and Response to RFC 430 February 1973 Item A8 - Yes. Item B - There are at least two ways to solve the FTP parameter encoding problem presented by Bob Braden. One is to allow multiple letter in the TYPE command as suggested by Bob and the other is to have a new command such as FORM (which could be P or U). Other solutions are equally acceptable to me. Item C - Our emphasis should be on working protocol as well as elegance. I like the proposed GSOC command over the listen. In fact GSOC can be used for all data connection security checking. The 255 reply should be sent with GSOC only, and the server should use only those sockets for data connection. Item D - We need more discussion on the issue of site dependent FTP parameters. I will put it on the agenda for the forthcoming FTP meeting.FURTHER COMMENTS 1. The command-reply sequence needs to be tightened in both specification and implementations to allow convenient use of FTP by programs or "automatons". 2. A 300 reply greeting upon first connecting to the FTP server should be required and not optional. This avoids the programs having to wait an arbitrary time for such a greeting before issuing commands. Commands may only be sent after the 300 reply is received from the server. 3. RFC 454 needs a discussion of transfer between two FTP servers arranged by the user via the LSTN or GSOC commands. 4. Perhaps we should allow specification of data transfer parameters in a single command line (for reasons of efficiency). A suggested format is to have separate the parameters bunched together in a single line (requiring only a single reply). Consider the following sequences: STRU F TYPE I BYTE 36 MODE S reply - 200 OK 5. Further discussion of MAIL and MAIL.file commands seems necessary. Perhaps we will get some useful input from the MAIL meeting at SRI on February 23, The following issues seem particularly relevant to me: a) Allowing mail to multiple users. It should be required that FTP servers allow this.Bhushan [Page 2] RFC 463 FTP Comments and Response to RFC 430 February 1973 b) Using NIC idents. FTP servers should accept some standard form of user name. This could be NIC idents or last name with optional use of initials. c) Uniform conventions for who the mail is from, day, time, etc., and how the mail is delivered to user. The mail usually gets tagged twice or sometimes not tagged at all. Perhaps we need a different mechanism for indicating who the mail is from than provided by the USER command. d) handling bulk or junk mail (particularly the NIC documents that may be sent on-line by the NIC). Perhaps mail.file should put a file in user's directory and notify him of the same. The user does not see all the junk on his console but can print the file on a printer and read that class of mail at his leisure. [ This RFC was put into machine readable form for entry ] [ into the online RFC archives by Alex McKenzie with ] [ support from GTE, formerly BBN Corp. 9/99 ]Bhushan [Page 3]
 

FTP

Comments

and

response

to

RFC430

http://www.rfc-editor.org/rfc/rfc463.txt

RFC0463 2008 September

dvd rental

dvd


FTP Comments and response to RFC430

Rules

© 2008 Internet Explorer 5+ or Netscape 6+
Recommended Sites: 1. Arts - Business - Computers - Games - Health - Home - Kids and Teens - News - Recreation - Reference - Regional - Science - Shopping - Society - Sports - World Miss Gallery - Top Anime Hentai - DVD rental by mail - Hummer Dealer - Credit Cards - News - Remortgages - Xbox Mod Chip
2008-09-06 22:57:02

Copyright 2005, 2006 by Webmaster
Websites is cool :) 97Magnesy - 0844 - Bingo - Hotell Munchen - Hotel Florencia